pwmt issueshttps://git.pwmt.org/groups/pwmt/-/issues2023-12-19T11:14:01+01:00https://git.pwmt.org/pwmt/zathura/-/issues/391Content gets cropped with a wrong center after moving the cursor out of zathura2023-12-19T11:14:01+01:00la .uetcis.Content gets cropped with a wrong center after moving the cursor out of zathuraDescription:
As the title, this bug can be stably reproduced on my platform by following these steps:
1. open a pdf file using zathura
2. copy something (the message panel pops up at the bottom)
3. move the cursor to another window
4. n...Description:
As the title, this bug can be stably reproduced on my platform by following these steps:
1. open a pdf file using zathura
2. copy something (the message panel pops up at the bottom)
3. move the cursor to another window
4. now the content is cropped, and all attempts to zoom are centered at the wrong position
Environment:
OS: Artix Linux
WM: Hyprland (Wayland)
Reproduction confirmed on commit e68c0f5f7f41c92bb3aca4204deb5e06dad185c0, though I'm pretty sure that this bug appeared earlier from last week in the release as this bug is discovered when I was using the packaged zathura release from Artix repo. If needed, I can try bisecting this when I have time.
A video of the reproduction of this bug can be downloaded from https://paste.fal.moe/RkHxTwjf.mp4https://git.pwmt.org/pwmt/zathura-pdf-mupdf/-/issues/26tesseract undefined symbol2023-12-13T10:37:02+01:00John Juttytesseract undefined symbolgirara, zathura and zathura-pdf-mupdf all compiledfrom develop branch:
```
$ LD_LIBRARY_PATH=/usr/local/lib64 zathura
error: Could not load plugin '/usr/local/lib64/zathura/libpdf-mupdf.so' (/usr/local/lib64/zathura/libpdf-mupdf.so: und...girara, zathura and zathura-pdf-mupdf all compiledfrom develop branch:
```
$ LD_LIBRARY_PATH=/usr/local/lib64 zathura
error: Could not load plugin '/usr/local/lib64/zathura/libpdf-mupdf.so' (/usr/local/lib64/zathura/libpdf-mupdf.so: undefined symbol: _ZTVN9tesseract14ResultIteratorE).
```https://git.pwmt.org/pwmt/zathura/-/issues/392Wrong page format for pdf documents with varying page formats2023-12-13T09:31:39+01:00Patrick KurthWrong page format for pdf documents with varying page formatsWhen viewing a pdf that contains pages with different formats (for instance one page is in landscape), pages with the "wrong" formats are not fully displayed (parts of them are cut off). It seems like all pages have the same display form...When viewing a pdf that contains pages with different formats (for instance one page is in landscape), pages with the "wrong" formats are not fully displayed (parts of them are cut off). It seems like all pages have the same display format as the first page, but I'm unsure on this.
OS: Arch Linux
Zathura Version (--version):
zathura 0.5.4
girara 0.4.1 (runtime: 0.4.1)
(plugin) pdf-mupdf (0.4.1) (/usr/lib/zathura/libpdf-mupdf.so)
(plugin) ps (0.2.7) (/usr/lib/zathura/libps.so)
This happened after upgrading, and down-grading solves this. Full version after down-grading:
zathura 0.5.2
girara 0.3.9 (runtime: 0.4.1)
(plugin) pdf-mupdf (0.4.1) (/usr/lib/zathura/libpdf-mupdf.so)
(plugin) ps (0.2.7) (/usr/lib/zathura/libps.so)
This issue also occurs with the latest git version (which is also 0.5.4, not sure if they differ).
Here is an example pdf that reproduces the issue:
[drawing.pdf](/uploads/5163f12ac117f1f8bc7af61e2f6a2d50/drawing.pdf)https://git.pwmt.org/pwmt/zathura/-/issues/390"warning: Failed to parse color string" with zathura 0.5.32023-12-10T13:47:47+01:00Robin Candau"warning: Failed to parse color string" with zathura 0.5.3Hello,
Zathura v0.5.3 (built with [these build/packaging instructions](https://gitlab.archlinux.org/archlinux/packaging/packages/zathura/-/blob/main/PKGBUILD?ref_type=heads) on an Arch Linux system) produces the following warning messag...Hello,
Zathura v0.5.3 (built with [these build/packaging instructions](https://gitlab.archlinux.org/archlinux/packaging/packages/zathura/-/blob/main/PKGBUILD?ref_type=heads) on an Arch Linux system) produces the following warning message at each usage:
```
warning: Failed to parse color string 'rgba(100%,%84,0%,0.9)'.
(org.pwmt.zathura:7247): Gtk-CRITICAL **: 18:19:17.954: gtk_event_controller_set_propagation_phase: assertion 'GTK_IS_EVENT_CONTROLLER (controller)' failed
```
Zathura v0.5.2 does not produce such warning.
Here is the output of `zathura --version` (thus including the warning):
```
$ zathura --version
warning: Failed to parse color string 'rgba(100%,%84,0%,0.9)'.
(org.pwmt.zathura:7247): Gtk-CRITICAL **: 18:19:17.954: gtk_event_controller_set_propagation_phase: assertion 'GTK_IS_EVENT_CONTROLLER (controller)' failed
zathura 0.5.3
girara 0.4.1 (runtime: 0.4.1)
(plugin) pdf-poppler (0.3.2) (/usr/lib/zathura/libpdf-poppler.so)
```
Build logs for the produced zathura v0.5.3 package are available [here](https://pkgbuild.com/~antiz/zathura-0.5.3-1-x86_64-build.log).
The resulted built packages for zathura v0.5.3 and girara v0.4.1 are also available [here](https://pkgbuild.com/~antiz/) and can be installed locally on an Arch based system for testing purposes if needed.
I remain available if you any additional information are required! :)https://git.pwmt.org/pwmt/zathura/-/issues/361How to map mouse button for panning the document?2023-12-10T07:19:07+01:00Peter BakerHow to map mouse button for panning the document?The default setting for panning the document is holding middle button and move the mouse around.
Can I map it to holding the mouse left button (or right button) in .zathurarc?The default setting for panning the document is holding middle button and move the mouse around.
Can I map it to holding the mouse left button (or right button) in .zathurarc?https://git.pwmt.org/pwmt/zathura/-/issues/387zathura hangs after invoking `print`2023-12-08T18:42:55+01:00Jan Paluszathura hangs after invoking `print`Noticed today that `:print` started to hang `zathura` entirely. No print dialog is shown, no CPU is used, `zathura` can only be killed. After some debugging it turns out to be a problem with default sandbox that explicitly disallows `vms...Noticed today that `:print` started to hang `zathura` entirely. No print dialog is shown, no CPU is used, `zathura` can only be killed. After some debugging it turns out to be a problem with default sandbox that explicitly disallows `vmsplice`.
In my particular setup I'm connecting to network `CUPS` printer over secure connection using `GnuTLS` configured to make use of `AF_ALG` kernel crypto API through `libkcapi` which in turn makes use of `vmsplice`:
https://github.com/smuellerDD/libkcapi/blob/0e3e2032a97c51697a5134ca6eabbd5708e9498a/lib/kcapi-kernel-if.c#L324https://git.pwmt.org/pwmt/zathura/-/issues/375Add $DBUS variable for exec2023-12-08T18:42:54+01:00blankieblankie@nixnetmail.comAdd $DBUS variable for execI'm writing a shell script that is invoked with the `exec` command in zathura which opens a PDF or EPub (by asking the user with a GUI file selection dialog). It seems like zathura can be remotely controlled with D-Bus, but there doesn't...I'm writing a shell script that is invoked with the `exec` command in zathura which opens a PDF or EPub (by asking the user with a GUI file selection dialog). It seems like zathura can be remotely controlled with D-Bus, but there doesn't appear to be a way to pass in the dbus name to the shell script (nor could I make one from the predictable format, as `$PPID` is 1).https://git.pwmt.org/pwmt/zathura/-/issues/355[FR] Expose index of the current document through dbus_interface.c2023-12-08T18:42:53+01:00Rodrigo Morales[FR] Expose index of the current document through dbus_interface.cExpose table of contents through dbus
By calling the functions defined in [dbus-interface.c](https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/dbus-interface.c), I have been able to write Elisp functions (please see below) in ord...Expose table of contents through dbus
By calling the functions defined in [dbus-interface.c](https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/dbus-interface.c), I have been able to write Elisp functions (please see below) in order to be able to reuse Zathura instances when opening Org Mode links of the form `[[file:<<filename>>#<<page number>>` (i.e. the same Zathura instance will be used if it is already opening the desired document.)
```elisp
(defun my/dbus-zathura-use-instance-or-open-new (file link)
"Launch zathura to open FILE or Reuse a running instance.
LINK is provided by Org Mode when this function has been
specified in `org-file-apps'. This function is intended to be
used in `org-file-apps' and shouldn't be called on its own."
(let* ((process-alist (proced-process-attributes))
(pids (mapcar 'car (proced-filter process-alist '((comm . "zathura")))))
(pid
(catch 'found
(cl-loop for pid in pids
when (equal
(dbus-get-property
:session
(concat "org.pwmt.zathura.PID-" (number-to-string pid))
"/org/pwmt/zathura"
"org.pwmt.zathura"
"filename")
file)
do (throw 'found pid))))
(page-number
(or
(progn
;; FIXME: According to the docstring of org-file-apps, we
;; can access capture groups using (match-string n
;; link). However, when I tried it, the capture groups
;; didn't have the entire content. For this reason, I'm
;; running string-match with the same regex that I used
;; in org-file-apps, but (match-string n link) should
;; work as specified in the Org Mode documentation.
(string-match "\\.\\(pdf\\|djvu\\)::\\([0-9]+\\)\\'" link)
(match-string 2 link))
"1")))
(if pid
;; Jump to that page in the existing instance
(dbus-call-method
:session
(concat "org.pwmt.zathura.PID-" (number-to-string pid))
"/org/pwmt/zathura"
"org.pwmt.zathura"
"GotoPage"
(1- (string-to-number page-number)))
;; Open a new instance
(make-process
:name "zathura"
:buffer nil
:command `("zathura" "--page" ,page-number ,file)))))
```
```elisp
(setq org-file-apps
'((auto-mode . emacs)
(directory . emacs)
("\\.png\\'" . "mpv %s")
("\\.\\(pdf\\|djvu\\)" . my/dbus-zathura-use-instance-or-open-new)
("\\.\\(pdf\\|djvu\\)::\\([0-9]+\\)\\'" . my/dbus-zathura-use-instance-or-open-new)))
```
Now, I would like to create a function for Emacs which prompts for an item in the table of contents of the document and jumps to that specific page. Currently, [dbus-interface.c](https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/dbus-interface.c) expose the page number and the filename and it provides an interface for jumping to an specific page (interface which I used in my Elisp function shown above). However, the table of contents from the current document is not exposed. Therefore, I propose that the index of the document is exposed in some way.
This feature will not only benefit Emacs users but also users of any completion framework (e.g. rofi, dmenu, fzf, vim, etc), since such specialized completion frameworks have more features available (e.g. regex search, movement with operators, fuzzy finding) which, I believe, might require significant effort to incorporate in the zathura index viewer.https://git.pwmt.org/pwmt/zathura/-/issues/365[Feature Request] Sending a USR2 signal would cause :source2023-12-08T18:42:52+01:00Nima Askarian[Feature Request] Sending a USR2 signal would cause :sourceSending a USR2 or USR1 signal to zathura (`pkill -USR2 zathura`/`pkill -USR1 zathura`) would cause program to do `:source` command. I use pywal for color generation, and I open a lot of pdfs at a same time. It would be nice if I didn't n...Sending a USR2 or USR1 signal to zathura (`pkill -USR2 zathura`/`pkill -USR1 zathura`) would cause program to do `:source` command. I use pywal for color generation, and I open a lot of pdfs at a same time. It would be nice if I didn't need to hit my `:source` keymap every time, but instead send a USR2/USR1 signal inside my bash script.https://git.pwmt.org/pwmt/zathura/-/issues/328"$PAGE" string in file name get replaced with the page number in `:exec` command2023-12-08T18:42:50+01:00user202729"$PAGE" string in file name get replaced with the page number in `:exec` commandAs mentioned in the title, if some file has name for example `1$PAGE3.pdf` then `exec some-command $FILE` will pass `123.pdf` to `some-command`.
Side note, I think the issue is with https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathu...As mentioned in the title, if some file has name for example `1$PAGE3.pdf` then `exec some-command $FILE` will pass `123.pdf` to `some-command`.
Side note, I think the issue is with https://git.pwmt.org/pwmt/zathura/-/blob/develop/zathura/commands.c#L559 which replaces `$FILE` before replacing `$PAGE`. Reversing the replacement order would fix the issue.https://git.pwmt.org/pwmt/zathura/-/issues/38Backspace over the first digit typed to follow a link exits the number insert...2023-12-04T23:03:13+01:00Enrico Maria De AngelisBackspace over the first digit typed to follow a link exits the number insertion but still draws numeric hintsTo reproduce the behavior
- hit <kbd>f</kbd> in normal mode (so that the hints for the various links show up),
- hit a single digit, _e.g._ <kbd>1</kbd>,
- hit <kbd>Backspace</kbd>.
Now you are in normal mode *and* the hints are still ...To reproduce the behavior
- hit <kbd>f</kbd> in normal mode (so that the hints for the various links show up),
- hit a single digit, _e.g._ <kbd>1</kbd>,
- hit <kbd>Backspace</kbd>.
Now you are in normal mode *and* the hints are still shown.
Imho the behavior is inconsistent. At least we should be either in
- normal mode **without** the hints shown,
- "follow link"-mode **with** the hints shown.
I'd rather prefer the latter, actually.https://git.pwmt.org/pwmt/zathura/-/issues/384Option to display epub pages continously2023-12-03T13:15:31+01:00a bOption to display epub pages continouslyIs there a way to remove the margin/gap between epub pages? There should be an option to display them in a continuous/gapless way. Setting `page-padding` to `0` doesn't remove this effect, unfortunately.
![image](/uploads/e17b3c9132bf19...Is there a way to remove the margin/gap between epub pages? There should be an option to display them in a continuous/gapless way. Setting `page-padding` to `0` doesn't remove this effect, unfortunately.
![image](/uploads/e17b3c9132bf196941142d2dd7e2b38e/image.png)https://git.pwmt.org/pwmt/zathura/-/issues/278Trouble with exec mapped to mouse button2023-11-07T00:38:48+01:00Hugo RaguetTrouble with exec mapped to mouse buttonI experience troubles when trying to map mouse buttons to exec commands.
`map <C-l> exec ls` works like expected, but after `map <Button3> exec ls` a click with Button 3 of the mouse spawns a process which fails with
Failed to execu...I experience troubles when trying to map mouse buttons to exec commands.
`map <C-l> exec ls` works like expected, but after `map <Button3> exec ls` a click with Button 3 of the mouse spawns a process which fails with
Failed to execute command: Failed to execute child process “/shorttitle” (No
such file or directory)
Note that in the above `/shorttitle` seems to be some random gibberish that might depend on the content of the currently open document.https://git.pwmt.org/pwmt/zathura/-/issues/386Highlight current index in Index Mode2023-11-03T17:04:55+01:00a bHighlight current index in Index ModeIn Index Mode, it'd be nice if the index that the currently open page belongs to is automatically highlighted/updated.In Index Mode, it'd be nice if the index that the currently open page belongs to is automatically highlighted/updated.https://git.pwmt.org/pwmt/zathura/-/issues/148[Feature Request] Smooth scrolling2023-11-02T15:06:47+01:00sheep[Feature Request] Smooth scrollingSmooth scrolling can be enabled for a touchpad, but keybindings ^d, ^u, j and k are unaffected by this change. Would be nice if there were a similar property for them too.
You can do something similar with first pressing `g` and then sc...Smooth scrolling can be enabled for a touchpad, but keybindings ^d, ^u, j and k are unaffected by this change. Would be nice if there were a similar property for them too.
You can do something similar with first pressing `g` and then scrolling with PageUp, PageDown, but it feels hacky, feels too fast and you can't use it for scrolling half a page.https://git.pwmt.org/pwmt/zathura/-/issues/370Document / Improve smooth scrolling2023-11-02T15:06:46+01:00Ignacio TarantoDocument / Improve smooth scrollingCurrently, pressing `j` or `k` doesn't do smooth scrolling. Weirdly, `^Down` and `^Up` does.
Why is that?
Is there a way to enable smooth scrolling with `j` and `k` or even `^d` or `^u`?Currently, pressing `j` or `k` doesn't do smooth scrolling. Weirdly, `^Down` and `^Up` does.
Why is that?
Is there a way to enable smooth scrolling with `j` and `k` or even `^d` or `^u`?https://git.pwmt.org/pwmt/zathura/-/issues/382Option to display page thumbnail in place of the "Loading..." text2023-10-22T11:17:42+02:00blankieblankie@nixnetmail.comOption to display page thumbnail in place of the "Loading..." textWhen scrolling a document with a lot of empty space, I tend to go a page past a piece of content, since I would scroll past a page (and ignore the "Loading..." text since the document has a lot of blank space). A quick thumbnail would le...When scrolling a document with a lot of empty space, I tend to go a page past a piece of content, since I would scroll past a page (and ignore the "Loading..." text since the document has a lot of blank space). A quick thumbnail would let me know if a page has content (so I can wait for it to load) or nothing (so I know to scroll past).https://git.pwmt.org/pwmt/zathura-pdf-mupdf/-/issues/40zathura crashes when :info is run on a non-PDF document (such as an EPUB)2023-10-22T10:54:52+02:00blankieblankie@nixnetmail.comzathura crashes when :info is run on a non-PDF document (such as an EPUB)https://git.pwmt.org/pwmt/zathura/-/issues/351Segfault when quitting quickly after zooming.2023-10-17T12:37:14+02:00Jonas DujavaSegfault when quitting quickly after zooming.Trying to **_quit immediately after zooming_** sometimes leads to `segmentation fault`.
Happens reproducibly on **scans** or highly **annotated pdfs**, in particular when focusing after the zoom takes a while.
Leaves for example the fo...Trying to **_quit immediately after zooming_** sometimes leads to `segmentation fault`.
Happens reproducibly on **scans** or highly **annotated pdfs**, in particular when focusing after the zoom takes a while.
Leaves for example the following `Stack trace`:
```
systemd-coredump[13801]: Process 13764 (zathura) of user 1000 dumped core.
Stack trace of thread 13785:
#0 0x00007fd9f4dbe170 n/a (n/a + 0x0)
#1 0x00007fda0ab5f18f _ZN3Gfx2goEb (libpoppler.so.126 + 0x15f18f)
#2 0x00007fda0ab5fc37 _ZN3Gfx7displayEP6Objectb (libpoppler.so.126 + 0x15fc37)
#3 0x00007fda0ab70a0f _ZN3Gfx8drawFormEP6ObjectP4DictPKdS5_bbP13GfxColorSpacebbbP8FunctionP8GfxColor (libpoppler.so.126 + 0x170a0f)
#4 0x00007fda0ab710da _ZN3Gfx6doFormEP6Object (libpoppler.so.126 + 0x1710da)
#5 0x00007fda0ab743b8 _ZN3Gfx9opXObjectEP6Objecti (libpoppler.so.126 + 0x1743b8)
#6 0x00007fda0ab5f18f _ZN3Gfx2goEb (libpoppler.so.126 + 0x15f18f)
#7 0x00007fda0ab5fc37 _ZN3Gfx7displayEP6Objectb (libpoppler.so.126 + 0x15fc37)
#8 0x00007fda0abced92 _ZN4Page12displaySliceEP9OutputDevddibbiiiibPFbPvES2_PFbP5AnnotS2_ES2_b (libpoppler.so.126 + 0x1ced92)
#9 0x00007fda0c9671f2 n/a (libpoppler-glib.so.8 + 0x2d1f2)
#10 0x00007fda0cd36996 n/a (libpdf-poppler.so + 0x2996)
#11 0x00005575bba30902 n/a (zathura + 0x2e902)
#12 0x00007fda103709a3 n/a (libglib-2.0.so.0 + 0x8c9a3)
#13 0x00007fda1036b315 n/a (libglib-2.0.so.0 + 0x87315)
#14 0x00007fda0ffccbb5 n/a (libc.so.6 + 0x85bb5)
#15 0x00007fda1004ed90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 13764:
#0 0x00007fda0ffc993b __lll_lock_wait_private (libc.so.6 + 0x8293b)
#1 0x00007fda0ffda850 n/a (libc.so.6 + 0x93850)
#2 0x00007fda0ffdce63 __libc_free (libc.so.6 + 0x95e63)
#3 0x00007fda0abc1e97 _ZN6Object4freeEv (libpoppler.so.126 + 0x1c1e97)
#4 0x00007fda0abc1e5a _ZN6Object4freeEv (libpoppler.so.126 + 0x1c1e5a)
#5 0x00007fda0abfddd8 n/a (libpoppler.so.126 + 0x1fddd8)
#6 0x00007fda0abfe041 _ZN4XRefD1Ev (libpoppler.so.126 + 0x1fe041)
#7 0x00007fda0abd1878 _ZN6PDFDocD1Ev (libpoppler.so.126 + 0x1d1878)
#8 0x00007fda0c95b760 n/a (libpoppler-glib.so.8 + 0x21760)
#9 0x00007fda104514a4 g_object_unref (libgobject-2.0.so.0 + 0x224a4)
#10 0x00007fda0cd3645b n/a (libpdf-poppler.so + 0x245b)
#11 0x00005575bba16d87 zathura_document_free (zathura + 0x14d87)
#12 0x00005575bba1b38b n/a (zathura + 0x1938b)
#13 0x00005575bba1b46f n/a (zathura + 0x1946f)
#14 0x00005575bba0eebc main (zathura + 0xcebc)
#15 0x00007fda0ff6a790 n/a (libc.so.6 + 0x23790)
#16 0x00007fda0ff6a84a __libc_start_main (libc.so.6 + 0x2384a)
#17 0x00005575bba0f615 _start (zathura + 0xd615)
Stack trace of thread 13771:
#0 0x00007fda100470dd syscall (libc.so.6 + 0x1000dd)
#1 0x00007fda103947b5 g_cond_wait (libglib-2.0.so.0 + 0xb07b5)
#2 0x00007fda10308fb4 n/a (libglib-2.0.so.0 + 0x24fb4)
#3 0x00007fda1036ff9e n/a (libglib-2.0.so.0 + 0x8bf9e)
#4 0x00007fda1036b315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fda0ffccbb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007fda1004ed90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 13770:
#0 0x00007fda100419df __poll (libc.so.6 + 0xfa9df)
#1 0x00007fda1039b17f n/a (libglib-2.0.so.0 + 0xb717f)
#2 0x00007fda1033d1a2 g_main_context_iteration (libglib-2.0.so.0 + 0x591a2)
#3 0x00007fda1033d1f2 n/a (libglib-2.0.so.0 + 0x591f2)
#4 0x00007fda1036b315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fda0ffccbb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007fda1004ed90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 13772:
#0 0x00007fda100470dd syscall (libc.so.6 + 0x1000dd)
#1 0x00007fda10394d03 g_cond_wait_until (libglib-2.0.so.0 + 0xb0d03)
#2 0x00007fda10308f83 n/a (libglib-2.0.so.0 + 0x24f83)
#3 0x00007fda10309127 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x25127)
#4 0x00007fda10370846 n/a (libglib-2.0.so.0 + 0x8c846)
#5 0x00007fda1036b315 n/a (libglib-2.0.so.0 + 0x87315)
#6 0x00007fda0ffccbb5 n/a (libc.so.6 + 0x85bb5)
#7 0x00007fda1004ed90 n/a (libc.so.6 + 0x107d90)
Stack trace of thread 13780:
#0 0x00007fda100419df __poll (libc.so.6 + 0xfa9df)
#1 0x00007fda1039b17f n/a (libglib-2.0.so.0 + 0xb717f)
#2 0x00007fda1033dc7f g_main_loop_run (libglib-2.0.so.0 + 0x59c7f)
#3 0x00007fda1059ed5c n/a (libgio-2.0.so.0 + 0x10ed5c)
#4 0x00007fda1036b315 n/a (libglib-2.0.so.0 + 0x87315)
#5 0x00007fda0ffccbb5 n/a (libc.so.6 + 0x85bb5)
#6 0x00007fda1004ed90 n/a (libc.so.6 + 0x107d90)
ELF object binary architecture: AMD x86-64
systemd[1]: Started Process Core Dump (PID 13800/UID 0).
kernel: Code: 00 00 80 f0 ff ff ff ff ff ff 40 1c 00 00 00 00 00 00 80 09 00 00 00 00 00 00 d0 a8 8d f6 d9 7f 00 00 a1 05 00 00 00 00 00 00 <00> 9d 84 f4 d9 7f 00 00 e0 59 7c f6 d9 7f 00 00 00 00 00 00 00 00
kernel: pool-org.pwmt.z[13785]: segfault at 7fd9f4dbe170 ip 00007fd9f4dbe170 sp 00007fda01dfcd48 error 15 likely on CPU 7 (core 3, socket 0)
```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?