Crash when connecting some bluetooth devices

Support GNOME
1

Hi,

Looks like some Bluetooth devices cause a crash when connecting / disconnecting (for example Sony WF-C700N).
Bugs have been raised and addressed by gnome (see here).

Unfortunately while waiting for this fix to get released with Gnome 49 and packaged in Manajro - I can’t use my bluetooth device and trying it makes gnome go into “deathloop”.

What I am supposed to do in these cases?

How do I use a Manjaro compatible version of gnome which would let me use my hardware and then able to automatically upgrade once updated Gnome 49 comes out?

Apparently the fix has been merged in the upcoming RC - do we know usually how long it’ll take?

In general, what is the best avenue for this to get addressed?

Apologies for all the questions, but been an Ubuntu LTS user since 2007 and that distro would have been on older packages but those would be functional and retro patched when necessary.

I believe Manjaro should be a seen as a more stable Arch - how is this achieved?

Many thanks!

2

As with most cases, the adage “it will be ready when it’s ready” likely applies – and then each distribution providing GNOME must also wait for the updated (bug-fixed) version to reach them.

Generally longer again for any Arch Linux based distribution, as it must pass Arch quality checking to Arch Stable, and then through Manjaro Unstable, Testing and finally Stable branches.

It’s ufortunately quite impossible to answer a question such as “how long will it take” with any semblence of accuracy – and that question is asked often – at best, we might need a :crystal_ball: :eyes:

If a documented “fix” is already in the pipeline, then the most obvious resolve is to wait; as inconvenient as that may be for some, there is little alternative. :man_shrugging:

2 Likes
3

Thanks - as I imagined. If I download the offending library (as displayed in the stack trace of the reported bugs), patch it to at least avoid the NULL de-reference and overwrite the one existing in my system, once the upgrade happens will it be seamlessly overwritten?

4

In theory, yes.

5

I’ll give it a go then!

1 Like
6

Right, I made an emergency patch against gnome 49, rebuilt within a Manjaro VirtualBox VM (I knew I would install all sort of packages to build it experimenting) and it seems it doesn’t crash my desktop anymore and those work!

Result!?

I know this may be a bit dodgy but I couldn’t stand not being able to use my Bluetooth buds!

For people interested, this is the patch to libgcv (a git submodule of gnome-shell)

diff --git a/gvc-mixer-control.c b/gvc-mixer-control.c
index 5704270..6e0d323 100644
--- a/gvc-mixer-control.c
+++ b/gvc-mixer-control.c
@@ -272,6 +272,7 @@ gvc_mixer_control_lookup_device_from_stream (GvcMixerControl *control,
                 } else if (!is_network_stream) {
                         const GvcMixerStreamPort *port;
                         port = gvc_mixer_stream_get_port (stream);
+                       if(!port) continue;
 
                         if (stream_id == gvc_mixer_stream_get_id (stream) &&
                             g_strcmp0 (gvc_mixer_ui_device_get_port (device),
diff --git a/gvc-mixer-stream.c b/gvc-mixer-stream.c
index f9bcc40..67cbc05 100644
--- a/gvc-mixer-stream.c
+++ b/gvc-mixer-stream.c
@@ -532,7 +532,7 @@ gvc_mixer_stream_get_port (GvcMixerStream *stream)
                 }
         }
 
-        g_assert_not_reached ();
+        //g_assert_not_reached ();
 
         return NULL;
 }
2 Likes
7

The fix was applied a week ago with gnome-shell 1:49.4-3 available in the Manjaro testing & unstable branches. It was also applied on Arch the same day.

3 Likes
8

Excellent - shall we get it in Manjaro stable next month?

9

It should be in the next Stable update. There is no set schedule for Stable updates though. Usually they happen about once per month, however if there is a major update on the way (such as a new release of Plasma or Gnome), then it can take longer as the Manjaro Team will wait until any issues identified by Unstable & Testing branch users are resolved.

Alternatively, you could switch to Testing branch, which is quite stable & updates on a (roughly) weekly basis. The process is quite straightforward:

To switch to Testing branch:

sudo pacman-mirrors --api --set-branch testing

or, to switch to Unstable branch:

sudo pacman-mirrors --api --set-branch unstable

After you changed the branch, rebuild the mirrorlist and update your packages:

sudo pacman-mirrors --continent && sudo pacman -Syyu
1 Like
10

Thanks very much - I reckon my patch makes it work somehow. I’ll wait for packages to be updated in stable then.

2 Likes
11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.