Jeff Fortin commented on issue #1658 at GNOME / gnome-calendar
I wondered if this could be due to gtk#6465, but those failed assertions don't really sound like it at first glance...
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
I wondered if this could be due to gtk#6465, but those failed assertions don't really sound like it at first glance...
One of the commit messages has a typo, "dipsose" ;) Clearly you meant dip sauce 😋️
There is a typo in this MR's title and your commit message: "finisgh" 😉️ Also, the commit message only links to one of the two bugs?
This seems a bit like the opposite problem to #724: on my ThinkPad T480 with Intel Kabylake chipset (Core™ i5-8350U CPU + Intel UHD Graphics 620 "KBL GT2" GPU), whether with the nightly flatpak version or the latest stable version from Flathub, running on Fedora 44 Workstation, there is little to no information shown for my Intel integrated GPU: Video Memory Usage is always reported as "0 B" Video Memory Frequency is "N/A" Power Usage is "N/A" etc.
I tend to agree with Khalid's use here, personally I see that label mostly as a "new contributors attraction vector" through reasonably-easy-to-fix actionable papercuts that facilitates them dipping their toes into the project. That doesn't forbid experimented contributors from just fixing it themselves if they want to, though :)
Just in case this is useful as an additional data point (for Adrian or Sebastian) somehow: it seems Felix found a subtle leak on the app side in World/Shortwave#767 (comment 2901730), but from what you had investigated above and in https://github.com/flatpak/xdg-desktop-portal/issues/854 I find it surprising that anything could still be involved on a per-app basis…
The "Export" terminology is too abstract for casual non-technical users. Also always show a label on the button instead of relying on a tooltip, as casual users often don't recognize the abstract symbolic save icon, from my observations in the field. Fixes: #589 Note: I have tested this in a limited way by building and running through GNOME Builder, and forcing the "Save As…" button to be sensitive so that I could at least use it (or Ctrl+S) to open the "Save As…" file chooser dialog, but I was…
Jeff Fortin (12eceedd) at 18 Oct 00:25 app-window: Relabel "Export" to "Save As…"
Jeff Fortin (840d9362) at 18 Oct 00:24
Jeff Fortin (21fbbab5) at 18 Oct 00:24 data: Update bugtracker URL from /issues to /-/work_items ... and 67 more commits
Jeff Fortin (840d9362) at 18 Oct 00:24
I've tried out this branch using Test Center now, and I am running into unreliable behavior there. Sometimes those shortcuts work, but oftentimes they don't. An easy way to reproduce this is to: Ctrl+- repeatedly to bring it below 2 rows Ctrl++ repeatedly to bring it above 6-7™ rows At first, I thought there might be something wrong going on with the way you manage minimum and maximum amounts of rows, and it somehow goes out of bounds... but I think it's just that: your shortcuts only work…
Context Using nm-connection-editor, and hopefully someday GNOME Settings itself, it is possible to rename a known network connection to give it a more meaningful nickname (see GNOME/gnome-control-center#3807 for details). However, while GNOME Settings' GUI reflects this, its GUI doesn't do a great job at laying out both the nickname and SSID texts in a way that can be easily distinguished: List of networks in main Wi-Fi panel List of networks in "Saved Networks" Problems Everything is on the…
Another thing I am noticing that is clearly wrong there is that the event, which spans a bit less than 4 days (from 09:00 EDT on Tuesday October 13th to 18:00 EDT on Friday October 16th) in reality, is rendered as spanning 5 days columns (as if it was from Wednesday October 14th to Sunday October 18th) when the first day of the week is set to Monday instead of Sunday. Since the EDT timezone is UTC-4, 9+4 = 15h UTC and 18+4 = 22h UTC so even if there was a timezones/UTC-related bug I wouldn't…