Bug 468454 - On default install banshee will not start
Summary: On default install banshee will not start
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: banshee
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-24 19:24 UTC by S.A. Hartsuiker
Modified: 2009-07-15 08:21 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-15 08:21:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
log file after a first install and startup of banshee (1.53 KB, text/plain)
2009-01-23 03:04 UTC, S.A. Hartsuiker
no flags Details

Description S.A. Hartsuiker 2008-10-24 19:24:40 UTC
Description of problem:
Banshee will not start with a mention of 
/usr/bin/banshee-1: line 45: /home/ogd/.config/banshee-1/log: No such file or directory
in $HOME/.xsession-errors where /home/ogd == $HOME

Version-Release number of selected component (if applicable):
$ rpm -qa|grep banshee
banshee-1.2.1-2.fc9.i386


How reproducible:
Take a user who has not started banshee and try to start banshee from the menu

Steps to Reproduce:
1.
2.
3.
  
Actual results:
banshee seems to be starting and then stops/dies

Expected results:
banshee creates the dir it needs and continues

Additional info:

Comment 1 Michel Lind 2008-12-30 22:54:02 UTC
This should work fine with the current banshee 1.4.1, could you retest? Thanks.

Comment 2 S.A. Hartsuiker 2009-01-23 03:03:06 UTC
Sorry for the wait.

Well, it does start, sort of...
It now displays the gui, but it is completely unresponsive after that.
This is on a laptop without a music player attached to it.

I will attach the $HOME/.config/banshee-1/log file.

Comment 3 S.A. Hartsuiker 2009-01-23 03:04:24 UTC
Created attachment 329770 [details]
log file after a first install and startup of banshee

Comment 4 Fedora Update System 2009-01-27 01:52:34 UTC
banshee-1.4.2-1.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing-newkey update banshee'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2009-1007

Comment 5 Fedora Update System 2009-01-27 01:56:08 UTC
banshee-1.4.2-1.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update banshee'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-1051

Comment 6 Michel Lind 2009-03-11 04:58:25 UTC
Looks like Bodhi (the update server) failed to update this bug properly. S.A., is the problem fixed for you?

Comment 7 S.A. Hartsuiker 2009-03-11 09:56:37 UTC
Hi Michel,

banshee-1.4.2-3 on f10 works as it should. Thank you.

Comment 8 Bug Zapper 2009-06-10 03:04:21 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 WONTFIX if it remains open with a Fedora 
'version' of '9'.

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 prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2009-07-15 08:21:49 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.

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.