Summary: | K3b crashes after opening a .iso file | ||
---|---|---|---|
Product: | [Applications] k3b | Reporter: | Jonathan Ryshpan <jonrysh> |
Component: | general | Assignee: | k3b developers <k3b> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | aacid, michalm, trueg |
Priority: | NOR | Keywords: | drkonqi |
Version: | 22.12.1 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jonathan Ryshpan
2023-01-24 16:35:08 UTC
Can you reproduce the crash? Is the .iso that caused the crash something you can share? The file is available at: https://drive.google.com/file/d/1TH8nKX8AZHRWaFejigLViqMwQ9nKp-Tw/view?usp=share_link It was created by running K3B->Copy Medium->Options->Only Create Image on a disk of x-rays of my ankles. (I don't need to have my x-rays kept private, but would rather not have them posted on the web.) The disk appears to be self-starting on Windows and can be read in Linux using the Weasis program. It no longer causes K3B to crash. My system is now running normally; it's no longer slow to start programs. I have no idea why the system is working better, possibly some background process is no longer running. However the image is very strange: Opening it from causes K3B to reject it with the popup message "Error -- Could not open document". Opening it using K3B->More Actions->Desktop/.../Ankle-DiskImage-1.iso produces the popup message Type of image file is not recognizable. Do you want to burn it anyway? The file command doesn't recognize it: $ file Ankle-DiskImage-1.iso Ankle-DiskImage-1.iso: data Nevertheless the Dolphin "Open with Disk Image Mounter" command appears to mount the image correctly, and it's possible to burn a copy by answering "Do you want to burn it anyway?" with Yes. The word "Dolphin" is missing from the following line in my last comment. However the image is very strange: Opening it from <Dolphin> causes K3B to reject it with the popup message "Error -- Could not open document". > Opening it from <Dolphin> causes K3B to reject it with the popup message "Error -- Could not open document".
That's a separate thing k3b only tries to open k3b projects, which an iso is not, that's why it fails
Sadly that backtrace you have doesn't give much to go on :/ |