** Changed in: xorg-server (Ubuntu)
Sourcepackagename: acpi-support => xorg-server
Status: Confirmed => Fix Released
--
Regression: Brightness up restarts X in Edgy with Asus V6J
https://bugs.launchpad.net/bugs/68391
You received this bug notification because you are a member of Ubuntu
Bug
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 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
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
It seems the attachment of the xorg.conf didn't work. So I post it here
(without comments):
Section "ServerLayout"
Identifier "Layout"
Screen "Screen" 0 0
InputDevice"Keyboard"
InputDevice"Mouse"
InputDevice"Touchpad" "AlwaysCore"
EndSection
Section "Fi
This evening, I installed on another disk the Ubuntu Edgy.
After testing it, I don't have any problem reported with it: the brightness up
and down keys work fine (the touchpad lock also).
The only things that work badly as they are in Dapper are the suspend and the
hibernate functions (with hotke
I forgot one thing: perhaps it is the X configuration that cause theses
troubles.
This is as attachment file my xorg.conf file.
--
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.
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
Additional information with the Dapper on the V6J:
- the event sent when pressing the brightness up is 001f instead of
0086 as reported in the bug,
- the event sent when pressing the brightness down is 002e.
Could this issue come from the hardware or from a misunderstanding of
events
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
J. Pulliainen, I have the same information under Dapper, nevertheless,
brightness hotkeys works fine on my laptop (a V6J-X001P) :
$ lsmod | grep acpi
sony_acpi 5580 0
pcc_acpi 12416 0
dev_acpi 11236 0
asus_acpi 11476 0
acpi_sbs
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
16 matches
Mail list logo
