Ubuntu

keepass2 crashes on start when using xmir

Reported by Shane O'Sullivan on 2013-11-04
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
keepass2 (Ubuntu)
Undecided
Unassigned

Bug Description

After installing keepass2 on 13.10 any attempts to launch it results in an immediate crash. Launching from the terminal results in the following trace: http://paste.ubuntu.com/6360371/

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: keepass2 2.23+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 4 19:10:59 2013
InstallationDate: Installed on 2013-10-25 (9 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: keepass2
UpgradeStatus: No upgrade log present (probably fresh install)

Shane O'Sullivan (hitsuji) wrote :
Julian Taylor (jtaylor) wrote :

try resetting the configuration:

mv ~/.config/KeePass/KeePass.config.xml ~/.config/KeePass/KeePass.config.xml.bak

if that fixes the issue please attach the configuration to the bug (after checking it does not contain anything private)

Shane O'Sullivan (hitsuji) wrote :

There is no configuration. This crash is happens on a fresh install and before an initial configuration is generated.

J (jstock-l) wrote :

I am encountering this issue as well. My results from terminal are identical. Issue is with a clean install.

I have also included my environment.

David Lechner (dlech) wrote :

I did a little digging in the source code. The actual crash is because the height or width of a bitmap is <= 0. If we follow this up the stack trace, it is coming from trying to create a cursor for a MesssageBox.

But, if we go all the way up the stack trace, we will see that KeePass failed to start and that it was trying to show an error message. Relevant code from Program.cs is:

try
{
     if(m_cmdLineArgs[AppDefs.CommandLineOptions.DebugThrowException] != null)
       throw new Exception(AppDefs.CommandLineOptions.DebugThrowException);

     m_formMain = new MainForm();
    Application.Run(m_formMain);
}
catch(Exception exPrg) { MessageService.ShowFatal(exPrg); }

Since the crash is occurring in the MessageBox code, we can't see what the actual error is.

There is an undocumented command line option that should be able to simulate this crash. If you run ```keepass2 --debug-throwexcp```, do you get the same crash and stack trace?

I am not able to reproduce, the crash in a fresh install in a virtualbox vm. It may be a system related issue. Have you changed anything from the default Ubuntu install? In particular, anything that may have to do with a cursor?

Shane O'Sullivan (hitsuji) wrote :

```keepass2 --debug-throwexcp``` lead to the same exception.

The main thing I had installed that was different from the default Ubuntu install was unity-system-compositor. After removing this with ```sudo apt-get remove unity-system-compositor && sudo apt-get autoremove``` and rebooting allowed KeePass2 to run.

David Lechner (dlech) wrote :

Ah, unity-system-compositor would be the new Mir display server. KeePass requires an X window server, so I am afraid that this is going to be a "won't fix".

Julian, you will probably want to add a conflicts entry for this package in the debian/control file.

Julian Taylor (jtaylor) wrote :

isn't mir supposed to be compatible with X via Xmir?
is xserver-xorg-xmir installed and xmir running?

Shane O'Sullivan (hitsuji) wrote :

Yes, xmir is loaded when it crashes.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in keepass2 (Ubuntu):
status: New → Confirmed
David Lechner (dlech) wrote :

> isn't mir supposed to be compatible with X via Xmir?

Supposed to? Yes. But obviously, there is something that libgdi+ is doing that the xmir xserver compatibility layer does not like.

summary: - keepass2 crashes on start
+ keepass2 crashes on start when using xmir
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers