Bug 1251714

Summary: [abrt] caja: g_type_check_instance(): caja killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Brandon Amaro <omega13a>
Component: cajaAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fedora, omega13a
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1f551ac36044ca70c87f363d3f10d7e24eb9b212
Whiteboard: abrt_hash:df3fba49a8e1b152987f6bb0c5b553f0edf776aa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:25:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brandon Amaro 2015-08-09 03:40:13 UTC 
Description of problem:
I was trying to copy and paste a couple of files over my local network.

Version-Release number of selected component:
caja-1.10.3-1.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        caja
crash_function: g_type_check_instance
executable:     /usr/bin/caja
global_pid:     1995
kernel:         4.1.3-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_type_check_instance at gtype.c:4134
 #1 g_signal_connect_data at gsignal.c:2411
 #2 set_pending_icon_to_reveal at caja-icon-container.c:655
 #3 end_renaming_mode at caja-icon-container.c:9211
 #4 button_press_event at caja-icon-container.c:4706

Potential duplicate: bug 1147289
Comment 1 Brandon Amaro 2015-08-09 03:40:16 UTC 
Created attachment 1060680 [details]
File: backtrace
Comment 2 Brandon Amaro 2015-08-09 03:40:17 UTC 
Created attachment 1060681 [details]
File: cgroup
Comment 3 Brandon Amaro 2015-08-09 03:40:18 UTC 
Created attachment 1060682 [details]
File: core_backtrace
Comment 4 Brandon Amaro 2015-08-09 03:40:19 UTC 
Created attachment 1060683 [details]
File: dso_list
Comment 5 Brandon Amaro 2015-08-09 03:40:20 UTC 
Created attachment 1060684 [details]
File: environ
Comment 6 Brandon Amaro 2015-08-09 03:40:21 UTC 
Created attachment 1060685 [details]
File: limits
Comment 7 Brandon Amaro 2015-08-09 03:40:24 UTC 
Created attachment 1060686 [details]
File: maps
Comment 8 Brandon Amaro 2015-08-09 03:40:25 UTC 
Created attachment 1060687 [details]
File: mountinfo
Comment 9 Brandon Amaro 2015-08-09 03:40:26 UTC 
Created attachment 1060688 [details]
File: namespaces
Comment 10 Brandon Amaro 2015-08-09 03:40:27 UTC 
Created attachment 1060689 [details]
File: open_fds
Comment 11 Brandon Amaro 2015-08-09 03:40:27 UTC 
Created attachment 1060690 [details]
File: proc_pid_status
Comment 12 Brandon Amaro 2015-08-09 03:40:28 UTC 
Created attachment 1060691 [details]
File: var_log_messages
Comment 13 Brandon Amaro 2015-10-18 06:37:22 UTC 
Another user experienced a similar problem:

I deselected a file after deciding not to rename it.

reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        caja
crash_function: g_type_check_instance
executable:     /usr/bin/caja
global_pid:     11177
kernel:         4.2.3-200.fc22.x86_64
package:        caja-1.10.4-1.fc22
reason:         caja killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Brandon Amaro 2016-02-04 21:48:22 UTC 
Another user experienced a similar problem:

I went to go rename a file and then changed my mind.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        caja
crash_function: g_type_check_instance
executable:     /usr/bin/caja
global_pid:     1921
kernel:         4.2.8-200.fc22.x86_64
package:        caja-1.12.2-2.fc22
reason:         caja killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 Brandon Amaro 2016-05-12 03:52:30 UTC 
Similar problem has been detected:

I was renaming a file, got interupted and didn't get back to the computer for a few hours. When I did, I forgot what I was going to rename the file so I deselected it. That's when Caja froze and then crashed.

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        caja
crash_function: g_type_check_instance
executable:     /usr/bin/caja
global_pid:     20677
kernel:         4.4.6-201.fc22.x86_64
package:        caja-1.12.7-1.fc22
reason:         caja killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 Brandon Amaro 2016-06-10 03:56:17 UTC 
Similar problem has been detected:

I was trying to rename a directory I just created

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        caja
crash_function: g_type_check_instance
executable:     /usr/bin/caja
global_pid:     2498
kernel:         4.4.11-200.fc22.x86_64
package:        caja-1.12.7-2.fc22
reason:         caja killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 17 Fedora End Of Life 2016-07-19 17:25:40 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.