SlackwareThis 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.
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.
So 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.
If I had the answer, I would supply it. Unfortunately I do not, as I have not run into this problem, nor read much about it.
As you've noted though, a few others have had similar KDE problems after upgrade, and so there are a few other similar/related threads about this subject; I guess you have checked out those other threads and not found the solution to your case there...
Well anyhow, it's a good idea to wait at least 24 hours minimum before wondering whether or not anyone's out here; you've barely waited an hour for a reply. Be patient and someone will come along sooner or later with some suggestion. Remember too, threads with no replies will get automatically "bumped" a few times, back to the top of the "new threads" list.
If no help has come after 24 hours, consider your thread and decide if there's more information you could add to it, that might make it easier for someone to answer. For example, exactly which set of updates you applied, might be useful info. Or maybe, what debugging or investigating you have done so far in trying to find the problem.
I cant believe how bad this all broke. There is not even one message on the log that can even give me a clue why kde wont start.
Having to reformat. Thanks slack!
I looked to that thread many times and none are the same as my problem.... right now its fubar.... to think that I have to go threw the whole install again just pist me off! Getting KDE in this distro was a bitch. And lets not for get the rest..... I am so pist right now...
Interesting your conclusion is. If you read carefully the thread mentioned above, you would notice that I had similar problem. Anyway, do like I did - remove kde, install once more, should work. If not, try to remove .kde directory from your users dir.
Thanks for your reply... I think that my issue is related to hald and dbus. Since dbus does not start properly hald hangs and does not start ether.... Please point me to the correct post where people are having dbus and hald issues.... It looks like I am not seen them.... Most are issues with symlinks, qt, etc.... To even tell you more nothing in my system work.... but once I start dbus and hald everything starts working again except for video.
I looked to that thread many times and none are the same as my problem.... right now its fubar.... to think that I have to go threw the whole install again just pist me off! Getting KDE in this distro was a bitch. And lets not for get the rest..... I am so pist right now...
The error messages I was receiving were slightly different than what you report, but the symptoms were exactly the same. KDE starts the splash screen then crashes back to the terminal.
I tried a number of things, but the only thing that finally worked for me was downgrading the mesa-7.9 to 7.8.2. A link to mesa-7.8.2 was provided here:
Thanks for your reply... Id di that in the past and some what works... but I can not run with the mesa driver because it only gives me generic display because I can not run on high res or even opengl for my video editing tools.
In top of that my issue is hald, dbus, and nvidia.
Here is where evrything goes down south for my video...
Code:
[ 672.796] ================ WARNING WARNING WARNING WARNING ================
[ 672.799] This server has a video driver ABI version of 8.0 that this
driver does not officially support. Please check
http://www.nvidia.com/ for driver updates or downgrade to an X
server with a supported driver ABI.
[ 672.814] =================================================================
[ 672.818] (EE) NVIDIA: Use the -ignoreABI option to override this check.
[ 672.822] (II) UnloadModule: "nvidia"
[ 672.822] (II) Unloading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 672.822] (EE) Failed to load module "nvidia" (module requirement mismatch, 0)
[ 672.826] (EE) No drivers available.
[ 672.830]
Fatal server error:
[ 672.839] no screens found
[ 672.843]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 672.860] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 672.865]
Did you reinstall the nVidia driver after doing the updates?
Are you using an up to date version of the driver.
Your log shows that your driver is unable to support the new X.
I have reverted back to 13.1
I am not a tinkerer or a test monkey my desktop is a production machine so I cant afford to be down like this
As I posted before I ended up in current land by mistake. so I am back at 13.1 and all is fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.