Bug 487411 - QApt batch installer crash on Vivaldi launch
Summary: QApt batch installer crash on Vivaldi launch
Status: RESOLVED UPSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2024-05-23 06:13 UTC by edison23
Modified: 2024-05-23 20:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description edison23 2024-05-23 06:13:49 UTC
Application: qapt-batch (3.0.5)

Qt Version: 5.15.13
Frameworks Version: 5.115.0
Operating System: Linux 6.8.0-31-generic x86_64
Windowing System: X11
Distribution: Ubuntu 24.04 LTS
DrKonqi: 5.27.11 [KCrashBackend]

-- Information about the crash:
It seems QApt batch installer crashed during Vivaldi launch because I didn't provide elevated permission authentication credentials in time. I don't really know what QApt is and what it was trying to do that required elevated permission level. That's why I was hesitant to privide the credentials. It prevented Vivaldi to load fully, tho. Not repro on next vivaldi launch.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: QApt Batch Installer (qapt-batch), signal: Segmentation fault

[KCrash Handler]
#4  0x0000729c5aedbbcb in QMutex::lock() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x0000729c5b0da0cc in QCoreApplicationPrivate::lockThreadPostEventList(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x0000729c5b0db362 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x0000729c5c46408c in QApt::Transaction::onCallFinished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQApt.so.3
#8  0x0000729c5b112dbf in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x0000729c5ad96001 in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#10 0x0000729c5b106343 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x0000729c5bd6bd45 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x0000729c5b0d8118 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x0000729c5b0db94b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x0000729c5b135c0f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x0000729c595145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x0000729c59573717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x0000729c59513a53 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x0000729c5b135279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x0000729c5b0d6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x0000729c5bf8aebb in QDialog::exec() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x000061fc8e3d6770 in ?? ()
#22 0x0000729c5a62a1ca in __libc_start_call_main (main=main@entry=0x61fc8e3d5950, argc=argc@entry=4, argv=argv@entry=0x7ffdb3016f28) at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x0000729c5a62a28b in __libc_start_main_impl (main=0x61fc8e3d5950, argc=4, argv=0x7ffdb3016f28, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdb3016f18) at ../csu/libc-start.c:360
#24 0x000061fc8e3d7085 in _start ()
[Inferior 1 (process 4878) detached]

Reported using DrKonqi
This report was filed against 'kde' because the product 'qapt-batch' could not be located in Bugzilla. Add it to drkonqi's mappings file!
Comment 1 Nate Graham 2024-05-23 20:52:18 UTC
Neither of those pieces of software comes from KDE. This looks like a Qt bug, so I'd recommend bringing it up to the Qt folks, or else the developer of the crashing app.