Ask Your Question

psg_nm's profile - activity

2019-01-23 01:22:32 -0500 commented question XFCE login stuck

It is a bit of a shot in the dark, but you might check to see if you are getting any SELinux denials/errors. There are

2019-01-23 01:01:07 -0500 answered a question Fedora 28 Server install failure

Considering that the system is using a Matrox MGA G200 video card (mgag200), I ran across the following articles that se

2019-01-19 08:51:00 -0500 commented question Fedora 29 boot hangs at "Started GNOME display manager"

If you can confirm that GDM is crashing using the instructions above, you might replace GDM with another display manager

2019-01-19 08:43:36 -0500 commented answer Problems starting Fedora 29

Assuming you can login as suggested in the previous comments, you might try replacing GDM with a different display manag

2019-01-19 08:39:38 -0500 commented answer Problems starting Fedora 29

As another approach, at the black screen, type Ctrl-Alt-F2 (or similar) to get to a console virtual terminal. At that p

2019-01-19 08:25:06 -0500 commented question Fedora 29 boot hangs at "Started GNOME display manager"

It sounds to me that the GNOME display manager (gdm) has crashed. To debug the problem, type Ctrl-Alt-F2 to get to a vi

2019-01-19 00:16:56 -0500 commented question can't start my sql

It is a bit hard to read. If you indent each line of the output with 4 spaces (Markdown markup for code snippets) it wi

2019-01-18 23:43:04 -0500 commented question Fedora 28 Server install failure

Poking around a little bit, I ran across the following: https://elrepo.org/bugs/view.php?id=668 https://bugzilla.redha

2019-01-18 23:42:03 -0500 commented question Fedora 28 Server install failure

Poking around a little bit, I ran across the following: https://elrepo.org/bugs/view.php?id=668 https://bugzilla.redhat

2019-01-16 23:12:22 -0500 commented question Fedora 28 Server install failure

The dmesg output says the following: [ 6.225165] mgag200 0000:01:00.0: Video card doesn't support cursors with part

2019-01-16 22:35:14 -0500 answered a question Fedora 29 KDE : WiFi + KWallet issue durig startup

I have seen the same problem with the Fedora 29 KDE Spin. I agree that integration with KDEWallet is probably involved.

2019-01-16 21:45:07 -0500 received badge  Notable Question (source)
2019-01-16 21:45:07 -0500 received badge  Famous Question (source)
2019-01-16 21:45:07 -0500 received badge  Popular Question (source)
2019-01-04 00:44:35 -0500 commented answer Should I update my Fedora 25 Workstation and if so how can I do it

I agree that reinstalling would probably be the best option. If your home directory is in its own partition or LVM logi

2019-01-01 01:25:32 -0500 commented answer Problems starting Fedora 29

If you do find "nomodeset", you can try removing the "nomodeset" parameter as an experiment by typing "e" at the GRUB me

2019-01-01 01:14:05 -0500 commented answer Problems starting Fedora 29

I agree with @ewt - this sounds like a problem with the NVIDIA proprietary drivers. If they are installed, check to see

2019-01-01 01:12:52 -0500 commented answer Problems starting Fedora 29

I agree with @ewt - this sounds like a problem with the NVIDIA proprietary drivers. If they are installed, check to see

2018-11-10 19:31:33 -0500 received badge  Notable Question (source)
2018-11-10 19:31:33 -0500 received badge  Famous Question (source)
2018-01-26 12:59:29 -0500 answered a question ssh-agent not running by default in Xfce

As noted above by villykruse, you can use the GNOME (or KDE) services to handle this.

If you don't want to run the GNOME or KDE services at startup under Xfce, you can simply run ssh-add in a terminal to add your private key identity to the authentication agent (ssh-agent).

I had jumped to conclusions that ssh-agent wasn't running when I kept getting prompted for my SSH passphrase. As noted in my comment above, I ran ps aux | grep ssh-agent and confirmed that Xfce was actually starting up ssh-agent for me (sorry for the confusion).

At that point, I realized that I had been so spoiled with GNOME and KDE, which automatically ask you for your SSH passphrase during a desktop session the first time you try to use ssh. After you provide the SSH passphrase to GNOME or KDE, that private key identity is registered with the equivalent ssh-agent for the session.

For the stock Xfce installation (using dnf as described in the question above), which doesn't automatically run the GNOME or KDE services, you need to run ssh-add manually--something I haven't had to do for a while--or you can configure Xfce to run the GNOME or KDE services at startup (as villykruse explains).

2018-01-26 12:21:28 -0500 received badge  Commentator
2018-01-26 12:21:28 -0500 commented answer ssh-agent not running by default in Xfce

Thanks for the response. I sounds like a good solution.

What I realize now is that ssh-agent is actually running (I checked with ps aux | grep ssh-agent--I jumped to conclusions earlier) and I have been spoiled by GNOME and KDE, which do the ssh-add function for you by automatically prompting you for the passphrase when you first try using ssh.

Since ssh-agent is running, I remembered that I can manually use ssh-add in a terminal to add my private key identity to the the authentication agent (ssh-agent) for the session--it has been a while since I've needed to do that.

2018-01-25 23:59:51 -0500 received badge  Popular Question (source)
2018-01-25 23:54:14 -0500 asked a question ssh-agent not running by default in Xfce

I recently installed Xfce using the dnf groupinstall "Xfce Desktop" on a stock Fedora 27 machine (i.e., I am not using the Xfce Spin). When trying to ssh from the machine to other machines, I noticed that ssh-agent must not have been running as a part of the startup of Xfce because I had to repeatedly put in my ssh passphrase. When using Gnome 3 or Plasma on the same system, I only have to enter my ssh passphrase once per session.

Is there some setting I need to modify or add to enable ssh-agent on Xfce session startup? Any guess why this doesn't work when installed with "dnf" already? Seems like a bug.

2017-09-11 23:36:59 -0500 received badge  Supporter (source)
2017-08-20 18:35:04 -0500 commented answer libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

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.

2017-08-20 18:11:34 -0500 commented answer libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

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.

2017-08-19 21:34:47 -0500 commented answer libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

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.

2017-08-18 00:00:45 -0500 answered a question libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

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.

2017-08-13 23:51:57 -0500 commented question libprotobuf.so.9 is missing after update

Here are some links to information on libprotobuf:

Basically, it is a library from Google for 'serializing' data structures, making it easier to store and communicate information in a language-neutral and platform-neutral way.

As for why a recompile fixed things, maybe the old binary had some library path encoded in it that doesn't exist anymore. There are probably many other possibilities.

By the way, it does look like you can install it directly from the Fedora repos since Fedora 24.

2017-08-13 23:33:09 -0500 commented question Nylas Mail installed but wont load

I spun up a clean Fedora 26 VM curious to see if I could recreate the problem. Sure enough, when I installed Nylas Mail in the VM, the software did not start up. When I ran the software on the command line (nylas-mail), I saw the following error: nylas-mail: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory . I looked up the package on my main Fedora 26 machine (rpm -q -f /usr/lib64/libXss.so.1) and libXss.so.1 is provided by libXScrnSaver. After I ran sudo dnf install libXScrnSaver, Nylas Mail starts.

2017-08-12 23:10:33 -0500 commented answer Basic firewall setup

For more detailed information on firewalld, I would suggest looking at the firewalld documentation as well.

2017-08-12 22:51:42 -0500 commented answer Nylas Mail installed but wont load

I think the updates that are being referred to in the question above and the linked post are updates to Fedora itself and not to the Nylas Mail application.

Also, you are correct that dnf is not useful for automatically updating applications that didn't come from a DNF/YUM repository, but it is worth noting that dnf can be used to install and remove standalone RPMs (i.e., RPMs not from a repo). In fact, if you do use dnf instead of just rpm to do the installation it can resolve what dependencies it can from the available repos during installation, which can be very convenient.

2017-08-12 22:27:14 -0500 commented question Nylas Mail installed but wont load

Did you see any errors when trying to run nylas-mail from the command line? If so, please post them. I just tried installing Nylas Mail and running from both the Gnome Activities menus and from the command line under Fedora 26 and it doesn't seem to have any problems for me. I also have SELinux in Enforcing mode, so that doesn't seem to be special. As an Electron application, it appears to have very few Fedora dependencies (libgnome-keyring and rpmlib). You might remove the RPM and install the latest from the website.

2017-08-12 17:33:30 -0500 commented answer how to find and open this installed program?

In the output of rpm -q -l draftsight see if there are files installed in /usr/bin or /usr/local/bin (or a similar place). Those would likely be the files to try to execute. Otherwise, you might execute the following to find the executable files:

files=`rpm -q -l draftsight`; for i in $files; do ls -alF $i | grep "\\-..x..x..x"; done

This command records the files from the draftsight RPM in the files variable, performs an ls -alF on each of the files, and prints out only files that everyone can execute, ignoring links and directories. Ignore .so files, they are libraries.

2017-08-12 08:30:40 -0500 received badge  Nice Answer (source)
2017-08-12 05:35:07 -0500 received badge  Teacher (source)
2017-08-12 02:59:17 -0500 answered a question how to find and open this installed program?

As fcomida said, you might be able to simply run the program as draftsight on the command line.

To find out more about the files in a package, I will frequently run rpm -q -l <name of package>. If just running draftsight doesn't work, try running rpm -q -l draftsight to figure out the name of the program and its location in the file system.

2017-08-11 08:57:47 -0500 commented question Can't access Software centre on fedora 26t

I suggest trying to run gnome-software from the command line (i.e., in a terminal), capturing the console output, and posting the console output so we can see what errors are generated. That might give people some hints regarding the source of the problem.

2017-08-11 01:22:18 -0500 asked a question libmutter segfaulting when Nvidia drivers are installed (Fedora 26)

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 ...
(more)