1. 12 Dec, 2016 1 commit
  2. 22 Nov, 2016 1 commit
  3. 07 Nov, 2016 1 commit
  4. 28 Oct, 2016 1 commit
  5. 10 Oct, 2016 1 commit
  6. 22 Sep, 2016 1 commit
  7. 19 Sep, 2016 2 commits
  8. 13 Sep, 2016 1 commit
  9. 08 Sep, 2016 1 commit
  10. 05 Sep, 2016 1 commit
  11. 17 Aug, 2016 1 commit
  12. 16 Aug, 2016 2 commits
  13. 22 Jul, 2016 1 commit
  14. 18 Jul, 2016 1 commit
  15. 26 Jun, 2016 1 commit
  16. 25 Jun, 2016 4 commits
  17. 21 Jun, 2016 1 commit
  18. 30 May, 2016 1 commit
  19. 26 May, 2016 1 commit
  20. 13 May, 2016 2 commits
  21. 09 May, 2016 1 commit
  22. 26 Apr, 2016 1 commit
  23. 11 Apr, 2016 1 commit
  24. 21 Mar, 2016 1 commit
  25. 17 Mar, 2016 3 commits
  26. 14 Mar, 2016 1 commit
  27. 03 Mar, 2016 1 commit
  28. 26 Feb, 2016 1 commit
  29. 25 Feb, 2016 1 commit
  30. 23 Feb, 2016 1 commit
    • Debarshi Ray's avatar
      thumbnail: Demote a log message from WARNING to DEBUG · 75072547
      Debarshi Ray authored
      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:
        GnomeDesktop-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
      75072547
  31. 16 Feb, 2016 2 commits