Brasero crashes on start

[Fran Diéguez]

By using UbuntuGNOME 13.10 and all the available gnome3-team ppas (gnome3, next and staging) brasero crashes at start right away.

Here is the dump

$ brasero -d

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion 'dest_width > 0' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_colorspace: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_data: assertion 'data != NULL' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion 'dest_width > 0' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_bits_per_sample: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_colorspace: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed

(brasero:28396): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_data: assertion 'data != NULL' failed
**
Gtk:ERROR:/build/buildd/gtk+3.0-3.9.14/./gtk/gtkrecentmanager.c:1960:get_icon_fallback: assertion failed: (retval != NULL)
Aborted (core dumped)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: brasero 3.8.0-1ubuntu2
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Mon Sep 16 23:52:21 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-08-25 (22 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130825)
MarkForUpload: True
SourcePackage: brasero
UpgradeStatus: No upgrade log present (probably fresh install)

[Tim Lunn (darkxst)]

It works fine here.

Those messages looks like its failing to find and/or load some icon.

Can you get a backtrace?

[Fran Diéguez (frandieguez)]

I'm using the default icon set from gnome.

Please find attached the complete backtrace

[Tim Lunn (darkxst)]

Fran, you will need to install debug symbols for atleast brasero, gtk and glib and then redo the backtrace!

[Fran Diéguez (frandieguez)]

I have installed libgtk-3-0-dbg and libglib2.0-0-dbg. I can't find the debug symbols for brasero (brasero***-dbg??).
Here is the new backtrace

[Tim Lunn (darkxst)]

For packages that don't have -dbg packages you need to setup ddeb's and install the -dbgsym packages.

See https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages

[Fran Diéguez (frandieguez)]

I have tested with a new user in the same machine and with another machine with the same installation, and brasero starts without problem.

So before continue trying to fix this bug I will take a look at my settings in ~/.config ~/.gnome* and ~/.local and I will try to figure out what is happening with my user settings.

Sorry for making you spend time in this silly issue.

[Fran Diéguez (frandieguez)]

Cleaning all the user settings now brasero starts and works like a charm. Sorry for the extra work.

I will mark this bug as invalid.

[Iván Stepaniuk (istepaniuk)]

Removing ~/.local/share/recently-used.xbel solved this exact problem for me. There was no need to delete additional configuration files.