On Wed, 13 Aug 2025 22:14:19 -0400 "Andrew J. Buehler" <[email protected]> wrote:
>On 2025-08-13 at 12:19, Andreas Rönnquist wrote: > >> On Wed, 13 Aug 2025 11:53:29 -0400 "Andrew J. Buehler" >> <[email protected]> wrote: > >> Thanks for your report - however, I cannot reproduce this. I have >> 2.5-8 running fine on three machines, two Trixie and one Sid - >> running ldd and grepping for libx265 on all those three gives >> >>> libx265.so.215 => /lib/x86_64-linux-gnu/libx265.so.215 >>> (0x00007fc727c00000) >> >> so I suspect this is something on your side. Can anybody else >> reproduce this? If not, I'll close it as unreproducible, but I'll >> give it some time of course. > >I would be *entirely* willing to go along with an answer which has this >caused by something on my side, but I have no idea what it might be, or >how to fix it. > --------------------- 8< --------------------- > >And just for good measure: > >$ ls -l /usr/bin/geeqie /var/cache/apt/archives/geeqie_1%3a2.5-8_amd64.deb >-rwxr-xr-x 1 root root 2566504 Jul 6 06:30 /usr/bin/geeqie >-rw-r--r-- 1 root root 1050604 Jul 7 08:52 >/var/cache/apt/archives/geeqie_1%3a2.5-8_amd64.deb > >I'm reasonably confident that I'm running geeqie from the Debian >package. AFAIK I've never even tried to install it from anywhere else. >I've also done 'locate geeqie', and the only results either look >plausible to be from the package (I haven't *explicitly* checked the >package's file-list for comparison) or are about >~/.{cache,config,local/share}/geeqie . > >This is not my first rodeo, but it does seem to be the first one where >I've hit this particular ride, so to speak. > I'm kind of more interested in where you got libx265-209 from, since it doesn't look like it comes from the Debian package. If it does, updating a trixie should probably give you lib265-215. What does sudo "apt show libx265-209" give? /Andreas
