Application: konqueror (22.08.3) Qt Version: 5.15.7 Frameworks Version: 5.99.0 Operating System: Linux 6.0.8-arch1-1 x86_64 Windowing System: X11 Distribution: Arch Linux DrKonqi: 5.26.3 [KCrashBackend] -- Information about the crash: Whenever trying to start konqueror in any way at all, it immediately crashes. Konqueror has been uninstalled from the system for a few months and this user was created while konqueror was uninstalled and has no previously existing configuration or cache for Konqueror. Another user on the system that had previously used Konqueror has no problems and Konqueror starts normally for that person. The crash can be reproduced every time. -- Backtrace: Application: Konqueror (konqueror), signal: Segmentation fault Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>} [KCrash Handler] #6 0x00007f5049929e43 in KSycocaEntry::name (this=<optimized out>) at /usr/src/debug/kservice-5.99.0/src/sycoca/ksycocaentry.cpp:93 #7 0x00007f504a65a5df in tryLoadingService (service=...) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqfactory.cpp:71 #8 0x00007f504a6a0369 in KonqFactory::createView(QString const&, QString const&, QExplicitlySharedDataPointer<KService>*, QList<QExplicitlySharedDataPointer<KService> >*, QList<QExplicitlySharedDataPointer<KService> >*, bool) [clone .constprop.0] (serviceType=..., serviceName=..., serviceImpl=0x7ffcec89dd00, partServiceOffers=<optimized out>, appServiceOffers=<optimized out>, forceAutoEmbed=<optimized out>, this=<optimized out>) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqfactory.cpp:129 #9 0x00007f504a642b63 in KonqViewManager::createView (this=<optimized out>, serviceType=..., serviceName=..., service=..., partServiceOffers=..., appServiceOffers=..., forceAutoEmbed=true) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqviewmanager.cpp:805 #10 0x00007f504a6653f0 in KonqViewManager::createFirstView (serviceName=..., mimeType=..., this=0x564e6c9cea30) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqviewmanager.cpp:64 #11 KonqMainWindow::openView (this=0x564e6c645ea0, mimeType=..., _url=..., childView=0x0, req=...) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqmainwindow.cpp:829 #12 0x00007f504a6953b2 in UrlLoader::embed (this=0x564e6cd503d0) at /usr/src/debug/konqueror/konqueror-22.08.3/src/urlloader.cpp:426 #13 UrlLoader::performAction (this=0x564e6cd503d0) at /usr/src/debug/konqueror/konqueror-22.08.3/src/urlloader.cpp:284 #14 0x00007f504a66058a in UrlLoader::goOn (this=0x564e6cd503d0) at /usr/src/debug/konqueror/konqueror-22.08.3/src/urlloader.cpp:156 #15 UrlLoader::goOn (this=0x564e6cd503d0) at /usr/src/debug/konqueror/konqueror-22.08.3/src/urlloader.cpp:149 #16 KonqMainWindow::openUrl (this=<optimized out>, _view=<optimized out>, _url=..., _mimeType=..., _req=..., trustedSource=<optimized out>) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqmainwindow.cpp:609 #17 0x00007f504a688516 in KonqMainWindowFactory::createNewWindow (url=..., req=...) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqmainwindowfactory.cpp:70 #18 0x00007f504a69c1aa in handleCommandLine (parser=..., workingDirectory=..., ret=ret@entry=0x7ffcec89e268) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqmain.cpp:98 #19 0x00007f504a69e718 in kdemain (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/konqueror/konqueror-22.08.3/src/konqmain.cpp:269 #20 0x00007f504a42a290 in __libc_start_call_main (main=main@entry=0x564e6c504020 <main(int, char**)>, argc=argc@entry=1, argv=argv@entry=0x7ffcec89e418) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x00007f504a42a34a in __libc_start_main_impl (main=0x564e6c504020 <main(int, char**)>, argc=1, argv=0x7ffcec89e418, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcec89e408) at ../csu/libc-start.c:381 #22 0x0000564e6c504055 in _start () at ../sysdeps/x86_64/start.S:115 [Inferior 1 (process 8071) detached] Reported using DrKonqi
Unfortunately, I can't reproduce your issue. I tried creating a new user and starting Konqueror and on my system it works correctly. From the backtrace you provided, it seems that Konqueror tries to create a view, but it fails loading the library which should provide it. However, it looks like that (unless your distribution applied some patch which changes the line numbers from the released version) the crash comes not from the failure itself, but from attempting to displaying a message box informing you of this failure. I can't understand how this could happen, however. I think that, regardless of the exact cause, this crash will be fixed in the 22.12 release because the code which seems to be causing it has been changed significantly. Does the user experiencing the crash have any KDE related configuration files, even if not for Konqueror itself? The code which seems to be failing relies on the KDE infrastructure, so maybe the issue is caused by some non Konqueror-specific configuration file.
(In reply to Stefano Crocco from comment #1) > > Does the user experiencing the crash have any KDE related configuration > files, even if not for Konqueror itself? The code which seems to be failing > relies on the KDE infrastructure, so maybe the issue is caused by some non > Konqueror-specific configuration file. Ahh, this is one of those frustrating "phantom" errors that only occur with a very small set of "special" users. The user normally runs KDE as their standard desktop. It is possible that there were some old config files with cruft that the user copied in for some parts of KDE. They did this with much of the Akonadi stuff and they were having problems with Akregator putting articles into the wrong feed folders until they refreshed their Akregator config and removed their old Akregator database. It looks increasingly like the proper solution is to have the user save the data they want, then create a fresh user account and have the user manually configure things on the new account instead of just copying in old config files for KDE.
I've confirmed that clearing the old KDE profile eliminated the Konqueror crash on my user's profile. Closing the bug as "intentional" and leaving this here just in case someone in the future has an issue.