Bug 1032853

Summary: [abrt] mate-file-manager-1.6.3-0.7.gitbf47018.fc18: get_iter_from_path: Process /usr/bin/caja was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alexey Kardashevskiy <aik>
Component: mate-file-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dan.mashal, fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e0a9ecf2f87ef653fb2acee2cdcdb4c1f6e651f6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-01 09:29:10 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 Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Alexey Kardashevskiy 2013-11-21 02:58:40 UTC 
Description of problem:
I attached laptop (Lenovo Thinkpad x230) to port replicator, plugged external display cable into the laptop's mini-dvi port (the replicator does not have DVI), waited a bit - and Caja crashed.
And this happens every morning.

Version-Release number of selected component:
mate-file-manager-1.6.3-0.7.gitbf47018.fc18

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        caja -n
crash_function: get_iter_from_path
executable:     /usr/bin/caja
kernel:         3.11.4-101.fc18.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 get_iter_from_path at bluetooth-client.c:342
 #1 device_services_changed at bluetooth-client.c:400
 #2 marshal_dbus_message_to_g_marshaller at dbus-gproxy.c:1736
 #7 dbus_g_proxy_emit_remote_signal at dbus-gproxy.c:1789
 #8 dbus_g_proxy_manager_filter at dbus-gproxy.c:1356
 #16 gtk_main at gtkmain.c:1257
Comment 1 Alexey Kardashevskiy 2013-11-21 02:58:44 UTC 
Created attachment 826945 [details]
File: backtrace
Comment 2 Alexey Kardashevskiy 2013-11-21 02:58:47 UTC 
Created attachment 826946 [details]
File: cgroup
Comment 3 Alexey Kardashevskiy 2013-11-21 02:58:51 UTC 
Created attachment 826947 [details]
File: core_backtrace
Comment 4 Alexey Kardashevskiy 2013-11-21 02:58:54 UTC 
Created attachment 826948 [details]
File: dso_list
Comment 5 Alexey Kardashevskiy 2013-11-21 02:58:58 UTC 
Created attachment 826949 [details]
File: environ
Comment 6 Alexey Kardashevskiy 2013-11-21 02:59:01 UTC 
Created attachment 826950 [details]
File: exploitable
Comment 7 Alexey Kardashevskiy 2013-11-21 02:59:04 UTC 
Created attachment 826951 [details]
File: limits
Comment 8 Alexey Kardashevskiy 2013-11-21 02:59:08 UTC 
Created attachment 826952 [details]
File: maps
Comment 9 Alexey Kardashevskiy 2013-11-21 02:59:13 UTC 
Created attachment 826953 [details]
File: open_fds
Comment 10 Alexey Kardashevskiy 2013-11-21 02:59:17 UTC 
Created attachment 826954 [details]
File: proc_pid_status
Comment 11 Alexey Kardashevskiy 2013-11-21 02:59:20 UTC 
Created attachment 826955 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2013-11-21 10:05:14 UTC 
Backtrace pointed me to a prob with a bluetooth device.
Are you using bluetooth?
Can you disable/disconect any bluetooth device?
What does the port replicator do?
Comment 13 Alexey Kardashevskiy 2013-11-21 13:02:50 UTC 
I am using bluetooth keyboard Microsoft mobile 5000.
If I do not use bluetooth keyboard (like when I bring laptop home), no crash happens.
The port replicator is basically a USB hub.

I guess you are making a good point about bluetooth as I am having continuous issues with it such as I cannot have both bluetooth mouse and keyboard - when they go standby, 50% of cases one of them cannot reconnect, instead dmesg is full of backtraces from bluetooth hid driver so I ended up using just a keyboard (not because it is bluetooth but because it is tiny, "natural" and has no keypad :) ).
Comment 14 Wolfgang Ulbrich 2013-11-21 13:35:23 UTC 
Ok, to be shure that the issue wasn't caused by mate-bluetooth and mate-user-share, which use mate-bluetooth, can you uninstall both and test again with your bluetooth keyboard?