Bug 458721

Summary: Skanpage crash on exit
Product: [Applications] Skanpage Reporter: Paul Anderson <ando.paul.j>
Component: generalAssignee: Alexander Stippich <a.stippich>
Status: RESOLVED FIXED    
Severity: crash CC: johnmaverick74
Priority: NOR Keywords: drkonqi
Version First Reported In: 1.0.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Paul Anderson 2022-09-05 01:36:12 UTC
Application: skanpage (1.0.0)

Qt Version: 5.15.2
Frameworks Version: 5.96.0
Operating System: Linux 5.19.6-100.fc35.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 35 (Thirty Five)"
DrKonqi: 5.25.4 [KCrashBackend]

-- Information about the crash:
Tried to scan a page with scan2pdf and it hung while saving the page.  Used Skanpage and it successfully scaned the page.  When exiting Skanpage the crash message came up.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Skanpage (skanpage), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f96694d1726 in QObjectPrivate::maybeSignalConnected(unsigned int) const () from /lib64/libQt5Core.so.5
#5  0x00007f96694da336 in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#6  0x000056548e4c49aa in DocumentSaver::save(QUrl const&, QList<SkanpageUtils::PageProperties> const&) ()
#7  0x000056548e4c1307 in non-virtual thunk to QtConcurrent::RunFunctionTask<void>::run() ()
#8  0x00007f96692ec650 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5
#9  0x00007f96692e9546 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#10 0x00007f9668a9f822 in start_thread () from /lib64/libc.so.6
#11 0x00007f9668a3f450 in clone3 () from /lib64/libc.so.6

Thread 3 (Thread 0x7f963bebe640 (LWP 27381) "skanpag:disk$0"):
#1  0x00007f9668a9ebc0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6
#2  0x00007f96423d128b in util_queue_thread_func () from /usr/lib64/dri/crocus_dri.so
#3  0x00007f96423d0edb in impl_thrd_routine () from /usr/lib64/dri/crocus_dri.so
#4  0x00007f9668a9f822 in start_thread () from /lib64/libc.so.6
#5  0x00007f9668a3f450 in clone3 () from /lib64/libc.so.6

Thread 2 (Thread 0x7f965d387640 (LWP 27372) "QDBusConnection"):
#1  0x00007f966817d29c in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#2  0x00007f96681258a3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007f96694f7ffe in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#4  0x00007f96694a55f2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#5  0x00007f96692e834a in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x00007f966ab84b7b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5
#7  0x00007f96692e9546 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#8  0x00007f9668a9f822 in start_thread () from /lib64/libc.so.6
#9  0x00007f9668a3f450 in clone3 () from /lib64/libc.so.6

Thread 1 (Thread 0x7f966560c940 (LWP 27369) "skanpage"):
#1  0x00007f9668a9ebc0 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6
#2  0x00007f96692ef09b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib64/libQt5Core.so.5
#3  0x00007f96692ebb3f in QThreadPoolPrivate::waitForDone(QDeadlineTimer const&) () from /lib64/libQt5Core.so.5
#4  0x00007f96692ebf7f in QThreadPoolPrivate::waitForDone(int) () from /lib64/libQt5Core.so.5
#5  0x00007f96694a8feb in QCoreApplication::~QCoreApplication() () from /lib64/libQt5Core.so.5
#6  0x000056548e4b7599 in main ()
[Inferior 1 (process 27369) detached]

Reported using DrKonqi
Comment 1 John 2022-10-28 17:29:20 UTC
Happens to me too!
Comment 2 Alexander Stippich 2024-03-03 11:32:59 UTC
I this still an issue with the latest version?
Comment 3 John 2024-03-04 12:41:12 UTC
(In reply to Alexander Stippich from comment #2)
> I this still an issue with the latest version?

It's happening here in neon's Plasma 6 (but was not happening in the latest plasma 5). 
Probably related to some bug recently introduced...
Comment 4 Alexander Stippich 2024-06-23 17:53:40 UTC
There was a fix for a crash upon exit in 24.05. If possible, please check.
If the issue still persists, please open a new bug report.