[opensuse] Amarok crashing
I first tried to use the stock Amarok that came with 11.3. Upon opening it, it gets to splash screen and then crashes. Every signle time. Whether anything else is running or it's by itself on the desktop. Fine. I bug it at kde.bugs. I'm told by them to upgrade to 2.3.2, which I did yesterday (all but the debug rpm's...I'm on dial-up and 23MB is a bit much to download for something I was *hoping* was simple). I install Amarok 2.3.2 (from an opensuse 11.3 repo, by the way), anticipating being able to use it. Amarok crashes, in the exact same way as before. I bug this one again (this time with the generic debug info that kde.bugs window says isn't good enough to send, btw). Their reply to *this* bug: -------------------------- https://bugs.kde.org/show_bug.cgi?id=255139 --- Comment #1 from Myriam Schweingruber <myriam kde org> 2010-10-25 02:25:06 --- 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. -------------------------- So, who/how/what do I talk to/do/tell about the qtbindings thing in Opensuse? I don't want to use another audio player for too long when I know Amarok is working fine on other distros and I just plain like it over any other I've ever run/tried. -- Μολὼν λαβέ Top-posters: The Village Idiots of the computer world. Religion: The longest running scam known to mankind. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 2010-10-25 at 12:05 -0500, John wrote:
I first tried to use the stock Amarok that came with 11.3. Upon opening it, it gets to splash screen and then crashes. Every signle time. Whether anything else is running or it's by itself on the desktop.
Fine. I bug it at kde.bugs. I'm told by them to upgrade to 2.3.2, which I did yesterday (all but the debug rpm's...I'm on dial-up and 23MB is a bit much to download for something I was *hoping* was simple).
It actually looks like a simple problem. It is dying trying to dynamically load a symbol from a library/plugin which can't be found. It looks like an installation problem with some qt package, but I can't tell which from the backtrace Have you tried running it from the command line to see if perhaps it tells you what it's trying to load? Worst case: run amarok with strace, something like strace -f -s 200 -o amarok.strace amarok Wait for it to crash, and then upload the amarok.strace file somewhere. That should tell us what it's trying to load, and from there it shouldn't take long to figure out which package is missing or badly installed Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday, October 25, 2010 12:26 Anders Johansson wrote:
On Mon, 2010-10-25 at 12:05 -0500, John wrote:
<snip>
yesterday (all but the debug rpm's...I'm on dial-up and 23MB is a bit much to download for something I was *hoping* was simple).
It actually looks like a simple problem. It is dying trying to dynamically load a symbol from a library/plugin which can't be found. It looks like an installation problem with some qt package, but I can't tell which from the backtrace
Have you tried running it from the command line to see if perhaps it tells you what it's trying to load?
Yes, that's what I sent to the bug list, everything that showed up after it crashed. By the way, after it crashed when I started it on the cli, it never goes back to a prompt. It just sits there like it's waiting for something to happen. Only thing I knew to do to stop it was to just close the konsole.
Worst case: run amarok with strace, something like
strace -f -s 200 -o amarok.strace amarok
Wait for it to crash, and then upload the amarok.strace file somewhere. That should tell us what it's trying to load, and from there it shouldn't take long to figure out which package is missing or badly installed
Just in case it's *not* the nvidia thing (below), I'll do this anyway and let you know.
Anders
Hi Anders, I just now got this from bugs.kde: ----------------------------- [Bug 253055] Start new amarok build lead to crash [@ AmarokScript::ScriptImporter::loadQtBinding] https://bugs.kde.org/show_bug.cgi?id=253055 --- Comment #26 from Christoph Feck <christoph maxiom de> 2010-10-25 20:30:28 --- This bug is caused by the NVIDIA driver update. *** This bug has been marked as a duplicate of bug 251719 *** ----------------------------- So, now my problem will be - how do I uninstall the nvidia driver I downloaded from the nvidia site and installed by hand per their instructions and re-install whatever it is I'll need for my nvidia card. Any *simple* ways to do this? -- Μολὼν λαβέ What is top posting, and why should you avoid it? A3: Please. Q3: Should I avoid top posting on this mailing list? A2: Because, by reversing the order of a conversation, it leaves the reader without much context, and makes them read a message in an unnatural order. Q2: Why is top posting irritating? A1: It is the practice of putting your reply to a message before the quoted message, instead of after the (trimmed) message. Q1: What is top posting? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday, October 25, 2010 12:26 Anders Johansson wrote:
On Mon, 2010-10-25 at 12:05 -0500, John wrote:
<snip>
It actually looks like a simple problem. It is dying trying to dynamically load a symbol from a library/plugin which can't be found. It looks like an installation problem with some qt package, but I can't tell which from the backtrace
Worst case: run amarok with strace, something like
strace -f -s 200 -o amarok.strace amarok
Wait for it to crash, and then upload the amarok.strace file somewhere. That should tell us what it's trying to load, and from there it shouldn't take long to figure out which package is missing or badly installed
I just did the strace thing you said to try - Amarok worked without crashing! I adjusted the settings (which seemed kind of lean and maybe missing things, like cddb and all that) and closed it, then I tried to start it from kmenu and it crashed. <sigh> Now what? -- Μολὼν λαβέ What is top posting, and why should you avoid it? A3: Please. Q3: Should I avoid top posting on this mailing list? A2: Because, by reversing the order of a conversation, it leaves the reader without much context, and makes them read a message in an unnatural order. Q2: Why is top posting irritating? A1: It is the practice of putting your reply to a message before the quoted message, instead of after the (trimmed) message. Q1: What is top posting? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 25 October 2010, John wrote:
I just did the strace thing you said to try - Amarok worked without crashing! I adjusted the settings (which seemed kind of lean and maybe missing things, like cddb and all that) and closed it, then I tried to start it from kmenu and it crashed. <sigh>
Now what?
Did you do anything unusual when you ran it with strace? Did you run it as a different user? Anything? I really can't see how the nvidia driver update can be a valid solution to this. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday, October 25, 2010 15:34 Anders Johansson wrote:
On Monday 25 October 2010, John wrote:
I just did the strace thing you said to try - Amarok worked without crashing! I adjusted the settings (which seemed kind of lean and maybe missing things, like cddb and all that) and closed it, then I tried to start it from kmenu and it crashed. <sigh>
Now what?
Did you do anything unusual when you ran it with strace? Did you run it as a different user? Anything?
Nothing unusual at all. I closed all running apps, opened konsole as me, the one and only user on this system, and entered the command just as you advised me to try.
I really can't see how the nvidia driver update can be a valid solution to this.
So you think I should leave the nvidia driver I installed alone? I have absolutely no idea what else to do, since the kde bug folks I'm sure are adamant about it not being anything but an Opensuse problem. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Anders Johansson -
John