abrt version: 1.1.13 architecture: i686 cmdline: /usr/bin/python /usr/bin/ffado-mixer component: libffado executable: /usr/bin/ffado-mixer kernel: 2.6.33.6-147.2.4.rt28.1.fc13.ccrma.i686.rt package: ffado-2.0.1-3.20100706.svn1864.fc13 reason: motu.py:572:initValues:AttributeError: 'Motu' object has no attribute 'mode' release: Fedora release 13 (Goddard) time: 1284848752 uid: 500 backtrace ----- motu.py:572:initValues:AttributeError: 'Motu' object has no attribute 'mode' Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/ffado/panelmanager.py", line 350, in updatePanels mixerwidget.initValues() File "/usr/lib/python2.6/site-packages/ffado/mixer/motu.py", line 572, in initValues if (self.model==MOTU_MODEL_828mk3 or self.mode==MOTU_MODEL_ULTRALITEmk3 or self.mode==MOTU_MODEL_ULTRALITEmk3_HYB): AttributeError: 'Motu' object has no attribute 'mode' Local variables in innermost frame: self: <ffado.mixer.motu.Motu object at 0x895606c> How to reproduce ----- 1. Opened ffado-mixer application 2. reached the point where it deduced that the MOTU device was set for 96000hz 3. application froze up
Created attachment 448241 [details] File: backtrace
Thanks. Is this reported upstream to the developers?
Hey there, Not at this point. Should I report it to them as well? I'm new to all of this Linux stuff (what with people actually contacting you like this and asking questions). Thanks!
Hello Michael, It's all good. For 99% of the crash reports such as this one, the person (the package maintainer) you are talking in this bugzilla is not the actual program developer. In fact, the person might not even be a programmer. By posting your report here, you are expecting the package maintainer to forward this to the developers, thus adding another layer between you and the people who can actually solve your issues. Things might work this way depending on the time the package maintainer can dedicate. My preference is to report bugs to the developers, as they might need more information from you and the additional layer might slow down the process. However, filing a bug, even if it's filed here, is better than filing no bug. I can forward this report upstream for you. Thanks for your time.
forwarded upstream: http://subversion.ffado.org/ticket/305
Hello, I am still negotiating with the developers how to tackle the updating strategy of ffado. Meanwhile you can use this command (single line) as root to prevent the crash: # sed -i 's|self.mode=|self.model=|g' /usr/lib/python2.6/site-packages/ffado/mixer/motu.py
libffado-2.1.0-0.1.20101015.svn1913.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/libffado-2.1.0-0.1.20101015.svn1913.fc14
libffado-2.1.0-0.1.20101015.svn1913.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/libffado-2.1.0-0.1.20101015.svn1913.fc13
libffado-2.1.0-0.1.20101015.svn1913.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update libffado'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/libffado-2.1.0-0.1.20101015.svn1913.fc14
libffado-2.1.0-0.1.20101015.svn1913.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
libffado-2.1.0-0.1.20101015.svn1913.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.