Description: i was trying to setup my digital signatures workflow so that when i share some document, i can sign it. the dialog didn't show my gpg keys (which i imported on the system using gpg --import <key_file> command), and when i clicked on the help button to learn more about it, the application crashed. Steps to Reproduce: 1. open a pdf in draw 2. open the digital signatures dialog from File > Digital Signatures > Digital Signatures... 3. click on the help button 4. crash! Actual Results: the application crashes Expected Results: clicking on the help button should redirect me to the help page. Reproducible: Always User Profile Reset: Yes Additional Info: -
Hello Sahil Gautam, I am unable to reproduce the bug in the current build Version: 25.2.3.2 (X86_64) / LibreOffice Community Build ID: bbb074479178df812d175f709636b368952c2ce3 CPU threads: 22; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Can you confirm the build and operating system you are using. Also can you test that you get the same result in safe mode From the menu bar: Choose Help - Restart in Safe Mode. From a command line Start LibreOffice from command line with --safe-mode option I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once this has been completed and the results shared.
On pc Debian x86-64 with master sources updated today + with-help in autogen.input, I don't reproduce this. Sahil: on what env are you? (Windows, macOS, Linux) If Linux, Gnome, KDE, other? Do you use a build with help embedded or online help? what language UI do you use? If possible, it would be useful to have a backtrace.
- version and system info Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 520(Build:2) CPU threads: 32; OS: Linux 6.12; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded - crashes in safe mode as well, both from the ui and when started with --safe-mode
@Julien Nabet hi, how can i share the backtrace for libreoffice installed from the package manager? i have SAL_LOG="+INFO" and SAL_LOG_FILE=logfile set in my .zshrc on linux. I am using Void Linux with Kernel: 6.12.28_1 with a tiling window manager (dwm). how can i know if the help is embedded or online? there is a `/usr/lib/libreoffice/help` directory with a bunch of files, pasting a few here ``` ./es/sdraw.idxl/segments.gen ./es/sdraw.idxl/segments_3 ./es/sdraw.idxl/_0.cfs ./es/sdatabase.idxl ./es/sdatabase.idxl/segments.gen ./es/sdatabase.idxl/segments_3 ./es/sdatabase.idxl/_0.cfs ./es/swriter.db ./es/simpress.jar ./es/scalc.db ./es/simpress.idxl ./es/simpress.idxl/segments.gen ./es/simpress.idxl/segments_3 ./es/simpress.idxl/_0.cfs ./es/sdatabase.tree ./es/sbasic.tree ./es/sdraw.jar ./es/simpress.db ./es/scalc.cfg ./es/smath.ht ./es/err.html ``` (all of them https://termbin.com/h4gc)
it crashes on gnome too!
(In reply to Sahil Gautam (allotropia) from comment #4) > @Julien Nabet hi, how can i share the backtrace for libreoffice installed > from the package manager? i have SAL_LOG="+INFO" and SAL_LOG_FILE=logfile > set in my .zshrc on linux. See https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU/Linux:_How_to_get_a_backtrace > > I am using Void Linux with Kernel: 6.12.28_1 with a tiling window manager > (dwm). how can i know if the help is embedded or online? If when trying to go to Help, it opens a browser, it's online. It makes me think, do you have a crash any time you click an help button or specifically in the situation of the bugtracker? Perhaps it could be a dup of tdf#165980 (put in see also)?
indeed it was built with --with-help (https://github.com/void-linux/void-packages/blob/515f40b00c44dcb6760daba70e77cbac2b27f5f9/srcpkgs/libreoffice/template#L410)
(In reply to Sahil Gautam (allotropia) from comment #7) > indeed it was built with --with-help > (https://github.com/void-linux/void-packages/blob/ > 515f40b00c44dcb6760daba70e77cbac2b27f5f9/srcpkgs/libreoffice/template#L410) Ok let's consider then it as a dup of tdf#165980 unless you can provide a bt showing otherwise *** This bug has been marked as a duplicate of bug 165980 ***