[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 --- Comment #23 from Maik Qualmann --- Git commit cf8aa4a0a9475b0e9ea35ebeda421303c6a783f0 by Maik Qualmann. Committed on 06/05/2020 at 05:50. Pushed by mqualmann into branch 'master'. revert all unicode changes at Exiv2 M +1-6core/libs/metadataengine/engine/metaengine_comments.cpp M +1-6core/libs/metadataengine/engine/metaengine_exif.cpp M +2-12 core/libs/metadataengine/engine/metaengine_fileio.cpp M +1-6core/libs/metadataengine/engine/metaengine_iptc.cpp M +2-12 core/libs/metadataengine/engine/metaengine_p.cpp M +1-6core/libs/metadataengine/engine/metaengine_previews.cpp M +1-6core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/cf8aa4a0a9475b0e9ea35ebeda421303c6a783f0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420600] Krita 4.3.0 Preserve Alpha Colorsmudge Opacity Affected by Smudge Length
https://bugs.kde.org/show_bug.cgi?id=420600 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 419966] Latte is super unresponsive and slow
https://bugs.kde.org/show_bug.cgi?id=419966 --- 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.
[lattedock] [Bug 415341] Latte dock crash when logging out on dual display in Kubuntu
https://bugs.kde.org/show_bug.cgi?id=415341 --- 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.
[Powerdevil] [Bug 414440] Brightness gets maximized after screen times out.
https://bugs.kde.org/show_bug.cgi?id=414440 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 418488] Can't open menu after add new monitor
https://bugs.kde.org/show_bug.cgi?id=418488 --- 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.
[lattedock] [Bug 415109] Latte Dock crash when opening settings
https://bugs.kde.org/show_bug.cgi?id=415109 --- 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.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #24 from Brian Wright --- Also - the windows did not open for Skype, Slack, and KeepassXC on both system startup and logout/login. They were effectively running in the background. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #23 from Brian Wright --- Started system - all plasma icons appeared in the system tray. Autostarted, running, but missing from the system tray: Keepassxc slack skypeforlinux dropbox hp-systray Ran listIcons.sh :1.31/StatusNotifierItem Discover Notifier_org.kde.DiscoverNotifier Updates :1.38/StatusNotifierItem KOrganizer Reminder Daemon KOrganizer Reminder Daemon :1.40/org/ayatana/NotificationItem/pasystray pasystray pasystray :1.56/StatusNotifierItem KMix Volume Control :1.76/StatusNotifierItem KAlarm KAlarm Stopped and restarted xembedsniproxy - no change listIcon.sh output: :1.31/StatusNotifierItem Discover Notifier_org.kde.DiscoverNotifier Updates :1.38/StatusNotifierItem KOrganizer Reminder Daemon KOrganizer Reminder Daemon :1.40/org/ayatana/NotificationItem/pasystray pasystray pasystray :1.56/StatusNotifierItem KMix Volume Control :1.76/StatusNotifierItem KAlarm KAlarm Logged out, then logged back in. No change, as seen by listIcons.sh :1.198/org/ayatana/NotificationItem/pasystray pasystray pasystray :1.191/StatusNotifierItem Discover Notifier_org.kde.DiscoverNotifier Updates :1.195/StatusNotifierItem KOrganizer Reminder Daemon KOrganizer Reminder Daemon :1.208/StatusNotifierItem KMix Volume Control :1.226/StatusNotifierItem KAlarm KAlarm I'll test with my virtualbox system, and another test user account on my local machine, unless there's something else that you'd like me to run. I'm suspecting that non-plasma apps are not being picked up by the SNI when the system starts? -- 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 #23 from Musikolo --- Yes, I can confirm the same thing. After updating to the latest packages in ArchLinux, it's working fine now! I saw new version of plasma-desktop (from 5.18.4.1-2 to 5.18.5-1) which contains plasmashell. This is the only relevant thing I found that could have any relationship with previous bug. Thank you all! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398440] plasmashell crashes on wayland when dragging a file from dolphin over a panel
https://bugs.kde.org/show_bug.cgi?id=398440 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knotifications] [Bug 409268] Notifications don't auto hide after update.
https://bugs.kde.org/show_bug.cgi?id=409268 Iiari changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||bre...@yahoo.com Ever confirmed|0 |1 --- Comment #8 from Iiari --- Someone just let me know about this bug on Reddit, as I have had this same phenomenon with Pushbullet notifications sent from Chrome on Manjaro. All other Chrome notifications seem to time out appropriately, but not those being generated by the Pushbullet extention within Chrome, which require manual dismissal to remove. So that might help narrow down the problem to reproduce it and track the issue. Also, in retrospect, the PIA notification mentioned above has the same problem as well. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417488] Broken fonts and fuzzy theme previews in multiple system settings
https://bugs.kde.org/show_bug.cgi?id=417488 joe changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||kgavion...@gmail.com --- Comment #26 from joe --- Bug disappeared on version Plasma 5.18.5, even though i don't see anything related in the change log. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 421095] New: KDE Crashing when attempting to exit
https://bugs.kde.org/show_bug.cgi?id=421095 Bug ID: 421095 Summary: KDE Crashing when attempting to exit Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: linuxu...@neo.rr.com Target Milestone: --- Application: kontact (5.13.3 (19.12.3)) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-29-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04 LTS -- Information about the crash: - What I was doing when the application crashed: I was attempting to close out the software. I was also installing software via the Discover app while doing this. Firefox was also open and in the background - Unusual behavior I noticed: I've noticed that hitting the "x" in the upper right does NOT close out the software. I have to manually select "File/Quit" (or hold down Ctrl-Q) to get the software to close. The "x" doesn't appear to do anything? It does not minimize or in any way dismiss the window. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9971250f00 (LWP 47912))] Thread 24 (Thread 0x7f99527fc700 (LWP 50912)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f99527fb4a0, clockid=, expected=0, futex_word=0x7f99527fb5e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f99527fb4a0, clockid=, mutex=0x7f99527fb598, cond=0x7f99527fb5c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f99527fb5c0, mutex=0x7f99527fb598, abstime=0x7f99527fb4a0) at pthread_cond_wait.c:656 #3 0x7f997dc7fb2e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f997dc8051f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f997dc80615 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f997dc41da6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f997dc44c48 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f997dc44ef8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f997dc82b63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f99836dc609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f99846f1103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f98cbfff700 (LWP 50900)): #0 0x7f996c2b7934 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #1 0x7f996c339416 in pa_mainloop_prepare () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f996c339eb4 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f996c339f70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f996c34811d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f996c2e657c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #6 0x7f99836dc609 in start_thread (arg=) at pthread_create.c:477 #7 0x7f99846f1103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 22 (Thread 0x7f992dffb700 (LWP 50613)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7f992dffa4a0, clockid=, expected=0, futex_word=0x7f992dffa5e8) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7f992dffa4a0, clockid=, mutex=0x7f992dffa598, cond=0x7f992dffa5c0) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7f992dffa5c0, mutex=0x7f992dffa598, abstime=0x7f992dffa4a0) at pthread_cond_wait.c:656 #3 0x7f997dc7fb2e in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f997dc8051f in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f997dc80615 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f997dc41da6 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f997dc44c48 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #8 0x7f997dc44ef8 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #9 0x7f997dc82b63 in ?? () from /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #10 0x7f99836dc609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f99846f1103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f98d5911700 (LWP 49119)): #0 __GI___errno_location () at errno-loc.c:25 #1 0x7f9982d441b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9982d442e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9984c9d583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f9984c444db in
[kdenlive] [Bug 421094] Motion Tracker Effect Missing
https://bugs.kde.org/show_bug.cgi?id=421094 Ahmed changed: What|Removed |Added CC||code.compile.l...@gmail.com Version|unspecified |20.04.0 Keywords||reproducible -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421094] New: Motion Tracker Effect Missing
https://bugs.kde.org/show_bug.cgi?id=421094 Bug ID: 421094 Summary: Motion Tracker Effect Missing Product: kdenlive Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: code.compile.l...@gmail.com Target Milestone: --- SUMMARY On Ubuntu 20.04 LTS. Motion tracker effect as announced in the release of kdenlive 20.04 is missing when kdenlive is installed from apt - PPA repository. STEPS TO REPRODUCE 1. Ubuntu 20.04 64 bit 2. Follow the page https://launchpad.net/~kdenlive/+archive/ubuntu/kdenlive-stable 3: open terminal and perform sudo add-apt-repository ppa:kdenlive/kdenlive-stable sudo apt-get update sudo apt-get install kdenlive version 20.04.0 will be installed 4: open kdenlive and click effects panel, search for motion tracker, no effect found OBSERVED RESULT Motion tracker effect is missing EXPECTED RESULT Motion tracker effect should be present as advertised in the release of version 20.04 SOFTWARE/OS VERSIONS Ubuntu 20.04 LTS 64 bit GNOME version 3.36.1 Windowing system X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421079] Array is used before checking index
https://bugs.kde.org/show_bug.cgi?id=421079 Tymond changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/10d47bd625663e ||d576ccc527f3219e8aa133995f Status|REPORTED|RESOLVED --- Comment #1 from Tymond --- Git commit 10d47bd625663ed576ccc527f3219e8aa133995f by Agata Cacko. Committed on 06/05/2020 at 00:44. Pushed by tymond into branch 'master'. Change order in conditions in while() in KoZoomAction Before this commit, while loop would first check the value of the array in a specific index and only later if the index is in range. That shouldn't lead to any problems per se unless the array is very short, because it always starts from the other end of the array and the loop ends before the index can fall out of range. However it seems like it triggered some statis analysis tool and it might potentially deceive a future programmer if some of the external conditions (like the starting index) changes. This commit reverses the order of the conditions so the index is checked first. M +4-3libs/widgets/KoZoomAction.cpp https://invent.kde.org/kde/krita/commit/10d47bd625663ed576ccc527f3219e8aa133995f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421076] Identical expressions in KoToolBase.cpp
https://bugs.kde.org/show_bug.cgi?id=421076 Tymond changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||krita/commit/c2ffbc6b19ac96 ||6b231cc8edea13533ac56a310c --- Comment #1 from Tymond --- Git commit c2ffbc6b19ac966b231cc8edea13533ac56a310c by Agata Cacko. Committed on 05/05/2020 at 22:48. Pushed by tymond into branch 'master'. Move asserts before usage of a variable Before this commit, there were two asserts that were checked only after both of the variables were used. This means that instead of asserting, Krita would crash. It probaby doesn't change much in case of Q_ASSERTs (it would be different with asserts that allows recovering) but nonetheless, it makes no sense to assert after using a variable. This commit moves the asserts above the usage. M +2-2libs/pigment/KoColorConversionSystem.cpp https://invent.kde.org/kde/krita/commit/c2ffbc6b19ac966b231cc8edea13533ac56a310c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421082] Copy paste bug in KisWindowLayoutResource.cpp
https://bugs.kde.org/show_bug.cgi?id=421082 Tymond changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421084] t variable is reasigned in kis_color_selector.cpp
https://bugs.kde.org/show_bug.cgi?id=421084 Tymond changed: What|Removed |Added Ever confirmed|0 |1 CC||tamtamy.tym...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421093] New: Right clicking on notification body moves to bottom right
https://bugs.kde.org/show_bug.cgi?id=421093 Bug ID: 421093 Summary: Right clicking on notification body moves to bottom right Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: model...@outlook.com.au CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 128188 --> https://bugs.kde.org/attachment.cgi?id=128188=edit Demonstration of the bug. SUMMARY Right-clicking in the notification body causes it to stop avoiding other windows and revert back to the bottom right corner. STEPS TO REPRODUCE 1. Open the notifications popup (easiest if you pin it) 2. `notify-send "Title" "Body"` 3. Right-click on the notification body OBSERVED RESULT Notification drops to the bottom right corner. EXPECTED RESULT The notification stays above the popup of the notifications bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405266] File name is unreadable while the file is dragged on dark background
https://bugs.kde.org/show_bug.cgi?id=405266 Nate Graham changed: What|Removed |Added Version Fixed In||20.08.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 405266] File name is unreadable while the file is dragged on dark background
https://bugs.kde.org/show_bug.cgi?id=405266 Christian Christiansen changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/dol ||phin/1d72710039b547d91b7138 ||d3899e783e26aac849 Resolution|--- |FIXED --- Comment #2 from Christian Christiansen --- Git commit 1d72710039b547d91b7138d3899e783e26aac849 by Christian Christiansen. Committed on 05/05/2020 at 23:40. Pushed by cchristiansen into branch 'master'. Keep name readable on drag to matching background Summary: Previously, when a single item was selected and dragged, the name would become unreadable when the text colour matched the background colour it was dragged onto. This is now fixed by not deselecting the item (and hence keeping the highlighting around the text) before creating the pixmap for dragging. Test Plan: Tested with Breeze and Breeze Dark. Reviewers: #dolphin, elvisangelaccio, meven Reviewed By: #dolphin, elvisangelaccio, meven Subscribers: meven, elvisangelaccio, kfm-devel Tags: #dolphin Differential Revision: https://phabricator.kde.org/D29378 M +0-1src/kitemviews/kitemlistwidget.cpp https://commits.kde.org/dolphin/1d72710039b547d91b7138d3899e783e26aac849 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420800] QHY CCD 5II driver crashes
https://bugs.kde.org/show_bug.cgi?id=420800 astrogod...@gmail.com changed: What|Removed |Added Version|3.4.1 |3.4.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421092] New: System Settings crashes when trying to access Application Style settings
https://bugs.kde.org/show_bug.cgi?id=421092 Bug ID: 421092 Summary: System Settings crashes when trying to access Application Style settings Product: systemsettings Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: skyw...@cox.net CC: zom...@protonmail.com Target Milestone: --- SUMMARY System Settings crashes when trying to access Application Style settings STEPS TO REPRODUCE 1. Open System Settings 2. Click Application Style 3. System Settings will then crash OBSERVED RESULT System Settings will crash every time. EXPECTED RESULT The Application Style section of System Settings should open. SOFTWARE/OS VERSIONS Operating System: Antergos Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.10-arch1-1 OS Type: 64-bit Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION systemsettings5[722655]: Cannot mix incompatible Qt library (version 0x50c02) with this library (version 0x50e02) kernel: audit: type=1701 audit(1588720114.571:268): auid=1000 uid=1000 gid=985 ses=2 pid=722655 comm="systemsettings5" exe="/usr/bin/systemsettings5" sig=6 res=1 audit: AUDIT1334 prog-id=37 op=LOAD kernel: audit: type=1334 audit(1588720114.585:269): prog-id=37 op=LOAD kernel: audit: type=1334 audit(1588720114.585:270): prog-id=38 op=LOAD audit: AUDIT1334 prog-id=38 op=LOAD systemd[1]: Started Process Core Dump (PID 722686/UID 0). audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@11-722686-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' kernel: audit: type=1130 audit(1588720114.585:271): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@11-722686-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' kwin_x11[1283]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8936, resource id: 115343366, major code: 15 (QueryTree), minor code: 0 kwin_x11[1283]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8941, resource id: 115343366, major code: 18 (ChangeProperty), minor code: 0 kwin_x11[1283]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8978, resource id: 46137559, major code: 18 (ChangeProperty), minor code: 0 systemd-coredump[722689]: Process 722655 (systemsettings5) of user 1000 dumped core. Stack trace of thread 722655: #0 0x7f6c3cb53ce5 raise (libc.so.6 + 0x3bce5) #1 0x7f6c3cb3d857 abort (libc.so.6 + 0x25857) #2 0x7f6c3cf5e938 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x8e938) #3 0x7f6c3cf73860 n/a (libQt5Core.so.5 + 0xa3860) #4 0x7f6c2087bf3f n/a (libqgtk2style.so + 0x23f3f) #5 0x7f6c2086a5f0 n/a (libqgtk2style.so + 0x125f0) #6 0x7f6c2087eb00 n/a (libqgtk2style.so + 0x26b00) #7 0x7f6c3dd31cae _ZN13QStyleFactory6createERK7QString (libQt5Widgets.so.5 + 0x1d1cae) #8 0x7f6c227970e3 n/a (kcm_style.so + 0x370e3) #9 0x7f6c3c1d97ed _ZN17QQmlObjectCreator8finalizeER26QQmlInstantiationInterrupt (libQt5Qml.so.5 + 0x3017ed) #10 0x7f6c3c16201b n/a (libQt5Qml.so.5 + 0x28a01b) #11 0x7f6c3c162563 _ZN17QQmlEnginePrivate8incubateER13QQmlIncubatorP15QQmlContextData (libQt5Qml.so.5 + 0x28a563) #12 0x7f6c3a86b270 n/a (libQt5QmlModels.so.5 + 0x6b270) #13 0x7f6c3a86b415 _ZN17QQmlDelegateModel6objectEiN13QQmlIncubator14IncubationModeE (libQt5QmlModels.so.5 + 0x6b415) #14 0x7f6c3c6bc4f6 n/a (libQt5Quick.so.5 + 0x35c4f6) #15 0x7f6c3c6afdee n/a (libQt5Quick.so.5 + 0x34fdee) #16 0x7f6c3c6bd854 n/a (libQt5Quick.so.5 + 0x35d854) #17 0x7f6c3c6c08f1 n/a (libQt5Quick.so.5 + 0x3608f1)
[okular] [Bug 421091] New: Too much memory
https://bugs.kde.org/show_bug.cgi?id=421091 Bug ID: 421091 Summary: Too much memory Product: okular Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: nilsoc...@gmail.com Target Milestone: --- Created attachment 128187 --> https://bugs.kde.org/attachment.cgi?id=128187=edit KSysGuard screenshot Okular is using way too much of memory Steps to reproduce: Open any PDF file, and scroll through the document for sometime. It even crossed 6GiB in my-case. In comparison, I tested doing the same with Evince, at max it crossed 300MiB and it is much more faster. Okular Version: 1.10.0 Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 Kernel Version: 5.6.8-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 418179] Cannot stop looping image capture
https://bugs.kde.org/show_bug.cgi?id=418179 --- Comment #1 from mountainai...@outlook.com --- This issue can be resolved by turning off the feature that causes the FITS Viewer to focus when receiving an image. However, this is often not ideal. Additional details: When running a 1-second exposure loop, I often need to click twice to get to the Ekos tab, then I often don't have enough time to click the Stop button before it starts downloading the image and then focuses on the FITS viewer. This often takes two attempts, sometimes three, to stop the exposures. One potential remedy is to NOT deliver the image to the FITS viewer when the user clicks stop during a download. I have not seen it completely block me, forcing me to quit KStars, in a while so this ticket can be closed if you feel there is nothing actionable here. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 420984] Problem when compiling kio-extras in craft in Windows 10 Home China
https://bugs.kde.org/show_bug.cgi?id=420984 --- Comment #5 from brute4s99 --- The patch is in review: https://phabricator.kde.org/D29461 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 418159] Polar Alignment Fails
https://bugs.kde.org/show_bug.cgi?id=418159 --- Comment #3 from mountainai...@outlook.com --- To recap, two issues: 1) When the PA is too far off, the PA tool seems to get confused and can slew the telescope to its limits. I have not had this happen in quite a while, so I think we can close that issue. These days the worst I seem to see is the PA correction vector being wider than the screen, but that's expected if my PA is off. 2) The issue regarding the PA tool not automatically slewing the mount appears to be a function of the SPEED dropdown, which defaults to 5x. Changing this to 9x proves that it slews normally (I did NOT verify that it is actually slewing at 5x). I recommend changing this default, as I imagine it would take some manner of minutes to slew 30 degrees at 5x. Feel free to close this ticket, but I did not mark it as such because I recommended the default slew speed change. Feel free to close it. -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 359063] Plain text version of html-only message is not respecting encoding specified in html message
https://bugs.kde.org/show_bug.cgi?id=359063 xchain changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||xch...@gmx.net --- Comment #6 from xchain --- Cannot reproduce with a mail as generated by the script in Comment 4 using KMail git master. Respecting the encoding seems to be fixed in the meantime. There is one issue left: The "" is not displayed. However, this can be fixed by adding the missing "", so that's more of an issue with the generated mail than something to work around in KMail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 362650] an extra space character in attached file names the UTF-8 encoded
https://bugs.kde.org/show_bug.cgi?id=362650 xchain changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||xch...@gmx.net --- Comment #7 from xchain --- Cannot reproduce using KMail git master. Like in Comment 2, files attached to mails created with KMail have their filename encoded in a single line and display and save just fine. Please let us know whether you can still reproduce. It would also be interesting to know which mail application was used to create the message you received. You can also attach a test case to the bug by saving as an mbox file. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 416758] Encoding broken
https://bugs.kde.org/show_bug.cgi?id=416758 xchain changed: What|Removed |Added CC||xch...@gmx.net --- Comment #9 from xchain --- I could reproduce the issue with the test case from Comment 8. However, after ea14bb921d43 in messagelib it seems to be fixed (did not try to reproduce with the other cases mentioned above, though). Might be worth trying again once 5.14.1 shipped, and possibly attach an mbox test case if it is still failing for you. Otherwise close as fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420702] Secondary monitor black after rotation
https://bugs.kde.org/show_bug.cgi?id=420702 --- Comment #2 from Roger Light --- I have done a clean install (but still have an image of the old install, although that's irrelevant). The problem persists. I created a fresh user and the problem is not present for that user, so it must be a user configuration issue. -- You are receiving this mail because: You are watching all bug changes.
[kmime] [Bug 420849] Adresses are incorrectly quoted if they contain a non-ascii character
https://bugs.kde.org/show_bug.cgi?id=420849 xchain changed: What|Removed |Added CC||xch...@gmx.net --- Comment #2 from xchain --- Not sure what the "unspecified" version refers to, but I cannot reproduce with KMail 5.14.0. I could reproduce briefly with an older git master, by saving a new message with two addresses containing non-ascii characters in the Drafts folder and trying to reply to all. However, in addition I had to move "utf-8" to the top of KMail's "Charset" configuration page. In the default configuration with "us-ascii" on top it worked just fine. That being said, with the current git master this seems to be fixed (at least for the moment). Possibly due to ea14bb921d43 in messagelib. Could you try again? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420766] Envelope From is empty on outgoing mails
https://bugs.kde.org/show_bug.cgi?id=420766 xchain changed: What|Removed |Added CC||xch...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] Messages or parts with Content-Transfer-Encoding: base64 have no line breaks displayed
https://bugs.kde.org/show_bug.cgi?id=392239 xchain changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||xch...@gmx.net --- Comment #1 from xchain --- I tried reproducing with the following mbox file using git master: MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" YWFhIGJiYgpjY2MgZGRkCmVlZSBmZmYK According to "base64 -d" this should be shown as: aaa bbb ccc ddd eee fff ..which is exactly what KMail showed, including line breaks, i.e. I'm unable to reproduce. (Let me know in case I misunderstood the steps to reproduce.) Please check whether the issue still happens with a recent version of KMail, and add a test case. You can use a text editor to redact the mail after saving as mbox, of course. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 298349] kmail2 composer (still) fails to display non-ascii characters in quoted text on reply with some mails (only with nested multipart mime parts?)
https://bugs.kde.org/show_bug.cgi?id=298349 xchain changed: What|Removed |Added CC||xch...@gmx.net --- Comment #17 from xchain --- (In reply to Hans-Peter Jansen from comment #16) > "Keep original charset..." [...] is enabled by default Are you sure about that? I tested KMail 18.08 and current git master, and in both cases "Keep original charset..." was unchecked by default. Anyway, I simplified the mail attached in Comment 2 a bit (see below). Findings (with "Keep original charset..." checked): - "Content-Type: multipart/mixed;" is necessary to reproduce - after removing the "€" symbol (first line), "können" is not garbled anymore Reduced test case: Date: Wed, 18 Apr 2012 14:57:15 +0200 From: "X xxxh" To: "xx " Subject: Re: [] Content-Type: multipart/mixed; boundary="===3895039973466476490==" --===3895039973466476490== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable =E2=82=AC k=C3=B6nnen --===3895039973466476490==-- -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 404863] KMail should use UTF-8 as default encoding
https://bugs.kde.org/show_bug.cgi?id=404863 xchain changed: What|Removed |Added CC||xch...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kdepim] [Bug 345959] When an individual folder is set to prefer HTML to Plaintext, some E-mails with both HTML and plaintext parts will display the plaintext part
https://bugs.kde.org/show_bug.cgi?id=345959 xchain changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from xchain --- Thanks for the response. Let's set the status to RESOLVED for now, but feel free to reopen if you happen to come across a failing mail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385649] KMail renders HTML-escaped elements without having HTML-view enabled
https://bugs.kde.org/show_bug.cgi?id=385649 xchain changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||xch...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421090] New: Clicked on updates tray icon and updates crashed
https://bugs.kde.org/show_bug.cgi?id=421090 Bug ID: 421090 Summary: Clicked on updates tray icon and updates crashed Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: jtz...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-99-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: I had a few apps open, but definitely no memory or CPU pressure. I saw the Update icon in the system tray and left clicked on it. It opened up the window and I clicked the update button. That's when I got a crash report prompt and filled out this report. I just tried it a second time and it crashed again. I'm wasn't running any other instance of a package manager (i.e. wasn't running aptitude on the Konsole). This is the first time I've seen Discover crash like this so it's something new. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7feaf793d800 (LWP 480))] Thread 10 (Thread 0x7fea9f9aa700 (LWP 527)): #0 0x7feaf2f1a839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7feaf361c775 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7feaf0e8bf96 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7feaf0e8c835 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7feaf0e688cc in QSslSocket::startClientEncryption() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7feaf0e69578 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7feaf0e71379 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7feaf3832555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7feaf0e3bf09 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7feaf0e3ee78 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7feaf0e4f7ed in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7feaf5ad783c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7feaf5adf104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7feaf38038d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7feaf385d4ed in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7feaed704417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7feaed704650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7feaed7046dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7feaf385c8ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7feaf380190a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7feaf362023a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7feaf362517d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7feaef8336db in start_thread (arg=0x7fea9f9aa700) at pthread_create.c:463 #23 0x7feaf2f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7feaa517b700 (LWP 491)): #0 0x7feaed703cf0 in g_main_context_query () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7feaed704547 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feaed704962 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feab9be8276 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7feaed72c175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7feaef8336db in start_thread (arg=0x7feaa517b700) at pthread_create.c:463 #6 0x7feaf2f2088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7feaa597c700 (LWP 490)): #0 0x7feaf2f0f0b4 in __GI___libc_read (fd=25, buf=0x7feaa597bce0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7feaed7492b0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7feaed7040b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feaed704570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7feaed7046dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7feaed704721 in () at
[kstars] [Bug 417968] Critical Break: Guiding via MOUNT Unavailable.
https://bugs.kde.org/show_bug.cgi?id=417968 --- Comment #24 from mountainai...@outlook.com --- GREAT NEWS! KStars Mac 3.4.2 to StellarMateOS 1.5.2 -- Guide Via show Celestron CGX KStars Mac 3.4.3 to StellarMateOS 1.5.2 -- Guide Via show Celestron CGX StellarMateOS 1.5.2 -- Guide Via show Celestron CGX KStars Mac 3.4.2 Direct USB -- Guide Via show Celestron CGX It appears that Celestron CGX is now back in the Guide Via dropdown. I wasn't able to test it because I had the gear set up in my living room, but may be able to test it tonight. Side note: It would be really great if we had an easy way to update the INDI drivers on the Mac without waiting for a KStars release. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421089] New: Plasma Crash
https://bugs.kde.org/show_bug.cgi?id=421089 Bug ID: 421089 Summary: Plasma Crash Product: plasmashell Version: 5.18.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: georges.schw...@free.fr CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.3) Qt Version: 5.13.2 Frameworks Version: 5.68.0 Operating System: Linux 5.6.8-300.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (Thirty Two) -- Information about the crash: - What I was doing when the application crashed: Normal Usage of My desktop then Crash of plasma - Unusual behavior I noticed: Task Bar Is glitching I experienced problems using Dolphin No task bar, no wallpapaer - Custom settings of the application: I'm using multi-screen on my desktop 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 0x7fd5bc61c580 (LWP 5411))] Thread 74 (Thread 0x7fd4909dd700 (LWP 14626)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd5c0288463 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7fd5c1d14f64 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7fd5c1d1644d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7fd5c0282846 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 73 (Thread 0x7fd44700 (LWP 14625)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd59e42b13b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fd59e42ac0b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 72 (Thread 0x7fd44effd700 (LWP 12806)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd5c0288463 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7fd5c1d14f64 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7fd5c1d1644d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7fd5c0282846 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 71 (Thread 0x7fd44f7fe700 (LWP 12805)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd59e42b13b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fd59e42ac0b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 70 (Thread 0x7fd4917fb700 (LWP 9183)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd5c0288463 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 #2 0x7fd5c1d14f64 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7fd5c1d1644d in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7fd5c0282846 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 69 (Thread 0x7fd491ffc700 (LWP 9182)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd59e42b13b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fd59e42ac0b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 68 (Thread 0x7fd4927fd700 (LWP 9117)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd59e42b13b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fd59e42ac0b in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fd5bf7d2432 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd5bff099d3 in clone () at /lib64/libc.so.6 Thread 67 (Thread 0x7fd4a1186700 (LWP 8757)): #0 0x7fd5bf7d8e92 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd5c0288463 in
[elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830 Rick changed: What|Removed |Added CC|rickjcar...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 420771] CRASH after try of commit to git repository
https://bugs.kde.org/show_bug.cgi?id=420771 --- Comment #8 from Kevin Kofler --- I cannot promise that I will be able to fix it (especially without having access to a reproducer), but the chance that I will be able to find what is wrong will be higher if I know the exact line where it crashes. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 420771] CRASH after try of commit to git repository
https://bugs.kde.org/show_bug.cgi?id=420771 --- Comment #7 from Piotr Mierzwinski --- (In reply to Kevin Kofler from comment #6) > The problem with these backtraces is that there is no debugging information > for libkomparediff2 installed, so I do not see line numbers nor other > details. If you are able to identify issue and fix it, I'll try to provide more detailed backtrace, so I will install libkomparediff2 with debug information. Thanks for quick response. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 420771] CRASH after try of commit to git repository
https://bugs.kde.org/show_bug.cgi?id=420771 --- Comment #6 from Kevin Kofler --- The problem with these backtraces is that there is no debugging information for libkomparediff2 installed, so I do not see line numbers nor other details. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421061] Ugly icons with some apps
https://bugs.kde.org/show_bug.cgi?id=421061 --- Comment #4 from jan.clausse...@web.de --- Yes, I understand that. The people at VSCode said they use a quality PNG and I should use a „proper“ dock. No one wants to take responsibility and that is fine. Open source is not a company and too many apps have to work together somehow. It is not a manageable task in some cases. No offense! That is why setting custom icons would be solution, I think. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 420800] QHY CCD 5II driver crashes
https://bugs.kde.org/show_bug.cgi?id=420800 astrogod...@gmail.com changed: What|Removed |Added CC||astrogod...@gmail.com --- Comment #1 from astrogod...@gmail.com --- I'm having same issue -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421070] Moving files / folders across
https://bugs.kde.org/show_bug.cgi?id=421070 --- Comment #2 from brute4s99 --- > What do you mean by panel 1 and panel 2? Split views in the same window? > Yes -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 421088] New: Where are the interpolated data?
https://bugs.kde.org/show_bug.cgi?id=421088 Bug ID: 421088 Summary: Where are the interpolated data? Product: LabPlot2 Version: 2.7.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: robgrueb...@gmail.com Target Milestone: --- SUMMARY Today I tried Labplot for the first time and compliment, I like it very much. Unfortunately I got stuck with my first Use Case: STEPS TO REPRODUCE 1. new spreadsheet filled with 10 xy-pairs 2. menu / Analysis greyed out - ? 3. right click on Y-column / Analyze and Plot Data / Interpolate - this works as expected 4. but where are the interpolated data? OBSERVED RESULT Interpolated data can only be seen in the graphic EXPECTED RESULT I would have expected a new spreadsheet with the interpolated data or an extension of the source spreadsheet. What am I doing wrong? SOFTWARE/OS VERSIONS Win 10 64 bit ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421004] Group "Print" and "Print preview" next to each other in the File menu
https://bugs.kde.org/show_bug.cgi?id=421004 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://invent.kde.org/kde/ ||okular/commit/390a88411acc9 ||893425789cee9963709255d25c5 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Albert Astals Cid --- Git commit 390a88411acc9893425789cee9963709255d25c5 by Albert Astals Cid. Committed on 05/05/2020 at 20:33. Pushed by aacid into branch 'release/20.04'. Fix File menu structure M +2-2shell/shell.rc https://invent.kde.org/kde/okular/commit/390a88411acc9893425789cee9963709255d25c5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421075] Trailing Whitespace when creating directories or files.
https://bugs.kde.org/show_bug.cgi?id=421075 --- Comment #4 from Larry Dewey --- (In reply to Christoph Feck from comment #3) > It could warn about those spaces (and offer to remove them), but never > silently drop them. I understand why you never want to do something without the user knowing about it. Especially when the user DOES mean to have them there. At the same time, I feel like wanting them there is more of the edge case than the vase majority. Would it be possible to remove, warn, potentially and prompt to leave the spaces in (with an option to disable the warning in settings)? Then the majority of users will get the expected experience, while edge case users can still keep the customization of the naming? -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 421083] Karbon crashes on closing a svg fail after selecting any of its parts
https://bugs.kde.org/show_bug.cgi?id=421083 --- Comment #2 from avlas --- Created attachment 128185 --> https://bugs.kde.org/attachment.cgi?id=128185=edit Karbon's icon As an example, this also happens in my system with Karbon's icon -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 420771] CRASH after try of commit to git repository
https://bugs.kde.org/show_bug.cgi?id=420771 --- Comment #5 from Kevin Kofler --- Well, strictly speaking, it's a crash in libkomparediff2, KDevelop does not use the code from the kompare application (anymore). But there is no separate libkomparediff2 component, it seems. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421044] "Titlebar buttons" tab sholud be moved outside of "Look and feel" section
https://bugs.kde.org/show_bug.cgi?id=421044 --- Comment #6 from Christoph Feck --- Some decorations don't respect the button configuration. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 --- Comment #22 from Maik Qualmann --- Git commit a28e8c9512c53a2ee68e60446c9e57ef6f988214 by Maik Qualmann. Committed on 05/05/2020 at 20:58. Pushed by mqualmann into branch 'master'. try to give Exiv2 under Windows a UTF16 string M +5-0core/libs/metadataengine/engine/metaengine_comments.cpp M +5-0core/libs/metadataengine/engine/metaengine_exif.cpp M +9-1core/libs/metadataengine/engine/metaengine_fileio.cpp M +5-0core/libs/metadataengine/engine/metaengine_iptc.cpp M +10 -0core/libs/metadataengine/engine/metaengine_p.cpp M +5-0core/libs/metadataengine/engine/metaengine_previews.cpp M +5-0core/libs/metadataengine/engine/metaengine_xmp.cpp https://invent.kde.org/kde/digikam/commit/a28e8c9512c53a2ee68e60446c9e57ef6f988214 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 421086] Import a project installed by kdesrc-build
https://bugs.kde.org/show_bug.cgi?id=421086 Friedrich W. H. Kossebau changed: What|Removed |Added Severity|normal |wishlist Version|5.3.2 |5.5.1 -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 421083] Karbon crashes on closing a svg fail after selecting any of its parts
https://bugs.kde.org/show_bug.cgi?id=421083 --- Comment #1 from avlas --- I mentioned about this here: https://www.reddit.com/r/kde/comments/gab898/karbon_dependency_for_calligra/foz42tw -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421087] New: Plasmashell Randomly Crashed
https://bugs.kde.org/show_bug.cgi?id=421087 Bug ID: 421087 Summary: Plasmashell Randomly Crashed Product: plasmashell Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ferenos...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-46-generic x86_64 Windowing system: X11 Distribution: Feren OS -- Information about the crash: - What I was doing when the application crashed: I was just doing my regular GTK theme making when I accidentally opened Slick Greeter's Test Mode (LightDM Greeter) after checking my GTK theme thus far in it, and then went to open gtk3-widget-factory instead when before it had a chance to be loaded Plasmashell was already reloading from having just crashed. -- 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 0x7f7472180800 (LWP 11643))] Thread 28 (Thread 0x7f73d9ffb700 (LWP 4006)): #0 0x7f740fb8df36 in pa_pstream_ref () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #1 0x7f740fb8eab1 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f740fb8f33f in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #3 0x7f74142f1108 in pa_mainloop_dispatch () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f74142f14de in pa_mainloop_iterate () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f74142f1560 in pa_mainloop_run () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f74142ff3c9 in () at /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f740fb9f318 in () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7f746883c6db in start_thread (arg=0x7f73d9ffb700) at pthread_create.c:463 #9 0x7f746b4e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7f73da7fc700 (LWP 30926)): #0 0x7f74688429f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f7418141e58) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f74688429f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f7418141e08, cond=0x7f7418141e30) at pthread_cond_wait.c:502 #2 0x7f74688429f3 in __pthread_cond_wait (cond=0x7f7418141e30, mutex=0x7f7418141e08) at pthread_cond_wait.c:655 #3 0x7f74430cca0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f74430cc607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f746883c6db in start_thread (arg=0x7f73da7fc700) at pthread_create.c:463 #6 0x7f746b4e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f73daffd700 (LWP 25123)): #0 0x7f74688429f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5569ee81efd0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f74688429f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5569ee81ef80, cond=0x5569ee81efa8) at pthread_cond_wait.c:502 #2 0x7f74688429f3 in __pthread_cond_wait (cond=0x5569ee81efa8, mutex=0x5569ee81ef80) at pthread_cond_wait.c:655 #3 0x7f746bc05e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f746bc05fd9 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f746fd46233 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f746fd46691 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f746bbff8ac in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f746883c6db in start_thread (arg=0x7f73daffd700) at pthread_create.c:463 #9 0x7f746b4e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f73db7fe700 (LWP 25122)): #0 0x7f74688429f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5569f0ae5098) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f74688429f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5569f0ae5048, cond=0x5569f0ae5070) at pthread_cond_wait.c:502 #2 0x7f74688429f3 in __pthread_cond_wait (cond=0x5569f0ae5070, mutex=0x5569f0ae5048) at pthread_cond_wait.c:655 #3 0x7f74430cca0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f74430cc607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f746883c6db in start_thread (arg=0x7f73db7fe700) at pthread_create.c:463 #6 0x7f746b4e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f73dbfff700 (LWP 24764)): #0 0x7f74688429f3 in futex_wait_cancelable (private=,
[kdevelop] [Bug 421086] New: Import a project installed by kdesrc-build
https://bugs.kde.org/show_bug.cgi?id=421086 Bug ID: 421086 Summary: Import a project installed by kdesrc-build Product: kdevelop Version: 5.3.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Build tools: CMake Assignee: kdevelop-bugs-n...@kde.org Reporter: ed...@gmx.fr Target Milestone: --- Importing in kdevelop the okular/CMakeLists.txt project installed through `kdesrc-build okular`, code navigation failed: Hovering on a method or hitting Alt does not bring any information (usually, it says where it has been defined, allowing easy navigation, it's great !) Note: grep build-dir ~/.kdesrc-buildrc build-dir /usr/local/build/kde/build # Where the source build is run (not in the standard place for disk space/speed/no-backup reasons) This report shares how this has been solved, thanks to help on freenode #kdevelop: [17:31] ederag: so in the project configuration, in the page "CMake", at the top you want to have the entry pointing to the toplevel build dir of okular you use with kdesrc-build. That's the directory shown by grep build-dir ~/.kdesrc-buildrc Now all the variables point to the /usr/local/build/kde ... great ! And a few minutes later (5-15 min ?), the semantic highlighting just came on. code navigation works ! Now configure the launch: workaround https://bugs.kde.org/show_bug.cgi?id=420630#c1 Settings > configure kdevelop > Environment > profile > Add "kde" add a line with variable: QT_PLUGIN_PATH value: /usr/local/build/kde/install/lib64/plugins run > Configure Launches > Add > choose a name, e.g. 'kdesrc-build run' Script interpreter: perl Always run the same file : file:///home/ederag/share/prog/kde/kdesrc-build/kdesrc-build Arguments: --run okular Environment: kde (the one created above) since the launch passes through a script, the process has to be attached manually: https://docs.kde.org/trunk5/en/extragear-kdevelop/kdevelop/attaching-the-debugger-to-a-running-process.html Of course it could be possible to add these instructions, e.g. in https://docs.kde.org/trunk5/en/extragear-kdevelop/kdevelop/setting-up-a-session-and-importing-an-existing-project.html#option-2--importing-a-project-that-is- already-on-your-hard-drive but it would be great if this could be integrated into the wizard itself. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388155] Kmail shows duplicate emails - detect automatically on refresh?
https://bugs.kde.org/show_bug.cgi?id=388155 --- Comment #2 from Alexandre Bonneau --- I'm adding a comment here instead of creating a new issue, since under Debian Bullseye with akonadi and kmail version `4:19.08.3-1`, I'm getting mail duplicates only in a very specific situation ; If I open kmail on two different computers at the same time (ie. on my laptop and my workstation). If only one akonadi server is running on both computers, then everything is fine. However if I run akonadi server on both computers, everything goes haywire and kmail starts spewing lots (LOTS!..in the hundreds) of duplicates mails. I hope this helps figuring out any race condition that might happen. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 421078] [V 3.2.0] Toolbar status is not saved
https://bugs.kde.org/show_bug.cgi?id=421078 --- Comment #1 from avlas --- > This happens when opening Karbon and enabling the toolbar in the main script Sorry, I meant in the main view (i.e., when opening karbon with no specific open file; no idea why I said main script) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421075] Trailing Whitespace when creating directories or files.
https://bugs.kde.org/show_bug.cgi?id=421075 --- Comment #3 from Christoph Feck --- It could warn about those spaces (and offer to remove them), but never silently drop them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421085] New: KDE desktop crash after update and reboot
https://bugs.kde.org/show_bug.cgi?id=421085 Bug ID: 421085 Summary: KDE desktop crash after update and reboot Product: plasmashell Version: 5.18.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jase...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.4) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.6.7-050607-generic x86_64 Windowing system: X11 Distribution: KDE neon Testing Edition -- Information about the crash: After last updates Desktop chrash on login after reboot. The crash can be reproduced sometimes. -- 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 0x7f59ebf1ec80 (LWP 3422))] Thread 19 (Thread 0x7f59554b8700 (LWP 4070)): #0 0x7f59e262f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fbf3744614) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f59e262f9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fbf37445c0, cond=0x55fbf37445e8) at pthread_cond_wait.c:502 #2 0x7f59e262f9f3 in __pthread_cond_wait (cond=0x55fbf37445e8, mutex=0x55fbf37445c0) at pthread_cond_wait.c:655 #3 0x7f59e59f7e5b in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55fbf37445c0) at thread/qwaitcondition_unix.cpp:146 #4 0x7f59e59f7e5b in QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=, mutex=0x55fbf39b5f60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f59e59f7fd9 in QWaitCondition::wait(QMutex*, unsigned long) (this=this@entry=0x55fbf39b5f68, mutex=mutex@entry=0x55fbf39b5f60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f59e9af6233 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55fbf39b5f58) at scenegraph/qsgthreadedrenderloop.cpp:255 #7 0x7f59e9af6233 in QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55fbf39b5ec0) at scenegraph/qsgthreadedrenderloop.cpp:905 #8 0x7f59e9af6691 in QSGRenderThread::run() (this=0x55fbf39b5ec0) at scenegraph/qsgthreadedrenderloop.cpp:1000 #9 0x7f59e59f18ac in QThreadPrivate::start(void*) (arg=0x55fbf39b5ec0) at thread/qthread_unix.cpp:342 #10 0x7f59e26296db in start_thread (arg=0x7f59554b8700) at pthread_create.c:463 #11 0x7f59e529b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f5955cb9700 (LWP 4069)): #0 0x7f59e262f9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fbf3aa2618) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f59e262f9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fbf3aa25c8, cond=0x55fbf3aa25f0) at pthread_cond_wait.c:502 #2 0x7f59e262f9f3 in __pthread_cond_wait (cond=0x55fbf3aa25f0, mutex=0x55fbf3aa25c8) at pthread_cond_wait.c:655 #3 0x7f59c5116a0b in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f59c5116607 in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f59e26296db in start_thread (arg=0x7f5955cb9700) at pthread_create.c:463 #6 0x7f59e529b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f5977016700 (LWP 4066)): #0 0x7f59df3dd644 in g_mutex_unlock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f59df396b18 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f59df3974fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f59df3976dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f59e5c4044b in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f5968007fa0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f59e5bdf9aa in QEventLoop::exec(QFlags) (this=this@entry=0x7f5977015d60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f59e59f03d7 in QThread::exec() (this=) at thread/qthread.cpp:536 #7 0x7f5958839467 in KCupsConnection::run() () at /usr/lib/x86_64-linux-gnu/libkcupslib.so #8 0x7f59e59f18ac in QThreadPrivate::start(void*) (arg=0x55fbf37671d0) at thread/qthread_unix.cpp:342 #9 0x7f59e26296db in start_thread (arg=0x7f5977016700) at pthread_create.c:463 #10 0x7f59e529b88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f5977fff700 (LWP 3706)): #0 0x7f59df3dd629 in g_mutex_lock () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f59df396b33 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f59df3974fb in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f59df3976dc in g_main_context_iteration () at
[krita] [Bug 421084] t variable is reasigned in kis_color_selector.cpp
https://bugs.kde.org/show_bug.cgi?id=421084 Scott Petrovic changed: What|Removed |Added CC||scottpetro...@gmail.com --- Comment #1 from Scott Petrovic --- Usually for code changes, there are not done in bugzilla. We have a different process for changing code through our GitLab instance. Usually for bugzilla, the important thing is having reprodicible steps to get a bug. These seem more like code refactorings. https://invent.kde.org/kde/krita It looks like you have already created a fork. Could you just make the fixes and do Pull requests for these fixes? https://invent.kde.org/qarmin/krita That would help us out a lot. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388155] Kmail shows duplicate emails - detect automatically on refresh?
https://bugs.kde.org/show_bug.cgi?id=388155 Alexandre Bonneau changed: What|Removed |Added CC||alexandre.bonneau@linuxfr.e ||u --- Comment #1 from Alexandre Bonneau --- This sounds like an XY problem. Instead of "automatically detecting and deleting" duplicates mails (I can easily imagine how this could go wrong and delete lots of non-duplicated mails), akonadi should strive to _not_ duplicate the mails in the first place! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Subsurfaces are not clipped
https://bugs.kde.org/show_bug.cgi?id=387313 --- Comment #66 from Patrick Silva --- *** Bug 410729 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410729] gtk menu and submenu are black on Wayland
https://bugs.kde.org/show_bug.cgi?id=410729 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 387313 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421084] New: t variable is reasigned in kis_color_selector.cpp
https://bugs.kde.org/show_bug.cgi?id=421084 Bug ID: 421084 Summary: t variable is reasigned in kis_color_selector.cpp Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mikrutra...@protonmail.com Target Milestone: --- ``` qreal t = (pt.x() - m_lightStripArea.x()) / qreal(m_lightStripArea.width()); t = (pt.y() - m_lightStripArea.y()) / qreal(m_lightStripArea.height()); ``` https://invent.kde.org/kde/krita/-/blob/master/plugins/dockers/artisticcolorselector/kis_color_selector.cpp#L348-349 -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 421083] New: Karbon crashes on closing a svg fail after selecting any of its parts
https://bugs.kde.org/show_bug.cgi?id=421083 Bug ID: 421083 Summary: Karbon crashes on closing a svg fail after selecting any of its parts Product: karbon Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: jsar...@gmail.com Target Milestone: --- Application: karbon (3.2.0) Qt Version: 5.14.2 Frameworks Version: 5.69.0 Operating System: Linux 5.3.0-46-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: 1. I opened a svg file (any as far as I can say) 2. I selected any item 3. I closed the file The crash can be reproduced every time. -- Backtrace: Application: Karbon (karbon), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3fa99da800 (LWP 10505))] Thread 5 (Thread 0x7f3f73f95700 (LWP 13099)): #0 0x7f3fa93320b4 in __GI___libc_read (fd=19, buf=0x7f3f73f94b90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f3fa085f2b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3fa081a0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3fa081a570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3fa081a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3fa7d5a44b in QEventDispatcherGlib::processEvents (this=0x7f3f6c987f20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f3fa7cf99aa in QEventLoop::exec (this=this@entry=0x7f3f73f94da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f3fa7b0a3d7 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f3fa7b0b8ac in QThreadPrivate::start (arg=0x55e0a7219280) at thread/qthread_unix.cpp:342 #9 0x7f3fa1f8c6db in start_thread (arg=0x7f3f73f95700) at pthread_create.c:463 #10 0x7f3fa934388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f3f7d8e4700 (LWP 10524)): #0 0x7f3fa1f929f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e0a2d0ef28) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e0a2d0eed8, cond=0x55e0a2d0ef00) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e0a2d0ef00, mutex=0x55e0a2d0eed8) at pthread_cond_wait.c:655 #3 0x7f3f7ed97ecb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3f7ed97ac7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3fa1f8c6db in start_thread (arg=0x7f3f7d8e4700) at pthread_create.c:463 #6 0x7f3fa934388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f3f8bfff700 (LWP 10507)): #0 0x7f3fa9336bf9 in __GI___poll (fds=0x7f3f8402f780, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3fa081a5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3fa081a6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3fa7d5a44b in QEventDispatcherGlib::processEvents (this=0x7f3f84000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f3fa7cf99aa in QEventLoop::exec (this=this@entry=0x7f3f8bffed70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #5 0x7f3fa7b0a3d7 in QThread::exec (this=) at thread/qthread.cpp:536 #6 0x7f3fa25db555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f3fa7b0b8ac in QThreadPrivate::start (arg=0x7f3fa2853da0) at thread/qthread_unix.cpp:342 #8 0x7f3fa1f8c6db in start_thread (arg=0x7f3f8bfff700) at pthread_create.c:463 #9 0x7f3fa934388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f3f93852700 (LWP 10506)): #0 0x7f3fa9336bf9 in __GI___poll (fds=0x7f3f93851ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3f99b4d747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f3f99b4f36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f3f95fb0fd0 in QXcbEventQueue::run (this=0x55e0a2b0bfb0) at qxcbeventqueue.cpp:228 #4 0x7f3fa7b0b8ac in QThreadPrivate::start (arg=0x55e0a2b0bfb0) at thread/qthread_unix.cpp:342 #5 0x7f3fa1f8c6db in start_thread (arg=0x7f3f93852700) at pthread_create.c:463 #6 0x7f3fa934388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3fa99da800 (LWP 10505)): [KCrash Handler] #6 0x7f3f8a76a114 in KoPACanvasBase::viewConverter (this=0x55e0a4a8c1f0) at ./libs/pageapp/KoPACanvasBase.cpp:139 #7 0x7f3f8a767bf8 in KoPACanvas::inputMethodQuery (this=0x55e0a4a8c1c0,
[dolphin] [Bug 421075] Trailing Whitespace when creating directories or files.
https://bugs.kde.org/show_bug.cgi?id=421075 Larry Dewey changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Larry Dewey --- (In reply to Nate Graham from comment #1) > Can you explain why you think this should happen? What problem is it causing > you? Bug reports that just describe a problem are usually more helpful than > ones that propose a solution without explaining the problem. Can you explain why you think this should happen? There are a number of reasons that I feel it should happen: 1. Consistency with other file managers. - Nautilus, Thunar, Nemo, etc all prevent you from entering a name with a trailing or leading white space. 2. Ease of use. - In most instances users do not mean to place a leading or trailing white space when naming their directories or file names. - Saving files to samba, nfs, or sshfs file shares fail to save when not quoted or escaped. - Output while in command line directory tree fails to clearly show spaces when in such a directory. 3. Navigation from the command line. - Without quoting or escaping the space at the beginning or end of the file or directory name, you may end up in an undesired location. - Allows for duplicate directory naming. For example, "python stuff" and "python stuff " or " python stuff". while this could easily be blamed on the user, it could also be prevented from happening. What problem is it causing you? I currently have an nfs share, a samba share, and an sshfs share all connected to my Kubuntu machine. When trying to transfer documents, it throws an error because the intened destination was unable to be found (due to the space). While it is easily fixed by removing the space, it could have been avoided in the first place by stripping the leading/trailing white spaces from the name of the file or directory. Also, my son and wife use this computer, and tend to inadvertently leave a trailing space after the name. Which causes frustration for them. (In reply to Nate Graham from comment #1) > ...Bug reports that just describe a problem are usually more helpful than > ones that propose a solution without explaining the problem. I agree that fully understanding what is happening is helpful for debugging. Having dealt with many bugs, myself, I also try to prevent detail overloads. Hope this helps clarify what I am experiencing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421082] New: Copy paste bug in KisWindowLayoutResource.cpp
https://bugs.kde.org/show_bug.cgi?id=421082 Bug ID: 421082 Summary: Copy paste bug in KisWindowLayoutResource.cpp Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mikrutra...@protonmail.com Target Milestone: --- ``` if (aRect.y() == bRect.y()) return aRect.x() < bRect.x(); return (aRect.y() < aRect.y()); }); ``` https://invent.kde.org/kde/krita/-/blob/master/libs/ui/KisWindowLayoutResource.cpp#L212 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421081] New: Toolbar is used before checking against nullptr in KisMainWindow.cpp
https://bugs.kde.org/show_bug.cgi?id=421081
Bug ID: 421081
Summary: Toolbar is used before checking against nullptr in
KisMainWindow.cpp
Product: krita
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: mikrutra...@protonmail.com
Target Milestone: ---
```
KToolBar * toolBar = ::qobject_cast(it);
toolBar->setMovable(KisConfig(true).readEntry("LockAllDockerPanels",
false));
if (toolBar) {
```
https://invent.kde.org/kde/krita/-/blob/master/libs/ui/KisMainWindow.cpp#L514-517
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 421027] wrong text rendering when installed with flatpak
https://bugs.kde.org/show_bug.cgi?id=421027 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||aa...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Albert Astals Cid --- Please attach screenshots and file used for those screenshots -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421040] Mouse warp effect can't be disabled
https://bugs.kde.org/show_bug.cgi?id=421040 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Severity|normal |wishlist --- Comment #3 from Albert Astals Cid --- As a data point, you're the first person to ever complain about this feature in something like the 15 years we've had it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421028] allow for text selection during review/annotations
https://bugs.kde.org/show_bug.cgi?id=421028 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421080] New: Duplicated if branches in KoTableCellStyle.cpp
https://bugs.kde.org/show_bug.cgi?id=421080
Bug ID: 421080
Summary: Duplicated if branches in KoTableCellStyle.cpp
Product: krita
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: mikrutra...@protonmail.com
Target Milestone: ---
```
}
if (styleStack.hasProperty(KoXmlNS::style, "repeat-content")) {
setRepeatContent(styleStack.property(KoXmlNS::style, "repeat-content")
== "true");
}
if (styleStack.hasProperty(KoXmlNS::style, "repeat-content")) {
setRepeatContent(styleStack.property(KoXmlNS::style, "repeat-content")
== "true");
}
```
https://invent.kde.org/kde/krita/-/blob/master/plugins/flake/textshape/kotext/styles/KoTableCellStyle.cpp#L675-681
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 421079] New: Array is used before checking index
https://bugs.kde.org/show_bug.cgi?id=421079 Bug ID: 421079 Summary: Array is used before checking index Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mikrutra...@protonmail.com Target Milestone: --- ``` while (d->effectiveZoom > d->sliderLookup[i] - eps && i < d->sliderLookup.size() - 1) i++; ``` https://invent.kde.org/kde/krita/-/blob/master/libs/widgets/KoZoomAction.cpp#L236 -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 421078] New: [V 3.2.0] Toolbar status is not saved
https://bugs.kde.org/show_bug.cgi?id=421078 Bug ID: 421078 Summary: [V 3.2.0] Toolbar status is not saved Product: karbon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ja...@gmx.net Reporter: jsar...@gmail.com Target Milestone: --- I add toolbars to Karbon that are by default disabled and they are not remembered This happens when opening Karbon and enabling the toolbar in the main script as well as when opening a file and enabling Objects, Align and Effects toolbars -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 421077] New: Akonadi crashes after almost any boot
https://bugs.kde.org/show_bug.cgi?id=421077 Bug ID: 421077 Summary: Akonadi crashes after almost any boot Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: peter.huy...@gmx.de Target Milestone: --- Application: akonadiserver (5.14.0 (20.04.0)) Qt Version: 5.14.1 Frameworks Version: 5.69.0 Operating System: Linux 5.6.8-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Since last OpenSuse Tumbleweed-Update Akonadi crashes after almost any boot. A handful restarts of akonadi later KMail runs normal. The crash can be reproduced every time. -- Backtrace (Reduced): #6 0x7ff2524c1544 in QSqlResult::~QSqlResult (this=, __in_chrg=) at ../../include/QtCore/../../src/corelib/tools/qhash.h:601 #7 0x7ff24d2344eb in QMYSQLResult::~QMYSQLResult (this=0x7ff204003a60, __in_chrg=) at qsql_mysql.cpp:457 #8 QMYSQLResult::~QMYSQLResult (this=0x7ff204003a60, __in_chrg=) at qsql_mysql.cpp:458 #9 0x7ff2524b1562 in QSqlQueryPrivate::~QSqlQueryPrivate (this=0x7ff204048920, __in_chrg=) at kernel/qsqlquery.cpp:94 #10 0x7ff2524b1901 in QSqlQuery::~QSqlQuery (this=, __in_chrg=) at kernel/qsqlquery.cpp:248 Possible duplicates by query: bug 376822. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421076] New: Identical expressions in KoToolBase.cpp
https://bugs.kde.org/show_bug.cgi?id=421076
Bug ID: 421076
Summary: Identical expressions in KoToolBase.cpp
Product: krita
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: mikrutra...@protonmail.com
Target Milestone: ---
```
if (d->canvas && d->canvas->canvasController() &&
d->canvas->canvasController()) {
```
https://invent.kde.org/kde/krita/-/blob/master/libs/flake/KoToolBase.cpp#L189
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 421075] Trailing Whitespace when creating directories or files.
https://bugs.kde.org/show_bug.cgi?id=421075 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Can you explain why you think this should happen? What problem is it causing you? Bug reports that just describe a problem are usually more helpful than ones that propose a solution without explaining the problem. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 419498] gwenview is can't load current directory with %U
https://bugs.kde.org/show_bug.cgi?id=419498 --- Comment #4 from ferweer --- (In reply to Nate Graham from comment #3) > That's not going to work. :) %U is a special symbol in .desktop files that > gets replaced with a space-separated list of URLs. For your purpose, you > need to pass the list of URLs yourself, or in the script. thanks. i changed script. gwenview ./* & -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421075] New: Trailing Whitespace when creating directories or files.
https://bugs.kde.org/show_bug.cgi?id=421075 Bug ID: 421075 Summary: Trailing Whitespace when creating directories or files. Product: dolphin Version: 19.04.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: larry.j.de...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When creating a file or directory in Dolphin, if the user places a leading or trailing white space in the name, it leaves it there. Spaces in between multiple words should be honored, but all others should be stripped. STEPS TO REPRODUCE 1. Open Dolphin 2. Right click 3. Create New 4. Select any of the options 5. Enter any name with a leading or trailing white space OBSERVED RESULT // Trailing white space Creates " " // or // Leading white space Creates " " // or // Leading and trailing white space. Creates " " EXPECTED RESULT // No leading or trailing white space Creates "" SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-7648-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-10210U CPU @ 1.60GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION Dolphin Version: 19.04.3 Bug occurs in the following distributions: - Ubuntu: - 16.04, 16.10, 17.04, 17.10, 18.04, 18.10, 19.04, 19.10, 20.04 - openSUSE: - Tumbleweed, Leap 15.1 - Fedora: - 31, 32 - Arch -- 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 #22 from broekhoff.joc...@gmail.com --- I can confirm that the delay is gone with the latest packages installed (Arch). -- 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 #21 from Tim Mohlmann --- I've pulled some updates yesterday and today (Arch linux) and this included some QT libraries. Not sure which one is was the culprit. Today on reboot plasmashell started just fine and without delay :). QT version is still the same and Plasma version is still the same. This were just some minor updates. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 419675] okular crashes when opening a menu if invoked from auctex
https://bugs.kde.org/show_bug.cgi?id=419675 --- Comment #7 from Albert Astals Cid --- can't really help you with opensuse questions, sorry :/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421072] Usage of strange `= +` operators in KoOdfNumberStyles.cpp
https://bugs.kde.org/show_bug.cgi?id=421072 Tymond changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||tamtamy.tym...@gmail.com --- Comment #1 from Tymond --- That looks like a bug long time ago, someone wrote =+ instead of +=, then someone "fixed the coding style" by adding a space between them, then it was commented out because of a warning that suggested that this code won;t be executed, then someone uncommented it... Quite a weird situation. @Rafał, how did you find this bug? Also would you want to contribute a patch? That would be quite easy, I believe. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421074] New: Checking if pointers are null after using it in KoColorConversionSystem.cpp
https://bugs.kde.org/show_bug.cgi?id=421074
Bug ID: 421074
Summary: Checking if pointers are null after using it in
KoColorConversionSystem.cpp
Product: krita
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: mikrutra...@protonmail.com
Target Milestone: ---
```c
if (*srcColorSpace == *dstColorSpace) {
return new KoCopyColorConversionTransformation(srcColorSpace);
}
Q_ASSERT(srcColorSpace);
Q_ASSERT(dstColorSpace);
```
https://invent.kde.org/kde/krita/-/blob/master/libs/pigment/KoColorConversionSystem.cpp#L236-240
--
You are receiving this mail because:
You are watching all bug changes.
[kompare] [Bug 420771] CRASH after try of commit to git repository
https://bugs.kde.org/show_bug.cgi?id=420771 Milian Wolff changed: What|Removed |Added Assignee|kdevelop-bugs-n...@kde.org |kompare-de...@kde.org Product|kdevelop|kompare Version|5.5.0 |unspecified Component|general |general --- Comment #4 from Milian Wolff --- indeed, seems to be a crash in kompare -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421073] New: While loop inside bufferfragment_p.h which execute only max once
https://bugs.kde.org/show_bug.cgi?id=421073
Bug ID: 421073
Summary: While loop inside bufferfragment_p.h which execute
only max once
Product: krita
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: mikrutra...@protonmail.com
Target Milestone: ---
```c
while (*start < len) {
int end = indexOf(c, *start);
if (end == -1) {
end = len;
}
BufferFragment line(d + (*start), end - (*start));
*start = end + 1;
return line;
}
```
https://invent.kde.org/kde/krita/-/blob/master/libs/resources/bufferfragment_p.h#L92-100
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 421072] New: Usage of strange `= +` operators in KoOdfNumberStyles.cpp
https://bugs.kde.org/show_bug.cgi?id=421072 Bug ID: 421072 Summary: Usage of strange `= +` operators in KoOdfNumberStyles.cpp Product: krita Version: git master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: mikrutra...@protonmail.com Target Milestone: --- ``` format = + ',' ; ``` https://invent.kde.org/kde/krita/-/blob/master/libs/odf/KoOdfNumberStyles.cpp#L456 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 419484] wrong syntax highlighting (editor assumes math environment but it is not)
https://bugs.kde.org/show_bug.cgi?id=419484 --- Comment #5 from Nibaldo G. --- Sorry, I was wrong, this bug was fixed in ** KDE Frameworks 5.69.0 ** (not in 5.59) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Version Fixed In|5.59.0 |5.69.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #22 from Brian Wright --- Over the weekend, I discovered that my KDE user profile was corrupted. Monitor resolution changes weren't saving and SDDM was black-screening with the mouse cursor. I backed up all the user data and rebuild my home directory. I'm going to re-run the testing as I don't trust the results with the corrupted profile. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 343645] Treat archive files (.zip, .rar, ...) full of images in the same way as CBR and CBZ files
https://bugs.kde.org/show_bug.cgi?id=343645 Gaëtan Gilbert changed: What|Removed |Added CC||gaetan.gilbert@skyskimmer.n ||et --- Comment #8 from Gaëtan Gilbert --- At some point, modifying desktop files stopped working. Instead to get okular to open .zip as cbz I ended up replacing the one occurence of "cbz" by "zip" in the compiled okularGenerator_comicbook.so, which worked so I guess the source of truth moved somehow. However this stopped working with version 20 where this wild hack instead gave me segfaults (specifically the debian package at version 4:19.12.3-2 and some previous versions tolerated the hack, 4:20.04.0-1 segfaults with the hack). Even if it's not considered an acceptable default could the controls be moved back to a human editable file? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418269] folderview popup config dialog icon/list selection
https://bugs.kde.org/show_bug.cgi?id=418269 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/1d557e8a78a737b ||6c63bf2400e863738f1f063ff Resolution|--- |FIXED Version Fixed In||5.19.0 --- Comment #5 from Nate Graham --- Git commit 1d557e8a78a737b6c63bf2400e863738f1f063ff by Nate Graham, on behalf of Alexandre Pereira. Committed on 05/05/2020 at 18:46. Pushed by ngraham into branch 'master'. Fix folderview popup mode list view icon size inheriting icon view icon size Summary: The icon size is only selectable in icon view mode. but selecting a different icon size on icon view mode also changes the size of the icons in list view mode. This creates a problem since the list icon size is hardcoded by default to small, but it seems it is being changed on other places of the code. FIXED-IN: 5.19.0 Test Plan: I tested this on icon folderview and normal desktop folderview, changing icon sizes in iconview and listview and restarting plasmashell. Reviewers: #plasma, #vdg, ngraham Reviewed By: #vdg, ngraham Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D28057 M +8-0containments/desktop/package/contents/ui/FolderView.qml https://commits.kde.org/plasma-desktop/1d557e8a78a737b6c63bf2400e863738f1f063ff -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420755] Animated scroll transitions should respect global animation speed
https://bugs.kde.org/show_bug.cgi?id=420755 --- Comment #12 from nfx...@gmail.com --- Christoph Loy: I don't know. My bug was closed as duplicate of this, and it wasn't about any links at all. gwarser: Judging from the closing of my bug report, what you suggest is part of this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421039] Unwanted velocity and bounce effects / option to disable all animations
https://bugs.kde.org/show_bug.cgi?id=421039 gwar...@gmail.com changed: What|Removed |Added CC||gwar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
