[Bug 1017342] New: KDE:Extra: Bug digikam crash when selcting map tool
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 Bug ID: 1017342 Summary: KDE:Extra: Bug digikam crash when selcting map tool Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: kde-maintainers@suse.de Reporter: epistemepromeneur@free.fr QA Contact: opensuse-communityscreening@forge.provo.novell.com Found By: --- Blocker: --- opensuse 42.2 digikam 5.3.0 i replaced all system packages by those of kde applications and kde extra when i click on the map tool then digikam disappears after a short delay. here is the crash report **************************************************************************** Application: digikam (5.3.0) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: i was clicking on map tool to display the map corresponding to a photo The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Floating point exception Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1c7d63e9c0 (LWP 20881))] Thread 12 (Thread 0x7f1bbffff700 (LWP 20912)): #0 0x00007f1c75110458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c7930c5a8 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1c793089a0 in ?? () from /usr/lib64/libQt5Core.so.5 #3 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7f1be7fff700 (LWP 20897)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8e6e3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f1beffff700 (LWP 20896)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8e6e3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f1bf4dae700 (LWP 20895)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8e6e3 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f1bf55af700 (LWP 20894)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6dc8d70d in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6dfb0341 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f1bf657a700 (LWP 20893)): #0 0x00007f1c6fd6269e in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x00007f1c6fd648fb in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f1c6fd65230 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f1c6fd6542c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f1c7951e32b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f1c794cbfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #6 0x00007f1c79306f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f1c3729a700 (LWP 20890)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c6df81873 in ?? () from /usr/lib64/libQt5WebKit.so.5 #2 0x00007f1c6df81899 in ?? () from /usr/lib64/libQt5WebKit.so.5 #3 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f1c49880700 (LWP 20887)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c7930c65b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1c7bf7dc99 in Digikam::ParkingThread::run (this=0x1ea9050) at /usr/src/debug/digikam-5.3.0/core/libs/threads/threadmanager.cpp:115 #3 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f1c4a081700 (LWP 20884)): #0 0x00007f1c751100af in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f1c7930c65b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQt5Core.so.5 #2 0x00007f1c7cb99f40 in Digikam::ScanController::run (this=0x7f1c7d4a6ae0 <_ZZN7Digikam12_GLOBAL__N_113Q_QGS_creator13innerFunctionEvE6holder>) at /usr/src/debug/digikam-5.3.0/core/libs/database/utils/scancontroller.cpp:677 #3 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #4 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f1c4a91a700 (LWP 20883)): #0 0x00007f1c789fc51d in read () from /lib64/libc.so.6 #1 0x00007f1c6fda5670 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f1c6fd64e49 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f1c6fd652a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f1c6fd6542c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x00007f1c7951e32b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #6 0x00007f1c794cbfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #7 0x00007f1c79306f1a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x00007f1c753371d5 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #10 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #11 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f1c525e5700 (LWP 20882)): #0 0x00007f1c78a0049d in poll () from /lib64/libc.so.6 #1 0x00007f1c6a2cc3e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007f1c6a2cdfcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007f1c540c7839 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007f1c7930b9e9 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x00007f1c7510b734 in start_thread () from /lib64/libpthread.so.0 #6 0x00007f1c78a08d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f1c7d63e9c0 (LWP 20881)): [KCrash Handler] #6 0x00007f1c79a65279 in QImageData::create(QSize const&, QImage::Format) () from /usr/lib64/libQt5Gui.so.5 #7 0x00007f1c79a652cb in QImage::QImage(int, int, QImage::Format) () from /usr/lib64/libQt5Gui.so.5 #8 0x00007f1c79a655f3 in QImage::copy(QRect const&) const () from /usr/lib64/libQt5Gui.so.5 #9 0x00007f1c79a65a58 in QImage::QImage(QImage const&) () from /usr/lib64/libQt5Gui.so.5 #10 0x00007f1c73c19f19 in Marble::LabelGraphicsItem::image() const () from /usr/lib64/libmarblewidget-qt5.so.25 #11 0x00007f1b6c891465 in Marble::ElevationProfileMarker::isInitialized (this=<optimized out>) at /usr/src/debug/marble-16.12.0/src/plugins/render/elevationprofilemarker/ElevationProfileMarker.cpp:129 #12 0x00007f1c73ccdf0c in ?? () from /usr/lib64/libmarblewidget-qt5.so.25 #13 0x00007f1c73ccd69e in Marble::MarbleWidgetInputHandler::MarbleWidgetInputHandler(Marble::MarbleAbstractPresenter*, Marble::MarbleWidget*) () from /usr/lib64/libmarblewidget-qt5.so.25 #14 0x00007f1c73c629c1 in ?? () from /usr/lib64/libmarblewidget-qt5.so.25 #15 0x00007f1c73c6285b in ?? () from /usr/lib64/libmarblewidget-qt5.so.25 #16 0x00007f1c73c61ef8 in Marble::MarbleWidget::MarbleWidget(QWidget*) () from /usr/lib64/libmarblewidget-qt5.so.25 #17 0x00007f1c7c293037 in GeoIface::BackendMarble::mapWidget (this=0x2891250) at /usr/src/debug/digikam-5.3.0/core/utilities/geolocation/geoiface/backends/backendmarble.cpp:235 #18 0x00007f1c7c2b7363 in GeoIface::MapWidget::setActive (this=0x28896a0, state=<optimized out>) at /usr/src/debug/digikam-5.3.0/core/utilities/geolocation/geoiface/mapwidget.cpp:2060 #19 0x00007f1c7c0c3ffc in Digikam::ImagePropertiesGPSTab::setActive (this=0x2888630, state=<optimized out>) at /usr/src/debug/digikam-5.3.0/core/libs/imageproperties/imagepropertiesgpstab.cpp:440 #20 0x00007f1c7ccc1784 in Digikam::ImagePropertiesSideBarDB::slotChangedTab (this=0x271c2c0, tab=0x2888630) at /usr/src/debug/digikam-5.3.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:388 #21 0x00007f1c7c0c7e00 in Digikam::ImagePropertiesSideBar::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/digikam-5.3.0/build/core/libs/imageproperties/moc_imagepropertiessidebar.cpp:97 #22 0x00007f1c794f7bb1 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #23 0x00007f1c7c08c42f in Digikam::Sidebar::signalChangedTab (this=<optimized out>, _t1=0x2888630) at /usr/src/debug/digikam-5.3.0/build/core/libs/widgets/moc_sidebar.cpp:536 #24 0x00007f1c7c09201b in Digikam::Sidebar::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/digikam-5.3.0/build/core/libs/widgets/moc_sidebar.cpp:458 #25 0x00007f1c794f7bb1 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #26 0x00007f1c7c08c3ee in Digikam::DMultiTabBarButton::clicked (this=<optimized out>, _t1=3) at /usr/src/debug/digikam-5.3.0/build/core/libs/widgets/moc_sidebar.cpp:208 #27 0x00007f1c794f7bb1 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #28 0x00007f1c7a2cb702 in QAbstractButton::clicked(bool) () from /usr/lib64/libQt5Widgets.so.5 #29 0x00007f1c7a2cb8fa in ?? () from /usr/lib64/libQt5Widgets.so.5 #30 0x00007f1c7a2cc928 in ?? () from /usr/lib64/libQt5Widgets.so.5 #31 0x00007f1c7a2ccaa4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #32 0x00007f1c7a216c9a in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #33 0x00007f1c7a1d4e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #34 0x00007f1c7a1d9d14 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #35 0x00007f1c794cdfc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #36 0x00007f1c7a1d8a10 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/libQt5Widgets.so.5 #37 0x00007f1c7a22f911 in ?? () from /usr/lib64/libQt5Widgets.so.5 #38 0x00007f1c7a231eb3 in ?? () from /usr/lib64/libQt5Widgets.so.5 #39 0x00007f1c7a1d4e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #40 0x00007f1c7a1d949a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #41 0x00007f1c794cdfc5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #42 0x00007f1c79a2168b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #43 0x00007f1c79a22e05 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #44 0x00007f1c79a04eeb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5 #45 0x00007f1c540f4bc0 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #46 0x00007f1c6fd65134 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #47 0x00007f1c6fd65388 in ?? () from /usr/lib64/libglib-2.0.so.0 #48 0x00007f1c6fd6542c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #49 0x00007f1c7951e30c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #50 0x00007f1c794cbfdb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #51 0x00007f1c794d3ec6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #52 0x0000000000408946 in main (argc=1, argv=<optimized out>) at /usr/src/debug/digikam-5.3.0/core/app/main/main.cpp:237 ******************************************************************************* gilles caulier says : It crash in Marble shared lib from your system. Use digiKam AppImage instead. It do not crash. Marble used in bundle is clean... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 Episteme PROMENEUR <epistemepromeneur@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|KDE:Extra: Bug digikam |KDE:Extra: Bug digikam |crash when selcting map |crash when selecting map |tool |tool -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c1 --- Comment #1 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- i assume something in marble (in kde applications) is not at the same level of digikam 5.3.0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c2 --- Comment #2 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- Created attachment 709734 --> http://bugzilla.opensuse.org/attachment.cgi?id=709734&action=edit libmarblewidget dependency Digikam 5.4.0 Marble 16.12.0 same problem is it normal that - libdigikamcore5-5.4.0 - showphoto 5.4.0 use libmarblewidget-qt5.25-16.08.2 instead of libmarblewidget-qt5.26-16.12.0 ? see the attachement -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c3 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #3 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Episteme PROMENEUR from comment #2)
is it normal that - libdigikamcore5-5.4.0 - showphoto 5.4.0
use libmarblewidget-qt5.25-16.08.2 instead of libmarblewidget-qt5.26-16.12.0 ?
There is no libmarblewidget-qt5-26-16.12.0 in Leap 42.2. Install libmarblewidget-qt5-25-16.08.2 from the standard repo and see if it still crashes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c4 --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- PS, better remove KDE:Applications completely and switch all marble packages back to the standard versions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c5 --- Comment #5 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- if i want to use digikam 5.4.0 this is because i take also little videos then i need to manage videos with digikam. there is many fixes about video management for example we can again export video to Google photo. also now again we get dolphin file selector to import photo or folder instead of the horrible qt file selector. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c6 --- Comment #6 from Episteme PROMENEUR <epistemepromeneur@free.fr> ---
There is no libmarblewidget-qt5-26-16.12.0 in Leap 42.2. Install libmarblewidget-qt5-25-16.08.2 from the standard repo and see if it >> still crashes.
libmarblewidget-qt5-25-16.08.2 is installed also libmarblewidget-qt5-26-16.12.0 is installed because kde marble 16.12.0 is installed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c7 --- Comment #7 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Episteme PROMENEUR from comment #5)
if i want to use digikam 5.4.0 this is because i take also little videos then i need to manage videos with digikam.
And? I told you to try to revert marble, not digikam. (In reply to Episteme PROMENEUR from comment #6)
also libmarblewidget-qt5-26-16.12.0 is installed because kde marble 16.12.0 is installed.
Again, to be clear, install marble-15.08.2 (and other related packages like marble-data and marble-kde) from the standard repo and see if it fixes your crash. Actually I would recommend you to remove KDE:Applications completely and forget about it. You won't miss much anyway, as many applications cannot even be built for 42.2 any more in 16.12 because they require newer KDE Frameworks. KDE:Extra is being built for standard 42.2 (not KDE:Applications), there may be incompatibilities. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c8 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Component|3rd party software |KDE Applications Version|unspecified |Leap 42.2 Product|openSUSE.org |openSUSE Distribution Summary|KDE:Extra: Bug digikam |Digikam crash with marble |crash when selecting map |16.12.0 from |tool |KDE:Applications when | |selecting map tool QA Contact|opensuse-communityscreening |qa-bugs@suse.de |@forge.provo.novell.com | --- Comment #8 from Wolfgang Bauer <wbauer@tmo.at> --- For the record, I can reproduce the crash with both digikam 5.4.0 and 5.2.0 after adding KDE:Applications and switching to it (though marble 16.12.0 itself works fine). Without KDE:Applications it works fine (both 5.2.0 from the standard repos and 5.4.0 from KDE:Extra). And just downgrading marble to 16.08.2 fixes the crash too. So apparently it is indeed an incompatibility between marble 16.12.0 and libmarblewidget-qt5-25 16.08.2. Maybe we should just remove marble from KDE:Applications, for 42.2 at least... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kde-maintainers@suse.de |opensuse-kde-bugs@opensuse. | |org -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c9 Episteme PROMENEUR <epistemepromeneur@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |NEW Component|KDE Applications |3rd party software Version|Leap 42.2 |unspecified Assignee|opensuse-kde-bugs@opensuse. |kde-maintainers@suse.de |org | Product|openSUSE Distribution |openSUSE.org Summary|Digikam crash with marble |KDE:Extra: Bug digikam |16.12.0 from |crash when selecting map |KDE:Applications when |tool |selecting map tool | QA Contact|qa-bugs@suse.de |opensuse-communityscreening | |@forge.provo.novell.com --- Comment #9 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- History of problem 1 I do a clean install of 42.2 then I launch digikam 5.2.0 then I see that there is no map tool in digikam when I select it then I see that only libmarblewidget-qt5-25 16.0.8.2 is installed then I install kde marble 16.08.2 then in digikam now when I select the map tool then digikam disappears. then I installed digikam 5.3.0 from KDE Extra then digikam disappears when selecting map tool then I installed kde marble from KDE Applications thus it's from the very beginning that digikam has no map tool activated then crashes when selecting map tool. reverting to original digikam and marble leads to the same problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c10 --- Comment #10 from Episteme PROMENEUR <epistemepromeneur@free.fr> ---
And just downgrading marble to 16.08.2 fixes the crash too.
i am goig to test -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c11 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Component|3rd party software |KDE Applications Version|unspecified |Leap 42.2 Assignee|kde-maintainers@suse.de |opensuse-kde-bugs@opensuse. | |org Product|openSUSE.org |openSUSE Distribution Summary|KDE:Extra: Bug digikam |Digikam crash with marble |crash when selecting map |16.12.0 from |tool |KDE:Applications when | |selecting map tool QA Contact|opensuse-communityscreening |qa-bugs@suse.de |@forge.provo.novell.com | --- Comment #11 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Episteme PROMENEUR from comment #9)
reverting to original digikam and marble leads to the same problem.
Sorry, both digikam versions work fine here with marble 16.08.2 on a standard 42.2 installation. Btw, why did you revert all changes to this bug report that I made? It's now assigned to the wrong mail address again, which nobody reads any more... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c12 --- Comment #12 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- i did nor revert your change. when i send my comment then a mid air collision occurs. i answered i want ot publish my comment then bugs kde open a window i don't understood i understood only if i don't click on "commit" then my comment is canceled. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c13 --- Comment #13 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- i confirm that with digikam 5.4.0 when reverting to marble 16.08 then no more crash when selecting map tool. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c14 --- Comment #14 from Episteme PROMENEUR <epistemepromeneur@free.fr> ---
Btw, why did you revert all changes to this bug report that I made? It's now assigned to the wrong mail address again, which nobody reads any more...
did you fixed it? thanks for your help. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c15 --- Comment #15 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Episteme PROMENEUR from comment #12)
i did nor revert your change.
You did, see the bug report's history. Though probably not on purpose...
when i send my comment then a mid air collision occurs. i answered i want ot publish my comment then bugs kde open a window i don't understood
i understood only if i don't click on "commit" then my comment is canceled.
A "mid-air" collision happens if there are changes to the bug report while you already had it open in your browser. You should get two options though, to either submit all your changes or only your new comment. (In reply to Episteme PROMENEUR from comment #14)
did you fixed it?
Yes. (In reply to Episteme PROMENEUR from comment #13)
i confirm that with digikam 5.4.0 when reverting to marble 16.08 then no more crash when selecting map tool.
Thanks for confirming. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c16 Episteme PROMENEUR <epistemepromeneur@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|Leap 42.2 |Leap 42.3 --- Comment #16 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- problem still there with 42.3 --- Comment #17 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- problem still there with 42.3 and digikam 5.8.0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c18 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse-kde-bugs@opensuse. | |org Flags| |needinfo?(opensuse-kde-bugs | |@opensuse.org) --- Comment #18 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Episteme PROMENEUR from comment #17)
problem still there with 42.3 and digikam 5.8.0
Likely because KDE:Extra still doesn't build against KDE:Applications, only against the standard distribution. Maybe we should add a KDE:Applications target to KDE:Extra as I proposed on the opensuse-kde mailinglist back then. What do the other team members think? Other than that, this is an upstream problem (in marble) I think. It should rather not crash if the versions don't match exactly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c19 --- Comment #19 from Wolfgang Bauer <wbauer@tmo.at> --- PS: (In reply to Wolfgang Bauer from comment #18)
Maybe we should add a KDE:Applications target to KDE:Extra as I proposed on the opensuse-kde mailinglist back then.
This would also help with other applications. Like skrooge and calibre requiring the exact Qt version as built against, or others like kdeconnect-kde that can only be built with newer Qt versions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1017342 http://bugzilla.opensuse.org/show_bug.cgi?id=1017342#c20 Episteme PROMENEUR <epistemepromeneur@free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #20 from Episteme PROMENEUR <epistemepromeneur@free.fr> --- too old -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com