Jehan commented on issue #16907 at GNOME / GIMP
Thanks and sorry for the lateness. Both variables (for macOS and for MSIX) updated. Testing again: https://gitlab.gnome.org/GNOME/gimp/-/pipelines/1136438
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
Thanks and sorry for the lateness. Both variables (for macOS and for MSIX) updated. Testing again: https://gitlab.gnome.org/GNOME/gimp/-/pipelines/1136438
Well, I was a little confused here, but nevertheless, adding overflow="hidden" to the might help.
@nmontero would you be available to review this?
The Wired.Carrier property lives on a different D-Bus interface than Device.State, and changes to it do not emit "state-changed". Since NetDeviceEthernet only subscribed to "state-changed", a carrier-only change never triggered a refresh and the row kept rendering whatever it last drew. Subscribe to notify::carrier as well, and fold the open-coded carrier check in connection_list_row_activated_cb into a device_has_carrier() helper. This also fixes a smaller ordering problem: State and Carrier…
Felipe Borges (c228b63d) at 29 Oct 10:22 network: Report "Cable unplugged" whenever the carrier is down ... and 1 more commit
I suppose we could add a test which bounds the amount of time g_thread_yield() is allowed to take ⇒ !5446
To put an upper bound on how long g_thread_yield() should be allowed to take. Signed-off-by: Philip Withnall pwithnall@gnome.org Helps: #4099
Affected version Distribution, including version: Fedora Silverblue 41.20241107.0 Papers cersion: 47.0 Package format and distributor: Flatpak from Flathub" Summary Text selection doesn't follow the document's structure, making selection hard. Description On documents with two side-by-side "paper" pages per PDF page, the text selection is performed as if they were a single page. In Firefox's PDF reader, it works as expected. This makes selecting text harder than it should be. Here is the…
I am not entirely sure that it is a Poppler issue, given that it works just fine in Okular, as I demonstrated in https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1547#note_3735644
Affected Version Distribution and version: Ubuntu 26.04 Package format and distributor: deb from Debian Papers version: 50.2 (flatpak 51.0 behaves the same) Summary Selecting (OCR generated) text in a multi-column layout selects lines spanning different columns, but if I open the same document in Firefox, it works fine and I can select a paragraph in a column. I expect that from any PDF viewer. Description Please find attached a simple sample document with the mentioned problem. test.pdf
Does the issue occur with Okular too? If so, it's almost certainly a Poppler issue like #296.
nit on past me: not new gsetting, but rather documenting scroll and fallback keys in the gsetting. It's fine if Mutter changes land without that documentation, since it'll all fail cleanly, and there's no need to keep them synced outside of actually documenting the settings.
Best to put this code in a central place. Also add a test.
Marge Bot (c706c00e) at 25 Oct 03:51 Merge branch 'for-main' into 'main' ... and 2 more commits
And Spending Countless Hours on these Messages 🤦♂️ It's been a long time since something I did was that inefficient. Because a Tool that didn't miss Anything got an "Update". That's what we call »Verschlimmbesserung« (DisImprovement) in German.
This reverts commit 87383719. The required pango change has landed in the gnome os image.
Best to put this code in a central place. Also add a test.
Hi there 🙋♂️ My Answer on this is late because I misunderstood some of the Things You said and couldn't see any changes after updating. To Me I felt the Efforts put into my Proposal simply disregarded which I found to be rather Enraging. I can't test the New UI for the Time Being since I'm still on the Same Manjaro System on which I gave up on Updating for the Sake of No More Breakage. I could still Update simple-scan ~ which shows v.50.0 on the About Screen now ~ but Appearance is still the…
The file format does not specify correct behaviour for this. (In some contexts, such as for conditional formats, solid is definitely correct.) I suggest filing a bug against openpyxl to make it avoid such xml. Nonetheless I have changed Gnumeric for this.
When I create a spreadsheet in openpyxl all the cells have a white fill that blocks the gridlines. If I select some cells and reset the fill, I can see the gridlines. I was able to find a workaround that may point to the issue. In xl/styles.xml, openpyxl writes the following which corresponds to the default, PatternFill(fill_type='none') or PatternFill(fill_type='none') : If I change this to The problem goes away. So is Gnumeric treating an unspecified fill pattern as solid white? If someone…
Morten Welinder (f2ce1b98) at 25 Oct 02:34 xlsx: fix possible problem with xlsx import.
Which extension Affected version Bug summary Steps to reproduce What happened What did you expect to happen Relevant logs, screenshots, screencasts etc.
Morten Welinder (973fdb33) at 25 Oct 01:49 WbcGtk: various fixes.
It's been three years since someone last tested; Is anyone even seeing this at all in recent versions like 51.x? Personally I don't think I've experienced it in 50.x and newer, but then I'm running Fedora Workstation (i.e. RPMs + Flatpak), not Silverblue. Is it only something that occurs on Silverblue / rpm-ostree? If so, I think it should be part of the ticket title and have the rpm-ostree label too.
Bruno (3bfa5e8d) at 25 Oct 00:49 build/macos: Save fontconfig cache files on ~/Library/Caches on macOS
Bruno (6b78ec4f) at 25 Oct 00:42 libgimpwidgets: Fix wrong colors on ScreenCaptureKit codepath ... and 2 more commits
Time to create an AI policy for this project, methinks.
I'm the coordinator of the Azerbaijani translation team on l10n.gnome.org. I'd like to create a personal project for "hunayn", a GPL-licensed CLI and QA linter for GNOME translators that works with the Damned Lies API. Currently my account gets a 403 when creating projects. Could you enable project creation for my account?
If your idea of a "bunch of code" is 45 lines, then let me know and I'll rework the commits. I'm not sure how you feel about backporting the fd checking commit vs the symlink version (that would be another argument for keeping the 45 LOC version)
@WarisMaqbool I probably used GEGL_DEBUG=all or one of the other env vars: https://www.gegl.org/environment.html#GEGL_DEBUG. I can test if it still happens for me after you fixed the issue you mentioned.