[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok
Subject:    Re: Amarok cannot connect to X -- SOLVED
From:       Mike McCallister <workingwriter () prodigy ! net>
Date:       2007-03-19 11:53:56
Message-ID: 200703190653.57105.workingwriter () prodigy ! net
[Download RAW message or body]

Figured out what happened. I was experimenting with Novell's AppArmor tool 
(package-specific Internet security), and made a profile for an 
already-running instance of Amarok. Subsequent attempts to launch Amarok were 
prevented by AppArmor. Removing the AppArmor profile freed Amarok from its 
jail.

Thanks to Jonathan Ryshpan for a helpful idea.

Mike

On Sunday 18 March 2007 08:07, Mike McCallister wrote:
> Hi folks!
>
> I posted this on the forum, searched the buglist, and Googled on the error
> message. It's a strange problem. I am in 64-bit openSUSE 10.2, Amarok 1.4.5
> (latest Guru package). Amarok was working fine for a long while, now it
> tries to launch and dies. The Konsole error reads:
>
> _X11TransSocketINETConnect() can't get address for localhost:6000: Name or
> service not known
>
> : cannot connect to X server :0
>
> KDE is running fine, so clearly I've got an X server running. All thoughts
> appreciated.

-- 


Mike McCallister		ProTek Writing Services
workingwriter@prodigy.net	"Translation from the Geek a specialty"
Notes from the Metaverse: http://metaverse.wordpress.com
Author, "SUSE Linux 10 Unleashed"
_______________________________________________
Amarok mailing list
Amarok@kde.org
https://mail.kde.org/mailman/listinfo/amarok
[prev in list] [next in list] [prev in thread] [next in thread]