[01:45] <bcurtiswx> what package has glib.h ?
[01:49] <BUGabundo> bcurtiswx: have you tried dpkg -S glib.h?
[01:49] <bcurtiswx> no, didn't know i could :D
[01:50] <bcurtiswx> thx
[02:01] <bcurtiswx> BUGabundo1: what package can i install that has all the important dev packages
[02:01] <BUGabundo1> none
[02:03] <bcurtiswx> haha, darn, ok
[02:13] <bcurtiswx> BUGabundo1: -lGL looks for libgl right?
[02:13] <BUGabundo1> no idea
[02:13] <bcurtiswx> hmm, ok
[02:13] <BUGabundo1> didn't search for it
[02:19] <brocgiddens> I want to help with bugs but am new to the process
[02:21] <bcurtiswx> brocgiddens: check out https://wiki.ubuntu.com/Bugs/HowToTriage
[02:21] <brocgiddens> looking at that now
[02:21] <brocgiddens> its one of those things where i really love ubuntu but i'm new enough not to know alot
[02:21] <brocgiddens> but i want to contribute
[02:22] <bcurtiswx> brocgiddens: we all start that way :D
[02:24] <brocgiddens> thanks for the encouragment
[02:24] <bcurtiswx> brocgiddens: anyone in here is more than willing to help you out along your way of learning triage.  don't hesitate to ask any question you have... i've already paved the way for the dumb questions..
[02:25] <brocgiddens> so is it enough just to find a new bug and comment that I have had the same problem?
[02:27] <brocgiddens> i just did that on one, related to Intel HDA alsa driver.  I couldn't get mine to work until I broke down and did a clean install.  That fixed it.
[02:27] <bcurtiswx> brocgiddens: theres something in launchpad that says "this bug does not effect me", you can click that and change it to "this bug effects me too", we don't want all the "yeah i get this too" comments in bugs
[02:28] <brocgiddens> oh ok.  mine was more than that but I know the answer isn't always a clean install, I will look for the option to do that instead next time
[02:29] <bcurtiswx> brocgiddens: a good start to bug traige is finding bug duplicates
[02:30] <bcurtiswx> but i'd suggest reading up on that website I gave you
[02:30] <brocgiddens> oh ok.  why on some bug reports does it say i386 in one place and i686 in another.  in the same report
[02:31] <bcurtiswx> well, that all depends on how the bug has changed through its life
[02:31] <bcurtiswx> whats an example bug
[02:32] <bcurtiswx> type 'bug #xxxxxx'
[02:32] <brocgiddens> 384107
[02:32] <bcurtiswx> type bug and make sure to include the #
[02:32] <bcurtiswx> like bug #384107
[02:32] <ubot4> Launchpad bug 384107 in firefox-3.0 "pandora.com crashes firefox 3" [Undecided,New] https://launchpad.net/bugs/384107
[02:32] <brocgiddens> bug #384107
[02:32] <bcurtiswx> that way ubot lists it :-)
[02:32] <brocgiddens> gotcha
[02:34] <hggdh> sometimes ;-)
[02:36] <bcurtiswx> hggdh: may I PM you?
[02:36] <hggdh> of course
[02:39] <brocgiddens> so, any reason it lists both 386 and 686?
[02:44] <bcurtiswx> im not sure exactly
[02:44] <hggdh> brocgiddens, looking at it
[02:45] <hggdh> !log
[02:45] <ubot4> Official channel logs can be found at http://irclogs.ubuntu.com/ - For LoCo channels, http://logs.ubuntu-eu.org/freenode/
[02:45] <bcurtiswx> stgraber: are you there?
[02:45] <hggdh> bcurtiswx, ^^
[02:45] <bcurtiswx> ty
[02:46] <hggdh> brocgiddens, then 686 is the version of the kernel you are running. I do not think we still compile for 386
[02:46] <hggdh> s/then/the/
[02:47] <hggdh> the Arch: i386 indicates this code is compiled for an Intel-compatible, 32 bits
[02:47] <brocgiddens> ok, that is the app
[02:47] <brocgiddens> but its in a 64 bit kernel?
[02:47] <hggdh> Arch has a series of possible values, and each indicate one type of CPU
[02:48] <hggdh> no, this is on a 32-bit kernel
[02:48] <hggdh> a 686 is 32 bits
[02:49] <brocgiddens> whats the dif between 686 and 386?
[02:49] <hggdh> so. The uname line states this kernel was compiled for a i686/compatible CPU; the Arch line on the app states the Architecture used to build the app was a i386 (i.e., Intel-compatible, 32 bits
[02:50] <hggdh> one is for the kernel, one is for the app
[02:50] <hggdh> unfortunately they pretty much mean the same (er, sort of)
[02:50] <brocgiddens> lol
[02:50] <hggdh> but use different names
[02:50] <brocgiddens> ok, i'll stop asking questions before i confuse myslef
[02:50] <brocgiddens> myself
[02:51] <hggdh> on the kernel: this kernel should *not* be able to run on a real i386
[02:52] <brocgiddens> I'll dive into the howto wiki for now and check back with more (on topic) questions later
[02:52] <hggdh> brocgiddens, no prob ;-)
[02:54] <hggdh> bcurtiswx, try the -motu channel
[02:54] <hggdh> but it is probably late now
[02:54] <bcurtiswx> k
[02:54] <hggdh> late as time-of day, I mean
[02:55] <bcurtiswx> i know :P
[10:10] <askand> Backporting tomboy 0.15 from Karmic to Jaunty (currently at 0.14) would fix bug 581582, what is the things one should do to backport something?
[13:25] <porthose1> !backports
[13:25] <ubot4> If new updated Ubuntu packages are built for an application, then they may go into Ubuntu Backports. See https://help.ubuntu.com/community/UbuntuBackports - See also !packaging
[13:26] <porthose1> !packaging
[13:26] <ubot4> The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[15:15] <leoquant> ! sun java update -13
[15:15] <ubot4> leoquant: Error: I am only a bot, please don't think I'm intelligent :)
[15:15] <leoquant> !sun java update -13
[15:15] <ubot4> leoquant: Error: I am only a bot, please don't think I'm intelligent :)
[16:44] <xteejx> Hi guys, I need a suggestion with bug 377060 - should portaudio be added as an assigned package to this bug?
[16:44] <ubot4> Launchpad bug 377060 in espeak "[jaunty karmic] espeak missing words and phonemes from sentences" [Low,Confirmed] https://launchpad.net/bugs/377060
[17:41] <xteejx> https://code.launchpad.net/~pwlars/bughelper/bughelper.364896/+merge/5766 how long does it normally take for something to be released?
[17:53] <hggdh> xteejx, in this case it depends on Markus or Brian...
[17:53] <xteejx> hggdh, oh right ok heh just wondered :)
[17:55] <hggdh> :-)
[17:55] <asac> bcurtiswx: what use case are you using gnome-ppp for? old modem style dialup?
[17:56] <BUGabundo> hey asac that's an HUGE backlog
[17:56] <BUGabundo> lol
[17:56] <asac> :)
[17:56] <Hew> Damn, the number of open bugs is exploding. I'm sure it was only a few months ago it was under 50k, now it's about to break 60k..
[17:57] <bcurtiswx> asac: i was talking about bug #384060, let me try to refresh my memory
[17:57] <ubot4> Launchpad bug 384060 in gnome-ppp "gnome-ppp needs sudo" [Undecided,Incomplete] https://launchpad.net/bugs/384060
[17:57] <asac> bcurtiswx: yeah. just was curious why you use gnome-ppp at all
[17:57] <BUGabundo> asac: its not bcurtiswx... it's a bug triage
[17:57] <asac> but its old style modem
[17:57] <bcurtiswx> asac: i personally don't, its the bug
[17:57] <asac> ok ok ;)
[17:58] <bcurtiswx> asac: nothing wrong with old-school though
[17:58] <xteejx> bencrisford, Evening :)
[17:59] <bcurtiswx> i was just wondering based on that bug, whether gnome-ppp by default should ask for sudo when calling it as a user before launching the GUI
[17:59] <asac> depends. usually "normal" users probably should be in a group that allows dialup
[18:00] <asac> in the long run all this should probably be replaced with some policykit like implementation
[18:00] <bcurtiswx> asac: so should I treat that bug as a wishlist item or continue triaging the "problem" ?
[18:00] <asac> i dont think we should add more sudo logic anymore as we try to get rid of it in general
[18:01] <BUGabundo> yay
[18:01] <BUGabundo> asac: what happened with coreutils?
[18:01] <BUGabundo> heard something was wrong?
[18:01] <asac> i didnt investigate coreutls ;)
[18:01] <BUGabundo> when I upgrade it asked me to remove mktemp
[18:01] <BUGabundo> and then I got an update  from it the next day
[18:02] <bcurtiswx> BUGabundo: wait your turn :P asac is mine right now
[18:02] <BUGabundo> ahahahahahaa
[18:02] <asac> bcurtiswx: check whether gnome-ppp binary has some special group rights attached
[18:02] <asac> and check if that matches a group we normally add users to
[18:03] <asac> bcurtiswx: if there is a mismatch (e.g. gnome-ppp uses dialup, but user has just dip) thats a bug
[18:04] <bcurtiswx> and how do i check binary?
[18:04] <asac> otherwise its a wishlist bug you can file upstream
[18:04] <asac> bcurtiswx: ls -la path/to/binary
[18:05] <bcurtiswx> oh, i thought i was checking code or something here :-X
[18:07] <asac> bcurtiswx: also user should check what permissions the /dev/modem device (or whatever device he uses) has
[18:09] <xteejx> Bug 155473 - how should this be debugged? It looks like there's enough info for a developer, but not too sure.
[18:09] <ubot4> Launchpad bug 155473 in hal "/media/.hal-mtab not cleaned up after restart" [Unknown,Confirmed] https://launchpad.net/bugs/155473
[18:11] <asac> bcurtiswx: so we have ls -l /dev/ttyS0
[18:11] <asac> crw-rw---- 1 root dialout 4, 64 2009-06-01 12:36 /dev/ttyS0
[18:12] <asac> meaning that if user is in dialout group all should be fine
[18:13] <bcurtiswx> ok, so ask the user for the output of ls -al /usr/bin/gnome-ppp and ls -l /dev/ttyS0 to see if theres a problem there?
[18:13] <bcurtiswx> asac: ^^
[18:24] <bcurtiswx> xteejx: its been upstreamed, which is good.  But it lacks any important information for devs in Ubuntu.  We don't know which version of Ubuntu it was reported against, and since i'm guessing theres been upgrades to ubuntu since, we don't know if its fixed in a later release.
[18:26] <bcurtiswx> on a side note, this is why i wish the bug report gui for launchpad would grab Ubuntu version and Package version info on a report (not reported through apport).. thankfully apport-collect is available now, but for now it's only good for jaunty/karmic bugs
[18:26] <bencrisford> xteejx: I would say that is enough to go on, but only with the ubuntu version
[18:26] <bencrisford> without it, sensible devs wont start work on it until its there
[18:27] <xteejx> bcurtiswx, I TOTALLY agree with the apport-collect gui in LP, are you talking about the proposed idea of invoking apport from the LP report a bug pages? I'd definitely +1 it :)
[18:28] <xteejx> But yeah guys I agree, version at least, testing in later, etc etc
[18:29] <bcurtiswx> bdmurray: why don't we invoke apport-collect on launchpad reported ubuntu bugs ?
[18:40] <Hew> Uh, rhythmbox is currently using 100% of one of my CPU cores. How do I debug this?
[18:46]  * Hew debugs with killall rhythmbox :-)
[18:53] <bcurtiswx> Hew: what were you doing on rhythmbox before it went 100% CPY?
[18:53] <bcurtiswx> CPU*
[18:53] <Hew> it's just playing songs
[18:54] <Hew> I actually didn't get around to killing it so it's still going!
[18:56] <jpds> Hew: Install banshee.
[18:56]  * jpds runs away.
[18:57] <bcurtiswx> well it looks like banshee will be default in Karmic.. so yeah... thats not actually a bad idea
[18:57] <Hew> jpds: Banshee contains a critical bug, which is it depends on libmono* :-)
[18:58] <Hew> yea I heard something about that.. where did that discussion happen? UDS? Is there info about it somewhere?
[18:58] <jpds> Hew: At UDS - and it's probably on gobby.ubuntu.com
[18:58] <Hew> thanks jpds I'll have a look
[18:59] <Hew> hmm not much there..
[18:59] <Hew> looks like rhythmbox finally decided to stop eating my CPU, how strange
[18:59] <bcurtiswx> was it searching for album art?
[19:00] <bcurtiswx> or downloading something like that?
[19:00] <Hew> bcurtiswx: It happened for multiple songs, started with no user interaction, and ended the same
[19:06] <asac> bcurtiswx: replace /dev/ttyS0 with whatever modem device the user is using
[19:07] <bcurtiswx> asac: how can the user find out which one they're using?
[19:07] <asac> bcurtiswx: well. the user has to know
[19:08] <asac> if he just uses /dev/modem then he should look where the link points to
[19:08] <bcurtiswx> asac: ok, j/w if there was a way they could find out.. im expecting to get an "idk what i'm using" from the reporter
[19:08] <asac> bdmurray: well. he _enters_ that info in gnome-ppp dialog
[19:09] <asac> bcurtiswx: if he doesnt know its probably whatever ls -l /dev/modem shows
[19:09] <asac> which is usually a link to ttyS0, but could be somewhere else
[19:09] <asac> ok off for a while
[19:11] <bcurtiswx> bye asac: thx for help
[19:20] <DoMeN____> hy is this the right place to ask a question regarding a possible bug in ubuntu keyboard messages handling ( using x11 )?
[19:23] <jmarsden> DoMeN____: Try asking in #ubuntu .  #ubuntu-bugs is more about triaging existing bug reports.
[19:23] <DoMeN____> thx