Bug 1278458

Created attachment 1090105 [details]
File: backtrace

Created attachment 1090106 [details]
File: cgroup

Created attachment 1090107 [details]
File: core_backtrace

Created attachment 1090108 [details]
File: dso_list

Created attachment 1090109 [details]
File: environ

Created attachment 1090110 [details]
File: exploitable

Created attachment 1090111 [details]
File: limits

Created attachment 1090112 [details]
File: maps

Created attachment 1090113 [details]
File: mountinfo

Created attachment 1090114 [details]
File: open_fds

Created attachment 1090115 [details]
File: proc_pid_status

Created attachment 1090116 [details]
File: var_log_messages

Another user experienced a similar problem:

Just click on a folder and it crashed.  Not doing anything special.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        nemo -n
crash_function: __strcmp_sse2_unaligned
executable:     /usr/bin/nemo
global_pid:     4519
kernel:         4.2.6-300.fc23.x86_64
package:        nemo-2.8.2-2.fc23
reason:         nemo killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Already have 2 tabs open then try to open one directory into a new tab and nemo crush.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/nemo
crash_function: __strcmp_sse2_unaligned
executable:     /usr/bin/nemo
global_pid:     7230
kernel:         4.2.6-301.fc23.x86_64
package:        nemo-2.8.5-1.fc23
reason:         nemo killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

open two directories in tabs and perform copy one directory sized 450MB. In the middle of the copy process, suddenly nemo crash.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        nemo /run/media/kris/Win7_X86X64_en-US_Mar2015
crash_function: __strcmp_sse2_unaligned
executable:     /usr/bin/nemo
global_pid:     3551
kernel:         4.2.8-300.fc23.x86_64
package:        nemo-2.8.6-1.fc23
reason:         nemo killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Crash occurred randomly in the background while I was using another program. 

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        nemo -n
crash_function: __strcmp_sse2_unaligned
executable:     /usr/bin/nemo
global_pid:     2749
kernel:         4.2.3-300.fc23.x86_64
package:        nemo-2.6.7-2.fc23
reason:         nemo killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.

Just had this issue on Fedora 25, with Cinnamon Desktop. It won't let me upload a stacktrace, but I had tried to open a file from a sftp connection with VS Code if that helps.

Here's the log from the error reporter, (not that I think it'll help much):

--- Running report_uReport ---
('report_uReport' completed successfully)

--- Running analyze_CCpp ---
Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES'
Querying server settings
Preparing an archive to upload
Uploading 4.7 MiB
Upload successful
Retrace job started
Analyzing crash data
Preparing environment for backtrace generation
...................
Generating backtrace
Retrace job finished successfully
Looking for similar problems in bugzilla
Duplicate bugzilla bug '#1278458' was found
Searching for updates
No updates for this package found

(In reply to NGupton98 from comment #19)
> Just had this issue on Fedora 25, with Cinnamon Desktop. It won't let me
> upload a stacktrace, but I had tried to open a file from a sftp connection
> with VS Code if that helps.
> 
> Here's the log from the error reporter, (not that I think it'll help much):
> 
> --- Running report_uReport ---
> ('report_uReport' completed successfully)
> 
> --- Running analyze_CCpp ---
> Ok to upload core dump? (It may contain sensitive data). If your answer is
> 'No', a stack trace will be generated locally. (It may download a huge
> amount of data). 'YES'
> Querying server settings
> Preparing an archive to upload
> Uploading 4.7 MiB
> Upload successful
> Retrace job started
> Analyzing crash data
> Preparing environment for backtrace generation
> ...................
> Generating backtrace
> Retrace job finished successfully
> Looking for similar problems in bugzilla
> Duplicate bugzilla bug '#1278458' was found
> Searching for updates
> No updates for this package found

Almost forgot, here is the FAF report from this: https://retrace.fedoraproject.org/faf/reports/1620770/