SRU: Launching a Qt app crashes X when using Xinerama

[Alejandro Cuervo]

Justification:
=============
Regression from Ubuntu 10.04, causing an Xserver crash when starting a Qt application in an multi-head X configuration using Xinerama. The X crash risks losing user data from unsaved documents in applications.

Fix:
===
This is caused by a typo in commit 80b5d3a3. A fix has been pulled to the server-1.9 stable branch in commit 3effb61e (http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d ). This commit has been cherry-picked onto the Natty xserver tree.

Test case:
========
Start a Qt app such as Skype while using Xinerama multi-head. Users of the binary nVidia driver who have multiple monitors and select “Separate X screen” rather than “Twinview” in nvidia-settings will be using a Xinerama multi-head configuration.

Regression Potential:
==================
Low. Patch is a one-line typo fix, and anything which exercises this codepath currently crashes.

Original report:

PROBLEM
=======
Starting a Qt app such as Skype crashes X, leaving
"Caught signal 11 (Segmentation fault). Server aborting"
in Xorg.0.log.old and the dazzled user with the login screen.
This is a bug in X, fixed upstream in http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d .

WORKAROUND
==========
Until the fix is released as an official Ubuntu update, Jared Bunting has it in his PPA at https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539 (thx!).
You need xserver-xorg-core and xserver-common, so for 32 bit
1) Download
https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539/+files/xserver-xorg-core_1.9.0-0ubuntu7%2Bbug650539%2B1_i386.deb and
https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539/+files/xserver-common_1.9.0-0ubuntu7%2Bbug650539%2B1_all.deb
2) Install
sudo dpkg -i xserver-xorg-core_1.9.0-0ubuntu7+bug650539+1_i386.deb xserver-common_1.9.0-0ubuntu7+bug650539+1_all.deb

ORIGINAL DESCRIPTION
====================
I think this may be related to QT apps, as keepassx, skype also crash X when started
This is on maverick will all current updates.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: speedcrunch 0.10.1-2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Sep 28 12:29:04 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: speedcrunch
---
Architecture: amd64
DistroRelease: Ubuntu 10.10
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
NonfreeKernelModules: nvidia
Package: xorg 1:7.5+6ubuntu3
PackageArchitecture: amd64
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Tags: maverick
Uname: Linux 2.6.35-22-generic x86_64
UnreportableReason: The drivers from nvidia.com are not supported by Ubuntu. Please uninstall them and test whether your problem still occurs.
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

[Alejandro Cuervo (a-cuervo)]

Backtrace:
[ 3664.878] 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a0fa8]
[ 3664.878] 1: /usr/bin/X (0x400000+0x60fcd) [0x460fcd]
[ 3664.878] 2: /lib/libpthread.so.0 (0x7fe2b211e000+0xfb40) [0x7fe2b212db40]
[ 3664.878] 3: /usr/bin/X (0x400000+0xbb22f) [0x4bb22f]
[ 3664.878] 4: /usr/bin/X (0x400000+0x2c2d9) [0x42c2d9]
[ 3664.878] 5: /usr/bin/X (0x400000+0x2184b) [0x42184b]
[ 3664.878] 6: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7fe2b1089d8e]
[ 3664.878] 7: /usr/bin/X (0x400000+0x213d9) [0x4213d9]
[ 3664.879] Segmentation fault at address 0x4
[ 3664.879]
Caught signal 11 (Segmentation fault). Server aborting
[ 3664.879]
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 3664.879] Please also check the log file at "/var/log/Xorg.0.log" for additional information.

[Alejandro Cuervo (a-cuervo)]

apport information

[Alejandro Cuervo (a-cuervo)]

apport information

[Fabio Marconi (fabiomarconi)]

Hello
Is this issue present again with the latest updatets?
Thanks
Fabio

[Alejandro Cuervo (a-cuervo)]

I just installed a bunch of the latest updates, including a whole bunch of QT related, rebooted, and it is still happening.
Apps are crashing either on launch or as soon as you hover over them. :(
I found people on the net having the same issue with no answers or workarounds. At least now I know I'm not the only one with this issue.
Any ideas?

[Fabio Marconi (fabiomarconi)]

Not reproducible by me in a fully updated (backports + proposed enabled) maverick

[Alejandro Cuervo (a-cuervo)]

I did not have backports or proposed enabled.
However for the sake of testing, I just enabled them one a time, neither of them had package updates.
I also went a version back on the proprietary nvidia drivers (thinking they may be an issuse) but nothing changed.
Those apps still crash.
I have a pretty standard setup, so don't know what the culprit may be.
I do know however, that I am not the only one affected by this issue. I'm trying for the other affected people to voice their problem here

[Chris Fell (brucemcbruce)]

This bug affected me as well on a fresh maverick install with the nVidia drivers installed.
I tried re-installing ubuntu, and I've managed to track down exactly what causes QT apps to crash - it appears to be to do with my multi-monitor setup. I have tried all X configurations (single, twinview and 'separate X screens', with and without xinerama) and it only occurs on separate X screens with xinerama enabled.

Alejandro, are you using a multi-monitor setup?

[Chris Fell (brucemcbruce)]

My xorg.conf, initially generated by nvidia-xconfig and further tweaked by the nvidia xserver settings utility.

[Alejandro Cuervo (a-cuervo)]

Chris, I am indeed running a 3 monitor setup, with the nvidia proprietary drives and Xinerama enabled.
I was beginning to suspect Xinerama, but had doubts since it was working ok on 10.04.

First a little bit of history:
My multi-monitor setup has always given me trouble since I added the 3rd monitor. Two were always perfect with twinview.
When I added the 3rd, I had to switch to Xinerama because It was the only configuration I could make work. When I upgraded to 10.04 everything continued to work well, except for the occasional X crash, due to this bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/570151.
Hoping to completely fix that bug I upgraded to 10.10RC because it had a newer version of Xserver. That bug seems to be fixed (I think), but now this QT bug appears. It seems that I will never get back a perfect running 3 monitor setup. :(
Multi-monitor configurations (3+) under Linux are very complex, hope someone can tackle this soon.

Any how, back to this bug, for the sake of testing I disabled Xinerama and indeed the problem went away.
Having Xinerama disabled is not a solution since it renders the whole multi-monitor setup pretty much useless. Not being able to drag windows from one monitor to another is simply not acceptable.
Not sure what changed from 10.04 to 10.10 that started this, so now I am not sure if this bug is a QT bug, a Xinerama Bug, an Xserver bug, or an Nvidia-Propietary drivers BUG.
Anyone can shed a light on this?

I am also attaching my xorg.conf file for documentation purposes and hopefully for someone to review it.

[Alejandro Cuervo (a-cuervo)]

Forgot to ask, Does anybody know if it is possible to run nVidia's twinview on a 3 monitor setup? Or is it just limited to 2 monitors?

[Alejandro Cuervo (a-cuervo)]

Jonathan, I don't think this is an issue with the Nvidia Drivers. Their current, their beta and their five prior versions of the Nvidia Drivers work well and without this issue on 10.04, 9.10 and 9.04

Also, according to the changelog of the Xinerama packages nothing changed between 10.04 and 10.10. (Xinerama is deprecated so not much work is going on there.)

So it must be an issue with QT since alot changed in the QT packages from 10.04 to 10.10.
Some change in the QT pakages broke its interaction with xinerama.

[Harald Sitter (apachelogger)]

X should not crash..

[espen (espen-offshoreutdanning)]

I can confirm that this also happens on a upgraded Ubuntu Maverick installation with a quad head setup, our computers running twinview works just fine.

[Jérôme (kibohely)]

I confirm it too (last nvidia drivers, 64bit, maverick up to date)

[Kevin McCarthy (me-kevinmccarthy)]

Confirmed.

Latest Xorg / Nvidia drivers / qt

Steps:

1. Launch a qt app (I used kcalc)
2. Move your mouse cursor over the app
3. Insta crash (Xorg Segfault)

- If you disable Xinerama, everything is fine
- If you use the nouveau (nv) open source drivers instead of the Nvidia binary blob (nvidia), the problem STILL happens

Same issue, other places:
https://bbs.archlinux.org/viewtopic.php?pid=836875#p836875
http://bugs.gentoo.org/show_bug.cgi?id=339135

[Jérôme (kibohely)]

Hi,

as i only have one monitor (the laptop's one), I don't think that xinerama is the core of this issue.

I try to desactivate xinerama in my xorg.conf :

Section "ServerFlags"
        Option "Xinerama" "0"
EndSection

and force TwinView in Section "Device" :

    Option "TwinView" "1"

but, it's still crash ...

[Jérôme (kibohely)]

same thing with ** Option Xinerama "0" ** in the Layout section ..

[Roland Ruiken (rolandruiken)]

Hi

i have the same problem:
Ubuntu 10.10 64 bit with the latest updates
Nvidia - propireter driver, 2 monitor

upstart of Skype crashes X-driver: i get logout
the same with KeepassX

[Roland Ruiken (rolandruiken)]

Hi

now I have disabled Xinerama, and KeepassX works well, no crash, no Logout.

But it would be fine to get Xinerama again.....

[Jérôme (kibohely)]

hi,

as I have only one monitor, and it's doesn't work, it's seems that I didn't
do the right thing to disable Xinerama ?!?! What are yout suggestion to do
it right? (my Xorg.conf is in attachment)

Thanks

On Fri, Oct 8, 2010 at 10:57 AM, Roland Ruiken <email address hidden>wrote:

> Hi
>
> now I have disabled Xinerama, and KeepassX works well, no crash, no
> Logout.
>
> But it would be fine to get Xinerama again.....
>
> --
> Launching QT apps such as SpeedCrunch, keepassX, Lucky Backup, Pencil,
> Stellarium, skype chrashes Xsever
> https://bugs.launchpad.net/bugs/650539
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “nvidia-graphics-drivers” package in Ubuntu: New
> Status in “qt4-x11” package in Ubuntu: Invalid
>
> Bug description:
> I think this may be related to QT apps, as keepassx, skype also crash X
> when started
> This is on maverick will all current updates.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: speedcrunch 0.10.1-2
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Tue Sep 28 12:29:04 2010
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: speedcrunch
> ---
> Architecture: amd64
> DistroRelease: Ubuntu 10.10
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
> NonfreeKernelModules: nvidia
> Package: xorg 1:7.5+6ubuntu3
> PackageArchitecture: amd64
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Tags: maverick
> Uname: Linux 2.6.35-22-generic x86_64
> UnreportableReason: The drivers from nvidia.com are not supported by
> Ubuntu. Please uninstall them and test whether your problem still occurs.
> UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video
> system:
> distro: Ubuntu
> codename: maverick
> architecture: x86_64
> kernel: 2.6.35-22-generic
>
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/650539/+subscribe
>

[Ashley (lifenstein)]

Multi-monitor (one ext monitor connected to laptop) , Separate X Screens, Xinerama Enabled.

X restarts when moving the mouse over the window.

[kion (kion-inbox)]

Updated from 10.04 to 10.10.

Multi-monitor (namely, two monitors), Separate X Screens, Xinerama Enabled. X restarts when moving the mouse over the window. No matter what desktop environment is used - crashes in any case (i have tried KDE/GNOME/Xfce/WindowMaker).

X does not crash, though, if I login using "Safe Mode".

[Antoni Aloy (antoni-aloy-gmail)]

Same for me with 10.10, nvidia driver (latest) with Xinerama. Applications like keepassx, vlc and skype crash X.

[MikeB (mikeb-timetrex)]

10.10 with Nvidia, KDE and three montior setup using Xinerama crashes for me as well. If I disable Xinerama I can get two monitors working with Twinview instead, but three monitors always crashes for me.

[Alejandro Cuervo (a-cuervo)]

Workarrounds for the meantime:

Dual monitors: Use twinview. There is no need to have xinerama enabled if you just have two monitors using twinview.
Besides with twinview you get hardware accelerated graphics.

Three monitors: Have two of them with twinview and one separate screen. All of them with xinerama disabled.

[MikeB (mikeb-timetrex)]

Thanks for the tips, that is basically what I'm doing right now, but
with KDE4.5 I can't figure out how to actually start apps on the 3rd
monitor (the one not using twinview). Nothing displays on that monitor
except the mouse cursor. (no taskbar, right click menu or anything)

I'm almost thinking KDE doesn't support this.

Thanks.

On Mon, 11 Oct 2010 17:25:44 -0000
Alejandro Cuervo <email address hidden> wrote:

>
> Workarrounds for the meantime:
>
> Dual monitors: Use twinview. There is no need to have xinerama enabled if you just have two monitors using twinview.
> Besides with twinview you get hardware accelerated graphics.
>
> Three monitors: Have two of them with twinview and one separate screen.
> All of them with xinerama disabled.
>

--
Mike Benoit
TimeTrex
Tel: [phone] Ext: 790
http://www.TimeTrex.com

[Daniel Dadap (ddadap)]

Just set the DISPLAY variable to your third display's X screen.

Example, if your third display is screen :0.1:

DISPLAY=:0.1 xterm

[MikeB (mikeb-timetrex)]

This works (xterm loads on the 3rd monitor), however KDE doesn't appear
to be running on the 3rd monitor, so there is essentially no window
manager, making it pretty useless. :(

From what I can obtain from Google, KDE4+ doesn't support separate X
displays like this. I attempted to use the script at the bottom of this
forum post:

http://forum.kde.org/viewtopic.php?f=66&t=12180&start=30

However it pops up a message saying KDE is already running on this (the
3rd) display, but I see no task bar or window decorations/title bars
whatsoever.

On Mon, 11 Oct 2010 18:04:27 -0000
Daniel Dadap <email address hidden> wrote:

> Just set the DISPLAY variable to your third display's X screen.
>
> Example, if your third display is screen :0.1:
>
> DISPLAY=:0.1 xterm
>

--
Mike Benoit
TimeTrex
Tel: [phone] Ext: 790
http://www.TimeTrex.com

[Obi1Kenobi (hatespam00-bugrep)]

Maybe I am doing something wrong but ... in my nvidia-settings the TwinView option is grayed out. And always has been with all nvidia drivers I used. I have even tried to enable it manually on the xorg.conf file but again to no avail.

In my case I have 2 PCI-E video cards and each monitor is hooked to a different card (rather than one card with dual connectors) - does that have anything to do with TwinView being unavailable ? Is such a setup not supported by TwinView ?

On Mon, 11 Oct 2010 17:25:44 -0000
Alejandro Cuervo <email address hidden> wrote:

>
> Workarrounds for the meantime:
>
> Dual monitors: Use twinview. There is no need to have xinerama enabled if you just have two monitors using twinview.

[Daniel Dadap (ddadap)]

TwinView is only supported when two displays are used on one GPU.

[Obi1Kenobi (hatespam00-bugrep)]

Thanks for clarifying that part Daniel.

Then Alejandro, unfortunately the workaround will not work for me and TwinView is not a always **the** option for dual head. I must use Xinerama.

It worked fine, no problem, albeit a little slow at (many) times with Kubuntu 10.04 though ... I need this dual head functionality so badly that I am a breadth away from putting back 10.04.

[nomad42184 (rob-patro)]

I can also verify this issue. My triple monitor setup using Xinerama was working perfectly using the most recent Nvidia drivers under 10.04. Upon the upgrade to 10.10, I started receiving the segfault when starting X. Disabling Xinerama allows me to run X, but is not a long term solution. Likewise, using TwinView is not an option for me as the two 20.1" monitors connected to one video card are separated by a 30" monitor connected to the other (which requires full use of the other video card for dual-link DVI). The only real solution for creating a single, uninterrupted, physical desktop is Xinerama. Any idea if this issue is currently being explored upstream?

[Laurent (syrius-no-log)]

Hi there.

I've got a 4 screens (2 quadro nvs 285) setup (2 twinview + xinerama)
I'm able to reproduce this by running emacs22-gtk (or emacs23-gtk). AFAIK emacs23-gtk is not linked to qt ! :-)

My workaround is to use lucid packages for xserver-xorg-core, xserver-xorg, xserver-xorg-input-evdev and nvidia.
It's kind of working with this workaround.
kinda because my X server freezes every weeks or so. The cursor gets stuck between the 2 twinview screens with X using 100% of a cpu. (have to kill -9 to restart...)

[alfille (paul-alfille)]

Nomad42184 asked if the Xinerama problem is being "explored upstream"?

Bug 6450599 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/650599

I reported be experience with nVidia. They confirm the bug, but says it's an Ubuntu-only problem and closed the bug report.

They claim that Arch-linux doesn't have the same issue.

My advice is to pester nVidia.
http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=44

I don't think they realise what a big deal this issue is.

[ExtremeMultiman (extrememultiman)]

Since it happens even with nouveau drivers and old nvidia drivers and only in Xinerama that's probably a problem of xinerama mode itself with some nvidia card instruction, not of nvidia binary drivers.
Using twinview is only a temprorary solution since some have dualhead on different GPUs or Trial Heads.

[MikeB (mikeb-timetrex)]

The cursor getting stuck between the two screens (using Xinerama for
me) and using 100% CPU was one of the main reasons I attempted to
upgrade to Ubuntu 10.10. Unfortunately that didn't work so well. :(

On Tue, 12 Oct 2010 11:35:28 -0000
Laurent <email address hidden> wrote:

> My workaround is to use lucid packages for xserver-xorg-core, xserver-xorg, xserver-xorg-input-evdev and nvidia.
> It's kind of working with this workaround.
> kinda because my X server freezes every weeks or so. The cursor gets stuck between the 2 twinview screens with X using 100% of a cpu. (have to kill -9 to restart...)
>

--
Mike Benoit
TimeTrex
Tel: [phone] Ext: 790
http://www.TimeTrex.com

[Jean-Paul Argudo (jean-paul-argudo)]

Same problem here, experienced today

DISPLAY=:0.1 xterm ... was working, but I tried with firefox (instead of xterm), since its my usage for 2nd screen (FF visible in all desktops): crashed X

I then decided to not use screen1 anymore. Then in the morning, while I was scrolling in FF helding the vertical bar, the mouse pointer got stuck between the two screens (exactly as MikeB), X was 100% CPU. Had to kill it remotely.

At lunch break, I "xlock"-ed my screen as allways, when back, the load was 40+, with tons of "kscreenlock" spawned, one each minute since lock screens mode are just changing each minute. Had to kill everything again remotely.

Finaly, I ripped of any Screen1 or Device1 or Monitor1 in my xorg.conf, then the 2nd monitor is completely inactive and unconsidered.

Since then, everything works fine, except my second monitor is off :/

Hope this helps.

I have some log files of everything here, I can send it,if it is of any use.

Thanks,

[Jared Bunting (jared-bunting)]

I've put the patched version in a PPA (maverick only) if anyone's interested.

https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539

[dzs (dzsabor)]

off

Actually, this bug gave me something new :-o
I have a TV connected to my GeForce 9500 GT's secondary and so far I've used a multi screen config with xinerama, where KDE turned off composite. Because of this bug I had to turn off xinerama, so I cannot drag windows between the screens anymore, but hey, I didn't do that much so far anyway, I don't miss it (almost) at all. And now, composite works :)

Does anybody know how to keep composite working after I re-enable xinerama some time when the fix gets to the repo?
(and where shall I get to the hell with my off question? :) )

/off

[Carlos Moffat (carlos-eldiabloenlosdetalles)]

@dzs:

I have to use Xinerama b/c TwinView doesn't allow to rotate only one monitor. But I believe Xinerama+Composite doesn't work either. So you have to choose what you need more/will miss less!

Cheers.

[Bluchris (christoph-thiery)]

Thank you very much Jared Bunting!
I 've installed how you wrote and it seems to work super with xinerama!!!

Greatings,
Christoph Thiery

Am 19.11.2010 20:37, schrieb Jared Bunting:
> I've put the patched version in a PPA (maverick only) if anyone's
> interested.
>
> https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539
>

[William King (quentusrex)]

It appears like this bug effects everyone who has Xinerama enabled and starts any QT application. From the comments it also appears there is a patch for xserver-xorg 1.9.0, but Maverick only uses 1.7.5.

So my question is: Is there any work on backporting the patch to xserver-xorg 1.7.5 so that a new build with the fix can be released to everyone with 10.10? We are looking at about 5 months away from an upgrade to 11.04, and this is a major bug for anyone using Xinerama.

[Jared Bunting (jared-bunting)]

William King:

From what I was able to accomplish, I think there's some confusion here.

The relevant package isn't xserver-xorg (which, after closer inspection is actually version 1:7.5) but xserver-xorg-core (and related packages, which come from source package xorg-server (confusing, I know)). Applying the patch (that's already been provided upstream, http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d) to the xorg-server package, compiling, and installing the resultant packages from that that I needed (nowhere near all of them) fixed the problem for me.

As a convenience to anyone else having this problem, I've put my patched package in a PPA. Please feel free to use it, as I think it will resolve your problems.

https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539

[Jérôme (kibohely)]

Still not working for me, i try :

- rebuild and patch the packages by myself;
- jared's packages;

It still crash .. and I'm a special "case" because i don't even use
Xinerama..

My config :

Sony Vaio Z12 / NVIDIA 350 / 1600 x 900 / Maeverick up-to-date ..

Maybe the bug is somewhere else, and the first one with xinerama only
trigger it ?

Cheers,

Jérôme

On Fri, Nov 19, 2010 at 11:41 PM, Jared Bunting <<email address hidden>
> wrote:

> William King:
>
> >From what I was able to accomplish, I think there's some confusion here.
>
> The relevant package isn't xserver-xorg (which, after closer inspection
> is actually version 1:7.5) but xserver-xorg-core (and related packages,
> which come from source package xorg-server (confusing, I know)).
> Applying the patch (that's already been provided upstream,
>
> http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d
> )
> to the xorg-server package, compiling, and installing the resultant
> packages from that that I needed (nowhere near all of them) fixed the
> problem for me.
>
> As a convenience to anyone else having this problem, I've put my patched
> package in a PPA. Please feel free to use it, as I think it will
> resolve your problems.
>
> https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539
>
> --
> Launching QT apps under Xinerama crashes Xorg : affects SpeedCrunch,
> KeePassX, Lucky Backup, Pencil, Stellarium, Skype, Google Earth, VLC,
> Konqueror, VirtualBox, Opera ...
> https://bugs.launchpad.net/bugs/650539
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.Org X server: Unknown
> Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid
> Status in “qt4-x11” package in Ubuntu: Invalid
> Status in “xorg” package in Ubuntu: Triaged
> Status in “nvidia-graphics-drivers” source package in Maverick: Invalid
> Status in “qt4-x11” source package in Maverick: Invalid
> Status in “xorg” source package in Maverick: Triaged
>
> Bug description:
> I think this may be related to QT apps, as keepassx, skype also crash X
> when started
> This is on maverick will all current updates.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: speedcrunch 0.10.1-2
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic x86_64
> NonfreeKernelModules: nvidia
> Architecture: amd64
> Date: Tue Sep 28 12:29:04 2010
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: speedcrunch
> ---
> Architecture: amd64
> DistroRelease: Ubuntu 10.10
> InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
> NonfreeKernelModules: nvidia
> Package: xorg 1:7.5+6ubuntu3
> PackageArchitecture: amd64
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Tags: maverick
> Uname: Linux 2.6.35-22-generic x86_64
> UnreportableReason: The drivers from nvidia.com are not supported by
> Ubuntu. Please uninstall them and test whether your problem still occurs.
> UserGroups: adm admin cdrom dialout lpadmin...

[Ian! D. Allen (idallen)]

I followed the source-building and editing steps in #95 "JMason wrote on 2010-10-23" and I finally have an Xorg that doesn't crash.

Linux ian 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64 GNU/Linux

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 10.10
Release: 10.10
Codename: maverick

Finally - this has been a problem for over a month now.

[Alberto Milone (albertomilone)]

Requesting an SRU.

I've already uploaded the package with the patch in maverick-proposed and it's waiting for approval.

The rationale for this SRU is available in the bug description.

[Martin Pitt (pitti)]

Accepted xorg-server into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

[Mauro (mauroma)]

Hi,
I've installed all maverik-proposed but I still have the problem

here is my .xsession-errors

/etc/gdm/Xsession: Beginning session setup...
export DESKTOP_SESSION='gnome'
export DISPLAY=':0'
export GDMSESSION='gnome'
export GDM_KEYBOARD_LAYOUT='it'
export GDM_LANG='it_IT.utf8'
export GNOME_KEYRING_CONTROL='/tmp/keyring-294sin'
export GNOME_KEYRING_PID='20199'
export HOME='/home/mmazza'
export JAVA_HOME='/home/mmazza/XMauro/Programs/jdk1.6.0_14'
export LANG='it_IT.utf8'
export LANGUAGE='it_IT:it:en_GB:en'
export LD_LIBRARY_PATH='/home/mmazza/XMauro/Programs/instantclient_11_1'
export LOGNAME='mmazza'
export ORACLE_HOME='/home/mmazza/XMauro/Programs/instantclient_11_1'
export PATH='/home/mmazza/XMauro/Programs/jdk1.6.0_14/bin:/home/mmazza/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games'
export PWD='/home/mmazza'
export SHELL='/bin/bash'
export SPEECHD_PORT='7560'
export USER='mmazza'
export USERNAME='mmazza'
export WINDOWPATH='8'
export XAUTHORITY='/var/run/gdm/auth-for-mmazza-CDcqjY/database'
export XDG_SESSION_COOKIE='192f319259574f9c0c31e7134a133252-1290591945.219999-1121441382'
export http_proxy='http://proxy:8080/'
MainThread 2010/11/24 10:45:45.8710 (sabayon-apply): No profile for user 'mmazza' found
Non è stato trovato alcun profilo per l'utente «mmazza»
MainThread 2010/11/24 10:45:45.8711 (sabayon-apply): Fatal exception! Exiting abnormally.
MainThread 2010/11/24 10:45:45.8713 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 149, in <module>
    sys.exit (util.EXIT_CODE_NO_USER_PROFILE)
SystemExit: 3

===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) =====
MainThread 2010/11/24 10:45:45.8710 (sabayon-apply): No profile for user 'mmazza' found
MainThread 2010/11/24 10:45:45.8711 (sabayon-apply): Fatal exception! Exiting abnormally.
MainThread 2010/11/24 10:45:45.8713 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 149, in <module>
    sys.exit (util.EXIT_CODE_NO_USER_PROFILE)
SystemExit: 3

===== END MILESTONES (/usr/sbin/sabayon-apply) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) =====
MainThread 2010/11/24 10:45:45.8710 (sabayon-apply): No profile for user 'mmazza' found
MainThread 2010/11/24 10:45:45.8711 (sabayon-apply): Fatal exception! Exiting abnormally.
MainThread 2010/11/24 10:45:45.8713 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 149, in <module>
    sys.exit (util.EXIT_CODE_NO_USER_PROFILE)
SystemExit: 3

===== END RING BUFFER (/usr/sbin/sabayon-apply) =====

This configuration for the debug log can be re-created
by putting the following in ~//etc/sabayon/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
Setting IM through im-switch for locale=it_IT.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
GNOME_KEYRING_CONTROL=/tmp/keyring-294sin
SSH_AUTH_SOCK=/tmp/keyring-294sin/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-294sin
SSH_AUTH_SOCK=/tmp/keyring-294sin/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-294sin
SSH_AUTH_SOCK=/tmp/keyring-294sin/ssh
** (<unknown>:20301): DEBUG: Client r...

[Eric Hough (k2eric)]

The xorg-server package from maverick-proposed works!

ii xorg 1:7.5+6+xserver1.9
ii xserver-xorg 1:7.5+6+xserver1.9
ii xserver-xorg-core 2:1.9.2.901+git20101115+server-1.9-branch.201273a2-0ubuntu0sarvatt2~maverick

[Kenny (asmig+dalahucpn)]

Installing xserver-xorg-core and xserver-common from maverick-proposed resolved this issue for me.

x86_64
Four monitors, two rotated, Xinerama.

xorg 1:7.5+6ubuntu3
xserver-common 2:1.9.0-0ubuntu7.1
xserver-xorg 1:7.5+6ubuntu3
xserver-xorg-core 2:1.9.0-0ubuntu7.1

Thanks!

[Jared Bunting (jared-bunting)]

maverick-proposed works for me.

[Alberto Milone (albertomilone)]

@Mauro
Please post the output of the following command
apt-cache policy xserver-xorg-core

[Mauro (mauroma)]

sure, here is the output

mmazza@mmazza:~$ apt-cache policy xserver-xorg-core
xserver-xorg-core:
  Installato: 2:1.9.0-0ubuntu7.1
  Candidato: 2:1.9.0-0ubuntu7.1
  Tabella versione:
 *** 2:1.9.0-0ubuntu7.1 0
        500 http://ubuntu.fastbull.org/ubuntu/ maverick-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     2:1.9.0-0ubuntu7 0
        500 http://ubuntu.fastbull.org/ubuntu/ maverick/main i386 Packages
N: Ignoring file 'apt-build' in directory '/etc/apt/sources.list.d/' as it has no filename extension

[Mauro (mauroma)]

I noticed I've got the problem both using xinerama or twinview,
the problem comes after I upgraded from 10.04 to 10.10
thanks in advance
mauro

[Jérôme (kibohely)]

as Mauro, I still have the problem :

- Sony Vaio z series;
- Ubuntu 10.10 64bits
- Nvidia Geforce GT 330
- last NVIDIA driver

I only use one screen, and if I use the intel card (my laptop have two, but
only one at once is activated), I don't have the issue...

On Thu, Nov 25, 2010 at 11:13 PM, Martin Pitt <email address hidden>wrote:

> ** Tags added: verification-done
> ** Tags removed: verification-needed
>
> --
> SRU: Launching a Qt app crashes X when using Xinerama
> https://bugs.launchpad.net/bugs/650539
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.Org X server: Unknown
> Status in “nvidia-graphics-drivers” package in Ubuntu: Invalid
> Status in “qt4-x11” package in Ubuntu: Invalid
> Status in “xorg-server” package in Ubuntu: Fix Committed
> Status in “nvidia-graphics-drivers” source package in Maverick: Invalid
> Status in “qt4-x11” source package in Maverick: Invalid
> Status in “xorg-server” source package in Maverick: Fix Committed
>
> Bug description:
> Justification:
> =============
> Regression from Ubuntu 10.04, causing an Xserver crash when starting a Qt
> application in an multi-head X configuration using Xinerama. The X crash
> risks losing user data from unsaved documents in applications.
>
> Fix:
> ===
> This is caused by a typo in commit 80b5d3a3. A fix has been pulled to the
> server-1.9 stable branch in commit 3effb61e (
> http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d). This commit has been cherry-picked onto the Natty xserver tree.
>
> Test case:
> ========
> Start a Qt app such as Skype while using Xinerama multi-head. Users of the
> binary nVidia driver who have multiple monitors and select “Separate X
> screen” rather than “Twinview” in nvidia-settings will be using a Xinerama
> multi-head configuration.
>
> Regression Potential:
> ==================
> Low. Patch is a one-line typo fix, and anything which exercises this
> codepath currently crashes.
>
>
> Original report:
>
> PROBLEM
> =======
> Starting a Qt app such as Skype crashes X, leaving
> "Caught signal 11 (Segmentation fault). Server aborting"
> in Xorg.0.log.old and the dazzled user with the login screen.
> This is a bug in X, fixed upstream in
> http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d.
>
> WORKAROUND
> ==========
> Until the fix is released as an official Ubuntu update, Jared Bunting has
> it in his PPA at
> https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539 (thx!).
> You need xserver-xorg-core and xserver-common, so for 32 bit
> 1) Download
>
> https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539/+files/xserver-xorg-core_1.9.0-0ubuntu7%2Bbug650539%2B1_i386.deband
>
> https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539/+files/xserver-common_1.9.0-0ubuntu7%2Bbug650539%2B1_all.deb
> 2) Install
> sudo dpkg -i xserver-xorg-core_1.9.0-0ubuntu7+bug650539+1_i386.deb
> xserver-common_1.9.0-0ubuntu7+bug650539+1_all.deb
>
> ORIGINAL DESCRIPTION
> ====================
> I think this may be related to QT apps, as keepassx, skype also crash X
> when started
> This...

[Chris Halse Rogers (raof)]

Exactly what problem are you seeing?

If you've got problems in a single monitor setup then you'll be
triggering a different bug. Please feel free to file a new bug so we
can start to figure out the cause of your problem.

[Bryce Harrington (bryce)]

Regression found to be associated with this change: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/680811

[Fabian Alenius (fabian-alenius)]

Installing xserver-xorg-core and xserver-common from maverick-proposed resolved this issue for me.

I have an ati mobility card with an external monitor that I'm using Xinerama with. I'm using the fglrx driver.

[Robert Fleming (fleming)]

> Exactly what problem are you seeing?
>
> If you've got problems in a single monitor setup then you'll be
> triggering a different bug. Please feel free to file a new bug so we
> can start to figure out the cause of your problem.

I'm seeing the same problem as Jérôme and Mauro. I have exactly one NVIDIA display adapter, using the proprietary driver (version 173 and "current" both exhibit the problem), and the adapter is attached to exactly one monitor. Emacs, rxvt, VLC, and xawtv crash the server. Here is the Xorg output:

  Backtrace:
  0: X (xorg_backtrace+0x3b) [0x80e82fb]
  1: X (0x8048000+0x5da8d) [0x80a5a8d]
  2: (vdso) (__kernel_rt_sigreturn+0x0) [0x13e40c]
  3: X (ProcessWorkQueue+0x30) [0x8073a60]
  4: X (WaitForSomething+0x56) [0x809fc06]
  5: X (0x8048000+0x25d3e) [0x806dd3e]
  6: X (0x8048000+0x1a5ba) [0x80625ba]
  7: /lib/libc.so.6 (__libc_start_main+0xe7) [0xd3ace7]
  8: X (0x8048000+0x1a191) [0x8062191]
  Segmentation fault at address (nil)

  Caught signal 11 (Segmentation fault). Server aborting

I ran through half of the demos in the "qtdemo" package and none crashed the server. (I don't have all the KDE infrastructure installed, so I didn't test that.) The server does *not* crash when using the free-software NVIDIA driver.

I have not been able to disable the Xinerama extension either by putting 'Option "Xinerama" "0"' in the "ServerLayout" sections, or by using the "-xinerama" command-line argument to /usr/bin/Xorg. I've read that the NVIDIA driver forces it on or something.

So our bug is probably not this one, would you agree? I couldn't find a report for our bug.

[Robert Fleming (fleming)]

Sorry for the spam, I've filed bug 683016 to cover my last comment.

[mustangtyson (tysonsmith)]

I enabled "proposed" updated, rebooted and it solved the problem. Thanks!
http://ubuntuforums.org/showthread.php?p=10268993#post10268993

[MBeale (malcolm-beale-yahoo)]

Yes, works for me on triple monitor Nvidia SLI setup, thanks, hope it becomes official.
For those left wondering just run Synaptic Package Manager -> Settings -> Repositories.In the Software Sources dialog box select the Updates tab.Check the Pre-released updates (maverick-proposed) box.Run update-manager, restart and your'e done.
--- On Thu, 23/12/10, mustangtyson <email address hidden> wrote:

From: mustangtyson <email address hidden>
Subject: [Bug 650539] Re: SRU: Launching a Qt app crashes X when using Xinerama
To: <email address hidden>
Received: Thursday, 23 December, 2010, 6:09 AM

I enabled "proposed" updated, rebooted and it solved the problem. Thanks!
http://ubuntuforums.org/showthread.php?p=10268993#post10268993

--
You received this bug notification because you are a direct subscriber
of a duplicate bug (659538).
https://bugs.launchpad.net/bugs/650539

Title:
  SRU: Launching a Qt app crashes X when using Xinerama

Status in X.Org X server:
  Unknown
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Invalid
Status in “qt4-x11” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers” source package in Maverick:
  Invalid
Status in “qt4-x11” source package in Maverick:
  Invalid
Status in “xorg-server” source package in Maverick:
  Fix Committed

Bug description:
  Justification:
=============
Regression from Ubuntu 10.04, causing an Xserver crash when starting a Qt application in an multi-head X configuration using Xinerama.  The X crash risks losing user data from unsaved documents in applications.

Fix:
===
This is caused by a typo in commit 80b5d3a3.  A fix has been pulled to the server-1.9 stable branch in commit 3effb61e (http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d ).  This commit has been cherry-picked onto the Natty xserver tree.

Test case:
========
Start a Qt app such as Skype while using Xinerama multi-head.  Users of the binary nVidia driver who have multiple monitors and select “Separate X screen” rather than “Twinview” in nvidia-settings will be using a Xinerama multi-head configuration.

Regression Potential:
==================
Low.  Patch is a one-line typo fix, and anything which exercises this codepath currently crashes.

Original report:

PROBLEM
=======
Starting a Qt app such as Skype crashes X, leaving
"Caught signal 11 (Segmentation fault). Server aborting"
in Xorg.0.log.old and the dazzled user with the login screen.
This is a bug in X, fixed upstream in http://cgit.freedesktop.org/xorg/xserver/commit/?id=78f94f19aab66a1e5331df0ce29f36e310b4195d .

WORKAROUND
==========
Until the fix is released as an official Ubuntu update, Jared Bunting has it in his PPA at https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539 (thx!).
You need xserver-xorg-core and xserver-common, so for 32 bit
1) Download
https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539/+files/xserver-xorg-core_1.9.0-0ubuntu7%2Bbug650539%2B1_i386.deb and
https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539/+files/xserver-common_1.9.0-0ubuntu7%2Bbug650539%2B1_all.deb
2) Install
sudo d...

[Martin Pitt (pitti)]

As discussed with Bryce, the reported regression is still very dubious and the benefit of this patch is very high, so we'll get it into -updates now.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xorg-server - 2:1.9.0-0ubuntu7.1

---------------
xorg-server (2:1.9.0-0ubuntu7.1) maverick-proposed; urgency=low

  * debian/patches/207_Xext_panoramiXprocs_fix_typo.patch:
    - This prevents Qt applications from crashing when using
      Xinerama multi-head with drivers such as nvidia (LP: #650539).
 -- Alberto Milone <email address hidden> Mon, 22 Nov 2010 18:55:50 +0100

[Ashley Yakeley (ashley-semantic)]

Not fixed for me. This is with 2:1.9.0-0ubuntu7.1, but also not fixed with 7.3.

[Scott Money (scott-money)]

I am still seeing this issue in 2:1.9.0-oubuntu7.3 using the NVIDIA driver version NVIDIA-Linux-x86-260.19.12 or NVIDIA-Linux-x86-260.19.29

[Harry Flink (to-harryflink-from-launchpad)]

> I am still seeing this issue in 2:1.9.0-oubuntu7.3 using the NVIDIA
> driver version NVIDIA-Linux-x86-260.19.12 or NVIDIA-Linux-x86-260.19.29

No wonder. I verified the issue exists still by doing this:
$ apt-get source xserver-common
$ zgrep -A2 -B2 650539 xorg-xserver_1.9.0-0ubuntu7.3.diff.gz
+ * debian/patches/207_Xext_panoramiXprocs_fix_typo.patch:
+ - This prevents Qt applications from crashing when using
+ Xinerama multi-head with drivers such as nvidia (LP: #650539).
+
+ -- Alberto Milone <email address hidden> Mon, 22 Nov 2010 18:55:50 +0100

So it is reported to be fixed in the change log.

$ grep -A4 "pDst == screenInfo" xorg-xserver-1.9.0/Xext/panoramiXprocs.c
    if((pDst == screenInfo.screens[0]->root) ||
       (pWin->drawable.id == screenInfo.screens[0]->screensaver.wid))
    {
        rep.dstX += screenInfo.screens[0]->x;
        rep.dstY += screenInfo.screens[0]->y;

So if compared to the original patch (https://launchpad.net/~jared-bunting/+archive/xorg-xserver-650539), it is not fixed, only falsely reported to be fixed.

I'd really liked to see this fix included soon and before next Ubuntu is released. Althought I'm sure the history still continues to repeat itself and this will not get fixed before Ubuntu 11.04. Then the Ubuntu 11.04 version will break the multimonitor setup of Xorg (or something related) again and the fixing takes again more than releasing even next Ubuntu 11.10 and so on. That's the neverending cycle that have been past i-cannot-even-remember-how-many Ubuntus. I guess it's just so rare to use multimonitor setup that they don't test it before release.

[Fjodor (sune-molgaard)]

Neither fixed in 7.3 nor in packages from xorg-edgers for me. Could some of us be seeing a different problem with the same symptoms?

[Perry Hung (iperry)]

I've tried Jared's PPA, the packages from maverick proposed, 1.9.0ubuntu7.3, as well as rebuilding it from source and making sure the patch was in there, and none of them fixed the issue for me.

nvidia GTX 260. I've tried nvidia-current, as well as proprietary drivers 260.19.21

[Ashley Yakeley (ashley-semantic)]

The fix didn't make it into 7.3, as Harry Flink discovered by source inspection, and many others through using the package. Could this bug be re-opened, please?

[Harry Flink (to-harryflink-from-launchpad)]

It's been almost three weeks since my post. Any chance this issue could get fixed soon?

After all the patch exists already so there's not much to do but to apply and release it. This is easily solved but very important to us because Xorg seem to update every now and then and when updated everyone has to patch the new version.

[Ashley Yakeley (ashley-semantic)]

Since it's not possible to reopen a bug in "Fix Released" state, I created a new bug. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/738526

[Chris Halse Rogers (raof)]

The patch *is* applied to the 1.9.0-0ubuntu7.3 package, as you can see in the .diff.gz on launchpad. I suspect that Harry's grep was done from an unpacked source tree before running “quilt push -a” (or ‘debian/rules patch’).

If you're still seeing crashes, you're seeing a *different* crash.

[Ashley Yakeley (ashley-semantic)]

If you're still seeing crashes, try uninstalling xfs.

sudo apt-get remove xfs

[Alkalyzer (alkalyzer)]

It seems that this bug just recently occurred to me after a kernel update.
I am running Natty (64 bits) with the nvidia drivers from the repositories (280.13). Everything worked fine until the yesterday update to kernel 2.6.38-11, then all QT applications produced a segmentation fault and sent me back to gdm.
Removing "xfs" solved this issue.

[borillionstar (babakrezai)]

Im not running Xinerama as far as I know.
Backtrace:
[ 17148.125] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]
[ 17148.125] 1: /usr/bin/X (0x400000+0x64b7a) [0x464b7a]
[ 17148.125] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f57571d5000+0x10060) [0x7f57571e5060]
[ 17148.126] 3: /usr/bin/X (doListFontsWithInfo+0x16a) [0x43061a]
[ 17148.126] 4: /usr/bin/X (ProcessWorkQueue+0x21) [0x433d51]
[ 17148.126] 5: /usr/bin/X (WaitForSomething+0x65) [0x45dec5]
[ 17148.126] 6: /usr/bin/X (0x400000+0x2f912) [0x42f912]
[ 17148.126] 7: /usr/bin/X (0x400000+0x232fe) [0x4232fe]
[ 17148.126] 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f575611130d]
[ 17148.126] 9: /usr/bin/X (0x400000+0x235ed) [0x4235ed]
[ 17148.126] Segmentation fault at address 0xf79a7f60
[ 17148.126]
Caught signal 11 (Segmentation fault). Server aborting
[ 17148.126]
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.

[wayward4now (wayward4now)]

bump?