** Changed in: metacity
Status: Invalid => Expired
** Changed in: metacity
Importance: Unknown => Critical
--
Metacity crashes at startup
https://bugs.launchpad.net/bugs/84080
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
Closing the bug since no further information has been provided.
** Changed in: metacity (Ubuntu)
Status: Incomplete => Invalid
--
Metacity crashes at startup
https://bugs.launchpad.net/bugs/84080
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Any news about this? it's working fine on jaunty? could we close this
report?
--
Metacity crashes at startup
https://bugs.launchpad.net/bugs/84080
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bu
Upstream is wondering if you are still able to reproduce this with a
newest version of Metacity? could you try with Jaunty? Thanks in
advnace.
** Changed in: metacity (Ubuntu)
Status: Confirmed => Incomplete
--
Metacity crashes at startup
https://bugs.launchpad.net/bugs/84080
You received
** Changed in: metacity
Status: New => Invalid
--
Metacity crashes at startup
https://bugs.launchpad.net/bugs/84080
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Once more...
** Attachment added: "Crash"
http://librarian.launchpad.net/6714153/_usr_bin_metacity.1000.crash
--
Metacity crashes at startup
https://launchpad.net/bugs/84080
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
the way to use gdb on a CoreDump is "gdb $(which binary) CoreDump"
--
Metacity crashes at startup
https://launchpad.net/bugs/84080
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Oh, thanks. That's nifty.
So now I have a file called CoreDump, and file thinks it's a coredump
and gdb doesn't. Am I doing something wrong here?
[EMAIL PROTECTED]:/tmp/ap$ file CoreDump
CoreDump: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style,
from 'metacity'
[EMAIL PROTECT
"apport-unpack file.crash directory". On feisty apport sent different
files to the bug so it's easier, you can open or download only what you
want. You can also use "apport-retrace" to download the debug packages
for everything used by the app and regenerate a backtrace then (or just
update the bac
Procedural question: How do I get the core dump out of the .crash file?
I could write a program to do it, but I'm sure something else exists
already. I asked on IRC and googled around, but I couldn't find anything
out.
--
Metacity crashes at startup
https://launchpad.net/bugs/84080
--
desktop-b
** Changed in: metacity (upstream)
Status: Unknown => Unconfirmed
--
Metacity crashes at startup
https://launchpad.net/bugs/84080
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=406049
** Changed in: metacity (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs
Debug backtrace for the crash:
2019 else if (env->object_height >= 0 &&
(gdb) bt
#0 0x08082ab2 in pos_eval_helper (tokens=0x80ffca0, n_tokens=3,
env=0xbfe77be4, result=0xbfe77b54, err=0xbfe77dc0)
at theme.c:2019
#1 0x080832f3 in pos_eval (tokens=0x80ac1ce, n_tokens=13527295
** Attachment added: "Archive"
http://librarian.launchpad.net/6352649/_usr_bin_metacity.1000.crash
--
Metacity crashes at startup
https://launchpad.net/bugs/84080
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
14 matches
Mail list logo
