[00:00] slangasek: not much of a problem in the patch itself ... more about the fact that we try to keep firefox-3.1 branch more or less in sync with our firefox-3.0 branch [00:01] asac: ok, just checking :) [00:01] slangasek: well. one maybe issue is that its a bashism isnt it? [00:01] bryce: mumble, why did xscreensaver 5.07-0ubuntu1 just now appear in the archive with a changelog dated from 28Aug? [00:01] i think its ok to use bash in general, but we tried to prevent that in the past [00:01] asac: %% and ## are not bashisms, if that's what you mean [00:02] those are posix; the bashism is // [00:02] slangasek: ok. then all fine [00:02] slangasek: probably because it had been sitting in the sponsor queue for a long long time [00:02] its just that we also have to look what we can do better in the future. all this is a bit hairy. especially considering that we still have patches that hard code what gets written into gconf for the www-browser user preference :) [00:03] bryce: :/ [00:03] and we would like to have a better $0 ... if possible ;) [00:03] and the changelog lacks any mention of the changed Recommends:, sigh [00:05] bryce: in fact, this upload clobbered the changes from 5.05-1ubuntu2... checking to see if any other fixes went missing... [00:06] nope, just that one [00:10] slangasek: need me to do anything? [00:11] bryce: I've got it, thanks... I'm just my usual grumbly self about regressions introduced in non-obvious ways :) [00:11] slangasek: ok cool, sorry about not catching that. === cr3_ is now known as cr3 [01:53] Heh, the acpi package still uses old-style changelog entries. [02:27] is there an easy way to check what versions of a package were included in a given alpha release? [02:28] bryce: The .manifest [02:28] ah thanks [02:29] hmm, where can I find .manifest's for alpha3 and alpha4? not spotting them immediately on cdimage.ubuntu.com [02:29] or .list if you're looking at alternate/server installs [02:29] they aren't published anywhere unfortunately [02:30] hrm [02:31] I've got a reporter who says an issue did not exist in alpha 3, and started appearing with alpha 4, so to upstream the bug I'd like to translate that into the appropriate package version numbers [02:31] what package do you care about? [02:31] xserver-xorg-video-ati (and xorg-xserver) [02:32] we have an archive of alpha-4 (but for some reason not alpha-3) on antimony [02:32] (hmm, maybe I should start snapshotting version numbers of X packages) [02:32] xorg-xserver> YM xserver-xorg? or xserver-xorg-core? [02:32] xserver-xorg-core [02:33] alpha-4 had xserver-xorg-video-ati 1:6.9.0+git20080802.1f3eee36-1ubuntu1, xserver-xorg-core 2:1.4.99.906-1ubuntu3 [02:33] bryce: you can check dates of uploads corresponding to the release schedule too, if you wanted to. [02:34] yeah, that's probably the easiest approach [02:34] (assumign it didn't get updated terribly often) [02:34] excellent thanks. Yeah from the changelog it looks like we had perhaps 6.9.0-1 in alpha3 [02:34] Hobbsee: yeah that's what I've usually done, but it's a touch ambiguous in this case [02:35] bryce: darn :( [02:35] -ati was updated pretty frequently both by us and debian, and we sync'd from them for much of this cycle so the changelog dates don't necessarily indicate when the package was present in our archives [02:36] but I think this info is sufficient, thanks [02:36] look at the publication dates in LP [02:36] (this is for bug #264462 btw) [02:36] Launchpad bug 264462 in xserver-xorg-video-ati "Radeon Driver fails to load on 2 Sep daily [ATI HD3870]" [High,Triaged] https://launchpad.net/bugs/264462 [02:36] https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati [02:36] ah good point [02:37] you can hover over the date to get an exact date and time [02:38] confusingly when it says "superseded" that gives you the upload time of the *next* package in chronological order in that series [02:38] i.e. it gives you current publication state plus the time when it changed to that state [02:41] hum, interesting [03:05] NCommander: Sure thing. [03:05] NCommander: Which? [03:07] ScottK, we decided not to fix in intrepid (which I don't get but yeah ...) [03:07] NCommander: OK. Wanna update amule? [03:09] New upstream? [03:09] NCommander: Yeah. [03:09] You writing the FFe? [03:09] No, you are. [03:09] I am? [03:09] I'll give it a first ack though. See Bug 260471 [03:10] Launchpad bug 260471 in amule "[intrepid] update aMule to version 2.2.2" [Medium,In progress] https://launchpad.net/bugs/260471 [03:10] Part of what 'update' entails. I just don't have the time. [03:11] Does Launchpad accept .bz2 original tarballs yet? [03:13] ScottK, I think we can simply sync from experimental [03:13] NCommander: I'm fine with whatever works. [03:13] defien 'works' here? :P [03:13] Please steal it from me. [03:14] ScottK, can we straight sync from Debian? [03:14] Meaning people don't wine a motu-release about amule being old again. [03:14] NCommander: Dunno. You tell me. [03:14] from experimental? [03:14] I know we can from sid [03:14] yes, you can. [03:14] It's technically possible. [03:14] But I never requested from experimental [03:14] of course, you can sync it yourself, too. [03:14] * NCommander is seeing if the Ubuntu diverance is still needed [03:14] Hobbsee, some of us aren't MOTU [03:14] NCommander: bribes accepted. [03:14] * ScottK kicks NCommander in the appropriate place to get his application in. [03:15] ScottK, I was told I won't pass the vote until I've been in a full cycle [03:15] (two 0s, and a -1 are likely) [03:15] That's DIF jaunty [03:15] NCommander: Is you have enough sponsors speaking for you, my predication is it won't matter. [03:16] NCommander: if you're unlucky, someone (*glares at Mithrandir) will put you forward anyway. [03:16] Hobbsee, I can be sponsored for MOTUship without doing anything? [03:16] * NCommander got UDS sponsorship that way [03:16] NCommander: If your work and your demonstrated abilities are exceptional. [03:16] NCommander: sure. I mean, you have to talk about it afterwards, but you don't have to be teh first one to send mail applying for it. [03:17] NCommander: oh, you're coming? excellent. [03:18] NCommander: how normal that is, i'm not sure. [03:18] NCommander: oh, and people might just stop sponsoring your stuff, and tell you to apply instead :P [03:24] Hobbsee, then they are only shooting themselves in the foot :-) [03:25] * NCommander is coding in x86 ASM [03:25] Hobbsee, I'm writing my application :-) [03:26] NCommander, AT&T or Intel syntax? [03:27] AT&T [03:27] :-) [03:27] NCommander: I hope that's real mode ASM. None of this flat-memory-model laziness! [03:27] I need it to compile in GAS [03:27] RAOF, thats my core dev application [03:27] This one will simply be an ELF application [03:27] Hrm [03:27] Or [03:27] I could write a amd64 ASM app [03:27] gas can compile Intel syntax too [03:27] Oooh [03:28] That must be a relatively new feature [03:28] You know what you really want to do? Raw CIL! [03:28] Ew [03:30] NCommander, what are you doing in assembly may I ask? I'm learning x86 assembly right now, so maybe can share code or something [03:30] emet, I'm writing my MOTU application [03:30] :-) [03:31] in assembly? O_o [03:31] heh [03:31] Yes [03:31] In assembly [03:31] * Hobbsee wonders if MOTU applications are automatically rejected if they are written in brainfuck. [03:31] Actually [03:31] That idea did cross my path [03:32] But x86 is more like 32-bit brainfuck [03:32] no if you do anything useful in brainfuck that deserves a medal [03:32] mcasadevall@blacksteel:~/motu-application$ gcc test.s -m32 [03:32] /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.3.2/libgcc.a when searching for -lgcc [03:32] Yah know [03:32] Screw it [03:32] brainfuck it is [03:32] * NCommander writes an application to change ASCII strings to brainfuck [03:32] as -o test test.s [03:32] emet, no, I'm on x86_64 [03:32] oh okay [03:32] I mean [03:33] I could write it in x86_asm [03:33] er [03:33] NCommander: Got gcc-multilib installed? [03:33] x86_64 [03:33] emet: i recently saw an application that wrote out the beer song. [03:33] and a few other interesting ones. [03:33] that's cool [03:33] Is there a brainfuck compiler in Ubuntu? [03:33] * NCommander notes that would be a preq [03:33] yes [03:33] Hrm [03:33] x86 asm or brainfuck [03:33] hrm ... [03:33] beef [03:34] !info beef [03:34] :o [03:34] beef (source: beef): flexible Brainfuck interpreter. In component universe, is extra. Version 0.0.6-1 (hardy), package size 7 kB, installed size 60 kB [03:34] NCommander: or both :P [03:34] NCommander: half in one, half in teh other? [03:35] We really have a package with fuck in its description in Ubuntu? [03:36] !info bitchx [03:36] Package bitchx does not exist in hardy [03:36] :o [03:36] That one was removed due to it's consistent security history, IIRC [03:36] NCommander: it's a language [03:36] well, kinda [03:37] notice the size too [03:44] http://www.reghardware.co.uk/2008/10/08/asus_eee_box_virus/ [03:44] nice. [03:44] Ok, I do remember x86 ASM [03:45] * NCommander just managed to write hello world [03:46] emgent: Heh [04:01] hey guys anybody get "wireless event too big" messages in their virtual console running intrepid? [04:02] bug 267063 was filed about it, and i put in my dmesg output in that bug as well [04:02] Launchpad bug 267063 in linux "iwl4965 - wireless event too big (366) and 2.6.27-2 regression" [Medium,Triaged] https://launchpad.net/bugs/267063 [04:03] it still exists in 2.6.27-6 [04:06] is there a console based program to view and edit bugs? or is it best to use Lynx/Links [04:06] Not for Ubuntu. [04:07] Launchpad works pretty well with no css in text based browsers, however. [04:07] ScottK - Thanks [04:08] Scott what text browser is maintained and renders sites the best? Links/Lynx/Elinks [04:08] ? === jamesh_ is now known as jamesh [04:13] jturek: IMO elinks is the best. [04:16] cjwatson: Bug #96435 , I added a comment for you to look at, as maintainer of the bug. I don't know if you get emails at every post. [04:16] Launchpad bug 96435 in oem-config "[apport] oem-config-dm crashed with XStartupError in run()" [Medium,Confirmed] https://launchpad.net/bugs/96435 [06:45] Good morning [06:46] Morning pitti [06:46] ScottK: private bug dups>neither really; I still think we shouldn't make crash bugs public by default === tkamppeter_ is now known as tkamppeter [07:36] i wonder, [07:36] when setting up flashplugin-nonfree, [07:36] it downloads http://download.macromedia.com/pub/labs/flashplayer10/flashplayer10_install_linux_091508.tar.gz [07:36] does it then check some fingerprint? [07:36] because i'm in china, [07:37] and i'm concerned if this download can be altered in the middle by the government [07:37] it checks the md5sum [07:37] Treenaks: what is the source of the md5sum? [07:37] yao_ziyuan: the package [07:38] yao_ziyuan: it checks the md5sum of the .tar.gz first, then of the libflashplayer.so (plugin) file [07:38] and there are 2 md5sums in the postinst in the package [07:39] but does it check the package's fingerprint before checking the .tar.gz? [07:39] the package itself's md5sum [07:39] i think so. [07:39] yao_ziyuan: apt/dpkg checks the md5sum before unpacking the package. [07:39] yao_ziyuan: yes, apt will warn you if the package's GPG signature doesn't match (and won't install the package) [07:40] good [07:40] i just ctrl+break and used sudo torify apt-get install -f to make sure [07:41] yao_ziyuan: it's very hard to get apt to install packages that don't match the md5sum/sha1sum from the (gpg-signed) packages file [07:41] TheMuso: dpkg won't check a sig. [07:41] apt will. [07:41] wgrant: Right, wasn't quite sure where in the stack it is checked, but that makes sense. [07:41] Unless you say yes to the 'COULD NOT BE AUTHENTICATED' warning. [07:41] In which case you are strange. [07:41] wgrant: selectively paranoid :) [07:41] i think displaying a line "md5sum of flashplayer....tar.gz verified" can calm users like me [07:41] TheMuso: dpkg does check the md5sums, but the md5sums in the .deb aren't signed. [07:42] wgrant: yeah true. [07:42] wgrant: but if the hash of a .deb doesn't match the hash in the Packages file, apt will complain even harder than 'could not be authenticated', and just refuse to install [07:42] afaik [07:42] Treenaks: Oh, true. [07:42] Treenaks: It'll give "Hash sum mismatch" [07:42] Or something similar. [07:42] But one can easily enough fake unsigned Packages files. [07:43] just deny access to the signature file [07:43] I think? [07:43] Treenaks: Quite possibly. [07:44] i pay close attention to apps who download executables from their own websites [07:44] like sun java's autoupdate, firefox's check for browser update [07:44] Those apps should generally be shot unless they're apt. [07:44] adobe reader's auto update [07:45] yao_ziyuan: Ubuntu's firefox doesn't do that check, I think [07:45] i know [07:45] Treenaks: It does for extensions. [07:45] extensions are https [07:45] if an extension doesn't use a https update link, firefox will disable updating it [07:47] Ah, good. [07:47] yao_ziyuan: Debian/Ubuntu people tend to be very paranoid about downloaded software as well [07:57] pitti: I get a timeout error trying to give back linux-restricted-modules-lpia, can you wave buildd.py at it? [08:05] StevenK: done, but it's in depwait; nothing to kick here [08:05] pitti: Yeah, it did itself, thanks. [08:23] Hey StevenK [08:49] pitti: hey [08:51] bonjour seb128 [08:51] pitti: the retracer is chocking on bug #279171 [08:51] Bug 279171 on http://launchpad.net/bugs/279171 is private [08:53] pitti: rather the duplicate checking doesn't like it, can't download because needs > 1 value to unpack error [08:55] pitti: is that a known bug? [08:58] seb128: ah, it's because the original reporter changed the description to have stuff below the apport report, fixing [08:58] pitti: thanks! [08:59] seb128: description updated, should work now [09:01] pitti: "Report is a duplicate of #277616 (fixed in version 0.5~beta1-0ubuntu3)" [09:01] pitti: danke schön [09:04] siretart: hey, do you tag bugs for retracing sometime? [09:05] siretart: the retracers are just set up for hardy and intrepid, so no need to tag crash sent before that, launchpad doesn't show who tagged bugs but I came accross an old bug you triaged recently why was tagged for retracing so in case you added the tag [09:10] seb128, Is that a disk space issue, or just convenience? I'd think ideally the retracers would cover all supported releases + the development release. [09:11] persia: the retracer are lot of maintainance work, and eat some gigabytes of ram and load the porter box a lot already [09:11] persia: I'm limited to the intrepid instance and stopping those every now and then to run the hardy ones [09:12] because hardy and intrepid on i386 and amd64 makes the box explode under the load [09:12] seb128: oh, I see [09:12] seb128: what shall I do with failed retraces then? [09:12] it's not worth the trouble to try to set retracers for older version right now seeing how many bugs we can on before hardy versions [09:13] seb128, Completely understood. Thanks for the explanation. [09:13] siretart: clean those manually [09:13] I'm wondering what to do after intrepid though [09:13] we will need to keep hardy, intrepid retracers [09:15] And jaunty. Could more hardware be requested? [09:15] siretart: I usually ask if the bug still happens on the current version and to attach an updated stacktrace or use apport to send a new report if that's the case [09:16] persia: right and jaunty, I was listing the non current versions to have retraced [09:16] persia: not sure if hardware is the reply there, ideally those should be moved to a non porter box and we reworked and optimized [09:17] persia: we are spending way too much time to fix upgrade issues, fighting python-launchpad-bugs which make those crash, etc, it would be nice to have something better [09:18] but that would require somebody have some free cycles to spend on those [09:18] cycles not in sense of ubuntu cycles, just some days should be enough ;-) [09:19] How do the retracers work? Is there source people can fiddle with? [09:19] persia: we are also limited by the availability of dbgsym packages [09:19] pitti, That's an ongoing bug. Haven't we generated -dbgsym for most packages yet? [09:20] persia: we did, but we still don't have them for e. g. gutsy [09:20] seb128: with 'cleaning' you mean 'removing the core dump, unmark the bug as private and ask submitter for a manual retrace', right? [09:20] pitti, Sure. I'm more thinking about the future than the past. [09:20] siretart: right [09:20] siretart: siretart: I usually ask if the bug still happens on the current version and to attach an updated stacktrace or use apport to send a new report if that's the case [09:21] seb128: okay. I've already done so for some bugs in the past. will keep that up for future ones. thanks for notifying me [09:21] siretart: you're welcome ;-) === glatzor_ is now known as glatzor === seb128_ is now known as seb128 [10:21] Hello seb128. Today, the update of ubuntu intrepid shipped a new version of gdm. Could you please tell me whether there was a with the patch supplied in bug#264834, or was there any other problem? [10:23] frafu: hi, looking [10:23] bug #264834 [10:23] Launchpad bug 264834 in gdm "RFE: Add gesture to start onboard and mousetweaks at login (patch supplied)" [Undecided,New] https://launchpad.net/bugs/264834 [10:24] frafu: oh, there is just too many bugs open to keep track of everything, the sponsor team should be subscribed if there is something to sponsor [10:28] ok; I was not aware of it; I just subscribed ubuntu-main-sponsors to it. Correct? [10:29] frafu: right [10:30] thanks [10:31] you're welcome [10:31] the patch will likely be uploaded today [10:31] good news === asac_ is now known as asac === thegodfather is now known as fabbione [11:11] Riddell: could you look if there are more changes for knetworkmanager? there appears to be still a bunch of complains in 259278 [11:11] Riddell: also ... have you tried the kde 4 nm? i think wstephenson said to me that he properly migrated the dbus api to the latest there [11:11] while hschaa only updated a few things he thought were necessary to get the minimum features working again [11:13] there's no new changes in knetworkmanager [11:13] kde 4 nm is still at a very early stage [11:23] ok [11:24] Riddell: is knetworkmanager used at all in kubuntu by default? reason is that i hear quite small amount of noise because of all these knetworkmanager issues [11:25] could also be that most works now and that the noise left is because they have other issues (and just happen to use knetworkmanager) [11:26] does anyone happen to know how the LCD backlight brightness can be adjusted from userspace on Lenovo thinkpads? [11:27] I'm trying to work out what's causing bug 280646 [11:27] Launchpad bug 280646 in linux "ACPI brightness events no longer work on ThinkPad T61" [Undecided,New] https://launchpad.net/bugs/280646 [11:27] * Hobbsee presumes the answer is not function+up? [11:27] or the applet? [11:27] Hobbsee: the bug is that the hotkeys aren't working, so I'm looking for how it's supposed to work behind the scenes [11:27] asac: yes it's the default, it works for me, what's the noise? [11:27] e.g. what command can I run to manually set the brightness [11:28] mdz: ahh. No idea, then :) [11:28] my research so far seems to indicate that it isn't handled in hardware on this model, and something in userspace needs to handle the ACPI event and tell it what to do [11:29] the applet doesn't work either, I guess I can check what that's trying to do [11:29] mdz: Is there anything in sysfs that allows you to tweak it by echoing values to something? [11:29] mdz: no idea on whether it'll work on that particular machine, but editing /proc/acpi/video/VGA/LCD/brightness is supposed to do it. [11:30] ie, sudo echo –n 100 > /proc/acpi/video/VGA/LCD/brightness for full brightness. [11:30] Hobbsee: I thought all that stuff was in sysfs now. [11:30] hobbsee: was just looking at that, will try [11:30] TheMuso: may well be. *shrug*. I already said above i had no idea, so now i'm back to guess work :) [11:30] hobbsee: yep, that works [11:30] Riddell: mostly people claiming that it doesnt work in the bug i posted [11:30] mdz: \o/ [11:31] hobbsee: so the next question becomes, what maze of scripts is supposed to twiddle that value and where is it going wrong? [11:31] mdz: now that one, i really have no idea about... [11:32] I guess it depends on what the fdi files refer to, but stuff like that is in /usr/lib/hal afaiu. [11:34] mdz, What graphics chipset does your T61 have? [11:34] cody-somerville: intel [11:35] 945GM [11:35] sorry, GM965 [11:35] all of my hardware info is on the bug [11:36] mdz: starting point may well be /etc/acpi/thinkpad-brightness-up.sh, but that could be a red herring too. [11:36] hobbsee: that seems to be for ibm-acpi, which is for older/IBM thinkpads [11:36] lenovo ones explicitly don't use those, and use the standard acpi events instead [11:36] ah [11:37] well, you can certainly see if the event is getting generated... [11:37] oh, which you already have. [11:38] now I wonder why I have two VID devices [11:38] one of which works and one of which doesn't [11:43] one relates to actual hardware, and the other doesn't? The scripts are trying to use the one not pointed to real HW? *shrug* [11:45] hobbsee: one is for the onboard graphics, one for the mini-pcie I think [11:45] I'm going to reboot and see if I still have two on an older kernel [11:45] ahhh [11:45] * Hobbsee wonders why a mini-pcie slot counts as a VID device. [11:46] I am trying to figure this out as I go, everything I know is in the bug [11:46] Hobbsee, Perhaps there's an e.g. TV out card in the miniPCIe slot? [11:47] persia: possibly. [11:50] what does m mean in /boot/config-? [11:51] Module [11:52] So CONFIG_ACPI_VIDEO=m in there means that option is enabled? [11:53] cody-somerville, It means a module is built for it, which may or may not be inserted at runtime. [11:53] cody-somerville, lsmod can help determine what is actually inserted at any given time. [11:55] So from http://launchpadlibrarian.net/18362442/ProcModules.txt it looks like CONFIG_VIDEO_OUTPUT_CONTROL and CONFIG_ACPI_VIDEO aren't in there? [12:05] cody-somerville, From the lack of response, I suspect none of us has a handy CONFIG_* -> module name mapping. Maybe? [12:05] you need to look in the relevant Makefile for that [12:10] starting to look like a gnome-power-manager issue [12:20] mdz, Does adding http://pastebin.ubuntu.com/55573/ to /usr/share/hal/fdi/information/10freedesktop/10-laptop-panel-hardware.fdi fix your problem? [12:20] isnt that gone upstream already ? [12:22] cody-somerville: no change [12:22] I just noticed this: [12:22] [12:22] false [12:22] [12:22] but I have /sys/devices/virtual/backlight/acpi_video[01], not acpi_video [12:23] toggling that doesn't fix it though [12:23] laptop_panel.brightness_in_hardware = true (bool) [12:24] cody-somerville: I'm already getting this by default: [12:24] laptop_panel.brightness_in_hardware = false (bool) [12:24] which I believe is correct [12:26] cody-somerville: what do you see in g-p-m --verbose when you use your brightness keys? [12:28] cody-somerville: and lshal -m? [12:28] I get nothing in either [12:28] mdz, Nothing is written. [12:28] cody-somerville: but it works? [12:29] On my laptop on Hardy, yes. [12:29] mdz, matches all that contains that path, so also acpi_video[01] [12:31] this used to work for me, too, and I can't work out where it's broken [12:31] hardy used only half of hal for thinkpads ... the other half was hotkeysetup [12:31] ogra: ah, of course [12:31] cody-somerville: does sudo acpi_fakekey 224 change your brightness? [12:32] Not on my Aspire, no. [12:33] https://bugs.edge.launchpad.net/ubuntu/+source/hal/+bug/267682/comments/86 [12:33] Launchpad bug 267682 in hal "Hotkeys no longer working in Intrepid on Thinkpads" [Critical,Fix released] [12:34] mdz, http://www.nabble.com/T61-Brightness-keys-with-2.6.26-not-working-(NVIDIA)-td18577619.html seems to indicate that enabling CONFIG_VIDEO_OUTPUT_CONTROL and CONFIG_ACPI_VIDEO results in both brightness keys create proper acpi / key events AND change the brightness in both X and console. I assume you've already verified that those options are enabled in your kernel build? [12:35] cody-somerville: they are; that's just video.ko which is loaded and working [12:38] so that person's problem seems to have been a simpler one (no acpi video support) [12:39] mdz, `echo down > /proc/acpi/ibm/brightness` decreases your screen brightness, right? [12:39] cody-somerville: no, I don't have that file. that's for older thinkpads where brightness is handled by firmware [12:40] I have this: [12:40] [ 20.635444] thinkpad_acpi: Lenovo BIOS switched to ACPI backlight control mode [12:40] [ 20.635446] thinkpad_acpi: standard ACPI backlight interface available, not loading native one... [12:40] cody-somerville: and writing 0-100 to /proc/acpi/video/VID1/LCD0/brightness changes the brightness [12:41] cody-somerville: the brightness applet does work [12:45] pitti: this is starting to look like a hal issue; do you have any ideas? (bug 280646) [12:45] Launchpad bug 280646 in hal "ACPI brightness events no longer work on ThinkPad T61" [Undecided,New] https://launchpad.net/bugs/280646 [12:46] smells like hal or gpm wasnt properly prted here ... note that it doesnt use /proc for anything anymore so i'd suspect the proper sysfs translation is missing [12:46] *ported [12:46] mdz, is http://www.klabs.be/~fpiat/linux/debian/Etch_on_Thinkpad_T61.html referring to the old setup or new setup? [12:46] etch is as old as edgy [12:47] mdz, That page reports the issue is fixed in Lenny (and the Lenny page says the brightness stuff just works) [12:47] lenny is somehow like hardy with some intrepid bits, so that might be intersting, though lenny still makes full use of acpi-support etc [12:48] cody-somerville: they're running an older BIOS on that page [12:48] by about 9 months. could be that theirs works differently [12:48] * ogra thinks its hard to compare debian and ubuntu wrt power management [12:50] there must be a sysfs path equivalent to /proc/acpi/video/VID1/LCD0/brightness [12:50] that *should* be what gpm/hal uses [12:50] tkamppeter, is there a way to auto-detect shared network printer (here, a printer server box, sharing 2 printers by lpd) ? [12:51] ogra: isn't that what /sys/devices/virtual/backlight/acpi_video is? [12:52] no idea, i have no IBM hw here, does it do what you expect on console ? [12:52] /actual_brightness there gets changed when I press the keys [12:52] but the display brightness doesn't change [12:53] mdz, did you say that you have more than one laptop_panel device? [12:53] cody-somerville: yes [12:54] can you echo any values or "up/down" into any of the sub files to make it work ? [12:54] like you cn do with /proc/acpi/video/VID1/LCD0/brightness [12:54] iirc the change that gpm and hal completely ignore /proc only came with intrepid [12:55] mdz, Will you try blacklisting video in /etc/modprobe.d/blacklist and rebooting and seeing if that fixes the two laptop_panel device issue? [12:55] so hardy might have had a mishmash reading from /sys and writing to /proc [12:55] ogra: yes, acpi_video1 [12:56] hm, if you change the above mentioned .fdi to match acpi_video1 instead of acpi_video, does it work ? [12:56]