hope someone finds it helpful. The reorg'd code
kinda highlights how incomplete it is, there's lots of mouse models out there.
So if it looks good or almost-good to you and there's anything else I can do,
tell me and I'll be glad to do it.
Thanks,
Jim
>From 2681957a610191cb5
Package: debian-handbook
Version: 6.0+20120509
Severity: minor
---
en-US/01_the-debian-project.xml | 4 ++--
pot/01_the-debian-project.pot | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/en-US/01_the-debian-project.xml b/en-US/01_the-debian-project.xml
index e33a2ab..dd
0.5.3-5
-- no debconf information
>From 0f68b4f5ecf76b66ca4d907ee93c1f47b194819e Mon Sep 17 00:00:00 2001
From: Jim Hill
Date: Sat, 14 Jan 2012 02:12:38 -0800
Subject: [PATCH] rsyslog.conf.5 socket module example sb imuxsock
---
tools/rsyslog.conf.5 |2 +-
1 files changed, 1 ins
On Tue, Oct 11, 2011 at 1:38 AM, Sven Joachim wrote:
> Do you have binutils-gold from testing installed? Then you have hit
> #644708.
I do. Reinstalled libncurses5-dev, installed
binutils{,-gold,-dev}/unstable, it works, thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debi
Package: libncurses5-dev
Version: 5.9-2
Severity: important
Dear Maintainer,
`make menuconfig` started failing. Some digging showed all -lncurses
links failing with the subject message.
/usr/lib/x86_64-linux-gnu/libncurses.so contains
INPUT(libncurses.so.5 -ltinfo)
replacing that with
INPUT
Sorry for missing that "static" bit. I'll file a separate bug
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
/usr/x86_64-linux-gnu/libncurses.so contains
INPUT(libncurses.so.5 -ltinfo)
Replacing it with
INPUT(/lib/x86_64-linux-gnu/libncurses.so.5 -ltinfo)
made `make menuconfig` work for me.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
> unreproducible for me.
blacklisting nouveau makes it go away for me. with nouveau:
jthill@gadabout:~$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024
Package: xorg
Version: 1:7.5+8
Severity: normal
asking on irc says this reproduces on ubuntu 10.10, doesn not reproduce
on lenny or 10.04.
this does reproduce on squeeze vanilla kernel 2.6.32-5-amd64.
git bisect on git://anongit.freedesktop.org/xorg/app/xrandr says
61fc9cc04e1ac179ac5e2cc4ff86
ge. No one else has tried this yet.
Signed-off-by: Jim Hill
---
This is a second version, choosier about accepting apparently-valid
start bytes, no redundant test and more concise syslog and changelog
text.
This is my first patch, I hope I got the procedures right, apologies in
advance if I g
et it to 0 to effectively disable the patch.
Tested on AMD64, full coverage - syslog is a good argument for
replacing my mouse soon, but it's quirky not intolerable.
Signed-off-by: Jim Hill
---
Hi, this is my first patch, I hope I got the procedures right, apologies in
advance if I goofed
So much for certainty. I thought rate=40 fixed the desyncs and freezing
but it's back, no more frequent, just the same as before.
The question remains what XP is doing different that the problem
doesn't occur there. I can reboot into XP and it runs fine for much
longer than it takes the proble
For my part I'm certain of it: this is a failing mouse overloading
some part of the link. The mouse now misbehaves rarely but it's
plainly my middle mouse button sizzling briefly and everything
recovers fine, no desyncs or parity errors at all after I backed off
further to rate=40.
shirish, if
I made it stop on my squeeze beta 2.6.32 with a driver parameter change
I found on the net.and played with to strip unnecessary stuff:
This-boot workaround:
$ sudo rmmod psmouse && sudo modprobe psmouse rate=80
Every-boot workaround:
$ sudo sh
# cat >> /etc/modprobe.d/psmouse.conf
Okay, digging it seems this is a common hardware problem that Windows
solves by ignoring: https://bugzilla.kernel.org/show_bug.cgi?id=6105
Linux does too since 2.6.34:
$ git describe 6b9d363c49d22395d0cf8729c5963f83cfbb6d69
v2.6.34-rc1-31-g6b9d363
--
To UNSUBSCRIBE, email to debian-bugs-dist-
I'm getting this too. Here's the tail of my syslog. The parity messages make
me kinda suspect failing hardware.
Dec 23 08:08:42 gadabout kernel: [ 889.790156] psmouse.c: bad data from KBC -
bad parity
Dec 23 08:08:46 gadabout kernel: [ 893.077036] psmouse.c: Wheel Mouse at
isa0060/serio1/i
Subject: xfwm4-themes: Wildbush theme is xfwm4 insta-kill
Package: xfwm4-themes
Version: 4.6.0-2
Severity: important
I was bopping through the theme list with the down arrow, and xfwm4 flushed.
Login, instant flush. Try it, it's fun!
Recovery only from the command line, yay twm for Google access
Package: installation-reports
Severity: minor
First two install attempts gave me the "No common CD-ROM" message.
Returning to get debug logs, it found it just fine, of course.
reportbug from the menu popped "Please install the python-vte
package to use the GTK+ (known as 'gtk2' in reportbug) int
18 matches
Mail list logo
