Sync Updates for Week 46, 2023

Patrice

Hi all,
After this update, something went wrong with Evolution.
When I click to see a message, I have a notification saying that :

A process WebKitWebProcess stopped suddenly when printing message.

Some other messages are just empty with the same notification on top of it.
I can file a bug if you need, unless someone already got the solution. Let me know.

I found some kind of same bug here :
https://gitlab.gnome.org/GNOME/evolution/-/issues/1854
And here :
https://discuss.getsol.us/d/8613-evolution-webkitwebprocess-problem

MetaNorm

Patrice
I can confirm that.

Sebastian

Patrice A downgrade of libwebkit-gtk41 seems to solve the issue:

sudo eopkg install https://packages.getsol.us/shannon/libw/libwebkit-gtk41/libwebkit-gtk41-2.42.1-15-1-x86_64.eopkg

Though as the noob that I am, I can't tell if it is advisable to do so. But you can always reverse it by just updating again with sudo eopkg up

I filed an issue on our bug tracker.

synth-ruiner

Patrice my Evolution won't connect to my mail server now. Just hangs on "Scanning folders in IMAP server..." and keeps prompting me for my password. I even changed the password just to make sure, but no luck. I can get to it via Thunderbird with the same config and credentials so I think this is specifically an Evolution problem.

LarsImNetz

One very important information:
If you create a /etc/pam.d directory after the Update (copy from /usr/share/defaults/etc/pam.d)
and then downgrade to the old history (eopkg history -t <old>)
REMOVE the /etc/pam.d before reboot, or you will NOT be able to login any longer.

I need to boot from an old install USB Stick and remove the directory by hand.

Just a hint from me.

Solarmass

Love those detailed notes with examples!

ReillyBrogan

fernkaufmann That one is fine. Should be safe to ignore it.

ReillyBrogan

LarsImNetz Do you mean because of the changes to /etc/environment? You can still use that file, you just need to have it in the following format instead:

DISPLAY=:0

The file is read by pam_env, not by shells so it doesn't use export.

Patrice

@MetaNorm, I think problem comes from libwebkit-gtk that has been updated.
Maybe a downgrade will solve the problem. I just don't want to try.

Patrice

Sebastian , thanks, it works.
I'll wait for the next update to see if problem is solved.

brent

Updated 95 packages, desktop computer, budgie, last night and went to bed. Now home from work I've had 1 hour of uptime and every file, app, folder and menu functions as per normal. The rig is fine, thank you.

Postscript: a pam update usually means back to a virgin terminal with the 'great responsibility' dialogue that greets a first-timer...(I'm assuming pam update does that..)

WetGeek

I'm having some problems with the version of Telegram installed from the repository. I use it every day to keep in touch with friend from LA tp France. This problem has never occurred before today's update.

It seems to time out after a while, and the UI closes. If I restart it from the Latte dock, it's as if nothing happened. A message I started to write will be intact up to the character I typed just before the UI closed. The above is the notification that occurs a while before the error occurs.

This is not keeping me from using Telegram. Just making it damned inconvenient, requiring frequent restarts. I have performed a clean new installation--reading the PC version's QR code from the mobile--and that appears not to change anything. The same behavior soon begins.

I ran eopkg check | grep Broken and the update was clean.

ReillyBrogan

WetGeek I've noticed some similar behavior and I think it might have to do with having Telegram autostart or start minimized to the tray. I'm hoping that an update to qt6 that I'm planning to do in the next week or so might help.

It's just annoying, it's not like it's not usable though which is why I decided to keep the update. We'd been stuck on 4.8.4 for so long due to dependency issues that I figured more users would appreciate the new version.

WetGeek

ReillyBrogan It's just annoying, it's not like it's not usable

I agree, and said as much in my post. I wish you luck with finding the solution.

After I reinstalled, it seems to last longer before it closes. That's just a subjective impression, not a measurement. I've gone off to do things in other workspaces, and noticed that it's stil up and running in its own. But eventually it disappears again.

elfprince

I too noticed that for a while now, Telegram (installed from repo) aborts from time to time without any notice. Attempts to restart fail, as it aborts right after I access chats. If I wait a few hours and restart again, it seems to stop this behaviour. Puzzling.

ReillyBrogan

Sometimes when it says it "aborted" I find that it's still running in the status bar. Seems to be that Plasma might be confused with the user clicking on the icon and it not starting up (because it's already running minimized).

WetGeek

ReillyBrogan Sometimes when it says it "aborted" I find that it's still running in the status bar.

I'm not sure that's true in my case, but I've never looked in the status bar to check. I've always restarted it from Latte, as I mentioned in my earlier post. But I'll check that the next time it happens to me. Anything I can do to help with debugging this, please just ask.

EDIT: Yup, I just checked, and it's not present in my Plasma status bar. I checked the hidden icons, as well.
MORE: To be clear, I don't use a task manager, just the Latte dock. What I checked was the system tray.

Harvey

Firefox 120.0 cherry-picked.

brent

@"Harvey"#p87358on first glance this change link was interesting. some cosmetic only 'improved' tracking stuff including the fingerprint implemented..I got this covered and back in :config...so neglibible for me.

Some moves regarding a new German law and the trust anchors....at small writing at the bottom of that page it says "view security fixes"--

now that was the money page. of 10 CVE warnings, 5 were marked 'high' impact. 10 is plenty of CVE's. thanks for getting on 120.00.

Harvey

Thunderbird 115.5.0 cherry-picked.

mbevks

I normally wait a couple of days after an update to see if there is much chatter in the forum. This update has me nervous. I am a non-technical user. Am I better off waiting until next week so there are less issues? I really cannot deal with not being able to login, if that's a common problem. When I do update, is there anything I should do first to avoid serious issues?

elfprince

mbevks I feel same way. Many of us depend on the Solus OS for their work, and/or important daily work/chores at home. Can't afford to have a broken system. Always keep my fingers and toes crossed when updates arrive. 😃

ReillyBrogan

mbevks Not being able to login is not a common problem. The sole affected user who reported that was using a custom compiled shell and had not added it to their /etc/shells file. Really it should have never worked in the first place, and the fact that it did is reflective of the prior poor state of our PAM stack (which is now corrected).

As long as you do not have any of the following it should be safe to update:

A custom user shell (like xonsh) that is not packaged in the repos. If you do have one (like oil or xonsh) it can still work you just need to make sure to add it to /etc/shells.
A /etc/environment or /etc/environment.d/* file that uses export VARIABLE=VALUE syntax. You just need to change it to VARIABLE=VALUE syntax instead.
Custom files in /etc/pam.d (if you have a /etc/pam.d/vlock that one is fine and expected).

I totally get the reluctance to update, but keep in mind that people with problems are much more likely to post about it than people who aren't having any problems.

brent

mbevks I would be nervous at 90% (see poll) too with 0% able to DIY their problem (see poll). these hiccups are always temporary and there is other stuff to spend your anxiety on.

mbevks I really cannot deal with not being able to login, if that's a common problem

it's going to happen to everybody in any distro at least once in a lifetime--this fear is not solus-related. there's a trillion factors. if you have booted successfully 499 times out of 500--anywhere-- I'd say this is par across the linux spectrum any way. The Win BSOD was part of day-to-day life for a while.

short version: play the odds

« Previous Page Next Page »