Issue 584 in xmonad: Random crashes with vim running in Termite

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 584 in xmonad: Random crashes with vim running in Termite

codesite-noreply@google.com
Status: New
Owner: ----

New issue 584 by Svanti... at gmail.com: Random crashes with vim running in  
Termite
https://code.google.com/p/xmonad/issues/detail?id=584

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.

Attachments:
        xmonad.hs  150 bytes

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply | Threaded
Open this post in threaded view
|

Issue 584 in xmonad: Random crashes with vim running in Termite

codesite-noreply@google.com

Comment #1 on issue 584 by Svanti... at gmail.com: Random crashes with vim  
running in Termite
https://code.google.com/p/xmonad/issues/detail?id=584

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


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply | Threaded
Open this post in threaded view
|

Issue 584 in xmonad: Random crashes with vim running in Termite

codesite-noreply@google.com

Comment #2 on issue 584 by allber... at gmail.com: Random crashes with vim  
running in Termite
https://code.google.com/p/xmonad/issues/detail?id=584

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.)

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply | Threaded
Open this post in threaded view
|

Issue 584 in xmonad: Random crashes with vim running in Termite

codesite-noreply@google.com

Comment #3 on issue 584 by Svanti... at gmail.com: Random crashes with vim  
running in Termite
https://code.google.com/p/xmonad/issues/detail?id=584

Ah, I'll try to do something about drivers. Thanks for fast reply.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings