[kdeconnect] [Bug 470165] Runs in background on Pixel watch with no notification, increases battery use
https://bugs.kde.org/show_bug.cgi?id=470165 felix changed: What|Removed |Added CC||timothy1...@protonmail.com --- Comment #1 from felix --- Having the same issue. There should be a button in the app to stop kdeconnect completely and permanently. Stopping it in the Apps settings just restarts it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 Felix changed: What|Removed |Added CC||lcz.l...@outlook.com Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Felix --- Faced the same problem here, the work around for me is to turn off the main monitor and turn it on again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427751] New: Brush outline gets stuck in position when the size is reduced to zero by the transfer curve
https://bugs.kde.org/show_bug.cgi?id=427751 Bug ID: 427751 Summary: Brush outline gets stuck in position when the size is reduced to zero by the transfer curve Product: krita Version: 4.4.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: felgut...@gmail.com Target Milestone: --- SUMMARY If you activate the curve for the size in a brush, and assign the time or fade parameter to it, setting the curve from more than 0 to 0 (for example to draw grass from the base towards the tips), the outline freezes when reached the end, staying as a point, where it has become the end of the stroke. Only append in Krita 4.0 with graphics canvas acceleration turned on, but if you turn off canvas acceleration, the ouline directly disappears (outline missing). STEPS TO REPRODUCE 1. In the brush size configuration, activate the time or fade parameter, set the curve to end at 0 2. make a stroke. 3. OBSERVED RESULT The outline stuck at final position with canvas graphic acceleration turned on, and outline missing with canvas acceleration turned off. EXPECTED RESULT that the outline follow the cursor or pen (in case you only use outline as me) with canvas acceleration turned on, and can see the outline with canvas acceleration turned off. SOFTWARE/OS VERSIONS Windows: 10 laptop hp i5, 16g ram, integrated graphic card UHD620. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427751] Brush outline gets stuck in position when the size is reduced to zero by the transfer curve
https://bugs.kde.org/show_bug.cgi?id=427751 --- Comment #1 from Felix --- Excuse me, only in 4.4 not in 4.3. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422267] Advanced color selector hue rotate affects saturation/value in 16 bit color space
https://bugs.kde.org/show_bug.cgi?id=422267 Felix changed: What|Removed |Added CC||felgut...@gmail.com --- Comment #2 from Felix --- I would like to add that it is not necessary to touch the color wheel. Directly the advanced color selector where the color is clicked, it selects a more saturated color from where it was selected. The rest of the selectors mark the correct color, even the same docker of the advanced color selector does, if the color was chosen from the advanced color selector of the pop_up. When the used selector is updated (be it the docker or the pop_up), for example, selecting another layer or reopening the pop_up (if this was the one used), the indicator circle will be placed in the correct position. forum thread: https://krita-artists.org/t/bug-with-advanced-color-selector-hue-in-16-bit-color-space/7557 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422267] Advanced color selector hue rotate affects saturation/value in 16 bit color space
https://bugs.kde.org/show_bug.cgi?id=422267 --- Comment #3 from Felix --- Sorry, this is the thread: https://krita-artists.org/t/advanced-colour-selector-bug/14202/22 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433079] On Wayland container windows created by XEmbedSNIProxy are not stacked below root window
https://bugs.kde.org/show_bug.cgi?id=433079 felix changed: What|Removed |Added CC||fel...@disroot.org --- Comment #26 from felix --- The Bug is still there. Happens with wire and beyond all reason. Is there some idea how to fix this Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-10-amd64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429612] New: Unable to delete a single reference image in Espanish (European) keyboard
https://bugs.kde.org/show_bug.cgi?id=429612 Bug ID: 429612 Summary: Unable to delete a single reference image in Espanish (European) keyboard Product: krita Version: 4.4.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: felgut...@gmail.com Target Milestone: --- SUMMARY It is not possible to delete a single reference image using the delete key in European keyboard (It seems that on American keyboards if it works correctly). STEPS TO REPRODUCE 1. Open a reference image, select it with the reference image tool active. Press supr (suprimir) button (equivalent to delete key). OBSERVED RESULT The image reference is not deleted. EXPECTED RESULT Have the reference image removed SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION thread of krita artist:https://krita-artists.org/t/unable-to-delete-a-single-reference-image/14369 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 429612] Unable to delete a single reference image in Espanish (European) keyboard
https://bugs.kde.org/show_bug.cgi?id=429612 --- Comment #2 from Felix --- No, I cannot erase entire vectors. I can only delete them node by node, using backspace (remove point default shortcut). I can delete layers, using shift + del (shift + del). I have noticed that if I change the remove layer shortcut, to simply delete (del), there is no warning that this shortcut is being used by another option (although it is also true that I have not found the possibility of changing the remove vector shortcut in that menu, only remove point). -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 433610] KDE PIM memory/CPU leak
https://bugs.kde.org/show_bug.cgi?id=433610 Felix changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Felix --- Yes, that fixed the problem. Thank you for the help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491992] New: Brush Outline
https://bugs.kde.org/show_bug.cgi?id=491992 Bug ID: 491992 Summary: Brush Outline Classification: Applications Product: krita Version: 5.2.4 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: felix.heitbr...@gmx.de Target Milestone: --- Created attachment 172819 --> https://bugs.kde.org/attachment.cgi?id=172819&action=edit White brush outline SUMMARY Brush outline can get invisible depending on the background STEPS TO REPRODUCE 1. Pick a brush outline color 2. Paint 3 stripes of colors: white, black and grey (50% black) OBSERVED RESULT The brush outline is visible on black and white but not on the 50% grey one because it gets the same color. The same is also true for other colors of the brush like for example if you pick a green color the brush outline might also get invisible. EXPECTED RESULT Brush outline on grey backgrounds should be white (or the selected color) SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491992] Brush Outline
https://bugs.kde.org/show_bug.cgi?id=491992 --- Comment #1 from Felix --- Created attachment 172820 --> https://bugs.kde.org/attachment.cgi?id=172820&action=edit Green outline -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 491992] Brush Outline
https://bugs.kde.org/show_bug.cgi?id=491992 --- Comment #3 from Felix --- Hey, thank you for the reply here are is my system info. Krita Version: 5.2.3 (git 68d178c) Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.19045 Pretty Productname: Windows 10 Version 2009 Product Type: windows Product Version: 10 Locale Languages: en_GB, en_Latn_GB, en_US, en, en_Latn_US C locale: C QLocale current: en-GB QLocale system: en-GB QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 1252 (ANSI - Latin I) OpenGL Info Vendor: "Google Inc. (NVIDIA)" Renderer: "ANGLE (NVIDIA, NVIDIA GeForce RTX 2080 Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.15.3734)" Driver version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Requested format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) GL version: 3.0 Supports deprecated functions false Is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: true Extensions: GL_EXT_draw_buffers_indexed GL_NV_fence GL_EXT_texture_type_2_10_10_10_REV GL_EXT_read_format_bgra GL_OES_packed_depth_stencil GL_CHROMIUM_bind_generates_resource GL_OES_compressed_ETC2_sRGB8_texture GL_ANGLE_texture_multisample GL_OES_element_index_uint GL_EXT_debug_label GL_ANGLE_provoking_vertex GL_ANGLE_base_vertex_base_instance GL_ANGLE_texture_compression_dxt5 GL_EXT_map_buffer_range GL_OES_draw_buffers_indexed GL_EXT_blend_minmax GL_NV_EGL_stream_consumer_external GL_OES_EGL_image GL_ANGLE_copy_texture_3d GL_ANGLE_robust_client_memory GL_OES_mapbuffer GL_OES_EGL_image_external GL_ANGLE_depth_texture GL_EXT_sRGB GL_NV_pack_subimage GL_OES_texture_half_float GL_OES_texture_float_linear GL_KHR_debug GL_EXT_texture_norm16 GL_OES_compressed_EAC_R11_unsigned_texture GL_EXT_debug_marker GL_ANGLE_pack_reverse_row_order GL_OES_texture_stencil8 GL_EXT_robustness GL_OES_standard_derivatives GL_ANGLE_multiview_multisample GL_CHROMIUM_lose_context GL_EXT_instanced_arrays GL_EXT_shader_texture_lod GL_OES_texture_border_clamp GL_EXT_texture_compression_rgtc GL_OES_compressed_ETC2_punchthroughA_RGBA8_texture GL_ANGLE_memory_size GL_OES_texture_npot GL_ANGLE_client_arrays GL_OES_vertex_array_object GL_ANGLE_instanced_arrays GL_EXT_multi_draw_indirect GL_ANGLE_framebuffer_blit GL_EXT_frag_depth GL_OVR_multiview GL_OES_compressed_ETC2_RGBA8_texture GL_EXT_EGL_image_external_wrap_modes GL_EXT_color_buffer_half_float GL_CHROMIUM_copy_compressed_texture GL_EXT_texture_compression_bptc GL_OES_compressed_ETC2_RGB8_texture GL_OES_draw_elements_base_vertex GL_EXT_color_buffer_float GL_AMD_performance_monitor GL_EXT_multisampled_render_to_texture GL_EXT_float_blend GL_EXT_texture_compression_dxt1 GL_OVR_multiview2 GL_OES_get_program_binary GL_OES_compressed_EAC_RG11_unsigned_texture GL_ANGLE_lossy_etc_decode GL_ANGLE_translated_shader_source GL_EXT_occlusion_query_boolean GL_OES_compressed_EAC_R11_signed_texture GL_EXT_draw_elements_base_vertex GL_OES_texture_half_float_linear GL_ANGLE_program_cache_control GL_EXT_texture_storage GL_EXT_unpack_subimage GL_OES_rgb8_rgba8 GL_OES_surfaceless_context GL_OES_compressed_EAC_RG11_signed_texture GL_OES_depth32 GL_ANGLE_texture_compression_dxt3 GL_EXT_blend_func_extended GL_EXT_disjoint_timer_query GL_NV_framebuffer_blit GL_CHROMIUM_copy_texture GL_EXT_texture_rg GL_KHR_parallel_shader_compile GL_EXT_draw_buffers GL_EXT_texture_filter_anisotropic GL_ANGLE_framebuffer_multisample
[kwin] [Bug 491576] New: Show osk button only works once
https://bugs.kde.org/show_bug.cgi?id=491576 Bug ID: 491576 Summary: Show osk button only works once Classification: Plasma Product: kwin Version: 6.1.4 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: virtual-keyboard Assignee: kwin-bugs-n...@kde.org Reporter: felix-...@niederer.dev Target Milestone: --- If the show on screen keyboard button is used in a application, it won't work again after the keyboard is dismissed, until another window is focused again. STEPS TO REPRODUCE 1. Switch to tablet mode 2. Open application that requires the show osk button (like vs code) 3. Open osk and dismiss it again 4. Opening osk again, will fail now 5. Switch to another application and back 6. Opening osk works again. OBSERVED RESULT On screen keyboard can't be opened all the time EXPECTED RESULT On screen keyboard can be opened all the time SOFTWARE/OS VERSIONS Operating System: NixOS 24.11 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.6.44 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491576] Show osk button only works once
https://bugs.kde.org/show_bug.cgi?id=491576 --- Comment #1 from Felix --- May be a nixos issue, since it comes with the error message: Aug 11 23:34:19 nixos plasmashell[2379]: file:///nix/store/44da1wkw0zbks5makdcd9awp62ls385i-plasma-workspace-6.1.4/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:60: TypeError: Property 'pressed' of object QQuickMouseArea(0x561ace0) is not a function -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 491576] Show osk button only works once
https://bugs.kde.org/show_bug.cgi?id=491576 --- Comment #3 from Felix --- Yes, this works in applications where taping the text field brings up the virtual keyboard. But I am talking about applications where the virtual keyboard does not appear automatically, like VS code or Google Chrome. In this case, the button to show the virtual keyboard has to be used. (it only appears in such applications) But this button does not work after the keyboard was once dismissed; tapping it again results in the above-mentioned error message. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462267] New: KWin tabbox should not make the X server leak "/memfd:xshmfence" filedescriptors until the X server becomes unusable due to exhausted filedescriptors.
https://bugs.kde.org/show_bug.cgi?id=462267 Bug ID: 462267 Summary: KWin tabbox should not make the X server leak "/memfd:xshmfence" filedescriptors until the X server becomes unusable due to exhausted filedescriptors. Classification: Plasma Product: kwin Version: 5.26.3 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: felix+bugs.kde@ferey.de Target Milestone: --- SUMMARY Each showing of the task switcher window makes the X server leak resources, overloading it over time. STEPS TO REPRODUCE 1. Run KWin on X11 on Linux. 2. Observe the number of open filedescriptors of the X server which refer to "/memfd:xshmfence", e.g. using "ls -la /proc/"$(pidof X)"/fd | grep "/memfd:xshmfence" | wc -l". Note this number. For example, the number is 157. 3. Hold the left "alt" key. Press and release the "tab" key. Wait until the task switcher window (it does not matter which style of task switcher window you have configured, the problem seems to appear for any task switcher window style). Then release the left "alt" key. 4. Observe the number of open filedescriptors of the X server which refer to "/memfd:xshmfence" again, e.g. using "ls -la /proc/"$(pidof X)"/fd | grep "/memfd:xshmfence" | wc -l". Note this number, too. 5. Repeat step 3. 6. Repeat step 4. OBSERVED RESULT It can be observed that the number of "xshmfence"-filedescriptors increased each time the task switcher window was shown. The observed increase in the number of filedescriptors is sometimes by +1, sometimes by +2 per task switcher window show. If sufficiently many shows of task switcher windows happen, then the limited number of filedescriptors of the X server process (usually 1024) is exhausted. After that, the KDE desktop becomes completely unusable and a restart of the X server becomes necessary, loosing all the current open work. Depending on user behavior, this may take some hours or days to happen. It may never happen for users who do not use the task switcher. It does not happen if the user is always fast enough when using the Alt+Tab shortcut such that the task switcher window is never shown. EXPECTED RESULT It is expected that the number of "xshmfence"-filedescriptors does not increase each time the task switcher window is shown. If sufficiently many task switcher windows are shown, the limited number of filedescriptors of the X server process (usually 1024) should not be exhausted. The KDE desktop should not become completely unusable. A restart of the X server should not become necessary. SOFTWARE/OS VERSIONS Linux Kernel: 6.0.9 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.1 Qt Version: 5.15.7 ADDITIONAL INFORMATION The bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018176 is probably the same. Bug 443990 may be related. This bug exists despite the fix to bug 406303. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462267] KWin tabbox should not make the X server leak "/memfd:xshmfence" filedescriptors until the X server becomes unusable due to exhausted filedescriptors.
https://bugs.kde.org/show_bug.cgi?id=462267 Felix changed: What|Removed |Added CC||felix+bugs.kde@ferey.de -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 433610] New: KDE PIM memory/CPU leak
https://bugs.kde.org/show_bug.cgi?id=433610
Bug ID: 433610
Summary: KDE PIM memory/CPU leak
Product: kontact
Version: 5.16.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: felicitusn...@vivaldi.net
Target Milestone: ---
SUMMARY
The entire KDE PIM GUI application suite leaks memory and CPU time as it is
running.
STEPS TO REPRODUCE
1. Start any Kontact process (kontact, kmail, akregator...)
OBSERVED RESULT
The process will start running at 100% or more CPU time. Memory usage will also
increase by up to ~35 MB per second. These are observable through the top
terminal tool.
Running the application in terminal will also output this message continuously:
[671057:671057:0225/{timestamp}:ERROR:network_service_instance_impl.cc(286)]
Network service crashed, restarting service.
Closing the application when it was run in terminal will also output this
message (multiple times for kontact):
kf.xmlgui: 0x5641a2dc9ad8 deleted without having been removed from the factory
first. This will leak standalone popupmenus and could lead to crashes.
EXPECTED RESULT
The program runs normally and does not leak CPU time or RAM.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux, updated to 2021-02-25, kernel 5.11.1
KDE Plasma Version: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION
The version of Kontact/KDE PIM being used is 5.16.2 (20.12.2), as is currently
available in official Portage. This version was not listed in the version
selector on the submission form.
emerge --info:
Portage 3.0.15 (python 3.8.8-final-0,
default/linux/amd64/17.1/desktop/plasma/systemd, gcc-10.2.0, glibc-2.32-r7,
5.11.1-gentoo x86_64)
=
System uname:
Linux-5.11.1-gentoo-x86_64-Intel-R-_Core-TM-_i7-8700K_CPU_@_3.70GHz-with-glibc2.2.5
KiB Mem:16321716 total,497456 free
KiB Swap: 20971516 total, 20969212 free
Timestamp of repository gentoo: Thu, 25 Feb 2021 17:00:01 +
Head commit of repository gentoo: 644ced449c9ced1c0aeae1bd7aa92acb9ab2e522
Head commit of repository megazeux: e1413e83aacaf6319057d3a9bbb8a1bee0486a9f
sh bash 5.1_p4
ld GNU ld (Gentoo 2.35.2 p1) 2.35.2
app-shells/bash: 5.1_p4::gentoo
dev-java/java-config: 2.3.1::gentoo
dev-lang/perl:5.32.1::gentoo
dev-lang/python: 2.7.18_p7::gentoo, 3.7.10::gentoo, 3.8.8::gentoo,
3.9.2::gentoo
dev-util/cmake: 3.19.6::gentoo
dev-util/pkgconfig: 0.29.2::gentoo
sys-apps/baselayout: 2.7-r1::gentoo
sys-apps/sandbox: 2.20::gentoo
sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r5::gentoo
sys-devel/automake: 1.16.3-r1::gentoo
sys-devel/binutils: 2.35.2::gentoo
sys-devel/gcc:10.2.0-r5::gentoo
sys-devel/gcc-config: 2.3.3::gentoo
sys-devel/libtool:2.4.6-r6::gentoo
sys-devel/make: 4.3::gentoo
sys-kernel/linux-headers: 5.11::gentoo (virtual/os-headers)
sys-libs/glibc: 2.32-r7::gentoo
Repositories:
gentoo
location: /usr/portage
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-verify-jobs: 1
sync-rsync-verify-max-age: 24
sync-rsync-verify-metamanifest: yes
sync-rsync-extra-opts:
megazeux
location: /var/db/repos/megazeux
sync-type: git
sync-uri: https://github.com/Spectere/megazeux-overlay.git
masters: gentoo
anomen
location: /var/lib/layman/anomen
masters: gentoo
priority: 50
bobwya
location: /var/lib/layman/bobwya
masters: gentoo
priority: 50
jm-overlay
location: /var/lib/layman/jm-overlay
masters: gentoo
priority: 50
pentoo
location: /var/lib/layman/pentoo
masters: gentoo
priority: 50
snapd
location: /var/lib/layman/snapd
masters: gentoo
priority: 50
sorrow
location: /var/lib/layman/sorrow
masters: gentoo
priority: 50
thegreatmcpain
location: /var/lib/layman/thegreatmcpain
masters: gentoo bobwya
priority: 50
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="@FREE Oracle-BCLA-JavaSE Vivaldi ValveSteamLicense NVIDIA-r2
all-rights-reserved MPEG-4 linux-fw-redistributable openssl Snes9x"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/angband/gamedata/ /etc/ca-certificates.conf
/etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release
/etc/php/apache2-php7.4/ext-active/ /etc/php/cgi-php7.4/ext-active/
/etc/php/cli-php7.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d
/etc/terminfo"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB
PERL5
[kontact] [Bug 433610] KDE PIM memory/CPU leak
https://bugs.kde.org/show_bug.cgi?id=433610 --- Comment #2 from Felix --- Created attachment 136443 --> https://bugs.kde.org/attachment.cgi?id=136443&action=edit valgrind --leak-check=full --show-leak-kinds=all -s kontact Please note that I have not used Valgrind before, so I'm mostly just going by the suggestions made by the program itself as far as flags used. Please let me know if you need more or different information. -- You are receiving this mail because: You are watching all bug changes.
[kmplayer] [Bug 412422] kmplayer crashes right on start
https://bugs.kde.org/show_bug.cgi?id=412422 --- Comment #2 from Felix --- (In reply to Christoph Feck from comment #1) > Are you using a Wayland session? Indeed, I was. Felix -- You are receiving this mail because: You are watching all bug changes.
[kmplayer] [Bug 412422] New: kmplayer crashes right on start
https://bugs.kde.org/show_bug.cgi?id=412422
Bug ID: 412422
Summary: kmplayer crashes right on start
Product: kmplayer
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: koos.vrie...@gmail.com
Reporter: fe...@kngnt.org
Target Milestone: ---
Application: kmplayer ("0.12.0b")
Qt Version: 5.13.1
Frameworks Version: 5.62.0
Operating System: Linux 5.3.1-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages
-- Information about the crash:
I have just installed kmplayer and mplayer on arch linux. Then, I have tried to
start kmplayer, to only get a segfault.
The crash can be reproduced every time.
-- Backtrace:
Application: KMPlayer (kmplayer), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7ae82e5e80 (LWP 23911))]
Thread 3 (Thread 0x7f7ad700 (LWP 23914)):
#0 0x7f7aec00e415 in pthread_cond_wait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1 0x7f7ae4ac9f5c in ?? () from /usr/lib/dri/i965_dri.so
#2 0x7f7ae4ac9b58 in ?? () from /usr/lib/dri/i965_dri.so
#3 0x7f7aec00857f in start_thread () from /usr/lib/libpthread.so.0
#4 0x7f7aeee050e3 in clone () from /usr/lib/libc.so.6
Thread 2 (Thread 0x7f7ae6c7c700 (LWP 23912)):
#0 0x7f7aeedfa667 in poll () from /usr/lib/libc.so.6
#1 0x7f7aeb496130 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x7f7aeb496201 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3 0x7f7aed4f9a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4 0x7f7aed4a04ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5 0x7f7aed2d2385 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6 0x7f7aecad9b37 in ?? () from /usr/lib/libQt5DBus.so.5
#7 0x7f7aed2d35b0 in ?? () from /usr/lib/libQt5Core.so.5
#8 0x7f7aec00857f in start_thread () from /usr/lib/libpthread.so.0
#9 0x7f7aeee050e3 in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7f7ae82e5e80 (LWP 23911)):
[KCrash Handler]
#6 0x7f7aecee7148 in xcb_get_setup () from /usr/lib/libxcb.so.1
#7 0x7f7aeecba6d7 in KMPlayer::ViewArea::syncVisual() () from
/usr/lib/libkmplayercommon.so
#8 0x7f7aeecbc267 in KMPlayer::ViewArea::timerEvent(QTimerEvent*) () from
/usr/lib/libkmplayercommon.so
#9 0x7f7aed4ce3e5 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#10 0x7f7aede9f08b in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7f7aede5b4f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#12 0x7f7aede64e11 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#13 0x7f7aed4a19c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x7f7aed4f8d9d in QTimerInfoList::activateTimers() () from
/usr/lib/libQt5Core.so.5
#15 0x7f7aed4f9632 in ?? () from /usr/lib/libQt5Core.so.5
#16 0x7f7aeb4943ae in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#17 0x7f7aeb4961c1 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x7f7aeb496201 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#19 0x7f7aed4f9a03 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#20 0x7f7aed4a04ec in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#21 0x7f7aed4a8326 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#22 0x7f7aeef02c70 in kdemain () from /usr/lib/libkdeinit5_kmplayer.so
#23 0x7f7aeed2fee3 in __libc_start_main () from /usr/lib/libc.so.6
#24 0x55ae427b805e in _start ()
[Inferior 1 (process 23911) detached]
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 --- Comment #15 from Felix --- HI, I don't know if something was changed, but in my case the reason I made the post is almost gone. Now at least the zoom is already usable. But in effect, as Lempikq comments, it still gets stuck when instant preview is used, and only if the canvas is more than 1000 pixels or so. The user interface in my case does not seem to affect me, it works the same in full screen as without it. By the way, I tried it in 3.0, although the 2.8 worked the same for me. Greetings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414576] Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 --- Comment #16 from Felix --- In my case I have to say, that the problem is not as big as it was at the beginning, but I have checked it, and in fact this is not repeated in Krita 4.2.7. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414576] New: Zoom failure in 4.2.8 but not in 4.2.7.
https://bugs.kde.org/show_bug.cgi?id=414576 Bug ID: 414576 Summary: Zoom failure in 4.2.8 but not in 4.2.7. Product: krita Version: 4.2.8 Platform: Windows CE OS: Windows CE Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: felgut...@gmail.com Target Milestone: --- SUMMARY Zoom failure in 4.2.8 but not in 4.2.7. STEPS TO REPRODUCE In Krita 4.2.8 (or beta) press shift and space bar and drag whit pen in the tablet. OBSERVED RESULT The zoom does not work correctly. It gets stuck and only sometimes updates the movement when lifting the pencil (or something like that, it's a bit random). EXPECTED RESULT That the zoom works just like in Krita 4.2.7 SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION Hardware: Hp, with an i7 cpu, integrated UHD 620 card and 16 gigabytes of ram Checked in beta and stable version. With 4.2.7 and 4.2.8 installed and then only with 4.2.8 installed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394110] Unable to render animation
https://bugs.kde.org/show_bug.cgi?id=394110 Felix changed: What|Removed |Added CC||felix.s.schind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394538] Animation will not render
https://bugs.kde.org/show_bug.cgi?id=394538 Felix changed: What|Removed |Added CC||felix.s.schind...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397900] New: Animation render Fail
https://bugs.kde.org/show_bug.cgi?id=397900 Bug ID: 397900 Summary: Animation render Fail Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: felix.s.schind...@gmail.com Target Milestone: --- Created attachment 114622 --> https://bugs.kde.org/attachment.cgi?id=114622&action=edit These aure the Informaition output after failing. I want to Render an short animation. Saving frames works but it failed to convert the image Sequence. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391061] New: On the Net worth report, when range is set to "all dates", many consecutive months show 30E9€ (which, unfortunately, I do not have)
https://bugs.kde.org/show_bug.cgi?id=391061 Bug ID: 391061 Summary: On the Net worth report, when range is set to "all dates", many consecutive months show 30E9€ (which, unfortunately, I do not have) Product: kmymoney Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: reports Assignee: kmymoney-de...@kde.org Reporter: fe...@kngnt.org Target Milestone: --- When selecting "all dates" in the net worth report, I have a point for the first month with correct values, then 24 months with 30E9 €, and then the series comes back to normality. I have checked that there are no weird transactions during the first two months, but there are only 4 and look pretty normal (as in the openning of an account, the openning of a brokerage+investments account and two transactions on each). -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391061] On the Net worth report, when range is set to "all dates", many consecutive months show 30E9€ (which, unfortunately, I do not have)
https://bugs.kde.org/show_bug.cgi?id=391061 Felix changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Felix --- (In reply to Thomas Baumgart from comment #1) > Do you have valid price information for the investments? Indeed! that was it! for a reason I do not understand, Yahoo had reported the price to be astronomically high for one of the shares (NOKIA). Thank you!! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391959] New: Patch 1c908e6 should be backported to 5.0.0
https://bugs.kde.org/show_bug.cgi?id=391959 Bug ID: 391959 Summary: Patch 1c908e6 should be backported to 5.0.0 Product: kmymoney Version: 5.0.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: fe...@kngnt.org Target Milestone: --- Bug 390834 (related to the inability of accepting scheduled entries from the ledger) was fixed by patch 1c908e6, which will be released with 5.0.1 stable. This is a major usability issue, as not being able to work as with the previous versions forces the user to go back and forth between the ledger and the scheduled entries tab. Can this patch be included in the 5.0.0 branch? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391959] Patch 1c908e6 should be backported to 5.0.0
https://bugs.kde.org/show_bug.cgi?id=391959 --- Comment #2 from Felix --- (In reply to Thomas Baumgart from comment #1) > To clarify a few things, there is no such thing as the 5.0.0 branch. > > 5.0.0 is a release and the number is fixed and will never change. > Nevertheless, 5.0.0 marks the starting point of the 5.0 branch, which > received a bunch of fixes (as the one you mention). The next maintenance > release will be drawn from the tip of this branch, will be named 5.0.1 and, > as you can figure out by now, will contain the fix without doubt. It's then > up to the packagers to create updates for distro specific packages. Then, question: should I just locally apply the patch and recompile the package (in my case, for Arch linux), or would be seen as acceptable contacting the packager to include this specific commit? Thank you for your time, by the way. I really appreciate your efforts and software. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390834] Scheduled transactions: "Enter next transaction" should be available in ledger
https://bugs.kde.org/show_bug.cgi?id=390834 Felix changed: What|Removed |Added CC||fe...@kngnt.org --- Comment #1 from Felix --- I am having exactly the same problem, and is very annoying: I have about 30 scheduled transactions and going to "Scheduled transactions" after seeing them in the ledger, to have them entered and then return to the ledger is not handy at all. As this is a functionality rather basic that is missing, can the Importance be changed to "Major"? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390834] Scheduled transactions: "Enter next transaction" should be available in ledger
https://bugs.kde.org/show_bug.cgi?id=390834 Felix changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 Felix changed: What|Removed |Added CC||felixbuett...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 377084] WebEnginePart does not render kio output (kio_help, kio_man, ...)
https://bugs.kde.org/show_bug.cgi?id=377084 Felix changed: What|Removed |Added CC||fe...@enqueue.eu -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 354130] Telepathy can't connect to a Jabber account anymore
https://bugs.kde.org/show_bug.cgi?id=354130 Felix changed: What|Removed |Added CC||fe...@enqueue.eu --- Comment #28 from Felix --- I am facing the same issue: Telepathy cannot connect to the ejabberd service. It looks to me like the fallback to the PLAIN authentication method never takes place. However, I am not competent enough to judge whether this error is in ktp-auth-handler or gabble. Let me know if you need any debug output. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 370352] system hangs when waking up from screen off with a blank screen with mouse pointer
https://bugs.kde.org/show_bug.cgi?id=370352 Felix Miata changed: What|Removed |Added CC||mrma...@earthlink.net --- Comment #7 from Felix Miata --- (In reply to Martin Gräßlin from comment #1) > First of all: if you are using Intel > hardware please switch from xorg-intel to xorg-modesettings driver and check > whether the problem persists. Beginning with server 1.17.0, the separate modesetting driver package was eliminated and the driver incorporated into the server. To switch to the modesetting driver in distro releases providing 1.17.0 or newer, simply uninstall the intel driver package and restart the server. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370156] digital clock font is tiny since plasma 5.8.0
https://bugs.kde.org/show_bug.cgi?id=370156 Felix Miata changed: What|Removed |Added CC||mrma...@earthlink.net --- Comment #16 from Felix Miata --- downstream bug https://bugzilla.opensuse.org/show_bug.cgi?id=1007706 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449777] Parent menu disappears when a submenu opens
https://bugs.kde.org/show_bug.cgi?id=449777 --- Comment #4 from Felix Ernst --- (In reply to Vlad Zahorodnii from comment #1) >Moving to dolphin. Patrick Silva says he "can reproduce this bug with menus of Dolphin, Konsole, Ark, Gwenview and Kate." >If dolphin doesn't hide it, then it's definitely a qtwayland bug. I don't think Dolphin hides it. I am not aware of anything interesting happening in the menu bar menus of Dolphin and I also did a crude search to confirm. It kind of looks like the disappearing of the tooltip triggers the destruction of the menus. The hiding happens here https://invent.kde.org/frameworks/kxmlgui/-/blob/master/src/ktooltiphelper.cpp#L150 but that shouldn't have any side-effects. There hasn't been any non-style changes in that file for 7 month anyway so I don't think that's the issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 449179] Visual bugs during zoom animation
https://bugs.kde.org/show_bug.cgi?id=449179 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/syst ||em/dolphin/commit/a05343530 ||d0f434347158889020675123090 ||98ce --- Comment #6 from Felix Ernst --- Git commit a05343530d0f43434715888902067512309098ce by Felix Ernst, on behalf of Eugene Popov. Committed on 13/02/2022 at 12:16. Pushed by felixernst into branch 'master'. Fix zooming animation Current implementation of the zooming animation is a bit buggy. This MR fixes the following issues: * in the Icon view mode, the icons sometimes "jump" * in the Compact view mode, the labels sometimes are cut off M +11 -12 src/kitemviews/kitemlistview.cpp M +27 -2src/kitemviews/kitemlistwidget.cpp M +11 -0src/kitemviews/kitemlistwidget.h M +23 -21 src/kitemviews/kstandarditemlistwidget.cpp M +1-0src/kitemviews/kstandarditemlistwidget.h M +8-0src/kitemviews/private/kitemlistviewanimation.cpp M +3-3src/kitemviews/private/kitemlistviewanimation.h https://invent.kde.org/system/dolphin/commit/a05343530d0f43434715888902067512309098ce -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436648] Switching monitor input from one connector type to another loses containment mapping/screen setup
https://bugs.kde.org/show_bug.cgi?id=436648 Felix Miata changed: What|Removed |Added CC||mrma...@earthlink.net --- Comment #13 from Felix Miata --- (In reply to Nate Graham from comment #6) > Ideally we could identify screens purely UUIDs or something less volatile > than a thing that includes the connector type. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453172] Revise wording for "Leading Column Padding"
https://bugs.kde.org/show_bug.cgi?id=453172 Felix Ernst changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/dolphin/commit/ca0d0bb32 ||2925e2119f13f76d8e9643d24cb ||f3e0 --- Comment #3 from Felix Ernst --- Git commit ca0d0bb322925e2119f13f76d8e9643d24cbf3e0 by Felix Ernst, on behalf of Jin Liu. Committed on 26/05/2022 at 08:31. Pushed by felixernst into branch 'master'. Change wording "Leading Column Padding" to "Side Padding" Since it actually adds padding on both left and right sides, "Side Padding" might be more accurate. This change is also propagated to variable and method names. M +2-2doc/index.docbook M +3-0src/CMakeLists.txt M +7-7src/kitemviews/kitemlistheader.cpp M +3-3src/kitemviews/kitemlistheader.h M +9-9src/kitemviews/kitemlistview.cpp M +1-1src/kitemviews/kitemlistview.h M +7-7src/kitemviews/kitemlistwidget.cpp M +4-4src/kitemviews/kitemlistwidget.h M +6-6src/kitemviews/kstandarditemlistwidget.cpp M +1-1src/kitemviews/kstandarditemlistwidget.h M +19 -19 src/kitemviews/private/kitemlistheaderwidget.cpp M +5-5src/kitemviews/private/kitemlistheaderwidget.h M +2-2src/settings/dolphin_detailsmodesettings.kcfg A +8-0src/settings/dolphin_detailsmodesettings.upd M +1-1src/views/dolphinitemlistview.cpp M +10 -10 src/views/dolphinview.cpp M +1-1src/views/dolphinview.h https://invent.kde.org/system/dolphin/commit/ca0d0bb322925e2119f13f76d8e9643d24cbf3e0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453046] Line selection: The blueish selection background may start later in case of smaller preview icons
https://bugs.kde.org/show_bug.cgi?id=453046 Felix Ernst changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/commit/58622f431 ||b0d7d347333a4bc7b2f57fe1787 ||8f9d Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Felix Ernst --- Git commit 58622f431b0d7d347333a4bc7b2f57fe17878f9d by Felix Ernst, on behalf of Travis Burrows. Committed on 26/05/2022 at 12:38. Pushed by felixernst into branch 'master'. Extend selection rectangle to left edge This commit changes it so the sizes of selection rectangles and hover highlights in compact and details view mode is identical for all items. Before this commit, selection rectangles in lists would have varying indentation of the left edge of the selection rectangle depending on the preview image's width-to-height ratio. This would cause a sort of "ragged edge" in both compact and details list view when multiple items were selected. This commit doesn't change anything about icon view mode. M +10 -1src/kitemviews/kstandarditemlistwidget.cpp https://invent.kde.org/system/dolphin/commit/58622f431b0d7d347333a4bc7b2f57fe17878f9d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 --- Comment #16 from Felix Ernst --- Git commit 5ebf2065d525160a29f1d7aeef41541c6033bccf by Felix Ernst. Committed on 16/06/2022 at 09:11. Pushed by felixernst into branch 'master'. Don't consider drops on a row as drops on the row's item Since d3839617193e92463806580699caa595c892b8a6 in details view mode clicking anywhere within the row is considered a click on the item. That commit also changed it so that dropping files anywhere inside a row would make it so the files are received by the folder of that row. This commit reverts the drop behaviour to be identical to the old one. I am having trouble explaining why this is better because one can look at it in different ways. Bottom line is that one doesn't really feel like one is dropping files inside a folder unless the mouse cursor is actually directly above a folder's icon or name. Another argument is that it is normal behaviour to just throw files onto an application and the files then being opened by it. Having potentially large parts of the view area covered by the rows of folders means that there has to be more of a conscious effort to not drop the files inside one of the folders by accident while with this commit one has to aim precisely onto a folder to do it intentionally. M +22 -2src/kitemviews/kitemlistcontroller.cpp M +9-0src/kitemviews/kitemlistcontroller.h https://invent.kde.org/system/dolphin/commit/5ebf2065d525160a29f1d7aeef41541c6033bccf -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455548] New: White artifacts around rounded corners when using dark theme (similar to korners bug) + when animating
https://bugs.kde.org/show_bug.cgi?id=455548 Bug ID: 455548 Summary: White artifacts around rounded corners when using dark theme (similar to korners bug) + when animating Product: lattedock Version: 0.10.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: fischerfeli...@gmail.com Target Milestone: --- Created attachment 149888 --> https://bugs.kde.org/attachment.cgi?id=149888&action=edit Video of the dock in motion, corners can be seen on bottom & top dock SUMMARY When using a dark theme (Breeze dark with accent color tint in my case) and looking at a dock with rounded corners in front of a dark background, you notice a couple of white pixels outside the corner radius. Similarly, when the dock is moving (i.e. because of the parabolic effect or when auto-hiding) white can be seen on the leading edge, so when animating up from the bottom of the screen (previously hidden) a strip of white is in front. STEPS TO REPRODUCE 1. Install latest version of latte dock (on arch community/latte-dock 0.10.8-1) 2. set up 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455548] White artifacts around rounded corners when using dark theme (similar to korners bug) + when animating
https://bugs.kde.org/show_bug.cgi?id=455548 --- Comment #1 from Felix Fischer --- Messed up and accidentally pressed enter before finishing the bug report, so I'll post the rest here (can't find a way to edit original post). STEPS TO REPRODUCE 1. Install latest version of latte dock (on arch community/latte-dock 0.10.8-1) 2. set up dock with rounded corners using dark theme in front of dark background 3. inspect corners and move dock (auto-hide) OBSERVED RESULT White edges when moving, white pixels just outside the rounded corners EXPECTED RESULT Dock animates "in one piece" and rounded corners are clean SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux latest stable packages (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION I can confirm that this is caused by the contrast effect, as disabling it in Desktop Effects removes both problems. I believe it could be solved by shrinking the mask for the contrast effect a bit, so there is a small margin for error. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455548] White artifacts around rounded corners when using dark theme (similar to korners bug) + when animating
https://bugs.kde.org/show_bug.cgi?id=455548 --- Comment #2 from Felix Fischer --- Created attachment 149889 --> https://bugs.kde.org/attachment.cgi?id=149889&action=edit same tests as in first video with contrast effect disabled -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455540] Unable to download from Settings with error "invalid number of concurrent streams"
https://bugs.kde.org/show_bug.cgi?id=455540 Felix Fischer changed: What|Removed |Added CC||fischerfeli...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455548] white artifacts around rounded corners when using dark theme (similar to korners bug) + when animating
https://bugs.kde.org/show_bug.cgi?id=455548 --- Comment #4 from Felix Fischer --- 1. You're right, when using a floating plasma panel I can see exactly the same 2. The reason I was experiencing the issue just now is that I switched back to breeze from layan (https://github.com/vinceliuice/Layan-kde) which does not show any of what I described (also not on the plasma panel) 3. I doubt that the issue with the animations is my system. It certainly is not the fastest, but I run a Ryzen 5 3600 and a Radeon RX 5500XT, so if a faster computer is required in order to run latte smoothly, that would mean everyone would need a high end pc. What could be done differently in layan that it does not show any of the issues? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455540] Unable to download from Settings with error "invalid number of concurrent streams"
https://bugs.kde.org/show_bug.cgi?id=455540 --- Comment #10 from Felix Fischer --- Can confirm that just today on arch extra/qt5-base got an update to 5.15.5+kde+r163-1 that fixed it -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 455605] New: Add search on "Enter Bug" page
https://bugs.kde.org/show_bug.cgi?id=455605 Bug ID: 455605 Summary: Add search on "Enter Bug" page Product: bugs.kde.org Version: unspecified Platform: Other OS: All Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: fischerfeli...@gmail.com CC: she...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** It would be nice if there was a search bar on https://bugs.kde.org/enter_bug.cgi, as it is quite annoying to have to scroll through the page to find the product you are trying to submit a bug report for. I know you can ctrl +f, but it seems like a trivial thing to do. STEPS TO REPRODUCE 1. go to https://bugs.kde.org/enter_bug.cgi OBSERVED RESULT No search for product present EXPECTED RESULT Search for product present -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 455607] New: Use system colour schemes for konsole
https://bugs.kde.org/show_bug.cgi?id=455607 Bug ID: 455607 Summary: Use system colour schemes for konsole Product: konsole Version: 22.04.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: fischerfeli...@gmail.com Target Milestone: --- SUMMARY Currently system color schemes and konsole color schemes are completely independent. This worked fine for me until plasma 5.25 and the introduction of tinted color schemes. Since my wallpaper changes periodically, my color scheme also gets updated, but konsole obviously stays the same. This means my window decorations and window borders are now a different color from the actual terminal background. It would be nice if there was an option to set the terminal background to the standard BackgroundNormal color that all other apps also use (i.e. Dolphin, System Settings). STEPS TO REPRODUCE 1. enable System Settings > Appearance > Colours > Use accent colour from current wallpaper 2. edit a colour scheme and toggle Options > Tint all colours with accent colour, apply 3. open Konsole and change the wallpaper OBSERVED RESULT background colour of konsole stays the same while window decorationand borders (if enabled) change colour according to the wallpaper EXPECTED RESULT Konsole follows system wide colours SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux stable (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 455548] white artifacts around rounded corners when using dark theme (similar to korners bug) + when animating
https://bugs.kde.org/show_bug.cgi?id=455548 --- Comment #6 from Felix Fischer --- > if someone wants blur area that is able to move around flowlessly then it > needs a high end pc and in some cases that also might not be enough... kwin > disables blur during moving windows for the exact same reason. Fair enough, disabling blur does fix that issue, so I guess there is nothing to be done about that. Maybe I'll just use a solid background. > the problem is probably your theme in use... > the mask that is providing does not take into account antialiasing cases. > the mask provided should be 1px. narrower from the actual transparent area. > this is the way plasma dialogs are solving the case. Then it is an issue with breeze not providing the correct mask, right? Is there a way I can change this, or is this something the breeze devs have to do? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #3 from Felix Ernst --- Yea, after thinking some more about it, I have to say that it would of course generally be an improvement long-term if the Space key could be mapped to other actions. If/when a QuickLook feature would be implemented, users that got used to selection mode on Space would be just as disrupted by the sudden change as you are now by changing it to selection mode. I doesn't/didn't seem high priority to me because the old functionality on Space couldn't really be changed either. I'll now explain a way I see how this could potentially be implemented. Maybe someone is interested in picking this up. The biggest issue for what happens by default on Space is that the Space key needs to be usable for example by blind people to press down the currently focused button. If we were to simply bind the Space key to an action, pressing Space could no longer be used for anything else (https://bugs.kde.org/show_bug.cgi?id=458281), including Dolphin's type-ahead feature (https://bugs.kde.org/show_bug.cgi?id=458282). So when an action were to be bound to Space by a user, we need to disable it in certain situations so it doesn't interfere with other functionality. The way to disable a keyboard shortcut in certain situations is QAction::shortcutContext (https://doc.qt.io/qt-5/qaction.html#shortcutContext-prop). Unfortunately AFAIK this can't simply be used in our case with our frameworks. So instead we use QAction::shortcutContext to completely disable all keyboard shortcuts for the action that got assigned to the Space key. To make the shortcut still work, we will need to trigger the action ourselves when the Space key is pressed in the correct context. We do this by telling the view controller that that action is what is supposed to be triggered when the Space key is pressed while the view has focus. Then everything would be mostly working! Except if that action also has another non-Space keyboard shortcut. We can either let users know that that one doesn't work while Space is also assigned, or we install an eventFilter on the whole application to listen for that other shortcut. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465344] Full line highlight is disabled after selecting two items
https://bugs.kde.org/show_bug.cgi?id=465344 --- Comment #6 from Felix Ernst --- (In reply to Nate Graham from comment #4) > It should also show up if you have the Ctrl or Shift modifier key held down, > such that clicking will in fact grow the selection rather than unselecting > everything. Makes sense to me. (In reply to medin from comment #5) > Sorry but your argument is not convincing at all, if I want to deselect my > selected items I simply release ctrl key and click anywhere. Not sure if I was able to communicate what I mean. When you are about to "click anywhere" to deselect items, you would be confused if a file was highlighted. You would think that your next click would act on that file instead of deselecting everything and not acting on that file. For that reason the highlight should only show up if your next click will interact with that file. > > I personally would want the highlight to never appear if any item is > > selected at all > > Line Highlighting is a necessary way to make easy and fast selection instead > of following that tiny mouse pointer and verify which one is going to be > selected. Right. As Nate said: The highlight should show up while you are for example pressing Ctrl to select additional items. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465347] Selection marker is present when single-click selects items
https://bugs.kde.org/show_bug.cgi?id=465347 --- Comment #7 from Felix Ernst --- (In reply to Nate Graham from comment #6) > Regardless, supposed differences in usage (which I'm contesting) don't > justify the inconsistency between Dolphin and Folder View IMO. Please contest it with words. How are users supposed to select files that are diagonally next to each other if they don't know about Ctrl+Click, and don't/don't want to use selection mode? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465588] Selection mode is activated if I press delete key when nothing is selected
https://bugs.kde.org/show_bug.cgi?id=465588 --- Comment #1 from Felix Ernst --- This is intentional. You are being asked what you intend to move to the trash because nothing was selected when you pressed the delete key. I know this is unusual because most applications just do nothing/silently fail when one triggers a keyboard shortcut for something that can't directly be accomplished currently, but helping users to accomplish the task they wanted to accomplish (e.g. delete something) is strictly better than no reaction AFAICT. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465447] Make the Selection Mode optional
https://bugs.kde.org/show_bug.cgi?id=465447 --- Comment #7 from Felix Ernst --- > > is useless > > is useless > > The only useless thing is your belief that you really know what users want. You are literally ignoring my arguments while imputing that I was holding a belief without reason. (Except from being rude once more) this is what I meant with "I also didn't see him getting persuaded by anything yet which makes me think that he will keep arguing in favour of whatever he is proposing no matter if it is factually in the best interest of our users/software or not." above. I don't think discussing anything with you can ever be constructive like this. Don't be surprised when your actions don't lead anywhere this way. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465623] New: Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager
https://bugs.kde.org/show_bug.cgi?id=465623 Bug ID: 465623 Summary: Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager Classification: Applications Product: systemsettings Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Keywords: usability Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: felix.virt...@gmail.com Target Milestone: --- Created attachment 156173 --> https://bugs.kde.org/attachment.cgi?id=156173&action=edit Disks & Devices opens Elisa instead of Dolphin STEPS TO REPRODUCE 1. Press on `Disks & Devices` Plasmoid 2. Press a `Open in File Manager` button OBSERVED RESULT 3. Witness Elisa opening instead. EXPECTED RESULT 3. Dolphin opens to browse the mounted partition. SOFTWARE/OS VERSIONS Why is this duplicate here if there are selections for these above the summary and description fields already? Much UX genious here, such wow. Have one or the other. Having both just creates user confusion. Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465447] Make the Selection Mode optional
https://bugs.kde.org/show_bug.cgi?id=465447 --- Comment #9 from Felix Ernst --- There is no point. I have literally exhaustively answered you question number 2 last week in https://bugs.kde.org/show_bug.cgi?id=463048, and yet here we are again and you are asking the same question. I am not interested in writing more comments just for you to ignore them. Your questions are also only trying to put me into the defensive anyway. I didn't decide anything alone. We did. Most of what you are angry about wasn't even my idea. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager
https://bugs.kde.org/show_bug.cgi?id=465623 --- Comment #2 from Felix Kütt --- (In reply to Nate Graham from comment #1) > Is Elisa somehow set up to open folders, maybe? > > If you run `xdg-open ~` in a terminal window, does it open Elisa, or your > file manager? Gives me the following in terminal: ``` qrc:/qml/ElisaMainWindow.qml:18:1: QML ElisaMainWindow: Accessible must be attached to an Item ✔ file:///usr/lib/qt/qml/org/kde/kirigami.2/Page.qml:365: Error: Cannot assign QObject* to PageRow_QMLTYPE_174* file:///usr/lib/qt/qml/org/kde/kirigami.2/Page.qml:365: Error: Cannot assign QObject* to PageRow_QMLTYPE_174* org.kde.elisa.indexers.manager: Local file system indexer is inactive org.kde.elisa.indexers.manager: Baloo indexer is unavailable org.kde.elisa.indexers.manager: Baloo indexer is inactive qrc:/qml/NativeTrayMenu.qml:42: TypeError: Cannot call method 'name' of undefined qrc:/qml/NativeTrayMenu.qml:50: TypeError: Cannot call method 'name' of undefined org.kde.elisa.indexers.manager: Baloo indexer is available org.kde.elisa.indexers.manager: Baloo indexer is active org.kde.elisa.indexers.manager: trigger init of baloo file indexer qrc:/qml/ImageWithFallback.qml:36:5: QML Image: Invalid embedded cover image in /run/media/user/Secondary/Music/Lineage2/L2C2_tower_of_oman.mp3 ``` And does open Elisa. > Also, can you paste the output of `grep "inode/directory" > ~/.config/mimeapps.list`? ``` inode/directory=org.kde.elisa.desktop;org.kde.dolphin.desktop; inode/directory=org.kde.elisa.desktop; ``` Still, the button says 'Open in File Manager'. But if the application to open with can be changed somewhere then perhaps it should reflect that and say 'Open in Media Player' or 'Open in ApplicationType' or "Open in [executable name here]" respectively? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager
https://bugs.kde.org/show_bug.cgi?id=465623 --- Comment #4 from Felix Kütt --- (In reply to Nate Graham from comment #3) > Looks like the problem is that Elisa has become somehow configured as your > file manager. This isn't something that's supported, and Elisa doesn't > register itself as a handler for opening folders, so it's either a > configuration issue or a packaging error. I'd recommend fixing this in > System Settings > Applications > Default Applications. Yes, my best guess is when/while I changed waterfox to be my default browser months ago I might have been hovering over the file manager setting for a moment and since my mouse has a really sensitive scroll wheel it might have accidentally switched the file manager there. But that's besides the point and not the issue I'm trying to highlight. I'm trying to highlight that a button label that I assume should be contextual doesn't really reflect the action it's going to trigger. A small and nit-picky and thus surely low priority issue. But if it reflected what application or type of application it would launch that would also immediately communicated to me as a user that I might have misconfigured it rather than being left with a confusing surprise. Or I might still be left confused why the button would even say that but I wouldn't be surprised it opened something other than a file manager. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465623] Removable Devices systray Plasmoid(?) opens Elisa instead of File Manager
https://bugs.kde.org/show_bug.cgi?id=465623 --- Comment #6 from Felix Kütt --- Aye, as said, surely low priority, minor issue. But if nobody ever show interest, it'll never happen. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465347] Selection marker is present when single-click selects items
https://bugs.kde.org/show_bug.cgi?id=465347 --- Comment #9 from Felix Ernst --- Selection markers can already be disabled in the Dolphin settings. If we don't have a plan in mind how users are supposed to accomplish a basic task (selecting items diagonally next to each other), it doesn't make sense to me that we would be removing a feature. The same applies to Folder View AFAIAC, but even if it didn't, basic functionality is more important than consistency in this case IMO. Maybe the story is different in a year or two when users had the chance to get accustomed to selection mode for selecting, but until then Resolved Intentional seems to be fitting for this bug report to me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465588] Selection mode is activated if I press delete key when nothing is selected
https://bugs.kde.org/show_bug.cgi?id=465588 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Felix Ernst --- There are more reasons, but I guess I'll simply mark this as resolved. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 --- Comment #1 from Felix Ernst --- >On a keyboard it's more or less worthless The Ctrl+Arrow keys and Ctrl+Space keyboard shortcuts aren't that discoverable so having another more guided approach for multi-select helps the average user. Also see https://bugs.kde.org/show_bug.cgi?id=458091, which is about making selection mode more useful for keyboard users. >with a mouse, ctrl/shift + left click and right click for actions works fine. Absolutely, but again: Ctrl/Shift+click isn't that discoverable. Many users don't know about it, or aren't even used to using the keyboard and mouse together for "shortcuts". I noticed that without selection mode, some users weren't able to select multiple files unless they fit into a "selection rectangle" i.e. the thing that shows up when one draws a rectangle in the view area. Similarly, we have a rule in KDE not to expect users to be aware of right-click functionality because it is a somewhat hidden way to interact with the system by design. >triggering selection mode exclusively by accident Which keyboard shortcut are you triggering by accident? Mostly the Space key shortcut or others as well? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 --- Comment #6 from Felix Ernst --- (In reply to Riku from comment #2) > File manager GUIs have worked more or less the same for as long as I can > remember and now suddenly the muscle memory is destroyed. But I won't argue > against accessibility and it's great that people are actually thinking about > this stuff. It's just that it seems to always come at the expense of > irritating proficient users. Yea, I think there is often times not much way around that. After all, the most proficient computer users use keyboard shortcuts (often) and are therefore more likely to gain muscle memory for pretty much any action. If we want to change anything for the benefit of average users it is somewhat unavoidable in many situations that it causes disruption/irritation for proficient users. The most bug reports we got for a change in the last year was about the pre-selected button on the permanently delete dialog switching from "Delete" to "Cancel". It broke muscle memory and even though it is not completely stupid to have "Cancel" pre-selected, many users were getting really angry over it until I fixed it. See https://bugs.kde.org/show_bug.cgi?id=462845. > >Which keyboard shortcut are you triggering by accident? Mostly the Space key > >shortcut or others as well? > Mostly space indeed. I noticed there was already some discussion about > allowing rebinding space which would help a lot! However I do also end up > hitting copy or cut on an empty selection. > Say I try to copy but the file I thought was selected isn't. Now I would > instinctively try space, which actually exits selection mode. Even with the > original behavior of space restored, entering selection mode on an empty > copy is not what I wanted and doesn't help me in terms number of key > presses, etc. > I just don't see myself ever benefitting from selection mode, only having to > cancel it after having mistakenly activated it. > > I'd like to hear your thoughts on my proposed solutions. This is generally not a good use of my time. I'll answer briefly but please don't expect a back-and-forth discussion to come from this. >A. Add an option to fully disable selection mode. Seems like a somewhat weird way to solve this bug report to me. Selection mode isn't really meant to be a feature that users have to live with. It is supposed to only be triggered after explicit user action. It wouldn't really make a lot of sense to have an action in the UI and then a separate setting in the settings to disable that action. >B. Do not trigger selection mode with keyboard. It could still be triggered >with mouse or touch. This does make some sense for the specific issue in mind, but it is also totally inconsistent with every other action in KDE applications. Having actions that act differently depending on how they are triggered goes against many expectations. So while I agree that it would make some sense in the given case, I consider it overall a harmful precedent that can be solved differently. >C. Put selection mode on some shortcut that won't be constantly hit by >accident. >From the feedback I have gathered (which has been overwhelmingly positive at times) it seems like a good idea to make selection mode easily accessible by default. There is no way to get representative statistics on this because we have no way to gather representative data of our user base (only opt-in which computer-illiterate people who are part of the target user group of this feature won't have enabled). So, changing the shortcut away from Space by default doesn't seem like a great idea to me currently. It is not totally out of the picture but AFAIK we don't have enough reason to assume that this is the issue. Being able to change the key-binding of selection mode on the other hand does seems like a good idea, which is why my favourite solution for this bug report would be marking it as a duplicate of https://bugs.kde.org/show_bug.cgi?id=465489. This, however, doesn't address the other issue you mentioned about activating selection mode by accident e.g. by pressing Ctrl+C when nothing is selected. I don't really think this is something we need to fix. Maybe I am weird, but I generally don't press keyboard shortcuts by accident unless they are very close to each other. That's an issue for example with Ctrl+Q (quit application) right next to Ctrl+W (close tab). However we aren't going to remove the Ctrl+Q shortcut by default because having that is normal among pretty much every application. In the same way we shouldn't remove keyboard shortcuts out of fear that users are going to press them accidently, especially when the only thing that happens then is that a bar is shown which can be closed again in many different way
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Felix Ernst --- Thank you for understanding! *** This bug has been marked as a duplicate of bug 465489 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Selection Mode still gets triggered by Space, even after reassigning the shortcut
https://bugs.kde.org/show_bug.cgi?id=465489 --- Comment #7 from Felix Ernst --- *** Bug 466050 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 466107] Make it clear how you can re-enable the menu bar and the toolbar when both are hidden
https://bugs.kde.org/show_bug.cgi?id=466107 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #4 from Felix Ernst --- >Maybe any state where the menu gets hidden should show a message >telling the user it can still be accessed with the context menu, the same >way there's a message that tells you the keyboard shortcut to bring back >the menu. I don't think this can be implemented in frameworks because it is up to the applications to add the hamburger menu (or some other way to get back some sort of menu) to their context menus. They could also have a button on the UI to re-enable the toolbar, or they could decide that the toolbar is purely optional in their application and wouldn't want to add anything to the context menu to re-enable it or the menu. We also can't assume that the application would have a menu bar so we can't advertise the Ctrl+M shortcut. Similarly we can't even assume that the application has a toolbar because KHamburgerMenu doesn't need to be placed on a toolbar, so we can't tell users about such an action either. All in all, unless all right-clicks and all context-menu opening were to be routed through KHamburgerMenu (which seems like a bad idea), I don't really see a way to ever implement this in frameworks. -- Oh, even worse! I forgot that the same issue applies for applications that don't even use KHamburgerMenu. We would have to show a dialog for them any time the menu bar is hidden because we can't know if a hamburger menu is implemented in the toolbar. So, while I understand the basic argument, this might not be an actionable bug report for frameworks. I want to add though that if I (or anyone) doesn't see a way to technically implement something, it might just be that I/they simply don't have the right idea on how to accomplish something. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464967] dolphin process for another user (using kdesu) crashes after screen wake
https://bugs.kde.org/show_bug.cgi?id=464967 --- Comment #6 from Felix Ernst --- (In reply to Dick Tracey from comment #3) > Still happening with plasma 5.27.2, dolphin 22.12.3, nvidia 525.89.02 > Also not restricted to Dolphin, happens with Konsole as well: > > [backtrace] > > Seems like this is a bug it Qt5. Should I report this elsewhere? I unfortunately don't know. This is currently filed in Dolphin which seems wrong, but I can't tell you where it belongs to. I somehow doubt that reporting this to Qt, when it seems to be restricted to KDE code, will help, but I don't have that much experience with Qt's development. Sorry for not being of more help! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466636] Unable to set the value of # higher than 99 when bulk renaming files using Rename Tool provided by Dolphin
https://bugs.kde.org/show_bug.cgi?id=466636 Felix Ernst changed: What|Removed |Added CC||dav84m...@protonmail.com --- Comment #1 from Felix Ernst --- *** Bug 466959 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466959] multiple renaming
https://bugs.kde.org/show_bug.cgi?id=466959 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 466636 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 466636] Unable to set the value of # higher than 99 when bulk renaming files using Rename Tool provided by Dolphin
https://bugs.kde.org/show_bug.cgi?id=466636 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org, ||kdelibs-b...@kde.org Component|general |general Version|22.12.2 |5.103.0 Assignee|dolphin-bugs-n...@kde.org |kio-bugs-n...@kde.org Product|dolphin |frameworks-kio --- Comment #2 from Felix Ernst --- I assume https://invent.kde.org/frameworks/kio/-/commit/17584f077724838bc37daa2058ad36ebb6201dd2 caused this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 310123] Make it possible to enable/disable all preview plugins
https://bugs.kde.org/show_bug.cgi?id=310123 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #3 from Felix Ernst --- Isn't this already implemented through the "View>Show Previews" action? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 310123] Make it possible to enable/disable all preview plugins
https://bugs.kde.org/show_bug.cgi?id=310123 --- Comment #4 from Felix Ernst --- Oh, I think I understand. This might not really be about wanting to enable or disable all previews but about having an easy way in the settings to e.g. disable all previews and then enable them only for very specific file types. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443438] dolphin not usable keyboard-only / without mouse
https://bugs.kde.org/show_bug.cgi?id=443438 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 466636] Unable to set the value of # higher than 99 when bulk renaming files using Rename Tool provided by Dolphin
https://bugs.kde.org/show_bug.cgi?id=466636 Felix Ernst changed: What|Removed |Added Latest Commit|https://invent.kde.org/fram |https://invent.kde.org/fram |eworks/kio/commit/04e311555 |eworks/kio/commit/d8e4f575e |74939dc0be2078b5f17c36791ef |4967a2303812529a866b89ad2fe |57e5|26f5 --- Comment #5 from Felix Ernst --- Git commit d8e4f575e4967a2303812529a866b89ad2fe26f5 by Felix Ernst, on behalf of Xaver Hugl. Committed on 08/03/2023 at 10:22. Pushed by felixernst into branch 'kf5'. widgets/renamefiledialog: set number limit again Not setting a maximum makes it default to 99, which is not what we want. Instead, set it to a billion, which should be enough for everyone (cherry picked from commit 04e31155574939dc0be2078b5f17c36791ef57e5) M +1-0src/widgets/renamefiledialog.cpp https://invent.kde.org/frameworks/kio/commit/d8e4f575e4967a2303812529a866b89ad2fe26f5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- One can already change the folder icon in the properties window. Folders with various colours are available as icons there. A more direct way to switch the folder colour doesn't really seem necessary to me, but maybe there is a workflow I am missing. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED CC||felixer...@kde.org Resolution|--- |FIXED --- Comment #1 from Felix Ernst --- > Dolphin version 21.12.3 There was some work on the relevant code for this bug in the last 12 month when work was done related to https://bugs.kde.org/show_bug.cgi?id=440663. I was neither able to reproduce the bug reported here with Dolphin 22.08 nor with the yet-to-be-released 23.04 beta. I'll mark this as resolved. Feel free to re-open if you can reproduce it with a more recent Dolphin version. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 Felix Ernst changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Felix Ernst --- You are probably talking about this "Color Folder" Dolphin service menu: https://store.kde.org/p/998450 >Tags are fine but they aren't even close to just right click and change it to >"blue", >get the "blue" folders and them put them in the right place (that's my >workflow with this). That might be the ideal workflow though if this was to be implemented. The "Create New Tag" dialog could have colour tags as one way to create a new tag. Folders who get this tag could be switched to the fitting coloured folder icon. Might be really neat! Another way would be to have this as a standalone "official" service menu entry that could be dis/enabled in Dolphin's settings, but then we wouldn't get the advantage of tags, which is being usable from other applications. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #3 from Felix Ernst --- Dolphin version 21.12.3 stands for the version that was released in the year 2021, month 12 (December), third bugfix release. Kubuntu 22.04 is the Kubuntu version that was released in the year 2022, month 4 (April). The Kubuntu 22.04 version won't receive any new Dolphin versions that were released later than April 2022. This is out of KDE's control. >From my testing, the bug that you are reporting has been fixed and released since then. Unless you upgrade your Kubuntu installation to newer versions e.g. Kubuntu 22.10 or the soon-to-be-released Kubuntu 23.04, you won't be able to upgrade to a Dolphin version that has the fix. Please only re-open if you have confirmed that this bug exists on those later versions. I literally can't do anything else because from my testing, the bug has already been fixed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 --- Comment #5 from Felix Ernst --- Well, I am not sure what I am supposed to tell you. I do my development for KDE in my free time as a volunteer without payment. We are not payed to fix those bugs, so expecting anything to happen from our side is already a bit ill-advised. In this case though, we did actually fix the bug (AFAIK), so that's all we do about it. Dolphin has never had the concept of a long term support version. We release a new Dolphin version three times a year currently and support each of these versions with bugfixes for that third of a year. Now Ubuntu by the company Canonical comes along and offers a so-called long term support (LTS) version of their distribution. The idea of this LTS version is that it will receive security fixes for some amount of years (https://ubuntu.com/blog/what-is-an-ubuntu-lts-release). They aren't even claiming that they will provide bug-fixes, only security fixes. So in this case they are true to their word. In the end, there is probably simply not enough money in this business to fix annoyances like these in older versions. I am not sure how much money you might have paid for your distribution, but none of it landed in the pockets of the KDE contributors that maintain Dolphin. If it was a good use of my time to maintain old versions instead of improving future releases, either because of a financial or a "the greater good" incentive, I wouldn't mind doing it. As it currently stands though, it isn't really feasible for us to provide long term support versions of Dolphin for free. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 --- Comment #7 from Felix Ernst --- >So if the KDE Team isn't maintaining it, who is it then? https://kubuntu.org/the-kubuntu-team/ >What would happened in a case of a security issue? Someone would let the KDE security team know https://kde.org/info/security/. Then someone would have to fix it. The various operating systems will be notified of this. It is the responsibility of the Kubuntu team that this fix is then available for their users. >And I also wonder how this bug can even come into a LTS release. As I mentioned above: There are no Dolphin LTS versions. The decision which Dolphin version to use for their Kubuntu LTS version is with the Kubuntu people. They might not have been aware of the issue, or they considered the bug not that important because it isn't a security issue for example. >Waiting two years to get a bug fixed that disturbs my workflow every >day isn't really an option for me, so what can I do? You can upgrade to a later Kubuntu version. Alternatively there is the backports repository for later versions of KDE software. You should be able to get a more up to date Dolphin version there while staying on Kubuntu 22.04. That would be here: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports I have never used that, but it is supposed to work without a problem. >I'm also happy to give some money, but first I can't find a way to >donate specific for a application or even a bug, and second I'm not rich, >so I could not afford to pay a full time developer. And well, I still >have a few other new bugs that I haven't reported jet, but this one is >the most annoying thing. Most projects in KDE do not have a way to receive direct donations. Instead donations go to KDE as a whole. There are some exceptions like Krita and kdenlive. Some individual contributors might take donations, but those are generally not meant for a specific purpose either. I am not sure how many would be willing to fix a specific bug because of a donation. You can ask in a chat to see if anyone wants to take you up on an offer. Here are the various ways to talk to people: https://userbase.kde.org/Getting_Help Writing in a developer chatroom or making an offer on the mailing list might be your best bets. I personally would be interested in fixing bugs for pay. If it was sustainable for me to fix bugs, I could do it a lot more so that makes sense to me. If you want a specific bug fixed, you can send me an eMail and I'll give you an offer. The typical going rate for a c++ software developer is about 100€ per hour, but I would go way below that (depending on the work as low as 20€ per hour) if it is in line with what I consider important for our users. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467221] Folder color switcher function
https://bugs.kde.org/show_bug.cgi?id=467221 --- Comment #8 from Felix Ernst --- >2 - Change the "create a tag menu" to a "manage tags menu" >that can associate tags with colors (and even no color/no change), >rename, add or remove, enable and disable tags >(just like MacOS, take a look at screenshot2). I agree. That would be a lot better. This could be as easy as having a colour symbol like "🔵", "🟡" as the first character of every such tag, and then colour every folder with the corresponding colour if it has any tag associated that contains such a colour symbol. >The tag should ALWAYS be visible at the start of the name of >the file/folder (just like MacOS, take a look at screenshot3); Having it at the beginning of a file makes some sense. What we have right now already is that one can "Show additional information>Tags" and then the tags will be listed right below the file name. This is not as pretty, but it allows hiding the tags information when one doesn't need it, which is a slight upside. If the tag's name is a symbol like "🔴", it somewhat serves the purpose you are describing. >1 - Put the "Tag" menu visible on the sidebar by default Tags already show up in the sidebar by default (after a Dolphin restart) if a tag was created. >Now let's suppose i have a very specific tag called "fun/comedy", >i can find content with this tag in all kinds of folders BUT it >is faster when i am accessing the /Videos/Movies/ and i can see >the tag for "fun/comedy" in a file and i can immediately find the >"Adam Sandler" movie i was searching for. Get it? Right. We don't have an easy way to jump to see the files with a certain tag within a specific folder currently. >Imho this would be a killer feature It does sound useful for a certain type of user. It wouldn't really make a difference for my personal way of organising files, but I bet it would make a big difference for others. >1 - Nemo color switcher menu is a MUST, horizontal bar inside the >context menu with nothing else, just "blue this" and "red that" >is by far the best option. I don't think every user would want this in their context menu, but it could be something that is enabled by default but could be disabled. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467192] Folders are opened in new tab but should open in new window
https://bugs.kde.org/show_bug.cgi?id=467192 --- Comment #8 from Felix Ernst --- You can also comment directly on bug reports that you want to see fixed and offer a bug bounty. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 452614] Monitors with identical EDID hash values (e.g. from same vendor and no serial numbers or identical serial numbers) get scrambled on boot
https://bugs.kde.org/show_bug.cgi?id=452614 Felix Miata changed: What|Removed |Added CC||mrma...@earthlink.net -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 171300] Let user choose if 'paste' actions take place in the currently selected folder or in the active view
https://bugs.kde.org/show_bug.cgi?id=171300 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #12 from Felix Ernst --- I think this is another case where bug https://bugs.kde.org/show_bug.cgi?id=424723 is in the way. That bug is about the current behaviour that a folder is automatically selected if one ermeges from it. If one hasn't explicitly selected a folder and uses the paste action, it can be confusing that the file won't be pasted to the current directory. I feel like we could be more bold in acting on the selected folder if we could be sure that a folder was actually selected by the user. So I would be fine with changing the behaviour to always paste into a singular selected folder if the automatic selection of folders wasn't a thing anymore. So https://bugs.kde.org/show_bug.cgi?id=424723 needs to be fixed first IMHO. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467371] Dolphin too slow to navigate on remote filesystems mounted over VPN
https://bugs.kde.org/show_bug.cgi?id=467371 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Yes, working with remote folders isn't that great on Dolphin currently. There is https://invent.kde.org/system/dolphin/-/merge_requests/522 which might improve this a bit. >1. Notice that subfolders with many sub-subfolders in them may take very long >to appear on dolphin This one might be improved in the next version (Dolphin 23.04) by https://invent.kde.org/system/dolphin/-/commit/ba930ddb3635fe2d94d727e72aaf261513b28060. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467371] Dolphin too slow to navigate on remote filesystems mounted over VPN
https://bugs.kde.org/show_bug.cgi?id=467371 --- Comment #3 from Felix Ernst --- >I would love to see both MR's applied. Is there anything I can to help this >happen? Thanks for the offer to help! Unfortunately, unless you are a very skilled software developer, there isn't much you can do at this point in time to move this forward. The right people are currently actively working on it, which is great. I hope they won't get stuck in which case emotional support might help. ^^ This is one of the more complicated topics to work on even for proficient developers, and one of the people reviewing it is very careful about this being implemented cleanly, which sets a high bar. The later commit I mentioned (https://invent.kde.org/system/dolphin/-/commit/ba930ddb3635fe2d94d727e72aaf261513b28060) is already merged so you might already see slight performance improvements once you update to the yet-to-be-released Dolphin 23.04. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467752] Dolphin uses black text over black background when using the BreezeDark theme
https://bugs.kde.org/show_bug.cgi?id=467752 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- There are actually currently discussions about how to fix this in a general manner. You can read up on it in https://invent.kde.org/teams/vdg/issues/-/issues/26 but try to refrain from commenting there unless you have a deep knowledge of the topic because it is already quite busy there. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467682] Initiate filter bar when typing
https://bugs.kde.org/show_bug.cgi?id=467682 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- I don't think those two should be combined. Typing a key to find a specific file seems intuitive to me. I don't think a user would want all the files that don't match this to be hidden then. It certainly is a bit weird that we have a "type ahead" feature, a "filter" feature, and a "search" feature, but if I were to combine two of them it would be "filter" and "search" and not "type ahead" and "filter". In a way filtering is the same as searching but only for the current location. I agree however that the "type ahead" feature could be improved in the sense that it currently isn't very clear what was typed. I believe we should show text in the bottom left of the view that explains "Jumping to "test"…". The text should fade away when no new key was typed for a second or two. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467838] Weird colouring bug causes selected location in sidebar to become darkened, therefore not following the colour scheme.
https://bugs.kde.org/show_bug.cgi?id=467838 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Felix Ernst --- Items that have keyboard focus are supposed to be more visibly highlighted than items that don't have keyboard focus. So the list in the side bar will have a more dimmed highlight effect after being clicked once because the keyboard focus goes to Dolphin's main view then (which in turn gets an accent-coloured frame to signify that it has keyboard focus). When the same list item in the side bar is clicked again after that, it gains the keyboard focus and therefore becomes more bright (i.e. non-dimmed accent-coloured). You can test it yourself: Whenever the highlight in the sidebar is brighter, using the up and down arrows will move the highlight within that sidebar instead of in Dolphin's main view. When Dolphin's main view has keyboard focus you will see a bright outline around the view. I know that not all areas of Dolphin clearly highlight themselves when they have keyboard focus, but at least the behaviour you are reporting here seems correct to me. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458900] Selection Mode should work with keyboard
https://bugs.kde.org/show_bug.cgi?id=458900 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 458091 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458091] Make multiple selection keyboard navigable
https://bugs.kde.org/show_bug.cgi?id=458091 Felix Ernst changed: What|Removed |Added CC||ad.liu@gmail.com --- Comment #2 from Felix Ernst --- *** Bug 458900 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458982] Setting Show Tooltips causes file info to appear which obscures file names in a file list
https://bugs.kde.org/show_bug.cgi?id=458982 Felix Ernst changed: What|Removed |Added Resolution|--- |DUPLICATE CC||felixer...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 455645 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455645] Tooltip frequently covers filenames when it appears
https://bugs.kde.org/show_bug.cgi?id=455645 Felix Ernst changed: What|Removed |Added CC||pjdyn...@yahoo.co.uk --- Comment #10 from Felix Ernst --- *** Bug 458982 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454578] Mirrored displays are set to 1,0 instead of the 0,0 of the second display, causing desktop misbehaviour
https://bugs.kde.org/show_bug.cgi?id=454578 Felix Yan changed: What|Removed |Added CC||felixonm...@archlinux.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454578] Mirrored displays are set to 1,0 instead of the 0,0 of the second display, causing desktop misbehaviour
https://bugs.kde.org/show_bug.cgi?id=454578 --- Comment #2 from Felix Yan --- Confirming the problem. Arch Linux 5.19.9-zen1 KDE Plasma 5.25.5 Kscreen 5.25.5 Qt 5.15.6-kde -- You are receiving this mail because: You are watching all bug changes.
