Bug 1394451

Could you try again with the latest version, please ? vim-8.0.133-1.fc26 or newer...

I have abandoned Fedora for multiple reasons. Could you please close this bug?

I am sorry to hear that, Diamantis. Have a nice day.

Fedora has been regressing to the point it's started to pissoff even hard fans like me. Critical bugs like this one should not just be closed away citing insufficient data. Infact that much info is all the data spit out by gvim on konsole.

I installed Fedora25 yday, the latest official version and my basic tool gvim was not present. Appauling to find that fedora folk have removed important editors like vim, gvim, emacs, and expect users to toil to get them. I spent hours figuring things out and finally after much more effort, installed "dnf install vim-enhanced vim-X11" and then.. more frustration ... several of this same error line is printed on konsole

(gvim:1640): 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

The 1640 is gvim PID.

vim works fine.


@Karsten hopp: The version is of vim-X11 pkg dnf got for me: 2:8.0.586-1.fc25. That's way recent than what you stated before bug got closed. 

Pls re open as Critical and fix on priority.

Hi Vla,

I use Fedora 25 (version on which you are reporting bug) and have Fedora 26 as virtual machine (version on which Diamantis was reporting bug) and gvim works fine on both machines. So I need more info for deciding if it is GVIM's bug, GTK's bug, GDK's/cairo's bug, bug caused by desktop environment, or by window's manager, or even by your graphic card. Diamantis couldn't provide it, because he abandoned Fedora and without further help we couldn't solve this issue - so I closed this bug as INSUFFCIENT_DATA. If you have this issue, would you mind providing such information? Plus actual steps for reproducing it (such as if you are using gvim directly or through ssh, ideally providing the file which causing this behavior). I did these steps:

1) I have fully updated f26 and f25 - $ sudo dnf -y update
2) I tried both ways to open file in gvim -
   a) $ gvim 
      - and I opened file through GUI
   b) $ gvim test_file

- and no errors happened. Didn't gvim start at all? Or gvim started and worked fine, but I printed out these error messages on stdout?

P.S. Fedora provides editor 'vi' by default. If you consider as hard work issuing command 'sudo dnf install vim gvim', I am sorry, but I do not know how to make it easier for you. Fedora is trying to ship image as small as possible, so tools, which doesn't need GUI for working, are shipped in their smallest and CLI variant. You can install GUI parts by dnf after installation.

And I use gvim without ssh, desktop environment gnome, window's manager x11, graphic card integrated Intel HD Graphics 5500.

Because of no response, closing as INSUFFICIENT_DATA.

Hi Zdenek,

Its not everyday/wk that I can troll around to reply to such obvious bugs, so pls pardon the delayed response.

I did run:
dnf -y update
as root on my Fedora 25 already and then only logged the bug. Its a fresh install of Fedora 25 with an Encrypted file-system.

On the 'konsole' window, there are no more info printed other than what Diamantis already pasted originally (and also acquiesced by me). FYI, here it is again (which again means its STILL A BUG AND DO NOT CLOSE IT AWAY ONCE AGAIN):

===================================================
(gvim:2800): 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


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

(gvim:2800): 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


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

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

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

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

(gvim:2800): 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

===================================================


The GVIM instance which starts up, DOES NOT load ANY file, and just freezes without any response to typing or mouse clicks onto that GVIM instance (rest of the computer is fine). That CLEARLY IMPLIES that the issue is with GVIM and its made ALL THE MORE CLEAR by the GTK ERRORS spit onto the bash-shell console.

Once again, no point in closing this CRITICAL ISSUE as INSUFFICIENT DATA as that does not resolve the clearly spit out errors onto the bash-shell console screen. My wild guess is that GVIM code is making invalid to 'gtk_widget_set_size_request()' or some such thing. 

That is all the info I have at this time. And I do not want to try Fedora 26 alpha releases as I'm not looking to encounter more bugs with it.

Kindly fix this CRITICAL issue as GVIM is COMPLETELY UNUSABLE at this point.


(In reply to Zdenek Dohnal from comment #5)
> Hi Vla,
> 
> I use Fedora 25 (version on which you are reporting bug) and have Fedora 26
> as virtual machine (version on which Diamantis was reporting bug) and gvim
> works fine on both machines. So I need more info for deciding if it is
> GVIM's bug, GTK's bug, GDK's/cairo's bug, bug caused by desktop environment,
> or by window's manager, or even by your graphic card. Diamantis couldn't
> provide it, because he abandoned Fedora and without further help we couldn't
> solve this issue - so I closed this bug as INSUFFCIENT_DATA. If you have
> this issue, would you mind providing such information? Plus actual steps for
> reproducing it (such as if you are using gvim directly or through ssh,
> ideally providing the file which causing this behavior). I did these steps:
> 
> 1) I have fully updated f26 and f25 - $ sudo dnf -y update
> 2) I tried both ways to open file in gvim -
>    a) $ gvim 
>       - and I opened file through GUI
>    b) $ gvim test_file
> 
> - and no errors happened. Didn't gvim start at all? Or gvim started and
> worked fine, but I printed out these error messages on stdout?
> 
> P.S. Fedora provides editor 'vi' by default. If you consider as hard work
> issuing command 'sudo dnf install vim gvim', I am sorry, but I do not know
> how to make it easier for you. Fedora is trying to ship image as small as
> possible, so tools, which doesn't need GUI for working, are shipped in their
> smallest and CLI variant. You can install GUI parts by dnf after
> installation.

Hi,

once again, GVim works fine in my case, so I need to know your usage, settings etc. to reproduce this issue. I cannot blindly start fixing something where should be the problem by my opinion, I need to test if my patch will fix this problem or not. So if I cannot reproduce it, I cannot test it. To be able to reproduce the issue, I need to know reporter's configuration, usage, settings etc. And to know reporter's configuration, I need reporter's cooperation (your first comment was after 4 months after closing the bug, your response now is after nearly one month). So yes, I will close this bug as WORKSFORME/INSUFFICIENTDATA again, if I won't be able to reproduce the bug and NEEDINFO will be set here for nearly month.
Clearly it isn't critical issue, because there would be much more affected users like you. If you don't set anything else after install, I guess you use gnome desktop environment and Wayland as window manager. Is that correct?
Don't you run GVim as root by any chance? Because Wayland strictly forbids running GUI applications as root and with sudo (you can check which windows manager you use by commands: 1) loginctl (from it you find out session) 2) loginctl show-session <session>).

Once again, I cannot reproduce your issue. Here are my steps:

1) install fresh Fedora 25 Workstation in QEMU/KVM
2) set to encrypt data on disk
3) create user (is in wheel group)
4) as user update system ($ sudo dnf -y update)
5) install gvim ($ sudo dnf -y install gvim)
6) a) I opened gvim from application menu - no error
   b) I opened it from CLI - $ gvim - no error
   c) I opened it from CLI with file - $ gvim test - no error
   d) I opened it from CLI with sudo - $ sudo gvim - gives this output:

      No protocol specified
      E233: cannot open display
      Press ENTER or type command to continue

      E852: The child process failed to start the GUINo protocol specified

      Press ENTER or type command to continue

      and opens Vim after that.
   e) I opened it from CLI with sudo and file - $ sudo gvim test - same as d)
   f) I opened it from CLI as root - # gvim - gives output:

      E233: cannot open display
      Press ENTER or type command to continue

      and opens Vim after that.
   g) I opened it from CLI as root with file - same as f)

   When you use Wayland as window manager and you are logged in as user and you
   try to run GUI app with sudo or as root, d) - g) is correct behavior. So I 
   would like to know more of your configuration to be able to reproduce it.

Hi Vla,

I came across this issue today with fresh install gvim.
But after running this

yum builddep vim-X11

It now works for me.