[kde] [Bug 331857] New: Unresponsive applications, kdecode ktimezone did not receive a reply

docd1990 at gmail.com docd1990 at gmail.com
Fri Mar 7 20:06:13 GMT 2014


https://bugs.kde.org/show_bug.cgi?id=331857

            Bug ID: 331857
           Summary: Unresponsive applications, kdecode ktimezone did not
                    receive a reply
    Classification: Unclassified
           Product: kde
           Version: unspecified
          Platform: Archlinux Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: docd1990 at gmail.com

Kde version: 4.12.3 (was not in the list)

I removed .kde4 directory because I had plasma broken after upgrade.

So when I rebooted clean starting dolphin took almost a minute.
Then it froze after a "control" click.

I opened gwenview, it frozed on F11 press.

Then I opened the KDE System Settings, which froze.

The message in the console was similar to

[code]
dolphin(25687)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize()
D-Bus call failed:  "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." 
[/code]

Then I found this half-year old thread.
https://bbs.archlinux.org/viewtopic.php?pid=1389739#p1389739

The last message suggested disabling upower, what indeed helped for me
After disabling upower and reboot, everything was responsive.

Reproducible: Always

Steps to Reproduce:
1. Open any Kde application (surely reproduce on dolphin, gwernview and System
Settings, but looks like it should freeze any application)
2. Press some buttons.
Actual Results:  
Application freezed

Expected Results:  
Application responsive.

ArchLinux x64, 3.13.5-1-ARCH #1 SMP PREEMPT Sun Feb 23 00:25:24 CET 2014 x86_64
GNU/Linux
btrfs filesystem

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list