Bug 652354 - world clock applet hangs
Summary: world clock applet hangs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdeedu
Version: 15
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 17:31 UTC by Jeff Bastian
Modified: 2011-05-31 18:19 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-31 17:39:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
plasma config files (2.72 KB, application/x-gzip)
2010-11-11 18:11 UTC, Jeff Bastian
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 256193 0 None None None Never

Description Jeff Bastian 2010-11-11 17:31:25 UTC
Description of problem:
I upgraded my Fedora 13 systems to KDE 4.5.2 this morning and now when I login I just get a blank screen with two xterms (started by my ~/.kde/Autostart/terminals.sh script).  According to 'ps', kwin and plasma and the other daemons are all running, but there's nothing on the screen.  The mouse buttons are not bound to anything on the desktop.

I moved my ~/.kde directory out of the way and started with a fresh profile and it launched correctly, but when I restored my ~/.kde directory it broke again.

I could start from scratch, I suppose, but it would take me quite some time to customize everything the way I had it.

I looked at ~/.xsession-errors and noticed this:
<unknown program name>(1926)/: Communication problem with  "plasma-desktop" , 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." "

I'll try and figure out which of my ~/.kde files is causing this.


Version-Release number of selected component (if applicable):
kdebase-4.5.2-2.fc13.i686

How reproducible:
unsure

Steps to Reproduce:
1. upgrade to kdebase-4.5.2-2.fc13.i686
2. login to KDE
  
Actual results:
KDE doesn't start

Expected results:
KDE starts normally

Additional info:

Comment 1 Jeff Bastian 2010-11-11 17:41:05 UTC
I started with the obvious and removed these three files:
   ~/.kde/share/config/plasma-desktoprc
   ~/.kde/share/config/plasmarc
   ~/.kde/share/config/plasma-desktop-appletsrc
and now KDE starts!

I wonder what it didn't like about my old files.

I have to setup my widgets again, but at least the rest of my customizations are preserved.

Comment 2 Rex Dieter 2010-11-11 17:46:05 UTC
Which applets/plasmoids were you using?

Mind attaching the contents of those files?

Comment 3 Jeff Bastian 2010-11-11 18:11:41 UTC
Created attachment 459815 [details]
plasma config files

I had removed the Desktop folder viewer widget and I added the the World Clock widget.

The files are attached.

Comment 4 Jeff Bastian 2010-11-11 18:19:23 UTC
It appears that the World Clock widget is the culprit.  I just tried adding it back to my desktop and plasma locked up on me.  I restarted plasma and tried again and it locked up a second time.

Does it start for you?

This widget comes from kdeedu-marble:
$ rpm -qf /usr/lib/kde4/plasma_applet_worldclock.so
kdeedu-marble-4.5.2-2.fc13.i686

Comment 5 Jeff Bastian 2010-11-11 18:21:52 UTC
Looks like it's been reported upstream too:
https://bugs.kde.org/show_bug.cgi?id=256193

Comment 6 Rex Dieter 2010-11-11 18:40:43 UTC
Thanks!  excellent detective-work, I've used it in the past, but not recently... I'll try world clock again to test.

Comment 7 Bug Zapper 2011-05-30 13:51:46 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Jeff Bastian 2011-05-31 15:23:44 UTC
It still crashes with Fedora 15

Comment 9 Rex Dieter 2011-05-31 16:01:51 UTC
crashes or hangs?

The referenced upstream bug was presumably fixed in kdeedu-4.5.5 series, fwiw, so perhaps you're seeing something different?

Comment 10 Jeff Bastian 2011-05-31 17:39:49 UTC
Oh, you're right, this might be different.  This morning I tried adding the World Clock to my desktop and it crashed (the KDE bug catcher popped up).

I just tried again, however, and it successfully launched.  I removed it and added it again a few times and it's launched every time.

I'll keep my eye on it and open a new BZ if it crashes again.  In the meantime, I guess this one can be closed now.

Comment 11 Rex Dieter 2011-05-31 18:19:33 UTC
OK, there's in interesting bug we found testing the kde-4.6.x f14 updates.

After upgrading from < kde-4.6.x, anything marble-related would crash *once*, afterwhich, all is fine.  I'd bet you just hit the one-time anti-fun. :(


Note You need to log in before you can comment on or make changes to this bug.