[03:34] <calc> bdmurray: i think the graphs broke again
[03:35] <calc> bdmurray: nevermind they just updated again, looks like they were broken for a couple hours though
[12:06] <tapas> today i tried to boot my system which worked fine yesterday and it hang at some hot/cold/power management stuff
[12:07] <tapas> booting an older kernel seems to have worked
[12:07] <tapas> [    0.704238] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[12:07] <tapas> stuff like that.
[12:07] <tapas> it might have something to do with a package upgrade done yesterday
[12:07] <tapas> is there a log about what packages got installed at what time?
[12:09] <tapas> so i can file a bug report about that package?
[12:18] <Nafallo> tapas: /var/log/dpkg.log /var/log/apt/term.log
[12:39] <mnemo> when I run "git-format-patch" bash tells me the command is not installed and that I must install "git-core" to get this command... then I run "apt-get install git-core" and re-run the command but it still says I need package "git-core" ??  this works on intrepid just fine but it seems broken on jaunty --> http://rafb.net/p/DJg2a121.html
[12:41] <mnemo> so is the jaunty git-core package corrupt or something?
[12:41] <mnemo> does anyone else see this behavior?
[12:41] <mnemo> should I file a bug on it?
[12:41] <petski> mnemo: in intrepid git-core: /usr/bin/git-format-patch , in jaunty /usr/lib/git-core/git-format-patch
[12:42] <petski> in jaunty, the git-format-patch tool isn't in PATH, so it cannot be found
[12:43] <mnemo> aah, why isn't it in path? is that a bug?
[12:43] <petski> don't know, maybe it's by design
[12:43] <petski> I suggest you submit a bug .. (please add the information about intrepid git-core: /usr/bin/git-format-patch , in jaunty /usr/lib/git-core/git-format-patch)
[12:46] <petski> your nick rings a bell, hehe (LP: #276603)
[12:47] <mnemo> yeah that's me ;)
[12:47] <petski> hi :)
[12:48] <mnemo> hi ;>
[12:51] <mnemo> petski: seems like all the git-BLAH commands have been deprecated now... replacement is like "git format-patch" etc
[12:51] <mnemo> https://bugs.launchpad.net/ubuntu/+source/git-core/+bug/301905
[12:52] <petski> aha, if that's the case, it should be stripped from the "package suggests"
[12:52] <mnemo> yup, I will file such a bug
[12:53] <petski> ok, super. Unfortunalty have to go now. Bye
[12:55] <mnemo> bye
[13:57] <LimCore> hi, how to debug more https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/268925 ? would be good to fix it finally, because otherwise using kmail+pgp is epic fail
[14:10] <Crewsr3> I'm new to helping with bugs and I would like to contribute.  There is a bug   318336   That I'm looking at and I cannot reproduce it.  Can someone help me run the same reports that orbitcowboy did to see if my output is diffrent
[14:21] <savvas> Crewsr3: If I were you I would first ask these questions: 1) does it happen every time? 2) Can you create a new user and try again? 3) If (2) does not crash, close firefox on your user, backup your profile ( command in Terminal: mv .mozilla mozilla-backup ) and run firefox again. Does it work now?
[14:22] <savvas> crashes usually happen because they use their old profiles
[14:24] <savvas> Crewsr3: Also, it might be better to cut that 1,2,3 in a few lines :)
[14:28] <Crewsr3> savvas, thanks, I will ask those questions, someone from my loco also recommend asking to try it without any addons enabled
[14:30] <savvas> Crewsr3: Users usually download their own extensions rather than using the packages from the ubuntu repositories. If they clear their profile ( .mozilla folder in home/youruser folder ), they probably will have cleared all their extensions as well :)
[14:35] <Crewsr3> savvas, good to know, I will outline the risk and encourage a backup like you mentioned before
[14:41] <LimCore> btw, I find this amusing that we have an over 1 year old security exploit
[14:42] <LimCore> with phisical access to some locked boxes (30% ?) you can see what was on the screen more or less
[16:02] <hggdh> LimCore, what security exposure?
[16:09] <hggdh> meaning what bug number?
[18:58] <afflux> any ideas what bug 318499 is about?
[18:59] <kylezoa> Bug #318169 send over to wishlist please
[19:01] <afflux> is the networkmanager thing really something for brainstorm? Sounds like a proper wishlist bug imho.
[19:02] <Rocket2DMn> is that how it normally behaves?
[19:03] <Rocket2DMn> i dont use kde, idk if its supposed to behave like that.
[19:04] <Rocket2DMn> afflux, i think i see what is up with that other bug
[19:04] <Rocket2DMn> there is discoloration
[19:07] <Rocket2DMn> i kinda think its supposed to be like that though
[19:18] <afflux> Rocket2DMn: don't know that's wrong with that
[19:18] <Rocket2DMn> with what
[19:18] <Rocket2DMn> the kde one or the image?
[19:18] <afflux> Rocket2DMn: the usplash
[19:19] <Rocket2DMn> i think its just limited by the number of pixels and the colors available
[19:20] <afflux> Rocket2DMn: are we talking about the same thing? What discoloration do you mean exactly?
[19:21] <Rocket2DMn> if you zoom in on that splash image you can see where the colors vary
[19:21] <Rocket2DMn> i think that is what the OP was getting at
[19:21] <afflux> Rocket2DMn: around the center of the yellow bar?
[19:22] <afflux> or the orange dot
[19:23] <Rocket2DMn> yeah
[19:23] <afflux> that's most probably intended, I think.
[19:23] <Rocket2DMn> i think they just need to use a low quality image because not everybody's video card or monitor can support the full range of colors
[19:24] <afflux> if more colors would be possible at all at this time of booting.
[19:26] <afflux> Rocket2DMn: about the knetworkmanager: I may be wrong about brainstorm, but I thought that's more of a voting and discussion forum. This request is a simple missing option, which imho is more of a bug.
[19:27] <thekorn> I think it is about the unbalanced gap between the orange circle and the yellow part of the logo
[19:27] <afflux> thekorn: you mean the dot should be half a pixel raised?
[19:28] <Rocket2DMn> afflux, its not a problem with an existing feature, so its really a wishlist item.  nothing is actually broken
[19:28] <afflux> (kind off)
[19:28] <afflux> -f
[19:28] <Rocket2DMn> as far as brainstorm goes, i agree, its not really a brainstorm type request
[19:28] <afflux> Rocket2DMn: wishlist of course, but I wonder if it should go to brainstorm as the comments suggest.
[19:28] <afflux> *comment suggests
[19:29] <afflux> what happend to my spelling? :(
[19:29] <thekorn> afflux, don't know, I'm no artist, but it looks like the it could be raised a bit
[19:30] <thekorn> but I'm not sure if this is an important bug to fix,
[19:30] <afflux> thekorn: I'll ask the reporter what the problem is.
[20:06] <maco> apport fails 100% of the time at uploading crash reports for me. is there a way i can upload the info myself and still have launchpad retrace it?
[20:13] <charlie-tca> You can get the crash logs from /var/crash. The format is harder to read, but it should all be there
[20:13] <charlie-tca> I just attach it as a separate attachment
[20:15] <maco> right ive got that
[20:15] <maco> but does apport-retrace still need to hapen?
[20:15] <charlie-tca> I don't know.
[20:58] <hggdh> maco, how does apport fails? There are two different failues: (1) it tries to open file://, or it does not find the link
[20:58] <maco> urlopen timeout
[20:59] <hggdh> OK. it seems if you wait some 2 minutes, it will work
[20:59] <hggdh> then just hit the reload
[21:00] <hggdh> apport-retrace is only useful if you are going to open a gdb session on the crash, or if you want to load the corresponding dbgsym
[21:01] <hggdh> charlie-tca, usually a .crash is not really useful -- too much work to get it all out, mostly if your local configuration does not match the reporter's
[21:01] <charlie-tca> yeah, misunderstood the question
[21:01] <maco> there was no reload...
[21:02] <maco> its just "send report" or "cancel"
[21:03] <hggdh> maco are you under firefox or apport-gtk?
[21:03] <maco>  apport-gtk
[21:03] <maco> network manager (the service, not the applet) crashed
[21:03] <hggdh> ah. click on send report. Now, what happens?
[21:04] <maco> then it does the loady bar for a while, then it gives an error about urlopen timeout
[21:04] <hggdh> still under apport-gtk?
[21:04] <maco> firefox doesnt open at all
[21:04] <hggdh> dammit
[21:04] <hggdh> sigh
[21:04] <maco> i mean, i can start firefox, but apport doesnt get it open
[21:04] <hggdh> what version of apport are you running?
[21:04] <maco> 0.127
[21:05] <hggdh> OK. So there are 3 different errors... :-(
[21:05] <hggdh> maco, you can still load & get a stacktrace locally
[21:05] <hggdh> 1. cancel apport-gtk
[21:06] <hggdh> 2. sudo apport-retrace -o an-output-file.name /var/crash/_usr_etc, etc
[21:06] <hggdh> this will load all possible dbgsyms
[21:07] <hggdh> and do a retrace. Then you can either look at the output file, or run apport-retrace -g on the crash
[21:07] <hggdh> if on gdb, just do a thread apply all bt full, and load on the LP bug the output
[21:07] <maco> what's the ", etc" bit? does something come after /var/crash/_usr.....0.crash?
[21:08] <hggdh> no, just the full crash file name
[21:08] <maco> ok
[21:08] <maco> lots of -dbgsym packages not available...
[21:10] <hggdh> yes, it may, or may not, be a problem. Apport goes through the depends list, and on the list of loaded libraries, and try to install all
[21:10] <maco> hggdh: should i be worried by all the "WARNING: package lib*-dbgsym not available" messages?
[21:10] <maco> ok
[21:11] <hggdh> normally no need to worry. If the stacktrace you get not many ??'s, it is probably good enough.
[21:11] <maco> ok
[21:11] <maco> i should at some point learn to read gdb output better
[21:11] <hggdh> heh
[21:11] <maco> right now i put it in the "black magic" categor
[21:11] <maco> y
[21:11] <hggdh> black magic box
[21:12] <maco> what's the -g thing you suggested as an "or"?
[21:13]  * maco checks for sensitive data since it crashed in "network_manager_clear_secrets()"
[21:14] <hggdh> the -g runs gdb
[21:15] <maco> should i do that too? or is the first enough
[21:15] <hggdh> probably the first already got a backtrace
[21:15] <hggdh> less it, and check
[21:15] <maco> ok
[21:15] <maco> stack trace == back trace ?
[21:16] <hggdh> for all that matters, yes
[21:16] <maco> ok
[21:18] <hggdh> on gdb, 'bt' means 'backtrace'; a 'bt' will trace the current thread
[21:18] <maco> yeah ive followed the bactrace directions before
[21:19] <hggdh> if there are many threads (usual), then you should bt all: 'thread apply all bt'
[21:19] <maco> and used it to step through my own code a few times
[21:19] <hggdh> there you go ;-)
[21:21] <maco> holy crap this includes a LARGE chunk of /var/log/messages...like 4 hours after the crash
[21:25] <hggdh> it's the n-m hook in apport, collecting the messages that (may) shed light on the crash
[21:27] <maco> hggdh: thank you
[21:27] <hggdh> welcome
[21:28] <hggdh> maco, I remembered one small detail...
[21:28] <hggdh> sometimes apport-retrace will load a dbgsym for a previous version of the corresponding package, breaking dpkg
[21:28] <maco> im up to date
[21:29] <hggdh> oh, YOU may be up-to-date, but not the dbgsym repos
[21:29] <maco> oh ok
[21:29] <hggdh> all you will need to, if that happens, ir run synaptic, go to the "broken" packages, and unselect the offending dbgsyms
[21:30] <hggdh> I proposed a patch for it, but it has not yet been looked at
[21:30] <maco> is it just me or has libgnome been broken for days?
[21:31] <hggdh> I have seen no indication of that -- what happens?
[21:31] <afflux> macd: do you have the ddebs repository in apt/sources.list?
[21:31] <maco> yes
[21:31] <afflux> ah, good.
[21:33] <afflux> hggdh: the urlopen timeout thingy prevents basicly any crash reporting since the beginning of the jaunty cycle, as I see it. seems to be a LP problem
[21:34] <hggdh> afflux, this is what I remember from a discussion here some weeks (?) ago. There was a bug opened on it, and it was later on closed
[21:34] <hggdh> this is not good at all
[21:34] <maco> oh goody
[21:34] <afflux> hggdh: do you happen to have the bug at hand?
[21:34] <maco> normally i dislike apport for spamming LP, but i think thats why its disabled in final
[21:34] <hggdh> afflux, let me check
[21:36] <charlie-tca> bug 314212
[21:37] <afflux> charlie-tca: thanks
[21:37] <hggdh> the bug I remembered (maybe wrong, I am old and senile) had been closed stating this was corrected on LP
[21:39] <charlie-tca> hggdh: you are probably right, too. Your memory is better than mine.
[21:40] <hggdh> charlie-tca, thank you for your vote of confidence, but what is this conversation about? ;-)
 I am old and senile) had been closed stating this was corrected on LP
[21:42] <hggdh> charlie-tca, there you go... see how my memory is good? ;-D
[21:42] <charlie-tca> haha
[21:42] <afflux> I'm going to bed now. good night.
[21:42] <hggdh> g'night