Gdk-WARNING **: XID collision, trouble ahead

karmic testing

in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble ahead
previously, have had this one: (nautilus:3572):
 GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (bug report 401822)

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: firefox 3.0.11+build2+nobinonly-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Have added my xsession-errors file. The good bit is as follows:

(firefox:3621): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

(nautilus:3180): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

targetting for release milestone; in case this causes trouble we want a fix; if it doesnt cause crashes or alike we should drop the warning for the stable ubuntu release as it seems to flood xsession-errors et al.

using 9.10 as milestone as we probably dont want to hide this too early.

not sure if there is anything that can be done on firefox. anyway, triaged as it has an upstream bug.

This is what was being logged just before a reproducible (on this boot anyway) firefox-3.5 seg fault when I launched firefox on the CLI after a prior crash. aaport didn't pick up on the crash though.

Crash was when I was in google voice, trying to click the button to edit cell phone settings... It did work previously (several days back) - no idea what changed.

[08-08 02:40:16] Torbutton NOTE: Crash detected, attempting recovery
[08-08 02:40:16] Torbutton NOTE: Restoring cookie status
[08-08 02:40:16] Torbutton NOTE: Loading non-tor jar after crash
[08-08 02:40:16] Torbutton NOTE: Restoring tor state

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead

(firefox-3.5:14875): Gdk-WARNING **: XID collision, trouble ahead
Segmentation fault (core dumped)

Looks like the crash has been fixed in updates today. libgtk2.0-0 libgtk2.0-0-dbg libgtk2.0-bin libgtk2.0-common libgtk2.0-dev all updated.

- update and no more crash where it was very reproducible.

apt-cache policy libgtk2.0-0 libgtk2.0-0-dbg libgtk2.0-bin libgtk2.0-common libgtk2.0-dev
libgtk2.0-0:
  Installed: 2.17.7-0ubuntu2
  Candidate: 2.17.7-0ubuntu2
  Version table:
 *** 2.17.7-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
libgtk2.0-0-dbg:
  Installed: 2.17.7-0ubuntu2
  Candidate: 2.17.7-0ubuntu2
  Version table:
 *** 2.17.7-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
libgtk2.0-bin:
  Installed: 2.17.7-0ubuntu2
  Candidate: 2.17.7-0ubuntu2
  Version table:
 *** 2.17.7-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
libgtk2.0-common:
  Installed: 2.17.7-0ubuntu2
  Candidate: 2.17.7-0ubuntu2
  Version table:
 *** 2.17.7-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status
libgtk2.0-dev:
  Installed: 2.17.7-0ubuntu2
  Candidate: 2.17.7-0ubuntu2
  Version table:
 *** 2.17.7-0ubuntu2 0
        500 http://archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

(note - still get the warning messages, it just doesn't appear to crash anymore...)

firefox:16818): Gdk-WARNING **: XID collision, trouble ahead

(firefox:16818): Gdk-WARNING **: XID collision, trouble ahead

(firefox:16818): Gdk-WARNING **: XID collision, trouble ahead

Hi, it's the same bug?
The libcanberra error is related to https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/369498

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

$ firefox
Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: classe ELF errata: ELFCLASS64
NPP_New called
DBUS connection created
Listening to path /control/16915
ARG: src = http://static.ak.fbcdn.net/sound/pop.mp3
ARG: autostart = true
ARG: loop = false
ARG: hidden = true
New Stream Requested
opening /home/tyrael/.cache/gnome-mplayer/plugin/gecko-mediaplayertaudde.mp3 for localcache
Entering destroy stream reason = 0 for http://static.ak.fbcdn.net/sound/pop.mp3
Entering list_parse_qt localsize = 625
unable to find rmda in /home/tyrael/.cache/gnome-mplayer/plugin/gecko-mediaplayertaudde.mp3
Entering list_parse_asx localsize = 625
Item
src = http://static.ak.fbcdn.net/sound/pop.mp3
local = /home/tyrael/.cache/gnome-mplayer/plugin/gecko-mediaplayertaudde.mp3
id = 1
play = 1
path =
controlid = 0
playerready = 0
newwindow = 0
cancelled = 0
streaming = 0
loop = 0
loopcount = 0
Exiting list_parse_asx
Entering list_parse_qml localsize = 625
Item
src = http://static.ak.fbcdn.net/sound/pop.mp3
local = /home/tyrael/.cache/gnome-mplayer/plugin/gecko-mediaplayertaudde.mp3
id = 1
play = 1
path =
controlid = 0
playerready = 0
newwindow = 0
cancelled = 0
streaming = 0
loop = 0
loopcount = 0
Exiting list_parse_qml
URL Notify http://static.ak.fbcdn.net/sound/pop.mp3
,0 = 0
http://static.ak.fbcdn.net/sound/pop.mp3
/home/tyrael/.cache/gnome-mplayer/plugin/gecko-mediaplayertaudde.mp3
/control/16915
New Stream Requested
item is null
stream url http://static.ak.fbcdn.net/sound/pop.mp3
Entering destroy stream reason = 1 for http://static.ak.fbcdn.net/sound/pop.mp3
Exiting destroy stream reason = 1 for http://static.ak.fbcdn.net/sound/pop.mp3

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed

(firefox:3864): Gdk-CRITICAL **: gdk_x11_xatom_to_atom_for_display: assertion `xatom != None' failed
*** NSPlugin Viewer *** ERROR: NPN_InvalidateRect() invoke: Connessione interrotta dal corrispondente
Segmentation fault (core dumped)

I have a Zotac ION motherboard with ATOM N330 and Karmic AMD64

$ lspci
00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b2)
00:03.1 RAM memory: nVidia Corpor...

xid collision is gone now

Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: firefox 3.5.2+nobinonly-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
Uname: Linux 2.6.31-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Alex, can you please watch this, or unblock for karmic if it's not such a big deal? Thanks!

I'm also getting the error in #10 except the number this time is 15780 which is simply the PID of the process.

i invalidated the karmic task. not sure why no untargetted task came back for firefox.

hi all,

I am able to give you more comments about how that happen:

On an uptodated system, . xsession-errors don't show xid collision errors after boot process.
If i use Firefox, no warnings

but if i run both Firefox & audacious, errors start:

** (audacious2:22303): WARNING **: event-device-plugin: unable to load config file evdev-plug.conf , default settings will be used.

** (audacious2:22303): WARNING **: Could not open file:///home/oem/.adplug/adplug.db for reading or writing: Erreur à l'ouverture du fichier : Aucun fichier ou dossier de ce type
Warning: Unsafe event_queue of "hide seekbar" with pointer. (Use event_queue_with_data_free instead.)

(firefox:16694): Gdk-WARNING **: XID collision, trouble ahead

So, i'm thinking about a flashplugin problem.

I also do not see the XID collisions anymore
but I do not have flash or flashplugin issues
as when I am viewing flash or retieving flash I do not see this
I do see that I can not stream more than five videos simultaneously
but thats kind of pushing the limit anyway
I believe that this has something to do with how gdm is pulling the files from xorg
because the errors occur in gnome and not x and irrelevant to the fact of having a browser open or not
just as in bug 449993
But I am not the expert
I am just a noob

hi,

please, ignore my previous post #18, xid collision still happen without audacious: only firefox and nothing else in the background.
Just before i've seen these .xsession-errors, i've heard a hdd system activity : maybe system was checking for updates ?

I also get the following message:

(firefox:1938): Gdk-WARNING **: XID collision, trouble ahead

(firefox:1938): Gdk-WARNING **: XID collision, trouble ahead

(firefox:1938): Gdk-WARNING **: XID collision, trouble ahead

2.4+ kernel w/o ELF notes? -- report this

What's the meaning of the last line?

Sorry, I forgot: This is the output when running firefox from terminal. The last line "2.4+ kernel w/o ELF notes? -- report this" appears after waiting for a while not using firefox. When using firefox interface again after this, the XID collision lines appear again fluently.

On Mon, Oct 19, 2009 at 01:14:40PM -0000, Christian Niemeyer wrote:
> Sorry, I forgot: This is the output when running firefox from terminal.
> The last line "2.4+ kernel w/o ELF notes? -- report this" appears after

whatever that is ... its _not_ this bug. Please open new ones ...

 - Alexander

So:

gnome-bugs #581526 is the upstream GTK crash bug (which seems fixed for people here now?)
mozilla-bugs #497561 is the "XID collision" flood of messages upstream with the Firefox guys, but no-one owns the bug yet
xlibs #21573 is a crash which is related to the same XID problem, but isn't necessarily the exact same bug

...and this bug is tracking the non-fatal problem with "XID collision" messages?

just before the "xid collision" warnings appear, i've had this one:

(nautilus:2683): CRITICAL **: dbus_g_proxy_begin_call: assertion `DBUS_IS_G_PROXY (proxy)' failed

then, xid collision full filled .xsessions-errors (log greater than 100mb today, usually had less than 40kb)

Digging this problem, i've found on some forums that: XID collisions, can be Totally Ignored!

If so, what's the way to not full filled log with that stuff ? ( some kind of >> null)

(firefox:2783): Gdk-WARNING **: XID collision, trouble ahead

(firefox:2783): Gdk-WARNING **: XID collision, trouble ahead

I just keep seeing these errors on the terminal - is this going to be fixed before karmic final release? I am karmic rc now.

The critical thing about this bug is, that it floods .xsession-errors from usually a few kb to megabytes.

Imho, this causes annoying useless disk activity/capacity and probably a slightly slowdown/overhead.

This should be fixed.

I am switching to opera till this is fixed - I see a lot of these collision messages and resulting slowdown when playing videos in facebook and youtube. Firefox hasn't crashed thus far though!

newer firefox release 3.5.5 does not help: the problem is outside firefox.

i see this problem in chromium as well as occasionally in opera - mostly when watching videos

ok, we should remove the warning in a gtk SRU after release. setting milestone accordingly.

I'm seeing this message in Karmic RC also. It follows by segmentation fault and crashed Firefox. It happened in higher frequency ever since I upgraded to RC. I've never experience it before the upgrade.

@Homeless4ever

This will be fixed in the GTK packages in karmic-updates. Please don't change a Won't Fix Status without consulting the developers.

I'm sorry. I clicked on it by accident.

ok now this warning is no longer logged

On Thu, Oct 29, 2009 at 08:24:26AM -0000, dino99 wrote:
> ok now this warning is no longer logged

we didnt change anything, so I assume that you are just lucky and do
not hit this issue temporarily for now ... most likely it will happen
again for you at some point.

Plan is to remove that warning output from gtk+ in a SRU still ...

 - Alexander

Using Koala RC with latest updates, still receiving (firefox:27198): Gdk-WARNING **: XID collision, trouble ahead in my .xsession-errors file and then an X server crash.

On Thu, Oct 29, 2009 at 12:11:49PM -0000, cviorel wrote:
> Using Koala RC with latest updates, still receiving (firefox:27198):
> Gdk-WARNING **: XID collision, trouble ahead in my .xsession-errors file
> and then an X server crash.
>

please don't post more "me too"'s here. use the "this bug affects me" feature
in the bug tracker.

 - Alexander

I had to reboot after this happened and it wiped out all of my firefox settings.

hi Alexander,

since final karmic release, i've added some ppa:

- ubuntu-mozilla-daily : i'm using 3.5.5 shiretoko now
- cybolic ppa

So, i confirm that there is no more xid collision seen in .xsession-errors .

I would like to know meanwhile the recommended practice ? Delete xsession-errors every week ? I'm getting 30MB+ .xession-errors files per session, will this keep increasing ?

@Miguel:
I would suggest starting firefox from a terminal with:
firefox > /dev/null &

I guess ALT+F2 with firefox > /dev/null should work, too.

Here is a post that explains why the "Gdk-WARNING **: XID collision, trouble ahead" message was added:
 <a href="http://osdir.com/ml/svn-commits-list/2009-05/msg01611.html"></a>
 Looking at the patch, it seems to me that the best fix would simply be to use g_debug() instead of g_warning() to log the message. This would mean that you would only get it when you were actually trying to debug a GTK/GDK problem.

uploaded gtk+2.0 (2.18.3-1ubuntu2) karmic-proposed; urgency=low and subscribed ubuntu-sru

we just remove that warning output alltogether for now.

Accepted gtk+2.0 into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

hi Martin,

Lucid need it too: xid collision is flooding .xsession-errors (actual is 2.18.3-1)

@Martin Pitt: The new version from -proposed has fixed it for me, no ill effects ore regressions so far.

that's ok in Lucid now

please ignore #62, xid collision come ramdomly:

seem to start flooding when FF open url links with few animated pop in.

some more comments:

continue to observe why xid problems happens.
Today i'm posting on a forum (forexfactory.com), using it during more than 1 hour without any xid collision. Then i open 1 more FF tab to search on google, without opening any links provided; and xid collisions come flooding.

To resume: there is no addins used (flash or else), nothing logged too. Is it an overflow ?

This bug was fixed in the package gtk+2.0 - 2.18.3-1ubuntu2

---------------
gtk+2.0 (2.18.3-1ubuntu2) karmic-proposed; urgency=low

  * debian/patches/093_git_change_fix_gtkiconview_rendering_issue.patch:
    - drop not confirmed fix (see #393534)
  * debian/patches/094_remove-xid-collision-warning.patch:
    - remove output of "Gdk-WARNING **: XID collision, trouble ahead" which can
      cause excessive .xsession-errors flooding (LP: #401823)
 -- Alexander Sack <email address hidden> Mon, 09 Nov 2009 13:30:40 +0100

Copied gtk+2.0 from karmic-proposed to lucid.

I don't think that suppressing the warning message fixes the underlying bug. This is a rather deep bug. Have a look at http://bugs.freedesktop.org/show_bug.cgi?id=21583

This has been a huge problem for me for at least the last 6 months, if not the last year. The only patch I've seen come out that addresses it is http://bugzilla-attachments.gnome.org/attachment.cgi?id=144074 from the Gnome bug here https://bugzilla.gnome.org/show_bug.cgi?id=581526 . I've patched gtk with this patch (which conflicts with the xid collision error hiding patch, which I removed) and am about to test this on my own system from my PPA.

I'm all for a better solution to the XID problem and this certainly doesn't seem to be a permanent fix (why can the X server even give out conflicting XIDs at all?), but I really like having firefox run without crashing a few times a day (even though I have 4-5 windows and typically between 140-180 tabs open, total).

Anyone who wants to test out this patched gtk can get it off my PPA here:
https://launchpad.net/~lessoffensive/+archive/lessoffensive/

Just wanted to report back--I've been using this patch since I posted my previous response and noticed at one juncture experiencing a severe memory leak, though I now believe that was prior to rebooting and may have been from an already loaded library. Since rebooting and using it, I have not experienced any firefox crashes and have seen (running it in a terminal) a number of XID collisions that it has managed to work around. So it seems that this may work until the XID issue is permanently fixed.

I can personally confirm that it is not firefox that is causing the problem. It seems to be one of it's dependencies. I compiled the latest version from source. Now I need to know what dep is causing the issue.

Earlier I was using Ubuntu 8.10. Recently I upgraded to Ubuntu 9.10 i386 32 bit OS.
Now I have started getting this error.

(firefox-3.5:2398): Gdk-WARNING **: XID collision, trouble ahead

so please let me know the possible solutions.

@rajhanschinmay
Are you getting flooded with the messages, or is it occasional? If it's occasional, then there are already upstream bugs for the issue and it's only a warning, so nothing bad should happen. Before it was flooding the .xsession-errors file for people which was causing issues.

Micah said "it's only a warning, so nothing bad should happen".

Please read comment 67. This diagnostic is a warning of bad things going on. They will eventually bite you unless you restart FireFox.

please don't change bug status without explanation.

Updating GTK bug as GNOME Bug Tracker #590690 is the one related to the Firefox issues which seems to be the focus of this bug.

@D. Hugh Redelmeier

I apologize, I had not read all the upstream comments. It does seem to be a more serious issue, but we're waiting on upstream now. After upstream fixes it, we might be able to patch the current versions of the involved apps.

I am sry for changing the status. I was not knowing what it is.

I searched and found this as partial solution.
use command
sudo aptitude reinstall firefox-3.5

this helped to reduce the problem.

Now I am getting following error message:
(firefox:18250): GLib-WARNING **: g_set_prgname() called multiple times

if there is any solution, please let me know.

GDM complaint to about XID collision:

gdm-binary[1126]: WARNING: Unable to find users: no seat-id found

sorry, forget post #79

(firefox-bin:13635): Gdk-WARNING **: XID collision, trouble ahead

flood again Xsession-errors with FF 3.6 (Lucid A3 updated)

Xid collision appears with some URL (like http://www.boursorama.com even with noscript in full protection) but not with launchpad site for example.
So, it seem that is related to additional technologies ( in that case of "boursorama" i'm only seeing "Adobe Flash Player 10" be used as everything else seem be stopped by "noscript").
If i close this "boursorama" url, Xid collision flooding stop.
Other sites using Flash or else with banners and animated graph seem build these Xid collisions.

Flash installed with flashplugin-installer (Lucid 10.0.45.2ubuntu1)

new tests results on Lucid with latest updates installed:

FF 3.6 with plugin "Shockwave Flash 10.0 r45" activated make "Xid collision" errors appears and flooding .Xsession-errors.
Deactivating that plugin stop that problem on my end.

no more "Xid collision" since i use gnash instead of shockwave.

Happened on Lucid today, everything here is just up-to-date.

(exe:2295): Gdk-WARNING **: XID collision, trouble ahead
(exe:2295): Gdk-WARNING **: XID collision, trouble ahead
(exe:2295): Gdk-WARNING **: XID collision, trouble ahead
(exe:2295): Gdk-WARNING **: XID collision, trouble ahead
(exe:2295): Gdk-WARNING **: XID collision, trouble ahead
(exe:2295): Gdk-WARNING **: XID collision, trouble ahead
(exe:2295): Gdk-WARNING **: XID collision, trouble ahead

It might be related to Adobe Flash which I'm using into Google Chrome beta. But for sure it doesn't happen while browsing Youtube (I'm doing it now and "peeping" a console window with "tail -f .xsession-errors" now).

I have the same problem here running Seamonkey 2.0.3 on openSuSE 11.2.

As soon as I bring a tab to the foreground with an embedded flash player content the XID warnings flood my console (Seamonkey is startet from a comand line). After bringing another tab to the foreground (without flash content) XID warnings no more occur. It is enough to hide a flash content to stop this warnings.

Seems it is a flashplayer bug.

    Dateiname: libflashplayer.so
    Shockwave Flash 10.0 r45

I have the same problem here running Seamonkey 2.0.3 on openSuSE 11.2.

As soon as I bring a tab to the foreground with an embedded flash player content the XID warnings flood my console (when Seamonkey is startet from a CLI).

After bringing another tab to the foreground (without a flash content) the warnings stop.

    Dateiname: libflashplayer.so
    Shockwave Flash 10.0 r45

I don't think that the bug is related to Flash: I get it without having Flash on my system. I do think that Flash makes everything worse :-)

Again, I point to this bug report: http://bugs.freedesktop.org/show_bug.cgi?id=21583

Unfortunately, that report has been diluted by a bunch of Cairo problem reports that I believe have nothing to do with the underlying problem. Pay attention to comments up to #5, then read the rest realizing they may be about a different bug.

If I were an X programmer, I'd attempt to write a small test program to duplicate the problem.

This was marked fixed because of patch 094_remove-xid-collision-warning.patch. I don't see this patch in the current sources so it's not fixed anymore. My .xsession-errors file is mess:

test@box:~$ cat .xsession-errors | grep "trouble ahead" | wc -l
6039
test@box:~$ uptime
 15:43:43 up 6:00, 3 users, load average: 0.06, 0.13, 0.23

=> a hundred lines per hour coming from firefox and operapluginwrapper. :-(

Can't we have this message hidden again or repeated messages detected?

For what it's worth, I just had this hit me again but on Fedora 11 with Firefox 3.5.8 on x86-64. Note: I don't have Flash on the system. The fact that it is Fedora should not be important since this is an upstream bug.

Removing the warning does not remove the bug, it just obscures it.

If the flood of warnings is a problem, perhaps a patch to rate-limit the warning would be useful.

Here's what I observed during this event:

- FireFox opened a tab in a new window without the usual navigation bar etc. This is a sure sign that things have gone very wrong.

- I looked in stdout from FF and it did have the dreaded XID warning

- I closed the window that should have been a tab

- firefox printed "firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0." on stdout and quit

- No core file was produced even though I have the appropriate ulimit cranked up

confirmed previous post 86

its with Lucid installed on its own formated partition: i began to have these warnings after installing flashplugin-installer 10.0.45.2ubuntu1 and viewing some video on web.

This problem came up with Karmic and a patch has been applied to stop flooding .xsession-errors ( only hidding but better than nothing), now Lucid show up this too with shockwave on my end.

So i've removed/purged theses packages and settings: result is no more xid collisions (i'm using gnash instead)

XID collision, trouble ahead still. Ubuntu 10.4

As of Lucid Beta 2 kernel 2.6.32-21 and intel driver 2:2.9.1-3ubuntu5 still getting XID collisions with i845 video graphics. Must be soaking up some processor cycles and slowing things down.

Jerry

Freshly installed Lucid Lynx gives me the warnings "(firefox-bin:7011): Gdk-WARNING **: XID collision, trouble ahead"

This randomly showed up in my Terminal:

steven@utop:~$
(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:2494): Gdk-WARNING **: XID c...

I also get this warning but my situation is worse as Firefox freezes any time I click on a menu item, Bookmarks Toolbar item or right-click on a text box. Since this bug does not mention freezing, only annoying error output, I started a new one, Bug #574617 for my type of situation. As detailed in that bug report, reinstalling Firefox, xulrunner and removing flash-plugin, as well as running in firefox --safe-mode does not help.

Sorry, that should have been "removing adobe-flashplugin".

After generating anywhere from hundreds, to thousands, of these messages, firefox 3.6.3 eventually segfaults here on latest updated lucid x64 install with flash 10.0.45.2.

following the flood of thousands of these errors I get:

(firefox-bin:8111): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:8111): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:8111): Gdk-WARNING **: XID collision, trouble ahead

Program received signal SIGSEGV, Segmentation fault.
0x00007fffd37e46db in ?? () from /home/marc/.mozilla/plugins/libflashplayer.so
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7bc17bb in raise () from /lib/libpthread.so.0
(gdb) continue
Continuing.
[Thread 0x7fffd11f6710 (LWP 8142) exited]
[Thread 0x7fffbceff710 (LWP 8695) exited]
[Thread 0x7fffd98ff710 (LWP 8506) exited]
[Thread 0x7fffd19f7710 (LWP 8141) exited]
[Thread 0x7fffdecab710 (LWP 8763) exited]
[Thread 0x7fffd21f8710 (LWP 8140) exited]
[Thread 0x7fffd90fe710 (LWP 8139) exited]
[Thread 0x7fffde0a1710 (LWP 8125) exited]
[Thread 0x7fffe17f9710 (LWP 8123) exited]
[Thread 0x7fffdf4ac710 (LWP 8120) exited]
[Thread 0x7fffdfcad710 (LWP 8119) exited]
[Thread 0x7fffe52ff710 (LWP 8115) exited]
[Thread 0x7fffe61e5710 (LWP 8114) exited]
[Thread 0x7fffe69e6710 (LWP 8113) exited]
[Thread 0x7fffe73f1710 (LWP 8112) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb)

I see Fix Released for some components in this bug. Is this still the place to report this bug for Firefox 3.6.3 in Lucid?

For information, this "Gdk-WARNING **: XID collision, trouble ahead" message shows up repeatedly in my console when (and only when) i am displaying a flash having parameter wmode='transparent'. Removing this parameter also removes the trace. I tried adding/removing the parameter a dozen times and the behavior is pretty consistent:

 <embed id="flash_object" src="xxx.swf" quality="high" bgcolor="#869ca7"
   width="100%" height="100%" name="XXX" align="middle"
          flashVars=""
   play="true"
   loop="false"
   quality="high"
   allowScriptAccess="always"
   type="application/x-shockwave-flash"
   wmode="transparent"
   pluginspage="http://www.adobe.com/go/getflashplayer">
 </embed>

shows "(firefox-bin:10775): Gdk-WARNING **: XID collision, trouble ahead
" traces in the console

 <embed id="flash_object" src="xxx.swf" quality="high" bgcolor="#869ca7"
   width="100%" height="100%" name="XXX" align="middle"
          flashVars=""
   play="true"
   loop="false"
   quality="high"
   allowScriptAccess="always"
   type="application/x-shockwave-flash"
   pluginspage="http://www.adobe.com/go/getflashplayer">
 </embed>

does not.

In my case, i doesn't change much since i need to have this 'wmode' value to 'transparent'.

By the way, "wmode='opaque'" also works. The point is not to have "wmode='window'" (which is the default).
From the information i gathered around, this wmode parameter has a big impact on the way the flash is physically displayed in the window manager and apparently affects this "XID collision" issue.

How do I fix this bug

(firefox-bin:2051): Gdk-WARNING **: XID collision, trouble ahead

My "xsession-errors" file is also flooded and crippled with thousand of that warning ! (Last Ubuntu Lucid here, with all the updates).
Please do something for us. This bug is painfull... How to fix it ?

firefox crashes when trying to play a flash video producing this error

My guess is that this is a problem with flash. Nothing to do with Firefox or GDK.
I am working on an Adobe Air application. Using the Air debug launcher. (adl) The test application has Air running Flex running webkit running Flash and this is where this warning shows up. Anything without this second layer of flash does not have any problems.
My guess is poor GDK programming on the part of Adobe.

(adl:2702): Gdk-WARNING **: XID collision, trouble ahead

I think that Flash provokes the bug more often than other things, but I don't think that this is a Flash bug. Read my comment #92.

My desktop is Fedora 11. I get these crashes regularly if I leave a lot of tabs open for a long time. I don't have Flash installed on the system. I don't know if there are particular web pages that provoke the problem or just the shear quantity of them.

I think that this is the bug: http://bugs.freedesktop.org/show_bug.cgi?id=21583
As with many bug reports, there is somewhat of a muddle. In this case, Cairo is mixed in and confusing things.

I can confirm this bug. The exact error I get is: "(firefox-bin:17547): Gdk-WARNING **: XID collision, trouble ahead"
I'm running Mint Isadora X64 and firefox 3.6.3. The problem shows up in the console when you run firefox from console. Initially, I had the problem where multiple of this error would populate the console and if I went to a specific website, or typed in a URL, the browser'd seg fault and instantly crash. So I found an entry in the ubuntu forums that suggested it was a problem with adobeflash x64. I followed these instructions: http://ubuntuforums.org/showthread.php?t=1358591

Now, I still get the exact same message, but so far (last hour or so), no seg faults and browser crashing. So I HOPE the new adobe flashplayer at least will help firefox be more stable.

Peace

firefox-bin:3956): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:3956): Gdk-WARNING **: XID collision, trouble ahead

Lucid, I even deleted my .mozilla folder to be sure, its something else going on after the upgrade.

In Xubuntu-Lucid FireFox gives:

Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
Failed to load x11 FrontEnd module.

(firefox-bin:1550): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:1550): Gdk-WARNING **: XID collision, trouble ahead

(firefox-bin:1550): Gdk-WARNING **: XID collision, trouble ahead
...

Alexander,
may we add FF 3.6.3, since it still floods xsession-errors?
$ dpkg -l firefox
ii firefox 3.6.3+nobinonly-0
$ uname -a
2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux
$ ls -l /var/lib/apt/periodic
total 0
-rw-r--r-- 1 root root 0 2010-06-01 19:56 update-stamp
-rw-r--r-- 1 root root 0 2010-06-01 20:22 update-success-stamp

Same problem in Firefox 3.6.3 in Ubuntu 10.4. What's the best way to report the same bug in newer software?

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3

Linux linux 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux

|~[5253] ls -l /var/lib/apt/periodic/
total 8
drwxr-xr-x 2 root root 4096 May 27 08:04 ./
drwxr-xr-x 6 root root 4096 Jun 2 05:25 ../
-rw-r--r-- 1 root root 0 Jun 2 00:31 update-stamp
-rw-r--r-- 1 root root 0 Jun 2 01:57 update-success-stamp

Same problem. My .xsession-errors is about 5Mb filled with
(firefox-bin:1639): Gdk-WARNING **: XID collision, trouble ahead

Firefox about:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3

$ uname -a
Linux thor 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux

All updates are applied.

Please, do not post comments that just say "it happens to me too". Instead, use the button "this bug affect n persons" at the top of the page.
The goal of this button is to avoid flooding in comments and to make a difference between affected people and comments bringing information to solve the problem.

Thanks.

arno_b,
I did use the button "affects me too", in addition I've raised my question, since the header only mentiones FF 3.5.
As Ian! D. Allen #116 pointed out, do we need to create a new bug for the same reason but different FF version?
Thanks.

Sam, your question was not concerned by my post (of course ;)).
Do not open an other report for firefox 3.6 since the problem seems to be the same than firefox 3.5.
I add the ubuntu firefox package to the list of the affected packages; since package firefox on Lucid is mapped to firefox-3.6: this bug report is now also related to FF3.6.

Merci beaucoup arno_b.

Update.
Not sure if it's related.
I've found the multiple lines '(firefox-bin:1527): Gdk-WARNING **: XID collision, trouble ahead'
only appear when a java applet starts. Java brings up CPU to 100.
http://javatester.org/version.html

xession-errors says at this point:
## multiple lines
(firefox-bin:1527): Gdk-WARNING **: XID collision, trouble ahead
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8-0ubuntu1)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
java.lang.InterruptedException: sleep interrupted
 at java.lang.Thread.sleep(Native Method)
 at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:735)
 at sun.applet.PluginAppletViewer.handleMessage(PluginAppletViewer.java:649)
 at sun.applet.PluginStreamHandler.handleMessage(PluginStreamHandler.java:270)
 at sun.applet.PluginMessageHandlerWorker.run(PluginMessageHandlerWorker.java:82)

Exception in thread "Thread-14" java.lang.NullPointerException
 at sun.applet.AppletPanel.showAppletStatus(AppletPanel.java:947)
 at sun.applet.AppletPanel.run(AppletPanel.java:607)
 at java.lang.Thread.run(Thread.java:636)

I was trying to troubleshoot a freezing Java applet for a friend, so I started Firefox from the terminal. After the Java applet froze, I looked in the terminal and found a stream of the "...trouble ahead" messages.

I've been able to consistently reproduce this on two systems now, so maybe it is a usable test case. The only caveat is you need to have a TD Ameritrade account (which I don't).

Anyway, here's what I did:
1) I am using sun-java6 NOT openjdk/icedtea.
2) Open the TD Ameritrade Command Center.
3) Once the streamer has loaded, click on the settings button (looks like a wrench) to open the streamer settings. The settings window begins to appear, but is only partially drawn (no text), then it freezes up so badly that the system monitor cannot kill the task. Other applications can be used and closed, but the Java app will just sit there frozen until the system is rebooted.

This doesn't happen using Karmic, only Lucid. I have tested it on two systems, both using an Intel graphics chipset (I don't know if that matters). The next time I am over at my friend's place, I will try to get more information so I can create a proper bug report.

new test on maverick+sun-java-jre+firefox 3.6.4

got these comments logged into .xsession-errors:

(<unknown>:4295): Gdk-WARNING **: XID collision, trouble ahead
  (child won, so we're deferring)
  (child won, so we're not deferring)
  (processing deferred in-call)

I seem to be seeing this problem too:

rep 'XID collision' .xsession-errors | wc -l
56489

mstevens@mstevens-desktop:~ % uname -a
Linux mstevens-desktop 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux

Fully patched Lucid Lynx.

Hi,

I've also this bug in Seamonkey 2.0.4.

(seamonkey-2.0-bin:2003): Gdk-WARNING **: XID collision, trouble ahead

$ dpkg -l | grep seamonkey | grep ii
ii seamonkey 2.0.4+nobinonly-0ubuntu1 The Seamonkey Internet Suite
ii seamonkey-browser 2.0.4+nobinonly-0ubuntu1 Seamonkey Navigator (Internet browser) and C
ii seamonkey-chatzilla 2.0.4+nobinonly-0ubuntu1 Seamonkey Chatzilla IRC client
ii seamonkey-dbg 2.0.4+nobinonly-0ubuntu1 Debugging symbols for the Seamonkey Internet
ii seamonkey-gnome-support 2.0.4+nobinonly-0ubuntu1 Gnome Depends for the Seamonkey Internet Sui
ii seamonkey-mailnews 2.0.4+nobinonly-0ubuntu1 Seamonkey Mail & Newsgroups and Address Book

$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

$ uname -a
Linux eeepc 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux

Quick re-summary then.

Karmic looks like it was fixed (although it only seems to be me that posted a confirmation.)

Lucid says "fix-released." I, and many others, are still seeing these warnings in lucid. So, "fix" doesn't work, can someone suitably qualified change the status back please, or state which symptoms they think are fixed, and I'll open a new bug for anything that isn't fixed.

Flash *seems* to trigger it the most easily, although correlation is not causation.
On my system Firefox without flash, and Chrome, and very occasionally other arbitrary GTK apps trigger it.

... and the bug is almost a year old. Oops. :-) Happy to help test anything if required.

I have a new work laptop coming next week so I have an opportunity to test a totally fresh install with all current updates, will do so and report back.

Could I ask no-one else posts confirmations for now, we've got about 50 of those above already...

(<unknown>:3480): Gdk-WARNING **: XID collision, trouble ahead

... I just started noticing this for the first time a few days ago.

I've always been running basically the latest released ubuntu.

As stated above by Zack Evans and confirmed by many previous me-too's, this bug is still present in GTK on an up-to-date lucid install. This occurs with the latest chromium stable build for me. It is not fixed. Changing status to correctly reflect... status.

Could someone clarify if this is a firefox bug or not? I am getting "XID collision, trouble ahead" with the qiv image viewer.
https://bugs.launchpad.net/ubuntu/+source/qiv/+bug/625707

On Seamonkey 2.0 this bug appeared when activating adobe flash plugin.

maverick is full filed too with this warning (i386 updated)

Pffff, that annoying bug has been reported first by dino99 on 20-07-2009. ... More than one year later, still nothing... Can we have a kind of "status" or scheduled fix release ? I mean, that bug affects thousand of people and cripple their "xsession-errors" file with tons of warnings... Why it takes so long to fix ?...

the flooding of .xsession-errors and hd activity/waste is most
annoying for the end user.

here's a workaround:
ALT+F2

gnome-session-properties ENTER

"Add"
Name: remove xsession-errors on login
Command: rm -f .xsession-errors*
Comment: cool

That's it. logout and login.

Note that is should be "rm -f .xsession-errors*"
-f means, that if no .xsession-errors* is there rm won't complain.

If you want to check your logfile again just disable the entry in
gnome-session-properties. logout and login.

I'm sorry:

The command line is wrong. It works with this line:

sh -c "rm -f ~/.xsession-errors*"

my solution is to use logrotate to limit xsession-errors size

What's the * for? You don't really want to remove every file starting with ".xsession-errors", you ONLY want to remove the file ".xsession-errors". I'd suggest doing:

sh -c 'rm -f ~/.xsession-errors'

the * ist just because there is also a file called .xsession-errors.old

if you switch this on/off in your session-properties, in case you want to view the log file, with this XID-collision flooding, it may happen, that the .old-file also get's quite big.

maybe the * is too much, but it's not harmfiul for other files. of course, your version is the exact way to do it. also the ' instead of " are better.

I am also getting this error very frequently.

Firefox:
(firefox-bin:2043): Gdk-WARNING **: XID collision, trouble ahead

Seamonkey:
(seamonkey-2.0-bin:2193): Gdk-WARNING **: XID collision, trouble ahead

Opera:
(operapluginwrapper:2507): Gdk-WARNING **: XID collision, trouble ahead

I am running my browsers via a session created using Putty and ssh onto a linux Ubuntu 10.04 OS.

I think this is to do with Adobe flash player only else how come 3 browsers have the same problem/

Kindly solve it and let all of us know the solutions if any.

Thanking you.

hi devs,

waiting the final release in few days for maverick, and this error is continuously flooding our log, so is there a way to hide it at least ?

@dino99:
I guess this is related to the flash plugin. I only get this error with installed flash plugin. Maybe the new preview releases from adobe fixes this. But I doubt it. Maybe it's not Flash's fault at all.

However, to work around the problem:

Do once in terminal: rm -f ~/.xsession-errors*

Then hit ALT+F2 and type gnome-session-properties

Add a new entry with the command: sh -c 'rm -f ~/.xsession-errors'

Add a description like "deletes xsession-errors at login"

Close, Log out and log in. You're done.

I've removed the official flashplugin-installer incl. nspluginwrapper and installed native 64bit 'square' from Adobe.
I'm not able to reproduce the issue with java applet, flash, google maps, opened all in tabs.
$ LANG=C apt-cache policy firefox
firefox:
Installed: 3.6.12+build1+nobinonly-0ubuntu0.10.04.1

java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.2) (6b18-1.8.2-4ubuntu2)
OpenJDK 64-Bit Server VM (build 16.0-b13, mixed mode)

on Natty i386 updated

confirm that this problem is no more logged now with firefox 4

Issue stil occurs with google-street-view but not with other flash sites.
The pid in xsession-errors refers to plugin-container.
ps aux |grep 1555
1000 1555 14.0 11.4 703020 116876 ? Sl 13:07 49:54 /usr/lib/firefox-3.6.12/plugin-container /user/zookeeper/.mozilla/plugins/libflashplayer.so 1521 plugin true

Also affects an updated Maverick.
I typed something in FF 3.6.13 and suddenly got logged out.
Afterwards I reviewed .xession-errors.old and found the ominous lines there.
Before I've visited lots of pages using flash.
I'm using native 64bit 'square' since nspluginwrapper is still no useful choice in my case.

Forgive me something but - come on - this bug exists since 2009.
It should be solved by now, in my humble opinion... but it's not!
I can still reproduce:
" (firefox-bin:2685): Gdk-WARNING **: XID collision, trouble ahead "
in Ubuntu 10.10 and Firefox 3.6.16, Chrome 10.0..., etc. when viewing sites with flash content.
I believe that this is causing some flash plugin crashes.
After more than a year googling perhaps hundreds of webpages, I still couldn't find a solution.

If you read enough of this bz entry, you will see that it cannot be fixed by a new Adobe Flash. Proof: I have the problem but don't have Flash installed.

My best guess is that this is a GTK bug. You will see hints of this if you read the whole bz entry. Or just look for GTK.

I am using 3.6.13 version of Firefox along with Adobe Flash player version 10.0 in Ubuntu 10.04.
I am getting this error.

(<unknown>:1716): Gdk-WARNING **: XID collision, trouble ahead

I tried upgrading my Firefox version to 3.7 once but I found it was not at all a stable version and crashed multiple times.
so now I decided to use this version which is performing well except above warnings.

someone above has suggested to use latest Macromedia flash player.
http://download.macromedia.com/pub/labs/flashplatformruntimes/flashplayer10-3/flashplayer10-3_b1_lin_030811.tar.gz

I downloaded this file. It is a tar file. I extracted it.
Inside it, there is a file like *.so and one folder.
kindly let me know how to install that.

I am having multiple users in Linux. so I would want to install it in such a way that all the other users also can use the same flash player.
kindly let me know the steps.

if .deb kind of file exists for this flash player, then kindly give me the link.
Installing that is much easier and safer.

Yours
Chinmay

If it's not a flash issue, at least interferes with flash videos playback.
And perhaps it's a javascript issue.
Eg., I get "trouble ahead" all the time on videos like these: http://videos.sapo.pt/categoria.html?id=9

This should really be passed to the GDK guys as well (if no one has beaten me to it meanwhile)

That "XID collision, trouble ahead" message originates from /usr/lib/libgdk-x11-2.0.so.

@Chinmay

Well, I don't know about at .deb, but there is a package of the 10.3 player (the FINAL version)
called flash-plugin-10.3.183.11-release.i386.rpm.

Just for test I tried installing it with
$ rpm -i --force-debian --nodeps flash-plugin-10.3.183.11-release.i386.rpm

and what I can I say, it worked! =D
For IceWeasel, I just had to symlink from /usr/lib/flash-plugin/libflashplayer.so to /usr/lib/iceweasel/plugins and voila!
BTW, don't be worried about the "--nodeps" override; RPM cannot correctly detect dependencies on Debian and even does not know about existence of a sane libc6/libstdc++/whatever system, so it generally assumes you have literally "none" of the above. Though you do have those and they work.)

-

Besides, there is also a v11 package out meanwhile:
flashplayer-mozilla_11.1.102.55-0.2_i386.deb
This time, for IceWeasel, symlink from /usr/lib/flashplayer-mozilla/libflashplayer.so to said Iceweasel plugins directory.

FWIW. Though it must be noted that it did not make these stupid error messages disappear.

I did not seen that errors since a while (#172) and gtk2 is less used now, so this report is quite dormant. Maybe it could be closed.

dormant and still broken are two different things...

bladernr@klaatu:~$ grep XID .xsession-errors |wc -l
139

That's 139 instances in .xsession errors in the last 24 hours for me...

Not to mention the fact that SO MANY things are reporting errors into xsession-errors these days (for me at least) that I have to delete the log every few days as it very quickly grows to over 100GB in size... I think the last time I caught it, it went from 0 to 95GB in about a week :(

I need to remember to start parsing that long and opening more bugs

@Jeff
i've often seen the xsession-errors errors/warnings going away after renaming the .gconf .local .gnome2 then they are cleanly recreated on next boot. That should not exist with if packages updates was taking care of deprecated settings/symlinks etc but the fact is.

I have also got this bug and here it is causing system crash. This bug exists after Ubuntu 10.04, at least for me. It is reproducible
by opening sites with flash content. Also for those who, this is just a logging issue, well let me say, it is not. This is real problem and it should be fixed. I am also giving my system information so that developers can fix this easily.

I have raised this issue in separate ticket 994688

If it helps any, I have this problem too, kubuntu,
lsb_release:
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
uname -r:
3.2.0-24-generic
dpkg -l 'libgtk2.0*':
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-================-================-================================================
ii libgtk2.0-0 2.24.10-0ubuntu6 GTK+ graphical user interface library
un libgtk2.0-0-dbg <none> (no description available)
ii libgtk2.0-bin 2.24.10-0ubuntu6 programs for the GTK+ graphical user interface l
rc libgtk2.0-cil 2.12.10-2ubuntu4 CLI binding for the GTK+ toolkit 2.12
un libgtk2.0-cil-de <none> (no description available)
ii libgtk2.0-common 2.24.10-0ubuntu6 common files for the GTK+ graphical user interfa
ii libgtk2.0-dev 2.24.10-0ubuntu6 development files for the GTK+ library
ii libgtk2.0-doc 2.24.10-0ubuntu6 documentation for the GTK+ graphical user interf

I notice this issue when running Google-Chrome from cmdline.

Also believe this bug could be related to crashes/system freezes/hangs I experience, almost regularly.

This one's quantal 3.4.0-5 after today's update/upgrade even.

Jerry

I run Chrome from the command line in order to add the '-disable-bundled-ppapi-flash' argument to prevent the other flash freezeup, and I get this message in the terminal window that's running Chrome.

Cleaning up where this can no longer be fixed/has been fixed. Does anyone still have this issue?

Can someone please close this bug?