Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#66995 - [solfege] backtrace when opening settings
Attached to Project:
Community Packages
Opened by Fabrizio del Tin (fdteuniversity.pub) - Saturday, 13 June 2020, 19:35 GMT
Last edited by David Runge (dvzrv) - Sunday, 13 September 2020, 14:20 GMT
Opened by Fabrizio del Tin (fdteuniversity.pub) - Saturday, 13 June 2020, 19:35 GMT
Last edited by David Runge (dvzrv) - Sunday, 13 September 2020, 14:20 GMT
|
DetailsDescription:
Solfege has no audio. Clicking on Preference, the following errors are displayed: Traceback (most recent call last): File "/usr/share/solfege/solfege/mainwin.py", line 665, in open_preferences_window self.g_config_window = ConfigWindow() File "/usr/share/solfege/solfege/configwindow.py", line 111, in __init__ self.create_sound_config() File "/usr/share/solfege/solfege/configwindow.py", line 467, in create_sound_config self.create_linux_sound_page() File "/usr/share/solfege/solfege/configwindow.py", line 622, in create_linux_sound_page connections = solfege.soundcard.alsa_sequencer.get_connection_list() File "/usr/share/solfege/solfege/soundcard/alsa_sequencer.py", line 123, in get_connection_list sequencer = alsaseq.Sequencer(name='default', alsaseq.SequencerError: Failed to create sequencer: Invalid argument Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: Click on Preferences |
This task depends upon
Closed by David Runge (dvzrv)
Sunday, 13 September 2020, 14:20 GMT
Reason for closing: Won't fix
Additional comments about closing: solfege or python-pyalsa is buggy and should be fixed upstream.
It is possible to uninstall python-pyalsa and use a MIDI sequencer such as timidity++ instead.
Sunday, 13 September 2020, 14:20 GMT
Reason for closing: Won't fix
Additional comments about closing: solfege or python-pyalsa is buggy and should be fixed upstream.
It is possible to uninstall python-pyalsa and use a MIDI sequencer such as timidity++ instead.
Have you tried to delete the config folder of solfege to clean any broken settings?
It's the first time I run solfege, so it's not an issue of the config folder.
Thank you
solfege 3.23.4-4
I think it would be best to report this upstream (as the message window suggests): https://savannah.gnu.org/bugs/?group=solfege
Note, that upstream unfortunately is close to abandoned...
I believe that python-pyalsa is either buggy or not compatible with solfege anymore, or that solfege is calling internal functions in the wrong way.
I tried digging around in the code base for a while, but I don't see how to fix it.
I have tried reproducing this behavior by plainly calling the same functionality as used in get_connection_list() in /usr/share/solfege/solfege/soundcard/alsa_sequencer.py but was unable to trigger the same behavior.
If you find a way of debugging or fixing this, do tell, but meanwhile I will close this, as I don't see it as downstream's responsibility to fix an upstream bug (especially given the long list of applied patches and that it's possible to use an external MIDI sequencer such as timidity++ instead).