bluez snap: SEGV on termination

Bug #1907498 reported by Dan Dedrick on 2020-12-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snappy-hwe-snaps
Medium
Alfonso Sanchez-Beato

Bug Description

When the snap.bluez.obex.service systemd service is stopped it gets a SIGSEGV. The issues is that bluez has been patched to set option_root to an environment variable. The problem is that on cleanup it tries to free option_root and gets the SIGSEGV because it has been set to an environment variable instead of malloced memory.

The patch that added this issue is specific to the snap version of bluez. It is authored by Simon Fels and has the commit message "Add snappy runtime directory support". In the bluez/5.48 branch it is 52e16885a4d0d67cd6b1ae3d41414c82bd0122cf.

I've attached a patch that can either be applied in addition to this or be squashed into the existing change.

Revision history for this message
Dan Dedrick (ddedrick) wrote :
Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :
Changed in snappy-hwe-snaps:
status: New → Confirmed
importance: Undecided → Medium
status: Confirmed → In Progress
assignee: nobody → Alfonso Sanchez-Beato (alfonsosanchezbeato)
Changed in snappy-hwe-snaps:
status: In Progress → Fix Committed
Revision history for this message
Dan Dedrick (ddedrick) wrote :

Thanks for fixing this up!

Revision history for this message
Alfonso Sanchez-Beato (alfonsosanchezbeato) wrote :

Fixed in 5.48-2 (latest/stable) and 5.53-3 (20/stable).

Changed in snappy-hwe-snaps:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers