In data mercoledė 15 marzo 2023 12:31:13 CET, Stakanov ha scritto:
> In data sabato 11 marzo 2023 15:04:35 CET, Marco Calistri ha scritto:
> > Hello,
> >
> > I will not go to open another bug-report for this issue, since I guess
> > it being spread away on many different systems around, independently of
> > the specific hardware.
> >
> > Bluetooth file transfer in TW works only for an unidirectional way: from
> > external device to the computer and not vice-versa.
> >
> > rpm -qa|grep blue
> >
> > NetworkManager-bluetooth-1.42.2-1.1.x86_64
> > bluez-auto-enable-devices-5.66-1.4.noarch
> > kernel-firmware-bluetooth-20230210-1.1.noarch
> > bluez-firmware-1.2-150.1.x86_64
> > libbluetooth3-5.66-1.4.x86_64
> > bluez-obexd-5.66-1.4.x86_64
> > bluez-5.66-1.4.x86_64
> > bluez-cups-5.66-1.4.x86_64
> > thunar-sendto-blueman-2.3.5-1.1.noarch
> > blueman-lang-2.3.5-1.1.noarch
> > bluez-qt-imports-5.103.0-1.1.x86_64
> > blueman-2.3.5-1.1.x86_64
> >
> > How many users are having same issue?
> >
> > Regards,
>
> entropy@localhost:~> rpm -qa|grep blue
> bluez-obexd-5.66-1.4.x86_64
> bluez-5.66-1.4.x86_64
> bluez-qt-imports-5.104.0-1.1.x86_64
> bluedevil5-lang-5.27.2-1.1.noarch
> NetworkManager-bluetooth-1.42.4-1.1.x86_64
> bluedevil5-5.27.2-1.1.x86_64
> bluez-qt-udev-5.104.0-1.1.x86_64
> kernel-firmware-bluetooth-20230210-1.1.noarch
> libbluetooth3-5.66-1.4.x86_64
> bluez-cups-5.66-1.4.x86_64
>
>
> in this asset and with the following BT adapter and a Xiaomi Poco X3 Pro it
> "works for me".
>
> Bus 008 Device 004: ID 0b05:184c ASUSTek Computer, Inc. 802.11ac NIC
>
> Maybe your dongle?
> BT transfer fail if you go from one user to another user session in the
> meanwhile. In my experience the transfer does not support multiple users on
> the same machine at the same time using BT (probably because the active user
> steals the focus of the BT device).
>
> Operating System: openSUSE Tumbleweed 20230313
> KDE Plasma Version: 5.27.2
> KDE Frameworks Version: 5.104.0
> Qt Version: 5.15.8
> Kernel Version: 6.2.4-1-default (64-bit)
> Graphics Platform: X11
> Processors: 4 × AMD FX(tm)-4300 Quad-Core Processor
> Memory: 31.3 GiB of RAM
> Graphics Processor: AMD Radeon Pro W5500
> Manufacturer: Gigabyte Technology Co., Ltd.
>
>
> in journalctl -r during transfer I have:
>
> mar 15 12:25:17 localhost systemd[3854]: app-
> org.kde.bluedevilsendfile-3dd5402740174ce7ad1424ad89ebd23e.scope: Consumed
> 3.182s CPU time.
> mar 15 12:25:17 localhost plasmashell[4084]: org.kde.plasma.notifications:
> Failed to determine mime type for QUrl("file:Pan Galactic Gargel Blaster")
> "Il file o la cartella Pan Galactic Gargel Blaster non esiste."
>
> where Pan Galactic Gargle Blaster is my phone.
>
> My take would be to check the dongle, I have a Cambridge
> Bus 008 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth
> Dongle (HCI mode)
> which does not work well with Linux Bluez file transfer. I think it may be
> chip dependent.
>
> what does lsusb say about your BT device?
> Errors in journalctl -r?
I forgot to put here the obvious "PEBKAK" issue in which I did run in the
past:
not enough space in receiving device. This happened because when Xiaomi
updates the OS then the new OS does not take up the path of BT received files
to the preexisting one, so it may be that you are directed with the transfer
to the internal memory (which may be insufficient) while on the SD card may be a
lot of space available.
So maybe for precaution you check if your receiving device has the path
correctly defined.
(I would not wish this to appear "patronizing" far from it. Just to do
brainstorming.
Ambasciatore non porta pena per cosi dire.