From: HiPhish <hiphish@posteo.de>
To: help-guix@gnu.org
Subject: OpenGL applications crash entire system (foreign distro)
Date: Sun, 08 Sep 2019 13:35:58 +0200 [thread overview]
Message-ID: <2126298.ElGaqSPkdT@aleksandar-ixtreme-m5740> (raw)
Hello Guix,
I have noticed that on my foreign distro (Kubuntu 19.04) running an OpenGL
application crashes the entire system. First everything becomes unresponsive
(except the mouse cursor), then the screen goes off and on and eventually I'm
logged out, but even after logging back in everything is messed up. The only
way out is to hard-reset the computer (hold down power button until the power
goes off) and restart.
I have noticed this behaviour first when I followed the Learn OpenGL Tutorial
(first lesson involving actual OpenGL[1]), but I thought that maybe I was doing
something wrong or that the fault was with my system (I'm using the packages
glfw, gcc-toolchain and mesa in a Guix environment). Then today I tried the
Kitty terminal emulator (package kitty) and the same thing happened.
However, after I installed Kitty through APT it works perfectly fine, so the
problem is in the packages that Guix installs. I can live with a slightly
outdated Kitty, but the Guix environment is the real killer feature I don't
want to miss.
Is there anything that can be used to track down and fix the issue? I would
guess that it's because of the mesa package, but that's just a guess. My
system specs:
OS: Ubuntu 19.04 x86_64
Kernel: 5.0.0-27-generic
DE: KDE
WM: KWin
CPU: Intel i5 650 (4) @ 3.201GHz
GPU: AMD ATI Radeon R7 370 / R9 270/370 OEM
Memory: 2442MiB / 5949MiB
Thanks for your time.
[1] https://learnopengl.com/Getting-started/Hello-Window
reply other threads:[~2019-09-08 11:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2126298.ElGaqSPkdT@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=help-guix@gnu.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).