Docky cannot initialize Transmisson custom item (Path too long)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Do |
Won't Fix
|
Undecided
|
Unassigned | ||
gnome-do (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-do
When I'm adding Transmission to the Docky items, Do won't start the next time. Here is the snippet of --debug (I'm ataching the whole output, but that's the part that shows the problem):
[Error 10:39:29.458] Error in RunOnMainThread: Path is too long. Path: BitTorrent клиент Transmission: Скачивайте и обменивайтесь файлами в сети BitTorrent (Do.Universe.
[Debug 10:39:29.460] at System.
at Docky.Core.
at Docky.Core.
at Docky.Core.
at Docky.Core.
at (wrapper delegate-invoke) System.
at Do.Core.
at Do.Platform.
The string that is treated as path, is in fact the Comment in ru_RU locale of the Transmission .desktop file. Here is the .desktop file:
#!/usr/bin/env xdg-open
[Desktop Entry]
Name=Transmission BitTorrent Client
GenericName=
Comment=Download and share files over BitTorrent
Exec=transmission %F
Icon=transmission
Terminal=false
TryExec=
Type=Application
MimeType=
Categories=
X-Ubuntu-
Icon[ru_
Name[ru_
Comment[
I've looked into Docky.Core.
AbstractDockItem MaybeCreateCust
{
ItemDockItem customItem = null;
if (identifier.
identifier = identifier.
if (File.Exists (identifier) || Directory.Exists (identifier)) {
if (identifier.
So that's where Directory.Exists fails because the path is very much incorrect - in fact, it obviously isn't a path.
As far as I see, there are several possible fixes:
1) Add try..catch to code that treats the item identifier as path (the code snippet above)
2) Change the format of ItemsService_
Cheers,
Alex
ProblemType: Bug
Architecture: amd64
Date: Sat Nov 21 10:33:39 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: gnome-do 0.8.2+dfsg-1
ProcEnviron:
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: gnome-do
Uname: Linux 2.6.31-14-generic x86_64
description: | updated |
description: | updated |
Thank you for your bug report. We have stopped support on Docky 1 (the Docky that ships with Gnome Do). Docky 2 was a complete rewrite and thus this bug may or may not exist there. Please install Docky 2 (it is a stand-alone app, you can install from lp:docky or Docky's PPA) and test for this bug. If it exists there, please report it to Docky's launchpad bug tracker.