[00:02] <azimout1> bdmurray: descriptions added: https://wiki.ubuntu.com/UbuntuBugDay/Planning
[00:20] <niadh> I think network manager might be broken under my installation
[00:20] <mohbana> hi, does flash work?
[00:20] <niadh> Yes, flash works
[00:21] <mohbana> i get a blank screen
[00:23] <niadh> You do have it installed then I assume?
[00:28] <mohbana> found it; https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/262693
[00:57] <Flare183> Bug 293211
[00:57] <Flare183> umm
[04:13] <woody86> is there any way to add the 5-1-day applet to kubuntu?
[04:13] <woody86> 5-a-day*
[04:14] <yiannipa> have any issues been reported with today's (kernel) update?
[04:14] <yiannipa> since the update, I've experienced complete system freezes
[04:14] <yiannipa> 2x @ about 30 minute intervals
[04:18] <hggdh> yiannipa, check LP -- and opena bug if needed
[04:18]  * hggdh is downloading the new kernel now
[05:38] <yiannipa> update: no relapse freezes, therefore can't definitely determine cause
[05:38] <yiannipa> if the problem persists I'll open a bug, or something
[07:59] <elmargol> Bug #24330 <- verry annoying
[08:01] <thekorn> good morning!
[08:24] <danage> asac: could you point rtg to bug 278190 for me when you have a chance?
[09:02] <BUGabundo_work> good morning asac...
[09:02] <BUGabundo_work> I think I just made a mistake
[09:02] <BUGabundo_work> lol
[09:03] <BUGabundo_work> asac: ping
[09:39] <asac> hi .... not sure what mistake that can be BUGabundo_work
[09:39] <asac> danage: thats all properly scheduled ... not sure what you want here
[09:42] <jibel> mvo: What's your opinion about bug 291262 ?
[09:43] <jibel> mvo: most of the python modules upgrade from 8.04 to 8.10 are failing because of this.
[09:43] <mvo> jibel: hey, thanks for all the triage you do currently, that is great stuff!
[09:44] <mvo> jibel: I think the patch I posted is the appropriate solution, I think pycentral is overly cautious here
[09:44] <mvo> at the expense of unneeded failures
[09:44] <mvo> I would even vote for a SRU on this, but certainly it should go into jaunty
[09:45] <jibel> mvo: shall we mark all those upgrades as duplicates of this master ? What do you think is the right policy to triage those bugs ?
[09:45] <jibel> mvo: some triager are just marking them "invalid" but I don't believe this is a good from a user point of view
[09:46] <jibel> s/good/good thing/
[09:47] <mvo> jibel: yeah, I think we should dup them on this master
[09:47] <mvo> and I also think marking them invalid is wrong, sure its the user who did something "wrong" but that should not screw the upgrade, it should just work, especially nice its easy to fix
[09:50] <jibel> mvo: Ok. I'm at work right now and don't have too much time but I'll try to send an email to the bugsquad list as soon as I can to summarize this.
[09:50] <jibel> mvo: thank you for your help.
[09:53] <danage> asac: it's probably just my lack of knowledge then -- so there is no risk tim might "overlook" and not implement the patch?
[09:53] <mvo> thanks jibel
[10:00] <asac> danage: unlikely .. and it surely isnt my responsibility to mummy him ;)
[10:00] <asac> danage: you can bug him directly ;)
[10:00] <asac> but give this man some rest ;)
[10:00] <asac> (like once every week might be a good idea ;))
[10:00] <asac> in  #ubuntu-kernel
[10:03] <danage> asac: i couldn't find him on this channel so i thought i might ask you. not trying to make this your responsibility & thanks for the pointer
[10:03] <asac> no problem ;)
[10:04] <BUGabundo_work> asac: I reported on bug 292054. not sure it was right
[10:09] <danage> oh
[10:11] <danage> BUGabundo_work: i think that may be related to bug 278190
[10:37] <danage> asac: you recently commented on bug 187313. about that bug: i cannot reproduce, but i do get it. is there some way of setting up gdb so i can "record" what happens when it occurs? or do i need a VM for that? this bug is *really* annoying
[10:49] <asac> no
[10:49] <asac> we need a way to reproduce
[10:52] <danage> rats
[12:08] <woody86> is anyone using the 5-A-Day applet in a KDE panel?
[12:11] <thekorn> woody86: I'm not sure if this would work,
[12:12] <thekorn> it is an explicit gnome applet and I don't know if the kde panel is able to show them
[12:12] <thekorn> it is possible to use this applet in xfce as the xfce panel has a wrapper applet for gnome applets
[12:13] <thekorn> don't know if such a thing exist for kde
[12:14] <thekorn> woody86: if you found a way to use this applet in the kde panel, I'm happy to hear about it
[12:14] <woody86> thekorn: that's what I was afraid of, but thanks :)
[15:19] <BUGabundo_work> guys
[15:20] <BUGabundo_work> can some one take a look at bug 284808 and tell me what's wrong?
[16:13] <Guest9038> hello, I have a bug with evolution, I can reproduce it, but I don't know how to submit a crash report
[16:13] <Guest9038> I found this link:https://wiki.ubuntu.com/DebuggingEvolution
[16:14] <Guest9038> it say's: Program crash - Log files from the crash incident are required to track down these. Almost always, this will require the reporter to file in a nice backtrace (since most of the times we cannot reproduce it :-(). For example, see bug 106504. if  Apport is installed, a crash report will be generated under /var/crash.
[16:14] <Guest9038> apport is installed, but /var/crash is empty
[16:14] <hggdh> Guest9038, yes. Did you get a crash?
[16:14] <Guest9038> (evolution:2589): Gdk-CRITICAL **: gdk_screen_is_composited: assertion `GDK_IS_SCREEN (screen)' failed
[16:14] <Guest9038> Segmentation fault
[16:14] <hggdh> and what Ubuntu version are you running?
[16:15] <Guest9038> 8.10
[16:16] <hggdh> Guest9038, indeed... apport is disabled on 8.10 now. For you to enable it 'sudo vi /etc/default/apport', and change énabled'from 0 to 1
[16:17] <hggdh> Guest9038, *but* -- if the GdK-CRITICAL message has something to do with the crash, this sounds more like a compiz issue
[16:17] <Guest9038> hggdh: thx, I'll try it again, the page saying: if apport is installed a crash report will be generated...
[16:18] <Guest9038> hggdh: tried with and witout compiz, still crashed
[16:18] <Guest9038> this is my first report: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/294203
[16:18] <hggdh> Guest9038, OK. We will need a crash report then. --- and... I will change the page to state 'if apport is enabled'
[16:19] <Guest9038> hggdh: now I get (evolution:2781): evolution-shell-CRITICAL **: e_shell_set_crash_recovery: assertion `E_IS_SHELL (shell)' failed
[16:20] <hggdh> Guest9038, not necessarily related to your crash
[16:20] <Guest9038> and no crash report, not even warnings in cli
[16:20] <Guest9038> I can still reproduce the crash
[16:20] <hggdh> by default CRITICAL messages do not kill the program
[16:21] <Guest9038> Segmentation fault
[16:21] <Guest9038> jens@neo:~$ ls /var/crash/
[16:21] <Guest9038> jens@neo:~$
[16:23] <hggdh> Guest9038, did you enable apport?
[16:23] <Guest9038> yes, and restarted it
[16:24] <Guest9038> ow wait, didn't restart
[16:24] <hggdh> this is interesting. Apport should have kicked in to handle the SEGV
[16:24] <xteejx> Hey guys stupid question : What is the LOWEST version of Ubuntu that is now supported is it Hardy 8.04.1?
[16:25] <BUGabundo_work> hggdh: apport only kicks in during devel. not on a stable release
[16:25] <xteejx> BUGabundo_work: You can enable it
[16:25] <BUGabundo_work> sure
[16:25] <BUGabundo_work> https://help.ubuntu.com/community/ReportingBugs
[16:25] <charlie-tca> No, it's actually 6.06, the previous LTS, which is supported until 9/09 for desktops
[16:25] <hggdh> BUGabundo_work, yes. I asked the reporter to re-enable it
[16:25] <BUGabundo_work> ubuntu-bug PID is his best choice
[16:26] <BUGabundo_work> ah sorry
[16:26] <BUGabundo_work> lol
[16:26] <xteejx> OK, so only 6.06 8.04 and 8.10?
[16:26] <BUGabundo_work> just read the tail of the log
[16:26] <Pici> xteejx: And 7.10
[16:26] <charlie-tca> xteejx: also, 7.10
[16:26] <xteejx> Really? Damn lol So if someone is reporting bugs about 7.10 we can't just say "upgrade" kinda thing?
[16:27] <xteejx> (in a nicer way obviously)
[16:27] <BUGabundo_work> you can say, but you can't force...
[16:27] <BUGabundo_work> and not all bugs will be fixed
[16:27] <BUGabundo_work> mostly secutity only
[16:27] <BUGabundo_work> Pici: bug 284808 makes any sense to you ?
[16:28] <xteejx> Of course, but surely they can enable the backports for their version and get more updates that way for the more serious issues right? I'm new to triaging :)
[16:28] <Guest9038> xteejx: you can tell them to use the backports repo cant't you?
[16:28] <Guest9038> I'm to slow
[16:28] <xteejx> Guest9038: Sure, was just checking, don't want to mess up first time hehe
[16:28] <xteejx> Oops me too now lol
[16:29] <Pici> BUGabundo_work: I'll take a look, gotta go for a conference call right now though
[16:29] <xteejx> Bugabundo_work: I don't suppose your laptop happens to be Hp or Compaq does it?
[16:29] <BUGabundo_work> no prob Pici
[16:29] <BUGabundo_work> nope
[16:29] <BUGabundo_work> ASI/asustek S37S
[16:30] <xteejx> OK no worries, just have been seeing a lot of HP/Compaq problems recently
[16:30] <xteejx> ACPI problems etc
[16:31] <BUGabundo_work> I could file it against acpi....
[16:31] <BUGabundo_work> but logs don't show anything
[16:31] <BUGabundo_work> and I can't find a way to manually force the behaviour
[16:31] <BUGabundo_work> some times I'm 15min away from it, and it goes to sleep
[16:31] <BUGabundo_work> when GPM is set to OFF on AC and 45 min on bat
[16:32] <BUGabundo_work> other times I'm even using it, and it goes to sleep
[16:32] <Guest9038> hggdh: any Idea's about what I have to do to get the crash report?
[16:32] <BUGabundo_work> it also happened a few times when running with more then 50% (1h) of battery
[16:33] <xteejx> BUGabundo_work: Personally I'd file it under linux as chances are it's a kernel problem, but can't say for sure without further info.
[16:33] <xteejx> BUGabundo_work: Suggestion: It's not overheating at all is it? You might want to check temp.
[16:34] <BUGabundo_work> 53ºC
[16:35] <BUGabundo_work> it doesn't change much
[16:35] <BUGabundo_work> disk is at 58ºC
[16:35] <BUGabundo_work> GPU at 36ºC
[16:35] <xteejx> bug 200919 : Did I do the right thing with this marking it Incomplete it's been sitting there without anything from the reporter for 8 months
[16:35] <hggdh> Guest9038, one apport is enabled, you should have it as soon as Evo crashes
[16:35] <xteejx> 53 system? hmm not that then
[16:35] <hggdh> if it is not happening... then you can do it the hard way
[16:36] <BUGabundo_work> Guest9038: get its pid and the run ubuntu-bug «PID»
[16:36] <xteejx> Guest9038: You can get the PID using the "top" command or checking in processes
[16:39] <Guest9038> xteejx: the pid of evolution?
[16:39] <Guest9038> do I run this before it crashes? or after it has crashed?
[16:40] <BUGabundo_work> during evo running
[16:40] <Guest9038> ok
[16:41] <Guest9038> but then apport starts to get data at once, before I reproduced the crash
[16:42] <seb128_> are you sure it's crashing?
[16:42] <seb128_> did you run apport start?
[16:42] <Guest9038> I get a segmentation fault, and the window disapears
[16:43] <homy> Hi! I have a question: What advantages do I have when I join the Ubuntu BugSquad team in launchpad? Can't I also triage bugs the same without being in that team?
[16:44] <Guest9038> seb128: http://paste.ubuntu.com/67975/
[16:44] <seb128> do you have any .apport* in your user directory? did you try "start" rather than "restart"?
[16:45] <seb128> restart doesn't do what you think, try doing start
[16:45] <Guest9038> ok seb128, thanx, that fixed my problem...
[16:46] <Guest9038> weird, I tought restart would also start it...
[16:47] <BUGabundo_work> me too
[16:47] <seb128> no
[16:48] <BUGabundo_work> seb128: so stuff like /etc/init.d/postfix restart or
[16:49] <BUGabundo_work>  /etc/init.d/bluetooth restart aint the same as
[16:49] <BUGabundo_work> stop && start ?
[16:49] <seb128> BUGabundo_work: you can use your editor on the apport script and look at what it's doing
[16:50] <seb128> some do a stop and start
[16:50] <seb128> not sure if that's worth a bug, you can try to ask pitti directly on IRC
[16:51] <BUGabundo_work> never thought about it...
[16:51] <BUGabundo_work> its one of those thing a person tends to assume that it just works like that
[16:56] <murdok> hello asac , are you there?
[16:58] <asac> on a call now
[16:59] <murdok> okay, make me know when you are free for 5 minutes
[17:02] <Guest9038> BUGabundo_work: if you look at the /etc/init.d/apport source code a restart only call's set_maxsize, but no stop and no start...
[17:05] <homy> If I join BugSquad launchpad team, do I get an email for every new ubuntu bug that is reported ?
[17:06] <chrisccoulson> nope
[17:06] <chrisccoulson> there is another team you can subscribe too if you want that
[17:06] <chrisccoulson> i think#
[17:07] <chrisccoulson> but i wouldn't advise you do that;)
[17:07] <homy> no, I wouldn't want that email, thats why I'm asking :)
[17:07] <homy> Anyway, what good is it to be in the BugSquad launchpad team? I mean, can't also also triage bugs the same without being in it?
[17:08] <chrisccoulson> yes you can, but you will also receive e-mails from the bugsquad mailing list (which is a low traffic list)
[17:08] <chrisccoulson> that can be very useful
[17:09] <homy> thanks! I think I'll try triaging a bug or two like that and if I like doing it, I'll join the BugSquad team.
[17:10] <chrisccoulson> homy - have you had a look at https://wiki.ubuntu.com/Bugs/HowToTriage
[17:11] <homy> yes, I also listened in the "How to triage Bugs" lesson in #ubuntu-classroom yesterday
[17:11] <chrisccoulson> good good
[17:12] <chrisccoulson> also this is very useful, but you may be aware of it already: https://wiki.ubuntu.com/BugSquad/KnowledgeBase
[17:13] <homy> thanks, I only saw subsites of that up to now. Thanks, I bookmarked it.
[17:21] <murdok> asac: did you finish :?
[17:30] <asac> murdok: right now
[17:34] <murdok> asac: it's about bug 293290 . I am the reporter, and I don't understand you still your reply and why it's incomplete
[17:35] <murdok> I changed the status to save time, and I had done it a lot of times without nobody complained
[17:36] <murdok> the question is answered, why do you think it must be still incomplete?
[17:36] <asac> murdok: i will come around and ask for more questions
[17:36] <asac> just because you answered the first one, doesnt mean its complete and there are no more questions left
[17:36] <asac> murdok: by bumping status to confirmed you make this bug be less likely to be looked at by me
[17:37] <murdok> then you can set it back to incomplete, isn't it the method?
[17:37] <asac> murdok: no
[17:37] <asac> thats cumbersome
[17:37] <asac> murdok: the procedure is that reporter doesnt change status at all
[17:37] <asac> only triagers do that
[17:38] <murdok> okay if you say that, but I have never read that.
[17:40] <murdok> anyway you could give friendlier answers not like that one, when I read it this afternoon I thought at the beginning that I had broken last xorg at least
[17:41] <maco_> asac: sometimes they mark confirmed when they get someone else showing up and "me too"ing...dont they?
[17:41] <asac> maco_: define "they" ... there are certainly a bunch of people confirming things with me too. yes
[17:42] <asac> i dont mind. its just that i complain if reporters change their own bug status ;)
[17:43] <murdok> wow i thought the code of conduct should be followed by everyone
[17:43] <murdok> not only by those who mind
[17:43] <maco_> asac: asac well, i recall saying on a list one time (devel discuss?) what the wiki page says, which is that confirm means there's enough info, which resulted in someone (bdmurray?) going "huh? no that's triage" and then we check the wiki and oh wait confirmed has way too high a bar, it does look like triage, oops, change confirmed to mean it's reproducible
[17:44] <maco_> i think one wiki page still says that
[17:46] <asac> maco: i think its well understood that confirmed is a bogus state
[17:46] <asac> without much benefit
[17:46] <maco> oh.
[17:46] <asac> there are discussions to remove it completely
[17:46] <asac> maybe its ment to be a staging area for those that dont have permissions to push to triage
[17:46] <asac> kind of "suggest as triaged for developers and qa folks"
[17:47] <asac> maco: https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook
[17:48] <asac> thats the specific handbook for firefox triaging ;)
[17:48] <maco> yeah, ive seen that
[17:48] <asac> so there is kind of meangin for confirmed even for me
[17:50] <maco> HowToTriage is the page that seems to make confirmed be more like triaged
[17:56] <BUGabundo> asac: wpa entreprise is working fine today! FYI
[17:56] <BUGabundo> connected at 1st attemped
[17:58] <asac> BUGabundo: what variant is that?
[17:58] <asac> PEAP or TTLS?
[18:01] <BUGabundo> TTLS
[18:01] <BUGabundo> tell me what you want me to log.... lol
[18:02] <BUGabundo> I'll have to send current logs
[18:02] <BUGabundo> 'cause I won't risk not reconnecting
[18:02] <BUGabundo> lol
[18:04] <BUGabundo> asac: what's theat VPN bug? I need to email it to our Local groups so they know how to work around that server miss configuration!
[18:21] <asac> BUGabundo: sorry. so how did you workaround?=
[18:21] <asac> BUGabundo: oh ok
[18:21] <BUGabundo> diferent machine .... lol
[18:21] <asac> yes. that bugs should be on the intrepid list for -pptp
[18:21] <BUGabundo> can't find LP id for it
[18:21] <asac> BUGabundo: look for intrepid bugs for -pptp should be just two or so ;)
[18:21] <asac> https://bugs.edge.launchpad.net/ubuntu/intrepid/+source/network-manager-pptp
[18:22] <asac> 4 to be correwct
[18:22] <asac> think the first is your
[18:22] <BUGabundo> Bug #259168
[18:44] <drunkenkilla> hello
[18:49] <drunkenkilla> i have some problems to regulate the brightness... today i tested pre-release of fedora 10 and i could change the brightness with the applet in the panel. but the fn-keys doesn't work in fedora too
[18:52] <BUGabundo> do you have a an ibm drunkenkilla?
[18:52] <BUGabundo> pitty added some work arounds... some time ago...
[18:53] <drunkenkilla> BUGabundo: no i have a samsung notebook
[18:53] <drunkenkilla> https://bugs.launchpad.net/ubuntu/+bug/219116
[18:53] <drunkenkilla> thats the bugreport
[18:56] <BUGabundo> thanks
[18:56] <BUGabundo> I'll guess you will have to wait for some dev to look at it
[18:57] <BUGabundo> drunkenkilla: don't nominate it, ok?
[18:57] <drunkenkilla> i'm waiting till april 08 ;)
[18:58] <drunkenkilla> ok
[18:59] <BUGabundo> 09 you mean!
[18:59] <BUGabundo> no need
[18:59] <BUGabundo> 20 of november you will have alpha1
[18:59] <drunkenkilla> yes 09^^
[19:00] <drunkenkilla> no april 08
[19:01] <drunkenkilla> Reported by  drunkenkilla  on 2008-04-18
[19:01] <drunkenkilla> it's a long time ago
[19:02] <chrisccoulson> drunkenkilla - your bug report could use some more info really
[19:02] <drunkenkilla> which infos?
[19:03] <chrisccoulson> your dmesg shows some unknown scancodes. it would be useful to know whih keys these scancodes actually corresponded to on your notebook
[19:03] <chrisccoulson> that would be needed in order to make the hal-info change to register these keys
[19:03] <chrisccoulson> the scancodes are e008 and e009
[19:04] <chrisccoulson> and if you could also attach the output of "lshal" too
[19:04] <chrisccoulson> then iu'll have a look at the other hal-info changes for similar problems and see how easy it is to implement. if it's not too hard, then i'll do it when i get the chance
[19:07] <chrisccoulson> it looks pretty trivial to do actually
[19:07] <drunkenkilla> ok first i added the lshal
[19:09] <drunkenkilla> today i tried the acpi-fix but it doesn't help me
[19:14] <drunkenkilla> chrisccoulson: keys...scancodes...do you mean something like this?: http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-check.html
[19:16] <chrisccoulson> if you do something like "tail -f /var/log/dmesg" and then press each non-working key in turn, an error will be reported to the terminal containing the scancode for each keypress
[19:16] <chrisccoulson> thats the bit i need. you've already posted the scancodes in the bug report, but the problem is i don't know which keys they belong too
[19:18] <chrisccoulson> hi - the output of lshal in your bug report looks wrong. it looks like the output of dmesg instead
[19:19] <chrisccoulson> and could you please attach the output of lshal instead of posting inline? to do this, run "lshal > lshal.log" and attach the file "lshal.log" to the bug report
[19:23] <drunkenkilla> chrisccoulson: i tipped tail -f /var/... and when i'm tipping the fn-keys no error is shown
[19:24] <chrisccoulson> what about /var/log/syslog?
[19:26] <drunkenkilla> something like this comes:
[19:26] <drunkenkilla> Nov  5 20:25:40 drunkenkilla-laptop kernel: [ 5202.298802] atkbd.c: Unknown key pressed (translated set 2, code 0x89 on isa0060/serio0).
[19:26] <drunkenkilla> Nov  5 20:25:40 drunkenkilla-laptop kernel: [ 5202.298821] atkbd.c: Use 'setkeycodes e009 <keycode>' to make it known.
[19:26] <chrisccoulson> thats right. now, which key did you press to make that happen. that is the missing link;)
[19:27] <chrisccoulson> and i could still do with the output of lshal, as described above
[19:27] <chrisccoulson> i'm not quite sure wht the other data is that you posted
[19:27] <drunkenkilla> i pressed once fn-key+up arrow and fn-key+down arrow
[19:28] <chrisccoulson> ok, but one of those keys corresponds to scancode e008 and the other key corresponds to scancode e009
[19:28] <chrisccoulson> which way round is it?
[19:29] <drunkenkilla> Nov  5 20:28:56 drunkenkilla-laptop kernel: [ 5398.061901] atkbd.c: Use 'setkeycodes e008 <keycode>' to make it known.
[19:29] <drunkenkilla>    this ist fn-key+up arrow
[19:29] <chrisccoulson> thanks
[19:31] <drunkenkilla> i upped the lshal.log
[19:32] <chrisccoulson> thanks drunkenkilla. did you have an external keyboard connected when you ran lshal?
[19:32] <drunkenkilla> no
[19:32] <chrisccoulson> hmmm. that's odd. there appears to be 2 keyboards;)
[19:33] <drunkenkilla> now i'm tipping on the notebook-keyboard...sometimes, when i'm at home, i'm tipping on an external keyboard but not now
[19:34] <chrisccoulson> thanks anyway, i think there is enough info in there now. i'll work on it soon and then ask you to test a modified hal-info
[19:35] <drunkenkilla> ok thank chrisccoulson
[19:35] <drunkenkilla> thanks
[19:38] <drunkenkilla> bye
[19:43] <unenough> hey, i have an annoying problem, sometimes when i have connection problems to a wifi, nm-applet suddenly disappears from the panel
[19:43] <unenough> until i reboot
[19:44] <Awsoonn> unenough: did you check out https://wiki.ubuntu.com/DebuggingNetworkManager
[19:46] <Awsoonn> it's probably crashing and you should file a bug and atach a backtrace. It;s not as dificult as it sounds. :)
[19:52] <weboide> Hi, I want to work on fixing watch files in some packages I found in the UEHS, I'd like to know if that'd helpful and what I should do after it's been fixed. (posting a debdiff in a bug report or sthg else?)
[19:53] <weboide> *if that'd be
[20:42] <unenough> Awsoonn, i don't think it's difficult, i'm a developer too. just annoying that i have to spend time on it. But thanks for the link, i'll do that next time it happens.
[21:07] <drunkenkilla> chrisccoulson: hello
[21:07] <chrisccoulson> hi
[21:07] <drunkenkilla> i installed your hal-info
[21:08] <chrisccoulson> what happened?
[21:08] <drunkenkilla> when i press the fn-key+up/down arrow, the icon comes for change the brightness but then the other keys doesn't work, the mouse-keys doesn't work right...
[21:09] <chrisccoulson> does the brightness change? and which other keys don't work?
[21:09] <drunkenkilla> i can't press any keys...
[21:09] <drunkenkilla> the brightness doesn't change
[21:10] <chrisccoulson> could you post the output of lshal to http://paste.ubuntu.com/ ?
[21:11] <drunkenkilla> yes mom
[21:12] <drunkenkilla> http://paste.ubuntu.com/68052/
[21:12] <chrisccoulson> this is with the update hal-info isn't it?
[21:13] <drunkenkilla> this is with the update hal-info
[21:13] <chrisccoulson> thats odd
[21:14] <chrisccoulson> i'm not sure why it made any difference. the HAL quirk i added didn't apply for some reason
[21:14] <drunkenkilla> i updated the gnome-power-manager from you too
[21:15] <chrisccoulson> ah, i wouldn't do that;)
[21:15] <drunkenkilla> too late^
[21:15] <chrisccoulson> the hal quirk did actually add. i'm not sure why it causes your problem though
[21:16] <drunkenkilla> hmm
[21:17] <drunkenkilla> i'm changing the gnome-power-manager back...
[21:18] <drunkenkilla> ok i will press the fn-keys now
[21:18] <drunkenkilla> maybe that i must reboot it
[21:22] <drunkenkilla> re
[21:23] <drunkenkilla> i got some bugs now in the windows...i must reboot
[21:23] <drunkenkilla> re
[21:25] <drunkenkilla> chrisccoulson: when i press the fn-key+up/down-arrow, then the other keys doesn't work...i must press ctrl+alt+F1 and then ctrl+alt+f7 and then it works
[21:25] <drunkenkilla> but not fine
[21:25] <chrisccoulson> hmmmm. that's odd. that sounds like a separate issue
[21:26] <chrisccoulson> i've got to go at the moment. if i'm around later, i'll ask you for some more info
[21:26] <drunkenkilla> ok
[22:52] <bdmurray> jibel: weren't you talking about an ubuntu-studio upgrade bug once?
[22:53] <jibel> bdmurray: yes I did
[22:54] <bdmurray> jibel: is bug 288608 a duplicate of that?
[22:56] <jibel> bdmurray: not much info on this report. Could he provide the output of the upgrade ?
[22:56] <jibel> bdmurray: the master report is bug 276503
[22:59] <jibel> bdmurray: I've talked to luisbg about it few days ago, but I've got no feedback since then and I don't know if he's working on it.
[22:59] <bdmurray> jibel: did you get any traction with that bug?
[23:08] <jibel> bdmurray: I've asked for help on #ubuntustudio and #ubuntu-devel but no one followed up.
[23:11] <bdmurray> jibel: there's an ubuntu-studio-users mailing list
[23:11] <bdmurray> oh, and a devel one
[23:12] <bdmurray> hmm, the devel one loks mostly like bug mail
[23:18] <bdmurray> jibel: I pinged a dev in #ubuntu-devel about it
[23:19] <jibel> bdmurray: The devel seems to be simply the recipient for launchpad bug mails and developers are not very active on the users one.
[23:20] <jibel> bdmurray: Impressive, I can see that you're more influent than I am ;)
[23:22] <bdmurray> I just happened to know a good person to ask.
[23:25] <jibel> bdmurray: I had tried since he was in the changelog but I probably don't know the magic words.
[23:25] <jibel> bdmurray: Do you know where I can reach the maintainer of wubi ?
[23:26] <jibel> bdmurray: I have another metabug in my bag. bug 252900
[23:26] <bdmurray> He's xivulon on IRC and shows up in #ubuntu-installer
[23:26] <bdmurray> https://launchpad.net/~ago
[23:27] <jibel> bdmurray: I haven't tried #ubuntu-installer. will do. thanks,
[23:28] <bdmurray> jibel: Did you see his comment on that bug?
[23:31] <jibel> bdmurray: Yes I have, but we have to find a more user friendly way to tell the user that it doesn't work except just a failure.
[23:31] <bdmurray> I agree that would be best.
[23:33] <jibel> bdmurray: If we know that kernel upgrade doesn't work then maybe kernel upgrade could simply be locked.
[23:34] <jibel> bdmurray: we have the same kind of issue with users trying to upgrade a live cd from a memory stick. It just fails.
[23:39] <jspiro> hi all.  Each time cllaudyu types "sudo apt-get update
[23:39] <jspiro> ", she gets "Segmentation faultchete... 1%"
[23:40] <jspiro> cllaudyu: (is it "she"?  your nick sounds female)
[23:40] <cllaudyu> is he
[23:40] <jspiro> sorry
[23:40] <cllaudyu> that's ok :))
[23:41] <jspiro> i told him he probably ran into a bug, and should report it.  Could someone here please help cllaudyu figure out if this is a known bug, and if not, how to report it?
[23:41] <cllaudyu> thank you
[23:41] <cllaudyu> but i think i will get help far more hard
[23:42] <jspiro> what does "more hard" mean?
[23:42] <cllaudyu> i mean in never
[23:43] <cllaudyu> i don't know what to do
[23:43] <jspiro> cllaudyu:  (each time you see a segmentation fault, that means there is a serious bug in apt-get that should be fixed.  And if you are experiencing the bug, there are probably a hundred or more other people who have experienced the same bug as you before.)
[23:44] <cllaudyu> jspiro i hope there is a simple solution for this
[23:45] <jspiro> cllaudyu:  there may be a simple solution.  But if you do the simple solution, then the bug will remain unfixed for everyone else.  If you report the bug, then you will be helping all other Ubuntu users experiencing the bug.
[23:46] <cllaudyu> jspiro repporting i want but how do i repport the bugg?
[23:48] <jspiro> cllaudyu:  you wait here for someone else here to help you.  I am not sure, but probably they will tell you how to upgrade to the newest apt from a newer Ubuntu, verify the bug still exists, get a backtrace, rebuild with dpkg-buildpackage if you don't have symbols in the backtrace, try again to get the backtrace, and upload it.
[23:48] <jspiro> cllaudyu:  It is hard but they can tell you everything to type.
[23:48] <hggdh> cllaudyu, what is your Ubuntu version?
[23:48] <cllaudyu> hggdh 8.04
[23:49] <hggdh> cllaudyu, OK. when you get hte segmentation fault, do you see a pop-up stating something about "apport"?
[23:50] <cllaudyu> no
[23:50] <cllaudyu> i just tipe in terminal sudo apt-get update
[23:50]  * jspiro idly wonders: (do segfaulting console apps ever cause apport to pop up?)
[23:50] <cllaudyu> and i get
[23:50]  * jspiro didn't know console apps could.
[23:50] <hggdh> jspiro, they should
[23:51] <jspiro> it's annoying how it isn't for cllaudyu then.
[23:51] <hggdh> there is a reason: apport is usually disabled on stable releases
[23:51] <cllaudyu> i just done an update command and it got me this in the terminal
[23:51] <cllaudyu> Segmentation faultchete... 18%
[23:52] <hggdh> cllaudyu, and you get the shell prompt again, right?
[23:52] <cllaudyu> yes
[23:52] <hggdh> k
[23:53] <hggdh> let's check if apport is enabled: on the terminal 'sudo vi /etc/default/apport'
[23:53] <jspiro> hggdh: not nano?
[23:53] <hggdh> or nano
[23:53] <jspiro> hggdh: or gedit, better yet :)
[23:53]  * hggdh uses vi
[23:53] <jspiro> cllaudyu: sudo gedit /etc/default/apport
[23:54] <hggdh> the important piece is to open it under an editor ;-)
[23:54] <cllaudyu> it opened
[23:54] <cllaudyu> know?
[23:54] <hggdh> not check if 'enabled=1' -- if it is =0, make it =1
[23:54] <hggdh> s/not/now/
[23:56] <hggdh> cllaudyu, did you check?
[23:56] <cllaudyu> yes
[23:56] <hggdh> and?
[23:56] <hggdh> =0 or =1?
[23:56] <cllaudyu> it was =0
[23:56] <cllaudyu> i put it =1
[23:56] <cllaudyu> now??
[23:56] <hggdh> OK. save the file, then 'sudo invoke-rc.d apport start'
[23:57] <jspiro> cllaudyu:  After you do something that we tell you to do, please tell us you did it.  Otherwise we won't know you did it  :)
[23:57] <cllaudyu> i wrote the command
[23:58] <hggdh> k
[23:58] <hggdh> now
[23:58] <hggdh> run apt-get again
[23:58] <jspiro> sudo apt-get update
[23:58] <cllaudyu> i'l run it know
[23:59] <cllaudyu> i think it's workong
[23:59] <cllaudyu> working
[23:59] <jspiro> cllaudyu: what do you see?
[23:59] <cllaudyu> Segmentation Fault (core dumped)
[23:59] <hggdh> do you now get a pop-up?
[23:59] <cllaudyu> it didn't work