Package: libwayland-server0
Version: 1.22.0-2.1+b1
Hi,
Please consider upgrading libwayland-server to 1.23, or at least package
1.23 in experimental, as it is required by recent versions of wlroots.
Thanks.
> could you please confirm that your problem is fixed since version
> 2:1.11.2.901-1 in which #649420 [1] was closed.
I haven't had the X server SIGSEGV in ages (I've had just one hard lock
in the last months). Closing.
Thanks for your help,
-- Juliusz
--
To UNSUBSCRIBE, email to debian-x-re
Package: xserver-xorg-video-intel
Version: 2:2.16.0-1
X server is 1:7.6+9. Libdrm2 is 2.4.27-1. Libdrm-intel1 is 2.4.27-1.
Kernel is linux-image-3.1.0-1-amd64 version 3.1.1-1. Hardware is Sandy
Bridge integrated graphics.
[ 7320.393] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f78f72f58f6]
[ 732
Package: x11-common
Version: 1:7.5+8
Hi Julien,
At some point, Xdm stopped reading my ~/.Xresources file on both my
desktop and laptop machines (running testing). The work-around is easy
enough (I've added "xrdb < ~/.Xresources" to my window manager's init
script), but I think that the expected
>> $ dpkg -s linux-image-2.6.32-trunk-686 | grep ^Version
>> Version: 2.6.32-5
> I meant 4 as ABI version, so package 2.6.32-4-686, version >= 2.6.32-10,
> which includes:
Ah, sorry.
Juliusz
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian
reopen 579558 =
thanks
> Probably need to upgrade your kernel to 2.6.32-4-*.
$ uname -r
2.6.32-trunk-686
$ dpkg -s linux-image-2.6.32-trunk-686 | grep ^Version
Version: 2.6.32-5
Juliusz
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian
Package: xserver-xorg-video-intel
Version: 2:2.9.1-3
$ xvinfo
X-Video Extension version 2.2
screen #0
no adaptors present
$ grep -i video /var/log/Xorg.0.log
X.Org Video Driver: 6.0
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
Mod
retitle 576454 Synaptics configuration mysteriously changed
thanks
> There is no "new way", and afaik the default configuration hasn't
> changed in a long while (a year maybe?).
Then I'm at a loss.
For whatever reason, left edge scrolling and tap-drag no longer work.
Multitouch, which used to si
retitle 576454 Synaptics configuration lost by upgrade
thanks
It turns out that the driver is working, it is just that my
configuration (that sets up things like multitouch and click-drag) in
the xorg.conf file is being ignored.
Something is wrong about that, but I'm not quite sure what. Please
> The device is being added once (here) from xorg.conf, and then another
> time from the hotplugging code (which fails, because the device is
> already grabbed).
I am quite positive that the touchpad behaves as when it is driven by an
ordinary PS/2 mouse driver. None of tap-drag, multitouch or sc
Package: xserver-xorg-input-synaptics
Version: 1.2.1-1
Severity: normal
C'est intenable, ton truc.
-- Package-specific info:
/var/lib/x11/X.roster does not exist.
/var/lib/x11/X.md5sum does not exist.
X server symlink status:
lrwxrwxrwx 1 root root 13 Jun 4 2006 /etc/X11/X -> /usr/bin/Xorg
-
Package: xserver-xorg-input-synaptics
Version: 1.2.1-1
After upgrading, my Synaptics touchpad is no longer recognised:
(II) config/udev: Adding input device "SynPS/2 Synaptics TouchPad"
(/dev/input/event7)
(II) Synaptics touchpad driver version 1.2.1
(**) Option "Device" "/dev/input/event7
Package: xserver-xorg
Version: 1:7.3+10
Forwarding this to bugs@, just to make sure Julien is sufficiently
annoyed to do something about it.
Juliusz
--- Begin Message ---
Dear all,
After my recent adventures with Radeon, XAA and EXA, I've come to the
concl
Tags: upstream, wontfix
Hi. (I'm the original author of the FreeType backend in X.Org.)
This bug was introduced in revision 1.32 of ftfuncs.c[1] in XFree86
CVS[2] on 19 October 2003 by David Dawes <[EMAIL PROTECTED]>. This
commit was made against my opinion (as expressed on the internal
XFree86
Package: xfonts-encodings
Version: 1:1.0.2-1
Hi David, hi Julien,
In /usr/share/doc/xfonts-encodings/copyright, I read,
> Copyright 2002-2004 Red Hat Inc., Durham, North Carolina.
> All Rights Reserved.
Considering that I personally generated most of the files contained in
this package, and tha
Yes, that's the patch that I applied. David, let me know if you want
me to tag luit upstream.
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I've just fixed this upstream.
Juliusz
pgpdsFjNFquic.pgp
Description: PGP signature
I believe that this is the same bug as #291137.
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
merely unusual font is loaded,
and provides no functionality that our users will need. I hereby
volunteer to ruthlessly flame anyone who complains about the change.
With my most sincere regards,
Juliusz Chroboczek
pgpLpsp7q99Pk.pgp
Description: PGP signature
Package: xserver-xorg
Version: 6.9.0.dfsg.1-6
Severity: wishlist
Hi Branden, or whoever is maintaining the X server nowadays.
On my systems at least, X.Org is loading the "type1" font backend. I
have no idea whether this is the default behaviour, or an artefact of
my configuration -- if the latt
Hi, Branden, how's tricks?
> > > This issue should hopefully be fixed upstream in 4.3.0.
> > Is this really the case? If so, this scary bug should be closed.
In the default configuration, it should no longer apply to Type 1
fonts. However, it still applies to CIDFonts.
CIDFonts are history.
TD> ...and since it has to be set to a particular value (and because there's
TD> no good method to determine what it was - or isn't there?) you suggest
TD> that the application not use G1 for anything else.
Exactly. (There is none.)
I suggest that the application use smacs=\E(0, which sets G0 to
TD> I read what I could find on EUC, but don't see where it uses codes 0-31 for
TD> printable text.
It doesn't use codes 0-31.
EUC is an application of of ISO 2022 that uses G1, which is one of the
registers of the ISO 2022 virtual machine. For example, in EUC-CN, G1
points at GB-2312.
ESC ) 0
Hi Thomas!
>> The latest xterm seems to be able to display CJK characters.
>> However, I found that after running a slang / ncurses application,
>> the characters become garbled again.
Geoffrey: as a workaround, you may do
TERM=kterm; export TERM
> So, if that's true, does that mean it is lui
MS> Two (2) questions remain:
I grant you two (2) questions.
MS> [1] Why am I confused by xrdb?
Everyone is confused by xrdb.
MS> Why did it give me some _other_ font?
No idea. I'm confused by xrdb.
MS> [2] Once I am in an xterm window, *HOW* can I query that window for its
MS> current c
MS> OK, I give up! I use 9x15 almost everywhere. Please, suggest
MS> alternatives that meet this criterion . . .
9x15 is an alias for
-misc-fixed-medium-r-normal--15-*-75-75-c-*-iso8859-1
You should use
-misc-fixed-medium-r-normal--15-*-75-75-c-*-iso10646-1
instead.
Yes, having to spec
> These are probably bugs in the manpages: They use '-' where '\-'
> should be used.
It's a little more complicated than that.
Both Unicode and roff distinguish between the hyphen (- in roff,
U+002D) and the minus sign (\- in roff, U+2010).
If used with the right font, XTerm will display both.
> Is somebody could explain me what would I have to change in debian (rules?
> or elsewhere) to try to rebuild this Xhp server under linux?
Please note that Xhp is not supported by XFree86, and most probably
doesn't build.
Try adding a file xc/config/cf/host.def with the following line:
#defin
> Is somebody could explain me what would I have to change in debian (rules?
> or elsewhere) to try to rebuild this Xhp server under linux?
Please note that Xhp is not supported by XFree86, and most probably
doesn't build.
Try adding a file xc/config/cf/host.def with the following line:
#defin
Could you please try out version 1.1.27 of the Savage driver
http://www.probo.com/timr/savage40.html
and see if the problem goes away?
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PR
That's expected behaviour: Xft doesn't grok Speedo fonts (an obsolete
format).
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Could you please try out version 1.1.27 of the Savage driver
http://www.probo.com/timr/savage40.html
and see if the problem goes away?
Juliusz
That's expected behaviour: Xft doesn't grok Speedo fonts (an obsolete
format).
Juliusz
Fabio,
Just to let you know that 4.3.0 is out, and this is the right time to
take your patches upstream. If you're still interested in pursuing
the matter, please go to www.xfree86.org, subscribe to the devel
mailing list, and start the discussion.
I am looking forwards to seeing you there.
Fabio,
Just to let you know that 4.3.0 is out, and this is the right time to
take your patches upstream. If you're still interested in pursuing
the matter, please go to www.xfree86.org, subscribe to the devel
mailing list, and start the discussion.
I am looking forwards to seeing you there.
Would you be so kind as to write to the driver's authors and ask them
why they don't get their driver included in the upstream XFree86 tree.
Thanks,
Juliusz
The current Type 1 rasteriser is being obsoleted. In the default 4.3
installation, it will only be used for CIDFonts, and I hope to kill it
completely in a future release.
Life is short, and I do not intend to fix this bug myself, although
I'll be glad to accept a patch that does.
Would you be so kind as to write to the driver's authors and ask them
why they don't get their driver included in the upstream XFree86 tree.
Thanks,
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
The current Type 1 rasteriser is being obsoleted. In the default 4.3
installation, it will only be used for CIDFonts, and I hope to kill it
completely in a future release.
Life is short, and I do not intend to fix this bug myself, although
I'll be glad to accept a patch that does.
> PS I was not able to search too much on INRIA and on the university of
> Paris (as suggested) for the simple reason that 99% of the pages I found
> are in french.
Eh?
Typing ``X11R6 IPv6 INRIA'' in Google gives the following English page
as the third hit:
http://www.ipv6.org/impl/inria.html
> PS I was not able to search too much on INRIA and on the university of
> Paris (as suggested) for the simple reason that 99% of the pages I found
> are in french.
Eh?
Typing ``X11R6 IPv6 INRIA'' in Google gives the following English page
as the third hit:
http://www.ipv6.org/impl/inria.html
FMDN> I was not aware of other implementations when i started merging and
FMDN> working on this one (talking about Sun and INRIA). Are they publically
FMDN> available?? any URL??
Fabio,
The INRIA implementation is but a vague memory. I don't think that
Sun's implementation is available to the ge
One Sun engineer claimed on the XFree86 lists that the IPv6
implementation required a minor protocol change. Of course, this may
have been mere bragging (of the ``look, we've done some really hard
work''), or else an indication of how they like to do complicated
things when it's not needed. (Yes,
FMDN> I was not aware of other implementations when i started merging and
FMDN> working on this one (talking about Sun and INRIA). Are they publically
FMDN> available?? any URL??
Fabio,
The INRIA implementation is but a vague memory. I don't think that
Sun's implementation is available to the ge
One Sun engineer claimed on the XFree86 lists that the IPv6
implementation required a minor protocol change. Of course, this may
have been mere bragging (of the ``look, we've done some really hard
work''), or else an indication of how they like to do complicated
things when it's not needed. (Yes,
This is fixed in upstream CVS. It is due to the 4.2 version of the
Savage driver mis-detecting the video memory size.
A workaround is to set the size in your XF86Config-4 explicitly using
the VideoRam keyword. A proper solution is to remove the code that
(mistakenly) probes for the memory size u
This is fixed in upstream CVS. It is due to the 4.2 version of the
Savage driver mis-detecting the video memory size.
A workaround is to set the size in your XF86Config-4 explicitly using
the VideoRam keyword. A proper solution is to remove the code that
(mistakenly) probes for the memory size u
>> Well, I don't necessarily think that's the case, since my
>> understanding is that the "@euro" modifier refers to the
>> characteristics of the locale setting as opposed to the details of
>> economic zones.
I suggest that we postpone this debate until Her Gracious Majesty's
Government convinces
PK> No, I do not have any encodings.dir files. What I run is:
PK> ttmkfdir > fonts.scale
PK> mkfontdir
$ mkfontdir -e /usr/X11R6/lib/X11/fonts/encodings \
-e /usr/X11R6/lib/X11/fonts/encodings/large
Other useful commands include ``less fonts.README'' and ``man mkfontdir''.
>> Well, I don't necessarily think that's the case, since my
>> understanding is that the "@euro" modifier refers to the
>> characteristics of the locale setting as opposed to the details of
>> economic zones.
I suggest that we postpone this debate until Her Gracious Majesty's
Government convinces
PK> No, I do not have any encodings.dir files. What I run is:
PK> ttmkfdir > fonts.scale
PK> mkfontdir
$ mkfontdir -e /usr/X11R6/lib/X11/fonts/encodings \
-e /usr/X11R6/lib/X11/fonts/encodings/large
Other useful commands include ``less fonts.README'' and ``man mkfontdir''.
>> Does playing with the pci_burst and pci_retry options change anything?
>> (See the s3virge manual page.)
DE> I wish it did. I spent a couple of days with the s3virge manpage trying
DE> every possible combinition of variables I could think of, with no luck.
I suspect you may have a hardware is
Please note that the en_GB.ISO8859-15 locale *is* supported by the X
server (at least in current CVS). It uses the ISO 8859-15 character
encoding, which makes the Euro sign available. However, it differs
from an [EMAIL PROTECTED]'' variant because it uses the Pound, not the Euro, as
the currency
Note by the way that two default modelines for 1400x1050 have been
included in XFree86 4.2.0 (after Debian 3.0). The list of default X
server modelines is in hw/xfree86/common/xf86DefModes.c, and
configuration tools could probably link against this file.
Ju
> The xlsfonts man page doesn't explain "pattern" good enough.
$ man xlfonts
...
Xlsfonts lists the fonts that match the given pattern. The wildcard
character "*" may be used to match any sequence of characters (includ-
ing none), and "?" to match any single character
Font installation is documented in the README.fonts file (under
xfree86-common). This file does not metion xfs as I (the author of
the document) believe that xfs is a Bad Idea and do not wish to
promote its use.
However, font installation using xfs is documented in the xfs(1)
manual page. With s
No reply...
Could I please ask you to tell me whether you can reproduce the
problem without Tk, i.e. what happens if you do
xfd -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1'
If the problem is not reproducible with xfd, it's a Tk bug, not an X
bug. If it is reproducible wit
Does playing with the pci_burst and pci_retry options change anything?
(See the s3virge manual page.)
Juliusz
This issue should hopefully be fixed upstream in 4.3.0. There will be
no fix for 4.2.
Juliusz
Sorry to ask the obvious: you do ``Load "glx"'' in your XF86Config-4?
Juliusz
Je vous suggère d'en
envoyer le contenu sur la liste debian-users. Voyez sur
www.debian.org pour la liste des listes de discussion.
Attention : les listes Debian sont de langue anglaise. Si vous
envoyez un message en français, vous risquez de vous faire mal voir.
Salutations,
Juliusz Chroboczek
Does the directory with the fonts contain a proper encodings.dir file?
In other words, have you run mkfontdir with the proper -e option?
I am fairly positive that ISO 8859-13 does work correctly. However,
it is not a built-in encoding, and the server relies on an
encodings.dir file to locate its
>> Does playing with the pci_burst and pci_retry options change anything?
>> (See the s3virge manual page.)
DE> I wish it did. I spent a couple of days with the s3virge manpage trying
DE> every possible combinition of variables I could think of, with no luck.
I suspect you may have a hardware is
Please note that the en_GB.ISO8859-15 locale *is* supported by the X
server (at least in current CVS). It uses the ISO 8859-15 character
encoding, which makes the Euro sign available. However, it differs
from an ``@euro'' variant because it uses the Pound, not the Euro, as
the currency symbol.
I
Note by the way that two default modelines for 1400x1050 have been
included in XFree86 4.2.0 (after Debian 3.0). The list of default X
server modelines is in hw/xfree86/common/xf86DefModes.c, and
configuration tools could probably link against this file.
Ju
> The xlsfonts man page doesn't explain "pattern" good enough.
$ man xlfonts
...
Xlsfonts lists the fonts that match the given pattern. The wildcard
character "*" may be used to match any sequence of characters (includ-
ing none), and "?" to match any single character
Font installation is documented in the README.fonts file (under
xfree86-common). This file does not metion xfs as I (the author of
the document) believe that xfs is a Bad Idea and do not wish to
promote its use.
However, font installation using xfs is documented in the xfs(1)
manual page. With s
No reply...
Could I please ask you to tell me whether you can reproduce the
problem without Tk, i.e. what happens if you do
xfd -fn '-adobe-helvetica-medium-r-normal--12-*-75-75-p-*-iso8859-1'
If the problem is not reproducible with xfd, it's a Tk bug, not an X
bug. If it is reproducible wit
Does playing with the pci_burst and pci_retry options change anything?
(See the s3virge manual page.)
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
This issue should hopefully be fixed upstream in 4.3.0. There will be
no fix for 4.2.
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sorry to ask the obvious: you do ``Load "glx"'' in your XF86Config-4?
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Je vous suggère d'en
envoyer le contenu sur la liste debian-users. Voyez sur
www.debian.org pour la liste des listes de discussion.
Attention : les listes Debian sont de langue anglaise. Si vous
envoyez un message en français, vous risquez de vous faire mal voir.
Salutations,
Does the directory with the fonts contain a proper encodings.dir file?
In other words, have you run mkfontdir with the proper -e option?
I am fairly positive that ISO 8859-13 does work correctly. However,
it is not a built-in encoding, and the server relies on an
encodings.dir file to locate its
JL> vesa one is vesa 1, i.e. vbe, afaik, so it works in lots of places
JL> where vesafb doesn't.
Just to be pedantic: Xvesa does work on anything that has either VBE
1.2 or later, or a VGA BIOS, or an EGA BIOS. (It has been tested on a
plain EGA chipset by a friendly sysadmin from Sverdlovsk.)
X
JL> vesa one is vesa 1, i.e. vbe, afaik, so it works in lots of places
JL> where vesafb doesn't.
Just to be pedantic: Xvesa does work on anything that has either VBE
1.2 or later, or a VGA BIOS, or an EGA BIOS. (It has been tested on a
plain EGA chipset by a friendly sysadmin from Sverdlovsk.)
TM> X server crashes when modules freetype and xtt are both enabled. Here is
TM> Duplicate symbol TT_FreeType_Version in
[...]
It doesn't crash, it fails gracefully.
The fact that both modules cannot be used simultaneously is
documented. If any configuration tools produce XF86Config files with
TM> X server crashes when modules freetype and xtt are both enabled. Here is
TM> Duplicate symbol TT_FreeType_Version in
[...]
It doesn't crash, it fails gracefully.
The fact that both modules cannot be used simultaneously is
documented. If any configuration tools produce XF86Config files wit
JL> I don't know XDirectFB, but the kdrive servers are probably
JL> better served being compiled against a uclibc (yes they compile
JL> cleanly against the newer uclibcs). Unless the idea is to use
JL> Xvesa as a failsafe X server for intel. Else what's the point?
I do see Xvesa as a failsafe alte
JL> I don't know XDirectFB, but the kdrive servers are probably
JL> better served being compiled against a uclibc (yes they compile
JL> cleanly against the newer uclibcs). Unless the idea is to use
JL> Xvesa as a failsafe X server for intel. Else what's the point?
I do see Xvesa as a failsafe alt
XB> I'm trying to use some bitmapped fonts with Xft, but they're all
XB> packaged as .bdf.gz or .pcf.gz, and freetype can't read that.
Correct.
XB> I could manually gunzip all my font directories, but then next upgrade
XB> will mess it up.
Correct. There are three people in the world who unders
XB> I'm trying to use some bitmapped fonts with Xft, but they're all
XB> packaged as .bdf.gz or .pcf.gz, and freetype can't read that.
Correct.
XB> I could manually gunzip all my font directories, but then next upgrade
XB> will mess it up.
Correct. There are three people in the world who under
> x = curent_destination_byte;
> z = x & 0111b
> x = z | y
> You have to do this to do every single pixel write with 15bit color. With
> 16bit color all the bytes are even so it's just
> dest = val;
No. Depth 15 is stored in the framebuffer at 16 bpp; i.e. there's one
pixel per 16 bits, wit
> Why not use depth 16?
Because pink is not my favourite shade of gray.
Juliusz
http://www.pps.jussieu.fr/~jch/software/files/analyse-x.pl
Interesting.
We'd really need to have xscope traces in order to find out what's
going on.
Could somebody be so kind as to tell the originator how to generate
xscope traces from the two runs of his Tcl/Tk clients? I'd do it
myself if I zeren't stuck zith this AZERTY keyboqrd.
>> FreeType module? Anti-aliased fonts?
There is no relationship whatsoever between the FreeType module and
AA. AA is done for client-side fonts by Keith's Xft library. Xft
doesn't require the FreeType module.
(It is true that older versions of the Freetype module did implement a
hackish form
> /me yet again wonders why he bothers to write documentation that no
> one reads.
FreeType module? Anti-aliased fonts?
Juliusz
> I'm wondering if XFree86 considers it worth the trouble.
I have no doubt that a tested, cross-platform patch will be accepted.
Non-portable patches are sometimes considered more trouble than they
are worth.
(You should at least consider Linux, the three Free BSDs, Solaris,
Lynx and OS X, on all
>>> Does anyone know if there has ever been attempt to have Bigelow and
>>> Holmes licensing changed so that it fits dfsg?
>> Yes, both by me and Branden.
> What was the result of your attempts? Did they reject the idea?
I'm CC-ing this to Charles Bigelow in case I misrepresent something.
As us
> I wonder if Bigelow and Holmes would allow modification of their fonts
> with a clause that the name must be changed.
I doubt it. If you do contact them on this matter, please make it
very clear that you are not speaking for XFree86, who are happy with
the current license. (This is the officia
> for inexpensive hardware. However, as soon as X is loaded and a window
> is perturbed, the sound card goes insane.
> Now, if I remember my history, PCI video card manufacturers discovered
> at some point that they could lengthen the little bars produced by
> WinBench by a few percent if they wro
>> * Modify this extension's build procedure, on Alpha, to not use
>> optimization. We certainly don't want to compile the entire X server
>> without optimization.
Branden, I suggest you take this approach. Unfortunately, this will
significantly slow down the speed of the rasteriser.
I guess
> The alternative to the compose mechanism -- using the input method
> mechanism -- is just too nasty to consider. End of offtopic.)
Is that the same as the 'altgr' key?
No. It's a mechansim that allows a separate process to do dictionary
lookups for East-Asian input. The protocol i
NV> I recently switched to the en_US.UTF-8 locale. In
NV> /usr/X11R6/lib/X11/locale, I see the compose maps for the various
NV> character sets, however there isnt one for en_US.UTF-8. As far as I can
NV> tell, this locale uses the compose map from iso8859-1 (though I couldnt
NV> figure out how/wh
NV> I recently switched to the en_US.UTF-8 locale. In
NV> /usr/X11R6/lib/X11/locale, I see the compose maps for the various
NV> character sets, however there isnt one for en_US.UTF-8. As far as I can
NV> tell, this locale uses the compose map from iso8859-1 (though I couldnt
NV> figure out how/w
RN> However, X still refused to start on account of a duplicate symbol for
RN> freetype in /usr/X11R6/lib/modules/fonts/libxtt.a. Removing xtt from
RN> the configuration "fixed" the problem.
That's okay.
X-TT and FreeType have always been mutually exclusive. They should
not be loaded simultaneou
RN> However, X still refused to start on account of a duplicate symbol for
RN> freetype in /usr/X11R6/lib/modules/fonts/libxtt.a. Removing xtt from
RN> the configuration "fixed" the problem.
That's okay.
X-TT and FreeType have always been mutually exclusive. They should
not be loaded simultaneo
But, according to the log, they don't exist. It's been suggested that
modules "pex5" and "xie" are deprecated (which could explain their not
being able to be loaded ;-).
They are no longer supported and no longer built by default. No major
application uses these extensions.
Is this
> the reason I use Alt to bind window-manager commands is that Meta is
> used by Emacs...
The Key Formerly Known As Meta (``Windows'') is now called Super. You
should feel free to bind S-x in your window manager.
> Ew. Well, I guess that if the X people don't care, and Branden
> doesn't care, I
> the reason I use Alt to bind window-manager commands is that Meta is
> used by Emacs...
The Key Formerly Known As Meta (``Windows'') is now called Super. You
should feel free to bind S-x in your window manager.
> Ew. Well, I guess that if the X people don't care, and Branden
> doesn't care,
1 - 100 of 223 matches
Mail list logo
