[opensuse] Responsivness problems

I'm begining to suspect all this may have a single root cause.

For the last few update to KDE (4.2.x) the various widgets 'freeze' or
are unresponsive or have a long (> 1 minute) delay in responding.

These include the widgets in the bottom bar, the menu pop-up and of
course the screen widgets I have - the clock and weather. The clock
doesn't tick; it may jump at intervals.

Other KDE widget things are unresponsive too. Doing a file save it may
take a minute ore more before the dialogue box comes up.

Now all this may have something going on behind the scenes, but I don't
know because all this is on my start-up or a result from clicking
applications. Once an application *is* running it runs just fine, its
these little widgets and applets and start-ups that are problematic.

So today I started K3B from the command line.
I got these errors

=========
$ k3b
k3b(10639): ""Backgroundcolor" - conversion from "Window" to QColor
failed" " (wrong format: expected '3' or '4' items, read '1')"


k3b(10639): ""Foregroundcolor" - conversion from "WindowText" to QColor
failed" " (wrong format: expected '3' or '4' items, read '1')"


k3b(10639): ""Backgroundcolor" - conversion from "Window" to QColor
failed" " (wrong format: expected '3' or '4' items, read '1')"


k3b(10639): ""Foregroundcolor" - conversion from "WindowText" to QColor
failed" " (wrong format: expected '3' or '4' items, read '1')"


<unknown program name>(10638)/: Communication problem with "k3b" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken." "


=========

Is there some kind of DBUS problem?
I'm not running AppArmour.

I try again ... and get a different result

==============
$ k3b
QStringList
Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const
Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.NoReply"

k3b(10639): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory!
k3b(10639): Attempt to use QAction "view_contents" with KXMLGUIFactory!
k3b(10639): Attempt to use QAction "quick_dir_selector" with KXMLGUIFactory!
QStringList
Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const
Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.NoReply"

<unknown program name>(10695)/: Communication problem with "k3b" , it
probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken." "

BigBoy:~/Downloads> QStringList
Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const
Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.NoReply"

QStringList
Solid::Backends::Hal::HalManager::findDeviceByDeviceInterface(const
Solid::DeviceInterface::Type&) error: "org.freedesktop.DBus.Error.NoReply"


==============

IS HAL the problem?

========
ps -ef | grep hal
105 2453 1 0 07:20 ? 00:00:01 /usr/sbin/hald --daemon=yes
root 2457 2453 0 07:20 ? 00:00:00 hald-runner
root 2571 2457 0 07:20 ? 00:00:00 hald-addon-input:
Listening on /dev/input/event6 /dev/input/event5 /dev/input/event8
/dev/input/event3 /dev/input/event4 /dev/input/event0 /dev/input/event9
root 2630 2457 0 07:20 ? 00:00:00 hald-addon-storage:
polling /dev/sdb (every 2 sec)
root 2632 2457 0 07:20 ? 00:00:06 hald-addon-storage:
polling /dev/sr0 (every 2 sec)
105 2635 2457 0 07:20 ? 00:00:00 hald-addon-acpi:
listening on acpid socket /var/run/acpid.socket
root 3064 2457 0 07:20 ? 00:00:00
/usr/lib/hal/hald-addon-rfkill-killswitch
root 3141 2457 0 07:20 ? 00:00:00 /usr/lib/hal/hald-addon-leds
anton 10376 1 0 10:54 ? 00:00:00
/usr/lib/gvfs/gvfs-hal-volume-monitor
anton 10806 10456 0 11:23 pts/0 00:00:00 grep hal

========

Interesting. Sometimes it says that HAL has disabled devices.



All in all I'm confused, both by what I see and by the fact that its
inconisitent. Some days I have no problems. I don't know why.

Any suggests as to where I should start tracknig this down?

--
The quality, not the longevity, of one's life is what is important.
--Dr. Martin Luther King Jr

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages