cinnamon: cinnamon-menu-editor segmentation fault / fails to start on Python 3.14
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- build-system, desktop-dev
Research direction
The payload names only the cinnamon package (6.6.7_1) and cinnamon-menu-editor crashing on Python 3.14, with no file or function identified. Start by running cinnamon-menu-editor from a terminal with python3 -X faulthandler or under gdb to capture the crashing C-extension frame. Done means either a working package build on Python 3.14 or a documented workaround, confirmed by the editor launching without a segfault.
Written by the indexing model from the issue text.
Description
Is this a new report?
Yes
System Info
Void Linux x86_64, Kernel: 6.18, Python 3.14
Package(s) Affected
cinnamon-6.6.7_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
Unknown / Not reported upstream yet. This issue is triggered by Void Linux's recent update to Python 3.14, where C-extension/GObject bindings in cinnamon-menu-editor cause a segmentation fault.
Expected behaviour
The menu editor (cinnamon-menu-editor) should launch normally when opened from the main menu or via terminal, allowing users to edit application shortcuts without crashing.
Actual behaviour
The menu editor (cinnamon-menu-editor) fails to open and immediately crashes with a "Segmentation fault" error when launched from the main menu or via terminal on Python 3.14.
Steps to reproduce
- Open the main menu or open a terminal.
- Launch the menu editor by clicking "Edit menu" in the context menu or running
cinnamon-menu-editorin the terminal. - Observe that the application fails to open and immediately terminates with a "Segmentation fault" (core dumped) error.
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 2.8k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 325
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from void-linux/void-packages
-
bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
void-linux/void-packages#63249 · 3 comments ·
Maintainers usually reply within 1 day
-
xmlto: sources no longer available from upstreamPossibly taken @L1TerminalFault claimed this 5 days ago. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63237 ·
Maintainers usually reply within 1 day
-
AI 🤖 bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
void-linux/void-packages#63041 · 1 comment ·
Maintainers usually reply within 1 day
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63016 ·
Maintainers usually reply within 1 day
-
nextcloud-client: VFS plugins installed where the client does not searchMay be free again A pull request for this issue was closed without being merged. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
void-linux/void-packages#62700 ·
Maintainers usually reply within 1 day
All issues in void-linux/void-packages
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
paperclipai/paperclip#18671 ·
Maintainers usually reply within 1 day
-
area:core
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
julian-hemmer/ypass#4 ·
-
needs-triage
Difficulty 2/5 Under an hour Newbie friendliness 62/100
manaflow-ai/cmux#32519 ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
mukkund1996/serenity#88 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openwrt/packages#31124 · 1 comment ·
Maintainers usually reply within 1 day