Bug 1023118 - When I wanted import files, then rhythmox crashed
Summary: When I wanted import files, then rhythmox crashed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-24 16:31 UTC by Anonymous
Modified: 2015-06-29 12:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:43:04 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 251970 0 None None None Never

Description Anonymous 2013-10-24 16:31:24 UTC
Description of problem:
I was using rhythmox to play music. The last thing I did, was import the music from directory.

Version-Release number of selected component (if applicable):
rhythmbox.x86_64                       3.0-3.fc20               @fedora
gnome-do-plugins-rhythmbox.x86_64      0.8.4-14.fc20            fedora


How reproducible:
I don't know how to reproduce it

Steps to Reproduce:
1. Sorry, I don't know. I was using it by a few minuts and then imported new files.
2.
3.

Actual results:
Crashed

Expected results:
Not crash and import files

Additional info:
https://retrace.fedoraproject.org/faf/reports/251970/
I want to add more information from my pc, but I don't know how. So I copied and compressed /var/tmp/abrt/ccpp-2013-10-24-15\:42\:22-11521/ directory. It is after compresion 21 MB. Before 780. Sorry, but I don't know how to  deal with it so I give you raw data.
https://mega.co.nz/#!t99G2IzB!H5GwGmFfXNxX4rFYo23CMkrqbpx1Wn4xBeBQAoHEPI4
http://speedy.sh/dFx44/ccpp-2013-10-24-15-42-22-11521.tar.bz2

Comment 1 Adam Williamson 2013-12-10 23:56:16 UTC
If you run the 'abrt-gui' tool (from Overview, look for 'abrt') you should find an entry for the crash and the option to submit it to Bugzilla. If you do so, it should submit a new report with a proper backtrace attached. Can you try that, and if you're successful, post here with a note of the new bug number? Thanks.

Comment 2 Fedora End Of Life 2015-05-29 09:37:51 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 3 Fedora End Of Life 2015-06-29 12:43:04 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.