[dolphin] [Bug 432862] dolphin crashes when starting

[Aurélien Oudelet]

https://bugs.kde.org/show_bug.cgi?id=432862

Aurélien Oudelet (auroud85_fr) <aoudelet at outlook.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aoudelet at outlook.com
          Component|search                      |general
                URL|                            |https://bugs.mageia.org/sho
                   |                            |w_bug.cgi?id=28324
           Platform|Other                       |Mageia RPMs

--- Comment #1 from Aurélien Oudelet (auroud85_fr) <aoudelet at outlook.com> ---
After many tries, we, at Mageia, conclude this is due to the Saved Session
management.

In facts, the "Live" user session and datas are carried over in the newly
installed system on harddrive to the first user which will have a new Unix name
based on user info and will have a user ID of 1000.
As reported by our KDE maintainers at Mageia at Comment 0, launching Dolphin in
Live env. is OK but not in newly installed system. It segfaults badly.

But, trying to know why, I created a totally new user "test" with totally empty
/home/test directory. And noow, Dolphin DOES NOT segfault. I conclued that:
there are strange bits of datas written somewhere in Live environment that are
carried over the newly system and present in the first user home directory.

Investigating:
The culprit is session management added to Dolphin in Dolphin 20.08 I think.
This is the option in Dolphin's preferences:
Startup => Show on startup "Folders, tabs, and window state from last time".

This wants to open /home/live/ with several name "live" somewhere... and it
crashed because it no longer exists although there is a symlink "Live" that
points to /home/aurelien (where "aurelien" is the name of the first user
created after installation on my test system).

But, the GUI option is not user accessible as Dolphin crashes as soon as it
launches.

After many tries, there are several files to delete to workaround this on
already installed systems:
First:
~/.config/session/dolphin_dolphin_dolphin
~/.config/dolphinrc

Remove everything in them. => No segfault after.

My request also is to know which CLI command can we type to deactivate the
option to restore the previous Dolphin's state.

-- 
You are receiving this mail because:
You are on the CC list for the bug.