On Wed, Feb 25, 2026 at 12:13:52PM +0100, intrigeri wrote: > - With Evince 49 (currently in sid), AFAICT the only problems this > bug causes are:
I believe the main problem is that thumbnails are not saved/cached but instead regenerated on every launch - which is both I/O + CPU intensive, and also makes for a poor experience (I see a placeholder image on all thumbnails, until all thumbnails are regenerated). Note that in contrast to Simon, for me this happens on every run, for every thumbnail. I don't need to clear old thumbnails for the issue to manifest. Even after an "aa-complain; evince; aa-enforce; evince" cycle this is still present and very much a visible difference between the two runs. > - This bug being RC and marked as affecting all current versions > means apt-listbugs currently discourages some users from upgrading > from a crashing version (48.1) to a working version (49). > I can't see how this helps anyone. I'm not familiar at all with how apt-listbugs operates :) Given it's the same bug as the 48.1 crash, and marked in the BTS as affecting both 48.1 and 49, my guess would have been that it would not consider it a regression... If it isn't, you're right, that's not helpful at all! > > but I'll let someone more involved with evince maintenance make > > that decision. > > Same here. Same here. I downgraded from grave, but I felt it is too much of a regression to be "just" important. It also felt to me like the original crashing bug was "accidentally" fixed with 49, rather than addressing it at its root cause (= the glycin+AppArmor incompatibility), so it felt wrong to me to ignore it just because the most obvious crashes were gone. I don't have a strong opinion, though. Regards, Faidon
