[00:00] <crimsun> well, i recommend you proceed with an SRU once it has received some testing in jaunty
[00:00] <daradib> ok
[00:01] <daradib> correction: according to upstream, it looks very close to version currently in 8.10 (one-lined upstream changelog in fact)
[00:02] <daradib> thanks
[02:03] <crimsun> persia: is bug 43825 still reproducible for you on a supported release or the current devel version?
[04:01] <Lupine> should this be a WishList: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/310833
[04:04] <crimsun> Lupine: yes, and i've triaged it
[04:04] <Lupine> ty
[04:38] <persia> crimsun, I could crash intrepid that way a month ago (as noted in my last comment).  Do you really need me to crash it again now?
[04:40] <crimsun> persia: not right this moment, but likely sometime in the next couple weeks. it's on my TODO.
[04:40] <persia> crimsun, On reflection, I strongly suspect that it's related to the vast number of different subsystems that look for various special keys, and expect it to be fixed with the rationalisation in jaunty: that said, I wonder if it's a semantic issue, that "exclusive" isn't blocking the events from appearing elsewhere (kernel may show things in different ways)
[04:41] <persia> (because that system behaves like that when I try to "suspend" as well)
[04:44] <persia> Hrm?  You need me to crash again in the next couple weeks?  What information are you trying to collect, beyond that intrepid suffers from this issue?
[04:46] <crimsun> persia: jaunty will be my primary focus
[04:47] <persia> OK.  When I am in "exclusive" mode, should that block access by things like acpi-utils, X, etc?
[04:48] <crimsun> it should, but X is hairy
[04:49] <persia> heh.  OK.  I'll get that system to jaunty, and crash it, and determine which key(s) cause the unresponsiveness then.
[04:50] <crimsun> i'll work at upstream's 20081014-101501 and see if something can be twiddled locally to reproduce it
[07:33] <itnet7> Bug #311059 , Can someone please mark this "Wishlist", I need to get to bed, but don't want to forget to ask
[07:33] <itnet7> Thanks!
[07:33]  * Ryan52 looks
[07:34] <sekyourbox> whas there a major kernel change in ubuntu in the past few days?  I'm getting checksum failures in Tiger...
[07:34] <Ryan52> itnet7: set status: triaged, importance: wishlist...thanks!
[07:35] <itnet7>  Ryan52: Thanks a lot!!
[07:35] <itnet7> gnight all
[07:36] <maco> sekyourbox: what version of ubuntu?
[07:38] <sekyourbox> Ubuntu 8.04.2 \n \l
[07:39] <maco> 2.6.24-23 came out in november
[07:39] <maco> sekyourbox: ^
[07:39] <sekyourbox> oh
[07:40] <maco> dpkg -l linux*
[07:40] <maco> read through that (dont paste it here)
[07:40] <maco> what do you have? linux-ubuntu-modules? linux-backports-modules?
[07:41] <sekyourbox> okay, sorry I'm slow.  2.6.24-23-generic
[07:41] <sekyourbox> actually lost my mail from tiger, trying to find exact error
[07:42] <maco> no i mean, do you have both of those?
[07:42] <maco> or just one? or neither?
[07:42] <maco> oh, linux-restricted-modules?
[07:43] <sekyourbox> linux-restrict, linux-ubuntu,
[07:44] <sekyourbox> bunch
[07:44] <sekyourbox> would you like to know the ver or something?
[07:45] <sekyourbox> no backports module
[07:45] <maco> linux-ubuntu-modules last updated dec 3
[07:47] <sekyourbox> k, thanks. I'll investigate
[07:47] <maco> linux-restricted-modules was updated on the 17th
[07:47] <maco> so a week ago
[07:47] <maco> that recent enough?
[07:48] <maco> that one's only in -proposed though
[07:48] <jmarsden> sekyourbox: If you think you installed something, maybe look at /var/log/dpkg.log too?
[07:48] <maco> if it's giving you issues, report a bug. things dont get released from -proposed if there are regression bugs filed against them
[07:51] <maco> sekyourbox: here's where you can see what changed in l-r-m: https://launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24
[07:54] <sekyourbox> Okay, i guess this is nothing new with tiger. I have read back in september, I was getting the same errors.
[07:55] <sekyourbox> looks something like this.  Installed file `/lib/modules/2.6.24-19-generic/modules.ieee13
[07:55] <sekyourbox> 94map' checksum differs from installed package 'linux-image-2.6.24-19-generic'.
[07:55] <sekyourbox> sorry for the big paste
[07:57] <jmarsden> sekyourbox: Tiger is pretty useless if you don't read its output and act on it... ;)  So, the question is, did you update your kernel in September?  if so, that is what changed these modules, most likely.
[07:58] <sekyourbox> ;)
[07:58] <sekyourbox> indeed
[07:59] <jmarsden> You may be able to look in /var/log/dpkg.log for anything with ;inux- in it around the time you first saw these messages?
[07:59] <jmarsden> anything with   linux-    that should have been.
[08:08] <sekyourbox> Thanks for the help...
[08:08] <jmarsden> No problem.
[14:32] <bddebian> Boo
[22:26] <MrKanister> Can someone please set bug #564029 to "wishlist"? Thanks in advance.
[22:26] <MrKanister> hm...wrong number... bug #311208
[22:36] <Ryan52> MrKanister: done
[22:37] <MrKanister> Ryan52: Thank you