Bug 129310

Summary:	locked windows with no titlebar after "start new session" KDE form previous KDE session
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Darek Borkowski <borkows>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED WORKSFORME	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Darek Borkowski 2005-10-19 08:54:26 UTC

Problem persists in Suse linux pro 9.2 as in Open Suse 10.0 final. I use KDE by 
default, my wife too. When I'm logged into KDE and I choose "Switch user" and 
then "start new session" from KDE menu, the new xserver starts in console vt8 
and new KDM instance shows there. After loging into KDE session of different 
user the windows are VERY OFTEN BUT NOT ALWAYS locken into positions were they 
were opened. They don't have title bar or close, max, ... buttons. They are 
unmoveable even using ALT + LMB and I cannot resize them using ALT + RMB.
It seems that this does not appear when I use "Switch user" and then "Lock 
session and start another one". It also do not happen when new session uses 
Gnome or other than KDE window manager.
I think that problem may be related to binary nvidia gfx drivers. I use dual 
head configuration (one X server screen on TVout and second on DVI connected 
flatpanel). So after start new sessions the following two screens start. 
Moreover when I'm switching between the sessions I sometimes get corrupted 
screen. So I have to switch to the one of the six text consoles and thet to the 
graphical one and screen is OK. I have nvidia driver installed with fetch-
nvidia.sh (driver version 76.76).

The problem does not exist on my laptop on 9.3 and 10.0 SuSE Linux. The laptop 
has intel 8xx graphics card and single head x-server layout.

Comment 1 Lubos Lunak 2005-10-19 09:00:00 UTC

Try if the problem persists with the open source nvidia drivers. Check if process 'kwin' is running for the new user, if not, try to run it. If there's any crash information please provide it.

Comment 2 Darek Borkowski 2005-10-19 09:23:44 UTC

Indeed it depends on kwin is running or not. Sometimes it starts for new user in two instances sometimes not. I'll do the test with opensource nvidia driver at night, now I have go to work.
Is it a good idea to add kwin into ~/kde/Autostart ??? I doubt it.

Comment 3 Darek Borkowski 2005-10-20 07:22:29 UTC

I cannot start the X without nvidia legacy drivers. I tried to change "nvidia" to "nv" in /etc/X11/xorg.conf, comented out Load "glx", rmmod nvidia. But X always starts using legacy driver. I tried to change "nvidia" to "vesa" in xorg.conf. Same result. I renamed nvidia.ko to nvidia.ko.bak so the module cannot be load and X refuses to start. Strange for me. It worked in fedore core. How to test it?
PS: Comment to my previous comment, kwin either does not start at all or in two instances per user after starting new session.

Comment 4 Darek Borkowski 2005-11-16 08:56:04 UTC

I added soft link to kwin to ~/.kde/Autostart and it works good for now.

Comment 5 Lubos Lunak 2005-11-16 12:17:19 UTC

Do you have anything in ~/.xsession-errors or some core file that'd point out why kwin doesn't start up successfully?

Comment 6 Stephan Kulow 2006-05-07 11:38:03 UTC

we can't reproduce this and you did not provide the necessary info ;(

if you can reproduce it with 10.1, please reopen the bug with the information. Thanks