network manager icon does not correctly display status

Bug #1172062 reported by Tim Lunn on 2013-04-23
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
NetworkManager
Fix Released
Medium
network-manager (Ubuntu)
Undecided
Unassigned
systemd (Ubuntu)
Undecided
Unassigned

Bug Description

The network manager icon is not updating correctly to show the current network status. i.e. it is always showing as disconnected.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: gnome-shell 3.8.1-0ubuntu1~raring1.1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
Date: Wed Apr 24 08:43:34 2013
DisplayManager: gdm
MarkForUpload: True
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to raring on 2013-03-19 (35 days ago)

Tim Lunn (darkxst) wrote :
Tim Lunn (darkxst) wrote :

This looks like fallout from logind

** (process:6506): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/8: No session found for uid 1000 (No session found for uid 1000)

** (process:6506): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Settings/0: No session found for uid 1000 (No session found for uid 1000)

** (process:6506): WARNING **: handle_property_changed: failed to update property 'available-connections' of object type NMDeviceWifi.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
status: New → Confirmed
Tim Lunn (darkxst) on 2013-04-24
affects: gnome-shell (Ubuntu) → network-manager (Ubuntu)
affects: gnome-shell → network-manager
Tim Lunn (darkxst) wrote :

uploaded a fix to gnome3-staging ppa

Changed in network-manager:
importance: Unknown → Medium
status: Unknown → New
Changed in network-manager:
status: New → Fix Released
Martin Pitt (pitti) wrote :

What logind manager are you using? gdm, I presume? Do you have libpam-systemd installed? I'm afraid I need some reproduction steps how to get into a GNOME session without a logind session.

Changed in systemd (Ubuntu):
status: Confirmed → Incomplete
Martin Pitt (pitti) wrote :

Closing systemd task, leaving NM ubuntu task open for getting the upstream fix.

Changed in systemd (Ubuntu):
status: Incomplete → Invalid
Martin Pitt (pitti) wrote :

Imported upstream fix into Ubuntu packaging.

Changed in network-manager (Ubuntu):
status: Confirmed → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.9.8.0-0ubuntu9

---------------
network-manager (0.9.8.0-0ubuntu9) saucy; urgency=low

  * debian/tests/nm: Add hotplug ethernet test.
  * Add git_systemd_session_tracking.patch: Fix systemd session tracking
    detection in configure. (LP: #1172062)
  * debian/tests/nm: Verify device type.
  * debian/tests/nm: Don't assert that in IPv4 mode we don't have any IPv6
    configuration. This makes the tests work with current upstream git head.
  * debian/tests/nm: Enlarge DHCP/RA timeout from 8/10 to 15 seconds, this
    still times out too often otherwise.
  * debian/tests/nm: Allow the user to specify extra daemon arguments in
    $NM_TEST_DAEMON_ARGS. With that, one can run NM from upstream git head
    ("--debug --run-from-build-dir") or with extra verbosity
    ("--log-level=DEBUG"). Drop the latter by default, as it makes log files
    harder to read.
  * debian/tests/nm: Avoid comparing current privacy setting against
    NetworkManager.SettingIP6ConfigPrivacy.UNKNOWN, as that is not
    well-defined (and fails with current trunk).
  * debian/tests/nm: Introduce "auto_connect" option to start_nm() to disable
    automatic connections (to wired devices), and add a "manual IPv4" case to
    the Ethernet tests.
  * debian/tests/nm: Add tests for the two explicit IPv6 PE modes for (manual)
    ethernet connections.
  * debian/tests: Only stop/restart NM once, not once per test class.
  * debian/tests/nm: Exit with a meaningful message if not called as root.
  * debian/tests/network_test_base.py, start_dnsmasq(): Use a temporary lease
    file to avoid cluttering the system one.
  * debian/tests/network_test_base.py: Update file docstring.
  * debian/tests/dnsmasq: Some PEP8/pyflakes fixes.
  * debian/control: Drop obsolete network-manager-kde recommends (renamed to
    plasma-widget-networkmanagement which we alternatively recommend).
 -- Martin Pitt <email address hidden> Wed, 29 May 2013 09:58:16 +0200

Changed in network-manager (Ubuntu):
status: Fix Committed → Fix Released
CatchesAStar (catchesastar) wrote :

HI, is it possible for someone to get a backport of the fix into 13.04?

People from 13.04 are still having issues with this.

Todd Kennedy (toddkenn) wrote :

I'm on gnomeubuntu 13.10 and have this issue when I've used a vpn. The VPN Control never switchs to ON from the OFF state. The network icon does change to the VPN Icon with the lock but you can never get it to switch back once the vpn has been switch off.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.