Comment 26 for bug 284596
Revision history for this message
| terdon (terdon) wrote Re: nm-applet fail when another user is logged in (intrepid) | #26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
- How can you be sure that NetworkManager does not start, if the whole desktop is blocked?
Well, I have gnome-do and keyboard shortcuts which allow me to move around. It is only the desktop itself that is locked. I can get a terminal and run ps commands ok.
- Does starting KDE, then going to GNOME breaks the same way?
Yes, in the way described in this bug. If I load one WM first and then switch, the other has no network
- Do you see any error messages in ~/.xsession-errors after starting KDE the second time? (get it from the console)
Yes, loads, will not post them here.
"Basically, KDE should not rely on the network to work (obvious). "
Absolutely, yet it does... I think it is part of the fancy new desktop the folks at KDE have created.
"Again, please open a new report and post its address here. No need to spam all the people with something that's not stricly the same bug."
Fair enough, I will. But I still think that what I am experiencing is connected. I have now fixed it, but when I first logged on to kde it was broken. Running nm-applet fixed it. Sounds like its another effect of the same bug to me. If it isn't sorry for the spam. I will shut up now :)