Bug 313186 - Crashes on attempt to use the "Send to" menu
Summary: Crashes on attempt to use the "Send to" menu
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-13 14:54 UTC by Alex Lowe
Modified: 2018-02-04 11:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Lowe 2013-01-13 14:54:15 UTC
Application: ksnapshot (0.8.2)
KDE Platform Version: 4.9.97
Qt Version: 4.8.3
Operating System: Linux 3.5.0-21-generic x86_64
Distribution: Ubuntu 12.10

-- Information about the crash:
- What I was doing when the application crashed:

Every time I try to use the "send to" menu in ksnapshot, it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KSnapshot (ksnapshot), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8aaac0f780 (LWP 19803))]

Thread 2 (Thread 0x7f8a98cb1700 (LWP 19804)):
#0  0x00007f8aa744f303 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f8aa46a3d84 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f8aa46a3ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f8aa7ecbc16 in QEventDispatcherGlib::processEvents (this=0x7f8a940008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f8aa7e9c2bf in QEventLoop::processEvents (this=this@entry=0x7f8a98cb0dd0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f8aa7e9c548 in QEventLoop::exec (this=0x7f8a98cb0dd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f8aa7d9db10 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f8aa7e7c9af in QInotifyFileSystemWatcherEngine::run (this=0xfa5cd0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f8aa7da0aec in QThreadPrivate::start (arg=0xfa5cd0) at thread/qthread_unix.cpp:338
#9  0x00007f8aa4b72e9a in start_thread (arg=0x7f8a98cb1700) at pthread_create.c:308
#10 0x00007f8aa745acbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8aaac0f780 (LWP 19803)):
[KCrash Handler]
#6  QString::operator= (this=0x72006500730097, other=...) at tools/qstring.cpp:1411
#7  0x00007f8a93df1d89 in KIPI::Plugin::setUiBaseName (this=0xfbe240, name=<optimized out>) at ../../libkipi/plugin.cpp:309
#8  0x00007f8a982a5baf in KIPIIpodExportPlugin::Plugin_iPodExport::Plugin_iPodExport (this=0xfbe240, parent=0xee56a0) at /build/buildd/digikam-3.0.0~beta3/extra/kipi-plugins/ipodexport/plugin_ipodexport.cpp:66
#9  0x00007f8a982a60a7 in KPluginFactory::createInstance<KIPIIpodExportPlugin::Plugin_iPodExport, QObject> (parentWidget=<optimized out>, parent=<optimized out>, args=...) at /usr/include/kpluginfactory.h:477
#10 0x00007f8aa86747c5 in KPluginFactory::create (this=0x1060360, iface=0x7f8aa9c3b0c0 "KIPI::Plugin", parentWidget=0x0, parent=0xee56a0, args=..., keyword=...) at ../../kdecore/util/kpluginfactory.cpp:203
#11 0x00007f8aa9c2f586 in KIPI::PluginLoader::Info::plugin() const () from /usr/lib/libkipi.so.9
#12 0x0000000000417758 in _start ()

This bug may be a duplicate of or related to bug 307114.

Possible duplicates by query: bug 307114.

Reported using DrKonqi
Comment 1 caulier.gilles 2013-01-13 18:30:12 UTC
*** Bug 303338 has been marked as a duplicate of this bug. ***
Comment 2 first.polack 2013-02-20 14:52:41 UTC
Same problem occurs on PCLinuxOS, both 32bit and 64bit versions. Removal of kipi plugins and kipi-plugins-libs allows return of proper functioning of the Send To... feature of ksnapshot.
Comment 3 caulier.gilles 2013-02-20 22:28:44 UTC

*** This bug has been marked as a duplicate of bug 306693 ***
Comment 4 caulier.gilles 2018-02-04 11:07:38 UTC
Problem fixed in 6.0.0 where all tools are now in digiKam core