From Newsgroup: alt.os.linux

Over the past 24 hours I've been trying to install Ubuntu 22 on a laptop
and copy my customisations from another installation, but had many
problems. I tried making a USB by 3 different methods, but with each
the installation failed, so I sat up half the night installing 18 and in
place upgrading from 18 to 20 to 22. Then I copied the installation
from a working Ubuntu 22 on a different PC, rather a clumsy sledgehammer approach of copying my customisations but it has usually worked pretty
well in the past. However, on this occasion, I have some boot messages relating to snap failures as below. Searching for the first yields
almost nothing, and absolutely nothing in English:

root@Charles-I:home# systemctl list-units snap*
UNIT LOAD ACTIVE SUB
DESCRIPTION
snap-bare-5.mount loaded active mounted Mount
unit for bare, revision 5
? snap-core-17200.mount loaded failed failed Mount
unit for core, revision 17200
snap-core22-1439.mount loaded active mounted Mount
unit for core22, revision 1439
snap-core22-1564.mount loaded active mounted Mount
unit for core22, revision 1564
? snap-gnome\x2d3\x2d26\x2d1604-111.mount loaded failed failed Mount
unit for gnome-3-26-1604, revision 111
? snap-gnome\x2d3\x2d26\x2d1604-70.mount loaded failed failed Mount
unit for gnome-3-26-1604, revision 70
snap-gnome\x2d42\x2d2204-176.mount loaded active mounted Mount
unit for gnome-42-2204, revision 176
? snap-gnome\x2dcalculator-180.mount loaded failed failed Mount
unit for gnome-calculator, revision 180
? snap-gnome\x2dcharacters-103.mount loaded failed failed Mount
unit for gnome-characters, revision 103
? snap-gnome\x2dlogs-37.mount loaded failed failed Mount
unit for gnome-logs, revision 37
? snap-gnome\x2dsystem\x2dmonitor-51.mount loaded failed failed Mount
unit for gnome-system-monitor, revision 51
snap-gtk\x2dcommon\x2dthemes-1535.mount loaded active mounted Mount
unit for gtk-common-themes, revision 1535
? snap-gtk\x2dcommon\x2dthemes-319.mount loaded failed failed Mount
unit for gtk-common-themes, revision 319
snap-snapd-21465.mount loaded active mounted Mount
unit for snapd, revision 21465
snap-snapd-21759.mount loaded active mounted Mount
unit for snapd, revision 21759
snapd.apparmor.service loaded active exited Load AppArmor profiles managed internally by snapd
snapd.seeded.service loaded active exited Wait
until snapd is fully seeded
snapd.service loaded active running Snap
Daemon
snapd.socket loaded active running Socket activation for snappy daemon
snapd.mounts-pre.target loaded active active
Mounting snaps
snapd.mounts.target loaded active active
Mounted snaps
--

Fake news kills!

I may be contacted via the contact address given on my website: www.macfh.co.uk
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 29/08/2024 15.11, Java Jive wrote:

However, on this occasion, I have some boot messages
relating to snap failures as below.  Searching for the first yields
almost nothing, and absolutely nothing in English:

root@Charles-I:home# systemctl list-units snap*
  UNIT                                     LOAD   ACTIVE SUB DESCRIPTION
...
unit for gnome-calculator, revision 180
? snap-gnome\x2dcharacters-103.mount       loaded failed failed  Mount
unit for gnome-characters, revision 103
? snap-gnome\x2dlogs-37.mount              loaded failed failed  Mount
unit for gnome-logs, revision 37
...

try: journalctl -u "*snap*"
--
//Aho

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 29/08/2024 14:18, J.O. Aho wrote:

On 29/08/2024 15.11, Java Jive wrote:

 However, on this occasion, I have some boot messages relating to snap
failures as below.  Searching for the first yields almost nothing, and
absolutely nothing in English:

root@Charles-I:home# systemctl list-units snap*
   UNIT                                     LOAD   ACTIVE SUB DESCRIPTION
...
unit for gnome-calculator, revision 180
? snap-gnome\x2dcharacters-103.mount       loaded failed failed  Mount
unit for gnome-characters, revision 103
? snap-gnome\x2dlogs-37.mount              loaded failed failed  Mount
unit for gnome-logs, revision 37
...

try: journalctl -u "*snap*"

Thanks for your reply, relevant section from copious results appended.

Since my first post, I've been investigating particularly the first
failure, and what seems to be happening is that a block device is
missing from ...
/var/lib/snapd/snaps
... which I could create using mknod, but I would need to know the
correct major and minor numbers to use.

See third message down "special device
/var/lib/snapd/snaps/core_17200.snap does not exist" and several others similar.

# journalctl -u "*snap*"

Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for bare,
revision 5...
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for core,
revision 17200...
Aug 29 13:10:09 [hostname] mount[332]: mount: /snap/core/17200: special
device /var/lib/snapd/snaps/core_17200.snap does not exist.
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for core22, revision 1439...
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for core22, revision 1564...
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for gnome-3-26-1604, revision 111...
Aug 29 13:10:09 [hostname] mount[335]: mount: /snap/gnome-3-26-1604/111: special device /var/lib/snapd/snaps/gnome-3-26-1604_111.snap does not exist. Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for gnome-3-26-1604, revision 70...
Aug 29 13:10:09 [hostname] mount[336]: mount: /snap/gnome-3-26-1604/70: special device /var/lib/snapd/snaps/gnome-3-26-1604_70.snap does not exist.
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for
gnome-42-2204, revision 176...
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for gnome-calculator, revision 180...
Aug 29 13:10:09 [hostname] mount[338]: mount:
/snap/gnome-calculator/180: special device /var/lib/snapd/snaps/gnome-calculator_180.snap does not exist.
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for gnome-characters, revision 103...
Aug 29 13:10:09 [hostname] mount[339]: mount:
/snap/gnome-characters/103: special device /var/lib/snapd/snaps/gnome-characters_103.snap does not exist.
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for
gnome-logs, revision 37...
Aug 29 13:10:09 [hostname] mount[340]: mount: /snap/gnome-logs/37:
special device /var/lib/snapd/snaps/gnome-logs_37.snap does not exist.
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for gnome-system-monitor, revision 51...
Aug 29 13:10:09 [hostname] mount[341]: mount:
/snap/gnome-system-monitor/51: special device /var/lib/snapd/snaps/gnome-system-monitor_51.snap does not exist.
Aug 29 13:10:09 [hostname] systemd[1]: Mounting Mount unit for gtk-common-themes, revision 1535...
Aug 29 13:10:10 [hostname] systemd[1]: Mounting Mount unit for gtk-common-themes, revision 319...
Aug 29 13:10:10 [hostname] mount[343]: mount:
/snap/gtk-common-themes/319: special device /var/lib/snapd/snaps/gtk-common-themes_319.snap does not exist.
Aug 29 13:10:10 [hostname] systemd[1]: Mounting Mount unit for snapd,
revision 21465...
Aug 29 13:10:10 [hostname] systemd[1]: Mounting Mount unit for snapd,
revision 21759...
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for bare,
revision 5.
Aug 29 13:10:10 [hostname] systemd[1]: snap-core-17200.mount: Mount
process exited, code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]: snap-core-17200.mount: Failed
with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for
core, revision 17200.
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for core22,
revision 1439.
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for core22,
revision 1564.
Aug 29 13:10:10 [hostname] systemd[1]: snap-gnome\x2d3\x2d26\x2d1604-111.mount: Mount process exited,
code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]: snap-gnome\x2d3\x2d26\x2d1604-111.mount: Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gnome-3-26-1604, revision 111.
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gnome\x2d3\x2d26\x2d1604-70.mount: Mount process exited,
code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gnome\x2d3\x2d26\x2d1604-70.mount: Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gnome-3-26-1604, revision 70.
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for
gnome-42-2204, revision 176.
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gnome\x2dcalculator-180.mount: Mount process exited, code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gnome\x2dcalculator-180.mount: Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gnome-calculator, revision 180.
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gnome\x2dcharacters-103.mount: Mount process exited, code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gnome\x2dcharacters-103.mount: Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gnome-characters, revision 103.
Aug 29 13:10:10 [hostname] systemd[1]: snap-gnome\x2dlogs-37.mount:
Mount process exited, code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]: snap-gnome\x2dlogs-37.mount:
Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gnome-logs, revision 37.
Aug 29 13:10:10 [hostname] systemd[1]: snap-gnome\x2dsystem\x2dmonitor-51.mount: Mount process exited,
code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]: snap-gnome\x2dsystem\x2dmonitor-51.mount: Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gnome-system-monitor, revision 51.
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for gtk-common-themes, revision 1535.
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gtk\x2dcommon\x2dthemes-319.mount: Mount process exited,
code=exited, status=32/n/a
Aug 29 13:10:10 [hostname] systemd[1]:
snap-gtk\x2dcommon\x2dthemes-319.mount: Failed with result 'exit-code'.
Aug 29 13:10:10 [hostname] systemd[1]: Failed to mount Mount unit for gtk-common-themes, revision 319.
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for snapd,
revision 21465.
Aug 29 13:10:10 [hostname] systemd[1]: Mounted Mount unit for snapd,
revision 21759.
Aug 29 13:10:10 [hostname] systemd[1]: Reached target Mounted snaps.
--

Fake news kills!

I may be contacted via the contact address given on my website: www.macfh.co.uk

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 29/08/2024 16.47, Java Jive wrote:

On 29/08/2024 14:18, J.O. Aho wrote:

On 29/08/2024 15.11, Java Jive wrote:

 However, on this occasion, I have some boot messages relating to
snap failures as below.  Searching for the first yields almost
nothing, and absolutely nothing in English:

root@Charles-I:home# systemctl list-units snap*
   UNIT                                     LOAD   ACTIVE SUB
DESCRIPTION
...
unit for gnome-calculator, revision 180
? snap-gnome\x2dcharacters-103.mount       loaded failed failed
Mount unit for gnome-characters, revision 103
? snap-gnome\x2dlogs-37.mount              loaded failed failed
Mount unit for gnome-logs, revision 37
...

try: journalctl -u "*snap*"

Thanks for your reply, relevant section from copious results appended.

Since my first post, I've been investigating particularly the first
failure, and what seems to be happening is that a block device is
missing from ...
    /var/lib/snapd/snaps
... which I could create using mknod, but I would need to know the
correct major and minor numbers to use.

I kind of think you are missing the snap image that is tried to be automatically started, I have to say I have limited knowledge about
snaps as the distros I have been using do not support snaps.

Maybe a full clean out of snaps would fix this and that you after that
can reinstall all your snaps images.

Here is one example how to remove snaps and snapd https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.
--
//Aho
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 29/08/2024 17:28, J.O. Aho wrote:

On 29/08/2024 16.47, Java Jive wrote:

Since my first post, I've been investigating particularly the first
failure, and what seems to be happening is that a block device is
missing from ...
     /var/lib/snapd/snaps
... which I could create using mknod, but I would need to know the
correct major and minor numbers to use.

I kind of think you are missing the snap image that is tried to be automatically started, I have to say I have limited knowledge about
snaps as the distros I have been using do not support snaps.

Maybe a full clean out of snaps would fix this and that you after that
can reinstall all your snaps images.

Here is one example how to remove snaps and snapd https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.

Yes, uninstalled snap and deleted all remaining relevant files and
folders, rebooted to ensure messages had gone which they had, then
reinstalled the snap mechanism but no packages as yet.

All good, thanks for your help.
--

Fake news kills!

I may be contacted via the contact address given on my website: www.macfh.co.uk

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On Thu, 8/29/2024 6:38 PM, Java Jive wrote:

On 29/08/2024 17:28, J.O. Aho wrote:

On 29/08/2024 16.47, Java Jive wrote:

Since my first post, I've been investigating particularly the first failure, and what seems to be happening is that a block device is missing from ...
     /var/lib/snapd/snaps
... which I could create using mknod, but I would need to know the correct major and minor numbers to use.

I kind of think you are missing the snap image that is tried to be automatically started, I have to say I have limited knowledge about snaps as the distros I have been using do not support snaps.

Maybe a full clean out of snaps would fix this and that you after that can reinstall all your snaps images.

Here is one example how to remove snaps and snapd
https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.

Yes, uninstalled snap and deleted all remaining relevant files and folders, rebooted to ensure messages had gone which they had, then reinstalled the snap mechanism but no packages as yet.

All good, thanks for your help.

The Gnome Desktop is a Snap package. Removing every snap would not
leave you with much of a desktop GUI to look at. Presumably
that's why Canonical likes that particular kind of handcuffs.

I expect you've just removed the optional content, and there
should not be a fuss about the optional/discretionary content.

This design choice also has consequences when you add a Gnome
utility which is not part of the desktop package. The dependencies
of a .deb Gnome utility, then cause a metric ton of libraries to be
pulled in (which would normally have already been pulled in for
a Gnome Desktop .deb metapackage).

And you wonder why the ISO download is 6GB now.

Paul
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 30/08/2024 03:18, Paul wrote:

On Thu, 8/29/2024 6:38 PM, Java Jive wrote:

On 29/08/2024 17:28, J.O. Aho wrote:

Maybe a full clean out of snaps would fix this and that you after that can reinstall all your snaps images.

Here is one example how to remove snaps and snapd
https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.

Yes, uninstalled snap and deleted all remaining relevant files and folders, rebooted to ensure messages had gone which they had, then reinstalled the snap mechanism but no packages as yet.

The Gnome Desktop is a Snap package. Removing every snap would not
leave you with much of a desktop GUI to look at. Presumably
that's why Canonical likes that particular kind of handcuffs.

I expect you've just removed the optional content, and there
should not be a fuss about the optional/discretionary content.

No, I use XCFE.

This design choice also has consequences when you add a Gnome
utility which is not part of the desktop package. The dependencies
of a .deb Gnome utility, then cause a metric ton of libraries to be
pulled in (which would normally have already been pulled in for
a Gnome Desktop .deb metapackage).

And you wonder why the ISO download is 6GB now.

Yes, Linux bloat seems always to be trying to catch up with Microsoft bloat.
--

Fake news kills!

I may be contacted via the contact address given on my website: www.macfh.co.uk

--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

J.O. Aho wrote:

I kind of think you are missing the snap image that is tried to be automatically started, I have to say I have limited knowledge about
snaps as the distros I have been using do not support snaps.

Maybe a full clean out of snaps would fix this and that you after that
can reinstall all your snaps images.

Here is one example how to remove snaps and snapd https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.

Just install Linux Mint instead, no snaps by default.
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

Java Jive <java@evij.com.invalid> wrote at 09:49 this Friday (GMT):

On 30/08/2024 03:18, Paul wrote:

On Thu, 8/29/2024 6:38 PM, Java Jive wrote:

On 29/08/2024 17:28, J.O. Aho wrote:

Maybe a full clean out of snaps would fix this and that you after that can reinstall all your snaps images.

Here is one example how to remove snaps and snapd
https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.

Yes, uninstalled snap and deleted all remaining relevant files and folders, rebooted to ensure messages had gone which they had, then reinstalled the snap mechanism but no packages as yet.

The Gnome Desktop is a Snap package. Removing every snap would not
leave you with much of a desktop GUI to look at. Presumably
that's why Canonical likes that particular kind of handcuffs.

I expect you've just removed the optional content, and there
should not be a fuss about the optional/discretionary content.

No, I use XCFE.

This design choice also has consequences when you add a Gnome
utility which is not part of the desktop package. The dependencies
of a .deb Gnome utility, then cause a metric ton of libraries to be
pulled in (which would normally have already been pulled in for
a Gnome Desktop .deb metapackage).

And you wonder why the ISO download is 6GB now.

Yes, Linux bloat seems always to be trying to catch up with Microsoft bloat.

At least there are other distros.. I think the internet Debian install
is sub 500mb?
--
user <candycane> is generated from /dev/urandom
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On Mon, 2 Sep 2024 22:50:05 -0000 (UTC)
candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:

Java Jive <java@evij.com.invalid> wrote at 09:49 this Friday (GMT):

On 30/08/2024 03:18, Paul wrote:

On Thu, 8/29/2024 6:38 PM, Java Jive wrote:

On 29/08/2024 17:28, J.O. Aho wrote:

Maybe a full clean out of snaps would fix this and that you after that can reinstall all your snaps images.

Here is one example how to remove snaps and snapd
https://askubuntu.com/questions/1309144/how-do-i-remove-all-snaps-and-snapd-preferably-with-a-single-command

You may just want to go with removing the snaps packages.

Yes, uninstalled snap and deleted all remaining relevant files and folders, rebooted to ensure messages had gone which they had, then reinstalled the snap mechanism but no packages as yet.

The Gnome Desktop is a Snap package. Removing every snap would not
leave you with much of a desktop GUI to look at. Presumably
that's why Canonical likes that particular kind of handcuffs.

I expect you've just removed the optional content, and there
should not be a fuss about the optional/discretionary content.

No, I use XCFE.

This design choice also has consequences when you add a Gnome
utility which is not part of the desktop package. The dependencies
of a .deb Gnome utility, then cause a metric ton of libraries to be
pulled in (which would normally have already been pulled in for
a Gnome Desktop .deb metapackage).

And you wonder why the ISO download is 6GB now.

Yes, Linux bloat seems always to be trying to catch up with Microsoft bloat.

At least there are other distros.. I think the internet Debian install
is sub 500mb?

<Sticking oar in mode>

tinycore has bloated from 16M (with desktop) to 23M (at time of posting)

http://tinycorelinux.net/downloads.html
--
Bah, and indeed Humbug.
--- Synchronet 3.20a-Linux NewsLink 1.114