Network indicator stopped working, Unity crashed when restarting networking

Bug #1080923 reported by Ada Wah
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
indicator-session (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Sometimes, WiFi disconnects, and I have to disable and re-enable wireless to get in to connect. This happens on many systems, so it`s maybe related to the technology rather than Ubuntu. Only this time, both Enable networking and Enable wireless in the indocator menu were greyed out. When trying to run `sudo service networking restart`, Unity crashed. I could start Unity again from command line, but it started without window decorations. I tried to restart Compiz without luck.

Also, when Unity started up, the networking indicator were gone. After a reboot, everything went back to normal.

I cannot give any more information on how to reproduce, other than than one other user were logged in, and this happened after resuming from suspend. I will add a comment if it happens again, and under which circumstances.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: indicator-session 12.10.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Uname: Linux 3.5.0-18-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
Date: Tue Nov 20 01:05:37 2012
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-10-11 (39 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: indicator-session
UpgradeStatus: Upgraded to quantal on 2012-10-19 (31 days ago)

Revision history for this message
Ada Wah (ailurius) wrote :
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in indicator-session (Ubuntu):
status: New → Confirmed
Revision history for this message
Ada Wah (ailurius) wrote :

It happened again, under similar circumstances. Resumed from suspend, two users were logged in. Had to reboot to fix the problem.

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.