[05:46] <marcelo_> I have installed Ubuntu 9.04 and have notice the slowness of graphics!!!  Xorg is taking up 30% of my cpu and beagle-helper is taking up 15% to 20% of my cpu...    thats on avarage 50% of my cpu!!!   can anyone please help me before i have to back to vista witch ran just fine....   I am a nuwbie to linux and have liked it so far but now I am stuck with this problem.
[06:43] <pitti> Good morning
[07:35] <didrocks> hi pitti
[07:38] <pitti> hey didrocks
[07:38] <didrocks> pitti: still reviewing SRUs? :)
[07:38] <pitti> every day after a release :)
[07:39] <didrocks> good luck ;)
[07:39] <pitti> I spent the morning packaging the new g-p-m, though
[07:39] <pitti> still has some rough edges, though, so I'd like to get some more work onto that
[07:39] <didrocks> is it working great?
[07:39] <didrocks> oki
[07:39] <pitti> robert_ancell: oh, FYI, in case you are interested in g-p-m, I have a branch with 2.26.1 (to avoid double work)
[07:40] <pitti> didrocks: yay devicekit :)
[07:40] <didrocks> pitti: oh, didn't know they integrated devicekit. I will have a look to it :)
[07:41] <pitti> didrocks: I blogged about it a while ago
[07:42] <didrocks> found http://martinpitt.wordpress.com/2009/03/11/wanna-touch-devicekit/, remember now :)
[07:42] <robert_ancell> pitti: g-p-m = gnome-power-manager?  Don't think I've ever looked at it...
[07:43] <didrocks> pitti: I will try it when you will make it available. I'm bored that my suspend to ram works so well :)
[07:46] <robert_ancell> Who is the local Firefox expert?  I've been looking at bug 368252 and I don't have the know-how to trace how the totem plugin is invoked.  Clues are making it look like Firefox+javascript may be causing the problem..
[07:47] <pitti> ok, I'm off for an hour or two for a doctor appointment
[07:47] <didrocks> see you
[07:47] <robert_ancell> later
[07:47] <didrocks> robert_ancell: asac IIRC
[07:48] <robert_ancell> didrocks: cheers
[07:48] <didrocks> y/w
[08:43] <pitti> re
[08:43] <didrocks> re pitti
[08:47] <seb128> hello pitti didrocks
[08:47] <pitti> hey seb128
[08:48] <didrocks> Hi seb128
[08:48] <robert_ancell> seb128: hey seb
[08:48] <seb128> hello robert_ancell
[08:49] <seb128> robert_ancell: how was your day? did you manage to squash some bugs? ;-)
[08:51] <robert_ancell> seb128: hard going today.  I worked on the totem-mozilla bug but I think it's a firefox issue? Some more work on the SSH bug, I can repeat it but I don't get what is going on
[08:51]  * robert_ancell has been pushing all his work upstream today :)
[08:51] <seb128> robert_ancell: could be for totem, it's weird that the non-hd things are working and firefox is calling totem by looking to .xsession-errors
[08:52] <pitti> hm, this U1 thing doesn't really seem to like me :/
[08:52] <robert_ancell> seb128: well it seems to be due to the way the page is crafted.  I was hacking it apart to find what HTML/JS code is making the difference
[08:52] <crevette> hello
[08:52] <didrocks> hey crevette
[08:52] <seb128> robert_ancell: I see
[08:53] <seb128> lut crevette
[08:53] <seb128> robert_ancell: don't spend too much time on it, reassign to firefox if the bug is there
[08:53] <robert_ancell> pitti: I was wondering if it didn't work 'cause it was shut down when I was awake - it hardly never works!
[08:53] <crevette> hello frenchies
[08:54] <pitti> well, I set it up, and I see my files again which I uploaded two months ago
[08:54] <pitti> but it never syncs
[08:54] <robert_ancell> seb128: that's my guess - I'll do that and they can reassign it back if they can say why its invoking the plugin in different ways
[08:54]  * crevette is interested by what is this U1 project
[08:54] <crevette> :)
[08:54] <crevette> I guess today we just know mere mortal
[08:54] <crevette> +s
[08:54] <pitti> crevette: wait until May 7 :) then the public beta will start
[08:54] <pitti> ECHANNEL, sorry
[08:55] <pitti> but well, we talked about it in the meeting yesterday
[08:55] <pitti> crevette: can you see http://ubuntuone.com ?
[08:55] <asac> robert_ancell: ?
[08:55] <asac> robert_ancell: what have you found so far?
[08:55] <crevette> pitti, no, I don't permission to see it :)
[08:56] <robert_ancell> asac: can you look at bug 368252 - I'm a bit lost on the divide between firefox and the totem plugin
[08:57] <seb128> robert_ancell: the rhythmbox issue, are you waiting on an another example?
[08:57] <seb128> robert_ancell: I think the current case is already worth fixing, what do you think
[08:58] <robert_ancell> seb128:  I agree.  I was diving into the source but I got lost.  I'm not sure if it's a gstreamer or rhythmbox issue.  I was looking at the diffs but couldn't see anything.
[08:59] <seb128> robert_ancell: I would expect rather a gstreamer one
[08:59] <seb128> but I'm not sure either
[08:59] <seb128> it's just a random guess ;-)
[08:59] <robert_ancell> seb128: I also tried the Intrepid rb but it occurs for that too - this is why I think it is probably in gstreamer
[09:00] <asac> robert_ancell: what is supposed to happen when you left click?
[09:01] <robert_ancell> It should open the video in fullscreen afaik
[09:01] <robert_ancell> (it's just a standard link)
[09:02] <robert_ancell> asac: the interesting thing that stood out in the log is "width 1" and "height 1" for the failed cases
[09:10] <asac> robert_ancell: onclick="s_objectID=&quot;http://movies.apple.com/movies/paramount/star_trek/startrek-clip_480p.mov_1&quot;;return this.s_oc?this.s_oc(e):true"
[09:10] <asac> thats what happens "on click"
[09:10] <asac> doesnt look right
[09:11] <robert_ancell> asac: yeah, do you think they've changed the page?
[09:12] <robert_ancell> asac: how did you get that?  I was playing around with the web developer plugin but couldn't find out how to get what a link would resolve to
[09:12] <asac> robert_ancell:  can you check what "this.s_oc function does?
[09:12] <asac> robert_ancell: install firefox-3.0-dom-inspector
[09:13] <asac> robert_ancell: then you can click on elements and see the HTML element in the inspector
[09:15] <seb128> tseliot: hi, did you read the xrandr capplet bug about virtual settings questions?
[09:15] <tseliot> seb128: what bug?
[09:15]  * seb128 grrr at people not reading their bug emails
[09:16] <seb128> let me get the number, I assigned the bug to you
[09:16] <seb128> tseliot: bug #365210
[09:16] <tseliot> seb128: I might have read that but I would like to know what bug you're referring to
[09:16] <asac> robert_ancell: it seems to do something ... so figure out what this.s_oc function does
[09:16] <asac> robert_ancell: and so on
[09:16] <asac> have to get coffee now ;)
[09:17] <robert_ancell> asac: ok, cheers
[09:17] <seb128> tseliot: I get it every time on several boxes
[09:17] <seb128> tseliot: it's quite annoying and would be nice to fix in a sru
[09:18] <tseliot> seb128: I think I missed this report. I'll try to reproduce the problem here and work on a fix
[09:18] <seb128> tseliot: thanks
[09:18] <tseliot> np
[09:19] <seb128> tseliot: it's easy, start the capplet, try a lower resolution and back to your normal one
[09:19] <seb128> it will not go back until you restart the capplet
[09:19] <seb128> and it wants to add virtual settings when not required
[09:19] <seb128> ie just to go back to the normal value you were using for example
[09:19] <tseliot> seb128: and does this happen when the virtual resolution is already set in xorg.conf?
[09:19] <seb128> pitti: how do you deal with sync-source -a errors?
[09:20] <pitti> seb128: one by one, I'm afraid
[09:20] <seb128> tseliot: I've not tried, I'm using one screen
[09:20] <pitti> seb128: often we need to remove packages first, because they got renamed
[09:20] <seb128> pitti: is there a way to skip the broken entry or resume from there instead of redoing the whole -a ?
[09:20] <pitti> seb128: or binaries moved around (then -F helps)
[09:20] <pitti> seb128: or different orig
[09:20] <tseliot> seb128: ah, ok, so in your case it wasn't set
[09:21] <seb128> pitti: could you look to the libdca error and tell me what you would do?
[09:21] <pitti> seb128: resuming isn't possible, I'm afraid
[09:21] <pitti> seb128: you have to temporarily blacklist it, -a again, rinse and repeat until it succeeds
[09:21] <pitti> and then resolve the temporary blacklisted ones
[09:21] <seb128> tseliot: I'm using one screen on ati and no, I've no virtual on this box
[09:21] <pitti> seb128: looking
[09:21] <tseliot> ok
[09:22] <seb128> tseliot: but virtual is not required since that the normal resolution
[09:22] <seb128> I just start the capplet
[09:22] <seb128> change to 800x600 for example
[09:22] <seb128> ack the choice
[09:22] <seb128> and then try to change back to the normal value
[09:22] <seb128> I get the error
[09:22] <seb128> restart the capplet and it works
[09:22] <tseliot> ok, thanks for the info
[09:22] <seb128> you're welcome, thanks for looking into it!
[09:23] <seb128> pitti: thanks
[09:23] <seb128> pitti: I've been fixing some overwritte issues yesterday by using -f for those
[09:23] <pitti> seb128: right, what I said; our current libdts-dev is built from the libdts source
[09:23] <seb128> binaries which are built by new sources
[09:23] <pitti> seb128: so this one should just be --force'd, I think
[09:23] <seb128> ok, so -f, flush, wait for publishing and -a again?
[09:24] <seb128> pitti: ok, can you do it while you have it locally? thanks!
[09:24] <pitti> seb128: or just skil flush and publisher, and immediately run -a again
[09:24] <seb128> pitti: oh, no need to wait for publisher?
[09:24] <pitti> seb128: no, just don't flush
[09:24] <pitti> and let it sync all over again
[09:24] <seb128> pitti: I was not sure where it was getting versions to compare
[09:24] <pitti> that should be faster
[09:24] <seb128> pitti: it breaks again on the same case then
[09:25] <seb128> even if I -f ed it
[09:25] <pitti> seb128: not if you temporarily blacklist it
[09:25] <seb128> ah ok
[09:25] <seb128> ok, makes sense
[09:25] <seb128> I will do that next time, thanks!
[09:25] <pitti> seb128: oh, hang on
[09:25] <pitti> seb128: no, I won't sync that
[09:25] <pitti> seb128: our libtds-dev is ubuntu modified
[09:25] <pitti> it won't scribble over that
[09:25] <pitti> it needs to be merged
[09:26] <pitti> (or at least checked if the changes can go)
[09:26] <seb128> pitti: so just blacklist it for now?
[09:26] <pitti> seb128: yes
[09:26] <robert_ancell> I'm off, see you guys tomorrow
[09:26] <seb128> robert_ancell: have a nice evening see you tomorrow
[09:26] <pitti> robert_ancell: good night!
[09:26] <seb128> pitti: can you do that while you are at it?
[09:26] <robert_ancell> bye
[09:26] <pitti> well, I'm not "at it", but *shrug*
[09:26] <seb128> pitti: I'll continue on sync when I'm done with what I'm doing right now
[09:26] <pitti> sure
[09:26] <seb128> pitti: ok don't bother, I though you were already sshing on the box
[09:27] <seb128> I will do that in a bit
[09:27] <pitti> seb128: doing now, don't worry
[09:27] <seb128> I stopped on that this night and didn't resume yet
[09:27] <seb128> I just kept the question for this morning ;-)
[09:27]  * seb128 hugs pitti
[09:28] <pitti> seb128: ah, that's an ancient package (gutsy)
[09:28] <pitti> seb128: I'll just remove the libdts source, then it should just sync
[09:29] <chrisccoulson> is anyone intereted in taking bug 337441 for karmic?
[09:29] <seb128> chrisccoulson: you? ;-)
[09:29] <pitti> seb128: it'd probably be better to do a full process-removals run, I'll do that one
[09:29] <seb128> pitti: you rock!
[09:29] <chrisccoulson> seb128 - i was going to offer if noone else wanted to do it already:)
[09:30] <seb128> chrisccoulson: go for it, I expect we will find enough to do to not get bored without that one ;-)
[09:30] <chrisccoulson> i'll take that one then. thanks
[09:30] <seb128> thank you
[09:30] <pitti> seb128: right, process-removals duefully caught it
[09:31] <chrisccoulson> pitti - did you see my response in bug 360399? I don't think we're going to get an SRU-worthy fix to resolve this issue
[09:32] <chrisccoulson> upstream identified some issues with the plugin but when they fixed it it caused a big regression, and so they've just disabled it completely in 0.6.9x which we have in jaunty
[09:32] <chrisccoulson> and they're not planning any more work on that
[09:33] <pitti> chrisccoulson: right, I saw it; nevermind about it
[09:33] <chrisccoulson> you can probably unsubscribe the sponsors team and ubuntu-sru team from that if you like
[09:33] <pitti> at least the sponsors, yes
[09:34] <pitti> chrisccoulson: thanks
[09:34] <chrisccoulson> thanks:)
[09:41]  * pitti finally removes gtk+1.2
[09:42] <seb128> pitti: waouh!
[09:42] <pitti> seems that nobody ran process-removals for some time
[09:44] <pitti> seb128: hmm, eel2 got removed in Debian
[09:45] <pitti> ROM; obsolete, no rdeps, now in nautilus
[09:45] <seb128> pitti: right, we got it off the CD in jaunty
[09:45] <pitti> still being used by g-c-c and libnautilus-burn
[09:45] <seb128> g-c-c ?!
[09:45] <pitti> and three universe packages
[09:45] <pitti> -- karmic/main build deps on libeel2-dev:
[09:45] <pitti> gnome-control-center
[09:45] <seb128> that's a mistake
[09:46] <pitti> seb128: anyway, I'll keep it for now
[09:46] <seb128> rdpends lists n-c-b too but that's a mistake too
[09:46] <pitti> we'll do another process-removal run
[09:46] <seb128> ok
[09:46] <pitti> seb128: or want me to kill it now as a kind of reminder? :-)
[09:47] <seb128> I would not mind you doing that
[09:47] <pitti> "oops", it's gone :)
[09:47] <seb128> I've karmic sources there and there is only 3 rdepends
[09:47] <pitti> yay cruft cleanup
[09:47] <seb128> and I expect 2 of those to be fixed when syncing the second half of the archive
[09:47] <pitti> absolutely
[09:47] <pitti> they must have fixed it in debian
[09:48] <pitti> let's create some breakage
[09:48] <seb128> and g-c-c is just a cruft left in the build-depends
[09:48] <pitti> karmic works waaaaay too well right now
[09:48] <seb128> yeah, karmic is boring
[09:48] <pitti> well, new kernel+uxa is quite nice, though :)
[09:49] <pitti> seb128: okay, process-removals done; I suggest to let that publish (12:00 CEST) and then do a sync run
[09:49] <pitti> should get a little further now
[09:49] <seb128> pitti: ok thanks
[09:50] <seb128> pitti: no hurry I expect the buildds are busy for the day
[09:50] <pitti> hehe
[09:50] <seb128> the first sync runs yesterday did quite some work
[09:50] <pitti> it also cut quite a dent into MoM main.html
[09:50] <pitti> ok, so I'll get back to fixing g-p-m 2.26.1
[09:51] <pitti> and then I'll look into DK-disks and gnome-disk-tool
[09:51]  * pitti is in crack & breakage mood today
[09:52] <crevette> yeah
[09:52] <chrisccoulson> we're getting g-p-m 2.26.1 this cycle are we?
[09:53]  * crevette wants to have a broken distro
[09:53]  * chrisccoulson gives crevette a large hammer
[09:53] <pitti> crevette: that's my plan anyway
[09:53] <crevette> :)
[09:53] <pitti> crevette: likewise, gnome-mount/hal -> gnome-disk-tool/dk-disks
[09:53] <crevette> I didn't switch to karmic yet
[09:54] <crevette> gnome-mount is superseded by gnome-disk-tool
[09:54] <pitti> erm, chrisccoulson: that's my plan anyway
[09:54] <chrisccoulson> pitti - nice:)
[09:54]  * crevette is lagging behind for new gnome technology
[09:54] <pitti> I'm running gpm/dk-power here, but it has some small problems
[09:55] <chrisccoulson> what sort of problems? i know the newer g-p-m has proper consolekit support so doesn't try to do actions on the inactive VT
[09:55] <chrisccoulson> should fix an annoying bug i have where i press the power button on my machine and the shutdown dialog appears on all user sessions
[09:57] <pitti> chrisccoulson: it doesn't suspend when I close the lid
[09:57] <pitti> other than that, it seems to work fine
[09:57] <pitti> chrisccoulson: weird, I thought that problem was gone ages ago
[09:58] <seb128> pitti: gnome bug #573826
[09:58] <chrisccoulson> pitti - my power button produces a HAL event on the system bus rather than going through X, so all running instances of g-p-m get the event and respond to it
[09:58] <seb128> too
[09:58] <seb128> pitti: I expect they will land it upstream in 2.27
[09:58] <chrisccoulson> pitti - what sort of event does your lid button produce?
[09:58] <pitti> seb128: you are a bug machine
[09:58] <seb128> lol
[09:59] <seb128> I spend too much time working on bugs indeed ;-)
[09:59] <pitti> seb128: ah, for that; thanks (I thought you referred to the lid issue)
[09:59] <pitti> chrisccoulson: what kind of events? I'll watch g-p-m in debug mode
[09:59] <seb128> pitti: no, sorry for the confusion
[10:00] <pitti> seb128: your's is for gvfs hal->dk, isn't it?
[10:00] <seb128> pitti: yes, it was a reply to your dk-disks comment
[10:04] <chrisccoulson> pitti - if your lid button produces a hal event, then it won't work in g-p-m 2.26.x unless you built it with --enable-legacy-buttons
[10:07] <pitti> chrisccoulson: indeed, pressing the power button doesn't do anything either
[10:08] <pitti> chrisccoulson: I just get hal events, but nothing in g-p-m
[10:26] <chrisccoulson> pitti - i just get HAL events too. the new g-p-m doesn't support those unless you enable the support explicitly. that should probably be enabled in karmic until all hotkey support has gone from HAL
[10:31] <pitti> chrisccoulson: ah, I'll have a look at this
[10:32] <chrisccoulson> pitti - the stuff you're interested in is in src/gpm-button.c
[10:33] <chrisccoulson> all the hal stuff is conditionally compiled with #ifdef HAVE_LEGACY_BUTTONS
[10:33] <pitti> chrisccoulson: right, so that would require a DK-acpi or something such
[10:34] <crevette> so to understand the big picture hal is being deprecated to DeviceKit?
[10:34] <chrisccoulson> the comments in there suggest that hotkey support is being removed from HAL and they will all produce keypress events through X
[10:35] <seb128> pitti: CEST is european time right?
[10:35] <seb128> pitti: ie still half an hour to wait for this publisher run?
[10:36] <pitti> seb128: right
[10:36] <seb128> thanks
[10:36] <pitti> chrisccoulson: many thanks, testing now
[10:39] <crevette> CEST is our time
[10:39] <crevette> mere frenchies
[10:40] <crevette> and all the countries around (to not appear selfish)
[10:40] <crevette> :)
[10:42] <seb128> crevette: right, what I though and has been confirmed, "european time"
[10:43] <crevette> sorry I'm lagging
[10:44] <pitti> chrisccoulson: hm, doesn't seem to help :/
[10:44] <seb128> mvo: ok, I've update-notifier buggy again
[10:44] <seb128> mvo: it opens update-manager every time I do an apt-get install
[10:46] <mvo> seb128: please keep it in that state
[10:46] <seb128> mvo: ok
[10:46] <mvo> seb128: I need to for for lunch, after afterwards I would love to diagnose it
[10:46] <seb128> mvo: ok, I'm not touching the box until after lunch
[10:46] <seb128> or rather letting that in state ;-)
[10:46] <seb128> I will do bug triage now
[10:49] <pitti> chrisccoulson: ah, nevermind, working perfectly; was just my docking station going mad at me
[10:49] <seb128> pitti: I know you already did SRU yesterday but it would be nice if you could review libical today
[10:49] <seb128> pitti: we have quite some users annoyed by evolution hanging or crashing
[10:50] <seb128> the change should be easy enough to review
[10:50] <pitti> seb128: I will (I need to do SRU daily these times anyway)
[10:50] <seb128> thanks!
[10:50] <pitti> well, I do it right now; g-p-m isn't that urgent
[10:55] <pitti> seb128: can you please dupe some real bug reports to bug 368508, to get some affected users subscribed, and to underline the necessity for SRU?
[10:56] <seb128> pitti: I plan to add comments on the stack of evo bugs when it's accepted
[10:56] <seb128> to ask people to try this change
[10:56] <pitti> okay
[10:56] <seb128> I don't want to dup since the other ones a still bugs
[10:56] <seb128> they will not lead to crashes but should still be fixed
[10:56] <seb128> a -> are
[10:56] <pitti> if you ask them to give feedback on this one, that's okay
[10:57] <pitti> (accepted)
[10:58] <seb128> ok, commenting now
[10:58] <pitti> seb128: since bug 363169 is not a regression, I'm nervous about it for SRU; it might uncover other bugs in the new functionality
[10:58] <seb128> pitti: the bug submitter is upstream and the code path different is some 7-8 lines
[10:59] <seb128> pitti: it's just a callback called on new device detection
[10:59] <pitti> right, but that hasn't been tested properly?
[10:59] <seb128> pitti: and it has been tested in other distros
[10:59] <seb128> pitti: well, I don't feel strongly about it, just upstream has been pushy to get it sru-ed
[11:00] <pitti> well, it's not a regression, and not at all a major bug, so it needs some more convincing to become an SRU
[11:00] <seb128> and we have some user complaining about keyboard settings being dropped after suspend etc
[11:00] <seb128> it's a "annoying bug"
[11:00] <seb128> it reset your keyboard settings in some cases where xorg redetect the device
[11:00] <seb128> but I'm fine waiting a bit to have karmic feedback or debian one
[11:01] <chrisccoulson> pitti - it's good that works now:)
[11:03] <pitti> chrisccoulson: now I just need to find out how to repair the notify-osd patch, then it's all good
[11:03] <chrisccoulson> i've not seen that patch. is it quite big?
[11:03] <pitti> it's in the bzr tree
[11:04] <pitti> shouldn't be too hard to port
[11:05] <seb128> re
[11:06] <seb128> pitti: I would not have sru-ed to fix the issue only since I think it's a minor one too, I'm trying to not make manage upstream there but if want to put it on hold fine with me too
[11:35] <pitti> mvo: lots of people still have trouble in bug 257639
[11:40] <glatzor> servus pitti and mvo, as a work around we could disable the update cache of packagekit
[11:40] <glatzor> this would require a backport of f876a76737e504fca161f075bd0d1b8ba386cb75 and setting the corresponding configuration option
[11:41] <glatzor> if we disable the internal update cache of packagekit there would be no need for the apt post-update script anymore
[11:42] <pitti> hey glatzor, wie gehts?
[11:43] <glatzor> pitti, oh, work time consumes a lot of my life currently - so could be better. and yourself?
[11:43] <pitti> glatzor: pretty good, thanks; looking forward to karmic breakage :)
[11:50] <asac> mvo: are "restart required" notifications still done in tray or by a pop up in jaunty?
[11:51] <seb128> asac: dialog auto opening
[11:51] <asac> ah ... so thats why users complain about getting that without seeing the in-firefox notification
[11:55] <james_w> asac: if I have an empty .mozilla/extensions/\{ec8030f7-c20a-464f-9b0e-13a3a9e97384\}/ does that mean ubufox is disabled?
[11:55] <asac> mvo: i have http://paste.ubuntu.com/160607/ in /var/lib/update-notifier/user.d/firefox-3.0-restart-required ... nothing happens at all
[11:55] <asac> james_w: check in tools -> addons ... search for "Ubuntu Firefox ..."
[11:55] <glatzor> pitti, mvo: sorry for not thinking about this. but we could delay the packagekit statehaschanged action quite easily
[11:55] <james_w> asac: that's my old profile
[11:55]  * pitti merges the 73177 line diff of g-p-m dk branch to the ubuntu branch, *ugh*
[11:56] <james_w> asac: going back to that might lose my tabs again :-)
[11:56] <mvo> glatzor: do you have a diff to look at?
[11:57] <glatzor> pitti, mvo: we could raise PK_ENGINE_STATE_CHANGED_PRIORITY_TIMEOUT in src/pk-engine.c
[11:57] <mvo> asac: have yu touched /var/lib/update-notifier/dpkg-run-stamp ?
[11:57] <asac> james_w: not sure that i get what you mean ;)
[11:57] <james_w> asac: it claims to be enabled
[11:57] <asac> james_w: and touching the file doesnt display the in-firefox notification ?
[11:58] <asac> mvo: since when do i need to do that?
[11:58] <mvo> asac: its done automatically by apt if you install the package
[11:58] <mvo> asac: but if you just do local testing, then its needed
[11:58] <asac> mvo: i just raun --reinstall firefox-3.0
[11:58] <james_w> asac: it does this time
[11:58] <mvo> asac: hm, that should work, give me a sec to check
[11:59] <asac> mvo: touched both a few times ... nothing changes.
[11:59] <asac> james_w: so maybe you didnt see that when it happened?
[12:00] <james_w> asac: what happened was that I installed today's upgrades, and firefox stopped working properly in the middle as usual. After a while I noticed the update-notifier dialog, closed that, went to firefox, and there was no banner. So I just hit the X in the top right and then started firefox again.
[12:00] <asac> james_w: anyway. there are still bugs with upgrading even with this in-firefox notification ... so with some bad luck you might loose tabs on upgrade - unfortunately
[12:00] <mvo> asac: hm, seems to work for me, could you please run "update-notifier --debug-hooks" ? it will spit out quite a bit of output
[12:00] <asac> omg
[12:00] <asac> lol
[12:00] <asac> mvo: update-notifier --debug-hooks
[12:00] <asac> The program 'update-notifier' can be found in the following packages: * update-notifier
[12:01] <mvo> glatzor: if that is not used for other stuff, I'm fine with changing that timeout. but I wonder why the other fix does not help, it should have the same effect
[12:01] <mvo> asac: ;)
[12:02] <mvo> seb128: could it be that you have pending security updates?
[12:02] <seb128> mvo: how do I check that?
[12:03] <mvo> seb128: u-m should display those on top of the updates list
[12:03] <seb128> mvo: no I don't then
[12:04] <asac> oh goodness. thats really bad (popping up the window :))
[12:04] <mvo> pitti: sorry if that is a stupid question, but if I sru compiz-fusion-plugins-unsupported to jaunty-proposed, will it be poket copied or something like this?
[12:04] <seb128> asac: talk to mpt but I think some people complained already ;-)
[12:04] <mvo> asac: ...
[12:04] <mvo> asac: you are just not the target user
[12:04] <asac> maybe that was the reason i didnt have update-notifier installed anymore ;)?
[12:05] <asac> damn
[12:05] <mvo> there is a gconf key to get the previous behavior back
[12:05] <asac> well. we have a notification in firefox if you have ubufox
[12:05] <asac> so that shouldnt be displayed at all on default installs
[12:05] <asac> guess i have to make the DisplayIf: smarter
[12:06] <asac> mvo: how is the kapturl going? i still cannot require kubuntu to install ubufox due to that dependency ;)
[12:06] <mvo> seb128: hm, hm. what is the value of /apps/update-manager/launch-time  for you (in gconf)?
[12:06] <mvo> asac: I don't know :) hacking a bit qt would be fun  I guess
[12:06] <seb128> mvo:
[12:06] <seb128> $ LC_ALL=C gconftool -g /apps/update-manager/launch-time
[12:07] <seb128> No value set for `/apps/update-manager/launch-time'
[12:07] <mvo> asac: the code is nicely seperated now
[12:07] <mvo> launch_time (sorry)
[12:07] <asac> mvo: the idea would be to not use synaptic
[12:07] <seb128> mvo:  launch_time = 1241003015
[12:07] <seb128> if that's what you meant
[12:07] <asac> mvo: could apturl just not use synaptic?
[12:07] <mvo> asac: it does, but it still needs a little bit of frontend cod
[12:07] <mvo> e
[12:08] <asac> mvo: well. if thats just gtk it would be ok i guess
[12:08] <asac> firefox requires gtk anyway
[12:09] <asac> gnome-app-install,
[12:09] <asac> gnome-icon-theme
[12:09] <asac> why does apturl depend on that icon theme?
[12:09] <asac> synaptic
[12:11] <mvo> seb128: hm, that time looks very valid
[12:12] <seb128> ** (update-notifier:4981): DEBUG: /usr/lib/update-notifier/apt-check returned 116 (security: 2)
[12:12] <seb128> (update-notifier:4981): update-DEBUG: is_package_system_locked: 0
[12:12] <seb128> (update-notifier:4981): update-DEBUG: update_apt_is_running: 0
[12:12] <seb128> (update-notifier:4981): inotify-DEBUG: apt_get_running=TRUE
[12:12] <seb128> (update-notifier:4981): inotify-DEBUG: apt_get_running=TRUE
[12:12] <seb128> (update-notifier:4981): inotify-DEBUG: dpkg_was_run=TRUE
[12:12] <seb128> (update-notifier:4981): inotify-DEBUG: dpkg_was_run=TRUE
[12:12] <mvo> seb128: what does /usr/lib/update-notifier/apt-check print ?
[12:12] <seb128> (update-notifier:4981): update-DEBUG: update_check()
[12:12] <seb128> mvo: that's the debug log
[12:12] <seb128> so it says security 2
[12:12] <seb128> but there is none listed in update-manager
[12:12] <seb128> and still I would not expect it to auto open after each install
[12:13] <mvo> seb128: yes the security ones would explain it
[12:13] <mvo> seb128: well, yeah, that sucks
[12:13] <seb128> what is the code logic for security = 2?
[12:14] <seb128> ie how can I get those 2 names ?
[12:14] <seb128> update-manager lists none
[12:14] <mvo> seb128: the logic is in /usr/lib/update-notifier/apt-check
[12:15] <mvo> seb128: try adding a print into isSecurityUpgrade() before the "return True" please
[12:15] <seb128> let me add debug print there
[12:17] <seb128> ok
[12:17] <seb128> it's freetype
[12:17] <seb128>      2.3.9-4.1 0
[12:17] <seb128>         500 http://archive.ubuntu.com karmic/main Packages
[12:17] <seb128>      2.3.9-4ubuntu0.1 0
[12:17] <seb128>         500 http://security.ubuntu.com jaunty-security/main Packages
[12:17] <seb128>         500 http://archive.ubuntu.com jaunty-updates/main Packages
[12:17] <seb128>  *** 2.3.9-4build1 0
[12:17] <seb128>         100 /var/lib/dpkg/status
[12:17] <seb128> so update-manager lists the karmic version
[12:17] <seb128> which is a standard upgrade
[12:17] <seb128> but update-notifier still count the security one
[12:18] <pitti> mvo: we can, but it would clash with the version number in Debian
[12:18] <pitti> mvo: so we won't
[12:18] <mvo> pitti: I mean the new one with -1ubuntu1 (sorry for the version number bogus)
[12:19] <mvo> seb128: let me check if I can reproduce it
[12:19] <pitti> mvo: we can do that, yes
[12:19] <mvo> pitti: thanks, I update the bugreport and ask for this then
[12:20] <seb128> mvo: still my issue is that security upgrade or not it should stop auto open at each apt command
[12:20] <seb128> mvo: didn't we decide that manual apt run would tell it that user want to do things manually?
[12:21] <seb128> ie that it should not autostart at all?
[12:22] <mvo> seb128: well, the spec says it should auto-open on security updates
[12:23] <seb128> every time I use apt?
[12:23] <mvo> seb128: yeah, it sucks, I'm not sure what is the right answer, maybe have a minimal nag interval
[12:23] <seb128> that's ridiculous ...
[12:23] <mvo> seb128: every time there is a security update
[12:23] <seb128> well, there is a security update, I  know about it
[12:23] <seb128> but I'm using apt to do some work
[12:23] <mvo> I'm not defending this behavior, just saying why its there
[12:23] <mvo> and I want it changed too
[12:23] <seb128> well I though the timestamp thing was to not to that
[12:24] <seb128> ie not auto-open if users are using apt manually?
[12:24] <mvo> I'm just not sure yet how
[12:24] <seb128> I though we said that auto-opening was for luser who don't use the package manager and should be doing their upgrades
[12:24] <mvo> the apt timestamp stuff is only used for non-security updates, security updates are handled special
[12:24] <seb128> but that we would not annoy people who are using command line tools
[12:24] <seb128> hum, k
[12:25] <mvo> IMO its already way too much magic
[12:25] <seb128> is that a design team issue?
[12:25] <seb128> ie should I talk to mpt?
[12:25] <seb128> or is that a code bug?
[12:25] <mvo> please file a bug
[12:25] <seb128> I'm not sure what would be right
[12:25] <mvo> I think I still need to tlak to mpt what he thinks should be done
[12:25] <seb128> but auto-opening update-manager every 5 minutes while I'm working is not right ;-)
[12:25] <seb128> ok will do
[12:26] <seb128> thanks
[12:26] <mvo> seb128: just install those two security updates ;)
[12:26] <mvo> seb128: I agree
[12:26] <seb128> I guess that one is really a corner case
[12:26] <seb128> right, I would have if they were listed as security updates :-p
[12:26] <seb128> I did enable karmic
[12:26] <mvo> seb128: it is, u-m should still display them as security updates, I'm checking now why it does not
[12:26] <seb128> and I don't want to upgrade the hundred packages there
[12:26] <mvo> seb128: it shoudl be clever enough to get it right
[12:26] <seb128> mvo: it displays the karmic version which is never
[12:26] <seb128> newer
[12:27] <seb128> which makes sense
[12:27] <mvo> seb128: i.e. to detect that its karmic but there is a security thing in between, so there is a bug somewhere
[12:27] <seb128> well it's just that update-manager lists the most recent version
[12:27] <seb128> which makes sense
[12:27] <mvo> seb128: one obvous solution would be to only auto-start on new security updates, but that would require some persistant knowledge in u-n that it currently does not have (and until now not needed)
[12:28] <seb128> but maybe update-notifier should not count the security update in that case
[12:28] <mvo> seb128: yeah, I will fix this bug now, the other too when I got some input from the designers
[12:36] <asac> who could copy xulrunner-1.9 from jaunty-security (1.9.0.10+nobinonly-0ubuntu0.9.04.1) to karmic? just pitti or all archive admins?
[12:37] <mvo> seb128: aha, I know why it does not list freetype as a security update, give me a min and I fix it in karmic (only affects people with karmic sources)
[12:40] <pitti> asac: any archive admin
[12:41] <pitti> asac: done
[12:44] <asac> pitti: thanks.
[12:44] <asac> (oops.. didnt mean to include nick)
[13:04] <mvo> seb128: do you have a bugnumber yet?
[13:04] <mvo> seb128: or should I file it
[13:06] <seb128> mvo: bug #369198
[13:07] <mvo> thanks seb128
[13:07] <seb128> grr, managed to open twice by reclicking on launchpad being slow
[13:07] <seb128> closing dup
[13:07] <seb128> mvo: you're welcome
[14:36] <pitti> kenvandine_wk: hm, I now put some 5 MB of data into ~/u1; the icon keeps spinning (i. e. syncing) for almost half an hour now; that's the slow performance you already noticed/reported?
[14:37] <kenvandine_wk> not quite that bad
[14:37] <kenvandine_wk> look at the log, ~/.cache/ubuntuone/logs/
[14:37] <pitti> kenvandine_wk: I reported some 5 bugs today, but it's mostly working now
[14:37] <kenvandine_wk> good
[14:37] <kenvandine_wk> thx
[14:37] <kenvandine_wk> i uploaded 2.4G since last night :)
[14:37] <pitti> kenvandine_wk: lots of "called nothign"/"starting" cycles
[14:37] <kenvandine_wk> only reported one bug today
[14:38] <kenvandine_wk> how many files?
[14:38] <pitti> kenvandine_wk: oh, I thought we had something like a 2MB quota
[14:38] <pitti> well, it's my entire latex folder
[14:38] <kenvandine_wk> 2G
[14:38] <pitti> $ find ~/latex -type f| wc -l
[14:38] <pitti> 310
[14:38] <pitti> that shouldn't be too bad
[14:39] <kenvandine_wk> i have done 1248 files since last night
[14:39] <kenvandine_wk> 13 hours
[14:39] <kenvandine_wk> 2.4G
[14:39] <pitti> so I think it's rather a question of numbers of files than total size
[14:44] <ember> pitti: sorry about brasero SRU, the bugfix fixed quite a lot of lp bugs and sj ones.
[14:44] <pitti> ember: np, I didn't complain :)
[14:44] <mpt> mvo, using apt is supposed to *suppress* the updates window, not make it come up instantly :-)
[14:45] <tseliot> seb128: is there going to be a 2.26.2 release of gnome?
[14:46] <seb128> tseliot: yes but I doubt we will get everything in jaunty
[14:46] <seb128> it's not a lts
[14:46] <seb128> there is a .2 and .3
[14:46] <ember> pitti: cool, i have one more bugfix left with already verification done bug #345166
[14:47] <tseliot> seb128: ok then I think we can include my patch with an SRU while upstream can include it in either .2 or .3
[14:47] <seb128> tseliot: right
[14:48] <seb128> tseliot: the bug is an upstream one?
[14:48] <tseliot> seb128: yes, it is, I caused it. A 5 lines patch should solve it
[14:49]  * tseliot is recompiling gnome-desktop
[14:49] <seb128> tseliot: ok thanks
[14:49] <mvo> mpt: I changed update-notifier now to show security updates at most once every N hours (current N is set to 12h, but any value will do)
[14:50] <tseliot> seb128: BTW I have a gnome account now, which means that I can upload to the gnome svn (or is it git now?) but I think I'll need my changes to be approved first, right?
[14:50] <seb128> tseliot: correct
[14:50] <pitti> tseliot: wow, congrats
[14:50] <seb128> tseliot: you need to have a maintainer setting your patch "accept-commit"
[14:50] <mpt> mvo, thanks
[14:51] <tseliot> pitti: thanks :-)
[14:51] <seb128> you could technical commit but that would bad taste ;-)
[14:51] <seb128> +be
[14:51] <seb128> ie better to wait for a review and ack
[14:51] <mvo> mpt: should this be a SRU? its currently only available in karmic?
[14:51] <tseliot> seb128: yes, of course. I think I can bug federico about it ;)
[14:52] <mpt> mvo, I don't know. How many people use apt outside of synaptic/g-a-i/update-manager, and how often?
[14:52]  * dobey uses apt a lot
[14:52] <dobey> :)
[14:53] <mvo> mpt: I suspect its a bit of a corner case, it only happens if there are pending security updates that have not been installed
[14:53] <mvo> mpt: so its currently a over agressive nag
[14:53] <mpt> yeah
[14:53] <seb128> mpt: the people who use apt often are the people you don't want to annoy too much
[14:53] <mvo> I will mointor the bugs and decide based on that I think
[14:54] <mpt> seb128, I was just about to say exactly the same thing :-)
[14:54] <Ampelbein> seb128: regarding gnome-vfs: why did we drop the quilt build-dependency?
[14:55] <seb128> Ampelbein: probably because I don't like to use quilt but you can keep it while doing the merge I don't expect active work on gnome-vfs
[14:56] <Ampelbein> seb128: how can one not like quilt? ;-)
[14:56] <seb128> Ampelbein: cdbs-edit-patch autoreconf; autoreconf; rm cache; exit
[14:56] <pitti> Ampelbein: ever tried to do a 99autoreconf.patch with quilt?
[14:57] <Ampelbein> find * | xargs quilt add ?
[14:57] <seb128> Ampelbein: export QUILT_PATCHES=debian/patches; quilt push otherchange; quilt new autoreconf; find . -name | xargs add ...; autoreconf; quilt refresh; quilt pop; debuild
[14:57] <seb128> Ampelbein: see which one is easier? ;-)
[14:57] <seb128> Ampelbein: same with "drop a svn diff in the patches directory"
[14:58] <tseliot> seb128: my patch works :-)
[14:58] <pitti> quilt add sucks rocks through a needle, in general it's quite okay
[14:58] <seb128> not to mention the "ups I forgot to quilt add something, how to I undo ... remove directory start from scratch"
[14:58] <pitti> bzr looms are better for that
[14:58] <Ampelbein> seb128, pitti ok, i see your point.
[14:58] <seb128> tseliot: you rock!
[14:59] <pitti> Ampelbein: I'm quite okay with quilt, but this particular bit drives me mad :)
[15:01] <asac> dropping the change to not create patches link on top level was a fault imo
[15:01] <asac> adding the change ;)
[15:01] <asac> it was done in debian because of new source format ... which i never understood :)
[15:02] <asac> (all about quilt ;))
[15:17] <pitti> $ devkit-disks --mount /devices/sdb1
[15:17] <pitti> Mounted /devices/sdb1 at /media/Pitti USB
[15:17] <pitti> yohoo
[15:18] <mvo> glatzor: is PK acting on more than the update-list signal? is it also monitoring other files. I wonder why the fix for #257639 is not working
[15:23] <pitti> dobey: out of interest, what does U1 use hal for?
[15:23] <dobey> hal?
[15:24] <pitti> dobey: ubuntuone-storage-protocol and -client depend on it
[15:24] <dobey> oh, the apport hook used it, but it doesn't any more, so we could remove that explicit dep i guess
[15:24] <pitti> ah, splendid
[15:24] <pitti> dobey: I'll file a bug
[15:25] <pitti> dobey: thanks
[15:25] <dobey> sure
[15:31] <glatzor> mvo, no. there is only one further trigger which also emits the StatusHasChagned signal after resuming the computer
[15:46] <rickspencer3> kenvandine_wk: I have the U1 client working, how do I share stuff and what not?
[15:46] <pitti> hey rickspencer3
[15:46] <rickspencer3> hi pitti
[15:46] <rickspencer3> nice to see you guys
[15:46]  * pitti didn't figure out sharing yet either, the "share" button is grayed out for me in the web ui
[15:48] <seb128> hello rickspencer3
[15:48] <rickspencer3> hi seb128
[15:49]  * rickspencer3 copying all my work documents into my U1 folder
[15:49] <kenvandine_wk> rickspencer3: i think you can only share a top level
[15:49] <kenvandine_wk> that is all i have done so far
[15:50] <kenvandine_wk> i am syncing a load of crap now... so don't want to mess with it until it is done
[15:50] <kenvandine_wk> i have been syncing photos all night :)
[15:50] <kenvandine_wk> and not a single traceback!
[15:50] <kenvandine_wk> but it is saturating my uplink... sp my internets are slow :/
[15:51] <rickspencer3> hey!
[15:51] <kenvandine_wk> hopefully that will be done by the time i finish my openweek session... which starts in 9m
[15:51] <rickspencer3> someone shared files with me, and it's not pr0n!
[15:51] <kenvandine_wk> haha
[15:51] <kenvandine_wk> rickspencer3: disappointed?
[15:51] <kenvandine_wk> :)
[15:52] <rickspencer3> actually, there is a folder called "spanky" in there in
[15:52]  * rickspencer3 afraid to look
[15:52] <kenvandine_wk> hehe
[15:53] <seb128> mvo: could you look at bug #369282?
[15:53] <pitti> -rwxr-xr-x root/root    161368 2009-04-29 16:50 ./usr/bin/palimpsest
[15:53] <pitti> WTH
[15:53] <pitti> to your native English speakers, how would you denote "palimsest"?
[16:00] <mclasen> ...psest
[16:00] <mclasen> missing a p there
[16:01] <pitti> right, sorry
[16:01] <pitti> never heard the term before, and dict.leo.org is quite useless
[16:02] <Amaranth> pitti: Isn't it a made up word?
[16:02] <mclasen> its a bit medieval...
[16:03] <mclasen> its a name for a document that has been written over several times
[16:03] <mclasen> like monks used to do
[16:03] <mpt> It's not a common word
[16:03]  * Amaranth wonders what that has to do with audio mixing
[16:07] <mclasen> Amaranth: nothing. but disk (re-)formatting is in some sense analogous to what those monks used to do
[16:07] <Amaranth> oh, I thought that was the name of the pulseaudio mixer
[16:07] <Amaranth> is that the gnome-disk-utility thing using devicekit?
[16:08] <mclasen> yes
[16:09] <pitbullthe1st_> whats this channel for? (Sorry for being dumb)
[16:11] <mpt> pitbullthe1st_, discussing the development of most of the graphical bits in Ubuntu
[16:11] <tseliot> seb128: my patch is in the gnome bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=580754
[16:12] <glatzor> mvo, have you found a way to reproduce the error?
[16:12] <pitbullthe1st_> O ok so not for non coders like me then
[16:12] <pitbullthe1st_> thanks
[16:12] <seb128> tseliot: thanks
[16:12] <mpt> pitbullthe1st_, for the non-graphical bits, see #ubuntu-devel. For Kubuntu, see #kubuntu-devel. For user suppport, see #ubuntu.
[16:12] <pitbullthe1st_> ok thanks
[16:13] <mclasen> tseliot: federico and I fixed exactly that bug last night...
[16:14] <glatzor> mvo, a simple "os.fork()
[16:14] <glatzor> c = apt.Cache()" seems to work without any problems
[16:14] <mvo> glatzor: I have not :/ I was even doing a "while True: c = apt.Cache()" in parallel with a few tasks without luck
[16:15] <mvo> seb128: woah, that bug is pretty impressive
[16:16] <seb128> mvo: you think so? ;-)
[16:16] <tseliot> mclasen: do you refer to this? http://git.gnome.org/cgit/gnome-desktop/commit/?id=3f811a611185a3bdbb6b6d4c19590bd26ae1dc82
[16:16] <mclasen> tseliot: yes
[16:17] <tseliot> mclasen: it's not enough. Because you still don't have the information that you need and you'll get a screen size which is 0 x 0
[16:18] <tseliot> mclasen: believe me, I caused the bug and I know how to fix it ;)
[16:18] <mclasen> tseliot: well, what I committed certainly fixed my symptoms
[16:19] <seb128> mclasen: do you have your change applied?
[16:19] <seb128> mclasen: can you try to change to a lower resolution, ack the change, and try to change back to higher one
[16:19] <seb128> without closing the capplet between the changes
[16:19] <dobey> mvo: i am having some weird behavior with apturl...
[16:19] <mclasen> no, my laptop claims to only support one resolution...
[16:19] <tseliot> mclasen: how can you get the right information without calling XRRGetScreenSizeRange() ?
[16:20] <seb128> mclasen: ok, I will try later thanks anyway ;-)
[16:20] <mclasen> tseliot: the right ranges are already in the GnomeRRScreen struct
[16:21] <dobey> mvo: if i add a ppa in /etc/apt/sources.list.d/foo.list or something, and then do xdg-open "apt://package-in-new-ppa?refresh=yes" it doesn't work, but if i immediately do the xdg-open a second time, it works... like it's not re-reading the cache properly or something
[16:21] <mclasen> tseliot: but federico thought that some other fixes might be necessary; so it is probably best to discuss that with him
[16:21] <mvo> seb128: I wonder if its something like a wubi install or an other strange FS
[16:21] <tseliot> mclasen: no, they are no longer there because screen_info_new() calls fill_out_screen_info() with a half-empty GnomeRRScreen struct
[16:22] <tseliot> mclasen: sure, I'll bug him ;)
[16:22] <mclasen> not in my case...
[16:22] <seb128> mvo: feel free to ask on the bug ;-)
[16:22] <mvo> dobey: oh, let me check the code. that might be possible that there is a bug there
[16:22] <mvo> seb128: I did and reassigned to you as its cleary a gtk bug
[16:22]  * seb128 hugs mvo
[16:22] <mvo> seb128: :P no, reassigned to dpkg
[16:22] <dobey> mvo: yeah i'm looking at the code, but i don't really understand it :)
[16:22] <seb128> did I say that we need an installation issues component? ;-)
[16:23] <seb128> mvo: danke
[16:23] <mvo> its called "dpkg"
[16:23]  * mvo hides
[16:23] <mvo> and we really need someone deeply faimilar with it
[16:23] <seb128> let's make Keybuk be responsive for this one and all the bugs there ;-)
[16:24] <mvo> dobey: yep, thanks for the report, fixing it now
[16:24]  * Keybuk looks forward to how you intend to make him responsive <g>
[16:24]  * mvo gets some popcorn 
[16:25] <dobey> mvo: great! any chance we can get a release/update too? :)
[16:25] <mvo> dobey: yes, I just need a bug about it
[16:25] <dobey> mvo: ok, will file
[16:25] <mvo> dobey: the fix is pretty trivial
[16:25]  * seb128 sends the german mafia to convince Keybuk
[16:26] <seb128> mvo: you are in charge of that now ;-)
[16:26]  * mvo starts making weeping noises
[16:30] <dobey> Wenn ist das Nunstruck git und Slotermeyer?
[16:31] <Keybuk> dobey: Ja! .. Beiherhund das Oder die Flipperwaldt gersput.
[16:32] <mvo> lol
[16:33] <dobey> heh
[16:34] <dobey> mvo: bug #369324
[16:38] <mvo> dobey: thanks
[16:54] <tkamppeter> pitti, I have posted a new SRU for system-config-printer, bug 365329. Can you approve it? Thanks.
[17:14] <pitti> tkamppeter: does it really need to be fixed in three packages, or are the other package tasks invalid?
[17:39] <crevette> seb128, would you be interested with gnome-bluetooth 2.27.x ?
[17:40] <seb128> crevette: for karmic yes
[17:41] <crevette> seb128, of course, how should I do to replace bluez-gnome in the package ?
[17:41] <crevette> just Replace ?
[17:41] <seb128> Replaces is for when there is file conflicts
[17:41] <seb128> I though they were parallel installable?
[17:41] <asac> Conflicts/Replaces/Provides
[17:41] <crevette> no
[17:41] <seb128> are you sure?
[17:41] <crevette> the binary names are the same
[17:42] <crevette> not 100% but around 90%
[17:42] <crevette> :)
[17:42] <crevette> you can try it for free https://edge.launchpad.net/~bmillemathias/+archive/ppa :)
[17:42] <asac> http://wiki.debian.org/Renaming_a_Package
[17:42] <seb128> asac: it's not a rename
[17:43] <asac> seb128: if its supposed to replace it ;)
[17:43] <seb128> crevette: they should Conflicts, Replaces
[17:43] <seb128> asac: it's a fork
[17:43] <crevette> okay
[17:43] <crevette> thanks for the tip
[17:43] <asac> seb128: do we still want to support the other package?
[17:44] <asac> otherwise you can treat it like a rename packaging wise imo
[17:44] <crevette> I would ask to move bluez-gnome to universe, because I don't think it'll wont be updated
[17:44] <seb128> asac: I don't know enough about bluetooth to know
[17:44] <asac> k;)
[17:44] <seb128> I think that's on the UDS topic lists though
[17:44] <crevette> ah
[17:44] <asac> yeah so if both stay in the archive jkust conflicts/replaces and adjusting seeds once we want to change the default i guess
[17:44] <crevette> asac, exactly
[17:45] <asac> crevette: but why is it necessary to ship conflicting files?
[17:45] <crevette> necessary ?
[17:45] <crevette> you mean I could change the binary name ?
[17:46] <asac> no. just wonder why upstream did that. but guess its just compatibility thing
[17:46] <crevette> gnome-bluetooth is a fork and intend to replace bluez-gnome because the upstream developer was not active
[17:47] <crevette> https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-karmic-bluetooth-stack
[17:47] <crevette> asac, you're the guy on irt
[17:48] <asac> i know that i somehow ended up there ;)
[17:48] <asac> thats why i asked :)
[17:48] <crevette> because of conman?
[17:48] <crevette> does it fit in the spec ?
[17:48] <asac> no clue and no comment ;)
[17:48] <crevette> okay
[17:48] <asac> i dont think connman needs a spec either ;)
[17:49] <crevette> why ubuntu is looking for alternative stack ?
[17:49] <seb128> it's not?
[17:49] <asac> well. connman is in the archive. its just not ready for real use ;)
[17:49] <asac> i just dont see what a connman spec would contain ;)
[17:49] <seb128> bbl
[17:50] <crevette> it used to have affix tack apparently
[17:50] <asac> other than "lets try to get latest connman available in karmic "
[17:51] <crevette> asac, so back to my package I should use the method B from you rlink ?
[17:52] <asac> crevette: for now just create a normal package and set conflicts/replaces on bluez-gnome
[17:52] <asac> e.g. dont provide the transitional package
[17:53] <crevette> okay, so it's I 've already done in my ppa package
[17:53] <crevette> I should also modify gnome-user-share which recommend bluez-gnome
[17:54] <asac> crevette: so gnome-bluetooth already exists in jaunty?
[17:54] <crevette> If I could have a 30 hours day, 8 hours to do my day boring job, and 8 to do the thing I want
[17:54] <asac> apt-cache rdepends gnome-bluetooth
[17:54] <asac> oiops;)
[17:54] <crevette> asac, yes, but version < 2.xx served for another purpose
[17:55] <crevette> it used to be an obex file server, but now it provides tools to manage bluez
[17:55] <asac> crevette: what happens to the rdepends?
[17:56] <asac> seems to be just gpodder
[17:56] <crevette> gpodder should depends on gnome-user-share
[17:58] <asac> crevette: is gnome-user-share also changed?
[17:58] <crevette> need to
[17:59] <asac> crevette: no i mean ... did it get a new upstream purpose ;) ... similar to gnome-bluetooth
[17:59] <crevette> ah now, it still a file sharing over WebDAV and bluetooth
[18:00] <crevette> s/still/remains/
[18:00] <crevette> the scope could move to something wider but later I think
[18:02] <crevette> asac, you're afraid of a moving target?
[18:03] <crevette> need to go
[18:03] <crevette> byz
[18:10] <pitti> kenvandine_wk: ah, welcome back
[18:13] <kenvandine_wk> i rebooted before lunch and walked away :)
[18:13] <pitti> kenvandine_wk: ah, I was afraid that U1 synced you over into the cloud
[18:13] <kenvandine_wk> hehe
[18:14] <kenvandine_wk> it seems to have lost 400M of my data somewhere though :)
[18:14] <kenvandine_wk> doing a diff now
[18:14] <kenvandine_wk> which is very slow for 3G
[18:26] <jcastro> didrocks: ~30 minutes until your session!
[18:27] <didrocks> jcastro: yes, ready. Thanks! :)
[19:01]  * pitti chuckles at gvfs' 90relibtoolize.patch which patches itself
[19:04] <dobey> heh
[19:13] <kenvandine_wk> rickspencer3: i just shared something with you... sharing is fixed now btw
[20:32] <Ampelbein> seb128: the gnome-vfs merge is taking a bit longer, my guess is i'll be ready in 2-3 hours. my home-dsl line is down and i'm stuck with 9.6k/s mobile connection. this is no fun.
[20:32] <chrisccoulson> Ampelbein - ouch
[20:33] <seb128> Ampelbein: there is no hurry karmic just opened
[20:33] <Ampelbein> chrisccoulson: yeah. that's what i said ;-) at least it's free.
[20:33] <seb128> and buildds are busy for some weeks with the initial sync ;-)
[20:34] <chrisccoulson> why is karmic not broken yet? no fun ;)
[20:35] <seb128> chrisccoulson: did you dist-upgrade to it? ;-)
[20:36] <seb128> I ran the initial debian sync today, some thousand updates
[20:36] <chrisccoulson> i did, but it's still working here
[20:36] <chrisccoulson> only in a VM so far though ;)
[20:36] <seb128> give some times to the buildds to do their work ;-)
[20:40] <chrisccoulson> ooh, the save session button in gnome-session-properties works again with the debian version
[20:42] <vuntz> chrisccoulson: yes, it's a patch that I have to review :-)
[20:43] <chrisccoulson> cool, thanks vuntz:)
[20:48] <chrisccoulson> vuntz - some users are enabling session saving in the preferences, then disabling it sometime later on, but get confused that it doesn't clear their ~/.config/gnome-session/saved-session when they do that. is that the intended behaviour, and should there be a "restore default" button in the preferences to clear the saved session?
[20:52] <vuntz> chrisccoulson: it's semi-broken right now. It will get fixed later
[20:52] <chrisccoulson> thanks
[20:52] <vuntz> chrisccoulson: (ie, this behavior will change)
[20:58] <robby_> Hello
[20:59] <robby_> Anyone here
[20:59] <Rue-kun> Hello anyone out there?
[20:59] <rickspencer3> Rue-kun: what's up?
[21:00] <Rue-kun> I had a question about the kickoff menu
[21:00] <pitti> good night everyone!
[21:00] <Rue-kun> THe favorites menu that shows up. Is there a way to move it hide it?
[21:01] <rickspencer3> 'night pitti
[21:01] <rickspencer3> don't forget that if the barrels land in the oil drum they can climb ladders!
[21:01] <rickspencer3> Rue-kun: I'm wondering if you are looking for #ubuntu for support?
[21:02]  * pitti remembers the old C64 days
[21:02] <pitti> *wave*
[21:02] <rickspencer3> but which favorites menu do you refer to?
[21:02] <Rue-kun> Ok in Kubuntu the little start menu type thing
[21:02] <rickspencer3> oh
[21:03] <seb128> pitti: 'night
[21:04] <rickspencer3> Rue-kun: you're welcome to hang out here, but unfortunately, we won't be able to answer that too well
[21:04] <rickspencer3> if you go to #kubuntu, you should be able to discuss there and get answers
[21:04] <rickspencer3> this room is more for people who are developing Ubuntu itself
[21:04] <Rue-kun> Ok thank you rickspencer3 sorry ^_^
[21:04] <rickspencer3> (again, you're more than welcome to hang out, though)
[21:05] <rickspencer3> Rue-kun: no apologies necessary
[21:05] <rickspencer3> I'm glad you're using Kubuntu, it's a kick ass desktop
[21:05] <rickspencer3> :)
[21:05] <Rue-kun> It gets the job done
[21:08] <Rue-kun> Oh oh I have a questions that the devlopment team might be able to answer ^_^
[21:08] <Rue-kun> Did you ever fix the network manager bug?
[21:09] <rickspencer3> Rue-kun: which bug do you mean?
[21:10] <Rue-kun> Where it wont allow you to keep static ip addesses unless you uninstall the manager then manually write files?
[21:21] <rickspencer3> Rue-kun: that's a kubuntu bug, I believe
[21:22] <rickspencer3> and I believe there were release notes for how to work around it
[21:22] <rickspencer3> a good question for #kubuntu I would guess
[21:22] <Rue-kun> No it happened on my ubuntu compter idk if kubuntu works
[21:25] <Rue-kun> The final comand was "suso nano etc/network/interfaces"
[21:27] <Ampelbein> Rue-kun: do you mean bug 185584?
[21:27] <Ampelbein> erm bug 185854
[21:27] <Ampelbein> https://bugs.edge.launchpad.net/bugs/185854
[21:28] <Rue-kun> Yes
[21:28] <Ampelbein> fixed since 14.04.2008
[21:29] <Rue-kun> My teacher will be delighted to hear that
[21:37] <rickspencer3> kenvandine_wk: I saved a file in the shared folder
[21:37] <rickspencer3> can you see it?
[21:38] <dobey> doh, mvo is gone
[21:38] <kenvandine_wk> rickspencer3: let me check
[21:39] <kenvandine_wk> rickspencer3: no...
[21:39] <kenvandine_wk> rickspencer3: i have filed several bugs this afternoon related to sharing
[21:39] <rickspencer3> I created it in gedit, and saved it to the share folder
[21:39] <rickspencer3> but when I look at the folder in nautilus, it's not there
[21:39] <kenvandine_wk> rickspencer3: did you have any trouble creatin git?
[21:39] <kenvandine_wk> creating it
[21:39] <rickspencer3> but I can close and reopen the file from within gedit
[21:39] <kenvandine_wk> humm
[21:40] <kenvandine_wk> verify the path
[21:40] <kenvandine_wk> and look at ~/.cache/ubuntuone/logs/syncdaemon.log
[21:40] <rickspencer3> I saved it into Shared With Me/Ubunto One from System Users
[21:41] <kenvandine_wk> syncing is completely busted for me atm... waiting for a new build with a bug fix
[21:41] <rickspencer3> Shared With Me/Ubunto One from System User
[21:41] <kenvandine_wk> oh
[21:41] <kenvandine_wk> it should be "Desktop Team shared from Ken VanDine"
[21:41] <kenvandine_wk> something like that
[21:41] <kenvandine_wk> that was read only for pitti
[21:41] <rickspencer3> nothing says that
[21:41] <kenvandine_wk> and he forced it
[21:41] <rickspencer3> it's all "System User"
[21:41] <kenvandine_wk> humm
[21:42] <kenvandine_wk> rickspencer3: you saw the Test.txt file?
[21:42] <rickspencer3> no
[21:43] <kenvandine_wk> what's in your "Shared with me" folder?
[21:43] <rickspencer3> geez, where is it mounted?
[21:44] <kenvandine_wk> ~/Ubuntu One/Shared With Me
[21:44] <rickspencer3> never mind, found it
[21:44] <rickspencer3> rick@rick-desktop:~/Ubuntu One/Shared With Me$ ls
[21:44] <rickspencer3> Canonical from System User  Company Information from System User  Ubuntu One from System User
[21:44] <kenvandine_wk> it's not a mount point anymore
[21:44] <kenvandine_wk> ok, you aren't seeing my share
[21:44] <rickspencer3> here
[21:44] <rickspencer3> dr-xr-xr-x 3 rick rick 4096 2009-04-29 07:42 Canonical from System User
[21:44] <rickspencer3> dr-xr-xr-x 2 rick rick 4096 2009-04-29 07:41 Company Information from System User
[21:44] <rickspencer3> drwxr-xr-x 7 rick rick 4096 2009-04-29 13:37 Ubuntu One from System User
[21:44] <rickspencer3> easier
[21:45] <rickspencer3> is it possible that U1 is not running for me?
[21:45] <kenvandine_wk> possible
[21:45] <kenvandine_wk> or
[21:45] <kenvandine_wk> just not syncing
[21:45] <kenvandine_wk> which is the problem i have now
[21:45] <kenvandine_wk> it synced 2.6G of data
[21:45] <kenvandine_wk> then decided it wasn't gonna do any more ;)
[21:45] <rickspencer3> heh
[21:46] <kenvandine_wk> not even trying to sync... corruption in some metadata
[21:46] <rickspencer3> I think the lock file was not deleted properly, so it's not running for me
[21:46] <kenvandine_wk> they are working on getting me a fix now
[21:46] <kenvandine_wk> pitti had that problem
[21:46] <kenvandine_wk> filed a bug about it
[21:46] <kenvandine_wk> so whack the lock file
[21:46] <rickspencer3> but I can't tell where the lock file is
[21:47] <kenvandine_wk> ~/.cache/ubuntuone/syncdaemon/.lock
[21:47] <kenvandine_wk> something like that
[21:47]  * rickspencer3 looks
[21:47] <kenvandine_wk> make sure syncdaemon isn't running
[21:49] <rickspencer3> ok
[21:49] <rickspencer3> I deleted the lock file, and then quit U1, and restarted it
[21:49] <rickspencer3> seems to be moving now
[21:50] <rickspencer3> I see your folder now
[21:50] <kenvandine_wk> woot
[21:50] <kenvandine_wk> try to edit Test.txt
[21:50] <rickspencer3> the folder is read onlyu
[21:51] <kenvandine_wk> right
[21:51] <kenvandine_wk> ok
[21:51] <kenvandine_wk> i filed that bug already :/
[21:51] <rickspencer3> heh
[21:51] <rickspencer3> chmod the folder?
[21:51] <kenvandine_wk> about 30m ago
[21:51] <kenvandine_wk> you can
[21:51] <kenvandine_wk> i think it should work
[21:53] <rickspencer3> *sigh* I didn't chmod recursively :)
[21:53] <rickspencer3> I edited it
[21:53] <rickspencer3> (the Test.tx that is)
[21:53] <kenvandine_wk> ok
[21:54] <rickspencer3> I see how my .lock file got screwed up
[21:54] <rickspencer3> you can run multiple instances of U1
[21:54] <rickspencer3> that's probably a bug
[21:54] <kenvandine_wk> yeah
[21:54] <kenvandine_wk> ok... so do this
[21:55] <kenvandine_wk> u1sync --diff ~/Ubuntu\ One/Shared\ With\ Me
[21:55] <rickspencer3> will do, but it seems to be working now
[21:55] <kenvandine_wk> not syncing your changes out
[21:55] <kenvandine_wk> or i don't think it is
[21:55] <rickspencer3> ok, gave it access to my keyring
[21:56] <rickspencer3> hmm
[21:56] <rickspencer3> kenvandine_wk: was the command supposed to return?
[21:57] <kenvandine_wk> files that need to be synced
[21:57] <kenvandine_wk> nothing?
[21:57] <rickspencer3> it popped a dialog asking for access to my key ring, then blocked at the CL
[21:57] <kenvandine_wk> it takes time
[21:57] <rickspencer3> k
[21:57] <kenvandine_wk> and no progress
[21:58] <rickspencer3> the log file does not appear to be changing, and the icon is not moving
[21:58] <kenvandine_wk> i am betting it will say your version of the file differs
[21:58] <kenvandine_wk> yeah
[21:58] <kenvandine_wk> i need to run though... time to get the kids to soccer practice
[21:58] <rickspencer3> ok
[21:58] <kenvandine_wk> will check tonight to see if the new build fixes some of this stuff
[21:58] <rickspencer3> I can help more tomorrow
[21:58] <kenvandine_wk> good
[21:58] <rickspencer3> it *looks* very good
[21:58] <kenvandine_wk> i'll ping you in the morning
[21:58] <rickspencer3> very polished look and feel
[21:59]  * calc will be trying to upload OOo 3.1.0~rc2-1ubuntu1 today if he can get it working... debian guy forgot to commit his change so i also have to diff his debian dir to the debian bzr repo
[23:15] <Ampelbein> harr. back again on 16Mbit/s. now i'm gonna rock!
[23:19] <chrisccoulson> Ampelbein - that's good news
[23:19] <chrisccoulson> that's faster than my connection
[23:19] <chrisccoulson> my broadband dropped to 3.6kbps a few weeks ago, after i told my ISP i was leaving them
[23:20] <Ampelbein> chrisccoulson: whoa. you should cancel your contract... oh wait ;-)
[23:20] <chrisccoulson> heh. i'm glad that i'm rid of them now
[23:22] <Ampelbein> i can't complain here. 16mbit down, 1mbit upstream, no limit for 29 Euro/month
[23:22] <Ampelbein> today was only the second time this year that the line went down.
[23:22] <Ampelbein> but it's usually up after 3-10 hours, so...
[23:24] <chrisccoulson> yeah, that sounds pretty good. is that cable or dsl?
[23:25] <Ampelbein> dsl