Bug 1031233

Created attachment 824763 [details]
File: backtrace

Created attachment 824764 [details]
File: cgroup

Created attachment 824765 [details]
File: core_backtrace

Created attachment 824766 [details]
File: dso_list

Created attachment 824767 [details]
File: environ

Created attachment 824768 [details]
File: exploitable

Created attachment 824769 [details]
File: limits

Created attachment 824770 [details]
File: maps

Created attachment 824771 [details]
File: open_fds

Created attachment 824772 [details]
File: proc_pid_status

Created attachment 824773 [details]
File: var_log_messages

*** Bug 1036094 has been marked as a duplicate of this bug. ***

*** Bug 1013430 has been marked as a duplicate of this bug. ***

*** Bug 1100996 has been marked as a duplicate of this bug. ***

Can you tell me what Actions you have installed?

They'll either be in /usr/share/nemo/actions or ~/.local/share/nemo/actions

Specifically looking for any additional you may have installed (besides what came with Nemo).  If there are 3rd party actions, would you mind attaching the .nemo_action files?

Thanks

I'm not sure which one of these are additional actions.

$ ls -la /usr/share/nemo/actions/
total 44
drwxr-xr-x. 2 root root 4096 Jun  3 13:10 .
drwxr-xr-x. 4 root root 4096 Jun  3 13:10 ..
-rw-r--r--. 1 root root  216 May 21 14:03 add-desklets.nemo_action
-rw-r--r--. 1 root root  251 May 21 14:03 change-background.nemo_action
-rw-r--r--. 1 root root  363 May 21 14:03 mount-archive.nemo_action
-rwxr-xr-x. 1 root root  214 May 21 14:03 myaction.py
-rw-r--r--. 2 root root  312 May 21 14:03 myaction.pyc
-rw-r--r--. 2 root root  312 May 21 14:03 myaction.pyo
-rw-r--r--. 1 root root  241 May 21 14:03 new-launcher.nemo_action
-rw-r--r--. 1 root root 3327 May 21 14:03 sample.nemo_action
-rw-r--r--. 1 root root  231 May 21 14:03 set-as-background.nemo_action

Do you need more info besides that?

Those look ok - were there any in ~/.local/share/nemo/actions ?

I think I found the problem anyhow, but this may be one of those 'fix blindly' problems, as I can't reproduce this for myself, so I'd hope to rule everything else out first.

Thanks

Oh i forgot to copy that. ~/.local/share/nemo/actions is empty:
$ ls -la .local/share/nemo/actions/
total 8
drwxr-xr-x. 2 lb lb 4096 Feb  5 11:33 .
drwxr-xr-x. 3 lb lb 4096 Feb  5 11:33 ..

Another user experienced a similar problem:

it crashed and closed all the instances

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        nemo -n
crash_function: recalc_dbus_conditions
executable:     /usr/bin/nemo
kernel:         3.14.5-200.fc20.x86_64
package:        nemo-2.2.2-1.fc20
reason:         nemo killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

(In reply to vikram goyal from comment #19)
> Another user experienced a similar problem:
> 
> it crashed and closed all the instances
> 
> reporter:       libreport-2.2.2
> backtrace_rating: 4
> cmdline:        nemo -n
> crash_function: recalc_dbus_conditions
> executable:     /usr/bin/nemo
> kernel:         3.14.5-200.fc20.x86_64
> package:        nemo-2.2.2-1.fc20
> reason:         nemo killed by SIGSEGV
> runlevel:       N 5
> type:           CCpp
> uid:            1000

Can you reproduce with nemo-2.2.2-4.fc20 + (nemo-2.2.3-1.fc20 is current)?

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

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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.

thanks