** Description changed:
+ 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.4.2~hybrid0.0.1 0.4.2~hybrid0.1 in saucy).
+
+ * 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
+ 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)!
+ 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
- ?? ()
+ ?? () 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
** Changed in: cryptkeeper (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245621
Title:
cryptkeeper crashed with SIGSEGV in __libc_start_main()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptkeeper/+bug/1245621/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
