[bug-notifications] [gvim 0004815]: vim/gtk/dbus error
Mantis Bug Tracker
noreply at opencsw.org
Mon Sep 19 22:10:34 CEST 2011
The following issue has been set as RELATED TO issue 0004821.
======================================================================
https://www.opencsw.org/mantis/view.php?id=4815
======================================================================
Reported By: zzxtty
Assigned To: dam
======================================================================
Project: gvim
Issue ID: 4815
Category: regular use
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
======================================================================
Date Submitted: 2011-08-10 16:58 CEST
Last Modified: 2011-08-12 17:09 CEST
======================================================================
Summary: vim/gtk/dbus error
Description:
[xxxxxx at taskmaster ~]0% gvim
Gtk-Message: Failed to load module "pk-gtk-module": ld.so.1: vim-x11:
fatal: libpk-gtk-module.so: open failed: No such file or directory
Gtk-Message: Failed to load module "canberra-gtk-module": ld.so.1:
vim-x11: fatal: libcanberra-gtk-module.so: open failed: No such file or
directory
process 29001: D-Bus library appears to be incorrectly set up; failed to
read machine uuid: Failed to open "/opt/csw/var/lib/dbus/machine-id": No
such file or directory
See the manual page for dbus-uuidgen to correct this issue.
D-Bus not compiled with backtrace support so unable to print a
backtrace
Vim: Caught deadly signal ABRT
Vim: Finished.
Abort
[xxxxxx at taskmaster ~]134%
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0004821 D-Bus library appears to be incorrectly...
======================================================================
----------------------------------------------------------------------
(0009239) dam (administrator) - 2011-08-12 17:09
https://www.opencsw.org/mantis/view.php?id=4815#c9239
----------------------------------------------------------------------
Yeah, these are in fact different: mirror/opencsw/current and
mirror/opencsw/unstable are the same while mirror/opencsw-future/unstable
is newer. Sorry for the confusion.
More information about the bug-notifications
mailing list