| === sam113101 is now known as sam113101_afk | ||
| === sam113101_afk is now known as sam113101 | ||
| === sam113101 is now known as sam113101_afk | ||
| === sam113101_afk is now known as sam113101 | ||
| trippeh | Still no bind update? Sniff. | 02:10 |
|---|---|---|
| trippeh | http://lists.debian.org/debian-security-announce/2013/msg00138.html | 02:12 |
| === Ursinha-afk is now known as Ursinha | ||
| Whoopie | Hi, does someone of you have contact to a Dell developer. I'm still trying to find out how to get one of my special keys working on my Dell Vostro V131. It doesn't show up as a keyboard or wmi event. | 07:45 |
| sladen | Whoopie: hello Whoopie. Would you be able to file a bug report. I used to do a lot of work on laptop special-keys a few years ago, and there is a large variation in how the keys are implemented; so that it is necessary to know model/revision and sometimes even firmware version. | 07:52 |
| sladen | Whoopie: we can then work through those questions and keep all the details in one place, and work out what the fix is | 07:53 |
| Whoopie | sladen: sure | 07:53 |
| Whoopie | sladen: should I file it under "linux-image"? | 07:54 |
| sladen | Whoopie: can you link to http://www.notebookcheck.net/fileadmin/_migrated/pics/v131tastatur_01.jpg (or a photo of your own machine) in the bug report | 07:54 |
| sladen | Whoopie: that'll do for the moment, we can redirect it when the actual issue has been debugged and identified | 07:55 |
| sladen | Whoopie: is it one of the three hardware keys visible in the top-right (cogs, no-entry, and star-box) ? | 07:56 |
| Whoopie | sladen: yes, it the right one, the middle key works with a udev quirk "keyboard-force-release". I'll post the patch in the bug report. | 07:57 |
| sladen | Whoopie: mjg59 seems to have had a look, I'm just reading through http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg03124.html | 07:58 |
| Whoopie | sladen: that's my mail. ;-) | 07:59 |
| sladen | Whoopie: so you're the same Peter Meiser as provided the udev patch for the lack of key-up? | 08:01 |
| Whoopie | sladen: right | 08:01 |
| sladen | Whoopie: (can you add this to the bug report, and anything else you're also aware of; again so it's all linked in one place) | 08:01 |
| Whoopie | sure | 08:02 |
| sladen | ftp://ftp.dell.com/Manuals/all-products/esuprt_laptop/esuprt_vostro_notebook/vostro-v131_Setup%20Guide_en-us.pdf Page 1 names those keys with the intended MS Windows functionality | 08:03 |
| Whoopie | sladen: just mentioned the names in the report. | 08:07 |
| sladen | Whoopie: can you sudo apt-get install acpidump iasl | 08:09 |
| sladen | Whoopie: https://wiki.edubuntu.org/BIOSandUbuntu#Buggy_DSDT snippet here for grapping the ACPI DSDT (and if you are interested) decompiling it | 08:09 |
| sladen | Whoopie: this is the bytecode that is specific to that machine. | 08:10 |
| sladen | Whoopie: can you attach the acpidump.txt to the bug report | 08:12 |
| sladen | Whoopie: and then we can go hunting for the hotkey handling code in there | 08:12 |
| Whoopie | sladen: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205791 | 08:13 |
| ubottu | Ubuntu bug 1205791 in linux (Ubuntu) "Dell Vostro V131: special keys not working" [Undecided,New] | 08:13 |
| sladen | Whoopie: ta | 08:22 |
| sladen | Whoopie: does the ACPI interrupt-count also increase for using the other keys too (i8042 0xee down, and WSMI) ? | 08:26 |
| sladen | Whoopie: can you attach an lspnp too | 08:33 |
| Whoopie | sladen: lspnp attached (btw, SMO8800 is the freefall sensor) | 08:49 |
| Whoopie | sladen: the ACPI interrupt only increases for the "not-working" key. | 08:51 |
| Whoopie | sladen: but the other 2, it's i8042 | 08:51 |
| sladen | Whoopie: are you seeing "unhandled WMI event" in the syslog? | 09:46 |
| ari-tczew | rsalveti: as you're the last upload of packages of eet und eina, I'd like to ask you whether can we sync these? | 11:24 |
| ari-tczew | The remaining changes in Ubuntu are following: @ eet only Build-Depends on libeina-dev (>= 1.7.7) -> (>= 1.2.0) (builds fine, though) | 11:25 |
| ari-tczew | and @ eina is bumped on debhelper 9 in Ubuntu (without info in d/changelog, though); in Debian is still on debhelper 6 | 11:27 |
| === doko_ is now known as doko | ||
| Whoopie | sladen: no | 13:17 |
| Whoopie | sladen: I also added a WMI dump to the bug report. | 13:34 |
| roaksoax | mterry: working on a sunday huh? | 16:38 |
| mterry | roaksoax, I had some time :) | 16:45 |
| roaksoax | mterry: heh :) | 16:49 |
| rsalveti | ari-tczew: feel free to sync them, didn't have much time to get those synced with debian after I updated the packages | 18:35 |
| ari-tczew | rsalveti: ok | 18:40 |
| ajdicks | Trying to use bzr to get the raring branch of the gtk+3 sources: this should be possible according to <https://code.launchpad.net/~ubuntu-branches/ubuntu/raring/gtk+3.0/raring> by running "bzr branch lp:ubuntu/raring/gtk+3.0", but this gives "bzr: ERROR: Revision {[...]} not present...". Is this because of a failure reported at <http://package-import.ubuntu.com/status/gtk+3.0.html>, should I report this as a bug, or am I doing something wrong? | 19:09 |
| penguin42 | ajdicks: I can confirm I also get that revision not present error | 19:16 |
| ajdicks | penguin42, Is what I did supposed to work? I'm not very familiar with bzr. | 19:24 |
| penguin42 | ajdicks: I think so, lp tells you to do exactly that! | 19:24 |
| === Ursinha is now known as Ursinha-afk | ||
| === Ursinha-afk is now known as Ursinha | ||
| === Guest85887 is now known as LoganCloud | ||
| === mnepton is now known as mneptok | ||
| === Ursinha is now known as Ursinha-afk | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
