[01:03] asac: it's fixable, and it's on my todo list. [01:04] pitti: let's review the list of packages for language-support later, when you come online, shall we? [01:04] ArneGoetje: talk to ccheney and pitti [01:04] they seem to think they can fix it in the bug i filed [01:04] or comment there ;) [01:04] thanks!! [01:04] let me know if you need something [01:04] info etc ;) [01:05] asac: ok [01:06] asac: which bug number? [01:08] 23:46 < ubottu> Launchpad bug 532262 in openoffice.org-dictionaries "openoffice gets installed when adding a language in language-selector" [High,Triaged] https://launchpad.net/bugs/532262 [01:08] Launchpad bug 532262 in openoffice.org-dictionaries "openoffice gets installed when adding a language in language-selector" [High,Triaged] [01:08] ArneGoetje: ^^ [01:14] asac: thanks === bjf is now known as bjf-afk [03:50] does UNE call glxinfo to determine if it should run in 2D or 3D mode? I remember someone asking about ways to determine which was in use in #ubuntu-x a month or two ago about that. mesa-utils is now in universe for some reason (making GL compositing not work on the kubuntu livecd also) [03:57] hmm yeah, netbook-launcher doesn't depend on mesa-utils but netbook-launcher/nl-config.c is calling glxinfo [04:13] Cool. Both save & save as now work. [04:13] And undo is a matter of hooking up an appropriate button. [04:13] And checking that memory consumption doesn't fly to Mars with large images. [04:15] https://bugs.edge.launchpad.net/ubuntu/+source/netbook-launcher/+bug/532405 [04:15] Launchpad bug 532405 in netbook-launcher "netbook-launcher should depend on mesa-utils" [Undecided,New] [04:18] That aubergine really is a soothing colour for the terminal background. [04:19] being forced to that new profile didn't make me happy, i lost a 2 hour long build log because i didnt notice it forced me into a new profile with a 512 line scrollback :) [04:19] ...! [04:19] looked exactly the same as my old setup at low screen brightness [04:19] Thanks for the heads up! [04:20] * RAOF checks the new “unlimited” button. [05:00] Yup, there it is. Memory usage FTW! [05:05] RAOF, oh, I hadn't noticed the unlimited button. I've been wanting that for so long :) [05:06] robert_ancell: It's clearly the correct behaviour, too. [05:11] f-spot is now an excellent way of evicting unused pages from RAM. [05:13] better than tmpfs mounted /var/cache/pbuilder/build/ and g++? [05:13] Not quite as good as that. [05:35] f-spot would be easier to hack on if random pieces of code didn't call Dispose() on perfectly good pixmaps. [06:01] anybody have an idea how to help me install libdap for Matlab I have on my Ubuntu? [06:02] kayve: By joining #ubuntu and asking there? Or checking on ubuntuforums.org? [06:04] nobody listens on #ubuntu [06:04] ever. [06:05] Hm. It'd make sense for Undo to be a button on the Edit sidebar, wouldn't it. [06:06] ubuntuforums.org is a total desolate wasteland for my question [06:06] Are there Matlab-specific forums you could investigate? [06:22] RAOF: u is a real WISE guy.. a WISE guy [06:55] * RAOF has visions of smart undo/redo managers, with memory-limits pushing old data out to disc and pulling it back in as needed... [06:55] Warning: Architecture abstronaught boarding the shuttle! [07:27] good morning [07:28] didrocks: Good morning. [07:29] hey RAOF, how was your day? [07:29] Pretty good. [07:29] Well, frustrating at times. [07:29] oh? [07:30] The f-spot code has a habit of Dispose()ing Pixbufs in strange places. [07:30] But I got 3 f-spot work items this morning, and am pretty much done on the 2nd now. [07:30] argh, so it doesn't make your edit/undo code like easier :) [07:30] sweet! [07:30] life* [07:31] Right. [07:32] well, you have to assume to be the Mono rockstar there :) [07:33] So now the undo passes copies around, and everything is groovy. And just needs to be hooked up to a button! [07:34] * didrocks hugs RAOF for his good work [07:34] and the memory consumption isn't too scary? [07:34] * RAOF hugs didrocks for being awesome. [07:34] Ahem. [07:34] Weeeeeell... [07:34] :) [07:34] ok :-) [07:34] Currently memory consumption is scary. [07:35] It's obvious how to deal with that, though, and the undo API won't need any changes to make it file-backed rather than memory-backed. [07:35] (Or, indeed, to make it a mixture of memory-backed & file-backed, depending on mem-usage and undo length). [07:36] do you know how gimp do for that? It just eats memory IIRC [07:36] The gimp's much smarter than I am, I think; I'm pretty sure it's tile-based and will only copy the changed tiles & such. [07:37] Also, the gimp doesn't have to store a pixmap for each operation, it can just store the operation. [07:37] oh ok. That's because my gf uses more than 3000x2500 px images than it's just scary :) [07:38] but a file backend in /tmp sounds good for f-spot :) [07:38] Ideally that's what I'd be doing here, too, but it'd need a bit of a re-architecturing before that'd work - f-spot is all about passing pixmaps around. [07:38] Yeah. [07:38] oh sweet if you can do that! But that's more intrusive :) [07:39] I'm not going to attempt it. [07:39] It's not the sort of patch I'd be pushing a couple of days away from beta freeze :) [07:40] no, after release candidate is fine :) [07:40] I guess storing pixmaps as a first approach is good, especially for an LTS [07:42] Yeah. [07:44] Woot! One working undo button! [07:44] \o/ [07:45] Good morning [07:45] oh, the edit button is already translated in French [07:45] good morning pitti, how are you? [07:45] And with that, I'm out for dinner with my beautiful wife. Have a good day! [07:45] bonjour didrocks [07:45] much better, a good night's sleep helped a lot :) [07:45] how are you guys? [07:45] RAOF: bye! [07:45] RAOF: enjoy your dinner and your week-end, too! [07:46] pitti: same here :-) [08:11] hmm, it's snowing like mad [08:11] I thought winter was finally over.. [08:12] oh really? it's nice and sunny there [08:37] good morning there [08:38] bonjour seb128 [08:38] hey pitti! [08:38] seb128: do you still remember what the requirements for the gdm cursor are? [08:39] seb128: hide it from X start until gdm is ready, that much I know [08:39] requirements? [08:39] hide it [08:39] seb128: but also from "press login" to "session is ready"? [08:39] * pitti would like to keep that one, but isn't sure [08:39] I think sabdfl would like no spinning cursor at all on login [08:39] hey seb128 [08:39] seb128: ok, I'll see what I can do [08:39] looks rather easy to do [08:39] especially in the autologin case [08:40] no need to have a cursor on an empty screen [08:40] we want it to be displayed when the desktop is loaded [08:40] ack [08:40] lut didrocks [08:40] how lucid looks for everybody? [08:40] * seb128 did several rounds of updates and fixing until late and hope theming is ok [08:40] shiny! [08:40] seb128: look awesome. I like the new defaults (and new g-t color) [08:41] I still need to restart my session to get the full love [08:41] good ;-) [08:41] pitti, I screwed the gdm bzr btw [08:41] oh, how? [08:41] you didn't push your 0ubuntu5 [08:41] so I did debcommit and tag my 0ubuntu5 [08:41] got the uploaded bounced back [08:41] argh, I'm so sorry [08:42] so I had to merge your changes, do mines again and push that as 0ubuntu6 [08:42] so 0ubuntu5 tag is not what it should [08:42] but I'm not sure how to fix that afterward [08:42] pitti, np [08:42] it was just starting be late and I'm not sure how much we care about tags being right [08:42] just letting you know they are wrong for this upload [08:43] right, thanks [08:45] seb128: I think you can untag/override tags [08:45] mvo, I tried deleted one and failed [08:45] yes, but the last two uploads are all in one commit now [08:45] nevermind [08:45] seb128: bzr tag ---force does not work? [08:45] bzr tag --remove , and then retag [08:45] mvo, I get warnings about duplicate tags when I tag again [08:45] pitti, that remove it locally but not online [08:45] but you'd need separate commits for ubuntu5 and ubuntu6 for that [08:46] seb128: for that you need to push --overwrite [08:46] when you push it complains about duplicate tag still [08:46] ah, that might be it [08:46] pitti, well either we let it this way [08:46] seb128: just leave it, it's not a biggie [08:46] or we uncommit my change, push yours and then I do the bzr update again [08:46] ok, good [08:47] * pitti cdbs-edit-patch debian/patches/32-hide-mouse-cursor.patch [08:47] where? gdm? [08:47] or xorg? [08:47] yes [08:47] * seb128 curious [08:47] xorg is fine [08:48] it already starts with an invisible mouse cursor [08:48] so the --enable-null-root-cursor option is obsolete [08:48] it was also removed entirely in git head [08:48] so we just need to stop gdm from displaying the busy one [08:48] there is a patch on launchpad for that IIRC [08:48] and remove it again after you press the login button [08:48] or hack rather [08:49] let me look [08:49] dx guys did one where they commented some gtk calls previous cycle [08:50] it looks rather easy to do anyway [08:50] I didn't see a bug about it [08:50] seb128: btw, is it intended to have a kind of frame around the close/minimize buttons? [08:50] looks a bit weird [08:50] the color shading is opposite to the main window title bar there [08:51] it looks like a drawing error to me [08:51] ARGH ARGH! [08:51] I'm not sure [08:51] pitti, what? [08:51] wo set white text on violet background by default in the terminal? [08:51] * pitti sighs [08:51] sabdfl [08:52] he's the one who sent the settings to use for that one [08:52] well, I guess only in the dark theme anyway [08:52] seb128: in g-appearance-props, my theme is now set to "custom"; is that just local configuration? [08:53] pitti, what ubuntu-artwork version do you have? [08:53] both Ambiance and Radiacne look different [08:53] ambiance is dark, radiance is light [08:54] right, but the "custom" one (which I got after upgrade) has slightly different colors than ambiance [08:54] seb128: 53.1 [08:54] weird [08:54] do you get it in a guest session too? [08:54] can't find the gdm patch from previous cycle [08:55] seb128: don't worry about gdm, it's really not rocket science so far [08:56] ok [08:56] * seb128 away a few minutes to get coffee [08:56] so, need to dist-upgrade my laptop still - this morning it wanted to remove empathy, so I just upgraded [08:56] ah, it's there now [08:56] pitti, wfm in a guest session [08:57] seb128: ok, I blame local configuration then; so it's intended that ambiance is the default? [09:03] pitti, yes [09:03] I use radiance there [09:03] hm, terminal doesn't use the system theme by default, so it's white-on-black for the bright theme as well [09:04] right, design said there was no need to make 2 themes there [09:04] only one with the current settings [09:04] but that means that the terminal defaults to white-on-black in any theme.. [09:04] don't tell me [09:04] well, I'll file a bug [09:04] this is WRONG [09:05] if you ask me we should fiddle with command line themes at all [09:05] shouldn't [09:05] it's tricky anyway [09:05] those don't get set by GNOME themes in the appareance capplet [09:05] so you can't get them changed by switching GNOME themes [09:06] seb128: hm, I removed my entire ~/.gconf/ (on the mini), rebooted, and it still says "custom"; hmm [09:06] pitti, so [09:06] can you get me the gconf key for mouse cursor, gtk, wm themes [09:07] pitti, look to /usr/share/gconf/defaults/16_ubuntu-artwork [09:07] for the key names [09:07] and gconftool --get the one I listed [09:08] those are the first 3 in the gconf-default [09:08] or rather 1 to 5 [09:09] gtk_theme: Dust [09:09] icon_theme: Humanity-Dark [09:09] urg [09:10] that's not coming from the packaging for sure [09:10] grep Dust /usr/share/gconf/defaults/* [09:10] grep Dust .gconf/* -r [09:11] seb128: ok, local b0rkage, nevermind [09:11] ok [09:11] good ;-) [09:11] I've confirmed it's ok on my mini [09:12] which has an alpha3 untouched installed [09:12] install [09:23] hum, maybe netbook-launcher should use the Ambiance theme [09:24] that doesn't break UI freeze? [09:25] what ui freeze? [09:25] ui freeze was yesterday and the theme uploaded yesterday [09:26] seb128: right, but I'm talking about changing the default theme for netbook-launcher session… [09:28] urgh [09:28] seb128: did the new theme do anything to force new settings over existing terminal gconf keys? [09:28] seb128: I previously had no menu bar, no scrollbar, and a different font [09:28] (and different colors0 [09:28] ) [09:28] it's all messed up now [09:28] pitti, ask chrisccoulson when he joins [09:29] ok [09:29] he did all the g-t changes [09:29] he said he took care of having the new profile applied on upgrade [09:29] that might be a sideeffect [09:30] seb128: so that's in gnome-terminal itself? just want to know where to file the bug against [09:31] yeah mine was changed to Ambience too [09:31] pitti, yes [09:31] I flipped it back to "default", and it's back to normal [09:31] "legacy"? [09:31] or that [09:31] "Vorgabe" :) [09:31] which doesn't mean "legacy", but "default" [09:33] ok [09:40] good morning everyone [09:40] hey chrisccoulson! [09:40] how are you? [09:40] yeah, good thanks. how are you? [09:41] hey chrisccoulson [09:41] hey pitti, how are you? [09:41] Laney: please feel free to confirm bug 532511 [09:41] Launchpad bug 532511 in gnome-terminal "terminal settings messed up after upgrade due to forced profile change" [Undecided,New] https://launchpad.net/bugs/532511 [09:41] chrisccoulson: you destroyed my terminals! [09:41] chrisccoulson: I'm great, thanks! how are you? [09:41] pitti - what happened? [09:41] chrisccoulson: bug 532511 [09:42] looking now [09:43] good morning chrisccoulson [09:43] hey didrocks [09:48] chrisccoulson: I attached my original gconf settings now [09:49] pitti - i'm confused slightly. those gconf settings are post-upgrade aren't they? [09:49] chrisccoulson: yes, they are [09:49] chrisccoulson: you changed the default theme gconf key and as most of user change in the default profile and don't create a new one… [09:49] right [09:49] it hasn't migrated you to the new profile according to the settings (it's only merged in the new system profile, so that it appears in your profile list) [09:50] chrisccoulson: I think what happened is [09:50] 1) I have changed the default profile, since that's what "profile settings..." does [09:50] 2) Default was changd to Legacy [09:50] 3) the new default theme is "Ambience" [09:50] didrocks - that was intentional as the request was that people would see the new settings on upgrade [09:50] so it would have totally ignored my settings in "Default" [09:50] chrisccoulson: but that doesn't work at all with customizations [09:51] black on black text is bad.. [09:51] pitti - i only changed the visible UI string from Default to Legacy - the actual (previously default) theme is actually still called "Default" really [09:51] i'll try upgrading a few times this morning and see if i can trigger that too [09:52] I saw it too, btw [09:52] upgrade, restart g-t, got new theme [09:52] chrisccoulson: but it apparently didn't use the settings in /apps/gnome-terminal/profiles/Default [09:52] I had just modified some colours of the default theme [09:52] chrisccoulson: oh, I have an idea [09:52] chrisccoulson: http://launchpadlibrarian.net/40235420/gnome-terminal.gconf-original.xml [09:53] chrisccoulson: my gconf tree only has changes for "Default" [09:53] chrisccoulson: but it doesn't have a custom gconf key for /apps/gnome-terminal/global/default_profile [09:53] so I assume I got that from the schema [09:54] it wouldn't be so bad if the upgrade wouldn't have disabled "use colors from system theme" [09:54] now terminal is white-on-black in all themes, even the light ones [10:08] CURSEs.. foiled again [10:11] * seb128 is away for a bit [10:11] mpt: good morning. i need a error message (in addition to "not connected to the internet") for the ratings&reviews submission when the server is not availalbe (or in read only mode). I except this will happen quite a bit when the server is launched. something like "Sorry, the server is not ready, please try again later." (well, text and place) [10:13] any idea against which package this bug can be opened against (see video): https://bugs.edge.launchpad.net/ubuntu/+source/netbook-launcher/+bug/531997/comments/5 ? [10:13] Launchpad bug 531997 in netbook-launcher "netbook-launcher desktop menu and icons don't always work" [Undecided,Fix released] [10:23] mvo, the spec has "Couldn’t connect to the review service." Is that ok? [10:27] mpt: sure, that is fine. sorry, seems like I have overlooked that. anything like "please try again later" or is that obvious anyway? [10:29] mvo, good point. We have limited room there, though. How about "Sorry, couldn’t connect. Try again later." ? [10:30] pitti: does jockey remove the nvidia packages when you disable nvidia? Or does it only disable the driver? [10:30] tseliot: it removes the package [10:30] mvo, if so, that case we could use the same string for sign-on errors as for review submission errors [10:31] mpt: fine as well. limitied space is a problem indeed, maybe we could move it to a different place or something? I suppose some languages will make it long. [10:31] pitti: can't we just make it switch to the free driver? [10:31] tseliot: since it overwrote libGL (before the alternatives setup), and we also want to untaint the kernel by removing the module [10:31] tseliot: I guess with the alternatives setup we could just switch [10:31] tseliot: but then you woulnd't have a GUI way to actually uninstall it [10:31] pitti: right as nouveau would prevent nvidia from loading [10:31] but I don't mind either way [10:31] whichever you like better [10:32] mvo, how about we move it above the Cancel/Publish buttons? (But still left aligned.) So if there's an error the window lengthens a bit. [10:32] pitti: synaptic or software center should allow you to remove the driver [10:32] mpt: I wonder if we should show something more verbose while the server is in beta mode so that users do not get put off, I'm not sure that this makes sense though [10:32] yes [10:32] mvo, then we could make it more verbose [10:32] mpt: good idea, I can do that can send you a screenshot? [10:32] mvo, sure [10:33] mpt: the window should not resize, right. when its hidden there is just blank space? [10:33] pitti: is there anything that needs to be overridden in the nvidia handler to do this? [10:33] * pitti checks [10:34] seb128: when you will be back: (cf upper): any idea against which package this bug can be opened against this comment: https://bugs.edge.launchpad.net/ubuntu/+source/netbook-launcher/+bug/531997/comments/5 (the video show, even in gnome session, all flickering: gnome panel, nautilus…). That's stop when opening a menu. xorg, maybe? [10:34] Launchpad bug 531997 in netbook-launcher "netbook-launcher desktop menu and icons don't always work" [Undecided,Fix released] [10:35] tseliot: hm, uninstalling the package is pretty deeply woven into the basic Handler [10:35] tseliot: so far we assumed that you want to completely get rid of it to avoid side effects from leftover files [10:35] tseliot: you could hack around it by temporarily unsetting self.package in nvidia.py's disable() [10:35] pitti: right, that used to be the case [10:36] tseliot: this was originally written with this "freedom" idea in mind, thus removing a driver should purge the evil^Wnonfree bits from the computer [10:36] pitti: ah, I think I'll have to do that we I reenable fglrx too [10:36] hehe [10:37] mvo, I was suggesting that it should resize [10:38] mvo, it would be a jump in 2.0, but in Lucid+1 it would slide smoothly [10:39] mpt: ok, fine with me. so just error there or connection label as well? [10:39] http://people.canonical.com/~mvo/tmp/Screenshot-Review%202vcard.png [10:45] mvo, just errors -- "Submitting review…" shouldn't make it resize. [10:48] mpt: yep [10:49] mvo, and remember the mini error icon at the leading end [10:49] mpt: ok, thanks. [10:51] mvo, also the border around the review field. ;-) [10:51] (ok, I'll stop now) [10:52] mpt: border? [10:52] mpt: oh, I think thats a iside effect of it being "sensitive(False)" [10:53] mvo, for some reason in Glade, text fields are missing their border by default, so you need to add it. It should obviously be there even when insensitive. [10:53] mpt: *cough* how are your glade skills doing ;) *cough* [10:53] mvo, I have card sorting sessions for the next 4.5 hours, but if it can wait until after that, sure. :-) [10:54] mpt: no worries, I can fix it now [10:54] mpt: but for stuff that looks incorrect, just jump in and fix it in the glade file, I will merge then [10:55] mpt: +4.5h? woah! [10:55] ok, will do [10:55] mpt: what kind of border do you need exactly? shadow_type? [10:56] or a explicit gtk.Frame? [10:57] mvo, 1/2 hour preparation, 1 hour session, 1/2 hour data collection, lunch, 1 hour session, 1/2 hour data collection [10:58] * mvo nods [11:02] mvo, sorry, I asked bratsche and he didn't know. I know it's been fixed before in other applications. [11:03] mvo, e.g. the Gnome Dictionary does it. [11:04] I can't find it in Glade. === al-maisan is now known as al-maisan-lunch === al-maisan-lunch is now known as al-maisan [11:07] mvo, separate topic, I don't know why the categories branch is showing up as conflicting, I just merged trunk and there were no conflicts [11:07] I committed the merge [11:14] i'm completely confused by this terminal issue now [11:18] asac, chrisccoulson: do you have an opinion about network-manager-pptp? [11:22] pitti: yes, MIR [11:23] on CD [11:23] its essential for 80% of russian DSL users [11:23] asac: I mean, do you know if it's good, or crap, or didn't you use it so far? [11:23] we shouldnt forget to do it [11:23] pitti: its one of the things i actually use from time to time ;) [11:23] it looks pretty okay to me, but I haven't ever used it [11:23] should be fine [11:23] ok, thanks [11:24] pitti: do you need it for private? [11:24] asac: no, just looking at the MIR [11:24] aah [11:24] yes. the main problem was that in the past the vpn plugins werent really maintained as first class citizen upstream [11:24] but that has changed now in 0.8 [11:25] e.g. they were released together with nm/nma [11:37] pitti, ok to upload simple-scan 0.9.6? [11:37] robert_ancell, do you have "Scanning" Category in its .desktop file? [11:38] robert_ancell, ah, nm, I see it does [11:38] mpt, no, way to spoil my release candidate :) [11:38] mpt, oh good. it does :) [11:44] pitti - so, i'm not too sure how to get around this terminal issue. gnome-terminal seems to write user-specific gconf keys for the colour settings even if you don't change them [11:45] so, if i just change the default colour settings in the "Default" profile, then only new users get the new colours, and no upgrader will see them [11:45] chrisccoulson: same issue than with gnome-panel, welcome :) [11:45] which is why I created a whole new profile [11:46] and then the patch I wrote ensures the new profile is merged in to the users list of available profiles [11:55] chrisccoulson: hm, I was going to suggest to just change the default gconf keys [11:55] so that customizations don't get lost [11:55] creating a new profile and forcing upgraders to it will always cause trouble like that [11:55] chrisccoulson: and if a user customized his settings, we should respect that IMHO [11:56] chrisccoulson: and for the default case the new schema values should take over, shouldn't they? [11:56] chrisccoulson: "write user-specific gconf keys for the colour settings even if you don't change them" -> shouldn't we fix that instead? [11:56] pitti - well, that's the issue. gnome-terminal seems to write user-specific keys even if you don't change any settings [11:56] i'll have a look and see if i can make it work anyway [11:56] chrisccoulson: with fixing that, and changing your patch to unset keys which are equal to the default value (for fixing upgrades) we might get much closer to where we want to be? [11:57] yeah, i think so [11:59] pitti, ok to upload ^^^ ? [11:59] robert_ancell: oh, hello; unusual time for you :) [11:59] robert_ancell: what does it change? [12:00] pitti, just bug fixes. It's the 1.0 release candidate [12:00] robert_ancell: bug fixes are alright, UI changes and new features need exceptions now [12:00] re [12:00] didrocks, what was the question? [12:00] I don't fancy reading all the backlog [12:00] robert_ancell: bug fix only is fine, we don't have a "bug fix freeze" [12:00] robert_ancell, hey [12:00] * pitti -> lunch [12:01] pitti, I think I have to ask because it's a new upstream version right? If it was Ubuntu patches it wouldn't need permission [12:01] seb128, hey [12:01] seb128: no pb. It was just "do you have any idea against which package the bug should be reported": the user (on the video) have a flickering screen (gnome-panel and nautilus for instance). It stops when clicking on a menu [12:02] didrocks, xorg? ;-) [12:02]