[00:23] ogasawara: is this a kernel crash? http://launchpadlibrarian.net/24664263/DSC00353.JPG [00:23] bdmurray: looks like it [00:24] bdmurray: don't suppose you caught the begnning of that [00:24] I wasn't sure if it was usplash related or not [00:24] its not mine its bug 353658 [00:24] Launchpad bug 353658 in ubuntu "Ubuntu 9.04 hang in shut down" [Undecided,New] https://launchpad.net/bugs/353658 [00:26] ogasawara: is it possible to increase the VGA size on TTY to get a longer pic of a trace back on shutdown? [00:26] I'm getting one 60% of the time [00:26] it usually happens when I disable wifi (intel 4965) via NM [00:27] BUGabundo: setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz [00:28] ogasawara: Couldnt get a file descriptor referring to the console [00:30] BUGabundo: are you in a virtual terminal? [00:30] no [00:30] but I will now [00:31] done [00:31] will try to shutdown and get a traceback and a pic of it [00:32] * BUGabundo thinks this stuff should be logged [00:36] BUGabundo: boot with a vesa mode on the command line: add vga=0x317 (to get 1024x768) or vga=0x31a (to get 1280x1024) and with splash and quiet disabled. [00:37] BUGabundo: hard to log if syslogd and klogd have already shutdown. [00:37] sbeattie: haven't touch vga paramt since gutsy broke it ! lol guess I should try it again [00:38] there used to be a command to see the proper VGA size for my screen [00:38] anyone remembers what is it? [00:38] xrandr will show you what x currently thinks it is. [00:39] not that [00:39] that table of vga output to place in the kernel mode [00:39] you can do vga=ask on the kernel boot line to let it scan what modes it supports. [00:41] ahhh nice [00:41] but I wish I remember how I used to do it [00:41] it was so easy === pitoow is now known as pitoow-AFK === lacqui_ is now known as lacqui [04:21] * Lord_Ahriman is away (.) === Lord_Ahriman is now known as Lord_Ahriman|AfK === Lord_Ahriman|AfK is now known as Lord_Ahriman [06:48] good morning [07:02] good morning YoBoY [07:07] good morning [07:13] hi thekorn, good morning dholbach [07:14] good morning dholbach [07:14] hi thekorn, hi YoBoY === thekorn_ is now known as thekorn === thekorn_ is now known as thekorn === mkorn is now known as thekorn === haggisbasheruk is now known as Haggis-AAO === _neversfelde is now known as neversfelde === thekorn_ is now known as thekorn === pedro__ is now known as pedro_ === thiras_ is now known as Thiras === keta_ is now known as keta === mdz_ is now known as mdz [15:06] bdmurray: Hello, did you read my email? [15:08] bdmurray: sorry for late in responding. [15:09] Boo [15:10] bdmurray: BTW, about gutsy EOL thing, I figured out that status "won't fix" can't be set anymore if you are not in the ubuntu-bug-control team. [15:20] hi, I have been working on a bug, and have found that a patch that fixes it has been released upstream. This won't be included now until the next release cycle. What should I set the status of the bug report to? 'Fix comitted' or 'Fix released', is there a 'Fixed upstream' option hidden somewhere? [15:22] oops, should have looked at the wiki first. Looks like this should come under 'Fix released' is that correct? [15:22] "Fix Released" is when it is fixed in Ubuntu, so it won't be that [15:25] the wiki says: If a bug is fixed in the current development branch, that is good enough for Fix Released. If the bug also needs to be fixed in a stable release, use the "Target to release" link to nominate it for that release. [15:25] so the question I guess is whether the upstream patch has made it into Karmic yet or not [15:25] Karmic doesn't exist yet, so it won't have [15:28] right, so the wiki also says: For a bug task about an upstream project: the fix is in CVS/SVN/bzr or committed to some place [15:28] for 'fix committed' [15:28] lwfa: if you link the upstream bug to the ubuntu bug then the bug watch will mark the upstream bug as fix committed [15:29] and the ubuntu bug will then still be Confirmed or Triaged or whatever [15:29] unfortunately this is a bug in vim, and I don't think there's a bug tracker for vim AFAIK it seems that there are just patches sent to a mailing list [15:29] right [15:30] but you can tell it "I sent a patch to the mailing list" or something [15:30] yeah I could do that, and leave the status as 'Confirmed'? [15:30] right [15:31] and since there's no bug tracker or you might just want to link to the mailing list post in a comment or something for reference [15:32] ok, I'll do that, thanks for the help, I'm quite new to bug triaging [15:32] lwfa: the wiki is talking about the project's upstream task [15:32] it's ok, it's confusing [15:32] so basically, it's fix committed in "vim", but not in "vim (Ubuntu)" [15:32] ok [15:45] ok, so I've updated the bug report. It was initially reported under vim-latexsuite as it affects that package, so I've added vim (ubuntu) as well. Would someone mind quickly having a look at the bug and letting me know if there's anything else I need to do? Mainly just as an exercise so I can learn more about triaging? It's #42283 on launchpad. Thanks. [15:47] bug #42283 [15:47] Launchpad bug 42283 in vim-latexsuite "not possible to launch evince as dvi viewer programm out of gvim latexsuite" [Medium,Confirmed] https://launchpad.net/bugs/42283 [15:48] ooh cool [15:49] lwfa: looks pretty good to me, I set it to Triaged for you [15:50] does anything need to change in vim-latexsuite to make it work? [15:52] one of my comments described a workaround which would require the user to put a line in their .vimrc [15:52] a workaround could be coded into vim-latexsuite I suppose, but by the time that is released the fix for vim will also have been released [15:56] ok [15:56] so please mark the "vim-latexsuite (Ubuntu)" task as Invalid, as nothing needs to be done there [15:56] ok will do [15:59] well back to real work, thanks for the help [16:36] Hi there, I am going crazy, what is the way to add a remote bug watch to bug #67785 which already has one? [16:36] Launchpad bug 67785 in evolution "default timezone set to Africa/Algeria instead of matching the locale" [Low,Triaged] https://launchpad.net/bugs/67785 [16:38] If I say please? :) [16:39] I have to paste the link and close my browser! [16:40] Le-Chuck_ITA: what link do you want to add? [16:40] I want to add http://bugzilla.gnome.org/show_bug.cgi?id=381132 as an upstream bug [16:40] Gnome bug 381132 in Calendar "Evolution should use system timezone settings" [Normal,Assigned] [16:40] but I can only add "also affects project" or "also affects distribution". In both cases it's not what I want [16:42] why is that different to http://bugzilla.gnome.org/show_bug.cgi?id=364729 ? [16:42] Gnome bug 364729 in Calendar "default timezone set to Africa/Algeria instead of matching the locale" [Normal,Unconfirmed] [16:43] ah, suspected duplicate [16:44] if you click the arrow on the left of "gnome-bugs #364729" [16:44] Launchpad bug 364729 in firefox "Uploading Files to Firefox Painfully Slow" [Low,New] https://launchpad.net/bugs/364729 [16:44] then there is a URL box [16:44] and also just above it there is a radio button for selecting the bug you want anyway [16:44] just select that and click "Save Changes" [16:45] james_w: I don't know why they are different, that's why I want to link both :) [16:45] well, you can only link one [16:46] Then the other one seems better, but I commented with the link in the bug report. [16:46] On launchpad I mean. So I leave the decision to other subscribers :) [16:46] thanks james_w [16:49] thanks Le-Chuck_ITA === savvas_ is now known as savvas === lacqui_ is now known as lacqui === mnem0 is now known as mnemo === Valdemar- is now known as Valdemar === mvo__ is now known as mvo === Valdemar is now known as Vldmar [20:28] How to I report a bug with Ubuntu? [20:30] iso50: What application is the bug about? [20:33] The problem is my sound card stops working after a say in the 32bit version, but works fine in the 64bit version (8,10) [20:33] after a day* [20:35] iso50: you should review https://wiki.ubuntu.com/DebuggingSoundProblems then [20:35] bdmurray: Hello, did you see my email? sorry for late in responding... [20:35] primes2h: The bug control one? [20:35] bdmurray: about gutsy EOL thing, I saw I can't set it as "Won't fix". [20:35] bdmurray: yes [20:36] bdmurray: been though that [20:36] iso50: well, it says how to report sound bugs there [20:37] bdmurray: It can be done in ubuntu bug control team, isn't it? [20:37] primes2h: yes, it can be set by that team [20:37] bdmurray: I will as soon as I get my launchpad login info [20:38] unless 9.04 fixes it of course :-) [20:38] iso50: it'd be good test with 9.04 [20:39] just seems strange the 64 bit version has no issues yet the 32 bit version does [20:39] primes2h: I approved your e-mail but don't see it in the bug control archive now, could you resend it? [20:40] bdmurray: do you mean I have to join it again? [20:41] bdmurray: or you need my previous email? [20:43] primes2h: Didn't you send your application in this morning? [20:45] I join the team (waiting for approval) last year and today I replied to your email about joining the team. Do I have to rejoin the team or resend the email? [20:45] bdmurray: s/join/joined [20:45] primes2h: please resend the e-mail [20:48] bdmurray: done. [20:52] bdmurray: sorry for misunderstanding, I thought you couldn't find my email address in my joining request on launchpad [21:19] has anyone noticed a bug about "disappearing backgrounds" that windows that go transparent? [21:19] *and windows [21:23] savvas: Yes, it usually affects gnome-terminal for me [21:23] Unfortunately I've no idea what might be causing it, so I've not filed a bug [21:24] maxb: same here, with irssi + screen :) [21:24] I suppose I should try switching from nvidia to nv or nouveau, and seeing if the problem goes away [21:24] I found another user though, with qt4 applications and kwin that seem to be causing this a lot more [21:24] Unfortunately I can't reproduce it on demand, which makes it a real pain [21:25] same here :P [21:26] I kind of dislike quassel right now, I need my scripting! :) brb from irssi [21:28] much better :) [21:30] bdmurray: I forwarded the email at your @ubuntu.com address. This morning I just replied to ubuntu-bugcontrol@lists.launchpad.net. Have you received it now? [21:30] primes2h: yes, I have it now === beDrung is now known as bdrung === andre___ is now known as andre__ === keta is now known as luchino === luchino is now known as keta === savvas_ is now known as savvas