Fedora 34 boot screen
by Paul Smith
Dear All,
Since a few weeks ago, when I boot my Fedora 34 machine, I get a three
animated square dots as a boot screen like the following:
https://i.stack.imgur.com/7hFp0.png
Moreover, the booting duration seems to be longer than before.
Any reason for that?
Thanks in advance,
Paul
2 years, 9 months
how to configure smartd to send a mail with ssmtp?
by François Patte
Bonjour,
I dessperatly try to have smartd sending me an email with ssmtp but it
seems to be impossible!
There are a lot of environment variables (SMARTD_MAILER,
SMARTD_ADDRESS...) but nowhere I found where they could be defined!
I tried in file smartd.conf, in smartd_warning.sh, in
/usr/libexec/smartmontools/smartdnotify... But it does not work.
Does somebody know how to proceed?
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire MAP5 --- UMR CNRS 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 4286 2145
http://www.math-info.univ-paris5.fr/~patte
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
2 years, 9 months
Confused
by jarmo
Just checked KERNEL related, what installed into
my desktop, I found:
[root@oh1mrr oh1mrr]# rpm -qa | grep kernel
kernel-srpm-macros-1.0-4.fc34.noarch
libreport-plugin-kerneloops-2.15.2-2.fc34.x86_64
abrt-addon-kerneloops-2.14.6-3.fc34.x86_64
kernel-core-5.12.15-300.fc34.x86_64
kernel-modules-5.12.15-300.fc34.x86_64
kernel-5.12.15-300.fc34.x86_64
kernel-modules-extra-5.12.15-300.fc34.x86_64
kernel-core-5.12.17-300.fc34.x86_64
kernel-modules-5.12.17-300.fc34.x86_64
kernel-5.12.17-300.fc34.x86_64
kernel-modules-extra-5.12.17-300.fc34.x86_64
kernel-core-5.13.4-200.fc34.x86_64
kernel-modules-5.13.4-200.fc34.x86_64
kernel-5.13.4-200.fc34.x86_64
kernel-modules-extra-5.13.4-200.fc34.x86_64
kernel-headers-5.13.3-200.fc34.x86_64
Now what makes me wonder, why this:
kernel-headers-5.13.3-200.fc34.x86_64
is different than all other KERNEL versions?
Or is this "no worries mate" ?
Jarmo
2 years, 9 months
Message after update of wine 6.13??
by Michael D. Setzer II
Just did dnf update and it installed wine 6.13.
Afterwards I generally run
wine notepad
from command line to have it do the test of update.
This time, it did the update fine, and comes up with the
blank screen and I closed the notepad.
After a short time, the following comes up on terminal
window.
wine: Unhandled page fault on write access to
0000000000000000 at address 00007F56D62BE3A1
(thread 0074), starting debugger...
0074:err:seh:start_debugger Couldn't start debugger
L"winedbg --auto 100 72" (1115)
Read the Wine Developers Guide on how to set up
winedbg or another debugger
Not sure why it can't start debugger.
I can run
wine winedbg --auto 100 72
afterwards, but it shows info, but doesn't apply to the
previous notepad run.
If I run notepad from the menu, you would never see this
message at all, so not sure if it is just something to
ignore.
Thanks.
2 years, 9 months
resizing qemu image
by Robert Moskowitz
Things have been 'quiet' here, working away, but I need a bit of help....
I have a 10G Fedora image that is now too small. I need to grow it.
I have shutdown the image in VMM, and quite VMM.
I backed up the image, /var/lib/libvirt/images/fedora21.qcow2 to a USB
drive.
Then I ran:
qemu-img resize fedora21.qcow2 +10G
and
qemu-img info fedora21.qcow2
image: fedora21.qcow2
file format: qcow2
virtual size: 20 GiB (21474836480 bytes)
disk size: 10 GiB
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
refcount bits: 16
corrupt: false
That seems to be the easy part. But now the instructions I am finding
seem to offer different approachs, and might not be for running on
Fedora. What is the 'best' approach forward?
thanks
2 years, 9 months
usb port enumeration changed?
by Eyal Lebedinsky
I know that device numbers change, but bus/port numbers are stable and reflect the physical layout
of the hubs and devices. I relied for years on these port numbers to identify specific (otherwise
identical) devices.
For example, I have two TEMPer temperature sensor devices attached. They are both plugged into
a 4-port USB3 hub. They are on ports 3 and 4. Port 2 is unused and port 1 has a bluetooth radio
attached. I also have 5 dvb usb tuners which stayed in their old positions.
Until now, I would see this:
$ lsusb
Bus 001 Device 013: ID 0c45:7401 Microdia TEMPer Temperature Sensor
Bus 001 Device 025: ID 0c45:7401 Microdia TEMPer Temperature Sensor
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
|__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 5: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 2: Dev 26, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 27, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 27, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 10, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 10, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 1: Dev 6, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 12, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 15, If 0, Class=Printer, Driver=usblp, 12M
|__ Port 1: Dev 14, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 14, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 4: Dev 16, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 4: Dev 16, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 8, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 2: Dev 8, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 5: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 20, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 1: Dev 20, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 25, If 0, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 3: Dev 25, If 1, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 4: Dev 13, If 0, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 4: Dev 13, If 1, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 6: Dev 19, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M
The TEMPer devices show on Bus 01 as expected:
Port 5.Port 3 (Dev 11)
Port 5.Port 4 (Dev 13)
After rebooting the newly installed kernel 5.13.4-200.fc34.x86_64 I get:
$ lsusb
Bus 001 Device 012: ID 0c45:7401 Microdia TEMPer Temperature Sensor
Bus 001 Device 003: ID 0c45:7401 Microdia TEMPer Temperature Sensor
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M
|__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 5: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
|__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 11, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 3: Dev 11, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 1: Dev 7, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 4: Dev 13, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 15, If 0, Class=Printer, Driver=usblp, 12M
|__ Port 1: Dev 14, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 1: Dev 14, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 4: Dev 16, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 4: Dev 16, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 9, If 0, Class=Vendor Specific Class, Driver=dvb_usb_rtl28xxu, 480M
|__ Port 2: Dev 9, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 5: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 10, If 0, Class=Wireless, Driver=btusb, 12M
|__ Port 1: Dev 10, If 1, Class=Wireless, Driver=btusb, 12M
|__ Port 3: Dev 12, If 0, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 3: Dev 12, If 1, Class=Human Interface Device, Driver=, 1.5M <<<<<
|__ Port 6: Dev 18, If 0, Class=Human Interface Device, Driver=usbfs, 1.5M
One can see that the TEMPer devices are now showing on Bus 01 in separate positions:
Port 3 (Dev 3) new position
Port 5.Port 3 (Dev 12) old position
This, naturally, confuses my script that collects the data (I use temper-poll).
Is this an intentional change?
--
Eyal Lebedinsky (fedora(a)eyal.emu.id.au)
2 years, 9 months
Restart systemd service based on memory usage
by Richard Shaw
I have a Kiosk I'm trying out using Chromium, unfortunately it seems to
have a memory leak and crashes in less than 24 hours of usage.
I see systemD has an option for "MemoryMax" but was wondering if anyone has
actually used it?
Is it as simple as
MemoryMax=512M
OnFailure=Restart
or something like that?
Thanks,
Richard
2 years, 9 months
Audio output device changes unbidden under f34
by Jonathan Ryshpan
When I queue up a number of podcasts to play in rhythmbox, the output
device often changes when the second podcast starts, from a device
connected via a USB port to the built in audio. This happens when I
use either the PulseAudio Volume Control application or the KDE Plasma
Audio Volume applet. I don't remember it happening under Fedora-33.
System
* KDE Frameworks 5.83.0
* Fedora-34 with all updates installed
--
Thanks for your help Jonathan Ryshpan <jonrysh(a)pacbell.net> Dance, as
if nobody's watching, Love, as if you've never been hurt, Sing, as if
no one can hear you, Work, as if you don't need the money, Live, as if
heaven is on earth. -- Rumi
2 years, 9 months
The meaningless kernel bug ever
by Sam Varshavchik
I feel silly even writing this.
I just installed the 5.13.4-200 kernel update on my venerable Thinkpad W520.
This old battle tank'd keyboard has a button that mutes the built-in
microphone. It has a tiny orange LED that's lit when the mike is muted. I
don't remember ever having to use it in the last decade, but it's there and
that's what it does.
Booting the 5.13 kernel: the orange LED gets turned on during the boot, and
it stays lit. The mute button itself is fully functional. Audio mixer
dutifully reports the ambient noise level gets muted on/off.
There's also the built-in speaker mute button that works the same way, and
its behavior is unchanged under 5.13, its orange LED is on only when it
mutes the audio out.
Rebooting 5.12: both mute buttons' LED indicators work as advertised.
Can anyone think of an even more meaningless kernel bug?
2 years, 9 months
