Bug 87499

Summary:	Session can't be restored on another display
Product:	[I don't know] kde	Reporter:	Alex Hermann <gaaf>
Component:	dualhead	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alex Hermann 2004-08-19 12:51:28 UTC

Version:            (using KDE KDE 3.3.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The session won't restore if i use 'Start New Session' on the K-menu. The new session will start on display :2. (vt9) while it was saved on dispay :1. (vt8).
The session also doesn't restore for display :0. (vt7)

Note that this also means kwin is not started, and makes it difficult for the average user to use the system.

----------------------
How to reproduce:
----------------------
1) login as user1 to vt7 and log out, thereby saving the session.
2) login as user2 to vt7
3) start a new session as user1 (on vt8)
4) the session of user1 is not restored

----------------------
Expected behaviour
----------------------
One would expect that the display number in ksmserverrc is ignored, the screen number should be used though.

----------------------
.xsession-errors
----------------------
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified

kwin: cannot connect to X server :1.0
Xlib: connection to ":1.1" refused by server
Xlib: No protocol specified

kwin: cannot connect to X server :1.1
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified

konsole: cannot connect to X server :1.0
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified

kded: cannot connect to X server :1
DCOP aborting call from 'anonymous-11484' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified

kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
Xlib: connection to ":1.0" refused by server
Xlib: No protocol specified

ksensors: cannot connect to X server :1
DCOP aborting call from 'anonymous-11472' to 'ksensors'
ERROR: Communication problem with ksensors, it probably crashed.

------------------------------
ksmserverrc
------------------------------
[$Version]
update_info=ksmserver.upd:kde3

[General]
screenCount=2

[LegacySession: saved at previous logout]
count=0

[Session: saved at previous logout]
clientId1=117f000001000109291061900000106230000
clientId2=117f000001000109291061900000106230001
clientId3=117f000001000109291202500000110530008
clientId4=117f000001000109291064500000106230013
count=4
discardCommand1=rm,$HOME/.kde/share/config/session/kwin_117f000001000109291061900000106230000_1092912035_176648
discardCommand2=rm,$HOME/.kde/share/config/session/kwin_117f000001000109291061900000106230001_1092912035_176861
discardCommand3=
discardCommand4=rm,$HOME/.kde/share/config/session/konsole_117f000001000109291064500000106230013_1092912035_130484
program1=kwin
program2=kwin
program3=ksensors
program4=konsole
restartCommand1=kwin,-session,117f000001000109291061900000106230000_1092912035_176648,-display,:1.0
restartCommand2=kwin,-session,117f000001000109291061900000106230001_1092912035_176861,-display,:1.1
restartCommand3=ksensors,-session,117f000001000109291202500000110530008_1092912035_128400,-display,:1
restartCommand4=konsole,-session,117f000001000109291064500000106230013_1092912035_130484,-display,:1.0
restartStyleHint1=0
restartStyleHint2=0
restartStyleHint3=0
restartStyleHint4=0
userId1=waxy
userId2=waxy
userId3=waxy
userId4=waxy

Comment 1 Oswald Buddenhagen 2004-08-27 22:05:45 UTC

no idea what is going on, but it's not my responsibility anyway. :-P
worksforme, btw.

Comment 2 Alex Hermann 2004-08-28 15:26:49 UTC

The problem is the "-display :1" in the "restartCommand" lines. If the user logs in to another display number, the applications can't be started because that user has no access to display :1.
The applications should be restarted on the display the user is currently logged in to, and not on the one he/she was previously logged into.

Comment 3 Lubos Lunak 2004-08-28 16:07:33 UTC

Multihead specific. I have to wonder if the unmaintained hacks are worth all this.

Comment 4 Andrew Crouthamel 2018-11-02 04:21:54 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-11-16 02:49:06 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 6 Nate Graham 2020-09-09 02:58:41 UTC

Bug was reported against KDE3 and pertains to dualhead (as distinct from multi-monitor), neither of which are officially supported anymore.