View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007957 | Kali Linux | Kali Package Bug | public | 2022-09-27 09:27 | 2022-10-11 06:49 |
Reporter | leontiosp | Assigned To | sbrun | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Fixed in Version | 2022.4 | ||||
Summary | 0007957: GVM Report exported in PDF format results to 0 byte document | ||||
Description | GVM Report exported in PDF format results to 0 byte document. | ||||
COPYING FOR GVM FORUM on same issue: QUOTE According to / if i understand the last part of the comment Error in pre-release-4 with utf8x and hyperref · Issue 0000833 · latex3/latex2e · GitHub correctly this seems to be an issue in the utf8x part of the inputenc package. Identifying the issue / bug tracker of that package and creating a sane bug report (with a reference to the previous linked one) could help in getting a fixed version of that LaTeX package into Kali Use the workaround to remove the buggy LaTeX package mentioned in PDF, XML reports are empty on Kali Linux - 0000004 by Eero 2 As a last resort (no guarantee for success): One could directly create a pull request at GitHub - greenbone/gvmd: Greenbone Vulnerability Manager - The database backend for the Greenbone Community Edition (removing that buggy package) to directly start a conversation with the responsible team Note: Options 2. and 3. might not work as expected for all cases where the inputenc package is still required. UNQUOTE |
|
Any news on the issue? Panos |
|
Hi look for the file latex.xsl in /var/lib/gvm/gvmd/report_formats/* In the file replace "\usepackage[utf8x]{inputenc}" by "%\usepackage[utf8x]{inputenc}" |
|
@sbrun Thank you for your workaround suggestion. |
|
I didn't need to change the 2 other latex files to fix the issue on my machine Do you have any information in the gvmd log to guide us? (/var/log/gvm/gvmd/*) |
|
Thank you for concerning... Attached you may find a gvmd.log and my latex.xsl. |
|
The attached files... |
|
@sbrun Eventually, your workaround worked perfectly for me also!!! P.S. It was my mistake in editing the file... |
|
Thanks for the update. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2022-09-27 09:27 | leontiosp | New Issue | |
2022-09-27 10:47 | g0tmi1k | Assigned To | => sbrun |
2022-09-27 10:47 | g0tmi1k | Status | new => assigned |
2022-09-29 15:20 | leontiosp | Note Added: 0016856 | |
2022-10-03 15:09 | leontiosp | Note Added: 0016905 | |
2022-10-04 07:44 | sbrun | Note Added: 0016907 | |
2022-10-05 06:02 | leontiosp | Note Added: 0016917 | |
2022-10-06 09:22 | sbrun | Note Added: 0016934 | |
2022-10-06 14:40 | leontiosp | Note Added: 0016938 | |
2022-10-06 14:42 | leontiosp | Note Added: 0016939 | |
2022-10-08 09:19 | leontiosp | Note Added: 0016941 | |
2022-10-11 06:49 | sbrun | Note Added: 0016955 | |
2022-10-11 06:49 | sbrun | Status | assigned => resolved |
2022-10-11 06:49 | sbrun | Resolution | open => fixed |
2022-10-11 06:49 | sbrun | Fixed in Version | => 2022.4 |