On Fri, 2017-12-29 at 11:27 +0100, Andre Klapper wrote: > On Fri, 2017-12-29 at 06:46 +0100, Ralf Mardorf wrote: > > FWIW usually there is a file ~/.xsession-errors that contains the > > output > > of all running GUI apps. > > No there is not, in times of Wayland instead of X. > And I'd doubt anyway that this would be any helpful.
There even necessarily is ~/.xsession-errors when running X, as long as the user doesn't redirect the output or the user chose a display manager doing this. That's why I've written "FWIW" and "usually", let alone that I first explained how to run evolution from command line. However, while reading the mixture of output redirected to ~/.xsession-errors often isn't that clear as running a GUI app from command line, it still could be very helpful, if a culprit e.g. is easy to "grep" by terms such as "error", "evolution", "lib", in addition with "| grep -v -i warning" to eliminate all the waste, that isn't filtered when simply launching an app from command line. Résumé: Mentioning ~/.xsession-errors makes very well sense. There is a reason that this file usually is provided by default installs of user-friendly distros, even if they migrated already to Wayland while a lot of issues caused by Wayland still aren't solved yet. AFAIK know for good reason they allow still to chose between a Wayland and a X user session by the display manager's greater. _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
