[00:08] RAOF: gds blew up [00:08] RAOF: and it stopped working [00:09] RAOF: rmmod psmouse; modprobe psmouse hath fixed it. [00:09] You mean g-d-s? Aaah. [00:12] RAOF: yes, yes I do [00:13] RAOF: details in #distro where I was chatting with kirkland [00:31] chmrr: sure, please send me an email or add a note about that on the blueprint, so I don't forget to ping you :) [00:34] Where can I find the blueprint? [00:35] chmrr: just a second [00:37] chmrr: https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-desktop-network-enhancements [00:42] cyphermox: Updated. Thanks! [01:40] c [02:12] does anyone know how i would go about making it so that pressing the power button didn't generate an X event (but continued to generate ACPI events for, e.g., apcid)? i'm open to either configuration or software patching [02:14] broder: You could probably do that by configuration by excluding the /dev/input/event? device that corresponds to your power button. [02:14] RAOF: and if i was interested in not hard-coding a specific device? [02:16] Add a udev rule that strips the ID_INPUT flag from devices whose DEVPATH includes LNXPWRBN? [02:16] that sounds exactly like my sort of solution :-D [02:17] although, would that keep acpid from catching the events as well? [02:17] Dunno. I'd presume that acpid wouldn't be looking for power button presses from an evdev device, though. [02:18] oh, is /dev/input specifically an evdev construct? [02:18] Yeah. [02:18] cool, i didn't realize that [02:19] i'll go experiment, then. thanks for the pointers [02:45] RAOF: 'The program 'gnome-settings-daemon' received an X Window System error. [02:45] This probably reflects a bug in the program. [02:45] The error was 'BadMatch (invalid parameter attributes)'. [02:45] RAOF: twice in one day. Win. [02:45] (Details: serial 79543 error_code 8 request_code 3 minor_code 0) [02:45] ' [02:45] (classic mode w/no effects) [02:48] lifeless: You might want to run g-s-d with --sync, attach gdb to it, and break on XError to find out where that crash occurs. === braiam_ is now known as braiam [02:49] Hm. Which raises the obvious follow-up: how can we more easily debug these things? [02:56] Starting program: /usr/bin/gnome-settings-daemon --sync [02:56] [Thread debugging using libthread_db enabled] [02:56] Program exited normally. [02:57] RAOF: does it /try/ to be difficult ? [02:57] RAOF: or was it written by e.g. lennart? [02:57] :/ [02:58] (3 times) [02:58] I think that's it trying to grab the dbus name, and being unhelpful about failing. [02:58] lifeless: --no-daemon, possibly? [02:59] will add that hte next time [03:02] RAOF: hmm...for debugging, how about some sort of protocol extension that lets you look up requests that triggered error events? [03:06] ok [03:06] so its spitting this out [03:06] bad event received, major opcode 34 [03:06] not crashing yet [03:06] A good first approximation might be to actually decode the request_code and error_code. [03:07] broder: But some sort of protocol extension like that should be relatively easy to hook up. [03:07] xtrace? [03:07] the idea would be that Gdk sets up the requisite connections in its error handler [03:08] bryce: xtrace is obviously the ultimate hammer. It'd be nice to have something between “gah, let's see if the code is doing anything obviously wrong” and “trace all X calls ever, so in case something breaks we can report useful info” :) [03:09] RAOF, oh definitely agreed. but for present bug sounds like xtrace is next step, barring that [03:10] uh oh, some little person is knocking on my door [03:10] :) [03:10] Quick! Cover all the power buttons! [03:10] i'd be willing to bet that for something like g-s-d, knowing the request that triggered the error would at least let you figure out which module was doing something stupid [03:11] Hm. Actually, gdk *already* has all the info it needs to print a more useful error message; it knows what request serial 79543 corresponds to, and it's got more context. [03:55] RAOF: The program 'gnome-settings-daemon' received an X Window System error. [03:55] This probably reflects a bug in the program. [03:55] The error was 'BadMatch (invalid parameter attributes)'. [03:55] RAOF: but it just exited [03:55] (Details: serial 62010 error_code 8 request_code 3 minor_code 0) [03:55] rather than letting gdb do $foo [03:55] backtrace from your debugger if you break on the gdk_x_error() function.) [03:55] [Thread 0x7fffef461700 (LWP 15772) exited] [03:55] [Thread 0x7fffdffbb700 (LWP 15777) exited] [03:55] Program exited with code 01. [03:56] 2 breakpoint keep y gdk_x_error [03:56] Bah! [03:58] As bryce said, running g-s-d under xtrace will definitely catch the failing request (at the cost of tremendous debug spew), but that loses interesting program context. [03:58] 0ok, that can be my next step [03:58] whats a request_code 3 ? [03:59] I'd need to dive through xlib to find that out. I don't know offhand. [04:02] (Details: serial 69137 error_code 8 request_code 2 minor_code 0) [04:02] http://www.rahul.net/kenton/xproto/xrequests.html [04:04] ok, its off running under xtrace [04:04] do you just need the end of it ? [04:05] Generally, yes. The bit that contains the request which fails and the bit which contains the error reply. Although more can sometimes be useful. [04:06] well, for now its just running in screen [04:06] so I'll get 100 lines or something free [04:15] RAOF: http://pastebin.com/dnxXZGcd [04:19] Hm. It looks like it's trying to set some properties on a window that it has recieved a DestroyNotify on. [04:20] Also, it looks like it's already swallowed a couple of errors from Get* on that window. [04:20] And it just hasn't set a error-handler for the Set* [04:21] I bet its chromium fail or something [04:21] tickling a latent bug [04:21] lifeless: That looks like there's some worth to the data in that pastebin; the next step is probably to attach it to a bug. [04:22] ubuntu-bug [04:22] ubuntu-bug $(dpkg -S /usr/bin/gnome-settings-daemon) [04:23] Actually, I think you can just ubuntu-bug /usr/bin/gnome-settings-daemon [04:23] incoming [04:26] https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/787316 [04:26] Launchpad bug 787316 in gnome-settings-daemon "BadMatch (invalid parameter attributes)" [Undecided,New] [05:18] Good morning [05:21] RAOF: ^^ [05:21] lifeless: Ta [06:19] RAOF: how do you break an X mouse grab ? [06:20] Killing the client which has the grab works. [06:23] if I knew [06:23] I would [06:23] all I know is: [06:24] - I can alt-tab and switch virtual desktops [06:24] - I can't maximise or minise windows [06:24] my normally autohide panel is stuck visible [06:25] * lifeless pkill gnome-panel [06:25] seems to work [06:25] \o/ [06:25] Heh. [06:25] so, consumer ready? [06:26] Obviously not. [06:26] :p [06:27] something is seriously whack here [06:27] g-s-d just went awol again [06:31] monitus regiminis fenestrae: GtkMenu failed to grab the pointer [07:12] pitti, hey, I'm doing an MIR for lightdm, should I add that to the desktop seed to pull it into main? [07:15] robert_ancell: yes, you can do that already [07:15] robert_ancell: it won't actually get effective until promotion, but at least it will appear in component-mismatches [07:15] pitti, ok. I guess there will be a race for which one is active when that occurs though [07:16] in the old days we had an /etc/default/ file which one was the default dm [07:16] with debconf integration [07:16] but I think that's gone at least for gdm? [07:17] robert_ancell: so perhaps for now it should Conflicts: x-display-manager as well, to have only one? [07:17] It appears to be /etc/X11/default-display-manager, but I think it's the first one that installs that claims it. There is a debconf question when you install the second one, don't know what the automatic response to that is on a CD build [07:17] ah, right [07:17] so it is safe to have both installed, but I don't know which one will start up [07:17] [ ! -f /etc/X11/default-display-manager -o "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm" ] || { stop; exit 0; } [07:18] ^ in /etc/init/gdm.conf [07:18] I matched that in lightdm.conf [07:19] apt-get install lightdm -> gdm is still the default in debconf, I suppose it reads the existing file [07:19] robert_ancell: for CD builds I think we should drop gdm from the seeds [07:19] and only install one [07:20] no point in instlaling more than one by default [07:20] of course, I'm just wondering when is the correct time to drop GDM from the seed - as soon as lightdm achieves MIR? [07:25] robert_ancell: yes, I think so [07:25] robert_ancell: btw, I just tried lightdm, and it starts classic even though the session said "ubuntu" [07:25] pitti, which version? [07:25] I suppose that's because some of didrocks' magic script check $GDM_SESSION or soimilar? [07:25] it used to do that, but mine is working now [07:25] 0.2.3-0ubuntu2, what is in oneiric [07:26] ah, I just uploaded 0.3.5, please try that [07:26] ah, will do [07:26] pitti: I think that is more robert_ancell telling us his desktop preference...shh...we won't tell... [07:26] :) [07:26] yes, you're all now forced to use classic forever. mwahahaha! [07:27] jasoncwarner: btw, you are the approver of https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-screensaver [07:27] jasoncwarner: was that deliberate? [07:27] no, rpobably a mistake.... [07:28] just changed to you, I mean...better ot have someone approving that has a clue ;) [07:29] ok, queueing for review then; I wasn't sure whether you wanted to sign of the general approach [07:37] good morning everyone [07:43] hey chrisccoulson_ [07:44] hi pitti, how are you? [07:44] quite fine, thanks! [07:44] good :) [07:44] and hungry, high time for breakfast -- gosh, 1.5 hours for morning email only :/ [07:44] bbl [07:54] good morning [08:30] bonjour didrocks [08:31] guten morgen pitti, how are you? [08:31] didrocks: I'm great, thanks! how about you? [08:32] pitti: I'm fine :) almost finished the gnome-session update/merge which was kind of a PITA ;) [08:32] I bet [08:33] pitti: so, no more box at home after this week-end? [08:33] or do you follow the rule "there is always one more box to unpack"? :) [08:34] didrocks: oh, still 8 boxes left, and several sacks with clothing; we need to wait until our shelf system gets delivered [08:34] (and the couch, and wardrobe, etc.) [08:35] oh, you bought a lot of new furnitures? [08:35] yeah, we only took very little from our old flat, most of it was really old and desperately waiting to be replaced :) [08:35] so it was the right moment to do it, right :-) [09:08] morning everyone [09:11] morning [09:18] hey rodrigo_, how are you? [09:18] hi didrocks, I'm fine thanks, and you? [09:19] rodrigo_: I'm good, thanks! Working from the balcony since last week. Less stress :) [09:20] didrocks: oh, that sounds nice as well [09:22] didrocks, heh, good weather then? [09:24] pitti: rodrigo_: yeah ;) it's heading south (so can be a little bit warm sometimes) and not on the street side. My neighbours are just trees in front in me ;) Julie has made some kind of zen ambiance as well: http://latolo.didrocks.fr/post/2011/04/10/un-jardin-zen-sur-mon-balcon-%3A-la-presque-fin [09:25] * rodrigo_ thinks of didrocks in a yoga position while compiling stuff :-) [09:25] hey rodrigo_ pitti [09:25] lut didrocks [09:25] bonjour seb128 [09:25] rodrigo_: heh, that's not that far from the truth :-) [09:25] salut seb128, ça va? :) [09:25] didrocks: oh, nice [09:26] pitti, screensavers "hacks" are the effects you can select in the gnome-screensaver-preferences dialog [09:26] i.e the things rendered on the locked screen [09:26] I could actually work in the garden as well, but I think it'd be a lot less comfortable (screen, chair, keyboard) [09:26] didrocks, ah, you're lucky you have a roof, on my balcony there's not (last floor) so all the sun gets direct so it's hard to work there during sunlight [09:26] hey seb128 [09:26] seb128: ah, I see [09:26] pitti, I will update the spec to address your comments [09:26] didrocks, you do yoga? [09:26] seems "hack" is the official word for those but it confuses a lot of people ;-) [09:26] rodrigo_: yeah, but you have the advantage to be at last floor (I'm on 2nd on 3, which is not so bad) [09:27] didrocks, yes, during the evenings, my balcony is great [09:27] rodrigo_: no, but sometimes I should when this ****** of patch doesn't want to compile :-) [09:27] but now it's starting to be too hot to work there [09:27] didrocks, :) [09:29] btw, how do you specify an optional Build-Depends? haven't been able to find any doc about how to do it [09:30] rodrigo_, bug #786899 seems similar to bug #786417 which has a patch and has been forwarded to debian [09:30] Launchpad bug 786899 in gnome-settings-daemon "package gnome-settings-daemon 2.32.1-0ubuntu13.1 failed to install/upgrade: trying to overwrite '/usr/share/gnome-control-center/keybindings/50-accessibility.xml', which is also in package gnome-control-center-data 1:3.0.1.1-1ubuntu1~natty1" [Undecided,In progress] https://launchpad.net/bugs/786899 [09:30] Launchpad bug 786417 in gnome-control-center "package gnome-control-center-data (not installed) failed to install/upgrade: trying to overwrite '/usr/share/gnome-control-center/keybindings/50-accessibility.xml', which is also in package gnome-settings-daemon 2.32.1-0ubuntu13.1" [Medium,Confirmed] https://launchpad.net/bugs/786417 [09:31] rodrigo_, there is no "optional" [09:31] seb128, ah, then that's why I didn't find anything then :) [09:31] build-depends are installed [09:31] seb128, so, it's about the tracker-dev dep in brasero, so do I just remove it then? [09:31] what would an optional build-depends be? something installed or not following the moon or something? ;;-) [09:31] yes [09:32] ok [09:32] it doesn't prevent people to do a local build to install it [09:32] but if we want to use it we should promote tracker to main [09:32] which I'm not sure we want to do, we have enough to do already [09:32] yes, and little space :) [09:34] rodrigo_, btw did you see the bug references I copied before? [09:34] seb128, yes, applying the patch right now [09:34] rodrigo_, is a g-c-c update coming today? [09:35] upstream release you mean? [09:35] yes [09:35] you might maybe wait for the update to do an upload [09:35] no need to do 2 uploads when you can batch things in one [09:35] yes, I was going to do it yesterday, but my inet was flaky, so just forgot to do it in the evening [09:35] yes [09:35] g-s-d needs to be updated in oneiric as well [09:35] yes, doing that also [09:36] gasp, i should not have rebooted. oneiric is (almost) unusable now. [09:40] didrocks, can you sponsor evolution-exchange if you have time? [09:41] is libgconf2-dev still a valid build-dep in oneiric? [09:41] yes [09:41] https://launchpadlibrarian.net/72317499/buildlog_ubuntu-oneiric-amd64.chromium-browser_13.0.774.0~svn20110524r86385-0ubuntu1~ucd1_FAILEDTOBUILD.txt.gz [09:42] it's deprecated and we are porting things away from it but it didn't change [09:42] uninstallable [09:42] it means it can't be installed, which usually means one of the depends is not installable [09:42] but apt is not doing a great job at telling you why [09:44] fta, gconf2-common : Depends: dbus but it is not going to be installed [09:44] dbus : Depends: netbase (>= 4.45ubuntu3) but 4.45ubuntu1 is to be installed [09:44] ah, that also happens locally for dist-upgrade [09:44] it's a dbus bug [09:45] https://launchpad.net/ubuntu/+source/netbase/+changelog [09:45] netbase is at ubuntu2 [09:45] right, the dbus depends is wrong [09:49] seb128: sure, doing that in a few [09:49] thanks [09:49] seb128: want me to fix, or are you on it? [09:49] didrocks, thanks [09:50] pitti, if you want to fix it please do, I'm catching up with some emails and updating the screensaver spec [09:50] at it [09:50] danke [09:53] my desktop (backgroup) is no longer repainted, and my (nautilus?) files/folders on the wallpaper are gone too, known? [09:53] (backgroud) [09:53] grr, +n [09:54] here as well; I think g-s-d and nautilus aren't in agreement who paints the wallpaper, or it didn't import my gconf setting properly? [09:55] although the latter seems to have worked [09:55] $ gsettings get org.gnome.desktop.background picture-uri [09:55] '/home/martin/download/digitalblasphemy/worldsedgewinter11280.jpg' [09:55] that's right [09:55] so I guess it's g-s-d and nautilus both thinking "that other thing will render it"? [09:56] fta, bug 784209, the assignment to unity-2d is wrong though but I don't know which package is to blame. [09:56] Launchpad bug 784209 in unity-2d "Background fails to redraw" [High,Confirmed] https://launchpad.net/bugs/784209 [09:56] good morning desktop people. Someone noticed that this particular string's translation is not loaded on a running system: https://translations.launchpad.net/ubuntu/natty/+source/gnome-system-tools/+pots/gnome-system-tools/nl/+translate?batch=10&show=all&search=can+change+anything+on+the+system - it seems to come from a .conf.in file. Does anyone happen to know if this this a new type of format, or just a plain configuration text file? [09:57] pitti, fta: dconf-editor -> org.gnome.desktop.background picture-uri [09:57] set that and draw-background [09:57] seb128: see above; the setting seems correct to me [09:57] $ gsettings get org.gnome.desktop.background draw-background [09:57] true [09:57] pitti, no, it's a path not an uri you have [09:57] should be file:/// [09:57] oh [09:57] seb128: I didn't set that manually, it was from auto-migration [09:58] pitti, right, http://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=81e581e67962ecf290f886afd2fbf5767f1970ad [09:58] and I set the original one from the gnome 2 background conf dialog [09:58] $ gsettings get org.gnome.desktop.background picture-uri [09:58] 'file:///usr/share/themes/Adwaita/backgrounds/stripes.jpg' [09:58] pitti, they stopped migrating it now [09:58] but i have no such file [09:58] no Adwaita at all [09:58] pitti, the scripts can only do value copies, they can't do tweaks and the sementic changed from a path to an uri [09:59] pitti, which is a bit unfortunate [09:59] we will probably need to fix it in some way but for now "known bug" [09:59] seb128: so the better solution would be to check if it's not an URI in g-s-d, and convert it to an URI there? [09:59] rodrigo_, ^ what do you think? [09:59] until the next LTS at least [10:00] it's "file://" + abspath(current_value), nothing more, right? [10:01] pitti, I've added a WI to https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-gtk3-gnome3 [10:02] cheers [10:02] pitti, right [10:02] it just can't be done from the .convert so it needs code [10:02] oh, added file://, and it immediately works, yay [10:02] wow, now an empty desktop pretty much exactly looks like natty again :) [10:03] seb128, pitti: yes, probably we should check ad convert to an uri if it's just a path [10:03] rodrigo_, do you want to take over the WI? [10:03] fta, you need gnome-themes-standard installed for that file [10:03] seb128, yes [10:03] rodrigo_, thanks [10:04] rodrigo_, oh, installing. why isn't it a dep? [10:04] fta, bug I guess :) [10:04] good, it worked [10:04] pitti: does that mean you have a workaround for people with broken settings? :-) [10:05] i have a blue/grey desktop now :P but at least i can work [10:05] pitti, you can get the icons displayed with show-desktop-icons = true in the same schemas [10:05] lool: see above, we'll add a migration to the code, for now you can just prepend a file:// [10:05] seb128: it's already the case here; I'm not sure whether I enabled it manually, but I don't remember doing so [10:05] rodrigo_, fta: not sure if we want to install gnome-themes-standard or just tweak the default value to be one of our themes [10:05] yes, probably better [10:06] pitti: well I did get "file://" in the output of gsettings get org.gnome.desktop.background picture-uri, but it was a missing file [10:06] pitti, it's false by default, you probably tried to tweak it to get your background back ;-) [10:06] but all settings seem broken, not just background [10:06] seb128: well, I want my files/folders back :) [10:06] lool, you get a different bug from others then ;-) [10:06] like icon theme [10:06] seb128: what I did was to enable "home is desktop" in gnome 2 ages ago, and a week or two ago I re-ran the gsettings migration [10:06] pitti, well, run nautilus? [10:07] at least I get proper desktop paints again [10:07] seb128: sorry, misunderstanding; it's already starting by default for some reason, just with background icons AND a window (it should just be the desktop) [10:07] pitti, with org.gnome.desktop.background show-desktop-icons on you don't get your icons after running nautilus? [10:07] oh ok [10:07] known issue [10:08] it's the "Get nautilus to install an autostart desktop conditional on the gsettings show icons key (upstream said they would welcome a patch for that):" on the spec [10:08] pitti, I think it's starting now because didrocks didn't upload the new gnome-session yet [10:08] ah there aren't any separate capplets utilities anymore [10:08] ah [10:09] lool, no, they are control-center-panels now [10:10] pitti, so nautilus is still a "required component" and run on start which gives you that dialog, once we update gnome-session it should not start at all which is what the workitem is about [10:10] they dropped it from the required components [10:10] since nautilus doesn't start in GNOME3 [10:10] right [10:10] what will be fixed today then :) [10:10] let's call it "changed" :) [10:11] heh [10:11] I'm not sure what is better [10:11] a lot of people use their desktop as their file manager, which is arguably a bad habit, but presumably hard to get out of [10:11] well, we should at least have the autostart conditional on the gsettings key [10:11] hmm how does one change the gnome theme or icon theme? I can't find it in the gnome-control-center settings [10:11] so people who turn desktop back on would get nautilus to start [10:12] lool, gnome-tweak-tools [10:12] do we have teh "home" nautilus icon in the launcher by default? [10:12] I don't, but I customized mine a lot [10:12] lool, "design decision" from GNOME, changing theme is not something their designer recommend... [10:12] pitti, no, we have a clean desktop by default [10:12] hmmm [10:12] i.e only devices and your own icons [10:12] no computer, home or bin [10:13] ah, we do [10:13] seb128: I mean in the launcher as a starter [10:13] gnome-tweak-tool crashes on start :-/ [10:13] right now, I put nautilus back for unity and unity-2d, but not for the other [10:13] it's in the guest session, so I guess "yes" [10:13] should I remove it definitively then? [10:13] but eww @ guest session, background is totally broken [10:13] we tried removing the file manager in UNE maverick, we got bad feedback [10:13] pitti, we do [10:14] you move windows around, and the background just keeps old images [10:14] seb128: with having that there's a better justification of not starting it by default [10:14] (just catching up on the conversation) [10:14] but still, it seems quite a waste to not do something useful with the large background area ;) [10:15] didrocks: I have no strong opinion either way myself [10:15] pitti, guest session -> do you have a correct uri for the background or do you run into the bug fta mentioned? i.e the default being an image from gnome-theme-standard which is not installed [10:15] seb128: ah, I don't have gnome-theme-standard installed [10:15] (that's the upstream settings, we need to bring back ubuntu values) [10:15] so it's probably that [10:15] we should just tweak the gsettings value to be the ubuntu background [10:15] might also explain why the indicators are almost invisible [10:16] where is gnome-tweak-tools? [10:16] so, so all "known" for now [10:16] fta, in universe [10:16] E: Unable to locate package gnome-tweak-tools [10:16] fta, gnome-tweak-tool [10:16] sorry for the typo before [10:16] oh [10:16] thanks [10:17] lool, do you have details on the error, a stacktrace? [10:17] crashes here too [10:18] seb128: http://paste.ubuntu.com/612211/ [10:19] oh, it depends on gnome-shell [10:19] My background is also ugly, I have to hold gnome-settings-daemon back to make it work well. Anyone else with the same issue and/or a fix? [10:19] (the discussion above seems to be regarding this) [10:19] seb128, hmm, i forgot to add it :\ [10:19] cdbs, read the previous half an hour backlog [10:19] so in dconf-editor, I see all settings pointing at Adwaita [10:20] lool, right, that's the upstream GNOME3 theme, it's also the only gtk3 theme we have now [10:20] seb128: oh so it is normal that I see everything with a bogus theme [10:20] lool, yes [10:20] seb128: Ok :) [10:20] we have no gtk3 theme yet [10:20] seb128: So, installing gnome-theme-standard will fix it by making Adwaita the default theme? [10:21] cdbs, not really but I don't feel like rewritting what is in the backlog, just read it? [10:21] cdbs, you have a gsettings background key to change [10:21] cdbs: Check whether the background is set properly [10:21] cdbs: You can check whether gsettings get org.gnome.desktop.background picture-uri returns an existing file:// URI [10:21] pitti: yeah, the launcher has the home icon and will still have it in oneiric as the first element (still catching up on IRC, sorry for the lag ;)) [10:22] thanks lool and seb128, I managed to get to the right part of the backlog [10:23] pitti, so https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-screensaver I'm not sure about the "[smspillaz] help getting a list of requirements and drive contributors:" [10:23] seb128: you mean what it was about? [10:23] pitti, https://blueprints.launchpad.net/ubuntu/+spec/security-o-compiz-screenlocking somewhat overlap with the spec [10:23] pitti, right [10:24] pitti, I've adressed the other points I think [10:24] pitti, but the outcome was basically "locking should be done in the compositor, i.e compiz, but if that doesn't happen this cycle we will ship gnome-screensaver 3 with hack support restored" [10:25] lool: Also do you know how to set Adwaita as the default GTK3 theme as right now there's no Ambiance for GTK3? [10:25] seb128: ah, that sounds like a better decision than the fuzzy ones that are currently in the spec [10:26] pitti, apport-retrace complains about a lot of missing -dbgsym & :i386-dbgsym [10:26] cdbs: dconf-editor from dconf-tools seems like the easiest way to do it right now [10:27]