Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38173 - [keepass] Failure to start keepass in regular session
Attached to Project:
Community Packages
Opened by Alexander Peltzer (alexpe87) - Tuesday, 17 December 2013, 12:34 GMT
Last edited by Timothy Redaelli (tredaelli) - Tuesday, 17 December 2013, 17:38 GMT
Opened by Alexander Peltzer (alexpe87) - Tuesday, 17 December 2013, 12:34 GMT
Last edited by Timothy Redaelli (tredaelli) - Tuesday, 17 December 2013, 17:38 GMT
|
DetailsDescription: Recently the keepass package got moved from AUR to [community] and I was happy to get precompiled packages. However, the "new" keepass package does include a few problems for me, namely that the keepass application does not start when I try to start it using e.g. ALT+F2 -> "keepass" or click on my icon in Gnome3 launcher. Simply entering "keepass" in my shell session however starts the keepass application without any problems.
Additional info: * Current version 2.24 Steps to reproduce: Try to start keepass (current community package) under x86_64 with Gnome3 using the ALT+F2 combo and entering keepass there. Other than that, try to start it using the Gnome3 Dock / Program Selection Menu. It does not work at all, and I already tried to verify this on 3 different PCs all with AL 64Bit and the same WM+Kernel (newest, stable). |
This task depends upon
Closed by Timothy Redaelli (tredaelli)
Tuesday, 17 December 2013, 17:38 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#38010
Tuesday, 17 December 2013, 17:38 GMT
Reason for closing: Duplicate
Additional comments about closing:
If you have any idea on how to get useful information like logfiles for this particular case, let me know.