[frameworks-kio] [Bug 293888] Poor performance with mounted network locations
https://bugs.kde.org/show_bug.cgi?id=293888 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com --- Comment #43 from Andrew Udvare --- I recently updated to Plasma 6 and this is one of the issues I encountered. I have some CIFS mounts. In Plasma 5 there was no slow down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #31 from Andrew Udvare --- I rebuilt Kwin 6.0.90 with normal flags. Running in Wayland. Cannot reproduce. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 --- Comment #11 from Andrew Udvare --- The patch here https://invent.kde.org/plasma/breeze/-/commit/9b93fb968ed6a2817cee367aab5cfef7003b4073.patch works with KDE 5.27 and seems to partially fix the issue. I tested after logging out and logging back in. For maximisation, the window loses all outline even with the new setting Outline intensity set to Maximum. The only case not handled by the patch is snapping where perhaps the alternate screen should have the outline removed. This can be worked around by setting Outline intensity to Off. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 --- Comment #7 from Andrew Udvare --- macOS does not have the feature. iTerm does. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 378872] yakuake-3.0.4 window is larger in wayland than on X11
https://bugs.kde.org/show_bug.cgi?id=378872 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470992] New: Panel height is significantly larger in Wayland vs X
https://bugs.kde.org/show_bug.cgi?id=470992 Bug ID: 470992 Summary: Panel height is significantly larger in Wayland vs X Classification: Plasma Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: audv...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. In X, set scale to 150%. Log out and log back in. 2. Set up a panel on the top. Set its height to 50. 2. Log out and log back in with Wayland. OBSERVED RESULT Panel size is much larger than in X. EXPECTED RESULT Panel size should be exactly the same. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux 6.3.7 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I do not think a migration to the correct Wayland size (about 34) is acceptable. The numbers in X and Wayland should be the same. Sometimes with the way things are we still need to go back to X and do not expect significant changes (preferably none). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449682] hp-systray does not restart on logging back in
https://bugs.kde.org/show_bug.cgi?id=449682 --- Comment #3 from Andrew Udvare --- (In reply to Nate Graham from comment #2) > Thanks. If it works on the other machine, then the code is doing the right > thing, and the issue could be caused by: > - a different, older, or broken version of hp-systray on the failing machine > - a different, older, or broken version of ksmserver on the failing machine > - some local override or configuration that breaks it on the failing machine How can I fully reset the relevant settings for the KDE part of this without making a new profile? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449682] hp-systray does not restart on logging back in
https://bugs.kde.org/show_bug.cgi?id=449682 --- Comment #1 from Andrew Udvare --- Since writing this bug I installed Plasma on another machine from scratch and hp-systray restarts properly on that machine. Still does not restart on the machine I originally reported this bug on. I do not want to migrate to a new profile. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 313210] Ability to open a new tab with a specific profile
https://bugs.kde.org/show_bug.cgi?id=313210 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #29 from Andrew Udvare --- I tried every single -mno-avx512* option until I had all of them set. When all were set the issue was gone. So really, *any* AVX512 feature in use will cause this bug. I also tried with Clang and got the same results with all sorts of flag combinations. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 449540] Open Tab in New Profile with Yakuake
https://bugs.kde.org/show_bug.cgi?id=449540
Andrew Udvare changed:
What|Removed |Added
CC||audv...@gmail.com
--- Comment #1 from Andrew Udvare ---
One odd workaround is to use qdbus, where you set the Konsole defaultProfile to
the one you want, create a new session and then set it back:
ynsp() {
local -r original_profile=$(qdbus org.kde.yakuake /Windows/1 defaultProfile)
qdbus org.kde.yakuake /Windows/1 setDefaultProfile "$1"
qdbus org.kde.yakuake /yakuake/sessions addSession
qdbus org.kde.yakuake /Windows/1 setDefaultProfile "$original_profile"
}
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #27 from Andrew Udvare --- The UBSAN/ASAN output is probably not related. -fno-tree-vectorize does not resolve the issue with -march=native (or x86-64-v4) which is suprising. For the last test these were the flags: CXXFLAGS="-O2 -ggdb -march=native -mtune=native -pipe -fno-tree-vectorize -fsanitize=undefined" LDFLAGS="-Wl,-O1 -Wl,--as-needed -fsanitize=undefined" Expanded native: CXXFLAGS="-O2 -ggdb -march=rocketlake -mabm --param=l1-cache-line-size=64 --param=l1-cache-size=48 --param=l2-cache-size=16384 -pipe -fno-tree-vectorize -fsanitize=undefined" LDFLAGS="-Wl,-O1 -Wl,--as-needed -fsanitize=undefined" rocketlake can be replaced with x86-64-v4 and the results will be the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #26 from Andrew Udvare --- (In reply to Andreas Sturmlechner from comment #24) > This is the moment where you provide upstream with more information about > your toolchain and optimisation flags. More details: # gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/12/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-12.2.1_p20230121-r1/work/gcc-12-20230121/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/12 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/12/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/12 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/12/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/12/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/12/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --enable-nls --without-included-gettext --disable-libunwind-exceptions --enable-checking=release --with-bugurl=https://bugs.gentoo.org/ --with-pkgversion='Gentoo Hardened 12.2.1_p20230121-r1 p10' --with-gcc-major-version-only --enable-esp --enable-libstdcxx-time --disable-libstdcxx-pch --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-multilib --with-multilib-list=m32,m64 --disable-fixed-point --enable-targets=all --enable-libgomp --disable-libssp --disable-libada --disable-cet --disable-systemtap --disable-valgrind-annotations --disable-vtable-verify --disable-libvtv --with-zstd --enable-lto --without-isl --enable-default-pie --enable-default-ssp --with-build-config=bootstrap-lto Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.2.1 20230121 (Gentoo Hardened 12.2.1_p20230121-r1 p10) Building with -march=x86-64-v4 is what makes this break. -fsanitize=undefined gives the following on startup: $ kwin_x11 --replace /var/tmp/portage/kde-plasma/kwin-5.27.1/work/kwin-5.27.1/src/main_x11.cpp:113:46: runtime error: member call on address 0x7faff8006310 which does not point to an object of type 'KWinSelectionOwner' 0x7faff8006310: note: object has invalid vptr 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 25 00 00 00 ^~~ invalid vptr OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 OpenGL version string: 3.1.0 NVIDIA 525.89.02 OpenGL shading language version string: 1.40 NVIDIA via Cg compiler Driver: NVIDIA Driver version: 525.89.2 GPU class: Unknown OpenGL version: 3.1 GLSL version: 1.40 X server version: 1.21.1 Linux kernel version: 6.2 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no Kwin runs and triggering the behaviour does not make further output. -fsanitize=address gives the following and Kwin aborts: $ kwin_x11 --replace = ==20622==ERROR: AddressSanitizer: odr-violation (0x7fc35434f780): [1] size=48 'staticMetaObject' /var/tmp/portage/kde-plasma/kwin-5.27.1/work/kwin-5.27.1_build/src/kwin_autogen/7HEHEGDA3T/moc_common.cpp:119:38 [2] size=48 'staticMetaObject' /var/tmp/portage/kde-plasma/kwin-5.27.1/work/kwin-5.27.1_build/src/libkwineffects/kwineffects_autogen/include/moc_kwinglobals.cpp:108:38 These globals were registered at these points: [1]: #0 0x7fc35463a628 in __asan_register_globals /var/tmp/portage/sys-devel/gcc-12.2.1_p20230121-r1/work/gcc-12-20230121/libsanitizer/asan/asan_globals.cpp:341 #1 0x7fc354d8ec0d in call_init /var/tmp/portage/sys-libs/glibc-2.36-r7/work/glibc-2.36/elf/dl-init.c:70 #2 0x7fc354d8ec0d in call_init /var/tmp/portage/sys-libs/glibc-2.36-r7/work/glibc-2.36/elf/dl-init.c:26 [2]: #0 0x7fc35463a628 in __asan_register_globals /var/tmp/portage/sys-devel/gcc-12.2.1_p20230121-r1/work/gcc-12-20230121/libsanitizer/asan/asan_globals.cpp:341 #1 0x7fc354d8ec0d in call_init /var/tmp/portage/sys-libs/glibc-2.36-r7/work/glibc-2.36/elf/dl-init.c:70 #2 0x7fc354d8ec0d in call_init /var/tmp/portage/sys-libs/glibc-2.36-r7/work/glibc-2.36/elf/dl-init.c:26 ==20622==HINT: if you don't care about these errors you may set ASAN_OPTIONS=detect_odr_violation=0 SUMMARY: AddressSanitizer: odr-violation: global 'staticMetaObject' at /var/tmp/portage/kde-plasma/kwin-5.27.1/work/kwin-5.27.1_build/src/kwin_autoge
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #23 from Andrew Udvare --- This bug is actually caused by using --march=native to GCC. Maybe it's specific to my CPU or how my GCC is built. Regardless, it would seem the code path in question is sensitive to CPU optimisations. I can compile a local Git clone with -march=native and get the same behaviour. When -march=native is gone, the problem is gone. Can the section of code dealing with this be marked to avoid optimisation? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #22 from Andrew Udvare --- Built Kwin from source (tag v5.27.0) and ran with --replace. The issue does not appear in that build. The Gentoo build environment must be to blame. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #21 from Andrew Udvare --- I tried to reproduce this in the developer version of KDE Neon in VirtualBox and was not able to, even after matching up my settings as much as possible. I also tried building without -ftree-vectorize but this did not fix it either. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #20 from Andrew Udvare --- (In reply to Vlad Zahorodnii from comment #18) > Can you check whether the issue is reproducible in 5.27? Still happening in 5.27. I rebooted after fully updating my system to ensure there are no conflicting old still running libs. Only non-maximised windows snapped to the left side of the screen are affected. This happens for others but most notably Chrome and Telegram. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #17 from Andrew Udvare --- Worst offender is Chrome. I cannot reliably trigger this issue with Dolphin, pavucontrol, etc. When compositing is enabled, after snapping Chrome wants to use the shadow of the window instead of the real edge of the window. The shadow should be ignored in that scenario. Chrome renders shadow on its own (or just black border with compositing disabled). This has nothing to do with the KDE theme shadow setting. It is not affected by my current Chrome settings. Chrome run with configuration reset has the same issue. A new user account exhibits the same issue. Let me know if there is more information I can provide. Settings -> Window Decorations: Theme: Breeze Window border size: Tiny -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #16 from Andrew Udvare --- It seems only *some* Gtk+ apps get affected. I was able to reproduce the same issue with dconf-editor but not Filezilla or GIMP. It seems some windows may have a particular way of drawing that triggers the bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #15 from Andrew Udvare --- I am not positive the lines are relevant to this bug because they appear after resize when the window is not snapped to the left edge of the screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #14 from Andrew Udvare --- (In reply to Vlad Zahorodnii from comment #13) > > These lines mostly came when resizing Chrome on the right side while it was > > snapped to the left side of the screen, with compositing enabled. > > Do you see them after you've finished resizing chrome? These lines appear in the log immediately after finishing the resize of Chrome (on mouse button up). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #12 from Andrew Udvare --- The bug seems to be that the theme shadow is being used to figure out where to have the right-side (E) resize grabber trigger instead of the window edge. This seems to only happen when snapping the window to the left side of the screen (W snap). 1. Set Window Decoration to Breeze 2. In the Breeze theme settings (pencil icon), go to Shadows and set Size to Very Large and Strength to 100%. 3. Set 'Window border size' to 'No Borders' or 'Theme's default (No Borders)'. 4. For a KDE or Qt app window not snapped to the left side, note where the E resize grabber shows. 5. Drag that window to the left and let it snap. 6. Now note where the E resize grabber shows. The way I might have confirmed this is by setting the shadow strength to 100% and 'Very Large' (Breeze theme). Then I was able to clearly see where the grabber shows. The issue is 'fixed' for KDE/Qt windows by setting Window border size to Normal or bigger, but the theme's default is 'No Borders' and I'd prefer to have that. The setting change does not fix Gtk+ apps or Chrome. Worst for all of these is that the content is virtually about 30px to the right so interacting with the window does not work as expected at all. After unsnapping, the window goes fully back to normal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #11 from Andrew Udvare --- Created attachment 155349 --> https://bugs.kde.org/attachment.cgi?id=155349&action=edit Kwin debug log kwin_core: Failed to create window pixmap for window 0x10a (mismatched geometry) These lines mostly came when resizing Chrome on the right side while it was snapped to the left side of the screen, with compositing enabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #10 from Andrew Udvare --- Adding to my previous comment: This does not fully fix the window. It fixes Chrome it seems (somewhat), but everything else still thinks it's wider than it is after snapping to the left even without compositing. With Chrome, the issue is the shadow during compositing. When snapped to the left, the left shadow is gone so the handle on the right for resizing is off to right by 27px. This used to work in the past. With compositing off, Chrome forces the window to have a black border where the shadow would've been. So the resize handle goes to the correct place (at edge of browser window, not the shadow/border). The only commit I saw that looked interesting was one regarding Kwin switching to all floating point for metrics. But it is not easy for me to test a reversion of that change in its current state. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #8 from Andrew Udvare --- (In reply to Vlad Zahorodnii from comment #7) > What if you toggle compositing? Does the window "fix" itself? Yes. The window moves to the right a few pixels, to the correct position. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #6 from Andrew Udvare --- Any thoughts on where I can look to possilbly fix the bug? Kwin source? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #5 from Andrew Udvare --- I made a new profile to test against just to make sure it's not a configuration issue. I was able to reproduce the issue in X11 as with my current profile. I was not able to reproduce the issue in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #4 from Andrew Udvare --- (In reply to Nate Graham from comment #3) > Cannot reproduce with Chromium (in either CSD or SSD mode). > > Do you have any 3rd-party KWin scripts or effects active? No KWin scripts enabled. Effects: Accessibility: Zoom Appearance: Background contrast Desaturate Unresponsive Applications Fading Popups Full Screen Login Logout Maximise Morphing popups Screen Edge Sliding popups Squash Show Desktop Animation: Window Aperture Virtual Desktop Switching Animation: Fade Desktop Window Management: Overview Present Windows Window Open/Close Animation: Scale -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 --- Comment #2 from Andrew Udvare --- Recently updated and I am still getting the bug. Two demonstration videos: https://youtu.be/Qup9ifJSCnc https://youtu.be/vwKTbOtpEkI Note where the mouse cursor is vs the window edges after the window is snapped. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Windows snapped to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 Andrew Udvare changed: What|Removed |Added Summary|Snapped windows to screen |Windows snapped to screen |edges display correctly but |edges display correctly but |content is shifted to the |content is shifted to the |right virtually |right virtually -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] Snapped windows to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 Andrew Udvare changed: What|Removed |Added Version|unspecified |5.26.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460572] New: Snapped windows to screen edges display correctly but content is shifted to the right virtually
https://bugs.kde.org/show_bug.cgi?id=460572 Bug ID: 460572 Summary: Snapped windows to screen edges display correctly but content is shifted to the right virtually Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: audv...@gmail.com Target Milestone: --- Created attachment 152921 --> https://bugs.kde.org/attachment.cgi?id=152921&action=edit Screenshot showing behaviour SUMMARY When I let a window snap into place along the screen sides, the contents are assumed to be about 5 pixels to the right. STEPS TO REPRODUCE 1. Drag a window that is re-sizeable and let it snap to the left side. 2. Resize the window once on the right side. 2. Attempt to resize the window again with the right side. OBSERVED RESULT Nothing happens. EXPECTED RESULT The horizontal resize cursor should display in the correct area. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo KDE Plasma Version: 5.26.0 on X11 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION If I move the mouse slightly to the right about 5 pixels, I can see the resize cursor and resize. All of the contents of the window are affected, not just the sides. The mouse coordinates become off by about 5 px, perhaps vertically as well in some cases but I have not yet seen that. As soon as I move the window away from being snapped, everything works as normal. This bug only affects snapped windows. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 181437] Detailed view: for better clarity, rolling over an element should highlight the whole line, not just the name of the element
https://bugs.kde.org/show_bug.cgi?id=181437 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com --- Comment #20 from Andrew Udvare --- I like and dislike this change. Can we get an option for this? 'Highlight entire row' in View Modes -> Details? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 449682] New: hp-systray does not restart on logging back in
https://bugs.kde.org/show_bug.cgi?id=449682 Bug ID: 449682 Summary: hp-systray does not restart on logging back in Product: ksmserver Version: 5.23.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: audv...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Run hp-systray from HPLIP 2. Log out allowing session to save 3. Log back in OBSERVED RESULT Upon logging back in, hp-systray does not start. The following message is logged: hp-systray[9295]: hp-systray[9295]: error: option -s not recognized EXPECTED RESULT hp-systray should start and should not log any errors. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.16.5/5.23.5 (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.23.5 Qt Version: 5.15.2 ADDITIONAL INFORMATION $ fgrep hp-systray ~/.config/ksmserverrc program1=/usr/bin/hp-systray restartCommand1=/usr/bin/hp-systray,-session,1014cd2d4cd00016439893250094520009_1643989599_866247,-name,hp-systray I am not sure on the format of this file but it appears -session is being passed to hp-systray and does not get ignored. It results in hp-systray failing to start. $ hp-systray -session 101 HP Linux Imaging and Printing System (ver. 3.21.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. System Tray monitors the HP device status and Displays Usage: hp-systray [MODE] [OPTIONS] [MODE] Run in graphical UI mode: -u or --gui (Default) [OPTIONS] Use Qt5:--qt5 (Default) Set the logging level: -l or --logging= : none, info*, error, warn, debug (*default) Run in debug mode: -g (same as option: -ldebug) This help information: -h or --help Startup even if no hplip-x or --force-startup CUPS queues are present: error: option -s not recognized I have tried editing the file to remove all mentions of hp-systray and this did not help. -- 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 --- Comment #2 from Andrew Udvare --- Honestly I can't believe the 'solution' to this. This is Nvidia's fault. Their driver is sending a message to dbus to a service they removed a while ago. And it's sending it 27 times per second, about every 2 frames. Any app that calls GL stuff will be affected and that includes kwin. For those interested in a 'fix' for now: https://forums.developer.nvidia.com/t/bug-nvidia-v495-29-05-driver-spamming-dbus-enabled-applications-with-invalid-messages/192892/9 You may need to use a different user than 'dbus'. On Gentoo systemd it's messagebus. Once I started this service, the spamming stops. -- 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 Andrew Udvare changed: What|Removed |Added Version|unspecified |5.23.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 444634] New: dbus-daemon spamming about full message queue from kwin_x11 a few hours after startup
https://bugs.kde.org/show_bug.cgi?id=444634 Bug ID: 444634 Summary: dbus-daemon spamming about full message queue from kwin_x11 a few hours after startup Product: kwin Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: audv...@gmail.com Target Milestone: --- SUMMARY A few hours after logging in (~6 hours for this boot), I start seeing this message repeating many times per second in journal: dbus-daemon[2006]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.38" (uid=1000 pid=2526 comm="/usr/bin/kwin_x11 ") Overall, this does not slow down my system, but this is very strange and blocks me from normally using journalctl. STEPS TO REPRODUCE 1. Restart system 2. Log in to Plasma (X11) 3. Use as normal 4. After a few hours, observe journalctl -f OBSERVED RESULT dbus-daemon is spamming with 'destination has a full message queue' and the comm =/usr/bin/kwin_x11 every time. EXPECTED RESULT Should not see above message, or at least should not see it being repeated many times per second. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.14.15 / 5.23.2 (available in About System) KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This was also happening on 5.23.0. I am using the Nvidia proprietary driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 --- Comment #14 from Andrew Udvare --- Is anyone here getting dbus-daemon spam in the log? Oct 29 17:57:50 limelight dbus-daemon[2006]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.38" (uid=1000 pid=2526 comm="/usr/bin/kwin_x11 ") It's not exactly causing a leak as I saw in that video (and I also use the Nvidia driver). But obviously it's very annoying as I have to filter dbus-daemon out when I try to check my log. Restarting fixes the issue temporarily. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443990] Kwin memory leak
https://bugs.kde.org/show_bug.cgi?id=443990 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com --- Comment #8 from Andrew Udvare --- Are you getting endless messages in DBus? Maybe related: Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") Oct 27 14:25:06 limelight dbus-daemon[2019]: [system] Rejected: destination has a full message queue, 0 matched rules; type="error", sender="(unset)" ((bus)) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.ServiceUnknown" requested_reply="1" destination=":1.39" (uid=1000 pid=2627 comm="/usr/bin/kwin_x11 ") -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 431703] Ark cannot open some iso's
https://bugs.kde.org/show_bug.cgi?id=431703 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com --- Comment #4 from Andrew Udvare --- Isn't the issue that Ark cannot view UDF based ISOs? That is the issue I have. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 290349] [wish] Add support to save results to eliminate re-scanning each time
https://bugs.kde.org/show_bug.cgi?id=290349 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442629] Pixel MTP device does not appear in Disks & Devices
https://bugs.kde.org/show_bug.cgi?id=442629 --- Comment #5 from Andrew Udvare --- Honestly I think this is a USB-C cable issue. Sometimes the cable works, other times it doesn't. If I use a USB-C to 3.x cable, it always works. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442629] Pixel MTP device does not appear in Disks & Devices
https://bugs.kde.org/show_bug.cgi?id=442629 --- Comment #2 from Andrew Udvare --- It's an issue that seems to be intermittent. If this happens again, what kind of information can I attach for debugging? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442629] New: Pixel MTP device does not appear in Disks & Devices
https://bugs.kde.org/show_bug.cgi?id=442629 Bug ID: 442629 Summary: Pixel MTP device does not appear in Disks & Devices Product: plasmashell Version: git-stable-Plasma/5.22 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: audv...@gmail.com Target Milestone: 1.0 SUMMARY My Pixel 2 XL shows up in Disks & Devices after accessing it from the Places view in Dolphin. It used to appear automatically after plugging in. This is a high-speed (USB 2) device. My Pixel 5 does not show up in Disks & Devices in any case. I am plugging it in via a Thunderbolt bridged connector just in case this makes a difference. This allows the device to use SuperSpeed without going through a USB-A connector. Browsing from Dolphin works fine. I think Pixel devices or any MTP device should be appearing under Removable Devices, but both show up in the 'Devices' section in the Places view. Sep 18 00:48:23 limelight kernel: pcieport :00:01.1: PME: Spurious native interrupt! Sep 18 00:48:25 limelight kernel: usb 4-2: new SuperSpeed USB device number 18 using xhci_hcd Sep 18 00:48:25 limelight kernel: usb 4-2: New USB device found, idVendor=18d1, idProduct=4ee1, bcdDevice= 4.40 Sep 18 00:48:25 limelight kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 18 00:48:25 limelight kernel: usb 4-2: Product: Pixel 5 Sep 18 00:48:25 limelight kernel: usb 4-2: Manufacturer: Google Sep 18 00:48:25 limelight kernel: usb 4-2: SerialNumber: ... STEPS TO REPRODUCE 1. Have a Plasma Panel configured to show a System Tray widget with Disks & Devices 2. Plug in an MTP device OBSERVED RESULT Disks & Devices does not show a new device. EXPECTED RESULT Disks & Devices should show the new device. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 5.14.5 , X11 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434175] Move to wastebin functionality is so slow that is unusable when it already has a lot of stuff in it
https://bugs.kde.org/show_bug.cgi?id=434175 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 440176] New: Add option to inhibit notifications
https://bugs.kde.org/show_bug.cgi?id=440176 Bug ID: 440176 Summary: Add option to inhibit notifications Product: kde-cli-tools Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: audv...@gmail.com Target Milestone: --- SUMMARY Please add an option such as --notifications to inhibit notifications. Could be done via org.freedesktop.Notifications /org/freedesktop/Notifications Inhibit method. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 439312] SimulateUserActivity doesn't unlock the screen, even when unlocking without password is enabled
https://bugs.kde.org/show_bug.cgi?id=439312 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 414776] Rendering glitch when moving in an zoomed PNG with Alphachannel (RGBA)
https://bugs.kde.org/show_bug.cgi?id=414776 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com --- Comment #11 from Andrew Udvare --- I have this issue with any kind of image. I'm on 150% scale with Nvidia drivers. This happens when I move the image with the hand cursor. It is less likely to happen when using the widget on the bottom right. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 427352] New: Folders view flickers continuously
https://bugs.kde.org/show_bug.cgi?id=427352 Bug ID: 427352 Summary: Folders view flickers continuously Product: dolphin Version: 20.08.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: audv...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 132127 --> https://bugs.kde.org/attachment.cgi?id=132127&action=edit Video demonstrating issue. Watch carefully the folder panel on left side for flickering arrows. SUMMARY The folders panel flickers its arrows very quickly, repeatedly on certain directories, usually ones that do not have a sub-directory. STEPS TO REPRODUCE 1. Launch Dolphin. 2. Enable Folders Panel. 3. Click around folders panel and see flickering of arrows. OBSERVED RESULT Flickers arrows, causing distraction. EXPECTED RESULT Should not flicker arrows so much. I assume this is while trying to check if a directory exists in the path. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.8.13 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION This was not happening in a prior version. My main filesystems are ext4 mounted with defaults. mount output shows this to mean: rw,relatime I have seen this happen with the /run path which is tmpfs. I do have 'File Search' enabled, with file content scanning enabled, but not hidden files. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420487] Feature request: lock window geometry
https://bugs.kde.org/show_bug.cgi?id=420487 Andrew Udvare changed: What|Removed |Added Summary|Feature request: lock |Feature request: lock |window placement|window geometry -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420487] Feature request: lock window geometry
https://bugs.kde.org/show_bug.cgi?id=420487 --- Comment #1 from Andrew Udvare --- To answer my last question, yes. I made a Kwin script to implement this feature. https://github.com/Tatsh/kwin-lock-window-placement/blob/master/contents/code/main.js -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420487] New: Feature request: lock window placement
https://bugs.kde.org/show_bug.cgi?id=420487 Bug ID: 420487 Summary: Feature request: lock window placement Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: audv...@gmail.com Target Milestone: --- SUMMARY I often want to lock a window so I cannot accidentally move/resize it especially if it has a grabber somewhere besides the title bar such as the bottom right corner. Setting up a rule for this in settings makes the rule basically permanent. It is not easy to add and remove rules as needed, nor is it quick. I want to be able to enable/disable this quickly, such as in the context menu in the title bar, under More Actions, if there was an option: Lock size/placement This would set the window to be not moveable and not resizeable. PS I've not done much KDE development especially not with Kwin but I wouldn't mind attempting to put something together for this. Also, can this be achieved with a Kwin script? -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 420294] New: Chrome drops Qt scaling environment variables
https://bugs.kde.org/show_bug.cgi?id=420294 Bug ID: 420294 Summary: Chrome drops Qt scaling environment variables Product: plasma-browser-integration Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: audv...@gmail.com Target Milestone: --- SUMMARY This is related to https://bugs.kde.org/show_bug.cgi?id=415421 When I run a KDE application such as Ark via Chrome (by clicking on the file in the download manager), it shows up with the incorrect scale because it does not have the environment variables that would normally be set: QT_AUTO_SCREEN_SCALE_FACTOR=0 QT_SCREEN_SCALE_FACTORS=DVI-I-0=1.5;DVI-I-1=1.5;HDMI-0=1.5;DP-0=1.5;DP-1=1.5;DP-2=1.5;DP-3=1.5;DP-4=1.5;DP-5=1.5; Chrome/Chromium now runs with a minimum environment which causes applications to lose environment variables set by Plasma or in ~/.xprofile or similar. However since it seems to use xdg-open, I can edit the .desktop file for an app and add environment variables, but this is very inconvenient. Even adding `export QT_AUTO_SCREEN_SCALE_FACTOR=0` to .xprofile (and logging in again) does not fix this. STEPS TO REPRODUCE 1. Open Chrome, download a zip file. 2. Click on the file in the download bar or download manager to open it with Ark. OBSERVED RESULT Ark opens with incorrect scale. EXPECTED RESULT Ark should respect the QT_AUTO_SCREEN_SCALE_FACTOR and QT_SCREEN_SCALE_FACTORS values when opened from anywhere. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo / 5.18.4 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #32 from Andrew Udvare --- (In reply to Fabian Vogt from comment #31) > Git commit ea66bff2af8466f2bb5acafcc43ac8f79b1f447f by Fabian Vogt. > Committed on 21/01/2020 at 10:56. > Pushed by fvogt into branch 'Plasma/5.18'. > > Also disable automatic scaling on Qt >= 5.14 > > Summary: > Applications which set `Qt::AA_EnableHighDpiScaling` use the DPI of the > monitor the window is on to calculate an additional scaling factor. > Plasma sets `QT_SCREEN_SCALE_FACTORS` in the environment for manual > specification of per-monitor scale, which combined with the automatic > scaling may result in double scaling. > To disable the automatic scaling, `QT_AUTO_SCREEN_SCALE_FACTOR=0` has to be > set, even on Qt 5.14. > > As a side effect, this works around QTBUG-80967 as well. > > Test Plan: On X11, with a >144dpi monitor and a scaling factor of 2 set > manually, scaling was doubled previously. Now it works as expected. > > Reviewers: #plasma, apol, davidedmundson, fvogt > > Reviewed By: #plasma, davidedmundson, fvogt > > Subscribers: acooligan, fvogt, asturmlechner, dfaure, davidedmundson, > anthonyfieroni, plasma-devel > > Tags: #plasma > > Differential Revision: https://phabricator.kde.org/D26185 > > M +0-2startkde/startplasma.cpp > > https://commits.kde.org/plasma-workspace/ > ea66bff2af8466f2bb5acafcc43ac8f79b1f447f That fix resolves most of the issue but Chrome seems to now run with a reduced environment. /proc//environ shows a very minimal environment. As a result, when Chrome launches Ark (click on item in the download bar) I get the same issue. I modified the .desktop file to force the QT_AUTO_SCREEN_SCALE_FACTOR=0 value and it works. I wouldn't want to have to create custom .desktop files just for Chrome. Should I file another ticket? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #30 from Andrew Udvare --- (In reply to Postix from comment #28) > (In reply to Fabian Vogt from comment #27) > > However, setting QT_AUTO_SCREEN_SCALE_FACTOR=0 seems to have universal > > success. > > > > > Thanks, I can confirm that! I had to revert the `Exec=env QT_FONT_DPI=96` > changes in the desktop file and added `QT_AUTO_SCREEN_SCALE_FACTOR=0` to > /etc/environment. > After rebooting everything went back to normal. > > (Putting `export QT_AUTO_SCREEN_SCALE_FACTOR=0` into the .bashrc and logging > out and back in again was not successfull for unknown reasons.) I put export QT_AUTO_SCREEN_SCALE_FACTOR=0 in my ~/.xprofile and everything works like it should. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #29 from Andrew Udvare --- The goal should be to have no extra environment variables set to solve this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #20 from Andrew Udvare --- Also one workaround for now that must be applied to the broken apps specifically is to use the QT_FONT_DPI environment variable. Setting this to 96 in the .desktop file for Kate/Dolphin/etc makes things seem normal again, and icons are the correct size. $ fgrep Exec ~/.local/share/applications/org.kde.kate.desktop Exec=env QT_FONT_DPI=96 kate -b %U -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #19 from Andrew Udvare --- I updated and rebooted. This issue remains. I tested Ark, VirtualBox and Qt Designer. All 3 show large fonts. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #18 from Andrew Udvare --- (In reply to David Edmundson from comment #17) > As you're on gentoo, can you be sure to re-emerge plasma-workspace after you > upgraded Qt to rule that out? Currently doing a system upgrade which update my system to 5.17.5. I will reboot after to make sure I'm running all newly built libs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #12 from Andrew Udvare --- I currently have the broken apps forced to use 96 DPI but of course this means the toolbar icons, etc are very small on a 4K display. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #7 from Andrew Udvare --- Rebooted with Breeze theme (and all other appearance settings set to Breeze) and still got the same issue. Just for reference, this is a KF5 5.65.0 installation. Plasma-desktop and related is at 5.17.4. Qt is at 5.14.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #6 from Andrew Udvare --- I rebooted and still get the same issue. About to try switching to Breeze widget style. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #4 from Andrew Udvare --- Created attachment 124839 --> https://bugs.kde.org/attachment.cgi?id=124839&action=edit VirtualBox screenshot Found a non-KDE app affected: VirtualBox -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #3 from Andrew Udvare --- Created attachment 124635 --> https://bugs.kde.org/attachment.cgi?id=124635&action=edit New user screenshot This is from a new user account with minimal customisation, 1.5x scale enabled, 144 DPI force enabled (because that is what System Settings does automatically). The left is Kate and the right KPatience. KPatience correctly shows its menus while Kate remains too large. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #2 from Andrew Udvare --- Created attachment 124634 --> https://bugs.kde.org/attachment.cgi?id=124634&action=edit Konsole displaying incorrectly Konsole claims this is point size 9 but it definitely is not when compared to my browser or LibreOffice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 --- Comment #1 from Andrew Udvare --- Created attachment 124633 --> https://bugs.kde.org/attachment.cgi?id=124633&action=edit System Settings rendering correctly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 415421] New: [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole
https://bugs.kde.org/show_bug.cgi?id=415421 Bug ID: 415421 Summary: [hidpi] Inconsistent font size with certain apps such as Kate, KWrite, Konsole Product: plasmashell Version: master Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: audv...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 124632 --> https://bugs.kde.org/attachment.cgi?id=124632&action=edit Dolphin vs a Gtk+ app rendering SUMMARY Certain apps are rendering font sizes too large in comparison to others. This applies to: * Dolphin * Kate * KWrite * Konsole The font sizes are about 25% larger than expected. System Settings and just about every other app I have including Chromium run at the correct size. I am attaching screenshots for reference. The first is a Gtk+ app vs Dolphin, where the Gtk+ app is showing the correct scale. The second is System Settings which is rendering correctly with the current settings. STEPS TO REPRODUCE 1. Set scale factor to 1.5 2. Log out and log back in 3. Run Kate OBSERVED RESULT Kate is running with correct size icons (I think) but a 25% larger font than expected. EXPECTED RESULT Kate should have normal size fonts as other apps (like System Settings) do. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Gentoo, 5.17.4 (available in About System) KDE Plasma Version: 5.17.4 KDE Frameworks Version: 5.65.0 Qt Version: 5.14.0 ADDITIONAL INFORMATION Recently updated to latest versions available of Qt, Plasma, etc on Gentoo Portage. This was not happening in a prior version. I do not have forced font DPI enabled nor a DPI setting in ~/.Xresources. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404886] New: Crash on checking notifications
https://bugs.kde.org/show_bug.cgi?id=404886 Bug ID: 404886 Summary: Crash on checking notifications Product: plasmashell Version: 5.15.1 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: audv...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.15.1) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.55.0 Operating System: Linux 4.20.12-gentoo-limelight x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: Clicked on notification widget number (incicating 4 notifications available). Plasma crashed and now the notifications are gone. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa242ad7640 (LWP 1825))] Thread 7 (Thread 0x7fa21e21d700 (LWP 1970)): #0 __GI___libc_read (fd=54, buf=buf@entry=0x7fa21e21cb20, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fa245b1bea0 in read (__nbytes=16, __buf=0x7fa21e21cb20, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7fa218003bb0) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gwakeup.c:210 #3 0x7fa245ad62bf in g_main_context_check (context=context@entry=0x7fa21bf0, max_priority=2147483647, fds=fds@entry=0x7fa210004dd0, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3698 #4 0x7fa245ad6790 in g_main_context_iterate (context=context@entry=0x7fa21bf0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3917 #5 0x7fa245ad690c in g_main_context_iteration (context=0x7fa21bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3981 #6 0x7fa247b1ab7b in QEventDispatcherGlib::processEvents (this=0x7fa21b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7fa247acb2b3 in QEventLoop::exec (this=this@entry=0x7fa21e21cd40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7fa2479446a6 in QThread::exec (this=this@entry=0x5638c87224a0) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7fa21ee8f8c5 in QQuickXmlQueryEngine::run (this=0x5638c87224a0) at qqmlxmllistmodel.cpp:323 #10 0x7fa24794d5ea in QThreadPrivate::start (arg=0x5638c87224a0) at thread/qthread_unix.cpp:367 #11 0x7fa2469d53e3 in start_thread (arg=) at pthread_create.c:486 #12 0x7fa2475ba13f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fa21ea5d700 (LWP 1968)): #0 g_mutex_unlock (mutex=0x7fa218000bf0) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gthread-posix.c:1355 #1 0x7fa245ad6916 in g_main_context_iteration (context=0x7fa218000bf0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3982 #2 0x7fa247b1ab7b in QEventDispatcherGlib::processEvents (this=0x7fa218000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #3 0x7fa247acb2b3 in QEventLoop::exec (this=this@entry=0x7fa21ea5cd60, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #4 0x7fa2479446a6 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #5 0x7fa24794d5ea in QThreadPrivate::start (arg=0x5638c739ae80) at thread/qthread_unix.cpp:367 #6 0x7fa2469d53e3 in start_thread (arg=) at pthread_create.c:486 #7 0x7fa2475ba13f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fa2388ff700 (LWP 1958)): #0 __GI___libc_read (fd=41, buf=buf@entry=0x7fa2388feb00, nbytes=nbytes@entry=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7fa245b1bea0 in read (__nbytes=16, __buf=0x7fa2388feb00, __fd=) at /usr/include/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7fa228003720) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gwakeup.c:210 #3 0x7fa245ad62bf in g_main_context_check (context=context@entry=0x7fa22800e5d0, max_priority=2147483647, fds=fds@entry=0x7fa228013080, n_fds=n_fds@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3698 #4 0x7fa245ad6790 in g_main_context_iterate (context=context@entry=0x7fa22800e5d0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /var/tmp/portage/dev-libs/glib-2.58.3/work/glib-2.58.3/glib/gmain.c:3917 #5 0x7fa245ad690c in g_main_context_iteration (context=0x7fa22800e5d0, may_block=may_block@entry=1) at /var/tmp/portage/dev-libs/glib-2.58.3/wo
[Craft] [Bug 403920] Icon theme "breeze" not found
https://bugs.kde.org/show_bug.cgi?id=403920 --- Comment #4 from Andrew Udvare --- (In reply to Hannah von Reth from comment #3) > craft --print-files breeze-icons > Craft : /home/hannah/CraftRoot > Version : master > ABI : linux-64-gcc > Download directory : /home/hannah/CraftRoot/download > = > = > == > *** Handling package: kde/frameworks/tier1/breeze-icons, action: print-files > *** > *** Action: print-files for kde/frameworks/tier1/breeze-icons *** > share/icons/breeze-dark/actions/12/object-fill.svg > $ craft --print-files breeze-icons Craft : /Users/tatsh/.craft Version : master ABI : macos-64-clang Download directory : /Users/tatsh/.craft/download == *** Handling package: kde/frameworks/tier1/breeze-icons, action: print-files *** *** Action: print-files for kde/frameworks/tier1/breeze-icons *** share/icons/breeze-dark/breeze-icons-dark.rcc share/icons/breeze/breeze-icons.rcc share/icontheme.rcc -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403920] Icon theme "breeze" not found
https://bugs.kde.org/show_bug.cgi?id=403920 --- Comment #2 from Andrew Udvare --- This is my output: $ craft --search breeze.* Craft : /Users/tatsh/.craft Version : master ABI : macos-64-clang Download directory : /Users/tatsh/.craft/download Craft was unable to find breeze.*, similar packages are: kde/plasma/breeze Name: breeze BlueprintPath: /Users/tatsh/.craft/etc/blueprints/locations/craft-blueprints-kde/kde/plasma/breeze/breeze.py Homepage: https://www.kde.org/ Description: The KDE Community is a free software community dedicated to creating an open and user-friendly computing experience, offering an advanced graphical desktop, a wide variety of applications for communication, work, education and entertainment and a platform to easily build new applications upon. We have a strong focus on finding innovative solutions to old and new problems, creating a vibrant atmosphere open for experimentation. Tags: Options: args=, branch=(str), buildStatic=(bool), buildTests=(bool), buildType=RelWithDebInfo, ignored=(bool), patchLevel=(int), version=(str) Latest version: 5.14.5 Installed versions: 5.14.5 Installed revision: None Available versions: master, 5.10.5, 5.11.5, 5.12.7, 5.13.5, 5.14.4, 5.14.5 kde/frameworks/tier1/breeze-icons Name: breeze-icons BlueprintPath: /Users/tatsh/.craft/etc/blueprints/locations/craft-blueprints-kde/kde/frameworks/tier1/breeze-icons/breeze-icons.py Homepage: https://www.kde.org/ Description: Breeze icon theme. Tags: Options: args=, branch=(str), buildStatic=(bool), buildTests=(bool), buildType=RelWithDebInfo, ignored=(bool), patchLevel=(int), useBreezeDark=False, useIconResource=True, version=(str) Latest version: 5.54.0 Installed versions: 5.54.0 Installed revision: None Available versions: master, 5.42.0, 5.43.0, 5.44.0, 5.45.0, 5.46.0, 5.47.0, 5.48.0, 5.49.0, 5.50.0, 5.51.0, 5.52.0, 5.53.0, 5.54.0 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403920] New: Icon theme "breeze" not found
https://bugs.kde.org/show_bug.cgi?id=403920 Bug ID: 403920 Summary: Icon theme "breeze" not found Product: Craft Version: unspecified Platform: Other OS: OS X Status: REPORTED Severity: normal Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: audv...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY All apps are missing icons. Running the app directly via the command line gives the output in the title of this bug. STEPS TO REPRODUCE 1. craft kate 2. Run Kate.app OBSERVED RESULT No icons are displayed. EXPECTED RESULT Breeze icon theme should be found, as it is installed: $ craft --search breeze Craft : /Users/tatsh/.craft Version : master ABI : macos-64-clang Download directory : /Users/tatsh/.craft/download Package breeze found: kde/plasma/breeze Name: breeze BlueprintPath: /Users/tatsh/.craft/etc/blueprints/locations/craft-blueprints-kde/kde/plasma/breeze/breeze.py Homepage: https://www.kde.org/ Description: The KDE Community is a free software community dedicated to creating an open and user-friendly computing experience, offering an advanced graphical desktop, a wide variety of applications for communication, work, education and entertainment and a platform to easily build new applications upon. We have a strong focus on finding innovative solutions to old and new problems, creating a vibrant atmosphere open for experimentation. Tags: Options: args=, branch=(str), buildStatic=(bool), buildTests=(bool), buildType=RelWithDebInfo, ignored=(bool), patchLevel=(int), version=(str) Latest version: 5.14.5 Installed versions: 5.14.5 SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Icon theme seems to be installed: $ tree -L 2 ~/.craft/share/icons/ /Users/tatsh/.craft/share/icons/ ├── Breeze_Snow │ ├── cursors │ └── index.theme ├── breeze │ └── breeze-icons.rcc ├── breeze-dark │ └── breeze-icons-dark.rcc ├── breeze_cursors │ ├── cursors │ └── index.theme └── hicolor ├── 128x128 ├── 16x16 ├── 22x22 ├── 32x32 ├── 48x48 ├── 64x64 └── scalable 14 directories, 4 files -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403057] Cannot build packages with Craft: cmake failed with exit code 9
https://bugs.kde.org/show_bug.cgi?id=403057 --- Comment #4 from Andrew Udvare --- We're missing a blueprint for kactivities-stats, and systemsettings does not pull in khtml as it should. -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403057] Cannot build packages with Craft: cmake failed with exit code 9
https://bugs.kde.org/show_bug.cgi?id=403057 --- Comment #2 from Andrew Udvare --- I had to do `craft -i --update` and it seems like the CMake binary now works. But I was unable to install systemsettings due to missing packages, it seems: -- Could NOT find KF5ActivitiesStats: found neither KF5ActivitiesStatsConfig.cmake nor kf5activitiesstats-config.cmake -- Could NOT find KF5KHtml: found neither KF5KHtmlConfig.cmake nor kf5khtml-config.cmake CMake Error at /Users/tatsh/.local/share/dev-utils/cmake/CMake.app/Contents/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find KF5 (missing: ActivitiesStats) (found suitable version "5.52.0", minimum required is "5.50.0") Call Stack (most recent call first): /Users/tatsh/.local/share/dev-utils/cmake/CMake.app/Contents/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE) /Users/tatsh/.local/share/share/ECM/find-modules/FindKF5.cmake:110 (find_package_handle_standard_args) CMakeLists.txt:28 (find_package) -- Configuring incomplete, errors occurred! See also "/Users/tatsh/.local/share/build/kde/plasma/systemsettings/work/RelWithDebInfo-5.14.4/CMakeFiles/CMakeOutput.log". See also "/Users/tatsh/.local/share/build/kde/plasma/systemsettings/work/RelWithDebInfo-5.14.4/CMakeFiles/CMakeError.log". executing command: "/Users/tatsh/.local/share/dev-utils/bin/ninja" ninja: error: loading 'build.ninja': No such file or directory Action: compile for kde/plasma/systemsettings:5.14.4 FAILED *** Craft all failed: kde/plasma/systemsettings after 3 seconds *** fatal error: package kde/plasma/systemsettings all failed -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 403057] New: Cannot build packages with Craft: cmake failed with exit code 9
https://bugs.kde.org/show_bug.cgi?id=403057 Bug ID: 403057 Summary: Cannot build packages with Craft: cmake failed with exit code 9 Product: Craft Version: unspecified Platform: Other OS: OS X Status: REPORTED Severity: normal Priority: NOR Component: Blueprints Assignee: vonr...@kde.org Reporter: audv...@gmail.com CC: kde-wind...@kde.org Target Milestone: --- SUMMARY Getting no output from CMake. It seems CMake that is packaged through Craft is broken as even invoking it as `cmake --help` shows no output. STEPS TO REPRODUCE 1. Install Craft 2. Source craft environment 3. craft systemsettings OBSERVED RESULT 2019-01-09 22:52:51,851 DEBUG Command "/Users/tatsh/.local/share/dev-utils/bin/cmake" -G "Ninja" -DBUILD_TESTING=ON -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_INSTALL_PREFIX="/Users/tatsh/.local/share" -DCMAKE_PREFIX_PATH="/Users/tatsh/.local/share" -DCMAKE_BUILD_TYPE=RelWithDebInfo -DKDE_INSTALL_BUNDLEDIR="/Users/tatsh/.local/share/Applications/KDE" -DAPPLE_SUPPRESS_X11_WARNING=ON -DKDE_INSTALL_USE_QT_SYS_PATHS=ON "/Users/tatsh/.local/share/build/kde/plasma/systemsettings/work/systemsettings-5.14.4" failed with exit code 9 2019-01-09 22:52:51,852 WARNING Action: compile for kde/plasma/systemsettings:5.14.4 FAILED 2019-01-09 22:52:51,852 INFO *** Craft all failed: kde/plasma/systemsettings after 1 second *** 2019-01-09 22:52:51,856 DEBUG Craft was unable to locate: snoretoast, in None 2019-01-09 22:52:51,856 ERROR fatal error: package kde/plasma/systemsettings all failed EXPECTED RESULT The package should build. SOFTWARE/OS VERSIONS Windows: MacOS: macOS 10.14.2 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 338489] multiple xcb_put_image calls required to upload "big" images -> client splitting of requests is required
https://bugs.kde.org/show_bug.cgi?id=338489 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 378523] KFontRequester: Fonts are saved with face name preventing bold/italic to work
https://bugs.kde.org/show_bug.cgi?id=378523 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Andrew Udvare changed: What|Removed |Added CC|audv...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #82 from Andrew Udvare --- (In reply to Stefan from comment #81) > Created attachment 99000 [details] > attachment-22055-0.html > > As I see it, the problem is the whole locale system which assumes that all > your preferences are based on a single region. This problem is beyond KDE, > and affects the entire UNIX ecosystem. The problem with the 'UNIX ecosystem' is beyond the scope of KDE. Yes it would be nice if there were better ways to universally solve the problem at that level and this would fix this issue and make every single application conform, not just ones that use Qt's library for this. OS X uses POSIX locales just as Linux does. But just as KDE 4 kept things separate so does OS X. LC_ALL=C generally has no effect on an OS X application, but it does have an effect on grep/etc as would be expected. Although OS X was developed a very long time, I think Apple saw it as necessary to keep these systems separate. It is nice to have a universal standard for all, but the POSIX locale system is too inflexible for this as it is. It has no built-in customisation, only forced conformity. But even so, sometimes applications come with their own way to override locale, even ls. GNU ls has the --time-style argument, like so: --time-style="+%Y-%m-%d %H:%M:%S". -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Andrew Udvare changed: What|Removed |Added CC||audv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
