[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 webcap...@gmail.com changed: What|Removed |Added CC||webcap...@gmail.com --- Comment #18 from webcap...@gmail.com --- Created attachment 123229 --> https://bugs.kde.org/attachment.cgi?id=123229=edit Checkboxes are black Same for me. Almost every site has black checkboxes with Breeze Dark Plasma Style Theme. Breeze Light looks like good -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403640] Wrong positioning of launchers and windows during startup for icon-only taskmanager
https://bugs.kde.org/show_bug.cgi?id=403640 Michail Vourlakos changed: What|Removed |Added CC||halpieh...@gmail.com --- Comment #2 from Michail Vourlakos --- *** Bug 413013 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413013] application icons change position randomly when opened
https://bugs.kde.org/show_bug.cgi?id=413013 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Michail Vourlakos --- *** This bug has been marked as a duplicate of bug 403640 *** -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 412954] Software tests fails after build
https://bugs.kde.org/show_bug.cgi?id=412954
--- Comment #3 from syst...@mdc-berlin.de ---
The last master fails before the tests.
See the build master attachment.
/builddir/build/BUILD/heaptrack-master/src/analyze/gui/parser.cpp:37:13: error:
specialization of 'template struct std::hash' in different namespace
[-fpermissive]
struct std::hash {
^
In file included from /usr/include/c++/4.8.2/bits/basic_string.h:3033:0,
from /usr/include/c++/4.8.2/string:52,
from /usr/include/c++/4.8.2/random:41,
from /usr/include/c++/4.8.2/bits/stl_algo.h:65,
from /usr/include/c++/4.8.2/algorithm:62,
from /usr/include/qt5/QtCore/qglobal.h:109,
from /usr/include/qt5/QtCore/qnamespace.h:43,
from /usr/include/qt5/QtCore/qobjectdefs.h:48,
from /usr/include/qt5/QtCore/qobject.h:46,
from /usr/include/qt5/QtCore/QObject:1,
from
/builddir/build/BUILD/heaptrack-master/src/analyze/gui/parser.h:22,
from
/builddir/build/BUILD/heaptrack-master/src/analyze/gui/parser.cpp:19:
/usr/include/c++/4.8.2/bits/functional_hash.h:58:12: error: from definition
of 'template struct std::hash' [-fpermissive]
struct hash;
^
make[2]: ***
[src/analyze/gui/CMakeFiles/heaptrack_gui_private.dir/parser.cpp.o] Error 1
make[2]: Leaving directory `/builddir/build/BUILD/heaptrack-master/my_build'
make[1]: *** [src/analyze/gui/CMakeFiles/heaptrack_gui_private.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs
--
You are receiving this mail because:
You are watching all bug changes.
[Heaptrack] [Bug 412954] Software tests fails after build
https://bugs.kde.org/show_bug.cgi?id=412954 --- Comment #2 from syst...@mdc-berlin.de --- Created attachment 123228 --> https://bugs.kde.org/attachment.cgi?id=123228=edit Build log of master -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 404787] In K3b - The ISRC Field in the Audio Track Properties Dialog Box only allows for 2 Characters - ISRC's are 12 Characters Long eg: "CAS9S1900101" so this field need to be increased
https://bugs.kde.org/show_bug.cgi?id=404787 Marek Klein changed: What|Removed |Added Status|RESOLVED|REOPENED CC||ma...@gregoriana.sk Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #3 from Marek Klein --- Hello, my ISRC codes do not have dashes and contain letters too - it is simply 12 character string - for example ushm91985865. The original poster example was CAS9S1900101 - how would you put it in the field using dashes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375666] Please add option to adjust output RGB range
https://bugs.kde.org/show_bug.cgi?id=375666 David Korth changed: What|Removed |Added CC||gerbils...@gerbilsoft.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413014] New: KScreen design degradation in Plasma 5.17
https://bugs.kde.org/show_bug.cgi?id=413014 Bug ID: 413014 Summary: KScreen design degradation in Plasma 5.17 Product: KScreen Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm Assignee: kscreen-bugs-n...@kde.org Reporter: itnat...@gmail.com Target Milestone: --- Created attachment 123227 --> https://bugs.kde.org/attachment.cgi?id=123227=edit new kscreen design Guys, the new design of kscreen is incorrect. Replacement the evident picture of a second monitor by the hardly perceptible selector is a complete failure. Please, revert it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 412039] Auto mask is several kinds of horribly broken
https://bugs.kde.org/show_bug.cgi?id=412039 --- 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.
[krita] [Bug 411664] clicking on a certain brush preset crashes software
https://bugs.kde.org/show_bug.cgi?id=411664 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #9 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412497] Problem with scale. See list too close and can't correct it normal. And brushes lag, can't see it and move with freeze.
https://bugs.kde.org/show_bug.cgi?id=412497 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411331] Crashing when trying to stabilize and when saving clip title
https://bugs.kde.org/show_bug.cgi?id=411331 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 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 412953] Compositions Docker exports duplicates of one composition when you export multiple.
https://bugs.kde.org/show_bug.cgi?id=412953 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413005] Night Color settings break after switching to "Times" operation mode
https://bugs.kde.org/show_bug.cgi?id=413005 Michael changed: What|Removed |Added CC||finod...@protonmail.com --- Comment #1 from Michael --- I can confirm, it happens to me too. KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.6-arch1-1-ARCH Xorg, xf86-video-amdgpu 19.0.1-1 driver. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #17 from Carson Black --- (In reply to Nate Graham from comment #16) > I notice that all the reports are from Arch. I wonder if there's something > odd with their packaging or GTK version. It's most likely not the GTK version, as no relevant code was changed from 3.24.11 (known good) to 3.24.12 (Arch's version). Additionally, I cannot reproduce it building 3.24.12 from source on openSUSE. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #16 from Nate Graham --- I notice that all the reports are from Arch. I wonder if there's something odd with their packaging or GTK version. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413013] New: application icons change position randomly when opened
https://bugs.kde.org/show_bug.cgi?id=413013 Bug ID: 413013 Summary: application icons change position randomly when opened Product: lattedock Version: 0.9.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: halpieh...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. click on an application in the dock OBSERVED RESULT Icons randomly change positions regardless of whether their applications are open or not. Apparently it only happens with applications pinned to the launcher. Applications without pinned icons maintain the right position as expected. EXPECTED RESULT Maintain the previously defined position. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.6-arch1-1-ARCH OS Type: 64-bit Processors: 4 × Intel® Core™ i5 CPU M 430 @ 2.27GHz Memory: 7.6 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412704] Stops working when selecting a catalogue
https://bugs.kde.org/show_bug.cgi?id=412704 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.4.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412924] [kwin_wayland] High CPU usage with Qt 5.14 and mouse cursor artifacts
https://bugs.kde.org/show_bug.cgi?id=412924 Mojahed Yavazi changed: What|Removed |Added CC|mojahed...@gmail.com| -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412348] Scrollbar floats to the left in i3, without Plasma.
https://bugs.kde.org/show_bug.cgi?id=412348 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Kurt Hindenburg --- committed in ef13a09e -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412924] [kwin_wayland] High CPU usage with Qt 5.14 and mouse cursor artifacts
https://bugs.kde.org/show_bug.cgi?id=412924 Mojahed Yavazi changed: What|Removed |Added CC||mojahed...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413012] New: System Settings Compositor Crash
https://bugs.kde.org/show_bug.cgi?id=413012 Bug ID: 413012 Summary: System Settings Compositor Crash Product: systemsettings Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mi...@shootingstars.com Target Milestone: --- Application: systemsettings5 (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: Open System Settings, click on Display and Monitor, click on Compositor --> every single time I do this, I get a message that System Settings closed unexpectedly. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f21fc228800 (LWP 3025))] Thread 6 (Thread 0x7f21c3583700 (LWP 3031)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67 #1 0x7f21f775f0a5 in __GI___libc_read (fd=30, buf=0x7f21c3582b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #2 0x7f21f0c1c2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f21f0bd70b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f21f0bd7570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f21f0bd76dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f21f80b69db in QEventDispatcherGlib::processEvents (this=0x7f21bc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7f21f8056eaa in QEventLoop::exec (this=this@entry=0x7f21c3582d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #8 0x7f21f7e723ca in QThread::exec (this=this@entry=0x55be88abf480) at thread/qthread.cpp:531 #9 0x7f21f5c15cb5 in QQmlThreadPrivate::run (this=0x55be88abf480) at qml/ftw/qqmlthread.cpp:152 #10 0x7f21f7e73b72 in QThreadPrivate::start (arg=0x55be88abf480) at thread/qthread_unix.cpp:360 #11 0x7f21f2f966db in start_thread (arg=0x7f21c3583700) at pthread_create.c:463 #12 0x7f21f777088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f21ca6e3700 (LWP 3030)): #0 0x7f21f7763bf9 in __GI___poll (fds=0x7f21c4003ce0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f21f0bd75c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f21f0bd76dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f21f80b69db in QEventDispatcherGlib::processEvents (this=0x7f21c4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f21f8056eaa in QEventLoop::exec (this=this@entry=0x7f21ca6e2d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f21f7e723ca in QThread::exec (this=this@entry=0x55be880271d0) at thread/qthread.cpp:531 #6 0x7f21f5c15cb5 in QQmlThreadPrivate::run (this=0x55be880271d0) at qml/ftw/qqmlthread.cpp:152 #7 0x7f21f7e73b72 in QThreadPrivate::start (arg=0x55be880271d0) at thread/qthread_unix.cpp:360 #8 0x7f21f2f966db in start_thread (arg=0x7f21ca6e3700) at pthread_create.c:463 #9 0x7f21f777088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f21d3583700 (LWP 3029)): #0 0x7f21f775f0b4 in __GI___libc_read (fd=12, buf=0x7f21d3582b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f21f0c1c2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f21f0bd70b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f21f0bd7570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f21f0bd76dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f21f80b69db in QEventDispatcherGlib::processEvents (this=0x7f21cc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f21f8056eaa in QEventLoop::exec (this=this@entry=0x7f21d3582d80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f21f7e723ca in QThread::exec (this=this@entry=0x55be87e1b7c0) at thread/qthread.cpp:531 #8 0x7f21f5c15cb5 in QQmlThreadPrivate::run (this=0x55be87e1b7c0) at qml/ftw/qqmlthread.cpp:152 #9 0x7f21f7e73b72 in QThreadPrivate::start (arg=0x55be87e1b7c0) at thread/qthread_unix.cpp:360 #10 0x7f21f2f966db in start_thread (arg=0x7f21d3583700) at pthread_create.c:463 #11 0x7f21f777088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f21e0915700 (LWP 3027)): #0 0x7f21f775f0b4 in __GI___libc_read (fd=7, buf=0x7f21e0914b60, nbytes=16) at
[plasmashell] [Bug 406130] Keyboard shortcut for wallpaper change
https://bugs.kde.org/show_bug.cgi?id=406130 Lukas Sabota changed: What|Removed |Added CC||lu...@lwsabota.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413001] Flickering of radiobuttons and checkboxes
https://bugs.kde.org/show_bug.cgi?id=413001 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #4 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 412078 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Patrick Silva changed: What|Removed |Added CC||bartos.p...@gmail.com --- Comment #15 from Patrick Silva --- *** Bug 413001 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413005] Night Color settings break after switching to "Times" operation mode
https://bugs.kde.org/show_bug.cgi?id=413005 Spencer changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=413010| -- You are receiving this mail because: You are watching all bug changes.
[kgamma] [Bug 413010] night color: "times" setting does not respect 12/24hr time choice
https://bugs.kde.org/show_bug.cgi?id=413010 Spencer changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=413005| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413005] Night Color settings break after switching to "Times" operation mode
https://bugs.kde.org/show_bug.cgi?id=413005 Spencer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413010 -- You are receiving this mail because: You are watching all bug changes.
[kgamma] [Bug 413010] night color: "times" setting does not respect 12/24hr time choice
https://bugs.kde.org/show_bug.cgi?id=413010 Spencer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=413005 Keywords||accessibility Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413011] New: Reactivating a display then opening taskbar configuration
https://bugs.kde.org/show_bug.cgi?id=413011 Bug ID: 413011 Summary: Reactivating a display then opening taskbar configuration Product: plasmashell Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: louissimonmcnic...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.5) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.4-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I had deactivated a display. When reactivating it, the task manager was gone from the main display (the one which wasnt deactivated) so I opened the taskbar's configuration then kde crashed but it restarted fine. - Unusual behavior I noticed: Task manager was gone after reactivating a display -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1834b87880 (LWP 752))] Thread 33 (Thread 0x7f177a7fa700 (LWP 38775)): #0 0x7f18393219ef in poll () at /usr/lib/libc.so.6 #1 0x7f1837b40180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1837b40251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f18398c6a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f183986d4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f183969f385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f183b11f849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f18396a05b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1838b6b4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f183932c2d3 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f1802ffd700 (LWP 38716)): #0 0x7f1838b71c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f18396a6660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f18396a6752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f183b48adad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f183b48b05e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f18396a05b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1838b6b4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f183932c2d3 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f1817bff700 (LWP 38715)): #0 0x7f1838b71c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f18396a6660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f18396a6752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f183b48adad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f183b48b05e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f18396a05b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1838b6b4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f183932c2d3 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f17a0ffc700 (LWP 36344)): #0 0x7f1838b71c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f18396a6660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f18396a6752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f183b48adad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f183b48b05e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f18396a05b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1838b6b4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f183932c2d3 in clone () at /usr/lib/libc.so.6 Thread 29 (Thread 0x7f17a95eb700 (LWP 18661)): #0 0x7f1838b71c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f18396a6660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f18396a6752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f183b48adad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f183b48b05e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f18396a05b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f1838b6b4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f183932c2d3 in clone () at /usr/lib/libc.so.6 Thread 28 (Thread 0x7f180e100700 (LWP 16812)): #0 0x7f183931d42c in read () at /usr/lib/libc.so.6 #1 0x7f1837af09f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1837b3ea41 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1837b40128 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1837b40251 in g_main_context_iteration () at
[kgamma] [Bug 413010] New: night color: "times" setting does not respect 12/24hr time choice
https://bugs.kde.org/show_bug.cgi?id=413010 Bug ID: 413010 Summary: night color: "times" setting does not respect 12/24hr time choice Product: kgamma Version: 5.17.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: amplespen...@protonmail.com Target Milestone: --- SUMMARY night color: "times" setting does not respect 12/24hr time choice STEPS TO REPRODUCE 1. open system settings 2. display and monitor>night color 3. select times 4. only HH:MM is supported and no HH:MM:AM/PM EXPECTED RESULT time choice is respected SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413005] Night Color settings break after switching to "Times" operation mode
https://bugs.kde.org/show_bug.cgi?id=413005 Spencer changed: What|Removed |Added CC||amplespen...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413009] New: Re-initializing canvas interactions/shortcuts after messing with other dockers.
https://bugs.kde.org/show_bug.cgi?id=413009 Bug ID: 413009 Summary: Re-initializing canvas interactions/shortcuts after messing with other dockers. Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- I've been plagued with this issue for as long as I've used Krita, and it is a massive pain. Happens dozens, if not hundreds of times per art session. I'm hoping it's something that can be looked into or fixed, if not mitigated in some way, I can't imagine it's intentional. I draw very quickly and this breaks every point of my workflow and makes me waste time undoing what happens. Summary: When I interact with a docker other than the canvas, I have to tap the canvas 'out of bounds' before doing anything other than what I was previously doing. For instance, this will be my workflow, happening in under 2 seconds or so: The set up: I press b to select a brush. I draw a line I select a new layer on the layers docker. I hold [key] to do a quick zoom/quick rotate/any other quick action I drag my pen down on the canvas to zoom out What happens: I draw a line across my canvas What I expect to happen: I zoom out/rotate/whatever else because I'm holding the shortcut for it. Sometimes I don't even realize I accidentally drew a line, and have to spend time at the end of the piece going through each layer looking for stray lines I drew, or breaks in lines I erased. Krita Version: 4.3.0-prealpha (git 6310d2d) 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.17134 Pretty Productname: Windows 10 (10.0) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412796] Can we get an icon for Gravit designer ???
https://bugs.kde.org/show_bug.cgi?id=412796 Noah Davis changed: What|Removed |Added Status|NEEDSINFO |RESOLVED CC||noaha...@gmail.com Resolution|WAITINGFORINFO |NOT A BUG --- Comment #2 from Noah Davis --- Since this isn't a Breeze icons bug and adding icons for proprietary applications is a legal gray area, I'm closing this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412856] Okular prompts for password when none is needed for display
https://bugs.kde.org/show_bug.cgi?id=412856 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #3 from Albert Astals Cid --- This is a poppler bug, please report upstream at https://gitlab.freedesktop.org/poppler/poppler/issues -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412906] Feature to save current layout as a new Global Theme package
https://bugs.kde.org/show_bug.cgi?id=412906 --- Comment #5 from Nate Graham --- Thanks! That is quite obscure and could do with some UI polish IMO. Still it's there, so that's nice. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412906] Feature to save current layout as a new Global Theme package
https://bugs.kde.org/show_bug.cgi?id=412906 --- Comment #4 from David Edmundson --- It's maybe a bit obscure. new theme -> fill in the details -> layout from current plasma setup -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413008] New: Incorrect Russian translation for the word "rate"
https://bugs.kde.org/show_bug.cgi?id=413008 Bug ID: 413008 Summary: Incorrect Russian translation for the word "rate" Product: systemsettings Version: 5.16.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_keyboard Assignee: unassigned-b...@kde.org Reporter: arti...@artifth.ru Target Milestone: --- Created attachment 123226 --> https://bugs.kde.org/attachment.cgi?id=123226=edit Part of window with incorrect translation SUMMARY The keyboard settings page has incorrect translation for the word "rate" on the repeat rate label. Its translated using word for "tariff" - "тариф". Correct translation would be "Скорость повтора" or "Частота повтора". SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413002] Properties Dialog: Make path to the symlink clickable
https://bugs.kde.org/show_bug.cgi?id=413002 Nate Graham changed: What|Removed |Added Keywords||usability Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org --- Comment #1 from Nate Graham --- Great idea! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412783] Screen configuration should have "orientation: Auto" as an option
https://bugs.kde.org/show_bug.cgi?id=412783 --- Comment #3 from m.w...@web.de --- Wayland -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 413007] Desktop file assumes `qdbus` is the name of the command
https://bugs.kde.org/show_bug.cgi?id=413007 Nate Graham changed: What|Removed |Added CC||fab...@ritter-vogt.de, ||lbeltr...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 413007] New: Desktop file assumes `qdbus` is the name of the command
https://bugs.kde.org/show_bug.cgi?id=413007 Bug ID: 413007 Summary: Desktop file assumes `qdbus` is the name of the command Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: n...@kde.org CC: k...@david-redondo.de Target Milestone: --- ...But in openSUSE, it's `qdbus-qt5`. This means that if you compile Spectacle from source in openSUSE, the desktop file will reference a program that doesn't exist and fail. Presumably the openSUSE packagers are fixing this in their packaging, but it would be nicer to them--as well as support people who compile things from source--to programmatically generate the name of this command rather than hardcode it. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 413006] New: Impossible to save a non finished play
https://bugs.kde.org/show_bug.cgi?id=413006 Bug ID: 413006 Summary: Impossible to save a non finished play Product: ksudoku Version: unspecified Platform: Mageia RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: nk0...@yahoo.fr CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 123225 --> https://bugs.kde.org/attachment.cgi?id=123225=edit Other example of a saved file impossible to re open SUMMARY Concerne Ksudoku 19.04.0 STEPS TO REPRODUCE 1. Open a new play 2. Save the non finished play 3. open the saved file OBSERVED RESULT ksudoku cannot read the saved file : "impossible to read the line 1 of the xml file" Same for 10 different filed saved EXPECTED RESULT Open the saved play and finish it SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.15.4 (available in About System) KDE Plasma Version: 5.57.0 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION example of a saved file : d___b_c__h__i_fb__c_hd_f__e_e__d_j__f_f__h_jd_e__fg_c__d__j_d___i difhbecjghjcigfdbegbejcdfihjhdcfgiebecbdijhgfifgehbjdccdhbeigfjfeigjcbhdbgjfdheci -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412552] Extended screen on 2 displays overlaps by 1px
https://bugs.kde.org/show_bug.cgi?id=412552 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #7 from Nate Graham --- Sweet! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412552] Extended screen on 2 displays overlaps by 1px
https://bugs.kde.org/show_bug.cgi?id=412552 --- Comment #6 from el...@seznam.cz --- I confirm that this issue is indeed fixed in 5.17. You may close this issue. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413005] New: Night Color settings break after switching to "Times" operation mode
https://bugs.kde.org/show_bug.cgi?id=413005
Bug ID: 413005
Summary: Night Color settings break after switching to "Times"
operation mode
Product: systemsettings
Version: 5.17.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: amd...@yandex.com
Target Milestone: ---
SUMMARY
Switching to "Times" operation mode breaks night color settings and you can't
save your new changes anymore or disable it. As a workaround you can remove the
[NightColor] section from ~/.config/kwinrc, restart kwin and you'll be able to
change settings normally again.
STEPS TO REPRODUCE
1. Access Night Color settings, for example by navigating to System Settings >
Display and Monitor > Night Color
2. Enable Night Color and change Operation Mode to Times
3. Apply your changes and close the window (important)
4. Access Night Color settings again, make any new changes and try to apply
them
OBSERVED RESULT
The Apply button is disabled and the OK button won't save new changes anymore.
EXPECTED RESULT
New changes should be able to be applied.
SOFTWARE/OS VERSIONS
KDE Neon Testing
KDE Plasma Version: 5.17.0
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.1
X11, proprietary nvidia drivers
ADDITIONAL INFORMATION
Output from running kcmshell5 nightcolor:
org.kde.kcoreaddons: Error loading plugin "kcm_nightcolor" "The shared library
was not found."
Plugin search paths are ("/usr/lib/x86_64-linux-gnu/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
gpsd not found
"location"
Fetching https://location.services.mozilla.com/v1/geolocate
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:136:
TypeError: Value is undefined and could not be converted to an object
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:71:
TypeError: Cannot read property 'actions' of null
file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:203:42: QML
LocationsAutoView: Binding loop detected for property "implicitWidth"
file:///usr/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml:191:42: QML
TimingsView: Binding loop detected for property "implicitWidth"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/private/ScrollView.qml:113:9:
QML ScrollBar: Binding loop detected for property "visible"
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 413000] In openSUSE Tumbleweed, navigating to updates page while backends are updating crashes Discover
https://bugs.kde.org/show_bug.cgi?id=413000 Nate Graham changed: What|Removed |Added Summary|In openSUSE Tumbleweed, |In openSUSE Tumbleweed, |navigating to updates page |navigating to updates page |whil|while backends are updating ||crashes Discover -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413004] New: In openSUSE Tumbleweed, Cuttlefish doesn't show up in discover
https://bugs.kde.org/show_bug.cgi?id=413004 Bug ID: 413004 Summary: In openSUSE Tumbleweed, Cuttlefish doesn't show up in discover Product: Discover Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- Plasma+Discover from git master on openSUSE Tumbleweed. Cuttlefish is visible to `appstreamcli search`: appstreamcli search cuttlefish Identifier: org.kde.plasma.cuttlefish [desktop-application] Name: Cuttlefish Summary: Icon Previewer for Artists and Developers But it doesn't show up in Discover, either in browse or search lists. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412906] Feature to save current layout as a new Global Theme package
https://bugs.kde.org/show_bug.cgi?id=412906 --- Comment #3 from Nate Graham --- (In reply to David Edmundson from comment #1) > See lookandfeelexplorer As Postix implies, this doesn't really satisfy the request here. It doesn't actually have a "save current settings as a new theme" feature (or at least, not that I can find). > Also, there's a task at T11746 which has a different proposed implementation > of doing things which I think makes a lot more sense. Lets not split the > discussion especially when this only represents one side of the comments. Assuming you're referring to https://phabricator.kde.org/T11746#202374, I can accept that, and we can keep the conversation there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session
https://bugs.kde.org/show_bug.cgi?id=412152
alg...@aaathats3as.com changed:
What|Removed |Added
CC||alg...@aaathats3as.com
--- Comment #13 from alg...@aaathats3as.com ---
I have the same problem also on Arch.
I'd like to add that it works fine with the proprietary nvidia drivers but
fails with the nouveau drivers.
I have the exact same problems as described here so appearently it is not
caused by the drivers themselves (since I am on Nvidia, others Intel here) but
we all get the exact same error messages (""/usr/bin/kwin_wayland"
("--xwayland", "--libinput",
"--exit-with-session=/usr/lib/startplasma-waylandsession") exited with code
11")
--
You are receiving this mail because:
You are watching all bug changes.
[Heaptrack] [Bug 412954] Software tests fails after build
https://bugs.kde.org/show_bug.cgi?id=412954 --- Comment #1 from Milian Wolff --- can you try a newer version than 1.1 - i.e. latest git master - and see if it fails there too? -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 412742] $pipe for mkfifo has no write permission
https://bugs.kde.org/show_bug.cgi?id=412742 Milian Wolff changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/hea ||ptrack/2d14f5de75b9dae33be0 ||e782bcec043794e3f5e7 Resolution|--- |FIXED --- Comment #5 from Milian Wolff --- Git commit 2d14f5de75b9dae33be0e782bcec043794e3f5e7 by Milian Wolff, on behalf of Sam Saffron. Committed on 15/10/2019 at 21:06. Pushed by mwolff into branch 'master'. Allow high priv user to profile low priv user process In some cases `root` may attach to a non `root` process, in that case we need to ensure th pipe can be written to by the process being profiled M +10 -0src/track/heaptrack.sh.cmake https://commits.kde.org/heaptrack/2d14f5de75b9dae33be0e782bcec043794e3f5e7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 412320] Support OBS Studio as screen recorder
https://bugs.kde.org/show_bug.cgi?id=412320 Nate Graham changed: What|Removed |Added Severity|normal |wishlist Keywords||junior-jobs --- Comment #1 from Nate Graham --- Basically just a matter of copying how existing apps were added: https://cgit.kde.org/knewstuff.git/tree/data/kmoretools-desktopfiles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412704] Stops working when selecting a catalogue
https://bugs.kde.org/show_bug.cgi?id=412704 --- Comment #3 from Anders Wennerberg --- Thanks Maik, it seems to work now! Anders On 2019-10-14 09:49, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=412704 > > --- Comment #2 from Maik Qualmann --- > I think that issue is fixed in the pre-release version of digiKam-6.4.0. > Please > test this version from here: > > https://files.kde.org/digikam/ > > Maik > --- This email has been checked for viruses by AVG. https://www.avg.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412999] Some photos downloaded in previous version of digikam no more recognized as already downloaded
https://bugs.kde.org/show_bug.cgi?id=412999 --- Comment #3 from Nicofo --- Hum, indeed, if I play with the setting "Use file metadata (makes connection slower)" in Settings > Camera > Behavior, I have no recognition problem anymore. Something has changed between 6.1 and 6.3 regarding this setting. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412865] Memory leak when spamming notifications
https://bugs.kde.org/show_bug.cgi?id=412865 --- Comment #2 from danc...@disroot.org --- On Wednesday, October 16, 2019 2:35:03 AM +07 you wrote: > https://bugs.kde.org/show_bug.cgi?id=412865 > > --- Comment #1 from Kai Uwe Broulik --- > Did you clear the notification from history (does it show up there?) or what > did you mean by "as soon as it is cleared"? Yes, I cleared the notifications. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412959] Distinguish between exFAT and FAT32
https://bugs.kde.org/show_bug.cgi?id=412959 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||kpmcore/commit/59c9ba2f8d64 ||4357e759e6584b4cddad545d4fe ||b Resolution|--- |FIXED --- Comment #3 from Andrius Štikonas --- Git commit 59c9ba2f8d644357e759e6584b4cddad545d4feb by Andrius Štikonas. Committed on 15/10/2019 at 20:37. Pushed by stikonas into branch '4.0'. Set MBR partition type of FAT32 partitions to 0x0c. M +1-1src/plugins/sfdisk/sfdiskpartitiontable.cpp https://invent.kde.org/kde/kpmcore/commit/59c9ba2f8d644357e759e6584b4cddad545d4feb -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 413003] New: KInfoCenter eventually crashes when browsing through energy information
https://bugs.kde.org/show_bug.cgi?id=413003 Bug ID: 413003 Summary: KInfoCenter eventually crashes when browsing through energy information Product: kinfocenter Version: 5.17.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: hubn...@gmail.com Reporter: ruben.carbonba...@gmail.com Target Milestone: --- Application: kinfocenter (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-31-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: When browsing through energy information, it would eventually crash every time I did it. This behaviour was repeatable. There was also a segfault notification. The crash can be reproduced every time. -- Backtrace: Application: Info Center (kinfocenter), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff21a140d40 (LWP 24591))] Thread 5 (Thread 0x7ff1ebfff700 (LWP 24596)): #0 0x7ff20fb80664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff20fb3a6e6 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff216d3d9db in QEventDispatcherGlib::processEvents (this=0x7ff1e4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7ff216cddeaa in QEventLoop::exec (this=this@entry=0x7ff1ebffed80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #4 0x7ff216af93ca in QThread::exec (this=this@entry=0x5625077766d0) at thread/qthread.cpp:531 #5 0x7ff21525bcb5 in QQmlThreadPrivate::run (this=0x5625077766d0) at qml/ftw/qqmlthread.cpp:152 #6 0x7ff216afab72 in QThreadPrivate::start (arg=0x5625077766d0) at thread/qthread_unix.cpp:360 #7 0x7ff2118816db in start_thread (arg=0x7ff1ebfff700) at pthread_create.c:463 #8 0x7ff2163f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff1f1d1a700 (LWP 24594)): #0 0x7ff2118879f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5625078214ec) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562507821498, cond=0x5625078214c0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5625078214c0, mutex=0x562507821498) at pthread_cond_wait.c:655 #3 0x7ff1f2fed2cb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7ff1f2fecff7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7ff2118816db in start_thread (arg=0x7ff1f1d1a700) at pthread_create.c:463 #6 0x7ff2163f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff1fef19700 (LWP 24593)): #0 0x7ff2163e60b4 in __GI___libc_read (fd=7, buf=0x7ff1fef18b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7ff20fb7f2d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff20fb3a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff20fb3a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff20fb3a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff216d3d9db in QEventDispatcherGlib::processEvents (this=0x7ff1f8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff216cddeaa in QEventLoop::exec (this=this@entry=0x7ff1fef18d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7ff216af93ca in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7ff21441e0e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7ff216afab72 in QThreadPrivate::start (arg=0x7ff214695d80) at thread/qthread_unix.cpp:360 #10 0x7ff2118816db in start_thread (arg=0x7ff1fef19700) at pthread_create.c:463 #11 0x7ff2163f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff206f31700 (LWP 24592)): #0 0x7ff2163eabf9 in __GI___poll (fds=0x7ff206f30ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff211eb0747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff211eb236a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff209d16f00 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7ff216afab72 in QThreadPrivate::start (arg=0x56250761c0a0) at thread/qthread_unix.cpp:360 #5 0x7ff2118816db in start_thread (arg=0x7ff206f31700) at pthread_create.c:463 #6 0x7ff2163f788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff21a140d40 (LWP 24591)): [KCrash Handler] #6 0x7ff216ce8f67 in QMetaObject::cast (this=this@entry=0x7ff2050ac8e0 , obj=0x562507e3e980) at
[systemsettings] [Bug 412913] Label for Provider::setEnabled is misleading
https://bugs.kde.org/show_bug.cgi?id=412913 David Edmundson changed: What|Removed |Added Summary|Initial loading is broken |Label for ||Provider::setEnabled is ||misleading --- Comment #5 from David Edmundson --- Ninja edit. There was a bad bug before where opening and saving the KCM would accidentally set the plasma's feedback enablement without user changes. That had a quick patch. Only the bug about this checkbox having misleading text remains. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 319001] Smart detection whether file was been already downloaded
https://bugs.kde.org/show_bug.cgi?id=319001 Maik Qualmann changed: What|Removed |Added CC||nic...@tuxfamily.org --- Comment #4 from Maik Qualmann --- *** Bug 412999 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412999] Some photos downloaded in previous version of digikam no more recognized as already downloaded
https://bugs.kde.org/show_bug.cgi?id=412999 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 319001 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412999] Some photos downloaded in previous version of digikam no more recognized as already downloaded
https://bugs.kde.org/show_bug.cgi?id=412999 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The date format has not changed between the digiKam versions. However, if you have used or did not use metadata in the camera settings, a different date may be created. We can not do anything about that. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412913] Initial loading is broken
https://bugs.kde.org/show_bug.cgi?id=412913 --- Comment #4 from Nate Graham --- I'm glad my confusion has some value at least. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 412668] Make it easy to navigate to the path of any open Dolphin windows
https://bugs.kde.org/show_bug.cgi?id=412668 --- Comment #3 from Gregor Mi --- (In reply to Nate Graham from comment #1) > Were you aware that you can drag-and-drop files and folders into the main > area of the file dialog to have it switch there? No, I weren't. That's nice! > Not exactly what you're asking for, but > maybe that's good enough? What do you think? Now, that I know it, I'll use it when I am again in the situation. According to your last remark, I think there are indeed ways which are more discoverable. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412948] Deleting a versioned file leaves original hidden in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=412948 --- Comment #2 from Maik Qualmann --- Git commit 949e19574898e05d104a5a97638fd8e73774f758 by Maik Qualmann. Committed on 15/10/2019 at 20:22. Pushed by mqualmann into branch 'master'. add repair function for hidden versioned items M +21 -11 core/libs/album/treeview/albumselectiontreeview.cpp M +1-1core/libs/album/treeview/albumselectiontreeview.h https://invent.kde.org/kde/digikam/commit/949e19574898e05d104a5a97638fd8e73774f758 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412913] Initial loading is broken
https://bugs.kde.org/show_bug.cgi?id=412913 --- Comment #3 from David Edmundson --- @volker Right now, I don't know. This whole concept of the Provider::enabled killswitch has been a bit problematic purely at a UX level. The way we currently present things in the KCM doesn't sound like things are off by default, without needing explanatory text. It's apparently confusing to devs even after explaining the situation. Hopefully that's something that can be fixed just on our side Current thread: https://phabricator.kde.org/D24635 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412659] Documents Modified on Disk: Case "Deleted": Add "Close Document" button
https://bugs.kde.org/show_bug.cgi?id=412659 --- Comment #2 from Gregor Mi --- :-) There are tooltips on the buttons explaining things at bit more. But the buttons and the tooltips were apparently not written with the "Deleted" case in mind. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412988] Black buttons on GTK3 applications
https://bugs.kde.org/show_bug.cgi?id=412988 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 412078 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Patrick Silva changed: What|Removed |Added CC||leguen.yann...@gmail.com --- Comment #14 from Patrick Silva --- *** Bug 412988 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 412990] Print shortcuts feature results in almost 200 pages printed with no warning
https://bugs.kde.org/show_bug.cgi?id=412990 --- Comment #6 from Juraj --- As an option - Print action icon if present Many times I use some feature in menu, toolbar I use icon as a guide to find it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412917] On macOS Mojave image editor opens withouth toolbars
https://bugs.kde.org/show_bug.cgi?id=412917 --- Comment #5 from caulier.gil...@gmail.com --- Done. new 6.4.0 PKG installer is rebuilt and available here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412660] For symlinks: Add "Show Target" to context menu (and/or to Properties Dialog)
https://bugs.kde.org/show_bug.cgi?id=412660 --- Comment #2 from Gregor Mi --- Separate bug created here https://bugs.kde.org/show_bug.cgi?id=413002 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413002] New: Properties Dialog: Make path to the symlink clickable
https://bugs.kde.org/show_bug.cgi?id=413002
Bug ID: 413002
Summary: Properties Dialog: Make path to the symlink clickable
Product: frameworks-kio
Version: 5.60.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Properties dialog
Assignee: fa...@kde.org
Reporter: codestr...@posteo.org
CC: kdelibs-b...@kde.org
Target Milestone: ---
Coming from https://bugs.kde.org/show_bug.cgi?id=412660
It would be nice if in the Properties Dialog, the target path of a symlink
("Points to:") would be easily accessible.
E.g.
- either by making the label clickable, see screenshot
https://bugsfiles.kde.org/attachment.cgi?id=123050
- or by adding a "Show target" button
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 413001] Flickering of radiobuttons and checkboxes
https://bugs.kde.org/show_bug.cgi?id=413001 --- Comment #3 from Petr Bartos --- Created attachment 123224 --> https://bugs.kde.org/attachment.cgi?id=123224=edit Recent version 3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413001] Flickering of radiobuttons and checkboxes
https://bugs.kde.org/show_bug.cgi?id=413001 --- Comment #2 from Petr Bartos --- Created attachment 123223 --> https://bugs.kde.org/attachment.cgi?id=123223=edit Recent version 2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413001] Flickering of radiobuttons and checkboxes
https://bugs.kde.org/show_bug.cgi?id=413001 --- Comment #1 from Petr Bartos --- Created attachment 123222 --> https://bugs.kde.org/attachment.cgi?id=123222=edit Recent version 1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413001] New: Flickering of radiobuttons and checkboxes
https://bugs.kde.org/show_bug.cgi?id=413001 Bug ID: 413001 Summary: Flickering of radiobuttons and checkboxes Product: Breeze Version: 5.17.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: bartos.p...@gmail.com Target Milestone: --- Created attachment 123221 --> https://bugs.kde.org/attachment.cgi?id=123221=edit Working in older version SUMMARY Hi, in 5.17.0 (and it was also in 5.16.90) i'm seeing flickering of radiobuttons and checkboxes. They are either filled black or have black border which are dissapearing and reappearing randomly when mouse is moved over them. STEPS TO REPRODUCE 1. Open gtk theme preview in system settings (or any gtk window showing these) OBSERVED RESULT See attachments EXPECTED RESULT See attachments ADDITIONAL INFORMATION Installed from https://copr.fedorainfracloud.org/coprs/mkyral/plasma-unstable/ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 412662] Overwrite dialog: Show if files are identical
https://bugs.kde.org/show_bug.cgi?id=412662 --- Comment #3 from Gregor Mi --- (In reply to Nate Graham from comment #2) > In fact, if the files actually are identical by checksum comparison (or > whatever), maybe we should just auto-skip without even prompting the user. > What do you think? Sounds good. I wonder what should happen for the corner case when the file contents is equal but not the file modification date. I think that skipping would also be ok for that. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 412990] Print shortcuts feature results in almost 200 pages printed with no warning
https://bugs.kde.org/show_bug.cgi?id=412990 --- Comment #5 from Nate Graham --- (In reply to Juraj from comment #4) > - Print only assigned shortcuts (exclude empty shortcuts) Definitely. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 412990] Print shortcuts feature results in almost 200 pages printed with no warning
https://bugs.kde.org/show_bug.cgi?id=412990 --- Comment #4 from Juraj --- - Print only assigned shortcuts (exclude empty shortcuts) It would shrink the list quite a lot. If one wants to print only used shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 412990] Print shortcuts feature results in almost 200 pages printed with no warning
https://bugs.kde.org/show_bug.cgi?id=412990 Juraj changed: What|Removed |Added CC||sgd.or...@gmail.com --- Comment #3 from Juraj --- - There could be an option to select which component / main category shortcuts to print. Many KDE applications consist of many other KDE applications and plugins. These often add tons of shortcuts. It would be nice to be able to select which to print and which NOT. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412999] New: Some photos downloaded in previous version of digikam no more recognized as already downloaded
https://bugs.kde.org/show_bug.cgi?id=412999 Bug ID: 412999 Summary: Some photos downloaded in previous version of digikam no more recognized as already downloaded Product: digikam Version: 6.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-History Assignee: digikam-bugs-n...@kde.org Reporter: nic...@tuxfamily.org Target Milestone: --- SUMMARY With Digikam 6.3, import pictures. Observation: some pictures already imported with previous version of digikam (e.g. 6.1 or older) are not recognized as already downloaded. Note: the opposite is also true: import pictures with Digikam 6.3. In Digikam 6.1, import pictures: observe that some pictures imported with 6.3 are not recognized as already downloaded. If I again import an already unrecognized imported picture, I see in the digikam4.db (DownloadHistory table) that the filedate is not the same for both imports. My guess: with Digikam 6.1 and older, EXIF date was used while with 6.3 filedate is used to store the date in db. As a result, loss of compatibility between 6.1 and 6.3. (I have not tested 6.2) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413000] New: In openSUSE Tumbleweed, navigating to updates page whil
https://bugs.kde.org/show_bug.cgi?id=413000 Bug ID: 413000 Summary: In openSUSE Tumbleweed, navigating to updates page whil Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- openSUSE Tumbleweed with everything KDE built from source. STEPS TO REPRODUCE 1. Open Discover 2. While the sidebar item for the updates page says, "Fetching updates...", click on it OBSERVED RESULT Discover reproducibly crashes with the following backtrace: #0 0x77e5a230 in QList::QList(QList const&) (this=this@entry=0x7fff49f0, l=...) at /usr/include/qt5/QtCore/qlist.h:825 #1 0x77e599ba in QStringList::QStringList(QStringList const&) (this=0x7fff49f0) at /usr/include/qt5/QtCore/qstringlist.h:99 #2 0x77e599ba in AddonList::addonsToInstall() const (this=) at /home/nate/kde/src/discover/libdiscover/Transaction/AddonList.cpp:34 #3 0x7fffd80de799 in PackageKitBackend::installApplication(AbstractResource*, AddonList const&) () at /usr/lib64/qt5/plugins/discover/packagekit-backend.so #4 0x77e62bc0 in ResourcesModel::fetchingUpdatesProgress() const (this=0x5c2630) at /home/nate/kde/src/discover/libdiscover/resources/ResourcesModel.cpp:412 #5 0x77e46e9b in ResourcesModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=) at /home/nate/kde/build/discover/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_ResourcesModel.cpp:469 #6 0x766a6a81 in () at /usr/lib64/libQt5Qml.so.5 #7 0x766a8824 in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () at /usr/lib64/libQt5Qml.so.5 #8 0x766c6a86 in () at /usr/lib64/libQt5Qml.so.5 #9 0x766cba4f in () at /usr/lib64/libQt5Qml.so.5 #10 0x7665962f in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib64/libQt5Qml.so.5 #11 0x767de6c7 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib64/libQt5Qml.so.5 #12 0x767e41df in QQmlBinding::evaluate(bool*) () at /usr/lib64/libQt5Qml.so.5 #13 0x767e8bf6 in () at /usr/lib64/libQt5Qml.so.5 #14 0x767e5494 in QQmlBinding::update(QFlags) () at /usr/lib64/libQt5Qml.so.5 #15 0x779f5ebc in () at /usr/lib64/libQt5Quick.so.5 #16 0x779f5f39 in QQuickTransitionManager::complete() () at /usr/lib64/libQt5Quick.so.5 #17 0x779f7428 in QQuickTransitionManager::transition(QList const&, QQuickTransition*, QObject*) () at /usr/lib64/libQt5Quick.so.5 #18 0x779f3e60 in QQuickState::apply(QQuickTransition*, QQuickState*) () at /usr/lib64/libQt5Quick.so.5 #19 0x779fe532 in () at /usr/lib64/libQt5Quick.so.5 #20 0x779ff4a7 in QQuickStateGroup::componentComplete() () at /usr/lib64/libQt5Quick.so.5 #21 0x77adc476 in QQuickItem::componentComplete() () at /usr/lib64/libQt5Quick.so.5 #22 0x70a37459 in QQuickControl::componentComplete() () at /usr/lib64/libQt5QuickTemplates2.so.5 #23 0x70a0ff9a in QQuickPane::componentComplete() () at /usr/lib64/libQt5QuickTemplates2.so.5 #24 0x70a148ea in QQuickPage::componentComplete() () at /usr/lib64/libQt5QuickTemplates2.so.5 #25 0x767f3e4c in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () at /usr/lib64/libQt5Qml.so.5 #26 0x76776701 in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () at /usr/lib64/libQt5Qml.so.5 --Type for more, q to quit, c to continue without paging-- #27 0x76776812 in QQmlComponentPrivate::completeCreate() () at /usr/lib64/libQt5Qml.so.5 #28 0x76e0 in QQmlComponent::createObject(QQmlV4Function*) () at /usr/lib64/libQt5Qml.so.5 #29 0x767797d3 in () at /usr/lib64/libQt5Qml.so.5 #30 0x76779c83 in QQmlComponent::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib64/libQt5Qml.so.5 #31 0x767b663d in () at /usr/lib64/libQt5Qml.so.5 #32 0x766ad2d6 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib64/libQt5Qml.so.5 #33 0x766c9a76 in () at /usr/lib64/libQt5Qml.so.5 #34 0x766cba4f in () at /usr/lib64/libQt5Qml.so.5 #35 0x7665a510 in () at /usr/lib64/libQt5Qml.so.5 #36 0x766c9a76 in () at /usr/lib64/libQt5Qml.so.5 #37 0x766cba4f in () at /usr/lib64/libQt5Qml.so.5 #38 0x7665a510 in () at /usr/lib64/libQt5Qml.so.5 #39 0x7673838a in QV4::Runtime::method_callQmlContextPropertyLookup(QV4::ExecutionEngine*, unsigned int,
[okular] [Bug 412978] Okular creates tabs for deleted files
https://bugs.kde.org/show_bug.cgi?id=412978 --- Comment #12 from Andi Sardina --- Postix, I notice it, but the problem is that the function to open the file is in the part (KParts::ReadWritePart), which is created and added to the tab widget before know if the file will be opened successfully or not. Maybe there is a way to do update the UI after. I am trying to write an autotest right now, and it will take me a bit because I haven't written a test in Qt before. But after I finish this, I will try to solve it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366471] Plasma desktop becomes unresponsive with a .desktop file using a .svgz icon
https://bugs.kde.org/show_bug.cgi?id=366471 David Edmundson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #8 from David Edmundson --- Can you reopen if this is still an issue? We haven't had any other reports. I could not reproduce. Note also the file attached is not a compressed .svg the contents are plain text. Yet the file format is svgz and the backtrace shows we're decompressing things. That could be an issue attaching or could have been the source of the original problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412998] System Settings -> Display and Monitor -> Compositor crashes
https://bugs.kde.org/show_bug.cgi?id=412998 --- Comment #3 from Piotr Mierzwinski --- Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb714dea800 (LWP 8951))] Thread 9 (Thread 0x7fb6eeb12700 (LWP 9052)): #0 0x7fb717898922 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #1 0x7fb71789a128 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb71789a251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb71a053a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb719ffa4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb719e2c385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb719135849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fb719e2d5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fb6f482d700 (LWP 9045)): #0 0x7fb719aae9ef in poll () at /usr/lib/libc.so.6 #1 0x7fb71789a180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb71789b123 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7fb6f608fb48 in () at /usr/lib/libgio-2.0.so.0 #4 0x7fb717876c11 in () at /usr/lib/libglib-2.0.so.0 #5 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fb6f5d28700 (LWP 9044)): #0 0x7fb719aaa42c in read () at /usr/lib/libc.so.6 #1 0x7fb71784a9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb717898a41 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb71789a128 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb71789a251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb71789a2a2 in () at /usr/lib/libglib-2.0.so.0 #6 0x7fb717876c11 in () at /usr/lib/libglib-2.0.so.0 #7 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fb7094ba700 (LWP 8997)): #0 0x7fb719aae9ef in poll () at /usr/lib/libc.so.6 #1 0x7fb71789a180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb71789a251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb71a053a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb719ffa4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb719e2c385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb719135849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fb719e2d5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fb70b574700 (LWP 8995)): #0 0x7fb719aaa42c in read () at /usr/lib/libc.so.6 #1 0x7fb71784a9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb717898a41 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb71789a128 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb71789a251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb71a053a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb719ffa4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fb719e2c385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fb719135849 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fb719e2d5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb70bfff700 (LWP 8993)): #0 0x7fb71868fc45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb71089f4fc in () at /usr/lib/dri/i965_dri.so #2 0x7fb71089f0f8 in () at /usr/lib/dri/i965_dri.so #3 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb7129fb700 (LWP 8991)): #0 0x7fb719aae9ef in poll () at /usr/lib/libc.so.6 #1 0x7fb71789a180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb71789a251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb71a053a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb719ffa4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb719e2c385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb71a28db37 in () at /usr/lib/libQt5DBus.so.5 #7 0x7fb719e2d5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb7186894cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb719ab92d3 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fb713fcf700 (LWP 8975)): #0 0x7fb719aae9ef in poll () at /usr/lib/libc.so.6
[digikam] [Bug 412948] Deleting a versioned file leaves original hidden in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=412948 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/bb0a8d2ca056 ||51d99171722de1690cda357da6d ||e Resolution|--- |FIXED Version Fixed In||6.4.0 --- Comment #1 from Maik Qualmann --- Git commit bb0a8d2ca05651d99171722de1690cda357da6de by Maik Qualmann. Committed on 15/10/2019 at 19:42. Pushed by mqualmann into branch 'master'. show original image after deleting a derived image and mark original image for the next initial scan to resolve the history FIXED-IN: 6.4.0 M +2-1NEWS M +28 -3core/libs/database/utils/ifaces/dio.cpp https://invent.kde.org/kde/digikam/commit/bb0a8d2ca05651d99171722de1690cda357da6de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 352068] kwin_x11 uses 100% CPU on intel (wetab) since 5.3
https://bugs.kde.org/show_bug.cgi?id=352068 David Edmundson changed: What|Removed |Added Resolution|--- |WORKSFORME CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED --- Comment #10 from David Edmundson --- This bug is now quite old with no particularly useful information. Please do reopen if it's still an issue with feedback relating to the comments above -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412978] Okular creates tabs for deleted files
https://bugs.kde.org/show_bug.cgi?id=412978 --- Comment #11 from Postix --- > I used your idea to solve both problems. > We only needed to add that line > [closeTab( m_tabs.size() - 1 );] > in the function Shell::openUrl. Great that you could have resolve it. As I am not quiet familiar with the Okular shell code: To me it sounds like you implement kind of workaround with this line, as a faulty tab is created and closed. Should it not be created at all in the first place? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 412914] Cannot update due to PKCON error
https://bugs.kde.org/show_bug.cgi?id=412914 --- Comment #1 from Peter Wibberley --- Discover no longer seems to be crashing when I attempt an update. However, the error with 'pkcon refresh' is still occurring. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412998] System Settings -> Display and Monitor -> Compositor crashes
https://bugs.kde.org/show_bug.cgi?id=412998 --- Comment #2 from Piotr Mierzwinski --- Crash also happens after I chose "Gamma" and "Night Color" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412998] System Settings -> Display and Monitor -> Compositor crashes
https://bugs.kde.org/show_bug.cgi?id=412998 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- After Plasma has been updated I restarted my PC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412865] Memory leak when spamming notifications
https://bugs.kde.org/show_bug.cgi?id=412865 --- Comment #1 from Kai Uwe Broulik --- Did you clear the notification from history (does it show up there?) or what did you mean by "as soon as it is cleared"? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412998] New: System Settings -> Display and Monitor -> Compositor crashes
https://bugs.kde.org/show_bug.cgi?id=412998 Bug ID: 412998 Summary: System Settings -> Display and Monitor -> Compositor crashes Product: systemsettings Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- Created attachment 123220 --> https://bugs.kde.org/attachment.cgi?id=123220=edit glewinfo SUMMARY Running System Settings -> and Monitor -> Compositor causes crash. I tried 3 times with the same result. STEPS TO REPRODUCE 1. Run System Settings 2. Select: Display and Monitor -> Compositor Crash OBSERVED RESULT Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe83219b800 (LWP 5857))] Thread 7 (Thread 0x7fe8135ef700 (LWP 5933)): #0 0x7fe836e5b42c in read () from /usr/lib/libc.so.6 #1 0x7fe834bfb9f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe834c49a41 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fe834c4b128 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fe834c4b251 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fe837404a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fe8373ab4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fe8371dd385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7fe8364e6849 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7fe8371de5b0 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fe835a3a4cf in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fe836e6a2d3 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fe81a86b700 (LWP 5904)): #0 0x7fe836e5b42c in read () from /usr/lib/libc.so.6 #1 0x7fe834bfb9f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe834c49a41 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fe834c4b128 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fe834c4b251 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fe837404a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fe8373ab4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fe8371dd385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7fe8364e6849 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7fe8371de5b0 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fe835a3a4cf in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fe836e6a2d3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe82893a700 (LWP 5902)): #0 0x7fe8374046f8 in ?? () from /usr/lib/libQt5Core.so.5 #1 0x7fe834c4aa60 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7fe834c4b0a6 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7fe834c4b251 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7fe837404a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fe8373ab4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fe8371dd385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7fe8364e6849 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7fe8371de5b0 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7fe835a3a4cf in start_thread () from /usr/lib/libpthread.so.0 #10 0x7fe836e6a2d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe8295a1700 (LWP 5900)): #0 0x7fe835a40c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fe829c4e4fc in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fe829c4e0f8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fe835a3a4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fe836e6a2d3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe82bd0a700 (LWP 5891)): #0 0x7fe836e5b42c in read () from /usr/lib/libc.so.6 #1 0x7fe834bfb9f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fe834c49a41 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7fe834c4b128 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7fe834c4b251 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7fe837404a1c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7fe8373ab4ec in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fe8371dd385 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7fe83763eb37 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7fe8371de5b0 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7fe835a3a4cf in start_thread () from /usr/lib/libpthread.so.0 #11 0x7fe836e6a2d3 in clone () from
[systemsettings] [Bug 412997] New: System Settings' crash
https://bugs.kde.org/show_bug.cgi?id=412997 Bug ID: 412997 Summary: System Settings' crash Product: systemsettings Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: arkadistatse...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.6-zen1-1-zen x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: When I tried to set "Breeze Dark" in Look and Feel >> Working Enviroment, the application crashed The crash does not seem to be reproducible. -- Backtrace: Application: Параметры системы (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1d02ee0800 (LWP 2048))] Thread 9 (Thread 0x7f1ce2380700 (LWP 4675)): #0 0x7f1d059404e4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f1d05990098 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1d05991123 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0 #3 0x7f1ce2cc9b48 in () at /usr/lib/libgio-2.0.so.0 #4 0x7f1d0596cc11 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1d0677f4cf in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1d07baf2d3 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7f1ce2ba0700 (LWP 4674)): #0 0x7f1d07ba49ef in poll () at /usr/lib/libc.so.6 #1 0x7f1d05990180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1d05990251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1d059902a2 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1d0596cc11 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1d0677f4cf in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f1d07baf2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f1ce3fff700 (LWP 2058)): #0 0x7f1d0598ddbd in () at /usr/lib/libglib-2.0.so.0 #1 0x7f1d0598e6dc in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1d0598e83f in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f1d05990128 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f1d05990251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f1d08149a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f1d080f04ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1d07f22385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f1d0722b849 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f1d07f235b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f1d0677f4cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f1d07baf2d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f1ceefcc700 (LWP 2056)): #0 0x7f1d05940470 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f1d05990079 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f1d05990251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f1d08149a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f1d080f04ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f1d07f22385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f1d0722b849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f1d07f235b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f1d0677f4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f1d07baf2d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f1cf90b2700 (LWP 2054)): #0 0x7f1d08147be1 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #1 0x7f1d081481b6 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #2 0x7f1d0814975f in () at /usr/lib/libQt5Core.so.5 #3 0x7f1d0598fa60 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #4 0x7f1d059900a6 in () at /usr/lib/libglib-2.0.so.0 #5 0x7f1d05990251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #6 0x7f1d08149a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f1d080f04ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #8 0x7f1d07f22385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #9 0x7f1d0722b849 in () at /usr/lib/libQt5Qml.so.5 #10 0x7f1d07f235b0 in () at /usr/lib/libQt5Core.so.5 #11 0x7f1d0677f4cf in start_thread () at /usr/lib/libpthread.so.0 #12 0x7f1d07baf2d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f1cfa00a700 (LWP 2052)): #0 0x7f1d06785c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f1cfa6bd4fc in () at /usr/lib/dri/i965_dri.so #2 0x7f1cfa6bd0f8 in () at /usr/lib/dri/i965_dri.so #3 0x7f1d0677f4cf in
[frameworks-kxmlgui] [Bug 412990] Print shortcuts feature results in almost 200 pages printed with no warning
https://bugs.kde.org/show_bug.cgi?id=412990 --- Comment #2 from Nate Graham --- The fact that it doesn't tell you how many pages will be printed or show an inline preview is a generic flaw with the Qt print dialog. These issues are tracked with https://bugreports.qt.io/browse/QTBUG-79243 and https://bugreports.qt.io/browse/QTBUG-57982. Beyond that, the information density of the pages to be printed is extremely low: - Margins are huge - Font size is huge - Entire Description column could probably be removed (half or more of the descriptions are empty anyway) - "Main:" and "Alternate:" text could probably be removed - Could move to a multi-column layout with the above changes made Let's use this bug to track improving the information density. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412996] Notifications are muted because "the screen is mirrored", whilst it isn't actually mirrored
https://bugs.kde.org/show_bug.cgi?id=412996 --- Comment #2 from Jeffrey Bouter --- Created attachment 123219 --> https://bugs.kde.org/attachment.cgi?id=123219=edit external monitor settings -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412996] Notifications are muted because "the screen is mirrored", whilst it isn't actually mirrored
https://bugs.kde.org/show_bug.cgi?id=412996 --- Comment #1 from Jeffrey Bouter --- Created attachment 123218 --> https://bugs.kde.org/attachment.cgi?id=123218=edit laptop settings -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 412996] New: Notifications are muted because "the screen is mirrored", whilst it isn't actually mirrored
https://bugs.kde.org/show_bug.cgi?id=412996 Bug ID: 412996 Summary: Notifications are muted because "the screen is mirrored", whilst it isn't actually mirrored Product: frameworks-knotifications Version: 5.63.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: k...@kn0x.org CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 123217 --> https://bugs.kde.org/attachment.cgi?id=123217=edit notifications SUMMARY Since the upgrade to Plasma 5.17 today, my notifications are being muted because my screen is detected (by the notification application) to be mirrored, whilst really - my laptop's screen is disabled and my external monitor is enabled. Nothing is being mirrored. STEPS TO REPRODUCE 1. Attach external monitor 2. Disable laptop's screen 3. Use only external monitor OBSERVED RESULT Notifications are being muted because it is detected my screen is mirrored EXPECTED RESULT Notifications not to be affected, because there is no mirroring. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Please see the attached screenshots PS: It is odd that my screens aren't both shown in the settings page, and a dot is shown in the bottom to "scroll" to the settings of the other screen. Is this by design now? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 412990] Print shortcuts feature results in almost 200 pages printed with no warning
https://bugs.kde.org/show_bug.cgi?id=412990 Nate Graham changed: What|Removed |Added CC||n...@kde.org Ever confirmed|0 |1 Version|unspecified |5.63.0 Priority|NOR |HI Severity|normal |grave Assignee|kdevelop-bugs-n...@kde.org |kdelibs-b...@kde.org Product|kdevelop|frameworks-kxmlgui Status|REPORTED|CONFIRMED Keywords||usability Component|UI: general |general --- Comment #1 from Nate Graham --- This dialog comes from kxmlgui; moving there. -- You are receiving this mail because: You are watching all bug changes.
