Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Docky does not start
https://bugzilla.redhat.com/show_bug.cgi?id=822477
Summary: Docky does not start
Product: Fedora
Version: 17
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: high
Priority: unspecified
Component: docky
AssignedTo: lzap(a)redhat.com
ReportedBy: marek78uk(a)o2.pl
QAContact: extras-qa(a)fedoraproject.org
CC: lzap(a)redhat.com, mono(a)lists.fedoraproject.org
Classification: Fedora
Story Points: ---
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Description of problem:
Docky does not start
Version-Release number of selected component (if applicable):
# rpm -qa | grep docky
docky-2.0.12-1.fc17.x86_64
How reproducible:
always
Steps to Reproduce:
1. install docky
2. run docky
Actual results:
$ docky
Missing method Init in assembly /usr/lib64/docky/Docky.exe, type
NDesk.DBus.BusG
Unhandled Exception: System.IO.FileNotFoundException: Could not load file or
assembly 'NDesk.DBus.GLib, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=f6716e4f9b2ed099' or one of its dependencies.
File name: 'NDesk.DBus.GLib, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=f6716e4f9b2ed099'
[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not
load file or assembly 'NDesk.DBus.GLib, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=f6716e4f9b2ed099' or one of its dependencies.
File name: 'NDesk.DBus.GLib, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=f6716e4f9b2ed099'
Expected results:
docky to run
Additional info:
funnily enough, docky works just fine in a virtual machine on the other
computer. the only difference is on my test laptop I've got some updates from
updates-testing repo, while the vm has just updates. Also laptop was installed
from Fedora 17 Beta DVD install media, while vm was installed from net-install
disc.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.