[Ubuntu-x-swat] [Bug 487204] [NEW] radeon_loc k.c:65: radeonGetLock: „drawable != ((vo id *)0)” Assertion

2009-11-23 Thread Roti
Public bug reported: Binary package hint: xserver-xorg-video-radeon starting smc gives me this: radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion karmic 2.6.31-15-generic xserver-xorg-video-radeon 1:6.12.99+git20090929.7968e1fb-0ubuntu1 ProblemType: Bug Architecture: i386 Dat

[Ubuntu-x-swat] [Bug 487204] Re: radeon_lock. c:65: radeonGetLock: „drawable != ((void *)0)” Assertion

2009-11-23 Thread Roti
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35978840/Dependencies.txt -- radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion https://bugs.launchpad.net/bugs/487204 You received this bug notification because you are a member of Ubuntu-X, which is subs

[Ubuntu-x-swat] [Bug 487204] Re: radeon_lock. c:65: radeonGetLock: „drawable != ((void *)0)” Assertion

2009-11-23 Thread Roti
my videocard is: ATI Technologies Inc Radeon R200 QL [Radeon 8500 LE] -- radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion https://bugs.launchpad.net/bugs/487204 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-a

[Ubuntu-x-swat] [Bug 433075] Re: Xorg crashed with SIGSEGV on ATI hybrid graphics laptop with fglrx enabled

2009-12-02 Thread Roti
I had an X crash today. fresh Karmic install on 11-05. For a while I used 3D, but now I disabled visual effects. When I clicked a button on skype, X crashed. end of Xorg.0.log: Backtrace: 0: /usr/bin/X(xorg_backtrace+0x26) [0x4f00c6] 1: /usr/bin/X(xf86SigHandler+0x41) [0x4852c1] 2: /lib/libc.so.6

[Ubuntu-x-swat] [Bug 433075] Re: Xorg crashed with SIGSEGV on ATI hybrid graphics laptop with fglrx enabled

2009-12-02 Thread Roti
** Attachment added: "Xorg log" http://launchpadlibrarian.net/36329102/Xorg.0.log.old -- Xorg crashed with SIGSEGV on ATI hybrid graphics laptop with fglrx enabled https://bugs.launchpad.net/bugs/433075 You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 487204] Re: radeon_lock. c:65: radeonGetLock: „drawable != ((void *)0)” Assertion

2009-12-06 Thread Roti
** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/36522616/Xorg.0.log.old -- radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion https://bugs.launchpad.net/bugs/487204 You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 487204] Re: radeon_lock. c:65: radeonGetLock: „drawable != ((void *)0)” Assertion

2009-12-06 Thread Roti
this one contains the backtrace ** Attachment added: "Xorg.0.log.old" http://launchpadlibrarian.net/36522625/Xorg.0.log.old -- radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion https://bugs.launchpad.net/bugs/487204 You received this bug notification because you are a membe

[Ubuntu-x-swat] [Bug 487204] Re: radeon_lock. c:65: radeonGetLock: „drawable != ((void *)0)” Assertion

2009-12-06 Thread Roti
** Attachment added: "lspci -vvnn" http://launchpadlibrarian.net/36522634/lspci-vvnn -- radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion https://bugs.launchpad.net/bugs/487204 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x

[Ubuntu-x-swat] [Bug 487204] Re: radeon_lock. c:65: radeonGetLock: „drawable != ((void *)0)” Assertion

2009-12-23 Thread Roti
I changed my card to ATI Technologies Inc RV350 AR [Radeon 9600] the same problem exist. And the same problem with foobillard, and ppracer too. -- radeon_lock.c:65: radeonGetLock: „drawable != ((void *)0)” Assertion https://bugs.launchpad.net/bugs/487204 You received this bug notification becaus

[Ubuntu-x-swat] [Bug 460440] Re: X [r300_dri.so] segfault when closing glxgears

2009-12-23 Thread Roti
i have segfault with smc, foobillard, ppracer Program received signal SIGSEGV, Segmentation fault. 0xb747e6e9 in ?? () from /usr/lib/dri/r300_dri.so (gdb) bt #0 0xb747e6e9 in ?? () from /usr/lib/dri/r300_dri.so #1 0xb75d3e3c in _mesa_Clear () from /usr/lib/dri/r300_dri.so #2 0x08050d5e in ?? ()

[Ubuntu-x-swat] [Bug 296122] Re: XNEST crashes in X_PolyFillRectangle with error config/hal: NewInputDeviceRequest failed

2010-01-06 Thread Roti
problem in karmic: $ Xnest :1 -query 192.168.99.118 [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! (EE) config/hal: NewInputDeviceRequest failed (2) (EE) config/hal: NewInputDeviceRequest failed (2) (EE) config/hal: NewInputDeviceRequest failed (2) (EE)

[Ubuntu-x-swat] [Bug 453989] Re: Xephyr - unrecognised device identifier!

2010-01-06 Thread Roti
still exists $ Xephyr :1 -ac -query myhostname [dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed (2) unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed

[Ubuntu-x-swat] [Bug 453989] Re: Xephyr - unrecognised device identifier!

2010-01-06 Thread Roti
on karmic ** Attachment added: "dmesg" http://launchpadlibrarian.net/37494000/dmesg -- Xephyr - unrecognised device identifier! https://bugs.launchpad.net/bugs/453989 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. __

[Ubuntu-x-swat] [Bug 453989] Re: Xephyr - unrecognised device identifier!

2010-01-06 Thread Roti
updated today ** Attachment added: "lspci" http://launchpadlibrarian.net/37494027/lspci -- Xephyr - unrecognised device identifier! https://bugs.launchpad.net/bugs/453989 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. __