From what I saw Cosmic has a lot of potential and looks pretty sleek too, right now I’m using KDE it’s a great desktop, but now that I have a second monitor it randomly crashes on me, I think I’ll switch to Cosmic when it reaches beta.
From what I saw Cosmic has a lot of potential and looks pretty sleek too, right now I’m using KDE it’s a great desktop, but now that I have a second monitor it randomly crashes on me, I think I’ll switch to Cosmic when it reaches beta.
I’m using it every day now. I have one machine installed with the 24.04 ISO and it’s working fine. There’s some TODO items to come which I understand will be added by Alpha2. With a little command line knowledge COSMIC is perfectly usable now and is stable.
I’m sure my command line game is weak. Do you have a solution for connecting to Bluetooth and for timing out to login screen and blanking it after a certain period?
Bluetooth can be managed with
systemctl
andbluetoothctl
.https://www.makeuseof.com/manage-bluetooth-linux-with-bluetoothctl/
In my experience I find just running
bluetoothctl
to enter the interactive mode easiest. You can enter commands without prependingbluetoothctl
. You can usehelp
at any stage. So you want to usesystemctl
to make sure Bluetooth is running, then enterbluetoothctl
. Make sure the device is discoverable and pairing is set to on. Start your [headphones/whatever] in pairing mode and rundevices
. When you see the device runpair
. Only use the numbers. You may have to go into settings and select the device in the sound applet.My situation doesn’t require a logout timer, but if I’m walking away from the PC I just use the shortcut Super + ESC. Alternatively, there’s many ways you can create a basic Bash script that when invoked times down to a
systemctl suspend
command. Or possibly the hybrid-sleep option could do what you want. Seesystemctl -h
for possibilities.Blanking the login screen is something that will be implemented shortly. Maybe I’ll work on a script for that because it annoys me too. Fortunately I rarely use it. I’ll repost if I do this.
I really don’t think the two years people are saying in this thread is realistic. The hard work and core is written. What is there is stable. I think they will get this completed much sooner. They do have a hardware business to support after all.
Thanks for the useful info. Still, I don’t think I want to fool with it until it’s available via GUI. That’s just me.
And I hope you are right about the rest being quicker.