Bug 74706 - FORMCONTROLS: bug with mouse command
Summary: FORMCONTROLS: bug with mouse command
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.4.2 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-08 10:22 UTC by Bertschi J-Y
Modified: 2014-02-26 02:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bertschi J-Y 2014-02-08 10:22:42 UTC 
Problem description: 
when I select a cell to move it with the mouse, the mouse is able to move on the screen but all computer action are over;
I just can press the button to restart computer...

Steps to reproduce:
1. ....select a cell to move it
2. ....try to move it to an other place
3. ....everything is freez

Current behavior:

Expected behavior:

              thank you so for your interest and devotion to FreeOffice
Operating System: Fedora
Version: 4.1.4.2 release
Comment 1 A (Andy) 2014-02-09 11:41:02 UTC 
not reproducible with LO 4.2.0.4 (Win 8.1)
Comment 2 Bertschi J-Y 2014-02-12 08:26:43 UTC 
Hei,

The bug I reported didn't happened on Window  but on Linux Fedora 19
Thanks...

J-Y B


On Sunday 09 February 2014 11:41:02 bugzilla-daemon@freedesktop.org wrote:
> https://bugs.freedesktop.org/show_bug.cgi?id=74706
> 
> --- Comment #1 from A (Andy) <stgohi-lobugs@yahoo.de> ---
> not reproducible with LO 4.2.0.4 (Win 8.1)
Comment 3 sophie 2014-02-13 16:57:28 UTC 
I can't reproduce with 4.5.1.3 on Debian Squeeze - Sophie
Comment 4 Joel Madero 2014-02-26 02:50:31 UTC 
Another person saying cannot confirm. Ubuntu 13.10, LibreOffice 4.1.5.3 and 4.3 dev built today

Please try the following: 
Upgrade to 4.1.5
Start with a fresh profile (backup and then delete ~/.config/libreoffice)

Marking as WFM - if those two solutions don't work let us know, mark the bug as UNCONFIRMED and we'll go from there but I suspect it's not our bug as no one can reproduce it.