[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-11-25 Thread Launchpad Bug Tracker
This bug was fixed in the package metacity - 1:2.25.8-0ubuntu1 --- metacity (1:2.25.8-0ubuntu1) jaunty; urgency=low * New upstream release - Ignore mouse button modifier if it's missing (Thomas) (LP: #258054, LP: #266929) - Merge screen and window keybindings files;

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-26 Thread Thomas Thurman
Is this actually a dupe of #258074? -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-25 Thread Christophe Dumez
I'm also experiencing the same problem with metacity in Intrepid release candidate. Any suggestion to fix this problem? -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-25 Thread Christophe Dumez
I installed debugging symbols and ran metacity in gdb. Here is the backtrace (message about ui.c looks strange, did I do something wrong?): (gdb) run Starting program: /usr/bin/metacity [Thread debugging using libthread_db enabled] [New Thread 0xb73509d0 (LWP 12524)] Program received signal

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-25 Thread Christophe Dumez
X and gnome are running but I have no window manager. Here is the message in dmesg: [ 622.813587] metacity[7580]: segfault at 0 ip 080abab3 sp bf9c8ff0 error 4 in metacity[8048000+7a000] Rename .gnome and .gnome2 folders does not solve anything. -- metacity crashed with SIGSEGV in

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-25 Thread Christophe Dumez
Here is valgind output, I think it should be more useful. ** Attachment added: valgind output http://launchpadlibrarian.net/1141/valgrind.log -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-25 Thread Christophe Dumez
I attached apport report (with debug symbols) there: #258074 -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread Thomas Thurman
®om: sorry, I'm missing the relevance of your comment. -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread tdflanders
Hi there Thomas Thurman, I fear that it is actually very relevant. It all has to do with PAM and authentication problems. See bug Bug #284653. Cheers, Thomas -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread Thomas Thurman
I'm still bewildered. Someone reports a crash in Metacity. Someone else says he doesn't use Metacity (so what?). And now you point to a crash in consolekit. I can only see the relevance of the first one. Sorry if I'm being stupid. -- metacity crashed with SIGSEGV in __libc_start_main()

Re: [Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread tdflanders
:44:45 PM Subject: [Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main() I'm still bewildered. Someone reports a crash in Metacity. Someone else says he doesn't use Metacity (so what?). And now you point to a crash in consolekit. I can only see the relevance of the first one

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread Thomas Thurman
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. --

Re: [Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread tdflanders
Thurman [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread Thomas Thurman
Please, please, please, tell me what this has to do with Metacity. I didn't see a mention of Metacity anywhere in your reply. -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu

Re: [Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread tdflanders
occured for instance by just '$ x-session-manager' after I head already called '$ sudo valgrind stuff, see wiki compiz. - Original Message From: Thomas Thurman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, October 18, 2008 6:29:48 PM Subject: [Bug 266929] Re: metacity crashed

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread Thomas Thurman
Metacity never does any authentication with anyone, never has, never will. I'm closing this bug; I think you may wish to raise another bug against the session manager, rather than a window manager. -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-18 Thread Thomas Thurman
(Okay, I won't close it, because the apport trace appears to contain a genuine Metacity crash. The comments here don't make much sense to me, though.) -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-16 Thread ®om
I don't use metacity, but compiz... -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-10-02 Thread Nxx
** Changed in: metacity (Ubuntu) Status: New = Confirmed -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-09-19 Thread Brian Murray
** Tags added: regression-retracer -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 266929] Re: metacity crashed with SIGSEGV in __libc_start_main()

2008-09-16 Thread Andreas Moog
** Attachment removed: CoreDump.gz http://launchpadlibrarian.net/17316986/CoreDump.gz ** Visibility changed to: Public -- metacity crashed with SIGSEGV in __libc_start_main() https://bugs.launchpad.net/bugs/266929 You received this bug notification because you are a member of Ubuntu Bugs,