[systemsettings] [Bug 412998] System Settings -> Display and Monitor -> Compositor crashes
https://bugs.kde.org/show_bug.cgi?id=412998 Farah Nur changed: What|Removed |Added CC||rafiorton...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session on AMD hardware
https://bugs.kde.org/show_bug.cgi?id=412152 --- Comment #15 from Pawel --- (In reply to Alexandre Pereira from comment #14) > strangely i have this bug if i boot with amdgpu_dc=0. > with amdgpu_dc=1, kwin loads the wayland session. > > can anyone test ? I tested on two kernels (my own, and linux-zen) with both: amdgpu_dc=0 and amdgpu_dc=1 but without any success. Still only black screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session on AMD hardware
https://bugs.kde.org/show_bug.cgi?id=412152 Méven Car changed: What|Removed |Added Summary|[Wayland] cannot start |[Wayland] cannot start |session |session on AMD hardware -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413129] New: gtk apps not respecting border width setting
https://bugs.kde.org/show_bug.cgi?id=413129 Bug ID: 413129 Summary: gtk apps not respecting border width setting Product: Breeze Version: 5.17.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: m.mcn...@gmail.com Target Milestone: --- Created attachment 123308 --> https://bugs.kde.org/attachment.cgi?id=123308=edit frame around window SUMMARY After updating to 5.17, I've noticed my gtk apps have a border, despite my Window Decoration being set to no border. Example apps - Firefox with title bar turned off, peek, gnome settings, Fedy - anything gtk. Forcing no border for individual apps has no effect. Also present on a fresh user profile. Was not present in 5.16.90 STEPS TO REPRODUCE 1. System Settings > Application Style > Window Decorations > Set drop down to no borders 2. Open Gtk App 3. Marvel at thick Window borders OBSERVED RESULT Window borders EXPECTED RESULT No Window borders SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30 (with Plasma 5.17 out of copr), also present on Neon User Ed 5.17 (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63 Qt Version: 5.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413129] gtk apps not respecting border width setting
https://bugs.kde.org/show_bug.cgi?id=413129 --- Comment #1 from Matt --- Created attachment 123309 --> https://bugs.kde.org/attachment.cgi?id=123309=edit apps with borders -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 413072] german user interface?
https://bugs.kde.org/show_bug.cgi?id=413072 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||6.4.0 Status|REPORTED|RESOLVED Component|Usability-Ergonomy |Usability-i18n Resolution|--- |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Screenshot of the language menu, dialog selection, and user interface in German, under MacOS Mojave... https://i.imgur.com/lKeInW0.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 411984] Lattedock leaking memory
https://bugs.kde.org/show_bug.cgi?id=411984 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[kdenlive] [Bug 411905] New version in Flathub
https://bugs.kde.org/show_bug.cgi?id=411905 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.
[krita] [Bug 411988] Shortcuts and Canvas Input Settings reset at reboot
https://bugs.kde.org/show_bug.cgi?id=411988 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413125] Color to alpha makes the image loses its original color
https://bugs.kde.org/show_bug.cgi?id=413125 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- 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.
[kate] [Bug 411865] kate crashes when clicking print button, caused by an inconsistency in a printer PPD file
https://bugs.kde.org/show_bug.cgi?id=411865 --- 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.
[kwin] [Bug 412008] kwin crashed after VT switch from another X session
https://bugs.kde.org/show_bug.cgi?id=412008 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412276] no root access from normal user login using plasma 5.16.90
https://bugs.kde.org/show_bug.cgi?id=412276 --- 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.
[kdenlive] [Bug 412028] Can't exit full screen mode
https://bugs.kde.org/show_bug.cgi?id=412028 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412581] Okular fails to open an unencrypted ePub
https://bugs.kde.org/show_bug.cgi?id=412581 --- 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.
[kwin] [Bug 413128] New: kwin_x11 --reload -- CoreDump
https://bugs.kde.org/show_bug.cgi?id=413128 Bug ID: 413128 Summary: kwin_x11 --reload -- CoreDump Product: kwin Version: 5.16.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nroycea+...@gmail.com Target Milestone: --- SUMMARY kwin_x11 was pegged at 100% and the GUI was somewhat unresponsive (mouse cursor still moved). "$ kwin_x11 --replace" resulted in a coredump. STEPS TO REPRODUCE 1. Normal every day use. OBSERVED RESULT Coredump EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION While I was browsing in Chrome, action responses froze. I could move my mouse around, but there would be no action from any clicking or even ALT-Tab. I switched terminals (luckily?), and saw kwin_x11 was pegged at 100% CPU usage, and bouncing around among the cores. I tried to "$ kwin_x11 --replace", but after a short wait, there was a coredump: * Oct 17 21:51:31 computername systemd-coredump[1598113]: Process 1598070 (kwin_x11) of user 1000 dumped core. Stack trace of thread 1598078: #0 0x7b753249af25 raise (libc.so.6) #1 0x7b75320f26b0 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5) #2 0x7b753249afb0 __restore_rt (libc.so.6) #3 0x7b753249af25 raise (libc.so.6) #4 0x7b7532484897 abort (libc.so.6) #5 0x7b7530e2c8f8 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5) #6 0x7b7529374cec n/a (KWinX11Platform.so) #7 0x7b7531061b70 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #8 0x7b753106eb78 _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5) #9 0x7b75310623e5 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #10 0x7b75319f14f5 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #11 0x7b75319fae11 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #12 0x7b75310359c2 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #13 0x7b753108cd9d _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5) #14 0x7b753108b169 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #15 0x7b75310344ec _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #16 0x7b7530e66385 _ZN7QThread4execEv (libQt5Core.so.5) #17 0x7b7530e675b0 n/a (libQt5Core.so.5) #18 0x7b752ffd54cf start_thread (libpthread.so.0) #19 0x7b753255e2d3 __clone (libc.so.6) Stack trace of thread 1598074: #0 0x7b752ffdbf7a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x7b7530e6d5cc _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5) #2 0x7b7530e6d719 _ZN14QWaitCondition4waitEP6QMutexm (libQt5Core.so.5) #3 0x7b7530e6ab9b n/a (libQt5Core.so.5) #4 0x7b7530e675b0 n/a (libQt5Core.so.5) #5 0x7b752ffd54cf start_thread (libpthread.so.0) #6 0x7b753255e2d3 __clone (libc.so.6) Stack trace of thread 1598071: #0 0x7b75325539ef __poll (libc.so.6) #1 0x7b7530d87630 n/a (libxcb.so.1)
[lattedock] [Bug 413127] With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 andydecle...@gmail.com changed: What|Removed |Added Version|unspecified |0.9.3 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #2 from andydecle...@gmail.com --- Created attachment 123307 --> https://bugs.kde.org/attachment.cgi?id=123307=edit Default.layout.latte -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 --- Comment #1 from andydecle...@gmail.com --- Created attachment 123306 --> https://bugs.kde.org/attachment.cgi?id=123306=edit lattedockrc -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 413127] New: With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked
https://bugs.kde.org/show_bug.cgi?id=413127 Bug ID: 413127 Summary: With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked Product: lattedock Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andydecle...@gmail.com Target Milestone: --- Created attachment 123305 --> https://bugs.kde.org/attachment.cgi?id=123305=edit Video demo SUMMARY With parabolic effect disabled and hover-zoom at 0%, plasma task manager hover actions are not activated, and entries are permanently highlighted when clicked. STEPS TO REPRODUCE 1. add plasma task manager to a latte dock 2. disable parabolic effect 3. set zoom on hover to 0% OBSERVED RESULT No matter the task manager's settings, windows will not be highlighted or previewed when hovering over their entries. Clicking on each entry changes its color, permanently. EXPECTED RESULT If the task manager is set to highlight windows on hover, then hovering over each entry should highlight the window. If the task manager is set to show a window preview tooltip on hover, then hovering over each entry should show show a window preview tooltip. If a task manager entry is clicked, its color should not be permanently changed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Configuration files which are the simplest-possible modification of default settings, which reproduce the problem, are attached, as well as a video demonstration of the problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413125] Color to alpha makes the image loses its original color
https://bugs.kde.org/show_bug.cgi?id=413125 --- Comment #2 from acc4commissi...@gmail.com --- (In reply to vanyossi from comment #1) > did you adjust the trheshold too high?? > > If you only want to remove pure white you have to adjust threshold to > something around 30, any value higher than that will probably make color to > alpha remove other colors near white, like yellows. > > I do loose some color information if threshold is high. > > Tested on 8bit RGB ColorSpace. The point is that 'the color shouldn't change as I move the silder'. Sorry for mentioning other applications but in gimp it only scrapes opacity and not the color. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413126] New: Filter mask is so heavy
https://bugs.kde.org/show_bug.cgi?id=413126 Bug ID: 413126 Summary: Filter mask is so heavy Product: krita Version: 4.2.7.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY After filter mask is applied to a layer, it slows any operations down on that layer : moving, transforming, even painting. It seems that the filter mask is applied to the entire canvas area no matter how small the image on the layer is, and stays where it is like 'a filter layer attatch to its target layer'. Is it possible to limit filter mask application to the actual images on the layer, and make it move along with the target layer changes? * This is an issue with transparency mask too, although it doesn't make layer as laggy as filter mask. (transparency mask also moves along with the target layer moves.) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413125] Color to alpha makes the image loses its original color
https://bugs.kde.org/show_bug.cgi?id=413125 vanyossi changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||ghe...@gmail.com --- Comment #1 from vanyossi --- did you adjust the trheshold too high?? If you only want to remove pure white you have to adjust threshold to something around 30, any value higher than that will probably make color to alpha remove other colors near white, like yellows. I do loose some color information if threshold is high. Tested on 8bit RGB ColorSpace. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413125] New: Color to alpha makes the image loses its original color
https://bugs.kde.org/show_bug.cgi?id=413125 Bug ID: 413125 Summary: Color to alpha makes the image loses its original color Product: krita Version: 4.2.7.1 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Filters Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- Created attachment 123304 --> https://bugs.kde.org/attachment.cgi?id=123304=edit capture SUMMARY STEPS TO REPRODUCE 1. load any image, preferably the one has some high-saturated colors. 2. Apply Color to Alpha to it, over white background layer. OBSERVED RESULT Color changes. EXPECTED RESULT The original color is preserved. Color to Alpha in GIMP does not do this. The color stays exactly the same regardless of its threshold. (Thought It's necessary to change the layer mode to 'legacy' after 2.10 update...) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session
https://bugs.kde.org/show_bug.cgi?id=412152 --- Comment #14 from Alexandre Pereira --- strangely i have this bug if i boot with amdgpu_dc=0. with amdgpu_dc=1, kwin loads the wayland session. can anyone test ? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 413124] New: KDE Connect won't connect.
https://bugs.kde.org/show_bug.cgi?id=413124 Bug ID: 413124 Summary: KDE Connect won't connect. Product: kdeconnect Version: 1.3.5 Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: leftcr...@tutanota.com Target Milestone: --- [Marking as critical since this bug breaks the software entirely.] SUMMARY This is a continuation of the story in Bug 400010 where KDE would crash when the connection got interrupted. And it would keep crashing until you rebooted both devices. Now, it no longer crashes but it will still drop the connection at some point after working for a few days and then NEVER re-establish the connection EVER again. So for at least the past month of constantly running KDE connect on both the PC and the phone - as well as rebooting both devices, reinstalling the software and disabling firewall - the two devices haven't never discovered each other on the network. In fact, the PC wasn't visible on the network at all. As described in Bug 400010, the issue seems to arise after several cycles of enabling/disabling VPN and suspeding/resuming the machine (though I can't be sure obviously). Can KDE connect even be used with VPN software, or is there a fundamental conflict between the two by design? A google search shows that KDE Connect not Connecting is a problem that's as old as KDE Connect itself, and there are apparently no self-fixes for it. (SIDE NOTE: Is bluetooth connectivity planned or is that out of scope for this project?) Operating System: Kubuntu 19.04 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-32-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i7-4600U CPU @ 2.10GHz -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 --- Comment #3 from David Bate --- Created attachment 123303 --> https://bugs.kde.org/attachment.cgi?id=123303=edit Kontact appointment bug pic 2 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 --- Comment #2 from David Bate --- Created attachment 123302 --> https://bugs.kde.org/attachment.cgi?id=123302=edit Kontact add appointment bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work
https://bugs.kde.org/show_bug.cgi?id=413104 --- Comment #2 from David Edmundson --- Weirder part is how FolderView works. https://phabricator.kde.org/D24748 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 410167] Cannot change or enter time for calendar entry
https://bugs.kde.org/show_bug.cgi?id=410167 --- Comment #1 from David Bate --- Have upgraded to: Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Still same issue. When trying to set times, they revert back to midnight when saved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work
https://bugs.kde.org/show_bug.cgi?id=413104 David Edmundson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 413123] New: Cannot select target languge in Project > Configure project > General > Target language
https://bugs.kde.org/show_bug.cgi?id=413123 Bug ID: 413123 Summary: Cannot select target languge in Project > Configure project > General > Target language Product: lokalize Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: bozid...@yahoo.com CC: sha...@ukr.net Target Milestone: --- SUMMARY Cannot select target language in "Configure project". In fact cannot select any language, as the bar is empty, cannot be clicked. STEPS TO REPRODUCE 1. Menu > Project > Configure project > General > Target language 2. Nothing can be selected, I need Croatian as target language. 3. In main window, when mouse hover above space for translated strings, tip tool reports "American English", all Croatian words are "misspelled", as Lokalize thinks they are English word but misspelled. OBSERVED RESULT Cannot select target language EXPECTED RESULT Be able to select target language and be able to use Croatian spell check. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION My PC is running Windows 10, but is configured as US version. I have added Croatian keyboard which works perfectly in Word, also spelling is correct in the Word documents. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 413121] won't play aac/m4a
https://bugs.kde.org/show_bug.cgi?id=413121 --- Comment #1 from Peter Maiwald --- Sorry I have right clicked in dolphin and open with amarok. The songs are in the playlist but can't play. If I drag and drop the file from dolphin to amaroks playlist it will play. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412808] Undoing selecting new area makes the previous selection invisible in global selection mask
https://bugs.kde.org/show_bug.cgi?id=412808 --- Comment #5 from acc4commissi...@gmail.com --- (In reply to acc4commissions from comment #4) > If you use outline selection tool I was wrong. Appareantly it happens with all selection tools... -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 413121] New: won't play aac/m4a
https://bugs.kde.org/show_bug.cgi?id=413121 Bug ID: 413121 Summary: won't play aac/m4a Product: amarok Version: 2.9.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Playback Assignee: amarok-bugs-d...@kde.org Reporter: peter.maiw...@web.de CC: ma...@laitl.cz Target Milestone: kf5 Amarok does not play acc/m4a files. Clementine does it. STEPS TO REPRODUCE 1. open m4a file 2. click play 3. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 413122] New: Crashing when trying to open USB key.
https://bugs.kde.org/show_bug.cgi?id=413122 Bug ID: 413122 Summary: Crashing when trying to open USB key. Product: partitionmanager Version: 4.0.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: falling_failing_fall...@protonmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Plug an Lexar USB key in the computer 2. Click on the Lexar USB key in KDE Partition Manager 3. The KDE Partition Manager will crash. OBSERVED RESULT KDE Partition Manager crash. EXPECTED RESULT Not crashing. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE NEON 5.17 (available in About System) KDE Plasma Version: latest KDE Frameworks Version: latest Qt Version: latest ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412808] Undoing selecting new area makes the previous selection invisible in global selection mask
https://bugs.kde.org/show_bug.cgi?id=412808 --- Comment #4 from acc4commissi...@gmail.com --- (In reply to acc4commissions from comment #3) > 1 If you select a new area that include the previous area before undoing it, > the later operations is applied to the intersecting area. If you use outline selection tool to do this, the 'intersecting area' appears to be square-shaped, even though the original shape was different. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413120] New: Can't save anymore the night mode settings
https://bugs.kde.org/show_bug.cgi?id=413120 Bug ID: 413120 Summary: Can't save anymore the night mode settings Product: systemsettings Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: falling_failing_fall...@protonmail.com Target Milestone: --- Created attachment 123301 --> https://bugs.kde.org/attachment.cgi?id=123301=edit Look at the button at the bottom right of the screen. SUMMARY STEPS TO REPRODUCE 1. Open the system settings. 2. Go to the night mode settings. 3. You can't click on the "apply button" on the bottom right of the window. OBSERVED RESULT Unable to click on the "apply button" on the bottom right of the window. EXPECTED RESULT Able to click on the "apply button" on the bottom right of the window. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE NEON 5.17 (available in About System) KDE Plasma Version: latest KDE Frameworks Version: latest Qt Version: latest ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413119] ioctl wrapper for DRM_IOCTL_I915_GEM_MMAP
https://bugs.kde.org/show_bug.cgi?id=413119 Simon Richter changed: What|Removed |Added CC||simon.rich...@hogyros.de -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413119] ioctl wrapper for DRM_IOCTL_I915_GEM_MMAP
https://bugs.kde.org/show_bug.cgi?id=413119 --- Comment #2 from Simon Richter --- Created attachment 123299 --> https://bugs.kde.org/attachment.cgi?id=123299=edit Patch to handle ioctl -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413119] ioctl wrapper for DRM_IOCTL_I915_GEM_MMAP
https://bugs.kde.org/show_bug.cgi?id=413119 --- Comment #3 from Simon Richter --- Created attachment 123300 --> https://bugs.kde.org/attachment.cgi?id=123300=edit Patch to handle legacy ioctl -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413119] ioctl wrapper for DRM_IOCTL_I915_GEM_MMAP
https://bugs.kde.org/show_bug.cgi?id=413119 --- Comment #1 from Simon Richter --- Created attachment 123298 --> https://bugs.kde.org/attachment.cgi?id=123298=edit Patch to update ioctl argument definition -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 413119] New: ioctl wrapper for DRM_IOCTL_I915_GEM_MMAP
https://bugs.kde.org/show_bug.cgi?id=413119 Bug ID: 413119 Summary: ioctl wrapper for DRM_IOCTL_I915_GEM_MMAP Product: valgrind Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: simon.rich...@hogyros.de Target Milestone: --- SUMMARY This adds a wrapper for the DRM_IOCTL_I915_GEM_MMAP ioctl, which creates a mapping for a DRM buffer object in the client's address space. STEPS TO REPRODUCE 1. Run an OpenGL application with direct rendering enabled on an Intel GPU under valgrind OBSERVED RESULT Memory accesses to command and texture buffers are flagged as errors EXPECTED RESULT Command buffers can be written normally SOFTWARE/OS VERSIONS Linux: 4.19.37 ADDITIONAL INFORMATION There are two versions of this ioctl that are distinguished by different argument sizes. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413106] problem confiuring 3 monitors kde neon 5.16 worked fine 5.17 not work
https://bugs.kde.org/show_bug.cgi?id=413106 --- Comment #3 from alda --- Created attachment 123297 --> https://bugs.kde.org/attachment.cgi?id=123297=edit kcm monitor2 position and rotation i am attaching monitor fubar1.png to show how kcm_kscreen looks after reboot monitor fubar2.png shows how kcm_kscreen looks after clicking button for rotation 90 degrees clockwise -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413106] problem confiuring 3 monitors kde neon 5.16 worked fine 5.17 not work
https://bugs.kde.org/show_bug.cgi?id=413106 --- Comment #2 from alda --- Created attachment 123296 --> https://bugs.kde.org/attachment.cgi?id=123296=edit kcm monitor position and rotation i am attaching monitor fubar1.png to show how kcm_kscreen looks after reboot monitor fubar2.png shows how kcm_kscreen looks after clicking button for rotation 90 degrees clockwise -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413118] Scrollbar mouse down/click on background zone not registered.
https://bugs.kde.org/show_bug.cgi?id=413118 Martín Lucas Golini changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413118] New: Scrollbar mouse down/click on background zone not registered.
https://bugs.kde.org/show_bug.cgi?id=413118 Bug ID: 413118 Summary: Scrollbar mouse down/click on background zone not registered. Product: Breeze Version: 5.17.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: spart...@gmail.com Target Milestone: --- Created attachment 123295 --> https://bugs.kde.org/attachment.cgi?id=123295=edit This shows the lack of click detection, the first time it's using the latest breeze-gtk version, after I replace the version with an older one that works fine. SUMMARY Since at least version 5.16.90 I'm having problems registering clicks on the "background" zone of the scrollbar at least in Firefox. The problem seems to be related to this: https://github.com/KDE/breeze-gtk/commit/71a9a1f203df5c4d9bb165e9a3f57bf8265b1252 change. The background is now transparent, and seems to not register clicks on transparent zones. This problem at least affects Firefox with breeze-gtk for GTK3. It's quite annoying since you can't quick click the scrollbar from the screen border. STEPS TO REPRODUCE 1. Install latest version 5.17.0 2. Open Mozilla Firefox with a scrollable page. 3. Try to scroll by clicking the background zone of the scrollbar. OBSERVED RESULT Click not registered. EXPECTED RESULT Click should be registered to scroll easily. SOFTWARE/OS VERSIONS openSUSE Tumbleweed with latest Plasma version (5.17.0). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413118] Scrollbar mouse down/click on background zone not registered.
https://bugs.kde.org/show_bug.cgi?id=413118 Martín Lucas Golini changed: What|Removed |Added CC||spart...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 413062] note can create only one unique sticky note
https://bugs.kde.org/show_bug.cgi?id=413062 jms changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from jms --- do you need more infos? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 413046] Typing Cyrillic letters causes huge input lags
https://bugs.kde.org/show_bug.cgi?id=413046 Ilya Bizyaev changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Ilya Bizyaev --- Appears to have been fixed in 19.08.2, at least cannot reproduce now :) -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 256014] Allow one script trigger to be a prefix of another
https://bugs.kde.org/show_bug.cgi?id=256014
--- Comment #1 from Misha Aizatulin ---
Looks like this is still an issue with 2.9.92.
In fact, now the issue is worse - neither "\{" nor "\\{" as triggers work at
all, I presume due to it being confused about escaping.
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 256014] Allow one script trigger to be a prefix of another
https://bugs.kde.org/show_bug.cgi?id=256014 Misha Aizatulin changed: What|Removed |Added CC||ava...@hot.ee -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371447] laptop screen disabled after resume from suspend to RAM
https://bugs.kde.org/show_bug.cgi?id=371447 Nicolas Fella changed: What|Removed |Added Version Fixed In||5.17.1 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413068] Slideshow is broken
https://bugs.kde.org/show_bug.cgi?id=413068 --- Comment #5 from techxga...@outlook.com --- Doesn't seem to be related to slideshow anymore because mine just crashed, and I'm not using a slideshow now. Output with `journalctl -r | grep kscreenlocker`: `Oct 17 17:03:27 Y4M1-MS-7978 kernel: kscreenlocker_g[14627]: segfault at 7ffe6e854ff8 ip 7f2e210bc13c sp 7ffe6e855000 error 6 in libc-2.30.so[7f2e2104c000+178000]` After it crashed, I tried to lock again, and this time, lockscreen was just going off and on. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 413113] ktouch crashes on start
https://bugs.kde.org/show_bug.cgi?id=413113 Sebastian Gottfried changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Sebastian Gottfried --- Thanks for the response. Under Flatpak, applications are sandboxed and need to request permissions to access certain hard- and software components. With '--device=dri' you gave the permission to use OpenGL. I will add this to the Flatpak manifest of KTouch, so with next update it will works out of the box. I have no idea why it I don't need this on my system, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413019] Widget positioning is broken when switching to the external monitor
https://bugs.kde.org/show_bug.cgi?id=413019 --- Comment #4 from Marco Martin --- I need a screenshot before and after and the resolutions of the internal and external monitors -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 413117] New: kio-5.63 makes kdav-19.08.2 fail with HTTP error (400)
https://bugs.kde.org/show_bug.cgi?id=413117 Bug ID: 413117 Summary: kio-5.63 makes kdav-19.08.2 fail with HTTP error (400) Product: frameworks-kio Version: 5.63.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: HTTP Assignee: kdelibs-b...@kde.org Reporter: c...@fowelin.de Target Milestone: --- kio-5.63 makes kdav-19.08.2 fail with HTTP error (400) STEPS TO REPRODUCE Install the mentioned packages. Try to connect to a davical server via https. RESULT HTTP error (400). Works with kio-5.62. Reverting commit 9713ea02e49eda11d72e1ac605417dac0dab8c37 "Consider the usage of WebDAV methods sufficient for assuming WebDAV" in kio-5.63 makes kdav work again. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 82053] program is closing without any question about "file is modified.would you like to save it [yes] [no].."
https://bugs.kde.org/show_bug.cgi?id=82053 Brennda Vallejo changed: What|Removed |Added CC||duckpoo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 413116] New: Plasma freezes for few seconds when maximizing window
https://bugs.kde.org/show_bug.cgi?id=413116 Bug ID: 413116 Summary: Plasma freezes for few seconds when maximizing window Product: kwin Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: enautge...@gmail.com Target Milestone: --- SUMMARY When using proprietary nvidia drivers (using an optimus laptop), if the modset is activated (for disabling screen tearing in nvidia chips), and if a window is dragged to the top of screen to maximize, sometimes (about 2/3 times) the screen completely freezes for about 3-6 seconds. In the intel graphics card there isn't any issues. STEPS TO REPRODUCE 1. Install Kubuntu 18.04<(This issue is present in all versions above 18.04, below i haven't tested, as they're unsupported) 2. Install the proprietary nvidia drivers 3. Make a config file such as '/etc/modprobe.d/nvidia-nomodset.conf' and add the following line: 'options nvidia-drm modset=1' to disable screen tearing. 4.Update initramfs of the kernel (# update-initramfs -u) and reboot 5.Maximize any window by dragging to the top of the screen OBSERVED RESULT May the screen freeze for about 3-6 seconds, and then responds maximizing the wanted window, but may occur really often. You may try maximizing until the screen freezes. EXPECTED RESULT Maximize without screen freezes SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.04 and above (available in About System) KDE Plasma Version: 5.16.5 / 5.17 KDE Frameworks Version: 5.56 / 5.62.0 Qt Version: 5.12.2 / 5.12.4 ADDITIONAL INFORMATION When the modset is not activated there are no freezes, but there is screen tearing, which is not possible to fix from the compositor settings. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 413113] ktouch crashes on start
https://bugs.kde.org/show_bug.cgi?id=413113 --- Comment #2 from Alex Bradatan --- With `flatpak run --device=dri org.kde.ktouch` the application launches just fine. If it helps I also attached that output. Since it seems to be dri related, it may be of use to know that I am running a Nvidia gpu with proprietary drivers. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 413113] ktouch crashes on start
https://bugs.kde.org/show_bug.cgi?id=413113 --- Comment #3 from Alex Bradatan --- Created attachment 123294 --> https://bugs.kde.org/attachment.cgi?id=123294=edit terminal output of flatpak run --devices=dri org.kde.ktouch -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412885] Okular does not remember window position
https://bugs.kde.org/show_bug.cgi?id=412885 --- Comment #4 from Nate Graham --- (In reply to Albert Astals Cid from comment #2) > Completely disagree, it's none of the applications responsibility to > position itself. Let the window manager do it's job. > > Moreover in any sane modern windowing system you can't know where you are, > so you can't restore yourself either. That's exactly that I would have said too, except for KWin's developers feel pretty strongly that it's not the window manager's job to remember window positions. See Bug 15329. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413115] New: Screen area does not change when the laptop lid is open or closed
https://bugs.kde.org/show_bug.cgi?id=413115 Bug ID: 413115 Summary: Screen area does not change when the laptop lid is open or closed Product: KScreen Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: adrianoma...@gmail.com Target Milestone: --- SUMMARY I have an external HDMI monitor connected to a laptop. Sometimes I used just the external monitor (with the laptop lid closed), sometimes I use both the external monitor and the laptop screen. Debian Strech used to automatically adjust the screen area when I closed or opened the laptop lid. Now that I am using Debian Buster, the system behaves as the laptop lid was always open, even when it is actually closed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Buster 10 KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION $ xrandr Screen 0: minimum 320 x 200, current 3286 x 1080, maximum 8192 x 8192 eDP-1 connected 1366x768+1920+312 (normal left inverted right x axis y axis) 344mm x 194mm 1366x768 60.00*+ 48.00 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 60.0050.0059.94 1920x1080i60.0060.0050.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0060.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.0050.00 720x576i 50.0050.00 720x480 60.0060.0059.9459.9459.94 720x480i 60.0060.0059.9459.94 640x480 75.0072.8166.6760.0059.9459.94 720x400 70.08 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413114] New: Plasma crashed after clicking on the "Intel P-state and CPUFreq Manager" widget.
https://bugs.kde.org/show_bug.cgi?id=413114 Bug ID: 413114 Summary: Plasma crashed after clicking on the "Intel P-state and CPUFreq Manager" widget. Product: plasmashell Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: roscaale...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.17.0) Qt Version: 5.13.1 Frameworks Version: 5.63.0 Operating System: Linux 4.19.79-2-lts x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I logged in and I first clicked on the "Intel P-state and CPUFreq Manager" widget in the plasma panel. The widget panel appeared for a second and then Plasma crashed and recovered. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3ab43b6c80 (LWP 719))] Thread 13 (Thread 0x7f3a7d4a5700 (LWP 7452)): [KCrash Handler] #6 0x7f3ab8ac0e94 in wl_proxy_marshal_constructor () at /usr/lib/libwayland-client.so.0 #7 0x7f3ab3f954d0 in QtWaylandClient::QWaylandWindow::handleUpdate() () at /usr/lib/libQt5WaylandClient.so.5 #8 0x7f3ab2507b31 in () at /usr/lib/qt/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #9 0x7f3ab959ea72 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f3abac7f0ee in () at /usr/lib/libQt5Quick.so.5 #11 0x7f3abac82fc8 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f3ab8ff75b0 in () at /usr/lib/libQt5Core.so.5 #13 0x7f3ab84e84cf in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f3ab8c812d3 in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f3a7e613700 (LWP 1008)): #0 0x7f3ab921d71f in () at /usr/lib/libQt5Core.so.5 #1 0x7f3ab7364a60 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7f3ab73650a6 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f3ab7365251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3ab921da1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3ab91c44ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f3ab8ff6385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f3ab8ff75b0 in () at /usr/lib/libQt5Core.so.5 #8 0x7f3ab84e84cf in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f3ab8c812d3 in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f3a7ef68700 (LWP 1005)): #0 0x7f3ab84eec45 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f3ab8ffd660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f3ab8ffd752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f3abac82dad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f3abac8305e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f3ab8ff75b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f3ab84e84cf in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f3ab8c812d3 in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f3a8499d700 (LWP 998)): #0 0x7f3ab8c769ef in poll () at /usr/lib/libc.so.6 #1 0x7f3ab7365180 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3ab7365251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3ab921da1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3ab91c44ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3ab8ff6385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f3ab8ff75b0 in () at /usr/lib/libQt5Core.so.5 #7 0x7f3ab84e84cf in start_thread () at /usr/lib/libpthread.so.0 #8 0x7f3ab8c812d3 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7f3a8519e700 (LWP 997)): #0 0x7f3ab8c7242c in read () at /usr/lib/libc.so.6 #1 0x7f3ab73159f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f3ab7363a41 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f3ab7365128 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f3ab7365251 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f3ab921da1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f3ab91c44ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f3ab8ff6385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f3a870b913b in KCupsConnection::run() () at /usr/lib/libkcupslib.so #9 0x7f3ab8ff75b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f3ab84e84cf in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f3ab8c812d3 in clone () at
[ktouch] [Bug 413113] ktouch crashes on start
https://bugs.kde.org/show_bug.cgi?id=413113 --- Comment #1 from Sebastian Gottfried --- Hm, on my computer the flatpak version just launches fine. So I am left to guesswork here. Can please try to run KTouch with: flatpak run --device=dri org.kde.ktouch and report back if this works? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406019] Corrupted image thumbnail on some pictures
https://bugs.kde.org/show_bug.cgi?id=406019 --- Comment #16 from Maik Qualmann --- Git commit 3397546f18a0f15bf8dfecb049f6032e4bcb73d1 by Maik Qualmann. Committed on 17/10/2019 at 20:24. Pushed by mqualmann into branch 'master'. do not try video thumbnail from image type M +2-3core/libs/threadimageio/thumb/thumbnailcreator_engine.cpp https://invent.kde.org/kde/digikam/commit/3397546f18a0f15bf8dfecb049f6032e4bcb73d1 -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 413113] ktouch crashes on start
https://bugs.kde.org/show_bug.cgi?id=413113 Alex Bradatan changed: What|Removed |Added CC||alex.bradata...@yahoo.it -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 413113] New: ktouch crashes on start
https://bugs.kde.org/show_bug.cgi?id=413113 Bug ID: 413113 Summary: ktouch crashes on start Product: ktouch Version: 19.08.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: alex.bradata...@yahoo.it Target Milestone: --- Created attachment 123293 --> https://bugs.kde.org/attachment.cgi?id=123293=edit terminal output of flatpak run org.kde.ktouch SUMMARY ktouch fails to run when launched with flatpak run org.kde.ktouch . Traditionally packaged version, however, works fine. STEPS TO REPRODUCE 1. flatpak run org.kde.ktouch from terminal or execute .desktop OBSERVED RESULT ktouch crashes without reaching gui. Output is attached. EXPECTED RESULT ktouch launches. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.3.6-arch1-1-ARCH KDE Plasma Version: Plasma 5.17 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412885] Okular does not remember window position
https://bugs.kde.org/show_bug.cgi?id=412885 --- Comment #3 from Christoph Feck --- KWin developers say it's the application's job to request placement. IMHO the toolkit should bridge both expectations, and from what I know, KMainWindow used to help there. Not sure what the replacement for Qt5 was. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413111] Breeze Dark and Firefox Light theme conflict
https://bugs.kde.org/show_bug.cgi?id=413111 --- Comment #3 from stevemcqu...@mailinator.com --- apologies, the first attachment "firefox theme settings" (the 97KB one) is a screenshot of Firefox demonstrating the problem. The second attachement labelled that (24KB) is Firefox's theme settings. Not sure how to fix that. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4
https://bugs.kde.org/show_bug.cgi?id=412366 --- Comment #16 from Wolfgang Bauer --- (In reply to Ralf Habacker from comment #15) > (In reply to Ralf Habacker from comment #13) > > > Qt5/KDE5, at which point I would move to KMyMoney 5. > > KHtmlView/KF5 provides the QPainter parameter. This means that there will be > > no issue, if print preview would be added to KF5 port. > > I need to correct this statement: KHTMLView/KF5 also do not has a print > method with QPrinter parameter (see > https://cgit.kde.org/khtml.git/tree/src/khtmlview.h#n200). I filed a bug > report for this (see https://bugs.kde.org/show_bug.cgi?id=405011) But kmymoney 5.x doesn't use KHTML anymore. It can either be built with QtWebKit or QtWebEngine. Or am I misunderstanding something here? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413111] Breeze Dark and Firefox Light theme conflict
https://bugs.kde.org/show_bug.cgi?id=413111 --- Comment #2 from stevemcqu...@mailinator.com --- Created attachment 123292 --> https://bugs.kde.org/attachment.cgi?id=123292=edit KDE GTK application theme -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413111] Breeze Dark and Firefox Light theme conflict
https://bugs.kde.org/show_bug.cgi?id=413111 --- Comment #1 from stevemcqu...@mailinator.com --- Created attachment 123291 --> https://bugs.kde.org/attachment.cgi?id=123291=edit firefox theme settings -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412885] Okular does not remember window position
https://bugs.kde.org/show_bug.cgi?id=412885 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #2 from Albert Astals Cid --- Completely disagree, it's none of the applications responsibility to position itself. Let the window manager do it's job. Moreover in any sane modern windowing system you can't know where you are, so you can't restore yourself either. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413112] New: Can't control most applications' notifications anymore
https://bugs.kde.org/show_bug.cgi?id=413112 Bug ID: 413112 Summary: Can't control most applications' notifications anymore Product: plasmashell Version: 5.17.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: techxga...@outlook.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Back in Plasma 5.16, I was able to control how the notification system will handle applications, like QBitTorrent (i.e. have it placed on the notification drop down without popping up). However, I can't anymore in 5.17. OBSERVED RESULTS I noticed that Discord may notify me, but they don't get sent to the notification tray. SOFTWARE/OS VERSIONS Operating System: Kubuntu 19.10 KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-18-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION Not sure if my snap applications, like Discord was shown before because I couldn't remember. This also applies with KDE Neon. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413111] New: Breeze Dark and Firefox Light theme conflict
https://bugs.kde.org/show_bug.cgi?id=413111 Bug ID: 413111 Summary: Breeze Dark and Firefox Light theme conflict Product: Breeze Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: stevemcqu...@mailinator.com Target Milestone: --- Created attachment 123290 --> https://bugs.kde.org/attachment.cgi?id=123290=edit firefox theme settings SUMMARY Firefox won't fully use a light theme when KDE is overall using a dark theme (Breeze Dark). I've set everything I can think of to 'light' for firefox, but it still shows menus, tooltips, alert boxes in a dark theme, and websites that detect dark/light mode will prefer dark theme. Not sure if the problem is on KDE's end or Firefox's, but it only started recently (today, after a system update). It was working fine (everything light in Firefox) before STEPS TO REPRODUCE 1. Enable Breeze Dark theme in KDE. 2. Set GTK Application styles under settings -> Application Style -> Gnome/GTK Application Style to "breeze" (light) for GTK2 and GTK3. 3. under firefox preferences -> themes, choose "default" or "Light" to see behavior OBSERVED RESULT When firefox is in the "default" theme, everything behaves like it's Breeze Dark, rather than a light theme. Choosing "light" theme will mostly work, except menus, tooltips, alert boxes etc. will still be in a dark theme. Websites like bugzilla.mozilla.org which detect if you're dark/light will detect you as dark mode. setting ui.systemUsesDarkTheme=0 in firefox will make bugzilla revert to light mode, but all the menus, tooltips etc. remain dark. The attached screenshot should show an example. EXPECTED RESULT Firefox in light theme and KDE's GTK theme settings set to "breeze" should have all UI elements appear in light mode. Firefox should think it's a light theme, not dark. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.17 (available in About System) KDE Plasma Version: 5.17 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Firefox Version: 69.0.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 376714] kcmshell5 formats ignores ~/.config/plasma-localerc
https://bugs.kde.org/show_bug.cgi?id=376714 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412948] Deleting a versioned file leaves original hidden in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=412948 --- Comment #5 from Han Holl --- Ok, pity. Thanks for the warning. I'll keep watching the news. I suspect that "delete from Images where name = 'file_v1.jpg'" in my 6.1.0 will also fix the database. Or i could rebuild the entire database occasionally. Cheers, Han Holl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 397760] Plasma ignores /usr/share/X11/locale
https://bugs.kde.org/show_bug.cgi?id=397760 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 337676] Locale format is wrongly formatted
https://bugs.kde.org/show_bug.cgi?id=337676 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 344588] 'Regional Setting - Formats - Region' setting behaves unexpected
https://bugs.kde.org/show_bug.cgi?id=344588 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 353853] Regional settings KCM only provides nds_DE instead of de_DE
https://bugs.kde.org/show_bug.cgi?id=353853 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 362865] Plasma forces my character encoding to US-ASCII
https://bugs.kde.org/show_bug.cgi?id=362865 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #11 from philip mirabelli --- Ok I have checked my shuttle machine and the version of libkgapi is the same as on my other machine i.e. version 19.08.2-1. I have just rechecked editing a .doc file with softoffice Textmaker and it seems to work i.e. no crash bug. I shall continue to edit other files to see if they work seamlessly. On Thu, 2019-10-17 at 14:31 +, David Barchiesi wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #9 from David Barchiesi --- > (In reply to philip mirabelli from comment #8) > > I can confirm I am using: "Name : libkgapi Version: 19.08.2-1":- > > printout from terminal > > > > > > On Thu, 2019-10-17 at 13:15 +, David Barchiesi wrote: > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > --- Comment #7 from David Barchiesi --- > > > (In reply to philip mirabelli from comment #5) > > > > Ok so WPS and Abiword seem to work ok, so its ony Softoffice > > > > Textmaker > > > > that has the issue (and only on the Shuttle machine I have) on > > > > my > > > > other > > > > Fiistu laptop with the same configuration (Arch/KDE etc) it > > > > seems > > > > to > > > > work?? > > > > > > > > On Sun, 2019-10-13 at 13:23 +, Elvis Angelaccio wrote: > > > > > https://bugs.kde.org/show_bug.cgi?id=412791 > > > > > > > > > > --- Comment #3 from Elvis Angelaccio < > > > > > elvis.angelac...@kde.org> > > > > > --- > > > > > (In reply to philip mirabelli from comment #2) > > > > > > Created attachment 123139 [details] > > > > > > kdeinit5-20191010-222009.kcrash.txt > > > > > > > > > > > > Hi, just tried editing an .rtf file and it does the same > > > > > > thing > > > > > > > > > > Using which application? > > > > > > > > > > > archlinux is using version 19.08.2-1 which has the bug fixed. > > > > > Is that the "Shuttle machine" or the "Fiistu laptop"? Do both have > the same > versions of kio-gdrive and libkgapi? > -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 402004] k3b issues System Probe warning for locale when using custom regional settings.
https://bugs.kde.org/show_bug.cgi?id=402004 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 404151] Time Format setting to en_SE results in unrecognized LC_TIME
https://bugs.kde.org/show_bug.cgi?id=404151 Vadym Krevs changed: What|Removed |Added CC||vkr...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413104] Left-click mouse actions on Desktop don't work
https://bugs.kde.org/show_bug.cgi?id=413104 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 412715] Terminology for double-sided printing option is too technical and confusing
https://bugs.kde.org/show_bug.cgi?id=412715 --- Comment #3 from Michael --- This is now fixed upstream. We'll have a clearer print dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 383202] System tray icon's context menu isn't updated properly in plasma/x11
https://bugs.kde.org/show_bug.cgi?id=383202 --- Comment #8 from Konrad Materka --- I had to check :) It is not working on "pure" LXDE. LXDE has a QPA plugin, similar one as KDE has. Run your test application with: XDG_SESSION_DESKTOP=X QT_QPA_PLATFORMTHEME=X ./menubugtest You will see exactly the same results. You can also remove/move the file: /usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/libqtlxqt.so On KDE install package "plasma-integration" (at least on *Ubuntu) at will work correctly, the same as in LXDE. It should be installed by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413110] Plasmashell high CPU, unresponsive, gives "filesystem not responding" with many NFS mounts
https://bugs.kde.org/show_bug.cgi?id=413110 --- Comment #1 from Kevin Liu --- Created attachment 123289 --> https://bugs.kde.org/attachment.cgi?id=123289=edit strace of plasmashell as it loops loading /etc/mtab -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413102] Move "Go up" in Project bin to the toolbar
https://bugs.kde.org/show_bug.cgi?id=413102 Christoph Feck changed: What|Removed |Added Summary|Some wishes |Move "Go up" in Project bin ||to the toolbar --- Comment #1 from Christoph Feck --- I took the liberty to retitle the ticket for the first wish. Every actionable item needs a separate ticket, but regarding the other wishes, these seem nice long-term goals, but no actionable items. Support for more formats would need to go to ffmpeg libraries. The titler is being reworked as a student project; feedback would be needed once it lands. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413110] New: Plasmashell high CPU, unresponsive, gives "filesystem not responding" with many NFS mounts
https://bugs.kde.org/show_bug.cgi?id=413110 Bug ID: 413110 Summary: Plasmashell high CPU, unresponsive, gives "filesystem not responding" with many NFS mounts Product: plasmashell Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DataEngines Assignee: plasma-b...@kde.org Reporter: kevin@potatofrom.space Target Milestone: 1.0 Created attachment 123288 --> https://bugs.kde.org/attachment.cgi?id=123288=edit NFS mtab list SUMMARY On a system with many NFS mounts (desktop doubling as a Kubernetes node for homelab), plasmashell becomes increasingly unresponsive as more and more NFS mounts are created. It uses higher and higher CPU as well. STEPS TO REPRODUCE 1. Mount a ton of NFS shares (cat /etc/mtab | wc -l gives 554) 2. Start plasmashell, view CPU usage and responsivity. Eventually, dozens of "Filesystem at is not responding" notifications show up. OBSERVED RESULT Here is a gdb backtrace of plasmashell while under high load: #0 0x7fd79091921e in _int_malloc () from /nix/store/kksyrix1bpklvgkmvngcv0q9nh8hn2fl-glibc-2.27/lib/libc.so.6 #1 0x7fd79091be7a in malloc () from /nix/store/kksyrix1bpklvgkmvngcv0q9nh8hn2fl-glibc-2.27/lib/libc.so.6 #2 0x7fd79105daf2 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #3 0x7fd79105fc30 in QByteArray::QByteArray(int, Qt::Initialization) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #4 0x7fd79126c218 in ?? () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #5 0x7fd7910d24c8 in QString::toUtf8_helper(QString const&) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #6 0x7fd792d73c11 in QQmlPropertyMap::value(QString const&) const () from /nix/store/mq9ssjnaqs17b9189g14j9znkcjyw3z8-qtdeclarative-5.12.3/lib/libQt5Qml.so.5 #7 0x7fd77c12b39c in Plasma::DataModel::dataUpdated(QString const&, QMap const&) () from /nix/store/hs77gmwd1bx196m498ksyqixqlcwff4y-plasma-framework-5.61.0-bin/lib/qt-5.12.3/qml/org/kde/plasma/core/libcorebindingsplugin.so #8 0x7fd79123f69f in QMetaObject::activate(QObject*, int, int, void**) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #9 0x7fd77c111578 in Plasma::DataSource::newData(QString const&, QMap const&) () from /nix/store/hs77gmwd1bx196m498ksyqixqlcwff4y-plasma-framework-5.61.0-bin/lib/qt-5.12.3/qml/org/kde/plasma/core/libcorebindingsplugin.so #10 0x7fd77c131c0e in Plasma::DataSource::dataUpdated(QString const&, QMap const&) () from /nix/store/hs77gmwd1bx196m498ksyqixqlcwff4y-plasma-framework-5.61.0-bin/lib/qt-5.12.3/qml/org/kde/plasma/core/libcorebindingsplugin.so #11 0x7fd77c113a9d in Plasma::DataSource::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /nix/store/hs77gmwd1bx196m498ksyqixqlcwff4y-plasma-framework-5.61.0-bin/lib/qt-5.12.3/qml/org/kde/plasma/core/libcorebindingsplugin.so #12 0x7fd79123f54e in QMetaObject::activate(QObject*, int, int, void**) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #13 0x7fd7936ad4b8 in Plasma::DataContainer::dataUpdated(QString const&, QMap const&) () from /nix/store/394nk3yny74i5l3b5xbhbjnkvmrfzr0i-plasma-framework-5.61.0/lib/libKF5Plasma.so.5 #14 0x7fd7936b2622 in Plasma::DataContainer::checkForUpdate() () from /nix/store/394nk3yny74i5l3b5xbhbjnkvmrfzr0i-plasma-framework-5.61.0/lib/libKF5Plasma.so.5 #15 0x7fd7936b7d14 in Plasma::DataEngine::timerEvent(QTimerEvent*) () from /nix/store/394nk3yny74i5l3b5xbhbjnkvmrfzr0i-plasma-framework-5.61.0/lib/libKF5Plasma.so.5 #16 0x7fd79123fdab in QObject::event(QEvent*) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Core.so.5 #17 0x7fd791db0471 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Widgets.so.5 #18 0x7fd791db7860 in QApplication::notify(QObject*, QEvent*) () from /nix/store/h3plrbghl3xaf61qnlkp4sdyfplf0ijx-qtbase-5.12.3/lib/libQt5Widgets.so.5 #19 0x7fd791215a09 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
[KScreen] [Bug 413109] After I change the screen resolution on Wayland, "Resolution" dropdown shows the initial resolution on reopening
https://bugs.kde.org/show_bug.cgi?id=413109 --- Comment #1 from Patrick Silva --- Created attachment 123287 --> https://bugs.kde.org/attachment.cgi?id=123287=edit screenshot This issue does not occur on X11. The area above "Resolution" dropdown also shows 1920x1080 instead of 1280x720. I'm attaching a screenshot. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413109] After I change the screen resolution on Wayland, Kscreen shows the initial resolution on reopening
https://bugs.kde.org/show_bug.cgi?id=413109 Patrick Silva changed: What|Removed |Added Summary|After I change the screen |After I change the screen |resolution on Wayland, |resolution on Wayland, |"Resolution" dropdown shows |Kscreen shows the initial |the initial resolution on |resolution on reopening |reopening | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 413109] New: After I change the screen resolution on Wayland, "Resolution" dropdown shows the initial resolution on reopening
https://bugs.kde.org/show_bug.cgi?id=413109 Bug ID: 413109 Summary: After I change the screen resolution on Wayland, "Resolution" dropdown shows the initial resolution on reopening Product: KScreen Version: 5.17.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm Assignee: kscreen-bugs-n...@kde.org Reporter: bugsefor...@gmx.com Target Milestone: --- STEPS TO REPRODUCE 1. start Wayland session 2. open system settings > display and monitor 3. change the screen resolution from 1920x1080 to 1280x720 (the change is successful and "Resolution" dropdown shows 1280x720 , as expected) 4. reopen system settings > display and monitor OBSERVED RESULT "Resolution" dropdown shows 1920x1080 instead of 1280x720 EXPECTED RESULT "Resolution" dropdown always shows the current screen resolution SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.17 KDE Frameworks Version: 5.63 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 412968] List of Values became unresponsive
https://bugs.kde.org/show_bug.cgi?id=412968 Thomas Fischer changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 413008] Incorrect Russian translation for the word "rate"
https://bugs.kde.org/show_bug.cgi?id=413008 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from Nate Graham --- Please report it to Manjaro. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 375012] cannot print in custom dimensions
https://bugs.kde.org/show_bug.cgi?id=375012 --- Comment #16 from bruce.samha...@samhaber.ca --- I am still working towards the upgrade. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 413008] Incorrect Russian translation for the word "rate"
https://bugs.kde.org/show_bug.cgi?id=413008 --- Comment #2 from arti...@artifth.ru --- Oops, sorry, apparently this was a distro-specific dialog. The "kcmshell5 keyboard" dialog shows one with correct translations. -- You are receiving this mail because: You are watching all bug changes.
