@nekohayo@mastodon.social
@nekohayo@mastodon.social avatar

nekohayo

@nekohayo@mastodon.social

Free & #OpenSource software contributor (#Linux + #GNOME + #GStreamer) since 2004. Currently co-maintaining the most magical desktop productivity apps combo you can find (https://fosstodon.org/@GettingThingsGNOME & GNOME Calendar), as their benevolent lean engineering manager + occasional User Interaction & UX designer.

Waging war on mediocrity & unsustainability in business.
Founder of https://mastodon.social/@ideemarque + https://mastodon.social/@atypica, and mercenary CMO https://mastodon.social/@regento.

Ex-Collabora, ex-psy, ex-Shinra.
I don't roleplay but I wear a cloak. ❄️

This profile is from a federated server and may be incomplete. Browse more on the original instance.

AxelTerizaki, to linux French
@AxelTerizaki@shelter.moe avatar

Je comprends pas comment quelqu'un a pu valider le fait que sous Linux avec wireplumber, les sorties audio se mettent en veille.

Du coup chaque fois qu'une notif doit arriver via une app, on entend même pas ou à peine la notif parce que le temps que l'audio se réactive et que le volume remonte (il commence à 0) ben on a loupé la notif.

Je sais, pas ça me sidère. C'est vraiment abhérrant comme comportement d'UX. Je croyais que c'était propre à Arch (je l'avais corrigé à l'époque de l'install) mais visiblement sur d'autres distros pareil.

nekohayo,
@nekohayo@mastodon.social avatar

@gnomelibre @AxelTerizaki Heu j'ai jamais eu le problème avec mes diverses cartes son en tout cas (intégrées, PCI, USB), ça sonne comme un problème de pilote, spécifique à un modèle particulier? Tout est instantané chez moi, je reçois chaque son, et si y'a une suspension du matériel entre les deux eh bien elle est de toute évidence imperceptible dans mon cas.

nekohayo,
@nekohayo@mastodon.social avatar

@AxelTerizaki @gnomelibre Si ça se constate juste sur sortie son HDMI vers TV, ça explique pourquoi je n'ai jamais rencontré le bug, et ça sonne juste comme un rapport de bug à trouver/ouvrir sur le fait que ça ne devrait pas faire ça pour les sorties son HDMI.

Parce que sinon, si les autres périphériques n'ont pas de tel délai, ben je peux dire que j'apprécie fortement le fait que mon ThinkPad usagé avec une batterie sur deux peut tenir une autonomie de 16 à 25 heures sous Fedora, par défaut.

nekohayo,
@nekohayo@mastodon.social avatar

@AxelTerizaki @gnomelibre Ça sent suspicieusement comme un bug, parce que mes glissières de volume (sous GNOME Shell, GNOME Settings, et pavucontrol) ne bougent absolument pas par elles-mêmes « Lorsqu'il y a / n'a pas de sons qui jouent », sur aucun de mes ordinateurs. Les seuls cas où ça peut bouger c'est si un logiciel de visioconf WebRTC décide de troller avec mon micro, mais y touchent pas aux sorties.

m_j, to GNOME French
@m_j@piaille.fr avatar

est-il toujours le programme GUI par défaut recommandé par (présent dans ) ?

https://wiki.gnome.org/Apps/OCRFeeder

nekohayo,
@nekohayo@mastodon.social avatar

@m_j De nos jours je dirais que ce serait probablement plutôt https://www.openpaper.work/fr/ mais je ne l'ai pas essayé plus que quelques minutes par curiosité, j'ai du mal à me départir de l'idée de tout gérer dans mon système de fichiers.

AxelTerizaki, to linux French
@AxelTerizaki@shelter.moe avatar

Je redonne sa chance à Fedora (40) et bon, là je sais pas trop comment m'en tirer mais j'ai les boites de dialogue d'ouverture de fichier qui sont toutes blanches sur les appimages. Genre, ça affiche rien, que du blanc.

C'est cool mais des fois, c'est quand même chiant de devoir sans cesse chercher pourquoi un truc marche pas.

nekohayo,
@nekohayo@mastodon.social avatar

@AxelTerizaki La raison pourquoi j'upgrade pas à Fedora 40 (et n'utilise pas Arch, BTW) c'est justement parce que je sais que GTK 4.14 a changé complètement son moteur de rendu par NGL, et je laisse les usagers d'Arch servir de cochons d'inde. Je prévois mettre à jour mon OS seulement vers la fin de l'année.

C.f.:

Spécialement si tu roules encore du nVidia… j'dirais neuf neuf neuf neuf!

nekohayo,
@nekohayo@mastodon.social avatar

@AxelTerizaki Teste c't'astuce là sous Fedora, au cas où: https://bbs.archlinux.org/viewtopic.php?id=294168

nekohayo, to accessibility
@nekohayo@mastodon.social avatar

As GitLab 17.0 is coming next week, it looks like my very polite reminder nudge might have encouraged the maintainers to request reviews from specific people for the automatic ("system") light/dark theme mode implementation, hopefully this lands in time for 17.0 🤞 so that we don't have to wait another full year to enjoy this and improvement, even if somehow considered experimental: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/150254#note_1895251010

nekohayo, (edited ) to GNOME
@nekohayo@mastodon.social avatar

I have a huge amount of appreciation for the fact that Nautilus / can seamlessly pattern-select, batch-rename and move files both from its treeview and from search results… all with keyboard shortcuts! Extremely useful to clean up filenames.

Today, in someone else's messy folders, I was able to cleanly rename everything and eliminate at least 40 duplicates in a directory that contained over 180 files, most of which were in the wrong locations.

nekohayo,
@nekohayo@mastodon.social avatar

@antoniof With its self-documenting label I personally find it pretty straightforward to use, though I could imagine these improvements:

  • Showing an item for it in the folder pathbar's meatballs menu, for discoverability (instead of only the "Ctrl+S" keyboard shortcut)?
  • Maybe using some color or bold type on the * and ?? / ??? characters in the example label?
  • Wild idea: a realtime preview or indication of how many files the user's pattern would match? A bit like the batch renaming dialog?
nekohayo,
@nekohayo@mastodon.social avatar

@a_lex_ander Ah no, today I mostly used the filtering search and its realtime updating results when you move or rename items, along with batch renaming, previewing & comparing with Sushi, and batch deleting redundant contents I flicked through with that tool; pattern selection is useful in other situations, on occasion…

A dupe detector or integration with @YaLTeR's "Identity" app would be rad, but most files were PDFs…

eugenialoli, to debian
@eugenialoli@mastodon.social avatar

On 11, the whole system along with was taking 500 MB of RAM. On Debian 12, the system takes 850 MB of RAM. On Trixie/Sid-unstable, it takes 1.3 GB. I honestly don't know what they're shoving in it.

With and , it takes 1.6 GB on idle. Since when Cinnamon, a gnome2/gtk3 fork takes (or should take) as much RAM as Gnome4/gtk4? Something's amiss.

nekohayo,
@nekohayo@mastodon.social avatar

@eugenialoli With kernel caching etc. (i.e. "unused RAM is wasted RAM"), is it still meaningful to compare total RAM usage across DEs, vs analyzing individual RAM usage of components/applications to look for a more specific anomaly?

But even then, my observation in the past few years is that the more RAM you have available in a system, the more it tends to use it anyway.

tbernard, to random
@tbernard@mastodon.social avatar

Damn, Mahjongg looks pretty slick nowadays 👀

Latest visual changes aren't released yet, but you can get the last release from Flathub: https://flathub.org/apps/org.gnome.Mahjongg

nekohayo,
@nekohayo@mastodon.social avatar

@tbernard Could we polish it up to this level eventually? 👇
The 3D graphics and ambient sound track on this version are really realistic 😜 https://youtu.be/qzcmCvOM2KY?t=4

tamas, to GNOME
@tamas@hachyderm.io avatar

The performance improvement in the Files app is fantastic (particularly, opening a directory with many entries is almost instant now). Thanks to whoever fixed that 🙏

nekohayo,
@nekohayo@mastodon.social avatar

@sonny @antoniof @tamas @gnomelibre
And yet, there's still a lot of room for potential performance improvements in future Nautilus versions. For large directories, these come to my mind:

For searching, these come to my mind:

eugenialoli, to debian
@eugenialoli@mastodon.social avatar

So I found myself in a weird predicament. I had some older laptops that I converted to & with a bunch of added apps and games. I gave some to my family, and the rest I wanted to give them to kids for school. I asked around. Well, no one seems to want them. No one is using computers anymore in it seems, they only use . They barely browse the web too (just some gov sites). They just use and few apps, consoles for games. That's it.

nekohayo,
@nekohayo@mastodon.social avatar

@eugenialoli This problem has been around for over ten years now, and it's not getting any better: http://coding2learn.org/blog/2013/07/29/kids-cant-use-computers/

sam, to GNOME
@sam@social.coop avatar

Every now and then I think I should go back to using because it would be simpler than my own weird mix of Mate and i3 and look a lot nicer, and then I try one of their apps… I just tried out their official Markdown editor and it starts running noticeably slowly (menus don't respond, the rendering preview gets locked up, etc.). This is on a very fast laptop and this is just a text editor. This matches my previous experiences running gnome years ago. Maybe I'll go with something else…

nekohayo, (edited )
@nekohayo@mastodon.social avatar

@sam @gnomelibre Gimme a sample Markdown file and clear instructions on how to reproduce the issue and I will performance-profile it as a public service, if you can't.

nekohayo,
@nekohayo@mastodon.social avatar

@sam @gnomelibre I'm running 15-years-old hardware and I made the latest versions of GNOME Shell + apps fast on it over the past year of profiling and reporting.

You'll need to be MUCH more specific than your description above. Provide a way to instantly test your exact data and context (distro, software versions, packaging format, graphics driver, graphics server…). The basics of https://handbook.gnome.org/issues/reporting.html

No guarantees, as Sysprof doesn't do Python yet; manually profiling Python would be a pain

nekohayo,
@nekohayo@mastodon.social avatar

@sam OK, so Intel GPU, not nVidia?… you're running on Xorg though, that'll slow you down a bit.

I see GTK 4.14.3 in your list of packages with Apostrophe 3.0. I'd bet the problem is that this version of GTK is running its new "NGL" renderer. It's the sole reason I haven't upgraded to Fedora 39 / GNOME 46, as I'm too scared of the glitches and perf regressions, with the amount of issues with that "gpu renderer" tag mentioned in https://gitlab.gnome.org/GNOME/gtk/-/issues/6411

Try this trick: https://bbs.archlinux.org/viewtopic.php?id=294168

nekohayo,
@nekohayo@mastodon.social avatar

@sam Which animations where? And you are running Intel graphics (or at least open source AMD graphics), not nVidia, right?

Worst case scenario, you can disable most animations globally with GNOME Control Center's "Reduce Animations" accessibility setting, but animations "shouldn't" be slow if the graphics stack is in order.

nekohayo,
@nekohayo@mastodon.social avatar

@sam Also use https://developer.gnome.org/documentation/tools/inspector.html to check the global properties of the app's graphics stack, and see if you see any mention of "LLVMpipe" in there. If so, that would mean the app/GTK is somehow running in software rendering mode, without any GPU assistance, everything on the CPU, and that's terribly slow. Also watch out if it's running Vulkan (instead of GL) on a GPU that is not actually Vulkan…

nekohayo,
@nekohayo@mastodon.social avatar

@sam I'm kind of out of ideas there, as it sounds like you're running non-broken Intel graphics, which is the best scenario… yet it seems like something is still wrong somewhere in Mesa/GTK, somewhere in middleware. It might fix itself with updates eventually.

At least the Inspector might help you troubleshoot further with fellow Arch users; or it might be that everyone with the latest versions is in trouble, AFAICS in https://gitlab.gnome.org/GNOME/gtk/-/issues?label_name=gpu+renderer

You somehow make me even more scared to upgrade! 👀

thomholwerda, to random
@thomholwerda@exquisite.social avatar

At least my choice to ditch GNOME for KDE turns out, once again, to be the right choice.

nekohayo,
@nekohayo@mastodon.social avatar

@dusthillperson @thomholwerda @frumble To claim that we GNOME developers "hate" our users is pretty damned wild.

nekohayo, to UX
@nekohayo@mastodon.social avatar

Filed this little issue in the VNC/RDP/SSH application, but it can apply to other software applications in general:
If your app depends on strict input of hostnames/usernames/passwords and does not check for invisible whitespaces prefixing/trailing the value in a field, eventually an idiot like me will spend weeks troubleshooting an issue resulting from having pasted something from a spreadsheet/website and being unable to see the invisible character: https://gitlab.com/Remmina/Remmina/-/issues/3106

nekohayo, to firefox
@nekohayo@mastodon.social avatar

It turns out that GitLab's homebrew PDF files previewer is so wildly inefficient that it is an excellent performance torture test for any browser engine, not just WebKitGTK but also .

I have reported an issue here in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1893884

…but I have been unable to capture a performance profile so far. If anyone manages to do so, that could be quite helpful to add to the report!

nekohayo, to random
@nekohayo@mastodon.social avatar

Found an interesting Calc scrolling performance bug report in Bugzilla some days ago, that was reported to be more visible with HiDPI screens, so tonight I grabbed a 4K laptop with Wayland and ran to try to capture at least partial performance profile information on this issue: https://bugs.documentfoundation.org/show_bug.cgi?id=154602#c16

gnomelibre, to GNOME
@gnomelibre@mamot.fr avatar

Today, I had to fill in a form to send to my insurer. I opened it with Document Viewer and filled in the various fields without any problem 🙂

Unfortunately, at the end of the document, we have to write our name and sign, but the application doesn't offer any options for adding text and inserting an image 😬

nekohayo,
@nekohayo@mastodon.social avatar

@m_j @gnomelibre The issue is here for anyone who might have the skills to implement it; patches would be incredibly welcome: https://gitlab.gnome.org/GNOME/Incubator/papers/-/issues/60

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • megavids
  • tacticalgear
  • magazineikmin
  • thenastyranch
  • Youngstown
  • mdbf
  • rosin
  • slotface
  • InstantRegret
  • khanakhh
  • Durango
  • kavyap
  • osvaldo12
  • DreamBathrooms
  • JUstTest
  • GTA5RPClips
  • ngwrru68w68
  • everett
  • tester
  • ethstaker
  • cisconetworking
  • cubers
  • modclub
  • provamag3
  • anitta
  • normalnudes
  • Leos
  • lostlight
  • All magazines
    •