[01:44] <Laibsch> Is it just me or can somebody confirm bug 334528 ?
[01:57] <crashsystems> https://bugs.edge.launchpad.net/ubuntu/+source/gimp/+bug/340297
[01:57] <crashsystems> oops
[01:57] <crashsystems> https://bugs.edge.launchpad.net/ubuntu/+source/gimp/+bug/340297
[02:15] <tw1tch> 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] <tw1tch> right.... =)
[02:26] <hggdh> tw1tch, good question. Could you please email bug-control with this, and with the URLs for the pages you found?
[02:26] <hggdh> (at this point in time, most are sleeping)
[02:26] <bdmurray> the video is wrong the wiki page is right
[02:27] <hggdh> yo bdmurray  how's life?
[02:27] <bdmurray> hggdh: alright
[02:27] <tw1tch> ok thanks guys
[06:50] <dholbach> good morning
[07:25] <thekorn> good morning bugsquad
[13:18] <harrisony> anyone have experience in linking a ubuntu bug report to a launchpad bug report
[13:18] <harrisony> another project bug repiort
[13:18] <harrisony> i tried but failed pretty badly
[13:18] <charlie-tca> What is the bug number?
[13:19] <harrisony> bug 2462 is the ubuntu bug
[13:19] <harrisony> with bug 182923 being the upstream
[13:22] <charlie-tca> 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] <persia> 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] <charlie-tca> I think the only way to link the two now is make 182923 a duplicate of 2462
[13:24] <persia> Or maybe the other way around, and add tasks to 192923, as upstream is more likely to be tracking 182923
[13:24] <charlie-tca> true, but the duplicates against 2462 would have to be moved, also
[14:00] <bddebian> Boo
[14:01] <pedro_> buuu
[14:04] <bddebian> :)
[15:20] <ball> 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] <hggdh> guess so, since -server does not install any X thingies
[15:24] <ball> hggdh: I think it happened after the Ubuntu splash screen
[15:24] <ball> Is there a key I can press to turn that off?
[15:25] <hggdh> no, but you can edit the boot parameters (and, perhaps, open a bug on usplash?)
[15:26] <ball> hggdh: how (where) do I edit boot parameters?
[15:27] <ball> I'm not yet brave enough to open a bug ;-)
[15:27] <hggdh> 2 ways: (1) when cold-booting the system; (2) editing /boot/grub/menu.lst, and then running 'sudo update-grub'
[15:28] <hggdh> ball, nobody will bite you if you open a bug
[15:28] <hggdh> and we need the feedback: if something is wrong, better correct than bypass
[15:28]  * ball nods
[15:29] <ball> I was a little surprised that Ubuntu Server even used a splash screen.
[15:29] <ball> I can see it on the desktop versions, where it's safe to assume there's a framebuffer.
[15:29] <hggdh> usplash is boot-time only, and looks nice
[15:29] <hggdh> well, even my servers run with fbs
[15:31] <ball> hggdh: Perhaps that's a safe assumption with PC servers then.
[15:32] <hggdh> 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] <ball> Ah, now when I say "framebuffer", I'm talking about the physical hardware.
[15:32] <ball> VGA card, basically.
[15:33]  * ball tries to get used to Linux terminology
[15:33] <hggdh> it still should work, with 640x480 (or whatever)
[15:33] <ball> hggdh: I'm used to servers with no graphics hardware
[15:33]  * ball <- old fart.
[15:33] <ball> ...so splash screens aren't a priority for me.
[15:33]  * hggdh <- farter old
[15:35] <ball> Should the splash screen revert to the previous display mode after doing its thing?
[15:35] <hggdh> then just disable it on the boot parms. I still like the increased real estate when using FBs (a terminal with 140x60)
[15:35] <hggdh> yes
[15:36] <ball> hggdh: I'm used to terminals that attach via a serial cable.  No splash screen there then.
[15:36] <ball> Okay, well I'll break out google and look for a way to turn that off.
[15:36] <hggdh> oh. *real* old. ;-)
[15:36] <hggdh> ball, I gave you the way
[15:37] <ball> hggdh: you told me where to do it, but I still need to look for the commands, keypresses etc.
[15:37] <hggdh> ah
[15:37] <hggdh> sorry
[15:37] <ball> I'm new to Linux (sort of)
[15:38] <hggdh> be careful when editing /boot/grub/menu.lst
[15:38] <patanachai> Hi
[15:39] <patanachai> bug #339686 > wishlist
[15:39] <ball> Does the alternate install CD also use graphics?
[15:41] <charlie-tca> patanachai: It doesn't say what version of Ubuntu they are using, but gsynaptics should take care of that
[15:41] <hggdh> I think so, do not remember.
[15:41] <charlie-tca> patanachai: It just has to be installed from Synaptic Package Manager
[15:42] <ball> Doesn't make much sense to me, but that may just be because I'm so "old school".
[15:42] <patanachai> charlie-tca: I believe gsynaptics could, but how to treat this kind of bug?
[15:43] <charlie-tca> invalid it, with a comment to use install gsynaptics from Synaptic Package Manager. Be sure and thank them for helping
[15:43] <hggdh> ball, actually it makes installing the system much more easier
[15:43] <charlie-tca> Even that is an attempt to help improve things.
[15:43] <patanachai> charlie-tca: thanks for suggestion
[15:43] <charlie-tca> You are welcome
[15:44] <ball> hggdh: Hmm... I can see that it might for those locales with a non-latin character set.
[15:45] <ball> I seem to remember a language selection thing early during the install
[15:45] <ball> Perhaps that's what its for.
[15:45] <hggdh> yes, it is quite early on the isntall
[15:46] <ball> That's a valid use of graphics.
[15:48] <ball> ...and if the things going into a graphics mode anyway, then the splash screen makes some sense.
[15:52] <ball> ...so I just need to make it work with my hardware.
[15:52] <hggdh> :-)
[15:52] <hggdh> sometimes there are issues with a particular graphics card and the installer. Yours might be one of them
[15:54]  * ball nods
[15:54] <ball> My guess is that the framebuffer (it's not using X, right?) is using a VESA mode that the video BIOS doesn't support.
[17:43] <YoBoY> hi
[19:25] <jcastro> bdmurray: wrt your blog about people using apport
[19:26] <jcastro> do we keep track of what percentage of apport bugs get fixed?
[19:26] <jcastro> like say ... crashers?
[19:28] <bdmurray> jcastro: something like http://people.ubuntu.com/~brian/complete-graphs/apport-crash/plots/apport-crash-fullyear-fixreleased.png ?
[19:29] <jcastro> sweet
[23:58] <savvas> The tag "packaging" hasn't yet been used by fonttools (Ubuntu) before. Is this a new tag?
[23:58] <savvas> is this checked for every package?