[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Gnome 3 crash with iceweasel and chromium



On 19/10/11 14:25, Camaleón wrote:
On Wed, 19 Oct 2011 12:01:59 +0100, José Silva wrote:

a few days ago, when it became available, and now I'm experiencing
crashes (goes to login screen) with several web pages. Sometimes it
repeats with the specific page, sometimes not. Happens both with
iceweasel and chromium, didn't try with epiphany.

So gnome-shell only crashes when you use a browser?

Yes, up to now.

If the crash is fully reproducible, that's something to take into account.

It became random and less frequent.

(...)
Okay, you can grep that file (grep -i "gnome-shell $HOME/.xsession-
errors") to put the focus into the gnome-shell crash.


It happened again several times. I went into console mode right after the crash. I think it's better to let you know slightly more than just grep gnome-shell that would only capture one line which I doubt is that relevant; here it goes:

(gnome-settings-daemon:7788): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 104 (Connection reset by peer) on X server :0.

(gnome-power-manager:7781): Gdk-WARNING **: gnome-power-manager: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

gnome-session[7728]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
system-config-printer-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
      after 11 requests (11 known processed) with 0 events remaining.
kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

(gnome-screensaver:7837): Gdk-WARNING **: gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

[1319326506,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
<unknown>: Fatal IO error 104 (Connection reset by peer) on X server :0.

(gdu-notification-daemon:7845): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

firefox-bin: Fatal IO error 104 (Connection reset by peer) on X server :0.

(nm-applet:7844): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Window manager warning: Log level 16: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

gnome-shell-calendar-server[7861]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Regards,
jss


Reply to: