Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
05-11-2004, 07:31 PM
|
#1
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Rep:
|
swaret update, upgrade, install - now font error
I loaded a full install of slackware 9.1 on a laptop and then grabbed swaret and updated everything. I rebooted and got 4 Error dialogs with the following message:
Code:
Font `-misc-console-medium-r-normal--16-160-72-72-c-80-iso10646-1' not found.
Check README.linux.console for help.
Has anybody else seen this? My system doesn't have a README.linux.console file to check. I didn't change any font directory locations in XF86Config.
I googled for this, but haven't come across a solution for my setup yet.
Still looking.
Thanks
(Note: I found a similar thread in the software forum, and I posted there, but I think this new titled thread was the better idea. Sorry about that.)
|
|
|
05-11-2004, 11:35 PM
|
#2
|
Member
Registered: Aug 2003
Location: Planet Earth
Distribution: Linux Mint
Posts: 216
Rep:
|
I did a fresh install of 9.1, then used swaret to upgrade to slackware-current. In /etc/swaret.conf I commented out the EXCLUDE lines, and set VERSION=current. Make sure you run lilo after swaret is done (before you reboot) since you'll get a kernel upgrade. No problems at all!
|
|
|
05-11-2004, 11:40 PM
|
#3
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Original Poster
Rep:
|
I set the VERSION to current, but I didn't change the EXCLUDE lines. So I didn't do the kernel upgrade on this one.
I think this may be related to some kde files. I haven't had a chance to google it further. I'll be doing that some more tomorrow.
Edit: Actually, I wanted to get everything current and then try my first kernel upgrade to 2.6.5 or 2.6.6 in the next couple of days.
Last edited by itsjustme; 05-11-2004 at 11:42 PM.
|
|
|
05-12-2004, 01:32 AM
|
#4
|
Member
Registered: Apr 2004
Distribution: Slackware/Mandrake/Debian (sarge)
Posts: 266
Rep:
|
Yeah.. I recommend keeping the kernel excluded as it's best to custom compile it for your system anyway. With the default kernel my system was a bit sluggish and unresponsive at times (music would stutter if the media player was in the background and I was moving windows).. but with a custom kernel no problems.. and it's got all the extensions my athlon xp supports loaded, etc.
Very nice ..
|
|
|
05-12-2004, 09:28 AM
|
#5
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Original Poster
Rep:
|
Well, I'm finding no help on google for this. But, comparing my other slackware machine (which I also swaret upgraded, including the kernel to 2.4.26) to this one, the other machine has a '.fonts.cache-1' file in my home directory, which is an empty file, and no '.fonts' directory, but this machine now has the '.fonts.cache-1' with a couple of new '.fonts' directory listings in it:
Code:
root@lapslack:/home/bs# ls -ld .font*
drwxr-xr-x 3 bs users 112 May 10 07:48 .fonts/
-rw-r--r-- 1 bs users 89 May 12 07:51 .fonts.cache-1
root@lapslack:/home/bs# cat .fonts.cache-1
"/home/bs/.fonts" 0 1084193326 ".dir"
"/home/bs/.fonts/kde-override" 0 1084366054 ".dir"
root@lapslack:/home/bs# cd .fonts
root@lapslack:/home/bs/.fonts# ls -l
total 5
-rw-r--r-- 1 bs users 2 May 12 07:26 fonts.dir
drwxr-xr-x 2 bs users 136 May 12 07:47 kde-override/
root@lapslack:/home/bs/.fonts# cat fonts.dir
0
root@lapslack:/home/bs/.fonts# cd kde-override
root@lapslack:/home/bs/.fonts/kde-override# ls -l
total 20
-rw-r--r-- 1 bs users 3770 Jun 30 2002 cursor.pcf.gz
-rw-r--r-- 1 root root 12288 May 12 07:47 et
-rw-r--r-- 1 bs users 23 May 12 07:26 fonts.dir
root@lapslack:/home/bs/.fonts/kde-override# cat fonts.dir
1
cursor.pcf.gz cursor
root@lapslack:/home/bs/.fonts/kde-override#
Maybe I just need to clear out the '.fonts.cache-1' file and see what that does.
The investigation continues.
Sometimes I hate these WTF stack issues. I want to look into the kernel upgrade thing, but I have to chase down this stupid font problem, since it gives me 4 error messages and plays a weird sound for each error when I startx.
Edit: There needs to be an option:
"swaret --upgrade only_essential_stuff_that_won't_screw_up_your_system" 
Last edited by itsjustme; 05-12-2004 at 09:36 AM.
|
|
|
05-12-2004, 03:07 PM
|
#6
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Original Poster
Rep:
|
Update. No solution yet. Except maybe, don't use KDE.
But, I did discover that KDE is now 3.2.2 and clicking on the terminal icon in the task bar pops up 'Shell - Konsole'. If I go to Settings/Font I see that Unicode is selected. If I change that to Linux then that pops up the error message about --the font could not be found. Although it was found and being used prior to the swaret upgrade.
Ok, so I'm getting close. I just checked, if I don't have any 'Shell - Konsole' open when KDE starts, then I don't get the errors.
[testing]
Weird. Now I am not getting the error when I startx (even if I have left a couple of konsoles open), except when I try to change the Konsole/Settings/Font to Linux. I can select other fonts in the Custom selection.
So, I'm not going to waste any more time trying to track this down.

Last edited by itsjustme; 05-12-2004 at 03:09 PM.
|
|
|
05-12-2004, 09:29 PM
|
#7
|
Senior Member
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132
Rep:
|
After upgrading via swaret, did you search for all of the .new configuratiion files and rename them accordingly? Seems a lot of people miss that step.
|
|
|
05-12-2004, 09:49 PM
|
#8
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Original Poster
Rep:
|
Hmmm... I didn't know anything about that.
I have 44 .new files on the system. 
|
|
|
05-12-2004, 09:53 PM
|
#9
|
Senior Member
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132
Rep:
|
Well, there you go. If you haven't made any changes to your cofiguration files, you can just rename whatever.the.filename.is.new to whatever.the.filename.is and reboot. You can have issues, though, if you have made changes to the original config files. In that case, you'll need to make the same changes to the .new files. I'm lazy and just did the rename. Re-booted and haven't had any isuues since. Try it out. If you're not sure, make backups beforehand.
If you just did a fresh install, you should be pretty safe just renaming.
Last edited by shilo; 05-12-2004 at 09:54 PM.
|
|
|
05-12-2004, 10:13 PM
|
#10
|
Senior Member
Registered: Mar 2003
Location: Earth
Distribution: Slackware, Ubuntu, Smoothwall
Posts: 1,571
Original Poster
Rep:
|
What a pain! I'll have to go through them one by one. 
For instance:
Code:
root@lapslack:~# ls -l /etc/passw*
-rw-r--r-- 1 root root 705 May 1 13:46 /etc/passwd
-rw------- 1 root root 700 May 1 13:46 /etc/passwd-
-rw-r--r-- 1 root root 666 Jun 13 2003 /etc/passwd.new
Here, passwd.new is a year older than passwd. I don't know where that passwd- came from.
I don't recall seeing any previous info, related to swaret, on .new files, except for swaret.conf.new.
|
|
|
05-12-2004, 11:28 PM
|
#11
|
Senior Member
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132
Rep:
|
When you upgrade a package that comes along with a configuration file, the new configuration file gets saved with a .new extension. This keeps your current configuration file from being overwritten. It really is a good thing. I believe you'll see the same thing with Dropline if you choose to use it.
I don't know about the passwd.new file. It's been awhile since I first upgraded to current. Try just re-naming a few of the .new files at a time and re-booting. If you have any problems, you'll know which ones to change back. I'm a more, "Let's see if this breaks anything", type of guy, so I just re-named all of the .new files in one fell swoop.
I remember that it was like two weeks after I upgraded everything the first time that I first found out about all of the .new files. Took me by surprise, too.
My top tips for using swaret are
1) Don't change the exclude list.
You don't want to upgrade the kernel with swaret. Do it yourself. You'll get much better results. Also, the default exclude list keeps you from having issues with Dropline, should you choose to use Dropline.
2) Use updatedb frequently and set swaret to use slocate
This will save you some time.
3) Uncomment the line to use linuxpackages.net as a repository
You'll get a few benefits here. Your packages will be upgraded to i686 packages if they exist. You'll also be able to use swaret --install to get a lot more software.
|
|
|
All times are GMT -5. The time now is 05:27 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|