No Video Following Update
by David Dembrow
A recent fedora 23 update included kernel 4.3.3-300 and breaks the
video. The video module that is causing the problem is the i915 (actual
hardware is Intel 945GM). Is there a know workaround better than
booting up on the previous kernel (4.2.8-300)?
8 years, 3 months
will downgrade fedora kernel break libvirt features ?
by thibaut noah
Hello, i use fedora 23 with kernel 4.2.5 to run a win10 vm using qemu/kvm
with vga passthrough (vfio).
I purchased a raid pci card, the problem is got is the compatibility for
the driver stop at kernel 4.0.4
Is it possible to downgrade the kernel to install the driver?
If i do will i still be able to run my virtual machine without changing
everything?
8 years, 3 months
firewalld and source/dest rules?
by Alex
Hi,
I have a fedora23 system and just starting to learn how firewalld
works. None of the documentation really discusses how to add rules
from a specific source (the -s option with iptables).
Is this not what firewalld was intended to do?
How do I restrict access to ssh or dns only from specific remote IP addresses?
I've found the "rich" rules, but if I have to create rules at the port
level without any association to the service, then I don't understand
the point of using it. In other words, it appears necessary to add
additional manual rules, while also having to "--add-service=dns"
instead of the dns service taking care of it all in the first place.
In other words, to create a "rich" rule for dns, it appears necessary to do:
firewall-cmd --add-rich-rule='rule family="ipv4" source
address="192.168.1.0/24" port port=53 protocol="tcp" accept'
--permanent
firewall-cmd --add-rich-rule='rule family="ipv4" source
address="192.168.1.0/24" port port=53 protocol="udp" accept'
--permanent
and that also doesn't provide the ability to control the "state" of the packets.
Thanks for any ideas.
Alex
8 years, 3 months
disk encryption
by Jeffrey Ross
I installed Fedora 23 on a Laptop a while back and I decided to use disk
encryption. At this point I find the disk encryption to be more of a
hindrance and would like to remove it.
Am I correct that it may simply be easier to re-install the system
rather than try to remove the encryption or is there an easy way to
remove it?
Thanks, Jeff
8 years, 3 months
Lexar jumpdrive and Linux support
by Alex
Hi,
I just purchased a Lexar Jumpdrive S25 2x32GB USB sticks and just
noticed it has some kind of built-in encryption. Any chance it's
supported with Linux? What is it exactly?
Before I open the package, I thought I'd post a message to see what
people's experience has been with them?
I didn't notice the encryption support until after I purchased it. I
thought I recalled there being a problem with some USB sticks with
encryption and support for Linux, so I thought I'd see if that was
still the case before opening the package.
Thanks,
Alex
8 years, 3 months
WARNING you cannot build info or html versions of the R manuals
by Rolf Turner
It's no big deal, but when I build R from source (as I must) I always
get the warning given in the subject line of this post.
I have searched the web a bit and have found a number of references to
this warning. Universally the proffered solution is "install texinfo".
So I did (just now)
sudo yum install texinfo
and was told:
> Package texinfo-4.13a-16.fc17.x86_64 already installed and latest version
> Nothing to do
I checked with "whereis texinfo" and got:
> texinfo: /usr/share/texinfo /usr/share/man/man5/texinfo.5.gz
So it's there on my system --- but perhaps not where R can find it???
Can anyone suggest to me what I need to do to get R and texinfo to
cooperate?
Please note that I am running Fedora 17. Yes, I know, it's
antediluvian. But for reasons I do not wish to discuss, I'm stuck
there. (This is one of the reasons why I must build R from source.
It all works fine, except for that warning.)
cheers,
Rolf Turner
--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276
8 years, 3 months
Can you suggest a way to get SELinux back in order?
by Doug H.
After about a day of not having crontabs running I realized that
SELinux was stopping both user and root crontab jobs. I messed with it
and then discovered:
https://bugzilla.redhat.com/show_bug.cgi?id=1298192
(Recent dnf updates caused crontabs to be restricted. Reboot to last
kernel fixes that.)
I added myself to that bug but I had already broken SELinux to the
point where it would not work properly even if I rebooted to the
previous kernel. I was willing to be stupid/brave about messing with
it since I figure that if I can't get it back in order then I don't
know enough about it. A full relabel takes about ten minutes on my
system, so it is not terrible.
I have been with "Fedora" since it was "Redhat 5.0" but only enabled
SELinux after upgrading to F23. This bug keeps making me want to go
back to "disabled" but then I come back to it and do some more
googling.
My last attempt to fix it was with:
(reformatted to easier reading)
dnf reinstall
libselinux-utils
selinux-policy
libselinux-devel
libselinux-python3
libselinux.i686
libselinux-python
selinux-policy-targeted
rpm-plugin-selinux
libselinux.x86_64
Then a reboot to do the relabel and run with "permissive" to debug. It
had lots of issues. I suspect that most were simply that I was doing
working as the admin for my machine and that was not properly set.
My question:
Can anybody suggest a series of steps to put my F23 SELinux
installation in line with the default workstation install of F23?
Note that I was previously running:
setsebool -P httpd_enable_homedirs 1
setsebool -P httpd_read_user_content 1
I happen to have a personal use web server running out of /home/httpd
and I would rather leave it there since /home is a partition. The
point being that I am fine with running the basic allows that SELinux
Troubleshooter identified when I first enabled it.
--
Doug H.
8 years, 3 months
Previous message sent in error.
by Rolf Turner
The message that I sent to this list, a few minutes ago (with subject
line "WARNING you cannot build info or html versions of the R manuals")
was sent here by mistake. I *intended* it to go to r-sig-fedora, and
messed up.
I have re-sent this message to the address that I originally intended.
My apologies for the inadvertent cross-posting.
cheers,
Rolf Turner
--
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276
8 years, 3 months
Anyone seeing spurious characters in their text?
by Temlakos
With the latest Fedora kernel build (4.2.8-200.fc22.x86_64), I see this
behavior:
A string of spurious characters, beginning with a digit 6 and continuing with an unending stream of digit-8 characters, suddenly appears and fills whatever text workspace, dialog box, etc. currently has the focus. If the application has the focus, these spurious characters act like keystrokes attempting to initiate a keyboard-triggered menu command or other command.
Sometimes the string consists of digits 5. This can cause a problem with applications like Thunderbird, which uses digit 5 as a command to toggle the "can wait" flag on a piece of e-mail.
Version-Release number of selected component (if applicable):
4.2.8-200.fc22.x86_64
How reproducible:
Happens at random during a session with any application putting a focus on a particular text working area or other area sensitive to keystrokes of any kind.
Steps to Reproduce:
1. Start a browser, a word processor, a text editor, or any other application having a text working area of any kind.
2. Place the focus on a particular text working area. For safety's sake, do this in an empty document in a plain-text editor, like KWrite.
3. Watch and wait. (Although sometimes spurious characters will appear as you type!)
Actual results:
Without your typing anything, the machine will start with a digit 6 and then continue with an unbreaking string of 8's. The only way to break it is with another keystroke of your own. After that you have to erase the spurious characters.
Sometimes the machine will throw a number "68" into your text as you are typing. This leaves you with a typographical error you must correct. And it can salt your text with typographical errors requiring as much time to remove as it took to type the text to begin with!
Expected results:
No character, of any description, should appear without your striking a key.
Additional info:
This error has occurred before. It crops up on occasion with a kernel update and vanishes one or at most two updates later. Everyone knows about it. Before now, it was a Plague of Fives. Now it is a Plague of Eights.
A spurious number 68 introduced itself into my text as I was typing this report.
The nature of the error, and its apparent dependency on versions of the kernel, should preclude any consideration of a hardware fault like "sticking keys."
Filed with Bugzilla as Bug No. 1299130. Assigned to the Kernel
Maintainers' Group. Add this to it: I fell back on the next earlier
version of the kernel. And the problem vanished. So let no one say I'm
just typing on a keyboard with sticky keys. Temlakos
8 years, 3 months
