[Bug 263697] x11/xscreensaver libglade-WARNING
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 01 May 2022 05:54:46 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263697 Bug ID: 263697 Summary: x11/xscreensaver libglade-WARNING Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: zeising@FreeBSD.org Reporter: inbox@alleghenycomputer.com Flags: maintainer-feedback?(zeising@FreeBSD.org) Assignee: zeising@FreeBSD.org The latest version of xscreensaver (5.44_3) is throwing an error when glslideshow is selected (perhaps other screen saver selections as well). It still shows an image, but quickly shows a text error over top the image. I ran xscreensaver-demo from the cmd line to capture the exact wording: (xscreensaver-demo:6695): libglade-WARNING **: 01:19:04.554: Could not load sume.so" not found, required by "xscreensaver-demo" "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783. "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783. "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783. ^[[29~"my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783. "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783 "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783 "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 783 "my" variable $uri masks earlier declaration in same scope at /usr/local/lib/perl5/site_perl/LWP/UserAgent.pm line 78 I am not sure if this is a problem with libglade or xscreensaver as they were updated in ports on the same day (4/10/2022). I am running 13.0-RELEASE-p11 64-bit on about 12 different workstations and it's happening on all of them. Any ideas, thoughts, etc. would be greatly appreciated. -- You are receiving this mail because: You are the assignee for the bug.