Workarround:
export FORCE_ATI_UNINSTALL=/usr/share/ati and then try again. The
script seams to be unable to find the old drivers location.
--
package fglrx (not installed) failed to install/upgrade: subprocess new
pre-installation script returned error exit status 1 - inst_path_default or
the PPA gave back something similar to the 9.10-freeze bug.
Interesting like at the end of Xorg.0.log:
(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or
eben a frozen display: Input/output error.
...it decided to freeze.
--
[i855] Lucid Freeze shortly after X
Strange things:
- downgraded to 2.9 driver - it still behaved as the 2.11 driver (=freeze
after a while, can switch to console).
- back to vesa - got an error about a KMS driver being loaded (!).
- fix for this was to purge the intel driver and reinstall it. This also
restored the instant crash
I'm sure, this bug is _not_ fixed, esp. as I get exactly the problem
described by Rebug on 2009-07-23 with an intel 855 on the 9.10 final. It
doesn't crash at a predictable time but random somewhere when the
X-Server is fresh loaded. Changing to vesa is the only workarround.
--
[i845] karmic
Public bug reported:
Another way to crash Ghostscript :(
D [26/Mar/2009:11:24:39 +0100] [Job 1] Starting renderer with command: gs
-dFirstPage=1 -q -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs
-sIjsServer=hpijs -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842
Public bug reported:
sometimes I need to enter my password to be able to shut the system down
from a running gnome session. This happens on two systems here and is
in no way predictable - sometimes it comes twice in a row, sometimes
half a week not... :/
** Affects: ubuntu
Importance:
Public bug reported:
loading gdm earlier in the boot process is a great idea, but as the
other services are loaded directly after it, it doesn't have time to
settle (esp. showing the login screen). The result is, that gdm loads
after about 25 seconds for me, but it takes another 10, until I can
ups, sorry... it's on jaunty. Very complicate to reproduce. Instead of
the normal will shut down in 60 Seconds-dialog gksu appears.
--
need to enter password to shut down sometimes
https://bugs.launchpad.net/bugs/346830
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: gdm
if you set the gdm theme in the selection tool to random from
selected, it autoselects happy gnome (the first theme in the list),
but not the theme, which was previously the only one (which is, what I'd
expect).
** Affects: gdm (Ubuntu)
Also doesn#t work here. Manually running /etc/init.d/ondemand start
also doesn't work, but fails silently. Putting the echo-Command manually
works. I'm no bash guru, so no idea, where the problem sits.
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug
I also get the message here - AMD 780G chipset and a WD WD10EADS-00L5B1.
Everythings boots fine afterwards and performance is also not affected,
but the message looks scary.
--
Softreset failed (device not ready)
https://bugs.launchpad.net/bugs/285392
You received this bug notification because
as nobody reacts, some more details: Asus M2N (intel Pentium M, 855
Chipset); no known ACPI issues since ages. Nothing (except that
nforce2-message) from cpufreq in any of the logs...
--
system stays on full CPU clock
https://bugs.launchpad.net/bugs/341573
You received this bug notification
Public bug reported:
Binary package hint: linux-image-2.6.28-9-generic
(critical regression from today's update)
the system now starts with the CPU governor set to performance each
time, so we waste electrical power like hell and after 5 minutes my ears
get killed by the CPU fan...
** Affects:
*** This bug is a duplicate of bug 340283 ***
https://bugs.launchpad.net/bugs/340283
Nop, *definitly* no dup, as it's a lot older and stayed after compiz
came back. Also as you can see parts of the problem have nothing to do
with compiz.
--
missplaced window decoration
*** This bug is a duplicate of bug 340283 ***
https://bugs.launchpad.net/bugs/340283
ok, there we go, found it. Once again gconf screwed up. So a register-
all was required (maybe should be automatically ran, if let's say
libgnome geht's updates?)
--
missplaced window decoration
*** This bug is a duplicate of bug 340283 ***
https://bugs.launchpad.net/bugs/340283
you have to reinstall compiz-gnome manually.
--
missplaced window decoration
https://bugs.launchpad.net/bugs/340423
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: metacity
The window decoration on jaunty appears missplaced both with and without
compiz. With the 3 icons are only very far apart; without the maximise
icon is on the far left, the menu item slightly right of it ant the
others are totally missing.
**
Screenshot with compiz enabled.
** Attachment added: compiz.png
http://launchpadlibrarian.net/23715301/compiz.png
--
missplaced window decoration
https://bugs.launchpad.net/bugs/340423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
and the version without compiz.
Changing themes has no effect, it looks the same on all default themes.
intel GMA 855 (driver Version irrelevant)
** Attachment added: nocompiz.png
http://launchpadlibrarian.net/23715490/nocompiz.png
--
missplaced window decoration
imho the default should be just changed to set UTC=no and never ask the
user. There is no practical use for this function, except producing
problems with Windows.
--
doesn't ask if BIOS time is in UTC
https://launchpad.net/bugs/37750
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: xrandr
I you change your desktops resolution with xrandr, this doesn't get
resettet to default, if you log out of the system, so other users (and
the login-screen) still have the changed resolution.
** Affects: xrandr (Ubuntu)
Importance: Untriaged
Public bug reported:
Binary package hint: linux-image-2.6.15-25-686
regression in 2.6.15-25: network gets lost on suspend on Asus M2N.
ifconfig only shows lo, you need to activate eth0 and eth1 manually.
Also resuming takes much longer, as with -23. Nothing interesting in
/var/log/messages or
ok, some more details, I found:
I'm using network-manager here, so the devices do not get automatically
configured in /etc/network/interfaces, but the NetworkManager-Scripts
seam to do ifconfig eth0 up and ifconfig eth1 up (nothing more!) after
booting. This get's restored with 2.6.15-23, but not
yes, I can. If I boot with -23, it still works automatically - that's
why I guess it's the kernel.
--
network lost on suspend on Asus M2N
https://launchpad.net/bugs/49984
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
24 matches
Mail list logo
