| Summary: | [abrt] gnome-keyring-2.28.2-6.el6: Process /usr/bin/gnome-keyring-daemon was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Red Hat Case Diagnostics <case-diagnostics> | ||||
| Component: | gnome-keyring | Assignee: | Tomáš Bžatek <tbzatek> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.0 | CC: | m_roark, shei, swaikar, tsmetana | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:f6b63b2908e9f48b718f97316f1b6c90d93599b6 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-02-28 13:27:47 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Red Hat Case Diagnostics
2011-05-25 18:21:21 UTC
Created attachment 500907 [details]
File: backtrace
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. May I ask for a proper backtrace without unresolved symbols? This has happened to us since we upgraded to RHEL 6. At first, I did not have choice but to log out and log back in as the one who reported the problem did. Then we found a better workaround:
1) On any gnome-terminal, run /usr/bin/gnome-keyring-daemon and it will print out couple lines including one for SSH_AUTH_SOCK, say it's
SSH_AUTH_SOCK=/tmp/keyring-M7D3UA/socket.ssh
2) On any of your current gnome-terminal, do 'env | grep SSH_AUTH_SOCK'. Say you got:
SSH_AUTH_SOCK=/tmp/keyring-8Ymwr6/socket.ssh
3) Remove the one in step 2) and rename the one you got from step 1) to the one named in step 2):
rm -rf /tmp/keyring-8Ymwr6
mv /tmp/keyring-M7D3UA /tmp/keyring-8Ymwr6
The very first time when you ssh into a remote machine after performing these steps, it will pop a window asking you to enter your passphrase to unlock it. But you don't need to do it (enter your passphrase) anymore after that.
Tomáš, check out the service case 00540487 for couple bactraces (without unresolved symbols) I sent. Thanks.
|