Discussion:
[arch-general] Cannot receive files via bluetooth
Peter Nabbefeld
2016-10-09 08:13:56 UTC
Permalink
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
Ralf Mardorf
2016-10-09 10:24:50 UTC
Permalink
Post by 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. :-(
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_files_are_created
[3]
https://git.archlinux.org/svntogit/community.git/tree/trunk/libvirt.install?h=packages/libvirt
Ralf Mardorf
2016-10-09 10:28:09 UTC
Permalink
Post by Ralf Mardorf
[1]
https://wiki.archlinux.org/index.php/Bluetooth#Bluetoothctl
Oops, wrong link, this should read
https://wiki.archlinux.org/index.php/Bluetooth .
Peter Nabbefeld
2016-10-09 12:12:08 UTC
Permalink
Hello,

changes are:
-rw-r--r-- 1 root root 514464 26. Sep 17:30
bluez-5.42-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 76128 26. Sep 17:30
bluez-libs-5.42-1-x86_64.pkg.tar.xz
-rw-r--r-- 1 root root 1007296 26. Sep 17:30
bluez-utils-5.42-1-x86_64.pkg.tar.xz

However, I'm not a bluetooth expert, so I cannot do much other than
trying out some minor changes without any advice.

Kind regards
Peter
Friedrich Strohmaier
2016-10-11 00:52:32 UTC
Permalink
Hi Peter, *,
Post by 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).
Post by Peter Nabbefeld
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
Ralf Mardorf
2016-10-11 05:44:40 UTC
Permalink
Post by Friedrich Strohmaier
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_duplicates

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_on_bugs

Regards,
Ralf
Jayesh Badwaik
2016-10-11 06:25:06 UTC
Permalink
Post by Friedrich Strohmaier
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
Ralf Mardorf
2016-10-11 06:40:58 UTC
Permalink
Post by Jayesh Badwaik
Post by Friedrich Strohmaier
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

Loading...