Bug 19653

Summary: Running gvim emits many warnings and results in a mal-functioning window.
Product: Mageia Reporter: Shlomi Fish <shlomif>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: guillomovitch, marja11
Version: CauldronKeywords: UPSTREAM
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
URL: https://bugzilla.gnome.org/show_bug.cgi?id=773387
Whiteboard:
Source RPM: vim-8.0.5-3.mga6.src.rpm CVE:
Status comment:

Description Shlomi Fish 2016-10-25 16:46:41 CEST
Description of problem:

On jwm/plasma5, including as a new user, running "gvim" from the command line causes it to emit many warnings and results in a mal-functioning and unusable window (with a usable menu). I am getting this:

shlomif@telaviv1:~$ gvim
shlomif@telaviv1:~$ 
(gvim:20740): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed

(gvim:20740): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed

(gvim:20740): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed
                                                                                
(gvim:20740): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion 'width >= -1' failed                                                                      
*** BUG ***                                                                     
In pixman_region32_init_rect: Invalid rectangle passed                          
Set a breakpoint on '_pixman_log_error' to debug                                
                                                                                
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
Comment 1 Shlomi Fish 2016-10-25 18:28:23 CEST
Some more recent notes:

1. The same problem is exhibited with vim from git master when compiled against gtk+3. When compiled against gtk+2, it is fine.

2. downgrading the gtk+3.0 packages to 3.22.1 fixes the symptoms of the problem for both gvims.
Samuel Verschelde 2016-10-26 09:48:11 CEST

Keywords: (none) => UPSTREAM

Comment 2 Marja Van Waes 2016-10-26 13:30:58 CEST
@ Shlomi

Is there an upstream bug report?

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud

Comment 3 Shlomi Fish 2016-10-26 14:25:31 CEST
(In reply to Marja van Waes from comment #2)
> @ Shlomi
> 
> Is there an upstream bug report?

I don't know - I didn't report one.
Comment 4 Shlomi Fish 2016-10-26 14:29:26 CEST
(In reply to Shlomi Fish from comment #3)
> (In reply to Marja van Waes from comment #2)
> > @ Shlomi
> > 
> > Is there an upstream bug report?
> 
> I don't know - I didn't report one.

seems like there is one - https://bugzilla.gnome.org/show_bug.cgi?id=773387

URL: (none) => https://bugzilla.gnome.org/show_bug.cgi?id=773387

Guillaume Rousse 2016-11-02 22:47:11 CET

CC: (none) => guillomovitch

Comment 5 Thierry Vignaud 2017-01-07 18:00:24 CET
It works fine as of vim-X11-8.0.133-2.mga6 + gtk+3.0-3.22.6-1.mga6

Status: NEW => RESOLVED
Resolution: (none) => FIXED