Thanks, I did it. I'll see if I get again the crash screen. -----Original Message----- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Evan Dandrea Sent: vendredi 23 mars 2012 11:58 To: Vrignaud Etienne Subject: [Bug 960757] Re: whoopsie crashed with SIGSEGV in g_object_newv()
Can you please first upgrade whoopsie to 0.1.20 or later. Then please edit /etc/init/whoopsie.conf as root (sudo gedit /etc/init/whoopsie.conf) and just below the line that reads "env CRASH_DB_URL=https://daisy.ubuntu.com, put "env G_SLICE=always-malloc". So the file then looks like this: ... env CRASH_DB_URL=https://daisy.ubuntu.com env G_SLICE=always-malloc ... Then run `sudo restart whoopsie`, and report back here on whether that stops the crash in whoopsie from happening. The dialog that appears will say "Ubuntu has encountered an internal error", but if you hit Show Details, the Package will be whoopsie. To be clear, you may get crashes that say "Ubuntu has encountered an internal error", but we're only concerned about ones for the whoopsie package in this bug report. Thanks! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/960757 Title: whoopsie crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/960757/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/960757 Title: whoopsie crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/960757/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
