Red Hat Bugzilla – Bug 367711
NM-gnome or knetworkmanager, but NOT both!
Last modified: 2007-11-30 17:12:21 EST
NetworkManager-gnome autostarts nm-applet under KDE. Please stop it.
knetworkmanager should control NM under KDE. Yes, I know it is broken and
replaced with the same nm-applet for now. The thing is that if you have both
NM-gnome and knetworkmanager, two instances of nm-applet are attempted with
very unpredictable results, including blocked logouts, etc. With
NetworkManager daemon off, it is even weirder.
Anyway, stop NetworkManager-gnome from starting nm-applet under KDE, please.
nm-applet blocking logouts is a separate issue (bz?).
It is my strong belief that both nm-applet (and knetworkmanager) should be
usable under *any* desktop, so to me, your suggestion isn't compatible with that.
What *is* missing in nm-applet, is an ability for an end-user to disable it, ie,
disable it auto-launching (knetworkmanager has/had that feature).
Do you want two applets launched together by default? As it stands right now,
two nm-applets are attempted to be launched. It is an ugly bug in the default
Cross-usability is great, but a default user shouldn't be cornered with the two
choices in his face, even when there will be a choice.
We don't want to duplicate everything (or anything) on the default desktop.
If you don't want both, then don't install both.
corrolary: if you *do* install both, the expectation should be to be able to use
both (or either, that's your choice).
It is not like I have a choice.
knetworkmanager depends on NetworkManager-gnome
The latter installs /etc/xdg/autostart/nm-applet.desktop
which is missing X-Gnome-UniqueApplet=true or something.
So you have
both starting the same damn thing.
Am I clear now?
I fail to the a problem, atm.
Are you seeing 2 instances of nm-applet? (I don't, it WORKSFORME).
When, the *real* knetworkmanager comes back, then yes, we'll have to have devise
a n upgrade strategy to handle this.
The second launch attempt sometimes blocks logout for me and others:
The fact that the second attempt just does NOTBOTHERYOU doesn't mean that it
won't SCREWOTHERS. This is a bug in NetworkManager-gnome package.
Even when you update knetworkmanager, nm-applet will continue to autostart on
KDE. My last comment in this bug, Thanks!
No one is suggesting bugs like what you (and others) seeing shouldn't fixed.
The trivial fix is to add
reassigning -> knetworkmanager
so that we can disable the 2nd (emulated) nm-applet launch.
(OnlyShowIn was reverted, and is not recommended, see bug #336021)
Sorry, I posted before I tried it. With OnlyShowIn=GNOME in nm-applet.desktop
and knetworkmanager installed, the hell breaks loose. I have no idea how, but
this interferes with kpowersave(!) and prevents it from starting very
Strange, I cannot verify this bug:
I installed a fresh copy of Fedora 8 on my system, created an entirely new,
virgin user, and still, I only have one applet.
Alexei, did that problem come up with an entirely new user on a virgin system
or did it happen on a system where you upgraded. If the second case is true,
can you describe the update path?
Btw., Alexei, please be aware that Rex' "WORKSFORME" wasn't an insult or
screaming but is a set phrase of the bugzilla language.
(In reply to comment #12)
> I only have one applet.
I didn't say that the second applet successfully launches. Most of the time it
fails. Sometimes it fails with consequences. Sometimes it prevents even the
first applet from normally starting, sometimes it blocks logouts.
nm-applet is a very raw application. In addition to the above symptoms, it
never reports if NetworkManager daemon is not running. It just just fails with
a different series of unpredictable consequences.
If you combine double-launch with stopped NetworkManager... Oh boy, good luck
* Tue Nov 06 2007 Rex Dieter <rdieter[AT]fedoraproject.org> - 0.2-0.7
- omit knetworkmanager-autostart, so nm-applet doesn't start twice (#367711)
- omit needless (icon) scriptlets
can you try this build, does it help?
Ok. This seems to work ok. All applets started fine.
knetworkmanager-0.2-0.7.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 374321 has been marked as a duplicate of this bug. ***
*** Bug 375331 has been marked as a duplicate of this bug. ***
why knetwork don't use knetwork instead of this horrible of nm-applet that even
don't have a quit button .
Sergio, knetworkmanager doesn't (yet) work with nm-0.7, see bug #298991