[Bug 1295721] Re: xfburn crashed with SIGSEGV in fill_combo_speed()

[Thomas Schmitt]

Hi,

> Well I get brw-rw----+ 1 root cdrom 11, 0 Mar 23 09:42 /dev/sr0 so the
> drive is there

So device file non-existence is not the cause.

But meanwhile i was able to produce a nice crash of xfburn after
  chmod a-rw /dev/sr0
and trying to compose an ISO image. At start-up Xfburn warns me
that there is no usable drive.

Valgrind complains about uninitialised values being used.
Among its output is
  Process terminating with default action of signal 11 (SIGSEGV)
  Access not within mapped region at address 0x1
    at 0x417E12: fill_combo_speed (xfburn-device-box.c:453)
which in my xfburn-0.5.1-git version is the same C statement as in
0.5.0's line 470:
    gint write_speed = GPOINTER_TO_INT (el->data);

--------- 
    
So the lack of a detected drive seems to be an intermediate cause,
indeed. I will inform the upstream developer now.

---------

Still we do not know why your drive does not get recognised by Xfburn.
The next two suspects would be udev and libburn.

udev should report drive properties by:

  udevadm info --export-db | grep ID_CDROM

libburn can best be exercised by a CLI program

  xorriso -devices

If no drive is found, then direct the SCSI transaction log to a file
/tmp/xorriso_log and post it here:

  xorriso -scsi_log on -report_about all -devices 2>&1 | \
    tee -i /tmp/xorriso_log


If this stays inconclusive, then we would have to start experiments
with the source code of xfburn.
(xfburn/xfburn-device-list.c:get_libburn_device_list around the call
 of burn_drive_scan.)


Have a nice day :)

Thomas

-- 
You received this bug notification because you are a member of Ubuntu
Burning Team, which is subscribed to xfburn in 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