Thank you - this is a helpful start and some tips to go on with, and the from-terminal opening might be a workaround for now. -cal.
________________________________ From: Luke A. Call <luke...@onemodel.org> Sent: Monday, 26 September 2022 12:39 AM To: Cal Ledsham <cfleds...@hotmail.com>; misc@openbsd.org <misc@openbsd.org> Subject: Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem Details in case it helps: https://marc.info/?l=openbsd-misc&m=161280915705719&w=2 https://marc.info/?l=openbsd-bugs&m=164814366002554&w=2 On 2022-09-25 08:24:44-0600, Luke A. Call <luke...@onemodel.org> wrote: > I had a similar problem where I could open files with LO if I typed them > on the command line when launching LO, but File / Open would crash when > choosing the file and hitting OK. But I don't think mine was > python-related. It seemed that my cleaning up by removing evidently unused > packages > removed something that was required for LO but not explicitly listed in > its dependencies. Fortunately I had been logging the output whenever I > ran pkd_delete, and could use that for reference. After a long process of > elimination, reinstalling things to see what would happen, I think it was one > of these that made it work again (though probably a different one for > you): > > (from most to least likely): devhelp gsettings-desktop-schemas > glib2-networking > (and probably not, but maybe caused some other package to be installed > that did it: gnome-desktop totem) > > The relevant email thread at the time is probably in the archives; I > never got a reply, IIRC. > > Good luck :) > > > On 2022-09-25 02:23:00+0000, Cal Ledsham <cfleds...@hotmail.com> wrote: > > Dear OBSDer's - > > I am running 7.1 with out of the box FVWM. Since this Sunday morning > > libreoffice has crashed whenever I try to either open an existing file or > > create a new file in libreoffice writer. When opening it allows file > > selection but then crashes. > > > > (Below I have put the crash message ex launching terminal, the messages > > from a pkg_add -u, and a dmesg). > > > > I have tried the following remedies with the same result: opening different > > files, updating all packages with doas pkg_add -u (looked promising as > > there was a libreoffice update), rebooting a few times, syspatching again > > (first attempt at using libreoffice since applying patch 10_expat > > yesterday? or Friday?), and also opening the safe mode of libreoffice. The > > same result seems to occur. I tried to run an doas EXPORT PYTHONHOME > > <prefix>[:<exec_prefix>] > > but have no idea what should be set as <prefix> and <exec_prefix> and how > > the grammar should quite be. > > > > In accord with requested convention, there is a dmesg at the end of the > > file. > > > > Any help gratefully received. > > > > (Sorry if this is a stupid problem or if the information here is > > unhelpfully insufficient.) > > > > regards, > > Cal > > > > message in terminal screen from which libreoffice was invoked: > > > > cfl$ libreoffice > > Warning: failed to launch javaldx - java may not function correctly > > Could not find platform independent libraries <prefix> > > Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>] > > Python path configuration: > > PYTHONHOME = (not set) > > PYTHONPATH = '/usr/local/lib/libreoffice/program/../program' > > program name = 'python3' > > isolated = 0 > > environment = 1 > > user site = 1 > > import site = 1 > > sys._base_executable = '/usr/local/bin/python3' > > sys.base_prefix = '/usr/local' > > sys.base_exec_prefix = '/usr/local' > > sys.platlibdir = 'lib' > > sys.executable = '/usr/local/bin/python3' > > sys.prefix = '/usr/local' > > sys.exec_prefix = '/usr/local' > > sys.path = [ > > '/usr/local/lib/libreoffice/program/../program', > > '/usr/local/lib/python39.zip', > > '/usr/local/lib/python3.9', > > '/usr/local/lib/python3.9/lib-dynload', > > ] > > Fatal Python error: init_fs_encoding: failed to get the Python codec of the > > filesystem encoding > > Python runtime state: core initialized > > LookupError: no codec search functions registered: can't find encoding > > > > Current thread 0x000000b1d90594e8 (most recent call first): > > <no Python frame> > > pthread_mutex_destroy on mutex with waiters! > > >
