[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.
[gwenview] [Bug 467833] New: gwenview crashed after trying to delete multiple images
https://bugs.kde.org/show_bug.cgi?id=467833 Bug ID: 467833 Summary: gwenview crashed after trying to delete multiple images Classification: Applications Product: gwenview Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: travn...@gmail.com Target Milestone: --- Application: gwenview (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.7-200.fc37.x86_64+debug x86_64 Windowing System: X11 Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: I did ctrl+a to select several images. Then pressed del (maybe shift/ctrl+del, not sure) and it crashed immediately. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 0x7f8c866ed6e8 in Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib64/libgwenviewlib.so.5 #5 0x7f8c866f85b5 in Gwenview::LoadingDocumentImpl::slotMetaInfoLoaded() () from /lib64/libgwenviewlib.so.5 #6 0x7f8c848d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #7 0x7f8c846f21b5 in QFutureWatcherBase::event(QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7f8c855aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7f8c8489d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f8c848a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #11 0x7f8c848eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #12 0x7f8c82718c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #13 0x7f8c8276f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #14 0x7f8c82715f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7f8c848ee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f8c8489bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f8c848a4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55ebed1b4afb in main () [Inferior 1 (process 11095) detached] The reporter indicates this bug may be a duplicate of or related to bug 458876. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467326] New: sddm-kcm should also synchronize CursorSize
https://bugs.kde.org/show_bug.cgi?id=467326 Bug ID: 467326 Summary: sddm-kcm should also synchronize CursorSize Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: andrewammerl...@gentoo.org CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- SUMMARY I was trying out the native wayland support in SDDM git and found that the cursor looked way to big. The problem was easily fixable by setting 'CursorSize=24' in sddm.conf.d. However, this should probably be synchronized as well when the user presses the "Apply Plasma Settings" button. STEPS TO REPRODUCE 1. Upgrade to sddm-git 2. Switch sddm to wayland with 'DisplayServer=wayland' 3. Synchronize settings from plasma OBSERVED RESULT Currently synchronizing the Plasma settings to sddm gives me this kde_settings.conf: [Autologin] Relogin=false Session= User= [General] HaltCommand=systemctl shutdown Numlock=on RebootCommand=systemctl reboot [Theme] Current=breeze CursorTheme=breeze_cursors Font=Noto Sans [GOOG],10,-1,5,50,0,0,0,0,0,Regular [Users] MaximumUid=65000 MinimumUid=1000 [X11] ServerArguments=-dpi 0 EXPECTED RESULT The CursorSize setting is also synchronized automatically, leading to a uniform cursor size when logging in and loading a Plasma session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 6.3.0_rc1 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467219] Effect stack: drag and drop reordering crash
https://bugs.kde.org/show_bug.cgi?id=467219 --- Comment #1 from Andrew --- To be clear, drag and drop does not crash if the order is unchanged. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467219] New: Effect stack: drag and drop reordering crash
https://bugs.kde.org/show_bug.cgi?id=467219 Bug ID: 467219 Summary: Effect stack: drag and drop reordering crash Classification: Applications Product: kdenlive Version: 22.12.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: awchamp...@gmail.com Target Milestone: --- SUMMARY Kdenlive crashes when trying to reorder effects with drag and drop STEPS TO REPRODUCE 1. Add clip to timeline 2. Add multiple effects to clip effect stack 3. Drag any effect to change the stack order 4. Drop effect in new order OBSERVED RESULT Dragging appears as expected, with line indicating where the effect will be placed in the stack. Kdenlive crashes if the order of effects is changed. The intended change cannot be recovered when the project is reopened. EXPECTED RESULT A list of two effects would be reversed. Three or more is also easily understood. SOFTWARE/OS VERSIONS macOS: 12.6.3 ADDITIONAL INFORMATION -- 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.
[plasma-systemmonitor] [Bug 457237] Changing priority does not work
https://bugs.kde.org/show_bug.cgi?id=457237 Andrew Meyer changed: What|Removed |Added CC||amey...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466387] New: Intermittent segfault when plugging in PS5 or PS4 controller
https://bugs.kde.org/show_bug.cgi?id=466387 Bug ID: 466387 Summary: Intermittent segfault when plugging in PS5 or PS4 controller Classification: Frameworks and Libraries Product: frameworks-kded Version: 5.103.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: accounts+...@chiller3.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When I plug in my PS5 or PS4 controllers via USB, kded will sometimes segfault. I have not changed any settings other than disabling the controller's touchpad from KDE's system settings. It happens pretty frequently, but not always. There seems to be a higher chance of a crash after resuming from suspend, but I don't have any hard data on that. STEPS TO REPRODUCE 1. Plug in PS5 or PS4 controller via USB OBSERVED RESULT kded segfaults (which triggers side effects related to that, like night color breaking) EXPECTED RESULT kded shouldn't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 (x11 session) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION journalctl messages starting from plugging in the controller to the crash: Feb 24 21:38:02 cxl-desktop-1 kernel: usb 1-9: new high-speed USB device number 22 using xhci_hcd Feb 24 21:38:02 cxl-desktop-1 kernel: usb 1-9: New USB device found, idVendor=054c, idProduct=0ce6, bcdDevice= 1.00 Feb 24 21:38:02 cxl-desktop-1 kernel: usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Feb 24 21:38:02 cxl-desktop-1 kernel: usb 1-9: Product: Wireless Controller Feb 24 21:38:02 cxl-desktop-1 kernel: usb 1-9: Manufacturer: Sony Interactive Entertainment Feb 24 21:38:02 cxl-desktop-1 kernel: input: Sony Interactive Entertainment Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-9/1-9:1.3/0003:054C:0CE6.0022/input/input47 Feb 24 21:38:02 cxl-desktop-1 kernel: hid-generic 0003:054C:0CE6.0022: input,hidraw15: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-:00:14.0-9/input3 Feb 24 21:38:02 cxl-desktop-1 mtp-probe[275156]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-9" Feb 24 21:38:02 cxl-desktop-1 mtp-probe[275156]: bus: 1, device: 22 was not an MTP device Feb 24 21:38:02 cxl-desktop-1 kernel: playstation 0003:054C:0CE6.0022: hidraw15: USB HID v1.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-:00:14.0-9/input3 Feb 24 21:38:02 cxl-desktop-1 kernel: input: Sony Interactive Entertainment Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-9/1-9:1.3/0003:054C:0CE6.0022/input/input48 Feb 24 21:38:02 cxl-desktop-1 kernel: input: Sony Interactive Entertainment Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-9/1-9:1.3/0003:054C:0CE6.0022/input/input49 Feb 24 21:38:02 cxl-desktop-1 kernel: input: Sony Interactive Entertainment Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-9/1-9:1.3/0003:054C:0CE6.0022/input/input50 Feb 24 21:38:02 cxl-desktop-1 kernel: playstation 0003:054C:0CE6.0022: Registered DualSense controller hw_version=0x0313 fw_version=0x0104000c Feb 24 21:38:02 cxl-desktop-1 mtp-probe[275167]: checking bus 1, device 22: "/sys/devices/pci:00/:00:14.0/usb1/1-9" Feb 24 21:38:02 cxl-desktop-1 mtp-probe[275167]: bus: 1, device: 22 was not an MTP device Feb 24 21:38:02 cxl-desktop-1 kded5[91269]: Touchpad reset Feb 24 21:38:03 cxl-desktop-1 kded5[91269]: KCrash: Attempting to start /usr/bin/kded5 Feb 24 21:38:03 cxl-desktop-1 kded5[91269]: KCrash: Application 'kded5' crashing... Feb 24 21:38:03 cxl-desktop-1 kded5[91269]: KCrash: Attempting to start /usr/libexec/drkonqi Backtrace from gdb (with debuginfo): Core was generated by `/usr/bin/kded5'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading 0.00 MB source file /usr/src/debug/glibc-2.36-9.fc37.x86_64/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7f5ac256c840 (LWP 275201))] (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f5ac1aafec3 in __pthread_kill_internal (signo=11, threadid=) at pthread_kill.c:78 #2 0x7f5ac1a5fa76 in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26 #3 0x7f5ac374b7b1 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kf5-kcrash-5.103.0-1.fc37.x86_64/src/kcrash.cpp:611 #4 0x7f5ac1a5fb20 in () at /lib64/libc.so.6 #5 0x7f5ac1ef14b9 in XPending (dpy=0x7f5a9a94e4a0 ) at
[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_autogen/7HEHEGDA3T/moc_common.cpp:119:38 ==20622==ABORTING -
[kwin] [Bug 466179] Graphical glitches after minimizing windows using multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=466179 --- Comment #5 from Andrew --- (In reply to Nate Graham from comment #4) > 1. Is this 100% reproducible, or did it happen once and then never again? It is NOT 100% reproducible. I don't know if that is a good thing or a bad thing This has happened to me twice on separate days. If it happens again, I will make sure to immediately note any special circumstances (for example, previous graphical problems I had encountered were propagated by connecting a sleeping laptop to the monitors and then waking it). I know it is frustrating to receive a bug report with little contextual information. I should note that while I had other multi-monitor graphical glitches before (like my wallpaper changing randomly or flickering displays), this exact problem only appeared after I updated to 5.27. As far as good news: I haven't encountered those previous problems since upgrading to 5.27 so... congrats! The updated display configuration capacities seem to be working. > 2. If you right-click on the black area, do you get a context menu? I can't say now, but I will remember to check the next time this happens (if there is a next time). --- Thanks for all of your hard work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466179] Graphical glitches after minimizing windows using multi-screen setup
https://bugs.kde.org/show_bug.cgi?id=466179 --- Comment #2 from Andrew --- (In reply to Nate Graham from comment #1) > What kind of GPU are you using? > > Also, can you paste the output of: > - `kscreen-doctor -o` > - `qdbus org.kde.KWin /KWin supportInformation` Here is the output of when my laptop is connected to my monitors via a CalDigit TB3+ dock: ``` ➜ ~ inxi -Gzzz Graphics: Device-1: Intel Iris Plus Graphics 640 driver: i915 v: kernel Device-2: Suyin HP TrueVision FHD RGB-IR type: USB driver: uvcvideo Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1 compositor: kwin_wayland driver: X: loaded: intel gpu: i915 resolution: 1: 900x1600 2: 2560x1440 3: 900x1600 OpenGL: renderer: Mesa Intel Iris Plus Graphics 640 (Kaby Lake GT3e) (KBL GT3) v: 4.6 Mesa 22.2.5 ``` ``` ➜ ~ kscreen-doctor -o Output: 1 eDP-1 disabled connected priority 0 Panel Modes: 0:1920x1080@60*! 1:1920x1080@40 2:1280x1024@60 3:1024x768@60 4:1280x800@60 5:1920x1080@60 6:1600x900@60 7:1368x768@60 8:1280x720@60 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 DP-2 enabled connected priority 2 DisplayPort Modes: 0:1600x900@60*! 1:1280x1024@75 2:1280x1024@60 3:1152x864@75 4:1024x768@75 5:1024x768@60 6:800x600@75 7:800x600@60 8:640x480@75 9:640x480@60 10:720x400@70 11:1024x768@60 12:1280x800@60 13:1368x768@60 14:1280x720@60 Geometry: 0,0 900x1600 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 3 DP-3 enabled connected priority 1 DisplayPort Modes: 0:2560x1440@60*! 1:2048x1080@60 2:2048x1080@24 3:1920x1080@60 4:1920x1080@60 5:1920x1080@60 6:1920x1080@50 7:1600x1200@60 8:1280x1024@75 9:1280x1024@60 10:1152x864@75 11:1280x720@60 12:1280x720@60 13:1280x720@60 14:1280x720@50 15:1024x768@75 16:1024x768@60 17:800x600@75 18:800x600@60 19:720x576@50 20:720x576@50 21:720x480@60 22:720x480@60 23:720x480@60 24:720x480@60 25:640x480@75 26:640x480@60 27:640x480@60 28:640x480@60 29:720x400@70 30:1600x1200@60 31:1280x1024@60 32:1024x768@60 33:1920x1200@60 34:1280x800@60 35:1920x1080@60 36:1600x900@60 37:1368x768@60 38:1280x720@60 Geometry: 900,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 4 DP-4 enabled connected priority 3 DisplayPort Modes: 0:1600x900@60*! 1:1280x1024@75 2:1280x1024@60 3:1152x864@75 4:1024x768@75 5:1024x768@60 6:800x600@75 7:800x600@60 8:640x480@75 9:640x480@60 10:720x400@70 11:1024x768@60 12:1280x800@60 13:1368x768@60 14:1280x720@60 Geometry: 3460,0 900x1600 Scale: 1 Rotation: 2 Overscan: 0 Vrr: incapable RgbRange: Automatic ``` ``` KWin Support Information: The following information should be used when requesting support on e.g. https://forum.kde.org. It provides information about the currently running instance, which options are used, what OpenGL driver and which effects are running. Please post the information provided underneath this introductory text to a paste bin service like https://paste.kde.org instead of pasting into support threads. == Version === KWin version: 5.27.0 Qt Version: 5.15.8 Qt compile version: 5.15.8 XCB compile version: 1.14 Operation Mode: Xwayland Build Options = KWIN_BUILD_DECORATIONS: yes KWIN_BUILD_TABBOX: yes KWIN_BUILD_ACTIVITIES: yes HAVE_X11_XCB: yes HAVE_EPOXY_GLX: yes X11 === Vendor: The X.Org Foundation Vendor Release: 12201001 Protocol Version/Revision: 11/0 SHAPE: yes; Version: 0x11 RANDR: yes; Version: 0x14 DAMAGE: yes; Version: 0x11 Composite: yes; Version: 0x4 RENDER: yes; Version: 0xb XFIXES: yes; Version: 0x50 SYNC: yes; Version: 0x31 GLX: yes; Version: 0x0 Decoration == Plugin: org.kde.breeze Theme: Plugin recommends border size: None onAllDesktopsAvailable: false alphaChannelSupported: true closeOnDoubleClickOnMenu: false decorationButtonsLeft: 1 decorationButtonsRight: 6, 3, 4, 5 borderSize: 0 gridUnit: 10 font: Noto Sans,10,-1,0,50,0,0,0,0,0 smallSpacing: 2 largeSpacing: 10 Output backend == Name: DRM Active: true Atomic Mode Setting on GPU 0: true Cursor == themeName: breeze_cursors themeSize: 24 Options === focusPolicy: 1 xwaylandCrashPolicy: xwaylandMaxCrashCount: 3 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 750 delayFocusInterval: 300 shadeHover: false shadeHoverInterval: 250 separateScreenFocus: false activeMouseScreen: true placement: activationDesktopPolicy: 0 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false rollOverDesktops: false focusStealingPreventionLevel: 1 operationTitlebarDblClick: 5000 operationMaxButtonLeftClick: 5000 operationMaxButtonMiddleClick: 5015 operationMaxButtonRightClick: 5014 commandActiveTitlebar1: 0 commandActiveTitlebar2: 28 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInacti
[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.
[KScreen] [Bug 464590] kded5 crashes in KScreen::Config::setOutputPriority() after monitor wakes from sleep
https://bugs.kde.org/show_bug.cgi?id=464590 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 466036] kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.com --- Comment #3 from Andrew Gunnerson --- I've having the same issue as well after the Plasma 5.27.0 update. When this occurs, the screen also stays blank until I switch to another VT and then back. Software info: * Distro: Fedora 37 * Session type: X11 * kernel: 6.1.11-200.fc37.x86_64 * kf5: 5.103.0-1.fc37.x86_64 * plasma: 5.27.0-2.fc37.x86_64 * qt5: 5.15.8-5.fc37.x86_64 * Nvidia proprietary drivers: 525.89.02-1.fc37.x86_64 Backtrace with debuginfo: Core was generated by `/usr/bin/kded5'. Program terminated with signal SIGSEGV, Segmentation fault. #0 KScreen::Output::id (this=0x0) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/output.cpp:189 Downloading 0.00 MB source file /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/output.cpp 189 return d->id; [Current thread is 1 (Thread 0x7f3ae576c840 (LWP 593267))] (gdb) bt #0 KScreen::Output::id() const (this=0x0) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/output.cpp:189 #1 0x7f3abc09110c in KScreen::Config::setOutputPriority(QSharedPointer const&, unsigned int) (this=0x558343e4d3f0, output=..., priority=1) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:301 #2 0x7f3abc09aa5e in KScreen::SetConfigOperationPrivate::fixPrimaryOutput() (this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:301 #3 KScreen::SetConfigOperation::start() (this=0x558343ae4550) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/setconfigoperation.cpp:114 #4 0x7f3ae54c8134 in QObject::event(QEvent*) (this=0x558343ae4550, e=0x558343e21070) at kernel/qobject.cpp:1347 #5 0x7f3ae63aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x558343ae4550, e=0x558343e21070) at kernel/qapplication.cpp:3640 #6 0x7f3ae549d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x558343ae4550, event=0x558343e21070) at kernel/qcoreapplication.cpp:1064 #7 0x7f3ae54a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x5583433de340) at kernel/qcoreapplication.cpp:1821 #8 0x7f3ae54eeb07 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5583434bfe20) at kernel/qeventdispatcher_glib.cpp:277 #9 0x7f3ae4264cbf in g_main_dispatch (context=0x7f3acc005010) at ../glib/gmain.c:3444 #10 g_main_context_dispatch (context=0x7f3acc005010) at ../glib/gmain.c:4162 #11 0x7f3ae42ba598 in g_main_context_iterate.constprop.0 (context=0x7f3acc005010, block=1, dispatch=1, self=) at ../glib/gmain.c:4238 #12 0x7f3ae4261f40 in g_main_context_iteration (context=0x7f3acc005010, may_block=1) at ../glib/gmain.c:4303 #13 0x7f3ae54ee5fa in QEventDispatcherGlib::processEvents(QFlags) (this=0x5583434bf6e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #14 0x7f3ae549bf3a in QEventLoop::exec(QFlags) (this=this@entry=0x7fff5b65c820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #15 0x7f3ae54a4002 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #16 0x7f3ae595fad0 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1863 #17 0x7f3ae63aecd9 in QApplication::exec() () at kernel/qapplication.cpp:2832 #18 0x55834213d5ab in main(int, char**) (argc=, argv=) at /usr/src/debug/kf5-kded-5.103.0-1.fc37.x86_64/src/kded.cpp:785 -- 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.
[kde] [Bug 466179] New: Artifacts from minimized windows are visible and flickering
https://bugs.kde.org/show_bug.cgi?id=466179 Bug ID: 466179 Summary: Artifacts from minimized windows are visible and flickering Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: parsonsandr...@gmail.com Target Milestone: --- Created attachment 156562 --> https://bugs.kde.org/attachment.cgi?id=156562=edit Screenshot of desktop; artifacts from minimized windows are visible and flickering. SUMMARY STEPS TO REPRODUCE 1. Have a portrait-landscape-portrait multi-monitor setup. 2. Minimize windows 3. Observe flickering result OBSERVED RESULT See screenshot. EXPECTED RESULT Wallpaper displays and artifacts of windows don't display. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Wayland. Kernel 5.19.0-32-generic (64 bit) -- 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.
[kdeplasma-addons] [Bug 389766] Weather widget does not show the temperature beside or over the icon in the Plasma panel when I use wetter.com provider
https://bugs.kde.org/show_bug.cgi?id=389766 --- Comment #9 from Andrew Brouwers --- Is it possible to switch providers, or offer others (for example, met.no or openweathermap seem popular with other OSS projects) for people to choose? It seems broken to ship wetter if it will never work for such a common case. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465056] Tokodon crash when opening "conversation"
https://bugs.kde.org/show_bug.cgi?id=465056 Andrew Nitrogenesis changed: What|Removed |Added CC||nitrogenesis.developer@gmai ||l.com -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 465056] Tokodon crash when opening "conversation"
https://bugs.kde.org/show_bug.cgi?id=465056 --- Comment #3 from Andrew Nitrogenesis --- Created attachment 156369 --> https://bugs.kde.org/attachment.cgi?id=156369=edit New crash information added by DrKonqi tokodon (23.01.0) using Qt 5.15.8 Plasma 5.27.0, Arch Linux, Tokodon 23.01.0 Tokodon crashes when trying to open tab "Conversations" on an instance that doesn't support them (in my case social.linux.pizza). How I think that might be fixed: Check if instance supports Conversations and show/hide tab when does/doesn't -- Backtrace (Reduced): #8 0x7fcb73d7463d in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /usr/lib/libQt5Qml.so.5 [...] #11 0x7fcb73d36c36 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #12 0x7fcb73e971ad in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #13 0x7fcb73e97729 in QQmlBinding::evaluate(bool*) () from /usr/lib/libQt5Qml.so.5 [...] #15 0x7fcb73e98f73 in QQmlBinding::update(QFlags) () from /usr/lib/libQt5Qml.so.5 -- 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.
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 --- Comment #10 from Andrew Gunnerson --- Woohoo! Any chance we could leave this issue open? The patch is good enough for my use case, but the general problem still exists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 --- Comment #15 from Andrew Hakman --- (In reply to Andrew Hakman from comment #14) > Oh, also, even when I do manage to get my session back, the second monitor > stays disconnected and not detected in display settings. Sometimes switching > between applications will magically bring it back, sometimes starting to > play video in mplayer will bring it back, and sometimes doing all of that > doesn't. It's very non-deterministic. Oh, and apparently sometimes closing windows will bring it back. I thought I was going to have to reboot to recover it this time, started closing windows, and after closing one, the second monitor was re detected (and the menu and task switcher came back at the same time) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 Andrew Hakman changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WORKSFORME |--- Status|RESOLVED|REOPENED --- Comment #14 from Andrew Hakman --- Oh, also, even when I do manage to get my session back, the second monitor stays disconnected and not detected in display settings. Sometimes switching between applications will magically bring it back, sometimes starting to play video in mplayer will bring it back, and sometimes doing all of that doesn't. It's very non-deterministic. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464334] Plasmashell crash when primary monitor disconnected
https://bugs.kde.org/show_bug.cgi?id=464334 Andrew Hakman changed: What|Removed |Added CC||andrew.hak...@gmail.com --- Comment #13 from Andrew Hakman --- I am also having this same bug after updating Debian SID recently. I routinely lock my session, and then turn off my monitors, and when I turn off the primary monitor, kded5 crashes / takes lots of CPU. When I turn my monitors back on later, the lock screen is stuck at the time I turned off the monitors last time, and nothing is responding. I have to manually kill all the kded5 processes and restart some combination of kwin, kded5, and plasmashell from a virtual tty to sometimes get my session back. Not sure if it's useful or not, but my 2 monitors are different resolutions (1 is 1920x1080, the other is 1920x1200) - this seems to cause much weird behavior in plasma / kwin / something, but I never had this crash on turning monitors off until very recently. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 --- Comment #8 from Andrew Gunnerson --- Thanks for the info, Dāvis! Looking forward to the upcoming changes :) I'm quite new to the KIO and Dolphin code bases, but happy to help wherever I can if needed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 --- Comment #5 from Andrew Gunnerson --- I submitted an MR for skipping directory counts when KFileItem::isSlow() here: https://invent.kde.org/system/dolphin/-/merge_requests/507 --- Regarding the slow stat() calls blocking the UI, I did some further investigation. The stat() calls are coming from KIO::WorkerThread threads, not the UI thread. The stack trace looks something like this: Thread 14 (Thread 0x7fffbd7fa6c0 (LWP 255122) "KIO::WorkerThre"): #0 stat (pathname=0x7fff9c00abe8 "/home/chenxiaolong", statbuf=0x7fffbd7f9780) at slow_stat.cpp:35 #1 0x76f16646 in acl_get_file (path_p=0x7fff9c00abe8 "/home/chenxiaolong", type=16384) at libacl/acl_get_file.c:73 #2 0x7fffd80be93e in createUDSEntry(QString const&, QByteArray const&, KIO::UDSEntry&, QFlags, QString const&) [clone .lto_priv.0] () from /usr/lib64/qt5/plugins/kf5/kio/kio_file.so #3 0x7fffd80c64c6 in FileProtocol::stat(QUrl const&) () from /usr/lib64/qt5/plugins/kf5/kio/kio_file.so #4 0x7790ff15 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #5 0x7790869e in KIO::SlaveBase::dispatchLoop() () from /lib64/libKF5KIOCore.so.5 #6 0x77983553 in KIO::WorkerThread::run() () from /lib64/libKF5KIOCore.so.5 #7 0x75ae8507 in QThreadPrivate::start (arg=0x55683ff0) at thread/qthread_unix.cpp:330 #8 0x754ae12d in start_thread (arg=) at pthread_create.c:442 #9 0x7552fbc0 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Since the UI is freezing despite the slow stat calls being on another thread, I'm assuming there's a StatJob::exec()/KJob::exec() call somewhere forcing the UI to wait for its completion. Unfortunately, I've had no luck at all tracking down where the job came from. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 --- Comment #3 from Andrew Gunnerson --- (In reply to Nate Graham from comment #2) > > Specifically, when I try to access a `cifs` mount point > For just this reason, it's not recommended to manually mount network shares. > Is there a reason why you have to do this, and accessing the share from its > network URL when needed doesn't work for you? Yeah, unfortunately, kio smb:// isn't quite fast enough for my (admittedly unusual) use case. I'm connecting to a very high bandwidth server and frequently access files both from GUI apps and the CLI. With kernel cifs mounts, I get around ~3 GiB/s sequential reads/writes, and Dolphin + smb:// only hits around ~500 MiB/s and kio-fuse around ~80 MiB/s. > Regardless, skipping directory counts for known slow paths would probably > help indeed. Can you please submit it at > https://invent.kde.org/system/dolphin/-/merge_requests? Sure thing! -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 457472] Crash when reloading modified files
https://bugs.kde.org/show_bug.cgi?id=457472 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465357] Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 --- Comment #1 from Andrew Gunnerson --- Created attachment 155993 --> https://bugs.kde.org/attachment.cgi?id=155993=edit A tiny library to intentionally slow down stat() for testing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465357] New: Dolphin's UI freezes when stat() is slow
https://bugs.kde.org/show_bug.cgi?id=465357 Bug ID: 465357 Summary: Dolphin's UI freezes when stat() is slow Classification: Applications Product: dolphin Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: accounts+...@chiller3.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 155992 --> https://bugs.kde.org/attachment.cgi?id=155992=edit A patch to skip directory counts when KFileItem::isSlow SUMMARY When stat() does not complete quickly, Dolphin's UI freezes until it returns. This seems to be the root cause for the freezes I'm encountering. Specifically, when I try to access a `cifs` mount point, Dolphin kicks off `KDirectoryContentsCounter.scanDirectory()` for all the subdirectories visible on screen. The opendir/readdir calls are enough to slow down the server to the point where each stat takes a couple of seconds. Once stat starts slowing down, the Dolphin's UI stops responding. I've been working around the problem by making Dolphin skip `KDirectoryContentsCounter.scanDirectory()` if `KFileItem::isSlow()` is true (patch attached). Even though this hides the issue, I wonder if it may be good to have anyway since it matches the behavior of kio smb://, where directory counts don't happen. STEPS TO REPRODUCE To avoid the need to connect to a slow server, I've attached an LD_PRELOAD'able library to help reproduce this. It slows down all stat calls to paths under /home/, except for paths containing "/." so that Dolphin's startup isn't slowed down when reading configs. 1. $ g++ -shared -fPIC slow_stat.cpp -o slow_stat.so 2. $ LD_PRELOAD=$(pwd)/slow_stat.so dolphin 3. Navigate to somewhere under /home/ 4. Try to perform UI actions, like hovering over items, selecting, right clicking, opening menus, etc. OBSERVED RESULT Dolphin's UI freezes until stat returns EXPECTED RESULT Dolphin should ideally remain responsive while stat occurs SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION (Patch for my workaround is attached) I've also tried compiling the latest commit in dolphin (580f3bf0d5c8735cf230208fd6e4b288a3e55722) and there's no change in behavior. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423499] KFileItem::iconName ignorant of isSlow() and can block gui thread
https://bugs.kde.org/show_bug.cgi?id=423499 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447948] Lift gamma gain
https://bugs.kde.org/show_bug.cgi?id=447948 Andrew Buck changed: What|Removed |Added CC||andrew.r.b...@gmail.com --- Comment #4 from Andrew Buck --- A quick summary of what the video shows. Changing the slider bars up/down on the lift/gamma/gain effect causes the color selected on the color wheel associated with that slider to wander around to random colors as the slider moves up and down. I experienced the same thing when running the flatpack version of kdenlive, but if I run the native installed version (from the ppa) I don't experience this effect. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 394535] Torrents menu item has no accelerator key assigned
https://bugs.kde.org/show_bug.cgi?id=394535 --- Comment #3 from andrew brewster --- Created attachment 155831 --> https://bugs.kde.org/attachment.cgi?id=155831=edit Screenshot of KTorrent menu items with no accelerator key for Torrents item -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465081] New: Localization error in plasma-workspace 5.26.5-3
https://bugs.kde.org/show_bug.cgi?id=465081 Bug ID: 465081 Summary: Localization error in plasma-workspace 5.26.5-3 Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: foxscarlet...@gmail.com Target Milestone: --- Created attachment 155824 --> https://bugs.kde.org/attachment.cgi?id=155824=edit Localization error in plasma-workspace 5.26.5-3 SUMMARY Linux/KDE Plasma: Arch Linux KDE Plasma (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465000] New: Rotation for transform effect and similar does not allow fractional degrees.
https://bugs.kde.org/show_bug.cgi?id=465000 Bug ID: 465000 Summary: Rotation for transform effect and similar does not allow fractional degrees. Classification: Applications Product: kdenlive Version: 22.12.1 Platform: Flatpak OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: andrew.r.b...@gmail.com Target Milestone: --- When Adding a transform effect or any similar one that offers a rotion option, like crop/rotate or similar, the field letting you set the rotation angle only allows integer values for a degree. So rotations by less than 1 degree are not possible. I have a video where I did a push in with the zoom on the camera lens and the action of turning the knob on the lens rotates the video by about 1/2 degree and then back 1/2 degree the other way when the push zoom is stopped. A transform would fix this nicely, but 1 degree is too big of a rotation. So basically just need to tweak the UI to allow floating point numbers to be specified on rotation angles, instead of limiting these fields to integers. The slider bar can still be limited to integers as that is what most people will want, but being able to type in a value with the keyboard like '0.5' would fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 464780] New: Wishlist Request for more command-line control
https://bugs.kde.org/show_bug.cgi?id=464780 Bug ID: 464780 Summary: Wishlist Request for more command-line control Classification: Applications Product: okular Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: a...@meiji.ac.jp Target Milestone: --- SUMMARY *** In order to integrate okular into varied workflows, such as online presentation, in-person presentation, display of documents processed from LaTeX, it would be very useful to have more control of a specific okular instance via command-line flags rather than having to open the window and then use the graphical interface to set display options. *** STEPS TO REPRODUCE 1. open okular from the command line 2. new window inherits settings such as "menu visible" and "view mode" from the settings and then the most recently altered open instance 3. No option to give options for the new window on the command line OBSERVED RESULT New instances inherit current settings from most recently interacted with instance EXPECTED RESULT Desire to be able to open with menu visible or not visible and in fit-to-page view mode or fit-width view mode (or others) via a command line option. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464286] klipper can't save in history both mouse selection and ctrl+c clipboard without synchronizing them
https://bugs.kde.org/show_bug.cgi?id=464286 --- Comment #4 from Andrew --- (In reply to Nate Graham from comment #3) > If we intermixed them, the history wouldn't work as > people expect, and would be commonly populated with random-seeming text, > which is in fact how it used to be, and we got a lot of complaints about it. So I'm right with my feel that it worked recently and just stopped. OK, but is there anything wrong with enabling "Always save in history" radio buttons? People can't complain if they enabled this intermixing by themselves with a clearly named option. And everything is ready for that, I just don't get why these buttons became disabled for some cases. it's just not very convenient to remind yourself to press ctrl+c for all data which might be necessary for you later. For me there is no problem when some random selection adds to the history - I just ignore it since it doesn't affect any of my workflows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464286] klipper can't save in history both mouse selection and ctrl+c clipboard without synchronizing them
https://bugs.kde.org/show_bug.cgi?id=464286 --- Comment #2 from Andrew --- (In reply to Nate Graham from comment #1) > I think it would be helpful if you could explain your use case, yeah. What I have in mind right now: 1) Simultaneous copypasting two elements instead of one. Like: select one line, do ctrl+c. Select another and get it copied in mouse buffer. Now move to the destination and ctrl+v for pasting first snippet and middle click for second. 2) Just replacing some text with another. Select source, do ctrl+c (or don't). Move to destination, select it to be replaced. It's often much more convenient instead of "paste new, then delete old" because you can select a word with double click for example and it will not be possible after pasting. After electing the destination text, press ctrl+v. Text will be replaced with itself instead of source snippet. Both of that is possible when checkbox "keep the selection and clipboard the same" is not set - but I want also to have everything saved in history to find it later. Just can't enable this saving, "always save" radio buttons are disabled for some reason. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452119] Poor performance on intel igp on wayland versus Xorg
https://bugs.kde.org/show_bug.cgi?id=452119 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.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 #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=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 450327] Night Color Has No Effect on KDE Wayland with NVIDIA
https://bugs.kde.org/show_bug.cgi?id=450327 andrew morris changed: What|Removed |Added CC||andy_morri...@yahoo.com --- Comment #3 from andrew morris --- Bug confirmed on my machine. Works on x11 but not wayland. Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.18.18-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-4720HQ CPU @ 2.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980M/PCIe/SSE2 Manufacturer: ASUSTeK COMPUTER INC. Product Name: G751JY System Version: 1.0 Relevent packages: Name : akmod-nvidia Version : 515.65.01 & Name : akmods Version : 0.5.7 -- 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.
[plasmashell] [Bug 464286] New: klipper can't save in journal both mouse selection and ctrl+c clipboard without synchronizing them
https://bugs.kde.org/show_bug.cgi?id=464286 Bug ID: 464286 Summary: klipper can't save in journal both mouse selection and ctrl+c clipboard without synchronizing them Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: travn...@gmail.com Target Milestone: 1.0 I believe it's recent regression which I got in Fedora 37 few days ago after updating plasma-workspace-5.26.4.1-1.fc37.x86_64 -> plasma-workspace-5.26.5-1.fc37.x86_64 What I had and want to have working at the same time (can put more details why it helps me, if necessary): 1) * mouse selection can be pasted only by middle mouse button click and not by ctrl+v (ctrl+v pastes different content) * ctrl+c clipboard can be pasted only by ctrl+v and not by middle mouse button click (mouse pastes different content) 2) * both ctrl+c and mouse selection are saved in Klipper's list / journal Currently I could have 1) or 2) but not together. And it worked previously, I think. When have 1) - mouse selection is not saved in journal and the related radio button in Klipper's settings is disabled for some reason. When have 2) - mouse selection is also pasted by ctrl+v. I see some similar bugs here, but all of them seem referencing Wayland and I don't use it. Using X.Org X Server 1.20.14 KDE Frameworks 5.101.0 Qt 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461155] On Wayland, "Keep the selection and clipboard the same" only works if "Text selection: Always save in history" is also active
https://bugs.kde.org/show_bug.cgi?id=461155 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 459335] Klipper's history is not updated in the Wayland session
https://bugs.kde.org/show_bug.cgi?id=459335 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427214] Add ability to paste Klipper's contents on selection
https://bugs.kde.org/show_bug.cgi?id=427214 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 395284] Clipboard entries added by xclip are not accessible by ctrl-v
https://bugs.kde.org/show_bug.cgi?id=395284 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355841] Unpredictable what actually will be pasted due to copy-only-selection item not being visually differentiated in any way
https://bugs.kde.org/show_bug.cgi?id=355841 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 97913] Clipboard / Selection Behavior enhancement
https://bugs.kde.org/show_bug.cgi?id=97913 Andrew changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 432627] drag and drop from remote locations (dolphin/kio-fuse) to apps not working
https://bugs.kde.org/show_bug.cgi?id=432627 Andrew Gunnerson changed: What|Removed |Added CC||accounts+...@chiller3.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464174] Add Watermark with text fails to process any items with no useful output
https://bugs.kde.org/show_bug.cgi?id=464174 --- Comment #1 from Andrew Sayman --- It appears to have something to do with the font selection. When I pick fonts that begin in "MS," it fails with an empty error message. When I pick "Noto Sans," "Noto Serif," or "DejaVu Serif" then the watermark is successfully added. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 464174] New: Add Watermark with text fails to process any items with no useful output
https://bugs.kde.org/show_bug.cgi?id=464174 Bug ID: 464174 Summary: Add Watermark with text fails to process any items with no useful output Classification: Applications Product: digikam Version: 7.9.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Bqm-WaterMark Assignee: digikam-bugs-n...@kde.org Reporter: andrew.say...@gmail.com Target Milestone: --- SUMMARY I have recently moved to Windows 11. I'm setting up a new workflow and Adding a text watermark does not work. The error output and the debug view output is not useful. It's worth noting that the Watermark plugin works if I use an image instead of text. This is not some general failure where my system can't do any batch processing. STEPS TO REPRODUCE 1. Add an image to the batch queue manager 2. Select Decorate -> Add Watermark 3. Click on text 4. Set the watermark text to 'a' 5. Click run OBSERVED RESULT The item fails to be processed. 18:21:43 :: Item "P1200861.jpg" from queue "#1": Processing... 18:21:43 :: Item "P1200861.jpg" from queue "#1": Failed to process item... 18:21:43 :: Item "P1200861.jpg" from queue "#1": 18:21:43 :: Item "P1200861.jpg" from queue "#1": Failed to process item... 18:21:43 :: Item "P1200861.jpg" from queue "#1": Failed to create file... In the debug view the only output is: [5872] QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout EXPECTED RESULT A new version of the image is generated which has 'a' somewhere in it. SOFTWARE/OS VERSIONS Windows: 11 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 464059] New: ktorrent segfaults while quit
https://bugs.kde.org/show_bug.cgi?id=464059 Bug ID: 464059 Summary: ktorrent segfaults while quit Classification: Applications Product: ktorrent Version: 22.12.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: travn...@gmail.com Target Milestone: --- Application: ktorrent (22.12.0) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.0.16-300.fc37.x86_64+debug x86_64 Windowing System: X11 Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: Happens when I start Ktorrent with some active torrents placed on an unmounted drive. It asks if I want to download them again, I answer no and quit - it segfaults immediately. Fedora 37 x64 ktorrent-22.12.0-1.fc37.x86_64 The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault [KCrash Handler] #4 0x7f6fcf57a3e0 in QtPrivate::isRightToLeft(QStringView) () from /lib64/libQt5Core.so.5 #5 0x7f6fcfc30363 in QTextEngine::itemize() const () from /lib64/libQt5Gui.so.5 #6 0x7f6fcfc39aa0 in QTextLayout::beginLayout() () from /lib64/libQt5Gui.so.5 #7 0x7f6fd0426fe4 in viewItemTextLayout(QTextLayout&, int, int, int*) () from /lib64/libQt5Widgets.so.5 #8 0x7f6fd042b461 in QCommonStylePrivate::viewItemSize(QStyleOptionViewItem const*, int) const () from /lib64/libQt5Widgets.so.5 #9 0x7f6fd042b84f in QCommonStylePrivate::viewItemLayout(QStyleOptionViewItem const*, QRect*, QRect*, QRect*, bool) const () from /lib64/libQt5Widgets.so.5 #10 0x7f6fd042c5ca in QCommonStyle::sizeFromContents(QStyle::ContentsType, QStyleOption const*, QSize const&, QWidget const*) const () from /lib64/libQt5Widgets.so.5 #11 0x7f6fd0497b78 in QFusionStyle::sizeFromContents(QStyle::ContentsType, QStyleOption const*, QSize const&, QWidget const*) const () from /lib64/libQt5Widgets.so.5 #12 0x7f6fd065192e in QStyledItemDelegate::sizeHint(QStyleOptionViewItem const&, QModelIndex const&) const () from /lib64/libQt5Widgets.so.5 #13 0x55da1b700548 in kt::ViewDelegate::sizeHint(QStyleOptionViewItem const&, QModelIndex const&) const () #14 0x7f6fd06979f3 in QTreeView::indexRowSizeHint(QModelIndex const&) const () from /lib64/libQt5Widgets.so.5 #15 0x7f6fd069ef3e in QTreeViewPrivate::layout(int, bool, bool) () from /lib64/libQt5Widgets.so.5 #16 0x7f6fd06a4da1 in QTreeView::doItemsLayout() () from /lib64/libQt5Widgets.so.5 #17 0x7f6fd069c94d in QTreeViewPrivate::updateScrollBars() () from /lib64/libQt5Widgets.so.5 #18 0x7f6fd06a6882 in QTreeView::updateGeometries() () from /lib64/libQt5Widgets.so.5 #19 0x7f6fcf6dbdaf in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #20 0x7f6fd0644f03 in QHeaderView::viewportEvent(QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f6fcf6a8041 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7f6fd03aed02 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7f6fcf6a8278 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7f6fd03ec770 in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #25 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #26 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #27 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #28 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #29 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #30 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #31 0x7f6fd03ec75d in QWidgetPrivate::hideChildren(bool) () from /lib64/libQt5Widgets.so.5 #32 0x7f6fd03ec947 in QWidgetPrivate::hide_helper() () from /lib64/libQt5Widgets.so.5 #33 0x7f6fd03f1568 in QWidgetPrivate::setVisible(bool) () from /lib64/libQt5Widgets.so.5 #34 0x7f6fd03ecdf8 in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () from /lib64/libQt5Widgets.so.5 #35 0x7f6fd03ed384 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #36 0x55da1b6996d0 in kt::GUI::~GUI() () #37 0x55da1b6845eb in main () [Inferior 1 (process 3590) detached] The reporter indicates this bug may be a duplicate of or related to bug 383127. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 463989] Remote RAW image previews don't work because of missing file extension in thumbnail temp file
https://bugs.kde.org/show_bug.cgi?id=463989 --- Comment #2 from Andrew Gunnerson --- In case approach #2 is acceptable, I've created an MR to implement that here: https://invent.kde.org/frameworks/kio/-/merge_requests/1103 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 463989] New: Remote RAW image previews don't work because of missing file extension in thumbnail temp file
https://bugs.kde.org/show_bug.cgi?id=463989 Bug ID: 463989 Summary: Remote RAW image previews don't work because of missing file extension in thumbnail temp file Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.101.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: accounts+...@chiller3.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY In Dolphin, when browsing a directory containing RAW image files (eg. Canon's .cr2), previews work for local files, but not remote files. I believe I've tracked down the reason: On the Dolphin side, when it runs the PreviewJob, it takes this code path for remote files: https://invent.kde.org/frameworks/kio/-/blob/v5.101.0/src/widgets/previewjob.cpp#L742. This creates a file called /tmp/dolphin.XX, which is passed to the thumbnailer. On the kioslave/thumbnail.so side, RAWCreator::create() is called as expected (https://invent.kde.org/graphics/kdegraphics-thumbnailers/-/blob/v22.12.0/raw/rawcreator.cpp#L47), which then calls https://invent.kde.org/graphics/libkdcraw/-/blob/v22.12.0/src/kdcraw.cpp#L87. KDcraw::loadEmbeddedPreview() returns false because of the `!rawFilesExt.toUpper().contains(ext)` condition. libkdcraw requires the filename to have a known file extension. Off the top of my head, it seems like there are a couple ways to solve this: 1. Change libkdcraw to not depend on the file extension (not sure how feasible this is). 2. Change kio so that the temporary file it creates has the original file extension. STEPS TO REPRODUCE 1. In Dolphin, change the settings for the max file limit for remote thumbnails. 2. Navigate to a remote folder containing RAW images. OBSERVED RESULT There are no thumbnails. EXPECTED RESULT Thumbnails should be shown. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION (Included above) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463952] Moving a file within the same remote share results in a copy (via kio-fuse) + delete
https://bugs.kde.org/show_bug.cgi?id=463952 --- Comment #1 from Andrew Gunnerson --- I did a bit more testing to try and track this down. The latest commit in `master` (https://invent.kde.org/system/dolphin/-/commit/1c4baff760c7975d17381f72029a145943b32ff6) still has this problem. Doing a git bisect shows that https://invent.kde.org/system/dolphin/-/commit/8d7e600f63a1961294dfe2c278a710b4ce0716e9 is the commit that first introduced the problem. Reverting that commit on top of `master` fixes the problem. The `release/22.12` branch also works because of the revert at https://invent.kde.org/system/dolphin/-/merge_requests/479. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 463967] New: Missing console.log when running Plasmoid Launcher
https://bugs.kde.org/show_bug.cgi?id=463967 Bug ID: 463967 Summary: Missing console.log when running Plasmoid Launcher Classification: Applications Product: kdevelop Version: 5.10.221200 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Output Views Assignee: kdevelop-bugs-n...@kde.org Reporter: ash...@linuxcomp.ru Target Milestone: --- SUMMARY When executing plasmoid, there is no output from console.log messages from plasmoid. I am developing the plasmoid/widget using KDevelop. I want to be able to launch it for testing with Execute button. For this I created a new launch configuration of type Plasmoid Launcher. But it misses the debugging/log messages. STEPS TO REPRODUCE 1. Open a plasmoid project that has some console.log messages in it. I use my own org.kde.plasma.monitorcommander. 2. Create a launch configuration: 2.1 Click Run -> "Configure Launches". A Launch Configurations window will appear. 2.2 Press Add -> "Plasmoid Launcher". 2.3. In the "Path or name" type the name or path of the plasmoid (org.kde.plasma.monitorcommander). 2.4 Apply and OK. 3. Press Execute button 4. In Plasmoidviewer window trigger some thing in the plasmoid that should output something with console.log OBSERVED RESULT In the "Run" tool view there is no any logs from plasmoid. The only output is: ``` /tmp> /usr/bin/plasmoidviewer --formfactor planar -a org.kde.plasma.monitorcommander QML debugging is enabled. Only use this in a safe environment. ``` EXPECTED RESULT There should be output that plasmoid generates. Like ``` QML debugging is enabled. Only use this in a safe environment. qml: View QML loaded qml: Hello World <-- the thing plasmoid spitted with console.log ``` SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 KDevelop: 5.10.221200 (22.12.0) ADDITIONAL INFORMATION I was able to workaround this. Workaround 1: Use script configuration and set special environment variable 1. Create a script plasmoid_viewer.sh with the following content: ``` #!/bin/bash echo heelloo plasmoidviewer -a org.kde.plasma.monitorcommander ``` 2. In the "Launch Configurations" add new Script Application. Set "Script interpreter" to bash, set "Always run the same file" and enter the path to the plasmoid_viewer.sh 3. In "Environment" create a new profile, and add the variable QT_FORCE_STDERR_LOGGING with value "1". 4. Choose Run -> "Current Run Configuration" and select a script application you just created. 5. Press Execute. Now you see the console.log messages from plasmoid. P.S. The idea was taken from Bug 397062, and the QT_LOGGING_TO_CONSOLE is deprecated, it was said (not sure if I choose the correct one, but it worked): warning: Environment variable QT_LOGGING_TO_CONSOLE is deprecated, use QT_ASSUME_STDERR_HAS_CONSOLE and/or QT_FORCE_STDERR_LOGGING instead. Without setting a variable, the script's "heelloo" is shown, but plasmoid's log is still not shown. So variable is needed. Workaround 2. Create External Script that launches Konsole and use it instead of Execute button and Run tool view. 1. In "External Scripts" tool view create a new command: ``` konsole -e "plasmoidviewer -a org.kde.plasma.monitorcommander" ``` 2. Press that new script entry. Now you can see the all output including console.log in a separate konsole window. See also: Bug 397062, Bug 360093 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463952] New: Moving a file within the same remote share results in a copy (via kio-fuse) + delete
https://bugs.kde.org/show_bug.cgi?id=463952 Bug ID: 463952 Summary: Moving a file within the same remote share results in a copy (via kio-fuse) + delete Classification: Applications Product: dolphin Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: accounts+...@chiller3.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When trying to move a large file on a remote share into a different directory within the same share, dolphin doesn't perform a move operation. Instead, it's doing a copy via kio-fuse and then a delete. This seems to only happen in dolphin. Doing the move operation via kioclient works fine: kioclient --interactive move smb://hostname/home/large_file.iso smb://hostname/home/new_folder/ STEPS TO REPRODUCE 1. Navigate to a remote share in Dolphin (eg. smb://hostname) 2. Cut a large file 3. Navigate to another directory in the same share 4. Paste the file OBSERVED RESULT Dolphin pops up a notification showing that it's moving the file from /run/user/1000/kio-fuse-XX/smb/hostname/home/large_file.iso to smb://hostname/home/new_folder/large_file.iso. From the speed and network bandwidth, it's apparent that the data is being downloaded and reuploaded. EXPECTED RESULT kio-fuse shouldn't be involved in a move operation across the same remote share. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 37 KDE KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION kio-fuse Version: 5.0.1-4.fc37.x86_64 dolphin Version: 22.12.0-1.fc37.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378223] Request: markdown preview
https://bugs.kde.org/show_bug.cgi?id=378223 Andrew Shark changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378223] Request: markdown preview
https://bugs.kde.org/show_bug.cgi?id=378223 --- Comment #4 from Andrew Shark --- Created attachment 155047 --> https://bugs.kde.org/attachment.cgi?id=155047=edit See where you can enable Preview tool Found it. You need to right click on the bottom pane, then in the pop-up select Preview (see screenshot). Then when clicking on it in toolbar, you will see the preview in parallel with the document. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 378223] Request: markdown preview
https://bugs.kde.org/show_bug.cgi?id=378223 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru --- Comment #3 from Andrew Shark --- Is it released? I have discovered from [this](https://www.reddit.com/r/kde/comments/mw3sts/comment/gvg2ett/?utm_source=share_medium=web2x=3) post that in Kate you can enable markdown preview with enabling Document Preview plugin, and in the right side you will see markdown preview button. But what about KDevelop? There is also a Document Preview plugin there, and it is enabled. But where is a preview view itself? Here https://github.com/KDE/ktexteditorpreviewplugin it is said that it is in Tool View for KDevelop. But where is it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462980] In Panel Edit Mode, "Maximize" button is inappropriately enabled while Panel is already maximized
https://bugs.kde.org/show_bug.cgi?id=462980 --- Comment #6 from Andrew Brouwers --- OK, I guess I won't argue about the UX; I think it's not discoverable and poorly laid out. But, perhaps just disabling "maximize" when the panel is already in a "maximized" state (be it floating or not) would "nudge" the user in the right direction, and allow them to figure it out. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462980] In Panel Edit Mode, "Maximize" button is inappropriately enabled while Panel is already maximized
https://bugs.kde.org/show_bug.cgi?id=462980 --- Comment #4 from Andrew Brouwers --- Yeah, I understand that - I'm just saying "Maximize" and "Floating Panel" (and, Remove) are presented with the same alignment, font size, etc, making them look like they all perform separate tasks. It's pretty confusing that one would select the second button on the list, and then understand that the button above it actually can be a sub-option of the second button. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462980] In Panel Edit Mode, "Maximize" button is inappropriately enabled while Panel is already maximized
https://bugs.kde.org/show_bug.cgi?id=462980 --- Comment #2 from Andrew Brouwers --- Ah, then I misunderstood. Because of the alignment and presentation of the buttons, I assumed "Maximize" meant "full width, no gaps" (ie, the normal/default layout, fully expanded). It's really confusing if "maximize" is actually an option of "floating," but the "Maximize" button exists above the "floating" button, with the same alignment, etc. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462781] Rework "Capture current popup" mode
https://bugs.kde.org/show_bug.cgi?id=462781 --- Comment #2 from Andrew Shark --- Not a problem. Here is what it goes: 1) Improving documentation is obvious, and also now spectacle has reworked interface. I hope docs will be improved anyway. 2) Make this mode work in Wayland. I thing this will be obvious when addressing Bug 463817. 3) Move this capture mode from Options to Areas. Created bug report Bug 463817 for this. 4) Add ability to capture several menu levels as a one area. When commented here https://bugs.kde.org/show_bug.cgi?id=462780#c2 I noticed that several levels of menu _are_ captured in those working apps like Cuttlefish. So I think this is already addressed, and disappearing menu in another apps like Dolphin is another issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 463817] New: Move the "Capture current pop-up only" to "Capture modes"
https://bugs.kde.org/show_bug.cgi?id=463817 Bug ID: 463817 Summary: Move the "Capture current pop-up only" to "Capture modes" Classification: Applications Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ash...@linuxcomp.ru CC: k...@david-redondo.de Target Milestone: --- Created attachment 155007 --> https://bugs.kde.org/attachment.cgi?id=155007=edit Suggested place of pop-up capture mode As suggested in https://bugs.kde.org/show_bug.cgi?id=462780#c1, taking screenshot of window should always include its popup. And the capture setting "Capture the current pop-up only" seems to be placed in wrong place. As it is determining an area of capturing, it should go to the selection mode buttons. See screenshot. STEPS TO REPRODUCE 1. Open main app window OBSERVED RESULT See that "Capture the current pop-up only" is in Capture Setting section and this is confusing. EXPECTED RESULT In the "Take a new screenshot" section another one button should be added for this (see screenshot). SOFTWARE/OS VERSIONS Spectacle 23.03.70 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462780] Child pop-ups of window not included in "Window Under Cursor" and "Active Window" capture modes
https://bugs.kde.org/show_bug.cgi?id=462780 --- Comment #2 from Andrew Shark --- Agree, I also think it is ok to always capture a window with menu and remove an option to disable this (of course user still has a way to avoid menu capturing by just escaping it before taking screenshot). I noticed that there are applications in which this _already_ works. For example in Cuttlefish and in Elisa capturing window with menu works. But other applications does not work this way. For example, Dolphin or Kate. Try to capture a window with menu. When cursor becomes aim shape to choose window, the popup disappears. May this be a QtWidgets vs QtQuick application problem? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463673] New: System Settings crashes when switching from Icon View to Sidebar View
https://bugs.kde.org/show_bug.cgi?id=463673 Bug ID: 463673 Summary: System Settings crashes when switching from Icon View to Sidebar View Classification: Applications Product: systemsettings Version: master Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: iconview Assignee: plasma-b...@kde.org Reporter: andrew1st...@gmail.com Target Milestone: --- Created attachment 154932 --> https://bugs.kde.org/attachment.cgi?id=154932=edit .kcrash file of crash Application: systemsettings (5.24.4) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.14.21-150400.24.38-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.4" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: In the System Settings application, I was switching from Icon View to List View. Before the switch was even able to occur, System Settings crashed. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 QWeakPointer::internalData (this=0x564830159a70) at ../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:698 #5 QPointer::data (this=0x564830159a70) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:77 #6 QPointer::operator QObject* (this=0x564830159a70) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:83 #7 QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x5649304c8020, event=event@entry=0x564930529550) at kernel/qcoreapplication.cpp:1183 #8 0x7fc44265a392 in QApplicationPrivate::notify_helper (this=this@entry=0x56492fe87a90, receiver=receiver@entry=0x5649304c8020, e=e@entry=0x564930529550) at kernel/qapplication.cpp:3626 #9 0x7fc4426611a0 in QApplication::notify (this=0x7ffcc9deb0b0, receiver=0x5649304c8020, e=0x564930529550) at kernel/qapplication.cpp:3156 #10 0x7fc44118ac23 in QCoreApplication::notifyInternal2 (receiver=0x5649304c8020, event=0x564930529550) at kernel/qcoreapplication.cpp:1064 #11 0x7fc44118adfe in QCoreApplication::sendEvent (receiver=receiver@entry=0x5649304c8020, event=event@entry=0x564930529550) at kernel/qcoreapplication.cpp:1462 #12 0x7fc44118d641 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x56492fe74480) at kernel/qcoreapplication.cpp:1821 #13 0x7fc44118dbc8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #14 0x7fc4411ed983 in postEventSourceDispatch (s=0x56492ff5ce60) at kernel/qeventdispatcher_glib.cpp:277 #15 0x7fc439aa082b in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #16 0x7fc439aa0bd0 in ?? () from /usr/lib64/libglib-2.0.so.0 #17 0x7fc439aa0c5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #18 0x7fc4411ed02c in QEventDispatcherGlib::processEvents (this=0x56492ff6c020, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #19 0x7fc44118948a in QEventLoop::exec (this=this@entry=0x7ffcc9deaf90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #20 0x7fc441192cc7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375 #21 0x56492e00da3e in main (argc=, argv=) at /usr/src/debug/systemsettings5-5.24.4-bp154.1.23.x86_64/app/main.cpp:183 [Inferior 1 (process 2250) detached] Possible duplicates by query: bug 463663, bug 463649, bug 463006, bug 462770, bug 462710. Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463499] no sound only for Konsole notifications
https://bugs.kde.org/show_bug.cgi?id=463499 Andrew changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrew --- It lasted for months and got fixed several days after I created this ticket :) Problem disappeared after update to Konsole 22.12, maybe some other components as well. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463570] New: External proxy documentation, configuration
https://bugs.kde.org/show_bug.cgi?id=463570 Bug ID: 463570 Summary: External proxy documentation, configuration Classification: Applications Product: kdenlive Version: 22.12.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Documentation Assignee: fritzib...@gmx.net Reporter: awchamp...@gmail.com Target Milestone: --- In the application preferences, kdenlive surfaces "GoPro LRV" as an option for proxy files. What it doesn't mention is that this is a profile expecting a specific convention, and that is saved to the project. The profile cannot be edited in-app. On at least one setting, Akaso cameras use a different convention: low and full-res videos differ only by extension, e.g. `/NORM0001.LRV` and `/NORM0001.MP4`. The GoPro preset doesn't recognize this, so Kdenlive creates a new proxy. Thanks to the developer documentation (https://community.kde.org/Kdenlive/Development/externalProxy), I was able to create a basic new profile: "Akaso LRV=./;;.LRV;./;;.MP4" and found two ways to hack it in: * per-project: manually edit the file property `kdenlive:docproperties.externalproxyparams`. * globally: open the `/Applications/kdenlive.app` bundle and manually edit `Contents/Resources/externalproxies.rc` At a bare minimum, I guess the user documentation should explain it? -- You are receiving this mail because: You are watching all bug changes.
[kscd] [Bug 222841] kscd often fails to begin playback when play button is pressed
https://bugs.kde.org/show_bug.cgi?id=222841 Andrew Munkres changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #9 from Andrew Munkres --- I tried building KsCD from source, using the kf5 branch in the https://invent.kde.org/multimedia/kscd.git Git repository), but it failed to compile: [ 38%] Building CXX object CMakeFiles/kscd.dir/mbmanager.cpp.o /home/amunkres/software/aur/kscd-git/src/kscd/mbmanager.cpp: In member function ‘void MBManager::discUpload(const QString&)’: /home/amunkres/software/aur/kscd-git/src/kscd/mbmanager.cpp:325:43: error: cannot convert ‘QString’ to ‘const QUrl&’ 325 | QDesktopServices::openUrl(url); | ^~~ | | | QString In file included from /usr/include/qt/QtGui/QDesktopServices:1, from /home/amunkres/software/aur/kscd-git/src/kscd/mbmanager.cpp:36: /usr/include/qt/QtGui/qdesktopservices.h:59:37: note: initializing argument 1 of ‘static bool QDesktopServices::openUrl(const QUrl&)’ 59 | static bool openUrl(const QUrl ); | ^~~ make[2]: *** [CMakeFiles/kscd.dir/build.make:197: CMakeFiles/kscd.dir/mbmanager.cpp.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:479: CMakeFiles/kscd.dir/all] Error 2 make: *** [Makefile:136: all] Error 2 (See also the comments at https://aur.archlinux.org/packages/kscd-git -- the AUR package maintainer encountered this same compilation error.) However, the KsCD project on invent.kde.org is currently in "archived" status (see https://invent.kde.org/groups/multimedia/-/archived ), which seems to indicate that KsCD is no longer maintained? If so, then I suppose there's no reason to keep this bug open. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463499] New: no sound only for Konsole notifications
https://bugs.kde.org/show_bug.cgi?id=463499 Bug ID: 463499 Summary: no sound only for Konsole notifications Classification: Applications Product: konsole Version: 22.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: travn...@gmail.com Target Milestone: --- Can't make Konsole playing sounds for notifications. What I do: * open Konsole window * go to "Settings" -> "Configure Notifications" * check "Play a sound" * select sound file. Example: /usr/share/sounds/alsa/Front_Center.wav or /usr/share/sounds/KDE-Im-Cant-Connect.ogg * press "play" (▶) button near the sound file name. It's just silent after this. If I open pavucontrol window and look at it while pressing ▶ — there is no activity at "Playback" tab in this case. Other notifications like "show popup message" and "mark taskbar entry" work fine. Note: it's Fedora 37 x86-64 installation updating by `dnf distro-sync` for years, so some configuration could be outdated. Have no other sound issues here. Konsole 22.08.3 KDE Frameworks 5.101.0 Qt 5.15.7 plasma-workspace-5.26.4.1-1.fc37.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 463315] New: Allow to choose a diff file from welcome window / Rework welcome window
https://bugs.kde.org/show_bug.cgi?id=463315 Bug ID: 463315 Summary: Allow to choose a diff file from welcome window / Rework welcome window Classification: Applications Product: kompare Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: ash...@linuxcomp.ru Target Milestone: --- When you launch Kompare on its own (not by clicking on a patch file in Dolphin), you see a welcome window. And that window does not allow you to choose a single diff/patch file. STEPS TO REPRODUCE 1. Open kompare from start menu 2. Observe the window you see OBSERVED RESULT The window shows you an interface (on the Files tab) that allows you to choose file 1 and file 2 to compare them. But there is no way to open a patch file itself. EXPECTED RESULT Ability to choose a diff or patch file on a separate tab at least. ADDITIONAL INFORMATION This window that is shown at start is actually a dialog that is shown when you choose menu "File" - "Compare Files". But there is also "File" - "Open Diff" entry. I suggest to add a nice welcome window, like for example in Ark, saying "Welcome to Kompare" and has two buttons: "Compare Files" and "Open Diff". And that dialog window for several files to be only shown when user actually selects "Compare Files". SOFTWARE/OS VERSIONS Kompare: 4.1.22120 -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 278665] Kompare text window doesnt continues activated
https://bugs.kde.org/show_bug.cgi?id=278665 Andrew Shark changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME CC||ash...@linuxcomp.ru --- Comment #1 from Andrew Shark --- In kompare 4.1.22120, there is a tool "Show Text View". And it keeps its presence on toolbar panel after restarting kompare. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 406826] When trying to compare two folders in KDE Plasma on the latest 19.04.0-1 version you cannot select two folders and right click and compare. If you have single click activated yo
https://bugs.kde.org/show_bug.cgi?id=406826 Andrew Shark changed: What|Removed |Added CC||ash...@linuxcomp.ru Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Andrew Shark --- Invalid bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 389766] Weather widget shows no temperature aside the icon in the plasma panel when I use wetter.com provider
https://bugs.kde.org/show_bug.cgi?id=389766 --- Comment #6 from Andrew Brouwers --- Also, if "wetterer" will never allow this to be possible, it might make sense to remove this as an option in the settings? It doesn't seem right to offer a feature that could never possibly work. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 389766] Weather widget shows no temperature aside the icon in the plasma panel when I use wetter.com provider
https://bugs.kde.org/show_bug.cgi?id=389766 --- Comment #5 from Andrew Brouwers --- Any thought to providing another backend, then? I think gnome uses met.no, for example. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463293] New: Small white dot in upper-left corner
https://bugs.kde.org/show_bug.cgi?id=463293 Bug ID: 463293 Summary: Small white dot in upper-left corner Classification: Applications Product: konsole Version: 22.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: abrouw...@gmail.com Target Milestone: --- Created attachment 154721 --> https://bugs.kde.org/attachment.cgi?id=154721=edit konsole screenshot SUMMARY I recently updated to 22.12.0, and noticed a small, white dot in the corner of my konsole window. STEPS TO REPRODUCE 1. Launch Konsole (running zsh if it matters) OBSERVED RESULT Small white dot - see screenshot SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.5 KDE Frameworks Version: 5.101.0 konsole: 22.12.0 Qt: 5.15.7+kde+r177 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 463273] New: Temp Display next to Icon doesn't work
https://bugs.kde.org/show_bug.cgi?id=463273 Bug ID: 463273 Summary: Temp Display next to Icon doesn't work Classification: Plasma Product: kdeplasma-addons Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Weather Assignee: plasma-b...@kde.org Reporter: abrouw...@gmail.com Target Milestone: --- Created attachment 154713 --> https://bugs.kde.org/attachment.cgi?id=154713=edit Settings SUMMARY The weather applet doesn't seem to work very well; I don't seem to get temp updates too frequently, though I suspend/wake my laptop somewhat frequently, so maybe the "30 minute update" minimum is too much (why can't this be lowered???). But mostly, clicking "Show Beside Icon" doesn't seem to do anything - see screenshot. STEPS TO REPRODUCE 1. Try to use weather applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462980] New: "Maximize" button doesn't work when trying to un-float panel
https://bugs.kde.org/show_bug.cgi?id=462980 Bug ID: 462980 Summary: "Maximize" button doesn't work when trying to un-float panel Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: abrouw...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Today, I tested the floating panel. Not liking it, I went to undo this; trying again to edit, I was presented with "Maximize," "Floating Panel" (which was highlighted/active), and the option to remove. Intuitively, I tried "Maximize" to return to a full-width panel. It LOOKS like I'm clicking a button, but takes no action. Instead, I had to click "Floating Panel" again, which made the maximize text/button active. Instead, I'd propose the "maximize" button actually do something, or remove the response when I click the text. STEPS TO REPRODUCE 1. Right click -> More Options -> Floating Panel 2. Right click -> More Options -> "Maximize" -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox
https://bugs.kde.org/show_bug.cgi?id=458494 --- Comment #4 from Andrew Brown --- No keep this ticket open and carry on. I have moved over to installing Firefox from launchpad or somewhere, but I would like to move back to snap as it seems the architected way to go with respect to Canonical. With all the things that were wrong with snap, though, I do think Canonical arranged what looked like a shotgun wedding between Mozilla and ubuntu. Best regards, Andrew Andrew Brown The Blackheath Art Club ☞ G.P.O. Film Unit<http://www.english-heritage.org.uk/visit/blue-plaques/g.p.o.-film-unit> / The Crown Film Unit<http://www.bfi.org.uk/films-tv-people/4ce2b941e0766/> From: Erik Sent: Sunday, December 11, 2022 8:54:59 PM To: Andrew J. Brown Subject: [plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox https://bugs.kde.org/show_bug.cgi?id=458494 --- Comment #3 from Erik --- Would it be possible to re-open this bug or should I create a new one? Browser Integration still doesn't seem to work with the Snap version of Firefox 107.0.1. Support for native messaging is added to the stable version of the snap now so therefore I expected Browser Integration to work as well. Got a prompt when starting Firefox to allow Plasma Browser Integration and I clicked OK. When inspecting from Firefox's about:debugging I see the following error message in the console: Uncaught (in promise) Error: Attempt to postMessage on disconnected port sendPortMessage moz-extension://f2a3fa37-c27f-4678-90f5-94eadb4bc46c/extension-utils.js:51 sendSettings moz-extension://f2a3fa37-c27f-4678-90f5-94eadb4bc46c/extension.js:45 -- You are receiving this mail because: You reported the bug. -- 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.
[Spectacle] [Bug 462781] New: Rework "Capture current popup" mode
https://bugs.kde.org/show_bug.cgi?id=462781 Bug ID: 462781 Summary: Rework "Capture current popup" mode Classification: Applications Product: Spectacle Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ash...@linuxcomp.ru CC: k...@david-redondo.de Target Milestone: --- 1) Improve documentation Currently, the documentation in Help menu says: that "Capture the current popup only" checkbox is available only for "Active Window" and "Window Under Cursor" areas. But it does not say that it is also unavailable when in Wayland session. I sent a letter to KDE Docs team about this. 2) Make this mode work in Wayland Because it is now disabled in wayland 3) Move this capture mode from Options to Areas. Because it is actually about choosing capture area. 4) Add ability to capture several menu levels as a one area Currently it selects one of the levels only. It is not what user may want. For example, see how Snagit (a WinOS commercial capture utility) works in this video: https://youtu.be/dfvUd0leElI?t=57 You can see that there are two menu levels opened, and at 1:03 shagit allows you to select an area of first menu level (it is outlined with orange dashed line). Unfortunately not shown on the video, it easily allows you to add second level to capture area, as well as selecting second level menu area alone. SOFTWARE/OS VERSIONS Spectacle: 22.08.3 See also Bug 462780 - ability to capture window including menu -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462780] New: Add option to capture window including the popup menu
https://bugs.kde.org/show_bug.cgi?id=462780 Bug ID: 462780 Summary: Add option to capture window including the popup menu Classification: Applications Product: Spectacle Version: 22.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: ash...@linuxcomp.ru CC: k...@david-redondo.de Target Milestone: --- Created attachment 154425 --> https://bugs.kde.org/attachment.cgi?id=154425=edit How interface with additional checkbox for window with popup could look Currently there is no standard way to capture window including its popup menus. The only way to do it now is capturing the rectangle area. For example, I captured this attachment https://bugs.kde.org/show_bug.cgi?id=462702#c3 manually. I wish such capture mode (window and also popups belonging to it) would be available. It can be added as another Area (Active window with menu) or as an additional checkbox (Include window popup menus) applicable to "Active Window" and "Window Under Cursor". I think the second one is more accurate. See screenshot of how it may look. So with such option it will be comfortable for user to control if he wants to capture windows with or without menus, and use standard shortcuts every time (Meta + PrtScr). SOFTWARE/OS VERSIONS Spectacle: 22.08.3 ADDITIONAL INFORMATION Snagit (a WinOS application) allows you to do such thing, see instruction here: https://support.techsmith.com/hc/en-us/articles/203731168-Capturing-a-Dropdown-Menu-in-Snagit-Windows -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 461719] The Akonadi server broke down after exiting the "Monitor Power Saving" mode
https://bugs.kde.org/show_bug.cgi?id=461719 --- Comment #3 from Andrew Rembrandt --- Created attachment 154418 --> https://bugs.kde.org/attachment.cgi?id=154418=edit New crash information added by DrKonqi akonadiserver (5.21.3 (22.08.3)) using Qt 5.15.7 When I plug in my Dell TB16 dock (with a second external monitor connected, and usb mouse + keyboard), this often occurs, along with what seems a crash or exit of all applications (I get a black / blank desktop with no plasmashell) Happy to provide more details & will hopefully find some time to get the other crashes reported in system journal: Dec 08 09:21:16 keaton systemd-coredump[23979]: [] Process 1085 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 1085: #0 0x7f109f347358 n/a (libkwin.so.5 + 0x347358) #1 0x7f109f192f4e n/a (libkwin.so.5 + 0x192f4e) #2 0x7f109f4489c6 n/a (libkwin.so.5 + 0x4489c6) #3 0x7f109f1ab2a9 _ZN4KWin6OutputD2Ev (libkwin.so.5 + 0x1ab2a9) #4 0x7f109f34bc6e _ZN4KWin9DrmOutputD0Ev (libkwin.so.5 + 0x34bc6e) #5 0x7f109f2e9e31 _ZN4KWin9Workspace13updateOutputsEv (libkwin.so.5 + 0x2e9e31) #6 0x7f109d8bda51 n/a (libQt5Core.so.5 + 0x2bda51) #7 0x7f109f3323b2 _ZN4KWin10DrmBackend13updateOutputsEv (libkwin.so.5 + 0x3323b2) #8 0x7f109f32c0bd _ZN4KWin10DrmBackend15handleUdevEventEv (libkwin.so.5 + 0x32c0bd) #9 0x7f109d8bda51 n/a (libQt5Core.so.5 + 0x2bda51) #10 0x7f109d8bf904 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2bf904) #11 0x7f109d8bfa48 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2bfa48) #12 0x7f109cf78b1c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x178b1c) #13 0x7f109d88cf98 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x28cf98) #14 0x7f109d8d690c _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 + 0x2d690c) #15 0x7f109d8d7a01 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d7a01) #16 0x556ba264db52 n/a (kwin_wayland + 0x12cb52) #17 0x7f109d88573c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28573c) #18 0x7f109d890269 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x290269) #19 0x556ba256e611 n/a (kwin_wayland + 0x4d611) #20 0x7f109c83c290 n/a (libc.so.6 + 0x23290) #21 0x7f109c83c34a __libc_start_main (libc.so.6 + 0x2334a) #22 0x556ba256fc95 n/a (kwin_wayland + 0x4ec95) Stack trace of thread 1141: #0 0x7f109c89c4b6 n/a (libc.so.6 + 0x834b6) #1 0x7f109c89ecd0 pthread_cond_wait (libc.so.6 + 0x85cd0) #2 0x7f109510799e n/a (iris_dri.so + 0x10799e) #3 0x7f10950baf8c n/a (iris_dri.so + 0xbaf8c) #4 0x7f10951078cc n/a (iris_dri.so + 0x1078cc) #5 0x7f109c89f8fd n/a (libc.so.6 + 0x868fd) #6 0x7f109c921a60 n/a (libc.so.6 + 0x108a60) Stack trace of thread 1144: #0 0x7f109c9140bf __poll (libc.so.6 + 0xfb0bf) #1 0x7f109b56d1ff n/a (libglib-2.0.so.0 + 0xac1ff) #2 0x7f109b515132 g_main_context_iteration (libglib-2.0.so.0 + 0x54132) #3 0x7f109d8d7c4c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d7c4c) #4 0x7f109d88573c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28573c) #5 0x7f109d6e721f _ZN7QThread4execEv (libQt5Core.so.5 + 0xe721f) #6 0x7f109e6c0370 n/a (libQt5Qml.so.5 + 0x2c0370) #7 0x7f109d6e42ea n/a (libQt5Core.so.5 + 0xe42ea) #8 0x7f109c89f8fd n/a (libc.so.6 + 0x868fd) #9 0x7f109c921a60 n/a (libc.so.6 + 0x108a60) -- Backtrace (Reduced): #6 std::default_delete::operator() (__ptr=0x111, this=) at /usr/include/c++/12.2.0/bits/unique_ptr.h:89 #7 std::unique_ptr >::~unique_ptr (this=, this=) at /usr/include/c++/12.2.0/bits/unique_ptr.h:396 #8 std::__new_allocator > >::destroy > > (__p=, this=0x7ffdad9bb178) at /usr/include/c++/12.2.0/bits/new_allocator.h:181 #9 std::allocator_traits > > >::destroy > > (__p=, __a=...) at /usr/include/c++/12.2.0/bits/alloc_traits.h:535 #10 std::vector >, std::allocator > > >::_M_erase (__position=..., this=0x7ffdad9bb178) at /usr/include/c++/12.2.0/bits/vector.tcc:181 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 461719] The Akonadi server broke down after exiting the "Monitor Power Saving" mode
https://bugs.kde.org/show_bug.cgi?id=461719 Andrew Rembrandt changed: What|Removed |Added CC||pub...@rembrandt.dev -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462702] Reimplement Window Actions from KHotkeys for Wayland
https://bugs.kde.org/show_bug.cgi?id=462702 --- Comment #5 from Andrew Shark --- Yes. Window Actions can run one of three things: arbitrary command, dbus command, simulate keyboard input. See screenshots. In Trigger tab you can choose when to trigger: window appears, window disappears, window looses focus, window gets focus. And you have a list of window match rules (by class, by title, by something called window role (I do not know what it is), by window type). How I used it. I created a rule that match steam games, and when window gets focus, run a command to change my physical monitor color preset to Game. And oppositely, when steam game looses focus, revert monitor preset to Comfort View (yellowish colors). My project is https://gitlab.com/AndrewShark/monitor-commander. The downside is that in trigger tab we do not have trigger by window changing monitor (see Bug 436062) and you have to make the same list of windows to match two times (for the gets focus and for the looses focus). I can agree that maybe such window actions module is not something to be in system settings. Also because of downsides I said above. I happily will implement it in my app/widget, but how can I do it? Is there something like I can listen to window actions from kwin (events like the window with such title just got focus and so on). What is the starting point of programming this? So the resolution of current bug will be Resolved Intentional, right? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462702] Reimplement Window Actions from KHotkeys for Wayland
https://bugs.kde.org/show_bug.cgi?id=462702 --- Comment #4 from Andrew Shark --- Created attachment 154417 --> https://bugs.kde.org/attachment.cgi?id=154417=edit Trigger tab and edit window match fields -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462702] Reimplement Window Actions from KHotkeys for Wayland
https://bugs.kde.org/show_bug.cgi?id=462702 --- Comment #3 from Andrew Shark --- Created attachment 154416 --> https://bugs.kde.org/attachment.cgi?id=154416=edit Create new window action -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 167585] size of edit in chat window shouldn't be so small
https://bugs.kde.org/show_bug.cgi?id=167585 --- Comment #5 from Andrew Belitsky --- Sorry, I can't check if it true or not anymore. чт, 8 дек. 2022 г., 03:00 Justin Zobel : > Justin Zobel changed bug 167585 > <https://bugs.kde.org/show_bug.cgi?id=167585> > What Removed Added > Status REPORTED NEEDSINFO > Resolution --- WAITINGFORINFO > > *Comment # 4 <https://bugs.kde.org/show_bug.cgi?id=167585#c4> on bug > 167585 <https://bugs.kde.org/show_bug.cgi?id=167585> from Justin Zobel > * > > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! > > -- > You are receiving this mail because: > >- You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
