Bug 159849 - Konqueror fails when started from Kickoff or the Panel
Summary: Konqueror fails when started from Kickoff or the Panel
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-25 20:48 UTC by Stuart Neill
Modified: 2008-06-20 03:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Neill 2008-03-25 20:48:44 UTC
Version:           Version 4.0.2 (KDE 4.0.2) "release 17.2" (using KDE 4.0.2)
Installed from:    SuSE RPMs

Konqueror fails when started from Kickoff or the Panel but not when started using the Open with dialogue. I created another user which had a working Konqueror for a while but it too crashed in the same way when logging into that account on the next occasion. I have been able to track the problem down to the saved profile I create for web browsing. That profile always has tabs with two specified, home folder and www.google.co.uk/. In addition I show the sidebar with "home" open.

I am able consistently to get a working Konqueror back again by deleting the files in ~/.kde4/share/apps/konqueror/profiles/
Comment 1 Stuart Neill 2008-03-26 11:54:49 UTC
I have looked a little further and it is the filemanager aspect that is failing. I notice that if I drag the Konqueror (Webbrowser) and Konqueror (Filemanager) icons on to the panel, looking at permissions, the first is owned by "myuser" with a group ownership of users while the later is owned and grouped by "root".
Comment 2 Florian Reinhard 2008-06-08 00:04:00 UTC
can't reproduce on svn trunk r817720 (~4.1 beta) please give feedback if you are still affected by that bug (i assume you updated to any recent kde release).
Comment 3 mario tuling 2008-06-20 03:35:06 UTC
with rev 822278 it works, the link has owner root:root but this is okay