From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74535@debbugs.gnu.org, Mike Kupfer <kupfer@rawbw.com>
Subject: bug#74535: 30.0.92; partial hang, esp. keyboard events
Date: Wed, 1 Jan 2025 19:58:59 -0600 [thread overview]
Message-ID: <CADwFkmkM-SWBbLT--tZ6ABt6zBvEB6EXFjBg9eLaq9R4L6pD=A@mail.gmail.com> (raw)
In-Reply-To: <86a5d6hff4.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 08 Dec 2024 08:11:59 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Mike Kupfer <kupfer@rawbw.com>
>> cc: 74535@debbugs.gnu.org
>> Comments: In-reply-to Eli Zaretskii <eliz@gnu.org>
>> message dated "Sat, 07 Dec 2024 14:25:51 +0200."
>> Date: Sat, 07 Dec 2024 18:23:48 -0800
>>
>> Eli Zaretskii wrote:
>>
>> > > From: Mike Kupfer <kupfer@rawbw.com>
>> > > Date: Mon, 25 Nov 2024 13:59:48 -0800
>> > >
>> > > Eli Zaretskii wrote:
>> > >
>> > > Okay, I'll revert to 30.0.91 and see if the problem is still there.
>> >
>> > Mike, did you make any progress since then?
>>
>> Well, I've been running 30.0.91 since Nov 25, and I haven't seen the
>> hang during that time.
>>
>> According to my notes, it was 4 weeks between the time I installed
>> 30.0.92 and when I got the hang on MATE. (Sorry, I should have
>> mentioned that earlier.) So I'm not sure how long to let a given build
>> run before declaring it "good".
>
> So I guess we need to wait a few more weeks before we are sure.
>
> Thanks.
That was over 3 weeks ago. Do we feel more confident now?
next prev parent reply other threads:[~2025-01-02 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 19:13 bug#74535: 30.0.92; partial hang, esp. keyboard events Mike Kupfer
2024-11-25 19:27 ` Eli Zaretskii
2024-11-25 21:59 ` Mike Kupfer
2024-12-07 12:25 ` Eli Zaretskii
2024-12-08 2:23 ` Mike Kupfer
2024-12-08 6:11 ` Eli Zaretskii
2025-01-02 1:58 ` Stefan Kangas [this message]
2025-01-02 2:28 ` Mike Kupfer
2025-01-02 3:13 ` Stefan Kangas
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='CADwFkmkM-SWBbLT--tZ6ABt6zBvEB6EXFjBg9eLaq9R4L6pD=A@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=74535@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kupfer@rawbw.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.