Hi John,
John David Anglin dave.ang...@nrc.ca (05/05/2007):
Package: xserver-xorg
Version: 1:7.1.0-18
Severity: normal
After starting X using any of gdm, kdm or xstart, keyboard wasn't
accepted. […]
is that still happening in an up-to-date squeeze (or higher) system?
KiBi.
After starting X using any of gdm, kdm or xstart, keyboard wasn't
accepted. [=E2=80=A6]
is that still happening in an up-to-date squeeze (or higher) system?
No. This issue was an upgrade problem (old X version).
Dave
--
J. David Anglin
On Wed, 2007-07-11 at 14:34 -0400, John David Anglin wrote:
It could also indicate a broken framebuffer device. John, which one are
you using?
HP VisEG.
[...]
(II) FBDEV(0): hardware: stifb (video memory: 2048kB)
(II) FBDEV(0): checking modes against framebuffer device...
(II)
On Tue, 2007-07-10 at 20:56 +0200, Brice Goglin wrote:
John David Anglin wrote:
Which xserver-xorg-video-fbdev and xserver-xorg-core is this?
ii xserver-xorg-v 1:0.3.1-1 X.Org X server -- fbdev display driver
ii xserver-xorg-c 2:1.3.0.0.dfsg X.Org X server -- core server
It could also indicate a broken framebuffer device. John, which one are
you using?
HP VisEG.
Dave
--
J. David Anglin [EMAIL PROTECTED]
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
X Window System Version 1.3.0
Release Date:
John David Anglin wrote:
Could you try with the latest xserver-xorg-core 1.3 currently in
unstable and latest drivers and report back whether this bug still occurs?
I'm not sure when I can get to this. Too many problems with recent update
to glibc version 2.5 in testing and gcc issues
Did you have a chance to test this?
The software updates are installed and the links that I installed
are removed. However, I haven't actually had a chance to look at
the display. Normally, I access the machine remotely.
I think there's a new problem:
...
(EE) FBDEV(0): FBIOPUT_VSCREENINFO
John David Anglin wrote:
Did you have a chance to test this?
The software updates are installed and the links that I installed
are removed. However, I haven't actually had a chance to look at
the display. Normally, I access the machine remotely.
I think there's a new problem:
...
Which xserver-xorg-video-fbdev and xserver-xorg-core is this?
ii xserver-xorg-v 1:0.3.1-1 X.Org X server -- fbdev display driver
ii xserver-xorg-c 2:1.3.0.0.dfsg X.Org X server -- core server
Dave
--
J. David Anglin [EMAIL PROTECTED]
National Research
John David Anglin wrote:
Which xserver-xorg-video-fbdev and xserver-xorg-core is this?
ii xserver-xorg-v 1:0.3.1-1 X.Org X server -- fbdev display driver
ii xserver-xorg-c 2:1.3.0.0.dfsg X.Org X server -- core server
The version of xserver-xorg-core is truncated :) Last one
John David Anglin wrote:
Which xserver-xorg-video-fbdev and xserver-xorg-core is this?
ii xserver-xorg-v 1:0.3.1-1 X.Org X server -- fbdev display driver
ii xserver-xorg-c 2:1.3.0.0.dfsg X.Org X server -- core server
The version of xserver-xorg-core is truncated :)
Could you try with the latest xserver-xorg-core 1.3 currently in
unstable and latest drivers and report back whether this bug still occurs?
I'm not sure when I can get to this. Too many problems with recent update
to glibc version 2.5 in testing and gcc issues (and my real world job).
Dave
--
Hi,
Could you try with the latest xserver-xorg-core 1.3 currently in
unstable and latest drivers and report back whether this bug still occurs?
thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: xserver-xorg
Version: 1:7.1.0-18
Severity: normal
After starting X using any of gdm, kdm or xstart, keyboard wasn't
accepted. There were no errors in Xorg.0.log. However, I see stuff
like the following in kdm.log:
(==) Log file: /var/log/Xorg.0.log, Time: Sat May 5 14:43:39 2007
14 matches
Mail list logo
