Bug 155444 - dolphin crashes while dragging/dropping files
Summary: dolphin crashes while dragging/dropping files
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
: 156778 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-11 10:12 UTC by Martin Fabian Hohenberg
Modified: 2008-06-30 00:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Crash from Dolphin when drag-n-drop into a folder (6.65 KB, text/plain)
2008-06-30 00:29 UTC, Neil S
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Fabian Hohenberg 2008-01-11 10:12:05 UTC
Version:           1.0 (using KDE 4.00.00 (KDE 4.0.0), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.22-14-generic

This is reproduceable behaviour:

I try to drag'n drop a file/folder into another folder. dolphin crashes in every single case. This should not happen, as drag'n drop is one of the main features of a file manager ;)

Backtrace: 

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".

[Thread debugging using libthread_db enabled]
[New Thread -1238088000 (LWP 8791)]
[New Thread -1262404720 (LWP 8792)]

0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 8791)]

Thread 2 (Thread -1262404720 (LWP 8792)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6b842a1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7efaf82 in ?? () from /usr/lib/libQtCore.so.4
#3  0x0000000d in ?? ()
#4  0xb4c132d0 in ?? ()
#5  0x00000000 in ?? ()

Thread 1 (Thread -1238088000 (LWP 8791)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb6b4a6db in waitpid () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7b48c2b in ?? () from /usr/lib/kde4/lib/libkdeui.so.5
#3  0x000022b4 in ?? ()
#4  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()
Comment 1 Peter Penz 2008-01-11 10:28:05 UTC
Sorry, but I cannot reproduce this crash with Dolphin for KDE 4.0.0. Did you compile the packages yourself or do you refer to official Kubuntu packages?
Comment 2 Martin Fabian Hohenberg 2008-01-11 12:09:34 UTC
those are the official kubuntu packages, last upgraded about 30 minutes ago.
Comment 3 Peter Penz 2008-01-12 11:43:38 UTC
I just installed the official Suse packages for KDE 4.0.0 (-> cannot reproduce) and also cannot produce it with the build sources for KDE 4.0.0. If there is a problem within Dolphin generally and no local problem for Kubuntu or your installation, then we'll get flamed anyway during the next days :-) So in the meantime I'll leave this issue to unconfirmed.
Comment 4 FiNeX 2008-01-13 12:54:23 UTC
Just tried on revision 760683. It doesn't crash.
Comment 5 Peter Penz 2008-01-13 13:26:48 UTC
Thanks FiNeX for checking. As we get so many Kubuntu related bug reports currently which cannot be confirmed with other distributions, I'll set this issue to WORKSFORME, otherwise we'll lose the overview... :-/
Comment 6 Peter Penz 2008-01-27 15:29:23 UTC
*** Bug 156778 has been marked as a duplicate of this bug. ***
Comment 7 Todd 2008-03-28 19:02:16 UTC
I have the same problem for OpenSuse 10.3 packages on one of my computers.
Comment 8 Todd 2008-03-28 21:56:21 UTC
(this copied from bug 155574)

I have been able to isolate the problem, at least to me, to the config file:

.kde4/share/config/kdeglobals

The setting that causes the problem is:

EffectAnimateMenu=true

If that line is absent, or set to "false", then the right-click does not open files.  If the line is present and set to "true", then right-clicking does open the file.  An additional setting in the same file:

EffectsEnabled=true

If this line is absent, or set to "false", then the problem also does not occur.  I am pretty sure turning off this setting also, by extension, turns off the EffectAnimateMenu setting.

Further, I have bug Bug 155574Right-clicking on a file launches it.  Removing this setting fixes this bug as well.

So I think everyone who has the problem should try changing that one setting in their config file to see if it fixes the problem or if I am just a fluke.  Either way I hope this helps solve the problem.
Comment 9 Todd 2008-03-28 22:12:21 UTC
(this copied from bug 155574) 

I have tried loading System Settings, going to Appearance -> Style -> Effects Tab.  There, setting the "Menu Effect" dropdown to either "Animate" or "Fade" triggers the problem.  Setting it to "Disable" fixes the problem.  I cannot use "make translucent" because it says oxygen does not support it, so I could not test that.  So try changing the settings first before messing with the config file. 
Comment 10 Peter Penz 2008-03-29 07:09:26 UTC
(this copied from bug 155574) 

Thanks Todd for the hint! I just tried to enable those settings (KDE 4.0.x (SUSE) and on trunk), but still cannot reproduce this issue. Is this problem fixed for other subscribers of this bug? 
Comment 11 Neil S 2008-06-30 00:29:30 UTC
Created attachment 25715 [details]
Crash from Dolphin when drag-n-drop into a folder
Comment 12 Neil S 2008-06-30 00:30:44 UTC
I get this too, running 4.0.83 from Fedora Rawhide, x86_64.
Happens on a local ext3 filesystem as well as mounted smb filesystems.

As suggested, it only happens when EffectAnimateMenu is set to true, if I set to false then it's fine. 

With it set to true when you drop the file into the folder the menu animates into existence, the mouse pointer gets the 'no entry' icon - circle with a line through it, and the menu items do not highlight as you roll over them.
If at this point you move the pointer off the menu and onto the dolphin window behind it and click, it crashes.
If you click on the menu the mouse pointer goes back to normal - i.e. loses the 'no entry' icon - then the menu items highlight as you roll over them. Click anywhere (menu item or dolphin window) and it crashes.

100% reproducible, stacktrace attached (above).

Is 157630 a duplicate of this bug?
Comment 13 Peter Penz 2008-06-30 00:42:45 UTC
@Neil: This seems to be a Qt-issue and I've reported a bug-report already (http://trolltech.com/developer/task-tracker/index_html?id=206637&method=entry). I did a workaround for KDE 4.1, so I'm wondering that it still appears in 4.0.83...