[00:32] Oh, damn. Alioth's broken again, isn't it. [00:33] * RAOF gardens the SRU queue instead. [00:40] lol [00:53] Changing my boot sequence by means of installing an SSD has exposed an absolutely superb bug - hardware initialisation on this hybrid laptop is not deterministic, and the radeon card comes up first now. Plymouth eagerly throws up the cryptsetup prompts on fb0, provided by radeon. [00:54] There's only one problem: the radeon card isn't connected to any outputs, so those cryptsetup prompts sit happily in VRAM :) [00:56] lol [00:57] Thats awesome~! [01:05] The kernel knows about this, too; once i915 is loaded, the kernel goes ‘Oh, whoops. The primary console's actually on fb1, chaps, as it's conceivable that the user might be able to see it’. [01:05] RAOF: \o/ [01:05] Not in so many words, though, because kernel developers are uncouth oafs! [01:06] lol [01:06] RAOF: ITYM uncouth aufs [01:07] :P [01:07] TheMuso: what sound do you get for :P ? [01:07] :P [01:08] lifeless: Literally how it is written. [01:08] colon-P? [01:08] Yes. [01:08] There's a joke in there, if you've got the scope to find it. [01:09] groan [01:09] RAOF: In other news, I think I had a GPU lockup earlier with nouveau, to the point where speech was still reading activity in the channel, but I got no keyboard and no mouse, and no changes on the screen. I couldn't even switch to a VT... [01:10] TheMuso: Any trigger you could identify? [01:11] RAOF: No, this is the first time this has ever happened, I was just in a terminal using irssi. Didn't bring up anything in particular, no Unity features fo any kind. [01:12] Ok. I think our ability to debug unreproducible nouveau hangs is somewhere between slim and none; if it happens again please pipe up, but I'm not sure I can do anything about a once-off. [01:13] * TheMuso nods, just thought I'd let you know. [01:15] Thanks. [01:16] Probably won't happen again, since this is the first time in weeks that I have had one. [01:16] I.e the first time since I ever used nouveau with the NVIDIA GPU. [01:17] That's nice to hear :) [01:20] Yeah. [01:23] RAOF: any idea about my issue? [01:24] Sorry, that's dropped out of my context. [01:24] What was it again? :) [01:43] very quiet weekend it's been === micahg_ is now known as micahg [01:50] micahg: What was your problem again? [01:51] RAOF: external monitor won't stay on after upgrade to precise [01:52] Ok. It's a DisplayPort monitor, I take it?+ [01:52] * micahg isn't sure [01:52] What does the plug look like? :) [01:52] DVI [01:53] * RAOF is surprised. [01:53] Do you have a bug report with more details, or shall I quiz you here? [01:53] no bug report yet [01:53] just upgraded 2 hours ago [01:54] micahg: i'd love to know the circumstances of your confusion :) [01:54] oh, I'm not familiar with X terminology [01:54] ahh [01:54] displayport is just another connector type [01:55] micahg: What's the GPU? Intel, ATI, nVidia? [01:55] nVidia [01:55] And we're talking about the nouveau drivers, not the nvidia binary drivers++ [01:55] ? [01:55] GeForce GTX 460M [01:55] binary nvidia [01:55] Poot. [01:56] am I better off with nouveau? [01:56] Maybe. [01:56] There are definitely tradeoffs involved. [01:56] depends on how you feel about global warming :) [01:57] is there an easy way to make that switch? [01:57] micahg: jocky is probably the easiest way [01:57] Right. Nouveau doesn't do reclocking (although this is now enabled in git). If your BIOS brings the card up in the lowest power state (most do) then you'll have reasonable power consumption. If your BIOS brings up the card in the high-power state it'll eat electrons like candy. [01:57] 'additional drivers' in the system settings [01:58] umm, jockey shows me 2 proprietary drivers :( [01:58] Yeah. “Additional drivers” is easiest. You can also go manually fiddling around with update-alternatives if you want. [01:58] micahg: disable them!!! [01:58] Disabling the proprietary driver will get you to the default (ie: open-source nouveau) [01:58] (says the free-software muse sitting on your left shoulder) [01:59] micahg: other one is... wifi? [01:59] it tells me it's required if I want to run unity :) [01:59] It's lying. [01:59] micahg: that's probably not true [01:59] We might want to reword that :) [01:59] wifi is enabled, but not active [01:59] although your unity experience will likely suffer [01:59] * micahg has been using unity-2d anyways, so not likely :) [02:00] Maybe. You'll find that smspillaz runs nouveau in part because he hits fewer 3D bugs on it :) [02:00] * desrt notes that the jockey UI looks quite ugly when no proprietary drivers are installed/needed [02:02] * micahg tries a reboot [02:02] Yup, that's easiest [02:05] jockey could use some usability love [02:08] * RAOF notes the ominous lack of micahg [02:08] lol [02:09] micahg: welcome back, we were worried [02:09] * desrt files scathing UI review against jockey [02:09] bad jockey [02:09] umm, well, got a low graphics warning [02:09] seems fine now, I can see the screen, but it still won't stay on [02:10] It turns on, displays something, and then turns off after a while? [02:11] yeah, if I power cycle it, it shows the screen and then goes black [02:12] That's… [02:12] Um. [02:12] *cough* hardware issue *cough* [02:12] Does the screen give a warning message? [02:13] There would seem to be two obvious options here: (1) the display clocks are drifting, and after a while they've drifted too far for the display to sync, or (2) for no obvious reason both drivers are sending DPMS off requests. [02:14] no warning issue, this happened right after I upgraded [02:14] Can I get an Xorg.0.log please? [02:14] And, hey, lets throw in a dmesg for good measure. [02:17] RAOF: e-mailed [02:22] Hm. There's nothing particularly odd there, apart from the bit where it changes from cloned → spanned → cloned → spanned. [02:22] I"m going to try in anotherWM [02:23] brb [02:23] Fair call. [02:36] ok, I don't know where my VGA cable is right now so I can test this with another machine [02:37] I'll have to resort to single monitor mode until I find it I guess [02:38] The other thing to check would be that the kernel framebuffer is cloned across the monitors. [02:38] same thing in Xubuntu with metacity and unity-3d as well [02:38] But this is not exactly a common failure mode :) [02:38] how do I do that? [02:39] Boot into recovery mode, but remove the “nomodeset” from the kernel command line. [02:39] That should get you the kernel VT, spanned across both monitors. [02:39] why do I need recovery mode for that? [02:41] Just to stop X starting. [02:42] That'll remove any possibility of the X driver sending a DPMS off signal or something. [02:42] then how can I test it? [02:42] The kernel should bring up *both* displays, cloned. [02:42] ah, ok [02:42] brb [02:42] RAOF: i don't recall if we've had this conversation before [02:43] RAOF: is there a way to use xinput to change my laptop's trackpad into an absolute-movement touch device? [02:43] I don't think we've had that conversation before, and I don't *think* so. [02:44] * desrt installed some weird evdev-consuming driver once that did something like this [02:44] it was pretty flaky, though [02:44] Yeah, with uinput you could do that. [02:45] pull the evdev events out of the kernel, feed them back in after flipping the absolute bit. [02:45] Huh. You could also do that with XTest if you felt the need. [02:45] desrt: Need to do some testing of absolute devices? [02:45] RAOF: i'm trying to test the gtk multitouch branch [02:46] after some recent X updates it looks like it compiles at least [02:46] Yeah, the Xserver 1.11 transition included the 1.12 input stack, ie: Xi 2.2 ie: multitouch. [02:46] Which is what that branch will have been written against. [02:47] it was missing some constants in the headers for a while [02:47] so the thing compiles now, but it appears not to allow me to interact with my trackpad in any useful way [02:47] You were seeing the prototype, Ubuntu-only, multitouch protocol. [02:47] Huh. [02:47] Oh, yeah. [02:48] synaptics is currently not doing multitouch - Chase is on it. [02:48] ah. that'll explain it [02:48] meanwhile i have no way to test :) [02:48] maybe i should throw precise on my exopc [02:48] Yeah. [02:49] If that uses evdev it should multitouch (I believe) [02:49] it works on fedora [02:49] there's a reasonable chance that this branch could land this cycle [02:49] so i want to make sure that doesn't cause any crisis on ubuntu [02:49] The multitouch does? Then it'd work on Ubuntu, too. === fenris is now known as Guest45833 === Guest45833 is now known as ejat [04:56] does anyone have a concept of how stable precise is in terms of server-side? [04:56] like, i guess there may be a new kernel or something coming [04:57] but presumably not major new versions of core system components [05:30] Good morning [05:32] pitti: hello [05:32] good weekend? [05:33] pretty relaxed, yes; and you? [05:33] pretty decent. saw lots of old friends. ate too much, i think. [05:33] Morning pitti. [05:33] hey TheMuso, how are you? [05:34] pitti: Not too bad thanks, yourself? [05:34] TheMuso: pretty well, thanks! [05:56] hum [05:57] launchpad email appears to have become useful while i wasn't looking [06:00] Ha! [06:00] relatively useful? [06:01] you used to get emails from every single event that was vaguely related to any team that you were on and the only way to stop them was to leave the team... [06:01] it still sends out a lot of unwanted ones, but for bug mail they are quite useful indeed [06:01] it seems to only send me mails that are actually relevent to me now [06:01] desrt: you can configure it a lot more these days, too [06:01] * desrt had redirected all launchpad emails to his spam folder for some time [06:02] only looked now to find out that it doesn't send nearly as many as it used to === fenris is now known as Guest67783 [06:44] robert_ancell: hey Robert, how are you? [06:45] pitti, good [06:45] robert_ancell: do you know what creates /etc/lightdm/lighthdm.conf? Is that only ubiquity? [06:45] I don't see anything in lightdm's postinst for this [06:45] pitti, yes, it should be that way now [06:45] robert_ancell: i. e. if it does not exist at all, lightdm still works [06:46] robert_ancell: I want to tackle bug 854431 now [06:46] Launchpad bug 854431 in lightdm "GDM automatic login is not transitioned to lightdm automatic login" [High,In progress] https://launchpad.net/bugs/854431 [06:46] right [06:46] robert_ancell: i. e. if lightdm gets installed during upgrade, there will be nothing writing the conffile [06:46] robert_ancell: so if it's not there, I'll create one based on gdm custom.conf [06:47] pitti, yes I think that's correct, but you might want to confirm with didrocks as he did a lot of work in that area [06:47] robert_ancell: I took that bug from you, if that's alright with you? [06:47] (unless you want to work on it today) [06:47] pitti, I never complain if people take my bugs :) [06:47] but I'd like it to be in a2 [06:51] greeter-session=unity-greeter [06:51] user-session=ubuntu [06:51] robert_ancell: ^ are these two internal defaults? [06:51] robert_ancell: or do I need to set them if lightdm.conf exists? [06:52] robert_ancell: i. e. would it be better to set them or should it only have autologin-user= ? [06:53] pitti, from debian/rules: dh_auto_configure -- --with-greeter-user=lightdm --with-user-session=ubuntu [06:53] I'm trying to work out what sets unity-greeter in there... [06:53] robert_ancell: well, it needs to do something sensible if there is no lightdm.conf at all, so I guess it's ok [06:53] robert_ancell: that's in unity-greeter.postinst [06:53] pitti, ah right, it's done by /usr/lib/lightdm/lightdm-set-defaults in the unity-greeter postinst [06:53] /usr/lib/lightdm/lightdm-set-defaults --keep-old --greeter=unity-greeter [06:55] right, so that just needs patching to handle the autologin user [06:55] robert_ancell: I'll add autologin support to lightdm-set-defaults upstream and backport it [07:40] good morning [07:41] bonjour didrocks [07:41] ca va? [07:41] guten morgen pitti! ça va bien, et toi? :) [07:41] je suis bien, merci! [07:47] didrocks: "Make some promotion on user test cases once the tools are ready" (amber graner), do you happen to know whether this happened? [07:48] pitti: no, it didn't. I warned her that she can do some in uwn [07:49] didrocks: ok, thanks [07:51] didrocks: for the tarmac integration, would you call this done now? (description is fuzzy), or do you plan to do more? [07:52] pitti: I wanted to add more at first, but it's a little bit difficult to progress on it right now socially speaking… [07:53] didrocks: at least it seems to do its main job now? [07:53] pitti: yeah, it does [07:54] didrocks: so, perhaps we should call it done now, and you add a new WI for beta-1 with a more specific name if you want to add something? [07:54] pitti: oh, you are speaking about the autopilot? [07:54] or the "additional tarmac facility" [07:54] "Help on the tarmac autopilot integration" [07:54] pitti: no, this one is blocked. I tried to bring the subject back on the table twice [07:54] but no reaction from the third involved party [07:55] so I would say "blocked" on my side [07:55] didrocks: ok, updating status and moving to b1 [08:11] rodrigo_: good morning, how are you? [08:11] hi pitti [08:12] rodrigo_: would it help you if I upload packagekit with the new LANGUAGE_SUPPORT enum backported? [08:12] rodrigo_: I also did a few other fixes upstream which make "pkcon what-provides" work on the command line, which makes testing easier [08:12] pitti, yes, i already have it on my jhbuild setup, but yes, do it, it will be helpful [08:13] I will push my g-c-c branch later today, just a couple things to finish [08:13] rodrigo_: I haven't implemented it in aptdaemon yet, as glatzor wanted to add plugin support first [08:13] rodrigo_: but I wondered whether you actually test against packagekit itself, or aptdaemon-pkcompat? [08:14] pitti, since I hadn't finished it, I was just compiling against my PK branch [08:14] rodrigo_: ok, that's fine [08:15] rodrigo_: are you using the aptcc or the apt backend? [08:15] rodrigo_: as the apt backend currently just crashes if you try WhatProvides(); I fixed that in trunk, too, and will backport it along [08:16] pitti, hmm, aptcc [08:17] rodrigo_: ok; we can't really implement it there, I think glatzor wants to switch back to "apt" as default [08:17] pitti, hi [08:17] hey tkamppeter, guten Morgen [08:18] tkamppeter: FYI, I did a few changes to cups and cups-filters, but can't push my branch (alioth is down again) [08:18] tkamppeter: if you want to work on it, please ping me, I can put it on LP [08:19] pitti, why did you change the milestone of the cups task in bug 885324? I have fixed this. [08:19] Launchpad bug 885324 in imagemagick "Completely replace lcms1 by lcms2 in Ubuntu" [Undecided,In progress] https://launchpad.net/bugs/885324 [08:20] tkamppeter: hm, cups still depends on liblcms1 [08:20] tkamppeter: and today is alpha-2 freeze [08:20] tkamppeter: oh, it's in cups-filters now, I see [08:20] pitti, what makes cups depending on liblcms1? [08:21] tkamppeter: that was still -15, sorry [08:21] I'll update the bug [08:21] pitti, already done. [08:21] tkamppeter: ah, you already did; moved back the milestone [08:22] rodrigo_: btw, I had to "git merge master" in your branch to build it (failed on wacom stuff) [08:22] then it worked fine [08:24] pitti, oh, already did it over the weekend [08:24] pitti, did you push? [08:24] rodrigo_: no, just locally for testing [08:24] ok [08:25] I really don't want to mess up your branch :) [08:25] :) [08:28] rodrigo_: BTW, does that automatically configure the default ibus module? [08:28] language-selector still has an explicit combobox for this [08:28] but I don't know enough about this to say whether it should be there or nor [08:29] Chinese people tend to use different modules, though [08:35] pitti, hmm, not sure [08:39] pitti, thanks for the quick switchover to the new cups/cups-filters packages. [08:42] Morning. [08:52] mvo: can I get the "system architecture" from python-apt somehow, or do I need to call dpkg --print-architecture? [08:56] pitti: python -c 'import apt_pkg; print apt_pkg.get_architectures()' [08:56] >>> apt.apt_pkg.get_architectures() [08:56] ['amd64', 'i386'] [08:56] pitti: eh, actually this needs a apt_pkg.init() first (or apt does this implicitely for you) :) [08:57] mvo: can I rely on the first one being the native system one, or is that just ordered alphabetically? [08:57] pitti: yeah, thats the one - the first is the native one [08:57] mvo: sweet, thanks! [08:57] yw [09:07] hey [09:08] bonjour seb128 [09:08] salut seb128 [09:08] good morning everyone [09:09] hey guys [09:09] how are you? [09:09] quite fine, thanks! [09:19] is Precise stable enough to be used as development platform? :> [09:21] BigWhale: it's our mission to keep it working and upgradeable every day [09:21] and we use a lot more staging these days for pre-upload testing [09:21] BigWhale: so I'd say yes [09:21] errors still happen, of course, but it feels a lot more stable than earlier releases [09:22] even according to non-developers like rickspencer3 :) [09:23] I'm thinking about upgrade ... [09:23] How's with restricted graphics drivers? fglrx, to be more exact. [09:24] hm drrmd yo nr rok [09:25] err... seems to be ok [09:25] BigWhale: yes, nvidia-current works; -173 and -96 don't [09:26] hey seb128, didrocks, pitti, how was your weekend? [09:26] chrisccoulson: it was nice, quite quiet because of the weather, but nice, yours? [09:26] quite good, lot of doing nothing, i.e tv and video games ;-) [09:27] what about you? [09:27] didrocks, yeah, mine was not too bad, although i did work yesterday to get the firefox / thunderbird 10 releases ready [09:27] seb128, sounds like you had quite a relaxing weekend ;) [09:27] oh, that's why you blogged about it :) [09:27] indeed [09:28] didrocks, yeah :) [09:28] chrisccoulson: very relaxed, thanks! wanted to go for some cross-country skiing, but not quite enough snow here yet, so we just went for a long walk [09:30] pitti, for the full source vcs-es like dx components or lightdm you can bzr merge a revision, it's easier than using the patch system [09:30] pitti, next bzr merge-upstream will ignore the commit backported, or rather deal with it, so no added a patch and reverting later [09:30] seb128: ah, I see; I actually started with bzr merge -c [09:30] it's just a "one comamnd, one time" [09:30] seb128: but then saw that there was a debian/patches/ [09:30] the patches dir is useful for stuff not coming from the upstream vcs [09:30] like real distro diff [09:30] seb128: ok; will remember next time [09:30] ok ;-) [09:30] well it works also your way, it's just extra work [09:35] pitti, ah well, I'll just run an upgrade and see what happens :> [10:07] Anyone happen to know how to change the keybinding for HUD, for it not to steal alt? [10:13] Daviey: there is the option on ccsm to assign any keybinding you want [10:14] (not tested there though) [10:14] I thought that package was unspeakable now [10:17] pitti: it is, but I can give the gconf key as well :) I trust Daviey to not go crazy on ccsm options [10:34] Random trivia: during an upgrade to precise, unity will die and you will end up with all the windows crammed on one screen with no means to move them. quite funny. :> [10:35] I'll wait for an upgrade to finish :> === chronossc is now known as chronos [10:55] didrocks: heh, thanks! [10:55] Daviey: yw ;) [11:04] what's the default terminal background in precise? dark or light? [11:06] hey, does this kind of build error messages ring a bell to any of you: "/bin/sed: can't read /usr/lib/libgtk-3.la: No such file or directory", while trying to build indicator-appmenu on precise [11:07] find out which dependencies pulls this in and that one needs fixing [11:13] oneiric package for libgtk-3-dev shipped it, but it does not anymore [11:22] agateau: package was multiarched, it's in (e. g.) /usr/lib/x86_64-linux-gnu/libgtk-3.a now [11:22] agateau: ah, ignore me; .la files are obsolete [11:23] agateau: if some package needs them, please stop that from shipping a .la file, too [11:23] pitti: mmm, I am not sure I know how to do this [11:23] * agateau digs into indicator-appmenu build files [11:23] my guess: an other .la file still mentions it [11:24] what's the issue? [11:24] install the build-depends and grep the .la files for it [11:24] $ find /usr/lib -name '*.la' | xargs grep gtk-3 [11:24] $ [11:24] seb128: FTBFS due to mentioning a non-existant .la file [11:24] agateau: nothing here; can you run this on your boxZ? [11:25] seb128: "/bin/sed: can't read /usr/lib/libgtk-3.la: No such file or directory", while trying to build indicator-appmenu on precise [11:25] agateau: also run it on /usr/local/lib, to be sure [11:25] agateau: often this happens if you do a "make install" from e. g. trunk into /usr/local/ [11:25] pitti: what is "boxZ"? [11:25] agateau: "box" [11:25] like "computer" [11:26] pitti: uh ok, I thought it was another tool I didn't know about :) [11:26] agateau, likely a local build, grep for /usr/lib/libgtk *.la in your local build dirs [11:27] could be indeed, the find returns a bunch of libdummy-indicator-*.la files [11:27] * agateau rms [11:27] I mean rm them [11:31] seb128: do you know if the default terminal background (as we ship it) is dark or light? [11:31] geser, ? [11:31] what do you mean? [11:31] open a guest session and try? ;-) [11:31] in Gnome terminal, the background color [11:31] no idea but it seems trivial to test [11:32] ok, will try it out then [11:32] though I think the current version is buggy [11:32] chrisccoulson or somebody made it ubuntuish some cycles ago and that has been dropped or broken it seems [11:32] pitti, hi, where can I find a complete list of the drivers that Jockey handles? I've found examples/handlers/, but presumably those are only examples. (This is for the desktop-p-control-center-cleanup work item "Design a replacement for the Jockey interface ready to implement in Q".) [11:33] there is vim bug asking to "set background=dark" by default (which only works if we have a dark terminal by default) [11:33] geser, the default seems to be to follow the system theme [11:34] seb128: pitti: ok, problem fixed by removing those manually installed .la files. Thanks for the help! [11:34] agateau, yw [11:34] and the default system theme stays like it is or are there any changes planned? [11:35] there is not only one theme, there are 2 themes [11:35] they will not change this cycle afaik [11:35] but you need to make sure it works with the light theme as well I guess [11:37] is there a vapi file for gnome control center? Anyone knows how to integrate an applet inside g-c-c? [11:37] that's my fear that there is no default which works in every case (GNOME, KDE and the other variants) [11:38] manish, GNOME doesn't allow integration in g-c-c, so if you do that your code will be Ubuntu specific [11:38] manish, you can look at deja-dup as an example [11:38] seb128: in this case a new window opens up [11:38] I want it to behave like bluetooth, displays etc [11:38] not possible? [11:39] manish, in Ubuntu you can, upstream you can't [11:39] seb128: I am working on activity-log-manager g-c-c integration [11:39] so this means there needs to be an ubuntu specific patch [11:40] manish, oh, then libgnome-control-center-dev [11:40] manish, check /usr/include/gnome-control-center-1/libgnome-control-center/cc-panel.h [11:40] manish, you can use deja-dup as a code example, it does integrate there [11:40] yup [11:40] that's the file I am looking at [11:40] yup, but I am writing alm in vala, so need the vapi file [11:40] thanks, checking deja-dup [11:40] oh [11:41] thanks for you help, only 2 weeks left and this work is not finished, but activity-log-manager gtk3 port is done [11:41] manish, in fact deja-dup is doing it in C, I guess you can either do that part in C or hack a local vapi... [11:42] yup, I am not very good at vala either, this was my first work in vala. Will copy the integration part from deja-dup [11:42] ok === om26er__ is now known as om26er === MacSlow is now known as MacSlow|lunch [12:23] Where does the font settings thing live nowaways? [12:24] soren, in gsettings [12:24] Ah, so no UI? [12:24] you can "zoom the text" in the a11y control panel [12:25] but otherwise no [12:25] GNOME considers the font as part of the branding [12:25] so they just give you the ability to zoom if you want bigger or smaller text [12:26] Hm. OK. [12:26] Where in gsettings can I fiddle with this? === s9iper1_ is now known as s9iper1 [12:30] org.gnome.desktop.interface [12:30] Found it. [12:43] seb128: I spent the weekend on screen locking. suspend/resume should be consistent with autologin now, both in gnome-shell and unity. Also, auth dialog should consistently appear after resume now, and another bug squashed that preventing locking from working in certain situations. [12:46] * didrocks no X anymore… [12:46] didrocks: It's overrated anyway. [12:47] soren: yeah, quite annoying for releasing unity though :) [12:52] mdeslaur, thanks a lot ! [12:52] seb128: np, let me know if I broke anything [12:54] mdeslaur, oh sure, I can do that ;-) [12:54] seb128: hehe === greyback is now known as greyback|bia [13:03] good morning, I got nautilus working except that the Change Desktop Background and Ubuntu Documentation menu items don't show up [13:03] it's in https://code.launchpad.net/~gnome3-team/nautilus/ubuntu if someone wants to look at it [13:05] hey jbicha [13:05] jbicha, you mean the unstable serie version? or is something broken in the precise version? [13:06] seb128: 3.3.4 === MacSlow|lunch is now known as MacSlow === s9iper1 is now known as bil21al [13:18] Sarvatt: hey, can I bother you about a latest xorg + nvidia-current issue? :) [13:19] hello jbicha, how are you? [13:20] seb128: FYI, https://launchpad.net/~ubuntu-desktop/+archive/ppa/+packages has udisks2 now [13:21] seb128: it apparently still has some trouble with our udev version, though [13:21] seb128: I don't feel 100% sure about it yet [13:23] pitti, \o/ [13:23]