=== 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 [02:10] Still no bind update? Sniff. [02:12] http://lists.debian.org/debian-security-announce/2013/msg00138.html === Ursinha-afk is now known as Ursinha [07:45] 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:52] 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:53] 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] sladen: sure [07:54] sladen: should I file it under "linux-image"? [07:54] 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:55] Whoopie: that'll do for the moment, we can redirect it when the actual issue has been debugged and identified [07:56] Whoopie: is it one of the three hardware keys visible in the top-right (cogs, no-entry, and star-box) ? [07:57] 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:58] 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:59] sladen: that's my mail. ;-) [08:01] Whoopie: so you're the same Peter Meiser as provided the udev patch for the lack of key-up? [08:01] sladen: right [08:01] 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:02] sure [08:03] 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:07] sladen: just mentioned the names in the report. [08:09] Whoopie: can you sudo apt-get install acpidump iasl [08:09] Whoopie: https://wiki.edubuntu.org/BIOSandUbuntu#Buggy_DSDT snippet here for grapping the ACPI DSDT (and if you are interested) decompiling it [08:10] Whoopie: this is the bytecode that is specific to that machine. [08:12] Whoopie: can you attach the acpidump.txt to the bug report [08:12] Whoopie: and then we can go hunting for the hotkey handling code in there [08:13] sladen: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205791 [08:13] Ubuntu bug 1205791 in linux (Ubuntu) "Dell Vostro V131: special keys not working" [Undecided,New] [08:22] Whoopie: ta [08:26] Whoopie: does the ACPI interrupt-count also increase for using the other keys too (i8042 0xee down, and WSMI) ? [08:33] Whoopie: can you attach an lspnp too [08:49] sladen: lspnp attached (btw, SMO8800 is the freefall sensor) [08:51] sladen: the ACPI interrupt only increases for the "not-working" key. [08:51] sladen: but the other 2, it's i8042 [09:46] Whoopie: are you seeing "unhandled WMI event" in the syslog? [11:24] 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:25] The remaining changes in Ubuntu are following: @ eet only Build-Depends on libeina-dev (>= 1.7.7) -> (>= 1.2.0) (builds fine, though) [11:27] and @ eina is bumped on debhelper 9 in Ubuntu (without info in d/changelog, though); in Debian is still on debhelper 6 === doko_ is now known as doko [13:17] sladen: no [13:34] sladen: I also added a WMI dump to the bug report. [16:38] mterry: working on a sunday huh? [16:45] roaksoax, I had some time :) [16:49] mterry: heh :) [18:35] ari-tczew: feel free to sync them, didn't have much time to get those synced with debian after I updated the packages [18:40] rsalveti: ok [19:09] Trying to use bzr to get the raring branch of the gtk+3 sources: this should be possible according to 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 , should I report this as a bug, or am I doing something wrong? [19:16] ajdicks: I can confirm I also get that revision not present error [19:24] penguin42, Is what I did supposed to work? I'm not very familiar with bzr. [19:24] ajdicks: I think so, lp tells you to do exactly that! === 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