crash of Xorg using xrandr

[Martin Nowack]

After login into kde 4.1.1 I try to xrandr to change the resolution of a second screen.

The result is Xorg crashes often (>70%) not always and I'm back to the login screen.

The xorg.0.log showed following backtrace:

0: /usr/bin/X(xf86SigHandler+0x79) [0x80c3069]
1: [0xb7f04400]
2: /usr/lib/dri/r300_dri.so(__driUtilUpdateDrawableInfo+0xc1) [0xad5034a1]
3: /usr/lib/dri/r300_dri.so(radeonGetLock+0x75) [0xad50a0a5]
4: /usr/lib/dri/r300_dri.so(r300FlushCmdBuf+0xd0) [0xad515dd0]
5: /usr/lib/dri/r300_dri.so(r300DestroyContext+0x433) [0xad50fac3]
6: /usr/lib/dri/r300_dri.so [0xad507578]
7: /usr/lib/dri/r300_dri.so [0xad503357]
8: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a66c29]
9: /usr/lib/xorg/modules/extensions//libglx.so(__glXFreeContext+0x89) [0xb7a5b9d9]
10: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a5ba27]
11: /usr/bin/X(FreeResourceByType+0xe2) [0x8073ce2]
12: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a57cf7]
13: /usr/lib/xorg/modules/extensions//libglx.so [0xb7a5bd8a]
14: /usr/bin/X(Dispatch+0x34f) [0x808c91f]
15: /usr/bin/X(main+0x47d) [0x8071d8d]
16: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b1c685]
17: /usr/bin/X [0x8071171]
Saw signal 11. Server aborting.

Graphic card: ati x1400 using radeon driver with dri enabled.

Actual packages on Kubuntu Intrepid:

xorg: 7.4~2ubuntu4
libgl1-mesa-glx: 7.1-1ubuntu3

If you need informations I will provide them.

[wired (wired-wired-things)]

I have a similar problem. I am using Kubuntu Intrepid on a IBM Thinkpad T42p with ATI FireGL MobilityT2 video card. I also use the opensource driver, in my case the radeon module gets loaded.

Only difference is that using xrandr to enable dual-monitor setup with my external display with

xrandr --output DVI-0 --auto --above LVDS

freezes the complete machine. Only option is to switch off via the power button and reboot. This also roughly happens in 70% of the cases, I try to do it. I have found no backtrace in my xorg.log but I will attach it nevertheless. However, I noticed, that if I kill plasma with

killall -9 plasma

before using xrandr the external display gets activated correctly. Afterward I just reload plasma from the terminal and everything works fine. So, I would guess that this problem might be related to plasma as well.

[Andrew Baumann (0xab)]

I have what I think is the same bug, on a Lenovo X301 with an Intel graphics controller. xrandr changes tend to crash about half to two thirds of the time.

Backtrace from Xorg.log when the crash happens:
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x65) [0x480f35]
1: /lib/libc.so.6 [0x7fbaf5669060]
2: /usr/lib/xorg/modules/extensions//libglx.so(__glXDeassociateContext+0x35) [0x7fbaf4b44375]
3: /usr/lib/xorg/modules/extensions//libglx.so(__glXContextDestroy+0xf) [0x7fbaf4b406ef]
4: /usr/lib/xorg/modules/extensions//libglx.so [0x7fbaf4b4c902]
5: /usr/lib/xorg/modules/extensions//libglx.so(__glXFreeContext+0x6c) [0x7fbaf4b428ac]
6: /usr/lib/xorg/modules/extensions//libglx.so [0x7fbaf4b428f3]
7: /usr/bin/X(FreeResourceByType+0x105) [0x435505]
8: /usr/lib/xorg/modules/extensions//libglx.so [0x7fbaf4b3f1fe]
9: /usr/lib/xorg/modules/extensions//libglx.so [0x7fbaf4b42bd2]
10: /usr/bin/X(Dispatch+0x364) [0x44d6e4]
11: /usr/bin/X(main+0x45d) [0x4336fd]
12: /lib/libc.so.6(__libc_start_main+0xe6) [0x7fbaf5654466]
13: /usr/bin/X [0x432ad9]
Saw signal 11. Server aborting.

The common culprit seems to be libglx.so, but this is part of xserver-xorg-core, so why is this bug filed against mesa?

[Tim Holy (holy-wustl)]

This happens for me, too, with Kubuntu Intrepid and with hardware described in the attached file (and as the first poster indicated,
ati x1400 using radeon driver with dri enabled).

This happens only when I have desktop effects turned on. I can reboot the machine with a ctrl-alt-delete; but note that restarting X with ctrl-alt-backspace does _not_ work.

[Tim Holy (holy-wustl)]

Here's my Xorg.0.log file.

[Timo Aaltonen (tjaalton)]

Tim: it contained the same backtrace as Martin had, so I deleted the attachment (it was over 60MB :)

[James Dunmore (james-dunmore)]

Same bug here:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/bin/X(ProcSetClipRectangles+0xc1) [0x808acb1]
4: /usr/bin/X(Dispatch+0x34f) [0x808c89f]
5: /usr/bin/X(main+0x47d) [0x8071d1d]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b4d685]
7: /usr/bin/X [0x8071101]
Saw signal 11. Server aborting.

I think it is related to Plasma, because when I try to resize a plasma wiget on the Deskop, X restarts.

Graphics card is (lspci):
00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller (rev 04)

Anyone any ideas, it's making intrepid kubuntu quite unusable

[Tim Holy (holy-wustl)]

On Wednesday 12 November 2008, James Dunmore wrote:
> Anyone any ideas, it's making intrepid kubuntu quite unusable

James, you probably have already discovered this, but a workaround is to turn
off desktop effects (K menu -> System Settings -> Desktop). You don't get any of
the fancy features, but it is more stable.

[James Dunmore (james-dunmore)]

Thanks - but I've already turned this off - it was the first thing I did.

However, I have a feeling that despite turning it off, there might be some residual config or something similar still in place?

I did try and mv .kde .kdeTemp (and re-start X ), but still having the problems :(

[Tim Holy (holy-wustl)]

OK, it seems like you might have a worse problem than I do---I have this
problem only (or at least much more often) when desktop effects are on.

FYI, I'm now running without an xorg.conf file. Perhaps if you are still using
your old one, it's got some setting that's causing trouble? If so, you might
want to consider renaming the file to something else and restarting X.

[James Dunmore (james-dunmore)]

I've deleted XORG - same issues

I've installed ubuntu-desktop - more stable, but same issues at the end of the day (random x crashes/restart when trying to do stuff like changing windows, resizing, etc.)

With GDM I get the following:
gdm[9168]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

Which is very similar to the KDM in syslog:

kdm[5021]: X server for display :0 terminated unexpectedly

Getting quite annoying.

If anyone would like logs, etc. please let me know ASAP, because it's getting to the stage where I'm going to have to re-install Hardy

Thanks.

[mumulox (mihaigabriel)]

Hello, I have the same problem. The xserver is crashing every 10 minutes or less. I run Ubuntu Intrepid. This is the log from xorg.log

II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): EDID vendor "QDS", prod id 17

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/lib/libpixman-1.so.0(pixman_region_subtract+0xb4) [0xb7e32174]
4: /usr/bin/X11/X(miSubtract+0x2b) [0x811cd4b]
5: /usr/lib/xorg/modules//libexa.so [0xb786c368]
6: /usr/lib/xorg/modules//libexa.so [0xb786cb39]
7: /usr/lib/xorg/modules//libexa.so(exaDoMigration+0x64a) [0xb786d2fa]
8: /usr/lib/xorg/modules//libexa.so [0xb7869e9b]
9: /usr/lib/xorg/modules//libexa.so [0xb786b5e2]
10: /usr/lib/xorg/modules//libexa.so [0xb786a16c]
11: /usr/bin/X11/X [0x8178708]
12: /usr/bin/X11/X(ProcPolySegment+0x100) [0x8089c60]
13: /usr/bin/X11/X(Dispatch+0x34f) [0x808c89f]
14: /usr/bin/X11/X(main+0x47d) [0x8071d1d]
15: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b02685]
16: /usr/bin/X11/X [0x8071101]
Saw signal 11. Server aborting.

[mumulox (mihaigabriel)]

I just downgraded the xserver and video driver to gutsy versions and now it`s ok

[Pasha (pashash)]

I see the same problem on my Thinkpad T60 when I my dock/undock scripts. Is it any progress with this issue.
I downgrade X and Mesa to ubuntu 8.04 and everything works perfect.

[Oibaf (oibaf)]

Is this still an issue with Ubuntu 9.10?

[Aaron Roydhouse (aaron-roydhouse)]

I saw this problem with Intrepid (9.04) on a Lenovo X301 with the Mobile Intel GMA 4500 MHD (integrated), but I haven't seen the problem since Jaunty (9.10). As a mobile laptop using I xrandr for different external screens and projectors a couple of times a day.

The Xrandr applet has its quirks in 9.10, like putting the new confirmation/roll-back dialogue under its own window, but it doesn't crash the X server for me any more, which is fabulous.

Following an xrandr change to a larger size a lot of applications can still act funny. Most notable is Firefox and Thunderbird, their auto-complete drop-list won't work expect inside the original (smaller) pre-xrandr screen size. Not sure if this is a ui toolkit issue or a missed/ignored screen size change notification. But presumably not related to this bug anyway.

Aaron.

[Andrew Baumann (0xab)]

I haven't seen any xrandr-related X crashes since the 9.10 upgrade.

[Julian Kalinowski (julakali)]

Well, i have.
Enabling the second output on my Thinkpad X60s results in a crash (Black screen/no output).
Can't even reboot the system with ctrl-alt-del.
When booting up with the second display plugged in already, it works, but i experienced a random crash yesterday (while the system is running stable without a second display), too.
Like said before, its working well without desktop effects.

[Oibaf (oibaf)]

Is this still an issue with Ubuntu 10.10 or later?

[Tim Holy (holy-wustl)]

In 10.10 neither KMS nor desktop effects work for me, so they are turned off. Given that, I have no problems changing resolution with xrandr.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[Oibaf (oibaf)]

No response after years, closing.