Er, I mean, I'm using 3.13-rc5 plus Trusty packages on Saucy.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1266746
Title:
x86_64: Fails to start using EFI firmware
To manage
I can confirm this, though in my case, I'm using 3.13-rc5 kernel plus
Trusty's qemu-related packages.
The following command works (though gives no isa-debugcon output):
qemu-system-x86_64 -M pc -m 5120 -boot menu=on -monitor stdio -chardev
stdio,id=seabios -device
Hmm, I've gone on to use git qemu and newer OVMF, and I'm running into
various other hangs that are not necessarily the same. Feel free to
place this bug back in its previous status; I've unmarked affects me
too for now.
--
You received this bug notification because you are a member of Ubuntu
I'd consider the removal of that displayconfig script a fix in and of
itself so you might consider marking it fixed rather than won't
fix.
--
guidance-backends overwrites xorg.conf without confirmation or notification, if
video card has changed since last boot
I would agree with the 'invalid' evaluation on the Xorg task, since
evdev refusing to handle the device is merely because the device does
not present itself as a valid keyboard (as shown in
/proc/bus/input/devices). I had marked Xorg as affected due to its
interaction with the bug. I would like
I have a bridge device in my (attached) Interfaces file, for any VMs I
may run; this bridge device uses dnsmasq to serve up dns and dhcp, for
NAT. However, with the latest few versions of NetworkManager...
NetworkManager seems to try to connect as a _client_ on that
interface... which I am the
I have a bridge device in my (attached) Interfaces file, for any VMs I
may run; this bridge device uses dnsmasq to serve up dns and dhcp, for
NAT. However, with the latest few versions of NetworkManager...
NetworkManager seems to try to connect as a _client_ on that
interface... which I am the
Aah, new discovery: the latest version of NetworkManager
(0.7~~svn20081008t224042-0ubuntu1) fixed my br0 issue for me; now br0 merely
does not appear in NetworkManager. I actually do want eth0 to be managed by
NetworkManager; the bridge contains only tap devices, not physical devices.
It looks
After a lot of searching, I managed to find the Ubuntu-patched
toshiba_acpi source; for some reason, neither the linux-source package,
nor the source (apt-get source) for linux-image-2.6.27-7-generic
contained the current 0.19a-dev version of the toshiba_acpi module. In
fact, the Ubuntu patches
Is there any way to build the module out-of-tree? It'd be a great help
if somebody could build either a full kernel image, or just the .ko
file, and attach it to this bug page. I'd do it myself, but the linux-
source package doesn't have the Ubuntu patches installed, so it can't
use
I can also confirm this; it's rather irritating. Oddly enough, it
seemed to work for a while after I had initially installed quodlibet,
but then broke once I added stuff to the actual collection -- which I
don't use, anyway.
--
Filesystem browser stops listing files with GtkWarning
Marking as confirmed, because three confirmations seems like enough to
me.
** Changed in: quodlibet (Ubuntu)
Status: New = Confirmed
--
Filesystem browser stops listing files with GtkWarning
https://bugs.launchpad.net/bugs/155348
You received this bug notification because you are a
I have also been experiencing random hard lockups, usually when either playing
music, or seeding torrents, from my ntfs (-3g) partition. Oddly enough, it
only ever seems to happen when I'm also using (nvidia binary) 3D functionality,
including the simple rss-glx 'flux' screensaver. However,
Here's how to reproduce it:
Open glchess.
Select Game-New, or press Ctrl-n).
Set one player to Human, and the other to Gnu Chess.
Click Start to begin the game.
Now go to Help-Contents. An Info Bar with the following text appears:
[Color of Human] Wins
One of the players has died
How do you even
I thought of a different way to re-add zero: simply allow it as one of the
usable values. As it is right now, gnome-power-manager's indicated brightness
levels
(100, 85, 71, 57, 42, 28, 14, 0)
no longer match the indicated values in the dsdt:
(100, 87, 75, 62, 50, 37, 25, 12, and a true zero
Do the /dev/input/by-id symlinks still work? If so, a better message
would be the following:
$IDENTIFIER: The 'Name' option has been removed in the transition to
Input Hotplug; please use 'Device' instead.
($IDENTIFIER is from xorg.conf.)
--
evdev mouse fails on hardy: cannot open input
Hmm, when I was looking at the changelog for 2.6.25-rc1, I noticed the
following two changelogs and bug reports that may address this issue:
ACPI: video: Rationalise ACPI backlight implementation
http://bugzilla.kernel.org/show_bug.cgi?id=9277
It also addresses this second issue of
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
LCD backlight turns off when between discrete levels, both from hotkeys and
from dim-on-idle.
https://bugs.launchpad.net/bugs/121833
You received this bug notification because you are a member of Ubuntu
Bugs, which
I am also getting this even in the Hardy kernel; however, only my
modifier keys ever get stuck down. Try doing anything productive with
'super' (or with 'shift', too, and firepaint!) held down. it renders
the desktop useless. I have to ctrl-alt-backspace to kill X; if I'm
particularly
Another note: I've now tested with [EMAIL PROTECTED] stopped, and it seems to
make no difference. However, switching from compiz-fusion to Metacity
does prevent the problem occuring.
Just this evening (and now night), I've had to ctrl-alt-backspace the X server
about 15 times times because my
Here's the output from dmesg under the latest alsa-source
(1.0.16-0ubuntu3) modules, compiled with --with-debug=all for kernel
2.6.24-11-generic:
(here I load the snd-hda-intel module)
[10106.027223] ACPI: PCI Interrupt :00:1b.0[A] - GSI 22 (level, low) -
IRQ 21
[10106.027256] PCI: Setting
Hmm, I was getting the hang, but not the error, with -d; then I realized
that it should be -Dhw:0 (capital letter).
The error given by arecord after the hang is this: arecord:
pcm_read:1347: read error: Input/output error
I have added single_cmd=1 to the options for snd-hda-intel, in
Hmm, under the direction of RAOF in IRC, I have booted the
2.6.22-14-generic kernel, and can confirm that the issue does still
occur there (I'm on Hardy, dist-upgraded from Gutsy). The bug is
instantly reproducible by pressing a key and using a mouse button at the
same time -- for example, save
One thing I've noticed (and appreciated) recently: now both Xorg and
console-setup offer a US International (AltGr Deadkeys) layout. This allows
me to _not_ have dead keys under normal usage, and then merely press right-alt
to use deadkeys and ordinary altgr-alphanumeric keys. This might be
(dang, where's the edit function?)
I also forgot to mention: this AltGr Deadkeys layout may be new to Hardy.
--
better console setup
https://bugs.launchpad.net/bugs/137510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Another related bug is this: bug 190934
When I get the key stuck, then unsticking it produces the same broken
modifiers. In addition, ctrl-alt-backspace will no longer work -- if you run
'xev' in console and press ctrl-alt-backspace, you get the Terminate_Server
keysym, which Xorg itself
Thank you! I'm glad to see that the 2.6.24-11-generic kernel I recently
installed has fixed this!
One slightly odd request: sometimes, for a gimmick, it's fun to turn off the
backlight deliberately; is there any way to do this now, perhaps by echoing a
specific negative value into sysfs
I had just completed writing up this thing, and then my 'alt' key got
stuck and rendered me unable to post, or even save, my writeup grr.
I've also been having severe keyboard breakage under Hardy. Initially I
used evdev for my keyboard, but then I started having the issue where,
almost
Hmm, yesterday and today I went through older versions of xorg (mainly just
xserver-xorg-core) by two or three at a time, and the first version I
encountered that didn't have the sticking issue is2:1.4-3ubuntu1 (
xserver-xorg-core_1.4-3ubuntu1_i386.deb ) . I tried the same actions of
Well, I must be lucky: the very next version (
2:1.4.1~git20071105-1ubuntu3 ) reintroduces the bug. Therefore, the bug
must've been introduced somewhere between the following two versions:
DateStatus Target
Pocket Component
Is there any chance of reopening this bug for Hardy? I greatly prefer
the old subpixel rendering method, and before the rendering patches were
moved upstream, I could use my local.conf to enable the old method;
however, as of fontconfig 2.5.0-2ubuntu2, I can no longer do that --
instead, I just
Well, I'm glad I didn't decide to change any attributes of this bug myself.
I followed the link to https://bugs.freedesktop.org/show_bug.cgi?id=13566 and
discovered that the constant had been renamed to 'lcdlegacy'. I then tried
that value in local.conf, and it claimed 'lcdlegacy' was invalid.
Here's something kind of interesting: the new 2.6.26-2-generic kernel in
Intrepid somehow magically fixed my audio capture.
I had previously (a few months ago) tried the HG version of ALSA, with no
effect... but this time, somehow, the new kernel must've changed something else
(perhaps
At my college (Cal Poly, SLO), all the wireless access points use the
same SSID, but each is on a different subnet. When I roam from one
access point to another, my connection mysteriously breaks without
notice... and thinks it's still up. It seems NetworkManager can't
handle different access
Two corrections:
...instead, they give true internet IPs.
... upon roaming to a different access point with the _same_ SSID, ...
--
WiFi roaming causes NetworkManager to lose routing
https://bugs.launchpad.net/bugs/201202
You received this bug notification because you are a member of Ubuntu
This is not just bcm-anything; it happens on my Intel 3945ABG (iwl3945)
card.
--
[bcm4xx] WiFi roaming causes NetworkManager to lose routing
https://bugs.launchpad.net/bugs/201202
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Intrepid still has this bug, since the filesystem.py file is still as it
was before that changeset 4189. I can also confirm that applying those
changes to filesystem.py fixes the issue.
--
Filesystem browser stops listing files with GtkWarning
https://bugs.launchpad.net/bugs/155348
You received
Hmm, after applying the fix, QuodLibet no longer maintains folder
selection after quitting and re-launching the application -- instead,
the application always launches with NO folder selected, and thus with
an empty playlist.
--
Filesystem browser stops listing files with GtkWarning
I can also confirm this issue.
I have two sound cards: my onboard 2-channel HDA card (front:0), and my cardbus
Audigy2 (surround51:1). I've set default-sample-channels=6 in daemon.conf,
since the Audigy2 refuses to open in multichannel mode if it's already open in
stereo mode.
One hopefully
New observation: After undoing the patch (by purging and reinstalling
QuodLibet), I've realized that that behavior (not restoring selected
folders) is not an issue with that patch -- the behavior also exists
with the original packaged version. If I edit the config file to unset
the collection
Here's a note that may be relevant: Intel's document, Intel® 82567 Gigabit
Ethernet
Controller Specification Update and
Sighting Information, (
http://download.intel.com/design/network/specupdt/82567_su.pdf ) states the
following:
3. 82567-LM Device ID for Montevina Platform
Changed from
Public bug reported:
Binary package hint: kde-guidance
Some laptops allow the user to choose between an integrated GPU (for
power savings) and a discrete GPU (for performance). One of my friends
has such a laptop; I've set it up with a customized xorg.conf file,
tweaked with Device entries for
** Description changed:
Binary package hint: kde-guidance
Some laptops allow the user to choose between an integrated GPU (for
power savings) and a discrete GPU (for performance). One of my friends
- has such a laptop, and I've set it up with a customized xorg.conf file,
- with touchpad
** Description changed:
Binary package hint: kde-guidance
Some laptops allow the user to choose between an integrated GPU (for
power savings) and a discrete GPU (for performance). One of my friends
has such a laptop; I've set it up with a customized xorg.conf file,
tweaked with
Public bug reported:
In the latest Intrepid kernel, the toshiba_acpi module has been removed,
in favor of the new 'tlsup' driver. However, this breaks all the
hotkeys on an old Toshiba laptop I'm testing Intrepid on; system is a
Satellite 1415-S105, with an aftermarket ipw2200 card.
HAL has no
** Attachment added: lshal output
http://launchpadlibrarian.net/17071871/tosh-lshal.txt
--
Xorg doesn't know how to use Toshiba Laptop Support (tlsup) input device
https://bugs.launchpad.net/bugs/261318
You received this bug notification because you are a member of Ubuntu
Bugs, which is
One factor: the HANDLER line for the tlsup device in 'cat
/proc/bus/input/devices' shows only 'event7' -- no 'mouse' or 'kbd' at
all!
** Attachment added: output of 'cat /proc/bus/input/devices'
http://launchpadlibrarian.net/17073420/tosh-proc_bus_input_devices.txt
--
Xorg doesn't know how
** Summary changed:
- Xorg doesn't know how to use Toshiba Laptop Support (tlsup) input device
+ Xorg can't use Toshiba Laptop Support (tlsup) input device; input device does
not support 'kbd' input handler
--
Xorg can't use Toshiba Laptop Support (tlsup) input device; input device does
not
Marking as affecting HAL, Linux, and Xorg, since I'm not sure where the
bug exactly lies, and the behavior involves all three.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: hal (Ubuntu)
Importance: Undecided
Status: New
--
Xorg can't use
This is also still broken in the latest Intrepid kernel,
2.6.26-5-generic.
--
acpi_fakekey stopped working for certain keycodes
https://bugs.launchpad.net/bugs/217504
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hmm, here's a thought: aren't the uinput framework and module meant
exactly for this purpose (injecting input events)? Perhaps acpi_fakekey
can be adapted to use uinput instead of writing to existing input
devices.
--
acpi_fakekey stopped working for certain keycodes
This is still broken for me on the just-uploaded fglrx 8.600 driver on
Jaunty -- see bug report at https://bugs.launchpad.net/ubuntu/+source
/fglrx-installer/+bug/314600
--
fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is
not supported on this hardware (return code =
This is still broken for me in the just-uploaded fglrx 8.600 driver for
Jaunty -- I still get a kernel panic. Note that this is on the
2.6.28-10-generic amd64 kernel.
Another related bug report: https://bugs.launchpad.net/fglrx/+bug/288620
** Attachment added: fglrx-still-panics.log
Note on that 8.750: that's a typo; should be 8.570.
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Another thing I've noticed: this auto-launching update manager doesn't even
achive its stated purpose of having people install updates:
Just yesterday, I booted a drive I hadn't booted in 5 weeks and
update-manager, of course, auto-launched
The only problem: it didn't update the PACKAGE
Not fixed -- still panics on Jaunty with fglrx 8.600 (amd64).
** Changed in: fglrx-installer (Ubuntu)
Status: Fix Released = Confirmed
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are
Hmm, I just tried booting the 64-bit Intrepid (8.04.1) ISO (on a USB
drive); the same thing happens there. I believe there must be something
wrong with the newer versions of the driver (in this case, the just-
released Catalyst 9.1). Some time this weekend, I can make a spare
full-install of
ANother new thing I noticed: after installing (and fixing) HDAAnalyzer, as
shown here, I was able to confirm that asserting GPIO 0 on the adi1984 chip
sets the hardware mute feature.
http://article.gmane.org/gmane.linux.alsa.devel/59132
Relevant lines from Windows .inf file:
Correction: I meant GPIO 1.
--
mute, brightness buttons on new HP 6930p laptop
https://bugs.launchpad.net/bugs/284319
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
One additional comment: on systems such as the HP EliteBook laptops,
which offer bootability from a Ricoh SDHC controller, the initramfs will
also need to include the ricoh_mmc driver (disables the proprietary mmc
controller) in order for the SDHC controller to handle the cards. Also,
I have
This is still broken for me, if I use a non-default icon theme (such as
Tangerine). The old notification-daemon package worked perfectly fine
with all my icons, but for some reason, this new one only seems to like
Human -- literally NO other icon themes on my system show anything for
it.
--
Seems pretty confirmed to me.
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = Confirmed
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Some new discovery: it looks like the hal FDI file mentioned here:
https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/325560 needs
to be updated to add the EliteBook models in two places: one for
backlight control and one where the current fdi file matches for
Compaq. Even after that, I
For me on Jaunty, the 2.6.28-7-generic kernel has been fixed now -- it
seems they've reverted the don't use _BCM and _BCL patches. I'm not
sure about the Intrepid kernel, though. Also, this is not quite a
duplicate -- it's more of a fixing that one broke this one issue.
--
2.6.27-11 makes
This also happens for me (Mobility HD3650 with fglrx): any sort of new
window creation -- including simple un-minimizing -- takes about 1 full
second of doing nothing, during which time compiz or metacity-with-
composite hangs, and Xorg eats 100% of one CPU core. Oddly enough, the
animations
Actually, I'd say my issue is a different one, after all:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/288385
--
[intrepid] Live CD not booting on Intel Centrino Laptop with GME chipset -
possibly ACPI
https://bugs.launchpad.net/bugs/294339
You received this bug notification
Here's what I think is the problem: current versions of the Linux kernel break
the stick out as a separate PS/2 Generic Mouse, instead of having it be part
of the touchpad device.
http://www.cs.helsinki.fi/linux/linux-kernel/2003-27/0026.html
It seems the Synaptics Xorg driver still has
I have an EliteBook 8530w (with ATI card, not nvidia), and have many of
the same issues: mute control and hotkeys don't work very well, as
stated; the only difference is that my backlight control seems to work
fine. Although the brightness hotkeys work in gnome after I run
setkeycodes, the
I also have the same model laptop, and as I commented in this other bug report
(found it before I found this one), I can use serial-over-LAN to get
stacktraces of the OOPSes.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294339
Should I reattach my attachments and comments to this bug
Correction: I diff'd the two binary dsdt files, and there's no
difference.
--
Kernel stops booting on HP EliteBook 8530w
https://bugs.launchpad.net/bugs/288385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I was using it with that BIOS setting enabled, because that's my
preference, but now that I've disabled that option, it boots. However,
I'd consider that more of a workaround, and not a fix -- I'd like to be
able to get it to boot with that option enabled.
Perhaps I should try doing a diff of
Okay, I just tested, and the same version (but 32-bit) kernel on my old
Gateway M685 also breaks backlight control. Same symptoms: proc has
not supported and sys is empty.
--
2.6.27-11 makes brightness not work
https://bugs.launchpad.net/bugs/315922
You received this bug notification because
** Summary changed:
- 2.6.27-11 makes brightness not work
+ 2.6.27-11 makes brightness not work [2.6.28-4.10 also affected]
--
2.6.27-11 makes brightness not work [2.6.28-4.10 also affected]
https://bugs.launchpad.net/bugs/315922
You received this bug notification because you are a member of
Another system affected: an old Toshiba Satellite 1415 laptop. ACPI
Video module normally gives levels labeled as 0%, 40%, and 100%, but now
gives nothing. For better backlight control, this laptop needs toshiba-
acpi instead of tlsup, but that's an entirely different issue.
--
2.6.27-11 makes
Aah, I see it now in the Intrepid changelogs. Cool, so now I can just
wait, and it'll be fixed with an upcoming Jaunty kernel, right?
(By the way, the tlsup bug is also fixed in intrepid-proposed but not
in jaunty: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/261318 )
linux
I'm on the Jaunty kernel Version: 2.6.28-4.10, and this last upgrade
just broke ACPI backlight control on my EliteBook 8530w, which happens
not to have any vendor module for backlight control. The
/sys/class/backlight dir is now empty. Interestingly enough, I also
have another laptop where the
(curse the lack of an edit feature)
More specifically, the EliteBook is using the x86-64 generic kernel.
--
The slider brightness Applet has value inverted after the last update
(2.6.27-11)
https://bugs.launchpad.net/bugs/311716
You received this bug notification because you are a member
It also happens on the Intrepid LiveCD, though -- don't tell me that the
new X server in Jaunty causes that. I've also tried the leaked 8.750
(with INTREPID X server and INTREPID libdrm2!) and it still happens.
Video card is the FireGL equivalent of the Mobility Radeon HD3650.
--
fglrx versions
Sure can do.
** Attachment added: 8530w-ati-lspci-nnvv.log
http://launchpadlibrarian.net/21258958/8530w-ati-lspci-nnvv.log
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of
I'm on Jaunty, and the latest 2.6.28-4.10 generic x86-64 kernel entirely
removes my ability to change brightness levels; the previous kernel
works perfectly.
Under the old kernel, /proc/acpi/video/DGFX/LCD/brightness returns this:
levels: 100 51 30 37 44 51 58 65 72 79 86 93 100
current: 100
** Attachment added: EliteBook-8530w-dsdt
http://launchpadlibrarian.net/21291692/EliteBook-8530w-dsdt
--
2.6.27-11 makes brightness not work
https://bugs.launchpad.net/bugs/315922
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Does the Jaunty 2.6.28-5 kernel also include this fix?
--
Kernel stops booting on HP EliteBook 8530w
https://bugs.launchpad.net/bugs/288385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The 2.6.28 kernel works for me -- the hotkeys give ACPI events again. However,
I run into two other issues: some hotkeys are incorrectly defined for the
laptop's keyboard, and acpi_fakekey doesn't work (
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/217504 ).
Interestingly enough, it
Public bug reported:
I am currently using Jaunty with the latest 2.6.28-4-generic #8-Ubuntu
x86-64 kernel, and any time I try to use fglrx 8.552 or 8.561 (apt-
pinned to Intrepid X server and libdrm2), I get the system hanging at a
black screen when I try to start X, followed by a kernel panic
** Attachment added: fglrx-ouch.log
http://launchpadlibrarian.net/20967279/fglrx-ouch.log
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 313027 ***
https://bugs.launchpad.net/bugs/313027
This is NOT a duplicate: apt-pinned to Intrepid X server and libdrm2
and In addition, using the official ATI installer to buildandinstallpkg
Ubuntu/intrepid within the Intrepid LiveCD gives the same result.
** This bug is no longer a duplicate of bug 313027
MASTER: fglrx does not support xserver 1.6
--
fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Same issue applies for me (Mobility FireGL V5700, which is a rebranded HD3650),
with the addition of a panic on any driver newer than 8.543:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/314600
--
fglrx:fireglAsyncioIntEnableMsgHandler] *ERROR* interrupt source ff66 is
I'm not sure if my issue is the same bug, but my new HP Elitebook 8530w
also won't boot with ACPI enabled. Using the Linux serial console
through AMT Serial-Over-LAN, I was able to capture the boot messages
from when I boot wityh ACPI enabled; note that the system hangs after
the last boot
Interestingly enough, if I disable thermal zone control by adding
options thermal off=1 to some modprobe.d file, it instead errors out
on the battery module.
** Attachment added: HP-EliteBook-8530w.tar.gz
http://launchpadlibrarian.net/20188168/HP-EliteBook-8530w.tar.gz
--
[intrepid] Live CD
I've now upgraded to the 2.6.28-2-ub-generic kernel, and the bug still
exists in that kernel.
--
[intrepid] Live CD not booting on Intel Centrino Laptop with GME chipset -
possibly ACPI
https://bugs.launchpad.net/bugs/294339
You received this bug notification because you are a member of Ubuntu
Here's something interesting on the 2.6.28-2-generic kernel (now that they've
gotten rid of the -ub): I booted with thermal control disabled as above, and
I managed to boot the thing with ACPI enabled -- but this time it OOPS'd out on
the battery module. Additionally, the system hung at the
As seen in kernel.org bug report: Rejecting as INVALID. If someone has
a machine with working ahci external port marking, I have patches to
test but given that most other controllers don't have such feature, I
think we need hal whitelisting one way or the other. -- hmm, I could
use such
Another new discovery: with acpi-services on, I save more power than
with acpi-services off, even if both Battery and AC-Power are set to
low power usage in amdccle. However, in exchange, having acpi-
services enabled makes suspend fail -- system hangs even before going
into suspend.
--
[HD
Speaking of Nautilus, I get some assertion failures, currently:
(nautilus:3021): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion
`pixmap == NULL || gdk_drawable_get_depth (window) ==
gdk_drawable_get_depth (pixmap)' failed
(nautilus:3021): GLib-GObject-CRITICAL **:
I can confirm this on my UEFI-based HP EliteBook 8530w laptop -- I also
get the hard-reboot upon trying to start the kernel.
--
elilo.efi boot failure karmic vmlinuz-2.6.31-x-generic
https://bugs.launchpad.net/bugs/408378
You received this bug notification because you are a member of Ubuntu
Hmm, I seem to have having similar issues on my laptop (Core 2 Duo
2.4GHz, 4GB RAM, 7200RPM hard drive). Oddly enough, I have sometimes
seen udevd sit there for around 10 seconds, doing seemingly nothing.
I believe in my case, sreadahead may just not be working -- I see spew
at boot of No
Hmm, I know Fedora does some interesting stuff with their Leonidas
wallpaper -- it's actually an XML file that selects different images
depending on the aspect ratio of the display. Perhaps we could do the
same here.
--
ubuntu-xsplash-artwork contains redundant graphics
I've just discovered something interesting, after some time
experimenting in Karmic -- somehow, I managed to catch a line about
failed to connect to acpid just before the crash.
Apparently, the acpi-services part of the fglrx driver explicitly
depends on having acpid up and running by the time
A related bug report (though started back in HAL days):
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/153768 -- same issue
of eSATA not being detected as external.
--
eSATA external drive requires password to mount
https://bugs.launchpad.net/bugs/477782
You received this bug notification
1 - 100 of 319 matches
Mail list logo
