| Summary: | Marble crashes on start | ||
|---|---|---|---|
| Product: | [Applications] marble | Reporter: | beojan <beojan> |
| Component: | general | Assignee: | marble-bugs |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | mgraesslin, nienhueser |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
beojan
2013-01-04 12:04:26 UTC
Created attachment 76320 [details]
New crash information added by DrKonqi
marble (1.5.20 (development snapshot)) on KDE Platform 4.9.90 using Qt 4.8.2
- What I was doing when the application crashed:
tried to start marble after a complete rebuild from current master (7de6214438c13c22bbe392d681bba3a6ac55ef1c). Crashes directly at start
-- Backtrace (Reduced):
#7 QString (other=..., this=0x7fff68d80f50) at /usr/include/qt4/QtCore/qstring.h:726
#8 Marble::GeoSceneGeodata::sourceFile (this=0x15fb620) at /home/martin/kdesrc/kde/kdeedu/marble/src/lib/geodata/scene/GeoSceneGeodata.cpp:47
#9 0x00007f46e92077e3 in Marble::MarbleModel::setMapThemeId (this=0xf37a48, mapThemeId=...) at /home/martin/kdesrc/kde/kdeedu/marble/src/lib/MarbleModel.cpp:324
#10 0x000000000042fc4d in Marble::MarblePart::readSettings (this=this@entry=0xdfce50) at /home/martin/kdesrc/kde/kdeedu/marble/src/marble_part.cpp:463
#11 0x0000000000431f97 in Marble::MarblePart::MarblePart (this=0xdfce50, parentWidget=0xdfe5e0, parent=<optimized out>, arguments=..., __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /home/martin/kdesrc/kde/kdeedu/marble/src/marble_part.cpp:172
starting marble from console gives me: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/martin/.local/share/marble/maps/earth/placemarks/ Ignoring the following plugin since it couldn't be loaded: "/home/martin/kde/lib/kde4/plugins/marble/QNamNetworkPlugin.so" Git commit 0b9a7cc54f901ce4698f498b1c52607aaa2704a6 by Dennis Nienhüser. Committed on 09/01/2013 at 00:02. Pushed by nienhueser into branch 'master'. Create placemark cache directory, if needed. Fixes watching offline maps installation when there is no offline map yet and avoids the inotify warning. M +6 -1 src/plugins/runner/local-osm-search/LocalOsmSearchPlugin.cpp http://commits.kde.org/marble/0b9a7cc54f901ce4698f498b1c52607aaa2704a6 Martin, please delete the file /home/martin/kde/lib/kde4/plugins/marble/QNamNetworkPlugin.so We have removed all network plugins recently. The commit above is unrelated to the crash, but silences the other two warnings you get. After an update it likely crashes silenty now ;-) Thibaut will commit a safety check soon around MarbleModel:324. Can you please report which map theme is trying to be loaded at startup? grep mapTheme ~/.kde/share/config/marblerc extracts it from the config file. deleting the contents of the marble plugins directory, then reinstalling (with make install/fast) has fixed the crash for me. > Can you please report which map theme is trying to be loaded at startup?
> grep mapTheme ~/.kde/share/config/marblerc
> extracts it from the config file.
I moved away the marblerc and it still crashed, but will do the grep
nevertheless (on old and new marblerc) once I'm back on the other system where
I had the crash.
(In reply to comment #6) > I moved away the marblerc and it still crashed, but will do the grep > nevertheless (on old and new marblerc) once I'm back on the other system > where > I had the crash. Thanks. We've been looking at all map themes under our control and think that they couldn't cause this crash, but knowing the map theme would still make testing easier. Based on that and on comment #5 I wonder if the real problem is some ABI problem. For example a now outdated plugin might still be loaded (or load an old libmarblewidget.so) and result in a crash with a misleading backtrace. > Based on that and on comment #5 I wonder if the real problem is some ABI
> problem. For example a now outdated plugin might still be loaded (or load an
> old libmarblewidget.so) and result in a crash with a misleading backtrace.
quite possible, I just did a make install without deleting the installation
directory before. If that is a common problem: we have ABI checkers in KWin to
not load incompatible libs (e.g. decos, effects).
Git commit b769d371ea750fc6ea709c9436854ec0ae71ce7c by Thibaut Gridel. Committed on 09/01/2013 at 20:05. Pushed by tgridel into branch 'master'. MarbleModel: be clear that geodata layers need geodata datasets Does not fix the original crash in any way M +5 -5 src/lib/MarbleModel.cpp http://commits.kde.org/marble/b769d371ea750fc6ea709c9436854ec0ae71ce7c deleting the plugin solved the crash - thanks for the help. Now I can enjoy the new features :-) Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! 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 mark the bug 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! 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! |