Your message dated Sun, 18 Nov 2018 17:14:38 +0000
with message-id <e1goqec-0006t1...@fasolo.debian.org>
and subject line Bug#911199: Removed package(s) from unstable
has caused the Debian Bug report #788276,
regarding docky: Docky Trash Icon Docklet broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
788276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docky
Version: 2.2.0-2
Severity: normal

Dear Maintainer,

The Trash docklet in Docky seems to be broken. At first (clean) installation
left clicking on the Trash icon would do nothing, after installing Audacious
media player, it started launching Audacious trying to load a new playlist but
with the following error message:

Error opening trash:///:
Unknown URI scheme

I'm not sure if the link has that extra ":" at the end or what...

When right clicking on the icon the dialog does pop out and will show me what
items are inside the trash folder and "Empty Trash" action in that pop-up
works, but "Open Trash" replicates the same error as directly left clicking on
the icon.

Thanks!



-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages docky depends on:
ii  gconf2                          3.2.6-3
ii  libc6                           2.19-18
ii  libdbus-glib2.0-cil             0.6.0-1
ii  libdbus2.0-cil                  0.8.1-1
ii  libgconf2.0-cil                 2.24.2-3
ii  libglib2.0-0                    2.42.1-1
ii  libglib2.0-cil                  2.12.10-5.1
ii  libgnome-keyring1.0-cil         1.0.0-4
ii  libgnomedesktop2.20-cil         2.26.0-8
ii  libgtk2.0-0                     2.24.25-3
ii  libgtk2.0-cil                   2.12.10-5.1
ii  libmono-addins0.2-cil           1.0+git20130406.adcd75b-3
ii  libmono-cairo4.0-cil            3.2.8+dfsg-10
ii  libmono-corlib4.5-cil           3.2.8+dfsg-10
ii  libmono-posix4.0-cil            3.2.8+dfsg-10
ii  libmono-sharpzip4.84-cil        3.2.8+dfsg-10
ii  libmono-system-core4.0-cil      3.2.8+dfsg-10
ii  libmono-system-web4.0-cil       3.2.8+dfsg-10
ii  libmono-system-xml-linq4.0-cil  3.2.8+dfsg-10
ii  libmono-system-xml4.0-cil       3.2.8+dfsg-10
ii  libmono-system4.0-cil           3.2.8+dfsg-10
ii  libnotify0.4-cil                0.4.0~r3032-7
ii  librsvg2-2.18-cil               2.26.0-8
ii  librsvg2-common                 2.40.5-1
ii  libwnck2.20-cil                 2.26.0-8
ii  libx11-6                        2:1.6.2-3
ii  mono-runtime                    3.2.8+dfsg-10

Versions of packages docky recommends:
pn  dockmanager  <none>

docky suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 2.2.1.1-1+rm

Dear submitter,

as the package docky has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911199

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to