[01:57] TheMuso, hey, could you sponsor the latest gcalctool to main? Last day tomorrow for getting stuff in right... [02:01] robert_ancell: RC freeze is tomorrow, I'll get to it in a bit. [02:01] s/tomorrow/thursday [02:01] TheMuso, np, thanks [02:39] robert_ancell, hiya [03:13] rickspencer3, hey, back from lunch [03:49] robert_ancell, welcome back [03:50] robert_ancell, did you see bug 447049 [03:50] Launchpad bug 447049 in gdm "Login screen face browser should respond to keyboard as well as a mouse click" [High,Confirmed] https://launchpad.net/bugs/447049 [03:52] hey rickspencer3 [03:52] hi kenvandine [03:52] how was your weekend? [03:58] hi robert_ancell_ are you here for reals? [03:59] ") [03:59] rickspencer3, trying to be, my network seems to be having some problems (tcp/ip stalls) [03:59] bummer [03:59] I'll keep it short while I have you attention then :) [04:00] been happening quite a bit lately. I would chase up the ISP but that never works :) [04:00] bug 447049 [04:00] Launchpad bug 447049 in gdm "Login screen face browser should respond to keyboard as well as a mouse click" [High,Confirmed] https://launchpad.net/bugs/447049 [04:00] robert_ancell_ seems that in certain cases, the greater does not have focus, and there is no way to log in without a mouse :( [04:01] can you alt-tab? [04:01] lifeless, nope [04:01] lifeless, good thought though [04:01] alt-esc etc neither? [04:01] as I said in the bug, some users can't use a mouse [04:01] * rickspencer3 tries alt-esc [04:02] lifeless, nope [04:03] worth a crack [04:03] would still be ugly if it had worked [04:03] lifeless, yes, but would not be so serious if there were such a workaround [04:03] so good thinking [04:04] it seems that the theme changes quite a bit recently, I wonder if that could have introduced a problem [04:10] Try CTRL + ALT + Tab [04:11] grr, not my day. Network problems and now text mode doesn't work after the last upgrade [04:11] yay [04:12] network connectivity sucks at the best of times [04:14] rickspencer3, still there? Did you say something about bug 447049? [04:14] Launchpad bug 447049 in gdm "Login screen face browser should respond to keyboard as well as a mouse click" [High,Confirmed] https://launchpad.net/bugs/447049 [04:15] hi robert_ancell [04:15] robert_ancell: yes he did [04:15] my, quite the selection of robert_ancell's [04:15] robert_ancell, yes [04:15] the problem is that in certain cases, the GDM greeter can't be navigated with the keyboard [04:15] which of course really bites if you can't use a keyboard [04:16] I know I used to be able to press space bar and start typing my password. I can't do that any more. [04:16] so I bumped it to high, and assigned it to you, of course ;) [04:16] TheMuso, well, on my netbook, it's busted, but my desktop works fine [04:16] interesting [04:16] in any case, according to one of the bug comments, sounds like the greater does not have focus [04:17] rickspencer3, right, that appears to be the case for me [04:17] TheMuso, I don't want to speak for blind users, but I would assume that this would make the greeter work not to well if you were blind [04:17] rickspencer3: Very mcuh so. [04:17] much [04:17] ok, so I'm thinking that accessibility-wise, we need to do something asap [04:17] It appears the very first time you start the greeter it occurs but it's ok from then on [04:18] robert_ancell ... not for me, it is recurrent on my netbook [04:18] robert_ancell .. is there a way to simply force focus on the greeter when it loads? [04:18] rickspencer3, can you check when you're logged in if the greeter is still running (using alt+ctrl+F keys) [04:19] rickspencer3, yes, will see why it hasn't picked it [04:20] robert_ancell, I tried alt+ctrl+f and nothing happened, but perhaps I misunderstood your directions [04:21] rickspencer3, in my case my session is running on alt+ctrl+F7 and the greeter is running in the background on alt+ctrl+F10 - I'm not sure how gdm decides when to keep it in the background. If you can't find it chances are it is being restarted each time you switch user [04:21] oh, I see [04:21] switch to a VT you mean [04:21] ;) [04:21] yeah, the name escaped me for a minute :) [04:23] robert_ancell, ok, on my netbook, if I switch to VT 9, the greeter is there, and has focus (or at least keyboard works) [04:25] rickspencer3, so is the lack of focus only occuring on startup or each time you switch user? [04:25] robert_ancell, on startup, then when I go to switch users through the session indicator [04:31] robert_ancell, now after doing the VT switch thing, it has focus again :/ [04:31] * rickspencer3 tries restarting [04:31] * robert_ancell also restarting [04:35] hmm [04:36] robert_ancell, ok, I repro'd the weirdness and captured the steps in the bug [04:36] thanks [04:37] robert_ancell, gotta run ... any other work I can add to your list before I go? [04:37] :) [04:37] no thanks :) [04:37] we've only got 2 days to get any changes in! [04:38] well, we *have* to fix this one [04:38] * rickspencer3 suspects the new theme is somehow culpable [04:39] That doesn't make sense though [04:39] its just a GTK theme [04:39] right, but maybe some widget has focus and is invisible for something [04:39] right [04:39] so [04:39] I just don't know what other changes occured [04:39] think abou the mechanics [04:39] gdm starts [04:39] it starts x [04:39] it starts xsplash [04:40] it's a pain because it's got a custom widget in it and a bunch of hidden stuff too [04:40] it signals xsplash to die [04:40] AIUI there isn't a WM running [04:40] hmm .. xsplash changed, and it's just a gdm app, maybe xsplash has keyboard focus [04:41] lifeless, metacity is running [04:41] ok [04:41] so there is a wm [04:41] if everything is sane the focus should end up somewhere useful... [04:41] right, but the point still remains to consider ordering [04:41] sure [04:41] so the key components are xsplash, metacity & gdm-binary [04:41] rickspencer3, apt-get remove xsplash and see if it occurs [04:41] * rickspencer3 tries [04:42] gdm-simple-greeter not gdm-binary [04:42] robert_ancell, ? [04:42] robert_ancell: hey, I'm just doing ideas-man :P [04:43] ehe [04:43] lifeless, that job is taken [04:43] ;) [04:43] gdm-binary is the server component, gdm-simple-greeter is the gui, gdm-simple-slave is the server side component of the greeter [04:43] the new gdm is complex... [04:43] rickspencer3: robert_ancell was correcting my understanding of what bit of gdm shows the gui :) [04:43] robert_ancell: thanks btw ;) [04:44] lifeless, :) [04:44] I'm only peeked shallowly [04:44] boot up is much less pretty without xsplash [04:45] dang it! [04:45] robert_ancell ... works after removing xsplash [04:45] robert_ancell ... works after removing xsplash [04:46] rickspencer3, ok, there's our problem [04:46] TheMuso, if we can't get this fixed by Thur, is removing xsplash and acceptable work around in your opinion? [04:46] rickspencer3: IMO yes. [04:46] I suppose for blind users, xsplash has minimal utility in any case [04:46] but people can't use mice for other reasons as well [04:47] * rickspencer3 notes on bug and adjusts priority and assigns to xsplash [04:47] rickspencer3: I'm not sure its an xsplash problem [04:47] rickspencer3: consider that once xsplash quits there is nothing more it can do; getting focus to the right place is up to metacity [04:48] lifeless, xsplash doesn't quit ... it just get's invisible [04:48] rickspencer3: it quits [04:48] I don't think so, I think it fades out and waits for a signal from the gdm greater to fade in [04:48] rickspencer3: I was looking at it with Cody last week [04:48] rickspencer3: it quits [04:48] hmmm [04:48] fair enough [04:48] /etc/gdm/PreSession/default starts it up again once the user is selected [04:49] [that path is from memory, may be slightly off] [04:49] but none the less, xsplash change, the problem occurred, I removed xsplash, it went away [04:49] rickspencer3: right, but that doesn't make xsplash the problem :) [04:50] that just makes xsplash the thing that makes the problem visible [04:50] robert_ancell: do you know metacity/wm guts well? [04:50] lifeless, no [04:51] xsplash does catch the focus out signal though which I'm investigating [04:51] Sounds like a bug I experience occasionally where I close a window, and I totally lose focus on the desktop, and can't use orca or anything but the mouse to regain focus on a window etc. Sounds very much like metacity., [04:51] TheMuso: exactly [04:51] TheMuso: Thats where my money is, a metacity issue that we've found a minimal test case for ;) [04:52] lifeless: Right, and whats more, this bug I experience occasionally is random as well. [04:53] rickspencer3: if we need a package for this bug, all the data I have says its metacity; xsplash is dead simple and I didn't see anything odd related to window mgmt when I was looking over Cody's shoulder [04:53] lifeless, agreed [04:53] I'll leave it on GDM for now, as robert_ancell is working on it for the time being in any case [04:54] while it may be metacity with the core problem chances are it will be easier to make xsplash play nice [04:54] foR THE SHORT TERM, THAT SOUNDS REASONABLE. [04:55] gah capslock [04:55] robert_ancell, yah [04:55] something change in xsplash that exposed this bug [04:55] it would seem [04:55] mmm [04:56] or, it's related to the new theme, those are the only things that changed, so far as I know [04:56] robert_ancell: what changes do you have in mind that would make xsplash not trigger this [04:56] lifeless, not sure but other windows close without focus being lost [04:57] robert_ancell: personally, I'd look at the root cause; its often simpler than it seems to fix things properly. IMNSHO. Yada Yada Yada. [04:59] robert_ancell, given our time constraints, it's your call [04:59] * rickspencer3 has to go [04:59] good night all [04:59] rickspencer3, cya [04:59] robert_ancell, thanks for picking this up and taking a crack at it, please comment wrt progress on the bug, and I'll see where we're at in the morning === Amaranth_ is now known as Amaranth [06:40] dobey: Ubuntuone seems to be using the icon of the drive with a cloud ... rather than the greyscale icons that have been added to humanity... [07:16] Good morning [07:35] hey pitti [07:36] bonjour didrocks [07:53] hi [07:53] to use vmware or vbox [08:01] vbox. [08:06] kvm! [08:09] kvm++ [08:10] no hardware support ftl =( [08:10] of all the core 2 duos around, i got the one that doesn't support vtx === tkamppeter_ is now known as tkamppeter [09:05] good morning everyone [09:06] hey chrisccoulson [09:06] hey seb128 [09:06] hey chrisccoulson, seb128 [09:07] hey pitti [09:07] hey pitti [09:07] you guys had a good night? [09:09] hey seb128, thanks for the sponsoring :) [09:09] hello chrisccoulson [09:09] didrocks, thank you for the work ;-) [09:09] hey didrocks [09:09] * didrocks hugs seb128 [09:10] seb128: bit short, but I slept well [09:11] same here [09:25] seb128 - can you figure out what problem this user is trying to describe on bug 448759? [09:25] Launchpad bug 448759 in gdm "gnome-session command in terminal causes nautilus error" [Low,Incomplete] https://launchpad.net/bugs/448759 [09:25] i don't know if it's just me who doesn't understand it [09:29] chrisccoulson, no, I don't understand it either [09:30] yeah, i'm really confused with it now [09:30] there may be something lost in translation -- the reporter does not seem to understand, or refused to answer your quesiton [09:30] BTW, chrisccoulson, did you get in contact with the folks on b.g.o for your bug access? [09:31] hggdh - possibly. perhaps you would like to comment on it? ;) [09:31] hggdh - not yet, i haven't had time yet [09:31] but thanks for replying to my message btw:) [09:31] heh. nothing like a foreigner to talk with another one... [09:31] lol [09:49] hi [09:50] are there plans to update evince in jaunty, for example to fix the infamous "last slide skipped in presentation mode" bug? [09:57] lucas, depends if somebody is interested to work on the sru [09:57] I'm not but I'm happy to sponsor a debdiff if somebody does the paper work and the change [09:59] seb128: evince 2.26.2 fixes the bug, so updating to that upstream release would be enough [09:59] lucas, we don't upload new versions to stable usually [09:59] ah, I thought you did for gnome. sorry. [09:59] especially not new in a non lts version when the paperwork etc will bring us after karmic being stable [10:00] if nobody complained in 6 months there is no strong case to sru now [10:00] ok. I just saw someone running into that bug, that's why I asked. === egon is now known as mvo__ [10:21] seb128: lp:human-theme has the added icons for the gdm shutdown dialog and it works well (thanks to chrisccoulson for the names) [10:22] kwwii, it was an error on your side yesterday then? [10:25] seb128: yeah, I think I was somewhat blind last night :p [10:47] mat_t: you still get beeping on your system? if so, can you please check if https://bugs.edge.launchpad.net/ubuntu/+source/pulseaudio/+bug/449582/comments/6 helps? [10:47] Launchpad bug 449582 in pulseaudio "Hideous BEEP on new email" [Undecided,New] [10:51] kwwii, uploaded to karmic [10:51] pitti, thanks for the gnome-disk-utility snapshot [10:52] seb128: yw [10:52] seb128: I was going to ask you whether we wouldn't get it anyway with 2.28.2 next Monday [10:52] pitti, I would have done it myself but I don't know if you want to stay on sync with debian there [10:52] but you were offline, so I just did it [10:52] pitti, I don't know davidz has not been good at rolling regular tarballs for it [10:52] seb128: I don't want to put git snapshots into debian git, but of course I want to commit all packaging changes [10:53] so I just want to avoid piling up permanent deltas [10:53] pitti: ok, thanks! [10:53] pitti, ok makes sense [11:06] asac: you wanted us to test 3G cards again; I just plugged in mine, and got some bouncing in dmesg (http://pastebin.com/f2a0c3d56), but it doesn't appear in nm-applet [11:06] Oct 13 12:06:38 tick usb_id[12686]: unable to access '/devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8.2/1-8.2:1.1/ttyUSB1/tty/ttyUSB1' [11:06] hmm [11:07] did you see this before? want a bug report? what info should I include? [11:07] hm, no /dev/ttyUSB0 [11:07] pitti: https://wiki.ubuntu.com/DebuggingModemmanager [11:08] the debug log would be great [11:08] unable to access feels odd [11:08] asac: ah, thanks; I think it's got something to do with transitioning the fake CD-ROM to modem mode [11:08] I'll have a look at this wiki page [11:20] asac: thanks, done [11:28] seb128: thanks! [11:33] pitti: would it be ok if I moved the trigger for the debconf interface to the several nvidia-$VER-modaliases packages from the kernel postinst.d? (bug #292606) [11:33] Launchpad bug 292606 in nvidia-common "dkms - error when installing custom kernel" [Medium,New] https://launchpad.net/bugs/292606 [11:35] tseliot: why modaliases? shouldn't such a thing be in nvidia-common? [11:36] pitti: it is there already but it's possible that the debconf interface is called before the drivers (and the modaliases) are updated [11:36] tseliot: where are the debconf interfaces now? [11:37] pitti: it's all in nvidia-common however we install the trigger to /etc/kernel/header_postinst.d/ and /etc/kernel/postinst.d/ too [11:38] (see setup.py in nvidia-common) [11:39] and why does it break? [11:40] pitti: because DKMS doesn't clean stdout and the debconf interface gets part of the DKMS output as a reply instead of getting only the output of the nvidia-detector app [11:41] tseliot: dkms is called in *.config? [11:41] anyway, isn't the proper way to fix that to call db_stop after being done wiht debconf and callnig stuff? [11:42] pitti: no, dkms is called in the kernel postinst.d (just like nvidia-common) [11:43] tseliot: so, I don't understand the problem yet, but moving debconf to -modaliases sounds wrong (since they are installed by default) [11:43] and triggers installed by default shoulnd't care which package they come from (-common or modalises)? [11:43] pitti: and so is nvidia-common [11:44] not that I'm keen on adopting this solution [11:44] I just want to fix this bug once and for all [11:45] tseliot: the only proper way to fix this debconf breakage that I know is to call db_stop after you're done with debconf, and not call programs which mess with stdout in between [11:46] pitti: here's the debconf script: http://pastebin.ubuntu.com/292280/ [11:48] currently it has to call nvidia-detector in order to get the recommended driver (or "none" if no obsolete driver is installed) [11:48] dkms is called before nvidia-common in the kernel postinst.d. NOTE: it's not nvidia-common that calls it [11:49] tseliot: that looks fine, though, since it redirects nvidia-detector's stdout [11:50] right but it looks like dkms "pollutes" the $LATEST variable with its own stdout [11:50] see superm1 reply to the bug report [11:57] tseliot: I read it, but admittedly it would take me a long while to really understand this bug [11:58] tseliot: if superm1 and you agree that moving it to the modalias files is the way to go, then go ahead, but it feels utterly wrong to me: conceptually (since it's got nothing to do with modalises), structurally (since it'd replicate one script four times), and behaviourally (relying on any unpack order instead of fixing the true root cause) [11:59] if you want dkms to run for a new driver version, it should be done in that very driver, not any other package [11:59] pitti: ok, thanks for your help. I'll further discuss this with superm1 then. [11:59] e. g. nvidia-180-kernel-source [11:59] tseliot: well, I'm afraid I wasn't really helpful here :-( (sorry, have my head full with other stuff) [12:01] pitti: no problem, we're all quite busy at this point in the development cycle [12:10] seb128 - do you know the purpose of 100_load_desired_settings.patch in gnome-desktop? [12:11] chrisccoulson, to load the desired settings? ;-) [12:12] heh. i couldn't figure out what determines the desired settings, and what benefit it gives over the upstream design [12:12] i was unsure of the difference between the intended settings and desired settings [12:12] * debian/patches/100_load_desired_settings.patch: [12:12] - enable gnome-settings-daemon to load the desired settings [12:12] saved by the xrandr capplet when the virtual resolution has [12:12] to be saved and the settings cannot be applied immediately. [12:13] chrisccoulson, I think it has to do with configs where you need to add virtual to xorg.conf [12:13] ah, ok. that makes more sense then [12:13] chrisccoulson, the config is only applied after an xorg restart in such cases [12:13] since virtual is not dynamic [12:13] chrisccoulson, tseliot wrote that so he might know better [12:13] i understand now [12:13] thanks:) [12:13] you're welcome [12:14] i think that's enough. i just wanted to understand why it was there [12:14] what seb128 wrote is correct [12:14] * tseliot > lunch [12:15] tseliot - thanks [12:15] i might make a small change later so that gnome_rr_config_apply_with_time() always sets the GError when the call fails [12:16] it doesn't do that currently, which causes some g_criticals in gnome-settings-daemon [12:17] chrisccoulson, ok [12:35] * mvo__ is away for some minutes [12:51] istaz, hi, bug #411805 has quite some duplicates do you know if there is an easy fix we could backport? [12:51] Launchpad bug 411805 in telepathy-butterfly "telepathy-butterfly crashed with UnicodeDecodeError in ()" [Medium,Fix committed] https://launchpad.net/bugs/411805 [12:55] seb128: sorry apparently it's not fixed yet if you are still getting report of it with papyon 0.4.2, I will take a look at it latter, a way to reproduce it would be great [12:55] istaz, ok thanks [12:55] I guess it caused by contact having non-ascii char in their adress [12:55] istaz, do you look at bugs on launchpad btw? there is quite some assertions and crashers there but nobody seems to comment, would you prefer if we forward those?N [12:56] I look at them when I have time but I have been quite busy with my new job [12:56] ok [12:57] is somebody else looking at those upstream, ie is that worth forwarding those or will it lead at you being too busy and not looking at them anyway? [13:00] seb128: voip related bugs may be nice to forward since it's mostly Tester fixing them and I don't think he look at launchpad. Others butterfly/papyon contributors seems to be too busy for now :/ [13:01] ok, thanks [13:01] so I don't think it worth the efford forwarding other bugs for now [13:02] seb128: I made a papyon bug fixes release last week, do you think it's still in time to package it for karmic? [13:03] istaz, let me have a look to the diff with what we have now but if it's bug fix only it should be ok [13:03] ok [13:03] it mostly contain patch you would have to backport anyway [13:08] istaz, looks fine, looking at the change there is only https://bugs.freedesktop.org/show_bug.cgi?id=24236 which we don't have now [13:08] Freedesktop bug 24236 in papyon "crashed with NameError in __group_contact_delete_errback()" [Normal,Resolved: fixed] [13:08] and the av fixes but since we don't have that on in karmic... [13:09] seb128: well if you have the fix for the bug in _MSG it's ok then, it's probably the most important one [13:11] seb128: also you could put the bugs directly in public, only the full log should contain private data [13:11] istaz, ok, good to know, I was not sure if exception could have login informations [13:12] thought it would be easier if we had the full logs (with the sensitive information removed of course) to debug [13:13] would be nice if the log would not have sensitive informations to start [13:14] if somebody want to have a look at making remplace account names and password by dummy ones [13:14] those should not be really useful for debugging [13:14] yes we should do that === hggdh_ is now known as hggdh [13:15] except this particular bug seems to be caused by someone account name ;) [13:16] istaz, well in such cases we can still ask for details ;-) [13:17] papyon bug fixed on today's updates, finally I can test it :P [13:21] joaopinto: tell me if you encounter the other bug [13:23] hum, i have know idea what's that TargetID about [13:27] hmm, does update-manager handle PPAs and other 3rd party repositories in any way during upgrade? [13:38] kklimonda, don't think so [13:39] kklimonda: it [13:40] does check from PPA also and PPA is treated [13:40] just as any other software source. and wherever it finds latest version of the package in PPA or other repo [13:40] is changes jaunty to karmic on ppas sources ? [13:40] it will uuse it [13:41] it [13:42] tgpraveen, what you are describing is apt specific, not related to update-manager :) [13:46] joaopinto: and um update manager does it differently? [13:46] I thought it also did the same thing [13:46] tgpraveen, update does it differently for the ubuntu official sources [13:47] not it only changes the sources itself, as it also covers some specific upgrade scenarios for some packages/components [13:48] I guess kklimonda was asking if update-manager doe something "special" about PPAs :P [13:51] seb128: is it too late to introduce the patch in comment 24? bug #386017 [13:51] Launchpad bug 386017 in hundredpapercuts "Brushing right-edge of trackpad causes clipboard to paste text" [Undecided,Confirmed] https://launchpad.net/bugs/386017 [14:00] seb128: it's for the gnome-settings-daemon and it would add some strings [14:01] tseliot, sorry I was tracking a python bug [14:01] looking [14:02] ok, thanks [14:02] tseliot, yes it's too late for karmic for such changes [14:02] it adds new feature and new strings [14:02] no way we can get those tested and translated now [14:03] seb128: ok, just as I suspected [14:03] seb128: there's another things that concerns me. The gnome-settings-daemon disables tap-to-click also on touchpads which don't have physical buttons [14:04] which means that users might be left without a way to perform clicks [14:04] hmmm [14:04] i just caught the tail end of that, but i don't think thats the intended behaviour is it? [14:04] hello btw:) [14:04] hey chrisccoulson [14:04] I think I can fix that in the g-s-d [14:04] hi [14:05] hey seb128 [14:05] tseliot, talk to rick when he's around about what to do about tap-on-click in karmic [14:06] seb128: I'm referring only to that specific case. I'm not suggesting that we enable tap-to-click for everyone. But yes, I'll talk to him later [14:07] tseliot, well if you can fix this case great but there is still the default question to discuss [14:07] could be a topic for meeting today [14:08] I think people suggested to enable it by default with the desactive click while typing too [14:08] seb128: ah, ok, we can discuss that too [14:09] seb128: where is the default value for tap-to-click stored? In what file? [14:09] tseliot, gconf key [14:10] it doesn't seem to be in g-s-d.gconf-defaults [14:10] tseliot, /desktop/gnome/peripherals/touchpad/tap_to_click [14:10] hmm... for some reason ubuntu one has marked all the files&folders in my system as synced :/ [14:10] seb128: I mean, in the source package [14:11] aah, maybe in data/ [14:11] in one of the schema files in the data directory most likely [14:11] yeah [14:11] ok [14:11] tseliot, desktop_gnome_peripherals_touchpad.schema [14:12] desktop_gnome_peripherals_touchpad.schemas in g-s-d [14:12] ok, thanks [14:16] <|_i|\]|_|X> Hi [14:21] is there a meeting of desktop team today? [14:21] in how much time? [14:24] yes, in 3 hours [14:30] k. thanks [14:32] hey - is there a dbus signal from gnome-power-manager for returning from hibernate/suspend ? [14:34] mvo__: at least the gpm debug log says "emit resume" [14:35] mvo__: what are you trying to do? [14:35] mvo__ - not that i'm aware of === robbiew_ is now known as robbiew [14:36] you can listen to the BrightnessChanged signal but that's not necessarily a sign of returning from hibernate/suspend [14:37] mvo__: ^ [14:38] tseliot, hm, thanks. I want to fix #450286 [14:39] bug #450286 [14:39] so basicly update the "last checked" time in u-m [14:39] Launchpad bug 450286 in update-manager "[wishlist] update "last updated" text after resume from hibernate/suspend" [Wishlist,Confirmed] https://launchpad.net/bugs/450286 [14:41] seb128: do you have any idea how my G1 mobile gets x_content_types: x-content/image-dcf in gvfs? [14:41] seb128: grep -r image-dcf doesn't give anythign in dk-disks, gdu, or gvfs [14:41] (except in the gphoto2 backend in gvfs, which isn't relevant here) [14:41] mvo__ - there's currently discussions starting about having suspend/resume events from devkit-power-gobject, for triggering things like locking the screen on suspend etc [14:41] but that doesn't exist yet [14:41] pitti, what directories are there? [14:41] seb128: it has a DCIM/ [14:42] chrisccoulson, thanks, I see if I can just do it differently then! [14:42] seb128: I just fixed one half of bug 440290, but the mime type is still missing [14:42] Launchpad bug 440290 in devicekit-disks "iPod only being detected as Drive, not as iPod" [High,Fix committed] https://launchpad.net/bugs/440290 [14:42] pitti, that's probably it [14:42] seb128: grepping for DCIM in those three doesn't match anything either :-( [14:43] mvo__ - sorry i can't be of much more use ;) [14:43] pitti, freedesktop.org.xml: [14:43]