Michael Murphy (S76) @ mmstick @lemmy.world

I'm a System76 engineer / Pop!_OS maintainer. I've been a Linux user since

---

Read more

Posts

59

Comments

280

Joined

2 yr. ago

Moderating

---

I'm using it with onboard audio at the moment. You may need to log out and log back in, and then start the filter-chain config before launching anything else. If not, running it with PIPEWIRE_DEBUG=3 might help.

The file manager isn't hardcoded to anything right now, and I don't see much point in doing so. We will have our own file manager that fits in with the COSMIC aesthetics and technologies though. We should be able to create something that will make Nemo and Dolphin users want to switch to COSMIC's file manager.

I don't think GTK has the tooling for that. It's stored in an XML file here: ~/.local/share/recently-used.xbel. One could write a program for this, but it's probably not worth it.

Use these two commands:

    
gsettings set org.gnome.desktop.interface gtk-theme "{{NAME_OF_THEME}}"
gsettings set org.gnome.shell.extensions.user-theme name "{{NAME_OF_THEME}}"

  

Or perhaps you mean the terminal theme. Depends on the terminal. I'm not aware of any that observe the desktop's dark preference.

There's an error in the script if python-is-python3 is not installed. May be worth calling python3 explicitly.

Fully update the system, restart, install blueman, run blueman-manager, right click on the bluetooth device, select sound profile, try different codecs. Some codecs need more bandwidth than others.

The stability of the bluetooth connection depends on the strength of the bluetooth transmitter and the amount of interference there exists nearby. If you're using a Bluetooth mouse or keyboard, try to switch to RF or wired.

Standard IT practice to turn it off and on again. Some updates require system restarts to apply the update to the running system, otherwise you may see some broken behavior where something's inaccessible because the installed drivers don't match the kernel you're using.

Yes, there is already a light theme.

Shortcuts are currently defined in /etc/cosmic-comp/config.ron. You may need to copy the config.ron from cosmic-comp's github repo. The default shortcut for the launcher is Super + /.

Yes, but the file chooser application hasn't been designed & developed yet.

Actually, cosmic packages are regularly released to the Pop!_OS release repository. All you have to do is enable Wayland in GDM and install cosmic-session. NVIDIA also requires a udev tweak to enable Wayland in GDM. See https://github.com/pop-os/cosmic-epoch/blob/master/README.md#installing-on-pop_os

If you have an older installation with a the 512 MB EFI partition, you need to edit /etc/initramfs-tools/initramfs.conf and set COMPRESS to xz. Then the next time you update the initramfs (sudo update-initramfs -c -k all), it should recover around 150 MB of space. We will probably change this to xz soon.

QA tests updates on some docks but I think as long as it's complaint to the Thunderbolt spec, it should be be fine. I suppose if it doesn't, you could return the dock.

If it's the meer6, Thunderbolt 3 and 4 are supported.

Disabled

What Rust's maintainers recommend is what I'd recommend: https://rust-lang.github.io/api-guidelines/

Many of these are automatically detected and suggested by clippy's pedantic flag.

Are you able to update the initramfs manually with sudo update-initramfs -c -k all? Besides custom kernels or relying on an oldkern boot, that's the only thing I can think of that might be causing a difference between what's in the initramfs and what's installed on the system.

Are there any warnings or errors that you see from journalctl -fk over time that you think would be related?

Purge any existing NVIDIA driver packages with sudo apt purge ~nnvidia. Run sudo apt autoremove to remove any remaining orphaned packages on the system. And then install the current driver with sudo apt install nvidia-driver-525. After rebooting, you should get stats when running nvidia-smi in a terminal.