Ubuntu
gnome-screensaver package

Gnome won't show screen saver unlock, clock-applet high cpu

Bug #738458 reported by Harald Rudell on 2011-03-19

10

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	gnome-screensaver (Ubuntu)	New	Low	Unassigned

Bug Description

Binary package hint: gnome-panel

On return to my computer, the screen saver unlock is not displayed
instead, the screen is black with only a mouse cursor that can be moved
ssh in to the machine and top shows:
PID USR PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1305 root 20 0 686m 312m 21m R 98 9.0 110:05 Xorg
2395 foxyboy 20 0 351m 10m 5768 S 60 0.3 21.33.10 clock-applet
...

kill the clock-applet process 2395, and the screen saver login appears
Gnome shows: "Clock" has quit unexpectedly

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13 04:29:19 PDT 2010
GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
Architecture: amd64
Date: Sat Mar 19 15:24:37 2011
DkmsStatus:
nvidia-current, 260.19.06, 2.6.32-26-generic, x86_64: built
nvidia-current, 260.19.06, 2.6.35-24-generic, x86_64: installed
nvidia-current, 260.19.06, 2.6.35-27-generic, x86_64: installed
nvidia-current, 260.19.06, 2.6.35-28-generic, x86_64: installed
nvidia-current, 260.19.06, 2.6.35-23-generic, x86_64: installed
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-28-generic root=UUID=6e418107-84af-4790-b047-0df1e3d0f0bf ro quiet splash
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
Xrandr:
Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension "RANDR" missing on display ":0.0".
RandR extension missing
dmi.bios.date: 05/25/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1208
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-EM DO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1208:bd05/25/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-EMDO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
distro: Ubuntu
codename: maverick
architecture: x86_64
kernel: 2.6.35-28-generic

Tags:

Revision history for this message

Harald Rudell (harald-rudell) wrote on 2011-03-19:

#1

.proc.driver.nvidia.cards.0.txt Edit (159 bytes, text/plain; charset="utf-8")
.proc.driver.nvidia.cards.1.txt Edit (159 bytes, text/plain; charset="utf-8")
.proc.driver.nvidia.registry.txt Edit (408 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (60.6 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (247.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.2 KiB, text/plain; charset="utf-8")
GdmLog.txt Edit (610.6 KiB, text/plain; charset="utf-8")
GdmLog1.txt Edit (37.4 KiB, text/plain; charset="utf-8")
GdmLog2.txt Edit (89.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (17.1 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (1.0 KiB, text/plain; charset="utf-8")
PciDisplay.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.2 KiB, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (246 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (120.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (260.2 KiB, text/plain; charset="utf-8")
XorgConf.txt Edit (2.1 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (790.7 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (53.0 KiB, text/plain; charset="utf-8")
glxinfo.txt Edit (22.2 KiB, text/plain; charset="utf-8")
nvidia-settings.txt Edit (55.7 KiB, text/plain; charset="utf-8")
peripherals.txt Edit (1.5 KiB, text/plain; charset="utf-8")
setxkbmap.txt Edit (333 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (15.3 KiB, text/plain; charset="utf-8")
xkbcomp.txt Edit (61.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Sebastien Bacher (seb128) wrote on 2011-03-21:

#2

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

affects:	gnome-panel (Ubuntu) → gnome-screensaver (Ubuntu)
Changed in gnome-screensaver (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-05-21:

#3

[Expired for gnome-screensaver (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-screensaver (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Harald Rudell (harald-rudell) wrote on 2011-09-02:

#4

This still happens. Different gnome-panel apps that do frequent redraw lock sup their thread and Xorg with high cpu: xclock eyes sensors-applet

Changed in gnome-screensaver (Ubuntu):
status:	Expired → New

Revision history for this message

Harald Rudell (harald-rudell) wrote on 2011-09-02:

#5

Every month or so it occurs (a system, that is never shut down) What I do is that I ssh in from another box and kill the high-load process. If I can't find out which one it is (happened once), I restart X.

I think it is related to that I have an nVidia Quadro NVS 450 with three displays and Ubuntu 11.04 effectively stopped supporting more than one display. X or GPU gets confused and draws in the wrong rectangle. A window might update on display 1 but is all black on display 2. This was all good on 10.10

Revision history for this message

Harald Rudell (harald-rudell) wrote on 2011-09-02:

#6

killall gnome-panel is also effective

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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