Todays update / Touchpad [Solved]

[Metaphysik]

Forgot to ask:

Is it the same when on battery / plugged in ?

Also is it ok if you boot with systemd ?

Result, starting unplugged: In both cases it did now also not work before login ..

How can I boot with systemd?

[Metaphysik]

When I think with an update they could run into the same crap I get sick. I thought updates were supposed to ...

Yes, but they're mostly from Debian (directly) :)

I think than there is only one way for me an the three users that uses MX after I've showed it them: as before, as soon as it is working again, disabling updates and have freedom for a few years ..

[Metaphysik]

Is there a way to downgrade these packages to the versions before?

2023-10-13 04:12:20 upgrade libjavascriptcoregtk-4.1-0:amd64 2.40.5-1~deb12u1 2.42.1-1~deb12u1
2023-10-13 04:12:19 upgrade libwebkit2gtk-4.1-0:amd64 2.40.5-1~deb12u1 2.42.1-1~deb12u1
2023-10-13 04:12:18 upgrade libjavascriptcoregtk-4.0-18:amd64 2.40.5-1~deb12u1 2.42.1-1~deb12u1
2023-10-13 04:12:17 upgrade libwebkit2gtk-4.0-37:amd64 2.40.5-1~deb12u1 2.42.1-1~deb12u1
2023-10-13 04:12:17 upgrade gir1.2-webkit2-4.0:amd64 2.40.5-1~deb12u1 2.42.1-1~deb12u1
2023-10-13 04:12:17 upgrade gir1.2-javascriptcoregtk-4.0:amd64 2.40.5-1~deb12u1 2.42.1-1~deb12u1
2023-10-12 18:37:10 upgrade mx-snapshot:amd64 23.10 23.10.01
2023-10-12 18:37:10 upgrade libcurl3-gnutls:amd64 7.88.1-10+deb12u3 7.88.1-10+deb12u4
2023-10-12 18:36:58 upgrade libcurl4:amd64 7.88.1-10+deb12u3 7.88.1-10+deb12u4
2023-10-12 18:36:58 upgrade firefox:amd64 118.0.1~mozillabinaries-1mx23+1 118.0.2~mozillabinaries-1m
x23+1
2023-10-12 18:36:57 upgrade samba-common:all 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:57 upgrade curl:amd64 7.88.1-10+deb12u3 7.88.1-10+deb12u4
2023-10-12 18:36:53 upgrade python3-samba:amd64 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:52 upgrade samba:amd64 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:47 upgrade samba-libs:amd64 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:46 upgrade samba-common-bin:amd64 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:46 upgrade libwbclient0:amd64 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:46 upgrade libsmbclient:amd64 2:4.17.11+dfsg-0+deb12u1 2:4.17.12+dfsg-0+deb12u1
2023-10-12 18:36:45 upgrade python3-ldb:amd64 2:2.6.2+samba4.17.11+dfsg-0+deb12u1 2:2.6.2+samba4.17.
12+dfsg-0+deb12u1
2023-10-12 18:36:45 upgrade libldb2:amd64 2:2.6.2+samba4.17.11+dfsg-0+deb12u1 2:2.6.2+samba4.17.12+d
fsg-0+deb12u1

[Metaphysik]

Thanks for your help guys!

Fortunately I have a snapshot from 30.09. . So with a little copy work I can go back to the stand. I'll wait until tomorrow, maybe you can think of a better solution.

Otherwise, I play the one and disable the update function at me and my three friends whom I recommended MX.

If you can run on Linux, whether directly through Debian or however in the same crap as Windows updates there is something wrong for me. Anyway, my 19.3 er MX ran after the Bootsectordesaster almost four years without updates / problems, MX 23 should probably also manage ;-)

[j2mcgreg]

@Metaphysik wrote:

Since I started using MX, I have convinced 3 users to use MX. When I think with an update they could run into the same crap I get sick. I thought updates were supposed to improve things and not ruin things that worked before ...

When MX is installed properly, your last statement is generally true.

[Metaphysik]

The touchpad works again!

However, this does not make sense to me in any way.

More out of boredom, I looked in the Bios to see if there was any setting for the touchpad. No, nothing in that direction, but the touchpad works inside Bios. However, I saw the option "Wake up when the lid is opened". I switched that on. When I rebooted, I wiped back and forth over the MX logo in frustration until the login came up. And what happened? The touchpad responded at login, now again even with MX running.

There was no change or installation before apart from the "wake up when lid is opened". Maybe someone can explain this, for me it seems more like voodoo ....

Before future updates I will definitely take a snapshot and with my acquaintances I put out the updates. Would be really bad if with those far away suddenly something of the hardware would also no longer run.

Idea for the programmers of MX - There is still something missing under MX tools: MX Rollback. A system recovery with calendar for MX ;-)

Just now the update icon also reports. There are three updates again. I will now guaranteed not run ... I'm glad that the touchpad works again, without it was really annoying.

Thank you again for your attempt to help!

[jasalt]

Idea for the programmers of MX - There is still something missing under MX tools: MX Rollback. A system recovery with calendar for MX ;-)

@Metaphysik Would the "Timeshift" MX utility work for this? I didn't try it yet but sounds like the nearest match to what you describe.

[Metaphysik]

Idea for the programmers of MX - There is still something missing under MX tools: MX Rollback. A system recovery with calendar for MX ;-)

@Metaphysik Would the "Timeshift" MX utility work for this? I didn't try it yet but sounds like the nearest match to what you describe.

Great! I didn't know that this exists! Thanks!

[Charlie Brown]

In the meantime you can begin / consider using Timeshift (installed ootb, ready in Menu).

Idea for the programmers of MX - There is still something missing under MX tools: MX Rollback. A system recovery with calendar for MX ;-)

@Metaphysik Would the "Timeshift" MX utility work for this? I didn't try it yet but sounds like the nearest match to what you describe.

Great! I didn't know that this exists! Thanks!

[Metaphysik]

In the meantime you can begin / consider using Timeshift (installed ootb, ready in Menu).

@Metaphysik Would the "Timeshift" MX utility work for this? I didn't try it yet but sounds like the nearest match to what you describe.

Great! I didn't know that this exists! Thanks!

Sorry, Charlie Brown. I didn't realize that this might have something to do with System Restore and thought it was something to fiddle with the system to get the touchpad working again, and I didn't want to do command line etc. I'm sorry, but I'm not going to do that. If I had understood what it was about, that would have been the solution. My mistake.