linuxmint / linuxmint/cinnamon
Bugs in Linux Mint 21 Cinnamon desktop environment
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5.6k
- Forks
- 915
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 3
Description
Hi everybody!
I discovered some blemishes on the freshly installed Linux Mint 21 Cinnamon.
Scenario 1:
- Click and HOLD the left mouse button -> Any file or folder (Nemo or Desktop) OR click on an empty area of the desktop OR click on an empty area or a button within a program.
- Click and release the "superkey" ("windows key" or "tux-key") (Cinnamon main menu opens.)
- Now release the left mouse button.
The Cinnamon main menu no longer reacts to any selection and remains in the foreground until the "super button" is pressed again.
Scenario 2:
- Right-click and release on the desktop (regardless of whether it is an empty area or an object).
The brightness AND the volume can no longer be controlled via the FN key until the selection is deselected again with the LEFT mouse button. (Fn-key (hold) + Fx keys (press); depends on the keyboard)
Scenario 3:
- Left click on the calendar OR the battery icon OR the volume control OR the network icon OR the eject icon OR the notification icon in the taskbar and release.
The brightness can no longer be controlled via the FN key until the selection is deselected again with the LEFT mouse button.
System:
Kernel: 5.15.0-53-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: Cinnamon 5.4.12
tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy
Machine:
Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X705FN_N705FN v: 1.0
serial: <superuser required>
Mobo: ASUSTeK model: X705FN v: 1.0 serial: <superuser required> UEFI: American Megatrends
v: X705FN.314 date: 07/04/2019
Battery:
ID-1: BAT0 charge: 30.5 Wh (97.4%) condition: 31.3/43.0 Wh (72.8%) volts: 11.6 min: 11.6
model: ASUSTeK ASUS Battery serial: N/A status: Not charging
CPU:
Info: quad core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Comet/Whiskey Lake
note: check rev: C cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
Speed (MHz): avg: 897 high: 1302 min/max: 400/3900 cores: 1: 1302 2: 700 3: 700 4: 745 5: 1194
6: 1165 7: 700 8: 673 bogomips: 28800
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: ASUSTeK driver: i915 v: kernel
ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3ea0
Device-2: NVIDIA GP108M [GeForce MX150] vendor: ASUSTeK driver: nvidia v: 515.65.01 pcie:
speed: 2.5 GT/s lanes: 4 bus-ID: 02:00.0 chip-ID: 10de:1d10
Device-3: IMC Networks USB2.0 VGA UVC WebCam type: USB driver: uvcvideo bus-ID: 1-7:5
chip-ID: 13d3:5a11
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting,nvidia
unloaded: fbdev,nouveau,vesa gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 98
Monitor-1: eDP-1 model: LG res: 1920x1080 dpi: 128 diag: 438mm (17.3")
OpenGL: renderer: Mesa Intel UHD Graphics 620 (WHL GT2) v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
Device-1: Intel Cannon Point-LP High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9dc8
Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel bus-ID: 00:14.3
chip-ID: 8086:9df0
IF: wlo1 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 03:00.0 chip-ID: 10ec:8168
IF: eno2 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
bus-ID: 1-10:7 chip-ID: 8087:0aaa
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
sub-v: 100
Drives:
Local Storage: total: 715.41 GiB used: 338.65 GiB (47.3%)
ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKNW512G8 size: 476.94 GiB speed: 31.6 Gb/s
lanes: 4 serial: <filter> temp: 25.9 C
ID-2: /dev/sda type: USB vendor: Samsung model: 470 Series S size: 238.47 GiB serial: <filter>
Partition:
ID-1: / size: 467.89 GiB used: 123.45 GiB (26.4%) fs: ext4 dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 8 GiB used: 2 MiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 48.0 C pch: 45.0 C mobo: N/A
Fan Speeds (RPM): cpu: 1900
Repos:
Packages: 2545 apt: 2529 flatpak: 16
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb https: //ftp-stud.hs-esslingen.de/pub/Mirrors/packages.linuxmint.com vanessa main upstream import backport
2: deb http: //mirror.easyname.at/ubuntu-archive jammy main restricted universe multiverse
3: deb http: //mirror.easyname.at/ubuntu-archive jammy-updates main restricted universe multiverse
4: deb http: //mirror.easyname.at/ubuntu-archive jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/picoscope7.list
1: deb [signed-by=/usr/share/keyrings/picoscope7.gpg] https: //labs.picotech.com/rc/picoscope7/debian/ picoscope main
Info:
Processes: 323 Uptime: 6h 59m Memory: 7.62 GiB used: 3.83 GiB (50.3%) Init: systemd v: 249
runlevel: 5 Compilers: gcc: 11.3.0 alt: 11 Client: Cinnamon v: 5.4.12 inxi: 3.3.13
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source files or tests. Start by reproducing the three scenarios in Cinnamon 5.4.12, then trace input handling for the desktop, main menu, taskbar, and keyboard controls. Done means opening or selecting these UI elements no longer prevents the reported menu, brightness, or volume controls from responding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100