Use dmraid -r to see, if your system has any dmraid controlled disks.
Then, to remove the dmraid signatures, use: dmraid -r /dev/sdX -E, where
/dev/sdX is a disk displayed by the dmraid -r command. A safe bet is to
do a cross compare between the devices listed by dmraid -r and the
devices listed in
Ah, problem solved: The reason is that mdadm thinks the partitions are
controlled by fake raid on motherboard. Adding nodmraid to boot options
solves the problem.
However, this is still an issue, as the motherboard raid is disabled on
bios and the mdadm should not use dmraid then
--
udev causes
Oh, and the motherboard chipset is Intel P35 (Asus P5K Pro)
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Final out, still no change.
However, could this be related to the Intel fake raid controller I have
onboard? It's disabled in bios (the SATA mode is AHCI, not RAID), but
still worth noting
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You recei
Just a quick update: After RC came out, the partitions are still missing
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33843705/Dependencies.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Output of blkid"
http://launchpadlibrarian.net/33843775/blkid.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/33843725/UdevLog.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/33843723/UdevDb.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/33843721/ProcModules.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/33843710/Lsusb.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/33843718/ProcCpuinfo.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/33843719/ProcInterrupts.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/33843701/CurrentDmesg.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/33843708/Lspci.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/33843698/BootDmesg.txt
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Architecture: i386
CustomUdevRuleFiles: 86-hpmud-hp_laserjet_p1505.rules 45-libmtp7.rules
86-hpmud-hp_laserjet_p1006.rules 86-hpmud-hp_laserjet_p1008.rules
86-hpmud-hp_laserjet_1005_series.rules 86-hpmud-hp_laserjet_1018.rules
86-hpmud-hp_laserjet_1020.rules 45-libnjb5.rules
86-hpmud-hp_laserje
Change to correct Project
** Project changed: ubuntu-on-ec2 => udev
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
You received this bug notification because you are a m
Version of udev is 147~-5
--
udev causes raid to degrade after update to Karmic beta
https://bugs.launchpad.net/bugs/449876
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
https:/
T500 attached
** Attachment added: "dmidecode T500"
http://launchpadlibrarian.net/30906912/dmidecode.out
--
Mute button on thinkpad x200/x200s
https://bugs.launchpad.net/bugs/281732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: compiz
Focus follows mouse does not work as without desktop effects and leads
to odd behaviour of focus.
Steps to reproduce:
1. Open terminal and Gedit on workspace 1
2. Focus on Gedit
3. Move to workspace 2, move mouse to place where terminal is on wor
Currently the button on my T500 is no longer muting. The mute state
changes in /proc/acpi/ibm/volume, but the sound still plays ok
--
Mute button on thinkpad x200/x200s
https://bugs.launchpad.net/bugs/281732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 306088 ***
https://bugs.launchpad.net/bugs/306088
** Summary changed:
- Adobe Flash Player 10: Full-screen stay only one seconde
+ Flash player full-screen stays on only for a second if focus follows mouse
** Description changed:
- When i read Vidéos in
Public bug reported:
Xcb-util >= 0.3.0 is required by Awesome 3.0 (bug #253985). Current
Jaunty version is 0.2.1, Debian experimental provides 0.3.1 and it
should be ported to Jaunty.
** Affects: xcb-util (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Xcb-ut
I updated the description to require Awesome 3.0 for Jaunty. The 3.0
also needs xcb-util 0.3.0, which probably needs another ticket
** Summary changed:
- Package Awesome 3.0-rc1 for Intrepid
+ Package Awesome 3.0 for Jaunty
** Description changed:
Binary package hint: awesome
- Awesome 3.0
0.2.1 is provided by Jaunty, so I'm closing this bug
** Changed in: xcb-util (Ubuntu)
Status: New => Fix Released
--
Package xcb-util for Intrepid (8.10)
https://bugs.launchpad.net/bugs/253984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Seems that the package can be found in sid repositories
(http://packages.debian.org/source/sid/xcb-util).
--
Package xcb-util for Intrepid (8.10)
https://bugs.launchpad.net/bugs/253984
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: ecryptfs-utils
Following directions from
https://wiki.ubuntu.com/EncryptedPrivateDirectory leads to a situation
where gnome-screensaver will no longer unlock due to the changes in
common-auth
** Affects: ecryptfs-utils (Ubuntu)
Importance: Undecided
Awesome 3.0rc1-1 has hit experimental in Debian:
http://packages.debian.org/experimental/awesome
I'll try later today building the package with my Intrepid install
--
Package Awesome 3.0-rc1 for Intrepid
https://bugs.launchpad.net/bugs/253985
You received this bug notification because you are a
** Tags added: xcb-util
--
Package xcb-util for Intrepid (8.10)
https://bugs.launchpad.net/bugs/253984
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
https://lists.ubuntu.com/mai
** Tags added: awesome window-manager xcb-util
--
Package Awesome 3.0-rc1 for Intrepid
https://bugs.launchpad.net/bugs/253985
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
https
Releaser is also the Debian maintainer of the xcb-util, so we'll
propably see it there soon. I'll report on this bug when it happens.
--
Package xcb-util for Intrepid (8.10)
https://bugs.launchpad.net/bugs/253984
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
xcb-util got released a 0.2.1[1] finally, it would be nice to have in
the Intrepid repositories
[1] http://lists.freedesktop.org/archives/xorg-
announce/2008-August/000627.html
** Affects: xcb-util (Ubuntu)
Importance: Undecided
Status: New
--
Package xcb-uti
Public bug reported:
Binary package hint: awesome
Awesome 3.0-rc1 got released[1] earlier today, it would be nice to have
it replace 2.3 in Intrepid. Awesome 3 requires latest xcb-util to run,
so this is related to bug #253984
[1]http://permalink.gmane.org/gmane.comp.window-managers.awesome/2480
I'm using svn revision 682 and the Length Required -problem seems to be
gone. Maybe the Ubuntu package should be updated to a newer version?
--
Firebug console shows incorrect response
https://bugs.launchpad.net/bugs/221899
You received this bug notification because you are a member of Ubuntu
Bug
This is confirmed on Feisty
--
MoinMoin reset password email improperly encoded
https://bugs.launchpad.net/bugs/85372
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
I can confirm this behaviour with Asus V6J too.
--
kernel oops after resuming from suspend to RAM
https://bugs.launchpad.net/bugs/129226
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
With 2.0.0.6 that just hit the repos this is no longer reproducible.
Didn't test on 2.0.0.5 though.
--
Firefox deletes passwords when clearing private data and it shouldn't
https://bugs.launchpad.net/bugs/126780
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Gutsy ships with ipw3945 1.2.1 which fixes some issues with driver not
waking up in some cases. It fixed suspend problems on my laptop.
I'm not sure does this driver ship with later Feisty kernels, but at
least the 2.6.20-13 and previous shipped with 1.2.0. You can override
this manually installin
In addition: after this it cannot save passwords anymore.
--
Firefox deletes passwords when clearing private data and it shouldn't
https://bugs.launchpad.net/bugs/126780
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bu
Public bug reported:
Binary package hint: firefox
In Gutsy with Firefox 2.0.0.4 (updated from Feisty) Firefox clears
passwords when using "Clear Private Data"-function. This happens even if
"Saved Passwords" is not checked.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status:
Seems that it wakes up on the first suspend, but after second it
doesn't so there (propably) happens something on first resume that
makes second resume impossible. If someone could point out some ways
to debug this I'd be glad to do it.
--
ipw3945 radio kill switch on when returning from suspend
With my Nvidia card the problem seems to be gone.
--
Screen corruption.
https://bugs.launchpad.net/bugs/88504
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
MODULES_WHITELIST seems not to help with 2.6.20-14. It works with
2.6.20-13.
More to debugging:
rf_kill for the card is: 2
(turns to 3 if echo -n 1 > .../rf_kill is ran)
power/state is 0
--
ipw3945 radio kill switch on when returning from suspend
https://bugs.launchpad.net/bugs/99732
You recei
On suspend this can be overridden by adding module to MODULES_WHITELIST
in /etc/default/acpi-support
e.g.
MODULES_WHITELIST="ipw3945"
--
ipw3945 radio kill switch on when returning from suspend
https://bugs.launchpad.net/bugs/99732
You received this bug notification because you are a member of
Bit more debugging:
Seems that the wifi wake up or shutdown scripts are somehow broken. I
don't know has there been new additions to those in 2.6.20-13.
Pressing the hotkey shuts the wlan, but it doesn't wake up after being
pressed again. Modprobing it again prints "Kill Switch is on" -message
to
The problem is that I could test this with newer bios if it wouldn't
crash my laptop otherwise. If I could find out a way to revert my bios
to 212 I would gladly test this with 303.
--
ipw3945 radio kill switch on when returning from suspend
https://bugs.launchpad.net/bugs/99732
You received this
As this problem persists on two users. I'm marking this confirmed.
The problem appeared on 2.6.10-13, it was working fine before (2.6.20-12
and prior)
** Changed in: linux-restricted-modules-2.6.20 (Ubuntu)
Status: Unconfirmed => Confirmed
--
ipw3945 radio kill switch on when returning f
*** This bug is a duplicate of bug 94133 ***
https://bugs.launchpad.net/bugs/94133
I've made a new bug of my problem: #99732
It's a bit similiar to this but the main difference is that my ipw3945
doesn't switch kill switch off when returning from suspend. There's no
difference if I unload the
** Attachment added: "lspci -vvnn output"
http://librarian.launchpad.net/7099188/lspci.log
--
ipw3945 radio kill switch on when returning from suspend
https://launchpad.net/bugs/99732
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
** Attachment added: "dmesg attachment"
http://librarian.launchpad.net/7099176/dmesg.log
--
ipw3945 radio kill switch on when returning from suspend
https://launchpad.net/bugs/99732
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Public bug reported:
Binary package hint: linux-restricted-modules-2.6.20-13-generic
After suspend ipw3945 wifi device doesn't wake up. Trying modprobe
ipw3945 reports in dmesg the kill switch is on. Using hardware switch
doesn't wake it up, only boot seems to help. Suspend was working fine
with
I suspended with the wlan on and it didn't wake up after suspend.
--
IPW3945 unable to restart after suspend
https://launchpad.net/bugs/91645
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm somewhat similiar behaviour with my gnome terminal. It
tends to corrupt when I change from another virtual desktop to another.
** Attachment added: "Corrupted GNOME Terminal"
http://librarian.launchpad.net/6854997/corrupted_terminal.png
** Changed in: vte (Ubuntu)
Status:
Public bug reported:
Binary package hint: network-manager
When returning from suspend, NetworkManager connects to wired network. I
manually have to select the wireless network even if it is the same as
before and there's no link up in wired network.
It should not default to wired if the link is
Every feed I've tried so far have resulted in the similiar error.
** Changed in: firefox (Ubuntu)
Status: Needs Info => Confirmed
--
Firefox cannot read Feeds anymore
https://launchpad.net/bugs/85772
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
"me too"
Confirmed with Asus V6J
--
Locked screen won't unlock
https://launchpad.net/bugs/84975
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
"me too"
Confirmed with Asus V6J
--
Locked screen won't unlock
https://launchpad.net/bugs/84975
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Unconfirmed => Confirmed
--
Random synaptics mouse input lockups
https://launchpad.net/bugs/62626
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same behaviour found on my computer. Vbetool crashes on every login and
returning from suspend
** Changed in: vbetool (Ubuntu)
Status: Unconfirmed => Confirmed
--
[apport] vbetool crashed with signal 5
https://launchpad.net/bugs/83170
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
There's somehow identical bug in Gnome bugzilla. If someone agrees this
is an identical problem, update it to the description of the bug
http://bugzilla.gnome.org/show_bug.cgi?id=354565
--
[feisty] nm-applet claims wired connection when its wireless
https://launchpad.net/bugs/83178
--
ubuntu-bu
I can confirm this with Asus V6J with IPW3945
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed => Confirmed
--
[feisty] nm-applet claims wired connection when its wireless
https://launchpad.net/bugs/83178
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
This behaviour is confirmed now. Another V6J user ('Visik7' on Ubuntu
wiki) found out that bios 303 causes the dsdt code to change. Change
causes the Brightness up to restart X. I can confirm this behavior with
bios version 303.
** Changed in: acpi-support (Ubuntu)
Status: Rejected => Confi
I can confirm this behaviour on my laptop (Asus V6J) running Edgy Eft
with latest updates.
Best way to unlock the pointer I've found so far is to find the place it
got stuck and click right mouse button there.
--
Random synaptics mouse input lockups
https://launchpad.net/bugs/62626
--
ubuntu-b
This occures on Asus V6J + Edgy too.
I can't risk testing Feisty, since the computer holds essential work
data.
--
after sleep+resume I can't restart the system
https://launchpad.net/bugs/29695
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
I sent the laptop to Asus for repair and they changed the motherboard.
Now, the brightness works ok.
--
Regression: Brightness up restarts X in Edgy with Asus V6J
https://launchpad.net/bugs/68391
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
Rejecting, since a hardware issue afterall
** Changed in: acpi-support (Ubuntu)
Status: Unconfirmed => Rejected
--
Regression: Brightness up restarts X in Edgy with Asus V6J
https://launchpad.net/bugs/68391
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
Now the behaviour has changed. Pressing brightness up restarts the whole
machine. And it restarts it controlled (as if I'd called reboot), not
like crashing down.
--
Regression: Brightness up restarts X in Edgy with Asus V6J
https://launchpad.net/bugs/68391
--
ubuntu-bugs mailing list
ubuntu-bu
Public bug reported:
Binary package hint: gnome-power-manager
When on AC power the panel is not dimming correctly. G-p-m (apparently)
just changes whole screen black without notifying acpi to should down
LCD display (or the backlight of it).
This causes a luminated black screen and temperature r
Seems that this persists still with up to date Dapper to Edgy upgrade. I
had to revert paths to get this fixed.
--
fonts do not diplay when run in X
https://launchpad.net/bugs/57803
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
We had somehow different X.org and I tried yours. X works, but the
brightness up still crashes it. Also, I don't get the same acpi codes as
you.
Seems, that there indeed is some hardware difference between these two
machines, but I still don't understand why Edgy behaves like it does.
--
Regres
To clarify previous comment: I've made the revert to Dapper from Edgy
beta, the one now installed is the released version, upgraded from
dapper. I've also tested a clean install with Beta (this shouldn't,
however, make this bug less severe)
--
Regression: Brightness up restarts X in Edgy with Asu
I've done revert back to Dapper once (during beta) and the brightness up
key worked fine. Now that I installed Edgy, it started to do the
restarting X.
The codes from the ACPI I've gathered by pressing the Brightness Up -key
in TTY1 and copying the output to the log here. I've also double checked
Thanks for your reply,
the brightness worked under Dapper, so that's why I'm now confused with
the Edgy behaviour.
--
Regression: Brightness up restarts X in Edgy with Asus V6J
https://launchpad.net/bugs/68391
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Output of /proc/acpi/asus/info
Asus Laptop ACPI Extras Driver 0.30
Model reference: M2E
SFUN value : 0x18f7
DSDT length: 34937
DSDT checksum : 159
DSDT revision : 1
OEM id : V6J00
OEM table id : V6J5
OEM revision : 0x5
ASL comp vendor id :
Apparently asus_acpi is not loaded correctly.
The output of `lsmod | grep acpi`
sony_acpi 6412 0
pcc_acpi 14080 0
dev_acpi 12292 0
asus_acpi 17688 0
Nothing is using asus_acpi, how could this be fixed?
--
Regression: Brightness up
Public bug reported:
Binary package hint: acpi-support
Pressing brightness up hotkey (fn+f6) restarts X. This didn't happen in
Dapper, the brightness hotkey was correctly working there. No setup
changes (like BIOS) was done before updating. This also happens if Edgy
is installed from a clean inst
Public bug reported:
Binary package hint: gnome-bluetooth
Gnome-obex-server doesn't create essential gconf entries when installed.
It should create ~/.gconf/apps/gnome-obex-server/%gconf.xml file
including keys for savedir (string, directory to save) and
receive_notification (boolean).
These two
Using unofficial repo providing most recent rhythmboxes (deb
http://www.elisanet.fi/mlind/ubuntu dapper main) the problem is gone, so
maybe this is fixed in 0.96.
Anyway, the Dapper Rhythmbox 0.93 still crashes.
** Description changed:
Binary package hint: rhythmbox
Rhythmbox (0.93) crash
Public bug reported:
Binary package hint: rhythmbox
Rhythmbox (0.93) crashes, if it can't open radio stream given. The
program must be shut down via kill or similiar.
On 0.95 port found in backports (not in repos, in comments at
launchpad), the rhythmbox just crashes silently in this case.
How
I'm having same kind of problem where mouse clicks are not responding.
Only way is to switch workspaces, but that doesn't always help.
Best solution so far has been right clicking on the zone where the mouse
was when it stopped responding. This problem is more frequent all the
time
--
Mouse clic
Public bug reported:
Selecting an item from history that has already been removed causes the
deskbar applet to throw following error:
A Programming error has been detected
Details section:
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/deskbar/DeskbarApplet.py", lin
Edgy Eft Beta 1 g-p-m tells that the capacity is 55% (Poor) and says
that there is 10 hours before battery runs out.
Acpi tells that it has 1:53 left (which is not correct either)
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs maili
Apparently it's not a hardware issue. See comments
** Changed in: gnome-power-manager (Ubuntu)
Status: Rejected => Confirmed
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Would be a nice handler for Asus V6J too, where the Power4Gear button is
locking the screen at the moment.
Proposed script, however, is not working since Asus V6J has two cores
and in that case, two cpus that can be individually scaled.
--
asus hotkey ATKD 005c (power4gear)
https://launchpad
Problem persits so this is a hardware problem or propably solvable with
battery calibration in BIOS. Anyway, not a software bug.
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Now, after updating BIOS the sensor says 17% (after a brief charging).
I'll try to run out of battery during the evening so I can confirm is it
a hardware / bios version issue
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs mailing li
Apparently, it's lying (Acpi has been showing 0% for the last 30 mins).
Asus has updated bios recently, so I'll report more soon after I get my
bios updated
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Confirmed the bug and added acpi-support as package
** Changed in: Ubuntu
Sourcepackagename: None => acpi-support
Status: Unconfirmed => Confirmed
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
I confirm this with my Asus V6J too.
--
[ACPI] Wrong number considering minutes before extinction
https://launchpad.net/bugs/57356
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Here are the relevant parts of my acpid. Neither do syslog or dmesg have
anything even error-like in them.
[Tue Jul 18 09:00:23 2006] received event "button/sleep SLPB 0080 0002"
[Tue Jul 18 09:00:23 2006] notifying client 4708[108:108]
[Tue Jul 18 09:00:23 2006] executing action "/etc/acp
I'm having similiar problems with my Asus V6J too. I'll try to get you
the logs as soon as possible. As a side note, no hsfmodem is installed.
--
[regression] Suspend [to-RAM and to-disk] is broken in 2.6.15-25.43
https://launchpad.net/bugs/50031
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
92 matches
Mail list logo
