Bug 892610 - [abrt] mate-keyring-1.5.0-2.fc18: _dbus_abort: Process /usr/bin/mate-keyring-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] mate-keyring-1.5.0-2.fc18: _dbus_abort: Process /usr/bin/mate-keyring-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a827bac40ee0aa4cad9133481ec...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 11:55 UTC by Sam Tygier
Modified: 2013-04-11 10:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-11 10:08:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (14.17 KB, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: cgroup (126 bytes, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: core_backtrace (1.62 KB, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: dso_list (2.51 KB, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: environ (1.56 KB, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: maps (12.79 KB, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: open_fds (544 bytes, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: proc_pid_status (927 bytes, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details
File: var_log_messages (694 bytes, text/plain)
2013-01-07 11:55 UTC, Sam Tygier
no flags Details

Description Sam Tygier 2013-01-07 11:55:33 UTC
Description of problem:
empathy was asking for a password. the keyring dialog came up. I entered my keyring password several times, but each time it was rejected.

Version-Release number of selected component:
mate-keyring-1.5.0-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/mate-keyring-daemon --start --components=pkcs11
crash_function: _dbus_abort
executable:     /usr/bin/mate-keyring-daemon
kernel:         3.6.11-3.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #2 _dbus_abort at dbus-sysdeps.c:94
 #3 _dbus_warn_check_failed at dbus-internals.c:290
 #4 dbus_message_new_signal at dbus-message.c:1353
 #5 mark_as_complete at gkd-secret-unlock.c:133
 #7 on_unlock_complete at gkd-secret-unlock.c:177
 #8 process_result at gck-call.c:153
 #9 process_completed at gck-call.c:167
 #10 completed_dispatch at gck-call.c:199

Comment 1 Sam Tygier 2013-01-07 11:55:36 UTC
Created attachment 673951 [details]
File: backtrace

Comment 2 Sam Tygier 2013-01-07 11:55:40 UTC
Created attachment 673952 [details]
File: cgroup

Comment 3 Sam Tygier 2013-01-07 11:55:42 UTC
Created attachment 673953 [details]
File: core_backtrace

Comment 4 Sam Tygier 2013-01-07 11:55:44 UTC
Created attachment 673954 [details]
File: dso_list

Comment 5 Sam Tygier 2013-01-07 11:55:46 UTC
Created attachment 673955 [details]
File: environ

Comment 6 Sam Tygier 2013-01-07 11:55:48 UTC
Created attachment 673956 [details]
File: limits

Comment 7 Sam Tygier 2013-01-07 11:55:50 UTC
Created attachment 673957 [details]
File: maps

Comment 8 Sam Tygier 2013-01-07 11:55:52 UTC
Created attachment 673958 [details]
File: open_fds

Comment 9 Sam Tygier 2013-01-07 11:55:53 UTC
Created attachment 673959 [details]
File: proc_pid_status

Comment 10 Sam Tygier 2013-01-07 11:55:56 UTC
Created attachment 673960 [details]
File: var_log_messages

Comment 11 Dan Mashal 2013-02-22 04:30:59 UTC
This is not a mate-keyring bug. I was also not able to reproduce the crash.

Empathy is loaded with issues and is meant to be run in Gnome. If you are using MATE please use Pidgin (it should be included).

.xsession-errors:

** (empathy-accounts:1717): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
OpenGL Warning: crPixelCopy3D:  simply crMemcpy'ing from srcPtr to dstPtr
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4600007 (Messaging )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.




Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000007 (Contact Li)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(empathy:1500): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

Comment 12 Dan Mashal 2013-03-26 10:31:26 UTC
Hopefully this update helps.

Comment 13 Fedora Update System 2013-03-26 10:32:03 UTC
mate-keyring-1.5.1-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mate-keyring-1.5.1-1.fc18

Comment 14 Fedora Update System 2013-03-27 00:49:23 UTC
Package mate-keyring-1.5.1-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mate-keyring-1.5.1-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4468/mate-keyring-1.5.1-1.fc18
then log in and leave karma (feedback).

Comment 15 Fedora Update System 2013-04-11 10:08:32 UTC
mate-keyring-1.5.1-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.