[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #204 from Maik Qualmann --- OK, JPEG is an unknown format. Now the log would be good from the beginning. With digiKam-6.4.0, the image loaders will now also be plugins. These plugins are probably not found in your installation. The search is done in the Qt system plugin path. But there is the possibility to set an env variable to the plugin path. export DK_PLUGIN_PATH=path_to_plugin_dir Maik -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413418] New: KDE Partition Manager crashes when opening partition information on USB drive
https://bugs.kde.org/show_bug.cgi?id=413418 Bug ID: 413418 Summary: KDE Partition Manager crashes when opening partition information on USB drive Product: partitionmanager Version: 4.0.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: dsincu...@gmail.com Target Milestone: --- Application: partitionmanager (4.0.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.0.0-32-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: trying to view the partition information of USB drive. I tried using KDE PM to view the USB partition twice and each time the USB was seleced KDE PM would crash. At the moment I had a download running in the background and an open instance of Chromium browser. I was able to install gnome-disk-utility and check the partion using that, the USB was just a single 16GB NTFS partion blank. The crash can be reproduced every time. -- Backtrace: Application: KDE Partition Manager (partitionmanager), signal: Floating point exception Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe71b59bf80 (LWP 11211))] Thread 6 (Thread 0x7fe6f0a2e700 (LWP 11224)): #0 0x7fe7171320b4 in __GI___libc_read (fd=25, buf=0x7fe6f0a2dc90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe7116932d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe71164e0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe71164e570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe71164e962 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe6f1b9a0e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fe711676195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fe71317d6db in start_thread (arg=0x7fe6f0a2e700) at pthread_create.c:463 #8 0x7fe71714388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fe6f122f700 (LWP 11223)): #0 0x7fe7171320b4 in __GI___libc_read (fd=23, buf=0x7fe6f122eca0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe7116932d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe71164e0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe71164e570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe71164e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe71164e721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fe711676195 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fe71317d6db in start_thread (arg=0x7fe6f122f700) at pthread_create.c:463 #8 0x7fe71714388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fe6f4314700 (LWP 11215)): #0 0x7fe717136bf9 in __GI___poll (fds=0x7fe6ec004a50, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe71164e5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe71164e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe717a899db in QEventDispatcherGlib::processEvents (this=0x7fe6ec000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe717a29eaa in QEventLoop::exec (this=this@entry=0x7fe6f4313d50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fe71b16ba54 in DBusThread::run (this=0x55719a670510) at ./src/util/externalcommand.cpp:483 #6 0x7fe717846b72 in QThreadPrivate::start (arg=0x55719a670510) at thread/qthread_unix.cpp:360 #7 0x7fe71317d6db in start_thread (arg=0x7fe6f4314700) at pthread_create.c:463 #8 0x7fe71714388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fe7006db700 (LWP 11214)): #0 0x7fe717136bf9 in __GI___poll (fds=0x7fe6f801ace0, nfds=1, timeout=863532964) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe71164e5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe71164e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe717a899db in QEventDispatcherGlib::processEvents (this=0x7fe6f8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fe717a29eaa in QEventLoop::exec (this=this@entry=0x7fe7006dad30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7fe7178453ca in QThread::exec (this=) at thread/qthread.cpp:531 #6 0x7fe7166540e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe717846b72 in QThreadPrivate::start
[systemsettings] [Bug 413417] New: System Settings Crashes after Leaving "Display Configuration"
https://bugs.kde.org/show_bug.cgi?id=413417 Bug ID: 413417 Summary: System Settings Crashes after Leaving "Display Configuration" Product: systemsettings Version: 5.17.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: fr.fr...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.1) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-19-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I adjusted the "Display Configuration" to have my two monitors setup correctly. I could "Apply" the new configuration that took effect as ntended. I then exited the "Display and Monitor" settings. Then clicking on any section in the general pane made the "System settings" crash (e.g. "Online Accounts" but any section I'v tried did lead to the the same crash. - Unusual behavior I noticed: Every time I login to the Plasma session, the left monitor (which is in portrait mode if that matters) is configured with an exceedingly large geometry. In the "Displayconfiguration" I simply drag the rectangle corresponding to the right monitor. so that it is no longer overlapping with the left one. 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 0x7fcccb920800 (LWP 28858))] Thread 6 (Thread 0x7fccb1609700 (LWP 29160)): #0 0x7fcccf991104 in __GI___clock_gettime (clock_id=1, tp=0x7fccb1608af0) at ../sysdeps/unix/sysv/linux/clock_gettime.c:33 #1 0x7fcccff1cf85 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fcccff1b82d in QTimerInfoList::updateCurrentTime() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fcccff1be09 in QTimerInfoList::timerWait(timespec&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcccff1d416 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcccdaa5fbf in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fcccdaa696b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fcccdaa6b73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fcccff1d6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fcccfec463b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fcccfcfda75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fccceff0319 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fcccfcfecc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fccce342669 in start_thread (arg=) at pthread_create.c:479 #14 0x7fcccf983323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fccb88bb700 (LWP 29019)): #0 0x7fcccdaa358d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fcccdaa4bac in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcccdaa638f in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcccdaa69e2 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcccdaa6b73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fcccff1d6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcccfec463b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fcccfcfda75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fccceff0319 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fcccfcfecc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fccce342669 in start_thread (arg=) at pthread_create.c:479 #11 0x7fcccf983323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fccbadaf700 (LWP 29017)): #0 0x7fcccdaf2c3d in g_mutex_lock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fcccdaa647c in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fcccdaa69e2 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fcccdaa6b73 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fcccff1d6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fcccfec463b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fcccfcfda75 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fccceff0319 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fcccfcfecc2 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9
[kdenlive] [Bug 413416] New: Build failure with gcc 9
https://bugs.kde.org/show_bug.cgi?id=413416
Bug ID: 413416
Summary: Build failure with gcc 9
Product: kdenlive
Version: git-master
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Installation
Assignee: vpi...@kde.org
Reporter: lbeltr...@kde.org
Target Milestone: ---
SUMMARY
When trying to build kdenlive git master on openSUSE Tumbleweed, with GCC 9,
compilation fails with this error:
[ 120s] cd
"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build/thumbnailer"
&& /usr/bin/c++ -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB
-DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG
-DQT_NO_URL_CAST_FROM_STRING -DQT_WIDGETS_LIB -DTRANSLATION_DOMAIN=\"kdenlive\"
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -Dmltpreview_EXPORTS
-I"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build/thumbnailer"
-I"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/thumbnailer"
-I"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build/thumbnailer/mltpreview_autogen/include"
-I/usr/include/mlt -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtCore
-isystem /usr/lib/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui
-isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5 -isystem
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem
/usr/include/KF5/KConfigCore -isystem /usr/include/qt5/QtNetwork -isystem
/usr/include/qt5/QtConcurrent -isystem /usr/include/qt5/QtDBus -isystem
/usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KJobWidgets -isystem
/usr/include/qt5/QtWidgets -isystem /usr/include/KF5/KCompletion -isystem
/usr/include/KF5/KWidgetsAddons -fomit-frame-pointer -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
-flto=auto -g -DNDEBUG -fno-operator-names -fno-exceptions -Wall -Wextra
-Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith
-Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Wvla
-Wdate-time -Wsuggest-override -Wlogical-op -fPIC -Wno-suggest-override -fPIC
-fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o
CMakeFiles/mltpreview.dir/mltpreview.cpp.o -c
"/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/thumbnailer/mltpreview.cpp"
[ 120s]
/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/src/lib/external/media_ctrl/mediactrl.c:
In function 'find_first_device':
[ 120s]
/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/src/lib/external/media_ctrl/mediactrl.c:355:5:
error: 'for' loop initial declarations are only allowed in C99 or C11 mode
[ 120s] 355 | for (int i = 0; i < 32; i++) {
[ 120s] | ^~~
[ 120s]
/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/src/lib/external/media_ctrl/mediactrl.c:355:5:
note: use option '-std=c99', '-std=gnu99', '-std=c11' or '-std=gnu11' to
compile your code
[ 120s] make[2]: ***
[src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/build.make:76:
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/mediactrl.c.o] Error 1
[ 120s] make[2]: Leaving directory
'/home/abuild/rpmbuild/BUILD/kdenlive-19.11.70git.20191024T115227~628d47842/build'
[ 120s] make[1]: *** [CMakeFiles/Makefile2:752:
src/lib/external/media_ctrl/CMakeFiles/media_ctrl.dir/all] Error 2
I can't track which recent commit might have broken it, though.
STEPS TO REPRODUCE
1. Build the latest kdenlive git master
SOFTWARE/OS VERSIONS
gcc --version
gcc (SUSE Linux) 9.2.1 20190903 [gcc-9-branch revision 275330]
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
All the KF5 stack is built from its latest git master state.
--
You are receiving this mail because:
You are watching all bug changes.
[kcharselect] [Bug 411658] Chess Symbols not displaying correctly for any font
https://bugs.kde.org/show_bug.cgi?id=411658 Christoph Feck changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #6 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412794] Can't select Text to edit it
https://bugs.kde.org/show_bug.cgi?id=412794 --- Comment #3 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 412593] Selection area (the marching ants) becomes invisible after using krita for some time
https://bugs.kde.org/show_bug.cgi?id=412593 --- Comment #5 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 412792] basically i can zoom out but cannot zoom in, not with my normal keys or my tablet
https://bugs.kde.org/show_bug.cgi?id=412792 --- Comment #3 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 412736] Krita crashes when I customize my palette
https://bugs.kde.org/show_bug.cgi?id=412736 --- 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.
[krita] [Bug 411001] Brushes will not appear
https://bugs.kde.org/show_bug.cgi?id=411001 --- Comment #15 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.
[dolphin] [Bug 407030] Mass renaming fails to properly handle items which will themselves be renamed
https://bugs.kde.org/show_bug.cgi?id=407030 Alex changed: What|Removed |Added CC||amd...@yandex.com --- Comment #1 from Alex --- This happens because of the order in which files are renamed. So 0, 1 -> 1, 2 doesn't work as expected, but 1, 2 -> 0, 1 does. I can't think of any way to fix this within Dolphin properly, KIO deals with the batch renaming. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 412716] Bluetooth headphones spontaneously disconnect
https://bugs.kde.org/show_bug.cgi?id=412716 --- Comment #1 from Brian DuSell --- Any thoughts? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413415] New: Plasma crashed when disconnecting from WiFi
https://bugs.kde.org/show_bug.cgi?id=413415 Bug ID: 413415 Summary: Plasma crashed when disconnecting from WiFi Product: plasmashell Version: 5.15.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: benji6...@gmail.com Target Milestone: 1.0 SUMMARY Plasma segfaulted when disconnecting from WiFi. This was the first time it's ever done this to me, and I can't think of anything that was unique about this situation. The WiFi *did* succesfully disconnect, though. STEPS TO REPRODUCE 1. Connect to WiFi. 2. Disconnect. OBSERVED RESULT My background and panels disappeared and came back a couple seconds later along with a notice that plasma had crashed. EXPECTED RESULT Plasma not crashing. SOFTWARE/OS VERSIONS Fedora 30 Linux 5.3.5 KDE Plasma 5.15.5 KDE Frameworks 5.59.0 Qt 5.12.5 DEVELOPER INFORMATION Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ff8b21d00 (LWP 1450))] Thread 12 (Thread 0x7f4fd3fff700 (LWP 2411)): [KCrash Handler] #6 0x7f4fd9b5d948 in Plotter::render() () at /usr/lib64/qt5/qml/org/kde/kquickcontrolsaddons/libkquickcontrolsaddonsplugin.so #7 0x7f4ffc96cf40 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #8 0x7f4ffe59b584 in QQuickWindowPrivate::renderSceneGraph(QSize const&) () at /lib64/libQt5Quick.so.5 #9 0x7f4ffe54160f in QSGRenderThread::syncAndRender() () at /lib64/libQt5Quick.so.5 #10 0x7f4ffe5453b8 in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #11 0x7f4ffc79b4e6 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #12 0x7f4ffbc3a4c0 in start_thread () at /lib64/libpthread.so.0 #13 0x7f4ffc41a553 in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f4f9f7fe700 (LWP 1955)): #0 0x7f4ffbc403c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ffc7a0ff3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f4ffc7a1081 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f4ffe5451a9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #4 0x7f4ffe54544d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #5 0x7f4ffc79b4e6 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7f4ffbc3a4c0 in start_thread () at /lib64/libpthread.so.0 #7 0x7f4ffc41a553 in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f4f9700 (LWP 1954)): #0 0x7f4fd94bf1c3 in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #1 0x7f4fd94bfa4a in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7f4fd95be553 in pa_mainloop_dispatch () at /lib64/libpulse.so.0 #3 0x7f4fd95be882 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7f4fd95be920 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7f4fd95ccc2d in () at /lib64/libpulse.so.0 #6 0x7f4fd94cfd1c in () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #7 0x7f4ffbc3a4c0 in start_thread () at /lib64/libpthread.so.0 #8 0x7f4ffc41a553 in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f4fc0ef8700 (LWP 1916)): #0 0x7f4ffbc403c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ffc7a0ff3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f4ffc7a1081 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f4ffe5451a9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #4 0x7f4ffe54544d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #5 0x7f4ffc79b4e6 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7f4ffbc3a4c0 in start_thread () at /lib64/libpthread.so.0 #7 0x7f4ffc41a553 in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f4fc2236700 (LWP 1911)): #0 0x7f4ffbc403c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ffc7a0ff3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7f4ffc7a1081 in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #3 0x7f4ffe5451a9 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #4 0x7f4ffe54544d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #5 0x7f4ffc79b4e6 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x7f4ffbc3a4c0 in start_thread () at /lib64/libpthread.so.0 #7 0x7f4ffc41a553 in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f4fc2bc3700 (LWP 1910)): #0 0x7f4ffbc403c5 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ffc7a0ff3
[systemsettings] [Bug 413414] New: System Settings crashes from time to time while doing multiple things.
https://bugs.kde.org/show_bug.cgi?id=413414 Bug ID: 413414 Summary: System Settings crashes from time to time while doing multiple things. Product: systemsettings Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: freefreen...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.1) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-arch1-1-ARCH x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: I was just flipping thru the settings after doing a clean install of KDE Plasma on Arch Linux. The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54c84ab800 (LWP 9136))] Thread 8 (Thread 0x7f54a3fff700 (LWP 9243)): #0 0x7f54cd4eda5e in () at /usr/lib/libQt5Core.so.5 #1 0x7f54cd715122 in () at /usr/lib/libQt5Core.so.5 #2 0x7f54caf59912 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f54caf5b118 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f54aa96e700 (LWP 9144)): #0 0x7f54cd16f9ef in poll () at /usr/lib/libc.so.6 #1 0x7f54caf5b170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f54bcd0d700 (LWP 9143)): #0 0x7f54cd16b42c in read () at /usr/lib/libc.so.6 #1 0x7f54caf0b9f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf59a31 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f54caf5b118 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #9 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f54beb6a700 (LWP 9142)): #0 0x7f54cd16f9ef in poll () at /usr/lib/libc.so.6 #1 0x7f54caf5b170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf5b241 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f54cd714a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f54cd6bb4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f54cd4ed385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f54cc7f6849 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f54cd4ee5b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f54bf36b700 (LWP 9140)): #0 0x7f54cbd50c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f54bf84c50c in () at /usr/lib/dri/i965_dri.so #2 0x7f54bf84c108 in () at /usr/lib/dri/i965_dri.so #3 0x7f54cbd4a4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f54cd17a2d3 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f54c60fe700 (LWP 9139)): #0 0x7f54cd16f9ef in poll () at /usr/lib/libc.so.6 #1 0x7f54caf5b170 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f54caf5b241 in g_main_context_iteration () at
[konsole] [Bug 408048] Selection by words is sticky in Midnight Commander
https://bugs.kde.org/show_bug.cgi?id=408048 Dan Stahlke changed: What|Removed |Added CC||d...@stahlke.org --- Comment #3 from Dan Stahlke --- Also happens in tmux. Konsole 18.12.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409296] powermanagement data engine returns incorrect sleep states in login time
https://bugs.kde.org/show_bug.cgi?id=409296 --- Comment #4 from Musikolo --- The issue still persists in KDE Plasma 5.17.1. Is there any tentative version in which this will be fixed? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413354] Memory leak
https://bugs.kde.org/show_bug.cgi?id=413354 Daniel Biagi changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #5 from Daniel Biagi --- Nevermind, at least for me it was fixed after today's update -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 339971] Detach Tabs / Combine multiple windows in tabs
https://bugs.kde.org/show_bug.cgi?id=339971 Jonas changed: What|Removed |Added CC||jonas...@gmail.com --- Comment #3 from Jonas --- Yes we need this! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413407] The search field should have keyboard focus when Discover is launched
https://bugs.kde.org/show_bug.cgi?id=413407 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.18.0 Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dis ||cover/5d1b3718efb8eb88808c7 ||9165082521eff33a75d --- Comment #4 from Nate Graham --- Git commit 5d1b3718efb8eb88808c79165082521eff33a75d by Nate Graham. Committed on 25/10/2019 at 00:30. Pushed by ngraham into branch 'master'. Fix search field focus, both initial and on-demand Summary: Right now the search field doesn't get focus initially, or when the user types on a page. This is because the conditional loader that conditionally loads the GlobalDrawer's toolbar containing the search field isn't able to pass on focus or signals to its content properly. I tried various methods of fixing this by adding `focus: true` to all the focus stopes in the chain, but was unsuccessful. So this patch implements the conditional loading of the top content differently: instead the top content is always loaded, but conditionally discarded when in non-widescreen mode. This fixes the aforementioned issues. However it may not be the correct way to fix the problem; if not, assistance would be appreciated. FIXED-IN: 5.18.0 Test Plan: - Search field has focus when Discover is launched - Search field gains focus and accept text when typing anywhere - When the window is made mobiley, the sidebar's toolbar disappears - When a mobiley window is made desktoppy, the sidebar;s toolbar re-appears Reviewers: #discover_software_store, apol, davidedmundson Reviewed By: #discover_software_store, apol Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D24935 M +41 -40 discover/qml/DiscoverDrawer.qml https://commits.kde.org/discover/5d1b3718efb8eb88808c79165082521eff33a75d -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 413413] New: Global menu applet not clickable if clicked too early
https://bugs.kde.org/show_bug.cgi?id=413413 Bug ID: 413413 Summary: Global menu applet not clickable if clicked too early Product: kded-appmenu Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: export Assignee: plasma-b...@kde.org Reporter: leftcr...@tutanota.com Target Milestone: --- I've observed this behavior with a few QT applications, notably RStudio. 1. Launch Rstudio. 2. Start clicking on the menu as soon as it is drawn. 3. None of the menus won't open. 4. Wait a bit, then try again. The menus still won't open. 5. Try to switch to another window, then switch back to Rstudio 6. Now observe that the menus function normally. Alternately, try the menu widget in the titlebar. This one will work consistently. I've observed this with several applications over a fairly long period of time (can't recall all of them) and it's always the same pattern. The menus in the plasmoid won't open until you switch from and then back to the application. At the same time the locally integrated menus work. I think it was LibreOffice "File" Menu that wouldn't open until you alt-tabbed from and back to the Libre office. There was some other bug with it to it, but this was part of the issue. (It's now been fixed upstream). I think a few other similar cases were discussed on this bugtracker. It seems like this is a general problem specific to the plasma appmenu applet for which there should be a general fix, even if the problem could also be fixed inside the various misbehaving applications individually. Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-32-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413125] Color to alpha makes the image loses its original color
https://bugs.kde.org/show_bug.cgi?id=413125 --- Comment #6 from vanyossi --- This a link to the original xcf: https://drive.google.com/open?id=1YjfmfWuiI5AMiR7QuYGsZjKx_Wxr-q4u Im not familiar with the mode you mention in the gimp, but the gimp docs suggests it is a switch to activate legacy blending modes for the dropdown list. If that is the case that would explain why chaning the "mode" does nothing to the ouput of color to Alpha in gimp when I tried out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413145] No Context Help button in Aurorae themes
https://bugs.kde.org/show_bug.cgi?id=413145 --- Comment #4 from Vlad Zahorodnii --- Most likely that decoration theme doesn't have help.svg file. Can you provide a link to this sweet decoration theme? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413407] The search field should have keyboard focus when Discover is launched
https://bugs.kde.org/show_bug.cgi?id=413407 --- Comment #3 from Nate Graham --- Oops sorry, I didn't find your bug earlier. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 408106] Search field should be focused on opening
https://bugs.kde.org/show_bug.cgi?id=408106 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 413407 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413407] The search field should have keyboard focus when Discover is launched
https://bugs.kde.org/show_bug.cgi?id=413407 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- *** Bug 408106 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 412455] Segfault of LabPlot2 when opening settings dropdown
https://bugs.kde.org/show_bug.cgi?id=412455 --- Comment #6 from waterlub...@rocketmail.com --- (In reply to Alexander Semke from comment #4) > (In reply to waterlubber from comment #3) > > I tried with some other KDE/QT applications, like KDenlive (with the same > > menu option) and KStars, and was not able to reproduce the issue there. It > > appears to be limited to LabPlot2. > I manage to reproduce this only once on my computer. Hard to > understand/debug unfortunately... > > Is LabPlot linked to the same KF5 libraries as kdenlive? > > Any chance to compile the new version released today > (https://labplot.kde.org/2019/10/24/labplot-2-7-released/) and try again? I updated to the latest version from the Arch repos -- version 2.7 -- and experienced the same issue. I also tried compiling the latest version and running from there -- same problem. Would compiling with debug flags help? How would I go about that? -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 412455] Segfault of LabPlot2 when opening settings dropdown
https://bugs.kde.org/show_bug.cgi?id=412455 --- Comment #5 from waterlub...@rocketmail.com --- Created attachment 123469 --> https://bugs.kde.org/attachment.cgi?id=123469=edit Screenshot of LabPlot version. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413274] System Setting Crash (Compositor)
https://bugs.kde.org/show_bug.cgi?id=413274 --- Comment #2 from mb1 --- Created attachment 123468 --> https://bugs.kde.org/attachment.cgi?id=123468=edit New crash information added by DrKonqi systemsettings5 (5.17.1) using Qt 5.13.1 - What I was doing when the application crashed: Open Settings>Compositor - Custom settings of the application: I am using OpenGL compositing with Nvidia proprietary drivers on Arch Linux. -- Backtrace (Reduced): #6 0x7f7cd05887f0 in QQuickWindowPrivate::dirtyItem(QQuickItem*) () from /usr/lib/libQt5Quick.so.5 #7 0x7f7cd05d89e3 in QQuickText::setLinkColor(QColor const&) () from /usr/lib/libQt5Quick.so.5 [...] #9 0x7f7cd05e1e5b in QQuickText::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQt5Quick.so.5 #10 0x7f7cca30c687 in QQuickLabel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQt5QuickTemplates2.so.5 #11 0x7f7cd01a8f37 in QV4::QQmlValueTypeWrapper::write(QObject*, int) const () from /usr/lib/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413274] System Setting Crash (Compositor)
https://bugs.kde.org/show_bug.cgi?id=413274 mb1 changed: What|Removed |Added CC||marcor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413409] No VHDL highlight for uppercase VHDL keywords
https://bugs.kde.org/show_bug.cgi?id=413409 Dominik Haumann changed: What|Removed |Added Component|syntax |syntax Version|19.08.2 |5.63.0 Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 399923] Segmentation fault during face detection
https://bugs.kde.org/show_bug.cgi?id=399923 --- Comment #203 from timo...@zoho.com --- I doesn't look very helpful to me, but here's the full log of the scan (completed in 7 seconds): http://sprunge.us/fVfY1j -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413412] New: First Wayland session is buggy
https://bugs.kde.org/show_bug.cgi?id=413412 Bug ID: 413412 Summary: First Wayland session is buggy Product: plasmashell Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: finn@pm.me CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.1) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 5.3.7-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Right clicked on the chromium title bar. - Unusual behavior I noticed: Right click boxes stayed after I left clicked again. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3b33dcbc80 (LWP 872))] Thread 39 (Thread 0x7f3a88ff9700 (LWP 1474)): [KCrash Handler] #6 0x7f3b384d5e94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #7 0x7f3b33cb14d0 in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #8 0x7f3b310bbb31 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f3b38fb3a72 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f3b3a6940ee in () at /usr/lib/libQt5Quick.so.5 #11 0x7f3b3a697fc8 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f3b38a0c5b0 in () at /usr/lib/libQt5Core.so.5 #13 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 38 (Thread 0x7f3a897fa700 (LWP 1473)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b2b2c1e1c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f3b2b2c1a18 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 37 (Thread 0x7f3a89ffb700 (LWP 1472)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b2b2c1e1c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f3b2b2c1a18 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 36 (Thread 0x7f3a8a7fc700 (LWP 1447)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b38a12660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3b38a12752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3b3a697dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f3b3a69805e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f3b38a0c5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 35 (Thread 0x7f3a8bfff700 (LWP 1446)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b2b2c1e1c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f3b2b2c1a18 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 34 (Thread 0x7f3aa6ffd700 (LWP 1445)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b2b2c1e1c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f3b2b2c1a18 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 33 (Thread 0x7f3a8affd700 (LWP 1408)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b38a12660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3b38a12752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3b3a697dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f3b3a69805e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f3b38a0c5b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f3b37efd4cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3b386962d3 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f3aa4fba700 (LWP 1407)): #0 0x7f3b37f03c45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3b2b2c1e1c in () at /usr/lib/dri/radeonsi_dri.so #2 0x7f3b2b2c1a18 in () at /usr/lib/dri/radeonsi_dri.so #3 0x7f3b37efd4cf in
[okular] [Bug 413304] Chinese characters instead of Polish diacritical marks
https://bugs.kde.org/show_bug.cgi?id=413304 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #9 from Albert Astals Cid --- Do you get any warning if you start okular from the command line (i.e. konsole)? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413117] kio-5.63 makes kdav-19.08.2 fail with HTTP error (400)
https://bugs.kde.org/show_bug.cgi?id=413117 David Faure changed: What|Removed |Added CC||fa...@kde.org --- Comment #1 from David Faure --- This has been fixed in https://phabricator.kde.org/D24880 for 5.64. Any chance you can test that the fix works for you? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413411] New: "Titlebar buttons" tab of the "Window decorations" KCM shows pixelated icon if fractional display scaling is used
https://bugs.kde.org/show_bug.cgi?id=413411 Bug ID: 413411 Summary: "Titlebar buttons" tab of the "Window decorations" KCM shows pixelated icon if fractional display scaling is used Product: systemsettings Version: 5.17.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- Created attachment 123467 --> https://bugs.kde.org/attachment.cgi?id=123467=edit screenshot STEPS TO REPRODUCE 1. set display scale factor to 1.2 in system settings > display and monitor > display configuration 2. restart plasma session 3. open system settings > application style > window decorations and select "Titlebar buttons" tab. OBSERVED RESULT As we can see in the attached screenshot, the icon that represents the apps icons is pixelated. EXPECTED RESULT crisp icon SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.14.0 beta2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413410] New: Mac Os 10.15 valgrind 3.15.0
https://bugs.kde.org/show_bug.cgi?id=413410
Bug ID: 413410
Summary: Mac Os 10.15 valgrind 3.15.0
Product: valgrind
Version: unspecified
Platform: Homebrew (macOS)
OS: macOS
Status: REPORTED
Severity: crash
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: aitem1...@icloud.com
Target Milestone: ---
--27658-- Valgrind options:
--27658----tool=memcheck
--27658----xml=yes
--27658--
--xml-file=/private/var/folders/vv/f22t8y7d1l96ynv9mzgy0j5wgn/T/valgrind
--27658----gen-suppressions=all
--27658----leak-check=yes
--27658---v
--27658-- Output from sysctl({CTL_KERN,KERN_VERSION}):
--27658-- Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019;
root:xnu-6153.11.26~2/RELEASE_X86_64
--27658-- Arch and hwcaps: AMD64, LittleEndian,
amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand
--27658-- Page sizes: currently 4096, max supported 4096
--27658-- Valgrind library directory:
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind
--27658-- /Users/artemsereda/CLionProjects/Block2/cmake-build-debug/client (rx
at 0x1, rw at 0x11000)
--27658--reading syms from primary file (2 9)
--27658--dSYM=
/Users/artemsereda/CLionProjects/Block2/cmake-build-debug/client.dSYM/Contents/Resources/DWARF/client
--27658--reading dwarf3 from dsyms file
--27658-- /usr/lib/dyld (rx at 0x14000, rw at 0x100093000)
--27658--reading syms from primary file (5 2667)
--27658-- Scheduler: using generic scheduler lock implementation.
--27658-- Reading suppressions file:
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind/default.supp
==27658== embedded gdbserver: reading from
/var/folders/vv/f22t8y7d1l96ynv9mzgy0j5wgn/T//vgdb-pipe-from-vgdb-to-27658-by-artemsereda-on-???
==27658== embedded gdbserver: writing to
/var/folders/vv/f22t8y7d1l96ynv9mzgy0j5wgn/T//vgdb-pipe-to-vgdb-from-27658-by-artemsereda-on-???
==27658== embedded gdbserver: shared mem
/var/folders/vv/f22t8y7d1l96ynv9mzgy0j5wgn/T//vgdb-pipe-shared-mem-vgdb-27658-by-artemsereda-on-???
==27658==
==27658== TO CONTROL THIS PROCESS USING vgdb (which you probably
==27658== don't want to do, unless you know exactly what you're doing,
==27658== or are doing some strange experiment):
==27658== /usr/local/Cellar/valgrind/3.15.0/lib/valgrind/../../bin/vgdb
--pid=27658 ...command...
==27658==
==27658== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==27658== /path/to/gdb
/Users/artemsereda/CLionProjects/Block2/cmake-build-debug/client
==27658== and then give GDB the following command
==27658== target remote |
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind/../../bin/vgdb --pid=27658
==27658== --pid is optional if only one valgrind process is running
==27658==
--27658-- REDIR: 0x100053840 (dyld:strcmp) redirected to 0x258057de2 (???)
--27658-- REDIR: 0x10004db20 (dyld:arc4random) redirected to 0x258057e80 (???)
--27658-- REDIR: 0x100052c20 (dyld:strlen) redirected to 0x258057db1 (???)
--27658-- REDIR: 0x100052a0e (dyld:strlcat) redirected to 0x258057e1b (???)
--27658-- REDIR: 0x100053b40 (dyld:strcpy) redirected to 0x258057dfe (???)
--27658-- REDIR: 0x100050cb4 (dyld:strcat) redirected to 0x258057dc2 (???)
--27658-- UNKNOWN fcntl 98!
--27658-- UNKNOWN fcntl 101!
--27658--
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind/vgpreload_core-amd64-darwin.so
(rx at 0x100105000, rw at 0x10010b000)
--27658--reading syms from primary file (3 93)
--27658--dSYM=
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind/vgpreload_core-amd64-darwin.so.dSYM/Contents/Resources/DWARF/vgpreload_core-amd64-darwin.so
--27658-- UNKNOWN fcntl 98! (repeated 2 times)
--27658-- UNKNOWN fcntl 101! (repeated 2 times)
--27658--
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind/vgpreload_memcheck-amd64-darwin.so
(rx at 0x10010f000, rw at 0x100117000)
--27658--reading syms from primary file (72 102)
--27658--dSYM=
/usr/local/Cellar/valgrind/3.15.0/lib/valgrind/vgpreload_memcheck-amd64-darwin.so.dSYM/Contents/Resources/DWARF/vgpreload_memcheck-amd64-darwin.so
--27658-- /usr/lib/libSystem.B.dylib (rx at 0x10011d000, rw at 0x10011f000)
--27658--reading syms from primary file (29 8)
--27658-- UNKNOWN fcntl 98! (repeated 4 times)
--27658-- UNKNOWN fcntl 101! (repeated 4 times)
--27658-- /usr/lib/system/libcache.dylib (rx at 0x100127000, rw at 0x10012d000)
--27658--reading syms from primary file (32 29)
--27658-- /usr/lib/system/libcommonCrypto.dylib (rx at 0x100134000, rw at
0x10014)
--27658--reading syms from primary file (242 172)
--27658-- /usr/lib/system/libcompiler_rt.dylib (rx at 0x10015, rw at
0x100158000)
--27658--reading syms from primary file (505 8)
--27658-- /usr/lib/system/libcopyfile.dylib (rx at 0x100167000, rw at
0x100171000)
--27658--reading syms from primary file (11 39)
--27658-- UNKNOWN fcntl 98! (repeated 8 times)
--27658-- UNKNOWN
[kate] [Bug 413409] New: No VHDL highlight for uppercase VHDL keywords
https://bugs.kde.org/show_bug.cgi?id=413409 Bug ID: 413409 Summary: No VHDL highlight for uppercase VHDL keywords Product: kate Version: 19.08.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: leobe...@live.it Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Write some VHDL keywords (ENTITY, PORT, ...) in uppercase OBSERVED RESULT No highlight EXPECTED RESULT Should be highlighted because VHDL is case-insensitive SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION VHDL is a case-insensitive description language and keywords can be written uppercase or lowercase. In the first case they aren't highlighted by kate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413145] No Context Help button in Aurorae themes
https://bugs.kde.org/show_bug.cgi?id=413145 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #3 from Patrick Silva --- Created attachment 123466 --> https://bugs.kde.org/attachment.cgi?id=123466=edit missing context help button on Plasma 5.17.1 Context help button is still missing on my system after update to Plasma 5.17.1. I use sweet aurorae theme. Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.14.0 beta2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413407] The search field should have keyboard focus when Discover is launched
https://bugs.kde.org/show_bug.cgi?id=413407 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Patch: https://phabricator.kde.org/D24935 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413369] unhandled amd64-darwin syscall: unix:151 (getpgid)
https://bugs.kde.org/show_bug.cgi?id=413369 Rhys Kidd changed: What|Removed |Added CC||rhysk...@gmail.com Assignee|jsew...@acm.org |rhysk...@gmail.com Summary|unhandled syscall getpgid |unhandled amd64-darwin ||syscall: unix:151 (getpgid) -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 413401] Plots are not saved
https://bugs.kde.org/show_bug.cgi?id=413401 Alexander Semke changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/lab ||plot/9fb1574cf3bfba33a88143 ||d2a326ebab0d0042db Version Fixed In||2.8 --- Comment #2 from Alexander Semke --- Git commit 9fb1574cf3bfba33a88143d2a326ebab0d0042db by Alexander Semke. Committed on 24/10/2019 at 20:51. Pushed by asemke into branch 'master'. In plot data dialog, don't add new worksheets as children to workbooks, use the proper parent aspect. FIXED-IN: 2.8 M +3-1src/kdefrontend/spreadsheet/PlotDataDialog.cpp https://commits.kde.org/labplot/9fb1574cf3bfba33a88143d2a326ebab0d0042db -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 401054] Stream parser exceptions
https://bugs.kde.org/show_bug.cgi?id=401054 --- Comment #5 from Aaron Williams --- I believe this is due to https://bugs.kde.org/show_bug.cgi?id=403903 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413408] New: Chrome previews don't update thumbnails
https://bugs.kde.org/show_bug.cgi?id=413408 Bug ID: 413408 Summary: Chrome previews don't update thumbnails Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons-only Task Manager Assignee: h...@kde.org Reporter: alexis.diava...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 123465 --> https://bugs.kde.org/attachment.cgi?id=123465=edit screenshot SUMMARY That bug affects both "Icons Only" and the "Default" task manager, and it only happens in Chrome, or at least I can't reproduce it on other apps STEPS TO REPRODUCE 1. Open Two Chrome windows, and go to a different site on each 2. Hover on Chrome icon on task manager OBSERVED RESULT It will display the same thumbnail of one of the two pages we have opened, or even something different from previous browsing EXPECTED RESULT Should display the current/active Chrome tab of each Chrome window -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #9 from Harald Sitter --- This should be fixed in unstable and testing already. user editions lag behind because appstream data only refreshes when new snapshots are made, which is done as needed. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 378843] Printing to pdf file produces a file with no text and no embedded fonts
https://bugs.kde.org/show_bug.cgi?id=378843 --- Comment #9 from Attila --- I have just tested on KDE Neon (Qt 5.13.1). It is reproducible. I have reported the issue to QtWebEngine developers. https://bugreports.qt.io/browse/QTBUG-79527 Perhaps someone should change here the status to "reopened" or "verified" because the issue is definitely not resolved. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #8 from Nate Graham --- Yep, looks like the same issue for sure. So when it that going to be demonstrably fixed in production? Are you just waiting on Ubuntu or something? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #7 from Harald Sitter --- Surely that's https://bugs.kde.org/show_bug.cgi?id=413272 which should be fixed for a day or two in dev editions. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #6 from Nate Graham --- *** Bug 403118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403118] Installed page is cluttered and dangerous
https://bugs.kde.org/show_bug.cgi?id=403118 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #5 from Nate Graham --- *** This bug has been marked as a duplicate of bug 403119 *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 413384] LabPlot crashes when trying to evaluate any python cell in embedded Cantor
https://bugs.kde.org/show_bug.cgi?id=413384 Alexander Semke changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Alexander Semke --- Crash in 2.6. Doesn't crash in 2.7 but never shows a result of a computation. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413391] DBus API /org/freedesktop/ScreenSaver is not supported
https://bugs.kde.org/show_bug.cgi?id=413391 --- Comment #19 from Kai Uwe Broulik --- Heh, alright. Glad we could figure this out :) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #5 from Nate Graham --- *** Bug 403120 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403120] Plasma updates are displayed very messily
https://bugs.kde.org/show_bug.cgi?id=403120 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 403119 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 --- Comment #4 from Nate Graham --- *** Bug 404341 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404341] collapse duplicative update information
https://bugs.kde.org/show_bug.cgi?id=404341 --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 403119 *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 413401] Plots are not saved
https://bugs.kde.org/show_bug.cgi?id=413401 --- Comment #1 from Alexander Semke --- I assume you created the XY plot via the context menu and selected in the "Plot Data" dialog the option "new plot in a new worksheet". With this the new worksheet is added as child to the workbook in your project. Workbook should have only spreadsheets, no worksheets. This is a bug and we'll fix it. As a workaround, just create manually a new worksheet first and use it in the plot data dialog. Alternatively, create manually the worksheet, plot and xy-curve and select the data columns from the spreadsheets for x and y-data. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 403119] Plasma components are counted as apps when viewing updates and installed apps
https://bugs.kde.org/show_bug.cgi?id=403119 Nate Graham changed: What|Removed |Added Product|Discover|neon CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Component|discover|Packages Dev Edition ||[unstable] Version|5.14.4 |unspecified --- Comment #3 from Nate Graham --- This seems to be a packaging/AppStream bug in Neon. Other distros I've used recently (Manjaro, openSUSE) correctly mark the various kpackage components as addons of Plasma itself. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 413401] Plots are not saved
https://bugs.kde.org/show_bug.cgi?id=413401 Alexander Semke changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413394] An option to set font size
https://bugs.kde.org/show_bug.cgi?id=413394 --- Comment #2 from alex285 --- (In reply to Nate Graham from comment #1) > The Event Calendar widget does this, but people keep asking for this to be > built into the default Digital Clock widget. I think it's probably > inevitable. it is funny you say, because I related that issue to Event Calendar on a video[1], and i hope it is inevitable because Event Calendar is a great addition! i dont know its codebase if it is active developed etc, but i guess it will gain more attention if it becomes by default although there should be some re-write on options perhaps [1]https://youtu.be/0npewm2YvNo -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413391] DBus API /org/freedesktop/ScreenSaver is not supported
https://bugs.kde.org/show_bug.cgi?id=413391 --- Comment #18 from Guo Yunhe --- Found out this is not a problem of KDE. It was my mistake when building RetroArch. The `--enable-dbus` option wasn't correctly added to the build command. So it skipped the DBus part and look for xdg_screensaver, like Kai said. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413407] New: The search field should have keyboard focus when Discover is launched
https://bugs.kde.org/show_bug.cgi?id=413407 Bug ID: 413407 Summary: The search field should have keyboard focus when Discover is launched Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: n...@kde.org CC: aleix...@kde.org Target Milestone: --- Most windows and apps with search fields follow this pattern, and Discover probably should too. Also, it's not as if keyboard focus is currently somewhere more interesting; in fact nothing at all seems to get focus right now, and hitting the tab key doesn't move it anywhere! Also, once upon a time this was done for Muon in bug 330049. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 413407] The search field should have keyboard focus when Discover is launched
https://bugs.kde.org/show_bug.cgi?id=413407 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 413397] LabPlot crashes when rearranging column for second time
https://bugs.kde.org/show_bug.cgi?id=413397 Alexander Semke changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 412455] Segfault of LabPlot2 when opening settings dropdown
https://bugs.kde.org/show_bug.cgi?id=412455 --- Comment #4 from Alexander Semke --- (In reply to waterlubber from comment #3) > I tried with some other KDE/QT applications, like KDenlive (with the same > menu option) and KStars, and was not able to reproduce the issue there. It > appears to be limited to LabPlot2. I manage to reproduce this only once on my computer. Hard to understand/debug unfortunately... Is LabPlot linked to the same KF5 libraries as kdenlive? Any chance to compile the new version released today (https://labplot.kde.org/2019/10/24/labplot-2-7-released/) and try again? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389660] Lot of "org.kde.powerdevil.backlighthelper[PID]: QDBusArgument: read from a write-only object" in journal log
https://bugs.kde.org/show_bug.cgi?id=389660 --- Comment #3 from k...@xtronics.com --- Oct 24 14:37:19 pocket dbus-daemon[550]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.349' (uid=1001 pid=4920 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev") (using servicehelper) Oct 24 14:37:19 pocket org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object Oct 24 14:37:19 pocket org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object Oct 24 14:37:19 pocket org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object Oct 24 14:37:19 pocket dbus-daemon[550]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Oct 24 14:38:34 pocket dbus-daemon[550]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.349' (uid=1001 pid=4920 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev") (using servicehelper) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 389660] Lot of "org.kde.powerdevil.backlighthelper[PID]: QDBusArgument: read from a write-only object" in journal log
https://bugs.kde.org/show_bug.cgi?id=389660 k...@xtronics.com changed: What|Removed |Added CC||k...@xtronics.com Platform|openSUSE RPMs |Debian stable --- Comment #2 from k...@xtronics.com --- Bug still alive in: libpowerdevilcore24:5.14.5-1 libpowerdevilui5 4:5.14.5-1 "read from a write-only object" sounds like a bug - didn't detect the hardware type? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413406] New: Night color only working while settings window open
https://bugs.kde.org/show_bug.cgi?id=413406 Bug ID: 413406 Summary: Night color only working while settings window open Product: systemsettings Version: 5.17.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: martin.f...@gmail.com Target Milestone: --- SUMMARY Every time I close the settings window for night colors on X11, the night colors get lost. If I let open the settings window, the night colors are staying as expected. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20191022 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION - graphic card NVIDIA GTX 1060 with NVIDIA drivers -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413405] Button icons in Documents Tree View turned small after update
https://bugs.kde.org/show_bug.cgi?id=413405 --- Comment #1 from magib...@hotmail.com --- Created attachment 123464 --> https://bugs.kde.org/attachment.cgi?id=123464=edit Screenshot of kate 19.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413405] New: Button icons in Documents Tree View turned small after update
https://bugs.kde.org/show_bug.cgi?id=413405 Bug ID: 413405 Summary: Button icons in Documents Tree View turned small after update Product: kate Version: 19.08.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: magib...@hotmail.com Target Milestone: --- Created attachment 123463 --> https://bugs.kde.org/attachment.cgi?id=123463=edit Screenshot of kate 19.08.1 SUMMARY After updating from 19.08.1 to 19.08.2, the button icons in the Documents tool view (New document, Open document, Previous/Next document...) turned from 22x22 to 16x16. kate was not the only KDE app that received an update that day, though I'm certain the issue was already affecting me before updating Frameworks from 5.62 to 5.63. I am not entitled to dictate what the application should look like, but I clearly found this change to worsen my experience. I tried to find a setting for the size of those icons but failed to do so. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.7-arch1-1-ARCH OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 11,6 GiB of RAM ADDITIONAL INFORMATION Thank you very much. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 413086] Can't create .tar.lz4 nor .tar.zst files.
https://bugs.kde.org/show_bug.cgi?id=413086 --- Comment #5 from Tony --- (In reply to Méven Car from comment #4) > How about `/usr/lib/x86_64-linux-gnu/libarchive.so.13` or wherever > libarchive.so is on your system ? Tumbleweed:~> ls -l /usr/lib64/ | grep libarchive lrwxrwxrwx 1 root root20 Oct 8 15:11 libarchive.so -> libarchive.so.13.4.0 lrwxrwxrwx 1 root root20 Oct 8 15:11 libarchive.so.13 -> libarchive.so.13.4.0 -rwxr-xr-x 1 root root797464 Oct 8 15:11 libarchive.so.13.4.0 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 412496] Can't alter copy/paste shortcut and it doesn't respect the KDE global shortcuts for copy/paste
https://bugs.kde.org/show_bug.cgi?id=412496 --- Comment #3 from Adam --- Also, Konsole allows me to remap to ctrl-c/v. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 412496] Can't alter copy/paste shortcut and it doesn't respect the KDE global shortcuts for copy/paste
https://bugs.kde.org/show_bug.cgi?id=412496 --- Comment #2 from Adam --- Of all the terminals I have used, Yakuake is the only one that won't allow me to remap the shortcut. I use ctrl c/v a hell of a lot more than I ever need to send SIGTERM and it's quite detrimental to my workflow. Ctrl-shift+CV is not an easy thing to do one handed and is extremely cumbersome. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413394] An option to set font size
https://bugs.kde.org/show_bug.cgi?id=413394 Nate Graham changed: What|Removed |Added Keywords||usability Status|REPORTED|CONFIRMED Flags|Usability+ |Usability- Ever confirmed|0 |1 CC||n...@kde.org --- Comment #1 from Nate Graham --- The Event Calendar widget does this, but people keep asking for this to be built into the default Digital Clock widget. I think it's probably inevitable. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401940] More than one Assistant Tool causes black rectangle to appear
https://bugs.kde.org/show_bug.cgi?id=401940 Nate changed: What|Removed |Added CC||n...@heroicdreams.com --- Comment #14 from Nate --- I just ran into this after watching a video on the Assistant tool. I decided to try out the tool by setting up guides for isometric drawing but the screen kept going black on zoom it. It appears to happen with the ends of assistants are all out of view and you are zooming in between them. I had assistants drawn over the entire canvas so if I zoomed in more than 50% it would all go black. After testing a much smaller assistants you can tell it is only if you are zooming in between endpoints. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413394] An option to set font size
https://bugs.kde.org/show_bug.cgi?id=413394 Gerhard Dittes changed: What|Removed |Added Flags||Usability+, VisualDesign+ CC||g-...@web.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412278] Assertion failure when trying to open a specific kra document
https://bugs.kde.org/show_bug.cgi?id=412278 Boudewijn Rempt changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412747] Crashed when editing global selection mask (Safe assert: clonedDocument->image()->isIdle() at KisDocument.cpp 1006)
https://bugs.kde.org/show_bug.cgi?id=412747 Boudewijn Rempt changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 378843] Printing to pdf file produces a file with no text and no embedded fonts
https://bugs.kde.org/show_bug.cgi?id=378843 --- Comment #8 from Attila --- Thanks for your reply. Unfortunately Qt 5.13 is not available on Fedora 30 but hopefully on Fedora 31. I will give it a try then and if it still doesn't work, I will report it to QtWebEngine developers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412756] Artifacts on 8 bit brushes that get composited at low transparencies.
https://bugs.kde.org/show_bug.cgi?id=412756 Boudewijn Rempt changed: What|Removed |Added Severity|normal |wishlist --- Comment #3 from Boudewijn Rempt --- Putting to wish/project since we want to make it an Intel project. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412905] bugged "reference images" layer
https://bugs.kde.org/show_bug.cgi?id=412905 Boudewijn Rempt changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406668] Touch docker/QML does not response to tablet input with WinInk
https://bugs.kde.org/show_bug.cgi?id=406668 Boudewijn Rempt changed: What|Removed |Added Status|ASSIGNED|CONFIRMED Assignee|dimul...@gmail.com |krita-bugs-n...@kde.org -- 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 #13 from Andi Sardina --- @Postix I was wrong about what I said in my last comment. The code for updating the UI is in a different place. I have moved it to only show a tab when the file is successfully opened. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412860] Mouse pointer randomly appearing when pop up shows up
https://bugs.kde.org/show_bug.cgi?id=412860 Boudewijn Rempt changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Boudewijn Rempt --- the latter wouldn't be too hard; it might even be made generic, a way to add all dockers as popup buttons to the toolbar. But that would be a (new) wish bug. If the issue with the cursor also happens in other applications (I wouldn't have noticed, because I use three applications on macOS, Terminal, Krita and Firefox...), then it's not a bug in Krita, I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 395609] New Text File is created with 600 (-rw-------) permissions
https://bugs.kde.org/show_bug.cgi?id=395609 Alex Bikadorov changed: What|Removed |Added CC||bb0...@gmail.com --- Comment #12 from Alex Bikadorov --- *** Bug 413389 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 413389] When I create a new file in Krusader (Shift+F4), the permissions will be 600 instead of 644
https://bugs.kde.org/show_bug.cgi?id=413389 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Alex Bikadorov --- Already fixed in version 2.7.2. *** This bug has been marked as a duplicate of bug 395609 *** -- 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 --- Comment #4 from Ingo --- This is the bug in the poppler issue tracker: https://gitlab.freedesktop.org/poppler/poppler/issues/832 It got closed today, so their fix should be available soon. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 413324] "Typewriter" annotation tool - Text too high to show some diacritics
https://bugs.kde.org/show_bug.cgi?id=413324 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #5 from Albert Astals Cid --- ok, i can reproduce -- You are receiving this mail because: You are watching all bug changes.
[kolf] [Bug 413383] kolf installs a private library system-wide
https://bugs.kde.org/show_bug.cgi?id=413383 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://commits.kde.org/kol ||f/78eb81496525ee5d97d78b259 ||0ca75b25831b904 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Albert Astals Cid --- Git commit 78eb81496525ee5d97d78b2590ca75b25831b904 by Albert Astals Cid. Committed on 24/10/2019 at 18:12. Pushed by aacid into branch 'master'. Don't install the kolfprivate lib Also doesn't need a SOVERSION, it's a private lib M +0-6CMakeLists.txt https://commits.kde.org/kolf/78eb81496525ee5d97d78b2590ca75b25831b904 -- You are receiving this mail because: You are watching all bug changes.
[kolf] [Bug 413383] kolf installs a private library system-wide
https://bugs.kde.org/show_bug.cgi?id=413383 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- by now you mean in master, right? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 413404] New: KDE Connect nicht KDE-Connect
https://bugs.kde.org/show_bug.cgi?id=413404 Bug ID: 413404 Summary: KDE Connect nicht KDE-Connect Product: i18n Version: unspecified Platform: unspecified OS: unspecified Status: REPORTED Severity: normal Priority: NOR Component: de Assignee: kde-i18n...@kde.org Reporter: villene...@arcor.de Target Milestone: --- Hallo, wie mir von Entwicklerseite bestätigt wurde wird KDE Connect offiziell ohne Bindestrich geschrieben, jedoch sowohl in der Desktop-Komponente als auch in der Android-App ist mehrmals von KDE-Connect die Rede. Bitte korrigieren! Vielen Dank! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413328] mouse can go out of monitor in dual monitor setup
https://bugs.kde.org/show_bug.cgi?id=413328 --- Comment #2 from lestofant...@gmail.com --- fixed by deleting the kscreen folder under ~/.local/share; looks like even if I enable/disable the monitors and change the conf, something broken get carried over. I think proper fix should be to find the problematic configuration and get rid of it at load time -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413326] secondary screen goes black after login, mouse still visible
https://bugs.kde.org/show_bug.cgi?id=413326 --- Comment #2 from lestofant...@gmail.com --- fixed by deleting the kscreen folder under ~/.local/share; looks like even if I enable/disable the monitors and change the conf, something broken get carried over. I think proper fix should be to find the problematic configuration and get rid of it at load time -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413329] dual monitor configuration break secondary extended monitor
https://bugs.kde.org/show_bug.cgi?id=413329 --- Comment #2 from lestofant...@gmail.com --- fixed by deleting the kscreen folder under ~/.local/share; looks like even if I enable/disable the monitors and change the conf, something broken get carried over. I think proper fix should be to find the problematic configuration and get rid of it at load time -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 413390] Date in 'Help/About KDevelop' shows year "2.019" instead of "2019"
https://bugs.kde.org/show_bug.cgi?id=413390 --- Comment #6 from Karl Ove Hufthammer --- > When using semantic markup (KDE User Interface Text = KUIT), one needs to > use the xi18n call variants with KF5's KI18n API. > See https://api.kde.org/frameworks/ki18n/html/prg_guide.html#kuit_markup > > It might be more simple though to just format the year as string using the > respective QLocale date string methods and then pass this string as arg. According to that page, one should just use QString::number(year). And that seems simple enough. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 407397] Impossible to adjust the volume level of the notification sounds
https://bugs.kde.org/show_bug.cgi?id=407397 --- Comment #32 from steddy --- Persists in Kubuntu 19.10 with Plasma 5.17.1 Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 410656] The increase (or decrease) of the audio volume with the keyboard shortcut produces a loop in certain conditions (increase/decrease won't stop)
https://bugs.kde.org/show_bug.cgi?id=410656 --- Comment #4 from steddy --- Persists in Kubuntu 19.10 with Plasma 5.17.1. Quite annoying Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-19-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413391] DBus API /org/freedesktop/ScreenSaver is not supported
https://bugs.kde.org/show_bug.cgi?id=413391 --- Comment #17 from Kai Uwe Broulik --- Sure, but not on the /org/freedesktop/ScreenSaver path. It either sends it to the /ScreenSaver or it uses xdg-screensaver but never does it properly send a message to /org/freedesktop/ScreenSaver In https://bugsfiles.kde.org/attachment.cgi?id=123461 it calls Inhibit "RetroArch" on /ScreenSaver which works. In https://bugsfiles.kde.org/attachment.cgi?id=123459 it checks for org.gnome.ScreenSaver, org.mate.ScreenSaver, org.cinnamon.ScreenSaver, and because it doesn't find any, then uses xdg-screensaver which will run and quit releasing the inhibition. Under no circumstance does it properly send Inhibit "RetroArch" on /org/freedesktop/ScreenSaver. Both of these outputs behave wildly different. -- You are receiving this mail because: You are watching all bug changes.
[kalzium] [Bug 413180] Kalzium claims all elements were "known to ancient cultures".
https://bugs.kde.org/show_bug.cgi?id=413180 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org Version Fixed In||19.08.3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413391] DBus API /org/freedesktop/ScreenSaver is not supported
https://bugs.kde.org/show_bug.cgi?id=413391 --- Comment #16 from Guo Yunhe --- Both were compiled with `--enable-dbus` flag. In both dbus-monitor logs, we can find it sends "org.freedesktop.ScreenSaver" message. -- You are receiving this mail because: You are watching all bug changes.
