Bug#1128501: glycin-image-rs and glycin-svg keep streams open longer than necessary, causing the inability to unmount a prior working directory

tag 1128501 + moreinfo
reassign 1128501 glycin-loaders
thanks

Hi,

Am 20.02.26 um 16:55 schrieb Al Ma:
> Package: libreoffice-writer
> Version: 4:25.2.3-2+deb13u3
Uh, what?
> Control: affects -1 glycin-loaders
>
> This misbehavior started after we updated glycin and GDK Pixbuf recently. 
So it's a bug there? And why would anyone install unstables glygin/gd-pixbuf on stable anyway?
> As the user action was calling libreoffice on a DOCX document, I am filing this bug report against libreoffice-writer; the maintainer may reassign if necessary.
>
Just beause llibeoffice loads images? I don't think so. (And even then writer is just writer, image loading probably is -core)


> Reproduce:
>
> $ sshfs username@remote_host:/remote_directory ~/Remote

Oh, dear...

> $ sudo dpkg -l libreoffice-writer libgdk-pixbuf-2.0-0 glycin-loaders
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                      Version            Architecture Description
> +++-=========================-==================-============-===========================================
> ii  glycin-loaders            2.0.8-1            amd64 sandboxed image loaders for GNOME
> ii  libgdk-pixbuf-2.0-0:amd64 2.44.5+dfsg-4      amd64        GDK Pixbuf library
> ii  libreoffice-writer        4:25.2.3-2+deb13u3 amd64 office productivity suite -- word processor
Why are you installing unstables glycin on stable?
> Requested change: Close the streams to the current working directory when they are no longer required.

Rquested action: Don't install random packages from sid on stable and then blame stable.

In any case: Even if there was a bug in libreoffice noone will care about it in *stable* since the gdk-pixbuf there is not using glycin anyway.

If you insist that this is libreoffice at fault (which I don't think is) please at least try with testing or sids version.


Regards,


Rene