Tray applet menus detached from panel

When right clicking on a given applet in the system tray, their menus are appearing about 1/3 of the way up the screen. I can't find where I can change this behavior and have no clue how this happened in the 1st place.

Post the output of inxi -Fxz
put ``` before and after the text so it's formatted correctly.

We have no idea what you're running. :thinking:


Apologies, thought tagging this as Cinnamon would be enough.

  Host: jiibus-pc Kernel: 5.1.8-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.3.0 
  Desktop: Cinnamon 4.0.10 Distro: Manjaro Linux 
  Type: Desktop Mobo: ASUSTeK model: ROG STRIX X370-F GAMING v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 4024 date: 09/07/2018 
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse MX Master 2S 
  charge: 100% (should be ignored) status: Discharging 
  Topology: 6-Core model: AMD Ryzen 5 1600X bits: 64 type: MT MCP arch: Zen rev: 1 
  L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 96446 
  Speed: 2471 MHz min/max: 2200/3900 MHz Core speeds (MHz): 1: 3205 2: 3230 3: 1785 
  4: 1783 5: 1785 6: 1779 7: 1784 8: 1787 9: 3216 10: 3216 11: 1785 12: 1784 
  Device-1: NVIDIA GP104 [GeForce GTX 1070 Ti] vendor: ASUSTeK driver: nvidia 
  v: 430.14 bus ID: 0a:00.0 
  Display: x11 server: X.Org 1.20.5 driver: nvidia 
  resolution: 1920x1080~75Hz, 2560x1440~60Hz 
  OpenGL: renderer: GeForce GTX 1070 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 430.14 
  direct render: Yes 
  Device-1: NVIDIA GP104 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 0a:00.1 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus ID: 0c:00.3 
  Sound Server: ALSA v: k5.1.8-1-MANJARO 
  Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: 5.6.0-k 
  port: e000 bus ID: 05:00.0 
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
  Local Storage: total: 7.73 TiB used: 1.67 TiB (21.6%) 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB 
  ID-2: /dev/sda vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB 
  ID-3: /dev/sdb vendor: Samsung model: SSD 840 EVO 500GB size: 465.76 GiB 
  ID-4: /dev/sdc vendor: Western Digital model: WD30EZRZ-00GXCB0 size: 2.73 TiB 
  ID-1: / size: 440.20 GiB used: 43.49 GiB (9.9%) fs: ext4 dev: /dev/sdb2 
  ID-2: swap-1 size: 17.22 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sdb3 
  System Temperatures: cpu: 37.9 C mobo: N/A gpu: nvidia temp: 40 C 
  Fan Speeds (RPM): cpu: 0 gpu: nvidia fan: 0% 
  Processes: 312 Uptime: 9h 03m Memory: 31.41 GiB used: 3.70 GiB (11.8%) Init: systemd 
  Compilers: gcc: 8.3.0 Shell: bash v: 5.0.7 inxi: 3.0.34 

1 Like

I think is related with the way that dual display layout works
From terminal:
rm -r ~/.config/monitors.xml
systemctl reboot
and see if the issue persists. Consider to change the theme too, maybe is related.

Seems like you're onto something. Deleted monitors.xml and it made the smaller monitor the primary one and the tooltips/menus showed properly, but when I set the larger monitor as primary, the issue rears its head. Changing desktop themes doesn't affect it either.

This might seem silly and I don't recall if you can do this on Cinnamon...
Maybe the menus need a refresher. Can you resize the taskbar (or whatever Cinnamon calls it) larger and/or smaller?
Perhaps that might reset the placeholder spot telling the applet where the taskbar is for the applet menu?

It does have the option, but going from smallest to largest didn't do anything. Although it does give me the idea of completely deleting the panel and creating a fresh one.

Actually, resetting the panel to default seems to have done the trick. Can't believe I didn't try that before.

I believe I've isolated the cause. Having a panel on the bottom of the 2nd, smaller monitor seems to freak out the DE. I can add a panel to the top and the menus show as intended on my primary.

1 Like

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

Forum kindly sponsored by