Package: xserver-xorg-input-all
Version: 1:7.7+1
Severity: important
Since the last couple weeks, once every couple of days my keyboard suddenly
stops responding. The mouse still
works, so I use that to logout of my my window manager (LXDE) and once I am
back to gdm the keyboard works again.
S
Just happened again a couple of days ago, BTW. It is a really quite
disconcerting bug when it happens right in the middle of a video
conference.
Thanks,
Clayton
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@
On Mon, 06 Aug 2007 17:56:23 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> Clayton wrote:
> > Hi Brice,
> >
> > I am pretty sure that each time I moved from one version of xorg to
> > another (snapshot.debian.net/archive/2007/03/08/debian/ <--> testing
&g
On Thu, 09 Aug 2007 10:05:21 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> Clayton wrote:
> > Brice, I just added the "testing" version of only xserver-xorg-core
> > to the snapshot.debian.net/archive/2007/03/08/debian/ version of
> > xorg. And then booted i
Package: xserver-xorg
Version: 1:7.2-5
Severity: important
I track testing with this machine. It was working just fine with
xorg/siliconmotion module until I upgraded to the
current testing version. Now starting X results in a blank screen, and a locked
up keyboard (Ctl-Alt-F1,
Ctl-Alt-Backsp
On Wed, 13 Jun 2007 20:37:07 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> > I also tried the vesa module, and had exactly the same result:
> > blank screen, unresponsive keyboard.
>
> I wonder whether it could be related to
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424684 (vesa drive
Package: xserver-xorg
Version: 1:7.2-3
Severity: normal
Occasionally (not reliably repeatable) mplayer brings down X. This
backtrace from the attached log comes from the most recent event.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c8591]
1: /lib/libc.so.6 [0xb7dbfe28]
2: /usr/lib/xorg/
On Thu, 05 Jul 2007 11:24:14 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> Clayton wrote:
> > On Wed, 13 Jun 2007 20:37:07 +0200
> > Brice Goglin <[EMAIL PROTECTED]> wrote:
> >
> >
> >>> I also tried the vesa module, and had exactly the sam
On Mon, 6 Aug 2007 16:25:24 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> On Sun, Jul 15, 2007 at 12:20:35AM +0800, Clayton wrote:
> > No progress I am afraid, the same blank screen and locked keyboard
> > for both the vesa and silicon motion drivers using latest unstable
&
On Sun, 18 Nov 2007 17:07:07 +0100
Brice Goglin <[EMAIL PROTECTED]> wrote:
> On Sun, Oct 07, 2007 at 10:16:33AM +0800, Clayton wrote:
> > mplayer/X were kind enough to give us rapid feedback. Last night I
> > started mplayer and X was clobbered, just like before. This bug i
Package: xserver-xorg
Version: 1:7.3+2
Severity: normal
I just did a fresh install to a new hard-drive, everything up-to-date to
the latest "testing". Now when I hit Ctl-Alt-F1, instead of getting a
console, the keyboard and mouse are locked up. This happens at both the
gdm login prompt and wh
On Sun, 23 Sep 2007 11:44:33 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 22, 2007 at 08:47:29AM +0200, Brice Goglin wrote:
> > clayton wrote:
> > > Occasionally (not reliably repeatable) mplayer brings down X.
> > > This backtrace from the attach
s having the same problem, but no luck with that
one, still broken.
You can close this bug report at your leisure.
Clayton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, 04 Oct 2007 19:13:29 +0200
Brice Goglin <[EMAIL PROTECTED]> wrote:
> Clayton wrote:
> > Sorry for the delay, Brice, your request was caught up in a hardware
> > change. I now have xserver-xorg-video-ati/experimental 1:6.7.194-1
> > installed and it seems to be
Package: xserver-xorg-core
Version: 2:1.4-3
Severity: normal
Navigating to http://www.caseyresearch.com/ in mozilla/iceape
1.0.10~pre070720-0etch3+lenny1 causes xserver to crash within seconds.
In my current configuration it works every time.
I am using gnash 0.7.2-1lenny1, should flash be an
On Sat, 13 Oct 2007 09:03:07 +0200
Julien Cristau <[EMAIL PROTECTED]> wrote:
> On Sat, Oct 13, 2007 at 14:52:18 +0800, clayton wrote:
>
> > Package: xserver-xorg-core
> > Version: 2:1.4-3
> > Severity: normal
> >
> >
> > Navigating to http://www.
And now the Xorg.0.log seems to have some very interesting new details
about the failed start. See at the end of the attached log:
(II) SMI(0): Printing probed modes for output LVDS
(II) SMI(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603
607 624 -hsync +vsync (37.4 kHz) (II) SMI(0)
Package: xserver-xorg-input-kbd
Version: 1:1.3.1-1
Severity: important
On this Thinkpad x24 / KDE / running SCIM, I am frequently finding that
the keyboard seems to have gotten itself re-mapped in the middle of my
typing or using the keyboard to navigate (I frequently eschew mouse for
keyboard
This bug also screws up the mouse buttons so that mouse clicks do not
work like they used to.
This seems to have something to do with the "Scroll lock" indicator
light. (There is also a "ScrLk" key, which seems to have no effect on
this light, or anything else that I can see, while running Debian.
forced loading of the siliconmotion driver by manually adding
appropriate device and screen entries to xorg.conf, and I am back to a
blank screen and locked up keyboard, just like before.
Clayton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
It has been many moons since I have seen this behavior.
I am the originator and would not object to this bug being closed down
at this time, as having been overcome by events.
Clayton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
le --> X = borked. Hard locks are
very irritating.
Clayton
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, 28 Jan 2011 11:04:48 +0100
Cyril Brulebois wrote:
> Hi,
>
> Clayton (21/09/2009):
> > And now the Xorg.0.log seems to have some very interesting new
> > details about the failed start. See at the end of the attached log:
> >
> > (II) SMI(0): Prin
23 matches
Mail list logo
