1) Did a du (the first in the last 2 months!) 2 days ago following slh advices and all went well. No problem with kde or gcc transition. Dolphin was working but crashed when I tried to access /home; access to other places were ok. I then checked the location of /home in the dolphin settings and change it to the correct one; then dolphin crashed and I was never able to launch it again.

2) I tried to uninstall dolphin and istall it again but it keeps crashing due to a segmentation fault.

dolphin was upgraded from its KDE4 variant to a new KDE5 port a couple of days ago. This new KDE5 port has a couple of quite questionable traits of behaviour, but does work in general (and yes, it's also a tad crashy, but not all the time).

There are mostly two upgrade issues:
- as you mentioned, KDE4 dolphin needed file:/home/user as starting location, KDE5 dolphin insists in just /home/user (so you'll need to change that in the settings)
- the desktop icon location changed, so you probably need to delete the old icon from the quickstart bar and pull in the new (visually identical) one from the kmenu.

Concerning the crashiness, I haven't really found a pattern yet. For me, it tends working for hours and then it suddenly crashes while browsing totally normal directories (and all restarted windows keep crashing within a couple of seconds as well). It's a weird behaviour, but rebooting might make a difference. One bug tracking this would be #800061.

nsm

Post subject: RE: dolphin does not lauch Posted: 26.09.2015, 21:08

Joined: 2012-03-14
Posts: 17
Location: montreal
Status: Offline

Thank you for replying so quickly.
Dolphin does not lauch at all.
I almost always launch applications using alt-F2 but no success; trying to lauch it from konsole gets me a _segmentation fault_ message.
There is a glimpse of a window that could be dolphin flashing on the screen.

I tried to tweak the configuration by right clicking on the icon in the _K_ launcher (is that the proper name?) and using the _edit application..._ menu but no success there either.
Thanks again.

slh

Post subject: RE: dolphin does not lauch Posted: 26.09.2015, 23:01

Joined: 2010-08-25
Posts: 962

Status: Offline

I'd suggest to create a new user, with an empty profile (home directory) first, maybe it's just some old config interfering. (Trying with a fresh user/ empty $HOME is typically the best way, then one can selectively nuke the problematic config).

nsm

Post subject: RE: dolphin does not lauch Posted: 27.09.2015, 02:43

Joined: 2012-03-14
Posts: 17
Location: montreal
Status: Offline

Thanks
I create a new user: dolphin launch without problem.
But, _ then one can selectively nuke the problematic config_ is mystery to me. How do we do that?

Just to be sure, you mean _removing_ these files (folders), one at a time, going through the list?
Still a lot to learn.
Thank you very much again.

slh

Post subject: RE: dolphin does not lauch Posted: 27.09.2015, 16:39

Joined: 2010-08-25
Posts: 962

Status: Offline

There typically isn't much specific configuration for dolphin, so unless you have a very particular setup that would be hard to replicate, just delete all of them (those only affect dolphin, nothing else).

nsm

Post subject: RE: dolphin does not lauch Posted: 27.09.2015, 20:52

Joined: 2012-03-14
Posts: 17
Location: montreal
Status: Offline

Problem solved.
After removing the config files as per your (slh) advice, dolphin launch properly.
Funny thing is that it launched with the configuration that I set before the problem arised.

Thank you very much.
Despite difficult times, aptosid is still my distro of choice and I hope that it will live long.

slh

Post subject: RE: dolphin does not lauch Posted: 27.09.2015, 23:26

Joined: 2010-08-25
Posts: 962

Status: Offline

There is a difference, after starting from scratch, there are no KDE4-dolphin configs anymore - which means KDE5-dolphin doesn't try to migrate the configs (and this is one of the more fragile steps) or try to make sense of the old ones anymore.

KDE5 based applications store their configuration and session files in other places than KDE4 based applications do (and the file formats also tend to differ significantly). Many times KDE5 totally ignores previous KDE4 settings and reverts to upstream defaults (e.g. plasma), in other cases there are some limited migration approaches. In quite some cases KDE5 ports of popular KDE4 applications don't share much more than the name with their predecessors (especially for low-level/ basic applications integrating tightly with KDE's guts), in other cases the porting can be much more limited in scope - and often developers took the opportunity to remove vestiges of KDE3 derived code parts and concepts.