Bug 24303

Summary:

X restarts when I maximize a window in KDE 4.3.1; brings me to KDM login screen

Product:

xorg

Reporter:

Zhivko <beadierps14>

Component:

Driver/Radeon

Assignee:

xf86-video-ati maintainers <xorg-driver-ati>

Status:

RESOLVED FIXED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

Version:

unspecified

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Xorg.0.log	none
Xorg.0.log.old	none

Description Zhivko 2009-10-04 08:27:44 UTC

I had a stable system running with the ati-git driver built on 14-SEP-2009. On 04-OCT-2009 I built a new git package and installed it witn no problem, but this time whenever I maximize a window, for instance my Konsole Terminal, X is being restarted and it brings me to my KDM login screen. I opened my Xorg.0.log file in Kate and miximized the window, and that brought me to my login screen too. This happens with or without Kwin composite being enabled. What puzzles me is that if I open Firefox and maximize the window it doesn't restart X.


============================
X -version

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH i686
Current Operating System: Linux jtb 2.6.30-ARCH #1 SMP PREEMPT Wed Sep 9 12:37:32 UTC 2009 i686
Build Date: 04 September 2009  03:37:03PM
=============================

Comment 1 Zhivko 2009-10-04 08:31:02 UTC

Created attachment 30037 [details] [review]
Xorg.0.log

Comment 2 Zhivko 2009-10-04 08:31:57 UTC

Created attachment 30038 [details] [review]
Xorg.0.log.old

Comment 3 Alex Deucher 2009-10-04 14:48:16 UTC

Can you get a proper backtrace of the crash with gdb?  Also, can you bisect what commit caused the problem?

Comment 4 Zhivko 2009-10-05 10:18:41 UTC

(In reply to comment #3)
> Can you get a proper backtrace of the crash with gdb?  Also, can you bisect
> what commit caused the problem?
> 

Should I do a gdb on /usr/bin/X ? I haven't done this before. If I do so I get

======
Starting program: /usr/bin/X 
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program exited with code 01.
(gdb) 
[K(gdb) Hangup detected on fd 0
Error detected on fd 0
error detected on stdin
======

I think the last 3 rows are generated when X restarts when I maximized a window. But it it could be a standard gdb output whenever X crashes and gdb is stopped. Not sure I'm doing it properly.

As far as the commits, I really don't know what could have caused it, I mean, I'm not an expert :(

Comment 5 Zhivko 2009-10-08 10:27:55 UTC

I tried with the official 6.12.4 and I don't have any problems with it.

Comment 6 Zhivko 2009-10-09 13:52:57 UTC

Doesn't appear to be happening now. No problems with newer build dates. 10x for the attention.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.