[13:18] <pwaller> Does anyone how I can run apport-collect but check that the output doesn't contain company secrets?
[13:22] <rbasak> pwaller: according to apport-collect(1) and apport-cli(1), you can use --save, check the results manually, and then use --crash-file to upload.
[13:22] <rbasak> pwaller: I'm not familiar with this though. Best to test first to be sure.
[13:22] <pwaller> rbasak: odd, apport-collect -h doesn't suggest it will do anything :(
[13:22] <pwaller> (I mean it isn't listed)
[13:22] <pwaller> But thanks, I'll try that!
[13:34] <pwaller> rbasak: unfortunately that only applies to apport-cli, which doesn't do anything unless you have .crash files around
[13:34] <rbasak> pwaller: apport-collect(1) says that --save works with it.
[13:34] <rbasak> pwaller: is that incorrect?
[13:34] <pwaller> rbasak: that manpage applies to both apport-collect and apport-cli
[13:34] <pwaller> it doesn't work with apport-collect (no such option --save)
[13:35] <rbasak> pwaller: oh, OK. Sorry. You have a reasonable use case, IMHO. File a bug if there's not one there already?
[13:44] <Guest24417> Hey guys, I'm in the process of reporting this bug which makes it so that, after coming out of sleep, my keyboard input is sent to whatever program was open before I put the computer to sleep, rather than to the password screen. So, if I was gchatting before putting my computer to sleep, and I type in my password and hit enter, then my password gets sent to the person I was chatting with. I'm reporting this as a 'screen locking