Recently I tried to edit some image from the internet in GIMP. Pressing "open image in new tab" in Firefox yielded a "data:image/svg+xml;base64..." link. Being a lazy person, instead of saving the image to disk, I selected "open location" in GIMP and pasted the link there. Next thing I know, there's some fireworks.
I spun up a clean Fedora 34 VM to try to replicate this, and here's my observations:
1. Gnome on Wayland: GIMP crashes and that seems to be the end of it.
2. Gnome on X11: GIMP crashing brings down the Gnome panel (taskbar, whatever you want to call it) along with it. The latter auto-restarts. Other programs are unaffected.
3. Cinnamon: GIMP does not crash, instead it displays a gargantuan (over 5000 pixels wide) error message window. Moving this window around causes Cinnamon to crash. It then auto-restarts... but, amusingly, apart from Cinnamon, Openbox starts up as well. (Should someone try reproducing this - by default, both the Cinnamon and Openbox panels appear on the bottom of the screen, so the Openbox panel won't be visible. Just move the Cinnamon panel to another edge of the screen.) GIMP survives this, and other programs are unaffected.
4. KDE Plasma on Wayland: the gigantic error message appears, but instead of rendering the text, it's just a big black rectangle on the screen. However, GIMP does not crash. Other programs seem unaffected.
5. KDE Plasma on X11: as above, but the error message window doesn't render at all. It is there, it takes input, you can alt+tab to and away from it, but it's not visible.
6. XFCE: GIMP crashes and that's the end of it.
7. MATE: GIMP crashes and other program windows jump around on the screen for a short while. Afterwards, things seem to work fine, but every window renders with a several-pixels wide black border around it.
8. LXQt: GIMP crashes and brings down the LXQt panel with it. The latter does *NOT* auto-restart. Other programs stop reacting to keyboard input. This effectively locks one in the desktop session (short of switching to a TTY).
9. Openbox: the whole session crashes, bringing you back to the display manager's login screen.
The base64 image is too big to put it in an e-mail, so I attach it as a link: https://suve.fedorapeople.org/2021-06-18-gimpcrash-image-base64.txt
I have not tested whether other base64-encoded SVG images cause similar issues, or if it's only this one.
I'm not sure if this a bug in GIMP, or in poor old Xorg, so that's why I decided to post an e-mail here, instead of going straight to bugzilla.
Should anyone try to dig into this, let me know if you need a core dump or something.
strongswan and NetworkManager-strongswan packages were passed to me from
previous maintainer. I admit I have little experience with them and do
not run any service based on them. Because IPSsec is quite complex
technology, I am looking for help with its maintenance. I was always
using OpenVPN based solutions myself, so I guess I am not the best
person as main admin. I would like to transfer main admin to anyone
doing a good job, not not immediately. That is why I haven't orphaned it
I would like to keep commit access for a while, but I would share at
least commit access with anyone willing to improve those packages.
Especially someone using they (almost) everyday would be ideal maintainer.
Hi, I'd like to retire the original glib, GLib 1 from the GNOME 1 era.
This is would take out the gtk+ package (GTK 1) along with it. (I'm not
proposing to remove GTK 2.) GLib 1 has been obsolete for 19 years now,
since GLib 2 was released in March 2002. That's a real long time to
maintain a compatibility package, so I'm not sympathetic to anything
that still requires it.
GLib 2 has been API and ABI stable for 19 years now, so it's not moving
too fast for your package to depend on. :) The full list of packages
still depending on GLib 1 is below. If you own one of the below
packages, please consider upgrading to GLib 2. The only one that I
recognize is Sagemath.
$ sudo dnf repoquery --recursive --whatrequires glib
Last metadata expiration check: 0:28:04 ago on Fri 07 May 2021 09:06:03
It's nearly time for another round of mathematical software updates,
including some soname bumps. I am going to do the following, in this
- cliquer: update to version 1.22
- cocoalib: update to version 0.99713
- ffcall: update to version 2.3
- memtailor: update to git head for some minor improvements
- pari: build with pthreads support
- primecount: update to version 7.0, which entails an soname bump
- clisp: rebuild due to the ffcall and pari updates
- eclib: rebuild due to the pari update
- giac: rebuild due to the cocoalib and pari updates, and add cliquer support
- L-function: rebuild due to the pari update
- mathic: update to git head for some minor improvements
- normaliz: rebuild due to the cocoalib update
- python-cysignals: update to version 1.10.3
- mathicgb: update to git head for some minor improvements
- python-cypari2: update to version 2.1.2
- python-fpylll: update to version 0.5.6
- python-pplpy: rebuild due to the python-cysignals update
- Singular: update to version 4.2.0, which entails an soname bump
- palp: update to version 2.11
- polymake: update to version 4.4, which entails an soname bump
- pynac: update to version 0.7.27
- python-jupymake: rebuild due to the polymake soname bump
- sagemath: update to version 9.3
- python-jupyter-polymake: rebuild due to the polymake soname bump
- Macaulay2: update to version 1.18
I'm still working through some minor issues with Macaulay2 and some
major issues with sagemath, but I hope to have those worked out and
builds ready to go sometime next week. The builds will be done for
Rawhide initially, but the sagemath fans in the Fedora audience
*really* want version 9.3, so if all goes well, I will also update at
least F34, and F33 as well if sufficient pressure is applied to do so.