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

Nemo start then crash after 1-2 seconds

Open
#3,738 8 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 13 days

Nobody has claimed this yet.

Assessment

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

Research direction

The report concerns Nemo 6.6.3 on Linux Mint 22.3 and includes stacktrace.txt; start by reading that trace and reproducing the crash by launching nemo from a console. Review the extension initialization messages around the free(): invalid pointer failure. Done means Nemo remains running after startup without the crash.

Written by the indexing model from the issue text.

Description

Distribution

Linux Mint 22.3 Zena

Package version

nemo 6.6.3

Frequency

Always

Bug description

Hi,

After OS update, Nemo has a problem.. start then collapse after 1-2 seconds.

Steps to reproduce

Use Menu or by use console:

pancio@desktop:~$ nemo
Initializing nemo-pastebin extension...
DEBUG:nemo-pastebin:Initializing nemo-pastebin extension...
[Nemo Terminal] I: Initializing the Nemo extension
nemo-media-columns: using a timeout of 0.20 second(s) for file processing
Initializing nemo-image-converter extension
free(): invalid pointer
Przerwane (zrzut pamięci)
pancio@desktop:~$ 
Expected behavior

To be stable and not collapse...

Additional information

stacktrace.txt

Dominant language
C
Stars
1.6k
Forks
371
Avg merge
8d 7h
Merged PRs (30d)
1

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/nemo

All issues in linuxmint/nemo

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.