there is released first version of kdebluetooth subsystem for kde4 please add it to the tree info http://extragear.kde.org/apps/kdebluetooth/ download http://sourceforge.net/project/showfiles.php?group_id=89888
Not sure if this would or even could be a version bump for net-wireless/kdebluetooth.
Wll we have it as kdebluetooth4 in kde-testing and kde-crazy. But none of us uses bluetooth so it surely need some love. If someone is willing to test report all issues and even fix them :P (reporting should be enought) but maybe only slotting should be enought insead of creating new package.
I'll do it this weekend. :)
that will be great. then i'll test it while i use kdebluetooth:3.5 on daily basis and now i use kde4 for testing purposes so that also could be tested by me.
I have been testing the ebuild but I was not able to compile it... I got kdelibs [4.1.3-r1] but the ebuild still complains * NEED_KDE=:4.1 currently not supported. Does this mean it actually does not support kde 4.1? That does not make much sense. Any ideas anyone?
You have something broken. Paste your ebuild here or join on irc i will try to help.
It's the one from kde-testing... I guess I'll end up fixing the ebuild.
scarab@Ugly-Elf: /usr/local/portage/kde/net-wireless/kdebluetooth4 $ repoman manifest >>> Creating Manifest for /usr/local/portage/kde/net-wireless/kdebluetooth4 digest.assumed 1 kdebluetooth4-0.2::kdebluetooth4-0.2.tar.bz2 This is weird. Really try to sync main tree or what so ever.
Created attachment 176957 [details, diff] fixed dep on solid patch this change to the ebuild fixed build on systems that don't have a full kde-4.1 installed
Version 0.3 of kdebluetooth4 was released...
I've tried 0.3 and the "live" ebuild from kde-testing. Both build but neither seem to work. When I run kbluetooth4, it starts in offline mode. If I replug my adapter then it goes into online mode and crashes with some D-Bus error. No icon ever appears in the tray. If I try to run one of the other binaries, they crash straight away with D-Bus errors. I wonder if this is a Gentoo-specific problem because another Gentoo user reported the same thing with 0.2 over at http://kde-apps.org/content/show.php?content=84761&forumpage=3. I don't have the error message from my machine (it's not this machine) but it was similar at least. process 8339: arguments to dbus_message_new_method_call() were incorrect, assertion "path != NULL" failed in file dbus-message.c line 1070.
Exactlty the same issue here; KDE 4.2.1, Bluez 4.32, DBus 1.2.3-r1. Cheers, Nico
Oh, and by the way this was reported on abn *Ubuntu* list as well, see https://lists.ubuntu.com/archives/ubuntu-bluetooth/2008-October/002371.html so it might actually not be Gentoo specific. Cheers, Nico
It seem that the problem is with the permissions of something: if I start it from console using sudo, it appears in the tray bar and it seem to work correctly excluding the device manager, but I can send files or change property of the adapter. The device manager don't start from the tray icon, but if I start it from console using sudo the window appear, but I can't so anything. Inputwizard, instead, it seem to work with sudo, but I don't tried it as well.
Your problem sounds more like a console kit problem. Before starting the applet, check whether you have a session open with ck-list-sessions. If not, run ck-launch-session and then start the applet.
(In reply to comment #15) > Your problem sounds more like a console kit problem. Before starting the > applet, check whether you have a session open with ck-list-sessions. If not, > run ck-launch-session and then start the applet. > I checked, but I don't resolved. with consolekit started by init, I closed kbluetooth4 started with sudo and I checked ck-list-sessions, that returned nothing. Then I launched a session with ck-launch-session and I tried again ck-list-sessions and this time it listed me a session: Session2: uid = '1000' realname = 'Urban' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0.0' x11-display-device = '/dev/tty7' display-device = '/dev/pts/1' remote-host-name = '' is-local = TRUE on-since = '2009-03-23T13:00:56.953605Z' but when I started the applet, the icon haven't appeared on the tray!
Re-assigning to herd for better treatment.
Have got it to work but i need to start a session zorry@laptop1 ~ $ ck-launch-session zorry@laptop1 ~ $ ck-list-sessions Session1: unix-user = '1000' realname = '' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0.0' x11-display-device = '/dev/tty7' display-device = '/dev/pts/3' remote-host-name = '' is-local = TRUE on-since = '2009-06-09T19:12:56.595812Z' login-session-id = '4294967295' zorry@laptop1 ~ $ kbluetooth4 AGENT registered ! zorry@laptop1 ~ $ I got the icon and i could add a bt mouse. We need a open session before we lunch kbluetooth4 and that fail. How to debug that part and what fail? But i did get some error to as. zorry@laptop1 ~ $ Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(const QString &)
Got session working did forget USE consolekit on some packages. :(
I've just tried this kdebluetooth4-0.3 I was unable to made it to work under regular user (icon was missing every time). I checked strace what's going on there: [...] socket(PF_FILE, SOCK_STREAM, 0) = 3 connect(3, {sa_family=AF_FILE, path=@"/tmp/dbus-54fHdnkTWy"...}, 23) = 0 [...] read(3, "l\2\1\1\4\0\0\0\n\0\0\0/\0\0\0\6\1s\0\6\0\0\0:1.124\0\0\5"..., 2048) = 68 read(3, 0x80a9cb0, 2048) = -1 EAGAIN (Resource temporarily unavailable) exit_group(0) = ? I tried to create a session as it was suggested (without results): uniks@lenovo ~/ $ ck-list-sessions Session4: uid = '1000' realname = '' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2009-06-15T11:11:14.998946Z' uniks@lenovo ~/ $ kbluetooth4 uniks@lenovo ~/ $ killall -9 kbluetooth4 uniks@lenovo ~/ $ ck-launch-session uniks@lenovo ~/ $ ck-list-sessions Session4: uid = '1000' realname = '' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty8' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2009-06-15T11:11:14.998946Z' Session5: uid = '1000' realname = '' seat = 'Seat1' session-type = '' active = FALSE x11-display = ':0.0' x11-display-device = '/dev/tty8' display-device = '/dev/pts/3' remote-host-name = '' is-local = TRUE on-since = '2009-06-15T14:26:07.346658Z' uniks@lenovo ~/ $ kbluetooth4 finally started as root, and applet started almost properly... * icon was shown * i was able to receive file (send some jpg from mobile) but, when I wanted to start Device Manager and tried to scan for a devices, I got: Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeCreated(const QString &) Object::connect: No such signal Solid::Control::BluetoothRemoteDevice::nodeRemoved(const QString &) There was also no possibility to send something over bluetooth, each time I tried, I got pop-up with error "org.openobex.Error.NotFound"
I did two things I saw at http://forums.gentoo.org/viewtopic-t-738161-highlight-kbluetooth4.html: 1. duplicated these lines <policy user="root"> <allow own="org.bluez"/> <allow send_destination="org.bluez"/> <allow send_interface="org.bluez.Agent"/> </policy> from /etc/dbus-1/system.d/bluetooth.conf and changed the first line in the duplicate to <policy group="users"> 2. rm -rf /var/lib/bluetooth Now, executing kbluetooth4, I can at least receive from my mobile. I didn'n try to send ...
(In reply to comment #21) > I did two things I saw at > http://forums.gentoo.org/viewtopic-t-738161-highlight-kbluetooth4.html: > > 1. > > duplicated these lines > <policy user="root"> > <allow own="org.bluez"/> > <allow send_destination="org.bluez"/> > <allow send_interface="org.bluez.Agent"/> > </policy> > from /etc/dbus-1/system.d/bluetooth.conf > and changed the first line in the duplicate to > > <policy group="users"> > > 2. rm -rf /var/lib/bluetooth > > Now, executing kbluetooth4, I can at least receive from my mobile. > I didn'n try to send ... > That just let anyone to own the bluethooth controller dbus' interface, which is a big security hole. Any local user can bypass the pairing mecanism in this way.
I have just installed KDE 4.3.0 and kdebluetooth4 svn/live version (kdebluetooth4-9999.ebuild from kde-testing overlay) and it does not have this issue.
According to http://techbase.kde.org/Kbluetooth kdebluetooth4 is deprecated. So i've committed net-wireless/kbluetooth instead. *** This bug has been marked as a duplicate of bug 286316 ***
