*** This bug is a duplicate of bug 227146 ***
https://bugs.launchpad.net/bugs/227146
SCIM doesn't work with XInputExtension failed, precisly the scim-panel-*
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notificat
*** This bug is a duplicate of bug 227146 ***
https://bugs.launchpad.net/bugs/227146
Confirm this bug on Intrepid AMD64.
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 227146 ***
https://bugs.launchpad.net/bugs/227146
** This bug has been marked a duplicate of bug 227146
vnc4server too slow with xinetd/gdm
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You receive
Disabling mouse- and keyboard-plugins seemed to solve the problem.
However, i upgraded to vnc 4.1.2 after reading this:
http://ubuntuforums.org/showthread.php?t=782665
And not only did this improve the overall vnc performance greatly -
gnome-settings-daemon finally seems to be happy now. Even wit
I confirm this bug on a fully updated Hardy AMD64.
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Running:
gconftool-2 --set --type boolean /apps/gnome-settings-
daemon/plugins/mouse/active false
Did *not* work for me.
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a member of Ubuntu
B
I went back to try the mouse disabling suggestion again. This time, I
fired up gconf-editor rather than run the suggested commandline. I
noticed I had both a gnome_settings_daemon and a gnome-settings-daemon.
The suggested command line above uses hyphens, but the entry with
underscores has the mo
On Fri, 2008-08-01 at 01:50 +, level323 wrote:
> And FYI - disabling the keyboard plugin via gconf-editor *does* appear
> to stop gnome-settings-daemon crashing. This is a workaround only,
> though.
Hi,
I realise it is a workaround, but if we can have some more
confirmations that this fixes
Sorry everyone - my suggestion to add "+extension XInputExtension" was
WRONG. It doesn't solve the issue at all. I was fooled into thinking it
did because subsequent connections 'seemed' to show the correct theme
indefinitely, but after a while gnome-settings-daemon failed again.
Sorry for causing
Adding "+extension XInputExtension" to the vnc server launch doesn't
work, either.
VNC version is:
# aptitude show vnc4server
Package: vnc4server
State: installed
Automatically installed: yes
Version: 4.1.1+xorg1.0.2-0ubuntu7
Priority: optional
Section: universe/x11
I use xinetd to manage the li
Hi,
Thanks for testing.
gconftool-2 --set --type boolean /apps/gnome-settings-
daemon/plugins/mouse/active true
will put your system back to the way it was before.
Thanks,
James
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You receive
gconftool-2 --set --type boolean /apps/gnome-settings-
daemon/plugins/mouse/active false
does not work.
sudo gconftool-2 --set --type boolean /apps/gnome-settings-
daemon/plugins/mouse/active false
does not work.
rebooted after both just to be sure (as I wasn't sure if the change was
immed
Hi,
As well as testing the above could someone try running vnc as before,
but disabling the mouse plugin?
gconftool-2 --set --type boolean /apps/gnome-settings-
daemon/plugins/mouse/active false
The mouse plugin attempts to protect against a missing XInput extension, but
that protection may be
I experienced the same problem as many have already mentioned - namely
gnome-settings-daemon fails when accessing the GNOME GUI via vnc4server.
After a little experimentation and research, I discovered what I think
is a solution (or at least an easy workaround).
What works for me is to add the ar
Same problem here, i have a fresh install of Ubuntu 8.04...i tried
creating a new user (with fresh gnome settings) but nothing changed :o/
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a me
Exact same problem, x86 and x86_64 machines: does anyone have a workaround for
this missing extension? Or is there an alternative VNC server that works
equally well?
-Tom
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bu
Exact same problem, x86 and x86_64 machines: does anyone have a workaround for
this missing extension? Or is there an alternative VNC server that works
equally well?
-Tom
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bu
David, FYI I upgraded from Gutsy (7.10) to Hardy, I run vnc4server via a
WAN (over ssh tunnel), and use inetd (not xinetd) to launch vnc
sessions. So that takes 3 of 4 commonalities out of the mix.
Sincerely,
Jordan
David McNeill wrote:
> I'm seeing similar errors:
>
> Common theme:
> * Upgr
This sheds a little more light on the situation, there is no
XInputExtension in the free version, and it shouldn't be being asked for
by the app...
http://www.realvnc.com/pipermail/vnc-list/2005-December/053489.html
Check with this
xdpyinfo | grep XInput
(nothing)
on the physical console
xdpyin
It seems XInputExtension is not complied into vnc4server 4.1.1 as discussed
here
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379617
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a
I'm seeing similar errors:
Common theme:
* Upgraded from Dapper 6.06 to Hardy 8.04
* VNC to problem box on local lan
* xinetd to launch vnc
* Xlib: extension "XInputExtension" missing on display ":1.0".
I'm running Kubuntu, and see this error on lots of apps, not just gnome-
settings-daemon.
Same problem here, after upgrading from 6.06 to 8.04.
The machine is a 2100+ rated AthlonXP with suited Board, 1GB Ram, no
other fancy hardware.
I would be very happy to see a solution here, because this bug renders
my setup unusable.
--
Error starting gnome-settings-daemon while logged in via
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I have a similar setup as described in the original post, but simpler one: VNC
over 1 Gb LAN, no SSH, vnc4server starts-up via xinetd.
The visible symptoms are exactly the same as Jordan put it, nothing to add
here, and it all started after 7.1 to 8.04 upgrade.
The problem affected both upgraded
Hey Marc & Jordan
I confirm. when running hardy clean installation and also disabling
sound support as not needed and XRandR as well, I get quite the same
output as you guys. Take a look below. I also did try to make the
workaround with touching the gnome-session. nothing helped me for now.
** (g
I've been having this as well since upgrading from Gutsy to Hardy. Same
basic problem and error messages, but error info is slightly different.
~$ gnome-settings-daemon
** (gnome-settings-daemon:32689): WARNING **: The X Server does not
support the XRandR extension. Runtime resolution changes to
I should also add that this happens with:
- A non-upgraded (Fresh Hardy) install
- A newly created user
- Manually changing theme to a non-default theme.
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification beca
** Attachment added: "Screenshot of gnome-settings-daemon error"
http://launchpadlibrarian.net/15223180/gnomesettingsdaemonerror.png
--
Error starting gnome-settings-daemon while logged in via vnc
https://bugs.launchpad.net/bugs/239342
You received this bug notification because you are a memb
28 matches
Mail list logo
