Plasma does not save session
Tags:
None
Registered Member 
|
Hi,
I am using FreeBSD 8.4, and just upgraded my KDE from 4.10.5 to 4.12.4. For unknown reason, every time I login, All customization gone. Here what I had tried: - I removed .kde, and it just showed default workspace, but next login, still didn't save my customization. - I created new user, same effect. - Session managment already set to restore to previous. - Every time, I placed a widget into the screen, ~/.kde4/share/config/plasma-desktop-appletsrc changed, but next login, any customized gone. - So, I customized all virtual desktops, and set read only to plasma-desktop-appletsrc. I was expecting, my customized was reset to previous one. But still the customization gone  - If I added a new startup program in system settings, but next login also gone. But old startup was there. - nepomuk run ok. - I have read to quit desktop from terminal, and run again (I forgot the command, something using kwinapp), but still the customization gone in the next login. But, restarting desktop from terminal, any shortcut that I placed on the screen, the shortcuts were there when desktop been restart from terminal (but also gone when login!) any help, please! |
|
does plasma-desktop-appletsrc change with the login?
If yes, try
That sets the file immutable. If it doesn't help, run
|
|
Registered Member
|
it doesn't help. I customized, I checked plasma-desktop-appletsrc changed, set read only and immutable, log off and login, the customization gone, but ofcouse file plasma-desktop-appletsrc remain the same as before I logged off (read only and immutable). So, somehow after login, plasma read from somewhere, and then plasma tried to overwrite file plasma-desktop-appletsrc. If it could not overwrite, it was using the unknown plasma-desktop-appletsrc
note: plasma-desktop-appletsrc.old2 was file before customization plasma-desktop-appletsrc was file after customization (with plasma-desktop-appletsrc.old2 was full customization) log off and login, plasma didn't use plasma-desktop-appletsrc |
Administrator
|
You mentioned that the Autostart applications were also affected - are applications other than Plasma Desktop also affected by this issue?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Some KDE applications could not be launched from menu (just cursor jumping up, down, then disappear). But I could run then from terminal of wbar. I tried dolpin, and gwenview. Konqueror run fine though. I got q-dbus message from some application, Including transmission-qt and restarted plasma from terminal. Non KDE application runs fine.
Edit About autostart I could not changed the autostart, it kept getting back to the old autostart (before upgraded) every time I login
Last edited by binyo66 on Tue May 06, 2014 10:58 am, edited 1 time in total.
|
|
the qdbus message is "common" (though not ok, but it happens for everybody)
more interesting is the segfault - do you also get a crash dialog? if not, can you "gdb --args dolphin --nofork" (or whatever process caused that message)? |
|
Registered Member
|
I didn't see the crash dialog. Transmission-qt just didn't want to lunch. Other applications run fine.
Cursor keep staying after (gdb) |
|
Registered Member
|
I could not run filezilla from KDE menu (with different userid), when I run it in terminal
But It seems filezilla run fine so far |
|
Administrator
|
When at the (gdb) prompt you then need to follow with "run" to start Dolphin.
In terms of the D-Bus messages - does running "qdbus" yield anything in particular? (it should give a long list of items, many which will start with org.freedesktop or org.kde).
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
If I run as myself, dolphin, run fine. But when I tried to run as root, I got error
qdbus shows
|
|
transmission-qt is not a KApplication and doesn't have the crash dialog signal handler - that's expectable.
you cannot (easily) run (many) KDE applications as root, use "kdesu" instead, it will set required environment variables (like the session dbus) - does the issue only occur when running applications as root under the session of a different user? Running gdb as root to run a KDE application is a bit tricky then, but I don't think you should not have to do this for the moment (it's only relevant for segfaulting applications and segfaulting KDE applications should trigger the crash dialog anyway) PS: sorry for not explaining gdb - i somehow assumed you were familiar with it =) when finally encountering the crash, type "bt" and then press enter until there's no output left. "detach" and "quit" will get you out. This will also work with transmission-qt |
|
Registered Member
|
typing bt 3x gave the same output, so I just detached it
BTW whereis kdesu? |
|
trying to gdb dolphin this way won't work at all, no reason to interact with gdb, the process already has exited.
kdesu should be part of kdebase-runtime. |
|
Registered Member
|
The application just stayed there. nothing happen |
|
I told you that debugging dolphin this way would be far more complicated and is not required since the only known segfault was apparently on transmission-qt
Far more important for now is to know why you insist on debugging it as root, thus again: does this problem only happen if you try to run an application as root under the session of another user? |
Bookmarks
Who is online
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], q.ignora, watchstar
