[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #11 from Martin Kyral --- Created attachment 171952 --> https://bugs.kde.org/attachment.cgi?id=171952&action=edit Patch to use KDCraw over QtRaw Patch to use KDCraw over QtRaw -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #10 from Martin Kyral --- Build of gwenview patched to prefer KDCRaw (Fedora 40 only): https://copr.fedorainfracloud.org/coprs/mkyral/gwenview/ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 463132] Gwenview Removed Support for All RAW Files (Regression)
https://bugs.kde.org/show_bug.cgi?id=463132 --- Comment #8 from Martin Kyral --- It looks like the kimageformats update changes what image format is hinted and that broke image loading by the KDCRaw pipeline. Hardcoding the image format to "jpeg" fixes the pipeline. However, as another fix was already implemented, effecrively ditching KDCRaw altogether and replacing it with QtRaw plugin that works but is slower by 2 orders of magnitude, for this fix/workaround to work one needs to also revert the previous "fix". -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #9 from Martin Kyral --- After some time I looked at the issue again and got some success: the breakage by the kimageformats update was apparently caused by kimageformats somehow affecting the formatHint value, when I hardcoded the format value to "jpeg" for RAW images processed by the KDCraw pipeline, it works. However, I also needed to backport the patch forcing QtRaw plugin in order to get into the KDCRaw pipeline in the first place. With my rudimentary patch, the RAW preview looks like it used to look: it is fast (loading an image in a split second) and it shows the images as get by the camera. Once again: for most manufacturers, the colour science is proprietary and it gets some tweaking if you want to demosaic the raw data and get acceptable colours (getting the colours as if processed by the camera/manufacturer's software is virtually impossible). With this progress, I'd like to ask if it's acceptable/manageable to have the preferred RAW processing pipeline (QtRaw or KDCRaw) configurable by the user. Now, IIUC the switch to KDCRaw pipeline would require recompiling QtImage with QtRAw disabled. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #8 from Martin Kyral --- Just to have a glimpse: I was extracting the embedded hi-res jpeg image using dcraw -e (the method kdcraw uses as well) from 150 raws from 16mpx Olympus. It took under 500ms. Compare it to the Qt Raw plugin which takes several seconds per image. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #7 from Martin Kyral --- (In reply to Martin Kyral from comment #6) > The config option seems perfectly fine to me. Let the user decide that's > best for them. > > The problem is, that KDCraw fucntionality is apparently broken (maybe by > kimageformats 5.99) for quite a while. So, the KDCraw code is still present > but broken. I tried myself with gwenview patched to prefer KDCraw. > > I am looking into the code trying to understand what happens with the data. What happened in kimageformats 5.99? Qt Raw pluging support was implemented. That broke kdcraw pipeline in gwenview, which has been 'fixed' by forcing gwenview to use the Qt RAw plugin as well, which works with the small caveat that it is by orders of magnitude slower, than what was before, rendering gwenview virtually unsable in some use cases (such as crawling through a folder with large number of raw files, which is very common situation everytime one comes home from a shoot). I suppose, kimageformats Qt Raw plugin code shall be reviewed and fixed so it doesn't break code in gwenview that does not utilize it. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #6 from Martin Kyral --- The config option seems perfectly fine to me. Let the user decide that's best for them. The problem is, that KDCraw fucntionality is apparently broken (maybe by kimageformats 5.99) for quite a while. So, the KDCraw code is still present but broken. I tried myself with gwenview patched to prefer KDCraw. I am looking into the code trying to understand what happens with the data. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #4 from Martin Kyral --- Another downturn is that while with KDCraw you get the image straight from the camera, with Qt Raw plugin the image looks different, rather dull and underexposed as the demosaicing algorithm and colour science is proprietary to the camera manufacturer and thus hard to replicate. While with full raw converter the user has wide palette of tools and settings to do the colour science and processing to their liking, the number of adjustments provided by gwenview is ZERO and providing them is far out of scope of it. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 --- Comment #3 from Martin Kyral --- By regression I mean the feature is virtually unusable. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 463132] Gwenview Removed Support for All RAW Files (Regression)
https://bugs.kde.org/show_bug.cgi?id=463132 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #7 from Martin Kyral --- I have no idea why Qt Raw plugin is being preferred over KDCraw, but the current implementation bring serious feature regression: while KDCraw implementation extracts insplit second already generated (in camera) preview jpeg from the raw file, the Qt Raw plugin implementation generates the jpeg data from raw, which takes considerable time even on pretty fast HW (on 10 core i7 ~ 7s). The same applies even to the thumbnailing. Imagine a folder containing some 500 raw images and you can do the math yourself. This change renders raw support in gwenview virtually unusable. I'd suggest either fixing the Qt Raw plugin implementation so it utilizes the embedded hi-res preview or preferring kdcraw over qt raw plugin. https://bugs.kde.org/show_bug.cgi?id=454206 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454206] Slow performance with RAW files on big folders
https://bugs.kde.org/show_bug.cgi?id=454206 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #2 from Martin Kyral --- Well, I just guess but with a grain of knowledge as I implemented the original RAW support in gwenview back in 2013: * the original KDCRaw-based implementation used the preview image bundled in the raw file itself. That's fast as it's only reading the already prepared preview data and treating them as jpeg (you can get the preview using dcraw -e file.raw). * it seems to me that alternative implementation using Qt Raw plugin and it is being preferred * from quick peek at the code I assume, that with Qt Raw plugin the trick with using the preview that's aready present is not used (I am not sure if Qt Raw plugin can do that) * demosaicing takes time I consider this to be a major regression. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465023] Opening "Window Decorations" Crashes System Settings.
https://bugs.kde.org/show_bug.cgi?id=465023 --- Comment #3 from Martin Kyral --- Fixing the packages fixed the segfault. Do make sure you have all of the packages in the same version. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465023] Opening "Window Decorations" Crashes System Settings.
https://bugs.kde.org/show_bug.cgi?id=465023 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #2 from Martin Kyral --- I am experiencing the same segfault on Fedora 37 and just now I noticed the likely cause: mixed packageset. You (and me too) are having installed plasma-systemseting 5.26.5 on top of 5.26.90 plasma. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 --- Comment #10 from Martin Kyral --- (In reply to andrey.zu from comment #9) > This is not a bug in the preview. It is bad when i want to save ARW to JPEG. It is not a bug. If you want to save jpeg out of RAW, you should always go through the proper processing in a dedicated application (darktable etc.). The preview is what it is: a preview. Not only it is scaled down in some RAW types, it is also heavily compressed. If you want to use processed image straight out of the camera, just save jpeg in the camera. There's nothing gwenview can do to improve preview quality for ARW. This bug shall therefore be closed as NOT A BUG. Note: the feature is broken since 21.08: https://bugs.kde.org/show_bug.cgi?id=441698 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441698] Gwenview fails to open and preview RAW images (NEF, ARW, etc.) : mimetype is detected as TIFF
https://bugs.kde.org/show_bug.cgi?id=441698 Martin Kyral changed: What|Removed |Added Keywords||regression Flags||corner_case-, Usability+ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441698] Gwenview fails to open and preview RAW images (NEF, ARW, etc.) : mimetype is detected as TIFF
https://bugs.kde.org/show_bug.cgi?id=441698 --- Comment #49 from Martin Kyral --- I believe this patch shall be reverted: https://invent.kde.org/graphics/gwenview/-/commit/6a79391a9ab68bec839897369c665ee2e3afe7e5 When fixing a bug, there always shall be a) regression testing and b) consideration if the benefit of the fix outweights the problems it causes. In this case, it fails in both. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441698] Gwenview fails to open and preview RAW images (NEF, ARW, etc.) : mimetype is detected as TIFF
https://bugs.kde.org/show_bug.cgi?id=441698 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #48 from Martin Kyral --- (In reply to Maximilian Schmeling from comment #34) > According to this site: http://lclevy.free.fr/nef/ > The Nikon Electronic File format (NEF) also stores an (approximately) > 160x120 preview thumbnail (uncompressed TIFF). > Gwenview might choose the thumbnail instead of the raw image. > This would also explain the duplicate attributes, one for the real raw image > and the other for the thumbnail. Well, there are acutally two jpeg previews in each and every RAW file: 160x120 and full-res or reduced-but-high-enough. What's the former one purpose, I don't know. The latter one is there so you can review the image on the back of the camera whle not draining the battery for demosaicing. dcraw -e abdc.raw gives you the preview. Gwenview uses libraw to extract the high-res jpeg preview and feed it into the jpeg pipeline. I know that, because I implemented the feature back in 2013. Unfortunatelly, I kind of fell out of the process and haven't written a line in C++ since then so I am not sure I can fix the breakage which I discovered right now. What a mess... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423052] [FTBFS]: kwin on f33 / s390x
https://bugs.kde.org/show_bug.cgi?id=423052 --- Comment #4 from Martin Kyral --- Thanks for the fix -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423052] [FTBFS]: kwin on f33 / s390x
https://bugs.kde.org/show_bug.cgi?id=423052 --- Comment #1 from Martin Kyral --- Any progress, please? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 423052] New: [FTBFS]: kwin on f33 / s390x
https://bugs.kde.org/show_bug.cgi?id=423052
Bug ID: 423052
Summary: [FTBFS]: kwin on f33 / s390x
Product: kwin
Version: 5.19.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: sine.nom...@centrum.cz
Target Milestone: ---
SUMMARY
kwin 5.19 fails to build on rawhide / s390x. The reason is:
/usr/bin/ld: CMakeFiles/kwin.dir/input.cpp.o: in function
`KWin::TabletInputFilter::tabletToolEvent(KWin::TabletEvent*)::{lambda(KWaylandServer::TabletCursor*)#2}::operator()(KWaylandServer::TabletCursor*)
const::{lambda()#1}::operator()() const':
/builddir/build/BUILD/kwin-5.19.0/input.cpp:1672: undefined reference to `void
KWin::WaylandCursorImage::loadThemeCursor(KWin::CursorShape
const&, KWin::WaylandCursorImage::Image*)'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/kwin.dir/build.make:2339: bin/libkwin.so.5.19.0] Error
1
make[2]: Leaving directory
'/builddir/build/BUILD/kwin-5.19.0/s390x-redhat-linux-gnu'
make[1]: *** [CMakeFiles/Makefile2:4330: CMakeFiles/kwin.dir/all] Error 2
make: *** [Makefile:164: all] Error 2
full log:
https://kojipkgs.fedoraproject.org//work/tasks/7168/45747168/build.log
First time I saw this issue was woth 5.18.90 (5.19 beta). Since then, it fails
consistently. This problem does not happen on older kwin releases nor on other
architectures.
Dan Horák 2020-06-15 15:58:41 UTC
So either this is a code bug (some incorrect template usage) or we have a g++
bug. I have reproduced the failure on ppc64le by adding the options s390x is
using for aggressive inlining (--param=inline-min-speedup=2
--param=max-inline-insns-auto=80).
...
Jonathan Wakely 2020-06-16 09:09:43 UTC
Like I said, "the definitions actually rely on something else that is only
declared in the pointer_input.cpp file".
If they don't want to declare KWayland in the header file then they'll need to
add explicit instantiation declarations to the header for the specializations
that are actually used (at least
KWin::WaylandCursorImage::loadThemeCursor) and then
explicitly instantiate that in the .cpp file.
Either way, the upstream code is not valid C++ and that's why GCC doesn't build
it.
...
https://bugzilla.redhat.com/show_bug.cgi?id=1847014
STEPS TO REPRODUCE
1. see the referenced downstream bug
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 422129] New: Plasma (plasmashell), signal: Segmentation fault in QQuickItemPrivate::removeItemChangeListener(..)
https://bugs.kde.org/show_bug.cgi?id=422129 Bug ID: 422129 Summary: Plasma (plasmashell), signal: Segmentation fault in QQuickItemPrivate::removeItemChangeListener(..) Product: plasmashell Version: 5.18.90 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sine.nom...@centrum.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.90) (Compiled from sources) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.14-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I am using plasma 5.18.90 on F32 built in copr: https://copr.fedorainfracloud.org/coprs/mkyral/plasma-unstable/ Though not official build, the contents is identical with what is being imported in Fedora Rawhide Behaviour: * plasmashell crashes right after session start * plasmashell crashes when started from kicker * plasmashell crashes often (but not always) when started from konsole Noteworthy detail: * when plasmashell starts, it runs fine * when plasmashell starts, it does not respect my locale settings (notable: language and time format) The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #7 0x7f27fa7f8fec in QQuickItemPrivate::removeItemChangeListener(QQuickItemChangeListener*, QFlags) () at /lib64/libQt5Quick.so.5 #8 0x7f27fa93107f in QQuickShaderEffectSource::~QQuickShaderEffectSource() () at /lib64/libQt5Quick.so.5 #9 0x7f27fa9310ed in QQuickShaderEffectSource::~QQuickShaderEffectSource() () at /lib64/libQt5Quick.so.5 #10 0x7f27cd6ba50f in QGfxSourceProxy::~QGfxSourceProxy() () at /usr/lib64/qt5/qml/QtGraphicalEffects/private/libqtgraphicaleffectsprivate.so #11 0x7f27cd6b7319 in QQmlPrivate::QQmlElement::~QQmlElement() () at /usr/lib64/qt5/qml/QtGraphicalEffects/private/libqtgraphicaleffectsprivate.so #12 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #13 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #14 0x7f27fa8413a9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #15 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #16 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #17 0x7f27fa8413a9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #18 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #19 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #20 0x7f27fa8413a9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #21 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #22 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #23 0x7f27fa840db9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #24 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #25 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #26 0x7f27fa8413a9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #27 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #28 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #29 0x7f27fa840db9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #30 0x7f27f8e5277a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #31 0x7f27f8e57ecf in QObject::~QObject() () at /lib64/libQt5Core.so.5 #32 0x7f27fa8413a9 in QQmlPrivate::QQmlElement::~QQmlElement() () at /lib64/libQt5Quick.so.5 #33 0x7f27f8e52961 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #34 0x7f27f981c063 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #35 0x7f27f8e2afc0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #36 0x7f27f8e2dc47 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #37 0x7f27f8e770a7 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #38 0x7f27f73a67af in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #39 0x7f27f73a6b38 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #40 0x7f27f73a6c03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #41 0x7f27f8e76b73 in QEventDispatcherGlib::processEvents(QFlags) () at /li
[gwenview] [Bug 158788] Gwenview does not support image files in RAW format
https://bugs.kde.org/show_bug.cgi?id=158788 Martin Kyral changed: What|Removed |Added CC||dee...@antrix.net --- Comment #13 from Martin Kyral --- *** Bug 127022 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 127022] RAW images selection impossible
https://bugs.kde.org/show_bug.cgi?id=127022 Martin Kyral changed: What|Removed |Added Status|REPORTED|RESOLVED CC||sine.nom...@centrum.cz Resolution|--- |DUPLICATE --- Comment #3 from Martin Kyral --- Fixed long ago: https://bugs.kde.org/show_bug.cgi?id=158788 *** This bug has been marked as a duplicate of bug 158788 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 --- Comment #6 from Martin Kyral --- See https://bugs.kde.org/show_bug.cgi?id=158788 for reference -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 347574] Sony DSC-RX100 ARW raw files are not displayed in full resolution
https://bugs.kde.org/show_bug.cgi?id=347574 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #5 from Martin Kyral --- Yes, that is intentional (I implemented the raw preview feature back in 2013). While Canon, Nikon and some other camera manufacturers do bundle full-res jpeg preview in the raw file, Sony bundles just a scaled-down one. As gwenview is intended to (pre)view the images as accurately as possible and at the same do it quickly, it uses the bundled preview rather than perform full raw data decoding. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380312] New: plasma crash on start (not every time)
https://bugs.kde.org/show_bug.cgi?id=380312
Bug ID: 380312
Summary: plasma crash on start (not every time)
Product: plasmashell
Version: 5.9.95
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: sine.nom...@centrum.cz
CC: bhus...@gmail.com, plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.9.95)
(Compiled from sources)
Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.11.3-200.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"
-- Information about the crash:
After login, plasmashell started as expected. I restarted it by pkill
plasmashell ; plasmashell - thing I do sometimes - but plasma didn't come up. I
tried starting plasmashell from console, getting:
$ plasmashell
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried ("/home/mkyral/.local/share",
"/home/mkyral/.local/share/flatpak/exports/share",
"/var/lib/flatpak/exports/share", "/usr/local/share", "/usr/share")
org.kde.kcoreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to
be a string list. Treating it as a list with a single entry: "panel"
org.kde.plasma.desktop.appmenubar
org.kde.kcoreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to
be a string list. Treating it as a list with a single entry: "panel"
org.kde.plasma.desktop.defaultPanel
org.kde.kcoreaddons: Expected JSON property "X-Plasma-ContainmentCategories" to
be a string list. Treating it as a list with a single entry: "panel"
org.kde.plasma.desktop.emptyPanel
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried ("/home/mkyral/.local/share",
"/home/mkyral/.local/share/flatpak/exports/share",
"/var/lib/flatpak/exports/share", "/usr/local/share", "/usr/share")
kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/plasma-popupapplet.desktop, tried ("/home/mkyral/.local/share",
"/home/mkyral/.local/share/flatpak/exports/share",
"/var/lib/flatpak/exports/share", "/usr/local/share", "/usr/share")
WARNING: Cannot find style "org.kde.desktop" - fallback:
"/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Desktop"
No metadata file in the package, expected it at:
"/home/mkyral/Obrázky/Wallpapers/"
No metadata file in the package, expected it at:
"/home/mkyral/Obrázky/Wallpapers/"
No metadata file in the package, expected it at:
"/home/mkyral/Obrázky/Wallpapers/"
No metadata file in the package, expected it at:
"/home/mkyral/Obrázky/Wallpapers/"
No metadata file in the package, expected it at:
"/home/mkyral/Obrázky/Wallpapers/"
No metadata file in the package, expected it at:
"/home/mkyral/Obrázky/Wallpapers/"
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderItemDelegate.qml:173:32:
Unable to assign [undefined] to double
file:///usr/
[plasmashell] [Bug 344860] unable to maximize after undocking
https://bugs.kde.org/show_bug.cgi?id=344860 Martin Kyral changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Martin Kyral --- The problem did not occur for quite some time, closing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 355235] kdeinit5 crash upon undocking
https://bugs.kde.org/show_bug.cgi?id=355235 Martin Kyral changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #4 from Martin Kyral --- The crash did not happen for quite some time, closing. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361419] Unaccepted Google calendar events not shown
https://bugs.kde.org/show_bug.cgi?id=361419 --- Comment #5 from Martin Kyral --- I'd be happy to look for a fix, had I known where. It must be just some if/filter when showing the incidences in the calendar view. Any hints, please? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361419] Unaccepted Google calendar events not shown
https://bugs.kde.org/show_bug.cgi?id=361419 --- Comment #4 from Martin Kyral --- Created attachment 104408 --> https://bugs.kde.org/attachment.cgi?id=104408&action=edit this week in google cal ui -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361419] Unaccepted Google calendar events not shown
https://bugs.kde.org/show_bug.cgi?id=361419 --- Comment #3 from Martin Kyral --- Created attachment 104407 --> https://bugs.kde.org/attachment.cgi?id=104407&action=edit this week in korganizer just to illustrate the impact of this bug -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 359786] No RW2 support on version 15.08.3
https://bugs.kde.org/show_bug.cgi?id=359786 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #1 from Martin Kyral --- I think it is safe to close this bug now. libkdcraw-enabled version of kf5 is hanging around for quite some time. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 361419] Unaccepted Google calendar events not shown
https://bugs.kde.org/show_bug.cgi?id=361419 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #2 from Martin Kyral --- Same with me. I have my calendar almost empty in Korganizer, while in the Overview screen of Kontact the omitted events are and (at least for some of them) I even got reminders. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 370981] Can't enter LUKS password
https://bugs.kde.org/show_bug.cgi?id=370981 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #1 from Martin Kyral --- I am confirming the bug, experiencing it too. No need to hit [Esc], the password can be typed blindly. But yeah, from plain black screen one can not tell it it is waiting for the password or just hung. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 369188] Unable to change backgoud of the lock screen in 5.7.95
https://bugs.kde.org/show_bug.cgi?id=369188 Martin Kyral changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Martin Kyral --- I had probably some important bits missing. After upgrading to 5.8.0 from copr everything works fine. Closing the bug now. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 369188] New: Unable to change backgoud of the lock screen in 5.7.95
https://bugs.kde.org/show_bug.cgi?id=369188 Bug ID: 369188 Summary: Unable to change backgoud of the lock screen in 5.7.95 Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sine.nom...@centrum.cz CC: bhus...@gmail.com, mgraess...@kde.org In plasma 5.8 there is a switch to new lock screen. Being plain and simple it is nice indeed, but I'd like to have other background than solid black. I tried to change it in systemsettings -> Desktop Behaviour -> Sceeen Locking but with no success. No matter what image I select there, the background stays black. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #24 from Martin Kyral --- Confirming. konversation blinking icon eats a lot of CPU time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays
https://bugs.kde.org/show_bug.cgi?id=359611 --- Comment #41 from Martin Kyral --- Are the blocking calls in the device manager widget going to be fixed, too? I sometimes mount nfs drive and when I'm out of the connection and need to restart plasma (or plasma crashes), it won't come up because of it. I know the workaround (umount -l and restart plasmashell once more), but still.. it's annoying... Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360889] Graphic artifacts on the panel's pop-ups
https://bugs.kde.org/show_bug.cgi?id=360889 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #1 from Martin Kyral --- I'm seeing the glitches with plasma 5.65.95 and intel graphics, too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays
https://bugs.kde.org/show_bug.cgi?id=359611 --- Comment #25 from Martin Kyral --- (In reply to David Edmundson from comment #24) > There is a patch for Qt. See email on KDE packagers ml. > > If you use a distro without that patch, your distro sucks and you should > change. Thanks, I updated qt to the patched version and it works (with powerdevil enabled, of course). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359611] Plasmashell loads itself incompletely and with long delays
https://bugs.kde.org/show_bug.cgi?id=359611 Martin Kyral changed: What|Removed |Added CC||sine.nom...@centrum.cz --- Comment #23 from Martin Kyral --- I experienced plasmashell hangups on DBUS call too. Now, I can use plasmshell, but I had to disable powerdevil and the battery widget. Backtrace: (gdb) i th Id Target Id Frame 8Thread 0x7f1cb5317700 (LWP 2091) "QXcbEventReader" 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 7Thread 0x7f1cafb65700 (LWP 2096) "QDBusConnection" 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 6Thread 0x7f1cae324700 (LWP 2123) "QQmlThread" 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 5Thread 0x7f1ca6359700 (LWP 2168) "QQmlThread" 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 4Thread 0x7f1ca498c700 (LWP 2181) "QQmlThread" 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 3Thread 0x7f1c9afb9700 (LWP 2259) "plasmashell" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 2Thread 0x7f1c13fff700 (LWP 2311) "QQuickPixmapRea" 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 * 1Thread 0x7f1cbea06940 (LWP 2070) "plasmashell" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 (gdb) t a a bt Thread 8 (Thread 0x7f1cb5317700 (LWP 2091)): #0 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1cd240c272 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f1cb5316b80) at /usr/include/bits/poll2.h:46 #2 0x7f1cd240c272 in _xcb_conn_wait (c=c@entry=0x56014cc91ac0, cond=cond@entry=0x56014cc91b00, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x7f1cd240dee7 in xcb_wait_for_event (c=0x56014cc91ac0) at xcb_in.c:693 #4 0x7f1cb756a349 in QXcbEventReader::run() (this=0x56014cc9c270) at qxcbconnection.cpp:1313 #5 0x7f1ccdeb8e18 in QThreadPrivate::start(void*) (arg=0x56014cc9c270) at thread/qthread_unix.cpp:340 #6 0x7f1ccc5ea60a in start_thread (arg=0x7f1cb5317700) at pthread_create.c:334 #7 0x7f1ccd2b2a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f1cafb65700 (LWP 2096)): #0 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1cc8d7516c in g_main_context_iterate (priority=2147483647, n_fds=3, fds=0x7f1ca8003020, timeout=, context=0x7f1ca8000990) at gmain.c:4135 #2 0x7f1cc8d7516c in g_main_context_iterate (context=context@entry=0x7f1ca8000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f1cc8d7527c in g_main_context_iteration (context=0x7f1ca8000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f1cce0e1d0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f1ca80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f1cce08a6ea in QEventLoop::exec(QFlags) (this=this@entry=0x7f1cafb64c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f1ccdeb4004 in QThread::exec() (this=this@entry=0x7f1cce8eb040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:503 #7 0x7f1cce877445 in QDBusConnectionManager::run() (this=0x7f1cce8eb040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:181 #8 0x7f1ccdeb8e18 in QThreadPrivate::start(void*) (arg=0x7f1cce8eb040 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:340 #9 0x7f1ccc5ea60a in start_thread (arg=0x7f1cafb65700) at pthread_create.c:334 #10 0x7f1ccd2b2a4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f1cae324700 (LWP 2123)): #0 0x7f1ccd2a6fdd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1cc8d7516c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f1ca0002e70, timeout=, context=0x7f1ca990) at gmain.c:4135 #2 0x7f1cc8d7516c in g_main_context_iterate (context=context@entry=0x7f1ca990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f1cc8d7527c in g_main_context_iteration (context=0x7f1ca990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x7f1cce0e1d0b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f1ca8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f1cce08a6ea in QEventLoop
[frameworks-kinit] [Bug 355235] kdeinit5 crash upon undocking
https://bugs.kde.org/show_bug.cgi?id=355235 Martin Kyral changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- --- Comment #2 from Martin Kyral --- Unfortunatelly even after the 'fix' of the bug in QT, kdeinit5 + bunch of other KDE processes crashes almost every time when I suspend the laptop, undock it and resume after a while. Yesterday something went so wrong that I am now unable to even start plasmashell - it hangs waiting on some futex. I am disappointed by that to the point that I am considering switch to another desktop - KDE is unusable for me now anyways. It is another bug in QT it seems. Please file them an issue for me. Application: kdeinit5 (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa03260e8c0 (LWP 15813))] Thread 2 (Thread 0x7fa00fad1700 (LWP 15815)): #0 0x7fa02fcc8fdd in poll () at /lib64/libc.so.6 #1 0x7fa02e33f16c in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fa02e33f27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fa030b00acb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fa030aa950a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fa0308d5744 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fa0326cd225 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7fa0308da6b8 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7fa02f51160a in start_thread () at /lib64/libpthread.so.0 #9 0x7fa02fcd4a4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa03260e8c0 (LWP 15813)): [KCrash Handler] #4 0x7fa016873081 in QXcbConnection::updateScreens(xcb_randr_notify_event_t const*) () at /lib64/libQt5XcbQpa.so.5 #5 0x7fa016874732 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /lib64/libQt5XcbQpa.so.5 #6 0x7fa016874bf6 in QXcbConnection::processXcbEvents() () at /lib64/libQt5XcbQpa.so.5 #7 0x7fa030ad8e59 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #8 0x7fa030aab7ea in QCoreApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #9 0x7fa030aab948 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #10 0x7fa030aad80a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #11 0x7fa030afe152 in QEventDispatcherUNIX::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #12 0x7fa0168e19fd in QUnixEventDispatcherQPA::processEvents(QFlags) () at /lib64/libQt5XcbQpa.so.5 #13 0x7fa030aa950a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #14 0x7fa030ab1d4c in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #15 0x7fa01726bc7a in kdemain () at /lib64/libkdeinit5_klauncher.so #16 0x55da5c633776 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #17 0x55da5c630a17 in main () Application: KDE Global Shortcuts Service (kglobalaccel5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa16902b8c0 (LWP 15851))] Thread 2 (Thread 0x7fa147436700 (LWP 15867)): #0 0x7fa166386bcd in read () at /lib64/libc.so.6 #1 0x7fa164df1390 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7fa164dadc64 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7fa164dae110 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7fa164dae27c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7fa1671c2acb in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7fa16716b50a in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7fa166f97744 in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7fa1690ea225 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #9 0x7fa166f9c6b8 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #10 0x7fa1652f660a in start_thread () at /lib64/libpthread.so.0 #11 0x7fa166396a4d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fa16902b8c0 (LWP 15851)): [KCrash H
[gwenview] [Bug 158788] Gwenview does not support image files in RAW format
https://bugs.kde.org/show_bug.cgi?id=158788 --- Comment #12 from Martin Kyral --- Unfortunatelly, many distributions pushed KF5 version of gwenview before digikam folks ported libkdcraw to KF5 - which happened in the 15.12 release. Thus, they are shipping gwenview with feature regression. Please, file a bug against your distribution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355750] When setting up panels in Plasma, plasma shell crashes
https://bugs.kde.org/show_bug.cgi?id=355750 --- Comment #6 from Martin Kyral --- Duplicate of: https://bugs.kde.org/show_bug.cgi?id=354660 After upgrade to plasma 5.5 it seems the crashes are a history. Please, close this bug as duplicate. Thanks! -- You are receiving this mail because: You are watching all bug changes.
