Summary: | Konqueror crashes on startup trying to create the search bar | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Robert R. Russell <robert> |
Component: | searchbarplugin | Assignee: | Arend van Beelen jr. <arendjr> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | adawit, browserbugs2, uncleanblessing |
Priority: | NOR | ||
Version: | 4.7.2 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
strace of a working konqueror showing www.google.com
strace of a not-working konqueror trying to show www.google.com backtrace of konqueror exploding after I restored the old .kde4 and .local dirs |
Description
Robert R. Russell
2011-10-23 19:20:16 UTC
This crash is happening in Qt during a QString assignment. Do you use any exotic optimization flags when compiling Qt ? grep CFLAGS /etc/make.conf returns CFLAGS="-march=native -O2 -pipe -ggdb" CXXFLAGS="$CFLAGS" Everything on the system was rebuilt with those flags to get that backtrace. g++ --version g++ (Gentoo 4.5.3-r1 p1.0, pie-0.4.5) 4.5.3 sys-libs/glibc-2.12.2 ld --version GNU ld (GNU Binutils) 2.21.1 > I do not know how to disable the search bar plugin.
Configuration/Configure extensions.../ Search bar checkbox
Gérard
No one else has reported this type crash before and I most definitely cannot reproduce this. The only things left for you to check is 1.) Create a new user and see if starting Konqueror crashes for that user too. 2.) If #1 happens, run "locate searchplugin.so" from the command line and see if there is more than one of that library installed on your system. There is no "searchplugin.so" on my system. kde-base/konq-plugins-4.7.4 which is the gentoo package responsible for konqueror's plugins owns /usr/lib64/kde4/searchbarplugin.so. Dawit, I know konqueror works if a delete .kde4 and .local, I had to do that to fix an ssl bug somewhere in the KDE-PIM suite. That amount of data loss is really bad though because I have bookmarks and passwords stored in the old .kde4 and .local folders dating from KDE 4.2 or 4.1. Which leads me to believe the problem is a file format change between 4.2 and late 4.6 or early 4.7, when Konqueror first started segfaulting on me. Created attachment 67618 [details]
strace of a working konqueror showing www.google.com
Created attachment 67619 [details]
strace of a not-working konqueror trying to show www.google.com
Created attachment 67620 [details]
backtrace of konqueror exploding after I restored the old .kde4 and .local dirs
I moved my old copies of the known bad .kde4 and .local directories to another user on my machine and the back trace looks very similar to the back trace posted when I filled this bug.
(In reply to comment #5) > There is no "searchplugin.so" on my system. > > kde-base/konq-plugins-4.7.4 which is the gentoo package responsible for > konqueror's plugins owns /usr/lib64/kde4/searchbarplugin.so. Actually that is what I meant... searchbarplugin.so. > Dawit, I know konqueror works if a delete .kde4 and .local, I had to do that to > fix an ssl bug somewhere in the KDE-PIM suite. That amount of data loss is > really bad though because I have bookmarks and passwords stored in the old > .kde4 and .local folders dating from KDE 4.2 or 4.1. Which leads me to believe > the problem is a file format change between 4.2 and late 4.6 or early 4.7, when > Konqueror first started segfaulting on me. I was not suggesting for you to delete your entire .kde4 directory. I was trying to determine whether or not that gets rid of the bug. That way we can tell whether or not this is crash was configuration related because it makes no sense. The crash is inside of QString. Anyhow, I suggest your first remove the [SearchBar] section from ~/.kde4/share/config/konquerorrc. You can copy that somewhere else first if you want to preserve it. In case that was the source of the crash. If that does not solve the issue, you can disable the searchbarplugin completely by adding the following line to your ~/.kde4/share/config/konquerorrc: [KParts Plugins] searchbarEnabled=false Make sure first close all instances of Konqueror before you attempt any of the suggestions I listed above. The bug causing konquerorrc on a different account. notch@neptune ~ $ cat ~/.kde4/share/config/konquerorrc [HTML Settings] DownloadManager= notch@neptune ~ $ the bug causing konquerorrc after inserting a statement to disable the search bar plugin and successfully starting and shutting down konqueror on my account. robert@neptune ~ $ cat ~/.kde4/share/config/konquerorrc [HTML Settings] AutomaticDetectionLanguage=1 DownloadManager= [KParts Plugin] searchbarEnabled=false [SearchBar] CompletionMode=5 CurrentEngine=google History list=\\0 Mode=1 SuggestionEnabled=true [Undo] Number of Closed Windows=1 robert@neptune ~ $ My conclusion is that one of the configuration parsers does not handle non-existent data very well. (In reply to comment #10) > The bug causing konquerorrc on a different account. > > notch@neptune ~ $ cat ~/.kde4/share/config/konquerorrc > [HTML Settings] > DownloadManager= > notch@neptune ~ $ > > the bug causing konquerorrc after inserting a statement to disable the search > bar plugin and successfully starting and shutting down konqueror on my account. > > robert@neptune ~ $ cat ~/.kde4/share/config/konquerorrc > [HTML Settings] > AutomaticDetectionLanguage=1 > DownloadManager= > > [KParts Plugin] > searchbarEnabled=false > > [SearchBar] > CompletionMode=5 > CurrentEngine=google > History list=\\0 > Mode=1 > SuggestionEnabled=true > > [Undo] > Number of Closed Windows=1 > robert@neptune ~ $ > > My conclusion is that one of the configuration parsers does not handle > non-existent data very well. That does not make sense because the same parser, KConfig, is used to read all KDE configurations. Moreover the backtrace shows the crash is caused by the code that reads the "CurrentEngine" entry, but I see no crash as a result of it and so far you are the only one to report such a crash. Additionally, you said that removing your .kde directory resolves the problem. To me all that points to something else being the actual culprit for this crash, but the crash occurring at this point. Anyhow, I am going to make one change to eliminate the one line code that reads the "CurrentEngine" entry from the equation. I doubt it solves the crash, but at least I would know that the issue is really somewhere else. The change might not make it into 4.8.0, but it should be in 4.8.1. Copying just the bad konquererrc file from my backup of the bad .kde4 directory into a known good .kde4 directory results in konqueror working correctly. Any other files that I need to check the contents of? Gentoo does not have QT-4.8.0 available to build from yet in the normal tree, would your patch work agains QT-4.7.4? I think I can add an extra patch to the Gentoo QT-4.7.4 ebuild locally on my system and rebuild, if you want to test it out? It may take a day or two for me to do it because school just restarted though. Git commit 32ea56a25e339b1dad81a1163a97439e7cf63d13 by Dawit Alemayehu. Committed on 12/01/2012 at 06:27. Pushed by adawit into branch 'KDE/4.8'. For clarity create the default search engine string outside the readEntry statement. M +3 -3 konq-plugins/searchbar/searchbar.cpp http://commits.kde.org/kde-baseapps/32ea56a25e339b1dad81a1163a97439e7cf63d13 Git commit e9815434a9ddcbe04d9551d67c22dae290b7e14c by Dawit Alemayehu. Committed on 12/01/2012 at 06:27. Pushed by adawit into branch 'master'. For clarity create the default search engine string outside the readEntry statement. (cherry picked from commit 32ea56a25e339b1dad81a1163a97439e7cf63d13) M +3 -3 konq-plugins/searchbar/searchbar.cpp http://commits.kde.org/kde-baseapps/e9815434a9ddcbe04d9551d67c22dae290b7e14c *** Bug 289900 has been marked as a duplicate of this bug. *** Can anyone confirm this crash still occurs in the latest version of KDE, v4.9 or higher ? I have never been able to reproduce it on my system. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! 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 in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |