[OpenIndiana-discuss] Metacity core dumps

[Gary Gendel]

Found an associated log file.  It looks like the client may be 
misbehaving but it still shouldn't cause gdm and metacity to crash.

On 3/25/12 7:59 AM, Gary Gendel wrote:
> I have a vnc client that I was configuring and I noticed that metacity 
> was core dumping.  All I did was to get the login screen to display 
> and then close the client's session. I've enclosed the pstack output 
> for a core file.  The pstack output is the same for the other core dumps.
>
> Let me know if there is something I should try to give better 
> information.  Is this a know issue or should I make a bug report?
>
> BTW, I'm using oi_151a2 on a V20z (64-bit AMD).
>
> Regards,
> Gary
>
>
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

-------------- next part --------------
_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root

** (gnome-settings-daemon:6924): WARNING **: Call to screen_info_new is too frequent, skipping...

** (gnome-settings-daemon:6924): WARNING **: Call to screen_info_new is too frequent, skipping...

** (gnome-settings-daemon:6924): WARNING **: Call to screen_info_new is too frequent, skipping...

** (gnome-settings-daemon:6924): WARNING **: Call to screen_info_new is too frequent, skipping...

(gnome-settings-daemon:6924): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-settings-daemon:6924): atk-bridge-WARNING **: IOR not set.

(gnome-settings-daemon:6924): atk-bridge-WARNING **: Could not locate registry
** (<unknown>:6927): DEBUG: Client registered with session manager: /org/gnome/SessionManager/Client1
Window manager warning: Failed to read saved session file /var/lib/gdm/.config/metacity/sessions/101214946a7899eaa9133263107298232700000069090004.ms: Failed to open file '/var/lib/gdm/.config/metacity/sessions/101214946a7899eaa9133263107298232700000069090004.ms': No such file or directory
** (process:6932): DEBUG: Greeter session pid=6932 display=::ffff:127.0.0.1:10.0 xauthority=/tmp/gdm-auth-cookies-sCaifd/auth-for-gdm-PCaifd/database

** (gnome-power-manager:6931): WARNING **: DBUS error: Could not get owner of name 'org.gnome.ScreenSaver': no such name
** (gnome-power-manager:6931): DEBUG: proxy is NULL, maybe the daemon responsible for org.gnome.ScreenSaver is not running?
Xlib:  extension "DPMS" missing on display "::ffff:127.0.0.1:10.0".

** (gnome-power-manager:6931): WARNING **: ERROR: Caller doesn't possess required privilege to change the governor: Syslog might give more information
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00029 (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00029 (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00029 (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
The application 'gnome-settings-daemon' lost its connection to the display ::ffff:127.0.0.1:10.0;
most likely the X server was shut down or you killed/destroyed
the application.
Window manager warning: Fatal IO error 131 (Connection reset by peer) on display '::ffff:127.0.0.1:10.0'.
The application 'gnome-session' lost its connection to the display ::ffff:127.0.0.1:10.0;
most likely the X server was shut down or you killed/destroyed
the application.
gdm-simple-greeter: Fatal IO error 131 (Connection reset by peer) on X server ::ffff:127.0.0.1:10.0.
gnome-power-manager: Fatal IO error 131 (Connection reset by peer) on X server ::ffff:127.0.0.1:10.0.
<unknown>: Fatal IO error 131 (Connection reset by peer) on X server ::ffff:127.0.0.1:10.0.
Window manager warning: Could not find display for X display 81a4f10, probably going to crash
Bug in window manager: IO error received for unknown display?
gdm-simple-greeter: Fatal IO error 131 (Connection reset by peer) on X server ::ffff:127.0.0.1:10.0.
gnome-power-manager: Fatal IO error 131 (Connection reset by peer) on X server ::ffff:127.0.0.1:10.0.