Bug 649350 - [abrt] gvfs-smb-1.6.4-2.fc14: raise: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT) @ gkr_operation_block_and_unref
Summary: [abrt] gvfs-smb-1.6.4-2.fc14: raise: Process /usr/libexec/gvfsd-smb was kille...
Keywords:
Status: CLOSED DUPLICATE of bug 657179
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:83ad5ebd886de53e2d5fe2dfc21...
: 646669 648552 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-03 15:39 UTC by niels
Modified: 2015-03-03 22:54 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 19:28:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (15.32 KB, text/plain)
2010-11-03 15:39 UTC, niels
no flags Details

Description niels 2010-11-03 15:39:03 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/6
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-smb
kernel: 2.6.35.6-48.fc14.i686
package: gvfs-smb-1.6.4-2.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1288798715
uid: 500

Comment 1 niels 2010-11-03 15:39:08 UTC
Created attachment 457473 [details]
File: backtrace

Comment 2 Matthew Roccella 2010-11-06 10:39:27 UTC
Package: gvfs-smb-1.6.4-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I was updating my system while trying to connect to a remote server on my network.
2.
3.


Comment
-----
Click on System and then Connect to Server while the software updater was running.

Comment 3 Jeff Raber 2010-11-08 17:30:50 UTC
*** Bug 646669 has been marked as a duplicate of this bug. ***

Comment 4 Jeff Raber 2010-11-08 17:30:55 UTC
*** Bug 648552 has been marked as a duplicate of this bug. ***

Comment 5 Jeff Raber 2010-11-08 17:37:07 UTC
Adding a selection from the stack trace to make find this bug a little easier:

#0  0x00679416 in __kernel_vsyscall ()
#1  0x00b9e501 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
        resultvar = <value optimized out>
        resultvar = <value optimized out>
        pid = 13635572
        selftid = 8678
#2  0x00b9ff6e in abort () at abort.c:92
#3  0x00168c84 in g_assertion_message (domain=0x0, file=0x54ec1f3 "gkr-operation.c", line=401, func=0x54ec575 "gkr_operation_block_and_unref", message=<value optimized out>) at gtestutils.c:1358
        lstr = "401\000\371J7\266}>\033\000H\347\317\266X\337&\000\230W7\266\361|\276\000\215#\006"
        s = 0xb637b248 "@"
#4  0x001691ee in g_assertion_message_expr (domain=0x0, file=0x54ec1f3 "gkr-operation.c", line=401, func=0x54ec575 "gkr_operation_block_and_unref", expr=0x54ec2d5 "op->pending != pending") at gtestutils.c:1369
        s = 0xb6374ad0 "assertion failed: (op->pending != pending)"
#5  0x054dcc48 in gkr_operation_block_and_unref (op=0x859f0f0) at gkr-operation.c:401
        pending = 0xb6333580
        __PRETTY_FUNCTION__ = "gkr_operation_block_and_unref"
#6  0x054e6d53 in gnome_keyring_find_network_password_sync (...)

Comment 6 Stef Walter 2012-01-31 12:55:22 UTC
I think this should now be fixed, now that we initialize libdbus threading.

Here's the fix: http://git.gnome.org/browse/libgnome-keyring/commit/?id=e2f1f426eccafd3db4f0f2f22f561c2a8a204913

As a double check, which version of libgnome-keyring are you running?

Comment 7 abrt-bot 2012-03-20 19:28:01 UTC
Backtrace analysis found this bug to be similar to bug #657179, closing as duplicate.

Bugs which were found to be similar to this bug: bug #585657, bug #592649, bug #597371, bug #598081, bug #601013, bug #605005, bug #605239, bug #611351, bug #624899, bug #625287, bug #640849, bug #645129, bug #650318, bug #650428, bug #652139, bug #655115, bug #655586, bug #655703, bug #657179, bug #657631, bug #665054, bug #666201

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 657179 ***


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