Bug in nvidia-tls (295.20) causes Evolution to segfault

[Julian Rüger]

I'm using LMDE UP4 x86_64, with MATE, Evolution 3.2.2-1 and nvidia-drivers 295.20.

I set up Evolution using a backup-archive created by Evolution 2.32.2-0ubuntu7 (from 11.04).

Output:
$ evolution

(evolution:22359): camel-CRITICAL **: camel_session_add_service: assertion `uri_string != NULL' failed
e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: Keine passenden Ergebnisse)

(evolution:22359): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: Keine passenden Ergebnisse)
Speicherzugriffsfehler

Translation from German:
"(Keyring reports: No matching results)
Segmentation fault"

EDIT: As explained in comment #2, the mate- or gnome-keyring has nothing to do with this crash, it's a known bug in the nvidia-tls component.

[Julian Rüger (jr98)]

Sorry, forgot to mention that this is on 64-bits.

[Julian Rüger (jr98)]

I did some more digging and found out that this crash has actually nothing to do with keyring-issues.

http://verahill.blogspot.de/2012/02/debian-testing-wheezy-64-no-real.html

The reason is a bug in nvidia-tls, my nvidia-driver version is 295.20. /var/log/messages contains lines like [151646.170771] evolution[29275]: segfault at 10 ip 00007fd65a95ac0f sp 00007fd63efbe508 error 6 in libnvidia-tls.so.295.20[7fd65a95a000+3000]

The workaround described on lindqvist's blog does the trick: starting evolution with strace:

$ strace -o evolution.log evolution

So, what should I do about this bug report? It looks like the Debian folks already know about the issue.

[Jack Knight (hackinjack)]

identical behavior seen here.

 LMDE UP4 x86_64, with MATE, Evolution 3.2.2-1 and nvidia-drivers - 64 bit

295.20-1

nVidia Corporation GT218 [GeForce 210] (rev a2)

behaves fine when run under strace

[Jack Knight (hackinjack)]

as a workaround I'm using:

    strace -e none evolution