Hi All, I know I should be asking these ?s and commenting on the Ubuntu support pages as well as others. So don't reply unless you really want to. I think the newish snap pkgs have been installed through upgrades and are the culprits for my issue. Just an FYI. I was attempting to use 'send to' function in Shotwell (default photo app in Ubuntu) and no file was being attached to the email message that popped up. I did a small amount of research and found that snap and flatpak pkgs were causing difficulties. I forced installed an earlier, and then default, version of Shotwell and it works now as it should and always has. So my updates and upgrades pulled the snap pkgs in and installed them. Here's this: '$ chromium --version Chromium 124.0.6367.118 snap' I uninstalled that version and force installed  '80.0.3987' version, which is confirmed in synaptic but the 'chrome --version' command remains unchanged and the 'about' in chromium shows the above snap version. I'd like to remove snap versions of pkgs and reinstall apt versions. I think my udpdating and upgrading pulled in all of those snap pkgs making many apt pkgs obsolete. Maybe the source of the vast auto-remove list? From what I read snap causes all sorts of problems and may be the source of some of mine. I know the group are not Ubuntu fans as such but I'd like to find a solution, if possible. I'll keep giving it some time here and there as I have written, this is mainly an inconvenience so far.   On 5/31/24 02:14PM, Brian O'Keefe wrote:

Here's that output:

$ sudo inxi -F System:   Host: brian-VivoBook-ASUS-Laptop-X505ZA-F505ZA   Kernel: 5.4.0-182-generic x86_64 bits: 64 Desktop: MATE 1.24.0   Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine:   Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop X505ZA_F505ZA   v: 1.0 serial: K1N0CX08M43402A   Mobo: ASUSTeK model: X505ZA v: 1.0 serial: QCCXKE1JD90305628   UEFI: American Megatrends v: X505ZA.307 date: 08/30/2018 Battery:   ID-1: BAT0 charge: 24.0 Wh condition: 24.3/43.0 Wh (57%) CPU:   Topology: Quad Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx   bits: 64 type: MT MCP L2 cache: 2048 KiB   Speed: 1439 MHz min/max: 1600/2000 MHz Core speeds (MHz): 1: 1495 2: 1374   3: 1460 4: 1406 5: 1369 6: 1369 7: 1369 8: 1376 Graphics:   Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]   driver: amdgpu v: kernel   Display: server: X.Org 1.20.13 driver: amdgpu resolution: 1280x720~60Hz   OpenGL: renderer: AMD Radeon Vega 8 Graphics (RAVEN DRM 3.35.0   5.4.0-182-generic LLVM 12.0.0)   v: 4.6 Mesa 21.2.6 Audio:   Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel   Device-2: AMD Family 17h HD Audio driver: snd_hda_intel   Sound Server: ALSA v: k5.4.0-182-generic Network:   Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi   IF: wlp1s0 state: up mac: 50:76:af:a1:c7:05   Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet   driver: r8169   IF: enp2s0 state: down mac: 40:b0:76:3c:9b:f3 Drives:   Local Storage: total: 715.41 GiB used: 201.05 GiB (28.1%)   ID-1: /dev/sda vendor: Crucial model: CT512MX100SSD1 size: 476.94 GiB   ID-2: /dev/sdb vendor: Micron model: 1100 MTFDDAV256TBN size: 238.47 GiB Partition:   ID-1: / size: 233.18 GiB used: 201.04 GiB (86.2%) fs: ext4 dev: /dev/sdb2 Sensors:   System Temperatures: cpu: 56.0 C mobo: N/A gpu: amdgpu temp: 56 C   Fan Speeds (RPM): cpu: 2400 Info:   Processes: 412 Uptime: 2d 21h 54m Memory: 6.78 GiB used: 3.75 GiB (55.3%)   Shell: bash inxi: 3.0.38

On 5/31/24 01:17PM, Tom Ashcraft wrote:

...

I know I said I'd leave you alone, Brian, but I've just got this itch in the back of my brain that keeps saying I've seen these things before and I know how to deal with them if I can just retrieve and dust off the memories.

On 5/31/24 12:21, Brian O'Keefe wrote:

...

Thanks again Tom and sorry that I'm responding before I read the whole thread. But FYI the 'inxi' command returned 'command not found'.

I noticed that.  'command not found' Indicates only that the package has not been installed.   Again, not that I think it would necessarily be helpful right now, but I'm pretty sure 'inxi' is in one of the Ubuntu software repos if you care to take a look at it: 'apt list inxi'.  If the listing for it shows, then do 'sudo apt install inxi'.  But you probably already know that, right?

...

Yes, I've checked the BIOS and changed the boot order. The cloned SSD shows up and I change the order so it is first but it still doesn't boot.

Just a wild guess, but I would imagine that *both* the original drive that the computer sees first *and* the new cloned SSD system would have to the boot order correctly defined in order for the new SSD system to boot?  Something to do with or similar to "chain booting" used on machines with multiple operating systems?

...

On 5/31/24 09:12AM, Tom Ashcraft wrote:

...

OK Brian, this morning it's clear to me ...

--

--