[06:28] <pitti> Good morning everyone! happy new year
[07:43] <lool> pitti: happy new year to you too
[07:43] <pitti> bonjour lool
[07:43]  * pitti -> supermarket, bbl
[08:21] <pitti> lool: had some nice holidays?
[08:40] <chrisccoulson> good morning everyone (and welcome back)
[08:40] <pitti> hey chrisccoulson, happy new year!
[08:40] <chrisccoulson> happy new year to you too pitti :)
[08:40] <chrisccoulson> did you have a nice break?
[08:41] <pitti> I did, very relaxing; we painted some rooms, did some major cleaning, lots of family events, and tons of snow \o/
[08:41] <seb128_> hey there
[08:41] <seb128_> happy new year!
[08:41] <chrisccoulson> excellent, sounds good
[08:41] <chrisccoulson> hey seb128_, happy new year to you too
[08:42] <seb128> hey chrisccoulson, how are you?
[08:42] <seb128> had good holidays?
[08:42]  * pitti hugs seb128
[08:42]  * seb128 hugs pitti
[08:42] <chrisccoulson> seb128 - yeah, good thanks, although quite busy with family visiting all the time
[08:42] <chrisccoulson> did you have a good holiday too?
[08:42] <seb128> yes, very relaxing
[08:43] <seb128> lot of doing nothing and familly seeing
[08:43] <seb128> that's always good ;-)
[08:43] <seb128> I manage to barrely touch the computer
[08:43] <seb128> which is a good thing to do once a year too
[08:47] <seb128> hum
[08:48] <seb128> not looking forward email catching up after those two weeks now
[08:48] <seb128> let's grab coffee first
[08:48] <seb128> brb
[08:50] <pitti> seb128: good luck!
[08:50] <pitti> seb128: is it actually so bad?
[08:50] <pitti> I just spent an hour on them yesterday to get them back to 0
[08:50] <pitti> it was pretty quiet over the holidays
[08:50] <pitti> s/0/3/
[08:52] <lool> pitti: Yup, how about you?  good holidays?
[08:52] <pitti> lool: indeed; lots of fresh air, family, and gaming; and only some hacking
[08:52]  * pitti played Battle for Wesnoth a lot
[08:53] <lool> haha
[08:55] <seb128> lool, hey, happy new year!
[08:56] <seb128> pitti, well, not bad but if you want to overview the bugsmails...
[08:56] <seb128> it usually takes me 2 hours after a weekend
[08:56] <pitti> yeah, I didn't touch those yet
[08:56] <seb128> so after 2 weeks
[08:56] <pitti> I just followed up on the high-urgency ones (subscribed/assigned)
[08:56] <pitti> my +ubugs folder is full again :(
[08:57] <seb128> I've installed ubuntu on my cousin's laptop yesterday, that's a fail btw
[08:57] <pitti> karmic?
[08:58] <seb128> yes
[08:58] <seb128> no eth nor wifi working
[08:58] <seb128> which is fixed in a linux sru done in december
[08:58] <seb128> I had to download the deb and copy it over usb key
[08:58] <seb128> and I still have no bluetooth
[08:58] <seb128> and screen doesn't come back from suspend
[08:58] <seb128> which I'm not sure how to debug
[08:59] <seb128> it's a toshiba laptop, I would not recommend those for ubuntu
[08:59] <seb128> jockey is a fail too, it activates fglrx but still mark it as not activated
[09:00] <seb128> ie the xorg.conf is correctly update and fglrx loaded in Xorg.0.log but the jockey UI still say it's not used
[09:02] <tseliot> seb128: in lucid?
[09:06] <seb128> tseliot, no, karmic
[09:06] <seb128> tseliot, it's early to install lucid on a luser box
[09:07] <tseliot> seb128: this is why I asked ;)
[09:07] <seb128> my cousin is a student and need to box to get work done and is nothing of a computer person
[09:07] <seb128> to box -> the box
[09:08] <tseliot> seb128: does the fglrx driver work?
[09:08] <seb128> the videocard is a radeon hd 4500 m92 I think
[09:08] <seb128> I'm not sure actually but I think so by looking through the xorg log
[09:08] <tseliot> or is it just that jockey shows it as disabled?
[09:08] <tseliot> seb128: can I see the log?
[09:08] <seb128> and 2d performance are slugish, ie you can the trail when moving things on screen
[09:09] <seb128> tseliot, with fglrx?
[09:09] <tseliot> yep
[09:09] <seb128> give me a few minutes, I cleaned that yesterday
[09:09] <seb128> I thought it might be what was breaking resume
[09:09] <seb128> but it has the same issue using ati
[09:10] <seb128> I will install it again now
[09:11] <tseliot> ok
[09:11] <lool> seb128: Happy new year to you too!  Hope you got some rest after new year celebrations!  :-)
[09:12] <seb128> lool, I sort of got used to sleep until 10am, was hard to wake up today ;-)
[09:12] <seb128> but yeah, I got plenty of sleep too
[09:12] <pitti> seb128: heh, me too; forced myself out of bed at 7 today
[09:13]  * lool ponders sending a "Happy GNU year" to a GNOME list   ;-)
[09:13] <chrisccoulson> lol
[09:14] <seb128> lool, is you new year resolution to do extra trolling? ;-)
[09:38] <pitti> argh, pitivi pulls in hal
[09:38] <pitti> seb128: ^ just looking at the outstanding alpha-2 work items, and pitivi/gbrainy MIRs are on your list; can you do them?
[09:38] <pitti> (nevermind about pitivi as long as it uses hal, though)
[09:39] <seb128> they are not on my list and I guess I could though I've zillions of things to do after 2 weeks break
[09:39] <pitti> seb128: well, the work items are assigned to you
[09:39] <seb128> and those are nowhere near of what I consider priorities or things I enjoy to do
[09:39] <pitti> but I'm happy to reassign the gbrainy one to me
[09:39] <seb128> I didn't know until now thanks for letting me know
[09:39] <seb128> that would be great
[09:39] <seb128> would be nice if somebody was processing the mirs too
[09:40] <seb128> I opened the libiphone, etc ones a month ago ;-)
[09:40] <seb128> though there was end of year break in the middle so I guess delay was expected
[09:40] <seb128> tseliot, ok, jockey fails to install fglrx today
[09:40] <pitti> asac: ^ got some time for that?
[09:40] <seb128> tseliot, when I tried yesterday that was before doing the karmic updates though
[09:41] <pitti> seb128: for http://piware.de/workitems/desktop/lucid-alpha2/report.html#seb128 , the third and remaining one is "pull new f-spot with edit capabilities in viewer mode", then you are done for alpha-2
[09:41]  * pitti reassigns the gbrainy one to him
[09:41] <tseliot> seb128: maybe debug mode will help you see why it fails
[09:41] <seb128> pitti, ok thanks
[09:41] <seb128> tseliot, log in non debug mode seems useless
[09:41] <seb128> how do I turn debug mode on?
[09:42] <tseliot> seb128: killall jockey-backend
[09:42] <tseliot> seb128: and sudo /usr/share/jockey/jockey-backend --debug -l > /var/log/jockey.log
[09:42] <seb128> pitti, when is a2?
[09:42] <tseliot> then run jockey as usual
[09:42] <pitti> seb128: Jan 14
[09:42] <seb128> ok
[09:42] <seb128> I can do the pitivi mir and the f-spot change this week
[09:42] <pitti> cool
[09:43] <tseliot> pitti: does this look good to you (see the last two commits)? https://code.launchpad.net/~albertomilone/jockey/alternatives
[09:44] <tseliot> that assumes that my new nvidia-common is uploaded first ;)
[09:46] <huats> morning everyone
[09:48] <pitti> tseliot: first commit is obvious; I can't verify the second just by looking at the diff, but structurally it looks fine; please go ahead and commit (I just added you to the team)
[09:48] <pitti> hey huats
[09:48] <tseliot> pitti: great, thanks
[09:48] <huats> hello mister pitti
[09:51] <seb128> tseliot, ok, the new error is my fault, I mixed proposed versions and updates ones and don't have a proposed source
[09:51] <seb128> I will sort that later and ping you when I've an xorg log
[09:52] <seb128> hey huats
[09:54] <tseliot> seb128: ok
[10:03] <seb128> tseliot, otherwise do you know if they are known suspend, resume issues due to the ati driver?
[10:16] <tseliot> seb128: not that I know of
[10:16] <tseliot> tjaalton: ^^
[10:20] <tjaalton> no idea, I don't even know if fglrx works at all
[10:20] <seb128> tjaalton, the question was about ati no fglrx though
[10:20] <seb128> the screen doesn't come back on resume
[10:20] <tjaalton> seb128: ah ok
[10:20] <seb128> the box is a toshiba laptop with a radeon hd 4500 card
[10:20] <seb128> ati m92 mobility I think...
[10:20] <tjaalton> try booting witn radeon.modeset=0
[10:21] <tjaalton> with
[10:21] <seb128> where do I put that?
[10:21] <tjaalton> kernel cmdline
[10:21] <seb128> on the kernel options?
[10:21] <tjaalton> yes
[10:21] <seb128> ok thanks
[10:22] <tjaalton> if that works, bug the kernel people to got through the drm commits ;)
[10:22] <tjaalton> *go, dammit
[10:23] <tseliot> KMS should be already off in Karmic
[10:23] <tseliot> for ati
[10:24] <tjaalton> huh, it was karmic?
[10:24] <seb128> yes
[10:24] <tjaalton> ok, there probably are bugs yes ;)
[10:25] <seb128> there is no kms active there
[10:25] <seb128> ie vt1 is plain old text mode
[10:25] <tjaalton> right, it was enabled after lucid alpha1
[10:25] <seb128> is there anything else worth testing?
[10:25] <seb128> updated ati driver from a ppa or something?
[10:26] <tjaalton> it's likely a kernel drm bug
[10:26] <tjaalton> so try lucid
[10:28] <seb128> great
[10:28] <seb128> the box is not mine though and I don't think lucid is production ready quality wise
[10:28] <seb128> I guess I will just tell him to keep using vista for now :--
[10:28] <seb128> :-(
[10:29] <tjaalton> well, a daily livecd should be enough to test it
[10:31] <seb128> right I will do that
[10:32] <seb128> bah, some random user wrote a 1 page comment explaining how to remove pulseaudio and break half of your system and keep copying it in random bugs
[10:39] <chrisccoulson> seb128 - hggdh contacted him last night about those
[10:39] <seb128> good
[10:40] <seb128> is there any way in karmic to tell polkit1 to not ask for a password to mount ntfs disks?
[10:40] <chrisccoulson> we requested on #launchpad that they deactivate their account when we noticed what they was doing, but they weren't keen on doing that
[10:40] <seb128> ie to mount the vista partition on the same disk
[10:43] <pitti> seb128: copy /var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.DeviceKit.Disks.pkla from lucid to that karmic system
[10:43] <pitti> seb128: http://paste.ubuntu.com/351179/
[10:43] <seb128> pitti, thanks
[10:48] <pitti> seb128: FYI, I dropped the MIR bits from the whiteboard and linked to two MIR bugs (just stubs for now)
[10:48] <pitti> (to avoid confusion about the whiteboard diffs)
[10:48] <seb128> pitti, ok thanks
[11:01] <seb128> pitti, thanks for renewing my membership, I didn't read my launchpad box during holidays and didn't notice it expired
[11:01] <pitti> seb128: my pleasure
[11:06] <asac> pitti: seb128: yes. checking
[11:07] <seb128> hey asac, happy new year
[11:07] <seb128> pedro_, hey, happy new year!
[11:07] <pedro_> happy new year seb128!
[11:07] <seb128> asac, no hurry for the mir but this week would be nice
[11:07] <seb128> pedro_, had good holidays? ;-)
[11:09] <asac> happy new year too!!
[11:09] <pitti> hey asac, gesundes Neues!
[11:09] <pedro_> seb128, yeah, thanks for asking, what about you?
[11:09] <asac> hey pitti .... hope you are a bit less burried in snow than we are ;)
[11:09] <pedro_> happy new year pitti and asac!
[11:09] <asac> crazy winter
[11:09] <pitti> hey pedro_, happy new year!
[11:09]  * asac hugs pedro_ 
[11:09] <seb128> pedro_, yes, pretty relaxing ;-)
[11:10]  * pedro_ hugs asac back
[11:10] <pitti> asac: it has snown for three days here; all white
[11:10] <pitti> we had a great "Schneeballschlacht" yesterday :)
[11:10] <seb128> lucky you
[11:10] <pitti> and I built a snowman with my niece
[11:10] <seb128> we had some snow 2 weeks ago
[11:10] <seb128> but not since
[11:10] <asac> hehe
[11:17] <pitti> seb128: btw, hold on with the MIR; I'll propose some MIR process simplification on u-devel@, just doing some wiki cleanup first
[11:17] <seb128> ok thanks
[11:32] <chrisccoulson1> i think freenode hates me today
[11:32] <chrisccoulson1> i keep getting disconnected
[11:47] <pitti> seb128: sent to MIR team and CCed u-devel@; your feedback appreciated
[11:47] <seb128> pitti, I'm about to go for lunch but I will comment after that
[11:50] <pitti> seb128: btw, I had a quick look at the brasero nautilus plugin; I don't see any obvious time difference with and without (but I didn't measure very carefully); is it still taking a second? If so, want me to look into this?
[11:52] <seb128> pitti, you are welcome to do so, it takes over 1 second there on the mini config
[11:52] <seb128> and over 3 seconds on my laptop config
[11:53] <pitti> urgh
[11:53] <seb128> if you strace it you will see it execve every commands it known with --version to know what is available
[11:55] <pitti> seb128: ok, I think I'll prepare a test nautilus which gives some debugging output for plugin loading and exits once it loaded everything
[11:55] <pitti> that should be convenient for timing
[11:55] <seb128> right
[11:56] <seb128> ideally the code should just register what it can do
[11:56] <pitti> I have no urgent non-blocked alpha-2 tasks any more, and working on speedup is urgent, so I'll do that now
[11:56] <seb128> not do all the brasero .so init
[11:56] <pitti> right
[11:56] <pitti> and defer expensive bits to lazy initialization
[11:56] <seb128> right
[11:56] <seb128> or to first use or something
[11:57]  * pitti hardly burns any CDs these days, and I guess the same is true for many people
[11:57] <pitti> in particular for netbook users who don't even have a drive :)
[11:57] <pitti> seb128: lazy init == first use, right, that's what I mean
[11:57] <seb128> ok, you can also see lazy init as idle loop code
[11:57] <pitti> seb128: btw, do you have your test gnome-session somewhere which loads everything at once?
[11:58] <pitti> ah
[11:58] <seb128> it's not a gnome-session change
[11:58] <seb128> I've emptied the gconf key for required components
[11:59] <seb128> ie /desktop/gnome/session/required_components_list
[11:59] <pitti> oh, I thought it was this Autostart-Phase: thing
[11:59] <pitti> okay
[11:59] <seb128> copied the nautilus and gnome-panel autostart from /usr/share/applications to etc
[11:59] <seb128> to /etc/xdg/autostart
[12:00] <seb128> and changed all the desktop files there to have Application for the autostart stage
[12:00] <seb128> so everything is started as an application
[12:00] <seb128> and they are all started together
[12:00] <seb128> just copy /etc/xdg/autostart away
[12:00] <seb128> do the changes and try
[12:00] <seb128> have to go for lunch
[12:00] <seb128> be back in a bit
[12:00] <pitti> ok, was just curious
[12:00] <pitti> enjoy!
[12:24] <pitti> seb128: yep, after a 3 > drop_caches, brasero takes ages here, too
[12:24]  * pitti has a debug nautilus now
[12:28] <pitti> seb128: thanks for the heads-up, I think I'm good to go now
[12:29] <seb128> back from lunch
[12:29] <seb128> pitti, ok good, let me know if you have any question
[12:29] <seb128> pitti, you got a reference hardware box?
[12:30] <seb128> pitti, or you use your laptop to do testing?
[12:30] <pitti> seb128: my normal laptop; I don't have a Dell mini
[12:30] <pitti> but that should be good enough
[12:30] <seb128> right
[12:30] <seb128> enough people do daily testing on the mini anyway
[12:31] <seb128> and what improves on your box should benefit other installs too
[12:52] <asac> pitti: http://pastebin.com/f21452d4b ... let me know if its ok to carry that fix in ubuntu/debian for a bit. for upstream one probably would have to check in configure if gcc has that feature :/
[13:20] <pitti> asac: looks fine, but please do report it upstream as well
[13:20] <pitti> asac: I'll turn it into a patch and commit to bzr
[13:22] <pitti> asac: hm, does that work on "arm" as well, or only "armel"?
[13:25] <pitti> ah, bug 497331
[13:26] <pitti> it does build on Debian's armel, I guess that doesn't use thumb2
[13:28] <pitti> asac: ok, pushed and bug updated
[13:41] <asac> thx
[14:00] <dholbach> hola
[14:01] <kenvandine> het dholbach
[14:01] <kenvandine> hey even :)
[14:01] <dholbach> can anybody imagine running a session at UDW: https://wiki.ubuntu.com/UbuntuDeveloperWeek/Prep still has a couple of empty slots
[14:01] <dholbach> hey kenvandine
[14:01] <pitti> hey kenvandine, happy new year!
[14:01] <kenvandine> happy new year too you too!
[14:02] <seb128> hey dholbach kenvandine
[14:02] <seb128> happy new year
[14:02] <dholbach> maybe something about what's specific to packaging desktop stuff?
[14:02] <dholbach> I'm sure you guys want more desktop contributors :-D
[14:02] <seb128> pitti, the measure I did before holidays for nautilus loading times were similar to your notes
[14:03] <seb128> everything else than brasero was around 0.1 seconds or under that
[14:03] <seb128> share was faster there but you might use a non empty nautilus config
[14:04] <pitti> ok, thanks
[14:05] <dholbach> or is there anything else desktop related that would fit well into UDW?
[14:05] <kenvandine> hey seb128
[14:09] <kenvandine> seb128, i'll bump empathy today
[14:10] <seb128> thanks
[14:10] <seb128> hey tedg
[14:10] <seb128> tedg, happy new year
[14:10] <tedg> Good morning seb128.  Good holiday?
[14:10] <tedg> Thanks
[14:10] <seb128> yes, excellent
[14:10] <seb128> didn't touch work stuff for 2 weeks
[14:11] <seb128> nor email
[14:11] <seb128> (or almost not, I did read email 3 times in 2 weeks)
[14:11] <chrisccoulson> dholbach - i keep thinking that a session on debugging X errors would be useful, to help with issues like gnome bug 598476, but i just don't have any time at the moment :(
[14:11] <tedg> Wow.  That's impressive.
[14:12] <chrisccoulson> such a session would be closely related to interpreting stacktraces anyway
[14:12] <dholbach> chrisccoulson: maybe bryce__ and tseliot have some ideas for that? ^
[14:12] <tedg> seb128: Are you testing to see if Evolutions mail counting algorithms can count to a million? ;)
[14:12] <dholbach> chrisccoulson: shall I mail you three guys and we can debate what would go in there?
[14:12] <seb128> tedg, I almost could ;-)
[14:12] <chrisccoulson> dholbach - possibly. i'd like to do such a session, but i'd struggle to find the time at the moment
[14:13] <seb128> very annoyed by the spam count though
[14:14] <dholbach> chrisccoulson: a bunch of bullet points and some discussion with bryce__ and tseliot would be appreciated - I'll kick off the mail in a sec :-)
[14:15] <tseliot> chrisccoulson, dholbach: yes, an email would be fine :-)
[14:15] <dholbach> fantastico
[14:15] <tseliot> ;)
[14:16] <chrisccoulson> the gnome-screensaver issue might be a good example for a session too, because i already understand why that broke :)
[14:18] <dholbach> tseliot, bryce__, chrisccoulson: sent
[14:18] <tseliot> thanks
[14:41] <kenvandine> good morning rickspencer3
[14:41] <rickspencer3> hi kenvandine
[14:41] <rickspencer3> so, we're back
[14:41] <kenvandine> yup!
[14:41] <rickspencer3> :)
[14:41]  * rickspencer3 checks calendar, checks email
[14:41] <rickspencer3> aaah
[14:42] <pitti> hey rickspencer3! happy new year!
[14:43] <rickspencer3> happy new year pitti
[14:43] <rickspencer3> pitti, how was your vacation?
[14:44] <seb128> hey rickspencer3
[14:44] <pitti> rickspencer3: I really enjoyed it; got some household stuff done (wallpainting, cleaning), lots of snow, some gaming, and some hacking
[14:44] <seb128> happy new year!
[14:45] <pitti> it was good to rest for some ten days
[14:45] <dholbach> ArneGoetje: do you think you could follow up on https://lists.ubuntu.com/archives/ubuntu-motu/2010-January/006447.html ?
[14:46] <rickspencer3> hi seb128
[14:47] <ArneGoetje> dholbach: looking
[14:47] <seb128> rickspencer3, did you have good holidays?
[14:48] <rickspencer3> seb128, yes
[14:48] <pitti> rickspencer3: I saw your blog entries, seems you hacked all the time :)
[14:48] <rickspencer3> spent quite some time with my family, and did some hacking, yes
[14:48] <pitti> quidmasgets
[14:49] <rickspencer3> pitti, I see an MRI bug for pitivi
[14:49] <rickspencer3> thanks for doing that
[14:50] <pitti> rickspencer3: it's just a stub so far
[14:50] <pitti> rickspencer3: biggest problem is that it pulls hal back in
[14:50] <kenvandine> eww
[14:50] <pitti> (and of course all those bugs :) )
[14:50] <kenvandine> i used it a couple times over the break and it worked pretty well
[14:50] <pitti> TBH I only tested it once at UDS
[14:51] <ArneGoetje> dholbach: replied
[14:51] <pitti> I don't know anyone who actually edits videos, so I don't have a real-live test case
[14:51] <pitti> "life"
[14:51] <rickspencer3> I used it a bit last summer
[14:51] <pitti> but either way, we need to do something about hal
[14:51] <rickspencer3> and it worked quite well
[14:51] <rickspencer3> but was a tad crashy
[14:51] <kenvandine> i do from time to time... my biggest beef is it is such a pain to get dv video off the camera
[14:51] <dholbach> ArneGoetje: awesome - thanks
[14:51] <dholbach> ArneGoetje: moderated
[14:53] <ArneGoetje> dholbach: thanks
[14:56] <seb128> pitti, I replied to the mir email and some other people too apparently, all good feedback
[14:57] <seb128> go pitti go ;-)
[14:57] <pitti> nice
[15:02] <ccheney> hi
[15:12] <rickspencer3> hi ccheney
[15:12] <rickspencer3> welcome back
[15:13] <rickspencer3> Not too surprised to see we are a bit over the trend line
[15:15] <pitti> hey ccheney, happy new year!
[15:15] <pitti> rickspencer3: right, you can clearly see the holidays..
[15:16] <rickspencer3> stupid holidays
[15:16] <rickspencer3> ;)
[15:28] <seb128> pitti, we should perhaps have small template for mir bugs and decide on whether the description or comments should be used too
[15:28] <seb128> template, ie:
[15:28] <seb128> rational: we need a video editor
[15:28] <seb128> security: no known issue
[15:28] <seb128> packaging: standard cdbs one, actively maintained in debian
[15:29] <pitti> seb128: i don't actually expect security/packaging to be in mir bugs at all if they are okay
[15:29] <pitti> (we still review the packaging anyway)
[15:29] <seb128> ok, good
[15:29] <pitti> seb128: I just expect reporters to walk through UbuntuMainInclusionRequirements and pick out the bad stuff
[15:29] <seb128> I was just doing the pitivi one and I'm not too sure what to write about "well maintained upstream and in debian, no security issue"
[15:29] <seb128> ok
[15:29] <pitti> (which is why I want people to explicitly confirm that they did this, to ensure that they know about the page and sign off on having done the checks)
[15:30] <seb128> it just feel weird when you are used to write every detail, but good weird ;-)
[15:30] <pitti> just go through the checklist, and note down things that come to your mind when you review the package
[15:31] <seb128> pitti, ie do you expect extra comments on https://bugs.launchpad.net/bugs/502897?
[15:32] <pitti> seb128: yes, one: "a confirmation that you checked the requirements carefully"
[15:34] <seb128> pitti, ok, done
[15:35] <seb128> I'm not sure if we should delay its use until it stops using hal though
[15:37] <pitti> seb128: thanks, moved back to new and assigned to me
[15:37] <seb128> pitti, thank you
[15:37] <pitti> seb128: if we put it in now, we need to change hal to get activated on demand, and fix g-p-m to not activate hal on startup
[15:38] <pitti> but that's sort of on my list anyway
[15:38] <seb128> I would be in favor of delaying until pitivi is fixed
[15:38]  * pitti too
[15:38] <seb128> ok good
[15:38] <seb128> let's see how upstream is responsive
[15:38] <pitti> not that I would have ever been anxious to get in pitivi :)
[15:38] <seb128> the bug has been opened 2 days ago
[15:43]  * pitti chuckles at http://people.canonical.com/~scott/daily-bootcharts/
[15:43] <pitti> Keybuk: I want this mysterious "201000" extra month, too!
[15:44] <Keybuk> heh
[15:44] <Keybuk> I just fixed that
[15:44] <seb128> hey Keybuk
[15:44] <seb128> happy new year!
[15:44] <Keybuk> hey, happy new year to you too
[15:45] <seb128> pitti, bug #448180 seems a "gnome-alsamixer crashes when there is no soundcard"
[15:46] <seb128> pitti, do you think it's worth fixing in a sru? it would still do nothing, just display a "no sound card" rather than crashing...
[15:46] <seb128> (not that I fixed the bug yet)
[15:47] <pitti> hm, sounds like a feature to me :) why should it be running if there's no card?
[15:47] <seb128> it seems users try to run it to fix their "no sound issue"
[15:47] <pitti> from my shallow look I'd say don't bother
[15:47] <seb128> which is fact a alsa or driver issue
[15:47] <pitti> if you want to, I won't stop you of course
[15:47] <seb128> ie no sound card is listed by alsa on those config
[15:47] <seb128> not especially
[15:48] <seb128> you just assigned the bug to me so I was checking ;-)
[15:48] <seb128> I will try to get it fixed for lucid so we stop receiving crash bugs
[15:48] <seb128> but I will not bother for karmic
[15:50] <pitti> assigned> ah, that was last year already :)
[15:51] <pitti> right, lucid only
[15:51] <seb128> yeah, but during my holidays
[15:51] <seb128> ok, all good ;-)
[15:54] <rickspencer3> tseliot, hi
[15:54] <tseliot> hi rickspencer3
[15:54] <rickspencer3> happy New Year tseliot
[15:54] <rickspencer3> I saw some mails regarding "Updated plans for Lucid"
[15:55] <tseliot> rickspencer3: happy new year to you :-)
[15:55] <rickspencer3> anything I should know?
[15:55] <tseliot> I think it was a status update that tjaalton wrote
[15:56] <tseliot> I just explained that all my work for the "proprietary improvements" blueprint is in a PPA
[15:56] <tseliot> as I worked on it during the holidays
[15:56] <rickspencer3> tseliot, great, so I don't need to reed those :)
[15:56] <rickspencer3> tseliot, btw, really great work on the mini 10v trackpad
[15:56] <tseliot> rickspencer3: no, don't worry ;)
[15:57] <rickspencer3> turned it from something stupid and frustrating to something that works quite well
[15:57] <tseliot> rickspencer3: thanks, I'm working to make sure that my fixes can be applied in the future (despite the changes in X and udev)
[15:57] <tseliot> :-)
[16:03] <pitti> there, nautilus brasero extension starts in 0.3 secs now
[16:05] <pitti> (from cold cache)
[16:06] <pitti> now it's just class registration and gconf
[16:06] <bratsche> Happy New Year desktop hackers!
[16:06] <seb128> pitti, you rock!
[16:06] <pitti> hey bratsche! happy new year to you, too!
[16:06] <seb128> hey bratsche, happy new year
[16:06] <pitti> seb128: just need to fix that tiny crash now :)
[16:06] <seb128> lol
[16:07] <pitti> burning an .iso from the menu works; clicking menu on computer:/// on CD breaks
[16:07] <seb128> pitti, I opened a bug upstream about it being slow btw so no need to open a new one to add your changes
[16:07] <pitti> seb128: oh, great; which one?
[16:07] <pitti> I'll send my patch there
[16:07] <seb128> sec, looking for the bug number
[16:07] <pitti> oh, you probably did it a while ago already, I'll find it
[16:11] <pitti> seb128: got it
[16:11] <seb128> pitti, ok, sorry I got sidetracked in finishing something else
[16:11] <pitti> NP, took me like 3 seconds to fine
[16:12] <pitti> find
[16:12] <robbiew> pitti: seb128:  pardon if this has already been addressed in a bug or email or whatever :)...but is there a reason why installing nvidia-glx-185 is fubar'd on my 64bit machine?
[16:12] <pitti> robbiew: what breaks in particular?
[16:13] <pitti> (no idea, I don't have nvidia here for testing)
[16:13] <robbiew> pitti: installing that package automatically removes all xserver- packages
[16:13] <robbiew> and without it...nvidia driver doesn't work
[16:13] <robbiew> so stuck with framebuffer
[16:13] <pitti> eww, WTH
[16:14] <pitti> tseliot: seems it needs to depend on the newer x.org ABI?
[16:14] <pitti> robbiew: ^ I think that's it
[16:14] <tseliot> yep
[16:14] <pitti> robbiew: tseliot has new packages in the pipeline, I'm sure that they will work
[16:15] <tseliot> I'm still cleaning them up a bit but they should work: https://edge.launchpad.net/~albertomilone/+archive/proprietary-video-improvements
[16:15] <tseliot> note: you will have to update all of the packages in the PPA
[16:16] <robbiew> pitti: tseliot: thanks
[16:16] <robbiew> :)
[16:16] <robbiew> figured you all were on top of it ;)
[16:16] <tseliot> np
[16:16] <tseliot> robbiew: if you have problems with the drivers, just let me know
[16:17] <robbiew> will do
[16:17] <tseliot> robbiew: also are you going to install the latest driver? 190.53
[16:17] <tseliot> if not, you'll have to type an additional command
[16:18]  * robbiew is all about the latest and greatest :D
[16:18] <tseliot> ok, no additional work then ;)
[16:20] <rickspencer3> tseliot, you have 50 bugs assigned to you?
[16:21] <tseliot> rickspencer3: I didn't count them but yes, it should be a considerable amount of bugs
[16:21] <rickspencer3> well "bug tasks"
[16:22] <rickspencer3> looks like 10 > medium importanc
[16:22] <Martinp23> if anyone gets a few mins, could you look at bug #502775 please? it's ages since i did packaging so not entirely sure if i'm following the right procedure here :p
[16:22] <tseliot> rickspencer3: let me check
[16:22] <pitti> seb128: so, fixed the crash; I can't say that brasero actually worked before (it keeps complaining about not having enough space on CD), but at least it now works as before
[16:23] <seb128> pitti, ok good, and upstream have time to comment on the changes before lucid
[16:23] <seb128> pitti, btw there is a 2.29.4 new version if you feel doing an upgrade too :-)
[16:23] <tseliot> rickspencer3: what's the purpose of you question? (I'm curious)
[16:23] <rickspencer3> tseliot, no action required for you
[16:23] <pitti> seb128: might just as well do; was about to upload, nice timing :)
[16:24] <tseliot> rickspencer3: ah, good
[16:24] <seb128> hey Martinp23
[16:24] <rickspencer3> in general, I like bugs that are assigned to be bugs that are planned for fixing
[16:24] <Martinp23> hi seb128 :)
[16:24] <seb128> usually mvo look at vte updates
[16:24] <seb128> not sure if he's around I've seen him today yet
[16:24] <rickspencer3> tseliot, >10 seems a bit aggressive, but since you're a gues on desktop team, you shouldn't need to change your bug management strategy
[16:25] <pitti> rickspencer3: uh, you consider > 10 too much?
[16:25] <pitti> I was proud to reduce my list from 70 (start of december) to 38 (now) ..
[16:25] <mvo> seb128: hello!
[16:25] <tseliot> rickspencer3: ok. Some of them will be fixed soon
[16:25] <mvo> seb128: did I hear my name :) ?
[16:25] <rickspencer3> pitti, not "too much" just aggressive
[16:25] <seb128> hey mvo
[16:25] <mvo> happy new year
[16:26] <pitti> hey mvo, gesundes Neues! *hug*
[16:26] <seb128> mvo, Happy New Year!
[16:26] <rickspencer3> hi mvo
[16:26] <seb128> mvo, Martinp23 worked on bug #502775
[16:26] <seb128> Martinp23, and was wondering if somebody was feeling like give it a look
[16:26] <seb128> ups
[16:26] <seb128> mvo, ^
[16:27] <mvo> seb128: sure, I can do that
[16:27] <seb128> mvo, thanks
[16:36] <Martinp23> seb128, mvo: thanks! :)
[16:36] <mvo> Martinp23: please give me ~10min, I just need to finish anohter task
[16:37] <Martinp23> sure, no rush at all
[16:50]  * pitti uploads brasero and is eager to see tomorrow's boot chart
[16:50] <pitti> it won't reduce total time (gnome-panel is critical path), but should reduce the nautilus churn
[16:57] <seb128> right
[17:13] <karmst> hello
[17:13] <karmst> is anyone in here?
[17:14] <mvo> Martinp23: looks good, test-building now
[17:15] <baptistemm> karmst, when you enter in a room, do you say "is anyone in here?" ?
[17:15] <mvo> Martinp23: the only "complain" is that you might want to add "debian/patches/90_autoreconf.patch: refreshed" to debian/changelog. but that is really minor :)
[17:15]  * mvo needs to leave for lunch now
[17:15] <mvo> eh, dinner
[17:15] <baptistemm> karmst, usually on IRC, you say hello, and you ask your question
[17:15] <baptistemm> :)
[17:15] <karmst> ok
[17:16] <karmst> I'm new to the linux world but have used windows and dos for over 20 years
[17:16] <karmst> so please be kind =)
[17:17] <karmst> I'm trying to find out if there is a way to have the user home directory sync with a server
[17:17] <karmst> like how in Windows you can use GPO to redirect desktops
[17:18] <karmst> and profiles
[17:18] <karmst> can something be done in Ubuntu similar?
[17:21] <baptistemm> I know zip about windows and I guess this is not the right chan, and this is not specific to ubuntu. I guess you should look to Samba
[17:21] <karmst> I think you didn't get my question
[17:21] <karmst> it is specific to Ubuntu
[17:22] <karmst> Can you have the workstation home directories sync with a server
[17:22] <karmst> so you can have a mobile profile?
[17:22] <seb128> use nfs?
[17:23] <baptistemm> karmst, no this is not specific to ubuntu, this is specific to Linux
[17:23] <seb128> I'm not sure to understand the question, you want datas synced automatically?
[17:23] <karmst> yes
[17:23] <karmst> I want to be able to pull the same home directory on multiple workstations
[17:24] <baptistemm> karmst, nfs should be the solution
[17:24] <karmst> ah
[17:24] <seb128> well nfs is not offline
[17:25] <seb128> it requires connection to the server
[17:25] <karmst> hmmm
[17:25] <karmst> that's what I want
[17:25] <karmst> like my workstation and laptop to sync
[17:25] <seb128> you can try unison for example
[17:25] <Martinp23> mvo: thanks! I've pushed a better changelog to my bzr branch
[17:26] <karmst> or if I go to another workstation for it to have the same Desktop, documents. etc
[17:26] <karmst> by login
[17:26] <seb128> look at unison
[17:26] <karmst> unison
[17:26] <seb128> apt-cache show unison
[17:27] <mvo> thanks Martinp23
[17:27] <karmst> yes
[17:27] <karmst> that's close to what I'm looking for
[17:29] <karmst> Hey thanks Seb I think this will work
[17:29] <karmst> ;)
[17:29] <seb128> you're welcome
[17:30] <karmst> ok and one last question
[17:30] <karmst> What's the best way to make incremental image backups of Karmic?
[17:32] <seb128> not sure about that one, it's not really desktopish
[17:32] <seb128> try #ubuntu-server maybe
[17:32] <seb128> I know that backuppc can do that sort of things
[17:32] <karmst> ok
[17:32] <karmst> thanks
[17:33] <seb128> not sure if that's the best way though
[17:35] <karmst> ah
[17:35] <karmst> I'm not sure if Acronis works on a live Ubuntu
[17:36] <karmst> or maybe symantec?!?
[17:36] <seb128> I don't know those
[17:36] <seb128> the company I was working before used backuppc for incremental backuping
[17:37] <karmst> does that do an image backup?
[17:37] <karmst> or file backup?
[17:40] <seb128> file backups
[17:40] <seb128> you can set up the directories to backup
[17:40] <seb128> it can use smb shares or rsync or ssh
[17:41] <karmst> hmm
[17:42] <karmst> I'm basically looking for something that if the computer gets fried you can restore an entire system to another computer
[17:42] <karmst> even if the hardware is different
[17:45] <seb128> I don't know about a software doing that
[17:51] <karmst> so what do you guys do if your computer blows up?
[17:53] <rickspencer3> karmst, I suppose we keep backups of our files, and then just do a reinstall, etc...
[17:53] <rickspencer3> I think it's pretty rare for a computer to just completely fail with no warning
[18:00] <seb128> I don't think I ever had a computer which blowed up
[18:00] <seb128> and I do backup my user datas
[18:00] <seb128> reinstalling a distro is a 2 hours job
[18:01] <seb128> 2 hours counting the download of things I use which are not on the default install, etc
[18:02] <karmst> true
[18:02] <karmst> that's still quite a bit of time.
[18:02] <seb128> well it's mainly my download speed taking in account there
[18:03] <karmst> true but then what about customization and screens
[18:03] <karmst> and so on
[18:03] <karmst> I'll look around for something and let you know if I find anything
[18:03] <seb128> I do backup user config
[18:03] <seb128> I don't have nonuser customization
[18:04] <seb128> im clients, images, music, etc are in my user dir
[18:04] <seb128> web browser
[18:04] <seb128> keyring
[18:04] <seb128> etc
[18:04] <seb128> installing karmic from an usb stick is 15 minutes job
[18:04] <seb128> then you need to dump your user backup in place and install extra softwares
[18:04] <seb128> but you are basically back to a working system in half an hour
[18:05] <seb128> then you can work while extra things get installed
[18:05] <seb128> well that's my view on that
[18:05] <seb128> but having something to backup and dump back what you did backup later would be cool
[18:05] <rickspencer3> seb128, it would be nice if there was a list of apps that you have installed and you could just say "yes just reinstall all of that list"
[18:06] <seb128> you need at some point to bootstrap the software to write the backup back though
[18:06] <seb128> rickspencer3, it's just 2 dpkg commands ;-)
[18:06] <rickspencer3> seb128, sort of, except that it doesn't get done automatically for you
[18:06] <seb128> right
[18:06] <rickspencer3> like what if you dumped from dpkg and that list got stored in your U1 account
[18:06] <seb128> quickly backup
[18:06] <seb128> quickly restore
[18:06] <rickspencer3> hehe
[18:07] <seb128> yeah, that would be cool
[18:07] <rickspencer3> anyway, nice thoughts for features for future versions
[18:07] <seb128> a small pygtk gui which takes a package list and install things you don't have
[18:07] <seb128> and which let you export your current set
[18:40] <pitti> good night everyone
[18:42] <chrisccoulson> good night pitti
[22:41] <ccheney> anyone know how to fix this http://pastebin.ubuntu.com/351477/ ?
[22:41] <ccheney> trying to recompile karmic glib on hardy
[22:45] <chrisccoulson> ccheney - which release are you building this on?
[22:45] <ccheney> hardy
[22:45] <chrisccoulson> thats why
[22:45] <ccheney> i think i found the issue was with patch 5
[22:45] <chrisccoulson> the hardy glibc doesn't have this symbol
[22:45] <ccheney> yea
[22:46] <ccheney> trying to get the firefox/webkit/e-b stuff done for the old releases
[22:46] <chrisccoulson> if you give me 1 second, i'll find you the officially upstreamed patch, which contains a build-time check for this to make it use it's own internal symbol
[22:47] <ccheney> i tried disabling assert messages but it doesn't seem to work
[22:47] <ccheney> i might have done something wrong though
[22:47] <chrisccoulson> ccheney - this is the official patch, which will be in the next glib version
[22:47] <chrisccoulson> http://git.gnome.org/browse/glib/commit/?id=da66897950431870390f8dc3f798e24f23ffb8c8
[22:47] <chrisccoulson> not sure how that differs to what we already have in ubuntu
[22:48] <chrisccoulson> it should build fine on hardy with that patch, because the configure check will notice your glibc version is too old
[22:48] <ccheney> ok
[22:51]  * ccheney didn't read the rules file close enough it seems