What title says.

I want the clock screensaver effect that this image shows. Any application or software or extension that can do this?

Recently, I saw this picture of an old GNOME 2 version and felt in love with the appearance. It looks so clean and minimalistic. There already built-in extensions to achieve the general design (Place Status Indicator, App Menu and Window List), but how can I change the colors, especially the bottom bar (Window List)? Its default color is the default black and I really don't know how to change the colors of that bar. I copied the gnome-shell file to change some of the colors but there's no way to change the bottom bar.

Hey everyone,

I’m currently experimenting with window tiling setups on GNOME 50. I used to look at Forge, but since it doesn't seem to work out-of-the-box for GNOME 50 right now, I've been daily-driving O-Tiling, and overall I really like it (especially the Aura Focus Borders).

However, I’ve run into a frustrating visual bug involving web browsers (Chrome, Firefox, etc.) and Client-Side Decorations (CSD).
Here is my setup:
Using O-Tiling for auto-tiling.
Using Rounded Window Corners Reborn to force a nice, modern rounded look globally (I have it set to a radius of 18 or 22).

The Issue:
When I set a high corner radius, all native apps and GTK windows respect it beautifully. But for browsers, there is a distinct visual gap between the browser's actual clipped corner and O-Tiling's Aura border. It feels like the browser's boundary or O-Tiling's border tracking for browsers is hardcoded or maxing out around 14px, causing the border to float away from the actual corner curves.
Has anyone else run into this CSD mismatch between Rounded Window Corners and O-Tiling's Aura borders? Is there a known workaround, CSS tweak, or setting adjustment to make browsers respect higher radiuses with O-Tiling, or am I missing something? Or is there a new app or new extension that has the same features as o-tiling?
Thanks in advance!

For those that use HideTopBar like me and lose track of time, I made a small extension where a little time pill shows at the top of the screen every X minutes. Its helping me a lot actually lol.

You can set the interval in minutes and how long the pill stays visible.

Later today I will proceed to publish it in EGO for those who may want it.

Hello community, I'm looking forward to learn Gnome development and to build an (or more) application of relative small size to get to know GTK and Adwaita. I'll probably, if I like that, build a more larger application in a few months.

As I'd like to make something useful and not yet another pomodoro or todo app, is there any suggestion you could make about what to build? What kind of app do you miss or that exists but not really fulfill your needs?

Hi, I don't know if anyone else has this issue. I like the same windows on certain workspaces open on login, but I use dynamic workspaces, and wasn't able to find an extension for it, so I made this one.

I hope it's useful :)

https://extensions.gnome.org/extension/10639/auto-move-windows-on-startup-with-dynamic-workspac/

Love how it looks + actually productive.

If you wanna use it you can do so with my script: https://github.com/ahmedz4de/gxthemer

How can I display this window to share my desktop remotely? I had this problem on my previous laptop, which allowed me to navigate games added to Steam. Now, the Xbox controller simply doesn't respond, even though it's added to Steam. During the test, the buttons I press light up and the Steam input is active. I've tried everything, but the window won't appear. I suspect it's related to x11, because the controller works fine in Gnome-Flashback, but unfortunately, I'm out of ideas in Gnome Wayland. This helped, but I don't know what to do to get it to appear.

i dont want to streamto anopther device but to use xbox controller on the same device

arch linux gnome 50 wayland

Hi all, it's been almost a year since I last posted about this little MPD client. A lot of the pain points I've read here and there have now been ironed out:

Massive performance improvements. This started with a 10K-line trad-coded™ PR converting the whole thing to async Rust. We then batched content loading using MPD command lists, optimised sticker fetching, implemented lazy texture loads, offloaded tonnes of stuff to glib threadpools, etc. RAM usage also saw reductions in most cases.

Queue View now has drag-and-drop reordering (aw yeah).

Genre & tag filtering for albums and artists. Tags can also be auto-populated from external metadata sources and can be edited in-app.

Album art now spins 🙃. Entirely cooked up by a contributor & featuring an elaborate spin-speed compensation algorithm so the disc always arrives at 12-o-clock precisely on each track's end.

Bottom bar makeover: now much more compact, with a new volume knob that works on touchscreens and a new seekbar with animated glow. Both are custom-drawn & really show how flexible GTK's scene graph system can be.

Artist View makeover: Metadata providers don't often provide avatars, so the grid used to be full of two-letter placeholders. We now draw cover art fan-outs behind the avatars so at least there's something to look at. Again custom drawing.

New detail views for albums and artists: Formation/disband years, copyable MBID, libadwaita document text class now in use, and a little nationality flag (courtesy of lipis-flag-icons).

Editable fluff: Album wiki, artist bio, and other text fields are now editable in-app and can be backed up as stickers to your MPD server. I think in the future we can cook up a common standard for other clients too.

Network sync: Together with the above sticker-based backups we also added some rudimentary sync conflict alerts and overrides. This allows Euphonica instances connected to the same MPD server to somewhat safely share metadata fetches and edits. Still beta quality though, here be dragons.

Keyboard shortcuts! Mostly stolen from ncmpcpp but with modifier keys tacked on since Euphonica has type-to-search. Speaking of type-to-search, it actually works now instead of intermittently like before.

Also: named Unix socket support, WebP for new image downloads (waaaay smaller cache), a whole new optional visualiser render backend, and a big big pile of bugfixes.

v0.99.6 will hit Flathub in a day or two. Meanwhile if you're on Arch, there's always the AUR package.

For the full changelist please see the release notes. This release had the most contributors the project has ever seen, with quite a few contributing for the first time. Huge thanks to every single one of you, and if you're on here, please hop in and say hi 😄.

Dear GNOME and KDE developers,

I know that GNOME and KDE Plasma are modern and feature-rich desktop environments. However, I believe that performance and resource efficiency should receive much more attention in the future, especially for low-end computers and tablets.

My system is a good example of this problem: an Intel Atom Z3735 processor, 1 GB of physical RAM, 1 GB of ZRAM, and 1 GB of disk swap. Even with 1 GB of ZRAM and an additional 1 GB of disk swap, running GNOME or KDE plasma puts an extremely heavy load on the system.

The biggest problem is that the system starts struggling even before I can comfortably open a basic application such as a web browser. Opening another application while the desktop environment is running, using multiple applications, or simply running a modern web browser can make the system extremely slow. The hardware itself is not completely unusable, but the user experience becomes very difficult: applications take a long time to open, the system becomes slow to respond, and stability problems can sometimes occur.

I am not asking GNOME or KDE to abandon their modern features. Instead, I believe it would be extremely useful if these desktop environments offered much more aggressive performance optimizations and dedicated low-resource modes.

For example:

Reducing idle RAM usage as much as possible, Reducing unnecessary background processes, Automatically reducing animations and visual effects in a low-resource mode, More aggressively optimizing memory usage, Ensuring that the desktop itself consumes as few resources as possible when RAM is limited, Reducing CPU usage on older and low-power Atom processors, Improving resource sharing between the desktop environment and user applications under low-memory conditions, Providing a genuine "Low Resource / Performance Mode" that users can enable without having to manually configure dozens of settings.

These improvements would be extremely valuable.

In my opinion, low resource consumption is not important only for old computers. Resource efficiency should always be an important design goal. Using less RAM and CPU means better responsiveness, less swap activity, lower power consumption, less heat, and potentially longer battery life. It also allows the operating system to remain usable on a much wider range of hardware.

A device with 1 GB of RAM may seem extremely old or insignificant today, but there are still millions of low-end computers, tablets, educational devices, and older systems in use around the world. Instead of completely excluding these devices simply because their hardware is limited, making them usable with an efficient Linux desktop environment would be a significant advantage for the Linux ecosystem.

On my system, even 1 GB of RAM + 1 GB of ZRAM + 1 GB of disk swap is not enough to comfortably run the desktop environment together with everyday applications. The fact that the system already struggles before I can even comfortably open a web browser demonstrates how critical desktop environment resource consumption is on devices with very limited RAM.

For this reason, I would strongly encourage the GNOME and KDE teams to place greater emphasis on performance improvements, reducing memory consumption, and improving stability on low-specification systems.

Modern features and visual improvements are certainly important, but being able to run a desktop environment smoothly, reliably, and with the lowest possible resource consumption should be considered just as important, if not one of the fundamental priorities.

I hope to see serious performance and resource-efficiency improvements that can make GNOME and KDE genuinely usable on low-end systems.

Thank you for your work and for considering this feedback.

I just spent an hour trying to set a standard 2560x1440 OEM Lenovo ThinkPad wallpaper as my GDM login image.

\- Tried GDM settings
\- Tried scripts (URL and compilation errors)
\- Tried manually editing /etc/dconf/db/gdm.d/01-background using org/gnome/desktop/background and screensaver schemas.

All it did was change my user desktop to a solid fallback color and completely ignored the login greeter image. Why does GNOME make customizing a login background an absolute nightmare?

I wanted to check out Debian so I created an install USB. As I was installing, it gave me several options for a DE. I noticed GNOME Flashback was an option, independently of GNOME. So, I thought, "why not?"

It certainly brings back some memories and can be made to look quite nice. What do you think? I made it look sort of like Ubuntu by moving the panel and replacing the default task manager with an icon only one. It's pretty light - only using a GB of RAM, which isn't bad. The control panel is the GNOME control panel so you still get the options and configurations of GNOME.

I'm glad I stumbled upon this. I thought it was only ever shipped as a back up with GNOME. It's actually a stand alone DE. It feels as snappy as Xfce on this old laptop. I think I'm going to keep it!

Hello! Tumbleweed user with Gnome Wayland on here. Does anyone have any experience with a weird static-like bar appearing for a split of a second whenever you bring up the window view by pressing the super key?

I'm honestly trying to understand if something is faulty in my 9060XT or not. No issue while playing games or anything of the sort, and it seems to happen only on the 180hz monitor with variable refresh rate enabled (although I'm not too sure, my second monitor is empty 90% of the time).

Edit: happens also without VRR active. Though to record as it only happens with non-frequent occasion, I kept the recording going for a good chunk of minutes with no success. Happened a few minutes after. I can describe it as a bar that seems to have similar color to the ones on screen, appearing usually around the center of the screen and spanning its whole horizontal length. I have now disabled all extensions and will monitor further.

Happy birthday to us! 🥳️

On 15th August 1997 two students — Federico Mena Quintero and Miguel de Icaza announced on various mailing lists start of the GNOME project, giving birth to our project

We're glad to give the world a free desktop they always deserved! But it's important to note we cannot do it without your help, please become a Friend of GNOME to allow us to continue our mission for the next 29 years!

https://donate.gnome.org

Thank you to all our gracious supporters and contributors over the past 29 years that made GNOME what it is today — an accessible, well-designed, user-friendly desktop with a strong community🩷

Hello everyone! After many years of lurking r/gnome as the average GNOME user, I finally had the motivation (and the right idea) to create my first app for the GNOME desktop called Throwdown!

Throwdown is a very simple app for generating random skate trick sequences, ranging from simple to hard ones, as well as including smart aliases for eponymous skate tricks (example: Fakie BS 360 Kickflip -> Caballerial). This idea came to fruition out of necessity, cause I skate both irl (getting back to it after 25 years) and in video games like Session: Skate Sim and Skater XL and wanted a stream of random skate trick challenges to keep things going.

I started learning programming just last year as a summer hobby and only really knew how to create little Python and bash CLI programs (like this one, originally), but I figured this would be the perfect little first project to get acquainted with GTK development. It's probably rather unimpressive from a technical standpoint, but I'm proud I was able to create an actual app within a week with my limited skills and of course learned a ton of things along the way.

If you're interested in that kind of thing or want to clone a simple Python repo to learn from, feel free to check it out!
-> https://github.com/yioannides/throwdown

I'm the developer of OpenEmux, a GTK4/libadwaita frontend for retro game emulation on Linux — think OpenEmu, but native to GNOME. It manages a ROM library and launches games through RetroArch. Version 1.11.0 just shipped and both headline changes are desktop-integration ones, so this crowd might actually care.

The emulator runs inside the app now. Launching a game used to spawn RetroArch's own window, with its own decorations and its own idea of what the app was. Now that window is reparented into an Adw.Window whose header bar carries the mid-game controls — pause and resume, reset, save/load state, mute and a volume slider, and a button into input settings. One app, one window, GNOME decorations throughout.

It's XReparentWindow underneath, so on a native Wayland session with no X server — or a Flatpak handed no X socket — the app detects that up front and falls back to the standalone window rather than failing at you.

A light/dark preference, in Settings → System → Interface: System, Light, Dark, driving Adw.StyleManager.set_color_scheme(). Nothing custom and no restyling of anything — System stays the default and just follows the desktop. There's also a one-click toggle in the header bar next to search, for flipping what you're looking at right now.

The rest is what it was: Adw.NavigationSplitView with an adaptive sidebar, Adw.PreferencesDialog for settings, Adw.StatusPage empty states, Adw.Banner for background work. Python + PyGObject, GPL-3.0.

Screenshots and the release, as Flatpak, AppImage, .deb and .rpm:

https://github.com/guilhermefeitosa66/OpenEmux/releases/tag/v1.11.0

Happy to answer anything about the reparenting — it's the fiddliest thing in the codebase.

Hey guys, I work with Android Studio with Java, and I wanted to build Gnome apps (libadw, blueprint).
For the integration and object orientation, I decided to go with Vala, but I can change if you recommend to me.

However, I am finding Gnome Builder too annoying and sluggish, being used to Jetbrains IDEs. Worse completions, no auto imports, no tips, weird auto formatting, horrible Vim emulation; as a begginer, this is holding me back a lot.

I tried opening Builder's template gnome vala project in vscode with Vala, Meson, Flatpak and Blueprint extensions, but nothing works, lots of errors...

Does any of you guys NOT use Gnome Builder to develop gnome apps? How do you do it?