Bug 1028948 - NetworkManager nm-applet does not show ethernet connection profiles
Summary: NetworkManager nm-applet does not show ethernet connection profiles
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lxde-common
Version: 19
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-11 10:10 UTC by Miroslav Betak
Modified: 2015-02-17 19:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:11:13 UTC
Type: Bug


Attachments (Terms of Use)

Description Miroslav Betak 2013-11-11 10:10:09 UTC
Description of problem:



I have installed Fedora 19 LXDE spin with current updates.
As non root user I have defined two ethernet connection profiles via nm-applet:
1., ens32 - ipv4 dhcp
2., direct - ipv4 manual

Test 1:

-computer switch on
-starting OS Fedora
-login as non root user
-left click on nm-applet and I see booth defined ethernet networks

Test 2:

- logout
- login as the same non root user
- left click on nm-applet and I see only "Auto ethernet"
( I miss booth my profile )

Test 3:

- logout
- login as the same non root user               
-left click on nm-applet and I see booth defined ethernet networks

Test 4:

- logout
- login as the same non root user
- left click on nm-applet and I see only "Auto ethernet"
( I miss booth my profile again )


and over and over           


wheen I run "nm-applet" as non root user from terminal in case of missing ethernet connection profiles I see:

** (nm-applet:21898): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/1: No session found for uid 1000 (unknown)

** (nm-applet:21898): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/0: No session found for uid 1000 (unknown)

** (nm-applet:21898): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceEthernet.

(nm-applet:21898): nm-applet-WARNING **: Failed to register as an agent: (32) Session not found

(nm-applet:21898): nm-applet-WARNING **: Failed to register as an agent: (32) Session not found




/var/log/messagess:


Nov  9 10:55:34 LXDE-VM systemd-logind[406]: Removed session 9.
Nov  9 10:55:38 LXDE-VM systemd[1]: lxdm.service holdoff time over, scheduling restart.
Nov  9 10:55:38 LXDE-VM systemd[1]: Stopping LXDM (Lightweight X11 Display Manager)...
Nov  9 10:55:38 LXDE-VM systemd[1]: Starting LXDM (Lightweight X11 Display Manager)...
Nov  9 10:55:38 LXDE-VM systemd[1]: Started LXDM (Lightweight X11 Display Manager).
Nov  9 10:55:45 LXDE-VM systemd-logind[406]: New session 19 of user betak.
Nov  9 10:55:45 LXDE-VM systemd-logind[406]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
Nov  9 10:55:46 LXDE-VM ck-launch-session: error connecting to ConsoleKit
Nov  9 10:55:46 LXDE-VM rtkit-daemon[418]: Successfully made thread 21464 of process 21464 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov  9 11:04:08 LXDE-VM NetworkManager[1369]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.178': no such name
Nov  9 11:04:08 LXDE-VM NetworkManager[1369]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.178': no such name
Nov  9 11:04:13 LXDE-VM ck-launch-session: error connecting to ConsoleKit
Nov  9 11:04:13 LXDE-VM rtkit-daemon[418]: Successfully made thread 21826 of process 21826 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Nov  9 11:04:13 LXDE-VM pulseaudio[21826]: [pulseaudio] pid.c: Daemon already running.






Version-Release number of selected component (if applicable):

Installed from Fedora-Live-LXDE-i686-19-1.iso

[root@LXDE-VM ~]# uname -a
Linux LXDE-VM.domain.sk 3.11.7-200.fc19.i686 #1 SMP Mon Nov 4 14:32:57 UTC 2013 i686 i686 i386 GNU/Linux

[root@LXDE-VM ~]# rpm -qa | grep NetworkManager
NetworkManager-0.9.8.8-1.fc19.i686
NetworkManager-glib-0.9.8.8-1.fc19.i686

How reproducible:

allways

Steps to Reproduce:
1. Install Fedora 19-1 LXDE spin
2. login as non root user and define two etherent connection profile via nm-applet
3. logout and login again as the same non root user - left click on nm-applet.
Yu will see only "Auto ethernet" connection profile

Actual results:

"Auto ethernet" connection profile 


Expected results:

booth user defined profiles

Additional info:

Comment 1 Dan Williams 2013-11-11 21:52:10 UTC
Please run:

loginctl
ck-list-sessions

and provide the output for these two commands, thanks!

Comment 2 Miroslav Betak 2013-11-11 22:39:48 UTC
Thanks for your prompt answer Dan


betak@LXDE-VM ~]$ loginctl
   SESSION        UID USER             SEAT
        19       1000 betak            seat0

1 sessions listed.
[betak@LXDE-VM ~]$
[betak@LXDE-VM ~]$ ck-list-sessions
[betak@LXDE-VM ~]$

Comment 3 Christoph Wickert 2013-11-12 10:47:43 UTC
@Dan: Who is to call ck-launch-session? LXDM or the startlxde script?

Comment 4 Miroslav Betak 2013-11-14 15:59:33 UTC

Fedora 20 beta-5 LXDE  has the same problem.

Comment 5 Fedora End Of Life 2015-01-09 20:33:20 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-02-17 19:11:13 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.