[00:00] JohnNapster_: I am not sure, but I think it related to something called PAM (not entering in much technical detail) [00:00] I will try to reproduce, and then we will know better [00:01] sudo-related? [01:15] hggdh: still here? [01:15] i was watching Top Gear on the telly [01:16] anyway... i don't know whether this issue is sudo related [01:19] when you will install Ubuntu 11.10 in your machine... create an account and set a password for it... once installed, go to User Accounts... [01:20] and in there, change the password of your account to None [01:22] restart your machine and now observe that you will not be able to login to that account of yours [01:22] JohnNapster_: I will try that -- but tomorrow, today I am due a double pure malt [01:22] okay [01:22] and thank you for the steps to reproduce [01:23] * hggdh loves top gear [01:23] if you will be able to reproduce the bug, please file a bug report [01:23] * JohnNapster_ too :) [01:23] will do. I do not like the effect this has [01:23] it's a nasty bug [01:23] but I was watching american idol, SO required me to tonight ;-) [01:24] oh that :P [01:24] it is, even if I think admin account should never be without a password, this break bad [01:24] you see? [01:24] it's a regression bug [01:25] you'll notice it in 11.04 as well [01:25] not yet, tomorrow, I was behind on some due tasks. I do apologise for the delay, but I will get there [01:25] ihope this gets fixed before 12.04 final [01:25] yes, I thought it looked like a regression. I do not remember hearing about this before [01:25] me too [01:26] anyway, i'm off to bed (2.26 a.m. here) [01:26] heh. Cheers, sir [01:26] that's because no one ever changed his password to blank :P [01:26] oh, not a lot of people do that [01:26] s/not// [01:27] maybe not on admin group accounts ;) [01:27] this is commonish [01:27] it is? [01:27] why wasn't it ever reported? [01:27] even on admin accounts -- most folks that install Ubuntu install it on the personal box [01:27] so only one account, ergo admion [01:27] admin, even [01:27] hmm [01:28] but I am mostly a console guy, so I do not pay too much attention to the graphic piece [01:29] can you try making the password be blank and also make the Automatic Login be True and then another time be False (still having the blank password) [01:29] please play a bit with this [01:29] you mena a null password [01:29] I will [01:29] yup [01:30] dammit, the wisky is already working [01:30] cannot tupe for me life [01:30] ah rats [01:30] you're irish i presume? [01:31] i nice lad :) [01:31] no, not at all. Just the wisky (or wiskey) [01:31] heh [01:31] now that whiskey is running in your vains, you're half irish :D [01:32] most certainly. Although, to be honest, Ireland sounds like a nice place [01:32] but the language, oh the language... [01:33] well, it's quite nice [01:33] i hear it on the tell [01:33] telly [01:33] heh [01:33] i find it amusing :) [01:34] got to see the bloody show again, beatuful JLo is talking [01:34] the american idol? [01:35] anyway, please test that nasty bug tommorow [01:35] i really am going now :) [01:35] bye, talk to you later [01:36] * JohnNapster_ thinks JLo is so fuc*ing hot :P [05:38] Hey folks, I'm not sure if I am in the right place but here goes. I keep getting assigned to some Lubuntu bugs and I have no idea why that would be, how do I figure out why this is happening? [08:45] can anybody please triage & raise importance of bug 885730? [08:45] Launchpad bug 885730 in gnome-settings-daemon "keyboard layout indicator reacts incorrectly" [Undecided,Confirmed] https://launchpad.net/bugs/885730 [08:45] as someone said, "I survived Unity migration, but not this "tiny" bug" :) [09:13] mitya57, can you work me through the steps to reproduce? i can't seem to here [09:14] brednand: https://bugs.launchpad.net/gnome-settings-daemon/+bug/885730/comments/4 [09:14] Launchpad bug 885730 in gnome-settings-daemon "keyboard layout indicator reacts incorrectly" [Undecided,Confirmed] [09:14] mitya57, i have two keyboard layouts, en (uk) and en (us) [09:14] mitya57, yeah i saw that - but they don't reproduce the bug [09:14] this should still work for you... [09:14] strange... [09:14] right now it's on EN [09:15] which is the default one for you (i.e. actually used for new windows?) [09:15] EN [09:15] i mean UK [09:16] so can you change the layout of your chat window to US, and open [09:16] a gedit window, and see if the indicator changes? [09:16] (it should change to uk if it's used for new windows as you said) [09:17] that's not the bug i'm reading though [09:17] if that's the bug then you guys are way overcomplicating the description [09:17] I agree [09:18] but from the description: "mappings which is used is often not the same as indicator shows" [09:18] but still, did you manage to reproduce it? [09:18] but the mapping used is always what the indicator shows for me [09:19] and i had 'use the same mapping for new windows' [09:19] happy to hear that you're not affected by this :) [09:20] anyway, seb128 said that charles will look at it. [09:21] brendand, mitya57: that bug is confusing [09:21] do you guys use a by win layout? [09:21] seb128, it's deeply confusing [09:21] seb128, i can't reproduce it because i have no idea what they're saying [09:22] well I understand what they say [09:22] my settings are: [09:22] seb128, i'm not affected, just a traiger trying to reproduce [09:22] [x] per-window layouts [09:22] they say "in some cases the label indicating the current layout is not reflecting the right layout" [09:22] [x] use default layout for new windows [09:22] mitya57, ok, I guess that's the issue [09:22] seb128: that's true for me [09:22] default is "same layout for all" [09:23] which is what I use [09:23] the "per-win layout" concept by itself is confusing :p [09:24] I had to enable it to workaround another bug that was in maverick long time ago... [09:24] seb128, for me the per-window aspect is broken in itself [09:24] seb128, if i follow the steps in comment 4 then when i open the terminal it is still set to 'other' === vivek is now known as Guest30550 === Guest30550 is now known as pvivek === greyback is now known as greyback|lunch [12:26] Hallo. I just got the following during a update of precise: http://paste.ubuntu.com/875964/ but I don't have kde-telepathy installed. What should I report that against? [13:35] hggdh: hello, are you here? === greyback|lunch is now known as greyback [13:41] JohnNapster: yes, I am, sort of [13:43] did you manage to file that bug report? [13:46] no, not yet. But I will get it done today [13:46] great === JanC_ is now known as JanC === vivek is now known as Guest78341 === Guest78341 is now known as pvivek === zyga is now known as zyga-afk === dshufelt is now known as dsmitty === zyga-afk is now known as zyga === bulldog98_ is now known as bulldog98 === darkchar1 is now known as darkcharl === jalcine_ is now known as jalcine [19:47] hey all, I'm looking at bug 951033, which seems to be the same as bug 870150, which says there is a fix committed in Ayatana Design, but I can't really find a link to this fix in that project. So my question is, should I just confirm the bug (I've experienced this too), or make it a duplicate? [19:47] Launchpad bug 951033 in unity "deleted files displayed in unity" [Undecided,New] https://launchpad.net/bugs/951033 [19:47] Launchpad bug 870150 in unity "Dash - files deleted by dragging and dropping the file from the Dash to the Trash are not removed from the Dash" [Medium,Confirmed] https://launchpad.net/bugs/870150 [19:52] matthew-parlette: If it is a duplicate (the bug described is the same then go ahead and mark in duplicate) [19:55] I was thinking that they are two methods of getting to the same error, so I wasn't sure. But thinking through it, it would make sense to make it a duplicate [19:55] Thanks for taking a look at it === zyga is now known as zyga-weekend === ashams is now known as Guest59082 [20:48] Whoever have an AirPlay device check this : https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/951120 [20:48] Launchpad bug 951120 in pulseaudio "AirPlay - AirTunes (Airport Express) support stopped working on precise" [Undecided,New] === jalcine is now known as JackyAlcine === JackyAlcine is now known as jalcine [22:00] Good evening all. :) I think bug 659344 can be marked Triaged since it a) is easily reproducible b) logs are attached c) also reported in Debian. [22:00] Launchpad bug 659344 in billard-gl "[Maverick] Billard-gl crashes when attempt to configure video" [Undecided,Confirmed] https://launchpad.net/bugs/659344 [22:13] hjd: is the [Maverick] bit in the title necessary or accurate? [22:18] bdmurray: hm, that can probably be trimmed out. I was able to reproduce it in Precise, and since the package has the same version number I would expect all releases to be affected... [22:19] hjd: and do you have a thought on the importance? [22:26] bdmurray: I am not sure. It crashes, which is pretty severe, but it only seem to happen in this specific instance so I'm torn between Medium and Low... [22:29] I'm going to set it to Medium [22:31] thank you :) [22:34] bdmurray: Do you think it would be a good time to submit a control app or should I perhaps wait longer? [22:34] bkerensa: I haven't been following your work closely === yofel_ is now known as yofel [22:38] * bdmurray does some stalking [22:41] hggdh: when you are going to fix your greasemonkey gmane follower? [22:56] bdmurray: ok well I submitted anyways :) thanks for your consideration and that of the rest of the team [23:02] bdmurray: I did not even know it was broken... [23:03] bdmurray: adding in the TODO [23:04] hggdh: heh I'll look at it again my javascript is getting a bit better [23:05] bdmurray: no matter how bad it is, it will still be better than the GM script, it was my very first JS ever [23:05] :-) [23:05] I will buy a beer for whomever fixes the Chrome Greasemonkey :) with Chrome having a majority share of the browser market and Adobe EOL'ing Flash for everything except Chrome it seems the way to go [23:05] :D [23:13] hggdh: mark it off your list ;-) [23:14] * hggdh rubbers it off [23:14] bdmurray: that easy? [23:14] hggdh: yeah just a modification to replace on a string [23:15] cool [23:15] beats me why I didn't fix it earlier