Whenever I mistype a URL,
it gets turned into food for Midcontinent's search engine.
What is really annoying is that the back
button does not take me back to what I typed.
Also, the search results rarely includes the site I wanted.
My suspicion is that this is done at least partly through DNS corruption.
Anyone know for sure?
I'm running F33 connected directly to Midco's modem/router.
Assuming DNS corruption is at least part of the issue,
how, if at all, do I bypass Midco's DNS?
The problem seems not unique to Midco or F33:
My girlfriend has the same problem with CenturyLink and Ubuntu.
They send her to yahoo.
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
I have a shiny new Fedora 33 install on my new LG Gram 17
I'm having an issue where every 10 min or so my bluetooth music player
disconnects, then reconnects and starts playing again.
Any advice on how to debug / fix?
Thanks in advance
The last 2 or 3 kernel updates seem to have triggered a regression in
the i915 (internal Intel GPU) driver. I get damaged screen updates,
very noticeable tearing on videos and occasional freezes in the DE
(Plasma under X11). A look at the journal shows:
Feb 19 16:33:16 Bree kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:cbd2d2d2, in chrome 
Feb 19 16:33:16 Bree kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Feb 19 16:33:16 Bree kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it.
Feb 19 16:33:16 Bree kernel: GPU crash dump saved to /sys/class/drm/card0/error
Feb 19 16:33:16 Bree kernel: i915 0000:00:02.0: [drm] chrome context reset due to GPU hang
Feb 19 16:33:22 Bree kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85ffbff8, in chrome 
Feb 19 16:33:22 Bree kernel: i915 0000:00:02.0: [drm] chrome context reset due to GPU hang
Feb 19 16:33:59 Bree kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:7f7f7f7f, in chrome 
Feb 19 16:33:59 Bree kernel: i915 0000:00:02.0: [drm] chrome context reset due to GPU hang
Feb 19 23:43:39 Bree kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85fffffc, in Xorg 
Feb 19 23:43:39 Bree kernel: i915 0000:00:02.0: [drm] Xorg context reset due to GPU hang
Feb 20 11:23:50 Bree kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85fffff8, in plasmashell 
Feb 20 11:23:50 Bree kernel: i915 0000:00:02.0: [drm] plasmashell context reset due to GPU hang
Feb 20 11:23:53 Bree kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 7:1:85fffdfc, in plasmashell 
Feb 20 11:23:53 Bree kernel: i915 0000:00:02.0: [drm] plasmashell context reset due to GPU hang
Unfortunately I'd rebooted before looking at the journal, so
/sys/class/drm/card0/error is currently empty. I'll capture it next
time around, but it the meantime has anyone else seen this?
I've been seeing strange things on my panel for about a week or two.
They are triangles or lines extending horizontally from a region of
some color, narrowing to a point. They last generally for up to about
30 seconds. Attached is a picture of such an artifact
(PanelArtifact.jpg), taken with my cell phone. Note the black stripe
just above "System Information". Has anyone seen anything like this
System: Fedora-32 all updates installed
Processor: 4 x Intel i5 4460 CPU at 3.2 GHz
Memory: 15.5 GiB RAM
Video System: Xorg (not Wayland)
Graphics: Mesa DRI Intel HD Graphics 4600
KDE Plasma: 5.20.5
KDE Framework: 5.78.0
Several days ago, Skype pushed an update for Linux that I cannot
install. I cannot install it because it requires a new version of the
GNU Atomic Library called libatomic1. Not "libatomic," which is what
Fedora uses, but "libatomic1" (note the placement of that digit "1") for
which Fedora seems to have no builds.
I have found builds for several RPM-based distros, including Alt-Linux
Sisyphus, OpenMandriva, and OpenSUSE.
Question: may anyone safely install any of these packages into a Fedora
Three days ago I did a dnf system upgrade to apply all available
Fedora updates. I have now tried to start Plasma under Xorg, but it now
refuses to start with a crash in ksplashqml, and if I press
ctrl-alt-delete to try to logout the ksmserver-greeter also crashes.
Plasma under Wayland runs quite happily albeit without resolution
scaling. Gnome under Wayland runs fine without scaling and Gnome under
Xorg also runs fine. How do I determine why the apps are failing with
Plasma under Xorg now?
Anyone know what this is `dnf upgrade` error is
Problem: cannot install both rdma-core-33.0-1.fc33.x86_64 and
- rdma-core-32.0-1.fc33.i686 has inferior architecture
- cannot install the best update candidate for package
- problem with installed package rdma-core-32.0-1.fc33.i686
Has anyone installed Fedora on an LG Gram? I bought one a few years back
and ended up returning it due to issues... Maybe these laptops are
better supported now?
Thanks in advance for any advice...
From: "S Bob" <sbob(a)quadratum-braccas.com<mailto:email@example.com>>
Date: Tuesday, 16 February 2021 at 01:10:08
To: "Community support for Fedora users" <users(a)lists.fedoraproject.org<mailto:firstname.lastname@example.org>>
Subject: cannot ssh between 2 Fedora 33 laptops
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces
"Destination Host Unreachable"
Is there something else in Fedora 33 I need to do?
Thanks in advance
What does tcpdump -n -i <device-name> show?
And: arp -a ?
Or: ip neigh show ?
( can you see each other?)
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
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
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.