Ticket #237 (closed bug: wontfix)

Opened 11 years ago

Last modified 8 years ago

ffado-dbus-server crash after resetting sample rate on saffire pro26

Reported by: nettings Assigned to:
Priority: minor Milestone: FFADO 2.1
Component: Version: FFADO SVN (trunk)
Keywords: Cc:
The device the bug applies to:

Description

hi! with current trunk (r1673), ffado-dbus-server crashes after changing the sample rate in ffado-mixer. the sample rate is changed successfully, then the device needs to reboot or something, and then the mixer freezes for a loong time. the console says:

nettings@kleineronkel:~> ffado-mixer 18:01:21 main INFO Starting up Traceback (most recent call last):

File "/usr/local/lib64/python2.5/site-packages/ffado/mixer/globalmixer.py", line 69, in on_samplerate_activated

self.samplerateselect.select( sr )

File "/usr/local/lib64/python2.5/site-packages/ffado/dbus_util.py", line 326, in select

return self.iface.select(idx)

File "/usr/lib64/python2.5/site-packages/dbus/proxies.py", line 140, in call

**keywords)

File "/usr/lib64/python2.5/site-packages/dbus/connection.py", line 607, in call_blocking

message, timeout)

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply?: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 18:02:18 panelmanager ERROR error in polled update Traceback (most recent call last):

File "/usr/local/lib64/python2.5/site-packages/ffado/panelmanager.py", line 157, in pollPanels

child.polledUpdate()

File "/usr/local/lib64/python2.5/site-packages/ffado/mixer/globalmixer.py", line 118, in polledUpdate

self.samplerate.setEnabled(self.samplerateselect.canChangeValue())

File "/usr/local/lib64/python2.5/site-packages/ffado/dbus_util.py", line 332, in canChangeValue

return self.iface_element.canChangeValue()

File "/usr/lib64/python2.5/site-packages/dbus/proxies.py", line 140, in call

**keywords)

File "/usr/lib64/python2.5/site-packages/dbus/connection.py", line 607, in call_blocking

message, timeout)

dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply?: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

after a while, the mixer window becomes responsive again, complaining "failed to communicate with dbus server, please restart it and ffadomixer."

spot on, that's the only thing that helps.

it's not a killer bug, but distinctly uncool.

Change History

03/28/12 04:01:07 changed by jwoithe

From the description you gave it seems like the device goes offline for a period of time after the sample rate is changed. That's really odd - I don't know of any other device which does that.

Anyway, the obvious question is whether the problem occurs with the current trunk. Are you able to test it?

When ffado-dbus-server crashes, does it leave a core dump or provide any useful information about why it's died? It may be worthwhile explicitly running ffado-dbus-server in a terminal prior to starting ffado-mixer; that way anything printed by ffado-dbus-server will be clearly evident.

05/11/12 05:31:33 changed by jwoithe

  • status changed from new to closed.
  • resolution set to wontfix.

Without further information relating to tests with a recent kernel, libraw1394 and FFADO it's not possible to progress this further. I'll close as "wontfix" for the moment; if further details become available this ticket can be reopened.