Bug 263361 - Copy to Samba share, crash
Summary: Copy to Samba share, crash
Status: RESOLVED WORKSFORME
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.4
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords: triaged
: 275876 282300 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-16 21:41 UTC by Jeffrey
Modified: 2018-10-27 02:51 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey 2011-01-16 21:41:36 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.32-5-686 i686
Distribution: Debian GNU/Linux 6.0 (squeeze)

-- Information about the crash:
Tried to copy a local folder to a remote Samba share (mounted in fstab) and Dolphin crashed.  Happy that I selected 'Copy' and not 'Move' as I had a feeling something wouldn't work out.

Note, Amarok was scanning the Samba share at this time.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QMetaObjectPrivate::disconnectHelper (sender=0x95d33f0, signal_index=-1, receiver=0x8f38400, method_index=-1, disconnectType=QMetaObjectPrivate::DisconnectAll) at kernel/qobject.cpp:2990
#7  QMetaObjectPrivate::disconnect (sender=0x95d33f0, signal_index=-1, receiver=0x8f38400, method_index=-1, disconnectType=QMetaObjectPrivate::DisconnectAll) at kernel/qobject.cpp:3050
#8  0xb69d8781 in QObject::disconnect (sender=0x95d33f0, signal=0x0, receiver=0x8f38400, method=0x0) at kernel/qobject.cpp:2762
#9  0xb72228f9 in QObject::disconnect (this=0x9473368) at /usr/include/qt4/QtCore/qobject.h:229
#10 KIO::SimpleJobPrivate::slaveDone (this=0x9473368) at ../../kio/kio/job.cpp:485
#11 0xb7229b3b in KIO::SimpleJob::slotFinished (this=0x95d33f0) at ../../kio/kio/job.cpp:494
#12 0xb7227843 in KIO::SimpleJob::qt_metacall (this=0x95d33f0, _c=QMetaObject::InvokeMetaMethod, _id=32, _a=0xbfa8e33c) at ./jobclasses.moc:171
#13 0xb722793a in KIO::DirectCopyJob::qt_metacall (this=0x95d33f0, _c=QMetaObject::InvokeMetaMethod, _id=32, _a=0xbfa8e33c) at ./job_p.moc:157
#14 0xb69c67aa in QMetaObject::metacall (object=0x95d33f0, cl=158061352, idx=32, argv=0xbfa8e33c) at kernel/qmetaobject.cpp:237
#15 0xb69d51bb in QMetaObject::activate (sender=0x8f38400, m=0xb73d8f44, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3295
#16 0xb72f54a7 in KIO::SlaveInterface::finished (this=0x8f38400) at ./slaveinterface.moc:171
#17 0xb72f87cd in KIO::SlaveInterface::dispatch (this=0x8f38400, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#18 0xb72f5963 in KIO::SlaveInterface::dispatch (this=0x8f38400) at ../../kio/kio/slaveinterface.cpp:91
#19 0xb72e8e38 in KIO::Slave::gotInput (this=0x8f38400) at ../../kio/kio/slave.cpp:324
#20 0xb72e9043 in KIO::Slave::qt_metacall (this=0x8f38400, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfa8e64c) at ./slave.moc:82
#21 0xb69c67aa in QMetaObject::metacall (object=0x8f38400, cl=158061352, idx=30, argv=0xbfa8e64c) at kernel/qmetaobject.cpp:237
#22 0xb69d51bb in QMetaObject::activate (sender=0x9489878, m=0xb73d5820, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#23 0xb71f1cb7 in KIO::Connection::readyRead (this=0x9489878) at ./connection.moc:92
#24 0xb71f405e in KIO::ConnectionPrivate::dequeue (this=0x950cad8) at ../../kio/kio/connection.cpp:82
#25 0xb71f418e in KIO::Connection::qt_metacall (this=0x9489878, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x95c09c0) at ./connection.moc:79
#26 0xb69c67aa in QMetaObject::metacall (object=0x9489878, cl=158061352, idx=5, argv=0x95c09c0) at kernel/qmetaobject.cpp:237
#27 0xb69d0d36 in QMetaCallEvent::placeMetaCall (this=0x954a088, object=0x9489878) at kernel/qobject.cpp:561
#28 0xb69d1dfe in QObject::event (this=0x9489878, e=0x954a088) at kernel/qobject.cpp:1248
#29 0xb5f0a5cc in QApplicationPrivate::notify_helper (this=0x8e609d8, receiver=0x9489878, e=0x954a088) at kernel/qapplication.cpp:4302
#30 0xb5f1115e in QApplication::notify (this=0xbfa8efa4, receiver=0x9489878, e=0x954a088) at kernel/qapplication.cpp:3706
#31 0xb6f89bfa in KApplication::notify (this=0xbfa8efa4, receiver=0x9489878, event=0x954a088) at ../../kdeui/kernel/kapplication.cpp:302
#32 0xb69c14cb in QCoreApplication::notifyInternal (this=0xbfa8efa4, receiver=0x9489878, event=0x954a088) at kernel/qcoreapplication.cpp:726
#33 0xb69c4f2c in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8e42858) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e42858) at kernel/qcoreapplication.cpp:1367
#35 0xb69c50ad in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1260
#36 0xb69ed57f in QCoreApplication::sendPostedEvents (s=0x8e62b10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#37 postEventSourceDispatch (s=0x8e62b10) at kernel/qeventdispatcher_glib.cpp:276
#38 0xb54ce305 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#39 0xb54d1fe8 in ?? () from /lib/libglib-2.0.so.0
#40 0xb54d21c8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#41 0xb69ed075 in QEventDispatcherGlib::processEvents (this=0x8e42330, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#42 0xb5fc8ed5 in QGuiEventDispatcherGlib::processEvents (this=0x8e42330, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#43 0xb69bfae9 in QEventLoop::processEvents (this=0xbfa8ef04, flags=) at kernel/qeventloop.cpp:149
#44 0xb69bff3a in QEventLoop::exec (this=0xbfa8ef04, flags=...) at kernel/qeventloop.cpp:201
#45 0xb69c516f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#46 0xb5f0a667 in QApplication::exec () at kernel/qapplication.cpp:3581
#47 0x0807bc3f in _start ()

Possible duplicates by query: bug 238931.

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-23 16:14:55 UTC
[Comment from a bug triager]
The backtrace looks a bit related to bug 196988.
- If the Samba share is mounted via fstab, then the SMB kioslave doesn't need to be used. Were you using the /mnt/share location or a smb://IP/share location ?
Regards
Comment 2 Jeffrey 2011-01-23 18:13:44 UTC
> Were you using the /mnt/share location or a smb://IP/share location
I was using the /mnt/samba/Music mountpoint (the fstab entry), not the KIO
slave.
Comment 3 Dario Andres 2011-01-23 18:15:39 UTC
Thanks
Comment 4 Beat Wolf 2011-06-20 15:35:32 UTC
*** Bug 275876 has been marked as a duplicate of this bug. ***
Comment 5 Joris Guisson 2011-09-18 18:21:01 UTC
*** Bug 282300 has been marked as a duplicate of this bug. ***
Comment 6 Dawit Alemayehu 2013-12-22 05:34:44 UTC
Is this still an issue with a more recent version of KDE, v4.11 or higher?
Comment 7 Jeffrey 2014-01-09 22:06:29 UTC
> Is this still an issue with a more recent version of KDE, v4.11 or higher?

I cannot test this, my setup has significantly changed.  Others who have duplicates of this bug may have additional information for you.

Thanks for looking into this bug.
Comment 8 Andrew Crouthamel 2018-09-25 03:50:55 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 9 Andrew Crouthamel 2018-10-27 02:51:45 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!