Your message dated Mon, 08 Nov 2021 20:35:33 +0000 with message-id <[email protected]> and subject line Bug#998837: fixed in gnome-flashback 3.42.0-2 has caused the Debian Bug report #998837, regarding gnome-flashback: GNOME Flashback segfaults at login to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 998837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998837 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-flashback Version: 3.42.0-1 Severity: important Dear Maintainer, After updating gnome-flashback today, I am unable to login to the "GNOME Flashback (Metacity)" sesson - I immediately get the "Oh no, an error occured, please log out" screen. Poking around in `journalctl --user` I discovered the following entry at the time of my login attempt: gnome-flashback.service: Main process exited, code=killed, status=11/SEGV After installing systemd-coredump, I managed to extract a backtrace: #0 gf_logical_monitor_configs_have_monitor (logical_monitor_configs=logical_monitor_configs@entry=0x55ec78aeb020 = {...}, monitor_spec=monitor_spec@entry=0x55ec78ad1f50) at ./backends/gf-logical-monitor-config.c:56 #1 0x000055ec77c8bd48 in gf_monitors_config_new (monitor_manager=monitor_manager@entry=0x7fa438003d70, logical_monitor_configs=logical_monitor_configs@entry=0x55ec78aeb020 = {...}, layout_mode=layout_mode@entry=GF_LOGICAL_MONITOR_LAYOUT_MODE_PHYSICAL, flags=flags@entry=GF_MONITORS_CONFIG_FLAG_NONE) at ./backends/gf-monitors- config.c:179 #2 0x000055ec77c934a6 in create_monitors_config (match_rule=<optimized out>, positioning=MONITOR_POSITIONING_LINEAR, config_flags=GF_MONITORS_CONFIG_FLAG_NONE, config_manager=<optimized out>, config_manager=<optimized out>) at ./backends/gf-monitor-config-manager.c:603 #3 0x000055ec77c8643b in gf_monitor_manager_ensure_configured (manager=manager@entry=0x7fa438003d70) at ./backends/gf-monitor-manager.c:2786 #4 0x000055ec77c98d79 in gf_monitor_manager_xrandr_ensure_initial_config (manager=0x7fa438003d70) at ./backends/gf-monitor-manager-xrandr.c:699 #5 0x000055ec77c85ce7 in gf_monitor_manager_setup (manager=0x7fa438003d70) at ./backends/gf-monitor-manager.c:2477 #6 0x000055ec77c841c3 in gf_backend_new (type=type@entry=GF_BACKEND_TYPE_X11_CM) at ./backends/gf-backend.c:377 #7 0x000055ec77c823e0 in gf_application_init (application=0x55ec78ae4550) at ./gnome-flashback/gf-application.c:328 Looking at the code of gf_logical_monitor_configs_have_monitor(), it takes a list of GfLogicalMonitorConfig, and the first one in the list looks like: (gdb) print *((GfLogicalMonitorConfig *)l->data) $5 = {layout = {x = 3, y = 0, width = 0, height = 0}, monitor_configs = 0xe000100000000 = {<error reading variable> ...which seems very suspicious to me. The second one in the list looks like: (gdb) print *((GfLogicalMonitorConfig *)logical_monitor_configs->next->data) $9 = {layout = {x = 0, y = 0, width = 1920, height = 1080}, monitor_configs = 0x55ec78b1ac60 = {0x55ec78b1f020}, transform = GF_MONITOR_TRANSFORM_NORMAL, scale = 1, is_primary = 1, is_presentation = 0} ...which seems to exactly match the monitor I'm using. There is no third item in the list. I walked up the stack to create_monitors_config() where this data structure is created, and it looks like the `logical_monitor_configs` variable is created, and then appended to, but never initialised. I don't know if that's actually the problem, but it's consistent with the symptoms I'm seeing. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-flashback depends on: ii gnome-flashback-common 3.42.0-1 ii libasound2 1.2.5.1-1 ii libatk1.0-0 2.36.0-2 ii libc6 2.32-4 ii libcairo2 1.16.0-5 ii libcanberra-gtk3-0 0.30-8 ii libcanberra0 0.30-8 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libgdm1 41.0-3 ii libglib2.0-0 2.70.0-3 ii libgnome-bluetooth13 3.34.5-4 ii libgnome-desktop-3-19 41.0-1 ii libgnome-panel0 3.42.0-1 ii libgtk-3-0 3.24.30-3 ii libibus-1.0-5 1.5.25-2 ii libpam0g 1.4.0-10 ii libpango-1.0-0 1.48.10+ds1-1 ii libpangocairo-1.0-0 1.48.10+ds1-1 ii libpolkit-agent-1-0 0.105-31 ii libpolkit-gobject-1-0 0.105-31 ii libpulse-mainloop-glib0 15.0+dfsg1-2 ii libpulse0 15.0+dfsg1-2 ii libsystemd0 249.5-2 ii libx11-6 2:1.7.2-2+b1 ii libx11-xcb1 2:1.7.2-2+b1 ii libxcb-randr0 1.14-3 ii libxext6 2:1.3.4-1 ii libxfixes3 1:5.0.3-2 ii libxi6 2:1.8-1 ii libxkbfile1 1:1.1.0-1 ii libxrandr2 2:1.5.2-1 ii libxxf86vm1 1:1.1.4-1+b2 ii nautilus 41.1-1 Versions of packages gnome-flashback recommends: ii dbus 1.12.20-3 ii gnome-settings-daemon 41.0-2 ii libpam-gnome-keyring 40.0-3 Versions of packages gnome-flashback suggests: ii gnome-power-manager 3.32.0-2 -- no debconf information
--- End Message ---
--- Begin Message ---Source: gnome-flashback Source-Version: 3.42.0-2 Done: Dmitry Shachnev <[email protected]> We believe that the bug you reported is fixed in the latest version of gnome-flashback, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev <[email protected]> (supplier of updated gnome-flashback package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 08 Nov 2021 23:19:43 +0300 Source: gnome-flashback Architecture: source Version: 3.42.0-2 Distribution: unstable Urgency: high Maintainer: Debian GNOME Maintainers <[email protected]> Changed-By: Dmitry Shachnev <[email protected]> Closes: 998837 Changes: gnome-flashback (3.42.0-2) unstable; urgency=high . * Backport upstream patch to fix segfault on login. Thanks to Timothy Allen for the bug report. (Closes: #998837) Checksums-Sha1: b9d263d8891e7f205a8f08db52b0a97177467f77 2875 gnome-flashback_3.42.0-2.dsc 95a433b7dc875f692ef4cb7c73f232f57ac6bdb3 9656 gnome-flashback_3.42.0-2.debian.tar.xz fb59e8955d24c13584822cd7fbbd1ff902df04be 16524 gnome-flashback_3.42.0-2_source.buildinfo Checksums-Sha256: 17fe67be204e398399473a38b7d95a6b45dd45243a66f39b148941f034baf52e 2875 gnome-flashback_3.42.0-2.dsc 6a9b81b5d80811fef7f9d2a1c5a3050a3cb071a1156c6715115277e07c6795c2 9656 gnome-flashback_3.42.0-2.debian.tar.xz 5c95308b699e604f069ec89e7cdce0216fd2c88a9132b22620be984952e8cab5 16524 gnome-flashback_3.42.0-2_source.buildinfo Files: f055308f33828cab767efa75867d011e 2875 gnome optional gnome-flashback_3.42.0-2.dsc ebec60c216be0b1cfcb7322f1fb9a545 9656 gnome optional gnome-flashback_3.42.0-2.debian.tar.xz 38547a4748496a7dff792653b8789f4d 16524 gnome optional gnome-flashback_3.42.0-2_source.buildinfo -----BEGIN PGP SIGNATURE----- iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmGJhwcTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBmRiZbWGuDy7/REACM3rRFp0+6kQWM3SdWatrO3kkonuX9 m2iLOLyDe8n2Qkhirn2X3Jf/lD546t9eSQnyr+9xsghlo8HLnfTp63Tda69GIlsr zX8n+GIG6gLxj2CmJi0ejTD/XYj6t+B8nFOg0euo6acmHik9jNkb0ZkrgoMMLOfa x0L2fXmXyULt13W3PibUYT3wVs6jSGeqc68a0snBPZxOILyxRQzC9SmYgEONQQFu hv17bgAI53A0gOReR+6ajXO+8J/8TG9LhXQoTGopiqtbiVORckEXWDrCvH3uylWH FUcG6klSri93A6CbhXGr1kcvc8xRTDLpVHd9oRGSxEemyGAsjgqQY4y9gbf8tTPu mYDoSg612damA8Q1YBFPDgRdmoyL5suBgk0bgwQI1AHO320xQBMSM6aJvOKd3Pp9 eSskzw3zXCo354C0cd/exXiIXPcZnY15gSUgX9746g2+M2j8w1rWlzJ87im6m76R D1qR+ei+V6fBLGLJWEtbOMNsZ551ulR32HKMdkzm5koMILfgXfkA9Tv3MUKA3mui UdVemk2LhkjZc6LtaVSYGzVl+e2gcUxndz2x0i0sQNDt8uOlFBQbydusBFKZrqso vxjjKkMU86rSZl+3cLB1dzWD6/36WNrquwj7tR+VbSQqL5e0XxD/WpJJbmI3ZuFm KsCrVXwxdEZM5w== =9yzF -----END PGP SIGNATURE-----
--- End Message ---
