Update to F32 remotely
by Neal Becker
I've been holding off on updating my server at a remote site from F31 ->
F32 because I hate to risk something going wrong at this time of covid,
when I have no access to the remote. At some point I guess I will have to
take the risk. I believe the update can be done entirely remotely.
Thoughts?
--
*Those who don't understand recursion are doomed to repeat it*
3 years, 9 months
resume from suspend to RAM not working properly with / on btrfs
by Lukas Middendorf
Hi,
TL,DR: I have problems with resuming from suspend to RAM on my new Ryzen
computer. I have only seen this happen if I put root onto a btrfs
subvolume, not on ext4. The proprietary nvidia driver seems to be one
additional factor, but I have also seen this with the nvidia driver
removed. Experienced something similar?
I have upgraded my PC with a Ryzen 7 3700X, Asus ROG STRIX x570-E Gaming
and a Samsung 970 EVO PLUS NVMe SSD.
The existing Fedora 32 system from my old SATA SSD worked flawlessly
(with suspend to RAM).
For the last years I have always used ext4 (previously ext3) on
monolithic root partitions (no separate /boot or /home, but separate
data partitions) on mbr partitioned SATA disks, booting in legacy BIOS mode.
With the new drive I wanted to make the switch to GPT, UEFI boot and
btrfs (ext4 /boot). I didn't want to install a new system (with those
months of finding programs you have not yet installed) but opted to just
copy over my old F32 system.
So I used gparted to set up the GPT and a 200MiB EFI System partition,
three 500MiB boot partitions (for different distributions or Fedora
versions), a 16GiB swap partition and the rest of the drive as btrfs. In
the btrfs volume I created a fedora32 subvolume with a nested home
subvolume. I then mounted everything (/, /boot, /boot/efi) on my old f30
system and copied over everything from my f32 partition. After bind
mounting /sys, /proc and /dev I chrooted into the new copy, adjusted the
fstab, installed all efi related packages, ran grub2-mkconfig and made
sure the kernel paths in /boot/loader/entries were correct. I then
switched to the system rescue mode of a f32 netinstall USB drive booted
in UEFI mode (to get access to the efivars) to install grub with target
x86_64-efi and regenerate the initrds.
After that everything booted up and seemed to work until I tried suspend
to RAM. It went to sleep properly, but resuming did not complete. After
waking up it just continued to display the last four kernel messages of
the suspend action (suspending processes, ..., suspending terminal). It
reacted to emergency sync sysrq (HDD LED blinking) but the other sysrq
keys did not seem to work ("u" also provoked a blinking LED sometimes).
This happened from within KDE as well as from text terminal with
systemctl suspend. Log files after reboot just had entries until shortly
before suspend (processes suspended, all except the last CPU core
disabled, unneeded drives stopped) but not from the attempt to resume.
I assumed this to be caused by the NVMe-SSD and unsuccessfully tried
some suggested solutions that have worked for others with suspend
problems with NVMe-SSDs (disabling acpiphp, disabling d3cold_allowed).
Since I had too many variables I trashed the content of the new SSD and
started anew with a mbr partition table to boot in legacy BIOS mode. I
just plain cloned the original f32 partition to the NVMe SSD, adjusted
the fstab, updated grub.cfg, recreated the initrds installed grub to the
mbr and everything worked, including suspend.
I then again did another copy with btrfs root (and ext4 /boot), this
time on MBR with BIOS boot and it again showed the previous suspend
problem. No swap space this time.
I also did a new install of F32 (from Everything Netinstall with Plasma
Workspace profile) with btrfs root and ext4 /boot, which suspended
correctly at the beginning but failed to resume after I installed the
proprietary nvidia driver for my graphics card. Removing the nvidia
driver (and updating grub.cfg and the initrds) returned that install to
a working state.
I then removed the nvidia driver also on the second non-working copy of
my old system (checked that "lsmod | grep nvidia" does not show
anything), but suspend still did not work. It did not show the kernel
messages but just a black screen with frozen mouse pointer. So the
nvidia driver seems to be one way to trigger it but there apparently are
other ways to reach the non-working state.
I have now trashed everything again and settled for GPT, UEFI and root
on ext4 (no separate /boot) with /home on a btrfs subvolume as a
compromise. This seems to be working fine. As I now have a btrfs /home
my problem is also likely not caused by having files open on a btrfs
partition.
The problems were with kernels 5.7.9-200.fc32 and 5.7.10-201.fc32 . I
should likely also have tried an older kernel, but have not yet done so
(might try to get a new non-working test setup tomorrow).
Nvidia driver packages were version 440.100 from rpmfusion on the new
install and a rebuild of the f33 packages of 450.57 for the existing
install.
My hardware:
- AMD Ryzen 7 3700X
- Asus ROG STRIX x570-E Gaming (latest BIOS version 2407)
- Samsung 970 EVO PLUS NVMe SSD
- Geforce GTX960
Tested setups:
Old Ext4 on MBR, SATA: working
copy of old Ext4 on MBR, NVMe: working
copy to BTRFS (Ext4 /boot, with nvidia) on GPT, UEFI, NVMe: not working
copy to BTRFS (Ext4 /boot, with nvidia) on MBR, BIOS, NVMe: not working
copy BTRFS (Ext4 /boot; nvidia removed) on MBR, BIOS, NVMe: not working
new on BTRFS (Ext4 /boot, w/o nvidia) on MBR, BIOS, NVMe: working
new on BTRFS (Ext4 /boot, with nvidia) on MBR, BIOS, NVMe: not working
copy on Ext4 (btrfs /home, with nvidia) on MBR, BIOS, NVMe: working
copy on Ext4 (btrfs /home, with nvidia) on GPT, UEFI, NVMe: working
So this seems to be unrelated to the partition table type and the boot
mode. If it is related to NVMe this is just one factor. I have just
observed it with / on BTRFS. On a new install the proprietary nvidia
driver is also needed to trigger this, but on my old install it also
occurred with the nvidia driver removed.
Things I have not tried yet (might try when I find the time again):
- older kernel version
- ext4 root but with separate boot partition (unlikely cause)
- non-nvidia graphics card (don't have one)
- logging kernel messages on different device using some serial output
(there is a way, right?) to see what really is failing
Has anybody else experienced something similar? Is there something I
might have missed in the btrfs conversion process?
This might become interesting with F33 with lots of new btrfs systems.
Best regards,
Lukas
3 years, 9 months
laptop freezes when screen is blank (when closing the lid)
by Jan-Erik Wichmann
Hi,
I have some problem with my laptop freezing when the screen is blank.
Basically every time I lock the screen (or close the lid) my laptop freezes and cannot be woken up anymore.
The screen will stay black regardless of which buttons I press.
The only way to recover is to press and hold the power button to shut off the computer.
Obviously, that's not very convenient.
Even more so as I cannot even bring my laptop to someone else's desk to quickly show them something; I first need to reboot at their place.
My coworkers are already making fun of linux and how it is not suitable for laptop use and maybe I should consider switching to Microsoft Windows instead.
They say: "Well, it is open source, so why don't you just go ahead and fix the problem yourself?"
I wish I could, but I do not even know where the issue is.
journalctl seems to be unhelpful (see below of the output right before the hard reboot).
So, any ideas of how to debug and hopefully solve this problem?
Thanks a lot!
Aug 27 10:36:57 localhost systemd[6304]: Started GNOME Media keys handling.
Aug 27 10:36:57 localhost systemd[6304]: Reached target GNOME Media keys handling.
Aug 27 10:36:57 localhost systemd[6304]: Reached target GNOME Session.
Aug 27 10:36:57 localhost systemd[6304]: Reached target GNOME Wayland Session (session: gnome).
Aug 27 10:36:57 localhost systemd[6304]: Reached target Current graphical user session.
Aug 27 10:36:57 localhost systemd[6304]: Condition check resulted in GNOME Initial Setup being skipped.
Aug 27 10:36:57 localhost systemd[6304]: Condition check resulted in GNOME Welcome Tour being skipped.
Aug 27 10:36:57 localhost libcanberra-login-sound.desktop[7612]: Failed to play sound: File or data not found
Aug 27 10:36:57 localhost systemd[6304]: gnome-launched-libcanberra-login-sound.desktop-7612.scope: Succeeded.
Aug 27 10:36:57 localhost gsd-media-keys[7523]: Failed to grab accelerator for keybinding settings:rfkill
Aug 27 10:36:57 localhost gsd-media-keys[7523]: Failed to grab accelerator for keybinding settings:playback-repeat
Aug 27 10:36:57 localhost gsd-media-keys[7523]: Failed to grab accelerator for keybinding settings:playback-random
Aug 27 10:36:57 localhost gsd-media-keys[7523]: Failed to grab accelerator for keybinding settings:hibernate
Aug 27 10:36:57 localhost nextcloud[7608]: QSocketNotifier: Can only be used with threads started with QThread
Aug 27 10:36:57 localhost gnome-software[7594]: enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, fedora-pkgdb-collections, desktop-menu-path, fedora-langpacks, flatpak, hardcoded-blacklist, hardcoded-popular, modalias, packagekit-refine, rewrite-resource, odrs, packagekit-history, provenance, repos, systemd-updates, generic-u>
Aug 27 10:36:57 localhost gnome-software[7594]: disabled plugins: dummy
Aug 27 10:36:57 localhost systemd[6304]: GNOME session X11 services is not active.
Aug 27 10:36:57 localhost systemd[6304]: Dependency failed for GNOME XSettings.
Aug 27 10:36:57 localhost systemd[6304]: gsd-xsettings.target: Job gsd-xsettings.target/start failed with result 'dependency'.
Aug 27 10:36:57 localhost systemd[6304]: Starting GNOME XSettings...
Aug 27 10:36:57 localhost ibus-daemon[7357]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
Aug 27 10:36:57 localhost systemd[6304]: dbus-:1.2-org.freedesktop.portal.IBus@0.service: Succeeded.
Aug 27 10:36:57 localhost systemd[6304]: Started dbus-:1.2-org.freedesktop.portal.IBus@1.service.
Aug 27 10:36:57 localhost gnome-shell[7885]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Aug 27 10:36:57 localhost gnome-shell[7885]: > Warning: Unsupported maximum keycode 569, clipping.
Aug 27 10:36:57 localhost gnome-shell[7885]: > X11 cannot support keycodes above 255.
Aug 27 10:36:57 localhost gnome-shell[7885]: > Internal error: Could not resolve keysym Invalid
Aug 27 10:36:57 localhost gnome-shell[7885]: > Error: Key <LFSH> added to map for multiple modifiers
Aug 27 10:36:57 localhost gnome-shell[7885]: > Using Lock, ignoring Shift.
Aug 27 10:36:57 localhost gnome-shell[7885]: Errors from xkbcomp are not fatal to the X server
Aug 27 10:36:58 localhost systemd[6304]: Started GNOME XSettings.
Aug 27 10:36:58 localhost gnome-shell[7235]: GNOME Shell started at Thu Aug 27 2020 10:36:56 GMT+0900 (Japan Standard Time)
Aug 27 10:36:58 localhost gnome-shell[7235]: Registering session with GDM
Aug 27 10:36:58 localhost gsd-color[7506]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Eizo_Nanao_Corporation_EV2785_25537038_gdm_42
Aug 27 10:36:58 localhost gsd-color[7506]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_BOE_gdm_42
Aug 27 10:36:58 localhost gnome-software[7594]: not handling error failed for action get-updates-historical: failed to build result for e234811a0b3925f31157d034477df3bc368a3254
3 years, 9 months
OT: Command-line tool on Fedora 32 to remove a small portion of mp4
by Ranjan Maitra
Hi,
I am writing to ask if there is a way to remove a small portion of a mp4 file. Basically, the file is my lecture (has both audio and video
recorded using simplescreenrecorder) and I want to remove a portion of the mp4 (from the 14:30 to the 15:50 time-points) of an mp4. The mp4
itself is currently 17:50 minutes long.
Is there a way to do this, using a command line tool (preferred) or something else? I like command line tools because they are faster.
Thanks,
Ranjan
3 years, 9 months
VideoConference Package?
by John Mellor
In this extended period of Covid-19 isolation, is there a
videoconference package available?
Hosted systems like Zoom are not opensource, do not use a browser as a
client, feed connection data to Facebook, only allow 2 participants for
free, and not available for a local install.
I thought of Webex, but its Cisco. Maybe its just me :-)
I took a quick look at Jitsi, but users say it has a fatal extreme
processor utilization bug, the rpm packages are 3 years out-of-date, and
does not seem to be present in the normal rpm repos.
I also took a quick look at BigBlueButtion, which looks pretty good.
However, it only runs on an ancient version of Ubuntu, and uses a shell
installer for some unknown reason.
This seems like a major application type that appears to be completely
missing from the repos. Is anyone building one, and just hasn't
announced it yet?
3 years, 9 months
Chromium OS / Fedora / cros-termina ??
by David
This is a follow-up, about my post a few days ago that I had purchased
a real computer running Chrome OS. It is actually running Chromium OS.
My goal is to someday get Fedora running in a virtual window on my ACER
24 Chromebase computer.
The Linux Beta feature that is so easily activated is apparently something
called "cros-termina."
cros-termina - Version: 13099.48.0 is my current version, which I think has
an
available update.
I do not yet have any idea how to add Fedora either to replace Debian or to
in some
sort of other option.
I think most users would not want to run several distros, as the virtual
machine is
so slow and so small.
To add to my confusion, I have almost zero experience with virtual
computing - maybe
none, unless you count briefly looking at a new iso of a distro in Gnome
Boxes.
For anyone interested Chromium OS has 14 visible components. You can
view the names
of those components on your Chromium device, by typing,
"chrome://components."
Some of mine are: ME Preload, Legacy TLS Deprecation Configuration, Adobe
Flash Player,
Intervention Policy Database [ email me if you want the
others ]
I got into this accidentally, and have not followed previous internet news
stories about this
topic, nor yet seen any videos on YouTube.
But I am super duper impressed so far. I hope my future emails to you
will be coming
from the Linux-virtual-machine on this device and hopefully eventually with
Fedora.
David Locklear
3 years, 9 months
Calibre and Python
by Patrick O'Callaghan
Since F32 now has Python 3 as the default, I find that some Calibre
plug-ins no longer work, though Calibre itself is fine. For the moment,
I'm running it in an F31 VM to get round this, but there must be a
better way. I expect it involves environment variables but am too lazy
to experiment, so if anyone has done this I'd appreciate a hint.
poc
3 years, 9 months
launch applications always in the same position/same monitor
by Frederic Muller
Hi!
I'm looking for the above mainly for Thunderbird (which a web search
didn't give me much) but would be happy to do with other apps, under
GNOME 3.
Any idea if this is even possible?
Thank you.
Fred
ps: I mentioned same monitor as actually when switching 1 monitor
orientation from landscape to portrait then half of my apps change
monitor.... should I file a bug or is it to little a problem to even bother?
3 years, 9 months
ssh reverse tunnel as a service?
by Alex Regan
Hi, I have a fedora32 system behind a firewall without any access from
the outside. I'd like to build a reverse ssh tunnel so I can get to it
from my remote location while working remotely. I'm familiar with how
remote ssh tunnels work, but can't quite get systemctl to create a
proper service, presumably because ssh expects to be tied to a terminal.
I've built the following shell script. I believe "bash -s" can be used
to spawn processes not connected to a terminal.
# cat /etc/init.d/ssh-tunnel.sh
#!/bin/bash -s
ssh -i /root/.ssh/orion-key -R 43022:localhost:22 root(a)orion.example.com
I was using this script in a unit file, but got closer to what I want by
placing the ssh command itself into the unit file as the ExecStart
parameter.
# cat /etc/systemd/system/connection.service
[Unit]
Description=Reverse SSH to orion
After=network.target
[Service]
Type=forking
#EnvironmentFile=-/etc/sysconfig/sshd-permitrootlogin
#EnvironmentFile=-/etc/sysconfig/sshd
#ExecStart=/etc/init.d/ssh-tunnel.sh
ExecStart=ssh -tt -i /root/.ssh/orion-key -R 43022:localhost:22
root(a)orion.example.com
#ExecReload=/bin/kill -HUP $MAINPID
User=root
KillMode=process
Restart=on-failure
#RestartSec=42s
[Install]
WantedBy=multi-user.target
I also read that -tt can be passed to ssh to start it on a pseudo-terminal.
I then added the unit file as a service using "systemctl enable
connection.service"
Can someone guide me on the unit parameters I should be using for this?
Should Type=forking?
3 years, 9 months
