Summary: | Crash related to the burning process [K3b::MetaItemModel::parent, QModelIndex::parent] | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | kai-schuermann |
Component: | general | Assignee: | k3b developers <k3b> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, cigydd, cparg, mario.zimpel, rogerfang1, saneedham, trueg, youknowoliver |
Priority: | NOR | ||
Version: | 1.91.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
kai-schuermann
2010-05-14 08:06:41 UTC
Can't reproduce the error. / Ich kann den Fehler nicht reproduzieren. *** Bug 240451 has been marked as a duplicate of this bug. *** I'm reopenning this, looks like we've got another crash. rogerfang1@yahoo.com: are you able to reproduce this crash? If so, could you write the steps to do that? I submitted a couple of bug crashes this day - assuming the translation referred to selecting from the list to burn, I am providing more info (from memory) on my crash when trying to burn a disc from songs ripped from 2 discs: Ubuntu 10.04 LTS 64-bit Desktop I loaded source disk 1, dragged and dropped all songs to my project in the lower pane and ripped. I loaded source disk 2 and dragged and dropped all songs to my project in the lower pane, then ripped. The songs were showing up in my project as "CD tracks" instead of "Egg-vobs", and when I tried to burn to disc, nothing happened except clock time counter incrementing. Nothing showed up on the progress bar after waiting for hours. I re-tried burning a few times with the same result. I then re-tried by deleting all songs from the project, re-dragging all songs already ripped from disc 1, reinserting disc 2, dragging and dropping all songs and ripping again. I think this is the sequence that caused the crash. I was able to successfully burn by ripping each disc and making sure they were "Egg-vob" type instead of "CD track" type, then dragging and dropping in my project, then burning. I think trying to drag and drop to my project before ripping caused them to show up as "CD-track" and is why it wouldn't burn. *** Bug 241068 has been marked as a duplicate of this bug. *** *** Bug 244486 has been marked as a duplicate of this bug. *** *** Bug 244495 has been marked as a duplicate of this bug. *** Created attachment 52725 [details]
New crash information added by DrKonqi
k3b nach "apt-get update && apt-get dist-upgrade" mit "konsole"(im root-Modus), in anderer virtueller Arbeitsfläche abgestürzt...
[Comment from a bug triager] I would like to add that the original backtrace was related to a viewport change on the TreeView that triggered and update, while in the latest duplicates (and bug 254570 and bug 257292) the crash was caused because some file changed externally, KIO detected that change and the TreeView data was updated. I can't really say if both crashes have the same root cause, but they sure crash in the same first line (K3b::MetaItemModel::parent) In any case I would suggest to rename this bug report so it has a better title in english. Regards [Comment from a bug triager] Also note that "K3b::JobProgressDialog::startJob" appears on some backtraces so it could be related to some error caused by nested event loops. *** Bug 259462 has been marked as a duplicate of this bug. *** *** Bug 283001 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! 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 mark the bug 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! 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! |