all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bjoern Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 56967@debbugs.gnu.org
Subject: bug#56967: 29.0.50; Frequent crashes under Wayland
Date: Sun, 07 Aug 2022 18:14:50 +0300	[thread overview]
Message-ID: <3629604.AQ1hHsVFQY@odin> (raw)
In-Reply-To: <83zgggw0r2.fsf@gnu.org>

Am Sonntag, 7. August 2022, 18:07:29 EEST schrieb Eli Zaretskii:
> > Cc: 56967@debbugs.gnu.org
> > Date: Sun, 07 Aug 2022 17:51:25 +0300
> > From:  Bjoern Bidar via "Bug reports for GNU Emacs,
> > 
> >  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> > 
> > 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
> > 
> > I don't really understand why calling _exit is an acceptable solution
> > anyone that has to safe some state to the disk is lost.
> 
> > I attach the whole conversation to not take anything out of context here:
> Those guys evidently think that an application without display cannot
> do anything.  They forget that even if display connection is lost, and
> even if this is due to some fault of the application, that application
> could still shut down gracefully instead of losing all of the user's
> work, if only GTK wouldn't call _exit "because it's acceptable", or
> "because emacs is a 1980s teletype app", or because whatever other
> ridiculous justifications these guys come up for such misconduct.

I don't know what to say, I'm befuddled too.
The audacity to act such a way as a library.

> > <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
> 
> Really?  Since when does saving data to disk require a display
> connection??

I don't know either, this is what came after:

<ebassi> Because the toolkit has no idea what's left of the system's integrity
<two[m]> how could it start before the compositor?
<Thaodan> the display connection lost doesn't mean the whole system is broken 
but just the compositor. But I assume that the toolkit takes precedence over 
the app it self.
<ebassi> Thaodan: You literally **cannot** know that
<Thaodan> two[m]: background services such as systemd --user services
<two[m]> wouldn't it fail because no $WAYLAND_DISPLAY?
*** First activity: MichaelNazzarenoTrimarchi[m] joined 53 minutes 11 seconds 
ago.
<MichaelNazzarenoTrimarchi[m]> Well the app can really do anything before 
starting the graphic subsystem. It can even wait that Wayland service is 
started before do any specific toolkit initialization 
<Thaodan> MichaelNazzarenoTrimarchi[m]: Exactly, apps such as editors might 
reload their last session which can take quite some time 
<Thaodan> There it makes sense to start as early as possible.
<Thaodan> How can I find out if GTK did an invalid request to the compositor?
<MichaelNazzarenoTrimarchi[m]> That is simple 
<MichaelNazzarenoTrimarchi[m]> You can activate Wayland tracing of message
<MichaelNazzarenoTrimarchi[m]> You can see then message sent to compositor
<MichaelNazzarenoTrimarchi[m]> It's rather difficult that is an application 
bug but could be a client side Wayland part bug








  reply	other threads:[~2022-08-07 15:14 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 [this message]
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
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=3629604.AQ1hHsVFQY@odin \
    --to=bug-gnu-emacs@gnu.org \
    --cc=56967@debbugs.gnu.org \
    --cc=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    --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.