[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)

2018-03-20 Thread Christian Niemeyer
** Summary changed: - [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf + [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver) -- You received this bug notification because you are a member of Ubuntu-X, wh

[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf

2018-03-10 Thread Christian Niemeyer
Maybe this is i915/i965 intel driver related. If someone with an in intel IGP could reproduce this. I have xserver-xorg-video-intel installed by the way. With not mentioning "intel" explicitly as the driver in xorg.conf doesn't it automatically uses modesetting or glamorgl? -- You received this b

[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf

2018-03-10 Thread Christian Niemeyer
Just had the idea to unload "glx" and see if I can Disable Composite without crashing Xorg / startx / xinit. It works! Here's my xorg.conf: Section "Module" Disable "glx" EndSection Section "Extensions" Option "Composite" "0" EndSection I'll put my resulting Xorg.0.log as an attachment. Ho

[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-09 Thread Christian Niemeyer
I suspect libglx0 (transition from libgl1-mesa-glx to libglx0) Because now we have: /usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0 (from libglx0 in bionic, new with bionic) instead of: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 /usr/lib/x86_64-linux-gnu/mesa/l

[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Now I remove +s bit from /usr/bin/X, /usr/bin/xinit, /usr/bin/startx, /usr/bin/Xorg and tried to run Valgrind with it. Honestly I have no idea about debugging. I just know that valgrind and strace can be somehow use for it. Hope this helps! output of valgrind -v startx 1> valgrind_v_startx.txt 2>&

[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
tried with "strace startx" ** Attachment added: "strace startx" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5072778/+files/strace_startx_001.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. http

[Ubuntu-x-swat] [Bug 1754296] [NEW] [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Public bug reported: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite ex

[Ubuntu-x-swat] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Ok, thanks! However there was nothing in my /var/crash folder. Nonetheless I tried to file a new bug with ubuntu-bug xorg. It added lots of system information and logs. here it is: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296 -- You received this bug notification because you are

[Ubuntu-x-swat] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Tried with rebooting and restarting, nothing in /var/crash -- 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/1754177 Title: [bionic] xserver / startx crashes with Composite Disabled in xorg.

[Ubuntu-x-swat] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-07 Thread Christian Niemeyer
Another interesting thing with this xserver-xorg-core is that it ignores Option "AIGLX" "Off" in the ServerFlags section and initializes AIGLX. This also hasn't happened before bionic. And the crashing (see the Xorg.0.log in my previous post) seems to happen right where normally some AIGLX initial

[Ubuntu-x-swat] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-07 Thread Christian Niemeyer
Here's my glxinfo output when Xserver is not crashing (started with Composite *enabled*) ** Attachment added: "glxinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1754177/+attachment/5072328/+files/glxinfo.txt ** Description changed: For certain games I disable the Comp

[Ubuntu-x-swat] [Bug 1754177] [NEW] [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-07 Thread Christian Niemeyer
Public bug reported: For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bi

[Ubuntu-x-swat] [Bug 217908] Re: FFe: Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD implementation in several video drivers

2010-01-14 Thread Christian Niemeyer
However, please fix this upstream or patch xulrunner in the ubuntu repositories for lucid at least! I often use Ctrl++ to view websites larger, e.g. forums, articles etc. This is very annoying, when images get messep up. It's not a nice web experience. Thanks. -- FFe: Pixellated Images in Firefo

[Ubuntu-x-swat] [Bug 217908] Re: FFe: Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD implementation in several video drivers

2010-01-14 Thread Christian Niemeyer
here's a good and simple explanation what causes the problem on linux: http://www.neowin.net/forum/index.php?showtopic=826968&view=findpost&p=591626200 -- FFe: Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD implementation in several video drivers https://bugs.launchpad.net/bugs/2