Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Firefox becomes unresponsive after a while
Date: Mon, 12 Sep 2022 04:15:29 +0200	[thread overview]
Message-ID: <20220912021529.PqyQM9JU2EmsoGaHIqyiVpVbME0RQvt-f4nF5Wn2B9g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35460@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

Closed issue by meator on void-packages repository

https://github.com/void-linux/void-packages/issues/35460

Description:
### System

* xuname:  *Void 5.15.19_1 x86_64 GenuineIntel uptodate rrrmdFFFFFFF*
* package:  *firefox-96.0.2_1*

### Expected behavior
Firefox working normally.
### Actual behavior
When I leave Firefox running for a while, everything stops working. I can't create or close tabs by clicking the buttons nor by using keyboard shortcuts, I can't open links, I can't use buttons, I can't edit the URL bar... Apart from that, everything else works normally. I can switch tabs, links I hover over get highlighted, I can even create and close tabs via right-clicking the tab bar... It's really weird.
### Steps to reproduce the behavior
I'm not aware of anything special on my system that could cause this. I have tried to run Firefox with all extentions disabled and the problem occurred again. I can reproduce this by using Firefox in general. If there are any log files or some information that could help diagnose the problem, I can post it here.

      parent reply	other threads:[~2022-09-12  2:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 16:35 [ISSUE] " meator
2022-02-07 22:12 ` ram02z
2022-02-08  0:39 ` cinerea0
2022-02-10 15:52 ` Vistaus
2022-02-10 16:16 ` daerich
2022-02-10 16:21 ` daerich
2022-02-10 16:36 ` ram02z
2022-02-12  0:10 ` wertz14
2022-02-13 18:30 ` ram02z
2022-02-13 18:55 ` Vistaus
2022-02-13 19:03 ` ram02z
2022-02-14  5:36 ` zlice
2022-02-14 10:34 ` Vistaus
2022-02-14 16:52 ` meator
2022-02-24 17:20 ` meator
2022-02-24 18:04 ` Vistaus
2022-03-10 11:44 ` jdnumm
2022-03-10 14:09 ` meator
2022-03-10 14:23 ` jdnumm
2022-05-15  5:55 ` AviKav
2022-05-15 12:30 ` zlice
2022-05-27 19:52 ` zlice
2022-05-29  9:39 ` biopsin
2022-08-28  2:14 ` github-actions
2022-09-12  2:15 ` github-actions [this message]

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=20220912021529.PqyQM9JU2EmsoGaHIqyiVpVbME0RQvt-f4nF5Wn2B9g@z \
    --to=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).