=== jbarnes_ is now known as jbarnes_LHR [16:38] can anyone here with an intel gpu change the panel brightness using the panel brightness keys after turning on KMS? [16:39] yes [17:27] no problems here either [17:28] make sure you have acpi video loaded [17:29] i have no randr properties on lvds though [17:30] yeah I think the panel fitting stuff is still pending [17:30] I had wanted to avoid adding brightness props to lvds in the kms case [17:30] since we already have /sys/class/backlight I was hoping it would be the main interface going forward [17:31] but what if i use xdmcp on my laptop? :) [17:32] hyperair: are you on karmic? gnome-power-manager is going through huge changes right now if so [17:33] jcristau: heh, life is hard [17:33] Sarvatt: yeah i'm on karmic. and i noticed it's going through huge changes. [17:33] using devicekit-power and xbacklight instead of HAL now [17:33] cool [17:34] wait, if that's so then xbacklight needs to be installed, right? [17:34] oh looks like it falls back to hal if xbacklight isnt available [17:34] xbacklight goes through randr props afaik [17:37] jbarnes_LHR: more seriously using randr to set the backlight was a nice way to do that without being root i think [17:37] hmm [17:41] jcristau: /sys/class/backlight doesn't have to be root only [17:42] could be console owned for example [17:42] yeah i dont get notifications about backlight level changes anymore and i never got acpi events. no clue how it all works but i guess its handled in the EC directly? I can see the ec registers changing when I watch it while doing it. would having something else mapped to the keys stop that from working maybe? [17:42] Hello, are you the guys who interfered on X to disable completely the ctrl-alt-backspace? [17:42] jbarnes_LHR: fair enough [17:43] marcosRz: no. [17:45] marcosRz: it's disabled by default upstream too :) is adding Option "DontZap" "false" to your ServerFlags in xorg.conf to reenable that big a deal? [17:46] Sarvatt, Actually X currently has disabled the DontZap feature [17:46] =( [17:46] no [17:46] http://bbs.archlinux.org/viewtopic.php?id=73064&p=2 [17:47] marcosRz: and you believe what you read on random web forums? good for you. [17:47] jcristau, is it fake? [17:47] but you can still turn it on [17:48] (**) Option "DontZap" "false" [17:48] xorg-server 2:1.6.99.1+git20090524.12e725d0-0ubuntu0sarvatt (buildd@rothera.buildd) [17:48] marcosRz: killing the server with ctrl-alt-backspace was made an option.. [17:48] Sarvatt, I cant, they disabled completely [17:48] marcosRz: no, they did not. [17:48] I'm running the last X here [17:48] they did it [17:48] =/ [17:49] what jcristau said :) [17:49] sigh [17:49] i wrote the xkeyboard-config patch to make that a layout option, so i should know.. [17:49] xkeyboard-config (1.6.1 - latest) is preventing ctrl-alt-backspace from killing X [17:50] marcosRz: ... and you can set the appropriate option, and you can kill X again. [17:50] why did they disabled? [17:50] http://who-t.blogspot.com/2009/04/zapping-server.html [17:51] jcristau, http://bbs.archlinux.org/viewtopic.php?id=73064&p=1 [17:51] they only disabled enabling it by default, you can still turn it on manually in xorg.conf [17:51] Sarvatt: actually not in xorg.conf anymore :) [17:52] ah really? it's working on git master of xserver here, what changed it away from xorg.conf? [17:53] So its not on xorg.conf anymore... [17:53] Sarvatt: read that url i pasted.. [17:53] alrighty, thanks for the link :) [17:53] I think that they are destroying X [17:54] marcosRz: that's ok, you can fork it [17:54] for the benefits of ubuntu newbies, not even fedora users whant this [17:55] marcosRz: i think you should take your trolling elsewhere [17:55] it was nice talking to you [17:55] I actually not trolling, but questioning the change... [17:56] this isnt even a ubuntu specific issue or problem though, #xorg would be the appropriate place to complain :D [17:59] Just by curiosity [17:59] have you tried setxkbmap -option "terminate:ctrl_alt_bksp" marcosRz? [17:59] Do you guys agree with this change [18:00] Sarvatt, I alread fix it [18:00] I patched X [18:00] ? [18:00] its even easier enabled now than having to change xorg.conf, I like it :) [18:01] I liked so much when It was enabled by default :3 [18:01] But at least this way will prevent newbies to kill X accidently [18:01] It was a good choice, but I hate the convergence that open source projects are taking towards newbies users [18:02] plus you can remap the key combo to whatever you want now [18:02] thats cool :) [18:02] thanks for the patience [18:03] I need to learn to live with newbiews users... [18:03] I did this patch [18:04] Sarvatt, http://pastebin.com/m4ad0ee81 [18:09] Sarvatt, sorry for the trouble :) [18:28] Hmm... after the latest Karmic update, my touchpad now has tapping disabled when my laptop wakes up from suspend. [18:29] Also, any keymap changes I've made with xmodmap are gone. [18:32] what brand touchpad? [18:33] alps [18:34] how'd i know you'd say that? :D [18:35] well, it used to work just fine :) [18:35] now, after resuming, "synclient -l" says "TapButton1 = 0" [18:36] yeah there was some changes in alps in the main driver and a ubuntu patch on top of that [18:37] have you tried gpointing-device-settings? [18:37] its only a recommends so it doesnt install by default but its great [18:39] Well, I used gsynaptics (which apparently is the predecessor). [18:39] With that, I can re-enable tapping. But I'd rather not do it manually every time. [18:40] i think gpointing-device-settings can remember your settings [18:41] yeah it works great in that regard for me, also lets you enable multiple finger stuff [18:45] oh dang, they dropped almost all patches in the latest xserver-xorg-input-synaptics in karmic, was synced from debian [18:45] surprised you had tapping enabled at all before the resume johanbr :D [18:46] oh, that's the problem :) [18:47] there was a similar bug in Intrepid that was fixed by patching gnome-settings-daemon: https://bugs.launchpad.net/gnome-settings-daemon/+bug/280148 [18:47] Ubuntu bug 280148 in gnome-settings-daemon "g-s-d needs to set mouse properties when a new device appears" [Medium,Fix released] [18:48] you can grab this one thats the same but with the patches enabled, https://edge.launchpad.net/%7Ewgrant/+archive/ppa/+sourcepub/639179/+listing-archive-extra or this one if you want to try something newer for some reason https://edge.launchpad.net/~sarvatt/+archive/ppa/+sourcepub/634362/+listing-archive-extra [18:49] johanbr: it's a change in the driver upstream, they disabled tapping completely in the driver by default now and ubuntu has a patch that reenable it [18:49] oh :) [18:49] I just installed the wgrant package. [18:49] I probably need to restart X, right? [18:49] but debian doesn't use that patch and it was automatically synced from debian so the patches were lost [18:50] less patches == good :) [18:51] I'll reboot and test [18:51] brb... [18:51] could just restart hal and rmmod/modprobe psmouse i think [18:51] actually think it restarted hal after the install [18:51] it did [18:51] I'll reboot just to be sure... [18:52] wonder why they disabled tapping anyway, i'll have to dig through the logs [18:55] oh i guess it was always off by default and ubuntu just enabled it :D [18:57] Sarvatt: yep, that works! [18:57] thanks a lot [18:59] no worries, you're like the 50th person thats said something about that in the past few weeks :D that 1.1.99 driver i linked is pretty nice too, it lets you disable the tap and drag feature that was forced enabled always on synaptics before [19:00] I like tap and drag :) [19:02] i set up a keybinding to turn it on and off, i've accidentally moved way too many things in nautilus with it on :D [19:03] got a bad habit of highlighting things as i read it moving text around alot too :)