** Changed in: gnome-settings-daemon
Importance: Unknown = Critical
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Fix Released = New
** Changed in: gnome-settings-daemon
Status: Fix Released = New
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug
I have exaclty the same problem as mabawsa, with the themes not working
in a FreeNX session. Disabling the keyboard plugin fixes the problem.
This seems to be a regression that was introduced by an update that was
released 1-2 weeks ago. Can't say exactly because I only noticed it
after a restart.
Please don't reopen old bugs that are fixed. If you're having issues,
please open a new bug even if your symptoms are similar.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Fix Released
** Changed in: gnome-settings-daemon
Status: New = Fix Released
--
I have started a new bug report on this: Bug #409621
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
mabawsa how did you exactly disable the keyboard plugin ?
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just forgot what I said
Open gconf-editor and go to apps/gnome-settings-daemon/plugins/keyboard and
disable it ;)
This bug has recently happened with Freenx session (since the last kernel
update (2.6.28-14) actually) ...maybe you should open a new bug report ?
--
gnome-settings-daemon
This bug also happens when using a Freenx session (I will try it with VNC and
x11vnc later today). The only side effect is that theming and icons display
incorrectly. It has only recently started to happen so there may be a
regression somewhere.
After logging into freenx and Typing
Should I open a new bug for Jaunty or mark this one as new or do
nothing?
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
still happening with jaunty - a real pity, lost a couple of hours with
this old bug.
This is what I get when I launch gnome-settings-manager in a terminal
window inside the vnc (vnc4server) session.
incidentally the VNC resolution i get is also wrong (800x600 all the
time, ignoring the
The resolution not being configurable by the vnc client is expected I
think. Xvnc and I assume vnc4server don't support xrandr so you can't
change the resolution from what is configured on the server when the
display is created. So I think that one is a limitation rather than a
bug. You can make
I'm seeing the failures stop as of 4/02/2009.
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I should be more specific - the session I'm starting with x11vnc via gdm
(the KillInitClients = False trick documented elsewhere) keeps the
settings daemon alive. It seems to still die under TightVNC server when
started by xrdp.
--
gnome-settings-daemon crash opening any window: BadWindow X
the bug described there has been fixed according to the GNOME bug, if
you still have an issue on jaunty better to open a new bug
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = Fix Released
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
Me too!
Still fails on Jaunty (2009-03-15) with Terminal Server Client (Xnest
and Xephyr) unless the keyboard plugin is disabled.
-jh
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification
I updated to Jaunty and as of today's Jaunty (2/3/2009) I can replicate
this problem on i386.
The good news is that the workaround still works as well.
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug
fixed upstream, thanks for reporting.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = Fix Committed
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are
Is somebody still having this in jaunty? could someone comment on the
upstream report then? thanks.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Fix Committed = Incomplete
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
I can confirm this on a fresh install of intrepid x86 with all the
latest updates and vnc4server installed. It works fine under normal X
but under Xvnc, gnome-settings-daemon crashes every time it tries to
start. With nothing disabled, it segfaults when initializing the mouse
plugin. After
Aaron Roydhouse's suggestion to disable the keyboard plugin also stopped
my gnome-settings daemon from crashing. This is on an up-to-date hardy
system and vnc4server.
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You
** Attachment added: gsd-error.txt
http://launchpadlibrarian.net/19330161/gsd-error.txt
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Not fixed in intrepid, even though stated in comment 26. See the file
I'm attaching. With normal settings, Segmentation Fault is gotten just
by starting gnome-settings-daemon. With the mouse plugin disabled, the
BadWindow is gotten if any window/application is opened. With both mouse
and keyboard
Pedro: Is there any way to get this fix into ubuntu-updates (not ubuntu-
security) for Hardy 8.04 LTS? Although not a security issue, it is a
significant enduser annoyance issue (the number of duplicate bug reports
attests to that), and Hardy 8.04 is marked LTS indicating that it
should be okay to
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: gnome-settings-daemon
Status: Confirmed = Fix Released
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
this is fixed in Intrepid with the 2.24.0 version of the package.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triaged = Fix Released
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug
** Changed in: gnome-settings-daemon
Status: New = Confirmed
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have approximately the same crash here. It looks like the gsd-
keyboard-xkb filter gets a CreateWindow notification event, but the
window id isn't valid anymore (maybe the window already disappeared?),
for an unknown reason. When the xklavier engine tries to get the
Window's title property, it
latest trace is a duplicate of bug 254671.
** Bug watch added: GNOME Bug Tracker #537592
http://bugzilla.gnome.org/show_bug.cgi?id=537592
** Also affects: gnome-settings-daemon via
http://bugzilla.gnome.org/show_bug.cgi?id=537592
Importance: Unknown
Status: Unknown
** Changed
** Changed in: gnome-settings-daemon
Status: Unknown = New
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Okay, I've done some serious digging, and it looks like a window is
created (in my case it's mostly gnome-screensaver), but it disappears
*before* the CreateNotify goes out. This is because gnome-screensaver
complains that it's already running, and immediately quits. Thus it
doesn't seem to call
I've followed Roydhouse suggestions. The improvement is minimal
compared to the performance seen in Gutsy which I had running for a
year... and which was virtually undetectable on a 1Gb lan. With Hardy
upgrade (which I'm totally regretting) on the same network setup this
is one significant
Following Aaron Roydhouse and others' suggestion, I found that disabling
the mouse plugin fixed the error messages. keyboard plugin had no
effect. However, disabling the mouse plugin messed with my key bindings
in such a way that the system was unusable.
--
gnome-settings-daemon crash opening
I had the same problems but the descripton of Aaron Roydhouse fixed my
problems.. Thank you!
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I experienced the same problem with gnome-settings-daemon using Xvnc
(vnc4server 4.1.1+xorg1.0) with Ubuntu 8.04 desktop (all updates as at
15 June 2008). I found that disabling just the keyboard plug-in for
gnome-settings-daemon, and logging in again, gave immediate relief.
For the other dimwits
Moving to confirmed, the gnome-settings-daemon problem is definitely
there. Please no comments about performance related problems, file a new
bug or find an existing bug about it.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = Confirmed
--
gnome-settings-daemon crash
Ok. On current hardy, the problem seems to be even more about the gnome-
settings-daemon's mouse plugin than keyboard plugin. Unsetting apps -
gnome_settings_daemon - plugins - mouse - active gives me themed VNC
session already, but it gnome-settings-daemon crashes often when doing
anything with
[quote]By the way, where I mean VNC performance is Xvnc, not x11vnc.
They are 2 different programs. The performance of Xvnc is fine in Feisty
or Gutsy, but not in Hardy. The performance of x11vnc won't be as good
as Xvnc in theory, since it's started for the existing DISPLAY and need
to track the
I have similar problems with vnc speed and the gnome-settings Daemon
crashing. To stop the message I not only had to disable the keyboard
plug in but the mouse plug in as well. The speed is still sluggish
compared to Gutsy though.
--
gnome-settings-daemon crash opening any window: BadWindow X
The Slow VNC thing everyone is noticing is actually NOT directly
related to VNC. So trying new VNC servers/clients will not help,
unfortunately.
I suspect that this slowness in my VNC sessions (and probably yours too)
is coming from something in the Gnome session... Very likely gnome-
Interesting findings.
To confirm the performance issue is caused by gnome-settings-daemon, I
just run following test:
1. Ctrl + Alt + F1, login
2. X :1 -query localhost
Then a similar window appears like open a VNC session. In this X
session, the performance is good.
So I guess it's a Xvnc -
I confirm that I'm seeing the exact same issues (Xtightvnc causing
gnome-settings-daemon to keep crashing with BadWindow on new windows
being mapped, and being restarted) with the same fix (disabling the
keyboard plugin for gnome-settings-daemon), in addition to the other
issue with TightVNC
Oh yes, and as more than one person has noted, VNC performance is
incredibly poor on hardy. In fact, in my case, it's so poor that gnome-
settings-daemon takes long enough to start up that the first thing to
appear is a grey blank window that later (in a minute or so) paints to
reveal an error
Same slow performance here with x11vnc server. I can't comment on performance
before hardy as I ran vino, but x11vnc is very slow. I also applied the fix
but this did nothing to help with performance.
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
Same problem here; same fix; same poor VNC performance. Mine is started
by inetd, not xinetd.
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have the same problem, using Hardy Beta 5, updated to April 1st. Disabling
the keyboard plugin on Gnome Settings Daemon fixes the crashes.
Is there any open bug about Xvnc performance?
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
I have the same problem here. And I've been using Xvnc with xinet.d in
this way under Feitsy and Gutsy, the speed is acceptable. But with Hardy
b4, just try to vnc to localhost:1 will like viewing the desktop
remotely through WAN. So I believe there should be something wrong here.
Hope the
I can also report this problem and the same solution --disabling the
keyboard plugin to gnome-settings-daemon made everything work smoothly.
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug notification
Not sure what else I can do to help, or what else is needed to move bug from
incomplete status. Hoping this is a good start.
FWIW Xvnc under Hardy is abysmally slow and klunky compared to Gutsy. I
have no idea why the performance is so awful here. I can see the individual
GTK widgets being
According to the output log, it's not failing during the xrandr plugin,
but rather during the keyboard plugin, and in particular in some of the
xklavier function calls:
#3 0xb792dab6 in XGetWindowProperty () from /usr/lib/libX11.so.6
No symbol table info available.
#4 0xb63feda4 in
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided = Low
Assignee:
gdb backtrace attached.
** Attachment added: gdb-gnome-settings-daemon.txt
http://launchpadlibrarian.net/12520587/gdb-gnome-settings-daemon.txt
--
gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
https://bugs.launchpad.net/bugs/199245
You received this bug
52 matches
Mail list logo
