** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete => Confirmed
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://bugs.launchpad.net/bugs/245896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Description changed:
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
on Fri Jan 16 2009, Bryce Harrington 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.
> Ple
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 me
** Changed in: fglrx-installer (Ubuntu)
Assignee: Mario Limonciello (superm1) => (unassigned)
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://bugs.launchpad.net/bugs/245896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Why was this marked "Won't Fix" without further explanation? I have
confirmed that it happens on Intrepid!
** Changed in: fglrx-installer (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
Status: Won't Fix => New
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X
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!
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://b
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!
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://b
This needs to be reproduced on Intrepid. If you can reproduce there,
please reopen this bug.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Won't Fix
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://bugs.launchpad.net/bugs/245896
You received this bug noti
** Changed in: fglrx-installer (Ubuntu)
Sourcepackagename: xorg => fglrx-installer
--
/etc/init.d/gdm stop doesn't kill Xorg, leaves /tmp/.X0-lock
https://bugs.launchpad.net/bugs/245896
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
10 matches
Mail list logo
