Your message dated Fri, 6 Oct 2023 10:19:12 +0200
with message-id <[email protected]>
and subject line Re: Bug#739384: keepass2: does not start anymore (after
upgrade to mono?)
has caused the Debian Bug report #739384,
regarding keepass2: does not start anymore (after upgrade to mono?)
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 [email protected]
immediately.)
--
739384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739384
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: keepass2
Version: 2.24+dfsg-1
Severity: important
Dear Maintainer,
Recently I installed the latest Jessie upgrades to mono, today I wanted
to start keepass2 as usual. However, it does not start anymore. I tried
from command line, but it neither gives *any* message.
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages keepass2 depends on:
ii libmono-corlib4.5-cil 3.0.6+dfsg2-11
ii libmono-system-configuration4.0-cil 3.0.6+dfsg2-11
ii libmono-system-drawing4.0-cil 3.0.6+dfsg2-11
ii libmono-system-security4.0-cil 3.0.6+dfsg2-11
ii libmono-system-windows-forms4.0-cil 3.0.6+dfsg2-11
ii libmono-system-xml4.0-cil 3.0.6+dfsg2-11
ii libmono-system4.0-cil 3.0.6+dfsg2-11
ii libx11-6 2:1.6.2-1
ii mono-runtime 3.0.6+dfsg2-11
Versions of packages keepass2 recommends:
ii xsel 1.2.0-2
Versions of packages keepass2 suggests:
pn keepass2-doc <none>
pn mono-dmcs <none>
ii xdotool 1:3.20130111.1-3
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 18 Feb 2014 21:41:04 +0100 "Matthias F. Brandstetter"
<[email protected]> wrote:
The bug can be closed, it seems it was on my end.
--- End Message ---
