A verbose description can be found on the provided URL. Reproducible: Always Steps to Reproduce: 1. Start xfburn 2. select iso file 3. insert blank disc 4. start burn process 5. wait for the crash at the end of burning Actual Results: Xfburn finished the burning process. The burned disc is seems ok, but xfburn simply crashes after it has done its work. Expected Results: xfburn finishes without a segfault There was a patch by the Ubuntu folks. It is mentioned in the BUG-report (the provided URL). Also there are two other annoying bugs, for which patches have been made.
Created attachment 217875 [details, diff] was the patch: 01_fix-infinite-dialog-spawn.patch This patch should fix the problem xfburn is asking unlimited times to erase a disk.
Created attachment 217876 [details, diff] was the patch: 02_keep-the-devlist-around.patch This patch should fix the problem, which i experienced and which is detailed at the bug-report, which i posted the URL for.
Created attachment 217877 [details, diff] was the patch: 03_uint-screwed-up-the-1-return.patch This patch should fix the issue, that xfburn is crashing when hal is not running.
Created attachment 217879 [details, diff] modified ebuild I modified the file xfburn-0.4.2.ebuild with this patch. The patches apply cleanly and it compiles fine. At least for me it fixes the segfaults xfburn had before.
I can confirm I get the infinite dialogs for erasing discs and the random segfaults after a successful burning. I'm running ~amd64 no-multilib. The relevant attached patches fix the infinite dialogs and segfaults for me too.
Please report any crashes upstream at http://bugs.xfce.org . I'm not aware of any crashes, at least with master. If anyone can provide me a backtrace that would be useful. I'm going to release any day now, and if there are known crashes I'd like to fix them before that...
So, I assume this was reported to http://bugs.xfce.org/ as per Comment #6 as requested by upstream? And is now fixed in 0.4.3 release, added to portage half an hour ago?
Since I never got a backtrace, I can only say that the patches attached to this bug report are included in the 0.4.3 release.
(In reply to comment #8) > Since I never got a backtrace, I can only say that the patches attached to this > bug report are included in the 0.4.3 release. > Thanks. Good enough for me based on the provided information, closing (Reopen if it doesn't work)
Hi David, Samuli, Sorry, I simply didn't have time to get a backtrace done and haven't seen the problems since applying the patches. I did notice in the 0.4.3 changelog some fixes that sounded related, so I'll see how that release goes and I'll report upstream any problems. Thanks and regards, Josh