HAL error, ImportError: No module named gnome

davidguygc · 07-19-2007, 02:09 AM

Hi, I've been looking around, and I haven't seen anyone with the same error as me.

I updated to Slack 12.0 the other day, and when I type hal-device,

Code:

bash-3.1# hal-device
error: dbus_bus_get: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket
/var/run/dbus/system_bus_socket: Connection refused
bash-3.1# hal-device-manager

and when I run hal-device-manager,

Code:

bash-3.1# hal-device-manager
Traceback (most recent call last):
  File "/usr/bin/hal-device-manager", line 9, in <module>
    import gnome
ImportError: No module named gnome

I get the same error on both my root and user account. I have Dropline-Gnome, and I have Beryl up and running, if that means anything.

Any ideas?

Thanks,
--David

erklaerbaer · 07-20-2007, 01:14 PM

it's quite obviously, really. there is no python package named "gnome" on your system ( on mine there is not even pygtk )

this is hal-device-manager:

Code:

#!/usr/bin/env python

"""This is the main executable for DeviceManager. GTK+/Glade code is based
on simplepy from Shannon -jj Behrens <jjinux@yahoo.com>"""

import sys
import pygtk
import gtk
import gnome

sys.path.append('/usr/share/hal/device-manager')

import Const
import LibGladeApplication
from DeviceManager import DeviceManager

gnome.program_init(Const.NAME, Const.VERSION)
gtk.glade.bindtextdomain('hal', '/usr/share/locale')
gtk.glade.textdomain('hal')
DeviceManager()
gtk.main()

that's normal.
your first error however is more serious. did you have another dbus/hal package before upgrading? merged the .new files?
try to stop dbus , rm -rf /var/run/dbus , and restart it; still got errors?

davidguygc · 07-20-2007, 05:23 PM

well, I have a dbus-daemon, and dbus-daemon-1... I'm not sure what that's all about. Before I upgraded to 12.0, I installed Dropline Gnome and upgraded to current in May, so I may have done it then. I did that command, and I'm restarting now.

erklaerbaer · 07-20-2007, 05:41 PM

ok, i'm not sure about dropline, but i think they added their own dbus package. i guess best thing to do would be to remove every dbus package, rm /var/lib/dbus and /var/run/dbus and reinstall the slackware dbus packages (dbus-1.0.2-i486-3 dbus-glib-0.73-i486-1 dbus-qt3-0.70-i486-1
)

dropline replaces some system packages and afaik don't have a proper uninstall mehod; you will run into other problems. maybe it's easier to do a clean install.

davidguygc · 07-20-2007, 08:32 PM

Well I got hal-device working, I had to restart dbus-daemon, then hald, but I can't get it to stick when I reboot. And I tried a shell script whenever I start up my computer with no luck.

When DBus is working, I still get the same error when I try hal-device-manager.

So, I'm lost, if there isn't a gnome module, why did they put it in there? I've done too much tweaking to do a clean install, so IDK what I should do to fix it.
--David

davidguygc · 07-22-2007, 12:27 AM

Well, I still cannot get hal-device to work without doing it manually... so I'm lost

davidguygc · 07-22-2007, 04:37 PM

New update, For some reason, rc.hald was not being started up, so I got that going from rc.local, so now the only problem is the "No module named gnome" problem...

erklaerbaer · 07-22-2007, 05:03 PM

Quote:

it's quite obviously, really. there is no python package named "gnome" on your system ( on mine there is not even pygtk )

it won't work unless you install a gnome distribution. most likely you won't need it too.

rworkman explained the reason, why it's there in the first place:

Quote:

/usr/bin/hal-device-manager needs PyGTK and a few things from gnome in order to work. Pat elected to leave the binary in the package due to the fact that some users will elect to install one of the third-party gnome builds, and any of those should provide the necessary dependencies for hal-device-manager to work.

davidguygc · 07-22-2007, 05:05 PM

I have dropline gnome, and pygtk installed though...

erklaerbaer · 07-22-2007, 05:13 PM

check the dropline gnome forums

davidguygc · 07-22-2007, 05:52 PM

OK, Thanks.