cryptkeeper segfault when started

Bug #1404748 reported by zebul666 on 2014-12-21
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
cryptkeeper (Ubuntu)
Medium
Unassigned

Bug Description

cryptkeeper is not even useable as it segfault as soon it is started. Please fix this.

in /var/log/syslog

Dec 21 23:33:17 callisto kernel: [20768.476774] traps: cryptkeeper[15994] general protection ip:7fe834d6f55a sp:7fff171760c0 error:0 in libgtk-x11-2.0.so.0.2400.25[7fe834ceb000+440000]

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: cryptkeeper 0.9.5-5.1ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 21 23:36:40 2014
InstallationDate: Installed on 2014-01-22 (333 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: cryptkeeper
UpgradeStatus: Upgraded to utopic on 2014-10-24 (58 days ago)

zebul666 (zebul666) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in cryptkeeper (Ubuntu):
status: New → Confirmed
Stefan Seifried (s-seifried) wrote :

same here on Linux Mint with MATE desktop

Andreas Moog (ampelbein) wrote :

FWIW, I can't reproduce this is 15.04.

Changed in cryptkeeper (Ubuntu):
importance: Undecided → Medium
Hieronymus (hieronymusch) wrote :

Kubuntu 14.10

with the following output running cryptkeeper via gdb:

(gdb) run
Starting program: /usr/local/bin/cryptkeeper
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffef622700 (LWP 7552)]
[New Thread 0x7fffeee21700 (LWP 7553)]

Program received signal SIGSEGV, Segmentation fault.
read_config () at main.cpp:834
834 if (*next) *(next++) = '\0';

S. W. (muell-7) wrote :

Same here on 14.04.3. GDB says:

Starting program: /usr/bin/cryptkeeper
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffedfda700 (LWP 8920)]
[New Thread 0x7fffed7d9700 (LWP 8921)]
[New Thread 0x7fffe7fff700 (LWP 8922)]
[New Thread 0x7fffe500c700 (LWP 8923)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff782092d in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers