Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Fri, 2003-02-14 at 15:10, stan wrote: > On Fri, Feb 14, 2003 at 11:58:20AM -0800, Mark Edwards wrote: > > On Friday, February 14, 2003, at 11:21 AM, stan wrote: > > > > >On Thu, Feb 13, 2003 at 11:46:47AM -0800, Mark Edwards wrote: > > >>On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: > > >> > > >>>On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: > > >>I've fixed my XFree86 install, and I have 4.2.1 running. All of > > >>the > > >>ports mentioned above are installed. I am able to run xf86cfg > > >>graphically and configure, and I can run X using startx, which > > >>loads > > >>fine. > > >> > > >>However, when I do: > > >> > > >>sudo /usr/X11R6/etc/rc.d/gdm.sh start > > >> > > >>I get: > > >> > > >>Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display > > >>server > > >>several times in a short time period; disabling display :0 > > > > > >I would need to see the X log to know if it's a gdm problem. > > >However, > > >I've never tried starting gdm under sudo. > > > > Well, the same behavior occurs if I just restart the machine and let > > the script be triggered normally, so I doubt that sudo has anything > > to > > do with it. Also, I successfully started gdm many times this way > > under > > gnome 2.0. > > > > I have posted /var/log/:0.log and var/log/XFree86.0.log here: > > > > http://mark.antsclimbtree.com/Xlog.txt > > >>> > > >>>Nothing useful here. You might try doing a forced rebuild of gdm2. > > >>> > > >>>Joe > > >> > > >>I got it. I tried switching to root, and running startx (root's > > >>.xinitrc was set to start gnome). I got a complaint that fontconfig > > >>couldn't start. Aha! > > >> > > >>I removed /usr/X11R6/etc/fonts and reinstalled > > >>/usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I > > >>have anti-aliased fonts! Damn, that was painful, but I guess it was > > >>worth it. > > > > > >I"m fighting this exact same problem, and I was wondering if I could > > >trouble you with a couple of questions. > > > > > >You say you removed /usr/X11R6/etc/fonts. Do you mean the whole thing? > > >As > > >in evert font on the system? If so, exactly what did you do to reinstall > > >just the fonts? > > > > My /usr/X11R6/etc/fonts directory looks like this: > > > > total 16 > > -r--r--r-- 1 root wheel 8618 Feb 13 11:35 fonts.conf > > -r--r--r-- 1 root wheel 5712 Feb 13 11:35 fonts.dtd > > > > So, I removed that directory, and I did > > > > cd /usr/ports/x11-fonts/fontconfig > > make deinstall > > make clean install > > Thanks, I was confused, I thought yu were remooving the fonts themselves. I > had to remove the 75 dpi fonts on one of my machines to get fc-cahe to run. Probably a corrupt font file. You might try removing XFree86-font*, then reinstall those ports to see if the problem goes away. Like I said, fc-cache runs just fine for me on four different machines (3 -STABLE, 1 -CURRENT). Two of them have custom TrueType fonts added as well. All of them have webfonts installed. Joe > > In any case, I've done this, and I will be able to test when I egt home. > > Thanks for the help. -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Fri, Feb 14, 2003 at 11:58:20AM -0800, Mark Edwards wrote: > On Friday, February 14, 2003, at 11:21 AM, stan wrote: > > >On Thu, Feb 13, 2003 at 11:46:47AM -0800, Mark Edwards wrote: > >>On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: > >> > >>>On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: > >>I've fixed my XFree86 install, and I have 4.2.1 running. All of > >>the > >>ports mentioned above are installed. I am able to run xf86cfg > >>graphically and configure, and I can run X using startx, which > >>loads > >>fine. > >> > >>However, when I do: > >> > >>sudo /usr/X11R6/etc/rc.d/gdm.sh start > >> > >>I get: > >> > >>Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display > >>server > >>several times in a short time period; disabling display :0 > > > >I would need to see the X log to know if it's a gdm problem. > >However, > >I've never tried starting gdm under sudo. > > Well, the same behavior occurs if I just restart the machine and let > the script be triggered normally, so I doubt that sudo has anything > to > do with it. Also, I successfully started gdm many times this way > under > gnome 2.0. > > I have posted /var/log/:0.log and var/log/XFree86.0.log here: > > http://mark.antsclimbtree.com/Xlog.txt > >>> > >>>Nothing useful here. You might try doing a forced rebuild of gdm2. > >>> > >>>Joe > >> > >>I got it. I tried switching to root, and running startx (root's > >>.xinitrc was set to start gnome). I got a complaint that fontconfig > >>couldn't start. Aha! > >> > >>I removed /usr/X11R6/etc/fonts and reinstalled > >>/usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I > >>have anti-aliased fonts! Damn, that was painful, but I guess it was > >>worth it. > > > >I"m fighting this exact same problem, and I was wondering if I could > >trouble you with a couple of questions. > > > >You say you removed /usr/X11R6/etc/fonts. Do you mean the whole thing? > >As > >in evert font on the system? If so, exactly what did you do to reinstall > >just the fonts? > > My /usr/X11R6/etc/fonts directory looks like this: > > total 16 > -r--r--r-- 1 root wheel 8618 Feb 13 11:35 fonts.conf > -r--r--r-- 1 root wheel 5712 Feb 13 11:35 fonts.dtd > > So, I removed that directory, and I did > > cd /usr/ports/x11-fonts/fontconfig > make deinstall > make clean install Thanks, I was confused, I thought yu were remooving the fonts themselves. I had to remove the 75 dpi fonts on one of my machines to get fc-cahe to run. In any case, I've done this, and I will be able to test when I egt home. Thanks for the help. -- "They that would give up essential liberty for temporary safety deserve neither liberty nor safety." -- Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Fri, 2003-02-14 at 14:58, Mark Edwards wrote: > On Friday, February 14, 2003, at 11:21 AM, stan wrote: > > > On Thu, Feb 13, 2003 at 11:46:47AM -0800, Mark Edwards wrote: > >> On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: > >> > >>> On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: > >> I've fixed my XFree86 install, and I have 4.2.1 running. All of > >> the > >> ports mentioned above are installed. I am able to run xf86cfg > >> graphically and configure, and I can run X using startx, which > >> loads > >> fine. > >> > >> However, when I do: > >> > >> sudo /usr/X11R6/etc/rc.d/gdm.sh start > >> > >> I get: > >> > >> Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display > >> server > >> several times in a short time period; disabling display :0 > > > > I would need to see the X log to know if it's a gdm problem. > > However, > > I've never tried starting gdm under sudo. > > Well, the same behavior occurs if I just restart the machine and let > the script be triggered normally, so I doubt that sudo has anything > to > do with it. Also, I successfully started gdm many times this way > under > gnome 2.0. > > I have posted /var/log/:0.log and var/log/XFree86.0.log here: > > http://mark.antsclimbtree.com/Xlog.txt > >>> > >>> Nothing useful here. You might try doing a forced rebuild of gdm2. > >>> > >>> Joe > >> > >> I got it. I tried switching to root, and running startx (root's > >> .xinitrc was set to start gnome). I got a complaint that fontconfig > >> couldn't start. Aha! > >> > >> I removed /usr/X11R6/etc/fonts and reinstalled > >> /usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I > >> have anti-aliased fonts! Damn, that was painful, but I guess it was > >> worth it. > > > > I"m fighting this exact same problem, and I was wondering if I could > > trouble you with a couple of questions. > > > > You say you removed /usr/X11R6/etc/fonts. Do you mean the whole thing? > > As > > in evert font on the system? If so, exactly what did you do to reinstall > > just the fonts? > > My /usr/X11R6/etc/fonts directory looks like this: > > total 16 > -r--r--r-- 1 root wheel 8618 Feb 13 11:35 fonts.conf > -r--r--r-- 1 root wheel 5712 Feb 13 11:35 fonts.dtd > > So, I removed that directory, and I did > > cd /usr/ports/x11-fonts/fontconfig > make deinstall > make clean install > > That fixed the problem for me. I don't know that deleting the > fonts.conf and fonts.dtd actually did anything, I was just shooting in > the dark. I saw that something was foul with fontconfig, so I wanted to > make sure I wiped out anything corrupted in fonts.conf. I knew the > installer would replace that directory. > > If two of us have had this issue now, I wonder if there's something > about the build order of the gnome2.2 port that is messing up fontconfig > when upgrading from a previous gnome2 install, or something like that. > Does that sound plausible Joe? Not likely. I've upgraded four machines now, and never encountered this problem. I know quite a few others that haven't run in to it, either. As long as you properly upgrade GNOME 2 and all of its components, you really shouldn't run into a problem. That's not to say a bad font or fontdir, or bad ~/.fonts.conf couldn't hurt you. Joe > > -- > Mark Edwards > Engineer > Mr. Toad's > San Francisco, CA > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Friday, February 14, 2003, at 11:21 AM, stan wrote: On Thu, Feb 13, 2003 at 11:46:47AM -0800, Mark Edwards wrote: On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Well, the same behavior occurs if I just restart the machine and let the script be triggered normally, so I doubt that sudo has anything to do with it. Also, I successfully started gdm many times this way under gnome 2.0. I have posted /var/log/:0.log and var/log/XFree86.0.log here: http://mark.antsclimbtree.com/Xlog.txt Nothing useful here. You might try doing a forced rebuild of gdm2. Joe I got it. I tried switching to root, and running startx (root's .xinitrc was set to start gnome). I got a complaint that fontconfig couldn't start. Aha! I removed /usr/X11R6/etc/fonts and reinstalled /usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I have anti-aliased fonts! Damn, that was painful, but I guess it was worth it. I"m fighting this exact same problem, and I was wondering if I could trouble you with a couple of questions. You say you removed /usr/X11R6/etc/fonts. Do you mean the whole thing? As in evert font on the system? If so, exactly what did you do to reinstall just the fonts? My /usr/X11R6/etc/fonts directory looks like this: total 16 -r--r--r-- 1 root wheel 8618 Feb 13 11:35 fonts.conf -r--r--r-- 1 root wheel 5712 Feb 13 11:35 fonts.dtd So, I removed that directory, and I did cd /usr/ports/x11-fonts/fontconfig make deinstall make clean install That fixed the problem for me. I don't know that deleting the fonts.conf and fonts.dtd actually did anything, I was just shooting in the dark. I saw that something was foul with fontconfig, so I wanted to make sure I wiped out anything corrupted in fonts.conf. I knew the installer would replace that directory. If two of us have had this issue now, I wonder if there's something about the build order of the gnome2.2 port that is messing up fontconfig when upgrading from a previous gnome2 install, or something like that. Does that sound plausible Joe? -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 13, 2003, at 11:29 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Well, the same behavior occurs if I just restart the machine and let the script be triggered normally, so I doubt that sudo has anything to do with it. Also, I successfully started gdm many times this way under gnome 2.0. I have posted /var/log/:0.log and var/log/XFree86.0.log here: http://mark.antsclimbtree.com/Xlog.txt Nothing useful here. You might try doing a forced rebuild of gdm2. Joe I got it. I tried switching to root, and running startx (root's .xinitrc was set to start gnome). I got a complaint that fontconfig couldn't start. Aha! I removed /usr/X11R6/etc/fonts and reinstalled /usr/ports/x11-fonts/fontconfig and voila! Everything's fine, AND I have anti-aliased fonts! Damn, that was painful, but I guess it was worth it. I'm not sure what was fubar'd with fontconfig, but maybe make a mental note of it in case someone else is upgrading to gnome2.2 and gnome suddenly stops working. Could have simply been corruption on my end because of running a funky XFree86 3.3.6/gnome2 setup or something. I don't know and at this point I don't care, cause it works! Thanks for your patience, Joe... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thu, 2003-02-13 at 13:03, Mark Edwards wrote: > >> I've fixed my XFree86 install, and I have 4.2.1 running. All of the > >> ports mentioned above are installed. I am able to run xf86cfg > >> graphically and configure, and I can run X using startx, which loads > >> fine. > >> > >> However, when I do: > >> > >> sudo /usr/X11R6/etc/rc.d/gdm.sh start > >> > >> I get: > >> > >> Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display > >> server > >> several times in a short time period; disabling display :0 > > > > I would need to see the X log to know if it's a gdm problem. However, > > I've never tried starting gdm under sudo. > > Well, the same behavior occurs if I just restart the machine and let > the script be triggered normally, so I doubt that sudo has anything to > do with it. Also, I successfully started gdm many times this way under > gnome 2.0. > > I have posted /var/log/:0.log and var/log/XFree86.0.log here: > > http://mark.antsclimbtree.com/Xlog.txt Nothing useful here. You might try doing a forced rebuild of gdm2. Joe > > Thanks. > > -- > Mark Edwards > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 13, 2003, at 08:52 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-13 at 04:42, Mark Edwards wrote: On Tuesday, February 11, 2003, at 02:30 PM, Scott A. Moberly wrote: My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? pkg_info | fgrep XFree86 XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit imake-4.2.0_1 Imake and other utilities from XFree86 First of all you probably need to install: XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts to deal with the explicit problem on your X startup. Though this may not work as you also want the following packages: XFree86-Server-4.2.1_7 XFree86-4 X server and related programs XFree86-clients-4.2.1_2 XFree86-4 Client environments XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files wrapper-1.0_2 Wrapper for XFree86-4 server freetype2-2.1.3_1 A free and portable TrueType font rendering engine Some aren't strictly necessary, but... If you are in a rush you could install these one by one (starting with default fonts) until you are up and running otherwise make install clean deinstall everything you 'think' you have and start from scratch. Okay, well I've made some progress, but still can't get gdm/gnome running with 2.2. I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Well, the same behavior occurs if I just restart the machine and let the script be triggered normally, so I doubt that sudo has anything to do with it. Also, I successfully started gdm many times this way under gnome 2.0. I have posted /var/log/:0.log and var/log/XFree86.0.log here: http://mark.antsclimbtree.com/Xlog.txt Thanks. -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thu, 2003-02-13 at 04:42, Mark Edwards wrote: > On Tuesday, February 11, 2003, at 02:30 PM, Scott A. Moberly wrote: > > >>> My two cents in here real quick, what does: > >>> > >>> pkg_info | fgrep XFree86 > >>> > >>> give? > >> > >>> pkg_info | fgrep XFree86 > >> XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit > >> imake-4.2.0_1 Imake and other utilities from XFree86 > > > > First of all you probably need to install: > > > > XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts > > > > to deal with the explicit problem on your X startup. > > > > Though this may not work as you also want the following packages: > > > > XFree86-Server-4.2.1_7 XFree86-4 X server and related programs > > XFree86-clients-4.2.1_2 XFree86-4 Client environments > > XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts > > XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts > > XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files > > XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files > > wrapper-1.0_2 Wrapper for XFree86-4 server > > freetype2-2.1.3_1 A free and portable TrueType font rendering engine > > > > Some aren't strictly necessary, but... > > > > If you are in a rush you could install these one by one (starting with > > default fonts) until you are up and running > > > > otherwise make install clean deinstall everything you 'think' you have > > and > > start from scratch. > > Okay, well I've made some progress, but still can't get gdm/gnome > running with 2.2. > > I've fixed my XFree86 install, and I have 4.2.1 running. All of the > ports mentioned above are installed. I am able to run xf86cfg > graphically and configure, and I can run X using startx, which loads > fine. > > However, when I do: > > sudo /usr/X11R6/etc/rc.d/gdm.sh start > > I get: > > Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server > several times in a short time period; disabling display :0 I would need to see the X log to know if it's a gdm problem. However, I've never tried starting gdm under sudo. Joe > > So, my problems seem to be specifically with gnome 2.2. I was running > gnome 2.0 with no problems before doing a portupgrade -ra and getting > the new gnome 2.2 stuff installed. I did have a fairly goofy XFree86 > install, granted, but it ran. > > In any case, my /var/log/:0.log and /var/log/XFree86.0.log show no > errors. gdm just isn't starting up. Where can I look for clues? I've > tried installing /usr/ports/x11/gnome2 again just to make sure nothing > is missing, but it says everything is found. Perhaps I should cvs and > portupgrade? I'm stuck... > > -- > Mark Edwards > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 02:30 PM, Scott A. Moberly wrote: My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? pkg_info | fgrep XFree86 XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit imake-4.2.0_1 Imake and other utilities from XFree86 First of all you probably need to install: XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts to deal with the explicit problem on your X startup. Though this may not work as you also want the following packages: XFree86-Server-4.2.1_7 XFree86-4 X server and related programs XFree86-clients-4.2.1_2 XFree86-4 Client environments XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files wrapper-1.0_2 Wrapper for XFree86-4 server freetype2-2.1.3_1 A free and portable TrueType font rendering engine Some aren't strictly necessary, but... If you are in a rush you could install these one by one (starting with default fonts) until you are up and running otherwise make install clean deinstall everything you 'think' you have and start from scratch. Okay, well I've made some progress, but still can't get gdm/gnome running with 2.2. I've fixed my XFree86 install, and I have 4.2.1 running. All of the ports mentioned above are installed. I am able to run xf86cfg graphically and configure, and I can run X using startx, which loads fine. However, when I do: sudo /usr/X11R6/etc/rc.d/gdm.sh start I get: Feb 13 01:28:56 lilbuddy gdm[15381]: Failed to start the display server several times in a short time period; disabling display :0 So, my problems seem to be specifically with gnome 2.2. I was running gnome 2.0 with no problems before doing a portupgrade -ra and getting the new gnome 2.2 stuff installed. I did have a fairly goofy XFree86 install, granted, but it ran. In any case, my /var/log/:0.log and /var/log/XFree86.0.log show no errors. gdm just isn't starting up. Where can I look for clues? I've tried installing /usr/ports/x11/gnome2 again just to make sure nothing is missing, but it says everything is found. Perhaps I should cvs and portupgrade? I'm stuck... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
>> My two cents in here real quick, what does: >> >> pkg_info | fgrep XFree86 >> >> give? > > > pkg_info | fgrep XFree86 > XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit > imake-4.2.0_1 Imake and other utilities from XFree86 First of all you probably need to install: XFree86-fontDefaultBitmaps-4.2.0 XFree86-4 default bitmap fonts to deal with the explicit problem on your X startup. Though this may not work as you also want the following packages: XFree86-Server-4.2.1_7 XFree86-4 X server and related programs XFree86-clients-4.2.1_2 XFree86-4 Client environments XFree86-font100dpi-4.2.0 XFree86-4 bitmap 100 dpi fonts XFree86-font75dpi-4.2.0 XFree86-4 bitmap 75 dpi fonts XFree86-fontEncodings-4.2.0 XFree86-4 font encoding files XFree86-fontScalable-4.2.0 XFree86-4 Scalable font files wrapper-1.0_2 Wrapper for XFree86-4 server freetype2-2.1.3_1 A free and portable TrueType font rendering engine Some aren't strictly necessary, but... If you are in a rush you could install these one by one (starting with default fonts) until you are up and running otherwise make install clean deinstall everything you 'think' you have and start from scratch. -- Scott A. Moberly [EMAIL PROTECTED] One of the lessons of history is that nothing is often a good thing to do and always a clever thing to say. -- Will Durant To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 02:19 PM, Scott A. Moberly wrote: I'm beginning to suspect my XFree86 install is toast. My man pages say 3.3.6. I think I had 3.3.6 installed from the original FreeBSD 4.3 or something like that, and somehow didn't fully remove it. When I do cd /usr/ports/x11/XFree86 sudo make deinstall it says the port isn't installed. However, I don't have XFree86-4 installed either, and my XFree86 man pages say 3.3.6, so clearly 3.3.6 didn't get deinstalled and is still half-working. Is there a way to say, "deinstall the files that would be installed if this port was installed?" Not that I know of. Perhaps portupgrade and friends have this capability. Or, would it be best to install /usr/ports/x11/XFree86, and then deinstall it? This would do it, but you might be able to get away with just installing XFree86-4 over top your existing X disaster. Joe I'm pretty sure if I can get 3.3.6 totally gone, and then install /usr/ports/x11/XFree86-4, I'm going to be set. Sorry to be bringing such a fubar'd system to you! -- Mark Edwards Engineer Mr. Toad's San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? > pkg_info | fgrep XFree86 XFree86-libraries-4.2.1_6 XFree86-4 include/(shared) library kit imake-4.2.0_1 Imake and other utilities from XFree86 -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
> On Tue, 2003-02-11 at 17:10, Mark Edwards wrote: >> On Tuesday, February 11, 2003, at 01:57 PM, Joe Marcus Clarke wrote: >> >> > >> > You may have accidentally overwritten X. However, it could also be >> that this file is very ancient, and doesn't properly reflect what's >> going on now. If you've found you've messed up X, you should remove >> all XFree86 packages, then reinstall the XFree86-4 meta-port. >> > >> > Joe >> >> I'm beginning to suspect my XFree86 install is toast. My man pages >> say 3.3.6. I think I had 3.3.6 installed from the original FreeBSD >> 4.3 or something like that, and somehow didn't fully remove it. When >> I do >> >> cd /usr/ports/x11/XFree86 >> sudo make deinstall >> >> it says the port isn't installed. However, I don't have XFree86-4 >> installed either, and my XFree86 man pages say 3.3.6, so clearly 3.3.6 >> didn't get deinstalled and is still half-working. >> >> Is there a way to say, "deinstall the files that would be installed if >> this port was installed?" > > Not that I know of. Perhaps portupgrade and friends have this > capability. > >> Or, would it be best to install >> /usr/ports/x11/XFree86, and then deinstall it? > > This would do it, but you might be able to get away with just installing > XFree86-4 over top your existing X disaster. > > Joe > >> >> I'm pretty sure if I can get 3.3.6 totally gone, and then install >> /usr/ports/x11/XFree86-4, I'm going to be set. Sorry to be bringing >> such a fubar'd system to you! >> >> -- >> Mark Edwards >> Engineer >> Mr. Toad's >> San Francisco, CA > -- > PGP Key : http://www.marcuscom.com/pgp.asc My two cents in here real quick, what does: pkg_info | fgrep XFree86 give? -- Scott A. Moberly [EMAIL PROTECTED] One of the lessons of history is that nothing is often a good thing to do and always a clever thing to say. -- Will Durant To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tue, 2003-02-11 at 17:10, Mark Edwards wrote: > On Tuesday, February 11, 2003, at 01:57 PM, Joe Marcus Clarke wrote: > > > > > You may have accidentally overwritten X. However, it could also be that > > this file is very ancient, and doesn't properly reflect what's going on > > now. If you've found you've messed up X, you should remove all XFree86 > > packages, then reinstall the XFree86-4 meta-port. > > > > Joe > > I'm beginning to suspect my XFree86 install is toast. My man pages say > 3.3.6. I think I had 3.3.6 installed from the original FreeBSD 4.3 or > something like that, and somehow didn't fully remove it. When I do > > cd /usr/ports/x11/XFree86 > sudo make deinstall > > it says the port isn't installed. However, I don't have XFree86-4 > installed either, and my XFree86 man pages say 3.3.6, so clearly 3.3.6 > didn't get deinstalled and is still half-working. > > Is there a way to say, "deinstall the files that would be installed if > this port was installed?" Not that I know of. Perhaps portupgrade and friends have this capability. > Or, would it be best to install > /usr/ports/x11/XFree86, and then deinstall it? This would do it, but you might be able to get away with just installing XFree86-4 over top your existing X disaster. Joe > > I'm pretty sure if I can get 3.3.6 totally gone, and then install > /usr/ports/x11/XFree86-4, I'm going to be set. Sorry to be bringing > such a fubar'd system to you! > > -- > Mark Edwards > Engineer > Mr. Toad's > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 01:57 PM, Joe Marcus Clarke wrote: You may have accidentally overwritten X. However, it could also be that this file is very ancient, and doesn't properly reflect what's going on now. If you've found you've messed up X, you should remove all XFree86 packages, then reinstall the XFree86-4 meta-port. Joe I'm beginning to suspect my XFree86 install is toast. My man pages say 3.3.6. I think I had 3.3.6 installed from the original FreeBSD 4.3 or something like that, and somehow didn't fully remove it. When I do cd /usr/ports/x11/XFree86 sudo make deinstall it says the port isn't installed. However, I don't have XFree86-4 installed either, and my XFree86 man pages say 3.3.6, so clearly 3.3.6 didn't get deinstalled and is still half-working. Is there a way to say, "deinstall the files that would be installed if this port was installed?" Or, would it be best to install /usr/ports/x11/XFree86, and then deinstall it? I'm pretty sure if I can get 3.3.6 totally gone, and then install /usr/ports/x11/XFree86-4, I'm going to be set. Sorry to be bringing such a fubar'd system to you! -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tue, 2003-02-11 at 16:28, Mark Edwards wrote: > On Tuesday, February 11, 2003, at 12:37 PM, Joe Marcus Clarke wrote: > > >> Well, I updated to 2.2 today, and while I was still in the gnome > >> desktop, it seemed to fix the anti-aliasing issues I was having. > >> However, I restarted, and now I get this: > >> > >> Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal > >> X error - Restarting :0 > >> Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal > >> X error - Restarting :0 > >> Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal > >> X error - Restarting :0 > >> Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal > >> X error - Restarting :0 > >> Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several > >> times in a short time period; disabling display :0 > >> > >> I've seen this before, of course. gdm is starting from > >> /usr/X11R6/etc/rc.d/gdm.sh, so that's not it. > >> > >> I removed the font-related alterations I made recently, that's not it. > >> > >> How do I figure out what's causing gdm to hang? > > > > Not sure. What's in your /var/log/XFree86.0.log? > > > > Joe > > I think I'm onto it. I don't have a /var/log/XFree86.0.log, but I do > have a /var/log/:0.log (where'd that name come from?), and it says: What is the date on this file? > > > XFree86 Version 3.3.6 / X Window System > > (protocol Version 11, revision 0, vendor release 6300) > > Release Date: xx November 2000 > > If the server is older than 6-12 months, or if your card is > > newer > > than the above date, look for a newer version before reporting > > problems. (see http://www.XFree86.Org/FAQ) > > Operating System: FreeBSD 4.5-PRERELEASE i386 [ELF] > > Configured drivers: > > Mach64: accelerated server for ATI Mach64 graphics adaptors > > (Patchlevel 1) > > Using syscons driver with X support (version 2.0) > > (using VT number 9) > > > > XF86Config: /etc/XF86Config > > (**) stands for supplied, (--) stands for probed/default values > > (--) no ModulePath specified using default: /usr/X11R6/lib/modules > > freetype: Unknown error loading module > > type1: Unknown error loading module > > (**) XKB: rules: "xfree86" > > (**) XKB: model: "pc101" > > (**) XKB: layout: "us" > > (**) Mouse: type: SysMouse, device: /dev/mouse, resolution: 100 > > (**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms) > > (**) Mach64: Graphics device ID: "Primary Card" > > (**) Mach64: Monitor ID: "Primary Monitor" > > Warning: 'fonts.dir' not found (or not valid) in > > "/usr/X11R6/lib/X11/fonts/local". > > Entry deleted from font path. > > (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local"). > > (**) FontPath set to > > "/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled, > > /usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/ > > X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/ > > fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/ > > " > > (--) Mach64: PCI: Mach64 CT rev 9, Aperture @ 0xfe00, Block I/O @ > > 0xfc00 > > (--) Mach64: Card type: PCI > > (--) Mach64: Memory type: DRAM (1) > > (--) Mach64: Clock type: Internal > > (--) Mach64: Maximum allowed dot-clock: 80.000 MHz > > (**) Mach64: Mode "800x600": mode clock = 60.750 > > (--) Mach64: Virtual resolution: 800x600 > > (--) Mach64: Video RAM: 2048k > > (--) Mach64: Using hardware cursor > > (--) Mach64: Using 16 MB aperture @ 0xfe00 > > (--) Mach64: Ramdac is Internal > > (--) Mach64: Ramdac speed: 80 MHz > > (**) Mach64: Color weight: 565 > > (--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 > > slots > > (--) Mach64: Font cache: 0 fonts > > failed to set default font path > > '/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled, > > /usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/ > > X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/ > > fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/ > > ' > > Fatal server error: > > could not open default font 'fixed' > > > > When reporting a problem related to a server crash, please send > > the full server output, not just the last messages > > Now, I'd say the error is clear. Do I just need to run mkfontdir on my > font directories? Odd that I need to do that, since this was a working > installation before the 2.2 update. > > Other questions -- why does the log report XFree86 Version 3.3.6 on > FreeBSD 4.5 PRERELEASE? As far as I can tell I'm running XFree86 4.2.1, > and I'm definitely running FreeBSD 4.7p4. That's scary. Maybe I need > to completely reinstall and reconfigure XFree86? Is that as simple as > removing the XFree86-libraries-4.2.1_6 package and reinstalling it? Do > I just need to go to /stand/sysinstall and re-config
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tuesday, February 11, 2003, at 12:37 PM, Joe Marcus Clarke wrote: Well, I updated to 2.2 today, and while I was still in the gnome desktop, it seemed to fix the anti-aliasing issues I was having. However, I restarted, and now I get this: Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several times in a short time period; disabling display :0 I've seen this before, of course. gdm is starting from /usr/X11R6/etc/rc.d/gdm.sh, so that's not it. I removed the font-related alterations I made recently, that's not it. How do I figure out what's causing gdm to hang? Not sure. What's in your /var/log/XFree86.0.log? Joe I think I'm onto it. I don't have a /var/log/XFree86.0.log, but I do have a /var/log/:0.log (where'd that name come from?), and it says: XFree86 Version 3.3.6 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: xx November 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 4.5-PRERELEASE i386 [ELF] Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 1) Using syscons driver with X support (version 2.0) (using VT number 9) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (--) no ModulePath specified using default: /usr/X11R6/lib/modules freetype: Unknown error loading module type1: Unknown error loading module (**) XKB: rules: "xfree86" (**) XKB: model: "pc101" (**) XKB: layout: "us" (**) Mouse: type: SysMouse, device: /dev/mouse, resolution: 100 (**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms) (**) Mach64: Graphics device ID: "Primary Card" (**) Mach64: Monitor ID: "Primary Monitor" Warning: 'fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/local"). (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled, /usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/ X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/ fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/ " (--) Mach64: PCI: Mach64 CT rev 9, Aperture @ 0xfe00, Block I/O @ 0xfc00 (--) Mach64: Card type: PCI (--) Mach64: Memory type: DRAM (1) (--) Mach64: Clock type: Internal (--) Mach64: Maximum allowed dot-clock: 80.000 MHz (**) Mach64: Mode "800x600": mode clock = 60.750 (--) Mach64: Virtual resolution: 800x600 (--) Mach64: Video RAM: 2048k (--) Mach64: Using hardware cursor (--) Mach64: Using 16 MB aperture @ 0xfe00 (--) Mach64: Ramdac is Internal (--) Mach64: Ramdac speed: 80 MHz (**) Mach64: Color weight: 565 (--) Mach64: Pixmap cache: 0 256x256 slots, 0 128x128 slots, 0 64x64 slots (--) Mach64: Font cache: 0 fonts failed to set default font path '/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled, /usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/ X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/ fonts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi,/usr/X11R6/lib/X11/fonts/webfonts/ ' Fatal server error: could not open default font 'fixed' When reporting a problem related to a server crash, please send the full server output, not just the last messages Now, I'd say the error is clear. Do I just need to run mkfontdir on my font directories? Odd that I need to do that, since this was a working installation before the 2.2 update. Other questions -- why does the log report XFree86 Version 3.3.6 on FreeBSD 4.5 PRERELEASE? As far as I can tell I'm running XFree86 4.2.1, and I'm definitely running FreeBSD 4.7p4. That's scary. Maybe I need to completely reinstall and reconfigure XFree86? Is that as simple as removing the XFree86-libraries-4.2.1_6 package and reinstalling it? Do I just need to go to /stand/sysinstall and re-configure XFree86? Very odd. -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Tue, 2003-02-11 at 04:03, Mark Edwards wrote: > On Friday, February 7, 2003, at 12:05 AM, Joe Marcus Clarke wrote: > > > On Fri, 2003-02-07 at 02:58, Mark Edwards wrote: > > > >> > >> Well, I have the XFree86-libraries-4.2.1_6 port installed, and my > >> XF86Config file contains: > >> > >> Section "Module" > >> Load "freetype" > >> Load "type1" > >> EndSection > >> > >> I think that fits the bill, but obviously something is wrong... > > > > Probably is the lack of RENDER support. Since it works for Mozilla, it > > should work for GNOME 2.2, so just be patient. I've just finished all > > the ports, and assuming I didn't miss anything in my documentation > > updates, I'll start the merge when I wake up tomorrow. > > Well, I updated to 2.2 today, and while I was still in the gnome > desktop, it seemed to fix the anti-aliasing issues I was having. > However, I restarted, and now I get this: > > Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal > X error - Restarting :0 > Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal > X error - Restarting :0 > Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal > X error - Restarting :0 > Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal > X error - Restarting :0 > Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several > times in a short time period; disabling display :0 > > I've seen this before, of course. gdm is starting from > /usr/X11R6/etc/rc.d/gdm.sh, so that's not it. > > I removed the font-related alterations I made recently, that's not it. > > How do I figure out what's causing gdm to hang? Not sure. What's in your /var/log/XFree86.0.log? Joe > > -- > Mark Edwards > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Friday, February 7, 2003, at 12:05 AM, Joe Marcus Clarke wrote: On Fri, 2003-02-07 at 02:58, Mark Edwards wrote: Well, I have the XFree86-libraries-4.2.1_6 port installed, and my XF86Config file contains: Section "Module" Load "freetype" Load "type1" EndSection I think that fits the bill, but obviously something is wrong... Probably is the lack of RENDER support. Since it works for Mozilla, it should work for GNOME 2.2, so just be patient. I've just finished all the ports, and assuming I didn't miss anything in my documentation updates, I'll start the merge when I wake up tomorrow. Well, I updated to 2.2 today, and while I was still in the gnome desktop, it seemed to fix the anti-aliasing issues I was having. However, I restarted, and now I get this: Feb 11 00:51:32 lilbuddy gdm[24662]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:34 lilbuddy gdm[24666]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:39 lilbuddy gdm[24670]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24674]: gdm_slave_xioerror_handler: Fatal X error - Restarting :0 Feb 11 00:51:44 lilbuddy gdm[24661]: Failed to start X server several times in a short time period; disabling display :0 I've seen this before, of course. gdm is starting from /usr/X11R6/etc/rc.d/gdm.sh, so that's not it. I removed the font-related alterations I made recently, that's not it. How do I figure out what's causing gdm to hang? -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Friday, February 7, 2003, at 12:05 AM, Joe Marcus Clarke wrote: On Fri, 2003-02-07 at 02:58, Mark Edwards wrote: Well, I have the XFree86-libraries-4.2.1_6 port installed, and my XF86Config file contains: Section "Module" Load "freetype" Load "type1" EndSection I think that fits the bill, but obviously something is wrong... Probably is the lack of RENDER support. Since it works for Mozilla, it should work for GNOME 2.2, so just be patient. I've just finished all the ports, and assuming I didn't miss anything in my documentation updates, I'll start the merge when I wake up tomorrow. Joe Great! Let me know if you need any other info from me... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Fri, 2003-02-07 at 02:58, Mark Edwards wrote: > > Well, I have the XFree86-libraries-4.2.1_6 port installed, and my > XF86Config file contains: > > Section "Module" > Load "freetype" > Load "type1" > EndSection > > I think that fits the bill, but obviously something is wrong... Probably is the lack of RENDER support. Since it works for Mozilla, it should work for GNOME 2.2, so just be patient. I've just finished all the ports, and assuming I didn't miss anything in my documentation updates, I'll start the merge when I wake up tomorrow. Joe > > -- > Mark Edwards > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 11:53 PM, Joe Marcus Clarke wrote: 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 verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. I've done a bit of work on this, despite your suggestion not to, and I'm still coming up short. I found a tutorial that suggests xdpyinfo | grep -c -i render as a test to see if XFree86 is including render support. Doing this on my system returns 0 instead 1 which the tutorial says is necessary for anti-aliasing. The tutorial says "wait until XFree86 supports Render on your graphics card." This is an old machine with an ATI Mach64 CT, so I would believe it is unsupported, however ... What's strange is that anti-aliasing is clearly occurring in a few places for me, most notably in Mozilla. In Mozilla Mail, a message displayed in fixed-width font (Courier) is quite clearly anti-aliased, next to a variable-width font (Times) that is not. Zooming the text to 600% makes this quite evident. I also have seen anti-aliased text in the gdm2 graphic greeter. These two examples existed even before I had added GDK_USE_XFT to my environment, or followed any of the directions in the FAQ for enabling anti-aliased text. So, there is anti-aliasing going on without any settings whatsoever, but following the directions in the FAQ, adding all my font directories to XftConfig, and setting "match edit antialias=true;" in that file, still results in most fonts not being anti-aliased. 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 Well, I have the XFree86-libraries-4.2.1_6 port installed, and my XF86Config file contains: Section "Module" Load "freetype" Load "type1" EndSection I think that fits the bill, but obviously something is wrong... -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Fri, 2003-02-07 at 02:41, Mark Edwards wrote: > On Thursday, February 6, 2003, at 09:14 AM, Joe Marcus Clarke wrote: > > > 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. > > 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 > > in > > the GUI tool. > > I figured this out. gdm2 has removed the BackgroundProgram feature > from the configuration gui, but it still exists in gdm.conf. You have > to set > > BackgroundProgram=/usr/X11R6/bin/xscreensaver -nosplash > > and also > > RunBackgroundProgramAlways=true > > However, it doesn't seem to work with the new graphical greeter. > That's what got me. Use the default greeter, and set the above > settings in gdm.conf (and put an .xscreensaver in the gdm home > directory) and you get xscreensaver during the login window. > > >> 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. > > I think I spoke too quickly on this one. It appears that on second > load, the gdm configure tool just takes a really long time on my > machine. I mistook this for the crashing that I saw with gdm under > gnome 1.4, which I originally solved by a re-install. Sorry for the > false alarm! > > >> 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 > > verge > > of committing GNOME 2.2 which no longer requires GDK_USE_XFT. > > I've done a bit of work on this, despite your suggestion not to, and > I'm still coming up short. I found a tutorial that suggests > > xdpyinfo | grep -c -i render > > as a test to see if XFree86 is including render support. Doing this on > my system returns 0 instead 1 which the tutorial says is necessary for > anti-aliasing. The tutorial says "wait until XFree86 supports Render > on your graphics card." This is an old machine with an ATI Mach64 CT, > so I would believe it is unsupported, however ... > > What's strange is that anti-aliasing is clearly occurring in a few > places for me, most notably in Mozilla. In Mozilla Mail, a message > displayed in fixed-width font (Courier) is quite clearly anti-aliased, > next to a variable-width font (Times) that is not. Zooming the text to > 600% makes this quite evident. > > I also have seen anti-aliased text in the gdm2 graphic greeter. These > two examples existed even before I had added GDK_USE_XFT to my > environment, or followed any of the directions in the FAQ for enabling > anti-aliased text. So, there is anti-aliasing going on without any > settings whatsoever, but following the directions in the FAQ, adding > all my font directories to XftConfig, and setting "match edit > antialias=true;" in that file, still results in most fonts not being > anti-aliased. > > 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 > > -- > Mark Edwards > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 09:14 AM, Joe Marcus Clarke wrote: 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. 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 in the GUI tool. I figured this out. gdm2 has removed the BackgroundProgram feature from the configuration gui, but it still exists in gdm.conf. You have to set BackgroundProgram=/usr/X11R6/bin/xscreensaver -nosplash and also RunBackgroundProgramAlways=true However, it doesn't seem to work with the new graphical greeter. That's what got me. Use the default greeter, and set the above settings in gdm.conf (and put an .xscreensaver in the gdm home directory) and you get xscreensaver during the login window. 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. I think I spoke too quickly on this one. It appears that on second load, the gdm configure tool just takes a really long time on my machine. I mistook this for the crashing that I saw with gdm under gnome 1.4, which I originally solved by a re-install. Sorry for the false alarm! 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 verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. I've done a bit of work on this, despite your suggestion not to, and I'm still coming up short. I found a tutorial that suggests xdpyinfo | grep -c -i render as a test to see if XFree86 is including render support. Doing this on my system returns 0 instead 1 which the tutorial says is necessary for anti-aliasing. The tutorial says "wait until XFree86 supports Render on your graphics card." This is an old machine with an ATI Mach64 CT, so I would believe it is unsupported, however ... What's strange is that anti-aliasing is clearly occurring in a few places for me, most notably in Mozilla. In Mozilla Mail, a message displayed in fixed-width font (Courier) is quite clearly anti-aliased, next to a variable-width font (Times) that is not. Zooming the text to 600% makes this quite evident. I also have seen anti-aliased text in the gdm2 graphic greeter. These two examples existed even before I had added GDK_USE_XFT to my environment, or followed any of the directions in the FAQ for enabling anti-aliased text. So, there is anti-aliasing going on without any settings whatsoever, but following the directions in the FAQ, adding all my font directories to XftConfig, and setting "match edit antialias=true;" in that file, still results in most fonts not being anti-aliased. Any thoughts on what is wrong? -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 09:27 AM, Joe Marcus Clarke wrote: On Thu, 2003-02-06 at 12:14, Joe Marcus Clarke wrote: 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. I've verified this does not happen in the GNOME 2.2 gdm2. Joe But you don't know if it does happen with 2.0, right? Its funny because I had the same issue with gdm a while back. I wonder if its due to something else on my machine. I guess I'll wait for 2.2 and see. Thanks. -- Mark Edwards Engineer Mr. Toad's San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thu, 2003-02-06 at 12:27, Mark Edwards wrote: > Ah. So if XftConfig is set up properly, I should see everything > anti-aliased, is that right? And you have followed the instructions at http://www.freebsd.org/gnome/docs/faq2.html#q9, yes. Joe > > -- > Mark Edwards > San Francisco, CA > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thursday, February 6, 2003, at 09:14 AM, Joe Marcus Clarke wrote: 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. 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 in the GUI tool. Yes, I want the monitor to go into standby after 5 minutes of the login screen. 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. 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 verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. Ah. So if XftConfig is set up properly, I should see everything anti-aliased, is that right? -- Mark Edwards San Francisco, CA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
On Thu, 2003-02-06 at 12:14, Joe Marcus Clarke wrote: > > 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. I've verified this does not happen in the GNOME 2.2 gdm2. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Re: Gnome 2 on FreeBSD 4.7p3 -- multiple issues
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. 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 in the GUI tool. > > > 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. > > > 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 verge of committing GNOME 2.2 which no longer requires GDK_USE_XFT. Joe > > > Thanks! > > > > -- > > Mark Edwards > > San Francisco, CA -- PGP Key : http://www.marcuscom.com/pgp.asc signature.asc Description: This is a digitally signed message part
Gnome 2 on FreeBSD 4.7p3 -- multiple issues
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. 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. 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? Thanks! -- Mark Edwards San Francisco, CA
