From: Bjoern Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 56967@debbugs.gnu.org
Subject: bug#56967: 29.0.50; Frequent crashes under Wayland
Date: Mon, 08 Aug 2022 11:56:19 +0300 [thread overview]
Message-ID: <2062339.XFdaHZJ8Qi@odin> (raw)
In-Reply-To: <875yj3sbj5.fsf@yahoo.com>
Am Montag, 8. August 2022, 05:40:30 EEST schrieb Po Lu:
> Bjoern Bidar <bjorn.bidar@thaodan.de> writes:
> > I did I had my hole session running, nothing else had that issue.
> > I kept the GTK-Demo running nothing happened it ran just fine.
>
> Thanks.
>
> > After a few hours Emacs exited with the same behaviour as explained in the
> > bug.
>
> Do you see the same if you run Emacs as something other a daemon?
>
> > I on the #gtk channel on what do and I got from ebassi that it is ok to
> > just call _exit.
> > He says it might be the client behaving wrong:
> > <ebassi> Thaodan: It could happen because the client made an invalid
> > request— Wayland mandates that the display server closes the connection
> > in that case
> We don't make raw Wayland requests anywhere, so it must be a bug in GTK.
What could be the way that GTK is used or is emacs with pgtk 99% a run of the
mill gtk app?
> > <ebassi> And if you lose the socket then you'
> > <ebassi> you'll have to find the new one and reconnect
> > <ebassi> Thaodan: Only emacs does that
> > <ebassi> Pretty much literally
> > <Thaodan> "that"?
> > <ebassi> "app may run longer or before the compositor starts"
> > <ebassi> Because emacs is really a 1980s teletype app
> > <Thaodan> What does that change? calling _exit is not a solution.
> > <Thaodan> Lets assume the fault for this happening is emacs, what could
> > cause this?
>
> Outdated information. The PGTK port of Emacs doesn't do anything close
> to that, because GTK doesn't let us.
>
> > <ebassi> Calling exit is perfectly acceptable: the display connection is
> > severed, and that can happen for multiple reasons, including the display
> > server going away
> > <ebassi> There's no "the display server is still running, but it closed
> > the
> > socket" mechanism for the toolkit to use
>
> So why not use exit, which lets the atexit handlers run?
I don't know, can someone ask? I feel like these people act like douches when
some random person asks.
> > <ebassi> The socket got closed
> > <ebassi> The toolkit terminates
> > <ebassi> Thaodan: It could happen because the client made an invalid
> > request— Wayland mandates that the display server closes the connection
> > in that case <ebassi> Or the display server decided to kill the client
> > because it was unresponsive
> > <Thaodan> Why should the toolkit/lib call exit isn't there any better
> > mechanism to doing such a thing in glib or gtk for that matter?
> > <Thaodan> It would be better to not need any hacks to prevent gtk from
> > killing apps.
> > <ebassi> Thaodan: There is no such mechanism
> > <Thaodan> ebassi: OK so what's the idea behind using _exit as a mechanism,
> > doesn't that break any other app that has state so safe too? like for
> > example an office application that wants to safe it's data before going
> > down. <ebassi> I already told you
> > <ebassi> If the display connection is closed by the server, then there's
> > no
> > safe way to store the data
>
> Store the data that is in Emacs core?? How did these people learn to
> write software?
I guess they did but learned that they are always right when there's an issue?
Idk.
next prev parent reply other threads:[~2022-08-08 8:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 7:36 bug#56967: 29.0.50; Frequent crashes under Wayland Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 8:01 ` Eli Zaretskii
[not found] ` <3230275.qDoO4GC8Cx@odin>
2022-08-04 8:21 ` Eli Zaretskii
2022-08-04 11:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 0:18 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:25 ` Eli Zaretskii
2022-08-05 6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:43 ` Eli Zaretskii
2022-08-05 6:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 7:46 ` Eli Zaretskii
2022-08-05 8:26 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 8:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:56 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:40 ` Gregory Heytings
2022-08-05 11:50 ` Eli Zaretskii
[not found] ` <2972937.jrzt3BHeHG@odin>
2022-08-05 6:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 14:51 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:07 ` Eli Zaretskii
2022-08-07 15:14 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:44 ` Eli Zaretskii
2022-08-08 2:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 2:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 6:07 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 8:56 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-08 10:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 13:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 17:06 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:31 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <2189728.upBv5HjrgE@odin>
2022-08-05 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <1917872.q2Y8mqo1ke@odin>
2022-08-05 6:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:55 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 7:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 16:02 ` Gavin Massingham
[not found] <CAH3b6=SPM_Pys81fi-_Eu=VXO8mETqV+s0YFC+8c1huv4dmh9Q@mail.gmail.com>
2022-08-04 18:29 ` Eli Zaretskii
2022-08-05 7:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=2062339.XFdaHZJ8Qi@odin \
--to=bug-gnu-emacs@gnu.org \
--cc=56967@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=luangruo@yahoo.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.