[ubuntu-mono] [Bug 670762] Re: Docky crashes when DBus connection refused [ECONNREFUSED]
Kevin Hunter
hunteke at earlham.edu
Thu Nov 4 19:04:16 UTC 2010
Are you sure it's expected behavior? As an end-user, it smells an awful
lot like a crash.
The behavior is that Docky is /already/ started, and I am able to use it
for anywhere between 5 and 30 minutes. Then, something interrupts
communication with DBus, I gather temporarily, and that's enough to
crash Docky. As an end-user, it smells an awful lot like a crash.
Even if it is expected behavior, what the developer in me notices is the
"Unhandled Exception" text from Mono. That implies that something is
happening, in my case way more than just once, and isn't being handled.
--
Docky crashes when DBus connection refused [ECONNREFUSED]
https://bugs.launchpad.net/bugs/670762
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to docky in ubuntu.
Status in Docky: Invalid
Status in “docky” package in Ubuntu: New
Bug description:
Binary package hint: docky
Subject says it all, but I also have the dieing words of Docky (attached). I'm not sure what I'm doing to cause this, but the later link in the chain certainly seems clear enough.
I'm sorry that I'm not using the most up-to-date version, but I'm hoping it's close enough to be helpful to y'all:
[Info 19:14:46.797] Docky version: 2.0.7 Release
[Info 19:14:46.816] Kernel version: 2.6.35.22
[Info 19:14:46.817] CLR version: 2.0.50727.1433
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: docky 2.0.7-1
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Nov 3 23:58:43 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: docky
More information about the Ubuntu-mono
mailing list