*urgent help*calls and gnome-conatcs gone after update

[goku499]

I'm usually doing updates from ssh so I can clearly see what happens. I noticed 2 packets were held back (gnome-maps and common-folks). When I wanted to force install them, apt told me it would uninstall A LOT of important packets so I skipped it.
Not sure how or why you had it bypassed by using the GUI. I mean, it should be safer from GUI...

[bcnaz]

I'm usually doing updates from ssh so I can clearly see what happens. I noticed 2 packets were held back (gnome-maps and common-folks). When I wanted to force install them, apt told me it would uninstall A LOT of important packets so I skipped it.
Not sure how or why you had it bypassed by using the GUI. I mean, it should be safer from GUI...

 
In this instance, it would not 'just update' ... but showing "missing dependencies". 

I found the missing chats, calls, contacts Apps  in 'the Software Store' and simply installed them from there.

I did not see any mention of 'Maps' in the missing dependencies...

This description is for my 'updating' my daily driver phone.

My experience was slightly different with installing the fresh image on one of my test phones, but similar.

[goku499]

I'm usually doing updates from ssh so I can clearly see what happens. I noticed 2 packets were held back (gnome-maps and common-folks). When I wanted to force install them, apt told me it would uninstall A LOT of important packets so I skipped it.
Not sure how or why you had it bypassed by using the GUI. I mean, it should be safer from GUI...

 
In this instance, it would not 'just update' ... but showing "missing dependencies". 

I found the missing chats, calls, contacts Apps  in 'the Software Store' and simply installed them from there.

I did not see any mention of 'Maps' in the missing dependencies...

This description is for my 'updating' my daily driver phone.

My experience was slightly different with installing the fresh image on one of my test phones, but similar.

The main issue here is that it shouldn't break the system from doing updates from the GUI.

[user641]

I'm usually doing updates from ssh so I can clearly see what happens. I noticed 2 packets were held back (gnome-maps and common-folks). When I wanted to force install them, apt told me it would uninstall A LOT of important packets so I skipped it.
Not sure how or why you had it bypassed by using the GUI. I mean, it should be safer from GUI...

 
In this instance, it would not 'just update' ... but showing "missing dependencies". 

I found the missing chats, calls, contacts Apps  in 'the Software Store' and simply installed them from there.

I did not see any mention of 'Maps' in the missing dependencies...

This description is for my 'updating' my daily driver phone.

My experience was slightly different with installing the fresh image on one of my test phones, but similar.

The main issue here is that it shouldn't break the system from doing updates from the GUI.

Yes exactly, I was frustrated about that, but overall I am very thankfull for the great work of developers and contributors so far, it's amazing how good it is already!

[bcnaz]

Actually I am Very Impressed,

Mobian is quite Intuitive,

I was able to use just GUI methods to make the repairs myself in just a few moments...

[calinb]

IF you have a 'working' phone with mobian installed,  TURN OFF updates until this is resolved !!!

---

a wise proposal

Since switching Mobian stable to Bookworm unstable, I've been keeping known good image backups on my 128 GB SD card. (I boot Mobian Bookworm from eMMC). I have Megi's multiboot installed on the SD card so it's easy to boot to Mobian (or other OS) on the multiboot and use dd to archive an image on the SD card. I think I'm going to restore a backup image and take a holiday from updates too. Bookworm worked great when I first switched to the new unstable branch but it is becoming rather buggy.

[user641]

IF you have a 'working' phone with mobian installed,  TURN OFF updates until this is resolved !!!

---

a wise proposal

Since switching Mobian stable to Bookworm unstable, I've been keeping known good image backups on my 128 GB SD card. (I boot Mobian Bookworm from eMMC). I have Megi's multiboot installed on the SD card so it's easy to boot to Mobian (or other OS) on the multiboot and use dd to archive an image on the SD card. I think I'm going to restore a backup image and take a holiday from updates too. Bookworm worked great when I first switched to the new unstable branch but it is becoming rather buggy.

Someone correct me if I am wrong, but I think you can perform updates normally, but only do apt update & apt upgrade and never apt full-upgrade (gnome software does that) that's why so many people got this problem. Updating from the terminal avoiding apt full-upgrade, will not cause those problems

[calinb]

IF you have a 'working' phone with mobian installed,  TURN OFF updates until this is resolved !!!

---

a wise proposal

Since switching Mobian stable to Bookworm unstable, I've been keeping known good image backups on my 128 GB SD card. (I boot Mobian Bookworm from eMMC). I have Megi's multiboot installed on the SD card so it's easy to boot to Mobian (or other OS) on the multiboot and use dd to archive an image on the SD card. I think I'm going to restore a backup image and take a holiday from updates too. Bookworm worked great when I first switched to the new unstable branch but it is becoming rather buggy.

Someone correct me if I am wrong, but I think you can perform updates normally, but only do apt update & apt upgrade and never apt full-upgrade (gnome software does that) that's why so many people got this problem. Updating from the terminal avoiding apt full-upgrade, will not cause those problems

Yes. I appears that some of the problems reported here are due to lost packages. Excerpts from the Debian wiki (https://wiki.debian.org/DebianPackageMan...our_system )

You should upgrade you system everyday, this gives you security and bug fixes:

# apt upgrade

Sometimes it is helpful to use "full-upgrade". It performs the function of the upgrade but will remove currently installed packages if that is essential to upgrade the system as a whole. This command is usually issued while doing system upgrades.

# apt full-upgrade

Before upgrading your Debian system to the next release, drop into a "tty" console by pressing CTRL+ALT+F3/F4/F5 etc, as dpkg restarts some login managers that will forcefully log you out while upgrading, resulting in a broken/partial upgrade
...<snip>

Distribution Upgrade of all the files:

WARNING
Following the upgrade instructions found in the release notes is the best way to ensure that your system upgrades from one major Debian release to another (e.g. from jessie to stretch) without breakage!

These instructions will tell you to do a dist-upgrade (instead of upgrade) at least once. You would have to type something like

# apt-get dist-upgrade

at some point during the major release upgrade.

A dist-upgrade will also be required to keep up-to-date with the latest version in testing and unstable. A dist-upgrade may be very occasionally needed for you to obtain security upgrades in stable releases too in the case where packages change names. 

So "upgrade", "full-upgrade", "dist-upgrade"? Having never read Mobian release notes that provide guidance as advised in the Debian wiki, I'm not sure which method I should be using for stable, unstable, testing, etc. at various times.

[user641]

IF you have a 'working' phone with mobian installed,  TURN OFF updates until this is resolved !!!

---

a wise proposal

Since switching Mobian stable to Bookworm unstable, I've been keeping known good image backups on my 128 GB SD card. (I boot Mobian Bookworm from eMMC). I have Megi's multiboot installed on the SD card so it's easy to boot to Mobian (or other OS) on the multiboot and use dd to archive an image on the SD card. I think I'm going to restore a backup image and take a holiday from updates too. Bookworm worked great when I first switched to the new unstable branch but it is becoming rather buggy.

Someone correct me if I am wrong, but I think you can perform updates normally, but only do apt update & apt upgrade and never apt full-upgrade (gnome software does that) that's why so many people got this problem. Updating from the terminal avoiding apt full-upgrade, will not cause those problems

Yes. I appears that some of the problems reported here are due to lost packages. Excerpts from the Debian wiki (https://wiki.debian.org/DebianPackageMan...our_system )

You should upgrade you system everyday, this gives you security and bug fixes:

# apt upgrade

Sometimes it is helpful to use "full-upgrade". It performs the function of the upgrade but will remove currently installed packages if that is essential to upgrade the system as a whole. This command is usually issued while doing system upgrades.

# apt full-upgrade

Before upgrading your Debian system to the next release, drop into a "tty" console by pressing CTRL+ALT+F3/F4/F5 etc, as dpkg restarts some login managers that will forcefully log you out while upgrading, resulting in a broken/partial upgrade
...<snip>

Distribution Upgrade of all the files:

WARNING
Following the upgrade instructions found in the release notes is the best way to ensure that your system upgrades from one major Debian release to another (e.g. from jessie to stretch) without breakage!

These instructions will tell you to do a dist-upgrade (instead of upgrade) at least once. You would have to type something like

# apt-get dist-upgrade

at some point during the major release upgrade.

A dist-upgrade will also be required to keep up-to-date with the latest version in testing and unstable. A dist-upgrade may be very occasionally needed for you to obtain security upgrades in stable releases too in the case where packages change names. 

So "upgrade", "full-upgrade", "dist-upgrade"? Having never read Mobian release notes that provide guidance as advised in the Debian wiki, I'm not sure which method I should be using for stable, unstable, testing, etc. at various times.

As far as I know on testing and unstable better avoid full-upgrade that is the same as dist-upgrade...On bookworm that is testing only apt update and apt upgrade

[bcnaz]

There does not seem to be a huge difference that I can see between the bookworm updated, and a complete fresh nightly release.

The changes may become more obvious with time, but at the moment bookworm itself is still brand new.

I don't think there is anything at this time that is labeled : "Bookworm Stable"