Date: 07 Feb 2003 02:53:53 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Mark Edwards <mark@antsclimbtree.com> Cc: questions@freebsd.org Subject: Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues Message-ID: <1044604432.6865.32.camel@shumai.marcuscom.com> In-Reply-To: <9F83D0A4-3A6F-11D7-9E22-000A278CC960@antsclimbtree.com> References: <9F83D0A4-3A6F-11D7-9E22-000A278CC960@antsclimbtree.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-0oJd/flYAy2sAKq6P6Eo Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2003-02-07 at 02:41, Mark Edwards wrote: > On Thursday, February 6, 2003, at 09:14 AM, Joe Marcus Clarke wrote: >=20 > > On Thu, 2003-02-06 at 12:07, Mark Edwards wrote: > >> 1) Is there any way to run xscreensaver with gdm2? With gdm, there > >> was a Background option in the config tool, but that's gone. > > > > What do you mean? Run xscreensaver while gdm itself is running (i.e.=20 > > no > > user logged in)? I've never done this, but there are quite a few > > configuration options in the /usr/X11R6/etc/gdm/gdm.conf that are not=20 > > in > > the GUI tool. >=20 > I figured this out. gdm2 has removed the BackgroundProgram feature=20 > from the configuration gui, but it still exists in gdm.conf. You have=20 > to set >=20 > BackgroundProgram=3D/usr/X11R6/bin/xscreensaver -nosplash >=20 > and also >=20 > RunBackgroundProgramAlways=3Dtrue >=20 > However, it doesn't seem to work with the new graphical greeter. =20 > That's what got me. Use the default greeter, and set the above=20 > settings in gdm.conf (and put an .xscreensaver in the gdm home=20 > directory) and you get xscreensaver during the login window. >=20 > >> 2) gdm2 crashes if I go to the configure tool, close, then go to the > >> configure tool again. I saw this same behavior in gdm, and it was > >> solved by starting via /etc/ttys, I think. Is there anyway to fix > >> this? Basically, once I go to the configure tool, I have to resart > >> gdm2 if I want to go to the configure tool again. > > > > I haven't seen this, but I'll take a look. >=20 > I think I spoke too quickly on this one. It appears that on second=20 > load, the gdm configure tool just takes a really long time on my=20 > machine. I mistook this for the crashing that I saw with gdm under=20 > gnome 1.4, which I originally solved by a re-install. Sorry for the=20 > false alarm! >=20 > >> 3) I followed the directions to get font anti-aliasing working, and I > >> do have GDK_USE_XFT set to 1 via .gnomerc. However, I don't see any > >> difference in anti-aliasing. There was some anti-aliasing before I > >> did anything at all, for instance in mozilla some fonts are > >> anti-aliased. But there is none in the gnome2 desktop even after the > >> new settings. What am I missing? Do I just need to add the proper > >> fonts or something? > > > > You need to make sure your XftConfig is setup correctly, and you have > > the latest freetype2. It hardly merits any work now as I'm on the=20 > > verge > > of committing GNOME 2.2 which no longer requires GDK_USE_XFT. >=20 > I've done a bit of work on this, despite your suggestion not to, and=20 > I'm still coming up short. I found a tutorial that suggests >=20 > xdpyinfo | grep -c -i render >=20 > as a test to see if XFree86 is including render support. Doing this on=20 > my system returns 0 instead 1 which the tutorial says is necessary for=20 > anti-aliasing. The tutorial says "wait until XFree86 supports Render=20 > on your graphics card." This is an old machine with an ATI Mach64 CT,=20 > so I would believe it is unsupported, however ... >=20 > What's strange is that anti-aliasing is clearly occurring in a few=20 > places for me, most notably in Mozilla. In Mozilla Mail, a message=20 > displayed in fixed-width font (Courier) is quite clearly anti-aliased,=20 > next to a variable-width font (Times) that is not. Zooming the text to=20 > 600% makes this quite evident. >=20 > I also have seen anti-aliased text in the gdm2 graphic greeter. These=20 > two examples existed even before I had added GDK_USE_XFT to my=20 > environment, or followed any of the directions in the FAQ for enabling=20 > anti-aliased text. So, there is anti-aliasing going on without any=20 > settings whatsoever, but following the directions in the FAQ, adding=20 > all my font directories to XftConfig, and setting "match edit=20 > antialias=3Dtrue;" in that file, still results in most fonts not being=20 > anti-aliased. >=20 > Any thoughts on what is wrong? What version of X is this? You really need a recent 4.2.x version with freetpye and type1 modules loaded. Joe >=20 > -- > Mark Edwards > San Francisco, CA --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-0oJd/flYAy2sAKq6P6Eo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQA+Q2YQb2iPiv4Uz4cRAjTsAKCg5ozZUM+VS1XkgvTsWu8grb/BYACfWWiG 1IbHd1HT2tJF4VYalK1bGME= =7m8Q -----END PGP SIGNATURE----- --=-0oJd/flYAy2sAKq6P6Eo-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1044604432.6865.32.camel>