-   Slackware (
-   -   X broken after latest x86_64 -current upgrade (

the_penguinator 02-23-2013 02:26 PM

X broken after latest x86_64 -current upgrade
I've developed the "klauncher can't find dbus" problem since upgrading yesterday...from the kdm.log the warning is that dbus isn't running or installed, but $ps aux | grep dbus shows that it is in fact installed and running...did #slackpkg reinstall kde and there's no change...also did #slackpkg reinstall xf86-video-ati and xorg-server with no change in behaviour

I've got the machine going to runlevel 3 now, and have tried xwmconfig as both root and user to select another wm and see if I could get it to start X without kdm, but it borks with the same black screen and dead keyboard...

which of those x/ directory programs could have caused this broken communiciation? needing some clues here folks

01micko 02-23-2013 03:25 PM

Sorry, no help to you, but it's working fine here on a low end 64 bit laptop (compaq-CQ-60, Celeron-1.6, intel Cantiga graphics, 1 GB RAM). Did you get the "added" glu package? The upgrade has increased glxgears numbers by ~25% (fwiw).

Ah, seems you visited here, so can discount glu I guess. Sure seems the symptoms of a KMS (forgetting the dbus error) issue, was it a long time since last update?

the_penguinator 02-24-2013 08:23 AM


Originally Posted by 01micko (Post 4898320)
Sure seems the symptoms of a KMS (forgetting the dbus error) issue, was it a long time since last update?

yes, it did, and this laptop gets upgraded every time -current changes so it's pretty well on the edge of "new", all the time...this is the first time in about 2 years that it has gotten this badly munged after an upgrade

well, it was fun trying to figure out where the issue was, but you don't get those hours back so I've done a clean re-install back to 14 and will do #slackpkg upgrade to -current, one file at a time when I get to those x/ directory files from the 22nd and see if I can id which one of the little f***ers buggered up my system

the_penguinator 02-24-2013 05:45 PM

who knows what it corruption of some sort during the previous upgrade...all is as it has been...correct and functional at -current

All times are GMT -5. The time now is 03:50 PM.