my laptop resolution is 2256x1504, while my monitor has standard 1920x1080. when I start Pop is always default 200% scale, even I changed it to 100% before. I have to manually set it to 100% scale on my laptop and monitor. But it would not sustain. When I unplug hdmi and reconnect, everything goes back to default. Is there any ways I can optimize this? thank you

Reviewing some of the latest updates with the cosmic terminal, files, and more.

COSMIC is a Wayland desktop environment for Linux that is written in Rust with Smithay and Iced. COSMIC applications are developed with the libcosmic platform toolkit, which is based on iced. They are cross-platform and supported on Windows, Mac, and Redox OS in addition to Linux.

As COSMIC nears its alpha release in Q1 of 2024, we have thus far developed a terminal, file manager, and text editor for our desktop environment within the last few months.

• https://github.com/pop-os/cosmic-term
• https://github.com/pop-os/cosmic-files
• https://github.com/pop-os/cosmic-edit
• https://github.com/pop-os/cosmic-settings
• https://github.com/pop-os/libcosmic

See cosmic-epoch for instructions on building and installing COSMIC.

Everything worked fine until today, updated the system yesterday. Cursor works, I can start the reboot and such, but not app will open, no terminal command can be performed, and the shutdown doesn't finish after 30 minutes, meaning I have to perform a SysRq reboot to actually do something. Will check Discord and VSCode in a second, also try to apt update and post findings in an edit. Worst case I can wait for an update using dual-booted windows.

Edit: Apparently the problem fixed itself - none of the apps crashed, even when I went back to the previous settings. I've booted into Windows to write this post which might've helped (instead of breaking things the usual way), apt didn't do anything, but there were 2 runtime updates on Pop shop which I've installed prior to starting Firefox. Anyway, one of them can help if any of you are unfortunate enough to have the same problem.

Gaming on Linux is easier now than ever before. Though many PC games are still developed with Windows in mind, the emergence of Valve’s Proton and proceeding contributions from the open source community have made Linux gaming into a first-class experience.

Hi, I'm making this post today because I've been having some problems with Nvidia drivers with wayland. Looks like nvidia driver 535 was having some issues with Godot (flatpak), the error was something about Vulkan, anyway, it's not important now.

The versions 535 and 545 of the nvidia driver have been causing some problems on my machine while using wayland, so I'm making this tutorial for the folks that are encountering problems and wish to change their driver version to (hopefully) solve their bugs while waiting for the latest driver to be updated.

Let's get started.

DISCLAIMER: I am not responsible if you break your installation or if you damage your machine in any way.

1st step

First of all, I highly advise to install Timeshift. It's a neat program that will make a snapshot of your system configuration (depending on how you configure it) so you can roll back in time if something goes wrong. It saved my linux installation many times.

2nd step

If you wish to see your current driver version, open a terminal and type:

$ nvidia-smi

I advise to write the version down, or at least remember it.

3rd step

To view all the nvidia drivers you can install, open a terminal and execute:

$ ubuntu-drivers list

or

$ ubuntu-drivers devices

These 2 commands (you can use whatever you prefer) will tell you all the nvidia drivers that are available for installation.

To delete your current nvidia driver, open a terminal and execute:

$ sudo apt purge ~nnvidia

Then, you can install one of the nvidia drivers we have seen before, for example:

$ sudo apt install nvidia-driver-535-server

(If I understand correctly, the server drivers are no different from the normal drivers, other than the fact that they are supported for longer and they should in teory be more stable).

4th step

After your new driver is installed, you can reboot your machine, using the UI or the terminal by executing:

$ sudo reboot

5th step

If you want to use X11, you're done. If you want to use Wayland, you have to do some additional steps.

To enable wayland in pop-os, you first have to enable nvidia modeset if it's not already enabled.

To check if it's enabled, you can go inside /etc/modprobe.d/ and check if any of the files contains options nvidia_drm modeset=1. If you find nothing, you have to create the file yourself.

To do this, execute:

$ sudo nano /etc/modprobe.d/zz-nvidia-modeset.conf

The content of this file should be:

options nvidia_drm modeset=1

Then execute:

$ sudo update-initramfs -u

6th step

To be sure that there is nothing else blocking your machine from enabling wayland, execute:

sudo nano /usr/lib/udev/rules.d/61-gdm.rules

Inside this file there are some rules, some of which may stop your system from displaying the wayland option inside the little gear in the login screen.

Specifically, you have to check these lines:

LABEL="gdm_prefer_xorg"
#RUN+="/usr/libexec/gdm-runtime-config set daemon PreferredDisplayServer xorg"
GOTO="gdm_end"

LABEL="gdm_disable_wayland"
#RUN+="/usr/libexec/gdm-runtime-config set daemon WaylandEnable false"
GOTO="gdm_end"

LABEL="gdm_end"

Check that the lines starting with "run" are commented out.

7th step

We are almost done.

Execute in the terminal

$ sudo nano /etc/gdm3/custom.conf

Here you will find a line like this

# Uncoment the line below to force the login screen to use Xorg
# WaylandEnable=false

You can leave it as is, but if you can't see the wayland option in the login screen, you can come back and edit it like this:

# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=true

8th step

You can reboot your machine, and when it boots back up, you should hopefully see the wayland option in the bottom-right gear in the login screen.

9th step

Don't forget to run:

$ flatpak update

To allow flatpak to install the new version of the nvidia driver for your flatpak software.

Final

I hope you found this tutorial useful. If you want you can suggest improvements, or edit and share it on other platforms if you want more people to see it.

Resources

https://askubuntu.com/questions/1428525/how-to-permanetely-disable-wayland

https://lemmy.world/post/2155783

https://old.reddit.com/r/linuxquestions/comments/8fb9oj/how_to_fix_screen_tearing_ubuntu_1804_nvidia_390/dy2t8m1/

https://unix.stackexchange.com/questions/700938/enable-wayland-in-popos-22-04

Heyo,

i swapped to Pop!_os 2 days ago ( from linux mint, because i wanted some change and found pop_os ) and i like it!

I have just few points that i would like to share:

• That the displays scaling cant be changed per monitor untilthe activation of "Fractial Scaling" ( just as a beginner "weird" behaviour )

• You cant disable / make the "Active window" border smaller.

• You cant hide the top bar ( but thats acceptable as it hides itself if you are in full screen )

• Customizability/Lack of keybinds ( for example move active window to Screen 1,2,3 with Super + 1,2,3,4 )

• (The pop_store lags? sometimes if i search? idk if its just a known bug or if its something on my side?) )

But its still very good and it has some cool features and simple installation!

Thanks for the System76 devs for making such great OS!

LazPaint is a surprisingly good image editor.

I've looked around at many raster image editing apps for Linux, and I have mostly been disappointed.

• The Gimp is hard to use and has lagged behind major other platforms' banner image editors.
• Pinta is "ok" but has graphics glitches on my hardware (Intel).
• Inkscape is good but specializes in vector graphics, not raster images.
• Krita looks like it might be particularly good for artists using a tablet, but is mediocre for raster image tasks and has a complex interface.

I've also tried various "simple" apps such as KolourPaint [1] and Drawing [2], but these are generally more like "MS Paint" and have limited capabilities when importing images for various editing tasks.

LazPaint has all of the major features you would expect, without an over-complicated UI--selection, layers, gradients, filters, shapes, opacity, many file formats etc.. However, it is not wrapped in a Flatpak, so you need to download the "deb" file and install with Eddy (or the CLI):

https://github.com/bgrabitmap/lazpaint/releases/tag/v7.2.2

As an aside, I recently also discovered Pixelitor, and I think it's another one to keep an eye one. The author seems to be making some great progress lately (most recent release in September 2023).

• [1] https://flathub.org/apps/org.kde.kolourpaint
• [2] https://flathub.org/apps/com.github.maoschanz.drawing

Pictured are three COSMIC Terminal windows with different themes and syntax themes. The furthest in the back is terminal with a dark theme with the COSMIC Dark syntax theme. In the middle is a personalized, albeit questionable, desktop theme. In front is a light theme with the One Half Dark syntax theme.

COSMIC Terminal is a GPU-accelerated terminal for COSMIC which supports bidirectional text and ligatures. As it is built using the libcosmic platform toolkit, and thereby iced, it is rendered with Vulkan using the wgpu Rust library. The terminal functionality is provided by the alacritty Rust library, and text rendering by cosmic-text. It will support platform integrations with COSMIC themes, as well as featuring syntax themes like COSMIC Editor.

Developed for the display settings page, and compatible with all Wayland compositors which support the wlr-output protocols, cosmic-randr is a new Rust library and command line utility for displaying and configuring display outputs on Wayland desktops.

This is cosmic-term, a very WIP project that takes the alacritty_terminal crate providing the majority of terminal code but rewrites the renderer to support additional features such as bidirectional text and ligatures. It will support both software and GPU rendering, and will have additional UI sugar provided by libcosmic as they are implemented.

cosmic-term

I ran apt upgrade on my laptop today after not using it for a couple of weeks, the main thing was upgrade of NVIDIA driver to 545.29.06, but there was also some change on one of the steam-lib packages (I'm using the Steam deb version, not flatpak). Ever since upgrading, Steam crashes on start.

I tried searching for recently reported issues with the Steam Linux client but can't find anything. Is this a known issue? Any suggestions on what I can check/do?

=-=-=

Here's the segfault from syslog, I have a bunch of core files but don't know if I can get anything useful from them.

Dec  6 17:13:30 computer steam.desktop[5200]: steam.sh[5200]: Running Steam on pop 22.04 64-bit
Dec  6 17:13:30 computer steam.desktop[5200]: steam.sh[5200]: STEAM_RUNTIME is enabled automatically
Dec  6 17:13:30 computer steam.desktop[5321]: setup.sh[5321]: Steam runtime environment up-to-date!
Dec  6 17:13:31 computer steam.desktop[5200]: steam.sh[5200]: Steam client's requirements are satisfied
Dec  6 17:13:31 computer steam.desktop[5392]: 12/06 17:13:31 Init: Installing breakpad exception handler for appid(steam)/version(1701289036)/tid(5392)
Dec  6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/main.rc:727: error: unexpected identifier 'direction', expected character '}'
Dec  6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/apps/chrome.rc:50: error: invalid string constant "button", expected valid string constant
Dec  6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/apps/xfce.rc:79: error: invalid string constant "entry", expected valid string constant
Dec  6 17:13:33 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: Uploading dump (out-of-process)
Dec  6 17:13:33 computer steam.desktop[5404]: /tmp/dumps/crash_20231206171333_5.dmp
Dec  6 17:13:33 computer crash_20231206171333_5.dmp[5404]: Uploading dump (out-of-process)#012/tmp/dumps/crash_20231206171333_5.dmp
Dec  6 17:13:33 computer kernel: [   72.142532] show_signal_msg: 19 callbacks suppressed
Dec  6 17:13:33 computer kernel: [   72.142534] steam[5392]: segfault at 0 ip 00000000f7ab5045 sp 00000000fffb3e8c error 4 in libc.so.6[f7a20000+182000] likely on CPU 4 (core 4, socket 0)
Dec  6 17:13:33 computer kernel: [   72.142544] Code: 40 38 ca 0f 84 4d 01 00 00 80 f9 00 0f 84 71 01 00 00 40 4f 75 14 8a 08 38 ca 0f 84 36 01 00 00 80 f9 00 0f 84 5a 01 00 00 40 <8b> 08 bd ff fe fe fe bf ff fe fe fe 01 cd 31 cd 01 cf 8d 40 04 0f
Dec  6 17:13:33 computer steam.desktop[5200]: /home/user/.local/share/Steam/steam.sh: line 798:  5392 Segmentation fault      (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
Dec  6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: Finished uploading minidump (out-of-process): success = yes
Dec  6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: response: CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206
Dec  6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: file ''/tmp/dumps/crash_20231206171333_5.dmp'', upload yes: ''CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206''
Dec  6 17:13:35 computer crash_20231206171333_5.dmp[5404]: Finished uploading minidump (out-of-process): success = yes
Dec  6 17:13:35 computer crash_20231206171333_5.dmp[5404]: response: CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206
Dec  6 17:13:35 computer crash_20231206171333_5.dmp[5404]: file ''/tmp/dumps/crash_20231206171333_5.dmp'', upload yes: ''CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206''
Dec  6 17:13:35 computer systemd[3855]: app-gnome-steam-5200.scope: Consumed 1.187s CPU time.

I wanted to transfer some files from my phone to my old laptop and when I opened LocalSend it looked like this. It's installed via Flatpak, everything is up to date. I've reinstalled LocalSend, I've reinstalled org.freedesktop.Platform.GL.default, I've reinstalled my graphics drivers, I've prayed to my Torvalds-Shrine, I don't know how to fix this. Other Flatpak apps, even the ones that use the same version of org.freedesktop.Platform.GL.default work perfectly fine. Any ideas?

Was just browsing the site an saw that S76 now offers components on some of the stuff they sell. That is really cool.

The pop_os subreddit has many Pop!_OS-specific help requests per day. I'm kind of surprised there aren't more here on the Fediverse/lemmy side of the community.

I browse looking for ways to help, and after having shifted my attention from Reddit to the Fediverse I feel like I could be helping out more. Why aren't there more requests here?

In the dynamic world of Linux a new Linux distribution is nothing new, but Pop!_OS is something special. Born out of necessity when Ubuntu announced the end of its Unity Desktop in 2017, Pop!_OS has not just filled the void left by Unity, but has carved out a distinct identity in the Linux community. This journey, from an alternative for disillusioned Unity users to the creation of the innovative COSMIC desktop has created a version of Linux that has been very well received. But to understand how we got to Pop! We have to look back at what happened to Unity.

@[email protected] I had a feature request, but I wasn't sure if it belonged here or sent directly to System 76.

It would be wonderful if we could configure the maximum battery charge level. Many people (myself included) leave our laptops plugged in, and I am relatively confident it is bad for the battery to let it set at near 100% or at 100% essentially forever.

I suspect this would require a firmware update, and I don't know if it would only be possible with the new laptop System 76 being developed from the ground up.

Anyway, I just wanted to throw it out there as I think it would be a great feature.

Check out my latest review of the Rust Cosmic Desktop updates. This one is getting some serious attention - https://youtu.be/L7iiJhfV3_s

Floating windows, UI implementation, and compositor improvements for the new COSMIC desktop environment.