Re: AwesomeWM + Gvim resize crashes (segfault)

[Viacheslav Mikerov]

That does not necessarily occur only with awesome. I have the same problem
in awesome and in xfwm. And yes it is fair to assume that it is a vim bug.
You cannot do match. That seems like some memory access violation. And you
notice it more in awesome because, perhaps, more resizing is happening
there.

Best,
Slava

On Mon, May 2, 2016 at 9:41 PM, Jeroen Budts  wrote:

> On 04/30/2016 06:16 PM, Uli Schlachter wrote:
> > Hi,
> >
> > Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
> > [...]
> >> When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
> >> stderr.txt` I got the following in stdout.txt:
> >> RenderBadPicture (invalid Picture parameter)
> >> Vim: Got X error
> >> Vim: Finished.
> >>
> >> Any help on this is much appreciated.
> >
> > I know that this isn't helpful at all, but this sounds like a problem
> with GVim.
> > A BadPicture means that gvim sent a request to the X11 server to act on
> some
> > picture, but that picture does not exist (or is not suitable for this
> request
> > due to some other reason). The window manager has nothing to do with
> Pictures,
> > so hm.
>
> I certainly believe that it is probably a bug in Gvim (probably
> triggered by one of the plugins I use). I only find it strange that the
> issue occurs when running Gvim under Awesome, but not when running Gvim
> under Xmonad and (certainly) not when running xfwm4. So that obviously
> makes me wonder what is different about the gvim+awesome combination
> that triggers this...
>
> Jeroen
>
>
> --
> website: http://budts.be/ - twitter: @teranex
> ___
> Registered Linux User #482240 - GetFirefox.com - ubuntu.com
>
>
>

Re: AwesomeWM + Gvim resize crashes (segfault)

[Jeroen Budts]

On 04/30/2016 06:16 PM, Uli Schlachter wrote:
> Hi,
> 
> Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
> [...]
>> When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
>> stderr.txt` I got the following in stdout.txt:
>> RenderBadPicture (invalid Picture parameter)
>> Vim: Got X error
>> Vim: Finished.
>>
>> Any help on this is much appreciated.
> 
> I know that this isn't helpful at all, but this sounds like a problem with 
> GVim.
> A BadPicture means that gvim sent a request to the X11 server to act on some
> picture, but that picture does not exist (or is not suitable for this request
> due to some other reason). The window manager has nothing to do with Pictures,
> so hm.

I certainly believe that it is probably a bug in Gvim (probably
triggered by one of the plugins I use). I only find it strange that the
issue occurs when running Gvim under Awesome, but not when running Gvim
under Xmonad and (certainly) not when running xfwm4. So that obviously
makes me wonder what is different about the gvim+awesome combination
that triggers this...

Jeroen


-- 
website: http://budts.be/ - twitter: @teranex
___
Registered Linux User #482240 - GetFirefox.com - ubuntu.com




signature.asc
Description: OpenPGP digital signature

Re: AwesomeWM + Gvim resize crashes (segfault)

[Abraham Baker]

Also not helpful:  have you tried just using vim in xterm?  That works
great for me, but you might be using plugins/features that terminal vim
doesn't support.  But, if you are just using vanilla Gvim, then you might
consider giving terminal vim a try.

Abe

On Sat, Apr 30, 2016 at 11:16 AM, Uli Schlachter  wrote:

> Hi,
>
> Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
> [...]
> > When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
> > stderr.txt` I got the following in stdout.txt:
> > RenderBadPicture (invalid Picture parameter)
> > Vim: Got X error
> > Vim: Finished.
> >
> > Any help on this is much appreciated.
>
> I know that this isn't helpful at all, but this sounds like a problem with
> GVim.
> A BadPicture means that gvim sent a request to the X11 server to act on
> some
> picture, but that picture does not exist (or is not suitable for this
> request
> due to some other reason). The window manager has nothing to do with
> Pictures,
> so hm.
>
> The only recommendations that I can give is to try other (newer?) versions
> of
> gvim, gtk and cairo (the drawing library used by gtk).
>
> Sorry & good luck,
> Uli
> --
> Q: Because it reverses the logical flow of conversation.
> A: Why is putting a reply at the top of the message frowned upon?
>
> --
> To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
>

Re: AwesomeWM + Gvim resize crashes (segfault)

[Uli Schlachter]

Hi,

Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
[...]
> When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
> stderr.txt` I got the following in stdout.txt:
> RenderBadPicture (invalid Picture parameter)
> Vim: Got X error
> Vim: Finished.
> 
> Any help on this is much appreciated.

I know that this isn't helpful at all, but this sounds like a problem with GVim.
A BadPicture means that gvim sent a request to the X11 server to act on some
picture, but that picture does not exist (or is not suitable for this request
due to some other reason). The window manager has nothing to do with Pictures,
so hm.

The only recommendations that I can give is to try other (newer?) versions of
gvim, gtk and cairo (the drawing library used by gtk).

Sorry & good luck,
Uli
-- 
Q: Because it reverses the logical flow of conversation.
A: Why is putting a reply at the top of the message frowned upon?

-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

AwesomeWM + Gvim resize crashes (segfault)

[Jeroen Budts]

Hi all,

A few days ago I started using Awesome as my window manager (running
inside XFCE on xubuntu 15.10). The versions from the repository are
v3.5.6 (awesome) and 7.4.712 (gvim). I upgraded Awesome to 3.5.9 using a
ppa[1].
When Gvim gets resized, either because I resize the master-pane of
awesome, or simply by switching Awesome layout, Gvim will frequently
hang and/or crash.
From what I could find it seems to be a segfault, but I have no clue
what is causing this. In the past I have been using Gvim without any
problems with xfwm4 (default xfce window manager). I also tried xmonad
for a week where I didn't see these crashes when similarly resizing the
xmonad master-pane or switching layouts.

This is what I saw in the Ubuntu crash-submit tool:
 vim.gnome crashed with sigsegv in get_syntax_atttr()

When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
stderr.txt` I got the following in stdout.txt:
RenderBadPicture (invalid Picture parameter)
Vim: Got X error
Vim: Finished.

Any help on this is much appreciated.

[1] https://launchpad.net/~klaus-vormweg/+archive/ubuntu/awesome

Kind regards,
Jeroen

-- 
website: http://budts.be/ - twitter: @teranex
___
Registered Linux User #482240 - GetFirefox.com - ubuntu.com




signature.asc
Description: OpenPGP digital signature