-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kupfer seems broken with Python 3.11.8 (but not 3.11.7) #176
Comments
I don't see any problem with python 3.11.8 on Debian Sid. |
Same here. I can't find any hint using the console output or even |
I don't see any problem on fresh Arch installation (py 3.11.8, xfce4, Kupfer from repo or git and enabled all plugins). |
This is the dump I get from running in a terminal: (this is without debug info, i will try that next) ` INF [kupfer.core.sources] SourceController: Initial sources load (kupfer.py:4639): Gdk-CRITICAL **: 07:49:39.371: gdk_app_launch_context_set_screen: assertion 'screen == NULL || gdk_screen_get_display (screen) == context->display' failed |
I've attached a file where i had a run WITH debug info on as well. |
Look like problem with gdk and detecting default display. Maybe some other updates take place (gi, gtk, gdk) or gi binding in Arch is broken. Please comment or remove line 537: |
On try_close_unused_displays current display is put in skip_displays list and is not closing. But compare Display objects don't work right and default / current display may be tried to close. Normally this should be harmful. Now skip_displays list contains displays name. Also - if somehow - there is no default_display - do not close anything. Close: kupferlauncher#176 (maybe)
@KarolBedkowski - i've been running with that line disabled for the entire weekend now and if does indeed seem to have fixed the issue! I haven't had any segmentation faults since! |
Environment
Kupfer Version: 325
Window Manager: xfwm4
Desktop Environment: XFCE
Linux Distribution: Arch Linux
Actual Behaviour
Running fully update Arch (as of 2024-04-09) with the latest Python (3.11.8) the program crashed with segmentation fault. The crash does not occur immediately but after some time when activating it through my selected shortcut keys.
Running with debugging on the terminal does not show any information as to why it crashed. The log only shows the output from processes started through kupfer.
Reverting back to previous version of python 3.11.7, this behaviour is not observed.
I'm not sure if this a problem within kupfer itself or a bug in python.
Expected Behaviour
Kupfer should run stable on version of Python > 3.0
The text was updated successfully, but these errors were encountered: