=== paultag is now known as ptagliamonte
=== Ursinha is now known as Ursinha-afk
=== ptagliamonte is now known as paultag
[13:51] <jmburgess> Is anyone available to mark bugs as triaged? I have two kernel bugs that I think are ready.
[13:58] <yofel> jmburgess: most of us don't touch kernel bugs as the kernel team has their own procedure. You usually want to talk to JFo when he's here
[14:01] <jmburgess> Yofel, ok ill go talk to ubuntu-kernel
[14:22] <bullgard4_> My Natty kernel crashed. It left 63 lines of code in a virtual terminal. How can I generate a meaningful error report to Launchpad on this?
[14:24] <charlie-tca> usually by filing a bug in terminal, with       ubuntu-bug linux
[14:24] <charlie-tca> after restarting
[14:24] <charlie-tca> That should include those lines automatically
[14:25] <charlie-tca> and it helps to tell what you were doing when it happened
[14:26] <bullgard4_> Of course it helps to tell what I were doing when the kernel crashed. But I doubt that these lines of text will be included automaticalle. I will give it a try.
[14:27] <bullgard4_> s/automaticalle/automatically/ .
[14:28] <charlie-tca> why? everything gets logged in dmesg
[14:29] <bullgard4_> Not all goes logged in dmesg.
=== Ursinha-afk is now known as Ursinha
[14:36] <bdmurray> yofel: did you find anything out about digikam and geolocation?
[14:38] <yofel> no sorry, was busy getting the last bits of kde 4.7 and deps into oneiric
[14:42] <bdmurray> yofel: that sounds kind of imporant ;-)
[14:43] <jmburgess> Hey guys isn't bug 81942 just how background processes in the terminal work?
[14:43] <ubot4> Launchpad bug 81942 in update-manager (Ubuntu) "[apport] update-manager crashed with DBusException in __call__() (dup-of: 81835)" [Undecided,New] https://launchpad.net/bugs/81942
[14:43] <ubot4> Launchpad bug 81835 in update-manager (Ubuntu) "[apport] update-manager crashed with DBusException in __call__() (affects: 13) (dups: 36) (heat: 1)" [High,Fix released] https://launchpad.net/bugs/81835
[14:43] <bullgard4_> charlie-tca: '~$ ubuntu-bug linux' automatically added the files BootDmesg.txt and CurrentDmesg.txt" to the bug report. But these 2 files do not include processor register states, for example.
[14:43] <yofel> it sure is, with FF ahead and some of us in berlin next week ;)
[14:43] <jmburgess> Sorry I meant 819842
[14:44] <yofel> lp 819842
[14:44] <ubot4> Launchpad bug 819842 in ubuntu "Commands in the background are terminated after closing the terminal (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/819842
[14:44] <charlie-tca> bullgard4_: do the backups include those?
[14:44] <charlie-tca> like /var/log/dmesg.0
[14:44] <yofel> uh yeah, when you close the terminal the shell inside dies and the background jobs with it (AFAIK)
[14:44] <charlie-tca> or /var/log/dmesg.1
[14:45] <yofel> there's nohup and screen if you need to keep them running
[14:45] <bullgard4_> charlie-tca: What backups do you speak about?
[14:45] <charlie-tca> if you look in /var/log you will see that there are backups of all current log files. Many logs are started new when you reboot.
[14:46] <charlie-tca> Do the previous logs have what you are looking for?
[14:48] <jmburgess> yofel, yeah that's what I thought. Maybe its a bug in git gui
[14:48] <jmburgess> ?
[14:49] <bullgard4_> yofel: In welchen Räumen der Humboldt-Universität wird die GNOME-Konferenz stattfinden?
[14:56] <hggdh> jmburgess: no, it is not a bug. This is The Way It Works. The new process is still tied to the terminal. When a parent process dies, it carries all still-tied-in offspring
[14:57] <hggdh> jmburgess: so, this is not a bug. The user should run the background process disconnected from the terminal (via, for example, 'nohup')
[14:58] <hggdh> and, actually, 'nohup' describes the signal that is passed to the offspring (a kill -HUP)
[14:59] <jmburgess> Hggdh, according to roadmr and the reporter this is different behavior than before. That's why I'm interested
[14:59] <jmburgess> Hggdh, I agree with you though
[15:00] <hggdh> roadmr: ^ What did you see?
[15:01] <roadmr> hggdh: on Natty or even Oneiric with xterm, I can gedit & and then kill the terminal, and gedit stays
[15:02] <roadmr> hggdh: on Oneiric with gnome-terminal, I do the same and gedit dies when I close the terminal
[15:03] <yofel> bullgard4_: sry, was gone: https://www.desktopsummit.org/program has the schedule for the rooms
[15:03] <yofel> click on workshops for the other schedule
[15:03] <hggdh> interesting
=== bambee_ is now known as bambee
[15:12] <hggdh> roadmr, jmburgess: perhaps GTK disconnects/disconnected. Worth a look, indeed
[15:13] <hggdh> roadmr, jmburgess: I subscribed to it; when I have time, I will also look at it
[15:13] <roadmr> hggdh: using nohup to launch gui programs keeps them from dying when the terminal is closed :) (old Unix trick)
[15:13]  * roadmr hadn't used nohup in years
[15:14] <hggdh> roadmr: indeed, but without nohup I expected the spawned process to die -- and it did not, on Natty
[15:15] <roadmr> hggdh: maybe the terminal didn't send any signals to its children before and it does now?
[15:15] <hggdh> perhaps
[15:16] <bullgard4_> yofel: I take it that the workshops will be held also in Audimax, Kinosaal, Rm2002, and Rm3038.
[15:16] <hggdh> but it is not the term that sends HUP, it is the OS (init? Do not remember)
[15:17] <yofel> bullgard4_: here's the usable plan https://www.desktopsummit.org/program/workshops-bofs
[15:17] <yofel> I hope that one's right at least
[15:17] <yofel> you coming to DS?
[15:18] <bullgard4_> yofel: Yes, I will.
[15:18] <yofel> yay
[15:29] <jmburgess> hggdh, I think it is bash that's supposed to send the signal.
[15:41] <roadmr> if a bug is marked upstream as won't fix (MP3 support on Firefox), should I mark the Launchpad bug won't fix as well, or is it best to make it invalid?
[15:43] <charlie-tca> I tend to go with upstream in most cases.
[15:44] <hggdh> makes sense -- and add a comment we are wont-fixing following to upstream decision
[15:44] <charlie-tca> but you should be checking what the upstream status vs launchpad status means. Sometimes they are not the same, and we have to adjust launchpad status to match
[15:44] <micahg> roadmr: bug #?
[15:45] <roadmr> micahg: bug 820343 on launchpad, and upstream bug is here: https://bugzilla.mozilla.org/show_bug.cgi?id=562730
[15:45] <ubot4> Mozilla bug 562730 in Video/Audio "Reproducing Mp3 files with html5" [Enhancement,Resolved: wontfix]
[15:45] <ubot4> Launchpad bug 820343 in firefox (Ubuntu) "No support for HTML5 Audio tag (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/820343
[15:45] <roadmr> micahg: I'm still preparing the comment with this information, just wanted to be certain about what status to set to, so I can include an explanation in the comment
[15:46] <roadmr> it seems to match LP's won't fix status (feature request that developers do not want to implement)
[15:47] <micahg> roadmr: well, it's not entirely true, there won't be native support in Firefox for it, but if a gstreamer backend is added, it should be possible to play mp3 files with HTML5 audio
[15:48] <roadmr> ah, interesting
[15:49] <micahg> so, native support is won't fix, the ability to play mp3 w/HTML is wishlist triaged...
[15:50] <micahg> oh, wait, hmm, there's a bug for gstreamer video support, I should make sure there's audio as well :)
[16:02] <micahg> roadmr: I don't see an upstream bug for a gstreamer HTML5 audio backend, maybe worth filing
[16:09] <roadmr> micahg: something like this (for video)? https://bugzilla.mozilla.org/show_bug.cgi?id=422540
[16:09] <ubot4> Mozilla bug 422540 in Video/Audio "GStreamer backend for HTML5 video element" [Enhancement,Assigned: ]
[16:11] <micahg> roadmr: yep, but for audio, probably won't be worked on unless someone has an itch to scratch, but might as well file it
[16:11] <roadmr> micahg: ok, I'll work on that then (filing it, not actually implementing :)
[16:11] <micahg> roadmr: thanks
[16:37] <bullgard4_> persia: ping
=== ogasawara_ is now known as ogasawara
[18:24] <tomtiger11> hello all
[18:25] <tomtiger11> its very quiet
[18:26] <Pici> no more bugs
[18:27] <tomtiger11> is anyone going to talk?
[18:27] <Pici> Well if you have a question about traiging just ask.  #ubuntu is the support channel though.
[18:28] <tomtiger11> i know that but thanks, i was just expecting more chat
[18:30] <charlie-tca> We seldom chat about anything except bugs here
[18:34] <tomtiger11> i suppose we do
[18:34] <tomtiger11> but who would talk about bugs alot
[18:38] <bdmurray> Anybody remember an update-manager bug report about not offering to upgrade to the next release if on a Live CD?
[18:38] <bdmurray> oh I do! bug 775656
[18:38] <ubot4> Launchpad bug 775656 in update-manager (Ubuntu Oneiric) (and 1 other project) "'Ubuntu 11.04 Upgrade Available' must not be displayed when 10.10 is started from a Live CD (affects: 2) (heat: 44)" [Medium,Triaged] https://launchpad.net/bugs/775656
[18:40] <charlie-tca> That's right! It showed up in a big window in the middle of the screen
[18:51] <tomtiger11> any help on bug 657788 ?
[18:51] <ubot4> Launchpad bug 657788 in grub2 (Ubuntu Maverick) (and 2 other projects) "grub minimal bash after first Maverick update (affects: 5) (heat: 27)" [Critical,New] https://launchpad.net/bugs/657788
[18:53] <tomtiger11> im looking for a good simple bug to triage as im quite new
[18:54] <tomtiger11> anyone find me an easy bug to triage?
[18:55] <tomtiger11> as i dont think bug ^^ is any good for me
[18:56] <yofel> what's the application you use most frequently - triage bugs for that
[18:56] <tomtiger11> um
[18:57] <tomtiger11> firefox
[18:57] <yofel> micahg: ^
[18:57]  * micahg hides
[18:57] <yofel> hehe
[18:57] <charlie-tca> heh, that was easy
[18:58] <micahg> firefox is a little tricky, a lot of "bugs" are caused by addons
[18:58] <tomtiger11> what, i like the internet?!?!?
[18:58] <tomtiger11> so you think i am totaly new eh?
[18:58] <tomtiger11> il look for one in firefox
[18:59] <micahg> tomtiger11: no, no comment about you, just about firefox triage in geenral
[19:00]  * micahg certainly doesn't want to discourage help though since there are so many bugs to look at
[19:01] <tomtiger11> @micagh how about bug 629164?
[19:01]  * micahg kicks ubot4 
[19:02] <tomtiger11> whats the * for
[19:02] <micahg> that's not a firefox bug
[19:03] <micahg> it's for an "action" versus a statement, one can do it by starting a line with /me
[19:03] <tomtiger11> ok
[19:03]  * tomtiger11 
[19:10]  * roadmr greets tomtiger11
[19:10] <tomtiger11> i would love to be a member of the ubuntu council
[19:12]  * tomtiger11 sobbs loudly as he wants a *@ubuntu.com forwarder =[
[19:12] <paultag> tomtiger11: that's not a reason to get one.
[19:12] <tomtiger11> how do you comment me?
[19:13]  * tomtiger11 is new is irc channels
[19:13] <paultag> tomtiger11: type the name, or part of it then hit tab
[19:13] <charlie-tca> tomtiger11: you can get that by becoming an ubuntu member
[19:14] <tomtiger11> paultag: i didnt say it was
[19:14] <paultag> tomtiger11: generally the people who care about the email don't so much care about the work :)
[19:14] <tomtiger11> charlie-tca: get what?!?
[19:15] <tomtiger11> paultag: i care about the work, and the email
[19:15] <charlie-tca> !member
[19:15] <ubot4> Ubuntu Membership means recognition of a significant and sustained contribution to Ubuntu and the Ubuntu community.  For more info see https://wiki.ubuntu.com/Membership
[19:15] <charlie-tca> tomtiger11: the *@ubuntu.com
[19:15] <tomtiger11> paultag: and honestly i didnt know about cloaks until 5 seconds ago or near bouts
[19:17] <tomtiger11> charlie-tca: i have looked at what i get, and how i join
[19:18] <tomtiger11> charlie-tca: and i probaly wont use the cloaks, but id use the rest
[19:18] <bdmurray> so depressing
[19:18] <bdmurray> I found a ubiquity bug with 36 duplicates!
[19:18] <charlie-tca> ouch
[19:18] <charlie-tca> That is depressing
[19:18] <bdmurray> But wait that's only 2.4% of the total
[19:18] <tomtiger11> bdmurray: really?
[19:18] <bdmurray> so still lots more work to do
[19:19] <tomtiger11> bdmurray: have you ever been called a nerd, because i have.
[19:20] <paultag> hahahaha
[19:20] <paultag> bdmurray: nerd.
[19:20] <paultag> There, now he has
[19:20] <charlie-tca> heh
[19:20] <charlie-tca> That's funny
[19:20] <tomtiger11> paultag: nerd
[19:20] <paultag> tomtiger11: how old are you, by chance? You read like someone under the age of 17
[19:21] <paultag> tomtiger11: dude, I went to public school. I've been called worse things by better people :)
[19:21] <roadmr> bdmurray: I think bug 784442 has been wrongly set as a duplicate of bug 743359
[19:21] <ubot4> Launchpad bug 784442 in ubiquity (Ubuntu) "Ubuntu install fails (dup-of: 743359)" [Undecided,Confirmed] https://launchpad.net/bugs/784442
[19:21] <ubot4> Launchpad bug 743359 in ubiquity (Ubuntu Oneiric) (and 1 other project) "Installer: LockFailedException: Failed to lock /target/var/cache/apt/archives/lock (affects: 45) (dups: 36) (heat: 316)" [Medium,Confirmed] https://launchpad.net/bugs/743359
[19:21] <tomtiger11> paultag: why the hell would i tell you my age
[19:21] <tomtiger11> charlie-tca: by chance, what does the red nick mean?
[19:21] <roadmr> 784442 has a syslog that a user with another problem attached, and the dupe status was set based on that, but it's not the original reporter's syslog
[19:22] <paultag> tomtiger11: because you read like someone under 18, and generally I stay away from them. Also, might want to check out ubuntu-youth, they are a group of kids. Might help :)
[19:22] <bdmurray> roadmr: okay unmark it
[19:22] <roadmr> bdmurray: ok, will do, thanks
[19:22] <bdmurray> I didn't check for squashfs-error tags when marking those dupes
[19:22] <tomtiger11> paultag: i never read well on the internet, whats the point?
[19:23] <charlie-tca> tomtiger11: it is the color your irc client uses for that nick
[19:23] <paultag> No point. I'm off. Have a nice day :)
[19:23] <tomtiger11> bdmurray: how do i change the status of a bug?
[19:23] <charlie-tca> Usually those of us who are older don't mind telling ages
[19:24] <charlie-tca> tomtiger11: is the red nick a highlighted nick or just normal?
[19:24] <tomtiger11> charlie-tca: Id rather not start an irc argument
[19:24] <charlie-tca> Is it the only nick in a different color?
[19:24] <tomtiger11> charlie-tca: ^ is normal
[19:25] <charlie-tca> Are all the other nicks one color?
[19:25] <tomtiger11> charlie-tca: but the one above that is red
[19:25] <tomtiger11> charlie-tca: yes, but yours and pauls is red
[19:25] <charlie-tca> Most of the clients will color nicks to let you see them rapidly
[19:25] <charlie-tca> that's all it is
[19:26] <charlie-tca> Unless it only shows red when I give your name
[19:26] <tomtiger11> charlie-tca: i dont think mine does that
[19:26] <charlie-tca> tomtiger11: did this go red?
[19:26] <tomtiger11> charlie-tca: yes
[19:26] <charlie-tca> or do all the lines from me go red?
[19:26] <charlie-tca> It is telling you someone wrote directly to your nick
[19:26] <tomtiger11> charlie-tca: just that one that you said my name on
[19:27] <charlie-tca> That is called a highlight
[19:27] <tomtiger11> charlie-tca: ok!
[19:27] <charlie-tca> It is to get your attention
[19:27] <tomtiger11> charlie-tca: i know that but it could have been different
[19:27] <tomtiger11> charlie-tca: ok, guys ive got to go
[19:27] <tomtiger11> charlie-tca: il talk tomorrow (GMT)
[19:28] <charlie-tca> okay, have fun
[19:28] <tomtiger11> bye
[19:28] <tomtiger11> =]
[19:28] <paultag> someone's pre-pubesent
[19:28] <paultag> Oh crap, did not mean to write that out loud. /clear
[19:28] <charlie-tca> heh
[19:29]  * charlie-tca hates when he talks out loud by accident
=== paultag is now known as paulbag
[19:50] <hggdh> now, that one was an interesting dialog
[19:50]  * hggdh is happy to have been elsewhere
[19:51] <roadmr> but you still got to read it - best of both worlds
[19:55] <hggdh> yes!
[19:55] <yofel> does someone know why the debian-installer apport-hook doesn't collect /var/log/installer/* ?
[19:58] <hggdh> yofel: /var/log/installer/ is only created after the install completes. Maybe because of that?
[19:58] <yofel> well, I wanted to file a bug about the installer *after* install, wouldn't the installer logs be usefull?
[19:58] <hggdh> then yes, certainly
[19:59] <hggdh> and, stoipping to think about it, I doubt apport would be able to run *during* install... bdmurray ^?
[20:00] <bdmurray> hggdh: could you repeat the question fully?
[20:01] <hggdh> bdmurray: why the apport hook for debian-installer does not collect /var/log/installer?
[20:03] <bdmurray> hggdh: I don't have an answer but do know how to fix it
[20:04] <hggdh> yofel: ^ :-)
[20:04] <yofel> :)
[20:09] <hggdh> bdmurray: so you will do it, or should I?
[20:09] <bdmurray> I'll do it
=== yofel_ is now known as yofel
=== paulbag is now known as paultag
=== Ursinha is now known as Ursinha-afk
=== kentb is now known as kentb-out