Bug 247712
| Summary: | amarokFS crash on startup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Riku Seppala <riku.seppala> | ||||
| Component: | amarokFS | Assignee: | Francois Aucamp <francois.aucamp> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 6 | CC: | triage | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | Flags: | kevin:
fedora-cvs+
|
||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | bzcl34nup | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-06 19:42:13 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
Riku Seppala
2007-07-10 21:56:42 UTC
Created attachment 158896 [details]
backtrace
Hmm... this works fine for me (F7/i386, using standard Fedora KDE) - I really am unable to recreate the crash. I'll try and find a FC6 box here and test it on that. By the way, how often is "often" - does it work sometimes? In the meantime, try starting amarok (not amarokFS) first, wait until it's running, and then run amarokFS (from a terminal). Any outputs/irregularities/crashes? Thanks for the report! /me goes of searching for a FC6/KDE-redhat box Now that I tried, if amarok is running it seems to work everytime. When amarok wasn't already running and I started amarokFS, it crashed on second try. Though I've tried several times after that now, and it worked everytime. So not so often? Only output is this and only when amarok isn't running: there was some error calling DCOP function trackTotalTime() ... That same thing from the first post. BTW, http://www.kde-apps.org/content/show.php/Amarok+Full+Screen?content=52641 At least two other people seem to have similar (same?) problem... Thanks for this - now we know it's a race condition, and we know more-or-less what causes it - I'll get right on it. (In reply to comment #3) > BTW, http://www.kde-apps.org/content/show.php/Amarok+Full+Screen?content=52641 > At least two other people seem to have similar (same?) problem... Oh, and thank you VERY much for reporting this via bugzilla - bug "reports" on forums tend to go unnoticed... :-) This application does not support Qt4 or Amarok2 (Fedora 9 will be running KDE 4), and I currently am unable to spend enough time on it to port it and properly maintain it; so I will be orphaning this package. Reopening this bug because amarokFS is still included in Fedora 9, due to populare demand ;-) Please disregard comment #5; I'll continue to maintain this package. I believe the rawhide update of this package fixed this issue; I'll move this update to F-8 and F-7. rel-eng, could you please create a CVS branch for Fedora 8 (the package was never built explicitly for it)? Request in next comment. Package Change Request ====================== Package Name: amarokFS New Branches: F-8 There should be an F-8 branch already. Make sure you call cvs update with '-d'. ie, 'cvs update -d' Otherwise cvs will not pull in new directories. amarokFS-0.5-3.fc8 has been submitted as an update for Fedora 8 amarokFS-0.5-3.fc8 has been pushed to the Fedora 8 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 amarokFS'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-2095 Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. amarokFS-0.5-3.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report. |