[00:08] <bigzero> hey guys, I tried asking this in #ubuntu but no one knew the answer. Having trouble using time command under ubuntu. I'm trying to set the --format flag, but time keeps trying to execute the flags as bash commands. "time -v echo hi" fr instance gives me "-bash: -v: command not found"
[00:09] <Hobbsee> bigzero: are you sure you don't want date?
[00:09] <bigzero> i need to time execution of a program
[00:09] <Hobbsee> hrm, time -v should be supported.
[00:10] <bigzero> it only works with -p flag
[00:10] <bigzero> for me anyway
[00:11] <bigzero> i can't even check the version
[00:11] <bigzero> time -V tried to execute -V in bash
[00:38] <ebroder> Any backporters that could look at LP bug #323546?
[01:25] <zed> nvidia driver spose to work with jaunty yet ?
[03:19] <error404notfound> hi!
[03:20] <error404notfound>  any idea on how to develop a web ui which shows a lists of softwares like add/remove or adept does from the repositories? something like appnr.com but after striping the install part
[04:05] <slangasek> pitti: the hal-info stuff you've added to Hotkeys/Troubleshooting still doesn't match up for my thinkpad hotkeys
[04:06] <slangasek> pitti: if I hit the ThinkVantage button, showkeys -s shows '0xe0 0x1f 0xe0 0x9f'
[04:06] <slangasek> pitti: and the hal-info fdi file has:
[04:06] <slangasek>         <append key="input.keymap.data" type="strlist">0x17:prog1</append> <!-- ThinkPad/ThinkVantage button -->
[04:06] <slangasek> (which works)
[04:43] <stooj> I'm trying to install jaunty (alpha 2 I think) and not getting very far. Can anyone tell me how to debug the installer to figure out what's going wrong (and submit a bug report)?
[04:47] <slangasek> stooj: for starters, I would recommend that you not use alpha2, which is superseded by alpha3
[04:48] <slangasek> stooj: then, you should check http://www.ubuntu.com/testing/jaunty/alpha3 to see whether it's a known bug
[04:48] <slangasek> and if not, you probably want to ask #ubuntu-installer rather than here
[04:49] <stooj> Perfect - many thanks slangasek
[04:49] <slangasek> no problem
[04:52] <Yasumoto> stooj: https://wiki.ubuntu.com/DebuggingUbiquity
[04:56] <slangasek> pitti: oh, I see; you're saying to grab the info from input-events output, but 'code' and 'value' are always 0 for me...
[05:13] <stooj> Thanks Yasumoto
[06:00] <slangasek> bryce: I believe the reference in https://wiki.ubuntu.com/Hotkeys/Architecture to nvram-only hotkeys is obsolete because the thinkpad_acpi driver is supposed to fix these up; do you have any information to the contrary, perhaps specific to older models?
[06:23] <slangasek> anyone have any guesses why in jaunty I would have sound coming out on one channel, whether or not pulseaudio is running and alsamixer showing both channels set at the same level, and then the problem would fix itself sometime overnight with an intervening suspend/resume cycle?
[07:23]  * slangasek eyes http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html - if this is an example for a "fictional IBM laptop", why are we shipping it? :-)
[08:05] <pitti> slangasek: ThinkVantage change> in hal-info? sure, go ahead; for bonus points, send the patch to hal@lists.freedesktop.org; but I'll commit it upstream either way
[08:30] <tjaalton> uh, what exactly is the point of hwtest-gtk.postrm?
[08:31] <tjaalton> it just tries to include itself
[08:31] <tjaalton> hmm no
[08:31] <tjaalton> sorry
[08:31] <tjaalton> but if hwtest has already been removed, it'll fail to remove itself
[08:31] <tjaalton> since hwtest.postrm is no longer there
[08:33]  * calc is going to attempt to upgrade to jaunty at the sprint
[08:53] <IntuitiveNipple> What would be package version to use for a bug-fix for an existing release update (x.y.z-0ubuntu3.8.04.1) ?
[09:07] <liw> IntuitiveNipple, my guess would be x.y.z-0ubuntu3.8.04.2
[09:08] <IntuitiveNipple> hmm... yeah, but .2 is gone so currently I'm guessing at .3  - the thing is, I need to create several debdiffs to address several different bugs in the same package, so its got a bit confusing
[09:13] <pochu> IntuitiveNipple: why don't you fix all bugs in the same debdiff?
[09:15] <liw> version numbers are per upload, and whoever uploads it, can apply several debdiffs before uploading one version
[09:15] <IntuitiveNipple> pochu: Because I'm posting debdiff patches to each bug report
[09:16] <IntuitiveNipple> liw: Ahhh... that would make sense then! I'll set them all to .3 for the Hardy package. Intrepid and Jaunty will be easier (I hope)
[09:18] <pochu> IntuitiveNipple: you can paste one with all fixes in one report, saying the debdiff also closes the other bugs. I think that will be easier for the sponsor and the SRU team
[09:19] <IntuitiveNipple> pochu: Yeah, but I'd rather keep them separate since some might not be considered for SRU
[09:19] <IntuitiveNipple> I'll keep that in mind though, if that happens with another package
[10:15] <davmor2> tseliot: Is Nvidia still on the blacklist?  I'm doing a kubuntu install from 20090202 on an nv based machine and nothing is showing up in Hardware Drivers...
[10:17] <tseliot> davmor2: no but the drivers were uploaded yesterday and the blacklist was removed. Maybe you should just wait for the new drivers (or for the new jockey) to be available on the servers
[10:18] <davmor2> tseliot: Ah okay I saw the fix on the bug report and assumed it would be in place but it's not yet.  Thanks for the info though :)
[10:19] <tseliot> np
[10:32] <gnomefreak> tseliot: nvidia seems fixedatleast i am now able to install it but for some reason it upgraded nvidia drivers that i didnt hve installed
[10:32] <tseliot> gnomefreak: ?
[10:33] <gnomefreak> tseliot: one sec im gonna pastebin it
[10:33] <gnomefreak> tseliot: http://pastebin.mozilla.org/614813
[10:34] <tseliot> gnomefreak: the modaliases are not drivers
[10:34] <tseliot> gnomefreak: they only enable jockey to detect which driver supports your card
[10:35] <gnomefreak> tseliot: oh ok
[10:35] <gnomefreak> tseliot: thanks
[10:35] <slangasek> tseliot: did you need a sponsor for the xfree86-synaptics-driver upload?
[10:35] <tseliot> np
[10:36] <tseliot> slangasek: I asked tjaalton to upload it therefore I think he will upload it sooner or later
[10:36] <tseliot> thanks for your offer
[10:36] <slangasek> tseliot: in that case, I think calc is volunteering to upload it sooner ;)
[10:38] <tseliot> slangasek: ok
[10:49] <gimpuzmani> hi
[11:09] <calc> tseliot: package uploaded
[11:10] <devcow> hi guys, where i can find some infos on clipboard function on gnome desktop? i want to fetch a file which will then imported by a applocation. i only need the file name with path from clipboard, i want to automate some stuff.
[11:10] <tseliot> calc: thanks a lot
[11:11] <calc> tseliot: thank you :)
[11:11] <calc> tseliot: i upgraded to jaunty today and saw my touchpad closing anything i touched ;-)
[11:11] <calc> so the patch was very helpful :)
[11:12] <tseliot> calc: I'm glad to read that it works for you
[11:12] <calc> tseliot: i've only been testing it for a few minutes but it seems to work better already
[11:12] <tseliot> :-)
[11:13] <calc> i had thought i had lost my mind and was doing it until slangasek mentioned the bug report to me
[11:13] <tseliot> hehe
[11:13] <maxb> How on earth did so much manage to break in one driver update :-/
[11:14] <slangasek> calc: heh, I thought I had managed to break my hardware ;)
[11:14] <calc> maxb: from version 0.15 -> 0.99 is how ;-)
[11:15]  * maxb contemplates bisecting
[11:16] <calc> tseliot/maxb: if you need more sponsoring wrt synaptics just send me an email or try pinging me on irc
[11:17] <tseliot> calc: ok, great, thanks
[11:36] <gimpuzmani> hello
[11:38] <hyperair> could someone sponsor a SRU for me please? https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/263779
[11:39] <hyperair> intrepid task has been added, but nobody's approved it
[11:45] <gimpuzmani> hi
[11:45] <gimpuzmani> I'm the editorial writer and designer of the official Ubuntu-TR Community E-Magazine SUDO
[12:20] <EagleScreen> hello, i am trying to upload a package to my PPA, using dput
[12:21] <Hobbsee> and you want #launchpad for questions about ppa.
[12:21] <EagleScreen> i run this:
[12:21] <EagleScreen> $ dput my-ppa usb-creator_0.1.11ubuntu1~ppa1_source.changes
[12:21] <EagleScreen> No host my-ppa found in config
[12:21] <EagleScreen> ok thanks
[12:22] <Hobbsee> EagleScreen: and FYI, you want to follow each step in the PPA start guide, but #launchpad can help you further
[12:23] <EagleScreen> i am following now this guide: https://help.launchpad.net/Packaging/PPA#Adding%20a%20PPA%20to%20your%20Ubuntu%20repositories
[12:24] <Hobbsee> EagleScreen: Please see https://help.launchpad.net/Packaging/PPA#Uploading
[12:25] <Hobbsee> (yes, that's the same guide, but a different section)
[12:27] <EagleScreen> yes that is which I was reading, but i have problems following these steps
[12:27] <Hobbsee> then talk to #launchpad, because we don't do their support here ;)
[12:27] <EagleScreen> yes, ok
[12:32] <EagleScreen> i have made a change in debian/control in usb-creator package, i have changed depends on gksu by gksu | kdesudo | sudo to can install it in KDE without installing much Gnome stuff by gksu dependences
[12:33] <Riddell> we really should find a generic solution for that sort of issue
[12:34] <directhex> Riddell, use Provides: more?
[12:35] <Riddell> directhex: well applications have to know what binary to run
[12:35] <directhex> provides and alternatives!
[12:35] <directhex> isn't there an xdg binary for su?
[13:05] <Riddell> directhex: no, but it would be nice
[13:06] <directhex> make it so!
[13:06] <pochu> there is, but not packaged
[13:06] <pochu> xdgsu
[13:07] <directhex> see, pochu already did it for you. that was fast!
[13:07] <pochu> http://lists.freedesktop.org/archives/portland/2008-May/001054.html
[13:07] <pochu> unfortunately I got no replies to that mail...
[13:18] <ScottK> Riddell: Isn't that what su-to-root is for?
[13:28] <pochu> ScottK: that's Debian specific and thus can't be integrated upstream
[13:29] <pochu> xdgsu would be suitable for upstream if it was shipped and packaged everywhere
[13:29] <ScottK> True, but the specific context there was Debian packaging.
[13:29] <pochu> it's in universe anyway
[13:29] <ScottK> That would be better.
[13:29] <pochu> (menu package)
[13:29] <ScottK> That can change.
[13:30] <ogra> seb128, meh, just doing an upgrade intrepid->jaunty, i think the old /etc/login.defs conffile bug (where gnome-system-tools have changed tabs against spaces) is back
[13:31] <ogra> -UID_MIN 1000
[13:31] <ogra> -UID_MAX 60000
[13:31] <ogra> +UID_MIN			 1000
[13:31] <ogra> +UID_MAX			60000
[13:31] <directhex> awesome
[13:36] <slangasek> apw: https://wiki.ubuntu.com/Hotkeys/Troubleshooting
[13:37]  * ogra wonders if its normal that all dbus using apps just crash during a dist upgrade
[13:37] <ogra> NM obviouslsy tells me networking is deactivated, g-p-m tells me it has no access to any data
[13:38] <ScottK> dbus restarts are not typically handled well
[13:38] <ogra> well, then update-manager should prevent it from restarting until its completely done
[13:39] <ogra> just having all your applets die looks quite weird
[13:39] <ogra> s/die/switch to something nonfunctional/
[13:39] <mvo> ogra: well, that is really something that the dbus package needs to handle
[13:40] <ogra> mvo, i ndoubt it can ... it might be able to grow a hook that u-m can trigger though i guess
[13:40] <ogra> like it does if you install it in a chroot ...
[13:43] <ogra> so it delays the restart
[14:01] <mpt> slangasek, reported bug 324304. Feel free to add details (e.g. a more common example than your PAM tool, if you know one). :-)
[14:02]  * StevenK sighs how mesa failed to build on every arch aside from i386, amd64 and armel
[14:05] <StevenK> bryce_: Fix mesa? :-)
[14:09] <slangasek> mpt: \o/ \o/
[14:12] <tjaalton> StevenK: no, the ports just need a newer kernel
[14:15] <StevenK> tjaalton: Oh, argh
[14:16] <StevenK> tjaalton: And mesa doesn't even die if it's not 2.6.28?
[14:19] <StevenK> tjaalton: And mesa doesn't build depend on linux-headers?
[14:22] <IntuitiveNipple> Any tracker package experts around?
[14:30] <IntuitiveNipple> If an existing package has a bug that writes an incorrect value into the per-user sqlite database, is it permissible to add a postinst script in the fixed package to scan all homes and update each affected user database?
[14:33] <LeonWP> hi
[14:34] <LeonWP> I need to talk to someone who developed the cryptroot scripts from initrd
[14:35] <LeonWP> how can I find out who this is? :)
[14:36] <IntuitiveNipple> check the package's debian/changelog and debian/control
[14:37] <LeonWP> hm how could that package be called?
[14:38] <hyperair> LeonWP: how about dpkg -S /path/to/initscript
[14:38] <LeonWP> thanks
[14:39] <hyperair> LeonWP: cryptsetup
[14:41] <LeonWP> thank you
[14:42] <tjaalton> StevenK: no, probably should though since it sources drm.h
[14:43] <tjaalton> and it's linux-libc-dev it should bdepend on
[14:46] <StevenK> tjaalton: Oh, right. linux-libc-dev
[14:59] <rainmanp7> :)
[15:04] <rainmanp7> Does anyone know if the kernal can probe for a device scan it and chuck information at it and see if it responds to those certin calls ?
[15:05] <rainmanp7> I'm thinking of writing a script to probe a device for somthing and I want it to tell me if that device can do that or has that capability\
[15:05] <rainmanp7> and have the sciprt write it to a file
[15:06] <IntuitiveNipple> rainmanp7: You'd need to create a simple device driver to probe hardware. What do you mean by "device" ?
[15:07] <rainmanp7> Is there a way to just make a call to -> probe it via a script and have it write the information to a file on the desktop ?
[15:07] <rainmanp7> a simple device driver :)
[15:09] <rainmanp7> device = any piece of hardware -> chipset/Video Card/USB/Hard Drive Controller/mouse/keyboard
[15:13] <kirkland> slangasek: http://people.ubuntu.com/~kirkland/search.html?cof=FORID%3A9&cx=003883529982892832976%3Aly2fmeg302s&q=rfkill+iwl+resume&sa=Search
[15:13] <IntuitiveNipple> rainmanp7: No, you'd have to work with the individual driver and what it exposes (check the /sys/* file-system)
[15:14] <rainmanp7> IntuitiveNipple thank you I'm starting to remember things from long ago :)
[15:14] <IntuitiveNipple> rainmanp7: You might try the hal database
[15:18] <IntuitiveNipple> rainmanp7: You might want to check out the bin/ executables in the hal package; things like  hal-find-by-property
[15:20] <rainmanp7> IntuitiveNipple tyty I remember allot thank you
[15:23] <ogra> pitti, hmm, the rfkill thing seems to be asac's fault, not yours :)
[15:24] <pitti> ogra: dmesg should tell you, it has some stuff on disabling /enabling usually
[15:24] <ogra> if i manually disable networking in NM and re-enable it again it works fine .... the actual key pressing switches the interface off and on fine
[15:24] <ogra> just NM doesnt re-associate afterwards
[15:25] <ogra> though i get the "unknown atkbd key" message for all my Fn based keys
[15:25] <ogra> seb128, scrolling works fine if i use the right mouse button ...
[15:26] <ogra> bryce, ^^^ thats why it worked for you, you accidentially used the right one
[15:37] <calc> bryce: ping
[15:37] <calc> bryce: http://lists.go-oo.org/pipermail/dev-go-oo.org/2009-February/001077.html
[15:41] <calc> bryce: and the ooo bug i am seeing does indeed have the gdk_x11_get_server_time in the stack
[15:44] <calc> bryce: can you get that patch in like today? ;-)
[15:44] <calc> bryce: i'm getting lots of bug reports about it on OOo and alpha 4 goes out thursday
[15:45] <slangasek> calc: LP bug number for that?
[15:46] <calc> slangasek: one of them is lp 322425
[15:47] <calc> slangasek: i have several others that i think are the same issue but not 100% certain
[15:47] <slangasek> hum, but still marked 'incomplete'?
[15:48] <calc> slangasek: yea i just found out the cause right before pinging bryce
[15:48] <slangasek> ok
[15:50] <calc> i've updated the bug now
[16:31] <Chipzz> 15:30 < IntuitiveNipple> If an existing package has a bug that writes an incorrect value into the per-user sqlite database, is it permissible to add a postinst script in the fixed package to scan all homes and update each affected user database? >> It certainly is not
[16:31] <bryce_> calc, slangasek: ok, fix looks good and applies, just checking that it builds before uploading.
[16:31] <slangasek> cheers
[16:31] <bryce_> libx11 takes a while to build
[16:31] <IntuitiveNipple> Chipzz: So, how would the existing database be fixed?
[16:32] <Chipzz> not from the postinst
[16:32] <IntuitiveNipple> okay... so how?
[16:32] <Chipzz> packages are not allowed to touch other packages config files, or files in user home directories
[16:33] <Chipzz> no idea
[16:33] <Chipzz> but
[16:33] <Chipzz> let's say you have homedirs on a network drive
[16:33] <Chipzz> which get automounted when the user logs in
[16:33] <Chipzz> your approach breaks
[16:33] <Chipzz> worse
[16:33] <Chipzz> if the network drive is used by multiple machines
[16:33] <Chipzz> your update may run more than once
[16:34] <Chipzz> or you may have other boxes where you still have an old version where the breakage hasn't occured yet
[16:34] <bryce_> calc, slangasek:  uploaded.  Please update and verify it solved the issue, when you get a chance.
[16:34] <IntuitiveNipple> the db *belongs* to the buggy package
[16:34] <Chipzz> which is why your approach is totally unacceptable ;)
[16:34] <calc> bryce: ok
[16:35] <Chipzz> you said per-user, so I'm assuming the db you mention is in the users' homedir
[16:35] <IntuitiveNipple> I wasn't *my* approach; I was asking if that was permissible, since otherwise something has to be done for each user log-in
[16:35] <Chipzz> well, it isn't ;)
[16:35] <pochu> IntuitiveNipple: you cannot touch files in the users' home directory
[16:36] <IntuitiveNipple> Chipzz: indeed, it's the trackerd ~/.local/share/tracker/db/common.db
[16:36] <pochu> IntuitiveNipple: the application could though
[16:36] <joaopinto> IntuitiveNipple, the usual approach for touching home dirs, is to have the launching script check the running users home dir, that is a regular behavior
[16:36] <Chipzz> best approach would be to patch the application to fix it when it starts?
[16:36] <IntuitiveNipple> pochu: So, how do we *fix* the user's broken db in the updated package?
[16:36] <IntuitiveNipple> hmmm
[16:36] <pochu> IntuitiveNipple: upstream could fix it in the code
[16:37] <pochu> but you are not allowed to do so in the package maintainer scripts
[16:37] <pochu> e.g. when trackerd is started it checks the database and if it's broken, it fixes it and continues
[16:37] <pochu> vinagre does that for example, to migrate a file to the new conf location
[16:38] <IntuitiveNipple> pochu: I posted the bug-fix upstream and it has been committed. However, their trunk code has been refactored and our tracker 0.6.6 codebase is very different in this respect. Fixing the source doesn't solve the existing-values-in-db issue
[16:38] <pochu> (not with a db though, but you see the point)
[16:38] <pochu> IntuitiveNipple: what I mean is that trackerd could load the db, check if it's buggy, and if it is fix that
[16:39] <pochu> otherwise force the creation of a new db. It's just a cache AFAIK...
[16:39] <IntuitiveNipple> pochu: yeah... this is going to be horrendous for SRUs!
[16:39] <IntuitiveNipple> pochu: No, not common.db, it contains Options :s
[16:39] <pochu> oh
[16:40] <IntuitiveNipple> pochu: there are now two problems with the tracker Options table. The first is, it is currently writing OptionValue as OptionKey and visa-versa...
[16:41] <pochu> what I mean is, whatever you're going to do in the package postinst, do it from inside trackerd
[16:41] <IntuitiveNipple> pochu: and I've also discovered that Options allows multiple entries for the same option since the table wasn't created with "OptionKey PRIMARY KEY"
[16:42] <IntuitiveNipple> Hmmm, can of worms anyone? :D
[16:42] <IntuitiveNipple> These bugs are incidental to the main one I'm chasing, which is 100% CPU usage by trackerd
[16:44] <pochu> the fix for that is to remove tracker ;)
[16:44] <IntuitiveNipple> lol don't tempt me!
[16:45] <IntuitiveNipple> I can fix the database with a simple script using sqlite3, *if* I can figure out a per-user way to start it :)
[16:46] <pochu> make trackerd a wrapper that calls your script and then tracker.real ;)
[16:46] <IntuitiveNipple> for an SRU? *eeek*
[16:46] <pochu> heh
[16:47] <IntuitiveNipple> I'm *hoping* I can fix all the bugs I'm finding and get them into one SRU for Hardy and Intrepid - luckily H/I/J all have the same codebase
[16:57] <cody-somerville> IntuitiveNipple, I'd rather have a one to one ratio
[16:58] <IntuitiveNipple> cody-somerville: one-to-one what?
[16:58] <cody-somerville> Bug to SRU ratio
[17:00] <IntuitiveNipple> cody-somerville: Oh... well, they are looking to be inter-related, so right now I've got three LP bugs that relate to one overall fix, but yeah, for things like the threads-not-stopping-on-SIGINT, that'd be separate
[17:00] <cody-somerville> IntuitiveNipple, And you're sure all these bugs are SRU worthy? Have they been fixed in Jaunty?
[17:01] <IntuitiveNipple> No, Jaunty is affected by the same ones, but obviously the patches for Juanty don't need SRU
[17:02] <IntuitiveNipple> cody-somerville: The bugs, combined, cause trackerd to eat 100% CPU in some circumstances, all mainly because it writes the wrong entries to its Options table
[17:03] <IntuitiveNipple> cody-somerville: So it's a case of fixing for new installs, and cleaning up the existing installed options
[17:06]  * ogra hugs slangasek
[17:06] <ogra> slangasek, all solved :)
[17:07] <slangasek> \o/
[17:07] <ogra> bryce, latest synaptics fixes my issue :D
[17:12] <davmor2> any pulse audio guys here?
[17:38] <superm1> pitti, can you nuke the intrepid-proposed upload of fglrx.  It didn't fix the problem as expected so it doesn't need to be sitting there
[17:38] <superm1> you can unsubscribe ubuntu-sru from bug 284408 too
[17:51] <xnox> There is a source package in the archive which has ~100 files with copyright/license headers (GPL2 and GPL2+), it has a toplevel license/copyright as well GPL2+, and there are ~200 files without any copyright nor license. Similar situation is with the new upstream release and their svn. Is it acceptable for such thing to enter (continue to stay) in the Debian and/or Ubuntu archives?
[17:51] <xnox> it's currently in Debian main, Ubuntu universe.
[18:11] <hyperair> xnox: well if it entered nevermind imo
[18:11] <hyperair> xnox: but it would be good to attempt to persuade upstream to handle it
[18:11] <IntuitiveNipple> Would the Feature-Freeze be the applicable deadline for updating a package to the latest upstream?
[18:13] <stgraber> asac: any objection to bug 305531 importance to be raised to high ?
[18:13] <stgraber> asac: it's really a very very annoying bug for all ltsp users as having to wait 3s to get a drop-down to appear tends to make the xul applications almost impossible to use
[18:15] <xnox> hyperair: ok thanks.
[18:15] <hyperair> xnox: np
[18:57] <tkamppeter> pitti, ping
[20:16] <tjaalton> patches.ubuntu.com hasn't been updated since Jan 18th?
[20:41] <maxb> As we're not yet in FeatureFreeze, it would probably make sense to requestsync bzr, right? (Since we're two upstream releases behind at the moment)
[20:42] <maxb> Do I need to separately requestsync bzrtools, or can it be a single bug?
[21:52] <Turl> hello
[21:52] <Turl> why does jaunty have such an old upstart version?
[21:54] <ion_> turl: There will more incentive to upgrade the package when Upstart reaches the point where all initrd scripts can be migrated to Upstart jobs.
[21:54] <ion_> Uh. Brainfart. s/initrd/sysvinit/
[21:54] <Turl> ion_: will this happen for jaunty or jaunty+n?
[21:55] <ion_> Probably not for jaunty.
[21:55] <Turl> :(
[21:55] <TheMuso> Considering the upstart upstream author works on ubuntu, I think he wants to make the upgrade when everything in upstart is ready.
[21:57] <Turl> also, is it a know issue the fact that gdm->usable desktop takes a long time on a quite recent pc?
[21:59] <ion_> Yes
[21:59] <TheMuso> Yes its known, and is being worked on for Jaunty.
[21:59] <Turl> ok then
[22:00] <Turl> another thing, when will the intel graphic cards 3d accel work well? it works a day, breaks the next one, ...
[22:01] <Turl> TheMuso: about the gdm->desktop, I'm refering to a quite big regression from intrepid, idk if you were refering to the same problem.
[22:01] <Hobbsee> wfm
[22:01]  * TheMuso can't answer that
[22:01] <TheMuso> Turl: No I wasn;t.
[22:01] <Hobbsee> oh, jaunty.  that seems to always be dodgy.
[22:02] <Turl> TheMuso: well, it might be related to the intel problem, I don't have another pc to test my theory though
[22:02] <TheMuso> right
[22:58] <slangasek> blueyed: ping; is bug #217504 still an issue for you in jaunty, or does hal now recognize your WWW key?
[23:02] <blueyed> slangasek: no, acpi_fakekey still does not work for 148 or 150 (2.6.27-8-generic however)
[23:03] <slangasek> blueyed: I don't mean "does acpi_fakekey work", I mean "does hal recognize your WWW key, making acpi_fakekey unnecessary" :)
[23:03] <slangasek> acpi_fakekey is going to go away; I'm just trying to figure out whether this bug is already fixed by other means
[23:03] <blueyed> slangasek: yes, it does.. :)
[23:04] <slangasek> hal does recognize the key?
[23:04] <blueyed> xev displays it being pressed. I don't know if it comes from hal?! is there a hal-monitor?
[23:06] <slangasek> well, it either comes from there being a correct default in-kernel keymap for the key, or one being provided by the hal-info package