[02:05] <glaucovinicius> Hello people!
[02:07]  * Ienorand says: "Hush, this channel is sleeping"
[02:07] <Ienorand> :)
[02:29] <wolfger> huh? what?
[03:01] <PCTeacher012> Okay, Ubuntu Community needs to learn to send emails to bug support team members in MODERATION. i have 900 from it <_<
[03:01] <PCTeacher012> lol
[03:03] <Hobbsee> PCTeacher012: which list did you subscribe to?
[03:06] <PCTeacher012> the bug list i think
[03:06] <PCTeacher012> i dont remember, but i have tothank them for 1291 + 97emails lol
[03:07] <Hobbsee> well, that's warned to be a high email list...
[03:07] <hggdh> pretty much every and all bug opened or commented on...
[03:07] <PCTeacher012> ya, i didnt know that till now and through those emails, i have to find password reset toCHANGE it D:
[03:08] <hggdh> you should have received it, probably buried in the 900+ emails you got
[03:08] <PCTeacher012> i did, and it sucks, but i finally fouindit
[03:09] <PCTeacher012> okay, now how do i unregister from it? i dont see uit
[03:11] <Hobbsee> at the bottom of every email, it tells you how to, usually
[03:12] <PCTeacher012> it doesnt tell me:( 1754 DELETED <_<LOL
=== Vantrax is now known as Vantrax|away
[04:46] <leoXsys> Can anybody tell me where ubuntu-bus is stored all reports before uploading to Launchpad?
[04:48] <lifeless> /var/crash
[04:48] <lifeless> or something like that
[04:48] <leoXsys> lifeless: I think that will stored the crash report.
[04:50] <leoXsys> lifeless: Look, My problem is i want to report one bug, it has been already reported, but the reporter has not provided the enough information, But i have collected using ubuntu-bug, but that i can only use with new, Bug, is there any facility in LP that i can attach with already reported bug?
[04:56] <leoXsys> Looks like i have asked the dumb question :(
[04:56] <persia> leoXsys, There isn't such a facility, to my knowledge.
[04:57] <leoXsys> persia: Ok
[04:57] <persia> You could use ubuntu-bug to report the bug, and then mark it duplicate, and leave a comment saying "I've replicated on my system, and uploaded debugging information to bug #nnnnnn".
[04:57] <leoXsys> persia: But can i know the location, where ubuntu-bug is storing all reports before uploading to the LP?
[04:57] <persia> The new duplicate shouldn't show in most searches, but someone reviewing the bug can easily get to the additional information.
[04:58] <persia> It stores it in /var/crash, but in a format that isn't obvious.
[04:58] <persia> If you *really* want, you can fiddle with apport-retrace to try to extract the information.
[04:59] <leoXsys> persia: Yes, I am doing something same...
[05:26] <leoXsys> Ok, I got the solution for my problem, Rather then using 'ubuntu-bug", You can use "apport-cli  -f -P PID", then it will give you option to to Send/View/Keep/Cancel, Just View it and save it in your desire location with desire name, attached to existing bug :)
[05:32] <leoXsys> persia: I have provided the enough information to one "Incomplete' bug, So, now which would be next status? Should i make it "New" again, so it get noticed to Developer/
[05:35] <sbeattie> leoXsys: apport-collect <bugnumber> will attach your information to an existing bug report
[05:38] <persia> sbeattie, That's *extremely* useful.  Thanks!
=== Vantrax|away is now known as Vantrax
[06:32] <leoXsys> sbeattie: Oh, Thanks :)
[06:35] <leoXsys> sbeattie: But, when i want to attach the report to existing bug like "X package / Applet is utilizing 100%CPU / Memory" then i think we also requires Memory Dump, which apport-collect will not gathered :(
=== seb128_ is now known as seb128
=== Brownout_ is now known as Brownout
[15:04] <bddebian> Boo
[15:05] <pedro_> buuu!
[15:05] <BUGabundo> foo
[15:06] <bddebian> :)
=== fader_ is now known as fader|lunch
=== ccooke_ is now known as ccooke
=== fader|lunch is now known as fader_
=== ivoks_ is now known as ivoks
[21:18] <maxb> I'm trying to figure out what program draws the gnome system monitor graphs in the panel. I'm slightly confused because I can't see any process running corresponding to it, unlike the other panel applets. Any help? :-)
[21:19] <pedro_> maxb: that's the multiload applet which is part of gnome-applets
[21:19] <bdmurray> maxb: apt-cache search monitor | grep gnome
[21:20] <maxb> pedro_: aha!
[21:20] <pedro_> maxb: process is called multiload-applet-2
[21:21] <maxb> this means I should report a bug strictly in the panel graphs against gnome-applets, not gnome-system-monitor, I assume?
[21:23] <pedro_> maxb: that's correct
=== stpere is now known as goinghome
=== goinghome is now known as stpere|goinghome
=== yofel_ is now known as yofel
=== stpere|goinghome is now known as stpere