Thanks for testing, I can see why it's not working.
Would you mind reporting the xrandr issue separately please, and obtain
the backtrace with libxrandr2-dbg installed please?
Thanks
** Changed in: libxklavier (Ubuntu Karmic)
Status: Fix Released => Triaged
** Changed in: libxklavier (Ub
btw the last two files have xrand disabled.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
** Attachment added: "g-s-d-XKL_DEBUG.log"
http://launchpadlibrarian.net/33814762/g-s-d-XKL_DEBUG.log
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notificatio
** Attachment added: "XInputExtension.txt"
http://launchpadlibrarian.net/33814748/XInputExtension.txt
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notificatio
** Attachment added: "gdb-gsd-xrand-disabled-2.txt"
http://launchpadlibrarian.net/33814738/gdb-gsd-xrand-disabled-2.txt
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received th
OK I made similar logs to last time (with and without xrand enabled)
** Attachment added: "gdb-gsd-xrand-enabled.txt"
http://launchpadlibrarian.net/33814714/gdb-gsd-xrand-enabled.txt
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a
btw this is the output I get from gsd with the "fixed" libxklavier
(4.0-0ubuntu4) and keyboard plugin enabled:
~$ gnome-settings-daemon
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extensio
I just upgraded to Karmic. There is a new xrand bug that stops gsd
loading and that plugin needs to be disabled; I should report a new bug
maybe. Anyway the keyboard plugin patch appeared to work as when I
enabled the plugin gsd started. However on subsequent restarts gsd
crashes (even with xrand d
This bug was fixed in the package libxklavier - 4.0-0ubuntu4
---
libxklavier (4.0-0ubuntu4) karmic; urgency=low
* debian/patches/92_handle_xi_errors.patch:
- Upstream CVS change to trap XI errors resulting from missing
features in FreeNX, and not crash gnome-settings-daemo
** Changed in: libxklavier (Ubuntu Karmic)
Status: Triaged => Fix Committed
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a mem
Here's a patch for Karmic
** Attachment added: "libxklavier_4.0-0ubuntu4.debdiff"
http://launchpadlibrarian.net/33698123/libxklavier_4.0-0ubuntu4.debdiff
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchp
And here's the actual error on Karmic (the Xinput issue, not the xrandr
one):
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'XI_BadClass (invalid Class parameter)'.
(Details: serial 149 error_code 133 request_cod
I guess some are going to hate me for all that noise, sorry for that.
Working again on a clean system, there are actually two issues on Karmic.
First: Our usual libxklavier bug when built with Xinput support (that I didn't
see at first as I was running a patched version)
Second: g-s-d crashing wh
Marked the task as invalid as my conclusion was wrong.
The result although being extremely similar comes because of the xrandr plugin
this time and not the keyboard plugin as it used to be in jaunty.
I'll file another bug against gnome-settings-daemon for that issue
(xrandr plugin not starting in
Here's the error output when starting g-s-d on karmic:
stgra...@orilla:~$ gnome-settings-daemon
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on display ":1000.0".
Xlib: extension "Generic Event Extension" missing on di
I have been successful at reproducing the issue with Karmic.
** Also affects: libxklavier (Ubuntu Karmic)
Importance: Low
Assignee: Ubuntu Desktop Bugs (desktop-bugs)
Status: Triaged
** Changed in: libxklavier (Ubuntu Karmic)
Importance: Low => High
--
The program 'gnome-setti
** Changed in: libxklavier (Ubuntu Jaunty)
Importance: Undecided => High
** Changed in: libxklavier (Ubuntu Jaunty)
Status: New => Triaged
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/b
** Also affects: libxklavier (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are
Good spot there - thanks! The extra build-dep on libxi-dev enables the
code which trigger this.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because
Adding the regression-update tag as the bug appeared with 3.9-0ubuntu2 in
jaunty-updates.
Downgrading that single package to 3.9-0ubuntu1 solves the issue without
needing any kind of gconf configuration.
That command will revert to a working libxklavier12:
apt-get install --reinstall libxklavier
Getting bit by this as well.
Have up to date karmic on a fresh new 16 core with no user data on it yet.
Let me know how I can help test.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
Jens has pointed out in the upstream bug report that the presence of XIE
does not necessarily mean that DevicePresence is supported. So, this can
be fixed in libxklavier after all
** Package changed: gnome-settings-daemon (Ubuntu) => libxklavier
(Ubuntu)
** Changed in: libxklavier (Ubuntu)
Spooky - thanks for the info. I will take a look at that when I get the
chance
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member
As pointed out a few comments ago, the actual code in libxklavier where
this error occurs is this:
#ifdef HAVE_XINPUT
if (xkl_engine_priv(engine, features) | XKLF_DEVICE_DISCOVERY) {
DevicePresence(display, xitype, xiclass);
XSelectExtensionEvent(display,
xkl_engine_priv(engine, roo
This guide covers it pretty well:
https://help.ubuntu.com/community/FreeNX
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of U
Thanks for the info.
That's interesting anyway - it seems you do have XIE there. We've
identified and fixed one bug in libxklavier now that could cause a crash
when XIE is missing, but that isn't going to fix your issue though. I'm
completely stuck now - I think my next step is to run FreeNX here
Sorry for the double posting.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
$ xdpyinfo -ext XInputExtension
name of display::1000.0
version number:11.0
vendor string:The X.Org Foundation
vendor release number:6090
X.Org version: 6.9.0
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding:32, LSBFirst, 32
imag
$ xdpyinfo -ext XInputExtension
name of display::1000.0
version number:11.0
vendor string:The X.Org Foundation
vendor release number:6090
X.Org version: 6.9.0
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding:32, LSBFirst, 32
imag
Hi,
Could you please post the output of "xdpyinfo -ext XInputExtension"?
Could you also please run "XKL_DEBUG=200 gnome-settings-daemon --sync
--debug --no-daemon 2>&1 | tee g-s-d.log" up until the point that it
crashes?
Thanks
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Triage
Thanks. The Xorg.0.log actually isn't that much use as you're using
FreeNX, so it doesn't have the information I was looking for (my fault).
Anyway, I did some reading online, and FreeNX doesn't support
XInputExtension AFAICT, which is what triggers your issue here.
** Changed in: gnome-settings-d
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/30290757/Xorg.0.log
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are
Thanks for your time Chris and Sebastien. Here is the new gdb file and my Xorg
log.
Unfortunately I don't have Karmic installed on the nx servers I have and as
they are calculation servers used by 5-6 users I don't want to install a
development version. I do have a spare machine which I will try
Could you also please attach your /var/log/Xorg.0.log? I want to see if
you have XInputExtension. It seems that the mouse plugin had a similar
issue and was fixed by this change:
http://bugzilla.gnome.org/attachment.cgi?id=123812&action=view
There is similar code in xklavier used by the keyboard
Thank you. That trace there seems to be the right one now, showing the
error that triggers the crash. (XSelectExtensionEvent causes the
BadClass error, which seems plausible according to the libxi
documentation). There are still a few missing symbols though which could
make it more useful. Would yo
OK
** Attachment added: "gdb-gnome-settings-daemon.txt"
http://launchpadlibrarian.net/30287021/gdb-gnome-settings-daemon.txt
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You receiv
I'm not sure that trace is showing the real error there, as the error
shown in your trace should be trapped correctly and not cause g s-d to
exit (and your debug output suggests this is the case as well). Would
you mind trying again, but after encountering the first gdk_x_error in
GDB, could you pl
** Changed in: gnome-settings-daemon
Status: Unknown => New
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
De
The crash seems similar to
http://bugzilla.gnome.org/show_bug.cgi?id=583709
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete => New
** Bug watch added: GNOME Bug Tracker #583709
http://bugzilla.gnome.org/show_bug.cgi?id=583709
** Changed in: gnome-settings-daemon (Ubunt
OK
** Attachment added: "gdb-gnome-settings-daemon.txt"
http://launchpadlibrarian.net/30270546/gdb-gnome-settings-daemon.txt
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You receiv
could you get one with libgnome-desktop2-dbgsym and libx11-6-dbgsym
installed?
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member
OK the -no-daemon did the trick. Is this enough or should I install the
other symbols?
** Attachment added: "gdb-gnome-settings-daemon.txt"
http://launchpadlibrarian.net/30269287/gdb-gnome-settings-daemon.txt
--
The program 'gnome-settings-daemon' received an X Window System error. During
o
I have the same problem.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-s
you can install libgtk2.0-0-dbg and do
- gdb gnome-settings-daemon
(gdb) break gdk_x_error
(gdb) run --sync --no-daemon
get the crash
(gdb) bt full
it should stop on the error
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
h
Any ideas on how I can get the stack trace??
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
the issue there is clearly a bug in gnome-settings-daemon when some
xserver feature are not available, having a gdb stacktrace would be
useful though
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/b
We should nominate this bug as "The Infamous Highlander Bug".
Just kidding :)
Affecting me too since last year. I'm using the original NoMachine NX Server
and Client.
Disabling the keyboard plugin works perfectly.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.04
DISTRIB_CODENAME=jaunty
DISTRIB_DESCRIPTION=
Would be interesting to try on karmic
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
To do this u can use gconf-editor:
$ gconf-editor
Then navigate to the appropriate key (see attached image)
** Attachment added: "Screenshot-Configuration Editor - keyboard.png"
http://launchpadlibrarian.net/30097891/Screenshot-Configuration%20Editor%20-%20keyboard.png
--
The program 'gno
In the original problem description, mabawsa wrote:
"Disabling the keyboard plugin stops the error and the themes load correctly."
Keyboard plugin to what? How does one disable this?
I agree that the warnings about Generic Event Extension missing are
probably not related. Sorry about that mislea
I see those errors all the time when starting applications in an NX
session. For instance, starting gedit from the terminal gives errors
like that. I don't think it's related to this bug, because it's been
happening as long as I can remember.
--
The program 'gnome-settings-daemon' received an X
Hello. I notice that, before gnome-settings-daemon fails as described, it says:
Xlib: extension "Generic Event Extension" missing on display ":1003.0".
Xlib: extension "Generic Event Extension" missing on display ":1003.0".
Xlib: extension "Generic Event Extension" missing on display ":1003.0".
weird, the ""gdk_x_error" not defined." usually indicates that gdk debug
symbols are not there
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because y
Thanks for the tip. I installed libgtk2.0-0-dbg and it reduced the '(no
debugging symbols found)' messages, but it still isn't reporting any
backtrace.
** Attachment added: "gdb-gnome-settings-daemon.txt"
http://launchpadlibrarian.net/29984863/gdb-gnome-settings-daemon.txt
--
The program 'gno
it seems you didn't install libgtk2.0-0-dbg
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
https://bugs.launchpad.net/bugs/409621
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
** Attachment added: "The correct debugging symbols are installed but appear
not to be recognised."
http://launchpadlibrarian.net/29962564/Screenshot-Synaptic%20Package%20Manager%20.png
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suri
OK I tried to follow the instructions and got the following attachment.
However even though the debugging symbols are installed (see the attached
synaptic image) gdb throws up a lot of (no debugging symbols found) so I am not
too sure what where I am going wrong.
** Attachment added: "gdb-gnome
Thank you for your bug report. Please try to obtain a backtrace as
described in your error above and following the instructions at
https://wiki.ubuntu.com/DebuggingProgramCrash (run "gnome-settings-
daemon --sync" in GDB, and then set a breakpoint on gdk_x_error, and
obtain the backtrace when this
** Summary changed:
- The program 'gnome-settings-daemon' received an X Window System error.
+ The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server suring a session.
--
The program 'gnome-settings-daemon' received an X Window System error. During
on
59 matches
Mail list logo
