Re: Bluetooth headset "protocol not available". (Bug#998220)
On Wed, 10 Nov 2021, Andrey Rahmatullin wrote:
> > I think "someone" should recommend libspa-0.2-bluetooth, maybe pipewire
> > itself.
> Note that pulseaudio-module-bluetooth isn't recommended by pulseaudio
> either.
Agreed, but
pulseaudio-module-bluetooth
is somehow a *natural* naming for a candidate to get bluetooth support,
while
libspa-0.2-bluetooth
is something I wouldn't have found myself ...
Norbert
--
PREINING Norbert https://www.preining.info
Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Re: Bluetooth headset "protocol not available". (Bug#998220)
On Wed, Nov 10, 2021 at 01:07:33PM +0900, Norbert Preining wrote: > I think "someone" should recommend libspa-0.2-bluetooth, maybe pipewire > itself. Note that pulseaudio-module-bluetooth isn't recommended by pulseaudio either. -- WBR, wRAR signature.asc Description: PGP signature
Re: Bluetooth headset "protocol not available". (Bug#998220)
Hi all the comments about how to activate pipewire are somehow strange to me, I guess because you followed some ubuntu guide. BUT indeed, libspa-0.2-bluetooth is necessary for bluetooth audio compatibility. Just retried it and after installation and restart of pipewire I could connect my BT headphones. I think "someone" should recommend libspa-0.2-bluetooth, maybe pipewire itself. Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Bluetooth headset "protocol not available". (Bug#998220)
I was about to comment on Bug#998220, but I changed my mind. I do have `pipewire` installed. For one thing `libpipewire` is in the dependencies of `kwin- wayland`, so it's a requirement on my system. After last upgrade (sid) a couple of days ago, bluetooth headset were refusing to connect, "Protocol not available". But they were willing to connect if I was before doing: (after each reboot) `systemctl --user restart pulseaudio.service` Then I decided to do some searches, and here is what came from it. I'm putting it here because it's not sure at all that every bit of what I did was really necessary. Specifically, were the libraries `libspa-0.2-bluetooth` and `pipewire-audio- client-libraries` really needed. Or even just `libspa-0.2-bluetooth`. === I do initially, have the following issue: `otherwise device connections will fail with "Protocol not available".` (https:// wiki.debian.org/PipeWire) Here is an edited version of how I fixed it on #debian-next: === Giving the ubuntu tuto a try now (https://askubuntu.com/questions/1339765/replacing-pulseaudio-with-pipewire-in-ubuntu-20-04) `sudo aptitude install libspa-0.2-bluetooth pipewire-audio-client-libraries` `systemctl --user daemon-reload` (as plain user, other terminal) `systemctl --user --now disable pulseaudio.service pulseaudio.socket` `systemctl --user mask pulseaudio` => `Created symlink /home/chris/.config/systemd/user/pulseaudio.service → /dev/null.` `systemctl --user --now enable pipewire-media-session.service` => `Failed to enable unit: Unit file /etc/xdg/systemd/user/pipewire-media-session.service is masked.` Here I'm suggested to use the two pivotal following lines: `sudo aptitude purge pipewire-media-session` `sudo aptitude reinstall wireplumber` => "Created symlink /etc/systemd/user/pipewire-session-manager.service → /usr/lib/ systemd/user/wireplumber.service." I still have "device connections will fail with "Protocol not available"." `systemctl --user restart pipewire` There it is. Bottom line: I did not follow https://wiki.debian.org/PipeWire which contains things not possible to do. I followed https://askubuntu.com/questions/1339765/replacing-pulseaudio-with-pipewire-in-ubuntu-20-04 With `pipewire-media-session` replaced by `wireplumber`. I did do `apt purge --autoremove pipewire-media-session` and then `apt install --reinstall wireplumber` And `systemctl --user restart pipewire` I didn't do: `touch /etc/pipewire/media-session.d/with-pulseaudio`, nor did I do: `cp /usr/ share/doc/pipewire/examples/systemd/user/pipewire-pulse.* /etc/systemd/user/` (from https://wiki.debian.org/PipeWire) The line: "Install pipewire-pulse (which replaces pulseaudio and pulseaudio-bluetooth)" from https://wiki.archlinux.org/title/bluetooth_headset suggests that the two latter packages should be removed (not sure about that, just saying) I rebooted to see if it'd be still working: it auto connected very very quickly. And audio is working. === Packages: https://packages.debian.org/sid/libspa-0.2-bluetooth[1] and https:// packages.debian.org/sid/pipewire-audio-client-libraries[2] are saying that they are "experimental". That could explain why they are not in the dependencies. But they seem to work.
Re: which commands are executed by the "bluetooth enable" button?
Il 03/05/20 00:09, Marco Möller ha scritto:
the question how KDE is achieving to unblock the soft block on
bluetooth (even without this package being installed) did not become
clarified to me. :-(
I'm not a qml expert, but it should do in this way(from Toolbar.qml):
var enable = !btManager.bluetoothOperational;
btManager.bluetoothBlocked = !enable;
for (var i = 0; i < btManager.adapters.length; ++i) {
var adapter = btManager.adapters[i];
adapter.powered = enable;
}
--
Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
On 30.04.20 18:21, Marco Möller wrote: On 30.04.20 17:01, luca.pedrielli wrote: Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. rfkill is working here, but you can also try this(working here too): $ dbus-send --system --dest=org.bluez --print-reply /org/bluez/hci0 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true or false https://medium.com/@konchunas/how-to-toggle-bluetooth-with-shortcut-on-linux-the-proper-way-a440dd88605e I notice that the dbus command uses "hci0" somewhere in the line. This "hci0" is what I am for hours investigating already and therefore I haven't answered back earlier. By now I did not find out how to deal with this "hci0" correctly, but after you have kindly provided another suggestion I think I should interrupt my investigations and first give feedback what I so far found out: By now the most promising hint towards a solution results from the finding, that "hci0" seems to not be present as long as the magic GUI button has not been triggered, and therefore all other so far tested CLI tools (for instance bluetoothctl and hcitool) fail. The mouse click on the magic buttons makes "hci0" present, though, and subsequently commands work. EXAMPLE (after reboot, "hci0" is still not detected by "hcitool dev"): (1) System Settings - Network - Bluetooth: trigger the button (2) bluetoothctl power off now works correctly (3a) bluetoothctl power on now works correctly (3b) the dbus command as a user now works correctly (3c) hcitool dev now works correctly, reports "hci0" with its MAC (3d) bluetoothctl list now works correctly, reports the MAC I followed your suggestions to /usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/Toolbar.qml and towards rfkill and by this I hit into several more keywords, which let me start study the issue for many more hours. I by now have collected a list of available commands after searching for already installed packages or by asking with the "apropos" command, but by now I did not find out if any of them carries the secret: Commands of interest could be: by now only used for monitoring if "hci0" shows up or not hcitool dev bluetoothctl list still not understanding how to maybe use them beyond above mentioned monitoring: bluetootctl hcitool hciattach - attach serial devices via UART HCI to BlueZ stack hciconfig - configure Bluetooth devices hcitool - configure Bluetooth connections hid2hci - Bluetooth HID to HCI mode switching utility btattach - attach serial devices to BlueZ stack btmgmt - A command-line interface of BlueZ for management obexctl - A command-line interface of BlueZ for OBEX (file transfer) The following tools demonstrate that in principal the driver is loaded all the time, right after reboot already: modinfo bluetooth I am also searching towards systemd maybe needing to do something, as I have found at least 4 systemd items which could be of interest, but also here I haven't succeeded with my investigations by now: systemctl status bluetooth.service systemctl status bluetooth.socket systemctl status systemd-rfkill.service systemctl status systemd-rfkill.socket Using the rfkill command as announced in the very first answer from Luca is the only applicable path which I could find to make the bluetooth device available at teh CLI. As this command (this package) wasn't installed in my OS, the question how KDE is achieving to unblock the soft block on bluetooth (even without this package being installed) did not become clarified to me. :-(
Re: which commands are executed by the "bluetooth enable" button?
On 30.04.20 17:01, luca.pedrielli wrote: Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. rfkill is working here, but you can also try this(working here too): $ dbus-send --system --dest=org.bluez --print-reply /org/bluez/hci0 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true or false https://medium.com/@konchunas/how-to-toggle-bluetooth-with-shortcut-on-linux-the-proper-way-a440dd88605e I notice that the dbus command uses "hci0" somewhere in the line. This "hci0" is what I am for hours investigating already and therefore I haven't answered back earlier. By now I did not find out how to deal with this "hci0" correctly, but after you have kindly provided another suggestion I think I should interrupt my investigations and first give feedback what I so far found out: By now the most promising hint towards a solution results from the finding, that "hci0" seems to not be present as long as the magic GUI button has not been triggered, and therefore all other so far tested CLI tools (for instance bluetoothctl and hcitool) fail. The mouse click on the magic buttons makes "hci0" present, though, and subsequently commands work. EXAMPLE (after reboot, "hci0" is still not detected by "hcitool dev"): (1) System Settings - Network - Bluetooth: trigger the button (2) bluetoothctl power off now works correctly (3a) bluetoothctl power on now works correctly (3b) the dbus command as a user now works correctly (3c) hcitool dev now works correctly, reports "hci0" with its MAC (3d) bluetoothctl list now works correctly, reports the MAC I followed your suggestions to /usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/Toolbar.qml and towards rfkill and by this I hit into several more keywords, which let me start study the issue for many more hours. I by now have collected a list of available commands after searching for already installed packages or by asking with the "apropos" command, but by now I did not find out if any of them carries the secret: Commands of interest could be: by now only used for monitoring if "hci0" shows up or not hcitool dev bluetoothctl list still not understanding how to maybe use them beyond above mentioned monitoring: bluetootctl hcitool hciattach - attach serial devices via UART HCI to BlueZ stack hciconfig- configure Bluetooth devices hcitool - configure Bluetooth connections hid2hci - Bluetooth HID to HCI mode switching utility btattach - attach serial devices to BlueZ stack btmgmt - A command-line interface of BlueZ for management obexctl - A command-line interface of BlueZ for OBEX (file transfer) The following tools demonstrate that in principal the driver is loaded all the time, right after reboot already: modinfo bluetooth I am also searching towards systemd maybe needing to do something, as I have found at least 4 systemd items which could be of interest, but also here I haven't succeeded with my investigations by now: systemctl status bluetooth.service systemctl status bluetooth.socket systemctl status systemd-rfkill.service systemctl status systemd-rfkill.socket
Re: which commands are executed by the "bluetooth enable" button?
Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. rfkill is working here, but you can also try this(working here too): $ dbus-send --system --dest=org.bluez --print-reply /org/bluez/hci0 org.freedesktop.DBus.Properties.Set string:org.bluez.Adapter1 string:Powered variant:boolean:true or false https://medium.com/@konchunas/how-to-toggle-bluetooth-with-shortcut-on-linux-the-proper-way-a440dd88605e -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. also bluez-tools can be useful -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
Il 29/04/20 16:23, Marco Möller ha scritto: On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though. you can take a look at /usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/Toolbar.qml -- Saluti, Luca Pedrielli
Re: which commands are executed by the "bluetooth enable" button?
On 29.04.20 10:15, luca.pedrielli wrote: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| Hmmm. I have no rfkill installed in my system. I may install it and try it out. The GUI button will know another trick, though.
Re: which commands are executed by the "bluetooth enable" button?
you can try: |#!/bin/bashifrfkill list bluetooth |grep -q 'yes$';thenrfkill unblock bluetooth elserfkill block bluetooth fi| https://askubuntu.com/questions/1144596/set-a-shortcut-to-toggle-bluetooth-on-or-off Il 28/04/20 23:03, Marco Möller ha scritto: There are two buttons for triggering Bluetooth availability by a mouse click, and they appear to do some magic. I would need to find out about this, I am searching for the commands which become executed by these buttons. After a reboot Bluetooth is still deactivated, and for activating it I can go here: System Settings - Network - Bluetooth There, I find emphasized by alarming color "Bluetooth is disabled" and next to it is then nicely provided an "Enable" button which perfectly works. After Bluetooth becomes activated in this way, then there appears the related System Tray icon in the panel of KDE Plasma, and from now on I can there deactivate Bluetooth, or activate it there again, forth and back, repeatedly, which works as expected. In another thread I asked how to set a keyboard shortcut for this activation/deactivation of Bluetooth, and quickly got the very helpful answer how to set the needed "custom shortcut" (Thanks, Helge!). However, the command which has to become executed by the shortcut troubles. It worked for Helge, but not for me, and the Internet is full about the problem and error message as I receive it. There obviously is something more going on behind this buttons, than simply calling the commands "bluetoothctl power on" or "bluetoothctl power off". I tested the "bluetoothctl" command interactively on a CLI as the user or with sudo and got with sub-command "devices" (and others) the error message: "No default controller available". The internet is full of questions about this and by now I could not find any good answer. There are suggestions that the problem would have been solved after a cold start (not simply a reboot), after driver re-installation, booting into Windows and back into Linux, and many more weird solutions. BUT: if I use the mouse in order to trigger the button, then bluetooth becomes enabled or disabled without any problems, forth and back, repeatedly. And if it first becomes enabled by the mouse click on the button, I then afterwards also succeed on the CLI with the commands given as a normal user "bluetoothctl power off" and "bluetoothctl power on", forth and back, repeatedly (and also the keyboard shortcut works for me, then). Once I use the mouse for deactivating Bluetooth by the button, then the bluetoothctl commands again fail with said error message. Obviously, the buttons know the magic trick how to activate/deactivate the communication with the present hardware at a state, when bluetoothctl cannot succeed to get access to the device. I should add, that "systemctl status bluetooth" confirms this service to all the time being active, and obviously there are no drivers or configurations missing - the buttons can do the job. So, nothing is missing but to find out which commands these buttons trigger. Well, I am now searching for this full series of commands, for achieving on the CLI the same result as these buttons are doing it. Could you help? Marco. -- Saluti, Luca Pedrielli
which commands are executed by the "bluetooth enable" button?
There are two buttons for triggering Bluetooth availability by a mouse click, and they appear to do some magic. I would need to find out about this, I am searching for the commands which become executed by these buttons. After a reboot Bluetooth is still deactivated, and for activating it I can go here: System Settings - Network - Bluetooth There, I find emphasized by alarming color "Bluetooth is disabled" and next to it is then nicely provided an "Enable" button which perfectly works. After Bluetooth becomes activated in this way, then there appears the related System Tray icon in the panel of KDE Plasma, and from now on I can there deactivate Bluetooth, or activate it there again, forth and back, repeatedly, which works as expected. In another thread I asked how to set a keyboard shortcut for this activation/deactivation of Bluetooth, and quickly got the very helpful answer how to set the needed "custom shortcut" (Thanks, Helge!). However, the command which has to become executed by the shortcut troubles. It worked for Helge, but not for me, and the Internet is full about the problem and error message as I receive it. There obviously is something more going on behind this buttons, than simply calling the commands "bluetoothctl power on" or "bluetoothctl power off". I tested the "bluetoothctl" command interactively on a CLI as the user or with sudo and got with sub-command "devices" (and others) the error message: "No default controller available". The internet is full of questions about this and by now I could not find any good answer. There are suggestions that the problem would have been solved after a cold start (not simply a reboot), after driver re-installation, booting into Windows and back into Linux, and many more weird solutions. BUT: if I use the mouse in order to trigger the button, then bluetooth becomes enabled or disabled without any problems, forth and back, repeatedly. And if it first becomes enabled by the mouse click on the button, I then afterwards also succeed on the CLI with the commands given as a normal user "bluetoothctl power off" and "bluetoothctl power on", forth and back, repeatedly (and also the keyboard shortcut works for me, then). Once I use the mouse for deactivating Bluetooth by the button, then the bluetoothctl commands again fail with said error message. Obviously, the buttons know the magic trick how to activate/deactivate the communication with the present hardware at a state, when bluetoothctl cannot succeed to get access to the device. I should add, that "systemctl status bluetooth" confirms this service to all the time being active, and obviously there are no drivers or configurations missing - the buttons can do the job. So, nothing is missing but to find out which commands these buttons trigger. Well, I am now searching for this full series of commands, for achieving on the CLI the same result as these buttons are doing it. Could you help? Marco.
Re: after latest updates dolphin->share->send via bluetooth stops working
Il 18/10/19 18:41, Alex DEKKER ha scritto: On 18/10/2019 17:11, luca pedrielli wrote: file:///usr/share/purpose/bluetoothplugin_config.qml:20:1: module "QtQuick.Controls" version 2.5 is not installed Any output from: dpkg -l | grep quick-controls ? alexd as a workaround I changed the import QtQuick.Controls 2.5 to import QtQuick.Controls 2.4 in /usr/share/purpose/bluetoothplugin_config.qml waiting for latest quick-controls -- Saluti, Luca Pedrielli
Re: after latest updates dolphin->share->send via bluetooth stops working
Il 18/10/19 18:41, Alex DEKKER ha scritto: On 18/10/2019 17:11, luca pedrielli wrote: file:///usr/share/purpose/bluetoothplugin_config.qml:20:1: module "QtQuick.Controls" version 2.5 is not installed Any output from: dpkg -l | grep quick-controls ? alexd $ dpkg -l | grep quick-controls ii qml-module-qtquick-controls:amd64 5.11.3-2 amd64 Qt 5 Quick Controls QML module ii qml-module-qtquick-controls-styles-breeze 4:5.14.5-2 amd64 QtQuick style for Qt and KDE Software ii qml-module-qtquick-controls2:amd64 5.11.3+dfsg-2 amd64 Qt 5 Qt Quick Controls 2 QML module I think that bluetoothplugin_config.qml search for a 2.5 version, but a 1.1 is installed Luca.
Re: after latest updates dolphin->share->send via bluetooth stops working
On 18/10/2019 17:11, luca pedrielli wrote: file:///usr/share/purpose/bluetoothplugin_config.qml:20:1: module "QtQuick.Controls" version 2.5 is not installed Any output from: dpkg -l | grep quick-controls ? alexd
after latest updates dolphin->share->send via bluetooth stops working
Hi, today i tried to send via bluetooth an image with dolphin->share->send via bt but only a blank panel appears. in .xsession-errors: --- qrc:/JobDialog.qml:28: TypeError: Cannot read property 'pluginName' of undefined missing mandatory argument "device" missing mandatory argument "device" file:///usr/share/purpose/bluetoothplugin_config.qml:20:1: module "QtQuick.Controls" version 2.5 is not installed qrc:/org/kde/purpose/PurposeWizard.qml:40: TypeError: Type error --- still working in buster. Best, Luca.
Re: bluetooth, PA, annoying issues
On Sunday, May 5, 2019 1:55:26 AM CEST Lisandro Damián Nicanor Pérez Meyer wrote: > El domingo, 10 de marzo de 2019 12:57:22 -03 inkbottle escribió: > > Since a fortnight or so, I have glitches with BT headset connection, which > > otherwise has worked flawlessly for a year or more. > > > > The connection is usually OK. However quite often, when I turn on the > > headset, the BT Plasma icon is changing its aspect as it should (adding 2 > > small dots on each side), but the headset doesn't say "device connected", > > and the headset is not showing in PA available devices, and if I go in > > Settings/Bluetooth, the device is not trusted, and sometimes also not > > present at all (this latter part, in this situation, would even change > > within seconds). And there are also plenty of other things, anyway. > > > > The angle I would like to consider, is that the issue appeared together > > with > > a nice looking enhancement: > Well, I'm also seeing this. It also happen with GTK's blueman, but always > inside a Plasma session. Sometime I need to reset the device in order to > make it work. > > But I doubt it's a Plasma-related thing, although I should do a better > check... With time it seems the issue sort of wore off (however my last upgrade dates from the beginning of the soft freeze or so). Devices are still sometime forgotten but not a big issue. Beside that I now have A2DP without interruption or latency which is great. The connection is much more stable now and is resilient to signal degradation. If I move away from the computer with my headset, until the signal is degraded, and then come back, there is no loss of synchronization (I tried only once). And the distance beyond which the signal is becoming too weak, was previously 2 meters or less, and is now more like 5 meters or more.
Re: bluetooth, PA, annoying issues
El domingo, 10 de marzo de 2019 12:57:22 -03 inkbottle escribió: > Since a fortnight or so, I have glitches with BT headset connection, which > otherwise has worked flawlessly for a year or more. > > The connection is usually OK. However quite often, when I turn on the > headset, the BT Plasma icon is changing its aspect as it should (adding 2 > small dots on each side), but the headset doesn't say "device connected", > and the headset is not showing in PA available devices, and if I go in > Settings/Bluetooth, the device is not trusted, and sometimes also not > present at all (this latter part, in this situation, would even change > within seconds). And there are also plenty of other things, anyway. > > The angle I would like to consider, is that the issue appeared together with > a nice looking enhancement: Well, I'm also seeing this. It also happen with GTK's blueman, but always inside a Plasma session. Sometime I need to reset the device in order to make it work. But I doubt it's a Plasma-related thing, although I should do a better check... -- Alas, I am dying beyond my means. Oscar Wilde, as he sipped champagne on his deathbed Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
bluetooth, PA, annoying issues
Since a fortnight or so, I have glitches with BT headset connection, which otherwise has worked flawlessly for a year or more. The connection is usually OK. However quite often, when I turn on the headset, the BT Plasma icon is changing its aspect as it should (adding 2 small dots on each side), but the headset doesn't say "device connected", and the headset is not showing in PA available devices, and if I go in Settings/Bluetooth, the device is not trusted, and sometimes also not present at all (this latter part, in this situation, would even change within seconds). And there are also plenty of other things, anyway. The angle I would like to consider, is that the issue appeared together with a nice looking enhancement: When I boot the computer and then later turn on the headset, I always have a nice looking popup: (screenshot attached) "XXX is requesting access to this computer" Very nice looking indeed, though not very relevant, since I already authorized the access. What I'm wondering is *why am I seeing that only since 2 weeks ago*, though googling the above sentence shows me it's from a 3 y.o. commit: https://github.com/KDE/bluedevil/blob/master/src/kded/helpers/requestauthorization.cpp[1] It seems the message has every bits of the function: RequestAuthorization lines 31 to 58. Bottom line: There has been a regression on my system, in the BT/PA thingy. This appeared together with the awesome looking messages described above. How come I see the outcomes of a 3yo commit only now? Could the code had been uploaded to debian repo recently? Could the code had been triggered by other changes? Best, Chris [1] https://github.com/KDE/bluedevil/blob/master/src/kded/helpers/requestauthorization.cpp
Bug#906783: bluedevil: Bluedevil is not able to add new bluetooth devices.
Package: bluedevil Version: 4:5.8.4-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-7-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluedevil depends on: ii bluez5.43-2+deb9u1 ii bluez-obexd 6.43-2+deb9u1 ii kio 5.28.0-2 ii libc62.24-11+deb9u3 ii libkf5bluezqt6 5.28.0-1 ii libkf5configcore55.28.0-2 ii libkf5configgui5 5.28.0-2 ii libkf5configwidgets5 5.28.0-2 ii libkf5coreaddons55.28.0-2 ii libkf5dbusaddons55.28.0-1 ii libkf5i18n5 5.28.0-2 ii libkf5iconthemes55.28.0-2 ii libkf5kiocore5 5.28.0-2 ii libkf5kiofilewidgets55.28.0-2 ii libkf5kiowidgets55.28.0-2 ii libkf5notifications5 5.28.0-1 ii libkf5widgetsaddons5 5.28.0-3 ii libkf5windowsystem5 5.28.0-2 ii libqt5core5a 5.7.1+dfsg-3+b1 ii libqt5dbus5 5.7.1+dfsg-3+b1 ii libqt5gui5 5.7.1+dfsg-3+b1 ii libqt5qml5 5.7.1-2+b2 ii libqt5widgets5 5.7.1+dfsg-3+b1 ii libstdc++6 6.3.0-18+deb9u1 ii plasma-framework 5.28.0-2 ii qml-module-org-kde-bluezqt 5.28.0-1 ii qml-module-org-kde-kio 5.28.0-1 ii qml-module-org-kde-kquickcontrolsaddons 5.28.0-1 ii qml-module-qtquick-layouts 5.7.1-2+b2 ii qml-module-qtquick2 5.7.1-2+b2 bluedevil recommends no packages. Versions of packages bluedevil suggests: ii pulseaudio-module-bluetooth 10.0-1+deb9u1 -- no debconf information
please have pulseaudio-module-bluetooth recommended for installation
If only a knew that installing pulseaudio-module-bluetooth will make kde bluetooth thing play audio from my phone to my pc. Please make the package recommended (or even dependency? )so other users can have knowledge of this functionality Thank you for your work on debian and kde.
Bug#594883: marked as done (bluedevil: BlueDevil applet crash when reconnect to a bluetooth mouse)
Your message dated Sun, 28 May 2017 19:43:24 +0200 with message-id <20170528174236.5etyypvqzun23...@neoptolemo.gnuservers.com.ar> and subject line Re: Bug#594883: Perhaps conflict with kbluetooth (may be solved) has caused the Debian Bug report #594883, regarding bluedevil: BlueDevil applet crash when reconnect to a bluetooth mouse to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 594883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bluedevil Version: 1.0~rc2-1 Severity: normal Hi, It happen when re-enabling my mouse (Logitech Bluetooth Laser Travel Mouse)... I can reproduce it every time : - poweroff the mouse, - disable bluetooth with rfkill switch (or put the computer in stand by), - re-enable it, - when icon re-appear in systray, power on the mouse BlueDevil applet will crash at that step ! Regards Mourad -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluedevil depends on: ii bluez 4.69-1 Bluetooth tools and daemons ii kdebase-runtime 4:4.4.5-1 runtime components from the offici ii libbluedevil1 1.7+dfsg-1 A Qt wrapper for bluez ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libkdecore5 4:4.4.5-1 the KDE Platform Core Library ii libkdeui5 4:4.4.5-1 the KDE Platform User Interface Li ii libkfile4 4:4.4.5-1 the File Selection Dialog Library ii libkio5 4:4.4.5-1 the Network-enabled File Managemen ii libqt4-dbus 4:4.6.3-1 Qt 4 D-Bus module ii libqtcore44:4.6.3-1 Qt 4 core module ii libqtgui4 4:4.6.3-1 Qt 4 GUI module ii libstdc++64.4.4-11 The GNU Standard C++ Library v3 ii obex-data-server 0.4.5-1+b1 D-Bus service for OBEX client and ii obexd-client 0.28-1 D-Bus OBEX client bluedevil recommends no packages. Versions of packages bluedevil suggests: ii bluez-alsa4.69-1 Bluetooth ALSA support -- no debconf information --- End Message --- --- Begin Message --- ¡Hola newbeewan! El 2010-09-02 a las 09:07 +0200, newbeewan escribió: I solve that issue by removing kbluetooth (1:0.4.2-3), no more crash with bluedevil ! I think it would be better to add that conflict in the package controls to prevent that issue... This is a really old issue. Since this was last reported kbluetooth has been completely removed from the archive. bluedevil has also matured and I would expect it not to crash when there is another bluetooth "handler" running. Based on this, I'm closing the issue, please reopen if you can still reproduce it. Happy hacking, -- "There are only two things wrong with C++: The initial concept and the implementation." -- Bertrand Meyer Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#793037: marked as done (no more bluetooth since upgrade to 4:5.3.2-1)
Your message dated Tue, 16 May 2017 17:23:22 +0200 with message-id <20170516152321.qqw6xjnygif3u...@gnuservers.com.ar> and subject line Re: Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1 has caused the Debian Bug report #793037, regarding no more bluetooth since upgrade to 4:5.3.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bluedevil Version: 4:5.3.2-1 Severity: normal Since upgrade 2.0~rc1-44-gb7697a7-3 -> 4:5.3.2-1 I have no more access to bluetooth either in system setting or system tray. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (700, 'oldstable-proposed-updates'), (600, 'stable'), (500, 'proposed-updates'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluedevil depends on: ii bluez 5.23-2+b1 ii bluez-obexd 5.23-2+b1 ii libc6 2.19-18 ii libkf5bluezqt5 5.3.1-1 ii libkf5completion5 5.12.0-1 ii libkf5configcore5 5.12.0-1 ii libkf5configgui55.12.0-1 ii libkf5configwidgets55.12.0-1 ii libkf5coreaddons5 5.12.0-1 ii libkf5dbusaddons5 5.12.0-1 ii libkf5i18n5 5.12.0-1 ii libkf5iconthemes5 5.12.0-1 ii libkf5kiocore5 5.12.0-1 ii libkf5kiofilewidgets5 5.12.0-1 ii libkf5kiowidgets5 5.12.0-1 ii libkf5notifications55.12.0-1 ii libkf5widgetsaddons55.12.0-1 ii libqt5core5a5.4.2+dfsg-4 ii libqt5dbus5 5.4.2+dfsg-4 ii libqt5gui5 5.4.2+dfsg-4 ii libqt5qml5 5.4.2-3 ii libqt5widgets5 5.4.2+dfsg-4 ii libstdc++6 5.1.1-14 ii obex-data-server0.4.5-1+b4 ii qml-module-org-kde-bluezqt 5.3.1-1 bluedevil recommends no packages. Versions of packages bluedevil suggests: ii bluez-alsa 4.101-4.1 -- no debconf information --- End Message --- --- Begin Message --- ¡Hola Alexandre! El 2015-07-24 a las 00:22 -0300, Alexandre Pereira Nunes escribió: On Thu, Jul 23, 2015 at 2:47 PM, Jeremy Lainé <jeremy.la...@m4x.org> wrote: On 07/23/2015 02:36 PM, Alexandre Pereira Nunes wrote: > Package: bluedevil > Version: 4:5.3.2-1 > Followup-For: Bug #793037 > In my system, the tray icon is missing, but I can still access bluetooth > settings in the configuration panel. Are you running plasma-desktop 5.3.2? I wasn't at the time of my report. Now I am, and the bluetooth tray icon is there, as well as the configuration options. I'm closing the issue as it seems that the issue solved itself. The only weird issue is that I had to install kwin-x11 by hand. This is a different issue, I think this was already solved. Happy hacking, -- "Las computadoras son inútiles, solo pueden darte respuestas." -- Pablo Picasso Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Bug#627070: marked as done (Bluetooth not usable any more in Squeeze)
Your message dated Mon, 13 Mar 2017 16:40:31 +0100 with message-id <20170313154017.po7duljxrxrvo...@gnuservers.com.ar> and subject line Re: Bug#597003: It happens to me with the new bluez 4.91 has caused the Debian Bug report #597003, regarding Bluetooth not usable any more in Squeeze to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 597003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kdebluetooth Version: 1:1.0~rc3-2 Justification: renders package unusable Severity: grave *** Please type your report below this line *** In KDE3 bluetooth connection to mobile devices was working with nearly no problems. Now in KDE4 / Squeeze it does not work any more. The are only some rudimentary functionality that works on the shell with bluetooth devices. My opinion is that's poor and not a progress for KDE. Working interfaces to other devices is basically for a desktop environment. Regards Karsten -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdebluetooth depends on: ii bluedevil 1.0~rc3-2 The KDE bluetooth stack kdebluetooth recommends no packages. kdebluetooth suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 4:5.2.0-1~ Hi, For quite sometime now bluedevil has became a part of KDE Plasma, and was migrated to use the KDE Frameworks 5, on top of qt5, which leaves little in common with the kde4 version this bug was originally reported to. As expected, I'm not being able to reproduce the issue reported here, so I'm closing the issue. Please, if you manage to reproduce the issue with a newer version of bluedevil create a new report, to avoid mixing the reports with kde4 versions. Happy hacking, -- "Any change looks terrible at first." -- Principle of Design Inertia Saludos /\/\ /\ >< `/ signature.asc Description: PGP signature --- End Message ---
Re: plasma5 timeout with bluetooth
Am 13.11.2015 um 18:56 schrieb Holger Schramm: > Am 13.11.2015 um 08:16 schrieb Matthias Bodenbinder: >> Hi, >> >> my plasma5 is hanging for ca. 50 s after login when bluetooth is enabled. As >> soon as I do "systemctl disable bluetooth.service" the login proceeds just >> fine. As soon as I do "systemctl enable bluetooth.service" I have to wait >> for about 50 s. >> >> The log file says: >> >> Nov 13 08:07:16 rakete dbus[1270]: [system] Activating via systemd: service >> name='org.bluez' unit='dbus-org.bluez.service' >> Nov 13 08:07:41 rakete dbus[1270]: [system] Failed to activate service >> 'org.bluez': timed out >> Nov 13 08:07:41 rakete dbus[1270]: [system] Activating via systemd: service >> name='org.bluez' unit='dbus-org.bluez.service' >> Nov 13 08:08:06 rakete dbus[1270]: [system] Failed to activate service >> 'org.bluez': timed out >> >> The background service "bluetooth" in plasma5 systemsettings is disabled. It >> looks like plasma5 is waiting for this service in any case. > > It sounds like this bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 > Yes, thank you. This eventually explains why the bluetooth service is not starting. But it does not explain why plasma5 is waiting 50 s for this service. XFCE and cinnamon are starting just fine. So i can not understand why plasma5 behaves like that. Matthias
Re: plasma5 timeout with bluetooth
Am 13.11.2015 um 08:16 schrieb Matthias Bodenbinder: > Hi, > > my plasma5 is hanging for ca. 50 s after login when bluetooth is enabled. As > soon as I do "systemctl disable bluetooth.service" the login proceeds just > fine. As soon as I do "systemctl enable bluetooth.service" I have to wait for > about 50 s. > > The log file says: > > Nov 13 08:07:16 rakete dbus[1270]: [system] Activating via systemd: service > name='org.bluez' unit='dbus-org.bluez.service' > Nov 13 08:07:41 rakete dbus[1270]: [system] Failed to activate service > 'org.bluez': timed out > Nov 13 08:07:41 rakete dbus[1270]: [system] Activating via systemd: service > name='org.bluez' unit='dbus-org.bluez.service' > Nov 13 08:08:06 rakete dbus[1270]: [system] Failed to activate service > 'org.bluez': timed out > > The background service "bluetooth" in plasma5 systemsettings is disabled. It > looks like plasma5 is waiting for this service in any case. It sounds like this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 -- Holger
Re: plasma5 timeout with bluetooth
Hi, >> It sounds like this bug: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804908 > > Yes, thank you. This eventually explains why the bluetooth service is not > starting. > > But it does not explain why plasma5 is waiting 50 s for this service. > XFCE and cinnamon are starting just fine. So i can not understand why plasma5 > behaves like that. https://bugs.kde.org/show_bug.cgi?id=354230 https://git.reviewboard.kde.org/r/125785/ https://quickgit.kde.org/?p=plasma-nm.git=commit=48a45eb Best wishes, Boris
plasma5 timeout with bluetooth
Hi, my plasma5 is hanging for ca. 50 s after login when bluetooth is enabled. As soon as I do "systemctl disable bluetooth.service" the login proceeds just fine. As soon as I do "systemctl enable bluetooth.service" I have to wait for about 50 s. The log file says: Nov 13 08:07:16 rakete dbus[1270]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 13 08:07:41 rakete dbus[1270]: [system] Failed to activate service 'org.bluez': timed out Nov 13 08:07:41 rakete dbus[1270]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Nov 13 08:08:06 rakete dbus[1270]: [system] Failed to activate service 'org.bluez': timed out The background service "bluetooth" in plasma5 systemsettings is disabled. It looks like plasma5 is waiting for this service in any case. Kind Regards Matthias
Bug#798664: marked as done (plasma-desktop: KIO QML dependency missing for bluetooth applet)
Your message dated Tue, 06 Oct 2015 07:21:53 + with message-id <e1zjmzn-0005lp...@franck.debian.org> and subject line Bug#798664: fixed in plasma-desktop 4:5.4.2-1 has caused the Debian Bug report #798664, regarding plasma-desktop: KIO QML dependency missing for bluetooth applet to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 798664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plasma-desktop Version: 4:5.4.0-2 Severity: normal Dear Maintainer, After installing KDE5-based Plasma, the Bluetooth applet shows an error (see attached screenshot). Only after installing some more applets (which drags in the KIO QML package), the applet now works fine. Kind regards, Ralf -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-desktop depends on: ii breeze 4:5.4.0-1 ii kactivities 5.13.0-1 ii kde-cli-tools 4:5.4.0-1 ii kded5 5.13.0-1 ii libc6 2.19-19 ii libcanberra00.30-2.1 ii libfontconfig1 2.11.0-6.3 ii libgcc1 1:5.2.1-16 ii libkf5activities5 5.13.0-1 ii libkf5activitiesexperimentalstats1 4:5.4.0-2 ii libkf5archive5 5.13.0-1 ii libkf5auth5 5.13.0-1 ii libkf5baloo15.9.2-3+b1 ii libkf5bookmarks55.13.0-1 ii libkf5codecs5 5.13.0-1 ii libkf5completion5 5.13.0-1 ii libkf5configcore5 5.13.0-1 ii libkf5configgui55.13.0-1 ii libkf5configwidgets55.13.0-2 ii libkf5coreaddons5 5.13.0-1 ii libkf5dbusaddons5 5.13.0-1 ii libkf5emoticons55.13.0-1 ii libkf5globalaccel5 5.13.0-2 ii libkf5guiaddons55.13.0-1 ii libkf5i18n5 5.13.0-1 ii libkf5iconthemes5 5.13.0-1 ii libkf5itemviews55.13.0-1 ii libkf5jobwidgets5 5.13.0-1 ii libkf5kcmutils5 5.13.0-1 ii libkf5kdelibs4support5 5.13.0-3 ii libkf5kiocore5 5.13.0-1 ii libkf5kiofilewidgets5 5.13.0-1 ii libkf5kiowidgets5 5.13.0-1 ii libkf5newstuff5 5.13.0-1 ii libkf5notifications55.13.0-1 ii libkf5notifyconfig5 5.13.0-1 ii libkf5parts55.13.0-1 ii libkf5people5 5.13.0-1 ii libkf5peoplewidgets55.13.0-1 ii libkf5plasma5 5.13.0-1 ii libkf5plasmaquick5 5.13.0-1 ii libkf5quickaddons5 5.13.0-1 ii libkf5runner5 5.13.0-1 ii libkf5service5 5.13.0-2 ii libkf5solid55.13.0-1 ii libkf5sonnetui5 5.13.0-1 ii libkf5wallet5 5.13.0-1 ii libkf5widgetsaddons55.13.0-1 ii libkf5windowsystem5 5.13.0-3 ii libkf5xmlgui5 5.13.0-1 ii libkfontinst5 4:5.4.0-2 ii libkfontinstui5 4:5.4.0-2 ii libkworkspace5-54:5.3.2-4+b1 ii libphonon4qt5-4 4:4.8.3-2 ii libpulse-mainloop-glib0 6.0-5 ii libpulse0 6.0-5 ii libqt5concurrent5 5.5.0+dfsg-6 ii libqt5core5a5.5.0+dfsg-6 ii libqt5dbus5 5.5.0+dfsg-6 ii libqt5gui5 5.5.0+dfsg-6 ii libqt5network5 5.5.0+dfsg-6 ii libqt5printsupport5 5.5.0+dfsg-6 ii libqt5qml5 5.5.0-2 ii libqt5quick55.5.0-2 ii libqt5svg5 5.5.0-1 ii libqt5widgets5 5.5.0+dfsg-6 ii libqt5x11extras55.5.0-1 ii libqt5xml5 5.5.0+dfsg-6 ii libs
Processed: Re: Bug#798664: plasma-desktop: KIO QML dependency missing for bluetooth applet
Processing control commands: > reassign -1 bluedevil 4:5.4.0-1 Bug #798664 [plasma-desktop] plasma-desktop: KIO QML dependency missing for bluetooth applet Bug reassigned from package 'plasma-desktop' to 'bluedevil'. No longer marked as found in versions plasma-desktop/4:5.4.0-2. Ignoring request to alter fixed versions of bug #798664 to the same values previously set Bug #798664 [bluedevil] plasma-desktop: KIO QML dependency missing for bluetooth applet Marked as found in versions bluedevil/4:5.4.0-1. > fixed -1 4:5.4.1-2 Bug #798664 [bluedevil] plasma-desktop: KIO QML dependency missing for bluetooth applet Marked as fixed in versions bluedevil/4:5.4.1-2. -- 798664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#798664: plasma-desktop: KIO QML dependency missing for bluetooth applet
Control: reassign -1 bluedevil 4:5.4.0-1 Control: fixed -1 4:5.4.1-2 Hi, On 11/09/15 17:05, Ralf Jung wrote: > After installing KDE5-based Plasma, the Bluetooth applet shows an error (see > attached screenshot). > Only after installing some more applets (which drags in the KIO QML package), > the applet now works fine. The missing dependency was added to bluedevil by Felix Geyer in the latest upload. Thanks for reporting. Happy hacking, -- "The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time." -- Tom Cargill Saludos /\/\ /\ >< `/ signature.asc Description: OpenPGP digital signature
Bug#798664: plasma-desktop: KIO QML dependency missing for bluetooth applet
Package: plasma-desktop Version: 4:5.4.0-2 Severity: normal Dear Maintainer, After installing KDE5-based Plasma, the Bluetooth applet shows an error (see attached screenshot). Only after installing some more applets (which drags in the KIO QML package), the applet now works fine. Kind regards, Ralf -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages plasma-desktop depends on: ii breeze 4:5.4.0-1 ii kactivities 5.13.0-1 ii kde-cli-tools 4:5.4.0-1 ii kded5 5.13.0-1 ii libc6 2.19-19 ii libcanberra00.30-2.1 ii libfontconfig1 2.11.0-6.3 ii libgcc1 1:5.2.1-16 ii libkf5activities5 5.13.0-1 ii libkf5activitiesexperimentalstats1 4:5.4.0-2 ii libkf5archive5 5.13.0-1 ii libkf5auth5 5.13.0-1 ii libkf5baloo15.9.2-3+b1 ii libkf5bookmarks55.13.0-1 ii libkf5codecs5 5.13.0-1 ii libkf5completion5 5.13.0-1 ii libkf5configcore5 5.13.0-1 ii libkf5configgui55.13.0-1 ii libkf5configwidgets55.13.0-2 ii libkf5coreaddons5 5.13.0-1 ii libkf5dbusaddons5 5.13.0-1 ii libkf5emoticons55.13.0-1 ii libkf5globalaccel5 5.13.0-2 ii libkf5guiaddons55.13.0-1 ii libkf5i18n5 5.13.0-1 ii libkf5iconthemes5 5.13.0-1 ii libkf5itemviews55.13.0-1 ii libkf5jobwidgets5 5.13.0-1 ii libkf5kcmutils5 5.13.0-1 ii libkf5kdelibs4support5 5.13.0-3 ii libkf5kiocore5 5.13.0-1 ii libkf5kiofilewidgets5 5.13.0-1 ii libkf5kiowidgets5 5.13.0-1 ii libkf5newstuff5 5.13.0-1 ii libkf5notifications55.13.0-1 ii libkf5notifyconfig5 5.13.0-1 ii libkf5parts55.13.0-1 ii libkf5people5 5.13.0-1 ii libkf5peoplewidgets55.13.0-1 ii libkf5plasma5 5.13.0-1 ii libkf5plasmaquick5 5.13.0-1 ii libkf5quickaddons5 5.13.0-1 ii libkf5runner5 5.13.0-1 ii libkf5service5 5.13.0-2 ii libkf5solid55.13.0-1 ii libkf5sonnetui5 5.13.0-1 ii libkf5wallet5 5.13.0-1 ii libkf5widgetsaddons55.13.0-1 ii libkf5windowsystem5 5.13.0-3 ii libkf5xmlgui5 5.13.0-1 ii libkfontinst5 4:5.4.0-2 ii libkfontinstui5 4:5.4.0-2 ii libkworkspace5-54:5.3.2-4+b1 ii libphonon4qt5-4 4:4.8.3-2 ii libpulse-mainloop-glib0 6.0-5 ii libpulse0 6.0-5 ii libqt5concurrent5 5.5.0+dfsg-6 ii libqt5core5a5.5.0+dfsg-6 ii libqt5dbus5 5.5.0+dfsg-6 ii libqt5gui5 5.5.0+dfsg-6 ii libqt5network5 5.5.0+dfsg-6 ii libqt5printsupport5 5.5.0+dfsg-6 ii libqt5qml5 5.5.0-2 ii libqt5quick55.5.0-2 ii libqt5svg5 5.5.0-1 ii libqt5widgets5 5.5.0+dfsg-6 ii libqt5x11extras55.5.0-1 ii libqt5xml5 5.5.0+dfsg-6 ii libstdc++6 5.2.1-16 ii libtaskmanager5 4:5.3.2-4+b1 ii libx11-62:1.6.3-1 ii libx11-xcb1 2:1.6.3-1 ii libxcb-record0 1.10-3+b1 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii libxcursor1 1:1.1.14-1+b1 ii libxfixes3 1:5.0.1-2+b2 ii libxi6 2:1.7.4-1+b2 ii libxkbfile1 1:1.0.8-1 ii oxygen-sounds 4:5.4.0-1 ii phonon4qt5 4:4.8.3-2 ii plasma-desktop-data 4:5.4.0-2 ii plasma-framework5.13.0-1 ii plasma-workspace4:5.3.2-4+b1 ii polkit-kde-agent-1 4:5.4.0-1 ii qml-module-org-kde-kwindowsystem
Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
On Thu, Jul 23, 2015 at 2:47 PM, Jeremy Lainé jeremy.la...@m4x.org wrote: On 07/23/2015 02:36 PM, Alexandre Pereira Nunes wrote: Package: bluedevil Version: 4:5.3.2-1 Followup-For: Bug #793037 In my system, the tray icon is missing, but I can still access bluetooth settings in the configuration panel. Are you running plasma-desktop 5.3.2? I wasn't at the time of my report. Now I am, and the bluetooth tray icon is there, as well as the configuration options. The only weird issue is that I had to install kwin-x11 by hand.
Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
Package: bluedevil Version: 4:5.3.2-1 Followup-For: Bug #793037 In my system, the tray icon is missing, but I can still access bluetooth settings in the configuration panel. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.3 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages bluedevil depends on: ii bluez 5.23-2+b1 ii bluez-obexd 5.23-2+b1 ii libc6 2.19-19 ii libkf5bluezqt5 5.3.1-1 ii libkf5completion5 5.12.0-1 ii libkf5configcore5 5.12.0-1 ii libkf5configgui55.12.0-1 ii libkf5configwidgets55.12.0-1 ii libkf5coreaddons5 5.12.0-1 ii libkf5dbusaddons5 5.12.0-1 ii libkf5i18n5 5.12.0-1 ii libkf5iconthemes5 5.12.0-1 ii libkf5kiocore5 5.12.0-1 ii libkf5kiofilewidgets5 5.12.0-1 ii libkf5kiowidgets5 5.12.0-1 ii libkf5notifications55.12.0-1 ii libkf5widgetsaddons55.12.0-1 ii libqt5core5a5.4.2+dfsg-4 ii libqt5dbus5 5.4.2+dfsg-4 ii libqt5gui5 5.4.2+dfsg-4 ii libqt5qml5 5.4.2-3 ii libqt5widgets5 5.4.2+dfsg-4 ii libstdc++6 5.1.1-14 ii obex-data-server0.4.5-1+b4 ii qml-module-org-kde-bluezqt 5.3.1-1 bluedevil recommends no packages. Versions of packages bluedevil suggests: ii bluez-alsa 4.101-4.1 ii pulseaudio-module-bluetooth 6.0-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150723123634.2283.45812.reportbug@localhost
Re: Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
On 07/23/2015 02:36 PM, Alexandre Pereira Nunes wrote: Package: bluedevil Version: 4:5.3.2-1 Followup-For: Bug #793037 In my system, the tray icon is missing, but I can still access bluetooth settings in the configuration panel. Are you running plasma-desktop 5.3.2? -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55b12876.7000...@m4x.org
Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
On 07/23/2015 02:36 PM, Alexandre Pereira Nunes wrote: Package: bluedevil Version: 4:5.3.2-1 Followup-For: Bug #793037 In my system, the tray icon is missing, but I can still access bluetooth settings in the configuration panel. Are you running plasma-desktop 5.3.2? -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55b12898.7090...@m4x.org
Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
Package: bluedevil Version: 4:5.3.2-1 Followup-For: Bug #793037 Can confirm here. - No icon appears anymore on my taskbar. In fact, there is no Bluetooth Preferences module anywhere on KDE settings! - bluetooth:// URLs no longer work on applications such as Konqueror - My hardware still works under other DEs/BT managers (MATE/Blueman), and through console: tomman@himawari:~$ sudo hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 94:DB:C9:xx:xx:xx ACL MTU: 1022:8 SCO MTU: 121:3 UP RUNNING PSCAN ISCAN RX bytes:2561 acl:0 sco:0 events:136 errors:0 TX bytes:3942 acl:0 sco:0 commands:124 errors:0 tomman@himawari:~$ sudo hcitool scan Scanning ... 00:16:CF:xx:xx:xx tomman-lp-c2.tomman.net.ve (That's my other laptop, running Blueman) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluedevil depends on: ii bluez 5.23-2+b1 ii bluez-obexd 5.23-2+b1 ii libc6 2.19-18 ii libkf5bluezqt5 5.3.1-1 ii libkf5completion5 5.12.0-1 ii libkf5configcore5 5.12.0-1 ii libkf5configgui55.12.0-1 ii libkf5configwidgets55.12.0-1 ii libkf5coreaddons5 5.12.0-1 ii libkf5dbusaddons5 5.12.0-1 ii libkf5i18n5 5.12.0-1 ii libkf5iconthemes5 5.12.0-1 ii libkf5kiocore5 5.12.0-1 ii libkf5kiofilewidgets5 5.12.0-1 ii libkf5kiowidgets5 5.12.0-1 ii libkf5notifications55.12.0-1 ii libkf5widgetsaddons55.12.0-1 ii libqt5core5a5.4.2+dfsg-4 ii libqt5dbus5 5.4.2+dfsg-4 ii libqt5gui5 5.4.2+dfsg-4 ii libqt5qml5 5.4.2-3 ii libqt5widgets5 5.4.2+dfsg-4 ii libstdc++6 5.1.1-14 ii obex-data-server0.4.5-1+b4 ii qml-module-org-kde-bluezqt 5.3.1-1 bluedevil recommends no packages. Versions of packages bluedevil suggests: ii pulseaudio-module-bluetooth 6.0-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150721233055.4500.44320.report...@himawari.tomman.net.ve
Bug#793037: no more bluetooth since upgrade to 4:5.3.2-1
Package: bluedevil Version: 4:5.3.2-1 Severity: normal Since upgrade 2.0~rc1-44-gb7697a7-3 - 4:5.3.2-1 I have no more access to bluetooth either in system setting or system tray. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (700, 'oldstable-proposed-updates'), (600, 'stable'), (500, 'proposed-updates'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluedevil depends on: ii bluez 5.23-2+b1 ii bluez-obexd 5.23-2+b1 ii libc6 2.19-18 ii libkf5bluezqt5 5.3.1-1 ii libkf5completion5 5.12.0-1 ii libkf5configcore5 5.12.0-1 ii libkf5configgui55.12.0-1 ii libkf5configwidgets55.12.0-1 ii libkf5coreaddons5 5.12.0-1 ii libkf5dbusaddons5 5.12.0-1 ii libkf5i18n5 5.12.0-1 ii libkf5iconthemes5 5.12.0-1 ii libkf5kiocore5 5.12.0-1 ii libkf5kiofilewidgets5 5.12.0-1 ii libkf5kiowidgets5 5.12.0-1 ii libkf5notifications55.12.0-1 ii libkf5widgetsaddons55.12.0-1 ii libqt5core5a5.4.2+dfsg-4 ii libqt5dbus5 5.4.2+dfsg-4 ii libqt5gui5 5.4.2+dfsg-4 ii libqt5qml5 5.4.2-3 ii libqt5widgets5 5.4.2+dfsg-4 ii libstdc++6 5.1.1-14 ii obex-data-server0.4.5-1+b4 ii qml-module-org-kde-bluezqt 5.3.1-1 bluedevil recommends no packages. Versions of packages bluedevil suggests: ii bluez-alsa 4.101-4.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150720173712.3474.15212.report...@bibi.depot.rail.eu.org
Re: Bluetooth sound and KNotify
On 2015-06-29, newbee...@nativobject.net newbee...@nativobject.net wrote: When my bluetooth speakers are usable, all works well, but when I'm too far or if there are off, knotify crash and I can't change the sound configuration in the systemsettings center, it also crash... Backtraces, or it didn't happen. It is a while ago since I last used my bluetooth connected speakers (but my computer and speakers are only 4 meters (and a wall) between eachothers. /Sune -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/mnah25$b6k$1...@ger.gmane.org
Re: Bluetooth sound and KNotify
On Monday 29 June 2015 10:58:48 newbee...@nativobject.net wrote: Hi, I have some bluetooth speaker paired with my laptop [debian Jessie + testing]. When my bluetooth speakers are usable, all works well, but when I'm too far or if there are off, knotify crash and I can't change the sound configuration in the systemsettings center, it also crash... Is there any solution to avoid that and having my bluetooth configuration working when my bluetooth speakers are usable and au fallback to internal speakers when there are not ? Hi Mourad! I think you should really get in touch with upstream to see how to solve this. I hardly doubt this is a debian-only issue. Good luck! -- 16: De quien es Internet * De DIOS dado que todas las cosas del mundo le pertenecen Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bluetooth sound and KNotify
Hi, I have some bluetooth speaker paired with my laptop [debian Jessie + testing]. When my bluetooth speakers are usable, all works well, but when I'm too far or if there are off, knotify crash and I can't change the sound configuration in the systemsettings center, it also crash... Is there any solution to avoid that and having my bluetooth configuration working when my bluetooth speakers are usable and au fallback to internal speakers when there are not ? Regards Mourad -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/559108c8.2030...@nativobject.net
No more Bluetooth in kde Sid with bluez 5
Hi, Bluetooth does not work in kde Sid after update of bluez to 5, bluedevil 1.3 can't work with bluez 5, the packet bluedevil 2 can do it, is there any hope that this packet move from experimental to Sid? Best regard. Philippe Merlin -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2004649.f2ZgL4kkKW@portable
Re: No more Bluetooth in kde Sid with bluez 5
On 2014-07-14, MERLIN Philippe phil-deb1.mer...@laposte.net wrote: Hi, Bluetooth does not work in kde Sid after update of bluez to 5, bluedevil 1.3 can't work with bluez 5, the packet bluedevil 2 can do it, is there any hope that this packet move from experimental to Sid? Best regard. Philippe Merlin The amazing Didier Raboud did upload bluedevil2 to sid today. /Sune -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lq19un$t6l$1...@ger.gmane.org
Re: No more Bluetooth in kde Sid with bluez 5
Le lundi 14 juillet 2014, 19:10:15 Sune Vuorela a écrit : On 2014-07-14, MERLIN Philippe phil-deb1.mer...@laposte.net wrote: Hi, Bluetooth does not work in kde Sid after update of bluez to 5, bluedevil 1.3 can't work with bluez 5, the packet bluedevil 2 can do it, is there any hope that this packet move from experimental to Sid? Best regard. Philippe Merlin The amazing Didier Raboud did upload bluedevil2 to sid today. /Sune Thank you, its fine. Philippe Merlin -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3545523.DRDyuI2BWR@portable
Bug#487522: marked as done (send to bluetooth)
Your message dated Wed, 17 Mar 2010 22:40:28 +0100 with message-id 201003172240.28433.ewoer...@kde.org and subject line kedit gone has caused the Debian Bug report #487522, regarding send to bluetooth to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 487522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487522 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kedit Version: 4:3.5.9-1 Severity: wishlist Hi, how for send to mail, can U add send to bluetooth option? Thanks psycheye -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-annette (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kedit depends on: ii kdelibs4c2a 4:3.5.9.dfsg.1-4 core libraries and binaries for al ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.2.2-4GCC support library ii libqt3-mt 3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3 kedit recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 4:3.5.9-1+rm Kedit is no longer part of the actively developed parts of debian and has been removed upstream. ---End Message---
Re: KDE4 Bluetooth
On Sunday 25 October 2009 at 19:04:48, zakary Flores wrote: Hello, http://packages.debian.org/experimental/kdebluetooth Thanks for the info! Any idea why it's not yet in the testing repository? -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: KDE4 Bluetooth
Hello, On pirmadienis 26 Spalis 2009 20:05:08 Vincent Frison wrote: On Sunday 25 October 2009 at 19:04:48, zakary Flores wrote: Hello, http://packages.debian.org/experimental/kdebluetooth Thanks for the info! Any idea why it's not yet in the testing repository? Because maintainer thinks it is not ready for general consumption yet. -- Modestas Vainius modes...@vainius.eu signature.asc Description: This is a digitally signed message part.
Re: KDE4 Bluetooth
Am Montag 26 Oktober 2009 20:12:45 schrieb Modestas Vainius: Any idea why it's not yet in the testing repository? Because maintainer thinks it is not ready for general consumption yet. I think I've got to agree here. I tried it today but got got some crashes. Was only on a virtualbox guest system, so not always the easiest part, Achim signature.asc Description: This is a digitally signed message part.
Re: KDE4 Bluetooth
Hi, Is the KDE bluetooth framework still broken in KDE4? The kdebluetooth package from unstable seems to be for KDE3 only. In fact I think I managed to have kdebluetooth working on my KDE4 a few months ago. But now there's nothing I can do, no action are clickable from the kbluetooth systray! It's like I have no BT device on my laptop. But I can see that a BT device is detected by the kernel and I have all bluetooth and bluez* packages installed. Thanks for your help, Vincent. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: KDE4 Bluetooth
Hello, http://packages.debian.org/experimental/kdebluetooth 2009/10/25 Vincent Frison vincent.fri...@gmail.com Hi, Is the KDE bluetooth framework still broken in KDE4? The kdebluetooth package from unstable seems to be for KDE3 only. In fact I think I managed to have kdebluetooth working on my KDE4 a few months ago. But now there's nothing I can do, no action are clickable from the kbluetooth systray! It's like I have no BT device on my laptop. But I can see that a BT device is detected by the kernel and I have all bluetooth and bluez* packages installed. Thanks for your help, Vincent. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- GNU/Linux user #388803 Debian Squeeze/Sid Kernel 2.6.29-phenomx4 NVIDIA Kernel Module 185.18.31 Kde 4.3.2 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. Albert Einstein there really is no patch for human stupidity Mike Danseglio
KDE4 Bluetooth
As the KDE3 version of kbluetooth has almost completely ceased to function on kde 4.3 in testing, I decided to test out the version of kbluetooth4 that's in experimental. It appears to launch without trouble, but is unable to see any bluetooth devices. If I launch it from the console, I see the following diagnostic output: QDBusObjectPath: invalid path QDBusObjectPath: invalid path process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member GetProperties process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member RegisterAgent QDBusObjectPath: invalid path AGENT registered ! process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member GetProperties process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member GetProperties k...@fireman53:~$ process 28753: arguments to dbus_message_new_method_call() were incorrect, assertion path != NULL failed in file dbus-message.c line 1074. This is normally a bug in some application using the D-Bus library. QDBusConnection: error: could not send message to service org.bluez path interface org.bluez.Adapter member UnregisterAgent Setting my computer to be discoverable gives me the following messages: Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int) Object::connect: (receiver name: 'AdapterWidget') Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString) Object::connect: (receiver name: 'AdapterWidget') Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int) Object::connect: (receiver name: 'AdapterWidget') Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString) Object::connect: (receiver name: 'AdapterWidget') Agent Release Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int) Object::connect: (receiver name: 'AdapterWidget') Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString) Object::connect: (receiver name: 'AdapterWidget') Object::connect: No such signal Solid::Control::BluetoothInterface::discoverableTimeoutChanged(int) Object::connect: (receiver name: 'AdapterWidget') Object::connect: No such signal Solid::Control::BluetoothInterface::nameChanged(const QString) Object::connect: (receiver name: 'AdapterWidget') AGENT registered ! KCrash: Application 'kbluetooth4' crashing... As you can see, it crashed shortly after. Any ideas on what might be going wrong? Is there DBUS permission that I need to change? I'm already a part of both the bluetooth and netdev groups. Thanks -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bluetooth in KDE4
Any news on kde4 for bluetooth? regards, Uli -- --- ROAD ...the handyPC Company - - - ) ) ) Uli Luckas Head of Software Development ROAD GmbH Bennigsenstr. 14 | 12159 Berlin | Germany fon: +49 (30) 230069 - 62 | fax: +49 (30) 230069 - 69 url: www.road.de Amtsgericht Charlottenburg: HRB 96688 B Managing director: Hans-Peter Constien -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bluetooth in KDE4
El Viernes 10 Abril 2009 02:29:11 Mark Purcell escribió: Unfortunately KDE4 doesn't have the full functionality of KDE3 so if those features are critical then you should stick with KDE3 for the time being. There is some work on packaging the bluetooth stack for KDE4 for debian, but there are a few issues which require resolution. The best place to discuss this is (Cc:): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504109 This kdebluetooth4 status was asked a couple of time in the last 2 or 3 months by several people, and I don't remember anyone got an answer. Well, this info by Mark was the kind of feedback I was talking about in that long discussion few days ago. Most of us, users, aren't retarded, and can understand a brief and clear explanation like Mark's one. After this feedback I don't think any regular reader of this list will come up again asking what's up with kdebluetooth4 in a reasonable period. Thanks for the info, Mark. P.D: Of course I just want to laud Mark's attitude, not to start a new discussion. ¡¡PLEASE, NO!! ;-P -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bluetooth in KDE4
Manolete, ese artista... wrote: P.D: Of course I just want to laud Mark's attitude, not to start a new discussion. ¡¡PLEASE, NO!! ;-P A pity I didn't have this info last week, now going back to kde3 is near to impossible bluetooth has become something essential for a lot of us (printing, lan, etc) Michel. -- View this message in context: http://www.nabble.com/Bluetooth-in-KDE4-tp22980789p22995983.html Sent from the Debian KDE mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bluetooth in KDE4
Hello folks! Today I made a dist-upgrade in Sid and got KDE4 that way. Now I can not use Bluetooth properly in KDE4. There is no Plasmoid or widget that gives me access to blueZ (neither directly nor via solid). The kdebluetooth suite from KDE3 is able to find my bluetooth dongle and I can search for bluetooth devices through it, but I can't establish any connection because the KDE3 bluetooth stuff relies on kio-slaves that don't work anymore in KDE4. I have my printer connected to my laptop via bluetooth and I use bluetooth to synchronize my appointments and contacts between my mobile phone and my laptop. Nothing of this is possible at the moment with KDE4 in Sid although it was working flawlessly in KDE3.5. I've read that there is a package called kdebluetooth4 which provides at least basic bluetooth functionality for KDE4, but it is not available in Sid. Is there any chance that I'll be able to print again anytime soon? If you need any further information to help me, I'll be glad to answer any questions that will bring me further towards a solution to my problem(s). Bye and Happy Easter Martin Neumann a.k.a. Neumaennl -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bluetooth in KDE4
On Friday 10 April 2009 09:04:39 Martin Neumann wrote: Nothing of this is possible at the moment with KDE4 in Sid although it was working flawlessly in KDE3.5. Martin, Quite a few of us are using bluetooth as well. Unfortunately KDE4 doesn't have the full functionality of KDE3 so if those features are critical then you should stick with KDE3 for the time being. There is some work on packaging the bluetooth stack for KDE4 for debian, but there are a few issues which require resolution. The best place to discuss this is (Cc:): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504109 Mark signature.asc Description: This is a digitally signed message part.
Re: Bluetooth
Alle sabato 28 febbraio 2009, DVW ha scritto: Anyway it's a big handicap for Linux to be a real alternative to Windows this distro slavery. If just there were a really working aptitude-like app which allowed to install form sources and resolve dependencies and updates... Daydreaming, I suppose, but it would be nice. Cheers El Viernes, 27 de Febrero de 2009 12:20:42 Andreas v. Heydwolff escribió: It does exist: it's called Gentoo. But be aware of the fact that you must compile and set up everything by yourself. Bye Valerio
Re: Bluetooth
Hi all, just a quick reply from me to show up that there are more people interested in kdebluetooth4. I'm missing kdebluetooth4, too - would be great if you could package it! Thanks in advance Florian Am Wednesday 25 February 2009 schrieb Manolete, ese artista...: Is Kdebluetooth4 being packaged relatively soon? I've been seeing it in other distros since a couple of months, or so, and was wondering when would these nice Debian developers of us package it for the joy and felicity of all us, mortal users (who don't forget to mention ya'll in our night prayers, BTW), :D. Cheers. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bluetooth
Florian Jauernig wrote: Hi all, just a quick reply from me to show up that there are more people interested in kdebluetooth4. I'm missing kdebluetooth4, too - would be great if you could package it! Thanks in advance Florian Am Wednesday 25 February 2009 schrieb Manolete, ese artista...: Is Kdebluetooth4 being packaged relatively soon? I've been seeing it in other distros since a couple of months, or so, and was wondering when would these nice Debian developers of us package it for the joy and felicity of all us, mortal users (who don't forget to mention ya'll in our night prayers, BTW), :D. Cheers. Me too. Exporting kaddressbook to Nokia phones is an important function for me, currently executed through kaddressbook/etch 3.5.5 (3.5.9 had no export to mobile phone function). Gnokii works but kaddressbook cannot connect wth gnokii, presumably because kdebluethooth4 is broken in this regard. Greetings Andreas -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bluetooth
Glad to see I'm not the only one who would like to have a native KDE 4 app to make communicate my phone and PDA with my computer, :). Strangely it seems not many people in Debian seem to want the same; or perhaps there are some technical difficulties we aren't aware of :-/ These guys do a lot of effort; we all know that and are grateful to them. Anyway it's a big handicap for Linux to be a real alternative to Windows this distro slavery. If just there were a really working aptitude-like app which allowed to install form sources and resolve dependencies and updates... Daydreaming, I suppose, but it would be nice. Cheers El Viernes, 27 de Febrero de 2009 12:20:42 Andreas v. Heydwolff escribió: Florian Jauernig wrote: Hi all, just a quick reply from me to show up that there are more people interested in kdebluetooth4. I'm missing kdebluetooth4, too - would be great if you could package it! Thanks in advance Florian Am Wednesday 25 February 2009 schrieb Manolete, ese artista...: Is Kdebluetooth4 being packaged relatively soon? I've been seeing it in other distros since a couple of months, or so, and was wondering when would these nice Debian developers of us package it for the joy and felicity of all us, mortal users (who don't forget to mention ya'll in our night prayers, BTW), :D. Cheers. Me too. Exporting kaddressbook to Nokia phones is an important function for me, currently executed through kaddressbook/etch 3.5.5 (3.5.9 had no export to mobile phone function). Gnokii works but kaddressbook cannot connect wth gnokii, presumably because kdebluethooth4 is broken in this regard. Greetings Andreas -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bluetooth
Is Kdebluetooth4 being packaged relatively soon? I've been seeing it in other distros since a couple of months, or so, and was wondering when would these nice Debian developers of us package it for the joy and felicity of all us, mortal users (who don't forget to mention ya'll in our night prayers, BTW), :D. Cheers. -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508464: Send contact to bluetooth
Package: kontact Version: 4:3.5.9-5 Severity: wishlist Hi, is it possible add to kontact an option to send a contact (vcard) to bluetooth? Thanks Pol -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-annette (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kontact depends on: ii kdelibs4c2a 4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for al ii libc62.7-16 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1 GCC support library ii libkcal2b4:3.5.9-5 KDE calendaring library ii libkdepim1a 4:3.5.9-5 KDE PIM library ii libkpimidentitie 4:3.5.9-5 KDE PIM user identity information ii libqt3-mt3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.2-1 The GNU Standard C++ Library v3 Versions of packages kontact recommends: ii kaddressbook4:3.5.9-5KDE NG addressbook application ii kitchensync 4:3.5.5.dfsg.1-6 Synchronization framework ii kmail 4:3.5.9-5KDE Email client ii knode 4:3.5.9-5KDE news reader ii knotes 4:3.5.9-5KDE sticky notes ii korganizer 4:3.5.9-5KDE personal organizer Versions of packages kontact suggests: ii akregator 4:3.5.9-5 RSS feed aggregator for KDE pn gnokiinone (no description available) ii knewsticker 4:3.5.9-4 news ticker applet for KDE ii kpilot4:3.5.9-5 KDE Palm Pilot hot-sync tool ii kweather 4:3.5.9-2 weather display applet for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491580: RFP: kdebluetooth4 -- Bluetooth framework for KDE 4
Package: wnpp Severity: wishlist * Package name: kdebluetooth4 Version : 0.1 Upstream Author : Tom Patzig [EMAIL PROTECTED] * URL or Web page : http://bluetooth.kmobiletools.org * License : GPL Description : Bluetooth framework for KDE 4 This package adds Bluetooth capabilities to the KDE desktop. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487522: send to bluetooth
Package: kedit Version: 4:3.5.9-1 Severity: wishlist Hi, how for send to mail, can U add send to bluetooth option? Thanks psycheye -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.22-annette (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kedit depends on: ii kdelibs4c2a 4:3.5.9.dfsg.1-4 core libraries and binaries for al ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.2.2-4GCC support library ii libqt3-mt 3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.2.2-4 The GNU Standard C++ Library v3 kedit recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: bluetooth, KDE and NOKIA 6630
Hello Han, I'm experiment with this program http://extragear.kde.org/apps/kdebluetooth/ -ftp://ftp.debian.org/debian/pool/main/k/kdebluetooth- (see your english doc http://docs.kde.org/development/en/extragear-pim/kdebluetooth ) and gnokii http://www.gnokii.org/ -ftp://ftp.debian.org/debian/pool/main/g/gnokii/-. --- Han [EMAIL PROTECTED] escribió: I have a Nokia 6630 am running kde 3.5.2 I need to communicate with it: :-I need a data-suite that supports it with bluetooth or cable-usb support :-I need to pair it to my computer. i want to be able to browse the phone and even upload things to it i can archive this feture in windows even without the Nokia-date suite. I wonder if i can use kmobiletools but i dont have experience with it --PLEASE help i would if the list would have some sollutions to the following problems that have come about from trying to this and just wondering dose anyone know howto unlock a nokia 6630 (network unlock) Regards Toni Sort Antoni Bella Perez ## # http://www.terra.es/personal7/bella5/home.htm ## Correu-e : bella5 AT teleline DOT es ##, ## ID de Jabber: vasten AT jabber DOT org ## i col·laborador dels projectes: Debian en català: http://www.debian.org/international/Catalan/ KDE en català: http://l10n.kde.org/teams/infos.php?teamcode=ca T.P: http://www.iro.umontreal.ca/translation/registry.cgi?team=ca - __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
pairing bluetooth devices
does anypne know how to pair bluetooth devices using kbluetoothD please provide detailed instuctions as i have tried almost everything i know. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: pairing bluetooth devices
Am Sonntag, 7. Mai 2006 22:35 schrieb Han: does anypne know how to pair bluetooth devices using kbluetoothD please provide detailed instuctions as i have tried almost everything i know. And you also read the messages that pop up on the first start of kbluetoothd? I guess that you didn't as it tells you to set pin_helper /usr/lib/kdebluetooth/kbluepin; in /etc/bluetooth/hcid.conf (do not forget to restart hcid after that!) There are also other pin helpers, some even work with dbus, but the above is a good and working start. HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bluetooth, KDE and NOKIA 6630
I have a Nokia 6630 am running kde 3.5.2 I need to communicate with it: :-I need a data-suite that supports it with bluetooth or cable-usb support :-I need to pair it to my computer. i want to be able to browse the phone and even upload things to it i can archive this feture in windows even without the Nokia-date suite. I wonder if i can use kmobiletools but i dont have experience with it --PLEASE help i would if the list would have some sollutions to the following problems that have come about from trying to this and just wondering dose anyone know howto unlock a nokia 6630 (network unlock) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
