gnome-session gets stuck utilizing 100% cpu time of one core
Bug #811822 reported by
Michael Neuffer
This bug affects 7 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-session (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
gnome-session gets stuck utilizing 100% cpu time of one core
killing gnome-session manually will kill -9 (it doesn't react to a normal kill) leaves
an unusable session behind.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-session 3.1.3-0ubuntu3
ProcVersionSign
Uname: Linux 3.0.0-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sun Jul 17 11:02:13 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
PackageArchitec
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)
Revision history for this message
| Michael Neuffer (neuffer) wrote | #1 |
| Changed in gnome-session (Ubuntu): | |
| status: | New → Confirmed |
Revision history for this message
| Michael Neuffer (neuffer) wrote | #2 |
Revision history for this message
| Chad Miller (cmiller) wrote | #3 |
Revision history for this message
| Michael Neuffer (neuffer) wrote | #4 |
Revision history for this message
| dino99 (9d9) wrote | #5 |
| Changed in gnome-session (Ubuntu): | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
As additional data point:
Starting a rescue session will leave a terminal behind even after killing -9 gnome-session from the console.
From within the terminal gnome-session can then successfully be restartet.