Slackware :: Upgrading KDE From 4.2 To 4.3 (64bit)
Mar 30, 2010
I'm trying to upgrade KDE from 4.2 to 4.3 since I encountered couples of problem with it and some people suggested me to upgrade it to 4.3.
Questions:
1. Is KDE 4.3 available in 64 bit?
2. KDE consists of bunch of packages, what is the best way to start? Should I uninstall the whole current packages in my machine and then install the new ones?
3. Using pkgtool, how do I know if I remove the whole KDE packages? Are all KDE packages named that begin with word "KDE"?
4. How to do this safely so to avoid corrupting the system?
I had downloaded a DVD disk with Fedora 12 on it (~3.7 gig) therabouts. I used it to upgrade my F11 system to F12 or so I think. Well to make a long story short, it had installed approx 1435 files on to my computer. I never so it finish up the process because my moniter timed out and I could get it back on after it had blanked out. So I rebooted the computer (after I had removed the DVD). It showed F12 booting up but the splash screen with logon was F11's. After I logged on my nvidia driver was gone along with compiz and Avant. So I followed 'leigh123linux' response on 'Nvidia' and get it reinstalled and working along with Avant, and compiz and my rotating cube desktop. I did a yum clean to cllean up the packages and ran yum update again to refresh what may have not been installed. It show a couple hundred packages needed to be upgraded and also had alot of 'dependency' errors' for a lot of the packages. That's where I stand now. Is it 11 or still 12? Did the DVD upgrade work? Who nows.
I have 90 + clients running Fedora 12 on a beefy i7 machines used for various reasons. The configuration is as follows:
HD = 1 Terabye with the following partition setup: 200 Meg for /boot 60 Gig for / 844 Gig for /opt
Users authenticate using NIS and have their home dirs auto mounted as well as others directories.The issue on hand:
1) We want to move up to Fedora 14 (since 12 is no longer supported).
2) The first hurdle is working around the 200 meg boot partition. Does anyone know of a process which can be automated for this? Currently, I was able resize a client by decreasing the root to 59 gigs and boot to 1.2 gigs through the use of gparted.
3) Is there a utility which will allow me to deploy this using a utility/script on all the clients?
4) Ultimately I want to automate the process without having to touch each machine.
When I was trying to upgrade my fedora 13 system to fedora 14 through preupgrade,there was an error message as show below: Cannot retrieve metalink for repository: fedora. verify its path and try again How to upgrade my system to fedora 14.
I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
Has anyone tried upgrading the BIOS on Dell laptops? This is the Dell Windows based update for my Studio 1558 laptop. [URL] Would this work using Wine? Is there a Fedora way to apply this update?
I'm having problems upgrading my FF browser from the standard 3.5 up to 3.6. This is a 64bit system, & if I can provide any other info about it, just ask.I've searched this forum for the help I'm looking for, but I have not yet seen an acceptable answer. If this has glitches, or is too complicated, I won't even bother....3.5 is fine for now, but it would be nice to upgrade.
I am going to upgrade from Lucid 32-bit to Lucid 64-bit, and I have some questions as to what I need to do. My system is a dual boot of XP and Lucid, but I only use XP rarely nowadays. I know I have to do a clean install, so here goes. Do I have to blow away my current install of Lucid? If the answer to (1) is yes, what about Grub? How do I get a list of my currently installed applications?
Currently Lucid is on one partition. I have a Clonezilla copy of the file system. Can I restore the /home directory from that copy once I have installed the 64-bit system? If I decide to make /home a separate partition, are there any good rules of thumb about how much space to allocate to the various partitions? Are there any other directories or files I should consider copying from the Clonezilla copy?
I've upgraded Slackware-13.1 I had installed to Slackware-Current using a local tree I had download with mirror-slackware-current.sh script, but when I rebooted I could not get the graphics to load. I think it's because I've also modified /etc/groups and add an username after audio: and video: group, but I forgot that and had to remove slackware from the machine.
I have installed multilib support in my 64bit slackware 13.37 installation than I proceed it to install google earth from slackbuilds... and did ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3Now when I try to run google earth I get:[ 760.092745] googleearth-bin[3647]:segfault at 984f7d31 ip 00000000984f7d31 sp 00000000ffbfe100 error 4
using Slackware 13 64bit, 2.6.29.6-smp, KDE desktop. i installed the flash-player-plugin using sbopkg. when i try [URL], it says i'm missing the flash plugin. i copied the. so file to
I bought a new laptop HP Pavillion dv3-4170ee that has Core i5 2.53ghz dual core with hyper threading, intel hd graphics and Ati Radeon HD 5470 512 mb dedicated. It came with windows 7 64bit. It also has 6 gb ram(2gb in first slot + 4 gb in the second one).I installed slackware 13.37 64 bit. It installed just fine. installed lilo onto mbr. When it boots up it shows the slackware screen. I am able to boot into windows just fine. When I select Linux it boots into linux bios data check successful. lots of stuff goes on the screen the normal linux boot stuff. and then it goes to the next screen and stays blank
Nothing happens and even the hard disk light is not blinking.By the way the HDD is Western Digital.
1: How much does it affect securty, over a lan network? 2: Will it cause any other security issues? 3: The most important is can I forwad X11 from a 32 bit slackware to a 64bit slackware
Some time in the past after upgrading from one version of Slackware to another, I remember having issues using the previous version's .kde directory. This was remedied by removing that directory and letting KDE recreate it followed by me painstakingly migrating files one by one to get all my settings, mail, etc. under the new version of KDE. Is this the case with the upgrade from 13.1 to 13.37 and is there a better way that I'm missing?!
I have a few systems (linux boxes and windows boxes) that are currently 32bit hardware systems with 32bit OS installed and running. These systems are HP desktops pc with intel pentium chipset, Dell desktop pc with AMD chipset, IBM xSeries servers with intel pentium chipset. But now I want to upgrade all these systems (workstation/servers) to 64bit OS, but need the 64bit supported hardware. Is there "possibly" any way to work around this 32bit hardware systems and make them ready to accept 64bit OS?
I have some doubts about the official Pat's upgrading procedure. In the UPGRADE.TXT file, one of the stepts says:
Code: upgradepkg --install-new *.t?z What does --install-new mean? Pkgs I have no installed on my 13.1 will be installed on the 13.37 upgrade? For example, I did not installed KDE on 13.1. Will be installed when upgrade? - What about third party pkgs? Slacky, SlackBuilds.org, compiled by myself. Should I remove them before upgrading slack?
After upgrading I also updated abiword and wv from slackbuilds.It complains it can't find libwv-1.2.so.3, although libwv-1.2.so.4 exists.Making a symbolic link gets it to start, although then it complains about libpng and hwile it starts the toolbar icons are not displayed, instead with red X's in their place.What is needed to get abiword easily working on 13.1?
procedure or instructions on how to reinstall the X server or upgrade it to the latest? Every time I played around with X I screwed up things good... I think it got corrupted and I have display problems that I cant fix, so far everything points to a software problem, probably X server...If you need more background info:
1. Upgrade the kernel and kernel-modules packages normally.
That sounds simple except that day-to-day, I don't run a stock Slackware kernel. I compile and run my own and always have. As I look back on my history with Slackware, I don't think I've ever upgraded kernel packages once I got a system up and running. When there's been big changes (2.4 to 2.6, for example), I've done a full re-install.
Most recently when I made the jump to 64bit, I did a full install using the huge.s kernel and once everything worked, I downloaded the current source from kernel.org and was on my way. I haven't booted huge.s since that day.
I do, of course, know how to upgrade my own custom kernel, but I like having huge.s installed as a backup. If I upgrade gcc/glibc, compile a new custom kernel and update lilo.conf/fstab without upgrading huge.s, then I will be left with only one working kernel.
So, my question is: is it simply a matter of running upgradepkg on the 6 kernel packages (headers, modules, firmware, generic, huge and source)? or is there more to it than that..ie, what about the system maps and symlinks in /boot?
I'm looking at running -current instead of 13.1, and wondering about 'upgrading' to -current, as well as running multi-lib. I found the following procedures from another post of about a year ago, but I'm not sure from what directory to run such a script:
Should the procedures above work for me? and although I know that things may occasionally break here and there (and get fixed too), are there any known issues right now that would break things on my machine?
after i update to -current a few days ago. my slack partition cannot be mounted...and after that it's show 'kernel panic'.before i experience that problem, i have encounter an odd problem after i update my slack to -current, after i lock my screen and i want to unlock it, i cannot unlock it, it says 'i must kill kscreenlocker manually'. After that i reboot using root account. then i cannot enter my slackware again.kernel panic in boot screen.Kernel panic: VFS : Unable to mount root fs (8,2)
i am runnin slackware 64 bit and trying to install eiskaltdcpp. i am new to slackware and i dont understand how it should be installed. i have found the eiskaltdcpp-2.1.1-i486-1sl.txz package but it seems it is not for my arch. i also cant find all the dependencies.
just wondering has anyone gone through ATI Radeon HD 4830 with Slackware 13 64bit, can it be recognized correctly by HAL with built-in open source radeon drivers or it should be installed with fglrx.
i am trying to install Slackware 13.1 64bit on my HP Desktop. right now i am writing from a debian.
on the installation they ask me if i want to setup network right now.. when i press "yes" they need: name, domain, proxy etc... what is that things? :S slackware create new connection that i am going to pay extra? (pay extra money for that connection slackware create?) if i press "No" after the log in my network is not working..
my Questioni is: while i am complete the boxes on network setup (name,domain etc) slack creates new internet line that its going to pay? or not?
I've recently upgraded from Slackware 12.2 to Slackware 13.0 and so far everything works fine with one exception: the TightVNC package that comes with Slackware-13.0 (in /extra) produces a garbled desktop. Applications look fine, but the default desktop of 13.0 is corrupted. Restarting the VNC server doesn't solve the problem. Before the upgrade, I had 1.3.9 compiled from source. I have just installed the 1.3.10 package that came with Slack-13.0 on top of what was there, hoping it would overwrite old files as needed (couldn't find an automatic uninstall procedure for 1.3.9).
I have attached a printscreen. Notice the taskbar and the top left quarter of the screen. Firefox seems to be rendered properly though. Has anyone encountered this before or may have a clue what could be causing it?
