Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 39

Thread: 6.2.1 .xsession-errors

  1. #11
    Moderator Moderator
    Join Date
    Jan 2010
    Location
    Asheville, NC, USA
    Posts
    528
    Quote Originally Posted by utu View Post
    So here's one type, representing 3/4 of my .xsession-errors:

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

    The four digits #### are not always the same.

    This occurs using iceweasel 3.5.6-1 with Shockwave Flash Plug-in 10.1r53.

    Disabling this plug-in makes these errors stop. Re-enabling and going to
    nytimes site, for example makes the errors begin again.

    I'm unaware of what, if any performance is not correct.

    Disabling compiz and/or java have no effect I'm aware of.

    Constructive comments welcome here.
    Also, would like to confirm version numbers are standard for Knoppix 6.2.1.
    [rant]This basically was what Steve Jobs was talking about re: Adobe Flash being "the number one reason Macs crash." Well, at least it's just error messages going into a logfile that can be handled (variously, as others have described) without a crash at all. I've tried Gnash, the open-source replacement for Flash, and it's bad - really bad. Now that HTML-5 native video is on the horizon, perhaps we can all move on to a future without mucn need for Flash as such, except perhaps in transcoding to the new format.[/rant]

    Cheers!
    Krishna

  2. #12
    Senior Member registered user
    Join Date
    Feb 2010
    Posts
    198
    @utu

    I wrote in my first message a workaround of the problem (Gdk-WARNING **: XID collision, trouble ahead)
    I made a small shell script containig:

    nohup iceweasel 1>/dev/null 2>&1 &

    and then modify your iceweasel.desktop in /usr/share/applications

    The line Exec=
    should be
    Exec=sh path-to-shell/filename.sh

    You will not get anymore error messages from iceweasel including XID collision error. You should know though, when you update iceweasel you will have to edit iceweasel.desktop again, or you can just copy it before you update and restore it after the update.

  3. #13
    Senior Member registered user
    Join Date
    Feb 2010
    Posts
    198
    This also apply to google-chrome, chromium browsers. It can be tackled the same way. It is strange though - I did not see so many XID collision errors when using midori browser which is also based on webkit - the xid collision error is there, but not as many as when using firefox or chromium based browsers

  4. #14
    Senior Member registered user
    Join Date
    May 2006
    Location
    Columbia, Maryland USA
    Posts
    1,631
    @krishna.

    I enjoy my 200 shares of Apple stock, but I don't own any of their products.
    My shock wave seems to work ok; shows You Tube here just fine. No crashes.
    It just fills .xsession-errors up in the process.
    Some folks think it's a security hazard, and I wouldn't be surprised.
    It doesn't sound right letting a hidden file fill up with undiagnosed
    complaints.

    @mecho

    I hadn't ignored your first post, mecho. I just don't prefer to adress the
    problem that way. I prefer to keep the error messages to remind me to look
    for a more fundamental work-around. One of the posts on the 60448 threads
    ought to appeal to you; it takes each complaint one-by-one from
    /etc/X11/Xsession and trashes it. It does this with a simple link, which can
    be undone if you change your mind. Now thats elegant. Just not my taste.

    @both

    You may recall I've been waiting to observe a crash I can call my own?
    Looking for what tips my 2Gb Flash Knoppix over? Well, my ship just
    arrived. I thought I'd see what Chromium might do for me. Tried Synaptic
    and, you guessed it, no Chromium here, just a crippled system. Menu panel
    and bottom icons give me enough tools to write this, but I'll have to
    shut this rig down and start over again from the CD.

    My suspicion all along was that these crashes were self-induced. All the
    Gigabyte .xsession-errors I've read about never happened here. Like Frank,
    I did it _my way_.

    See you later, with a clean .xsession-errors.

  5. #15
    Senior Member registered user
    Join Date
    May 2006
    Location
    Columbia, Maryland USA
    Posts
    1,631
    I've learned a few things since my post #1 on .xsession-errors:

    1. This topic has an enormous history I wasn't aware of.

    2. I was surprised to discover this 'gem' in Knoppix; I'm even
    more surprised now that I discover my old reliable Lucid has some
    of the same surprises hidden there.

    3. From some of my googling I came to believe or expect that
    the build-up of these errors might explain an occasional crash
    I have from time-to-time with my 2Gb Flash Knoppix set-up. I
    no longer think that is the most likely cause in my case.
    I've never seen huge errors like some report. I'm fairly sure
    my crashes are more likely self-induced results of attempting
    operations that require more resources than I've provided.


    Similarly on my post #5, I note on closer inspection of Lucid:

    1. .xsession-errors for Lucid is as described 'typical of current-
    day Ubuntus', the errors are only those for the current boot session;
    but,

    2. .xsession-errors.old for Lucid is a _cumulative_ record of past
    errors. I can't tell if this record is edited or truncated. And,

    3. A lot of the exact same type of .xsession-errors are logged for
    Lucid as for Knoppix. Perhaps its the Debian dna.


    I still think it is useful to bring these errors out in the open
    and try to make sure they are indeed harmless rather than leave
    them hidden and ignored.

  6. #16
    Senior Member registered user
    Join Date
    May 2006
    Location
    Columbia, Maryland USA
    Posts
    1,631
    I have recently upgraded IceWeasel from 3.5.6 to 3.5.10-1. These .xsession-errors, many related to Flash video are at least much reduced, if not gone. My Knoppix 6.2.1 has, at present libgtk2.0-0 version 2.18.6-1. I'm interested in similar or different experiences on this,

  7. #17
    Senior Member registered user
    Join Date
    May 2006
    Location
    Columbia, Maryland USA
    Posts
    1,631
    Upgrading IceWeasel from 3.5.6 to 3.5.10 has reduced most of the flash-video-induced .xsession errors here. I have codified a remaining six types of non-flash-related .xsession errors that I observed. Five of these now represent a minor, but puzzling continuing affliction. I have no reason to believe any of these non-flash-related .xsession-errors represent a performance problem, just an interesting puzzlement.

    ******************************** First type of error (polkit) **************************************************
    (polkit-gnome-authentication-agent-1:3419): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'
    (polkit-gnome-authentication-agent-1:3405): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'
    (polkit-gnome-authentication-agent-1:3405): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (polkit-gnome-authentication-agent-1:3419): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
    ******************************** Second type of error (polkit/nm-applet) ************************************ **
    (polkit-gnome-authentication-agent-1:3405): WARNING **: Unable to register authentication agent: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.RegisterAuthe nticationAgent() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for session Cannot register authentication agent: Remote Exception invoking org.freedesktop.PolicyKit1.Authority.RegisterAuthe nticationAgent() on /org/freedesktop/PolicyKit1/Authority at name org.freedesktop.PolicyKit1: org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for session ** (lxpanel:3373): DEBUG: cache file_name = /home/knoppix/.cache/menus/361db3b2db5a0a00114ba4be48c3a0f3 ** (nm-applet:3421): WARNING **: get_all_cb: couldn't retrieve system settings properties: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files. ** (nm-applet:3421): WARNING **: fetch_connections_done: error fetching system connections: (2) The name org.freedesktop.NetworkManagerSystemSettings was not provided by any .service files.

    ******************************* Third type of error (gtk/Clearlooks) **********************************************
    (gtk-window-decorator:3529): GConf-CRITICAL **: gconf_client_set_string: assertion `val != NULL' failed Window manager warning: Failed to load theme "Clearlooks": Failed to find a valid file for theme Clearlooks

    ****************** Fourth type of error (compiz/themes: there is no /usr/share/gdm/ in Knoppix 6.2.1) ******************

    /usr/bin/compiz.real (cube) - Warn: Failed to load slide: /usr/share/gdm/themes/Human/ubuntu.png /usr/bin/compiz.real (cube) - Warn: Failed to load slide: /usr/share/gdm/themes/Human/ubuntu.png /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format

    ************************** Fifth type of error (lxpanel BadWindow) **************************************************
    xpanel : X error: BadWindow (invalid Window parameter) lxpanel : X e
    rror: BadWindow (invalid Window parameter)

    ******* Sixth type of error (atk-bridge: solved by setting /desktop/gnome/interface/accessibility to false)
    ************
    (firefox-bin:3624): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.
    (firefox-bin:3624): atk-bridge-WARNING **: IOR not set. (firefox-bin:3624): atk-bridge-WARNING **: Could not locate registry
    Last edited by utu; 07-06-2010 at 10:29 PM.

  8. #18
    Senior Member registered user
    Join Date
    Feb 2010
    Posts
    198
    The second error you are getting - the polkit one is because there are 2 instances of polkit in your autostart. Look in /etx/xdg/autostart and ~/.config/autostart and the last place could be /etc/xdg/lxsession/LXDE/autostart - open the file and check if there is a line for polkit.
    You should have only one autostart link for polkit, otherwise this error occurs.
    The clearlooks error could be fixed as well. Just look if you have the gtkrc file in /usr/share/themes/Clearlooks/gtk-2.0
    Regarding errors 1 and 5 I am still getting them as well. Still no solution for them

  9. #19
    Senior Member registered user
    Join Date
    May 2006
    Location
    Columbia, Maryland USA
    Posts
    1,631
    @Mecho

    Thanks for your reply.
    Here's what I get for the polkit suggestion.

    #### Regarding /etc/xdg/autostart:
    knoppix@Microknoppix:/$ ls -l /etc/xdg/autostart gives
    total 8
    -rw-r--r-- 1 root root 4831 Jan 26 23:53 nm-applet.desktop
    -rw-r--r-- 1 root root 2531 Jan 15 23:40 polkit-gnome-authentication-agent-1.desktop

    #### Regarding ~/.config/autostart:
    knoppix@Microknoppix:~$ ls -l ./.config/autostart gives
    total 12
    -rw-r--r-- 1 knoppix knoppix 4832 Jul 7 09:05 nm-applet.desktop
    -rw-r--r-- 1 knoppix knoppix 2532 Jul 7 09:05 polkit-gnome-authentication-agent-1.desktop

    #### Regarding /etc/xdg/lxsession/LXDE/autostart:
    knoppix@Microknoppix:/etc/xdg/autostart$ ls -l /etc/xdg/autostart gives
    total 8
    -rw-r--r-- 1 root root 4831 Jan 26 23:53 nm-applet.desktop
    -rw-r--r-- 1 root root 2531 Jan 15 23:40 polkit-gnome-authentication-agent-1.desktop

    Does this tell you anything?
    I have no idea what this means.

  10. #20
    Senior Member registered user
    Join Date
    Feb 2010
    Posts
    198
    Yor second command has a typo: ls -l ./.config/autostart should be ls -l ~/.config/autostart
    And your 3rd command is wrong.

    Do it the following way:
    ls -l ~/.config/autostart
    ls -l /etc/xdg/autostart
    cat -n /etc/xdg/lxsession/LXDE/autostart

    The 3rd one is lxsession autostart file which probably contains 1 instance of polkit and I can see that you already have one in /etc/xdg/autostart/
    If cat -n /etc/xdg/lxsession/LXDE/autostart prints polkit line, then it is safe to delete
    /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop
    and
    /home/knoppix/.config/autostart/polkit-gnome-authentication-agent-1.desktop
    Only leave the starting line in /etc/xdg/lxsession/LXDE/autostart and you will be fine
    Last edited by mecho; 07-14-2010 at 12:03 AM.

Page 2 of 4 FirstFirst 1234 LastLast

Posting Permissions

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