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

2018-11-23 Thread Theo Linkspfeifer
** Changed in: xfburn (Ubuntu) Status: Confirmed => Fix Released -- 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

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

2014-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xfburn (Ubuntu) Status: New = Confirmed -- 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:

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

2014-04-17 Thread Mantas Kriaučiūnas
New XfBurn version (0.5.2) is released at 2014-04, see http://git.xfce.org/apps/xfburn/tree/NEWS xfburn 0.5.2 (2014-04-09) - Blu-Ray support - Large file support (iso9660 level 3) - Small bugfixes Many thanks to Thomas Schmitt who supplied numerous patches and much debugging help to make this

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

2014-03-26 Thread Thomas Schmitt
Hi, the crash should now be fixed in Xfburn's Git repository. In a test i was able to create an ISO image file while no burner drive was accessible. Packagers interested in a patch will have to combine http://git.xfce.org/apps/xfburn/commit/?id=75557169edbb5f499ed97b6bc8708f96f8469d4c and

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

2014-03-23 Thread 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

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

2014-03-23 Thread Thomas Schmitt
Hi, one reason for the drive being not recognizable would be if it was mounted by the operating system. Does it get visible to Xfburn if you start it after doing as superuser: umount /dev/sr0 Have a nice day :) Thomas -- You received this bug notification because you are a member of

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

2014-03-22 Thread Thomas Schmitt
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

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

2014-03-22 Thread Volkodav
Well I get brw-rw+ 1 root cdrom 11, 0 Mar 23 09:42 /dev/sr0 so the drive is there On 03/23/2014 01:31 AM, Thomas Schmitt wrote: ls -l /dev/sr* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.