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

EggSMClient-WARNING, GConf Err, TCP/IP re Orbit, et al



I'm concerned with one dynamic of the recurring, like instances (stdout below).

Please, do tell of the security risk implied here, and what would be a
reasonable course of investigation / reparation; best practice for
ensuring a properly configured system-- when that system is NOT to
accept connections, for example, on port 80, as it is built to be a
development server, and basic desktop facility.

as copied/pasted here, the following is Fedora gnome-terminal
/home/owner/ "su"'d to root.
in contrast to these occurrences for "root", this user can not account
(in confidence) for such error reporting, stdout while operating as
User (not root), or in another environment, this user is unfamiliar
with any like disparity([1]) between "root" and "User"-- upon general
command execution-- as to launch, for example, in the WM, a GUI like
GEdit. (re: FC5-Fedora 8 [^F6] and various 'buntu'bes).
[(1) As to have exhausted TFM; community resources in search of a resolve ]

[BEGIN STDOUT_01]
(gedit:32160): EggSMClient-WARNING **: Failed to connect to the
session manager: None of the authentication protocols specified are
supported

GConf Error: Failed to contact configuration server; some possible
causes are that you need to enable TCP/IP networking for ORBit, or you
have stale NFS locks due to a system crash. See
http://www.gnome.org/projects/gconf/ for information. (Details -  1:
Failed to get connection to session: Did not receive a reply. Possible
causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.)
[END STDOUT_01]

[BEGIN STDOUT_02]
root nigel8it etc ]# gnome-session --debug
gnome-session[32183]: DEBUG(+): Enabling debugging
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 1:
signum=4 (nil)
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 4 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 2:
signum=7 (nil)
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 7 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 3:
signum=11 (nil)
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 11 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 4:
signum=6 (nil)
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 6 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 5:
signum=5 (nil)
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 5 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 6:
signum=15 0x417290
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 15 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 7:
signum=2 0x417290
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 2 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 8:
signum=8 0x417290
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 8 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 9:
signum=1 0x417290
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 1 signals
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Adding handler 10:
signum=10 0x417290
gnome-session[32183]: DEBUG(+): GdmSignalHandler: Registering for 10 signals
gnome-session[32183]: WARNING: Could not make bus activated clients
aware of DISPLAY=:0.0 environment variable: Did not receive a reply.
Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.
gnome-session[32183]: WARNING: Could not make bus activated clients
aware of GNOME_DESKTOP_SESSION_ID=this-is-deprecated environment
variable: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network
connection was broken.
gnome-session[32183]: WARNING: Could not make bus activated clients
aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/32183,unix/unix:/tmp/.ICE-unix/32183
environment variable: Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.
gnome-session[32183]: DEBUG(+): GsmXsmpServer:
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/32183,unix/unix:/tmp/.ICE-unix/32183

gnome-session[32183]: Gtk-CRITICAL: gtk_main_quit: assertion
`main_loops != NULL' failed
gnome-session[32183]: CRITICAL: dbus_g_proxy_new_for_name: assertion
`connection != NULL' failed
gnome-session[32183]: Gtk-CRITICAL: gtk_main_quit: assertion
`main_loops != NULL' failed
gnome-session[32183]: GLib-GObject-CRITICAL: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
gnome-session[32183]: DEBUG(+): GsmManager: setting client store 0x1802f20
gnome-session[32183]: CRITICAL: error getting session bus: Did not
receive a reply. Possible causes include: the remote application did
not send a reply, the message bus security policy blocked the reply,
the reply timeout expired, or the network connection was broken.
[END]

Must this event be reported, as a bug? If so, whom should receive what?

thank shoes!
pie (because /Peace/ is not a salutation)

-----------------------------------------------------------
i reckon there be no need to bunch panty here, yo. (should it please
the fraternity individuals to gaze upon the notorious flexings of
dinkfellow, then i wish for no pardon... but, for me to poo-pon!)


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