[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit|

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 Harald Sitter changed: What|Removed |Added CC||dav84m...@protonmail.com --- Comment #8 from

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 Harald Sitter changed: What|Removed |Added CC||feat...@engineer.com --- Comment #7 from

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b |

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 --- Comment #6 from tagwer...@innerjoin.org --- (In reply to Arjen Hiemstra from comment https://bugs.kde.org/show_bug.cgi?id=482082#c7) > Just to collect some extra data, can we the output of `systemd-analyze --user > blame` for those that > can

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 --- Comment #5 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #4) > See Bug 482082 which has the summary: > > By default, the Breeze Splash screen is enabled. I noticed the system took a > long time to log in after entering my

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 --- Comment #4 from tagwer...@innerjoin.org --- See Bug 482082 which has the summary: By default, the Breeze Splash screen is enabled. I noticed the system took a long time to log in after entering my password after upgrading to Neon / Plasma 6. I went

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 tagwer...@innerjoin.org changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 --- Comment #3 from tagwer...@innerjoin.org --- Also Bug 481805 -- You are receiving this mail because: You are watching all bug changes.

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 tagwer...@innerjoin.org changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 --- Comment #2 from tagwer...@innerjoin.org --- Bug 481959 describes something similar -- You are receiving this mail because: You are watching all bug changes.

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 --- Comment #1 from tagwer...@innerjoin.org --- This doesn't seem to affect all Neon Testing systems, I have one older version where it works. What seems different is that the failing systems have: $ systemctl --user status obex ○ obex.service

[frameworks-bluez-qt] [Bug 481870] Neon Testing: Bluetooth related 25 second delay after logging in.

https://bugs.kde.org/show_bug.cgi?id=481870 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail