Bug 285966 - simulate consistently crashes while an actual write succeeds
Summary: simulate consistently crashes while an actual write succeeds
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 2.0.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-11-07 08:51 UTC by Radek Novacek
Modified: 2018-10-27 03:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Radek Novacek 2011-11-07 08:51:29 UTC
Version:           2.0.2
OS:                Linux

Disclaimer: This bug origins in bugzilla of Fedora Project, see https://bugzilla.redhat.com/show_bug.cgi?id=751595 

Description of problem:
For a given set of data, testing with a simulate always crashes yet doing an
actual burn works. When the crash occurs, it appears to unmount the DVD,
rendering it useless until I reboot (there's probably a way to remount w/o
restarting but I don't know how)

Version-Release number of selected component (if applicable):
Running v2.0.2 Linux (x86_64) on OS Linux (x86_64) release
2.6.35.14.100.fc14.x86_64


See attachments in downstream bugzilla


Reproducible: Always

Steps to Reproduce:
As described in Description. Once this bug is accepted, I will attach the debug
output from simulate and write


Actual Results:  
See description

Expected Results:  
I would expect the simulate to succeed given that the actual write succeeded

I am running under Gnome. This is the first time I have yum installed a KDE
package and am assuming it got all the necessary dependencies.

Once F16 comes out, I "hope" to be able to migrate and will test under it as I
am aware F14 is very near eol

Let me know if I can provide more info ... thanks, Paul
Comment 1 pnewell0705 2011-11-08 04:05:21 UTC
I see that my bug got transferred from Bugzilla of Fedora Project.

I'll remember to report directly here if I have future issues regarding KDE, sorry for not submitting this one via KDE

I am assuming that this is the active bug as opposed to the one I put in Fedora Project.

Thanks,
Paul
Comment 2 Radek Novacek 2011-11-08 07:35:16 UTC
Paul, thanks for reporting bug to Fedora Project bugzilla. It is useful to have it there for tracking purposes (to ensure that fix will make it to Fedora packages). But there is higher chance of fixing the bug in upstream bugzilla.
Comment 3 Albert Astals Cid 2014-09-29 22:56:37 UTC
So k3b crashes? Can you attach the backtrace (debug information) that drkonqi shows on the crash?

Can you also please run 
  valgrind k3b --nofork
try to make it crash and attach the valgrind output here?
Comment 4 pnewell0705 2014-10-03 21:58:45 UTC
This was back in 2011 on f14 which I have moved on from a long time ago. I am currently running Centos 6.5 which has k3b version 1.0.5 which is older than the 2.0.2 version with F14. Fedora closed the bug out awhile ago.

Until I move to Centos 7.0 or create a test machine with a Fedora that isn't EOL, I am unable to exercise the bug (let alone k3b)

FYI, it would be nice if Centos 6.5 had version 2.0.2 ... though it looks like no work has been done since then (per http://www.k3b.org/)?

Thanks,
Paul
Comment 5 Albert Astals Cid 2014-10-05 15:50:44 UTC
> FYI, it would be nice if Centos 6.5 had version 2.0.2 ... though it looks like no work has been done since then (per http://www.k3b.org/)?

That's something for the Centos people to solve.
Comment 6 Andrew Crouthamel 2018-09-25 03:50:07 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-27 03:33:24 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!