Bug 495943

Summary: Drag and Drop of contacts in Kontact doesn't work
Product: [Applications] kontact Reporter: todd.lasman
Component: contactsAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: 6.3.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description todd.lasman 2024-11-07 21:28:32 UTC 
SUMMARY
Dragging a contact from KAddressBook onto the Tasks icon should create a task with that contact. Similarly, dragging it onto the Calendar should create an event with this contact. This does not happen. The cursor changes to something that looks like it will accept the drop target, but no event or task gets created.

Dragging an email onto these icons works fine, however.

STEPS TO REPRODUCE
1.  Select a contact from KAddressBook and drag onto the Calendar or Task icon on the sidebar.
2.  The cursor changes to show that this is a valid drop.

OBSERVED RESULT
No event or task is created

EXPECTED RESULT
Per the handbook, an event or a task with that contact should be created.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
6.2.3
KDE Frameworks Version: 
6.7.0
Qt Version: 
6.8.0

ADDITIONAL INFORMATION
Comment 1 todd.lasman 2025-02-16 19:46:46 UTC 
As an addendum, right-clicking a contact to bring up its context menu shows Copy Contact To... and Move Contact To...
Just hovering the mouse over either of these two options causes the context menu to close, without being able to choose a copy/move target.
Comment 2 Colin J Thomson 2025-02-16 19:53:06 UTC 
(In reply to todd.lasman from comment #1)
> As an addendum, right-clicking a contact to bring up its context menu shows
> Copy Contact To... and Move Contact To...
> Just hovering the mouse over either of these two options causes the context
> menu to close, without being able to choose a copy/move target.

This looks very much related to bug 485661
Comment 3 todd.lasman 2025-02-16 20:02:45 UTC 
Should have searched this first. You’re right.
Comment 4 Colin J Thomson 2025-02-16 23:00:24 UTC 
(In reply to todd.lasman from comment #3)
> Should have searched this first. You’re right.

I'll mark this as a dupe, it can always be changed back.

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