Bug 61621 - copy file to second instance of konqueror
Summary: copy file to second instance of konqueror
Status: RESOLVED DUPLICATE of bug 47418
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-24 14:42 UTC by JohnML
Modified: 2003-07-28 00:48 UTC (History)
0 users

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 JohnML 2003-07-24 14:42:39 UTC
Version:            (using KDE KDE 3.1.2)
Installed from:    SuSE RPMs
Compiler:          gcc version 2.95.3 20010315 (SuSE) 
OS:          Linux

Hi,

you have bug reports to this problem, signed closed, but the bug is still there. See 47418.

My configuration
Qt: 3.1.2
KDE: 3.1.2
Konqueror: 3.1.2
SuSE 8.0 Pro
rpm's from kde.org (kde 3.1.2)

Bug description:
assume you copied a file in konqueror, opened a second instance of
konqueror and tried to paste the file to another directory. The
menu-entry "paste" will be disabled.

It doesn't matter if you have the two instances of konqueror side by side, have the source konqueror closed ...
Klipper has your copied filed but doesn't know how to handle it. Klipper wants a file name for its content and pastes it as plain text.

on www.kde-forum.org this problem is known.


thanks for konqueror, kde ... and keep on coding

 JohnML
Comment 1 JohnML 2003-07-24 14:47:04 UTC
p.s. JohnML 
This bug also exists on my Knoppix 3.2 HD-Install 
Comment 2 Maksim Orlovich 2003-07-24 15:02:28 UTC
It's fixed in 3.1.3, and recent CVS, AFAIK. How old is your 3.2 build? 
 
Comment 3 JohnML 2003-07-24 16:05:27 UTC
>It's fixed in 3.1.3, and recent CVS, AFAIK. How old is your 3.2 build?

Rpm's KDE 3.1.2 Date 22.05.2003 14:__
I'm not shure but i think i got them from kde.org

I'll try to get 3.1.3 as soon as possible. 
That was my first bug report and i have to look the fix-date for the future first.

JohnML
Comment 4 John Firebaugh 2003-07-28 00:48:13 UTC

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