Bug#1031865: gnome-terminal: all themes not applying, including 'custom' and 'use colors from system theme'

[birch]

Package: gnome-terminal
Version: 3.46.7-1
Severity: important
Tags: a11y

Dear Maintainer,

No themes are applied when selected. This includes selecting "use colors from system theme" and "custom," as well as attempting to change the theme via selecting or deselecting "dark mode" in gnome system menu.

Colors still can be changed in the console via OSC 4/11 apparently (I have tried installing theme.sh which indicates it applies colors via this protocol).

I have attempted to install other VTE based terminals and all of them suffer the same problem (gnome-console, sakura, etc).

This leads me to believe this is a VTE issue but since I am not a developer I cannot test further or make an appropriately specific libvte bug report.

This is in a fresh install of bookworm.

-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-terminal depends on:
ii dbus-user-session [default-dbus-session-bus] 1.14.6-1
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4
ii gnome-terminal-data 3.46.7-1
ii gsettings-desktop-schemas 43.0-1
ii libatk1.0-0 2.46.0-5
ii libc6 2.36-8
ii libgcc-s1 12.2.0-14
ii libglib2.0-0 2.74.5-1
ii libgtk-3-0 3.24.36-3
ii libpango-1.0-0 1.50.12+ds-1
ii libstdc++6 12.2.0-14
ii libuuid1 2.38.1-4
ii libvte-2.91-0 0.70.2-2
ii libx11-6 2:1.8.3-3

Versions of packages gnome-terminal recommends:
ii gvfs 1.50.3-1
ii nautilus-extension-gnome-terminal 3.46.7-1
ii yelp 42.2-1

gnome-terminal suggests no packages.

-- no debconf information

[Egmont Koblinger]

Hi,

In VTE, colors defined via OSC 4 / 10 / 11 take precedence over the ones set in the preferences dialog.

Please double check that you don't emit these OSC codes, or reset them via their corresponding OSC 104 / 110 / 111.

Does this fix your problem?

cheers,

egmont