Modify
Warning Please read the Ticket HowTo before creating or commenting on a ticket. Failure to do so may cause your ticket to be rejected or result in a slower response.

Opened 2 years ago

Closed 15 months ago

#9396 closed Bug Report - Crash (Unverified)

[CRASH] alsa:bluetooth crashes mythmusic

Reported by: fbeatrous@… Owned by: paulh
Priority: critical Milestone: 0.25
Component: Plugin - MythMusic Version: 0.24-fixes
Severity: medium Keywords: alsa bluetooth
Cc: Ticket locked: no

Description

I have ALSA:bluetooth configured as a bluetooth headset. Attempting to play mp3 music with "Audio output device" set to ALSA:bluetooth causes mythfrontend to exit immediately. The last few lines in the log file are

2010-12-20 12:54:51.403 XMLParse: LoadTheme? using '/usr/local/share/mythtv/themes/default-wide/music-ui.xml'
2010-12-20 12:54:52.010 AO: Opening audio device 'bluetooth' ch 2(2) sr 44100 sf signed 16 bit reenc 0
2010-12-20 12:54:52.010 ALSA, Error: snd_pcm_info_get_card: Operation not permitted
2010-12-20 12:54:52.010 ALSA, Error: Unable to sufficiently increase ALSA hardware buffer size - underruns are likely

HOWEVER: Identical lines appear in the log file when I start playback of a recorded tv program, and, in this case, the recording plays with stereo sound in the bluetooth headset.

Also, I can play music with mplayer using bluetooth audio.

As far as I can tell, the failure is unique to mythmusic.

I should also mention that bluetooth audio worked for me with mythmusic in 0.23.

Attachments (2)

bt.log (954 bytes) - added by fbeatrous@… 2 years ago.
Backtrace after seg fault
gdb.txt (48.2 KB) - added by fbeatrous@… 2 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 2 years ago by stuartm

  • Component changed from Plugin - MythMusic to MythTV - Audio Output
  • Owner changed from paulh to jyavenard
  • Status changed from new to assigned

comment:2 Changed 2 years ago by jyavenard

  • Status changed from assigned to infoneeded

The error showing in the log is normal if your ALSA hardware buffer is set too low (you would have a line telling you what to do to increase it) and has no bearing on audio working or not (just that you will lilely get interruption with buffer under runs)

So please provide a backtrace, because your log doesn't contain any indications on what could be wrong, nor help identifying if the issue is in the myth music plugin, or the core audio framework

Changed 2 years ago by fbeatrous@…

Backtrace after seg fault

comment:3 Changed 2 years ago by stuartm

  • Milestone changed from unknown to 0.25
  • Status changed from infoneeded to assigned

comment:4 Changed 2 years ago by beirdo

  • Summary changed from alsa:bluetooth crashes mythmusic to [CRASH] alsa:bluetooth crashes mythmusic

comment:5 Changed 2 years ago by jyavenard

  • Status changed from assigned to infoneeded

Please try with the latest version of mythtv. MythMusic could incorrectly call the audio framework. Even if audio initialisation failed, mythmusic would happily use it.

Added some work-around code so even if mythmusic is doing the wrong thing, it won't crash.

Changed 2 years ago by fbeatrous@…

comment:6 Changed 2 years ago by fbeatrous@…

Just tried with the latest 0.24 fixes (v0.24-196-g4af46b1), with the same result as before: Bluetooth audio works with playback of recorded tv, but mythmusic crashes when I attempt to use bluetooth.

A backtrace is attached.

comment:7 Changed 2 years ago by jyavenard

Latest version of mythtv isn't 0.24, but in trunk/master

comment:8 Changed 2 years ago by jyavenard

  • Owner changed from jyavenard to paulh

The crash is in:
avfDecoder::initialize (this=0x98f9f08) at avfdecoder.cpp:215

comment:9 Changed 2 years ago by robertm

  • Status changed from infoneeded to assigned

comment:10 Changed 16 months ago by stuartm

  • Component changed from MythTV - Audio Output to Plugin - MythMusic
  • Priority changed from minor to critical
  • Type changed from Bug Report to Bug Report - Crash

comment:11 Changed 15 months ago by paulh

  • Resolution set to Unverified
  • Status changed from assigned to closed

A lot has changed since this ticket was opened and to my knowledge this is the only report of problems of this kind. Please try 0.25 and reopen if it's still a problem.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'new'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.