[okular] [Bug 389206] Efficiently generate print data when Qt's new "arbitrary pages" feature is used
https://bugs.kde.org/show_bug.cgi?id=389206 Yuri Chornoivan changed: What|Removed |Added CC||jeremy.lorelli.1337@gmail.c ||om --- Comment #3 from Yuri Chornoivan --- *** Bug 421670 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421670] Okular hangs when printing pages specified in "Print range -> Pages"
https://bugs.kde.org/show_bug.cgi?id=421670 Yuri Chornoivan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #4 from Yuri Chornoivan --- *** This bug has been marked as a duplicate of bug 389206 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421712] Sidebar text turns white or disappear
https://bugs.kde.org/show_bug.cgi?id=421712 --- Comment #4 from Maik Qualmann --- Yes, the text from the sidebar can be shortened with ... or disappear completely if there is not enough space on the screen. In the digiKam setup under Miscellaneous you can set that the text should only be displayed for active tabs. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421712] Sidebar text turns white or disappear
https://bugs.kde.org/show_bug.cgi?id=421712 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- Can you take a screenshot please? The log shows nothing unusual. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 421714] New: plasma panel crashes when adding when adding browser widget
https://bugs.kde.org/show_bug.cgi?id=421714 Bug ID: 421714 Summary: plasma panel crashes when adding when adding browser widget Product: plasma-browser-integration Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: pelardona...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. click on panel 2. +Add widget 3. drag web browser widget into panel OBSERVED RESULT segfaults in a loop EXPECTED RESULT no segfault, and a web browser link SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.5.5 (available in About System) KDE Plasma Version: 5.18.0 KDE Frameworks Version: 5.18.0 Qt Version: 5.5.1 ADDITIONAL INFORMATION restored older plasma-org.kde.plasma.desktop-appletsrc that was Ok, which did not have [Containments][1][Applets][389] immutability=1 plugin=org.kde.plasma.webbrowser -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 421713] New: I played the tiny killer and I found that the game has ambiguities
https://bugs.kde.org/show_bug.cgi?id=421713 Bug ID: 421713 Summary: I played the tiny killer and I found that the game has ambiguities Product: ksudoku Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: iandw...@gmail.com Reporter: delam...@unam.mx CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 128562 --> https://bugs.kde.org/attachment.cgi?id=128562=edit I played the tiny killer and I found that the game has ambiguities SUMMARY I opened a Tiny Killer and I found that it has a situation where there are ambiguities Below I send the saved game where you can see the problem STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421712] Sidebar text turns white or disappear
https://bugs.kde.org/show_bug.cgi?id=421712 --- Comment #2 from Rachael Greig --- I'm sorry, maybe it disappeared because of insufficient display space. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 421434] smb4k crashed when closed with ctrl+q
https://bugs.kde.org/show_bug.cgi?id=421434 --- Comment #2 from Alexander Reinholdt --- Thank you for reporting this issue. I tried to reproduce your problem on a KDE neon User and on a Kubuntu 20.04 system. However, I wasn't successful. Is the problem still occurring? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421712] Sidebar text turns white or disappear
https://bugs.kde.org/show_bug.cgi?id=421712 --- Comment #1 from Rachael Greig --- And after Album text turns white, it turns black when mouse move over it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421712] New: Sidebar text turns white or disappear
https://bugs.kde.org/show_bug.cgi?id=421712
Bug ID: 421712
Summary: Sidebar text turns white or disappear
Product: digikam
Version: 6.4.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Usability-Ergonomy
Assignee: digikam-bugs-n...@kde.org
Reporter: huohuo5...@gmail.com
Target Milestone: ---
SUMMARY
Sidebar text turns white or disappear.
STEPS TO REPRODUCE
1. Show status bar.
2. Sidebar text disappears.
3. Close status bar.
4. some sidebar text appears.
1. Click one entry in sidebar, like Albums.
2. Click another, like Tags.
3. Now Album text turns white.
OBSERVED RESULT
Sidebar text disappears, Album text turns white.
EXPECTED RESULT
Sidebar text shouldn't disappear, Album text keeps black.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
ADDITIONAL INFORMATION
```
$ export QT_LOGGING_RULES="digikam*=true"
$ digikam
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is
created.
digikam.widgets: Use installed icons
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
Icon theme "gnome" not found.
digikam.general: AlbumWatch is disabled
digikam.general: Database Parameters:
Type: "QSQLITE"
DB Core Name: "/home/*/.config/digiKam/digikam4.db"
DB Thumbs Name: "/home/*/.config/digiKam/thumbnails-digikam.db"
DB Face Name: "/home/*/.config/digiKam/recognition.db"
DB Similarity Name: "/home/*/.config/digiKam/similarity.db"
Connect Options: ""
Host Name:""
Host port:-1
Internal Server: false
Internal Server Path: ""
Internal Server Serv Cmd: ""
Internal Server Init Cmd: ""
Username: ""
Password: ""
digikam.dbengine: Loading SQL code from config file
"/usr/share/digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected: 3 found: 3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version 10
digikam.coredb: Core database: makeUpdates 10 to 10
digikam.database: Creating new Location
"/Office/Files-Sync-Computer/Pictures/Photos-Temp" uuid
"volumeid:?uuid=8006a77e06a773b6"
digikam.database: location for "/run/media/*/Photos-Temp" is available true
KMemoryInfo: Platform identified : "LINUX"
KMemoryInfo: TotalRam: 8227274752
digikam.general: Allowing a cache size of 200 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
digikam.thumbsdb: Thumbs database: have a structure version "3"
digikam.general: Thumbnails database ready for use
digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
digikam.similaritydb: SimilarityDb SelectSimilaritySetting val ret = 0
digikam.similaritydb: Similarity database: have a structure version "1"
digikam.similaritydb: Similarity database ready for use
digikam.dimg: ("/usr/share/color/icc")
digikam.dimg: No X.org XICC profile installed for screen 0
digikam.general: Camera XML data: "/home/*/.local/share/digikam/cameras.xml"
digikam.general: Starting to load external tools.
digikam.general: Parsing plugins from "/usr/lib/qt/plugins/digikam/"
digikam.general: Plugins found: 131
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_HotpixelsTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_FreeRotationTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_FilmTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_PerspectiveTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_InvertTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_AutoCropTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_AntivignettingTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_BlurTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_HSLTool_Plugin.so"
digikam.general: Plugin of type Digikam::DPluginEditor loaded from
"/usr/lib/qt/plugins/digikam/editor/Editor_RatioCropTool_Plugin.so"
[krusader] [Bug 407102] Single instance not working in root mode
https://bugs.kde.org/show_bug.cgi?id=407102 --- Comment #13 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.
[rkward] [Bug 414437] R Engine failed when I start RKWARD
https://bugs.kde.org/show_bug.cgi?id=414437 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420245] Bottom panel missing each time after reboot
https://bugs.kde.org/show_bug.cgi?id=420245 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 406757] Bug in first start
https://bugs.kde.org/show_bug.cgi?id=406757 --- 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 421708] Some combination of copying, pasting, and saving a new file creates phantom pixels that remain in a .kra file no matter what you do
https://bugs.kde.org/show_bug.cgi?id=421708 Lynx3d changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||lynx.mw+...@gmail.com --- Comment #1 from Lynx3d --- Well I'm afraid that's a user error, you apparently pasted those things as reference images, because that's what they are. Select the Reference Images Tool, select and delete them if you don't want those anymore. If you keep doing this by accident, you may disable the keyboard shortcut for "Paste as Reference Image". I hope this solves your problem. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396543] Bookmark context sub-menus opens near mouse
https://bugs.kde.org/show_bug.cgi?id=396543 --- 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.
[rkward] [Bug 400519] Crash on change of workspaces
https://bugs.kde.org/show_bug.cgi?id=400519 --- 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.
[krusader] [Bug 403573] Will not save directory for Syncronize Folders
https://bugs.kde.org/show_bug.cgi?id=403573 --- 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.
[rkward] [Bug 396691] on line search Crashed RKward
https://bugs.kde.org/show_bug.cgi?id=396691 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 421711] New: Energy error kde plasma
https://bugs.kde.org/show_bug.cgi?id=421711 Bug ID: 421711 Summary: Energy error kde plasma Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: francisco42...@outlook.com Target Milestone: --- Application: org_kde_powerdevil (2.0.0) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: - Unusual behavior I noticed: When turning on my computer, a power failure report came out in kde plasma, without using any program or action -- Backtrace: Application: Sistema de gestión de energía de KDE (org_kde_powerdevil), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4eabc99800 (LWP 1419))] Thread 5 (Thread 0x7f4e92adf700 (LWP 1478)): #0 0x7f4ea86fa0b4 in __GI___libc_read (fd=20, buf=0x7f4e92adeb90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f4ea34af2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4ea346a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4ea346a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4ea346a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4ea90657cb in QEventDispatcherGlib::processEvents (this=0x7f4e8b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f4ea9004d2a in QEventLoop::exec (this=this@entry=0x7f4e92adeda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f4ea8e15757 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f4ea8e16c2c in QThreadPrivate::start (arg=0x563aa5511760) at thread/qthread_unix.cpp:342 #9 0x7f4ea5a216db in start_thread (arg=0x7f4e92adf700) at pthread_create.c:463 #10 0x7f4ea870b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f4e93fff700 (LWP 1460)): #0 0x7f4ea86fa0b4 in __GI___libc_read (fd=11, buf=0x7f4e93ffecd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f4ea34af2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4ea346a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4ea346a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4ea346a962 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4e99bf6276 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7f4ea3492175 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f4ea5a216db in start_thread (arg=0x7f4e93fff700) at pthread_create.c:463 #8 0x7f4ea870b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f4e98e33700 (LWP 1459)): #0 0x7f4ea86fa0b4 in __GI___libc_read (fd=9, buf=0x7f4e98e32ce0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f4ea34af2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4ea346a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4ea346a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f4ea346a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f4ea346a721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f4ea3492175 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f4ea5a216db in start_thread (arg=0x7f4e98e33700) at pthread_create.c:463 #8 0x7f4ea870b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f4e9af5a700 (LWP 1454)): #0 0x7ffe421af99a in clock_gettime () #1 0x7f4ea871aea6 in __GI___clock_gettime (clock_id=clock_id@entry=1, tp=tp@entry=0x7f4e9af59ae0) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f4ea90650d1 in qt_clock_gettime (ts=0x7f4e9af59ae0, clock=) at kernel/qelapsedtimer_unix.cpp:111 #3 do_gettime (frac=, sec=) at kernel/qelapsedtimer_unix.cpp:166 #4 qt_gettime () at kernel/qelapsedtimer_unix.cpp:175 #5 0x7f4ea9063909 in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f4e94005110) at kernel/qtimerinfo_unix.cpp:91 #6 0x7f4ea9063ee5 in QTimerInfoList::timerWait (this=0x7f4e94005110, tm=...) at kernel/qtimerinfo_unix.cpp:388 #7 0x7f4ea906552e in timerSourcePrepareHelper (timeout=0x7f4e9af59ba4, src=) at kernel/qeventdispatcher_glib.cpp:133 #8 timerSourcePrepare (source=, timeout=0x7f4e9af59ba4) at kernel/qeventdispatcher_glib.cpp:166 #9 0x7f4ea3469b28 in g_main_context_prepare () from
[plasmashell] [Bug 421710] New: fail at move shortcut icon to botom left corner on desk
https://bugs.kde.org/show_bug.cgi?id=421710 Bug ID: 421710 Summary: fail at move shortcut icon to botom left corner on desk Product: plasmashell Version: 5.18.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jseh...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: fail at move shortcut icon to botom left corner on desk, ia try to move and icon below another it fail The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6cf29f71c0 (LWP 1335))] Thread 35 (Thread 0x7f6c19205700 (LWP 5138)): #0 0x7f6cebd94bf9 in __GI___poll (fds=0x7f6c1c011550, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6c91a2b481 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f6c91a1ce40 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f6c91a1d4d0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f6c91a1d560 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f6c91a2b3c9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f6c91145318 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #7 0x7f6ce912f6db in start_thread (arg=0x7f6c19205700) at pthread_create.c:463 #8 0x7f6cebda188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7f6c1a207700 (LWP 4630)): #0 0x7f6ce5c165d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6ce5c18f50 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ce5c19570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ce5c19962 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6c9036f276 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7f6ce5c41175 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6ce912f6db in start_thread (arg=0x7f6c1a207700) at pthread_create.c:463 #7 0x7f6cebda188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7f6c1aa08700 (LWP 4629)): #0 0x7f6cebd900b4 in __GI___libc_read (fd=55, buf=0x7f6c1aa07ce0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f6ce5c5e2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ce5c190b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ce5c19570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6ce5c196dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6ce5c19721 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6ce5c41175 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f6ce912f6db in start_thread (arg=0x7f6c1aa08700) at pthread_create.c:463 #8 0x7f6cebda188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7f6c1bfff700 (LWP 4621)): #0 0x7f6ce91359f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55adf7353a04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55adf73539b0, cond=0x55adf73539d8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55adf73539d8, mutex=0x55adf73539b0) at pthread_cond_wait.c:655 #3 0x7f6cec4b31db in QWaitConditionPrivate::wait (deadline=..., this=0x55adf73539b0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x55adf9e13e70, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f6cec4b3359 in QWaitCondition::wait (this=0x55adf9e81968, mutex=0x55adf9e13e70, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f6c899e1855 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7f6c899e56b8 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7f6c899e0b1d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7f6c899e5712 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7f6c899e0b1d in
[digikam] [Bug 421693] Digikam only read xmp:Label during first import then prioritizes its digiKam:ColorLabel over the xmp:Label.
https://bugs.kde.org/show_bug.cgi?id=421693 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 418806 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 418806] digikam:colorlabel in xmp sidecar files not compatible with external programs
https://bugs.kde.org/show_bug.cgi?id=418806 Maik Qualmann changed: What|Removed |Added CC||e...@airmail.cc --- Comment #6 from Maik Qualmann --- *** Bug 421693 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421709] New: layers erase their content, won't let me recover the progress
https://bugs.kde.org/show_bug.cgi?id=421709 Bug ID: 421709 Summary: layers erase their content, won't let me recover the progress Product: krita Version: 4.2.9-beta1 Platform: Windows CE OS: Windows CE Status: REPORTED Severity: critical Priority: NOR Component: CPU Canvas Assignee: krita-bugs-n...@kde.org Reporter: agt...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. finish piece 2. merge group of layers 3. merge layers OBSERVED RESULT layers erase their content when trying to merge. the layers below cover the content of the following layers. EXPECTED RESULT layers merging without problem SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION autosave is configured to save work every 15 minutes. I spent more than 4 hours using krita, and when the bug presented I opened the autosaved document. It saved only the first sketch I did hours ago. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420598] kendlive crashes upon start on Ubuntu 20.4
https://bugs.kde.org/show_bug.cgi?id=420598 Felix Delacruz changed: What|Removed |Added CC||felix.r.delacruz.jr@gmail.c ||om Platform|Ubuntu Packages |Kubuntu Packages --- Comment #1 from Felix Delacruz --- Fresh install of kdenlive Snap from Discover. Launch, after splash screen I get the following: Could not create the video preview window. There is something wrong with your Kdenlive install or your driver settings, please fix it. Click OK and crashes the app. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-29-lowlatency OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6770HQ CPU @ 2.60GHz Memory: 15.1 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421584] File Saving is getting extremely slow
https://bugs.kde.org/show_bug.cgi?id=421584 Lynx3d changed: What|Removed |Added CC||lynx.mw+...@gmail.com --- Comment #12 from Lynx3d --- Okay I dug a bit into this, for me it was mergedimage.png that ate the most amount of time compressing, and the reason is apparently that since this commit 4d609a56ef572b22ec9a712985e1927c7a0143d0 the compression level is now Z_BEST_COMPRESSION (level 9), because KoQuaZipStore::setCompressionEnabled(true) set this, while initially it is initialized with Z_DEFAULT_COMPRESSION (-1, which apparently is 6 internally for zlib). Using Z_DEFAULT_COMPRESSION gets the save time and file size pretty much identically to the old code used in krita 4.2.9 on the file I tested. The file size difference was pretty much negligible btw, ~200kB for a 23MB file for taking 3-4 times longer to save. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421708] Some combination of copying, pasting, and saving a new file creates phantom pixels that remain in a .kra file no matter what you do
https://bugs.kde.org/show_bug.cgi?id=421708 alphalimata...@runbox.com changed: What|Removed |Added CC||alphalimata...@runbox.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421708] New: Some combination of copying, pasting, and saving a new file creates phantom pixels that remain in a .kra file no matter what you do
https://bugs.kde.org/show_bug.cgi?id=421708 Bug ID: 421708 Summary: Some combination of copying, pasting, and saving a new file creates phantom pixels that remain in a .kra file no matter what you do Product: krita Version: 4.2.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: alphalimata...@runbox.com Target Milestone: --- Created attachment 128561 --> https://bugs.kde.org/attachment.cgi?id=128561=edit A .kra file where I see the phantom pixels SUMMARY I have a workflow that somewhat frequently creates images with "phantom pixels." These are parts of a drawing that were in my clipboard and which appear on the canvas, but which can't be deleted. They don't appear as part of any layer and they can't be removed from the file. I have to make a new file to get rid of them. The pixels can't be selected or made invisible, but the eyedropper tool is aware of them. The move tool can't move them, the pixels appear outside the image when cropping, and they appear in front of every other layer. I don't know the exact steps to reproduce this, but I have a file that's in this corrupted state. My workflow is generally: 1. Draw in a .kra file over many sessions, filling it with doodles 2. When the file is filled up, go to Save As -> new file, delete all the layers except the background layer, make a new layer, and keep drawing. Sometimes I'll select parts of the drawing and cut or copy the pixels and paste them into the new version of the file, after saving. This is definitely when the bug happens, but I can't reliably reproduce it. I'm missing some kind of step. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Devuan $ cat /etc/os-release PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)" NAME="Devuan GNU/Linux" VERSION_ID="3" VERSION="3 (beowulf)" VERSION_CODENAME=beowulf ID=debian ID_LIKE=debian HOME_URL="https://www.devuan.org/; SUPPORT_URL="https://devuan.org/os/community; BUG_REPORT_URL="https://bugs.devuan.org/; $ krita --version krita 4.2.9 $ dpkg -l | grep plasma-framework ii plasma-framework 5.54.0-1 amd64Plasma Runtime components $ dpkg -l | grep libqt5core ii libqt5core5a:amd64 5.11.3+dfsg1-1 amd64Qt 5 core module This has happened on Debian as Ubuntu as well, at least as far back as Krita 4.1.5 The attachment demonstrates two separate instances of this happening in one file. I had pixel data in my clipboard that shows text that says "3/24/20 09:32 PM" (for an unrelated reason), and then last night a doodle. Whatever I try I can't get these drawings out of the image, including deleting layers, adding them, etc. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421707] New: Crashed when painting
https://bugs.kde.org/show_bug.cgi?id=421707 Bug ID: 421707 Summary: Crashed when painting 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: acc4commissi...@gmail.com Target Milestone: --- SUMMARY git 5ef8149 (4.3.0-beta nightly) I was just making brushstrokes and Krita crashed. I'm writing a report just in case. There was literally nothing else was going on so I guess it might be related to autosaving or something, but I wouldn't know. I have no idea. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Backtrace : Error occurred on Monday, May 18, 2020 at 09:28:19. krita.exe caused an Access Violation at location 07FED8846DE7 in module Qt5Core.dll Reading from location . AddrPC Params 07FED8846DE7 03E88CB3C9484E2B 07FED88654B0 07FED8C1A200 Qt5Core.dll!0x206de7 QMetaObject::cast+0x17 07FED73C5B11 0070 Qt5Widgets.dll!0x55b11 QGestureRecognizer::unregisterRecognizer+0x6c21 07FED73802C5 07FED866211F 529DFE50 Qt5Widgets.dll!0x102c5 QApplication::notify+0x1a55 07FED51E78C6 0001 001E libkritaui.dll!0x2d78c6 KisApplication::notify+0x16 07FED883D758 0004072E 001F 0251E600 Qt5Core.dll!0x1fd758 QCoreApplication::sendEvent+0x1a8 07FED8897C14 07FED8846DE9 0022BFA8 Qt5Core.dll!0x257c14 QEventDispatcherWin32Private::sendTimerEvent+0xd4 07FED88984E8 0022FBB0 0001 Qt5Core.dll!0x2584e8 QEventDispatcherWin32::event+0xf8 07FED7377BDC 00020003 Qt5Widgets.dll!0x7bdc QApplicationPrivate::notify_helper+0x9c 07FED737EC23 0004072E 07FED866211F 0020 Qt5Widgets.dll!0xec23 QApplication::notify+0x3b3 07FED51E78C6 0B68D9B0 07FEEEDAD03B 541F2750 libkritaui.dll!0x2d78c6 KisApplication::notify+0x16 07FED883D0D8 0001 0001 Qt5Core.dll!0x1fd0d8 QCoreApplication::notifyInternal2+0x198 07FED8843709 FFEB 0010056E Qt5Core.dll!0x203709 QCoreApplicationPrivate::sendPostedEvents+0x199 6A8FE90E 77A469C8 0010056E 0401 qwindows.dll!0x7e90e qt_plugin_instance+0x2a3e 07FED889814A 0038 0022C5F8 Qt5Core.dll!0x25814a QEventDispatcherWin32Private::sendTimerEvent+0x60a 777E9861 0022C720 07FED8897C70 USER32.dll!0x19861 UserCallWinProcCheckWow+0x1ad 777E9572 0022C720 0022C720 07FED8897C70 USER32.dll!0x19572 DispatchMessageWorker+0x3b5 07FED88975EB 0251E600 0024 02402A70 Qt5Core.dll!0x2575eb QEventDispatcherWin32::processEvents+0x5cb 6A8FE8F5 0080 0014 30795A70 qwindows.dll!0x7e8f5 qt_plugin_instance+0x2a25 07FED883B8FF 0843E030 085F5AB0 307F3CA0 Qt5Core.dll!0x1fb8ff QEventLoop::exec+0x13f 07FED8844B77 0022FC00 0022FB70 0008 Qt5Core.dll!0x204b77 QCoreApplication::exec+0x77 000140006E90 0001 023FC290 000140F5F978 krita.exe!0x6e90 main+0x20f0 0001400013C7 krita.exe!0x13c7 __tmainCRTStartup+0x247 0001400014CB krita.exe!0x14cb WinMainCRTStartup+0x1b 778E556D kernel32.dll!0x1556d BaseThreadInitThunk+0xd 77A4372D ntdll.dll!0x5372d RtlUserThreadStart+0x1d 00014000-000140F6F000 krita.exe 779F-77B8F000 ntdll.dll 6.1.7601.24545 07FEF942-07FEF9433000 aswhook.dll 20.3.5200.0 778D-779EF000 kernel32.dll 6.1.7601.24545 07FEFD88-07FEFD8E7000 KERNELBASE.dll6.1.7601.24545 07FEF09D-07FEF0A1B000 libkritaglobal.dll 07FEF09C-07FEF09CE000 libkritaversion.dll 6144-6145A000 libgcc_s_seh-1.dll 07FEFDDB-07FEFDE4F000 msvcrt.dll7.0.7601.17744 6494-64955000 libwinpthread-1.dll 1.0.0.0 6FC4-6FDA5000 libstdc++-6.dll 777D-778CA000 USER32.dll6.1.7601.24546 07FEFE0C-07FEFE127000 GDI32.dll 6.1.7601.24540 07FEFDF3-07FEFDF3E000 LPK.dll
[kdeconnect] [Bug 421706] New: remote smartphone touchscreen doesn't work with limited login on UBUNTU 20.04 (after system error report)
https://bugs.kde.org/show_bug.cgi?id=421706 Bug ID: 421706 Summary: remote smartphone touchscreen doesn't work with limited login on UBUNTU 20.04 (after system error report) Product: kdeconnect Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: woodso...@yahoo.fr Target Milestone: --- SUMMARY remote smartphone touchscreen doesn't work with limited login on UBUNTU 20.04 LTS (after system error report) STEPS TO REPRODUCE 1. kdeconnect worked ubuntu 18.04 LTS (on limited user) 2. upgrade to ubuntu 20.04 LTS 3. after system error report, remote touchscreen doesn't work with limited but work with administrative login OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version:1.4-0ubuntu5 ubuntu-focal-universe ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421494] Dolphin crashes when creating new folder with existing folder name
https://bugs.kde.org/show_bug.cgi?id=421494 --- Comment #2 from sm.emon...@gmail.com --- I am using Dolphin 20.04.0. Still it happens. For some folder it takes 8~9 try, for some folder it takes 1~2 tries. For me creating 'Desktop' folder crashes almost after 1~2 try. I opened Dolphin, pressed F10, typed 'Desktop' and pressed ENTER. Try with my version dolphin. If it doesn't recreate the crash, then I think it will take someday to provide you with the information you need. Because, currently I am using Arch Linux. After searching internet, I found there is no debug symbol in arch. So the only way is to compile it my self. I have compiled some program by my self. But I didn't compiled with debug option enable. Currently I am trying to learn. Thank you for your time. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Gastón M. Tonietti changed: What|Removed |Added CC|gaston.tonie...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421704] `#include ` with parser set to c++2a causes a crash
https://bugs.kde.org/show_bug.cgi?id=421704 --- Comment #1 from krzysio.ku...@wp.pl --- Created attachment 128560 --> https://bugs.kde.org/attachment.cgi?id=128560=edit full backtrace konqui seems to be bugged and can't send the crash as an attachment. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 421705] Make kleopatra be able to use opaque signatures for signing and verifying operations
https://bugs.kde.org/show_bug.cgi?id=421705 Francesco Bonanno changed: What|Removed |Added CC||mibo...@fsfe.org -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 362986] Application Dashboard needs an option for the name to have two lines
https://bugs.kde.org/show_bug.cgi?id=362986 nyanpasu64 changed: What|Removed |Added CC||nyanpas...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 421705] New: Make kleopatra be able to use opaque signatures for signing and verifying operations
https://bugs.kde.org/show_bug.cgi?id=421705 Bug ID: 421705 Summary: Make kleopatra be able to use opaque signatures for signing and verifying operations Product: kleopatra Version: 3.1.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: mibo...@fsfe.org CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY (Even if gpgsm has not yet the support to CAdES compliant signatures, due to the missing but expected function in libksba for signing attributes, and so on) gpgsm can make an opaque signature. So if you do as an example gpgsm gpgsm -s test.txt -o test.txt.p7m, you obtain a signed p7m cryptographic envelope with the file inside. As specified in the source code and in the popup message if you try to do this with kleopatra, it is uncommon, but in some jurisdiciton, like Italy, for the AdES signatures of CMS type (so the CAdES ones), the regulated format is the opaque signature in p7m, not the detached one in p7s. https://www.gazzettaufficiale.it/atto/serie_generale/caricaArticolo?art.progressivo=0=21=1=09A14307=2009-12-03=7=10=1=0 the official gazette of Italy about it. So it will be REALLY nice, to have the possibility to have a button in the sign/encrypt window to choose to use the opaque signature, and in the verify/decrypt window to verify it (gpgsm can do it without issues) or autodetect and verify it. STEPS TO REPRODUCE Try to sign a file with Kleopatra, using a x.509 cert and related private key, making an opaque signature enveloped in a p7m or try to verify a opaque signed envelope. OBSERVED RESULT Kleopatra will complain about the choice of trying renaming the file to a dot p7m, and in any case, the output will be a p7s detached signature. Trying to verify an opaque signed envelope, kleopatra will complain about it. EXPECTED RESULT Kleopatra having a button to choose to make an opaque signature and have as output an opaque signed p7m and verifing no complains about it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Obviously, sorry guys if part of this or all the issue is solved already in the master of kleopatra. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 tguen changed: What|Removed |Added CC||tg...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Add more kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 --- Comment #7 from Dawid Wróbel --- Lastly, the following icons are missing the color option and would be otherwise perfect candidates for sidebar actions: go-home-large view-statistics tag system-users/user-others -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Christoph Feck changed: What|Removed |Added CC||slartibar...@gmail.com --- Comment #198 from Christoph Feck --- *** Bug 421692 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421692] plasma global scale shows artifacts in konsole
https://bugs.kde.org/show_bug.cgi?id=421692 Christoph Feck changed: What|Removed |Added Resolution|NOT A BUG |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 373232 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398908] Dolphin uses up huge amounts of memory
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #67 from Ash --- This Bug is still present in Plasma 5.18.5 and KDE Frameworks 5.70. I tried what Andrei suggested, I built a modified libKF5Solid with the overlays feature removed, and then opened Dolphin to leave it running for 48 hours over the weekend. Unfortunately in my case, it did not fix it. The Dolphin process grew to over 7.8GB memory used, and 100% (of one core) CPU usage for at least the last 24 hours. I believe in this case it is not related to Docker overlays, but more likely related to the multiple NFS4 mounts on the system. I have a different VM with same Ubuntu OS and very similar software stack, it has only one (different) NFS4 mount, and it is not affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421704] New: `#include ` with parser set to c++2a causes a crash
https://bugs.kde.org/show_bug.cgi?id=421704 Bug ID: 421704 Summary: `#include ` with parser set to c++2a causes a crash Product: kdevelop Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: krzysio.ku...@wp.pl Target Milestone: --- Application: kdevelop (5.5.1) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.11-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: Trying to parse a file that has a include causes a crash if the parser has been set to c++2a The crash can be reproduced every time. -- Backtrace (Reduced): #4 clang::ConceptReference::getNamedConcept (this=0x0) at ../tools/clang/include/clang/AST/ASTConcept.h:155 #5 isSameTemplateParameter (X=0x7fba0628e7e8, Y=0x7fba0628ee28) at ../tools/clang/lib/Serialization/ASTReaderDecl.cpp:2890 #6 isSameTemplateParameterList (C=..., X=0x7fba0628e8b8, Y=0x7fba0628eef8) at ../tools/clang/lib/Serialization/ASTReaderDecl.cpp:2981 #7 0x7fba5eb165d5 in isSameEntity (X=0x7fba0628e288, Y=0x7fba0628e8f8) at ../tools/clang/lib/Serialization/ASTReaderDecl.cpp:3183 #8 0x7fba5eb155df in clang::ASTDeclReader::findExisting (this=, D=0x7fba0628e8f8) at ../tools/clang/lib/Serialization/ASTReaderDecl.cpp:3469 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 421703] New: Calculator bug
https://bugs.kde.org/show_bug.cgi?id=421703 Bug ID: 421703 Summary: Calculator bug Product: kstars Version: 3.4.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: tstima...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Launch Calculator 2. Select Conjunctions 3. Select Between Objects, Single Object, Select Jupiter and Saturn 4. Set Start date 5/18/20 5. Set End date 5/18/21 6. Select Conjunction, press Compute 7. Program finds Conjunction on 2020-12-21 8. Press Clear 9. Set End date to 5/18/31 10. Press Compute OBSERVED RESULT Program does not find any conjunction EXPECTED RESULT Program should have found conjunction on 2020-12-21 SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421702] New: discover dont send internet connection and dont open the applications
https://bugs.kde.org/show_bug.cgi?id=421702 Bug ID: 421702 Summary: discover dont send internet connection and dont open the applications Product: Discover Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: enuga...@hotmail.it CC: aleix...@kde.org Target Milestone: --- SUMMARY discover dont open the applications dont internet resource STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS opensuse 15.2 Windows: macOS: Linux/KDE Plasma: 5.18.5 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404959] Icon sizes and type inconsistency
https://bugs.kde.org/show_bug.cgi?id=404959 Dawid Wróbel changed: What|Removed |Added Ever confirmed|1 |0 Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #4 from Dawid Wróbel --- Noah, per our conversation I am changing its stats back. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421701] New: bars and background not visible
https://bugs.kde.org/show_bug.cgi?id=421701 Bug ID: 421701 Summary: bars and background not visible Product: plasmashell Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kde-bug-acc...@online.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.12.7 Frameworks Version: 5.70.0 Operating System: Linux 5.3.18-lp152.14-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.2 Beta -- Information about the crash: - What I was doing when the application crashed: i logged in to plasma session with sddm - Unusual behavior I noticed: The background und the bars are shown for a short time (2s) than a black screen occurse. Only the latte-bar are visible. STRG+ALT+Entf working for logout. After repeating login, the same behavior - Custom settings of the application: -sddm -latte-dock (bar on the left side) -only one desktop (no other virtual desktop/activity) -kde bars on top and bottom -alignment of desktop symbols rigth and column -the behavior are on leap (today) und on tumbleweed (before 4 days) after the update and followed restart -after editing file /.config/plasma-org.kde.plasma.desktop-appletsrc [Containments][1][General] alignment=1 arrangement=1 to [Containments][1][General] alignment=0 arrangement=0 and a logout and new login, the desktop was shown again, but the alignment /arrangement shouldnt be changed again, because the black screen shown again after new loggin. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f70d19b1900 (LWP 3143))] Thread 17 (Thread 0x7f706c48b700 (LWP 3435)): #0 QMutex::unlock (this=this@entry=0x55b96e9b8050) at thread/qmutex.cpp:335 #1 0x7f70cb77d817 in QMutexLocker::unlock (this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:219 #2 QMutexLocker::~QMutexLocker (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:213 #3 QThreadData::canWaitLocked (this=) at ../../include/QtCore/5.12.7/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:269 #4 postEventSourcePrepare (timeout=, s=0x55b96e9bf600) at kernel/qeventdispatcher_glib.cpp:259 #5 postEventSourceCheck (source=0x55b96e9bf600) at kernel/qeventdispatcher_glib.cpp:269 #6 0x7f70c5278109 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #7 0x7f70c5278670 in ?? () from /usr/lib64/libglib-2.0.so.0 #8 0x7f70c52787dc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #9 0x7f70cb77d12b in QEventDispatcherGlib::processEvents (this=0x55b96e546760, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #10 0x7f70cb71e2da in QEventLoop::exec (this=this@entry=0x7f706c48ac70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #11 0x7f70cb54410a in QThread::exec (this=) at thread/qthread.cpp:531 #12 0x7f706cb70c97 in KCupsConnection::run() () from /usr/lib64/libkcupslib.so #13 0x7f70cb5458b2 in QThreadPrivate::start (arg=0x55b96e9b7e90) at thread/qthread_unix.cpp:361 #14 0x7f70c86a34f9 in start_thread () from /lib64/libpthread.so.0 #15 0x7f70cadf1f2f in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f706eb08700 (LWP 3413)): #0 0x7f70c86a987d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f70942f6939 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f70942f73ac in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f70942f743f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f70942b5ef8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f70942b88c6 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f70942b8c64 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f70942f9811 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f70c86a34f9 in start_thread () from /lib64/libpthread.so.0 #9 0x7f70cadf1f2f in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7f707c081700 (LWP 3344)): #0 0x7f70cade31d8 in read () from /lib64/libc.so.6 #1 0x7f709eb48551 in pa_read () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #2 0x7f709f1fe6fe in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0 #3 0x7f709f1ff170 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #4 0x7f709f1ff230 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #5 0x7f709f20ceb9 in ?? () from /usr/lib64/libpulse.so.0 #6 0x7f709eb76018 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-13.0.so #7 0x7f70c86a34f9 in start_thread () from /lib64/libpthread.so.0 #8 0x7f70cadf1f2f in clone () from
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #5 from Tyler Brown --- Created attachment 128559 --> https://bugs.kde.org/attachment.cgi?id=128559=edit Recording of tasks disappearing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] New: Plasma crashed on a Wayland session after I've switched from main laptop to external monitor conected via HDMI port.
https://bugs.kde.org/show_bug.cgi?id=421700 Bug ID: 421700 Summary: Plasma crashed on a Wayland session after I've switched from main laptop to external monitor conected via HDMI port. Product: plasmashell Version: 5.18.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: trader...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I switched from main laptop to external monitor conected via HDMI port. - Unusual behavior I noticed: black area around system windows. - Custom settings of the application: -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f40f50851c0 (LWP 2278))] Thread 4 (Thread 0x7f40cfded700 (LWP 2480)): #0 0x7f40eb7c79f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x563154ff97e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x563154ff9798, cond=0x563154ff97c0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x563154ff97c0, mutex=0x563154ff9798) at pthread_cond_wait.c:655 #3 0x7f40d550cecb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f40d550cac7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f40eb7c16db in start_thread (arg=0x7f40cfded700) at pthread_create.c:463 #6 0x7f40ee43388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f40de2cc700 (LWP 2432)): #0 0x7f40ee4220b4 in __GI___libc_read (fd=11, buf=0x7f40de2cbb70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f40e82f02b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f40e82ab0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f40e82ab570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f40e82ab6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f40eed8d7cb in QEventDispatcherGlib::processEvents (this=0x7f40db20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f40eed2cd2a in QEventLoop::exec (this=this@entry=0x7f40de2cbd80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f40eeb3d757 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f40f26f4fc5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f40eeb3ec2c in QThreadPrivate::start (arg=0x563154ce7cb0) at thread/qthread_unix.cpp:342 #10 0x7f40eb7c16db in start_thread (arg=0x7f40de2cc700) at pthread_create.c:463 #11 0x7f40ee43388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f40e0143700 (LWP 2303)): #0 0x7f40ee426bf9 in __GI___poll (fds=0x7f40d8002de0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f40e82ab5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f40e82ab6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f40eed8d7cb in QEventDispatcherGlib::processEvents (this=0x7f40d8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f40eed2cd2a in QEventLoop::exec (this=this@entry=0x7f40e0142d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f40eeb3d757 in QThread::exec (this=this@entry=0x7f40f0cb3da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:536 #6 0x7f40f0a3b555 in QDBusConnectionManager::run (this=0x7f40f0cb3da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:179 #7 0x7f40eeb3ec2c in QThreadPrivate::start (arg=0x7f40f0cb3da0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:342 #8 0x7f40eb7c16db in start_thread (arg=0x7f40e0143700) at pthread_create.c:463 #9 0x7f40ee43388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f40f50851c0 (LWP 2278)): [KCrash Handler] #4 QScreen::name (this=0x563154afec50) at kernel/qscreen.cpp:171 #5 0x563152996c1c in ShellCorona::addOutput (this=this@entry=0x563154b2c860, screen=, screen@entry=0x563154afec50) at ./shell/shellcorona.cpp:1324 #6 0x56315299ecc3 in ShellCorona::load (this=0x563154b2c860) at ./shell/shellcorona.cpp:766 #7 0x7f40eed696d7 in QtPrivate::QSlotObjectBase::call (a=0x7ffd0703aaa0,
[Breeze] [Bug 421382] Add more kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Summary|Missing kmymoney icons |Add more kmymoney icons CC||n...@kde.org Status|REPORTED|CONFIRMED Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 --- Comment #6 from Dawid Wróbel --- A -copy action for each of the below would also be nice, e.g. actions-account-copy, actions-transaction-copy, etc. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #4 from Tyler Brown --- I am able to reproduce this with a new default layout. I'm also not seeing anything weird when I toggle the setting when launching Latte Dock from the terminal with the debug flag. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #3 from Tyler Brown --- Created attachment 128558 --> https://bugs.kde.org/attachment.cgi?id=128558=edit Layout File My current layout file as if this moment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421699] New: System Settings crashed when attempting to open YaST
https://bugs.kde.org/show_bug.cgi?id=421699 Bug ID: 421699 Summary: System Settings crashed when attempting to open YaST Product: systemsettings Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rnjohnso...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.5) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.12-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Just trying out openSUSE Tumbleweed as of May 17, 2020. Everything is up to date. When trying to open YaST on a fresh install from the icon in System Settings, there's a crash. So far I have been able to reproduce this every time. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdf2e947f00 (LWP 80249))] Thread 3 (Thread 0x7fdf27984700 (LWP 80252)): #0 0x7fdf312844fc in read () from /lib64/libc.so.6 #1 0x7fdf2f47f37f in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fdf2f437537 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fdf2f437982 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7fdf2f437aff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fdf31831beb in QEventDispatcherGlib::processEvents (this=0x7fdf2b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7fdf317d9b7b in QEventLoop::exec (this=this@entry=0x7fdf27983d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #7 0x7fdf316045ce in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #8 0x7fdf30529507 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7fdf31605698 in QThreadPrivate::start (arg=0x7fdf305abda0) at thread/qthread_unix.cpp:342 #10 0x7fdf2fe37efa in start_thread () from /lib64/libpthread.so.0 #11 0x7fdf312933bf in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fdf2c840700 (LWP 80251)): #0 0x7fdf31288acf in poll () from /lib64/libc.so.6 #1 0x7fdf2fe07772 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fdf2fe0843a in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fdf2ca4aab0 in QXcbEventQueue::run (this=0x55e937c7fc30) at qxcbeventqueue.cpp:228 #4 0x7fdf31605698 in QThreadPrivate::start (arg=0x55e937c7fc30) at thread/qthread_unix.cpp:342 #5 0x7fdf2fe37efa in start_thread () from /lib64/libpthread.so.0 #6 0x7fdf312933bf in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fdf2e947f00 (LWP 80249)): [KCrash Handler] #4 0x7fdf311cfea1 in raise () from /lib64/libc.so.6 #5 0x7fdf311b953d in abort () from /lib64/libc.so.6 #6 0x7fdf315ccaef in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1894 #7 QMessageLogger::fatal (this=this@entry=0x7ffc40545490, msg=msg@entry=0x7fdf32a28880 "Accessed invalid KPluginInfo object") at global/qlogging.cpp:893 #8 0x7fdf329d60db in KPluginInfo::setPluginEnabled (enabled=, this=) at /usr/include/qt5/QtCore/qlogging.h:90 #9 0x7fdf329d60f3 in KPluginInfo::service (this=) at /usr/include/qt5/QtCore/qlogging.h:90 #10 0x7fdf32dc16d5 in KCModuleInfo::service (this=this@entry=0x55e937f6e268) at /usr/src/debug/kcmutils-5.70.0-1.1.x86_64/src/kcmoduleinfo.cpp:165 #11 0x7fdf32de420f in ModuleView::addModule (this=this@entry=0x55e937fc01e0, module=0x55e937f6e268) at /usr/src/debug/systemsettings5-5.18.5-1.1.x86_64/core/ModuleView.cpp:160 #12 0x7fdf32de625d in ModuleView::loadModule (menuItem=..., this=0x55e937fc01e0) at /usr/src/debug/systemsettings5-5.18.5-1.1.x86_64/core/ModuleView.cpp:150 #13 ModuleView::loadModule (this=0x55e937fc01e0, menuItem=...) at /usr/src/debug/systemsettings5-5.18.5-1.1.x86_64/core/ModuleView.cpp:134 #14 0x7fdf3180f9de in QtPrivate::QSlotObjectBase::call (a=0x7ffc40545720, r=0x55e937fc0940, this=0x55e938147810) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394 #15 doActivate (sender=0x55e9380c6cf0, signal_index=10, argv=0x7ffc40545720) at kernel/qobject.cpp:3870 #16 0x7fdf3180a19f in QMetaObject::activate (sender=sender@entry=0x55e9380c6cf0, m=m@entry=0x7fdf32805c40 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc40545720) at kernel/qobject.cpp:3930 #17 0x7fdf3254b955 in QAbstractItemView::activated (this=this@entry=0x55e9380c6cf0, _t1=...) at .moc/moc_qabstractitemview.cpp:668 #18 0x7fdf3254fb15 in QAbstractItemView::mouseReleaseEvent (this=0x55e9380c6cf0, event=) at itemviews/qabstractitemview.cpp:1940 #19 0x7fdf3259655f in
[okular] [Bug 421670] Okular hangs when printing pages specified in "Print range -> Pages"
https://bugs.kde.org/show_bug.cgi?id=421670 --- Comment #3 from Jeremy Lorelli --- Thanks for the replies :) I just tested it and, yes, it does max out CPU usage and eventually adds the job to the print queue after about 15 minutes. Wasn't able to get it to actually print, but that might just be an issue with my printer. When testing a small document (~30 pages), I was able to print individual pages using the "Pages: " input. When using the "print to pdf" option though, the entire PDF is saved. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 409670] Color space information {primaries:INVALID, transfer:INVALID, matrix:INVALID, range:INVALID}
https://bugs.kde.org/show_bug.cgi?id=409670 --- Comment #2 from prote...@hotmail.it --- It seems to have been fixed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 Dawid Wróbel changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Dawid Wróbel --- These are the unique icons KMyMoney uses for its own purposes: actions-account actions-account-add actions-account-close actions-account-delete actions-account-edit actions-account-open actions-account-reopen actions-account-types-asset actions-account-types-cash actions-account-types-checking actions-account-types-closed actions-account-types-credit-card actions-account-types-expense actions-account-types-income actions-account-types-investments actions-account-types-liability actions-account-types-loan actions-account-types-reconciled actions-account-types-savings actions-account-update-online actions-account-update-online-all actions-accounts actions-attention actions-backup actions-bank actions-budget actions-budget-add actions-budget-delete actions-budget-edit actions-categories actions-category-delete actions-category-edit actions-cleared actions-close-window actions-delete actions-forecast actions-hide-categories actions-hide-reconciled actions-home actions-institution actions-institution-add actions-institution-delete actions-institution-edit actions-institutions actions-investment actions-investment-add actions-investment-delete actions-investment-edit actions-investment-update-online actions-investment-update-online-all actions-investments actions-ledger actions-office-chart-tall-pie actions-online-banking actions-onlinebanking actions-pay-edit actions-payee actions-payee-rename actions-personal-data actions-reconcile actions-reconcile-finish actions-report actions-report-bar actions-report-line actions-report-pie actions-report-solid actions-report-text actions-schedule actions-set-as actions-transaction actions-transaction-add actions-transaction-delete actions-transaction-edit actions-transaction-export actions-transaction-find actions-transaction-import actions-transaction-report actions-transaction-split actions-unreconciled actions-update-prices actions-view-info Additionally, a refreshed KMyMoney icon would be great. Some effort was already made in the past: https://forum.kde.org/viewtopic.php?f=285=119635 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #2 from Michail Vourlakos --- Send also your Latte layout file in case something is broken in it. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Michail Vourlakos --- You need to find more information, it works just fine in my Latte git version -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421601] Crash after clicking on Network
https://bugs.kde.org/show_bug.cgi?id=421601 Elvis Angelaccio changed: What|Removed |Added Summary|What I was doing when the |Crash after clicking on |application crashed:|Network CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421642] [Wayland] Screen edges not blocked when playing StarCraft 2 (over Wine)
https://bugs.kde.org/show_bug.cgi?id=421642 --- Comment #2 from Alexander Potashev --- Sorry, installing a new version of kwin would be too complicated for me. I can re-test after update to Fedora 32 or a newer release, which is currently blocked because Fedora 32 doesn't ship Python2 which https://cgit.kde.org/pology.git depends on. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421554] Dolphin crashes when new file / folder is created with an underscore in the name
https://bugs.kde.org/show_bug.cgi?id=421554 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||elvis.angelac...@kde.org --- Comment #3 from Elvis Angelaccio --- If that locale is broken there is nothing we can do from the dolphin side. I think we can close this. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 421158] Add support for browsing RAR archives
https://bugs.kde.org/show_bug.cgi?id=421158 Elvis Angelaccio changed: What|Removed |Added Product|dolphin |kio-extras Version|20.04.0 |20.04 CC||elvis.angelac...@kde.org Assignee|dolphin-bugs-n...@kde.org |plasma-b...@kde.org Component|general |Archive -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 --- Comment #12 from andydecle...@gmail.com --- (In reply to Elvis Angelaccio from comment #11) > You can just right-click the location bar and choose "Text Completion -> > Dropdown List", btw. When I right-click the location bar, the only choices I get are: - Copy - Paste - Edit - Navigate - Show Full Path . . . Oh, first get the location bar into editable mode, then do that. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 417969] Inability to deterministically choose when an icon should be monochrome and when it should be colorful
https://bugs.kde.org/show_bug.cgi?id=417969 Nate Graham changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 421698] New: Error running in raspberry pi 3B
https://bugs.kde.org/show_bug.cgi?id=421698 Bug ID: 421698 Summary: Error running in raspberry pi 3B Product: gcompris Version: unspecified Platform: Other OS: other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: bruno.coud...@gcompris.net Reporter: helloth...@gmail.com Target Milestone: --- SUMMARY After downloading and installing as per the instructions for raspberry pi download page. The program is not responding when executing. The error is: error while loading shared libraries:libpulse-mainloop-glib.so.0: cannot open shared object file: No such file or directory. STEPS TO REPRODUCE 1. Download gcompris-qt-0.97-Raspberry.sh 2. chmod u+x gcompris-qt-0.97-Raspberry.sh 3. ./gcompris-qt-0.97-Raspberry.sh OBSERVED RESULT The application did not open EXPECTED RESULT Opening the application SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Raspberry pi 3B -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 420695] Dolphin crashes when closing terminal via "Close Session"
https://bugs.kde.org/show_bug.cgi?id=420695 --- Comment #12 from Elvis Angelaccio --- Tried again with 5603e1252251a23bca0f2cc48b9310d9bdfdfee7 applied, still crashes :( -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 --- Comment #11 from Elvis Angelaccio --- (In reply to andydecleyre from comment #8) > this can be fixed by adding: > > UrlCompletionMode=5 > > to the General section of ~/.config/dolphinrc > You can just right-click the location bar and choose "Text Completion -> Dropdown List", btw. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421693] Digikam only read xmp:Label during first import then prioritizes its digiKam:ColorLabel over the xmp:Label.
https://bugs.kde.org/show_bug.cgi?id=421693 --- Comment #1 from e...@airmail.cc --- exiftool -r -digiKam:ColorLabel= This fixes the problem, of course. Quit Digikam, run that command (basically remove the digikam:ColorLabel from xmp) and then reopen Digikam, xmp:Label is read again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421696] Hard disk activity: duplicated sensors appear in the list
https://bugs.kde.org/show_bug.cgi?id=421696 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #2 from David Edmundson --- edit, nm. Reproduced then it was clearly what you meant -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421696] Hard disk activity: duplicated sensors appear in the list
https://bugs.kde.org/show_bug.cgi?id=421696 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- >Adding a new sensors representing the I/O of all disks causes the "All >Sensors" list to grow two new "Disk Write Access" and "Disk Read Access" upon >clicking "Apply". The new sensor name disappears as well, although the entry >stays I don't understand, can you include a screenshot? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] New: Widget disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 Bug ID: 421697 Summary: Widget disappears when scrolling is enabled. Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: ty...@condoulo.com Target Milestone: --- Created attachment 128557 --> https://bugs.kde.org/attachment.cgi?id=128557=edit Desktop with application open not showing in Tasks. SUMMARY STEPS TO REPRODUCE 1. Go into the Tasks Tab of Settings 2. Enable Scrolling 3. OBSERVED RESULT Tasks disappear EXPECTED RESULT Scrolling should be enabled SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 KDE / 5.6.11-300.fc32.x86_64 (available in About System) KDE Plasma Version: Plasma 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Latte Dock: Latest Git build as of 2020-05-17 16:29 CDT. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 Tyler Brown changed: What|Removed |Added Summary|Widget disappears when |Tasks disappears when |scrolling is enabled. |scrolling is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421696] New: Hard disk activity: duplicated sensors appear in the list
https://bugs.kde.org/show_bug.cgi?id=421696 Bug ID: 421696 Summary: Hard disk activity: duplicated sensors appear in the list Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Adding a new sensors representing the I/O of all disks causes the "All Sensors" list to grow two new "Disk Write Access" and "Disk Read Access" upon clicking "Apply". The new sensor name disappears as well, although the entry stays. STEPS TO REPRODUCE 1. Add a hard disk activity widget 2. Go to preferences > Sensors Details 3. Select "partitions" > All > select a sensor and add it 4. Click Apply OBSERVED RESULT Two new pair of sensors appear in the list and the newly-added sensor in "Chart Sensors" loses its name (replaced by a blank string) EXPECTED RESULT Sensor is added correctly and the list of available sensor stay the same. SOFTWARE/OS VERSIONS Plasma from git master, KF5 from git master, Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421695] New: Network speed widget: preferences checkbox "Show sensors legend" does not show checked state
https://bugs.kde.org/show_bug.cgi?id=421695 Bug ID: 421695 Summary: Network speed widget: preferences checkbox "Show sensors legend" does not show checked state Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The checkbox "Show sensors legend" in applet configuration stays forever in checked state, at least visually. Note that clicking on it, even though does not cause visual feedback, does switch the feature on/off. STEPS TO REPRODUCE 1. Add Network speed widget 2. Enter applet preferences 3. Click on "show sensors legend" OBSERVED RESULT Checkbox remains checked, although the corresponding functionality is enabled / disabled. EXPECTED RESULT Checkbox should change visual state (toggled / untoggled and vice versa) SOFTWARE/OS VERSIONS Plasma from git master, KF5 from git master, Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421694] Network speed widget: Upload/download labels overlap with speed
https://bugs.kde.org/show_bug.cgi?id=421694 --- Comment #1 from Luca Beltrame --- Created attachment 128556 --> https://bugs.kde.org/attachment.cgi?id=128556=edit Screenshot of labels overlapping -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421694] New: Network speed widget: Upload/download labels overlap with speed
https://bugs.kde.org/show_bug.cgi?id=421694 Bug ID: 421694 Summary: Network speed widget: Upload/download labels overlap with speed Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: lbeltr...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY As the title says, the upload/download speed labels in the sensors legend are overlapping with the speed. Screenshot attached. STEPS TO REPRODUCE 1. Add a network speed widget 2. Add the sensors legend 3. Enlarge the widget enough that labels are shown OBSERVED RESULT Labels overlapping (see screenshot) EXPECTED RESULT Labels are not overlapping SOFTWARE/OS VERSIONS Plasma git master, KF5 git master, Qt 5.15 RC. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421693] Digikam only read xmp:Label during first import then prioritizes its digiKam:ColorLabel over the xmp:Label.
https://bugs.kde.org/show_bug.cgi?id=421693 e...@airmail.cc changed: What|Removed |Added Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421693] New: Digikam only read xmp:Label during first import then prioritizes its digiKam:ColorLabel over the xmp:Label.
https://bugs.kde.org/show_bug.cgi?id=421693 Bug ID: 421693 Summary: Digikam only read xmp:Label during first import then prioritizes its digiKam:ColorLabel over the xmp:Label. Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Xmp Assignee: digikam-bugs-n...@kde.org Reporter: e...@airmail.cc Target Milestone: --- Created attachment 128555 --> https://bugs.kde.org/attachment.cgi?id=128555=edit Metadata Section Digikam SUMMARY STEPS TO REPRODUCE 1. Import some pictures with color label Red applied in xmp:Label 2. Change color label in Digikam to Blue that will write xmp:Label: Blue in xmp 3. Open picture in Capture one that will read that xmp:Label Blue correctly and change the color label again to Green and it will write xmp:Label: Green 4. Open picture again in Digikam. OBSERVED RESULT Digikam won't pick up that last change of color label in Capture One or any program that writes xmp:Label. EXPECTED RESULT Digikam should read that label again just in case was changed in another program. The thing is that Digikam in the metadata section the xmp:Label reads correctly but Digikam (I guess) prioritize its digiKam:ColorLabel over the xmp:Label. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION On the screenshot we can see that Basic Scheme reads Label Blue and Digikam Scheme reads Label 6 (which is purple if I'm not mistaken) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421634] Presentation mode misrendering with two monitors and screen scaling
https://bugs.kde.org/show_bug.cgi?id=421634 --- Comment #1 from David Hurka --- QWidget, being a QPaintDevice, returns its size in Device Independent Pixels. That is the actual size / scaling factor. The intention is to let QPainter operations operate with the same Device Independent Pixels on any QPaintDevice, and QWidget will render painting operations in the correct display resolution. Considering that, returning 1280x720 as the widget size is correct. Sorry, this is for sure not the information you are looking for, and you probably already know that. Specifically, I can’t tell why the widget returns different sizes, and don’t know the painting code of the presentation widget. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421109] Dolphin chrashed
https://bugs.kde.org/show_bug.cgi?id=421109 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO CC||elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- If you can reproduce the crash, please install debug symbols for dolphin and then post another stacktrace. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404959] Icon sizes and type inconsistency
https://bugs.kde.org/show_bug.cgi?id=404959 Noah Davis changed: What|Removed |Added CC||noaha...@gmail.com --- Comment #3 from Noah Davis --- I don't think this is actually a duplicate of bug 417969. It would only be a duplicate if the problem was with Breeze. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 421052] Cannot copy folder to NTFS partition
https://bugs.kde.org/show_bug.cgi?id=421052 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org, ||kdelibs-b...@kde.org Component|general |general Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org Version|20.04.0 |5.69.0 Product|dolphin |frameworks-kio -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 406640] Graph not displaying correctly with coreboot
https://bugs.kde.org/show_bug.cgi?id=406640 petrk changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from petrk --- Since coreboot changed some specs reported to system, it screwed with graphs. Clearing upower stats associated with affected battery and rebooting fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421692] plasma global scale shows artifacts in konsole
https://bugs.kde.org/show_bug.cgi?id=421692 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Edmundson --- It's konsole which needs fixing, not plasmashell (there's a bug report there, if you search konsole you should find it) -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 417026] Battery monitor in system tray with missing translation
https://bugs.kde.org/show_bug.cgi?id=417026 --- Comment #11 from Frederik Schwarzer --- Hatte übersehen, dass von dem Applet noch eine andere Anwendung gestartet wird. In dieser ist nun die übersetzung auch vollständig. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 417026] Battery monitor in system tray with missing translation
https://bugs.kde.org/show_bug.cgi?id=417026 --- Comment #10 from Unknown --- SVN commit 1569721 by schwarzer: translation update & fixes M +8 -8 kcm_energyinfo.po WebSVN link: http://websvn.kde.org/?view=rev=1569721 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 417026] Battery monitor in system tray with missing translation
https://bugs.kde.org/show_bug.cgi?id=417026 Unknown changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Unknown --- SVN commit 1569720 by schwarzer: translation update & fixes M +8 -8 kcm_energyinfo.po WebSVN link: http://websvn.kde.org/?view=rev=1569720 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421689] FTP bug that has never changed, applies to all Linux platforms, stale icon selection status
https://bugs.kde.org/show_bug.cgi?id=421689 --- Comment #1 from Charl --- What I mean by "the old icons remain selected" is: the older(er) ones of the operations completed before the very last (freshest). These never update to show only the last icons related to your last operation. I understand this is a feature: to highlight icons in bulk/batch operations; however, it keeps icons selected in the entire history of what you're doing, unless you click in the blank area. It could help to only highlight (select) icons of files/folders that where done in the last "job", and if job history is important (hidden feature i may be unaware of) -then underline those - unless clicked in the blank area of course. I hope this clears things up a bit. Many thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386253] Impossible to set Alt+Print shortcut
https://bugs.kde.org/show_bug.cgi?id=386253 ariasuni changed: What|Removed |Added Version|5.17.90 |5.18.90 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 421691] New: New Account Wizard is not asking if the user wants to add a new payee
https://bugs.kde.org/show_bug.cgi?id=421691 Bug ID: 421691 Summary: New Account Wizard is not asking if the user wants to add a new payee Product: kmymoney Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: dev.rszczes...@gmail.com Target Milestone: --- Created attachment 128554 --> https://bugs.kde.org/attachment.cgi?id=128554=edit Expected result when focusing out of the Payee text box SUMMARY When the user enters a new payee name in the New Account Wizard and then changes focus to another form field by clicking the mouse, the user is not asked if he or she wants to add the new payee. The pop-up question window appears correctly if focus is changed by keyboard (e.g. by pressing the Tab key). STEPS TO REPRODUCE 1. Go to the Accounts view and click the "New Account..." button. 2. Follow the instructions in the Wizard. From the Account type drop-down list select "Credit Card". 3. On the Schedule page enter a new payee name. 4. Click your left mouse button to change focus to another form field. OBSERVED RESULT The new payee name is kept in the Payee text box but the user is not asked about adding the new payee. The Next button remains disabled even if all the required fields are filled. EXPECTED RESULT "New payee/receiver" pop-up window should appear exactly like it does when the Tab key is pressed after providing a new payee name. After adding the new payee and filling all the required fields on the form, the Next button should be enabled. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Please find attached a screenshot presenting expected result. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421692] New: plasma global scale shows artifacts in konsole
https://bugs.kde.org/show_bug.cgi?id=421692 Bug ID: 421692 Summary: plasma global scale shows artifacts in konsole Product: plasmashell Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: slartibar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I was just trying to play with the systemsettings5 > display configuration > global scale parameter. Initially, it seems to work nicely (in comparison to my current method, using font dpi modifications) BUT If you start konsole, you get - depending on your cursor position - single pixel black lines across the konsole window. (sometimes only line fragments and many pixels instead of a line) My konsole config: - black font on white background, dejaVu sans mono 9pt, smooth fonts, draw intense colors in bold I didn't try other fonts though, but this is still very annoying for this scaling feature and does never happen by just manipulating the font dpi. Any suggestions? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #25 from slartibar...@gmail.com --- i did another test on the machine showing the error: upgrade to fedora32 (without zawertun copr repo) reboot, all is fine, instant plasma load after login enabling zawertun repo dnf upgrade --refresh login into plasma there you got the error again. The way back is a bit more complicated: dnf downgrade kf5\* ... test again, error still there, so get back even further: that is, downgrade all individual programs of the zawertun repo (something like: dnf list installed | grep zawertun | cut -d " " -f1 > zawertun then create a nice 'dnf downgrade ' job out of the files contents So, what i have learned is: - the upgrade of the plasma apps from 19.12.3 to 20.04.0 seem to be the problem? Any help is appreciated -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 421690] New: Reset window layout to default
https://bugs.kde.org/show_bug.cgi?id=421690 Bug ID: 421690 Summary: Reset window layout to default Product: ksysguard Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: trufano...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- I'm missing the option in context menu that allows to reset the window layout (columns in table and their order) to its defaults with a single click. Just faced with problem when ksgrd_network_kelper eats 25% (whole core) of CPU and was trying to hide all Download/Upload columns. And didn't noticed that I had 2 copies of each in the end of table bcs before them I placed Command column which is very wide. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 397953] KIO::highlightInFileManager does not respect default file manager setting when launched via FileManager1 DBus activation
https://bugs.kde.org/show_bug.cgi?id=397953 Till Schäfer changed: What|Removed |Added Version|5.66.0 |5.70.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421687] Color change shortcuts glitch when changing hue or making it darker and lighter
https://bugs.kde.org/show_bug.cgi?id=421687 --- Comment #4 from Sonia --- Created attachment 128553 --> https://bugs.kde.org/attachment.cgi?id=128553=edit color hue change glitch -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421687] Color change shortcuts glitch when changing hue or making it darker and lighter
https://bugs.kde.org/show_bug.cgi?id=421687 --- Comment #3 from Sonia --- Comment on attachment 128552 --> https://bugs.kde.org/attachment.cgi?id=128552 Another recorded change for color change glitch Sorry this one did not record properly, uploading a new one -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421687] Color change shortcuts glitch when changing hue or making it darker and lighter
https://bugs.kde.org/show_bug.cgi?id=421687 --- Comment #2 from Sonia --- Created attachment 128552 --> https://bugs.kde.org/attachment.cgi?id=128552=edit Another recorded change for color change glitch -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421687] Color change shortcuts glitch when changing hue or making it darker and lighter
https://bugs.kde.org/show_bug.cgi?id=421687 --- Comment #1 from Sonia --- Created attachment 128551 --> https://bugs.kde.org/attachment.cgi?id=128551=edit recorded glitch for color change -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421689] New: FTP bug that has never changed, applies to all Linux platforms, stale icon selection status
https://bugs.kde.org/show_bug.cgi?id=421689 Bug ID: 421689 Summary: FTP bug that has never changed, applies to all Linux platforms, stale icon selection status Product: dolphin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: charl.xa...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 128550 --> https://bugs.kde.org/attachment.cgi?id=128550=edit screenshot of how an old folder shows as selected after copying a file into the main FTP view When using Dolphin to FTP files, the last icon that was selected/copied/moved remains selected. This has the undesired effect of assuming a file would be dropped inside the active (selected) directory, where in fact all is fine; however, I find myself often clicking in the blank area -just to make sure. Often there would be multiple selected (stale status) items in the FTP view. I have often mistakenly assumed selections and made mistakes during split-view operations while working and this causes issues. This is NOT only in split-view though, but this is where one could make dangerous assumptions when working long hours. STEPS TO REPRODUCE 1. open Dolphin in split-view 2. open an FTP location on either side 3. select a folder in FTP side, or drag+drop one into it from local disk 4. drag+drop another item from any other place into FTP view 5. see how the old selected icons remain focused in the FTP view OBSERVED RESULT Old selections remain focused in FTP view when copying/moving EXPECTED RESULT Only the last copied/moved item(s) should be focused (selected) after such action(s) completed. Operating System: openSUSE Tumbleweed 20200511 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.1 Kernel Version: 5.6.11-1-default OS Type: 64-bit Processors: 4 × Intel® Core™ i3-6006U CPU @ 2.00GHz Memory: 7.2 GiB of RAM ADDITIONAL INFORMATION KDE is amazing guys; I've been converting all my friends and family to Linx+KDE since 2010 and everybody is very happy about it, thanks to you; please keep up the good work. I'm a fullstack software engineer and KDE inspires me with every update. Thank you also for KDE-connect, awesome tool. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421688] New: Fedora 31 LInux KDE Plasma 5.17.5 Keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=421688 Bug ID: 421688 Summary: Fedora 31 LInux KDE Plasma 5.17.5 Keeps crashing on every login Product: kwin Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: misha.shcheti...@gmail.com Target Milestone: --- Application: kwin_x11 (5.17.5) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.11-200.fc31.x86_64 x86_64 Distribution: "Fedora release 31 (Thirty One)" -- Information about the crash: - What I was doing when the application crashed: Hello, I've just started the new session of my user, and inform message about Kwin crash appeared. It was tihrd time in a row. So the user expiriece could be described as follow: - Given user turn on the pc - And enters his credentials on the login screen - Then user is able to see the KDE loading progress bar - Then user is able to see the main panel - Then message about crash appeared The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb8165eb200 (LWP 2878))] Thread 5 (Thread 0x7fb7f1226700 (LWP 3083)): #0 0x7fb81b453d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb81b9d474a in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7fb81b9d476f in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7fb81b44d4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb81d5b16a3 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fb7f32ed700 (LWP 3031)): #0 0x7fb81b453d45 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fb7f37db19b in util_queue_thread_func () from /usr/lib64/dri/i965_dri.so #2 0x7fb7f37dadab in impl_thrd_routine () from /usr/lib64/dri/i965_dri.so #3 0x7fb81b44d4e2 in start_thread () from /lib64/libpthread.so.0 #4 0x7fb81d5b16a3 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fb801de8700 (LWP 3013)): #0 0x7fb81d5a6b36 in ppoll () from /lib64/libc.so.6 #1 0x7fb81c0e6d19 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7fb81c0e7f61 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7fb81c09423b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fb81bee4cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7fb81ab7e399 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #6 0x7fb81bee5e26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fb81b44d4e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb81d5b16a3 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fb803fff700 (LWP 2933)): #0 0x7fb81d5a6b36 in ppoll () from /lib64/libc.so.6 #1 0x7fb81c0e6d19 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7fb81c0e7f61 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7fb81c09423b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fb81bee4cd5 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7fb81a4d7f6a in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #6 0x7fb81bee5e26 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fb81b44d4e2 in start_thread () from /lib64/libpthread.so.0 #8 0x7fb81d5b16a3 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fb8165eb200 (LWP 2878)): [KCrash Handler] #6 0x55bd74516650 in ?? () #7 0x7fb81bb4b127 in KWin::DimInactiveEffect::canDimWindow(KWin::EffectWindow const*) const () from /lib64/libkwin4_effect_builtins.so.1 #8 0x7fb81bb4bf65 in KWin::DimInactiveEffect::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () from /lib64/libkwin4_effect_builtins.so.1 #9 0x7fb81d2a2b57 in KWin::EffectsHandlerImpl::paintWindow(KWin::EffectWindow*, int, QRegion, KWin::WindowPaintData&) () from /lib64/libkwin.so.5 #10 0x7fb81d341f06 in KWin::Scene::paintWindow(KWin::Scene::Window*, int, QRegion, KWin::WindowQuadList) () from /lib64/libkwin.so.5 #11 0x7fb81d33e8c5 in KWin::Scene::paintSimpleScreen(int, QRegion) () from /lib64/libkwin.so.5 #12 0x7fb8081814e7 in KWin::SceneOpenGL2::paintSimpleScreen(int, QRegion) () from /usr/lib64/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #13 0x7fb81d3414e0 in KWin::Scene::finalPaintScreen(int, QRegion, KWin::ScreenPaintData&) () from /lib64/libkwin.so.5 #14 0x7fb81d2a2902 in
