Description of problem: I can connect with VNC but when it starts startkde or gnome-session I get the above error. Version-Release number of selected component (if applicable):i686 and x64_86 How reproducible: Every time I try to connect with a vncviewer. Steps to Reproduce: 1.Vncserver is running of course from /etc/init.d. 2.Connect to the box with a viewer and see the message. 3. Actual results:No desktop is seen KDE or Gnome. Expected results: To see the KDE or Gnome desktop. Additional info: I can run both KDE and Gnome from the console, but not from within VNC. Messages says to check installation, which is fine but which installation, D-Bus, VNC(have uninstalled and reinstalled same result), KDE, X11, or xyz?
Created attachment 308539 [details] Error starting gnome in a vncviewer...
I disabled selinux "echo 0>/selinux/enforce" which allowed the desktop to appear but created additional errors. First one below and then see the attachment. There was an error starting the GNOME Settings Daemon. Some things, such as themes, sounds, or background settings may not work correctly. The last error message was: An SELinux policy prevents this sender from sending this message to this recipient (rejected message had interface "org.freedesktop.DBus" member "Hello" error name "(unset)" destination "org.freedesktop.DBus") GNOME will still try to restart the Settings Daemon next time you log in.
Not sure if I need to create new bug report for kdebase-workspace (startkde is from this package), but I have a similar problem with rawhide, but I'm not using VNC. It's happening from 4-5 days now (maybe after Sunday/Monday updates), and I can't start kde 4 because of this error. Not using SELinux. D-Bus appear to be running: dbus 2238 0.0 0.1 2740 960 ? Ss 09:38 0:00 dbus-daemon --system b 3182 0.0 0.0 2744 864 ? Ss 09:39 0:00 /bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session b 3183 0.0 0.0 3148 636 pts/0 S 09:39 0:00 dbus-launch --autolaunch 09812309129203814920912029123812 --binary-syntax --close-stderr Default runlevel is 3, so I'm starting kde with startx. Must be some new change from last 5 days in another package, becasue kdebase-workspace is from Jun 4-th.
Found the answer in the mailing list. I had the broken qt with /usr/lib/qt4/bin as symlink, but then I removed temporary files from rpm installation and everything seemed ok. Didn't know that this directory must not be symlink. Removed qt and reinstalled it again. Now kde starts without error.
Could you please verify that this bug is still reproducable with selinux-policy-3.3.1-72.fc9 or newer? It seems like dupe of bug #447631. Thanks
This appears to have been corrected with the current kernel 2.6.25.9-76.fc9.x86_64 installed yesterday. Works both with Gnome and KDE.
*** This bug has been marked as a duplicate of 447631 ***