Well Amarok used to work OK but, suddenly I just could not get it to run. The coloured startup came up but nothing else. So I ran it as su from a terminal and this was the result:
*<unknown program name>(6552)/: KUniqueApplication: Cannot find the D-Bus session server: “Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”
<unknown program name>(6551)/: KUniqueApplication: Pipe closed unexpectedly.
*
I just do not understand it. Any help would be appreciated.
This is weird, because KuniqueApplication, if I am correct, ensure that there is only one instance of an application open. So, maybe there is an instance of Amarok running in the background that has not been killed. I am not sure if I am correct in my assumption though…
I suggest you close your session and get back in to see if the problem persists.
Of course you are correct, I am thinking that maybe firstly he must go to his system monitor to kill the process if runs in background. Although runs background and now tries to run it again graphically, the application must run.
>
> Well Amarok used to work OK but, suddenly I just could not get it to
> run. The coloured startup came up but nothing else. So I ran it as su
> from a terminal and this was the result:
my amarok runs fine, but when i run amarok as “su”, i get the same error.
if you really do want to run amarok as root, you have to do “su -”, not
“su”. but i wouldn’t recommend that either.
> -<unknown program name>(6552)/: KUniqueApplication: Cannot find the
> D-Bus session server: “Did not receive a reply. Possible causes
> include: the remote application did not send a reply, the message bus
> security policy blocked the reply, the reply timeout expired, or the
> network connection was broken.”
>
> <unknown program name>(6551)/: KUniqueApplication: Pipe closed
> unexpectedly.
> -
>
> I just do not understand it. Any help would be appreciated.
>
>
PLEASE use CODE tags, not QUOTE tags for computer text.
And there seems to be a suggestion of someone running Amarok as root. That is one of the more stupid things to do. I hope it was only a suggestion, or a misunderstanding and not done in real.
divali@localhost:~> amarok
_IceTransSocketUNIXConnect: Cannot connect to non-local host linux-opqv
_IceTransSocketUNIXConnect: Cannot connect to non-local host linux-opqv
Qt: Session management error: Could not open network socket
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110420 21:22:16 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files…
InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer…
<unknown program name>(8303)/: Communication problem with “amarok” , it probably crashed.
Error message was: “org.freedesktop.DBus.Error.NoReply” : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Ok, I removed the Packman repo’s and tried to start Amarok in the terminal and here’s the result. Needless to say it wouldn’t start.
>
> PLEASE use CODE tags, not QUOTE tags for computer text.
>
> And there seems to be a suggestion of someone running Amarok as root.
> That is one of the more stupid things to do. I hope it was only a
> suggestion, or a misunderstanding and not done in real.
>
excuse me, that’s what he wrote in his first post, that he ran amarok as
“su”. that doesn’t work. it does work as “su -”, but i recommended not to
do that.
if you still can’t start amarok, and it’s a db issue (the errors you get in terminal hints at this) then try removing/renaming the following folder and restarting amarok:
~/.kde4/share/apps/amarok/mysqle
be aware though that will cause you to lose any rating statistics and such you may have done within amarok if you hadn’t already activated the “write statistics to file” option …
have you tried starting with the debug and nofork options? yet
I delibaratly called no names (and of course I do not intend to warn those who warned also). It was a general (but strong) remark becuase I saw a suggestion (or a bit more) of using root for non root things.