Bug 263465 - Marble crashes on start on reading config file from previous version
Summary: Marble crashes on start on reading config file from previous version
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: some future version
Assignee: marble-bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-01-17 20:50 UTC by Friedrich W. H. Kossebau
Modified: 2018-10-27 04:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Marble config file which made Marble crash on start (969 bytes, text/plain)
2011-01-17 20:50 UTC, Friedrich W. H. Kossebau
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Friedrich W. H. Kossebau 2011-01-17 20:50:58 UTC
Created attachment 56147 [details]
Marble config file which made Marble crash on start

Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

After one of the recent minor versions updates (to 4.5.4?) Marble started to crash right after the start, just after showing the mainwindow for less than a second. Installing the debugging info gave no useful backtrace, even with the help of DrKonqui. Config file to test attached.

Marble starts and runs fine after removing the config file. But other users upgrading might run into this issue as well.

Reproducible: Always

Steps to Reproduce:
Preparation:
Copy the attached config file to $(kde-config --localprefix)share/config/marblerc

Steps:
1. Start marble, done.

Actual Results:  
Marble crashes, DrKonqi dialog is shown.

Expected Results:  
Marbles starts fine.
Comment 1 Dennis Nienhüser 2011-01-17 23:03:20 UTC
Hi Friedrich,

thanks for reporting. We have other reports of crashes after upgrading which I'm not able to reproduce, so any help to track it down is appreciated. I just tried the 4.6 release candidate from SVN together with your config file, but Marble starts up fine here.
I'm suspecting the activated plugins in the config file to cause the crash. You do have two which I don't have: GeoRenderer-plugin is not in use anymore, externaldraw is installed by digikam. If they're built again an older Marble lib, that could be the reason for the crash.

Can you try two things, please:
Remove GeoRenderer-plugin and/or externaldraw from the config file and see if that makes a difference. To do that, remove the appropriate column in the three config entries in the [Plugins] section, e.g. to remove externaldraw, make it read

[Plugins]
pluginEnabled=0,1,1,1,1,1,1,1,0,1,1,1,1
pluginNameId=aprs-plugin,compass,crosshairs,GeoRenderer-plugin,coordinate-grid,scalebar,navigation,overviewmap,photo,progress,stars,weather,wikipedia
pluginVisible=1,1,1,1,1,1,0,1,0,0,1,0,0

When Marble starts with one or both of them removed, can you please call ldd on those plugins and post the output here? I'm interested in the marblewidget lib they link against, and whether they exist at all.

ldd /usr/lib/kde4/plugins/marble/ExternalDrawPlugin.so | grep marble
Comment 2 Dennis Nienhüser 2011-01-26 22:56:46 UTC
Any news? :-)
Comment 3 Friedrich W. H. Kossebau 2011-01-31 00:21:00 UTC
Finally found some time to (meanwhile updated to 4.6.0 by accident, crash still there). So here are some news :) No good ones, so.

Tried as you told me (hm, upgrade seems to have removed GeoRenderer-plugin from config), still crashes. So stripped the condig file to pure
"
[MarbleWidget]
mapTheme=earth/openstreetmap/openstreetmap.dgml
"
and marble still crashes :( Doesn't if another mapTheme is set.

The output you requested (was ExternalDraw.so, not ExternalDrawPlugin.so):
ldd /usr/lib/kde4/plugins/marble/ExternalDraw.so | grep marble
        libmarblewidget.so.11 => /usr/lib/libmarblewidget.so.11 (0x099e0000)
And that file is present, as is the one it links to, libmarblewidget.so.0.11.0

There is no /usr/share/kde4/config/marblerc.
Worse: running marble as another system user with exactly the same config file gives no crashes...

Any other place some config file, plugin or whatever could be hiding? I did not find anything in the pathes...

What else could I try?
Comment 4 Friedrich W. H. Kossebau 2011-02-20 03:06:05 UTC
No idea what the change was, but now it no longer crashes. Still the OSM plugin does not work, view is black and does not get rendered, besides by the view plugins (crosshair etc.) which leave traces when the view is moved around.
Perhaps interesting excerpt from the log given by --debug-info is:
"
Style reset requested. 
kiloBytes 30720 
"Setting tile cache to 30720 kilobytes." 
Theme changed to  "earth/openstreetmap/openstreetmap.dgml" 
Expected a GeoDataDocument, didn't get one though 
true 
FileStorageWatcher: Creating cache size 
"
Strange thing is still only happens for one user on my machine. But I could not find any self-compiled plugin anywhere (and don't remember I ever did, also all other map plugins work...)
Comment 5 Andrew Crouthamel 2018-09-25 03:55:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 04:19:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!