Bug 675876 - Amarok stops loading
Summary: Amarok stops loading
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-08 04:17 UTC by Tristan Santore
Modified: 2012-08-16 15:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 15:11:10 UTC
Type: ---


Attachments (Terms of Use)

Description Tristan Santore 2011-02-08 04:17:41 UTC
Description of problem:
Amarok stops loading

Version-Release number of selected component (if applicable):
Version     : 2.3.2                             Vendor: Fedora Project
Release     : 4.fc14        

How reproducible:
run amarok from shell or using usual icon in gui (Gnome)

Steps to Reproduce:
1. just start amarok
  
Actual results:
Desktop]$ amarok
Object::connect: No such signal Podcasts::SqlPodcastProvider::playlistAdded( Playlists::PlaylistPtr )
Object::connect: No such signal Podcasts::SqlPodcastProvider::playlistRemoved( Playlists::PlaylistPtr )
Object::connect: No such signal Playlists::SqlUserPlaylistProvider::playlistAdded( Playlists::PlaylistPtr )
Object::connect: No such signal Playlists::SqlUserPlaylistProvider::playlistRemoved( Playlists::PlaylistPtr )
Calling appendChild() on a null node does nothing.
[Titan@titan Desktop]$ ps ax|grep amarok
 4772 pts/1    Rl     2:27 amarok
 4843 pts/1    S+     0:00 grep --color=auto amarok

amarok just dies after hull node error, and the shell is given back to the user,
but a amarok process still shows. And before the error it shows two amarok processes. The start up screen for amarok sticks to the screen, shoing the first process as active.

Expected results:
amarok should just start.

Additional info:

I did scan for music again, maybe that is half the problem.

Comment 1 Tristan Santore 2011-02-08 07:47:41 UTC
I should have added, attaching strace gave same errors as above, so it was waiting for something, but did not wait, and time out sanely, but made the process die and go away, leaving an orphan.

Removing the config dirs and shared amarok stuff under ~/.kde, lets amarok start again.
Rescanning collection get following errors, probably unrelated to above issue.
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x6800024
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x6800287
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
amarok(4878) EventListener::eventFilter: User of KWidgetItemDelegate should not delete widgets created by createWidgets! 
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x6800a8e

Now on rescan it stops responding after doing a full scan, but the scan indicator went back to 0%

Comment 2 Fedora End Of Life 2012-08-16 15:11:12 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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


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