Dark Mode issue with Libre Office - Unreadable buttons

Hello,

I started to use Dark theme 1 week ago, and now after needing to use Libre Office Impress i was surprised by and issue related to the buttons at top menu unable to be read once the text or imagens in the buttons are black and the back ground are black too. see the image below for better understanding and comparison.

Searching in the forum I found the thread below but ti’s related to a different issue, if you open the link you will see the his menu if properly colored and he can identify all buttons while mine not. Don’t know if it’s Libre Office issue, KDE issue or Manjaro issue.

https://forum.manjaro.org/t/unreadable-text-with-libreoffice-dark-theme-dark-font/27200

System:
  Kernel: 5.14.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.14-x86_64
  root=UUID=dfa33105-8d9e-4555-9174-609a71216485 ro quiet apparmor=1
  security=apparmor resume=UUID=493ccde5-7f80-4bf5-b22c-98ce796aade6
  udev.log_priority=3
  Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
  Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-870A-UD3 v: x.x serial: <filter>
  BIOS: Award v: F5 date: 08/01/2011
Battery:
  Message: No system battery data found. Is one present?
Memory:
  RAM: total: 7.76 GiB used: 4.86 GiB (62.6%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: Quad Core model: AMD Phenom II X4 965 bits: 64 type: MCP arch: K10
  family: 10 (16) model-id: 4 stepping: 3 microcode: 10000C8 cache: L2: 2 MiB
  bogomips: 27336
  Speed: 800 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 800 2: 2200
  3: 800 4: 3400
  Flags: 3dnow 3dnowext 3dnowprefetch abm apic clflush cmov cmp_legacy
  constant_tsc cpuid cr8_legacy cx16 cx8 de extapic extd_apicid fpu fxsr
  fxsr_opt ht hw_pstate ibs lahf_lm lbrv lm mca mce misalignsse mmx mmxext
  monitor msr mtrr nonstop_tsc nopl npt nrip_save nx osvw pae pat pdpe1gb pge
  pni popcnt pse pse36 rdtscp rep_good sep skinit sse sse2 sse4a svm svm_lock
  syscall tsc vme vmmcall wdt
  Vulnerabilities: Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
  mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
  vendor: Micro-Star MSI driver: amdgpu v: kernel bus-ID: 01:00.0
  chip-ID: 1002:67df class-ID: 0300
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver:
  loaded: amdgpu,ati unloaded: modesetting,radeon alternate: fbdev,vesa
  display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
  s-diag: 582mm (22.9")
  Monitor-1: DVI-D-0 res: 1920x1080 hz: 60 dpi: 96
  size: 510x290mm (20.1x11.4") diag: 587mm (23.1")
  OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.42.0
  5.14.10-1-MANJARO LLVM 12.0.1)
  v: 4.6 Mesa 21.2.3 direct render: Yes
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte GA-880GMA-USB3
  driver: snd_hda_intel v: kernel bus-ID: 00:14.2 chip-ID: 1002:4383
  class-ID: 0403
  Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
  vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 01:00.1
  chip-ID: 1002:aaf0 class-ID: 0403
  Sound Server-1: ALSA v: k5.14.10-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.38 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Gigabyte driver: r8169 v: kernel port: 9e00 bus-ID: 06:00.0
  chip-ID: 10ec:8168 class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
  broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.48 TiB used: 1.84 TiB (74.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 240GB
  size: 223.58 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
  type: SSD serial: <filter> rev: 00RL scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 vendor: Corsair model: Corsair Force GS
  size: 119.24 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
  type: SSD serial: <filter> rev: 5.07 scheme: MBR
  ID-3: /dev/sdc maj-min: 8:32 vendor: Patriot model: Burst size: 223.57 GiB
  block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD
  serial: <filter> rev: KB.3 scheme: MBR
  ID-4: /dev/sdd maj-min: 8:48 vendor: Crucial model: CT120BX100SSD1
  size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
  type: SSD serial: <filter> rev: MU01 scheme: GPT
  ID-5: /dev/sde maj-min: 8:64 vendor: Western Digital model: WD20PURZ-85GU6Y0
  size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  type: HDD rpm: 5400 serial: <filter> rev: 0A80 scheme: MBR
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH22NS50 rev: TN02
  dev-links: cdrom
  Features: speed: 48 multisession: yes audio: yes dvd: yes
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 214.77 GiB size: 210.4 GiB (97.96%)
  used: 143.15 GiB (68.0%) fs: ext4 dev: /dev/sdc1 maj-min: 8:33
  label: LINUX-SSD uuid: dfa33105-8d9e-4555-9174-609a71216485
  ID-2: /home/<filter>/Games raw-size: 111.79 GiB size: 109.47 GiB (97.93%)
  used: 61.04 GiB (55.8%) fs: ext4 dev: /dev/sdd1 maj-min: 8:49
  label: LINUX-GAMES uuid: ef7d7ba9-f8da-4419-b9a3-ca9e2232da86
  ID-3: /home/<filter>/HDD-DATA-2T raw-size: 1.82 TiB size: 1.82 TiB (100.00%)
  used: 1.64 TiB (89.9%) fs: ntfs dev: /dev/sde1 maj-min: 8:65 label: DATA_2T
  uuid: 28A6726FA6723CFE
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 8.8 GiB used: 872.2 MiB (9.7%)
  priority: -2 dev: /dev/sdc2 maj-min: 8:34 label: N/A
  uuid: 493ccde5-7f80-4bf5-b22c-98ce796aade6
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 100 MiB fs: ntfs label: System Reserved
  uuid: E680DA2C5F90FD24
  ID-2: /dev/sda2 maj-min: 8:2 size: 223.48 GiB fs: ntfs label: WIN-SSD
  uuid: 07492E03A516286B
  ID-3: /dev/sdb1 maj-min: 8:17 size: 119.24 GiB fs: ntfs label: WIN-GAMES
  uuid: EAE6EE7DE6EE4A01
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 5 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 5 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 5 rev: 1.1 speed: 12 Mb/s
  chip-ID: 1d6b:0001 class-ID: 0900
  Hub-5: 5-0:1 info: Full speed (or root) Hub ports: 5 rev: 1.1 speed: 12 Mb/s
  chip-ID: 1d6b:0001 class-ID: 0900
  Hub-6: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
  chip-ID: 1d6b:0001 class-ID: 0900
  Hub-7: 7-0:1 info: Full speed (or root) Hub ports: 4 rev: 1.1 speed: 12 Mb/s
  chip-ID: 1d6b:0001 class-ID: 0900
  Device-1: 7-3:2 info: SINO WEALTH USB KEYBOARD type: Keyboard,HID
  driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s
  power: 100mA chip-ID: 258a:0001 class-ID: 0300
  Device-2: 7-4:3 info: Pixart Imaging Optical Mouse type: Mouse
  driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s
  power: 100mA chip-ID: 093a:2521 class-ID: 0301
  Hub-8: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-9: 9-0:1 info: Full speed (or root) Hub ports: 2 rev: 3.0 speed: 5 Gb/s
  chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 42.2 C mobo: N/A gpu: amdgpu temp: 54.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 203
Info:
  Processes: 306 Uptime: 13h 47m wakeups: 0 Init: systemd v: 249
  tool: systemctl Compilers: gcc: 11.1.0 Packages: 1504 pacman: 1490 lib: 445
  flatpak: 14 Shell: Bash v: 5.1.8 running-in: yakuake inxi: 3.3.08

Below also my current Libre Office Color settings (app default)

LibreOffice → View → Icon ?

1 Like

Regarding configuration: LibreOffice → View → Icon

It’s set to automatic but in parentheses you can see breeze indication witch clear mismatch my current Theme (Breath2 2021 Dark), so besides I can manually fixes the issue (thanks for that), this mismatch is still and issue that needs to be fixed.

There is no Breath theme for LibreOffice. Choose the Breeze Dark icon style instead.

1 Like

If you go into “Personalization” you can change the baground color of Libreoffice. You could give that a try

So you decide, is it fixed or does it need to be fixed? What are you expecting from us here? I gave you the solution. Now it is fixed. If you want you can contact LibreOffice to have their program looked at for your particular setup which doesn’t select the best icon set automatically but we can do nothing more here.

I expected Libre Office to follow Manjaro Theme definition once the default settings is Automatic and this behavior is issued, maybe Manjato team could open ticket to Libre Office to fix it. I can’t judge were the root cause is, if it’s Manjaro side or Libre office side.

I will tag the solution, but tomorrow, if I change the theme again, I will need to set Libre Office config manually again once the Automatic isn’t work properly, so a permanent solution should come via developers once your suggestion is just an interim solution.

Breath is a theme developed by the Manjaro developers. It is a KDE Global theme, and is not available as a LibreOffice icon theme.

In KDE, the default theme is Breeze (Manjaro changes its default theme to Breath), which is the icon theme LibreOffice chooses automatically, as Breeze is available as a LibreOffice theme. The “Automatic” theme is DE dependent. In XFCE, LibreOffice automatically chooses the Colibre icon theme instead.

If you want a “Breath” theme for Libreoffice, you will have to help create it. LibreOffice is a GTK app, it is not designed to automatically pickup the KDE global theme.

If you use a dark GTK theme, you need to choose a dark icon theme (e.g Breeze (dark)) in LibreOffice. If you use a light GTK theme, you need to manually choose a light icon theme in LibreOffice.

Hello archisman,

Regardless all technical characteristics of the applications and DE environment from user point of view I think it can be simplified as two options:

Is the default theme Dark or Light? and so, Libre Office should recognize both, all other themes, customization, etc, should just be variants of dark and light, once those two became standard in all devices applications. Someone might want to create a grey theme, or pink one, no problem, but in this specific case things should be set manually. But I think default themes should work automatically and well integrated. You just confirmed that there are some technical issues that needs to be managed from developers.

But it matters.
Graphical frameworks make a difference. You cant just set a plasma/qt theme and expect gtk apps like firefox to follow…they wont.
Libreoffice though, while GTK, is a slightly special case as it supports both integrations, but you may need to configure it.

See: LibreOffice - ArchWiki
(the vlc stuff … on plasma you probably want kf5)

No doubt It matter, but for developers, not for the users.

Sometimes linux community make confusion that all linux user are at certain point developers, currently maybe it’s real because linux desktop is very small in terms of maket percentage (1~2%), but if linux starts to grow in terms of adoption, more users we get, more far away from technical stuffs they will be. Take this into account.

No one can deny that there is an issue, because it’s a fact. Maybe currently, it can’t be fixed, OK, but due to the flexibility/freedom and large portfolio available in linux is a kind of system integration challenging, but this puzzle game needs to be played for developers and not users. Maybe also this is one of the reasons that there are so many distros.

The idea behind providing feedback as user, is to support the issue to be fixed as fast as possible in the best way as possible and because we want to support the improvement of the distro we chosen to use.

You can join the developers teams and to look it from inside and try to address all issues for years in a row for free or for some donations you will have.

I can fully understand you from a user point of view, but that’s only one side of the issue.

Now you can switch to makers point of view in try to understand common OSS problems a bit deeper.

If that’s toolbar view setup is a hard puzzle, and you do not plan to think a bit, than currently it is hard to suggest you any GNU/Linux distro. May be to try to be a bit more skilled to make yourself able to try generate ideas why something happens and what it depends on and to try to realize relations and to fix an issue? or to ask community - users just like you.

It is the upstream app, to make your ideas be able to implement, a package owners should know about it. Please try to file an issue report there. You can help yourself and others in future by getting a fix or probably will know makers/developers feedback on your idea.

Cheers!

I think donations to Manjaro team is better and safer, so they can grow and have the right people to do the right thing. I don’t think that all user have the skills, the ability or even time to invest learning programming languages.

Me an others can learn to do something small as DIY here and there, but we should not invert the responsibility, I’m glad for Manjaro and I will support this distro the best way I can, but again, don’t expect users to be developers, this is a wrong community understand for long.

Everybody expressed his thoughts about the issue, so, from my side, this thread can be closed.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.