Bug 115844

Summary:	Kicker crashes when browsing the K menu
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Andras Mantia <amantia>
Component:	KDE	Assignee:	E-mail List <kde-maintainers>
Status:	RESOLVED WORKSFORME	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P3 - Medium
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SUSE Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Fulel backtrace

Description Andras Mantia 2005-09-08 12:24:01 UTC

After upgrading SUSE 9.3 to 10.0 beta4, kicker's K menu crashes when certain  
entries are selected, like: Internet, Multimedia, Office. Selecting any other  
item is fine.  
The crash is due to the SUSE's extension for KDE, as the backtrace shows:  
 (no debugging symbols found) 
Using host libthread_db library "/lib/tls/libthread_db.so.1". 
(no debugging symbols found) 
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
[Thread debugging using libthread_db enabled] 
[New Thread 1095211008 (LWP 11240)] 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
(no debugging symbols found) 
[KCrash handler] 
#3  0x40aa4bfb in QString::QString () from /usr/lib/qt3/lib/libqt-mt.so.3 
#4  0x401d061f in KService::menuId () from /opt/kde3/lib/libkio.so.4 
#5  0x40211f27 in KServiceGroup::SuSEsortEntries () 
   from /opt/kde3/lib/libkio.so.4 
#6  0x41706d5a in PanelServiceMenu::doInitialize () 
   from /opt/kde3/lib/libkdeinit_kicker.so 
#7  0x4170820d in PanelServiceMenu::initialize () 
   from /opt/kde3/lib/libkdeinit_kicker.so 
#8  0x4104a021 in KPanelMenu::internalInitialize () 
   from /opt/kde3/lib/libkdeui.so.4 
#9  0x41069742 in KPanelMenu::slotAboutToShow () 
   from /opt/kde3/lib/libkdeui.so.4 
#10 0x410b9beb in KPanelMenu::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 
#11 0x4170e393 in PanelServiceMenu::qt_invoke () 
   from /opt/kde3/lib/libkdeinit_kicker.so 
#12 0x407cef29 in QObject::activate_signal () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#13 0x407cf3d0 in QObject::activate_signal () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#14 0x40b26aec in QPopupMenu::aboutToShow () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#15 0x408d8366 in QPopupMenu::subMenuTimer () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#16 0x40b26953 in QPopupMenu::qt_invoke () from /usr/lib/qt3/lib/libqt-mt.so.3 
#17 0x410b9a00 in KPopupMenu::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 
#18 0x410b9b83 in KPanelMenu::qt_invoke () from /opt/kde3/lib/libkdeui.so.4 
#19 0x4170e393 in PanelServiceMenu::qt_invoke () 
   from /opt/kde3/lib/libkdeinit_kicker.so 
#20 0x4170e4b3 in PanelServiceMenu::qt_invoke () 
   from /opt/kde3/lib/libkdeinit_kicker.so 
#21 0x407cef29 in QObject::activate_signal () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#22 0x407cf3d0 in QObject::activate_signal () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#23 0x40b11479 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3 
#24 0x407f33ef in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3 
#25 0x4076f891 in QApplication::internalNotify () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#26 0x40770209 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3 
#27 0x404b030e in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4 
#28 0x407645a8 in QEventLoop::activateTimers () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#29 0x4071ddaf in QEventLoop::processEvents () 
   from /usr/lib/qt3/lib/libqt-mt.so.3 
#30 0x40786763 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 
#31 0x40786646 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 
#32 0x4076f1df in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 
#33 0x416cf117 in kdemain () from /opt/kde3/lib/libkdeinit_kicker.so 
#34 0x40029534 in kdeinitmain () from /opt/kde3/lib/kde3/kicker.so 
#35 0x0804d985 in ?? () 
#36 0x00000001 in ?? () 
#37 0x08074880 in ?? () 
#38 0x00000001 in ?? () 
#39 0x00000000 in ?? () 
#40 0x00000000 in ?? () 
#41 0x40cd5d18 in in6addr_any () from /usr/X11R6/lib/libX11.so.6 
#42 0x4006e7d8 in ?? () 
#43 0x40d3a59c in ?? () from /usr/X11R6/lib/libX11.so.6 
#44 0x0006b090 in ?? () 
#45 0x08073e98 in ?? () 
#46 0xbf8ad318 in ?? () 
#47 0x40c95b87 in _XOpenLC () from /usr/X11R6/lib/libX11.so.6 
#48 0x0804f4e0 in ?? () 
#49 0x00000000 in ?? () 
#50 0x00000000 in ?? () 
#51 0x00000000 in ?? () 
#52 0x00000000 in ?? () 
#53 0x00000000 in ?? () 
#54 0x00000000 in ?? () 
#55 0x080501f2 in typeinfo name for QStrList () 
#56 0x00000000 in ?? () 
#57 0x00000000 in ?? () 
#58 0x40015ff4 in ?? () from /lib/ld-linux.so.2 
#59 0x400166ac in ?? () 
#60 0xbf8ad418 in ?? () 
#61 0xbf8ad42c in ?? () 
#62 0x400079c7 in _dl_lookup_symbol_x () from /lib/ld-linux.so.2 
#63 0x40e41e60 in __libc_start_main () from /lib/tls/libc.so.6 
#64 0x0804b0d1 in ?? () 
 
Unfortunately it is not possible for me to download the debuginfo for 
kdelibs3.

Comment 1 Stephan Kulow 2005-09-08 13:14:50 UTC

want it? You seem to be the only one (beside one or two occasional reports on 
bugs.kde.org) being able to reproduce it.

Comment 2 Andras Mantia 2005-09-08 13:25:49 UTC

You mean to solve it? ;-) Well, I'd need the suse patches as well. And I have   
only the 3.5 branch checked out.

Comment 3 Stephan Kulow 2005-09-08 15:30:10 UTC

I want to know if you not having debuginfos is a don't want to or a don't be 
able to. Because I can put them somewhere ;)

Comment 4 Andras Mantia 2005-09-08 17:00:16 UTC

Cannot have it. I downloaded beta4 at akademy, but now I'm home with a slow  
and expensive connection. But might try to get it somewhere else, but it will  
take some days until I download there as well (64kbps, altough not limited).

Comment 5 Stephan Kulow 2005-09-09 08:54:07 UTC

don't think it's major - so far no other report

Comment 6 Andras Mantia 2005-09-12 13:07:45 UTC

Created attachment 49607 [details]
Fulel backtrace

This is a backtrace with debug info, showing that there is an invalid pointer
somewhere.

Comment 7 Thiago Ramos 2005-10-20 14:28:37 UTC

This problems happens to me too. I'm usin Suse Linux 10.0(i586), and when I try to access the Internet menu on kicker, it crashes and kicker is restarted, but trying more times consecutivelly, it crashes and don't restart again. My Pc is:
Intel Pentium 4, 512 MB MRAM, GForce 64MB 440mx.

Comment 8 Thiago Ramos 2005-10-20 16:17:31 UTC

I got something. Here, my login is maded in network. And we changed with some distributions, without removing profiles in home. I openned the Menu Editor e sorted some entries, and saved changes. After, accessing the Internet menu, kicker doesn't crashed. Try this Andras.

Comment 9 Stephan Kulow 2005-11-30 13:09:31 UTC

Andras - are you sure you can't have mixed SUSE rpms and self compiled? Looking at the patch, it seems it's binary incompatible (and old).

I'm afraid I can't really do anything about it without being able to reproduce it - sorry ;(

Comment 10 Andras Mantia 2005-11-30 13:22:49 UTC

Everything is possible, but I doubt it is because of mixage of self compiled and rpm. They go in separate directories and I tested with a new user.
 Anyway, since than I upgraded to 10.0 final so I tested again. I could crash on the first try, but not after that. Even after a logout/login. So I do not oppose to closing, in worst case somebody will report again or reopen it.

Oh, and can't you port KDE's email to bugzilla interface here? It is so slow to wait for log in, wait for the page, enter the text and post. Email is so much easier. ;-)