Gajim - 2023-07-06

Hi, can there be an automatic closure due to phyton?

huh ss01 i dont quite understand what "automatic closure" is referring to here

> huh ss01 i dont quite understand what "automatic closure" is referring to here The application just closes and that's it, I accidentally discover that it is closed, without any error

ss01: run it from the terminal, wait for a crash, see the last lines

quite likely some wayland compositor thing, or a crash in libsoup

mjk: Tell me which file to run via cmd and the command to run

ss01: oh, are you on windows? look for gajim-debug.exe in the installation dir

File gajim-debug.exe right?

right

Yes, I launched it, it displays the status, thank you, let me contact you when the closure occurs, I think you understand this perfectly

make sure you've started it from the command line, not clicked on the exe

(the console window would close after a crash)

A couple of notifications are already shown at startup C:\Program Files\Gajim\bin>Gajim-Debug.exe No plugin translation path available (org.gajim.Gajim:9464): GStreamer-WARNING **: 21:08:10.161: Failed to load plugin 'C:\Program Files\Gajim\lib\gstreamer-1.0\libgstlibav.dll': ?? - c¤?- гЄ § --лc ┐R¤г<м. This usually means Windows was unable to find a DLL dependency of the plugin. Please check that PATH is correct. You can run 'dumpbin -dependents' (provided by the Visual Studio developer prompt) to list the DLL deps of any DLL. There are also some third-party GUIs to list and debug DLL dependencies recursively. (org.gajim.Gajim:9464): Gtk-WARNING **: 21:08:11.286: Theme directory 16x16/actions of theme hicolor has no size field

I started as an administrator, as far as I know the window as an administrator does not close automatically?!

forget debug.exe

start your normal Gajim, activate debug loggin in preferences

it will write a debug file to a folder

otherwise you will not catch the crash

and restart Gajim after you enabled the debug setting

I have already contacted here and provided a debugging file, they told me that something from the outside closes the program, and advised me to upgrade to version 1.8.0, but I have not solved the reason, I suspect it has something to do with Python, because there were no such problems before installing it

I wrote here on July 27

yes i remember

if the log still says SIGINT at the end

its still the same problem, i have no ideas how to debug what kills the process

I also installed the Process Monitor application, but my knowledge of error analysis is not enough to figure it out

do you have another windows machine available

then we could at least verify that its a problem with this specific machine

SIGINT/SIGTERM received

I noticed that this happens after installing python, could it be related somehow?

Because sometimes I need to install python and some modules, after that the closure of gajim begins

Package Version https://conference.gajim.org:5281/pastebin/62fb2f61-cf1f-4d58-b359-f1e4fd3548b0

and what do you do with your other python?

do you run applications, and kill them at the end?

Gajim of course also starts a python process

if whatever you do with your other python, starts looking and killing python processes

it might kill the wrong one

I use some scripts for automation, such as downloading data from websites and parsing, but this happens rarely and does not work in parallel with Gajim, the last time I ran scripts 2 weeks ago