After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 693623 - gdkwindow: guard for NULL source_device in send_crossing_event()
gdkwindow: guard for NULL source_device in send_crossing_event()
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: X11
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-02-11 22:23 UTC by Carl-Anton Ingmarsson
Modified: 2018-04-15 00:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdkwindow: guard for NULL source_device in send_crossing_event() (930 bytes, patch)
2013-02-11 22:23 UTC, Carl-Anton Ingmarsson 		none Details | Review

Description Carl-Anton Ingmarsson 2013-02-11 22:23:18 UTC 
source_device may be NULL, so we have to check that before we
use it. Although I can't say that I'm fluent in the code it
seems to be expected that source_device can be NULL since
an explicit check is done for this later in the function at
gdkwindow.c:8496
Comment 1 Carl-Anton Ingmarsson 2013-02-11 22:23:21 UTC 
Created attachment 235751 [details] [review]
gdkwindow: guard for NULL source_device in send_crossing_event()
Comment 2 Carlos Garnacho 2013-02-18 20:16:06 UTC 
I've got a feeling this is related to (or the same than) bug #692448 , were you getting the same warning?
Comment 3 Carl-Anton Ingmarsson 2013-02-18 21:13:35 UTC 
(In reply to comment #2)
> I've got a feeling this is related to (or the same than) bug #692448 , were you
> getting the same warning?

Yes I got the same warning.
Comment 4 Matthias Clasen 2018-02-10 04:56:43 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 5 Matthias Clasen 2018-04-15 00:02:08 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new