search

codehenry / xmonad

Automatically exported from code.google.com/p/xmonad
0 stars 0 forks source link

Random crashes with vim running in Termite #584

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

Open Termite and console vim in it. Enable jedi-vim plugin and edit some Python 
source code. When code-completion pops up, select anything and hit Enter to 
accept. From time to time XMonad will crash. Very hard to tell when it happens, 
because it sometimes does and sometimes not. Tried hard to investigate more, 
but with no results.

In system console outside X-server jedi-vim runs with no problem.

What version of the product are you using? On what operating system?

Arch Linux x86_64, vim 7.4, jedi-vim plugin and XMonad 0.11 from official Arch 
repositories. GHC version: 7.8.3.

Are you using an xmonad.hs?  Please attach it and the output of "xmonad
--recompile".

$ xmonad --recompile gives no output.

Original issue reported on code.google.com by Svanti...@gmail.com on 23 Dec 2014 at 8:59

Attachments:

GoogleCodeExporter commented 8 years ago 
Termite of course also is installed from official repositories. It might be 
important that in Xorg error logs at /var/log/Xorg.0.log the following message 
appears:

[ 12615.413] (EE) Backtrace:
[ 12615.413] (EE) 0: /usr/bin/Xorg.bin (xorg_backtrace+0x56) [0x594186]
[ 12615.413] (EE) 1: /usr/bin/Xorg.bin (0x400000+0x1982d9) [0x5982d9]
[ 12615.413] (EE) 2: /usr/lib/libc.so.6 (0x7f942d3e0000+0x33b20) 
[0x7f942d413b20]
[ 12615.413] (EE) 
[ 12615.413] (EE) Segmentation fault at address 0x0
[ 12615.413] (EE) 
Fatal server error:
[ 12615.413] (EE) Caught signal 11 (Segmentation fault). Server aborting

Original comment by Svanti...@gmail.com on 23 Dec 2014 at 9:04

GoogleCodeExporter commented 8 years ago 
Sadly, that's not xmonad; it's the X server itself segfaulting. Usually this 
means a bug in the display driver.

(People often think that the window manager handles drawing into windows, but 
all it handles is window placement and sizing policy; drawing, event 
processing, etc. is between the client and the X server itself.)

Original comment by allber...@gmail.com on 23 Dec 2014 at 9:07

GoogleCodeExporter commented 8 years ago 
Ah, I'll try to do something about drivers. Thanks for fast reply.

Original comment by Svanti...@gmail.com on 24 Dec 2014 at 11:09