Bug 182144 - marble crashes when there are no plugins
Summary: marble crashes when there are no plugins
Status: RESOLVED DOWNSTREAM
Alias: None
Product: marble
Classification: Applications
Component: data (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Torsten Rahn
URL:
Keywords:
: 180374 182375 182457 182459 182635 182730 201959 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-28 10:20 UTC by Oliver Wieland
Modified: 2009-09-20 08:44 UTC (History)
11 users (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 Oliver Wieland 2009-01-28 10:20:38 UTC
Version:           0.10.0-RC1 (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

After starting the program, digikam crashes everytime.

###################################
oli@jojo:~/Bilder$ digikam                                        
digikam(22575) Phonon::KdePlatformPlugin::createBackend: using backend:  "Xine"
Starting to load Plugins.                                                      
Files:  "initrd.img"                                                           
Files:  "initrd.img.old"
Files:  "vmlinuz"
Files:  "vmlinuz.old"
=== MarbleDirs: ===
Local Path: "/home/oli/.marble/data"
Plugin Local Path: "/home/oli/.marble/plugins"

Marble Data Path (Run Time) : ""
Marble Data Path (Compile Time): "/usr/share/kde4/apps/marble/data"

Marble Plugin Path (Run Time) : ""
Marble Plugin Path (Compile Time): "/usr/lib/kde4/plugins/marble"

System Path: "/usr/share/kde4/apps/marble/data"
Plugin System Path: ""
===================
"initrd.img"  -  "/boot/initrd.img-2.6.27-3-rt"
KCrash: Application 'digikam' crashing...
sock_file=/home/oli/.kde/socket-jojo/kdeinit4__0

########################################



Anwendung: digiKam (digikam), Signal SIGSEGV
0x00007f614f340621 in nanosleep () from /lib/libc.so.6
[Current thread is 0 (LWP 22739)]

Thread 9 (Thread 0x41e9a950 (LWP 22740)):
#0  0x00007f614f0872d9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f614fe21349 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2  0x000000000064fd4b in ?? ()
#3  0x00007f614fe20362 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#5  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 8 (Thread 0x4269b950 (LWP 22743)):
#0  0x00007f614f0872d9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f614fe21349 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2  0x00007f615360fe24 in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1
#3  0x00007f614fe20362 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#5  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 7 (Thread 0x4100c950 (LWP 22744)):
#0  0x00007f614f0872d9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f614fe21349 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#2  0x00007f615360fe24 in Digikam::LoadSaveThread::run () from /usr/lib/libdigikamcore.so.1
#3  0x00007f614fe20362 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#5  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 6 (Thread 0x42e9c950 (LWP 22745)):
#0  0x00007f614f08755d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f613fa0df31 in ?? () from /usr/lib/libxine.so.1
#2  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#3  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x4369d950 (LWP 22746)):
#0  0x00007f614f377482 in select () from /lib/libc.so.6
#1  0x00007f613fa369e4 in xine_usec_sleep () from /usr/lib/libxine.so.1
#2  0x00007f613fa1bc0b in ?? () from /usr/lib/libxine.so.1
#3  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#4  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#5  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x43e9e950 (LWP 22747)):
#0  0x00007f614f084ac9 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x00000000000014b2 in ?? ()
#2  0x0000000000000001 in ?? ()
#3  0x000000000351c280 in ?? ()
#4  0x000000000351dcb0 in ?? ()
#5  0x0000000000000001 in ?? ()
#6  0x00007f614a7bfde0 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x00007f614a5393f1 in ?? () from /usr/lib/libglib-2.0.so.0
#8  0x00007f614a5396cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#9  0x00007f614ff3117e in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#10 0x00007f614ff07682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#11 0x00007f614ff0780d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#12 0x00007f614fe1d3f8 in QThread::exec () from /usr/lib/libQtCore.so.4
#13 0x00007f613fc69a74 in ?? () from /usr/lib/kde4/plugins/phonon_backend/phonon_xine.so
#14 0x00007f614fe20362 in ?? () from /usr/lib/libQtCore.so.4
#15 0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#16 0x00007f614f37ec6d in clone () from /lib/libc.so.6
#17 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x4469f950 (LWP 22750)):
#0  0x00007f614f375206 in poll () from /lib/libc.so.6
#1  0x00007f6139c0f909 in ?? () from /usr/lib/xine/plugins/1.24/xineplug_ao_out_alsa.so
#2  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#3  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x44ea0950 (LWP 22751)):
#0  0x00007f614f0872d9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f613fa1f0c3 in ?? () from /usr/lib/libxine.so.1
#2  0x00007f614f0833ea in start_thread () from /lib/libpthread.so.0
#3  0x00007f614f37ec6d in clone () from /lib/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f61562fc6f0 (LWP 22739)):
[KCrash Handler]
#5  0x00007f6152c6c35f in Marble::PluginManager::loadPlugins () from /usr/lib/libmarblewidget.so.4
#6  0x00007f6152c6cdd4 in Marble::PluginManager::PluginManager () from /usr/lib/libmarblewidget.so.4
#7  0x00007f6152c6a849 in Marble::LayerManager::LayerManager () from /usr/lib/libmarblewidget.so.4
#8  0x00007f6152c2f7ef in Marble::MarbleModel::MarbleModel () from /usr/lib/libmarblewidget.so.4
#9  0x00007f6152c3846a in Marble::MarbleMap::MarbleMap () from /usr/lib/libmarblewidget.so.4
#10 0x00007f6152c2c6d9 in Marble::MarbleWidget::MarbleWidget () from /usr/lib/libmarblewidget.so.4
#11 0x00007f61536c4fd0 in ?? () from /usr/lib/libdigikamcore.so.1
#12 0x00007f61536c18ab in Digikam::ImagePropertiesGPSTab::ImagePropertiesGPSTab () from /usr/lib/libdigikamcore.so.1
#13 0x00007f61536aaf57 in Digikam::ImagePropertiesSideBar::ImagePropertiesSideBar () from /usr/lib/libdigikamcore.so.1
#14 0x000000000046910d in _start ()
Comment 1 caulier.gilles 2009-01-28 12:03:35 UTC
Another crash in marble....

Gilles Caulier
Comment 2 Torsten Rahn 2009-01-28 12:53:26 UTC
Obviously your plugin path isn't set correctly. If you got Marble and/or Digikam as a package blame your distributor.

Comment 3 Torsten Rahn 2009-01-28 12:55:38 UTC
Does Marble as a standalone application start well?
Comment 4 Luka Renko 2009-01-28 13:44:42 UTC
This is the problem with Debian/Ubuntu packages: plugins are not distributed in "libmarble4" package (which digikam depends on), but in separate "marble" package (which should ship standalone applications).

Workaround is to install "marble" package - this should workaround the problem for you until the packages are fixed.

I will close this bug as DOWNSTREAM and open bug in Ubuntu (and also notify debian developers about this).
Comment 5 Oliver Wieland 2009-01-28 14:22:49 UTC
Wow, that was fast!

Thanks, that worked for me!
Oli
Comment 6 Torsten Rahn 2009-01-28 15:01:39 UTC
Thanks Luka! :-)
Comment 7 Luka Renko 2009-01-28 18:23:29 UTC
Link to Ubuntu bug: https://launchpad.net/bugs/322278
Comment 8 Torsten Rahn 2009-01-28 18:55:21 UTC
Luka: The Marble-KPart should rather be shipped with the application. 

Otherwise the widget would require KDE 4 to be installed. If the KPart is shipped with the application then even people who don't have KDE 4 installed should be able to use it, as the only components that require KDE 4 are the KPart and the application. 
Comment 9 Luka Renko 2009-01-28 19:01:43 UTC
Torsten: good point. Will take care of this.
Comment 10 Torsten Rahn 2009-01-30 11:00:35 UTC
*** Bug 182375 has been marked as a duplicate of this bug. ***
Comment 11 Pino Toscano 2009-01-30 18:24:50 UTC
*** Bug 182459 has been marked as a duplicate of this bug. ***
Comment 12 Pino Toscano 2009-01-30 18:24:57 UTC
*** Bug 182457 has been marked as a duplicate of this bug. ***
Comment 13 Pino Toscano 2009-01-30 18:25:48 UTC
*** Bug 180374 has been marked as a duplicate of this bug. ***
Comment 14 Pino Toscano 2009-01-30 18:26:46 UTC
... even if IMHO Marble shouldn't crash in such situation.
Comment 15 Torsten Rahn 2009-01-30 23:13:24 UTC
That's why I fixed it:

http://lists.kde.org/?l=kde-commits&m=123333313509984&w=2

Still not a good excuse for "ew, I don't know where to put this but lets just assume it works fine in this place"-packaging.
Comment 16 Pino Toscano 2009-02-01 15:19:45 UTC
*** Bug 182730 has been marked as a duplicate of this bug. ***
Comment 17 Torsten Rahn 2009-02-01 17:08:08 UTC
*** Bug 182635 has been marked as a duplicate of this bug. ***
Comment 18 Torsten Rahn 2009-07-10 18:21:21 UTC
*** Bug 194832 has been marked as a duplicate of this bug. ***
Comment 19 Dario Andres 2009-07-31 15:33:50 UTC
*** Bug 201959 has been marked as a duplicate of this bug. ***
Comment 20 caulier.gilles 2009-09-06 19:12:29 UTC
*** Bug 205601 has been marked as a duplicate of this bug. ***
Comment 21 Dedanna1029 2009-09-20 08:44:14 UTC
I have this issue as well in Mandriva Cooker, and have for quite some time.

https://qa.mandriva.com/show_bug.cgi?id=52374

The bug was closed at the time, stating that it was reported upstream. You are saying it's downstream. I don't know where to go or what to do for this issue now, as Showfoto is still crashing on me.