problems with dbus?



---------- Forwarded message ----------
From: charles zeitler <cfzeitler@xxxxxxxxx>
Date: Sun, Jun 7, 2009 at 7:34 PM
Subject: some multimedia app failures
To: KDE on Fedora discussion <fedora-kde@xxxxxxxxxxxxxxxxxxxxxxx>


when i try to start amarok i get:


nnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
090607 17:59:46 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>(4562)/: 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." "

and nothing beyond the splash screen ( which remains after returning to
shell )

from juk i get:


l
juk(5910): Communication problem with "juk" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did
not receive a reply (timeout by message bus)" "

[fedora@cthulhu ~]$ KCrash: Application 'juk' crashing..

kmix does nothing. doesn't even try to start.

any suggestions on how to narrow this down?

thanx

charles zeitler



--

Do What Thou Wilt
Shall Be
The Whole of
The Law

-Aleister Crowley
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

Relevant Pages

  • Re: mysqld wont start
    ... Administration | Server Settings and highlight mysqld and click on start I ... InnoDB: Starting crash recovery. ... log sequence number 0 36808. ...
    (Fedora)
  • mysqld wont start
    ... Administration | Server Settings and highlight mysqld and click on start I ... InnoDB: Starting crash recovery. ... log sequence number 0 36808. ... There is no single government agency that views sustainability through a broad ...
    (Fedora)
  • SQL glitches
    ... InnoDB: Starting crash recovery. ... Reading tablespace information from the .ibd files... ... InnoDB: buffer... ... log sequence number 0 36808. ...
    (freebsd-questions)
  • MySQL on IA64 Problem
    ... (Installation etc. was ok, no errors) ... InnoDB: directory. ... Crash recovery may have failed for some .ibd files! ... log sequence number 0 43780. ...
    (comp.os.vms)
  • Re: MySQL on IA64 Problem
    ... (Installation etc. was ok, no errors) ... InnoDB: directory. ... Crash recovery may have failed for some .ibd files! ... log sequence number 0 43780. ...
    (comp.os.vms)