[kscreenlocker] [Bug 412527] KScreenlocker gets confused when changin displays
https://bugs.kde.org/show_bug.cgi?id=412527 Jan Przybylak changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438397] Colorize mask layer is placed over the lineart layer when it's converted to paint layer.
https://bugs.kde.org/show_bug.cgi?id=438397 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #3 from Dmitry Kazakov --- The regression is caused by 424e41cf211d6953aef3e44fb8b11f1b8893e5db, which removed a lot of specific logic for colorize masks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 440057] Need to debounce multiple rfkill events.
https://bugs.kde.org/show_bug.cgi?id=440057 David Redondo changed: What|Removed |Added Component|general |general Assignee|kdelibs-b...@kde.org|now...@gmail.com Product|frameworks-kglobalaccel |frameworks-bluez-qt CC||k...@david-redondo.de --- Comment #1 from David Redondo --- Bluez I guess? https://lxr.kde.org/search?!v=kf5-qt5&_filestring=&_string=rfkill After reading the systemd pull request I am not sure if that's the right approach though requiring fixes everywhere downstream... -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417787] sshfs key exchange methods deprecated
https://bugs.kde.org/show_bug.cgi?id=417787 Robert G. Siebeck changed: What|Removed |Added CC||kde.bugzilla.2...@r123.de -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438269] Filter -> Blur has no chain button any more (no way to adjust values separately)
https://bugs.kde.org/show_bug.cgi?id=438269 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/06d2270b7 ||7c3681edfa783ab006b765c7772 ||be93 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Dmitry Kazakov --- Git commit 06d2270b77c3681edfa783ab006b765c7772be93 by Dmitry Kazakov. Committed on 21/07/2021 at 06:44. Pushed by dkazakov into branch 'master'. Fix aspect button initialization in Blur filter The bug was caused by a coincidence of four problems: 1) KoAspectButton never did initialization of the icon in the constructor, it waited for someone to call setKeepAspectRatio() to set up the icon 2) Constructor of KisWdgBlur never initialized m_halfSizeLink variable and the button. 3) [not fixed] KisWdgBlur::setConfiguration() (and a lot of other filters) just skip initializing the GUI control in case the property is absent in the configuration. Ideally, it should fall back to the default value instead. 4) KisBlurFilter::defaultConfiguration() didn't add a property for "lockAspect", so the control has never been initialized unless the user clicked on it. M +7-4libs/widgets/KoAspectButton.cpp M +1-0plugins/filters/blur/kis_blur_filter.cpp M +3-0plugins/filters/blur/kis_wdg_blur.cpp https://invent.kde.org/graphics/krita/commit/06d2270b77c3681edfa783ab006b765c7772be93 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440063] presentation mode is incompatible with video conferencing via Zoom, BigBlueButton, Webex, ...
https://bugs.kde.org/show_bug.cgi?id=440063 --- Comment #5 from Wolfgang Ertel --- I am using KDE-Plasma-Version 5.18.5 --- Prof. Dr. Wolfgang Ertel http://www.hs-weingarten.de/~ertel Institut für Künstliche Intelligenz http://iki.hs-weingarten.de Hochschule Ravensburg-Weingarten Email: er...@hs-weingarten.de Postfach 3022, D-88216 Weingartenhttps://www.scientists4future.org Tel: +49-751-501-9721 oder +49-751-501-9870privat: +49-751-553814 --- Am 20.07.21 um 23:05 schrieb Albert Astals Cid: > https://bugs.kde.org/show_bug.cgi?id=440063 > > Albert Astals Cid changed: > >What|Removed |Added > > CC||aa...@kde.org > > --- Comment #4 from Albert Astals Cid --- > Are you using Plasma Wayland or Plasma X11? > -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 432578] Missing space after a '.'
https://bugs.kde.org/show_bug.cgi?id=432578 --- Comment #11 from Urs Fleisch --- KDE maintains its own Qt 5.15 releases with a patch collection, see https://dot.kde.org/2021/04/06/announcing-kdes-qt-5-patch-collection. Probably the bug is fixed in their version of Qt 5.15. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 402363] File mode always set to 0600 when saving changes
https://bugs.kde.org/show_bug.cgi?id=402363 --- Comment #8 from szecsodimlaszlo --- Another year has past… Is there any progress on this bug? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437288] After a color adjustment the filter mask layer is inverted. (black)
https://bugs.kde.org/show_bug.cgi?id=437288 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/c62ee0b25 ||647d3e61181c3dafff6b5b398f1 ||f3a9 Status|CONFIRMED |RESOLVED --- Comment #11 from Dmitry Kazakov --- Git commit c62ee0b25647d3e61181c3dafff6b5b398f1f3a9 by Dmitry Kazakov. Committed on 21/07/2021 at 06:04. Pushed by dkazakov into branch 'master'. Fix "Create Filter Mask" option to work in Instant Preview mode When filter dialog works in instant preview mode, we should wait until the stroke is fully cancelled before creating a mask, otherwise the mask will be initialized in IP mode only. M +6-1libs/ui/dialogs/kis_dlg_filter.cpp https://invent.kde.org/graphics/krita/commit/c62ee0b25647d3e61181c3dafff6b5b398f1f3a9 -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 432578] Missing space after a '.'
https://bugs.kde.org/show_bug.cgi?id=432578 --- Comment #10 from Vladimir Oleynik --- Created attachment 140229 --> https://bugs.kde.org/attachment.cgi?id=140229&action=edit Comparison of the latest version and the latest nightly build (#242) Looks like bug was fixed in last nightly build (#242) https://binary-factory.kde.org/job/Kid3_Nightly_macos/242/ -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437288] After a color adjustment the filter mask layer is inverted. (black)
https://bugs.kde.org/show_bug.cgi?id=437288 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #10 from Dmitry Kazakov --- The problem is in the fact that the filter mask is created while Instant Preview mode is still active. In Krita 5.0 Instant Preview mode is forced for filters by default. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440098] New: the quick brush selection tool is cut off at 150% system zoom
https://bugs.kde.org/show_bug.cgi?id=440098 Bug ID: 440098 Summary: the quick brush selection tool is cut off at 150% system zoom Product: krita Version: 4.4.5 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Tools/Selection Assignee: krita-bugs-n...@kde.org Reporter: godlyth...@gmail.com Target Milestone: --- Created attachment 140228 --> https://bugs.kde.org/attachment.cgi?id=140228&action=edit I don't know what it is called but it is the tool that comes up when I want to quickly select a brush and color, and I cannot see the whole thing since it is so big and cannot fit on the whole screen SUMMARY the quick brush selection tool is cut off at 150% system zoom STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT at 150% system zoom some of the UI elements in the quick brush selection tool cannot be reached because it is too big to have all the buttons in reach EXPECTED RESULT The quick brush selection tool shrinks or enlarges depending on the system zoom SOFTWARE/OS VERSIONS Windows: 19043.1110 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION It can be worked around when reducing the system zoom to 125%, but then it makes the UI elements really difficult to see since the text is so small on a smaller screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440097] New: KDE randomly slowly respond to key press
https://bugs.kde.org/show_bug.cgi?id=440097 Bug ID: 440097 Summary: KDE randomly slowly respond to key press Product: plasmashell Version: 5.20.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: linn...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 140226 --> https://bugs.kde.org/attachment.cgi?id=140226&action=edit case1 SUMMARY My previous system with KDE 5.12 or 5.15 do not have problem. It randomly happens, when I press some keys, such as Alt+TAB to switch between Kwrite to Vivaldi browser, then instead of Vivaldi window is active, TAB is wrote down in KWrite. It randomly happens so I can't exactly reproduce the bug but for particular situation the bug seems to appear frequently. Case 1: Alt+TAB, it's random, but as you can see on video, where I use 'ScreenKey' to capture key press, Alt+TAB are pressed but no windows switching. Case 2: I could reproduce the situation where KDE does not respond with key press. Note1: It happens even with KDE+openbox instead of kwin. Note2: It does not happens with KDE Plasma 5.12, so it's not TimeSlotTracker's problem (the program I used in this experiment below). Download TimeSlotTracker here: https://sourceforge.net/projects/timeslottracker/ STEPS TO REPRODUCE 1. Open TimeSlotTracker 2. Create new task 3. F2 to edit task 4. Esc to close the edit window, then immediately press some key (Alt+TAB, Alt+F2,..., etc.). In the video I press Alt+F2. OBSERVED RESULT Both TimeSlotTracker edit window and Krunner appear. EXPECTED RESULT Only Krunner is activate. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440005] Long Render Time turning Layer-visibility
https://bugs.kde.org/show_bug.cgi?id=440005 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 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.
[Discover] [Bug 439496] Discover crashes with failed assertion
https://bugs.kde.org/show_bug.cgi?id=439496 --- 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.
[kscreenlocker] [Bug 415112] Blank notification appears on lid up on Wayland
https://bugs.kde.org/show_bug.cgi?id=415112 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 436991] No colour palette
https://bugs.kde.org/show_bug.cgi?id=436991 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396202] Password can not be entered after connecting HDMI
https://bugs.kde.org/show_bug.cgi?id=396202 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414389] kscreenlocker_greeter segfaults when docking/undocking
https://bugs.kde.org/show_bug.cgi?id=414389 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 385321] Screen locker 'unable to unlock, use loginctl instead' randomly when system is locked
https://bugs.kde.org/show_bug.cgi?id=385321 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 415854] kscreenlocker_greet crashes when setting video(qml) wallpaper
https://bugs.kde.org/show_bug.cgi?id=415854 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432167] [Systemd]User has to click into the password field to be able to enter their password
https://bugs.kde.org/show_bug.cgi?id=432167 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 392442] Kscreenlocker keyboard layout selection issue.
https://bugs.kde.org/show_bug.cgi?id=392442 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440042] Window > New view > Close both documents > Crash
https://bugs.kde.org/show_bug.cgi?id=440042 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.
[plasmashell] [Bug 440097] KDE randomly slowly respond to key press
https://bugs.kde.org/show_bug.cgi?id=440097 --- Comment #2 from linn...@gmail.com --- Other person has the same issue! https://forum.kde.org/viewtopic.php?f=309&t=171976&p=447499&hilit=keyboard -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440097] KDE randomly slowly respond to key press
https://bugs.kde.org/show_bug.cgi?id=440097 --- Comment #1 from linn...@gmail.com --- Created attachment 140227 --> https://bugs.kde.org/attachment.cgi?id=140227&action=edit case2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416683] Samba shares tree is flat in Dolphin
https://bugs.kde.org/show_bug.cgi?id=416683 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 424737] Lock screen resets wallpaper to default when wallpaper type is changed
https://bugs.kde.org/show_bug.cgi?id=424737 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 424854] Some keyboard events can bypass lock screen
https://bugs.kde.org/show_bug.cgi?id=424854 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413442] kscreenlocker crashes after several hours of idle time
https://bugs.kde.org/show_bug.cgi?id=413442 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 396306] wayland: in dual screen, unlocking is possible only on one monitor
https://bugs.kde.org/show_bug.cgi?id=396306 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 360421] After waking from standby mouse clicks and keyboard input doesn't reach kscreenlocker or other applications, session kill necessary
https://bugs.kde.org/show_bug.cgi?id=360421 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #12 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 439466] Latte dock does not start up correctly at Plasma desktop startup
https://bugs.kde.org/show_bug.cgi?id=439466 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 437599] Display configuration shows mismatch between resolution
https://bugs.kde.org/show_bug.cgi?id=437599 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439267] Frequent freezes since switching to Wayland
https://bugs.kde.org/show_bug.cgi?id=439267 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415194] Search in folder with from here shows results from other folders
https://bugs.kde.org/show_bug.cgi?id=415194 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 431876] Can't update themes using Discover on OpenSUSE Tumbleweed
https://bugs.kde.org/show_bug.cgi?id=431876 --- 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.
[kscreenlocker] [Bug 412527] KScreenlocker gets confused when changin displays
https://bugs.kde.org/show_bug.cgi?id=412527 --- 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.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 --- Comment #20 from Cane Kostovski --- Created attachment 140225 --> https://bugs.kde.org/attachment.cgi?id=140225&action=edit Journal entries during a single boot Jul 20 23:33:17 is when I started KScreenLocker, Turned Off My TV, And Turned it back on to see the problem -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 350798] Okular opens large PDFs very slowly
https://bugs.kde.org/show_bug.cgi?id=350798 --- Comment #26 from 2wxsy5823...@opayq.com --- There is a way to use MuPDF as backend in Okular, [1] and it can render the pages in the test document (Intel's System Programming Guide) very quickly. [1] https://github.com/gustawho/okular-backend-mupdf -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438546] Configuring kdenlive bug
https://bugs.kde.org/show_bug.cgi?id=438546 2wxsy5823...@opayq.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #8 from 2wxsy5823...@opayq.com --- Closing this since this is not a bug (Comment 6). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440096] Add option for vertical layout in Digital Clock
https://bugs.kde.org/show_bug.cgi?id=440096 --- Comment #1 from farid --- Created attachment 140224 --> https://bugs.kde.org/attachment.cgi?id=140224&action=edit Digital clock in vertical panel -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440096] New: Add option for vertical layout in Digital Clock
https://bugs.kde.org/show_bug.cgi?id=440096 Bug ID: 440096 Summary: Add option for vertical layout in Digital Clock Product: plasmashell Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: snd.no...@gmail.com Target Milestone: 1.0 SUMMARY When the panel is in vertical layout, the clock becomes illegible. Adding a vertical option to display the hours above the minutes would be very handy. (See attachment.) STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT No way to change layout. EXPECTED RESULT Have option in the Digital Clock to have a vertical layout. SOFTWARE/OS VERSIONS (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440095] No support for "dc cvac" and "dc cvap" on Arm64
https://bugs.kde.org/show_bug.cgi?id=440095 kevinz changed: What|Removed |Added CC||assad.has...@linaro.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 440095] New: No support for "dc cvac" and "dc cvap" on Arm64
https://bugs.kde.org/show_bug.cgi?id=440095 Bug ID: 440095 Summary: No support for "dc cvac" and "dc cvap" on Arm64 Product: valgrind Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: kevin.z...@linaro.org Target Milestone: --- We are working on enabling PMDK for Arm64, which is the persist memory development kit. Running the test with valgrind, I experienced a valgrind error: ==256557== Memcheck, a memory error detector ==256557== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==256557== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==256557== Command: ./obj_basic_integration /mnt/mem0//test_obj_basic_integration5__PMDK_/testfile1 ==256557== Parent PID: 256503 ==256557== ARM64 front end: branch_etc disInstr(arm64): unhandled instruction 0xD50B7A20 disInstr(arm64): 1101'0101 '1011 0111'1010 0010' ==256557== valgrind: Unrecognised instruction at address 0x493a148. ==256557==at 0x493A148: arm_clean_va_to_poc (arm_cacheops.h:55) ==256557==by 0x493A3BB: flush_poc_nolog (flush.h:27) ==256557==by 0x493A3BB: flush_poc (init.c:33) ==256557==by 0x4934C2F: pmem_deep_flush (pmem.c:214) ==256557==by 0x48A8037: os_part_deep_common (os_deep_linux.c:136) ==256557==by 0x48B672B: shutdown_state_checksum (shutdown_state.c:32) ==256557==by 0x48B678B: shutdown_state_init (shutdown_state.c:47) ==256557==by 0x48AFE23: util_header_create (set.c:2313) ==256557==by 0x48B15A3: util_replica_init_headers_local (set.c:2777) ==256557==by 0x48B17BB: util_replica_create_local (set.c:2823) ==256557==by 0x48B2FEF: util_pool_create_uuids (set.c:3313) ==256557==by 0x48B31C3: util_pool_create (set.c:3356) ==256557==by 0x48D49DB: pmemobj_createU (obj.c:1351) ==256557== Your program just tried to execute an instruction that Valgrind ==256557== did not recognise. There are two possible reasons for this. ==256557== 1. Your program has a bug and erroneously jumped to a non-code ==256557==location. If you are running Memcheck and you just saw a ==256557==warning about a bad jump, it's probably your program's fault. ==256557== 2. The instruction is legitimate but Valgrind doesn't handle it, ==256557==i.e. it's Valgrind's fault. If you think this is the case or ==256557==you are not sure, please let us know and we'll try to fix it. ==256557== Either way, Valgrind will now raise a SIGILL signal which will ==256557== probably kill your program. ==256557== ==256557== HEAP SUMMARY: ==256557== in use at exit: 3,039 bytes in 39 blocks ==256557== total heap usage: 1,220 allocs, 1,181 frees, 1,653,499 bytes allocated ==256557== ==256557== LEAK SUMMARY: ==256557==definitely lost: 0 bytes in 0 blocks ==256557==indirectly lost: 0 bytes in 0 blocks ==256557== possibly lost: 0 bytes in 0 blocks ==256557==still reachable: 3,039 bytes in 39 blocks ==256557== suppressed: 0 bytes in 0 blocks ==256557== Reachable blocks (those to which a pointer was found) are not shown. ==256557== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==256557== ==256557== For lists of detected and suppressed errors, rerun with: -s ==256557== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) The one above will call: https://github.com/pmem/pmdk/blob/master/src/libpmem2/aarch64/arm_cacheops.h#L53, but Valgrind can not handle it. Also, the other one as below with "dc cvap" also got the same consequence. The dc cvap was called at: https://github.com/pmem/pmdk/blob/master/src/libpmem2/aarch64/arm_cacheops.h#L59 [root@fedora obj_basic_integration]# cat memcheck5.log ==261736== Memcheck, a memory error detector ==261736== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==261736== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info ==261736== Command: ./obj_basic_integration /mnt/mem0//test_obj_basic_integration5__PMDK_/testfile1 ==261736== Parent PID: 261682 ==261736== ARM64 front end: branch_etc disInstr(arm64): unhandled instruction 0xD50B7C20 disInstr(arm64): 1101'0101 '1011 0111'1100 0010' ==261736== valgrind: Unrecognised instruction at address 0x493a164. ==261736==at 0x493A164: arm_clean_va_to_pop (arm_cacheops.h:61) ==261736==by 0x493A453: flush_pop_nolog (flush.h:45) ==261736==by 0x493A453: flush_pop (init.c:49) ==261736==by 0x4934C2F: pmem_deep_flush (pmem.c:214) ==261736==by 0x48A8037: os_part_deep_common (os_deep_linux.c:136) ==261736==by 0x48B672B: shutdown_state_checksum (shutdown_state.c:32) ==261736==by 0x48B678B: shutdown_state_init (shutdown_state.c:47) ==261736==by 0x48AFE23: util_header_create (set.c:2313) ==261736==by 0x48B15A3: util_replica_ini
[kwin] [Bug 440094] Intermittent Kwin crash on wayland
https://bugs.kde.org/show_bug.cgi?id=440094 --- Comment #2 from ha...@dayfamilyweb.com --- It also looks similar to https://bugs.kde.org/show_bug.cgi?id=437709 but has a different stack trace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440094] Intermittent Kwin crash on wayland
https://bugs.kde.org/show_bug.cgi?id=440094 --- Comment #1 from ha...@dayfamilyweb.com --- Created attachment 140223 --> https://bugs.kde.org/attachment.cgi?id=140223&action=edit journalctl logs attached journalctl logs around time of failure -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440094] New: Intermittent Kwin crash on wayland
https://bugs.kde.org/show_bug.cgi?id=440094 Bug ID: 440094 Summary: Intermittent Kwin crash on wayland Product: kwin Version: 5.22.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ha...@dayfamilyweb.com Target Milestone: --- Created attachment 140222 --> https://bugs.kde.org/attachment.cgi?id=140222&action=edit Kwin core dump SUMMARY Hi there I have a reoccurring bug where kwin will crash on wayland. This crash then causes all x11 programs to crash (firefox running in X11 mode, spotify) and also all of plasma (producing lots of "Dr Konqi" windows). Sometimes its possible to reopen the application after, other times a full restart happens. It happens fairly regularly (once a day or so), but doesn't seem to be caused by any specific action and I can't see any logs that look suspicious. STEPS TO REPRODUCE 1. Run kwin in native wayland mode 2. Wait for it to crash OBSERVED RESULT Kwin crashes, as does firefox, spotify and all of plasma. Other applications seem to survive (e.g. system monitor). EXPECTED RESULT It shouldn't crash SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-22-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440093] [Crash] Animation Curves: Adding opacity key.
https://bugs.kde.org/show_bug.cgi?id=440093 Emmet O'Neill changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440093] [Crash] Animation Curves: Adding opacity key.
https://bugs.kde.org/show_bug.cgi?id=440093 Emmet O'Neill changed: What|Removed |Added Keywords||release_blocker Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 440093] New: [Crash] Animation Curves: Adding opacity key.
https://bugs.kde.org/show_bug.cgi?id=440093 Bug ID: 440093 Summary: [Crash] Animation Curves: Adding opacity key. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: emmetoneill@gmail.com Target Milestone: --- Just taking a personal note of a regression crash that popped up tonight with opacity keys in the curves docker. Backtrace: efd22 in raise () from /usr/lib/libc.so.6 #1 0x71cd9862 in abort () from /usr/lib/libc.so.6 #2 0x722a7910 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/libQt5Core.so.5 #3 0x722a6cf5 in qt_assert(char const*, char const*, int) () from /usr/lib/libQt5Core.so.5 #4 0x758178fc in KisKeyframeChannel::currentTime() const [clone .cold] () at /usr/include/c++/11.1.0/bits/atomic_base.h:385 #5 0x75902197 in KisScalarKeyframeChannel::currentValue (this=0x582bc950) at /home/eoin/Source/krita/src/libs/image/kis_scalar_keyframe_channel.h:138 #6 KisAnimatedOpacityProperty::get (this=0x62da2e68) at /home/eoin/Source/krita/src/libs/image/KisAnimatedOpacityProperty.cpp:23 #7 0x759eb9cd in KisBaseNode::opacity (this=) at /home/eoin/Source/krita/src/libs/image/kis_base_node.cpp:114 #8 0x75aff6de in KisProjectionLeaf::opacity (this=0x62f45ae0) at /home/eoin/Source/krita/src/libs/image/kis_projection_leaf.cpp:296 #9 0x75addb23 in KisLayerProjectionPlane::applyImpl (this=, painter=, rect=..., maxOutAlpha=) at /usr/include/qt/QtCore/qsharedpointer_impl.h:301 #10 0x75a666b8 in KisAsyncMerger::compositeWithProjection (rect=..., leaf=..., this=0x7fff3c83bb30) at /home/eoin/Source/krita/src/libs/image/kis_async_merger.cpp:358 #11 KisAsyncMerger::startMerge (this=0x7fff3c83bb30, walker=..., notifyClones=) at /home/eoin/Source/krita/src/libs/image/kis_async_merger.cpp:282 #12 0x75ad04fc in KisRegenerateFrameStrokeStrategy::doStrokeCallback (this=, data=) at /home/eoin/Source/krita/src/libs/global/kis_shared_ptr.h:158 #13 0x758a6d10 in KisStrokeJob::run (this=) at /home/eoin/Source/krita/build/libs/image/kritaimage_autogen/EWIEGA46WW/../../../../../src/libs/image/kis_stroke_job.h:32 #14 KisUpdateJobItem::run (this=0x62c54160) at /home/eoin/Source/krita/build/libs/image/kritaimage_autogen/EWIEGA46WW/../../../../../src/libs/image/kis_update_job_item.h:90 #15 0x722e82f2 in ?? () from /usr/lib/libQt5Core.so.5 #16 0x722e4fef in ?? () from /usr/lib/libQt5Core.so.5 #17 0x71e8a259 in start_thread () from /usr/lib/libpthread.so.0 #18 0x71db15e3 in clone () from /usr/lib/libc.so.6 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 294595] event recurrent move one of them to another day doesn't work
https://bugs.kde.org/show_bug.cgi?id=294595 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||gjditchfi...@acm.org Status|CONFIRMED |NEEDSINFO --- Comment #7 from gjditchfi...@acm.org --- Does this corrupted dialog still appear? If so, could you attach a screenshot? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 290257] Usability improvement: Integrate editor functionality into incident viewer
https://bugs.kde.org/show_bug.cgi?id=290257 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- The To-do List now lets the user edit most fields directly in the list. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 --- Comment #19 from Cane Kostovski --- How do I get debug info from kscreenlocker? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 --- Comment #18 from Cane Kostovski --- Operating System: openSUSE Tumbleweed 20210718 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.2-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 284689] Calendar plasmoid show some entries with wrong start/end times
https://bugs.kde.org/show_bug.cgi?id=284689 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||gjditchfi...@acm.org --- Comment #5 from gjditchfi...@acm.org --- This is not a KOrganizer problem. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 283273] Korganizer needs the ability to print to Dayrunner ot Daytimer formatted pages
https://bugs.kde.org/show_bug.cgi?id=283273 gjditchfi...@acm.org changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED --- Comment #5 from gjditchfi...@acm.org --- This would need the ability to specify different margins for even and odd pages (to leave room for the punch holes) and to reorder pages so they can be folded into a "signature". Some PDF and PostScript utilities can do that; KDE can't. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440092] New: Driver Updates cause KDE tools to crash.
https://bugs.kde.org/show_bug.cgi?id=440092 Bug ID: 440092 Summary: Driver Updates cause KDE tools to crash. Product: systemsettings Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ayden.koc...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Just updated my PC, Nvidia drivers were included in the update. I've noticed that whenever I update my drivers, random KDE tools crash repetedly. For example, the system settings and logout splashscreen after pressing shutdown will crash. Then, I have to reboot my computer through terminal to shutdown my computer. Luckily, after a reboot everything is fixed and back to normal. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f546cc36800 (LWP 64926))] Thread 5 (Thread 0x7f5457fff700 (LWP 64932)): #0 0x7f5470b4daff in __GI___poll (fds=0x7f54500029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f546ee2336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f546ee234a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54710ea583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f54710914db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5470ec9785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f547017b1a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f5470eca9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f546f707609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5470b5a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f5461f4f700 (LWP 64931)): #0 0x7f546ee70508 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f546ee228e1 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f546ee2329b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f546ee234a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f54710ea583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f54710914db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5470ec9785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f547017b1a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f5470eca9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f546f707609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f5470b5a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f546ae0b700 (LWP 64929)): #0 0x7f5470b4daff in __GI___poll (fds=0x7f545c0029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f546ee2336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f546ee234a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54710ea583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f54710914db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5470ec9785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f547136cefa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5470eca9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f546f707609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5470b5a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f546bd83700 (LWP 64928)): #0 0x7f5470b4daff in __GI___poll (fds=0x7f546bd82ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f546f6c4c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f546f6c690a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f546c58e298 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f5470eca9d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f546f707609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f5470b5a293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f546cc36800 (LWP 64926)): [KCrash Handler] #6 __GI
[frameworks-khtml] [Bug 440091] New: htmlparser doctypes.gperf ISO C++17 does not allow 'register' storage class specifier
https://bugs.kde.org/show_bug.cgi?id=440091 Bug ID: 440091 Summary: htmlparser doctypes.gperf ISO C++17 does not allow 'register' storage class specifier Product: frameworks-khtml Version: unspecified Platform: MacPorts Packages OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: kurt.hindenb...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- I build KF5 from current source. This is the first git change that doesn't build 8540c72b29cc48e9e6ba14807e4e6180e3f62fce which is confusing to me. I would have assume it as the 2 earlier registry changes that would have caused it: 9901089fd067b361583b165727ff56107dcd3b87 and b8a1f65d07c58f57e83f2a50344a374de137410b AppleClang 12.0.5.12050022; In file included from /Volumes/Devel/KDE/src/frameworks/khtml/src/html/htmlparse r.cpp:67: /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:33:21: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] Perfect_Hash::hash (register const char *str, register unsigned int len) ^ /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:33:47: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] Perfect_Hash::hash (register const char *str, register unsigned int len) ^ /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:64:3: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] register unsigned int hval = len; ^ /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:313:33: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] Perfect_Hash::findDoctypeEntry (register const char *str, register unsigned int len) /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:313:33: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] Perfect_Hash::findDoctypeEntry (register const char *str, register unsigned int len) ^ /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:313:59: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] Perfect_Hash::findDoctypeEntry (register const char *str, register unsigned int len) ^ /Volumes/Devel/KDE/src/frameworks/khtml/src/html/doctypes.gperf:81:11: error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] register const char *s = wordlist[key].name; ^ -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 282919] For trashed items, show the path to the actual file/folder on the disk in the properties dialog
https://bugs.kde.org/show_bug.cgi?id=282919 Ahmad Samir changed: What|Removed |Added Summary|Opening terminal (F4) in|For trashed items, show the |Trash starts a terminal in |path to the actual |wrong location because |file/folder on the disk in |trash:/ returns nothing in |the properties dialog |response to | |KIO::mostLocalUrl() | -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 282919] Opening terminal (F4) in Trash starts a terminal in wrong location because trash:/ returns nothing in response to KIO::mostLocalUrl()
https://bugs.kde.org/show_bug.cgi?id=282919 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #9 from Ahmad Samir --- There is no way to fix this, because kio_trash is a view on all the physical trash directories: ~/.local/share/Trash - the default trash dir, when you delete something from $HOME, that's where it goes; also used as fallback /path/to-another-partition-mount-point/.Trash-$UID - if you delete something from /path/to-another-partition-mount-point/ it's moved to that dir (moving trashed items to a dir on the same partition is much faster vs moving them to ~/.local/share/Trash (which is on another partition/disk). We could maybe improve the situation by showing the actual path to the trash dir where a trashed item resides in e.g. the properties dialog, so the user can delete the file manually from terminal ...etc. This will leave the corresponding .trashinfo (e.g. ~/.local/share/Trash/info/foo.trashinfo file behind, that gets cleaned up when you use the trash the next time). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440088] New: With multiple screens widgets change around randomly and backgrounds are lost
https://bugs.kde.org/show_bug.cgi?id=440088 Bug ID: 440088 Summary: With multiple screens widgets change around randomly and backgrounds are lost Product: plasmashell Version: 5.22.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: ericsbinarywo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have 4 monitors hooked up to my Linux computer running KDE Plasma 5 on Fedora 34. 2 monitors are DP and 2 are HDMI. When I turn monitors off and then back on, the widgets show up randomly on different screens. Also, some of the monitors lose their background. It either becomes black or the default KDE background for 5.22.3 - looks like a geometric mountain and lake. STEPS TO REPRODUCE 1. Have multiple monitors connected 2. set up your plasmoids and desktop backgrounds per screen 3. Turn off the screens 4. Turn the screens back on OBSERVED RESULT Widgets have moved to a random monitor and backgrounds are all messed up EXPECTED RESULT For things to remain where I put them SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 KDE Plasma 5.22.3 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel versio: 5.12.15-300 Graphics Platform: Wayland Processor: 8 x AMD FX-8320 Memory: 24 GB Graphics: Radeon RX 580 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440090] New: Configure Desktop and Wallpaper should be in System Settings
https://bugs.kde.org/show_bug.cgi?id=440090 Bug ID: 440090 Summary: Configure Desktop and Wallpaper should be in System Settings Product: plasmashell Version: 5.22.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: skierp...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After Plasma reset my external monitor's wallpaper and layout settings (bug 427861), I needed to change them back. So I launched System Settings, and... spent several minutes searching for "desktop", "wallpaper", folder", then browsing through all the plausible categories in the left-hand navigation. Nothing!? I remembered that these settings are per-display, so I found Display Configuration in System Settings and tried to access them here. Nope! Obviously the workaround is to right-click on the desktop on the display you want to configure, and choose Configure Desktop and Wallpaper... But there is no good reason for this not to be accessible from System Settings. STEPS TO REPRODUCE 1. Launch System Settings and try to find the layout (Desktop or Folder View) and Wallpaper for your display(s). OBSERVED RESULT You can't, Desktop Settings are not in System Settings. When you do find Desktop Settings, it looks like everything else in System Settings, so months later when you need to fix them again, you look in System Settings. EXPECTED RESULT These should be in System Settings along with (almost) everything else. If the counter-argument is that these are per-display settings, a) Display Configuration is in System Settings. You could have an affordance to launch these settings from the monitor display gadget that shows the display layout or reuse the monitor display gadget in Desktop Settings to launch the desktop settings for each display. b) I _don't_ want these settings to be per-display. I would love to be able to see them listed for each display one after the other, and have an "Apply to all displays" button, or have a toggle "Different settings for each display" that when unchecked only shows the single global settings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 34 KDE spin KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 on Wayland ADDITIONAL INFORMATION There _is_ a wallpaper chooser in System Settings, in Screen Locking > Appearance Configure... > Wallpaper type. But not for the desktop. Until Desktop Settings is available in System Settings, there could be some help text guiding users to them, e.g. a hack adding to Display Configuration the text "To set a display's desktop layout and wallpaper, right-click on the display's background to bring up its context menu and choose Configure Desktop and Wallpaper..." and make System Settings show this panel when you search it for terms like Folder and Wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440089] New: python syntax highlighting breaks with binary strings
https://bugs.kde.org/show_bug.cgi?id=440089 Bug ID: 440089 Summary: python syntax highlighting breaks with binary strings Product: kate Version: 21.04.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: shit...@gmail.com Target Milestone: --- Created attachment 140221 --> https://bugs.kde.org/attachment.cgi?id=140221&action=edit screenshot of issue SUMMARY Binary string highlighting affects the entire file after the string ends. So if strings are highlighted red, typing `b"test"` will cause all text after that to appear red note that the code runs as expected, so its not a syntax error STEPS TO REPRODUCE 1. Open python file in kate 2. Add a line like print(b"test") to the file OBSERVED RESULT All text after the binary string is highlighted the same color as the string (changing the color doesn't affect the bug) EXPECTED RESULT the color should revert back to normal after closing quote SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION note that I am using Qtile as a standalone WM but still have a full KDE environment installed but not in use. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440078] Support disabling updates on live system
https://bugs.kde.org/show_bug.cgi?id=440078 Neal Gompa changed: What|Removed |Added CC||ngomp...@gmail.com --- Comment #1 from Neal Gompa --- Discover can "discover" (lol) from the kernel command-line whether or not we're running on live OSes by looking at kernel args to see if "rd.live.image" is in the kernel command-line. Discover can self-disable by default when that is present in the kernel command line. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 422033] Break never counts down to zero in Wayland
https://bugs.kde.org/show_bug.cgi?id=422033 Eric Mesa changed: What|Removed |Added CC||ericsbinarywo...@gmail.com --- Comment #5 from Eric Mesa --- Adding that this also happens on Fedora 34 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440087] New: Properties sum up file sizes wrong with symlinks
https://bugs.kde.org/show_bug.cgi?id=440087 Bug ID: 440087 Summary: Properties sum up file sizes wrong with symlinks Product: dolphin Version: 21.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: hugojm...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140220 --> https://bugs.kde.org/attachment.cgi?id=140220&action=edit This is a screenshot of the wrong sum. SUMMARY Properties sum up file sizes wrong with symlinks STEPS TO REPRODUCE 1. Select all files in root 2. Right click and select properties 3. Observe the reported size OBSERVED RESULT Total size reported is an unrealistically high number. (128,3 TiB reported in this case) EXPECTED RESULT Total size to match what filelight would report. (392,4 GiB in this case) SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I have a 1TB nvme ssd and a 512GB sata hdd, only the ssd has anything and it's about 40% full. The 100+ TiB figure is impossible for this hardware. Using EndeavourOS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411884] In wayland BorderlessMaximizedWindows can cause window to not receive input
https://bugs.kde.org/show_bug.cgi?id=411884 Andrey changed: What|Removed |Added Status|CONFIRMED |ASSIGNED URL||https://invent.kde.org/plas ||ma/kwin/-/merge_requests/11 ||67 --- Comment #10 from Andrey --- I don't know why the fixes didn't get posted here, added manually: https://invent.kde.org/plasma/kwin/-/merge_requests/1167 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 280571] Ctrl+Click in the Location Bar should open in a new tab
https://bugs.kde.org/show_bug.cgi?id=280571 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ahmad Samir --- I've just tested and this seems to work now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 440084] exr.cpp/OpenEXR virtual function tellg error
https://bugs.kde.org/show_bug.cgi?id=440084 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kimageformats/commit ||/fbeef559b771af16c8e9221ca4 ||7691c569b16bb3 Status|REPORTED|RESOLVED --- Comment #4 from Albert Astals Cid --- Git commit fbeef559b771af16c8e9221ca47691c569b16bb3 by Albert Astals Cid. Committed on 20/07/2021 at 22:04. Pushed by aacid into branch 'master'. exr: Repair compability with openexr2 M +13 -0src/imageformats/exr.cpp https://invent.kde.org/frameworks/kimageformats/commit/fbeef559b771af16c8e9221ca47691c569b16bb3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 272361] Unavailable mounts that are Places entries make clients displaying a Places panel (e.g. Dolphin, Gwenview, file open or save dialogs) hang or become extremely slow
https://bugs.kde.org/show_bug.cgi?id=272361 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #18 from Ahmad Samir --- IIUC there are two different Places panels, one from KIO (which is used in e.g. the open file dialog that you can invoke from kwrite or kate), and one from Dolphin, do both have the issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 440084] exr.cpp/OpenEXR virtual function tellg error
https://bugs.kde.org/show_bug.cgi?id=440084 --- Comment #3 from Albert Astals Cid --- Can you check if https://invent.kde.org/frameworks/kimageformats/-/merge_requests/34 helps? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 439424] [clipboard] wish: workaround to send clipboard from phone to desktop
https://bugs.kde.org/show_bug.cgi?id=439424 Holger changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Holger --- Great - haven't seen that before, as you need to unfold the notification. But it perfectly fits my wish :D So I resolve as works for me. Thanks -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440086] New: Read and closed documents popping up on every reboot
https://bugs.kde.org/show_bug.cgi?id=440086 Bug ID: 440086 Summary: Read and closed documents popping up on every reboot Product: okular Version: 21.04.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: bobofengl...@zoho.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Read a .pdf file (opened via Firefox) 2. Close all instances of Okular 3. Reboot OBSERVED RESULT Any closed documents open, and have to be closed again, repeat and it happens again. EXPECTED RESULT No documents, unless left open for whatever reason, should not open on reboot. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 ADDITIONAL INFORMATION I have had this problem a few times before with KDE applications. Strangely it also happens (more often) that System trey applications (not necessarily KDE apps) don't load on boot, and I have a strange one right now, just in case you are interested (I know that KDE may not even have anything to do with it: The download manager Persepolis every once in a while doesn't load to the system trey on boot, although set in the app to do so. There is no entry in the system trey settings for it; Any app that does launch to the trey through any method should, as it wold be an easy way to enable and disable all of them in one place, and may be of help in trouble shooting too. It would be nice; if that's even possible. When it does work, it strangely also opens to the desktop which is annoying. When it shows this behavior (not loading on boot), it also doesn't load when launched via the Application Launcher, but. For the first tome today it launched as usual to the desktop (didn't look in the trey, but this time when I closed it, it was also missing from the trey as well, and would not launch any which way again. This program has the problem off and on for months now, possibly always. I know that it's independent from KDE, but it may just be that you could look into how easy it is for developers to implement the underlying procedures, or how they are handled... and streamline and improve implementing it (I know it may not have to do with KDE). I for one have always had a problem with KDE documentation, as there's very little info for many programs, plenty of outdated and no longer applicable info making me try stuff for things to either fail, or cause trouble, mostly find several possible locations for files to make changes in for the very same thing, only to realize they have changed yet again! There are few howto's... and when there is information, it is mostly geared toward developers, and way over the heads of anyone with little to no understanding of programming (Me), even when they are settings and customization's us users would love to implement and possibly share, like making any of the various themes, which is why so many on your app store are utterly useless, and often cause problems. I have never been able to make an Icon theme following any of your or anyone else's documentation that works right, often not at all. I guess I will have to send you guys a long list of suggestions (from a user perspective), which sounds strange for the desktop with the most and best options, settings, features, and gadgets over any other, at least in my experience, and why I have been using KDE for so long, and love it so much. Just looking at "Possible Duplicates below" doesn't tell me muvh because of the programmers lingo; I think it may help all of KDE a lot, to have two bug reporting sections or sites: One for developers and contributors, and one for users specifically, and yes I understand it is a huge amount of work, but will cut down on work in the long run, and so "pay" for itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 440084] exr.cpp/OpenEXR virtual function tellg error
https://bugs.kde.org/show_bug.cgi?id=440084 --- Comment #2 from Kurt Hindenburg --- /opt/local/include/OpenEXR/OpenEXRConfig.h:#define OPENEXR_VERSION_MAJOR 2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373440] konsole --new-tab opens window instead
https://bugs.kde.org/show_bug.cgi?id=373440 Igor Grkavac changed: What|Removed |Added CC||grkavac.i...@gmail.com --- Comment #45 from Igor Grkavac --- Hello, I checked this issue and I think it can be divided into 2 parts: 1. The first problem seems to be this line (which ironically says "Don't touch"): https://invent.kde.org/utilities/konsole/-/blob/fb69c183c672dff1d8e5e95d187622980255827c/src/main.cpp#L146 As it is preventing using a single process if 'multiple' is selected in options. Removing Konsole::KonsoleSettings::useSingleInstance() should be enough. 2. The second problem is that this is working only if konsole is launched with "--new-tab". If konsole is launched with no arguments, calling "konsole --new-tab" from within will open a new window. If "konsole --new-tab" is launched first, every additional "konsole --new-tab" will open a new tab. I am still not sure why is this happening. However, there is another thing that I noticed: A new tab is opened only on the initial konsole. So, if you open a konsole and run --new-tab a few times and open additional konsole, doing "konsole --new-tab" will add a tab to the previous konsole, not the current one. I guess that it is another issue due to a workaround that is just looking for the first non-nullptr window, but that should be checked on another ticket. I will update if I find anything regarding the second problem why it is happening. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417610] Automatically enqueue the following songs when selecting & playing a song from the main view
https://bugs.kde.org/show_bug.cgi?id=417610 techxga...@outlook.com changed: What|Removed |Added Version|0.4.2 |21.07.80 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417610] Automatically enqueue the following songs when selecting & playing a song from the main view
https://bugs.kde.org/show_bug.cgi?id=417610 --- Comment #5 from techxga...@outlook.com --- Another thought that came to mind. When you search a specific song, artist, or album, everything in the result should be enqueued. If the user closes the search result, everything in the library or playlist should be played. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440063] presentation mode is incompatible with video conferencing via Zoom, BigBlueButton, Webex, ...
https://bugs.kde.org/show_bug.cgi?id=440063 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #4 from Albert Astals Cid --- Are you using Plasma Wayland or Plasma X11? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 440084] exr.cpp/OpenEXR virtual function tellg error
https://bugs.kde.org/show_bug.cgi?id=440084 --- Comment #1 from Albert Astals Cid --- arg, i fixed openexr 3 and broke 2 :D Can you confirm if there's a OPENEXR_VERSION_MAJOR defined somewhere in your /opt/local/include/OpenEXR/ ? and which file is it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440071] Cannot set image as wallpaper if its file path contains a '#'
https://bugs.kde.org/show_bug.cgi?id=440071 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #41 from tagwer...@innerjoin.org --- (In reply to Scott from comment #40) > ... I am not sufficiently knowledgeable to provide the detail you appear to be > after ... > ... I would think that 20MB per sample file would be sufficient ... No problem, I'm certainly tapping in the dark and learning as I go... I think that finding comparative test cases, where one can be indexed and the other not, is the bigger job. If you've got that, then the sharing of the samples "ought" to be easier (dropbox perhaps...) but my limited understanding is: In a standard video, from the > perspective of the video player, you have 3 streams, video, audio and > subtitle. In an advanced container as I have discussed in this thread such > as .ts, .m2ts and .mkv files (containers/wrappers) there may be many more > streams than the 3 which the video player uses to produce the watchable > video. > > Each stream is encoded and read using a specific codec and is entirely > stand-alone, bearing no dependency relationship to the container whatsoever. > The audio and video streams have duration metadata, subtitles I don't know > as they are either a collection of still images or a text file. M2ts and ts > containers also have duration metadata while mkv containers do not see, > https://trac.ffmpeg.org/wiki/FFprobeTips. > > Unless provision can be made to upload larger files it will not be possible > to send a sample to be investigated. I would think that 20MB per sample file > would be sufficient. -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 440085] New: Video podcasts
https://bugs.kde.org/show_bug.cgi?id=440085 Bug ID: 440085 Summary: Video podcasts Product: kasts Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: bigbea...@gmail.com Target Milestone: --- SUMMARY I subscribe to the USGS Earthquake Science Seminars but I am only able to play the audio portion of the podcast. Wishlist: to be able to play video podcasts (vodcasts) within kasts. STEPS TO REPRODUCE 1. Subscribe to a vodcast 2. Play vodcast episode 3. OBSERVED RESULT Only audio plays - unable to see video. EXPECTED RESULT Video and audio should play. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Artix Linux - 5.12.14-artix1-1 (available in About System) KDE Plasma Version: 5.22.3 KWin X11 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 440084] New: exr.cpp/OpenEXR virtual function tellg error
https://bugs.kde.org/show_bug.cgi?id=440084
Bug ID: 440084
Summary: exr.cpp/OpenEXR virtual function tellg error
Product: frameworks-kimageformats
Version: unspecified
Platform: MacPorts Packages
OS: macOS
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: alex.me...@kde.org
Reporter: kurt.hindenb...@gmail.com
CC: aa...@kde.org, kdelibs-b...@kde.org
Target Milestone: ---
This appears to be similar to https://bugs.kde.org/show_bug.cgi?id=439767 but I
still get an error even after the patch for that BR.
I build KF5 from the current source.
AppleClang 12.0.5.12050022; openexr @2.3.0
/Volumes/Devel/KDE/src/frameworks/kimageformats/src/imageformats/exr.cpp:47:14:
error: virtual function 'tellg' has a different return type ('uint64_t' (aka
'unsigned long long')) than the function it overrides (which has return type
'Imath_2_3::Int64' (aka 'unsigned long'))
uint64_t tellg() override;
^
/opt/local/include/OpenEXR/ImfIO.h:117:19: note: overridden virtual function is
here
virtual Int64 tellg () = 0;
~ ^
/Volumes/Devel/KDE/src/frameworks/kimageformats/src/imageformats/exr.cpp:48:30:
error: non-virtual member function marked 'override' hides virtual member
function
void seekg(uint64_t pos) override;
^
/opt/local/include/OpenEXR/ImfIO.h:125:18: note: hidden overloaded virtual
function 'Imf_2_3::IStream::seekg' declared here: type mismatch at 1st
parameter ('Imath_2_3::Int64' (aka 'unsigned long') vs 'uint64_t' (aka
'unsigned long long'))
virtual voidseekg (Int64 pos) = 0;
^
/Volumes/Devel/KDE/src/frameworks/kimageformats/src/imageformats/exr.cpp:170:19:
error: variable type 'K_IStream' is an abstract class
K_IStream istr(device(), QByteArray());
^
/opt/local/include/OpenEXR/ImfIO.h:125:18: note: unimplemented pure virtual
method 'seekg' in 'K_IStream'
virtual voidseekg (Int64 pos) = 0;
^
--
You are receiving this mail because:
You are watching all bug changes.
[baloo-widgets] [Bug 407530] Impossible to delele tags while baloo indexes files
https://bugs.kde.org/show_bug.cgi?id=407530 --- Comment #4 from tagwer...@innerjoin.org --- (In reply to Patrick Silva from comment #3) > ... and the behavior mentioned > in comment 1 occurs when I try to delete tags while baloo is enabled but > indexing is not in progress ... Hmmm. So maybe there's a file "stuck somewhere" that still has the tag or that baloo has a "stuck record" of the tag on a file that no longer exists. If you are indexing your $HOME, try searching through all the extended attributes. Something like: getfattr -Rd ~ | grep -B1 test (not sure, you were using "test" and "teste" tags?). For the "stuck record", see what baloosearch returns: baloosearch 'tags:/test$' baloosearch 'tags:/teste$' There's a chance you've tagged a file and moved it to the wastebasket... I think it's worth a look... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440083] New: [wayland] plasma crashes when an external screen is connected over HDMI
https://bugs.kde.org/show_bug.cgi?id=440083 Bug ID: 440083 Summary: [wayland] plasma crashes when an external screen is connected over HDMI Product: plasmashell Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bednarczyk.pa...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.22.80) (Compiled from sources) Qt Version: 5.15.3 Frameworks Version: 5.85.0 Operating System: Linux 5.4.0-70-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.22.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: JUST CONNECTED an external TV - OLED LG 65 inch and the screen went black and shortly after plasma crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 1719] [New LWP 1768] [New LWP 1766] [New LWP 1763] [New LWP 1767] [New LWP 1770] [New LWP 1772] [New LWP 1765] [New LWP 1775] [New LWP 1769] [New LWP 1773] [New LWP 1790] [New LWP 1776] [New LWP 1771] [New LWP 1778] [New LWP 1774] [New LWP 1780] [New LWP 1777] [New LWP 1786] [New LWP 1783] [New LWP 1785] [New LWP 1781] [New LWP 1746] [New LWP 1782] [New LWP 1779] [New LWP 1957] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f73db6f19c0 (LWP 1719))] __preamble__ [Current thread is 1 (Thread 0x7f73db6f19c0 (LWP 1719))] Thread 26 (Thread 0x7f73767fc700 (LWP 1957)): #0 0x7f73df58faff in __GI___poll (fds=0x7f7364004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f73dde4236e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f73dde424a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f73dfb5efb2 in QEventDispatcherGlib::processEvents (this=0x7f7364000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f73dfb0325b in QEventLoop::exec (this=this@entry=0x7f73767fbbc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f73df91cc22 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f73e1124559 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f73df91ddbc in QThreadPrivate::start (arg=0x55f7cae017a0) at thread/qthread_unix.cpp:329 #8 0x7f73de874609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f73df59c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f7396ffd700 (LWP 1779)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f7caa71268) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f7caa71218, cond=0x55f7caa71240) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f7caa71240, mutex=0x55f7caa71218) at pthread_cond_wait.c:647 #3 0x7f73d8d6cb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f73d8d6c75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f73de874609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f73df59c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f73957fa700 (LWP 1782)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55f7caa71970) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55f7caa71920, cond=0x55f7caa71948) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55f7caa71948, mutex=0x55f7caa71920) at pthread_cond_wait.c:647 #3 0x7f73d8d6cb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f73d8d6c75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f73de874609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f73df59c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7f73dab24700 (LWP 1746)): #0 0x7f73df58faff in __GI___poll (fds=0x7f73d4005240, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f73dde4236e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f73dde424a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f73dfb5efb2 in QEventDispatcherGlib::processEvents (this=0x7f73d4000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f73dfb0325b in QEventLoop::exec (this=this@
[systemsettings] [Bug 440082] New: Removable Media Tab Refuses to Load, Crashes System Settings
https://bugs.kde.org/show_bug.cgi?id=440082 Bug ID: 440082 Summary: Removable Media Tab Refuses to Load, Crashes System Settings Product: systemsettings Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kcm_deviceautomounter Assignee: tdfisc...@kde.org Reporter: dev...@web.de CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The removable devices tab simply refuses to load, but that consistently. No stdout logs are produced, the application seems deadlocked and needs to be closed externally. STEPS TO REPRODUCE I do not know how far that was responsible for it, but the problems occurred after I mounted a new webcam via USB for the first time. Since then, this tab simply won't open, even when the webcam was removed again, and subsequently crashes the entire application. I do not know, however, whether the problem existed before as well, or only since then. 1. Open system settings (i. Mount webcam?) 2. Navigate to removable media tab 3. Click on this tab 4. Enjoy the crash OBSERVED RESULT Application becomes deadlocked and has to be terminated externally EXPECTED RESULT Program should not deadlock. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.8.0-59-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 15,5 GiB of RAM ADDITIONAL INFORMATION My best guess for how this issue came to be is that some system resource is requested that simply is never accessible, resulting in the application waiting forever to get access to that resource. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424795] "Open Link" action doesn't focus browser window
https://bugs.kde.org/show_bug.cgi?id=424795 Patrick Silva changed: What|Removed |Added CC||k...@asdrip.fr --- Comment #14 from Patrick Silva --- *** Bug 440032 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 440032] Kate won't go in the foreground in wayland if a file is already open
https://bugs.kde.org/show_bug.cgi?id=440032 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 424795 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359783] Right-aligned desktop icons move all the way to the left when icons are added or moved
https://bugs.kde.org/show_bug.cgi?id=359783 Patrick Silva changed: What|Removed |Added CC||ianc_...@fastmail.uk --- Comment #50 from Patrick Silva --- *** Bug 440034 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440034] Desktop Icons change from Right Aligned to Left Aligned and back to Right Aligned.
https://bugs.kde.org/show_bug.cgi?id=440034 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 359783 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439801] Auto change not working A2DP//HSp/HFP
https://bugs.kde.org/show_bug.cgi?id=439801 --- Comment #7 from Nicolas Fella --- This is unrelated to the kernel. The Android userspace is quite different to a normal Linux system -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440081] Make "Present Windows" more apparent when only one program is running and is maximized
https://bugs.kde.org/show_bug.cgi?id=440081 ba.tahaa...@gmail.com changed: What|Removed |Added Summary|Present Windows: make it|Make "Present Windows" more |apparent when only one |apparent when only one |program is running and is |program is running and is |maximized |maximized -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440081] New: Present Windows: make it apparent when only one program is running and is maximized
https://bugs.kde.org/show_bug.cgi?id=440081 Bug ID: 440081 Summary: Present Windows: make it apparent when only one program is running and is maximized Product: plasmashell Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ba.tahaa...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Currently, the Present Windows feature's activation is not apparent when only when program is running, and that program is maximized. Activating Present Windows in this case, does not apply a gap as it usually does, and it does not darken the desktop. STEPS TO REPRODUCE 1. Open only one program 2. Activate Present Windows OBSERVED RESULT It's almost difficult, if not impossible to tell whether Present Windows has been activated or not when icons, titles, and the close button are hidden/disabled. EXPECTED RESULT Present Windows should take into account the case when only one program is running and that program is maximized, and should apply the usual effects. SOFTWARE/OS VERSIONS Linux: Arch Linux, Linux 5.10.51-1-lts (x64) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373440] konsole --new-tab opens window instead
https://bugs.kde.org/show_bug.cgi?id=373440 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #44 from Gabor --- I am on manjaro XFCE konsole 21.04.3. In this version if "run all Konsole with single process" checked and first instance started with --new-tab, then another --new-tab works. This is an acceptable workaround. With this combination the dbus address is org.kde.konsole In other cases dbus-send --dest=$KONSOLE_DBUS_SERVICE --print-reply=literal --type=method_call /Windows/1 org.kde.konsole.Window.newSession works. and also works with --dest=org.kde.konsole-$KPID where $KPID is the pid of the konsole. Maybe the problem is that the dbus service is not the standard org.kde.konsole -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440080] New: Discover crashes on every start using git snapshots
https://bugs.kde.org/show_bug.cgi?id=440080 Bug ID: 440080 Summary: Discover crashes on every start using git snapshots Product: Discover Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: robby.engelm...@r-engelmann.de CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.22.80) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.2-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.22.80 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Discover crashes on every start using git snapshots on openSUSE Tumbleweed. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 QQmlRefPointer::QQmlRefPointer(QQmlRefPointer const&) (other=..., this=0x7f39f0ab3750, this@entry=0x7f39f0ab36d0) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/ftw/qqmlrefcount_p.h:152 #5 QQmlType::QQmlType(QQmlType const&) (this=this@entry=0x7f39f0ab3750) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltype.cpp:121 #6 0x7f39ff2a474c in QQmlPropertyCacheCreator::propertyCacheForObject(QmlIR::Object const*, QQmlBindingInstantiationContext const&, QQmlError*) const (this=this@entry=0x7f39f0ab3ad0, obj=obj@entry=0x7f39d82d23d8, context=..., error=error@entry=0x7f39f0ab37e8) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:310 #7 0x7f39ff2a7341 in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=this@entry=0x7f39f0ab3ad0, objectIndex=3, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:264 #8 0x7f39ff2a76cc in QQmlPropertyCacheCreator::buildMetaObjectRecursively(int, QQmlBindingInstantiationContext const&, QQmlPropertyCacheCreator::VMEMetaObjectIsRequired) (this=this@entry=0x7f39f0ab3ad0, objectIndex=objectIndex@entry=0, context=..., isVMERequired=isVMERequired@entry=QQmlPropertyCacheCreator::VMEMetaObjectIsRequired::Maybe) at /usr/include/qt5/QtCore/qendian.h:290 #9 0x7f39ff2a7ef4 in QQmlPropertyCacheCreator::buildMetaObjects() (this=this@entry=0x7f39f0ab3ad0) at ../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertycachecreator_p.h:215 #10 0x7f39ff2a2f0b in QQmlTypeCompiler::compile() (this=this@entry=0x7f39f0ab3c40) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypecompiler.cpp:85 #11 0x7f39ff1f4485 in QQmlTypeData::compile(QQmlRefPointer const&, QV4::ResolvedTypeReferenceMap*, std::function const&) (this=this@entry=0x7f39d82acae0, typeNameCache=..., resolvedTypeCache=resolvedTypeCache@entry=0x7f39f0ab3d20, dependencyHasher=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypedata.cpp:774 #12 0x7f39ff1fa49a in QQmlTypeData::done() (this=0x7f39d82acae0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypedata.cpp:451 #13 0x7f39ff1e7fe5 in QQmlDataBlob::tryDone() (this=0x7f39d82acae0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmldatablob.cpp:524 #14 QQmlDataBlob::tryDone() (this=0x7f39d82acae0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmldatablob.cpp:515 #15 0x7f39ff247815 in QQmlTypeLoader::setData(QQmlDataBlob*, QQmlDataBlob::SourceCodeData const&) (this=this@entry=0x5623b380c258, blob=blob@entry=0x7f39d82acae0, d=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:457 #16 0x7f39ff247f62 in QQmlTypeLoader::setData(QQmlDataBlob*, QString const&) (this=this@entry=0x5623b380c258, blob=blob@entry=0x7f39d82acae0, fileName=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:437 #17 0x7f39ff248dd0 in QQmlTypeLoader::loadThread(QQmlDataBlob*) (this=this@entry=0x5623b380c258, blob=blob@entry=0x7f39d82acae0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:299 #18 0x7f39ff24922c in PlainLoader::loadThread(QQmlTypeLoader*, QQmlDataBlob*) const (blob=0x7f39d82acae0, loader=0x5623b380c258, this=) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-ku.1.1.x86_64/src/qml/qml/qqmltypeloader.cpp:146 #19 QQmlTypeLoader::doLoad(PlainLoader const&, QQmlDataBlo
[frameworks-kdelibs4support] [Bug 344673] [Regression] Invalid KDateTime after adding seconds to a valid datetime
https://bugs.kde.org/show_bug.cgi?id=344673 --- Comment #5 from David Jarvie --- This bug still occurs. I'll have another look at it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428755] wrong color for combo boxes titles and items in Composition/Effect window for Fusion style and Breeze light themes
https://bugs.kde.org/show_bug.cgi?id=428755 --- Comment #4 from Martin Sandsmark --- I guess this is the culprit: https://invent.kde.org/multimedia/kdenlive/-/blob/master/src/assets/assetpanel.cpp#L382 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 428755] wrong color for combo boxes titles and items in Composition/Effect window for Fusion style and Breeze light themes
https://bugs.kde.org/show_bug.cgi?id=428755 Martin Sandsmark changed: What|Removed |Added CC||martin.sandsm...@kde.org --- Comment #3 from Martin Sandsmark --- I can reproduce it with latest master as well. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"
https://bugs.kde.org/show_bug.cgi?id=399245 lucaselin...@gmail.com changed: What|Removed |Added CC||lucaselin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
