[00:41] james_w: that person really did have a package for me [00:42] wow === Hurtz_ is now known as Hurtz === jussio1 is now known as jussi01 === asac_ is now known as asac === Igorots is now known as Igorot [12:28] hmm, is wiki.ubuntu.com slow/down for anybody else, or is it just me? [12:29] thekorn: Fails with a Squid error here. [12:30] right, same here [12:33] thekorn: Might want to tell #canonical-sysadmin - but I think that they're on holiday. [12:37] jpds, ok, it magically works again now, [12:37] thekorn: GReat. [12:37] great* === andre___ is now known as andre__ === bddebian2 is now known as bddebian === warp10_ is now known as warp10 [15:29] hi, I accidentally created a new 'project' in launchpad. https://bugs.launchpad.net/easytag [15:29] I was triaging a bug for easytag, and I looked back on it today, and saw that was created page was created. I don't know if that should have been created. [15:30] because there's also this page - https://bugs.launchpad.net/ubuntu/+source/easytag [15:31] skorasaurus, I think it is all right, you "created" this project when you linked this bug to the sf bug tracker [15:32] thekorn, okay, thank you. [15:43] i have a question: why does the status of a bug on launchpad not correspond with the upstream status ? For example, https://bugs.launchpad.net/brasero/+bug/187657 [15:43] Ubuntu bug 187657 in brasero "Uses beagle, not tracker" [Undecided,New] [15:44] because upstream and ubuntu don't always agree? it may be more important to one than another? [15:44] on the upstream (gnome's bugzilla), it is marked [unconfirmed, normal] [15:55] skorasaurus: the bug is triaged for Ubuntu, not for upstream. [15:56] Sometimes it takes a while for upstream status to catch up on launchpad [16:01] k [17:50] skorasaurus, upstream status depend on upstream work. A triaged bug on LP will still need to be confirmed upstream [17:51] these are completely separated BTSs; it may be that upstream has some other requirements before confirming, it may be a dup, etc [17:54] There are also many cases where a bug is fixed upstream, but still present in Ubuntu, or vice-versa. [17:58] BTW, 'BTS' means Bug Tracking System === jussio1 is now known as jussi01 [22:30] ok guys, im finishing triage on bug 308978 but i cant decide if its xorg or linux [22:30] Launchpad bug 308978 in xorg "Alternate keyboard layout doesn't works after a suspend" [Medium,Incomplete] https://launchpad.net/bugs/308978 [22:30] or even hal i suppose [22:34] Suspend to ram is acpi-support, isn't it? Otherwise, it is linux, since it happens after suspend [22:34] its like a nightmarish mix of all of the above [22:34] a usb device that works before suspend, but not after [22:35] well it sorta works, just doesnt recognize the language i guess [22:35] I guess I should ask if it works after the user restarts X after a resume [22:36] if it doesnt, then its not a X problem [22:38] Is it hibernate being called suspend? If so, it is linux [22:38] as in the kernel team works that [22:38] its not hibernate, its suspend to ram [22:38] (standby) [22:39] thats initially why i set the bug to xorg instead of linux [22:48] That should be acpi-support then [22:48] acpi-support is the package for suspend to ram bugs [23:09] ok thanks charlie-tca_ [23:12] err, that's not entirely correct. we need to update it. [23:13] acpi-support and pm-utils are scripts. if it's a kernel problem, the source package affected needs to be linux. [23:13] if we're failing to twiddle something in the scripts, however, yes, either acpi-support (old) and/or pm-utils (new). [23:15] (the situation becomes even more hairy when one considers hal-info) [23:16] crimsun, the thought had crossed my mind with hal [23:17] have a look at bug 308978 and let me know what package you think is appropriate [23:17] Launchpad bug 308978 in xorg "Alternate keyboard layout doesn't works after a suspend" [Medium,Incomplete] https://launchpad.net/bugs/308978 [23:17] the problem with the usb kb only appears after a suspend/resume [23:19] it's a linux bug. [23:19] nothing in acpi-support, pm-utils, or hal-info twiddles keyboard locales [because there's no such functionality there] [23:20] also, note that the reporter's laptop keyboard works fine [23:21] the symptom is only reproducible using a usb keyboard _post_-resume-from-* [23:21] the other possibility is that there's a bios issue; perhaps ask the reporter if he's running the appropriate (latest?) bios [23:25] hi.. kmail crashes ALWAYS when downloading.. how epic is that lol :/ [23:25] it's known [23:26] the one in 8.10 right? oh meh.. :/ [23:26] how to have a version that does NOT crash now then? im on 8.10 [23:27] does bug 312554 have enough information? [23:27] Launchpad bug 312554 in linux "bug: int 14 cr2... booting 2.6.28-4-generic" [Undecided,New] https://launchpad.net/bugs/312554 [23:28] LimCore: i really have no idea; most mail clients really frustrate me. i tend to use mutt or some smartphone. [23:29] btw... why we do not have an OBVIOUS field like ubuntu version and app version in the bug tracker? [23:29] like.. [ubuntu 8.10] [amd64] [kmail 4.2.1-...] etc. most can be auto-filled from user agent [23:30] LimCore: well, apport does include that. it's a question worth posing on ubuntu-devel-discuss [23:31] joumetal: the video card from lspci perhaps? Also, what version of ubuntu? [23:31] joumetal: if that's as much of the trace as you can capture, then unfortunately, yes [23:31] joumetal: it'd be better if you could grab the entire kernel ring buffer up to that point, perhaps via serial console