Hello Gianluca, Can you explain how to reproduce this issue? Also, did this happen after a particular package upgrade, or is this happening ever since the Debian Bullseye initial release? Cheers! Sylvain Beucler Debian LTS Team
Hello Gianluca, I can't reproduce this. I can open the print dialog just fine in bullseye. Since this happens in "libproxy", do you have a specific HTTP Proxy configuration? Cheers! Sylvain Beucler Debian LTS Team
In the beginning all worked perfectly. Two months ago, I tried to print something after a long time, and before the printer's selection dialog appears the application crash. All other pdf tools work fine. Il ven 11 apr 2025, 18:13 Sylvain Beucler <beuc@beuc.net> ha scritto:
I tried a complete reinstall of libproxy but nothing changed. I tried to remove all printers, and reinstall one printer at time but with no luck Il sab 12 apr 2025, 18:15 Gianluca Renzi <icjtqr@gmail.com> ha scritto:
Hi, I found a similar report at: https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/-/issues/151 but it's inconclusive. I still can't reproduce the problem so I can't really help you debug this issue. If you can determine what packages updates might have introduced it, we can look further into it. Cheers! Sylvain Beucler Debian LTS Team
It should be great if I can reproduce the core-dump so it can be useful as post mortem debug. Do you know how to do this? Il mer 16 apr 2025, 15:28 Sylvain Beucler <beuc@beuc.net> ha scritto:
If the crash is happening every time you open the print dialog, then it is reproducible for you. What Sylvain means is that it doesn´t happen for him, which means that it's not reproducible for him, and he may need extra steps or a different setup for it to happen. That's the information he's lacking at the moment. Something that you can do is to run atril under gdb and get a backtrace after the crash (assertion) happens. That may help diagnose the issue. Cheers, Emilio
Thanks for the tip! I thought the gdb post mortem be available only when compiled with debug option. Il mer 16 apr 2025, 17:13 Emilio Pozuelo Monfort <pochu@debian.org> ha scritto:
We finally figured out what causes this. Please let me know if removing libproxy1-plugin-networkmanager does not fix the issue. cu Adrian