[arch-general] Cannot receive files via bluetooth
Hello, it seems some bluetooth has overwritten my bluetooth main.conf, as last change has been on September, 26th. Also, I cannot receive files any more, so I guess, I'd cahnaged sth. there. Unfortunately, I cannot remember, what changes I'd made in the past. :-( Could You probably tell me, what might cause the non-functioning file transfer? Sending files works, btw. Kind regards Peter
On Sun, 9 Oct 2016 10:13:56 +0200, Peter Nabbefeld wrote:
it seems some bluetooth has overwritten my bluetooth main.conf, as last change has been on September, 26th. Also, I cannot receive files any more, so I guess, I'd cahnaged sth. there. Unfortunately, I cannot remember, what changes I'd made in the past. :-(
Could You probably tell me, what might cause the non-functioning file transfer? Sending files works, btw.
Hi, I'm not a bluetooth user myself, but regarding the Arch Wiki there are several ways to get bluetooth working [1]. You should mention what you chose that stopped working and provide information you got by troubleshooting, resp. what you already tried to get rid of the issue [1b]. At least point out what "last change has been on September, 26th" and provide a link where you posted that "bluetooth main.conf". If upgrades provide new system wide configurations, they don't overwrite anything, they get installed as foo.config.pacnew and you get informed about this by the command line output [2]. It could be that you need to use a new config. Sometimes a config in $HOME might require editing, but then you usually would see a message by the upgrade's command line output, too. Not related to bluetooth, just an example for messages [3]. Regards, Ralf [1] https://wiki.archlinux.org/index.php/Bluetooth#Bluetoothctl [1b] https://wiki.archlinux.org/index.php/Bluetooth#Troubleshooting [2] https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave#Why_these_fil... [3] https://git.archlinux.org/svntogit/community.git/tree/trunk/libvirt.install?...
[1] https://wiki.archlinux.org/index.php/Bluetooth#Bluetoothctl
Oops, wrong link, this should read https://wiki.archlinux.org/index.php/Bluetooth .
Hi Peter, *, Am 09.10.2016 um 10:13 schrieb Peter Nabbefeld:
it seems some bluetooth has overwritten my bluetooth main.conf, as last change has been on September, 26th. Also, I cannot receive files any more, so I guess, I'd cahnaged sth. there. Unfortunately, I cannot remember, what changes I'd made in the past. :-(
same issue here. Reverting to bluez-5.41-2 resolved the issue (restarting the windowmanager/dbus helped to get it work again).
Could You probably tell me, what might cause the non-functioning file transfer? Sending files works, btw.
didn't test this one.. btw. I'm not shure, where to report the bug? - Arch bugtracker or - upstream any ideas regarding this -- Friedrich
On Tue, 11 Oct 2016 02:52:32 +0200, Friedrich Strohmaier wrote:
I'm not shure, where to report the bug? - Arch bugtracker or - upstream
any ideas regarding this
1. https://www.google.de/?gws_rd=ssl#q=arch+linux+report+bug 2. "Search for duplicates If you encounter a problem or desire a new feature, there is a high probability that someone else already had this problem or idea. If so, an appropriate bug report may already exist. In this case, please do not create a duplicate report; see #Following up on bugs instead." - https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Search_for_dup... 3. https://bugs.archlinux.org/proj1?do=index&string=bluez 4. https://bugs.archlinux.org/task/51284 5. https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Following_up_o... Regards, Ralf
On Tuesday, 11 October 2016 02:52:32 CEST Friedrich Strohmaier wrote:
btw. I'm not shure, where to report the bug? - Arch bugtracker or - upstream
any ideas regarding this
Report to ArchLinux Bug repository only if the bug is ArchLinux specific, that is, cause by ArchLinux build process. If the bug is instead in the upstream package and not ArchLinux, report upstream. -- Jayesh Badwaik
On Tue, 11 Oct 2016 08:25:06 +0200, Jayesh Badwaik wrote:
On Tuesday, 11 October 2016 02:52:32 CEST Friedrich Strohmaier wrote:
btw. I'm not shure, where to report the bug? - Arch bugtracker or - upstream
any ideas regarding this
Report to ArchLinux Bug repository only if the bug is ArchLinux specific, that is, cause by ArchLinux build process. If the bug is instead in the upstream package and not ArchLinux, report upstream.
The problem likely is, that he doesn't know what does cause the bug, the reason either is that the required troubleshooting wasn't done or because the troubleshooting doesn't lead to a pointer. However, as already pointed out by https://lists.archlinux.org/pipermail/arch-general/2016-October/042209.html , when following the guidelines the question is irrelevant, because the bug already is reported. Regards, Ralf
participants (4)
-
Friedrich Strohmaier
-
Jayesh Badwaik
-
Peter Nabbefeld
-
Ralf Mardorf