Am Freitag 10 September 2010 schrieb George Kiagiadakis: > On Fri, Sep 10, 2010 at 3:53 PM, Zsolt Rizsanyi > > <rizsanyi@users.sourceforge.net> wrote: > > On Fri, Sep 10, 2010 at 2:35 PM, Dietz Pröpper <dietz@rotfl.franken.de> wrote: > >> George Kiagiadakis: > >>> On Fri, Sep 10, 2010 at 12:02 PM, Dietz Pröpper > >>> <dietz@rotfl.franken.de> > >> > >> wrote: > >>> > - digikam from unstable crashes (the kde term for "crash" should > >>> > be "krash" imho ;-) on startup. > >>> > - marble (from 4.5.1) crashes on startup too. > >>> > >>> Marble seems to work just fine here. I'll check digikam as well... > >>> Do you have any backtraces? > >> > >> Unfortunately not. And just no time atm to go to 4.5.1 again to > >> check. > > > > Marble crashes on startup for me too. Here is a backtrace: > > Thread 3 (Thread 0xb1362b70 (LWP 4221)): > > #0 0xb4572e16 in *__GI_clock_gettime (clock_id=-1269338124, > > tp=0xb1361fb8) at ../sysdeps/unix/clock_gettime.c:100 > > #1 0xb6a631db in ?? () from /usr/lib/libQtCore.so.4 > > #2 0xb6a68435 in ?? () from /usr/lib/libQtCore.so.4 > > #3 0xb6a6847a in ?? () from /usr/lib/libQtCore.so.4 > > #4 0xb6a662e8 in ?? () from /usr/lib/libQtCore.so.4 > > #5 0xb6a66375 in ?? () from /usr/lib/libQtCore.so.4 > > #6 0xb44e47ca in g_main_context_prepare () from > > /lib/libglib-2.0.so.0 #7 0xb44e4be9 in ?? () from > > /lib/libglib-2.0.so.0 > > #8 0xb44e51b8 in g_main_context_iteration () from > > /lib/libglib-2.0.so.0 #9 0xb6a660df in > > QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsF > > lag>) () from /usr/lib/libQtCore.so.4 > > #10 0xb6a38b19 in > > QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () > > from /usr/lib/libQtCore.so.4 > > #11 0xb6a38f6a in > > QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from > > /usr/lib/libQtCore.so.4 > > #12 0xb693b629 in QThread::exec() () from /usr/lib/libQtCore.so.4 > > #13 0xb6a1895b in ?? () from /usr/lib/libQtCore.so.4 > > #14 0xb693dfbe in ?? () from /usr/lib/libQtCore.so.4 > > #15 0xb458e955 in start_thread (arg=0xb1362b70) at > > pthread_create.c:300 #16 0xb5b8e10e in clone () at > > ../sysdeps/unix/sysv/linux/i386/clone.S:130 > > > > It is a segfault. > > That's not very useful, you need to install libqt4-dbg before > generating the backtrace. Sorry, other backtrace was Digikam. Now Marble and also with installed libglib dbg package - I thought it was installed cause some function in it were detected, but it wasn't. DrKonqi says not useful, but I do not see what dbg package is still missing. apt-cache search marble dbg doesn't yield any result: Application: Marble-Schreibtischglobus (marble), signal: Segmentation fault [Current thread is 1 (Thread 0xb3788710 (LWP 26893))] Thread 3 (Thread 0xb10d6b70 (LWP 26894)): #0 0xb7738424 in __kernel_vsyscall () #1 0xb5b8d916 in *__GI___poll (fds=0xb5c11ff4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0xb44ff06b in IA__g_poll (fds=0x9ed8730, nfds=1, timeout=-1) at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gpoll.c:127 #3 0xb44f1dac in g_main_context_poll (context=0x9ed9840, block=<value optimized out>, dispatch=1, self=0x9ed8708) at /build/buildd- glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2904 #4 g_main_context_iterate (context=0x9ed9840, block=<value optimized out>, dispatch=1, self=0x9ed8708) at /build/buildd-glib2.0_2.24.1-1- i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2586 #5 0xb44f21b8 in IA__g_main_context_iteration (context=0x9ed9840, may_block=1) at /build/buildd-glib2.0_2.24.1-1- i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2654 #6 0xb6a730df in QEventDispatcherGlib::processEvents (this=0x9edede8, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #7 0xb6a45b19 in QEventLoop::processEvents (this=0xb10d6290, flags=) at kernel/qeventloop.cpp:149 #8 0xb6a45f6a in QEventLoop::exec (this=0xb10d6290, flags=...) at kernel/qeventloop.cpp:201 #9 0xb6948629 in QThread::exec (this=0x9ed4c00) at thread/qthread.cpp:487 #10 0xb6a2595b in QInotifyFileSystemWatcherEngine::run (this=0x9ed4c00) at io/qfilesystemwatcher_inotify.cpp:248 #11 0xb694afbe in QThreadPrivate::start (arg=0x9ed4c00) at thread/qthread_unix.cpp:248 #12 0xb459b955 in start_thread (arg=0xb10d6b70) at pthread_create.c:300 #13 0xb5b9b10e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 2 (Thread 0xb05a5b70 (LWP 26898)): #0 0xb44f1822 in IA__g_main_context_prepare (context=0x9fcc100, priority=0xb05a514c) at /build/buildd-glib2.0_2.24.1-1- i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2296 #1 0xb44f1be9 in g_main_context_iterate (context=0x9fcc100, block=<value optimized out>, dispatch=1, self=0x9fd3b18) at /build/buildd- glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2571 #2 0xb44f21b8 in IA__g_main_context_iteration (context=0x9fcc100, may_block=1) at /build/buildd-glib2.0_2.24.1-1- i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c:2654 #3 0xb6a730df in QEventDispatcherGlib::processEvents (this=0x9fc96d0, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #4 0xb6a45b19 in QEventLoop::processEvents (this=0xb05a5290, flags=) at kernel/qeventloop.cpp:149 #5 0xb6a45f6a in QEventLoop::exec (this=0xb05a5290, flags=...) at kernel/qeventloop.cpp:201 #6 0xb6948629 in QThread::exec (this=0x9ec3538) at thread/qthread.cpp:487 #7 0xb6a2595b in QInotifyFileSystemWatcherEngine::run (this=0x9ec3538) at io/qfilesystemwatcher_inotify.cpp:248 #8 0xb694afbe in QThreadPrivate::start (arg=0x9ec3538) at thread/qthread_unix.cpp:248 #9 0xb459b955 in start_thread (arg=0xb05a5b70) at pthread_create.c:300 #10 0xb5b9b10e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb3788710 (LWP 26893)): [KCrash Handler] #7 0xb74c74b1 in ?? () from /usr/lib/libmarblewidget.so.10 #8 0xb74c86e6 in ?? () from /usr/lib/libmarblewidget.so.10 #9 0xb74eee36 in ?? () from /usr/lib/libmarblewidget.so.10 #10 0xb74d51bd in Marble::GeoParser::parseDocument() () from /usr/lib/libmarblewidget.so.10 #11 0xb74d534e in Marble::GeoParser::parseDocument() () from /usr/lib/libmarblewidget.so.10 #12 0xb74d534e in Marble::GeoParser::parseDocument() () from /usr/lib/libmarblewidget.so.10 #13 0xb74d534e in Marble::GeoParser::parseDocument() () from /usr/lib/libmarblewidget.so.10 #14 0xb74d534e in Marble::GeoParser::parseDocument() () from /usr/lib/libmarblewidget.so.10 #15 0xb74d534e in Marble::GeoParser::parseDocument() () from /usr/lib/libmarblewidget.so.10 #16 0xb74d566e in Marble::GeoParser::read(QIODevice*) () from /usr/lib/libmarblewidget.so.10 #17 0xb7584a85 in Marble::MapThemeManager::loadMapThemeFile(QString const&) () from /usr/lib/libmarblewidget.so.10 #18 0xb758774a in Marble::MapThemeManager::loadMapTheme(QString const&) () from /usr/lib/libmarblewidget.so.10 #19 0xb7587a83 in Marble::MapThemeManager::createMapThemeRow(QString const&) () from /usr/lib/libmarblewidget.so.10 #20 0xb7589b64 in Marble::MapThemeManager::updateMapThemeModel() () from /usr/lib/libmarblewidget.so.10 #21 0xb758a4f2 in Marble::MapThemeManager::initialize() () from /usr/lib/libmarblewidget.so.10 #22 0xb758a53b in Marble::MapThemeManager::mapThemeModel() () from /usr/lib/libmarblewidget.so.10 #23 0x08056b84 in _start () > > BTW which version of Qt are you using? My Qt version is 4:4.6.3-1+b1 > > and libglib2.0-0 2.24.1-1. I can try some other versions if needed. > > Hmm.. I'm actually using Qt 4.7.0~rc1 from experimental and glib > 2.24.1, like you. 4:4.6.3-1+b1, same glib. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Attachment:
signature.asc
Description: This is a digitally signed message part.