The small linux problem thread

/var/log/messages or in journalctl

would be useful to run fpaste --sysinfo as well

1 Like

Only journalctl is working. In /var/log/messages is nothing there and fpaste --sysinfo is loading for ever.
The journalctl is going back to Jan 2. How can i quickliy jump to april. I tride with grep but it filters only the text. Sorry newb here.

Usually means theres something not right at all. all fpaste does is run some standard commands. could try without uploading fpaste --sysinfo --printonly (maybe run as root)

try some of the following to get more info

sestatus
lsb_release -ds
uname -r ; cat /proc/cmdline
df -hT
dmesg | tail
dnf -C repolist
dnf -C list extras
rpm -qa --nodigest --nosignature --last | head -20

for logs that your asking about

For current boot:

journalxtl -xb

For april:

journalctl -x --since=2017-04-01

for warnings only add to the command

-p warning or -p 4

for errors only add to the command

-p err or -p 3

for all alerts, critical, errors, and warnings

-p 1..4
1 Like

fpaste is working forgot to run it with sudo... here is the link i got:
https://paste.fedoraproject.org/paste/Xs9vE-Lt5RuIvtGD8--FD15M1UNdIGYhyRLivL9gydE=

journalctl -xb -p3 is giving this:

-- Logs begin at Sun 2017-01-15 15:50:35 CET, end at Sat 2017-04-01 21:05:25 CEST. --
Apr 01 20:57:14 phobos-alpha avahi-daemon[962]: chroot.c: open() failed: No such file or directory
Apr 01 20:57:14 phobos-alpha bluetoothd[910]: Failed to set mode: Blocked through rfkill (0x12)
Apr 01 20:57:17 phobos-alpha abrtd[1048]: '/var/spool/abrt/ccpp-2017-02-08-10:51:08-2056.new' is not a problem dire
Apr 01 20:57:41 phobos-alpha nmbd[1234]: [2017/04/01 20:57:41.818083,  0] ../lib/util/become_daemon.c:135(daemon_st
Apr 01 20:57:41 phobos-alpha nmbd[1234]:   STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, 
Apr 01 20:57:51 phobos-alpha nmbd[1234]: [2017/04/01 20:57:51.858521,  0] ../lib/util/become_daemon.c:124(daemon_re
Apr 01 20:57:51 phobos-alpha nmbd[1234]:   STATUS=daemon 'nmbd' finished starting up and ready to serve connections
Apr 01 20:57:52 phobos-alpha smbd[1524]: [2017/04/01 20:57:52.794954,  0] ../lib/util/become_daemon.c:124(daemon_re
Apr 01 20:57:52 phobos-alpha smbd[1524]:   STATUS=daemon 'smbd' finished starting up and ready to serve connections
Apr 01 20:58:00 phobos-alpha setroubleshoot[1549]: SELinux is preventing gnome-shell from execute access on the fil
Apr 01 20:58:01 phobos-alpha spice-vdagent[1579]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat
Apr 01 20:58:03 phobos-alpha bluetoothd[910]: Failed to set mode: Blocked through rfkill (0x12)
Apr 01 20:58:14 phobos-alpha nmbd[1234]: [2017/04/01 20:58:14.893709,  0] ../source3/nmbd/nmbd_become_lmb.c:397(bec
Apr 01 20:58:14 phobos-alpha nmbd[1234]:   *****
Apr 01 20:58:14 phobos-alpha nmbd[1234]:   
Apr 01 20:58:14 phobos-alpha nmbd[1234]:   Samba name server PHOBOS-ALPHA is now a local master browser for workgro
Apr 01 20:58:14 phobos-alpha nmbd[1234]:   
Apr 01 20:58:14 phobos-alpha nmbd[1234]:   *****
Apr 01 20:58:29 phobos-alpha spice-vdagent[1911]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat
Apr 01 20:58:30 phobos-alpha bluetoothd[910]: Failed to set mode: Blocked through rfkill (0x12)

that's missing some of the text can you run it again and fpaste it, might be useful using -p 1..3

journalctl -xb -p 1..3 | fpaste

Here you go:
https://paste.fedoraproject.org/paste/27oROmj5jWRU1vr9RC-CcV5M1UNdIGYhyRLivL9gydE=

Can you run:

sealert -l 088eb345-4074-44fd-8765-f8784ca9b5bd | fpaste

https://paste.fedoraproject.org/paste/YdvUhA1XxCSGHMtNzQ3XCV5M1UNdIGYhyRLivL9gydE=

Here's a little thorn in my side.

Using main menu doesn't bring up all the shortcuts in the program drawer in gnome. I always end up having to browse to the app folder with all the .desktop files... Any ideas?

Also (I haven't yet searched for a solution) where can I add launch arguments to executables? For instance the unreal tournament .so must be executed from terminal with a couple flags. If I double click the game crashes.

I don't know anything about the gnome menu, but you can just make a custom .desktop file for anything and call arguments in it.

[Desktop Entry]
Version=1.0
Name=
Comment=
GenericName=
Exec=path/to/program -arg -uments
Icon=
Terminal=false
Type=Application
Categories=

you can make as many as you need if you want different arguments for each. copy this file to /usr/shared/applications and it should show up in your programs menu, or ln -s

That's how I have to do it now. And it is far more cumbersome than it needs to be.

Should be on the shortcut, right click -> properties menu to add arguments. And that's if the desktop shortcut exists in the first place, which is another unnecessary pain in the butt.

Once you create the custom .desktop file though, it's as easy as opening it like you normally would, just with the correct .desktop file. It's no more cumbersome after creating it. However, I do agree that you shouldn't have to do it. It would be nice to be able to add runtime arguments through a right click menu, similar to how you can do it on steam games, or Windows shortcuts.

I think I broke light DM?

Normally I would just uninstall and reinstall Linux, but I figure I probably should figure out what to do

Can anyone maybe @Eden help?

I tried looking by opening light DM status and journal CTL


I mean its lightdm its not that hard. It pretty much breaks itself most of the time.

Install GDM and you'll be fine.

3 Likes

Is there a installation guide/which packages do I install? My connection to the Arch package search is crapping out on me.

Or is it just sudo Pacman -S gdm?
After installing gdm, is the configuration automatic, if not, what do I need to do for the configuration.

I might check back in the morning, so if I don't reply, I am probably asleep

And uninstalling lightdm yeah. Not sure on the config because when I do Arch from scratch I don't install a dm login for security reasons. Check the page.

1 Like

my lightdm breaks after suspend A LOT for some reason.

why? no idea. but could you do me a favour? could you log in as root and

"startx" 
"killall Xorg"
"startx"

for some weird reason this does the trick for me but i have no idea what exactly is broken and gets fixed by this.

journalctl -xb -u lightdm.service will give you more information.

3 Likes

WOW! Tank you! <3

1 Like

I got it up and running. Turns out i had to use
systemctl disable on the light dm
then enable it on gdm

but now my settings menu doesn't work

Is there a way for me to have antegeros repair itself by reinstalling the default apps?