Xfburn crashes when trying to add files to data composition on Lubuntu 14.04

[Pierre]

Xfburn closes when trying to add files to data composition on Lubuntu 14.04. The Select file window open. After selecting files, clicking OK closes the entire program.

I did not test if it happens also in other modes, e.g. burning an iso, audio cd...

This is the default app for Lubuntu. Hope it gets fixed soon, especially that 14.04 is an LTS.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xfburn 0.5.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CurrentDesktop: LXDE
Date: Wed May 7 10:34:04 2014
InstallationDate: Installed on 2011-11-15 (903 days ago)
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: xfburn
UpgradeStatus: Upgraded to trusty on 2014-04-19 (17 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thomas Schmitt (scdbackup)]

Hi,

this bug is also discussed at the german Ubuntu forum
and brought to the attention of the upstream programmer
of xfburn. It appears as if it was depending on particular
installation environment.

We can believe that the author tested this use case before
release. I myself worked with it on non-standard xfce equipment
on Debian 6.
The german bug is with Lubuntu 14.04.
  http://forum.ubuntuusers.de/topic/brasero-3-10-0-schliesst-cd-dvd-nicht-ab/2/
(The thread began about Brasero. But since i do not know
 how to get the attention of Brasero maintainers, i
 proposed to hunt down the mentioned bug in xfburn.)

There is some problem indicated by valgrind on the machine
of the german user:
  ==3172== Invalid read of size 4
  ==3172== at 0x5217370: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4000.0)
  ...
  ==3172== by 0x4B8A7DD: gtk_object_destroy (in /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0.2400.23)
  ==3172== by 0x12BC9B: ??? (in /usr/bin/xfburn)
  ==3172== by 0x521E728: g_cclosure_marshal_VOID__VOIDv (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.4000.0)
  ==3172== by 0x521CCCD: ??? (in /usr/lib/i386-linux-gnu/libgobject-2.0.so.0.40
  ==3172== Address 0x150 is not stack'd, malloc'd or (recently) free'd

If Ubuntu could provide an xfburn package with debugging
information, then valgrind could probably tell more.

An apport crash file of a different run indicates a stack
trace without any xfburn function call in it.
So i (as bystanding libburn programmer) suspect that the
memory management gets damaged by the valgrind catch, and
that it stumbles ahead until it finally crashes.

It might still be some way to go after we learn about the
xfburn parameters in the valgrind report.
It is unclear whether xfburn or the desktop libraries are
to blame.

Very helpful would be a valgrind run of xfburn on some other
Ubuntu desktop, in order to see whether similar memory access
errors are detected. (Would help even without debugging-ready
xfburn.)
  https://wiki.ubuntu.com/Valgrind

Have a nice day :)

Thomas

[David Mohr (bugs-da)]

I'm discussing this here because the bug is likely ubuntu specific:

There's an add window (not dialog), after a button click the callback add_cb() runs which calls gtk_widget_destroy () on the add window (see attachment for callback).

This code was introduced in e18bcd65f8b02514c8f1ef8ec96b183a721fa727 in 2012, but because of my lazy release policy I have no clue when/if that was included in ubuntu before.

But in any case, since it works just fine on Debian 6 & sid I suspect some ubuntu patches to be responsible.

[Alexander (ramaryus)]

There're two nice workarounds for this issue (tested on my xubuntu 14.04):
1) If you double click on the file you want to add - application will not crash
2) If you use "file browser" - application will not crash

So, disregards there's real issue in xfburn, it is still quite usable.

Hope these helps,
Alex.