=== tkamppeter_ is now known as tkamppeter === fta_ is now known as fta [01:51] didrocks: is empathy logs and/or settings something that is being considered for OneConf? === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta === fta_ is now known as fta [05:27] Good morning [05:27] !lightweight [05:27] Factoid 'lightweight' not found [05:27] hi guys. what's the most lightweight, *functional* desktop manager/GUI environment I can use? [05:28] I'm running Lubuntu on my netbook, but I'd like to keep options open === fta_ is now known as fta === fta_ is now known as fta [06:57] good morning [06:57] duanedesign: for maverick, not for now, but in long term, yes [07:36] hey didrocks [07:36] Guten Morgen pitti, how are you? [07:39] didrocks: I'm great, thanks! I'm back in Munich [07:39] we did a nice climbing tour on Saturday [07:40] oh, great :) how is the weather in Munich (hope not too hot as you are in a little accomodation) ? [07:40] small* [07:40] it was 38 degrees on Saturday [07:41] it's a little less melting today, and fortunately this flat goes to the northwest [07:41] so it's quite nice right now (especially at 6 in the morning :) ) [07:41] sometimes it's good to have flat which goes to the north ;) [07:41] heh, right [07:42] In Bordeaux, it was 29 degrees at 8 AM :/ I let you imagine during the day… [08:01] morning all === fta_ is now known as fta === bryceh is now known as 40FAA7E1T [08:47] mpt: could I ask a quick UI question? [08:50] mpt: could I ask a quick UI question? [08:50] and471, yep [08:51] mpt: in this image http://imagebin.ca/img/ZwI8Bn.png, I feel as though how I present the first action is wrong (i.e. the button is on the wrong side or something), is there a better way to do it? === 40FAA7E1T is now known as bryyce [08:53] and471, one clue is that at the bottom of an alert or dialog, a Cancel button should always be second from the right, which means that something belongs to the right of it [08:53] Which is going to be the most common action? Saving, perhaps? [08:53] mpt, probably edit, then save as, then cancel [08:53] save as just means a user is going to edit later [08:54] the file format it saves in isn't really useful without editing first [08:54] ok [08:54] So, I can think of two ways to present this [08:54] One is easy to implement but slow to use [08:54] The other is harder to implement but quicker to use [08:54] sounds fun :D [08:54] The first way is using radio buttons, with an option menu inside the one that's about editing [08:55] What do you want to do with it? [08:55] (*) Edit with [## Pitivi :^] [08:55] ( ) Save it [08:55] ( Cancel ) (( Continue )) [08:55] ok [08:56] The second way is to use a combo button, something I've seen in Windows but haven't seen in GTK, so I'm guessing it probably doesn't exist in GTK and you'd need to do it custom [08:56] "4 minutes 38 seconds were recorded. [08:57] ( Save… ) ( Discard ) ( Edit with Pitivi |^) [08:57] where the "Edit with Pitivi" button has a menubutton at its end that you can use to select a different application. [08:58] mpt, cool, is there anywhere I could have an example of a combobutton, I kinda understand what you mean by it, but I would like to see one to be sure [08:59] and471, the "Open" button in http://www.wictorwilen.se/WindowsLiveWriter/CustomizetheFavoriteLinksinWindowsVistac_EA19/image070208[31].png [09:00] mpt, thankyou very much for your help :) [09:00] you're welcome [09:00] mpt, I shall leave you alone now ;p === fta_ is now known as fta [09:09] mpt, done! http://imagebin.ca/img/bRsbC9f.png [09:09] jolly good [09:11] * RAOF wonders why mutter was chosen for Unity. Compiz uses about half the memory, all the animations are smoother & more physical, and has a more useful window switcher. [09:12] njpatel: ^ [09:12] * and471 needs breakfast [09:13] It also works pretty well as a WM for unity. Pretty much everything still works when you replace mutter with compiz. [09:13] good morning everyone [09:17] hey chrisccoulson, had a nice weekend? [09:17] hey everybody: [09:17] did you have a nice weekend? [09:17] * pitti hugs seb128, how are you? [09:17] hey pitti, yeah, it was good thanks. the weather stayed nice for my garden party on saturday :) [09:17] how are you? [09:17] * seb128 hugs pitti back [09:17] we went climbing on Saturday, and swimming yesterday (what else to do when it's 38 degrees..) [09:17] hey seb128, did you have a good weekend too? [09:18] I'm fine though I wouldn't say no to less than 35°C during days [09:18] RAOF: and compiz just released 0.9.0 [09:19] RAOF: so it would be nice to give it a good boost by providing that in the compiz ppa [09:20] hey seb128, how are you? [09:21] lut didrocks [09:21] didrocks, read backlog, I'm lazy to type again :p [09:21] didrocks, how are you? [09:22] seb128: I'm fine, thanks ;) A little bit exhausted as I was home late in Paris after a too warm week. [09:22] didrocks, had fun at the rmll? [09:22] don't tell me [09:23] seb128: yeah, it's still more a social event than a technical one, but it was good to meet people and talk about projects, and so on [09:23] 28°C at 8AM is quite scary when you think about what it will be later :) [09:23] I find it already hot here, but you live in France! It must be unbearable there without cooling. [09:24] I just visited for a couple of hours Bordeaux. Seems a beautiful city [09:24] it start being windy there, it might rain ;-) [09:25] it rained a lot this night in Paris, the temperature is nice now :) (the 28°C was in Bordeaux) [09:25] RAOF, actually, without Mutter it doesn't/won't work for all the features we need [09:25] RAOF, though I agree compiz has better GL performance. It's something upstream Mutter and Clutter are working on [09:25] (as are we, where we can) [09:25] njpatel: Yeah, the swanky Ubuntu icon doesn't work properly :) [09:26] Heh, neither will any of the fancy window and workspace stuff when it lands :-) [09:26] Unity could be slightly more compiz-friendly by declaring itself to be always-on-top in addition to a panel. [09:27] RAOF, it would require us to keep switching between xshapes (when we're painting only panel + launcher and when we're painting places), which doesn't always work out well [09:27] seb128: didrocks pretented he was working all week, but I saw him! He was just sitting there, looking at people pass by [09:27] (hi!) [09:27] vuntz, hey, I'm not surprised! [09:28] vuntz, he also pretented there was no internet but I've seen other people at this conference been on IRC [09:28] vuntz: that's not nice from you :p [09:28] seb128: well, in fact, there were 3 sites [09:29] njpatel: Ah. I'm interested in the funky window and workspace stuff - is the first cut of this the compiz-scale-like action on right-click? [09:29] seb128: the one with conferences had a mostly working Internet connexion [09:29] didrocks: did you find good ice cream on sunday? [09:29] seb128: the free software "village" had a crappy one, with latency and a lot of disconnect (we didn't have any connection for 3 afternoon) [09:29] vuntz: yeah o/ it was the nicest part of sunday to be honest :) [09:30] didrocks, I was just jocking don't worry ;-) [09:31] seb128: ricotz (in #ubuntu-devel) has a gdkpixbuf package, maybe you can start with that and save some time ;) [09:31] seb128: btw, we learnt that you speak australian english [09:31] seb128: I now, I backlog on Saturday evening and saw you talked to jml :) [09:31] vuntz, that means crappy english right? ;-) [09:31] heh [09:31] didrocks, I didn't do IRC during the weekend, that was friday rather [09:32] vuntz: how was your flight, btw? :) [09:32] slomo, oh ok, thanks, did you commit that to debian or reviewed it? [09:32] seb128: yeah, but the saturday evening bar was the best Internet connexion I had this week, as the fact I backlogged IRC on that day :) [09:32] seb128: not yet, no. he said that the scripts and stuff are still missing [09:32] slomo, btw I just saw your glib upload, isn't an issue to have the bin compat entries in the library? [09:33] slomo, that would make different soname conflict no? [09:33] didrocks, oh ok [09:34] didrocks: my flight was one-hour late [09:34] didrocks: they had to fix something in the plane before we could take off [09:34] RAOF, right, that's the initial one. We'll have workspace switching in their soon. The benefits of being in the window manager will show when we add the fancy DND between windows/workspaces and other niceties for day-to-day usage [09:34] vuntz: urgh, we could have took an icecream finally… [09:35] seb128: the new library package would have a Replaces on the old for the links [09:36] slomo, hum, ok... [09:36] slomo, still seems against usual rules and weird to do [09:37] slomo, why not just using the -bin? [09:44] seb128: might be the better idea... [09:47] seb128: problem is, that gio-querymodules has no pkg-config entry and build systems might require it [09:47] seb128: so you would need to depend on libglib2.0-bin [09:48] slomo, well, how was that working until now? do we really have anything build depending on it in practice or is that something which could happens once to one source? [09:49] slomo, should probably discuss that on #debian-gnome [09:49] seb128: i think gvfs and gconf should call it in make install [09:49] and it worked before because they were, where upstream placed them... in /usr/bin [09:49] they should probably have a flag to not do that [09:49] similar to the disable schemas update one [09:50] well, why did we need to move them to start then? [09:50] i don't know, i didn't see the problem with keeping them in the -bin package together with the triggers and let libglib2.0-0 recommend the -bin package === fta_ is now known as fta === almaisan-away is now known as al-maisan === fta_ is now known as fta [11:32] mvo: hey! I tried to add the different host for oneconf in viewswitcher. The issue is that there is a lot of "if channel column" in the model preventing myself to use that for storing hostid that I need to switch to the right view. [11:33] mvo: what do you think? Should be attribute some kind of plugin id in COL_ACTION and use COL_CHANNEL for plugin? and checking that COL_ACTION is either USC and plugin handled? === al-maisan is now known as almaisan-away === DrPepperKid is now known as MacSlow === DrPepperKid is now known as MacSlow [12:26] didrocks: hi, is your branch available somewhere [12:27] mvo: only with the login integration, I can push my WIP branch. I'm trying something to patch USC, can push in 10 min a proposal I think [12:27] didrocks: ok [12:28] didrocks: once there is something to look at that is easier for me to figure out whats needed [12:28] mvo: sure :) [12:35] seb128: did you want me to merge gjs from debian or not bother since they're the same basic version? [12:36] micahg, would be nice to merge at least once in the cycle if you can do it [12:36] seb128: k, that shouldn't be a problem [12:36] thanks === MacSlow is now known as MacSlow|lunch [13:00] mvo: lp:~didrocks/software-center/expand-viewswitcher-select for my changes in USC and lp:~ubuntu-desktop/oneconf/trunk for oneconf [13:00] mvo: as you can see there (https://wiki.ubuntu.com/SoftwareCenter?action=AttachFile&do=get&target=installed-software-computers.jpg), hosts registered in OneConf will be "ACTION" for USC point of view [13:01] mvo: and I need to use COL_CHANNEL to get some hostid (more than one computer can have the same description, so I need this hostid) [13:02] mvo: the thing is, the current support in USC is only to refresh (by removing/adding) all channels, my change is to enable reselecting whatever item in the treeview rather than just channels [13:02] mvo: I still get some issues with the history element, I don't know why I can't get it selected === fta_ is now known as fta [13:22] didrocks: aha, I see. this sounds like we need to make the current schema in trunk/ more flexible, it looks like your change is a great start, let me start pondering a little bit [13:23] didrocks: and I will merge the plugin stuff to trunk now so that we have a easier time merging [13:25] mvo: great! :) yeah, that's exactly that: some flexibility to enable plugins to hook (as maybe an unique ID for plugins to not collide their action?) also, the some tweaking is needed for on_view_switcher_changed in app.py to enable plugin hooking their action their === MacSlow|lunch is now known as MacSlow [13:54] mvo, hi, I'd like to send a quick reply to https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2010-June/011729.html [13:54] mvo, is the right answer "we're migrating to Ubuntu Software Center long-term, so to fix it there, make sure that aptdaemon blocks session exit"? [13:58] didrocks: I just looked at the viewswitcher code and its in general a bit ugly and could do with some cleanup (all my fault). would something like "viewswitch.register_view" and some simple signals (selected, expanded) be ok? it seems like it would be a good idea to hide the gtktreemodel stuff as its not really releveant for most users of the ViewSwitcher class (i.e. the fact that its a treeview is just a implmeentation detail). what do you [13:58] think? === fta_ is now known as fta [13:58] mpt: yes [13:59] mvo, great, thanks [13:59] mpt: we should probably do both, block session exit and halt shutdown until the stuff is finished [13:59] mpt: for cases where the user uses stuff like "sudo halt" to halt the system [13:59] mpt: unattended-upgrades is a good pointer for him [13:59] mpt: it integrates a script like this (a upstart script) [14:00] mvo: this is a good idea. I think that if plugins can avoid playing directly with the model is a bad idea :) We just need for them to have a uuid for their entry (not related to what is displayed) in addition to name and icon, and some simple signal. [14:01] didrocks: yeah, I guess that can be a simple string that the we generate from the (plugin-name, name) ? [14:01] mvo: so, in my case, for instance, I show icons and hostname, but I can have more than one hostid for a hostname, so I should get that value when the selected signal is triggered (or just point to the right view) [14:01] mvo: also, I can add/remove some items during USC lifetime (what is doing my latest commit in OneConf) [14:01] mvo: plugin-name-name-id for me :) (see ^^ with hostname/hostid) [14:02] didrocks: ok, let me draft a interface for that [14:02] mvo: great, if I can help you, do not hesitate to ask me :) [14:10] didrocks: I created a ehterpad here http://openetherpad.org/uLbnSTxeFJ [14:10] didrocks: go wild there :) [14:10] mvo: on it, thanks :) [14:10] thanks! [14:13] mvo: testing new unity release, backport to lucid and on it in… let's say half an hour/45 minutes [14:14] didrocks: no problem, I have some test failures in python-apt to fix too [14:14] didrocks: just wanted to throw a skeleton out so that we have something to talk about [14:14] mvo, ok, I included that info in the message too, with links to the relevant branches [14:14] mpt: thanks! [14:39] hey, against which package should i file a bug, if an application "survives" a logout? banshee is still playing after I've logged out and logged in again. [14:40] the concerned software [14:40] k, thx === fta_ is now known as fta [14:48] seb128: hmm, current 2.31 gpm uses gsettings [14:48] pitti, we don't do GNOME 2.31 [14:49] ok; I wasn't sure whether we want to do some gsettings packages or not [14:50] depends [14:50] if the benefit is worth the work... [14:50] not so far; we can do cherrypicks [14:50] but that one seems a tricky one because it's likely to have keys shared over components [14:50] it ports from libdevkit-power to libupower-glib [14:50] but we can backport that as well [14:50] (next upower release will drop libdevkit-power) [14:50] ok [14:50] thanks [14:51] we try to avoid having shared desktop keys with gsettings and gconf clients [14:51] since there is no sync between those [14:51] so for now we only updates selected softwares, ie empathy [14:51] or gnome-calculator === almaisan-away is now known as al-maisan [15:06] hum [15:07] mvo, http://paste.ubuntu.com/462547/ [15:07] mvo, have you seen similar crashes? it's on current maverick there [15:09] seb128: let me check [15:10] mvo, https://bugs.edge.launchpad.net/ubuntu/+source/update-manager/+bug/604250 [15:10] Launchpad bug 604250 in update-manager (Ubuntu) "update-manager crashed with AttributeError in estimatedDownloadTime() (affects: 2) (dups: 1) (heat: 3286)" [Undecided,New] [15:10] mvo, it has been reported by somebody else so it's not only me ;-) [15:19] seb128: thanks, fixed [15:19] mvo, waouh, you rock as always, thanks! [15:23] mvo, I've changed the bug to fix commited [15:27] seb128: thanks, fix uploaded [15:28] mvo, ;-) [15:29] mvo: thinking about it, the view_id in my comment doesn't seem relevant for most of plugin I guess. I'll handle the dict on my side. I can't think about any other thing needed for the pane list [15:34] didrocks: thanks, so the view-manager thing looks ok? [15:35] mvo: yeah, sounds fullfill my needs at least and the one for your cases too, right? [15:36] mvo: I'm just wondering, as I'll refresh the list regularly as you do for channels, is it to the plugin to ensure that removing/adding the same view again still select the right item? === fta_ is now known as fta [15:37] didrocks: keep selected> not sure yet, I guess it should be done by the ViewManager, but I'm not 100% certain yet [15:37] didrocks: use-case> it should simplify the current code quite a bit, so it should be a good change [15:38] pitti, hum, seems the ddeb index is buggy [15:39] oh wow package summaries really suck don't they :) [15:40] some packages from the same source all have the same summary it seems :-/ [15:40] dobey, indeed... lots of those i think [15:40] mvo: sure, it would be good for you too :) I'm thinking about that view (https://wiki.ubuntu.com/SoftwareCenter?action=AttachFile&do=get&target=inventory-computer.jpg), do you think I just inherite from an existing one or start a new one? It has mutiple treeview (installed/removed/others) and I'm quite scary about the search integration TBH [15:41] pitti, http://ddebs.ubuntu.com/pool/main/libi/libindicator/ [15:41] i just ran update-manager and was like "wait, what am i updating?" [15:41] doesn't help that the package name is now [15:41] pitti, some of the debs are not listed in any index, neither the main one or the universe one [15:41] pitti, it seems it's binaries in universe from a source in main missing there [15:44] is the glib/gconf conflict fixed now? i've been holding back gconf since it broke [15:44] what conflicts? [15:45] there is no known conflicts [15:45] dobey, there was some issues with the gnome-shell ppa it seems [15:45] using that maybe? [15:45] no [15:46] there was a conflict with a man page [15:46] ok so we need details on the conflict [15:46] something to do with gsettings/dconf stuff [15:46] if you could copy the exact conflict line from apt that would be useful [15:49] trying to overwrite '/usr/share/man/man1/gsettings-schema-convert.1.gz', which is also in package libglib2.0-bin 2.25.9-1ubuntu3 [15:49] seems to not be in the glib2.0-bin package any more though, according to dpkg -L [15:49] hrmm [15:50] will try upgrading gconf2 again after the current update finishes running [15:51] dobey, sudo apt-get -f install [15:51] dobey, your libglib2.0-bin is outdated [15:51] i did that at the time, and it failed [15:51] dobey, sudo apt-get install libglib2.0-bin gconf [15:52] so i just installed the older gconf2 packages to get things going [15:52] but it looks like it installs ok now [15:53] i guess i ran an update at some point when the archive wasn't totally synced, to get that issue? [15:54] dobey, right and we forgot to use a replaces to handle the move nicely [15:55] dobey: update-manager> I have no strong opinions either way, there is a gconf key to switch to the old style [15:56] hrmm, well, need to reboot :) [15:59] seb128: ! [15:59] seb128: long time no see [15:59] mvo, have you seen this? https://code.launchpad.net/~ilidrissi.amine/software-properties/updates-redesign/+merge/29123 [15:59] re [15:59] mvo: did you saw my previous question? (approx 15 minutes before) about the paneview inheritence? [15:59] djsiegel, hey, how arre you? [15:59] seb128: I'd like for us to turn off the screen lock on resume by default. [16:00] +1 to djsiegel [16:00] mpt: no, I check it out after the call [16:00] * vish always the first thing i do on a fresh install [16:00] ok [16:00] djsiegel, hum, I think we had this discussion before [16:00] seb128: because it makes resume take about 3 seconds less [16:00] chrisccoulson, pitti: ^ [16:00] didrocks: no, can you paste it in again (in a call right now, sorry) [16:00] do you remember if we discussed this? [16:00] seb128: you've always had the discussion before! [16:00] sure, mvo: sure, it would be good for you too :) I'm thinking about that view (https://wiki.ubuntu.com/SoftwareCenter?action=AttachFile&do=get&target=inventory-computer.jpg), do you think I just inherite from an existing one or start a new one? It has mutiple treeview (installed/removed/others) and I'm quite scary about the search integration TBH [16:01] we did discuss it before at some point [16:01] djsiegel, not my fault if what ux guys see as annoyances are often a balance between security and usability ;-) [16:01] Yeah whatever. [16:01] lol [16:01] djsiegel, it also makes your system less secure [16:02] seb128: people can lock before they close it if they want [16:02] I don't like the idea that we are always locking the screen on idle, on screensaver, on sleep "for security" [16:03] well then you make suspend be 2 actions instead of one [16:03] yes, when you want it locked [16:03] you could change the default if you always want a lock [16:03] I'm not even sure how you suspend once it's locked [16:03] but users who don't want the lock get a better experience [16:03] I ran this by sabdfl and he is +1 on it. [16:03] at some point, the lock-on-idle and lock-on-suspend preference got decoupled, and we had a lot of users complain that when they enabled lock-on-idle in the screensaver preferences, their screen didn't lock on suspend [16:04] djsiegel, can we get a clear spec which defines the behaviour on all situations? [16:04] djsiegel, ie on user switching, on suspend, on hibernate [16:04] so we fixed that so that the preference applies to both suspend and idle, and we switched on lock-on-idle by default for security reasons [16:04] djsiegel, on manual screen locking [16:04] seb128: yeah, sure [16:04] djsiegel, and how we change from wanting to not lock to lock [16:04] djsiegel, thanks [16:05] djsiegel, we should probably have all those consistant and with one setting changing mode to lock to unlock [16:05] seb128: hmm [16:05] i'm surprised that locking affects resume speed so much though [16:05] lock on screensaver and lock on suspend could be two separate preferences for some people [16:05] chrisccoulson: I think there's some artifical sleep in there or something [16:06] we had that by accident and users got really confused [16:06] djsiegel, what about lock on user switch? [16:06] seb128: you mean the bug I reported? [16:06] dunno if you reported a bug, I know that's yet another case of "lock on..." [16:06] not sure if we want a screen with a list of "lock on..." options [16:06] or just having "lock in all cases or don't" [16:07] seb: https://bugs.edge.launchpad.net/ubuntu/+source/gdm-guest-session/+bug/600559 [16:07] Launchpad bug 600559 in gdm-guest-session (Ubuntu) "When screensaver lock is disabled, terminating a guest session resumes the parent session without asking for a password (affects: 1) (heat: 564)" [Undecided,New] [16:08] seems like the implementation is a bunch of spaghetti, interpreting the same gconf keys in different contexts [16:08] djsiegel, is that specific to the guest session? [16:08] right :-( [16:08] that's why I would like clear spec with all the case [16:08] seb128: no I think the account switch lock is reusing the screensaver lock! [16:08] rather than just tweaking one key which will have side effect [16:08] djsiegel, in the case of your bug report, the screen has to be locked regardless of whether you return to GDM or your session [16:08] chrisccoulson: isn't GDM the lock? [16:08] no [16:08] you wouldn't want a lock screen over GDM [16:09] djsiegel, no, your session will still be active on another VT [16:09] you can ctrl-alt-f [16:09] i could just switch VT from GDM ;) [16:09] you need the screensaver to lock the actual session [16:09] or anybody can use the keyboard to go to your session [16:10] ok, explain one more time please :) [16:10] When I switch user sessions, I am really switching to GDM on another vt? [16:11] explain what? I feel we have described lot of cases and are as confused as this whole locking story is [16:11] My session stays running on another vt with the screensaver lock? [16:11] yes [16:11] djsiegel, yes [16:11] the greeter screen is on one VT [16:11] and each user session has its own VT [16:11] the only way to protect the session is for the screensaver to lock it [16:11] changing user sessions or going to the user lists are only VT switches [16:11] so, when you said we need a lock at GDM, you meant a lock screen, locking my session, but not locking GDM, which happens to be running on another vt at the same time [16:12] we didn't say that gdm needs a lock [16:12] the user session needs gnome-screensaver to start locking on any context switch [16:12] ok, I was confused by "the screen has to be locked [if] ...you return to GDM" [16:13] ok, got it [16:13] I think we may want to disable lock on resume regardless if it's causing resume performance issues [16:13] Maybe we can fix the sleep though [16:13] do we want to lock the keyring then? [16:13] it does seem artificial [16:13] or do you want to let the keyring unprotected? [16:14] we should probably look at those performance issues before taking a decision like that [16:14] Well, what we want is fast resume, not 3 second resume [16:14] and we'd need to discuss such a decision with the security team anyway [16:14] well do you want your passwords to be protected on sleep? [16:14] I don't think the user will mind if the keyring is locked [16:14] or do you want anybody stealing your laptop having your password in clear [16:14] well it will in the sense you will have to enter your keyring password on resume [16:14] to connect to your im or wireless [16:14] seb128: immediately? [16:15] ah, ok [16:15] yes [16:15] bl8: ping [16:15] I see [16:15] so it sort of defeat the win [16:15] yep [16:15] do we even lock the keyring on suspend? [16:15] but at least you see your desktop state and not a black lock screen, but it's really all the same and we can do better [16:15] the other option is to not lock the keyring on suspend [16:15] i know we used to when the suspend requests were proxied through g-p-m...... [16:15] chrisccoulson, I think we do since gnome-screensaver unlock it [16:16] djsiegel, well at least people understand the "enter your password", they don't really understand the "enter your keyring password" and why it's displayed [16:16] hmmm, does gnome-screensaver actually lock the keyring? [16:16] djsiegel, ie they don't get they need that password to be able to read their im or wireless password in a secure way [16:17] chrisccoulson, I'm not sure what does lock it [16:17] yes, this is a separate issue that is solvable, I am just worried about the wait time added by the lock screen on resume, and also worried about asking for a password to resume [16:17] we can solve them in that order, I don't see any reason why the lock screen needs 3 seconds to show [16:17] seb128 - i have a feeling that nothing locks it right now [16:17] unless maybe it's going to disk or something? [16:18] djsiegel, it doesn't there [16:18] it would need debugging on why it does for you [16:18] chrisccoulson, that would be a bug [16:19] I've seen it on quite a few laptops. [16:19] With locking on, I resume, there's a pause, then the lock screen [16:19] With locking off, I resume and instantly see the desktop [16:19] it's been the case with all laptops I've tried [16:19] come to think of it, maybe even SSD too... === fta_ is now known as fta [16:26] djsiegel, is the desktop usable or do you just see the desktop displayed? [16:27] djsiegel, I think it's as slow but in your case you already have in the video the display you want to see [16:27] seb128: cannot test atm, maverick broke my suspend [16:27] so it's quite a nice user experience [16:27] it doesn't matter really, it feels fast [16:27] as long as you are trying to use it before it's ready [16:27] right [16:27] well I'm fine doing the change [16:28] but I don't want to tweak one key every second week because users get confused by some behaviour [16:28] I think we should think clearly about what we want in case of suspend, hibernate, lock screen, user switching, guest session [16:28] and specify the options to control these settings [16:28] ie have the behaviour we want spec-ed [16:29] otherwise we will keep have confusion on what settings do to each of those cases [16:29] and if that's the right behaviour [16:29] etc [16:29] djsiegel, ^ [16:41] seb128: right [16:41] we should do that, and that will likely involve some new code [16:41] to decouple currently tightly coupled settings [16:41] indeed [16:42] but I wonder whether we should just change the setting to get faster resumes for the time being, or make no change until we can fix it all? [16:42] mvo: I merged that code I sent you into a local branch of software-center - it works! [16:42] djsiegel, so changing from having the screen locking to have the keyring password prompt? [16:43] djsiegel, can I be nosy and ask what? [16:43] it does? [16:43] and471: / [16:43] ? [16:43] djsiegel, the patch [16:43] djsiegel, sorry I was thinking about something else, the code you sent mvo [16:43] and471: Ubuntu Software Center shows the oldest screenshot available for each package, and I patched it to show the newest one available... [16:43] djsiegel, woo! [16:44]