cryptkeeper crashed with SIGSEGV in __libc_start_main()

Bug #1245621 reported by Alberto Milone
156
This bug affects 30 people
Affects Status Importance Assigned to Milestone
cryptkeeper (Ubuntu)
Fix Released
Medium
Alberto Milone
Saucy
Fix Released
Medium
Alberto Milone

Bug Description

SRU request:

[Impact]

 * Something must have changed in the gtk+ libraries during Saucy's development
   cycle, thus causing cryptkeeper to segfault when launched. A simple no-change
   rebuild of the package seems to fix it. The package will still fail to launch
   from time to time (as it used to) but it will work fine most of the time.

[Test Case]

 * Enable the the saucy-proposed repository and install cryptkeeper (0.9.5-5.1ubuntu2.1).

 * If cryptkeeper can be launched (in, say, 2 or 3 attempts), then the fix is correct.

[Regression Potential]

 * The regression potential here is zero, as no change is involved.

-----------------------------

Launching cryptkeeper after a clean boot causes cryptkeeper to segfault

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: cryptkeeper 0.9.5-5.1ubuntu2
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
Architecture: amd64
Date: Mon Oct 28 19:33:02 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/cryptkeeper
ExecutableTimestamp: 1368445312
InstallationDate: Installed on 2012-11-16 (345 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121017.3)
MarkForUpload: True
ProcCmdline: cryptkeeper
ProcCwd: /home/alberto
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3bc57ef9c5: cmp %rsi,(%rdx)
 PC (0x7f3bc57ef9c5) ok
 source "%rsi" ok
 destination "(%rdx)" (0xcc8941c931455441) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: cryptkeeper
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
 ?? ()
 ?? ()
 __libc_start_main (main=0x405680, argc=1, ubp_av=0x7fff3a76b438, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3a76b428) at libc-start.c:260
 ?? ()
Title: cryptkeeper crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-10-06 (22 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alberto Milone (albertomilone) wrote :
Changed in cryptkeeper (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1228785, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
Changed in cryptkeeper (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
description: updated
Changed in cryptkeeper (Ubuntu):
status: Confirmed → In Progress
description: updated
Revision history for this message
Alberto Milone (albertomilone) wrote :

The SRU request is in the description.

Revision history for this message
Colin Watson (cjwatson) wrote :

cryptkeeper (0.9.5-5.1ubuntu3) trusty; urgency=low

  * No change rebuild. It should fix some random segfaults.

 -- Alberto Milone <email address hidden> Mon, 04 Nov 2013 19:15:13 +0100

Changed in cryptkeeper (Ubuntu):
status: In Progress → Fix Released
Changed in cryptkeeper (Ubuntu Saucy):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Alberto Milone (albertomilone)
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Colin Watson (cjwatson) wrote : Please test proposed package

Hello Alberto, or anyone else affected,

Accepted cryptkeeper into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cryptkeeper/0.9.5-5.1ubuntu2.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Holger (holger-burkhardt) wrote :

The package in proposed workes for me. With regular saucy, cryptkeeper crashed on start, with saucy-proposed, it starts alright! (Though I do not see were I should change the tag to verification-done.....

before:

$ dpkg -l | grep cryptk
ii cryptkeeper 0.9.5-5.1ubuntu2 amd64 EncFS system tray applet for GNOME

after (saucy-proposed):
$ dpkg -l | grep cryptk
ii cryptkeeper 0.9.5-5.1ubuntu2.1 amd64 EncFS system tray applet for GNOME

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cryptkeeper - 0.9.5-5.1ubuntu2.1

---------------
cryptkeeper (0.9.5-5.1ubuntu2.1) saucy-proposed; urgency=low

  * No change rebuild. This fixes a segfault on launch (LP: #1245621).
 -- Alberto Milone <email address hidden> Tue, 05 Nov 2013 11:39:35 +0100

Changed in cryptkeeper (Ubuntu Saucy):
status: Fix Committed → Fix Released
Revision history for this message
Stéphane Graber (stgraber) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Ludek (lusmo) wrote :

This proble still resist (from Ubuntu 13.04 -> 13.10 -> 14.10 /64bit)

Revision history for this message
Swift (frano-toich) wrote :

This problem still persists with 14.04 64 bit.

Revision history for this message
Stego (stegomon) wrote :

This problem still persists for me too with 14.04 64 bit.

Revision history for this message
Mike O'Connor (hu6hzq0zv8rdv031e6-michael-t16qijz8x59bnuup59) wrote :

ditto. 14.04 64 bit. core dump on startup..

Revision history for this message
sfc (sfc-0) wrote :

14.04 64bit. still segfault on startup...

Revision history for this message
tionov (christof-deganius) wrote :

Same here: Linux myx200 3.11.0-20-generic #35-Ubuntu SMP Fri May 2 21:32:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Ludek (lusmo) wrote :

Still crashed. U 14.04 64 bti..

Revision history for this message
Max (maxter) wrote :

Confirmed in trusty

Revision history for this message
Chugajstyr (chugajstyr) wrote :

Mint 17 (ubuntu 14.04 based) mostly crashed. Sometimes started...

Revision history for this message
Andrey Konstantinov (andreyinvolute) wrote :

Same here, Ubuntu 14.04 64-bit, 3.13.0-29-generic.

Revision history for this message
bpowell (bpowell2008) wrote :

14.04 64-bit...crashes when launced from Unity...works from terminal

Revision history for this message
Lasse (locknevi) wrote :

Cryptkeeper always crashes when started from gui, cinnamon.
If I start cryptkeepr from command line it often starts and I get the icon in the panel and can successfully use Cryptkeeper
( core dumped)

- Linux Mint, Cinnamon
- cryptkeeper 0.9.5-5.1ubuntu3 amd64 EncFS system tray applet for GNOME
- DISTRIB_DESCRIPTION="Linux Mint 17 Qiana"
- 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
timelf123 (timelf123) wrote :

6 times is the charm apparently. When starting from GUI it fails every time. Finally got it to launch via cmd line:

➜ cryptkeeper
[1] 10557 segmentation fault (core dumped) cryptkeeper
➜ cryptkeeper
[1] 10571 segmentation fault (core dumped) cryptkeeper
➜ cryptkeeper
[1] 10585 segmentation fault (core dumped) cryptkeeper
➜ cryptkeeper
[1] 10599 segmentation fault (core dumped) cryptkeeper
➜ cryptkeeper
[1] 10613 segmentation fault (core dumped) cryptkeeper
➜ cryptkeeper

(cryptkeeper:10627): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed

Revision history for this message
Ludek (lusmo) wrote :

Same here: Ubuntu 14.04, 14.10 64 bit :-(

Revision history for this message
Ludek (lusmo) wrote :

ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
sludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper
Neoprávněný přístup do paměti (SIGSEGV) (core dumped [obraz paměti uložen])
ludek@TravelMate-8471:~/Plocha$ cryptkeeper

(cryptkeeper:12020): Gtk-CRITICAL **: gtk_box_pack: assertion 'GTK_IS_WIDGET (child)' failed

Revision history for this message
dronus (paul-geisler) wrote :

Still affects 14.04 LTS 64bit.

Please add all possible stale builds from the cryptkeeper sources to this bug!

We're only fine if any binary package is running well.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.