Lately, I've noticed that different tabs that I have open in Firefox are
crashing. This seems to have started recently. They can be restored
easily, but there's a nuisance factor here.
Hardware/Software basic deets:
Dell XPS 13 L322X laptop, vintage circa 2013.
1TB Samsung Solid state drive
F32 - everything has been updated
Is there a way in the Fedora 32 installer to set the compression mount
option for a new BTRFS filesystem before installing Fedora itself? I
know I can add the option to the fstab file after installation, reboot,
and then run the defragment command to compress after the fact, but it
would be convenient if I could just have the filesystem compressed right
away during installation.
Also, from what I've read I think I already know the answer to this, but
I'll ask to make sure: is it possible to set the compression option
persistently in the filesystem itself? It would be nice if I could have
an external USB hard drive (with its obvious IO bottleneck) compressed
as well. However, it seems like I would then have to always manually
mount the drive with the compression option, or set the compression
attribute after mounting. Either way, this isn't persistent. I also know
I could set the disk's UUID to always be mounted with the compression
option, but that is specific to one machine.
Terveisin / Regards,
I'm looking for suggestions for a VM tool for Fedora 32. I am tired of
having to constantly patch VMware and have it stop working every time I
update to a new kernel. Looking for suggestions. Does KVM run on fedora
32? Can I install a windows VM with KVM? Anyone using other tools?
Thanks in advance
I have some JPEG files on a Western Digital My cloud drive that I would
like to extract. I regret ever getting involved with it but now I need
to get the files off it and the software they provide to do that is for
Windows. Has anyone found a way to do this with Fedora, F-32 preferably?
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
There is currently a large thread in devel discussing the
implementation of systemd-resolved for resolving DNS. As part of that
I read this:
> > This is not the reality I live in though. New-style high level
> > programming languages tend to avoid being just a wrapper around C
> > APIs. And thus they implement minimal DNS clients themselves,
> > ignoring the LLMNR, mDNS and so on.
> Not just for DNS. For SMTP, HTTP, etc.
> The modern way of coding apps is minimal marginally-compliant and
> secure built-in network client (so things sort of work on the dev
> system and in CI/CD unit tests), with the OS interposing a
> full-featured protocol proxy in “production” deployments.
For me, the implication of that is that I am no longer in control of
DNS, etc. If some program has hard coded DNS servers, they bypass
everything and just ignore system settings. Am I understanding
If I'm not, great, I'm happy. If I am, though, how do I take back
control? I have turned off NetworkManager control of DNS and use a
simple caching resolver, knot-resolver. Am I OK, since all DNS access
has to go through that resolver, with my configured DNS servers?
In particular, I'm thinking about firefox, since as part of that thread
it emerged that browsers are including their own DNS clients with
things like DOH and DOT. Before I start knot-resolver, firefox cannot
reach the web. Is that an indication that it does, in fact, use my
A reboot does *not fix* anything.
From: "ToddAndMargo via users" <users(a)lists.fedoraproject.org<mailto:email@example.com>>
Date: Tuesday, 29 September 2020 at 14:24:52
To: "users(a)lists.fedoraproject.org" <users(a)lists.fedoraproject.org<mailto:firstname.lastname@example.org>>
Cc: "ToddAndMargo" <ToddAndMargo(a)zoho.com<mailto:ToddAndMargo@zoho.com>>
Subject: Re: Reload kernel?
On 2020-09-27 04:40, Roger Heflin wrote:
> So the gui gets slow, a reboot clears it, does it clear up?
GUI and the file system. A reboot fixes it
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten.
This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
On Tue, Sep 29, 2020 at 3:07 PM Samuel Sieb <samuel(a)sieb.net> wrote:
> On 9/29/20 10:33 AM, Fulko Hew wrote:
> > No, no other thread. In the original email I used iw command to turn
> > manage off.
> > wlp2s0f0u4 wifi unmanaged --
> > wlp2s0f0u4 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>"
> > Mode:Managed Frequency=2.412 GHz Access Point:
> > So now nmcli says it's unmanaged but iwconfig says it IS managed.
> Ok, that is a little confusing. The nmcli "managed" means that
> NetworkManger is handling the device. The iwconfig "managed" is
> referring to the mode that the wifi device is in.
> > So I also tried both of the following to enable monitor:
> > [root@localhost fhew]# iw wlp2s0f0u4 set monitor none
> > command failed: No such device (-19)
> That can't be the actual command you ran, because it's not valid.
> You're missing a "dev".
I hear what you're saying, and yes, the man page says you should have a
'dev' in there,
but that doesn't make any difference"
[root@localhost fhew]# iw dev wlp2s0f0u4 set monitor none
command failed: No such device (-19)
> > [root@localhost fhew]# iwconfig wlp2s0f0u4 mode monitor
> > Error for wireless request "Set Mode" (8B06) :
> > SET failed on device wlp2s0f0u4 ; Invalid argument.
> > and neither worked. So I'm back to thinking it's a driver issue.
> Yes, that seems very likely to be the reason for both those commands
Where to look next ?
I started this journey with a variety of web pages such as this one:
I'm not wedded to this USB adapter, I'd like to know which one would
in monitor mode, out of the box, with Fedora supplied drivers.
> P.S. Looking at the newer Wireshark, I still didn't see a 'monitor'
> > button. Perhaps it's because the wi-fi driver isn't supporting it?
> When you open the capture options dialog, you might need to scroll to
> the right to see the monitor checkbox.
Nope, I tried sending a screen shot, but the mailing list is holding my
message for moderation.
There is a column in the table entitled Monitor Mode, but it's filled in
F.Y.I. I also sent this to the Wireshark user's list to see if someone
there can help me.
I'm trying to sniff my Wifi for a project, so I purchased a TP-Link WN722N
and followed the various instructions I've found on the Web.
(I don't know if it's a Wireshark issue, a driver issue, or a Fedora issue.)
ip link set wlan0 down
iw wlan0 set monitor none
ip link set wlan0 up
When I plugged the adapter in I saw a new device 'wlp0s20f0u3' in addition
to my internal adapter 'wlps20'.
Using the instructions, it failed:
# iw set wlp0s20f0u3 down
# iw wlp0s20f0u3 set monitor none
command failed: No such device (-19)
--> I don't know why?
So now that I have 2 adapters, I enabled the TPLink as my network
connection (successfully) and tried to put my on-board adapter
into monitor mode, instead:
# iw wlp2s0 set monitor none
wlp2s0 IEEE 802.11 Mode:Monitor Tx-Power=22 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
# iplink set wlp2s0 up
It looks good, so I start Wireshark (v 2.28) (Fedora 26),
and look at Wireshark's 'capture options' table, it shows the interface,
but under the heading 'Mon Mode', it shows disabled.
(I also have 'Use promiscuous mode on all interfaces' enabled.)
--> Why does it show disabled?
--> Is it really disabled ?
--> How do I know which frequencies (or bands) it might be listening on?
I started sniffing, but it doesn't capture anything.
... And after about 2 minutes, I get a pop-up error message from Wireshark
"The network adapter on which the capture was being
done is no longer running; the capture has stopped."
Where to start ?
Is there a way to reload or restart the kernel without
having to reboot?
When we ask for advice, we are usually looking for an accomplice.
-- Charles Varlet de La Grange