[kwin] [Bug 416033] New: Kwin crash with kwin-tiling enabled when launching a VM
https://bugs.kde.org/show_bug.cgi?id=416033 Bug ID: 416033 Summary: Kwin crash with kwin-tiling enabled when launching a VM Product: kwin Version: 5.17.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: damien.mou...@fr.interplex.com Target Milestone: --- Application: kwin_x11 (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.65.0 Operating System: Linux 5.4.8-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Started a Windows 10 virtual machine in virtual box, while the kwin-tiling script was enabled. I don't recall of it happening with the script disabled. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb3495c8880 (LWP 213902))] Thread 5 (Thread 0x7fb342dee700 (LWP 214386)): #0 0x7fb34ee0ac45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb34fc6acc4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fb34fc6ada2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7fb34e8bd18b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fb34e8bd41b in () at /usr/lib/libQt5Quick.so.5 #5 0x7fb34fc64fd6 in () at /usr/lib/libQt5Core.so.5 #6 0x7fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7fb3514502d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb340ee6700 (LWP 213921)): #0 0x7fb34ee0ac45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb34f75ef3c in () at /usr/lib/libQt5Script.so.5 #2 0x7fb34f75ef59 in () at /usr/lib/libQt5Script.so.5 #3 0x7fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb3514502d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb342127700 (LWP 213911)): #0 0x7fb351445ae6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fb34fe93cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fb34fe952dd in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fb34fe3e39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb34fc63e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fb34e523249 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fb34fc64fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb3514502d3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb343fff700 (LWP 213906)): #0 0x7fb351445ae6 in ppoll () at /usr/lib/libc.so.6 #1 0x7fb34fe93cc3 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fb34fe952dd in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fb34fe3e39c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb34fc63e62 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fb34dea2b28 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fb34fc64fd6 in () at /usr/lib/libQt5Core.so.5 #7 0x7fb34ee044cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb3514502d3 in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fb3495c8880 (LWP 213902)): [KCrash Handler] #6 0x7fb34e29260c in () at /usr/lib/libQt5Qml.so.5 #7 0x7fb34e318cea in QV4::PersistentValueStorage::mark(QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5 #8 0x7fb34e29298e in QV4::MemoryManager::collectRoots(QV4::MarkStack*) () at /usr/lib/libQt5Qml.so.5 #9 0x7fb34e292b7e in QV4::MemoryManager::mark() () at /usr/lib/libQt5Qml.so.5 #10 0x7fb34e294672 in () at /usr/lib/libQt5Qml.so.5 #11 0x7fb34e296aaa in QV4::MemoryManager::allocData(unsigned long) () at /usr/lib/libQt5Qml.so.5 #12 0x7fb34e320f0f in QV4::ArrayData::realloc(QV4::Object*, QV4::Heap::ArrayData::Type, unsigned int, bool) () at /usr/lib/libQt5Qml.so.5 #13 0x7fb34e328dbe in () at /usr/lib/libQt5Qml.so.5 #14 0x7fb34e3c7bf5 in QV4::Runtime::CallProperty::call(QV4::ExecutionEngine*, QV4::Value const&, int, QV4::Value*, int) () at /usr/lib/libQt5Qml.so.5 #15 0x7fb325391258 in () #16 0x in () [Inferior 1 (process 213902) detached] Possible duplicates by query: bug 415991, bug 415960, bug 415956, bug 415930, bug 415824. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #20 from Andrew Udvare --- Also one workaround for now that must be applied to the broken apps specifically is to use the QT_FONT_DPI environment variable. Setting this to 96 in the .desktop file for Kate/Dolphin/etc makes things seem normal again, and icons are the correct size. $ fgrep Exec ~/.local/share/applications/org.kde.kate.desktop Exec=env QT_FONT_DPI=96 kate -b %U -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 415836] Ethernet network connection after fresh install of fc31 stuck to 100MBit/s
https://bugs.kde.org/show_bug.cgi?id=415836 Jan Grulich changed: What|Removed |Added CC||jgrul...@redhat.com Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Jan Grulich --- It's a default connection created by NetworkManager, we do not automatically create connections, not even when there is none. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #19 from Andrew Udvare --- I updated and rebooted. This issue remains. I tested Ark, VirtualBox and Qt Designer. All 3 show large fonts. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416028] "Search in Tags" selection for Face detection/recognition unduly changes
https://bugs.kde.org/show_bug.cgi?id=416028 Maik Qualmann changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416028] "Search in Tags" selection for Face detection/recognition unduly changes
https://bugs.kde.org/show_bug.cgi?id=416028 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- When selecting face recognition, all "people" tags are selected. I also think that is a mistake. Maik -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416001] Font Preview in profile settings window does not display font in monospace style
https://bugs.kde.org/show_bug.cgi?id=416001 --- Comment #4 from Mariusz Glebocki --- I think that's not Konsole bug - it affects other Qt Widget apps. System settings uses QtQuick/Kirigami. Can you verify other QtQuick app? E.g. plasma discover (with main system font set to monospace one). Maybe system settings applies selected hinting for its own preview but for some reason does not apply it system-wide. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 --- Comment #7 from Maik Qualmann --- When choosing just one tag, the entire collection seems to be scanned, so I look at it. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 --- Comment #6 from Maik Qualmann --- 1) Is an intended behavior that applies everywhere in digiKam, there is no selection, the whole collection is used. This behavior also exists in the Icon View, if no selection is made, the entire items is taken over when called up by a tool. 2) The tags are not only limited to person tags. For example, by selecting the "France" tag from a trip. This will only scan these images. Maik -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416031] Panel shadow size no longer consistent between my two panels like they were before last update.
https://bugs.kde.org/show_bug.cgi?id=416031 --- Comment #1 from Michail Vourlakos --- Latte does not change anything about panel shadows. Close Latte and add plasma panels at the same edges you should notice same shadows. Probably your plasma theme was updated and contains different shadows for top and left panels. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 416001] Font Preview in profile settings window does not display font in monospace style
https://bugs.kde.org/show_bug.cgi?id=416001 --- Comment #3 from Andrzej Rybczak --- Indeed. I compared hintings and it looks like hintnone fontconfig setting (even though I'm using hintfull systemwide). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414016] Log file /var/log/syslog grows in size very fast
https://bugs.kde.org/show_bug.cgi?id=414016 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415882] DigiKam 6.4 crashes on processing a large number of new HEIC/HEIF files
https://bugs.kde.org/show_bug.cgi?id=415882 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414028] digikam spamming journal with details of almost everything it does...
https://bugs.kde.org/show_bug.cgi?id=414028 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414115] g'mic plugin not available on Mac
https://bugs.kde.org/show_bug.cgi?id=414115 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/8d792eca68f6 ||8eb6f210366b01139abdeb3df1a ||6 Version Fixed In||7.0.0 --- Comment #3 from caulier.gil...@gmail.com --- Git commit 8d792eca68f68eb6f210366b01139abdeb3df1a6 by Gilles Caulier. Committed on 09/01/2020 at 05:38. Pushed by cgilles into branch 'master'. move gmicqt plugin to the right target directory under MacOS FIXED-IN:7.0.0 M +2-0project/bundles/macports/03-build-digikam.sh https://invent.kde.org/kde/digikam/commit/8d792eca68f68eb6f210366b01139abdeb3df1a6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388481] No tags appear in tag column in detailed list view
https://bugs.kde.org/show_bug.cgi?id=388481 John Little changed: What|Removed |Added CC||john.b.lit...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415562] About screen "Getting Started" links to 404 page not found
https://bugs.kde.org/show_bug.cgi?id=415562 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415452] White squares
https://bugs.kde.org/show_bug.cgi?id=415452 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415491] Unable to create a keyframe on existing layer
https://bugs.kde.org/show_bug.cgi?id=415491 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 414930] Widget padding changes inexplicably.
https://bugs.kde.org/show_bug.cgi?id=414930 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391781] Add support for SIXEL in Konsole
https://bugs.kde.org/show_bug.cgi?id=391781 Frederick Zhang changed: What|Removed |Added CC||frederick...@tsundere.moe -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410287] Rendering selected zone not working
https://bugs.kde.org/show_bug.cgi?id=410287 Frederick Koehler changed: What|Removed |Added CC||fkoehle...@gmail.com Platform|Archlinux Packages |Fedora RPMs --- Comment #9 from Frederick Koehler --- See the same issue under Fedora 31 with kdenlive-19.08.2-1.fc31.x86_64 where the 'Selected zone' and 'Guide zone' options produce ~1 second render job without usable output (but the same job works fine when rendered over the full project). Tried options rendering to a file as well as scripts. Tried changing the profile frame rate. Tried reading in older projects and repeated the same issue. Would be happy just with a work-around... it's actually a useful feature to have available. I often render a big school concert twice...once with every group performing (for the school) and a second time selecting just the section with the ensemble that includes performers in our family (for our video library). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #18 from Andrew Udvare --- (In reply to David Edmundson from comment #17) > As you're on gentoo, can you be sure to re-emerge plasma-workspace after you > upgraded Qt to rule that out? Currently doing a system upgrade which update my system to 5.17.5. I will reboot after to make sure I'm running all newly built libs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416032] New: plasmashell segmentation fault involving KProcessList::processInfo
https://bugs.kde.org/show_bug.cgi?id=416032 Bug ID: 416032 Summary: plasmashell segmentation fault involving KProcessList::processInfo Product: plasmashell Version: 5.17.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matthew.fagn...@utoronto.ca CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.5.0-0.rc5.git0.1.fc32.x86_64 x86_64 Distribution: Fedora 32 (Rawhide) -- Information about the crash: - What I was doing when the application crashed: I started Plasma 5.17.4 on Wayland in Fedora Rawhide with Qt 5.13.2, KF 5.65.0, mesa 19.3.1. I opened konsole. I opened Firefox Nightly 74.0a, used it, and closed it. I opened Firefox again. - Unusual behavior I noticed: The Plasma task bar disappeared from the bottom of the screen and then reappeared. plasmashell segmentation faulted. The crashing thread 1 had the frame #12 showing pid 2658 #12 0x7fa42124c383 in KProcessList::processInfo(long long) (pid=pid@entry=2658) at /usr/src/debug/kf5-kcoreaddons-5.65.0-1.fc32.x86_64/src/lib/util/kprocesslist.cpp:106 The pid 2658 was shown by ps aux | grep 2658 as a defunct Firefox process. matt2658 3.3 0.0 0 0 ?Z20:17 0:58 [firefox-bin] The frames #6,8-9 had this=0x30 which looked like an invalid pointer. The invalid pointer might have been related to the Firefox process which hadn't stopped yet. I've seen this plasmashell crash with this trace once. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fa421f8f800 (LWP 1400))] Thread 24 (Thread 0x7fa3a99b1700 (LWP 1817)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x56157f0b7af8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56157f0b7aa8, cond=0x56157f0b7ad0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56157f0b7ad0, mutex=0x56157f0b7aa8) at pthread_cond_wait.c:638 #3 0x7fa40726049b in cnd_wait (mtx=0x56157f0b7aa8, cond=0x56157f0b7ad0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x56157eed3680) at ../src/util/u_queue.c:275 #5 0x7fa4072600ab in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fa41f44b482 in start_thread (arg=) at pthread_create.c:477 #7 0x7fa41fc43583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fa3a91b0700 (LWP 1814)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x56157f031f08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56157f031eb8, cond=0x56157f031ee0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56157f031ee0, mutex=0x56157f031eb8) at pthread_cond_wait.c:638 #3 0x7fa40726049b in cnd_wait (mtx=0x56157f031eb8, cond=0x56157f031ee0) at ../include/c11/threads_posix.h:155 #4 util_queue_thread_func (input=input@entry=0x56157f0502b0) at ../src/util/u_queue.c:275 #5 0x7fa4072600ab in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #6 0x7fa41f44b482 in start_thread (arg=) at pthread_create.c:477 #7 0x7fa41fc43583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7fa3be2d9700 (LWP 1812)): #0 0x7fa41fc389af in __GI___poll (fds=0x7fa3900029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa41e703e1e in g_main_context_poll (priority=, n_fds=1, fds=0x7fa3900029e0, timeout=, context=0x7fa39c30) at ../glib/gmain.c:4309 #2 g_main_context_iterate (context=context@entry=0x7fa39c30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4005 #3 0x7fa41e703f53 in g_main_context_iteration (context=0x7fa39c30, may_block=may_block@entry=1) at ../glib/gmain.c:4071 #4 0x7fa4201d78b3 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7fa39b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fa42018124b in QEventLoop::exec(QFlags) (this=this@entry=0x7fa3be2d8da0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7fa41ffd1c75 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7fa41ffd2dc6 in QThreadPrivate::start(void*) (arg=0x56157eba5eb0) at thread/qthread_unix.cpp:360 #8 0x7fa41f44b482 in start_thread (arg=) at pthread_create.c:477 #9 0x7fa41fc43583 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21
[lattedock] [Bug 416031] New: Panel shadow size no longer consistent between my two panels like they were before last update.
https://bugs.kde.org/show_bug.cgi?id=416031 Bug ID: 416031 Summary: Panel shadow size no longer consistent between my two panels like they were before last update. Product: lattedock Version: 0.9.7 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: containment Assignee: mvourla...@gmail.com Reporter: adamska...@gmail.com Target Milestone: --- Created attachment 124986 --> https://bugs.kde.org/attachment.cgi?id=124986=edit Left panel shadow is much larger SUMMARY Panel shadow size no longer consistent between my two panels like they were before last update. STEPS TO REPRODUCE Not sure how to reproduce. Maybe just put a panel on the left and another on top with shadows turned on. OBSERVED RESULT The left panel has a far bigger shadow and it didn't before the last update. EXPECTED RESULT Both panels should have the same shadow size. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.1 KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 4.12.14-lp151.28.36-default -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 415235] Cover art for certain songs/albums doesn't load.
https://bugs.kde.org/show_bug.cgi?id=415235 --- Comment #11 from Noah --- Update: I believe I have discovered the cause of this bug. For whatever reason, whenever the database for elisa says that there's a cover image in the album table, it won't display the cover image for certain albums. I like to keep a file in the directory where the contents of the album are kept called 'cover.png', and it's just an image of the album's cover art. For those albums that don't display correctly, if I remove the 'cover.png' file and then refresh the music collection in elisa, it will sometimes fix it. Other times, I have to close elisa and go into the database and manually write the change to fix it. For example, in the screenshot you can see that 'Looking Glass (feat. Bien) by Synthion' isn't displaying correctly. In the database, it says that there's a cover image for that album located at file:///home/noah/Music/Synthion/Synthion - Looking Glass (feat. Bien)/cover.png. For that particular album, if I just remove the cover.png file, then refresh elisa, it works correctly. That doesn't always fix it though. If you look near the bottom of the screenshot, you'll see that the album titled 'Promenade' is also not displaying correctly. For this one, I had to remove the cover file and delete the cover image pathway from the database manually, then restart elisa, to make it work normally. I don't know why this was happening, but I thought I'd share what I found out here. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 415014] Plasma5 crashes at startup
https://bugs.kde.org/show_bug.cgi?id=415014 David Edmundson changed: What|Removed |Added Component|generic-crash |general Assignee|plasma-b...@kde.org |dantt...@gmail.com Target Milestone|1.0 |--- CC||k...@davidedmundson.co.uk Version|5.17.3 |unspecified Product|plasmashell |print-manager -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415296] Plasmashell crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415296 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from David Edmundson --- *** This bug has been marked as a duplicate of bug 415650 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411869] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=411869 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from David Edmundson --- *** This bug has been marked as a duplicate of bug 415650 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415650] Double-clicking the digital clock makes plasma crash
https://bugs.kde.org/show_bug.cgi?id=415650 David Edmundson changed: What|Removed |Added CC||nik...@niklasmoran.com --- Comment #4 from David Edmundson --- *** Bug 415356 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415650] Double-clicking the digital clock makes plasma crash
https://bugs.kde.org/show_bug.cgi?id=415650 David Edmundson changed: What|Removed |Added CC||kokakiwi+...@kokakiwi.net --- Comment #6 from David Edmundson --- *** Bug 411869 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415356] plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415356 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from David Edmundson --- *** This bug has been marked as a duplicate of bug 415650 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415650] Double-clicking the digital clock makes plasma crash
https://bugs.kde.org/show_bug.cgi?id=415650 David Edmundson changed: What|Removed |Added CC||kde...@agilob.net --- Comment #5 from David Edmundson --- *** Bug 415296 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415356] plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415356 David Edmundson changed: What|Removed |Added CC||logan2...@gmail.com --- Comment #3 from David Edmundson --- *** Bug 415122 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415122] Plasma crashes on startup
https://bugs.kde.org/show_bug.cgi?id=415122 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 415356 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 415836] Ethernet network connection after fresh install of fc31 stuck to 100MBit/s
https://bugs.kde.org/show_bug.cgi?id=415836 David Edmundson changed: What|Removed |Added Target Milestone|1.0 |--- Component|general |general Assignee|k...@davidedmundson.co.uk|jgrul...@redhat.com Product|plasmashell |plasma-nm -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 415239] KDE plasma shell crashes on login
https://bugs.kde.org/show_bug.cgi?id=415239 David Edmundson changed: What|Removed |Added Version|5.17.4 |unspecified Product|plasmashell |print-manager Assignee|k...@davidedmundson.co.uk|dantt...@gmail.com Component|general |general Target Milestone|1.0 |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415953] Plasma Desktop Manager keeps crashing
https://bugs.kde.org/show_bug.cgi?id=415953 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |BACKTRACE --- Comment #1 from David Edmundson --- Crashes should have a backtrace otherwise we can't do much https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415984] Kickoff uses dialogs/background.svgz instead of dialogs/kickoff.svgz
https://bugs.kde.org/show_bug.cgi?id=415984 --- Comment #1 from David Edmundson --- >Is something missing here? Has it been renamed? No, it's just a subtle behaviour change we've had since 5.0. I'm not sure if it's worth fixing as it's quite a feature creep to have themes do something on a per-widget basis and this is the first report we've got since 5.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416017] Switching windows with the mouse wheel does not work
https://bugs.kde.org/show_bug.cgi?id=416017 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- Can you confirm it works again if you run: system settings -> screen edges -> switch on edge to disabled -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Kevin changed: What|Removed |Added CC||ke...@vanthiel.it -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415301] Plasma crashes after enabling Display configuration in System Tray Settings
https://bugs.kde.org/show_bug.cgi?id=415301 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #8 from David Edmundson --- We can't do much until there's a backtrace from kscreen, marking as needsinfo -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414326] PlasmaShell 100% CPU
https://bugs.kde.org/show_bug.cgi?id=414326 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from David Edmundson --- Firstly can you run - running "kcmshell5 qtquicksettings" and setting the render loop to basic and report if that makes a difference and report back. Secondly: >Run Kde from startx (start system in runlevel 3) Running kde from startx is not supported, as I have wasted too much time in the past dealing with what have turned out to be user setup issues. Please reopen whilst launching from sddm - output of env - output of xrandr -q - ideally a snapshot of gdb of what plasmashell is doing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 414478] User Should definitely be warned every time an Invalid filename is used!
https://bugs.kde.org/show_bug.cgi?id=414478 --- Comment #3 from jc_josue3...@hotmail.com --- OK, clearly this bug is more general as it affects not just Dolphin but Kdenlive. So, what is needed is to fix it not just in Dolphin but on any other KDE software that is affected as well. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Kwrite not working.
https://bugs.kde.org/show_bug.cgi?id=415986 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Should this be filed against kwrite and not against okular? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370726] Text selection tool highlight unintelligible
https://bugs.kde.org/show_bug.cgi?id=370726 Xu Zhao changed: What|Removed |Added CC||i...@xuzhao.net --- Comment #2 from Xu Zhao --- Can confirm this on Okular 1.9.0. Any progress on this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416030] New: Plasma has started crashing frequently. I don't know the root cause, I haven't been able to work it out.
https://bugs.kde.org/show_bug.cgi?id=416030 Bug ID: 416030 Summary: Plasma has started crashing frequently. I don't know the root cause, I haven't been able to work it out. Product: plasmashell Version: 5.17.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: t...@tim-richardson.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.3.13-custom x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: plasma crashes, I don't know why. It's happening every few hours, this problem started only in the past three days. The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x7ff187a79e61 in KIO::DropJob::setApplicationActions(QList const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #7 0x7ff1720ff874 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #8 0x7ff172100740 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so [...] #10 0x7ff182956237 in KIO::TransferJob::mimetype(KIO::Job*, QString const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #11 0x7ff182956e12 in KIO::TransferJob::slotMimetype(QString const&) () at /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5 Possible duplicates by query: bug 415994, bug 415991, bug 415960, bug 415956, bug 415955. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416030] Plasma has started crashing frequently. I don't know the root cause, I haven't been able to work it out.
https://bugs.kde.org/show_bug.cgi?id=416030 --- Comment #1 from Tim Richardson --- Created attachment 124985 --> https://bugs.kde.org/attachment.cgi?id=124985=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415727] a6f7aaa67aca9864f7802d170ec6a408176c6870 causes crash when visiting Settings page
https://bugs.kde.org/show_bug.cgi?id=415727 David Edmundson changed: What|Removed |Added Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #3 from David Edmundson --- Following up on an IM chat. Valgrind log shows a mixup of self-built discover with distro plugin. That commit is an incompatiable change and causes a bug - but not a real one. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 415950] 100% CPU usage of plasmashell
https://bugs.kde.org/show_bug.cgi?id=415950 Mal Haak changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Mal Haak --- (In reply to Kai Uwe Broulik from comment #1) > Download status is updated only every second. > > I believe it's the typical busy indicator (the spinning icon in your tray) > causing excess CPU issue on some GPUs bug... That could well be the issue however I don't see this issue with other tasks that cause the spinning icon, say a copy in Dolphin or NetworkManager trying to connect to wifi. Wait, I just tested the browser integration and its not doing it. Was a fix for this busy indicator pushed recently? I think I've updated since I lodged this bug report. Yep I have, Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Kernel Version: 5.4.8-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.5 GiB of RAM I also have an update to the NVIDIA driver that also seems to have fixed/changed DPI detection to match behavior seen on Intel. So that's a plus. Anyway, it seems to be working so I'm going to close my ticked as resolved. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 415976] KDEConnect increases bluetooth buffer size, leading to laggy sound in bluetooth headset via pulseaudio
https://bugs.kde.org/show_bug.cgi?id=415976 --- Comment #1 from Florian --- The situation seems to be a bit more complex than I thought: When I first started my desktop computer today (this is the device I experienced the audio lag), reinstalled KDEConnect with Bluetooth support and tried to reproduce the issue (prior to applying your code), nothing happened: No lag, no buffer increases anymore. However, after booting up my second computer (a laptop also running KDE, KDEConnect and with an enabled bluetooth adapter), the buffer increases started on the desktop computer again when playing audio. Watching the bluetooth systray of KDE on both computers, I noticed that both systems connected or tried to connect each other via bluetooth from time to time. Whenever this happened for the first time while playing audio, the buffer increased like this: I: [bluetooth] module-bluez5-device.c: Changing bluetooth buffer size: Changed from 5120 to 6144 I: [bluetooth] module-bluez5-device.c: Changing bluetooth buffer size: Changed from 6144 to 7168 I: [bluetooth] module-bluez5-device.c: Changing bluetooth buffer size: Changed from 7168 to 8192 Now I am not sure if the KDEConnect tool is responsible for this after all, even though during my tests yesterday it was clearly related. Anyway, I somehow managed to stop the automatic pairing tries of the systems and now the system behaviour regarding audio playback seems to be ok (even with KDEConnect with Bluetooth support running). BUT whenever I manually I press the "Connect" button in the KDE bluetooth systray applet to connect the desktop to the laptop via bluetooth while playing audio, I will immediately reproduce the same 3 buffer increases. Since I usually don't use this function, and somehow was able to stop the automatic connection attempts, the problem seems to be solved for me right now. Meanwhile, a pulseaudio developer told me that the buffer increases happen because there is some delay in the audio, so it is a reaction to the delay, not the cause. And he suggested to me to change the line size_t new_write_block_size = u->a2dp_codec->reduce_encoder_bitrate(u->encoder_info, u->write_link_mtu); to size_t new_write_block_size = 0; in module-bluez5-device.c I tried this out while the systems were still in the state that they tried to connect each other via bluetooth from time to time. So, whenever this happened, the audio would stutter for a short time, before continuing to play normally - until the next connection attemp, when it stuttered again. However, this way the audio stayed in sync with the videogame. In general, I think the original pulseaudio behaviour, to increase the buffer size, seems to be good for the use case of listening music. Because it will only stutter once, then increase the buffer, and be OK for the rest of the time. (but might be out of sync with video or game) The modified behaviour is not perfect because of regular stuttering that might occur, but that might be acceptable for gaming, because at least this way the audio will stay synchronized with the game. I hope this documentation will help others experience similar issues. This might not be a KDEConnect bug, but maybe it could be a general bug in the KDE bluetooth system (after all, just pressing the "Connect" button in the bluetooth systray applet to try to connect a different device will reproduce this) or just a general bluetooth software or hardware problem. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 415727] a6f7aaa67aca9864f7802d170ec6a408176c6870 causes crash when visiting Settings page
https://bugs.kde.org/show_bug.cgi?id=415727 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- --- Comment #2 from Nate Graham --- Now it's happening again. :( -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416019] Edit Shapes Tool misbehaves while dragging/bending certain imported paths
https://bugs.kde.org/show_bug.cgi?id=416019 --- Comment #3 from Cebtenzzre --- Created attachment 124984 --> https://bugs.kde.org/attachment.cgi?id=124984=edit Reproducer #2 with workaround applied Created with: $ svgcleaner --allow-bigger-file --apply-transform-to-paths=yes reproducer2.svg reproducer2_workaround.svg -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416016] Akonadi can no longer start : /run/user/1000/akonadi problem
https://bugs.kde.org/show_bug.cgi?id=416016 Xabi Leon changed: What|Removed |Added CC||xabi_l...@yahoo.fr Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416019] Edit Shapes Tool misbehaves while dragging/bending certain imported paths
https://bugs.kde.org/show_bug.cgi?id=416019 --- Comment #2 from Cebtenzzre --- Created attachment 124983 --> https://bugs.kde.org/attachment.cgi?id=124983=edit Reproducer #2 An SVG that needs a different workaround -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416027] Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 Christoph Feck changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416016] Akonadi can no longer start : /run/user/1000/akonadi problem
https://bugs.kde.org/show_bug.cgi?id=416016 Nicholas Istre changed: What|Removed |Added CC||nickis...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416027] Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 sac changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from sac --- Thanks for the tip. I tried it and activated "allow resizing maximized windows from window edges". Then I was only able to resize windows at the corner. However, I reverted it back to defaults with resizing maximized windows deactivated and now I can correctly close. Seems this was just a glitch on my side. Many thanks ;) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416019] Edit Shapes Tool misbehaves while dragging/bending certain imported paths
https://bugs.kde.org/show_bug.cgi?id=416019 --- Comment #1 from Cebtenzzre --- With a different imported SVG that had the same problem, I was able to work around the issue by extracting the vector layer from the .kra and running the following command: $ svgcleaner --no-defaults --allow-bigger-file --paths-to-relative=yes --apply-transform-to-paths=yes original.svg cleaned.svg Then I replaced the layer in the .kra with the new SVG. This didn't work without --apply-transform-to-paths=yes so this seems to be different from (but related to) the original attached reproducer, which has no transform attributes. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 385885] Multi-monitor HiDPI screens with scaling: Rectangular Region mode causes graphical corruption on one of the screens
https://bugs.kde.org/show_bug.cgi?id=385885 --- Comment #40 from tamius@gmail.com --- Here's something I noticed about this bug while playing around with xprop. I ran this command: $ sleep 5; xprop -id $(xdotool search --pid `pidof spectacle`) and ran spectacle --region in the 5 second grace period before the command ran. Here is a section of the output: [ begin output ]--- _NET_WM_NAME(UTF8_STRING) = "Spectacle" WM_CLASS(STRING) = "spectacle", "spectacle" WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_W WM_NORMAL_HINTS(WM_SIZE_HINTS): user specified location: -864, 0 user specified size: 11583 by 2159 program specified resize increment: 1 by 1 program specified base size: -1 by -1 window gravity: Static [ end output ]--- That's funny. "User specified location" is negative by the exact amount of pixels the preview gets offset by (and user specified size is one pixel less than my desktop resolution — 11584 x 2160). I assume this is the spectacle's "select rectangular region" window on which one draws rectangular selection. The "easy" solution/workaround for this bug could be to set spectacle's rectangular select window location to 0,0 and disallow other offsets (especially the negative ones, as they'd put spectacle off screen). # TRYING WORKAROUNDS — UNSUCCESSFUL I'm just leaving this here in order to save two minutes of anyone who thinks about trying to work around this bug with kwin window rules. Specifying kwin window rules didn't work. I tried the following: In 'window matching' tab: * 'spectacle' for window class (substring match) * 'Spectacle' (exact match) for window title (WM_CLASS and _NET_WM_NAME)) * all window types selected In 'size' tab: * [*] Position Force 0,0 Nothing happened. Spectacle kept being offset. # TRYING WORKAROUND — SUCCESSFUL 0. Create and open new file. 1. Paste this in (indent optional, it's present for visibility reasons) #!/bin/bash (sleep 2; xdotool windowmove $(xdotool search --pid `pidof spectacle` | tail -n 1) 0 0) & spectacle --region 2. Save the file. Make it executable. 3. Go to custom keyboard shortcuts. Create new shortcut. You can use the same keyboard shortcut as you already do (the old shortcut is useless anyway) or use a new one. 3. In the 'Action' tab, select this file as command/url 4. That's it, really Some side notes: * You absolutely DO need to put that command in a file. The command from step 1 didn't work if used as command directly. I had to put it in a file. * If this still doesn't work for you, try adding the file to your $PATH on startup * Just as a curiosity — according to my experience playing around in the terminal, it seems important that the xdotool bit goes first and spectacle last. If I tried to run it the other way around, that is: spectacle --region & sleep 5; Nothing would happen in this case. Side side note: I don't know enough about C/C++ to whip up a proper patch for this or else I would. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 416027] Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 Nate Graham changed: What|Removed |Added Assignee|visual-des...@kde.org |unassigned-b...@kde.org CC||n...@kde.org Resolution|--- |WAITINGFORINFO Component|Theme - Breeze |window decoration Target Milestone|1.0 |--- Status|REPORTED|NEEDSINFO Version|master |unspecified Product|plasmashell |Breeze --- Comment #2 from Nate Graham --- I'm willing to bet that's it, yeah. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416029] Webdav - problems with delete operation on folders
https://bugs.kde.org/show_bug.cgi?id=416029 Chromaluna <1...@pimpex.com> changed: What|Removed |Added Summary|Webdav - problems with |Webdav - problems with |operations on folders |delete operation on folders -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416029] New: Webdav - problems with operations on folders
https://bugs.kde.org/show_bug.cgi?id=416029 Bug ID: 416029 Summary: Webdav - problems with operations on folders Product: dolphin Version: 19.12.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: 1...@pimpex.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Folders in connected Webdav folder can not be deleted. They can be moved into other subfolder, renamed, but not deleted. STEPS TO REPRODUCE 1. Install Manjaro Linux with KDE https://osdn.net/dl/manjaro/manjaro-kde-18.1.5-191229-linux54.iso 2. Install updates - Dolphin v.19.12.0 3. add new network connection: webdav, server webdav.magentacloud.de, user: usern...@t-online.de, port 443, path /. 4. create folder 5. delete created folder. OBSERVED RESULT In Dolphin, after confirmation by clicking on "delete" button inside are you sure to delete popup window, the folder disapears but after pressing F5 (refresh) en empty screen is shown and no other folders and files are shown. In addition, few seconds later a warning text appears at the top of Dolphin window "File or folder webdavs://username%40t-online...@webdav.magentacloud.de:443/folder/subfolder does not exists" but after clicking on path line the parent folder shows up correctly and in subfolder we have also the correct view but the deleted folder still appears. EXPECTED RESULT Selected folder should be deleted permanently. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: manjaro-kde-18.1.5-191229-linux54.iso, (available in About System) Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.17.4 KDE-Frameworks-Version: 5.65.0 Qt-Version: 5.14.0 Kernel-Version: 5.3.18-1-MANJARO Art des Betriebssystems: 64-bit Prozessoren: 4 × Intel® Core™ i5 CPU M 560 @ 2.67GHz Speicher: 5,7 GiB Arbeitsspeicher KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION - maybe it has something to do with @ character in username? (which is stored as %40)? - Bug 209508 has anything to do with it? "/" at the end of command - do you need any additional log files? - davfs not installed, used only clean new installation Manjaro on board code - you can have free 10GB webdav space for testing at Telekom.de if needed - https://cloud.telekom-dienste.de/ Please help.. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416026] after update firefox to 72.0.1 kwin crashes
https://bugs.kde.org/show_bug.cgi?id=416026 --- Comment #4 from rafrey --- I reinstall old from timeshift ok. Reboot and update && upgrade all, for exemple plasma-desktop/bionic 4:5.17.5-0xneon+18.04+bionic+build68 amd64 [actualizable desde: 4:5.17.4-0xneon+18.04+bionic+build67] and the same problem. kwin: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN12KDecoration215DecoratedClient25hasApplicationMenuChangedEb systemsettings window decorations crashes, etc. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416028] New: "Search in Tags" selection for Face detection/recognition unduly changes
https://bugs.kde.org/show_bug.cgi?id=416028 Bug ID: 416028 Summary: "Search in Tags" selection for Face detection/recognition unduly changes Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY In the Face Detection/Recognition settings, when you switch from "Detect faces" to "Recognize faces", Tags selection is lost. STEPS TO REPRODUCE 1. in "Worklow" tab, select "Detect faces" 2. in "Search in" tab > "Tags" tab: 2a. unselect "Whole tags collection" 2b. select some Tags 3. in "Worklow" tab, select "Recognize faces" Result: Go back to "Search in" tab: the selection of tags (step 2b above) is not saved: all tags are now selected Same problem if you inversely switch from "Recognize faces" to "Detect faces" (except that now no tag is selected) SOFTWARE/OS VERSIONS digikam-7.0.0-beta2-20200108T085258-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #17 from David Edmundson --- As you're on gentoo, can you be sure to re-emerge plasma-workspace after you upgraded Qt to rule that out? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 415415] Renaming tag groups can produce tags with id=0
https://bugs.kde.org/show_bug.cgi?id=415415 --- Comment #3 from Johannes Zarl-Zierl --- Git commit 93dd93f195c03d6cb4bcab0fce7357f6161fe7e9 by Johannes Zarl-Zierl. Committed on 08/01/2020 at 21:59. Pushed by johanneszarl into branch 'master'. Display message when manual repair is needed In addition to the log messages, display a GUI message when categories with id=0 were found in the database and some of them could not be repaired automatically (i.e. more than one tag with id=0 in the same category). M +25 -1XMLDB/FileReader.cpp https://commits.kde.org/kphotoalbum/93dd93f195c03d6cb4bcab0fce7357f6161fe7e9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #16 from David Edmundson --- I think maybe this bug we're seeing is user's running plasma compiled against Qt5.13 on 5.14 - we introduced a change in startplasma, but we made that switch at compile time, which is arguably not right. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018
--- Comment #5 from Nicofo ---
(In reply to Maik Qualmann from comment #4)
> We have this reported as an error several times. I have never been able to
> reproduce it here. Only the selected albums are scanned. I've debugged the
> code many times, I can't imagine digiKam making a mistake here.
Where is the mistake then ? ... How can I help ?
I made new tests: in "Search in":
1) No Album selected, No Tag selected -> as said before, the entire collection
seems to be scanned (this is NOT as expected: I expect nothing is scanned).
2) No Album selected, One Tag selected -> only pictures tagged with that people
are scanned (don't know if it is as expected, because for me Tags should not be
related to face detection)
Note that I don't understand why it is possible to restrict the face detection
to some face Tags ? Face detection should be made possible for specified Albums
("Search in" > "Albums" tab) but NOT for specified people ("Search in" > "Tags"
tab) because this is only face detection, not face recognition. In the
detection phase, you obviously do not know if it corresponds to some Tag
people.
Sorry but for me the UI for face detection/recognition is very confusing (or
buggy?).
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 416027] Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 Hugo Pereira Da Costa changed: What|Removed |Added CC||hugo.pereira.da.costa@gmail ||.com --- Comment #1 from Hugo Pereira Da Costa --- Hi Thanks for reporting the issue. I cannot reproduce unfortunately. Can you check, in the breeze decoration settings, whether you have the option "allow resizing maximized windows from window edges" ? If checked, can you uncheck it and try to reproduce again ? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415943] Preferences (Appearence/Advanced options) window navigation bars when not needed
https://bugs.kde.org/show_bug.cgi?id=415943 --- Comment #3 from Christos --- Aha! ') "So it totally seems intentional" Intentional as: this is a good way for the windows to show scrollbars (WONTFIX) or as: this shouldn't be like this but that is how it has been designed? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416026] after update firefox to 72.0.1 kwin crashes
https://bugs.kde.org/show_bug.cgi?id=416026 --- Comment #3 from rafrey --- sorry in the first commentary have a error. Linux Mint 19.2 and 18.3 no is: Linux Mint 19.2 and 19.3 tricia. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416026] after update firefox to 72.0.1 kwin crashes
https://bugs.kde.org/show_bug.cgi?id=416026 --- Comment #2 from rafrey --- Another tip. I have install xfce4-notes and it's ok with barr and max. min. close buttons. Thank you -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415891] Project file loads perfectly fine in seconds in 4.1.7, never finishes loading in 4.2.8
https://bugs.kde.org/show_bug.cgi?id=415891 --- Comment #22 from to...@offensivelytolerant.com --- (In reply to Boudewijn Rempt from comment #21) > The debug output should be the same, and the backtrace is fairly clear. It's > just that I cannot reproduce it :-( That's weird... I have it everywhere here ( = on the mentioned x230, but also on a older x200, Intel core 2 duo from maybe 2009, but the OS is almost exactly the same) Command line mode for trying to export the sample file into a PNG gets stuck the same way too. Will try with a regular Debian live CD in the following days to see if it makes a difference -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415400] Okular stumbles while scrolling through a heavy epub
https://bugs.kde.org/show_bug.cgi?id=415400 --- Comment #3 from Albert Astals Cid --- > I don't understand how a plaintext document can be rendered so inefficiently. I'm eagerly awaiting your patches that will make everything so much better. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416027] New: Window close button is not positioned correctly in the corner
https://bugs.kde.org/show_bug.cgi?id=416027 Bug ID: 416027 Summary: Window close button is not positioned correctly in the corner Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: mila...@eclipso.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. open a window that has a close button 2. maximize the window 3. move the mouse cursor (blindly) in the very upper right corner (blindly move the mouse diagonally) 4. click OBSERVED RESULT the window is not closed EXPECTED RESULT window should close, as it does with the plastik theme, where the close button is correctly in the outmost corner. Should have some importance, because I think most people move the mouse blindly to the corner, and then expect the window to close after click, without aming for the close button. 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.
[kwin] [Bug 416026] after update firefox to 72.0.1 kwin crashes
https://bugs.kde.org/show_bug.cgi?id=416026 --- Comment #1 from rafrey --- In -systemsettings5/Application Style/Window Decorations- crash. Trace: Application: systemsettings5 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: The crash can be reproduced every time. -- Backtrace: Application: Preferencias del sistema (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe201d99800 (LWP 4994))] Thread 6 (Thread 0x7fe1c6e7c700 (LWP 5559)): #0 0x7fe1fd2cbbf9 in __GI___poll (fds=0x7fe1c0004e00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe1f69805c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe1f69806dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe1fdc1eb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1fdbbf06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1fd9da3aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe1fb77d815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe1fd9dbb52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe1f8d3f6db in start_thread (arg=0x7fe1c6e7c700) at pthread_create.c:463 #9 0x7fe1fd2d888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fe1cf36c700 (LWP 5218)): #0 0x7fe1fd2cbbf9 in __GI___poll (fds=0x7fe1c8003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe1f69805c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe1f69806dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe1fdc1eb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1fdbbf06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1fd9da3aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe1fb77d815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe1fd9dbb52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe1f8d3f6db in start_thread (arg=0x7fe1cf36c700) at pthread_create.c:463 #9 0x7fe1fd2d888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fe1d87df700 (LWP 5152)): #0 0x7fe1fd2cbbf9 in __GI___poll (fds=0x7fe1d0004a00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe1f69805c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe1f69806dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe1fdc1eb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1fdbbf06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1fd9da3aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe1fb77d815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe1fd9dbb52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe1f8d3f6db in start_thread (arg=0x7fe1d87df700) at pthread_create.c:463 #9 0x7fe1fd2d888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fe1e5b37700 (LWP 5013)): #0 0x7fe1fd2cbbf9 in __GI___poll (fds=0x7fe1e0004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe1f69805c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe1f69806dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe1fdc1eb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe1fdbbf06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe1fd9da3aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe1fe0950e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe1fd9dbb52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe1f8d3f6db in start_thread (arg=0x7fe1e5b37700) at pthread_create.c:463 #9 0x7fe1fd2d888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe1eec69700 (LWP 4996)): #0 0x7fe1fd2cbbf9 in __GI___poll (fds=0x7fe1eec68ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe1f8903747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe1f890536a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fe1f1a4ee10 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fe1fd9dbb52 in ??
[kwin] [Bug 416026] New: after update firefox to 72.0.1 kwin crashes
https://bugs.kde.org/show_bug.cgi?id=416026 Bug ID: 416026 Summary: after update firefox to 72.0.1 kwin crashes Product: kwin Version: 5.17.5 Platform: Neon Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: raf...@protonmail.com Target Milestone: --- SUMMARY Operating System: KDE neon 5.17 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 Kernel Version: 5.0.0-37-generic OS Type: 64-bit Processors: 4 × AMD Phenom(tm) II X4 955 Processor Memory: 7,8 GiB STEPS TO REPRODUCE 1. update firefox to 72.0.1 2. 3. OBSERVED RESULT kwin crashes EXPECTED RESULT all ok ADDITIONAL INFORMATION └─ $ ▶ kwin kwin: symbol lookup error: /usr/lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol: _ZN12KDecoration215DecoratedClient25hasApplicationMenuChangedEb This problem repeat in Linux Mint 19.2 and 18.3 but unknow update or install an app. Reinstall libkwin (kwin-common, kwin_x11, etc.) and the problem persist. Sorry for my poor english, iam spanish. regards. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416025] New: Sorting by name takes the dot of file extension into account when sorting files
https://bugs.kde.org/show_bug.cgi?id=416025 Bug ID: 416025 Summary: Sorting by name takes the dot of file extension into account when sorting files Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sephiroth...@hotmail.it CC: kfm-de...@kde.org Target Milestone: --- Created attachment 124982 --> https://bugs.kde.org/attachment.cgi?id=124982=edit File sorting example SUMMARY The current implementation of natural sorting takes the dot of the file extension into account, and this makes it so that files with numbers in their name are shown before those with the same name but without numbers. It seems like the dot of the extension is treated as part of the file name; while it is indeed part of the file name in UNIX-like OSes due to magic numbers, from a user perspective this is unintuitive as we humans treat the file name and the extension as two separate things, with the dot acting as the separator. STEPS TO REPRODUCE 1. create three files: "file.txt", "file 2.txt", "file 3.txt"; 2. use sorting by name. OBSERVED RESULT The files are shown in the following order: "file 2.txt", "file 3.txt", "file.txt". EXPECTED RESULT The files should be sorted in what we might call a "natural" way: files with a space and a number following their name should come after those without space and number in their file name. This behaviour is seen in all other desktop environments (e.g. GNOME) and operating systems (e.g. Windows). SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415943] Preferences (Appearence/Advanced options) window navigation bars when not needed
https://bugs.kde.org/show_bug.cgi?id=415943 Juraj changed: What|Removed |Added CC||sgd.or...@gmail.com --- Comment #2 from Juraj --- The scrollbars are same (I believe) all over the preferences dialog, not only the Themes section. Just go and resize the preferences windows and you will see that the scrollbars shows and disappears at the same moment on most of the views. On second thought it probably sets minimal with to show scrollbars based on the biggest previously opened "page". So it totally seems intentional. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 --- Comment #4 from Maik Qualmann --- (In reply to Nicofo from comment #2) > No: same result if no tags are selected We have this reported as an error several times. I have never been able to reproduce it here. Only the selected albums are scanned. I've debugged the code many times, I can't imagine digiKam making a mistake here. Maik -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 415399] Context menu of apps is shadowless on Wayland
https://bugs.kde.org/show_bug.cgi?id=415399 --- Comment #5 from Patrick Silva --- Created attachment 124981 --> https://bugs.kde.org/attachment.cgi?id=124981=edit shadowless context menu from the window decoration Context menu and menus from the menu bar have shadow again. But the context menu from the window decoration is shadowless. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.17.80 KDE Frameworks Version: 5.66.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[cervisia] [Bug 416021] Improve cervisia column sorting
https://bugs.kde.org/show_bug.cgi?id=416021 --- Comment #1 from d...@duradsl.duckdns.org --- Added two phabricator patches: https://phabricator.kde.org/D26534 https://phabricator.kde.org/D26536 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 --- Comment #3 from Maik Qualmann --- Git commit b904cf973b004d0f483efa63c4e8f6676068e7db by Maik Qualmann. Committed on 08/01/2020 at 21:06. Pushed by mqualmann into branch 'master'. disable "Clear unconfirmed results and rescan" option Because face detection and recognition are currently deactivated M +10 -1core/utilities/facemanagement/widgets/facescanwidget.cpp https://invent.kde.org/kde/digikam/commit/b904cf973b004d0f483efa63c4e8f6676068e7db -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413650] KDE Connect bug restarting after windows wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=413650 --- Comment #4 from Odin Vex --- I'd like to add, I'm using kdeconnect-kde-master-263-windows-msvc2017_64-cl.exe. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416024] New: Krunner crashes every time I try to open it
https://bugs.kde.org/show_bug.cgi?id=416024 Bug ID: 416024 Summary: Krunner crashes every time I try to open it Product: krunner Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: hgono...@gmail.com Target Milestone: --- Application: krunner (5.17.4) Qt Version: 5.13.1 Frameworks Version: 5.65.0 Operating System: Linux 5.3.12-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Alt+Space [the opening short cut] results in the communicate about a crash being shown and it just quits. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7fb75c394400 (LWP 23871))] Thread 4 (Thread 0x7fb75187e700 (LWP 23874)): #0 0x7fb76071ebdf in __GI___poll (fds=0x7fb7480025e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb75d42f2ee in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb75d42f40f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb75ea5698b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fb75e9ff0cb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb75e837021 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fb75ff023b5 in ?? () from /usr/lib64/libQt5Qml.so.5 #7 0x7fb75e8381a2 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7fb75dde0f2a in start_thread (arg=) at pthread_create.c:479 #9 0x7fb7607294af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fb75961d700 (LWP 23873)): #0 0x7fb75d47a604 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7fb75d42e86d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7fb75d42f21b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x7fb75d42f40f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7fb75ea5698b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fb75e9ff0cb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fb75e837021 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7fb75f2d04f6 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x7fb75e8381a2 in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x7fb75dde0f2a in start_thread (arg=) at pthread_create.c:479 #10 0x7fb7607294af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb75a2c2700 (LWP 23872)): #0 0x7fb76071ebdf in __GI___poll (fds=0x7fb75a2c1ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb75e2bd742 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fb75e2be3fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fb75a4c6f90 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fb75e8381a2 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7fb75dde0f2a in start_thread (arg=) at pthread_create.c:479 #6 0x7fb7607294af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb75c394400 (LWP 23871)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7fb76064f55d in __GI_abort () at abort.c:79 #8 0x7fb75e7ffa97 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5 #9 0x7fb76025ccfd in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib64/libQt5Quick.so.5 #10 0x7fb76027bea4 in ?? () from /usr/lib64/libQt5Quick.so.5 #11 0x7fb76027bf73 in ?? () from /usr/lib64/libQt5Quick.so.5 #12 0x7fb75ee0b96d in QWindow::event(QEvent*) () from /usr/lib64/libQt5Gui.so.5 #13 0x7fb7602de889 in QQuickWindow::event(QEvent*) () from /usr/lib64/libQt5Quick.so.5 #14 0x7fb76060e223 in PlasmaQuick::Dialog::event(QEvent*) () from /usr/lib64/libKF5PlasmaQuick.so.5 #15 0x559f7e71084f in ?? () #16 0x7fb75f4cdc62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7fb75f4d71e0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7fb75ea00562 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7fb75ee01f72 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib64/libQt5Gui.so.5 #20 0x7fb75ee02194 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from
[kdeconnect] [Bug 413650] KDE Connect bug restarting after windows wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=413650 Odin Vex changed: What|Removed |Added CC||odin.vex@ethicalexploiting. ||com --- Comment #3 from Odin Vex --- I have the same problem. At any time, KDE Connect can completely "just not work" unless I restart it. Even then, it can take quite a bit of time (a minute, maybe half an hour) for KDE Connect to begin working again. Eventually I will get "Failed to execute program org.kde.kdeconnect: The system cannot...(find the file specified)..." Meanwhile, my phone and laptop can see each other and respond to one another with no issues. Firewalls have been disabled for testing but make no difference. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409803] "Enable clipboard actions" missing from context menu
https://bugs.kde.org/show_bug.cgi?id=409803 Jeff Trull changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409803] "Enable clipboard actions" missing from context menu
https://bugs.kde.org/show_bug.cgi?id=409803 --- Comment #2 from Jeff Trull --- Created attachment 124980 --> https://bugs.kde.org/attachment.cgi?id=124980=edit UI element referring to nonexistent control -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 409803] "Enable clipboard actions" missing from context menu
https://bugs.kde.org/show_bug.cgi?id=409803 Jeff Trull changed: What|Removed |Added CC||jetr...@sbcglobal.net --- Comment #1 from Jeff Trull --- The irony here (and what I came to report) is the documentation and at least one UI control refer to a "Enable clipboard actions" control - which does not exist. Attached is an error message that refers to it - but there is no such control when you right-click on klipper. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 --- Comment #2 from Nicofo --- No: same result if no tags are selected -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 416023] New: (Script) preview window should show less obstrusive message while updating
https://bugs.kde.org/show_bug.cgi?id=416023 Bug ID: 416023 Summary: (Script) preview window should show less obstrusive message while updating Product: rkward Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: thomas.friedrichsme...@ruhr-uni-bochum.de Target Milestone: --- (Script) preview window should show less obstrusive message while updating. Instead of the red-ish message box, perhaps an animated "loading" icon in the header (or footer) would suffice? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 416022] Treat underscores as symbols instead of letters
https://bugs.kde.org/show_bug.cgi?id=416022 Riccardo Robecchi changed: What|Removed |Added CC||sephiroth...@hotmail.it -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 416022] New: Treat underscores as symbols instead of letters
https://bugs.kde.org/show_bug.cgi?id=416022 Bug ID: 416022 Summary: Treat underscores as symbols instead of letters Product: frameworks-ktexteditor Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: sephiroth...@hotmail.it Target Milestone: --- SUMMARY Underscores are currently treated as letters instead of symbols, making it impossible to use "ctrl+right/left" to navigate text which uses underscores as separator characters. STEPS TO REPRODUCE 1. write "this_is_a_text_using_underscores_as_separators" and "this-time-we-are-using-hyphens"; 2. use "ctrl+right/left" to navigate through the words; 3. see how the first text is treated as a whole word, instead of multiple words using underscores as separator characters, while the second one is correctly identified as being made of multiple used with hyphens used as separators. OBSERVED RESULT Underscores are treated like letters, so long sequences of characters using underscores as separators are treated as if they were a single word. This is especially frustrating if one has to select a portion of text inside a string which uses underscores as separators. EXPECTED RESULT Underscores are treated the same as all other symbols such as hyphens, commas, dots and so on, so that one can navigate text using "ctrl+right/left". As far as I have been able to asses GNOME follows this convention, which appears more intuitive and practical. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.13.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Check the Tag tab, you have probably also selected something there, these will be added to the search. Definitely only the albums that are selected will be scanned. Maik -- You are receiving this mail because: You are watching all bug changes.
[cervisia] [Bug 416021] New: Improve cervisia column sorting
https://bugs.kde.org/show_bug.cgi?id=416021 Bug ID: 416021 Summary: Improve cervisia column sorting Product: cervisia Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: christian.lo...@hamburg.de Reporter: d...@duradsl.duckdns.org Target Milestone: --- Created attachment 124979 --> https://bugs.kde.org/attachment.cgi?id=124979=edit Patch that correct this issues. SUMMARY - When sorting by Status column, the list is not sorted. - When sorting by Revision, Tag or Timestamp, the name alphabetical order is not maintained. STEPS TO REPRODUCE 1. Sort list by Status, Revision, Tag or Timestamp by clicking column header. OBSERVED RESULT The list is not sorted properly. EXPECTED RESULT The list is sorted properly. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Cervisia: 19.12.0 ADDITIONAL INFORMATION The attached patch correct this issues. I will put it on phabricator if I'm allowed to. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 416020] New: No smb-connection to Router/Server "FRITZ.BOX"
https://bugs.kde.org/show_bug.cgi?id=416020 Bug ID: 416020 Summary: No smb-connection to Router/Server "FRITZ.BOX" Product: krusader Version: 2.7.1 Platform: RedHat RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: net-connection Assignee: krusader-bugs-n...@kde.org Reporter: lp...@freenet.de CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Klick "Mount man" 2. Insert Adress name & P$Wd 3. you get : in DE Version: "Fehler: Interner Fehler Bitte senden Sie einen ausführlichen Problembericht an https://bugs.kde.org Unbekannte Fehlersituation in stat: Das Programm verursachte einen Abbruch der Verbindung. " [unfortuately i can't Cut this text and must retype it.] With the former Fedora (and SW-Version) it works fine. It is broken sinse update to Fedora 31. OBSERVED RESULT the above message EXPECTED RESULT an ftp/smb connection to the Fritz-NAS SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 31 (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.
[krita] [Bug 416019] New: Edit Shapes Tool misbehaves while dragging/bending certain imported paths
https://bugs.kde.org/show_bug.cgi?id=416019 Bug ID: 416019 Summary: Edit Shapes Tool misbehaves while dragging/bending certain imported paths Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: cebtenz...@gmail.com Target Milestone: --- Created attachment 124978 --> https://bugs.kde.org/attachment.cgi?id=124978=edit Reproduces the bug when opened in Krita SUMMARY When using the Edit Shapes Tool to bend a curve from certain imported paths, the curve is moved to the wrong place and the undo history is corrupted. The SVG that reproduces the issue is attached as reproducer.svg. I have been able to reproduce this simply by saving an SVG in Inkscape and opening it in Krita. An apparent workaround is to change the viewBox attribute to viewBox="0 0 1250 750". An apparent way to create a reproducer is to change the viewBox of an SVG saved by Krita to be smaller, e.g. viewBox="0 0 200 300". STEPS TO REPRODUCE 1. Open reproducer.svg in Krita 2. Select the paths and ungroup them 3. Use the Edit Shapes Tool to drag one of the curves, causing it to bend 4. Repeat step 3 but drag in a different direction 5. Attempt to undo steps 3 and 4 OBSERVED RESULT The result of bending the curve is inconsistent with the way it was moved, and often in the opposite direction. When an undo is attempted, the shape continues to bend in directions it was not supposed to. EXPECTED RESULT The curve bends to where the cursor was dragged, just as it normally would. When an undo is attempted, the previous state of the document is correctly restored. Both of these results are observed if the workaround is applied. SOFTWARE/OS VERSIONS Krita: Krita Plus AppImage 4.2.9-alpha (git 0c46041) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 413448] Plasmoid shows a big margin in right side
https://bugs.kde.org/show_bug.cgi?id=413448 Riccardo Robecchi changed: What|Removed |Added CC||sephiroth...@hotmail.it --- Comment #4 from Riccardo Robecchi --- I confirm I am affected by this bug, too. The issue is still present in the latest edition of KDE neon (Plasma 5.17.4, KDE Frameworks 5.65.0, Qt 5.13.2). It shows this bug on both my desktop and my laptop, both with Full-HD resolution and 1x scaling factor. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 416018] New: Face detection: specified list of albums not taken into account
https://bugs.kde.org/show_bug.cgi?id=416018 Bug ID: 416018 Summary: Face detection: specified list of albums not taken into account Product: digikam Version: 7.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Detection Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY When I make a Face Detection with following settings: - in "Worklow" tab, select "Scan again and merge results" or "Clear unconfirmed results and rescan" - in "Worklow" tab, select "Detect faces" - in "Search in" tab, select only a few Albums (of course "Whole albums collection" is not selected) Result: a lot more albums (maybe the entire collection?) are actually scanned. Notes: 1) No problem if I select "Skip images already scanned" 2) The bug is still more visible if in "Search in" I select no Album at all. Obviously the scan process should do nothing, but it's not what happens: a lot of Albums are still scanned. 3) Maybe I don't understand well what the option "Clear unconfirmed and rescan" is supposed to do, but I expected that the "Unconfirmed" people tags are cleared to be face-recognised again. This is not the case (items in "Unconfirmed" people tag are still there, unmodified) Also this is for me confusing: when "Detect faces" is selected, I expect that the scan will only... detect faces (seems obvious). So this is not related with "Unconfirmed" people tag, related to the face recognition process. -> is it normal ? If not I should probably open a new bug report ? 4) For a better comprehension, please use the same wording for "rescan"/"scan again" in: - "Scan again and merge results" - "Clear unconfirmed result and rescan" --> replace "rescan" by "scan again" as above SOFTWARE/OS VERSIONS digikam-7.0.0-beta2-20200108T085258-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
