From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: HCtl event callback gives "Fatal Python error: drop_gil: drop_gil: GIL is not locked"
Date: Tue, 14 May 2024 21:48:48 +0200 (CEST) [thread overview]
Message-ID: <20240514194848.85F20F80224@alsa1.perex.cz> (raw)
In-Reply-To: <1715716126585637331-webhooks-bot@alsa-project.org>
alsa-project/alsa-python issue #11 was edited from HEnquist:
I'm running the [hctltest2.py](https://github.com/alsa-project/alsa-python/blob/master/test/hctltest2.py) test.
Then change one of the controls, I tried the "Z Test Volume" that gets numid 4:
`amixer -D hw:0 cset numid=4 5`
This generates and event, which runs the callback function. That results in the test script crashing, with:
```
Fatal Python error: drop_gil: drop_gil: GIL is not locked
Python runtime state: initialized
Thread 0x00007cae1adbc740 (most recent call first):
File "/home/henrik/repos/camilladsp-controller/hctltest2.py", line 25 in event_callback
Current thread 0x00007cae1adbc740 (most recent call first):
File "/home/henrik/repos/camilladsp-controller/hctltest2.py", line 63 in <module>
Extension modules: pyalsa.alsahcontrol (total: 1)
Aborted (core dumped)
```
Tested on manjaro with python 3.11, and latest alsa-python.
Also tested on Python 3.8.19, using the latest alsa-python code directly from this repo, with the same result.
Issue URL : https://github.com/alsa-project/alsa-python/issues/11
Repository URL: https://github.com/alsa-project/alsa-python
next parent reply other threads:[~2024-05-14 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1715716126585637331-webhooks-bot@alsa-project.org>
2024-05-14 19:48 ` GitHub issues - edited [this message]
[not found] <1715715801664961576-webhooks-bot@alsa-project.org>
2024-05-14 19:43 ` HCtl event callback gives "Fatal Python error: drop_gil: drop_gil: GIL is not locked" GitHub issues - opened
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240514194848.85F20F80224@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).