[00:10] <shtylman> ccheney: I wish I knew...I have been trying many things to no avail... for some reason when using oxygen style..there is no text!
[00:20] <irvingpop> Howdy
[00:21] <irvingpop> I need help creating a PPA for a program that has never been packaged before for Debian/Ubuntu.   Is this the right place?
[00:22] <ScottK> irvingpop: #launchpad is the place for PPAs.
[00:22] <jpds> irvingpop: #ubuntu-motu can help you out.
[00:22] <irvingpop> Thanks!
[00:23] <ScottK> jpds: Unless it's intended to go into Ubuntu, I think it's OT for #ubuntu-motu.
[00:23] <jpds> ScottK: I assumed he was trying to get it into Ubuntu.
[00:24] <ScottK> Could be, I read it the other way.
[00:24] <mauren> hi
[04:45] <ccheney> shtylman: hmm weird :(
[04:45] <ccheney> shtylman: were you able to get the other bugs fixed?
[04:46] <shtylman> ccheney: I need to take a closer look at the other bugs, but I am pretty sure there are fixes for them...they seem like *normal* bugs compared to this one..
[04:46] <shtylman> the extension bug is not a problem and I have a fix
[04:46] <shtylman> the one where it goes up a directory might be related to this oxygen/no text bug
[04:47] <shtylman> and the cut off widgets...well... I don't think there is an immediate solution for that one.. the integration provides feedback on how big to make the widget...but it is either being ignored or we arn't doing it right..
[04:48] <shtylman> if I fix it for one style, it breaks for another...
[04:48] <shtylman> basically...im hung up on this filepicker text bug really
[04:50] <tripzero> doesn't look like consolekit is working without gdm in jaunty
[04:55] <ScottK> shtylman: My 15 year old daughter will be very glad to hear about the missing extension fix.  Between that and the fact that OOo only knows a .doc is .doc due to the extention, she thought she'd lost he homework and was going to have to redo  it.
[04:55] <shtylman> ScottK: haha... wow
[04:55] <shtylman> thats like an inspirational story..
[04:56] <ScottK> I added the .doc manually, opened it again and it was all there.  She was very relieved.
[04:56] <shtylman> ccheney: I will send the patches for extension tomorrow evening...I don't know about the other stuff...it isn't going well
[04:56] <ScottK> But, yeah.  That's a good one to get fixed.
[04:57] <shtylman> ScottK: yea... im quite upset that oo doesn't add the extension itself
[04:57] <shtylman> the checkbox is checked
[04:57] <shtylman> so I would have assumed that it would..guess not
[04:59] <Amaranth> *groan*
[04:59] <Amaranth> I can't reproduce bug 429858 anymore
[04:59] <Amaranth> err, wrong one
[05:00] <Amaranth> bug 430981
[05:00] <Amaranth> anyone here having that problem?
[05:22] <ccheney> shtylman: ugh sorry i was in another window, reading scrollback now :)
[05:23] <ccheney> shtylman: ok finished reading, thanks for the update
[05:24] <ccheney> shtylman: if at least some of the bugs can be fixed in time for beta that will definitely help :)
[05:24] <ccheney> shtylman: i can wait to do the upload until sunday night (UTC-0600) but not much further than that or people will call for my head ;-\
[05:29] <ScottK> more than usual ...
[05:30] <ScottK> ;-)
[05:30] <Amaranth> What? OOo uploads are done on weekends to not kill every else's day?
[05:53] <ccheney> Amaranth: well when i try to upload on monday's it seems arm people scream :-\
[05:53] <ccheney> Amaranth: our arm buildd is really slow
[05:53] <Amaranth> ccheney: hehe, you kill their whole week :P
[05:54] <ccheney> Amaranth: well it only takes ~ 30 or so hours to build but still its not like the 1-2 hours it takes on my machine
[05:54] <Amaranth> ccheney: Holy crap, what kind of machine do you have?
[05:54] <ccheney> i think with my new machine i get next week it will take < 1 hr to build OOo
[05:54] <Amaranth> A couple years ago on a top of the line machine it took over 6 hours
[05:55] <ccheney> i currently have a c2d 2.8ghz and next week will have ~ core i7 4ghz
[05:55]  * hyperair thinks that the buildds should use ccache
[05:55] <Amaranth> Wow, OOo must have improved their build times
[05:55] <Amaranth> That's getting into Firefox territory
[05:55] <Amaranth> ccheney: Soon "it's compiling" won't work well as an excuse for reading slashdot ;)
[05:55] <ccheney> Amaranth: a hyperthreaded 4 core 4ghz system is a little faster than a cellphone cpu ;-)
[05:56] <Amaranth> Yeah, I'd say
[05:56] <Amaranth> ccheney: Wait, does OOo use gold or something now?
[05:56] <ccheney> no
[05:56] <ccheney> if it did it would compile super fast aiui
[05:56] <Amaranth> Yeah, gold would probably have it under an hour on your current system
[05:56] <wgrant> Doesn't armel have $large_number buildds now?
[05:57] <ccheney> it might still take over an hour with the new system due to dpkg-shlibdeps etc, will have to see how it does
[05:57] <Amaranth> We need one of those dual core 2Ghz Cortex A9 things for a buildd :)
[05:57] <ccheney> yea :)
[05:57] <Amaranth> or several of them
[05:57] <ScottK> wgrant: It does, but if you upload a 30 hour monster right before a milestone freeze it can complicate things.
[05:57] <ccheney> need one of those in the next iphone too :)
[05:58] <wgrant> ScottK: I suppose so.
[05:58] <Amaranth> it'll still take forever but it'll be like compiling on a netbook instead of a cell phone
[05:58] <ccheney> 30 hours then if it breaks bad things happen, heh
[05:58] <Amaranth> distcc to the rescue ;)
[05:59] <ion> amaranth: Btw, icecc > distcc ;-)
[05:59]  * ccheney wonders how long it takes to start OOo on arm, it takes ~ 8-10s on atom
[05:59] <Amaranth> well most of that is IO, isn't it?
[05:59] <ccheney> maybe so, the system i have has a hd but its probably pretty slow
[05:59] <Amaranth> ccheney: cold cache it takes that long on my laptop
[05:59] <ion> It would be nice if icecc was fully decentralized, though.
[06:00] <ccheney> it takes ~ 2s on mine but it might not be completely cold
[06:00] <ccheney> my hd is definitely faster than a netbooks though
[06:00]  * Amaranth really hopes we don't have to enable unredirect_fullscreen_windows in compiz again
[06:00] <Amaranth> It fixes a bunch of bad bugs having it disabled
[06:04] <ccheney> anyone know if radeon 4350 works good on karmic?
[06:05] <ccheney> er with the open driver i mean
[06:19] <ccheney> hmm looks like 2d should work but not 3d
[06:45] <Amaranth> ccheney: Right, 3D is what caused the fun loop of splash screen on the alpha 6 cds
[08:31] <cjwatson> ScottK: ia64 is properly alive again, and I've given back everything that failed with chroot problems.
[08:31] <glick> excuse me, in jaunty is there a known issue with pulse or alsa not working correctly and picking up mics?
[08:31] <glick> not picking up mics?
[08:32] <glick> i dont know if i should file a bug report, or if im just stupid
[08:32] <Amaranth> yay!
[08:32]  * Amaranth has a failsafe GNOME session
[08:35] <wgrant> cjwatson: Do you want to give back lots of stuff in your rebuild archive, or do you want to grant the usual teams privileges to do so?
[08:36] <glick> im trying to figure out where or if i should file a bug report
[08:36] <cjwatson> wgrant: as it happens I'm right in the middle of doing so at the moment
[08:36] <glick> my microphone in alsa cant be unmutted, and when i switch my recording device to pulseaudio, none of the recording applications can use it
[08:36] <wgrant> cjwatson: Great, thanks.
[08:36] <glick> i dont know if that would be an ubuntu bug, alsa bug, or pulseaudio bug
[08:37] <cjwatson> wgrant: unfortunately the API gives up in despair when trying to do anything with my rebuild archive so I'm having to do it through the web UI. Takes a whiel.
[08:37] <cjwatson> while.
[08:37] <glick> or even IF its a bug
[08:37] <wgrant> cjwatson: Erm, really? What error does it give?
[08:37] <Amaranth> glick: file a bug or try asking about it again on a weekday
[08:38] <glick> ok Amaranth
[08:38] <cjwatson> similarly, the web UI can't actually load the main page for the archive so I probably can't adjust privileges either
[08:39] <wgrant> cjwatson: Privs are done through the API.
[08:39] <cjwatson> >>> launchpad.people['cjwatson'].getPPAByName(name='test-rebuild-20090909')
[08:39] <cjwatson> ...
[08:39] <wgrant> Ah.
[08:39] <cjwatson> lazr.restfulclient.errors.HTTPError: HTTP Error 400: Bad Request
[08:39] <wgrant> It's not a PPA.
[08:39] <wgrant> launchpad.load('https://api.edge.launchpad.net/beta/ubuntu/+archive/test-rebuild-20090909')
[08:39] <cjwatson> aha, thanks
[08:39] <wgrant> There might be another way to get it, but that's how I do it.
[08:39] <cjwatson> https://edge.launchpad.net/ubuntu/+archive/test-rebuild-20090909 oopses
[08:39] <wgrant> Er.
[08:40] <wgrant> That worked for me three hours ago.
[08:40] <cjwatson> it's been consistently failing for me for ages
[08:40] <wgrant> Yes, but you are special.
[08:40] <wgrant> It works for me.
[08:40] <cjwatson> as the archive owner, you mean?
[08:40] <wgrant> Right.
[08:40] <cjwatson> thanks, that API call works
[08:40] <wgrant> Great.
[08:41] <wgrant> Then you can hopefully call newComponentUploader on it.
[08:41] <cjwatson> on which team?
[08:42] <wgrant> It might be valuable to give ubuntu-dev access to all components, since all that can be done in that archive is retry.
[08:44] <cjwatson> breaks with HTTP 500. Life's too short and it's a Saturday. I'll try again in working hours
[08:45] <cjwatson> >>> ubuntu_dev = launchpad.people['ubuntu-dev']
[08:45] <cjwatson> >>> for component in ('main', 'restricted', 'universe', 'multiverse'):
[08:45] <cjwatson> ...     rebuild.newComponentUploader(component_name=component, person=ubuntu_dev)
[08:45] <cjwatson> lazr.restfulclient.errors.HTTPError: HTTP Error 500: Internal Server Error
[08:45] <wgrant> cjwatson: Argh, OK. I'll try things locally and see what's wrong. Thanks for trying.
[09:04] <wgrant> cjwatson: I can't reproduce that newComponentUploader OOPS or see how it's happening, unfortunately. Can you grab an OOPS code for that at some point?
[10:59] <cjwatson> wgrant: did you move http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20090909.html somewhere else? it's 404 now
[11:00] <wgrant> cjwatson: Add -karmic before the .html, sorry. I might symlink it.
[11:00] <cjwatson> ok
[11:00] <cjwatson> thanks
[11:00] <wgrant> cjwatson: I've identified and filed the bug that causes an OOPS when you view the copy archive, but can't reproduce the API OOPS.
[11:02] <cjwatson> it's just hanging on "Loading credentials..." for me now, so I can't dig into it more at the moment :(
[11:04] <wgrant> Hmm.
[11:30] <GobiTheGoblin> Hi there =) I asked this in kernel channel too, but that place is dead silent. So I came here. The question is this: If I have understood correctly this should be somewhat correct dir/file structure of 2.6.31 http://kernel.ubuntu.com/git-repos/ubuntu/linux-2.6/drivers/hid/ ?
[11:30] <GobiTheGoblin> Still, when i install sources from repos, those files are not there
[12:10] <directhex> yay for Evo. Inbox (-2 unread, 2209 total)
[12:11] <wgrant> directhex: I had -35 unread at one point.
[12:15] <Ademan> not sure if this is *really* the right place, but what's the relation between notify-osd and that notification applet? and how can i get my notifications to stay resident in that notification applet (like pidgin)
[12:20] <wgrant> Ademan: The notification applet to which you refer is indicator-applet. It's an entirely separate system from notify-osd (which uses libnotify).
[12:21] <Ademan> wgrant: ah thanks, is it similarly available over dbus?
[12:21] <wgrant> Ademan: yes.
[12:21] <Ademan> thanks wgrant, D-feet time hah
[12:22] <wgrant> Ademan: There are libraries around. libindicate, and its Python binding python-indicate.
[12:22] <Ademan> wgrant: thanks, but i'm trying to shoehorn some of this functionality into irssi, which means perl, which seems to mean raw-dbus :-/
[12:23] <wgrant> Ademan: Aha.
[12:23] <wgrant> Ademan: Excellent idea.
[12:24] <Ademan> thanks wgrant i have the notify-osd part working already :-) although it doesn't too much at the moment
[12:46] <Ademan> egh indicator-applet doesn't seem to implement any interfaces... wth?
[14:02] <directhex> sigh, that was quick. my karmic won't boot on my laptop
[14:20] <directhex> yup. bricked.
[14:22] <directhex> um... why would recovery mode still try to launch X? was that always the case?
[14:35] <Laney> i think thats a bug
[14:35] <Laney> did it for me too
[14:37] <directhex> oh for..........
[14:37] <directhex> Laney, this will fill you with as much rage as me
[14:37] <directhex> Laney, touch /forcefsck; reboot
[14:37] <directhex> Laney, welcome to extended black screen land
[14:37] <Laney> haha
[14:37] <Laney> i think i'll give it a miss
[14:38] <directhex> Laney, the modesetting happens before a slow, feedback-free, and frankly scary action - no hints as to what it's doing
[14:41] <directhex> okay, someone needs to do something about that, i mean really really badly
[14:42] <directhex> hm. is karmic meant to use grub2?
[14:43] <sebner> directhex: sure
[14:44] <Laney> did it come back?
[14:44] <directhex> sebner, you sure? this is grub1 still
[14:45] <directhex> Laney, oh, yeah. once fsck finishes, it boots fine.
[14:45] <cjwatson> grub2> only on fresh installs, and even then there are a couple of corner cases that still need grub1
[14:45] <cjwatson> if you want to upgrade to grub2, see http://wiki.ubuntu.com/Grub2
[14:45] <directhex> Laney, try adding "nomodeset" to boot parameters to actually see why it spends 5+ minutes on a black screen
[14:46] <Laney> rather you than me...
[14:46] <Laney> I wrestled with this system most of the week, finally got it reasonably alright
[14:55] <directhex> hm. well, grub2 seems to work. compiz has gone the way of the dodo though :(
[15:05] <directhex> aha, got it to come back
[15:35] <ScottK> cjwatson_: Thank you for taking on ia64 and getting it going again.
[15:50] <tgpraveen> is it true that the boot speed improvements and all would be available only from karmic beta
[15:50] <tgpraveen> ?
[16:49] <directhex> nspluginwrapper in karmic doesn't accept click events ¬_¬
[17:17] <ScottK> tgpraveen: There are quite a number of parts of boot speed improvements.  A great deal of them landed last week and were in Alpha 6.  I don't think it will all be done for a bit yet.
[19:02] <kirkland> superm1: ping
[19:34] <dhillon-v10> hi all, I need some help with a nautilus crashing problem, I enabled apport but all I get on stacktrace is ()????
[19:35] <c_korn> dhillon-v10: try to install nautilus-dbg
[19:36] <c_korn> (or even better: gnome-dbg)
 alright I will do that, I had to do a fresh install about 3 times before because this problem won't go away
[19:37] <c_korn> odd, I did not have any problems with nautilus
[19:38] <c_korn> which steps should reproduce the crash ?
 another problem is that this happens at random I am not sure what causes the problem, do you want me to post the log file viewer results
[19:39] <c_korn> just open a bug and attach it.
 I have done that several times before no response till now
[19:40] <dhillon-v10> http://paste.ubuntu.com/274312/
[19:46] <tgpraveen1> : http://ostatic.com/blog/ubuntu-version-9-10-code-named-lucid-lynx
[19:46] <tgpraveen1> (12:10:25 AM) tgpraveen1: ubuntu 10.04 name
[21:00] <zyga>  
[21:52] <citrus212> hi there
[21:52] <citrus212> i need help with grub bootloader
[21:52] <citrus212> i'm trying to load xp back onto it
[21:54] <ScottK> citrus212: Help is in #ubuntu+1 for Karmic and #ubuntu for other releases.
[22:40] <superm1> kirkland, contentless pong
[23:13] <MontelEdwards> Hi
[23:13] <MontelEdwards> I was wondering if anyone could help me with a Boo script.
[23:13] <MontelEdwards> I am new to it, and i need something like the subprocess.call function in python