[krita] [Bug 437196] Touch docker commands sometimes gets triggered twice
https://bugs.kde.org/show_bug.cgi?id=437196 Alvin Wong changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #1 from Alvin Wong --- @Dmitry: I traced the window messages and seem to have found a pattern. This is how the messages seem to arrive: 1. When drawing a stroke, WM_POINTERDOWN / WM_POINTERUPDATE / WM_POINTERUP are received for the pen input. 2. Synthesized WM_LBUTTONDOWN / WM_MOUSEMOVE / WM_LBUTTONUP are also received. 3. As the pen is released and the touch docker is touched, WM_POINTERDOWN / WM_POINTERUPDATE / WM_POINTERUP are received for the touch point. 4. Synthesized WM_TOUCH messages are also received. 5. Finally, synthesized WM_LBUTTONDOWN / WM_LBUTTONUP are received. Whenever the command gets triggered twice, however, the window received extra WM_PINTERUPDATE messages generated from the pen moving, in between item 3 and 5. Effectively, you don't need to draw on the canvas to trigger the bug. Simply shaking the pen hovering on the canvas and touching the touch docker buttons at the same time can trigger the bug. I suspect this to be the culprit: https://invent.kde.org/qt/qt/qtbase/-/commit/786c58817187bb18552934c807ba7a7ea845f49e#5fba19dc9f238dadbe8c1589df5a5f8c5c8a8537_732_734 I'm not sure if it is safe to just revert that commit though, since it does mention Qt Quick relies on this. What do you think? P.S. the code comment states that "using the bit 7 of the extra msg info for checking if synthesized for touch does not work", but I suspect it is related to the thing where Windows starts synthesizing touch events from pen input since 1709. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 439625] New: Display layout shows different resultion than the acual configured one
https://bugs.kde.org/show_bug.cgi?id=439625 Bug ID: 439625 Summary: Display layout shows different resultion than the acual configured one Product: KScreen Version: 5.22.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: carcin...@gmx.net Target Milestone: --- Created attachment 139937 --> https://bugs.kde.org/attachment.cgi?id=139937=edit wrong-display-resoltion-in-layout SUMMARY I have a dual monitor setup where i have a 4k laptop screen next to a full HD monitor. The monitors resolution is @ 1920x1080 60Hz and the laptop screen is @ 1440x810 60Hz (accordingly to xrandr). The layout (the nice grapical representation of the screens wich allows to position them via drag and drop) shows for the laptop screen a resolution of 576x324. STEPS TO REPRODUCE 1. Plugin a second full HD monitor next to the 4k monitor 2. Set the resolution of the 4k monitor to 1440x810 OBSERVED RESULT In the screen layout for the 4k monitor the resolution of 576x324 is show where as xrandr show a resolution of 1440x810. Because of this (i guess) positioning the laptop screen correctly is not possible. EXPECTED RESULT The layout should show the correct resolution and therefore the positioning to align the monitors on the bottom line should be possible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 21.04 KDE Plasma Version: Plasma 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphical System: X11 ADDITIONAL INFORMATION $ xrandr --current Screen 0: minimum 320 x 200, current 3520 x 1080, maximum 16384 x 16384 eDP-1 connected 1440x810+1920+180 (normal left inverted right x axis y axis) 344mm x 194mm 3840x2160 60.00 + 59.9859.97 3200x1800 59.9659.94 2880x1620 59.9659.97 2560x1600 59.9959.97 2560x1440 59.9959.9959.9659.95 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 59.9959.9859.9059.91 1920x1200 59.8859.95 1920x1080 60.0159.9759.9659.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.00* 59.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 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 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm 1920x1080 60.00*+ 50.0059.9430.0025.0024.0029.97 23.98 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) DP-1-3 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438340] Animation curves - Rotation with Transform Mask - Glitches
https://bugs.kde.org/show_bug.cgi?id=438340 --- Comment #9 from Eoin O'Neill --- Please try it again when you get some time. I think the glitchy rotations should be mostly resolved now. Reopen if you come across any additional edge-cases. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438340] Animation curves - Rotation with Transform Mask - Glitches
https://bugs.kde.org/show_bug.cgi?id=438340 Eoin O'Neill changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/b347ab13a |hics/krita/commit/ba10b857f |326fc571c6ff6e1f51f515c3e5d |963edc2467324b338d23af76d5c |5a78|6d58 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #8 from Eoin O'Neill --- Git commit ba10b857f963edc2467324b338d23af76d5c6d58 by Eoin O'Neill. Committed on 08/07/2021 at 05:43. Pushed by eoinoneill into branch 'master'. Fixed threading issue with animated transform masks with non-centered rotations. M +2-6 plugins/tools/tool_transform2/kis_animated_transform_parameters.cpp M +0-2 plugins/tools/tool_transform2/kis_animated_transform_parameters.h https://invent.kde.org/graphics/krita/commit/ba10b857f963edc2467324b338d23af76d5c6d58 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789
--- Comment #10 from Jiri Slaby ---
(In reply to Jiri Slaby from comment #9)
> BTW I also applied the patch from bug 439208#c3, but kwin still crashes with
> the very same backtrace.
Just checked with the core file:
> (gdb) l DrmConnector::DrmConnector
> 25 if (m_conn) {
> 26 for (int i = 0; i < m_conn->count_encoders; ++i) {
> 27 m_encoders << m_conn->encoders[i];
> 28 }
> 29 } else {
> 30 qCWarning(KWIN_DRM) << "drmModeGetConnector failed!" <<
> strerror(errno);
> 31 }
> 32 }
> 33
> 34 DrmConnector::~DrmConnector() = default;
--
You are receiving this mail because:
You are watching all bug changes.
[akregator] [Bug 432597] Akregator crashes on close.
https://bugs.kde.org/show_bug.cgi?id=432597 Tony changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Tony --- I have not been able to replicate it again, it's been working fine for a while now, so marking as worksforme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438789] kwin_wayland crashed in KWin::DrmGpu::updateOutputs while un/re-plugging monitor
https://bugs.kde.org/show_bug.cgi?id=438789 --- Comment #9 from Jiri Slaby --- (In reply to Zamundaaa from comment #8) > It seems like the logging rules aren't applied, did you add them? Ah, I am stupid. I am not using sddm for a couple of weeks as it doesn't start any session, so the log was old. I am using this from console: /usr/lib64/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland I assume the output is logged nowhere. Let me redirect the output to a file. > You can check if it worked with > echo $QT_LOGGING_RULES That's correctly set: $ echo $QT_LOGGING_RULES kwin_*.debug=true;kwin_libinput.debug=false BTW I also applied the patch from bug 439208#c3, but kwin still crashes with the very same backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439624] New: KDE Effects no longer working on Kde Plasma (Ubuntu 20.04.2 LTS)
https://bugs.kde.org/show_bug.cgi?id=439624 Bug ID: 439624 Summary: KDE Effects no longer working on Kde Plasma (Ubuntu 20.04.2 LTS) Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: jjb9...@tutanota.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139936 --> https://bugs.kde.org/attachment.cgi?id=139936=edit Detailed image of the not working transparency SUMMARY I was playing a game on my laptop, but I decided to skip the shaders processing, at first, there was no problem, I was using more resources, of course, leading to some crashes that was kinda expected. But in one of this crashes, my entire taskbar turned opaque and also the system notified saying there was 140MB storage free, I was not worried at first about the opaque taskbar, I tough that was a KDE functionality to reduce system resources to give a good gaming experience. So after I played, I was back into settings trying to re-enable the transparency/blur effect, but it changed nothing, I tried changing the themes, the theme changed, but there was still no transparency, I restarted the computer, nothing, returned to Gnome, which transparency was working, and changed back to KDE, and it was still not working, and not only transparency, but most of KDE Effects. When trying to edit the transparency on Konsole, the following message appeared (This color scheme uses a transparent background, which seems not to be supported by your desktop environment). So something made kde unable to show any transparency effect after I played the game, this game was running under Proton 6.5 GE-1. OBSERVED RESULT Kde lost most of its effects and Konsole was saying that kde seemed to not support transparency anymore. EXPECTED RESULT Transparency and other effects still working after the gameplay. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04.2 LTS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Game: VRChat Processor: Intel i3 3110M 2.40GHz Memory: 4GB Ram Graphics: Intel HD 4000 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439096] kscreenlocker broken with error message on wayland
https://bugs.kde.org/show_bug.cgi?id=439096 --- Comment #8 from Cane Kostovski --- Operating System: openSUSE Tumbleweed 20210704 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.13-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × AMD FX(tm)-8350 Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: Radeon RX 570 Series -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438012] Battery indicator in Wayland session
https://bugs.kde.org/show_bug.cgi?id=438012 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.
[KScreen] [Bug 437824] Wrong monitor enabled on wake-from-suspend
https://bugs.kde.org/show_bug.cgi?id=437824 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438985] keyboard shortcuts dont work with sh scripts
https://bugs.kde.org/show_bug.cgi?id=438985 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438244] discover has no apps in it.
https://bugs.kde.org/show_bug.cgi?id=438244 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 438242] Krita will not open.
https://bugs.kde.org/show_bug.cgi?id=438242 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437811] KDE Connect crashed Plasmashell when double click in KDE Connet icon in panel
https://bugs.kde.org/show_bug.cgi?id=437811 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 436919] Cannot compress large directory as 7zip
https://bugs.kde.org/show_bug.cgi?id=436919 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 398908] MimeTypeFinderJob can use huge amounts of memory reading unnecessary data
https://bugs.kde.org/show_bug.cgi?id=398908 --- Comment #95 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439619] DiscoverNotifier occasionally crashed with a failed assertion related to flatpak then SIGTRAP in g_log_structured_array in glib after Plasma started
https://bugs.kde.org/show_bug.cgi?id=439619 Matt Fagnani changed: What|Removed |Added Summary|DiscoverNotifier|DiscoverNotifier |occasionally crashed with |occasionally crashed with a |SIGTRAP in |failed assertion related to |g_log_structured_array in |flatpak then SIGTRAP in |glib after Plasma started |g_log_structured_array in ||glib after Plasma started --- Comment #1 from Matt Fagnani --- I forgot to mention that I think the failed assertion flatpak:ERROR:common/flatpak-variant-impl-private.h:1197:var_summary_get_metadata: assertion failed: (start <= end) is the reason for the first crash of DiscoverNotifier. The following DiscoverNotifier crash with SIGTRAP in g_log_structured_array likely happened when I tried to generate the trace in drkonqi by clicking the Advanced tab or button which led to the drkonqi crash. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 426813] Some KXMLGui-using apps are opening maximized instead of windowed
https://bugs.kde.org/show_bug.cgi?id=426813 --- Comment #32 from Doug Glenn --- (In reply to Nate Graham from comment #31) > Yeah there was a brief period of time during which those items were > inappropriately written to people's config files. The bug causing this to > happen has been fixed now, but it's possible that you would still be > affected if it happened to you during that period of time. Removing them is > a perfectly acceptable way to fix it for yourself. Considering the time stamp of the participants, true. What flummoxed me was the location. The convention for the .config directory originally was in this format $XDG_CONFIG_HOME/subdir/filename, so I was looking for .config/kde/configuration file location. It never occurred to me they would be in the base of the .config file. The KDE configuration file location has shifted a time or two since it was originally released so I was actually poking around the ./local directory looking. The issue wasn't a major file to me and I knew I'd eventually get around to finding an answer. I do wish the files would eventually follow the convention, but innovation doesn't occur without breaking a rule or two and the growth of Linux, KDE and the other windowing systems is phenomenal. When I ran across it in 1995 you had to know the specific hardware configuration and chipset of the video card to get X to run and all the apps had to be built in order to run. It was a daunting experience but I knew OS/2 was in it's death spiral and I was desperate not to be forced into using any Microsoft products at home. I switched to Linux full time in 1997 and the change from the 1995 version was profound. The growth and maturity has continued to defy my expectations and I don't see that changing. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439623] New: slack-desktop cannot connect to account.
https://bugs.kde.org/show_bug.cgi?id=439623 Bug ID: 439623 Summary: slack-desktop cannot connect to account. Product: frameworks-kio Version: 5.22.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: edj7...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 139935 --> https://bugs.kde.org/attachment.cgi?id=139935=edit Dialog box with error message SUMMARY slack-desktop package cannot connect to account. source: https://aur.archlinux.org/packages/slack-desktop/ STEPS TO REPRODUCE 1. open slack application 2. click "Sign In To Slack" which will open up a log in page on default browser 3. log in and select workspaces 4. click "open" prompting xdg-open to redirect to slack application OBSERVED RESULT Dialog box will appear with message "Unable to create io-slave. klauncher said: Unknown protocol 'slack'." EXPECTED RESULT The slack application will open, displaying the workspaces you selected, allowing you to send messages and interact with the interface. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kernel: 5.9.16-1-MANJARO (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439622] New: Dolphin crashes when pointing Trash to /dev/null
https://bugs.kde.org/show_bug.cgi?id=439622 Bug ID: 439622 Summary: Dolphin crashes when pointing Trash to /dev/null Product: dolphin Version: 21.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@tfaber.net CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.04.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.13-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.2 Distribution: Fedora 34 (Workstation Edition) -- Information about the crash: - What I was doing when the application crashed: In the left side bar under Places, right click Trash and select "Edit...". Change location to /dev/null, click OK. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f7dcb844ee4 in KIconButton::icon() const () from /lib64/libKF5IconThemes.so.5 #5 0x7f7dcc03b1a1 in KFilePlaceEditDialog::icon() const () from /lib64/libKF5KIOFileWidgets.so.5 #6 0x7f7dcc42b6bc in PlacesPanel::slotItemContextMenuRequested(int, QPointF const&) () from /lib64/libkdeinit5_dolphin.so #7 0x7f7dca26ac99 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f7dcc10a78a in KItemListController::itemContextMenuRequested(int, QPointF const&) () from /lib64/libdolphinprivate.so.5 #9 0x7f7dcc13ee39 in KItemListController::onPress(QPoint const&, QPointF const&, QFlags, QFlags) () from /lib64/libdolphinprivate.so.5 #10 0x7f7dcc1371f5 in KItemListController::mousePressEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /lib64/libdolphinprivate.so.5 #11 0x7f7dcc143669 in KItemListController::processEvent(QEvent*, QTransform const&) () from /lib64/libdolphinprivate.so.5 #12 0x7f7dcc143741 in KItemListView::event(QEvent*) () from /lib64/libdolphinprivate.so.5 #13 0x7f7dcadd4423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7f7dca237098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f7dcb112945 in QGraphicsScenePrivate::sendEvent(QGraphicsItem*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f7dcb112d01 in QGraphicsScenePrivate::sendMouseEvent(QGraphicsSceneMouseEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f7dcb11b5ca in QGraphicsScenePrivate::mousePressEventHandler(QGraphicsSceneMouseEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f7dcb125521 in QGraphicsScene::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f7dcadd4423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f7dca237098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f7dcb142ff5 in QGraphicsView::mousePressEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f7dcae16dbe in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7f7dcaec45b2 in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #24 0x7f7dca236e4d in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #25 0x7f7dcadd4412 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #26 0x7f7dcaddc054 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #27 0x7f7dca237098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #28 0x7f7dcaddab37 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #29 0x7f7dcae30530 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #30 0x7f7dcae337c5 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #31 0x7f7dcadd4423 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #32 0x7f7dca237098 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #33 0x7f7dca751db8 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #34 0x7f7dca731d0c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #35 0x7f7dc7bf18a4 in userEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5WaylandClient.so.5 #36 0x7f7dc81524cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #37 0x7f7dc81a64e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #38 0x7f7dc814fc03 in g_main_context_iteration () from
[frameworks-kirigami] [Bug 438442] Display author/credit task somehow in the Kirigami.AboutPage
https://bugs.kde.org/show_bug.cgi?id=438442 Nate Graham changed: What|Removed |Added Version Fixed In||5.85 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439578] Maximize button sometimes appears even in non-resizable windows with xdg-decoration
https://bugs.kde.org/show_bug.cgi?id=439578 Nate Graham changed: What|Removed |Added Version Fixed In||5.23 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439394] Some messages are not localized
https://bugs.kde.org/show_bug.cgi?id=439394 Nate Graham changed: What|Removed |Added Version Fixed In||5.22.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #80 from Nate Graham --- Woohoo! Thanks Andrey! -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 436442] kwallet fails to open at login most of the time.
https://bugs.kde.org/show_bug.cgi?id=436442
Timothy B changed:
What|Removed |Added
CC||yule2...@live.com
--- Comment #4 from Timothy B ---
This only happens for me immediately after upgrading Plasma, and strange
enough, rebooting my system made the issue go away at the next and subsequent
logins, i.e. kwallet stops appearing at Plasma startup. When kwallet nags me
with its dialog box, my session is unable to automatically connect to my WiFi
network without my input.
I got near identical journal logs to comment #3 above when this happens (see
below). This has been going on for the past couple of releases now -- I can't
remember what version I started getting this behavior.
SYSTEM INFORMATION
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.12.14-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: Radeon RX 570 Series
`journalctl -b-1 | grep -i kwallet` OUTPUT
Jul 07 18:47:41 pbngtower1 sddm-helper[1372]: pam_kwallet5(sddm:auth): (null):
pam_sm_authenticate
Jul 07 18:47:41 pbngtower1 sddm-helper[1372]: pam_kwallet5(sddm:setcred):
pam_kwallet5: pam_sm_setcred
Jul 07 18:47:41 pbngtower1 sddm-helper[1372]: pam_kwallet5(sddm:session):
pam_kwallet5: pam_sm_open_session
Jul 07 18:47:41 pbngtower1 sddm-helper[1375]: pam_kwallet5: final socket path:
/run/user/1000/kwallet5.socket
Jul 07 18:47:41 pbngtower1 kernel: audit: type=1105 audit(1625705261.151:104):
pid=1372 uid=0 auid=1000 ses=4 subj==unconfined msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_kwallet5
acct="pibeng" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0
res=success'
Jul 07 18:47:41 pbngtower1 audit[1372]: USER_START pid=1372 uid=0 auid=1000
ses=4 subj==unconfined msg='op=PAM:session_open
grantors=pam_loginuid,pam_keyinit,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_kwallet5
acct="pibeng" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=:0
res=success'
Jul 07 18:47:43 pbngtower1 dbus-daemon[1387]: [session uid=1000 pid=1387]
Activating service name='org.kde.kwalletd5' requested by ':1.11' (uid=1000
pid=1426 comm="/usr/bin/kded5 ")
Jul 07 18:47:43 pbngtower1 dbus-daemon[1387]: [session uid=1000 pid=1387]
Successfully activated service 'org.kde.kwalletd5'
Jul 07 18:47:44 pbngtower1 kwalletd5[1504]: Application ' "kded5" ' using
kwallet without parent window!
Jul 07 18:47:46 pbngtower1 plasma_session[1409]: org.kde.plasma.session:
Starting autostart service "/etc/xdg/autostart/pam_kwallet_init.desktop"
("/usr/lib/pam_kwallet_init")
Jul 07 18:47:46 pbngtower1 sddm[1376]: kwalletd5: Checking for pam module
Jul 07 18:47:46 pbngtower1 sddm[1376]: kwalletd5: Got pam-login param
Jul 07 18:47:46 pbngtower1 sddm[1376]: kwalletd5: Waiting for hash on 7-
Jul 07 18:47:46 pbngtower1 sddm[1376]: kwalletd5: waitingForEnvironment on: 8
Jul 07 18:47:46 pbngtower1 sddm[1376]: kwalletd5: client connected
Jul 07 18:47:46 pbngtower1 sddm[1376]: kwalletd5: client disconnected
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 Nate Graham changed: What|Removed |Added Version Fixed In||5.23 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417939] Task context menu disappears when Task's tooltip disappears
https://bugs.kde.org/show_bug.cgi?id=417939 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/49 ||8645ae60da4304512e72884fe2d ||0401073a628 Version Fixed In||5.23 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438971] GDK_SCALE scale envs not unset on wayland login
https://bugs.kde.org/show_bug.cgi?id=438971 Nate Graham changed: What|Removed |Added Version Fixed In|5.23|5.22.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438971] GDK_SCALE scale envs not unset on wayland login
https://bugs.kde.org/show_bug.cgi?id=438971 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |4ef92d8c9bba5429bf85c521bc9 |14cd19138cd514ea753a842d01b |62f105692c4ce |d2265ee8ad0b8 --- Comment #18 from Nate Graham --- Git commit 14cd19138cd514ea753a842d01bd2265ee8ad0b8 by Nate Graham, on behalf of David Edmundson. Committed on 08/07/2021 at 01:09. Pushed by ngraham into branch 'Plasma/5.22'. Set GDK scale explictily on wayland On wayland we don't want to use the env vars as we send the scale via wl_output scale. If a user logs into X first we set these in our activation env to a scaled value. If they then log into wayland afterwards they are still set. Calling qunsetenv won't work as then we won't remove them from the activation env. Arguably it's working round a bug, but we don't have other options. (cherry picked from commit 4ef92d8c9bba5429bf85c521bc962f105692c4ce) M +2-0startkde/startplasma-wayland.cpp https://invent.kde.org/plasma/plasma-workspace/commit/14cd19138cd514ea753a842d01bd2265ee8ad0b8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438971] GDK_SCALE scale envs not unset on wayland login
https://bugs.kde.org/show_bug.cgi?id=438971 Nate Graham changed: What|Removed |Added Version Fixed In||5.23 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439515] Refresh rate list is not sorted
https://bugs.kde.org/show_bug.cgi?id=439515 Nate Graham changed: What|Removed |Added Version Fixed In||5.23 Latest Commit||https://invent.kde.org/plas ||ma/kscreen/-/commit/413adfe ||1dcd233de9865abed51c9a409de ||e00c20 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 380497] Yakuake KeepOpen=false doesn't work with Wayland
https://bugs.kde.org/show_bug.cgi?id=380497 Patrick Silva changed: What|Removed |Added CC||ha...@lansmart.com --- Comment #10 from Patrick Silva --- *** Bug 439572 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 439572] Yakuake "Keep Window Open when it loses focus" pref deselection ignored in Wayland
https://bugs.kde.org/show_bug.cgi?id=439572 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 380497 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439539] Everything on Krita is smaller and stylus is offset
https://bugs.kde.org/show_bug.cgi?id=439539 --- Comment #2 from os79...@gmail.com --- (In reply to Halla Rempt from comment #1) > Sorry, but if you didn't update Krita, and things changed, then it's an > issue with your system, and not a bug in Krita. Maybe you got a Windows > update, or a tablet driver update, maybe you changed some system settings, > but this isn't something we can investigate and fix. > > (Especially tablet offset issues are often tablet driver problems > interacting with changes in display scaling or monitor settings.) Nope, no updates. The only thing I had done differently was change what the bottom button on my stylus does, but I changed that back and still no fix. So I have no idea -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439262] Alternative text not displayed for inaccessible inline images
https://bugs.kde.org/show_bug.cgi?id=439262 Nate Graham changed: What|Removed |Added CC||n...@kde.org Latest Commit||https://invent.kde.org/grap ||hics/okular/-/commit/74cb4e ||545d808963bebfbb7fbc98fadf0 ||dee3084 Version Fixed In||21.08 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439614] Running commands in Konsole becomes slow / laggy when it has been open a long time
https://bugs.kde.org/show_bug.cgi?id=439614
--- Comment #2 from Adam Fontenot ---
Created attachment 139934
--> https://bugs.kde.org/attachment.cgi?id=139934=edit
perf profile for konsole
(In reply to ninjalj from comment #1)
> A profile, e.g. using perf, may show something.
>
> To record a profile for konsole:
>
> perf record -g -p
Attached. Profile contains about 15 seconds of recording during which I ran
`python -S -c "print('test')"` 3 times.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 439616] Application menu overlaps with status bar in Wayland
https://bugs.kde.org/show_bug.cgi?id=439616 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 378694 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 378694] Kicker's sub-menus are covered up by Plasma panels
https://bugs.kde.org/show_bug.cgi?id=378694 Patrick Silva changed: What|Removed |Added CC||sombrag...@sombragris.org --- Comment #33 from Patrick Silva --- *** Bug 439616 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 426548] ibus layout switching not working in kscreenlocker, can't unlock
https://bugs.kde.org/show_bug.cgi?id=426548 Uriy Zhuravlev changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #4 from Uriy Zhuravlev --- Ok, I understand now. The button for change language on the lock screen I can see only for the Wayland session, and it's doesn't show for the Xorg session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431489] GTK windows fly offscreen when dragging with touchscreen and wobbly windows effect enabled (Wayland only)
https://bugs.kde.org/show_bug.cgi?id=431489 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/d78c89f0ede6 ||35d9aa2f6d7f369fe3d38d57b46 ||6 Version Fixed In||5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 388807] Choose icon dialog: distant of widgets is too high when dialog is wide
https://bugs.kde.org/show_bug.cgi?id=388807 Nate Graham changed: What|Removed |Added Version Fixed In||5.85 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 263449] korganizer sets DTSTART and DTEND to Zulu time when an e-mail invite is sent and recurrence is active
https://bugs.kde.org/show_bug.cgi?id=263449 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||gjditchfi...@acm.org --- Comment #5 from gjditchfi...@acm.org --- I can't reproduce this with KOrganizer 5.17.2; can you reproduce it with a recent version? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 438119] Add application to the Right-Click > "Open With" menu when the user manually specifies it to open something
https://bugs.kde.org/show_bug.cgi?id=438119 --- Comment #5 from Lonnie --- Created attachment 139933 --> https://bugs.kde.org/attachment.cgi?id=139933=edit How to Add Application to "Open With" Folder I discovered a way intended way to accomplish this (attached). I still say it is less intuitive than what I'm proposing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active
https://bugs.kde.org/show_bug.cgi?id=436240 Nate Graham changed: What|Removed |Added Target Milestone|1.0 |--- Component|Notifications |compositing Status|NEEDSINFO |REPORTED Summary|Notification display lag|Lag/hang in apps and Plasma |blocks input in Firefox |when a notification appears ||while compositing is active Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Product|plasmashell |kwin Assignee|k...@privat.broulik.de |kwin-bugs-n...@kde.org --- Comment #10 from Nate Graham --- Thanks folks. Moving to KWin, as it seems related to compositing. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438043] Konsole suddenly stopped asking me for conformation on multi-line paste
https://bugs.kde.org/show_bug.cgi?id=438043 Nate Graham changed: What|Removed |Added Version Fixed In||21.08 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439482] Application description shown in all languages available
https://bugs.kde.org/show_bug.cgi?id=439482 Aleix Pol changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Aleix Pol --- Correct, this is an issue in appstream. Can you please submit it here? If you include the "appstreamcli search kcron --details" output they should understand what is going on. https://github.com/ximion/appstream/issues/new -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 426813] Some KXMLGui-using apps are opening maximized instead of windowed
https://bugs.kde.org/show_bug.cgi?id=426813 --- Comment #31 from Nate Graham --- Yeah there was a brief period of time during which those items were inappropriately written to people's config files. The bug causing this to happen has been fixed now, but it's possible that you would still be affected if it happened to you during that period of time. Removing them is a perfectly acceptable way to fix it for yourself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439456] Widget doesn't remember its size
https://bugs.kde.org/show_bug.cgi?id=439456 dS810 changed: What|Removed |Added Summary|Wiodget doesn't remember|Widget doesn't remember its |its size|size -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 439566] Printing special sample file or generating a printer preview for it freezes UI
https://bugs.kde.org/show_bug.cgi?id=439566 Albert Astals Cid changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #6 from Albert Astals Cid --- Please open two new bugs, this is already dirty with being about two things with comments about both and whatnot. It'll be easier to track for future people that have time to have a look at the bugs if they are two separate and well defined issues. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 438119] Add application to the Right-Click > "Open With" menu when the user manually specifies it to open something
https://bugs.kde.org/show_bug.cgi?id=438119 --- Comment #4 from Lonnie --- If you know of a work-around to accomplish this, please direct me to it. When right-clicking on a folder, I need the ability to "Open With" > VLC. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439621] New: Resizing borders only easy with "No Borders", hard with tiny borders
https://bugs.kde.org/show_bug.cgi?id=439621 Bug ID: 439621 Summary: Resizing borders only easy with "No Borders", hard with tiny borders Product: kwin Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: boslma...@gmail.com Target Milestone: --- Created attachment 139932 --> https://bugs.kde.org/attachment.cgi?id=139932=edit Border resize Area only a few pixels SUMMARY The Borders of Windows are only easy to resize, when the setting in "Window Decorations" is "No Borders", because everywhere else resizing is only possible when touching the border pixels with the mouse and these can be very small. When having No Borders, the "resize area" is very large so its pretty easy to hit. Please make this resize area the same for all border sizes the same or at least make an option to let this be activated or else Tiny Borders are basically unusable because they are so hard to hit. (Just Google the problem, there are many people noticing the same, it's not just me.) STEPS TO REPRODUCE Go to "Window Decorations" Set Window Border Size to tiny Try to resize Windows, without needing 10 seconds to hit them. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 439620] New: Allow changing kcommandbar keyboard shortcut.
https://bugs.kde.org/show_bug.cgi?id=439620 Bug ID: 439620 Summary: Allow changing kcommandbar keyboard shortcut. Product: frameworks-kwidgetsaddons Version: 5.83.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: german...@hotmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY KCommandBar menu is missing in the shortcut configurator. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439070] Unable to copy/paste when using Wayland
https://bugs.kde.org/show_bug.cgi?id=439070 --- Comment #12 from Anton Kreuzkamp --- After update to 5.22.3 pasting images into krita (xwayland) works fine, pasting into Chrome (91.0, XWayland) still fails. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439513] Klipper interferes with XWayland: Copying text works only every second time
https://bugs.kde.org/show_bug.cgi?id=439513 Anton Kreuzkamp changed: What|Removed |Added Version|5.22.2 |5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438525] Buttons in the Sensor Details tab are styled in weird ways.
https://bugs.kde.org/show_bug.cgi?id=438525 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/frameworks/qqc2-desktop-style/-/merge_requests/79 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 438043] Konsole suddenly stopped asking me for conformation on multi-line paste
https://bugs.kde.org/show_bug.cgi?id=438043 --- Comment #4 from Kurt Hindenburg --- This should be fixed now -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439553] Warning about control characters when pasting with newline
https://bugs.kde.org/show_bug.cgi?id=439553 --- Comment #4 from Kurt Hindenburg --- This should be fixed now -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439614] Running commands in Konsole becomes slow / laggy when it has been open a long time
https://bugs.kde.org/show_bug.cgi?id=439614 ninj...@gmail.com changed: What|Removed |Added CC||ninj...@gmail.com --- Comment #1 from ninj...@gmail.com --- A profile, e.g. using perf, may show something. To record a profile for konsole: perf record -g -p A profile of the whole system may be interesting: perf record -g The profile can be analyzed with: perf report -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439619] New: DiscoverNotifier occasionally crashed with SIGTRAP in g_log_structured_array in glib after Plasma started
https://bugs.kde.org/show_bug.cgi?id=439619
Bug ID: 439619
Summary: DiscoverNotifier occasionally crashed with SIGTRAP in
g_log_structured_array in glib after Plasma started
Product: Discover
Version: 5.21.5
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Notifier
Assignee: aleix...@kde.org
Reporter: matthew.fagn...@utoronto.ca
Target Milestone: ---
SUMMARY
I've used a Fedora 34 KDE Plasma installation. Starting with Plasma 5.21.5 on
Wayland, DiscoverNotifier occasionally crashed with SIGTRAP in
g_log_structured_array in glib 2.68.2 about 30 s to 1 minute after login. Frame
1 of the crashing thread 1 had the error message "inotify read(): Bad file
descriptor"
Core was generated by `/usr/libexec/DiscoverNotifier'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0 g_log_structured_array (log_level=, fields=0x7fb94bffd7e0,
n_fields=4)
at ../glib/gmessages.c:556
556 G_BREAKPOINT ();
[Current thread is 1 (Thread 0x7fb94bfff640 (LWP 6231))]
(gdb) bt full
#0 g_log_structured_array (log_level=, fields=0x7fb94bffd7e0,
n_fields=4)
at ../glib/gmessages.c:556
__func__ = "g_log_structured_array"
#1 0x7fb96a4b5249 in g_log_default_handler
(log_domain=log_domain@entry=0x7fb9585976c4 "GLib-GIO",
log_level=log_level@entry=6, message=message@entry=0x7fb9440014a0 "inotify
read(): Bad file descriptor", unused_data=unused_data@entry=0x0)
at ../glib/gmessages.c:3236
fields =
{{key = 0x7fb96a5102e7 "GLIB_OLD_LOG_API", value = 0x7fb96a50e340,
length = -1}, {key = 0x7fb96a510228 "MESSAGE", value = 0x7fb9440014a0, length =
-1}, {key = 0x7fb96a51023b "PRIORITY", value = 0x7fb96a50a71d, length = -1},
{key = 0x7fb96a510295 "GLIB_DOMAIN", value = 0x7fb9585976c4, length = -1}}
n_fields =
#2 0x7fb96a4b661a in g_logv
(log_domain=0x7fb9585976c4 "GLib-GIO", log_level=G_LOG_LEVEL_ERROR,
format=, args=) at ../glib/gmessages.c:1382
domain = 0x0
data = 0x0
depth =
log_func = 0x7fb96a4b5190
domain_fatal_mask =
masquerade_fatal = 0
test_level = 6
was_fatal =
was_recursion =
--Type for more, q to quit, c to continue without paging--c
msg = 0x7fb9440014a0 "inotify read(): Bad file descriptor"
msg_alloc = 0x7fb9440014a0 "inotify read(): Bad file descriptor"
i = 2
#3 0x7fb96a4b6903 in g_log (log_domain=log_domain@entry=0x7fb9585976c4
"GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_ERROR,
format=format@entry=0x7fb9585cbd91 "inotify read(): %s") at
../glib/gmessages.c:1451
args = {{gp_offset = 32, fp_offset = 48, overflow_arg_area =
0x7fb94bffda10, reg_save_area = 0x7fb94bffd950}}
#4 0x7fb95858c5b7 in ik_source_read_some_events
(iks=iks@entry=0x5566818859b0, buffer=buffer@entry=0x7fb94bffda80 "",
buffer_len=buffer_len@entry=4096) at ../gio/inotify/inotify-kernel.c:160
result =
errsv =
#5 0x7fb95858c71b in ik_source_read_all_the_events (buffer_len=4096,
length_out=, buffer=0x7fb94bffda80 "", iks=0x5566818859b0)
at ../gio/inotify/inotify-kernel.c:169
n_read =
stack_buffer = '\000' ...
buffer_len =
offset =
iks = 0x5566818859b0
user_callback = 0x7fb95858da60
interesting = 0
now = 2076854595
__func__ = "ik_source_dispatch"
#6 ik_source_dispatch (source=0x5566818859b0, func=0x7fb95858da60
, user_data=) at
../gio/inotify/inotify-kernel.c:253
stack_buffer = '\000' ...
buffer_len =
offset =
iks = 0x5566818859b0
user_callback = 0x7fb95858da60
interesting = 0
now = 2076854595
__func__ = "ik_source_dispatch"
#7 0x7fb96a4ae4cf in g_main_dispatch (context=0x55668185dc70) at
../glib/gmain.c:3337
dispatch = 0x7fb95858c6a0
prev_source = 0x0
begin_time_nsec = 2076854591611
was_in_call =
user_data = 0x0
callback = 0x7fb95858da60
cb_funcs = 0x7fb96a5913a0
cb_data = 0x556681877780
need_destroy =
source = 0x5566818859b0
current = 0x7fb944000c10
i = 0
#8 g_main_context_dispatch (context=0x55668185dc70) at ../glib/gmain.c:4055
#9 0x7fb96a5024e8 in g_main_context_iterate.constprop.0
(context=context@entry=0x55668185dc70, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131
max_priority = 2147483647
timeout = -1
some_ready = 1
nfds = 2
allocated_nfds = 2
fds =
begin_time_nsec = 2040086645207
#10 0x7fb96a4abc03 in g_main_context_iteration (context=0x55668185dc70,
may_block=may_block@entry=1) at ../glib/gmain.c:4196
retval =
#11 0x7fb96a4abc51 in glib_worker_main (data=) at
../glib/gmain.c:6089
[systemsettings] [Bug 439618] New: Appearance of 'Import Shortcut Scheme' window is inconsistent
https://bugs.kde.org/show_bug.cgi?id=439618 Bug ID: 439618 Summary: Appearance of 'Import Shortcut Scheme' window is inconsistent Product: systemsettings Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: karlsson.gabr...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 139931 --> https://bugs.kde.org/attachment.cgi?id=139931=edit Screenshot of the window SUMMARY The modal window that appears when clicking the "Import Scheme..." button in the shortcuts settings looks a bit off. In the title bar the text size is different and it seems like it doesn't adapt to the changes made in window decorations. For example, changing to Plastik has no effect on its appearance. The content area however seems fine, though it could benefit from some side margins. STEPS TO REPRODUCE 1. Open System settings 2. Navigate to Shortcuts 3. Click the button "Import Scheme..." OBSERVED RESULT The appearing modal window has a title bar that doesn't adapt to basic theming and a content area that lacks side margins. EXPECTED RESULT The modal window looks consistent with the chosen theme settings and with some margins on each side of the content. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439617] New: Use the titlebar coloras the tabbar background
https://bugs.kde.org/show_bug.cgi?id=439617 Bug ID: 439617 Summary: Use the titlebar coloras the tabbar background Product: konsole Version: 21.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: tabbar Assignee: konsole-de...@kde.org Reporter: kinof...@gmail.com Target Milestone: --- Created attachment 139930 --> https://bugs.kde.org/attachment.cgi?id=139930=edit proposal Use the titlebar coloras the tabbar background. OBSERVED RESULT The tabbar background is not the same as the titlebar which is not in line with our current design. EXPECTED RESULT The tabbar background should use the same color as the titlebar so it's in line with our current design. (visually merge the titlebar and the toolbar, and I think it would be nice to extend this to the tabbar background) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDe (available in About System) KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438340] Animation curves - Rotation with Transform Mask - Glitches
https://bugs.kde.org/show_bug.cgi?id=438340 Eoin O'Neill changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #7 from Eoin O'Neill --- Yeah, there still seems to be some bugs with off centered rotations... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438538] Krita is doing some calculations on hidden layers
https://bugs.kde.org/show_bug.cgi?id=438538 Eoin O'Neill changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #5 from Eoin O'Neill --- Is this resolved as of commit b347ab13a326fc571c6ff6e1f51f515c3e5d5a78 ? Animated transform masks should no longer recalculate in general, so I would presume that this issue is either not around anymore or has to be rethought... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439449] [5.0.0 6f28dc0] When touching / pointing timeline scrollbar with stylus it never loses focus and weird zoom behavior happen.
https://bugs.kde.org/show_bug.cgi?id=439449 Eoin O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439449] [5.0.0 6f28dc0] When touching / pointing timeline scrollbar with stylus it never loses focus and weird zoom behavior happen.
https://bugs.kde.org/show_bug.cgi?id=439449 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com --- Comment #3 from Eoin O'Neill --- I'll iron this out. There must be something wrong with the focus behavior of the zoomable scrollbar. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438768] Animation curves - transform mask calculation activity even if cache has been rendered
https://bugs.kde.org/show_bug.cgi?id=438768 --- Comment #3 from Eoin O'Neill --- There's a small issue with this -- that the recalculate mask job can't get information about the cache state of the animation system (since caching happens on the GUI level.) For now, recalculate mask no longer occurs when dealing with animated transform masks so they no longer update on a timer. This should help iron out other issues with the transform mask not fully rendering the whole desired "region". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438343] Animation curves - Transform Mask - Rotation not intuitive
https://bugs.kde.org/show_bug.cgi?id=438343 Eoin O'Neill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/d525190d4 ||e8799bd61d4f61c57cfea6021e0 ||1baf --- Comment #7 from Eoin O'Neill --- Git commit d525190d4e8799bd61d4f61c57cfea6021e01baf by Eoin O'Neill. Committed on 07/07/2021 at 20:38. Pushed by eoinoneill into branch 'master'. Free Transform: Support negative rotation, track rotation direction for animation intent. M +2-3plugins/tools/tool_transform2/kis_free_transform_strategy.cpp https://invent.kde.org/graphics/krita/commit/d525190d4e8799bd61d4f61c57cfea6021e01baf -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439616] New: Application menu overlaps with status bar in Wayland
https://bugs.kde.org/show_bug.cgi?id=439616 Bug ID: 439616 Summary: Application menu overlaps with status bar in Wayland Product: plasmashell Version: 5.22.3 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: sombrag...@sombragris.org CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139929 --> https://bugs.kde.org/attachment.cgi?id=139929=edit Screenshot depicting how Application Menu submenus get hidden behind the status bar SUMMARY When using a wayland Session, the Application Menu (hierarchical/traditional menus) plasmoid overlaps with the status bar STEPS TO REPRODUCE 1. Use Application Menu as your menu launcher. 2. Chose a submenu, for example, "Shutdown" 3. OBSERVED RESULT Parts of the submenu are unreadable because they are placed behind the status bar. I shall attach a screenshot depicting the bug behavior. EXPECTED RESULT The submenus should be readable and not hidden behind the status bar. SOFTWARE/OS VERSIONS Operating System: Slackware64-current KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.14 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This shows only in Wayland. Under an X11 session the submenus adjust to the status bar and are readable. Screenshot attached depicting the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439581] Problems under Ubuntu with digiKam as snap package
https://bugs.kde.org/show_bug.cgi?id=439581 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #11 from caulier.gil...@gmail.com --- Ubuntu have been always a problem. It's the best Linux distro so far... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432265] No error message when Digikam fails to read XMP metadata from image file
https://bugs.kde.org/show_bug.cgi?id=432265 caulier.gil...@gmail.com changed: What|Removed |Added Component|Metadata-Xmp|Metadata-ExifTool -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 439615] New: ksystemstats keeps crashing on every login
https://bugs.kde.org/show_bug.cgi?id=439615 Bug ID: 439615 Summary: ksystemstats keeps crashing on every login Product: plasma-systemmonitor Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mirovsk...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 139928 --> https://bugs.kde.org/attachment.cgi?id=139928=edit dump from journalctl SUMMARY ksystemstats keeps crashing on every login or when starting manually via: systemctl --user start plasma-ksystemstats.service STEPS TO REPRODUCE Just login to a new plasma session from sddm OBSERVED RESULT Ksystemstats coredumps few times (after some retries) and system monitor sensors are not available. EXPECTED RESULT Ksystemstats should start SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I'm sorry. I'm unable to distinguish since when, because of the Arch package ksystemstats was unistalled since its introduction for high cpu consumption... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439614] New: Running commands in Konsole becomes slow / laggy when it has been open a long time
https://bugs.kde.org/show_bug.cgi?id=439614 Bug ID: 439614 Summary: Running commands in Konsole becomes slow / laggy when it has been open a long time Product: konsole Version: 21.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 139927 --> https://bugs.kde.org/attachment.cgi?id=139927=edit desktop recording of konsole slowdown problem SUMMARY I have a Konsole instance that has been running for about a week. I've been using it every day for various tasks (system updates, utilities that print things, and so on). Now, new commands take far too long to execute. (The processes themselves still run just as quickly, but Konsole is slow to print the output.) I've included a video of this happening. In the foreground you can see an XTerm instance which shows the exact frame I press the enter key on. If you count the frames from the instant the key is shown, Konsole consistently takes around 37 frames to show the result. As this video was recorded at ~60 fps, that's over 0.6 seconds and is easily noticeable to the user. As you can see in the video, I run the command using `time`, and the program runs in about ~0.05 seconds. In other words, over half a second of the time to return to the shell prompt is due to Konsole's output lagging. Typing in the terminal is *not* noticeably slow. Ctrl-shift-n to open a new window *does not* solve this problem. The resulting window is running under the same Konsole pid as the existing window, and is just as slow. If I start a new Konsole instance (e.g. by entering `konsole` at the prompt in Konsole), it is not slow. The reason I didn't show `echo test` in the video is that this command (which uses the zsh echo built-in) is almost always very fast. Once out of every 10 or 20 times I enter it it'll lag slightly. I'm not sure why this behaves differently than the command I show in the video. STEPS TO REPRODUCE 1. Leave Konsole running for a long time and do normal tasks in it from time to time 2. Try to run a simple command that should return ~instantly OBSERVED RESULT Konsole takes a lot of time to print the output from commands and return to the shell prompt. EXPECTED RESULT Konsole should take the normal amount of time to do the above. SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 kernel version 5.12.13 KDE Plasma: 5.22.2 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I have a fairly large scrollback of 100k lines, but my system is not even close to being out of memory. I have a pretty decent number of terminals open under this PID right now. I have "reflow lines" enabled (I think it's a default). It's the only other thing I've ever seen slow down Konsole - if I accidentally print an extremely long line (millions of characters), Konsole can slow to a crawl. I don't have a good reason for thinking it's related. I will try to leave this Konsole instance running for at least another day or two, in case anyone has debugging steps they would like me to try. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 438442] Display author/credit task somehow in the Kirigami.AboutPage
https://bugs.kde.org/show_bug.cgi?id=438442 Felipe Kinoshita changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kirigami/commit/0c55 ||aad1a5bd07ab768989d2271a578 ||f472bef94 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Felipe Kinoshita --- Git commit 0c55aad1a5bd07ab768989d2271a578f472bef94 by Felipe Kinoshita. Committed on 07/07/2021 at 12:38. Pushed by fhek into branch 'master'. Show author/credits task So if someone's task is "Author" or "UI redesign" it now is displayed in the about page component. M +4-0src/controls/AboutPage.qml https://invent.kde.org/frameworks/kirigami/commit/0c55aad1a5bd07ab768989d2271a578f472bef94 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439613] Task Manager does not show some applications under Wayland
https://bugs.kde.org/show_bug.cgi?id=439613 --- Comment #1 from sombrag...@sombragris.org --- Just upgraded Plasma to 5.22.3. The bug is still present for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438874] Disk & Devices applet doesn't show USB removable devices after connecting the device for 2nd time
https://bugs.kde.org/show_bug.cgi?id=438874 --- Comment #14 from MikeC --- Not fixed in plasma 5.22.3 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370206] KScreenlocker not unlockable after switching to new session when not using systemd
https://bugs.kde.org/show_bug.cgi?id=370206 vlao...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from vlao...@gmail.com --- I'm using elogind 246.10-r1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439535] Edit -> Search in files window does not appear after collapsing when using shortcut
https://bugs.kde.org/show_bug.cgi?id=439535 Christoph Cullmann changed: What|Removed |Added CC||kde.podag...@slmail.me --- Comment #2 from Christoph Cullmann --- *** Bug 439528 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439528] Search plugin can be collapsed and permanently hidden
https://bugs.kde.org/show_bug.cgi?id=439528 Christoph Cullmann changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- Yeah, not that nice. I added a merge request for that in a duplicated bug 439535. *** This bug has been marked as a duplicate of bug 439535 *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439534] 'x' on the Find dialog is on the left, it should be on the right.
https://bugs.kde.org/show_bug.cgi?id=439534 Christoph Cullmann changed: What|Removed |Added CC||cullm...@kde.org --- Comment #1 from Christoph Cullmann --- https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/177 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 426813] Some KXMLGui-using apps are opening maximized instead of windowed
https://bugs.kde.org/show_bug.cgi?id=426813 Doug Glenn changed: What|Removed |Added CC||d...@wildhair.org --- Comment #30 from Doug Glenn --- (In reply to 0xCAP from comment #9) > I currently solved > the issue by removing a bunch of "suspicious" lines from my > ~/.config/konsolerc file. > The lines looked like the following: > > Window-Maximized 1016x1807=true > ect ... This fixed my issue. I'd always had a window size defined (130 x 80) that was a good starting point. But like this gentleman, I had a window-maximized line that was totally out of place. Removed it, and expected behaviour was restored. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 439535] Edit -> Search in files window does not appear after collapsing when using shortcut
https://bugs.kde.org/show_bug.cgi?id=439535 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kate/-/merge_requests/451 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439613] New: Task Manager does not show some applications under Wayland
https://bugs.kde.org/show_bug.cgi?id=439613 Bug ID: 439613 Summary: Task Manager does not show some applications under Wayland Product: plasmashell Version: 5.22.2 Platform: Slackware Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: sombrag...@sombragris.org CC: plasma-b...@kde.org Target Milestone: 1.0 Using: Operating System: Slackware64-current KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.14 (64-bit) Graphics Platform: Wayland SUMMARY Under a Plasma Wayland Session, Task Manager does not show some apps. Currently I was able to observe this with claws-mail (GTK email app). STEPS TO REPRODUCE 1. Open a Plasma Wayland session. 2. Open claws-mail 3. OBSERVED RESULT There's no claws-mail application shown in the task manager plasmoid (I'm using is as part of my status bar) EXPECTED RESULT Task Manager should show the application as running. SOFTWARE/OS VERSIONS Shown above. ADDITIONAL INFORMATION Task Manager behaves as expected under an X11 session. This artifact shows only under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 438983] Double click on split view's splitter should revert to 50/50
https://bugs.kde.org/show_bug.cgi?id=438983 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kate/-/merge_requests/450 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 419967] Updating KIO libs requires executing kdeinit5 to pick up the new libs
https://bugs.kde.org/show_bug.cgi?id=419967 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #7 from RJVB --- Something already restarts kdeinit5 after a crash (or abort in a kioslave). Or is that just This isn't just a KIO problem: it's bound to happen to any project that installs a kioslave. The strange this is that I've just been tinkering with kio-gdrive, and I haven't had to kill any kdeinit5 instance myself in order for it to use the updated gdrive.so . I wrote that off to the fact that no `gdrive.so [kdeinit5]` process remained after quitting Dolphin, but that can't be it if the parent kdeinit5 process keeps the kioslave cached... BTW, hadn't the idea been dropped to use a single, central "speed loader" that keeps all shared libraries it has even seen loaded to speed up subsequent launches? I seem to recall a discussion that this wasn't relevant anymore with the modern fast storage? -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 439612] plasma-nm Applet does not prompt for login credentials when connecting to GlobalProtect VPN
https://bugs.kde.org/show_bug.cgi?id=439612 mason2...@gmail.com changed: What|Removed |Added Summary|Applet does not prompt for |plasma-nm Applet does not |login when connecting to|prompt for login |GlobalProtect VPN |credentials when connecting ||to GlobalProtect VPN -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 439612] Applet does not prompt for login when connecting to GlobalProtect VPN
https://bugs.kde.org/show_bug.cgi?id=439612 mason2...@gmail.com changed: What|Removed |Added CC||mason2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 439612] New: Applet does not prompt for login when connecting to GlobalProtect VPN
https://bugs.kde.org/show_bug.cgi?id=439612 Bug ID: 439612 Summary: Applet does not prompt for login when connecting to GlobalProtect VPN Product: plasma-nm Version: 5.21.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: mason2...@gmail.com Target Milestone: --- Created attachment 139926 --> https://bugs.kde.org/attachment.cgi?id=139926=edit Screenshot of kdialog missing the username and password fields SUMMARY When connecting to a global protect vpn via the plasma-nm applet, the auth dialog appears, but does not have fields for username and password. If the connect button next to the selected gateway is pressed, an error appears stating 'Unexpected 200 result'. I've done some debugging, and it appears that the problem is that Network Manager (verified with nmcli) does not run the authenticate step of openconnect and just asks for the gateway, certificate, and cookie (the results of an openconnect --authenticate command). I'm not sure if this would be considered a Network Manager bug, but I think that the plasma applet should account for this to insulate the user from the technical login process, even if network manager and nmcli are not user-friendly. Note that I am able to connect to the vpn using a script (see ADDITIONAL INFORMATION), so the openconnect system is working. The problem is that the applet (and nmcli) do not perform the intermediate authentication steps that the user shouldn't have to worry about. STEPS TO REPRODUCE 1. Install plasma-nm 5.21.5-1, networkmanager-openconnect 1.2.7, and networkmanager 1.30.4-3 (these are the current versions in a Manjaro system) 2. Add a vpn connection via the plasma network settings, set to globalprotect 3. Attempt to connect to the new vpn connection OBSERVED RESULT The authentication dialog appears with no fields for username and password EXPECTED RESULT The authentication dialog should have fields to enter a username and password, to be passed to the command `openconnect --authenticate`, whose output would be passed to network manager SOFTWARE/OS VERSIONS Manjaro Linux 5.10.42-1-MANJARO KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The following script properly connects to the vpn as expected: #!/usr/bin/env bash tmp=$(mktemp) chmod 600 "$tmp" eval "$(ksshaskpass | openconnect --protocol=gp --authenticate --user=me vpn.domain --passwd-on-stdin)" cat < "$tmp" vpn.secrets.cookie:$COOKIE vpn.secrets.gwcert:$FINGERPRINT vpn.secrets.gateway:$HOST EOF nmcli --ask con up connection-name passwd-file "$tmp" rm "$tmp" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 377253] Show option to format USB drive in context menu
https://bugs.kde.org/show_bug.cgi?id=377253 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438266] Wrong mouse is selected by default in Mouse KCM on Wayland
https://bugs.kde.org/show_bug.cgi?id=438266 Bharadwaj Raju changed: What|Removed |Added CC||bharadwaj.raju777@protonmai ||l.com Summary|Mouse settings not working |Wrong mouse is selected by |on Wayland |default in Mouse KCM on ||Wayland -- You are receiving this mail because: You are watching all bug changes.
[libkdcraw] [Bug 439611] New: libkdcraw should propagate the ${LIBS} from libraw.pc
https://bugs.kde.org/show_bug.cgi?id=439611
Bug ID: 439611
Summary: libkdcraw should propagate the ${LIBS} from libraw.pc
Product: libkdcraw
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: General
Assignee: imaging-bugs-n...@kde.org
Reporter: rjvber...@gmail.com
Target Milestone: ---
SUMMARY
libraw can be built with OpenMP support, which, at least when building with
Clang, adds a dependency to a corresponding shared library. As a result, my
libraw.pc (for v0.20.2) has
```
Libs: -L${libdir} -lraw -fopenmp
```
STEPS TO REPRODUCE
1. build and install libraw with OpenMP support (`configure [...]
--enable-openmp [...]`)
2. build and install libkdcraw
3. try to build a dependent like gwenview
OBSERVED RESULT
The build will fail with the error message that libraw.so.20 has an undefined
reference to a range of __kmpc_XXX symbols.
EXPECTED RESULT
No build failure. Adding `-fopenmp` to the linker flags fixes the issue.
ADDITIONAL INFORMATION
I've observed this on Linux but I presume it will be the case on any Unix
version where private dependencies of shared libraries aren't pulled in
automatically and/or where libraw itself isn't linked to the openmp library (=
all Unices except Darwin?).
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 439610] New: Autoscroll using middle click
https://bugs.kde.org/show_bug.cgi?id=439610 Bug ID: 439610 Summary: Autoscroll using middle click Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: karlsson.gabr...@gmail.com Target Milestone: --- Created attachment 139925 --> https://bugs.kde.org/attachment.cgi?id=139925=edit Example of autoscrolling a PDF in Firefox SUMMARY It would be quite nice to have autoscrolling by middle clicking and controlling speed and direction with the cursor and not just by using 'shift-arrow keys'. Such an option is wonderful to have when browsing through large documents. STEPS TO REPRODUCE 1. Open a document in Okular 2. Middle click OBSERVED RESULT Nothing EXPECTED RESULT A symbol (see attachment) appears as a reference point and scrolls based on the cursors distance from it. SOFTWARE/OS VERSIONS KDE neon User edition 5.22 ADDITIONAL INFORMATION Apologies if this is more relevant to another part of the software stack, e.g. Qt. If so, then please point me to the right place. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439609] New: crash creating folder on MTP device
https://bugs.kde.org/show_bug.cgi?id=439609 Bug ID: 439609 Summary: crash creating folder on MTP device Product: dolphin Version: 20.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: linuxhi...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.12.13-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: When I created a new folder (using the right-click context menu New->Folder) on my Huawei P20 phone, Dolphin immediatly crashed. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7fa384ad2189 in QLineEdit::text() const () from /lib64/libQt5Widgets.so.5 #5 0x7fa385bc1c48 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] () from /lib64/libKF5KIOFileWidgets.so.5 #6 0x7fa383e65386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7fa384f891c0 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #8 0x7fa384f8de8b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #9 0x7fa383e65386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7fa385725f6a in KIO::SlaveInterface::error(int, QString const&) () from /lib64/libKF5KIOCore.so.5 #11 0x7fa385725637 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #12 0x7fa38571e05d in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #13 0x7fa3857277a2 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #14 0x7fa383e65386 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fa383e5dd1e in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fa38498eec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7fa383e35bd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7fa383e388c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #19 0x7fa383e82c27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7fa381ddea9f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7fa381e30a98 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7fa381ddbe73 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7fa383e826f3 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7fa383e3457b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7fa383e3c1b4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x7fa385f75d5e in kdemain () from /lib64/libkdeinit5_dolphin.so #27 0x7fa385d7b1e2 in ?? () from /lib64/libc.so.6 #28 0x55ec1d7f00ae in _start () [Inferior 1 (process 5056) detached] Possible duplicates by query: bug 439605, bug 439542, bug 439303, bug 439043, bug 438933. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592
--- Comment #3 from Eugene Shalygin ---
Debug build does not seem to crash. In console output I see the following:
kdevelop.plugins.definesandincludes: error while fetching defines for the
compiler: "clang" ("-xc", "-std=c++17", "-dM", "-E", "-") "error: invalid
argument '-std=c++17' not allowed with 'C'\n"
kdevelop.plugins.definesandincludes: error while fetching includes for the
compiler: "clang" "clang version 12.0.0\nTarget: x86_64-pc-linux-gnu\nThread
model: posix\nInstalledDir: /usr/lib/llvm/12/bin\nSelected GCC installation:
/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0\nCandidate multilib: .;@m64\nCandidate
multilib: 32;@m32\nSelected multilib: .;@m64\n (in-process)\n
\"/usr/lib/llvm/12/bin/clang-12\" -cc1 -triple x86_64-pc-linux-gnu -E
-disable-free -disable-llvm-verifier -discard-value-names -main-file-name -
-mrelocation-model static -mframe-pointer=all -fmath-errno -fno-rounding-math
-mconstructor-aliases -munwind-tables -target-cpu x86-64 -tune-cpu generic
-fno-split-dwarf-inlining -debugger-tuning=gdb -v -resource-dir
/usr/lib/llvm/12/bin/../../../../lib/clang/12.0.0 -internal-isystem
/usr/local/include -internal-isystem
/usr/lib/llvm/12/bin/../../../../lib/clang/12.0.0/include
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-std=gnu++17 -fdebug-compilation-dir
/home/eugene/develop/alien/cmake/cbuild/debug -ferror-limit 19
-fgnuc-version=4.2.1 -o - -x c -\nerror: invalid argument '-std=gnu++17' not
allowed with 'C'\n"
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 424649] [Wayland] Cannot paste text copied from GTK app after closing it, even if the text is visibly in Klipper
https://bugs.kde.org/show_bug.cgi?id=424649 --- Comment #15 from Bharadwaj Raju --- Ok, I can reproduce the issue with both Gedit and Inkscape, only if "Prevent empty clipboard" is turned off in Klipper settings. My other Klipper settings, may be relevant: - Save clipboard contents on exit: YES - Prevent empty clipboard: NO - Ignore images: YES - Ignore selection: NO - Text selection only: NO - Sync clipboard and selection: NO Turning on "Prevent empty clipboard" (which is on by default), makes the bug disappear. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427953] Unique instance and open in tabs ignored
https://bugs.kde.org/show_bug.cgi?id=427953 --- Comment #5 from Christoph Cullmann --- Yes, there is no working dbus there. Kate uses QtSingleApplication for that on Windows, but that is hacky, too. I could try to improve the error message by checking better if some dbus session bus is around at all. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438559] Domain name quickgit.kde.org does not exist
https://bugs.kde.org/show_bug.cgi?id=438559 --- Comment #8 from Christopher Yeleighton --- (In reply to Aleix Pol from comment #7) > I have no idea what you are talking about. Discover doesn't list > quickgit.kde.org. Are you maybe running an old version of Discover? > > In the end it's true, at some point quickgit.kde.org was a thing. Not > anymore. Discover does not list any home page for itself, that is why distribution packagers get it wrong. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #2 from Eugene Shalygin --- Unfortunately, under Valgrind C++ parsing does not work at all: KDevelop can not find any include file even those from C++ stdlib. I see many messages from Valgring with the following content: Thread 1: status = VgTs_Runnable syscall 56 (lwpid 2096983) ==2096983==at 0x6818299: syscall (in /lib64/libc-2.33.so) ==2096983==by 0x613B4D3: QProcessPrivate::start(QFlags) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x26F4953E: .LTHUNK0.lto_priv.1 (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevdefinesandincludesmanager.so) ==2096983==by 0x26F40BE0: .LTHUNK3.lto_priv.0 (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevdefinesandincludesmanager.so) ==2096983==by 0x26F2CF29: DefinesAndIncludesManager::defines(KDevelop::ProjectBaseItem*, KDevelop::IDefinesAndIncludesManager::Type) const (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevdefinesandincludesmanager.so) ==2096983==by 0x27C98CC8: ClangParseJob::ClangParseJob(KDevelop::IndexedString const&, KDevelop::ILanguageSupport*) (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevclangsupport.so) ==2096983==by 0x27C99DB5: non-virtual thunk to ClangSupport::createParseJob(KDevelop::IndexedString const&) (in /usr/lib64/qt5/plugins/kdevplatform/35/kdevclangsupport.so) ==2096983==by 0x6981E22: KDevelop::BackgroundParser::parseDocuments() (in /usr/lib64/libKDevPlatformLanguage.so.5.6.40) ==2096983==by 0x61CDEE5: QObject::event(QEvent*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x518D4CE: QApplicationPrivate::notify_helper(QObject*, QEvent*) (in /usr/lib64/libQt5Widgets.so.5.15.2) ==2096983==by 0x61AA417: QCoreApplication::notifyInternal2(QObject*, QEvent*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61AAEB1: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61F10C2: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x9B0244A: g_main_context_dispatch (in /usr/lib64/libglib-2.0.so.0.6800.3) ==2096983==by 0x9B5C107: g_main_context_iterate.constprop.0 (in /usr/lib64/libglib-2.0.so.0.6800.3) ==2096983==by 0x9AFC5DE: g_main_context_iteration (in /usr/lib64/libglib-2.0.so.0.6800.3) ==2096983==by 0x61F5327: QEventDispatcherGlib::processEvents(QFlags) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61A29A2: QEventLoop::exec(QFlags) (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x61ADD8F: QCoreApplication::exec() (in /usr/lib64/libQt5Core.so.5.15.2) ==2096983==by 0x1144F0: main (in /usr/bin/kdevelop) client stack range: [0x1FFEFE1000 0x1FFF000FFF] client SP: 0x1FFEFFDC98 valgrind stack range: [0x10029AE000 0x1002AADFFF] top usage: 19456 of 1048576 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432975] krunner starts applications with cwd "/" with init system other than systemd (openrc, runit, ...)
https://bugs.kde.org/show_bug.cgi?id=432975 --- Comment #6 from Felix Tiede --- Behaviour is unchanged in plasma-5.22.3, no change so far. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427855] There's no option to enable/disable startup elements
https://bugs.kde.org/show_bug.cgi?id=427855 --- Comment #16 from Nick Stefanov --- Plasma 5.22.3 - there's no option to enable/disable a startup entry. -- You are receiving this mail because: You are watching all bug changes.
