=== MTecknology is now known as SomeoneElse === SomeoneElse is now known as MTecknology [03:34] bdmurray: i think the graphs broke again [03:35] bdmurray: nevermind they just updated again, looks like they were broken for a couple hours though === sepheebear is now known as Sepheebear === tim__sharitt is now known as tim_sharitt === ziroday` is now known as ziroday === HarassmentPanda| is now known as HarassmentPanda [12:06] today i tried to boot my system which worked fine yesterday and it hang at some hot/cold/power management stuff [12:07] booting an older kernel seems to have worked [12:07] [ 0.704238] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold [12:07] stuff like that. [12:07] it might have something to do with a package upgrade done yesterday [12:07] is there a log about what packages got installed at what time? [12:09] so i can file a bug report about that package? [12:18] tapas: /var/log/dpkg.log /var/log/apt/term.log [12:39] 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] so is the jaunty git-core package corrupt or something? [12:41] does anyone else see this behavior? [12:41] should I file a bug on it? [12:41] mnemo: in intrepid git-core: /usr/bin/git-format-patch , in jaunty /usr/lib/git-core/git-format-patch [12:42] in jaunty, the git-format-patch tool isn't in PATH, so it cannot be found [12:43] aah, why isn't it in path? is that a bug? [12:43] don't know, maybe it's by design [12:43] 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] your nick rings a bell, hehe (LP: #276603) [12:47] yeah that's me ;) [12:47] hi :) [12:48] hi ;> [12:51] petski: seems like all the git-BLAH commands have been deprecated now... replacement is like "git format-patch" etc [12:51] https://bugs.launchpad.net/ubuntu/+source/git-core/+bug/301905 [12:51] Launchpad bug 301905 in git-core "git-core in Jaunty does not include git-* commands" [Undecided,Invalid] [12:52] aha, if that's the case, it should be stripped from the "package suggests" [12:52] yup, I will file such a bug [12:53] ok, super. Unfortunalty have to go now. Bye [12:55] bye [13:57] 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 [13:57] Launchpad bug 268925 in kdepim "openpgp asks each time for pin/passphrase to the key instead caching it (kgpg? gpg agent is not helping)" [Undecided,New] [14:10] 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:10] Launchpad bug 318336 in firefox-3.0 "firefox crashed" [Undecided,New] https://launchpad.net/bugs/318336 === Hurtz_ is now known as Hurtz [14:21] 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] crashes usually happen because they use their old profiles [14:24] Crewsr3: Also, it might be better to cut that 1,2,3 in a few lines :) [14:28] savvas, thanks, I will ask those questions, someone from my loco also recommend asking to try it without any addons enabled [14:30] 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] savvas, good to know, I will outline the risk and encourage a backup like you mentioned before [14:41] btw, I find this amusing that we have an over 1 year old security exploit [14:42] with phisical access to some locked boxes (30% ?) you can see what was on the screen more or less === LimCore_ is now known as LimCore === thekorn is now known as thekorn1741 === thekorn1741 is now known as thekorn [16:02] LimCore, what security exposure? [16:09] meaning what bug number? === snap-l_ is now known as snap-l [18:58] any ideas what bug 318499 is about? [18:58] Launchpad bug 318499 in ubuntu "The Splash logo mistake!!" [Undecided,New] https://launchpad.net/bugs/318499 [18:59] Bug #318169 send over to wishlist please [18:59] Launchpad bug 318169 in knetworkmanager "Wireless connection always enabled on startup" [Undecided,New] https://launchpad.net/bugs/318169 [19:01] is the networkmanager thing really something for brainstorm? Sounds like a proper wishlist bug imho. [19:02] is that how it normally behaves? [19:03] i dont use kde, idk if its supposed to behave like that. [19:04] afflux, i think i see what is up with that other bug [19:04] there is discoloration [19:07] i kinda think its supposed to be like that though [19:18] Rocket2DMn: don't know that's wrong with that [19:18] with what [19:18] the kde one or the image? [19:18] Rocket2DMn: the usplash [19:19] i think its just limited by the number of pixels and the colors available [19:20] Rocket2DMn: are we talking about the same thing? What discoloration do you mean exactly? [19:21] if you zoom in on that splash image you can see where the colors vary [19:21] i think that is what the OP was getting at [19:21] Rocket2DMn: around the center of the yellow bar? [19:22] or the orange dot [19:23] yeah [19:23] that's most probably intended, I think. [19:23] 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] if more colors would be possible at all at this time of booting. [19:26] 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] I think it is about the unbalanced gap between the orange circle and the yellow part of the logo [19:27] thekorn: you mean the dot should be half a pixel raised? [19:28] afflux, its not a problem with an existing feature, so its really a wishlist item. nothing is actually broken [19:28] (kind off) [19:28] -f [19:28] as far as brainstorm goes, i agree, its not really a brainstorm type request [19:28] Rocket2DMn: wishlist of course, but I wonder if it should go to brainstorm as the comments suggest. [19:28] *comment suggests [19:29] what happend to my spelling? :( [19:29] afflux, don't know, I'm no artist, but it looks like the it could be raised a bit [19:30] but I'm not sure if this is an important bug to fix, [19:30] thekorn: I'll ask the reporter what the problem is. [20:06] 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? === erhesrhsrtb54vyh is now known as Elbrus [20:13] You can get the crash logs from /var/crash. The format is harder to read, but it should all be there [20:13] I just attach it as a separate attachment [20:15] right ive got that [20:15] but does apport-retrace still need to hapen? [20:15] I don't know. === erhesrhsrtb54vyh is now known as Elbrus [20:58] 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] urlopen timeout [20:59] OK. it seems if you wait some 2 minutes, it will work [20:59] then just hit the reload [21:00] 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] 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] yeah, misunderstood the question [21:01] there was no reload... [21:02] its just "send report" or "cancel" [21:03] maco are you under firefox or apport-gtk? [21:03] apport-gtk [21:03] network manager (the service, not the applet) crashed [21:03] ah. click on send report. Now, what happens? [21:04] then it does the loady bar for a while, then it gives an error about urlopen timeout [21:04] still under apport-gtk? [21:04] firefox doesnt open at all [21:04] dammit [21:04] sigh [21:04] i mean, i can start firefox, but apport doesnt get it open [21:04] what version of apport are you running? [21:04] 0.127 [21:05] OK. So there are 3 different errors... :-( [21:05] maco, you can still load & get a stacktrace locally [21:05] 1. cancel apport-gtk [21:06] 2. sudo apport-retrace -o an-output-file.name /var/crash/_usr_etc, etc [21:06] this will load all possible dbgsyms [21:07] and do a retrace. Then you can either look at the output file, or run apport-retrace -g on the crash [21:07] if on gdb, just do a thread apply all bt full, and load on the LP bug the output [21:07] what's the ", etc" bit? does something come after /var/crash/_usr.....0.crash? [21:08] no, just the full crash file name [21:08] ok [21:08] lots of -dbgsym packages not available... [21:10] 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] hggdh: should i be worried by all the "WARNING: package lib*-dbgsym not available" messages? [21:10] ok [21:11] normally no need to worry. If the stacktrace you get not many ??'s, it is probably good enough. [21:11] ok [21:11] i should at some point learn to read gdb output better [21:11] heh [21:11] right now i put it in the "black magic" categor [21:11] y [21:11] black magic box [21:12] 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] the -g runs gdb [21:15] should i do that too? or is the first enough [21:15] probably the first already got a backtrace [21:15] less it, and check [21:15] ok [21:15] stack trace == back trace ? [21:16] for all that matters, yes [21:16] ok [21:18] on gdb, 'bt' means 'backtrace'; a 'bt' will trace the current thread [21:18] yeah ive followed the bactrace directions before [21:19] if there are many threads (usual), then you should bt all: 'thread apply all bt' [21:19] and used it to step through my own code a few times [21:19] there you go ;-) [21:21] holy crap this includes a LARGE chunk of /var/log/messages...like 4 hours after the crash [21:25] it's the n-m hook in apport, collecting the messages that (may) shed light on the crash [21:27] hggdh: thank you [21:27] welcome [21:28] maco, I remembered one small detail... [21:28] sometimes apport-retrace will load a dbgsym for a previous version of the corresponding package, breaking dpkg [21:28] im up to date [21:29] oh, YOU may be up-to-date, but not the dbgsym repos [21:29] oh ok [21:29] all you will need to, if that happens, ir run synaptic, go to the "broken" packages, and unselect the offending dbgsyms [21:30] I proposed a patch for it, but it has not yet been looked at [21:30] is it just me or has libgnome been broken for days? [21:31] I have seen no indication of that -- what happens? [21:31] macd: do you have the ddebs repository in apt/sources.list? [21:31] yes [21:31] ah, good. [21:33] 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] 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] this is not good at all [21:34] oh goody [21:34] hggdh: do you happen to have the bug at hand? [21:34] normally i dislike apport for spamming LP, but i think thats why its disabled in final [21:34] afflux, let me check [21:36] bug 314212 [21:36] Launchpad bug 314212 in apport "Apport unable to report crash - urlopen error timed out" [Undecided,Confirmed] https://launchpad.net/bugs/314212 [21:37] charlie-tca: thanks [21:37] the bug I remembered (maybe wrong, I am old and senile) had been closed stating this was corrected on LP [21:39] hggdh: you are probably right, too. Your memory is better than mine. [21:40] charlie-tca, thank you for your vote of confidence, but what is this conversation about? ;-) [21:41] I am old and senile) had been closed stating this was corrected on LP [21:42] charlie-tca, there you go... see how my memory is good? ;-D [21:42] haha [21:42] I'm going to bed now. good night. [21:42] g'night