[kate] [Bug 486623] New: Opening this 909kb file in Kate causes it to leak memory and potentially crash the entire system
https://bugs.kde.org/show_bug.cgi?id=486623 Bug ID: 486623 Summary: Opening this 909kb file in Kate causes it to leak memory and potentially crash the entire system Classification: Applications Product: kate Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: i...@fdossena.com Target Milestone: --- Created attachment 169211 --> https://bugs.kde.org/attachment.cgi?id=169211=edit File that causes the leak SUMMARY The attached file is a config file from the game Colin McRae Rally 2005. I thought it would just be a text file so I tried opening it in Kate, it turned out to be a binary file, but instead of simply showing garbled text, Kate locks up, starts leaking memory and eventually gets killed by OOM (or crashes the whole system if you don't have OOM). STEPS TO REPRODUCE 1. Open Kate (or KWrite or any application like Ark that previews unknown files as text) 2. Drag the attached file into it 3. Watch RAM usage OBSERVED RESULT Kate freezes and fills up the entire memory EXPECTED RESULT Garbled text SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (Kernel 6.8.9-arch1-1) (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484334] New: Context menus, drop-down menus and tooltips sometimes open as separate windows in Wayland
https://bugs.kde.org/show_bug.cgi?id=484334 Bug ID: 484334 Summary: Context menus, drop-down menus and tooltips sometimes open as separate windows in Wayland Classification: Plasma Product: kwin Version: 6.0.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: i...@fdossena.com Target Milestone: --- Created attachment 167658 --> https://bugs.kde.org/attachment.cgi?id=167658=edit Screenshot of the issue SUMMARY Somtimes when a context menu, a drop-down menu or a tooltip is created, it opens in the middle of the screen as a fully decorated window that can be moved, maximised, etc. This only seems to happen under Wayland. STEPS TO REPRODUCE The problem can be easily triggered following these steps: 1. Open dolphin and right click on a file 2. Without closing the context menu, right click an empty area of the desktop 3. The plasmashell context menu opens as a separate window SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux amd64, Linux 6.8.1 (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION It's unlikely to be related, but I had to set QT_SCALE_FACTOR_ROUNDING_POLICY=round because plasmashell was all blurry on my PC after the upgrade to 6.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483832] Text not showing in browsers with Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483832 --- Comment #1 from Federico Kereki --- I managed to solve the problem. 1. Seeing that the display was correct in OpenBox, I tried creating a new user and logging with it; the browsers displayed tabs correctly. 2. Thinking that the problem could be in the browsers' configuration, I went back to me first user, removed the configuration (by renaming the ~/.cache corresponding directories) and tried the browsers again; still failing. 3. Thinking that the difference could be in KDE's configuration, I eventually thought of font handling. The standard font I was using was "ATKINSON HYPERLEGIBLE". I changed that font in the Systems Settings, and the browsers started displaying text correctly! KDE can use that font, but somehow Chromium/Brave cannot -- I don't know where's the issue or whose component's fault it is, but selecting a different font was the solution. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483832] New: Text not showing in browsers with Plasma 6
https://bugs.kde.org/show_bug.cgi?id=483832 Bug ID: 483832 Summary: Text not showing in browsers with Plasma 6 Classification: I don't know Product: kde Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: fker...@gmail.com Target Milestone: --- Created attachment 167366 --> https://bugs.kde.org/attachment.cgi?id=167366=edit Screen showing Brave browser, lacking text in tabs and menu SUMMARY *** I just updated OpenSUSE Tumbleweed to use Plasma 6, and text is not showing in Brave and Chrome browsers. *** STEPS TO REPRODUCE 1. Open Brave (or Chrome) 2. Visit some sites OBSERVED RESULT Tabs do not show text. For Brave browser, menu doesn't show text as well -- Chrome does show it. EXPECTED RESULT Tabs should show text, and menu as well. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION The bug doesn't appear in OpenBox, so it's a KDE-related thing. The bug didn't appear in Plasma 5 either, so it's a Plasma 6 issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] ScreenMapping entry in config file can grow infinitely due to lack of auto-removal of stale entries, which makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #47 from Federico Dossena --- No, this was fixed a while ago as far as I can tell. On 1/27/24 08:36, bugzilla_nore...@kde.org wrote: > https://bugs.kde.org/show_bug.cgi?id=469445 > > fanzhuyi...@gmail.com changed: > > What|Removed |Added > > CC||fanzhuyi...@gmail.com > > --- Comment #46 from fanzhuyi...@gmail.com --- > I can't seem to reproduce on plasma 6 RC1. Is this still a problem? > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473031] Thunderbird UI invisible/glitching after exiting a fullscreen application
https://bugs.kde.org/show_bug.cgi?id=473031 Federico Dossena changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DOWNSTREAM |--- --- Comment #3 from Federico Dossena --- I reported it here because it looks like a compositing issue that seems to be specific to KDE, version 115 introduced client side decorations so I thought it could be related. It's not something specific about my system either, I did a clean install of the OS and as soon as I added my accounts it started doing it again. I don't see reports of this issue on their side so I should probably report it there too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473031] Thunderbird UI invisible/glitching after exiting a fullscreen application
https://bugs.kde.org/show_bug.cgi?id=473031 --- Comment #1 from Federico Dossena --- Created attachment 160754 --> https://bugs.kde.org/attachment.cgi?id=160754=edit Another example -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473031] New: Thunderbird UI invisible/glitching after exiting a fullscreen application
https://bugs.kde.org/show_bug.cgi?id=473031 Bug ID: 473031 Summary: Thunderbird UI invisible/glitching after exiting a fullscreen application Classification: Plasma Product: kwin Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: i...@fdossena.com Target Milestone: --- Created attachment 160753 --> https://bugs.kde.org/attachment.cgi?id=160753=edit Screenshot of the invisible UI Since Thunderbird 115 came out if I leave it minimized then play a game or run any fullscreen application for a while, the UI becomes invisible or a glitchy mess. See attached screenshot. STEPS TO REPRODUCE 1. Launch Thunderbird 2. Minimize it 3. Launch a game, close it 4. Restore Thunderbird SOFTWARE/OS VERSIONS Linux: Kernel 6.4.8, Arch Linux, X11 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION The GPU is an AMD 6900xt and I'm running Mesa 23.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #17 from Federico Dossena --- As a temporary workaround for people who are affected by this bug, I just run this script at login and at logout: #!/bin/bash cd ~ sed -i /screenMapping=/d .config/plasma-org.kde.plasma.desktop-appletsrc It simply removes all the lines that contain "screenMapping=" from that file, it's a crappy workaround but it's better than having to reset my config every time it breaks, and it hasn't broken anything in the last couple of months that I've been using it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #9 from Federico Dossena --- Why did you mark this as fixed? That's a workaround, not a solution. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #3 from Federico Dossena --- That's exactly what I was doing, I work on wine, dxvk and vkd3d and have several folders where I build them regularly on my desktop. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470081] New: Desktop not loading after reboot, apps not starting, dmesg full of "comm: plasmashell, not enough memory for the allocation"
https://bugs.kde.org/show_bug.cgi?id=470081 Bug ID: 470081 Summary: Desktop not loading after reboot, apps not starting, dmesg full of "comm: plasmashell, not enough memory for the allocation" Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: i...@fdossena.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY This issue has been happening to me every few months for almost 2 years now and now it finally annoyed me enough to report it. Every now and then, after a reboot, all my desktop icons are gone, I can't launch any application from plasmashell, and dozens of GB of RAM are being used by it. When it happens, dmesg shows a lot of out of memory errors and restaring plasmashell has no effect: ``` comm: plasmashell, not enough memory for the allocation ``` To fix this I have no choice but to delete `~/.config/plasma-org.kde.plasma.desktop-appletsrc` and restart plasmashell, which resets all my desktop icons, the widgets, and the taskbar to their defaults, then the issue happens again after a few weeks, sometimes a few months. I took a look at my `~/.config/plasma-org.kde.plasma.desktop-appletsrc` file before deleting it and it had a line with almost 2 MILLION characters in the ScreenMapping section, with a really long list of files that have been on my desktop at some point (either directly or in a subdirectory) and aren't there anymore. I can't upload this file for privacy reasons unfortunately. This issue has happened to me on different distros and KDE versions over the years, not just arch, so it's either me doing something wrong or a plasmashell bug. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux amd64, Kernel 6.3.2 KDE Plasma Version: 5.27.5 from official repos KDE Frameworks Version: 5.106.0 from official repos Qt Version: 5.15.9 from official repos Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464871] Dynamic Brush Tool, Smoothing Problem (but not need restart)
https://bugs.kde.org/show_bug.cgi?id=464871 Federico changed: What|Removed |Added Platform|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 464871] New: Dynamic Brush Tool, Smoothing Problem (but not need restart)
https://bugs.kde.org/show_bug.cgi?id=464871 Bug ID: 464871 Summary: Dynamic Brush Tool, Smoothing Problem (but not need restart) Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: federicobarroso9...@gmail.com Target Milestone: --- I configure the Dynamic Brush Tool. But when I change the Freehand Brush Tool settings from the Tool Option (Brush Smoothing), close Krita and reopen them, the Dynamic Brush Tool works different, as if using the Smoothing Brush settings. Closing the document usually fixes it. STEPS TO REPRODUCE 1. Cinfigure Dynamic Brush Tool (Tool Option) 2. Configure Freehand Brush Tool (Tool Option; Brush Smoothing) 3. Close and open Krita 4. Dynamic Brush Tool Work diferent. OBSERVED RESULT The Brush Smoothing settings affect the Dynamic Brush Tool settings. From the Tool Option panel the Mass (and Drag) settings are unchanged, but the tool seems to work with the Brush Smoothing settings. EXPECTED RESULT Dynamic Brush Tool settings are not affected by other settings (Shoothing Brush) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Version (compiled): 5.12.12 Version (loaded): 5.12.12 ADDITIONAL INFORMATION Sometimes turning on the "Delay" option in the Tool Options of the Freehand Brush Tool causes this option to appear in the Dynamic Brush Tool. This is usually fixed by closing and opening the document, Luckily I don't need to restart Krita -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 463592] New: Problem "Paste into active layer"
https://bugs.kde.org/show_bug.cgi?id=463592 Bug ID: 463592 Summary: Problem "Paste into active layer" Classification: Applications Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: federicobarroso9...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Donload and use versión krita-nightly-x64-5.2.0-prealpha-8543a7d88c 2. then use version 5.2.0-prealpha (git a40c361) and then when using the option "Paste into active layer" it works incorrectly. In version 5.1.4 it no longer works OBSERVED RESULT downloading a new version or version nightly, causes the error of the option "paste into active layer" in previous versions EXPECTED RESULT Use New version or Nightly do not cause bugs to stable versions SOFTWARE/OS VERSIONS Windows: Window 10 KDE Plasma Version: 5.2.0-prealpha (git a40c361) KDE Frameworks Version: Qt Version:Version (compiled): 5.12.12 Version (loaded): 5.12.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 200564] Intergrate Ocrad into Okular for enhanced usage and increased accessibilty.
https://bugs.kde.org/show_bug.cgi?id=200564 Federico Calzoni changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Federico Calzoni --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 459842] New: Akonadi crash at user login on Fedora 36 Linux system
https://bugs.kde.org/show_bug.cgi?id=459842 Bug ID: 459842 Summary: Akonadi crash at user login on Fedora 36 Linux system Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: fbel...@iol.it Target Milestone: --- Application: akonadiserver (5.20.1 (22.04.1)) Qt Version: 5.15.5 Frameworks Version: 5.98.0 Operating System: Linux 5.19.11-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (Workstation Edition) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: The process akonadi was crash at user login. The user has the administrator rights. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted [KCrash Handler] #4 0x7f9d0ea6ac4c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7f9d0ea1a9c6 in raise () from /lib64/libc.so.6 #6 0x7f9d0ea047f4 in abort () from /lib64/libc.so.6 #7 0x556e0e0c8910 in akMessageHandler(QtMsgType, QMessageLogContext const&, QString const&) () #8 0x556e0e0d0bb2 in (anonymous namespace)::RemoteLogger::dbusLogger(QtMsgType, QMessageLogContext const&, QString const&) [clone .lto_priv.0] () #9 0x7f9d0ef11f78 in qt_message_print(QtMsgType, QMessageLogContext const&, QString const&) () from /lib64/libQt5Core.so.5 #10 0x7f9d0ef12098 in qt_message(QtMsgType, QMessageLogContext const&, char const*, __va_list_tag*) () from /lib64/libQt5Core.so.5 #11 0x7f9d0eee34dc in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #12 0x7f9d0eef7a36 in QObjectPrivate::QObjectPrivate(int) [clone .cold] () from /lib64/libQt5Core.so.5 #13 0x7f9d0f804e7f in QSQLiteDriverPlugin::create(QString const&) () from /usr/lib64/qt5/plugins/sqldrivers/libqsqlite3.so #14 0x7f9d0f4a6d9a in QSqlDatabasePrivate::init(QString const&) () from /lib64/libQt5Sql.so.5 #15 0x7f9d0f4a7165 in QSqlDatabase::addDatabase(QString const&, QString const&) () from /lib64/libQt5Sql.so.5 #16 0x556e0dfdb4a9 in Akonadi::Server::AkonadiServer::setupDatabase() () #17 0x556e0dfdd933 in Akonadi::Server::AkonadiServer::init() () #18 0x7f9d0f1042b4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f9d0f0da1fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f9d0f0dd584 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #21 0x7f9d0f12b457 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #22 0x7f9d0d343faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7f9d0d3992c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #24 0x7f9d0d341940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7f9d0f12af4a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #26 0x7f9d0f0d8c6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f9d0f0e0d32 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #28 0x556e0dfd6f88 in main () [Inferior 1 (process 2788) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456898] New: Not Paint in cambas
https://bugs.kde.org/show_bug.cgi?id=456898 Bug ID: 456898 Summary: Not Paint in cambas Product: krita Version: 5.0.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: federicobarroso9...@gmail.com Target Milestone: --- SUMMARYKrita Version: 5.0.6 Languages: es_US, es Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: arm64-little_endian-lp64 Build CPU: arm64 CPU: arm64 Kernel Type: linux Kernel Version: 4.19.113-24281538 Pretty Productname: Android (12.0) Product Type: android Product Version: 12.0 Desktop: OpenGL Info Vendor: "Qualcomm" Renderer: "Adreno (TM) 650" Version: "OpenGL ES 3.2 V@0502.0 (GIT@193b2ee, I593c16c433, 1633593732) (Date:10/07/21)" Shading language: "OpenGL ES GLSL ES 3.20" Requested format: QSurfaceFormat(version 2.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.2, 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.2 Supports deprecated functions false is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false Extensions: "GL_EXT_debug_marker" "GL_EXT_clip_cull_distance" "GL_OES_EGL_image" "GL_OES_EGL_image_external_essl3" "GL_EXT_clip_control" "GL_NV_shader_noperspective_interpolation" "GL_EXT_texture_filter_anisotropic" "GL_OES_get_program_binary" "GL_EXT_primitive_bounding_box" "GL_OES_depth_texture" "GL_OES_texture_3D" "GL_EXT_blit_framebuffer_params" "GL_EXT_texture_norm16" "GL_QCOM_YUV_texture_gather" "GL_EXT_tessellation_shader" "GL_EXT_external_buffer" "GL_QCOM_shader_framebuffer_fetch_rate" "GL_OES_surfaceless_context" "GL_EXT_shader_non_constant_global_initializers" "GL_OES_texture_storage_multisample_2d_array" "GL_OES_rgb8_rgba8" "GL_OES_texture_npot" "GL_OES_texture_float" "GL_EXT_shader_io_blocks" "GL_EXT_debug_label" "" "GL_EXT_texture_cube_map_array" "GL_EXT_copy_image" "GL_EXT_blend_func_extended" "GL_EXT_color_buffer_float" "GL_EXT_gpu_shader5" "GL_EXT_multisampled_render_to_texture2" "GL_QCOM_texture_foveated_subsampled_layout" "GL_OES_texture_float_linear" "GL_KHR_blend_equation_advanced" "GL_EXT_protected_textures" "GL_EXT_texture_format_sRGB_override" "GL_OES_framebuffer_object" "GL_EXT_shader_framebuffer_fetch" "GL_OES_vertex_half_float" "GL_KHR_blend_equation_advanced_coherent" "GL_OES_compressed_ETC1_RGB8_texture" "GL_EXT_EGL_image_array" "GL_OES_texture_stencil8" "GL_EXT_EGL_image_external_wrap_modes" "GL_OES_packed_depth_stencil" "GL_AMD_compressed_ATC_texture" "GL_KHR_debug" "GL_QCOM_texture_foveated" "GL_EXT_texture_sRGB_decode" "GL_EXT_EGL_image_storage" "GL_EXT_texture_format_BGRA" "GL_OES_depth24" "GL_EXT_robustness" "GL_OVR_multiview2" "GL_OES_EGL_sync" "GL_EXT_discard_framebuffer" "GL_OES_depth_texture_cube_map" "GL_EXT_texture_type_2_10_10_10_REV" "GL_KHR_texture_compression_astc_hdr" "GL_OES_texture_compression_astc" "GL_EXT_texture_buffer" "GL_KHR_no_error" "GL_EXT_texture_border_clamp" "GL_EXT_sRGB" "GL_OES_texture_half_float" "GL_OES_sample_variables" "GL_EXT_fragment_invocation_density" "GL_EXT_texture_sRGB_R8" "GL_OES_sample_shading" "GL_EXT_YUV_target" "GL_EXT_multisampled_render_to_texture" "GL_ARM_shader_framebuffer_fetch_depth_stencil" "GL_OES_EGL_image_external" "GL_OES_vertex_array_object" "GL_QCOM_validate_shader_binary" "GL_OVR_multiview_multisampled_render_to_texture" "GL_EXT_sRGB_write_control" "GL_EXT_color_buffer_half_float" "GL_OES_texture_half_float_linear" "GL_KHR_robust_buffer_access_behavior" "GL_EXT_geometry_shader" "GL_EXT_buffer_storage" "GL_OES_texture_view" "GL_EXT_read_format_bgra" "GL_QCOM_tiled_rendering" "GL_EXT_draw_buffers_indexed" "GL_EXT_memory_object_fd" "GL_ANDROID_extension_pack_es31a"
[Powerdevil] [Bug 454161] Brightness stuck at 30%
https://bugs.kde.org/show_bug.cgi?id=454161 Federico Cuello changed: What|Removed |Added CC||fe...@fedux.com.ar -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 452223] New: it is impossible to close kde partition manager until root permissions are granted
https://bugs.kde.org/show_bug.cgi?id=452223 Bug ID: 452223 Summary: it is impossible to close kde partition manager until root permissions are granted Product: partitionmanager Version: 21.12.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: federicocalzon...@gmail.com Target Milestone: --- SUMMARY once the program is started, root permissions are requested. At this point it is not possible to close the program until the password is entered. it is impossible to close the window that requires root permissions, and consequently it is impossible to close the other windows as they wait for the user to enter the password to grant permissions. STEPS TO REPRODUCE 1. Start KDE partition manager from Application Launcher 2. Click Cancel or the "X" in the window asking for root permission OBSERVED RESULT the window does not close and permissions are requested again EXPECTED RESULT since permissions have not been given the program should close SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.17.1-051701-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,1 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION I think it is possible to solve another bug ( https://bugs.kde.org/show_bug.cgi?id=312325 ) at the same time with a simple fix: similarly to G-Parted, before starting the program ask for permissions. if they are guaranteed then start the program otherwise terminate the process. By doing so, the permissions window will always be in the foreground -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 448942] New: Powerdevil does not call logind SetIdleHint on user idle
https://bugs.kde.org/show_bug.cgi?id=448942 Bug ID: 448942 Summary: Powerdevil does not call logind SetIdleHint on user idle Product: Powerdevil Version: 5.23.90 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nierr...@gmail.com Target Milestone: --- Currently, when user is idle, logind SetIdleHint method is not called. This is needed to communicate to any external utility that the desktop is in idle mode (eg: screen is dimmed). In this particular case, the feature is useful for my own [Clight](https://github.com/FedeDP/Clight) project (an utility to manage automatic brightness either using Ambient Light Sensors or webcams) to properly run using KDE dimmer (without using the dimmer provided by Clight itself), because it listens on IdleHint changes to understand when the automatic backlight calibration should be paused. Is this feasible? Thanks! Federico -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 446967] New: When annotating in spectacle the preview move instead of drawing
https://bugs.kde.org/show_bug.cgi?id=446967 Bug ID: 446967 Summary: When annotating in spectacle the preview move instead of drawing Product: Spectacle Version: 21.12.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: fedezotti...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When you annotate a screenshot and the preview is zoomed in, the drawing tool move the image instead of drawing on it. If you move very slowly you can trace a line for a small period of time. STEPS TO REPRODUCE 1. Take a screenshot with spectacle 2. Annotate 3. Draw with the pen OBSERVED RESULT The image (preview) move. EXPECTED RESULT The tool should draw. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.7-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443131] When there's more than one Kickoff, clicking on the old one causes search to be broken until you search with the new one
https://bugs.kde.org/show_bug.cgi?id=443131 Federico Cerutti changed: What|Removed |Added CC||feder...@ceres-c.it --- Comment #4 from Federico Cerutti --- I'm facing the same issue with plasmashell 5.23.1 and a dual display setup. I have "solved" the issue using the "Application Launcher" widget on the laptop and "Application Dashboard" on the external display. I think this might be somehow related to the keyboard shortcut feature since when I tried to delete both the Launchers, when I tried to assign the Alt-F1 shortcut to both of them I was forced to override the previous assignation. I'm not sure but this was not the case before this update, as far as I recall. Federico -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305534] Annotations don't show all non-ASCII letters
https://bugs.kde.org/show_bug.cgi?id=305534 Federico Calzoni changed: What|Removed |Added CC||federicocalzon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krename] [Bug 438868] New: Krename does not start
https://bugs.kde.org/show_bug.cgi?id=438868 Bug ID: 438868 Summary: Krename does not start Product: krename Version: 5.0.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: heiko.bec...@kde.org Reporter: federicocalzon...@gmail.com Target Milestone: --- Created attachment 139490 --> https://bugs.kde.org/attachment.cgi?id=139490=edit Test Krename SUMMARY if i try to start krename from the application launcher, the program doesn't start. instead if I start it from the terminal it works fine STEPS TO REPRODUCE 1. Try to start krename from GUI OBSERVED RESULT the app does not start. EXPECTED RESULT I expect the app to start properly SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-051300rc6-generic (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION Sometimes in the terminal log I show this warning. qt.qpa.wayland: Wayland does not support QWindow::requestActivate() I did a test with the krename --test command, I don't know if it will be useful. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438252] New: Add pinch-to-zoom and kinetic scroll support on Okular
https://bugs.kde.org/show_bug.cgi?id=438252 Bug ID: 438252 Summary: Add pinch-to-zoom and kinetic scroll support on Okular Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: federicocalzon...@gmail.com Target Milestone: --- SUMMARY When viewing a document, it would be nice to have the ability to use trackpad gestures such as pich-to-zoom to adjust the zoom. It would also be nice to implement kinetic scrolling OBSERVED RESULT pinch to zoom and kinetic scrolling have not yet been implemented EXPECTED RESULT The pinch-to-zoom gesture that works, and kinetic scrolling with the trackpad Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 OS Type: 64-bit Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 15,0 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435814] New: drag and drop folders and files to the location on the desktop where they drop
https://bugs.kde.org/show_bug.cgi?id=435814 Bug ID: 435814 Summary: drag and drop folders and files to the location on the desktop where they drop Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: federicocalzon...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 137654 --> https://bugs.kde.org/attachment.cgi?id=137654=edit example showing the "inconvenience" due to this lack. SUMMARY By dragging and dropping folders and files to the desktop, they are always placed in the first available slot. It would be nice and convenient for these to be positioned in the position where they are dropped. STEPS TO REPRODUCE 1. Select "Folder view" mode for the desktop 2. drag and drop a file by Dolphin to the desktop OBSERVED RESULT the file is placed in the first available space EXPECTED RESULT the file should be positioned where I drop it with the mouse. I want to place the icons where I prefer, to organize faster and better my works. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-49-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435739] New: pin a widget in the center of the panel, even in the presence of widgets of variable size on both sides
https://bugs.kde.org/show_bug.cgi?id=435739 Bug ID: 435739 Summary: pin a widget in the center of the panel, even in the presence of widgets of variable size on both sides Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: federicocalzon...@gmail.com Target Milestone: 1.0 SUMMARY In the presence of widgets with variable dimensions on both sides of the panel, it seems impossible to fix the position of a third widget exactly in the center: when one of the two widgets on the sides changes size, the widget in the center moves. STEPS TO REPRODUCE 1. add a new empty panel (in my case in the top border), add 2 widget of variable dimension, (like Global Menu, active window control, window app menu, or window buttons). In my case I have "Global menù" on the left corner and "window button" on the right (about window button, from the widget settings I have set it to disappear when the window is not maximized). 2. insert a third widget, in the center (in my case Digital clock) 3. add 2 spacer, one on each side: one to the left of the clock, and one to the right. if the spacers are flexible in size, we notice that when one of the widgets at the edges changes size (changing window in the case of the global menu or maximizing a window in the case of Window Button), the clock moves a little. if I set one of the two spacers to a fixed size or both to a fixed size I get worse results. OBSERVED RESULT The widget placed in the center moves with the change in size of the widgets at the edges, and it is not always centered in the center of the panel. EXPECTED RESULT The widget placed in the center remains fixed and exactly centered even if the size of the widgets at the edges changes. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-49-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435078] New: Direction of Wayland 4 finger gestures can't be modified from settings.
https://bugs.kde.org/show_bug.cgi?id=435078 Bug ID: 435078 Summary: Direction of Wayland 4 finger gestures can't be modified from settings. Product: systemsettings Version: 5.21.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: fede-...@outlook.com Target Milestone: --- SUMMARY Direction of Wayland 4 finger gestures can't be modified from settings. STEPS TO REPRODUCE 1. Go to System Settings -> Input Device -> Touchpad -> Invert Scroll Direction OBSERVED RESULT In Wayland, when changing the scroll direction it doesn't affect the direction of the 4 finger scroll to move from one desktop to another. EXPECTED RESULT The scroll direction between desktops should change when modifying that setting, or there should be an option to change the direction of those gestures somewhere else. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 153585] Akregator can't import OPML feedlist into toplevel direcotry
https://bugs.kde.org/show_bug.cgi?id=153585 Federico Ceccarelli changed: What|Removed |Added CC||ceccarelli.federico@gmail.c ||om Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Federico Ceccarelli --- I also stopped using Akregator, but since this request is 13 years old I think is safe to mark it as RESOLVED, at least just to not thinking about it anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 408059] Plasma-browser-integration should set CanSetFullscreen/FullScreen mpris2 property for videos
https://bugs.kde.org/show_bug.cgi?id=408059 --- Comment #4 from Federico --- > I cannot really know what the fullscreen button is. I imagined that could cause some troubles. > I just tried with vimeo which works fine. So maybe we can do this after all > and just have to live with the fact that sometimes it doesn't work as > expected. Setting this as confirmed. This is great, thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 408059] Plasma-browser-integration should set CanSetFullscreen/FullScreen mpris2 property for videos
https://bugs.kde.org/show_bug.cgi?id=408059 --- Comment #2 from Federico --- I think this surely is a stupid idea, so forgive me if it actually is...but what about just pressing fullscreen button from code when FullScreen=true is requested? This way it would be indistinguishable from a normal user "go-fullscreen" operation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 408059] New: Plasma-browser-integration should set CanSetFullscreen/FullScreen mpris2 property for videos
https://bugs.kde.org/show_bug.cgi?id=408059 Bug ID: 408059 Summary: Plasma-browser-integration should set CanSetFullscreen/FullScreen mpris2 property for videos Product: plasma-browser-integration Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: nierr...@gmail.com Target Milestone: --- SUMMARY org.mpris.MediaPlayer2 supports a CanSetFullScreen property that is very useful to distinguish between audio and video playing. I'd like plasma-browser-integration to provide the property together with its "FullScreen" counter-part. STEPS TO REPRODUCE 1. Start playing video in vlc 2. busctl --user introspect org.mpris.MediaPlayer2.vlc /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2 shows: .Quit method- - - .Raise method- - - .CanQuitproperty b true emits-change .CanRaise property b false emits-change .CanSetFullscreen property b true emits-change .DesktopEntry property s "vlc" emits-change .Fullscreen property b false emits-change writable .HasTrackList property b false emits-change .Identity property s "Lettore multimediale VLC" emits-change MORE... 3. Open a youtube video on firefox (same goes for chromium). 4. busctl --user introspect org.mpris.MediaPlayer2.plasma-browser-integration /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2 shows: .Quit method- - - .Raise method- - - .CanQuitproperty b false emits-change .CanRaise property b true emits-change .DesktopEntry property s "firefox" emits-change .HasTrackList property b false emits-change .Identity property s "Firefox Web Browser" emits-change .SupportedMimeTypes property as0 emits-change .SupportedUriSchemesproperty as0 emits-change OBSERVED RESULT No property "CanSetFullScreen" is provided. EXPECTED RESULT "CanSetFullScreen" provided for videos only. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION: Tested on Archlinux with kde 5.15.90 too. Still facing same "issue". -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 403054] GeoIP.dat.gz
https://bugs.kde.org/show_bug.cgi?id=403054 Federico Kereki changed: What|Removed |Added CC||fker...@gmail.com --- Comment #1 from Federico Kereki --- I can confirm that the bug also occurs in OpenSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385814] Some icons removed from the favorites list are back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Federico Cuello changed: What|Removed |Added CC||fe...@fedux.com.ar -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395035] dashboard launcher fail to switch some categories when you hover whit mouse pointer.
https://bugs.kde.org/show_bug.cgi?id=395035 Federico Acosta changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Federico Acosta --- Fixed in the last version of kde framework (5.47). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer
https://bugs.kde.org/show_bug.cgi?id=394993 --- Comment #7 from Federico Acosta --- when you send files from desktop computer to android device, transfer fails too but notification never come, nither computer, nither android device. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer
https://bugs.kde.org/show_bug.cgi?id=394993 --- Comment #6 from Federico Acosta --- when you send files from desktop computer to android device, transfer fails too... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395035] dashboard launcher fail to switch some categories when you hover whit mouse pointer.
https://bugs.kde.org/show_bug.cgi?id=395035 --- Comment #1 from Federico Acosta --- Created attachment 113082 --> https://bugs.kde.org/attachment.cgi?id=113082=edit demostration of bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395035] New: dashboard launcher fail to switch some categories when you hover whit mouse pointer.
https://bugs.kde.org/show_bug.cgi?id=395035 Bug ID: 395035 Summary: dashboard launcher fail to switch some categories when you hover whit mouse pointer. Product: plasmashell Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: acoguemo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 dashboard launcher fail to switch some categories when you hover whith mouse pointer. more details on video -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer
https://bugs.kde.org/show_bug.cgi?id=394993 --- Comment #5 from Federico Acosta --- Created attachment 113081 --> https://bugs.kde.org/attachment.cgi?id=113081=edit Video: Transfer progress forever -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394993] In recent beta version of kdeconncet android app, fails to send files from device to computer
https://bugs.kde.org/show_bug.cgi?id=394993 --- Comment #4 from Federico Acosta --- When the transfer starts, it fails instantaneously. However, in the desktop notifications, a progress bar appears that keeps oscillating from beginning to end without showing any progress. And it never ends, (it's been more than 2 hours) until I finish it from the desk with the stop button. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 394995] Digital clock applet show day selected, one day before than actually date.
https://bugs.kde.org/show_bug.cgi?id=394995 Federico Acosta changed: What|Removed |Added CC||acoguemo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 394995] Digital clock applet show day selected, one day before than actually date.
https://bugs.kde.org/show_bug.cgi?id=394995 --- Comment #2 from Federico Acosta --- *** Bug 394994 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 394994] Digital clock applet show day selected, one day before than actually date.
https://bugs.kde.org/show_bug.cgi?id=394994 Federico Acosta changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Federico Acosta --- *** This bug has been marked as a duplicate of bug 394995 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 394995] Digital clock applet show day selected, one day before than actually date.
https://bugs.kde.org/show_bug.cgi?id=394995 --- Comment #1 from Federico Acosta --- Created attachment 113039 --> https://bugs.kde.org/attachment.cgi?id=113039=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 394995] New: Digital clock applet show day selected, one day before than actually date.
https://bugs.kde.org/show_bug.cgi?id=394995 Bug ID: 394995 Summary: Digital clock applet show day selected, one day before than actually date. Product: kdeplasma-addons Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: acoguemo...@gmail.com Target Milestone: --- Digital clock applet show day selected, one day before than actually date. Diferent day on both. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 394994] New: Digital clock applet show day selected, one day before than actually date.
https://bugs.kde.org/show_bug.cgi?id=394994 Bug ID: 394994 Summary: Digital clock applet show day selected, one day before than actually date. Product: kdeplasma-addons Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: timer Assignee: plasma-b...@kde.org Reporter: acoguemo...@gmail.com Target Milestone: --- Created attachment 113038 --> https://bugs.kde.org/attachment.cgi?id=113038=edit Digital clock applet show day selected, one day before than actually date. Digital clock applet show day selected, one day before than actually date. Diferent day on both. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 394993] New: In recent beta version of kdeconncet android app, fails to send files from device to computer
https://bugs.kde.org/show_bug.cgi?id=394993 Bug ID: 394993 Summary: In recent beta version of kdeconncet android app, fails to send files from device to computer Product: kdeconnect Version: unspecified Platform: Android OS: Android 6.x Status: UNCONFIRMED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: acoguemo...@gmail.com Target Milestone: --- Created attachment 113037 --> https://bugs.kde.org/attachment.cgi?id=113037=edit screenshot from android device. In recent beta version of kdeconncet android app, fails to send files from device to computer. OS: Archlinux + Kde Plasma + KDE Connect version 1.3.1-1 + Kdeconnect android beta (last one). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 394727] Kirigami color scheme broken on a Gnome-based system
https://bugs.kde.org/show_bug.cgi?id=394727 --- Comment #4 from Federico Snobohm --- (In reply to Aleix Pol from comment #3) > Then this is maybe an issue with Kirigami integration with the GTK QStyle. > I'll send it to Kirigami maintainers so they can assess the importance of > the issue. Thank You very much. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394727] Cant see the apps text beacause the color
https://bugs.kde.org/show_bug.cgi?id=394727 --- Comment #2 from Federico Snobohm <federico_snob...@hotmail.com> --- (In reply to Aleix Pol from comment #1) > Make sure the color scheme you are using is correct. Discover, Kirigami and > QtQuick Controls 2 definitely support different color schemes. I tried changing the themes many times and it never change in Discover app, iam in Manjaro Cinnamon using vertex maia dark theme. (sorry for my english) Thanks -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 394727] New: Cant see the apps text beacause the color
https://bugs.kde.org/show_bug.cgi?id=394727 Bug ID: 394727 Summary: Cant see the apps text beacause the color Product: Discover Version: 5.12.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: federico_snob...@hotmail.com Target Milestone: --- Created attachment 112892 --> https://bugs.kde.org/attachment.cgi?id=112892=edit Discover How can i change the color of discover, i cant see nothing. thanks. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392456] New: Dolphin: does not update the search results when a file is deleted.
https://bugs.kde.org/show_bug.cgi?id=392456 Bug ID: 392456 Summary: Dolphin: does not update the search results when a file is deleted. Product: dolphin Version: 17.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: acoguemo...@gmail.com Target Milestone: --- Bug, or bad implementation on version: in all the versions. Hello, when I do a search in Dolphin, and it gives me a list of files. When you erase any of them, it keeps showing up. One would expect the search results to update and stop showing the file that has just been deleted. Greetings and excellent work. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 391080] New: KDE Connect Stop Working
https://bugs.kde.org/show_bug.cgi?id=391080 Bug ID: 391080 Summary: KDE Connect Stop Working Product: kde Version: 4.14.1 Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: federico_snob...@hotmail.com Target Milestone: --- I have a Xiaomi Redmi Note 5 with Miui 9 and KDE connect is stop working. i dont know why. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 --- Comment #4 from Federico <nierr...@gmail.com> --- I can't see any reverting patch here: https://git.archlinux.org/svntogit/packages.git/log/trunk?h=packages/kscreenlocker. The only patch i see is https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/kscreenlocker=3cde934f21af20462b85db6e36cc6a718b3c188f. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 --- Comment #2 from Federico <nierr...@gmail.com> --- Sorry, forgot that! $ pacman -Q kscreenlocker kscreenlocker 5.11.4-1 I'm on X11. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 388049] New: On lockscreen pasting user notes is not inhibited
https://bugs.kde.org/show_bug.cgi?id=388049 Bug ID: 388049 Summary: On lockscreen pasting user notes is not inhibited Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nierr...@gmail.com CC: bhus...@gmail.com, mgraess...@kde.org Target Milestone: --- While on lockscreen, pressing ctrl-v or clicking mid mouse button will copy selected text (if any) from clipboard. Then, it can be showed by pressing the "show" button. This is a privacy issue (i guess) as an extraneous person can access user clipboard (even if only most recent item). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385707] memcheck-amd64-linux crashing
https://bugs.kde.org/show_bug.cgi?id=385707 Federico Perez <perezfeder...@unc.edu.ar> changed: What|Removed |Added CC||perezfeder...@unc.edu.ar --- Comment #1 from Federico Perez <perezfeder...@unc.edu.ar> --- I need confirmation about if this corresponds to a bug. In that case I would like to solve it. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 385707] New: memcheck-amd64-linux crashing
https://bugs.kde.org/show_bug.cgi?id=385707 Bug ID: 385707 Summary: memcheck-amd64-linux crashing Product: valgrind Version: 3.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: perezfeder...@unc.edu.ar Target Milestone: --- Created attachment 108333 --> https://bugs.kde.org/attachment.cgi?id=108333=edit memcheck output Found this crash when debugging project. I think it's not a normal case. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 385561] New: Can't see the description of the software icons
https://bugs.kde.org/show_bug.cgi?id=385561 Bug ID: 385561 Summary: Can't see the description of the software icons Product: Planet KDE Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: ranveeraggar...@gmail.com Reporter: acoguemo...@gmail.com Target Milestone: --- Created attachment 108267 --> https://bugs.kde.org/attachment.cgi?id=108267=edit error Sometimes,this happen to me. Can't see the description of the software icons. Obviously, tha background is black, but the screenshot utility erase it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 384163] smplayer crashes at startup when using global menu + plasma QPA
https://bugs.kde.org/show_bug.cgi?id=384163 Federico <nierr...@gmail.com> changed: What|Removed |Added CC||nierr...@gmail.com --- Comment #4 from Federico <nierr...@gmail.com> --- I can reproduce same segfault on smplayer 17.9.0 on archlinux with qt 5.9.1, kde 5.10.5 with global menu enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379554] Packaging for Solus: Plasma Desktop refuses to show up
https://bugs.kde.org/show_bug.cgi?id=379554 --- Comment #1 from Federico Damián Schonborn <federicodamian...@gmail.com> --- Plasma is now included in the official repositories and works, please close this :D -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379554] New: Packaging for Solus: Plasma Desktop refuses to show up
https://bugs.kde.org/show_bug.cgi?id=379554 Bug ID: 379554 Summary: Packaging for Solus: Plasma Desktop refuses to show up Product: plasmashell Version: 5.9.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: federicodamian...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Hello KDE community! I'm having a problem to make Plasma Desktop fully run on Solus (https://solus-project.com). While I'm running the 'plasmashell' executable it does not give me any error, but also the desktop does not show up. I can enter to the Plasma session using LightDM, but after the splash animation I got a blank desktop with where only KRunner and KWin are working as expected. All details I can give: - I can run 'plasmawindowed' as a standalone program and as part of the KDEConnect Monitor in the MATE Desktop, but not 'plasmashell' (which also doesn't give me any output). - The Solus package sources are stored in their Git instance (https://git.solus-project.com). - My repository containing the Plasma Desktop package and the missing Framework needed to run it is stored in a GitHub repo (https://github.com/feddasch/top-secret). - The abi_* files in both sources are useful if you want to check for the libraries that the package builder loads as dependencies. - I have installed all the frameworks and Plasma components listed in both repositories. - This is the output of 'plasmashell' in a fresh MATE session: > casa@pandora ~> plasmashell > (plasmashell:1901): Gtk-WARNING **: Unable to locate theme engine in > module_path: "adwaita", > (plasmashell:1901): Gtk-WARNING **: Unable to locate theme engine in > module_path: "adwaita", > (plasmashell:1901): Gtk-WARNING **: Unable to locate theme engine in > module_path: "adwaita", > Invalid Context= "Apps" line for icon theme: > "/usr/share/icons/Arc/apps/symbolic/" > Invalid Context= "Mimetypes" line for icon theme: > "/usr/share/icons/Arc/mimetypes/symbolic/" > Invalid Context= "Mimetypes" line for icon theme: > "/usr/share/icons/Faba/symbolic/mimetypes/" > detected kglobalaccel restarting, re-registering all shortcut keys -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376868] New: Crash Plasma
https://bugs.kde.org/show_bug.cgi?id=376868 Bug ID: 376868 Summary: Crash Plasma Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: federico127...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.9-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - Unusual behavior I noticed: plasma has problem with 2 monitor. I use Nvidia GCard and VGA port The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fad64e42800 (LWP 1247))] Thread 18 (Thread 0x7fac6cd0f700 (LWP 4384)): #0 0x7fad5e5024ed in read () at /usr/lib/libc.so.6 #1 0x7fad514cff51 in pa_read () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fad51b6030e in pa_mainloop_prepare () at /usr/lib/libpulse.so.0 #3 0x7fad51b60d80 in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #4 0x7fad51b60e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #5 0x7fad51b6ee29 in () at /usr/lib/libpulse.so.0 #6 0x7fad514fefe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #7 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 17 (Thread 0x7fac6d610700 (LWP 3795)): #0 0x7fad514bc680 in pa_iochannel_is_readable@plt () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #1 0x7fad514ee617 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #2 0x7fad514ee989 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #3 0x7fad514ef20a in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #4 0x7fad51b6099c in pa_mainloop_dispatch () at /usr/lib/libpulse.so.0 #5 0x7fad51b60d9c in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #6 0x7fad51b60e40 in pa_mainloop_run () at /usr/lib/libpulse.so.0 #7 0x7fad51b6ee29 in () at /usr/lib/libpulse.so.0 #8 0x7fad514fefe8 in () at /usr/lib/pulseaudio/libpulsecommon-10.0.so #9 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 16 (Thread 0x7fac81f2c700 (LWP 3794)): #0 0x7fad5e50648d in poll () at /usr/lib/libc.so.6 #1 0x7fad59324786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fad5932489c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fad5ee2a06b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fad5edd389a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fad5ebf5a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fad61d2f025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fad5ebfa6d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 15 (Thread 0x7fac6f7fe700 (LWP 1274)): #0 0x7fad5dacb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad5ebfb58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7faca897d1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7faca89819d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7faca897c263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #5 0x7faca8981a32 in () at /usr/lib/libKF5ThreadWeaver.so.5 #6 0x7faca897c263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #7 0x7faca897f249 in ThreadWeaver::Thread::run() () at /usr/lib/libKF5ThreadWeaver.so.5 #8 0x7fad5ebfa6d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7fad5dac5454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fad5e50f7df in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7fac6700 (LWP 1273)): #0 0x7fad5dacb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fad5ebfb58b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7faca897d1d0 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5 #3 0x7faca89819d8 in () at /usr/lib/libKF5ThreadWeaver.so.5 #4 0x7faca897c263 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
[plasmashell] [Bug 376738] New: Plasma crash
https://bugs.kde.org/show_bug.cgi?id=376738 Bug ID: 376738 Summary: Plasma crash Product: plasmashell Version: 5.9.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: federico127...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.2) Qt Version: 5.8.0 Frameworks Version: 5.31.0 Operating System: Linux 4.9.9-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: error in laptop pc with second monitor on power on The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f305df5a800 (LWP 904))] Thread 8 (Thread 0x7f2f8f666700 (LWP 1082)): #0 0x7f305243c2e2 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #1 0x7f305243c7f0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f305243c89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3057f4206b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3057eeb89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3057d0da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f2f91f380a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7f3057d126d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f3056bdd454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f30576277df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7f2fa52c0700 (LWP 1073)): #0 0x7f305761e48d in poll () at /usr/lib/libc.so.6 #1 0x7f305243c786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7f305243c89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3057f4206b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3057eeb89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3057d0da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f305b9fafd6 in () at /usr/lib/libQt5Quick.so.5 #7 0x7f3057d126d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f3056bdd454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f30576277df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7f3033fff700 (LWP 1072)): #0 0x7f3056be310f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f305d6ef234 in () at /usr/lib/libQt5Script.so.5 #2 0x7f305d6ef279 in () at /usr/lib/libQt5Script.so.5 #3 0x7f3056bdd454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7f30576277df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7f303df71700 (LWP 1058)): #0 0x7f3052481db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f305243bed1 in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #2 0x7f305243c6f8 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f305243c89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3057f4206b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3057eeb89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7f3057d0da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7f305ae47025 in () at /usr/lib/libQt5Qml.so.5 #8 0x7f3057d126d8 in () at /usr/lib/libQt5Core.so.5 #9 0x7f3056bdd454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7f30576277df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7f303f9d1700 (LWP 1015)): #0 0x7f3052481dd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0 #1 0x7f305243c69e in () at /usr/lib/libglib-2.0.so.0 #2 0x7f305243c89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7f3057f4206b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7f3057eeb89a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3057d0da73 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7f305ae47025 in () at /usr/lib/libQt5Qml.so.5 #7 0x7f3057d126d8 in () at /usr/lib/libQt5Core.so.5 #8 0x7f3056bdd454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7f30576277df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7f30455e8700 (LWP 978)): #0 0x7f3052481db9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0 #1 0x7f305243bed1 in g_main_context_query () at /usr/lib/libglib-2.0.so.0 #2 0x7f305243c6f8 in () at /usr/lib/libglib-2.0.so.0 #3 0x7f305243c89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7f3057f4206b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7f3057eeb89a in
[krunner] [Bug 376278] Add a searchable command palette for current window inside krunner
https://bugs.kde.org/show_bug.cgi?id=376278 --- Comment #2 from Federico <nierr...@gmail.com> --- Well, we can always fallback to "menu button in titlebar" that does not adds any vertical space and it is quite hidden), if that's the case. By the way it would really be a nice improvement! -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 376278] New: Add a searchable command palette for current window inside krunner
https://bugs.kde.org/show_bug.cgi?id=376278 Bug ID: 376278 Summary: Add a searchable command palette for current window inside krunner Product: krunner Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: windows Assignee: k...@privat.broulik.de Reporter: nierr...@gmail.com Target Milestone: --- Hi everyone! This is only a wish: it would be wonderful if something like a "search through current window menu" would be added to krunner. I think this can really improve UX (much more than 5.9 global menu). There is a project aiming the same for gtk: https://github.com/p-e-w/plotinus. As menus are already exported to external resources (eg global menu applet), i don't think it is too hard to implement something like this (but i may be wrong). Thanks for your work! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374996] Global menu should not take up space when no menu are shown
https://bugs.kde.org/show_bug.cgi?id=374996 --- Comment #2 from Federico <nierr...@gmail.com> --- Thanks! This was really fast! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374997] When global menu is added on bottom bar, submenus cannot be properly seen
https://bugs.kde.org/show_bug.cgi?id=374997 --- Comment #2 from Federico <nierr...@gmail.com> --- Created attachment 103394 --> https://bugs.kde.org/attachment.cgi?id=103394=edit Menu correctly shown Here you can see that on second click, menu is correctly shown. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374997] When global menu is added on bottom bar, submenus cannot be properly seen
https://bugs.kde.org/show_bug.cgi?id=374997 --- Comment #1 from Federico <nierr...@gmail.com> --- Mmh it seems that on second click on same submenu object, it correctly shows submenu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374997] New: When global menu is added on bottom bar, submenus cannot be properly seen
https://bugs.kde.org/show_bug.cgi?id=374997 Bug ID: 374997 Summary: When global menu is added on bottom bar, submenus cannot be properly seen Product: plasmashell Version: 5.8.95 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: nierr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 103393 --> https://bugs.kde.org/attachment.cgi?id=103393=edit Here you can see "File" submenu" is cutted A screenshot is worth 100 words. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374996] New: Global menu should not take up space when no menu are shown
https://bugs.kde.org/show_bug.cgi?id=374996 Bug ID: 374996 Summary: Global menu should not take up space when no menu are shown Product: plasmashell Version: 5.8.95 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: nierr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 103392 --> https://bugs.kde.org/attachment.cgi?id=103392=edit You can see that ugly wasted space on panel Something like https://bugs.kde.org/show_bug.cgi?id=262148 but for plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374995] New: Global menu applet is not "cleared" after window is closed
https://bugs.kde.org/show_bug.cgi?id=374995 Bug ID: 374995 Summary: Global menu applet is not "cleared" after window is closed Product: plasmashell Version: 5.8.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Global Menu Assignee: k...@privat.broulik.de Reporter: nierr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 103391 --> https://bugs.kde.org/attachment.cgi?id=103391=edit You can see that no windows are present, but global menu is still there As title said, sometimes global menu is not cleared after a window, eg konsole, is closed. In attachment, screenshot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372271] New: Black screen on dual monitor
https://bugs.kde.org/show_bug.cgi?id=372271 Bug ID: 372271 Summary: Black screen on dual monitor Product: plasmashell Version: 5.8.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: federico127...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.5-2-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Boot the PC - Unusual behavior I noticed: Dual monitor (via VGA) crash Plasma. The second monitor (of Laptop) is black. I have different background for these monitor. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb9449e0800 (LWP 2124))] Thread 8 (Thread 0x7fb87cdbc700 (LWP 2290)): #0 0x7fb93e0f448d in poll () at /usr/lib/libc.so.6 #1 0x7fb9393bc786 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb9393bc89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb93ea1672b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb93e9c023a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb87f2e80a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fb93e7e7d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fb88c1ad700 (LWP 2281)): #0 0x7fb9393bbc95 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #1 0x7fb9393bc6ab in () at /usr/lib/libglib-2.0.so.0 #2 0x7fb9393bc89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fb93ea1672b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fb93e9c023a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fb9426e5856 in () at /usr/lib/libQt5Quick.so.5 #7 0x7fb93e7e7d78 in () at /usr/lib/libQt5Core.so.5 #8 0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fb916fac700 (LWP 2280)): #0 0x7fb93d8fd10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fb944175ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fb944175b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fb924d60700 (LWP 2279)): #0 0x7fb93ea15e73 in () at /usr/lib/libQt5Core.so.5 #1 0x7fb9393bbc89 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fb9393bc6ab in () at /usr/lib/libglib-2.0.so.0 #3 0x7fb9393bc89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fb93ea1672b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fb93e9c023a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fb941b462d5 in () at /usr/lib/libQt5Qml.so.5 #8 0x7fb93e7e7d78 in () at /usr/lib/libQt5Core.so.5 #9 0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fb9267c0700 (LWP 2218)): #0 0x7fb93e7def22 in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x7fb93ea16009 in () at /usr/lib/libQt5Core.so.5 #2 0x7fb9393bc179 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fb9393bc724 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fb9393bc89c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fb93ea1672b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fb93e9c023a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fb93e7e30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fb941b462d5 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fb93e7e7d78 in () at /usr/lib/libQt5Core.so.5 #10 0x7fb93d8f7454 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fb93e0fd7df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fb927fff700 (LWP 2175)): #0 0x7fb93e7def20 in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x7fb93ea15e9f in () at
[plasmashell] [Bug 368469] New: Configuration for second monitor gets lost
https://bugs.kde.org/show_bug.cgi?id=368469 Bug ID: 368469 Summary: Configuration for second monitor gets lost Product: plasmashell Version: 5.7.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: fker...@gmail.com CC: bhus...@gmail.com I have a dual monitor setup. After logging out, on the next log in, the configuration for the leftmost monitor is applied to the rightmost one, and the leftmost monitor is set to standard (desktop view, default wallpaper) instead of my settings. Widgets that were on the leftmost desktop now appear on the rightmost one. Reproducible: Always Steps to Reproduce: 1. set up two monitors with distinct configurations 2. log out 3. log in again Actual Results: The configuration for the monitor on the left will be applied to the monitor on the right The monitor on the left will be set to default Expected Results: I expected both monitors to be set as I had left them before logging out. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359831] Glide effect doesn't filter minimized windows
https://bugs.kde.org/show_bug.cgi?id=359831 --- Comment #2 from Federico <nierr...@gmail.com> --- Thank you very much for the fix :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 359831] New: Avoid closing animation if application is minimized
https://bugs.kde.org/show_bug.cgi?id=359831 Bug ID: 359831 Summary: Avoid closing animation if application is minimized Product: kwin Version: 5.5.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: nierr...@gmail.com As title says: i noted that "glide" closing animation is drawed even for minimized applications (eg: open konsole, minimize it, close it). I think that minimized applications should be blacklisted from the animation. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled
https://bugs.kde.org/show_bug.cgi?id=358610 --- Comment #3 from Federico Lorenzi <flore...@gmail.com> --- I posted a link to a Reddit thread: https://www.reddit.com/r/kde/comments/31s438/plasma_52_flickering_on_short_alttab/ that has my original YouTube video showing the problem in Plasma 5.2 ( https://www.youtube.com/watch?v=NJPUF8iT0UY ), as well as a few "me toos". I've taken some new videos now (on the exact machine that the support info is from): Showing the bug (Show selected window enabled): https://www.youtube.com/watch?v=b-05weuHDUM=youtu.be (slow speed) https://www.youtube.com/watch?v=Pa2YjI-ikMA=youtu.be (normal speed) Not showing the bug (Show selected window disabled): https://www.youtube.com/watch?v=n8IZLYs3D0A=youtu.be (normal speed) https://www.youtube.com/watch?v=BF_7qM0-QVA=youtu.be (slow speed) The behavior mirrors what I see exactly (ie, there are no screen recording artifacts). I'm not sure what you mean about the flicker being persistent? It happens every time I alt-tab, but once it has happened (ie, done alt-tabbing) everything is normal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358610] alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled
https://bugs.kde.org/show_bug.cgi?id=358610 --- Comment #2 from Federico Lorenzi <flore...@gmail.com> --- Created attachment 96863 --> https://bugs.kde.org/attachment.cgi?id=96863=edit Output of qdbus org.kde.KWin /KWin supportInformation This is the output from my desktop, running the binary Nvidia drivers. However, the exact same problem appears on my laptop (using the open source Intel drivers). Tweaking VSync / Compositor settings don't seem to make a difference (it still happens with XRender compositing). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358610] New: alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled
https://bugs.kde.org/show_bug.cgi?id=358610 Bug ID: 358610 Summary: alt-tab dialog flickers if aborted during animation and "Show selected window" is enabled Product: kwin Version: 5.5.3 Platform: Archlinux Packages URL: https://www.reddit.com/r/kde/comments/31s438/plasma_52 _flickering_on_short_alttab/ OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: effects-tabbox Assignee: kwin-bugs-n...@kde.org Reporter: flore...@gmail.com When "Show selected window" is enabled under system settings, weird artifacts can be observed on the alt-tab switcher. They seem to happen all the time when you don't let the switcher finish animating before releasing alt-tab, and also seem to happen if you release alt-tab while the slide animation of the box is happening This seems to have been a problem since at least Plasma 5.2, and doesn't seem to depend heavily on drivers or other specific configuration (see attached reddit thread) It is most noticeable on the Breeze switcher, but does appear to happen on other similar style switchers too (large thumbnails, details). Turning off "Show selected window" seems to completely fix the problem for me. Reproducible: Always Steps to Reproduce: 1. Press alt-tab quickly, slow enough that the dialog appears, but quick enough that it doesn't fully fade in - OR - 2. Press alt-tab normally, cycle through windows, while the highlighted window is changing, release alt-tab Actual Results: The alt-tab switcher fades out a bit, then fades in, then fades out. Happens very quickly, so it looks like flickering. Expected Results: The alt-tab switcher smoothly fades out -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358156] Clock doesn't update after switching back from tty
https://bugs.kde.org/show_bug.cgi?id=358156 --- Comment #2 from Federico Kereki <fker...@gmail.com> --- Created attachment 96708 --> https://bugs.kde.org/attachment.cgi?id=96708=edit Display after changing font properties Display after changing some font properties (in this case, I opted for bold text) All digits are back again. Changing to italics also works. If you go back to the original font settings, digits disappear as earlier. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358156] New: Clock doesn't update after switching back from tty
https://bugs.kde.org/show_bug.cgi?id=358156 Bug ID: 358156 Summary: Clock doesn't update after switching back from tty Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: mklape...@kde.org Reporter: fker...@gmail.com CC: plasma-b...@kde.org I opened a console with ALT+CTRL+F1. I left it open. After a (longish) while, I went back with ALT+CTRL+F7. The clock date was missing some digits. This also happens (sometimes) in the system tray. Also, sometimes digits are missing in the time itself. Reproducible: Sometimes Steps to Reproduce: 1. Switch to tty with ALT+CTRL+F1 2. Wait (possibly a while) 3. Switch back with ALT+CTRL+F7 Actual Results: Clock time or clock date is missing some digits. Expected Results: All digits (time, date) should have appeared. If you change font attributes (for example, apply bold or italics, or remove those if already checked) display goes back to normal. However, if you go back to the original font settings, digits will be missing again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358156] Clock doesn't update after switching back from tty
https://bugs.kde.org/show_bug.cgi?id=358156 --- Comment #1 from Federico Kereki <fker...@gmail.com> --- Created attachment 96707 --> https://bugs.kde.org/attachment.cgi?id=96707=edit Display after switching back, with digits missing This is a partial screenshot, after having gone back with ALT+CTRL+F7. In this case, digits are missing in the date part. (Other times, digits are missing in the time part.) I had switched to tty the night before. Next morning, I switched back. -- You are receiving this mail because: You are watching all bug changes.
