Bug 1040763 - [abrt] nautilus-3.10.1-2.fc20: vasprintf: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Summary: [abrt] nautilus-3.10.1-2.fc20: vasprintf: Process /usr/bin/nautilus was kille...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:a79bc4fa98f118af82a0dae2177...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 04:51 UTC by Frederick Grose
Modified: 2015-06-29 13:28 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:28:57 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (268.82 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: cgroup (172 bytes, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: core_backtrace (17.88 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: dso_list (11.79 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: environ (2.01 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: exploitable (82 bytes, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: maps (59.59 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: open_fds (2.00 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: proc_pid_status (902 bytes, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details
File: var_log_messages (1.16 KB, text/plain)
2013-12-12 04:51 UTC, Frederick Grose
no flags Details

Description Frederick Grose 2013-12-12 04:51:03 UTC
Description of problem:
0. running in a Live USB image,
1. launched nautilus at command line with sudo nautilus,
2. navigated to a folder /var/spool
3. tried to resize the window from the right border (or possibly resize a column in the file listing)
4. abrt reported the problem

Version-Release number of selected component:
nautilus-3.10.1-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        nautilus
crash_function: vasprintf
executable:     /usr/bin/nautilus
kernel:         3.11.10-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 vasprintf at /usr/include/bits/stdio2.h:210
 #3 g_vasprintf at gprintf.c:314
 #4 g_strdup_vprintf at gstrfuncs.c:517
 #5 g_strdup_printf at gstrfuncs.c:543
 #6 synch_user_menu at nautilus-properties-window.c:2021
 #7 attach_owner_combo_box at nautilus-properties-window.c:2052
 #8 create_simple_permissions at nautilus-properties-window.c:4213
 #9 create_permissions_page at nautilus-properties-window.c:4562
 #10 create_properties_window at nautilus-properties-window.c:4934
 #11 is_directory_ready_callback at nautilus-properties-window.c:5079

Potential duplicate: bug 902077

Comment 1 Frederick Grose 2013-12-12 04:51:07 UTC
Created attachment 835582 [details]
File: backtrace

Comment 2 Frederick Grose 2013-12-12 04:51:08 UTC
Created attachment 835583 [details]
File: cgroup

Comment 3 Frederick Grose 2013-12-12 04:51:10 UTC
Created attachment 835584 [details]
File: core_backtrace

Comment 4 Frederick Grose 2013-12-12 04:51:11 UTC
Created attachment 835585 [details]
File: dso_list

Comment 5 Frederick Grose 2013-12-12 04:51:12 UTC
Created attachment 835586 [details]
File: environ

Comment 6 Frederick Grose 2013-12-12 04:51:14 UTC
Created attachment 835587 [details]
File: exploitable

Comment 7 Frederick Grose 2013-12-12 04:51:15 UTC
Created attachment 835588 [details]
File: limits

Comment 8 Frederick Grose 2013-12-12 04:51:16 UTC
Created attachment 835589 [details]
File: maps

Comment 9 Frederick Grose 2013-12-12 04:51:18 UTC
Created attachment 835590 [details]
File: open_fds

Comment 10 Frederick Grose 2013-12-12 04:51:19 UTC
Created attachment 835591 [details]
File: proc_pid_status

Comment 11 Frederick Grose 2013-12-12 04:51:20 UTC
Created attachment 835592 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-05-29 09:58:18 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Comment 13 Fedora End Of Life 2015-06-29 13:28:57 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.