[frameworks-kdesu] [Bug 452532] kdesu stopped working in KUbuntu due to sudo's use_pty option
https://bugs.kde.org/show_bug.cgi?id=452532 Ardith Metz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=396767 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 396767] kdesu doesn't work when "use_pty" sudo option is enabled
https://bugs.kde.org/show_bug.cgi?id=396767 Ardith Metz changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=452532 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 396767] kdesu doesn't work when "use_pty" sudo option is enabled
https://bugs.kde.org/show_bug.cgi?id=396767 Ardith Metz changed: What|Removed |Added Resolution|WORKSFORME |FIXED Version Fixed In||5.109 Latest Commit||https://invent.kde.org/fram ||eworks/kdesu/-/commit/70ce5 ||87226206cd43122e51ec1220a50 ||3e267436 --- Comment #4 from Ardith Metz --- This issue was re-reported as https://bugs.kde.org/show_bug.cgi?id=452532 and finally fixed by https://invent.kde.org/frameworks/kdesu/-/merge_requests/30 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu stopped working in KUbuntu due to sudo's use_pty option
https://bugs.kde.org/show_bug.cgi?id=452532 --- Comment #30 from Ardith Metz --- Just post mortem note: this issue in kdesu was originally reported in 2018 (with a hint someday use_pty becomes the default): https://bugs.kde.org/show_bug.cgi?id=396767 for which only action taken was autoclose after 5 years of inactivity :) I laughed a bit seeing it here with critical importance. Nevertheless I'm glad it's finally fixed. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 455928] New: Reset timer after suspend/resume
https://bugs.kde.org/show_bug.cgi?id=455928 Bug ID: 455928 Summary: Reset timer after suspend/resume Product: rsibreak Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- SUMMARY *** Currently RSIBreak doesn't reset its timer after suspend/resume periods which makes it out of sync with real time that passed since last break. *** STEPS TO REPRODUCE 1. Set break for 60 min 2. Work on machine for 45 min 3. Suspend machine for 2 hours. Go for jogging 4. Resume machine. OBSERVED RESULT RSIBreak will ask for break 15 min. If you skip it then it will ask again after 60 min which makes total interval 75 min without a break. EXPECTED RESULT RSIBreak should reset its timer and ask for break after 60min. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.95 Qt Version: 5.15.5 ADDITIONAL INFORMATION RSIBreak 0.12.15 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 455515] kdeinit isn't started in plasma session since plasma 5.25.0
https://bugs.kde.org/show_bug.cgi?id=455515 --- Comment #1 from Ardith Metz --- I think this may be side-effect from systemd based startup that was enabled by default on 5.25.0[1]. I think I didn't enabled it manually in the past releases. I'm not sure if it's safe to disable it manually now (or even if this is possible). [1] https://invent.kde.org/plasma/plasma-workspace/-/commit/cb0d2459f5a7fab075ded1488ae4a570b9e3178e -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 455515] New: kdeinit isn't started in plasma session since plasma 5.25.0
https://bugs.kde.org/show_bug.cgi?id=455515 Bug ID: 455515 Summary: kdeinit isn't started in plasma session since plasma 5.25.0 Product: ksmserver Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: itgvk...@grr.la CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Since Plasma update to 5.25, kdeinit isn't started with Plasma session anymore. it makes org.kde.klauncher5 dbus service unavailable until kdeinit is started manually. In the past there was attempt to stop starting kdeinit but it was reverted: https://github.com/KDE/plasma-workspace/commit/45ca31099613c3742fd7f9c88544944fe08404ca I didn't found any trace if changing it again was intentional. STEPS TO REPRODUCE 1. Start fresh Plasma 5.25 session 2. execute: qdbus org.kde.klauncher5 /KLauncher org.kde.KLauncher.exec_blind /usr/bin/kate "" OBSERVED RESULT qdbus call failed, nothing happens EXPECTED RESULT /usr/bin/kate was started SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 2.25.0 KDE Frameworks Version: 5.95 Qt Version: 5.14.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400451] kwin_wayland blocks TMPDIR env variable inheritance in Plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=400451 Ardith Metz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Ardith Metz --- As in Plasma 5.25 with the new systemd based startup it's no longer an issue, see https://invent.kde.org/plasma/kwin/-/merge_requests/1590#note_350977 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453830] Plasma unable to detect installed styles
https://bugs.kde.org/show_bug.cgi?id=453830 --- Comment #1 from Ardith Metz --- Adding to he above: In plasma-frameworks 5.94 copying /usr/share/plasma/desktoptheme/default to ~/.local/share/plasma/desktoptheme/ doesn't make it detectable but if I copy /usr/share/plasma/desktoptheme/default from 5.93 version to ~/.local/share/plasma/desktoptheme/ then it is detected even in 5.94. This may mean the theme format from 5.94 isn't recognized why the old theme format still is. The suspicious change is https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/501 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 453830] New: Plasma unable to detect installed styles
https://bugs.kde.org/show_bug.cgi?id=453830 Bug ID: 453830 Summary: Plasma unable to detect installed styles Product: frameworks-plasma Version: 5.94.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libplasma Assignee: plasma-b...@kde.org Reporter: itgvk...@grr.la CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- SUMMARY *** After update plasma-frameworks package to 5.94 from 5.93 plasma is unable to detect installed styles (system-settings ->Appearance-> Plasma styles doesn't contain styles installed in /usr/share/plasma/desktoptheme path. It still detects styles from ~/.local/share/plasma/desktoptheme/ though. This leads to various visual glitches when no style is used. Downgrading package back to 5.93 fixes the problem (all installed in /usr/share/plasma/desktoptheme styles are detected again) *** STEPS TO REPRODUCE 1. Update plasma-frameworks to 5.94 2. Navigate to System-settings -> Appearance-> Plasma styles OBSERVED RESULT Plasma styles from /usr/share/plasma/desktoptheme aren't detected EXPECTED RESULT Plasma styles from /usr/share/plasma/desktoptheme are detected SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443708] Plasma crash in ShellCorona::createWaitingPanels() after logging on
https://bugs.kde.org/show_bug.cgi?id=443708 --- Comment #18 from Ardith Metz --- @MikeC as for me removing [Compositing] section from .config/kwinrc was enough to fix booting with plasma 5.23 so you may try that. For the record I had following settings in this file: [Compositing] GLColorCorrection=false GLCore=true GLPlatformInterface=egl GLPreferBufferSwap=e GLTextureFilter=1 HiddenPreviews=5 OpenGLIsUnsafe=false UnredirectFullscreen=false WindowsBlockCompositing=true XRenderSmoothScale=false -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 411771] Provide a 32-bit compatibility extension for flatpak runtime
https://bugs.kde.org/show_bug.cgi?id=411771 Ardith Metz changed: What|Removed |Added CC|itgvk...@grr.la | -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 411771] Provide a 32-bit compatibility extension for flatpak runtime
https://bugs.kde.org/show_bug.cgi?id=411771 Ardith Metz changed: What|Removed |Added Resolution|--- |FIXED CC||itgvk...@grr.la Status|REPORTED|RESOLVED --- Comment #5 from Ardith Metz --- This was fixed in https://invent.kde.org/packaging/flatpak-kde-runtime/-/commit/0a8bacd759741cb769e8aa878f8909c1e7b43d53 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431223] Flatpak: Projects plugin does not list files in the Projects-view
https://bugs.kde.org/show_bug.cgi?id=431223 --- Comment #26 from Ardith Metz --- Putting it differently: it's like running debian and complaining it doesn't use packages from fedora :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431223] Flatpak: Projects plugin does not list files in the Projects-view
https://bugs.kde.org/show_bug.cgi?id=431223 --- Comment #25 from Ardith Metz --- Generally flatpak is supposed to be self-contained and distro agnostic. If your system is debian then you can build something using debian tools that will work only on debian while other developer on fedora will work in totally different environ and another user on arch won't have a single binary that matched yours on their system. In flatpak you can build something using flatpak tools that will work everywhere flatpak works - that's the point of flatpak. That means every developer and user will share the same environment instead trying to keep people from 100 different environments on the same page. This is primary flatpak goal and all security et all is only secondary to that. I understand this may be not what you wanted and may not care about but may be worth to learn something about the platform kde releases its software for last couple years :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431223] Flatpak: Projects plugin does not list files in the Projects-view
https://bugs.kde.org/show_bug.cgi?id=431223 Ardith Metz changed: What|Removed |Added CC||itgvk...@grr.la --- Comment #22 from Ardith Metz --- Isn't it possible use kdesrc-build inside flatpak first then use kate in the same environ?? There is also flatpak-spawn command to allows you to execute any command from host: https://manpages.debian.org/experimental/flatpak/flatpak-spawn.1.en.html -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431223] Flatpak: Projects plugin does not list files in the Projects-view
https://bugs.kde.org/show_bug.cgi?id=431223 --- Comment #20 from Ardith Metz --- I wanted to note that there are other IDE tools in flathub like gnome builder or visual studio code and they generally work fine. Definitely using Sdk as runtime is the way to go for such case which give you access to cmake,git,perl,rust,go,clangd, etc. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413578] if fractional display scaling is used, scrolling by dragging the scroll bar makes the icons flicker
https://bugs.kde.org/show_bug.cgi?id=413578 Ardith Metz changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Ardith Metz --- This issue seems fixed in the following setup (I think qt update to 5.14 and rebuild plasma against it was crucial): SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 Dolphin: 19.12.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413578] if fractional display scaling is used, scrolling by dragging the scroll bar makes the icons flicker
https://bugs.kde.org/show_bug.cgi?id=413578 Ardith Metz changed: What|Removed |Added CC|itgvk...@grr.la | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 413578] if fractional display scaling is used, scrolling by dragging the scroll bar makes the icons flicker
https://bugs.kde.org/show_bug.cgi?id=413578 Ardith Metz changed: What|Removed |Added CC||itgvk...@grr.la --- Comment #1 from Ardith Metz --- I can confirm similar issue with the difference that it happens with both mouse wheel scroll and scrollbar. I use 1.5 scaling on Full HD (1980x1080) resolution. I also found similar report on reddit: https://old.reddit.com/r/kde/comments/chi715/flickering_when_scrolling_in_dolphin_kde/ SOFTWARE/OS VERSIONS KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Dolphin: 19.12.0 ADDITIONAL INFORMATION Intel HD Graphics 620 Tested on both intel and modesetting ddx driver. X11 session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 --- Comment #8 from Ardith Metz --- Gnome 3.34 adopted systemd for start/manage session: https://blogs.gnome.org/benzea/2019/10/01/gnome-3-34-is-now-managed-using-systemd/ I hope KDE join it some day. I saw some effort in https://github.com/KDE/plasma-systemd-integration but it stalled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400451] kwin_wayland blocks TMPDIR env variable inheritance in Plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=400451 Ardith Metz changed: What|Removed |Added Component|general |wayland-generic Summary|Plasma wayland session |kwin_wayland blocks TMPDIR |doesn't export provided |env variable inheritance in |TMPDIR env variable |Plasma wayland session Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Product|ksmserver |kwin --- Comment #4 from Ardith Metz --- I've found the cause. 'kwin_ayland' binary is installed with 'CAP_SYS_NICE' file capability[1] which blocks 'TMPDIR' inheritance across the runtime chain. Removing that capability makes 'TMPDIR' correctly exported again. This was introduced in[2] and caused env variables inheritance issue already in[3]. I think the fix should be similar to the above - if TMPDIR var exist then pass it explicitly to child processes [1] https://github.com/KDE/kwin/blob/988ca97c96f11912a856f36daf5f044845044f7b/CMakeLists.txt#L702 [2] https://github.com/KDE/kwin/commit/7c8003f7f6212ccad7de652943f94d501365d30f [3] https://github.com/KDE/kwin/commit/eb69e87288d37fdb13eca32ca807ed8279f912af -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 --- Comment #6 from Ardith Metz --- (In reply to David Edmundson from comment #5) > We absolutely cannot do that as a strict dependency. Then don't and simply assume that system has dbus already started which is true for most if not all distros. The current approach is described as detrimental[1] https://github.com/bus1/dbus-broker/issues/145#issuecomment-398727176 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 --- Comment #4 from Ardith Metz --- (In reply to David Edmundson from comment #3) > That's true only if one has dbus socket activated. Switching plasma session to run as systemd user service would allow to create dependency on dbus.socket service. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 405548] Dark breeze: invalid tooltip/widget colors with compositing enabled
https://bugs.kde.org/show_bug.cgi?id=405548 --- Comment #6 from Ardith Metz --- The fix isn't complete: https://bbs.archlinux.org/viewtopic.php?pid=1837417#p1837417 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 --- Comment #2 from Ardith Metz --- The issue is not about that you should rely on dbus-broker but about that you shouldn't rely on dbus-daemon and be agnostic of whatever dbus implementation is used. In other words prepare for that dbus-run-session won't exist on system anymore. dbus-broker maintainers gave you same ideas what to do but it's also possible to just omit dbus-run-session command and run /usr/bin/startplasmacompositor directly. I assume that at the time "Ubuntu LTS supported dbus-broker for at least two years" the vast majority of distros will already migrate to dbus-broker so unless the goal is to make KDE wayland session an Ubuntu LTS only thing you would better to reconsider this. Fedora 30 is expected in May 2019. No, you don't have to thank me for this heads-up at all. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #20 from Ardith Metz --- (In reply to Sem from comment #19) > Created attachment 118211 [details] > New crash information added by DrKonqi > > kwrite (18.12.0) using Qt 5.11.3 > > - What I was doing when the application crashed: > > Hey, so apparently this still happens sometimes. I'm on Fedora 29 and opened > a tab delimited file. Kwrite continues crashing everytime I point to the > scrolling preview thing. Hopefully this will help in resolving the issue. > This issue should be already solved with system setup as described in: https://bugs.kde.org/show_bug.cgi?id=395369#c18 . You have to wait till your distro updates their packages. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 404439] khelpcenter doesn't find unix man pages
https://bugs.kde.org/show_bug.cgi?id=404439 Ardith Metz changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #4 from Ardith Metz --- (In reply to Luigi Toscano from comment #3) > I will investigate, but can you please check on Arch forums to check if it's > a distribution-specific issue? I don't see relevant changes in kio-man (part > of kio-extras) and khelpcenter. > It ended up being my local issue. Executing "mandb" solved it. Thanks for your time. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 404439] khelpcenter doesn't find unix man pages
https://bugs.kde.org/show_bug.cgi?id=404439 --- Comment #2 from Ardith Metz --- (In reply to Luigi Toscano from comment #1) > Is kio-extras installed? Yes, it is. > (khelpcenter is released as part of a bundle called KDE Applications; > 18.12.2 is the version number of the bundle, not the version of program). I see, however all other apps I checked show the same version as the bundle. Only khelpcenter is different. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 404439] New: khelpcenter doesn't find unix man pages
https://bugs.kde.org/show_bug.cgi?id=404439 Bug ID: 404439 Summary: khelpcenter doesn't find unix man pages Product: khelpcenter Version: 18.12 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- SUMMARY khelpcenter doesn't find any unix man-pages. Only kde related docs are shown. STEPS TO REPRODUCE 1. Open khelpcenter 2. Search for any man page (i.e. passwd) OBSERVED RESULT No search results EXPECTED RESULT Appropriate man pages found SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma: 5.15.0 KDE Frameworks: 5.55.0 Qt: 5.12.1 khelpcenter 18.12.2 (About Help Center shows: "Version 5.7.3", I don't know why) Distro: Archlinux ADDITIONAL INFORMATION Executing: /usr/lib/khc_mansearch.pl --maxcount=10 --words=passwd --method=and shows: passwd: nothing appropriate. I've seen it working in the past. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404333] GDK_SCALE has no effect in plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=404333 Ardith Metz changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- --- Comment #2 from Ardith Metz --- @David Edmundson That means it won't work at all if display scaling in Plasma isn't enabled (set to 1) and due to lack of fractional scaling, display scaling is not usable on most setups. (on my system setting it to 2 makes elements so big that I even have hard time to undo that setting). When using both GDK_SCALE (for upscaling) and GDK_DPI_SCALE (for downscaling) you can achieve fractional scaling effect which is otherwise unreachable. If GDK_SCALE is set in environment then it's value should be used similarly as in x11 session otherwise it's a regression. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404335] New: Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session
https://bugs.kde.org/show_bug.cgi?id=404335 Bug ID: 404335 Summary: Don't rely on dbus-run-session or dbus-launch for starting plasma-wayland session Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: itgvk...@grr.la Target Milestone: 1.0 SUMMARY Currently plasma-wayland session is launched through dbus-run-session like: dbus-run-session /usr/bin/startplasmacompositor The problem with this is that the dbus-broker (https://github.com/bus1/dbus-broker) which is a new, modern, direct replacement for dbus implementation doesn't have equivalent of dbus-run-session command (https://github.com/bus1/dbus-broker/issues/145). Plasma x11 session isn't affected as it doesn't use dbus-run-session command to start itself. When dbus-broker is used on system then starting plasma-wayland through dbus-run-session will start the old dbus daemon which will be disconnected from the former thus connection to dbus services won't work. dbus-broker is already available in various distro repositiories (Arch Linux, Fedora, openSUSE) and there is actual plan to make dbus-broker the default dbus implementation in Fedora (https://fedoraproject.org/wiki/Changes/DbusBrokerAsTheDefaultDbusImplementation) - currently postponed to F30. Other distros will follow sooner or later. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404333] New: GDK_SCALE has no effect in plasma wayland session
https://bugs.kde.org/show_bug.cgi?id=404333 Bug ID: 404333 Summary: GDK_SCALE has no effect in plasma wayland session Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Keywords: wayland Severity: normal Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: itgvk...@grr.la Target Milestone: 1.0 SUMMARY Setting GDK_SCALE env variable has no effect in plasma-wayland session. It woks correctly in x11 session. GDK_DPI_SCALE works in both (but it significantly lowers font quality so it's not a workaround). STEPS TO REPRODUCE 1. Log into plasma-wayland session 2. Install kde-gtk-config package 3. Run "GDK_SCALE=2 gtk3-demo" (notice it's not scaled) 5. Log into plasma-x11 session 6. Install kde-gtk-config package 7. Run "GDK_SCALE=2 gtk3-demo" (notice it's scaled properly) OBSERVED RESULT GDK_SCALE has no effect for gt3 apps in plasma-wayland session EXPECTED RESULT GDK_SCALE has effect for gt3 apps in plasma-wayland session SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma: 5.15.0 KDE Frameworks: 5.55.0 Qt: 5.12.1 Kate/Kwrite 18.12.2 Distro: Archlinux ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 Ardith Metz changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #18 from Ardith Metz --- It seems not longer reproducible on: KDE Plasma: 5.15.0 KDE Frameworks: 5.55.0 Qt: 5.12.1 Kate/Kwrite 18.12.2 Distro: Archlinux -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 --- Comment #11 from Ardith Metz --- I opened new bug about editorconfig/kate interaction: https://bugs.kde.org/show_bug.cgi?id=402896 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402896] New: .editorconfig makes Kate gui settings unapplicable
https://bugs.kde.org/show_bug.cgi?id=402896 Bug ID: 402896 Summary: .editorconfig makes Kate gui settings unapplicable Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- SUMMARY .editorconfig support proposed in https://bugs.kde.org/show_bug.cgi?id=330843 have consequences that kate gui config is un-applicable when .editoconfig file exist and has set options which conflicts with those from Kate. This may be confusing for users as app behavior doesn't match what they see is set in config and not everyone is aware that such thing like .editoconfig may exist and overrides kate settings. This is a follow up from https://bugs.kde.org/show_bug.cgi?id=397956 cat ~/.editorconfig # http://editorconfig.org root = true [*] trim_trailing_whitespace = true STEPS TO REPRODUCE 1. rm ~/.kateconfig 2. rm ~/.config/katerc 3. rm ~/.config/katepartrc 4. rm ~/kate_test 5. echo " " >kate_test 6. kate kate_test 7. Chose from toolbar: "Settings" -> "Open/Save" -> "General" -> "Remove trailing spaces" -> "Never" -> "Apply" -> "Ok" 8. Click "Save" button (notice "Undo button is activated which means changes are done in document) 9. Close kate 10. rm ~/.editorconfig 11. rm ~/.kateconfig 12. rm ~/.config/katerc 13. rm ~/.config/katepartrc 14. rm kate_test 15. echo " " >kate_test 16. kate kate_test 17. Chose from toolbar: "Settings" -> "Open/Save" -> "General" -> "Remove trailing spaces" -> "Never" -> "Apply" -> "Ok" 18. Click "Save" button from toolbar (notice "Undo button isn't activated which means there aren't changes done in document) OBSERVED RESULT Settings in GUI are ignored by kate EXPECTED RESULT Settings in GUI are honored by kate SOFTWARE/OS VERSIONS Kde plasma:5.14.4 Kde frameworks: 5.53.0 Qt: 5.12.0 Kate: 18.12.0 Distro: Arch Linux ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 Ardith Metz changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 --- Comment #8 from Ardith Metz --- Wow, that's a nice finding! The excerpt that I showed in first post: [Document] ... Keep Extra Spaces=true Remove Spaces=0 ... was from ~/.config/katepartrc, not ~/.config/katerc. I misremembered it but I originally posted this couple of months ago :) Anyway my ~/.config/katepartrc matches ~/.config/katerc so that wasn't much relevant. I indeed have .editorconfig (not sure where it comes from) which has a below line: trim_trailing_whitespace = true after changing it to: trim_trailing_whitespace = false the issue reported here goes away. Thank you very much for helping to find this! There are still couple of things which aren't clear for me: 1. What is the difference between ~/.config/katepartrc and ~/.config/katerc, when they're used and why they both exist. 2. Why .editorconfig takes precedence over ~/.config/katepartrc and ~/.config/katerc? It may create confusion as: a) it makes kate gui config inapplicable b) it may be created by some different app than kate thus users like me may be unaware why the kate behavior suddenly changed -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 Ardith Metz changed: What|Removed |Added Version|18.08.0 |unspecified --- Comment #6 from Ardith Metz --- I showed excerpt from ~/.config/katerc (without saying that it's from ~/.config/katerc because I assumed it's obvious at least for kate developers). I also pointed to relevant gui option which will modify ~/.config/katerc. If you want me to go for full nit, then here I am: 1. rm ~/.kateconfig 2. rm ~/.config/katerc 3. rm ~/kate_test 4. echo " " >kate_test 5. kate kate_test 6. Chose from toolbar: "Settings" -> "Open/Save" -> "General" -> "Remove trailing spaces" -> "Never" -> "Apply" -> "Ok" 7. Click "Save" button (notice "Undo button is activated which means changes are done in document) 8. Close kate 9. touch .kateconfig 10. rm ~/.config/katerc 11. rm kate_test 12. echo " " >kate_test 13. kate kate_test 14. Chose from toolbar: "Settings" -> "Open/Save" -> "General" -> "Remove trailing spaces" -> "Never" -> "Apply" -> "Ok" 15. Click "Save" button from toolbar (notice "Undo button isn't activated which means there aren't changes done in document) I hope everything is clear now. Tested on: Kde plasma:5.14.4 Kde frameworks: 5.53.0 Qt: 5.12.0 Kate: 18.12.0 Distro: Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 --- Comment #4 from Ardith Metz --- Which part isn't clear? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 --- Comment #2 from Ardith Metz --- @Lothar did you read my description above? I tested this with "Remove Spaces=0" in ~/.config/katerc . Also with fresh config. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 400451] Plasma wayland session doesn't export provided TMPDIR env variable
https://bugs.kde.org/show_bug.cgi?id=400451 Ardith Metz changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 396767] kdesu doesn't work when "use_pty" sudo option is enabled
https://bugs.kde.org/show_bug.cgi?id=396767 Ardith Metz changed: What|Removed |Added Version|5.48.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 Ardith Metz changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #14 from Ardith Metz --- Still reproducible on: KDE Plasma: 5.14.4 KDE Frameworks: 5.53.0 Qt: 5.12.0 Kate/Kwrite 18.12.0 Distro: Archlinux Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x67463825a080 (LWP 19591))] Thread 3 (Thread 0x67462e72e700 (LWP 19594)): #0 0x67463d31fafc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x67462ed08c24 in ?? () from /usr/lib/dri/i965_dri.so #2 0x67462ed08948 in ?? () from /usr/lib/dri/i965_dri.so #3 0x67463d319a9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x67463e2ceb23 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x67463619d700 (LWP 19592)): #0 0x67463e2c3c21 in poll () from /usr/lib/libc.so.6 #1 0x67463ab04ee0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x67463ab04fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x67463e7fa5c4 in QEventDispatcherGlib::processEvents (this=0x67463b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x67463e7a358c in QEventLoop::exec (this=this@entry=0x67463619cd70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x67463e5e75c9 in QThread::exec (this=this@entry=0x67463eae9080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x67463ea6dba6 in QDBusConnectionManager::run (this=0x67463eae9080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x67463e5e89cc in QThreadPrivate::start (arg=0x67463eae9080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:361 #8 0x67463d319a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x67463e2ceb23 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x67463825a080 (LWP 19591)): [KCrash Handler] #6 0x0933d65ffad0 in ?? () #7 0x67463e7add89 in QMetaObject::cast (this=0x67463f7c3a00 , obj=obj@entry=0x933d65ff830) at kernel/qmetaobject.cpp:368 #8 0x67463e7addc6 in QMetaObject::cast (this=, obj=obj@entry=0x933d65ff830) at kernel/qmetaobject.cpp:357 #9 0x67463f2e47b4 in qobject_cast (object=0x933d65ff830) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:499 #10 QApplicationPrivate::notifyActiveWindowChange (this=, previous=) at kernel/qapplication.cpp:2187 #11 0x67463ece2345 in QGuiApplicationPrivate::processActivatedEvent (e=) at kernel/qguiapplication.cpp:2325 #12 0x67463ece6f1e in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x933d663a8d0) at kernel/qguiapplication.cpp:1858 #13 0x67463ecc075c in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1068 #14 0x674637ec9e71 in userEventSourceDispatch (source=) at qeventdispatcher_glib.cpp:74 #15 0x67463ab033cf in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x67463ab04f89 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0x67463ab04fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0x67463e7fa5a9 in QEventDispatcherGlib::processEvents (this=0x933d4460ee0, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #19 0x67463e7a358c in QEventLoop::exec (this=this@entry=0x7e8db4a68a80, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #20 0x67463e7ab896 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #21 0x0933c9ee53a8 in ?? () #22 0x67463e1f7223 in __libc_start_main () from /usr/lib/libc.so.6 #23 0x0933c9ee6b9e in _start () [Inferior 1 (process 19591) detached] -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 400451] Plasma wayland session doesn't export provided TMPDIR env variable
https://bugs.kde.org/show_bug.cgi?id=400451 --- Comment #3 from Ardith Metz --- (In reply to Martin Flöser from comment #2) > This is unrelated to KWin - KWin does not care about any env directories. It > belongs to startup which could be ksmserver. Thx. I asked on IRC under which component should I open this and they recommended Kwin as a roughly choice. > Overall it's questionable whether we want to support env variable loading at > all in Wayland as this is a security risk (at least KWin should not). I'm not sure what do you mean here. Ignoring /etc/profile.d, .profile, .pam_environment, .config/plasma-workspace/env? How do you setup working session without exporting env variables? How do you set correct LANG, scale dpi? Do you want to make wayland-session unconfigurable? Is the user config part of security threat scenario in wayland but not in X? In this specific case ignoring TMPDIR (which is changed from common shared dir to private user dir) make security worse not better. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400451] New: Plasma wayland session doesn't export provided TMPDIR env variable
https://bugs.kde.org/show_bug.cgi?id=400451 Bug ID: 400451 Summary: Plasma wayland session doesn't export provided TMPDIR env variable Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- SUMMARY Exporting TMPDIR variable in ~/.profile or ~/.config/plasma-workspace/env doesn't work in plasma-wayland session. STEPS TO REPRODUCE 1. echo "export TMPDIR="$HOME/.cache" >~/.config/plasma-workspace/env/tmpdir.sh 2. Log-in into plasma-wayland session. 3. echo $TMPDIR OBSERVED RESULT echo $TMPDIR has no output. $TMPDIR var isn't set. EXPECTED RESULT echo $TMPDIR /home/username/.cache SOFTWARE VERSIONS (available in About System) KDE Plasma Version: 5.14.2 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Tested on Arch Linux. Logging-in through SDDM. Expected result does happen in plasma-x11 session. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #11 from Ardith Metz --- Interestingly the crash happens only when hovering over scrollbar minimap is the first action I do after opening file in kate directly. If I simply click inside the document body or click somewhere in kate toolbar and then hover over scrollbar minimap the crash doesn't happen. It also doesn't happen when I start kate with empty session and open document trough File -> Open. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 Ardith Metz changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REOPENED Ever confirmed|0 |1 --- Comment #10 from Ardith Metz --- Unfortunately it still occurs with: Kde plasma:5.13.5 Kde frameworks: 5.50.0 Qt: 5.11.1 Kate/Kwrite 18.08.1 Distro: Archlinux Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x6aebde5c9800 (LWP 7649))] Thread 3 (Thread 0x6aebd0f42700 (LWP 7653)): #0 0x6aebe4cccafc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x6aebd1512274 in ?? () from /usr/lib/dri/i965_dri.so #2 0x6aebd1511f68 in ?? () from /usr/lib/dri/i965_dri.so #3 0x6aebe4cc6a9d in start_thread () from /usr/lib/libpthread.so.0 #4 0x6aebe63c7a43 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x6aebdaea4700 (LWP 7651)): #0 0x6aebe63bcbb1 in poll () from /usr/lib/libc.so.6 #1 0x6aebe1964ee0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x6aebe1964fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x6aebe68e84c4 in QEventDispatcherGlib::processEvents (this=0x6aebd4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x6aebe6893dac in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x6aebe66dcf59 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x6aebe6b3aba6 in QDBusConnectionManager::run (this=0x6aebe6bb6080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #7 0x6aebe66e7005 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #8 0x6aebe4cc6a9d in start_thread () from /usr/lib/libpthread.so.0 #9 0x6aebe63c7a43 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x6aebde5c9800 (LWP 7649)): [KCrash Handler] #6 0x6aebe689e597 in QMetaObject::cast (this=0x6aebe7858a60 , obj=obj@entry=0x89684864ef0) at kernel/qmetaobject.cpp:366 #7 0x6aebe689e5d6 in QMetaObject::cast (this=, obj=obj@entry=0x89684864ef0) at kernel/qmetaobject.cpp:355 #8 0x6aebe7380814 in qobject_cast (object=0x89684864ef0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:499 #9 QApplicationPrivate::notifyActiveWindowChange (this=, previous=) at kernel/qapplication.cpp:2186 #10 0x6aebe6da7b85 in QGuiApplicationPrivate::processActivatedEvent (e=) at kernel/qguiapplication.cpp:2304 #11 0x6aebe6da7dbe in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x89683dc8850) at kernel/qguiapplication.cpp:1837 #12 0x6aebe6d81a4c in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1032 #13 0x6aebdde795ed in QPAEventDispatcherGlib::processEvents (this=0x896828cd700, flags=...) at qeventdispatcher_glib.cpp:70 #14 0x6aebe6893dac in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #15 0x6aebe689c0a6 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #16 0x089643300072 in ?? () #17 0x6aebe62f0223 in __libc_start_main () from /usr/lib/libc.so.6 #18 0x0896433017ae in _start () -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 397956] New: Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist
https://bugs.kde.org/show_bug.cgi?id=397956 Bug ID: 397956 Summary: Kate unconditionally removes trailing spaces if .kateconfig file doesn't exist Product: kate Version: 18.08.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- I've found that if .kateconfig file doesn't exist in user $HOME, Kate always removes trailing whitespaces on document saving. [Document] ... Keep Extra Spaces=true Remove Spaces=0 ... In "Open/Save" -> "Remove trailing spaces" is set to "never" Clicking on "Save" in Kate toolbar clear all trailing spaces in document making it irreversibly damaged as there is no chance to undo changes without saving document. After merely touching an empty ".kateconfig" file in top $HOME dir or the dir where files are edited, everything is working normal, i.e. Kate keeps whitespaces if config is set to "never" and clears them if config is set to "In entire Document". I tested this with fresh kate config. Steps to reproduce: 1. touch abc 2. echo " " >abc 3. kate abc 4. Chose "Open/Save" -> "Remove trailing spaces" -> "never" -> "Apply" -> "Ok" 5. Click "Save" button (notice "Undo button is activated which means changes are done in document) 6. Exit kate 7. touch .kateconfig 8. rm abc && touch abc && echo " " >abc 9. Click "Save" button (notice "Undo button isn't activated which means there aren't changes done in document) Kde plasma:5.13 Kde frameworks: 5.49 Qt: 5.11.1 Distro: Archlinux -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #9 from Ardith Metz --- Yes, I'll wait for release and check. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 396767] New: kdesu doesn't work when "use_pty" sudo option is enabled
https://bugs.kde.org/show_bug.cgi?id=396767 Bug ID: 396767 Summary: kdesu doesn't work when "use_pty" sudo option is enabled Product: frameworks-kdesu Version: 5.48.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- "use_pty" is sudo option which enhance its security[0] and is supposed to be enabled in future sudo release[1]. You can enable it by adding below toy sudoers config: Defaults use_pty [0] http://www.openwall.com/lists/oss-security/2018/06/12/2 [1] http://www.openwall.com/lists/oss-security/2018/06/12/4 Unfortunately after enabling it kdesu stops working. There is following message in comsole: $ QT_LOGGING_RULES= kdesu -d -c echo [ /build/kdesu/src/kdesu-5.48.0/src/stubprocess.cpp : 219 ] Unknown request: "ok" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #5 from Ardith Metz --- Hi Kåre Särs, I installed QT with debug support and got the below. I hope it will be helpful. Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x6ec8e7cfd800 (LWP 24739))] Thread 3 (Thread 0x6ec8c21b5700 (LWP 24742)): #0 0x6ec8dea48ffc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x6ec8c2f91124 in ?? () from /usr/lib/dri/i965_dri.so #2 0x6ec8c2f90e18 in ?? () from /usr/lib/dri/i965_dri.so #3 0x6ec8dea43075 in start_thread () from /usr/lib/libpthread.so.0 #4 0x6ec8e263953f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x6ec8cff50700 (LWP 24740)): #0 0x6ec8e2d3e78c in QMutex::lock (this=this@entry=0xa14de25f160) at /usr/include/c++/8.1.1/bits/atomic_base.h:742 #1 0x6ec8e2f4cfd1 in QMutexLocker::QMutexLocker (m=0xa14de25f160, this=) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:206 #2 QThreadData::canWaitLocked (this=0xa14de25f130) at ../../include/QtCore/5.11.1/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:254 #3 postEventSourcePrepare (s=0x6ec8c8004fd0, timeout=0x6ec8cff4fb94) at kernel/qeventdispatcher_glib.cpp:259 #4 0x6ec8da30aa49 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #5 0x6ec8da30b44e in ?? () from /usr/lib/libglib-2.0.so.0 #6 0x6ec8da30b63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #7 0x6ec8e2f4d0c4 in QEventDispatcherGlib::processEvents (this=0x6ec8c8000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #8 0x6ec8e2ef89bc in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #9 0x6ec8e2d41b09 in QThread::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #10 0x6ec8e339d086 in QDBusConnectionManager::run (this=0x6ec8e3617080 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178 #11 0x6ec8e2d4bbb5 in QThreadPrivate::start(void*) () at thread/qthread_unix.cpp:367 #12 0x6ec8dea43075 in start_thread () from /usr/lib/libpthread.so.0 #13 0x6ec8e263953f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x6ec8e7cfd800 (LWP 24739)): [KCrash Handler] #6 0x6ec8e2f031a7 in QMetaObject::cast (this=0x6ec8e4ab0a60 , obj=obj@entry=0xa14def773c0) at kernel/qmetaobject.cpp:366 #7 0x6ec8e2f031e6 in QMetaObject::cast (this=, obj=obj@entry=0xa14def773c0) at kernel/qmetaobject.cpp:355 #8 0x6ec8e43d9504 in qobject_cast (object=0xa14def773c0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:499 #9 QApplicationPrivate::notifyActiveWindowChange (this=, previous=) at kernel/qapplication.cpp:2186 #10 0x6ec8e3c02d35 in QGuiApplicationPrivate::processActivatedEvent (e=) at kernel/qguiapplication.cpp:2304 #11 0x6ec8e3c02f6e in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0xa14def7fda0) at kernel/qguiapplication.cpp:1837 #12 0x6ec8e3bdcbfc in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:1032 #13 0x6ec8d57be5ed in QPAEventDispatcherGlib::processEvents (this=0xa14de22bb70, flags=...) at qeventdispatcher_glib.cpp:70 #14 0x6ec8e2ef89bc in QEventLoop::exec(QFlags) () at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #15 0x6ec8e2f00cb6 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #16 0x0a14ca57d6bd in ?? () #17 0x6ec8e256406b in __libc_start_main () from /usr/lib/libc.so.6 #18 0x0a14ca57eeba in _start () -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 Ardith Metz changed: What|Removed |Added Component|general |general Assignee|plasma-b...@kde.org |kwrite-bugs-n...@kde.org Product|kwayland-integration|kate -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #3 from Ardith Metz --- The temporary workaround is to force to use xcb backend on wayland with: QT_QPA_PLATFORM=xcb kate -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 --- Comment #10 from Ardith Metz --- This issue was caused by new meson build system with xorg. It's fixed by https://lists.x.org/archives/xorg-devel/2018-June/057142.html . You can still consider if kwin should pass '-nolisten tcp' argument as a precaution, similar to what display managers do. -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #2 from Ardith Metz --- It doesn't happen in kate from flatpak so it can be related to QT version (flatpak uses 5.9.5) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 --- Comment #9 from Ardith Metz --- (In reply to David Edmundson from comment #8) > I do not get the impression upstream points to us after Olivier analyses > what's happening. > > It's a weird quirk of them putting -listen with the wayland socket which > implicitly disables default listeners that you've apparently added when > compiling your X. I didn't compile my X. I use official Archlinux package. There isn't any listening option enabled during compilation[1]. The fact is when I start Xserver without '-nolisten tcp' it's listening on network sockets so it's the default behavior. I test this with with xorg 1.20 (the build details are in linked Archlinux site). This may be related to using new meson build system which doesn't even have 'listen' option[2]. > > Interestingly I do put -nolisten tcp in SDDM, so I'm more obliged to add it > here. You didn't put it there. It's in default SDDM configuration[3]. It's in default GDM configuration[4]. It's in default lightdm configuration[5]. Regardless of what the default xorg behavior is, virtually everyone is explicitly disabling listening on tcp sockets just to be on the safe side. The point of this issue is that kwin_xwayland should follow the common practices. [1]https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/xorg-server#n80 [2] https://cgit.freedesktop.org/xorg/xserver/tree/meson_options.txt [3] https://github.com/sddm/sddm/blob/815ee034303d51ce3850a533c2023eaf5eb09cae/data/man/sddm.conf.rst.in#L103 [4] https://github.com/GNOME/gdm/blob/f7bda8dac60eb556709fba085248df5395d09a56/data/gdm.schemas.in.in#L73 [5] https://github.com/CanonicalLtd/lightdm/blob/fe28fb17147611a99c03bf593f10f1fb73d80c59/data/lightdm.conf#L99 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 --- Comment #7 from Ardith Metz --- (In reply to David Edmundson from comment #6) > >It's worth noting that adding -nolisten options from the compositor doesn't > >work, because if that option isn't available (e.g. '-nolisten tcp6' when > >you've built without IPv6 support), failure to not listen will be a hard > >error. > > From Daniel Stone. > > So we're definitely not doing that. > > I will monitor that upstream thread. Please do not reopen it here. Option '-nolisten tcp6' doesn't even exist, it should be '-nolisten inet6' but I'm not advising to use it. Option '-nolisten tcp' will work always - it disables both ipv4/ipv6 and doesn't fail hard when ipv6 isn't available (see 'man xserver' for valid options). Actually kwin_wayland hard fails currently when ipv6 isn't available (just boot with 'ipv6.disable=1' kernel arg to test) so we have exactly opposite situation of what you quoted[1]. To conclude we have both: potential security issue and crash and you closing them both and pointing to upstream while upstream points to you while there is no sign they will address it in any way. [1] https://bugs.kde.org/show_bug.cgi?id=394431 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 Ardith Metz changed: What|Removed |Added Ever confirmed|0 |1 Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #5 from Ardith Metz --- (In reply to Martin Flöser from comment #1) > Please report to X developers. They should use sane and secure defaults. This is the upstream answer in related case[1]: "However, if the Wayland compositor enables IP, and you think that is a mistake, then you should report that to the Wayland compositor project in question." Moreover I'm able to override standalone xserver/xwayland defaults but I'm not able to override kwin/xwayland defaults. That's why I think this issue belongs to kde devs. At least if they care about security. Currently kwin starts xwayland as: /usr/bin/Xwayland -displayfd xx --rootless --wm xx To fix this issue it should start it as: /usr/bin/Xwayland -nolisten tcp -displayfd xx --rootless --wm xx [1] https://bugs.freedesktop.org/show_bug.cgi?id=106573#c2 BTW: I have reports from people who can reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 --- Comment #4 from Ardith Metz --- I can reproduce it always with: Starting: 1. kwin_wayland --xwayland 2. sudo ss -tunwrap | column -t |grep -i xwayland System: Distro: Archlinux Linux: 4.17.1 Plasma: 5.13 Frameworks: 5.47 QT: 5.11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 --- Comment #3 from Ardith Metz --- @David Edmundson what's is your setup? Mine: Archlinux; Plasma 5.13; sddm -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 395419] New: Xwayland listens on port 6000+n on all network interfaces
https://bugs.kde.org/show_bug.cgi?id=395419 Bug ID: 395419 Summary: Xwayland listens on port 6000+n on all network interfaces Product: kwin Version: 5.13.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: platform-x11-nested Assignee: kwin-bugs-n...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- In plasma wayland session Xwayland is started with default settings which means it listens on tcp/tcp6 on all network interfaces on port 6000+n (n=display number). Listening on network without user consent is harmful for security. Especially as it's not possible to disable this in config. In X11 session all display managers start xserver with '-nolisten tcp' option which disables above behavior. Considering above I think current Xwayland config is decreasing security in comparison to standalone X11 session and should be adjusted. BTW: This behavior can create specific issues for some users: https://bugs.kde.org/show_bug.cgi?id=394431 Steps to reproduce: 1. Login to plasma-wayland session 2. sudo ss -tunwrap | column -t -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 395369] kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 --- Comment #1 from Ardith Metz --- Actually it's reproducible with kwrite too: Application: KWrite (kwrite), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x6696fdeb0800 (LWP 8))] Thread 3 (Thread 0x6696d8e2e700 (LWP 11121)): #0 0x6696f4f21ffc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x6696d9c0a0a4 in ?? () from /usr/lib/dri/i965_dri.so #2 0x6696d9c09d98 in ?? () from /usr/lib/dri/i965_dri.so #3 0x6696f4f1c075 in start_thread () from /usr/lib/libpthread.so.0 #4 0x6696f9f5553f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x6696e6305700 (LWP 9)): #0 0x6696f9f46934 in read () from /usr/lib/libc.so.6 #1 0x6696f3194ed1 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x6696f314eff8 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x6696f314f4c6 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x6696f314f63e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x6696fa866e64 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x6696fa81285c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x6696fa65bac9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x6696f5c75976 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x6696fa665b95 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x6696f4f1c075 in start_thread () from /usr/lib/libpthread.so.0 #11 0x6696f9f5553f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x6696fdeb0800 (LWP 8)): [KCrash Handler] #6 0x0001 in ?? () #7 0x6696fa81d049 in QMetaObject::cast(QObject const*) const () from /usr/lib/libQt5Core.so.5 #8 0x6696fb589384 in QApplicationPrivate::notifyActiveWindowChange(QWindow*) () from /usr/lib/libQt5Widgets.so.5 #9 0x6696fadbd3d5 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /usr/lib/libQt5Gui.so.5 #10 0x6696fadbd60e in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #11 0x6696fad94a5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #12 0x6696ebb70f7d in ?? () from /usr/lib/libQt5WaylandClient.so.5 #13 0x6696fa81285c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #14 0x6696fa81ab56 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #15 0x026de6f575b9 in main () -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 395369] New: kate segmentation fault when hovering over scrollbar minimap under wayland session
https://bugs.kde.org/show_bug.cgi?id=395369 Bug ID: 395369 Summary: kate segmentation fault when hovering over scrollbar minimap under wayland session Product: kwayland-integration Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: itgvk...@grr.la Target Milestone: --- Under plasma wayland session kate always crashes when I hover mouse over scrollbar minimap. This doesn't happen with kwrite. Kde plasma:5.13 Kde frameworks: 5.47 Qt: 5.11 Distro: Archlinux It also happened with older versions of the above (at least for couple months). Below is backtrace from drkonqi (I know on Archlinux it's worthless but it's all I have): Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x65e771a14680 (LWP 8533))] Thread 3 (Thread 0x65e74c134700 (LWP 8536)): #0 0x65e767de5ffc in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x65e74cf100a4 in ?? () from /usr/lib/dri/i965_dri.so #2 0x65e74cf0fd98 in ?? () from /usr/lib/dri/i965_dri.so #3 0x65e767de0075 in start_thread () from /usr/lib/libpthread.so.0 #4 0x65e76c35653f in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x65e759e65700 (LWP 8534)): #0 0x65e76c34bea9 in poll () from /usr/lib/libc.so.6 #1 0x65e765dc2523 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x65e765dc263e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x65e76cc67e64 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x65e76cc1385c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x65e76ca5cac9 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x65e76d0b7976 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x65e76ca66b95 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x65e767de0075 in start_thread () from /usr/lib/libpthread.so.0 #9 0x65e76c35653f in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x65e771a14680 (LWP 8533)): [KCrash Handler] #6 0x65e76cc1e047 in QMetaObject::cast(QObject const*) const () from /usr/lib/libQt5Core.so.5 #7 0x65e76e0eb384 in QApplicationPrivate::notifyActiveWindowChange(QWindow*) () from /usr/lib/libQt5Widgets.so.5 #8 0x65e76d91f3d5 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /usr/lib/libQt5Gui.so.5 #9 0x65e76d91f60e in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5 #10 0x65e76d8f6a5c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #11 0x65e75f6d0f7d in ?? () from /usr/lib/libQt5WaylandClient.so.5 #12 0x65e76cc1385c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #13 0x65e76cc1bb56 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #14 0x0443b2c9a6bd in ?? () #15 0x65e76c28106b in __libc_start_main () from /usr/lib/libc.so.6 #16 0x0443b2c9beba in _start () -- You are receiving this mail because: You are watching all bug changes.
