Summary: | Konqueror crashes on start up | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | vbhunt |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | crash | CC: | stefano.crocco |
Priority: | NOR | Keywords: | drkonqi |
Version: | 22.08.3 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
vbhunt
2022-11-17 01:57:55 UTC
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. |