Well thanks very much for looking. I actually have several of those files from about 4 different VM's. For whatever reason those files do not get generated for every occurrence of the issue. Since posting the full file earlier, I have been learning about how to use apport-retrace (and gdb) to extract the stack trace for myself, so maybe I can eventually come back with something useful. So far it isn't working though.
My system seems to have hung again while "installing extra package compiz-core to get Executable path", or similar the terminal window has actually disappeared now. However, I did get this just now and via a SSH session: ... Core was generated by `compiz'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f75e06e9c24 in __memmove_sse2 (dest=0x26a8d7e0, src=<optimized out>, len=973293064) at ../string/memmove.c:99 99 ../string/memmove.c: No such file or directory. (gdb) I'll also add an attachment in a minute, but I have to delete the cor dump becuase the file is over 50 megabytes.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282342 Title: compiz crashes with segfault after recent updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1282342/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
