This might be a bug.

shingamba

I have a dual boot Solus budgie and windows 10.
Sometimes when i use Windows with my earphones plugged in and then shut down and boot into Solus with the earphones kept plugged in, the audio output will work on the earphones but when unplugged the in-built speaker doesn't output any sound although in the sound settings it shows that the in-built speakers have sound output.
I cannot always reproduce this bug, it happens occasionally, and it's fix is to restart with the earphones unplugged. But this never happens with windows so, i feel its not a hardware issue but a software issue with Solus. Hope you guys could look into this.
Laptop specs:

HP HP Pavilion Power Laptop 15-cb0xx
8.0 GB RAM
Intel® Core™ i5-7300HQ
NVIDIA GeForce GTX 1050
1 TB HDD

brent

shingamba Sometimes when i use Windows with my earphones plugged in and then shut down and boot into Solus with the earphones kept plugged in,

when I did dual boot I always noticed problems in Solus because of Windows after I'd use it and go back to Solus. It might be only an occasional problem for you because they happen after Windows updates. I had system clock shut down and modem manager services, among other things, shut down a few times that way. (the first place to check when it happens is systemctl).
Once I unplugged Windows these things never happened again.
2 cents

synth-ruiner

brent yeah, when I was dual-booting with Windows it would mess up the clock - I think Windows handles daylight saving time by changing the system clock twice a year, whereas Linux leaves it alone and handles the hour difference in software or something

kaktuspalme

synth-ruiner I think Windows sets the time on the mainboard to locale time while Linux sets it to UTC time or the other way around. Not sure.

WetGeek

kaktuspalme I think Windows sets the time on the mainboard to locale time while Linux sets it to UTC time or the other way around

Dunno what Windows does -- I don't use it. But I'm pretty sure you're right about the default for Linux, although it's something that the user can change.

synth-ruiner

kaktuspalme That would make sense, I'm in the UK so it's the same as UTC for half the year!

johano

That's right, @kaktuspalme. Linux by default assumes the real time clock (RTC) is set to UTC, whereas Windows 10 assumes it is set to Local Time. The solution is to force Windows 10 to always assume that—as in Linux—the RTC is set to UTC. Merging the following .regfile into the Windows registry does just that, and dual boot of Linux/Win10 will then abide happily together keeping the correct time without further intervention.

The registry file:
Create a plain text file with the following content, and save it with the .reg extension. Then double-click this file in your file manager to merge with the registry. Or edit the registry key manually using regedit.exe

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
     "RealTimeIsUniversal"=hex(b):01,00,00,00,00,00,00,00

penny-farthing

johano

Before switching to Solus, I was on Ubuntu and I had already noticed this time difference displayed by Linux and Windows.

On the Ubuntu forum in April 2016 (https://forum.ubuntu-fr.org/viewtopic.php?id=1988881), Malbo recommended the following command:

sudo timedatectl set-local-rtc 1

and that's how I solved the problem at this time.

Thanks for this new insight.

johano

penny-farthing, both solutions work. I left Solus at the default setting and forced Windows to change. Although your solution is more straightforward, I thought there might be other implications of changing from UTC that I'm unaware of, and as I rarely use windows prefer to keep Solus at its default