tablets?
by ToddAndMargo
Hi All,
Any sign of Fedora on a tablet?
-T
5 years, 2 months
F28 problems with tftp server firewall permissions
by Robert Moskowitz
I am trying to set up tftp server on my workstation to manage some switches.
I have done the following:
dnf install tftp tftp-server
firewall-cmd --add-service=tftp --permanent
firewall-cmd --reload
systemctl start tftp
I can get files from a local terminal window with:
tftp localhost -cv file
I had problems with put until I saw that the file had to preexist. I did
that with touch file on my system.
From a F24 notebook on the same subnet as the one running tftp server,
though I cannot get the file. I get:
Transfer timed out.
I also tried:
firewall-cmd --add-port=69/udp --permanent
but no different.
I don't see anything in the tftp.service file to indicate anything there.
What am I missing?
thanks
5 years, 2 months
can't connect to localhost via Firefox
by arnaud gaboury
I am following this wiki[0] to run R Studio on my box. Below are the
commands I run
----------------------
# podman run -d -p 8787:8787 -e PASSWORD=XXX --name rstudio rocker/tidyverse
..........
Storing signatures
a72fac512b891c21f0654334a2032b0d67b87720cb986a092237ab272d245f8d
-----------------------------------
At this point, I am supposed to access the R studio app via my Firefox
browser on port 8787 on localhost, which I can't.
Debuging:
--------------------------------------------
- Is the container running?
# podman ls
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
a72fac512b89 docker.io/rocker/tidyverse:latest /init 2 minutes ago Up
2 minutes ago 0.0.0.0:8787->8787/tcp rstudio
-Is the 8787 port open?
# podman port a72fac512b89
8787/tcp -> 0.0.0.0:8787
# lsof -i -P -n | grep LISTEN
8:cupsd 984 root 8u IPv6 35102 0t0 TCP [::1]:631 (LISTEN)
9:cupsd 984 root 9u IPv4 35103 0t0 TCP 127.0.0.1:631
(LISTEN)
67:conmon 12891 root 5u IPv4 453576 0t0 TCP *:8787 (LISTEN)
- Can I ping localhost, 0.0.0.0, 127.0.0.1, yogabx (hostname), 192.168.1.92
(returned by ip -a)
YES
- Do I have any firewall/iptable running?
# systemctl status firewalld.service
● firewalld.service
Loaded: masked (Reason: Unit firewalld.service is masked.)
Active: inactive (dead)
NO iptables
---------------------------------------------------
What am I doing wrong? How can I debug this issue?
Thank you for help.
5 years, 2 months
Vagrant and terminal
by Sudheer S
Hello,
I am using Fedora release 29 (Twenty Nine) and Vagrant 2.1.2.
After I bring up the guest via: vagrant up
in most cases, the terminal starts acting up. The terminal does not
print or recognize the character typed on keyboard. Sometimes, if the
character is typed twice, it appears on the terminal window. The
terminal almost stops accepting the input from keyboard if there is an
error from running the command: vagrant up.
I had noticed this on Fedora 28 too.
Is something wrong on my Fedora installation? How can I correct this issue?
-
Sudheer
5 years, 2 months
Terminal Badness
by Beartooth
Mate terminal, that is -- not life threatening but intensely
irritating and anti-productive. When I click on any little x, in the
upper right either of the whole terminal or of one tab, the whole
terminal closes. It should, of course, close only the tab it's on when I
click the x on one tab.
It has done this every time I've tried to close a single tab,
since I've been running F 29.
--
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
5 years, 3 months
f29 auto logging out?
by Dan
I have a fresh F29 install that is hooked up to a TV to display a dashboard. I will often come in in the morning and I will see the dashboard, but as soon as I touch the mouse or the keyboard, I am logged out automatically and need to enter my user/password again to log back in.
I have verified that screen saver is set to Never. What else could be going on?
5 years, 3 months
F29 KDE weirdness
by Robert McBroom
Upgraded to F29. On KDE desktop starting EMACS in a privileged command
window locks the system. Starting EMACS with sudo locks the system. On
XFCE4 normal EMACS access with privilege.
Other file managers don't like root but there are times when cli is awkward.
5 years, 3 months
what hath systemd wroght?
by Tom Horsley
Suddenly (probably after installing systemd updates this morning)
it takes 30 seconds or so for an NIS user to login via ssh and
I see this nonsense show up in the log:
Jan 16 14:53:33 tomh systemd-logind[811]: New session 11 of user tom.
Jan 16 14:53:33 tomh systemd[1]: Failed to mount /userland.
Jan 16 14:53:33 tomh systemd-logind[811]: Session 11 logged out. Waiting for processes to exit.
Jan 16 14:53:33 tomh systemd-logind[811]: Removed session 11.
Jan 16 14:53:34 tomh systemd[3119]: Listening on Sound System.
Jan 16 14:53:34 tomh systemd[3119]: Starting D-Bus User Message Bus Socket.
Jan 16 14:53:34 tomh systemd[3119]: Listening on Multimedia System.
Jan 16 14:53:34 tomh systemd[3119]: Reached target Paths.
Jan 16 14:53:34 tomh systemd[3119]: Started Mark boot as successful after the user session has run 2 minutes.
Jan 16 14:53:34 tomh systemd[3119]: Reached target Timers.
Jan 16 14:53:34 tomh systemd[3119]: Listening on D-Bus User Message Bus Socket.
Jan 16 14:53:34 tomh systemd[3119]: Reached target Sockets.
Jan 16 14:53:34 tomh systemd[3119]: Reached target Basic System.
Jan 16 14:53:34 tomh systemd[3119]: Starting Sound Service...
Jan 16 14:53:34 tomh dbus-daemon[822]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.90" (uid=2304 pid=3129 comm="/usr/bin/pulseaudio --daemonize=no ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus)
Jan 16 14:53:34 tomh systemd[3119]: Started D-Bus User Message Bus.
Jan 16 14:53:34 tomh dbus-daemon[3157]: [session uid=2304 pid=3157] Activating service name='org.gnome.GConf' requested by ':1.1' (uid=2304 pid=3156 comm="/usr/libexec/pulse/gconf-helper ")
Jan 16 14:53:34 tomh dbus-daemon[3157]: [session uid=2304 pid=3157] Successfully activated service 'org.gnome.GConf'
Jan 16 14:53:34 tomh systemd[3119]: Started Sound Service.
Jan 16 14:53:34 tomh pulseaudio[3129]: E: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.90" (uid=2304 pid=3129 comm="/usr/bin/pulseaudio --daemonize=no ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (bus)
Jan 16 14:53:34 tomh systemd[3119]: Reached target Default.
Jan 16 14:53:34 tomh systemd[3119]: Startup finished in 690ms.
Jan 16 14:53:44 tomh systemd[3119]: Stopping D-Bus User Message Bus...
Jan 16 14:53:44 tomh systemd[3119]: Stopped target Default.
Jan 16 14:53:44 tomh systemd[3119]: Stopping Sound Service...
Jan 16 14:53:44 tomh systemd[3119]: Stopped D-Bus User Message Bus.
Jan 16 14:53:44 tomh systemd[3119]: Stopped Sound Service.
Jan 16 14:53:44 tomh systemd[3119]: Stopped target Basic System.
Jan 16 14:53:44 tomh systemd[3119]: Stopped target Paths.
Jan 16 14:53:44 tomh systemd[3119]: Stopped target Timers.
Jan 16 14:53:44 tomh systemd[3119]: Stopped Mark boot as successful after the user session has run 2 minutes.
Jan 16 14:53:44 tomh systemd[3119]: Stopped target Sockets.
Jan 16 14:53:44 tomh systemd[3119]: Closed Multimedia System.
Jan 16 14:53:44 tomh systemd[3119]: Closed D-Bus User Message Bus Socket.
Jan 16 14:53:44 tomh systemd[3119]: Closed Sound System.
Jan 16 14:53:44 tomh systemd[3119]: Reached target Shutdown.
Jan 16 14:53:44 tomh systemd[3119]: Starting Exit the Session...
Jan 16 14:53:44 tomh systemd[3119]: Received SIGRTMIN+24 from PID 3179 (kill).
Most of the delay follows that last message. Any idea how to make
NIS login work fast again?
If I login as a local user the only message I see is:
Jan 16 15:01:20 tomh systemd-logind[811]: New session 23 of user tweety.
and the login is immediate.
5 years, 3 months
livesys.service take longer time
by Danishka Navin
Hi,
May I know why livesys.service take longer time?
1min 53.212s livesys.service
7.042s rc-local.service
4.880s httpd-init.service
4.641s ldconfig.service
3.754s lvm2-pvscan@8:2.service
3.064s lvm2-monitor.service
2.359s systemd-udev-settle.service
2.356s udisks2.service
1.933s auditd.service
1.535s initrd-switch-root.service
1.500s dev-mapper-live\x2drw.device
1.136s polkit.service
--------------------------------------
livesys.service +1min 53.212s
└─basic.target @8.739s
└─sockets.target @8.739s
└─dbus.socket @8.739s
└─sysinit.target @8.739s
└─systemd-update-done.service @8.731s +7ms
└─ldconfig.service @4.088s +4.641s
└─local-fs.target @4.080s
└─var-tmp.mount @4.072s +6ms
└─local-fs-pre.target @4.071s
└─lvm2-monitor.service @989ms +3.064s
└─lvm2-lvmetad.service @3.987s
└─lvm2-lvmetad.socket @981ms
└─-.mount
└─system.slice
└─-.slice
----------------------------------------------------------
I dont use LDAP service
-- Logs begin at Fri 2019-01-18 02:55:11 EST, end at Fri 2019-01-18
04:40:01 EST. --
Jan 18 02:55:24 localhost livesys[922]: Enabling swap partition
/dev/mapper/hl_localhost--live->
Jan 18 02:55:24 localhost useradd[972]: new group: name=liveuser, GID=1000
Jan 18 02:55:24 localhost useradd[972]: new user: name=liveuser, UID=1000,
GID=1000, home=/home>
Jan 18 02:55:24 localhost livesys[922]: Adding live user (Fri Jan 18
02:55:24:954169 2019) [sss>
Jan 18 02:55:24 localhost livesys[922]: Could not open available domains
Jan 18 02:55:24 localhost livesys[922]: useradd: sss_cache exited with
status 2
Jan 18 02:55:24 localhost livesys[922]: useradd: Failed to flush the sssd
cache.
Jan 18 02:55:25 localhost livesys[922]: (Fri Jan 18 02:55:25:034921 2019)
[sss_cache] [confdb_g>
Jan 18 02:55:25 localhost livesys[922]: Could not open available domains
Jan 18 02:55:25 localhost livesys[922]: useradd: sss_cache exited with
status 2
Jan 18 02:55:25 localhost livesys[922]: useradd: Failed to flush the sssd
cache.
Jan 18 02:55:25 localhost livesys[922]: [ OK ]
Jan 18 02:55:25 localhost livesys[922]: passwd: Note: deleting a password
also unlocks the pass>
Jan 18 02:55:25 localhost usermod[985]: add 'liveuser' to group 'wheel'
Jan 18 02:55:25 localhost usermod[985]: add 'liveuser' to shadow group
'wheel'
Jan 18 02:55:25 localhost livesys[922]: (Fri Jan 18 02:55:25:187886 2019)
[sss_cache] [confdb_g>
Jan 18 02:55:25 localhost livesys[922]: Could not open available domains
Jan 18 02:55:25 localhost livesys[922]: usermod: sss_cache exited with
status 2
Jan 18 02:55:25 localhost livesys[922]: usermod: Failed to flush the sssd
cache.
Jan 18 02:55:25 localhost livesys[922]: (Fri Jan 18 02:55:25:272265 2019)
[sss_cache] [confdb_g>
Jan 18 02:55:25 localhost livesys[922]: Could not open available domains
Jan 18 02:55:25 localhost livesys[922]: usermod: sss_cache exited with
status 2
Jan 18 02:55:25 localhost livesys[922]: usermod: Failed to flush the sssd
cache.
Jan 18 02:55:25 localhost livesys[922]: No such schema “org.gnome.software”
Jan 18 02:55:25 localhost livesys[922]: Created symlink
/etc/systemd/system/multi-user.target.w>
Jan 18 02:55:27 localhost livesys[922]: Created symlink
/etc/systemd/system/multi-user.target.w>
lines 1-27
Regards,
--
Danishka Navin
http://danishkanavin.blogspot.com
http://twitter.com/danishkanavin
5 years, 3 months
nm-dispatcher connectivity-change
by Hiisi
Dear users!
Since recently I'm unable to boot my system (f28) with the following
problem. It start to boot normally and just before the login screen would
normally appear it drops into terminal with some messages regarding
nm-dispatcher connectivity-change. It says something that it runs some
scripts but it stucks there forever. I've been messing with python earlier
today. Could it possibly be the cause? I'm able to boot the laptop from
live-usb (this is how I write to the list now), so it shouldn't be a
hardware issue. I was trying to google it but seems people having this
problem with their systems running (unlike mine). Is there a way to fix my
OS without the pain of reinstalling?
TIA
--
Hiisi.
Registered Linux User #487982. Be counted at: https://linuxcounter.net/
--
Spandex is a privilege, not a right.
5 years, 3 months