Red Hat Bugzilla – Bug 436842
Gnome Controllpanel Background crashes
Last modified: 2013-03-05 22:55:10 EST
Description of problem:
Gnome Controllpanel Background crashes when opening it
Version-Release number of selected component (if applicable):
I just dumped Fedora 7 to install Fedora 8. I am running it on a shuttleX, a
quite small PC. Fedora 7 was running fine on it. Fedora 8, unfortunatly has a
problem with gnome. This PC does only have 192MB RAM (default for this machine,
Don't worry CPU is 2 GHZ, works fine for a movieplayer). When I start up gnome
it allready says that gnome power management is not set up right. I don't have
any backgroundpic at all. Also the nice Icons in the top menu are missing. Well
it still works. Only the background changer doesn't open. This controllpanel app
crashes at start.
I have done yum update, so that's not the case.
Steps to Reproduce:
1. Open Gnome Controllpanel Background
2. crashes at start, unfortunalty autobug report fails then
Should open the background changer
I can go back and install fedora 7 again, or I can make the world a better
place. I would like to go for the second. Please tell me how to continue. What
is needed? Dumps, screenshots, logs?
I found a workaround. Most important on this issue is that its a Shuttle XPC PC
with AMD CPU and VIA Chipset. It has originally 256 MB RAM. The Shared Memorie
for the graphic card takes 64 MB Away. Leaving somehow 192 MB RAM for the CPU.
This is not enough for the graphical installer of Fedora 8.
This is the workaround: I anstalled 1 GB RAM addional. I reinstalled Fedora 8
with the graphical installer. Controllpanel Background works now. Additionaly
the system runs much smother, because it doesn't have to swap anymore.
Conclusion: This bug can be closed for now, unless someone want to fix the low
ram issue. It would be whise to reconsider the install routine. The installer
could be more strict, for example: If the System doesn't have 256MB RAM at
least, then gnome isn't installed at all. Installing something that deosn't work
correctly doesn't make sense anyway. The installer is not the issue of this
support. I will make some tests with the new installation. In case there is
still something I will open a new report.