[plasmashell] [Bug 414768] Plasma crash .... just after reboot, only task running was Disks doing filesystem repair on a SD card
https://bugs.kde.org/show_bug.cgi?id=414768 --- Comment #5 from Christoph Feck --- *** Bug 416975 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416975] Plasma crashed for no apparently reason
https://bugs.kde.org/show_bug.cgi?id=416975 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 414768 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414768] Plasma crash .... just after reboot, only task running was Disks doing filesystem repair on a SD card
https://bugs.kde.org/show_bug.cgi?id=414768 --- Comment #3 from Christoph Feck --- *** Bug 415795 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416409] Plasma crash while using
https://bugs.kde.org/show_bug.cgi?id=416409 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 414768 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414768] Plasma crash .... just after reboot, only task running was Disks doing filesystem repair on a SD card
https://bugs.kde.org/show_bug.cgi?id=414768 --- Comment #4 from Christoph Feck --- *** Bug 416409 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415795] Plasma crash when reenabling disabled monitors after existing Steam
https://bugs.kde.org/show_bug.cgi?id=415795 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 414768 *** -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 415192] The font increase and decrease buttons do not work
https://bugs.kde.org/show_bug.cgi?id=415192 Yuri Chornoivan changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/khe ||lpcenter/c56b981f44d64823ed ||cf558d787a995e11a5e29b Resolution|--- |FIXED --- Comment #12 from Yuri Chornoivan --- Git commit c56b981f44d64823edcf558d787a995e11a5e29b by Yuri Chornoivan. Committed on 31/01/2020 at 06:52. Pushed by yurchor into branch 'release/19.12'. Reload the page after changing the font size Summary: Currently the font size chage does not work because the content is not updated. Test Plan: 1. Open some help file. 2. Click on the "Increase/Decrease font size" buttons. 3. The size of the font should change. Reviewers: #kde_applications Subscribers: kde-doc-english Tags: #documentation Differential Revision: https://phabricator.kde.org/D27046 M +2-0view.cpp https://commits.kde.org/khelpcenter/c56b981f44d64823edcf558d787a995e11a5e29b -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 --- Comment #9 from y...@jacky.wtf --- Haha, I use mine every day but having something to sync the reader with would be nice. Could be the launch of a refresh of this application. Maybe a KDE GSoC project? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416975] New: Plasma crashed for no apparently reason
https://bugs.kde.org/show_bug.cgi?id=416975 Bug ID: 416975 Summary: Plasma crashed for no apparently reason 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.66.0 Operating System: Linux 5.3.10-customrc6 x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Edit documents in Chrome - Unusual behavior I noticed: None. I have three external monitors. This crashing is happening serveral times a day. It's fairly recent, never happened before 5.17. I have multiple monitors. The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x7f1ecfb9ecd6 in QV4::MemoryManager::collectFromJSStack(QV4::MarkStack*) const () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f1ecfb9ed3e in QV4::MemoryManager::collectRoots(QV4::MarkStack*) () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f1ecfb9ef63 in QV4::MemoryManager::mark() () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f1ecfba0db9 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f1ecfba2e56 in QV4::MemoryManager::allocString(unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 Possible duplicates by query: bug 416409, bug 415795, bug 414768, bug 409244, bug 406600. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416975] Plasma crashed for no apparently reason
https://bugs.kde.org/show_bug.cgi?id=416975 --- Comment #1 from Tim Richardson --- Created attachment 125565 --> https://bugs.kde.org/attachment.cgi?id=125565=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416936] Clipping mask when floating
https://bugs.kde.org/show_bug.cgi?id=416936 --- Comment #8 from Michail Vourlakos --- Ok one more time, having a white background window does not help. Please a new video that background is black in order to be able to notice the white area issue and mention also the exact second in the video that you notice it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable
https://bugs.kde.org/show_bug.cgi?id=416973 Kyle Devir changed: What|Removed |Added CC|m.dlubakow...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable
https://bugs.kde.org/show_bug.cgi?id=416973 --- Comment #1 from Kyle Devir --- So... this issue was fixed by editing ~/.config/kiorc ... :/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370356] very slow when delete photos and albums
https://bugs.kde.org/show_bug.cgi?id=370356 --- Comment #4 from caulier.gil...@gmail.com --- 402704 is about dolphin and Plasma trash. digiKam do not use desktop trash which is relevant of KIO and is not portable under MAcOS and Windows. Each collection has a hidden trash folder which is located on top of collection directory. DK trash is has the same place than collection so deleting collection files is just a move on same file system. This is perfect for remote or removable collections. Gillees Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416686] On Windows, make .URL files instead of .desktop when KDE Dolphin creates link to Internet URL
https://bugs.kde.org/show_bug.cgi?id=416686 --- Comment #3 from Murz --- Maybe make this on Linux optional via something like "Make Windows compatible link"? Because often we need to make links on folders, shared with Windows users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416268] Widgets disappear when moved
https://bugs.kde.org/show_bug.cgi?id=416268 --- 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.
[plasmashell] [Bug 416327] Plasma crashes after moving Panel to a different screen edge
https://bugs.kde.org/show_bug.cgi?id=416327 --- 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.
[kwin] [Bug 416974] New: Plasma 5.17.90 crashed due to a kwin_wayland segmentation fault in QWeakPointer::QWeakPointer
https://bugs.kde.org/show_bug.cgi?id=416974
Bug ID: 416974
Summary: Plasma 5.17.90 crashed due to a kwin_wayland
segmentation fault in
QWeakPointer::QWeakPointer
Product: kwin
Version: 5.17.90
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
I was using Plasma 5.17.90 on Wayland in Fedora Rawhide with KF 5.66.0, Qt
5.13.2, Mesa 19.3.3. I started VLC 3.0.9 (from rpmfusion). I played a video and
paused it after a few minutes. Plasma froze for about 3 minutes, and then sddm
appeared. The systemd-coredump process for the kwin_wayland crash didn't
complete correctly possibly due to timing out. I found the kwin_wayland core
dump file in /var/lib/systemd/coredump/ kwin_wayland had a segmentation fault
in
QWeakPointer::QWeakPointer at
/usr/include/qt5/QtCore/qsharedpointer_impl.h:589. The full trace of the
crashing thread 1 showed what looked like a invalid pointer d = 0x20 from
frames 0 to 2 in KWayland::Server::SurfaceInterface::lockedPointer at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/surface_interface.cpp:937.
The underlying problem might be in kwayland.
Core was generated by `/usr/bin/kwin_wayland --xwayland --libinput
--exit-with-session=/usr/libexec/st'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 QWeakPointer::QWeakPointer (other=..., this=0x7fff3257acb0)
at /usr/include/qt5/QtCore/qsharedpointer_impl.h:589
589 /usr/include/qt5/QtCore/qsharedpointer_impl.h: No such file or
directory.
[Current thread is 1 (Thread 0x7fc905ad7900 (LWP 1269))]
(gdb) bt full
#0 QWeakPointer::QWeakPointer(QWeakPointer const&)
(other=..., this=0x7fff3257acb0)
at /usr/include/qt5/QtCore/qsharedpointer_impl.h:589
d = 0x20
#1
QPointer::QPointer(QPointer
const&) (this=0x7fff3257acb0) at /usr/include/qt5/QtCore/qpointer.h:53
d = 0x20
#2 KWayland::Server::SurfaceInterface::lockedPointer() const (this=)
at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/surface_interface.cpp:937
d = 0x20
#3 0x7fc906938809 in
KWayland::Server::PointerInterfaceoperator()
(__closure=)
at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/src/server/pointer_interface.cpp:247
d = 0x5585256ff410
pos = {xp = 6.941689537196333e-310, yp = 6.9531853373731582e-310}
targetSurface =
#4 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KWayland::Server::PointerInterface::PointerInterface(KWayland::Server::SeatInterface*,
wl_resource*):: >::call
(arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#5
QtPrivate::Functor, 0>::call, void> (arg=, f=...)
at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#6
QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=, r=,
a=, ret= for more, q to quit, c to
continue without paging--c
out>) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:439
#7 0x7fc905d74a60 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff3257ae30, r=0x5585255ffd80, this=0x5585256ef150) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
obj = {d = 0x5585256ef150}
receiver = 0x5585255ffd80
receiverInSameThread =
sw = {receiver = 0x5585255ffd80, previousSender = 0x0, currentSender =
{sender = 0x558524d49310, signal = 8, ref = 1}, switched = true}
c = 0x558525704a70
last = 0x5585256118d0
locker = {val = 140501365871928}
connectionLists = {connectionLists = 0x558524d49690}
list =
currentThreadId = 0x7fc905ad7900
signal_index = 8
empty_argv = {0x0}
#8 QMetaObject::activate(QObject*, int, int, void**) (sender=0x558524d49310,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3789
obj = {d = 0x5585256ef150}
receiver = 0x5585255ffd80
receiverInSameThread =
sw = {receiver = 0x5585255ffd80, previousSender = 0x0, currentSender =
{sender = 0x558524d49310, signal = 8, ref = 1}, switched = true}
c = 0x558525704a70
last = 0x5585256118d0
locker = {val = 140501365871928}
connectionLists = {connectionLists = 0x558524d49690}
list =
currentThreadId = 0x7fc905ad7900
signal_index = 8
empty_argv = {0x0}
#9 0x7fc906909899 in
KWayland::Server::SeatInterface::pointerPosChanged(QPointF const&)
(this=this@entry=0x558524d49310, _t1=...) at
/usr/src/debug/kf5-kwayland-5.66.0-1.fc32.x86_64/x86_64-redhat-linux-gnu/src/server/KF5WaylandServer_autogen/EWIEGA46WW/moc_seat_interface.cpp:451
_a = {0x0, 0x7fff3257ae90}
#10 0x7fc906941c02 in
[kwin] [Bug 415379] eglgbmbackend.cpp:Moving the cursor only refreshes the damage area with a black background
https://bugs.kde.org/show_bug.cgi?id=415379 --- 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.
[Akonadi] [Bug 414974] Akonadi crashed while deleting emails
https://bugs.kde.org/show_bug.cgi?id=414974 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[elisa] [Bug 410353] Elisa indexing is spotty for tracks on NTFS disk
https://bugs.kde.org/show_bug.cgi?id=410353 --- Comment #7 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.
[amarok] [Bug 415652] Starting Amarok on FreeBSD 12.1-RELEASE causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=415652 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[krita] [Bug 415086] A file won't "draw"
https://bugs.kde.org/show_bug.cgi?id=415086 --- Comment #6 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.
[kmymoney] [Bug 415768] Scheduled Trans.
https://bugs.kde.org/show_bug.cgi?id=415768 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[kwin] [Bug 416033] Kwin crash with kwin-tiling enabled when launching a VM
https://bugs.kde.org/show_bug.cgi?id=416033 --- Comment #6 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.
[elisa] [Bug 405044] Elisa crashes on execution
https://bugs.kde.org/show_bug.cgi?id=405044 --- Comment #7 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.
[elisa] [Bug 410001] Can't add samba shared folders to Elisa library or even open samba shared audio files
https://bugs.kde.org/show_bug.cgi?id=410001 --- Comment #12 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.
[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable
https://bugs.kde.org/show_bug.cgi?id=416973 Kyle Devir changed: What|Removed |Added Version|unspecified |5.66.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416973] Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable
https://bugs.kde.org/show_bug.cgi?id=416973 Kyle Devir changed: What|Removed |Added Platform|Other |Archlinux Packages CC||kyle.de...@mykolab.com, ||m.dlubakow...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416973] New: Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable
https://bugs.kde.org/show_bug.cgi?id=416973 Bug ID: 416973 Summary: Dolphin won't run binaries or scripts, even when set to always ask on opening, and the binary or script is executable Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: kyle.de...@mykolab.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 125564 --> https://bugs.kde.org/attachment.cgi?id=125564=edit Visual of bug SUMMARY Recently, I noticed that Dolphin was always complaining with "The file is an executable program. For safety it will not be started.", even when Dolphin is set to always ask when I click an executable binary. For scripts, it will just always open them in kate. I decided to do some digging, and I think it might be caused by some odd bug in this commit: 2bb58858c8f6f37b82028bdbc86c19e9acfd71f2, "Added dialog to set execute permission for executable file when trying to run it.", author Marcin Dłubakowski STEPS TO REPRODUCE 1. Set "Settings -> Configure Dolphin -> General -> Confirmations -> When opening an executable file:" to "Always ask" 2. Set binary or script to be executable. 3. Click on binary or script in Dolphin. OBSERVED RESULT "The file is an executable program. For safety it will not be started.", always. EXPECTED RESULT Dolphin asks whether I would like to execute or run the binary or script. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.5.0-arch1-1-custom OS Type: 64-bit Processors: 6 × AMD Ryzen 5 2600X Six-Core Processor Memory: 15.6 GiB of RAM -- 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 Joseph Mitzen changed: What|Removed |Added CC||j...@myself.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #6 from Josh Freeno --- (In reply to Andrius Štikonas from comment #5) > (In reply to Josh Freeno from comment #4) > > (In reply to Andrius Štikonas from comment #3) > > > Unfortunately, without more info, I won't be able to do anything. > > > I just tried with my USB, it works fine. > > > > > > My theory (although I have no strong proof) is that for some reason your > > > Linux kernel marked USB as read only... Note that error happened > > > immediately > > > (in 0 seconds). In that case there is nothing KDE Partition Manager can > > > do... > > > > What more info do you need or want and I will get to you as soon as > > possible. Unless the partition manager is marking it read only then I can > > tell you that is not the problem. > > If you can, try to format the same USB again and see if you can still > reproduce this. > > If yes, try to see more logs by clicking Details button. > > Running "cat /sys/block/sdb/ro" might tell you if device is read only. > Running "dmesg" in terminal might also give some clues. > > ntfs-3g is needed but I think in this case error happens much earlier. You > can't even create partition (formatting partition happens after first > creating unformatted partition). I will look for logs although it happened three or four times on same USB. The very same USB I have formatted with windows to go on it now. I will look though and post here anything I find. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416972] New: Plasmashell, several KDE applications consume 100% CPU, spam notifications and become unresponsive with many overlayfs mounts
https://bugs.kde.org/show_bug.cgi?id=416972 Bug ID: 416972 Summary: Plasmashell, several KDE applications consume 100% CPU, spam notifications and become unresponsive with many overlayfs mounts Product: plasmashell Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DataEngines Assignee: plasma-b...@kde.org Reporter: chris.vanderpen...@gmail.com Target Milestone: 1.0 SUMMARY With many overlayfs mounts present, eg when created by microk8s, several KDE applications and Plasmashell consume 100% CPU, spam notifications and become unresponsive. Possibly related to bug 413110 STEPS TO REPRODUCE 1. Install microk8s: sudo snap install --classic microk8s 2. Run many containers: sudo microk8s.kubectl run nginx --image=nginx --replicas=50 --expose=true --port='80' 3. Tear down: sudo microk8s.kubectl delete service/nginx deployment/nginx ; sudo snap remove --purge microk8s This is likely reproducible by running a bunch of containers in regular Docker, too. OBSERVED RESULT * Kate, Gwenview, Dolphin consume 100% CPU and become partially unresponsive with significant delay responding to inputs * Dolphin begins consuming multiple gigabytes of RAM - Heaptrack suggests most of this goes via Solid::StorageAccess::accessibilityChanged * Plasmashell consumes 100% CPU and spams "Filesystem is not responding" notifications * If the notification backlog is not cleared fast enough, Plasmashell crashes EXPECTED RESULT None of the above should occur SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 19.10 + kubuntu backports PPA (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413110] Plasmashell high CPU, unresponsive, gives "filesystem not responding" with many NFS mounts
https://bugs.kde.org/show_bug.cgi?id=413110 Chris van der Pennen changed: What|Removed |Added CC||chris.vanderpen...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416943] Touchpad Settings Only Shows Built-in Touchpad
https://bugs.kde.org/show_bug.cgi?id=416943 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 414315 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414315] Touchpad select dropdown is disabled even if more than one touchpad is present
https://bugs.kde.org/show_bug.cgi?id=414315 Patrick Silva changed: What|Removed |Added CC||zach.richar...@gmail.com --- Comment #2 from Patrick Silva --- *** Bug 416943 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416954] wastebin icon shows move to wastebin
https://bugs.kde.org/show_bug.cgi?id=416954 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416971] New: Krunner crashes when start typing
https://bugs.kde.org/show_bug.cgi?id=416971 Bug ID: 416971 Summary: Krunner crashes when start typing Product: krunner Version: 5.17.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: framboois...@gmail.com Target Milestone: --- Application: krunner (5.17.5) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.14-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: using shortcut alt + f2 and super + space results in opening searching box on the top of the screen (krunner I assume), nothing wrong happens until I start typing, that results in dialog box show up with the message that krunner crashed. As opposite to marked possible duplicate where krunner crashes right away when started. - Unusual behavior I noticed: seems to be related that, in my system, many things don't work like alt + f1 and super key not starting application launcher, present all windows as keyboard shortcut and hot corners doesn't work - Custom settings of the application: I don't know if it's related but I installed the fingerprint-gui, in order to finish installing yast proposed to downgrade some packages, from the list of dependencies of that app, as far as I can remember it was at least those two packages which were installed instead of a newer ones: libQtCore.so.4 () (64bit) libQtGui.so.4 () (64bit) The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4d34623800 (LWP 5492))] Thread 7 (Thread 0x7f4cf77fe700 (LWP 5501)): #0 0x7f4d38ba7c22 in __libc_disable_asynccancel () at /lib64/libc.so.6 #1 0x7f4d38c16ad3 in poll () at /lib64/libc.so.6 #2 0x7f4d356c52ee in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4d356c5653 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4d1c506c96 in () at /usr/lib64/libgio-2.0.so.0 #5 0x7f4d356ee18e in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f4d3610ff2a in start_thread () at /lib64/libpthread.so.0 #7 0x7f4d38c2138f in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f4cf7fff700 (LWP 5500)): #0 0x7f4d38c16abf in poll () at /lib64/libc.so.6 #1 0x7f4d356c52ee in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4d356c540f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4d356c5461 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4d356ee18e in () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4d3610ff2a in start_thread () at /lib64/libpthread.so.0 #6 0x7f4d38c2138f in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f4d1ee6b700 (LWP 5497)): #0 0x7f4d361166a5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4d36c1a24b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5 #2 0x7f4d36c1a309 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #3 0x7f4d3873a21f in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f4d3873a499 in () at /usr/lib64/libQt5Quick.so.5 #5 0x7f4d36c14708 in () at /usr/lib64/libQt5Core.so.5 #6 0x7f4d3610ff2a in start_thread () at /lib64/libpthread.so.0 #7 0x7f4d38c2138f in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f4d2987e700 (LWP 5496)): #0 0x7f4d356c1f8f in () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4d356c356c in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4d356c4c5f in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4d356c5292 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4d356c540f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4d36e3fbdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4d36de7d5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f4d36c1363e in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f4d383bea65 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f4d36c14708 in () at /usr/lib64/libQt5Core.so.5 #10 0x7f4d3610ff2a in start_thread () at /lib64/libpthread.so.0 #11 0x7f4d38c2138f in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4d318da700 (LWP 5494)): #0 0x7f4d38c124ec in read () at /lib64/libc.so.6 #1 0x7f4d3570c1df in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4d356c4e47 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f4d356c5292 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f4d356c540f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f4d36e3fbdb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6
[Spectacle] [Bug 416970] New: Spectacle -b copy copies image URI instead of image.
https://bugs.kde.org/show_bug.cgi?id=416970 Bug ID: 416970 Summary: Spectacle -b copy copies image URI instead of image. Product: Spectacle Version: 19.12.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: waterlub...@rocketmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 125563 --> https://bugs.kde.org/attachment.cgi?id=125563=edit Video of the issue. I have spectacle configured in keyboard shortcuts so "Shift+PrtSc" captures a rectangular region. (This runs spectacle -br, as far as I can tell.) This works, however, I cannot copy the resulting image directly to my clipboard. Instead, it is immediately saved (because of the "background" option) and the copy action in the window in the lower-right hand corner of the screen merely copies its file *path* instead of the actual image data This makes pasting images very tedious. Spectacle run with full GUI happily copies images to my clipboard, and spectacle run with `spectacle -r` also allows me to copy to clipboard. Attached is a video that should make this much clearer. Suggested behavior: spectacle -b (background screenshot)'s notification's copy menu should copy the image data, rather than the URI, to be consistent with the rest of the application. I'm currently just setting a custom bind of spectable -r for the meantime. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416969] New: System settings crashes on startup
https://bugs.kde.org/show_bug.cgi?id=416969 Bug ID: 416969 Summary: System settings crashes on startup Product: systemsettings Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: archpol...@gmail.com Target Milestone: --- Application: systemsettings5 (5.14.5) Qt Version: 5.12.5 Frameworks Version: 5.62.0 Operating System: Linux 5.4.0-3-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: I was starting the application through Alt+F2 (krunner). It crashes every time I try running it with no exception. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2cd35e9cc0 (LWP 557762))] Thread 5 (Thread 0x7f2cc1a95700 (LWP 557774)): #0 0x7f2cd7c5bd1f in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2cd597010e in g_main_context_poll (priority=, n_fds=1, fds=0x7f2cb4004e30, timeout=, context=0x7f2cb4000bf0) at ../../../glib/gmain.c:4216 #2 g_main_context_iterate (context=context@entry=0x7f2cb4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3912 #3 0x7f2cd597022f in g_main_context_iteration (context=0x7f2cb4000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3978 #4 0x7f2cd81d888b in QEventDispatcherGlib::processEvents (this=0x7f2cb4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f2cd818178b in QEventLoop::exec (this=this@entry=0x7f2cc1a94d40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f2cd7fc2751 in QThread::exec (this=this@entry=0x5636c14e7d40) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f2cd72f7845 in QQmlThreadPrivate::run (this=0x5636c14e7d40) at qml/ftw/qqmlthread.cpp:148 #8 0x7f2cd7fc38d2 in QThreadPrivate::start (arg=0x5636c14e7d40) at thread/qthread_unix.cpp:361 #9 0x7f2cd6419fb7 in start_thread (arg=) at pthread_create.c:486 #10 0x7f2cd7c662df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:103 #11 0x in ?? () Thread 4 (Thread 0x7f2cc379a700 (LWP 557766)): #0 0x7f2cd7c5bd1f in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2cd597010e in g_main_context_poll (priority=, n_fds=1, fds=0x7f2cbc004a30, timeout=, context=0x7f2cbc000bf0) at ../../../glib/gmain.c:4216 #2 g_main_context_iterate (context=context@entry=0x7f2cbc000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3912 #3 0x7f2cd597022f in g_main_context_iteration (context=0x7f2cbc000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3978 #4 0x7f2cd81d888b in QEventDispatcherGlib::processEvents (this=0x7f2cbc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f2cd818178b in QEventLoop::exec (this=this@entry=0x7f2cc3799d40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f2cd7fc2751 in QThread::exec (this=this@entry=0x5636c13fc540) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #7 0x7f2cd72f7845 in QQmlThreadPrivate::run (this=0x5636c13fc540) at qml/ftw/qqmlthread.cpp:148 #8 0x7f2cd7fc38d2 in QThreadPrivate::start (arg=0x5636c13fc540) at thread/qthread_unix.cpp:361 #9 0x7f2cd6419fb7 in start_thread (arg=) at pthread_create.c:486 #10 0x7f2cd7c662df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:103 #11 0x in ?? () Thread 3 (Thread 0x7f2cd0fe2700 (LWP 557764)): #0 0x7f2cd7c5bd1f in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2cd597010e in g_main_context_poll (priority=, n_fds=1, fds=0x7f2cc4004e30, timeout=, context=0x7f2cc4000bf0) at ../../../glib/gmain.c:4216 #2 g_main_context_iterate (context=context@entry=0x7f2cc4000bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:3912 #3 0x7f2cd597022f in g_main_context_iteration (context=0x7f2cc4000bf0, may_block=may_block@entry=1) at ../../../glib/gmain.c:3978 #4 0x7f2cd81d888b in QEventDispatcherGlib::processEvents (this=0x7f2cc4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #5 0x7f2cd818178b in QEventLoop::exec (this=this@entry=0x7f2cd0fe1d30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #6 0x7f2cd7fc2751 in QThread::exec (this=this@entry=0x7f2cd84d6d80 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 --- Comment #10 from Patrick Silva --- This crash is still reproducible on Arch Linux (Plasma 5.18 beta) and Neon unstable edition. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #5 from Andrius Štikonas --- (In reply to Josh Freeno from comment #4) > (In reply to Andrius Štikonas from comment #3) > > Unfortunately, without more info, I won't be able to do anything. > > I just tried with my USB, it works fine. > > > > My theory (although I have no strong proof) is that for some reason your > > Linux kernel marked USB as read only... Note that error happened immediately > > (in 0 seconds). In that case there is nothing KDE Partition Manager can > > do... > > What more info do you need or want and I will get to you as soon as > possible. Unless the partition manager is marking it read only then I can > tell you that is not the problem. If you can, try to format the same USB again and see if you can still reproduce this. If yes, try to see more logs by clicking Details button. Running "cat /sys/block/sdb/ro" might tell you if device is read only. Running "dmesg" in terminal might also give some clues. ntfs-3g is needed but I think in this case error happens much earlier. You can't even create partition (formatting partition happens after first creating unformatted partition). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #4 from Josh Freeno --- (In reply to Andrius Štikonas from comment #3) > Unfortunately, without more info, I won't be able to do anything. > I just tried with my USB, it works fine. > > My theory (although I have no strong proof) is that for some reason your > Linux kernel marked USB as read only... Note that error happened immediately > (in 0 seconds). In that case there is nothing KDE Partition Manager can do... What more info do you need or want and I will get to you as soon as possible. Unless the partition manager is marking it read only then I can tell you that is not the problem. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416936] Clipping mask when floating
https://bugs.kde.org/show_bug.cgi?id=416936 --- Comment #7 from gregorystar...@gmail.com --- (In reply to Michail Vourlakos from comment #5) Hello, the show timer has no effect with it. It occurs every time the dock is raised/lowered. Mask is less of a correct word, its more like a white overlay that fits the shape of the lower part of the dock. It appears when raising, and lowering. It is a bit subtle, but very noticeable in person. Video is here: https://drive.google.com/file/d/1OipxsfdlLxJBK654_byWoI67JIPRPQPb/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416964] "AutoSkip" is not a word and the button's functionality is unclear
https://bugs.kde.org/show_bug.cgi?id=416964 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416964] "AutoSkip" is not a word and the button's functionality is unclear
https://bugs.kde.org/show_bug.cgi?id=416964 --- Comment #2 from Patrick Silva --- (In reply to Nate Graham from comment #1) > Yeah. What does the "AutoSkip" behavior even do? It's not at all obvious. I do not know either. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416964] "AutoSkip" is not a word and the button's functionality is unclear
https://bugs.kde.org/show_bug.cgi?id=416964 Nate Graham changed: What|Removed |Added Product|dolphin |frameworks-kio Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org Component|general |general CC||kdelibs-b...@kde.org, ||n...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED Version|unspecified |git master Summary|"AutoSkip" button should be |"AutoSkip" is not a word |labeled "Auto Skip" |and the button's ||functionality is unclear --- Comment #1 from Nate Graham --- Yeah. What does the "AutoSkip" behavior even do? It's not at all obvious. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416968] Using the KDE Partition manager to format disk causes Dell touchpad tap-to-click to stop working
https://bugs.kde.org/show_bug.cgi?id=416968 Andrius Štikonas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Andrius Štikonas --- That's probably duplicate of 413973. In principle this is not a bug in partition manager but some time ago I added a workaround to avoid triggering that bug. The workaround is not released yet, it will be part of next release. *** This bug has been marked as a duplicate of bug 413973 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413973] Editing partitions resets touchpad configuration
https://bugs.kde.org/show_bug.cgi?id=413973 Andrius Štikonas changed: What|Removed |Added CC||freefreen...@gmail.com --- Comment #34 from Andrius Štikonas --- *** Bug 416968 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #3 from Andrius Štikonas --- Unfortunately, without more info, I won't be able to do anything. I just tried with my USB, it works fine. My theory (although I have no strong proof) is that for some reason your Linux kernel marked USB as read only... Note that error happened immediately (in 0 seconds). In that case there is nothing KDE Partition Manager can do... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 --- Comment #2 from Josh Freeno --- (In reply to Andrius Štikonas from comment #1) > What are the errors? > > Does "mkfs.ntfs --quick --verbose deviceNode" work? Screenshot is of what is does every time and I tried this three or four times but I finally just put into my windows PC and formatted it so I did not try to manually do it. I have package ntfs-3g installed too. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416968] New: Using the KDE Partition manager to format disk causes Dell touchpad tap-to-click to stop working
https://bugs.kde.org/show_bug.cgi?id=416968 Bug ID: 416968 Summary: Using the KDE Partition manager to format disk causes Dell touchpad tap-to-click to stop working Product: partitionmanager Version: 4.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: freefreen...@gmail.com Target Milestone: --- Created attachment 125562 --> https://bugs.kde.org/attachment.cgi?id=125562=edit Screenshot after using the application SUMMARY Using the KDE Partition manager to format disk causes Dell touch pad tap-to-click to stop working and makes all the settings under tapping become greyed out until logging out and back into the desktop. STEPS TO REPRODUCE 1. Use KDE Partition manager to format disk 2. Close close the app 3. OBSERVED RESULT Tap-to-click stops working on touch pad EXPECTED RESULT Should not have any effect on touch pad at all SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.15-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION All the selections under tapping in input settings become greyed out until logging out and back into the desktop. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Andrius Štikonas --- What are the errors? Does "mkfs.ntfs --quick --verbose deviceNode" work? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 416967] New: KDE Partition manager fails to format USB with ntfs
https://bugs.kde.org/show_bug.cgi?id=416967 Bug ID: 416967 Summary: KDE Partition manager fails to format USB with ntfs Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: freefreen...@gmail.com Target Milestone: --- Created attachment 125561 --> https://bugs.kde.org/attachment.cgi?id=125561=edit Screenshot of error SUMMARY NTFS format fails STEPS TO REPRODUCE 1. Open KDE Partition manager 2. Try to format USB with ntfs 3. OBSERVED RESULT It fails with errors EXPECTED RESULT Format USB with ntfs without errors SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.15-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416966] option to set hibernate/suspend as default action for the "Leave" screen
https://bugs.kde.org/show_bug.cgi?id=416966 daniel-other+kde...@dadosch.de changed: What|Removed |Added CC||daniel-other+kdebug@dadosch ||.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416966] New: option to set hibernate/suspend as default action for the "Leave" screen
https://bugs.kde.org/show_bug.cgi?id=416966 Bug ID: 416966 Summary: option to set hibernate/suspend as default action for the "Leave" screen Product: plasmashell Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: daniel-other+kde...@dadosch.de Target Milestone: 1.0 SUMMARY currently, it is only possible to either end the session, turn PC off or reboot. However, if hibernate and suspend are available, they should also be available to be setup as a default action for the leave screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 416965] k3b - Application de gravure de CB/DVD pour GNOME / k3b - CB / DVD burning application for GNOME
https://bugs.kde.org/show_bug.cgi?id=416965 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- I don't see any GNOME mention in k3b source code. Please open a bug against opensuse. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416894] krita full screen in wrong monitor
https://bugs.kde.org/show_bug.cgi?id=416894 --- Comment #6 from Mobin --- my 2nd monitor is an "xp pen artist 12" (pen display tablet) and beside color it does not manage anything. resolution and dpi are covered by windows. (right now on 1080p same as my main monitor but with 150% dpi -my main is 100%-) if I disable the dpi in krita It will fix black borders but I still have the fullscrean problem that just only favors my main monitor not were is is placed or have more coverage. On Fri, Jan 31, 2020 at 1:42 AM Ahab Greybeard wrote: > https://bugs.kde.org/show_bug.cgi?id=416894 > > --- Comment #5 from Ahab Greybeard --- > Are your monitors identical? > Are there any OS level utilities and controls whose settings could have an > effect on this? (Right-click on desktop then Display Settings.) > (I rarely use Windows nowadays so I've lost familiarity with it.) > > I forgot to add my system information but I don't know if it would be of > any > help to anyone in solving this problem: > > Krita > > Version: 4.3.0-prealpha (git 0657457) > Languages: en_US, en > Hidpi: false > > Qt > > Version (compiled): 5.12.5 > Version (loaded): 5.12.5 > > OS Information > > Build ABI: x86_64-little_endian-llp64 > Build CPU: x86_64 > CPU: x86_64 > Kernel Type: winnt > Kernel Version: 10.0.16299 > Pretty Productname: Windows 10 (10.0) > Product Type: windows > Product Version: 10 > > OpenGL Info > > Vendor: "NVIDIA Corporation" > Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" > Version: "4.6.0 NVIDIA 388.13" > Shading language: "4.60 NVIDIA" > Requested format: QSurfaceFormat(version 3.0, options > QFlags(DeprecatedFunctions), depthBufferSize > 24, > redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, > stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, > swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile > QSurfaceFormat::CompatibilityProfile) > Current format:QSurfaceFormat(version 4.6, options > QFlags(DeprecatedFunctions), depthBufferSize > 24, > redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, > stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, > swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile > QSurfaceFormat::CompatibilityProfile) > Version: 4.6 > Supports deprecated functions true > is OpenGL ES: false > > QPA OpenGL Detection Info > supportsDesktopGL: true > supportsAngleD3D11: true > isQtPreferAngle: false > > Hardware Information > > GPU Acceleration: auto > Memory: 16381 Mb > Number of Cores: 8 > Swap Location: /tmp > > Current Settings > > Current Swap Location: /tmp > Undo Enabled: 1 > Undo Stack Limit: 20 > Use OpenGL: 1 > Use OpenGL Texture Buffer: 1 > Use AMD Vectorization Workaround: 0 > Canvas State: OPENGL_SUCCESS > Autosave Interval: 360 > Use Backup Files: 1 > Number of Backups Kept: 1 > Backup File Suffix: ~ > Backup Location: Same Folder as the File > Use Win8 Pointer Input: 1 > Use RightMiddleTabletButton Workaround: 0 > Levels of Detail Enabled: 1 > Use Zip64: 0 > > > Display Information > Number of screens: 2 > Screen: 0 > Name: \\.\DISPLAY2 > Depth: 32 > Scale: 1 > Resolution in pixels: 1280x1024 > Manufacturer: > Model: > Refresh Rate: 60 > Screen: 1 > Name: \\.\DISPLAY1 > Depth: 32 > Scale: 1 > Resolution in pixels: 1280x1024 > Manufacturer: > Model: > Refresh Rate: 60 > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416419] KWIN freezed
https://bugs.kde.org/show_bug.cgi?id=416419 --- Comment #1 from stefan...@posteo.de --- I've got a complete reboot now! Operating System: Arch Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 Kernel Version: 5.4.15-arch1-1 OS Type: 64-bit Jan 30 23:46:11 STEFANO-ARCHLINUX plasmashell[1221]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:454: TypeError: Cannot read property 'length' of undefined Jan 30 23:46:11 STEFANO-ARCHLINUX plasmashell[1221]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:371: Unable to assign [undefined] to QString Jan 30 23:46:12 STEFANO-ARCHLINUX kdeinit5[7754]: Qt: Session management error: networkIdsList argument is NULL Jan 30 23:46:21 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 33493, resource id: 71303190, major code: 18 (ChangeProperty), minor code: 0 Jan 30 23:46:22 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 34048, resource id: 33981875, major code: 3 (GetWindowAttributes), minor code: 0 Jan 30 23:46:22 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 34049, resource id: 33981875, major code: 14 (GetGeometry), minor code: 0 Jan 30 23:46:22 STEFANO-ARCHLINUX kmix[1241]: org.kde.kmix: Could not get icon for "SMPlayer" Jan 30 23:46:22 STEFANO-ARCHLINUX kmix[1241]: org.kde.kmix: Could not get icon for "SMPlayer" Jan 30 23:46:32 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 40805, resource id: 33982341, major code: 2 (ChangeWindowAttributes), minor code: 0 Jan 30 23:46:32 STEFANO-ARCHLINUX plasmashell[1221]: qml: applet destroyed Jan 30 23:46:32 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41065, resource id: 88080509, major code: 18 (ChangeProperty), minor code: 0 Jan 30 23:46:32 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 41086, resource id: 71303191, major code: 18 (ChangeProperty), minor code: 0 Jan 30 23:46:38 STEFANO-ARCHLINUX dolphin[7743]: Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") Jan 30 23:50:41 STEFANO-ARCHLINUX kwin_x11[1215]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 63796, resource id: 85983240, major code: 18 (ChangeProperty), minor code: 0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416616] Feature request: extract audio from cropped clips in the timeline
https://bugs.kde.org/show_bug.cgi?id=416616 CzAndrew changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from CzAndrew --- I just tried this, and it works! Thank you for the info! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396576] Re-implementing the old behavior of Isolate Layer used on Group Layers
https://bugs.kde.org/show_bug.cgi?id=396576 vanyossi changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||ghe...@gmail.com --- Comment #2 from vanyossi --- Isolate layer is designed to isolate the current layer only. Previous behaviour was a bug. You can achieve the same workflow using the layer visibility toggles. - Shift+Click over the eye icon of the group layer to turn visibility on for all the layers in that group and turn off all other layer visibility. To revert to previous state, shift+click again over the same layer eye icon. - Shift + Ctrl + click. over the eye icon of the group layer to turn visibility off for all layers outside that group. To revert to previous state, shift+click again over the same layer eye icon. The blue eye state, indicates you are in a temporary state, if you normal click any eye icon the color will go back to normal. In that case the previous original state will be overwritten. Visibility state is separated from isolate layer functionality, so you can shift+click the group, and isolate a single layer in the group further refine visibility. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 416965] New: k3b - Application de gravure de CB/DVD pour GNOME / k3b - CB / DVD burning application for GNOME
https://bugs.kde.org/show_bug.cgi?id=416965 Bug ID: 416965 Summary: k3b - Application de gravure de CB/DVD pour GNOME / k3b - CB / DVD burning application for GNOME Product: k3b Version: 19.12 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@kde.org Reporter: o.g.m.bell...@gmail.com CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 125559 --> https://bugs.kde.org/attachment.cgi?id=125559=edit Screenshot of yast showing K3B description in french SUMMARY In the French description of K3B it is presented as "k3b - CB / DVD burning application for GNOME" I checked the openSUSE spec: there is no GNOME that got lost there ... I guess a Troll wants to make some noise! Dans le description en français de K3B il est présenter ainsi "k3b - Application de gravure de CB/DVD pour GNOME" J'ai vérifié le spec de openSUSE : il n'y a pas de GNOME qui s'y soit égaré… Je suppose qu'un Troll veut faire un peu de bruit ! EXPECTED RESULT "k3b - Application de gravure de CB/DVD pour KDE" bien sûrs ! "k3b - CB / DVD burning application for KDE" of course! ADDITIONAL INFORMATION I sincerely hope that no Gnome or Troll will suffer from the correction of this error. J'espère de tout coeur qu'aucun Gnome ou Troll n'aura à souffrir de la correction de cette erreur. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416652] Empty items in system tray area
https://bugs.kde.org/show_bug.cgi?id=416652
Konrad Materka changed:
What|Removed |Added
Attachment #125539|0 |1
is obsolete||
Attachment #125540|0 |1
is obsolete||
--- Comment #16 from Konrad Materka ---
Created attachment 125558
--> https://bugs.kde.org/attachment.cgi?id=125558=edit
session bus monitor logs (cleared)
My investigation:
There are 3 parties involved:
:1.10 = org.kde.StatusNotifierWatcher
:1.33 = org.freedesktop.Notifications = com.canonical.Unity = plasmashell
:1.763 - Telegram
Tray icon is created twice:
> Sender=:1.33 Destination=org.kde.StatusNotifierWatcher
> Path=/StatusNotifierWatcher Interface=org.kde.StatusNotifierWatcher
> Member=RegisterStatusNotifierItem -> ":1.765"
> Sender=:1.763 Destination=org.kde.StatusNotifierWatcher
> Path=/StatusNotifierWatcher Interface=org.kde.StatusNotifierWatcher
> Member=RegisterStatusNotifierItem -> ":1.766"
The ":1.765" is immediately destroyed. I was able to observe similar behavior
with snap package on my computer to.
There is a race condition, if service is destroyed too soon,
StatusNotifierWatcher can't notice it. From StatusNotifierWatcher cpp:
//check if the service has registered a SystemTray object
org::kde::StatusNotifierItem trayclient(service, path,
QDBusConnection::sessionBus());
if (trayclient.isValid()) { // it exists here
m_registeredServices.append(notifierItemId); // it dies here
m_serviceWatcher->addWatchedService(service); // it is dead by now, no
chance to get notification
emit StatusNotifierItemRegistered(notifierItemId);
}
Race condition is a problem on it's own, but bigger issue is: why plasmashell
is creating SNI? For a brief moment there a SNI object with hidden menu with
only one item: toggled checkbox.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 416652] Empty items in system tray area
https://bugs.kde.org/show_bug.cgi?id=416652 Konrad Materka changed: What|Removed |Added Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416652] Empty items in system tray area
https://bugs.kde.org/show_bug.cgi?id=416652 Konrad Materka changed: What|Removed |Added Status|REOPENED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416964] New: "AutoSkip" button should be labeled "Auto Skip"
https://bugs.kde.org/show_bug.cgi?id=416964 Bug ID: 416964 Summary: "AutoSkip" button should be labeled "Auto Skip" Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 125557 --> https://bugs.kde.org/attachment.cgi?id=125557=edit screenshot SUMMARY See the attached screenshot. Current label looks weird without a space before a uppercase character. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.67.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 415256] Random Segmentation fault while Firefox open
https://bugs.kde.org/show_bug.cgi?id=415256 --- Comment #3 from pyro4h...@gmail.com --- another one [15546.198956] kwin_wayland[726]: segfault at 297f5dfd31ec ip 7f8d2093d9ee sp 7ffd08ac5410 error 4 in libKF5WaylandServer.so.5.66.0[7f8d208f2000+63000] [15546.198965] Code: 08 48 85 d2 74 04 f0 83 02 01 4c 89 e0 41 5c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 54 49 89 fc 48 89 f7 ff 15 ca c5 05 00 <48> 8b 90 38 02 00 00 48 8b 80 40 02 00 00 49 89 14 24 49 89 44 24 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416894] krita full screen in wrong monitor
https://bugs.kde.org/show_bug.cgi?id=416894 --- Comment #5 from Ahab Greybeard --- Are your monitors identical? Are there any OS level utilities and controls whose settings could have an effect on this? (Right-click on desktop then Display Settings.) (I rarely use Windows nowadays so I've lost familiarity with it.) I forgot to add my system information but I don't know if it would be of any help to anyone in solving this problem: Krita Version: 4.3.0-prealpha (git 0657457) Languages: en_US, en Hidpi: false Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.16299 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "NVIDIA Corporation" Renderer: "GeForce GTX 750 Ti/PCIe/SSE2" Version: "4.6.0 NVIDIA 388.13" Shading language: "4.60 NVIDIA" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 4.6, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile QSurfaceFormat::CompatibilityProfile) Version: 4.6 Supports deprecated functions true is OpenGL ES: false QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: false Hardware Information GPU Acceleration: auto Memory: 16381 Mb Number of Cores: 8 Swap Location: /tmp Current Settings Current Swap Location: /tmp Undo Enabled: 1 Undo Stack Limit: 20 Use OpenGL: 1 Use OpenGL Texture Buffer: 1 Use AMD Vectorization Workaround: 0 Canvas State: OPENGL_SUCCESS Autosave Interval: 360 Use Backup Files: 1 Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Use Win8 Pointer Input: 1 Use RightMiddleTabletButton Workaround: 0 Levels of Detail Enabled: 1 Use Zip64: 0 Display Information Number of screens: 2 Screen: 0 Name: \\.\DISPLAY2 Depth: 32 Scale: 1 Resolution in pixels: 1280x1024 Manufacturer: Model: Refresh Rate: 60 Screen: 1 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1280x1024 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416557] Screen after "Switch User" option shows normal login screen with currently logged user
https://bugs.kde.org/show_bug.cgi?id=416557 --- Comment #13 from Piotr Mierzwinski --- I found that in distribution KaOS it works well. Only I didn't test multi-monitor configuration. In this moment seems this is issue related with my distribution (or only my instance this distribution). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402704] Dolphin is slow to send to trash several small files located in a NTFS partition
https://bugs.kde.org/show_bug.cgi?id=402704 --- Comment #4 from Patrick Silva --- The issue shown in my screen recording is still happening regardless trash size limit is enabled or not in Dolphin 19.12.1 preferences. Operating System: Arch Linux KDE Plasma Version: 5.17.90 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416963] After the migration to aq6 the change of views takes a long time
https://bugs.kde.org/show_bug.cgi?id=416963 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.5,8.0.5 |4.8.5,5.0.9 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 416106] Save a screenshot to clipboard without the screenshot GUI
https://bugs.kde.org/show_bug.cgi?id=416106 daniel-other+kde...@dadosch.de changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #6 from daniel-other+kde...@dadosch.de --- You can do so by adding a short key to the printscreen in you system's setting which executes spectacle -b -c or, if you wish to have no notification: spectacle -b -c -n (but this doesn't work with old versions, see #411263) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416963] After the migration to aq6 the change of views takes a long time
https://bugs.kde.org/show_bug.cgi?id=416963 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kmy ||money/6606907b497bf88979db4 ||f34627c7c96743864ff Version Fixed In||4.8.5 Status|REPORTED|RESOLVED --- Comment #2 from Ralf Habacker --- Git commit 6606907b497bf88979db4f34627c7c96743864ff by Ralf Habacker. Committed on 30/01/2020 at 21:51. Pushed by habacker into branch '4.8'. Fix 'After the migration to aq6 the change of views takes a long time ' This commit also avoids flooding console with AqBanking warnings This problem does not occur until aq6, which indicates that the timing of aliases has deteriorated there. The loop over the accounts was moved to the outside to improve performance. FIXED-IN:4.8.5,5.0.8 M +19 -15 kmymoney/mymoney/onlinejobadministration.cpp https://commits.kde.org/kmymoney/6606907b497bf88979db4f34627c7c96743864ff --- Comment #1 from Ralf Habacker --- Git commit 5a4edfa8c2602e2e25d2bcda4f579a72ee6aae03 by Ralf Habacker. Committed on 30/01/2020 at 21:47. Pushed by habacker into branch '4.8'. Provide method to check for online mapping Added a method to retrieve information if an account is mapped to an online banking account and use it where appropriate Cherry picked from commit 93aa0838e26ec4ae25f648e9fe49c80d8e774424 M +6-6kmymoney/kmymoney.cpp M +5-1kmymoney/mymoney/mymoneyaccount.cpp M +5-0kmymoney/mymoney/mymoneyaccount.h https://commits.kde.org/kmymoney/5a4edfa8c2602e2e25d2bcda4f579a72ee6aae03 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416963] After the migration to aq6 the change of views takes a long time
https://bugs.kde.org/show_bug.cgi?id=416963 Ralf Habacker changed: What|Removed |Added Version Fixed In|4.8.5 |4.8.5,8.0.5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416963] After the migration to aq6 the change of views takes a long time
https://bugs.kde.org/show_bug.cgi?id=416963 --- Comment #1 from Ralf Habacker --- Git commit 5a4edfa8c2602e2e25d2bcda4f579a72ee6aae03 by Ralf Habacker. Committed on 30/01/2020 at 21:47. Pushed by habacker into branch '4.8'. Provide method to check for online mapping Added a method to retrieve information if an account is mapped to an online banking account and use it where appropriate Cherry picked from commit 93aa0838e26ec4ae25f648e9fe49c80d8e774424 M +6-6kmymoney/kmymoney.cpp M +5-1kmymoney/mymoney/mymoneyaccount.cpp M +5-0kmymoney/mymoney/mymoneyaccount.h https://commits.kde.org/kmymoney/5a4edfa8c2602e2e25d2bcda4f579a72ee6aae03 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414025] Jagged lines when canvas is too big and zoom out, it makes impossible to draw a smooth circle
https://bugs.kde.org/show_bug.cgi?id=414025 --- Comment #11 from vanyossi --- (In reply to Lissette from comment #8) Hi Lisette, could you test something to try and get better performance (It might or it might not work, but its worth a shot) - Locate kritarc: on macOS is usually in ~/Library/Preferences/kritarc - Open with a text editor add "textureSize=4096" as the first line. The number can be any power of 2. preferably anything like 256, 512, 1024, etc)The number upper limit depends on your hardware, on mine the number is somwhere around 10k, however I don't recommend going that higher. - Save the file - Start krita. Inside Krita Preferences, Display, Canvas Graphics acceleration should be on, and select OpenGL This should make possible to draw on big canvases zommed out. I tested with a 12000 by 12000 canvas at 4% zoom let me know if that helped -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370356] very slow when delete photos and albums
https://bugs.kde.org/show_bug.cgi?id=370356 Danny changed: What|Removed |Added CC||riverheart...@gmail.com --- Comment #3 from Danny --- On Reddit we are discussing the possibility that slow delete performance may be related to the size limit option. Performance seems to be greatly increased. Is it possible that every delete operation iterates the entire contents of the recycling bin to determine the size, or there's some other slow code path that happens through that option? I also noticed that file move operations are similarly much faster with the option unchecked, so this issue could be bigger than it seems. This may be related to #402704 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416716] Some dialogs are created off screen
https://bugs.kde.org/show_bug.cgi?id=416716 vanyossi changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from vanyossi --- Do you happen to know the Qt version you have installed? Arch repos tend to have recent versions of software. Since we have no control of where the Windows will be placed, that is decided by the window manager, Im inclined to think you have a Qt version >=5.13 which are known to be buggy. For krita we stick with 5.12.4 for the moment. I will mark as not a bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402704] Dolphin is slow to send to trash several small files located in a NTFS partition
https://bugs.kde.org/show_bug.cgi?id=402704 Danny changed: What|Removed |Added CC||riverheart...@gmail.com --- Comment #3 from Danny --- Does this have something to do with size limiting the recycle bin? On Reddit we seem to have all noticed a slowdown when recycling via Dolphin, if the size limit is enabled. It's possible the bug only takes effect with a full bin, I don't know on that one. Is there any change KIO could be iterating the entire trash folder to determine current size? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416894] krita full screen in wrong monitor
https://bugs.kde.org/show_bug.cgi?id=416894 --- Comment #4 from Mobin --- I have it on git 1164b81 and I have this problem with dpi as well: run on monitor one 100% and monitor 2nd has 150% scaling On Fri, Jan 31, 2020 at 12:23 AM Ahab Greybeard wrote: > https://bugs.kde.org/show_bug.cgi?id=416894 > > Ahab Greybeard changed: > >What|Removed |Added > > > CC| > |ahab.greybe...@hotmail.co.u >||k > > --- Comment #3 from Ahab Greybeard --- > I don't have this on Windows 10 with the Jan 30th 4.3.0-prealpha (git > 0657457) > standalone .zip. > > It goes to full screen on whatever monitor has the majority of the window > on it > then returns to its previous shape and size and placement. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391088] Pan tool shortcut inactive a few moments after docker widget interaction.
https://bugs.kde.org/show_bug.cgi?id=391088 vanyossi changed: What|Removed |Added CC||samuel.lostiousness@gmail.c ||om --- Comment #6 from vanyossi --- *** Bug 416849 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416849] Lag happened in alternating the hand tool and brush tool
https://bugs.kde.org/show_bug.cgi?id=416849 vanyossi changed: What|Removed |Added Status|REPORTED|RESOLVED CC||ghe...@gmail.com Resolution|--- |DUPLICATE --- Comment #2 from vanyossi --- This bug is the same as 391088, which is related to focus switching and is intentional. Bassically we have a timer after doing interactions with widgets outise of canvas to grab the focus. Using the Overview docker, this does not happen when clicking the preview, but using zoom or rotation controls the bahavior is the same as 391088 *** This bug has been marked as a duplicate of bug 391088 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 391088] Pan tool shortcut inactive a few moments after docker widget interaction.
https://bugs.kde.org/show_bug.cgi?id=391088 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Summary|Pan tool shortcut inactive |Pan tool shortcut inactive |after layer selection |a few moments after docker ||widget interaction. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 416850] Performance profiling does not work
https://bugs.kde.org/show_bug.cgi?id=416850 Eugene Shalygin changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-81767 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 416850] Performance profiling does not work
https://bugs.kde.org/show_bug.cgi?id=416850 Eugene Shalygin changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Eugene Shalygin --- Does not work in Otter to, seems to be a Qt bug -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416963] After the migration to aq6 the change of views takes a long time
https://bugs.kde.org/show_bug.cgi?id=416963 Ralf Habacker changed: What|Removed |Added Summary|After migration to aq6 the |After the migration to aq6 |finding of aliases takes a |the change of views takes a |long time |long time -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 416963] New: After migration to aq6 the finding of aliases takes a long time
https://bugs.kde.org/show_bug.cgi?id=416963 Bug ID: 416963 Summary: After migration to aq6 the finding of aliases takes a long time Product: kmymoney Version: 5.0.7 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: onlinebanking Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- After migrating from aq5, on an older laptop I get the following messages every time I change a view in kmymoney. 3:2020/01/30 12-38-47:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-47:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-47:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-47:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-47:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-47:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-48:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-48:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-48:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-48:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-48:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-48:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-49:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-49:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-49:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-49:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-49:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-49:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-50:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-50:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-50:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-50:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-50:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-50:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-51:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-51:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-51:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-51:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-51:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-52:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-52:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" 3:2020/01/30 12-38-52:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "A01" 3:2020/01/30 12-38-52:aqbanking(1603):banking_compat.c: 62: Invalid account id for alias "82096d96-867e-4c6c-a35e-9a5ded777668-A01" STEPS TO REPRODUCE 1. start kmymoney with enabled online banking from command line 2. switch ledger OBSERVED RESULT The mentioned message are displayed on the command line and delays switching ledger EXPECTED RESULT There should not be delay on switching ledger SOFTWARE/OS VERSIONS Linux: OpenSUSE Leap 15.1 KDE Frameworks: 5.49.5 Qt 5.9.7 ADDITIONAL INFORMATION 1. This bug
[krita] [Bug 416894] krita full screen in wrong monitor
https://bugs.kde.org/show_bug.cgi?id=416894 Ahab Greybeard changed: What|Removed |Added CC||ahab.greybe...@hotmail.co.u ||k --- Comment #3 from Ahab Greybeard --- I don't have this on Windows 10 with the Jan 30th 4.3.0-prealpha (git 0657457) standalone .zip. It goes to full screen on whatever monitor has the majority of the window on it then returns to its previous shape and size and placement. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416924] The server is not connecting
https://bugs.kde.org/show_bug.cgi?id=416924 andreas.sturmlech...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from andreas.sturmlech...@gmail.com --- The provided log indicates that kde-apps/akonadi was built exactly without USE=mysql. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416924] The server is not connecting
https://bugs.kde.org/show_bug.cgi?id=416924 --- Comment #2 from andreas.sturmlech...@gmail.com --- Not a bug. kde-apps/akonadi installation gives appropriate steps for how to configure your akonadi instance, depending on the use flags you have set. Example from my system: * You can select the storage backend in ~/.config/akonadi/akonadiserverrc. * Available drivers are: * QPSQL * has been set as your default akonadi storage backend. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416962] Unparsed HTML tags in Android notifications
https://bugs.kde.org/show_bug.cgi?id=416962 bart@protonmail.com changed: What|Removed |Added CC||bart@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 416962] New: Unparsed HTML tags in Android notifications
https://bugs.kde.org/show_bug.cgi?id=416962 Bug ID: 416962 Summary: Unparsed HTML tags in Android notifications Product: kdeconnect Version: unspecified Platform: Android OS: Android 8.x Status: REPORTED Severity: minor Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: bart@protonmail.com Target Milestone: --- Created attachment 12 --> https://bugs.kde.org/attachment.cgi?id=12=edit The notirication from the Android app SUMMARY The Android notifications originating from Ubuntu (18.04) contain HTML tags (like ). Example: "Laptop battery low. Only 25 minutes left." STEPS TO REPRODUCE 1. Install KDE Connect on Ubuntu 18.04 2. Pair with an Android phone and hit the checkbox "Send notifications" in the KDE Settings panel on the laptop. 3. Wait until the laptop battery drops to a certain point, wait for any program to send notifications containing bold/italic/underlined text, or manually send a notification on your laptop with HTML tags in it. OBSERVED RESULT The notifications on the laptop are showed with bold text as intended, but the notification on the phone contains the tags in plain text. EXPECTED RESULT The HTML tags are also parsed on the Android device and make the text bold, or, if this is not possible, at least no tags should be visible. SOFTWARE/OS VERSIONS Linux: Ubuntu 18.04 LTS KDE Connect (on Ubuntu): "kcmshell5" 5.12.8 Android: 8.0.0 KDE Connect (on Android): 1.13.7 ADDITIONAL INFORMATION This bug might be considered a duplicate from an older bug about the same issue. (https://bugs.kde.org/show_bug.cgi?id=358549) However, after updating the app, the problem was still there. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416928] Latte panel background is layered.
https://bugs.kde.org/show_bug.cgi?id=416928 Michail Vourlakos changed: What|Removed |Added Latest Commit|https://commits.kde.org/lat |https://commits.kde.org/lat |te-dock/8ab5779bcbc5c6f4604 |te-dock/b11dacc0042b0ba902b |afb11efeeca56faa77641 |cb92c4ce16562ad63aae2 --- Comment #11 from Michail Vourlakos --- Git commit b11dacc0042b0ba902bcb92c4ce16562ad63aae2 by Michail Vourlakos. Committed on 30/01/2020 at 20:04. Pushed by mvourlakos into branch 'v0.9'. compute blur area correctly on startup --improve calculations for Effects area during startup and at the same time when the dock is totally hidden so it should not paint any effects area at all. FIXED-IN:0.9.9 M +12 -17 app/view/effects.cpp M +22 -9containment/package/contents/ui/PanelBox.qml https://commits.kde.org/latte-dock/b11dacc0042b0ba902bcb92c4ce16562ad63aae2 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416928] Latte panel background is layered.
https://bugs.kde.org/show_bug.cgi?id=416928 Michail Vourlakos changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/lat ||te-dock/8ab5779bcbc5c6f4604 ||afb11efeeca56faa77641 Version Fixed In||0.9.9 --- Comment #10 from Michail Vourlakos --- Git commit 8ab5779bcbc5c6f4604afb11efeeca56faa77641 by Michail Vourlakos. Committed on 30/01/2020 at 20:02. Pushed by mvourlakos into branch 'master'. compute blur area correctly on startup --improve calculations for Effects area during startup and at the same time when the dock is totally hidden so it should not paint any effects area at all. FIXED-IN:0.9.9 M +12 -17 app/view/effects.cpp M +22 -9containment/package/contents/ui/PanelBox.qml https://commits.kde.org/latte-dock/8ab5779bcbc5c6f4604afb11efeeca56faa77641 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416616] Feature request: extract audio from cropped clips in the timeline
https://bugs.kde.org/show_bug.cgi?id=416616 Massimo Stella changed: What|Removed |Added Status|CONFIRMED |REPORTED Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 416949] kdesvn crashes when opening a repository
https://bugs.kde.org/show_bug.cgi?id=416949 Christian Ehrlicher changed: What|Removed |Added CC||ch.ehrlic...@gmx.de --- Comment #1 from Christian Ehrlicher --- I can't see anything kdesvn related here, please report it to the Kvantum developers. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416616] Feature request: extract audio from cropped clips in the timeline
https://bugs.kde.org/show_bug.cgi?id=416616 Massimo Stella changed: What|Removed |Added CC||maxs...@tin.it --- Comment #2 from Massimo Stella --- Hi CzAndrew. What you ask is just possible in Kdenlive without any workaround. When your piece of clip is on the timeline you have just to right click on it an choose Clip in Project Bin. After this your clip will open in the clip monitor with the In and Out already marked for that clip. At this point you can right click on the Clip Monitor window and choose select Extract zone. If you need the audio only choose as extention for your file an audio format (for eg: wav) You have to match the extention with the type of audio conteined in the videoclip. I hope you'll enjoy to use this feature you didn't know already. Cheers -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 416106] Save a screenshot to clipboard without the screenshot GUI
https://bugs.kde.org/show_bug.cgi?id=416106 --- Comment #5 from daniel-other+kde...@dadosch.de --- You can use spectacle -b -c to save it to the clipboard (in theory, however the -c isn't working for me) > org.kde.knotifications: Could not notify "newScreenshotSaved" by taskbar, > notification has no associated widget This should be just a warning that the notificatoin couldn't be displayed. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 416928] Latte panel background is layered.
https://bugs.kde.org/show_bug.cgi?id=416928 --- Comment #9 from Tom Albers --- The content of attachment 125550 has been deleted for the following reason: Per user request. (TA) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 412446] Animated webp with transparency don't render properly
https://bugs.kde.org/show_bug.cgi?id=412446 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- The same occurs when I open the attachment with Qt viewers qimgv and PhotoQt. -- You are receiving this mail because: You are watching all bug changes.
