pop-os / cosmic-session Goto Github PK

On both an existing regularly updated install (over 6 months old) and on a fresh install (literally yesterday), I was noticing that using the Super + F shortcut in cosmic-session was resulting in code-editors installed as flatpaks to open, instead of the current system default of org.gnome.Nautilus.desktop

This does not appear to be a unique problem for either Pop or Cosmic, as I found a couple of issues over the last three years reporting similar behaviour, as well as at least one issue where a standard package install of a code editor was being preferenced by flatpaks and snaps over a file manager.

On my system, running XDG_UTILS_DEBUG_LEVEL=2 xdg-mime query default inode/directory resulted in

Checking /home/daniel/.config/mimeapps.list
Checking /home/daniel/.local/share/applications/defaults.list and /home/daniel/.local/share/applications/mimeinfo.cache
Checking /home/daniel/.local/share/applications/defaults.list and /home/daniel/.local/share/applications/mimeinfo.cache
Checking /usr/share/cosmic/applications/defaults.list and /usr/share/cosmic/applications/mimeinfo.cache
Checking /usr/share/cosmic/applications/defaults.list and /usr/share/cosmic/applications/mimeinfo.cache
Checking /home/daniel/.local/share/flatpak/exports/share/applications/defaults.list and /home/daniel/.local/share/flatpak/exports/share/applications/mimeinfo.cache
com.vscodium.codium.desktop

Searching those files for inode/directory pointed to ~/.local/share/flatpak/exports/share/applications/mimeinfo.cache being the culprit:

daniel@iapetus:~$ cat ~/.local/share/flatpak/exports/share/applications/mimeinfo.cache |grep inode
inode/directory=com.vscodium.codium.desktop;

The two other locations which list explicit values for the inode/directory mimetype were
/usr/share/applications/mimeinfo.cache

inode/directory=com.system76.CosmicFiles.desktop;org.gnome.Nautilus.desktop;org.gnome.baobab.desktop;

and /usr/share/applications/defaults.list

inode/directory=org.gnome.Nautilus.desktop

I'm not sure why the flatpak's mimeinfo.cache is being preferenced over any other value. I saw this with VSCodium, VSCode, and Lapce, all installed as flatpaks. I have yet to test whether this is true of standard package installs (i.e. installing the .deb for VSCode). Testing that will be my next-step.

When attempting to logout, the logout prompt is dismissed if anywhere other than the confirm button is clicked. This seems to stop the logout process, but the behaviour is non-obvious in the case of a mis-click, especially when the mis-click is executed while trying to hit "Confirm".

The correct behaviour should probably be for the prompt to persist unless one of the two buttons is successfully pressed.

it becomes unbearable slow after login. i was using normally and suddenly it becomes like this.

checking journal logs, i saw the following

Mar 19 21:26:37 twin-engines cosmic-session[39887]: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load compositor config: [NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory]
Mar 19 21:26:37 twin-engines /usr/libexec/gdm-wayland-session[39887]: 2024-03-19T14:26:37.561980Z  WARN cosmic-workspaces: cosmic_session: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load compositor config: [NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfig>
Mar 19 21:26:37 twin-engines /usr/libexec/gdm-wayland-session[39887]: 2024-03-19T14:26:37.562019Z  WARN cosmic-workspaces: cosmic_session: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load workspaces config: [NoConfigDirectory, NoConfigDirectory]
Mar 19 21:26:37 twin-engines cosmic-session[39887]: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load workspaces config: [NoConfigDirectory, NoConfigDirectory]
Mar 19 21:26:37 twin-engines cosmic-session[39887]: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load workspaces config: [NoConfigDirectory, NoConfigDirectory]
Mar 19 21:26:37 twin-engines /usr/libexec/gdm-wayland-session[39887]: 2024-03-19T14:26:37.565936Z  WARN cosmic-workspaces: cosmic_session: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load workspaces config: [NoConfigDirectory, NoConfigDirectory]
Mar 19 21:26:37 twin-engines /usr/libexec/gdm-wayland-session[39887]: 2024-03-19T14:26:37.566068Z  WARN cosmic-workspaces: cosmic_session: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load compositor config: [NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfig>
Mar 19 21:26:37 twin-engines cosmic-session[39887]: [2024-03-19T14:26:37Z ERROR cosmic_workspaces] Failed to load compositor config: [NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory, NoConfigDirectory]

Commit a4a791e in the master branch is not building.

   Compiling lock_api v0.4.8
   Compiling slab v0.4.7
   Compiling tokio v1.21.1
   Compiling memoffset v0.6.5
   Compiling polling v2.3.0
   Compiling async-io v1.9.0
   Compiling sha1 v0.6.1
   Compiling slotmap v1.0.6
   Compiling async-channel v1.7.1
   Compiling ordered-stream v0.0.1
   Compiling tracing-log v0.1.3
   Compiling futures-lite v1.12.0
   Compiling object v0.29.0
   Compiling aho-corasick v0.7.19
error[E0658]: trait bounds other than `Sized` on const fn parameters are unstable
   --> /home/jacob/Work/cosmic-session/vendor/lock_api/src/mutex.rs:150:6
    |
150 | impl<R: RawMutex, T> Mutex<R, T> {
    |      ^
...
154 |     pub const fn new(val: T) -> Mutex<R, T> {
    |     --------------------------------------- function declared as const here
    |
    = note: see issue #93706 <https://github.com/rust-lang/rust/issues/93706> for more information
    = help: add `#![feature(const_fn_trait_bound)]` to the crate attributes to enable

error[E0658]: trait bounds other than `Sized` on const fn parameters are unstable
   --> /home/jacob/Work/cosmic-session/vendor/lock_api/src/remutex.rs:231:6
    |
231 | impl<R: RawMutex, G: GetThreadId, T> ReentrantMutex<R, G, T> {
    |      ^
...
235 |     pub const fn new(val: T) -> ReentrantMutex<R, G, T> {
    |     --------------------------------------------------- function declared as const here
    |
    = note: see issue #93706 <https://github.com/rust-lang/rust/issues/93706> for more information
    = help: add `#![feature(const_fn_trait_bound)]` to the crate attributes to enable

error[E0658]: trait bounds other than `Sized` on const fn parameters are unstable
   --> /home/jacob/Work/cosmic-session/vendor/lock_api/src/remutex.rs:231:19
    |
231 | impl<R: RawMutex, G: GetThreadId, T> ReentrantMutex<R, G, T> {
    |                   ^
...
235 |     pub const fn new(val: T) -> ReentrantMutex<R, G, T> {
    |     --------------------------------------------------- function declared as const here
    |
    = note: see issue #93706 <https://github.com/rust-lang/rust/issues/93706> for more information
    = help: add `#![feature(const_fn_trait_bound)]` to the crate attributes to enable

error[E0658]: trait bounds other than `Sized` on const fn parameters are unstable
   --> /home/jacob/Work/cosmic-session/vendor/lock_api/src/rwlock.rs:367:6
    |
367 | impl<R: RawRwLock, T> RwLock<R, T> {
    |      ^
...
371 |     pub const fn new(val: T) -> RwLock<R, T> {
    |     ---------------------------------------- function declared as const here
    |
    = note: see issue #93706 <https://github.com/rust-lang/rust/issues/93706> for more information
    = help: add `#![feature(const_fn_trait_bound)]` to the crate attributes to enable

For more information about this error, try `rustc --explain E0658`.
error: could not compile `lock_api` due to 4 previous errors
warning: build failed, waiting for other jobs to finish...
error: build failed
error: Recipe `all` failed on line 17 with exit code 101
make[1]: *** [debian/rules:27: override_dh_auto_build] Error 101
make[1]: Leaving directory '/home/jacob/Work/cosmic-session'
make: *** [debian/rules:8: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

COSMIC is still pre-alpha (which is why master doesn't have branch protection and why we're not checking COSMIC packages too closely in repo-release), but this package is temporarily unavailable to install since the non-built version was released in pop-os/repo-release#175.

As title says, I booted from GDM and the cursor from GDM just stayed in the same spot and didn't disappear. Don't know why or how to get rid of it.

The initialization behavior, and whether profile is read, varies from shell to shell, often .profile is not read at all.
if I remember correctly:

• bash uses .profile if .bash_profile doesn't exist in home or $XDG_CONFIG_HOME/bash
• fish just reads $XDG_CONFIG_HOME/fish/config.fish and has a special flag for running the login shell
• zsh uses .z_profile, I'm not sure if it checks for .profile if .z_profile isn't present.

shells have a -l flag that runs them as a login shell, which does thing such as read the appropriate profile and I think set a few environment variables. I'd recommend using that

Hi!

I just installed the pre-alpha for cosmic session and ran into a bug.

Usually when selecting display, portrait flipped (or landscape flipped) would mean rotate the display 180 degrees (flipped upside down).

However, it appears in cosmic-session, it just mirrors the display instead.

This prevents users who have a vertical monitor in the flipped orientation from using it.

Normal portrait:

Flipped (mirrored) portrait:

In reality, the desired outcome for flipped is as follows for portrait:

Specs if it is helpful:

Misspelling word 'environment' in description

Session manager for the COSMIC desktop enviornment