Ubuntu
gnome-screensaver package

computer freezes when the molecules screensaver starts

Bug #190580 reported by joe on 2008-02-10

This bug report is a duplicate of: Bug #106060: [r128 1002:5446] Selecting the Molecule screensaver makes the PC freeze. It is completely unresponsive.. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	gnome-screensaver (Ubuntu)	Invalid	Low	Basilio Kublik

Bug Description

When we open the screensaver preferences menu, the computer also freezes and won't allow me to choose a different screensaver.

Each time the molecules screensaver starts the computer freezes

ProblemType: Bug
Architecture: i386
Date: Sat Feb 9 17:44:39 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: ath_hal
Package: yelp 2.20.0-0ubuntu3
PackageArchitecture: i386
ProcCmdline: yelp
ProcCwd: /home/joe
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: yelp
Uname: Linux joe-desktop 2.6.22-14-generic #1 SMP Fri Feb 1 04:59:50 UTC 2008 i686 GNU/Linux

Tags:

Revision history for this message

joe (chasejoe02) wrote on 2008-02-10:

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (38.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (655 bytes, text/plain; charset="utf-8")

Revision history for this message

Basilio Kublik (sourcercito) wrote on 2008-03-27:

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Hardy Heron. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at [WWW] http://www.ubuntu.com/testing/ .

Thanks again and we appreciate your help.

Changed in gnome-screensaver:
assignee:	nobody → sourcercito
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-04-22:

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.