Bug 464746

Summary: K3b crashes after opening a .iso file
Product: [Applications] k3b Reporter: Jonathan Ryshpan <jonrysh>
Component: generalAssignee: 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
Application: k3b (22.12.1)

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.7-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
I opened a .iso file. K3B reported Transferring in a pop up window; there was a long period during which the progress meter in the popup window movded slowly, then the pop up reported "Transferrind (Failed) Application closed unecpectedly" and K3b crashed.

The system has been running extremely slowly before the crash, despite the fact that there doesn't seem to be a lot of CPU activity; my (very noisy) disk has been noisy lately. I have too many Firefox windows open, which seems to have something to do with slow system response.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: K3b (k3b), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fc393b75b8a in __memmove_avx_unaligned_erms () at /lib64/libc.so.6
#5  0x00007fc3942dbc26 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#6  0x00007fc395884e08 in KIO::TransferJob::data(KIO::Job*, QByteArray const&) () at /lib64/libKF5KIOCore.so.5
#7  0x00007fc3942dbc26 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#8  0x00007fc395866bf6 in KIO::SlaveInterface::data(QByteArray const&) () at /lib64/libKF5KIOCore.so.5
#9  0x00007fc39586ef8b in KIO::SlaveInterface::dispatch(int, QByteArray const&) () at /lib64/libKF5KIOCore.so.5
#10 0x00007fc395866aaa in KIO::SlaveInterface::dispatch() () at /lib64/libKF5KIOCore.so.5
#11 0x00007fc395869311 in KIO::Slave::gotInput() () at /lib64/libKF5KIOCore.so.5
#12 0x00007fc3942dbc26 in void doActivate<false>(QObject*, int, void**) () at /lib64/libQt5Core.so.5
#13 0x00007fc3942d2ec4 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#14 0x00007fc394faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#15 0x00007fc3942a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#16 0x00007fc3942ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#17 0x00007fc3942f9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#18 0x00007fc38f066cbf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#19 0x00007fc38f0bc598 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0
#20 0x00007fc38f063f40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#21 0x00007fc3942f938a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#22 0x00007fc3942a6cca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#23 0x00007fc3956a8195 in KJob::exec() () at /lib64/libKF5CoreAddons.so.5
#24 0x000055dbb4d2e8db in K3b::ProjectManager::openProject(QUrl const&) ()
#25 0x000055dbb4dd8b07 in K3b::MainWindow::openDocument(QUrl const&) [clone .isra.0] ()
#26 0x000055dbb4d0930e in K3b::Application::processCmdLineArgs() [clone .part.0] ()
#27 0x00007fc3942d2ec4 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#28 0x00007fc394faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#29 0x00007fc3942a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#30 0x00007fc3942ab5e4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#31 0x00007fc3942f9897 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#32 0x00007fc38f066cbf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#33 0x00007fc38f0bc598 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0
#34 0x00007fc38f063f40 in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#35 0x00007fc3942f938a in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#36 0x00007fc3942a6cca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#37 0x00007fc3942aed92 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#38 0x000055dbb4cda050 in main ()
[Inferior 1 (process 45573) detached]

Reported using DrKonqi
Comment 1 Albert Astals Cid 2023-01-24 21:54:26 UTC
Can you reproduce the crash?

Is the .iso that caused the crash something you can share?
Comment 2 Jonathan Ryshpan 2023-01-25 06:58:46 UTC
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.
Comment 3 Jonathan Ryshpan 2023-01-25 07:02:41 UTC
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".
Comment 4 Albert Astals Cid 2023-01-27 23:35:57 UTC
> 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
Comment 5 Albert Astals Cid 2023-01-27 23:41:05 UTC
Sadly that backtrace you have doesn't give much to go on :/