Nautilus search not working in F37
by Marco Sgobino
Hello everyone,
I'm experiencing a bug with nautilus file manager in Fedora Workstation
37. In particular, the moment I type something in the search it
suddenly hangs and never responds anymore. In order to use it again, I
have to kill nautilus from the shell. It doesn't seem to be related on
where I perform the search, nor on what I search.
Launching nautilus from shell and running a search yields message
** Message: 08:15:39.744: Connecting to
org.freedesktop.Tracker3.Miner.Files
and then hangs forever. This prevents me to run any search on nautilus.
The bug is not always reproducible, as sometimes when I boot my machine
the search works as expected.
If this is a bug and not a mistake in configuration, can anyone help me
file a bug report?
Do you need more informations regarding my system?
Which commands would you like me to run?
1 year, 6 months
startx fails
by Geoffrey Leach
suspend failed to do its thing, so I powered-down. <rebooting failed,
dropping me into the <root login. As far as I could tell from the log,
startup correctly, but no X. Running startx as root gave me a display.
However, running startx as a normal user, fails.
So, I have the startx log, but its unclear what its telling me. Is there a
"guide to interpretation of startx messages'"?
Or suggestions as to what might have failed?
Thanks.
1 year, 6 months
FIXED: Fedora 36 pypolicyd-spf-2.9.3-1 Breaks Postfix SPF
by Tom Rivers
Good morning,
TL;DR
If your Fedora 36 Postfix SPF configuration is broken due to the
latest pypolicyd-spf update, install python3-authres and restart
postfix to get it working again.
I noticed when I updated my system this past weekend that SPF was no
longer working after receiving a bounce message from another email
address I use:
Nov 13 14:20:47 impact-crater postfix/smtpd[203195]: connect from
m474.em.secureserver.net[198.71.246.105]
Nov 13 14:20:48 impact-crater postfix/smtpd[203195]: Anonymous TLS
connection established from
m474.em.secureserver.net[198.71.246.105]: TLSv1.3 with cipher
TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519
server-signature RSA-PSS (2048 bits) server-digest SHA256
Nov 13 14:20:48 impact-crater postfix/smtpd[203195]: warning:
premature end-of-input on private/policyd-spf while reading input
attribute name
Nov 13 14:20:49 impact-crater postfix/smtpd[203195]: warning:
premature end-of-input on private/policyd-spf while reading input
attribute name
Nov 13 14:20:49 impact-crater postfix/smtpd[203195]: warning:
problem talking to server private/policyd-spf: Connection reset by peer
Nov 13 14:20:49 impact-crater postfix/smtpd[203195]: NOQUEUE:
reject: RCPT from m474.em.secureserver.net[198.71.246.105]: 451
4.3.5 <tom(a)impact-crater.com>: Recipient address rejected: Server
configuration problem;
from=<sp_31346.182956.1.27afaa92b3a8a24889fe74c219575e84(a)bounces.em.secureserver.net>
to=<tom(a)impact-crater.com> proto=ESMTP helo=<m474.em.secureserver.net>
Nov 13 14:20:49 impact-crater postfix/smtpd[203195]: using
backwards-compatible default setting
smtpd_relay_before_recipient_restrictions=no to reject recipient
"tom(a)impact-crater.com" from client
"m474.em.secureserver.net[198.71.246.105]"
Nov 13 14:20:49 impact-crater postfix/smtpd[203195]: disconnect from
m474.em.secureserver.net[198.71.246.105] ehlo=2 starttls=1 mail=1
rcpt=0/1 quit=1 commands=5/6
Running policyd-spf manually gave me the following output:
[root@impact-crater ~]# /usr/libexec/postfix/policyd-spf
Traceback (most recent call last):
File "/usr/libexec/postfix/policyd-spf", line 33, in <module>
sys.exit(load_entry_point('spf-engine==2.9.3',
'console_scripts', 'policyd-spf')())
File "/usr/libexec/postfix/policyd-spf", line 25, in
importlib_load_entry_point
return next(matches).load()
File "/usr/lib64/python3.10/importlib/metadata/__init__.py", line
171, in load
module = import_module(match.group('module'))
File "/usr/lib64/python3.10/importlib/__init__.py", line 126, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 992, in
_find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 241, in
_call_with_frames_removed
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in
_find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in
exec_module
File "<frozen importlib._bootstrap>", line 241, in
_call_with_frames_removed
File "/usr/lib/python3.10/site-packages/spf_engine/__init__.py",
line 54, in <module>
import authres
ModuleNotFoundError: No module named 'authres'
I discovered that installing python3-authres-1.2.0-12.fc36.noarch and
restarting postfix seems to have fixed things:
dnf install python3-authres
postfix reload
I hope this helps anyone else who ran into this.
Tom
1 year, 6 months
Fedora 36 on a MS Surface GO (2 or 3)?
by Sbob
Hi All;
Anyone have any good guides for installing Fedora on a Surface Go 2 or a
Surface Go 3?
Is there a reason I should pick the 2 vs the 3?
Thanks in advance
1 year, 6 months
kvm and spice
by Ranbir
Hello Everyone,
I discovered to day that Red Hat has deprecated SPICE in RHEL 9. I've
been trying to get SPICE working on Fedora 36 host and I'm striking
out: the GSSAPI authentication for it never works, but it works just
fine for VNC.
Is the SPICE protocol still supported in F36? I have the SPICE related
RPMs installed and virt-manager still lets me choose SPICE as the
display. However, considering I can't get the damn console to work
without prompting me for a password, I'm starting to think something
fundamental has been removed.
I don't want to use VNC. It's slower, I can't use USB redirection and I
don't get any sound. RDP is an option, but it's also inferior to SPICE.
I'm sensing IBM's hands at play here...
--
Ranbir
1 year, 6 months
i915 Unstable
by Ken Smith
Hi everyone,
I have a Dell Latitude 5480 laptop with a Fedora 36 install. It crashes
regularly, uptime can sometimes be less that 5 mins but sometimes it
lasts several hours. There is no trace at all in journalctl of its
demise. It behaves like a machine with a memory issue. I've moved the
memory from one slot to another and cleaned the connector.
I've been using Redhat style systems for over 20 years and have known
uptimes of several years. This laptop also boots Win10 and that install
is stable. The machine passes Dells internal diagnostics. I'm travelling
this week and don't have access to memtest86, but the Win10 memory test
passes. Once I'm back home I can network boot it and run memtest86 and
FC36 live - which will eliminate the ssd & its controller from the picture.
.
This machine has a KabbyLake processor (Intel Core i5-7200U 2.50GHz), 8G
memory, an Intel i915 (HD Graphics 620) GPU and SSD storage. I've read
on various forums that this combination of CPU/GPU can be problematic
and some mentions that an upcoming Kernel release may contain a remedy
for this.
In addition to the FC36 standard kernel, I have tried a 6.0 kernel build
and even the development 6.1 kernel from Rawhide's daily builds ( Beta
for FC38 ) and its related firmware RPM. Also tried loading the 5.11
kernel from FC34. All with the same results. In fact the FC38 beta
kernel only survives a few minutes even without the GUI.
Is this hardware faulty, despite Win10 being stable? Does the Linux
install stress the hardware in a way Win10 doesent. Should I hold on
for a later kernel release with a fix.
Is anyone else experiencing this issue? I'd value any insights.
Many thanks
Ken
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
1 year, 6 months
Moving to a new GPU
by Patrick O'Callaghan
I've replaced my ageing Nvidia card with a more recent and much faster
AMD GPU. However when I boot the system, the default display still
shows as the built-in Intel chip, even though AMD modules are loaded:
$ sudo lsmod|grep -i amd
amdgpu 10153984 1
iommu_v2 24576 1 amdgpu
gpu_sched 49152 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
drm_buddy 20480 2 amdgpu,i915
drm_display_helper 180224 2 amdgpu,i915
ttm 94208 3 amdgpu,drm_ttm_helper,i915
(Nvidia modules are not loaded).
Inxi shows:
$ inxi -G
Graphics:
Device-1: Intel IvyBridge GT2 [HD Graphics 4000] driver: i915 v: kernel
Device-2: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3 driver: X:
loaded: amdgpu,modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa
22.1.7
Switcherooctl shows both GPUs:
$ switcherooctl list
Device: 0
Name: Intel® HD Graphics 4000
Default: yes
Environment: DRI_PRIME=pci-0000_00_02_0
Device: 1
Name: Advanced Micro Devices, Inc. [AMD®/ATI] Ellesmere
[Radeon RX 470/480/570/570X/580/580X/590] (Radeon RX 580)
Default: no
Environment: DRI_PRIME=pci-0000_01_00_0
I should mention that both GPUs are connected through an HDMI switch to
a single monitor. I've used this successfully in the past to get PCI
passthrough on Windows VMs for gaming.
I haven't touched anything else. I tried unplugging the i915 and
rebooting (after removing the HDMI switch and connecting the monitor
directly), but simply got a blank screen (in fact three dots at the top
left).
Is there some grub magic I need to do? I assumed this would be
automatic but it seems not.
poc
1 year, 6 months
Font Error Before a Display of the Grub Boot Menu
by Stephen Morris
Hi,
When I boot my machine I am getting a font error before the Grub
Menu is being displayed but is disappearing before I can get a good look
at it, which may be because of the Grub Boot Theme I am using, which has
not installed its files into /boot/grub2/themes but has stored them in
/usr/share/grub, irrespective of the error the grub menus display fine
with the theme. The error message seems to be referencing
efi/EFI/fedora/unicode.pf2 as a target but I can't be sure, but the
theme being used doesn't use that file anyway.
Is there anywhere I can look to find the message to understand what
is being objected to?
regards,
Steve
1 year, 6 months
