=== asac_ is now known as asac [02:09] anybody know if if the indicator applet uses the user's icon theme at all or it's own? [02:42] LaserJock: users [02:47] lifeless: ok [03:36] * ccheney uploading new OOo build :) [03:50] whee only 14min to upload the diff.gz [04:03] anyone have video out of range problems with both the install and livevd versions of 9.10? tried it both ways with my two machines and video being over driven out of range. [04:05] and are there ways to get screen resolution set with the initial bootstrap screen to set resolution so I can get around the problem. I am using a Nvidia GeForce 7500 series card with 512mb [05:04] pitti: 20091012 (daily-live or daily) should resolve the "muted on boot" symptom [05:06] dtchen, daily-live's are currently not functional, see bug 448981 [05:06] Launchpad bug 448981 in mountall "/var/run/dbus is not getting populated on live CDs" [Undecided,New] https://launchpad.net/bugs/448981 [05:07] superm1: that's fine; all the audio stack updates are in 20091012 anyhow [05:07] dtchen, reminds me, i had something to ask you about. it looked like fresh installs were having the mic muted on one of my laptops. going into alsamixer it looks like it's because "Capture" isn't selected by default [05:09] at least that's what changes if i have alsamixer open in terminal and uncheck the muted box in the gnome-media [05:12] well, that's ugly [05:12] that will take some fiddling with switch = foo in /usr/share/pulseaudio/alsa-mixer/paths/analog-input.conf [05:13] again, we could unbreak it for some codecs at the cost of regressing others [05:14] some of this pain will go away in the next release of PA due to device profiles [05:14] (to be fair, that really means the burden of maintenance gets shifted into some other conffile) [05:15] well what would you like out of me so that you can fully evaluate the best thing to do? [05:16] i'm assuming apport-bug SOME_ALSA_PACKAGE filed from a fresh install? [05:17] the problem is that i have no idea how much hardware is being used, so i can only guess (poorly) at HDA codecs being dominant [05:17] we could use switch = on for [Element Capture] [05:18] that's going to break SB Lives, Audigys, certain crackfully rebranded X-Fis, ... [05:18] in what fashion will it break those types of hardwares though? [05:19] "I can't hear anything played back through the speakers until I set Capture to nocap" [05:19] fun fun [05:20] is it not possible to query the launchpad hardware database to find out how prevalent certain codecs are? [05:21] it probably is possible, but we need to decide whether we care about legacy compatibility [05:21] if we don't care about hardware (older than five years) out of the box doing capture with no fiddling, then we could just set that one line [05:23] so who makes that call then? [05:24] http://pastebin.com/d4aef3f1a [05:25] WRT accountability -- well, i don't mind doing it, seeing how i get the arse-end of bug reports anyhow [05:26] it's easy enough to revert, but it _is_ quite late in the cycle to do it [05:27] well surely there will be a few more pulse uploads before the cycle is up, so if you put it in say the next upload and get some really bad feedback, you probably won't have to go out of your way for an upload "just for that" [05:28] i _really_ hope not to bribe TheMuso into uploading more than a couple times (: [05:34] * ajmitch seems to have only seen HDA hardware lately [06:01] dtchen: I think ac97 and hda are probably our two biggest, followed by Creative cards, as 5 or so years still = ac97 + creative hardware. [06:02] As for pulse, well I hope we only ned one more upload at the absolute most. [06:02] if that === Richie is now known as YDdraigGoch [07:16] Good morning [07:17] dtchen: muted on boot solved> yay! [07:41] good morning pitti, did you have a good week-end? [07:42] hey didrocks; I did, yes; and you? [07:43] pitti: short but great. I had a hard time in updating my book to karmic. Too many little changes that makes a bunch of stenza to rewrite :) [08:08] didrocks: yeah, karmic turned a lot of stuff upside down :) [08:10] pitti: exactly, I didn't figure out at first glance that there were so many little things changing! [08:45] good morning there [08:45] good morning seb128! [08:45] hey mvo, had a good week end? [08:46] yes, a bit too rainy for me taste, but otherwise fine [08:46] bonjour seb128, guten Morgen mvo [08:46] it didn't rain for weeks, it's good to have some water sometime ;-) [08:46] hey pitti [08:48] good morning seb128 [08:48] hey mvo [08:49] lut didrocks [08:49] hey chrisccoulson [08:49] hey seb128 [08:50] how are you? [08:53] good, you? [08:54] did you have a good weekend? [08:58] yeah, my weekend was quite relaxing. we had some family over on saturday and then i didn't do much yesterday [08:59] pitti, hi === tkamppeter_ is now known as tkamppeter [09:02] over 800 bug emails during the weekend [09:02] shrug [09:06] seb128 - that's quite a lot. it doesn't help when certain users keep repeatedly reporting the same bug ;) [09:07] yeah... [09:21] mac_v: how much will I make you cry if I find a gnome-power-manager icon which isn't monochome? ;) [09:21] I just plugged in a wireless mouse and it's giving me an icon about it having no battery left (which is a lie, but a separate bug) [09:25] "plugged in a wireless mouse" ? [09:25] Ng: we just havent made icons for those ;p .... damn it i hoped no one used those ;) [09:25] Ng: screenshot pls [09:28] mac_v: http://mairukipa.tenshu.net/screenshots/2009-10-12-wireless-mouse-icon.png [09:30] yeah, thats the gpm-mouse-* icons [09:31] Ng: i guess you need to file a bug ;) else lool wont update those icons unless they are release critical, even if i make them [09:31] mac_v: against which package? [09:32] Ng: humanity [09:32] humanity-icon-theme to the excapt [09:32] k [09:32] exact* [09:36] mac_v: done, bug #449334 [09:36] Launchpad bug 449334 in humanity-icon-theme "wireless mouse icons not monochrome" [Undecided,New] https://launchpad.net/bugs/449334 [10:09] pitti: morning! [10:09] hey mat_t [10:09] pitti: fade-out on shutdown doesn't work anymore :( [10:09] pitti: any idea what might have happened there? [10:11] mat_t: I think so; -> #u-devel [10:11] mat_t: oh, no Keybuk [10:12] pitti: do you mean "ask Keybuk"? :) [10:12] or "don't ask Keybuk"? [10:12] ;) [10:12] mat_t: I just asked cjwatson in #u-devel, Keybuk/cjwatson did the recent changes [10:15] hum [10:16] why are we getting a "need to use the mouse to log in" stack of bugs no? [10:16] now [10:17] comments seem to indicate that changed recently [10:17] pitti, did you do gdm changes recently? [10:17] Ng: Yeah we're deep in artwork/ui freezes so I need the design team to vouch for any required changes at this point [10:17] mac_v: Instead of sending people directly to me, get input of the design team first on the criticality of the fix [10:17] (If in doubt) [10:18] seb128: yeah, right now it seems like you have to make a selection with your mouse, hitting enter does not select the user [10:18] wth? [10:18] lool: yup , i'v told mat_t too , that for any bug that is release critical , it needs to be commented on the bug [10:18] by the UX [10:18] I'm wondering if that's a theme issue [10:18] since gdm didn't change recently out of theming... [10:19] seb128: isn't that because the user is not selected by default anymore? [10:19] why wouldn't it? [10:19] we didn't change that [10:19] pitti, ^ do you know about that? [10:19] seb128: I know that we didn't want it to be, because of usability issues, but only provided that hitting enter would still work [10:20] there was no recent gdm upload [10:20] what changes to make the default user not selected and who did that? [10:20] changed [10:20] seb128: I think someone changed it to "deselected" by default recently [10:20] hello mvo [10:20] how? [10:20] morning seb128 [10:21] seb128: I don't know! I certainly wasn't involved :) [10:21] https://edge.launchpad.net/ubuntu/+source/gdm/+changelog has no sign of such change [10:21] hey glatzor! [10:21] glatzor: how are you? [10:22] let me do testing, brb [10:22] hey glatzor [10:22] seb128: I wondered about that as well, and it annoys me too [10:23] mvo, fine! hope yourself too! [10:23] glatzor: yeah, its release time, so a bit in crunch mode, but otherwise fine :) [10:23] seb128: hola ... would you mind if i upload a workaround patch for gnome-terminal profile selection not working ;)? http://pastebin.com/f42b7ed25 [10:23] glatzor: have you seen my mail/patches? [10:24] i can submit that upstream too ... but feels like its a gtk bug that "toggled" does not work [10:27] seb128: wb [10:27] seb128: I wondered about that as well, and it annoys me too [10:27] seb128: it seems to work after restarting gdm, but not after initial boot [10:27] seb128: I didn't change gdm recently, though [10:28] seb128: it seems correlated with the "100% CPU" bug, thuogh [10:28] weird [10:28] seb128: cryptsetup/gdm sharing one VT might also lead to cryptsetup intercepting the key presses? [10:28] then again, the password entry does seem to work [10:28] pitti, is that new? I don't get the issue there but I didn't upgrade during the weekend [10:29] seb128: it's bug 439138; not really new, but I personally got it after the recent mesa upgrade last week [10:29] Launchpad bug 439138 in usplash "[karmic] Xorg 100% CPU utilization -- only after first login" [High,Confirmed] https://launchpad.net/bugs/439138 [10:29] pitti, bug #447049 [10:29] Launchpad bug 447049 in gdm "face browser should respond to as well as a mouse click" [High,Confirmed] https://launchpad.net/bugs/447049 [10:30] mvo, about the proxy? [10:30] I've assigned to canonical desktop team and targetted karmic [10:32] glatzor: yeah [10:32] mvo, ah, that is the reason for LP #448810 [10:32] Launchpad bug 448810 in aptdaemon "Update manager now requires two authentications" [Undecided,Confirmed] https://launchpad.net/bugs/448810 [10:32] Ah, I was just about to report bug 447049 :-) [10:32] Launchpad bug 447049 in gdm "face browser should respond to as well as a mouse click" [High,Confirmed] https://launchpad.net/bugs/447049 [10:33] seb128: replied [10:33] pitti, thanks [10:34] glatzor: yeah, I changed it to auth (I put a rational in the changelog that hopefully is clear why) [10:34] auth_admin [10:35] seb128, on my main partition I haven't yet installed whatever update it is that breaks Enter in GDM. So if you can think of other possible packages that might be causing the problem, I could update them one at a time and work out which it is. [10:35] mpt, I didn't upgrade either so I will try there but thanks [10:35] mpt, could you look to pitti's comment on the bug though? [10:36] mvo, but this changes the user experience a lot [10:36] seb128, pitti hasn't commented on that bug report. Do you mean another bug report, or someone else? [10:36] mpt: I just replied to bug 447049 [10:36] Launchpad bug 447049 in gdm "face browser should respond to as well as a mouse click" [High,Confirmed] https://launchpad.net/bugs/447049 [10:36] mvo, now you need to be an admin user to be notified about updates [10:36] oh, I was two minutes out of date :-) [10:38] pitti, if I upgraded I probably wouldn't be able to tell whether I was experiencing bug 439138, because I've been experiencing bug 447231, which would mask it. [10:38] Launchpad bug 439138 in usplash "[karmic] Xorg 100% CPU utilization -- only after first login" [High,Confirmed] https://launchpad.net/bugs/439138 [10:38] Launchpad bug 447231 in xorg "Xorg constantly uses near-100% CPU after 9.04->Karmic upgrade" [Undecided,Confirmed] https://launchpad.net/bugs/447231 [10:39] mpt: it should still work after logging out of the first session, though [10:39] pitti, sorry, by "it should still work" do you mean "GDM should start behaving properly", or something else? [10:39] mpt: yes [10:40] hm, actually, on my clean Karmic installation I have the GDM problem but I don't have any CPU problem at all [10:40] I get the effect for the gdm after boot, and then X.org 100%, log out, get back to gdm, and pressing Enter works [10:40] I will install all updates on that other installation, check it, and be back in 10 minutes [10:41] glatzor: hm, maybe we should change it then to only ask if there is a proxy in use? [10:49] pitti, hi [10:49] hi tkamppeter [10:50] pitti, have you seen bug 448769 and duplicates? Seems that on an update from Jaunty (or older) to Karmic the cupsd.conf gets completely wiped out. [10:50] Launchpad bug 448769 in cups "Printing broke on upgrade to Karmic [cupsd = signal 15] (dup-of: 429138)" [Undecided,Invalid] https://launchpad.net/bugs/448769 [10:50] Launchpad bug 429138 in cups "cups exits with "No valid Listen or Ports lines"" [Undecided,Confirmed] https://launchpad.net/bugs/429138 [10:52] pitti: ... no, I have the GDM problem but no CPU problem [10:59] mpt: ok, so it seems unrelated then [11:50] pitti: just running some tests on today's iso it seems to drop into in terminal login rather than gdm, just checking things through. [11:53] pitti: okay that's worrying ps aux | grep gdm nothing but the grep command. sudo start gdm then ps aux | grep gdm nothing but grep gdm :( [12:11] pitti, do you have any idea how the cupsd.conf get get wiped out when updating from Jaunty or older to Karmic? === statik` is now known as statik === Keybuk_ is now known as Keybuk [12:44] re [12:45] davmor2: eww; can you try "sudo gdm-binary --debug" and check what it complains about? [12:45] tkamppeter: no, not really; didn't we discuss that some days ago in #u-devel? [12:46] pitti: I've start bug 449454 where I've added the syslog output but I'll do that for you and add the info to the bug [12:46] Launchpad bug 449454 in ubuntu "Ubuntu has no gdm and no xsplash on todays iso" [Undecided,New] https://launchpad.net/bugs/449454 [12:47] davmor2: ah, thanks [12:49] pitti: added out put [12:51] pitti: Also I've check that there are no issues with the burn [12:52] davmor2: oh! no d-bus running? [12:53] pitti: should dbus show up in ps aux? [12:53] 102 588 0.0 0.1 24480 2168 ? Ss 07:52 0:01 dbus-daemon --system --fork [12:53] something like this [12:55] nope only get the grep dbus showing up [12:59] bug #438936 seems to confuse quite some user [12:59] Launchpad bug 438936 in indicator-session "Should be able to lock screen with autologin" [Medium,Confirmed] https://launchpad.net/bugs/438936 [12:59] I don't get the design decision behind blocking screen locking for autologin configs [13:03] seb128: eh? so you can not lock your sesion at all with autologin enabled? [13:04] mvo, you can but ted decided that the session indicator would have the option not enabled [13:04] mvo, seems it's a design decision to not confuse users who don't remember their password or something [13:04] that does not sound like it makes a lot of sense (especially if ctrl-l keeps working) [13:04] mvo, I don't really get it... [13:05] I think the rational is that "you use autologin so you should never have to type a password" [13:05] or something around those lines [13:09] seb128: seems some netbook users dont remember their passwords :/ well thats what tedg said , not sure how he got that user feedback... for now , i autologin and then switch off the autologin ;p [13:09] that doesn't make sense to me [13:09] we still lock on suspend for example [13:09] and there is lot of valid reason to lock an autologed session [13:09] doesnt make sense for me either ;) [13:09] seb128: that sounds confusing; why wouldn't I want to lock my screen with autologin? [13:10] like being in a public place and letting the computer while getting a coffee or something [13:10] but "never having to type my password" != autologin.. [13:10] pitti, because you don't manage to remember your password [13:10] but you need it for admin stuff etc. as well [13:10] autologin is just a convenience for a clean session [13:10] but I guess I'm preaching to the choir [13:10] not sure if that comes from ted or is a design team suggestion [13:11] I will talk to ted again when he's around [13:11] pitti , seb128: mpt suggested some changes for that > Bug #436724 , but seems its not possible to get that done for karmic [13:11] Launchpad bug 436724 in indicator-session "lock screen doesn't work" [Medium,Fix released] https://launchpad.net/bugs/436724 [13:11] it should only be hidden when teh password is disabled [13:12] right [13:13] "It would seem like if you specifically ask it to lock, it should. On [13:13] the other hand, if you accidentally hit the menu item and you've got no [13:13] clue of your password, that's no good as well. [13:13] Thoughts? I'm leaning towards disabling the menu item with autologin." [13:13] bah [13:13] "I suggest that if someone sets themselves up to log in automatically, the "Lock Screen" command is insensitive by default." [13:13] designers... [13:14] well, forgetting your own password is a rather curious use case [13:14] mpt: also , why do you want the lock screen to be greyed out ? why not hide the option for users who auto-login ? this is not a static menu structure where users need to be familiar with , why not just hide it for those users? [13:14] I'm tempted to distro patch that out for karmic [13:14] we shouldn't disable important functionality to make it easier for people to not use computers in a secure manner [13:14] mac_v, that makes sense [13:15] but why do you want to prevent autologed users to lock their screen? [13:15] seb128: I'm fine with a quick distro patch, but eventually it should be fixed "upstream", too [13:15] that just makes no sense [13:15] seb128: I commented on that bug, but it's already closed; should we reopen? [13:15] mpt: kindly alter the suggestion then :) [13:16] mac_v, so that seb128 can "bah" at me again? :-) [13:16] pitti, there is an another bug [13:16] bug #438936 [13:16] Launchpad bug 438936 in indicator-session "Should be able to lock screen with autologin" [Medium,Confirmed] https://launchpad.net/bugs/438936 [13:16] seb128, because I thought they probably wouldn't know their password in that case [13:16] mpt, I don't bah at you especially, but preventing users to secure their box when they need to is weird [13:17] mpt: ;) .. but we might forget this and it might get implemented as-is :) [13:17] mpt, if you forget your password you have lot of other issues, like not being to do any admin tasks or to log into the box after suspend [13:17] mpt, it seems inconsistent to enforce that in the menu when suspend will lock the screen anyway for example [13:18] seb128, yes, this wouldn't be an issue for admins [13:18] mpt, it is right now in karmic [13:18] seb128, I never suggested that suspend should act differently! If someone can't lock the screen, suspending shouldn't lock the screen. [13:18] mpt: yeah , the suspend locks screen on resume [by default] [13:19] also the option to not prompt for password is very well hidden in the gconf [13:19] mpt, ok, that just seems an half working solution not clearly design, I would suggest letting the indicator session menu lock screen since that's not the right place to enforce that [13:19] seb128, yes, this whole mess has never been designed properly [13:19] if you want to disable screen locking that should be done in a consistent way over the session [13:20] ok, good [13:20] let's undo the indicator session change and work on proper changes next cycle [13:20] I will talk to ted when he's there [13:20] \o/ [13:24] seb128, any chance of including the fix for bug 432558 ? I have seen more people on #ubuntu+1 unable to login into msn, could be related to this bug for which a fix is already available [13:24] Launchpad bug 432558 in telepathy-butterfly "telepathy-butterfly crashed with UnicodeDecodeError in _print_MSG()" [Unknown,Fix released] https://launchpad.net/bugs/432558 [13:24] hum, wait, fix released ? [13:25] joaopinto, I think there was a mess with sponsoring request, 2 bugs opened, no debdiff and no reply to dholbach's comment on the other one [13:25] there was no evidente on the other one that it was the same bug [13:25] evidence [13:26] it's a one line diff, something easy to check [13:26] right, I will check with dholbach why he didn't upload and sponsor it later if there is no reason [13:27] ok, tks [13:28] kenvandine, could you look at bug #448300? what is the right component for ubuntuone addressbook issues [13:28] Launchpad bug 448300 in evolution "[Karmic] In the adressbook (contactbook) in Evolution Epost. I can not delete any adresses on Ubuntu One contact book. " [Undecided,New] https://launchpad.net/bugs/448300 [13:29] seb128, that should be evolution-couchdb [13:29] kenvandine, ok thanks, can you have a quick look and reassign? [13:29] seb128, rodrigo has fixed it in couchdb-glib already and has a fix for evo-couch too [13:29] sure [13:30] kenvandine, thanks! [13:30] good that I asked you, you seem to have a clue about the issue ;-) [13:31] :) [13:31] i should have a packaging branch for it in a bit [13:31] technically a holiday here, so will do it after i run some errands this morning [13:32] oh I didn't know, sorry about that, there is no hurry [13:33] no worries [13:33] it was on my todo list :) [13:34] seb128, so you probably won't see much of rick either :) [13:34] good, I will be able to get work done ;-) [13:34] oh, he's not around to read that, not fun then [13:38] seb128, can you sponsor bug 447162 [13:38] Launchpad bug 447162 in evolution-couchdb "Change notifications don't get to evolution UI" [Undecided,Fix released] https://launchpad.net/bugs/447162 [13:38] i think that fixes 448300, but i need to confirm that with rodrigo [13:39] will do some sponsoring when I'm done with weekend backlog [13:40] thx [13:40] * kenvandine runs out [13:51] kenvandine, seb128: I'll sponsor while seb128 is debugging something for me (fair trade :) ) [13:53] pitti, I think, we did not discuss the wiping out of cupsd.conf, we only discussed about maintainer scripts not to modify conffiles to avoid "conffile changed" questions during installation/update. === MenZa is now known as lhavelund === lhavelund is now known as MenZa [13:55] tkamppeter: http://irclogs.ubuntu.com/2009/10/07/%23ubuntu-devel.html, 14:49 onwards [13:57] seb128: #444421 is fixed. Robert was right, it tests fine...change is in bzr already [13:59] ok [14:04] pitti, sorry, let's go to another problem: In bug 444126 a user cannot print because a manufacturer driver package looks for libcupsys. [14:04] Launchpad bug 444126 in cups "Canon ip2600 Printer won't print, but Ubuntu says it is." [Undecided,New] https://launchpad.net/bugs/444126 [14:19] tkamppeter: replied in the bug [14:37] hey tedg [14:37] tedg, so it has been decided that indicator session should let autologed users lock screen [14:37] tedg, can you change that upstream or do we need to distro change it? ;-) [14:37] pitti: wrt bug 449454 cr3 is getting a mixed result so we are wondering if it might be a race condition :( [14:37] Launchpad bug 449454 in dbus "Ubuntu has no gdm and no xsplash on todays iso" [Undecided,New] https://launchpad.net/bugs/449454 [14:39] davmor2: it certainly is; I remember that we already have had the "dbus doesn't start" problem a few weeks ago (Keybuk will still painfully remember, I guess) [14:40] seb128: So what's your plan for users that use autologin and don't know their password? [14:40] tedg, we lock screen on let's say suspend anyway [14:40] seb128: Only with GPM, not from the session menu. [14:40] seb128: We should probably patch GPM then :) [14:41] tedg: suspend from indicate menu locks the session [14:41] tedg, it doesn't make sense to patch one software to not behave in a consistent way there [14:42] tedg, if you want to prevent screen locking you should do it for the whole session [14:42] ie change the gnome-screensaver key [14:42] pitti: With autologin enabled? It shouldn't. [14:42] tedg: I didn't try that [14:42] tedg, well it does when closing the lid [14:43] tedg, users who don't know their password is something that should not happen [14:43] you need to password in lot of cases [14:43] admin tools, unlocking, user switching [14:43] you need it anyway for gnome-keyring, admin, etc.? [14:43] if you want to allow a "no password" mode that's not by hacking around in indicator session [14:43] "should not" and "doesn't" are very separate cases. [14:43] you need to design that properly rather [14:43] pitti: Thinking more non-admin users. [14:43] the user who forgets the password is screwed [14:44] you still need to unlock your keyring [14:44] tedg: but if you really don't want a password, then you should lock/disable the password rather, no? [14:44] pitti: How do you lock/disable the password [14:45] ? [14:45] passwd -l [14:45] pitti: Without the command line :) [14:45] we never really supported that mode [14:46] if we want to introduce a concept of passwordless accounts, then we need to do that on all levels [14:46] What should happen on the LiveCD? [14:46] that does have an empty password [14:47] pitti: How do we test for that? [14:47] with normal user privs you can't really [14:47] tedg, why do you want to test? you can lock screen and unlock using enter [14:47] except for just trying [14:48] seb128: Because I don't want to tell someone they can "Lock Screen" if they can't. [14:48] i. e. piping '' into unix_chkpwd [14:48] but that leaves traces in auth.log [14:48] pitti: And just trying would be bad, right? [14:48] tedg, you can lock it, you just need an empty password to unlock [14:48] tedg: well, just noisy in auth.log, not really bad [14:49] seb128: Honestly, that would be the best security for me. I'd probably try "ubuntu" with a thousand different spellings before guessing no password :) [14:49] tedg, now is not time to try to solve those case for karmic, lot of places need a password there is no point to try to enforce something new in indicator session there [14:51] Well, you guys design it. How should it work? It would probably be easier to distro patch as it's probably a 1-2 line change. [14:52] Adding the checking for null password would take longer. [14:52] (but you knew that) :) [14:52] It seems like it should still be insensitive for guest sessions. [14:54] tedg: mpt is now considering not showing the option than making it insensitive [14:55] mac_v, actually tedg and I just discussed it [14:55] and I'm fine with just allowing locking for now [14:55] oh lol ;) [14:55] I didn't know it was allowed before. [14:55] mac_v: Well, my personal thought is that it should change to "Blank Screen" and activate the screensaver. [14:56] I like "Activate Screensaver" but that'd probably make the menu too wide. [14:56] tedg: but still its not as secure as screen locking ;) [14:56] "Save Screen" [14:57] it's like "Save Ferris" but won't infringe on any (C) or (TM) [14:57] dobey: Then we could have "Save Screen to Disk" for screenshots ;) [14:57] didrocks, do you think you will do the mutter update? [14:57] tedg: but what if i don't want to save it to disk? [14:57] tedg, you speak about cases with no password though right? because I've a password and I know it and I lock screen [14:58] maybe i want to save it to a lithograph to hang on my wall [14:58] tedg, and I don't get while you want to force me to let my laptop unlock at confs when getting coffee ;-) [15:46] Keybuk: is there anything else I can add to bug 449454? [15:46] Launchpad bug 449454 in dbus "Ubuntu has no gdm and no xsplash on todays iso" [Undecided,New] https://launchpad.net/bugs/449454 [15:48] davmor2: not following that bug [15:55] I want to step through some evdev xorg handling in karmic (found a regression somewhere between jaunty and karmic) [15:55] I installed the dbgsym packages [15:55] and all the files seem to be there [15:55] but gdb just spits out stuff like: [15:55] Reading symbols from /usr/lib/xorg/modules/input//evdev_drv.so...Reading symbols from /usr/lib/debug/usr/lib/xorg/modules/input/evdev_drv.so...done. [15:55] (no debugging symbols found)...done. [15:55] any idea what's going wrong? [15:57] seb128: I wanted to do it this week-end but I finally saw it has been synced from debian unstable [15:57] didrocks, synced? [15:58] let me searched again. I have some debian sources in my sources.list I've maybe not checked that [15:58] just remind that now we are speaking about it :) [15:59] yeah, next time, I will comment those lines in my sources.list (apt-pinning seems to not work with deb-src) [15:59] so, I'll do it this evening, shouldn't take long [16:00] didrocks, thanks [16:22] * asac nm debugging bbl [16:30] seb128, pitti: care to take care of bug #449615 please? :) [16:30] Launchpad bug 449615 in ubuntuone-storage-protocol "Please update to 1.0.0" [Undecided,Confirmed] https://launchpad.net/bugs/449615 [16:30] I will do sponsoring later [16:30] debugging some other things right now [16:34] seb128: ok, cool [17:35] cking: ping [17:36] pgraner, hi [17:36] cking: I tried to swap out the POS broadcom on my HP mini and it has a whitelist of allowed cards it wouldn't boot with the intel card in it [17:37] :-/ [17:38] That's disappointing. What's wrong with the broadcom, apart from being unmaintainable binary blob? [17:38] cking: not very stable at close range to the AP (like my office) [17:38] cking: just thought you'd like to know [17:38]