Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#77905 - [xfce4-screenshooter] Does not start with libsoup 3.4.0
Attached to Project:
Arch Linux
Opened by Thomas Schuetz (Murray_B) - Sunday, 19 March 2023, 08:31 GMT
Last edited by Toolybird (Toolybird) - Sunday, 19 March 2023, 21:34 GMT
Opened by Thomas Schuetz (Murray_B) - Sunday, 19 March 2023, 08:31 GMT
Last edited by Toolybird (Toolybird) - Sunday, 19 March 2023, 21:34 GMT
|
DetailsDescription:
Well, it just does not start at all. Recompile the package with the new libsoup does not help, I get the same error, the symbol is missing. Downgrading to libsoup3-3.2.2-1 solves the problem Additional info: * package version(s) libsoup3-3.4.0-1 xfce4-screenshooter 1.10.3-1 * config and/or log files etc. Console output: xfce4-screenshooter: symbol lookup error: /usr/lib/libsoup-3.0.so.0: undefined symbol: g_task_set_static_name * link to upstream bug report, if any No upstream error found Steps to reproduce: Commandline (with up-to-date system): xfce4-screenshooter |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 19 March 2023, 21:34 GMT
Reason for closing: Not a bug
Additional comments about closing: Partial updates are not supported.
Sunday, 19 March 2023, 21:34 GMT
Reason for closing: Not a bug
Additional comments about closing: Partial updates are not supported.
00000000000ab4c0 T g_task_set_static_name
So I guess this task could be closed, if I update glib2 the problems with the screenshooter are gone. Okay, but now I have the problems with the screenlock again… Maybe I should switch to another
windowmanager until the stuff got fixed.