LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   *Nearly* Successful Upgrade to Current - Could Not Start D-Bus- No X (http://www.linuxquestions.org/questions/slackware-14/%2Anearly%2A-successful-upgrade-to-current-could-not-start-d-bus-no-x-730501/)

BobNutfield 06-03-2009 05:46 PM

SOLVED - *Nearly* Successful Upgrade to Current - Could Not Start D-Bus- No X
 
Hello Everyone,

Well, I posted recently about possible problems upgrading from 12.1 to current following Robby Workman's suggested method, and after several hours of downloading and installing, on the first reboot (after configuring Grub), I sat there watching my new kernel boot and I was about to heartily congratulate my self because it started its boot just fine. But, Alien Bob DID tell me I would find out soon enough. Actually, it does boot to a terminal login, but I do have the following problem if someone can point me in the right direction. Google does have a number of different forum posts with KDE4 similar posts, but I found none that offered a solution.

1. During boot, there is a repeating message (repeats for about 100 lines) as it starts to try and open wpa_ctrl, stating there is no such directory. I don't think this is very serious as I will probably just have to set wpa_supplicant back up again. Am I correct that this will fix this error?

2. Startx looks like it going to give me a desktop (an X cursor even appears on the screen, then fails and just goes to a black screen with a message in the corner:

Quote:

Could not start D-Bus. Check you installation
I am hoping these are simple fixes, and I will gladly read/learn about it if someone could give me some hints. I am pretty stuck on this one. I am hoping an entire re-install is not going to be necessary because I do not have an install DVD and would have to download one (huge download.)

Thanks for any replies

Bob

Alien Bob 06-03-2009 06:13 PM

After the upgrade, you did move all the .new files that have been installed on your system into their proper place (where necessary)? Check the difference with the originals, and if you do not see any changes that were made by yourself, move the .new files overwriting their originals without further thought.

Eric

BobNutfield 06-03-2009 06:20 PM

Thanks for the reply, Eric. When asked at the end of the installation if I wanted to overwite the original files, I answered yes (selected "O", for overwrite). If there are new files for me to move about, I won't have a clue which ones or where to move them.

Been working with this for hours. Looks like I will need to download the DVD and start over with a new install. Thought I was home free, but, oh well...

I never learned enough about D-Bus to understand what it does.

I also tried to recompile the fglrx module and got the error:

Quote:

gcc: command not found
I though gcc was part of basic install.

Thanks

Bob

shadowsnipes 06-04-2009 01:46 AM

You also have to be careful about the .original files that slackpkg leaves behind when your overwrite the config files. This is especially important for module blacklists. Your udev files might also need a little cleaning up.

Even more important: slackpkg should be used carefully when upgrading across multiple versions. You upgraded 12.1 directly to -current (future Slackware 13), skipping 12.2. The problem with using slackpkg when doing this is that slackpkg seems to use the Changelog for determining what packages are new, and the 12.2 changelog was not used. As a result, you could potentially be missing some new packages in -current that first showed up in Slackware 12.2. You also might have extra packages that were removed in 12.2 (though I think this is less likely). So, with multiple version upgrades with slackpkg, you really do have to step between each versions sequentially (unless you install/remove the differences manually). In multiple versions upgrades it is actually easier to simply follow the code in UPGRADE.TXT, which basically just upgradepkg --install-new in the different package sets. You could make exceptions in your for loop if you wanted to blacklist packages. You don't have to download a whole DVD either. If you don't need the sources, then you probably only need a couple of the install cds. For playing with -current I prefer using Eric's mirror-slackware-current.sh found on his tools page.

slackpkg is nice when using it to upgrade up one version because it "remembers" your install set. For instance, on one machine I may have excluded the kde set along with some other random packages. If I do a install-new or upgrade-all I won't be bugged about the kde packages (or others I explicitly blacklist).

Also, in case you haven't already done so, check out the CHANGES_AND_HINTS.TXT for 12.2 and -current. My upgrade HowTo for 12.2 (see my signature below) may also be of some use to you. It shows some examples of using the CHANGES_AND_HINTS.TXT along with usage of slackpkg and mirror-slackware-current.sh.

BobNutfield 06-04-2009 02:57 AM

Thanks, shadowsnipes. It was probably a silly thing to try when I am not a coder nor extremely well versed in Slackware, but I thought it would be good learning experience, and it was. Now I know that I don't know enough to do it properly. I backed everything up, so I am just re-installing with 12.2 and I will try the upgrade from there.

Thanks again

Bob

BobNutfield 06-04-2009 10:14 AM

Upgrade Successful-- Thanks to Alien Bob and shadowsnipes
 
Thanks to you guys....Current is up and running. I really should have known better than to try this skipping a version. I thought I could get away with it since I was already running the 2.6.27 kernel, but there were too many other things I should have considered.

@shadowsnipes

Your guide was what I followed.

Thanks again

Bob

shadowsnipes 06-05-2009 01:04 AM

Quote:

Originally Posted by BobNutfield (Post 3562967)
Thanks to you guys....Current is up and running. I really should have known better than to try this skipping a version. I thought I could get away with it since I was already running the 2.6.27 kernel, but there were too many other things I should have considered.

@shadowsnipes

Your guide was what I followed.

Thanks again

Bob

Glad it worked out for you! :)


All times are GMT -5. The time now is 11:47 PM.