[gwenview] [Bug 466836] Add a sort option "As in Dolphin" in the available sorting options; Sorting is not followed Dolphin in some cases.
https://bugs.kde.org/show_bug.cgi?id=466836 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 236059] Gwenview: use same sort order as current Dolphin view
https://bugs.kde.org/show_bug.cgi?id=236059 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443168] Add a setting to not follow sorting as in Dolphin when Gwenview started by image click
https://bugs.kde.org/show_bug.cgi?id=443168 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484218] Windows "clicking through", plasma menu not clickable on X11
https://bugs.kde.org/show_bug.cgi?id=484218 --- Comment #3 from Kamil --- (In reply to Kamil from comment #2) > So in my case problem reveal itself in 2 scenarios: > 1. In conjunction with right mouse click and then clicking on context menus. > After this all mouse pointer is moving but click inputs is "going to null" > also context menu that appeared does not disappear after clicking on it or > outside of it. To make things work again in this case I have to press ESC to > close opened context menu and mouse starts to work. > 2. If standard taskbar is configured to display a thumbnails of application > windows, then if I right-click on that thumbnail then no context menu > displayed and mouse starting to act as it has no buttons, in this case ESC > trick does not works, but I accidentally found that calling tdrop with > Alacritty window by hotkey causes to make mouse buttons work again > Found that unexpectedly thanks to sxhkd/tdrop that used to make drop down > terminal with Alacritty. But did not find how to trigger this problem. > Definitely restarting kwin with ```kwin_x11 --replace``` make this bug to > disappear for a while in addition: I use Arch Linux: Plasma 6.0.3 QT 6.6.3 KDE Frameworks Version: 6.0.0 Graphics Platform: X11 Graphics driver: admgpu (free) Graphics card: Radeon 6800XT -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484218] Windows "clicking through", plasma menu not clickable on X11
https://bugs.kde.org/show_bug.cgi?id=484218 Kamil changed: What|Removed |Added Ever confirmed|0 |1 CC||kamil.kurams...@tatar.ru Status|REPORTED|CONFIRMED --- Comment #2 from Kamil --- So in my case problem reveal itself in 2 scenarios: 1. In conjunction with right mouse click and then clicking on context menus. After this all mouse pointer is moving but click inputs is "going to null" also context menu that appeared does not disappear after clicking on it or outside of it. To make things work again in this case I have to press ESC to close opened context menu and mouse starts to work. 2. If standard taskbar is configured to display a thumbnails of application windows, then if I right-click on that thumbnail then no context menu displayed and mouse starting to act as it has no buttons, in this case ESC trick does not works, but I accidentally found that calling tdrop with Alacritty window by hotkey causes to make mouse buttons work again Found that unexpectedly thanks to sxhkd/tdrop that used to make drop down terminal with Alacritty. But did not find how to trigger this problem. Definitely restarting kwin with ```kwin_x11 --replace``` make this bug to disappear for a while -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483969] When you select any tool and use it, the toolbar disappears.
https://bugs.kde.org/show_bug.cgi?id=483969 --- Comment #3 from Kamil --- The error has been fixed. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 483969] When you select any tool and use it, the toolbar disappears.
https://bugs.kde.org/show_bug.cgi?id=483969 Kamil changed: What|Removed |Added CC||k...@ya.ru --- Comment #2 from Kamil --- I also noticed this error. In the panel I took the "Arrow" tool and worked with it, then I want to take the "Text" tool, but I can’t because the panel is no longer shown -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483523] KMail crashes when select multiple recipients with Shift
https://bugs.kde.org/show_bug.cgi?id=483523 --- Comment #1 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 167153 --> https://bugs.kde.org/attachment.cgi?id=167153=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483523] New: KMail crashes when select multiple recipients with Shift
https://bugs.kde.org/show_bug.cgi?id=483523 Bug ID: 483523 Summary: KMail crashes when select multiple recipients with Shift Classification: Applications Product: kmail2 Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: 9luty1...@gmail.com Target Milestone: --- Created attachment 167151 --> https://bugs.kde.org/attachment.cgi?id=167151=edit backtrace SUMMARY KMail crashes when select multiple recipients with Shift that are in group. When I select contacts outside group id does work. STEPS TO REPRODUCE 1. Compose mail 2. Open dialog with recipients selection 3. Select multiple contacts IN GROUP OBSERVED RESULT Kmail crashes EXPECTED RESULT Contacts are selected SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.7-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: Latitude 5520 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476540] Screens dims but doesn't un-dim after screens were switched off
https://bugs.kde.org/show_bug.cgi?id=476540 Kamil Trysiński changed: What|Removed |Added CC||kamilk...@pm.me --- Comment #7 from Kamil Trysiński --- The same happens on my PC, from time to time the screens will not return to 70% brightness, but will stay at 10-20%. Seems like it's happening only sometimes, not every time the screen dims. Everything was working ok before the recent update to Plasma 6. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel: 6.7.9-arch1-1 (64 bit) Graphics Platform: X11 ADDITIONAL INFORMATION GPU : NVIDIA RTX 3060 Ti -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 482969] New: kglobalaccel does not provide a DBus service file, causing kwin to be unable to start it
https://bugs.kde.org/show_bug.cgi?id=482969
Bug ID: 482969
Summary: kglobalaccel does not provide a DBus service file,
causing kwin to be unable to start it
Classification: Frameworks and Libraries
Product: frameworks-kglobalaccel
Version: 6.0.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: dkk...@gmail.com
Target Milestone: ---
Since the Plasma 6 upgrade in Arch Linux, KWin has been unable to start
kglobalaccel on my LXQt-based system, which leads to global shortcuts like
Alt-Tab or Alt-F4 not working.
I traced this to a DBus service file missing from the installation. The error
message from KWin is :
kwin_x11[783]: Couldn't start kglobalaccel from org.kde.kglobalaccel.service:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name is not
activatable")
KWin also starts the KScreen backend launcher which does provide a DBus file in
its installation - see
https://invent.kde.org/plasma/libkscreen/-/blob/master/src/backendlauncher/CMakeLists.txt
. This file is picked up by Arch packaging and installed into
/usr/share/dbus-1/services/ , which makes the service "activatable" and thus
KWin is able to run it.
Manually creating /usr/share/dbus-1/services/org.kde.kglobalaccel.service with
the following content :
[D-BUS Service]
Name=org.kde.kglobalaccel
Exec=/usr/lib/kglobalacceld
SystemdService=plasma-kglobalaccel.service
Makes the issue go away.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 482927] New: Too large margins/paddings on Overview, Grid View, Present Windows.
https://bugs.kde.org/show_bug.cgi?id=482927 Bug ID: 482927 Summary: Too large margins/paddings on Overview, Grid View, Present Windows. Classification: Plasma Product: kwin Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: kam.laskow...@gmail.com Target Milestone: --- Created attachment 166741 --> https://bugs.kde.org/attachment.cgi?id=166741=edit Gaps between desktops and margins or padding between the edges or other apps I'm not entirely sure if this is the appropriate place to report this, but I'll give it a try. In the Overview and Grid View, the margins or padding are excessively large, leaving a considerable amount of space unused. In my opinion, these margins/paddings should be much smaller. Personally, I would prefer to completely eliminate the gaps from the edge of the screen or between visible applications. Ideally, windows would simply be flush against each other. You can observe the current margins/paddings in the screenshots. The red border I've added indicates the suggested margins/paddings that would be ideal for me. I hope the screenshots provide clarity on the issue. Personally, I consider it somewhat of a bug that such a significant amount of space is wasted, and users should have configuration options to eliminate such large margins/paddings. Additionally, I'd like to point out that the gaps between virtual desktops in Grid View should also be adjustable. I would prefer to set them to 0 as well. STEPS TO REPRODUCE 1. Toggle Grid View 2. Toggle Overview OBSERVED RESULT The margins or padding are excessively large. EXPECTED RESULT The padding/margin between the edges or other apps should be significantly smaller in both the Overview and Grid View. The margins or padding should be smaller, and ideally, users should be able to adjust them in the settings. I would also appreciate it if the "Filter" input in the Overview view could be disabled to gain some additional space. If anything is unclear, please let me know. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476995] The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995 --- Comment #6 from Kamil Dudka --- The last update of my Gentoo Linux system made the bug disappear. Surprisingly, it was not an update of gwenview what fixed the bug. It must have been the update of KDE Frameworks to 5.115.0. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 444108] kmail dragging mail to sidebar starts scrolling fast in wayland sessions
https://bugs.kde.org/show_bug.cgi?id=444108 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 440874] Folder list scrolls up when trying to drag message into folder
https://bugs.kde.org/show_bug.cgi?id=440874 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476995] The Folders pane only show subdirs one level deep
https://bugs.kde.org/show_bug.cgi?id=476995 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 Kamil Cukrowski changed: What|Removed |Added CC||kamilcukrow...@gmail.com --- Comment #12 from Kamil Cukrowski --- +1 Hi! KDE is amazing, and thanks for making it! Please make this behavior, if it is intentional, optional. I would kindly want every time I click Meta+Right the window should be placed exactly at the right exact half of the screen every time, irrelevant if it was resized, or full screen, or anything. Please kindly add an option to make it possible, it is a really simple behavior. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467547] Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen
https://bugs.kde.org/show_bug.cgi?id=467547 Kamil Paral changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||kpa...@redhat.com Resolution|UPSTREAM|--- --- Comment #5 from Kamil Paral --- Reopening this bug, it's still not fixed. The downstream Fedora bug contains backtraces of the live sddm processes when this issue happens. Please see https://bugzilla.redhat.com/show_bug.cgi?id=2179591#c34 and below. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 330356] Panel auto-hide stops working after using desktop for a while.
https://bugs.kde.org/show_bug.cgi?id=330356 Kamil changed: What|Removed |Added CC||kamil.kurams...@tatar.ru --- Comment #43 from Kamil --- I have same issue Arch Linux with latest updates(06/03/2023). Each time a facing this problem I just restarting plasmashell: [code] kquitapp5 plasmashell && plasmashell [/code] -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 402833] memcheck/tests/overlap testcase fails, memcpy seen as memmove
https://bugs.kde.org/show_bug.cgi?id=402833 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462316] With all-DisplayPort monitor setup, containment on secondary DisplayPort monitor gets lost when it turn off and then back on, but returns when plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=462316 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460289] Opening the detailed progress window does nothing
https://bugs.kde.org/show_bug.cgi?id=460289 --- Comment #5 from Kamil Dudka --- I have rebuilt kmail-5.21.3 with the fix mentioned in comment #4 and the progress popup now works again. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460289] Opening the detailed progress window does nothing
https://bugs.kde.org/show_bug.cgi?id=460289 Kamil Dudka changed: What|Removed |Added Version|5.21.1 |5.21.3 --- Comment #3 from Kamil Dudka --- I am still affected by the bug with kmail-5.21.3. I think the progress popup is there but it is just not visible. If I enable "message preview pane below the message list" in Settings -> Configure KMail -> Appearance -> Layout and push the "Show Message Structure" button available via Settings -> Configure Toolbars, I can see a thin stripe of the progress popup in the border of the Message Structure pane. Then if change height of the Message Structure pane, I can see other parts of the hidden progress popup. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460289] Opening the detailed progress window does nothing
https://bugs.kde.org/show_bug.cgi?id=460289 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 460289] Opening the detailed progress window does nothing
https://bugs.kde.org/show_bug.cgi?id=460289 Kamil Dudka changed: What|Removed |Added CC||kol...@aon.at --- Comment #2 from Kamil Dudka --- *** Bug 462540 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462540] list of current jobs no longer shown
https://bugs.kde.org/show_bug.cgi?id=462540 Kamil Dudka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from Kamil Dudka --- *** This bug has been marked as a duplicate of bug 460289 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462540] list of current jobs no longer shown
https://bugs.kde.org/show_bug.cgi?id=462540 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kamil Dudka --- Same problem here after updating to kmail-5.21.3. I think the progress popup is there but it is just not visible. If I enable "message preview pane below the message list" in Settings -> Configure KMail -> Appearance -> Layout and push the "Show Message Structure" button available via Settings -> Configure Toolbars, I can see a thin stripe of the progress popup in the border of the Message Structure pane. Then if change height of the Message Structure pane, I can see other parts of the hidden progress popup. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 456471] Failed to connect with sstp 1.3.0
https://bugs.kde.org/show_bug.cgi?id=456471 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kamil Piwowarski <9luty1...@gmail.com> --- Bug still exists :( work-around: > nmcli connection modify +vpn.data "connection-type > = password" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459402] RGB Range field cannot be seen in Display Configuration on Wayland
https://bugs.kde.org/show_bug.cgi?id=459402 --- Comment #2 from Kamil Sołtysik --- (In reply to Nate Graham from comment #1) > That means your hardware or drivers don't support this feature. If you know > the hardware does, then the driver is to blame. It's AMDGPU on RX 580 - how to check whether the support is there or not? Any ideas where to play with stuff to make it work? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459402] RGB Range field cannot be seen in Display Configuration on Wayland
https://bugs.kde.org/show_bug.cgi?id=459402 Kamil Sołtysik changed: What|Removed |Added CC||ka...@soltysik.net -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 459402] New: RGB Range field cannot be seen in Display Configuration on Wayland
https://bugs.kde.org/show_bug.cgi?id=459402 Bug ID: 459402 Summary: RGB Range field cannot be seen in Display Configuration on Wayland Classification: Unclassified Product: KScreen Version: 5.25.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: ka...@soltysik.net Target Milestone: --- Created attachment 152227 --> https://bugs.kde.org/attachment.cgi?id=152227=edit Display Configuration window, as seen by me SUMMARY STEPS TO REPRODUCE 1. Launch kscreen "Display Configuration" settings from configuration window OBSERVED RESULT No "RGB range" selection can be made, the option is not visible. RgbRange parameter cannot be changed from kscreen-doctor seemingly. EXPECTED RESULT "RGB range" or similar selection can be made. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION I've double-checked I'm running Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453818] Panels on one screen block windows across all screens
https://bugs.kde.org/show_bug.cgi?id=453818 Kamil changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Kamil --- Not fixed in 5.25. KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-arch2-1 (64 bit) Graphics Platform: X11 (NVIDIA) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 457285] KConfigWatcher::config() returns nullptr when built without DBUS support
https://bugs.kde.org/show_bug.cgi?id=457285 Kamil Dudka changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED Latest Commit||ed0ecf5b7640f0eca4aeba0e19c ||f173bc224585e --- Comment #3 from Kamil Dudka --- The fix has been merged: https://invent.kde.org/frameworks/kconfig/-/commit/ed0ecf5b7640f0eca4aeba0e19cf173bc224585e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 457285] KConfigWatcher::config() returns nullptr when built without DBUS support
https://bugs.kde.org/show_bug.cgi?id=457285 --- Comment #2 from Kamil Dudka --- I have submitted a merge request to fix this: https://invent.kde.org/frameworks/kconfig/-/merge_requests/134 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Kamil Dudka changed: What|Removed |Added Ever confirmed|0 |1 CC||kdu...@redhat.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #403 from Kamil Dudka --- I am also facing this bug with 5.24.6. When I connect my laptop to a docking station, the panel moves to a wrong display, even though the settings stays the same. When I disconnect the laptop from the docking station and connect it again, the panel moves back to its original position. That is, the panel's position cycles with each reconnect. The following command moves the panel to the correct display without the need for HW reconnect: $ killall --wait plasmashell && plasmashell & -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 --- Comment #14 from Kamil Dudka --- The problem reported in comment #0 was actually caused by bug #457285. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session
https://bugs.kde.org/show_bug.cgi?id=423864 --- Comment #7 from Kamil Dudka --- (In reply to Kamil Dudka from comment #4) > After updating my Gentoo box to 5.20, the Log Out and Shut Down buttons in > plasma stopped working. They just cause plasma shell to crash. After > reverting the change mentioned in comment #2, the buttons work again. This was actually caused by bug #457285. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 457285] KConfigWatcher::config() returns nullptr when built without DBUS support
https://bugs.kde.org/show_bug.cgi?id=457285 --- Comment #1 from Kamil Dudka --- Created attachment 150988 --> https://bugs.kde.org/attachment.cgi?id=150988=edit [PATCH] KConfigWatcher: initialize d->m_config in constructor -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 457285] New: KConfigWatcher::config() returns nullptr when built without DBUS support
https://bugs.kde.org/show_bug.cgi?id=457285 Bug ID: 457285 Summary: KConfigWatcher::config() returns nullptr when built without DBUS support Product: frameworks-kconfig Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matt...@mjdsystems.ca Reporter: kdu...@redhat.com CC: kdelibs-b...@kde.org Target Milestone: --- As additional KDE applications started to use KConfigWatcher, they started to crash on my laptop running Gentoo Linux. I was trying to patch them one by one to prevent the crashes. Then I realized that kconfig was built without dbus support on my system. After rebuilding kconfig with -DKCONFIG_USE_DBUS, the crashes went away. I looked into the source code of KConfigWatcher and discovered that its constructor initializes d->m_config only if KCONFIG_USE_DBUS is defined: https://github.com/KDE/kconfig/blob/491f5464/src/core/kconfigwatcher.cpp#L47 Consequently KConfigWatcher::config() may return nullptr, which triggers null dereference at caller's side, where a non-null value is expected. STEPS TO REPRODUCE 1. build kconfig without dbus support OBSERVED RESULT Applications like plasma or kwin start to crash. EXPECTED RESULT No crashes. SOFTWARE/OS VERSIONS Linux: 5.15.52-gentoo-x86_64 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION Previously reported with backtraces at: bug #423864 comment #4 bug #453242 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 456471] Failed to connect with sstp 1.3.0
https://bugs.kde.org/show_bug.cgi?id=456471 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added CC||9luty1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 456471] New: Failed to connect with sstp 1.3.0
https://bugs.kde.org/show_bug.cgi?id=456471 Bug ID: 456471 Summary: Failed to connect with sstp 1.3.0 Product: plasma-nm Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: 9luty1...@gmail.com Target Milestone: --- SUMMARY After upgrade I am not able to connect with sstp vpn. I got error: "plugin NeedSecrets request #1 failed: GDBus.Error:org.freedesktop.NetworkManager.VPN.Error.BadArguments" Someone reporter and described it here: https://bugzilla.redhat.com/show_bug.cgi?id=2084525 https://gitlab.gnome.org/GNOME/network-manager-sstp/-/issues/50 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454044] New: Add option to unmount an sftp connection
https://bugs.kde.org/show_bug.cgi?id=454044 Bug ID: 454044 Summary: Add option to unmount an sftp connection Product: dolphin Version: 22.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bygreen...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY After I unlock the connection with my private key passphrase, Dolphin remembers it and will not ask for the private key again till I log out of my Plasma session. Can a button be added to completely unmount the sftp connection so it asks for my private key passphrase again? The button could be in the toolbar, or when rightclicking the entry in Places. An option to unmount after X minutes of inactivity or after Dolphin closes would be nice to have as well. It seems like an unnecessary security risk. And it's just annoying in general, I manage multiple servers that look identical in the home folder, but never multiple at once, it's very easy to click on the wrong server in Places and look through the wrong server's files, just because it was unlocked before. STEPS TO REPRODUCE 1. Connect to an sftp server by typing a sftp:// link in the location bar 2. Type your private key passphrase 3. There is no way to disconnect 4. Close dolphin 5. Connect to the same sftp server again 6. Dolphin now thinks for a while, like it's creating a new connection? 7. It did not ask for the passphrase this time SOFTWARE/OS VERSIONS Linux: 5.17.7-arch1-2 (64-bit) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION This is possible in the Nemo file manager. I asked on kde subreddit before I write this but I got no answers. I thought it might be the fault of a keyring or a wallet, but I do not see anything like this running on my system. Additionally, connecting to a second server that requires the same private key, it asks me to type the passphrase again, so this leads me to a conclusion it's a problem on Dolphin's side. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453818] Panels on one screen block windows across all screens
https://bugs.kde.org/show_bug.cgi?id=453818 --- Comment #2 from Kamil --- (In reply to Nate Graham from comment #1) > Does it happen in the Wayland session too? Yes, it happens on Wayland as well. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 --- Comment #13 from Kamil Dudka --- I do not think that the problem reported in comment #0 has been resolved. Bug #453734 has obviously not much in common with the SIGSEGV captured in comment #0. m_configWatcher->config() could hardly become nullptr due to missing plasma-geolocation-gps.so. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453818] New: Panels on one screen block windows across all screens
https://bugs.kde.org/show_bug.cgi?id=453818 Bug ID: 453818 Summary: Panels on one screen block windows across all screens Product: kwin Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: bygreen...@gmail.com Target Milestone: --- Created attachment 148844 --> https://bugs.kde.org/attachment.cgi?id=148844=edit Video showing this issue SUMMARY Panels attached to one screen that are not drawn on the second screen block window movement as if the panel stretches all the way across the second screen. STEPS TO REPRODUCE 1. Have 2 screens side by side 2. Attach a panel to the top of the main screen 3. Try to move a window to the top of the secondary screen OBSERVED RESULT The window will be blocked at the y-coordinate of the panel, that is on the other screen. EXPECTED RESULT The window should only get blocked by the visible parts of the panel. SOFTWARE/OS VERSIONS Linux: 5.17.7-arch1-1 (64 bit) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION X11, Nvidia proprietary driver -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 --- Comment #8 from Kamil Dudka --- I was observing the crashes (approx. one crash per second) on multiple machines after the update. It did not seem related to anything specific in ~/.config/kwinrc. On one of the machines the file has this content: [$Version] update_info=kwin.upd:enable-scale-effect-by-default [Compositing] Enabled=false OpenGLIsUnsafe=false [Desktops] Id_1=80512e95-79c0-44cc-9d1d-8d0c892714de Number=1 Rows=1 On another machine the file has this content: [$Version] update_info=kwin.upd:replace-scalein-with-scale,kwin.upd:port-minimizeanimation-effect-to-js,kwin.upd:port-scale-effect-to-js,kwin.upd:port-dimscreen-effect-to-js,kwin.upd:auto-bordersize,kwin.upd:animation-speed,kwin.upd:desktop-grid-click-behavior,kwin.upd:no-swap-encourage,kwin.upd:make-translucency-effect-disabled-by-default,kwin.upd:remove-flip-switch-effect,kwin.upd:remove-cover-switch-effect,kwin.upd:remove-cubeslide-effect,kwin.upd:remove-xrender-backend,kwin.upd:enable-scale-effect-by-default [Compositing] Enabled=false OpenGLIsUnsafe=true [Desktops] Id_1=2545027f-687a-4bc2-9d8c-ad4e20f1c3b8 Number=1 Rows=1 [org.kde.kdecoration2] BorderSize=Normal BorderSizeAuto=false ButtonsOnLeft=MS ButtonsOnRight=HIAX CloseOnDoubleClickOnMenu=false ShowToolTips=true library=org.kde.kwin.aurorae theme=kwin4_decoration_qml_plastik -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 --- Comment #21 from Kamil Dudka --- After upgrade to plasma 5.24.4 I can see "Sleep", "Hibernate", and "Switch User" buttons on my lock screen. The first two hunks of attachment #127083 are still needed to keep the HW power button functional while the screen is locked. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451894] Hidden dock with no compositor still leaves a line
https://bugs.kde.org/show_bug.cgi?id=451894 Kamil changed: What|Removed |Added Resolution|NOT A BUG |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #2 from Kamil --- (In reply to Michail Vourlakos from comment #1) > only thing to avoid this is to enable Behavior(advanced) -> Activate KWin > edge after hiding That setting does have any effect on this issue. The line is still there no matter if KWin edge is enabled or disabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 --- Comment #1 from Kamil Dudka --- The cause is similar to bug #423864 comment #4: m_configWatcher->config() for some reason returns nullptr. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 453242] New: kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade
https://bugs.kde.org/show_bug.cgi?id=453242 Bug ID: 453242 Summary: kded5 keeps crashing in LocationUpdater::resetLocator() after upgrade Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Night Color Assignee: plasma-b...@kde.org Reporter: kdu...@redhat.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. I updated my Gentoo Linux machines with KDE to latest stable versions of everything. OBSERVED RESULT Suddenly nm-applet stopped working and kded5 keeps crashing approx. once per second: Apr 30 21:38:18 b360 kded5[72702]: Installing the delayed initialization callback. Apr 30 21:38:18 b360 NetworkManager[2047]: [1651347498.1476] agent-manager: agent[9abe7988027e87ba,:1.1684/org.kde.plasma.networkmanagement/1026]: agent registered Apr 30 21:38:18 b360 systemd-coredump[72705]: elfutils disabled, parsing ELF objects not supported Apr 30 21:38:18 b360 systemd-coredump[72705]: [] Process 72675 (kded5) of user 1026 dumped core. Apr 30 21:38:18 b360 systemd[1]: systemd-coredump@1617-72703-0.service: Deactivated successfully. Apr 30 21:38:18 b360 kded5[72702]: kcm_touchpad: Using X11 backend Apr 30 21:38:18 b360 kded5[72702]: kf.config.core: Use of KConfigWatcher without DBus support. You will not receive updates Apr 30 21:38:19 b360 systemd[1]: Started Process Core Dump (PID 72728/UID 0). Apr 30 21:38:19 b360 systemd-coredump[72730]: Removed old coredump core.kded5.1026.d127f538c70549308c91f1781604c632.5497.165134278100.zst. EXPECTED RESULT No crashes after update to stable release. SOFTWARE/OS VERSIONS Linux: 5.15.32-gentoo-r1-x86_64 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION (gdb) bt #0 0x7fe9d156a06c in () at /lib64/libc.so.6 #1 0x7fe9d151e792 in raise () at /lib64/libc.so.6 #2 0x7fe9d256985c in KCrash::defaultCrashHandler(int) () at /usr/lib64/libKF5Crash.so.5 #3 0x7fe9d151e830 in () at /lib64/libc.so.6 #4 KConfigBase::isGroupImmutable(QByteArray const&) const (this=0x0, aGroup=...) at /var/tmp/portage/kde-frameworks/kconfig-5.92.0/work/kconfig-5.92.0/src/core/kconfigbase.cpp:78 #5 0x7fe9d1f175f8 in KConfigGroupPrivate::KConfigGroupPrivate(QExplicitlySharedDataPointer const&, QByteArray const&) (name=..., owner=..., this=0x563740d6fe80) at /usr/include/qt5/QtCore/qshareddata.h:161 #6 KConfigGroup::KConfigGroup(QExplicitlySharedDataPointer const&, QString const&) (this=this@entry=0x7ffefe2c2c30, master=..., _group=...) at /var/tmp/portage/kde-frameworks/kconfig-5.92.0/work/kconfig-5.92.0/src/core/kconfiggroup.cpp:491 #7 0x7fe9c4012764 in LocationUpdater::resetLocator() (this=0x563740d58cf0) at /var/tmp/portage/kde-plasma/plasma-workspace-5.24.4/work/plasma-workspace-5.24.4/libcolorcorrect/kded/locationupdater.cpp:28 #8 0x7fe9c4012ffa in KPluginFactory::createInstance(QWidget*, QObject*, QList const&) (parentWidget=, parent=, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:875 #9 0x7fe9d1e99272 in KPluginFactory::create(char const*, QWidget*, QObject*, QList const&, QString const&) (this= 0x563740cc8150, iface=0x7fe9d2586360 "KDEDModule", parentWidget=0x0, parent=0x563740af2930, args=..., keyword=...) at /var/tmp/portage/kde-frameworks/kcoreaddons-5.92.0/work/kcoreaddons-5.92.0/src/lib/plugin/kpluginfactory.cpp:232 #10 0x56374098a0c0 in () #11 0x56374098d0b2 in () #12 0x56374098d443 in () #13 0x56374098712a in () #14 0x7fe9d150a2fa in () at /lib64/libc.so.6 #15 0x7fe9d150a3a8 in __libc_start_main () at /lib64/libc.so.6 #16 0x563740987541 in () I do not need NightColor. If I comment out the body of LocationUpdater::resetLocator(), kded5 no longer crashes and everything seems to work as expected. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451894] New: Hidden dock with no compositor still leaves a line
https://bugs.kde.org/show_bug.cgi?id=451894 Bug ID: 451894 Summary: Hidden dock with no compositor still leaves a line Product: lattedock Version: 0.10.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: bygreen...@gmail.com Target Milestone: --- Created attachment 147728 --> https://bugs.kde.org/attachment.cgi?id=147728=edit At the bottom you can see the white pixels, the dock is dodging the browser. SUMMARY When the compositor is disabled, and the dock is dodging a window, it still leaves behind a single row of white pixels. STEPS TO REPRODUCE 1. Disable the compositor 2. Set the dock to dodge windows 3. Make it dodge a window OBSERVED RESULT A single row of white pixels is visible on the edge of the screen. EXPECTED RESULT Nothing is shown when the dock is dodging a window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #33 from Kamil Dudka --- Created attachment 146946 --> https://bugs.kde.org/attachment.cgi?id=146946=edit patch to reenable numbers, v21.08.3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 450029] New: Broadcast RGB setting gets reset to Automatic after reboot
https://bugs.kde.org/show_bug.cgi?id=450029 Bug ID: 450029 Summary: Broadcast RGB setting gets reset to Automatic after reboot Product: KScreen Version: 5.24.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: ka...@soltysik.net Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I have i915 as a driver and hence having wide range of colors by default is definitely not for me. In KDE however there's a RGB range option in Display settings applet which, in my case should be manually set to Full (it's Automatic by default, which probably means "whatever driver decides in its wisdom"). The option can also be set by kscreen-doctor: kscreen-doctor 'output.thescreenname.rgbrange.full The option however keeps getting reset to Automatic after rebooting - it doesnt matter if I set it through the applet or kscreen-doctor. Moreover, if I use libdrm's proptest to set properties of connectors so the option is set even in ttys, after starting KDE, I still get reverted to Automatic on it. STEPS TO REPRODUCE 1. Have i915 & a screen connected with HDMI 2. Set RGB range to Full in Display settings 3. Reboot OBSERVED RESULT Washed colors. EXPECTED RESULT Colorful colors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch, latest KDE Plasma Version: 5.24.0-1 KDE Frameworks Version: 5.90.0-1 Qt Version: 5.15.2+kde+r297-2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 334213] Stuck "Mail filter agent" progressbar
https://bugs.kde.org/show_bug.cgi?id=334213 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #17 from Kamil Dudka --- I have been observing this for 5 years or so. It still happens with kmail 5.17.3. I do not use any filters in kmail but it makes the overall progress bar less useful. Just quitting kmail and starting it again makes the problem disappear for me but the issue reappears whenever kmail starts akonadi for itself. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444634] dbus-daemon spamming about full message queue from kwin_x11 a few hours after startup
https://bugs.kde.org/show_bug.cgi?id=444634 Kamil Cukrowski changed: What|Removed |Added CC||kamilcukrow...@gmail.com --- Comment #4 from Kamil Cukrowski --- I have: Archlinux, 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) , kwin 5.23.3-1 I have the same messages flooding journal. After applying the above mentioned fix with nvidia-fake-powerd - the issue was fixed. Thank You. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443583] New: Toggled repos in Discover jump to the bottom of the list, and other repo names are changed to undefined
https://bugs.kde.org/show_bug.cgi?id=443583 Bug ID: 443583 Summary: Toggled repos in Discover jump to the bottom of the list, and other repo names are changed to undefined Product: Discover Version: 5.23.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: kpa...@redhat.com CC: aleix...@kde.org Target Milestone: --- This is an upstream report of Fedora downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=2011774 . I'll reprint the comment 0 here, please read the downstream report for full information, and also to see the attachments. With plasma-discover-5.22.90-3.fc35, repo configuration suffers from redrawing issues and confusing item reordering. If you enable/disable any repo in the "Fedora Linux 35" section, that repo, together will all other repos defined in that same file, is moved to the very bottom of the list (so e.g. "F35 Updates + Updates Debug + Updates Source" are moved to the bottom). If you don't pay close attention to this, you might get confused. For example if the 'updates' triplet jumps away and on the same place appears the 'fedora' triplet with the same selection as originally (the first item enabled, the other two disabled), you might not re-read the item again carefully and just assume that your click wasn't registered, and click again (and then it disappears from the view and you'll not realize you've just disabled the 'fedora' repo). Additionally, each time you perform the change, all items in the "Firmware Updates" and "Flatpak" sections get renamed to "undefined". For some items, scrolling up and down is enough the redraw them into proper names, for other items, you need to change the current tab to some other one and back. See the attached video: https://bugzilla.redhat.com/attachment.cgi?id=1830328 Version-Release number of selected component (if applicable): plasma-discover-5.23.0-1.fc35 How reproducible: always Steps to Reproduce: 1. go to Discover -> Settings 2. click an RPM repo to enable/disable it 3. see the repo (and related ones) disappear, find them at the bottom 4. see other items in other sections renamed to "undefined" -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #17 from Kamil Dudka --- (In reply to Anatol Rosch from comment #14) > Created attachment 127083 [details] > add suspend action to KDE Plasma lock screen Thanks for sharing! The above patch has solved the problem for me. The "Sleep" button in the UI is not aligned with the "Switch User" button but the HW button now finally makes the machine suspend even when the screen is locked. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423864] Updated "Confirm Logout" setting not applied on logout until next login session
https://bugs.kde.org/show_bug.cgi?id=423864 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #4 from Kamil Dudka --- After updating my Gentoo box to 5.20, the Log Out and Shut Down buttons in plasma stopped working. They just cause plasma shell to crash. After reverting the change mentioned in comment #2, the buttons work again. A backtrace of the crash follows: [KCrash Handler] #4 0x7f5e64871018 in KConfigBase::group(char const*) (this=0x0, str=str@entry=0x7f5e664a63f0 "General") at /var/tmp/portage/kde-frameworks/kconfig-5.78.0/work/kconfig-5.78.0/src/core/kconfigbase.cpp:43 #5 0x7f5e6648ca91 in SessionBackend::confirmLogout() const (this=) at /var/tmp/portage/kde-plasma/libkworkspace-5.20.5/work/plasma-workspace-5.20.5/libkworkspace/sessionmanagementbackend.cpp:65 #6 0x7f5e664896bd in SessionManagement::requestShutdown(SessionManagement::ConfirmationMode) (this=, confirmationMode=confirmationMode@entry=SessionManagement::ConfirmationMode::Default) at /var/tmp/portage/kde-plasma/libkworkspace-5.20.5/work/plasma-workspace-5.20.5/libkworkspace/sessionmanagement.cpp:129 #7 0x7f5e399d3719 in SystemEntry::run(QString const&, QVariant const&) (actionId=, argument=, this=) at /var/tmp/portage/kde-plasma/plasma-workspace-5.20.5-r3/work/plasma-workspace-5.20.5/applets/kicker/plugin/systementry.cpp:364 #8 SystemEntry::run(QString const&, QVariant const&) (this=, actionId=, argument=) at /var/tmp/portage/kde-plasma/plasma-workspace-5.20.5-r3/work/plasma-workspace-5.20.5/applets/kicker/plugin/systementry.cpp:347 #9 0x7f5e399d39f9 in SystemModel::trigger(int, QString const&, QVariant const&) (this=, row=, actionId=, argument=) at /var/tmp/portage/kde-plasma/plasma-workspace-5.20.5-r3/work/plasma-workspace-5.20.5/applets/kicker/plugin/systemmodel.cpp:83 #10 0x7f5e3998d75c in SystemModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffd1c740800, _o=) at applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_systemmodel.cpp:84 #11 SystemModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7ffd1c740800) at applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_systemmodel.cpp:77 #12 0x7f5e39991bb3 in SystemModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x55fd0fc80400, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7ffd1c740800) at applets/kicker/kickerplugin_autogen/7RBZBFH7CH/moc_systemmodel.cpp:121 #13 0x7f5e65a9b1ad in () at /usr/lib64/libQt5Qml.so.5 #14 0x7f5e65970d85 in () at /usr/lib64/libQt5Qml.so.5 #15 0x7f5e65972f07 in () at /usr/lib64/libQt5Qml.so.5 #16 0x7f5e65973d3b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib64/libQt5Qml.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 408817] Second monitor not recognized
https://bugs.kde.org/show_bug.cgi?id=408817 Kamil Neczaj changed: What|Removed |Added CC||knec...@gmail.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Kamil Neczaj --- I have the same problem. I run Arch Linux with kernel 5.9.13-arch1, kwin 5.20.4. I have Thinkpad P1 with Intel + Nvidia Quadro P2000 with nouveau drivers. However this works with Gnome! I see there two screens which on output of `xrandr` are labeled XWAYLAND0 and XWAYLAND1. At kde there is XWAYLAND0 only. Please tell me how can I get more info to debug it. As it works for me with Gnome out of the box I am sure I can help here :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 --- Comment #23 from Kamil Dudka --- (In reply to Nate Graham from comment #18) > Got it. Looks like everyone's actually complaining about Bug 422050, which > was just fixed! :) Yes, I was facing exactly this bug. Thank you for pointing me to the fix! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422050] Scrolling issues with PageDown/PageUp navigation
https://bugs.kde.org/show_bug.cgi?id=422050 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #20 from Kamil Dudka --- (In reply to Nate Graham from comment #15) > Fixed with > https://invent.kde.org/graphics/okular/-/commit/ > e637e2ed519cb2dfe523981b2d6dc34a9855716c in Okular 1.11.2 I confirm that the problem goes away if the above patch is applied on okular-20.04.3. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420755] Option to disable animated scroll transitions
https://bugs.kde.org/show_bug.cgi?id=420755 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 --- Comment #17 from Kamil Dudka --- (In reply to Nate Graham from comment #15) > Are we all talking about the same thing? Nope. For me the issue is the smooth scroll animation that blocks the scrolling. It makes it impossible to scroll large documents quickly with keyboard. I believe that the scroll distance can be to some extent configured as mentioned in another bug: Settings -> Configure Okular -> General -> Page Up/Down overlap -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 Kamil Dudka changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 --- Comment #13 from Kamil Dudka --- It might be inperfect but at least it is usable again. I am not a GUI developer either, so I will rather not touch the code myself. I would prefer if this bug was fixed by fully reverting the change that introduced the fancy animation on pgup/pgdn. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421822] 'Scroll Page Up'/'Scroll Page Down' actions do not scroll by pages
https://bugs.kde.org/show_bug.cgi?id=421822 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #11 from Kamil Dudka --- (In reply to triffid.hunter from comment #10) > Created attachment 130840 [details] > Prevent pgup/pgdn from triggering problematic "smooth" scroll This patch fixed the issue for me. I have a usable okular on my system again. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #68 from Kamil Piwowarski <9luty1...@gmail.com> --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #66 from Kamil Piwowarski <9luty1...@gmail.com> --- When it will be fixed? I've installed Majnaro KDE for my family. They aren't technical people and it's difficult for them to distinguish what the „Zaniechaj” is for. They were using Windows and have Android on their phones. They recognize easily „Anuluj” and the destination (cancelling) of that button but there are problems with recognizing what action will be done when they press „Zaniechaj”. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #30 from Kamil Dudka --- I just discovered that #include needs to be added to src/kmsystemtray.cpp when compiling kmail-19.12.3 with the attached patch. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 417041] New: [wayland] Quick Search placeholder text is transparent blur
https://bugs.kde.org/show_bug.cgi?id=417041 Bug ID: 417041 Summary: [wayland] Quick Search placeholder text is transparent blur Product: ksysguard Version: 5.17.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: 9luty1...@gmail.com Target Milestone: --- Created attachment 125603 --> https://bugs.kde.org/attachment.cgi?id=125603=edit Screenshot SUMMARY See attachment STEPS TO REPRODUCE 1. Run plasma wayland session 2. Open ksysguard OBSERVED RESULT Quick Search placeholder text is transparent blur EXPECTED RESULT Quick Search placeholder text is not transparent SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.0 Kernel Version: 5.5.0-1-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-3630QM CPU @ 2.40GHz Memory: 15,5 GiB -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 --- Comment #58 from Kamil Piwowarski <9luty1...@gmail.com> --- One of the goal of KDE is consistency. https://dot.kde.org/2019/09/07/kde-decides-three-new-challenges-wayland-consistency-and-apps In latest months there were done a lot of work to improve that and I am very happy with that. For example GTK3 apps looks and behavior better. I love using Plasma and the rest of Apps. Unfortunately there is still one thing that made me irritated, broke my workflow and ruin hard earned consistency. When I am using any Java/GKT3/Qt (non-KDE)/Electron/Wine/Android app next to KDE app I am very confused, because of this #BROKEN# translation. Please fix that bug. Firstly - because almost no one are using „Zaniechaj” as „Cancel” and almost no one know what does it mean in computer systems. Secondly - it is against one of the KDE goal which is consistency. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415440] New: SVG support - scripts
https://bugs.kde.org/show_bug.cgi?id=415440 Bug ID: 415440 Summary: SVG support - scripts Product: kdenlive Version: 19.12.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: 9luty1...@gmail.com Target Milestone: --- Created attachment 124645 --> https://bugs.kde.org/attachment.cgi?id=124645=edit example svg SUMMARY Feature request: support for JavaScript in SVG STEPS TO REPRODUCE 1. Create SVG file with JavaScript script (script replace text for each second - something like countdown) 2. Add that to kdenlive 3. Add to timeline OBSERVED RESULT JavaScript script doesn't work EXPECTED RESULT JavaScript script works -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412695] New: Plasmashell crash sometimes when I connect to VPN Network via network manager
https://bugs.kde.org/show_bug.cgi?id=412695 Bug ID: 412695 Summary: Plasmashell crash sometimes when I connect to VPN Network via network manager Product: plasmashell Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kbac...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.16.90) Qt Version: 5.13.1 Frameworks Version: 5.62.0 Operating System: Linux 5.3.1-arch1-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: I try to connect VPN via network manager from task bar. Crash sometimes occurs when I try to repeat it - Custom settings of the application: Added VPN Connection in Network Manager The crash can be reproduced sometimes. -- Backtrace: Application: Plazma (plasmashell), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f41e50a7c80 (LWP 806))] Thread 33 (Thread 0x7f414d7fa700 (LWP 3610)): #0 0x7f41e91e0415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f41e9ce8660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f41e9ce8752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f41eb96fdad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f41eb97005e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f41e9ce25b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f41e91da57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f41e996f0e3 in clone () at /usr/lib/libc.so.6 Thread 32 (Thread 0x7f414e7fc700 (LWP 2870)): #0 0x7f41e91e0415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f41e9ce8660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f41e9ce8752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f41eb96fdad in () at /usr/lib/libQt5Quick.so.5 #4 0x7f41eb97005e in () at /usr/lib/libQt5Quick.so.5 #5 0x7f41e9ce25b0 in () at /usr/lib/libQt5Core.so.5 #6 0x7f41e91da57f in start_thread () at /usr/lib/libpthread.so.0 #7 0x7f41e996f0e3 in clone () at /usr/lib/libc.so.6 Thread 31 (Thread 0x7f414dffb700 (LWP 2822)): #0 0x7f41e996018c in read () at /usr/lib/libc.so.6 #1 0x7f41e80069f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f41e80549f1 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7f41e80560d8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7f41e8056201 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7f41e9f08a1c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f41e9eaf4ec in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7f41e9ce1385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7f41eb8e46eb in () at /usr/lib/libQt5Quick.so.5 #9 0x7f41e9ce25b0 in () at /usr/lib/libQt5Core.so.5 #10 0x7f41e91da57f in start_thread () at /usr/lib/libpthread.so.0 #11 0x7f41e996f0e3 in clone () at /usr/lib/libc.so.6 Thread 30 (Thread 0x7f414effd700 (LWP 1584)): #0 0x7f41e91e0415 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f41e9ce8660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7f41e9ce8752 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #3 0x7f41bd3d6309 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7f41bd3d9d8b in () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7f41bd3d54fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7f41bd3d9de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7f41bd3d54fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7f41bd3d9de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #9 0x7f41bd3d54fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #10 0x7f41bd3d9de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #11 0x7f41bd3d54fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #12 0x7f41bd3d9de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #13 0x7f41bd3d54fe in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #14 0x7f41bd3d9de1 in () at /usr/lib/libKF5ThreadWeaver.so.5 #15 0x7f41bd3d54fe in
[plasma-nm] [Bug 411177] VPN password is not displayed even if store passwords is checked
https://bugs.kde.org/show_bug.cgi?id=411177 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added CC||9luty1...@gmail.com --- Comment #4 from Kamil Piwowarski <9luty1...@gmail.com> --- https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 400283] Kopete crashed while quitting
https://bugs.kde.org/show_bug.cgi?id=400283 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407797] Unseting act un new/unread crashes kmail
https://bugs.kde.org/show_bug.cgi?id=407797 --- Comment #6 from Kamil Dudka --- (In reply to Kamil Dudka from comment #5) The same scenario worked fine for me now with kmail 5.11.3 but I am not sure whether it was upgrade of kmail or something else that fixed it for me... -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410483] Filter with custom headers doesn't match
https://bugs.kde.org/show_bug.cgi?id=410483 Kamil changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 410483] New: Filter with custom headers doesn't match
https://bugs.kde.org/show_bug.cgi?id=410483 Bug ID: 410483 Summary: Filter with custom headers doesn't match Product: kmail2 Version: 5.11.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: kamil.kurams...@tatar.ru Target Milestone: --- Want to create a filter to match some custom header in messages. For example, X-MS-Exchange-Security - is a header inserted by Mail Server it has a specific value = beabed97-c8f6-4dff-a2a2-172912d88bc1. I have created a filter for this header: "X-MS-Exchange-Security" "beabed97-c8f6-4dff-a2a2-172912d88bc1" But it never match even if one apply it to specific message manually. Same thing if filter looks like: "" "beabed97-c8f6-4dff-a2a2-172912d88bc1" And selected filter action is not performed. Only if filter set to whole message it will start matching: "" "beabed97-c8f6-4dff-a2a2-172912d88bc1" STEPS TO REPRODUCE 1. Create a filter with _custom header_ that should match specific string 2. Got a message with _custom header_ you want to filter by. 3. Apply filter to message from 2. OBSERVED RESULT >From filter journal: [15:22:53] 0 = "" "beabed97-c8f6-4dff-a2a2-172912d88bc1" () [15:36:54] 0 = "" "beabed97-c8f6-4dff-a2a2-172912d88bc1" EXPECTED RESULT [15:22:53] 1 = "" "beabed97-c8f6-4dff-a2a2-172912d88bc1" () [15:36:54] 1 = "" "beabed97-c8f6-4dff-a2a2-172912d88bc1" Filter should match and action should be executed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: plasma-desktop 5.16.4-1 KDE Frameworks Version: plasma-framework 5.60.0-1 Qt Version: qt5-base 5.13.0-7 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407084] Changed behavior of profile shortcuts in Konsole
https://bugs.kde.org/show_bug.cgi?id=407084 --- Comment #16 from Kamil Dudka --- (In reply to Wolfgang Bauer from comment #15) > The change already has been reverted for 19.08: Perfect. Thanks for the good news! > https://cgit.kde.org/konsole.git/commit/?h=Applications/19.08=a1b64d7956485c6358bd2cccabde3843c1d314eb Thanks for the reference! I applied the patch locally and konsole now works as expected. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 407084] Changed behavior of profile shortcuts in Konsole
https://bugs.kde.org/show_bug.cgi?id=407084 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #14 from Kamil Dudka --- I did not even realize this could have been intentional. I though I hit some window redraw bug in compositor or something. It took me hours to google this bug report because I did not know what to look for. I had profiles like "default", "root shell", "Fedora VM", "CentOS VM", "Debian VM" and have been using the profile shortcuts to quickly fire up a new session of the chosen kind. After the update, the shortcuts only change the title of my konsole window without any other (useful) effect. Moreover, it is quite dangerous when I have root shell of my bare metal machine in a tab named "Fedora VM". Could you please restore the original behavior that I used to use for a decade or so? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407797] Unseting act un new/unread crashes kmail
https://bugs.kde.org/show_bug.cgi?id=407797 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #5 from Kamil Dudka --- I get a crash with similar backtrace on the same occasion but for me it happens only with 1 IMAP account out of 3. It does not seem to be folder-specific but account-specific. It happens consistently. Is there any workaround to change the property? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #27 from Kamil Dudka --- Comment on attachment 118961 --> https://bugs.kde.org/attachment.cgi?id=118961 patch to reenable numbers, v18.12 Works perfectly. Thanks for the quick fix! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521
--- Comment #25 from Kamil Dudka ---
Comment on attachment 114942
--> https://bugs.kde.org/attachment.cgi?id=114942
patch to reenable numbers, v18.04.3
I am not able to compile kmail-18.12.3 with this patch against up2date qt. The
build fails with this error:
/var/tmp/paludis/kde-apps-kmail-18.12.3/work/kmail-18.12.3/src/kmsystemtray.cpp:
In member function 'void KMail::KMSystemTray::updateCount(int)':
/var/tmp/paludis/kde-apps-kmail-18.12.3/work/kmail-18.12.3/src/kmsystemtray.cpp:175:31:
error: 'class QFontMetrics' has no member named 'width'; did you mean
'maxWidth'?
const int width = qfm.width(count < 100 ? QStringLiteral("99")
^
maxWidth
I was able to google up a page saying that QFontMetrics::width() is obsolete:
https://doc.qt.io/qt-5/qfontmetrics-obsolete.html
... but the page does not suggest any replacement for that method.
Any idea how to make it build again?
--
You are receiving this mail because:
You are watching all bug changes.
[i18n] [Bug 404286] Absurd "cancel" polish translation
https://bugs.kde.org/show_bug.cgi?id=404286 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added CC||9luty1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388440] scrolling in KMail: "page down" only works once
https://bugs.kde.org/show_bug.cgi?id=388440 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com --- Comment #15 from Kamil Dudka --- (In reply to Lukáš Turek from comment #12) > I hit this bug in Gentoo after updating to Qt 5.11.1 and it disappeared when > I rebuilt messagelib. Thank you for sharing the solution! Rebuilding kde-apps/messagelib on my Gentoo Linux box has fixed the problem for me, too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 401004] New: VPN ssh connection editor is not usable on small screen
https://bugs.kde.org/show_bug.cgi?id=401004 Bug ID: 401004 Summary: VPN ssh connection editor is not usable on small screen Product: plasma-nm Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: 9luty1...@gmail.com Target Milestone: --- Created attachment 116282 --> https://bugs.kde.org/attachment.cgi?id=116282=edit settings window SUMMARY VPN ssh connection editor is not usable when the window is small. STEPS TO REPRODUCE 1. Create new VPN ssh connection 2. Edit connection and resize window OBSERVED RESULT On small window input controls are changing their height EXPECTED RESULT Input controls height should be the same independently from window size. Scroll bar should appear when the content doesn't fit window. SOFTWARE/OS VERSIONS OS: Manjaro Linux KDE KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 401003] New: Cannot change VPN (sstp or pptp) connection password
https://bugs.kde.org/show_bug.cgi?id=401003 Bug ID: 401003 Summary: Cannot change VPN (sstp or pptp) connection password Product: plasma-nm Version: 5.14.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: 9luty1...@gmail.com Target Milestone: --- Created attachment 116281 --> https://bugs.kde.org/attachment.cgi?id=116281=edit settings window SUMMARY Changing password for sttp or pptp connections doesn't work. STEPS TO REPRODUCE 1. Create new VPN (sstp or pptp) connection with password 'test' 2. Edit connection, change password to 'test2' and save 3. Edit connection again and show password OBSERVED RESULT Password is 'test' EXPECTED RESULT Password is 'test2' SOFTWARE/OS VERSIONS OS: Manjaro Linux KDE KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Changing password manually in KWalletManager works as expected. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 396473] Can't enable blur or configure translucency
https://bugs.kde.org/show_bug.cgi?id=396473 Kamil changed: What|Removed |Added CC||redredempt...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kooka] [Bug 397877] New: libkookascan reported error: Error while scanning SANE reported error: Out of memory
https://bugs.kde.org/show_bug.cgi?id=397877 Bug ID: 397877 Summary: libkookascan reported error: Error while scanning SANE reported error: Out of memory Product: kooka Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libkscan Assignee: j...@keelhaul.me.uk Reporter: 9luty1...@gmail.com Target Milestone: --- Using Kooka 0.90 (GIT kooka-0.61-247-g8222a77) when I try to snan or previev my device starts working and after one second stops and Kooka displays error: "There was a problem during preview or scanning. Check that the scanner is still connected and switched on, and that media is loaded if required. Trying to use scanner device: brother3:bus4;dev3 libkookascan reported error: Error while scanning SANE reported error: Out of memory" Using Skanlite everything is ok. -- You are receiving this mail because: You are watching all bug changes.
[kooka] [Bug 397877] libkookascan reported error: Error while scanning SANE reported error: Out of memory
https://bugs.kde.org/show_bug.cgi?id=397877 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added CC||9luty1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397449] New: Muting 'Notification Sounds' has no effect
https://bugs.kde.org/show_bug.cgi?id=397449 Bug ID: 397449 Summary: Muting 'Notification Sounds' has no effect Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: redredempt...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Muting 'Notification Sounds' has no effect and all notification sounds are played at full volume except for 'Volume feedback' one that plays while changing the volume using my laptop's extra keyboard keys. Steps to Reproduce: 1. Open 'Audio Volume' configuration module; 2. Try muting 'Notification Sounds' volume; 3. Trigger a warning dialog box in 'Dolphin' file manager by selecting any item/file and pressing 'Del' button. Actual Results: The sound was made when the dialog box appeared. Expected Results: No sound should be played. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397445] New: Notification sounds don't play when any video game is run
https://bugs.kde.org/show_bug.cgi?id=397445 Bug ID: 397445 Summary: Notification sounds don't play when any video game is run Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: redredempt...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 The system's notification sounds do not play either through use of the play button in 'Notifications' configuration module or when a dialog box/notification popup is generated by a program like Dolphin or Konversation if any video game is played. Steps to reproduce: 1. Open 'Notifications' configuration module in 'System Settings'; 2. Click on the play button for any notification type with 'Play a sound" checked to verify whether the selected sound is played; 3. Run Steam client and run any game from your Steam library; 4a. Go back to the configuration module and click on the play button again. 4b. Open 'Dolphin' file manager and select any item/file and then press 'Del' button to trigger a warning dialog box. 4c. Enable popup notifications for new messages in a channel in 'Konversation' IRC client and wait for someone to send a message in a channel, which for notifications are enabled. Actual Results: No sound was played Expected Results: A notification sound should be played To get notification sounds working back, just close the game and the configuration module or the program (Dolphin or Konversation as in this example) and then follow all the steps above except for 3rd one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393723] Kwin master with bad blur effect on secondary monitor ( works perfectly on primary )
https://bugs.kde.org/show_bug.cgi?id=393723 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added CC||9luty1...@gmail.com --- Comment #14 from Kamil Piwowarski <9luty1...@gmail.com> --- *** Bug 396055 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 Kamil Piwowarski <9luty1...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #14 from Kamil Piwowarski <9luty1...@gmail.com> --- I am so stupid ;/ Sorry for wasting your time. Everything is ok. Some months ago I've testing multiscreen setup and I've created backup of `/usr/lib64/libkwin4_effect_builtins.so.1` --> `/usr/lib64/libkwin4_effect_builtins.so.1.bak`. When testing I've changed symlink from `/usr/lib64/libkwin4_effect_builtins.so.1.0.0` to point `/usr/lib64/libkwin4_effect_builtins.so.1.bak`. During updates symlinks didn't changed. So I was using old file libkwin4_effect_builtins.so and that was a problem. *** This bug has been marked as a duplicate of bug 393723 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #11 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113691 --> https://bugs.kde.org/attachment.cgi?id=113691=edit aligned to the left Only bottom monitor is ok -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #10 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113690 --> https://bugs.kde.org/attachment.cgi?id=113690=edit wayland - vertically aligned to the top Another bug - on vertically stacked screens (aligned to the top). See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #9 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113689 --> https://bugs.kde.org/attachment.cgi?id=113689=edit kwin_wayland without plasma I was doing some testing and experiments and when I run kwin_wayland remotely by ssh `XDG_SESSION_ID=c2 QT_QPA_PLATFORM=wayland kwin_wayland --libinput --exit-with-session=konsole` it almost works as expected. Almost, because you can see "lines" between screens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396055] Multiscreen Wayland: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=396055 --- Comment #8 from Kamil Piwowarski <9luty1...@gmail.com> --- Created attachment 113687 --> https://bugs.kde.org/attachment.cgi?id=113687=edit Window under console On first monitor - yes. -- You are receiving this mail because: You are watching all bug changes.
