This is a minor irritation, at least afaik: I'd fix it if I could
AND saw an easy way to.
I live by the Fedora workspace switcher -- probably the most
valuable applet I have, because it's so easy to set and forget. I have
canonical spaces for my terminal (with several tabs, my other most used
applet), my default browser (one that can handle long URLs, meaning
Firefox or Seamonkey unless I'm missing a good third one), one other
(varying) browser, my newsreader (All hail Pan!), and a space right below
it for writing posts. There are also several usually free spaces
scattered among those, so that I can bring up anything else conveniently,
and see the canonicals out of the corner of my eye.
I also upgrade every day, and reboot whenever there's a kernel
change. I suppose I should close the canonical applets, but I often
don't. Then when the reboot finishes, they all show up on the upper left
space, and I have to rearrange them. IFF, and I do mean only if, it would
be easy to make them launch where they were before, that would make the
workspace switcher even more valuable.
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
(F-30; Gnome; stand-alone home workstation)
Sometime last year, I saw an article that talked about a tool that
quickly and easily shows attempts to hack in to a computer. I think it
was either in the Fedora magazine or Gnome's website. I've since made
multiple attempts to find that article, but failed. I'm needing to
check for hack-in attempts (something I suppose I should do
quazi-periodically anyway). What is the tool/application to do that? If
such a tool/application does not exist, then what is the best way for me
to do that?
After any updates I must remember to run "rkhunter --propupd".
Is it possible to do this automatically?
There is some dnf plugins that does this?
-- Dario Lesca
(inviato dal mio Linux Fedora 31 Workstation)
Fedora Workstation 31
I was doing a dnf upgrade (which I aborted), when I got the message:
Removing dependent packages:
kmod-nvidia-5.4.18-200.fc31.x86_64 x86_64 3:440.59-1.fc31 @@commandline 30 M
I assume this package is dependent on kernel 5.4 and the dnf upgrade includes kernel 5.5.
So, I did
[simon@hedgehog ~]$ dnf list kmod-nvidia*
Last metadata expiration check: 0:00:10 ago on Sat 22 Feb 2020 08:51:05 GMT.
kmod-nvidia-5.4.18-200.fc31.x86_64.x86_64 3:440.59-1.fc31 @@commandline
kmod-nvidia-5.4.19-200.fc31.x86_64.x86_64 3:440.59-1.fc31 @@commandline
kmod-nvidia-5.4.20-200.fc31.x86_64.x86_64 3:440.59-1.fc31 @@commandline
kmod-nvidia.x86_64 3:440.59-1.fc31 rpmfusion-nonfree-nvidia-driver
Now, the kmod-nvidia package says that it is a meta-package to ensure the nvidia module(s) for the newest kernel.
So, my questions are:
1. Should I remove the installed nvidia packages and replace them with the meta-package?
2. Does the 'dnf list' imply that the nvidia packages for kernel 5.5 are not ready yet?
3. I don't want to upgrade the kernel until the nvidia package is available. What's the best way to monitor that?
I am looking for a pad to handwrite on both Fedora and MS Windows. I
am a total novice regarding that type of pads, so some help and
direction will be most appreciated.
The same pad is to be used also on MS Windows.
Mostly, the pad is to deliver my lectures instead of using blackboard.
Thanks in advance for your help,
I've been reading the thread about detecting hack attempts and I am
interested in in setting up "key based authentication" as described
In doing this is their danger of making an error and locking myself out
of my computer, if so what to avoid? I've made some catastrophic errors
in the not very distant past that required a new system re-installation
and would prefer not repeating that.
Bob Goodwin - Zuni, Virginia,
Fedora Linux-31 XFCE
This is probably something super simple, but…
My httpd is failing on boot.
The server has 3x adaptors, all are static IPs and don’t require DHCP or anything. Addresses, etc are specified in the config files. All are present once boot has ended. All are managed by NetworkManager, yet I get this error in the log
Feb 21 07:40:15 <server> systemd: Starting The Apache HTTP Server...
Feb 21 07:40:16 <server> httpd: [Fri Feb 21 07:40:16.208953 2020] [so:warn] [pid 1012:tid 140114180026688] AH01574: module ssl_module is already loaded, skipping
Feb 21 07:40:16 <server> httpd: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address <my ip>:80
Feb 21 07:40:16 <server> httpd: no listening sockets available, shutting down
Feb 21 07:40:16 <server> httpd: AH00015: Unable to open logs
Feb 21 07:40:16 <server> systemd: httpd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 07:40:16 <server> systemd: httpd.service: Failed with result 'exit-code'.
Feb 21 07:40:16 <server> systemd: Failed to start The Apache HTTP Server.
It’s like httpd is starting too early.
Looking at the service info I can see it’s supposed to start after network.target. Looking at its critical chain using systemd-analyze it seems to be doing this correctly. I’m kinda at a loss. Does anyone have any suggestions as to what I can try?
An infection seems to be spreading in systemd. First
I saw dhcpd taking forever to shut down:
Now I just saw the exact same thing with the apache
I found the systemctl --no-ask-password option, so
I tried it, now it no longer forks and execs the
password-agent process, it merely sits like a lump
timing out for the same amount of time.
Anyone have any idea what leads systemd to decide
it needs to wait for some mysterious something
when stopping some services? And why is the number
of these mysterious services growing? (Does this
have something to do with me not using NetworkManager?)
When I suspend my computer, it suspends for a few seconds, then
resumes.... So it is impossible to suspend!
Once upon a time, I could find some information the pm-suspend.log file.
Today, I cannot find this file! Is there no more log file for pm-suspend
or did I miss how to activate this file?
I use xfce4
Thank you for helping.
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
I'm the author of this bug report:
I'm new to filing bugs/filing bugs in fedora, this is my first bug report.
Please let me know if I need to add any more log files/etc
The gist of the bug is that I cannot lock the screen with the keyboard