Bug 209730 - Menu Editor crashed on launch
Summary: Menu Editor crashed on launch
Status: RESOLVED DUPLICATE of bug 200734
Alias: None
Product: kmenuedit
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-07 11:26 UTC by K.J. Petrie
Modified: 2009-10-09 00:28 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description K.J. Petrie 2009-10-07 11:26:36 UTC
Application that crashed: kmenuedit
Version of the application: 0.8
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.26.8.tex4 i686

What I was doing when the application crashed:
I right-clicked on the menu launcher button and selected the menu editor. It immediately crashed and launched the Crash Reporting Assistant

 -- Backtrace:
Application: KDE Menu Editor (kmenuedit), signal: Segmentation fault
[KCrash Handler]
#9  0xb6f7fb87 in qstrcmp () from /usr/lib/libQtCore.so.4
#10 0xb7314ce5 in KServiceGroup::KServiceGroup () from /usr/lib/libkdecore.so.5
#11 0xb73120fc in KServiceGroup::KServiceGroup$base () from /usr/lib/libkdecore.so.5
#12 0xb7313e63 in KServiceGroup::entries () from /usr/lib/libkdecore.so.5
#13 0xb7f5561e in kdemain () from /usr/lib/libkdeinit4_kmenuedit.so
#14 0xb7f56ed7 in kdemain () from /usr/lib/libkdeinit4_kmenuedit.so
#15 0xb7f58fc2 in kdemain () from /usr/lib/libkdeinit4_kmenuedit.so
#16 0xb7f5993b in kdemain () from /usr/lib/libkdeinit4_kmenuedit.so
#17 0xb7f44a5d in kdemain () from /usr/lib/libkdeinit4_kmenuedit.so
#18 0x0804863f in _start ()
#19 0xb6176a36 in __libc_start_main () from /lib/i686/libc.so.6
#20 0x08048591 in _start ()

This bug may be a duplicate of or related to bug 206456

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-09 00:28:48 UTC
Merging with bug 200734. Thanks

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