[Bug 2065234] Re: can't unlock and xfce4-screensaver-dialog segfaults if weston running
I discovered that invoking weston as `weston --socket=something` prevents the segfaults. But perhaps there should be some code in the screensaver to detect this problem and prevent the crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065234 Title: can't unlock and xfce4-screensaver-dialog segfaults if weston running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-screensaver/+bug/2065234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065234] [NEW] can't unlock and xfce4-screensaver-dialog segfaults if weston running
Public bug reported: laptop running xubuntu 22.04.4, logged into xubuntu session. xfce4-screensaver 4.16.0-1 weston 9.0.0-4ubuntu1 firefox 125.0.3-1 (snap) Run firefox. In terminal: tail -f /var/log/syslog In another terminal: weston Lock the screen by hotkey calling: xflock4 Press key to bring up dialog but only black shows - can see backlight periodically turning on/off and flashes of cursor when pressing keys. Ctrl-Alt-F1; login; pkill weston; Alt-F7 back to locked session. Now unlocking works normally again. However, after unlocking, many firefox empty windows have been created. /var/log/syslog shows new output: May 9 02:02:55 hostname kernel: [387457.737377] xfce4-screensav[355062]: segfault at 7fda0084 ip 7fdac936052f sp 7ffd6783c1a0 error 4 in libgdk-3.so.0.2404.29[7fdac9324000+83000] May 9 02:02:55 hostname kernel: [387457.737387] Code: 57 82 fc ff 49 8b 9c 24 70 01 00 00 48 85 db 74 4e 49 89 c5 eb 0a 0f 1f 44 00 00 48 85 db 74 3f 48 8b 2b 48 89 de 48 8b 5b 08 <48> 8b 45 08 48 85 c0 74 e8 4c 39 e8 7f e3 49 8b bc 24 70 01 00 00 May 9 02:02:55 hostname xfce4-screensav[2995]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed May 9 02:02:57 hostname kernel: [387459.627666] xfce4-screensav[355067]: segfault at 2580418 ip 559c184c2e59 sp 7ffc0b3c1370 error 4 in xfce4-screensaver-dialog[559c184be000+e000] May 9 02:02:57 hostname kernel: [387459.627676] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff May 9 02:03:01 hostname kernel: [387464.025803] xfce4-screensav[355081]: segfault at 2580418 ip 5646542f7e59 sp 7ffeed5fe800 error 4 in xfce4-screensaver-dialog[5646542f3000+e000] May 9 02:03:01 hostname kernel: [387464.025813] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff May 9 02:03:03 hostname kernel: [387466.135825] xfce4-screensav[355094]: segfault at 2580418 ip 557eccebee59 sp 7ffc5a202b10 error 4 in xfce4-screensaver-dialog[557ecceba000+e000] May 9 02:03:03 hostname kernel: [387466.135837] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff May 9 02:03:07 hostname kernel: [387469.786031] xfce4-screensav[355107]: segfault at 2580418 ip 5627b214be59 sp 7ffc56cbb780 error 4 in xfce4-screensaver-dialog[5627b2147000+e000] May 9 02:03:07 hostname kernel: [387469.786041] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff May 9 02:03:08 hostname kernel: [387471.125899] xfce4-screensav[355120]: segfault at 2580418 ip 558dad3b5e59 sp 7fff8de7d090 error 4 in xfce4-screensaver-dialog[558dad3b1000+e000] May 9 02:03:08 hostname kernel: [387471.125909] Code: 48 8d 74 24 30 4c 89 e7 e8 c4 cb ff ff 8b 4c 24 38 44 8b 44 24 3c 4c 89 ef 89 4c 24 1c 44 89 44 24 10 e8 7a dc ff ff 4c 89 ef <44> 8b 60 18 e8 6e dc ff ff 44 8b 4c 24 08 44 8b 44 24 10 4c 89 ff May 9 02:03:09 hostname wireplumber[2810]: [string "policy-bluetooth.lua"]:121: bad argument #1 to 'find' (string expected, got nil)#012stack traceback:#012#011[C]: in function 'string.find'#012#011[string "policy-bluetooth.lua"]:121: in upvalue 'isBluez5AudioSink'#012#011[string "policy-bluetooth.lua"]:389: in function <[string "policy-bluetooth.lua"]:387> May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.firefox-caf74e0d-aff8-419d-9e3c-44aabb8abacb.scope. May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.firefox-254eb60d-01c9-4a44-9558-825d8954d937.scope. May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.firefox-0cb163b8-0ef8-4e3c-94e7-8cfc3f1873b0.scope. May 9 02:03:09 hostname systemd[2801]: Started snap.firefox.firefox-56b82216-0fe6-4bc2-afee-c1ebb971e98a.scope. May 9 02:03:10 hostname systemd[2801]: Started snap.firefox.firefox-ccecdc0f-7743-4791-bd4a-f53a4e64b9ff.scope. May 9 02:03:13 hostname wireplumber[2810]: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed? May 9 02:03:13 hostname wireplumber[2810]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported. May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.firefox-8702c3ef-c11f-4c45-bb50-0a3873dd084c.scope. May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.firefox-8c3507de-27d0-4af8-88cc-c5ce8bb6438c.scope. May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.firefox-d43f024e-731a-4b55-ba1b-5ce97f58c116.scope. May 9 02:03:14 hostname systemd[2801]: Started snap.firefox.firefox-a6dce45f-
[Bug 1308439] Re: add --version argument
version option was added in 2.19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308439 Title: add --version argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findimagedupes/+bug/1308439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308439] Re: add --version argument
Sorry, I just saw this as I don't monitor bug trackers. I'm the author. I'm happy to add this option when I next update the program. -jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308439 Title: add --version argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findimagedupes/+bug/1308439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 502224] Re: findimagedupes should be parallelizable
Sorry, I just saw this as I don't monitor bug trackers. I'm the author. This is a good idea but the code would need to be refactored. I'll have a think. -jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/502224 Title: findimagedupes should be parallelizable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findimagedupes/+bug/502224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079788] Re: findimagedupes should honor bash IFS in its output
Hi, I am the author. Thank you for the suggestion.
It is not necessary to patch the code to do what you want.
The output is generated by running a shell script (which can be viewed with -s).
By default, the function VIEW simply does 'echo "$@";'. This can be overridden
by -i/-I.
So, you could accomplish your aim by something like, for example:
findimagedupes -i 'export IFS=":"' -i 'VIEW(){ echo "$*"; }' --
*.jpg
Note that the script should correctly escape filenames even without
this:
findimagedupes -s scriptfile --- *.jpg
more scriptfile
-jonathan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079788
Title:
findimagedupes should honor bash IFS in its output
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findimagedupes/+bug/1079788/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751403] [NEW] geometry no longer matches X(7) spec
Public bug reported: Ubuntu 17.10 xfce4-terminal 0.8.6-0ubuntu1 amd64 This command no longer behave correctly: xfce4-terminal --geometry=80x25-170-40 Expected: Per X(7), this should create a window whose lower right corner is located 170 pixels left of and 40 pixels up from the bottom right corner of the screen. What happens: Entering the example geom spec is incorrectly treated as if it were: 80x25-0-0 xterm / lxterm / uxterm work in the expected manner using: -geometry 80x25-170-40 ** Affects: xfce4-terminal (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 17.10 xfce4-terminal 0.8.6-0ubuntu1 amd64 - - This command no longer behave correctly: xfce4-terminal --geometry=80x25-170-40 + This command no longer behave correctly: + xfce4-terminal --geometry=80x25-170-40 Expected: Per X(7), this should create a window whose lower right corner is located 170 pixels left of and 40 pixels up from the bottom right corner of the screen. What happens: - Entering the example geom spec is incorrectly treated as if it were: 80x25-0-0 + Entering the example geom spec is incorrectly treated as if it were: + 80x25-0-0 - - xterm / lxterm / uxterm work in the expected manner using: -geometry 80x25-170-40 + xterm / lxterm / uxterm work in the expected manner using: + -geometry 80x25-170-40 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751403 Title: geometry no longer matches X(7) spec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/1751403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
