nm-applet not visible/present after upgrade to yakkety

Bug #1615833 reported by Jonas G. Drange
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
New
High
Unassigned

Bug Description

System:
Ubuntu Yakkety on an intel machine

Reproduce:
Reboot

What happens:
nm-applet does not start

What should happen:
nm-applet should automatically start

It can be started by running alt+f2 nm-applet.

Log: http://pastebin.ubuntu.com/23117241/

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. What desktop environment do you use? Do you have any error in syslog about it? it has an autostart .desktop and gnome-session should start it on login, nothing changed in that regard...

Changed in network-manager-applet (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

This was either a fluke, or it was fixed. I can't reproduce it.

Changed in network-manager-applet (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

Nah, it re-appeared. This is the log: http://pastebin.ubuntu.com/23117241/ where Aug 30 18:48:20 is startup, and Aug 31 10:21:37 waking up from sleep. It disappeared after waking up from sleep.

Changed in network-manager-applet (Ubuntu):
status: Invalid → New
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

is the process still active when you get the issue? it would be useful to get a backtrace of those warnings with the dbgsym installed, you can attach to a working instance to get it

$ gdb -p <pid>
(gdb) b g_log
(gdb) c

it might stop on debug prints in which case you can keep doing "c" but should also get the warning and then you can get the bt

Revision history for this message
Jonas G. Drange (jonas-drange) wrote :

There's no nm-applet process, no.

Revision history for this message
Sebastien Bacher (seb128) wrote :

k, even better, attach gdb to it while it's there and then keep it until the indicator goes missing and see if it segfault or what

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

Other bug subscribers

Remote bug watches

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