[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #22 from LOO Debugger --- Hi again, I found a very hacky workaround: by removing "~/.local/lib/python3.10/site-packages" I managed to regain control of LOo (just removing "uno*" there was not sufficient). **But I still believe there's a BIG problem if killing a macro results in LOo trashing the users' installed python packages directory...** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #21 from LOO Debugger --- Bump? Anyone else could try to help? LOo is totally unusable now... Removing my personal LOo folder, Reinstalling LOo, Reinstalling all UNO python packages, Reinstalling loo-py-provider, using completly new Writer/Calc files, NOTHING helps... I can't use LOo at all, just because I killed a faulty macro... 1) That's already quite a MAJOR problem per-se... 2) Since it's persistent over any re-install/re-configuration, it probably reflects quite a MAJOR problem in LOo code base, where it seem to modify something way out of its expected reach... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #20 from LOO Debugger --- Created attachment 191650 --> https://bugs.documentfoundation.org/attachment.cgi?id=191650&action=edit APSO install attempt failure message -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #19 from LOO Debugger --- Created attachment 191649 --> https://bugs.documentfoundation.org/attachment.cgi?id=191649&action=edit Trace dumped displayed on CLI after failed attempt to install APSO -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #18 from LOO Debugger --- Additional information: Reading: https://superuser.com/questions/1753373/libre-office-create-is-not-enabled-for-python-macro I tried to install APSO: https://extensions.libreoffice.org/en/extensions/show/apso-alternative-script-organizer-for-python And got this error message in attached picture. And now when I open libreoffice, I get the generic GUI proposing to create a Writer/Calc/... document. But whatever I do there (trying to open a Wirter doc or to open the Tools>Extensions menu), now LOo crashes!!! cf. new trace in attachment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #17 from LOO Debugger --- :( Thanks anyway for your time & help! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 BogdanB changed: What|Removed |Added Blocks||107659 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107659 [Bug 107659] [META] Macro bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 Julien Nabet changed: What|Removed |Added CC|serval2...@yahoo.fr | --- Comment #16 from Julien Nabet --- (In reply to LOO Debugger from comment #15) > ... > I just did: > # apt install libuno* --reinstall > # apt install libreoffice-script-provider-python --reinstall > > But problem is still there... Ok no idea then so uncc myself. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #15 from LOO Debugger --- I was on Ubuntu and switched to Mint. Should not be a problem since the 2nd is based on the 1rst... Also I needed a 7.x LOo a few months ago, so I set up a PPA: ``` $ cat /etc/apt/sources.list.d/libreoffice-ubuntu-libreoffice-still-jammy.list deb https://ppa.launchpadcontent.net/libreoffice/ppa/ubuntu/ jammy main ``` I just did: # apt install libuno* --reinstall # apt install libreoffice-script-provider-python --reinstall But problem is still there... -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 Julien Nabet changed: What|Removed |Added Status|NEEDINFO|NEW Keywords|wantBacktrace |haveBacktrace --- Comment #14 from Julien Nabet --- Thank you it worked! The relevant part is: #9 0x7f290a6d8027 in () at /usr/lib/libreoffice/program/libpyuno.so #10 0x7f290a6e59eb in pyuno::Runtime::extractUnoException(pyuno::PyRef const&, pyuno::PyRef const&, pyuno::PyRef const&) const () at /usr/lib/libreoffice/program/libpyuno.so #11 0x7f29b40e742d in pyuno_Loader_get_implementation () at /usr/lib/libreoffice/program/libpythonloaderlo.so #12 0x7f29bc2596a7 in () at /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 It seems LO can't load Python part. On which Linux distrib are you? I'm on Debian testing updated today and I've got the package libreoffice-script-provider-python installed. I think you need a Libreoffice/Python package. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #13 from LOO Debugger --- Created attachment 191624 --> https://bugs.documentfoundation.org/attachment.cgi?id=191624&action=edit BackTrace from gdb Not sure I understood where I should do the 'bt' or 'c', but I think I got the BT you asked -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 Julien Nabet changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #12 from Julien Nabet --- (In reply to LOO Debugger from comment #10) > Comment on attachment 191620 [details] > Attempting to debug with GDB > > Attempting to do as recommended. > - As user => GDB cannot attach to process > - Ass root => LOo seems to crash too strongly ; results in message "no bt" > in GDB Reading your last trace, I see: [New LWP 482951] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f7ddbd189df in __GI___poll (fds=0x556544072dd0, nfds=3, timeout=61357) at ../sysdeps/unix/sysv/linux/poll.c:29 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. (gdb) c Continuing. [New Thread 0x7f7dbb7fe640 (LWP 484614)] => OK Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault. 0x7f7d6860062d in ?? () (gdb) c Continuing. [New Thread 0x7f7dbbe2d640 (LWP 484676)] => OK but then: [Thread 0x7f7d453ce640 (LWP 484689) exited] Thread 1 "soffice.bin" received signal SIGABRT, Aborted. __pthread_kill_implementation (no_tid=0, signo=6, threadid=140178438963584) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) c Continuing. => No, you should have typed "bt" here since it wasn't "?" or "??". -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #11 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #10 from LOO Debugger --- Comment on attachment 191620 --> https://bugs.documentfoundation.org/attachment.cgi?id=191620 Attempting to debug with GDB Attempting to do as recommended. - As user => GDB cannot attach to process - Ass root => LOo seems to crash too strongly ; results in message "no bt" in GDB -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #9 from LOO Debugger --- Created attachment 191620 --> https://bugs.documentfoundation.org/attachment.cgi?id=191620&action=edit Attempting to debug with GDB -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #8 from Julien Nabet --- Could you try this? open a first terminal and launch LO open a second terminal and type: "gdb --pid=$(pidof soffice.bin)" then wait a bit and type "c" for continue Go back to terminal 1 and try to reproduce the pb. On terminal 2, each time you'll get something like "?" or "??", type "c". after these, you'll got something else, at this moment type "bt" and copy paste the result in a txt file that you'll attach. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #7 from LOO Debugger --- Created attachment 191614 --> https://bugs.documentfoundation.org/attachment.cgi?id=191614&action=edit LDD log2 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #6 from LOO Debugger --- Created attachment 191613 --> https://bugs.documentfoundation.org/attachment.cgi?id=191613&action=edit LDD log1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #5 from LOO Debugger --- Created attachment 191612 --> https://bugs.documentfoundation.org/attachment.cgi?id=191612&action=edit strace directly from LOo with interesting error message -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #4 from LOO Debugger --- Created attachment 191611 --> https://bugs.documentfoundation.org/attachment.cgi?id=191611&action=edit backtrace, LOo crashes before even getting to Macro problem -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 CC||serval2...@yahoo.fr Keywords||wantBacktrace Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Julien Nabet --- A backtrace would be useful (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:_How_to_get_a_backtrace) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #2 from LOO Debugger --- - Tools > Macro > Organize > BeanShell also crashes -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158889] Macro kill => any attempt to access macros crashes LOo
https://bugs.documentfoundation.org/show_bug.cgi?id=158889 --- Comment #1 from LOO Debugger --- - Tools > Macro > Run Macro also crashes - Tools > Macro > Organize > Javascript also crashes -- You are receiving this mail because: You are the assignee for the bug.
