This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Upgraded from 4.3 - plugged in devices not working!

Tags: None
(comma "," separated)
ayqazi
Registered Member
Posts
6
Karma
0
Hi,

I'm using Gentoo. I upgraded from KDE 4.1 to 4.2, and the ability for it to auto-detect devices plugged in no longer works... you know, the thing where the little window appears saying 'devices recently plugged in'?

When I plug in my USB drive (one that used to get mounted by KDE just fine), here's what ends up in the logs: http://pastie.org/546569

I was wondering if knew what the problem is? I really don't know how I'm supposed to investigate this, so sorry for the lack of information.

Last edited by ayqazi on Wed Sep 02, 2009 2:19 pm, edited 1 time in total.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Can you please ensure that the HAL backend is selected in System Settings > Hardware?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ayqazi
Registered Member
Posts
6
Karma
0
I go to the 'Advanced' tab, and open 'Hardware'. I can see 3 backends - Power Management (HAL), Network Management (Fake), and Bluetooth Management (BlueZ).

Am I meant to see something else?
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
That is correct.

Is your device listed in the outputs of "lshal" and "solid-hardware list"?
( Look for the "udi" you get from lshal in the output of solid-hardware )

You can execute "solid-hardware details <udi>" to get information on your device.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ayqazi
Registered Member
Posts
6
Karma
0
Whoops, didn't see the reply - my bad.

OK, upgraded to KDE 4.3, and same thing happens. Here's what comes out in syslog:

http://pastebin.com/f69a7045d

Here's what happens when I do 'solid-hardware list' :

virtual QStringList Solid::Backends::Hal::HalManager::allDevices() error: "org.freedesktop.DBus.Error.AccessDenied"
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
You need to adjust the DBus permissions for HAL to allow normal users to communicate with it. Distributions usually do this out of the box. Unfortunately I do not know how to adjust such rules, but they are likely placed under /usr/share/dbus-1/ or /etc/dbus-1/


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
ayqazi
Registered Member
Posts
6
Karma
0
OK, thanks for the help so far. I shall ask on the Gentoo forums.

Strange how the distro doesn't handle this automatically......
djm
Registered Member
Posts
43
Karma
0
OS
Hi, I have recently upgraded from KDE 3.5.9 (which came with openSUSE 11.0). I have upgraded to KDE 4.3 while remaining on openSUSE 11.0.

I had successfully been using a number of bluetooth devices for some time with 3.5.9. Then an "Online update" broke something to do with dBus and my bluetooth mouse and keyboard stopped functioning with KDE.

A few weeks later another online update got the mouse working, but not the keyboard.

After some time of frustration with this I thought that I would try upgrading to KDE 4.3 to see if that fixes bluetooth. At first no it did not. Then I ran gnome's bluetooth-applet and got both my mouse and keyboard working.

Obex functionality had disappeared too with the upgrade, but I found that installing gnome-obex-server got it back for me.

Then for no apparent reason the keyboard stopped again. "hcitool scan" shows it as present, but typing keys doesn't do anything.

Now neither an older kinputwizard nor gnome's bluetooth-applet will pair with it.

Now my mouse has stopped too. Again for no obvious reason. Again it is visible using hcitool scan.

Can solid-bluetooth be used for this? If so how?

The rpm package kdebase4-workspace which contains solid-bluetooth does not seem to come with any documentation.

Any help would be appreciated.

Thanks,

David.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Installing KBluetooth4 may help you.

Solid Bluetooth is an API for applications to interface with bluetooth systems, and is not usable by the user, except through the "solid-bluetooth" command, which does not provide the level of functionality required, and is intended for diagnostic purposes.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
djm
Registered Member
Posts
43
Karma
0
OS
I upgraded to openSUSE 11.1 which comes with KDE 4.1.3. I had expected to then upgrade to 4.3.1 (perhaps now 4.3.2) but all my bluetooth devices work with 4.1.3. So I'm going to leave it alone for now.
zagzigger
Registered Member
Posts
4
Karma
0
OS
On openSUSE 11.1 X64 and KDE 4.3.3
Everything seems to be OK from running "lshal" and "solid-hardware list" and even says:
parent = '/org/freedesktop/Hal/devices/usb_device_90c_1000_AA00000000000192_if0_scsi_host_scsi_device_lun0' (string)
vendor = 'Corsair' (string)
product = 'Flash Voyager' (string)
Block.major = 8 (0x8) (int)
Block.minor = 48 (0x30) (int)
Block.device = '/dev/sdd' (string)
StorageDrive.bus = 'Usb' (0x1) (enum)
StorageDrive.driveType = 'HardDisk' (0x0) (enum)
StorageDrive.removable = true (bool)
StorageDrive.hotpluggable = true (bool)

but the device notifier won't mount it (and I have managed to install the new automount version). I suspect it's because my "Device Actions" have become mangled (by me) but I can't seem to figure out how to reset them or delete the ones that the editor does not like. Can I revert them somehow (as one of the panels advises) and then build new entries?
Thanks
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
The Device Actions editor in KDE 4.3 is unfortunately not too good at what it does. It is much improved in 4.4 and cannot create mangled actions.

Remove ls ~/.local/share/applications/<name of action>.desktop

You can check for the X-KDE-Solid-Predicate line to determine which ones are actions. Also check under ~/.kde4/share/apps/solid/


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]


Bookmarks



Who is online

Registered users: Bing [Bot], Evergrowing, Google [Bot], rockscient