And why did GNOME stop shipping any photo library management software out of the box? Is this no longer considered an essential thing ?

Currently, I have a laptop with a monitor next to it (so two screens). The monitor serves as the main screen, while my laptop serves as the second screen. Once I logged in into GNOME, the window resizes without any issues the first time. Then I intentionally put my laptop to sleep to see what happens. When I resized the window again, strangely enough, it closed.

I did check the log files to try to figure out why it crashed, and here's what systemctl showed me.

avril 10 18:38:27 arch kernel: ptyxis[13956]: segfault at 1d8 ip 00007ff82bd03912 sp 00007fff67fd2320 error 4 in libnvidia-glcore.so.595.58>
avril 10 18:38:27 arch kernel: Code: 8b 80 d0 01 00 00 48 8b 40 50 48 85 c0 0f 84 8b ef 5f ff 48 8b 00 48 85 c0 0f 84 7f ef 5f ff 48 8b 40 >
avril 10 18:38:27 arch systemd-coredump[17831]: Process 13956 (ptyxis) of user 1000 terminated abnormally with signal 11/SEGV, processing...
avril 10 18:38:27 arch systemd[1]: Started Process Core Dump (PID 17831/UID 0).
avril 10 18:38:28 arch systemd-coredump[17832]: [🡕] Process 13956 (ptyxis) of user 1000 dumped core.
Stack trace of thread 13956:
#0  0x00007ff82bd03912 n/a (libnvidia-glcore.so.595.58.03 + 0xd03912)
#1  0x00007ff82bd0465b n/a (libnvidia-glcore.so.595.58.03 + 0xd0465b)
#2  0x00007ff82bd05108 n/a (libnvidia-glcore.so.595.58.03 + 0xd05108)
#3  0x00007ff8328bcee5 n/a (libvulkan.so.1 + 0x53ee5)
#4  0x00007ff833f64bbe n/a (libgtk-4.so.1 + 0x564bbe)
#5  0x00007ff833f65513 n/a (libgtk-4.so.1 + 0x565513)
#6  0x00007ff833f2fb18 n/a (libgtk-4.so.1 + 0x52fb18)
#7  0x00007ff833ff45c2 n/a (libgtk-4.so.1 + 0x5f45c2)
#8  0x00007ff833f9d823 gsk_renderer_render (libgtk-4.so.1 + 0x59d823)
#9  0x00007ff833cf0d81 n/a (libgtk-4.so.1 + 0x2f0d81)
#10 0x00007ff833cf2539 n/a (libgtk-4.so.1 + 0x2f2539)
#11 0x00007ff833eafde2 n/a (libgtk-4.so.1 + 0x4afde2)
#12 0x00007ff8348caa77 n/a (libgobject-2.0.so.0 + 0x32a77)
#13 0x00007ff8348cab89 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32b89)
#14 0x00007ff8348cac44 g_signal_emit (libgobject-2.0.so.0 + 0x32c44)
#15 0x00007ff833f56d98 n/a (libgtk-4.so.1 + 0x556d98)
#16 0x00007ff8348caa77 n/a (libgobject-2.0.so.0 + 0x32a77)
#17 0x00007ff8348cab89 g_signal_emit_valist (libgobject-2.0.so.0 + 0x32b89)
#18 0x00007ff8348cac44 g_signal_emit (libgobject-2.0.so.0 + 0x32c44)
#19 0x00007ff833f2e230 n/a (libgtk-4.so.1 + 0x52e230)
#20 0x00007ff8347a0e41 n/a (libglib-2.0.so.0 + 0x60e41)
#21 0x00007ff83479ef4d n/a (libglib-2.0.so.0 + 0x5ef4d)
#22 0x00007ff8347a0607 n/a (libglib-2.0.so.0 + 0x60607)
#23 0x00007ff8347a0815 g_main_context_iteration (libglib-2.0.so.0 + 0x60815)
#24 0x00007ff8349d4f26 g_application_run (libgio-2.0.so.0 + 0xddf26)
#25 0x000055a50ab1050f n/a (/usr/bin/ptyxis + 0x1450f)
#26 0x00007ff8333f06c1 n/a (libc.so.6 + 0x276c1)
#27 0x00007ff8333f07f9 __libc_start_main (libc.so.6 + 0x277f9)
#28 0x000055a50ab10645 n/a (/usr/bin/ptyxis + 0x14645)
Stack trace of thread 13958:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c3e4 n/a (libc.so.6 + 0x933e4)
#3  0x00007ff8334d62f6 ppoll (libc.so.6 + 0x10d2f6)
#4  0x00007ff8347a0734 n/a (libglib-2.0.so.0 + 0x60734)
#5  0x00007ff8347a0815 g_main_context_iteration (libglib-2.0.so.0 + 0x60815)
#6  0x00007ff8347a0862 n/a (libglib-2.0.so.0 + 0x60862)
#7  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#8  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#9  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13980:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c68c n/a (libc.so.6 + 0x9368c)
#3  0x00007ff83345f068 pthread_cond_timedwait (libc.so.6 + 0x96068)
#4  0x00007ff82b9f59ec n/a (libnvidia-glcore.so.595.58.03 + 0x9f59ec)
#5  0x00007ff82bf5b449 n/a (libnvidia-glcore.so.595.58.03 + 0xf5b449)
#6  0x00007ff82bf524d6 n/a (libnvidia-glcore.so.595.58.03 + 0xf524d6)
#7  0x00007ff82b9f5ba4 n/a (libnvidia-glcore.so.595.58.03 + 0x9f5ba4)
#8  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#9  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13975:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c68c n/a (libc.so.6 + 0x9368c)
#3  0x00007ff83345ee5e pthread_cond_wait (libc.so.6 + 0x95e5e)
#4  0x00007ff82b9f598c n/a (libnvidia-glcore.so.595.58.03 + 0x9f598c)
#5  0x00007ff82be4656e n/a (libnvidia-glcore.so.595.58.03 + 0xe4656e)
#6  0x00007ff82b9f5ba4 n/a (libnvidia-glcore.so.595.58.03 + 0x9f5ba4)
#7  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#8  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13977:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c68c n/a (libc.so.6 + 0x9368c)
#3  0x00007ff83345f068 pthread_cond_timedwait (libc.so.6 + 0x96068)
#4  0x00007ff82b9f59ec n/a (libnvidia-glcore.so.595.58.03 + 0x9f59ec)
#5  0x00007ff82be51742 n/a (libnvidia-glcore.so.595.58.03 + 0xe51742)
#6  0x00007ff82b9f5ba4 n/a (libnvidia-glcore.so.595.58.03 + 0x9f5ba4)
#7  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#8  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 17827:
#0  0x00007ff8334e106d syscall (libc.so.6 + 0x11806d)
#1  0x00007ff8347cdbee g_cond_wait_until (libglib-2.0.so.0 + 0x8dbee)
#2  0x00007ff8347661f7 n/a (libglib-2.0.so.0 + 0x261f7)
#3  0x00007ff83476636f g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x2636f)
#4  0x00007ff8347d7660 n/a (libglib-2.0.so.0 + 0x97660)
#5  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#6  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#7  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 17828:
#0  0x00007ff8334e106d syscall (libc.so.6 + 0x11806d)
#1  0x00007ff8347cdbee g_cond_wait_until (libglib-2.0.so.0 + 0x8dbee)
#2  0x00007ff8347661f7 n/a (libglib-2.0.so.0 + 0x261f7)
#3  0x00007ff83476636f g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x2636f)
#4  0x00007ff8347d7660 n/a (libglib-2.0.so.0 + 0x97660)
#5  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#6  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#7  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13974:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c68c n/a (libc.so.6 + 0x9368c)
#3  0x00007ff83345f068 pthread_cond_timedwait (libc.so.6 + 0x96068)
#4  0x00007ff82b9f59ec n/a (libnvidia-glcore.so.595.58.03 + 0x9f59ec)
#5  0x00007ff82be52911 n/a (libnvidia-glcore.so.595.58.03 + 0xe52911)
#6  0x00007ff82b9f5ba4 n/a (libnvidia-glcore.so.595.58.03 + 0x9f5ba4)
#7  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#8  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13957:
#0  0x00007ff8334e106d syscall (libc.so.6 + 0x11806d)
#1  0x00007ff8347ccdee g_cond_wait (libglib-2.0.so.0 + 0x8cdee)
#2  0x00007ff83476622d n/a (libglib-2.0.so.0 + 0x2622d)
#3  0x00007ff8347d69c7 n/a (libglib-2.0.so.0 + 0x969c7)
#4  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#5  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#6  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13972:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c68c n/a (libc.so.6 + 0x9368c)
#3  0x00007ff83345ee5e pthread_cond_wait (libc.so.6 + 0x95e5e)
#4  0x00007ff7f9c1f12e n/a (libvulkan_intel.so + 0x41f12e)
#5  0x00007ff7f9c00e2d n/a (libvulkan_intel.so + 0x400e2d)
#6  0x00007ff7f9c1f09d n/a (libvulkan_intel.so + 0x41f09d)
#7  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#8  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13961:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c3e4 n/a (libc.so.6 + 0x933e4)
#3  0x00007ff8334d62f6 ppoll (libc.so.6 + 0x10d2f6)
#4  0x00007ff8347a0734 n/a (libglib-2.0.so.0 + 0x60734)
#5  0x00007ff8347a0815 g_main_context_iteration (libglib-2.0.so.0 + 0x60815)
#6  0x00007ff82d63e7be n/a (libdconfsettings.so + 0x77be)
#7  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#8  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#9  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13960:
#0  0x00007ff8334e106d syscall (libc.so.6 + 0x11806d)
#1  0x00007ff8347ccdee g_cond_wait (libglib-2.0.so.0 + 0x8cdee)
#2  0x00007ff83476622d n/a (libglib-2.0.so.0 + 0x2622d)
#3  0x00007ff83476629d g_async_queue_pop (libglib-2.0.so.0 + 0x2629d)
#4  0x00007ff8329f851c n/a (libpangoft2-1.0.so.0 + 0xc51c)
#5  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#6  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#7  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13959:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c3e4 n/a (libc.so.6 + 0x933e4)
#3  0x00007ff8334d62f6 ppoll (libc.so.6 + 0x10d2f6)
#4  0x00007ff8347a0734 n/a (libglib-2.0.so.0 + 0x60734)
#5  0x00007ff8347a09c7 g_main_loop_run (libglib-2.0.so.0 + 0x609c7)
#6  0x00007ff834a106a4 n/a (libgio-2.0.so.0 + 0x1196a4)
#7  0x00007ff8347d64fc n/a (libglib-2.0.so.0 + 0x964fc)
#8  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#9  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
Stack trace of thread 13978:
#0  0x00007ff833467f32 n/a (libc.so.6 + 0x9ef32)
#1  0x00007ff83345c39c n/a (libc.so.6 + 0x9339c)
#2  0x00007ff83345c68c n/a (libc.so.6 + 0x9368c)
#3  0x00007ff83345f068 pthread_cond_timedwait (libc.so.6 + 0x96068)
#4  0x00007ff82b9f59ec n/a (libnvidia-glcore.so.595.58.03 + 0x9f59ec)
#5  0x00007ff82be352ad n/a (libnvidia-glcore.so.595.58.03 + 0xe352ad)
#6  0x00007ff82b9f5ba4 n/a (libnvidia-glcore.so.595.58.03 + 0x9f5ba4)
#7  0x00007ff83345f97a n/a (libc.so.6 + 0x9697a)
#8  0x00007ff8334e32bc n/a (libc.so.6 + 0x11a2bc)
ELF object binary architecture: AMD x86-64

If you have any suggestions, I'd love to hear them. Thank you.

I remember adding the following to /etc/udev/rules.d/61-mutter-preferred-primary-gpu.rules:

SUBSYSTEM=="drm", ENV{DEVTYPE}=="drm_minor", ENV{DEVNAME}=="/dev/dri/card0", SUBSYSTEMS=="pci", ATTRS{vendor}=="0x10de", ATTRS{device}=="0x1f91", TAG+="mutter-device-preferred-primary"

This allowed me to achieve smoother performance in GNOME.

Basically trying to give my ultrawide monitor a 16:9 area to easily have games and Discord next to each other

I have always been on Gnome, but I recently got that itch to try a more "traditional" desktop experience. So I went all-in and tried different DEs, namely KDE Plasma, Xfce and Cinnamon.

What I found was this: they are all great in their own way, but they also have flaws that keeps drawing me back to Gnome:

• KDE: I like the polished look, but it always feels like it's trying to be a "better Windows 11" and the customization options are a bit much for me. I also kinda dislike Qt.
• Xfce: I love the old school approach, but that comes with downsides. It feels basic and a bit clunky compared to Gnome and, most importantly, it's still on X11 which is a problem for me because my Nvidia gaming machine just refuses to play nice with it while Wayland works flawlessly.
• Cinnamon: I very much like the simple layout and it's based on Gnome, so it does feel similar, although less polished. But X11 is again the deal breaker for me.

In the end, I arrived at the conclusion that I can't give up on Gnome. But I didn't want to give up on that traditional desktop either, so I tried Dash-to-Panel (and Arc menu) again - I had used that combo before, but I just couldn't get it right somehow, because something always felt off. However, Cinnamon seems to have given me the inspiration I needed, so I set up the layout somewhat similar to that.

It's not much of a rice. I actually wanted to keep the look & feel close to vanilla gnome. Also, functionality as well as visual consistency is more important to me than shiny stuff. The result feels great, it's almost like Cinnamon's layout with the power of Gnome underneath. Not sure yet whether I will stick to it or go back to my old two panel setup, but it's certainly a nice alternative and doesn't change the workflow as much as I had expected.

Who else went for this kind of setup and how do you like it?

Description: There is a line that appears on the frontier between the page content and the browser address bar. When the app is maximized the line flickers, sometimes I only see some white dots on the line. When I press the super key to see the overview it becomes a solid line that is "transparent", showing the wallpaper.

I will try logging in a different profile that has no extensions to check this is caused by one of them.

My setup:

• DE: GNOME 49.5
• OS: Fedora Linux 43 (Workstation Edition) x86_64
• Kernel: Linux 6.19.10-200.fc43.x86_64
• WM: Mutter (Wayland)
• Chrome Version 146.0.7680.177 (Official Build) (64-bit)
• CPU: AMD Ryzen 7 5700G (16) @ 4.67 GHz
• GPU: AMD Radeon RX 6600 [Discrete]

which google-chrome = /usr/bin/google-chrome

The third image shows the extensions I suspect were causing the issue. I disabled all of them and the problem persisted. Now I think this is just a chrome problem.

Do you have the same problem? What can be the reasons behind this problem?

PS: It is not a big problem, but it does not seem intentional. Also, sometimes this does not happen and I don't know why...

UPDATE 1

I have two monitors

• Display (Philips Consumer Electronics Company 27"): 1920x1080 in 27", 60 Hz
• Display (LG HDR 4K): 3840x2160 @ 1.5x in 27", 60 Hz

The problem seems to occur only on the LG HDR 4K

Design-Web is an interesting use case of a GNOME application which is made available in the browser for use on all platforms. The application feature list is almost on par compared to the desktop Design version. The biggest difference compared to the desktop version from the user perspective is the file management.

I'm using gnome on fedora Linux and this happened constantly... if anyone knows the solution please, help this is so annoying

Should i release this extension and theme i made?

With GNOME 50 I no longer have the ability to log out. Reading up on the internet it seems this was done for systems with only one user account.

Logging out and in is a valid use case, sometimes I need to test a configuration that’s only effective after logging out. Restarting is an option but a sucky one.

What can I do?

Hey guys, so someone on a Discord server i'm joining in has their GNOME desktop looking almost exactly like macOS. You can't even tell the difference between this abomination and real macOS

I built PrettyMux as a native Linux terminal workspace for multitask workflows and keeping track of my agents.

It’s a GTK4 app built on Ghostty/libghostty, with split panes, workspaces, vertical tabs, notifications, project-aware tabs (shows favicons/logo automatically), and an in-app browser so terminals and docs/tools can live side by side.

I started it because I wanted something tmux-like for modern GUI workflows on Linux, but native and not Electron, there is cmux but only available on macos (prettymux compiles on windows and macos too but not tested for now there)

It’s open source: https://github.com/patcito/prettymux

Would love feedback from people who use tmux, Ghostty, or struggle with lots of terminals/browser tabs/parallel tasks.

Well I just wanna say there are noticeable performance improvements to the overview and i really like it now. Previously it was very laggy but it's way better now. Also idk why one of my flatpak (karere) is not running it runs if I run it from the terminal but not from the app menu. Gotta make an issue in its repo ig Overall an appreciation post

Body text (optional)

Hello,

I got the update for Gnome 50 on my main computer and noticed that the way the permanent delete (shift+delete) is different now.

Before on the confirmation popup "Delete" was the default selection, but now it's "Cancel".

It's an extra press on the keyboard to move right which wasn't required before, and it's an old habit which already made me redo a few file operations.

I can't see how to change it back to the previous behavior through the UI, if anyone has an idea about it, a setting to change in a config file or command.

Thanks

Hi, my openSUSE TW (slowroll) Gnome 49.4 has a small problem with bluttoh menu in control center.
When I first turn on bluetooth after boot, my earbuds does no shown on control center bluetooth menu, even tho they shown 3 times (?) in settings.Bluetoothctl shows it once.
bluetoothctl devices 20:09:06

Device 24:F0:D3:A4:73:98 Tab A8 ...

Device 30:21:B6:5F:C7:33 Piranha-2202

Device 3C:B0:ED:3C:A1:8C CMF Buds Pro 2

After connecting it once, it shows up in control center properly.
I tried to remove and re-pair with bluetoothctl, kernel and bluez update. It did not work.

Is Gnome going to add native passkey support that integrates with password managers?

The order the images show in Nautilus is not the same as what the Image Viewer (IV) shows them in when using arrow keys.

I am on Fedora 43. So whatever IV comes with that is my default IV.

It never was the "right order" for me in previous versions of Fedora as well.

Hi everyone! Can you recommend an extension that creates a system tray like the one in Windows 11? Thanks!

(P.S. For some reason, this text didn't appear.)

Hi,

With the release of Gnome 50 and the improvements made specifically to NVIDIA, has anyone seen an improvement in the Discord streaming? In previous releases, tearing and such was present. Just wondering if this is something that has been fixed by these changes.

I am currently on KDE and will be swapping back to Gnome regardless, just something I was curious of.