[12:17] <bkerensa> bug 805480
[12:17] <ubot4> Launchpad bug 805480 in gnome-utils (Ubuntu) "gnome-system-log crashed with SIGABRT (affects: 17) (dups: 13) (heat: 114)" [Undecided,Invalid] https://launchpad.net/bugs/805480
[16:54] <nagpaiper> After upgrading to oneric, i am having issue with screen brightness on my dell vostro
[16:54] <nagpaiper> It starts at its brightest
[16:55] <nagpaiper> and everytime the machine recovers from a dormant state, the screen goes bright again
[16:55] <nagpaiper> Is there a way to correct this
[16:59] <nagpaiper> anybody home?
[20:56] <bdmurray> jsalisbury: do you have a good understanding of kernel messages yet?
[20:57] <jsalisbury> bdmurray, you mean IPC messages?
[20:58] <bdmurray> jsalisbury: in bug 901502 in ubiquitysyslog I see the following
[20:58] <ubot4> Launchpad bug 901502 in ubiquity (Ubuntu) "I booted into Lubuntu Installation rather than running installation from the live desktop. After inputting my user info and proceeding, the installer encountered an error. (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/901502
[20:58] <bdmurray> Dec  7 20:19:58 ubuntu kernel: [   28.071489] loop1: rw=0, want=6496137616, limit=1048576
[20:58] <bdmurray> Dec  7 20:19:58 ubuntu kernel: [   28.071497] EXT2-fs (loop1): error: ext2_free_branches: Read failure, inode=98360, block=812017201
[20:59] <bdmurray> Dec  7 20:19:58 ubuntu kernel: [   28.071499] attempt to access beyond end of device
[20:59] <bdmurray> I'm not positive what that means but I don't think its good ;-)
[21:01] <jsalisbury> bdmurray, hmm,  looks like the filesystem tried to read past the end of the device.  Strage, could he have been out of diskspace?  If not, could be filesystem corruption.
[21:01] <bdmurray> jsalisbury: well its a ubiquity (installer) bug so it could be the media right?
[21:01] <bdmurray> jsalisbury: a bad cd / dvd
[21:02] <jsalisbury> bdmurray, yeah that could be, if it was reading the cd.
[21:02] <jsalisbury> bdmurray, and it probably is the cd, since rw=0 and cds are readonly
[21:04] <jsalisbury> bdmurray, loop1 refers to a loop device, which is usually a psedo device.
[21:04] <jsalisbury> bdmurray, which are used by CD ISO and floppy images
[21:06] <bdmurray> is interesting some earlier bugs have some more context
[21:06] <bdmurray> Dec 21 21:41:12 ubuntu kernel: [    9.294627] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[21:06] <bdmurray> Dec 21 21:41:12 ubuntu kernel: [   14.375581] EXT2-fs (loop1): warning: mounting unchecked fs, running e2fsck is recommended
[21:06] <bdmurray> Dec 21 21:41:12 ubuntu kernel: [   14.386433] aufs test_add:252:exe[642]: uid/gid/perm //filesystem.squashfs 0/0/0755, 0/0/0777
[21:08] <bdmurray> jsalisbury: thanks, I'm reasonably confident its bad media now.
[21:08] <jsalisbury> bdmurray, cool, that might be a good new bug pattern :-)
[21:09] <bdmurray> jsalisbury: yeah, searching my local cache of ubiquity attachments found quite a few of these ;-)
[21:09] <jsalisbury> bdmurray, I have to admit, I haven't played with bug patterns yet, but its definatily on my todo list
[21:10] <bdmurray> jsalisbury: well since you are looking it'd look like this
[21:10] <bdmurray> <pattern url="some wiki page">
[21:11] <bdmurray> <re key="Package">^ubiquity </re>
[21:11] <bdmurray> <re key="UbiquitySyslog">loop1.*Read failure</re>
[21:12] <bdmurray> <re key="UbiquitySyslog">attempt to access beyond end of device</re>

[21:13] <jsalisbury> bdmurray, nice.  And the url could point to the wiki page describing how to do md5 checks.
[21:13] <bdmurray> jsalisbury: yep
[21:14] <jsalisbury> bdmurray, good stuff.  /me just copied an pasted that example in my notes :-)
[21:14] <bdmurray> 13:13:45 - flash:[...ch/bug-attachments/ubiquity] cat 2011-12-08-bad-media.txt | uniq | sort | wc -l
[21:14] <bdmurray> 73
[21:14] <bdmurray> well, that's a somewhat significant number
[21:14] <jsalisbury> yeah
[21:15] <bdmurray> I'm glad that message isn't translated