[15:28] <cmplxen> hello
[15:29] <cmplxen> i have a quick question about duplicate bugs: is there any way to view the content of bugs that have been marked as duplicate, or maybe get their titles?
[15:30] <cmplxen> for example: https://bugs.launchpad.net/ubuntu-gnome/+bug/1163711 <-- when i click the bugs marked as duplicates on the side, i get a message saying that the page does not exist
[15:30] <cmplxen> woah that is neat :)
[15:31] <cmplxen> so what happens if i paste one of the duplicate bugs here... https://bugs.launchpad.net/bugs/1173654
[15:31] <cmplxen> exactly :)
[15:31] <rbasak> cmplxen: they may be private bugs.
[15:31] <rbasak> (eg. contain security-sensitive information)
[15:32] <rbasak> This happens by default for crash dumps. Only a restricted set can see them.
[15:32] <rbasak> I thought I was in that set, but perhaps not in this case, since I can't see those bugs either.
[15:32] <cmplxen> oh ok. i was thinking they got deleted to save space or something
[15:33] <rbasak> The general process to get access to them is to ask someone who does have access to vet it for security sensitive information (eg. passwords in the crash dump) and mark it public if it's OK to be.
[15:33] <cmplxen> i am actually trying to figure out if they are crash dumps (reported by Apport) so those are just the bugs/duplicates i am looking for
[15:33] <rbasak> I would help since normally I can see them, but I can't, so I don't know why and can't help. Maybe someone else will see this and help you out.
[15:33] <cmplxen> that makes sense. thank you very much for the explanatino
[15:34] <cmplxen> do you happen to know if there would be a way to determine if a given ID refers to a crash/from Apport without actually accessing the bug report (or at least any of the potentially-sensitive portions of the bug report)?
[15:34] <rbasak> I don't think that's possible, no.
[15:35] <rbasak> I think the reporter can mark his own bugs public, but I guess that doesn't help you much.
[15:35] <cmplxen> ok, thanks. nuts.
[15:35] <rbasak> This is the right place to ask for the status to be assessed, though. Hopefully someone who can will come along and help.
[15:35] <cmplxen> nah -- i was orignally thinking i could analyze all of the crash dumps, or at least the back traces, to make the fuzzy stack hashing uniqueness logic better
[15:36] <cmplxen> your point about the sensitive info is valid though -- they probably don't want the general public to have access to even the backtraces
[15:37] <rbasak> They're fine with it providing there's some per-dump check to make sure that it doesn't contain sensitive information.
[15:37] <rbasak> I think there was also talk about sorting out the legals to open unvetted access to the whole set more widely.
[15:38] <rbasak> (to vetted community members or something)
[15:38] <cmplxen> that would be awesome
[15:38] <rbasak> I'm not sure what progress that made.
[15:38] <rbasak> It sounds like you have a valid reason to want access. I appreciate you understanding why it's awkward though
[15:40] <cmplxen> absolutely; i totally respect not wanting to put users at risk. if a program existed to access the data i'd sign up.
[17:48] <krabador> i people, i would ask if it's soon a fix for nm-applet, that's not autostarted in lubuntu 14.04
[17:48] <krabador> workaround are simple
[17:49] <krabador> but sometimes it's hard to tell, in support channel
[18:16] <Mikaela> krabador: I believe the status will be reported on the bug report at Launchpad.
[18:17] <krabador> Mikaela, it's a first line bug
[18:18] <krabador> lubuntu newbies have a negative impact
[18:22] <krabador> Mikaela, https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1308348   https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1308703
[18:23] <Mikaela> krabador: It seems that that issue is assigned to gilir and they don't seem to be on this channel.
[18:23] <Mikaela> They are also offline.
[18:23] <Mikaela> You could probably comment on the bug or see https://launchpad.net/~gilir