[Bug 679489] New: NM: network manager applet does not show up
https://bugzilla.novell.com/show_bug.cgi?id=679489 https://bugzilla.novell.com/show_bug.cgi?id=679489#c0 Summary: NM: network manager applet does not show up Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: qa@suse.de Found By: --- Blocker: --- Gnome desktop, NM Gnome applet. It was set up for autostart, probably it was started correctly but it didn't show up in systray. I disabled autostart for it, logout, log in, and executed it from terminal. This is the output: ** Message: applet now removed from the notification area ** (nm-applet:14380): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files. ** Message: applet now embedded in the notification area ** Message: applet now removed from the notification area ** (nm-applet:14380): WARNING **: fetch_connections_done: error fetching system connections: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files. Luckily I use eth0 for now, it works, but I cannot use any settings for NM because I don't have applet in systray. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=679489
https://bugzilla.novell.com/show_bug.cgi?id=679489#c1
--- Comment #1 from Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=679489
https://bugzilla.novell.com/show_bug.cgi?id=679489#c2
Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=679489
https://bugzilla.novell.com/show_bug.cgi?id=679489#c3
Maciej Pilichowski
https://bugzilla.novell.com/show_bug.cgi?id=679489
https://bugzilla.novell.com/show_bug.cgi?id=679489#c4
Vincent Untz
You are missing the fact that opensuse ships with such broken configuration (reopening).
How is it broken? Note that on livecd at least, we ship with NM enabled by default.
Two things: a) make up your mind and configure opensuse default settings to either USE or NOT use NM -- you cannot have both
I don't understand this point. It is not an issue to have nm-applet running. Is this what you consider as an issue?
b) another issue is, that if you know in advance NM is not operational, forbid launching it -- i.e. if user sets Yast to disable NM, then disable it, plain and simple
This is the same as a), isn't it?
c) error message is completely cryptic:
Does it error
** (nm-applet:14380): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.
tells you that NM was disabled by Yast? (it is not even flagged as error!)
It simply tells you NM is not running. Yes, I guess that could be improved. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=679489
https://bugzilla.novell.com/show_bug.cgi?id=679489#c5
Maciej Pilichowski
You are missing the fact that opensuse ships with such broken configuration (reopening).
How is it broken? Note that on livecd at least, we ship with NM enabled by default.
Enabled -- in network module (of Yast)? This is correct settings. In DVD version OS is shipped with NM disabled and NM-applet running. Of course NM-applet will fail to run, but user does not see it, because it silently quits.
a) make up your mind and configure opensuse default settings to either USE or NOT use NM -- you cannot have both I don't understand this point. It is not an issue to have nm-applet running. Is this what you consider as an issue?
Maybe I rephrase and ask you a question -- in DVD version for Gnome, the network should be controlled manually (old-school way) or by NM?
b) another issue is, that if you know in advance NM is not operational, forbid
launching it -- i.e. if user sets Yast to disable NM, then disable it, plain and simple
This is the same as a), isn't it?
Yes/No. Initial settings have nothing to do what algorithm you use for UI to prevent non-working results of user actions. However, if you add such algorithm, it would prevent you (OS maintainers) from ship OS with broken initial settings.
** (nm-applet:14380): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.
It simply tells you NM is not running. Yes, I guess that could be improved.
If it "simply" tell you that, it should simply tell it. Without translating message on bugzilla. I am glad you agree on this point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=679489
https://bugzilla.novell.com/show_bug.cgi?id=679489#c6
Dominique Leuenberger
participants (1)
-
bugzilla_noreply@novell.com