On Mon, 17 Jan 2011 12:04:54 -0800, Joe Riel wrote: > On Sun, 16 Jan 2011 11:35:50 -0800 Joe Riel wrote: > >> A followup. Yesterday I installed the nvidia driver, replacing the >> (default) nouveau driver. So far the keyboard has not locked up, >> however, given its random nature, there hasn't been enough time to >> conclude that the problem is solved. If it runs for a few days with no >> lockups (I've never gone more than 2 days without one), I'll submit a >> bug report against the nouveau driver. > > So much for that...just had another lockup. Nothing in Xorg.0.log. The > following tidbit is in syslog: > > Jan 17 10:50:42 gauss kernel: [48543.711837] atkbd.c: Unknown key pressed > (translated set 2, code 0x0 on isa0060/serio0). > Jan 17 10:50:42 gauss kernel: [48543.711842] atkbd.c: Use 'setkeycodes 00 > <keycode>' to make it known. > Jan 17 11:17:01 gauss /USR/SBIN/CRON[6167]: (root) CMD (cd / && run-parts > --report /etc/cron.hourly) > > The atkbd message occured at least 15 minutes before the lockup. The > cron job occurred near the time of the lockout; I'll keep track of that > in the future. > > Not sure how to file a useful Debian bug; what package would this apply? > If I knew that ...
As keyboard is the "non-working" element here, I would fill a bug report against "x11-xkb-utils". Do not worry if this is correct/wrong assignation, if someone at BTS thinks it should be assigned to another package, he/she will take the proper steps to jump it in there :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.01.17.20.54...@gmail.com
