From: devlocalhost <devlocalhost@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Gnome crashes with segfault
Date: Thu, 07 Jul 2022 14:06:52 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37911@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1271 bytes --]
New issue by devlocalhost on void-packages repository
https://github.com/void-linux/void-packages/issues/37911
Description:
### Is this a new report?
Yes
### System Info
Void 5.15.52_1 i686 GenuineIntel uptodate rFF
### Package(s) Affected
gnome-shell-42.3_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4606
https://bugzilla.redhat.com/show_bug.cgi?id=1804968
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973740
I am not sure if these are valid, I just found them similar to my problem
### Expected behaviour
Gnome is not supposed to crash when using it, and have "glitches" like this: https://i.imgur.com/gq9PzYM_d.webp?maxwidth=640&shape=thumb&fidelity=medium
### Actual behaviour
Gnome randomly crashes when using it. For example, when clicking the applications button in overview, or when clicking a random application in applications list
### Steps to reproduce
1. Just use it normally, try launching apps from overview, or clicking the applications icon from overview
2. Crash, with this text thrown to tty
![IMG_20220707_121945](https://user-images.githubusercontent.com/56504654/177769207-4caab3e2-25eb-4a49-8cae-811b0139647a.jpg)
next reply other threads:[~2022-07-07 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 12:06 devlocalhost [this message]
2022-07-07 12:08 ` devlocalhost
2022-07-07 12:08 ` devlocalhost
2022-07-09 14:37 ` devlocalhost
2022-07-09 14:37 ` [ISSUE] [CLOSED] " devlocalhost
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37911@inbox.vuxu.org \
--to=devlocalhost@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).