Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Classic and Clutter dialogs show when pressing power button

Open
#181 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
desktop

Research direction

Start by reproducing the issue with the power button set to “Ask” and compare it with opening the dialog from the menu. Read the reported cinnamon-session-binary syslog message and trace the power-button path that launches the end-session dialog. Done means the power button shows only the Clutter dialog without the approximately 60-second freeze or GTK fallback.

Written by the indexing model from the issue text.

Description

* cinnamon-session version (cinnamon-session --version)
6.4.0

* Distribution - (Mint 17.2, Arch, Fedora 25, etc...)
Fedora 41 (also tested on Mint 22.1)

* Graphics hardware *and* driver used
Device-1: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
   driver: amdgpu

* 32 or 64 bit
64 bit

Issue
When the power button is set to "Ask" (in Power Management - When the power button is pressed), when the button is pressed, the entire system will freeze for ~60 seconds then pop up BOTH the new Clutter dialog and the old GTK dialog. The following is found in the syslog:

cinnamon-session-binary[1829]: CRITICAL: t+890.86122s: Failed to launch Cinnamon's end session dialog, falling back to Gtk end-session dialog: Timeout was reached

Steps to reproduce
Set power button behavior to "Ask" then press the power button

Expected behaviour
Clutter dialog only appears

Other information
It is only when pressing the power button that both dialogs will appear. If the dialog is opened by some other means (e.g. the menu), only the Clutter dialog shows.

Dominant language
C
Stars
30
Forks
41
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/cinnamon-session

All issues in linuxmint/cinnamon-session

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.