Bug 788986

Summary: Cannot talk to klauncher: Message did not receive a reply (timeout by message bus)
Product: [Fedora] Fedora Reporter: Xavier Hourcade <public.oss>
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: jreznik, kevin, ltinkl, mbriza, public.oss, rdieter, rnovacek, ry, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-08 21:04:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
xsession-errors as copied from tty2 during the "pause", before reboot
none
xsession-errors as copied during a successful session, after reboot none

Description Xavier Hourcade 2012-02-09 13:55:41 UTC
Created attachment 560586 [details]
xsession-errors as copied from tty2 during the "pause", before reboot

Description of problem:

KDE session "sometimes" fails to initialize correctly.

Version-Release number of selected component (if applicable):

Please help triage, not sure which component is responsible.
Running Fedora 16 KDE, strictly stable packages so far, up-to-date, few extras.
(hence current KDE is 4.7.4).

How reproducible:

Recurrent but *not* always.
Once every 5 or 6 KDE session init, maybe.
So far, never occurred twice consecutively.

Steps to Reproduce:
1. Boot computer until KDM screen shows up
2. Init KDE session
  
Actual results:

KDE session "sometimes" "fails to initialize correctly.
KDM splash screen get stuck after showing the last icon (the KDE one).

Expected results:

KDE session always open correctly.

Additional info:

Issue has occurred since fresh install I think (i.e. it was already occurring before "heavier" system customization such as replacing nouveau with kmod-nvidia, enabling desktop effects or adding panel applets e.g. lancelot, and awn is installed but *not* autostarted).

Attached xsession-errors as copied from tty2 during the "pause", before reboot.
Attached xsession-errors as copied during a successful session, after reboot.

During the pause, there is (little) disk activity for a minute maybe.
Then the system seems to be waiting forever with no activity.
After some time (minutes) a sound is played (see xsession-errors).
Later again, plasma desktop shows up but is unusable:
* no icon in default desktop folder applet
* clicking default panel has no effect.
* error dialogue is already open and shows the message

  « Cannot talk to klauncher: Message did not receive a reply
   (timeout by message bus) »

Workaround:

Switch tty (Alt+F2), at this stage or while waiting, login and `reboot`.
Then, after reboot, KDE session opens with no errors (every time so far).

Comment 1 Xavier Hourcade 2012-02-09 13:57:27 UTC
Created attachment 560592 [details]
xsession-errors as copied during a successful session, after reboot

Quite a few errors, even when all seem to go well. Any pointer welcome, thanks.

Comment 2 Rex Dieter 2012-02-09 14:05:31 UTC
"timeout by message bus" implies dbus is either stuck or crashed, which would essentially give the symptoms described here.

Comment 3 Xavier Hourcade 2012-02-24 21:37:58 UTC
Still happens, as usual KDM paused, then without changing or un/plugging anything, but doing a simple reboot, it opened just fine.

Captured a new set of logs & messages, diff'ing paused and good
(ignoring numbers using KDiff3)

dmesg : all seem identical and almost in the exact same sequence in both cases,
from messaging start,
until usb enumeration (included):

[    3.341183] usb 4-2: new full-speed USB device number 2 using uhci_hcd
[    3.567840] usb 4-2: New USB device found, idVendor=0b05, idProduct=1712
[    3.567848] usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=3
[    3.567856] usb 4-2: SerialNumber: 0194E8-5B-0002

From there, in paused only, plenty of these :

[    3.726204] hub 6-0:1.0: unable to enumerate USB device on port 1
[    4.891239] hub 6-0:1.0: unable to enumerate USB device on port 1
[    6.056202] hub 6-0:1.0: unable to enumerate USB device on port 1

Would this be a cause or consequence of dbus being stalled ?

(diff to be continued)

Comment 6 Xavier Hourcade 2012-09-08 21:04:29 UTC
No new occurrence in several months