[M56GL] /etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock

[DaveAbrahams]

Binary package hint: xserver-xorg

$ uname -a
Linux mcbain 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux

This is with all the latest updates, plus I am using the latest fglrx from ATI. I don't know whether this would happen with fglrx from the ubuntu repositories.

To kill my X server I need to do

/etc/init.d/gdm stop; killall -9 Xorg; rm /tmp/.X0-lock

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
     Subsystem: Lenovo Device [17aa:2015]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M56GL [Mobility FireGL V5200] [1002:71c4]
     Subsystem: Lenovo Device [17aa:2007]

[Mario Limonciello (superm1)]

This needs to be reproduced on Intrepid. If you can reproduce there, please reopen this bug.

[DaveAbrahams (boostpro)]

I confirm it still happens on intrepid.

Still, this is crazy. I reported this bug against Hardy, which is supposed to be LTS. The response should not be to ignore the report until it is reproduced in a different release!

[DaveAbrahams (boostpro)]

Why was this marked "Won't Fix" without further explanation? I have confirmed that it happens on Intrepid!

[Bryce Harrington (bryce)]

Hi boostpro,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

[DaveAbrahams (boostpro)]

on Fri Jan 16 2009, Bryce Harrington <bryce-AT-bryceharrington.org> wrote:

> Hi boostpro,
>
> Please attach the output of `lspci -vvnn`,
>
> and attach your /var/log/Xorg.0.log file
> from after reproducing this issue. If you've made any customizations to your
> /etc/X11/xorg.conf please attach that as well.

Done.

> Please attach the output of `lspci -vvnn` too.

Err, already done ;-)

--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

[Bryce Harrington (bryce)]

I've posted a new version of the -fglrx driver to our xorg-edgers PPA,
would you mind testing it either on Jaunty or Karmic and see if it
resolves this bug?

Get fglrx 8.620 here:

  https://edge.launchpad.net/~xorg-edgers/+archive/ppa

[DaveAbrahams (boostpro)]

I might, but...

Fair warning: I've switched my main machine to a Mac now so I'd really have to find some time on my hands to do any bleeding-edge linux testing.

[Bryce Harrington (bryce)]

Since the hardware is no longer available for doing troubleshooting with, we'll have to close the bug for now. However please feel free to reopen if you or anyone else has the same HW and can reproduce this issue using the latest development version of Ubuntu and is willing to do some troubleshooting with it.