LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-02-2004, 08:30 AM   #1
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Rep: Reputation: 30
Problem with Gnome after swaret upgrade


Installed Slack 10.0, installed swaret and updated, then upgrade -a.

After "startx", Gnome splash screen freezes in the desktop and the herring-bone background won't give way to the Gnome desktop. I can't see any open applications because the boot background is masking the desktop - I also can't log out because the log-out prompt is masked by the boot background also. I de-powered and booted to "kdm" instead so I could post this.

What happened to Gnome during the upgrade? What can I edit to fix this?

Compaq Armada M700, PIII, Slackware 10.0
 
Old 09-02-2004, 11:33 AM   #2
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 52
Try removing (or moving somewhere else from your ~) your gnome config files
 
Old 09-03-2004, 02:16 PM   #3
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Original Poster
Rep: Reputation: 30
I followed the direction #7 to the letter.... Could step #8 (That I did not do) be the problem?

Making Sure You've got the Latest & Greatest
7) Install SWareT. Go here http://www.swaret.org to get the package. The first thing you will want to do is edit the swaret.conf file. Change the version to current. Uncomment the line for linuxpackages.net. Enable slocate. Now type "swaret --update", then type "swaret --upgrade -a", Then "swaret --dep". This will take awhile. I run swaret --upgrade -a a few times, because you will usually have a few packages that didn't get downloaded the first few times.

Making Sure the Latest & Greatest Works!!!
8) Here's a step everyone seems to miss. Since you have done a fresh install, the configuration files should all still be stock. When you upgrade packages, you get a lot of files that end in .new. These are the new configuration files. The updaters that you have run didn't want to get rid of possibly custom configuration files. Since none of our configuration files are custom yet, it's pretty safe to do this: updatedb to update the search database. Now type "slocate .new" Go to each one of those files and drop the .new off of the filename. You'll have to also delete the other file with the same name first.

I re-installed Slack 10.0, so I'm back to a stock system. I didn't install Dropline yet, and I'm afraid to turn swaret loose on my system again.
 
Old 09-03-2004, 04:32 PM   #4
ringwraith
Senior Member
 
Registered: Sep 2003
Location: Indiana
Distribution: Slackware 14.2
Posts: 1,268

Rep: Reputation: 59
To avoid having this type stuff happen in the future, I would encourage you to read the changelogs. Use wget to download the updates then use upgradepkg or one of the other tools to manage your own system. That way you know your system isn't going to be left in an unusable state.
 
Old 09-03-2004, 07:20 PM   #5
mago
Member
 
Registered: Apr 2004
Location: Costa Rica
Distribution: slack current with 2.6.16.18 (still off the hook)
Posts: 284

Rep: Reputation: 33
I think you might have problems with the libcroco after the upgrade -a you probablu have the version 6, just install the libcroco.so.5 and I'm pretty sure you won't have any more problmes.

Already walked that path...
 
Old 09-04-2004, 02:18 PM   #6
shilo
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: Reputation: 50
It seems that you are following the advice from my website. I have changed my mind about uncommneting the linuxpackages.net repository. Leave it commented out. A little late now, I know, but if you end up doing a clean install ,this will help out a bunch.

Good luck,
 
Old 09-05-2004, 09:25 PM   #7
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Original Poster
Rep: Reputation: 30
I did re-install Slackware 10.0 and was afraid to touch it again... I'll give it a try again and comment out the linuxpackages.net repository. Thnx, Shilo!
 
Old 09-05-2004, 10:08 PM   #8
shilo
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: Reputation: 50
There have been some other changes. Here is my current /etc/swaret.conf. Feel free ot use it. You'l notice some small changes. I'd just copy this to /etc/swaret.conf, then:

updatedb
swaret --update
swaret --upgrade
swaret --install vsftp

That will give you Slackware current. Note that this installs vsftp, the new default ftp server. There will be changes that need to be made to config files, so don't forget to look for the ".new" files.

While your at it, I'd add checkinstall with the command:

swaret --install checkinstall

Hell, while your at it, if you want a CD burning application, might as well use:

swaret --install k3b

If you did a full install, you already have all the official Slackware packages except for the stuff in currrent, which you just installed, and the stuff in extra and pasture. Want to know what is still out there that comes in those directories? Well, with this /etc/swaret.conf, there are only packages from the official mirrors, so use this command:

swaret --list|most

Lots of good programs.

Code:
############################################################
#
# swaret.conf, Version: 1.6.2
#
### /etc/swaret.conf - SWARET EXAMPLE CONFIGURATION FILE ###
#
# Define a valid Slackware Linux Version.
# (Used for Dependency Support and other Features)
#
# NOTE: If you want to use Slackware Linux Current,
#       set VERSION to 'current' (VERSION=current).
#
VERSION=current
#
# Define the language for status and error messages
LANGUAGE=ENGLISH
#
# ----------------------------------------------------------
# Define Slackware (8.1 or Higher or Current) Linux Mirrors.
# (Used for Official Slackware Linux Packages)
# (Slackware Linux Mirrors available at http://www.slackware.com)
#
# Syntax: ROOT=PROTOCOL:URL
#
# NOTE: swaret will use the order of the specified ROOT URL's.
#
#ROOT=file:/mnt/cdrom
#ROOT=file:/mnt/dvdrom
#ROOT=file:/mnt/usbmemstick
ROOT=ftp://ftp.nluug.nl/pub/os/Linux/distr/slackware/slackware-$VERSION
ROOT=http://sunsite.cnlab-switch.ch/ftp/mirror/slackware/slackware-$VERSION
ROOT=ftp://ftp.slackware.no/pub/linux/slackware/slackware-$VERSION
ROOT=http://www.slackware.no/slackware/slackware-$VERSION
ROOT=ftp://ftp.slackware.at/slackware-$VERSION
ROOT=http://www.slackware.at/data/slackware-$VERSION
ROOT=ftp://ftp.planetmirror.com/pub/slackware/slackware-$VERSION
ROOT=http://ftp.planetmirror.com/pub/slackware/slackware-$VERSION
#ROOT=rsync://rsync.slackware.no/slackware/slackware-$VERSION
#ROOT=rsync://rsync.slackware.at/slackware/slackware-$VERSION
#ROOT=file:/pub/slackware
#ROOT=file:/mnt/nfsshare/slackware
#ROOT=file:/mnt/sambashare/slackware
#
# -----------------------------------------------------------
# Define Repository URL's with Slackware Linux Packages.
# (Used for Repository Slackware Linux Packages)
# (Repository URL's available at http://www.swaret.org/?menu=sp)
#
# NOTE 1: To use a Local Repository or Remote Repository,
#         be sure it contains the following Files:
#         - CHECKSUMS.md5 (For MD5 Sum, REQUIRED)
#         - FILELIST.TXT (For Package Name + Size, REQUIRED)
#         - PACKAGES.TXT (For Package Description, NOT REQUIRED)
#         - MANIFEST.bz2 (For Dependency Support, NOT REQUIRED)
# NOTE 2: To create your own Repository, use 'swaret-tools'.
#         You can get 'swaret-tools' at http://www.swaret.org!
#
# Syntax: REPOS_ROOT=REPOSITORYNAME%PROTOCOL:URL
#
# NOTE 1: The REPOSITORY NAME can only be ONE Keyword!
# NOTE 2: swaret will use the order of the specified REPOS_ROOT URL's.
#
#REPOS_ROOT=LinuxPackagesDOTNET%ftp://ftp4.linuxpackages.net/pub/Slackware-9.1
#
#REPOS_ROOT=My_Slackware_Packages_On_CD-ROM%file:/mnt/cdrom
#REPOS_ROOT=My_Slackware_Packages_On_DVD-ROM%file:/mnt/dvdrom
#REPOS_ROOT=My_Slackware_Packages_On_USB_Memory_Stick%file:/mnt/usbmemstick
#REPOS_ROOT=SomeRemoteRepository%ftp://ftp.someremoterepository.net/s.../slackware-9.1
#REPOS_ROOT=SomeRemoteRepository%http://www.someremoterepository.net/.../slackware-9.1
#REPOS_ROOT=SomeRemoteRepository%rsync://rsync.someremoterepository.net/slackware/slackware-9.1
#REPOS_ROOT=MyLocalRepository%file:/pub/myrepos"
#REPOS_ROOT=MyRemoteRepository_Using_NFS-Share%file:/mnt/nfsshare/slackware
#REPOS_ROOT=MyRemoteRepository_Using_Samba-Share%file:/mnt/sambashare/slackware
#
#   Here's some Repositories that I added
#
#REPOS_ROOT=DiffieTgzs%http://www.blazebox.homeip.net:81/diffie/slackware
#REPOS_ROOT=BlazeBox%http://users.lichtsnel.nl/pub/slackware
#REPOS_ROOT=SlackPack%http://packs.slack.it/
#REPOS_ROOT=GurnoDOTCOM%http://gurno.com/adam/slack/
#REPOS_ROOT=TcheLinux%http://slackpacks.tchelinux.com.br/ 
#
# ------------------------------------------------------------
# Define Libraries (8.1 or Higher or Current) List Mirrors.
# (Used for Dependency Support)
#
# NOTE 1: You need to specify a Libraries List Mirror which
#         contains a 'libraries-VERSION' File.
#
# NOTE 2: To create the Libraries List, use 'swaret-tools'.
#         You can get 'swaret-tools' at http://www.swaret.org!
#         You can also clear all DEP_ROOT Variable(s) which will
#         allow swaret to create the Libraries List for you
#         during Dependency Check using the defined ROOT Variable(s) above.
#
# Syntax: DEP_ROOT=PROTOCOL:URL
#
# NOTE: swaret will use the order of the specified DEP_ROOT URL's.
#
#DEP_ROOT=file:/mnt/cdrom
#DEP_ROOT=file:/mnt/dvdrom
#DEP_ROOT=file:/mnt/usbmemstick
DEP_ROOT=http://swaret.sourceforge.net
#DEP_ROOT=ftp://ftp.swaret.org/swaret
#DEP_ROOT=rsync://rsync.swaret.org/swaret
#DEP_ROOT=file:/pub/swaret
#DEP_ROOT=file:/mnt/nfsshare/swaret
#DEP_ROOT=file:/mnt/sambashare/swaret
#
# ----------------------------------------------------------
# General Settings
#
# Do you want swaret to use Random Slackware Linux Mirrors?
# -> 1 for yes, 0 for no.
#
RANDOMR=1
#
# Do you want swaret to parse all the Package Descriptions?
# -> If set to 1, swaret will also match Packages whose Description
#    is matching the Keyword(s) you specify after --ACTION.
#    NOTE: swaret will parse all the Package Descriptions for this,
#          and might slow down swaret when using an older System.
# -> If set to 0, swaret will not use Package Descriptions 
#    to match one or more Packages.
#
USEPKGDESC=0
#
# If you don't want swaret to Upgrade, Install, Re-Install, Download,... 
# some Packages, add the KEYWORDS to the EXCLUDE Variable.
# To disable Exclude Method: swaret --exclude -off
# To enable Exclude Method: swaret --exclude -on
#
# NOTE: You can add ANY EXTENDED REGEXP (Regular Expression) to the EXCLUDE Variable(s)
#
# Basic Exclude
#
EXCLUDE=kernel
EXCLUDE=lilo swaret
EXCLUDE=MANIFEST.bz2$
EXCLUDE=.*dl$ .*PACKAGER$ .*MYBUILD$
#
# Advanced Exclude
# Syntax: KEYWORD[DONT_EXCLUDE_ME_KEYWORD1,DONT_EXCLUDE_ME_KEYWORD2,...]
# Example: kde-i18n[nl,en_GB] koffice-i18n[nl,en_GB]
#
EXCLUDE=kde-i18n[nl,en_GB] koffice-i18n[nl,en_GB]
#
# Do you want to enable Dependency Check?
# -> If set to 1, swaret will start the Dependency Check after 
#    every Upgrade, Install and Re-Install Procedure.
# -> If set to 0, swaret will not start the Dependency Check 
#    after any Procedure.
#
DEPENDENCY=1
#
# Do you want swaret to Search for missing Libraries (and Fix) 
# which could be found on your System, but not tracked by ldconfig?
# -> 1 for yes, 0 for no.
#
DSEARCHLIB=1
#
# Set to 1, if you want swaret to use the 'slocate' program
# to Search for missing Libraries.
# (be sure to issue the 'updatedb' Command regularly!)
# If DSEARCHM is set to 0, swaret will use 
# the 'find' program to locate missing Libraries.
# -> 1 for yes, 0 for no.
#
DSEARCHM=1
#
# Start MD5 Check after Fetching Packages, Patches and Sources?
# -> 1 for yes, 0 for no.
#
MD5CHECK=1
#
# Start GPG Signature Check after Fetching Packages, Patches and Sources?
#
# NOTE: Check out F.A.Q. (--faq gpg) how to Import a Public GPG Key which
#       will be used by the GPG Signature Check.
#
# -> 1 for yes, 0 for no.
#
GPGCHECK=0
#
# Show Description for Packages during
# Upgrade, Install, Re-Install,... Procedures?
# -> If set to 0, you will not see a Description.
# -> If set to 1, you will see a Description.
#
DESC=0
#
# Cache Directory for (Repository) Packages and Sources.
#
CACHE_DIR=/var/swaret
#
# Enable Logging?
# -> 1 for yes, 0 for no.
#
LOG=1
#
# swaret Log File
#
LOG_FILE=/var/log/swaret
#
# Show Warnings?
# -> 1 for yes, 0 for no.
#
WARNINGS=1
#
# Show Information?
# -> 1 for yes, 0 for no.
#
INFORMATION=1
#
# -------------------------------------------------------------
# Network Settings
#
# Network Interface
# Use this if you have a Network Interface.
#
NIC=eth0
#
# Local Interface
# Use this if you do not have a Network Interface.
#
# For Example (CD-ROM):
# You got a Slackware Linux CD-ROM,
# mount the CD-ROM to /mnt/cdrom and
# set ROOT to 'file:/mnt/cdrom' in /etc/swaret.conf.
# Also, set NIC to 'lo' (Local Loop Device).
#
# NIC=lo
#
# Progress
# If set to 0, swaret will use the '%' Download Interface.
# If set to 1, swaret will use the 'size' Download Interface.
# If set to 2, swaret will use the 'wget/rsync' Download Interface.
#
PROGRESS=1
#
# Timeout for wget and/or rsync.
# -> Number of seconds for Timeout
#
TIMEOUT=35
#
# Retries for wget and/or rsync.
# -> Number of Retries
#
RETRIES=5
#
# Behind a Firewall? Using FTP Mirrors?
# -> 1 for yes, 0 for no
#
PASSIVE_FTP=1
#
# If you want HTTP or FTP Proxy Support,
# uncomment and Setup the following Variable:
#
# WGET_PROXY=http://IP or HOST:PORT
#
# If you want RSYNC Proxy Support,
# uncomment and Setup the following Variable:
#
# RSYNC_PROXY=IP or HOST:PORT
#
### /etc/swaret.conf - SWARET EXAMPLE CONFIGURATION FILE ###
 
Old 09-06-2004, 07:57 PM   #9
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Original Poster
Rep: Reputation: 30
Wow! Thangew! I shall give it a try...
 
Old 09-08-2004, 12:17 PM   #10
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Original Poster
Rep: Reputation: 30
Success! Thank you Shilo, for your generous help. Our swaret.conf files were remarkably similar already - I added the repositories you did, but left them commented out. Out of curiosity though, why this?:

Do you want swaret to use Random Slackware Linux Mirrors?
# -> 1 for yes, 0 for no.
#
RANDOMR=1

Also, there were very few ".new" files (only about 5) that I had to take care of... I renamed the old files to ".old" and replaced them with the new ones.

Now to get to work on that printer and a graphical lilo...

Thanks!
 
Old 09-08-2004, 12:37 PM   #11
shilo
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: Reputation: 50
Quote:
Out of curiosity though, why this?:

Do you want swaret to use Random Slackware Linux Mirrors?
# -> 1 for yes, 0 for no.
#
RANDOMR=1
That way, you use a different mirror every time, radomly chosen. Everyone starts out with that same list of mirrors in swaret.conf. If they all don't use the random mirror feature, they are gonna hit the first one in the list first, then the next if the first didn't work, etc. THis will cause sever congestion. Better to use random servers.

Quote:
I renamed the old files to ".old" and replaced them with the new ones.
You might want to manually check out the difference between those files. diff is your friend. Just blindly replacing the config files can lead to trouble. IT's usually OK in the beginning, since your config files haven't changed much, but later, it starts to be a real bad idea.
 
Old 09-08-2004, 01:29 PM   #12
noxious
Member
 
Registered: May 2004
Location: Ohio, USA
Distribution: LinuxMint Gloria, Ubuntu 9.10
Posts: 299

Original Poster
Rep: Reputation: 30
I understand about the server congestion... always a problem with up2date in FC2.

I felt safe renaming and replacing the old files with the ".new" ones since I hadn't tinkered with the files yet... I will be more careful as Slackware ages.

I even got the networked windows printer to work! Now for that graphical lilo...

I like Slackware better than any other distribution so far... less conflict issues, and everything seems to install in a working state right off the bat! There's just a bit of a learning curve and an adjustment in outlook to get over at first.

Thank you yet again!
 
Old 09-08-2004, 02:08 PM   #13
Smokey
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 313

Rep: Reputation: 30
the old version of swaret wont automatically resolve dependencies, that was your problem...you either need to edit the file to change its website to http://swaret.sourceforge.net or get the test package from swaret that already has this... then run a 'swaret --dep'
 
Old 09-08-2004, 06:48 PM   #14
catlion
LQ Newbie
 
Registered: Sep 2004
Distribution: Slackware 9.1
Posts: 6

Rep: Reputation: 0
noxious

Have you installed X.org? If not, you MUST do this because it have new libxinerama needed by GNOME.

I had the same problems when upgrading gnome from the sources...
 
Old 09-08-2004, 07:58 PM   #15
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 52
Quote:
Originally posted by noxious
Success! Thank you Shilo, for your generous help.
He did it
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
gnome problem after swaret upgrade munkie_poo Slackware 3 11-03-2004 12:55 PM
swaret upgrade from 9.1 to 10? virii Slackware 5 07-16-2004 02:16 PM
After swaret --upgrade -a....... Mingthefirst Slackware 2 07-09-2004 02:42 AM
Upgrade of Slack Gnome to current via swaret justaguynsrq Slackware 8 04-07-2004 06:38 AM
problem with swaret after a big upgrade Quartzophobia Slackware 5 02-17-2004 02:24 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:11 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration