Bug 32993

Summary: Can't delete a picture
Product: LibreOffice Reporter: Jiehong <ma.jiehong>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: VERIFIED FIXED    
Severity: normal    
Priority: medium    
Version: 3.3.0 RC2   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Jiehong 2011-01-11 05:17:41 UTC
When I insert a picture in writer I can't cut it nor delete it by using the del key of my keyboard.

However it works well in all the other modules (like impress, calc…)
Comment 1 Alex Thurgood 2011-01-11 06:32:23 UTC
Can not confirm on Mac OSX 10.6.5 with LibO RC2. This works fine for me. Note however, that on a Macbook the Del key is actually a Backspace key (there is no dedicated Del key on Macbooks).

Have you tried selecting the image and using Backspace ?


Alex
Comment 2 Jiehong 2011-01-11 06:56:13 UTC
(In reply to comment #1)
> Can not confirm on Mac OSX 10.6.5 with LibO RC2. This works fine for me. Note
> however, that on a Macbook the Del key is actually a Backspace key (there is no
> dedicated Del key on Macbooks).
> 
> Have you tried selecting the image and using Backspace ?
> 
> 
> Alex

I've tried with the backspace key and that is working fine (thank you by the way). But not with the del key.

In order to let some people to try to reproduce it, here is my configuration :
Archlinux x86_64
xfce 4.6
The Libreoffice version is the RC2.
Comment 3 Alex Thurgood 2011-01-11 07:00:39 UTC
Hmmm, I was wondering whether this behaviour has been introduced by the changes to the source code in the Delete cell data function in Calc ? Perhaps they are linked ? 


Alex
Comment 4 Alex Thurgood 2011-01-11 07:01:34 UTC
I'll have a try on a Linux machine and report back later.


Alex
Comment 5 Cédric Bosdonnat 2011-01-11 08:00:45 UTC
this is a duplicate of 
https://bugzilla.novell.com/show_bug.cgi?id=649506

which is now fixed by this commit

http://cgit.freedesktop.org/libreoffice/build/commit/?h=libreoffice-3-3&id=26413a442c949dad3e4cb32261cfeb493ebe1842

I'm closing the bug now, but feel free to reopen if a later version doesn't fix the bug.