Just additional note for anyone else stumbling into this. I ran into this 
problem, thought first my /home located on another disk caused it. So ran the 
reconfig and all, no fix. 
Careful rereading this report, lead met to check my .Xauthority... and there it 
was.  
I changed those for some experimentation during a training I was doing, and 
forgot to change it back. Setting it back only rw to the user fixed the problem 
for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1433165

Title:
  evince fails to run due to a gdk_mir_display_open

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Here's what happens when I try to run evince under 15.04. No evince
  window comes up. Instead, just:

  
  > evince 

  No protocol specified

  ** (evince:22430): WARNING **: Could not open X display
  No protocol specified
  gdk_mir_display_open
  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 15.04
  Package: evince 3.14.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 17 11:47:57 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-07 (9 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1433165/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to