On 05/22/2017 07:58 PM, Ed Greshko wrote: > Resending due to error in *not* sending to the list.... > > On 05/23/17 06:41, Paul Erickson wrote: >> On 22/05/17 02:56 PM, Ed Greshko wrote: >>> On 05/23/17 05:21, Paul Erickson wrote: >>>> Within the last couple of days an update is causing LibreOffice to >>>> crash. When I click on the icon, recovery mode comes up, but there is >>>> no file to recover, and when I click "OK" the Logo comes up briefly >>>> and then goes away. When I try to run from the command line, I get >>>> "Application error". >>>> >>>> I have tried reinstalling but get the same "Application error" when I >>>> attempt to run it from the command line. >>>> >>>> Any thoughts? >>> My first try would be to move ~/.config/libreoffice to a temporary >>> location and try again. >>> >> Tried that, and the same problem occurs. >> > I see.... > > Assuming you're starting it from the command line with just > "libreoffice" do you also have the problem if you start an individual > component such as "libreoffice --writer". (FWIW, similar suggestion > from Rick didn't help) > > And, if possible, have you tried logging in as another user and running > libreoffice to eliminate your current environment? > > Also, FWIW, I've run into some "interesting" failures when shared > libraries were updated and the older versions were still resident in > memory. e.g. unable to logout of a KDE session via the GUI. So, > sometimes logging out/in clears things up. > > You've indicated you've filed a BZ but didn't note the BZ number. Could > you post it? > Maybe try "strace -o trace.txt libreoffice --writer" and take a look around the end of the trace output for anything interesting, e.g., some library not found. (Sorry if this is delivered in html -- Thunderbird sometimes refuses to send plain text). *Mark C. Allman, PMP, CSM* Founder, See How You Ski, www.seehowyouski.com <http://www.seehowyouski.com> _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
