Bug 286069 - marble crashes under ubuntu unity on exit
Summary: marble crashes under ubuntu unity on exit
Status: RESOLVED FIXED
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 1.3 (KDE 4.8)
Assignee: Bernhard Beschow
URL:
Keywords:
: 284294 287209 300379 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-11-08 00:50 UTC by hansglotzen
Modified: 2013-04-07 15:47 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (1.66 KB, text/plain)
2012-02-23 06:40 UTC, Claudio Tubertini
Details
New crash information added by DrKonqi (1.14 KB, text/plain)
2012-08-30 16:13 UTC, Mat
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hansglotzen 2011-11-08 00:50:11 UTC
Application: marble (1.2.2 (stable release))
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-12-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

marble crashes under ubuntu unity on exit (by pressing window manager x button)

The crash can be reproduced every time.

-- Backtrace:
Application: Marble – Virtueller Globus (marble), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7818710 (LWP 7706))]

Thread 2 (Thread 0xb6bf9b70 (LWP 7709)):
#0  0x02b0dd44 in __pthread_mutex_unlock_usercnt () from /lib/i386-linux-gnu/libpthread.so.0
#1  0x00436f54 in pthread_mutex_unlock () from /lib/i386-linux-gnu/libc.so.6
#2  0x02b67565 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x02b67f9b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x0371dcea in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#5  0x02b8e5f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x02b0ad31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#7  0x004290ce in clone () from /lib/i386-linux-gnu/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb7818710 (LWP 7706)):
[KCrash Handler]
#7  0x03d9b7a0 in ?? ()
#8  0x0692255c in qt_call_post_routines() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#9  0x044b84da in QApplication::~QApplication() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#10 0x01012378 in KApplication::~KApplication() () from /usr/lib/libkdeui.so.5
#11 0x0805d10d in main (argc=) at ../../src/kdemain.cpp:278

Possible duplicates by query: bug 283401, bug 268923, bug 266528.

Reported using DrKonqi
Comment 1 Bernhard Beschow 2011-11-26 13:54:33 UTC
*** Bug 284294 has been marked as a duplicate of this bug. ***
Comment 2 Bernhard Beschow 2011-11-26 13:55:09 UTC
*** Bug 287209 has been marked as a duplicate of this bug. ***
Comment 3 Bernhard Beschow 2011-11-26 14:10:23 UTC
Does the crash happen if you let Marble run for at least 30 seconds after having performed the last click?
Comment 4 Bernhard Beschow 2011-12-06 21:59:57 UTC
Comment by Hans:

"Ja, auch bei längerer Nutzung von 30 Sekunden. Leider tritt das gleiche
Phänomen bei LXDE auf"

which translates to:

"Yes, also on longer usage than 30 seconds. Unfortunately, the same phenomena is present under LXDE"
Comment 5 Claudio Tubertini 2012-02-23 06:40:57 UTC
Created attachment 69027 [details]
New crash information added by DrKonqi

marble (1.2.2 (stable release)) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4

- What I was doing when the application crashed:

I closed the application clicking on x window button

-- Backtrace (Reduced):
#8  0x0027955c in qt_call_post_routines() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#9  0x0514350a in QApplication::~QApplication() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#10 0x010b2668 in KApplication::~KApplication() () from /usr/lib/libkdeui.so.5
#11 0x0805d10d in main (argc=) at ../../src/kdemain.cpp:278
Comment 6 Mat 2012-08-30 16:13:02 UTC
Created attachment 73563 [details]
New crash information added by DrKonqi

marble (1.2.2 (stable release)) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4

- What I was doing when the application crashed:

Every time I close Marble (X button, quit, ctrl-Q), it shows up as a crash. No visible side-effects other than this. Tried waiting 30s after last click as suggested above - no change. Standard settings in Marble, running Linux Mint 12 on Eee PC. Will provide more details if needed. (warning: Linux newbie)

-- Backtrace (Reduced):
#8  0x085ed55c in qt_call_post_routines() () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#9  0x040a650a in QApplication::~QApplication() () from /usr/lib/i386-linux-gnu/libQtGui.so.4
#10 0x011cf668 in KApplication::~KApplication() () from /usr/lib/libkdeui.so.5
#11 0x0805d10d in main (argc=) at ../../src/kdemain.cpp:278
Comment 7 Bernhard Beschow 2013-01-09 09:04:32 UTC
*** Bug 300379 has been marked as a duplicate of this bug. ***