Bug 178093 - Clicking "Switch User" menu item on Fedora 10/KDE 4.1.3 resuts in a crash
Summary: Clicking "Switch User" menu item on Fedora 10/KDE 4.1.3 resuts in a crash
Status: RESOLVED DUPLICATE of bug 170989
Alias: None
Product: kdm
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdm bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-18 20:48 UTC by Peter C. Trenholme
Modified: 2008-12-18 23:04 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 Peter C. Trenholme 2008-12-18 20:48:10 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Fedora RPMs

A pop-up box is briefly displayed and then "krunner" pops a crash box withe the following contents:

Application: Run Command Interface (krunner), signal SIGSEGV
(no debugging symbols found)
... Repeated 25 times                                
[Thread debugging using libthread_db enabled]               
[New Thread 0x7fd26c1ea840 (LWP 2841)]                      
(no debugging symbols found)                                
--- Repeated 79 times
[KCrash handler]                                            
#5  0x000000373d28c050 in Plasma::AbstractRunner::ignoredTypes ()
   from /usr/lib64/libplasma.so.2                                
#6  0x000000373d2df06e in Plasma::RunnerManager::launchQuery ()  
   from /usr/lib64/libplasma.so.2                                
#7  0x0000003741c1958e in KStartupInfoId::~KStartupInfoId ()     
   from /usr/lib64/libkdeinit4_krunner.so                        
#8  0x0000003741c2d676 in ?? () from /usr/lib64/libkdeinit4_krunner.so
#9  0x000000373fa22143 in ?? () from /usr/lib64/libQtDBus.so.4        
#10 0x000000373fa23354 in ?? () from /usr/lib64/libQtDBus.so.4        
#11 0x000000373fa23a31 in ?? () from /usr/lib64/libQtDBus.so.4
#12 0x000000373fa23d48 in ?? () from /usr/lib64/libQtDBus.so.4
#13 0x000000373eb513d5 in QObject::event () from /usr/lib64/libQtCore.so.4
#14 0x00000037431d45b6 in QWidget::event () from /usr/lib64/libQtGui.so.4
#15 0x000000374318281d in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#16 0x000000374318a5ca in QApplication::notify ()
   from /usr/lib64/libQtGui.so.4
#17 0x0000003743dfb46b in KApplication::notify ()
   from /usr/lib64/libkdeui.so.5
#18 0x000000373eb42391 in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#19 0x000000373eb4302a in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib64/libQtCore.so.4
#20 0x000000373eb6ab13 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x000000373663779b in g_main_context_dispatch ()
   from /lib64/libglib-2.0.so.0
#22 0x000000373663af6d in ?? () from /lib64/libglib-2.0.so.0
#23 0x000000373663b12b in g_main_context_iteration ()
   from /lib64/libglib-2.0.so.0
#24 0x000000373eb6a79f in QEventDispatcherGlib::processEvents ()
   from /usr/lib64/libQtCore.so.4
#25 0x000000374321319f in ?? () from /usr/lib64/libQtGui.so.4
#26 0x000000373eb40cb2 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#27 0x000000373eb40e3d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#28 0x000000373eb432ed in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#29 0x0000003741c1e2b5 in kdemain () from /usr/lib64/libkdeinit4_krunner.so
#30 0x000000373321e576 in __libc_start_main () from /lib64/libc.so.6
#31 0x0000000000400899 in _start ()

Note 1: I'm running the Fedora 10 kernel, 2.6.27.7-134.fc10.x86_64, on an Athelon dual processor system.
Note 2: The Fedora 10 distribution seems to leave the tty[1-6] inoperative after logon.
Comment 1 Dario Andres 2008-12-18 21:26:28 UTC

*** This bug has been marked as a duplicate of bug 170989 ***
Comment 2 Peter C. Trenholme 2008-12-18 22:23:58 UTC
Sorry. I thought it was a KDM bug, not a krunner one, and didn't see the duplicate when I searched.

Any idea when the fix will be included in a release?
Comment 3 Dario Andres 2008-12-18 23:04:03 UTC
This is fixed in KDE4.2 , so your answer is... when Fedora release the KDE4.2.0 packages