zathura issueshttps://git.pwmt.org/pwmt/zathura/-/issues2024-03-19T16:52:55+01:00https://git.pwmt.org/pwmt/zathura/-/issues/411zathura listed as background only process2024-03-19T16:52:55+01:00Hersh Kumarzathura listed as background only processWhen attempting to use `yabai` 7.0.2, it was found that zathura incorrectly lists itself as a background-only process. See [yabai issue #2168](https://github.com/koekeishiya/yabai/issues/2168).When attempting to use `yabai` 7.0.2, it was found that zathura incorrectly lists itself as a background-only process. See [yabai issue #2168](https://github.com/koekeishiya/yabai/issues/2168).https://git.pwmt.org/pwmt/zathura/-/issues/385`recolor` causes flashes when zooming2024-03-04T10:41:39+01:00a b`recolor` causes flashes when zoomingWhen `recolor` is set to `true`, zooming in and out with `-`/`+` will cause the pages' colors to flash between normal colors and `recolor`ed colors. The effect is extremely distracting and painful to look at.When `recolor` is set to `true`, zooming in and out with `-`/`+` will cause the pages' colors to flash between normal colors and `recolor`ed colors. The effect is extremely distracting and painful to look at.https://git.pwmt.org/pwmt/zathura/-/issues/334Zathura ignores font setting with complex font names2023-03-30T16:43:27+02:00Pavel KovachevZathura ignores font setting with complex font namesOn my system, I primarily use a font named `Bm437 Verite 8x16`, usually it's fairly simple to set up. With zathura, however, no matter the syntax used, f.e.:
`set font "Bm437 Verite 8x16 12"`
`set font "Bm437 Verite 8x16 Regular 12"`
...On my system, I primarily use a font named `Bm437 Verite 8x16`, usually it's fairly simple to set up. With zathura, however, no matter the syntax used, f.e.:
`set font "Bm437 Verite 8x16 12"`
`set font "Bm437 Verite 8x16 Regular 12"`
`set font "BM437 Verite 8x16 Regular" 12`
zathura either continues to fall back to the default alias in `monospace` (Liberation Mono in my case) or in some cases discards the configuration entirely and suddenly flips to a white background. The font in question is an .otb bitmap but other fonts in the same format (Terminus, f.e.) work fine. I've sifted through bug reports / forums / man pages and haven't found anything that resembles my issue so I'm a bit confused. The same behaviour persists between configuration via zathurarc and from command prompt at runtime.
Version info:
```
$ zathura -v
zathura 0.4.9
girara 0.3.7 (runtime: 0.3.7)
(plugin) pdf-mupdf (0.3.9) (/usr/lib64/zathura/libpdf-mupdf.so)
```https://git.pwmt.org/pwmt/zathura/-/issues/274rseq syscall not allowed in strict sandbox2023-03-06T07:25:50+01:00Simon Drseq syscall not allowed in strict sandbox# How to reproduce
```
$ zathura --version
zathura 0.4.9
girara 0.3.7 (runtime: 0.3.7)
(plugin) pdf-mupdf (0.3.8) (/usr/lib/zathura/libpdf-mupdf.so)
```
```
$ cat .config/zathura/zathurarc
set selection-clipboard clipboard
set sandbox s...# How to reproduce
```
$ zathura --version
zathura 0.4.9
girara 0.3.7 (runtime: 0.3.7)
(plugin) pdf-mupdf (0.3.8) (/usr/lib/zathura/libpdf-mupdf.so)
```
```
$ cat .config/zathura/zathurarc
set selection-clipboard clipboard
set sandbox strict
```
Running on Arch Linux, sway/wayland.
Try to open any pdf document or just start zathura
# Expected
A window opens.
# Observed
Zathura does not open and in journalctl you can find:
```
... audit[103187]: SECCOMP auid=1000 uid=1000 gid=984 ses=1 pid=103187 comm="zathura" exe="/usr/bin/zathura" sig=31 arch=c000003e syscall=334 compat=0 ip=0x7f81638183c6 code=0x0
```
334 corresponds to `rseq`.
Running zathura with `--log-level debug` shows that it allows some syscalls, but `rseq` is not in the list.
Wanted to fix it, but already seems to be fixed in `develop` in https://git.pwmt.org/pwmt/zathura/-/commit/0cfaac072df2bc0ca6693c6262ec5753076e3fe9, just not yet released.https://git.pwmt.org/pwmt/zathura/-/issues/261zathura crahsed when openning epub in Double Page View2024-01-09T06:40:00+01:00prheonorzathura crahsed when openning epub in Double Page View*** longjmp causes uninitialized stack frame ***: terminated
Segmentation fault
![Peek_2022-01-19_22-37](/uploads/cdc1ee6a17575bf416fd9e2fa5abd63d/Peek_2022-01-19_22-37.gif)*** longjmp causes uninitialized stack frame ***: terminated
Segmentation fault
![Peek_2022-01-19_22-37](/uploads/cdc1ee6a17575bf416fd9e2fa5abd63d/Peek_2022-01-19_22-37.gif)https://git.pwmt.org/pwmt/zathura/-/issues/209Lots of memory usage when zoomed in2024-02-27T16:05:28+01:00LuXuLots of memory usage when zoomed inWhen I open a document the memory usage is normally ~100MB. But if I zoom in to the maximum level, the memory usage goes above 2GB every time. It drops back to ~100MB if I zoom out to a normal level. So I guess that much memory are used ...When I open a document the memory usage is normally ~100MB. But if I zoom in to the maximum level, the memory usage goes above 2GB every time. It drops back to ~100MB if I zoom out to a normal level. So I guess that much memory are used to render an extremely zoomed in pdf page. I can reproduce this with almost every pdf document.
zathura version is 0.4.7https://git.pwmt.org/pwmt/zathura/-/issues/195Poor print quality, in particular for .pdf documents2021-07-14T18:32:02+02:00Manfred SauterPoor print quality, in particular for .pdf documentsI noticed that when printing .pdf documents using zathura the quality of the printout is significantly worse than when printing directly using lpr. The outline of all characters is jagged and pixelated. There is nothing special about my ...I noticed that when printing .pdf documents using zathura the quality of the printout is significantly worse than when printing directly using lpr. The outline of all characters is jagged and pixelated. There is nothing special about my .pdf documents (mostly generated with LaTeX, correct page sizes, embedded Type 1 fonts). I am using the zathura-pdf-mupdf on Arch Linux.
Looking at the code of the plugin and zathura itself, however, I am not surprised the print quality is bad. In the corresponding source file print.c in the zathura repository apparently simply a hack is used to “Render to a surface that is 5 times larger to workaround quality issues.” Apparently this hack does not perform well enough in general. Potentially this affects also other document types and plugins.
So this issue is basically a feature request to implement proper calculation of the required rendering output sizes to obtain a specific printout resolution. I suggest to ensure a printout resolution of at least 300 dpi by default. Ideally the desired printout resolution should be configurable (maybe via config or the printing dialog).https://git.pwmt.org/pwmt/zathura/-/issues/190Recolor: White flicker while page is loading2021-02-10T09:22:31+01:004goettmaRecolor: White flicker while page is loadingHow to reproduce:
0. Use e.g. [zathura 0.4.6 | girara 0.3.5 (runtime: 0.3.5) | (plugin) pdf-poppler (0.3.0)]
1. activate recolor mode
2. scroll quickly through a large PDF / jump to different pages / rotate pages
Observed behaviour:
Th...How to reproduce:
0. Use e.g. [zathura 0.4.6 | girara 0.3.5 (runtime: 0.3.5) | (plugin) pdf-poppler (0.3.0)]
1. activate recolor mode
2. scroll quickly through a large PDF / jump to different pages / rotate pages
Observed behaviour:
The page sometimes gets loaded in normal mode before (fractions of a second) changing colors defined for the recolor mode ("turning dark")
Result:
Recolor mode is not nice to use when sitting in a dark lecture room since there a bright flashes from time to time (when using a light colored PDF).
Suggestion:
Fill page with recolor-darkcolor color as long as the page is loading, apply recolor color changes to the page, and subsequently render the page to the user.
EDIT: There seem to be documents where I can recreate this with ease and others where this doesn't occur at all. I will try to find and provide an example.https://git.pwmt.org/pwmt/zathura/-/issues/156Issue with large files2023-04-29T18:14:10+02:00Marcelo MontuIssue with large filesI'm having trouble opening a large pdf files, such as [i.MX 8DualXPlus/8QuadXPlus Applications Processor Reference Manual ](https://www.nxp.com/webapp/Download?colCode=IMX8DQXPRM&location=null).
The window opens but it is not rendered.
...I'm having trouble opening a large pdf files, such as [i.MX 8DualXPlus/8QuadXPlus Applications Processor Reference Manual ](https://www.nxp.com/webapp/Download?colCode=IMX8DQXPRM&location=null).
The window opens but it is not rendered.
I've tried on Ubuntu 18, both with the apt packages and building manually:
```
zathura 0.4.5
girara 0.3.4 (runtime: 0.3.4)
(plugin) ps (0.2.6) (/usr/local/lib/x86_64-linux-gnu/zathura/libps.so)
(plugin) pdf-mupdf (0.3.5) (/usr/local/lib/x86_64-linux-gnu/zathura/libpdf-mupdf.so)
```
I'm using mupdf-1.16.1 since it seems there is something missing for [mupdf-1.17.0](https://github.com/zegervdv/homebrew-zathura/issues/52).
I've followed the `GDK_NATIVE_WINDOWS` advice on the "Known Bugs" of man zathura, but it seems it isn't applicable with GTK 3:
```
(zathura:6309): Gdk-WARNING **: 16:47:34.728: The GDK_NATIVE_WINDOWS environment variable is not supported in GTK3.
See the documentation for gdk_window_ensure_native() on how to get native windows.
warning: undefined link destination
```https://git.pwmt.org/pwmt/zathura/-/issues/94Screen freezes after a few view adjustments2023-06-25T10:36:19+02:00Nícolas F. R. A. PradoScreen freezes after a few view adjustmentsSetting the auto adjustment mode to width (default keybinding 's') sometimes freezes the view. When frozen, subsequent view adjustments and zoom adjustments don't work, but the pages can still be scrolled, also the status bar doesn't upd...Setting the auto adjustment mode to width (default keybinding 's') sometimes freezes the view. When frozen, subsequent view adjustments and zoom adjustments don't work, but the pages can still be scrolled, also the status bar doesn't update. To get out of this frozen state, the screen needs to be resized or the workspace switched back and forth. From my testing, this issue only happens when setting the adjustment mode to width, never to best-fit. Also, it only happens when the page mode is set to a single page per row.
This issue happened for the following version, both from the ArchLinux package as well as compiling from source:
zathura 0.4.3
girara 0.3.2 (runtime: 0.3.2)
(plugin) pdf-poppler (0.2.9) (/usr/lib/zathura/libpdf-poppler.so)
I'm willing to fix it myself if I could get some pointers on what's causing it. The problem seems to be in the `adjust_view` function, but I haven't been successful in finding the problem.https://git.pwmt.org/pwmt/zathura/-/issues/57Place in document not saved when zathura closed by shutdown2023-10-02T18:38:29+02:00Dan GommePlace in document not saved when zathura closed by shutdownWhen Zathura is quit via the `q` shortcut, the next time that file is opened, it will be on the page last open in the previous session. However, if the computer is shut down, the file will open on the page last open when `q` was used to ...When Zathura is quit via the `q` shortcut, the next time that file is opened, it will be on the page last open in the previous session. However, if the computer is shut down, the file will open on the page last open when `q` was used to quit.
Example:
* Read `example.pdf` to page 123.
* Quit via pressing `q`.
* Open `example.pdf` in Zathura. It opens on page 123.
* Read further, to page 456.
* Shut down the machine.
* Open `example.pdf` in Zathura. It opens on page 123.
In the last instance, Zathura should open onto page 456. Zathura should have the same behaviour when shut down as when quitting via `q`, surely? Is this possible?https://git.pwmt.org/pwmt/zathura/-/issues/21Large document is not drawn correctly2023-04-29T18:13:17+02:00AnatolLarge document is not drawn correctlyI am trying to open a large PDF with zathura but all I see is black screen. I try to scroll up and down - status bar shows pages are changed, but it does not improve the screen issue.
I tried it at Arch and Ubuntu linux.
To reproduce t...I am trying to open a large PDF with zathura but all I see is black screen. I try to scroll up and down - status bar shows pages are changed, but it does not improve the screen issue.
I tried it at Arch and Ubuntu linux.
To reproduce the issue please download this Intel manual and try to open https://software.intel.com/en-us/download/intel-64-and-ia-32-architectures-sdm-combined-volumes-1-2a-2b-2c-2d-3a-3b-3c-3d-and-4