[Expired for Compiz because there has been no activity for 60 days.]
** Changed in: compiz
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
compiz
[Expired for compiz (Ubuntu) because there has been no activity for 60
days.]
** Changed in: compiz (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Unity is a python script, so it won't work, but it supports debugging:
--debug Run unity under gdb and print a backtrace on crash. /!\
Only if devs ask for it.
i.e. run unity --debug --replace before the crash (preferrable in a
console terminal (hit CTRL-ALT-F1 and
I can certainly generate crashes when I run env MALLOC_CHECK_=3 G_SLICE
=always-malloc unity --replace. What do I do after that? It's not giving
me anything new in /var/crash. I tried ubuntu-bug and ended up with
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1061467. When I try
ubuntu-bug
I ran into the same problem. I'm not sure why it then fails to report a
crash :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
compiz assert failure: *** glibc detected *** compiz:
What about running it in gdb?:
MALLOC_CHECK_=3 G_SLICE=always-malloc gdb --args replace
/usr/bin/unity
and then when it crashes, type backtrace and then paste here what
appears.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That certainly works but I was aiming for something more user-friendly
to ask regular people to do...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
compiz assert failure: *** glibc
michael@doulos:~/Desktop$ MALLOC_CHECK_=3 G_SLICE=always-malloc gdb --args
replace /usr/bin/unity
GNU gdb (GDB) 7.5-ubuntu
snip copyright info
Reading symbols from /usr/bin/replace...(no debugging symbols found)...done.
(gdb) backtrace
No stack.
(gdb)
--
You received this bug notification
See? Normal people don't understand gdb so we shouldn't normally ask
them to without detailed instructions :)
Try this:
ulimit -c unlimited
env MALLOC_CHECK_=3 G_SLICE=always-malloc gdb --args replace /usr/bin/unity
# Wait for the crash
gdb /usr/bin/compiz core
(gdb) bt
# Now copy the output
--
Sorry. You need to type run after gdb has started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
compiz assert failure: *** glibc detected *** compiz: free(): invalid
pointer:
It's a little difficult to run all those commands before it crashes, and
also difficult to run commands afterwards if the screen is frozen. I
tried putting them into a script. Would a script be a better solution
for normal people? Still no output, though.
--
You received this bug notification
** This bug is no longer a duplicate of bug 750386
compiz crashed with SIGABRT in raise() from abort() from __libc_message()
from malloc_printerr() from _int_free()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: compiz (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
** Also affects: compiz
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
compiz assert failure: *** glibc detected *** compiz: free():
Slightly frustrated there is no stacktrace, I get this every time
logging in.
Interestingly though, if I switch to a vt and start unity manually, all
is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A stack trace would not help in the free() because it's a delayed effect
from earlier heap corruption.
All - Please try this to produce a better crash report that will help us
find the root cause of the problem:
env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace
** Changed in:
** Tags added: compiz-0.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045965
Title:
compiz assert failure: *** glibc detected *** compiz: free(): invalid
pointer: 0x7f516ea0fe84 ***
To
*** This bug is a duplicate of bug 750386 ***
https://bugs.launchpad.net/bugs/750386
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #750386, so is being marked as such.
18 matches
Mail list logo
