(Fixed) Konqueror doesn't like Dolphin anymore

[Bald Brick]

When trying to start Konqueror as file manager I got this error message 20 minutes ago:

There was an error loading the module Dolphin View.
The diagnostics is:
Cannot load library /usr/lib/kde4/dolphinpart.so: (/usr/lib/libattica.so.0: undefined symbol: _ZN9QListData11detach_growEPii)

I immediately reinstalled kdebase4-dolphin and libattica0 (the packages that come with dolphinpart.so and libattica.so). That didn't help.

I then renamed ~/.kde4. That didn't work (if you don't count my losing all my mails and settings).

I then tried to find the text string "_ZN9QListData11detach_growEPii" in several different ways. I found it in ~/Documents/dolphinerror.txt. Nowhere else.

Dolphin still works normally; it's just the Dolphin module in Konqueror that refuses to load.


HELP!

I don't want to reconfigure everything for a new user and I want to use Konqueror as my file manager.

[Bald Brick]

I've also tried completely removing and reinstalling kdebase4-konqueror (and also reinstalling the two kio packages that were removed with it). It didn't help.

[old_guy]

blackbird
You are not alone. Updated today and I am getting the same error.

[Bald Brick]

It seems that JohnBoy's found a fix -- very fast -- http://www.pclinuxos.com/forum/index.php/topic,77665.msg640410.html#msg640410

[Ertain]

I can't open Dolphin, period.  Konqueror works, though.  But now I've gotten use to Dolphin it's hard for me to go back to Konqueror.

[gseaman]

I used JohnBoy's fix and it worked. However, the error returns after rebooting.

Galen

[wedgetail]

I am joining the que, I did not notice until now, when I saw the thread and thought that is funny I use it all the time and I did not notice. However I have my Konq set to use as root for a specific reason (and need it a fair bit). I have not noticed anything in that mode.

This must mean that even if I use Konqueror in root mode and then Open in normal I still have the problem.  I have also for some time had the crash on login, I am living with this for the time being, vaguely trying to figure something out in Ertains thread with similar problem (Sorry Ertain sort of using your thread as a collection topic)  I ham living with Theme Greet turned off, but it seems that is not a guarantee for bypassing the problem.

Can anybody give a date for the update when it happened and I going to look back in my Synaptic History and see what I have installed. Since that date.

[old_guy]

The "fix" doesn't work for me.
I went back in to synaptic and FORCED
libattica0
from        0.1.4-0.1pclos2010
back to    0.1.2-1pclos2010

It deleted several other things:
  attica-devel
  kdeaccessibility4-devel
  kdeedu4-cantor
  kdeedu4-devel
  kdeedu4-kalgebra
  kdelibs4-devel
which I can't reinstall without updating libattica0

So I'll stay with the older version of libattica0, and hope it gets cleared up.

Earl

PS
Also posted in Broken Packages

[wedgetail]

old_guy

Clarification please: 

Are you saying that your fix as outlined did not cure the problem and you have reported it as broken package

[old_guy]

wedgeling
My "fix" is working for me, except for the packages it removed. There already was a post in Broken Packages in which I added this info.

Earl

[Bald Brick]

I used JohnBoy's fix and it worked. However, the error returns after rebooting.

Galen

I noticed the same thing this morning.

So I opened the menu editor and found that a normal instance of Konqueror was started with "konqueror --profile filemanagement". The root version was marked to be started by a different user, but not only that: it was  started with "dbus-launch konqueror --profile filemanagement".

Consequently I prefixed the non-root command with "dbus-launch". Now everything seems to function as it should, but of course dbus-launch could possibly do some bad things too.

I haven't checked whether the "kfmclient openProfile webbrowsing" that starts Konqueror as a web browser might also need some editing in the menu.

[wedgetail]

blackbird

Are you not concerned if you do these fixes that you may forget to 'reset' them when an update comes out? What about just run in Su Konq until it is cleared.

I do love your digging and fixing though, don't let me put you off   

[Bald Brick]

blackbird

Are you not concerned if you do these fixes that you may forget to 'reset' them when an update comes out?

It's happened.

But at this moment in time Konqueror is broken -- or one of its dependencies is. The fix may also lead to unexpected results, but so far nothing has indicated that it will. So we have a choice between something that is proved to be broken and something that theoretically may turn out to be broken too.... How do you choose?

What about just run in Su Konq until it is cleared.

On the other hand, if you click to start Konqueror as root and then click ignore when asked for root's password you aren't suing to root. You aren't starting Konqueror as root. You are starting it precisely the same way as if you had used the command

Code: [Select]

dbus-launch konqueror --profile filemanagementin a terminal as a normal user.

[Texstar]

I would not spend too much time messing with this as kde 4.5.0 is going up this weekend.

[rogaven]

I would not spend too much time messing with this as kde 4.5.0 is going up this weekend.

+1