| View previous topic :: View next topic |
| Author |
Message |
gordonp
Tux's lil' helper
Joined: 23 May 2005
Posts: 102
|
 Posted: Thu May 10, 2018 6:45 pm Post subject: Keepass won't start |
 |
|
This is a recent development - I maintain a keepass file with all my passwords, and something broke over the past few days (by that I mean keepass used to work fine, but not now).
When I say keepass is broken, I mean it won't start by way of a menu-item click; it won't start via file-association; it won't start via command-line.
From the command-line, my (stable, Gnome, systemd) terminal shows:
| Code: |
$ keepass -vvv
Unhandled Exception:
System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.ConsoleDriver..cctor () [0x0004d] in <ae60a710a4744d16826a514602b7b8ed>:0
--- End of inner exception stack trace ---
at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.Console..cctor () [0x0008e] in <ae60a710a4744d16826a514602b7b8ed>:0
--- End of inner exception stack trace ---
at KeePass.Program.ShowFatal (System.Exception ex) [0x0001c] in <c181e121d0524791a06c94345f9c687a>:0
at KeePass.Program.Main (System.String[] args) [0x0000c] in <c181e121d0524791a06c94345f9c687a>:0
[ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: The type initializer for 'System.Console' threw an exception. ---> System.TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception. ---> System.Exception: Magic number is wrong: 542
at System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) [0x00028] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.TermInfoReader..ctor (System.String term, System.String filename) [0x0005f] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.TermInfoDriver..ctor (System.String term) [0x00055] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.ConsoleDriver.CreateTermInfoDriver (System.String term) [0x00000] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.ConsoleDriver..cctor () [0x0004d] in <ae60a710a4744d16826a514602b7b8ed>:0
--- End of inner exception stack trace ---
at System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) [0x00007] in <ae60a710a4744d16826a514602b7b8ed>:0
at System.Console..cctor () [0x0008e] in <ae60a710a4744d16826a514602b7b8ed>:0
--- End of inner exception stack trace ---
at KeePass.Program.ShowFatal (System.Exception ex) [0x0001c] in <c181e121d0524791a06c94345f9c687a>:0
at KeePass.Program.Main (System.String[] args) [0x0000c] in <c181e121d0524791a06c94345f9c687a>:0
|
Googling further, it seems that maybe ncurses (or maybe mono?) are involved; I tried setting my TERM and reduced the error by 1/2 (got this idea from a forum):
| Code: |
$ TERM=xterm ; keepass -vvv
System.TypeInitializationException: The type initializer for 'System.Windows.Forms.XplatUI' threw an exception. ---> System.Net.Sockets.SocketException: Connection timed out
at System.Net.Sockets.Socket.Connect (System.Net.EndPoint remoteEP) [0x000b6] in <4229506c1c96445b8e95f2a8215a82f7>:0
at System.Windows.Forms.XplatUIX11.SetDisplay (System.IntPtr display_handle) [0x001ec] in <fe664b57a1b448b483fa7056430f4e32>:0
at System.Windows.Forms.XplatUIX11..ctor () [0x00077] in <fe664b57a1b448b483fa7056430f4e32>:0
at System.Windows.Forms.XplatUIX11.GetInstance () [0x00019] in <fe664b57a1b448b483fa7056430f4e32>:0
at System.Windows.Forms.XplatUI..cctor () [0x00066] in <fe664b57a1b448b483fa7056430f4e32>:0
--- End of inner exception stack trace ---
at System.Windows.Forms.Theme.get_MenuAccessKeysUnderlined () [0x00000] in <fe664b57a1b448b483fa7056430f4e32>:0
at System.Windows.Forms.SystemInformation.get_MenuAccessKeysUnderlined () [0x00005] in <fe664b57a1b448b483fa7056430f4e32>:0
at System.Windows.Forms.Control..ctor () [0x000e4] in <fe664b57a1b448b483fa7056430f4e32>:0
at (wrapper remoting-invoke-with-check) System.Windows.Forms.Control:.ctor ()
at System.Windows.Forms.WindowsFormsSynchronizationContext..cctor () [0x00000] in <fe664b57a1b448b483fa7056430f4e32>:0
|
Does anyone have suggestions, which will let my Gentoo desktop/workstation again work with my passwords?!?! TIA! |
|
| Back to top |
|
 |
Hieronymus Bosch
Tux's lil' helper
Joined: 29 Jan 2015
Posts: 83
Location: 31°45′33.14″N 106°29′24.63″W
|
| Posted: Thu May 10, 2018 11:44 pm Post subject: |
|
|
What version of Keepass ?
Did you try to install app-admin/keepasxc, at least to retrieve your passwords?
_________________
Details fueled any investigation ... |
|
| Back to top |
|
|
gordonp
Tux's lil' helper
Joined: 23 May 2005
Posts: 102
|
| Posted: Fri May 11, 2018 1:04 pm Post subject: |
|
|
My system is "stable", and the only Keepass in Portage is:
| Code: | | app-admin/keepass-2.38 |
Other stuff, which may/may_not be related:
| Code: | sys-libs/ncurses-6.1-r2
dev-lang/mono-4.8.0.524 |
I can still access my passwords - I keep the keepass file on a cloud-server, and have it available on cel-phones, tablets, laptops, etc. The problem is that my main all-day-long Gentoo workstation in my office is neutered, and this main workstation cannot be used productively right now 
In my experience, when one thing is broken like my keepass, it is likely there is a deeply-rooted problem which will rear it's head in other ways too. I'm stubborn  and would like to eliminate the underlying problem here. |
|
| Back to top |
|
|
Amity88
Apprentice
Joined: 03 Jul 2010
Posts: 260
Location: Third planet from the Sun
|
| Posted: Wed Sep 11, 2019 4:30 pm Post subject: |
|
|
If it may help, I have the exact same issue. It works under specific circumstances
1. When I run it from the terminal, I get the same set of errors as you listed.
2. When it's launched from the Awesome WM panel, it works fine. I'd assume that it's the same case if you launch it from any other gui panel. Give it a shot.
_________________
| Ant P. wrote: | | The enterprise distros sell their binaries. Canonical sells their users. |
Also... Be ignorant... Be happy! |
|
| Back to top |
|
|
xaviermiller
Bodhisattva
Joined: 23 Jul 2004
Posts: 8708
Location: ~Brussels - Belgique
|
| Posted: Wed Sep 11, 2019 5:40 pm Post subject: |
|
|
Hi,
A workaround is to use alternate versions as keepassxc
_________________
Kind regards,
Xavier Miller |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
