Maximizing Terminal causes Xorg crash

Compiz, KDE, Gnome, Fluxbox, etc...

Moderator: Moderators

Post Reply
oliver
Baby Hen
Posts: 17
Joined: Sun Dec 31, 2006 20:43

Maximizing Terminal causes Xorg crash

Post by oliver » Tue Dec 18, 2012 14:14

This is a freshly installed Sabayon X Core edition running fluxbox with the auto-detected fglrx driver.

After letting equo update and upgrade whatever was out of date I installed Terminal which works fine until I maximize it. At that point, I'm taken back to the login prompt

Terminal is from x11-apps/terminal

Here's my Xorg.log file tailed during a crash

Code: Select all

[    97.992] Backtrace:
[    98.019] 0: /usr/bin/X (xorg_backtrace+0x34) [0x56add4]
[    98.019] 1: /usr/bin/X (0x400000+0x16eaa9) [0x56eaa9]
[    98.019] 2: /lib64/libpthread.so.0 (0x7fbd7a4f4000+0x10bf0) [0x7fbd7a504bf0]
[    98.019] 3: /usr/lib64/libpixman-1.so.0 (0x7fbd7a260000+0x79788) [0x7fbd7a2d9788]
[    98.019] 4: /usr/lib64/libpixman-1.so.0 (0x7fbd7a260000+0x79b0b) [0x7fbd7a2d9b0b]
[    98.019] 5: /usr/lib64/libpixman-1.so.0 (pixman_blt+0x52) [0x7fbd7a26b702]
[    98.019] 6: /usr/lib64/xorg/modules/libfb.so (fbCopyNtoN+0x2e9) [0x7fbd7644d459]
[    98.019] 7: /usr/lib64/xorg/modules/glesx.so (0x7fbd7459a000+0x8262d) [0x7fbd7461c62d]
[    98.019] 8: /usr/lib64/xorg/modules/glesx.so (0x7fbd7459a000+0x84736) [0x7fbd7461e736]
[    98.019] 9: /usr/bin/X (0x400000+0xf9c34) [0x4f9c34]
[    98.019] 10: /usr/bin/X (0x400000+0xc114d) [0x4c114d]
[    98.019] 11: /usr/bin/X (0x400000+0xc25e2) [0x4c25e2]
[    98.019] 12: /usr/bin/X (0x400000+0xbf3a2) [0x4bf3a2]
[    98.019] 13: /usr/bin/X (ConfigureWindow+0x222) [0x4618f2]
[    98.019] 14: /usr/bin/X (0x400000+0x31e4b) [0x431e4b]
[    98.019] 15: /usr/bin/X (0x400000+0x37391) [0x437391]
[    98.019] 16: /usr/bin/X (0x400000+0x2645a) [0x42645a]
[    98.019] 17: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7fbd793985dd]
[    98.019] 18: /usr/bin/X (0x400000+0x2674d) [0x42674d]
[    98.019] 
[    98.019] Segmentation fault at address 0x7fbd6de47ff8
[    98.019] 
Fatal server error:
[    98.019] Caught signal 11 (Segmentation fault). Server aborting
[    98.019] 
[    98.019] 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[    98.019] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    98.019] 
[    98.036] (II) evdev: Power Button: Close
[    98.036] (II) UnloadModule: "evdev"
[    98.052] (II) evdev: Video Bus: Close
[    98.052] (II) UnloadModule: "evdev"
[    98.068] (II) evdev: Sleep Button: Close
[    98.068] (II) UnloadModule: "evdev"
[    98.084] (II) evdev: USB USB Keykoard: Close
[    98.084] (II) UnloadModule: "evdev"
[    98.100] (II) evdev: USB USB Keykoard: Close
[    98.101] (II) UnloadModule: "evdev"
[    98.116] (II) evdev: Logitech USB Optical Mouse: Close
[    98.117] (II) UnloadModule: "evdev"
[    98.132] (II) evdev: AT Translated Set 2 keyboard: Close
[    98.132] (II) UnloadModule: "evdev"
[    98.165] (II) UnloadModule: "synaptics"
[    98.180] (II) evdev: HP WMI hotkeys: Close
[    98.180] (II) UnloadModule: "evdev"
[    98.180] (II) AIGLX: Suspending AIGLX clients for VT switch
[    98.189] (II) fglrx(0): Backup framebuffer data.
[    98.208] (II) fglrx(0): Backup complete.
[    99.359] Server terminated with error (1). Closing log file.
Any ideas? This can be reproduced every time

Jago25_98
Young Hen
Posts: 21
Joined: Sun Nov 20, 2011 22:18

Re: Maximizing Terminal causes Xorg crash

Post by Jago25_98 » Mon Jan 07, 2013 22:32

sorry don't want to get your hopes up that I can help as I'm useless but you could confirm that fglrx is the problem by trying a vanilla x driver (sorry can't remember the syntax)
Everytime someone helps me I give $5 to Sabayon. Hopefully this will speed up equo bandwidth. If someone has helped you, why not say thanks and donate to speed it up for all :-)

oliver
Baby Hen
Posts: 17
Joined: Sun Dec 31, 2006 20:43

Re: Maximizing Terminal causes Xorg crash

Post by oliver » Mon Jan 07, 2013 22:40

thanks for responding... easier for me to give up Terminal though :-) No other app seems to exhibit the same behaviour. Now using 'terminator' with no problems

Post Reply