| 2007-12-15 09:50:34 |
Sense Egbert Hofstede |
description |
Binary package hint: gnome-panel
When I was changing the looks of my account I noticed that gnome-appearance-properties wouldn't start. When I inserted the command in the terminal it told me about a segfault. I tried to solve it with restarting the X server, but after I logged in on my account I got an empty desktop. I switched to tty1 and logged in with the root account and found out the segfaults in messages which are attached to this bug report(although those are just 10 minutes old). I killed the gdm processes and executed 'M_ALLOC=0 startx'. Now I had was logged in into gnome with root. It worked fine. But the same command by my own account still caused segfaults. I tried startx without M_ALLOC=0 at root and it still worked.
Can the username be the cause? My username is 'sense'
I files this bug against gnome-panel because that gave the most segfaults. update-manager gave just one, do I have to file this against that too, or should I pick the kernel?
'uname -a': Linux nott 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
I'm running an up-to-date Gutsy amd64. |
Binary package hint: gnome-panel
When I was changing the looks of my account I noticed that gnome-appearance-properties wouldn't start. When I inserted the command in the terminal it told me about a segfault. I tried to solve it with restarting the X server, but after I logged in on my account I got an empty desktop. I switched to tty1 and logged in with the root account and found out the segfaults in messages which are attached to this bug report(although those are just 10 minutes old). I killed the gdm processes and executed 'M_ALLOC=0 startx'. Now I had was logged in into gnome with root. It worked fine. But the same command by my own account still caused segfaults. I tried startx without M_ALLOC=0 at root and it still worked.
Can the username be the cause? My username is 'sense'
I thought the error could be in the hidden configuration files in my home directory, who are still from dapper, so I removed my account, changed the name of my home dir to sense-bak and created a new account. I could work on it for a while, I got it configured again and the files back to their place, but then it got segfaults again. Using nvidia or nv as display driver didn't change that. I created a test account called test, which is a Desktop user(sense is an Administrator), and it still works, although it is just 15 mins old.
I files this bug against gnome-panel because that gave the most segfaults. update-manager gave just one, do I have to file this against that too, or should I pick the kernel?
'uname -a': Linux nott 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
I'm running an up-to-date Gutsy amd64.
|
|
