Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
Dear Stuart, I tried the two things you suggested - the same libreoffice problems & same message occurred with a freshly-created default user. The pkg_info list you indicated as helpful is attached. I have cc'ed this to ports as you suggested. regards with gratitude, cal. PS the original email describing the problem is appended below for interested ports@ readers. ___ From: owner-m...@openbsd.org on behalf of Stuart Henderson Sent: Monday, 26 September 2022 11:27 PM To: misc@openbsd.org Subject: Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem On 2022-09-25, Luke A. Call wrote: > Details in case it helps: > https://marc.info/?l=openbsd-misc=161280915705719=2 > https://marc.info/?l=openbsd-bugs=164814366002554=2 I think I tried to read that bugs@ report before but got totally bogged down in all the detail about how you use a special script for pkg_add etc The packages you talked about as being necessary were I think devhelp and gsettings-desktop-schemas libreoffice's chain of dependencies already includes gsettings-desktop-schemas and libreoffice is running fine here without devhelp, so there must be something other than just those involved It would be helpful to have a list of all packages installed on a machine where it is failing. (full output of "pkg_info -q"). Also try to replicate with a newly created user i.e. so it is isolated from the contents of config files in your home directory. Please send reports about ports to po...@openbsd.org and/or the port maintainer. They are more likely to get seen there than on bugs@, and *much* more likely to get seen there than on misc. ___ Original message: ___ 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 [:] but have no idea what should be set as and 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 Consider setting $PYTHONHOME to [:] 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 0x00b1d90594e8 (most recent call first): pthread_mutex_destroy on mutex with waiters! ___@@ The results of the pkg_add process - libreoffice was indeed updated: cfl$ doas pkg_add -u doas (cfl@cfl.modem) password: quirks-5.5 signed on 2022-09-24T12:39:42Z Collision in partial-webkitgtk4-2.36.8->webkitgtk4-2.36.8: the following files already exist /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSBase.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSContextRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSObjectRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSStringRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSTypedArray.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSValueRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/Jav
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
On 2022-09-25, Luke A. Call wrote: > Details in case it helps: > https://marc.info/?l=openbsd-misc=161280915705719=2 > https://marc.info/?l=openbsd-bugs=164814366002554=2 I think I tried to read that bugs@ report before but got totally bogged down in all the detail about how you use a special script for pkg_add etc The packages you talked about as being necessary were I think devhelp and gsettings-desktop-schemas libreoffice's chain of dependencies already includes gsettings-desktop-schemas and libreoffice is running fine here without devhelp, so there must be something other than just those involved It would be helpful to have a list of all packages installed on a machine where it is failing. (full output of "pkg_info -q"). Also try to replicate with a newly created user i.e. so it is isolated from the contents of config files in your home directory. Please send reports about ports to po...@openbsd.org and/or the port maintainer. They are more likely to get seen there than on bugs@, and *much* more likely to get seen there than on misc.
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
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 Sent: Monday, 26 September 2022 12:39 AM To: Cal Ledsham ; 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=161280915705719=2 https://marc.info/?l=openbsd-bugs=164814366002554=2 On 2022-09-25 08:24:44-0600, Luke A. Call 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+, Cal Ledsham 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 > > [:] > > but have no idea what should be set as and 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 > > Consider setting $PYTHONHOME to [:] > > 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 0x00b1d90594e8 (most recent call first): > > > > pthread_mutex_destroy on mutex with waiters! > > >
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=161280915705719=2 https://marc.info/?l=openbsd-bugs=164814366002554=2 On 2022-09-25 08:24:44-0600, Luke A. Call 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+, Cal Ledsham 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 > > [:] > > but have no idea what should be set as and 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 > > Consider setting $PYTHONHOME to [:] > > 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 0x00b1d90594e8 (most recent call first): > > > > pthread_mutex_destroy on mutex with waiters! > > >
Re: Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
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+, Cal Ledsham 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 > [:] > but have no idea what should be set as and 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 > Consider setting $PYTHONHOME to [:] > 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 0x00b1d90594e8 (most recent call first): > > pthread_mutex_destroy on mutex with waiters! >
Libreoffice crashing on Thinkcentre m92p 7.1 FVWM - seems to be a python problem
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 [:] but have no idea what should be set as and 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 Consider setting $PYTHONHOME to [:] 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 0x00b1d90594e8 (most recent call first): pthread_mutex_destroy on mutex with waiters! ___@@ The results of the pkg_add process - libreoffice was indeed updated: cfl$ doas pkg_add -u doas (cfl@cfl.modem) password: quirks-5.5 signed on 2022-09-24T12:39:42Z Collision in partial-webkitgtk4-2.36.8->webkitgtk4-2.36.8: the following files already exist /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSBase.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSContextRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSObjectRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSStringRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSTypedArray.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JSValueRef.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/JavaScript.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/JavaScriptCore/WebKitAvailability.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCAutocleanups.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCClass.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCContext.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCDefines.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCException.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCOptions.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCValue.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCVirtualMachine.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/JSCWeakValue.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/jsc/jsc.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitApplicationInfo.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitAuthenticationRequest.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitAutocleanups.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitAutomationSession.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitBackForwardList.h from webkitgtk4-2.36.8 (same checksum) /usr/local/include/webkitgtk-4.0/webkit2/WebKitBackForwardListItem.h
