Bug 502381

Summary: I cannot send file(s) from Smartphone to Linux.
Product: [Plasma] plasmashell Reporter: AlexB <kde-identity-of-alex>
Component: Bluetooth in generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: kdedev
Priority: NOR    
Version First Reported In: 6.3.2   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
URL: https://gitlab.com/tuxedocomputers/development/tuxedo_os/os/-/issues/529
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description AlexB 2025-04-03 22:14:16 UTC
SUMMARY
I cannot send file(s) from Smartphone to Linux.
Please note: I have found the reason for it and a workaround, see WORKAROUND section at the bottom.

STEPS TO REPRODUCE
1. Activate bluetooth on smartphone and Linux.
2. Connect smartphone to Linux.
3. Choose a file on smartphone and send to Linux.
4. Smartphone says, that sending file to Linux failed.

OBSERVED RESULT
Smartphone says, that sending file to Linux failed. Linux does not say anything.

EXPECTED RESULT
File is transferred to Linux and Linux gives a notification about successful file reception.

SOFTWARE/OS VERSIONS

Operating System:             TUXEDO OS 
KDE Plasma Version:          6.3.2
KDE Frameworks Version: 6.11.0
Qt Version:                           6.8.2
Kernel Version:                    6.11.0-109019-tuxedo (64-bit)

bluetooth/tuxedo,tuxedo,now 5.79-1tux1 all  [Installiert,automatisch]
libbluetooth3/tuxedo,now 5.79-1tux1 amd64  [Installiert,automatisch]
libspa-0.2-bluetooth/tuxedo,now 1.4.1-1tux1 amd64  [installiert]
pulseaudio-module-bluetooth/noble-updates,now 1:16.1+dfsg1-2ubuntu10.1 amd64  [installiert]

bluez-cups/tuxedo,now 5.79-1tux1 amd64  [Installiert,automatisch]
bluez-obexd/tuxedo,now 5.79-1tux1 amd64  [Installiert,automatisch]
bluez/tuxedo,now 5.79-1tux1 amd64  [Installiert,automatisch]
kf6-bluez-qt/noble,now 6.11.0-0zneon+24.04+noble+release+build8 amd64  [Installiert,automatisch]
libkf5bluezqt-data/noble,noble,noble,now 5.116.0-1zneon+24.04+noble+release+build3 all  [Installiert,automatisch]
libkf5bluezqt6/noble,now 5.116.0-1zneon+24.04+noble+release+build3 amd64  [Installiert,automatisch]
qml-module-org-kde-bluezqt/noble,now 5.116.0-1zneon+24.04+noble+release+build3 amd64  [Installiert,automatisch]

evolution-data-server-common/noble-updates,noble-updates,now 3.52.3-0ubuntu1 all  [Installiert,automatisch]

ADDITIONAL INFORMATION

WORKAROUND
I have seen following messages in log:

    $ journalctl -ft obexd
    obexd[4206]: OBEX daemon 5.79
    obexd[4206]: Unable to acquire registery: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources5: Unit evolution-source-registry.service not found.

Since on my Linux machine KDE is used (no GNOME) and I have no Evolution installation, I have edited

    /usr/share/dbus-1/services/org.gnome.evolution.dataserver.Sources5.service

as follows (commented Exec=... line):

    [D-BUS Service]
    Name=org.gnome.evolution.dataserver.Sources5
    #Exec=/usr/libexec/evolution-source-registry
    SystemdService=evolution-source-registry.service

Then I have restarted obexd in terminal:

    $ systemctl --user restart obex.service

Messages in log after restart changed to:

    obexd[4917]: OBEX daemon 5.79
    obexd[4917]: Unable to get reference to default address book
    obexd[4917]: Unable to get reference to default address book

After this change it is possible now to send files from smartphone to Linux and Bluetooth applet shows reception progress and "File received" notification.
Comment 1 TraceyC 2025-04-03 23:47:43 UTC
Thanks for the bug report. I'm not able to reproduce this bug on git-master on Solus. I also don't have Evolution installed.

Based on the detailed root cause and workaround, this looks like a configuration or dependency problem with Tuxedo OS.
You'll want to report this to them via their GitLab issues tracker:
https://gitlab.com/tuxedocomputers/development/tuxedo_os/os/-/issues

Let us know if they're able to help you or say there's something KDE needs to do
Comment 2 AlexB 2025-04-04 18:21:37 UTC
(In reply to TraceyC from comment #1)

> You'll want to report this to them via their GitLab issues tracker:
> https://gitlab.com/tuxedocomputers/development/tuxedo_os/os/-/issues

Thank you for the hint, I have created bug ticket there.
 
> Let us know if they're able to help you or say there's something KDE needs
> to do

I will do so.
Comment 3 AlexB 2025-04-04 18:23:22 UTC
(In reply to AlexB from comment #2)
> (In reply to TraceyC from comment #1)
> 
> > You'll want to report this to them via their GitLab issues tracker:
> > https://gitlab.com/tuxedocomputers/development/tuxedo_os/os/-/issues
> 
> Thank you for the hint, I have created bug ticket there.

https://gitlab.com/tuxedocomputers/development/tuxedo_os/os/-/issues/529
Comment 4 AlexB 2025-04-13 20:59:44 UTC
(In reply to TraceyC from comment #1)
> Based on the detailed root cause and workaround, this looks like a
> configuration or dependency problem with Tuxedo OS.
> ...
> Let us know if they're able to help you or say there's something KDE needs
> to do

I've done further investigations in the issue and found the root cause. This was a missing dependency:

    bluez-obexd ---> libedataserver-1.2-27t64 ---> evolution-data-server-common -- x --> evolution-data-server

For more information and detailed description please visit:
https://gitlab.com/tuxedocomputers/development/tuxedo_os/os/-/issues/529#note_2448753118

I think this is not the issue in KDE's bluetooth component (and also not in bluez-obexd), but an issue in missing dependency between evolution-data-server-common and evolution-data-server. This is why I would propose to close this issue here.
Comment 5 Bug Janitor Service 2025-04-28 03:47:22 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 6 AlexB 2025-04-28 16:12:11 UTC
As I already described in Comment 4 (https://bugs.kde.org/show_bug.cgi?id=502381#c4) this is not a bug in plasmashell | bluetooth component => closing this ticket.