[kwin] [Bug 487126] New: kwin_wayland crashes sometimes when triggering overview effect using screen edge
https://bugs.kde.org/show_bug.cgi?id=487126 Bug ID: 487126 Summary: kwin_wayland crashes sometimes when triggering overview effect using screen edge Classification: Plasma Product: kwin Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: witte...@googlemail.com Target Milestone: --- Application: kwin_wayland () Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.9-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [CoredumpBackend] -- Information about the crash: kwin_wayland is crashing sometimes when triggering overview effect using screen edge. This only happens since yesterday or the day before yesterday so it can have to do something with an updated package in openSUSE Tumbleweed as I update the system regularly. The crash can be reproduced sometimes. -- Backtrace: Application: kwin_wayland (kwin_wayland), signal: Segmentation fault PID: 2596 (kwin_wayland) UID: 1000 (marcel) GID: 1000 (marcel) Signal: 11 (SEGV) Timestamp: Fri 2024-05-17 01:37:29 CEST (4min 43s ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_GQCWZL --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (marcel) Boot ID: e5ad182570d3494fb8358019c5194553 Machine ID: c168e24e486f45299a713c3048997284 Hostname: tuxsgaming Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.e5ad182570d3494fb8358019c5194553.2596.171590264900.zst (present) Size on Disk: 15.0M Message: Process 2596 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 2596: #0 0x n/a (n/a + 0x0) ELF object binary architecture: AMD x86-64 [New LWP 2596] [New LWP 2634] [New LWP 2632] [New LWP 2628] [New LWP 2633] [New LWP 2638] [New LWP 2637] [New LWP 2661] [New LWP 2663] [New LWP 2664] [New LWP 2665] [New LWP 2666] [New LWP 2685] [New LWP 2660] [New LWP 15814] [New LWP 2635] [New LWP 15822] [New LWP 6059] [New LWP 15818] [New LWP 8262] [New LWP 2667] [New LWP 6052] [New LWP 6058] [New LWP 8261] [New LWP 2668] [New LWP 15813] [New LWP 2636] [New LWP 15821] [New LWP 2670] [New LWP 2669] [New LWP 15823] [New LWP 15817] This GDB supports auto-downloading debuginfo from the following URLs: <https://debuginfod.opensuse.org/> Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayl'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x in ?? () [Current thread is 1 (Thread 0x7f3dc3492000 (LWP 2596))] [Current thread is 28 (Thread 0x7f3d27e006c0 (LWP 15821))] Thread 32 (Thread 0x7f3d48a006c0 (LWP 15817)): #0 0x7f3dc648effe in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7f3dc6491d40 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f3db9d10e1b in cnd_wait (mtx=0x5568852c4080, cond=0x5568852c40b0) at ../src/c11/impl/threads_posix.c:135 #3 util_queue_thread_func (input=input@entry=0x556884354010) at ../src/util/u_queue.c:290 #4 0x7f3db9d06e17 in impl_thrd_routine (p=) at ../src/c11/impl/threads_posix.c:67 #5 0x7f3dc6492bb2 in start_thread () from /lib64/libc.so.6 #6 0x7f3dc651400c in clone3 () from /lib64/libc.so.6 Thread 31 (Thread 0x7f3d26a006c0 (LWP 15823)): #0 0x7f3dc648effe in __futex_abstimed_wait_common () from /lib64/libc.so.6 #1 0x7f3dc6492065 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libc.so.6 #2 0x7f3dc6ef9493 in QWaitConditionPrivate::wait_relative (deadline=..., this=0x556883463020) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/thread/qwaitcondition_unix.cpp:92 #3 QWaitConditionPrivate::wait (deadline=..., this=0x556883463020) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/thread/qwaitcondition_unix.cpp:100 #4 QWaitCondition::wait (this=, mutex=0x5568834d4118, deadline=...) at /usr/src/debug/qtbase-everywhere-src-6.7.0/src/corelib/thread/qwaitcondition_unix.cpp:180 #5 0x7f3dc6ef3dc9
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 --- Comment #16 from Marcel Hasler --- Thanks! Will there be a 6.1.1 release to fix this? I see that Arch already provides a patched version, but many others will likely be affected by this regression, as well. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 --- Comment #7 from Marcel Hasler --- I've assigned the bug to the author of the commit (I hope that's okay to do). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507
--- Comment #6 from Marcel Hasler ---
Looking at the code some more, it seems that many functions explicitly check
for both cases, e.g. in StorageAccess::filePath():
const QString path = clearTextPath();
if (path.isEmpty() || path == "/") {
QString();
}
Other functions, such as StorageAccess::setup() (which I think might be the
culprit here), don't:
if (m_device->isEncryptedContainer() && clearTextPath().isEmpty()) {
return requestPassphrase();
} else {
return mount();
}
Perhaps it would make sense to refactor this check into an own function (e.g.
StorageAccess::isUnlocked()).
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 Marcel Hasler changed: What|Removed |Added Assignee|unassigned-b...@kde.org |k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 Marcel Hasler changed: What|Removed |Added Version|unspecified |6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 --- Comment #4 from Marcel Hasler --- Downgrading Solid back to 6.0.0 fixes the issue. Looking at the change log, there's really only one commit (https://invent.kde.org/frameworks/solid/-/commit/f000b6e99f741c66744a8995f6521e9158ebf289). I think the problem here is that the property "CleartextDevice" returned from the new code defaults to '/' if the device hasn't been unlocked yet, whereas the old code returned an empty string, which clients apparently expect. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 Marcel Hasler changed: What|Removed |Added CC||mahas...@gmail.com --- Comment #1 from Marcel Hasler --- I can confirm this. It works fine on my desktop which still has Frameworks 6.0.0 but is broken on my laptop after upgrading to 6.1.0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480367] Desktop sluggish/laggy after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=480367 --- Comment #6 from Marcel Hasler --- I investigated this issue a bit further and at least in my case, running under X11, it turned out to be related to TearFree rendering. Without any custom configuration in place, i.e. 'xrandr --props' reports 'TearFree: auto', I get the behavior as described above. As I understand it, since I don't have any scaling or rotation enabled, this means TearFree is actually disabled. If I temporarily enable TearFree with 'xrandr --output eDP --set TearFree on', the problem goes away immediately and the FPS counter shows approx. 120 Hz, as expected. If I disable it again the problem returns just as before with the FPS capped to 60 Hz. What's even stranger is that if I suspend my laptop just once with TearFree on, the problem goes away permanently, even if I then disable it again, at least until I log out and back in. So the solution for me is to enable TearFree permanently by creating a configuration file /etc/X11/xorg.conf.d/20-amdgpu.conf with 'Option "TearFree" "true"'. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480367] Desktop sluggish/laggy after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=480367 --- Comment #5 from Marcel Hasler --- BTW, I also have a ThinkPad E14 with a 60 Hz display and Ryzen 7 5825U / Radeon Graphics here running an almost identical system which does *not* show this behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480367] Desktop sluggish/laggy after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=480367 --- Comment #4 from Marcel Hasler --- Created attachment 165787 --> https://bugs.kde.org/attachment.cgi?id=165787=edit X11 info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480367] Desktop sluggish/laggy after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=480367 --- Comment #3 from Marcel Hasler --- Created attachment 165786 --> https://bugs.kde.org/attachment.cgi?id=165786=edit KWin info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480367] Desktop sluggish/laggy after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=480367 Marcel Hasler changed: What|Removed |Added CC||mahas...@gmail.com --- Comment #2 from Marcel Hasler --- Same here on a Ryzen 7 7840HS / Radeon 780M. Simply restarting compositing by hitting ALT+SHIFT+F12 twice makes thing work again as expected. This is on X11. I have a 120 Hz display. Looking at the FPS counter I normally see a refresh rate between 100-115 (which I know shouldn't be considered reliable). After waking from suspend the counter is stuck at 60 and all animations/movements are slow and jerky. 3D apps like glxgears still report 120 FPS, though. I have also tried setting the display to 60 Hz but get the same result, just with the counter stuck at 30. I also tried uninstalling xf86-video-amdgpu and using the modesetting driver instead, but that makes no difference. I'll attach my KWin/X11 info. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 Marcel Oliver changed: What|Removed |Added CC||marcel.oli...@ku.de --- Comment #22 from Marcel Oliver --- I can confirm that this is mouse-related. Logitech Anywhere 2S works, Logitech Anywhere 3 does not, even though it worked for years. I am using okular on Fedora Cinnamon, an update last week broke it. As far as I can tell, the breakage was between okular 23.04.3 and 23.08.3. The issue is annoying, and specific to okular. So even though the issue is hardware-related, it seems to me that it is okular which is buggy. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476792] FEATURE REQUEST: Please add a tablet-mode toggle to the system-tray
https://bugs.kde.org/show_bug.cgi?id=476792 Marcel changed: What|Removed |Added CC||misterx.m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476792] New: FEATURE REQUEST: Please add a tablet-mode toggle to the system-tray
https://bugs.kde.org/show_bug.cgi?id=476792 Bug ID: 476792 Summary: FEATURE REQUEST: Please add a tablet-mode toggle to the system-tray Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: misterx.m...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 I am owning a 2-in-1 laptop which seems to not expose the folded state (aka. tablet-mode) through the linux kernel. Therefore I have to enable/disable tablet-mode manually in the system settings every time I am using it in folded state. As I am most certainly not the only owner of such a device I think it would be a nice usability feature being able to quickly toggle tablet-mode on/off of from the system tray (like it's already done with the on screen keyboard). Therefore I'd like to propose adding such a feature to the system tray. I think it can/should be disabled by default but every owner of a 2-in-1 device which does not expose the folded state, can enable the feature thus switch more quickly and painless between tablet-mode on/off. Thanks Marcel -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 377216] qapt-deb-installer Window Locks Keyboard Input
https://bugs.kde.org/show_bug.cgi?id=377216 --- Comment #3 from Marcel Partap --- Why (and by whom?) was the qapt project archived? It doesn't show on https://invent.kde.org/system/libqapt/activity ... -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 448903] Allow the user to set default behavior regarding autoreload and automatic close
https://bugs.kde.org/show_bug.cgi?id=448903 Marcel Martin changed: What|Removed |Added CC||m...@freenet.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426178] Albumfilter on Unknown faces does not work
https://bugs.kde.org/show_bug.cgi?id=426178 --- Comment #7 from Marcel --- Yes, the problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416003] Scrollbar width in Breeze theme
https://bugs.kde.org/show_bug.cgi?id=416003 Marcel Partap changed: What|Removed |Added Resolution|FIXED |--- CC||mpar...@gmx.net Status|RESOLVED|REOPENED --- Comment #12 from Marcel Partap --- The tiny-scrollbars-everywhere trend continues to inflict pain on a non-miniscule percentage of computer users. Does it need years of debating to give people some choice here? a very simple settings widget would empower thousands to more comfortably use KDE.. Clearly the problem is not resolved yet (a setting was put in, but then removed again). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425619] Application: akonadi_imap_resource_5 (akonadi_imap_resource), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425619 --- Comment #10 from Marcel --- Created attachment 158476 --> https://bugs.kde.org/attachment.cgi?id=158476=edit New crash information added by DrKonqi akonadi_imap_resource (5.23.0 (23.04.0)) using Qt 5.15.9 I woke up my device from suspend to RAM and pressed "Check Mail" in KMail. -- Backtrace (Reduced): #4 QHash::findNode(QByteArray const&, unsigned int*) const (ahp=, akey=, this=) at /usr/src/debug/akonadi-23.04.0/src/core/attributestorage.cpp:69 #5 QHash::contains(QByteArray const&) const (akey=, this=) at /usr/include/qt5/QtCore/qhash.h:920 #6 Akonadi::AttributeStorage::hasAttribute(QByteArray const&) const (type=..., this=0x40) at /usr/src/debug/akonadi-23.04.0/src/core/attributestorage.cpp:69 #7 Akonadi::Collection::hasAttribute(QByteArray const&) const (this=this@entry=0x557b6d344140, type=...) at /usr/src/debug/akonadi-23.04.0/src/core/collection.cpp:163 #8 0x7ff81da45909 in Akonadi::Collection::hasAttribute() const (this=0x557b6d344140) at /usr/src/debug/akonadi-23.04.0/src/core/collection.h:595 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425619] Application: akonadi_imap_resource_5 (akonadi_imap_resource), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425619 Marcel changed: What|Removed |Added CC||k...@retux.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448231] Crash on closing Digikam
https://bugs.kde.org/show_bug.cgi?id=448231 --- Comment #5 from Marcel --- Hi Gil I could not reproduce it, but I now have a different operating system and another computer. I think you can close it for now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468126] New: the pen stops working for no reason
https://bugs.kde.org/show_bug.cgi?id=468126 Bug ID: 468126 Summary: the pen stops working for no reason Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: marceldob2...@gmail.com Target Milestone: --- Everything was working just fine, then out of nowhere my pen stoped working. I can click on things in the program and outside of krita my pen is owrking just fine. Its not the pen issue, because my maus also isnt working. Other files work fine, but this one drawing does not and i dont know what to do. I saved the file and tried again but it still didnt work. Thats not the first time this happend to me and its really frustrating. Please help :c its on windows 10 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 449073] WebEngine KPart does not accept drag'n'drop on main view area
https://bugs.kde.org/show_bug.cgi?id=449073 --- Comment #4 from Marcel Partap --- Hey Stefano, thanks a lot for implementing that! For me though, links dropped on a split view will open in a new tab, not in that view. I assume it doesn't for you? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458302] New: Korganizer crashses when dismissing an alert
https://bugs.kde.org/show_bug.cgi?id=458302 Bug ID: 458302 Summary: Korganizer crashses when dismissing an alert Product: kde Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: marcel-...@dyskolus.com Target Milestone: --- Application: akonadi_google_resource (5.20.3 (22.04.3)) Qt Version: 5.15.4 Frameworks Version: 5.96.0 Operating System: Linux 5.18.0-3-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux bookworm/sid DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Korganizer with Google plugin is showing a series of old alerts and crashes when dismiss on the first popup is clicked. The crash can be reproduced every time. -- Backtrace: Application: Google Groupware (marcel.ammerl...@gmail.com) (akonadi_google_resource), signal: Aborted [KCrash Handler] #4 0x7fdabd88983c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7fdabd83da52 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7fdabd828469 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7fdabe090c59 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdabe09005e in qt_assert_x(char const*, char const*, char const*, int) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fdabfecaeb8 in Akonadi::ResourceBase::retrieveItem(Akonadi::Item const&, QSet const&) () from /lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #10 0x7fdabfee5717 in ?? () from /lib/x86_64-linux-gnu/libKF5AkonadiAgentBase.so.5 #11 0x7fdabe2e89af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fdabf842085 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #13 0x7fdabf84356b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #14 0x7fdabe2dd2a0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fdabef62f4e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fdabe2b1618 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fdabe2b45b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fdabe309ae3 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fdabc322bc9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fdabc322e58 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7fdabc322eec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fdabe3091c6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7fdabe2b009b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7fdabe2b8206 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x555b96a453f2 in ?? () #26 0x7fdabd82920a in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #27 0x7fdabd8292bc in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #28 0x555b96a3a5fa in ?? () [Inferior 1 (process 1900) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'akonadi_google_resource' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 456504] New: When using the "double click to open files" setting, you need to click extremely fast on the deskop
https://bugs.kde.org/show_bug.cgi?id=456504 Bug ID: 456504 Summary: When using the "double click to open files" setting, you need to click extremely fast on the deskop Product: Active Window Control Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: marcelhentschel...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Use a high frame rate Monitor (144hz in my case) 2. Activate double click to open files and folders in the "General Behaviour"-Settings OBSERVED RESULT You need to double click extremly fast with files located on the desktop. (the higher the refresh rate, the faster you have to double click) EXPECTED RESULT The same click speed as on Dolphin. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 11 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-15-amd64 OS Type: 64-bit Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 377216] qapt-deb-installer Window Locks Keyboard Input
https://bugs.kde.org/show_bug.cgi?id=377216 Marcel Partap changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||mpar...@gmx.net --- Comment #2 from Marcel Partap --- This is a grave issue for users of f.e. a fullscreen terminal, as the qapt-installer locks on to keyboard focus.. very hard to get out of this situation (kill terminal via ssh, switch to VT or just shoot down X11 with CTRLALTBACKSPACE). It seems https://invent.kde.org/system/libqapt/-/blame/master/utils/qapt-deb-installer/DebInstaller.cpp#L151 is the cause, I've opened a merge request at https://invent.kde.org/system/libqapt/-/merge_requests/4 .. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451367] Light and Dark theme settings put GTK apps in the opposite color mode from what's expected
https://bugs.kde.org/show_bug.cgi?id=451367 Marcel changed: What|Removed |Added CC||marcmatias...@gmail.com --- Comment #2 from Marcel --- Hello! About this problem I notice that when we change the theme in Settings > Quick Settings menu to Light, ~/.kde4/share/config/kdeglobals update "[General] ColorScheme" as "BreezeDark" and vice versa. Maybe GTK is getting this value as a reference to change theme color? After logout and login, "[General] ColorScheme" in ~/.kde4/share/config/kdeglobals shows the actual theme selected correctly and GTK apps getting the right theme. I hope this helps in some way, Thanks! Operating System that i tested: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 451928] New: Vector OSM Theme: capital names only rendered on high zoom levels
https://bugs.kde.org/show_bug.cgi?id=451928 Bug ID: 451928 Summary: Vector OSM Theme: capital names only rendered on high zoom levels Product: marble Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: mpar...@gmx.net Target Milestone: --- Created attachment 147741 --> https://bugs.kde.org/attachment.cgi?id=147741=edit screenshot of marble showing no capital name SUMMARY When using the vector OSM tiles, capital names seem to show only on higher zoom levels. Smaller city names are shown before. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets
https://bugs.kde.org/show_bug.cgi?id=439472 Marcel changed: What|Removed |Added CC||witte...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets
https://bugs.kde.org/show_bug.cgi?id=439472 --- Comment #12 from Marcel --- Created attachment 147523 --> https://bugs.kde.org/attachment.cgi?id=147523=edit New crash information added by DrKonqi latte-dock (0.10.8) using Qt 5.15.2 I tried to add a widget to a SideBar. The first time the widget selector is appearing and directly disappearing, if I try to open this a second time this crash is happening. -- Backtrace (Reduced): #4 QScopedPointer >::operator->() const (this=0x8) at /usr/include/qt5/QtCore/qscopedpointer.h:116 [...] #7 QSGTexture::setFiltering(QSGTexture::Filtering) (this=this@entry=0x0, filter=QSGTexture::Linear) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.2.x86_64/src/quick/scenegraph/coreapi/qsgtexture.cpp:576 #8 0x7fb202ba6a8b in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) (this=0x5579301f8d00, state=..., newEffect=0x557934e8b2b0, oldEffect=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.2.x86_64/src/quick/scenegraph/util/qsgtexturematerial.cpp:90 #9 0x7fb202b8da24 in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) (batch=, this=0x557934e85200) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.2.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3097 #10 QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) (this=0x557934e85200, batch=0x5579339ce010) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-1.2.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3026 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446800] Feature Request: Please add a functionality for selecting multiple windows in the task manager
https://bugs.kde.org/show_bug.cgi?id=446800 --- Comment #2 from Marcel --- (In reply to Nate Graham from comment #1) > The Task Manager doesn't really have any kind of selection model or UI at > all, so I think bolting this onto it would be quite strange. No can do, > sorry. That's unfortunate but understandable. My thought was that because the task manager already allowed closing multiple windows of one program (if they are grouped) it would be easy to extend this onto arbitrary windows. Of course I did not think about the need to implement a selection model for this :-/ (Nevertheless I think that being able to select and close multiple windows at once is a useful feature. Maybe it would be a suitable feature for the new overview effect) Have a nice day Marcel -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 449073] New: WebEngine KPart does not accept drag'n'drop on main view area
https://bugs.kde.org/show_bug.cgi?id=449073 Bug ID: 449073 Summary: WebEngine KPart does not accept drag'n'drop on main view area Product: konqueror Version: 21.08.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: mpar...@gmx.net Target Milestone: --- A very useful technique (many years back) to check a list of links used to be to split a konqueror window into two views, then dragging links from one view to the other sequentially. This doesn't work anymore with the WebEngine KPart because it does not accept link drops on its main view area. None of the other browser seem to support (arbitrarily!) splitting a window into sub-views, so instead of that simple work-flow to sequentially check links, opening tabs is the dominant method bringing in the scourge of tab overkill into most IT persons life. Oh please someone make this work again .. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448231] Crash on closing Digikam
https://bugs.kde.org/show_bug.cgi?id=448231 --- Comment #2 from Marcel --- In the backtrace I can't see any evidence that it comes from Digikam itself. Do you see something? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448231] Crash on closing Digikam
https://bugs.kde.org/show_bug.cgi?id=448231 --- Comment #1 from Marcel --- Created attachment 145309 --> https://bugs.kde.org/attachment.cgi?id=145309=edit Error message on error without gdb -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448231] New: Crash on closing Digikam
https://bugs.kde.org/show_bug.cgi?id=448231 Bug ID: 448231 Summary: Crash on closing Digikam Product: digikam Version: 7.5.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: maes...@gmail.com Target Milestone: --- Created attachment 145308 --> https://bugs.kde.org/attachment.cgi?id=145308=edit backtrace with gdb SUMMARY With the newest self build version from digikam (c44258326a5270ad2b68ba14830ba3350038b6d6) and with asan enabled the application Digikam crashes always during the terminating process. *** STEPS TO REPRODUCE 1. Start Digikam and wait unit picture scan is started 2. Close Digikam 3. Error occurs OBSERVED RESULT EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426178] Albumfilter on Unknown faces does not work
https://bugs.kde.org/show_bug.cgi?id=426178 --- Comment #5 from Marcel --- Hi Gilles Thank you. I also wish you a happy new year. I checked the behavior again with a new version. Unfortunately it is still pretty much the same as when I reported it. I See that it is not that easy to solve as the filter must be applied to a virtual filter and not to one in the picture it self ( see comment from Maik). Anyway, I see it as a but as the filter option "unknown" is shown. One quick fix would be to hide that option but I definitely would like to see the filtered images. I tried to fix it by my own but did not succeed and in the resent months I was short in time. I changed my job and got a new child. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427203] Asan error on closing digikam
https://bugs.kde.org/show_bug.cgi?id=427203 --- Comment #8 from Marcel --- Hi Gilles I checked it with the pre-release bundle `digiKam-7.5.0-20220109T135438-x86-64.appimage` and couldn't see the asan message any more. If I remember right this pre-release does not include the asan, so I compiled the sources from the hash `c44258326a5270ad2b68ba14830ba3350038b6d6` with asan enables to be sure the error is gone. I could not see that error ether but Digikam on the self build version Digikam did always crash on closing. Error: ``` digikam.general: scan mode: ScanDeferredFiles digikam.general: total scan value : 74609 digikam.general: total scan value : 76233 digikam.database: items to tag () digikam.database: Complete scan took: 71299 msecs. digikam.general: Event is dispatched to KDE desktop notifier digikam.general: Cancel Main Thread digikam.general: Cancel Main Thread malloc_consolidate(): invalid chunk size KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = digikam path = /usr/bin pid = 270017 KCrash: Arguments: /usr/bin/digikam KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 With 1000s of "[warn] epoll_wait: Bad file descriptor" following after a while ``` Should I open a new bug for this or is it something I do wrong? -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 448131] New: For some controls, the mouse pointer needs to be left or up, in relation of the control being clicked
https://bugs.kde.org/show_bug.cgi?id=448131 Bug ID: 448131 Summary: For some controls, the mouse pointer needs to be left or up, in relation of the control being clicked Product: wacomtablet Version: 3.2.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: m...@marcelvanthoor.nl 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 Dolphin 2. Try to resize the width of the Places panel using the Wacom pen (or click a file name) OR 1. Open the Graphic Tablet window. 2. Try to click one of the tabs OBSERVED RESULT Observe that the mouse pointer changes into an arrow just left of the resize line (or you need to click "too high" to select the file) EXPECTED RESULT Expect that the mouse pointer changes to a resize arrow when exactly on the resize line. Expect the file name to be clicked when the mouse pointer is right over it in the middle. Same for the tabs in the Graphic Tablet window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Stable Bullseye KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Everything is working fine in Krita itself. When pointing at a control the mouse pointer behaves as expected. Clicks happen where expected, and the pen draws where expected. It is the KDE main user interface where, for some controls, the mouse pointer needs to be offset to the left or the top to click where expected. This is true for resizing the Places panel in Dolphin (needs offset to the left), but not when resizing the entire window to be bigger by dragging the left window edge. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 Marcel Dischinger changed: What|Removed |Added CC||mds...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446800] Feature Request: Please add a functionality for selecting multiple windows in the task manager
https://bugs.kde.org/show_bug.cgi?id=446800 Marcel changed: What|Removed |Added CC||misterx.m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446800] New: Feature Request: Please add a functionality for selecting multiple windows in the task manager
https://bugs.kde.org/show_bug.cgi?id=446800 Bug ID: 446800 Summary: Feature Request: Please add a functionality for selecting multiple windows in the task manager Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: misterx.m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Dear KDE developers, when using plasma I often find myself in a situation where I want to close multiple windows or move them to a different virtual desktop using the task manager at once. (note: I refer to the non-icon-only task manager) Unfortunately I have not found a way to achieve this. Therefore I propose to add the ability of Ctrl+clicking multiple windows in the task manager for selecting them (like one can select multiple files in dolphin using this shortcut) and make it possible to right click the selection for then using a tooltip to choose an action to be performed on those windows (e.g. close, move to virtual desktop / activity). I believe that I am not the only one whose workflow would be improved by this feature. Thanks Marcel P.S.: If this functionality already exists, it would be nice if someone could tell me the shortcut or how to enable it. SYSTEM INFORMATION Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.7-1-siduction-amd64 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444358] When printing multiple pages per sheet (such as 2X2) the described order of pages is misleading when printing in landscape mode
https://bugs.kde.org/show_bug.cgi?id=444358 Marcel changed: What|Removed |Added CC||misterx.m...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444358] New: When printing multiple pages per sheet (such as 2X2) the described order of pages is misleading when printing in landscape mode
https://bugs.kde.org/show_bug.cgi?id=444358 Bug ID: 444358 Summary: When printing multiple pages per sheet (such as 2X2) the described order of pages is misleading when printing in landscape mode Product: okular Version: 21.08.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: misterx.m...@gmail.com Target Milestone: --- SUMMARY When trying to print multiple landscapes pdf pages on one sheet of paper also in landscape format the option to choose the order of pages is still behaving like it's in portrait mode. STEPS TO REPRODUCE 1. Open a multiple pages landscape PDF (such as a presentation) in okular 2. Open the printing dialog, go to properties. 3. set the orientation of the page to landscape (if not already set) 4. choose to print 4(2X2) pages per sheet, also choose page order "left to right, top to bottom" 5. print the document OBSERVED RESULT The printed result has a page order which looks like this ___ | 3 | 1 | |__|__| | 4 | 2 | |__|__| EXPECTED RESULT I expected it to look like this and I assume that this is the behaviour an average user would expect. ___ | 1 | 2 | |__|__| | 3 | 4 | |__|__| SOFTWARE/OS VERSIONS Operating System: siduction (debian unstable based) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-siduction-amd64 (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon™ Vega 8 Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 443654] New: Split-views do not accept Link drops
https://bugs.kde.org/show_bug.cgi?id=443654 Bug ID: 443654 Summary: Split-views do not accept Link drops Product: konqueror Version: 21.08.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: mpar...@gmx.net Target Milestone: --- When splitting a web view and trying to drag a link from one into the other pane, a forbidden-cursor indicates that the view does not accept the link as drop target. This prevents using a split view to sequentially check a list of links from a search result f.e., which used to work very fine back in the days of KDE 3 .. Seeing as I couldn't find any other modern browser with splittable tabs, it would be great if this work flow could be made to work again.. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443256] New: discover shows wrong version information in update list
https://bugs.kde.org/show_bug.cgi?id=443256 Bug ID: 443256 Summary: discover shows wrong version information in update list Product: Discover Version: 5.22.90 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Flatpak Backend Assignee: lei...@leinir.dk Reporter: witte...@googlemail.com CC: aleix...@kde.org, jgrul...@redhat.com Target Milestone: --- Created attachment 142118 --> https://bugs.kde.org/attachment.cgi?id=142118=edit screenshot of discover update list SUMMARY For packages installed using flatpak discover shows wrong version information, app are always updating from "stable" and runtime updates are mixed up if different branches of the same runtime are installed. OBSERVED RESULT See the attached screenshot. The CLI returns another list: flatpak list Name Application ID VersionZweigInstallation Discordcom.discordapp.Discord 0.0.15 stable system Spotifycom.spotify.Client 1.1.55.498.gf9a83c60 stable system Synology Drive com.synology.SynologyDrive 3.0.1 stable system Freedesktop Platform org.freedesktop.Platform 20.08.15 20.08system defaultorg.freedesktop.Platform.GL.default 19.08system Mesa org.freedesktop.Platform.GL.default 21.1.7 20.08system openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system Freedesktop SDKorg.freedesktop.Sdk 19.08.14 19.08system Freedesktop SDKorg.freedesktop.Sdk 20.08.15 20.08system Breeze Gtk theme org.gtk.Gtk3theme.Breeze 3.22 system Breeze Gtk theme org.gtk.Gtk3theme.Breeze-Dark 3.22 system Signal Desktop org.signal.Signal 5.17.2 stable system flatpak remote-ls --updates Name Application ID Version Zweig Architektur Discordcom.discordapp.Discord 0.0.16 stable x86_64 Spotifycom.spotify.Client 1.1.68.632.g2b11de83 stable x86_64 Signal Desktop org.signal.Signal 5.18.0 stable x86_64 EXPECTED RESULT Show the correct installed version and do not show runtime updates that are not available SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 426955] Seg fault on QMessageBox because of exceeding canvas size
https://bugs.kde.org/show_bug.cgi?id=426955 Marcel changed: What|Removed |Added Resolution|WAITINGFORINFO |LATER --- Comment #3 from Marcel --- Unfortunately I don't have the system from a year ago any more. Currently I can't reproduce the error. I get errors earlier. Still working on it and update here if I can reproduce it again. If so I will have to compile Breeze from source. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #12 from Marcel --- Thank you very much for your work. I was using the discover program on fedora and had the misconception that from the two versions viewed, that both were installed. Instead, only the fedora version was. After some fiddling, I was able to install the flatpak version too which kept viewing the preview images after several restarts. Now, something different. The new version seems to have a different location of the config, can I have the previous puzzles set up back, or is that config too different to do that. Also, I am missing the irregular puzzle cutter which I also loved to use. (pointers to other issues perhaps, or plugins) Anyways, so far so good. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #10 from Marcel --- Created attachment 140629 --> https://bugs.kde.org/attachment.cgi?id=140629=edit base64 encoded palapeli-collectionrc I tried to attach the palapeli-collectionrc but it failed with an error, so, I try it this way. It is a base64 encoded version of the rc file. This rc is generated in a fresh account, started palapeli and added one image. After that, I restarted the program two times after which the images are gone. Hopefully, you find something in there. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #8 from Marcel --- Btw, all images were jpeg images. So, I've also tried to convert one image to png before making a puzzle. The same sad end takes place after two restarts. No preview images visible! -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #7 from Marcel --- Done the following; - Start out in a new account with a fresh palapeli; everything looks fine - Add some puzzles kf.notifications: Failed to play sound with canberra: Not available kf.notifications: Failed to play sound with canberra: Not available kf.itemviews: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! kf.itemviews: User of KWidgetItemDelegate should not delete widgets created by createItemWidgets! kf.itemviews: User of KWidgetItemDelegate should not delete widgets created ... Images are visible - stop and start again libpng warning: known incorrect sRGB profile libpng warning: profile matches sRGB but writing iCCP instead Images are still visible - again, stop and start libpng error: IDAT: invalid code -- missing end-of-block libpng warning: iCCP: CRC error libpng warning: iCCP: incorrect data check libpng error: bad adaptive filter value libpng error: IHDR: CRC error libpng warning: iCCP: CRC error libpng warning: iCCP: invalid distance too far back libpng error: bad adaptive filter value libpng error: bad adaptive filter value libpng error: bad adaptive filter value libpng warning: iCCP: CRC error ... -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 438633] gwenview segfault when cropping
https://bugs.kde.org/show_bug.cgi?id=438633 --- Comment #2 from Marcel Bergeron --- The problem has gone away, I did'nt notice when. As it was, trying to crop any image produced a crash. Le mar. 3 août 2021 à 06:43, postix a écrit : > https://bugs.kde.org/show_bug.cgi?id=438633 > > postix changed: > >What|Removed |Added > > > CC||pos...@posteo.eu > > --- Comment #1 from postix --- > Do you have a sample file? I cannot reproduce it on openSUSE Tumbleweed > 20210730 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #6 from Marcel --- I'm not sure this helps, the png libs on fedora 33; libpng-devel-1.6.37-6.fc33.x86_64 libpng-1.6.37-6.fc33.i686 libpng12-1.2.57-12.fc33.x86_64 libpng-1.6.37-6.fc33.x86_64 I've removed libpng12* and have tried to downgrade png libs but it did not give better results -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 --- Comment #5 from Marcel --- To be more precise, a new puzzle did show its icon next to the other invisible ones. After two restarts these were gone too. The same type of errors as shown in the first report of this bug issue. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 255209] Show progress of puzzles in the puzzlelist
https://bugs.kde.org/show_bug.cgi?id=255209 Marcel changed: What|Removed |Added CC||mt1...@gmail.com --- Comment #2 from Marcel --- Also because of bug 433403 - 'Preview puzzle images are not shown', and because I've used the same name for many puzzles (more like categories), I have to click on almost every puzzle to see if it is finished or not. Another problem with using the same name, is that the order changes between startups. So one time let's say, a building puzzle, is e.g. at the 3rd location then after a restart, it is at the 10th. To speed up puzzle display, categories might be useful. Can also display somewhat larger icons because not all puzzles are shown at once. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 433403] Preview puzzle images are not shown
https://bugs.kde.org/show_bug.cgi?id=433403 Marcel changed: What|Removed |Added CC||mt1...@gmail.com --- Comment #3 from Marcel --- I'm using version 2.1.21043 on Fedora 33. Palapeli does not show any images either. Tried to reinstall but no change. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 438633] New: gwenview segfault when cropping
https://bugs.kde.org/show_bug.cgi?id=438633 Bug ID: 438633 Summary: gwenview segfault when cropping Product: gwenview Version: 21.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: bergeron.mar...@gmail.com Target Milestone: --- Application: gwenview (21.04.2) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.12.9-1-default x86_64 Windowing System: X11 Drkonqi Version: 5.22.0 Distribution: "openSUSE Tumbleweed" -- Information about the crash: open any image and clic to crop, segmentation fault results The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fc136d63a40 (LWP 12644))] [KCrash Handler] #6 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x454545454545454d) at /usr/include/c++/11/bits/atomic_base.h:836 #7 std::atomic::load (__m=std::memory_order_relaxed, this=0x454545454545454d) at /usr/include/c++/11/atomic:570 #8 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #9 QBasicAtomicPointer::loadRelaxed (this=0x454545454545454d) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 #10 QObjectPrivate::isSignalConnected (this=this@entry=0x561b646bfed0, signalIndex=7, checkDeclarative=checkDeclarative@entry=true) at kernel/qobject.cpp:459 #11 0x7fc13a8531fc in QVariantAnimationPrivate::setCurrentValueForProgress (this=0x561b646bfed0, progress=) at animation/qvariantanimation.cpp:291 #12 0x7fc13a850493 in QAbstractAnimation::setCurrentTime (this=0x561b646bfcf0, msecs=17) at animation/qabstractanimation.cpp:1326 #13 0x7fc13a8505d4 in QAnimationTimer::updateAnimationsTime (this=0x561b641a66a0, delta=17) at animation/qabstractanimation.cpp:608 #14 0x7fc13a84ef0b in QUnifiedTimer::updateAnimationTimers (this=0x561b642caa80, currentTick=) at animation/qabstractanimation.cpp:324 #15 0x7fc13a850c1d in QAnimationDriver::advanceAnimation (this=, timeStep=-1) at animation/qabstractanimation.cpp:823 #16 0x7fc13aa79fbf in QObject::event (this=0x561b642caa98, e=0x7ffd7556a210) at kernel/qobject.cpp:1336 #17 0x7fc13b7d0a5f in QApplicationPrivate::notify_helper (this=, receiver=0x561b642caa98, e=0x7ffd7556a210) at kernel/qapplication.cpp:3632 #18 0x7fc13aa4daaa in QCoreApplication::notifyInternal2 (receiver=0x561b642caa98, event=0x7ffd7556a210) at kernel/qcoreapplication.cpp:1063 #19 0x7fc13aaa448b in QTimerInfoList::activateTimers (this=this@entry=0x561b63a80860) at kernel/qtimerinfo_unix.cpp:643 #20 0x7fc13aaa4d34 in timerSourceDispatch (source=source@entry=0x561b63a80800) at kernel/qeventdispatcher_glib.cpp:183 #21 0x7fc13834280f in g_main_dispatch (context=0x561b639bcb20) at ../glib/gmain.c:3337 #22 g_main_context_dispatch (context=0x561b639bcb20) at ../glib/gmain.c:4055 #23 0x7fc138342b98 in g_main_context_iterate (context=context@entry=0x561b639bcb20, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #24 0x7fc138342c4f in g_main_context_iteration (context=0x561b639bcb20, may_block=1) at ../glib/gmain.c:4196 #25 0x7fc13aaa50f4 in QEventDispatcherGlib::processEvents (this=0x561b63a75520, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x7fc13aa4c4bb in QEventLoop::exec (this=this@entry=0x7ffd7556a450, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #27 0x7fc13aa54790 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #28 0x7fc13b0721fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #29 0x7fc13b7d09d5 in QApplication::exec () at kernel/qapplication.cpp:2824 #30 0x561b621dc2f3 in main (argc=, argv=) at /usr/src/debug/gwenview5-21.04.2-1.1.x86_64/app/main.cpp:202 [Inferior 1 (process 12644) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436732] File context menu opens always on first connected workspace
https://bugs.kde.org/show_bug.cgi?id=436732 --- Comment #3 from Marcel Rupp --- I am running X11, I will ask a friend because he is running Wayland if he is experiencing the same issue -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 436732] New: File context menu opens always on first connected workspace
https://bugs.kde.org/show_bug.cgi?id=436732 Bug ID: 436732 Summary: File context menu opens always on first connected workspace Product: frameworks-kwindowsystem Version: 5.81.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: marcel.r...@live.de Target Milestone: --- SUMMARY As of the recent stable update whenever I try to open a context menu for a file it gets opened on the first available "screen" on the left hand side. Other programs as well as the desktop context menu itself do still work. Only file context menus are broken. It seems like the position calculation is still correct: A file on the top-right of Monitor 2 (RHS) will cause the context menu to open at the top-right as well but on Monitor 1 (LHS) instead of Monitor 2 (RHS). STEPS TO REPRODUCE 1. Connect a second monitor 2. Have the right hand monitor be "Folder view" instead of "Desktop" 3. Try opening a file context menu (right click a file) OBSERVED RESULT Context menu opens on the left hand monitor but retains the correct position for the context menu relative to the display itself. EXPECTED RESULT Context menu opens at cursor position SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 --- Comment #5 from Marcel Hoffmann --- Thank you for looking into this. I agree that a hint in the dialog would help. My expectation was that the dialog asks where to place the new category and not where to place the whole category structure. The initial dialog made it look like "Fruit" would become a direct child of the "Expense" parent account and that action was required to put it in the right place. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 --- Comment #2 from Marcel Hoffmann --- Created attachment 137910 --> https://bugs.kde.org/attachment.cgi?id=137910=edit Actual parent is shown on the bottom of this screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 --- Comment #1 from Marcel Hoffmann --- Created attachment 137909 --> https://bugs.kde.org/attachment.cgi?id=137909=edit Selecting the correct parent -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436177] New: Category Auto-Creation does not work as intended
https://bugs.kde.org/show_bug.cgi?id=436177 Bug ID: 436177 Summary: Category Auto-Creation does not work as intended Product: kmymoney Version: 5.1.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: kdebugrep...@pastsecurity.com Target Milestone: --- Created attachment 137908 --> https://bugs.kde.org/attachment.cgi?id=137908=edit Dialog after creating a new category from the ledger view SUMMARY Entering a new ledger entry allows to auto-create a new category if it does not exist. The dialog explains that the parent category will be Expense/Income, but can be changed in the next dialog. Selecting the correct parent category in the next dialog does not work as intended. Instead of adding the new category under the selected parent, it duplicates the whole category structure under the new parent entry. STEPS TO REPRODUCE 1. Enter new ledger entry 2. Enter non-existing category, e.g. "Food:Groceries:Fruit" 3. Click "Yes" in next dialog 4. Change parent category, e.g. from "Expense" to "Expense:Food:Groceries" 5. Click "OK" OBSERVED RESULT New category structure is "Food:Groceries:Food:Groceries:Fruit" EXPECTED RESULT New category structure should be "Food:Groceries:Fruit" 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.
[Discover] [Bug 409136] Setting to adjust checking for updates frequency
https://bugs.kde.org/show_bug.cgi?id=409136 Marcel changed: What|Removed |Added CC||misterx.m...@gmail.com --- Comment #4 from Marcel --- I would like to add to the already made suggestions the ability to chose to disable or change frequency of checking for updates depending on package type. For example disable checking for updates for system packages (e.g.:.deb, .rpm, ...) but keep or set an other frequency for flatpaks, snaps or fwupd packages. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410839] Kwin crashes sometimes when using the virtual desktop grid
https://bugs.kde.org/show_bug.cgi?id=410839 --- Comment #9 from Marcel --- Created attachment 134646 --> https://bugs.kde.org/attachment.cgi?id=134646=edit New crash information added by DrKonqi kwin_x11 (5.20.5) using Qt 5.15.2 This is again the same crash using current packages -- Backtrace (Reduced): #4 0x7fa2e06aabbb in KWin::VirtualDesktop::x11DesktopNumber() const (this=0x0) at /usr/src/debug/kwin5-5.20.5-387.1.x86_64/build/kwin_autogen/EWIEGA46WW/../../../virtualdesktops.h:57 #5 KWin::AbstractClient::desktop() const (this=0x55899e18c9f0) at /usr/src/debug/kwin5-5.20.5-387.1.x86_64/build/kwin_autogen/EWIEGA46WW/../../../abstract_client.h:468 #6 0x7fa2e06d8bd5 in KWin::AbstractClient::setDesktops(QVector) (this=, desktops=...) at /usr/src/debug/kwin5-5.20.5-387.1.x86_64/abstract_client.cpp:474 #7 0x7fa2e072c959 in KWin::EffectsHandlerImpl::windowToDesktops(KWin::EffectWindow*, QVector const&) (this=, w=, desktopIds=) at /usr/src/debug/kwin5-5.20.5-387.1.x86_64/effects.cpp:921 #8 0x7fa2deb6f5b6 in KWin::DesktopGridEffect::windowInputMouseEvent(QEvent*) (this=0x55899cca0c10, e=) at /usr/src/debug/kwin5-5.20.5-387.1.x86_64/effects/desktopgrid/desktopgrid.cpp:539 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410839] Kwin crashes sometimes when using the virtual desktop grid
https://bugs.kde.org/show_bug.cgi?id=410839 --- Comment #8 from Marcel --- (In reply to Mathieu Jobin from comment #7) > would you please try again with kwin 5.19+ > debug symbols installed > > desktop effects and compositing settings on and off. Sadly I cannot reproduce the bug actively, it just happens from time to time, currently using: * Qt 5.15.2 * KDE Frameworks 5.77.0 * Plasma 5.20.4 I will attach a new stacktrace as soon as the crash is happening again. I think I will never see this crash with compositing off as the desktop grid will not work without compositing enabled. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430876] Rename images without changing any properties
https://bugs.kde.org/show_bug.cgi?id=430876 --- Comment #5 from Marcel --- Ah, that's the solution I was looking for. I was not aware of the powerful rename plugin. In combination with Export to local storage plugin I can achieve exactly what I want. Selecting tagged images, export it to another folder and rename it with the build in tool. Thank you for your help. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430876] Rename images without changing any properties
https://bugs.kde.org/show_bug.cgi?id=430876 --- Comment #3 from Marcel --- To be hones I'm not satisfied with this answer. It does not solve my problem, probably because of a missunderstanding. 1. I don't want to rename the image, I want a copy with a different name. The reason is that my album creator software (for a printed album) has same nasty limitation. So I need to rename the images for correct ordering. 2. I don't want to create a new directory. The example uses sets the directory name of the containing folder to the file name (in BQM that works already very well :-) ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430876] Rename images without changing any properties
https://bugs.kde.org/show_bug.cgi?id=430876 Marcel changed: What|Removed |Added CC||maes...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430876] New: Rename images without changing any properties
https://bugs.kde.org/show_bug.cgi?id=430876 Bug ID: 430876 Summary: Rename images without changing any properties Product: digikam Version: 7.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: BatchQueueManager Assignee: digikam-bugs-n...@kde.org Reporter: maes...@gmail.com Target Milestone: --- SUMMARY Not sure if the batch queue manager is the right tool to do it. What I want is some thing to copy selected images to a new location with a new name but without changing any properties. With properties I mean the assigned tools (this can't be left empty) and the saving images tab (this is unnecessary as long as no tool is assigned or only meta data is changed). STEPS TO REPRODUCE 1. Try to copy selected images to a new location with a new name (e.g. [dir]_[file]) without changing the image. 2. 3. OBSERVED RESULT Using the batch queue manager I had to apply a tool and the image was rendered again. EXPECTED RESULT This is just an idea of there is no other way to solve it. - Allow to run batch queue manager to run without any tool - Add a flag on tab Saving images to leave as it is if possible (e.g. only mega data changed) 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.
[LabPlot2] [Bug 430464] New: Feature Request: Add option for scientific notation in powers of ten for axis labels
https://bugs.kde.org/show_bug.cgi?id=430464 Bug ID: 430464 Summary: Feature Request: Add option for scientific notation in powers of ten for axis labels Product: LabPlot2 Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: misterx.m...@gmail.com Target Milestone: --- Currently when creating a plot the options for axis labels are decimal, scientific notation, powers of 10, powers of 2 and multiples of pi. The option for scientific notation displays the labels looking like 1e+2, my request is to add a second scientific notation option which displays the labels looking like 1x10^2 as an alternative to the e notation. Thank you very much for creating such an useful tool like LabPlot. Marcel -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430004] Contradictory posting
https://bugs.kde.org/show_bug.cgi?id=430004 --- Comment #2 from André-Marcel Berthouzoz --- This is a Logitech K520 105-key keyboard. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 430004] New: Contradictory posting
https://bugs.kde.org/show_bug.cgi?id=430004 Bug ID: 430004 Summary: Contradictory posting Product: systemsettings Version: 5.20.2 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard_layout Assignee: plasma-b...@kde.org Reporter: am...@tvs2net.ch Target Milestone: --- Created attachment 133869 --> https://bugs.kde.org/attachment.cgi?id=133869=edit Contains the 2 screenshots mentioned The System Configuration / Hardware / Input Devices / Keyboard window does not display the same information as the Mageia Control Center Define the keyboard layout. See the 2 screenshots in the attached file "Configuration clavier.pdf" Best regards and have a good weekend. André-Marcel Berthouzoz -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429994] New: Tooltip to complete
https://bugs.kde.org/show_bug.cgi?id=429994 Bug ID: 429994 Summary: Tooltip to complete Product: systemsettings Version: 5.20.2 Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kded Assignee: molken...@kde.org Reporter: am...@tvs2net.ch CC: plasma-b...@kde.org Target Milestone: --- Created attachment 133857 --> https://bugs.kde.org/attachment.cgi?id=133857=edit explanatory screenshot System configuration / Startup and shutdown / Background services. Proposal to complete the tooltip in French : Automatically switch the loading of this service at startup. (Basculer automatiquement le chargement de ce service au démarrage) See the explanatory screenshot in the attached file : "Infobulle pour Services d'arrière plan.pdf" Best regards and thanks for your work. André-Marcel Berthouzoz -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 427190] pinebook labplot2 inability to produce any fitting analysis and xy curve from a mathematical equation
https://bugs.kde.org/show_bug.cgi?id=427190 Marcel changed: What|Removed |Added CC||misterx.m...@gmail.com --- Comment #2 from Marcel --- I can confirm this bug to be not exclusively limited to pinebooks or arm. I have the same problem on an HP laptop with amd64 architecture and Debian unstable. Labplot does not perform fits with custom equations, the field for the custom equation stays red and no fit appears on the worksheet. After trying to fit with a custom equation fitting with the predefined models like polynomial is also impossible. I can also confirm the problem with plotting an xy-curve form a mathematical equation, the field for entering the equation stays red no matter what and no curve appears on the worksheet. SOFTWARE / OS VERSIONS: Labplot Version: 2.8.1 Operating System: Debian GNU/Linux KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.9.7-towo.1-siduction-amd64 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428941] Cleanup tool to delete duplicated faces
https://bugs.kde.org/show_bug.cgi?id=428941 Marcel changed: What|Removed |Added CC||maes...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 428941] New: Cleanup tool to delete duplicated faces
https://bugs.kde.org/show_bug.cgi?id=428941 Bug ID: 428941 Summary: Cleanup tool to delete duplicated faces Product: digikam Version: 7.3.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: maes...@gmail.com Target Milestone: --- SUMMARY Feature request Over the time I have been using several face detection and recognition algorithms including manual face tagging. Sometimes when the tolerance of yolo it to big the algorithm does not see that there already is a tagged face in that area. A cleanup tool would be nice to scan on one hand for pictures with multiple occurrence of the same person and on the other hand for faces in faces. The cleanup must be individual and not automatically as it may be correct to have the the same person multiple times on the same image. This my happen e.g. on colleges, mirrors or background photos. STEPS TO REPRODUCE 1. Just mark manually the faces before running the face detection algorithm. Most of the time when surrounding the whole head instead of just the face, a second face is detected. 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.
[trojita] [Bug 428078] SMTP AUTH Login truncates Base64 representation of username
https://bugs.kde.org/show_bug.cgi?id=428078 --- Comment #3 from Marcel Bosling --- Hi again, I've used typeid().name() on buf to see what type get's deduced from auto buf and for me it turns out to be the following mangeld type name: 14QStringBuilderI10QByteArrayA3_cE It seems that a QStringBuilder is indeed involved. This is on GCC 10.2.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #15 from Marcel --- Ok, nice to see this confirmed. It'd be very nice to have some kind of migration/conversion, something like: If digikam's algorithm detect's a face located - at the same spot or - within a previously marked/detected rectangle then - assign the existing face tag to digikam's database or at least - make suggestions to do so (and maybe confirm this by the user) BTW: Is there some simple way to accept all suggestions for one person? Currently I need to select all of them and then confirm the selction, which is a bit of a hazzle for lots of suggestions (Picasa just had a "confirm all button" on the very top, so the process looked like: get rid of all non-matching faces and then just click that button) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #12 from Marcel --- Current git releases still show same behaviour: Google Picasa tagged faces get imported and displayed, however no newly detected faces are matched to the existing (Picasa) ones. After clearing all metadata and tagging all faces with digikam face matching works as expected. So - for me it looks like either - the Google Picasa tagged faces are totally ignored for training or - for some reason the Picasa tagging is so different from digikam's, that the training model fails Any ideas how to diagnose this some more? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 428078] SMTP AUTH Login truncates Base64 representation of username
https://bugs.kde.org/show_bug.cgi?id=428078
--- Comment #2 from Marcel Bosling ---
Hi Jan,
indeed the statement is a leftover of my investigations.
These are the results when using auto and QByteArray for buf:
const QString : "someexampleusern...@whereever.org"
auto buf: "a\x00u\x00t\x00o\x00 \x00""b\r\n"
QByteArray buf: "c29tZWV4YW1wbGV1c2VybmFtZUB3aGVyZWV2ZXIub3Jn\r\n"
SIDENOTE:
I've tried to reproduce the problem with a simple QT program doing just the
conversion with auto and QByteArray. The resulting variables hold the same
(correct) base64 encoded data, yielding:
auto: "U29tZWxvbmd1c2VybmFtZUB3aGVyZWV2ZXIub3Jn\r\n"
bufQB: "U29tZWxvbmd1c2VybmFtZUB3aGVyZWV2ZXIub3Jn\r\n"
SOURCE:
#include
#include
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);
const QString username = "somelongusern...@whereever.org";
const QString = username;
auto bufAuto = reftousername.toUtf8().toBase64() + "\r\n";
QByteArray bufQB = reftousername.toUtf8().toBase64() + "\r\n";
qDebug()<<"auto: " << bufAuto;
qDebug()<<"bufQB: " << bufQB;
return a.exec();
}
--
You are receiving this mail because:
You are watching all bug changes.
[trojita] [Bug 428078] New: SMTP AUTH Login truncates Base64 representation of username
https://bugs.kde.org/show_bug.cgi?id=428078
Bug ID: 428078
Summary: SMTP AUTH Login truncates Base64 representation of
username
Product: trojita
Version: git
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: SMTP
Assignee: trojita-b...@kde.org
Reporter: marcel.bosl...@rwth-aachen.de
Target Milestone: ---
The username is truncated for my usecase when using a AUTH Login. Therefore the
authentication fails with error 5.7.3.
STEPS TO REPRODUCE
1. Try to connect to an SMTP server via AUTH Login/StartTLS (my case: rather
long mail address)
OBSERVED RESULT
Authentication fails with error 5.7.3.
EXPECTED RESULT
Authentication should reach the next step and process the given password.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux Kernel 5.9.1 x64
(available in About System)
KDE Plasma Version: 5.20.1
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
ADDITIONAL INFORMATION
PATCH:
diff --git a/src/qwwsmtpclient/qwwsmtpclient.cpp
b/src/qwwsmtpclient/qwwsmtpclient.cpp
index 1c34fb86..619244dc 100644
--- a/src/qwwsmtpclient/qwwsmtpclient.cpp
+++ b/src/qwwsmtpclient/qwwsmtpclient.cpp
@@ -12,6 +12,7 @@
#include "qwwsmtpclient.h"
#include
#include
+#include
#include
#include
#include
@@ -544,7 +545,7 @@ void QwwSmtpClientPrivate::sendAuthPlain(const QString &
username, const QString
void QwwSmtpClientPrivate::sendAuthLogin(const QString & username, const
QString & password, int stage) {
if (stage==1) {
-auto buf = username.toUtf8().toBase64() + "\r\n";
+QByteArray buf = username.toUtf8().toBase64() + "\r\n";
emit q->logSent(buf);
socket->write(buf);
} else if (stage==2) {
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #11 from Marcel --- Ok - I will do so and keep you informed about my findings. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #9 from Marcel --- Ok, so I used latest appimage version of digikam (just to make sure there's no difference to my daily git build). Results however are not the desired ones: What's good: In both versions (appimage/daily build) I get lots of suggestions, for all kinds of identities (not only the small part tagged with digikam). What's bad: The recognition rate is round about zero. The suggestions appear random. I don't know, maybe the training based on the picasa tagging does something weird. I'll try to prepare a smaller training data set to analyze this some more. Or is there - by any chance - a data set like this available somewhere? Maybe even with "public" faces, so it's easier to reproduce such a behaviour without sending tons of private pictures? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #233 from Marcel --- The test runs now for 12 hours without a crash. Good job Maik and Gilles. Thank you for fixing that. I will continue the run to see if it finishes without a crash but I guess we can close this issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427203] Asan error on closing digikam
https://bugs.kde.org/show_bug.cgi?id=427203 --- Comment #5 from Marcel --- Created attachment 132075 --> https://bugs.kde.org/attachment.cgi?id=132075=edit asan output I get a new error from asan on closing Digikam. This time I have no idea where it comes from. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427203] Asan error on closing digikam
https://bugs.kde.org/show_bug.cgi?id=427203 --- Comment #3 from Marcel --- Created attachment 132067 --> https://bugs.kde.org/attachment.cgi?id=132067=edit Seg fault on closing Digikam Thank you Maik for fixing this asan bug. I successfully tested it. Unfortunately on the closing the next error occurs. A sig fault. See bt_clowing_digikam.txt. I guess it comes from the same thematic as Bug 426175. A virtual call is done in the destructor. Probably the mutex lock in ManagedLoadSaveThread::stopAllTasks() should be removed. What do you think? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #229 from Marcel --- Created attachment 132064 --> https://bugs.kde.org/attachment.cgi?id=132064=edit asan error in CPGFMemoryStream Maik, the test run for a long time. I original error did not occur. Instead this one was shown after hours. What is now the change? Is it now just the removeOne() function? @Gilles. In my work place we also had discussions about this clang-tidy rule. Technically it can help in a few places to decrease the move effort. But we came up with the conclusion that the readability is lower and its error prune when copying from such a place. Therefore we decided to not to use this rule. Anyway, in my opinion there are other rules far more important for Digikam than this one. On my work place it turned out that a good way to go is: - Activate new rule and auto fix it - Most autofix problems turned out to be compiler errors es well. Fix them. - After applying, look for a compiler flag doing the same (e.g override) and apply it and treat warnings as errors With this way you also find the false positive and ensure that nobody in the future does it wrong again. If you like I could spend some time with that and send you a merge request... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #226 from Marcel --- Maik, the version now looks very promising. It already works for hours without a crash. I saw you reverted most changes (even the typo fix :-) ). In your commit message are you writing "test this small change". What did you change, that we did not test so far? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427203] New: Asan error on closing digikam
https://bugs.kde.org/show_bug.cgi?id=427203 Bug ID: 427203 Summary: Asan error on closing digikam Product: digikam Version: 7.2.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Thumbs-Engine Assignee: digikam-bugs-n...@kde.org Reporter: maes...@gmail.com Target Milestone: --- Created attachment 132046 --> https://bugs.kde.org/attachment.cgi?id=132046=edit asan output SUMMARY After closing Digikam asan reports an error STEPS TO REPRODUCE 1. Start Digikam 2. Wait until scan for new images is finished 3. Close Digikam 4. Asan reports an error OBSERVED RESULT See attached file asanOnCloseDigikam.txt EXPECTED RESULT Close without an error on asan SOFTWARE/OS VERSIONS Digikam: Commit 2fdab922ec229c29be1698e9dce59b80dd6cfda6 Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427203] Asan error on closing digikam
https://bugs.kde.org/show_bug.cgi?id=427203 Marcel changed: What|Removed |Added CC||maes...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #222 from Marcel --- No look, it still crashes, at least with asan enabled. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #221 from Marcel --- Maik, I tried it with your commit https://invent.kde.org/graphics/digikam/-/commit/a296fd327a98a5d5ffbf6690cec4eb5b85de0330 but it again crashed after a few minutes. Digikam::LoadingCache::notifyNewLoadingProcess(Digikam::LoadingProcess*, Digikam::LoadingDescription const&) /home/marcel/Repos/digikam/core/libs/threadimageio/fileio/loadingcache.cpp:293 Now I'm on https://invent.kde.org/graphics/digikam/-/commit/a0157f8d2bcc6dfb33e74518b546c1553a864ae2 and it works until now (more than 50 minutes). I will keep it running during the night. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #8 from Marcel --- Ok - I'll give it a try over night. However I am running a post 7.1.0 git (git20200928.31e8fed), so I guess if the relevant changes are older than 2 days I already used them. PS: Sorry if I messed this up when reporting the bug, but as I'm testing with current git version I didn't know which version to choose. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #6 from Marcel --- Ok - did some more testing: Running "Detect faces" (with "Scan again and merge results") and running "Recognize faces" afterwards, results in new faces in both "Unconfirmed" and "Unknown". However only faces that were tagged using digikam seem to be considered for face recognition at all (at least that's my theory right now - please correct me if this isn't true). I've got quite some people listed as "People" in digikam (all but a few new ones were originally tagged with picasa) but to me it looks like the ones tagged in picasa are listed but completely ignored when it comes to face recognition. As a side effect the recognition rate is 0% (all suggested faces were wrong). Maybe it's just me, but even if there are technical reasons for this, I consider it quite confusing from a user's perspective. Can someone confirm or deny, that face tags not written by digikam are treated differently in some way? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #5 from Marcel --- Ok, so what's the right way to go then? 1. Do the rebuild database thing on first import 2. Run "Detect faces" (with "Scan again and merge results") 3. Run "Recognize faces" If so that's exactly what I'd expect when running "Maintenance" with "Detect and recognise faces" and "Clear and rebuild all training data" enabled -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 427071] Importing pictures with faces tagged by picasa results in error "missing identities"
https://bugs.kde.org/show_bug.cgi?id=427071 --- Comment #3 from Marcel --- Hmmm ... my test run finished. Good news is: - analyzing 90.000+ pictures worked fine. - I get lots of pre-tagged "People" - I do no longer get the "no identities" error Bad news is: - Not a single "Unconfirmed" or "Unknown" face was found (and that's *very* unlikely to be the case) Anything else I could try? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #212 from Marcel --- Feedback about patch: only one override +~ActionJob() override override; +~ActionThreadBase() override override; +~DynamicThread() override override; +~ThreadManager() override override; +~WorkerObject() override override; After my knowledge it does the same as before. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426968] Album title bar in icon view should be a selection switch
https://bugs.kde.org/show_bug.cgi?id=426968 Marcel changed: What|Removed |Added CC||maes...@gmail.com --- Comment #1 from Marcel --- Vishal, according to your question, I would start looking in the class itemcategorydrawer.cpp file. There is the place where the title bar is set up. About this whole bug report. In my opinion it is not a bug. The current solution is a state less user interface what makes it much less error prune. I don't know any program that deselects all items after pressing Ctrl + A a second time. -- You are receiving this mail because: You are watching all bug changes.
