blueman-tray error /home/username/.cache/blueman-tray-1000

[Artur Kwiatkowski]

[Impact]
This is one of the, if not the, most common crash for users of Ubuntu 20.04 LTS.

[Test Case]
Check the errors bucket at https://errors.ubuntu.com/problem/5e6627ae83ef4c84aff962ff2b0714b9061134c8 and confirm that the new version of the package is not appearing in the bucket

[Regression Potential]
The fix just logs an error if removing the file failed so unless the python code is missformatted there isn't much that go wrong.

Original Description
--------------------
There is blueman-tray error on every login and one particular thing is obvious:
"file not found /home/username/.cache/blueman-tray-1000"

I do not have user named "username" neither have I directory "username" in my home dir.

there is blueman-tray-1000 file in /home/kwiatek/.cache

Greetings

ProblemType: BugDistroRelease: Ubuntu 20.04
Package: blueman 2.1.2-1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri May 8 08:53:25 2020
InstallationDate: Installed on 2020-02-25 (72 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)SourcePackage: blueman
UpgradeStatus: Upgraded to focal on 2020-04-25 (12 days ago)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

[Sebastien Bacher (seb128)]

The issue was fixed in https://github.com/blueman-project/blueman/commit/b47d23fc

which is in https://launchpad.net/ubuntu/+source/blueman/2.1.3-1

[Brian Murray (brian-murray)]

This crash is still being seen regularly in Ubuntu 20.04 LTS and the fix should be SRU'ed to that release of Ubuntu.

https://errors.ubuntu.com/problem/771795995cb1e87fec9bdedcd1ce80b140b12b28

[Brian Murray (brian-murray)]

This is another and better errors bucket for the Ubuntu 20.04 LTS crash as it shows the versions of the package in -updates.

https://errors.ubuntu.com/problem/5e6627ae83ef4c84aff962ff2b0714b9061134c8

[Robie Basak (racb)]

Hello Artur, or anyone else affected,

Accepted blueman into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/blueman/2.1.2-1ubuntu0.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Brian Murray (brian-murray)]

Before I installed blueman version 2.1.2-1ubuntu0.3 my system would suffer from a blueman-tray crash on every boot, but since I've upgraded to the version of blueman from focal-proposed I'm no longer plagued by crash reports. I think everybody should use blueman version 2.1.2-1ubuntu0.3! Don't just take my word for though, here are some verification details.

bdmurray@atom:~$ ls -lh /var/crash
total 68K
-rw-r----- 1 bdmurray whoopsie 66K Oct 24 06:44 _usr_bin_blueman-tray.1001.crash
bdmurray@atom:~$ ps aux | grep blueman-tray
bdmurray 2710 0.0 0.2 367320 52072 ? Sl Oct24 0:00 /usr/bin/python3 /usr/bin/blueman-tray
bdmurray 35300 0.0 0.0 9032 724 pts/1 S+ 13:24 0:00 grep --color=auto blueman-tray
bdmurray@atom:~$ uptime
 13:24:13 up 1 day, 18:47, 2 users, load average: 0.02, 0.02, 0.00
bdmurray@atom:~$ apt-cache policy blueman
blueman:
  Installed: 2.1.2-1ubuntu0.3
  Candidate: 2.1.2-1ubuntu0.3

[Brian Murray (brian-murray)]

Additionally, the errors bucket referenced from the description does not contain the new version of the blueman listed in it and all the errors with FileNotFound tracebacks in them at https://errors.ubuntu.com/?package=blueman&period=day do not contain the new version of blueman either.

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for blueman has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package blueman - 2.1.2-1ubuntu0.3

---------------
blueman (2.1.2-1ubuntu0.3) focal; urgency=medium

  * d/p/handle-os-remove-failure.patch: Handle the case when removing the file
    didn't work out. (LP: #1877524)

 -- Brian Murray <email address hidden> Mon, 13 Sep 2021 19:49:31 -0700