Slackware :: Could Not Start KDEinit4 - Check Installation
Jan 9, 2011
So I closed out X with ctrl+alt+backspace, and when I did startx it showed the Nvidia splash screen like usual, then shows for just a second that loading splash screen that KDE does. Then a little box pops into the top left corner that says "Could not start kdeinit4. Please check installation." I hit okay on the box, it takes me back to the terminal. I try again, same result. I reboot. Same result. So I use xwmconfig to change to enlightenment, which boots up fine. So I ctrl+alt+backspace out and retry KDE again, with the same problem.
This is the first time I've closed out KDE in over a week, so I guess its possible that anything I've done over that time may have somehow broken it. I hadn't noticed any problems til now. The only reason I did it this time was because I'd changed the KDE plasma theme and I wanted to watch the new one boot up. I'm typing on the same computer and the same Slackware installation right now, just running E instead of KDE.
KDE update a number of components in tonights update. When I have gotten this error the past I could simply delete the .kde folder in my home directory and KDE would rebuild one and start. Doesn't work this time.Am I missing something or has something failed to download and install properly
I am using opensuse 11.3. I am encountering a problem while trying to log in. The problem message was "could not start kdeinit4. Check your installation" I tried to solve this problem by following the instructions given in OpenSuSE 11.0 Could not start kdeinit4... i.e., I opened yast2 and then I had to select "software management" from there in order to update all the packages in kde4. But I got another error when I clicked it.
/usr/lib/YaST2/bin/y2base:/usr/local/lib/libstdc++.so.6: no version information available (required by /usr/lib/YaST2/plugin/libpy2wfm.so.2)
The error list continues. I cannot type whole error list ending with similar wordings as above as am using different computer. I tried to solve this one too by following the instructions in Relocation Error but I could not understand its line "...fixed the problem by taking /usr/local/lib out of ld.so.conf, and then running ldconfig" as am new to linux.
There are thousands of threads in the Internet about kdeinit4 problem and I searched them for a solution but all I got is: it's a bug, accept it. There is this solution here and I added
Code: [DirWatch] PollInterval=60000 as plamaiziere said, but this changed nothing.
So kdeinit4 loads my CPU 100%. Maybe someone has figured out how to prevent this from happening? I use IceWM but have KDE fully installed because I use a lot of apps from KDE group.
I foolishly changed the mount point of a partition on a HDD which Linux was not in fact using, and now when I try to start up I get a message box stating:- Could not start kstartupconfig. Check your installation.
How do I recover the situation. I do not have an up to date recovery disc. I do have a full bootup disc of Suse 11.2 - could I use the opportunity to update without losing all my personal files, or should I use the old 10.2 disks? The first essential is to get something back up and working.
Im trying to get away from the world of M$ into linux and I think slackware is the way to go for me. In particular SW13-64bit. My question is though I dont see many hardware manufacturers supporting SW, but I do see suse and redhat. How hard/possible is it to use redhat suse drivers for slackware? Can they be modified/rebuilt?
Im also considering buying a cheap server off ebay to use. Can someone let me know if any of the following would cause an issue with slackware?In particular the Adaptec sata raid controller which I want to run in raid 5.
My configuration is OpenSuSE 11.4/KDE4/32bit. I am noticing that for about 20 minutes (or more) after first login every time there is a process which takes 100% CPU for most of the time and, of course, slows everything down. The system monitor suggests it is the 'tracker-miner' process (whatever that is). Do I need the tracker-miner? What good does it do? Is there any way to stop it (not to start it)?
When my system starts this command is executed by a script /usr/sbin/apache2 -k start...How can I find which one start it? I check in rc2.d/ dir in the apache script but didn't found anything similar. Where else should I look?
When I start the computer I receive the message that the drive that contains the /home partition has an error. If I press "F" the screen says that the drive is no ready, that I can wait, cancel or manually recovery. If I wait, in about 1 minute, the system starts normally. If I press "M" to repair manually, then I press fsck to repair the disk and apparently repairs the disk. But everytime I start (power on) the computer, Ubuntu always checks the disk and gives a dialog where I can: press F to attempt to fix the errors, I to ignore, S to skip mounting or M for manual recovery
unclean shutdowns/reboots. Whenever I boot/restart, I notice the message "/dev/hdb1 (and hdb2) was not cleanly unmounted, check forced." Then fsck(?) scans them without errors, and everything continues normally. FWIW, hdb1 @ hdb2 are ext2, /boot & /tmp respectively, whereas all other partitions are ext3. Could that (ext2) be why? I checked halt, reboot, umountfs, umountnfs.sh, and umountroot in /etc/init.d, and nothing jumped out at me, though I'm not exactly sure what I'm looking at/for.
I am using Sphinx search on my webserver and it quits after a certain amount of time leaving my search page broken.Here is a bash script that I want to run every 10mins via cron:
dd is wiping part of the hard drive( 270GB partition ) with /dev/urandom for quite some hours, is there anyway to check the proccess? like speed of the process etc., I read someone doing that with another drive while having access to other terminal because of the system, but since this is directly from the install dvd, I've no clue if there's anyway to do that or not. I'm asking that mainly because:
1) I prefer run things with some kind of verbose mode
2) I accentaly opened the dvd driver (yes I know, but I forgot the install dvd was inside of it), but I closed it right after it, no errors, but it may have stopped working and has just the _ clicking?
While booting Slackware 13.1 it stops to check sda4 It says something about discrepancies. This started today after leaving the system up overnight. The system was suspended and wouldn't respond. I ended up have to do a hard reboot. The system seems to be working fine, but it does this every time I start Linux. The sda4 partition is Windows XP. XP also is working fine. While Linux is checking sda4 there is a statement that I need to run fsck without options. When I ran fsck I got the following message.
root@b-bhome:~# fsck fsck from util-linux-ng 2.17.2 e2fsck 1.41.11 (14-Mar-2010)
<edit>never mind dump the ;'s and it all works fine</edit> I'm trying to write a bash script that will check if XMBC is running if it is then do nothing else start it then do some other things.This is the start
Writing a bash script and I need to check if a known HD partition is mounted or not. I do not think /etc/mtab is the place to check. Would /proc/mounts always work? To make it simple like this : cat /proc/mounts | grep /dev/sdb2
I have an Ubuntu server in which a file is dumped every hour and a new file for the next hour and the process continues. If there is any problem due to which the creation of file stops then empty files are created every minute till the process is killed & started again. I need help to make a shell script to check if the empty files are being created and then kill the process and start it again.It would be a great help if anyone can help me regarding this.
When I boot up my desktop, lilo spends more than a minute printing a string of dots to the screen, before it declares "Bios data check successful" and then loads slackware normally.
I did Code: echo compact >> /etc/lilo.conf lilo but lilo declared that to be a syntax error and is as slow as ever. My lilo/conf contains Code: # LILO configuration file
no problems until yesterday it won't let me logon.i get "could not start kstartupconfig - check your inst" i have neither downloaded nor installed anything recently nor have i knowingly made any changes i can logon as root it was suggested that i create a new user which i did and i can logon with this new identity it was suggested that i tried repair in mepis user assistant but my original logon name does not appear in the user list however when i tried to create a user identity using that name, i was told i couldn't as it already existed.
Started slackpkg upgrade-up and went to bed. Woke up to find the power had gone out during the night. The computer booted up, but displayed a message that said something to the effect of, "Error occurred during root file system check. You will be given the option of doing maintenance......"I can get to a command prompt, but regardless of what I do a message pops saying it can't find libblkid.so.1
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xb2d772fd, pid=2766, tid=2953837424 # # JRE version: 6.0_24-b07
[code]....
I tried reinstalling both JDK and Netbeans to no avail.
After I upgrade my slackware to current(kernel 2.6.35.11),X could not start.My video card is ATI Radeon HD 4570.and I do reinstall fglrx like old ways :
But after restart, X could not start,and Keyboard does not respond. Also ,when I try init 3 and remove xorg.conf,The X can start with a low resolution(1024X768).In console mode,I got a high resolution(1366X768). So,is there a confict between fglrx and new kernel or What have I done Wrong?
