KneadToKnow's questions

I upgraded one of my PCs from 22.04.5 to 24.04.1, and it seemed to go smoothly. Using another desktop, still on 22.04.5, though, I cannot connect to it through Remmina client as I normally do (LAN connection, desktop sharing, connecting to the active session, which is my needed condition). I get a black screen with "Connecting to name" a spinning "wheel" in the top left corner of the client window. I have not yet waited it out to see if it ever changes to an error, but it doesn't seem to.

What I've done so far:

• Connected a monitor so I could see what's going on, and I noticed that the new connection defaults call for port 3389, so I changed that in my client (added :3389 to the IP address) and made sure the port was open in UFW on the server and on the client.
• Confirmed that my password doesn't seem to have changed.
• I confirmed that I'm using X11 by running echo $XDG_SESSION_TYPE.
• I even tried changing the protocol on the client side to RDP, which resulted in a different result, "Cannot connect to the ip-address RDP server."

(edited to add a step I forgot).

I've followed the instructions here, but when I click Calibrate... nothing happens. Any thoughts on what I am doing wrong?

Ubuntu 21.10 Canon LiDE 400 scanner

I don't see this exact question in the prompted similar questions, so if it has been asked in a different form before, please forgive me.

I currently have 20.04 on my HDD and plan to upgrade to 22.04 (installed to an NVMe SSD) when it is released. I would like to dual-boot for a little while so I can test and make sure the new setup works as I want it to, then I will switch over fully to the 22.04 on SSD and drop the dual-boot. Can anyone suggest the best way to handle this?

Thanks!

EDITED TO ADD: From some of the comments, I realize that I did not make clear enough that my question is not about the testing phase as much as it is about the migrating from HDD to SSD boot drives with a dual-boot phase in between.

I'm still looking to see if there is a clear answer to the question of where GRUB should live during the dual-boot phase: should I put GRUB on the SSD when I install 22.04 or wait to move it there when I remove the HDD?

After struggling for some time, I've finally got my Canon LiDE 400 scanner working on Ubuntu 21.10, but now I have sort of the opposite problem. When I start up XSane, it makes me choose between 2 scanners when I only have 1.

scanimage -L gives the same "2" scanners and is easier to copy and paste, so I'll show that output:

device `escl:http://localhost:60000' is a Canon LiDE 400 (USB) platen scanner
device `airscan:e0:Canon LiDE 400 (USB)' is a eSCL Canon LiDE 400 (USB) ip=127.0.0.1

I've tested both and they both seem to work fine, I would just like to not have to choose when I only, in fact, have 1 scanner.

Please let me know what additional information I can provide, and if there is any reason to prefer one of these options over the other.

On Ubuntu 20.04.3 LTS, I recently switched from nouveau to the nvidia-driver-470 for my GeForce GT710 video card to improve stability. That has been successful, as I'm seeing much less random freezing (I was inspired by the stability improvements I found when I switched to nvidia-driver-470 on my Ubuntu 21.10 box). However, I'm seeing a lot of screen tearing (I hope I'm using the proper term) on my remote session via Remmina VNC.

To be clear, what I see in the remote window does not happen in the monitor connected to the PC. I found this thread and tried the 20-intel.conf solution suggested there (something I saw elsewhere had me under the impression that the video used for remote desktop doesn't go through the video card, but will use the built-in graphics, please feel free to confirm or correct me on this).

EDIT: I have also tried the NVIDIA X Server Settings solution from the linked page as well, to no avail.

Also, to make sure what I'm describing is truly screen tearing, what I see is partially-redrawn portions of the screen flashing through the top-most windows. For instance, if I have Files open, and am moving files around in it, I may see desktop icons briefly visible, or if I have several windows open, closing one of them may briefly show desktop icons or just elements of the bottom-most window before it settles down. This lasts usually a second or less, but it's very annoying.

If it weren't for the random freezes I was having, I would go back to nouveau, but at least the system is stable now.

I'm happy to provide any additional information needed to help troubleshoot this.

Ubuntu 21.10 desktop, AMD Ryzen 5 3600 (3.6 GHz), 64 GB RAM

I'm having this problem both with Wayland and without.

Common to all crash situations is Firefox (default Snap install). Sometimes just Firefox will crash, but sometimes takes my entire system down with it. Sometimes I get the Firefox crash report screen, sometimes I wind up at the Ubuntu login screen, sometimes the system just freezes to the point that only a hard reset works.

I've found the "about:crashes" page in Firefox and just discovered that the last 2 weeks or so of crash reports weren't submitted, so I've now submitted all of those.

When I look at /var/log/syslog, I see far too much that I don't understand, but will happily post if someone can tell me what to look for.

Thanks in advance.

Edits below as requested. No overclocking on CPU or RAM.

ls -al /var/crash

total 12
drwxrwsrwt  2 root     whoopsie 4096 Dec 16 07:38 .
drwxr-xr-x 16 root     root     4096 Dec 15 20:32 ..
-rw-r--r--  1 robert   whoopsie    0 Dec 14 06:46 _usr_lib_xorg_Xorg.1000.upload
-rw-------  1 whoopsie whoopsie   37 Dec 14 06:46 _usr_lib_xorg_Xorg.1000.uploaded

sudo lshw -C memory

  *-firmware
       description: BIOS
       vendor: American Megatrends Inc.
       physical id: 0
       version: P1.70
       date: 12/01/2020
       size: 64KiB
       capacity: 16MiB
       capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi
  *-memory
       description: System Memory
       physical id: f
       slot: System board or motherboard
       size: 64GiB
     *-bank:0
          description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
          product: F4-3200C16-16GVK
          vendor: Unknown
          physical id: 0
          serial: 00000000
          slot: DIMM 0
          size: 16GiB
          width: 64 bits
          clock: 2133MHz (0.5ns)
     *-bank:1
          description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
          product: F4-3200C16-16GVK
          vendor: Unknown
          physical id: 1
          serial: 00000000
          slot: DIMM 1
          size: 16GiB
          width: 64 bits
          clock: 2133MHz (0.5ns)
     *-bank:2
          description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
          product: F4-3200C16-16GVK
          vendor: Unknown
          physical id: 2
          serial: 00000000
          slot: DIMM 0
          size: 16GiB
          width: 64 bits
          clock: 2133MHz (0.5ns)
     *-bank:3
          description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns)
          product: F4-3200C16-16GVK
          vendor: Unknown
          physical id: 3
          serial: 00000000
          slot: DIMM 1
          size: 16GiB
          width: 64 bits
          clock: 2133MHz (0.5ns)
  *-cache:0
       description: L1 cache
       physical id: 12
       slot: L1 - Cache
       size: 384KiB
       capacity: 384KiB
       clock: 1GHz (1.0ns)
       capabilities: pipeline-burst internal write-back unified
       configuration: level=1
  *-cache:1
       description: L2 cache
       physical id: 13
       slot: L2 - Cache
       size: 3MiB
       capacity: 3MiB
       clock: 1GHz (1.0ns)
       capabilities: pipeline-burst internal write-back unified
       configuration: level=2
  *-cache:2
       description: L3 cache
       physical id: 14
       slot: L3 - Cache
       size: 32MiB
       capacity: 32MiB
       clock: 1GHz (1.0ns)
       capabilities: pipeline-burst internal write-back unified
       configuration: level=3

sysctl vm.swappiness

vm.swappiness = 60

free -h

               total        used        free      shared  buff/cache   available
Mem:            62Gi       5.6Gi       1.2Gi       179Mi        55Gi        56Gi
Swap:           71Gi        17Mi        71Gi

swapon -s

Filename                Type        Size    Used    Priority
/dev/sdb1            partition  75497468    17536   -2

UPDATED 2021-12-19

ls -al /var/crash

total 3204
drwxrwsrwt  2 root     whoopsie    4096 Dec 19 12:41 .
drwxr-xr-x 16 root     root        4096 Dec 19 12:38 ..
-rw-r--r--  1 robert   whoopsie       0 Dec 19 12:41 _opt_google_chrome_chrome.1000.upload
-rw-------  1 whoopsie whoopsie      37 Dec 19 12:41 _opt_google_chrome_chrome.1000.uploaded
-rw-r--r--  1 robert   whoopsie       0 Dec 19 12:41 _usr_bin_gnome-shell.1000.upload
-rw-------  1 whoopsie whoopsie      37 Dec 19 12:41 _usr_bin_gnome-shell.1000.uploaded
-rw-r-----  1 robert   whoopsie 3254690 Dec 19 12:41 _usr_bin_Xwayland.1000.crash
-rw-r--r--  1 robert   whoopsie       0 Dec 19 12:41 _usr_bin_Xwayland.1000.upload
-rw-------  1 whoopsie whoopsie      37 Dec 19 12:41 _usr_bin_Xwayland.1000.uploaded
-rw-r--r--  1 robert   whoopsie       0 Dec 14 06:46 _usr_lib_xorg_Xorg.1000.upload
-rw-------  1 whoopsie whoopsie      37 Dec 14 06:46 _usr_lib_xorg_Xorg.1000.uploaded

ls -al ~/.local/share/gnome-shell/extensions

total 16
drwxrwxr-x 4 robert robert 4096 Dec 13 11:52 .
drwx------ 4 robert robert 4096 Dec 19 16:19 ..
drwxrwxr-x 4 robert robert 4096 Dec 14 06:47 [email protected]
drwxrwxr-x 5 robert robert 4096 Dec  3 08:19 [email protected]

ls -al /usr/share/gnome-shell/extensions

total 20
drwxr-xr-x 5 root root 4096 May 14  2021 .
drwxr-xr-x 7 root root 4096 Oct 16 19:13 ..
drwxr-xr-x 2 root root 4096 Oct 16 18:49 [email protected]
drwxr-xr-x 3 root root 4096 Oct 16 18:49 [email protected]
drwxr-xr-x 3 root root 4096 Oct 16 18:50 [email protected]

Over the course of a day of working on my PC (Ubuntu 21.10 x86_64, Gnome 40.5, Wayland), without (I believe) my doing anything to cause it, the function of Alt+Tab (switching between open windows) stops working but suddenly Super+Tab does what Alt+Tab is supposed to do. I got this thread as a prompted similar question, but I only see there that Alt+Tab stops working, not that Super+Tab starts doing it's job, so I'm not sure if it's the same problem.

I'm happy to provide any additional information for troubleshooting.

EDIT: It didn't occur to me to check this until just now, but I've confirmed that my Alt key performs other combinations normally (like moving through tabs in Google Sheets), so it doesn't appear to be anything hardware-related.

Last Saturday night, I upgraded from Ubuntu 20.04 to 21.10. In reviewing my logs, I've noticed that immediately upon my upgrade, and lasting since, my PC's CPU temp baseline has jumped 15-20°. See charts from Friday, Saturday, and Sunday below, for comparison. I'd love to know if anyone has any thoughts on what might be going on.

Device specs: AMD Ryzen 5 3600, 64 GB RAM. I'm happy to provide any other info that might be helpful. I pull CPU temp with a script that runs every 5 minutes and reads the Tctl value from sensors.

UPDATE WITH MORE INFORMATION:

I've confirmed that pwrstatd was what was causing the high temps, and I feel like a complete dope for not checking sooner. Every day since I upgraded to 21.10, pwrstatd has been, as of my morning logs, either 93.8% or 100% CPU usage. I killed it yesterday afternoon, and here's what my temp graph looked like from this morning:

After I killed the daemon, I tried running "pwrstatd --help" just to get some more info on it, but that generated a segmentation fault. After I rebooted, the daemon no longer seems to be running. If anyone knows what my next steps should be, I'm open to suggestions.

I've used Clock Override for some time and am very happy with the formatting options it lets me choose. After I upgraded to Ubuntu 21.10, I found that that format needed re-applying, and that's when I quickly found that Clock Override has not been updated for newer versions of Gnome (nor does it seem will any time soon).

Can anyone recommend an alternative or a way to do what Clock Override does another way?

I'm developing a Bash script which cleans up old data files periodically, and right now everything works except for the log file I'm trying to generate so I can see what it did.

The structure I'm using is (sorry for the variables):

find $datfold -maxdepth 1 -type f -name "$month-*-data.dat" -printf "%f\n" | xargs tar -czvf $month-data.tar.gz >> $log

The tar.gz part is working fine, it's just not sending any output to the $log file. What am I missing?

I've confirmed that I got the point release update to 20.04.3 LTS with lsb_release -a, but uname -r shows that my kernel is still on 5.4.0-81-generic. Should I not be on 5.11? My machine running Ubuntu 21.04 is on 5.11.0-31-generic.

I found an old thread here which proposes using apt to install linux-generic, but I wanted to make sure it was still good advice.

Over the last year or so, I've be trying to learn bash scripting on Ubuntu (one 20.04 LTS box and one 21.04). I feel that my skills have been progressing nicely, but I'm at my wits end with one particular backup script I've written.

Long story short, if the backup script is only trying to backup my /home directory, it runs smoothly beginning to end, but if it is trying to backup my / directory, it runs until the rsync process is complete (including creating a log file), and then the script simply seems to stop, event though I've got some housekeeping code that follows to alert me. I even added an exit trap, but that isn't triggered.

I don't know what I'm missing, but I'm eager to try to learn, if anyone can help me out.

I don't know if it will help, but here's a slightly simplified version of my script:

#!/bin/bash
#
# backup
# unified back up, home and/or root folders to raid on Betty
# runs daily from sudo crontab (time varies by device); day of month determines which backup is performed
#
# related files
# generates backup.log in home folder of main user, archives existing backup.log to logs folder as yyyy-mm-dd-backup.log
# requires two files in $homefold: home-backup.exclude and boot-backup.exclude, to provide backup exclusions for rsync
#
# exit trap
function badquit {
   if [[ "$1" = "test" ]] ; then
      exit 0
   elif [[ "$goodflag" = "0" ]] ; then
      echo "$(date +%r) : $shname exited with goodflag=0" > $logfold/$shname.quit
   fi
}
trap badquit EXIT
#
# variables
host="$(hostname)"
hostlc="${host,,}"
shname="$(basename $0)"
hostuser="$(getent passwd "1000" | cut -d: -f1)"
homefold="/home/$hostuser"
logfold="$homefold/logs"
log="$homefold/$shname.log"
date="$(date +%Y-%m-%d)"
dom="$(date +%d)" # day of month at runtime determines which backup is performed (daily home, weekly home, quarterly boot)
soonwarn="7" # days in advance to create .soon report
case $host in # $bumount location varies by device: Betty mounts it differently than all others
   Betty)
      bumount="/mnt/raid"
      ;;
   *)
      bumount="/media/betty-raid"
      ;;
esac
bufold="$bumount/$hostlc"
goodflag="0" # default status of goodflag to trigger unexpected exit message
#
# pre-check
# confirm existence of $bufold, attempt to mount if not found, set fail message if unsuccessful
if [[ ! -e $bufold ]] ; then
   mount 192.168.x.x:/mnt/raid $bumount
   sleep 5
   if [[ ! -e $bufold ]] ; then
      echo "$(date +%r) : $shname exited because $bufold could not be mounted" > $logfold/$shname.quit
      goodflag="1"
      exit 1
   fi
fi
# 
# log management
if [[ -e $log ]] ; then
   mv $log $logfold/"$(date -r $log +"%Y-%m-%d")"-$shname.log
fi
#
# primary tasks
# set targdom per old boot backup schedule (to allow time for .soon)
case $host in
   Betty)
      targdom="8"
      ;;
   Veronica)
      targdom="12"
      ;;
   *)
      echo "$(date +%r) : $shname cannot identify $host" > $logfold/$shname.quit
      goodflag="1"
      exit 1
      ;;
esac   
# determine which backup to run, set final variables
if [[ "$dom" = "$targdom" ]] ; then # targdom triggers non-daily backups
   if [[ $(date +%m) -eq "01" ]] || [[ $(date +%m) -eq "04" ]] || [[ $(date +%m) -eq "07" ]] || [[ $(date +%m) -eq "10" ]] ; then # quarterly boot backup Jan,Apr,Jul,Oct
      ropts="-avuHkbi --delete --exclude-from=$homefold/boot-backup.exclude --backup-dir=$bufold/Backup.$date --log-file=$log" 
      rsource="/"
   else # monthly home backup
      ropts="-axvuHkbi --delete --exclude-from=$homefold/home-backup.exclude --backup-dir=$bufold/Backup.$date --log-file=$log"
      rsource="/home"
   fi
else # not targdom, daily home backup
   ropts="-axvuHkbi --exclude-from=$homefold/home-backup.exclude --backup-dir=$bufold/Backup.$date --log-file=$log" #daily home backup
   rsource="/home"
fi
# if this is a test, set variables appropriately
if [[ "$1" = "test" ]] ; then
   ropts="-navuHkbi --exclude-from=$homefold/boot-backup.exclude --backup-dir=$bufold/Backup.$date --log-file=$log" # dry-run ON
   rsource="/"
fi
# run the backup, finally
rsync $ropts --backup-dir=$bufold/Backup.$date --log-file=$log $rsource $bufold
#
# set exitcond
if [[ "$?" = "0" ]] ; then
# successful, log saved
   exitcond="successfully, log saved"
else
# unsuccessful, exit cond
   exitcond="unsuccessfully, exit code $?"
fi
#
echo "$(date +%r) : $shname completed $exitcond" >> $logfold/$shname.done
goodflag="1"