Bug 195227 - RTM plasmoid freezes the entire plasma-desktop if network not available on startup
Summary: RTM plasmoid freezes the entire plasma-desktop if network not available on st...
Status: RESOLVED DUPLICATE of bug 181015
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-misc (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-04 16:53 UTC by Harald Hvaal
Modified: 2009-06-10 08:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Hvaal 2009-06-04 16:53:18 UTC
Version:            (using Devel)
Installed from:    Compiled sources

RTM plasmoid freezes the entire plasma-desktop if network not available on startup.

I have a network setup where I sometimes have to change files manually when I move my laptop, and when network is not available when I come home (there is no dhcp system, so I guess it's stuck looking for ip or something) the plasma-desktop will first start with a black desktop for about 10-15 seconds, and then finally show desktop backgruond, but will not be open for user input.

When this happened I got the backtrace for the main plasma-thread, and discovered that it was stuck in an idle state in some event loop started by the RTM plasmoid, waiting for an authentication. 

Here is the backtrace:

#0  0x0090d422 in __kernel_vsyscall ()    
#1  0x048f8ae7 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0x055f274b in g_poll () from /usr/lib/libglib-2.0.so.0 
#3  0x055e4f82 in ?? () from /usr/lib/libglib-2.0.so.0     
#4  0x055e5268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#5  0x012c81d8 in QEventDispatcherGlib::processEvents (this=0x8942510, flags={i = -1077394312})
    at kernel/qeventdispatcher_glib.cpp:324                                                    
#6  0x062b8765 in QGuiEventDispatcherGlib::processEvents (this=0x8942510, flags={i = -1077394264})
    at kernel/qguieventdispatcher_glib.cpp:202                                                    
#7  0x0129adda in QEventLoop::processEvents (this=0xbfc84524, flags={i = -1077394200}) at kernel/qeventloop.cpp:149
#8  0x0129b21a in QEventLoop::exec (this=0xbfc84524, flags={i = -1077394132}) at kernel/qeventloop.cpp:200         
#9  0x006328ab in KIO::NetAccess::enter_loop (this=0xbfc84590) at /build/buildd/kde4libs-4.2.85/kio/kio/netaccess.cpp:502
#10 0x00632f6f in KIO::NetAccess::synchronousRunInternal (this=0xbfc84590, job=0x910a048, window=0x0, data=0xbfc84660,   
    finalURL=0x0, metaData=0x0) at /build/buildd/kde4libs-4.2.85/kio/kio/netaccess.cpp:487                               
#11 0x00633621 in KIO::NetAccess::synchronousRun (job=0x910a048, window=0x0, data=0xbfc84660, finalURL=0x0, metaData=0x0)
    at /build/buildd/kde4libs-4.2.85/kio/kio/netaccess.cpp:277                                                           
#12 0x01d2dbeb in RTM::Request::sendSynchronousRequest () from /usr/lib/librtm.so.4                                      
#13 0x01d259c0 in RTM::Session::checkToken () from /usr/lib/librtm.so.4                                                  
#14 0x01d25dcd in RTM::Session::setToken () from /usr/lib/librtm.so.4                                                    
#15 0x04debb73 in ?? () from /usr/lib/kde4/plasma_engine_rtm.so                                                          
#16 0x003e18ca in Plasma::ServiceJob::qt_metacall (this=0x939e370, _c=3217573660, _id=-1077393584, _a=0xbfc84858)        
    at /build/buildd/kde4libs-4.2.85/plasma/servicejob.cpp:41                                                            
#17 0x04de64fa in ?? () from /usr/lib/kde4/plasma_engine_rtm.so                                                          
#18 0x012b2a58 in QMetaObject::activate (sender=0x939e358, from_signal_index=4, to_signal_index=4, argv=0x0)             
    at kernel/qobject.cpp:3120                                                                                           
#19 0x012b36e2 in QMetaObject::activate (sender=0x939e358, m=0x138e908, local_signal_index=0, argv=0x0)                  
    at kernel/qobject.cpp:3194                                                                                           
#20 0x012b7e57 in QSingleShotTimer::timeout (this=0x939e358) at .moc/release-shared/qtimer.moc:76                        
#21 0x012b7f7c in QSingleShotTimer::timerEvent (this=0x939e358) at kernel/qtimer.cpp:298                                 
#22 0x012acf0f in QObject::event (this=0x939e358, e=0xbfc84cdc) at kernel/qobject.cpp:1082                               
#23 0x06216bcc in QApplicationPrivate::notify_helper (this=0x8946dd8, receiver=0x939e358, e=0xbfc84cdc)
    at kernel/qapplication.cpp:4057
#24 0x0621eede in QApplication::notify (this=0x893f270, receiver=0x939e358, e=0xbfc84cdc) at kernel/qapplication.cpp:3604
#25 0x00c18c9d in KApplication::notify (this=0x893f270, receiver=0x939e358, event=0xbfc84cdc)
    at /build/buildd/kde4libs-4.2.85/kdeui/kernel/kapplication.cpp:307
#26 0x0129c7ab in QCoreApplication::notifyInternal (this=0x893f270, receiver=0x939e358, event=0xbfc84cdc)
    at kernel/qcoreapplication.cpp:610
#27 0x012cbb31 in QTimerInfoList::activateTimers (this=0x8949a34)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#28 0x012c8280 in timerSourceDispatch (source=0x8949a00) at kernel/qeventdispatcher_glib.cpp:164
#29 0x055e1b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#30 0x055e50eb in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x055e5268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#32 0x012c81d8 in QEventDispatcherGlib::processEvents (this=0x8942510, flags={i = -1077391784})
    at kernel/qeventdispatcher_glib.cpp:324
#33 0x062b8765 in QGuiEventDispatcherGlib::processEvents (this=0x8942510, flags={i = -1077391736})
    at kernel/qguieventdispatcher_glib.cpp:202
#34 0x0129adda in QEventLoop::processEvents (this=0xbfc84f00, flags={i = -1077391672}) at kernel/qeventloop.cpp:149
#35 0x0129b21a in QEventLoop::exec (this=0xbfc84f00, flags={i = -1077391608}) at kernel/qeventloop.cpp:200
#36 0x0129d6c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x06216a47 in QApplication::exec () at kernel/qapplication.cpp:3526
#38 0x00a14290 in kdemain (argc=1, argv=0xbfc850b4)
    at /build/buildd/kdebase-workspace-4.2.85/plasma/shells/desktop/main.cpp:50
#39 0x08048712 in main (argc=Cannot access memory at address 0xe
)
    at /build/buildd/kdebase-workspace-4.2.85/obj-i486-linux-gnu/plasma/shells/desktop/plasma-desktop_dummy.cpp:3
(gdb)


Note: this is on 4.3 beta1 (bugs.kde.ord had only an entry for beta2 even though this is not available with ubuntu packages yet), but I have seen no commits for a long time in the rtm folder, so I assume the bug is still there.
Comment 1 Aaron J. Seigo 2009-06-10 08:30:19 UTC

*** This bug has been marked as a duplicate of bug 181015 ***