[10:05] <LimCore> hi
[10:05] <LimCore> how we can get https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/309724 moving?
[10:05] <ubot4> Launchpad bug 309724 in pulseaudio "no sound after fast switching between logged in users" [Low,Confirmed]
[10:33] <LimCore> anyone alive?
[11:03] <Hobbsee> no, everyone's dead.
[11:04] <Hobbsee> looks like you'll need to argue that one with pulseaudio upstream
[11:08] <LimCore> yeah I'm doing that.  System wide should fix that.  But it is said to not work in Ubuntu?  I will check hopefully in free time.
[12:24] <Laibsch> Can somebody point out some valid Launchpad script examples?  https://wiki.ubuntu.com/BugHelper/Dev/python-launchpad-bugs/Examples seems to be outdated at least for the easy to understand example "Mass closing"
[12:24] <Laibsch> I don't always want to use the web interface
[12:24] <Laibsch> Anybody have some easy launchpadlib examples?
[15:28] <snappca> I'm a long time kubuntu user but I've never reported a bug before.  I have a brand new thinkpad t400s that has a lot of issues (mostly with keyboard functions but also docking/undocking).  After reading through the ubuntu webpages related to reporting bugs, I'm still not sure how best to proceed.  I was intending to start with some bugs related to keyboard functions not working.  Should I enter those separately via the LaunchPad interface?  Any help
[15:28] <snappca>  started would be appreciated.  I apologize if this is the wrong place to ask, I honestly haven't used IRC since the 90's.
[15:36] <bac> snappca: yes, please enter your bugs in launchpad separately.  do a search first, to make sure they have not already been reported.
[15:41] <snappca> bac: ok, thanks....I was concerned that reporting hardware specific bugs via the launchpad web interface was not the appropriate way.
[15:43] <snappca> bac:  should I be using a different IRC channel or bug interface since I use Kubuntu?  Or does it matter since these are hardware related bugs and Kubuntu is simply a variant of Ubuntu?
[15:59] <hggdh> snappca, there are kubuntu-specific channels; let me search
[16:00] <snappca> hggd: I blindly typed in #kubuntu-bugs and entered into a channel, but there were only a handful of people in there.  Also I was thinking hardware bugs were ok to talk about in the main #ubuntu-bugs channel
[16:01] <hggdh> snappca, you can go to #kubuntu-bugs for bug information on kubuntu (here we deal mostly with Gnome), and #kubuntu for general help
[16:01] <snappca> hggdh: ok, thanks for pointing me in the right direction
[16:01] <hggdh> snappca, if your hardware is not working with *ubuntu, then there is a bug somewhere, so it is OK to open one
[16:02] <hggdh> snappca, also: #ubuntu-bugs and #kubuntu-bugs usually deal with *triaging* of bug, not with general support
[16:04] <snappca> hggdh: ok, I'll make sure not to clutter the channel with more questions, I appreciate the help though.  Mainly I just didn't want to be cluttering up the ubuntu bug tracker with several separate keyboard function related issues if I was actually supposed to report those via a forum first.  I'm sure once I see how the bug reporting mechanism goes I'll be more comfortable with it.  I'm currently adding my first bug and it is easier than I thought
[16:09] <hggdh> snappca, you did not clutter the channel. You *did* have a question that -- to my understanding -- fully applies here. Also -- please keep in mind a basic rule for bugs: one issue per bug, one bug per issue. You will not be cluttering Launchpad at all
[16:10] <hggdh> snappca, additionally: if you have doubts on how to open the bugs, please do ask (on either of #(k)ubuntu-bugs): we are here to help on this.
[16:10] <hggdh> and, oh, yes, thank you for helping making (k)ubuntu better :-)
[16:11] <snappca> hggdh: glad to see I wasn't off base.  now I'm off to report several minor issues, thanks again for answering my questions
[16:11] <hggdh> welcome
[16:24] <LimCore> bdmurray: system wide pulse audio solves my problem
[16:25] <LimCore> sound can mute or not mute other desktop users on switching.   Now it always mutes.  Perhaps it should be a config option...  but well then it is perhaps not a bug, just users have to know how to switch it
[16:33] <bender304> Running Ubuntu 9.04 with OOo calc (3.0) make a simple chart with data in different rows and columns such as B1, C2, D3. The chart is now made. When I go to save the file I get an error that it can't save. So the bug is you can't save the .ods spread sheet when data is in different rows and columns. What works though is when the data is all in same row or column. I didn't have this problem in Ubuntu 8.10. Anyone notice the same or if this ha
[16:35] <LimCore> bender304: strange. can you fill in a bug report,  attache example .ods file and screeenshot
[16:35] <LimCore> I will tr to confirm
[16:36] <LimCore> on .04 amd64
[16:37] <bender304> OK I go and file a bug report
[20:30] <aguynamedryan> Hello.  cpqarrayd is crashing and throwing up a stacktrace.   I've never reported a bug before, but I notice there is already a ticket (#98820) that looks to be similar to the crash I'm seeing.  I'm running 9.04 server edition and I can't seem to find ubuntu-bug to help me capture error information.  I also can't seem to find anything in my log files that would help diagnose the problem.  I've reviewed the wiki pages ab
[20:40] <aguynamedryan> Hello.  Is anyone around?
[21:02] <mrooney> aguynamedryan: hi!
[21:03] <aguynamedryan> Hello!
[21:04] <aguynamedryan> I figured out I need to install apport to get ubuntu-bug
[21:04] <mrooney> ah okay
[21:04] <aguynamedryan> That was kinda noobish of me, but the wiki pages seem to assume that you know what apport is and that its already installed
[21:06] <aguynamedryan> I was hoping cpqarrayd would put a crash file in /var/crash, but there isn't anything there
[21:07] <aguynamedryan> And the stacktrace that I get on my screen doesn't show me what function cpqarrayd is calling to cause the crash
[21:08] <aguynamedryan> I guess the only real question I have is: should I post a message to ticket 98820, even though I have a different version of cpqarrayd, or should I submit a new ticket?
[21:16] <mrooney> let's see, bug 98820
[21:16] <ubot4> Launchpad bug 98820 in cpqarrayd "[apport] cpqarrayd crashed with SIGSEGV" [Medium,Incomplete] https://launchpad.net/bugs/98820
[21:17] <aguynamedryan> Whoa...that's cool...can I do that?  bug 99820
[21:17] <ubot4> Launchpad bug 99820 in nexuiz "Use the current version as lower version limit for nexuiz-data (dup-of: 95002)" [Undecided,New] https://launchpad.net/bugs/99820
[21:17] <ubot4> Launchpad bug 95002 in edgy-backports "Can't upgrade nexuiz from edgy-backports" [Medium,Fix released] https://launchpad.net/bugs/95002
[21:17] <mrooney> haha
[21:17] <aguynamedryan> Wow!  Fancy
[21:17] <mrooney> aguynamedryan: so what I would recommend since that bug is so old, is file a new one, and add a comment in the old one saying you weren't sure if it was the same so you filed a new bug and link to it
[21:18] <aguynamedryan> Awesome.  Thanks!
[21:23]  * mrooney waves to BUGabundo
[21:23] <BUGabundo> hey mrooney
[21:58] <hggdh> aguynamedryan, what type of failure are you getting? sigsegv, sigabrt, etc?
[21:58] <aguynamedryan> Looks like a sigabrt
[21:59] <aguynamedryan> I'm just now following the instructions under:  https://wiki.ubuntu.com/DebuggingProgramCrash and https://wiki.ubuntu.com/Backtrace
[21:59] <aguynamedryan> Before I submit a ticket
[21:59] <hggdh> ah. Please be aware that apport does *not* trap SIGABRTs
[21:59] <micahg> hggdh: that's good to know :)
[21:59] <aguynamedryan> hggdh: Thanks for the confirmation about that.  I was wondering why I was just getting package information when I used ubuntu-bug
[22:00] <hggdh> so... you would probably need to run cpqarrayd manually under GDB, and do the stack trace yourself (thread apply all bt full)
[22:00] <hggdh> micahg, yes... I do not know why it was disabled... sigabrts usually are set by libc on malloc issues
[22:01] <hggdh> and they *still* are (usually) an indication of memory management issues in the appl
[22:01] <hggdh> aguynamedryan, you are welcome, just did not want you to find the hard way ;-)
[22:02] <aguynamedryan> Thanks!
[22:02] <micahg> hggdh: can that be document on the apport wiki page if it isn't already?
[22:02] <micahg> *documented
[22:02] <hggdh> micahg, it should be there, if it is not, then certainly!
[22:09] <micahg> hggdh: doesn't seem to be on there
[22:14] <hggdh> hum
[22:15] <aguynamedryan> Yay!  My first bug report: bug 409060
[22:15] <ubot4> Launchpad bug 409060 in cpqarrayd "cpqarrayd crashes while checking for controllers" [Undecided,New] https://launchpad.net/bugs/409060
[22:16] <aguynamedryan> I love that feature!  Thanks ubot4!
[22:19] <hggdh> micahg, do you have a suggestion of where to put it? Right now I am considering adding it at the end of "How to enable apport"
[22:20] <BUGabundo> aguynamedryan: LOL
[22:20] <BUGabundo> I've forgot what my was even about
[22:21] <BUGabundo> or what release
[22:21] <BUGabundo> 6.06 or 6.10
[22:21] <micahg> I think actually it might be better to add another section of what apport will NOT do ;)
[22:21] <BUGabundo> not sure
[22:21] <BUGabundo> been on ubuntu since 5.10
[22:21] <aguynamedryan> Nice!
[22:22] <aguynamedryan> I played around with it back then, but my company ended up going in a different direction for a while.  Now we're exploring our Linux options and I made sure we put Ubuntu on this list
[22:26] <hggdh> micahg, added in
[22:27] <hggdh> (sort of small, I know, but let's see what happens)
[22:28] <micahg> ok
[22:29] <hggdh> aguynamedryan, thanks :-) and also thank you for reporting the bug (which, hopefully, someone with knowledge of the programme will look at, eventually)
[22:31] <aguynamedryan> hggdh: Thanks!  I'm poking around the source right now trying to see if I can figure out what's dying...I'm so happy to be back in FOSS land!
[22:32] <hggdh> way to go, way to go!
[22:32] <aguynamedryan> hggdh: I'm not making any promises ;-)
[22:33] <hggdh> aguynamedryan, we are not asking for promises. The simple fact that you got back to FOSS, and is looking at Ubuntu (and, even in a small way, helping) is already good enough
[22:34] <aguynamedryan> hggdh: It's my pleasure!
[22:34]  * hggdh gratefully bows
[22:35]  * BUGabundo now knows why hggdh complains of his back
[22:35] <aguynamedryan> haha!
[22:36] <hggdh> :-)
[22:36] <hggdh> ah well. Time to get back to the hotel. Will be back in about 30 min