blueman-applet crashed with signal 5

Bug #2023152 reported by Chris Guiver
260
This bug affects 1 person
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I have no details to provide sorry.

This is a QA test install only.. with packages & VERY MINOR change(s) having taken place on it ...

(on subsequent boot; these messages are now appearing & requesting me to file.. I'm in the middle of another QA-test install in another partition on this system & was only booting this system to ensure the newly installed xubuntu.mantic didn't impact here).

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: blueman (not installed)
ProcVersionSignature: Ubuntu 6.2.0-21.21-generic 6.2.6
Uname: Linux 6.2.0-21-generic x86_64
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: LXQt
Date: Fri Jun 2 14:52:56 2023
ExecutablePath: /usr/bin/blueman-applet
InstallationDate: Installed on 2023-06-06 (1 days ago)
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
InterpreterPath: /usr/bin/python3.11
JournalErrors: -- No entries --
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-applet
Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1
PythonDetails: N/A
Signal: 5
SourcePackage: blueman
StacktraceTop:
 () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: blueman-applet crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
separator:

Revision history for this message
Chris Guiver (guiverc) wrote :
information type: Private → Public Security
Revision history for this message
Chris Guiver (guiverc) wrote :

I'm going to mark this incomplete

I suspect the issue is a consequence of a bad install - https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2023000

Regardless, if it's a real issue, it'll be re-filed...

Changed in blueman (Ubuntu):
status: New → Incomplete
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x00007fb1a0e5ef27 in ?? ()
 No symbol table info available.
 #1 0x0000000000000000 in ?? ()
 No symbol table info available.
StacktraceTop:
 ?? ()
 ?? ()

tags: removed: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in blueman (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

blueman version (not required, but 2.3.5-2build1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.