Bug 93383

Summary: Dragging cells broken after update to 5.0.0.5
Product: LibreOffice Reporter: Jochum <jochum.doring>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: momonasmon
Priority: medium    
Version: 5.0.0.5 release   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
Crash report or crash signature: Regression By:

Description Jochum 2015-08-12 10:38:04 UTC 
Created a new empty spreadsheet.

Entered a number in one cell and text in another.

Tried to move the cells down several rows but the cursor is not showing the proper moving symbol for dragging.

Pressing shift does activate the desired dragging mode (cursor changes), but dragging does not move the information/cells.
Comment 1 Maxim Monastirsky 2015-08-12 11:00:43 UTC 
Hi,

What distro do you use? Is it Arch by a chance? Is exporting SAL_USE_VCLPLUGIN=gtk makes any difference?
Comment 2 Jochum 2015-08-12 14:10:42 UTC 
Hello Maxim,

I am indeed using Arch or Manjaro to be exact. I used your suggestion and put it in my .bashrc

When i start libreoffice from a terminal it works again, this is the output:

libreoffice 
Xlib:  extension "XINERAMA" missing on display ":0.0".
W: Unknown node under /registry/extlang: deprecated
W: Unknown node under /registry/grandfathered: comments
W: Unknown node under /registry/grandfathered: comments

Could this also be related to the display driver or x server layout? I am using Nvidia's proprietary driver and a custom x configuration.

Cheers, Jochum
Comment 3 Maxim Monastirsky 2015-08-12 14:19:15 UTC 
OK, Thanks for confirming.

(In reply to Jochum from comment #2)
>I used your suggestion and put it in my .bashrc
AFAIK there is no need for that. You can just uncomment that line in /etc/profile.d/libreoffice-fresh.sh.

> Could this also be related to the display driver or x server layout?
No. It's related to the switch to GTK3 by default. The workaround with SAL_USE_VCLPLUGIN=gtk forces it to use GTK2, which doesn't have that bug.

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