This bug was fixed in the package xorg-server - 2:1.11.3-0ubuntu8
---
xorg-server (2:1.11.3-0ubuntu8) precise; urgency=low
* debian/patches/224_return_BadWindow_not_BadMatch.diff:
- Fix the error values of a whole slew of window-related calls.
Fixes some
** Changed in: xorg-server (Ubuntu Precise)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903973
Title:
gnome-settings-daemon crashed with signal 5 in
closing the g-s-d part it seems an xorg issue and the fix is pending
commit
** Changed in: gnome-settings-daemon (Ubuntu Precise)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug 907052 may be a duplicate of this one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903973
Title:
gnome-settings-daemon crashed with signal 5 in _XReply()
To manage notifications about this
Bug 907052 looks like it's a different issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903973
Title:
gnome-settings-daemon crashed with signal 5 in _XReply()
To manage notifications about this
I have not had gnome session daemon crash for a long time. In the past
it was due to obsolete packages and so was not reportable, but easily
fixed. This time I ran Update Manager to get the daily updates. This
completed without any problems but as it included a kernel update, I
rebooted and as
Discussion on http://lists.x.org/archives/xorg-
devel/2012-January/028361.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903973
Title:
gnome-settings-daemon crashed with signal 5 in _XReply()
The crash is because XGetWindowAttributes is throwing a BadMatch error,
which is unexpected. It will throw a BadMatch error (from
dixLookupWindow) if the specified window isn't really a window. This
might happen if a window is destroyed and replaced with a drawable of
the same ID whilst
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu Precise)
Importance: Undecided = High
** Changed in: xorg-server (Ubuntu Precise)
Status: New = Confirmed
** Changed in: xorg-server (Ubuntu Precise)
Assignee:
** Changed in: xorg-server (Ubuntu Precise)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903973
Title:
gnome-settings-daemon crashed with signal 5 in
Urgh. It looks like the patch you originally submitted upstream is more
correct than the patch that got committed - all manner of window calls
are broken, not just XGetWindowAttributes.
Let's see if the xorg-devel mailing list agrees.
--
You received this bug notification because you are a
Chris, you debugged similar issues before, do you remember what was
useful in such cases? Do we need a sync version of the stacktrace or the
.xsession-errors after the issue?
** Visibility changed to: Public
** Also affects: gnome-settings-daemon (Ubuntu Precise)
Importance: High
(note that --sync got replaced by GDK_SYNCHRONIZE=1 use nowadays, if a
sync stacktrace is required)
it seems that the issue started some weeks ago but g-s-d didn't change a
lot, could be something else in the stack...
--
You received this bug notification because you are a member of Ubuntu
13 matches
Mail list logo
