Ask Your Question
0

nautilus segmentation fault

asked 2018-11-18 13:59:09 -0600

fordprefect gravatar image

updated 2018-11-18 16:08:53 -0600

Hi Folks, I have problems with Nautilus. I have some cifs mounts via systemd. For one mountpoint if I want to enter it, Nautilus crashes with segmentation fault. I really don't understand it because it worked beforehand and all the other mount points which are nearly identical are working fine.

I even tried to completely stop, disable, the service and remover the file and the folder. Rebooting and adding everything again. But it doesn't help. I also removed nautilus and installed it again. Nothing helps. WIth this I really can't use the system.

When I do:

gdb nautilus

and then run I get the following output, when I want to enter the share:

Thread 15 "pool" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff1652700 (LWP 9439)]
0x00007ffff73c9e8d in ?? () from /lib64/libgio-2.0.so.0

Here is the recent output of journalctl -p3. Found on my internet research that this might provide more information.

Nov 18 22:59:07 lide systemd-coredump[10544]: Process 10528 (nautilus) of user 1000 dumped core.

                                              Stack trace of thread 10534:
                                              #0  0x00007f8ddeee7e8d n/a (libgio-2.0.so.0)
                                              #1  0x00007f8ddeee83d4 n/a (libgio-2.0.so.0)
                                              #2  0x00007f8ddeee721a n/a (libgio-2.0.so.0)
                                              #3  0x00007f8ddeec3983 g_content_type_guess (libgio-2.0.so.0)
                                              #4  0x00007f8ddeeb3184 n/a (libgio-2.0.so.0)
                                              #5  0x00007f8ddeeb4bbc n/a (libgio-2.0.so.0)
                                              #6  0x00007f8ddeeb1f11 n/a (libgio-2.0.so.0)
                                              #7  0x00007f8ddee204c8 n/a (libgio-2.0.so.0)
                                              #8  0x00007f8ddee5ba07 n/a (libgio-2.0.so.0)
                                              #9  0x00007f8ddfa1ee93 n/a (libglib-2.0.so.0)
                                              #10 0x00007f8ddfa1e48a n/a (libglib-2.0.so.0)
                                              #11 0x00007f8ddeaf558e start_thread (libpthread.so.0)
                                              #12 0x00007f8ddea24593 __clone (libc.so.6)

                                              Stack trace of thread 10532:
                                              #0  0x00007f8ddea1eded syscall (libc.so.6)
                                              #1  0x00007f8ddfa3d003 g_cond_wait (libglib-2.0.so.0)
                                              #2  0x00007f8ddf9c724b n/a (libglib-2.0.so.0)
                                              #3  0x00007f8ddfa1ee67 n/a (libglib-2.0.so.0)
                                              #4  0x00007f8ddfa1e48a n/a (libglib-2.0.so.0)
                                              #5  0x00007f8ddeaf558e start_thread (libpthread.so.0)
                                              #6  0x00007f8ddea24593 __clone (libc.so.6)

                                              Stack trace of thread 10529:
                                              #0  0x00007f8ddea19371 __poll (libc.so.6)
                                              #1  0x00007f8ddf9f55a6 n/a (libglib-2.0.so.0)
                                              #2  0x00007f8ddf9f56d0 g_main_context_iteration (libglib-2.0.so.0)
                                              #3  0x00007f8ddf9f5721 n/a (libglib-2.0.so.0)
                                              #4  0x00007f8ddfa1e48a n/a (libglib-2.0.so.0)
                                              #5  0x00007f8ddeaf558e start_thread (libpthread.so.0)
                                              #6  0x00007f8ddea24593 __clone (libc.so.6)

                                              Stack trace of thread 10530:
                                              #0  0x00007f8ddea19371 __poll (libc.so.6)
                                              #1  0x00007f8ddf9f55a6 n/a (libglib-2.0.so.0)
                                              #2  0x00007f8ddf9f5962 g_main_loop_run (libglib-2.0.so.0)
                                              #3  0x00007f8ddee9c79a n/a (libgio-2.0.so.0)
                                              #4  0x00007f8ddfa1e48a n/a (libglib-2.0.so.0)
                                              #5  0x00007f8ddeaf558e start_thread (libpthread.so.0)
                                              #6  0x00007f8ddea24593 __clone (libc.so.6)

                                              Stack trace of thread 10533:
                                              #0  0x00007f8ddea19371 __poll (libc.so.6)
                                              #1  0x00007f8ddf9f55a6 n/a (libglib-2.0.so.0)
                                              #2  0x00007f8ddf9f56d0 g_main_context_iteration (libglib-2.0.so.0)
                                              #3  0x00007f8dd997cc7d n/a (libdconfsettings.so)
                                              #4  0x00007f8ddfa1e48a n/a (libglib-2.0.so.0)
                                              #5  0x00007f8ddeaf558e start_thread (libpthread.so.0)
                                              #6  0x00007f8ddea24593 __clone (libc.so.6)

                                              Stack trace of thread 10542:
                                              #0  0x00007f8ddea1eded syscall (libc ...
(more)
edit retag flag offensive close merge delete

Comments

Without debug symbols installed (see the gdb output, especially the line mentioning the command dnf debuginfo-install …), the backtrace is useless. Please install debug symbols and try again.

genodeftest gravatar imagegenodeftest ( 2018-11-20 14:03:09 -0600 )edit

Currently I can reproduce the problem. But Thanks for the information.

fordprefect gravatar imagefordprefect ( 2018-11-21 12:40:38 -0600 )edit

1 Answer

Sort by » oldest newest most voted
2

answered 2018-11-18 19:19:33 -0600

ed209 gravatar image

Create a brand new user. Log in that account and start nautilus. If it works we'll know the culprit is in your settings, not in nautilus itself. The next step will be to rename ~/.config/nautilus and ~/.local/share/nautilus in your account .

edit flag offensive delete link more

Comments

Thx for your help. I created a new user and it worked without segmentation fault several times. I then switched back to my normal user and it worked there too. I can't reproduce the problem at the moment.

It's somehow hard to belief that creating a new user did the trick. Rather something I did yesterday. But I rebooted also there several times. I will let the topic open and see how it behaves in the next days.

fordprefect gravatar imagefordprefect ( 2018-11-18 23:49:57 -0600 )edit

I would say you have some hardware problems. Perhaps the disk, some corrupt library. Check out memory first, it's the easiest part.

ed209 gravatar imageed209 ( 2018-11-19 22:19:03 -0600 )edit

Hmm the problem didn't occur again. I will check the ram.

I also installed newly again. I wanted to make the next step and install Fedora on my laptop and the self check of the usb stick failed. I wasn't aware whether I run this the last time I installed Fedora on my Desktop. So having some problems like this and being in doubt I created the USB newly and installed again. So far I haven't had the issue again. But checking hardware might be good anyway. Can you recommend some linux tools?

fordprefect gravatar imagefordprefect ( 2018-11-20 00:14:46 -0600 )edit

After over Memtest86+ with over 5 passes I would say my RAM is fine. Since the new install was connected to a new setup of the partition and new installation of all files. I assume this isn't a problem either anymore. Of course the disk could be damaged, don't know how to check this despite SMART values. The CPU is fine too i guess. I overclocked it in BIOS and did a 24 hour prime test.

fordprefect gravatar imagefordprefect ( 2018-11-20 12:56:14 -0600 )edit

Perhaps the problem resides in the disk. Best tools to check disks are the ones provided by the maker itself. smart is useless, I never had a single warning worth it, yet the disk went belly up. Strange behaviour could also be observed while overclocking, a prime test will check for overheating and not much else, you could stress your sata or usb interfaces for instance without even knowing it. CPU used today are already fast, no need to risk killing hardware for a 5% increase. If you turn back to standard speed and have no problems, you hit the nail.

ed209 gravatar imageed209 ( 2018-11-20 18:25:02 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-11-18 13:59:09 -0600

Seen: 29 times

Last updated: Nov 18