New Updates For A New Decade | The Roundup #14

alecbcs

Hey everyone! Very impressive work by the Core Team again. The only issue I've run into after updating is, I think the latest kernel killed the bluetooth on my laptop. Gnome's Bluetooth settings appear to be in a permanent off position and after running,

bluetoothctl
power on

I get a No default controller available error. Running usysconf seems to make no difference. Anyone else run into this issue?

[Edit]
It actually seems to be an issue with usysconf? I rolled back and ran usysconf run -f then Bluetooth showed back up upon a new boot. Updating to the latest sync, everything appears to work as expected as long as I don't rerun usysconf run -f on the new kernel.

n2o

alecbcs Bluetooth goes back and forth here too (Dell XPS). It mostly works with the current kernel now. My speakers disappear from time to time so I have to reconnect them. That works with the LTS kernel but the LTS therefore drops the mouse every now and then and won't let me reconnect it. I then have to boot the current kernel, reconnect the mouse and go back to LTS. But as I said: right NOW it all works in the current kernel (knock knock knock)!

just

I thoroughly followed "big (systemd) upgrade" instructions, given in The Roundup #14. The upgrade was done 5 days ago and went apparently well, on all computers and in all Solus DEs. All DEs are installed in their own separate partitions and are completely independent one from another.

Only now, at a 5 days distance, I note a problem, which wasn't evident right after the upgrade. Network Time Synchronization (systemd-timesyncd.service) has stopped working. It happened in all DEs - Budgie, Gnome, Mate, Plasma.

Prior to upgrade systemd-timesyncd daemon was running without a problem. Budgie is restored from pre-upgrade backup in this example. The service was active:

$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-01-21 09:05:11 ***; 1min 51s ago
	 Docs: man:systemd-timesyncd.service(8)
 Main PID: 611 (systemd-timesyn)
   Status: "Idle."
	Tasks: 2 (limit: 4915)
   Memory: 2.1M
   CGroup: /system.slice/systemd-timesyncd.service
		   └─611 /usr/lib/systemd/systemd-timesyncd

Jan 21 09:05:11 alexsob.net systemd[1]: Started Network Time Synchronization.
Jan 21 09:05:12 alexsob.net systemd-timesyncd[611]: request_name_destroy_callback n_ref=1
Jan 21 09:05:14 alexsob.net systemd-timesyncd[611]: Network configuration changed, trying to establish connection.
Jan 21 09:05:14 alexsob.net systemd-timesyncd[611]: Network configuration changed, trying to establish connection.
$

After upgrade systemd-timesyncd is loaded but fails to start. The service is dead:

$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
	 Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
	 Active: failed (Result: exit-code) since Tue 2020-01-21 08:41:43 ***; 2min 16s ago
	   Docs: man:systemd-timesyncd.service(8)
	Process: 1493 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=238/STATE_DIRECTORY)
   Main PID: 1493 (code=exited, status=238/STATE_DIRECTORY)

Jan 21 08:41:43 alexsob.net systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 5.
Jan 21 08:41:43 alexsob.net systemd[1]: Stopped Network Time Synchronization.
Jan 21 08:41:43 alexsob.net systemd[1]: systemd-timesyncd.service: Start request repeated too quickly.
Jan 21 08:41:43 alexsob.net systemd[1]: systemd-timesyncd.service: Failed with result 'exit-code'.
Jan 21 08:41:43 alexsob.net systemd[1]: Failed to start Network Time Synchronization.
$

The are numerous old reports about the problem in Internet. None of them is related to or helps to solve the issue in Solus. I can't find any related info in Solus forum (here), blog posts, development portal.

What did I do wrong? Is there a way to have Network Time Synchronization up and running again?

algent

just Someone posted an issue with time sync in development portal and got it fixed.

just

algent Thank you very much for the precious link I missed somehow. Thanks to all guys in the thread. It's important to read the thread entirely, up to the end.

The problem is solved now and Network Time Synchronization works fine in all DEs here.

Thanks again, @algent !

WetGeek

just The problem is solved now and Network Time Synchronization works fine in all DEs here.

I was just about to create a script with those four commands, so I could update all the machines I've updated. I checked a VM on my laptop, and the hardware computer that drives our TV (both Solus Budgie) and both system times were correct.

In the Date & Time settings, I was surprised to find Automatic Date & Time turned off. Same for the TV computer. When I went upstairs to fetch my wristwatch I checked the two machines there, and they were both correct to the second. And on my laptop, I can verify that bluetooth is working fine and my earbuds work as expected.

I'm going to turn the Automatic Date & Time setting ON for some of these, and watch it over time, to see if that changes anything.

KingLucius

sudo eopkg up and sudo usysconf run -f twice.
sudo sync
logout via power menu
Full shutdown via hardware power button

Everything is smooth like butter , Budgie DE .

Thanks Josh

papyweb

KingLucius Yes...! Thanks.

WetGeek

WetGeek I'm going to turn the Automatic Date & Time setting ON for some of these, and watch it over time, to see if that changes anything.

Heh ... On the VM I turned Automatic Time & Date ON, and about 30 seconds later it turned itself back OFF. I thought that might be due to its relationship to the Windows host, where it might (or might not) be getting its time sync. So I turned that setting ON for the multimedia machine, and about 37 seconds later, that was also turned off.

So apparently I can't let these machines run for a while with the setting turned ON.

Related: I can get by until next week (and probably longer) with inaccurate system times on these Solus machines. Should we expect that next week's upgrades will handle this problem, or will we all need to fix it manually on every machine?

If it will fix itself with the next system upgrade, I can just live with it as-is until then.

elfprince

WetGeek Same here regarding Date & Time on my Solus Budgie. Was off, so I turned it on. Thanks! 😁

KingLucius

WetGeek I confirm this issue , Automatic time update is turn itself off after turning it on by about 25 seconds.
[Edit]
I can confirm that following the steps in this post solves the problem.

WetGeek

KingLucius I confirm this issue , Automatic time update is turn itself off after turning it on by about 25 seconds.

Now that this is an open issue, I remember that something seemed odd as I installed a new Solus Budgie VM recently. Normally I let the installer find the correct time zone automatically. This recent time, though, I had to select it manually. Since that's a trivial task, I didn't think much of it. Until new. Perhaps that's another clue?

KingLucius

WetGeek Did you tried the link after the edit ? it solved the issue at my end.

WetGeek

KingLucius Did you tried the link after the edit ?

I'm not sure what link you mean. I'm sure I didn't try any link, though.

just

Automatic Date & Time was switching from ON to OFF on its own while systemd-timesyncd.service was broken here.

Once systemd-timesyncd has been fixed - remains active all the time, - Automatic Date & Time remains permanently ON and doesn't switch to OFF anymore. I.e., works normally.

KingLucius

n2o WetGeek this is the commands I meant. try them it solved the issue at my end

n2o

sudo rm /var/lib/systemd/timesync
sudo systemctl restart systemd-timesyncd.service

Did the job here too. Same behaviour with time sync turning itself off.

WetGeek

KingLucius

I'll try those commands on one VM now, but I'm still hoping that next week's upgrade will fix it for all the other machines. Looking at the commands, I suspect it will be fixed there. Thanks!

WetGeek

KingLucius this is the commands I meant.

Yes. The Automatic Date & Time setting turned itself ON as soon as I'd executed those commands, and it's stayed on for long enough for me to call that problem fixed. Maybe I will take the time to fix all these machines now.

picnerd

Maybe the problem did not occur to all of them and a check would be good with : timedatectl status

It was the same for me and the workaround from mate-user helped.

greetings

WetGeek

picnerd a check would be good with : timedatectl status

Yes, thanks. I'd never used that command before, but it looks very useful. It generates a lot of good info!

« Previous Page Next Page »