Package: libunique-1.0-0
Version: 1.0.0-1
Severity: normal

I'm trying to create midori packages.  As a convenience to dbus-using
midori-users, I built it with libunique support.  However, *I* do not
use dbus, so if I try to run the same binary on my system, I get

    $ midori

    (midori:25212): Unique-DBus-WARNING **: Unable to open a connection to the 
session bus: Failed to execute dbus-launch to autolaunch D-Bus session

    (midori:25212): Unique-DBus-WARNING **: Unable to connect to the running 
instance, aborting.
    An instance of Midori is already running but not responding.
    $

    $ env | grep -i dbus
    $ which dbus-launch

As you can see, either midori or libunique does not correctly handle
the situation where the app was built with libunique *SUPPORT*, but
dbus is not available at runtime.

It seems to me that if this is wontfixed, I'll have to either make
midori depend on libdbus-bin, or create two separate binary packages:
midori (for dbus users) and midori-nounique (for everyone else).

If libunique is correctly reporting the error to the application
(midori), and midori isn't understanding the error, please reassign
this bug to "midori 0.0.21-1" and I'll chase the issue up with the
midori developers.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libunique-1.0-0 depends on:
ii  libc6                         2.7-13     GNU C Library: Shared libraries
ii  libdbus-glib-1-2              0.76-1     simple interprocess messaging syst
ii  libglib2.0-0                  2.16.4-2   The GLib library of C routines
ii  libgtk2.0-0                   2.12.11-3  The GTK+ graphical user interface 
ii  libx11-6                      2:1.1.4-2  X11 client-side library

libunique-1.0-0 recommends no packages.

libunique-1.0-0 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to