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 748513 - wayland: zoom level popup goes up (and doesnt work)
wayland: zoom level popup goes up (and doesnt work)
Status: RESOLVED DUPLICATE of bug 756976
Product: evince
Classification: Core
Component: general
3.16.x
Other Linux
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-27 09:39 UTC by Lasse Schuirmann
Modified: 2015-10-22 18:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of Evince showing a popover up (44.95 KB, image/png)
2015-04-27 11:12 UTC, Germán Poo-Caamaño
Details

Description Lasse Schuirmann 2015-04-27 09:39:03 UTC
See http://i.imgur.com/Dy1NaBf.png

Also it just crashed my whole wayland session when I clicked on "150%".

This is probably related to https://bugzilla.gnome.org/show_bug.cgi?id=719400
Comment 1 Germán Poo-Caamaño 2015-04-27 10:22:56 UTC
It seems you are reporting 2 bugs in one.  Please, split them:

The popover going up seems a bug in Gtk+.  Evince does not decide where to show it.

Regarding to the crash, you'll also need to add a stack trace; please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information about how to do so. When providing a better description and pasting a stack trace, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Comment 2 Lasse Schuirmann 2015-04-27 10:40:39 UTC
(In reply to Germán Poo-Caamaño from comment #1)
> It seems you are reporting 2 bugs in one.  Please, split them:
> 
> The popover going up seems a bug in Gtk+.  Evince does not decide where to
> show it.

Other popups in other apps show right. Otherwise I wouldn't have bothered you with this, sorry for not mentioning. But it seems evince is doing something strange here.

> Regarding to the crash, you'll also need to add a stack trace; please see
> https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for
> more information about how to do so. When providing a better description and
> pasting a stack trace, please reset the status of this bug report from
> NEEDINFO to its previous status. Thanks in advance!

I will open an own bug for this. Sadly the bug seems nondeterministic, so its something really evil. See https://bugzilla.gnome.org/show_bug.cgi?id=748515
Comment 3 Germán Poo-Caamaño 2015-04-27 10:53:28 UTC
(In reply to Lasse Schuirmann from comment #2)
> (In reply to Germán Poo-Caamaño from comment #1)
> > It seems you are reporting 2 bugs in one.  Please, split them:
> > 
> > The popover going up seems a bug in Gtk+.  Evince does not decide where to
> > show it.
> 
> Other popups in other apps show right. Otherwise I wouldn't have bothered
> you with this, sorry for not mentioning. But it seems evince is doing
> something strange here.

Do the other popover have the same height than Evince? Are the applications located in the same place?
What if you put another application close to the bottom (low enough that the popover does not fit full). Does the popover show up or down with some parts hidden?
Comment 4 Lasse Schuirmann 2015-04-27 10:57:32 UTC
(In reply to Germán Poo-Caamaño from comment #3)
> (In reply to Lasse Schuirmann from comment #2)
> > (In reply to Germán Poo-Caamaño from comment #1)
> > > It seems you are reporting 2 bugs in one.  Please, split them:
> > > 
> > > The popover going up seems a bug in Gtk+.  Evince does not decide where to
> > > show it.
> > 
> > Other popups in other apps show right. Otherwise I wouldn't have bothered
> > you with this, sorry for not mentioning. But it seems evince is doing
> > something strange here.
> 
> Do the other popover have the same height than Evince? Are the applications
> located in the same place?
> What if you put another application close to the bottom (low enough that the
> popover does not fit full). Does the popover show up or down with some parts
> hidden?

The popup also goes up when evince is maximized. The popup doesn't go up e.g. for nautilus when I put it right on the bottom of my screen and doesnt fit this way. My screen is big enough for the popover.

http://i.imgur.com/s3hknvy.png
Comment 5 Germán Poo-Caamaño 2015-04-27 11:12:41 UTC
Created attachment 302435 [details]
Screenshot of Evince showing a popover up

Thanks for the input.

As a side note, it is odd that you get "nan%" ("not a number", really?).

As a future reference: please add the screenshots as attachments (as I am doing it now). We don't know how transient are websites like imgur.
Comment 6 Lasse Schuirmann 2015-04-27 11:15:16 UTC
(In reply to Germán Poo-Caamaño from comment #5)
> Created attachment 302435 [details]
> Screenshot of Evince showing a popover up
> 
> Thanks for the input.
> 
> As a side note, it is odd that you get "nan%" ("not a number", really?).

As mentioned this is probably related to https://bugzilla.gnome.org/show_bug.cgi?id=719400 which already covers this weird behaviour.

> As a future reference: please add the screenshots as attachments (as I am
> doing it now). We don't know how transient are websites like imgur.

Thanks. I was not aware of that.
Comment 7 Matthias Clasen 2015-04-30 11:26:26 UTC
(In reply to Germán Poo-Caamaño from comment #1)
> It seems you are reporting 2 bugs in one.  Please, split them:
> 
> The popover going up seems a bug in Gtk+.  Evince does not decide where to
> show it.

It might be a bit surprising, but it is not a bug.

The default value for the GtkPopover::position property is 'top', unfortunately. This does not cause problems under X, since popovers can't escape the window there. Under Wayland, they can. In summary,

g_object_set (popover, "position", GTK_POS_BOTTOM, NULL);

will fix the problem.
Comment 8 Germán Poo-Caamaño 2015-10-22 18:17:13 UTC
Oops, the patch went into the newer bug.

*** This bug has been marked as a duplicate of bug 756976 ***