I followed all the instructions in the UPGRADE.TXT to upgrade Slackware 12.2 to 13.0. After I completed it, I ran
Quote:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
It started installing 12.2.
I have a brand new Slackware 13.1 x64 installation, and I'm having problems with slapt-get.
I'm unable to upgrade existing packages or install new ones. The output in terminal is:
Code:
bash-4.1# slapt-get -i tar
Reading Package Lists... Done
The following NEW packages will be installed:
tar
[Code]....
Worth mentioning also, I managed to install Gnome from [URL] without any problems immediately prior to this error message starting to appear.
I've been using Debian and Ubuntu derivatives for the last couple of years, so I'm comfortable using the terminal and possibly doing some more advanced stuff.
I recently upgraded to slackware-current from Slackware 13 via slackroll, and have only encountered one problem. My file manager no longer thumbnails images, and icons (mostly PNG) aren't appearing no matter what GTK theme is set. Running from the command line produces no errors, and when brought up in something else (say feh /path/to/icon.png) it works perfectly. This is the only hitch I have encountered so far. The same thing happens with emoticons in Pidgin. Does anyone know of a fix?
View 5 Replies View RelatedI am trying to upgrade from 10.4 to 10.10. I have never had a problem upgrading before with the Update Manager. Now I get an error message when using the Update Manager. The message says, "Could not calculate the upgrade". See screenshots. I also checked the package manager for broken packages and came up with nothing.
View 2 Replies View RelatedI started a thread asking for advice in the hardware forum. I didn't want to post a duplicate thread, but I was unable to get it moved here, so I'm kindly asking you slackers to help me install the aforementioned driver.
View 1 Replies View RelatedI use Alien Bob's mirror-slackware-current.sh with an excludes.txt to only download the parts of current that I want. Unfortunately it is not working for part of the exclude.txt file and I am at a loss to know why.
The excludes.txt is
Quote:
slackware64/e
slackware64/f
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txt
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txz
[code]...
This ignores e/ f/ y/ testing/ pasture/ source/ and usb-and-pxe-installers/ It also ignores most of kdei/ and /extra It is meant to ignore most of extra/source and just download the source for flash-player-plugin, but it is ignoring all of extra/source/, however the same syntax is working for kdei/ and extra/.
I've a multiboot machine and I recently installed Slackware64-13.1 on sda33. I added menu entry in SUSE boot loader and configured menu list as per [URL].. it returns GrUB error 15. Here is my menu list entry for Slackware -
Code:
###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
root (hd0,32)
kernel /boot/vmlinuz root=/dev/sda33 ro hdd=scsi
savedefault
[Code]...
How to upgrade to 13.1 ?
View 1 Replies View RelatedHow do I completely update KDE to the latest version?
I really haven't figured out what to download, what to compile etc. etc. And I don't wanna mess up my GUI...
I'm using Slackware 13.1 and don't want to renew the installation for 13.37 but just upgrade from one to the other.
View 8 Replies View RelatedI tried to upgrade from 12.2 to 13.1 using slackpkg but, by some reason, it did not upgrade and bash gave me error at any command I tried to use. I tried to use the boot CD but still, I couldn't use chroot. Desperately, I mounted the hdd partition into a directory and I installed all the packages from slackware/a directory (with --root /mnt/disk option). Surprisingly, I rebooted and the system successfully loaded the new kernel. Since I installed only the "slackware/a" packages, I would to know which would be the next step to fully upgrade the system. I intend to upgradepkg all the directories from dvd "slackware". Is this a good solution? If yes, which should be the next packages that should be upgraded: "slackware/l", "slackware/ap", "slackware/d" ?? I'm interested in the order of the directories that should be installed.
View 3 Replies View RelatedI have slackware 13.0.0.0 64bit that comes with KDE 4.2.4 installed and I want to upgrade its KDE to version 4.4.1. Since I'm new in Linux world, much less in KDE, I don't know what is the best way to do this. Should I uninstall the current version, and install the upgraded packages?
Is "view" menu of pkgtool shows installed packages or shows all available packages in Slackware build? How do I now which KDE packages that are currently installed?
Anyone built the latest release?
Here's the source: ftp://ftp.mozilla.org/pub/mozilla.or.../3.5.6/source/
Security Fixes: http://www.mozilla.org/security/know...l#firefox3.5.6
I'm currently downloading the source and will build and report back how it goes.
is there a way to upgrade from 13.0 using slackpkg or something more simpler?
View 14 Replies View RelatedI have upgraded from 13.1 to 13.37 on three PCs. No problems on 2 of these (home server and laptop), but on the third machine (main Desktop, where most KDE customisation had been done of course), KDE refuses to start for the main user (me). It will start OK for root and xfce will start OK for me, so X is OK with the updated NVIDIA driver that I have also installed. The KDE splash screen starts up and four of the five splash icons come into focus, but the fifth one never does. Some disk rattling goes on for a while but then ceases.
I have tried renaming the .kde folder and .kderc but this has not helped. Are there other KDE config files that I could try renaming / removing? Or are there log files / error messages somewhere that I should consult.
Obviously I am not in a position to change any KDE system settings from the KDE application.
Just tried KDE with a newly-created user and it's the same as with my user - no desktop. So KDE is only starting for root.
I decided to upgrade from Slackware64 13.0 to 13.1 using slackpkg. I did a slackpkg install-new and afterwards, upgrade-all. My first problem was solved regarding libblkid. The second one, with DIALUPS_CHECK_ENB and NOLOGIN_STR was solved too. Now, when booting, the system says it can't find /sbin/mount, swapon, hwlock and fsck, and also /proc/filesystems and /proc/ioports. It asks for the root password for maintenance and boots again afterwards. Do you have any idea what should I look for, because the mentioned /sbin/_files _ are at /sbin ?
View 1 Replies View RelatedI'm using Slackware 13.1_64 with multi-lib. Now that 13.37 is out I would like to upgrade my system but thought I would ask if there are any problems or considerations for upgrading multi-lib systems ?
View 1 Replies View RelatedI recently installed Slackware-13.37-RCpi on a production machine. In view of the many changes since then, will the upgrade to 13.37-stable, when it comes to the world, be as easy as syncing the local mirror with slackpkg and re-running lilo? What worries me is that there were changes of the kernel and the headers and I am afraid there might be some pitfalls associated with that. Will I need to recompile the packages I compiled and installed on the stock 13.37-RCpi?
View 3 Replies View RelatedI just installed slackware 13.1 and my KDE is version 4.4.3, I want to upgrade to version 4.6.1 or at least 4.6.0. I have used alien repository and download KDE 4.6.1 but it doesn't work.
Are they any options to upgrade my KDE to 4.6.1 or not?
Is there a way to upgrade Slackware 12.2 to 13.37 without having to download the new iso and making a new install? 'how to' Id like to read it. Or even a simple way to do a minimal install and then add the extra applications.
View 14 Replies View RelatedI installed Slackware 8.1 thinking that it was the earliest version to support flash drives (based on some forum discussions I had read), but then discovered Wiki info on flash drives which states that the 2.6.2 kernal is the first kernal to support them. Is it possible to load 2.6.2 into Slackware 8.1 or does this following link the highest kernal I can go with 8.1? [URL]
View 4 Replies View RelatedI had been running Slackware64 13 almost since it came out and recently upgraded to Slackware64 13.1.Every thing looked to be working well until I tried to burn a DVD with k3B. It starts the burn process but then dies and says that "cdrecord has no permission to open the device".I was able to put in a DVD+RW and erase it without a problem, but when trying to burn to a DVD-R it stops and gives me the error.I checked cdrecord and it is owned by root in the root group.
View 11 Replies View Relatedi have upgraded my desktop from 13.0 to 13.1 and the font rendering suffered big time (did the same procedure on the laptop but no problems there). anyway, the fonts on kdm are really bad as well as konsole and firefox. other qt apps don't seem too bad but should be much better. xterm and xmobar don't seem to be affected at all. the machine is running the 13.1 sbo of nvidia drivers.
i have tried a few things: playing with the anti-aliasing settings in kde control center (all the settings offered differnet level of 'badness' and no 'goodness') and trying to use the settings in the nvidia control panel but that didn't seem to have any effect.
I wanna upgrade one of my 13 installs to current and was wanting any tips, etc and whether I should do it?
View 7 Replies View RelatedPeople, there is a tutorial to upgrade the kernel 2.6.38.3(compiling tutorial included =D) to Slackware 13.1??And, this upgrade generate a better performance on system??
View 14 Replies View RelatedI burned the Slackware 13.1 DVD disk, and installed on a desktop, and it worked really great. Now, I would like to install 13.1 on my laptop, but my DVD-rom doesn't work. So is there any instruction for me to upgrade from slackware 12.1 (currently running)to slackware 13.1 directly, like what states in "Slackware 13.0 to 13.1 Upgrade HOWTO" ? Alternatively, is there any way that I can install slackware 13.1 from the ISO image file on my Windows partition? or I just following the instructions off this website, [URL]
View 1 Replies View RelatedSo I did an update to my slackware current and as many people here found that KDE crashes... Mine I am unable to find a fix for it.... I get the following error as I log in...
Warning Can not Open ConsoleKit Session Unable To Open Session: Failed To Connect to Socket: /var/run/dbus/system_bus_socket: No Such File or Directory.
I've been messing around with this for a while trying different mesa packages so far none of them have resolved the issue. XFCE, Fluxbox all work however kde wont load for some reason. Ive even tried using the drivers direct from dell as this is a poweredge t310.code...
View 3 Replies View RelatedI am using slackware-current 32bit version. After upgrading from kde 4.2.4 to 4.3.4 (using slackpkg), all my K-menu icons were missing.
There are also no icons in task managers for all kde-based applications like konsole,dolphin etc.. But for non-kde application like firefox, wicd and xmms, the icons show up in task manager. I have tried reinstalling kdebase, kdebase-runtime and kde-userspace with no luck.
One partition of my pata drives is not recognized anymore after upgrade. Using fdisk the partition is seen but just 33,8 GB of the 205 GB drive is recognized at all.
Quote:
root@7of9:~ >>> /sbin/fdisk -l /dev/sdd
Disk /dev/sdd: 33.8 GB, 33820286976 bytes
255 heads, 63 sectors/track, 4111 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[code].....
The filesystem is ok. Booting Slackware 12.2 the partition is recognized and mountable. why /dev/sdd4 is not recognized by Slackware 13.1?