[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 Nate Graham changed: What|Removed |Added CC||a...@ivantsov.tech --- Comment #8 from Nate Graham --- *** Bug 470217 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 Nate Graham changed: What|Removed |Added CC||greg...@gregorywilliams.me. ||uk --- Comment #7 from Nate Graham --- *** Bug 468989 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 Bruno A. Crespo changed: What|Removed |Added CC||br...@trustserver.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 Nate Graham changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-104398 Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |UPSTREAM --- Comment #6 from Nate Graham --- Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #5 from CUI Hao --- So this is not a Spectacle-specific bug. It's a bug of Qt or Jasper. FYI, I submitted a bug report to Qt: https://bugreports.qt.io/browse/QTBUG-104398 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #4 from CUI Hao --- Well, copying is now OK after I rebooted the system. Saving as jp2 file still triggers segfault. There was probably another bug in clipboard functions. But I think we can focus on the jp2 issue for now... -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362
--- Comment #3 from CUI Hao ---
I can confirm Gwenview and possibly other Qt programs crashes at the same place
when copying image data. I reproduced the bug using this very simple Qt
program:
```
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
MainWindow w;
auto clipboard = QApplication::clipboard();
auto data = new QMimeData();
QPixmap pixmap(128, 128);
pixmap.fill();
auto image = pixmap.toImage();
data->setImageData(image);
clipboard->setMimeData(data);
w.show();
return a.exec();
}
```
The error happens in QEventLoop. I don't know how to debug. I blindly searched
`Jpeg2000JasperReader` references but found none in Qt5 code.
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 --- Comment #2 from CUI Hao --- (In reply to Yerrey Dev from comment #1) > Are you using JP2 file format in Configure -> Save -> Filename? > It's PNG. I never changed the setting. I also wonder about why JP2 format is used. But I couldn't find a clue in the code. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 455362] Spectacle segmentation fault in libjasper after copying image to clipboard
https://bugs.kde.org/show_bug.cgi?id=455362 Yerrey Dev changed: What|Removed |Added CC||yer...@protonmail.com --- Comment #1 from Yerrey Dev --- Are you using JP2 file format in Configure -> Save -> Filename? Looking into this I stumbled upon that JP2 doesn't seem to work at all when saving images producing only 333B empty file and are then prompted with the same deprecation warning you posted. -- You are receiving this mail because: You are watching all bug changes.
