https://bugs.kde.org/show_bug.cgi?id=435313
--- Comment #6 from edgars.po...@zohomail.eu --- I ran `brave --enable-logging=stderr --v=1 > log.txt 2>&1` to open the Brave browser with logging enabled, and rebooted the system both with the prompt and with a command. First thing that I have noticed is that rebooting with a command(no crashes) is that the log file includes a "Histogram" And the second is that rebooting with the prompt (Brave thinks that it as crashed) the last two log entries are: > [2211:2211:0403/125901.829967:ERROR:connection.cc(66)] X connection error > received. > [2211:2227:0403/125901.829900:ERROR:connection.cc(66)] X connection error > received. Another time it is: > [1989:1989:0403/131034.610368:WARNING:browser_main_loop.cc(273)] Gdk: brave: > Fatal IO error 11 (Resource temporarily unavailable) on X server :0. root And another: > [1825:1831:0403/131229.024627:ERROR:connection.cc(66)] X connection error > received. > [1649:1649:0403/131229.025664:WARNING:browser_main_loop.cc(273)] Gdk: brave: > Fatal IO error 11 (Resource temporarily unavailable) on X server :0. > [1825:1825:0403/131229.025584:ERROR:connection.cc(66)] X connection error > received. So it may be that the X server gets shut down before the browser has the chance to close? That may explain why it has no problems when using `shutdown -r now`, because they probably kill processes in a different order -- You are receiving this mail because: You are watching all bug changes.
