Bug 163928 - Marble crashes at startup
Summary: Marble crashes at startup
Status: RESOLVED FIXED
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Torsten Rahn
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-12 20:35 UTC by Johannes von Scheidt
Modified: 2008-07-17 20:54 UTC (History)
0 users

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 Johannes von Scheidt 2008-06-12 20:35:30 UTC
Version:           4.0.80 (using KDE 4.0.5)
Installed from:    Ubuntu Packages
Compiler:          c++ 
OS:                Linux

Here is the backtrace:

Application: Marble-Schreibtischglobus (marble), signal SIGSEGV
(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)
(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 0xb610f720 (LWP 14702)]
[New Thread 0xb4748b90 (LWP 14703)]
(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)
(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]
#6  0xb77c59e7 in ?? () from /usr/lib/kde4/lib/libmarblewidget.so.4
#7  0xb7820d30 in ?? () from /usr/lib/kde4/lib/libmarblewidget.so.4
#8  0xb77d7b50 in MarbleModel::setupTextureMapper ()
   from /usr/lib/kde4/lib/libmarblewidget.so.4
#9  0xb77d7de2 in MarbleModel::setMapTheme ()
   from /usr/lib/kde4/lib/libmarblewidget.so.4
#10 0xb77da928 in MarbleMap::setMapThemeId ()
   from /usr/lib/kde4/lib/libmarblewidget.so.4
#11 0xb77d49b2 in MarbleWidget::setMapThemeId ()
   from /usr/lib/kde4/lib/libmarblewidget.so.4
#12 0x0805aea7 in ?? ()
#13 0x0805b90c in ?? ()
#14 0x0805c731 in ?? ()
#15 0x08059bb7 in ?? ()
#16 0x0805945c in ?? ()
#17 0xb697b450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#18 0x08053b11 in _start ()
#0  0xb7fa8410 in __kernel_vsyscall ()
Comment 1 Christophe Marin 2008-06-12 21:16:05 UTC
Can't reproduce in trunk (kdeedu rev. 819895).

Please follow this guide to provide an useful backtrace : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Andi Clemens 2008-06-14 16:08:43 UTC
I can reproduce this, I know that 1 week ago compiling from trunk created a lot of tiles, but now it doesn't anymore. Although I deleted my whole kde4 installdir and the settings in my homefolder. If I want to start marble, it just hangs while creating tiles (which it can't because there seems to be no data). If I kill the process in gdb, I get the following BT:

#0  0xb7f29424 in __kernel_vsyscall ()
#1  0xb6e54ee7 in poll () from /lib/libc.so.6
#2  0xb6cfc382 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#3  0xb6cfc668 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#4  0xb7e4769d in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#5  0xb75b892e in ?? () from /usr/lib/libQtGui.so.4
#6  0xb7e1e1cf in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#7  0xb7e1e390 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#8  0xb79521c2 in QDialog::exec () from /usr/lib/libQtGui.so.4
#9  0xb70a66fc in MarbleModel::setMapTheme () from /opt/kdemod/lib/libmarblewidget.so.5
#10 0xb70ab2da in MarbleMap::setMapThemeId () from /opt/kdemod/lib/libmarblewidget.so.5
#11 0xb70a15a4 in MarbleWidget::setMapThemeId () from /opt/kdemod/lib/libmarblewidget.so.5
#12 0x0805e034 in MainWindow::readSettings ()
#13 0x0805e930 in MainWindow::MainWindow ()
#14 0x08059574 in main ()

Actually I wanted to compile digiKam, but without Marble it is not starting anymore. I even installed a package of Marble provided by archlinux which has been generated 5 days ago. This package also doesn't work so there must be something wrong in trunk.
Comment 3 Andi Clemens 2008-06-14 16:29:57 UTC
Ok it works now, but I had to copy srtm.jpg to the system and local path like described in http://bugs.kde.org/show_bug.cgi?id=161474#c8 

The compile option did not work for me, so I guess cmake is making trouble here?
Comment 4 Torsten Rahn 2008-07-17 20:54:50 UTC
This bug should be resolved now. Please reopen this bug if the problem still exists with current SVN/packages.