Hi folks. FYI I'm running Slackware64 13.0 with kde upgraded to 4.3.1.

When I run k3bsetup from a shell the gui pops up without the dvd listed in the device section. I know the dvd works since that's what I used to load Slackware with and I can mount cd's and dvd's and copy files from them.

In the shell there is a message:
QStringList Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const Solid:eviceInterface::Type&) error: "org.freedesktop.DBus.Error.Disconnected"

Any ideas?

You need gparted installed. The Changelog sometime back stated that there is now a dependency on gparted.

Hmm ... I don't think think I need gparted since I have Slackware 13.0 on my desktop and laptop. K3bsetup finds the dvd on the laptop but not on the desktop. Gparted is not on either machine.

Also, I think that gparted would be a real pig to install in Slackware under kde since it is a gnome-based program ... lots of gnome-ish dependencies.

Correction, it's parted, not gparted.
SW13 Changelog

Thanks for the correction. It turns out that I do have parted on both of my machines in /usr/sbin but still no joy ..

thirteen

I dbus running at all?

Here's what I have from a ps x | grep dbus:

18905 tty1 S 0:00 dbus-launch --sh-syntax --exit-with-session
18906 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
19559 pts/2 S+ 0:00 grep dbus

This is from the desktop machine that doesn't see the drive.

Here's what I have from the same command on my laptop, which sees it's drive:

3623 ? S 0:00 dbus-launch --autolaunch 2bca6134dae7df0943df73de4b0af339 --binary-syntax --close-stderr
3624 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
3691 ? S 0:00 dbus-launch --sh-syntax --exit-with-session
3692 ? Ss 0:04 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
4757 pts/0 R+ 0:00 grep dbus

So, yes it appears that dbus is running on the desktop but not the same number of processes as the laptop. Recall that the distribution and upgrades for each are identical. As far as I know the software on each machine is exactly the same.

Thirteen

A little more information. I have tried running the command:

hal-find-by-property --key block.device --string /dev/sr0

on each machine. The output from the laptop is:

/org/freedesktop/Hal/devices/storage_model_DVD__RW_AD_7580S

and from the desktop machine:

error: libhal_ctx_set_dbus_connection: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

I don't know much about hal and dbus so any help would be much appreciated.

A quick look at the folder /var/run/dbus shows that on the desktop, it is empty while on the laptop:

-rw-r--r-- 1 root root 5 2010-03-13 08:28 dbus.pid
srwxrwxrwx 1 root root 0 2010-03-13 08:28 system_bus_socket=

Since there is no dbus.pid in this folder does this mean that dbus is not running, even though there is apparently a dbus daemon running? (see above post)

Thirteen

Even more info. A ps x | grep hal on the laptop shows:

3410 ? S 0:00 /usr/libexec/hald-addon-cpufreq
3412 ? S 0:00 hald-addon-storage: polling /dev/sdb (every 2 sec)
3420 ? S 0:00 hald-addon-storage: polling /dev/sr0 (every 2 sec)
3922 pts/2 R+ 0:00 grep hal

On the desktop:

27411 pts/2 R+ 0:00 grep hal

I can't seem to start hal manually using its startup script on the desktop machine. Any ideas?

Long shot:

http://www.linuxquestions.org/questi...-alias-714702/

That of any help?

Thanks for the link. I'll give it a shot this weekend.

thirteen

Probably not the case, but if you are running a custom kernel try booting with one of the stock kernels. I had this happen with one of my first attempts at minimizing a custom kernel.

I *think* I might have the answer. I looked at the list of users on my laptop and it includes "haldaemon" and "messagebus". These are not in the userlist on the desktop.

The reason they're not there is that after upgrading the desktop from a 32-bit machine to a 64-bit machine and upgrading from Slackware 12.0 to 13.0, I copied the passwd file from the old machine to the new one. The desktop is a server with several users depending on it. They need to be able to log in and edit webpages etc. Instead of recreating their usernames and sending them a new, temporary password I simply copied the old passwd file to etc. Bad idea I guess.

Anyway, I am on vacation at the moment and can't do anything with the server (well I *could* remotely I guess, but I'd like to be there in case the machine is borked .. Murphy's law) but I'll try adding a haldaemon and messagebus user in early April and seeing what happens. If it works I'll post it.

thirteen

Problem solved!

I was right .. adding the messagebus and haldaemon users to passwd and shadow fixed it.

Thanks for all the replies.

thirteen

P.S. I've forgotten how to mark this thread as 'solved'. Any help is appreciated.

Click the "Thread Tools" at the top of the thread listing.