Fatal python error pygame parachute segmentation fault python runtime state initialized

Fatal Python error: pygame_parachute: (pygame parachute) Segmentation Fault #304

Please include the log file

If the «An error has occurred»-dialog mentions a log file, then please include the log file to this report. A simple «copy-paste» of the log file contents into the report is sufficient.

Please include a savegame that can reproduce the issue
If you can, please provide a savegame where it is easy to demonstrate the problem.

GitHub doesn’t let me attach a save game.

To Reproduce
If possible, please describe the steps to reproduce the behavior:

1. Go to ‘. ‘
2. Click on ‘. ‘
3. Scroll down to ‘. ‘
4. See error

If applicable, please add screenshots to help explain your problem.

I’m not really sure what caused it.

Additional context
Add any other context about the problem here.

The text was updated successfully, but these errors were encountered:

I am sorry to hear that you experienced a crash. I notice that it happens in pygame’s C code and you have a nix-based build of pygame. Could you please check with your distribution to see if there are a known crash report against pygame in their bugtracker and if not then report it there?

This is to rule out that it is a bug in the distribution build.

I have a similar error:
$ singularity —theme=vector —nosound
Singularity 1.00 (commit: 2ebc2f3)
Running under Python 3.9.5 (default, Jul 15 2021, 11:19:42) [GCC 10.3.0]
pygame 2.0.1 (SDL 2.0.10, Python 3.9.5)
Hello from the pygame community. https://www.pygame.org/contribute.html
The error-log configured as /home/user/.local/share/singularity/log/error.log (lazily created when something is logged)

Fatal Python error: pygame_parachute: (pygame parachute) Segmentation Fault
Python runtime state: initialized

Current thread 0x00007f3d8edb6640 (most recent call first):

Thread 0x00007f3d91527740 (most recent call first):
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 230 in show
File «/usr/lib/python3.9/site-packages/singularity/code/screens/message.py», line 119 in show
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 125 in call_dialog
File «/usr/lib/python3.9/site-packages/singularity/code/screens/message.py», line 44 in show_list
File «/usr/lib/python3.9/site-packages/singularity/code/screens/map.py», line 639 in on_tick
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 405 in call_handlers
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 390 in handle
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 231 in show
File «/usr/lib/python3.9/site-packages/singularity/code/safety.py», line 64 in safe_call
File «/usr/lib/python3.9/site-packages/singularity/code/screens/map.py», line 580 in show
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 125 in call_dialog
File «/usr/lib/python3.9/site-packages/singularity/code/screens/main_menu.py», line 104 in new_game
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/button.py», line 247 in activated
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/button.py», line 213 in activate_with_sound
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/button.py», line 199 in handle_event
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 405 in call_handlers
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 390 in handle
File «/usr/lib/python3.9/site-packages/singularity/code/graphics/dialog.py», line 231 in show
File «/usr/lib/python3.9/site-packages/singularity/init.py», line 382 in main
File «/usr/bin/singularity», line 33 in
Aborted (core dumped)

Sorry to hear it crashes for you (even with the theme work around). By the looks of it, my answer to ryantm is also relevant to your case. Namely, we need to figure out if this bug should go to your Linux distribution or pygame upstream.

Given there is not a large influx of «pygame crashes» bugs in the pygame tracker, my gut feeling points to a bug in the distribution build/packaging — but it at best a vague gut feeling at this point. It would help me considerably if you could confirm that you are using a distribution provided pygame and (if so) ensure that the distribution has an open bug about your problem.

As you can see from paths where game was deployed, first reporter used NixOS (the operating system where each user compile his own instance of application). Mine distribution is Gentoo, which have the same properties. There is no much perspectives to write such bugs into bugtrackes of these kind of distributions.

@EinstokFair I didn’t actually compile it, I downloaded it from the cache. Also NixOS/nixpkgs has a GitHub issue tracker where these kind of problems can be posted. However, there are currently no open problems on that issue tracker for pygame at this time. More investigation required.

«More investigation required. »

There are two actions possible (independently or simultaneously):

1. to post a bug into bugtracker and forget about this project
2. to study the core dumping in linux and trying to provide more details or increase quantity of debug information

Your sentence can be read as «I don’t want neither post a bug into NixOS, nor have time/capabilities/will to perform investigation, and asking you to do that». I neither want to post a bug into gentoo bugtracker, because I know how low the gentoo developers count and how small their interests for nonsystem appications.

You can also try to use pygame + numpy from pip instead of from your distribution and then download the singularity source code from https://github.com/singularity/singularity/releases/tag/v1.00 using PYTHONPATH=. python3 -m singularity + the relevant runes to make sure you are using the pip-installed version of pygame + numpy rather than the distribution provided ones (If possible, I would recommend that you uninstall pygame and numpy in your distribution manager to be completely sure but that might have consequences for other things you have installed).

This would enable us to determine whether it is the distribution provided build that is broken or pygame in general.

I can’t use side binaries (such are ones from side package manager), because my religion doesn’t allow me that. Otherwise I would use debian, not gentoo.
My distribution doesn’t provide binaries. So what we can talk about is versions, compilation switches and runtime configuration.

Источник

Fatal Python error: (pygame parachute) Segmentation Fault #6118

Versions

• Python: v3.5.3
• OS: Raspbian / Debian 9.4
• Kivy: v1.10.1
• Kivy installation method: pip3 install —user kivy

Description

I get a segmentation fault at startup.
Maybe #6007 is related. But I don’t have that SDL backend. Also export KIVY_GL_BACKEND=gl did not help.

Code and Logs

When I debug with GDB, I see this:

A bit strange that I cannot unroll the full backtrace. I guess the stack got corrupted.
Interesting that this is in libcaca. Why is it loading that?

The text was updated successfully, but these errors were encountered:

Looks like you have compiled Kivy against pygame, but this is deprecated and no longer really supported. Try installing SDL2 and reinstalling Kivy, it should use SDL2 if available.

Well, I still would argue that it should not crash in any case. But not sure if to blame Kivy or some of the related libs.

Also, I did not compile Kivy, but just did pip3 install kivy . Which installed some prepackaged wheel package for me, so it was already pre-compiled.

For reference, maybe if other people find this report, to fix this:

• I installed some other needed dependencies to be able to really compile Kivy: pip3 install —user cython . (I did apt-get install build-essential and some other things before that, and I think this is also needed.)
• To force to install Kivy from source: pip3 install -I —no-binary «:all:» —user kivy
• Then I got the error failed to open vchiq instance . This was because I was not in the video group, so I added my user.
• Now the Kivy demo app started, but I just got a blank screen. However, on the terminal output, I noticed this: No protocol specified , Unable to connect to X server . The X server connection did not work because this was another user, and I had to grant access to the /home/pi/.Xauthority file ( chgrp users . && chmod g+rw . ). This actually might also have been the reason why PyGame ended up using libcaca originally, and maybe the crash was just libcaca related.
• Now it works. Although the performance is somewhat slow. Maybe increasing gpu_mem=128 in the /boot/config.txt somewhat fixes this.

On the rpi you can use the rpi-specific window backend, which doesn’t require X and may have superior performance. I’m not familiar with rpi though and not sure how to make sure it’s used.

Источник

Hello World Kivy causes Fatal Python error: (pygame parachute) Segmentation Fault Abort trap: 6 #1844

Kivy seem to have broken itself.
Originally I was doing ‘kivy main.py’ on 2 apps.
For both, ‘kivy main.py’ would make them run properly on the desktop.

I then wanted to package it for android.
I had a lot of problems with this.
Today, I finally managed to package the app for android and create the APK for the 2 apps.
The first app is a hello world app and it ran perfectly on the android device.
The other one is more complicated and it crashed in the android device. According to the debug messages it is something to do with unicode.
This was not an issue when run in the desktop.
Therefore I wanted to test it further in the desktop.
Unfortunately, this time when I ran ‘kivy main.py’. suddenly I got this error:

Fatal Python error: (pygame parachute) Segmentation Fault
Abort trap: 6

I googled this and supposedly it had something to do with OpenGL and rendering images. But my app doesn’t use images.

To prove to myself that this is a kivy error and not my coding error, I then ran ‘kivy main.py’ on the kivy hello world app that I created.

As expected, it also caused the same error to display.
I don’t know how to replicate / reproduce this error. but all i know is that kivy main.py use to work but for some reason it is not any more.

How can I fix this?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

The text was updated successfully, but these errors were encountered:

Источник

[PPA] Fatal Python error: (pygame parachute) Segmentation Fault #1004

Got Fatal Python error: (pygame parachute) Segmentation Fault

Worked before updating with PPA to 1.6.0.

Window provider is initialized. My system runs on Linux Mint 14 64bit Cinnamon.

Somehow the log is very short even though I enabled debug, but here you can see most of my configuration (this is from another bug report):
https://gist.github.com/anonymous/4318789

The text was updated successfully, but these errors were encountered:

Would you please provide a snippet that we can reproduce this issue with.

Same error on Ubuntu 12.04 with current version from ppa (1.6.0)
Problem occurs when importing:

Function core_select_lib tries to create kivy.core.window.window_pygame.WindowPygame and then my debuger freeze.

@lionbestpl if your app was working before and isn’t working now please post a small snippet that reproduces this issue, If this is the first time you are trying out kivy, then update your graphics driver.

@akshayaurora Yes, I try it first time. This simple line of importing module from my last post, reproduces this error.
Ubuntu 12.04 64bit with python 2.7 and NVIDIA Driver 310.14; pygame OpenGL example is working well.

Having an opengl example that works doesn’t mean anything 🙂 It could not use what we use.
Please give us a gdb backtrace with:

And when it stuck, do control+c, and then:

And then post the result 🙂

I shall rebuild it with debuging symbols perhaps, or is there one already?

could you try to remove your dist kivy, clone the current version in github, and do:

And reexecute the same gdb commands ?

I don’t know if it helps, but this is what I get when trying to start my game with gdb —args python main.py :
https://gist.github.com/snapy666/f714251f93edf1189f55

That’s the same backtrace as before, doesn’t help either

I use Kivy 1.6.0 from git and this issue do not occurs. Anyway is good to have working version on PPA.

@tito — Could the generated code by Cython be malformed? I mean causing these problems?
We are also using the latest code of Cython for our stable builds.

I used the Kivy-1.6.0.tar.gz from github to make the rpm packages and tested it now using the screenmanager.py — example. Works well!

I’m curious whether the tag’ed commit and the archive got other contents :/
PS: Btw. I’m not using the latest code of Cython to make these rpm builds.

I also had this exact same issue. When I upgraded to v1.6.0 using the Ubuntu PPA, my Kivy programs would produce pygame segfaults where they had worked before with the previous version. When I uninstalled the PPA package and installed via the git repo, it worked fine.

Same problem here on Ubuntu 12.04, AMD64.

I installed Kivy via the following commands:
sudo add-apt-repository ppa:kivy-team/kivy
sudo apt-get update
sudo apt-get install python-kivy

I had tried to simply:
sudo easy_install kivy
But that still gives a Cython error — perhaps due to the issue discussed in #814 (closed).

sudo pip install cython

Fails on my system as well.
Edit: Nevermind. A quick apt-get install python-dev causes pip install cython to work fine.

Install from source is cranky (pygame is unhappy, for some reason. Maybe I’ve just reinstalled too many different ways tonight. It probably isn’t related to this issue. — But it is preventing me from testing with a source install, at the moment, sorry.

So far all I have confirmed is that there are a lot of wrong ways to install Kivy on Ubuntu. :/

I’m going to try a source install within a virtualenv in a few minutes. I think that may get me enough of a clean room to get the kivy source install to work. That should confirm whether this issue also occurs after a source install. (Fingers crossed.)

After installing all of the prerequisites for Kivy:
sudo apt-get install python-setuptools python-pygame python-opengl
python-gst0.10 python-enchant gstreamer0.10-plugins-good python-dev
build-essential libgl1-mesa-dev libgles2-mesa-dev cython

Kivy works fine, even installed from the PPA.

So maybe the PPA is somehow not forcing something to install that should be installed, from that list above.

Edit: But it only works fine within the virtualenv, where I installed Cython using pip.
Outside the virtualenv, I still get the pygame segfault.

I am back to thinking this is somehow connected to #814. Perhaps the PPA is tickling the same issue by grabbing different version of Cython via Apt-get than is installed via pip.

Anyway, this is out of my depth, and I now have a workaround that works for me.
Please let me know if there’s anything specific I can test on my system that would help.

I have the same problem. After installing all the dependencies using recent version from PPA i get the same error as lionbestpl. Using easy_install, everything works flawlessly. Xubuntu 12.04 x64.

@thopiekar could you look at updating the ppas(compile them with the older version of cython). It seems the latest version of cython has some issues.

@akshayaurora sure. I will also check it with cython which is uploaded now — in case the problem is now fixed in their PPA (Cython).

While busy at the moment and lerning for exams I triggered a rebuild. Just wait for the update and give feedback whether it works or not. If not I’ll need to invest more time on it later.

Источник

Были похожие проблемы и у этой тоже. Нашел способ их решить:

Через несколько недель (была эта проблема даже раньше) я рад сообщить, что решил эту проблему!

1-я часть моей проблемы (http://i.stack.imgur.com/WpkjR.png): Я решил это, отредактировав скрипт setup.py с добавлением в него части «исключает». Результатом стало успешное создание исполняемого файла!

Измененный скрипт setup.py:

from distutils.core import setup
import py2exe
setup(windows=['source_static.py'], options={
          "py2exe": {
              "excludes": ["OpenGL.GL", "Numeric", "copyreg", "itertools.imap", "numpy", "pkg_resources", "queue", "winreg", "pygame.SRCALPHA", "pygame.sdlmain_osx"],
              }
          }
      )

Итак, если у вас есть похожие проблемы, просто поместите эти «отсутствующие» модули в эту строку «исключает».

2-я часть:

После того, как мне удалось создать исполняемый файл, у меня возникла следующая проблема: «Приложение запросило среду выполнения необычным образом завершить его. Пожалуйста свяжитесь…«. После нескольких дней поиска и размышлений о том, как решить эту другую проблему, я нашел способ сделать это. Я не мог поверить, что проблема была такой абсурдной. Проблема была в моем коде с определением шрифта:

font1 = pygame.font.SysFont(None, 13)

После изменения «Ничто«к имени некоторого системного шрифта (например,» Arial «(должно быть строкой)), и компилируя, я не мог поверить, что мой файл .exe работает!

font1 = pygame.font.SysFont("Arial", 13)

Конечно, вы можете использовать свой собственный шрифт, но вы должны указать его путь и определить его в своей программе.

Итак, для всех, кто сталкивается с этими проблемами, попробуйте эти шаги, и я надеюсь, что у вас все получится. Я очень надеюсь, что это поможет вам, потому что я потерял дни и недели, пытаясь решить эти проблемы. Я даже пытался создать свой файл .exe со всеми версиями python и pygame, со многими другими сборщиками .exe и сценариями установки, но безуспешно. Помимо этих проблем, у меня было много других проблем, но я нашел ответы на них на stackoverflow.com.

Я счастлив, что нашел способ решить эту проблему и помочь вам, если вы столкнетесь с такими же.

Небольшие советы (что я тоже делал):

1-й: обновите свою библиотеку Microsoft Visual C ++ до последней версии.

2-й: если у вас есть изображения или шрифты, похожие на нужные вашей исполняемой программе, включите их в расстояние папка (в которой был создан ваш EXE-файл).

3-й: когда вы создаете файл .exe, включите все необходимые файлы в папку, в которой находится ваш сценарий setup.py (все файлы и каталоги, которые использует ваш основной сценарий).

Использованный Питон 2.7 x64, Pygame и py2exe.