! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
X is exiting with "Caught signal 4" since last update
Status:
RESOLVED: INVALID

Comments

Description Florian Le 2006-06-25 18:22:03 CEST
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060406 Firefox/1.5.0.4 (Debian-1.5.dfsg+1.5.0.4-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060406 Firefox/1.5.0.4 (Debian-1.5.dfsg+1.5.0.4-1)

Hi

Hope that I'm not looking for the wrong keywords, but I found nothing about this problem in the bugtracker or google.

I'm running Debian etch with 2.6.12 kernel on a terminal-server(AMD 2600+) - diskless-client system.

Last Saturday (17th) I upgraded both systems (server and client) with aptget dist-upgrade.
X is crashing on my client (Pentium 200Mhz, Xorg7.0.0) since that upgrade with "Caught signal 4" when I start xfce(4.2) and it is loading xfwm4, but other desktops like gnome, kde, fluxbox work without errors.
On other clients (Pentium2 and 3) it is working fine, even when I use the same root, so I exclude broken packages etc...

Even installed directy on the client-machine xfwm4 is not able to start (same error).

Even a downgrade to Xorg 6.9.0 and using old (100% working) backups on my client  doesn't have any effect, so the source of that problem must be someting on the server, but I don't understand how xfwm4 can cause a "signal 4" on the clients side.

I had compiled xorg from source for i586 to get sure that there are no incompabilities.

Is it possible, that any package in the apt-system (depending to xfce) is builded incorrecty f
Comment 1 Olivier Fourdan editbugs 2006-07-10 07:27:18 CEST
1: [0xffffe420]
2: /usr/lib/xorg/modules/libfb.so(fbCompositeCopyAreammx+0x60) [0xb78bec90]
3: /usr/lib/xorg/modules/libfb.so(fbComposite+0x53c) [0xb78b1a5c]
4: /usr/lib/xorg/modules/libxaa.so(XAAComposite+0x20e) [0xb786fbae]
5: X [0x8152c11]

The bug seem top occur in composite, which may explain why it doesn't show in other desktops (which don't implement a compositing manager).

First thing would be to disable compositing in xorg.conf (who needs compositing on a 200MHz system anyway?). BTW, if the X11 server crashes, it's a bug in the X11 server. It should never crash, whatever the client does.

HTH
Olivier.
Comment 2 Florian Le 2006-08-06 09:29:02 CEST
Hi Olivier.

OWW! I forgot to quote my xorg.conf, sorry!

Section "Files"
        FontPath        "unix/:7100"                    # local font server
        FontPath        "/usr/share/fonts/X11/misc"
        FontPath        "/usr/lib/X11/fonts/misc"
        FontPath        "/usr/share/fonts/X11/cyrillic"
        FontPath        "/usr/lib/X11/fonts/cyrillic"
        FontPath        "/usr/lib/X11/fonts/100dpi/:unscaled"
        FontPath        "/usr/lib/X11/fonts/75dpi/:unscaled"
        FontPath        "/usr/share/fonts/X11/Type1"
        FontPath        "/usr/lib/X11/fonts/Type1"
        FontPath        "/usr/share/fonts/X11/CID"
        FontPath        "/usr/lib/X11/fonts/CID"
        FontPath        "/usr/share/fonts/X11/100dpi"
        FontPath        "/usr/lib/X11/fonts/100dpi"
        FontPath        "/usr/share/fonts/X11/75dpi"
        FontPath        "/usr/lib/X11/fonts/75dpi"
EndSection

Section "Module"
        Load    "bitmap"
        Load    "dbe"
        Load    "ddc"
        Load    "dri"
        Load    "extmod"
        Load    "freetype"
        Load    "glx"
        Load    "int10"
        Load    "record"
        Load    "type1"
        Load    "v4l"
        Load    "vbe"
EndSection

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "keyboard"
        Option          "CoreKeyboard"
        Option          "XkbRules"      "xorg"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "de"
        Option          "XkbVariant"    "nodeadkeys"
        Option          "XkbOptions"    "nodeadkeys"
EndSection

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mice"
        Option          "Protocol"              "ImPS/2"
        Option          "Emulate3Buttons"       "true"
        Option          "ZAxisMapping"          "4 5"
EndSection

Section "Device"
        Identifier      "Standardgrafikkarte"
        Driver          "s3"
EndSection

Section "Monitor"
        Identifier      "Standardbildschirm"
        Option          "DPMS"
        HorizSync       28-49
        VertRefresh     43-72
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Device          "Standardgrafikkarte"
        Monitor         "Standardbildschirm"
        DefaultDepth    16
        SubSection "Display"
                Depth           1
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           4
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           8
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           15
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           16
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
        SubSection "Display"
                Depth           24
                Modes           "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

Section "ServerLayout"
        Identifier      "Default Layout"
        Screen          "Default Screen"
        InputDevice     "Generic Keyboard"
        InputDevice     "Configured Mouse"
EndSection

Section "DRI"
        Mode    0666
EndSection

Here is it.

> The bug seem top occur in composite, which may explain why it doesn't show in
> other desktops (which don't implement a compositing manager).
> First thing would be to disable compositing in xorg.conf (who needs compositing

Checking if composite is disabled is one of my first tries, but I still find no hints that it might be active?

> BTW, if the X11 server crashes, it's a bug in the
> X11 server. It should never crash, whatever the client does.

Thats true, but I thought that my problem is a bug "well known" by you or you are at least interested in the existance of it ;)


Thanks

Florian
Comment 3 Brian J. Tarricone (not reading bugmail) 2008-05-02 20:56:34 CEST
Definitely not our bug... presumably this is fixed upstream by now anyway.

Bug #1955

Reported by:
Florian Le
Reported on: 2006-06-25
Last modified on: 2009-07-14

People

Assignee:
Olivier Fourdan
CC List:
0 users

Version

Version:
unspecified

Attachments

Additional information