Dolphin do not start anymore

**ronaldhafer** · 18-Jan-2018, 07:44

Hello Suse Community,

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:

Code:

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 only thing I see is an empty frame.

Thx for help
Ronni

**wolfi323** · 18-Jan-2018, 08:00

And what repos are you using?

Code:

zypper lr -d

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.

**ronaldhafer** · 19-Jan-2018, 01:32

Hello wolfi323,

thx for the fast answer and sorry for my late replay.

Originally Posted by wolfi323

And what repos are you using?

Code:

zypper lr -d

My repo list:

Code:

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/                     |

but the URI is from my local repository-server (have more than 5 PC), the repo1 load the repos with wget from:

Code:

repo1:~ # cat /etc/cron.d/my-repos
22 18 * * 5 repo wget --timeout=1200 --no-verbose -t6 -N -r -X /linux/opensuse/distribution/leap/42.3/repo/oss/suse/setup/ --no-host-directories -np --cut-dirs=2 http://ftp.uni-bayreuth.de/linux/opensuse/distribution/leap/42.3/repo/oss/suse/ -P /srv/www/repo/ > /var/adm/log/repo-oss.log 2>&1
26 18 * * 6 repo wget --timeout=1200 --no-verbose -t6 -N -r -X /linux/opensuse/update/leap/42.3/oss/src/ --no-host-directories -np --cut-dirs=2 http://ftp.uni-bayreuth.de/linux/opensuse/update/leap/42.3/oss/ -P /srv/www/repo/ > /var/adm/log/repo-oss-update.log 2>&1
42 21 * * 4 repo wget --timeout=1200 --no-verbose -t6 -N -r -X /linux/opensuse/distribution/leap/42.3/repo/non-oss/suse/setup/ --no-host-directories -np --cut-dirs=2 http://ftp.uni-bayreuth.de/linux/opensuse/distribution/leap/42.3/repo/non-oss/suse/ -P /srv/www/repo/ > /var/adm/log/repo-non-oss.log 2>&1
51 22 * * 4 repo wget --timeout=1200 --no-verbose -t6 -N -r -X /linux/opensuse/update/leap/42.3/non-oss/src/ --no-host-directories -np --cut-dirs=2 http://ftp.uni-bayreuth.de/linux/opensuse/update/leap/42.3/non-oss/ -P /srv/www/repo/ > /var/adm/log/repo-non-oss-update.log 2>&1

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?

Best Regards
Ronni

**wolfi323** · 19-Jan-2018, 01:56

Originally Posted by ronaldhafer

My repo list:

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.

**V_ido** · 19-Jan-2018, 02:22

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

**wolfi323** · 19-Jan-2018, 02:28

Originally Posted by V_idocq

You can also try zypper dup, maybe there are updates in the updates

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.

**hcvv** · 19-Jan-2018, 03:10

Originally Posted by V_idocq

You can also try zypper dup,

NO! Not on Leap!

Please do not give wrong advice. People may bork their systems.

**V_ido** · 19-Jan-2018, 04:49

Originally Posted by wolfi323

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

Code:

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?

**wolfi323** · 19-Jan-2018, 04:52

Originally Posted by V_idocq

TO 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.

**V_ido** · 19-Jan-2018, 05:06

Originally Posted by wolfi323

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