Re: evince needs some dbus and aborts

["Steven M. Bellovin" <smb%cs.columbia.edu@localhost>]

On Fri, 27 Feb 2009 10:58:42 -0600 (CST)
"Jeremy C. Reed" <reed%reedmedia.net@localhost> wrote:

> Something changed on my system and now evince fails to work:
> 
> ** (evince:26386): WARNING **: Failed to create dbus proxy for 
> org.gnome.SettingsDaemon: Could not get owner of name 
> 'org.gnome.SettingsDaemon': no such name
> process 26386: arguments to dbus_connection_ref() were incorrect, 
> assertion "connection != NULL" failed in file dbus-connection.c line
> 2509. This is normally a bug in some application using the D-Bus
> library. D-Bus not compiled with backtrace support so unable to print
> a backtrace Abort (core dumped)
> 
> I looked at core dump and see that it came via libdbus-glib-1.so.2
> from my dbus-glib-0.76 package. That package and dbus-1.2.1nb1 were
> both installed in June 2008. But my glib2 was upgraded to
> glib2-2.18.3nb1 a few days ago. I assume that is the problem.
> 
> So I used pkgsrc to install dbus-glib-0.80 (replaced existing and
> didn't rebuild any other packages). And now evince works for me.

Out of curiosity, if you fired up evince several times, did it crash
every time?  I'm getting intermittent crashes with glib2-2.18.4nb1
newly installed.
> 
> Should the dbus-glib dependency be bumped or something made to force 
> anything updating glib2 to also force the update of dbus-glib?
> 
> And what is the need or purpose of added complexity of dbus just to
> view a PDF?
> 
A number of gnomish programs do that these days -- gimp does also, for
example.


                --Steve Bellovin, http://www.cs.columbia.edu/~smb