manjaro-pinephone / plasma-mobile-dev: Update broken

[nelstomlinson]

I am running opensuse from the SD and I update the Manjaro like the previous time either with the dock or with `chroot` until the problem is solved again.

So sounds like I will have to find a monitor, mouse and keyboard to plug into the dock? Hadn't planned to do that any time soon, but I'm having this problem, too.

[ryo]

I am running opensuse from the SD and I update the Manjaro like the previous time either with the dock or with `chroot` until the problem is solved again.

So sounds like I will have to find a monitor, mouse and keyboard to plug into the dock? Hadn't planned to do that any time soon, but I'm having this problem, too.

I'm just using a dock and a LAN cable, and then SSH into it, if you want to cut a couple of extra hardware out.

[mouffa]

Today after a 105MB update containing many Plasma packages I was sure it would work, I got the same screen with the `loginctl`, so I logged in to terminal 3 again and

`sudo loginctl list-sessions`
`sudo loginctl unlock-session c1`
`sudo loginctl unlock-session c2`

then going back to terminal 2 which is the GUI I just get a black screen, it may be a problem with the wayland compositor.

[ryo]

Today after a 105MB update containing many Plasma packages I was sure it would work, I got the same screen with the `loginctl`, so I logged in to terminal 3 again and

`sudo loginctl list-sessions`
`sudo loginctl unlock-session c1`
`sudo loginctl unlock-session c2`

then going back to terminal 2 which is the GUI I just get a black screen, it may be a problem with the wayland compositor.

And the problem seems to exist on all branches too.
I originally updated while on unstable, switched to testing to downgrade packages to that branch, didn't work.
Then switched to stable to downgrade to everything to whatever is available in the stable branch, again didn't work.

I asked the Plasma Mobile team, but they told me to report to Manjaro instead.
However, Manjaro's Github server doesn't let me sign up for whatever reason, and their forum seems pretty silent about it too.
So let's just hope they're working on a fix behind the scenes.

[mouffa]

I am always on the stable branch. Indeed after some updates Plasma became better and the battery now lasts very long except for the strange behaviour of Angelfish and the keyboard. The overall stability of the distribution should be a responsibility of the Manjaro team, KDE would answer only for Neon. I think they upload the updates of every package immediately and sometimes the system breaks until all the necessary components have been updated.

[ryo]

I am always on the stable branch. Indeed after some updates Plasma became better and the battery now lasts very long except for the strange behaviour of Angelfish and the keyboard. The overall stability of the distribution should be a responsibility of the Manjaro team, KDE would answer only for Neon. I think they upload the updates of every package  immediately and sometimes the system breaks until all the necessary components have been updated.

The reason why I went to KDE in the first place is because the problem seemed to be in the Qt library, which is KDE's part.
Guess the only way out is to just back everything up, and flash a new image at this point.

[RenardRoux]

I am always on the stable branch. Indeed after some updates Plasma became better and the battery now lasts very long except for the strange behaviour of Angelfish and the keyboard. The overall stability of the distribution should be a responsibility of the Manjaro team, KDE would answer only for Neon. I think they upload the updates of every package  immediately and sometimes the system breaks until all the necessary components have been updated.

The reason why I went to KDE in the first place is because the problem seemed to be in the Qt library, which is KDE's part.
Guess the only way out is to just back everything up, and flash a new image at this point.

I don't have a solution, but during the update process a message appears saying that the "passwd" command needs to be run before rebooting due to something in the update. Haven't figured out how to do that before things get borked. I'm on stable and updated with "pacman -Syu".

edit: here's the quote from a serial terminal update on Beta 5 freshly installed: "You need to update your password![1;0m
Because of a library update, you need to update your password before you reboot. Run passwd to do so!"

[ryo]

I am always on the stable branch. Indeed after some updates Plasma became better and the battery now lasts very long except for the strange behaviour of Angelfish and the keyboard. The overall stability of the distribution should be a responsibility of the Manjaro team, KDE would answer only for Neon. I think they upload the updates of every package  immediately and sometimes the system breaks until all the necessary components have been updated.

The reason why I went to KDE in the first place is because the problem seemed to be in the Qt library, which is KDE's part.
Guess the only way out is to just back everything up, and flash a new image at this point.

I don't have a solution, but during the update process a message appears saying that the "passwd" command needs to be run before rebooting due to something in the update. Haven't figured out how to do that before things get borked. I'm on stable and updated with "pacman -Syu".

edit: here's the quote from a serial terminal update on Beta 5 freshly installed: "You need to update your password![1;0m
Because of a library update, you need to update your password before you reboot. Run passwd to do so!"

To be honest, not many people will read the output line by line unless the sentence clearly stands out.
My habit is to just check what packages are going to be updated, and then say "Y" to continue.
It does happen that something important shows up at the end of the update process, I expect it when updating GitLab or iRedMail since they do that every time.

[RenardRoux]

Today after a 105MB update containing many Plasma packages I was sure it would work, I got the same screen with the `loginctl`, so I logged in to terminal 3 again and

`sudo loginctl list-sessions`
`sudo loginctl unlock-session c1`
`sudo loginctl unlock-session c2`

then going back to terminal 2 which is the GUI I just get a black screen, it may be a problem with the wayland compositor.

Updating again today over a serial console (USB to 3.5mm jack) got me booted up after having the same issue. Looks like maybe a problem with the update that has been fixed. (Don't think the "passwd" thing I mentioned above needs to be done, but I'm not sure 'cause I did it) https://forum.manjaro.org/t/manjaro-arm-...e/69318/26

[mouffa]

now it works again, after updating the keys it updated 2 Qt packages and came back to life, it seems this will be happening often so keep a working distribution in an SD