[kio-gdrive] [Bug 467428] Expired or missing access tokens for account
https://bugs.kde.org/show_bug.cgi?id=467428 Ilgaz Öcal changed: What|Removed |Added CC||il...@ilgaz.gen.tr --- Comment #1 from Ilgaz Öcal --- I have the same issue and removed/re-added the account to make sure. I see these entries in the journal when I open the google drive folder. Operating System: openSUSE Tumbleweed 20230324 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468597] New: digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 Bug ID: 468597 Summary: digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering Classification: Applications Product: digikam Version: 8.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Bundle-Windows Assignee: digikam-bugs-n...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- Created attachment 158158 --> https://bugs.kde.org/attachment.cgi?id=158158&action=edit screenshot showing installer attempting to create a folder with 7.9.0 version numbering SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch Digikam 8.0 installer on a Windows System while having 7.9.0 installed 2. Accept the license and accept the prompt of uninstalling 7.9.x first 3. Continue with the installation OBSERVED RESULT Digikam installer prompts to create a start menu shortcuts folder with digiKam 7.9.0 version numbering EXPECTED RESULT Digikam should have created a start menu shortcuts folder with 8.0.0 version numbering. SOFTWARE/OS VERSIONS Windows: 22H2 19045.2908 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.
[digikam] [Bug 468597] digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 Ilgaz Öcal changed: What|Removed |Added CC||il...@ilgaz.gen.tr -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468597] digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 --- Comment #2 from Ilgaz Öcal --- (In reply to Maik Qualmann from comment #1) > Just tested, a correct digiKam-8.0.0-git start menu entry is created. I > suspect they had an orphaned entry from an older version still in the start > menu. > > Maik I had a Windows 10 VM image just in case. It had no Digikam version installed. I did the following: 1) Install Digikam 7.10.0 2) Install Digikam 8.0.0 Result: A Digikam 7.10.0 folder (instead of 8.0.0) was created in the Start Menu. I double checked checking the Start Menu on Windows 10, it says "Digikam 7.10.0" -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468597] digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 --- Comment #3 from Ilgaz Öcal --- Created attachment 158249 --> https://bugs.kde.org/attachment.cgi?id=158249&action=edit Actual Digikam 7.10.0 folder in Windows 10 start menu I have re-created the issue on a bare minimum/fresh Windows 10 VM by installing Digikam 7.10.0 first and Digikam 8.0.0 next. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468597] digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 --- Comment #5 from Ilgaz Öcal --- (In reply to caulier.gilles from comment #4) > After installing digiKam 7, when you install DK 8, the previous version must > be uninstalled. So DK 7 must disappear from your computer and from the > Windows Applications menu. This is the case ? Sorry for not making myself clear, as DK 8.0.0 installed, the start menu folder should be created as "Digikam 8.0.0" not "7.10.0" (previous version uninstalled) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468597] digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 --- Comment #7 from Ilgaz Öcal --- In reply to caulier.gilles from comment #6) > yes, i understand your previous explanations... > > But i ask again : 7.x is well uninstalled before to install 8.x ? Yes, I watched it being uninstalled by 8.0.0 installer. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468597] digikam 8.0.0 installer attempts to create a start menu folder with 7.9.0 version numbering
https://bugs.kde.org/show_bug.cgi?id=468597 --- Comment #13 from Ilgaz Öcal --- (In reply to Maik Qualmann from comment #11) > Hi Gilles, > > We may try to remove the old start menu entries with the same variable > ($SMPROGRAMS) that we use later for the installation. We need the "old" > version name when uninstalling. I would suggest we don't attach a version to > the start menu entry at all. > > Maik As a user, I suggest the same thing too. I am also using Creative Cloud from Adobe, applications (photoshop etc) doesn't have version number att(In reply to Maik Qualmann from comment #11) > Hi Gilles, > > We may try to remove the old start menu entries with the same variable > ($SMPROGRAMS) that we use later for the installation. We need the "old" > version name when uninstalling. I would suggest we don't attach a version to > the start menu entry at all. > > Maik Not attaching a version makes sense.(In reply to Maik Qualmann from comment #11) > Hi Gilles, > > We may try to remove the old start menu entries with the same variable > ($SMPROGRAMS) that we use later for the installation. We need the "old" > version name when uninstalling. I would suggest we don't attach a version to > the start menu entry at all. > > Maik I think not attaching a version number makes sense since some people are confused with version numbers and there is a working "self-update" mechanism under Windows now. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 --- Comment #33 from Ilgaz Öcal --- This one breaks the entire workflow, and there are several duplicates of this bug with all the technical details possible. Not a single KDE maintainer or a distribution maintainer cared about this issue. I think there is an ideological problem rather than a technical one, e.g. not supporting Google. I ended up using google-drive-ocamlfuse on all my KDE desktops for months now. Many may have switched to other desktops. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 --- Comment #21 from Ilgaz Öcal --- Without going into non-technical discussion, can't the user get a personal API key, enter that key in some field in the plugin settings and use it in an amateur (non-pro load) manner? FYI if one uses a non de-googlefied Android like Lineage+microG, they already give Google full access to their data, "as root". What happens is: KDE's target market which isn't GNU-HURD, especially paying ones from Third World countries (thanks to localized pricing) are being victimized. Disabling a small time user grabbing 10 images from their Google Photos won't really hurt Google, it will only hurt long term goals of KDE project. They will simply use Google Photos Web and get more profiled. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 481451] New: Ark crashes while dealing with 100K+ files removal on a 70GB tar archive
https://bugs.kde.org/show_bug.cgi?id=481451 Bug ID: 481451 Summary: Ark crashes while dealing with 100K+ files removal on a 70GB tar archive Classification: Applications Product: ark Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: il...@ilgaz.gen.tr CC: rthoms...@gmail.com Target Milestone: --- Application: ark (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.4-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I wanted to cleanup a "blindly created" archive with a lot of cache/vm files. In middle of "remove files from archive" operation, ark crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Ark (ark), signal: Segmentation fault [KCrash Handler] #4 0x7f4bf394696a in std::__atomic_base::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/13/bits/atomic_base.h:837 #5 std::atomic::load(std::memory_order) const (__m=std::memory_order_relaxed, this=) at /usr/include/c++/13/atomic:577 #6 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #7 QBasicAtomicPointer::loadRelaxed() const (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #8 QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) (obj=obj@entry=0x555a02f0f220) at tools/qsharedpointer.cpp:1396 #9 0x7f4bf4d298df in QWeakPointer::QWeakPointer(KJob*, bool) (ptr=0x555a02f0f220, this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:685 #10 QPointer::QPointer(KJob*) (p=0x555a02f0f220, this=) at /usr/include/qt5/QtCore/qpointer.h:62 #11 operator() (__closure=) at /usr/src/debug/kjobwidgets-5.115.0/src/kuiserverv2jobtracker.cpp:206 #12 QtPrivate::FunctorCall, QtPrivate::List<>, void, KUiServerV2JobTracker::registerJob(KJob*):: >::call (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #13 QtPrivate::Functor, 0>::call, void> (arg=, f=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #14 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #15 0x7f4bf3b25be2 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd517530e0, r=0x555a027db7c0, this=0x555a0270f610) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #16 doActivate(QObject*, int, void**) (sender=0x7f4bf4d39060 <_ZZN12_GLOBAL__N_117Q_QGS_serverProxy13innerFunctionEvE6holder.lto_priv.1>, signal_index=3, argv=0x7ffd517530e0) at kernel/qobject.cpp:3925 #17 0x7f4bf3b25be2 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffd51753200, r=0x7f4bf4d39060 <_ZZN12_GLOBAL__N_117Q_QGS_serverProxy13innerFunctionEvE6holder.lto_priv.1>, this=0x555a026a0490) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate(QObject*, int, void**) (sender=0x555a027f09c0, signal_index=5, argv=0x7ffd51753200) at kernel/qobject.cpp:3925 #19 0x7f4bf3b1e84f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x555a027f09c0, m=m@entry=0x7f4bf333e740 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffd51753200) at kernel/qobject.cpp:3985 #20 0x7f4bf332345f in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) (this=this@entry=0x555a027f09c0, _t1=..., _t2=..., _t3=...) at .moc/moc_qdbusservicewatcher.cpp:242 #21 0x7f4bf3323e8e in QDBusServiceWatcherPrivate::_q_serviceOwnerChanged(QString const&, QString const&, QString const&) (newOwner=..., oldOwner=..., service=..., this=) at qdbusservicewatcher.cpp:76 #22 QDBusServiceWatcher::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x555a027f09c0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=3, _a=_a@entry=0x7ffd51753380) at .moc/moc_qdbusservicewatcher.cpp:116 #23 0x7f4bf3324243 in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) (this=0x555a027f09c0, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffd51753380) at .moc/moc_qdbusservicewatcher.cpp:197 #24 0x7f4bf32d546b in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) (this=, object=, msg=, metaTypes=, slotIdx=) at qdbusintegrator.cpp:1001 #25 0x7f4bf3b196f0 in QObject::event(QEvent*) (this=0x555a027f09c0, e=0x7f4be804afa0) at kernel/qobject.cpp:1347 #26 0x7f4bf47a51ae in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x555a027
[plasmashell] [Bug 481881] New: minimize/maximize/close buttons are missing from Firefox
https://bugs.kde.org/show_bug.cgi?id=481881 Bug ID: 481881 Summary: minimize/maximize/close buttons are missing from Firefox Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: il...@ilgaz.gen.tr CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 166124 --> https://bugs.kde.org/attachment.cgi?id=166124&action=edit Screenshot of Firefox window SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install current KDE 6 from openSUSE Tumbleweed repos ( 20240225-2765.1 ) 2. Run wayland session 3. Launch Firefox OBSERVED RESULT Firefox displays with no buttons top right EXPECTED RESULT It should show minimize/restore/close buttons SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: LENOVO Product Name: 20L6S68A00 System Version: ThinkPad T480 ADDITIONAL INFORMATION If you right-click from panel, close option is there and it works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481881] minimize/maximize/close buttons are missing from Firefox
https://bugs.kde.org/show_bug.cgi?id=481881 Ilgaz Öcal changed: What|Removed |Added Target Milestone|1.0 |--- Product|plasmashell |kwin Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Component|general |general Version|master |git master -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481881] minimize/maximize/close buttons are missing from Firefox
https://bugs.kde.org/show_bug.cgi?id=481881 --- Comment #1 from Ilgaz Öcal --- Additionally "Eye of Gnome" (45.2) misses those buttons too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481881] minimize/maximize/close buttons are missing from Firefox
https://bugs.kde.org/show_bug.cgi?id=481881 Ilgaz Öcal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Ilgaz Öcal --- (In reply to fanzhuyifan from comment #2) > Seems like duplicate of BUG 471853. I guess we never figured out why this > happened, or how it seemed to be fixed. > > By the way what theme are you using? Sorry, forgot to add, it is the stock dark theme. I checked other themes too and no change. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481881] minimize/maximize/close buttons are missing from Firefox
https://bugs.kde.org/show_bug.cgi?id=481881 --- Comment #4 from Ilgaz Öcal --- This is very strange: the same issue appears on XFCE. Firefox and Eye of Gnome. I may try another tumbleweed install in matter of hours. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458291] New: nouveau kernel errors when plasma-wayland enabled
https://bugs.kde.org/show_bug.cgi?id=458291 Bug ID: 458291 Summary: nouveau kernel errors when plasma-wayland enabled Product: plasmashell Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: il...@ilgaz.gen.tr CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start plasma-wayland sesssion 2. Click kicker start menu 3. OBSERVED RESULT After a while it starts to freeze eventually leading to complete system freeze EXPECTED RESULT Display menu SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220823 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-1-default (64-bit) Graphics Platform: X11 Processors: 2 × Intel® Core™2 Duo CPU P7350 @ 2.00GHz Memory: 7.5 GiB of RAM Graphics Processor: NVAC Manufacturer: Apple Inc. Product Name: MacBook5,1 System Version: 1.0 ADDITIONAL INFORMATION These are the logs dmesg |grep nouveau [4.465343] nouveau :02:00.0: enabling device (0002 -> 0003) [4.499453] nouveau :02:00.0: vgaarb: deactivate vga console [4.499640] nouveau :02:00.0: NVIDIA MCP79/MCP7A (0ac180b1) [4.514577] nouveau :02:00.0: bios: version 62.79.40.00.01 [4.535604] nouveau :02:00.0: fb: 256 MiB stolen system memory [4.613119] nouveau :02:00.0: DRM: VRAM: 256 MiB [4.613126] nouveau :02:00.0: DRM: GART: 1048576 MiB [4.613132] nouveau :02:00.0: DRM: TMDS table version 2.0 [4.613135] nouveau :02:00.0: DRM: DCB version 4.0 [4.613139] nouveau :02:00.0: DRM: DCB outp 00: 01000123 00010014 [4.613143] nouveau :02:00.0: DRM: DCB outp 01: 02021232 0010 [4.613147] nouveau :02:00.0: DRM: DCB outp 02: 02021286 0f220010 [4.613151] nouveau :02:00.0: DRM: DCB conn 00: 0040 [4.613154] nouveau :02:00.0: DRM: DCB conn 01: a146 [4.616096] nouveau :02:00.0: DRM: MM: using M2MF for buffer copies [4.726667] nouveau :02:00.0: DRM: allocated 1280x800 fb: 0x5, bo (ptrval) [4.726832] fbcon: nouveaudrmfb (fb0) is primary device [4.749575] nouveau :02:00.0: [drm] fb0: nouveaudrmfb frame buffer device [4.771748] [drm] Initialized nouveau 1.3.1 20120801 for :02:00.0 on minor 0 [ 52.483350] nouveau :02:00.0: gr: magic set 0: [ 52.483363] nouveau :02:00.0: gr:00408604: 20087f02 [ 52.483368] nouveau :02:00.0: gr:00408608: 01615062 [ 52.483372] nouveau :02:00.0: gr:0040860c: 8430 [ 52.483377] nouveau :02:00.0: gr:00408610: 2922 [ 52.483381] nouveau :02:00.0: gr: TRAP_TEXTURE - TP0: 0009 [ LINEAR_MISMATCH] [ 52.483386] nouveau :02:00.0: gr: 0020 [] ch 6 [000f4a4000 plasmashell[2902]] subc 4 class 502d mthd 08dc data [ 52.487510] nouveau :02:00.0: gr: magic set 0: [ 52.487521] nouveau :02:00.0: gr:00408604: 20086b02 [ 52.487526] nouveau :02:00.0: gr:00408608: 01615062 [ 52.487531] nouveau :02:00.0: gr:0040860c: 8430 [ 52.487534] nouveau :02:00.0: gr:00408610: 2922 [ 52.487539] nouveau :02:00.0: gr: TRAP_TEXTURE - TP0: 0009 [ LINEAR_MISMATCH] [ 52.487544] nouveau :02:00.0: gr: 0020 [] ch 6 [000f4a4000 plasmashell[2902]] subc 4 class 502d mthd 08dc data [ 64.251793] nouveau :02:00.0: plasmashell[3118]: multiple instances of buffer 7 on validation list [ 64.251815] nouveau :02:00.0: plasmashell[3118]: validate_init [ 64.251818] nouveau :02:00.0: plasmashell[3118]: validate: -22 [ 64.251943] nouveau :02:00.0: plasmashell[3118]: multiple instances of buffer 7 on validation list [ 64.251953] nouveau :02:00.0: plasmashell[3118]: validate_init [ 64.251956] nouveau :02:00.0: plasmashell[3118]: validate: -22 [ 65.918078] nouveau :02:00.0: gr: DATA_ERROR 000c [INVALID_BITFIELD] [ 65.918096] nouveau :02:00.0: gr: 0010 [] ch 6 [000f4a4000 plasmashell[3118]] subc 3 class 8397 mthd 0d7c data 00086ed4 [ 65.918239] nouveau :02:00.0: gr: DATA_ERROR 000c [INVALID_BITFIELD] [ 65.918245] nouveau :02:00.0: gr: 0010 [] ch 6 [000f4a4000 plasmashell[3118]] subc 3 class 8397 mthd 198c data 013f [ 65.919127] nouveau :02:00.0: gr: DATA_ERROR 0004 [INVALID_VALUE] [ 65.919135] nouveau :02:00.0: gr: 0010 [] ch 6 [000f4a4000 plasmashell[3118]] subc 5 class 5039 mthd 022c data 00147900 [ 65.919153] nouveau :02:00.0: fifo: CACHE_ERROR - ch 6 [plasmashell[3118]] subc 0 mthd 0404
[digikam] [Bug 479156] New: Digikam crashes when I attempt to "Download&Delete all" from SD Card
https://bugs.kde.org/show_bug.cgi?id=479156 Bug ID: 479156 Summary: Digikam crashes when I attempt to "Download&Delete all" from SD Card Classification: Applications Product: digikam Version: 8.1.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- Application: digikam (8.1.0) Qt Version: 5.15.11 Frameworks Version: 5.113.0 Operating System: Linux 6.6.7-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I plug in the SDCard to a USB Card reader. it is nothing fancy a plain 64GB FAT32 one with CR2 files. I select "convert to DNG" and "generate date based albums" and click "Download&Delete All". It crashes. The crash can be reproduced sometimes. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault [KCrash Handler] #4 QReadWriteLock::tryLockForRead(int) (this=0x5606ace82bc0, timeout=-1) at thread/qreadwritelock.cpp:263 #5 0x7f07a27058a7 in QReadWriteLock::lockForRead() (this=) at thread/qreadwritelock.cpp:179 #6 0x7f07a5121bd4 in QReadLocker::relock() (this=) at /usr/include/qt5/QtCore/qreadwritelock.h:106 #7 QReadLocker::QReadLocker(QReadWriteLock*) (areadWriteLock=0x5606ace82bc0, this=) at /usr/include/qt5/QtCore/qreadwritelock.h:125 #8 Digikam::Album::childAtRow(int) const (this=0x5606ace82b90, row=28) at /usr/src/debug/digikam-8.1.0/core/libs/album/engine/album.cpp:139 #9 0x7f07a5114945 in Digikam::AbstractAlbumModel::index(int, int, QModelIndex const&) const (column=, parent=, row=28, this=0x5606b07bf100) at /usr/src/debug/digikam-8.1.0/core/libs/models/abstractalbummodel.cpp:274 #10 Digikam::AbstractAlbumModel::index(int, int, QModelIndex const&) const (this=0x5606b07bf100, row=28, column=, parent=) at /usr/src/debug/digikam-8.1.0/core/libs/models/abstractalbummodel.cpp:241 #11 0x7f07a513b3f0 in Digikam::AbstractCheckableAlbumTreeView::rowsInserted(QModelIndex const&, int, int) (end=, start=, parent=, this=) at /usr/src/debug/digikam-8.1.0/core/libs/album/treeview/abstractcheckablealbumtreeview.cpp:189 #12 Digikam::AbstractCheckableAlbumTreeView::rowsInserted(QModelIndex const&, int, int) (this=0x5606b07afc10, parent=..., start=, end=28) at /usr/src/debug/digikam-8.1.0/core/libs/album/treeview/abstractcheckablealbumtreeview.cpp:181 #13 0x7f07a29253e3 in doActivate(QObject*, int, void**) (sender=0x5606b07bdc00, signal_index=13, argv=0x7fff14f973f0) at kernel/qobject.cpp:3937 #14 0x7f07a291e0af in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5606b07bdc00, m=m@entry=0x7f07a2bc6d40 , local_signal_index=local_signal_index@entry=10, argv=argv@entry=0x7fff14f973f0) at kernel/qobject.cpp:3985 #15 0x7f07a2885ffe in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0x5606b07bdc00, _t1=..., _t2=, _t3=, _t4=...) at .moc/moc_qabstractitemmodel.cpp:592 #16 0x7f07a288ef4a in QAbstractItemModel::endInsertRows() (this=0x5606b07bdc00) at itemmodels/qabstractitemmodel.cpp:2782 #17 0x7f07a28bc595 in QSortFilterProxyModelPrivate::insert_source_items(QVector&, QVector&, QVector const&, QModelIndex const&, Qt::Orientation, bool) (this=this@entry=0x5606b07be2b0, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical, emit_signal=true) at itemmodels/qsortfilterproxymodel.cpp:950 #18 0x7f07a28c0465 in QSortFilterProxyModelPrivate::source_items_inserted(QModelIndex const&, int, int, Qt::Orientation) (this=0x5606b07be2b0, source_parent=..., start=, end=, orient=Qt::Vertical) at itemmodels/qsortfilterproxymodel.cpp:1061 #19 0x7f07a28c36bd in QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) (end=28, start=28, source_parent=..., this=0x5606b07be2b0) at itemmodels/qsortfilterproxymodel.cpp:1702 #20 QSortFilterProxyModelPrivate::_q_sourceRowsInserted(QModelIndex const&, int, int) (this=0x5606b07be2b0, source_parent=..., start=28, end=28) at itemmodels/qsortfilterproxymodel.cpp:1696 #21 0x7f07a29253e3 in doActivate(QObject*, int, void**) (sender=0x5606b07bf100, signal_index=13, argv=0x7fff14f97720) at kernel/qobject.cpp:3937 #22 0x7f07a291e0af in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5606b07bf100, m=m@entry=0x7f07a2bc6d40 , local_signal_index=local_signal_index@entry=10, argv=argv@entry=0x7fff14f97720) at kernel/qobject.cpp:3985 #23 0x7f07a2885ffe in QAbstractItemModel::rowsInserted(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0x5606b07bf100, _t1=..., _t2=, _t3=, _t
[digikam] [Bug 472494] New: Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 Bug ID: 472494 Summary: Export to Google Photos ends up with "too many requests" error Classification: Applications Product: digikam Version: 8.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Google Assignee: digikam-bugs-n...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Run Digikam 2. Select some photos, 5-8 would be OK 3. Export to Google Photos 4. Login to your Google Photos account with the opened Web Browser 5. Allow Digikam to perform displayed actions WHAT HAPPENS Error transferring https://photoslibrary.googleapis.com/v1/albums?pageSize=50 - server replied: Too Many Requests WHAT SHOULD HAPPEN Photos should be uploaded to Google Photos 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 On Reddit some users suggest that we should be able to enter our own API key to prevent the error from happening. See the comments at (archived) https://web.archive.org/web/20230722095942/https://www.reddit.com/r/FOSSPhotography/comments/151k574/digikam_export_to_google_photos_too_many_requests/?context=3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472494] Export to Google Photos ends up with "too many requests" error
https://bugs.kde.org/show_bug.cgi?id=472494 Ilgaz Öcal changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=400187 --- Comment #1 from Ilgaz Öcal --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=400187 ? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400187] Export to google photo in an existing album: bad request
https://bugs.kde.org/show_bug.cgi?id=400187 Ilgaz Öcal changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=472494 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 400187] Export to google photo in an existing album: bad request
https://bugs.kde.org/show_bug.cgi?id=400187 --- Comment #27 from Ilgaz Öcal --- (In reply to caulier.gilles from comment #26) > *** Bug 472494 has been marked as a duplicate of this bug. *** Hello I found this bug which happened to my setup a long time ago. I know the principle, you should add own albums from Digikam so a lock icon isn't displayed. The current situation is the error is displayed _right after_ authenticating therefore no albums or sign in displayed. This issue could be different. I can try things if you need. Thanks for caring. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472654] New: Clicking "Sign In" in Google Workspace dialog may lead to crash?
https://bugs.kde.org/show_bug.cgi?id=472654 Bug ID: 472654 Summary: Clicking "Sign In" in Google Workspace dialog may lead to crash? Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: il...@ilgaz.gen.tr CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.6) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.4-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.6 [CoredumpBackend] -- Information about the crash: I am not sure if it is absolutely related but today, I started to get something like "Google Workspace Login has expired, please re-login" prompts. Clicking on "Sign In" buttons. On the journal output they show up like : Jul 26 13:05:57 mbt akonadi_google_resource[5427]: org.kde.pim.google: Got error: KGAPI2::People::PersonFetchJob(0x55be42de8350) "Requested resource is forbidden.\n\nGoogle replied 'Request had insufficient authentication scopes.'" Jul 26 13:37:49 mbt akonadi_migration_agent[3252]: org.kde.pim.migration: GoogleResourceMigrator: backing up KWallet data for "ilgaz@gmail.com" Jul 26 13:37:49 mbt akonadi_migration_agent[3252]: org.kde.pim.migration: GoogleResourceMigrator: restoring KWallet data for "ilgaz@gmail.com" The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted PID: 2738 (plasmashell) UID: 1000 (ilgaz) GID: 1000 (ilgaz) Signal: 6 (ABRT) Timestamp: Wed 2023-07-26 13:41:09 +03 (34min ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ilgaz) Boot ID: b94c7240762948829c99a474fe9afab1 Machine ID: 76b4bd1e03954915b2b03f5593e4c22e Hostname: mbt Storage: /var/lib/systemd/coredump/core.plasmashell.1000.b94c7240762948829c99a474fe9afab1.2738.169036806900.zst (present) Size on Disk: 26.2M Message: Process 2738 (plasmashell) of user 1000 dumped core. Stack trace of thread 4848: #0 0x7f496a492abc __pthread_kill_implementation (libc.so.6 + 0x8fabc) #1 0x7f496a441266 raise (libc.so.6 + 0x3e266) #2 0x7f496cebdd3a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d3a) #3 0x7f496a441330 __restore_rt (libc.so.6 + 0x3e330) #4 0x7f496a492abc __pthread_kill_implementation (libc.so.6 + 0x8fabc) #5 0x7f496a441266 raise (libc.so.6 + 0x3e266) #6 0x7f496a429897 abort (libc.so.6 + 0x26897) #7 0x7f496a4297ab __assert_fail_base.cold (libc.so.6 + 0x267ab) #8 0x7f496a4394f6 __assert_fail (libc.so.6 + 0x364f6) #9 0x7f496436ed97 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4d97) #10 0x7f496436ecf8 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4cf8) #11 0x7f496436ee1c n/a (libdrm_nouveau.so.2 + 0x4e1c) #12 0x7f496436f097 n/a (libdrm_nouveau.so.2 + 0x5097) #13 0x7f496436fdb4 n/a (libdrm_nouveau.so.2 + 0x5db4) #14 0x7f49569812d4 n/a (nouveau_dri.so + 0x9812d4) #15 0x7f4956982db7 n/a (nouveau_dri.so + 0x982db7) #16 0x7f4956300e10 n/a (nouveau_dri.so + 0x300e10) #17 0x7f49563023ac n/a (nouveau_dri.so + 0x3023ac) #18 0x7f496c9daad5 _ZN16QSGBatchRenderer8Renderer17renderMergedBatchEPKNS_5BatchE (libQt5Quick.so.5 + 0x1daad5) #19 0x7f496c9dff6b _ZN16QSGBatchRenderer8Renderer13renderBatchesEv (libQt5Quick.so.5 + 0x1dff6b) #20 0x7f496c9e0826 _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5 + 0x1e0826) #21 0x7f496c9c8400 _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5 + 0x1c8400) #22 0x7f496c9c88b3 _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5 + 0x1c88b3) #23 0x7f496ca2aa93 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5 + 0x22aa93) #24 0x7f496ca9a389 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSizeS2_ (libQt5Quick.so.5 + 0x29a389) #25 0x7f496ca38937 n/a (libQt5Quick.so.5 + 0x238937) #26 0x7f496ca397df n/a (libQt5Quick.so.5 + 0x2397d
[plasmashell] [Bug 473145] New: I was filing a form on Firefox (flatpak) and plasma crashed.
https://bugs.kde.org/show_bug.cgi?id=473145 Bug ID: 473145 Summary: I was filing a form on Firefox (flatpak) and plasma crashed. Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: il...@ilgaz.gen.tr CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.6-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: I am running wayland session with nouveau current drivers. Macbook 5,1 nv9400 The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted PID: 2669 (plasmashell) UID: 1000 (ilgaz) GID: 1000 (ilgaz) Signal: 6 (ABRT) Timestamp: Tue 2023-08-08 14:33:29 +03 (43s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ilgaz) Boot ID: 05cce2b564e144d0829db3d5bd765234 Machine ID: 76b4bd1e03954915b2b03f5593e4c22e Hostname: mbt Storage: /var/lib/systemd/coredump/core.plasmashell.1000.05cce2b564e144d0829db3d5bd765234.2669.169149440900.zst (present) Size on Disk: 43.1M Message: Process 2669 (plasmashell) of user 1000 dumped core. Stack trace of thread 7606: #0 0x7f923b492abc __pthread_kill_implementation (libc.so.6 + 0x8fabc) #1 0x7f923b441266 raise (libc.so.6 + 0x3e266) #2 0x7f923de3ed3a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d3a) #3 0x7f923b441330 __restore_rt (libc.so.6 + 0x3e330) #4 0x7f923b492abc __pthread_kill_implementation (libc.so.6 + 0x8fabc) #5 0x7f923b441266 raise (libc.so.6 + 0x3e266) #6 0x7f923b429897 abort (libc.so.6 + 0x26897) #7 0x7f923b4297ab __assert_fail_base.cold (libc.so.6 + 0x267ab) #8 0x7f923b4394f6 __assert_fail (libc.so.6 + 0x364f6) #9 0x7f92352e7d97 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4d97) #10 0x7f92352e7cf8 nouveau_pushbuf_data (libdrm_nouveau.so.2 + 0x4cf8) #11 0x7f92352e7e1c pushbuf_submit (libdrm_nouveau.so.2 + 0x4e1c) #12 0x7f92352e8097 pushbuf_flush (libdrm_nouveau.so.2 + 0x5097) #13 0x7f92352e8db4 pushbuf_validate (libdrm_nouveau.so.2 + 0x5db4) #14 0x7f922690345c PUSH_VAL (nouveau_dri.so + 0x90345c) #15 0x7f92269402d1 nouveau_transfer_write (nouveau_dri.so + 0x9402d1) #16 0x7f922694058d nouveau_buffer_transfer_unmap (nouveau_dri.so + 0x94058d) #17 0x7f9226b42d93 pipe_buffer_unmap (nouveau_dri.so + 0xb42d93) #18 0x7f92262a072d pipe_buffer_write (nouveau_dri.so + 0x2a072d) #19 0x7f92262a1459 buffer_data (nouveau_dri.so + 0x2a1459) #20 0x7f92262a16a2 _mesa_buffer_data (nouveau_dri.so + 0x2a16a2) #21 0x7f923d7ccf4d _ZN16QOpenGLFunctions12glBufferDataEjlPKvj (libQt5Quick.so.5 + 0x1ccf4d) #22 0x7f923d7ced73 _ZN16QSGBatchRenderer8Renderer11uploadBatchEPNS_5BatchE (libQt5Quick.so.5 + 0x1ced73) #23 0x7f923d7e0796 _ZN16QSGBatchRenderer8Renderer6renderEv (libQt5Quick.so.5 + 0x1e0796) #24 0x7f923d7c8400 _ZN11QSGRenderer11renderSceneERK11QSGBindable (libQt5Quick.so.5 + 0x1c8400) #25 0x7f923d7c88b3 _ZN11QSGRenderer11renderSceneEj (libQt5Quick.so.5 + 0x1c88b3) #26 0x7f923d82aa93 _ZN23QSGDefaultRenderContext15renderNextFrameEP11QSGRendererj (libQt5Quick.so.5 + 0x22aa93) #27 0x7f923d89a389 _ZN19QQuickWindowPrivate16renderSceneGraphERK5QSizeS2_ (libQt5Quick.so.5 + 0x29a389) #28 0x7f923d838937 _ZN15QSGRenderThread13syncAndRenderEP6QImage (libQt5Quick.so.5 + 0x238937) #29 0x7f923d8397df _ZN15QSGRenderThread3runEv (libQt5Quick.so.5 + 0x2397df) #30 0x7f923bb03f8d operator() (libQt5Core.so.5 + 0x103f8d) #31 0x7f923b490c64 start_thread (libc.so.6 + 0x8dc64) #32 0x7f923b518550 __clone3 (libc.so.6 + 0x115550) Stack trace of thread 2712:
[kmail2] [Bug 474591] New: kmail crashes when I search for messages dated before 2022-1-1
https://bugs.kde.org/show_bug.cgi?id=474591 Bug ID: 474591 Summary: kmail crashes when I search for messages dated before 2022-1-1 Classification: Applications Product: kmail2 Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- Application: kmail (5.24.0 (23.08.0)) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.3-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: I have a full mailbox also effecting tiny hosting space I got so I am trying to archive old mails from mailbox. When I search for messages before Jan 1 of this year, it displayed several strange entries on window below and crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x7f1ecc691e0c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7f1ecc63f0e6 in raise () at /lib64/libc.so.6 #6 0x7f1ecc6268d7 in abort () at /lib64/libc.so.6 #7 0x7f1eccaacc17 in () at /lib64/libstdc++.so.6 #8 0x7f1eccabc1fc in () at /lib64/libstdc++.so.6 #9 0x7f1eccabc267 in () at /lib64/libstdc++.so.6 #10 0x7f1eccabc4c8 in () at /lib64/libstdc++.so.6 #11 0x7f1ecb2614dc in Akonadi::Item::throwPayloadException(int, int) const (this=this@entry=0x7ffc3c666358, spid=spid@entry=-1, mtid=mtid@entry=-1) at /usr/src/debug/akonadi-23.08.0/src/core/item.cpp:463 #12 0x7f1ed610a3e2 in Akonadi::Item::payload >() const (this=0x7ffc3c666358) at /usr/include/KPim5/AkonadiCore/akonadi/item.h:789 #13 0x7f1ed61356b1 in toolTip(Akonadi::Item const&) (item=...) at /usr/src/debug/kmail-23.08.0/src/searchdialog/kmsearchmessagemodel.cpp:35 #14 0x7f1ed613651b in KMSearchMessageModel::entityData(Akonadi::Item const&, int, int) const (this=0x7f1eb800da10, item=..., column=1, role=) at /usr/src/debug/kmail-23.08.0/src/searchdialog/kmsearchmessagemodel.cpp:123 #15 0x7f1ecb32da91 in Akonadi::EntityTreeModel::data(QModelIndex const&, int) const (this=0x7f1eb800da10, index=..., role=3) at /usr/src/debug/akonadi-23.08.0/src/core/models/entitytreemodel.cpp:325 #16 0x7f1ecd0b7731 in QSortFilterProxyModel::data(QModelIndex const&, int) const (this=, index=..., role=3) at itemmodels/qsortfilterproxymodel.cpp:2294 #17 0x7f1ece035ca3 in QModelIndex::data(int) const (arole=3, this=) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:460 #18 QAbstractItemDelegate::helpEvent(QHelpEvent*, QAbstractItemView*, QStyleOptionViewItem const&, QModelIndex const&) (index=, option=..., view=0x562d8172cad0, event=0x7ffc3c6668b0, this=) at itemviews/qabstractitemdelegate.cpp:401 #19 QAbstractItemDelegate::helpEvent(QHelpEvent*, QAbstractItemView*, QStyleOptionViewItem const&, QModelIndex const&) (this=, event=0x7ffc3c6668b0, view=0x562d8172cad0, option=..., index=) at itemviews/qabstractitemdelegate.cpp:385 #20 0x7f1ece020519 in QAbstractItemView::viewportEvent(QEvent*) (this=0x562d8172cad0, event=0x7ffc3c6668b0) at itemviews/qabstractitemview.cpp:1737 #21 0x7f1ecd0ed2eb in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) (receiver=receiver@entry=0x562d8285d0e0, event=event@entry=0x7ffc3c6668b0) at kernel/qcoreapplication.cpp:1190 #22 0x7f1ecdda518e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x562d802fc170, receiver=receiver@entry=0x562d8285d0e0, e=e@entry=0x7ffc3c6668b0) at kernel/qapplication.cpp:3634 #23 0x7f1ecddadd4c in QApplication::notify(QObject*, QEvent*) (this=, receiver=, e=0x7ffc3c6668b0) at kernel/qapplication.cpp:3306 #24 0x7f1ecd0ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x562d8285d0e0, event=0x7ffc3c6668b0) at kernel/qcoreapplication.cpp:1064 #25 0x7f1ecd0ed72e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #26 0x7f1ecddaacb9 in QApplication::event(QEvent*) (this=0x7ffc3c667120, e=0x7ffc3c6669c0) at kernel/qapplication.cpp:1901 #27 0x7f1ecdda519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x7ffc3c667120, e=0x7ffc3c6669c0) at kernel/qapplication.cpp:3640 #28 0x7f1ecd0ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7ffc3c667120, event=0x7ffc3c6669c0) at kernel/qcoreapplication.cpp:1064 #29 0x7f1ecd0ed72e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at kernel/qcoreapplication.cpp:1462 #30 0x7f1ecd145899 in QTimerInfoList::activateTimers() (this=0x562d80319470) at kernel/qtimerinfo_unix.cpp:643 #31 0x7f1ecd1461
[konsole] [Bug 454935] [wayland] Konsole opens with 0*0 window under wayland session
https://bugs.kde.org/show_bug.cgi?id=454935 Ilgaz Öcal changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 441712] DNG file preview shown as TV static
https://bugs.kde.org/show_bug.cgi?id=441712 Ilgaz Öcal changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 Ilgaz Öcal changed: What|Removed |Added CC||il...@ilgaz.gen.tr -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 --- Comment #3 from Ilgaz Öcal --- (In reply to djmenig from comment #1) > I found a work-around: > > 1. sudo apt update && sudo apt dist-upgrade (yes to all) > 2. Restart (I booted to a black screen, but was able to bring up the > terminal with ctrl+alt+t). > 3. sudo pkcon refresh && sudo pkcon update > > Worked for me, so hopefully it'll work for others. It sure works however a bit hard in a VM. Also I have read we should never use apt under neon I guess this looks like a good example. I am running it in a very bare VM without any additions therefore I had to take a screenshot of the _additional_ packages pkcon update requests. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 --- Comment #4 from Ilgaz Öcal --- Created attachment 161228 --> https://bugs.kde.org/attachment.cgi?id=161228&action=edit screenshot of packages to be installed by pkcon update This is what happens when you boot into blank screen because of having to run apt dist-upgrade on a Neon and run pkcon refresh && pkcon upgrade . After these installed and system rebooted, system displays and acts normally saying KDE Plasma 6.0 (apologies for sending a screenshot) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 473657] One cannot update the system
https://bugs.kde.org/show_bug.cgi?id=473657 Ilgaz Öcal changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UNMAINTAINED|--- --- Comment #11 from Ilgaz Öcal --- (In reply to Lorenzo Bettini from comment #6) > Some additional information: the update actually breaks something. For > example, `discover` had been uninstalled. Moreover, some desktop effects, > like blur, are not available anymore. I got noticed about this status. I believe it should stay open since the way it is "fixed" is a complete hack. Discover, very important part of system is missing (newbies/gui guys use it), transparency gone and several additional unknown side effects may be there. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 472229] New: OTF font files can't be displayed
https://bugs.kde.org/show_bug.cgi?id=472229 Bug ID: 472229 Summary: OTF font files can't be displayed Classification: Applications Product: kfontview Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open one of the attached files with kfontview 2. 3. OBSERVED RESULT Error displayed EXPECTED RESULT Font preview should be displayed SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230710 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.3.9-1-default (64-bit) Graphics Platform: Wayland Processors: 2 × Intel® Core™2 Duo CPU P7350 @ 2.00GHz Memory: 7.5 GiB of RAM Graphics Processor: NVAC Manufacturer: Apple Inc. Product Name: MacBook5,1 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 472229] OTF font files can't be displayed
https://bugs.kde.org/show_bug.cgi?id=472229 --- Comment #1 from Ilgaz Öcal --- Created attachment 160272 --> https://bugs.kde.org/attachment.cgi?id=160272&action=edit 'propaganda' font downloaded from https://www.dafont.com/propaganda.font -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] [kio-gdrive]Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Ilgaz Öcal changed: What|Removed |Added CC||il...@ilgaz.gen.tr --- Comment #21 from Ilgaz Öcal --- There are thousands of the following error messages on system log. I also saw signond occupying 100% of a single core for a long time after system came back from sleep. ul 19 20:12:30 mbt signonpluginprocess[13235]: Operation requested while plugin busy! - code 14 Jul 19 20:12:30 mbt kioslave5[3355]: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:30 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:30 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:30 mbt kioslave5[3355]: "Casting SessionData into subclass failed." Jul 19 20:12:30 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass failed." Jul 19 20:12:30 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:31 mbt signond[12050]: signonsessioncore.cpp 397 replyError Deprecated error code: 2 Jul 19 20:12:31 mbt signonpluginprocess[13242]: Operation requested while plugin busy! - code 14 Jul 19 20:12:31 mbt kioslave5[3355]: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:31 mbt kioslave5[3355]: "Casting SessionData into subclass failed." Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass failed." Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:31 mbt signond[12050]: signonsessioncore.cpp 397 replyError Deprecated error code: 2 Jul 19 20:12:31 mbt signonpluginprocess[13249]: Operation requested while plugin busy! - code 14 Jul 19 20:12:31 mbt kioslave5[3355]: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:31 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:31 mbt kioslave5[3355]: "Casting SessionData into subclass failed." Jul 19 20:12:31 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass failed." Jul 19 20:12:32 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:32 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:32 mbt signond[12050]: signonsessioncore.cpp 397 replyError Deprecated error code: 2 Jul 19 20:12:32 mbt signonpluginprocess[13250]: Operation requested while plugin busy! - code 14 Jul 19 20:12:32 mbt kioslave5[3355]: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:32 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:32 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:32 mbt kioslave5[3355]: "Casting SessionData into subclass failed." Jul 19 20:12:32 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass failed." Jul 19 20:12:33 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:33 mbt signond[12050]: signonsessioncore.cpp 397 replyError Deprecated error code: 2 Jul 19 20:12:33 mbt signonpluginprocess[13257]: Operation requested while plugin busy! - code 14 Jul 19 20:12:33 mbt kioslave5[3355]: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:33 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Failed to I/O session data to/from the signon daemon." Jul 19 20:12:33 mbt kioslave5[3355]: org.kde.kgapi: Unauthorized. Access token has expired or is invalid. Jul 19 20:12:33 mbt kioslave5[3355]: "Casting SessionData into subclass failed." Jul 19 20:12:33 mbt kioslave5[3355]: kf.kio.workers.gdrive: GetCredentialsJob failed: "Casting SessionData into subclass failed." Jul 19 20:12:33 mbt kioslave5[3355]: org.kde.kgap
[kdeconnect] [Bug 427952] Launched several times itself and crashed
https://bugs.kde.org/show_bug.cgi?id=427952 --- Comment #3 from Ilgaz Öcal --- Hello. Sorry I missed the initial mail. No, I can't reproduce the issue anymore. Thank you for caring. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 492040] APPIMAGE : symbol lookup error: /usr/lib64/libgnutls.so.30: undefined symbol: nettle_rsa_oaep_sha384_decrypt, version HOGWEED_6
https://bugs.kde.org/show_bug.cgi?id=492040 Ilgaz Öcal changed: What|Removed |Added CC||il...@ilgaz.gen.tr --- Comment #6 from Ilgaz Öcal --- (In reply to caulier.gilles from comment #3) > Git commit 24b0976975dcc6e7a0e06569fddd8af146b6bd21 by Gilles Caulier. > Committed on 22/08/2024 at 14:12. > Pushed by cgilles into branch 'master'. > > check if not manjaro linux 24.7 for this preloading > > M +4-2project/bundles/appimage/data/AppRun > > https://invent.kde.org/graphics/digikam/-/commit/ > 24b0976975dcc6e7a0e06569fddd8af146b6bd21 The originally reported error happened exactly the same on my openSUSE Tumbleweed (20240908) using latest weekly snapshot AppImage digiKam-8.5.0-20240909T160114-Qt6-x86-64-debug.appimage so I found this report. When I disabled (commented) the Manjaro workaround on line 170 (iffi) it got fixed and digikam launches fine. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490883] New: exiftool not found
https://bugs.kde.org/show_bug.cgi?id=490883 Bug ID: 490883 Summary: exiftool not found Classification: Applications Product: digikam Version: 8.4.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- Created attachment 172030 --> https://bugs.kde.org/attachment.cgi?id=172030&action=edit Error/warning message displayed *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Install/upgrade Digikam 8.4.0 Windows 64bit version (with qt6) to Windows 11 2. Launch it 3. OBSERVED RESULT On top of main window, I see a warning that "exiftool" wasn't found and I should set its location on preferences. EXPECTED RESULT Digikam launched without complaining. SOFTWARE/OS VERSIONS Windows: 11 23H2 (OS Build 22631.3958 ) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 6.2.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION It is possible to install exiftool binary to Windows via chocolate etc however it exceeds regular users capabilities and not that practical as on Linux/BSD. You would still have to pinpoint the directory which is C:\ProgramData\chocolatey\lib\exiftool\toolsv\exiftool -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 490883] exiftool not found (digikam 8.4.0/qt6/win64)
https://bugs.kde.org/show_bug.cgi?id=490883 Ilgaz Öcal changed: What|Removed |Added Summary|exiftool not found |exiftool not found (digikam ||8.4.0/qt6/win64) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427906] Appimage fails to launch on Wayland stating xkb
https://bugs.kde.org/show_bug.cgi?id=427906 --- Comment #16 from Ilgaz Öcal --- (In reply to caulier.gilles from comment #15) > Hi all, > > What's about the 7.9.0 pre-release available here : > > https://files.kde.org/digikam/ > > Problem still reproducible ? > > Thanks in advance > > Gilles Caulier Hello, Unfortunately it segfaults under openSUSE Tumbleweed. (In reply to caulier.gilles from comment #15) > Hi all, > > What's about the 7.9.0 pre-release available here : > > https://files.kde.org/digikam/ > > Problem still reproducible ? > > Thanks in advance > > Gilles Caulier Hello Unfortunately(In reply to caulier.gilles from comment #15) > Hi all, > > What's about the 7.9.0 pre-release available here : > > https://files.kde.org/digikam/ > > Problem still reproducible ? > > Thanks in advance > > Gilles Caulier Hello, Unfortunately under openSUSE Tumbleweed problem still seem to exist. ./digiKam-7.9.0-20221124T090601-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. -- Detected host Linux -64- -- AppImage mounted directory: /tmp/.mount_digiKa4PcQut Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libgmodule-2.0.so.0 -- Preloading shared libs: :/tmp/.mount_digiKa4PcQut/usr/lib/libavif.so.13:/usr/lib64/libxcb-dri3.so.0:/usr/lib64/libcrypto.so.1.1:/usr/lib64/libssl.so.1.1:/usr/lib64/libnss3.so:/usr/lib64/libnssutil3.so:/usr/lib64/libsmime3.so:/usr/lib64/libgmodule-2.0.so.0 xkbcommon: ERROR: failed to add default include path ././/share/X11/xkb unknown: failed to create xkb context unknown: EGL not available /tmp/.mount_digiKa4PcQut/AppRun: line 198: 2065 Segmentation fault (core dumped) digikam $@ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427906] Appimage fails to launch on Wayland stating xkb
https://bugs.kde.org/show_bug.cgi?id=427906 --- Comment #18 from Ilgaz Öcal --- (In reply to caulier.gilles from comment #17) > If you use "export XKB_CONFIG_ROOT=/usr/share/X11/xkb" before to run > AppImage as Maik said in comment #5 , this fix the problem ? > > Gilles Caulier Yes, it fixes the problem and Digikam launches fine. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433709] Drop-down menus in Kate and Kwrite appear in the wrong place on Wayland Multi-Monitor and Multi-DPI
https://bugs.kde.org/show_bug.cgi?id=433709 --- Comment #11 from Ilgaz Öcal --- The issue is resolved upstream however it is fixed in qt 6.4.0 RC1, 6.5.0 Beta1 which aren't yet relevant to KDE or other current qt5 applications. The only choice left to the user is disabling wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433709] [wayland] Drop-down menus in Kate and Kwrite appear in the wrong place on Wayland Multi-Monitor and Multi-DPI
https://bugs.kde.org/show_bug.cgi?id=433709 Ilgaz Öcal changed: What|Removed |Added Summary|Drop-down menus in Kate and |[wayland] Drop-down menus |Kwrite appear in the wrong |in Kate and Kwrite appear |place on Wayland|in the wrong place on |Multi-Monitor and Multi-DPI |Wayland Multi-Monitor and ||Multi-DPI -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433709] [wayland] Drop-down menus in Kate and Kwrite appear in the wrong place on Wayland Multi-Monitor and Multi-DPI
https://bugs.kde.org/show_bug.cgi?id=433709 --- Comment #12 from Ilgaz Öcal --- There is a workaround on Reddit saying "As a temporary fix, I found that if I align both monitors to the top, then menus are shown in the correct position. My laptop monitor is 1366x768, and the second monitor is 1920x1080, placed to the right of the laptop." https://www.reddit.com/r/kde/comments/s1fqjj/comment/hu1ecdn/?utm_source=share&utm_medium=web2x&context=3 which fixed the issue here. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 454935] [wayland] Konsole opens with 0*0 window under wayland session
https://bugs.kde.org/show_bug.cgi?id=454935 --- Comment #1 from Ilgaz Öcal --- This is somehow related to graphics hardware since the issue isn't present with Nvidia 9400 running with the nouveau driver. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 495837] New: Failed to transport message. Error during SSL handshake: error:0A00010B:SSL routines::wrong version number
https://bugs.kde.org/show_bug.cgi?id=495837 Bug ID: 495837 Summary: Failed to transport message. Error during SSL handshake: error:0A00010B:SSL routines::wrong version number Classification: Applications Product: kmail2 Version: 6.2.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- SUMMARY Kmail complains about "wrong version number" while handshaking with smtp server. Failed to transport message. Error during SSL handshake: error:0A00010B:SSL routines::wrong version number STEPS TO REPRODUCE 1. Create a mail 2. Send it 3. OBSERVED RESULT Getting Failed to transport message. Error during SSL handshake: error:0A00010B:SSL routines::wrong version number EXPECTED RESULT Mail sending success SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20241103 KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.5-2-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7300U CPU @ 2.60GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: LENOVO Product Name: 20L6S68A00 System Version: ThinkPad T480 ADDITIONAL INFORMATION The mail server is mail.ilgaz.gen.tr , user il...@ilgaz.gen.tr -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 495837] Failed to transport message. Error during SSL handshake: error:0A00010B:SSL routines::wrong version number
https://bugs.kde.org/show_bug.cgi?id=495837 --- Comment #2 from Ilgaz Öcal --- (In reply to Christophe Marin from comment #1) > (In reply to Ilgaz Öcal from comment #0) > > SUMMARY > > Kmail complains about "wrong version number" while handshaking with smtp > > server. > > Failed to transport message. Error during SSL handshake: error:0A00010B:SSL > > routines::wrong version number > > > The mail server is mail.ilgaz.gen.tr , user il...@ilgaz.gen.tr > > Does `openssl s_client mail.ilgaz.gen.tr:443` work if you run it locally? It says "Verify return code: 0 (ok)" Attaching full log in case it is needed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 495837] Failed to transport message. Error during SSL handshake: error:0A00010B:SSL routines::wrong version number
https://bugs.kde.org/show_bug.cgi?id=495837 --- Comment #3 from Ilgaz Öcal --- Created attachment 175551 --> https://bugs.kde.org/attachment.cgi?id=175551&action=edit output of 'openssl s_client mail.ilgaz.gen.tr:443' -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 502636] New: intel 620 gpu opencl support disabled on windows 11
https://bugs.kde.org/show_bug.cgi?id=502636 Bug ID: 502636 Summary: intel 620 gpu opencl support disabled on windows 11 Classification: Applications Product: digikam Version: 8.6.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: il...@ilgaz.gen.tr Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. Install the current Intel 620 GPU driver 2. Install Digikam 3. Enable opencl hardware acceleration 4. Restart and see "OpenCL No" in components information OBSERVED RESULT Displays "openCL availability: no" in components/openCV" EXPECTED RESULT It should list Intel 620 GPU and possibly (secondary) Intel i5 7xxx CPU SOFTWARE/OS VERSIONS Windows: 24H2 (26120.3671) macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I worked around this issue months ago via driver-reinstall and installing additional opencl (CPU) support from Intel. This time, it didn't change anything. I can build or test a git version if needed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 501236] OpenCV Not Detecting CUDA GPU In Latest 8.6 Weekly Build
https://bugs.kde.org/show_bug.cgi?id=501236 --- Comment #26 from Ilgaz Öcal --- Created attachment 180178 --> https://bugs.kde.org/attachment.cgi?id=180178&action=edit Intel 620 's openCL support is properly detected as well -- You are receiving this mail because: You are watching all bug changes.
