You are not logged in.

#1 2013-10-28 18:01:36

disjunkt
Member
From: Germany
Registered: 2013-06-23
Posts: 23

[Solved] Log in problem with at least two programms

Hi community,

once in a while I still need your help. This time I'm no longer able to log into my password manager KeePassX. When I start KeePassX I'm promtet to enter the passphrase for the password container. When I start typing the cursor stops blinking, nothing happens for a second and than KeePassX crashes. It's all the same with Spotify when I try to enter my user name.

I already asked almighty Google for a solutions, but I didn't get one. Supposedly that's because it's not a problem of KeePassX or Spotify but of another programm that's employed by both of them.

So I'd be glad if anyone could push me in the right direction to find the cause of the problem that bars me from listening to my music.

Regards
disjunkt

Last edited by disjunkt (2013-11-15 14:51:43)

Offline

#2 2013-10-29 01:26:32

stqn
Member
Registered: 2010-03-19
Posts: 1,191
Website

Re: [Solved] Log in problem with at least two programms

Both keepassx and spotify use qt4. Do you have similar problems with your other Qt applications?
Is your system fully up to date?
KeepassX works fine here.
You could try to run them from the terminal to see if there’s any error message. You can also use strace or maybe gdb to see where they are failing.

Offline

#3 2013-10-29 12:27:03

disjunkt
Member
From: Germany
Registered: 2013-06-23
Posts: 23

Re: [Solved] Log in problem with at least two programms

VLC has the same problem. As soon as I press any key VLC crashes. Using the mouse doesn't crash those programms.

My system is not fully up to date, as I don't have a acceptable internet connection here. But the error occures at least since the weekend before last and I updated my system last saturday. I can update my system next weekend again at the earliest.

If I start one of the affected programms from the termnal, I'll get the error message: Bus error (core dumped)

Where is the core dumped and can I obtain more information about the crash from the dump?

Offline

#4 2013-10-29 13:50:09

stqn
Member
Registered: 2010-03-19
Posts: 1,191
Website

Re: [Solved] Log in problem with at least two programms

You’ll have to use systemd-coredumpctl for that, or simpler, just start the program with gdb.

Offline

#5 2013-11-15 14:51:06

disjunkt
Member
From: Germany
Registered: 2013-06-23
Posts: 23

Re: [Solved] Log in problem with at least two programms

Well, that's weird. I installed gdb but did't have a clue what to do with that programm. Thinks were going to add up to some further reading and for lack of time that is why I quit trying to find out, what was happening on my machine for a few days. Today, the problem still exists, I started tackling it again.

Reading the man page of gdb was anything but a helpful tutorial, so I decided to give systemd-coredumpctl a try befor I search the web for a gdb tutorial. Starting systemd-coredumpctl without any optoins gets me the message: "No coredump found". Hmm, just a minute earlier KeePassX crashed with a core dump, so why would't it be found?

Just to provoke a new coredump I started KeePassX again and no error occured. A little bit confused I started Spotify as well and it works fine as well.

I absolutely do not have a clue, what happened. systemd-coredumpctl doesn't fix any problems independently, does is? However, the problem seems to be fixed. Thank you for your help anyway!

Offline

#6 2013-11-15 16:08:22

stqn
Member
Registered: 2010-03-19
Posts: 1,191
Website

Re: [Solved] Log in problem with at least two programms

Thanks to the extreme intelligence of the authors of systemd, systemd-coredumpctl needs to be run as root in order to get a normal user’s core dumps. Anyway, you’ll have to know how to use gdb in order to inspect the core file, and if the binaries do not contain debug information it will probably not be very helpful…

Just a very short gdb tutorial:
- type "gdb vlc"
- type "run"
- once vlc has crashed, type "bt" to get a backtrace.

This should show you where the crash happened.

Offline

Board footer

Powered by FluxBB