Bug 67783

Summary: noatun crash on exit
Product: noatun Reporter: Amit Shah <amitshah>
Component: generalAssignee: Multimedia Developers <kde-multimedia>
Status: RESOLVED NOT A BUG    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Amit Shah 2003-11-10 15:59:41 UTC
Version:           kde3.2beta1 (using KDE KDE 3.1.93)
Installed from:    Compiled From Sources
Compiler:          gcc3.3.2 
OS:          Linux

compiled from konstruct

(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)...[New Thread 1095599392 (LWP 32428)]
(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)...0x4115e30e in __waitpid_nocancel ()
   from /lib/tls/libpthread.so.0
#0  0x4115e30e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#1  0x40792784 in KCrash::defaultCrashHandler(int) ()
   from /home/Amit/kde3.2-beta1/lib/libkdecore.so.4
#2  <signal handler called>
#3  0x40b859f9 in QPalette::QPalette(QPalette const&) ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#4  0x40b1b61a in QApplication::style() ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#5  0x40baa2ea in QWidget::style() const ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#6  0x40c76ac8 in QPopupMenu::hidePopups() ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#7  0x40c752f9 in QPopupMenu::~QPopupMenu() ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#8  0x404a16e0 in KPopupMenu::~KPopupMenu() ()
   from /home/Amit/kde3.2-beta1/lib/libkdeui.so.4
#9  0x404c8c18 in KActionMenu::~KActionMenu() ()
   from /home/Amit/kde3.2-beta1/lib/libkdeui.so.4
#10 0x415e572d in NoatunStdAction::PluginActionMenu::~PluginActionMenu() ()
   from /home/Amit/kde3.2-beta1/lib/libnoatun.so.1
#11 0x40b76ce8 in QObject::~QObject() ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#12 0x40b1a6ab in QApplication::~QApplication() ()
   from /home/Amit/kde3.2-beta1/lib/libqt-mt.so.3
#13 0x406fe879 in KApplication::~KApplication() ()
   from /home/Amit/kde3.2-beta1/lib/libkdecore.so.4
#14 0x407b1e67 in KUniqueApplication::~KUniqueApplication() ()
   from /home/Amit/kde3.2-beta1/lib/libkdecore.so.4
#15 0x415b14a6 in NoatunApp::~NoatunApp() ()
   from /home/Amit/kde3.2-beta1/lib/libnoatun.so.1
#16 0x408ac330 in kdemain ()
   from /home/Amit/kde3.2-beta1/lib/libkdeinit_noatun.so
#17 0x408a9a46 in kdeinitmain ()
   from /home/Amit/kde3.2-beta1/lib/kde3/noatun.so
#18 0x0804cc66 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#19 0x0804e131 in handle_launcher_request(int) ()
#20 0x0804e629 in handle_requests(int) ()
#21 0x0804f522 in main ()
Comment 1 Maksim Orlovich 2003-11-10 16:07:56 UTC
The same report as #67472, also from you. 
Comment 2 Stefan Gehn 2003-11-10 18:56:36 UTC
try to choose a different widget style (something like "windows" or "hicolor" preferred) and see if it still happens.
Comment 3 Amit Shah 2003-11-12 09:23:37 UTC
Subject: Re:  noatun crash on exit

On Monday 10 Nov 2003 23:26, Stefan Gehn wrote:
> try to choose a different widget style (something like "windows" or
> "hicolor" preferred) and see if it still happens.

I don't have the hicolor style; but running with 'windows' and exiting 
didn't give me a crash. I tried this several times with and without --style 
windows. With the default style, it crashes. With the windows style, it 
doesn't crash.