So, this is not an X bug. XGrabServer prevents requests from any other
X connection from being processed.
It's probably not a Gdk bug either, as it looks like it needs to do
something that can't reasonably be pushed into the server with a stable
state.
--
You received this bug notification beca
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/400374
Title:
X server freezes while the application is executing XQueryPointer
** Changed in: xorg-server (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4003
Oh interesting. _gdk_windowing_window_at_pointer calls XQueryPointer
multiple times, and has the following explanation for the grab:
/* This function really only works if the mouse pointer is held still
* during its operation. If it moves from one leaf window to another
* than we'll end up
gdk_display_get_window_at_pointer() (or more specifically
_gdk_windowing_window_at_pointer) grabs with XGrabServer() before calling
XQueryPointer.
The grab can be broken by switching to a virtual terminal and killing
the app using gdk_display_get_window_at_pointer (or attaching to that
process wit
I just ran into the same problem without using gdb at all:
Start Firefox. Run "ksysguard". Select the firefox process, right-click,
and choose "Monitor Input&Output". go back to using Firefox, wait for
about a minute, and the desktop will become frozen.
This time, I have no idea who holds the loc
Is that even possible? I'd have to tell gdb to exit from the
XQueryPointer function in the main thread any time it stops the program
- whether I just attached it, or hit Ctrl-C, or the program hit a
breakpoint in some other thread. I've no idea how to do that.
I've debugged the same program in Win
I'm not sure if that's really a problem. Can't you teach gdb to skip
that?
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
--
X server freezes while the application is executing XQueryPointer
htt
Hi dima-gmail,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
(and maybe Xorg.0.log.old) file from after reproducing this issue. If you've
made any customizations to your /etc/X11/xorg.conf please attach that as well.
[This is an automated message. Apologies i
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
X server freezes while the application is executing XQueryPointer
https://bugs.launchpad.net/bugs/400374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Package changed: ubuntu => xorg (Ubuntu)
--
X server freezes while the application is executing XQueryPointer
https://bugs.launchpad.net/bugs/400374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I wonder if this could be the problem, on line 48 of QuPntr.c in libx11-6
LockDisplay(dpy);
It's way too easy to run into this problem when debugging a multi-
threaded application: it can stop in the middle of XQueryPointer when
another thread hits a completely unrelated breakpoint.
--
X ser
12 matches
Mail list logo
