From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: onboard-1.4.1_12 fails after upgrade python 3.12
Date: Thu, 19 Oct 2023 16:39:29 +0200 [thread overview]
Message-ID: <20231019143929.tMY2s5Bp61_3Mokd8KvJ30CaMMnowdDAzKsNVOgW9uY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46767@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 4762 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/46767#issuecomment-1771129608
Comment:
Confirmed
```
Thread 1 "python3" received signal SIGSEGV, Segmentation fault.
0x00007ffff7a276e6 in _PyInterpreterState_GET () at ./Include/internal/pycore_pystate.h:118
118 ./Include/internal/pycore_pystate.h: No such file or directory.
(ins)(gdb) bt
#0 0x00007ffff7a276e6 in _PyInterpreterState_GET () at ./Include/internal/pycore_pystate.h:118
#1 get_state () at Objects/obmalloc.c:866
#2 _PyObject_Malloc (ctx=<optimized out>, nbytes=112) at Objects/obmalloc.c:1563
#3 0x00007ffff7a26162 in _PyObject_New (tp=tp@entry=0x7ffff4d7ed80 <osk_device_event_type>) at Objects/object.c:319
#4 0x00007ffff4d72086 in new_device_event () at Onboard/osk/osk_devices.c:100
#5 osk_devices_call_event_handler_key (dev=0x7ffff26a3b40, type=2, display=0x5555557d64f0, device_id=3, source_id=14, keycode=133, keyval=65515)
at Onboard/osk/osk_devices.c:486
#6 0x00007ffff4d722c7 in osk_devices_event_filter (gdk_event=<optimized out>, dev=0x7ffff26a3b40, gdk_xevent=<optimized out>) at Onboard/osk/osk_devices.c:899
#7 osk_devices_event_filter (gdk_xevent=<optimized out>, gdk_event=<optimized out>, dev=0x7ffff26a3b40) at Onboard/osk/osk_devices.c:800
#8 0x00007ffff5c9483f in ?? () from /usr/lib/libgdk-3.so.0
#9 0x00007ffff5c97c21 in ?? () from /usr/lib/libgdk-3.so.0
#10 0x00007ffff5c3fa09 in gdk_display_get_event () from /usr/lib/libgdk-3.so.0
#11 0x00007ffff5c97932 in ?? () from /usr/lib/libgdk-3.so.0
#12 0x00007ffff6d74fa7 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007ffff6d77e77 in ?? () from /usr/lib/libglib-2.0.so.0
#14 0x00007ffff6d7866f in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#15 0x00007ffff51e688d in gtk_main () from /usr/lib/libgtk-3.so.0
#16 0x00007ffff74f6e6d in ?? () from /usr/lib/libffi.so.7
#17 0x00007ffff74f62aa in ?? () from /usr/lib/libffi.so.7
#18 0x00007ffff6ea5d9e in ?? () from /usr/lib/python3.12/site-packages/gi/_gi.so
#19 0x00007ffff6ea450c in ?? () from /usr/lib/python3.12/site-packages/gi/_gi.so
#20 0x00007ffff7a05d71 in _PyObject_Call (tstate=0x7ffff7e69170 <_PyRuntime+459600>, callable=0x7ffff59bffb0, args=0x7ffff7e0b808 <_PyRuntime+76264>, kwargs=<optimized out>)
at Objects/call.c:367
#21 0x00007ffff798345c in _PyEval_EvalFrameDefault (tstate=<optimized out>, frame=0x7ffff7fc0118, throwflag=<optimized out>) at Python/bytecodes.c:3259
#22 0x00007ffff7a04da0 in _PyFunction_Vectorcall (kwnames=0x0, nargsf=<optimized out>, stack=0x7fffffffd1a0, func=0x7ffff267e480) at Objects/call.c:419
#23 _PyObject_FastCallDictTstate (tstate=0x7ffff7e69170 <_PyRuntime+459600>, callable=0x7ffff267e480, args=0x7fffffffd1a0, nargsf=<optimized out>, kwargs=<optimized out>)
at Objects/call.c:133
#24 0x00007ffff7a057a8 in _PyObject_Call_Prepend (tstate=tstate@entry=0x7ffff7e69170 <_PyRuntime+459600>, callable=callable@entry=0x7ffff267e480,
obj=obj@entry=0x7ffff7107aa0, args=args@entry=0x7ffff7e0b808 <_PyRuntime+76264>, kwargs=kwargs@entry=0x0) at Objects/call.c:508
#25 0x00007ffff7a33e2b in slot_tp_init (self=0x7ffff7107aa0, args=0x7ffff7e0b808 <_PyRuntime+76264>, kwds=0x0) at Objects/typeobject.c:9007
#26 0x00007ffff7a32b9b in type_call (type=<optimized out>, type@entry=0x555555aa90d0, args=args@entry=0x7ffff7e0b808 <_PyRuntime+76264>, kwds=kwds@entry=0x0)
at Objects/typeobject.c:1673
#27 0x00007ffff7a04b7b in _PyObject_MakeTpCall (tstate=0x7ffff7e69170 <_PyRuntime+459600>, callable=0x555555aa90d0, args=0x7ffff7fc0078, nargs=0, keywords=0x0)
at Objects/call.c:240
#28 0x00007ffff7982d01 in _PyEval_EvalFrameDefault (tstate=<optimized out>, frame=0x7ffff7fc0020, throwflag=<optimized out>) at Python/bytecodes.c:2711
#29 0x00007ffff7acd682 in PyEval_EvalCode (co=co@entry=0x7ffff75805d0, globals=globals@entry=0x7ffff7619e80, locals=locals@entry=0x7ffff7619e80) at Python/ceval.c:570
#30 0x00007ffff7aec637 in run_eval_code_obj (tstate=tstate@entry=0x7ffff7e69170 <_PyRuntime+459600>, co=co@entry=0x7ffff75805d0, globals=globals@entry=0x7ffff7619e80,
locals=locals@entry=0x7ffff7619e80) at Python/pythonrun.c:1693
#31 0x00007ffff7aec5ab in run_mod (mod=mod@entry=0x555555600a10, filename=filename@entry=0x7ffff7619ff0, globals=globals@entry=0x7ffff7619e80,
locals=locals@entry=0x7ffff7619e80, flags=flags@entry=0x7fffffffd698, arena=arena@entry=0x7ffff753be30) at Python/pythonrun.c:1714
#32 0x00007ffff7aecca2 in pyrun_file (fp=fp@entry=0x55555555a590, filename=filename@entry=0x7ffff7619ff0, start=start@entry=257, globals=globals@entry=0x7ffff7619e80,
locals=locals@entry=0x7ffff7619e80, closeit=closeit@entry=1, flags=0x7fffffffd698) at Python/pythonrun.c:1614
```
next prev parent reply other threads:[~2023-10-19 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 21:53 [ISSUE] " nerdyslacker
2023-10-19 7:20 ` mhmdanas
2023-10-19 13:02 ` nerdyslacker
2023-10-19 14:39 ` sgn [this message]
2023-10-19 15:05 ` sgn
2023-10-20 2:37 ` [ISSUE] [CLOSED] " sgn
2023-10-20 10:01 ` MechDR
2023-10-20 10:02 ` MechDR
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=20231019143929.tMY2s5Bp61_3Mokd8KvJ30CaMMnowdDAzKsNVOgW9uY@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).