Gwenview Version is 18.04.2 Description: As soon as Gwenview encounters (using browse feature or clicked from Dolphin) a JPG created by a Pentax camera, it exits with a segfault. No other image files created by other cameras reproduce this behavior. Problem started either June 9 or 10 2018; no prior issues with 5 years of using Gwenview. dbg info output: Thread 1 "gwenview" received signal SIGSEGV, Segmentation fault. 0x00007ffff15b2b4f in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const() from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 Exiv2 culprit? Identical to bug reported on CentOS forum 2 weeks ago: https://bugs.centos.org/view.php?id=14882 Also identical to bug reported for EXIV2 last year: http://dev.exiv2.org/issues/1305 JPG picture files containing Olympus & Nikon EXIF data are fine. Only Pentax-created (both K50 and Kr models) cause segfault. Stripping EXIF data via EXIFTOOL does not prevent segfault. Renaming gwenviewrc and deleting thumbnails does not prevent segfault.
June 11 2018 Errata: Further testing shows removing as much Pentax-created EXIF data as possible using EXIFTOOL (exiftool -all= command) returns Gwenview to normal functionality with no further segfaults. This is contrary to the initial bug report description.
This bug is fixed upstream, but a new release 0.27 has not been made yet. I suggest to report it to the bug tracker of your distribution (Ubuntu) and request a backport of the commit referenced in the exiv2 bug tracker. *** This bug has been marked as a duplicate of bug 382842 ***
(In reply to Christoph Feck from comment #2) > This bug is fixed upstream, but a new release 0.27 has not been made yet. I > suggest to report it to the bug tracker of your distribution (Ubuntu) and > request a backport of the commit referenced in the exiv2 bug tracker. > > *** This bug has been marked as a duplicate of bug 382842 *** I was encouraged to file this bug and now I learn it's a year old duplicate with a fix that somehow hasn't made it yet to production NEON, supposedly the KDE flagship distro. Oh, and the solution suggested is pure kludge. I officially give up on Gwenview, and Neon is starting to look decidedly unprofessional as well.
Neon developers only provide KDE software, all other packages are maintained by Ubuntu developers. The bug is not in Gwenview, but in libexiv2.
(In reply to Christoph Feck from comment #4) > Neon developers only provide KDE software, all other packages are maintained > by Ubuntu developers. The bug is not in Gwenview, but in libexiv2. It is probably a regression, not a dupe. I suspect a June 6 update re-broke it and I now have no idea how to fix it, roll it back, nor who to contact about it so the blame for it is absolutely meaningless to me, the end user. I don't think this bug reporting system is really set up for end users, if this experience is typical. Feature suggestion: Preferences switch to turn off access to external functions & libraries Gwenview doesn't control, especially non-essential things like EXIF data that have nothing to do with *viewing pictures*. I prefer earlier versions of Gwenview where access to EXIF data was *optional* via plugin. Until then, nomacs is installed & will have to do. Thanks, you can close this thread.
Moving to Neon bug from Gwenview bug, as per suggestion here: https://old.reddit.com/r/kde/comments/9mlknd/bug_reporting_experience/
*** Bug 400952 has been marked as a duplicate of this bug. ***
Looks like bug is resolved with latest updates! No idea what fixed it though...
My bad, was convinced had taken pictures with my Pentax, turned out it wasn't!
Created attachment 117111 [details] New crash information added by DrKonqi gwenview (18.12.0) using Qt 5.11.2 - What I was doing when the application crashed: Attempting to open a jpg file on NFS share. JPG was created with a Pentax camera. -- Backtrace (Reduced): #6 0x00007fbfd78470ad in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #7 0x00007fbfd788b496 in Exiv2::Internal::PentaxMakerNote::printShutterCount(std::ostream&, Exiv2::Value const&, Exiv2::ExifData const*) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #8 0x00007fbfd7845957 in Exiv2::Exifdatum::write(std::ostream&, Exiv2::ExifData const*) const () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #9 0x00007fbfdd917baf in Exiv2::operator<< (md=..., os=...) at /usr/include/exiv2/metadatum.hpp:305 #10 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup<Exiv2::ExifData, std::_List_const_iterator<Exiv2::Exifdatum> > (this=0x55ad9a6ffbb0, parent=..., group=group@entry=0x55ad9a6da7a0, container=...) at ./lib/imagemetainfomodel.cpp:284
*** Bug 403615 has been marked as a duplicate of this bug. ***
Still not resolved 8 months later. Might be marked as "RESOLVED UPSTREAM", but every version of Neon still has the problem that Gwenview cannot open files with Pentax-created EXIF data without crashing. Neon is the ONLY KDE distro where this happens. All someone has to do is fix the invalid EXIF2 library in the compilation and then the problem will finally and actually be solved. EVERY SINGLE TIME I get yet another email for someone else reporting this problem will cause me to RE-OPEN this bug UNTIL IT IS FIXED.
(In reply to jinnax from comment #13) > EVERY SINGLE TIME I get yet another email for someone else reporting this > problem will cause me to RE-OPEN this bug UNTIL IT IS FIXED. I suggest re-familiarizing yourself with how bug trackers work and work on your manners and etiquette. See: - https://community.kde.org/Get_Involved/Bug_Reporting#Remember_your_manners - https://community.kde.org/Get_Involved/Bug_Reporting#Understand_what_the_resolution_statuses_mean If you want to get a new version of this library added to Neon, you need to file a bug against Neon, not Gwenview.
Created attachment 117896 [details] attachment-4117-0.html Please remove and and all references to any of my email addresses related to this bug. I haven't used Neon since last June, and these emails are getting tiresome. jk Feb 6, 2019, 11:30 AM by bugzilla_noreply@kde.org: > https://bugs.kde.org/show_bug.cgi?id=395198 <https://bugs.kde.org/show_bug.cgi?id=395198> > > Nate Graham <> nate@kde.org <mailto:nate@kde.org>> > changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|RESOLVED |CLOSED > > -- > You are receiving this mail because: > You reported the bug. >
You can remove yourself, just un-CC yourself using the "CC list" control at the top of the page.
I just hope that this bug will be fix before KDE Neon rebase to next Ubuntu LTE edition. I' am simple user that want best KDE experience and beacuse of that use KDE Neon. I can only file a bug raport using poor English skills.
Filed Bug 404033. I'll see if I can get it fixed.
*** Bug 404546 has been marked as a duplicate of this bug. ***
Created attachment 119267 [details] New crash information added by DrKonqi gwenview (18.12.3) using Qt 5.12.0 - What I was doing when the application crashed: Open a jpg in Dolphin, same picture causes the crash every time. -- Backtrace (Reduced): #6 0x00007f31337290ad in Exiv2::ExifData::findKey(Exiv2::ExifKey const&) const () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #7 0x00007f313376d496 in Exiv2::Internal::PentaxMakerNote::printShutterCount(std::ostream&, Exiv2::Value const&, Exiv2::ExifData const*) () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #8 0x00007f3133727957 in Exiv2::Exifdatum::write(std::ostream&, Exiv2::ExifData const*) const () from /usr/lib/x86_64-linux-gnu/libexiv2.so.26 #9 0x00007f3139872c4f in Exiv2::operator<< (md=..., os=...) at /usr/include/exiv2/metadatum.hpp:305 #10 Gwenview::ImageMetaInfoModelPrivate::fillExivGroup<Exiv2::ExifData, std::_List_const_iterator<Exiv2::Exifdatum> > (this=0x564b78700400, parent=..., group=group@entry=0x564b78598e20, container=...) at ./lib/imagemetainfomodel.cpp:284