Evince fails to start on Weston

Bug #1621173 reported by Fred
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Expired
Low
Unassigned

Bug Description

evince (3.21.4-1ubuntu1) doesn't work on Weston.
This is a regression. I believe version 3.20.1-1 worked.

$ evince
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused
Cannot parse arguments: Cannot open display:

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: evince 3.21.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Wed Sep 7 18:38:19 2016
InstallationDate: Installed on 2013-12-26 (985 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Fred (eldmannen+launchpad) wrote :
description: updated
summary: - Evince fails to start on Wayland
+ Evince fails to start on Weston
Revision history for this message
Sebastien Bacher (seb128) wrote :

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
Revision history for this message
Fred (eldmannen+launchpad) wrote :

I don't know how to downgrade.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

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
Revision history for this message
Fred (eldmannen+launchpad) wrote :

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".

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evince (Ubuntu) because there has been no activity for 60 days.]

Changed in evince (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.