GNOME Bugzilla – Bug 548985
crash in Brasero Disc Burning:
Last modified: 2008-08-23 06:48:34 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686-bigmem #1 SMP Fri Jul 18 18:30:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mac4Lin_Icons_v0.4 Memory status: size: 59973632 vsize: 59973632 resident: 25223168 share: 14303232 rss: 25223168 rss_rlim: 4294967295 CPU usage: start_time: 1219401906 rtime: 30 utime: 26 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/brasero' [Thread debugging using libthread_db enabled] [New Thread 0xb69dd940 (LWP 11610)] 0xb7fd6424 in __kernel_vsyscall ()
+ Trace 205529
Thread 1 (Thread 0xb69dd940 (LWP 11610))
----------- .xsession-errors (75 sec old) --------------------- (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (liferea:8992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed [00000360] access_http access: Raw-audio server found, mp3 demuxer selected --------------------------------------------------
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.
Thanks for the report and the stacktrace. I managed to fix your bug in SVN trunk. So the fix should be in 0.8.2. Feel free to reopen the bug if it still crashes.