When selection a multi-line URI in a terminal window
I've noticed two behaviors. Some will ?ignore? the
extra lines and only select to the end of the first
line. Others will select the entire URI, typically
to an ending ">". Obviously I would prefer the latter.
Is this behavior terminal specific, i.e. gnome-terminal
vs mate-terminal vs xterm. Or is it a configuration
parameter that I've not found?
Jon H. LaBadie jonfu(a)jgcomp.com
Dell T7500 won’t boot on 4.19.13 or later from fedora updates for F29. 4.19.10 works. 4.19.11 and 4.19.12 from Koji boot as well. No output after Probing EDD on vga console starting with 4.19.13 through the latest today, 4.9.15.
I'm encountering a strange issue with Gnome-Boxes and SELinux running
If SELinux is in enforcing mode, the VM can not be started. I get only
a nonsense error message that tells me it is impossible to startup.
Then, after checking the file permissions, I set SELinux to permissive
mode with 'setenforce 0'. Then, the VMs start without any problem.
I also did relablel the entire filesystem without success.
Sidenote: I had to reinstall F29 after trying the mls policy, 'cause it
f*cked up my system.
As told, I relabeled the whole filesystem after this reinstallation
just to ensure a proper labeled home partition, which I did not erase.
Do I have to set a special label for some subdirectories which are not
52064 Aachen, Germany
GPG: DDCB AF8E 0132 AA54 20AB B864 4081 0B18 1ED8 E838
Gee, I Thought I had Java installed, but just got the message:
This product requires the Java language, which is either disabled or not
available on this browser.
To use this product you must either upgrade your browser to one that is
Java compliant, or enable the Java language on your current browser.
How do I check what is needed and how to get it working...
rpm -q gstreamer1-plugins-ugly
sudo dnf upgrade
Problem: package gstreamer1-plugins-ugly-1.14.4-2.fc29.x86_64 requires
libx264.so.155()(64bit), but none of the providers can be installed
I'm using a newer version of x264, and rebuilt plugins-ugly with it. Why
does dnf keep trying to install the repo version. What rule does dnf
follow that overrides the the package version name ? And can you
override the override ?
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
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?
I am following this wiki 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
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.
- 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
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)
- Do I have any firewall/iptable running?
# systemctl status firewalld.service
Loaded: masked (Reason: Unit firewalld.service is masked.)
Active: inactive (dead)
What am I doing wrong? How can I debug this issue?
Thank you for help.
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?
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.