Bug 41505 - SIGSEGV when Super key pressed
Summary: SIGSEGV when Super key pressed
Alias: None
Product: Class Libraries
Classification: Mono
Component: Windows.Forms (show other bugs)
Version: 4.4.0 (C7)
Hardware: PC Linux
: Low normal
Target Milestone: Community
Assignee: Bugzilla
: 42676 (view as bug list)
Depends on:
Reported: 2016-06-03 21:44 UTC by Samuel Littley
Modified: 2016-11-29 11:52 UTC (History)
9 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:

Backtrace output of application crash (17.06 KB, text/plain)
2016-06-03 21:44 UTC, Samuel Littley

Description Samuel Littley 2016-06-03 21:44:48 UTC
Created attachment 16192 [details]
Backtrace output of application crash

Running keepass 2.33, the application crashes with SIGSEGV when the Super key is pressed (hugely awkward when using xmonad with the modifier key set to Super). See the attached backtrace, produced with debugging symbols for both mono and keepass.

A bug opened on KeePass itself (https://sourceforge.net/p/keepass/bugs/1523/) was closed by the developer stating that it was not keepass code that caused the segfault.

Running Arch Linux, using the xmonad window manager.
Comment 1 manzuzz 2016-07-06 18:25:35 UTC
I have the very same issue. 
For me, I have running Arch Linux and i3 windows manager. 
I opened a thread in Keepass sourceforge forum https://sourceforge.net/p/keepass/discussion/329221/thread/bd5d3514/#c779 and being told that it is a mono issue. Equally awkward in i3 because of the heavy usage of the Super key...
It is now a long time that this issue manifested itself. Any suggestion?
Comment 2 web 2016-07-10 19:49:59 UTC
Not a solution, but I switched to keepassx-http, which works as a drop-in replacement.
Comment 3 Facetoe 2016-07-18 13:27:12 UTC
Same issue here, also running i3.
Comment 4 Rodrigo Kumpera 2016-07-20 00:55:51 UTC
*** Bug 42676 has been marked as a duplicate of this bug. ***
Comment 5 Rodrigo Kumpera 2016-07-20 00:56:26 UTC

While we aim to fix all bugs in mono, WinForms is not a library we actively maintain anymore. On the other hand, we encourage the community to submit fixes for such issues through a pull request on github repository.

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Note You need to log in before you can comment on or make changes to this bug.