Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 659810

Summary: [abrt] nautilus-2.28.4-15.el6: brasero_io_return_result_idle: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Product: Red Hat Enterprise Linux 6 Reporter: Ben Woodard <woodard>
Component: braseroAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: azelinka, syeghiay, tsmetana
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f9c1028f6c8b35bdaf7364505b290e49a37fe35d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-25 15:52:17 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

Description Ben Woodard 2010-12-03 18:58:28 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: nautilus
component: nautilus
crash_function: brasero_io_return_result_idle
executable: /usr/bin/nautilus
kernel: 2.6.32-71.el6.x86_64
package: nautilus-2.28.4-15.el6
rating: 4
reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux release 6.0 (Santiago)
time: 1291402500
uid: 500

How to reproduce
-----
1. Dragged the ISO for RHEL6 onto the blank CD icon.
2. It asked me if I wanted to burn its contents or a file I said contents
3. hit OK and the world went away.

Comment 1 Ben Woodard 2010-12-03 18:58:30 UTC
Created attachment 464629 [details]
File: backtrace

Comment 2 Ben Woodard 2010-12-03 19:01:33 UTC
Package: nautilus-2.28.4-15.el6
Architecture: x86_64
OS Release: Red Hat Enterprise Linux release 6.0 (Santiago)


How to reproduce
-----
1. same as before just wanted to see if it was reproducible.
2.
3.

Comment 4 Ben Woodard 2010-12-25 19:49:41 UTC
Package: nautilus-2.28.4-15.el6
Architecture: x86_64
OS Release: Red Hat Enterprise Linux release 6.0 (Santiago)


How to reproduce
-----
1. Tried to burn a fedora CD
2. said burn as contents vs burn as file.
3.

Comment 6 Tomáš Bžatek 2011-01-14 17:20:57 UTC
*** Bug 635993 has been marked as a duplicate of this bug. ***

Comment 7 Tomáš Bžatek 2011-01-21 16:12:31 UTC
Works fine here (brasero-2.28.3-6.el6.x86_64), what package version of brasero do you use? Did you have medium placed in the drive? Was it blank or full?

Comment 8 Ben Woodard 2011-01-27 18:10:19 UTC
OK I've been able to burn a couple of disks without it crashing. I'll keep monitoring.

Comment 10 Tomáš Bžatek 2012-01-18 14:50:08 UTC
(In reply to comment #8)
> OK I've been able to burn a couple of disks without it crashing. I'll keep
> monitoring.

Ben, has this bug showed up during the last year?

Comment 11 Ben Woodard 2012-01-25 00:58:54 UTC
No it has been fine.

Comment 12 Tomáš Bžatek 2012-01-25 15:52:17 UTC
Okay, thanks for the answer. I'm going to close this bugreport now, feel free to reopen when the issue comes back.