[SOLVED] Opening Amarok 2.8 crashes entire X server (Slackware 64 14.1)
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
On my laptop Amarok runs fine, however in this desktop PC it doesn't. Shorty after i execute it, the KDE session terminates and i'm sent back to console.
I'm attaching the output after executing Amarok with --debug --no-fork flags.
Following other threads of people with a similar problem, i tried deactivating the analyzer plugin from amarok_homerc and also changing my oxygen theme because someone said Amarok had issues with oxygen transparent theme, but it seems this is a different problem because none of those two workarounds fixed it.
Do you have any idea why this could be happening?
Thanks a lot!
Yes, that's something i also tried... in fact, i created a new user with a new home directory to see if this user would suffer from the same issue, and it did, so i don't think it is related to config files.
I'm thinking about trying to debug it to see what the real issue is, but i will need time for this. Looking at the slackbuild scripts it seems i would have to run the kde build script with only amarok in the modules folder listed, in order to recompile it with debugging symbols.