The "drakroam" program crashed. Drakbug-15.65 caught it. Je lançais "gérer les réseaux sans fils". La surprise, c'est que la fenêtre apparait tout de même quand je répond à ce message ! you must be root to run this program at /usr/lib/libDrakX/common.pm line 387. Perl's trace: standalone::bug_handler() called from /usr/lib/libDrakX/common.pm:387 common::require_root_capability() called from /usr/lib/libDrakX/interactive.pm:113 interactive::vnew() called from /usr/sbin/drakroam:21 Theme name: oxygen-gtk Kernel version = 3.10.10-desktop-3.mga4 Distribution=Mageia release 4 (Cauldron) for x86_64 CPU=Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz
looks like there is no similar report. Can you reproduce this bug ? (adding colin as iirc the consolekit method to become root was changed)
CC: (none) => mageia, mageia, thierry.vignaud
I can't reproduce this bug.
Summary: drakroam crashed => drakroam crashed (you must be root to run this program)
*** Bug 11284 has been marked as a duplicate of this bug. ***
CC: (none) => rene
*** Bug 11301 has been marked as a duplicate of this bug. ***
CC: (none) => inster.css
Priority: Normal => release_blockerSummary: drakroam crashed (you must be root to run this program) => drakroam crashed (you must be root to run this program) (polkit update)
Assignee: bugsquad => mageia
I cannot actually reproduce this one either, but I still need to convert it to polkit anyway, so we'll see if it goes away at that point :)
I have the same bug. My wireless seems to disconnect every 30 minutes or so (I have a Intel Wireless-AC 7260). When I try to manually reconnect to my SSID from the taskbar, I have the same message as OP. I then have to manually open a console and "sudo drakroam" to get the wireless connected again. Network connections should be user owned and modifiable.
CC: (none) => nicblais
So I've now updated drakx-net to convert it to polkit. You should now be able to run drakroam and get an appropriate polkit dialog. There are still some issues with polkit conversion as it's not finalised, but I'm still working on it. Hopefully this bug is now fixed... but please reopen if it's still an issue on latest cauldron.
Status: NEW => RESOLVEDResolution: (none) => FIXED