Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
Loic Nageleisen wrote: > my conclusion: > - acpi stuff now only generates events and does not takes action anymore > - gnome power manager is the only app currently able to catch these key or > hal events and change brightness accordingly > - there's no app for KDE able to do that > - there's no console app either I agree with this, I posted a similar analysis a month or so ago. In fact, as of a couple of days ago I began working around the problem in KDE by shutting down guidance-power-manager and running gnome-power-manager. If these analyses are correct, then I'm at a loss as to how it seems to be overlooked that Kubuntu appears to have no facility for handling brightness key events, and how the actual brightness-changing functionality got removed from /etc/acpi/events before guidance-power-manager (or whatever) grew a replacement for it. > so one should: > 1. implement this in kde power manager > 2. implement this in a daemon listening for hal events (so that it works in > console mode) > 3. make sure those cooperate so that brightness is not set multiple times for > one keypress Agreed, I'd like to repeat my opinion that having to be logged into your desktop environment to change the brightness of your LCD using *dedicated hardware keys* is less than ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote: > Some package have been updated. > Now the FN-brightness keys work again. Still not working for me in KDE land, upgraded a number of packages, last upgrade was less than an hour ago. Browsing the code in guidance-power-manager right now, there was a python indentation error in it's DCOP interface code for brightness control. Fixing that didn't make the buttons work, however, and I can't see anywhere else besides that and the slider controls where brightness calls to HAL are made. So, still trying to figure it out.. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> ** Changed in: kdebase (Ubuntu) >Status: New => Invalid > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Fix Released I'd like to gently point out that the original reporter of this bug is a KDE user. This makes no sense at all. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;) Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote: > As of today, brightness setting fully works for me on a T60. Anyone > confirming that? Also on a T60 here, still not working for me (in KDE). -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> 1. Exact HW ThinkPad T60 > cat /var/lib/acpi-support/system-product-name 2007C3U > 2. Does these two command (if run from Konsole) change brightness > properly on your laptop? Yes, they do. I get a tooltip over guidance-power-manager's kicker icon about the brightness as well, instead of the KMilo OSD that it used to display the last time it worked. > 3. Does your laptop return same keycodes from brightness up (212) and down (101) Affirmative > .. what does "lshal -m" report when key is pressed? 18:17:49.465: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-up 18:17:49.848: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-down HTH! -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running Kubuntu. Brightness keys do not work even though "lshal -m", "acpi_listen", and acpid all see them/do the right thing. No OSD from kmilo anymore either, for anything, even volume or thinklight which work (probably only because they are done in hardware). This all worked several weeks ago, and has actually always worked up until then. Guidance can still adjust the brightness with the slider. Although it's not related directly to this bug, I tend to think it's not coincidental that my lock (Fn-F2, used to lock the session I think, I didn't use it much), battery (Fn-F3, which used to cause guidance-power- manager to show it's tooltip), suspend (Fn-F4), and suspend-to-disk keys (Fn-F12) do not work right anymore either, and broke at the same time. Their implementations in /etc/acpi and so forth are also all similar, only generating various fake keys (see below). The biggest problem with my troubleshooting is that I can't understand/find information on the big picture, how is this mechanism supposed to work at all to begin with. I seem to remember (although admittedly not infallibly) that the scripts in /etc/acpi used to actually modify the brightness (and perform the other key actions) directly thru /sys or /proc somehow. Now all they appear do is synthesize keystrokes using acpi_fakekey. This works right too, xev for example sees these fake keystrokes (although many of them do not have keysyms). But, is some program supposed to receive these keystrokes and perform the action? Or am I barking up the wrong tree? What is HAL's role, if any, in making this work? After the fake key generation, I lose the trail. Any clues? This is a terrible nuisance because I use(d) these keys frequently. Being night- blinded by your laptop is not cool :) -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 134252] Re: alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip
Confirming on my T60 with 82801G as well, including PCM going missing intermittently. It works fine on -9, broken on -10. Unfortunately I am reluctant to go back to -9 for normal use because of Very Annoying Bug #129226 which is fixed in -10 ! One other detail: the "PC speaker" system bell noise is at normal levels, but I can hear nothing else thru speakers or headphones. -- alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip https://bugs.launchpad.net/bugs/134252 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
On Thursday 02 August 2007 17:15, yostral wrote: > I can now (from when I could ? I don't know) connect to an wep encrypted > network with NetworkManager, without switching the kill switch button. > But I still need to do that with an unencrypted one. I am also now in the same boat after dist-upgrade. Thinkpad T60 with ipw3945. [EMAIL PROTECTED]:~$ apt-cache show linux-image-2.6.22-9-generic \ network-manager knetworkmanager | egrep '^Ver|^Pack' Package: linux-image-2.6.22-9-generic Version: 2.6.22-9.21 Package: network-manager Version: 0.6.5-0ubuntu7 Package: knetworkmanager Version: 1:0.2~r686534-0ubuntu1 WEP networks connect fine, have to use the kill switch trick on open ones. Additionally, KNetworkManager is now acting funny, the first time I try to select a network after login, I have to tell it to connect to a particular network twice, the first time I select it, the icon just blinks at me and then continues doing whatever it was doing (either automatically connecting to some network I'm not interested in, or sitting there disconnected). Obviously this may be a separate bug, but thought I'd throw it out there. Kyle -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I'm also having this problem, 2.6.22-7-generic, network- manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile. I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it. Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO- CARRIER. I couldn't reproduce this last symptom for this report. HTH, Kyle ** Attachment added: "daemon.log with play-by-play" http://launchpadlibrarian.net/8271391/daemon.log-with-comments.txt -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
Loic Nageleisen wrote: > my conclusion: > - acpi stuff now only generates events and does not takes action anymore > - gnome power manager is the only app currently able to catch these key or > hal events and change brightness accordingly > - there's no app for KDE able to do that > - there's no console app either I agree with this, I posted a similar analysis a month or so ago. In fact, as of a couple of days ago I began working around the problem in KDE by shutting down guidance-power-manager and running gnome-power-manager. If these analyses are correct, then I'm at a loss as to how it seems to be overlooked that Kubuntu appears to have no facility for handling brightness key events, and how the actual brightness-changing functionality got removed from /etc/acpi/events before guidance-power-manager (or whatever) grew a replacement for it. > so one should: > 1. implement this in kde power manager > 2. implement this in a daemon listening for hal events (so that it works in > console mode) > 3. make sure those cooperate so that brightness is not set multiple times for > one keypress Agreed, I'd like to repeat my opinion that having to be logged into your desktop environment to change the brightness of your LCD using *dedicated hardware keys* is less than ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> 1. Exact HW ThinkPad T60 > cat /var/lib/acpi-support/system-product-name 2007C3U > 2. Does these two command (if run from Konsole) change brightness > properly on your laptop? Yes, they do. I get a tooltip over guidance-power-manager's kicker icon about the brightness as well, instead of the KMilo OSD that it used to display the last time it worked. > 3. Does your laptop return same keycodes from brightness up (212) and down (101) Affirmative > .. what does "lshal -m" report when key is pressed? 18:17:49.465: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-up 18:17:49.848: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-down HTH! -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
On Thursday 02 August 2007 17:15, yostral wrote: > I can now (from when I could ? I don't know) connect to an wep encrypted > network with NetworkManager, without switching the kill switch button. > But I still need to do that with an unencrypted one. I am also now in the same boat after dist-upgrade. Thinkpad T60 with ipw3945. [EMAIL PROTECTED]:~$ apt-cache show linux-image-2.6.22-9-generic \ network-manager knetworkmanager | egrep '^Ver|^Pack' Package: linux-image-2.6.22-9-generic Version: 2.6.22-9.21 Package: network-manager Version: 0.6.5-0ubuntu7 Package: knetworkmanager Version: 1:0.2~r686534-0ubuntu1 WEP networks connect fine, have to use the kill switch trick on open ones. Additionally, KNetworkManager is now acting funny, the first time I try to select a network after login, I have to tell it to connect to a particular network twice, the first time I select it, the icon just blinks at me and then continues doing whatever it was doing (either automatically connecting to some network I'm not interested in, or sitting there disconnected). Obviously this may be a separate bug, but thought I'd throw it out there. Kyle -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134252] Re: alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip
Confirming on my T60 with 82801G as well, including PCM going missing intermittently. It works fine on -9, broken on -10. Unfortunately I am reluctant to go back to -9 for normal use because of Very Annoying Bug #129226 which is fixed in -10 ! One other detail: the "PC speaker" system bell noise is at normal levels, but I can hear nothing else thru speakers or headphones. -- alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip https://bugs.launchpad.net/bugs/134252 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running Kubuntu. Brightness keys do not work even though "lshal -m", "acpi_listen", and acpid all see them/do the right thing. No OSD from kmilo anymore either, for anything, even volume or thinklight which work (probably only because they are done in hardware). This all worked several weeks ago, and has actually always worked up until then. Guidance can still adjust the brightness with the slider. Although it's not related directly to this bug, I tend to think it's not coincidental that my lock (Fn-F2, used to lock the session I think, I didn't use it much), battery (Fn-F3, which used to cause guidance-power- manager to show it's tooltip), suspend (Fn-F4), and suspend-to-disk keys (Fn-F12) do not work right anymore either, and broke at the same time. Their implementations in /etc/acpi and so forth are also all similar, only generating various fake keys (see below). The biggest problem with my troubleshooting is that I can't understand/find information on the big picture, how is this mechanism supposed to work at all to begin with. I seem to remember (although admittedly not infallibly) that the scripts in /etc/acpi used to actually modify the brightness (and perform the other key actions) directly thru /sys or /proc somehow. Now all they appear do is synthesize keystrokes using acpi_fakekey. This works right too, xev for example sees these fake keystrokes (although many of them do not have keysyms). But, is some program supposed to receive these keystrokes and perform the action? Or am I barking up the wrong tree? What is HAL's role, if any, in making this work? After the fake key generation, I lose the trail. Any clues? This is a terrible nuisance because I use(d) these keys frequently. Being night- blinded by your laptop is not cool :) -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote: > Some package have been updated. > Now the FN-brightness keys work again. Still not working for me in KDE land, upgraded a number of packages, last upgrade was less than an hour ago. Browsing the code in guidance-power-manager right now, there was a python indentation error in it's DCOP interface code for brightness control. Fixing that didn't make the buttons work, however, and I can't see anywhere else besides that and the slider controls where brightness calls to HAL are made. So, still trying to figure it out.. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> ** Changed in: kdebase (Ubuntu) >Status: New => Invalid > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Fix Released I'd like to gently point out that the original reporter of this bug is a KDE user. This makes no sense at all. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;) Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote: > As of today, brightness setting fully works for me on a T60. Anyone > confirming that? Also on a T60 here, still not working for me (in KDE). -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I'm also having this problem, 2.6.22-7-generic, network- manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile. I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it. Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO- CARRIER. I couldn't reproduce this last symptom for this report. HTH, Kyle ** Attachment added: "daemon.log with play-by-play" http://launchpadlibrarian.net/8271391/daemon.log-with-comments.txt -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote: > Some package have been updated. > Now the FN-brightness keys work again. Still not working for me in KDE land, upgraded a number of packages, last upgrade was less than an hour ago. Browsing the code in guidance-power-manager right now, there was a python indentation error in it's DCOP interface code for brightness control. Fixing that didn't make the buttons work, however, and I can't see anywhere else besides that and the slider controls where brightness calls to HAL are made. So, still trying to figure it out.. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> ** Changed in: kdebase (Ubuntu) >Status: New => Invalid > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Fix Released I'd like to gently point out that the original reporter of this bug is a KDE user. This makes no sense at all. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;) Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote: > As of today, brightness setting fully works for me on a T60. Anyone > confirming that? Also on a T60 here, still not working for me (in KDE). -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running Kubuntu. Brightness keys do not work even though "lshal -m", "acpi_listen", and acpid all see them/do the right thing. No OSD from kmilo anymore either, for anything, even volume or thinklight which work (probably only because they are done in hardware). This all worked several weeks ago, and has actually always worked up until then. Guidance can still adjust the brightness with the slider. Although it's not related directly to this bug, I tend to think it's not coincidental that my lock (Fn-F2, used to lock the session I think, I didn't use it much), battery (Fn-F3, which used to cause guidance-power- manager to show it's tooltip), suspend (Fn-F4), and suspend-to-disk keys (Fn-F12) do not work right anymore either, and broke at the same time. Their implementations in /etc/acpi and so forth are also all similar, only generating various fake keys (see below). The biggest problem with my troubleshooting is that I can't understand/find information on the big picture, how is this mechanism supposed to work at all to begin with. I seem to remember (although admittedly not infallibly) that the scripts in /etc/acpi used to actually modify the brightness (and perform the other key actions) directly thru /sys or /proc somehow. Now all they appear do is synthesize keystrokes using acpi_fakekey. This works right too, xev for example sees these fake keystrokes (although many of them do not have keysyms). But, is some program supposed to receive these keystrokes and perform the action? Or am I barking up the wrong tree? What is HAL's role, if any, in making this work? After the fake key generation, I lose the trail. Any clues? This is a terrible nuisance because I use(d) these keys frequently. Being night- blinded by your laptop is not cool :) -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
On Thursday 02 August 2007 17:15, yostral wrote: > I can now (from when I could ? I don't know) connect to an wep encrypted > network with NetworkManager, without switching the kill switch button. > But I still need to do that with an unencrypted one. I am also now in the same boat after dist-upgrade. Thinkpad T60 with ipw3945. [EMAIL PROTECTED]:~$ apt-cache show linux-image-2.6.22-9-generic \ network-manager knetworkmanager | egrep '^Ver|^Pack' Package: linux-image-2.6.22-9-generic Version: 2.6.22-9.21 Package: network-manager Version: 0.6.5-0ubuntu7 Package: knetworkmanager Version: 1:0.2~r686534-0ubuntu1 WEP networks connect fine, have to use the kill switch trick on open ones. Additionally, KNetworkManager is now acting funny, the first time I try to select a network after login, I have to tell it to connect to a particular network twice, the first time I select it, the icon just blinks at me and then continues doing whatever it was doing (either automatically connecting to some network I'm not interested in, or sitting there disconnected). Obviously this may be a separate bug, but thought I'd throw it out there. Kyle -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134252] Re: alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip
Confirming on my T60 with 82801G as well, including PCM going missing intermittently. It works fine on -9, broken on -10. Unfortunately I am reluctant to go back to -9 for normal use because of Very Annoying Bug #129226 which is fixed in -10 ! One other detail: the "PC speaker" system bell noise is at normal levels, but I can hear nothing else thru speakers or headphones. -- alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip https://bugs.launchpad.net/bugs/134252 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
Loic Nageleisen wrote: > my conclusion: > - acpi stuff now only generates events and does not takes action anymore > - gnome power manager is the only app currently able to catch these key or > hal events and change brightness accordingly > - there's no app for KDE able to do that > - there's no console app either I agree with this, I posted a similar analysis a month or so ago. In fact, as of a couple of days ago I began working around the problem in KDE by shutting down guidance-power-manager and running gnome-power-manager. If these analyses are correct, then I'm at a loss as to how it seems to be overlooked that Kubuntu appears to have no facility for handling brightness key events, and how the actual brightness-changing functionality got removed from /etc/acpi/events before guidance-power-manager (or whatever) grew a replacement for it. > so one should: > 1. implement this in kde power manager > 2. implement this in a daemon listening for hal events (so that it works in > console mode) > 3. make sure those cooperate so that brightness is not set multiple times for > one keypress Agreed, I'd like to repeat my opinion that having to be logged into your desktop environment to change the brightness of your LCD using *dedicated hardware keys* is less than ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> 1. Exact HW ThinkPad T60 > cat /var/lib/acpi-support/system-product-name 2007C3U > 2. Does these two command (if run from Konsole) change brightness > properly on your laptop? Yes, they do. I get a tooltip over guidance-power-manager's kicker icon about the brightness as well, instead of the KMilo OSD that it used to display the last time it worked. > 3. Does your laptop return same keycodes from brightness up (212) and down (101) Affirmative > .. what does "lshal -m" report when key is pressed? 18:17:49.465: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-up 18:17:49.848: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-down HTH! -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I'm also having this problem, 2.6.22-7-generic, network- manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile. I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it. Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO- CARRIER. I couldn't reproduce this last symptom for this report. HTH, Kyle ** Attachment added: "daemon.log with play-by-play" http://launchpadlibrarian.net/8271391/daemon.log-with-comments.txt -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
On Thursday 02 August 2007 17:15, yostral wrote: > I can now (from when I could ? I don't know) connect to an wep encrypted > network with NetworkManager, without switching the kill switch button. > But I still need to do that with an unencrypted one. I am also now in the same boat after dist-upgrade. Thinkpad T60 with ipw3945. [EMAIL PROTECTED]:~$ apt-cache show linux-image-2.6.22-9-generic \ network-manager knetworkmanager | egrep '^Ver|^Pack' Package: linux-image-2.6.22-9-generic Version: 2.6.22-9.21 Package: network-manager Version: 0.6.5-0ubuntu7 Package: knetworkmanager Version: 1:0.2~r686534-0ubuntu1 WEP networks connect fine, have to use the kill switch trick on open ones. Additionally, KNetworkManager is now acting funny, the first time I try to select a network after login, I have to tell it to connect to a particular network twice, the first time I select it, the icon just blinks at me and then continues doing whatever it was doing (either automatically connecting to some network I'm not interested in, or sitting there disconnected). Obviously this may be a separate bug, but thought I'd throw it out there. Kyle -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134252] Re: alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip
Confirming on my T60 with 82801G as well, including PCM going missing intermittently. It works fine on -9, broken on -10. Unfortunately I am reluctant to go back to -9 for normal use because of Very Annoying Bug #129226 which is fixed in -10 ! One other detail: the "PC speaker" system bell noise is at normal levels, but I can hear nothing else thru speakers or headphones. -- alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip https://bugs.launchpad.net/bugs/134252 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote: > Some package have been updated. > Now the FN-brightness keys work again. Still not working for me in KDE land, upgraded a number of packages, last upgrade was less than an hour ago. Browsing the code in guidance-power-manager right now, there was a python indentation error in it's DCOP interface code for brightness control. Fixing that didn't make the buttons work, however, and I can't see anywhere else besides that and the slider controls where brightness calls to HAL are made. So, still trying to figure it out.. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> ** Changed in: kdebase (Ubuntu) >Status: New => Invalid > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Fix Released I'd like to gently point out that the original reporter of this bug is a KDE user. This makes no sense at all. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;) Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote: > As of today, brightness setting fully works for me on a T60. Anyone > confirming that? Also on a T60 here, still not working for me (in KDE). -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running Kubuntu. Brightness keys do not work even though "lshal -m", "acpi_listen", and acpid all see them/do the right thing. No OSD from kmilo anymore either, for anything, even volume or thinklight which work (probably only because they are done in hardware). This all worked several weeks ago, and has actually always worked up until then. Guidance can still adjust the brightness with the slider. Although it's not related directly to this bug, I tend to think it's not coincidental that my lock (Fn-F2, used to lock the session I think, I didn't use it much), battery (Fn-F3, which used to cause guidance-power- manager to show it's tooltip), suspend (Fn-F4), and suspend-to-disk keys (Fn-F12) do not work right anymore either, and broke at the same time. Their implementations in /etc/acpi and so forth are also all similar, only generating various fake keys (see below). The biggest problem with my troubleshooting is that I can't understand/find information on the big picture, how is this mechanism supposed to work at all to begin with. I seem to remember (although admittedly not infallibly) that the scripts in /etc/acpi used to actually modify the brightness (and perform the other key actions) directly thru /sys or /proc somehow. Now all they appear do is synthesize keystrokes using acpi_fakekey. This works right too, xev for example sees these fake keystrokes (although many of them do not have keysyms). But, is some program supposed to receive these keystrokes and perform the action? Or am I barking up the wrong tree? What is HAL's role, if any, in making this work? After the fake key generation, I lose the trail. Any clues? This is a terrible nuisance because I use(d) these keys frequently. Being night- blinded by your laptop is not cool :) -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
Loic Nageleisen wrote: > my conclusion: > - acpi stuff now only generates events and does not takes action anymore > - gnome power manager is the only app currently able to catch these key or > hal events and change brightness accordingly > - there's no app for KDE able to do that > - there's no console app either I agree with this, I posted a similar analysis a month or so ago. In fact, as of a couple of days ago I began working around the problem in KDE by shutting down guidance-power-manager and running gnome-power-manager. If these analyses are correct, then I'm at a loss as to how it seems to be overlooked that Kubuntu appears to have no facility for handling brightness key events, and how the actual brightness-changing functionality got removed from /etc/acpi/events before guidance-power-manager (or whatever) grew a replacement for it. > so one should: > 1. implement this in kde power manager > 2. implement this in a daemon listening for hal events (so that it works in > console mode) > 3. make sure those cooperate so that brightness is not set multiple times for > one keypress Agreed, I'd like to repeat my opinion that having to be logged into your desktop environment to change the brightness of your LCD using *dedicated hardware keys* is less than ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
On Thursday 02 August 2007 17:15, yostral wrote: > I can now (from when I could ? I don't know) connect to an wep encrypted > network with NetworkManager, without switching the kill switch button. > But I still need to do that with an unencrypted one. I am also now in the same boat after dist-upgrade. Thinkpad T60 with ipw3945. [EMAIL PROTECTED]:~$ apt-cache show linux-image-2.6.22-9-generic \ network-manager knetworkmanager | egrep '^Ver|^Pack' Package: linux-image-2.6.22-9-generic Version: 2.6.22-9.21 Package: network-manager Version: 0.6.5-0ubuntu7 Package: knetworkmanager Version: 1:0.2~r686534-0ubuntu1 WEP networks connect fine, have to use the kill switch trick on open ones. Additionally, KNetworkManager is now acting funny, the first time I try to select a network after login, I have to tell it to connect to a particular network twice, the first time I select it, the icon just blinks at me and then continues doing whatever it was doing (either automatically connecting to some network I'm not interested in, or sitting there disconnected). Obviously this may be a separate bug, but thought I'd throw it out there. Kyle -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> 1. Exact HW ThinkPad T60 > cat /var/lib/acpi-support/system-product-name 2007C3U > 2. Does these two command (if run from Konsole) change brightness > properly on your laptop? Yes, they do. I get a tooltip over guidance-power-manager's kicker icon about the brightness as well, instead of the KMilo OSD that it used to display the last time it worked. > 3. Does your laptop return same keycodes from brightness up (212) and down (101) Affirmative > .. what does "lshal -m" report when key is pressed? 18:17:49.465: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-up 18:17:49.848: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-down HTH! -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134252] Re: alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip
Confirming on my T60 with 82801G as well, including PCM going missing intermittently. It works fine on -9, broken on -10. Unfortunately I am reluctant to go back to -9 for normal use because of Very Annoying Bug #129226 which is fixed in -10 ! One other detail: the "PC speaker" system bell noise is at normal levels, but I can hear nothing else thru speakers or headphones. -- alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip https://bugs.launchpad.net/bugs/134252 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I'm also having this problem, 2.6.22-7-generic, network- manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile. I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it. Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO- CARRIER. I couldn't reproduce this last symptom for this report. HTH, Kyle ** Attachment added: "daemon.log with play-by-play" http://launchpadlibrarian.net/8271391/daemon.log-with-comments.txt -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote: > Some package have been updated. > Now the FN-brightness keys work again. Still not working for me in KDE land, upgraded a number of packages, last upgrade was less than an hour ago. Browsing the code in guidance-power-manager right now, there was a python indentation error in it's DCOP interface code for brightness control. Fixing that didn't make the buttons work, however, and I can't see anywhere else besides that and the slider controls where brightness calls to HAL are made. So, still trying to figure it out.. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> ** Changed in: kdebase (Ubuntu) >Status: New => Invalid > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Fix Released I'd like to gently point out that the original reporter of this bug is a KDE user. This makes no sense at all. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;) Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote: > As of today, brightness setting fully works for me on a T60. Anyone > confirming that? Also on a T60 here, still not working for me (in KDE). -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> 1. Exact HW ThinkPad T60 > cat /var/lib/acpi-support/system-product-name 2007C3U > 2. Does these two command (if run from Konsole) change brightness > properly on your laptop? Yes, they do. I get a tooltip over guidance-power-manager's kicker icon about the brightness as well, instead of the KMilo OSD that it used to display the last time it worked. > 3. Does your laptop return same keycodes from brightness up (212) and down (101) Affirmative > .. what does "lshal -m" report when key is pressed? 18:17:49.465: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-up 18:17:49.848: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-down HTH! -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
Loic Nageleisen wrote: > my conclusion: > - acpi stuff now only generates events and does not takes action anymore > - gnome power manager is the only app currently able to catch these key or > hal events and change brightness accordingly > - there's no app for KDE able to do that > - there's no console app either I agree with this, I posted a similar analysis a month or so ago. In fact, as of a couple of days ago I began working around the problem in KDE by shutting down guidance-power-manager and running gnome-power-manager. If these analyses are correct, then I'm at a loss as to how it seems to be overlooked that Kubuntu appears to have no facility for handling brightness key events, and how the actual brightness-changing functionality got removed from /etc/acpi/events before guidance-power-manager (or whatever) grew a replacement for it. > so one should: > 1. implement this in kde power manager > 2. implement this in a daemon listening for hal events (so that it works in > console mode) > 3. make sure those cooperate so that brightness is not set multiple times for > one keypress Agreed, I'd like to repeat my opinion that having to be logged into your desktop environment to change the brightness of your LCD using *dedicated hardware keys* is less than ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running Kubuntu. Brightness keys do not work even though "lshal -m", "acpi_listen", and acpid all see them/do the right thing. No OSD from kmilo anymore either, for anything, even volume or thinklight which work (probably only because they are done in hardware). This all worked several weeks ago, and has actually always worked up until then. Guidance can still adjust the brightness with the slider. Although it's not related directly to this bug, I tend to think it's not coincidental that my lock (Fn-F2, used to lock the session I think, I didn't use it much), battery (Fn-F3, which used to cause guidance-power- manager to show it's tooltip), suspend (Fn-F4), and suspend-to-disk keys (Fn-F12) do not work right anymore either, and broke at the same time. Their implementations in /etc/acpi and so forth are also all similar, only generating various fake keys (see below). The biggest problem with my troubleshooting is that I can't understand/find information on the big picture, how is this mechanism supposed to work at all to begin with. I seem to remember (although admittedly not infallibly) that the scripts in /etc/acpi used to actually modify the brightness (and perform the other key actions) directly thru /sys or /proc somehow. Now all they appear do is synthesize keystrokes using acpi_fakekey. This works right too, xev for example sees these fake keystrokes (although many of them do not have keysyms). But, is some program supposed to receive these keystrokes and perform the action? Or am I barking up the wrong tree? What is HAL's role, if any, in making this work? After the fake key generation, I lose the trail. Any clues? This is a terrible nuisance because I use(d) these keys frequently. Being night- blinded by your laptop is not cool :) -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I'm also having this problem, 2.6.22-7-generic, network- manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile. I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it. Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO- CARRIER. I couldn't reproduce this last symptom for this report. HTH, Kyle ** Attachment added: "daemon.log with play-by-play" http://launchpadlibrarian.net/8271391/daemon.log-with-comments.txt -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
I'm also having this problem, 2.6.22-7-generic, network- manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile. I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it. Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO- CARRIER. I couldn't reproduce this last symptom for this report. HTH, Kyle ** Attachment added: "daemon.log with play-by-play" http://launchpadlibrarian.net/8271391/daemon.log-with-comments.txt -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Tuesday 02 October 2007 18:26:28 Thomas Sommer wrote: > Some package have been updated. > Now the FN-brightness keys work again. Still not working for me in KDE land, upgraded a number of packages, last upgrade was less than an hour ago. Browsing the code in guidance-power-manager right now, there was a python indentation error in it's DCOP interface code for brightness control. Fixing that didn't make the buttons work, however, and I can't see anywhere else besides that and the slider controls where brightness calls to HAL are made. So, still trying to figure it out.. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> ** Changed in: kdebase (Ubuntu) >Status: New => Invalid > > ** Changed in: gnome-power-manager (Ubuntu) >Status: New => Fix Released I'd like to gently point out that the original reporter of this bug is a KDE user. This makes no sense at all. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Friday 05 October 2007 11:22:41 der_vegi wrote: > Yes, you're right, the marking is counter-productive. > [...] > It might be a HAL bug, but as I am not too much into that stuff, I'll > keep my fingers off marking now. ;) Yeah it seems like we're having to speculate where the problem actually lies because I for one still cannot find any documentation or insight on how it's *supposed* to work. It looks to me like they moved most of the ACPI event-handling functionality out of the /etc/acpi scripts and into gnome-power-manager, guidance-power-manager, or kpowersave which listen for the events via HAL. If that is the case, then neither guidance nor kpowersave seem have any provision at all for handling brightness key events in the first place, so perhaps the modifications to /etc/acpi should be reverted for the brightness keys. On the other hand, this could be dead wrong, in which case, somebody who knows how these subsystems are set up in (k)ubuntu, and/or where to find said information, *please* chime in. And I tend to agree that having to be logged into your DE to change the screen brightness using dedicated hardware keys is... not ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
On Saturday 06 October 2007 15:18:01 Alexander Hunziker wrote: > As of today, brightness setting fully works for me on a T60. Anyone > confirming that? Also on a T60 here, still not working for me (in KDE). -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 145337] Re: Brightness key stopped working after update [Gutsy]
I have the same symptoms as the OP on my up-to-date ThinkPad T60 running Kubuntu. Brightness keys do not work even though "lshal -m", "acpi_listen", and acpid all see them/do the right thing. No OSD from kmilo anymore either, for anything, even volume or thinklight which work (probably only because they are done in hardware). This all worked several weeks ago, and has actually always worked up until then. Guidance can still adjust the brightness with the slider. Although it's not related directly to this bug, I tend to think it's not coincidental that my lock (Fn-F2, used to lock the session I think, I didn't use it much), battery (Fn-F3, which used to cause guidance-power- manager to show it's tooltip), suspend (Fn-F4), and suspend-to-disk keys (Fn-F12) do not work right anymore either, and broke at the same time. Their implementations in /etc/acpi and so forth are also all similar, only generating various fake keys (see below). The biggest problem with my troubleshooting is that I can't understand/find information on the big picture, how is this mechanism supposed to work at all to begin with. I seem to remember (although admittedly not infallibly) that the scripts in /etc/acpi used to actually modify the brightness (and perform the other key actions) directly thru /sys or /proc somehow. Now all they appear do is synthesize keystrokes using acpi_fakekey. This works right too, xev for example sees these fake keystrokes (although many of them do not have keysyms). But, is some program supposed to receive these keystrokes and perform the action? Or am I barking up the wrong tree? What is HAL's role, if any, in making this work? After the fake key generation, I lose the trail. Any clues? This is a terrible nuisance because I use(d) these keys frequently. Being night- blinded by your laptop is not cool :) -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 121439] Re: [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver
On Thursday 02 August 2007 17:15, yostral wrote: > I can now (from when I could ? I don't know) connect to an wep encrypted > network with NetworkManager, without switching the kill switch button. > But I still need to do that with an unencrypted one. I am also now in the same boat after dist-upgrade. Thinkpad T60 with ipw3945. [EMAIL PROTECTED]:~$ apt-cache show linux-image-2.6.22-9-generic \ network-manager knetworkmanager | egrep '^Ver|^Pack' Package: linux-image-2.6.22-9-generic Version: 2.6.22-9.21 Package: network-manager Version: 0.6.5-0ubuntu7 Package: knetworkmanager Version: 1:0.2~r686534-0ubuntu1 WEP networks connect fine, have to use the kill switch trick on open ones. Additionally, KNetworkManager is now acting funny, the first time I try to select a network after login, I have to tell it to connect to a particular network twice, the first time I select it, the icon just blinks at me and then continues doing whatever it was doing (either automatically connecting to some network I'm not interested in, or sitting there disconnected). Obviously this may be a separate bug, but thought I'd throw it out there. Kyle -- [Gutsy]Network Manager Applet can't connect wireless with ipw3945 driver https://bugs.launchpad.net/bugs/121439 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 134252] Re: alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip
Confirming on my T60 with 82801G as well, including PCM going missing intermittently. It works fine on -9, broken on -10. Unfortunately I am reluctant to go back to -9 for normal use because of Very Annoying Bug #129226 which is fixed in -10 ! One other detail: the "PC speaker" system bell noise is at normal levels, but I can hear nothing else thru speakers or headphones. -- alsa mixer channels missing after upgrade to linux-image-2.6.22-10-generic with Intel 82801G HDA chip https://bugs.launchpad.net/bugs/134252 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
Loic Nageleisen wrote: > my conclusion: > - acpi stuff now only generates events and does not takes action anymore > - gnome power manager is the only app currently able to catch these key or > hal events and change brightness accordingly > - there's no app for KDE able to do that > - there's no console app either I agree with this, I posted a similar analysis a month or so ago. In fact, as of a couple of days ago I began working around the problem in KDE by shutting down guidance-power-manager and running gnome-power-manager. If these analyses are correct, then I'm at a loss as to how it seems to be overlooked that Kubuntu appears to have no facility for handling brightness key events, and how the actual brightness-changing functionality got removed from /etc/acpi/events before guidance-power-manager (or whatever) grew a replacement for it. > so one should: > 1. implement this in kde power manager > 2. implement this in a daemon listening for hal events (so that it works in > console mode) > 3. make sure those cooperate so that brightness is not set multiple times for > one keypress Agreed, I'd like to repeat my opinion that having to be logged into your desktop environment to change the brightness of your LCD using *dedicated hardware keys* is less than ideal. -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 145337] Re: Brightness key stopped working after update [Gutsy]
> 1. Exact HW ThinkPad T60 > cat /var/lib/acpi-support/system-product-name 2007C3U > 2. Does these two command (if run from Konsole) change brightness > properly on your laptop? Yes, they do. I get a tooltip over guidance-power-manager's kicker icon about the brightness as well, instead of the KMilo OSD that it used to display the last time it worked. > 3. Does your laptop return same keycodes from brightness up (212) and down (101) Affirmative > .. what does "lshal -m" report when key is pressed? 18:17:49.465: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-up 18:17:49.848: platform_i8042_i8042_KBD_port_logicaldev_input condition ButtonPressed = brightness-down HTH! -- Brightness key stopped working after update [Gutsy] https://bugs.launchpad.net/bugs/145337 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
