media-hub deadlocks, breaking ringer

Bug #1542947 reported by Thomas
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
Critical
John McAleely
media-hub (Ubuntu)
Fix Released
Critical
Jim Hodapp

Bug Description

Meizu MX 4, the notification sounds for Telegram messages not funkt. , and also no ringtones for incoming calls. That is very unsatisfactory. OTA9

Related branches

Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

The telegram issue is bug #1413818 and should not be new?

As for ringtones they certainly play on other devices so can you please check your settings and provide more information, does changing the the ringtone sound help, check silent mode, volume settings, etc. Thanks.

Changed in canonical-devices-system-image:
status: New → Incomplete
Revision history for this message
Thomas (tomec123) wrote :

We have all 3 Ubuntu Smartphon models here. The two BQS this problem does not occur, only the notification sound at Telegram is also not reliable. When Meizu MX4 itself offers additional from the ring tone. I think this is an issue related the. In the system setting the notification sounds are naturally activated. No mute. Once the notification sounds in turn Telegram, and the ring tone is no longer. In the system settings you can then try to select a different tone, but you do not hear the sounds in the selection. It only helps turn off the phone and boot up again.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

I've seen this at least a couple times on my arale. It's clear the media-hub is deadlocked, i connected to it with strace and there was nothing happening at all.

Of course when it's deadlocked, the ringer does work, or anything that plays audio with media-hub. music-app won't even start.

I confirmed keyboard sounds still play, which do not use media-hub. Also rebooting the device fixes it temporarily.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

The media-player.log doesn't look interesting, but here it is:

http://paste.ubuntu.com/15002759/

affects: messaging-app (Ubuntu) → media-hub (Ubuntu)
Changed in media-hub (Ubuntu):
importance: Undecided → Critical
status: New → Confirmed
assignee: nobody → Jim Hodapp (jhodapp)
summary: - No Ringtones and no alerttones at Telegram
+ media-hub deadlocks, breaking ringer
Revision history for this message
Ken VanDine (ken-vandine) wrote :

in comment #3 i meant the ringer does NOT work

Changed in canonical-devices-system-image:
assignee: nobody → John McAleely (john.mcaleely)
importance: Undecided → Critical
milestone: none → ww08-2016
status: Incomplete → Confirmed
Revision history for this message
Thomas Voß (thomas-voss) wrote :

If anyone manages to reproduce, please attach to media-hub with gdb via:

  sudo gdb -p `pidof media-hub-server`

And take a threaded backtrace by typing 't a a bt'. Pastebinning the output should give us a first hint.
Obviously, the more symbols we have on the backtrace, the better.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

I reproduced this again and collected the bt

http://pastebin.ubuntu.com/15018870/

Jim Hodapp (jhodapp)
Changed in canonical-devices-system-image:
status: Confirmed → In Progress
Revision history for this message
Jim Hodapp (jhodapp) wrote :

So far I'm not able to reproduce this issue on the latest rc-proposed image for arale. If someone who regularly runs into this bug can pay closer attention to what occurs leading up to media-hub hanging and also what happened at exactly the point that you first noticed it hang that should help.

Revision history for this message
Thomas (tomec123) wrote : Re: [Bug 1542947] Re: media-hub deadlocks, breaking ringer

Am Dienstag, 23. Februar 2016, 23:17:26 schrieben Sie:
> So far I'm not able to reproduce this issue on the latest rc-proposed
> image for arale. If someone who regularly runs into this bug can pay
> closer attention to what occurs leading up to media-hub hanging and also
> what happened at exactly the point that you first noticed it hang that
> should help.

Now the notification Sound for Telegram is also not funkt. with the BQ E5 HD.
OTA 9.1.....in german we say... "verschlimmbessert"

Revision history for this message
SB (emehntehtt) wrote :

I am having a similar bug on BQ Aquaris E4.5, ringer is not broken but sound notification for Messaging sometimes stops working, LED blinks on new SMS and it vibrates but no sound is heard, to resolve this I need to reboot the phone. It happens randomly, like something breaks sound notifications for Messaging, ringer works, Telegram works, and Music works but no sound from Messaging.

Revision history for this message
Thomas (tomec123) wrote :

Am Samstag, 27. Februar 2016, 16:23:12 schrieben Sie:
> I am having a similar bug on BQ Aquaris E4.5, ringer is not broken but
> sound notification for Messaging sometimes stops working, LED blinks on
> new SMS and it vibrates but no sound is heard, to resolve this I need to
> reboot the phone. It happens randomly, like something breaks sound
> notifications for Messaging, ringer works, Telegram works, and Music
> works but no sound from Messaging.

Exactly the same with my BQ E5 HD...

Jim Hodapp (jhodapp)
Changed in media-hub (Ubuntu):
status: Confirmed → In Progress
Jim Hodapp (jhodapp)
Changed in media-hub (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package media-hub - 4.1.0+16.04.20160308.2-0ubuntu1

---------------
media-hub (4.1.0+16.04.20160308.2-0ubuntu1) xenial; urgency=medium

  * Fix deadlock issue when adding/removing Player instances from the
    HashedKeyedPlayerStore (LP: #1542947)

 -- Jim Hodapp <email address hidden> Tue, 08 Mar 2016 19:36:07 +0000

Changed in media-hub (Ubuntu):
status: Fix Committed → Fix Released
Jim Hodapp (jhodapp)
Changed in canonical-devices-system-image:
status: In Progress → Fix Committed
Revision history for this message
Roascio Paolo (roa) wrote :
Revision history for this message
Jim Hodapp (jhodapp) wrote :

@roa: No, that's a separate issue. This bug was purely a deadlock in media-hub that was occurring when adding a new Player session to the storage container class that tracks Player instances. The bug you linked to is simply about having qtubuntu-media detect and recreate when media-hub-server goes away and thus the Player session that it was linked to over dbus.

Revision history for this message
Ken VanDine (ken-vandine) wrote :

I just reproduced this again :(

Here's the stacktrace:

(gdb) t a a bt

Thread 8 (Thread 0xb2d20360 (LWP 2574)):
#0 0xb40356b4 in ?? ()
#1 0xb4049c8c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 7 (Thread 0xb23ff360 (LWP 2575)):
#0 0xb40356b4 in ?? ()
#1 0xb4049c8c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 6 (Thread 0xb19ff360 (LWP 2576)):
#0 0xb623e132 in epoll_wait () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x0018bd94 in boost::asio::detail::epoll_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) ()
#2 0x0018d052 in boost::asio::detail::task_io_service::run(boost::system::error_code&) ()
#3 0x0018b23a in _start ()

Thread 5 (Thread 0xad1fe360 (LWP 2577)):
#0 0xb62374e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 4 (Thread 0xac9fe360 (LWP 2578)):
#0 0xb62374e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 3 (Thread 0xabace360 (LWP 2579)):
#0 0xb62a5d44 in __libc_do_syscall () from /lib/arm-linux-gnueabihf/libpthread.so.0
#1 0xb62a395c in __lll_lock_wait () from /lib/arm-linux-gnueabihf/libpthread.so.0
#2 0xb629f202 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
#3 0xb6dcd76a in ?? () from /usr/lib/arm-linux-gnueabihf/libgstreamer-1.0.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xa68fe360 (LWP 4847)):
#0 0xb623b620 in syscall () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0xb6cd6882 in ?? () from /lib/arm-linux-gnueabihf/libglib-2.0.so.0
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0xb40c3000 (LWP 2546)):
#0 0xb62374e0 in poll () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x00000000 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Jim Hodapp (jhodapp)
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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