Bug 500691 - Discover freezes and then crashes after being open for about 2 seconds
Summary: Discover freezes and then crashes after being open for about 2 seconds
Status: RESOLVED UPSTREAM
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: 6.3.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-24 20:40 UTC by leverettdaniel
Modified: 2025-03-09 18:15 UTC (History)
4 users (show)

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

Attachments
Backtrace with debug symbols (48.42 KB, text/plain)
2025-02-24 20:40 UTC, leverettdaniel 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description leverettdaniel 2025-02-24 20:40:46 UTC 
Created attachment 178838 [details]
Backtrace with debug symbols

SUMMARY
Discover freezes and then crashes after being open for about 2 seconds

STEPS TO REPRODUCE
1. Open Discover (either as normal or from terminal using plasma-discover)
2. ???
3. Crash

OBSERVED RESULT
Freezes for about a second and then closes, triggers crash reporter

EXPECTED RESULT
Does not crash and works as usual

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20250223
KDE Plasma Version: 6.3.1
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.3-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 7600
Product Name: B550M Phantom Gaming 4
Comment 1 Nate Graham 2025-02-24 21:24:46 UTC 
Backtrace of the crashing thread:


Thread 1 (Thread 0x7faa5d350b00 (LWP 36594)):
[KCrash Handler]
#4  QtPrivate::lengthHelperPointer<char> (data=<optimized out>) at /usr/include/qt6/QtCore/qbytearrayview.h:77
#5  QtPrivate::lengthHelperPointer<char> (data=<optimized out>) at /usr/include/qt6/QtCore/qbytearrayview.h:69
#6  QByteArrayView::QByteArrayView<char*, true> (data=<optimized out>, this=<optimized out>) at /usr/include/qt6/QtCore/qbytearrayview.h:161
#7  pool_ready_async_cb (cpool=<optimized out>, result=<optimized out>, user_data=0x55f569bcd4e0) at ../qt/pool.cpp:74
#8  0x00007faa5e8c9d54 in g_task_return_now (task=0x55f569bd0ef0) at ../gio/gtask.c:1361
#9  0x00007faa5e8c9d89 in complete_in_idle_cb (task=0x55f569bd0ef0) at ../gio/gtask.c:1375
#10 0x00007faa6091278e in ??? () at /lib64/libglib-2.0.so.0
#11 0x00007faa60914f38 in ??? () at /lib64/libglib-2.0.so.0
#12 0x00007faa60916d28 in ??? () at /lib64/libglib-2.0.so.0
#13 0x00007faa6091753c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#14 0x00007faa62004ee3 in QEventDispatcherGlib::processEvents (this=0x55f5693a5140, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.8.2/src/corelib/kernel/qeventdispatcher_glib.cpp:399
#15 0x00007faa61db58db in QEventLoop::exec (this=this@entry=0x7ffd76a63220, flags=..., flags@entry=...) at /usr/src/debug/qtbase-everywhere-src-6.8.2/src/corelib/global/qflags.h:34
#16 0x00007faa61db759a in QCoreApplication::exec () at /usr/src/debug/qtbase-everywhere-src-6.8.2/src/corelib/global/qflags.h:74
#17 0x000055f52d1d0d00 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/discover-6.3.1/discover/main.cpp:224

This is quite weird-looking. What is it doing in GIO code? That's GNOME stuff.
Comment 2 Joshua Goins 2025-02-25 17:29:39 UTC 
(In reply to Nate Graham from comment #1)
> This is quite weird-looking. What is it doing in GIO code? That's GNOME
> stuff.

It looks like it's crashing in appstream, actually:

#7  pool_ready_async_cb (cpool=<optimized out>, result=<optimized out>, user_data=0x55f569bcd4e0) at ../qt/pool.cpp:74
Comment 3 Harald Sitter 2025-03-09 18:15:18 UTC 
https://github.com/ximion/appstream/pull/701