[00:19] <charlie-tca> anything that can be done with this? see last comment bug 34508
[09:03] <BUGabundo> guud murning
[09:03] <BUGabundo> where should I file laptop touchpad bugs?
[09:09] <BUGabundo> I found this anoyning bug where if I click and scroll a sidebar, then let go the 2nd finger, if I try to scroll again it will fail
[09:09] <maco> BUGabundo: xserver-xorg-input-synaptics, most likely
[09:10] <BUGabundo> thanks girl
[09:13] <BUGabundo> maco: filed as bug 323519
[09:34]  * Laibsch bugs those with the power to change wrt bug 221010
[09:35] <Laibsch> Trivial fix
[09:59] <tawmas> Hi!
[09:59] <tawmas> I'm unable to use music CDs with latest Ubuntu 9.04 updates. It brings up a dbus error, and I can't figure out if the problem is with gvfs, hal or dbus.
[09:59] <tawmas> The error is quite long, do we have a preferred pastebin for this channel?
[09:59] <maco> pick one
[09:59] <tawmas> Or do I paste it here?
[09:59] <tawmas> maco: k
[09:59] <maco> use a pastebin, but which one is up to you
[10:00] <tawmas> http://pastebin.ca/1323527
[10:06] <maco> tawmas: i wonder if that could be smething in policykit...
[10:06] <maco> check your system -> administration -> authorizations and make sure nothing weird has changed to disallow you from using removable media
[10:06]  * tawmas goes looking
[10:09] <maco> and is it *only* music cds? or do audio cds misbehave as well?
[10:10] <tawmas> maco: under "Mount file systems from removable drives" I see "Active console: yes" under implicit authrizations, and no explicit authorization
[10:11] <tawmas> I need to check that. For a while I wasn't able to eject the CD, so I stopped trying anything else
[10:12] <maco> i didnt mean audio
[10:12] <maco> that was redundant
[10:12] <maco> do data cds misbehave
[10:12] <tawmas> Oh, it's so automatic that I forgot... I have an external USB drive that I turn on as soon as I login. It got mounted
[10:12] <tawmas> I'm trying a data CD now
[10:13] <tawmas> Same symptoms
[10:15] <tawmas> I've just tried an USB stick, and it got mounted
[10:16] <tawmas> It gets more wierd
[10:18] <tawmas> I have a second optical drive. If I put a data CD inside this one, it gets mounted, if I put a music CD, it says "Unable to mount Audio Disc. Drive /dev/sr0 does not contain audio files
[10:25] <mangilimic> hello! I've a doubt. bug #323543 . The user is using Ubuntu 7.10 and he reports an issue which involves audacious. He knows that this problem can be solved upgrading to 8.10. I've tried to reproduce this bug with ubuntu 8.10 but it works great for me. So is it correct to mark this bug report with status Fix Released ? Thanks in advance.
[10:25] <mangilimic> https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/323523
[10:26] <mangilimic> The correct bug number is 323543
[10:26] <mangilimic> (oops) The correct bug number is 323523 not 323543!
[10:27] <MrKanister> mangilimic: You can mark it as "invalid" since we don't know which code change fixes it
[10:28] <mangilimic> MrKanister: thanks, I suspected that "Invalid" was a better choice instead of "Fix Released".
[10:29] <MrKanister> mangilimic: You can also suggest that the bugreporter requests that package to be backported, but since Ubuntu 7.10 will be outdated in some moths I don't think that it will be worth that
[10:30] <mangilimic> MrKanister: I hope that the user won't get angry with me!
[10:30] <tawmas> maco: I also see lots of errors in dmesg, I think this is hardware-related. I'll need to investigate deeper
[10:31] <mangilimic> MrKanister: which is the best place to request a backport?
[10:31] <MrKanister> mangilimic: Don't worry, there is no reason for him being angry if you tell them why you close the bug ;)
[10:31] <MrKanister> mangilimic: backporting information can be found on https://help.ubuntu.com/community/UbuntuBackports#request-new-packages
[10:31] <mangilimic> MrKanister: great! Thanks a lot!
[10:31] <MrKanister> mangilimic: but as I said: It's probably not worth it
[10:32] <MrKanister> mangilimic: You're welcome
[11:14] <dhazin> Hi all! could u please help me, though it's a kubuntu issue.. I'm trying to resolve this issue several days but without any success so far :(
[11:14] <dhazin>  here is a topic on kubuntu forums http://kubuntuforums.net/forums/index.php?topic=3101259.0
[11:15] <dhazin> shortly I can't login to kde4.2, it returns back to login screen
[11:15] <dhazin>  here is my .xsession-errors: http://paste.ubuntu.com/112019/
[11:41] <Laibsch> Does one get Karma for being assigned a bug?  It's about the only logical explanation I can find for this guy: https://bugs.launchpad.net/~txwikinger assigning himself such a vast number of bugs which if he were even capable of doing it would probably require him a couple of years to actually do
[11:42] <Laibsch> sorry, numbers are much smaller, was looking at "related bugs" 758 instead of assigned bugs (just 33)
[11:43] <Laibsch> I still wonder
[11:43] <Laibsch> Does anyone know this guy?
[11:43] <Laibsch> I asked him in one or two bugs whether he was indeed working on the bug, but never got a response
[11:44] <Laibsch> I am thinking of asking him once more and then mass-unassigning him.  I'm afraid he may induce hesitation in those actually capable of fixing the bugs
[11:45] <Hobbsee> Laibsch: yeah, he's a kubuntu / ichtux guy.
[11:45] <Hobbsee> *ichthux
[11:46] <Laibsch> OK
[11:46] <Laibsch> That is good
[11:46] <Hobbsee> https://edge.launchpad.net/~txwikinger/+participation
[11:46] <Laibsch> Yes, I checked a bit of his background
[11:46] <Laibsch> Which is is when I stumbled on his large Karma
[11:46] <Hobbsee> iirc he'd gotten a bit busy, but he's still around every once in a while
[11:47] <Hobbsee> you'd probably do better to email directly
[11:48] <Laibsch> Well, I'm just trying to fathom if he has the right understanding of "assigned" and that assigning something to yourself without actually working on it is detrimental
[11:48] <Laibsch> I hope he understands that
[11:48] <Hobbsee> i'm sure he does
[11:49] <Hobbsee> however, you can probably hijack bits as well, if you mail first, and get a positive reply.
[11:49] <Hobbsee> otoh, there are lots of other bugs
[11:51] <Laibsch> I don't want to hijack any bugs
[11:51] <Laibsch> I'm just triaging and looking through "my" bugs
[11:51] <Laibsch> The ones where I have commented and stuff
[11:52] <Laibsch> But the need for hijacking should not exist, this is what I meant by detrimental
[11:52] <Laibsch> He's creating unnecessary hurdles for bugs to get fixed
[12:49] <LimCore> hi
[12:50] <BUGabundo> LimCore: hi
[14:17] <cornucopic> I have attached my patch at https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/321863
[14:17] <cornucopic> What is the next process so that it gets fixed and committed ?
[16:03] <jgoguen> https://launchpad.net/bugs/259678, user doesn't use Thunderbird past Feisty, I can't reproduce in Intrepid, and I can't find a report on Mozilla bugzilla...should this bug be set Invalid because an update appears to fix it?
[16:07] <Rocket2DMn> jgoguen, he is using an unsupported version of ubuntu
[16:07] <Rocket2DMn> user needs to try in the latest release
[16:09] <jgoguen> Rocket2DMn: I asked already to try in a later release, he just replied that he doesn't use Thunderbird in anything later than Feisty
[16:10] <jgoguen> should I ask him then to try anyway on one of his machines that is on a supported version?
[16:11] <Rocket2DMn> jgoguen, then the bug should probably be invalidated
[16:11] <hggdh> jgoguen, the reporter has already said he will not try on another version...
[16:12] <jgoguen> hggdh: that wasn't the impression I got from it, sorry
[16:12] <hggdh> hum. Is Feisty still supported?
[16:12] <Rocket2DMn> feisty reached EOL last fall
[16:12] <jgoguen> Rocket2DMn: ok, I'll do that
[16:13] <hggdh> jgoguen, state the user is free to reopen if this happens on a newer (and still supported) release
[16:13] <jgoguen> ok
[16:14] <hggdh> (and, of course, be nice) ;-)
[16:14] <jgoguen> always :)
[16:15] <hggdh> jgoguen, another thing: if you are willing to try, check the Thunderbird's changelog for a change that might address this
[16:15] <hggdh> if you find it, add in the comment that this may have been solved by <whatever>
[16:15] <jgoguen> hggdh: would that necessarily be on their bug tracker?  I couldn't find anything addressing this on their side
[16:15] <jgoguen> I did see something where FTP links in general weren't clickable
[16:16] <hggdh> it would probably be in the Thunderbird's changelog
[16:16] <jgoguen> ok
[16:16] <hggdh> well, in this bug the FTP links *are* clickable, they just act wrong
[16:24] <MrKanister> what is happening to bug #128165? The last comments seem auto-generated
[16:24] <MrKanister> I think it is spam
[16:29] <hggdh> not really spam, but probably someone's configured their email client wrong. The message says something like "we received your request, and you will receive a response later"
[16:29] <hggdh> sucker set an auto-response... since the sucker gets an email about the auto-response, the email is (again) auto-responded
[16:30] <MrKanister> lol...like recursion
[16:30] <hggdh> it *is*. Look at the comments headers ;-)
[16:30] <MrKanister> yep, I noticed the Re, Re, Re, Re...
[16:31] <MrKanister> what to do with it? I mean, There will be a comment every 10 min
[16:33] <hggdh> I just put a request to #launchpad to take care of it
[16:35] <hggdh> of course, now we have to wait for someone to read the request... meanwhile there is not much you can do, except unsubscribe
[16:35] <MrKanister> Ok, thank you
[18:28] <thomasdelbeke> Hi there
[18:29] <thomasdelbeke> I did a backtrace on 264323
[18:29] <thomasdelbeke> Is it a duplicate of 252046?
[18:29] <thomasdelbeke> I am looking for pastebin now
[18:29] <thomasdelbeke> !pastebin
[18:30] <jpds> bug 264323, bug 252046
[18:31] <thomasdelbeke> correct
[18:31] <thomasdelbeke> it is uploading
[18:31] <thomasdelbeke> http://paste.ubuntu.com/112184/
[18:32] <thomasdelbeke> It is a segmentation fault
[18:32] <thomasdelbeke> I cannot do valgrind I fear
[18:33] <thomasdelbeke> as I do no longer have the crash report
[18:33] <thomasdelbeke> not strace ...
[18:33] <hggdh> yes. Unfortunately, the backtrace is worthless, since there are no symbol resolution
[18:33] <thomasdelbeke> Is that correct?
[18:33] <thomasdelbeke> Yeah ...
[18:33] <thomasdelbeke> So?
[18:33] <thomasdelbeke> Invalid?
[18:34] <thomasdelbeke> hggdh, I was logging off yesterday, but you wanted to tell me something still?
[18:35] <hggdh> thomasdelbeke, no, we were all done. On your backtrace, there is nothing that can be used; also the two bugs you show have a SEGV on different places
[18:35] <thomasdelbeke> ok, mark invalid?
[18:35] <hggdh> so it is better to assume they are not duplicates
[18:36] <thomasdelbeke> ok
[18:36] <hggdh> on your bug: can you still reproduce it?
[18:37] <thomasdelbeke> nope
[18:37] <thomasdelbeke> I did it on the coredump
[18:37] <thomasdelbeke> It has been ages
[18:37] <hggdh> so you can state you cannot experience it anymore; Also state the current version of the g-h-v-m.
[18:38] <thomasdelbeke> attach that to the bug report?
[18:38] <hggdh> for whatever reason the core was not processed by the LP retracer. At this point in time, it is difficult to believe it will still be able to be retraced
[18:39] <thomasdelbeke> ok, one problem:
[18:39] <hggdh> you can attach the apt-cache output for gvfs-hal-volume-monitor there
[18:40] <thomasdelbeke> http://paste.ubuntu.com/112187/
[18:40] <thomasdelbeke> it is not a package
[18:41] <hggdh> sorry, the package is gvfs
[18:42] <thomasdelbeke> http://paste.ubuntu.com/112189/
[18:42] <thomasdelbeke> so attach apt-cache policy of gvfs?
[18:42] <thomasdelbeke> + state not reproducible?
[18:42] <hggdh> like this: http://paste.ubuntu.com/112190/
[18:43] <hggdh> "I cannot reproduce this issue anymore"
[18:43] <thomasdelbeke> Ok thanks! Terminate conversation?
[18:43] <thomasdelbeke> ok
[18:43] <hggdh> :-) yes, I guess
[18:43] <thomasdelbeke> cheers, see you
[18:45] <thomasdelbeke> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/264323 (done)
[19:27] <maco> if there's no .pot file, do i have to update the msgid in every .po file to update a help file in gnome? or do i just update the main .xml?
[19:52] <maco> hggdh: you around?
[20:23] <hggdh> maco, yes
[20:26] <diakopter> I'm using the latest jaunty nightly; llvm build from source succeeds for me when ocaml* are not installed, but it fails for me when ocaml* are installed.  how do I report such a thing? it appears it doesn't attempt to build the ocaml bindings (or the documentation) if ocaml* are not installed.
[20:27] <hggdh> diakopter, are you building from the source packages?
[20:27] <diakopter> hggdh: yes
[20:27] <maco> hggdh: you commented on bug 208763 that the help files that need to be changed are part of seahorse. do you know which files need to change? do i have to change all the msgid's in all the .po files?
[20:27] <diakopter> hggdh: llvm_2.4-1~exp1ubuntu2.dsc
[20:27] <hggdh> diakopter, report it as a FTBFS on llvm
[20:28] <hggdh> related to the presence of ocaml
[20:28] <hggdh> maco, let me see it
[20:28] <maco> hggdh: if you look in http://package-import.ubuntu.com/s/seahorse/jaunty/files/head%3A/help/ there's no .pot
[20:29] <diakopter> hggdh: cool; thanks. also, I can't find a way to get the ocaml bindings from debian/ubuntu...? maybe they should be packaged as a separate .deb?
[20:30] <hggdh> diakopter, check if they are part of the source ocaml; there will be probably a comment there about it
[20:30] <diakopter> part of the source ocaml?  they're part of the llvm source
[20:30] <hggdh> sorry, then on the control or rules for llvm
[20:31] <hggdh> maco, somehow they have to export the strings
[20:31] <hggdh> perhaps an autoconf thing?
[20:31] <maco> hggdh: i thought maybe im just supposed to change C/seahorse.xml but im not sure if i also have to go through */*.po and change the msgid in there too
[20:32] <maco> (i'm not quite sure how rosetta works either)
[20:32] <hggdh> let me look on what they have upstream
[20:32] <hggdh> heh. On rosetta, the only thing I know is it was discovered a looong time ago ;-)
[20:33] <maco> i know how to submit suggested translations in rosetta, and that's it
[20:35] <hggdh> eeek! I ran 'sudo apt-get build-dep seahorse'... and it wants to remove gnupg2!
[20:35] <hggdh> and kleopatra...
[20:35] <diakopter> hggdh: should I report the FTBFS on llvm in debian or launchpad?
[20:36] <hggdh> diakopter, if it is an Ubuntu package, on LP
[20:36] <hggdh> (and it seems so)
[20:36] <diakopter> debian experimental has llvm_2.4-1~exp1
[20:37] <hggdh> and we have ~exp1ubuntu2, so there is at least one local change
[20:37] <diakopter> hggdh: ahh... okay.  I understand, now. thanks for your help :)
[20:40] <hggdh> maco, I am looking now at the trunk code. I think this gets generated there
[20:41] <maco> yeah dtchen said he thought the .po files were coming from upstream. that still leaves me wondering the scope of the changes necessary
[20:44] <hggdh> maco, it seems that after you make the change to the string (in the source code) it will be reflected under the ./po directory by the basic build process
[20:45] <hggdh> yes, it is built during autoconf time
[21:01] <hggdh> maco, under ./po, make update-po
[21:02] <hggdh> and you will get the seahorse.pot
[21:02] <maco> and then i edit that?
[21:03] <hggdh> well... poor me, not sure. This is as far as I went. But the .pot is generated from the source code, so I guess you would change in the source
[21:03] <hggdh> and then update-po
[21:04] <hggdh> where is the string you want defined?
[21:04]  * hggdh never did translation
[21:05] <hggdh> except, long time ago, for pgp-international
[21:05] <LimCore> are there any plans to have Xorg stop displaying garbage>?
[21:06] <LimCore> I see this bug for over a year, on several boxes (and all 3 I own now) on intells, nvidias
[21:07] <maco> LimCore: define garbage?
[21:08] <maco> hggdh: im trying to change the base string, not the translation, though
[21:08] <maco> hence the confusion
[21:09] <LimCore> can I tag it as "epicfail" since it seems it is present on ALL cards (nvidia, intell AND readeon)?
[21:09] <LimCore> maco: my problems are similar as to thoes in https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/155116
[21:11] <maco> radeon 9700s can be nvidia and intel? news to me...
[21:11] <LimCore> maco: 9700s can not be nvidia nor intel
[21:11] <LimCore> and reading what one written is a nice thing to do
[21:12] <maco> >< note the invisible "</sarcasm>"
[21:12] <maco> and no, its not present on all cards
[21:12] <LimCore> I have this issue on nvidias and radeons
[21:12] <LimCore> yes, it is
[21:12] <LimCore> erm
[21:12] <maco> ive used intel for 2.5 years on two machines, and ive neve seen it
[21:12] <LimCore> I have on nvidias and intels
[21:12] <maco> er..3 machines
[21:12] <maco> i865, i945, and i965
[21:12] <LimCore> well I have two fresh intel laptops here and this happens here.  Perhaps it does not affect ALL laptops out there
[21:13] <LimCore> I have i915, and something recent /have to check/
[21:13] <hggdh> maco, yes. You change the base, then you run {cd ./po; make update-po} and you get your brand new .pot
[21:13] <maco> and i was making a joke about the bug saying it happens on radeons and you saying "ati, nvidia, and intel" as if radeons were made by all 3
[21:14] <maco> hggdh: but the .pot isnt in the source package, so how does that factor into a debdiff?
[21:14] <maco> or are there no debdiffs involved in this case?
[21:15] <hggdh> there should be, since you are changing the source. But, in this case, the folks at rosetta will have to finish up the additional translations before you can build the package again (I guess, I am not sure how we do local translations in Ubuntu)
[21:17] <hggdh> so -- and still guessing -- you would provide the POT to rosetta, translations would be done, and you would get them and then debdiff
[21:17] <hggdh> there has to be some official doc on how this is done... I just do not know where :-(
[21:21] <maco> yeah....ive never seen any docs on string changes
[21:28] <LimCore> hggdh: https://bugs.launchpad.net/ubuntu/+bug/323720
[21:36] <LimCore> https://bugs.launchpad.net/ubuntu/+bug/309747 looks interesting too. indeed 3d desktop on ubuntu seems to be full of glitches
[21:43]  * maco rolls eyes
[21:43] <hggdh> LimCore, what abut 323720?
[21:43] <maco> such a descriptive bug title...
[21:46] <LimCore> hggdh: it defines the random garbage
[21:47] <hggdh> LimCore, could you get a screenshot/video showing it?
[21:48] <LimCore> hggdh: ok I will try, but it dissapears quickly
[21:48] <hggdh> thanks
[22:13] <LimCore> hggdh: this is a well known EPIC bug: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/254468
[22:15] <LimCore> imho this bug is critical. Can we do something to have this fastly fixed in 8.04 and .10?
[22:15] <LimCore> *because of security exposure
[22:23] <hggdh> LimCore, it is being actively pursued, although I am still sort of unsure of security exposures
[22:23] <LimCore> this is the bug I know for a year \o/
[22:23]  * LimCore facepalms epically and switches to DOS...
[22:24] <hggdh> yes, it does seem very similar to yours
[22:24] <LimCore> hggdh: are you kidding me:  I can walk up to a password-locked terminal of coworker, move mouse, and see secret documents.  or son can walk up to dads locked station, move mouse, and see hardcore pri0n
[22:24] <LimCore> its like the definition of security exposure
[22:24] <hggdh> show it, then it will be accepted as a security issue
[22:24] <LimCore> hggdh: I belive the other gazilion people commenting there did show it already :)  what more is needed?
[22:26] <LimCore> random parts of pixmap / texture / whatever memory at shown  1) at random  2) when showing password input for locked station
[22:26] <hggdh> LimCore, do you run KDE?
[22:27] <hggdh> this does not happen to me under gnome
[22:27] <LimCore> I seen this moslty on kde, but also on gnome (8.10 clean install)
[22:27] <LimCore> no wait, ok this was gnome too
[22:28] <hggdh> I never saw it on Gnome
[22:29] <hggdh> and -- if you feel strongly about that, you could change it to a security exposure. I think it might be a *potential* privacy issue, but I am unsure if it is a security one
[22:30] <LimCore> if it is privacy then it is also security, no?
[22:30] <maco> oh oh
[22:31] <hggdh> no. privacy and security (although some times they go together) are very different things
[22:31] <maco> if i lock screen and close the lid (so it suspends) before it finishes activating the screensaver, when i resume itll show my desktop for about 3 seconds til i move the mouse and remind it that it was supposed to be activating the screensaver
[22:31] <LimCore> security is superset of it imho
[22:31] <LimCore> maco: here you see
[22:32] <hggdh> the other way around, LimCore. Privacy is one aspect looked at on Security
[22:32] <LimCore> so many people have this bug.. for year(s) lol... fail :(
[22:32] <maco> LimCore: when bugs are marked security bugs, it means remote-exploit-possible, usually
[22:32] <maco> hggdh: er, thats the right way around
[22:32] <maco> hggdh: if security is the superset, then privacy is part of security
[22:32] <hggdh> ugh! <blushes/>
[22:32] <LimCore> hggdh: then better provide different security flags
[22:32] <maco> LimCore: not for years for me. only with jaunty
[22:32] <LimCore> security-exploit
[22:32] <LimCore> and security-expostion  or something?
[22:32] <loic-m> When a bug has been submited in an old release for a package that's not in the repos anymore (removed from Debian repos), can we close the bug?
[22:33] <LimCore> maco: I first seen this bug afair on debian in like 2007 mid
[22:33] <maco> loic-m: if its not reproducible in the current version
[22:33] <LimCore> actualy!
[22:33] <LimCore> then this bug was on gnome, hggdh (about screensaver)
[22:33] <maco> yeah i was using gnome
[22:33] <maco> i only started using kde yesterday
[22:33] <hggdh> I did not say it was not. I said I never saw it
[22:33] <LimCore> maco: can you please confirm the MASTER bug as privacy (security?) problem alson in GNOME?
[22:34] <maco> its been nearly a full 24 hours. thats the longest amount of time i've ever been able to stand kde.
[22:34] <LimCore> lól. why so, kde is nice.
[22:34] <hggdh> heh
[22:34] <hggdh> maco, when this happens you ca read what was on the screen?
[22:34] <maco> hggdh: yeah, i could read my email the first time i noticed this
[22:34]  * LimCore opens massive pr0n collection + readies a photocamera, for the debuging purposes
[22:35] <hggdh> ugh
[22:35] <maco> i dont know if it still happens...this was before christmas
[22:35] <maco> and using compiz may have had something to do with it
[22:35] <maco> because it slows down screensaver activation
[22:35] <hggdh> then there is a clear risk of a security/privacy exposure
[22:35] <LimCore> 1. watch p0rn    2. lock station   3. invite children  4. sue ubuntu  5. PROFIT  6. ???  7. World domination
[22:35] <loic-m> maco: there's no version in Jaunty, the package has been removed from Debian in dec 08, however it's still in Intrepid
[22:35] <maco> put the underpants back, gnome
[22:36] <maco> loic-m: oh if its still in a supported release, leave it alone
[22:36] <hggdh> loic-m, then the package is still supported at least on Hardy and Intrepid
[22:36] <loic-m> hggdh, maco, thanks
[22:36] <maco> if we were talking about something in breezy...
[22:36] <LimCore> maco: write that in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/254468 comments plz, it will be helpfull
[22:37] <maco> LimCore: how does my mail client qualify as garbage?
[22:37] <LimCore> hggdh: should I make separate sub bug of this MASTER and describe there privacy exposure aspect?
[22:37] <hggdh> LimCore, you can also state your case at #ubuntu-hardened
[22:37] <maco> wait hold on
[22:37] <maco> it says released on jaunty
[22:37] <maco> lemme check the date because as i said this was over a month ago
[22:38] <hggdh> yes, and ScottK was suggesting a SRU
[22:38] <maco> oh so i should say that since i could read my email for about 3-5 seconds before logging in, it should be SRU'd?
[22:38] <hggdh> but I certainly would not call it an epic exposure.
[22:38] <hggdh> no
[22:39] <maco> heh im confused. what do y'all want me to do?
[22:39] <maco> LimCore: or did you want me to write the underpants gnome comment?
[22:39] <hggdh> If you can see what's on the screen, then this raises the ante
[22:39] <maco> (joking)
[22:40]  * hggdh just wishes happiness to maco
[22:40] <LimCore> maco: confirm that this happens as well on gnome, and that on GNOME you where able to see the private emails on a LOCKED station
[22:41] <maco> ok commented
[22:42] <LimCore> thx
[22:50] <hggdh> LimCore, nice user case ;-)
[22:53] <maco> hggdh:  what usecase?
[22:53] <hggdh> on the bug
[22:53] <hggdh> or in the bug
[22:53] <LimCore> ;)
[22:53] <maco> ah, i give up on this quassel thing. too many places full of text. back to irssi. brb
[22:54] <maco> haha
[22:55] <hggdh> no quassel anymore?
[22:55] <maco> no
[22:55] <maco> there were TWO panes showing texts and i dont know why
[22:56] <hggdh> to be sure you read it, perhaps?
[22:56] <maco> and i couldnt /wc when Nickserv started talking to me
[22:58] <maco> tried right-clicking and it started asking about buffers and then i didnt know what buffers had to do with the little list on the side and so back to the comfort of irssi
[22:59] <hggdh> heh. Myself, I stay with xchat
[23:48] <LimCore> hggdh: attached video
[23:50] <hggdh> good, this shows the screen with trash -- but it does not show a security/privacy issue...