gnu solfege crashes when you install python3-pyalsa

Bug #1883382 reported by danilo lujambio
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
solfege (Debian)
Fix Released
Unknown
solfege (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This bug is reported in debian bugs too. But I couldn't find any solution.
When you open the preference dialog, appear this bug
File "/usr/share/solfege/solfege/soundcard/alsa_sequencer.py", line 123, in get_connection_list
    sequencer = alsaseq.Sequencer(name='default',
OverflowError: signed integer is greater than maximum
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-28 (47 days ago)
InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: solfege 3.23.4-7
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
Tags: focal
Uname: Linux 5.4.0-37-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1883382

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntustudio-menu → solfege (Ubuntu)
Changed in solfege (Ubuntu):
status: New → Incomplete
Changed in solfege (Debian):
status: Unknown → New
Revision history for this message
danilo lujambio (lujambiodanilo) wrote : Dependencies.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
danilo lujambio (lujambiodanilo) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
danilo lujambio (lujambiodanilo) wrote : ProcEnviron.txt

apport information

Changed in solfege (Ubuntu):
status: Incomplete → New
Changed in solfege (Debian):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in solfege (Ubuntu):
status: New → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :
Download full text (13.4 KiB)

Also appears in Ubuntu 24.04 with python3-pyalsa 1.2.7-1build5. (Note that the Debian bug was closed because it worked for the OP after upgrade to python3-pyalsa 1.1.6-2+b2.)

solfege (3.23.4-12) crashes with segmentation fault while launching. This is the stack trace:

(gdb) where
#0 __memset_evex_unaligned_erms () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:170
#1 0x0000000000597aca in memset (__len=56, __ch=0, __dest=0x7ffff69be46c)
    at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:59
#2 _PyType_AllocNoTrack (nitems=1, type=0x7ffff69c6de0 <ConstantType>) at ../Objects/typeobject.c:1708
#3 PyType_GenericAlloc (type=0x7ffff69c6de0 <ConstantType>, nitems=1) at ../Objects/typeobject.c:1722
#4 0x0000000000568128 in long_subtype_new
    (obase=<optimized out>, x=<optimized out>, type=0x7ffff69c6de0 <ConstantType>) at ../Objects/longobject.c:5623
#5 long_new_impl (obase=<optimized out>, x=<optimized out>, type=0x7ffff69c6de0 <ConstantType>)
    at ../Objects/longobject.c:5562
#6 long_new (type=0x7ffff69c6de0 <ConstantType>, args=<optimized out>, kwargs=<optimized out>)
    at ../Objects/clinic/longobject.c.h:65
#7 0x00007ffff69b65e8 in Constant_create (name=name@entry=0x7ffff69be47c "SEQ_OPEN_INPUT", value=value@entry=2)
    at pyalsa/alsaseq.c:387
#8 0x00007ffff69ba9a5 in PyInit_alsaseq () at pyalsa/alsaseq.c:3337
#9 0x00000000006a9521 in _PyImport_LoadDynamicModuleWithSpec (spec=spec@entry=0x7ffff43f9130, fp=fp@entry=0x0)
    at ../Python/importdl.c:169
#10 0x00000000006a8c72 in _imp_create_dynamic_impl (module=<optimized out>, file=0x0, spec=0x7ffff43f9130)
    at ../Python/import.c:3775
#11 _imp_create_dynamic (module=<optimized out>, args=<optimized out>, nargs=<optimized out>)
    at ../Python/clinic/import.c.h:506
--Type <RET> for more, q to quit, c to continue without paging--
#12 0x00000000005820b7 in cfunction_vectorcall_FASTCALL
    (func=0x7ffff75972e0, args=0x7ffff439cef8, nargsf=<optimized out>, kwnames=<optimized out>)
    at ../Include/cpython/methodobject.h:50
#13 0x00000000005db593 in _PyEval_EvalFrameDefault
    (tstate=<optimized out>, frame=<optimized out>, throwflag=<optimized out>) at Python/bytecodes.c:3254
#14 0x0000000000549d27 in _PyObject_VectorcallTstate
    (kwnames=0x0, nargsf=2, args=0x7fffffffc140, callable=0x7ffff75a4040, tstate=0xba5048 <_PyRuntime+459656>)
    at ../Include/internal/pycore_call.h:92
#15 object_vacall
    (tstate=tstate@entry=0xba5048 <_PyRuntime+459656>, base=<optimized out>, callable=0x7ffff75a4040, vargs=0x7fffffffc1c8) at ../Objects/call.c:850
#16 0x000000000054b5b3 in PyObject_CallMethodObjArgs (obj=<optimized out>, name=<optimized out>)
    at ../Objects/call.c:911
#17 0x00000000005fde85 in import_find_and_load (abs_name=0x7ffff6701e70, tstate=0xba5048 <_PyRuntime+459656>)
    at ../Python/import.c:2779
#18 PyImport_ImportModuleLevelObject
    (name=name@entry=0x7ffff6701e70, globals=globals@entry=0x0, locals=locals@entry=0x0, fromlist=fromlist@entry=0x0, level=0) at ../Python/import.c:2862
#19 0x00000000005d3874 in builtin___import___impl
    (level=<optimized out>, fromlist=0x0, locals=0x0, globals=0x0, name=0x7ffff6701e70, module=<optimized out>)
--Ty...

Revision history for this message
Tormod Volden (tormodvolden) wrote :

In my case the segfault can be reproduced with simply:

$ python3 -c 'from pyalsa import alsaseq'
Segmentation fault (core dumped)
$

I am not sure this issue is actually the same as OP here or in the Debian bug, so I have reported bug #2073673 instead.

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.