Your message dated Sun, 9 Nov 2025 21:03:09 -0500
with message-id 
<CAAajCMaQ4aUjtM4OA418LXsro+LK0Q2-77rVcR2Z3tyvj=4...@mail.gmail.com>
and subject line closing old gnome-settings-daemon bugs
has caused the Debian Bug report #742232,
regarding gnome-settings-daemon: When accessing Background settings, settings 
menu crashes
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.)


-- 
742232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742232
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 3.8.5-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
        Opened Gnome Settings, chose "Background"
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
        Nothing stopped it from crashing instantly. I changed the background by
using Gnome-Tweak-Tool instead
   * What was the outcome of this action?
        Gnome-Tweak-Tool worked, but the Settings menu still crashses.
   * What outcome did you expect instead?
        For the Settings menu to open up the Background Settings options




-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-settings-daemon depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.18.0-1
ii  gsettings-desktop-schemas                    3.8.2-2
ii  libc6                                        2.18-4
ii  libcairo2                                    1.12.16-2
ii  libcanberra-gtk3-0                           0.30-2
ii  libcanberra0                                 0.30-2
ii  libcolord1                                   1.0.6-1
ii  libcups2                                     1.7.1-9
ii  libfontconfig1                               2.11.0-5
ii  libgdk-pixbuf2.0-0                           2.30.6-1
ii  libglib2.0-0                                 2.38.2-5
ii  libgnome-desktop-3-7                         3.8.4-2
ii  libgtk-3-0                                   3.10.7-1
ii  libgudev-1.0-0                               204-8
ii  libibus-1.0-5                                1.5.5-1
ii  liblcms2-2                                   2.5-1
ii  libnotify4                                   0.7.6-2
ii  libpackagekit-glib2-16                       0.8.16-1
ii  libpango-1.0-0                               1.36.2-2
ii  libpulse-mainloop-glib0                      4.0-6+b1
ii  libpulse0                                    4.0-6+b1
ii  librsvg2-2                                   2.40.2-1
ii  libupower-glib1                              0.9.23-2+b1
ii  libwacom2                                    0.8-1
ii  libx11-6                                     2:1.6.2-1
ii  libxfixes3                                   1:5.0.1-1
ii  libxi6                                       2:1.7.2-1
ii  libxkbfile1                                  1:1.0.8-1
ii  libxtst6                                     2:1.2.2-1
ii  nautilus-data                                3.8.2-2
ii  systemd                                      204-8

Versions of packages gnome-settings-daemon recommends:
ii  pulseaudio  4.0-6+b1

Versions of packages gnome-settings-daemon suggests:
ii  gnome-screensaver            3.6.1-1
ii  metacity [x-window-manager]  1:2.34.13-1
ii  x11-xserver-utils            7.7+2
ii  xfwm4 [x-window-manager]     4.10.1-2

-- no debconf information

--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.

Thank you,
Jeremy BĂ­cha

--- End Message ---

Reply via email to