unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "bdju" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 51889@debbugs.gnu.org
Subject: bug#51889: changing focus to Chromium can crash Sway entirely
Date: Tue, 16 Nov 2021 04:14:33 -0600	[thread overview]
Message-ID: <CFR4IGZ9V3QY.3UF7SL0N3A827@masaki> (raw)

guix (GNU Guix) 33a80e111096b05af3d60576dfcb2d67099dc60e
Guix System

For the second time now, when focusing the chromium window, Sway has
entirely crashed. I'm using ungoogled-chromium-wayland.

I have the following lines in my Sway config:

```
    # focus browser (chromium)
    bindsym ctrl+Shift+$mod+b [app_id="chromium-browser"] focus
```

So, I pressed those keys to jump right to it, then my monitors went
black and everything disappeared. I believe last time this happened,
I hadn't made that keybind yet, but I was similarly using a script to
focus chromium by its app_id with a swaymsg command before.
Chromium had some coursera tabs open. The first time there was likely
a paused video. I don't think I had a video up this time. (I am using
Chromium exclusively for coursera stuff recently because audio is broken
in qutebrowser and if I watch the lectures in mpv+youtube-dl I lose the
feature of being able to click part of the transcipt to jump to that
part of the video. Also, I have to let the video play in a browser
anyway so the task gets marked as complete.)

I'm not sure if this will be at all easy to reproduce. I jumped to the
Chromium window dozens of times without crashing all of Sway before, so
some special situation must have to happen. I had another video open in
mpv, some chat programs open, and qutebrowser at the time. I wasn't in
danger of running out of RAM the last time I'd looked. I think CPU
usage was normal.




                 reply	other threads:[~2021-11-16 10:17 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=CFR4IGZ9V3QY.3UF7SL0N3A827@masaki \
    --to=bug-guix@gnu.org \
    --cc=51889@debbugs.gnu.org \
    --cc=bdju@tilde.team \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).