Ask Your Question

libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

asked 2017-08-11 04:46:57 +0000

psg_nm gravatar image

I recently got a Dell Precision 5520 with Nvidia discrete graphics and Optimus support and have been bringing it up with Fedora. I initially installed the machine with Fedora 25 and then almost immediately updated it to Fedora 26 since Fedora 26 became available shortly after I installed the machine with Fedora 25.

I would like to try out the proprietary graphics drivers on the machine, but apparently libmutter is segfaulting, preventing GDM from even coming up. I have tried the packaged Nvidia drivers from https://negativo17.org and RPMFusion, but the result is the same--basically, GDM never properly comes up due to a crash in libmutter (so it seems).

Running dmesg (retrieved using journalctl -o short-precise -k -b -1), I see:

Aug 10 21:29:59.795747 skutter kernel: gnome-shell[5609]: segfault at 28 ip 00007f6fe074a7e4 sp 00007ffc6b962300 error 4 in libmutter-0.so.0.0.0[7f6fe06fb000+13a000]

Using journalctl -r, I see:

Aug 10 21:30:00 skutter systemd-coredump[5617]: Process 5609 (gnome-shell) of user 42 dumped core.

                                                     Stack trace of thread 5609:
                                                     #0  0x00007f6fe074a7e4 center_pointer (libmutter-0.so.0)
                                                     #1  0x00007f6fe075ead9 meta_backend_x11_post_init (libmutter-0.so.0)
                                                     #2  0x00007f6fe075fb19 meta_backend_x11_cm_post_init (libmutter-0.so.0)
                                                     #3  0x00007f6fe0789586 meta_init (libmutter-0.so.0)
                                                     #4  0x0000557a42b081aa main (gnome-shell)
                                                     #5  0x00007f6fda1a64da __libc_start_main (libc.so.6)
                                                     #6  0x0000557a42b085ba _start (gnome-shell)

                                                     Stack trace of thread 5613:
                                                     #0  0x00007f6fda28aa9d poll (libc.so.6)
                                                     #1  0x00007f6fdbd6c569 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd6c902 g_main_loop_run (libglib-2.0.so.0)
                                                     #3  0x00007f6fdd891cb6 gdbus_shared_thread_func (libgio-2.0.so.0)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)

                                                     Stack trace of thread 5614:
                                                     #0  0x00007f6fda291529 syscall (libc.so.6)
                                                     #1  0x00007f6fdbdb16fa g_cond_wait_until (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd40b31 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0)
                                                     #3  0x00007f6fdbd93ed4 g_thread_pool_thread_proxy (libglib-2.0.so.0)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)

                                                     Stack trace of thread 5610:
                                                     #0  0x00007f6fda28aa9d poll (libc.so.6)
                                                     #1  0x00007f6fdbd6c569 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd6c67c g_main_context_iteration (libglib-2.0.so.0)
                                                     #3  0x00007f6fdbd6c6c1 glib_worker_main (libglib-2.0.so.0)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)

                                                     Stack trace of thread 5615:
                                                     #0  0x00007f6fda28aa9d poll (libc.so.6)
                                                     #1  0x00007f6fdbd6c569 g_main_context_iterate.isra.25 (libglib-2.0.so.0)
                                                     #2  0x00007f6fdbd6c67c g_main_context_iteration (libglib-2.0.so.0)
                                                     #3  0x00007f6fb6f84f3d dconf_gdbus_worker_thread (libdconfsettings.so)
                                                     #4  0x00007f6fdbd93536 g_thread_proxy (libglib-2.0.so.0)
                                                     #5  0x00007f6fda55e36d start_thread (libpthread.so.0)
                                                     #6  0x00007f6fda296b8f __clone (libc.so.6)
Aug 10 21:30:00 skutter gnome-session[5570]: Unable to init server: Could not connect: Connection refused
Aug 10 21:30:00 skutter spice-vdagent[5623]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Aug 10 21:30:00 skutter gnome-session-binary[5570]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
Aug 10 21:30:00 skutter gnome-session-binary[5570]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Aug 10 21:30:00 skutter gnome-session-binary[5570 ...
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2017-08-18 05:00:45 +0000

psg_nm gravatar image

After reading up on the Nvidia drivers some, I discovered at least one issue. The Linux kernel command line for my installation had nomodeset included, which according to https://wiki.debian.org/InstallingDebianOn/Dell/Precision%205520%20%28Laptop%29/jessie will cause problems. Once I removed nomodeset from /etc/sysconfig/grub and then ran grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg since I have an EFI system (See Fedora Wiki: Grub 2), GDM no longer crashes during start up when I have the Nvidia proprietary drivers installed. In the end I believe that this actually allowed the Intel drivers to load properly, which were apparently important for GDM (and Gnome 3) to run using Wayland.

Not that it probably matters, but I am using the negativo17.org Nvidia packages again. So far so good.

Anyway, that is how this problem was solved. For me, there is still more to figure out with regard to Nvidia Optimus and Fedora, but now things are working much better.

edit flag offensive delete link more


I did this earlier this afternoon on my new Dell Precision 5520 amd I almost get to the full eyeball and then it hangs. What do you think I need to do to fix this issue?

RedMill_1 ( 2017-08-19 01:34:16 +0000 )edit

Where are you in the process? Do you have the Nvidia drivers installed? Have you removed the nomodeset from GRUB 2?

I should mention that to test this fix, I edited the linuxefi line for the default kernel interactively within GRUB 2 by hitting the letter "e" when the GRUB menu pops up with the default kernel. In my case, there was a line starting with linuxefi that included the nomodeset setting. I deleted nomodeset from that line interactively and hit Ctrl-x to start Fedora with the modified settings. Once this worked, I did the modifications mentioned above.

psg_nm ( 2017-08-20 02:34:47 +0000 )edit

I only removed nomedeset from GRUB2. No nvidia drivers are installed.


RedMill_1 ( 2017-08-20 16:19:31 +0000 )edit

Here is effectively what I did:

  1. After the initial installation of Fedora 25 and then an upgrade to Fedora 26, the nouveau driver was installed by default. I followed the instructions at Negativo17 to install the proprietary Nvidia drivers.
  2. I removed the nomodeset from GRUB 2 so the Intel video driver loads properly.
  3. Reboot (and hopefully enjoy).

In your situation, you can probably use Ctrl-Alt-F4 to transition to a command line terminal and install the proprietary Nvidia drivers if the graphical environment doesn't come up.

psg_nm ( 2017-08-20 23:11:34 +0000 )edit

When I installed the proprietary drivers I specifically ran the following: sudo dnf install nvidia-settings kernel-devel dkms-nvidia vulkan.i686 nvidia-driver-libs.i686 so 32-bit libraries were installed.

When you use Ctrl-Alt-F4 to get a console, you should be able to install the Nvidia drivers and do a sudo reboot to get the changes to take effect.

When the proprietary driver installs, it also disables the nouveau driver by adding rd.driver.blacklist=nouveau to the linuxefi line for GRUB 2. You could add that interactively to GRUB for now to start with the Intel drivers.

psg_nm ( 2017-08-20 23:35:04 +0000 )edit

Your Answer

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

Add Answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers. If a question you asked has been answered, accept the best answer by clicking on the checkbox on the left side of the answer.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Question Tools

1 follower


Asked: 2017-08-11 04:46:57 +0000

Seen: 260 times

Last updated: Aug 18 '17