Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: Trouble ahead!

  1. #1
    Join Date
    Jul 2008
    Location
    Éire
    Beans
    88

    Trouble ahead!

    Just got back from cinema with girlfriend and checked my laptop. Had aterm, ncmpc++ and deluge running and my aterm was filled up with:

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

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

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

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

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

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

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

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

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

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

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

    (firefox:31747): Gdk-WARNING **: XID collision, trouble ahead
    [me@arch_laptop ~]$
    cept the whole aterm buffer was filled with it!

    Firefox wasn't running so obviously there was some trouble! I thought it was funny so I said I'd share it, maybe it's just the tiredness (4:26 am here!) Oh well, good night ubuntu forums
    To be human is to affirm one's humanity by recognizing the humanity of others and, on that basis, establish respectful human relations with them.

    Ubuntu User 24011

  2. #2
    Join Date
    Oct 2006
    Beans
    Hidden!

    Re: Trouble ahead!

    This is not a new bug. Its just that there was a gtk+ commit that now shows this error: http://git.gnome.org/cgit/gtk+/commi...970b93438295a9.

    Bugs on the underlying issue:

    Gnome bug 581526 in gdk "XID table corruption from reuse of XIDs, resulting in leak, incorrect window destroyed status ("unexpectedly destroyed"), and crash" - http://bugzilla.gnome.org/show_bug.cgi?id=581526.

    Mozilla bug 467744 in Widget: Gtk "crash @gdk_window_new from moz_drawingarea_create_windows after GdkWindow 0x???????? unexpectedly destroyed" - http://bugzilla.mozilla.org/show_bug.cgi?id=467744.

  3. #3
    Join Date
    Oct 2009
    Beans
    30

    Smile Re: Trouble ahead!

    the problem still exists in ubuntu lucid with latest firefox!

  4. #4
    Join Date
    May 2007
    Location
    Australia
    Beans
    167
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Unhappy Re: Trouble ahead!

    confirmed, this still exists, occurring on both FF 3.6 and Google Chrome:

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

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


    uname -a
    Linux michael-desktop 2.6.32-19-generic #28-Ubuntu SMP Wed Mar 31 17:46:20 UTC 2010 i686 GNU/Linux

  5. #5
    Join Date
    Sep 2005
    Beans
    32
    Distro
    Kubuntu Development Release

    Re: Trouble ahead!

    Just got this tonight for the first time, Lucid 64-bit, with firefox. I haven't installed/tried it with chrome. But just today I installed my Gigabyte GSX 250 Nvidia card, and am running it via HDMI to my monitor with s/pdif leads plugged in. I say this because I never had this issue before hand. I haven't ran Konqueror via command line, but that has crashed as well. I hope this helps!

  6. #6
    Join Date
    Sep 2005
    Beans
    32
    Distro
    Kubuntu Development Release

    Re: Trouble ahead!

    Forgot this in the last post, but I seem to have only crashed with Gmail, with a seg fault, (yikes you can't point their firefox!) <<((that was me)) and yahoo caused many "(firefox-bin:2242): Gdk-WARNING **: XID collision, trouble ahead" warnings, however no crash. This info should help more than my last useless post.

  7. #7
    Join Date
    Nov 2007
    Location
    Siena, Italy
    Beans
    18
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: Trouble ahead!

    Same thing here using Namoroka development version and visiting Launchpad. (that's really weird... I have a bug visiting a bug tracking site!! :S)

  8. #8
    Join Date
    Mar 2006
    Location
    Denmark - Copenhagen
    Beans
    2,165

    Re: Trouble ahead!

    Code:
    aktiwers@HAL2:~$ firefox
    FoxyProxy settingsDir: /home/aktiwers/.mozilla/firefox/wdtnbv9m.default/foxyproxy.xml
    
    (firefox-bin:17615): Gdk-WARNING **: XID collision, trouble ahead
    
    (firefox-bin:17615): Gdk-WARNING **: XID collision, trouble ahead
    info: 0, warning: 936, error: 3976
    Done
    info: 0, warning: 0, error: 1
    Done
    info: 0, warning: 0, error: 1
    Done
    info: 0, warning: 0, error: 1
    Done
    info: 0, warning: 936, error: 3976
    Done
    Segmentation fault
    aktiwers@HAL2:~$ firefox -v
    Mozilla Firefox 3.6.3, Copyright (c) 1998 - 2010 mozilla.org
    aktiwers@HAL2:~$ uname -a
    Linux HAL2 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux
    aktiwers@HAL2:~$
    Got it as well

  9. #9
    Join Date
    Aug 2008
    Beans
    7

    Re: Trouble ahead!

    @aktiwers: Same system and problem (firefox segfaulting even after purging session information form filesystem manually):

    Mozilla Firefox 3.6.3, Copyright (c) 1998 - 2010 mozilla.org
    Linux thinktank 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux
    Ubuntu 10.04 LTS w/ latest Updates and Patches installed

    --

    I was able to fix the problem by moving from open source radeon_drv.so to ATI closed source fglrx_drv.so.

    Either install the one that comes with Ubuntu 10.04 LTS or install the latest catalyst 10.6:
    ati-driver-installer-10-6-x86.x86_64.run --buildpkg Ubuntu/lucid
    purge existing fglrx drivers and install at least:
    sudo dpkg -i fglrx_8.741-0ubuntu1_amd64.deb
    sudo dpkg -i fglrx-amdcccle_8.741-0ubuntu1_amd64.deb
    sudo dpkg -i fglrx-modaliases_8.741-0ubuntu1_amd64.deb
    sudo dpkg-reconfigure fglrx
    sudo aticonfig --initial --force

    All steps (including the latest) are required or google or head over to
    http://www.phoronix.com/forums/showthread.php?t=24300

    Latest catalyst 10.6 fixes long outstanding bug:
    https://bugs.launchpad.net/ubuntu/+s...er/+bug/568988

    If you don't have ATI then I don't know how to fix your bug. At least I had the same segfault and the above worked for me.

  10. #10
    Join Date
    Mar 2006
    Location
    Denmark - Copenhagen
    Beans
    2,165

    Re: Trouble ahead!

    Im on Nvidia..

    But did an upgrade to FF 3.6.4 and the problem seams to be gone for now..

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •