That is exactly the problem in fact. If you run dpkg-reconfigure debconf -p low and select text mode and priority low, followed by dpkg-reconfigure -ap low you will get configuration questions of the type: use: 1. unix authentication 2. consolekit 3. likewise 4. ... The choices should be seperated by a space: 1 2 3 If you select everything and then change your /home folder: sudo chmod -cR 777 /home* ; sudo -cR chown -cR 1000 /home/* you will get faulty ~/.dmrc and ~/.dbus settings. Many users will do that because they cannot remove installation files from their home folder through nautilus gui (to save space for instance). If you start: $ sudo nautilus you can change the permissions, but only one by one. I suspect that is the problem. Since your different authentication methods conflict, you experience a wide variety of crashes. To get a backtrace you should start valgrind 'previously crashed process' and then gdb 2>&1 | gdb-<previously_crashed_process>
and use gdb attach pid (check with pidof or ps -A). The problem is that most crashes are fatal, requiring reboot and which application will crash is unpredictable. I have not been able to backtrace this properly, I am currently searching the proper debug symbols: 'apt-cache search <packagename> | grep "dbg"'. Could you try this out on VirtualBox or VMWare or a dedicated testing machine, or better yet a server with many partitions? It could work, I promise.
----- Original Message ----
From: Thomas Thurman <email address hidden>
To: <email address hidden>
Sent: Saturday, October 18, 2008 5:30:16 PM
Subject: [Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()
Then this can't be a Metacity problem. Metacity doesn't use ConsoleKit
or DBus.
--
metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929
You received this bug notification because you are a direct subscriber
of the bug.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hi Thomas,
That is exactly the problem in fact. If you run dpkg-reconfigure debconf -p low and select text mode and priority low, followed by dpkg-reconfigure -ap low you will get configuration questions of the type: use: 1. unix authentication 2. consolekit 3. likewise 4. ... The choices should be seperated by a space: 1 2 3 If you select everything and then change your /home folder: sudo chmod -cR 777 /home* ; sudo -cR chown -cR 1000 /home/* you will get faulty ~/.dmrc and ~/.dbus settings. Many users will do that because they cannot remove installation files from their home folder through nautilus gui (to save space for instance). If you start: $ sudo nautilus you can change the permissions, but only one by one. I suspect that is the problem. Since your different authentication methods conflict, you experience a wide variety of crashes. To get a backtrace you should start valgrind 'previously crashed process' and then gdb 2>&1 | gdb-<previously _crashed_ process>
and use gdb attach pid (check with pidof or ps -A). The problem is that most crashes are fatal, requiring reboot and which application will crash is unpredictable. I have not been able to backtrace this properly, I am currently searching the proper debug symbols: 'apt-cache search <packagename> | grep "dbg"'. Could you try this out on VirtualBox or VMWare or a dedicated testing machine, or better yet a server with many partitions? It could work, I promise.
----- Original Message ----
From: Thomas Thurman <email address hidden>
To: <email address hidden>
Sent: Saturday, October 18, 2008 5:30:16 PM
Subject: [Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()
Then this can't be a Metacity problem. Metacity doesn't use ConsoleKit
or DBus.
-- /bugs.launchpad .net/bugs/ 266929
metacity crashed with SIGSEGV in __libc_start_main()
https:/
You received this bug notification because you are a direct subscriber
of the bug.
_______ _______ _______ _______ _______ _______ _______ _ mail.yahoo. com
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://