Bug 262978 - KDE sessions isn't fully restored (some applications missing)
Summary: KDE sessions isn't fully restored (some applications missing)
Status: RESOLVED LATER
Alias: None
Product: ksmserver
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-12 19:15 UTC by Marcelo Bossoni
Modified: 2011-12-02 11:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcelo Bossoni 2011-01-12 19:15:31 UTC
Version:           unspecified (using KDE 4.5.95) 
OS:                Linux

I'm using KDE 4.6RC2 from Kubuntu ppa and the saved session (on logout) isn't correctly saved/restored.

If I logout from my session with Kopete and qBittorrent opened, only Kopete is opened again.

If I open 3 apps, like Kopete, qbittorrent and chrome, only Kopete and qbittorrent are restored. Maybe we have -1 in some wrong place in the algorithm?

the content of the ksmserverrc file shows no qBittorrent at all
I already removed my .kde folder but no success

[$Version]
update_info=ksmserver.upd:kde3

[General]
screenCount=1

[LegacySession: saved at previous logout]
count=0

[Session: saved at previous logout]
clientId1=105552534f000129478717100000026470000
clientId2=105552534f000129478892100000018590000
clientId3=105552534f000129478717800000026470019
clientId4=105552534f000129478777400000026470034
clientId5=105552534f000129478787500000026470036
clientId6=105552534f000129478892600000018590017
clientId7=105552534f000129478892600000018590019
count=7
discardCommand1[$e]=rm,$HOME/.kde/share/config/session/kwin_105552534f000129478717100000026470000_1294789879_938704
discardCommand2[$e]=\\0
discardCommand3[$e]=rm,$HOME/.kde/share/config/session/kmix_105552534f000129478717800000026470019_1294789879_506278
discardCommand4[$e]=rm,$HOME/.kde/share/config/session/yakuake_105552534f000129478777400000026470034_1294789879_509442
discardCommand5[$e]=rm,$HOME/.kde/share/config/session/kopete_105552534f000129478787500000026470036_1294789879_507234
discardCommand6[$e]=
discardCommand7[$e]=rm,$HOME/.kde/share/config/session/printer-applet_105552534f000129478892600000018590019_1294789879_508937
program1=kwin
program2=/usr/bin/kactivitymanagerd
program3=/usr/bin/kmix
program4=/usr/bin/yakuake
program5=/usr/bin/kopete
program6=pulseaudio
program7=/usr/bin/printer-applet
restartCommand1=kwin,-session,105552534f000129478717100000026470000_1294789879_938704
restartCommand2=/usr/bin/kactivitymanagerd,-session,105552534f000129478892100000018590000_1294789879_506104
restartCommand3=/usr/bin/kmix,-session,105552534f000129478717800000026470019_1294789879_506278
restartCommand4=/usr/bin/yakuake,-session,105552534f000129478777400000026470034_1294789879_509442
restartCommand5=/usr/bin/kopete,-session,105552534f000129478787500000026470036_1294789879_507234
restartCommand6=
restartCommand7=/usr/bin/printer-applet,-session,105552534f000129478892600000018590019_1294789879_508937
restartStyleHint1=0
restartStyleHint2=0
restartStyleHint3=0
restartStyleHint4=0
restartStyleHint5=0
restartStyleHint6=0
restartStyleHint7=0
userId1=marcelo
userId2=marcelo
userId3=marcelo
userId4=marcelo
userId5=marcelo
userId6=marcelo
userId7=marcelo
wasWm1=true
wasWm2=false
wasWm3=false
wasWm4=false
wasWm5=false
wasWm6=false
wasWm7=false


Reproducible: Always

Steps to Reproduce:
Logout with qBittorrent and Kopete opened.
Login


Actual Results:  
Kopete is reopened. qBittorrent not reopened.

Expected Results:  
All opened applications are reopened.
Comment 1 Marcelo Bossoni 2011-01-28 00:42:20 UTC
Continues to happen on final kde 4.6 release
Comment 2 Jekyll Wu 2011-12-02 09:13:36 UTC
I can't reproduce the reported problem in KDE SC 4.8 beta1. Is it still a problem for the reporter in recent version?
Comment 3 Marcelo Bossoni 2011-12-02 10:24:46 UTC
Well,

Since I'm not using Kubuntu anymore (I've changed to archlinux) and since its not happening on current 4.7 I can consider this bug as solved.