Bug#613957: desktop broken after login with xserver-xorg-video-radeon 1:6.14.0-1 (Radeon X1550 64-bit)

2011-02-18 Thread Jonas Meurer
Package: xserver-xorg-video-radeon Version: 1:6.14.0-1 Severity: important Hello, Since the upgrade to xserver-xorg-video-radeon 1:6.14.0-1, my desktop is broken after the login with gdm3. My system is an up-to-date debian/sid amd64 system running gnome. I'll try to explain the exact symptoms:

Bug#613957: desktop broken after login with xserver-xorg-video-radeon 1:6.14.0-1 (Radeon X1550 64-bit)

2011-02-18 Thread Cyril Brulebois
Hi Jonas, Jonas Meurer jo...@freesources.org (18/02/2011): After I downgraded xserver-xorg-video-radeon to version 1:6.13.2-2 and restarted X (gdm3), the problem disappeared. thanks for mentioning the last working version. I'm happy to provide any further information that is needed to fix

Bug#613957: desktop broken after login with xserver-xorg-video-radeon 1:6.14.0-1 (Radeon X1550 64-bit)

2011-02-18 Thread Jonas Meurer
Hey Cyril, On 18/02/2011 Cyril Brulebois wrote: I'm happy to provide any further information that is needed to fix this bug. Please don't hesitate to ask me. What would be great would be giving master a try. That would be something like: sudo apt-get build-dep xserver-xorg-video-ati

Bug#613957: desktop broken after login with xserver-xorg-video-radeon 1:6.14.0-1 (Radeon X1550 64-bit)

2011-02-18 Thread Cyril Brulebois
forwarded 613957 https://bugs.freedesktop.org/show_bug.cgi?id=34452 thanks Jonas Meurer jo...@freesources.org (18/02/2011): just gave that a try, but unfortunately the bug still exists. therefore I reported the bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=34452 Thanks! Letting

Bug#613957: desktop broken after login with xserver-xorg-video-radeon 1:6.14.0-1 (Radeon X1550 64-bit)

2011-02-18 Thread Cyril Brulebois
Jonas Meurer jo...@freesources.org (18/02/2011): It seems like this bug is in xserver-xorg-core rather than in the radeon video driver. See the buglog of upstream bugreports 34452 and 33929. The patch that fixed the bug for me is located at