Bug 255139 - Still crashing after update/upgrade
Summary: Still crashing after update/upgrade
Status: RESOLVED DUPLICATE of bug 253055
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.3.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: 2.4.0
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-24 21:14 UTC by John
Modified: 2010-10-25 02:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
This is the pitiful crash report, not the debug which I don't have for this version. (17.40 KB, application/octet-stream)
2010-10-24 21:14 UTC, John
Details

Note You need to log in before you can comment on or make changes to this bug.
Description John 2010-10-24 21:14:05 UTC
Created attachment 52835 [details]
This is the pitiful crash report, not the debug which I don't have for this version.

Version:           2.3.2 (using KDE 4.4.3) 
OS:                Linux

I upgraded to version 2.3.2 from an opensuse repo, like I was told to do, and unfortunately Amarok still crashes. Nothing else was running on my desktop. I didn't download the debug rpm because I only have dial-up and it's 20MB, so I don't have the info to give this time other than the standard crash report that popped up.

Reproducible: Always

Steps to Reproduce:
Klick on Amarok in Kmenu. Splash window pops up and after a few seconds it disappears and the crash window pops up. The same exact thing happens when I try to start it in konsole.


Expected Results:  
I was hoping that the upgrade from 2.3.0 to 2.3.2 would fix whatever the problem was and it would run.
Comment 1 Myriam Schweingruber 2010-10-25 02:25:06 UTC
Backtrace from original comment. Please always paste backtraces inline, else those are not searchable.

As already stated in bug #253055: please talk to your distribution, this is specific to OpenSuSE and seems to be a problem with the QtScriptbindings. It is not reproducible in other distributions.

*** This bug has been marked as a duplicate of bug 253055 ***