[Touch-packages] [Bug 401823]

2018-12-14 Thread Gitlab-migration
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/i

[Touch-packages] [Bug 401823]

2018-12-14 Thread Jeremy Huddleston
This seems more like a server issue. I think it could easily be possible for the server to guarantee that XIDs are not reused within a certain time period since it issued a DestroyNotify. That won't guarantee that clients are happy, but it can certainly help. We just need to store a timestamp

[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead

2018-12-14 Thread Bug Watch Updater
** Changed in: xlibs Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead Status

[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead

2014-11-05 Thread dino99
** Changed in: chromium-browser Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead St

[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead

2014-11-05 Thread Jeff Lane
Can someone please close this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead Status in Chromium Browser:

[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead

2014-07-30 Thread Bryan Quigley
Cleaning up where this can no longer be fixed/has been fixed. Does anyone still have this issue? ** Changed in: gtk+2.0 (Ubuntu Lucid) Status: Confirmed => Invalid ** Changed in: firefox (Ubuntu Lucid) Status: Confirmed => Invalid ** Changed in: firefox (Ubuntu) Status: Con