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

Segmentation fault crash and slow opening of directories

Open
  • Is something wrong?
#3,794 0 comments 0 reactions 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
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
c, linux
Domain
desktop, operating-systems, performance

Research direction

Start by reproducing the delay and crash while opening directories in Nemo, especially on the reported NTFS partition and, for comparison, Ext4. Capture the relevant crash information beyond the single segfault line; done means directories open at a reasonable speed and Nemo no longer crashes.

Written by the indexing model from the issue text.

Description

Distribution

Linux Mint 22.3 - Cinnamon 64-bit

Package version

Nemo 6.6.3

Frequency

Quite often

Bug description

Nemo acts super slow. When opening a folder, it takes a long long time to load its contents. Yes I know that Linux doesn't handle NTFS quickly but this is ridiculous.

Often hanging on the "opening a directory" pop-up window for long enough to stop responding.

Sometimes this results in an outright app crash. Here is one such crash.

Jul 01 16:43:21 Glow-deck kernel: nemo-desktop[2018]: segfault at 0 ip 000058968dff8cf2 sp 00007ffd3b634630 error 4 in nemo-desktop[10bcf2,58968df1c000+10e000] likely on CPU 0 (core 0, socket 0)

Despite how it might look reading it, this is probably an issue with Nemo, not my hardware. Not much to be done about it but file a bug report.

Steps to reproduce

Open folders using Nemo and wait for them to load. Usually within my NTFS partition on my HDD. But rarely there will also be the same issues in my Ext4 SSD.

Expected behavior

Expected directories open promptly, or at least at a reasonable speed considering I'm browsing files in an NTFS partition. Also, expected Nemo to not crash, of course.

Additional information

Running nemo --quit && nemo and then using Nemo for tasks does not log any text into terminal except for this. I don't have any network share folders, so this message isn't concerning to me. But it's odd that nothing else is entering the Terminal log while I perform actions in Nemo.

afterglow@Glow-deck:~$ nemo --quit && nemo
Nemo-Share-Message: 17:09:13.231: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.
Gtk-Message: 17:18:53.312: Failed to load module "xapp-gtk3-module"
Qt: Session management error: Could not open network socket

I am unable to upload .xsession files to this Github, so i cannot share that with you. Bummer. It's also much too long to copypaste here.

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.