Description of problem: I have network controlled by NetworkManager. When I enable connection either by wi-fi or ethernet, I cannot start any of the draktools. I only see this error: No protocol specified Cannot be run in console mode. If program has console version, it is launched instead of graphical one. When I disconnect network, all starts fine. Version-Release number of selected component (if applicable): How reproducible: Always. Steps to Reproduce: 1. Enable some network connection. 2. Run any of draktools, for example drakrpm. Reproducible: Steps to Reproduce:
Are you sure the name of your box doesn't change when you do so?
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudSource RPM: drakconf-12.60-2.mga6.src.rpm, rpmdrake-6.20-1.mga5.src.rpm => drakconf-12.60-2.mga6.src.rpm
No, the name not changed, it's localhost. I also found this error not always happens when network is up. When I boot my system with network is up, I can start drakxtools. When I set network up, drakxtools still can start. But when I disconnect from my network, they won't start either with network connected or not. This happens when ethernet cable is not connected and wi-fi only in use.
I checked with ethernet instead of wi-fi - same behavior. After boot (either with network connected or not) drakxtools starts, after network disconnect not starts.
Hey Nikita, i am experiencing a similar issue which i've brought down to kdesu. If you don't mind, after a failed attempt of accessing the Mageia tools, could you run "/usr/lib64/kde4/libexec/kdesu dolphin" to see if that works at all? If it doesn't, then it shows that the problem is with the authentication, and not isolated to drakconf.
CC: (none) => klaye_parker
(In reply to Klaye p from comment #4) It does not. But I see different authentication window, than with draktools. After I enter password, nothing happens too. Output: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4 running... kdesu(32457)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0" kdesu(32457)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0" kdesu(32457)/kdesu (kdelibs) KDESu::KDESuPrivate::KCookie::getXCookie: No X authentication info set for display ":0"
Is this bug still valid?
CC: (none) => marja11
Yes. After I suspend my laptop and resume, I usually cannot run draktools until reboot.
(In reply to Nikita Krupenko from comment #7) > Yes. After I suspend my laptop and resume, I usually cannot run draktools > until reboot. That sounds as if you can before suspending. Can you?
Yes, it works right after boot.
(In reply to Nikita Krupenko from comment #9) > Yes, it works right after boot. And you can still start mcc in graphical mode after suspending and resuming, if you stop the network?
Summary: draktools cannot start in graphical mode if network connection is available => draktools cannot start in graphical mode after having suspended and resumed
Right now disabling network doesn't help :(
@ Nikita Do you mind trying again with current cauldron / Mga 6sta1 ?
Assignee: bugsquad => thierry.vignaud
I should be more clear: Is this bug still valid and is the summary of this bug correct?
Yes, it's still valid. The only thing I should note: disconnecting network doesn't help. Once I suspend my laptop, only reboot helps.
It's about several months that I don't see this bug any more.
(In reply to Nikita Krupenko from comment #15) > It's about several months that I don't see this bug any more. Good news, closing. Please reopen if it comes back.
Status: NEW => RESOLVEDResolution: (none) => FIXED