gvfs-gdu-volume-monitor sig11

[Fryderyk Dziarmagowski]

On Tue, 19 Jan 2010 22:30:23 +0100
Marcin Banasiak <megabajt w pld-linux.org> wrote:

> W dniu 16 stycznia 2010 19:08 użytkownik Pawel Golaszewski napisał:
> > Odpalone z palca:
> >
> > $ /usr/lib/gvfs/gvfs-gdu-volume-monitor
> > (process:26419): libgdu-WARNING **: Couldn't get daemon properties
> > (process:26419): GLib-GObject-WARNING **: invalid (NULL) pointer instance
> > (process:26419): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> > (process:26419): GLib-GObject-WARNING **: invalid (NULL) pointer instance
> > (process:26419): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> > (process:26419): GLib-GObject-WARNING **: invalid (NULL) pointer instance
> > (process:26419): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> > (process:26419): GLib-GObject-WARNING **: invalid (NULL) pointer instance
> > (process:26419): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
> > Naruszenie ochrony pamięci
> 
> 
> Brak DeviceKit-disks. Poprawione w gnome-disk-utility-libs-2.28.1-3

libs nie ma zależności runtime od DeviceKit-disks. gvfs-gdu ma ją jak
najbardziej.

-- 
Fryderyk Dziarmagowski