On Mon, Mar 9, 2009 at 6:02 AM, Julien Cristau wrote:
> Sounds like RAW mode isn't being set on the console... Probably because
> you're not using the kbd driver, and disabling AllowEmptyInput. This
> isn't really a supported configuration.
I can confirm that reenabling AllowEmptyInput solves
On Mon, Mar 9, 2009 at 4:31 AM, Julien Cristau wrote:
> Your config disables AllowEmptyInput but leaves AutoAddDevices and
> AutoEnableDevices on, so you get both kbd and evdev devices for your
> keyboard. Either leave AllowEmptyInput enabled, or disable
> AutoAddDevices. If you still have this
FWIW, I also had this problem with 2.3.2-2+lenny1 (and not with
2.3.2-2), and the version from
http://people.debian.org/~jcristau/493096/ did fix it for me. I also
got a backtrace of where X was hanging when it was too busy to bring
my windows up:
0xb7b13cfa in i830_crt_detect (output=0x8aaac00
On Fri, Jun 20, 2008 at 1:09 AM, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Still the same problem with intel 2.3.2 ? What if you enable XAA instead
> of EXA ?
I actually haven't seen this crash again since I filed this bug report.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Package: xserver-xorg-video-intel
Version: 2:2.2.99.901-1
Severity: normal
Today I got a crash while doing not much of anything (just browsing
the web in Iceweasel); my screen became unresponsive, and on sshing in
from another machine I found "Error in I830WaitLpRing()" in the log and
no running
reassign 430498 xinit
thanks
On investigation in the upstream bug, we've discovered that this bug
is actually a bug in xinit (xinit sends SIGKILL to the X server if it
doesn't shut down fast enough, which can happen on my system just from
heavy I/O load, and the X server obviously can't restore
This is less of an issue for me now, since upstream has started
fixing my bugs instead of just claiming my hardware is broken or
assigning them all to Keith Packard :-). I'm now using the new intel
driver (locally compiled from a git snapshot with some recent fixes)
and it's working acceptably f
This bug is fixed in the upstream git master as of 2008-2-25. I'll
test it in the next unstable version that comes out and close the
Debian bug if appropriate.
Thanks!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: xserver-xorg-video-intel
Version: 2:2.2.0-1
Severity: wishlist
The new xserver-xorg-video-intel driver has never worked properly for
me; there are several showstoppers (which I've been dutifully filing
into xorg's bugzilla), and so I've been using a kind of backport of
version 1.7.2-4 o
On 11/23/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Thanks a lot. You should probably attach your config and log with the
> intel driver 2.2.0 and maybe also a photo of the problem.
Yes, that is a good idea -- I'm away from home on holiday right now,
but I'll look into it when I get back. Qu
forwarded 432157 http://bugs.freedesktop.org/show_bug.cgi?id=13316
thanks
I've forwarded this to xorg's bugzilla.
Cheers.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
forwarded 430498 https://bugs.freedesktop.org/show_bug.cgi?id=12393
thanks
I've forwarded this bug to xorg's bugzilla.
Thanks!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
forwarded 432160 https://bugs.freedesktop.org/show_bug.cgi?id=12391
thanks
I've forwarded this bug to xorg's bugzilla.
Cheers.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 8/31/07, Andrew Moise <[EMAIL PROTECTED]> wrote:
> I'll let you know if I learn anything from trying the git version.
I'm sorry to report that I also see this crash in the git source I
pulled down today (7fd9a98178cdebda4213796fdc452a8a265a1197).
Thanks.
--
To UN
On 8/18/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
> You could try adding
> Option "AccelMethod" "EXA"
> to the Device section of your xorg.conf, it's supposed to work bette
> than the default XAA.
>
> Also, you might want to try with latest upstream git snapshot of the
> driver. It seems to
reopen 430498
found 430498 2:2.1.1-1
thanks
On 8/19/07, Andrew Moise <[EMAIL PROTECTED]> wrote:
> I see that there's a new version available now. I'll try that. I'm
> also planning to try a git snapshot soon (to investigate #432157); the
> bug seems to be inter
On 8/8/07, Andrew Moise <[EMAIL PROTECTED]> wrote:
> On 8/7/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
> > Does it still happen with xserver-xorg-video-intel 2:2.1.0-1 ?
>
> It doesn't happen in 2:2.1.0-2 at least. Thanks for the followup!
Whoops, sorry; I w
On 8/7/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
> Does it still happen with xserver-xorg-video-intel 2:2.1.0-1 ?
It doesn't happen in 2:2.1.0-2 at least. Thanks for the followup!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECT
On 6/21/07, Debian Bug Tracking System <[EMAIL PROTECTED]> wrote:
From: Brice Goglin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Thu, 21 Jun 2007 23:00:05 +0200
Subject: Bug#425181: xserver-xorg: [intel] Sometimes fails to find VGA out,
resulting in no display
Version: 2:2.0.0-2
According t
On 5/20/07, Brice Goglin <[EMAIL PROTECTED]> wrote:
You are probably experiencing the same bug than the one reported in
#420292 (I am merging these bugs). It has been reported upstream at
https://bugs.freedesktop.org/show_bug.cgi?id=10487 but it's not clear
whether it has been fixed yet.
Okay.
I still see this misbehavior with xterm 210-3.1 and
linux-image-2.6.17-2-686 2.6.17-9.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
After I talked with the driver author, he was gracious enough to fix
all the problems (including an unrelated problem of my monitor
rotation not working). The driver from git as of 2006-06-24 (which
required an X server checked out of git at that time; I don't know if
it still does) fixes all th
This does happen with newer versions of the driver; I saw it yesterday
on a driver compiled from a 2006-05-30 checkout from git.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I actually saw this again recently -- it was after upgrading the X
server again, but without an intervening X server restart. Should I try
to figure out a reproducible case (install X version foo, start X,
upgrade to version bar, start xterm), or is that an "isn't supposed to
work" case?
--
T
Package: xterm
Version: 210-3
Severity: minor
The X manpage has moved from X(1x) to X(7), so the references to it
in xterm's man page should be updated.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture:
Package: xserver-xorg-video-i810
Version: 1:1.5.1.0-2
Severity: normal
Sometimes (though not every time), when I start playing movies using
xine or mythtv, X will hang at a blank screen. The log (below)
indicates that this is because of an error in I830WaitLpRing(). This
bug is discussed in #4
On Tue, 2005-07-26 at 19:43 -0400, Thomas Dickey wrote:
> On Tue, Jul 26, 2005 at 07:12:04PM -0400, Andrew Moise wrote:
> > On Mon, 2005-07-25 at 05:20 -0400, Thomas Dickey wrote:
> > > Also - is this for the bitmap fonts, or for some TrueType font?
> >
> > I&
-xorg and noticing this problem, but maybe there were
some lingering upgrade issues...
If the problem reappears, I'll try to track it down in more detail.
It's very noticeable. :-)
> Also - is this for the bitmap fonts, or for some TrueType font?
I'm not sure what fonts xter
Package: xterm
Version: 6.8.2.dfsg.1-4
Severity: important
Every time I launch vim from within a uxterm, the xterm exits with
an X error:
[EMAIL PROTECTED] ~]$ uxterm
xterm: warning, error event received:
X Error of failed request: BadValue (integer parameter out of range for
operation)
Ma
It's not strictly unprintable characters that cause this -- I have
these fonts installed, and the characters print correctly on my system.
The line wrapping malfunction I describe still happens, though.
On Fri, 2004-09-24 at 11:02, Thomas Dickey wrote:
> My first inclination regarding a limit on cut/paste is the
> (system-dependent) caveat at the end of the xterm manpage:
Hm, that sounds plausible (it would also explain #184176, which has
been slightly annoying me for years). I never knew ptys
Package: xterm
Version: 4.3.0.dfsg.1-7
Severity: normal
If I cat right-line-wrap in an 80-character-wide xterm, then the second "z"
goes on a separate line, obviously. If I cat wrong-line-wrap, though (in a
UTF-8 locale), then the two Chinese characters at the end are not placed at the
end of t
Package: xterm
Version: 4.3.0.dfsg.1-7
Severity: normal
If I type 'seq -w 0 999' in one xterm, and cut-and-paste the output into
another xterm which is running 'cat > /dev/null', I see only the numbers 0
through 818. Cut-and-pasting 500 lines of 7 characters each, or 250 lines of
15 characters
On Wed, 2004-08-18 at 16:19, Thomas Dickey wrote:
> Perhaps you have a resource setting confusing things. I see the proper
> symbol (a lowercase "o" with a slash through it). The eightBitInput and
> metaSendsEscape resources related to "meta-X" (sending an escape character
> before the code).
On Wed, 2004-08-18 at 16:07, Thomas Dickey wrote:
> On Wed, Aug 18, 2004 at 09:10:13PM +0200, Andrew Moise wrote:
> > Package: xterm
> > Version: 4.3.0.dfsg.1-6
> > Severity: normal
>
> wrong package. This is a defect in your shell.
Yes, quite right -- aterm and my
Package: xterm
Version: 4.3.0.dfsg.1-6
Severity: normal
In the en_US.UTF-8 locale, inserting any non-ascii character into the command
line and then backspacing over it seems to backspace over bytes rather than
characters. If I insert "áõã" (either with compose keys or by cut-and-paste),
I can t
On Tue, 2004-08-17 at 16:14, Michelle Konzack wrote:
> I have the same BUG, if I use xterm instead of uxterm
> (which is an xterm called with another "class" for UTF-8)
>
> So do you have tried uxterm ?
Yes, I normally use uxterm. With uxterm I get this problem regardless
of the setting of LA
Package: xterm
Version: 4.3.0.dfsg.1-6
Severity: normal
When I run emacs inside an xterm which was started in the en_US.UTF-8 locale,
and press alt-X, emacs seems to receive a meta-8 keypress instead of a meta-X
keypress. When I start the xterm in the en_US.ISO-8859-1 locale instead, alt-X
is
38 matches
Mail list logo
