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
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.
--
[M56GL] /etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://bugs.launchpad.net/bugs/245896
You received this bug
** Summary changed:
- /etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
+ [M56GL] /etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
--
[M56GL] /etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://bugs.launchpad.net/bugs/245896
You received this bug
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
** Changed in: fglrx-installer (Ubuntu)
Status:
