SUMMARY Not sure if it's a slower laptop thing, but when I click the Installed tab on Discover, it says "Still looking" and stops responding. Sometimes it fixes itself and displays my Installed, but most of the time it's perminately stuck on it with the window not responding. STEPS TO REPRODUCE 1. Open Discover 2. Click Installed OBSERVED RESULT Stuck on not responding. EXPECTED RESULT To show my Installed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I'm on a dual core CPU with 4GB RAM.
Let's see what it's doing while frozen. Please do this: 0. Quit Discover if it's running 1. Run `gdb $(which pidof plasma-discover)` in a terminal window 2. Type "run" and then press the enter key 3. Navigate to the Installed page such that it hangs 4. In the terminal window, press Ctrl+C 5. In the terminal window, type "bt" and press the enter key 6. If it says "--Type <RET> for more, q to quit, c to continue without paging--" at the bottom of the terminal window, press the return key. Do this until there's nothing more. 7. Paste the terminal output into a comment here. Thanks!
Urgh, I made a mistake with the instructions, sorry. Step 1 should be: > Run `gdb $(which plasma-discover)` in a terminal window
The discover window shows up on the panel, but the window itself is no where to be seen. Even when I try to move it where I want it's like an invisible window. (Not even the title bar can be seen). I'm also still new to Linux in general so hopefully this is what you asked for. #0 0x00007fffd02aadec in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #1 0x00007fffd02ab3a0 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #2 0x00007fffd02aeca6 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #3 0x00007fffd02b2f45 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #4 0x00007ffff5ce7b30 in QObject::event (this=0x55555591e310, e=0x555557a7c170) at kernel/qobject.cpp:1347 #5 0x00007ffff776bf32 in QApplicationPrivate::notify_helper ( this=<optimized out>, receiver=0x55555591e310, e=0x555557a7c170) at kernel/qapplication.cpp:3637 #6 0x00007ffff5cbae38 in QCoreApplication::notifyInternal2 ( receiver=0x55555591e310, event=0x555557a7c170) at kernel/qcoreapplication.cpp:1064 #7 0x00007ffff5cbdeb1 in QCoreApplicationPrivate::sendPostedEvents ( receiver=0x0, event_type=0, data=0x5555555ec4a0) at kernel/qcoreapplication.cpp:1821 #8 0x00007ffff5d15427 in postEventSourceDispatch (s=0x555555623a60) at kernel/qeventdispatcher_glib.cpp:277 #9 0x00007ffff4672569 in g_main_dispatch (context=0x555555607c60) at ../../../glib/gmain.c:3444 #10 g_main_context_dispatch (context=0x555555607c60) at ../../../glib/gmain.c:4162 #11 0x00007ffff46c73c8 in g_main_context_iterate.constprop.0 ( context=0x555555607c60, block=<optimized out>, dispatch=1, self=<optimized out>) at ../../../glib/gmain.c:4238 #12 0x00007ffff466fd20 in g_main_context_iteration ( context=0x555555607c60, may_block=1) at ../../../glib/gmain.c:4303 #13 0x00007ffff5d14aea in QEventDispatcherGlib::processEvents ( this=0x5555555c48e0, flags=...) --Type <RET> for more, q to quit, c to continue without paging-- at kernel/qeventdispatcher_glib.cpp:423 #14 0x00007ffff5cb97cb in QEventLoop::exec ( this=this@entry=0x7fffffffda60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #15 0x00007ffff5cc1c2a in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #16 0x000055555556dc0f in ?? () #17 0x00007ffff5223510 in __libc_start_call_main ( main=main@entry=0x55555556d320, argc=argc@entry=1, argv=argv@entry=0x7fffffffdd58) at ../sysdeps/nptl/libc_start_call_main.h:58 #18 0x00007ffff52235c9 in __libc_start_main_impl (main=0x55555556d320, argc=1, argv=0x7fffffffdd58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdd48) at ../csu/libc-start.c:381 #19 0x000055555556e5e5 in ?? ()
It is helpful, thanks!
This is very weird, do you think you could install discover's debug symbols? It needs installing "plasma-discover-dbgsym" and then following the steps Nate provide earlier. Also if you wait really long, does it work eventually?
Sorry for the late response, I'm still learning how Linux and their distros work, how do I install discover's debug symbols? And the tab does load after a while, it just takes around a minute.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Ubuntu-based_distros_(Ubuntu,_Kubuntu,_KDE_Neon,_Linux_Mint)
I think I already have info because I'm on Kubuntu 22.10.
Oh good. Then all you need is to use `coredumpctl gdb` to get a backtrace, and the debug symbols will be downloaded automatically. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl.
Things came up and I don't think I'm going to have the time to continue on this. Sorry for any inconvenience.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
*** This bug has been marked as a duplicate of bug 467888 ***