[01:44] Is it just me or can somebody confirm bug 334528 ? [01:44] Launchpad bug 334528 in virtualbox-ose "[Jaunty] virtualbox-ose-source does not find kernel source and thus fails installation" [Undecided,New] https://launchpad.net/bugs/334528 [01:57] https://bugs.edge.launchpad.net/ubuntu/+source/gimp/+bug/340297 [01:57] Error: This bug is private [01:57] oops [01:57] https://bugs.edge.launchpad.net/ubuntu/+source/gimp/+bug/340297 [01:58] Ubuntu bug 340297 in gimp "gimp-2.6 crashed with SIGSEGV in g_object_get()" [Undecided,New] [02:15] hello all, i just watched the video from http://videos.ubuntu.com/qa/assigning-packages-to-bugs.ogg on assigning packages to bugs, in it the author says that all hibernate bugs should be assigned to "acpi-support" but some documentation from https://wiki.ubuntu.com/Bugs/FindRightPackage says that most hibernate/resume bugs should probably be asigned to gnome-power-manager, pm-utils, or the linux kernel. Is this contradictory and if so which one shou [02:24] right.... =) [02:26] tw1tch, good question. Could you please email bug-control with this, and with the URLs for the pages you found? [02:26] (at this point in time, most are sleeping) [02:26] the video is wrong the wiki page is right [02:27] yo bdmurray how's life? [02:27] hggdh: alright [02:27] ok thanks guys === asac_ is now known as asac [06:50] good morning [07:25] good morning bugsquad [13:18] anyone have experience in linking a ubuntu bug report to a launchpad bug report [13:18] another project bug repiort [13:18] i tried but failed pretty badly [13:18] What is the bug number? [13:19] bug 2462 is the ubuntu bug [13:19] Launchpad bug 2462 in mail-notification "mail-notifcation hogging the CPU polling when internet connection lost" [Undecided,Confirmed] https://launchpad.net/bugs/2462 [13:19] with bug 182923 being the upstream [13:19] Launchpad bug 182923 in mail-notification "absence of network connection causes high CPU usage" [Undecided,New] https://launchpad.net/bugs/182923 [13:22] They are both reported in launchpad. The original bug report for 182923 was a non-ubuntu bugzilla. It should not have been carried into launchpad. [13:23] harrisony, I'd suggest asking on #launchpad. I believe the model is that they should be the same bug report, and that there ought be Mail Notification, Ubuntu, Fedora, and Debian tasks. [13:23] I think the only way to link the two now is make 182923 a duplicate of 2462 [13:24] Or maybe the other way around, and add tasks to 192923, as upstream is more likely to be tracking 182923 [13:24] true, but the duplicates against 2462 would have to be moved, also [14:00] Boo [14:01] buuu [14:04] :) [15:20] Would it be considered a bug if the install CD (for Ubuntu Server) did something to the display adaptor that left the screen unreadable? [15:22] guess so, since -server does not install any X thingies [15:24] hggdh: I think it happened after the Ubuntu splash screen [15:24] Is there a key I can press to turn that off? [15:25] no, but you can edit the boot parameters (and, perhaps, open a bug on usplash?) [15:26] hggdh: how (where) do I edit boot parameters? [15:27] I'm not yet brave enough to open a bug ;-) [15:27] 2 ways: (1) when cold-booting the system; (2) editing /boot/grub/menu.lst, and then running 'sudo update-grub' [15:28] ball, nobody will bite you if you open a bug [15:28] and we need the feedback: if something is wrong, better correct than bypass [15:28] * ball nods [15:29] I was a little surprised that Ubuntu Server even used a splash screen. [15:29] I can see it on the desktop versions, where it's safe to assume there's a framebuffer. [15:29] usplash is boot-time only, and looks nice [15:29] well, even my servers run with fbs [15:31] hggdh: Perhaps that's a safe assumption with PC servers then. [15:32] it might, I am not sure (I had to add the FB to the servers manually). But usplash should have worked even with a "standard" setup [15:32] Ah, now when I say "framebuffer", I'm talking about the physical hardware. [15:32] VGA card, basically. [15:33] * ball tries to get used to Linux terminology [15:33] it still should work, with 640x480 (or whatever) [15:33] hggdh: I'm used to servers with no graphics hardware [15:33] * ball <- old fart. [15:33] ...so splash screens aren't a priority for me. [15:33] * hggdh <- farter old [15:35] Should the splash screen revert to the previous display mode after doing its thing? [15:35] then just disable it on the boot parms. I still like the increased real estate when using FBs (a terminal with 140x60) [15:35] yes [15:36] hggdh: I'm used to terminals that attach via a serial cable. No splash screen there then. [15:36] Okay, well I'll break out google and look for a way to turn that off. [15:36] oh. *real* old. ;-) [15:36] ball, I gave you the way [15:37] hggdh: you told me where to do it, but I still need to look for the commands, keypresses etc. [15:37] ah [15:37] sorry [15:37] I'm new to Linux (sort of) [15:38] be careful when editing /boot/grub/menu.lst [15:38] Hi [15:39] bug #339686 > wishlist [15:39] Launchpad bug 339686 in ubuntu "Insufficient touchpad configuration tool" [Undecided,New] https://launchpad.net/bugs/339686 [15:39] Does the alternate install CD also use graphics? [15:41] patanachai: It doesn't say what version of Ubuntu they are using, but gsynaptics should take care of that [15:41] I think so, do not remember. [15:41] patanachai: It just has to be installed from Synaptic Package Manager [15:42] Doesn't make much sense to me, but that may just be because I'm so "old school". [15:42] charlie-tca: I believe gsynaptics could, but how to treat this kind of bug? [15:43] invalid it, with a comment to use install gsynaptics from Synaptic Package Manager. Be sure and thank them for helping [15:43] ball, actually it makes installing the system much more easier [15:43] Even that is an attempt to help improve things. [15:43] charlie-tca: thanks for suggestion [15:43] You are welcome [15:44] hggdh: Hmm... I can see that it might for those locales with a non-latin character set. [15:45] I seem to remember a language selection thing early during the install [15:45] Perhaps that's what its for. [15:45] yes, it is quite early on the isntall [15:46] That's a valid use of graphics. [15:48] ...and if the things going into a graphics mode anyway, then the splash screen makes some sense. [15:52] ...so I just need to make it work with my hardware. [15:52] :-) [15:52] sometimes there are issues with a particular graphics card and the installer. Yours might be one of them [15:54] * ball nods [15:54] My guess is that the framebuffer (it's not using X, right?) is using a VESA mode that the video BIOS doesn't support. === bdrung_ is now known as bdrung === bac is now known as bac_lunch === x-spec-t is now known as Spec === jorge__ is now known as jcastro [17:43] hi === bac_lunch is now known as bac === jdstrand_ is now known as jdstrand [19:25] bdmurray: wrt your blog about people using apport [19:26] do we keep track of what percentage of apport bugs get fixed? [19:26] like say ... crashers? [19:28] jcastro: something like http://people.ubuntu.com/~brian/complete-graphs/apport-crash/plots/apport-crash-fullyear-fixreleased.png ? [19:29] sweet === jorge__ is now known as jcastro === seb128_ is now known as seb128 === lacqui_ is now known as lacqui === asac_ is now known as asac [23:58] The tag "packaging" hasn't yet been used by fonttools (Ubuntu) before. Is this a new tag? [23:58] is this checked for every package?