Notification message colour unreadable with "GNOME Classic" session

[Janne Snabb]

After upgrading my Ubuntu GNOME 17.04 system to Ubuntu 17.10 the notification message window colour is unreadable.

It is black text on very dark grey background. See attached screenshot.

To make sure that it does not come from my settings, I created a new user account with empty home directory and logged in using that user account. The issue still remains.

I am not sure if the notification messages are produced by the gnome-shell package.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Sat Sep 23 19:31:17 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2015-06-06 (839 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2017-09-20 (2 days ago)

[Janne Snabb (snabb)]

This bug appears only with "GNOME Classic" session.

How to repeat:

1. Install Ubuntu 17.10
2. apt install gnome-shell-extensions
3. reboot
4. login choosing "GNOME Classic" session
5. open terminal
6. do "notify-send foobar"
7. unreadable notification box appears

Thus, I was able to get rid of this problem by choosing "GNOME on Xorg" session.

[Janne Snabb (snabb)]

Forgot to include affected gnome-shell-extensions package version:

$ apt policy gnome-shell-extensions
gnome-shell-extensions:
  Installed: 3.26.0-1
  Candidate: 3.26.0-1
  Version table:
 *** 3.26.0-1 500
        500 http://se.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
        500 http://se.archive.ubuntu.com/ubuntu artful/universe i386 Packages
        100 /var/lib/dpkg/status

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jay Bhagat (hhbhagat1417)]

I am also affected by this bug. Example of issue in notifications window:

            .-/+oossssoo+/-. jay@jay-XPS-13-9360
        `:+ssssssssssssssssss+:` -------------------
      -+ssssssssssssssssssyyssss+- OS: Ubuntu 17.10 x86_64
    .ossssssssssssssssssdMMMNysssso. Host: XPS 13 9360
   /ssssssssssshdmmNNmmyNMMMMhssssss/ Kernel: 4.13.0-21-generic
  +ssssssssshmydMMMMMMMNddddyssssssss+ Uptime: 1 day, 3 hours, 6 mins
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/ Packages: 2322
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Shell: bash 4.4.12
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ Resolution: 1920x1080
ossyNMMMNyMMhsssssssssssssshmmmhssssssso DE: GNOME-Classic:GNOME
ossyNMMMNyMMhsssssssssssssshmmmhssssssso WM: GNOME Shell
+sssshhhyNMMNyssssssssssssyNMMMysssssss+ WM Theme: Adwaita
.ssssssssdMMMNhsssssssssshNMMMdssssssss. Theme: Adwaita [GTK2/3]
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/ Icons: Adwaita [GTK2/3]
  +sssssssssdmydMMMMMMMMddddyssssssss+ Terminal: gnome-terminal
   /ssssssssssshdmNNNNmyNMMMMhssssss/ CPU: Intel i5-8250U (8) @ 3.400GHz
    .ossssssssssssssssssdMMMNysssso. GPU: Intel Kabylake GT1.5
      -+sssssssssssssssssyyyssss+- Memory: 4962MiB / 7593MiB
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

[Francisco Nogueira (francisco-nogueira)]

Any news?
Also suffering from this issue. Although I haven't spent too much time (yet) poking around with settings, changing the theme didn't seem to make any improvements on the notifications colors.

[Anibal Sanchez (anibal-sanchez)]

Same issue here. Is there any workaround?