/srv/irclogs.ubuntu.com/2010/03/16/#ubuntu-desktop.txt

chrisccoulsonseb128 - thanks00:09
pittiGood morning07:00
=== MacSlow is now known as MacSlow|afk
RAOFMorning, pitti.07:30
pittihey RAOF, how are you?07:30
RAOFFine.  The smell of bolognese is making me hungry!07:31
pittiRAOF: did you get along with the bug mail filtering stuff?07:31
pittiyummy!07:31
RAOFYup.  I've reconfigured some of my evolution filters; I think the “filter out things of importance, dump the rest in appropriate buckets” method will scale better than the “bump in appropriate buckets” I used earlier.07:32
pittiRAOF: well, both sound like valid implementations, as long as you can make sure to be able to respond to urgent bug mail without getting drowned in the flood of incoming bugs :)07:36
pittiRAOF: ok, thanks for setting that up07:37
RAOFYeah.  I'm going to get a lot more bugs than I'm used to, what with X and a bunch of destkop stuff :)07:42
RAOFMmm, dinner!07:42
pittibryceh: wrt. https://blueprints.edge.launchpad.net/ubuntu/+spec/foundations-lucid-release-collaboration-with-debian, the "X" work item is still open08:11
pittibryceh: I guess we are pretty much settled for our X version in lucid? I guess this meant to be in sync with Debian as much as possible?08:12
sabdflas i understand it, we're driving X in both cases?08:15
pittimost of the client side just comes from Debian08:15
pittifor the server we have a pretty good collaboration between bryceh and tjaalton and the Debian guys, AFAICS08:15
pittiI'm off for a doctor appointment, back in an hour08:16
tjaaltonpitti: there's one stable release update (1.7.6) coming up, debian now has the rc2 version of it. the final should be released later this week most likely08:18
tjaaltonalso, mesa 7.7.1 will be released within two weeks, we have a snapshot of the stable branch (like debian)08:19
=== sabdfl1 is now known as sabdfl
tjaaltonpitti: but yes, we share most of it08:22
=== MacSlow|afk is now known as MacSlow
brycehpitti, oh I'd filled in that info the other day but didn't mark the task done08:47
brycehpitti, look at the blueprint, the X versions are shown there08:47
seb128hey there08:52
pittire09:08
pittibonjour seb12809:08
seb128hey pitti09:08
pittibryceh, tjaalton: thanks! so it seems we can flip that one to DONE?09:09
seb128pitti, how are you?09:09
pittiI'm great, thanks! just back from doctor09:09
brycehpitti, I set it to done, but I didn't actually verify the versions with debian.  But we've been tracking pretty close and I doubt they're going to suddenly do something exotic09:11
seb128pitti, hayfever again?09:11
pittiseb128: yes, it's a series of 10 treatments, twice a week09:11
pittibryceh: *nod*, thanks09:11
brycehpitti, I saw you set me as the assignee for the whole multitouch blueprint!09:11
brycehpitti, I suspect it should be duncan since he's project manager09:12
pittibryceh: oh, please feel free to assign it to someone else if  appropriate; I thought you and Rick said you were going to work on it?09:12
pittibryceh: fine for me; so he'll own the items by default, and you pick out some?09:12
brycehpitti, yes I am but just a portion; most of those tasks on the blueprint are going to be done by other folk09:12
brycehyep09:13
pittibryceh: I'm greatly relieved!09:13
brycehyeah I'm just going to play the role of hired gun on this one09:13
pittibryceh: what's his LP id?09:13
brycehprobably mostly just packaging/testing but we'll see09:13
pittithere are quite a lot of duncans09:13
brycehoubiwann09:14
seb128RAOF, hi09:14
pittiah, right09:14
seb128RAOF, bug #17519109:14
ubottuLaunchpad bug 175191 in f-spot "f-spot changes timestamp in an incorrect way" [Unknown,Confirmed] https://launchpad.net/bugs/17519109:14
bryceh== Duncan McGreggor09:14
pittibryceh: ah, I searched for "McGregor"09:14
pittichanged09:14
brycehpitti, btw this evening I made a new graph09:14
brycehhttp://www2.bryceharrington.org:8080/X/Reports/ubuntu-x-swat/totals-lucid.svg09:15
brycehthat is a (much saner) chart showing just X bugs tagged 'lucid'09:15
seb128RAOF, bug #175191, do you think it's something you can work on for lucid?09:15
ubottuLaunchpad bug 175191 in f-spot "f-spot changes timestamp in an incorrect way" [Unknown,Confirmed] https://launchpad.net/bugs/17519109:15
brycehso that limits it to just bugs we know are relevant on lucid.  Still a lot of bugs but looks more doable09:15
pittibryceh: urgh, half of it are -intel..09:16
brycehpitti, and half of those are bugs collected by the apport freeze hook09:17
pittibryceh: oh, btw, my after-resume corruption finally seems to be fixed \o/ (I'm running 2.6.33 for testing)09:17
brycehgreat09:17
pittiI guess it should also work with our lucid kernel now, with the backported drm; I'll test that again09:17
brycehyes it should09:17
mvopitti: I noticed that you changed module-init-tools at some point, did it build with bzr-buildpackage for you? or did you just plain-old apt-get source when you did it?09:17
pittinow X crashes sometimes after suspend, but at least it works perfectly if it doesn't crash09:17
pittiVcs-Bzr: http://bazaar.launchpad.net/~ubuntu-core-dev/module-init-tools/ubuntu09:18
pittimvo: ^09:18
pittimvo: but I don't remember whether I used bzr bd09:18
mvoright, I use that09:18
mvobut bzr-buildpackage is not happy, not in default nor --split mode09:18
mvoI was just wondering if I overlook something obvious, otherwise I will just bug keybuk when he is around09:19
RAOFseb128: Yeah, I've been investigating it.  As I said on the bug, I think simply not writing the timestamp out to the primary file will solve the most obnoxious problem.09:39
seb128RAOF, seems an easy enough change, can you work on it?09:40
RAOFYup.  I've done it locally.09:40
RAOFThat, plus a number of miscelaneous other fixes should be ready for once the archive unfreezes.09:40
seb128RAOF, if you think you are done with those changes feel free to add the debdiff on launchpad09:45
seb128we can queue uploads so they will go in after unfreeze09:45
seb128that's better than having to run around at the end of the week to see what was waiting09:45
RAOFI actually have upload privs to f-spot now, via the new pkg-mono team.  So, uploads made now are queued and pushed through after the freeze.09:46
RAOF?09:46
seb128RAOF, yes09:48
seb128RAOF, upload away things just get queued09:48
seb128and everything will be flushed after freeze09:48
RAOFCool.  Once I've finished polishing I'll upload.09:49
seb128thanks09:49
seb128re09:54
cassidykenvandine, you shouldn't enable the favorite feature, it requiers telepathy-logger which is not packaged yet09:55
seb128cassidy, oh btw what is the rational to display offline contacts by default?09:56
cassidyseb128, Cannonical's usability testing :)09:56
cassidyusers didn't find the option to display offline contacts and was expecting to have their full contact list09:57
seb128oh, interesting09:57
seb128see user testing is useful09:57
RAOFI can see how that would work, yeah.  Yay data!09:57
seb128I would never have though that's something user want :p09:57
cassidyand we assumed it's easier for user to think "How can I disable that?" than "Humm maybe there is an option to display online contacts"09:58
RAOFAny idea what the median number of contacts people have was?  That'd be a critical piece of info, I'd think.09:58
seb128hey chrisccoulson10:08
chrisccoulsonhey seb128, how are you?10:08
seb128good!10:08
seb128you?10:08
chrisccoulsonyeah, i'm good thanks, but quite tired10:08
pittihey chrisccoulson, how are you10:08
seb128had a late night again?10:09
chrisccoulsoni'm just doing some mass bug reporting now i can use apport again ;)10:09
chrisccoulsonhey pitti, yeah, i'm ok thanks10:09
chrisccoulsonseb128 - yeah, it was quite a late night last night, and i didn't rest much yesterday10:09
seb128chrisccoulson, :-(10:11
seb128chrisccoulson, you should call it a day early today, especially with the freeze there is no hurry to get changes10:11
seb128chrisccoulson, bug #412440, do you know if there was any design recommendation about what to do for this one?10:12
ubottuLaunchpad bug 412440 in gnome-disk-utility "gnome-disk-utility doesn't use new notifications" [Low,Confirmed] https://launchpad.net/bugs/41244010:12
chrisccoulsonyeah, i might do, although I got up quite late this morning already ;)10:12
seb128do you think we should just drop the action there?10:12
chrisccoulsoni'm not sure if anyone decided what we should do with that bug10:12
chrisccoulsonwe could drop the action for now, but i think there was a suggestion to use a more helpful dialog with a link to the manufacturers website10:13
seb128do we have those informations?10:13
seb128the manufacturer website10:13
seb128that seems a non trivial change with UI changes10:13
seb128I'm wondering if we should stop running the gdu things with the session in lucid10:14
chrisccoulsonwe could do, but i think the gdu-notifier process also displays the slow unmount dialog too10:16
chrisccoulson(the one which pops up when you unmount something in nautilus)10:16
seb128pitti, ^10:17
seb128any opinion on that?10:17
seb128in any case if we can't fix bug #438136 we should turn that notification off10:18
ubottuLaunchpad bug 438136 in libatasmart "palimpsest bad sectors false positive" [Unknown,Confirmed] https://launchpad.net/bugs/43813610:18
seb128we are freaking users about broken disks where disks are not broken10:18
pittiseb128: what do you mean with "new notifications"?10:18
pittiseb128: gdu shows the "low disk space" ones, the "please wait with removing USB device", "your RAID is broken", etc.10:19
pittiI think it's quite important to have10:19
seb128pitti, gdu is using actions right now10:19
pitti(also, "your hard drive is failing")10:19
seb128so we get those gtk fallback dialogs10:19
seb128instead of notification bubbles10:19
pittiweird, I see proper dialogs10:19
chrisccoulsonpitti - gsd shows the low disk space warning doesnt it?10:19
pittithey even have a checkbox10:19
pittichrisccoulson: yes10:19
chrisccoulson(unless we have 2 of those now)10:19
seb128pitti, for failing disks?10:19
pittiseb128: ah, so failing disks are notifications?10:19
seb128pitti, see bug #41244010:20
ubottuLaunchpad bug 412440 in gnome-disk-utility "gnome-disk-utility doesn't use new notifications" [Low,Confirmed] https://launchpad.net/bugs/41244010:20
pittiI'm fine with disabling actions for them10:20
seb128comment #1 has a screenshot10:20
seb128ok, that was minor point10:20
seb128but since we have dx contractors to work on those sort of issues10:20
pittiah, yes, those actions should be fixed10:20
seb128I will assign that to one of them10:20
chrisccoulsoni think that disabling actions is a good compromise at the moment, but we could probably think of something better for next cycle10:20
chrisccoulsonseb128 - i notice that someone is working on the gnome-screensaver "leave message" change now10:21
chrisccoulsonis that something we expect for lucid?10:21
seb128pitti, the one which really annoys me is the libatasmart one10:21
seb128chrisccoulson, I would consider it low priority, mpt pointed it as something nice to fix so I added to jpetersen tasks as lowest priority if he runs out of assigned tasks10:22
seb128chrisccoulson, he's one of the dx contractors10:22
seb128pitti, can you make sure the libatasmart issue is on the lucid radar?10:22
seb128pitti, or can we talk about disabling failing disk warnings if it's not fixed for lucid10:23
seb128pitti, telling people to change their disk when it's not broken is an issue10:23
pittiseb128: yes, we can disable the notifications as a last resort thing10:23
pittiI'll talk to it with mezcalero10:23
seb128thanks10:23
seb128the box my parents are using has the issue10:23
seb128quite annoying to explain them to ignore the dialog opening at every boot saying their disk is broken10:24
seb128"don't worry it's not broken, it's just a bug" ;-)10:24
pittiwhat does it say?10:24
seb128cf screenshot you just looked at before10:24
seb128"hard disk failing"10:25
pittiseb128: I mean, what does palimpsest say about the details/10:25
pitti?10:25
pittiI guess there are a few bad sectors, but not enough of them to start worrying?10:25
chrisccoulsonseb128 - i wouldn't mind being involved with any review of gnome-screensaver changes10:25
seb128chrisccoulson, ok, noted, thanks10:25
chrisccoulsonthanks10:26
seb128chrisccoulson, I will ping you if he comes with a patch for it10:26
seb128pitti, well, we had a look a few months back, all the win tools we found list 0 issues10:26
seb128no bad sectors10:26
seb128I'm pretty sure it's a bug in gdu or the libatasmart issue10:26
mvoout of curisotiry, how does redhat/fedora do global keyboard settings? is there a system-config-keyboard or somesuch?10:26
seb128mvo, no idea, ask mclasen when he's around10:27
pittiseb128: sudo skdump /dev/sda might be interesting10:27
pittiseb128: did you file a bug for it? these days apport includes a smart blob dump10:27
chrisccoulsonthe kernel team will love me by the end of the day10:27
pittiwhich upstream needs10:27
pittichrisccoulson: why, filed 5 bugs? :-)10:27
chrisccoulsonpitti - i think i might be able to report 5 ;)10:27
seb128pitti, no, but I can do that in half an hour if you want, against which package should I file it?10:28
pittiseb128: libatasmart10:28
pittiseb128: then I have a bug as a reminder, and good data; thanks10:29
seb128pitti, np10:29
seb128pitti, bug #438136 is not good enough?10:29
ubottuLaunchpad bug 438136 in libatasmart "palimpsest bad sectors false positive" [Unknown,Confirmed] https://launchpad.net/bugs/43813610:29
seb128pitti, it has over an hundred comments, responsive submitter and upstream bug reports10:29
pittiseb128: if that's what you are seeing, sure10:30
seb128pitti, anyway will file mine anyway you can dupif required10:30
pittiseb128: it has a million screenshots, but not a blob dump10:30
seb128right10:30
pittithese were reported in karmic mostly, where we didn't have the improved apport hook yet10:31
* pitti assigns the bug to himself for now, though10:31
seb128bug #454301 is weird10:33
ubottuLaunchpad bug 454301 in gnome-disk-utility "warning given about disk health due to smart not being enabled" [Low,Incomplete] https://launchpad.net/bugs/45430110:33
RAOFI haven't missed the team meeting reminder email, have I?10:37
chrisccoulsonRAOF, i haven't seen a reminder yet10:38
RAOFOk.  Well, I'll be up relatively early in the morning anyway.  Good night!10:39
chrisccoulsongood night RAOF!10:40
seb128'night RAOF10:41
seb128pitti, btw my .xsession-errors has this warning listed11:19
seb128" system-config-printer-applet: failed to start PrinterDriversInstaller service: org.freedesktop.DBus.Error.AccessDenied: Connection ":1.105" is not allowed to own the service "com.redhat.PrinterDriversInstaller" due to security policies in the configuration file"11:19
seb128do you know if that's a known issue?11:19
pittihm, I don't11:20
seb128pitti, bug #53021811:20
ubottuLaunchpad bug 530218 in system-config-printer "PrinterDriversInstaller service: AccessDenied error" [Undecided,New] https://launchpad.net/bugs/53021811:20
seb128pitti, should I milestone and assign to Till?11:20
pittiseb128: can you please assign it to Till?11:20
pittiyes, please :)11:20
seb128doing that, thanks11:20
seb128pedro_, hey11:34
pittiI'm off IRC for some hour for test-reinstalling my main laptop11:35
seb128pedro_, can you test if gedit remember the cursor position in a document for you?11:35
seb128ie open a text, move cursor, close and reopen gedit and see if it set the cursor where it was11:35
seb128pitti, have fun11:35
* seb128 lunch11:35
pedro_seb128, yeap one sec11:35
seb128pedro_, if it's broken for you can you open a bug on bugzilla? pbor said he would look at it11:35
seb128pedro_, no hurry I'm just going for lunch11:36
seb128bbl11:36
seb128pedro_, thanks11:36
pedro_seb128, enjoy!11:36
seb128thanks11:36
=== MacSlow is now known as MacSlow|lunch
pedro_seb128, fyi https://bugzilla.gnome.org/show_bug.cgi?id=61303211:59
ubottuGnome bug 613032 in general "Cursor position is not remembered" [Normal,Unconfirmed]11:59
seb128pedro_, thanks!11:59
pedro_my pleasure ;-)11:59
nigelbthoughts on this fix? worth getting into lucid? bug 52974412:00
ubottuLaunchpad bug 529744 in gnome-system-tools "When creating a new user, "Shortname" should really be "Username" ." [Low,Triaged] https://launchpad.net/bugs/52974412:00
chrisccoulsonnigelb, i don't think that justifies a UI freeze exception really12:02
nigelbmy thoughts too, I just wanted the desktop team's take on it12:03
nigelbchrisccoulson: can you unsubscribe sponsors and mention that there?12:04
kenvandinecassidy, cool, thx!12:14
seb128kenvandine, hey12:34
=== KenEdwards is now known as KenEdwards-afk
davmor2anyone working on une?12:45
kenvandinehey seb12812:45
seb128kenvandine, how are you?12:46
kenvandinegood, and you?12:46
seb128good, thanks!12:46
seb128kenvandine, was there anything decided about how to handle empathy calls requests?12:47
chrisccoulsonhmmm, is wiki.ubuntu.com working for anyone?12:47
seb128kenvandine, I know that we discussed that having those in the indicator was not obvious enough12:47
kenvandinejust forcing raising the incoming call window12:47
seb128kenvandine, do you plan to work on that? or should I add it to the contractors list?12:47
kenvandineseb128, i want it to just raise that incoming call dialog instead of a notification12:48
seb128chrisccoulson, seems not, or it's really slow12:48
kenvandineseb128, was going to do that next cycle12:48
chrisccoulsonseb128 - ah, so it's not just me then12:48
chrisccoulsoni hope it hasn't discarded my work ;)12:48
seb128kenvandine, "next cycle" = lucid+1?12:48
seb128chrisccoulson, oh, you mean it's because of you? ;-) doing too many changes there and loading the wiki with those? ;-)12:49
kenvandineseb128,  i would love to do it now12:49
kenvandineseb128, could we squeeze that in?12:49
seb128kenvandine, ok, so you want to take over the bug or should I assign it to a contractor?12:49
chrisccoulsonseb128 - yeah, i keep updating the wiki at the moment ;)12:49
kenvandinei think i have the time12:49
seb128kenvandine, not for beta1 but after beta1 one12:49
seb128one -> yes12:49
kenvandineawesome12:50
kenvandinei'll do it12:50
seb128kenvandine, thanks12:50
kenvandinegot the bug # handy?12:50
kenvandinecassidy, what is the best way to know an event is an incoming call?12:50
seb128kenvandine, bug #44086512:50
ubottuLaunchpad bug 440865 in empathy "Visual notification for/correct user response to incoming voice calls and subscription requests not obvious" [Low,Triaged] https://launchpad.net/bugs/44086512:50
cassidykenvandine, an EmpathyEvent ?12:51
kenvandineyeah12:51
kenvandinesame for subscription request12:51
kenvandinealthough i don't think that should be a dialog, so should run that by mpt12:51
cassidycheck the type attribute of the evnet12:51
cassidy    EmpathyEventType type;12:52
kenvandinecassidy, great12:53
kenvandinethx12:53
chrisccoulsongrrrr, it lost my changes12:53
seb128chrisccoulson, if you try to edit again it might take the draft back12:53
seb128it does it there usually12:54
seb128or ask at least if you want to use that one12:54
chrisccoulsonhmmm, it's not doing that here :-/12:54
seb128:-(12:54
seb128you should take the pitti way12:54
chrisccoulsonoh, hand on12:54
chrisccoulson"Load draft"12:55
chrisccoulsonthat brings back most of the changes ;)12:55
chrisccoulsonthat's ok then :)12:55
seb128use the editmoin to do edition locally in your favorite editor12:55
chrisccoulsonyeah, i might try that12:55
chrisccoulsonsometimes editing it online is so slow ;)12:55
=== MacSlow|lunch is now known as MacSlow
=== KenEdwards-afk is now known as KenEdwards
baptistemmHi there13:12
baptistemmpitti, is bug 529554 in your radar ?13:12
ubottuLaunchpad bug 529554 in apport "[8.04 -> 10.04 a3] Configuration prompt request" [Undecided,Confirmed] https://launchpad.net/bugs/52955413:12
chrisccoulsonseb128 - do you think bug 390816 is worth fixing for lucid?13:20
ubottuLaunchpad bug 390816 in gnome-power-manager "external monitor output is switched off when closing the laptop-lid when gnome-power-manager is set to blank screen on closing" [Medium,Triaged] https://launchpad.net/bugs/39081613:20
seb128yes!13:21
chrisccoulsonwould you mind adding a lucid task for that one then?13:21
chrisccoulson:)13:21
seb128will do13:21
chrisccoulsonthanks13:21
seb128I also need to check if I still get g-s-d crashing when suspending docked and waking up undocked13:21
seb128btw do you have any idea what source would be to blame for "no screen active" in such cases?13:22
seb128I need to enter my password without screen13:22
seb128and do fn-f713:22
seb128that's quite annoying too13:22
chrisccoulsoni'm not too sure about that one13:22
chrisccoulsonthat's probably another g-s-d issue ;)13:22
seb128I'm not sure if that's not xorg itsefl13:22
seb128it should make sure at least one output is active13:23
seb128tjaalton, bryceh: ^13:23
seb128opinions?13:23
seb128typical scenario is "use a laptop docked with lid closed, only the external screen is active, suspend, take the laptop, open it somewhere"13:24
seb128which leads to "no screen active"13:24
chrisccoulsonseb128 - that could be a xorg issue if g-s-d got no signal that the display configuration changed13:25
chrisccoulsonit should respond when the display configuration changes, and configure them appropriately13:25
chrisccoulsonthis is where xtrace helps :)13:26
seb128hehe13:26
seb128you recommend running g-s-d under xtrace?13:26
seb128I never used xtrace, I need to look at it13:26
chrisccoulsonit's probably a quick test, just to see if you get a RRScreenChangeNotify event when you resume the machine13:27
chrisccoulsonif not, then g-s-d has no way of knowing that the display configuration changed13:27
seb128how do I know about this? using xtrace?13:29
tjaaltonseb128: I'd say the driver13:29
seb128tjaalton, ok, I'm on intel96513:30
seb128tjaalton, do you know if that's a known issue for those?13:30
tjaaltonseb128: dunno, I could try with mine :)13:30
seb128tjaalton, would be nice ;-)13:30
seb128tseliot, do you think you could have a look to bug #432814?13:35
ubottuLaunchpad bug 432814 in xserver-xorg-input-synaptics "Action for middle and right click is reversed since jaunty" [Undecided,Invalid] https://launchpad.net/bugs/43281413:35
seb128tseliot, just to see if there is really an issue there or something we should look at changing13:35
tseliotseb128: sure13:35
seb128tseliot, it seems it annoy some users but I'm not sure to understand our options and if changing the config the way suggested would break other usecases13:35
tseliotseb128: I think we can only choose which users we want to annoy ;)13:36
seb128tseliot, ok, maybe you could drop a quick comment on the bug saying that?13:38
tjaaltonseb128: how do you keep the external alive with lid closed?13:38
seb128tjaalton, I boot docked and it just do it13:39
tjaaltonseb128: ah ok13:39
seb128tjaalton, otherwise plug the screen and use the capplet to activate external and desactive the laptop13:39
seb128or use fn-f7 to do that13:40
seb128and close the lid13:40
seb128with something else than suspend on lid close ;-)13:40
tseliotseb128: the attached patch is not such a bad idea and I think mpt approved something like that for karmic (but I didn't have the time to review it)13:40
seb128tseliot, can you maybe assign the bug to yourself then, it's low priority milestoned for lucid13:41
seb128tseliot, so it stays on your target of opportunity list13:41
seb128?13:41
tseliotseb128: yes, sure. BTW is there also a bug report about the disable touchpad thing?13:42
seb128tseliot, bug #47987813:42
ubottuLaunchpad bug 479878 in gnome-settings-daemon "Need an option to disable touchpad completely" [Wishlist,New] https://launchpad.net/bugs/47987813:42
tseliotseb128: ok, good13:44
seb128tseliot, thanks13:44
seb128slomo, hey13:44
slomohi seb12813:45
seb128chrisccoulson, bug #509478, do you still want to work on it for lucid or should I move it to the team list rather?13:47
ubottuLaunchpad bug 509478 in gnome-settings-daemon "gnome-settings-daemon crashed with signal 5 in xkl_process_error()" [High,Triaged] https://launchpad.net/bugs/50947813:47
seb128chrisccoulson, realistically you have lot of things to do already so you might want to try to give some bugs back to the team and claim those again later if time allows rather than overworking you for those13:48
tjaaltonseb128: well, I can't undock it while it's asleep13:51
seb128tjaalton, why not?13:51
pittibaptistemm: I bet it's the 2305324th duplicate of the update-manager bug, but I'll check13:51
tjaaltonthere's a button for the undock, and pressing it wakes the machine up13:51
seb128tjaalton, just undock without telling the dock :p13:51
tjaaltonseb128: it'll start whining loudly :)13:51
tjaaltonactually no, it wakes up13:53
seb128tjaalton, well that's good in any case13:53
seb128open the lid and see if you have a screen on :p13:53
mvopitti: what bug?13:53
pittimvo: bug 5180413:53
ubottuLaunchpad bug 51804 in launchpad-registry ""Change Maintainer" link on product overview page is misnamed (dup-of: 202135)" [Low,Triaged] https://launchpad.net/bugs/5180413:53
ubottuLaunchpad bug 202135 in launchpad-registry "Change project maintainer page also uses owner and registrant" [Medium,Fix released] https://launchpad.net/bugs/20213513:53
tjaaltonseb128: well it isn't13:54
pittimvo: argh, sorry; bug 51804313:54
ubottuLaunchpad bug 518043 in update-manager "Modifies /etc/default/apport during upgrade, causing conffile prompt" [High,Triaged] https://launchpad.net/bugs/51804313:54
tjaaltonseb128: so something is not waking it up, a vt-change does though13:54
tjaaltonseb128: could be g-s-d after all13:54
tjaaltonor is it g-p-m13:55
seb128tjaalton, "not waking it"? waking who there?13:55
seb128tjaalton, shouldn't xorg activate the screen on resume?13:55
chrisccoulsonseb128 - i still intend to look at that bug13:55
chrisccoulsonit's fairly reproducible here as well :)13:56
tjaaltonseb128: I'm not sure how it goes13:56
tjaaltonor should go13:56
seb128tjaalton, I will try checking with federico13:58
seb128I guess he should know, he works on a lot around those sort of scenarios13:58
tjaaltonyep13:59
tjaaltonthanks13:59
seb128thank you13:59
chrisccoulsonwe're still having a team meeting this afternoon aren't we?14:20
kenvandinechrisccoulson, afaik14:21
chrisccoulsoni haven't seen a reminder, and there's nothing at https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-03-1614:21
seb128chrisccoulson, yeah, I guess rickspencer3 has been busy, reminders come late sometime14:24
rickspencer3d'oh14:24
seb128hey rickspencer314:25
rickspencer3chrisccoulson, I just forget a lot14:25
rickspencer3hi seb12814:25
* rickspencer3 goes to remind14:25
rickspencer3thanks chrisccoulson14:25
chrisccoulsonhi rickspencer3, no worries :)14:25
pittihey rickspencer314:25
rickspencer3stupid daylight savings14:25
rickspencer3it's says 7:25am, but I am sooo tired14:25
seb128I would be tired too if I was waking up at 6am14:26
chrisccoulsonrickspencer3, yeah, i hate DST too. i prefer it when the clocks go back in the other direction ;)14:26
pittiI created the wiki page now14:28
pittihttps://wiki.ubuntu.com/DesktopTeam/Meeting/2010-03-1614:28
rickspencer3pitti, so did I14:28
pittioops14:28
kenvandinejames_w, ping14:28
rickspencer3pitti, it worked!14:28
pittiI didn't exist yet 2 minutes ago14:28
pittirickspencer3: did I overwrite any contents of your's?14:28
rickspencer3pitti, I know, when I created it, it didn't throw an error or blow away your changes14:29
rickspencer3nice14:29
rickspencer3pitti, nope, it worked in quite a pleasant manner14:29
rickspencer3so team meeting is in 2 hours, right?14:29
seb128dpm, hi14:29
james_whi kenvandine14:30
seb128dpm, the indicator-session translation issue, it's likely due to ted's merge from oem translation upstream14:30
kenvandinejames_w, how should we handle things like this14:30
kenvandinehttps://code.edge.launchpad.net/~facundo/ubuntu/lucid/pyinotify/fix-path-overlap/+merge/2126614:30
seb128rickspencer3, yes14:30
rickspencer3thanks seb12814:30
kenvandineshould we merge right into lp:ubuntu/pyinotify and upload?14:30
james_wkenvandine: yep, bzr merge; bzr commit; bzr bd -S; bzr mark-uploaded; bzr push lp:ubuntu/pyinotify; dput14:31
kenvandineok... only problem is i won't have commit access or upload perms for that package :)14:31
dpmhey seb128, oh I see... I didn't know there where upstream OEM translations for indicator-session. I knew there might be from other projects, but not for i-s. I'll talk to him, then. Thanks for the heads up14:31
seb128dpm, np14:32
kenvandineso i'll need to get a sponsor, but good to know14:32
kenvandinejames_w, thx14:32
james_wkenvandine: oh, in that case, I can do it14:32
kenvandinethx :)14:32
seb128dpm, tedg: any reason why indicator-session upstream translations are not open in launchpad?14:32
seb128dpm, tedg: or any reason to not merge translations back from ubuntu if those are considered upstream ones?14:33
james_wkenvandine: the only thing I was unsure of was whether this should be uploaded today or Friday?14:33
kenvandinefriday14:33
kenvandinebeta214:33
tedgseb128: Because the only way to merge them back currently is with a tarball dump, which really isn't a "merge"14:33
james_wkenvandine: ok, I'll go back to ignoring it :-)14:33
seb128kenvandine, can you review bug #405284?14:33
ubottuLaunchpad bug 405284 in empathy "improve empathy notifications support with notify-osd" [Wishlist,New] https://launchpad.net/bugs/40528414:34
kenvandineseb128, sure14:34
seb128kenvandine, or rather the patch there14:34
seb128kenvandine, it's not trivial and probably not good to use but since the submitter went through the work of posting it etc would be nice to comment14:34
seb128tedg, how did you "merge" from oem?14:34
dpmseb128, tedg, I think it's fine if the upstream project is not open for translations for now, so we only have a source for translation, but if we are to merge them, translations from Ubuntu translators should be given precedence . This can be done e.g with msgmerge14:35
tedgI'm hoping that KyleN and dpm are going to come up with a stellar plan. :)14:35
kenvandinejames_w, i'll assign the package bug to you then14:35
seb128james_w, kenvandine: just upload your fixes, don't wait for friday, those will be queued14:35
tedgseb128: We didn't have any upstream translations previously, so there was no merge.14:35
kenvandinejames_w, are you the "ubuntu-branches" team?14:35
dpmtedg, we've started (well kyleN has) some documentation for this. merges can be done with the gettext tools14:35
seb128tedg, well you added the oem ones, you could have done the same with the ubuntu ones from an export tarball14:35
tedgdpm: I agree, I'm not sure if that is useful or more of a problem at this point.14:36
kenvandineseb128, should i go ahead and upload that rb patch too then?14:36
kenvandinejust so it doesn't get forgotten :)14:36
tedgseb128: Yes, but I didn't realize what trouble that'd cause when I did it the first time :)14:36
seb128kenvandine, no, I've 2 other changes to batch there so no need to queue 2 uploads14:36
kenvandineok14:36
* kenvandine forgets about rb then14:36
seb128tedg, ok ;-) I will let dpm sort that14:36
seb128dpm, you can talk to oem and translators about the issue?14:36
james_wkenvandine: I am14:38
kenvandinejames_w, hehe :)14:38
dpmseb128, sure, I'll be talking to kyleN this week anyway. tedg, I don't think there is anything we can do now, but next time the preferred way is either to export a tarball with the translations from the Ubuntu source packages and give them preference with msgmerge. I'll follow this up in an e-mail14:39
tedgdpm: Cool, thanks.14:39
dpmno worries14:39
seb128dpm, tedg: thanks14:40
nigelbkenvandine: got a couple of minutes?14:45
kenvandinenigelb, sure14:48
kenvandinenigelb, what's up?14:48
nigelbI'm working on getting the gwibber package to debian, so if I run into troubles can you help out (when you get the time)14:49
kenvandinesure14:49
kenvandineawesome!14:49
nigelbI spoke to the current maintainers, they currently have an issue with it not running14:50
kenvandinewhat version do they have?14:53
kenvandinenigelb, well let me know if you run into issues, i'll be happy to help14:53
nigelbkenvandine: they have an old bzr package14:54
nigelbkenvandine: debian has gwibber (1.2.0+bzr358-2) I'm trying to get the lastest package in.  Lemme see how it goes.  I'll keep you posted15:01
chrisccoulsonhmmm, wiki.ubuntu.com is timing out again :-/15:06
seb128pitti, see bug #53963615:09
ubottuLaunchpad bug 539636 in libatasmart "gdu wrongly reports bad disk sectors" [Undecided,New] https://launchpad.net/bugs/53963615:09
seb128pitti, I guess it doesn't have the infos you want though15:09
seb128pitti, can you tell me what those are?15:09
seb128pitti, "DevkitDisksDump: Error: [Errno 2] No such file or directory"15:10
seb128pitti, bah, /usr/share/apport/package-hooks/libatasmart4.py15:11
seb128devkit-disks -> udisks15:11
seb128pitti, is that just a udisks --dump log that you need?15:11
fagankenvandine: I cant make a apport bug but gwibber is cashing with attributeerror in exclude_databases()15:14
faganI havent been able to use it for a week now :/15:15
kenvandinefagan, ah... that is the same as jcastro got15:15
kenvandineplease file a bug :)15:15
kenvandineor if you did.. point me at it please15:15
faganCant apport is broken :/15:15
faganHmmm is there any way to dump the apport info into a text file so I can report it manually?15:16
faganpitti: ^15:17
faganOh its working now15:17
seb128fagan, you can apport-unpack the .crash15:17
seb128and copy the files you want15:18
kenvandinefagan, or just attach the log file15:18
kenvandine~/.cache/gwibber/gwibber.log15:18
faganapport is working now :) Ill point you to the report15:18
kenvandinethx!15:18
kenvandinefagan, it's a situation that the u1 guys say shouldn't be possible15:18
kenvandineif it is the issue i am thinking of15:18
kenvandineso i guess we need to handle it better in gwibber, and have the u1 guys fix it on their end too15:19
fagankenvandine: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/53964115:20
ubottuLaunchpad bug 539641 in gwibber "gwibber-service crashed with AttributeError in exclude_databases()" [Undecided,New]15:20
kenvandinethx15:20
kenvandineyup15:20
kenvandinefagan, you use u1?15:20
fagankenvandine: yep15:20
kenvandinefagan, you are paired with ubuntuone, but you have no pairing record in the db15:20
kenvandinewhich they claim isn't possible15:21
kenvandine:)15:21
kenvandinewe thought jcastro was a corner case because of some of the really early testing he did15:21
faganbah it is then we have proof15:21
kenvandineand i guess the same could be true for you :)15:21
kenvandinebut still... :)15:21
kenvandinefagan, thx for the bug report15:21
faganSo its just a corner case then for people who have been using lucid since the early alphas15:22
kenvandinemore likely karmic15:22
jcastroI am doomed. I even blew away all my U1 stuff and reauthed my PC15:22
kenvandinedid you use u1 on karmic?15:22
kenvandineand like in the beta period?15:22
kenvandinejcastro, is that what they told you to do?15:22
jcastrono, it's my usual trying to fix u1 workflow15:23
jcastroI even have a script15:23
kenvandinehahaha15:23
kenvandinejcastro, that is sad dude15:23
jcastroit's like killev all over again15:23
kenvandinejcastro, can you "me too" that bug?15:24
jcastrodone, and subbed15:24
kenvandinethx15:25
tedgpitti: Can you update the status of this branch please (house keeping branches)?  https://code.launchpad.net/~pitti/indicator-session/libupower-glib15:53
pittiseb128_: argh, I'll fix the libatasmart apport hook, sorry about that; yes, it's udisks --dump16:03
pittifagan: apport-bug --save /tmp/report.apport packagename; and then apport-bug /tmp/report.apport on a different computer (or later on)16:03
pittitedg: yes, can do16:03
pittiseb128_: ah, it doesn't have the disk blob either, presumably because it's also querying it from dk-disks16:04
seb128_pitti, I still have the box on, what do you need?16:05
seb128_pitti, I added the udisks log16:05
=== seb128_ is now known as seb128
tedgpitti: Thanks!16:05
pittiseb128: install libatasmart-bin and do sudo skdump --save=/tmp/smart.blob /dev/sda16:06
pittiseb128: and attach /tmp/smart.blob to the bug16:06
seb128pitti, ok16:06
pittitedg: oh, great! you implemented it using async dbus calls now?16:08
tedgpitti: Yeah, merged that in this morning.16:10
tedgpitti: Trying to close out indicator-session issues :)16:10
pittitedg: thanks!16:10
seb128tedg, nice to see you fixed the session locking one too ;-)16:14
pittiseb128: I committed the apport hook fix to debian git and uploaded a new libatasmart; thanks and sorry for the trouble16:14
seb128pitti, np, thank you for fixing it!16:14
mvojames_w: I owe you a beer for your fix for #455861 (at least one!)16:18
mvojames_w: thanks!16:19
james_wyou've tested it?16:19
rickspencer3Riddell, can we discuss figuring out how to solve bug #538524 for beta in the desktop team meeting?16:22
ubottuLaunchpad bug 538524 in plymouth "boot hangs on splash screen, doesn't switch to KDM" [Medium,Confirmed] https://launchpad.net/bugs/53852416:22
seb128pitti, smart blob added to the bug16:22
pittiseb128: cheers16:22
Riddellrickspencer3: it's top of my list of important issues, I've no idea where to start in solving it16:22
seb128pitti, I added the hdc one since that's the drive which is shown as having issues16:23
pittiseb128: "hdc"?16:23
rickspencer3thanks Riddell16:23
rickspencer3maybe we can get some help on it at the team meeting16:23
seb128pitti, /dev/hdc16:23
seb128pitti, you said "sudo skdump --save=/tmp/smart.blob /dev/sda"16:23
seb128pitti, I changed to /dev/hdc, that's correct right?16:24
pittiseb128: ah, the udisks dump has sdc; I take it you mean that one16:24
pitti      overall assessment:      Disk reports many bad sectors16:24
pittiseems so16:24
seb128pitti, ok good16:24
seb128pitti, anyway else before I take my usb stick back to reinstall the mini with it?16:24
pittiseb128: looks complete now16:25
seb128anyway -> anything16:25
seb128pitti, ok good, thank you!16:25
rickspencer3desktop team meeting in 1 minute, right?16:29
ccheneyyea16:29
chrisccoulsoncool, i've just got to reboot quickly ;)16:29
tseliotyep16:31
rickspencer3ArneGoetje, bryceh, ccheney, chrisccoulson, didrocks, kenvandine, Nafai, pitti, RAOF, Riddell, seb128, tkamppeter, tseliot16:31
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-03-1616:31
pittio/16:31
ArneGoetjeo/16:31
* kenvandine waves16:31
seb128hey16:31
ccheneyhere16:31
Riddellhi16:31
* rickspencer3 tops gavel16:31
tselioto/16:31
chrisccoulsonhere16:31
Nafaiuh oh, I'm included now16:31
rickspencer3let's get going ...16:32
rickspencer3hi Nafai, yeah, you can just follow along16:32
rickspencer3no action for you, just fyi16:32
Nafai:)\16:32
rickspencer3anyway ...16:32
rickspencer3before we start ...16:32
rickspencer3I want to say ...16:32
rickspencer3Lucid is totally rocking!16:32
rickspencer3I used Karmic on my kid's computer yesterday, and I was shocked by the progress that we've made in Lucid16:33
pitti♪ weee willl weeeee will ... ♫16:33
rickspencer3I think we will look back on this release a special time16:33
* kenvandine sings along16:33
* rickspencer3 claps hands a bit out off time16:33
tseliot:-)16:33
rickspencer3ok16:33
rickspencer3so ...16:33
rickspencer3let's get to work16:33
rickspencer3first, outstanding actions from last week16:33
rickspencer3which I just realized I completely forgot to prepare :/16:34
* rickspencer3 chastises self16:34
rickspencer3moving on ...16:34
rickspencer3kenvandine, partner update16:34
kenvandineok16:34
kenvandineOLS will have some freeze exceptions16:34
kenvandinewell, bugs already filed and linked on the wiki page16:34
kenvandinenothing major afaict16:35
kenvandinethey are still having server side download issues with the music store16:35
rickspencer3:(16:35
kenvandinehopefully that will get fixed soon...16:35
kenvandine:(16:35
kenvandineit works as long as they restart it often16:35
rickspencer3kenvandine, do we have any kind of strategy for dealing with the (low) possibility that downloads won't be ready in time?16:35
kenvandinei think the current strategy is regular service restarts16:36
kenvandinewhich sucks... but downloads don't get lost16:36
tkamppeterhi16:36
kenvandineon to DX16:36
kenvandinethey will have an update to indicator-me this week that will only display the status update entry if the gwibber service is running16:37
kenvandineso no string changes and overall a very welcome changes16:37
kenvandinei see no issues with that16:37
rickspencer3great!16:37
kenvandineand some regular bug fixes, which i think most of which seb128 has already patched16:37
rickspencer3this is what I envisioned the "stabilization and completion" milestone to be fore16:37
seb128I did but they fixed an another round of issues since ;-)16:38
kenvandine:)16:38
kenvandinethat is all for the partner update16:38
rickspencer3having bug fixes come in too fast to keep up with is a problem I like to have16:38
seb128rocking dxteam work this cycle, everybody hugs tedg and bratsche and the others16:38
kenvandineyup16:38
kenvandinebig high five to the DX team!16:38
seb128or pay them a beer at uds ;-)16:38
rickspencer3kenvandine, wrt Dx mostly, but also OLS, does this cycle seem somewhat more organized?16:38
kenvandinehehe16:38
* pitti hugs tedg, bratsche, and davidbarth16:38
kenvandinerickspencer3, yes16:39
rickspencer3ok, never mind, what seb128 says :)16:39
rickspencer3rock!16:39
kenvandinerickspencer3, also16:39
pittiI think we learned from last cycle, on both ends16:39
rickspencer3indicator area = HUGE improvement for users16:39
tedgseb128: pitti Thanks guys.16:39
* davidbarth reads up the log; feels good anyway ;)16:39
rickspencer3ok16:39
kenvandinewe plan to get weekly releases going for OLS next cycle16:39
kenvandineso that will be great16:39
rickspencer3kenvandine, great16:39
rickspencer3thanks again to Dx for making Ubuntu great16:39
rickspencer3moving back a bit ..16:40
tseliot+116:40
rickspencer3outstanding items from last meeting:16:40
rickspencer3ACTION: rickspencer3 to ask bdmurray about included targetedness of bugs in bug query16:40
rickspencer3ACTION: rickspencer3 to follow up with sabdfl to confirm that boot time cursor requirement is met16:40
rickspencer3ACTION: seb128 to generate a list of 100 "right" bugs to fix in Lucid16:40
rickspencer3ACTION: rickspencer3 and seb128 to discuss gdm greeter options, especially wrt sound16:40
rickspencer3so all are done, except the sabdfl thing16:40
kenvandinepitivi testing too16:40
kenvandineright?16:40
rickspencer3and he's on holiday, so I'll push that16:40
rickspencer3kenvandine, good point, that fell off the list :(16:40
seb128I didn't do "100" but didn't want to add not matching bugs to get the number16:40
rickspencer3seb128, but you started, right?16:40
seb128some bugs got dispatched to people on the way too16:40
* kenvandine imported some DV clips from the camera and rendered a project16:41
kenvandineworked well16:41
pittiwell, also we already assigned some bugs to individual people16:41
rickspencer3let's not call it "100 bugs"16:41
pittihttps://bugs.edge.launchpad.net/~canonical-desktop-team/+assignedbugs16:41
rickspencer3let's call it "top bugs"?16:41
seb128rickspencer3, yes, we have a good list and dispatched some already16:41
pittiI'll get to that later on16:41
rickspencer3thanks pitti16:41
pittiwe have a good amount of fodder now16:41
rickspencer3ACTION: rickspencer3 to ask bdmurray about included targetedness of bugs in bug query16:41
rickspencer3ACTION: rickspencer3 to follow up with sabdfl to confirm that boot time cursor requirement is met16:41
rickspencer3ACTION: seb128 to generate a list of 100 "right" bugs to fix in Lucid16:41
rickspencer3ACTION: rickspencer3 and seb128 to discuss gdm greeter options, especially wrt sound16:41
seb128I wish we had a way to list all milestoned bugs for members of a team on launchpad16:41
rickspencer3d'oh16:41
rickspencer3seb128, gdm greeter?16:41
seb128rickspencer3, the gdmsetup sound option change is in bzr16:42
rickspencer3great!16:42
seb128thanks to robert_ancell and didrocks mainly16:42
rickspencer3so we'll need a UI freeze exception for that16:42
pittiyohoo16:42
rickspencer3ah, so that's what didrocks was pushing on16:42
pittiseb128: so the "call gconftool from server" worked out in the end?16:42
seb128right, I will take care of that after beta116:42
* pitti hugs seb12816:42
rickspencer3(btw, didrocks is rocking a Ubuntu conference this week, so he'll be offline mostly)16:42
seb128pitti, yes, still an issue I need to talk with you about though16:42
seb128but after meeting16:43
rickspencer3ok16:43
seb128didrocks worked on that yesterday but the uid change is not working as he want16:43
seb128I said I would check with you16:43
pittiseb128: I bet it's effective vs. real uid16:43
pittiyes, after meeting16:43
rickspencer3seb128, maybe we could hand that off16:43
rickspencer3I think didrocks has enough on his plate ;)16:43
rickspencer3so moving on16:43
seb128rickspencer3, we did16:43
rickspencer3kenvandine mentions pittivi testing16:44
seb128rickspencer3, I said I would take over for the remaining part yesterday16:44
rickspencer3(thanks seb128, I should have guessed ;) )16:44
seb128-> pitivi16:44
seb128the new version is in lucid16:44
rickspencer3pitivi16:44
rickspencer3whatever16:44
rickspencer3video editing16:44
seb128please do test and file bugs16:44
seb128bonus point if you file them on bugzilla too ;-)16:44
rickspencer3seb128, I saw lots of "Fix Release" and not too many "New"16:44
seb128right16:44
rickspencer3so I am taking this to be a good sign16:44
seb128I'm not sure how much people played with the new version though16:44
seb128would be nice to have everybody trying it again16:45
rickspencer3ok16:45
kenvandinei just wish it could import from my DV camera, i hate having to re-learn dvgrab everytime :)16:45
seb128and filing bugs with apport if it crashes16:45
rickspencer3my gut tells me the pitivi team is quite close16:45
kenvandinebut i hit no bugs creating a short 10m video out of about 5 clips16:45
rickspencer3kenvandine, pitivi is python, I'm sure they'll take a merge proposal from you16:45
rickspencer3;) j/k16:45
kenvandinehehe16:45
kenvandineif i hit bugs :)16:45
kenvandineit worked perfectly!16:45
kenvandinewhich was nice16:45
kenvandinebut always worked well for me with DV files :)16:46
rickspencer3I mean for the DV camera import16:46
kenvandineoh that16:46
kenvandineewww16:46
kenvandinesounds hard to me :)16:46
rickspencer3it worked for me with a screen capture from gtk-record-my-desktop16:46
kenvandinecool16:46
rickspencer3and when I say "worked" I mean totally without issue16:46
rickspencer3I tried to make problems and couldn't16:46
rickspencer3ok, let's move on to Kubuntu, because I know Riddell has a rather serious issue to address16:47
kenvandinemy wife saw me testing and now adding a task to my "Honey Do" list :)16:47
kenvandineshe wants more video on DVD16:47
Riddell * Beta is blocked by this bug https://launchpad.net/bugs/538524 "boot hangs on splash screen, doesn't switch to KDM"16:47
rickspencer3and I am hoping that we can rally and help out the Kubuntu team on this one16:47
ubottuLaunchpad bug 538524 in plymouth "boot hangs on splash screen, doesn't switch to KDM" [Medium,Confirmed]16:47
Riddell   It apparantly requires a chunk of C to be written and tested.  Unsure how to move forward, I don't even know a workaround for beta.16:47
Riddell * several SRUs are blocked in karmic-proposed unapproved queue16:47
Riddell * Still waiting on new logo from design team, no word from them and Iain doesn't seem to be on IRC16:47
rickspencer3Riddell, design team is at training atm16:47
kenvandinei think done today16:48
Riddellhmm, maybe they shouldn't give me deadlines that fall on their training days16:48
rickspencer3Riddell, I just asked oubiwann to help us get this resolved16:49
tseliotah, is this for the plymouth theme?16:49
rickspencer3Riddell, the plymouth thing seems a lot more serious though16:49
rickspencer3Riddell, would you rather focus on a work around, or focus on a fix for beta?16:49
rickspencer3(any why is it a Medium if it's blocking beta?)16:50
seb128timing seems to be really right to get a fix for beta now16:50
seb128*tight*16:50
pittiwe have a quite similar problem with gdm16:50
Riddellrickspencer3: I don't see it getting fixed in time for beta unless keybuk decides to do it toot sweet16:50
seb128workaround: don't install plymouth on kubuntu?16:51
pittiKeybuk now knows what's wrong and is working on a solution16:51
pittiRiddell: alt+f7 doesn't help?:16:51
rickspencer3pitti, is he targetting that for beta? is it feasible to pull Plymouth from Kubuntu until it's fixed?16:51
Riddellpitti: no alt+f7 doesn't help16:51
pittihm, then it's something else16:52
Riddellpitti: he is?  would be nice if he told me about it (well, would be nice if he's told me this was needed three months ago)16:52
Keybukpitti: what's wrong is Riddell didn't do the work item he marked as DONE16:52
pittirickspencer3: hm, I guess we could pull it somehow16:52
rickspencer3hold it16:52
rickspencer3let's not go down that path16:52
rickspencer3the past is of no use to us now16:52
pittiRiddell: I assumed it was the "doesn't switch to vt7 automatically" problem, which we discussed yesterday16:52
rickspencer3Keybuk, do you think we can pull Plymouth until this is fixed?16:53
pittibut apparently not16:53
Keybukrickspencer3: we can't pull plymouth from a seed - mountall depends on it16:53
rickspencer3can we tell kubuntu not to use it?16:53
rickspencer3just hack in a work around that let's it boot for now?16:53
Keybuknot that I know of16:53
rickspencer3so we have no choice but to fix it16:53
rickspencer3who has the knowledge to address this?16:54
rickspencer3Keybuk, tseliot, pitti?16:54
rickspencer3anyone else?16:54
rickspencer3chrisccoulson ?16:54
Keybukkdm is written in C++ in Qt16:54
Riddellneeds someone who knows C and how to debug VTs and whatnot16:54
rickspencer3seb128, ?16:54
RiddellKeybuk: the backend is C16:54
* tseliot doesn't know what the problem is16:54
chrisccoulsonme neither ;)16:54
* tseliot reads the bug report16:54
pittirickspencer3: one rather drastic way would be to drop the mountall dependency and seed it on ubuntu for now16:54
chrisccoulsoni could probably help out it if it was gdm16:54
seb128rickspencer3, I don't16:55
Riddelltseliot: KDM's backend needs to talk to plymouth before and after starting X (I think)16:55
Keybukpitti: err, but then you wouldn't have any filesystems on boot <g>16:55
Keybukpitti: and wouldn't have any services running, from dbus all the way past kdm :p16:55
rickspencer3Keybuk, is the implementation strategy known, but just needs someone to do the programming?16:55
pittiKeybuk: hm, did that change recently? I didn't have plymouth installed until some days ago16:55
Keybukrickspencer3: yup, SMOP16:55
pittiKeybuk: mountall depends libplymouth2 only, AFAICS?16:55
rickspencer3SMOP?16:55
Keybukpitti: oh, right16:56
Keybukrickspencer3: Simple Matter of Programming16:56
rickspencer3sill manager off point questions?16:56
pittiAFAICS it's just an ubuntu-standard recommends16:56
Riddellrickspencer3: Keybuk gave me the psudocode of what needs done, needs it turned into C and put into the right places in KDM's code16:56
rickspencer3Riddell, so we just need someone to step up and do this today?16:56
Riddell"just"16:56
pittiso in theory we could even blacklist it from the kubuntu seeds for now, perhaps?16:56
rickspencer3I'll take that as a yes16:57
rickspencer3Riddell, how many hours of programming?16:57
tseliotRiddell: where's this pseudocode?16:57
rickspencer3would you estimate?16:57
Riddellrickspencer3: depends if you can find the right places in KDMs code.  maybe 3 (plus testing)16:57
Keybuk in kdm, before starting the X server16:58
Keybuk call plymouth --ping16:58
Keybuk if this has exit status 0 (true), plymouth is running16:58
Keybuk if plymouth is running16:58
Keybuk   call plymouth deactivate16:58
Keybuk   then call plymouth --has-active-vt16:58
Keybuk   if this has exit status 0 (true), plymouth was displaying a splash screen and has terminated leaving it on screen16:58
Keybuk     get the currently active vt16:58
Keybuk     start the X server *on that vt*16:58
Keybuk     if the X server starts ok16:58
Keybuk       call plymouth quit --retain-splash16:58
Keybuk     if the X server *fails to start)16:58
Keybuk       call plymouth quit16:58
Keybuk   if plymouth --has-active-vt has a non-zero exit status (false), plymouth might have been running but did not display a splash screen16:58
Keybuk     call plymouth quit16:58
Keybuk     start the X server as you previously would have (hardcoded to VT7 I assume)16:58
Keybuk if plymouth --ping has a non-zero exit status (false), plymouth was not running16:58
Keybuk   start the X server as you previously would have (hardcoded to VT7 I assume)16:58
Keybuk<Keybuk> oh, and I forgot16:58
Keybuk the other bit (I always forget this)16:58
Keybuk when you start X on the current vt, pass -nr16:58
Keybuk e.g. -nr vt716:58
rickspencer3http://paste.debian.net/64495/16:58
rickspencer3:)16:58
seb128I think 3 is optimistic to find your way around a new codebase and do such changes16:58
rickspencer3tseliot, do agree with 3 hour estimate?16:59
Riddellwell I'm trying to not be too pessimistic :)16:59
tseliotrickspencer3: I wouldn't know, I would have to look at kdm first16:59
rickspencer3does *anyone* here know kdm?17:00
seb128I don't17:00
rickspencer3ok17:00
rickspencer3I think we'll need to consider going down the mitigation path17:00
* tseliot grabs the code17:00
Riddellit's the same code as xdm which is 15 years old and not the sort of code most people like to touch17:00
tseliotoh17:01
pittirealistically for beta-1, I think it might be easier to disable plymouth?17:01
rickspencer3Keybuk, pitti what pitti just said17:01
seb128I would think so too17:01
pittiafter all, half of the people had it uninstalled until a week ago17:01
rickspencer3not just easier, but in fact feasible17:01
seb128can we just make a small change to kdm code which make the thing boot?17:01
seb128even if it doesn't display the splash when it should etc17:01
seb128or do we need the full login to get it booting?17:02
Keybukrickspencer3: I don't know what any effects of that might be17:02
rickspencer3Keybuk, well, I think there will be a change/test/change/... cycle involved with the mitigation17:03
seb128Keybuk, do we need the full logic you described before of would part of it only allow to go through boot even if visually it doesn't do what it should?17:03
rickspencer3it won't be no work17:03
tseliotwould a certain degree of temporary ugliness be tolerated?17:03
Keybukseb128: I don't understand why not having the logic doesn't allow it to go through the boot ;)17:03
rickspencer3it will be work, but seems more likely to unblock Kubuntu beta than trying to fix it17:03
Keybukit should work anyway17:03
seb128Keybuk, can you try to help Riddell maybe there to figure why it's blocking?17:04
Keybukunfortunately in debugging, slangasek and I had assumed that Plymouth had the same code as gdm17:04
seb128can->could17:04
Keybuksince the work item had been marked done17:04
Keybukso that changes things17:04
Keybukseb128: honestly, not really17:04
KeybukI haven't time17:04
tseliotif the answer to my question ^^ is yes we can just prevent plymouth from loading if kdm is installed/in use17:05
tseliotjust like we do when we check the "splash" boot parameter in plymouth17:05
tseliotwould this be acceptable as a hack before we get an actual solution?17:05
Riddelluglyness is fine for beta, better than a frozen bootup17:05
seb128tseliot, graphical issues are not a stopper there I would say17:05
pittitseliot: I thought without splash it'd boot in text mode?17:06
seb128ie if you can make it boot without splash I would consider it enough for beta117:06
pittiyes, I agree17:06
tseliotKeybuk: yes, no, will you to kill me if I do it :-P ?17:06
pittiif we'd hack ubuntu-meta and kubuntu-meta to not pull in plymouth, this would amount to the same anyway17:06
pittiRiddell: does it boot without the "splash" parameter?17:07
tseliotpitti: no, AFAIK it falls back to text only if splash is there and your driver doesn't have a decent framebuffer17:07
pittithis could just be temporarily changed in cdimage17:07
Riddellpitti: I've no idea, I can't edit grub so I can't even workaround it locally17:07
tseliots/to/try/17:07
* tseliot can't spell today17:07
pittiRiddell: wouldn't the live system have the same problem?17:07
pittiyou can edit boot parameters in the boot splash thing with F617:08
Riddellpitti: doesn't seem to, live system is fine for me17:08
Keybuktseliot: the splash parameter in plymouth doesn't disable plymouth though17:08
pittiRiddell: pressing shift during boot should fire up the grub menu17:08
Riddellpitti: it doesn't17:08
pittioh, let's try to figure this out after the meeting, shall we?17:08
Keybuksorry, the lack of a splash parameter17:08
tseliotKeybuk: no, but it can prevent it from showing the splash, right?17:08
Keybuktseliot: no17:08
Keybukit just changes the plugin plymouth uses17:08
tseliotah, so pitti is right17:09
Keybuka lot of the reports of KDM issues are with the text plugin anyway17:09
tseliotKeybuk: we can change that though17:09
Keybuktseliot: err, no, please don't17:09
pittitseliot, Keybuk: question is if it's still hanging in text mode?17:09
tseliot:-)17:09
rickspencer3so what's the resolution?17:10
Keybukyou'll just discover new bugs by moving things around17:10
Keybukrickspencer3: 1024x768 :p17:10
rickspencer3we'll try unseeding Plymouth?17:10
pittiI'd check it in text mode first17:10
rickspencer3or not using it for Kubuntu?17:10
pittiif that boots, we can just work around it in cdimage17:10
rickspencer3who can work with Riddell on testing that?17:10
pittiand failing that, remove plymouth from -meta17:10
pittirickspencer3: I'm fine to help out with seed changes, etc.17:12
pittiwill take me a while to download the current kubuntu CD, though, but perhaps Riddell can do the testing, since he's able to reproduce17:12
kenvandinei can do some testing in a VM17:12
* kenvandine downloads latest image17:12
Riddellkenvandine: I don't have this problem in a VM17:12
rickspencer3pitti, am I understanding this correctlyL17:12
kenvandineRiddell, :/17:13
rickspencer3plan 1 - force Kubuntu to use plymouth text plugin17:13
rickspencer3if that doesn17:13
rickspencer3t work fall back to17:13
seb128I can't really help with that, I've no kubuntu image handy and with my download speed it would take hours to download one17:13
kenvandineRiddell, i could dig up hardware to install on17:13
rickspencer3plan 2 - don't install Plymouth at all on Kubuntu (and do whatever seed changes are required by that?)17:13
kenvandinedoes it only affect certain drivers?17:13
pittirickspencer3: right17:13
rickspencer3ok17:14
rickspencer3so pitti to organize this, Riddell and kenvandine to help with testing?17:15
tseliotRiddell: I guess it can all be done in kdm/backend/server.c17:15
kenvandinei am happy to test, just ping me17:15
chrisccoulsoni could probably help out with testing too17:15
chrisccoulsontseliot, i was just looking in there too. it doesn't look very pretty17:15
rickspencer3ok17:15
rickspencer3Riddell, do you think that plan 1, plan 2 will unblock Kubuntu beta 1?17:16
RiddellI don't know what plan 1 involves17:16
tseliotchrisccoulson: it's not so ugly, assuming that it works ;)17:16
pittiRiddell: boot with nosplash17:16
Riddellpitti: how?17:16
Keybukerr17:16
rickspencer3Riddell, do you think that plan 2 will unblock with beta17:16
Keybukwhat's "nosplash" ? :)17:16
rickspencer3?17:16
pittis/no/no /, sorry17:17
pittiRiddell: mind you, I have no idea at all whether this can work; but since we don't know why it's hanging in the first place, it's worth a try17:17
pittiRiddell: it can be disabled in grub (either in the menu, or by booting in rescue mode and editing it in /etc)17:17
rickspencer3I'd like to move off this topic in the meeting and move this plan into action17:18
Riddellpitti: and you can help me work out how to do that locally to test and on the CD if it works?17:18
pittiRiddell: yes17:18
sabdfl1Riddell: no need to block on artwork for beta117:18
Riddellrickspencer3: that'll be our plan for beta then17:18
Riddellsabdfl1: right, we're aiming for beta 2 for the new logo now17:19
rickspencer3Riddell, sabdfl1 let's just get the new logo asap ;)17:19
rickspencer3Riddell, may we move on?17:20
Riddellrickspencer3: yes17:20
rickspencer3thanks Riddell17:20
rickspencer3pitti, release status?17:20
pittiok, so fir st beta-1: http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html17:21
pittiI moved the remaining coding ones over to http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-2.html17:21
pittithere are four WIs left, which I think should be doable until Thursday17:21
pittikenvandine, tseliot, chrisccoulson, didrocks: please let me know if you don't have time for them, but please try to get them done by Thu17:22
pittiotherwise this looks quite well17:22
rickspencer3wow17:22
rickspencer3close17:22
chrisccoulsonpitti - i shouldn't have any issues17:22
pittiI won't talk about beta-2 just yet, that's for next week17:22
kenvandineok17:23
pittichrisccoulson: right, you just need the package list reviewed?17:23
chrisccoulsonpitti - yeah, which i've pretty much done. already, some people are disagreeing with my choices of extensions to remove though17:23
pittikenvandine: and you just have "write test plan" and an apport hook improvement?17:23
tseliotpitti: do you want me to upload fglrx even with the freeze? (just asking)17:23
pittitseliot: please do17:23
tseliotok17:23
kenvandineapport hook?17:23
pittitseliot: just to get it off the list (it'll stay in unapproved until after beta-1)17:23
kenvandinepitti, where is that?17:23
tseliotpitti: aah, ok17:24
pittikenvandine: oh, sorry, I thought tehre was something about "wrong notify priorities"17:24
pittikenvandine: nevermind, must hav mixed it up; it's just two documentation things17:24
kenvandine:)17:24
=== sabdfl1 is now known as sabdfl
pittiok, the more interesting thing now17:24
pittihttps://bugs.edge.launchpad.net/~canonical-desktop-team/+assignedbugs17:24
rickspencer3ya!17:24
pittiseb128 worked hard on producing a list of bugs which aren't earth shattering, but woudl really be nice to be fixed in lucid17:24
pittisome already got assigned to individual team members17:25
pittibut those still need to17:25
pittiso, I wanted to hear some general opinions17:25
pitti(1) I could go ahead and fan them out to appropriate people17:25
pittiand you guys reassign them back if you don't have time17:25
pittior17:25
pitti(2) everyone grabs a bunch17:25
pittiwith "everyone" being our GNOME loving team members17:26
chrisccoulsoni see there's a gpm one that's probably appropriate for me ;)17:26
pittichrisccoulson, didrocks, pitti, RAOF, seb12817:26
rickspencer3pitti, can we do #2 for say, rest of the week, and then you clean up with #1?17:26
pittirickspencer3: heh, I was just going to propose that ;)17:26
seb128I would prefer (2)17:26
seb128we already dispatched things around17:26
seb128but I feel people are already quite loaded with tasks now17:27
seb128so I would rather prefer having people picking extra one if they feel they have capacity for those17:27
pittiI'm not sure how everyone's task list looks like after beta-117:27
chrisccoulsonpretty heavy now :)17:27
pittiso, those five of us, can we grab 5 bugs each for now and see how far we get?17:28
seb128chrisccoulson has lot of assigned tasks already17:28
seb128pitti, you too apparently17:28
seb128not sure about other people17:28
rickspencer3not to mention compiz maintaining17:28
seb128lol17:28
pittiwell, remember that you can still unassign later on, or just not get it done17:28
pittibut it's good to have it on someone's radar17:28
seb128I would rather not have people claim bugs if they are realistically not going to work on those17:28
chrisccoulsonseb128 - could we also add bug 390816 to the list please :)17:28
ubottuLaunchpad bug 390816 in gnome-power-manager "external monitor output is switched off when closing the laptop-lid when gnome-power-manager is set to blank screen on closing" [Medium,Triaged] https://launchpad.net/bugs/39081617:28
seb128so they don't lock potential work from other contributors or team members17:29
rickspencer3I agree with seb12817:29
seb128chrisccoulson, oh right, doing that now17:29
pittiafter beta-1, our focus should move from the WI tracker to https://bugs.edge.launchpad.net/people/+me/+assignedbugs17:29
rickspencer3I'd rather have them on the list unassigned17:29
rickspencer3unless there is a 80% firm commitment to fix it17:29
pittirickspencer3: nobody will look at that, though17:29
chrisccoulsonseb128 - thanks17:29
pittiI don't believe in unassigned milestoned bugs17:29
pittifrom a long experience17:29
seb128pitti, I would expect you do once your +assignedbugs is empty17:30
rickspencer3fair enough17:30
pittiso I think everyone should grab a few, get them done, and reiterate until release17:30
seb128ok, works for me17:30
pittiseb128: a lot of stuff on my +assignedbugs isn't necessarily for lucid, though17:30
seb128please grab things you think you can get done17:30
rickspencer3pitti, ok, that's pretty much what i was trying to say17:30
pittiok, so there's enough game around, go ahead and hunt!17:30
rickspencer3thanks pitti17:31
pittiwe'll review this list every week from now on17:31
rickspencer3also thanks to seb128 for leading the top bugs effort17:31
pittiand remember:17:31
seb128np ;-)17:31
pittihttp://qa.ubuntu.com/reports/bug-fixing/lucid-fixes-report.html17:31
pittiwe have to chase seb128!17:31
seb128lol17:31
hernejjseb128: Excuse me for interjecting, where can community members who are interested in helping out find this "100 bug list"?17:31
rickspencer3I will give one of my track lead t-shirts to anyone who gets within 80% of seb12817:32
rickspencer3hi hernejj!17:32
seb128hernejj, https://bugs.edge.launchpad.net/~canonical-desktop-team/+assignedbugs17:32
rickspencer3pitti, else for release status, or can we close the meeting17:32
rickspencer3?17:32
seb128hernejj, it's not really 100 but that's the list17:32
pittirickspencer3: I'm done17:32
rickspencer3"top bugs" not "100 bugs" ;)17:33
rickspencer3okay17:33
seb128I think I asked before17:33
seb128but nobody has a way to list lucid tasks for all team members on one webpage?17:33
pittirickspencer3: if you add the ones on our personal +assignedbugs, it's 100 :)17:33
pittiseb128: bughugger can do that, I think17:33
rickspencer3nice17:33
seb128I would like to have an overview of how many bugs everybody claimed17:33
rickspencer3seb128, bughugger has that as of this morning17:33
seb128so we can try unload people who have too many17:33
rickspencer3do the json search for desktop team assigned17:34
seb128rickspencer3, ok, I will try that in a bit, maybe you can tell me what to do after the meeting?17:34
rickspencer3and then filter by release contains lucod17:34
seb128ok, seems easy17:34
seb128thanks17:34
rickspencer3seb128, I'll be around later if it doesn;t work for you17:34
seb128k, thanks17:34
rickspencer3bdmurray just added the release column, and I haven't tried it17:34
rickspencer3any other business?17:34
rickspencer3tick17:35
rickspencer3tick17:35
rickspencer3ok17:35
rickspencer3great17:35
* rickspencer3 taps gavel17:35
rickspencer3thanks all!17:35
rickspencer3let17:35
rickspencer3s get that Kubuntu beta out there!!17:35
rickspencer3:)17:35
seb128thanks17:35
Riddellpitti: so, what needs set in grub, and how can I set grub's settings from a live CD?17:37
* kenvandine digs up hardware to install kubuntu on :)17:37
pittiRiddell: what happens if you hold the left shift key down during boot?17:38
Riddellpitti: no change17:38
pittistrange17:38
pittiRiddell: you hold that down already when the bios boots?17:39
pittiit needs to be done rather early17:39
pittiRiddell: anyway, from a live CD, mount the root partition and edit /boot/grub/grub.cfg17:39
Riddellyes, just tried it, no sign of grub, usplash starts and freezes with 5 orange dots17:39
pittiRiddell: search for "keystatus"17:39
pittireplace that entire if..fi block with "set timeout=10"17:40
pittithat should show the menu during boot17:40
pittiRiddell: then, if you see it, edit the "linux" line to drop "splash"17:41
pittiRiddell: let's see what that does; expected result is that usplash starts in text mode17:41
pittiI don't know whether it makes a difference, but it's worth trying IMHO17:41
Riddelllive CD booting..17:41
Riddellgroovy, grub showing17:46
Riddellvoila, no splash and KDM starts17:46
pittidoes it shutdown correctly, too?17:47
pittiRiddell: would probably be worth trying this five times or so, just to check that it's not just good luck17:47
pittiRiddell: how reliable is the hang with "splash"?17:47
Riddellpitti: shuts down fine, no splash shown17:48
Riddellstarts up fine a second time with me editing grub, no splash shown17:48
pittiRiddell: hm, none at all?17:49
pittitseliot, Keybuk: until a week ago or so, removing "splash" used the text backend of plymouth; did that change?17:49
Riddellpitti: hang with splash happens every time on this computer17:49
tkamppeter pitti, hi17:49
pittiRiddell: finally, can you try booting the live system without "splash"? that should give a different timing behaviour17:49
pittitkamppeter: o/17:49
tkamppeterpitti, can you help me debugging a dbus problem?17:50
pittiRiddell: so, it's text mode, but perhaps acceptable for b1?17:50
pittitkamppeter: not right now, sorry; can we talk tomorrow?17:50
pittitkamppeter: or just ask around in #u-devel and see if someone bites? (otherwise we can debug tomorrow morning)17:50
tkamppeterOK, seems that the meeting did not end for you.17:51
pittitkamppeter: meeting did, but not the fun :)17:51
Riddellpitti: this is acceptable for beta 1 yes17:51
pittiRiddell: let's discuss that in #u-release a bit17:51
seb128chrisccoulson, did you want to claim bug #390816 btw?17:52
Riddellpitti: hum, booting live CD without "splash" gives me a blank screen and no KDM17:52
pittiRiddell: there might be two places -- one is the boot option for the live system, and one for the installed one, but I'm not sure; I pinged cjwatson17:52
seb128chrisccoulson, there is the lucid task now but it's unassigned17:52
chrisccoulsonseb128 - yeah, i will look at that one17:53
seb128chrisccoulson, thanks17:53
ubottuLaunchpad bug 390816 in gnome-power-manager "external monitor output is switched off when closing the laptop-lid when gnome-power-manager is set to blank screen on closing" [Medium,Triaged] https://launchpad.net/bugs/39081617:53
seb128chrisccoulson, assigning to you17:53
pittiRiddell: not even a text cursor?17:53
jcastrokenvandine: if we're turning on salut by default why ask the user for the name and all that when we can get that from the system?17:54
kenvandinejcastro, because it isn't always set17:54
jcastro a person's username?17:54
seb128well it could use the system info to prefil values17:54
jcastro^^^17:54
kenvandinejcastro, feel free to re-open if you think it could be better17:55
kenvandinethat would be fun to work on :)17:55
jcastrowell, not for lucid17:55
seb128the username at least should be easy17:55
pittiRiddell: another thing worth testing is to purge plymouth17:55
kenvandineseb128, yeah... that has to exist :)17:55
Riddellpitti: oh this time it booted ok from the live CD without "splash"17:55
pittiRiddell: I'm pretty sure that a system works fine without plymouth at all17:55
pittiRiddell: I'm less sure about "no splash", that gave some trouble in the past17:55
jcastrokenvandine: perhaps when U1 ties in the person's avatar and all the about-me stuff; that would be a good time to prefill things like that17:56
pittiRiddell: so that we can test both possibilities, and then work out what's easier to do17:56
Keybukpitti: text mode has the ENTER kills X bug still17:56
Keybukbut yes, splash vs. no splash changes the plymouth plugin from script to text or details17:57
Keybukcan't remember which offhand17:57
Keybukmight be details17:57
Keybukwhich I don't think has the enter kills X bug - at least, haven't replicated it on that one17:57
pittiKeybuk: I didn't get that one without splash two weeks ago, but some other funny effects (can't remember the details any more)17:58
pittiback then, slangasek said "drop splash -> don't do that", but a lot has changed since then17:58
Keybukatm, text.so is the only plugin that kills X :p17:58
Keybukanything with a proper renderer works17:58
pittiok, so it seems we should rather not install it at all then; seems safer than hoping that text mode works17:58
Keybukthat would probably be better17:59
Keybukit'll stop me getting bug reports17:59
Riddellpitti: third time unlucky with live CD boot, no KDM this time either18:01
pittiRiddell: ok, let's not pursue the "drop splash" thing then; too unreliable18:01
Sarvattcan you just throw stty -F /dev/tty7 -isig in a startup script for now to fix the text plugin enter crashes? (that works here)18:01
Riddellpitti: so plan 2, just apt-get remove plymouth?18:03
Riddellthat also removes plymouth-x1118:03
pittithat's fine; I don't think we're using p-x11 for anything right now18:03
pittiwell, maybe we do18:03
pittibut I never had problems without having it18:04
Riddellseems to boot fine, moans about plymouth being terminated but KDM starts18:04
Riddellpitti: I guess I need to remaster the CD image to test that on the live CD18:06
pittiRiddell: use persistency?18:07
pitti(usb key)18:07
Riddelloh aye, I'll try that18:07
pittiRiddell: but see #release, seems this would have some drawbacks as well18:07
pittiRiddell: so in the end it seems that plymouth is chained to our testicles now, and we have to fix kdm somehow18:10
Riddellmaybe we could offer tseliot irn bru?18:10
pittitseliot, Keybuk: wrt your idea about a simpler approach, could we just add "plymouth --quit" to kdm's upstart job for now?18:10
Keybukpitti: we have exactly that, basically18:11
Keybukapparently that doesn't work18:11
KeybukI'm confused about that18:11
tseliotRiddell: uh?18:11
Riddelltseliot: or any other beverage that might persuade you to write this patch tonight :)18:12
tseliotRiddell: really you don't want me to write code when I'm tired18:12
tseliotKeybuk: can't we just make kdm install a file in, say, /lib and make the plymouth upstart scripts look for that file and not start? (temporarily)18:13
Keybuktseliot: that's the same as not installing plymouth18:14
Keybukwhich means you're screwed when it comes to filesystem issues or cryptsetup, etc.18:14
tseliotright, mountall18:14
pittiright, that's why I thought a simple plymouth --quit in the kdm.init might be better18:14
Keybukpitti: there's a plymouth --quit in plymouth.conf18:14
Keybukwhich is run on "starting kdm"18:14
Keybukbut I've no idea why that doesn't work18:14
pittiis that really confirmed to be a kdm problem? or perhaps a hardware related one?18:15
Keybukit works just fine on intel ;p18:15
Keybuklots of people are confirming they see "login:"18:15
Keybukeven when they shouldn't :p18:15
Keybuksorry on ubuntu, not intel18:15
Keybukintel-on-the-brain today18:15
pittiRiddell: when the hang occurs, can you ssh in and check if plymouthd/kdm/Xorg are running?18:16
pittiRiddell: "initctl list" should tell which jobs are active; in particular, whether it already started kdm and stopped plymouth18:17
Riddellcould try18:17
pittior whether it's eternally hanging in plymouth itself18:17
Keybukalso how many dots do you see? :p18:17
Riddell5 orange ones18:17
Keybukdoes it jump to all 5 ?18:18
tseliotKeybuk: kdm.conf seems to emit "starting-dm", why can't we catch that?18:18
pitti   [ "$UPSTART_EVENTS" = "starting" -a "$JOB" = "kdm" ] && retain_splash="--retain-splash"18:19
Keybuktseliot: we don't use that for anything18:19
pittiKeybuk: perhaps the --retain-splash is a culprit?18:19
Keybukpitti: actually that line of code can never be true, but anyway18:19
pittiah, ok18:19
RiddellKeybuk: jumps from 1 to 5 orange then freezes18:19
Keybukthat's where we *started* from :)18:19
Keybukwe did the whole "err, this code is actually wrong - why hasn't kdm noticed" thing18:19
Keybukok18:19
Keybukif it jumps to 5, that means "plymouth quit" has been run18:20
* tseliot -> dinner18:20
pittiI thought that was meant to go back to VTs (like in server)18:20
Keybukit is18:20
Keybukthat's quite odd in of itself18:20
Riddell"initctl list" http://kubuntu.pastebin.com/ihF7cChn18:20
pittiso, plymouth is stopped and kdm running18:21
KeybukRiddell: and no plym in ps ?18:21
Riddellplym is not in ps, kdm is in ps18:21
Keybukand what do you see on screen?18:22
Riddell"ubuntu" plymouth splash with 5 orange dots18:22
pittiRiddell: does kdm have a patch to start the first X server on vt 7?18:23
Keybukcan you paste the X line from ps?18:23
pittiRiddell: sudo ls -l /proc/`pidof X`/fd|grep tty18:23
Keybukalso ls -l /proc/$(pidof X)/fd | grep tty18:24
pittiheh18:24
pittiRiddell: if that's tty1, then bad things will happen18:24
pittithey'd also happen without plymouth, though18:24
Keybuknot hugely bad18:24
Keybukright18:24
Keybukit still confuses me why the plymouth stuff is still on screen18:24
Keybukcould you also grab me cat /proc/fb18:25
pittiKeybuk: oh? before we had that it was completely screwed for me; getty would start on top of X and grab all the keypresses18:25
Riddellit has this patch from fedora http://bazaar.launchpad.net/~kubuntu-members/kdebase-workspace/ubuntu/annotate/head:/debian/patches/kubuntu_104_kdm_active_vt_plymouth.diff18:25
Keybukpitti: you can use the mouse ;-)18:25
Keybukup until the point getty gets bored, respawns, and nukes X18:25
KeybukRiddell: what triggers using that patch?18:25
Keybuknothing should afaict18:25
RiddellKeybuk: it's always used, the code runs if /var/spool/gdm/force-display-on-active-vt exists18:25
Keybuknothing makes that though18:26
Riddellright, so the patch does nothing18:26
Keybukafaict18:28
Keybukoutput of the above commands would be nice ...18:28
Riddelllrwx------ 1 root root 64 2010-03-16 18:28 7 -> /dev/tty818:28
Riddellthat's sudo ls -l /proc/`pidof X`/fd|grep tty18:28
Riddell>sudo ls -l /proc/$(pidof X)/fd | grep tty18:29
Riddelllrwx------ 1 root root 64 2010-03-16 18:28 7 -> /dev/tty818:29
Keybukok18:29
Keybukthat's used the first inactive VT18:29
Keybuksilly question18:29
Keybukhave you tried pressing Alt+F8 ? :)18:29
Keybukor maybe ssh in and chvt 818:29
Keybukwhat's in /proc/fb ?18:29
Riddellalt+f8 doesn't do anything18:30
Riddellhttp://kubuntu.pastebin.com/FZr3xVqE  ps shows /etc/gdm/failsafeXServer running18:30
Riddellsudo chvt 818:30
Riddellthat hangs18:30
Riddellwhen run from ssh18:30
pittiRiddell: oh, do you have /var/log/Xorg.0.log.old?18:31
Riddell>cat /proc/fb18:31
Riddell0 nouveaufb18:31
Riddell1 VGA16 VGA18:31
Riddellpitti: yes18:31
Riddellpitti: http://kubuntu.pastebin.com/AVSFNzDZ18:32
pittixf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call18:32
pittihmm18:32
pittitseliot, bryceh: do we know whether plymouth/gdm works with nouveau?18:32
pittiRiddell: so that also used vt 8; it's using vt7 here, but at least it won't get into the way of getty, so that's not it18:37
Keybukok, you're using nouveau18:37
KeybukRiddell: how many monitors do you have?18:38
RiddellKeybuk: 118:38
Keybukjust the panel?18:38
Riddellthis computer has a video chip on the motherboard which I think is S3 I don't use, and an nvidia card of some sort which is used18:39
Riddelli don't know if that answers your question or not18:40
brycehpitti, it ought to18:40
brycehpitti, I'm helping keybuk debug a nouveau issue on his card on #ubuntu-kernel presently18:41
brycehpitti, if you look at the testing results for nouveau while most cards "just work" there are definitely a fair number of cases where things are utterly broken18:41
KeybukRiddell: that implies to me that plymouth should be just using the frame buffer18:42
Keybukno fancy drm or gem involved18:42
pittibryceh: ok, thanks18:42
Keybukwhich is the simplest renderer by far18:42
Keybukit should have VT switched back though18:42
Keybukcould you try booting without kdm for me - how do you get left?18:43
pittiKeybuk: "xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call" - did you ever see that before?18:43
pittiit's a bit weird that X dies on such a thing18:43
pitti-EINTR is the silliest thing in the world, but one would guess that this would have been discovered before18:44
Keybukpitti: depends what the signal is18:44
KeybukI'm wondering whether this is kdm being badly written18:45
Keybukif it daemonises reaaally early18:45
Keybukthen it could be starting the X server *at the same time* as plymouth is tearing down the console18:45
Keybukoh18:45
Keybukno18:45
Keybukwe use starting kdm18:45
Keybukhmm18:45
Keybukplymouth should be gone18:45
KeybukRiddell: yeah, try booting without kdm18:45
Keybukwhere do you end up18:45
Keybukat a VT or left with plymouth?18:46
RiddellKeybuk: on a VT18:46
pittiso, ./hw/xfree86/os-support/linux/lnx_init.c doesn't do any effort to restart the VT_WAITACTIVE on a signal18:47
pittiRiddell: does /var/spool/gdm/ exist for you?18:48
pittiI wonder what part actually creates /var/spool/gdm/force-display-on-active-vt in kdm18:49
pitti(/var/spool/gdm doesn't exist in Ubuntu, BTW)18:49
Keybukpitti: old plymouth/gdm transition code in Fedora only18:51
KeybukRiddell: okkk18:51
KeybukRiddell: Alt+F7 for me - anything on there?18:51
RiddellKeybuk: from what state?  frozen splash screen?18:51
KeybukRiddell: from the current state - booted, no kdm, on VT118:52
Keybuk(I assume you saw some plymouth as you booted?)18:52
pittibug 441653  seems similar18:53
ubottuLaunchpad bug 441653 in xserver-xorg-video-ati "xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call" [Undecided,Confirmed] https://launchpad.net/bugs/44165318:53
Riddellyes plymouth was up18:53
pittibut that was pre-plymouth (but with kdm)18:53
Riddellalt+f7 takes me to a terminal saying "init: ureadahead-other main process terminated with status 4"18:53
KeybukRiddell: and you can go back to Alt+F1 ?18:53
RiddellKeybuk: I can go back to alt+f1 yes18:53
KeybukRiddell: ok, login18:53
Keybukand write the following file18:53
Keybukimport os18:53
Keybukimport fcntl18:54
Keybukfd = os.open("/dev/tty7", os.O_RDWR)18:54
Sarvattpitti: old bug but looks kind of relevant? https://bugzilla.redhat.com/show_bug.cgi?id=32350118:54
ubottubugzilla.redhat.com bug 323501 in rhgb "rhgb causes "xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call" on real X startup" [High,Closed: rawhide]18:54
pittiKeybuk: right, but if /var/spool/gdm wouldn't exist, http://bazaar.launchpad.net/~kubuntu-members/kdebase-workspace/ubuntu/annotate/head:/debian/patches/kubuntu_104_kdm_active_vt_plymouth.diff is a no-op18:54
Keybukfcntl.ioctl(fd, 0x4B3A, 0x01)18:55
pittiSarvatt: I found that, too, but it's for an "rhgb"18:55
Keybukfcntl.ioctl(fd, 0x5606, 0x07)18:55
Keybukfcntl.ioctl(fd, 0x5607, 0x07)18:55
Keybuk--18:55
Keybuksave that file18:55
Keybukrun sudo python on it18:55
Keybukpitti: welcome to the middle of this conversation <g>18:56
RiddellKeybuk: screen freezes18:56
Keybukjust freezes?18:57
Riddellyep18:57
Riddellcan't change VT18:57
Keybukblack freeze?18:57
Keybukor with that ureadahead message18:57
Riddellstill shows me what was on the terminal before18:58
Keybukok good18:58
Keybukssh back in, change the file18:58
Riddellsudo prompt18:58
Keybukfirst ioctl -> 0x01 to 0x0018:58
Keybuksecond and third ioctl -> 0x07 to 0x0118:58
Keybukthen run it again18:58
RiddellKeybuk: screen unfreezes18:58
KeybukI should worry that I know things like that off by heart18:59
RiddellI am impressed18:59
NCommanderccheney: ping, we have a revised ARM enablement patch. Can I tempt you to replace the one in ooo-build :-)?18:59
Keybukit helps that 0x4B is "K" -> so 4B3A is "K three A" which kinda rhymes18:59
Keybuk0x56 is "V" :)18:59
KeybukI was very briefly amused by the kernel folks when I discovered that ioctls kinda matched the first letter of the ioctl constant19:00
Keybukso ok19:00
Keybukthis is confusing19:00
Keybukwithout kdm, everything works19:02
Keybukplymouth quit restores VT7 back to text mode19:02
Keybukand switches the VT back to VT119:02
Keybukthis is the *same* plymouth quit that's run "on starting kdm"19:02
Keybukbut you don't see that with kdm enabled19:03
Keybukyou get stuck on VT7, which is still in graphics mode, which still has the plymouth output on it19:03
KeybukI wondered whether nouveau might have left that there19:03
Keybukyour Alt+F7 proved it isn't19:03
Keybukso I wondered whether nouveau, when you set to KD_GRAPHICS, restores what ever was graphical before19:03
Keybukit was a possibility given KMS + GEM (which I've never seen)19:03
Keybukthose ioctls you did proved that wasn't true19:03
Keybukyour system wasn't hung19:04
Keybukit was just in graphics mode ;)19:04
Keybukthe second set put it back to KD_TEXT19:04
Keybukso19:04
Keybuktheory?19:04
KeybukX is getting started before plymouth has quit?19:04
Keybukno idea how that could happen19:05
qenseI've got a patch ready for AppInd integration for Banshee. I have submitted the same patch upstream but it's not sure if it will make it into 1.6.0. Do you think it's worth the trouble to get the patch into our banshee package? It would allow us to expose it to some testing before the final release.19:06
pittiKeybuk: "on starting kdm", does that mean "before kdm daemon is even started"?19:07
pittior "while kdm is starting"?19:07
pittii. e. do these two run in parallel?19:07
pittiif so, would a sleep 5 right before launching kdm (in the upstart job) help to check this theory?19:08
Keybukpitti: before19:08
Keybukand wait19:08
pittiok, so that's not it then19:08
Keybuka sleep 5 would be an interesting test19:08
Keybukplease do try it19:08
Riddellk19:08
ccheneyNCommander: sure, url?19:09
pittiRiddell: before you reboot, can you please remove /var/log/Xorg.*, so that after boot we can be sure that if we have two Xorg logs, we really had two X servers starting up?19:09
* ccheney bbia 30m, lunch19:10
pittiit looks like the first one dies on that -EINTR, then failsafe kicks in, and doesn't work19:10
NCommanderccheney: http://pastebin.ubuntu.com/395620/19:10
Keybukit's strange to me though19:10
Keybukbecause ioctl 0x5607, 0x07 *is* VT_WAITACTIVE19:10
Keybukand riddell's python didn't get -EINTR :p19:10
ccheneyNCommander: ok will commit it after lunch19:12
Riddelladded sleep at the start of the script in /etc/init/kdm.conf and no change, plymouth splash gets to 5 orange dots and stays there19:12
pittiKeybuk: it's X which gets the signal, not kdm19:12
pitti(and dies)19:13
RiddellI have both Xorg.0.log and Xorg.failsafe.log19:13
pittiRiddell: Xorg.0.log has the EINTR again?19:13
Keybukinteresting19:13
Riddellpitti: it has xf86OpenConsole: VT_WAITACTIVE failed: Interrupted system call19:13
Keybukcould you add a sleep 5 to plymouth.conf at the bottom of the pre-stop script19:13
pittiok, that's consistent then19:13
pittiRiddell: just for testing I'll monkey-patch Xorg to retry on EINTR (which is the usual approach on that error code)19:14
Keybukpitti: I want to know what signal it's getting interrupted by19:15
Keybukcould we attach gdb to X ? :p19:15
pittistrace perhaps19:15
tseliothttps://wiki.ubuntu.com/X/Backtracing19:16
Riddelladding sleep 5 below exec plymouth in plymouth.conf makes no change, 5 orange dots frozen quite still19:16
Keybukok19:19
Keybukafter that sleep 5 can you add19:19
Keybukactually sod it19:19
Keybukthat's just weird in of itself19:19
Keybukok19:19
Keybukbefore and after the sleep 5 in plymouth pre-stop19:19
Keybuktouch /var/run/plymouth-pre-stop-before19:19
Keybuktouch /var/run/plymouth-pre-stop-after19:19
Keybuk(ie. one before, one after)19:19
Keybukthen do the same for kdm19:19
Keybuktouch /var/run/kdm-start-before19:20
Keybuktouch /var/run/kdm-start-after19:20
Keybukeither side of the sleep 519:20
Keybukthen reboot19:20
Keybukssh in19:20
Keybukand stat those four files and stick in pastebin19:20
Riddellok19:21
Keybuk(obviously ssh in to get the stat)19:22
RiddellKeybuk: http://kubuntu.pastebin.com/rdw9ern019:24
seb128bbl19:26
NCommanderccheney: figure you also might want to know that the latest ooo-build builds fine on lucid with our current config options (at leas ton ARM)19:31
KeybukRiddell: so the plymouth ones aren't being run?!19:38
ccheneyNCommander: ok19:39
RiddellKeybuk: seems so19:40
Keybukweird19:40
Keybukcan you add to plymouth.conf:   post-stop exec touch /var/run/plymouth-stopped19:40
pittiRiddell, Keybuk: https://edge.launchpad.net/~pitti/+archive/ppa now has an xserver which retries that ioctl on -EINTR; might be worth a try? (it won't tell us yet which signal it gets, that should be done with strace)19:41
ccheneyNCommander: is the patch name still proper? branch_directly_to_cpp_vtable_call_on_arm19:41
NCommanderccheney: yes, its just revised code that is more stable; the old patch under some cirmstances will corrupt the stack :-/19:42
Keybukpitti: it's ok19:42
KeybukX is correct, it probably should not retry that19:42
Keybuka signal during that signal is a bad thing19:42
Keybukwell19:42
Keybukactually arguably it's not very robust :p19:42
Keybukit shoudl recover19:43
pittiwell, like the sleep statements it's another thing to test19:43
Keybukbut the bug here is not an X one necessarily19:43
pittinot necessarily a final fix19:43
Keybukyeah, I'd like to continue down one line of testing at a time though ;)19:43
pittibut the problem certainly doesn't get easier with two X servers starting in a row19:43
pittiKeybuk: sure19:43
ccheneyNCommander: oh ok19:43
pittiKeybuk: just wanted to mention it, I have a meeting in 15 mins and need to grab a quick bite before19:43
RiddellKeybuk: that stuff I should add to plymouth.conf is all on one line ?19:44
pittiKeybuk: and to get a feeling that I contributed a least a tiny bit to the debugging :)19:44
KeybukRiddell: yeah all on one line outside of the script blocks19:45
RiddellKeybuk: http://kubuntu.pastebin.com/GjksHanj19:45
didrockspitti: hey o/ the WI wasn't close as it should, changing that now. The other one (forbidding for setting encrypted home user as autologin) should be quickly done, can have a try for next Friday but for beta 2, it's ok :)19:45
KeybukRiddell: ok, that's quite interesting19:46
KeybukRiddell: could you change the touch to "env > "19:46
Keybukie. dump environment to the plymouth-stopped file19:46
Keybukreboot19:46
Keybukand cat the file rather than stat it19:46
* Keybuk wonders whether it's a bug that your sleep 5 only slept for 4.46s19:47
pittididrocks: thanks19:48
* vuntz wonders whether he should repeat what didrocks told him today or not...19:49
seb128hey didrocks vuntz19:49
seb128vuntz, repeat!19:49
didrockshey seb128, pitti :-)19:49
didrocksvuntz: ahah ;)19:49
ccheneyNCommander: i think the info in issue 105359 needs to be updated by i might be wrong19:49
RiddellKeybuk: http://kubuntu.pastebin.com/R0fRKGp519:49
seb128how are the linux solutions this year?19:49
NCommanderccheney: in the tracker?19:50
NCommander(OOo bug tracker?)19:50
ccheneyNCommander: yea19:50
KeybukRiddell: and definitely nothing in /var/run to do with plymouth?19:50
ccheneyNCommander: lool wrote on it yesterday but no mention of this new patch on it yet19:50
RiddellKeybuk: only plymouth-stopped19:50
didrocksseb128: fine, lot of people coming (even if vuntz is there). Good cheese and wine tonight ;-)19:50
vuntzseb128: he told bad things19:50
Riddellno sign of /var/run/plymouth-pre-stop-before19:50
didrocksseb128: but bad network, as every year :-)19:51
KeybukRiddell: this vexes me19:51
KeybukI am very vexed19:51
Keybukcould you pastebin the kdm.conf as well, just so my eyes and brain match?19:51
didrocksvuntz: nobody will trust you anyway :p19:51
seb128didrocks, ah, food and drinks, I see what you do all day ;-)19:51
didrocksseb128: only this evening, then, we was flushed out by the security :-)19:52
RiddellKeybuk: kdm.conf http://kubuntu.pastebin.com/7v7Pnc9c19:52
Keybukok19:52
Keybukand the plymouth.conf - could you pastebin that too?19:52
RiddellKeybuk: plymouth.conf http://kubuntu.pastebin.com/5ZQQjvk319:53
Keybukoh19:53
Keybukduh19:53
Keybuk"exec plymouth quit" -> that should be just "plymouth quit"19:53
Keybuksorry19:53
Keybukcould you try that, then ls -l the /var/run bits for kdm and plymouth - along with the cat of the other file19:54
ccheneyNCommander: i got it checked into the 3-2 branch, just trying to find out how to pull a git commit into head, someone else managed to do it without it being another commit19:54
NCommanderccheney: no idea :-/19:54
ccheneyNCommander: rene might know how to do it if so he'll probably fix it by tomorrow19:55
ccheneyNCommander: i asked on the ooo-build channel but no response yet19:55
RiddellKeybuk: umm, my /etc/init/plymouth.conf seems to have emptied itself19:57
Keybukhttp://kubuntu.pastebin.com/5ZQQjvk319:57
Keybuk:p19:57
Keybukfortunately you put it on the internets19:57
* Riddell installs emacs, enough of this nano toy19:59
RiddellKeybuk: well KDM starts, no sign of /var/run/plymouth-*  http://kubuntu.pastebin.com/b8zCTcpd20:02
Keybukdid you modify plymouth.conf ?20:03
Keybukto remove the "exec" before plymouth quit ?20:03
Riddellyes20:03
Keybukcan you pastebin your plymouth.conf again20:03
Riddellplymouth.conf http://kubuntu.pastebin.com/HrgdXq6720:04
RiddellI don't see any splash on start now20:04
Keybuksorry20:16
Keybukjust to confirm20:16
Keybukyou didn't paste the jr@lichts:~>cat /etc/init/plymouth.conf bit20:16
Keybukinto your plymouth.conf20:16
Keybuk? :p20:16
RiddellKeybuk: no I didn't20:18
KeybukRiddell: edit the file, save it, check syslog20:18
RiddellKeybuk: I added a new line in /etc/init/plymouth.conf and saved it, syslog has some stuff about [drm] nouveau setting dpms mode20:19
Keybukno parse errors from init then?20:21
Riddellno20:21
Keybukhuh20:21
Keybukit was working fine until the file vanished20:21
Keybuk:-/20:21
KeybukI'm 100% sure I know what's wrong20:21
KeybukI just want to do this test to prove it20:21
Keybukah20:22
Keybukdid any of the other plymouth files empty themselves? :p20:22
Keybuklike plymouth-splash.conf ?20:22
Riddellno they all have non-zero size20:22
Keybukmeh20:24
Keybukrebooting doesn't show the splash at all?20:24
Riddellnope20:24
Keybukok, I guess we give up then20:24
Keybukfile permissions? directory permissions?20:24
KeybukRiddell: in other news, my Fedora spies tell me they've patched kdm to do almost the same thing as gdm ;)20:25
RiddellI looked at their packaging today and the patch hadn't changed from the one we stole from them months ago20:26
Keybukit might be in cvs somewhere?20:27
Keybukbut yeah20:27
Riddellhttp://cvs.fedoraproject.org/viewvc/rpms/kdebase-workspace/devel/kdebase-workspace-4.3.4-kdm_plymouth.patch?revision=1.3&view=markup20:27
KeybukI don't know how plymouth has broken for you since you emptied the file20:27
RiddellKeybuk: /etc/init is 755, /etc/init/* are all 644, all root owned20:27
pittiRiddell: I still feel this patch is a no-op, though20:28
Riddellpitti: yes I agree20:28
Keybukpitti: nah, I bet your patch fixes it now20:28
Keybuknow I understand what's happening20:29
Keybukthe only thing I couldn't see was why those files weren't appearing from pre-stop20:29
Keybukand that was because the line before was "exec ..." :p20:29
pittiah, heh20:29
pittiKeybuk: so you know why X gets an unexpected signal now?20:31
Keybukwell20:31
KeybukI know the state of the machine when X starts20:31
Keybukthe current VT is VT720:31
Keybukthat VT is in KD_GRAPHICS mode20:31
KeybukI don't know how X is started, but however it is, it clearly isn't happy about that20:31
tseliotKeybuk: but shouldn't it be in text mode before we start X?20:44
tseliotand I can fix how X is started20:45
Riddellkenvandine, chrisccoulson: are either of you doing kubuntu test installs?20:45
Keybuktseliot: no, that's what --retain-splash is all about20:45
Keybuk--retain-splash means "leave the console in a bad state"20:45
tseliothehe20:46
tseliotKeybuk: I'll try to reproduce the gdm behaviour in kdm if I can, so that we can use deactivate instead (after the beta)20:46
kenvandineRiddell, i have dug up a netbook i can test on20:53
kenvandineRiddell, found any specific fixes i should test?20:53
Riddellkenvandine: no but it would be good to have someone else that has the issue should we ever come across a fix20:54
kenvandineok, i'll reproduce now20:54
KeybukRiddell: it would be nice if you could get back into a state where plymouth at least apparently works20:55
Keybukuntil it kills kdm20:55
Keybuksince I can't get this nvidia machine to accept KMS20:55
RiddellKeybuk: I purged and reinstalled plymouth, it now starts and freezes with 5 orange dots20:55
Keybukok, sweet20:56
Keybukso can you try something for me20:56
Keybukmodify plymouth.conf20:56
Keybukscroll down to the pre-stop bit20:56
Keybukand comment out the line about retaining splash with kdm20:56
Riddellcomment is a hash presumably?20:56
tseliotyep20:58
Keybukyes20:58
Keybukthat's shell in there20:58
RiddellKeybuk: plymouth drops to a terminal, a few seconds later KDM starts21:00
Keybukand KDM starts normally21:01
RiddellKeybuk: yes21:01
Keybukhurrah21:01
Keybukthe universe is as it should be ... I am right21:01
Keybukok21:01
Keybukput that line back21:01
Keybukand try pitti's patched X server21:01
tseliotlol21:03
Riddellran  sudo apt-get install xserver-common xserver-xorg-core  and rebooted21:07
Riddellplymouth freezes at 5 orange dots21:07
Keybukok21:07
Keybukand I guess X is still getting -EINTR ?21:07
pittiRiddell: what does Xorg.0.log say now?21:07
Keybukis it looping continually getting -EINTR?21:07
pittior .old (if it's running failsafe now, which ps aux|grep X should tell)21:08
RiddellXorg.0.log http://kubuntu.pastebin.com/i3qwjV4m21:08
Riddelljr@lichts:/var/log>ps aux|grep X21:08
Riddelljr        1154  0.0  0.0   7544   884 pts/0    S+   21:08   0:00 grep X21:08
Riddellno X running?21:09
pittio_O21:09
pittihm, I was just going to ask for an strace to check whether it gets EINTR in a loop21:09
pittiI didn't test that X server with an EINTR, I just booted it here to see that it still works on a "normal" system21:10
Keybukohhhhhh21:10
KeybukI just worked this out21:10
Keybukof course it gets -EINTR21:10
Keybukthe next one will fail EINVAL or something21:10
Keybukand then X will give up and exit21:11
KeybukRiddell: you know how gdm has a patch pitti wrote so that the first X server is always on vt7, even when plymouth isn't running21:11
Keybukyou don't have one of those patches, do you? :p21:11
Riddellno21:11
Riddellwe don't21:11
Keybukyou always let X pick whatever VT it likes <g>21:11
Keybukso you have lots of bugs21:12
Keybukyou have the "X picked VT1 because getty wasn't using it yet" bug21:12
Keybukand, right now21:12
Keybukyou have "X picked VT8 but can't switch to it, because plymouth set VT7 up for X to takeover, so VT switches aren't allowed right now"21:12
mvoccheney: hello, re #516727 -- debian fixed this in their packages, can you please import the fix and upload a new version?21:13
mvohttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=57036121:13
ubottuDebian bug 570361 in openoffice.org-filter-binfilter "aptitude refuses upgrade from 3.1.1-15 to 3.2.0-1" [Serious,Fixed]21:13
mvofix is in 1:3.2.0-221:13
mvo(and why do I have to find out about this fix?)21:13
tseliotKeybuk, Riddell: right, that's a patch that I wanted to port to kdm too21:14
KeybukNOT A PLYMOUTH BUG21:14
* Keybuk dances around the house singing21:14
tseliotin fedora they always use tty121:14
tseliothehe21:14
Keybuktseliot: in Fedora they kill babies and eat them too21:14
tseliothehe21:15
mvoccheney: fixed in debian almost 3 weeks ago21:16
tseliotRiddell: so you have a temporary workaround, right?21:16
Riddellnot as far as I know21:16
Riddellalthough commenting out the --retain-splash line seemed to help21:16
tseliotKeybuk: can't we detect kdm and skip that ^^ ?21:17
Keybuktseliot: sure21:17
Riddellit's only set for KDM :)21:17
Keybukbut there's a far more serious kdm bug here21:17
Keybukyou can't just pick the first active VT like that21:17
Keybukthat'll be vt1 in half the cases21:17
Keybukand then kdm will run on the same tty as getty21:17
Keybukand they'll steal keypresses from each other21:18
Keybukand then getty will get bored, respawn21:18
Keybukand X will die21:18
Keybukthere'll be a funeral and everything21:18
Keybukso21:18
Keybukit's a bit of luck we didn't go with the "don't seed plymouth" option :p21:18
Keybukplymouth was the only thing protecting you from that bug21:18
tseliotheh, nice21:19
chrisccoulsonhi Riddell, sorry, i went for dinner21:21
chrisccoulsondo you still need me to do a test install?21:21
tseliotKeybuk: as the nth workaround we can just hardcode tty7 in kdm until the proper fix is in place21:21
Keybuktseliot: that breaks multi-user switching21:21
Riddellchrisccoulson: yes it would be good if you could21:21
pittitseliot: that's pretty much what http://bazaar.launchpad.net/%7Eubuntu-desktop/gdm/ubuntu/annotate/head%3A/debian/patches/05_initial_server_on_vt7.patch does21:22
pittiit's the worst patch evar21:22
pittibut until today I haven't figured out/got told a better way to do it :(21:22
tseliotpitti: yes, that's exactly what I had in mind. I remembered that piece of code21:22
rickspencer3seb128, I have your query in bughugger right now21:23
rickspencer3do you want me to paste the moin somewhere for you or something>21:23
rickspencer3?21:23
seb128rickspencer3, excellent, I was about to reboot to try something but I'm back in 2 minutes and then yes21:24
seb128brb21:24
rickspencer3ok21:24
tseliotKeybuk, Riddell: would something like that be acceptable for beta1? (please say yes)21:24
rickspencer3we have 80 Lucid bugs it looks like21:24
Riddelltseliot: sorry like what?21:25
Keybuktseliot: something like the initial_server_on_vt7 patch?21:25
tseliotRiddell: like the patch that pitti mentioned21:25
tseliotKeybuk: yep21:25
Riddelltseliot: yeah if there's a kind and clever soul who can code it in time21:25
* pitti downloads kdm code and has a look21:26
Keybuktseliot: that would be very nice indeed21:26
Keybukkdm needs that patch anyway21:26
pittiurgh, it's in kdebase-workspace21:26
tseliotRiddell: yes, I'll try. Otherwise (if I can't code it in time) we can just ship the workaround in the upstart script and keep our fingers crossed21:27
shtylman_pitti: yes.. indeed ... enjoy :)21:27
Riddelltseliot: which workaround in the upstart script?21:27
tseliotRiddell: commenting out the --retain-splash thing when using kdm21:28
Riddellright21:28
tseliotand joining the X funeral every once in a while as a side effect ;)21:28
shtylman_Riddell: tseliot: I was under the impression that the kdmrc file can tell kdm which vt to use?21:28
pittiso, I think buildling kdebase-workspace will take some two hours on my box21:28
shtylman_pitti: you can build just a part of it21:29
tselioticore7 FTW21:29
shtylman_pitti: specifically kdm21:29
pittishtylman_: oh, any tricks/21:29
pitti?21:29
pittithat would be very helpful indeed21:29
shtylman_pitti: yea... use cmake directly21:29
shtylman_now if you want to make the deb... thats another story21:29
shtylman_but for plain building.. you can most certainly build only the part you need21:29
pittishtylman_: as long as I can run it from the build tree, I don't care about a .deb21:29
shtylman_pitti: yea.. then you are good21:29
shtylman_use cmake to make the initial build tree21:30
seb128re21:30
shtylman_but stop it before it starts building21:30
pittiapt is almost done with installing the gazillion build deps21:30
shtylman_and then just change to the kdm directory (in the build tree) and do make there21:30
shtylman_it will handle the rest21:30
seb128ups, still buggy, brb21:30
pittishtylman_: how do I invoke that?21:31
TheMusoGood morning.21:32
Riddellpitti: you can run debuild then control-C once the cmake configuration is done21:32
pittiah, ok21:32
shtylman_pitti: best bet.. once you have the source... make a directory (i usually call it build) and then cd to that and run: cmake <path to source>21:32
Riddellthen cd obj-<tab>/kdm; make21:32
shtylman_pitti: or that :)21:32
seb128re21:33
seb128rickspencer3, ok, I'm back, sorry about that21:33
rickspencer3seb128, no problems21:34
rickspencer3seb128, do you want to try it with bughugger yourself first?21:34
seb128rickspencer3, sure21:35
rickspencer3seb128, when it in inevitably crashes or is too confusing, let me know, and I'll paste you the data somehere :/21:36
shtylman_pitti: let me know how that goes ... I can try testing it tonight on my laptop21:36
seb128ok, I'm waiting for it to unfreeze from the launchpad handshake right now ;-)21:36
seb128seems stucked...21:37
* tseliot -> off for the night21:37
seb128oh, slangasek there ;-)21:40
slangasekpitti: Riddell tells me you're stuck porting the vt7 patch to kdm?  is that going to get done today?21:41
pittislangasek: I'm on it right now21:41
pittiI'm currently finding my way in the kdm source to see where it starts the server21:41
seb128rickspencer3, "retrieving release targetted bug_tasks for canonical-desktop-team in lucid", how long does that usually takes?21:41
slangasekpitti: kdm/backend/server.c :)21:42
pittiah, thanks21:42
seb128rickspencer3, unping, it moved tp retrieving other things21:43
seb128I'm away for a shower while it's working21:43
rickspencer3seb128, nooo21:43
rickspencer3use the json search21:43
rickspencer3it will literally take hours to search that way21:43
rickspencer3I mean the way you are doing it21:43
seb128rickspencer3, I've no clue what json is or how to use that...21:43
rickspencer3ok21:44
rickspencer3go search->json searches21:44
rickspencer3click on desktop team assigned21:44
rickspencer3then click on the run button above21:44
rickspencer3this will slurp in the cached results from bdmurray's cron job21:44
seb128rickspencer3, ooooh21:45
seb128rickspencer3, ok, I though json would require me to write a json file21:45
seb128thanks ;-)21:45
seb128ok, now it makes sense21:46
rickspencer3sorry seb128, not an inutitive UI21:47
rickspencer3at least there is no help file to ensure that no else can use it easier21:47
seb128that's ok21:47
seb128lol21:47
rickspencer3this keeps bug reports rather to a trickle21:47
slangasekpitti: so I'm going to afk now for a bit, since I expect I'm going to be working late into the evening shepherding this through; if you get to a point where you need to drop it and you don't find me on IRC, feel free to call me and I'll take it from there as needed21:49
pittislangasek: ok, will do21:49
seb128robert_ancell, hye21:51
seb128hey21:51
robert_ancellseb128, hello21:52
seb128rickspencer3, ok, the UI sucks but otherwise bughugger is quite handy ;-)21:52
rickspencer3hehe21:52
rickspencer3seb128, patches welcome21:52
* rickspencer3 adds seb128 to bughuggers team21:52
seb128lol21:53
robert_ancelland assigns him all the bugs21:53
Keybukyes, because what we really need is for seb128 to burn out ;-)21:54
seb128robert_ancell, you wait to be back there!21:54
pittiKeybuk, Riddell: sorry, what was the reason again why kdm sends the first X to vt8?21:58
pittii. e. should we respect that, or force to vt7 on first start?21:58
Keybukpitti: first unallocated vt21:59
Keybukshould be forced to vt7, like gdm is21:59
Keybuk(for the first server)21:59
pittiKeybuk: no, I mean kdm launches X with an explicit "vt8"22:00
pittigdm doesn't do that (upstream)22:00
Keybukoh wow22:00
Keybukno idea on that one22:00
rickspencer3TheMuso, RAOF, robert_ancell, bryceh ... Eastern Edition?22:00
KeybukRiddell: ?22:00
TheMusorickspencer3: sure lets go22:00
* bryceh waves22:00
* RAOF was born ready!22:01
pittiKeybuk: ok, I thought it was discussed and I missed it; nevermind22:01
RiddellI don't know anything about an explicit "vt8", it starts on vt 7 pre-lucid22:01
Keybukpitti: I had assumed that X was just picking the first unusued22:01
Keybuknot that kdm has an explicit vt822:01
rickspencer3pitti, Riddell, Keybuk typically at this time we rehash the team meeting for our friends in Sydney and such22:02
rickspencer3so please excuse us while we flood the channel ;)22:02
pittirickspencer3: sorry, will STFU22:02
rickspencer3TheMuso, robert_ancell, RAOF, bryceh the minutes are here:22:02
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-03-1622:02
rickspencer3pitti, not at all, I didn't mean it that way22:02
rickspencer3we don't talk too much, so carry on22:03
rickspencer3;)22:03
robert_ancellhehe, didrocks is having fun with seteuid now :)22:04
* TheMuso reads through.22:05
* bryceh caught backlog earlier22:05
didrocksrobert_ancell: "fun" wasn't really the exact word TBH. There is a bug there and I strike on it yesterday for two hours before seb128 told "did you check that seteuid is working?" :)22:05
robert_ancelldidrocks, :)  I'm always suprised how complex low level unix stuff is when you actually try and use it22:06
didrocksrobert_ancell: right, and there is a bug there, but yesterday, it was 11 PM and I was tied to not have think the issue came from there (I was more blaming the gconftool-2 side :))22:07
didrocksas I'm at a French Linux event on the canonical booth those 3 days, I don't really have the time to check that. I'll see on Friday if nobody's touch it :)22:08
rickspencer3TheMuso, robert_ancell, RAOF, let me know when you're done looking over the minutes22:08
* TheMuso is done.22:08
robert_ancellrickspencer3, done22:08
pochumvo: heya, are you aware of any application using VteReaper from python-vte, other than gdebi?22:08
RAOFrickspencer3: Done.22:09
rickspencer3alright22:09
rickspencer3I guess we'll touch on some highlights22:10
rickspencer3looks like the GDM sound patch thingy is underway22:10
rickspencer3and there's a bit to discuss later about top bugs22:10
rickspencer3in the partner update there was generally agreement that the Dx team was delivering good stuff, and the weekly releases are quite useful22:12
rickspencer3should extend that to OLS next release22:12
mvopochu: no, I *think* nowdays everything is provided by vte, in the past IIRC the exit-status was missing from python-vtw without the reaper22:12
mvopochu: but somone will have to verify22:12
pittiKeybuk, slangasek, Riddell: ok, seems it's working in my local build tree now; I get the first X to vt7, and subsequent X to vt8 (kdm is pretty insistant on the latter)22:12
Riddellpitti: cool22:13
rickspencer3I propose we skip discussing the Kubuntu/KDM bug as it is being worked on in parallel22:13
RAOF:)22:13
TheMusosounds good22:13
pittiRiddell: are you on amd64 or i386?22:13
rickspencer3work items22:13
pittiRiddell: -> #u-devel22:14
rickspencer3pitti, sorry to keep interupting you guys22:14
rickspencer3we'll be done in like 2 minutes22:14
rickspencer3so we're pretty much done our work items22:14
rickspencer3please look and see if you have any left TODO22:14
rickspencer3and if so, ensure they are done by the scheduled milestone22:15
rickspencer3lastly, "Top Bugs"22:15
brycehrickspencer3, is the multitouch wi's included in that list?22:15
rickspencer3bryceh, hmmm22:15
brycehor are we handling it separately completely22:15
rickspencer3prolly should be22:15
rickspencer3but it should be targetted to beta 222:15
* bryceh nods22:15
baptistemm_hi there, if someone could sponsor bug 539914 it fixes corruption issue when sending files to devices22:15
ubottuLaunchpad bug 539914 in obexd "Update to version 0.22" [Undecided,New] https://launchpad.net/bugs/53991422:15
rickspencer3so, top bugs22:16
rickspencer3seb128 put quite some work into finding important and actionable issues22:16
rickspencer3though not release blockers, please pick them off and drive this list to zero22:16
rickspencer3ok22:17
rickspencer3that's it22:17
seb128baptistemm_, there is a meeting right now but please subscribe ubuntu-sponsors so it's in the queue for after beta freeze later22:18
rickspencer3TheMuso, any audio status?22:18
TheMusorickspencer3: Nothing big change wise since last week, just bug fixing and triaging.22:18
rickspencer3good to hear22:18
rickspencer3ok22:18
rickspencer3TheMuso, robert_ancell, RAOF, bryceh any questions or other business?22:19
TheMusonope22:19
robert_ancellrickspencer3, no22:19
RAOFNo.22:19
rickspencer3bryceh, next week is there some way we could check in on the status of your xorg quality project?22:20
rickspencer3not sure how you would report on that22:20
rickspencer3maybe just some impressions in next weak's Eastern edition22:20
ccheneymvo: ok, will apply the workaround as well with my next upload, it seems in the bug report relating to his change that it can still leave OOo in a broken state but that apparently it couldn't be fixed in aptitude22:20
brycehrickspencer3, sure22:21
rickspencer3thanks bryceh22:21
brycehrickspencer3, do you mean quality of X, or status of tools for measuring quality of X?22:21
ccheneymvo: though he was talking to himself in the comment from some other post that isn't in the comments so not sure what he was talking about exactly22:21
rickspencer3bryceh, I mean quality of x22:21
brycehok22:21
rickspencer3the thing you are doing with RAOF and jpeterson and tseliot, etc..22:21
rickspencer3started in #ubuntu-x22:21
brycehright22:21
rickspencer3I think it will be interesting to people, especially if you escape the mythical man month22:22
brycehwe had a good meeting today, and have a plan.  I'll summarize how we're doing next week.22:22
rickspencer3thanks bryceh22:22
mvoccheney: ok, thanks. I will add a workaround in u-m for beta-1 so that we do not get too many bugreport22:22
rickspencer3do you feel that you have the people power to do the right things now?22:22
brycehI hope so22:22
brycehRAOF took on a pretty large chunk of it22:22
brycehand hopefully jpeterson can offload his other tasks sufficiently22:23
baptistemm_g'dnight22:23
RAOFWe'll see how that goes :)22:23
brycehI can now easily measure # of bugs, % uploaded, and so on so we can measure this side pretty well22:23
brycehrickspencer3, the question will be if we can get bugs closed22:24
brycehwe've got some intel freezes I'm curious about, and various people reporting kms trouble on nouveau22:24
brycehno surprise there; we knew there'd be lots of regressions on nouveau22:24
rickspencer3bryceh, well ... I wouldn't want you to spend a ton of time measuring bugs instead of getting them fixed or fixing them, so just impression is fine22:24
brycehso just need to get a good stabilization effort moving on that.  raof has a good plan22:24
RAOFWhat's been surprising to me is how *few* regressions we've had reported.22:25
rickspencer3bryceh, there's a fall back position for folks if nouveau doesn't it for them, right?22:25
brycehRAOF, yeah, people reluctant to actually file bug reports.  odd22:25
brycehrickspencer3, blacklisting can be done but it's a really broad brush22:25
brycehrickspencer3, the trouble is this22:25
rickspencer3I guess I meant they can just switch to -nv or something, right?22:26
brycehwith UMS we had developed a pretty good set of techniques for debugging X problems22:26
brycehwe had quirks, lots of docs on wiki.ubuntu.com/X, and tools22:26
bryceha lot of this stuff is no longer viable for doing debugging with kms22:26
RAOFrickspencer3: Passing nomodeset=1 to the kernel will disable kms, which will disable nouveau, which will get you one of {nv, vesa}.22:26
brycehsome is obsolete, some we just don't have the hooks from the kernel to get the info out or put in stuff to test22:27
brycehso this all makes debugging the remaining issues a bit of a tough nut to crack22:27
rickspencer3bryceh, right22:27
brycehbut hopefully sending bugs upstream for them to look at will still be a viable tactic22:27
rickspencer3we'll have to start over with debugging, I guess22:27
brycehalso the kernel team might be able to lend a hand22:27
brycehI will draft up some of my thoughts and email the kernel and x team22:28
brycehultimately I think we need some kernel code written to give better debugging abilities22:28
brycehnot sure if I answered the question or just frightened everyone away ;-)22:30
rickspencer3sorry22:30
rickspencer3lots of questions all over22:30
rickspencer3bryceh, right, we should look at the intel crash handler work and use that as a model22:30
rickspencer3imho22:30
pochumvo: hmm, I'm not sure I get you. gdebi is still using the VteReaper bindings22:31
rickspencer3where h = "not humble at all"22:31
pochumvo: do you mean vte has other functionality to stop using it?22:31
RAOFIt should be possible to get some similar info out of nouveau, but that'll require upstream code.22:32
didrockswell, time to go to bed :-)22:32
mvopochu: yes, its still using the reaper bindings, but I think nowdays it could stop using them because vte got the needed features. I'm not 100% positive though22:32
didrockshave a good day/evening/night everyone!22:33
RAOFdidrocks: Goodnight!22:33
didrocks(not sure to be online tomorrow evening as I'll eat some dinner with evil GNOME devs like vuntz ;))22:34
pochumvo: ah ok22:34
RAOFdidrocks: Have fun!22:34
didrocksthanks RAOF22:34
pochumvo: nothing apart from gdebi that you're aware of then?22:34
Riddelldidrocks: give agateau a hug if you see him at the event22:35
mvopochu: no22:36
Riddellrickspencer3: I don't believe I've been introduced to RAOF, could you do so? :)22:37
rickspencer3hell yeah22:38
rickspencer3RAOF, meet Riddell22:38
rickspencer3Riddell, RAOF22:38
* Riddell shakes RAOF by the hand22:38
rickspencer3RAOF, Riddell is the guy who keeps the Kubuntu plane flying each release22:38
RAOFYeah; I've picked up as much :)22:39
rickspencer3he basically does for Kubuntu what the other 10 of us do for Ubuntu22:39
rickspencer3;)22:39
RAOFRiddell: Hi!22:39
NafaiRiddell is teh awesome. :)22:39
rickspencer3Riddell, RAOF is one of the UNE guys22:39
bryceh*cough* X22:39
rickspencer3so he'll be 50% UNE, and 50% other stuff, I'm hoping mostly x22:39
* rickspencer3 kicks bryceh under the table22:39
RAOFYeah.  There's a fair whack of X in there :)22:40
rickspencer3but for 10.10, RAOF will be virtual bryceh22:40
Riddelloh aye, we do UNE now in this team22:40
RiddellRAOF: are you new to canonical or did you move from another team?22:40
rickspencer3Riddell, YES!22:40
rickspencer3weren't you at the distro sprint?22:40
RAOFNew to Canonical, although I've been around Ubuntu quite some time.22:40
rickspencer3Riddell, oops, I see now you weren't asking a question, silly me22:41
RiddellRAOF: do you code UNE or get code from DX/UX/whatever they're called and make sure it works?22:42
RAOFA bit of both.22:42
RAOFWhat I've done so far has just been some bugfixes merged in to the netbook-launcher.22:44
RAOFMostly it should come in from Dx/Ux22:45
kklimondachrisccoulson: gconf support in transmission is only so it can register itself as a default handler for meta: links (sorry for missing your question completely, don't know if that's still a question). I'm pretty sure that doing it this way isn't the right way and I was going to investigate it because debian builds with both libraries disabled. charles is against storing configuration in gconf22:47
kklimondabecause at the moment the same settings.json can be used by all Transmission clients.22:47
Riddellrickspencer3: is Nafai someone I should get to know too?22:47
chrisccoulsonyeah, gconf is very desktop specific22:48
* pitti waves good night22:48
rickspencer3Riddell, sure22:48
chrisccoulsonkklimonda, i will review the changes then and make sure they're ok to upload22:48
rickspencer3night pitti22:48
chrisccoulsonbut not tonight ;)22:48
rickspencer3Riddell, Nafai is working on Indicators for Dx22:48
kklimondachrisccoulson: sure, no problem :)22:48
rickspencer3Riddell, Nafai is current contracting22:49
kklimondachrisccoulson: transmission isn't going to use gsettings either because daemon is aiming for small, embedded devices.22:49
vuntzdidrocks: it's on thursday, not tomorrow ;-)22:49
Riddellpleased to meet you Nafai22:52
NafaiNice to meet you too22:52
robert_ancellRAOF, TheMuso, lunch on Friday?22:54
RAOFrobert_ancell: Sounds good to me.22:55
chrisccoulsonmeh, there's nobody around here for me to have lunch with :p22:57
TheMusorobert_ancell: Sounds good.22:58
seb128chrisccoulson, how far are you from London?23:00
rickspencer3chrisccoulson, be careful what you wish for23:00
chrisccoulsonseb128 - quite far (about 2.5 hours drive)23:00
seb128yeah, too far for a lunch ;-)23:01
seb128but okish for one or two work day if you ever visit the office23:01
Riddellchrisccoulson, kenvandine: either of you get Kubuntu installed?23:23
chrisccoulsonRiddell, i've got it installed in kvm at the moment, although it's going a bit slow23:23
chrisccoulson(my laptop is grinding to a halt in general at the moment though)23:24
kenvandineRiddell, yup, just came back to it and rebooted23:41
kenvandinelets see if it boots :)23:41
kenvandineRiddell, booted fine... and i don't think i even saw plymouth23:43
kenvandinethis is on a netbook with intel graphics23:43
kenvandineRiddell, logged in and looks very shiny23:44
kenvandineRiddell, so i can't repro your bug here23:44
KeybukRiddell: https://edge.launchpad.net/~scott/+archive/ppa23:48
Riddellkenvandine: oh well thanks for trying23:53

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