[14:12] <fdr> Hi! I reported this bug https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1026587 and the triager marked it as "Incomplete" and asked a couple of questions. I've answered the questions -- now should I also change the status of the bug? Thanks!
[14:12] <ubot2> Ubuntu bug 1026587 in cheese "Cheese segfaults on start" [Undecided,Incomplete]
[14:15] <LoT> fdr: lemme see
[14:15] <fdr> LoT, thx. Just wondering if I should also change the status as a signal to the triager that his/her question is now answered.
[14:16] <LoT> fdr: its still technically incomplete.
[14:16] <LoT> since its missing information
[14:16] <LoT> so i would not change its staus
[14:16] <LoT> status*
[14:21] <fdr> ok, thx
[14:23] <LoT> fdr: also, he's subscribed to all bug notifications
[14:23] <LoT> so he's likely already seen an email about it
[16:06] <hggdh> fdr: when all questions are answered move the status to New again
[17:35] <astraljava> Hi gang, running quantal here, on a Studio box. Ḯ'm deliberately testing -generic alongside with -lowlatency, the default with Studio. Question: Should I file a bug when update-manager tells me a reboot is needed, when only the other kernel type was updated? Meaning, I'm currently running -lowlatency, and after the -generic update, I have the counter-clockwise indicator telling me I need a reboot.
[17:40] <penguin42> astraljava: Hmm, which one becomes the default boot kernel?
[17:41] <astraljava> penguin42: -lowlatency
[17:42] <penguin42> astraljava: How do you setit up so that lowlatency is the default boot kernel?
[17:42] <astraljava> penguin42: I didn't, it was that way once I installed this instance from Studio image.
[17:44] <penguin42> astraljava: Then yeh I'd say that's a bug - you may get some disagreement :-)
[17:46] <astraljava> penguin42: Alright, it doesn't much more than lobotomy, I suppose. *grin*
[17:46] <astraljava> hurt much more*
[17:46]  * penguin42 washes the icepick
[17:46] <astraljava> Whee!
[17:47] <penguin42> astraljava: So the reason I asked those questions; if you had done something weird to select which kernel was the default I'd understand the updater not realising, but if it's the default setup then it seems reasonable it should know
[17:48] <astraljava> penguin42: I got ya. The only change related to this was installing the -generic after installation. I was a tad surprised it didn't get selected as the default kernel, but *shrug*.
[17:49] <penguin42> astraljava: Ah well, then is that actually the bug?
[17:50] <astraljava> I really have no idea cause I don't know the expected behaviour behind these methods.
[17:50] <astraljava> Should I ask on -devel?
[17:51] <penguin42> me neither; you could try or maybe -kernel?
[17:51] <astraljava> I suppose they'll point me towards kernel-land if that's inappropriate. Thanks, bro!
[17:52] <penguin42> np
[17:56] <astraljava> penguin42: Supposedly it's a built-in procedure in every kernel package, ie. not-a-bug.
[17:57] <penguin42> hmph
[18:06] <micahg> astraljava: not just kernel, any package can trigger a restart if it needs to
[18:09] <astraljava> micahg: That I did expect, actually. I just didn't know the mechanism behind the functionality, and thus whether this was erroneous or not. Thanks a lot for clearing up the confusion!