[Ubuntu-x-swat] [Bug 1794104] Re: Xorg crash on first boot after apt upgrade

2018-09-24 Thread Christian Kirbach
(gdb) bt full #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 set = {__val = {171515904, 0, 0, 0, 0, 94870821356889, 94870821322000, 67108868, 140427223543248, 0, 0, 978464917824351488, 54, 94870838790880, 140727493513216, 140427243872632}} pid =

[Ubuntu-x-swat] [Bug 1794104] [NEW] Xorg crash on first boot after apt upgrade

2018-09-24 Thread Christian Kirbach
Public bug reported: I installed a daily snapshot of 18.10 in a VM. After removing some unneccessary application, I ran apt update apt upgrade and rebooted. I noticed X crashing after the reboot, taking me back to the login manager. I have the option selected to automatically login without pas

[Ubuntu-x-swat] [Bug 1237904] Re: Xorg crashed with SIGABRT in OsAbort()

2015-10-12 Thread Christian Kirbach
I do not understand why this is marked as invalid. It affects >100 people and I cannot see any questions not answered by the people affected. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1

[Ubuntu-x-swat] [Bug 1502571] Re: Xorg crashed with SIGABRT in switch_to (vt=7, from=0x560d7b89046d "xf86CloseConsole")

2015-10-04 Thread Christian Kirbach
** Attachment added: "StackTrace" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1502571/+attachment/4483498/+files/Xorg-stacktrace.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 1479913] Re: SRU request: fglrx.ko fails because of backported GPL-only 'pci_ignore_hotplug' symbol

2015-08-18 Thread Christian Kirbach
2:15.200-0ubuntu4.2 #verification-done The build succeeds now. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1479913 Title: SRU request: fglrx.ko fails because of backported

[Ubuntu-x-swat] [Bug 1449448] Re: fglrx-core 2:15.200-0ubuntu4: fglrx-core kernel module failed to build [error: ‘IRQF_DISABLED’ undeclared (first use in this function)]

2015-08-17 Thread Christian Kirbach
You are using kernel 4.1 This AMD catalyst (fglrx) does not support kernel 4.1 A patch has been suggested Fall back to kernel 4.0 and it should work again -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.la

[Ubuntu-x-swat] [Bug 351532] Re: [Jaunty] X quits with code 0177 when moving windows or scrolling using tdfx video driver

2011-04-29 Thread Christian Kirbach
This issue is fixed in Ubuntu Karmic ** Changed in: xserver-xorg-video-tdfx (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-tdfx in Ubuntu. https://bugs.launchpad.net/bugs/351

[Ubuntu-x-swat] [Bug 635419] Re: [maverick] Xserver segfaults with ATI cards in libglx module initialisation

2011-04-18 Thread Christian Kirbach
We can close this case. It was fixed at some point. ** Changed in: xorg-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/635419 Title: [m

[Ubuntu-x-swat] [Bug 714780] Re: [Natty Alpha-2] segfault in libexa module

2011-02-12 Thread Christian Kirbach
Hi, this one is not reproducable at will. Crash happened while running off the installation media, i.e. in the installation X session. Not sure if you can somehow use debugging symbols in that sessin. -- You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 105629] Re: DDC/EDID not working with tdfx driver

2011-02-07 Thread Christian Kirbach
This no longer holds true for me for Ubuntu 10.10 I believe the report can be closed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-tdfx in ubuntu. https://bugs.launchpad.net/bugs/105629 Title: DDC/EDID not working with t

[Ubuntu-x-swat] [Bug 351532] Re: [Jaunty] X quits with code 0177 when moving windows or scrolling using tdfx video driver

2011-02-07 Thread Christian Kirbach
This issue is fixed in Ubuntu Karmic and later. I believe the report can be closed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-tdfx in ubuntu. https://bugs.launchpad.net/bugs/351532 Title: [Jaunty] X quits with code 01

[Ubuntu-x-swat] [Bug 714780] Re: [Natty Alpha-2] segfault in libexa module

2011-02-07 Thread Christian Kirbach
'invalid frame buffer' looks suspicious in /var/log/messages Feb 7 18:54:09 ubuntu kernel: [ 276.606847] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id Feb 7 18:54:20 ubuntu ubiquity[3469]: debconffilter_done: ubi-partman (current: ubi-partman) Feb 7 18:54:20 ubuntu ubiquity[3469]: dbfi

[Ubuntu-x-swat] [Bug 714780] [NEW] [Natty Alpha-2] segfault in libexa module

2011-02-07 Thread Christian Kirbach
Public bug reported: Binary package hint: xorg Crash happened with Ubuntu Natty Alpha 2 in the installation X session, not the 'try Ubuntu' session. I.e. not in an installed system Ubiquity and Firefox were opened. I do not recall what exactly I did, but I was working in Firefox and launchpad.ne

[Ubuntu-x-swat] [Bug 714780] Re: [Natty Alpha-2] segfault in libexa module

2011-02-07 Thread Christian Kirbach
ubuntu@ubuntu:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx) 00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2) 00:12.0 USB Controller: ATI Technolo

[Ubuntu-x-swat] [Bug 714780] Re: [Natty Alpha-2] segfault in libexa module

2011-02-07 Thread Christian Kirbach
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in ubuntu. https://bugs.launchpad.net/bugs/714780 Title: [Natty Alpha-2] segfault in libexa module ___ Mailing list: https://launchpad.net/~ubun

[Ubuntu-x-swat] [Bug 635419] Re: [maverick] Xserver segfaults with ATI cards in libglx module initialisation

2010-10-14 Thread Christian Kirbach
I believe we can close this case, then. -- [maverick] Xserver segfaults with ATI cards in libglx module initialisation https://bugs.launchpad.net/bugs/635419 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 635419] Re: [maverick] Xserver segfaults with ATI cards in libglx module initialisation

2010-10-03 Thread Christian Kirbach
After installing fglrx you need to configure X to use the fglrx ATi driver: $ sudo aticonfig --initial and restart X. (I guess Ubuntu's restricted hardware tool does the same) It is odd that you still get the error using the open source drivers. At least the vesa driver does currently work for

[Ubuntu-x-swat] [Bug 545257] Re: gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion()

2010-09-26 Thread Christian Kirbach
with the latest updates fglrx kernel modules compile fine now (unlike before) -- gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion() https://bugs.launchpad.net/bugs/545257 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-i

[Ubuntu-x-swat] [Bug 635419] Re: [maverick] Xserver segfaults with ATI cards in libglx module initialisation

2010-09-25 Thread Christian Kirbach
The workaround is to install ATI's fglrx from the latest updates (2:8.780-0) and use that driver since it now compiles against the kernel used, unlike before. -- [maverick] Xserver segfaults with ATI cards in libglx module initialisation https://bugs.launchpad.net/bugs/635419 You received this bu

[Ubuntu-x-swat] [Bug 635419] Re: [maverick] Xserver segfaults with ATI cards in libglx module initialisation

2010-09-24 Thread Christian Kirbach
** Summary changed: - [maverick] Xserver segfaults in libglx module initialisation + [maverick] Xserver segfaults with ATI cards in libglx module initialisation -- [maverick] Xserver segfaults with ATI cards in libglx module initialisation https://bugs.launchpad.net/bugs/635419 You received this

[Ubuntu-x-swat] [Bug 635419] Re: Xserver segfaults in 10.10

2010-09-20 Thread Christian Kirbach
In my case the system does not become unresponsive, but instead I end up at the console login prompt. ** Attachment added: "full X log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/635419/+attachment/1614557/+files/Xorg.0.log ** Summary changed: - Xserver segfaults in 10.10 + [

[Ubuntu-x-swat] [Bug 635419] Re: Xserver segfaults in 10.10

2010-09-20 Thread Christian Kirbach
Confirming with an ATI HD3200 IGP chipset and up-to-date maverick installation -- Xserver segfaults in 10.10 https://bugs.launchpad.net/bugs/635419 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 105629] Re: DDC/EDID not working with tdfx driver

2009-10-08 Thread Christian Kirbach
Actuall, HorizSync and VertRefresh must be specified manually else X defaults to 800x600 This seems to be the best workaround for me -- DDC/EDID not working with tdfx driver https://bugs.launchpad.net/bugs/105629 You received this bug notification because you are a member of Ubuntu-X, which is s

[Ubuntu-x-swat] [Bug 351532] Re: [Jaunty] X quits with code 0177 when moving windows or scrolling using tdfx video driver

2009-10-07 Thread Christian Kirbach
This issue is fixed in Ubuntu Karmic beta ii xorg 1:7.4+3ubuntu5 X.Org X Window System ii xserver-xorg-video-tdfx 1:1.4.1-1 X.Org X server -- tdfx display driver -- [Jaunty] X

[Ubuntu-x-swat] [Bug 105629] Re: DDC/EDID not working with tdfx driver

2009-10-07 Thread Christian Kirbach
Last comment still holds true for Ubuntu Karmic beta. Odd enough, after logging out, i.e. restarting X, resolution switches to 1024x768. DDC/EDID still broken, driver assumes 800x600 on first X startup even if 16 bit colours and 1024x768 resolution are requested in the screen section like