[Expired for evince (Ubuntu) because there has been no activity for 60
days.]
** Changed in: evince (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
evince works for me when running GNOME on Wayland too.
But when I run under Weston then it says "Failed to connect to Mir:
Failed to connect to server socket: No such file or directory".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
evince 3.22.0-0ubuntu1 works fine here on GNOME on Wayland in Ubuntu
GNOME 16.10.
Could you give more specific instructions for me to try to duplicate the
bug you reported?
** Changed in: evince (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
I don't know how to downgrade.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1621173
Title:
Evince fails to start on Weston
To manage notifications about this bug go to:
Thank you for your bug report, could you downgrade and confirm it's due
to the update? That looks weird since there is not really changes that
should have impact on the backend
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a
** Summary changed:
- Evince fails to start on Wayland
+ Evince fails to start on Weston
** Description changed:
- evince (3.21.4-1ubuntu1) doesn't work on Wayland.
+ evince (3.21.4-1ubuntu1) doesn't work on Weston.
This is a regression. I believe version 3.20.1-1 worked.
$ evince
