Hi, https://bugs.launchpad.net/ubuntu/+source/xfburn/+bug/1295721/+attachment/4035991/+files/Stacktrace.txt > el = 0x8438bf0ae0f208b > profile_no = 32603
el differs much from all other addresses shown in the stack. profile_no cannot be originally obtained from libburn. I'd guess the crash reason is an uninitialized GSList *el; after g_object_get (G_OBJECT (xfburn_device_list_get_current_device (priv->devlist)), "profile-no", &profile_no, "supported-speeds", &el, NULL); > #0 fill_combo_speed (box=box@entry=0x7f5b0a8c5950, device=0x0) at > xfburn-device-box.c:470 The value of parameter device stems from xfburn_device_list_get_current_device (priv->devlist) two calls above: > #2 0x00007f5b0973ba3e in [...] at xfburn-device-box.c:297 So it has to be assumed that this happened in xfburn-device-box.c:436: g_object_get (G_OBJECT (NULL), "profile-no", &profile_no, "supported-speeds", &el, NULL); Regrettably http://www.gtk.org/api/2.6/gobject/gobject-The-Base-Object-Type.html#g-object-get does not specify what happens to &el and &profile in this case. The stack values indicate that they are random resp. uninitialized. ---------------------------------------------------------------------- The NULL obviously happens because there are no drives detected. So why that ? What do you get from xorriso -devices as the user who executes Xfburn, and as superuser ? What do you get from ls -l /dev/sr* Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295721 Title: xfburn crashed with SIGSEGV in fill_combo_speed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfburn/+bug/1295721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs