Sponsored Content
Special Forums UNIX and Linux Applications vnc viewer presents black screen along with GNOME settings daemon errors. Post 302833197 by Miguel E. Perez on Tuesday 16th of July 2013 12:29:08 PM
Old 07-16-2013
vnc viewer presents black screen along with GNOME settings daemon errors.

Hello folks,

I'm remotely connecting through VNC to two machines, each running Red Hat 5.9, from mine which is running Windows 7. Both connections were working well before. However, now one of the machines only gives me a black screen, with a pop up that says:

"There was an error starting GNOME Settings Daemon. Some things, such as themes, sounds, or background settings may not work correctly. The last error message was: 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."

I've searched all over the net for a solution to no avail. One thing I tried was deleting the following files in hopes of resetting my gnome environment but this did not help either.

Files: /tmp/orbit-<user>, .gconf, .gconfd, .gnome, .gnome2 and .metacity.

I have attached the two vncviewer log files, one from the connection that still works well and the other from the one that gives me the above errors, named bad and good respectively.

I'm new to the forum so I apologize if this is not the most adequate forum section for my problem or if I omitted any relevant files or debug information. I would greatly appreciate any help you can send my way.

Miguel.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

maximized vnc viewer

I would like the vnc viewer to be maxized when it is launched. How to implement this. Thanks (0 Replies)
Discussion started by: cy163
0 Replies

2. UNIX Desktop Questions & Answers

2 questions about VNC viewer

I am using VNC Viewer 4.0 in my windows enviornment. The questions are: 1. how do you switch the applications in VNC enviornment? ALT-tab doesn't work since it just switchs among VNC viewer itself and other windows applications. 2. how to copy/paste the texts from VNC enviornemnt to... (1 Reply)
Discussion started by: princelinux
1 Replies

3. Linux

Copy Paste in VNC Viewer

hi, I am running a VNCserver on my Fedora VMWare virtual machine. I make a VNCViewer connection to that from my Windows XP box. Can I have copy, paste functionality from Fedora to Windows (2 Replies)
Discussion started by: rakeshgupta
2 Replies

4. Solaris

VNC viewer problem

hi all i cant connect to vnc viewer ... when i try it showing follwing error message write/select : connection aborted (10053) Do you wish to attempt to reconnect to 1##.2##.###.1# # help me any one solved before this problem (3 Replies)
Discussion started by: coolboys
3 Replies

5. Shell Programming and Scripting

Backup & restore Gnome Desktop and all settings in Gnome

Hi I'm looking for scripts to backup & restore Gnome Desktop and all settings in Gnome. (0 Replies)
Discussion started by: ccc
0 Replies

6. Ubuntu

Blank Screen after logoff server via vnc Viewer.

Hello All, I have installed VNC Server on Ubuntu system to access this system from windows machine i'm using VNC Viewer. When i logged off the server from windows machine through VNC Viewer its showing blank screen only... Kindly help. Regards, Purushottam Aher (0 Replies)
Discussion started by: purushottamaher
0 Replies
DBUS-SEND(1)							   User Commands						      DBUS-SEND(1)

NAME
dbus-send - Send a message to a message bus SYNOPSIS
dbus-send [--system | --session | --address=ADDRESS] [--dest=NAME] [--print-reply [=literal]] [--reply-timeout=MSEC] [--type=TYPE] OBJECT_PATH INTERFACE.MEMBER [CONTENTS...] DESCRIPTION
The dbus-send command is used to send a message to a D-Bus message bus. See http://www.freedesktop.org/software/dbus/ for more information about the big picture. There are two well-known message buses: the systemwide message bus (installed on many systems as the "messagebus" service) and the per-user-login-session message bus (started each time a user logs in). The --system and --session options direct dbus-send to send messages to the system or session buses respectively. If neither is specified, dbus-send sends to the session bus. Nearly all uses of dbus-send must provide the --dest argument which is the name of a connection on the bus to send the message to. If --dest is omitted, no destination is set. The object path and the name of the message to send must always be specified. Following arguments, if any, are the message contents (message arguments). These are given as type-specified values and may include containers (arrays, dicts, and variants) as described below. <contents> ::= <item> | <container> [ <item> | <container>...] <item> ::= <type>:<value> <container> ::= <array> | <dict> | <variant> <array> ::= array:<type>:<value>[,<value>...] <dict> ::= dict:<type>:<type>:<key>,<value>[,<key>,<value>...] <variant> ::= variant:<type>:<value> <type> ::= string | int16 | uint16 | int32 | uint32 | int64 | uint64 | double | byte | boolean | objpath D-Bus supports more types than these, but dbus-send currently does not. Also, dbus-send does not permit empty containers or nested containers (e.g. arrays of variants). Here is an example invocation: dbus-send --dest=org.freedesktop.ExampleName /org/freedesktop/sample/object/name org.freedesktop.ExampleInterface.ExampleMethod int32:47 string:'hello world' double:65.32 array:string:"1st item","next item","last item" dict:string:int32:"one",1,"two",2,"three",3 variant:int32:-8 objpath:/org/freedesktop/sample/object/name Note that the interface is separated from a method or signal name by a dot, though in the actual protocol the interface and the interface member are separate fields. OPTIONS
The following options are supported: --dest=NAME Specify the name of the connection to receive the message. --print-reply Block for a reply to the message sent, and print any reply received in a human-readable form. It also means the message type (--type=) is method_call. --print-reply=literal Block for a reply to the message sent, and print the body of the reply. If the reply is an object path or a string, it is printed literally, with no punctuation, escape characters etc. --reply-timeout=MSEC Wait for a reply for up to MSEC milliseconds. The default is implementation-defined, typically 25 seconds. --system Send to the system message bus. --session Send to the session message bus. (This is the default.) --address=ADDRESS Send to ADDRESS. --type=TYPE Specify method_call or signal (defaults to "signal"). AUTHOR
dbus-send was written by Philip Blundell. BUGS
Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/ D-Bus 1.12.2 DBUS-SEND(1)
All times are GMT -4. The time now is 03:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy