Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my Xsession. - X

This is a discussion on Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my Xsession. - X ; Hello, I would like to know if I am the only one with this issue or not. I recently discover how to reproduce my X session crash because of gkrellm-hdplop plugin in GKrellM v2.3.1. I basically loaded up GKrellM2 (doesn't ...

+ Reply to Thread
Results 1 to 9 of 9

Thread: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my Xsession.

  1. Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my Xsession.

    Hello,

    I would like to know if I am the only one with this issue or not. I
    recently discover how to reproduce my X session crash because of
    gkrellm-hdplop plugin in GKrellM v2.3.1.

    I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    customized) with gkrellm-hdplop plugin running only on ONE virtual
    desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    ctrl-alt-F# (# is a number like 1) to go back to console/text mode.

    It resulted a X crash like:
    Backtrace:
    0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    1: [0xffffe420]
    2: /usr/bin/X11/X [0x81771e0]
    3: /usr/bin/X11/X [0x814a8ba]
    4: /usr/bin/X11/X [0x814b504]
    5: /usr/bin/X11/X [0x8154c1e]
    6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]

    Fatal server error:
    Caught signal 11. Server aborting


    If I disable this neat colorful plugin, then I won't get the crash. I am
    just wondering if I am the only one with this problem. I am using Debian
    (Kernel 2.6.22-K7) and keep it updated daily.

    Thanks in advance.
    --
    "They are like the ant... They start one way and turn around and go the
    other way... They look all the time at the ground and never see the
    sky." --Davi Kopenawa Yanomami, Amazonian Indian (Newsweek 117(17):5, 1991)
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  2. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my X session.

    Ant wrote:
    > Hello,
    >
    > I would like to know if I am the only one with this issue or not. I
    > recently discover how to reproduce my X session crash because of
    > gkrellm-hdplop plugin in GKrellM v2.3.1.
    >
    > I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    > customized) with gkrellm-hdplop plugin running only on ONE virtual
    > desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    > virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    > ctrl-alt-F# (# is a number like 1) to go back to console/text mode.
    >
    > It resulted a X crash like:
    > Backtrace:
    > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    > 1: [0xffffe420]
    > 2: /usr/bin/X11/X [0x81771e0]
    > 3: /usr/bin/X11/X [0x814a8ba]
    > 4: /usr/bin/X11/X [0x814b504]
    > 5: /usr/bin/X11/X [0x8154c1e]
    > 6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    > 7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    > 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    > 9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]
    >
    > Fatal server error:
    > Caught signal 11. Server aborting
    >
    >
    > If I disable this neat colorful plugin, then I won't get the crash. I am
    > just wondering if I am the only one with this problem. I am using Debian
    > (Kernel 2.6.22-K7) and keep it updated daily.
    >
    > Thanks in advance.


    I wonder if this problem still occurs with: startx -- -dumbSched

    By default XFree86/X.org use a "smart scheduler" that uses SIGALRM
    periodically. You might try without that, even though you're
    experiencing a signal 11 which is a SIGSEGV.

    By the way, do any X developers know why dispatch.c doesn't use
    sig_atomic_t instead of the volatile char code? IMO sig_atomic_t is
    better for variables used in signal handlers.

    Try to get a debug build of the X.org X server. I think then you will
    be able to see symbol names for the addresses likes 0x81771e0 when
    xorg_backtrace() dumps the backtrace.

    From what I've read of configure.ac for xorg-server, it seems that you
    want ./configure --enable-debug

    The default is --prefix=/usr/local so you may want to backup your X11
    install, and then try ./configure --enable-debug --prefix=/usr


    George

  3. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my X session.

    Ant wrote:
    >> > I would like to know if I am the only one with this issue or not. I
    >> > recently discover how to reproduce my X session crash because of
    >> > gkrellm-hdplop plugin in GKrellM v2.3.1.
    >> >
    >> > I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    >> > customized) with gkrellm-hdplop plugin running only on ONE virtual
    >> > desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    >> > virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    >> > ctrl-alt-F# (# is a number like 1) to go back to console/text mode.
    >> >
    >> > It resulted a X crash like:
    >> > Backtrace:
    >> > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    >> > 1: [0xffffe420]
    >> > 2: /usr/bin/X11/X [0x81771e0]
    >> > 3: /usr/bin/X11/X [0x814a8ba]
    >> > 4: /usr/bin/X11/X [0x814b504]
    >> > 5: /usr/bin/X11/X [0x8154c1e]
    >> > 6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    >> > 7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    >> > 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    >> > 9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]
    >> >
    >> > Fatal server error:
    >> > Caught signal 11. Server aborting
    >> >
    >> >
    >> > If I disable this neat colorful plugin, then I won't get the crash. I am
    >> > just wondering if I am the only one with this problem. I am using Debian
    >> > (Kernel 2.6.22-K7) and keep it updated daily.
    >> >
    >> > Thanks in advance.

    >
    >> I wonder if this problem still occurs with: startx -- -dumbSched

    >
    >> By default XFree86/X.org use a "smart scheduler" that uses SIGALRM
    >> periodically. You might try without that, even though you're
    >> experiencing a signal 11 which is a SIGSEGV.

    >
    > I will try that later since I am at work can't try it now.
    >
    >
    >> By the way, do any X developers know why dispatch.c doesn't use
    >> sig_atomic_t instead of the volatile char code? IMO sig_atomic_t is
    >> better for variables used in signal handlers.

    >
    >> Try to get a debug build of the X.org X server. I think then you will
    >> be able to see symbol names for the addresses likes 0x81771e0 when
    >> xorg_backtrace() dumps the backtrace.

    >
    >> From what I've read of configure.ac for xorg-server, it seems that you
    >> want ./configure --enable-debug

    >
    >> The default is --prefix=/usr/local so you may want to backup your X11
    >> install, and then try ./configure --enable-debug --prefix=/usr

    >
    > Do I have to compile to do this? I install and use packages from apt-get
    > command. Will any of these debug packages (e.g., xserver-xorg-core-dbg)
    > work do?


    see below

    > $ apt-cache search xorg |grep debug
    > libdmx1-dbg - X11 Distributed Multihead library (debug package)
    > libfontenc1-dbg - X11 font encoding library (debug package)
    > libfs6-dbg - X11 Font Services library (debug package)
    > libice6-dbg - X11 Inter-Client Exchange library (debug package)
    > libsm6-dbg - X11 Inter-Client Exchange library (debug package)
    > libx11-6-dbg - X11 client-side library (debug package)
    > libxau6-dbg - X11 authorisation library (debug package)
    > libxaw6-dbg - X11 Athena Widget library (debug package)
    > libxaw7-dbg - X11 Athena Widget library (debug package)
    > libxcomposite1-dbg - X11 Composite extension library (debug package)
    > libxdamage1-dbg - X11 damaged region extension library (debug package)
    > libxdmcp6-dbg - X11 authorisation library (debug package)
    > libxevie1-dbg - X11 EvIE extension library (debug package)
    > libxext6-dbg - X11 miscellaneous extensions library (debug package)
    > libxfixes3-dbg - X11 miscellaneous 'fixes' extension library (debug package)
    > libxfont1-dbg - X11 font rasterisation library (debug package)
    > libxi6-dbg - X11 Input extension library (debug package)
    > libxinerama1-dbg - X11 Xinerama extension library (debug package)
    > libxkbfile1-dbg - X11 keyboard file manipulation library (debug package)
    > libxkbui1-dbg - X11 keyboard UI presentation library (debug package)
    > libxmu6-dbg - X11 miscellaneous utility library (debug package)
    > libxmuu1-dbg - X11 miscellaneous micro-utility library (debug package)
    > libxpm4-dbg - X11 pixmap library (debug package)
    > libxrandr2-dbg - X11 RandR extension library (debug package)
    > libxres1-dbg - X11 Resource extension library (debug package)
    > libxss1-dbg - X11 Screen Saver extension library (debug package)
    > libxt6-dbg - X11 toolkit intrinsics library (debug package)
    > libxtrap6-dbg - X11 event trapping extension library (debug package)
    > libxtst6-dbg - X11 Record extension library (debug package)
    > libxv1-dbg - X11 Video extension library (debug package)
    > libxvmc1-dbg - X11 Video extension library (debug package)
    > libxxf86dga1-dbg - X11 Direct Graphics Access extension library (debug package)
    > libxxf86misc1-dbg - X11 XFree86 miscellaneous extension library (debug package)
    > libxxf86vm1-dbg - X11 XFree86 video mode extension library (debug package)
    > xserver-xorg-video-amd-dbg - X.Org X server -- AMD Geode GX/LX display driver (debugging symbols)
    > xserver-xorg-video-intel-dbg - X.Org X server -- Intel i8xx, i9xx display driver (debugging symbols)
    > xserver-xorg-core-dbg - Xorg - the X.Org X server (debugging symbols)
    >
    > If so, then do I just install all of these and do my normal startx,
    > reproduce the crash, and gather the crash dumps (where will they
    > located?)? Thanks in advance.



    Using a debug version of xserver-xorg-core-dbg combined with your video
    driver -dbg package, should be enough. Most of the lib packages you
    mentioned I believe are not part of the X server, and are primarily used
    by clients.


    George

  4. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my X session.

    > >> > I would like to know if I am the only one with this issue or not. I
    > >> > recently discover how to reproduce my X session crash because of
    > >> > gkrellm-hdplop plugin in GKrellM v2.3.1.
    > >> >
    > >> > I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    > >> > customized) with gkrellm-hdplop plugin running only on ONE virtual
    > >> > desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    > >> > virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    > >> > ctrl-alt-F# (# is a number like 1) to go back to console/text mode.
    > >> >
    > >> > It resulted a X crash like:
    > >> > Backtrace:
    > >> > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    > >> > 1: [0xffffe420]
    > >> > 2: /usr/bin/X11/X [0x81771e0]
    > >> > 3: /usr/bin/X11/X [0x814a8ba]
    > >> > 4: /usr/bin/X11/X [0x814b504]
    > >> > 5: /usr/bin/X11/X [0x8154c1e]
    > >> > 6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    > >> > 7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    > >> > 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    > >> > 9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]
    > >> >
    > >> > Fatal server error:
    > >> > Caught signal 11. Server aborting
    > >> >
    > >> >
    > >> > If I disable this neat colorful plugin, then I won't get the crash. I am
    > >> > just wondering if I am the only one with this problem. I am using Debian
    > >> > (Kernel 2.6.22-K7) and keep it updated daily.
    > >> >
    > >> > Thanks in advance.

    > >
    > >> I wonder if this problem still occurs with: startx -- -dumbSched

    > >
    > >> By default XFree86/X.org use a "smart scheduler" that uses SIGALRM
    > >> periodically. You might try without that, even though you're
    > >> experiencing a signal 11 which is a SIGSEGV.

    > >
    > > I will try that later since I am at work can't try it now.
    > >
    > >
    > >> By the way, do any X developers know why dispatch.c doesn't use
    > >> sig_atomic_t instead of the volatile char code? IMO sig_atomic_t is
    > >> better for variables used in signal handlers.

    > >
    > >> Try to get a debug build of the X.org X server. I think then you will
    > >> be able to see symbol names for the addresses likes 0x81771e0 when
    > >> xorg_backtrace() dumps the backtrace.

    > >
    > >> From what I've read of configure.ac for xorg-server, it seems that you
    > >> want ./configure --enable-debug

    > >
    > >> The default is --prefix=/usr/local so you may want to backup your X11
    > >> install, and then try ./configure --enable-debug --prefix=/usr

    > >
    > > Do I have to compile to do this? I install and use packages from apt-get
    > > command. Will any of these debug packages (e.g., xserver-xorg-core-dbg)
    > > work do?


    > see below


    > > $ apt-cache search xorg |grep debug
    > > libdmx1-dbg - X11 Distributed Multihead library (debug package)
    > > libfontenc1-dbg - X11 font encoding library (debug package)
    > > libfs6-dbg - X11 Font Services library (debug package)
    > > libice6-dbg - X11 Inter-Client Exchange library (debug package)
    > > libsm6-dbg - X11 Inter-Client Exchange library (debug package)
    > > libx11-6-dbg - X11 client-side library (debug package)
    > > libxau6-dbg - X11 authorisation library (debug package)
    > > libxaw6-dbg - X11 Athena Widget library (debug package)
    > > libxaw7-dbg - X11 Athena Widget library (debug package)
    > > libxcomposite1-dbg - X11 Composite extension library (debug package)
    > > libxdamage1-dbg - X11 damaged region extension library (debug package)
    > > libxdmcp6-dbg - X11 authorisation library (debug package)
    > > libxevie1-dbg - X11 EvIE extension library (debug package)
    > > libxext6-dbg - X11 miscellaneous extensions library (debug package)
    > > libxfixes3-dbg - X11 miscellaneous 'fixes' extension library (debug package)
    > > libxfont1-dbg - X11 font rasterisation library (debug package)
    > > libxi6-dbg - X11 Input extension library (debug package)
    > > libxinerama1-dbg - X11 Xinerama extension library (debug package)
    > > libxkbfile1-dbg - X11 keyboard file manipulation library (debug package)
    > > libxkbui1-dbg - X11 keyboard UI presentation library (debug package)
    > > libxmu6-dbg - X11 miscellaneous utility library (debug package)
    > > libxmuu1-dbg - X11 miscellaneous micro-utility library (debug package)
    > > libxpm4-dbg - X11 pixmap library (debug package)
    > > libxrandr2-dbg - X11 RandR extension library (debug package)
    > > libxres1-dbg - X11 Resource extension library (debug package)
    > > libxss1-dbg - X11 Screen Saver extension library (debug package)
    > > libxt6-dbg - X11 toolkit intrinsics library (debug package)
    > > libxtrap6-dbg - X11 event trapping extension library (debug package)
    > > libxtst6-dbg - X11 Record extension library (debug package)
    > > libxv1-dbg - X11 Video extension library (debug package)
    > > libxvmc1-dbg - X11 Video extension library (debug package)
    > > libxxf86dga1-dbg - X11 Direct Graphics Access extension library (debug package)
    > > libxxf86misc1-dbg - X11 XFree86 miscellaneous extension library (debug package)
    > > libxxf86vm1-dbg - X11 XFree86 video mode extension library (debug package)
    > > xserver-xorg-video-amd-dbg - X.Org X server -- AMD Geode GX/LX display driver (debugging symbols)
    > > xserver-xorg-video-intel-dbg - X.Org X server -- Intel i8xx, i9xx display driver (debugging symbols)
    > > xserver-xorg-core-dbg - Xorg - the X.Org X server (debugging symbols)
    > >
    > > If so, then do I just install all of these and do my normal startx,
    > > reproduce the crash, and gather the crash dumps (where will they
    > > located?)? Thanks in advance.


    > Using a debug version of xserver-xorg-core-dbg combined with your video
    > driver -dbg package, should be enough. Most of the lib packages you
    > mentioned I believe are not part of the X server, and are primarily used
    > by clients.


    Wait, I can't use the compiled NVIDIA binary driver (from
    NVIDIA-Linux-x86-169.12-pkg1.run) for this debug? That gives me a new
    idea. I wonder if X still crashes if I don't use NVIDIA's closed binary
    driver. I will try that later too!
    --
    "I've been on some fairways that are as good as the greens we putted on
    back then. We had crab grass. I remember one green where I putted
    through ants." --Sam Snead
    /\___/\
    / /\ /\ \ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Please remove ANT if replying by e-mail.
    ( )

  5. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my X session.

    Ant wrote:
    >> >> > I would like to know if I am the only one with this issue or not. I
    >> >> > recently discover how to reproduce my X session crash because of
    >> >> > gkrellm-hdplop plugin in GKrellM v2.3.1.
    >> >> >
    >> >> > I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    >> >> > customized) with gkrellm-hdplop plugin running only on ONE virtual
    >> >> > desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    >> >> > virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    >> >> > ctrl-alt-F# (# is a number like 1) to go back to console/text mode.
    >> >> >
    >> >> > It resulted a X crash like:
    >> >> > Backtrace:
    >> >> > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    >> >> > 1: [0xffffe420]
    >> >> > 2: /usr/bin/X11/X [0x81771e0]
    >> >> > 3: /usr/bin/X11/X [0x814a8ba]
    >> >> > 4: /usr/bin/X11/X [0x814b504]
    >> >> > 5: /usr/bin/X11/X [0x8154c1e]
    >> >> > 6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    >> >> > 7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    >> >> > 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    >> >> > 9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]
    >> >> >
    >> >> > Fatal server error:
    >> >> > Caught signal 11. Server aborting
    >> >> >
    >> >> >
    >> >> > If I disable this neat colorful plugin, then I won't get the crash. I am
    >> >> > just wondering if I am the only one with this problem. I am using Debian
    >> >> > (Kernel 2.6.22-K7) and keep it updated daily.
    >> >> >
    >> >> > Thanks in advance.
    >> >
    >> >> I wonder if this problem still occurs with: startx -- -dumbSched
    >> >
    >> >> By default XFree86/X.org use a "smart scheduler" that uses SIGALRM
    >> >> periodically. You might try without that, even though you're
    >> >> experiencing a signal 11 which is a SIGSEGV.
    >> >
    >> > I will try that later since I am at work can't try it now.
    >> >
    >> >
    >> >> By the way, do any X developers know why dispatch.c doesn't use
    >> >> sig_atomic_t instead of the volatile char code? IMO sig_atomic_t is
    >> >> better for variables used in signal handlers.
    >> >
    >> >> Try to get a debug build of the X.org X server. I think then you will
    >> >> be able to see symbol names for the addresses likes 0x81771e0 when
    >> >> xorg_backtrace() dumps the backtrace.
    >> >
    >> >> From what I've read of configure.ac for xorg-server, it seems that you
    >> >> want ./configure --enable-debug
    >> >
    >> >> The default is --prefix=/usr/local so you may want to backup your X11
    >> >> install, and then try ./configure --enable-debug --prefix=/usr
    >> >
    >> > Do I have to compile to do this? I install and use packages from apt-get
    >> > command. Will any of these debug packages (e.g., xserver-xorg-core-dbg)
    >> > work do?

    >
    >> see below

    >
    >> > $ apt-cache search xorg |grep debug
    >> > libdmx1-dbg - X11 Distributed Multihead library (debug package)
    >> > libfontenc1-dbg - X11 font encoding library (debug package)
    >> > libfs6-dbg - X11 Font Services library (debug package)
    >> > libice6-dbg - X11 Inter-Client Exchange library (debug package)
    >> > libsm6-dbg - X11 Inter-Client Exchange library (debug package)
    >> > libx11-6-dbg - X11 client-side library (debug package)
    >> > libxau6-dbg - X11 authorisation library (debug package)
    >> > libxaw6-dbg - X11 Athena Widget library (debug package)
    >> > libxaw7-dbg - X11 Athena Widget library (debug package)
    >> > libxcomposite1-dbg - X11 Composite extension library (debug package)
    >> > libxdamage1-dbg - X11 damaged region extension library (debug package)
    >> > libxdmcp6-dbg - X11 authorisation library (debug package)
    >> > libxevie1-dbg - X11 EvIE extension library (debug package)
    >> > libxext6-dbg - X11 miscellaneous extensions library (debug package)
    >> > libxfixes3-dbg - X11 miscellaneous 'fixes' extension library (debug package)
    >> > libxfont1-dbg - X11 font rasterisation library (debug package)
    >> > libxi6-dbg - X11 Input extension library (debug package)
    >> > libxinerama1-dbg - X11 Xinerama extension library (debug package)
    >> > libxkbfile1-dbg - X11 keyboard file manipulation library (debug package)
    >> > libxkbui1-dbg - X11 keyboard UI presentation library (debug package)
    >> > libxmu6-dbg - X11 miscellaneous utility library (debug package)
    >> > libxmuu1-dbg - X11 miscellaneous micro-utility library (debug package)
    >> > libxpm4-dbg - X11 pixmap library (debug package)
    >> > libxrandr2-dbg - X11 RandR extension library (debug package)
    >> > libxres1-dbg - X11 Resource extension library (debug package)
    >> > libxss1-dbg - X11 Screen Saver extension library (debug package)
    >> > libxt6-dbg - X11 toolkit intrinsics library (debug package)
    >> > libxtrap6-dbg - X11 event trapping extension library (debug package)
    >> > libxtst6-dbg - X11 Record extension library (debug package)
    >> > libxv1-dbg - X11 Video extension library (debug package)
    >> > libxvmc1-dbg - X11 Video extension library (debug package)
    >> > libxxf86dga1-dbg - X11 Direct Graphics Access extension library (debug package)
    >> > libxxf86misc1-dbg - X11 XFree86 miscellaneous extension library (debug package)
    >> > libxxf86vm1-dbg - X11 XFree86 video mode extension library (debug package)
    >> > xserver-xorg-video-amd-dbg - X.Org X server -- AMD Geode GX/LX display driver (debugging symbols)
    >> > xserver-xorg-video-intel-dbg - X.Org X server -- Intel i8xx, i9xx display driver (debugging symbols)
    >> > xserver-xorg-core-dbg - Xorg - the X.Org X server (debugging symbols)
    >> >
    >> > If so, then do I just install all of these and do my normal startx,
    >> > reproduce the crash, and gather the crash dumps (where will they
    >> > located?)? Thanks in advance.

    >
    >> Using a debug version of xserver-xorg-core-dbg combined with your video
    >> driver -dbg package, should be enough. Most of the lib packages you
    >> mentioned I believe are not part of the X server, and are primarily used
    >> by clients.

    >
    > Wait, I can't use the compiled NVIDIA binary driver (from
    > NVIDIA-Linux-x86-169.12-pkg1.run) for this debug? That gives me a new
    > idea. I wonder if X still crashes if I don't use NVIDIA's closed binary
    > driver. I will try that later too!



    You can use the NVIDIA driver, but the backtrace may not be as useful.
    It depends on what part of the code is causing the SIGSEGV. It probably
    wouldn't hurt to try with and without the NVIDIA binary driver. You
    should be able to use the nv driver from X.org.


    George

  6. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes my X session.

    > >> >> > I would like to know if I am the only one with this issue or not. I
    > >> >> > recently discover how to reproduce my X session crash because of
    > >> >> > gkrellm-hdplop plugin in GKrellM v2.3.1.
    > >> >> >
    > >> >> > I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    > >> >> > customized) with gkrellm-hdplop plugin running only on ONE virtual
    > >> >> > desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    > >> >> > virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    > >> >> > ctrl-alt-F# (# is a number like 1) to go back to console/text mode.
    > >> >> >
    > >> >> > It resulted a X crash like:
    > >> >> > Backtrace:
    > >> >> > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    > >> >> > 1: [0xffffe420]
    > >> >> > 2: /usr/bin/X11/X [0x81771e0]
    > >> >> > 3: /usr/bin/X11/X [0x814a8ba]
    > >> >> > 4: /usr/bin/X11/X [0x814b504]
    > >> >> > 5: /usr/bin/X11/X [0x8154c1e]
    > >> >> > 6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    > >> >> > 7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    > >> >> > 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    > >> >> > 9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]
    > >> >> >
    > >> >> > Fatal server error:
    > >> >> > Caught signal 11. Server aborting
    > >> >> >
    > >> >> >
    > >> >> > If I disable this neat colorful plugin, then I won't get the crash. I am
    > >> >> > just wondering if I am the only one with this problem. I am using Debian
    > >> >> > (Kernel 2.6.22-K7) and keep it updated daily.
    > >> >> >
    > >> >> > Thanks in advance.
    > >> >
    > >> >> I wonder if this problem still occurs with: startx -- -dumbSched
    > >> >
    > >> >> By default XFree86/X.org use a "smart scheduler" that uses SIGALRM
    > >> >> periodically. You might try without that, even though you're
    > >> >> experiencing a signal 11 which is a SIGSEGV.
    > >> >
    > >> > I will try that later since I am at work can't try it now.
    > >> >
    > >> >
    > >> >> By the way, do any X developers know why dispatch.c doesn't use
    > >> >> sig_atomic_t instead of the volatile char code? IMO sig_atomic_t is
    > >> >> better for variables used in signal handlers.
    > >> >
    > >> >> Try to get a debug build of the X.org X server. I think then you will
    > >> >> be able to see symbol names for the addresses likes 0x81771e0 when
    > >> >> xorg_backtrace() dumps the backtrace.
    > >> >
    > >> >> From what I've read of configure.ac for xorg-server, it seems that you
    > >> >> want ./configure --enable-debug
    > >> >
    > >> >> The default is --prefix=/usr/local so you may want to backup your X11
    > >> >> install, and then try ./configure --enable-debug --prefix=/usr
    > >> >
    > >> > Do I have to compile to do this? I install and use packages from apt-get
    > >> > command. Will any of these debug packages (e.g., xserver-xorg-core-dbg)
    > >> > work do?

    > >
    > >> see below

    > >
    > >> > $ apt-cache search xorg |grep debug
    > >> > libdmx1-dbg - X11 Distributed Multihead library (debug package)
    > >> > libfontenc1-dbg - X11 font encoding library (debug package)
    > >> > libfs6-dbg - X11 Font Services library (debug package)
    > >> > libice6-dbg - X11 Inter-Client Exchange library (debug package)
    > >> > libsm6-dbg - X11 Inter-Client Exchange library (debug package)
    > >> > libx11-6-dbg - X11 client-side library (debug package)
    > >> > libxau6-dbg - X11 authorisation library (debug package)
    > >> > libxaw6-dbg - X11 Athena Widget library (debug package)
    > >> > libxaw7-dbg - X11 Athena Widget library (debug package)
    > >> > libxcomposite1-dbg - X11 Composite extension library (debug package)
    > >> > libxdamage1-dbg - X11 damaged region extension library (debug package)
    > >> > libxdmcp6-dbg - X11 authorisation library (debug package)
    > >> > libxevie1-dbg - X11 EvIE extension library (debug package)
    > >> > libxext6-dbg - X11 miscellaneous extensions library (debug package)
    > >> > libxfixes3-dbg - X11 miscellaneous 'fixes' extension library (debug package)
    > >> > libxfont1-dbg - X11 font rasterisation library (debug package)
    > >> > libxi6-dbg - X11 Input extension library (debug package)
    > >> > libxinerama1-dbg - X11 Xinerama extension library (debug package)
    > >> > libxkbfile1-dbg - X11 keyboard file manipulation library (debug package)
    > >> > libxkbui1-dbg - X11 keyboard UI presentation library (debug package)
    > >> > libxmu6-dbg - X11 miscellaneous utility library (debug package)
    > >> > libxmuu1-dbg - X11 miscellaneous micro-utility library (debug package)
    > >> > libxpm4-dbg - X11 pixmap library (debug package)
    > >> > libxrandr2-dbg - X11 RandR extension library (debug package)
    > >> > libxres1-dbg - X11 Resource extension library (debug package)
    > >> > libxss1-dbg - X11 Screen Saver extension library (debug package)
    > >> > libxt6-dbg - X11 toolkit intrinsics library (debug package)
    > >> > libxtrap6-dbg - X11 event trapping extension library (debug package)
    > >> > libxtst6-dbg - X11 Record extension library (debug package)
    > >> > libxv1-dbg - X11 Video extension library (debug package)
    > >> > libxvmc1-dbg - X11 Video extension library (debug package)
    > >> > libxxf86dga1-dbg - X11 Direct Graphics Access extension library (debug package)
    > >> > libxxf86misc1-dbg - X11 XFree86 miscellaneous extension library (debug package)
    > >> > libxxf86vm1-dbg - X11 XFree86 video mode extension library (debug package)
    > >> > xserver-xorg-video-amd-dbg - X.Org X server -- AMD Geode GX/LX display driver (debugging symbols)
    > >> > xserver-xorg-video-intel-dbg - X.Org X server -- Intel i8xx, i9xx display driver (debugging symbols)
    > >> > xserver-xorg-core-dbg - Xorg - the X.Org X server (debugging symbols)
    > >> >
    > >> > If so, then do I just install all of these and do my normal startx,
    > >> > reproduce the crash, and gather the crash dumps (where will they
    > >> > located?)? Thanks in advance.

    > >
    > >> Using a debug version of xserver-xorg-core-dbg combined with your video
    > >> driver -dbg package, should be enough. Most of the lib packages you
    > >> mentioned I believe are not part of the X server, and are primarily used
    > >> by clients.

    > >
    > > Wait, I can't use the compiled NVIDIA binary driver (from
    > > NVIDIA-Linux-x86-169.12-pkg1.run) for this debug? That gives me a new
    > > idea. I wonder if X still crashes if I don't use NVIDIA's closed binary
    > > driver. I will try that later too!


    > You can use the NVIDIA driver, but the backtrace may not be as useful.
    > It depends on what part of the code is causing the SIGSEGV. It probably
    > wouldn't hurt to try with and without the NVIDIA binary driver. You
    > should be able to use the nv driver from X.org.


    OK. Will this backtrace be on screen or in a log with debug one? I
    assume debug would be enabled automatically after installing
    xserver-xorg-core-dbg package and when I run startx command.
    --
    "I've been on some fairways that are as good as the greens we putted on
    back then. We had crab grass. I remember one green where I putted
    through ants." --Sam Snead
    /\___/\
    / /\ /\ \ Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Please remove ANT if replying by e-mail.
    ( )

  7. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashesmy X session.

    OK... I am starting to think this is NVIDIA's fault. I went back to nv
    driver by renaming /etc/X11/xorg.conf and run startx. I tried to
    reproduce the problem and no crash with gkrellm-hdplop plugin! I am
    going to report this to NVIDIA via e-mail and the forum.

    Is it me or is NVIDIA driver getting buggy in Linux like in Windows?


    On 3/10/2008 10:42 PM PT, Ant typed:

    > I would like to know if I am the only one with this issue or not. I
    > recently discover how to reproduce my X session crash because of
    > gkrellm-hdplop plugin in GKrellM v2.3.1.
    >
    > I basically loaded up GKrellM2 (doesn't matter if it uses defaults or
    > customized) with gkrellm-hdplop plugin running only on ONE virtual
    > desktop in KDE v3.5.8 or Gnome v2.14.3. Then, I switched to another
    > virtual desktop that didn't have GKrellM on screen. Finally, I pressed
    > ctrl-alt-F# (# is a number like 1) to go back to console/text mode.
    >
    > It resulted a X crash like:
    > Backtrace:
    > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c89c1]
    > 1: [0xffffe420]
    > 2: /usr/bin/X11/X [0x81771e0]
    > 3: /usr/bin/X11/X [0x814a8ba]
    > 4: /usr/bin/X11/X [0x814b504]
    > 5: /usr/bin/X11/X [0x8154c1e]
    > 6: /usr/bin/X11/X(Dispatch+0x1a1) [0x808eff1]
    > 7: /usr/bin/X11/X(main+0x47e) [0x8076e2e]
    > 8: /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5450]
    > 9: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e9) [0x80761b1]
    >
    > Fatal server error:
    > Caught signal 11. Server aborting
    >
    >
    > If I disable this neat colorful plugin, then I won't get the crash. I am
    > just wondering if I am the only one with this problem. I am using Debian
    > (Kernel 2.6.22-K7) and keep it updated daily.

    --
    "Since the world began, we have never exterminated. We probably shall
    never exterminate as much as one single insect species. If there was
    ever an example of an insect we cannot destroy, the fire ant is it."
    --an entomologist quote mentioned by Leonard Nimoy on In The Search Of:
    Deadly Ants (1978)
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

  8. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashes myX session.

    Ant writes:

    > On 3/10/2008 10:42 PM PT, Ant typed:
    >
    >> I would like to know if I am the only one with this issue or not. I
    >> recently discover how to reproduce my X session crash because of
    >> gkrellm-hdplop plugin in GKrellM v2.3.1.

    ....top posting fixed... once.
    > OK... I am starting to think this is NVIDIA's fault. I went back to nv
    > driver by renaming /etc/X11/xorg.conf and run startx. I tried to
    > reproduce the problem and no crash with gkrellm-hdplop plugin! I am
    > going to report this to NVIDIA via e-mail and the forum.
    >
    > Is it me or is NVIDIA driver getting buggy in Linux like in Windows?


    As far as I can tell, the NVIDIA driver for Linux shares code
    with the Windows driver. Look at the version numbers.

    As for bugs, read the forums. Hell yeah there are bugs.
    The good news is, if you post the bug to the forums,
    you might find a work around and eventually it will get fixed.

  9. Re: Using gkrellm-hdplop plugin and ctrl-alt-F# together crashesmy X session.

    On 3/12/2008 7:54 AM PT, Dan Espen typed:

    >>> I would like to know if I am the only one with this issue or not. I
    >>> recently discover how to reproduce my X session crash because of
    >>> gkrellm-hdplop plugin in GKrellM v2.3.1.

    >>
    >> OK... I am starting to think this is NVIDIA's fault. I went back to nv
    >> driver by renaming /etc/X11/xorg.conf and run startx. I tried to
    >> reproduce the problem and no crash with gkrellm-hdplop plugin! I am
    >> going to report this to NVIDIA via e-mail and the forum.
    >>
    >> Is it me or is NVIDIA driver getting buggy in Linux like in Windows?

    >
    > As far as I can tell, the NVIDIA driver for Linux shares code
    > with the Windows driver. Look at the version numbers.
    >
    > As for bugs, read the forums. Hell yeah there are bugs.
    > The good news is, if you post the bug to the forums,
    > you might find a work around and eventually it will get fixed.


    Well, so far nothing in my post from yesterday:
    http://www.nvnews.net/vbulletin/show....php?p=1589973
    --
    "... Let's go pour these (peas from a can) onto an anthill I've found."
    --Strong Bad (Witness the Cheatar! episode)
    /\___/\
    / /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
    | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
    \ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
    ( ) or ANTant@zimage.com
    Ant is currently not listening to any songs on his home computer.

+ Reply to Thread