> I had the same problem. I guess you also made a udev rule to create
> /dev/input/mx1000. But looking at the manpage Option "Device" is
> discouraged:
>
>Option "Device" "string"
> Specifies the device note through which the device can be
> accessed.
Package: xterm
Version: 210-2
Severity: normal
As subject says:
[EMAIL PROTECTED]:~$ xterm -fa monospace
xterm: bad command line option "-fa"
[EMAIL PROTECTED]:~$ ldd /usr/bin/xterm | grep Xft
[EMAIL PROTECTED]:~$
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
This is an automatically created e-mail, please do not respond to it.
The e-mail you have replied to was an automatically created e-mail.
If you would like to reply to the original e-mail,
please review the original e-mail for an alternative e-mail address,
or visit www.kellyservices.com to conta
On Tue, Mar 21, 2006 at 10:59:45PM -0500, David Nusinow wrote:
> Hi everyone,
>
>So we're finally at the end of a very long line. At the end of this week
> I'm going to upload the whole of 7.0 to unstable. I've gotten the green
> light from the release team to do this, so I'm just going to go
Package: xserver-xorg
Version: 6.9.0.dfsg.1-5
Severity: important
After installing 6.9.0.dfsg.1-5 X crashes randomly. Usually after bootup
when gdm is started but also after running stable for hours.
It looks like it has something to do with the new evdev module:
Backtrace:
0: /usr/X11R6/bin/X(
Package: xterm
Version: 210-2
Severity: minor
Unicode characters generally render properly in my xterm, using
LANG=en_US.UTF-8, however I just noticed a glitch. When U+2218 is
rendered in some colors, it turns into the dashed box that usually
denotes a bad character. To reproduce:
- start vim i
On Sat, Mar 25, 2006 at 08:01:24PM +0100, Michael Biebl wrote:
> IIRC and please correct me if I'm wrong here, libxaw8 is not part of
> Xorg 7.0. There are 26 packages in unstable which build against libxaw8
> and would be affected by the transition to xorg 7.0. Do you intend to
> keep libxaw8 arou
Forgot to add: Please cc me, I'm not subscribed to debian-x.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Hi all,
today I upgraded to the modular X from experimental and the switch was
pretty smooth. Good work.
IIRC and please correct me if I'm wrong here, libxaw8 is not part of
Xorg 7.0. There are 26 packages in unstable which build against libxaw8
and would be affected by the transition to xorg 7.0.
I had the same problem. I guess you also made a udev rule to create
/dev/input/mx1000. But looking at the manpage Option "Device" is
discouraged:
Option "Device" "string"
Specifies the device note through which the device can be
accessed. Thiswil
Package: xserver-xorg
Version: 6.9.0.dfsg.1-5
Followup-For: Bug #341376
Latest Xorg do not see my PGX64 (ati RAGE XL) for the same reason, Xorg only
see 2 pci devices.
Here is the output of lspci:
:00:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module
Control: I/
severity 358927 minor
retitle 358927 Broken rules/xorg file crashes setxkbdmap
thx
Hi,
I pinned down the problem. During the upgrade of xserver-x11 and the
merging of local xkbd changes I messed up. (Maybe I should submit my
local changes, so I don't have to merge them any more...)
I have attach
Processing commands for [EMAIL PROTECTED]:
> severity 358927 minor
Bug#358927: setxkbd crashes Xserver badly
Severity set to `minor'.
> retitle 358927 Broken rules/xorg file crashes setxkbdmap
Bug#358927: setxkbd crashes Xserver badly
Changed Bug title.
> thx
Unknown command or malformed argumen
hi,
someone reported this bug :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302696
I asked on #debian-boot, Eddy Petrisor (eddyp) proposed:
maybe cloning the bug is a good idea, one for the X config part, and one for
the d-i (though I doubt is d-i itself that is to be blamed and not
udev/h
Package: xserver-common
Version: 6.9.0.dfsg.1-5
Followup-For: Bug #358927
Hi again,
I commented out all kbd-related options in the Xorg.conf, did not run
the gnome session (as gnome might set kbd options) and now the Xserver
survives the setxkbdmap call, but setxkbmap outputs:
Couldn't interpret
Package: xserver-common
Version: 6.9.0.dfsg.1-5
Severity: important
File: /usr/X11R6/bin/X
Hi X Strike Force,
running setxkbd with no arguments crashed the X server. Log is attached.
Running setxkbd -print does print:
xkb_keymap {
xkb_types { include "complete" };
xkb_com
16 matches
Mail list logo