[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.
https://bugs.kde.org/show_bug.cgi?id=442187 --- Comment #19 from Alexander Reinholdt --- Continuing my tests, I found out that the shares are obviously correctly added to the menu (the number of actions in the menu is correct), but they are not displayed. What causes this issue, I haven't found out yet, though. Even repainting the whole menu did not fix it. I suspect that I am missing something... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444799] System tray icons size does not decrease
https://bugs.kde.org/show_bug.cgi?id=444799 Bacteria changed: What|Removed |Added CC||dev.bacterios...@aleeas.com --- Comment #1 from Bacteria --- I am able to reproduce it. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87 Qt Version: 5.15.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 410453] Indicate which tasks belong to which desktops when sorting by desktop
https://bugs.kde.org/show_bug.cgi?id=410453 qydwhotm...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||qydwhotm...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from qydwhotm...@gmail.com --- The desktop info should be in the tooltip. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411039] Use the tray / SNI model as an additional source for "what's running" in libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=411039 qydwhotm...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||qydwhotm...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #7 from qydwhotm...@gmail.com --- Can you still reproduce the bug with the latest Telegram? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444764] How do snapping works?
https://bugs.kde.org/show_bug.cgi?id=444764 --- Comment #9 from Hoang Duy Tran --- I agreed with you, there are too many bugs in this report and it cannot be singly handled. The snapping options (shift-s) should be removed if it is NOT YET implemented properly, avoiding all hassles for everyone, programmers as well as users. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 332003] Adapt visualization when window thumbnail data is not available for tooltip
https://bugs.kde.org/show_bug.cgi?id=332003 qydwhotm...@gmail.com changed: What|Removed |Added CC||ncdeh...@gmail.com --- Comment #22 from qydwhotm...@gmail.com --- *** Bug 411336 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411336] Taskbar window thumbnails do not work
https://bugs.kde.org/show_bug.cgi?id=411336 qydwhotm...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE CC||qydwhotm...@gmail.com Status|REPORTED|RESOLVED --- Comment #4 from qydwhotm...@gmail.com --- *** This bug has been marked as a duplicate of bug 332003 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392841] grouped icon in taskmanager does not respond on click after a while.
https://bugs.kde.org/show_bug.cgi?id=392841 qydwhotm...@gmail.com changed: What|Removed |Added CC||qydwhotm...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from qydwhotm...@gmail.com --- Can you still reproduce the bug on 5.23? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442314] Skype call microphone notification
https://bugs.kde.org/show_bug.cgi?id=442314 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.
[Discover] [Bug 443936] Discover crash always
https://bugs.kde.org/show_bug.cgi?id=443936 --- 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.
[okular] [Bug 443928] Manga mode
https://bugs.kde.org/show_bug.cgi?id=443928 --- 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.
[kmymoney] [Bug 443551] Default reconciliation state not used for new entries
https://bugs.kde.org/show_bug.cgi?id=443551 --- 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.
[okular] [Bug 443707] Okular crashes while searching
https://bugs.kde.org/show_bug.cgi?id=443707 --- 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.
[systemsettings] [Bug 443521] Trackpad Disabled on Wayland
https://bugs.kde.org/show_bug.cgi?id=443521 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414121] taskbar freezes if window title updates frequently
https://bugs.kde.org/show_bug.cgi?id=414121 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/675 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414121] taskbar freezes if window title updates frequently
https://bugs.kde.org/show_bug.cgi?id=414121 qydwhotm...@gmail.com changed: What|Removed |Added CC||qydwhotm...@gmail.com Keywords||efficiency -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444804] New: [X11] Odd behaviour when switching desktops while Application Dashboard is open
https://bugs.kde.org/show_bug.cgi?id=444804 Bug ID: 444804 Summary: [X11] Odd behaviour when switching desktops while Application Dashboard is open Product: plasmashell Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: indecisiveautoma...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY When attempting to switch virtual desktops while the Application Dashboard is open, various strange behaviours occur. Firstly, the panel will appear over the dashboard briefly (for about as long as the desktop switching animation would take) and then nothing happens. If one repeatedly presses the shortcut for switching virtual desktops (e.g., Ctrl+Alt+LeftArrow) then a strange animation will play, as if Plasma is trying to switch virtual desktops but then is pulled back. Desktop is not switched. STEPS TO REPRODUCE 1. Open Application Dashboard 2. Perform actions detailed above 3. Unexpected behaviours OBSERVED RESULT Panel appears over Application Dashboard briefly and then nothing happens. If the desktop switching shortcut is pressed repeatedly then a strange animation will play as if Plasma is trying to switch desktops, and then gets pulled back. Desktop is not switched. EXPECTED RESULT I'm honestly not sure what expected/intended behaviour would be. I tested switching desktops with Application Dashboard, Application Launcher, and Application Menu under both X11 and Wayland. Here are their behaviours: X11 - Application Dashboard: Strange behaviour mentioned in this report. - Application Launcher: Stays open across virtual desktops. - Application Menu: Stays open across virtual desktops. Wayland: - Application Dashboard: Stays open on the virtual desktop it was opened on, and allows for switching virtual desktops. The other virtual desktops do NOT have the Application Dashboard, however it will stay open when switching back to the desktop it was opened on. - Application Launcher: Closes when switching virtual desktops. - Application Menu: Closes when switching virtual desktops. In my own PERSONAL opinion, the behaviour that makes the most sense would be that the Application Dashboard, Application Launcher and Application Menu allow for switching virtual desktops AND stay open across all virtual desktops - Essentially the behaviour of the Application Launcher and Application Menu on X11 (meaning as a result, the behaviour of these two on Wayland is incorrect). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.15-arch1-1 (64bit) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434950] Task manager labels disappearing
https://bugs.kde.org/show_bug.cgi?id=434950 qydwhotm...@gmail.com changed: What|Removed |Added CC||qydwhotm...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from qydwhotm...@gmail.com --- Can you reproduce the bug on 5.23? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424131] Right clicking on an option in an app menu also triggers the action
https://bugs.kde.org/show_bug.cgi?id=424131 qydwhotm...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||qydwhotm...@gmail.com --- Comment #2 from qydwhotm...@gmail.com --- Yes, but it can be filtered out. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
https://bugs.kde.org/show_bug.cgi?id=401400 --- Comment #12 from Prajna Sariputra --- Actually, I just realised that there is a key mapping option specifically for the Vi input mode, so simply substituting p with "+p works. Assuming that doesn't break anything else (at least compared to Vim with `set clipboard=unnamedplus`), I guess this bug can be closed then? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401400] kate vi mode does not synchronize content from clipboard
https://bugs.kde.org/show_bug.cgi?id=401400 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #11 from Prajna Sariputra --- > now say you copied some text to the clipboard in any other app, you have the > two options: > - paste that text in kate via Ctrl+V or in vi-mode using "+p > - put/paste the text you yanked previously via the p command So, since that appears to be the intended behaviour, would adding the option to make the p command use the system clipboard (or more generally have the internal/default clipboard be synced to the system one) be considered? Vim does support it via the `set clipboard=unnamedplus` command (not the +clipboard feature since that only enables system clipboard access). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 368858] Steam Big Picture mode shows in all activities thereby breaking it
https://bugs.kde.org/show_bug.cgi?id=368858 indecisiveautoma...@gmail.com changed: What|Removed |Added CC||indecisiveautomator@gmail.c ||om --- Comment #2 from indecisiveautoma...@gmail.com --- This seems to be fixed. Can't reproduce on Plasma 5.23.2 on Arch Linux. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 --- Comment #8 from sparhawk --- Most recently, killing `korganizer` closed half the windows, and killing `korgac` killed the other half. Both processes (re)start when you launch korganizer anyway, so I figure that's fine. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444803] New: Krita crashes (Segmentation Fault)
https://bugs.kde.org/show_bug.cgi?id=444803 Bug ID: 444803 Summary: Krita crashes (Segmentation Fault) Product: krita Version: 4.4.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: drewm...@protonmail.com Target Milestone: --- Krita crashes when starting up. Could be a possible Qt error or a Krita error? STEPS TO REPRODUCE 1. Open a terminal (Konsole in this case) 2. Run Krita via Terminal OBSERVED RESULT: So I ran an update on my machine (running EndeavourOS, which is Arch-based) and now the art program Krita crashes everytime it boots up. I couldn't figure out the solution to this one myself. Here is the error message I got running Krita through the terminal: [drew@DrewPC ~]$ krita Set style "breeze" Icon theme "elementary" not found. Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" Loading plugin "/usr/lib/kritaplugins/kritaseexprgenerator.so" failed, "Cannot load library /usr/lib/kritaplugins /kritaseexprgenerator.so: (libKSeExprUI.so.4: cannot open shared object file: No such file or directory)" qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point QPngHandler: Failed to parse ICC profile QObject::startTimer: Timers cannot have negative intervals /usr/lib/krita-python-libs/krita added to PYTHONPATH QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout qt.gui.icc: fromIccProfile: Invalid ICC profile - invalid white-point libpng error: bad adaptive filter value QImage::scaled: Image is a null image QImage::scaled: Image is a null image 19 -- exe=/usr/bin/krita 13 -- platform=xcb 11 -- display=:0 14 -- appname=krita 17 -- apppath=/usr/bin 10 -- signal=11 10 -- pid=11076 12 -- startupid=0 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = krita path = /usr/bin pid = 11076 KCrash: Arguments: /usr/bin/krita KCrash: Attempting to start /usr/lib/drkonqi Icon theme "elementary" not found. [1]+ Stopped krita QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 14 and type 'Read', disabling... QSocketNotifier: Invalid socket 17 and type 'Read', disabling... Unable to start Dr. Konqi Re-raising signal for core dump handling. [1]+ Segmentation fault (core dumped) krita SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (Kernel: 5.14-14-arch1-1 (64-bit)) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Yosuke Matsumura changed: What|Removed |Added CC||yosukematsum...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443961] plasmashell crashes in StatusNotifierItemSource::id() on launch
https://bugs.kde.org/show_bug.cgi?id=443961 --- Comment #10 from qydwhotm...@gmail.com --- Created attachment 143117 --> https://bugs.kde.org/attachment.cgi?id=143117=edit New crash information added by DrKonqi plasmashell (5.23.80) using Qt 5.15.2 - What I was doing when the application crashed: The crash was deliberately produced. Please ignore it and see https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1166 -- Backtrace (Reduced): #6 0x7f7108097a44 in QString::QString(QString const&) (this=0x7ffd4428c068, other=...) at /usr/include/qt5/QtCore/qstring.h:1093 #10 0x7f71162d8a73 in QModelIndex::data(int) const (arole=364, this=0x7ffd4428c210) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:460 #11 QConcatenateTablesProxyModel::data(QModelIndex const&, int) const (this=, index=, role=364) at itemmodels/qconcatenatetablesproxymodel.cpp:195 #12 0x7f71162e54c1 in QSortFilterProxyModel::data(QModelIndex const&, int) const (this=, index=..., role=364) at itemmodels/qsortfilterproxymodel.cpp:2294 #13 0x7f71162e54c1 in QSortFilterProxyModel::data(QModelIndex const&, int) const (this=, index=..., role=364) at itemmodels/qsortfilterproxymodel.cpp:2294 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444613] KisAnimTimelineFramesView invalid memory access on closing Krita
https://bugs.kde.org/show_bug.cgi?id=444613 Eoin O'Neill changed: What|Removed |Added Keywords||release_blocker -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444613] KisAnimTimelineFramesView invalid memory access on closing Krita
https://bugs.kde.org/show_bug.cgi?id=444613 Eoin O'Neill changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |eoinoneill1...@gmail.com --- Comment #1 from Eoin O'Neill --- I'll take a look at this tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #5 from Matt McDonald --- (In reply to Gabriel from comment #4) > Created attachment 143115 [details] > New crash information added by DrKonqi > > latte-dock (0.10.3) using Qt 5.15.2 > > - What I was doing when the application crashed: > Shortly after waking my computer and unlocking a previous session, I opened > Plasma settings and searched for "feedback." It was around this time that I > noticed the "crashed" frowning icon in Latte Dock. > > Some other info that may be relevant: > - I have a dual-head setup > - My wallpaper on one monitor is static > - The wallpaper on the other monitor changes to a random selection on a > schedule > - One monitor refresh rate is 144Hz; the other is 60Hz > - One monitor is connected via DVI; the other HDMI > - I do not use the standard Plasma panel at all as I replaced it with Latte > Dock and a couple of widgets (Digital Clock, Panon) > > -- Backtrace (Reduced): > #4 0x7ffb8dae6860 in QSGTexture::setFiltering(QSGTexture::Filtering) () > at /usr/lib/libQt5Quick.so.5 > #5 0x7ffb8db17b3c in > QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState > const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 > #6 0x7ffb8dafe41a in > QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch > const*) () at /usr/lib/libQt5Quick.so.5 > #7 0x7ffb8db03b96 in QSGBatchRenderer::Renderer::renderBatches() () at > /usr/lib/libQt5Quick.so.5 > #8 0x7ffb8db045a5 in QSGBatchRenderer::Renderer::render() () at > /usr/lib/libQt5Quick.so.5 I also have a dual-monitor setup, but both monitors are identical models. 1440p 165Hz. It happens about once every 2 or 3 logins. Once I'm logged in and it crashes and I restart it, it usually doesn't crash again for the duration of that session. It also crashes often when coming back to Plasma after shutting down my single-GPU passthrough VM. I'll try to get a backtrace again next time it happens but the drkonqi has been telling me there's no info. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 Matt McDonald changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 444802] Plasma PA doesn't disconnect to a virtual audio device created by Pipewire
https://bugs.kde.org/show_bug.cgi?id=444802 --- Comment #1 from christianarcadio...@gmail.com --- SOFTWARE/OS VERSIONS Windows: NA macOS: NA Linux/KDE Plasma: Garuda Linux KDE Gaming (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 444802] New: Plasma PA doesn't disconnect to a virtual audio device created by Pipewire
https://bugs.kde.org/show_bug.cgi?id=444802 Bug ID: 444802 Summary: Plasma PA doesn't disconnect to a virtual audio device created by Pipewire Product: plasma-pa Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: christianarcadio...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143116 --> https://bugs.kde.org/attachment.cgi?id=143116=edit Carla patchbay screenshots, from fresh reboot to multiple applet open SUMMARY On my machine, I have Pipewire installed as a JACK (and PulseAudio?) replacement. After creating a coupled stream virtual device according to https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#coupled-streams, plasma-pa doesn't disconnect to the virtual device after the applet closes, even though it disconnects from the "built-in" audio devices (observed in Carla patchbay). Also, probably because of that issue, plasma-pa creates new connection ports each time the applet opens, with each new ports connected to the virtual device not disconnecting and further bloating the patchbay. STEPS TO REPRODUCE 1. Install Pipewire and Carla. 2. Create a virtual device, following https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#coupled-streams. 3. Open Carla and go to the patchbay. 4. Open the plasma-pa applet several times. OBSERVED RESULT The Plasma PA 'device' in the Carla patchbay persists, with each call to the applet creating more ports for the virtual device which doesn't close. EXPECTED RESULT The Plasma PA 'device' in the Carla patchbay should properly disappear each time the applet closes. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I have `pipewire-jack-dropin` installed. But it probably shouldn't matter. Pipewire version: Compiled with libpipewire 0.3.39; Linked with libpipewire 0.3.39 Using Carla version 2.4.1 Python version: 3.9.7 Qt version: 5.15.2 PyQt version: 5.15.6x -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444642] Kinoite 35 Flatpak broken read only file system, home directory read only
https://bugs.kde.org/show_bug.cgi?id=444642 Aleix Pol changed: What|Removed |Added CC||trav...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 Gabriel changed: What|Removed |Added CC||accounts@gabriels.house -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438127] Latte Dock Crashes at Login
https://bugs.kde.org/show_bug.cgi?id=438127 --- Comment #4 from Gabriel --- Created attachment 143115 --> https://bugs.kde.org/attachment.cgi?id=143115=edit New crash information added by DrKonqi latte-dock (0.10.3) using Qt 5.15.2 - What I was doing when the application crashed: Shortly after waking my computer and unlocking a previous session, I opened Plasma settings and searched for "feedback." It was around this time that I noticed the "crashed" frowning icon in Latte Dock. Some other info that may be relevant: - I have a dual-head setup - My wallpaper on one monitor is static - The wallpaper on the other monitor changes to a random selection on a schedule - One monitor refresh rate is 144Hz; the other is 60Hz - One monitor is connected via DVI; the other HDMI - I do not use the standard Plasma panel at all as I replaced it with Latte Dock and a couple of widgets (Digital Clock, Panon) -- Backtrace (Reduced): #4 0x7ffb8dae6860 in QSGTexture::setFiltering(QSGTexture::Filtering) () at /usr/lib/libQt5Quick.so.5 #5 0x7ffb8db17b3c in QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState const&, QSGMaterial*, QSGMaterial*) () at /usr/lib/libQt5Quick.so.5 #6 0x7ffb8dafe41a in QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*) () at /usr/lib/libQt5Quick.so.5 #7 0x7ffb8db03b96 in QSGBatchRenderer::Renderer::renderBatches() () at /usr/lib/libQt5Quick.so.5 #8 0x7ffb8db045a5 in QSGBatchRenderer::Renderer::render() () at /usr/lib/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444372] Digital clock shows wrong time zone identifier
https://bugs.kde.org/show_bug.cgi?id=444372 --- Comment #5 from K.J. Petrie --- Europe's turn last week. America's turn this week. LXQT users are also affected so it does look like a QT problem. Does Resolved Upstream mean QT have already found and fixed it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Greg Martyn changed: What|Removed |Added CC||greg.mar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 443118] KDevelop's Problems tool view to list FIXME/TODO comments
https://bugs.kde.org/show_bug.cgi?id=443118 --- Comment #6 from Luke Horwell --- Looking at the source code again, the file "plugins/clang/duchain/todoextractor.cpp" suggests that Clang is used to extract TODO markers, which would confirm by design it's limited to the C family of languages. A solution could be to add logic to the problem reporter's model that parses commented lines (for any known language) against the list of TODO markers. Maybe there's something in KTextEditor/KPart/duchain (whichever handles the syntax highlighting) that can help filter a document's lines to comments only. My C++ is extremely limited, otherwise I'd give it a stab. A workaround for now could be to add an "external script" that executes: "egrep -n 'FIXME|TODO' %f" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 Alex changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=444801 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Alex changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=438839 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash
https://bugs.kde.org/show_bug.cgi?id=438839 --- Comment #33 from Alex --- Per David's request, here is a new bug to track this: https://bugs.kde.org/show_bug.cgi?id=444801 If you still encounter this issue, please post logs there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Alex changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444801] New: Turning monitor off and back on causes plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=444801 Bug ID: 444801 Summary: Turning monitor off and back on causes plasmashell crash Product: plasmashell Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: alex...@protonmail.com Target Milestone: 1.0 This is a new bug to track 438839, which apparently hasn't been fixed, according to comments. Normally, I would mark that bug as re-opened, but David Edmundson specifically requested to create a new bug with new logs if there are still issues. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444800] Discover crashes with error ASSERT: "m_responsePending != pending"
https://bugs.kde.org/show_bug.cgi?id=444800 --- Comment #2 from Ömer Fadıl USTA --- Created attachment 143114 --> https://bugs.kde.org/attachment.cgi?id=143114=edit coredumpctl info -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444800] Discover crashes with error ASSERT: "m_responsePending != pending"
https://bugs.kde.org/show_bug.cgi?id=444800 --- Comment #1 from Ömer Fadıl USTA --- Created attachment 143113 --> https://bugs.kde.org/attachment.cgi?id=143113=edit coredumpctl debug -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444800] New: Discover crashes with error ASSERT: "m_responsePending != pending"
https://bugs.kde.org/show_bug.cgi?id=444800 Bug ID: 444800 Summary: Discover crashes with error ASSERT: "m_responsePending != pending" Product: Discover Version: master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: KNewStuff Backend Assignee: lei...@leinir.dk Reporter: omeru...@gmail.com CC: aleix...@kde.org Target Milestone: --- Discover compiled with kdesrc-build with these compile flags : -DCMAKE_CXX_STANDARD=17 -DCMAKE_BUILD_TYPE=Debug User config / settings everything is clean ( completely recreated user just before kdesrc-build ) Whenever I try to launch(run) it crashes coredumpctl info and coredumpctl debug will be attached. *** journald log gives this warnings/errors before/after crash : systemd[1230]: Started Discover - Software Center. plasmashell[1319]: file:///home/kde-dev/kde/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:366: Unable to assign [undefined] to QString plasma-discover[3486]: qrc:/qml/DiscoverDrawer.qml:70: TypeError: Cannot read property 'objectName' of null plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: kf.newstuff.core: The CustomName property is deprecated and will be removed in KF6 plasma-discover[3486]: adding empty sources model QStandardItemModel(0x55fc214de8a0) systemd[1]: Starting Snap Daemon... snapd[3507]: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network plasma-discover[3486]: org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend" snapd[3507]: daemon.go:248: started snapd/2.51.3-2 (series 16; classic; devmode) manjaro/ (amd64) linux/5.14.15-1-MANJARO. kernel: loop0: detected capacity change from 0 to 8 systemd[1]: tmp-sanity\x2dmountpoint\x2d321404357.mount: Deactivated successfully. plasma-discover[3486]: file:///home/kde-dev/kde/usr/lib/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value" snapd[3507]: daemon.go:341: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap) systemd[1]: Started Snap Daemon. audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=snapd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' kernel: audit: type=1130 audit(1635809226.189:325): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=snapd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' plasma-discover[3486]: org.kde.plasma.discover: couldn't open file "/home/kde-dev/.cache/discover/featured-5.9.json" "No such file or directory" PackageKit[1433]: get-updates transaction /15_cbdcaddc from uid 1001 finished with success after 473ms plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 2)" plasma-discover[3486]: kf.newstuff.core: Could not find category "Cantor (Python 3)" plasma-discover[3486]:
[plasmashell] [Bug 443502] System tray settings does not work on Wayland
https://bugs.kde.org/show_bug.cgi?id=443502 Andreas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444799] System tray icons size does not decrease
https://bugs.kde.org/show_bug.cgi?id=444799 Andreas changed: What|Removed |Added CC||opendr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442219] Hotkeys + Window shortcut rules
https://bugs.kde.org/show_bug.cgi?id=442219 --- Comment #8 from Dominik Kummer --- @Ismael I think the icons-only task manager is focused more on mouse usage. Now I use Meta+Alt+D to launch Dolphin instance and Meta+D to focus first instance. Having Meta+D cycle focus multiple instances, or launch a new instance if no instance is launched, could shorten the formula. But this can be solved with Custom Shortcuts and scripts also. Could Custom Shortcuts Settings be the right place to manage more specific shortcut behavior? (KWin Rule Shortcuts should btw also be transparently listed there.) Besides "Global Shortcuts" it is already possible to define "Window Actions" there. But right now it is not possible to Trigger Window Actions with Global Shortcuts. I think that is the missing link which is currently implemented with Window Rules Shortcut. I like the idea of "visual scripting" dbus methods, thats what Custom Shortcuts is already aiming for I guess. ps: sorry for spamming, I just forgot about this bug report *facepalm* -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444799] New: System tray icons size does not decrease
https://bugs.kde.org/show_bug.cgi?id=444799 Bug ID: 444799 Summary: System tray icons size does not decrease Product: plasmashell Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: opendr...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 143112 --> https://bugs.kde.org/attachment.cgi?id=143112=edit system tray setting at "small" SUMMARY In the system tray, if I set the size of the icons to small in the settings, then their size does not decrease, instead, the distance between the icons increases. STEPS TO REPRODUCE 1. Open system tray settings -> General 2. Switch from "scale to panel size" to "small" OBSERVED RESULT icons size does not decrease EXPECTED RESULT the size of the icons should be reduced SOFTWARE/OS VERSIONS Linux: OpenSUSE Tumbleweed KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444798] Possible issue with layer styles causing files to become unusable
https://bugs.kde.org/show_bug.cgi?id=444798 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Can you please attach an example file that crashes for you? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 444797] Window trying to center between displays
https://bugs.kde.org/show_bug.cgi?id=444797 --- Comment #1 from Cameron --- Created attachment 143111 --> https://bugs.kde.org/attachment.cgi?id=143111=edit yakuake at 100% size / width, with content on 2 displays -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444798] Possible issue with layer styles causing files to become unusable
https://bugs.kde.org/show_bug.cgi?id=444798 Jaiden Williams changed: What|Removed |Added Version|unspecified |5.0.0-beta2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444798] New: Possible issue with layer styles causing files to become unusable
https://bugs.kde.org/show_bug.cgi?id=444798 Bug ID: 444798 Summary: Possible issue with layer styles causing files to become unusable Product: krita Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: jaw12...@gmail.com Target Milestone: --- SUMMARY I have been using multiple layer styles on my images, and after saving said files, and attempting to load them again, they have become unusable and apparently unrecoverable on current versions of krita next. Im not sure how to specifically replicate it however i have some general guides STEPS TO REPRODUCE 1. add a layer style (ones i use are outer glow or stroke), with default settings 2. apply a gradient to the effect, and choose one in the list of custom gradients 3. effect will work for the remainder of the session, if saved and reopened, it crashes OBSERVED RESULT File will no longer open, krita crashes upon attempting to load EXPECTED RESULT For the file to load SOFTWARE/OS VERSIONS Windows: 10/11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444796] Reverting display settings selects leftmost screen in screens list
https://bugs.kde.org/show_bug.cgi?id=444796 indecisiveautoma...@gmail.com changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 444797] New: Window trying to center between displays
https://bugs.kde.org/show_bug.cgi?id=444797 Bug ID: 444797 Summary: Window trying to center between displays Product: yakuake Version: 21.08.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: k...@ccontour.com Target Milestone: --- Created attachment 143110 --> https://bugs.kde.org/attachment.cgi?id=143110=edit yakuake window centered between 2 displays, with display arrangement settings visible SUMMARY Yakuake is incorrectly centering the window when using in a multi display setup. I am using a laptop, with an external monitor. While the laptop screen is closed, everything works as expected. When height / width is set to 100%, the window will take up the correct monitor + position most of the time (using the global open keybind). It will frequently shift the open position to be partly on each display. When height / width is set to 70%, the yakuake will hug the left side of the right display (still not correctly centered), but does not cross between displays like 100% does. STEPS TO REPRODUCE No special steps. Just multi monitor + global activate button OBSERVED RESULT See attached screenshot EXPECTED RESULT The window should correctly center itself on the desired display the same way that happens in single displays. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444796] New: Reverting display settings selects leftmost screen in screens list
https://bugs.kde.org/show_bug.cgi?id=444796 Bug ID: 444796 Summary: Reverting display settings selects leftmost screen in screens list Product: systemsettings Version: 5.23.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: indecisiveautoma...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY On both X11 and Wayland, when clicking the "revert" button after changing display settings, the leftmost screen in the screens list gets selected. STEPS TO REPRODUCE 1. Change display setting that will prompt a revert (e.g., refresh rate) 2. Click the "Revert" button 3. Leftmost screen will be selected OBSERVED RESULT Reverting display settings will select the leftmost screen and display options for that screen. EXPECTED RESULT Reverting display settings should keep the currently selected screen selected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.15-arch1-1 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Affects both X11 and Wayland. -- You are receiving this mail because: You are watching all bug changes.
[releaseme] [Bug 444795] New: Using KDE_L10N_SYNC_TRANSLATIONS option does not lead to compiling translations
https://bugs.kde.org/show_bug.cgi?id=444795 Bug ID: 444795 Summary: Using KDE_L10N_SYNC_TRANSLATIONS option does not lead to compiling translations Product: releaseme Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ash...@linuxcomp.ru CC: sit...@kde.org Target Milestone: --- When user uses cmake option KDE_L10N_SYNC_TRANSLATIONS, he expect that the translations will be downloaded and built. However, it does not happen. I tried to understand how things work. The l10n.rb defines get method with the parameter edit_cmake which defaults to true: https://invent.kde.org/sdk/releaseme/-/blob/b830efbdd392150b0b56e944bb34c07606492d4b/lib/releaseme/l10n.rb#L29-30 That edit_cmake means the following lines will be added to cmakelists.txt (as needed): ``` find_package(KF5I18n CONFIG REQUIRED) ki18n_install(po) ``` The tarme.rb calls that method without specifying edit_cmake parameter: https://invent.kde.org/sdk/releaseme/-/blob/b830efbdd392150b0b56e944bb34c07606492d4b/tarme.rb#L81 and it becomes true (because of default in l10n.rb) and prepared tar will have edited cmakelists.txt. The fetchpo.rb when running invoking get method specify the edit_cmake to false: https://invent.kde.org/sdk/releaseme/-/blob/b830efbdd392150b0b56e944bb34c07606492d4b/fetchpo.rb#L60-61 so running it will not trigger editing cmakelists.txt But that fetchpo.rb is invoked by cmake module KDECMakeSettings.cmake: https://invent.kde.org/frameworks/extra-cmake-modules/-/blob/8f7831c83f11f38c060fd0717b925b1fa28cd3d8/kde-modules/KDECMakeSettings.cmake#L356-361 The result is that the translations are not compiled to the package. STEPS TO REPRODUCE 1. git clone https://invent.kde.org/pim/zanshin.git 2. mkdir build 3. cd build 4. cmake -B . -S ../zanshin -DBUILD_TESTING=OFF -DKDE_L10N_SYNC_TRANSLATIONS=ON 6. cmake --build . 7. DESTDIR="$pkgdir" cmake --install build # from package() function in PKGBUILD OBSERVED RESULT The translations were downloaded, but not compiled. The built package does not contain translations. EXPECTED RESULT The translations are downloaded and compiled. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The solution could be to make fetchpo.rb to be able to accept parameter --edit-cmake, and pass it to the get method. And then two variants to do: Variant 1: Then add "--edit-cmake TRUE" to fetch_commands in the KDECMakeSettings.cmake. Variant 2: Make --edit-cmake parameter default to true in fetchpo.rb. Then editing KDECMakeSettings.cmake will not be necessary. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442743] Reverting screen rotation does not reset UI
https://bugs.kde.org/show_bug.cgi?id=442743 indecisiveautoma...@gmail.com changed: What|Removed |Added CC||indecisiveautomator@gmail.c ||om --- Comment #3 from indecisiveautoma...@gmail.com --- This also affects display scale. If reverting the changed display options for scale, even though the setting successfully reverts, the slider will not revert with it. If you were to set, say, 150% scale up from 100% scale and then revert, the display will go back to 100% scale but the slider will stay at 150%. It seems like these issues may be related, but should this be opened as a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 Brendon Higgins changed: What|Removed |Added CC||bren...@quantumfurball.net --- Comment #7 from Brendon Higgins --- I'm getting this lately, too (on Debian testing). Sometimes it's 4 windows, sometimes it's 63. To save RSI, I've found that if you have grouping enabled on the taskbar, you can close a bunch at once by right-clicking on the taskbar group. Doesn't close all of them, but for 63 windows it only takes about 6 clicks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444589] [libinput] [wayland] Keyboard repead rate is limited to about 60 repeats/s in Kirigami apps and some Plasma applets (QML Apps?)
https://bugs.kde.org/show_bug.cgi?id=444589 --- Comment #19 from Andrey --- (In reply to Till Schäfer from comment #17) > I was wondering if > flatpak is tampering with something of the graphics or input stack. like > vsync or so. >From system POV it's just usual app but sandboxed. It speaks Wayland and runs with restricted permissions, so nothing unusual it can do system-wise.. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444589] [libinput] [wayland] Keyboard repead rate is limited to about 60 repeats/s in Kirigami apps and some Plasma applets (QML Apps?)
https://bugs.kde.org/show_bug.cgi?id=444589 --- Comment #18 from Andrey --- Still it might be a regression, so it's worth to test it maybe in VM with Neon (but not sure if such kind of test is correct on VMs). You could test first your distro on VM to make sure the issue happens there, then test a Neon. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444589] [libinput] [wayland] Keyboard repead rate is limited to about 60 repeats/s in Kirigami apps and some Plasma applets (QML Apps?)
https://bugs.kde.org/show_bug.cgi?id=444589 --- Comment #17 from Till Schäfer --- (In reply to Andrey from comment #16) > (In reply to Till Schäfer from comment #15) > > I was wondering why qt 5.15.3 is used since this version is non-free. Maybe > > there is a qt fix upstream available? > Where do you see this info? In the about dialog of Elisa. > It uses org.kde.Platform runtime which AFAIK is opensource-only: > https://github.com/flathub/org.kde.elisa/blob/master/org.kde.elisa.json > It might include KDE Qt patches collection, though. Still it's interesting > indeed how 5.15.3 has arose.. > > Anyway, do you think we should close this as not relevant to KDE? No, this bug is happening on the normal KDE up to date stack and it is a wayland regression over X11 (both, the native as well as the flatpak version are running natively on wayland). We are not sure that, qt (i.e. out of control from KDEs point of view) is actually the cause. I was wondering if flatpak is tampering with something of the graphics or input stack. like vsync or so. I find an unpredictable (depending on system load, type of application) repeat speed of my keyboard annoying, since it makes input non-intuitive. I think for fast repeat speeds you o not really look precisely about the things happening, but predict the cause of your action. Thus, this makes high repeat speed unusable to me. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425385] Desktop freezes after taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=425385 --- Comment #50 from Nick Stefanov --- I see :) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425385] Desktop freezes after taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=425385 --- Comment #49 from Antonio Prcela --- (In reply to Nick Stefanov from comment #48) > With spectacle -ac it's working fine but it takes screenshot of the whole > screen :) Ah, nvm, "-c" works only when used with "-b". And "-a" should take a screenshot of the active window, except when your "active window" is the desktop. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-purpose] [Bug 444794] New: Bluetooth sharing requires bluedevil-sendfile
https://bugs.kde.org/show_bug.cgi?id=444794 Bug ID: 444794 Summary: Bluetooth sharing requires bluedevil-sendfile Product: frameworks-purpose Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: nicolas.fe...@gmx.de Target Milestone: --- The bluetooth plugin uses the bluedevil-sendfile command under the hood. This is problematic for multiple reasons: - It most likely doesn't work from flatpak'd apps - It assumes that bluedevil is installed, which it usually isn't when the user is not using Plasma We probably should use bluez-qt to talk to bluez directly from Purpose instead of going via a helper tool -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428243] Cannot select initial picture for a user
https://bugs.kde.org/show_bug.cgi?id=428243 --- Comment #4 from Alexander Potashev --- Cannot reproduce on Plasma 5.22.5. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444770] Tooltip mentions a button to install missing translations that does not exist
https://bugs.kde.org/show_bug.cgi?id=444770 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- Hmm, that doesn't seem possible, yet is is. The warning icon appears when `visible: model.IsIncomplete` is true, but the "Install missing packages" button also has the same condition for visibility. I don't understand how it could be that one is shown but not the other. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 384652] [RFE] [Openconnect] pkcs11: add support for separate pin value
https://bugs.kde.org/show_bug.cgi?id=384652 Anthony Rabbito changed: What|Removed |Added CC||he...@anthonyrabbito.com --- Comment #7 from Anthony Rabbito --- Has this been implemented? I can really use this.. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444772] Unexpected behavior of popup to add language: it opens with languages list scrolled down and moves vertically when I scroll the languages list up
https://bugs.kde.org/show_bug.cgi?id=444772 Nate Graham changed: What|Removed |Added Severity|normal |minor CC||n...@kde.org --- Comment #1 from Nate Graham --- This is actually the intended way that Kirigami.OverlaySheet works. I cannot reproduce the issue specific to this KCM of the sheet sharting scrolled to somewhere in the middle, though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444589] [libinput] [wayland] Keyboard repead rate is limited to about 60 repeats/s in Kirigami apps and some Plasma applets (QML Apps?)
https://bugs.kde.org/show_bug.cgi?id=444589 --- Comment #16 from Andrey --- (In reply to Till Schäfer from comment #15) > I was wondering why qt 5.15.3 is used since this version is non-free. Maybe > there is a qt fix upstream available? Where do you see this info? It uses org.kde.Platform runtime which AFAIK is opensource-only: https://github.com/flathub/org.kde.elisa/blob/master/org.kde.elisa.json It might include KDE Qt patches collection, though. Still it's interesting indeed how 5.15.3 has arose.. Anyway, do you think we should close this as not relevant to KDE? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 444793] New: Segfault on startup after failing to load layout
https://bugs.kde.org/show_bug.cgi?id=444793 Bug ID: 444793 Summary: Segfault on startup after failing to load layout Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: alex.de...@gmx.co.uk Target Milestone: --- SUMMARY When starting the latest version of lattedock, I get a segfault before the application even starts up. After debugging it seems that there's a null pointer dereference happening here: https://github.com/KDE/latte-dock/blob/90405fef8a6e7ec272ded6ffb807fe2ac6daf978/app/layouts/synchronizer.cpp#L640 SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS (unstable channel) (available in About System) KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444757] albums empty
https://bugs.kde.org/show_bug.cgi?id=444757 --- Comment #5 from Maik Qualmann --- You can simply copy only back the digikam4.db from the backup. All images that have been changed / deleted or added in the meantime will be updated again. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444589] [libinput] [wayland] Keyboard repead rate is limited to about 60 repeats/s in Kirigami apps and some Plasma applets (QML Apps?)
https://bugs.kde.org/show_bug.cgi?id=444589 --- Comment #15 from Till Schäfer --- (In reply to Andrey from comment #14) > Could you test Flathub version? It should be better chances we get similar > results: > https://flathub.org/apps/details/org.kde.elisa Hmm, the flatpack version does not seem to be affected. Weired. About says. elisa 21.08.2 frameworks 5.86 qt 5.15.3 I was wondering why qt 5.15.3 is used since this version is non-free. Maybe there is a qt fix upstream available? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444764] How do snapping works?
https://bugs.kde.org/show_bug.cgi?id=444764 Tiar changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #8 from Tiar --- I'm sorry, but this is not a valid bug report. A valid bug report only reports exactly one issue, is very precise and actionable by the programmer. Your issues seem to be more suitable for a discussion on our forum on krita-artists.org . Since some of what you ask for are things that are not implemented yet, please read this instruction to learn how to make a good feature request: https://docs.krita.org/en/untranslatable_pages/new_features.html (feature requests should be posted on krita-artists.org forum as well, not here on bugs.kde.org, which is a place for bug reports). Then make a post on krita-artists.org according to the instruction. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444624] Unable to change user/group of an element from the desktop
https://bugs.kde.org/show_bug.cgi?id=444624 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kio/-/merge_requests/623 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 444624] Unable to change user/group of an element from the desktop
https://bugs.kde.org/show_bug.cgi?id=444624 --- Comment #3 from Ahmad Samir --- Note that you can only change the user if you're root, otherwise the user combobox isn't shown. So it's only the group combobox that's not working here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 436286] Cannot embed face tags into JPG image with Exiv2 and "apple-fi" XMP namespace. Use ExifTool instead
https://bugs.kde.org/show_bug.cgi?id=436286 --- Comment #23 from MarcP --- Hi, I'm not sure of the status of this bug, or if it's the same thing I have experienced (I mentioned it in the mailing list about a month ago). Basically what I see is that some pictures taken from an iPhone have defective or corrupted metadata, which appears in digikam as a "flat" tag list, instead of seeing the keywords on a tree. On top of that, this issue seems to be limited to those pictures with people in it. And I have observed that the same problematic pictures are displayed correctly (with a hierarchical tag tree) in Digikam 7.3, but the problem appears if you see them in Digikam 7.4. Could it be some change between these two versions that changed how metadata is interpreted? Some of the pictures I'm seeing with this problem now are some that I took years ago and worked fine until now. For now on, the only solution I have for this problem is placing the problematic pictures in a folder and run the following to fix the metadata: exiftool -XMP:All -TagsFromFile @ -XMP:all *.JPG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444770] Tooltip mentions a button to install missing translations that does not exist
https://bugs.kde.org/show_bug.cgi?id=444770 Patrick Silva changed: What|Removed |Added CC||p.r.worr...@gmail.com --- Comment #2 from Patrick Silva --- *** Bug 444780 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444780] Language KCM has message about "Install Missing Packages button" that does not seem to exist
https://bugs.kde.org/show_bug.cgi?id=444780 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 444770 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444757] albums empty
https://bugs.kde.org/show_bug.cgi?id=444757 --- Comment #4 from Nadine --- I have saved a copy of each of the database files from early September. Can I use the previous copy of digikam4.db instead of creating a new database? Can I just reclaim digikam4.db or must I reclaim all 4 files? How much data will I lose by creating a new database? Thank you so much for your quick responses. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444710] "Always shown" visibility mode does not work consistently with "Automatic Load" applets
https://bugs.kde.org/show_bug.cgi?id=444710 Nate Graham changed: What|Removed |Added Summary|'Always shown' visibility |"Always shown" visibility |mode does not work |mode does not work |consistently with Media |consistently with |Player applet in system |"Automatic Load" applets |tray| Severity|normal |minor Status|REPORTED|CONFIRMED CC||ahiems...@heimr.nl, ||n...@kde.org, ||notm...@gmail.com Component|Media Player|System Monitor Ever confirmed|0 |1 Assignee|k...@privat.broulik.de |plasma-b...@kde.org --- Comment #1 from Nate Graham --- The Media Player applet is an "Automatic Load" applet, which means it actually disappears completely when not needed. We could perhaps remove the "always show" option for these applets, or instead make it override the applet's ehavior to disappear when it believes it's not needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442386] Prefer EGL to GLX for GL support also on X11
https://bugs.kde.org/show_bug.cgi?id=442386 --- Comment #4 from C. Leu --- Again a short update. During the last few weeks it has been shown that the best way to enforce EGL in kwin is through the "KWIN_OPENGL_INTERFACE=EGL" and not the "KWIN_COMPOSE=O2ES" variable. This will effectively keep the OpenGL 2.0 or OpenGL 3.1 "function feature set" and just force EGL over GLX. sudo nano /etc/profile.d/kwin.sh export KWIN_OPENGL_INTERFACE=EGL The first mentioned "KWIN_COMPOSE=O2ES" environment variable is also applicable but it will additionally switch the compositing to OpenGL ES 2.0. Just to be clear, this is perfect for weaker hardware like single core Netbooks, AIO computers, or older systems with limited GPU functionality. Such lower-end systems may benefit significantly from the OpenGL ES 2.0 mode, like the previously mentioned Apple iMac5,1 from 2006. However, the OpenGL ES 2.0 compositing may limit in certain situations some enhanced graphical effects of a theme. I can confirm this now for the "Se7en Aero" global design which shows partially missing elements. For example, all frames in dolphin are becoming "transparent". This is not the case regarding the regular OpenGL backend in conjunction with EGL. It should also be noted that this is not the case for the standard (more basic) KDE designs "Breeze" and "Breeze-Dark", - they work fine even with only OpenGL ES 2.0 feature set. Whatever, maybe there will be in the future beside a Vulkan additionally also an OpenGL ES 3.0 rendering backend, - it would allow more effects on weaker hardware. ;-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 444707] Name of SDDM theme is incorrectly aligned in SDDM KCM
https://bugs.kde.org/show_bug.cgi?id=444707 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kdeclarative/-/merge_requests/88 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 --- Comment #5 from Josef Ludvicek --- Same issue on Kubuntu 21.04 yakuake -v yakuake 20.12.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444661] When using a top panel (Application Menu Bar), dragging a Firefox tab to the top of the screen does not maximize the window.
https://bugs.kde.org/show_bug.cgi?id=444661 --- Comment #2 from evanmoh...@gmail.com --- It definitely occurs in X11, and I'm fairly sure it occurs on Wayland as well. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 444792] New: KPA crashes when a KIM containing only video clips (as sidecar files) is imported
https://bugs.kde.org/show_bug.cgi?id=444792 Bug ID: 444792 Summary: KPA crashes when a KIM containing only video clips (as sidecar files) is imported Product: kphotoalbum Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kpab...@willden.org Reporter: schleth...@web.de Target Milestone: --- Application: kphotoalbum (v5.8.1-21-g7f709159) Qt Version: 5.12.7 Frameworks Version: 5.76.0 Operating System: Linux 5.3.18-59.27-default x86_64 Windowing system: X11 Distribution: openSUSE Leap 15.3 -- Information about the crash: - What I was doing when the application crashed: I was trying to recreate the videothumbnails for a few clips. So I exported them to a *kim file with the clips copied next to the *kim. Then I deleted the clips in the data base and on disk (at their original location) from KPA. On importing this *kim back into KPA, KPA crashes after finishing the dialog for the import location and the categories. Twice. KPA is v5.8.1-21-g7f709159 KDE Frameworks 5.76.0 Qt 5.12.7 (kompiliert gegen 5.12.7) The crash can be reproduced every time. -- Backtrace: Application: KPhotoAlbum (kphotoalbum), signal: Segmentation fault [KCrash Handler] #4 0x0047dcea in QString::QString (this=0x7ffd76cee6c8, other=...) at /usr/include/qt5/QtCore/qstring.h:957 #5 0x00587a7f in DB::ImageInfo::label (this=0x0) at /home/usr/src/kphotoalbum-git/kphotoalbum/DB/ImageInfo.cpp:105 #6 0x005c59d3 in ImportExport::MD5CheckPage::clashes (settings=...) at /home/usr/src/kphotoalbum-git/kphotoalbum/ImportExport/MD5CheckPage.cpp:105 #7 0x005c4d5b in ImportExport::MD5CheckPage::pageNeeded (settings=...) at /home/usr/src/kphotoalbum-git/kphotoalbum/ImportExport/MD5CheckPage.cpp:29 #8 0x005c2137 in ImportExport::ImportDialog::possiblyAddMD5CheckPage (this=0x7ffd76cef990) at /home/usr/src/kphotoalbum-git/kphotoalbum/ImportExport/ImportDialog.cpp:383 #9 0x005c1b6a in ImportExport::ImportDialog::next (this=0x7ffd76cef990) at /home/usr/src/kphotoalbum-git/kphotoalbum/ImportExport/ImportDialog.cpp:324 #10 0x7fc3f310bfcf in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #11 0x7fc3f4049ec2 in QAbstractButton::clicked(bool) () from /usr/lib64/libQt5Widgets.so.5 #12 0x7fc3f404a0da in ?? () from /usr/lib64/libQt5Widgets.so.5 #13 0x7fc3f404b4ba in ?? () from /usr/lib64/libQt5Widgets.so.5 #14 0x7fc3f404b6ad in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7fc3f3fa22a8 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7fc3f3f61f9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #17 0x7fc3f3f6a488 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #18 0x7fc3f30dc3a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #19 0x7fc3f3f68a7f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7fc3f3fbcf81 in ?? () from /usr/lib64/libQt5Widgets.so.5 #21 0x7fc3f3fbfdda in ?? () from /usr/lib64/libQt5Widgets.so.5 #22 0x7fc3f3f61f9c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7fc3f3f695b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7fc3f30dc3a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #25 0x7fc3f36e34e5 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #26 0x7fc3f36e4835 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5 #27 0x7fc3f36be2bb in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #28 0x7fc3e66f625a in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #29 0x7fc3ebc48694 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #30 0x7fc3ebc48a30 in ?? () from /usr/lib64/libglib-2.0.so.0 #31 0x7fc3ebc48abc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #32 0x7fc3f313942f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #33 0x7fc3f30da5fa in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #34 0x7fc3f4154367 in QDialog::exec() () from /usr/lib64/libQt5Widgets.so.5 #35 0x005bed52 in ImportExport::ImportDialog::exec (this=0x7ffd76cef990, kimFileReader=0x7ffd76cef970, kimFileURL=...) at
[krita] [Bug 444791] Abnormal undo function when using the Transform tool
https://bugs.kde.org/show_bug.cgi?id=444791 --- Comment #2 from thetwo <310732...@qq.com> --- (In reply to Tiar from comment #1) > Do I assume correctly it doesn't happen this way in Krita 4.x? I don‘t know.. But it would be better if it was synchronized with the Bezier curve tool, which also does undo operations properly while it is running. In contrast, the undo of the Transform tool is redundant and inconvenient -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444791] Abnormal undo function when using the Transform tool
https://bugs.kde.org/show_bug.cgi?id=444791 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Do I assume correctly it doesn't happen this way in Krita 4.x? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425385] Desktop freezes after taking a screenshot
https://bugs.kde.org/show_bug.cgi?id=425385 --- Comment #48 from Nick Stefanov --- With spectacle -ac it's working fine but it takes screenshot of the whole screen :) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428242] User configuration doesn't open on double-click
https://bugs.kde.org/show_bug.cgi?id=428242 --- Comment #4 from Alexander Potashev --- Cannot reproduce anymore on Plasma 5.22.5. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444791] New: Abnormal undo function when using the Transform tool
https://bugs.kde.org/show_bug.cgi?id=444791 Bug ID: 444791 Summary: Abnormal undo function when using the Transform tool Product: krita Version: 5.0.0-beta2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: 310732...@qq.com Target Milestone: --- STEPS TO REPRODUCE 1. Draw two strokes with the brush, then click with the Transform tool 2. Use the shortcut key for undo, it takes two times to undo the box of the Transform tool 3. With the "undo history docker" undo, you click on the undo strokes since the Transform operation does not appear. But instead of the stroke disappearing, the outer frame of the Transform tool disappears EXPECTED RESULT When using the shortcut keys, we can undo the outer frame of the Transform tool at once When using "undo history docker", unframe the Transform tool and perform an undo operation (just like Bezier curve tool) -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 434308] Bluetooth headset broken in multi user environment
https://bugs.kde.org/show_bug.cgi?id=434308 Eridani Rodríguez changed: What|Removed |Added CC||eridanired...@yahoo.com.mx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444774] QML ConnectionItem: Binding loop detected
https://bugs.kde.org/show_bug.cgi?id=444774 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- I vaguely recall fixing this recently and cannot reproduce the issue with the git master version. Can you check that out and see if it's fixed for you too? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 Nate Graham changed: What|Removed |Added CC||n...@kde.org Component|general |generic-crash Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444769] Wayland display scale inconsistent
https://bugs.kde.org/show_bug.cgi?id=444769 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #5 from Nate Graham --- The plasma panel and icons being bigger is expected; you asked the system to make everything 25% bigger, so Plasma and Info Center obliged and made stuff 25% bigger. The fact that it *doesn't* do this on X11 is a bug, but one that people have gotten so used to that fixing it seems like a bug! But it is not; it is a feature. :) The fact that pixel-aligned graphics look blurry when scaled up 25% is also expected and pretty much unfixable; If you scale up something that is pixel-aligned by a non-integer amount, it it no longer pixel-aligned, and the result is blurriness if you have a lower resolution screen. The blurriness in Firefox is for two reasons: 1. it is being run as an XWayland app, and XWayland apps are blurry at any scale above 100% 2. Even if it was run as a native Wayland app, Wayland does not have non-blurry fractional scaling yet. Scaling is only nice and sharp and crisp for native wayland apps if you use 200%, 300%, etc. -- You are receiving this mail because: You are watching all bug changes.
[blogilo] [Bug 444790] New: Cannot write in Blogilo edit window
https://bugs.kde.org/show_bug.cgi?id=444790 Bug ID: 444790 Summary: Cannot write in Blogilo edit window Product: blogilo Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mehrdad.mom...@gmail.com Reporter: gaston.verhu...@telenet.be Target Milestone: --- Created attachment 143109 --> https://bugs.kde.org/attachment.cgi?id=143109=edit Screenshot of Blogio editor SUMMARY Starting in Fedora 34, I cannot write in text edit window, because of that window is not empty to write. Because text option buttons are in that window, and not above the window. STEPS TO REPRODUCE 1. Start or restart the program. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 (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.
[krunner] [Bug 444762] Krunner doesn't stay in center after displaying many results
https://bugs.kde.org/show_bug.cgi?id=444762 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444760] Allow configuring the locations of the publicshare and templates folders
https://bugs.kde.org/show_bug.cgi?id=444760 Nate Graham changed: What|Removed |Added Severity|normal |wishlist Component|general |kcm_desktoppath Summary|Missing fields for |Allow configuring the |locations publicshare and |locations of the |templates |publicshare and templates ||folders CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 444755] Wi-Fi not auto connecting to a saved Hidden network
https://bugs.kde.org/show_bug.cgi?id=444755 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
