No, Compiz is not enabled.
--
Resume fails with fglrx due to ASIC hang with dual-head configuration
https://bugs.launchpad.net/bugs/308964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Description changed:
Ubuntu Version: 8.10
xorg-driver-fglrx Version: 8.543
GFX Card: ATI Radeon Xpress 1250
Resume fails when using the attached xorg dual-head configuration
- without an external monitor connected. I have enable Randr 1.2 support
+ without an external monitor
Public bug reported:
Ubuntu Version: 8.10
xorg-driver-fglrx Version: 8.543
GFX Card: ATI Radeon Xpress 1250
Resume fails when using the attached xorg dual-head configuration
without an external monitor connected. I have enable Randr 1.2 support
with the following command because otherwise X
** Attachment added: xorg.conf
http://launchpadlibrarian.net/20496349/xorg.conf
--
Resume fails with fglrx due to ASIC hang with dual-head configuration
https://bugs.launchpad.net/bugs/308964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 308964 ***
https://bugs.launchpad.net/bugs/308964
** This bug has been marked a duplicate of bug 308964
Resume fails with fglrx due to ASIC hang with dual-head configuration
--
Resume fails with fglrx due to ASIC hang on Samsung R20
** Attachment added: lspci.log
http://launchpadlibrarian.net/20496380/lspci.log
--
Resume fails with fglrx due to ASIC hang with dual-head configuration
https://bugs.launchpad.net/bugs/308964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/20496406/Xorg.0.log
--
Resume fails with fglrx due to ASIC hang with dual-head configuration
https://bugs.launchpad.net/bugs/308964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: kern.log
http://launchpadlibrarian.net/20496375/kern.log
--
Resume fails with fglrx due to ASIC hang with dual-head configuration
https://bugs.launchpad.net/bugs/308964
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I can confirm this issue with ubuntu 8.10 (upgraded all the way from
7.04).
--
Screensaver just detects idle time on one screen
https://bugs.launchpad.net/bugs/87317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: kern.log
http://launchpadlibrarian.net/19427870/kern.log
--
Resume fails with fglrx due to ASIC hang on Samsung R20
https://bugs.launchpad.net/bugs/294713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Ubuntu Version: 8.10
xorg-driver-fglrx Version: 8.543
GFX Card: ATI Radeon Xpress 1250
After the latest security updates (2.6.27-7.14 - 2.6.27-7.16) resume
stopped working on my Samsung R20 notebook. The notebook suspends fine
but when trying to resume the screen just
** Attachment added: lspci.log
http://launchpadlibrarian.net/19427872/lspci.log
--
Resume fails with fglrx due to ASIC hang on Samsung R20
https://bugs.launchpad.net/bugs/294713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/19427883/Xorg.0.log
** Description changed:
Ubuntu Version: 8.10
xorg-driver-fglrx Version: 8.543
GFX Card: ATI Radeon Xpress 1250
After the latest security updates (2.6.27-7.14 - 2.6.27-7.16) resume
stopped working
** Description changed:
Ubuntu Version: 8.10
xorg-driver-fglrx Version: 8.543
GFX Card: ATI Radeon Xpress 1250
- After the latest security updates (2.6.27-7.14 - 2.6.27-7.16) resume
- stopped working on my Samsung R20 notebook. The notebook suspends fine
- but when trying to resume the
*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
** This bug has been marked a duplicate of bug 226279
Kernel 2.6.24-17 - broken resume from suspend to RAM
--
2.6.24-17 breaks suspend/resume
https://bugs.launchpad.net/bugs/226566
You received this bug
I can confirm this on my Samsung R20. Resume stopped working after the
upgrade to 2.6.24-17. Works fine with 2.6.24-16.
--
Kernel 2.6.24-17 - broken resume from suspend to RAM
https://bugs.launchpad.net/bugs/226279
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: hal.log
http://launchpadlibrarian.net/14342928/hal.log
--
Failed to intialize HAL error message after gdm login. possibly because of
wrong gdm priority in /etc/rc*/
https://bugs.launchpad.net/bugs/227838
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: gdm
After upgrades from Feisty to Gutsy and from Gutsy to Hardy I get an
error message after logging in with gdm (2.20.5-0ubuntu3) saying Failed
to initialize HAL but debugging HAL showed that it just comes up fine
(see attachment). These are the
In my case this bug is a consequence of this one:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/227838
Changing the priority of gdm in /etc/rc*/*gdm from 13 to 30 solved the
problem for me.
--
Network Manager does not automatically connect on login
https://bugs.launchpad.net/bugs/210346
Thanks! I've changed the level of gdm to 30 and everything's fine now.
I've created a new bug report against gdm which can be found at
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/227838
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification
I just ran into this problem after updating to hal 0.5.11~rc2-1ubuntu8
(which was supposed to fix this bug for some people if I got the
discussion right) on my Samung R20 running Hardy. Neither the subsequent
update to 0.5.11~rc2-1ubuntu8.1 nor the downgrade to 0.5.11~rc2-1ubuntu7
did help. After
** Attachment added: lshal.txt
http://launchpadlibrarian.net/14260858/lshal.txt
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Attachment added: kern.log
http://launchpadlibrarian.net/14260875/kern.log
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
changing the priority of hal in rc2.d from 24 to 13 seems to fix the
problem for me.
by the way, my upgrade history is feisty - gutsy - hardy.
--
Failed to initalize HAL.
https://bugs.launchpad.net/bugs/25931
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I can confirm this with my Hardy installation on my Samsung R20 laptop
(having a Atheros AR242x PCI Express Adapter).
--
Network Manager does not automatically connect on login
https://bugs.launchpad.net/bugs/210346
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm experiencing the same problem. IMHO the importance should be raised
from low to medium on this bug. For now I've hacked myself an
unsatisfying workaround:
http://cc.thammerl.interlinked.org/index.php/2008/01/13
/enablingdisabling-gnome-screensaver-with-a-custom-keyboard-shortcut/
**
*** This bug is a duplicate of bug 182063 ***
https://bugs.launchpad.net/bugs/182063
No boot hangs anymore when booting the gutsy kernel with hpet=disable.
There haven't been any system freezes either. Thanks for the suggestion,
Fil!
--
Random system freeze if multicore processing is
Using kernel 2.6.22-14 with kernel parameter acpi=off solved the boot
issue for me. For wifi support I need to pass noapic as well to the
kernel. With this configuration I don't experience any system freezes
anymore.
--
Random system freeze if multicore processing is enabled on Samsung R20 with
Updated my BIOS to the latest version (14SH). The system still randomly
freezes with kernel 2.6.20-16 if multicore processing is enabled. Kernel
2.6.22-14 takes very long to boot (~10 minutes) but wifi is working now
due to the latest update of linux-restricted-modules-generic. I haven't
Public bug reported:
I've installed Feisty on my Samsung R20 and experienced random system
freezes. Sometimes the freeze happens a few minutes after startup and
sometimes the system runs for a few hours without any problem until the
crash. The system halts and stays completely unresponsive. If
30 matches
Mail list logo
