/srv/irclogs.ubuntu.com/2009/11/25/#ubuntu-devel.txt

=== Richie is now known as WelshDragon
kirklandcjwatson: okay, no worries; changes reverted, uploaded again00:34
TheMusodtchen: I am awaiting a fix for the ARM FTBFs for pulseaudi obefore I upload it.00:49
TheMusogah typing00:49
dtchenTheMuso: hmm, should pull in http://git.debian.org/?p=pkg-pulseaudio/pulseaudio.git;a=commitdiff;h=f188f05eebcc5c28a5c3d98a35872c2e6c5d625c too00:52
TheMusodtchen: I'm aware of that, but I was asked to drop the arm stuff from debian/rules completely.00:53
dtchenTheMuso: right, didn't know what the plan was for ARM00:53
TheMusoAnd unfortunately, since there is no lucid chroot on the Canonical arm porter, or so I was told at least, I can't test anything myself.00:53
chuckfI have a question about the repos. When the project goes from karmic to lucid is the process simply to create a new repo called lucid from the packages released for karmic and proceed from there?00:58
chuckfthat is simple terms I'm sure, but I just want the general idea00:59
cjwatsonchuckf: approximately, yes - http://wiki.ubuntu.com/NewReleaseCycleProcess for the gory details00:59
chuckfI'll go read a bit, thanks cjwatson00:59
=== dendrobates is now known as dendro-afk
meanburrito920_where can I get the gnome toolchain? I've checked their site but I can't seem to find any info on it.01:26
meanburrito920_or really, a collection of all their build dependencies. I can't build any of their projects because I'm missing some random dependency that I have to hunt down.01:28
meanburrito920_is there a "mega-package" of all the dependencies for building gnome projects?01:28
cjwatsonmeanburrito920_: try gnome-core-devel01:29
mpontillomeanburrito920_: what are you trying to build? try "apt-get build-dep gnome-terminal", for example.01:29
cjwatsonprobably more than you need, but01:29
meanburrito920_I'm trying to build gedit01:30
cjwatson'apt-get build-dep gedit', then :)01:30
mpontilloyes ;)01:30
meanburrito920_cjwatson: wow, thats a lot of packages :)01:30
cjwatsonworks for anything that's already packaged in Ubuntu01:30
cjwatsonmeanburrito920_: like I say, no doubt more than you need - alternatively, just deal with it case-by-case for a while and soon enough you'll have a pretty complete environment01:31
meanburrito920_thanks!01:32
=== dendro-afk is now known as dendrobates
=== micahg1 is now known as micahg
=== dendrobates is now known as dendro-afk
maxbHmm... I think this boot parallelism has been taken a shade too far03:00
maxbMy GDM just started despite fscks still being ongoing03:00
maxb.... including the volume containing my homedir03:00
=== baytes-vm is now known as baytes-vm|sleep
=== jono_ is now known as jono
lamontlifeless: bah.  right04:38
* lamont puts a pasteit on the monitor04:38
jonodidrocks, ping?04:59
=== vorian_ is now known as vorian
didrocksjono: pong06:46
jonodidrocks, hey06:48
jonodidrocks, http://www.jonobacon.org/2009/11/25/introducing-lernid/ :-)06:48
jonoQuickly made this much easier :)06:48
didrocksjono: oh, sweet!06:49
jonoquickly is rocking my world :)06:49
didrocksjono: thanks for the notice ;)06:49
lifelessjono: nice06:50
lifelessjono: there's an IRC component?06:50
didrocksdo not hesitate to open a bug on any whishlist/request you have06:50
jonolifeless, it uses webchat.freenode.net06:50
jonothanks didrocks06:50
jonolifeless, although an embedded IRC widget would be nice06:50
didrockshum, not sure that exists in pure gtk. I'll try to have a look in the next few months if noone has the time06:51
didrocksbut linking with telepathy framework can be nice :)06:52
didrocksI really think that tool can be very handy, good opportunities to contribute there, it rocks jono!06:55
jonodidrocks, thanks pal :)06:55
jonoI wanted to get it out so we can start refining it ready for Ubuntu Developer Week06:55
didrocksright, still some week remaining to polish it06:56
jonoyeah :)06:57
jonoit also means we can file bugs and accept patches :)06:57
jonoso thanks again didrocks, Quickly awesome :)06:57
didrocksthanks to you for you rocking work :)06:57
jonoI also wrote https://edge.launchpad.net/flarebook in Quickly but havent had time to push a PPA yet06:58
jononeed to fix some last remaining bugs06:58
jono:)06:58
didrocksI really promis GPG key setup will be easier in 0.4 :)06:58
ajmitchjono: that looks good :)07:00
jonodidrocks, hehe, sounds good :)07:00
spmjono: my 2c is we need you to attend more events further away more often; oh, and ensure you have a powerplug in your aircraft seat ;-)07:01
jonoajmitch, thanks!07:01
jonospm, lol!07:01
pittiGood morning07:15
ajmitchhi pitti07:16
pittihey ajmitch, how are you?07:16
ajmitchgood, how are you? recovered from UDS?07:17
pittiyes, I did; and I skipped the Ubuflu this time \o/07:17
ajmitchyay!07:17
dholbachgood morning08:01
=== dholbach_ is now known as dholbach
directhexmorning dholbach09:30
dholbachhi directhex09:30
directhexhm. is http://1.bp.blogspot.com/_rihgl8Kfuew/SwqlbBnUxlI/AAAAAAAADW8/Pm2dnGqk-u0/s1600/Screenshot-F-Spot+View.png the kind of thing being talked about in the default apps session at UDS?09:30
dholbachdirecthex: were you asking me specifically? because I wasn't at that session :)09:31
directhexdholbach, more seb128 or pitti i think09:32
dholbachalright09:32
seb128directhex, yes, that change is following the uds discussion09:32
pittidirecthex: pretty much, yes09:32
seb128directhex, we talked with upstream about the changes we need there...09:33
directhexseb128, ah, cool. wasn't sure how much interaction you have w/ stephane09:33
pittimvo: https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-jockey-hotplug-support is ready for review; it's a very short one; I think it's sufficient, but let me know if you want more details09:42
mvopitti: sounds good to me, its short, but the task it needs to do is short as well :)09:43
pittimvo: exactly; main purpose of this is to track progress09:44
=== Tonio__ is now known as Tonio_
LucidFoxpitti, I have a question regarding autosyncing!09:57
pitti!ask | LucidFox09:57
ubottuLucidFox: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)09:57
LucidFoxI've been waiting for two new packages, x11vnc and dbus-c++, to be autosynced from testing for a long while, but it hasn't happened. Any idea why?09:57
pittiLucidFox: I guess none of the archive admins got to it yet09:57
pittiLucidFox: let me start an auto-import run09:58
pittiyep, they are in new-source09:58
StevenKI did an new-source run at UDS, I guess they dropped to testing after that09:59
pittiyay 3.0 packages10:00
StevenKAh ha10:00
LucidFoxNo, before UDS.10:00
StevenKIf they're 3.0, you can't have them yet10:00
LucidFoxHmm, they aren't using the 3.0 quilt format.10:00
LucidFoxIt can still be 3.0 even if it has diff.gz?10:01
* StevenK looks10:01
pittiLucidFox: no, not those particular two10:01
pittithere are just others in the list which are10:01
LucidFoxah10:01
pittiLucidFox: E: x11vnc is trying to override x11vnc_0.9.3.dfsg.1-1ubuntu2 without -f/--force.10:23
pittiLucidFox: apparenty it moved to a new source package?10:23
pittican the ubuntu changes be ditched?10:24
[BIOS]dnivrai am currently looking at logs of Ubuntu Developer Week and have some doubts; which is the IRC channel to ask help on this?10:26
[BIOS]dnivrais it this?10:26
[BIOS]dnivrasomeone please respond: i've been to 4 different channels asking for this in vain10:27
dholbach[BIOS]dnivra: best to just ask your question10:27
cjwatsonand please be patient, IRC is pretty asynchronous and a minute is a very short time to wait for a response10:27
[BIOS]dnivraoh ok10:27
[BIOS]dnivrawell i'm looking at Getting started with Ubuntu Development(right what you took dholbach)10:28
[BIOS]dnivraand am currently configuring pbuilder10:28
[BIOS]dnivrait says i need to add a line to the file ~/.pbuilderrc10:28
[BIOS]dnivrabut i don't have a file thus10:29
[BIOS]dnivrathe logs don't suggest that i need to create one10:29
[BIOS]dnivrado i have to create one or something wrong with my installation of pbuilder10:29
cjwatsoncreate it10:29
[BIOS]dnivrathere's nothing wrong with pbuilder installation is there?10:29
cjwatsoninstalling a package never creates files in your home directory10:30
[BIOS]dnivrawell gnupg did10:30
cjwatsonno, it didn't10:30
cjwatsonrunning the program gpg did10:30
cjwatsoninstalling the package gnupg did not10:30
cjwatsonimportant distinction :)10:30
[BIOS]dnivrai didn't run it!10:30
[BIOS]dnivrajust installed it10:30
cjwatsonsomething did, even if it was not you explicitly10:30
[BIOS]dnivraright10:31
cjwatsonpackages can't mess around in users' home directories - among other things, it tends to break when people are using NFS home directories10:31
cjwatsonso anyway, just create the file10:31
[BIOS]dnivracjwatson: ok thanks10:32
[BIOS]dnivrai keep getting unsafe permissions on ~/.gnupg/gpg.conf. is there some setting i need to change?10:44
johe|workhi, an mantainer of snmpd online?10:50
[BIOS]dnivrai am currently trying to create my gpg key and i keep getting error that unsafe permission on configuration file10:53
[BIOS]dnivrawhat is  exactly wrong with permissions of ~/.gnupg/gpg.conf? I am the owner. Is it something else?10:54
tsimpson[BIOS]dnivra: it needs to be 600 (-rw-------)10:55
tsimpsonand ~/.gnupg/ should be 700 (drwx------)10:56
[BIOS]dnivratsimpson: ok10:56
cjwatsonit's fine for gpg.conf itself to be mode 644, as long as the containing directory's permissions are tight11:00
cjwatsonalso your home directory needs to not be group- or world-writable11:00
siretart`will there be a lucid release for sparc? perhaps lucid-server only?11:01
cjwatsonsame as usual for ports, we'll release whatever CDs work although they won't be supported11:03
cjwatson(by Canonical anyway)11:03
seb128doing sync is no fun nowadays11:04
seb128there is a zillion of v3 sources now11:05
seb128need to edit the list and run sync-source a zillion times11:05
siretart`hm. I hoped that canonical would intend to continue the sparc port. so hardy was the last canonical supported release :-(11:05
siretart`seb128: are you doing ftp-master work right now? could you perhaps cleanup the emacs section confusion? (emacs22 -> universe, emacs23 -> main)11:05
seb128siretart': I'm doing syncs now but I can fix that one, is there a bug about it? is anything in main depending on emacs23?11:06
cjwatsonsiretart`: we announced this some time ago11:07
siretart`cjwatson: ok, seems I've missed it. thanks11:07
siretart`seb128: not that I knew, I was told that it should be handled during regular archive cleanups, but since it hasn't happend yet, I assume that this was wrong.11:08
cjwatsonsiretart`: indeed, 8.04 was not supported on sparc either. https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-March/000400.html11:08
siretart`seb128: I consider it as a 'normal' upstream version upgrade, only that the name of the source package changed11:08
seb128siretart': still it needs something to pull it in main, it's not archive side only11:09
seb128either a seed or a depends11:09
siretart`oh, I see. I'll check that11:09
siretart`seb128: okay, I've updated the seeds in bzr now. anything else I need to do?11:16
wgrantseb128: Why are you blacklisting v3 sources? They shouldn't crash sync-source any more -- they should just be rejected harmlessly later.11:46
seb128"I: imvirt [universe] -> imvirt_0.3.1-1 [universe].11:46
seb128 * command was 'dpkg-source -sn -x /home/lp_archive/syncs/imvirt_0.3.1+svn426-1.dsc'11:46
seb128 [dpkg-source output:] dpkg-source: error: Unsupported format of .dsc file (3.0 (quilt))11:46
seb128E: 'dpkg-source -x' failed for /home/lp_archive/syncs/imvirt_0.3.1+svn426-1.dsc [return code: 2304].11:46
seb128"11:46
seb128wgrant, I keep running into those11:46
wgrantOh.11:46
seb128and sync-source -a stops11:46
seb128any better way?11:47
wgrantThat's because of cocoplum's old dpkg, not lack of LP support :(11:47
wgrantDamn.11:47
seb128cjwatson, elmo: ^ do you know if that's something being worked?11:49
wgrantSorry, I completely forgot that sync-source unpacked the source beforehand, so didn't work around that as well.11:50
seb128wgrant, nothing to be sorry about, thanks for the work you do ;-)11:51
cjwatsonseb128: yes, there's an RT ticket and stuff12:00
ogradtchen, around ? i'm trying to fix the armel patch in debian/rules to clear the FTBFS, but the current bzr branch seems not to be for pulse-0.9.2012:10
ogradtchen, talking about pulse indeed :)12:11
seb128cjwatson, ok thanks12:12
ograTheMuso, ^^^ any hint ? did you guys change the default branch for pulse or is there just an upload of 0.9.21 missing ?12:16
mvoRiddell: hi, there is a new compiz that gets rid of the compiz-wrapper script and does the checks inside the binary itself. do you still use that wrapper for kde4?12:27
Riddellmvo: no we dropped that in karmic, kwin's detections seems to work fine on its own12:28
seb128go go go mvo!12:29
dijmenare grub2 vga/gfxpayload supposed to not work with karmic under no-guestadditions vbox?12:30
cjwatsondijmen: doesn't work particularly well period12:37
cjwatsondijmen: the kernel doesn't know how to display text when started with gfxpayload, so you don't get any text until/unless it manages to bring up a framebuffer12:38
mvoRiddell: great, thanks12:38
mvoseb128: heh :)12:38
dijmencjwatson: is it grub2 only?12:38
seb128mvo, you will get lot of free tea at next sprint or uds if you manage to speed compiz this cycle ;-)12:38
* seb128 hugs mvo12:38
cjwatsondijmen: yes12:41
dijmencjwatson: but I tried vga=792 too. doesn't this mean it's not a gfxpayload issue?12:42
=== jamie is now known as Guest27292
mvoseb128: tea!12:43
cjwatsondijmen: it's complicated :)12:43
cjwatsondijmen: grub2 uses Linux' 32-bit boot protocol, which works differently12:44
cjwatsondijmen: if you use the older 16-bit boot protocol (use the linux16/initrd16 commands instead of linux/initrd), then you may be able to get vga= to work; vga= is implemented by 16-bit code before Linux switches to 32-bit12:44
cjwatsondijmen: vga= doesn't fit all that well with KMS, though, in my understanding, so it probably has a pretty finite lifetime anyway12:45
=== MacSlow is now known as MacSlow|lunch
dijmencjwatson: thank you12:53
zanshinWho can tell me what's up with the rt61pci driver. Since Koala my wifi isn't working any more.13:03
LucidFox"Gwibber is shipping by default in Lucid. Let’s help it make a great first impression."13:05
LucidFoxSo let me get this straight... They're removing GIMP, yet introducing this ridiculously specific application?13:06
ScottKWell GIMP is a pretty specific application too.13:08
dijmenLucidFox: you won't have to use lucid13:08
LucidFoxI'd say image editing is probably a function more demanded by the average user than microblogging.13:09
LucidFoxHow many % of Ubuntu users are going to use microblogging at all, let alone a desktop client for it?13:09
dijmenLucidFox: what's wrong with gwibber? it's small and gets the job done. I don't see why it should be dropped.13:12
cjwatsonmm, gwibber is, to be fair, a fraction of the size of gimp. I'm not sure they should be considered in direct opposition like this (and honestly I have no data on image editing vs. microblogging, I don't know if you do but it isn't obvious to me)13:13
LucidFoxI'm not putting them in direct opposition. :)13:13
cjwatsonI think you did, above13:13
LucidFoxJust, out of all the features that could be shipped with Ubuntu by default, desktop microblogging doesn't exactly seem the most wanted one.13:13
cjwatsonat least it really did come across that way13:13
cjwatsongimp has been pretty much next on the list of things to be dropped from the default installation for quite a while now13:14
dijmenLucidFox: "So let me get this straight... They're removing GIMP, yet introducing this ridiculously specific application?"13:14
cjwatsonnot least because of its size13:15
cjwatsonI'm not 100% happy with it, but it doesn't seem a totally unreasonable decision either13:15
ograf-spot can do basic photo editing ...13:15
Laneyand there's time to get f-spot better13:16
dijmenLucidFox: given a good usefulness/size ratio, any feature could and should make it in the default installation13:16
LucidFoxGranted, you can call me biased because I'm annoyed by the Twitter fad, don't "get" microblogging and don't use it myself. And it's not like I can affect the minds of the people who make these decisions.13:18
dijmencjwatson: does it look like these gfxpayload issues will be fixed any time soon?13:19
cjwatsondijmen: no13:19
cjwatsondijmen: I wouldn't bother with gfxpayload if I were you13:19
cjwatsonat least not for a while13:19
dijmencjwatson: what should I do instead? I love a high-resolution tty!13:19
cjwatsonwe'll be taking a somewhat different approach to framebuffer init in lucid, but making the grub->linux transition smooth basically requires importing KMS code into grub13:20
cjwatsondijmen: use a graphics card for which KMS is supported, or else use vga= with linux16/initrd1613:20
dijmencjwatson: how do I force linux16/initrd16?13:20
cjwatsonwhere KMS is supported, you already get a high-resolution tty out of the box13:20
cjwatsonyou'd have to edit /etc/grub.d/10_linux I think13:20
dijmencjwatson: some text search pattern tip inside 10_linux?13:21
cjwatsonit's not that long. Sorry I'm not going to have time to walk you through it step by step :(13:21
dijmenthank you anyway (actually I was just asking for a relevant word)13:22
cjwatsondijmen: "linux" is accurate but might be considered to be unhelpful ...13:24
dijmen:)13:24
LucidFoxBy the way, why doesn't Ubuntu include an IRC client by default but Kubuntu does?13:25
StevenKLucidFox: It does, it's just hiding.13:26
LucidFoxEmpathy?13:26
StevenKLucidFox: Yup13:26
LucidFoxIts IRC support is even less intuitive than Pidgin's, I think.13:26
dijmenStevenK: then kubuntu has two13:26
LucidFoxKopete also technically has IRC support, yet Kubuntu still ships Quassel separately.13:27
dijmenLucidFox: that's exactly what I meant13:27
Riddellkopete doesn't have irc now13:28
ScottKNot since KDE3 times.13:28
dijmenRiddell: just add an account13:28
dijmenScottK: well, that's because they removed it13:29
* Riddell not quite sure where this argument is going but suspects he and ScottK won it13:32
* ScottK considered suitable replies and came up empty.13:32
Tm_Toh, dijmen is here too13:42
dijmenTm_T: yeah, I'm trying to offer some help13:42
Tm_Tdijmen: I know (:13:45
Tm_Tdijmen: Kopete doesn't have IRC-protocol supported currently because noone is working on it, it's broken13:45
Tm_Tdijmen: thus, Kubuntu has only one client13:46
rgreeningping persia13:50
=== tkamppeter_ is now known as tkamppeter
=== chuck_ is now known as zul
mathiazfree: hi - re bug 484861 - could you update the test case to have more detailed steps?14:02
ubottuLaunchpad bug 484861 in smart "Smart doesn't import proxy information from Landscape" [Medium,Fix committed] https://launchpad.net/bugs/48486114:02
=== MacSlow|lunch is now known as MacSlow
=== robbiew_ is now known as robbiew
=== korn_ is now known as c_korn
fatal^mutt14:56
fatal^err..14:56
tolonugaubuntu dropped hal, but didn't even touch packages depending on hal like "openct" so they are totaly broken now. where can I find information about the hal replacement, so I can fix the package?14:57
sorenhal is still in the archive. What's openct?14:58
cjwatsontolonuga: http://wiki.ubuntu.com/Halsectomy14:59
cjwatsonand indeed, hal is actually still installed by default14:59
dholbachand it's still installed by default, because at least xserver-xorg needs it15:00
cjwatsonI hope this isn't argument by rumour :)15:00
azteechsoren: http://www.opensc-project.org/openct/15:01
cjwatsonI'm puzzled that our openct packages don't depend on hal, if they need it15:02
dijmencjwatson: once I install the kms module, how do I enable it in grub2?15:02
sorenazteech: Ah, opensc I know about :)15:02
cjwatsondijmen: um15:03
azteech:)15:03
dholbachthere seem to be a number of openct bugs, most of which predate any hal/devicekit changes: https://bugs.launchpad.net/ubuntu/+source/openct15:03
cjwatsondijmen: kms isn't a module, and it has no direct support in grub2. Can you reformulate your question?15:03
dholbachit might have been broken before15:03
dholbach(not that it makes things better)15:03
dijmencjwatson: I asked "what should I do instead? I love a high-resolution tty!" and you replied "use a graphics card for which KMS is supported, or else use vga= with linux16/initrd16"... so what do I do now? :)15:04
cjwatsonif your system doesn't already support KMS, you are unlikely to have much luck trying to plumb it in yourself!15:04
dijmencjwatson: so are you sure installing vbox's guest additions won't add KMS support?15:05
tolonugacjwatson: was udev fixed in the meantime or is it still that buggy? we found several issues with udev, so the udev developers at some point asked us to use hal instead, to avoid all those race conditions.15:06
tolonugacjwatson: issue 1: sometimes a script is run by udev, before udev created /dev/bus/usb/nnnn/mmmm so you can't access the device it reports it created. (fork&sleep in background works, but ugly hack).15:07
tolonugacjwatson: issue 2: udev gets kernel signals about a new usb device and about usb interfaces that device has. by the time udev looks at the interfaces of the device, it forgot what the device file name for the device was, so it can't tell that to scripts matching the interface.15:08
tolonugacjwatson: ah,openct doesn't depend on hal, because for serial smart card readers hal is not needed. but for usb it is.15:09
Keybuktolonuga: udev can't forget15:11
Keybukthe device name is basically the only thing that the kernel *tells* udev15:11
tolonugaKeybuk: hu? they broke usb kernel/user space again? the last time I checked the kernel issues seperate events for the device itself and for interfaces it has (e.g. think keyboard with build in smart card reader -> 2 interfaces, 2 extra events), and udev processed them serially - by the time it got the event about the smart card interface it had forgotten what the name of the device was (or maybe even didn't process that event so far, so it knew about an15:13
tolonugainterface without device)15:14
Keybuktolonuga: just about everything you said there is wrong15:14
Keybukperhaps you should say what the problem you're having is15:14
Keybukand I'll try to help15:14
tolonugaok, fine. I want a script to be called everytime a usb smart card reader is plugged in. I have a) listof vendor/product id and b) interface class "b", and need to get called for both types of devices. I need the file name of the /dev/bus/usb/nnnn/mmmm device, and it should be already created (preferably, so I don't need to fork and sleep/loop in the background to wait for it)15:16
Keybuksomething like15:16
tolonugaan udev rule file is at http://www.opensc-project.org/svn/openct/trunk/etc/openct.udev.in - but the udev developers (kay sievers and greg k-h) told us to move to hal, because of the races and problems we had with udev...15:18
davidboyHow do I change my launchpad username in bazzar?15:18
tolonugaso now it is funny ubuntu promotes udev instead of hal (if I understand things right)15:18
KeybukSUBSYSTEM=="usb", ATTR{bInterfaceClass}=="b", ATTRS{idProduct}=="xxxx", ATTRS{idVendor}=="yyyy"15:19
Keybuk^ that should match your device's interface15:19
Keybukworth trying15:19
Keybuktolonuga: when did you ask?  the plumbing layer has been undergoing rapid development over the last few years15:19
KeybukHAL is entirely deprecated now, and expected to go away completely within the next year15:19
tolonugawell 2-3 years ago they started to push us from udev to hal.15:20
Keybukthere you go15:20
Keybuk2-3 years ago is practically a different world as far as this stuff is concerned ;)15:20
Keybuk2-3 years before that we didn't even *have* hotplug15:20
pittiKeybuk: shouldn't you check for ENV{DEVTYPE}=="usb_device" as well? or is SUBSYSTEMS=="usb" sufficient for matching a /dev/bus/usb/... kind of device?15:20
Keybukpitti: implied by checking for bInterfaceClass ;-)15:21
tolonuganot true, I did usb hotplugging with /sbin/hotplug interface in 2001.15:21
pittinice15:21
Keybuktolonuga: I don't remember it being around back then ;)15:21
KeybukI remember hotplug being new and shiny when we did warty15:21
* soren chuckles15:21
Keybukand being one of the first distros to actually use this stuff15:21
jdonglol those were the days15:21
sorenYeah. Good times.15:21
soren:)15:22
Keybukbut we could argue about that, or I could help you fix your problem :)15:22
KeybukI'm easy either way15:22
jdongand no longer mounting devfs...15:22
dholbachI didn't know we had that many historians here :-)15:22
* pitti sheds a tear for pmount15:22
Keybukpitti: Ubuntu contributes upstream product, Fedora rewrites it instead of adopting it?15:22
tolonugawhat about rules like KERNEL=="[0-9]*:*", WAIT_FOR_SYSFS="bInterfaceProtocol" -- still needed? that was for some race protection in udev.15:22
Keybuktolonuga: god no15:23
Keybukthat was kernel race protection15:23
Keybukwe fix those in the kernel now15:23
tolonugashould I simply cross fingers, remove all the old cruft, and hope for fixes in udev/kernel.15:23
Keybuktolonuga: if you're using karmic, you don't need any of that15:23
Keybukso first15:23
KeybukSUBSYSTEM=="usb", ATTR{bInterfaceClass}=="b", ATTRS{idProduct}=="xxxx", ATTRS{idVendor}=="yyyy"15:23
Keybukdoes that match your device?15:23
KeybukRUN+="/usr/bin/touch /tmp/foo" is a good trick15:23
tolonugaI have that rule (see the link I mentioned), and it works - except for the races we sometimes had under load.15:24
Keybukok15:24
Keybukand does $name expand to the /dev/bus/usb name of the interface?15:24
tolonugadoes ubuntu tell me the device file name?in which variable?15:24
Keybuk(if you have that rule)15:24
Keybuktolonuga: $parent oddly enough15:24
tolonuganormal is USB_DEVICEFS15:24
mptrobbiew, that list of USC work items, would it be ok if mvo and I prioritized those on Monday? Or do you want it sooner than that?15:24
Keybukthe ATTRS bit causes a parent match15:24
Keybukso fills the parent device node name into $parent15:25
tolonugaor DEVNAME15:25
tolonugaI can also guess it with "udevinfo" or "udevadm info"15:25
Keybuktolonuga: or you could listen ;)15:25
tolonugaENV{DEVTYPE}=="usb_interface", SYSFS{bInterfaceClass}=="0b", SYSFS{bInterfaceSubClass}=="00", SYSFS{bInterfaceProtocol}=="00" RUN+="@udevdir@/openct_usb"15:26
tolonugais ok?15:26
Keybukno none of that15:26
Keybukthat's not what I said at all15:26
Keybuksee15:26
robbiewmpt: need them this week..have to review Lucid items with mark next week15:26
tolonugaI either have product/vendor id pairs, or I have the bInterfaceClass "b" (then I don't care about product/vendor), so I have two rules for those.15:27
Keybuktolonuga: how about you just do what I said?15:28
Keybuksince I am the Ubuntu udev maintainer15:28
Keybukand an upstream maintainer15:28
Keybukso I know a _little_ bit about this stuff ;)15:28
Keybukso the rule I gave you is probably "correct"15:28
tolonugais there some document, which environment variables are set by udev, or do I simply test and hope the other distributions have it the same way.15:28
Keybuk(modulo some tweeking)15:28
tolonugaah, great to find the man in charge, super!15:28
Keybuktolonuga: all major distributions instead of Debian have the same udev stuff15:29
Keybukexcept Debian, I mean15:29
tolonugaah,ok. that wasn't always the case I remember :(15:29
tolonugacan you have a short look at http://www.opensc-project.org/svn/openct/trunk/etc/openct.udev.in15:29
Keybuktolonuga: that file is for an ancient version of udev15:30
tolonugait is the file we used for a long time,till kay told us to move to hal. it should work still I guess, and maybe we can cut rules no longer needed.15:30
Keybukno, it won't work15:30
tolonugadid udev stay compatible? or do I rewrite it?15:30
Keybukit'll parse that file still15:30
Keybukfor now15:30
Keybukbut it won't work how you want15:30
Keybukthe new rules are much better15:30
tolonuga"writing udev rules" by danial drake on reactivated.net version 0.74 is still authorative, or is that one outdated too?15:31
* pitti gently reminds Keybuk that Debian now has a more recent udev than lucid :)15:31
Keybukpitti: Marco still refuses to adopt the same rules directory as everyone else15:32
Keybuktolonuga: almost certainly massively out of date15:32
tolonugaok. what is my best progress from here? subscribe to hotplug-devel (or whatever list), and post my old rules for review/suggestions for the new ones?15:33
Keybukthat's one approach yeah15:33
KeybukSUBSYSTEM=="usb", ATTR{bInterfaceClass}=="0b", ATTRS{idVendor}=="0b97", ATTRS{idProduct}=="7762", RUN+="/bin/echo /dev/$parent"15:34
KeybukI just used that rule on a random usb device I have here15:34
Keybukudevadm test on the interface gives me15:34
Keybukudevadm_test: run: '/bin/echo /dev/bus/usb/002/005'15:34
Keybukwhich is, I think, what you want?15:34
Keybukthe "S" on the end of ATTRS is the important bit here15:34
Keybukmatch rules without an "S" match the exact kernel object15:35
pittitolonuga: if you split that, one rule tests ATTR{bInterfaceClass}, the  other tests ENV{DEVTYPE}="usb_device", ATTRS{idVendor}=="xxx", .., it should DTRT15:35
Keybukso in that case, we're matching a kernel object in the "usb" subsystem with a bInterfaceClass attribute of "0b"15:35
tolonugaACTION="add" is still there?15:35
Keybukpitti: no, it won't15:35
Keybukpitti: that's the entire point I'm trying to convey here, you _can't_ split these rules15:35
Keybuktolonuga: if you want to run something, yes15:35
pittitolonuga: it's best to write ACTION!="add", GOTO="end" at the top of the file, as you already do15:35
pittiKeybuk: but that's what he's looking for?15:36
Keybukbut right, pitti's advice on the action bit works15:36
Keybukpitti: but that's wrong15:36
* Keybuk rewinds himself15:36
Keybukwe're matching a kernel object in the "usb" subsystem with a bInterfaceClass attribute of "0b"15:36
tolonugapitti: yes, I have that,so was wondering if it should still work.15:36
Keybukthen once we have that match, we have two further ATTRS rules to process15:36
pittiKeybuk: ^ why?15:36
tolonugaor devices with different InterfaceClass (e.g. 0xff), but a certain product/vendor id.15:36
Keybukthese are special15:36
Keybukending with an "S" means "look up parent object"15:36
pittiah, for selecting $parent15:37
Keybukso once we've found a USB 0x0b device, we use ATTRS to look up its idVendor and idProduct attribute to check that's correct15:37
pittibut for ENV{DEVTYPE} you would use $name, not $parent?15:37
Keybukthis matches not only the device, but it's parent15:37
Keybukpitti: ignore DEVTYPE, it's really not important15:37
pittiseems that I need to re-learn udev rules myself15:37
mneptokivoks: thanks for the bug report. i'm on vacaton the next 3 days, but i will try to get one of the Maria core devs to look at the issue before my holiday.15:38
pittiKeybuk: but here we don't know what vendor/product ID should be, if we already have the iface class?15:38
Keybukso now we've matched an interface device, and its actual parent physical device15:38
Keybukthe /dev name of the physical device will be in $parent15:38
ivoksmneptok: thank you!15:38
Keybukpitti: ?15:38
tolonugaso s/SYSFS/ATTR and adding /dev/$parent to RUN+= are the changes I find. done.15:38
Keybuktolonuga: no15:38
Keybukthe important thing is that the matches are both on the same line15:38
pittiKeybuk: iface class=="0b" OR vendor/product match..15:38
mneptokivoks: nema na čemu!15:38
Keybukpitti: not following still?15:38
ivoksmneptok: hahaha15:39
mneptokivoks: please do not try to sort by that last word ;)15:39
pittiKeybuk: I know what you are trying to achieve with "selecting" the right parent with ATTRS, but we don't know what to compare with15:39
Keybukpitti: why not?15:39
ivoksmneptok: true15:39
KeybukI looked at the same rules file as you15:39
Keybukit's easy15:39
tolonugaKeybuk: btw: some while ago the usb developers diskussed obsoleteing some kernel code for usbfs, that would end up putting a lot less info into the uevent received by udev. any idea if that happened?15:39
Keybukjust convert all those SYSFS{}... lines into lines like the one I pasted15:39
pittiKeybuk: you don't know the vendor/product IDs15:40
Keybuktolonuga: some distributions disable it, others don't15:40
tolonugadoes ubuntu keep compiling kernel with USB_DEVICEFS?15:40
Keybukpitti: there's a list of them in the rules file15:40
Keybuktolonuga: I don't think so15:40
pittiKeybuk: right, for those15:40
Keybuk(otherwise I go beat the kernel developers again)15:40
pittibut I'm talking about hte replacement for15:40
pittiENV{DEVTYPE}=="usb_interface", SYSFS{bInterfaceClass}=="0b", SYSFS{bInterfaceSubClass}=="00", SYSFS{bInterfaceProtocol}=="00" RUN+="@udevdir@/openct_usb"15:40
Keybukpitti: that's the rule he needs the parent device for15:41
Keybukwhich is why he needs to write lots of them15:41
Keybukthat should be15:41
pittibut why bother, and not just use DEVTYPE==usb_device?15:41
tolonugaah, in my 2.6.31 from ubuntu it is still enabled. would I change any of these rules if it was disabled on other distros (or would that be a lost case anyway)?15:41
=== dendro-afk is now known as dendrobates
KeybukSUBSYSTEM=="usb", ATTR{bInterfaceClass}=="0b", ATTR{bInterfaceSubClass}=="00", ATTR{bInterfaceProtocol}=="00", ATTRS{idVendor}=="xxxx", ATTRS{idProduct}=="yyyy", RUN+="openct_usb"15:41
Keybukfor each device15:41
Keybuktolonuga: no, these rules are written assuming it doesn't exist15:42
tolonugaso I need $parent only if I match the interface, but not if I match the whole device (with product/vendor id)?15:42
Keybukpitti: because that doesn't help!15:42
Keybukpitti: that matches the device, not the interface15:42
Keybukhe's trying to match the interface15:42
tolonugaATTR{idVendor}=="0529", ATTR{idProduct}=="050c", RUN+="/openct_usb /dev/$parent"15:42
Keybuktolonuga: right, if you just match the device, you don't need the interface stuff or $parent ;)15:42
Keybukbecause you can match it directly15:42
tolonugafor example is for a device without "b" as interfaceclass15:42
Keybuktolonuga: yes, but that only matches the device, not the interface15:42
Keybukthe interface devices may not exist when that happens15:42
tolonugathen the usb device file name is in $DEVNAME? or in which environment variable?15:43
sorenJust add a "sleep 2"15:43
* soren runs away15:43
Keybuksoren: actually, udev will block for the completion of the RUN rule before even processing the interfaces15:43
Keybukso that really won't help15:43
Keybuktolonuga: $name :)15:43
Keybukthough it's often better form to use %N (temporary device node with the same major/minor)15:44
sorenWrite a wrapper script that goes into the background, sleeps for a couple of seconds and then runs the other command. :)15:44
* soren runs away some more15:44
pittiah, *headdesk*15:45
tolonugaKeybuk: temporary might be a problem, since the script runs app A, which has a look at the device and then runs app B, so it still needs to exist then...15:45
tolonugathe best place to put scripts to be run by udev is still /lib/udev/somename ? or some other place?15:49
pittitolonuga: so, Keybuk and I think that your first rule should work with sth. like ATTR{bInterfaceClass}=="0b", ATTRS{idVendor}=="?*", RUN+="foo /dev/$parent"15:52
pittithe vendor/product ones as above15:52
tolonugado I need the vendor if I don't care about it?15:54
pittitolonuga: the ?* means "nonempty"15:54
pittitolonuga: i. e. it means "select the first parent device which has any vendor ID15:54
pittiwhich should be the usb_device15:54
tolonugamy first two rules are:15:55
pitti. o O { sometimes I wish there was an ENVS{DEVTYPE}=="usb_device" ... }15:55
tolonugaSUBSYSTEM!="usb", GOTO="openct_usb_rules_end"15:55
tolonugaACTION!="add", GOTO="openct_usb_rules_end"15:55
tolonugaso I should be clean of non-usb devices. but if you suggest to match the vendor anyway, I can add that.15:55
Keybukpitti: that'll match just abotu every usb device with a comms port ;)15:55
Keybukwhich is pessimal15:55
tolonugadoes it hurt to also match ATTR{bInterfaceSubClass}=="00", ATTR{bInterfaceProtocol}=="00" ? (I do that, as I only support that revision)15:56
pittiwell, with teh subclalss/interface protocol, of course15:56
pittitolonuga: no, you should do that; I was only sketching the form15:56
pittiI don't know if that's tight enough to only select devices you can handle15:56
tolonugaand I have as first test: ENV{DEVTYPE}=="usb_interface", - keep or remove?15:57
pittiI think it's redudant, but harmless15:57
tolonugaok, thanks.15:57
cjwatsondijmen: I don't know how vbox's guest extensions work, I'm afraid; I only use kvm15:58
dijmencjwatson: but from what you know about the way kms works, it's most likely that they can't just enable it on the next reboot, or this is what you implied, right?16:00
cjwatsondijmen: KMS is a major piece of engineering; it requires significant kernel support, not just a switch. I have no information on whether vbox guests support it16:01
dmartHi; can anyone tell me which package gcc's debug symbols are in?  I've tried searching for gcc{,-4.4}.*dbg, but didn't find anything (I do have a suitable ddebs.ubuntu.com entry in my sources list)16:03
primes2hpitti: Hello, when you have time, could you have a look at this bug #441835 please? It should be a permission issue and it should be addressed to Karmic and Lucid too16:03
ubottuLaunchpad bug 441835 in udev "[Karmic] floppy is not working (Ubuntu 9.10)" [Medium,Invalid] https://launchpad.net/bugs/44183516:03
primes2hhttps://bugs.launchpad.net/ubuntu/+source/devicekit-disks/+bug/44183516:04
ubottuLaunchpad bug 441835 in udev "[Karmic] floppy is not working (Ubuntu 9.10)" [Medium,Invalid]16:04
pittiprimes2h: I'll have a look later16:05
primes2hpitti: ok, thank you very much. :)16:05
pittiprimes2h: I can't promise an easy solution; my last floppy went out of the house many years ago, and my neighbor/parents/in-laws don't have one either16:06
pittiso I'll need some more debugging info16:06
pittiprimes2h: do you have one?16:06
primes2hpitti: yes, ask me whatever you want.16:07
primes2hand you need16:07
primes2hpitti: I have some pcs with a floppy device so I can help in debugging.16:10
pittiprimes2h: whatever you want> great! so what is the meaning of live, the universe, and everything?16:15
pittij/k16:15
pittiprimes2h: I followed up to the bug, let's keep the discussion there; I'm subscribed now16:15
primes2hpitti: :D not that "whatever you want" ;)16:15
primes2hpitti: ok16:16
* primes2h don't have supernatural powers yet ;)16:17
pitti42!16:17
primes2hbut he's working on it16:17
pitti(well, it's not actually the answer, but that's now opening a greater philosophical debate about the hitchhiker)16:18
primes2hpitti: lol16:20
=== beuno is now known as beuno-lunch
tormodpitti, can you please take a look at the debdiff in bug 478874?16:40
ubottuLaunchpad bug 478874 in linux-wlan-ng "firmware loading broken with Karmic kernel" [Undecided,Confirmed] https://launchpad.net/bugs/47887416:40
jpds/3/3316:40
mptrobbiew, ok, I'll review them with mvo tomorrow.17:01
robbiewthanks a lot!17:01
mvoRiddell: did plasma/framesvg.h change location? compiz ftbfs currently17:02
mvoRiddell: or kwin? kdecoration.h and friends?17:02
Tm_Tmvo: in which version?17:03
=== beuno-lunch is now known as beuno
mvoTm_T: lucid17:04
=== manny__ is now known as mannyv
Tm_Tmvo: hmm, I cannot tell any change in paths, but perhaps I'm not best one to tell17:06
ScottKmvo: There was a binary incompatible change between Qt 4.6 beta and RC1.  We're in the middle of rebuilding all the affected packages.  Without looking at details, I'd be suprised if anything built that uses kdebase-workspace stuff right now.17:06
ScottKIf that from kdelibs, then it should be rebuilt.17:06
ScottKI don't recall which that bit is in.17:07
mvoScottK: ok, thanks. so I just wait a bit and rebuild?17:07
Tm_TScottK: kdelibs both17:07
Tm_TScottK: mvo: no, kdecoration.h and friends are in kdebase (:17:08
ScottKmvo: Since it's kdelibs, it should be done (as of a couple of hours ago).  If you didnt' try recently, I'd retry.17:08
mvothanks, I will try that17:09
* mvo queues rebuild and goes for dinner in the meantime17:09
pittitormod: hm, the original problem was that the firmware files are shipped in the wrong directory, wasn't it? how does that patch help then?17:10
pittishouldn't the package just move the fw bits then?17:10
* Keybuk does his first package update using bzr and pbuilder17:25
Keybukif I upload using dput, then I have finally changed all of my ways from my Debian days ;)17:25
macodo you normally ftp your files?17:26
ograwhat did you use in debian ?17:26
Keybukdupload17:26
ogradupload ?17:26
ograah :)17:26
* Keybuk iz old skool17:26
ogramorsing ones and zeroes eh to the internet ? :)17:27
* cjwatson still uses dupload, and doesn't see a reason to change :)17:27
tormodpitti, no the files are shipped in the right place for linux-wlan-ng, the original description is a bit misleading17:27
Keybukcjwatson: yes, you you'd still use dselect if you could <g>17:27
cjwatsonwell, yeah :) but dput was really just "rewrite in python because the author hated perl", it's not like it adds much17:28
Keybukdiscovering dput ppa:... was a big win ;)17:28
tormodpitti, moving the files would be a workaround17:28
Keybuk"you mean I don't have to edit .dupload.conf each time I add a new PPA?"17:29
Keybukogra: is there any way to make pbuilder not need sudo all the time?17:30
ograi dont think so17:31
macocant chroot without it, can ya?17:31
ograit uses system dirs for most of its stuff17:31
ograright and it chroots17:31
macomaybe could put your user as NOPASSWD in sudoers for chroot, but that sounds.... :-/17:31
Keybuksudo keeps eating my ARCH=i386 ;)17:31
superm1Keybuk, woah, that works?  (dput ppa:...).  i've been editing dput.cf every time....17:31
Keybuksuperm1: yeah, dput ppa:ubuntu-boot/staging ... dput ppa:scott/ppa ... it's all automatic17:32
superm1i need to figure out what release that started working.  that can simplify some of logic on an automated build box17:32
superm1looks like jaunty according to debian/changelog17:34
Keybukjamesh: there should be a bzr pbd that's like bd but implies pbuilder ;)17:34
cjwatsonKeybuk: perfectly possible to do that in dupload, I'll have you know. :)17:48
cjwatsonit's the kind of thing where if you already have it you might as well leave it there17:49
cjwatson(if anyone's curious, you start off .dupload.conf like this: http://paste.ubuntu.com/327847/)17:50
Davieysuperm1: fancy backporting dput? :)17:53
Davieywe are running hardy.17:53
superm1Daviey, well from reading debian/changelog and looking, it's just changes to dput.cf that enable this stuff17:55
ebroderDaviey: My build machine is Hardy, too. You can put http://paste.ubuntu.com/327854/ in your ~/.dput.cf17:55
superm1we can probably just put it in our dput.cf that we override anyway, and that should do the trick17:55
superm1or what he said :)17:55
Davieysuperm1: eww, i forgot how ugly our dput.cf was.17:57
superm1yeah so this would be much prettier17:58
superm1and not need touching every time there is a new upstream release17:58
Davieythanks ebroder17:58
cody-somervillecjwatson, Keybuk: Is there plans for xubuntu-dev to be setup with upload permissions like kubuntu-dev and mythubuntu-dev?18:05
cjwatsonultimately, yes, we've just not got round to you guys yet :)18:07
Keybukcody-somerville: you basically need to have something like https://wiki.ubuntu.com/Kubuntu/KubuntuDevelopers approved by the TB18:07
Keybukin parallel with sorting out the Xubuntu seed (which hasn't happened yet), if your team decided on your policies, that would speed up the process slightly18:07
* cody-somerville nods.18:11
tormodpitti, I updated the description in 478874 to explain the whole situation better.18:12
pittitormod: hm, I don't understand -- why shouldn't the normal kernel mechanism load the firmware?18:14
tormodpitti, because it is WIP18:14
pittiso it wouldn't work in the karmic package?18:14
tormodpitti, I hope to use it for lucid, but for Karmic it would be better to do it the old way18:15
pittiokay18:15
tormodpitti, it would have been a 2.6.31-only solution18:16
tormodpitti, even with the kernel mechanism working, we would like to have l-w-n working for those non-usb devices18:17
KeybukUndefined subroutine &Getopt::Long::GetOptionsFromArray called at /home/scott/tmp/debhelper-7.4.3ubuntu2/Debian/Debhelper/Dh_Getopt.pm line 79.18:29
Keybukhuh18:29
Keybukwhere do I get that from?18:29
* Keybuk backports perl too18:32
KeybukHow Hard Could It Be?18:33
* Keybuk wonders how anyone survives running an LTS on production machines18:33
Keybukit's soooo out of date :'(18:33
\shKeybuk, don't play with the devil...use only software from the LTS repos ;)18:33
Keybuk\sh: but I want the newer bootchart <g>18:34
Keybukwhich means I need newer debhelper18:34
\shKeybuk, so play with the devil ;)18:34
Keybukwhich means I need newer Perl18:34
\shKeybuk, typical developer ;) always wanting new stuff ;)18:34
KeybukI'm sure this will break something else18:34
Keybukreally, this box is LTS with everything I care about backported from karmic ;)18:34
Keybukso basically karmic18:34
* Keybuk adds the lucid python-cairo into the mix18:35
* sebner proposes to use lucid to Keybuk :P18:37
Keybuksebner: but it's a server! :p18:38
sebnerKeybuk: does this change anything? I'd say no :P18:38
\shKeybuk, pfff ;)18:39
=== paran_ is now known as paran
Keybukhuh19:03
Keybuknow I can't make python-support work19:03
Keybuk\o/19:10
Keybukright, that's all that forced in ;p19:10
Keybukseb128_: that's me moved over to Python bootcharts too19:10
Keybukso I guess we should just kill the java one19:10
Keybukseeing as it doesn't work anyway19:10
tormodwhat emits(?) tty-device-added?19:11
Keybukupstart-udev-bridge19:12
tormodKeybuk, thanks, I was looking through all .conf files but any program can initctl emit anything all the time I guess?19:14
Keybukcorrect19:14
tormodso there is no directory of possible emit sources, I have to strings|grep the exectables?19:15
Keybukright19:15
Keybukapplication authors are "encouraged" to use the "emits" stanza19:15
tormodI just started to look at upstart, because I want to make sure gdm is started _after_ radeon is loaded for KMS19:16
Keybuke.g. /etc/init/mountall.conf19:16
Keybuktormod: radeon creates a graphics (drm) device19:16
Keybuktormod: so gdm already has that19:16
tormodhmm19:16
Keybuk(otherwise this wouldn't work on Intel - and it definitely works there :p)19:17
tormodso the emits stanzas are just decoration?19:17
Keybukyes19:17
Keybukjust documentation19:17
tormodKeybuk, how does that work for cards with no drm ?19:21
tormodanyway, more important: why does it seem like X starts before radeon is initialized here?19:23
tormodand what emits graphics-device-added? udev?19:24
Keybuktormod: same, upstart-udev-bridge19:32
tormodKeybuk, so is the problem that upstart is starting gdm faster than the radeon module can set up its dri stuff?20:10
=== nixternal_ is now known as nixternal
kklimondaAre we going to use glibc 2.11 in lucid?20:16
Keybuktormod: the problem might be that it's assuming you don't have drm ;)20:24
tormodKeybuk, it?20:25
\shupstart is a self maintained entity ;) just like an alien ;)20:26
Keybuktormod: things20:26
tormodfor a second I wondered if you were saying there is a bug in u pstart20:27
Keybukno, shouldn't think so20:28
Keybukthe problem is that we have to support starting X with a drm device20:28
Keybukand starting X without one20:29
Keybukmaybe something odd about the radeon driver means it returns from module init/init_one before actually creating the device?20:29
Keybukso udevadm settle finishes, so gdm starts20:29
Keybukwithout waiting for the drm device20:29
Keybuk(the gdm job waits for the first of drm and udevadm finishing)20:30
\shKeybuk, you should implement a "wait-for <signal>" func ;)20:30
\shstart on (whatever and wait-for <something else needs to be there>)20:31
Keybukthat's exactly what it does20:31
=== wolfe_ is now known as wolfe
Keybukthe problem is it's waiting for one of two things ;)20:31
Keybukand the other thing is happening20:31
Keybuk(assumedly)20:31
=== Ng__ is now known as Ng
Cheeryin ubuntu there are couple of software that's activation is joined into keyboard combos.20:55
CheeryI have a thought about character sheet that starts when I press the SUPER -button.20:56
Cheeryand stays as long as SUPER -button is pressed down.20:56
Cheerythen, when I press any other key while keeping SUPER-button down, I'd like to get characters from that sheet.20:57
dtchenogra: 0.9.21 hasn't been uploaded yet. Luke was awaiting the armel FTBFS fix before uploading, but I guess you beat him to it?20:57
\shT-2m until I shutdown the internet...oh well, only our internet @company20:58
CheeryI'd like to implement such device, any guidance that'd avoid me the maximum trouble?20:58
=== wgrant_ is now known as wgrant
Cheery(ultimately there already exists such software I'm about to implement, though I'd feel good about writing it myself if it doesn't exist)20:59
TheMusoasac, ogra, lp:~ubuntu-core-dev/pulseaudio/ubuntu21:02
seb128hey TheMuso21:04
Cheeryit was sort of a pie in the sky anyway that anybody would answer my question.21:05
Cheeryduring the short time I bothered to wait for it.21:05
TheMusoHey seb128.21:06
Cheerydarn if I'd even know what are those things called in gnome.21:06
Cheerystuff that starts from shortcuts and floats on top of anything running, even opengl apps.21:07
Cheeryand then causes stuff like workspace/active window change or virtual input of characters.21:07
Cheerywell, another example would be XF86AudioRaiseVolume21:11
Cheeryof such program I'd like to come up with.21:12
Cheeryfor looking documentation on those feels quite tricky because I don't know what is those sort of software called.21:12
Cheeryerm. oops.21:13
Cheerythat's a keysym.21:13
=== DrKranz is now known as DktrKranz
Cheerygah, I'm getting sleep, obviously some answers later, memo me or something if you still bother.21:18
Cheerygn21:18
Keybukok21:46
KeybukI really prefer the python bootchart now21:47
* Keybuk finishes hacking useful things into it <g>21:47
chelzkirkland: in the Ubuntu Manpage Repository "locate(1)" is missing from all but dapper: http://manpages.ubuntu.com/cgi-bin/search.py?q=locate23:29
Keybuk                              23:43
Keybukquest pybootchartgui% bzr mark-uploaded23:43
Keybukbzr: ERROR: Unknown target distribution: lucid23:43
Keybuk...23:43
Keybukhuh23:43
Keybukjamesh: ! :)23:44
Keybukerr, wrong james ;)23:44
lifelessKeybuk: could you file that on bzr-builddeb23:44
lifelessalso, we should make sure that 'debrelease' does mark-uploaded for us.23:44
Keybuklifeless: I suspect it knows in lucid23:44
Keybukthe karmic version doesn't23:44
lifelessKeybuk: trunk does.23:48
lifelessKeybuk: still, we should publish a version of it in e.g. bzr PPA with lucid support for karmic.23:49
Keybukyeah23:49
Keybukwant a bug to remind you?23:49
lifelessplease23:51
Keybukseems to be bug #476530 already23:52
ubottuLaunchpad bug 476530 in bzr-builddeb "mark-uploaded fails with "Unknown target distribution: lucid"" [High,Fix committed] https://launchpad.net/bugs/47653023:52
=== robbiew is now known as robbiew_
lifelessk23:52
Keybukhttp://people.canonical.com/~scott/daily-bootcharts/20091120-max.png23:53
Keybukyay23:53
Keybukcropped and annotated charts ;-)23:54
ionNice23:54
Keybukit's not 100% accurate23:55
Keybukit looks for the first point at which the load is < 25%23:55
Keybukand the average load for the next three seconds is < 25%23:55
Keybukso if there's a bit of a blip, it can miss it23:56
Keybukbut it's good enough23:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!