Bug 11799 - drakroam crashed (undefined value for mandatory argument 'sensitive')
Summary: drakroam crashed (undefined value for mandatory argument 'sensitive')
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 11778
  Show dependency treegraph
 
Reported: 2013-11-27 18:28 CET by José Jorge
Modified: 2013-11-28 14:56 CET (History)
0 users

See Also:
Source RPM: drakx-net-2.1-1.mga4
CVE:
Status comment:


Attachments

Description José Jorge 2013-11-27 18:28:17 CET
The "drakroam" program crashed. Drakbug-16.0 caught it.

Switching from a WPA2 network to an hotel free wifi with web login, after a suspend

undefined value for mandatory argument 'sensitive' encountered at /usr/lib/libDrakX/network/connection_manager/gtk.pm line 129.
Perl's trace:
standalone::bug_handler() called from /usr/lib/perl5/vendor_perl/5.18.1/x86_64-linux-thread-multi/Glib/Object/Introspection.pm:59
Glib::Object::Introspection::__ANON__() called from /usr/lib/perl5/vendor_perl/5.18.1/Gtk3/SimpleList.pm:401
Gtk3::SimpleList::TiedList::CLEAR() called from /usr/lib/libDrakX/network/connection_manager/gtk.pm:168
network::connection_manager::gtk::update_networks() called from /usr/lib/libDrakX/network/drakroam.pm:54
network::drakroam::update_on_connection_change() called from /usr/lib/libDrakX/network/drakroam.pm:124
network::drakroam::main() called from /usr/libexec/drakroam:30

Theme name: oxygen-gtk
Kernel version = 3.12.1-desktop-1.mga4
Distribution=Mageia release 4 (Cauldron) for x86_64
CPU=Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz
Comment 1 Manuel Hiebel 2013-11-28 14:51:22 CET
(bug 11764 was 8 line before)

Blocks: (none) => 11778
Assignee: bugsquad => thierry.vignaud
Summary: drakroam crashed => drakroam crashed (undefined value for mandatory argument 'sensitive')

Comment 2 Thierry Vignaud 2013-11-28 14:56:31 CET
Fixed in git

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.