Hello fellow Antixers,
these days I use Antix on my computer at work for Office-duty. I work at an old Dell Optiplex GX270, using Antix, there is no need for my employer to buy new expensive (MS-)computers. Recently I experienced that LibreOffice-writer suddenly would lock-up and freeze while I was working on a document. This happened several times and caused my work to be lost, it was non-recoverable. I noticed when LibreOffice froze that parts of several applications started afterwards (terminal, applicationsmenu) remained visible in the frozen libreoffice window after I closed them. I did get the impression that there was a conflict between libreoffice and the windowmanager/wallpapersetter.
Now i have installed Lxde as desktop-environment to check out if this was the case. Lxde has a different way to apply wallpapers than the Antix-style. I haven't had any lock-ups of libreoffice since then __{{emoticon}}__ . I don't know what exactly caused the problems with libreoffice, but I thought it was good to let you know at the Antix forum.
topic title: LibreOffice in Antix 16
9 posts
• Page 1 of 1
-
Posts: 128
- Joined: 31 Jan 2009
-
Posts: 1,445
- Joined: 09 Feb 2012
#2
If not, it's a wide-open crapshoot guess as to what transpired.
Did you investigate (and preserve) the syslog and session log when the incidents occurred?I don't know what exactly caused the problems with libreoffice
If not, it's a wide-open crapshoot guess as to what transpired.
-
Posts: 128
- Joined: 31 Jan 2009
#3
I tried to search the logs (.xsession-errors, Xorg0.log) but I couldn't find any reference to libreoffice. All I could try was this 'wide-open crapshoot' as you call it.
-
Posts: 1,139
- Joined: 26 Apr 2008
#4
Sound reasonable?
Try doing similar work again, and if you encounter the problem, restart the system, capture the logs, and make them available to the antiX developers to interpret the results. Who knows, it may help, or the root cause may remain elusive, but it could be any number of things, not all necessarily related to the system or the release - such as hardware issues that only surface when certain sectors of the devices are accessed. Or the problem could be traced to something deep in the internals that a system expert may track, but anyone other than an expert may struggle to notice.Hannes Worst wrote:I tried to search the logs (.xsession-errors, Xorg0.log) but I couldn't find any reference to libreoffice. All I could try was this 'wide-open crapshoot' as you call it.
Sound reasonable?
-
Posts: 128
- Joined: 31 Jan 2009
#5
I will be doing similar work again, only in lxde. In fact I do this multiple times a day. It is my work-computer so i am trying not to lose to much of my documents. When I encouter problems (haven't experienced them in lxde yet) I will send you the logs.
-
Posts: 1,445
- Joined: 09 Feb 2012
#6
Hannes, by 'wide-open crapshoot' I meant 'unpredictable roll of the dice'
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Craps"
linktext was:"https://en.wikipedia.org/wiki/Craps"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Craps"
linktext was:"https://en.wikipedia.org/wiki/Craps"
====================================
-
Posts: 128
- Joined: 31 Jan 2009
#7
Skidoo, thanks for clarifying! And you were absolutely right, my approach was indeed some sort of gamble.
-
Posts: 32
- Joined: 15 Oct 2015
#8
I have been working out a LO bug on a Trusty GNOME earlier this month. FOund out issues are pretty much widespread, diverse (from super slowness to full *system* freeze 8-o) and so we have many reports available. I thought I'd share just a few with you guys:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://ubuntuforums.org/showthread.php?t=2322879&page=2"
linktext was:"LO super slow, Ubuntu 16.04"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mageialinux-online.org/forum/topic-22224-0-216292+libreoffice-instable.php#m216292"
linktext was:"LO Calc full freeze, Mageia (FR)"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://community.alfresco.com/thread/206797-script-to-restart-libreoffice-when-it-freeze"
linktext was:"Script to restart libreoffice core when it freeze"
====================================
They are so f***ing diverse one can gain lots of time proceeding step by step.
1. Use a different graphical engine using `$ SAL_USE_VCLPLUGIN={gen,gtk,gtk3,kde4} libreoffice`
2. Try after closing LO and having moved away ~/.config/libreoffice
3. Change the desktop environment as Hannes did.
...
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://ubuntuforums.org/showthread.php?t=2322879&page=2"
linktext was:"LO super slow, Ubuntu 16.04"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mageialinux-online.org/forum/topic-22224-0-216292+libreoffice-instable.php#m216292"
linktext was:"LO Calc full freeze, Mageia (FR)"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://community.alfresco.com/thread/206797-script-to-restart-libreoffice-when-it-freeze"
linktext was:"Script to restart libreoffice core when it freeze"
====================================
They are so f***ing diverse one can gain lots of time proceeding step by step.
1. Use a different graphical engine using `$ SAL_USE_VCLPLUGIN={gen,gtk,gtk3,kde4} libreoffice`
2. Try after closing LO and having moved away ~/.config/libreoffice
3. Change the desktop environment as Hannes did.
...
-
Posts: 99
- Joined: 07 Feb 2013
#9
Hannes I use LO in Xfce4 and have experienced problems when resizing the window. An extensive google search led me to stumble over libreoffice-gtk which are components to integrated with DE's built using the Gimp Tool Kit (like Xfce4). There is also a libreoffice-gnome and libreoffice-kde which may be of some use for you and might just fix your original problem.