By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 3157

Summary:	Konqueror crashes when cut-pasting in tree view mode
Product:	TDE	Reporter:	Arne <mail>
Component:	tdebase	Assignee:	Michele Calgaro <michele.calgaro>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bugwatch, mail, michele.calgaro, slavek.banko
Priority:	P5
Version:	R14.0.x [Trinity]
Hardware:	i386
OS:	Debian Buster
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	3161
Attachments:	Konqueror Cut&Paste Crash Report

Description Arne 2020-08-16 13:03:31 CDT

To reproduce:

* Open konqueror (as file browser).
* Switch to tree-view mode (if not your default).
* Select and cut one or multiple files (Ctrl+X).
* Change to a different directory or select a different tab (optional)
* Paste (Ctrl+V)
* Konqueror crashes immediately and leaves a stale "Progress Dialog" window behind (can be closed normally).

Notes:
* The crash also happens when pasting immediately after cutting (into the same tab and directory)
* The crash also occurs when using the mouse (right-click) to cut and paste.
* The crash only occurs if the tab where the file is cut is in tree-view mode. If the files are pasted into a different tab, its view mode doesn't matter.
* The crash does not occur if a new tab is opened between cutting and pasting (doesn't matter if the file is pasted in the new tab or an existing one).
* The crash does not occur when pasting into a different konqueror window.

Comment 1 Michele Calgaro 2020-08-19 09:08:43 CDT

Wow, fantastic bug report, very detailed. Bug reproducible here too.

Comment 2 Michele Calgaro 2021-03-29 10:03:10 CDT

Hi Arne,
this is probably a duplicate of bug 3008 which has now been fixed.
I can no longer reproduce this bug.
If you are on PSB version for Debian, could you try and let us know if the crash does not happen anymore on your side too? 
Instead if you are on a stable R14.O.x release, are you able to provide a crash dump of the crash? By looking into that it should be very clear whether it is a duplicate of bug 3008.

Comment 3 Arne 2021-04-01 15:28:20 CDT

Created attachment 3011 [details]
Konqueror Cut&Paste Crash Report

Comment 4 Arne 2021-04-01 15:29:23 CDT

Hi Michele,

I'm on stable, so I've attached the crash report. Hope this helps.

Comment 5 Michele Calgaro 2021-04-01 22:05:32 CDT

Thanks Arne, very useful.
The crash report looks exactly like the one in bug 3008 :-)

I am inclined to close this bug, but first as a double check, can I ask you to test the following:

1) right click Kicker in the systray and choose "Configure Kicker..."
2) in the dialog that opens, under "General" tab please deselect "Prevent empty clipboard" so that it is unchecked.

Apply the changes and try to reproduce the crash. You should not see any more crashes when you cut and paste.

If the test is successful, I will close the bug because it means it would be the same described in bug 3008.

Comment 6 Arne 2021-04-05 16:25:03 CDT

(In reply to Michele Calgaro from comment #5)
> 1) right click Kicker in the systray and choose "Configure Kicker..."
> 2) in the dialog that opens, under "General" tab please deselect "Prevent
> empty clipboard" so that it is unchecked.

Did you mean Klipper?

> Apply the changes and try to reproduce the crash. You should not see any
> more crashes when you cut and paste.

I can confirm that the bug no longer occurs with the option off. Enabled it again to double-check and Konqueror crashed on the first attempt, so changing the option appears to have immediate effect.

Comment 7 Michele Calgaro 2021-04-05 19:41:57 CDT

> Did you mean Klipper?
Yes, typo eh eh

> I can confirm that the bug no longer occurs with the option off. Enabled it 
> again to double-check and Konqueror crashed on the first attempt, so changing 
> the option appears to have immediate effect.

Great, that really confirms it was the same bug.

I am going to close this off. Should you experience it again on R14.0.10, please reopen it but most likely it would be something different in such case :-)

*** This bug has been marked as a duplicate of bug 3008 ***