Цікаво, ні в кого такого не було, як в мене? Коротше, Федора 8, на ній NX-сервер. Коннектюся до неї з Убунти NX-клієнтом, сесія як KDE, так і GNOME. Все добре, поки не починаю користуватися програмою grace (xmgrace). Якимось чином їй вдається вбити цю сесію, при чому відбувається це в найнесподіваніший момент, який важко передбачити.
у відповідному файл ~/.nx/ідентифікатор_сесії/clients останні рядки мало шо говорять:
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x300014c
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 19
Minor opcode: 0
Resource id: 0x300014c
QObject: Do not delete object, 'unnamed', during its event handler!
[/usr/bin/nepomukservicestub] QObject: Do not delete object, 'unnamed', during its event handler!
[/usr/bin/nepomukservicestub] QObject: Do not delete object, 'unnamed', during its event handler!
[/usr/bin/nepomukservicestub] QObject: Do not delete object, 'unnamed', during its event handler!
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
*** kdesktop got signal 1 (Exiting)
Application '/usr/bin/nepomukservicestub' exited normally...
kicker: sighandler called
klauncher: Exiting on signal 1
ksmserver: Fatal IO error: client killed
ICE default IO error handler doing an exit(), pid = 23929, errno = 11
kdeinit: sending SIGTERM to children.
kicker: sighandler called
kicker: Fatal IO error: client killed
ICE default IO error handler doing an exit(), pid = 23866, errno = 4
kdeinit: Exit.
klauncher: Fatal IO error: client killed
XIO: fatal IO error 2 (No such file or directory) on X server ":1192.0"
after 1047 requests (1012 known processed) with 0 events remaining.
DCOPClient::attachInternal. Attach failed Could not open network socket
DCOPClient::attachInternal. Attach failed Could not open network socket
ERROR: Couldn't attach to DCOP server!
startkde: Shutting down...
Warning: connect() failed: : No such file or directory
Error: Can't contact kdeinit!
startkde: Running shutdown scripts...
xprop: unable to open display ':1192'
usage: xprop [-options ...] [[format [dformat]] atom] ...
where options include:
-grammar print out full grammar for command line
-display host:dpy the X server to contact
-id id resource id of window to examine
-name name name of window to examine
-font name name of font to examine
-remove propname remove a property
-set propname value set a property to a given value
-root examine the root window
-len n display at most n bytes of any property
-notype do not display the type field
-fs filename where to look for formats for properties
-frame don't ignore window manager frames
-f propname format [dformat] formats to use for property of given name
-spy examine window properties forever
startkde: Done.
шось схоже з сесією GNOME:
(gnome-panel:24594): libgnomevfs-WARNING **: Failed to re-activate daemon: Connection is closed
cannot open display: :1193.0
Run 'nautilus --help' to see a full list of available command line options.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':1193.0'.
notifier.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :1193.0.
Gmail Notifier v1.6.1b (2009/02/01 23:41:51)
----------
xmllangs: XML file succesfully parsed
Configuration read (/home/noddeat/.notifier.conf)
selected language: English
connecting...
connection successful... continuing
----------
checking for new mail (2009/02/01 23:41:51)
no new messages
----------
checking for new mail (2009/02/01 23:42:12)
no new messages
----------
checking for new mail (2009/02/01 23:42:32)
no new messages
pam-panel-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :1193.0.
gnome-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :1193.0.
cannot open display: :1193.0
Run 'gnome-panel --help' to see a full list of available command line options.
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :1193.0.
якби були ідеї, був би вдячний.
