[kwin] [Bug 482626] On X11, screen locker flickers for 1-2minutes
https://bugs.kde.org/show_bug.cgi?id=482626 Siddhartha changed: What|Removed |Added CC||k...@sdht.in --- Comment #4 from Siddhartha --- I'm getting the same issue on NixOS. Strangely I was not facing the issue when I initially installed Plasma 6, so it might be because of some dependency update that Arch also has. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479954] KDE Connect not browser the phone file system.
https://bugs.kde.org/show_bug.cgi?id=479954 Siddhartha changed: What|Removed |Added CC||k...@sdht.in --- Comment #4 from Siddhartha --- Not sure, but possibly kio-fuse needs to be installed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481119] New: Bring back option to save text selection to history without syncing to clipboard
https://bugs.kde.org/show_bug.cgi?id=481119 Bug ID: 481119 Summary: Bring back option to save text selection to history without syncing to clipboard Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: k...@sdht.in Target Milestone: 1.0 After https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1065, the option to "Always save in history" is disabled for "Text selection" when "Keep selection and clipboard the same" option is disabled. I relied on this feature to both keep my selection and clipboard separate and also save my selections to clipboard history (with a large history size to accommodate many selections). The "More about.." help text tooltip still says "If it is turned off, the selection may still be saved in the clipboard history (subject to the options below)", but the code comment says otherwise. Can we please bring back this option? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 466467] Frameworks 5.103: wireless extensions that are deprecated for modern drivers; use nl80211
https://bugs.kde.org/show_bug.cgi?id=466467 Siddhartha changed: What|Removed |Added CC||k...@sdht.in --- Comment #2 from Siddhartha --- I'm getting a similar warning on Linux v6.4.2 and kded 5.107: `kded5' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454186] Kwin is not scaling 1080p resolution on a 4k screen correctly
https://bugs.kde.org/show_bug.cgi?id=454186 --- Comment #4 from Siddhartha --- Here is my xrandr output. In master, setting resolution to "3840x2160" works but not for "1920x1080". Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 3840x2160 60.00 + 59.97 3200x1800 59.9659.94 2880x1620 59.9659.97 2560x1600 59.9959.97 2560x1440 59.9959.9659.95 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 59.9959.9859.9059.91 1920x1200 59.8859.95 1920x1080 60.01* 59.9759.9659.93 1600x1200 60.00 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454186] Kwin is not scaling 1080p resolution on a 4k screen correctly
https://bugs.kde.org/show_bug.cgi?id=454186 --- Comment #3 from Siddhartha --- So the first bad commit is a4a2ee042 Refactor output mode abstractions. It's parent commit 6b4daeddc9 works okay for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454186] Kwin is not scaling 1080p resolution on a 4k screen correctly
https://bugs.kde.org/show_bug.cgi?id=454186 --- Comment #1 from Siddhartha --- Created attachment 149097 --> https://bugs.kde.org/attachment.cgi?id=149097=edit kwin incorrect scaling -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454186] New: Kwin is not scaling 1080p resolution on a 4k screen correctly
https://bugs.kde.org/show_bug.cgi?id=454186 Bug ID: 454186 Summary: Kwin is not scaling 1080p resolution on a 4k screen correctly Product: kwin Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: k...@sdht.in Target Milestone: --- I've a 1920x1080 resolution set on a 4K laptop screen. In Kwin master (773384b59f), Plasma is being rendered in only 1/4th of the laptop screen, as you can see in the attached photo. Downgrading to commit a23d23593b (from April) fixes the rendering to the full screen as expected. I have not been able to do a git bisect between these two commits yet to figure out the first bad commit. If a fix is not immediately obvious, let me know and I'll try to perform the git bisect sometime later. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451734] Plasma is unable to autostart programs with a space in the path
https://bugs.kde.org/show_bug.cgi?id=451734 --- Comment #2 from Siddhartha --- Thanks David! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451734] New: Plasma is unable to autostart programs with a space in the path
https://bugs.kde.org/show_bug.cgi?id=451734 Bug ID: 451734 Summary: Plasma is unable to autostart programs with a space in the path Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: k...@sdht.in CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY One of my autostart application has the following line in its .desktop: Exec="/opt/Mullvad VPN/mullvad-vpn" %U This leads to Plasma unable to execute this on startup. In the logs, I see: systemd[1869]: app-mullvad\x2dvpn@autostart.service: Failed at step EXEC spawning /opt/Mullvad: No such file or directory It seems the quoted path is not being parsed properly when auto generating the systemd startup service. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.16.15-arch1-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 450937] New: It is hard to switch away from an audio playback device when it becomes inactive
https://bugs.kde.org/show_bug.cgi?id=450937 Bug ID: 450937 Summary: It is hard to switch away from an audio playback device when it becomes inactive Product: plasma-pa Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: k...@sdht.in CC: m...@ratijas.tk, now...@gmail.com Target Milestone: --- SUMMARY The "simple" version of the audio applet, where the options to change the playback device are hidden, makes it hard to set the right audio output when an external device is connected and disconnected, as described below. STEPS TO REPRODUCE 1. Connect an external hdmi device with audio output. The audio applet shows two playback devices: "Laptop Speaker" and "HDMI Output". 2. Select HDMI Output as default or change playback output of a stream to HDMI in the "Applications" tab. Audio plays through the HDMI. 3. Disconnect HDMI. OBSERVED RESULT No audio can be heard, since output does not automatically switch back from HDMI to Speaker. Moreover, the audio applet becomes "simple", as there is only one output, so the applet decides to hide the options to set the default device or switch the playback device in the application tab. To fix the issue, I now have to open "Configure audio devices" to set the correct playback stream for an application. Also, I have to click on "Show inactive devices" before I can set the default back to "Speaker" again. EXPECTED RESULT I don't know if switching the default or playback stream of an application to "Speaker" automatically is the right solution. But perhaps the audio applet can continue to show the "advanced" options of selecting the default device or the corresponding options in the Applications tab as long as an inactive device is selected and only hide when none of the outputs is to an inactive device? SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-arch1-1 (64-bit) Graphics Platform: X11 Audio Server Name: PulseAudio (on PipeWire 0.3.47) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448709] New: Application crash.
https://bugs.kde.org/show_bug.cgi?id=448709 Bug ID: 448709 Summary: Application crash. Product: krita Version: 5.0.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Brush Engine/Shape Assignee: krita-bugs-n...@kde.org Reporter: sidlam3...@gmail.com Target Milestone: --- Krita Version: 5.0.2 Languages: en_US, en Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 6.2.9200 Pretty Productname: Windows 8 (6.2) Product Type: windows Product Version: 8 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (Intel(R) UHD Graphics Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) 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) Version: 3.0 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_OES_texture_half_float" "GL_CHROMIUM_bind_uniform_location" "GL_ANGLE_client_arrays" "GL_EXT_shader_texture_lod" "GL_NV_pack_subimage" "GL_ANGLE_multiview" "GL_EXT_color_buffer_float" "GL_NV_fence" "GL_OES_texture_half_float_linear" "GL_OES_texture_float" "GL_OES_standard_derivatives" "GL_OES_depth32" "GL_CHROMIUM_copy_texture" "GL_EXT_draw_buffers" "GL_EXT_texture_compression_dxt1" "GL_EXT_disjoint_timer_query" "GL_OES_mapbuffer" "GL_ANGLE_depth_texture" "GL_EXT_texture_compression_s3tc_srgb" "GL_EXT_texture_filter_anisotropic" "GL_NV_EGL_stream_consumer_external" "GL_CHROMIUM_sync_query" "GL_EXT_debug_marker" "GL_CHROMIUM_color_buffer_float_rgb" "GL_OES_vertex_array_object" "GL_ANGLE_program_cache_control" "GL_ANGLE_robust_client_memory" "GL_EXT_color_buffer_half_float" "GL_OES_surfaceless_context" "GL_ANGLE_lossy_etc_decode" "GL_EXT_blend_minmax" "GL_OES_packed_depth_stencil" "GL_ANGLE_texture_usage" "GL_OES_EGL_image_external_essl3" "GL_ANGLE_instanced_arrays" "GL_OES_compressed_ETC1_RGB8_texture" "GL_ANGLE_texture_compression_dxt3" "GL_OES_texture_npot" "GL_EXT_occlusion_query_boolean" "GL_EXT_read_format_bgra" "GL_EXT_discard_framebuffer" "GL_EXT_texture_storage" "GL_OES_EGL_image_external" "GL_EXT_unpack_subimage" "GL_KHR_debug" "GL_NV_pixel_buffer_object" "GL_EXT_map_buffer_range" "GL_EXT_texture_format_BGRA" "GL_ANGLE_pack_reverse_row_order" "GL_ANGLE_texture_compression_dxt5" "GL_EXT_sRGB" "GL_CHROMIUM_color_buffer_float_rgba" "GL_EXT_texture_rg" "GL_EXT_robustness" "GL_ANGLE_framebuffer_multisample" "GL_EXT_texture_norm16" "GL_OES_get_program_binary" "GL_EXT_frag_depth" "GL_OES_EGL_image" "GL_ANGLE_request_extension" "GL_OES_element_index_uint" "GL_CHROMIUM_bind_generates_resource" "GL_CHROMIUM_copy_compressed_texture" "GL_OES_rgb8_rgba8" "" "GL_OES_texture_float_linear" "GL_ANGLE_translated_shader_source" "GL_ANGLE_framebuffer_blit" QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true useBufferInvalidation (config option): false Hardware Information GPU Acceleration: auto Memory: 16219 Mb Number of Cores: 12 Swap Location: C:/Users/sidla/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/sidla/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 200 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 420 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location
[plasmashell] [Bug 429211] Digital clock/whole panel is not updated until user interaction
https://bugs.kde.org/show_bug.cgi?id=429211 --- Comment #9 from Siddhartha --- I'm on git master and haven't noticed it again. It's possible the fix just made it rarer. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442781] Audio test feature does not work as expected
https://bugs.kde.org/show_bug.cgi?id=442781 --- Comment #7 from Siddhartha --- Nice. Thanks Nicolas and Nate! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442781] Audio test feature does not work as expected
https://bugs.kde.org/show_bug.cgi?id=442781 --- Comment #2 from Siddhartha --- Oh hmm. Should have mentioned I'm using pipewire implementation of pulseaudio. Maybe that's the issue? Will check with the native pulseaudio sometime. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442781] New: Audio test feature does not work as expected
https://bugs.kde.org/show_bug.cgi?id=442781 Bug ID: 442781 Summary: Audio test feature does not work as expected Product: plasma-pa Version: git-master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: now...@gmail.com Reporter: k...@sdht.in CC: plasma-b...@kde.org Target Milestone: --- SUMMARY In Settings -> Audio, all playback devices have a "Test" button. I have a laptop speaker and a bluetooth device connected. The Test button for both the devices plays the test audio through whatever is the default playback device. Shouldn't the Test ignore the default setting and play through the individual devices associated with the Test button? If not, maybe there should be only one Test button? SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.80 (plasma-pa-git r968.20210916.61a0851) KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.5-arch1-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442534] Maximized window does not move to another moniroe
https://bugs.kde.org/show_bug.cgi?id=442534 Siddhartha changed: What|Removed |Added CC||mariusz.lib...@gmail.com --- Comment #5 from Siddhartha --- *** Bug 442615 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442615] shortcut 'window to next screen' doesn't work with maximized windows
https://bugs.kde.org/show_bug.cgi?id=442615 Siddhartha changed: What|Removed |Added CC||k...@sdht.in Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Siddhartha --- Had a similar issue. Should be fixed now. *** This bug has been marked as a duplicate of bug 442534 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425046] kscreen does not init multiple screens properly the first time
https://bugs.kde.org/show_bug.cgi?id=425046 Siddhartha changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Siddhartha --- Seems to be working fine for now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442363] Multiscreen handling is broken
https://bugs.kde.org/show_bug.cgi?id=442363 --- Comment #4 from Siddhartha --- Thanks Vlad. Both my bugs seems to have gone away. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442534] Maximized window does not move to another moniroe
https://bugs.kde.org/show_bug.cgi?id=442534 Siddhartha changed: What|Removed |Added CC||k...@sdht.in --- Comment #4 from Siddhartha --- *** Bug 442363 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442363] Multiscreen handling is broken
https://bugs.kde.org/show_bug.cgi?id=442363 Siddhartha changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Siddhartha --- *** This bug has been marked as a duplicate of bug 442534 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442363] Multiscreen handling is broken
https://bugs.kde.org/show_bug.cgi?id=442363 --- Comment #2 from Siddhartha --- > Is it with any window? or only particular windows? Good question. It seems to affect only maximized windows. E.g., doesn't work for a maximized dolphin or system settings window, but works after un-maximizing it. No window rules. Not sure if the Yakuake bug is related or a different one. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442363] New: Multiscreen handling is broken
https://bugs.kde.org/show_bug.cgi?id=442363 Bug ID: 442363 Summary: Multiscreen handling is broken Product: kwin Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: k...@sdht.in Target Milestone: --- Created attachment 141504 --> https://bugs.kde.org/attachment.cgi?id=141504=edit KWin supportInformation I have 3 screens: 1 laptop display + 2 external monitors. Multiscreen handling seems to be broken in two noticeable ways: * Move to screen # is not working, either through the right click menu on the titlebar or using global shortcuts. The window remains where it was. * Yakuake's slide-down-on-hotkey feature only works properly when the leftmost screen (1080p) is active. On the other 2 screens, Yakuake arbitrarily opens either on the active screen or on the leftmost screen across multiple invocations. Moreover, it's display area is cutoff when the 1440p screen is active. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.80 (kwin-git r19986.20210911.abe6b41534) KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-arch1-2 (64-bit) Graphics Platform: X11 Attached kwin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441396] Kwin is rendering old content when taking screenshots
https://bugs.kde.org/show_bug.cgi?id=441396 Siddhartha changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Siddhartha --- Well, I digged into my Arch configuration and turns out the issue was installed xf86-video-intel driver, which is not recommended [0]. Removing the driver seems to have fixed the issue. Will report back if it reappears. [0] https://community.kde.org/Plasma/5.9_Errata#Intel_GPUs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441396] New: Kwin is rendering old content when taking screenshots
https://bugs.kde.org/show_bug.cgi?id=441396 Bug ID: 441396 Summary: Kwin is rendering old content when taking screenshots Product: kwin Version: git master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: k...@sdht.in Target Milestone: --- Created attachment 140959 --> https://bugs.kde.org/attachment.cgi?id=140959=edit KWin supportInformation SUMMARY Taking screenshots with Spectacle renders old content instead of what is actually on the screen. I have to "reset" Kwin by changing some Compositor settings before taking screenshots. STEPS TO REPRODUCE > Open Spectacle and take a screenshot using rectangular region. The screen changes to some old state as it was when I had just logged in, including a partially black screen and a notification widget showing "Connected to wifi". > Try "Window Under Cursor" The same thing happens. Either some old window or the desktop itself comes in the screenshot, but not the currently open windows. > Go to Compositor settings and change "Scale method" or "Rendering backend" to > something else. Now Kwin resets and I can take screenshots of the current screen again. This bug appeared in the last month or so. Willing to help debug. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.80 (plasma-desktop-git r8585.20210820.4cc2de24d, kwin-git r19807.20210821.17b161213) KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-arch1-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Attaching kwin info. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422282] Crash inKFileItemModel::removeItems() when using the tree view mode of the details view
https://bugs.kde.org/show_bug.cgi?id=422282 --- Comment #25 from Siddhartha --- Created attachment 133446 --> https://bugs.kde.org/attachment.cgi?id=133446=edit double entries for some files and folders A reliable way for me to reproduce this crash is to open `/usr` in Dolphin in details view mode, and then expanding the `bin` or `lib` folder. Trying to collapse the folder always seems to giving me a crash. I noticed that some of the entries are duplicated, as shown in the screenshot, which must be related to this bug. I also observed that navigating into `lib', then going back to `/usr` and expanding `lib` does not result in a crash anymore. I suspect that the bug has something to do with the sorting implementation when running in expanded tree mode. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] Digital clock is not updated until user interaction
https://bugs.kde.org/show_bug.cgi?id=429211 --- Comment #4 from Siddhartha --- I've noticed just the clock, as it's the easiest to notice when out of date. But I suspect it's the entire panel that is freezing. I'll try to notice and post here if slack or other icons show any changes while being stuck. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] Digital clock is not updated until user interaction
https://bugs.kde.org/show_bug.cgi?id=429211 --- Comment #2 from Siddhartha --- Created attachment 133404 --> https://bugs.kde.org/attachment.cgi?id=133404=edit Full KWin info No, I have an integrated graphics card. Relevant KWin info snippet: Compositing === Compositing is active Compositing Type: OpenGL OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2) OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.2.2 OpenGL platform interface: GLX OpenGL shading language version string: 4.60 Driver: Intel GPU class: Unknown OpenGL version: 4.6 GLSL version: 4.60 Mesa version: 20.2.2 X server version: 1.20.9 Linux kernel version: 5.9.8 Direct rendering: Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine: no OpenGL 2 Shaders are used Painting blocks for vertical retrace: no -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429211] New: Digital clock is not updated until user interaction
https://bugs.kde.org/show_bug.cgi?id=429211 Bug ID: 429211 Summary: Digital clock is not updated until user interaction Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: k...@sdht.in Target Milestone: 1.0 SUMMARY I have a 3 monitor setup with the default Plasma panel on all 3 screens. Frequently, I am noticing that the digital clock on one or two of the 3 screens do not update their times normally. STEPS TO REPRODUCE 1. Setup default plasma panels on multiple screen, with digital clock visible. 2. Let time advance. OBSERVED RESULT Some of the digital clocks fall behind and show old times. However, the times get updated after I interact with Plasma somehow, either by clicking on the panel to open the system tray or the calender, opening Krunner, minimizing applications, and so on. This indicated that Plasma is not repainting the panel automatically for some reason. EXPECTED RESULT All clocks should get updated every minute. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: plasma-desktop-git r7987.20201114.dc704535c KDE Frameworks Version: 5.77.0 (plasma-framework-git r15649.20201114.9df6f42c6) Qt Version: 5.15.1 Kernel Version: 5.9.8-arch1-1 I've marked this as a major issue as incorrect times can lead to real world consequences, for instance being late for meetings. Likely more information will be needed to debug this unless it's easily reproducible. I am willing to help debug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425174] global menu widget doesn't have panning between sections
https://bugs.kde.org/show_bug.cgi?id=425174 --- Comment #10 from Siddhartha --- Thanks a lot, Noah! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425174] global menu widget doesn't have panning between sections
https://bugs.kde.org/show_bug.cgi?id=425174 Siddhartha changed: What|Removed |Added Attachment #131275|0 |1 is obsolete|| --- Comment #8 from Siddhartha --- Created attachment 131277 --> https://bugs.kde.org/attachment.cgi?id=131277=edit Global Menu Bug V2 Thanks, now I get back an older bug, where the items don't have any padding at the bottom, as shown in the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425174] global menu widget doesn't have panning between sections
https://bugs.kde.org/show_bug.cgi?id=425174 --- Comment #6 from Siddhartha --- Created attachment 131275 --> https://bugs.kde.org/attachment.cgi?id=131275=edit Global Menu Bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425174] global menu widget doesn't have panning between sections
https://bugs.kde.org/show_bug.cgi?id=425174 Siddhartha changed: What|Removed |Added CC||k...@sdht.in --- Comment #5 from Siddhartha --- Does not seem to have fixed it for me. I get the same layout as originally reported, and clicking on a menu item deforms it even further. Attaching screenshot. Operating System: Arch Linux KDE Plasma Version: 5.19.80 (git master compiled today) KDE Frameworks Version: 5.74.0 (plasma-framework-git r15542.8c37d1d22) Qt Version: 5.15.0 Kernel Version: 5.8.5-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 325205] Do not show contacts from disabled accounts in "show offline contacts" mode
https://bugs.kde.org/show_bug.cgi?id=325205 Siddhartha changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #3 from Siddhartha --- Closing old bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425405] systemsettings crashes when adding a new script to autostart
https://bugs.kde.org/show_bug.cgi?id=425405 Siddhartha changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Siddhartha --- Cannot reproduce this anymore. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425405] New: systemsettings crashes when adding a new script to autostart
https://bugs.kde.org/show_bug.cgi?id=425405 Bug ID: 425405 Summary: systemsettings crashes when adding a new script to autostart Product: systemsettings Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@sdht.in Target Milestone: --- Application: systemsettings5 (5.19.80) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.74.0 Operating System: Linux 5.8.1-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: I was testing out the new autostart implementation. On adding a new script, I'm getting a crash. I tried adding 2 "scripts" (Add.. -> Add login script", one a random .conf file and another .sh file. System settings crashes on selection both files, but after restarting, I can see that the .sh file has been added to the list. Another issue I noted is that "Add login script" is missing the option to select between pre-startup (~/.config/plasma-workspace/env) vs startup (~/.config/autostart-scripts). Is this expected or a regression? I depend on a pre-startup script to start a ssh-agent session. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7f968e4f3f8a in QUrl::path(QFlags) const () at /usr/lib/libQt5Core.so.5 #7 0x7f968e4f4246 in QUrl::fileName(QFlags) const () at /usr/lib/libQt5Core.so.5 #8 0x7f964b2411c6 in operator() (theJob=0x55a325fe7da0, __closure=0x55a32840a940) at /usr/include/qt/QtCore/qflags.h:121 #9 QtPrivate::FunctorCall, QtPrivate::List, void, AutostartModel::addScript(const QUrl&, AutostartModel::AutostartEntrySource):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #10 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #11 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x55a32840a930, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #12 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #13 0x7f968e9110aa in KJob::finished(KJob*, KJob::QPrivateSignal) (this=this@entry=0x55a325fe7da0, _t1=, _t1@entry=0x55a325fe7da0, _t2=...) at /usr/src/debug/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:555 #14 0x7f968e911cee in KJob::finishJob(bool) (this=0x55a325fe7da0, emitResult=) at /usr/src/debug/kcoreaddons/src/lib/jobs/kjob.cpp:93 #15 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #16 0x7f968e9111fd in KJob::result(KJob*, KJob::QPrivateSignal) (this=this@entry=0x55a326835390, _t1=, _t1@entry=0x55a326835390, _t2=...) at /usr/src/debug/build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #17 0x7f968e911d1c in KJob::finishJob(bool) (this=0x55a326835390, emitResult=) at /usr/src/debug/kcoreaddons/src/lib/jobs/kjob.cpp:96 #18 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #19 0x7f968c1937d6 in KIO::SlaveInterface::dispatch(int, QByteArray const&) (this=0x55a327528c50, _cmd=104, rawdata=...) at /usr/src/debug/kio/src/core/slaveinterface.cpp:149 #20 0x7f968c191f3a in KIO::SlaveInterface::dispatch() (this=0x55a327528c50) at /usr/src/debug/kio/src/core/slaveinterface.cpp:78 #21 0x7f968c195a3b in KIO::Slave::gotInput() (this=0x55a327528c50) at /usr/src/debug/kio/src/core/slave.cpp:402 #22 0x7f968e5e4a26 in () at /usr/lib/libQt5Core.so.5 #23 0x7f968e5da1d2 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7f968f1f6702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f968e5ad7ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f968e5b02a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #27 0x7f968e606cf4 in () at /usr/lib/libQt5Core.so.5 #28 0x7f968c2ae43c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #29 0x7f968c2fc1d9 in () at /usr/lib/libglib-2.0.so.0 #30 0x7f968c2ad221 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #31 0x7f968e606331 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f968e5ac13c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #33 0x7f968e5b45c4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #34 0x55a3248e1806 in main(int, char**) (argc=, argv=0x7ffcef914450) at /usr/src/debug/systemsettings/app/main.cpp:168 [Inferior 1 (process 30068) detached] Possible duplicates by query: bug 425205, bug 424644, bug 423766, bug 423719, bug 423459. Reported using DrKonqi -- You are receiving
[kdeplasma-addons] [Bug 425048] Picture of the day wallpaper is not loaded at startup if network is not available yet
https://bugs.kde.org/show_bug.cgi?id=425048 --- Comment #4 from Siddhartha --- Ah that could be it. /tmp on Archlinux is mounted as tmpfs, so loses everything after a restart. Isn't $XDG_CACHE_HOME a more appropriate place for storing such files? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425048] Picture of the day wallpaper is not loaded at startup if network is not available yet
https://bugs.kde.org/show_bug.cgi?id=425048 Siddhartha changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED --- Comment #2 from Siddhartha --- Cannot reproduce it with plasmashell --replace (wallpaper is set correctly), but can reproduce after a system restart (blank wallpaper for 10 minutes). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422934] Option to render (and/or otherwise make available) details about the picture of the day (potd) wallpaper
https://bugs.kde.org/show_bug.cgi?id=422934 Siddhartha changed: What|Removed |Added CC||k...@sdht.in --- Comment #2 from Siddhartha --- I'd like this feature very much. I frequently open bing.com manually to find out the details (location/background) of a particular wallpaper that looks amazing. Also, sometimes the wallpaper of a particular day is not attractive. An additional cool option would be to be able to load wallpapers from previous days, say using navigation arrows or a date picker on a widget, that'll allow the users to manually load historical wallpapers from an arbitrary day (provided the source supports accessing previous wallpapers, of course). -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425048] New: Picture of the day wallpaper is not loaded at startup
https://bugs.kde.org/show_bug.cgi?id=425048 Bug ID: 425048 Summary: Picture of the day wallpaper is not loaded at startup Product: kdeplasma-addons Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Picture of the Day Assignee: plasma-b...@kde.org Reporter: k...@sdht.in Target Milestone: --- SUMMARY At plasma startup, the Picture of the day wallpaper is not loaded and all the wallpapers are black. I suspect it happens because at startup, I need to unlock kwallet before the wifi can connect, which takes some time. Meanwhile, the wallpaper plugin must be trying to access the latest wallpaper, which would fail due to the lack of working internet. The wallpaper does come up properly within 10min (exactly), which must be the next time the plugin checks for an update? The plugin should use previously downloaded and cached wallpapers if it is unable to load one over the internet. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.80 (plasma-desktop-git r7774.27e1c236b-1) KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.11-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 425046] New: kscreen does not init multiple screens properly the first time
https://bugs.kde.org/show_bug.cgi?id=425046 Bug ID: 425046 Summary: kscreen does not init multiple screens properly the first time Product: KScreen Version: git Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: k...@sdht.in Target Milestone: --- Created attachment 130664 --> https://bugs.kde.org/attachment.cgi?id=130664=edit system and kscreen logs SUMMARY I have 2 external screens that I connect to my laptop using a USB-C dock. 1) When I connect the dock to the laptop, kscreen initially brings up plasma on all screens as expected. 2) But within seconds, the external screens are deinitialized (output stops and they turn off), while the laptop screen is frozen. I've to disconnect the dock to get the laptop screen responding again. 3) When I connect the dock again, this time the external screens are not initalized and I've to manually go and enable them from either the display settings or using the xrandr cli, after which the multiscreen setup works properly. 4) Sometimes, it takes multiple cycles of steps 1-3 to get the external screen to work. I've attached the system logs that shows 3-4 tries before I could get the screens working. All my plasma packages are git master. I'm willing to help debug this and try out patches to finally resolve this annoying bug that I face almost everyday. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.80 (kscreen-git r1266.65f342d-1) KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.11-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424389] Regression in "active screen follows mouse"
https://bugs.kde.org/show_bug.cgi?id=424389 --- Comment #4 from Siddhartha --- Yes, that is what I found as well. Fiddling with the settings removes the entry when I set the option to ON. Manually setting the entry to "true" in the config file and restarting kwin is a workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424389] Regression in "active screen follows mouse"
https://bugs.kde.org/show_bug.cgi?id=424389 --- Comment #2 from Siddhartha --- Thanks jukuc! That is correct. I see "Active screen follows mouse: no". So this is a regression in the kwin kcm, because it shows the option set to ON there? I'll use the workaround meanwhile (it works!). Do you still need the full support output? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424391] Add option to move windows to another screen
https://bugs.kde.org/show_bug.cgi?id=424391 --- Comment #1 from Siddhartha --- Note that I've set my task manager to only show windows from the current screen and the "Move to Screen" option will only affect the windows in one screen. For the default option where the task manager shows windows from all screens, not sure what the right semantics should be, but the simple action of moving all windows across all screens to only one screen could be one way to go. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424391] New: Add option to move windows to another screen
https://bugs.kde.org/show_bug.cgi?id=424391 Bug ID: 424391 Summary: Add option to move windows to another screen Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: k...@sdht.in CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Current task manager allows moving all windows in a group to another desktop with the Right Click context menu -> Move to Desktop. It'd be nice to have the same option for "Move to Screen" to move all windows in a group to another screen. Note that this option is already present for individual windows in the context menu of the title bar of windows. Should be easy to add this to the task manager menu as well. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.9-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 424390] New: Regression in handling custom shortcut commands
https://bugs.kde.org/show_bug.cgi?id=424390 Bug ID: 424390 Summary: Regression in handling custom shortcut commands Product: khotkeys Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@michael-jansen.biz Reporter: k...@sdht.in Target Milestone: --- SUMMARY Custom Shortcuts in Settings are unable to run commands like "kate" or "bash /path/to/script.sh args" no longer work and give an error. STEPS TO REPRODUCE 1. Create new shortcut in Shortcuts -> Custom Shortcuts -> New -> Global Shortcut -> Command/URL -> "kate" 2. Assign keys such as "Meta + U". 3. Invoke "Meta + U". OBSERVED RESULT Error message: "Unable to run the command specified. The file or folder bash kate does not exist." EXPECTED RESULT kate is started. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.80 (khotkeys-git r2010.52f4f8d) KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.7.9-arch1-1 ADDITIONAL INFORMATION Reverting commit 1d60f46f from this merge request https://invent.kde.org/plasma/khotkeys/-/merge_requests/1 brings back old behavior. It looks like KRun does not work with raw commands and needs to be updated to handle commands without an explicit schema, possibly here: https://invent.kde.org/frameworks/kio/-/blob/master/src/widgets/krun.cpp#L419 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424389] New: Regression in "active screen follows mouse"
https://bugs.kde.org/show_bug.cgi?id=424389 Bug ID: 424389 Summary: Regression in "active screen follows mouse" Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@sdht.in Target Milestone: --- SUMMARY New windows do not spawn on the screen which has the mouse, but instead spawns on the screen which contains the active window. STEPS TO REPRODUCE 1. Start plasma on > 1 screens. All screens have their own plasma panel with application menu. 2. Make sure "Active screen follows mouse" is ON in "Window management" in settings. 2. Start Dolphin on Screen 1 and make sure it is active. 3. Start another instance of Dolphin on Screen 2. OBSERVED RESULT Second instance of Dolphin starts on Screen 1. EXPECTED RESULT Second instance of Dolphin starts on Screen 2 which has the mouse. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.80 (kwin-git r18148.cf2712887) KDE Frameworks Version: 5.73.0 (git master) Qt Version: 5.15.0 Kernel Version: 5.7.9-arch1-1 ADDITIONAL INFORMATION This used to work before, and is a recent regression sometime in the last 2-4 weeks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424389] Regression in "active screen follows mouse"
https://bugs.kde.org/show_bug.cgi?id=424389 Siddhartha changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424295] New: Dolphin crashes when expanding and closing folders in tree view
https://bugs.kde.org/show_bug.cgi?id=424295 Bug ID: 424295 Summary: Dolphin crashes when expanding and closing folders in tree view Product: dolphin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@sdht.in CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.11.70) (Compiled from sources) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.7.8-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: It only happens sometimes and perhaps only when expanding and closing more than one folder. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Aborted Content of s_kcrashErrorMessage: (null) [KCrash Handler] #6 0x7fba3b874355 in raise () from /usr/lib/libc.so.6 #7 0x7fba3b85d853 in abort () from /usr/lib/libc.so.6 #8 0x7fba3b8b7878 in __libc_message () from /usr/lib/libc.so.6 #9 0x7fba3b8bed3a in malloc_printerr () from /usr/lib/libc.so.6 #10 0x7fba3b8c033d in _int_free () from /usr/lib/libc.so.6 #11 0x7fba3b780b9b in KFileItemModel::removeItems (behavior=KFileItemModel::DeleteItemData, itemRanges=..., this=0x55f50334a460) at /usr/src/debug/dolphin/src/kitemviews/kfileitemmodel.h:298 #12 KFileItemModel::removeItems (this=0x55f50334a460, itemRanges=..., behavior=KFileItemModel::DeleteItemData) at /usr/src/debug/dolphin/src/kitemviews/kfileitemmodel.cpp:1281 #13 0x7fba3b78c75e in KFileItemModel::setExpanded (this=0x55f50334a460, index=28, expanded=) at /usr/src/debug/dolphin/src/kitemviews/kitemrange.h:61 #14 0x7fba3b79c95b in KItemListController::mouseReleaseEvent (transform=..., event=0x7fff5e149250, this=0x55f5038b9b60) at /usr/src/debug/dolphin/src/kitemviews/kitemlistcontroller.cpp:783 #15 KItemListController::mouseReleaseEvent (this=0x55f5038b9b60, event=0x7fff5e149250, transform=...) at /usr/src/debug/dolphin/src/kitemviews/kitemlistcontroller.cpp:734 #16 0x7fba3b79f50b in KItemListController::processEvent (this=0x55f5038b9b60, event=0x7fff5e149250, transform=...) at /usr/src/debug/dolphin/src/kitemviews/kitemlistcontroller.cpp:1060 #17 0x7fba3b7af1cf in KItemListView::event (this=0x55f50342b7f0, event=0x7fff5e149250) at /usr/src/debug/dolphin/src/kitemviews/kitemlistview.cpp:917 #18 0x7fba3a51f702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #19 0x7fba399947ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x7fba3a844ed6 in ?? () from /usr/lib/libQt5Widgets.so.5 #21 0x7fba3a84528e in ?? () from /usr/lib/libQt5Widgets.so.5 #22 0x7fba3a84abbc in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #23 0x7fba3a857ac3 in QGraphicsScene::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #24 0x7fba3a51f702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #25 0x7fba399947ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #26 0x7fba3a874afa in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7fba3a560c7e in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #28 0x7fba3a60bf9f in QFrame::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #29 0x7fba39994523 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #30 0x7fba3a51f6f1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #31 0x7fba3a526977 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #32 0x7fba399947ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #33 0x7fba3a52585e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #34 0x7fba3a5793b2 in ?? () from /usr/lib/libQt5Widgets.so.5 #35 0x7fba3a57c78f in ?? () from /usr/lib/libQt5Widgets.so.5 #36 0x7fba3a51f702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #37 0x7fba399947ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #38 0x7fba39e2c37c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib/libQt5Gui.so.5 #39 0x7fba39e01b4c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/libQt5Gui.so.5 #40 0x7fba34aefc8c in ?? () from
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 --- Comment #12 from Siddhartha Sahu --- Created attachment 128112 --> https://bugs.kde.org/attachment.cgi?id=128112=edit New crash information added by DrKonqi yakuake (3.0.5+) using Qt 5.14.2 - What I was doing when the application crashed: Same as the other reports, yakuake crashes sometimes when a shell is closed using ctrl+d. -- Backtrace (Reduced): #6 0x7ff40ca2916f in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5 #7 0x7ff40e1b731e in KActionCollection::removeAssociatedWidget(QWidget*) () from /usr/lib/libKF5XmlGui.so.5 #8 0x7ff40e1ffebc in KXMLGUIClient::prepareXMLUnplug(QWidget*) () from /usr/lib/libKF5XmlGui.so.5 #9 0x7ff40e207440 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from /usr/lib/libKF5XmlGui.so.5 #10 0x7ff3fc506053 in Konsole::SessionController::~SessionController() () from /usr/lib/libkonsoleprivate.so.20 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake
https://bugs.kde.org/show_bug.cgi?id=415762 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 --- Comment #2 from Siddhartha Sahu --- Built from the latest master (commit on Feb 1): okular-git-r8658.c6d937ab0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 417118] New: Okular crashes on Print preview
https://bugs.kde.org/show_bug.cgi?id=417118 Bug ID: 417118 Summary: Okular crashes on Print preview Product: okular Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: sh.siddhar...@gmail.com Target Milestone: --- Application: okular (1.9.70) (Compiled from sources) Qt Version: 5.14.1 Frameworks Version: 5.67.0 Operating System: Linux 5.5.1-arch1-1 x86_64 Windowing system: X11 Distribution: Arch Linux -- Information about the crash: OPening File -> Print Preview on any pdf file (tried on 3 different ones) crashes Okular. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd296a50600 (LWP 59660))] Thread 7 (Thread 0x7fd28632f700 (LWP 59666)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7fd286b30700 (LWP 59665)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7fd27eb30700 (LWP 59664)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fd287331700 (LWP 59663)): #0 0x7fd299a94c45 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7fd287828dec in ?? () from /usr/lib/dri/i965_dri.so #2 0x7fd2878289e8 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #4 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fd28fdd3700 (LWP 59662)): #0 0x7fd29a5079ef in poll () from /usr/lib/libc.so.6 #1 0x7fd298f63120 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7fd298f631f1 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7fd29aac403c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fd29aa6a4cc in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7fd29a88ee52 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7fd29ad14b28 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7fd29a88ffc6 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #9 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fd295c67700 (LWP 59661)): #0 0x7fd29a5079ef in poll () from /usr/lib/libc.so.6 #1 0x7fd299d0e630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7fd299d102db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fd296634b81 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fd29a88ffc6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fd299a8e4cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7fd29a5122d3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fd296a50600 (LWP 59660)): [KCrash Handler] #6 0x7fd29b59a6a5 in QAction::setEnabled(bool) () from /usr/lib/libQt5Widgets.so.5 #7 0x7fd28eb1261f in PageView::updateActionState (this=0x55f58f3d05c0, haspages=haspages@entry=false, documentChanged=documentChanged@entry=false, hasformwidgets=hasformwidgets@entry=false) at /usr/src/debug/okular/ui/pageview.cpp:1268 #8 0x7fd28eaa6e18 in Okular::Part::Part (this=this@entry=0x55f58f38abb0, parentWidget=parentWidget@entry=0x7fffe4dade50, parent=parent@entry=0x7fffe4dade50, args=..., __in_chrg=, __vtt_parm=) at /usr/include/c++/9.2.0/bits/atomic_base.h:413 #9 0x7fd28eab00d4 in KPluginFactory::createPartInstance (parentWidget=0x7fffe4dade50, parent=0x7fffe4dade50, args=...) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:536 #10 0x7fd29bb308a5 in KPluginFactory::create (this=0x55f58ebb0dc0, iface=0x7fd29c295a18 "KParts::ReadOnlyPart", parentWidget=0x7fffe4dade50, parent=0x7fffe4dade50, args=..., keyword=...) at /usr/src/debug/kcoreaddons/src/lib/plugin/kpluginfactory.cpp:145 #11 0x7fd28ead58db in KPluginFactory::create
[frameworks-plasma] [Bug 397336] Tooltip timeout is too short and unalterable
https://bugs.kde.org/show_bug.cgi?id=397336 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #5 from Siddhartha Sahu --- This issue remains in plasma git master. I'd prefer tooltips to stay as long as the mouse is over the widgets. I have a bunch to timezones configured in the digital clock widget and face the short timeout issue when the tooltip showing the current time in different timezones closes while I'm still trying to lookup/process it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387901] Task manager loses windows with multi monitor
https://bugs.kde.org/show_bug.cgi?id=387901 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #6 from Siddhartha Sahu --- I am seeing the same issue on git master with the icon-only task manager configured to only show applications in current screen. Disconnecting my external screens does not reset the task manager state and I have to restart plasmashell as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 409285] New: Dolphin crash when copying files to pen drive
https://bugs.kde.org/show_bug.cgi?id=409285 Bug ID: 409285 Summary: Dolphin crash when copying files to pen drive Product: dolphin Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: sh.siddhar...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (19.07.70) (Compiled from sources) Qt Version: 5.12.4 Frameworks Version: 5.60.0 Operating System: Linux 5.1.15-arch1-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: Dragged and dropped a file to the flash drive entry in the dolphin pane and selected "copy file" -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8e461bbc80 (LWP 1680))] Thread 5 (Thread 0x7f8e37fff700 (LWP 1685)): #0 0x7f8e4e1d4667 in poll () from /usr/lib/libc.so.6 #1 0x7f8e496937c0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8e496938ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f8e4c16327c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f8e4c10a3ac in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f8e4bf459c5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f8e4bf46bf0 in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #8 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8e3dcb4700 (LWP 1684)): #0 0x7f8e4a5fa415 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8e3e169f7c in ?? () from /usr/lib/dri/i965_dri.so #2 0x7f8e3e169b78 in ?? () from /usr/lib/dri/i965_dri.so #3 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8e3700 (LWP 1683)): #0 0x7f8e4e1d018c in read () from /usr/lib/libc.so.6 #1 0x7f8e49641961 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8e49691f70 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f8e49693766 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f8e496938ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f8e4c16327c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f8e4c10a3ac in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f8e4bf459c5 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f8e4c3dfb37 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f8e4bf46bf0 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8e4518f700 (LWP 1682)): #0 0x7f8e4e1d4667 in poll () from /usr/lib/libc.so.6 #1 0x7f8e4a81d630 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f8e4a81f2db in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f8e45d80079 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f8e4bf46bf0 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f8e4a5f457f in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f8e4e1df0e3 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f8e461bbc80 (LWP 1680)): [KCrash Handler] #6 QSharedDataPointer::~QSharedDataPointer (this=0x555a9f40f6e0, __in_chrg=) at /usr/include/c++/9.1.0/bits/atomic_base.h:326 #7 KFileItem::~KFileItem (this=0x555a9f40f6e0, __in_chrg=) at /usr/src/debug/kio/src/core/kfileitem.h:47 #8 0x7f8e4db43433 in QList::node_destruct (this=0x555a9f0cde30, n=0x555a9f40f6e0) at /usr/include/qt/QtCore/qlist.h:452 #9 QList::erase (it=..., this=0x555a9f0cde30) at /usr/include/qt/QtCore/qlist.h:539 #10 KCoreDirListerCache::reinsert (oldUrl=..., item=..., this=0x7f8e4dbb2500 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at /usr/src/debug/kio/src/core/kcoredirlister_p.h:309 #11 KCoreDirListerCache::processPendingUpdates (this=0x7f8e4dbb2500 <(anonymous namespace)::Q_QGS_kDirListerCache::innerFunction()::holder>) at /usr/src/debug/kio/src/core/kcoredirlister.cpp:2014 #12 0x7f8e4c137460 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #13 0x7f8e4c1443f8 in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5 #14 0x7f8e4c137cd5 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #15 0x7f8e4cbdd485 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #16 0x7f8e4cbe69b1 in
[kdeconnect] [Bug 408399] Add pointer feature to slideshow remote plugin
https://bugs.kde.org/show_bug.cgi?id=408399 Siddhartha Sahu changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Siddhartha Sahu --- Found this was already reported. *** This bug has been marked as a duplicate of bug 403500 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 403500] Add a "laser pointer" in presentation mode
https://bugs.kde.org/show_bug.cgi?id=403500 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #1 from Siddhartha Sahu --- *** Bug 408399 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408399] New: Add pointer feature to slideshow remote plugin
https://bugs.kde.org/show_bug.cgi?id=408399 Bug ID: 408399 Summary: Add pointer feature to slideshow remote plugin Product: kdeconnect Version: unspecified Platform: Android OS: Android 9.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: sh.siddhar...@gmail.com Target Milestone: --- I loved the slideshow remote feature after discovering it recently. I can see this being a quick replacement for my hardware presenter, except for one missing feature: a pointer. It'd be great if the cursor control from the "remote input" plugin could be combined with "slideshow remote". * I don't know how hard this is, but on activating "slideshow remote", the mouse pointer on the laptop screen should change to a visible red dot similar to what google slides allows and how the laser in a hardware pointer works. Bonus if the color can be configured. * I tried navigating the normal mouse pointer using the "remote input" plugin, but the speed/acceleration of the pointer was that great. The combined plugin should allow easy navigation through the entire presentation screen area easily enough. (Using version 1.12.7 on Android currently) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408398] New: Inhibit screensaver plugin should take into account critical battery level settings
https://bugs.kde.org/show_bug.cgi?id=408398 Bug ID: 408398 Summary: Inhibit screensaver plugin should take into account critical battery level settings Product: kdeconnect Version: 1.3.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: sh.siddhar...@gmail.com Target Milestone: --- SUMMARY Currently, I like to use the inhibit screensaver plugin to disable screen locking when kdeconnect is active. However, this also disables the laptop suspend, even in battery mode. What I ideally want is to enable this feature, but if battery reaches a critical level, the power management settings should take over and the laptop should get suspended. STEPS TO REPRODUCE 1. Enable "Inhibit screensaver" plugin and connect phone to laptop. 2. Laptop lock screen is disabled 3. Turn off AC power for laptop until "critical level" as defined in power management settings is reached. OBSERVED RESULT Laptop does not suspend, as configured in settings and keeps running until it runs out of battery and forcefully shuts down. EXPECTED RESULT At critical level, power management settings should override kdeconnect and configured action (suspend in my case) should be performed. SOFTWARE/OS VERSIONS Linux/KDE Plasma KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.58.0 Qt Version: 5.12.3 ADDITIONAL INFORMATION I'm not 100% sure that this is due to the kdeconnect config, but I think the above is the current behavior. I do see the message "kdeconnect is currently inhibiting power management". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407473] Modify lock screen timeout behaviour for wrong passwords
https://bugs.kde.org/show_bug.cgi?id=407473 --- Comment #3 from Siddhartha Sahu --- I figured out one way to do this, and opened a RR at https://phabricator.kde.org/D21192. Please take a look and see if this makes sense. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407473] Modify lock screen timeout behaviour for wrong passwords
https://bugs.kde.org/show_bug.cgi?id=407473
--- Comment #2 from Siddhartha Sahu ---
Thanks Nate! So I did this and the text input doesn't get blocked anymore.
```
diff --git a/lookandfeel/contents/lockscreen/MainBlock.qml
b/lookandfeel/contents/lockscreen/MainBlock.qml
index 97e7e943..529ccea3 100644
--- a/lookandfeel/contents/lockscreen/MainBlock.qml
+++ b/lookandfeel/contents/lockscreen/MainBlock.qml
@@ -59,7 +59,6 @@ SessionManagementScreen {
focus: true
echoMode: TextInput.Password
inputMethodHints: Qt.ImhHiddenText | Qt.ImhSensitiveData |
Qt.ImhNoAutoUppercase | Qt.ImhNoPredictiveText
-enabled: !authenticator.graceLocked
revealPasswordButtonShown: true
onAccepted: {
@@ -93,6 +92,7 @@ SessionManagementScreen {
PlasmaComponents.Button {
id: loginButton
Layout.fillWidth: true
+enabled: !authenticator.graceLocked
text: i18nd("plasma_lookandfeel_org.kde.lookandfeel", "Unlock")
onClicked: startLogin()
```
I'm not sure what to change on line 88 that you linked. I guess another event
should replace "onClearPassword", maybe loginButton.onsubmit but I couldn't get
it to work yet.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 407473] New: Modify lock screen timeout behaviour for wrong passwords
https://bugs.kde.org/show_bug.cgi?id=407473 Bug ID: 407473 Summary: Modify lock screen timeout behaviour for wrong passwords Product: plasmashell Version: 5.15.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Lock/logout applet Assignee: plasma-b...@kde.org Reporter: sh.siddhar...@gmail.com Target Milestone: 1.0 Currently, the password input in the login/lock screen gets disabled for a timeout period after entering a wrong password. This is all good, but the behaviour can be slightly improved I think. Instead of disabling both the input field and the login button/action, just disable the login action, so that the user can continue to edit/retype the password while waiting for the timeout to expire. This way the user can save on some of the waiting time. Especially, by the time the user is done retyping, the timeout would have expired and the user can proceed to the login action. Apologies if there is already a way to do this easily or already been reported. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 404789] New: Refresh user application desktop files
https://bugs.kde.org/show_bug.cgi?id=404789 Bug ID: 404789 Summary: Refresh user application desktop files Product: plasmashell Version: 5.15.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: sh.siddhar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY On ArchLinux, changes to system desktop files are automatically rebuilt after each update by pacman. However, it is a little more difficult to change user desktop files. STEPS TO REPRODUCE 1. Make changes to user desktop files in ~/.local/share/applications OBSERVED RESULT Changes are not reflected in Kicker EXPECTED RESULT There should be a user visible way to refresh the entries. I know about kbuildsycoca5 after a web search, but I think from a usability perspective, there should be a graphical way to refresh the desktop files, maybe in the context menu or in the Menu editor. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55 Qt Version: 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 404110] Cannot auto-scroll the PDF preview anymore
https://bugs.kde.org/show_bug.cgi?id=404110 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Siddhartha Sahu --- It seems from the screenshot that "Live preview" is disabled, which is needed for auto-scroll and compile on save. Enable live preview, either using the button on the bottom of the window below the editor pane (below Next Latex Badbox in your screenshot) or from Build -> Live Preview menu, and try again. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 379865] Unable to type in Konsole using Tamil language input
https://bugs.kde.org/show_bug.cgi?id=379865 Siddhartha Sahu changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #1 from Siddhartha Sahu --- I just tried typing in tamil on konsole 18.08.2 and it works. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 346144] akonadi_launcher_agent crashes repeatedly
https://bugs.kde.org/show_bug.cgi?id=346144 Siddhartha Sahu <sh.siddhar...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 393413] Dolphin crash when previewing mp4
https://bugs.kde.org/show_bug.cgi?id=393413 Siddhartha Sahu <sh.siddhar...@gmail.com> changed: What|Removed |Added CC||sh.siddhar...@gmail.com --- Comment #1 from Siddhartha Sahu <sh.siddhar...@gmail.com> --- Do you get this crash consistently? Can you update your packages and check? I cannot reproduce this on Arch Linux (Dolphin 18.04.0 and Qt 5.10.1). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393352] New: Slow plasma startup
https://bugs.kde.org/show_bug.cgi?id=393352 Bug ID: 393352 Summary: Slow plasma startup Product: plasmashell Version: 5.12.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sh.siddhar...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112144 --> https://bugs.kde.org/attachment.cgi?id=112144=edit Bootchart showing plasma startup sequence Please find attached a bootchart showing my plasma startup. Steps: 1) Reboot and login to tty1. 2) Start systemd-bootchart: `/usr/lib/systemd/systemd-bootchart -o /tmp -r -n 1500 > /dev/null 2>&1 &` 3) `startx` (which is just `exec startkde`) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 346144] akonadi_launcher_agent crashes repeatedly
https://bugs.kde.org/show_bug.cgi?id=346144 --- Comment #3 from Siddhartha Sahu <sh.siddhar...@gmail.com> --- Hi Denis, You can close this bug report. I'm not using KMail at the moment. Thanks, Sid -- You are receiving this mail because: You are watching all bug changes.
