summaryrefslogtreecommitdiff
path: root/icons/128x128
diff options
context:
space:
mode:
authorraveit65 <[email protected]>2020-01-01 19:13:49 +0100
committermonsta <[email protected]>2020-02-16 14:02:51 +0300
commitccdc12575c8bf26c05de86e5af381f8b1f236a8d (patch)
treea8195c00ce7d7632eeb1a270bfd67e4389e19513 /icons/128x128
parent4b5002f327375c7f20f80be8174c64aae653d63a (diff)
downloadmate-desktop-ccdc12575c8bf26c05de86e5af381f8b1f236a8d.tar.bz2
mate-desktop-ccdc12575c8bf26c05de86e5af381f8b1f236a8d.tar.xz
thumbnail: Demote a log message from WARNING to DEBUG
Failure to create a GdkPixbufLoader for a specific MIME type doesn't necessarily indicate an error. It is possible that the fallback code would still be able to parse the image data. For example, Canon CR2 RAW files have the MIME type image/x-canon-cr2. While we don't have a loader for that specific MIME type, the TIFF loader can still parse the data. In case the fallback code failed to parse the image data, we get a WARNING anyway: MateDesktop-WARNING **: Error creating thumbnail for ... Having a log message to indicate that we are using the fallback code is useful for debugging, but there is no need for the WARNING. It can be extra noise and needlessly interferes with things like G_DEBUG=fatal-warnings. https://bugzilla.gnome.org/show_bug.cgi?id=762504 origin commit: https://gitlab.gnome.org/GNOME/gnome-desktop/commit/7507254
Diffstat (limited to 'icons/128x128')
0 files changed, 0 insertions, 0 deletions