my problem is that my dolphin file manager is not working. It is an very important application for me, I have installed pcmanfm as transitional solution.
I’m not sure why he does not work anymore. Probably it was an update which I had recorded and since then the file manager does not work anymore. If i start dolphin from konsole, the output is:
tux@iglu344:~> kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "stash"
Trying to convert empty KLocalizedString to QString.
Cannot creat accessible child interface for object: PlacesView(0x29309f0) index: 16
The mentioned “stash” support is not included in 42.3 yet… And there haven’t been any KDE related updates at all recently that could cause such a problem.
Also, I would suggest to try on a fresh user account.
The latest dolphin 17.12.1 works fine here on my 42.3 system with the latest KDE Frameworks5 and Qt5.
And the messages you posted do not indicate a problem, I get them too.
PS: why pcmanfm?
KDE alternatives would be Konqueror (which just embeds dolphin anyway, so trying it would be interesting in regard to your problem too) or krusader.
The mentioned “stash” support is not included in 42.3 yet… And there haven’t been any KDE related updates at all recently that could cause such a problem.
Also, I would suggest to try on a fresh user account.
You are right, had created a new user with his home-dir in /usr/local/share/testfeld because /home where my standard user live is a NFS share and with the new user dolphin works normal! There must be something wrong in my /home folder? But where?
PS: why pcmanfm?
KDE alternatives would be Konqueror (which just embeds dolphin anyway, so trying it would be interesting in regard to your problem too) or krusader.
PCmanfm works similar how dolphin. I like the split screen with F3 and it’s good that almost the same keyboard shortcuts work here. Konqueror is something between Browser and FileManager.
And yes Konqueror starts normal but then he hangs while working.** I think I must delete some files in my home dir?
Ok, fine.
These are just the standard repos, so that should rule out a problem with incompatible versions… (apparently some stash stuff did make it into 42.3 already, but that should be unrelated to your problem)
You are right, had created a new user with his home-dir in /usr/local/share/testfeld because /home where my standard user live is a NFS share and with the new user dolphin works normal! There must be something wrong in my /home folder? But where?
TBH, I don’t have any experience with NFS (or /home on it).
I suppose a new user with home on the NFS has the same problem?
One possible reason for such a hang would be that the NFS server is unreachable. But that’s rather not the case here I suppose… :-/
Maybe try to boot an older kernel (“Advanced Options” in the boot menu), maybe the recent security updates somehow interfere here. But that’s just grasping at straws.
Another thing you could try (as you say it apparently started since some update): look at zypper’s (or YaST’s) installation history, and try to revert installed updates one by one to find out which one (e.g. via the “Versions” tab in YaST).
And/or try to switch back to some older snapshot (if you are using btrfs) and see if it works again.
Search in .config the dolphin files and delete them, and then restart
You can also try zypper dup, maybe there are updates in the updates
Alternatively there is Dfm as a file manager for plasma which is very nice https://software.opensuse.org/package/dfm
Please, don’t advise to run “zypper dup” on Leap for installing updates, that is for distribution upgrades and may have unexpected side effects (especially if using additional repos, as it does vendor changes).
“zypper up” (or “zypper patch” to restrict to official updates/patches) is the (only recommended) way to update Leap.
With just the standard repos, it shouldn’t make much difference though.
There are no third-party repositories, and Packman is missing
tux@iglu344:~> zypper lr -d
Die Repository-Prioritäten sind ohne Effekt. Alle aktivierten Repositorys teilen sich die gleiche Priorität.
# | Alias | Name | Aktiviert | GPG-Überprüfung | Aktualisierung | Priorität | Typ | URI | Dienst
--+----------------+----------------+-----------+-----------------+----------------+-----------+--------+-------------------------------------------------------------------------+-------
1 | non-oss | non-oss | Ja | (r ) Ja | Ja | 99 | rpm-md | http://repo1.intranet.local.de/distribution/leap/42.3/repo/non-oss/suse/ |
2 | non-oss-update | non-oss-update | Ja | (r ) Ja | Ja | 99 | rpm-md | http://repo1.intranet.local.de/update/leap/42.3/non-oss/ |
3 | oss | oss | Ja | (r ) Ja | Ja | 99 | rpm-md | http://repo1.intranet.local.de/distribution/leap/42.3/repo/oss/suse/ |
4 | oss-update | oss-update | Ja | (r ) Ja | Ja | 99 | rpm-md | http://repo1.intranet.local.de/update/leap/42.3/oss/ |
O my god zypper dup on leap is the end !
What happened to Leap that you can not do zypper dup anymore !!
I have always done it from Opensuse 9.3 up to Leap42.2, but now you can not do it anymore?
Of course you can. And there are cases where it makes sense, or even is necessary (e.g. to switch all packages to a certain repo).
But you shouldn’t avertise it here as a general way to update a Leap system.
The main purpose of “zypper dup” is to upgrade from one distribution version to the next, e.g. upgrade Leap 42.2 to 42.3.
It can be an incomplete update, and with zypper dup can solve, if there is nothing to update the same command says that there is nothing.
In any case, if the zypper dup command displays dependencies to be solved, it is clear that the system is not in place
Still no reason to use “zypper dup” here. It won’t magically find updates that “zypper up” doesn’t see… (unless they come from a different repo, but then it’s likely unintended anyway)
Again, it doesn’t matter much with only the standard repo, but somebody else may read your post and “break” his system.
In any case, if the zypper dup command displays dependencies to be solved, it is clear that the system is not in place
If that would be the case, “zypper up” will show the same.
Btw, the command to check dependencies is “zypper ve”…
zypper dup (when doen in circumstances that many people have) can make your system unusable in the same way that rm -rf can do (when done in certain places).
Please inform yourself about what zypper dup, zypper up and zypper patch do and for which actions the thus are to be used.
The fact that you did wrongly zypper dup in circumstances that did not bork your system does not mean that it will not do so for others in circumstances that are very very normal (having more repos with the same packages).
You better try to learn here instead of give false information…
So what? We saw that in his post, he explained why it is as it is and we accepted that without a word. What is the problem?" And what does it have to do with your wrong advice to use zypper dup to update a Leap 43.3 installation?
My problem persists. And I have create a new user with home on the NFS and there is no problem, the new user can start dolphin.
One possible reason for such a hang would be that the NFS server is unreachable. But that’s rather not the case here I suppose… :-/
Maybe try to boot an older kernel (“Advanced Options” in the boot menu), maybe the recent security updates somehow interfere here. But that’s just grasping at straws.
Another thing you could try (as you say it apparently started since some update): look at zypper’s (or YaST’s) installation history, and try to revert installed updates one by one to find out which one (e.g. via the “Versions” tab in YaST).
And/or try to switch back to some older snapshot (if you are using btrfs) and see if it works again.
So I need not search in my system and packages. The problem must be in my home directory. What I have test is the Browser Qupzilla has the same problem how dolphin.
What I have to say to my home directory is that I have been using it since openSuse13.2 and I can well imagine that there are any old config files that I have to change or delete.But which of the data and folders could be removed safely?
