Bug 1245294

Summary: [abrt] nautilus: redo_layout_internal(): nautilus killed by SIGABRT
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ccecchi, ferdnyc, jkeen871, mclasen, miha.marolt, mikes, m, nuwanamila
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/29fbdcbdb2a31bf4d21dd3f425cd6a5b4d0a502f
Whiteboard: abrt_hash:1137f1abfe2444109c353cad4ccb7d9d6b70231f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:06:48 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 Brian J. Murrell 2015-07-21 16:57:08 UTC 
Description of problem:
Simply trying to start nautilus:

$ nautilus

** (nautilus:30636): CRITICAL **: Another desktop manager in use; desktop window won't be created
**
ERROR:nautilus-canvas-container.c:6118:finish_adding_new_icons: assertion failed: (!container->details->auto_layout)
Aborted (core dumped)

Killing nemo (the current desktop manager) and trying again did not help:

$ killall nemo
$ nautilus
**
ERROR:nautilus-canvas-container.c:6118:finish_adding_new_icons: assertion failed: (!container->details->auto_layout)
Aborted (core dumped)

Version-Release number of selected component:
nautilus-3.16.2-2.fc22

Additional info:
reporter:       libreport-2.6.1
backtrace_rating: 4
cmdline:        nautilus
crash_function: redo_layout_internal
executable:     /usr/bin/nautilus
global_pid:     30636
kernel:         4.0.8-300.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (5 frames)
 #4 redo_layout_internal at nautilus-canvas-container.c:6118
 #6 redo_layout at nautilus-canvas-container.c:1963
 #7 nautilus_canvas_container_sort at nautilus-canvas-container.c:7124
 #8 nautilus_canvas_view_clean_up_by_name at nautilus-canvas-view.c:329
 #9 nautilus_desktop_canvas_view_end_loading at nautilus-desktop-canvas-view.c:287
Comment 1 Brian J. Murrell 2015-07-21 16:57:10 UTC 
Created attachment 1054463 [details]
File: backtrace
Comment 2 Brian J. Murrell 2015-07-21 16:57:11 UTC 
Created attachment 1054464 [details]
File: cgroup
Comment 3 Brian J. Murrell 2015-07-21 16:57:12 UTC 
Created attachment 1054465 [details]
File: core_backtrace
Comment 4 Brian J. Murrell 2015-07-21 16:57:13 UTC 
Created attachment 1054466 [details]
File: dso_list
Comment 5 Brian J. Murrell 2015-07-21 16:57:13 UTC 
Created attachment 1054467 [details]
File: environ
Comment 6 Brian J. Murrell 2015-07-21 16:57:14 UTC 
Created attachment 1054468 [details]
File: limits
Comment 7 Brian J. Murrell 2015-07-21 16:57:15 UTC 
Created attachment 1054469 [details]
File: maps
Comment 8 Brian J. Murrell 2015-07-21 16:57:16 UTC 
Created attachment 1054470 [details]
File: mountinfo
Comment 9 Brian J. Murrell 2015-07-21 16:57:17 UTC 
Created attachment 1054471 [details]
File: namespaces
Comment 10 Brian J. Murrell 2015-07-21 16:57:18 UTC 
Created attachment 1054472 [details]
File: open_fds
Comment 11 Brian J. Murrell 2015-07-21 16:57:19 UTC 
Created attachment 1054473 [details]
File: proc_pid_status
Comment 12 Brian J. Murrell 2015-07-21 16:57:19 UTC 
Created attachment 1054474 [details]
File: var_log_messages
Comment 13 "FeRD" (Frank Dana) 2015-08-17 16:26:10 UTC 
Following a suggestion in this Arch forum discussion:
https://bbs.archlinux.org/viewtopic.php?id=196159

I found that moving my old $HOME/.config/nautilus out of the way solved this error. There appears to be something in (some) configs from older Nautilus releases that 3.16.2 can't deal with.
Comment 14 Michael Setzer II 2015-10-22 03:11:08 UTC 
I was getting an opps message with the nautilus on some machines in my lab, and at least in my case I've found what seems to be causing the error to occur on some machines while others work?? In the .config/nautilus direcotry there is a file call desktop-metadata. If one renames or deletes it, the error message goes away, on next login, and desktop-metadata file is recreated. I did a comparison of the file that caused the error, and the new one, and it appears to be a line that is missing, and not something that it doesn't deal with. Some lines had different timestamp or position values, but the line that was missing from the older version that caused the error is:

nautilus-desktop-icon-size=96
This is the 4th line from the beginning, and is under [directory] in my file??

Don't know why that not being there causes the oops error, or why the size is showing as 96?? But in my case it seems to just be that line that is missing that causes the issue? Not sure why, it just isn't added automatically if missing? or why the older version didn't have an issue with it.
Comment 15 Brian J. Murrell 2015-10-22 10:39:35 UTC 
Yes, I can confirm @Michael's discovery.  I do renamed that file and now nautilus starts.
Comment 16 Fedora End Of Life 2016-07-19 17:06:48 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.