After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 739812 - Evince launched from inside latexila comes with ugly black borders
Evince launched from inside latexila comes with ugly black borders
Status: VERIFIED FIXED
Product: gtk+
Classification: Platform
Component: .General
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2014-11-08 11:37 UTC by Atri
Modified: 2014-11-09 19:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Black borders on evince launched from withing latexila. (190.84 KB, image/png)
2014-11-08 11:37 UTC, Atri
Details

Description Atri 2014-11-08 11:37:54 UTC
Created attachment 290213 [details]
Black borders on evince launched from withing latexila.

When evince is launched from within latexila (versio 3.14.2) it launches with ugly thick black window borders. This does not ever happen when launching evince as a standalone application, but only when evince is launched from within latexila. Attached screenshot should make things clearer. Also note that the problem does not happen the first time evince is launched from latexila but every time thereafter.
Comment 1 Atri 2014-11-08 11:38:32 UTC
Just to add, the black borders disappear when the launched evince is maximised or docked to the left or right of the desktop.
Comment 2 Atri 2014-11-08 12:29:36 UTC
If latexila is launched from the terminal, the error messages that one sees are pasted below:
-----------------------------------------------------------

> latexila 

(latexila:23184): GLib-GObject-WARNING **: The property GSettings:schema is deprecated and shouldn't be used anymore. It will be removed in a future version.

(latexila:23184): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(latexila:23184): GLib-GObject-WARNING **: The property GtkToolButton:stock-id is deprecated and shouldn't be used anymore. It will be removed in a future version.

(latexila:23184): GLib-GObject-WARNING **: The property GtkButton:use-stock is deprecated and shouldn't be used anymore. It will be removed in a future version.

(latexila:23184): GLib-GObject-WARNING **: The property GtkSettings:gtk-button-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evince:23192): Gtk-WARNING **: Ignoring visual set on widget `EvWindow' that is not on the correct screen.

(evince:23192): Gtk-WARNING **: Ignoring visual set on widget `GtkPaned' that is not on the correct screen.

(evince:23192): Gtk-WARNING **: Ignoring visual set on widget `GtkPaned' that is not on the correct screen.

(evince:23192): Gtk-WARNING **: Ignoring visual set on widget `GtkOverlay' that is not on the correct screen.

(evince:23192): Gtk-WARNING **: Ignoring visual set on widget `EvView' that is not on the correct screen.

(evince:23192): GLib-GObject-WARNING **: The property GtkSettings:gtk-menu-images is deprecated and shouldn't be used anymore. It will be removed in a future version.

(evince:23192): Gtk-WARNING **: Ignoring visual set on widget `GtkTreeView' that is not on the correct screen.
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
Comment 3 Sébastien Wilmet 2014-11-08 13:34:33 UTC
I had a similar problem, but it's now fixed. I use gtk+, glib etc from git, so maybe the 3.14 version isn't fixed. Which version of GTK+ do you use? (it's most probably a GTK+ bug)
Comment 4 Atri 2014-11-08 14:02:16 UTC
(In reply to comment #3)
> Which version of GTK+ do you use? (it's most probably a GTK+ bug)

Gtk 3.14.3

Could you please tell me the commit which fixed this in gtk+ master?
Comment 5 Sébastien Wilmet 2014-11-08 15:19:18 UTC
It's maybe fixed in GTK+ 3.14.4. But I have no idea when and how it was fixed, I think it's in GTK+, but I'm not sure.

Which Linux distribution do you use?
Comment 6 Atri 2014-11-08 15:35:49 UTC
I am on openSUSE 13.2. We will have gtk+ 3.14.4 available soon through the update repos, so I could get back to you after testing with the updated version.
Comment 7 Sébastien Wilmet 2014-11-08 17:19:41 UTC
I can reproduce the bug on Fedora 21, with gtk+ 3.14.4.

The related bug was #738483, but it's not exactly the same bug.
Comment 8 Sébastien Wilmet 2014-11-08 17:20:40 UTC
bug #738483, it's better with the link.
Comment 9 Sébastien Wilmet 2014-11-08 17:31:27 UTC
I move the bug to GTK+. The bug occurs only with the 3.14 version, not with git master. LaTeXila launches evince with D-Bus. The problem comes maybe from client-side decorations and the headerbar.
Comment 10 Matthias Clasen 2014-11-09 15:47:46 UTC
You'll have to provide some details about your system, like the output of xdpyinfo. Are there multiple screens on your system ? nvidia drivers ? The error messages you see indicate that evince fails to use the rgba visual when launched in this way, which explains the black borders perfectly. The question is just why that would happen on your system, but not on others.
Comment 11 Atri 2014-11-09 16:13:33 UTC
(In reply to comment #10)
> You'll have to provide some details about your system, like the output of
> xdpyinfo. 

Quoted at the end of this comment

> Are there multiple screens on your system ?

No. Tried on 2 different setups: 1) laptop with Intel Graphics, and 2) desktop with AMD radeon graphics, both with just one display and both show the same issue.

> nvidia drivers ?

No.

> error messages you see indicate that evince fails to use the rgba visual when
> launched in this way, which explains the black borders perfectly. The question
> is just why that would happen on your system, but not on others.

Happens not only on my system (openSUSE 13.2, GNOME 3.14.1, gtk+ 3.14.3) but also on Fedora 21 with gtk+ 3.14.4 (see c7).

xdpyinfo output (from the laptop setup):
-------------------------------------------
name of display:    :0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    11601000
X.Org version: 1.16.1
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x2c00007, revert to Parent
number of extensions:    29
    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    DRI2
    DRI3
    GLX
    Generic Event Extension
    MIT-SCREEN-SAVER
    MIT-SHM
    Present
    RANDR
    RECORD
    RENDER
    SECURITY
    SGI-GLX
    SHAPE
    SYNC
    X-Resource
    XC-MISC
    XFIXES
    XFree86-DGA
    XFree86-VidModeExtension
    XINERAMA
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    1366x768 pixels (361x203 millimeters)
  resolution:    96x96 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16, 32
  root window id:    0x9b
  depth of root window:    24 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x22
  default number of colormap cells:    256
  preallocated pixels:    black 0, white 16777215
  options:    backing-store WHEN MAPPED, save-unders NO
  largest cursor:    256x256
  current input event mask:    0xda0003
    KeyPressMask             KeyReleaseMask           StructureNotifyMask      
    SubstructureNotifyMask   SubstructureRedirectMask PropertyChangeMask       
    ColormapChangeMask       
  number of visuals:    20
  default visual id:  0x20
  visual:
    visual id:    0x20
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x21
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x89
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x8a
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x8b
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x8c
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x8d
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x8e
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x8f
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x90
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x91
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x92
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x93
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x94
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x95
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x96
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x97
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x98
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x99
    class:    DirectColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
  visual:
    visual id:    0x5c
    class:    TrueColor
    depth:    32 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    8 bits
Comment 12 Matthias Clasen 2014-11-09 16:58:35 UTC
actually, nevermind. it is happening here too.
Comment 13 Sébastien Wilmet 2014-11-09 17:51:16 UTC
GTK+ 3.14.4: KO
GTK+ 3.15.0: KO
GTK+ 3.15.1: OK

So the problem has been fixed between 3.15.0 and 3.15.1, maybe commit fea13fcfc1a7d9e286d5bb12bdbb8b5acd774001.
Comment 14 Matthias Clasen 2014-11-09 18:09:06 UTC
I've cherry-picked the only patch that has a remote chance of being relevant to the 3.14 branch. Let me know if that helps
Comment 15 Sébastien Wilmet 2014-11-09 18:21:29 UTC
Yes, it fixes the problem. Thanks!
Comment 16 Atri 2014-11-09 19:55:42 UTC
(In reply to comment #14)
> I've cherry-picked the only patch that has a remote chance of being relevant to
> the 3.14 branch. Let me know if that helps

Yes, thanks a lot, Matthias for that quick fix. Works here too.