Opened 11 years ago

Closed 11 years ago

#40819 closed defect (invalid)

evince is able to launch, but not able to open any pdf or image files

Reported by: hong@… Owned by: dbevans (David B. Evans)
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc:
Port: evince

Description

After "sudo port install evince", evince can launch successfully. However, when I tried to use it to open any pdf or image files, nothing happened.

Change History (5)

comment:1 Changed 11 years ago by hong@…

Cc: hong@… added

Cc Me!

comment:2 Changed 11 years ago by dbevans (David B. Evans)

Cc: hong@… removed
Owner: changed from macports-tickets@… to devans@…
Port: evince added
Status: new → assigned

When submitting a ticket, the reporter is automatically CC'd -- no need to explicitly set the CC field or use CC me. But please do CC the maintainer(s) and set the port field. 

$ port info --maintainer evince
maintainer: devans@macports.org, openmaintainer@macports.org

comment:3 Changed 11 years ago by dbevans (David B. Evans)

evince works fine for me. I'm able to open pdf and other image files without any problems. Can you provide any additional information? Any error messages on the console for instance? When you try to open a file is the file selection window displayed or is there no response from the program at all? Please be detailed.

comment:4 in reply to:  3 Changed 11 years ago by hong@…

Replying to devans@…:

evince works fine for me. I'm able to open pdf and other image files without any problems. Can you provide any additional information? Any error messages on the console for instance? When you try to open a file is the file selection window displayed or is there no response from the program at all? Please be detailed.

Thanks for the reply! I've found the issue, I need to run "launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist" before I can use evince properly. Maybe this should be written in the documentation somewhere?

comment:5 Changed 11 years ago by dbevans (David B. Evans)

Resolution: → invalid
Status: assigned → closed

Yes, that would be a problem. The DBus session bus needs to be running for most if not all GNOME and KDE apps. On installation the dbus port provides the following message: 

  ############################################################################
  # Startup items have been generated that will aid in
  # starting dbus with launchd. They are disabled
  # by default. Execute the following command to start them,
  # and to cause them to launch at startup:
  #
  # sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist
  # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist
  ############################################################################

This only needs to be done once after installation. The system bus will automatically start at system startup. The session bus will start on login.

I also note that if you don't do this, evince outputs the following message on the console: 

Failed to get bus connection: Session D-Bus not running. Try running `launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist'.

Glad you got it working.

Note: See TracTickets for help on using tickets.