[kwin] [Bug 488560] OBS shows an encoding error using NVENC with NVIDIA GTX 1060 under Wayland with pipewire
https://bugs.kde.org/show_bug.cgi?id=488560 --- Comment #5 from Juan --- i also didn't change any settings between the two. After getting errors on Plasma 6.0.90/6.1 i went directly downgraded Arch packages and went back to 6.0.5 to try again. I don't know the reason for this... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488560] OBS shows an encoding error using NVENC with NVIDIA GTX 1060 under Wayland with pipewire
https://bugs.kde.org/show_bug.cgi?id=488560 --- Comment #3 from Juan --- (In reply to Vlad Zahorodnii from comment #2) > Can you post the obs logs when running on plasma 6.0.5? Sure thing https://drive.google.com/file/d/1icUyeadIURs-BnMbc9TyANr-W8yhGFh5/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488560] OBS shows an encoding error using NVENC with NVIDIA GTX 1060 under Wayland with pipewire
https://bugs.kde.org/show_bug.cgi?id=488560 Juan changed: What|Removed |Added Alias||NVIDIA-OBS -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488560] OBS shows an encoding error using NVENC with NVIDIA GTX 1060 under Wayland with pipewire
https://bugs.kde.org/show_bug.cgi?id=488560 --- Comment #1 from Juan --- Also reported the bug on NVIDIA forums: https://forums.developer.nvidia.com/t/obs-doesnt-work-on-nvidia-drivers-555-using-a-gtx-1060-3gb-under-wayland/296529 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488560] New: OBS shows an encoding error using NVENC with NVIDIA GTX 1060 under Wayland with pipewire
efault) 16:06:57.686: [Loaded global audio device]: 'Desktop Audio' 16:06:57.687: pulse-input: Server name: 'PulseAudio (on PipeWire 1.0.7) 15.0.0' 16:06:57.687: pulse-input: Audio format: s32le, 48000 Hz, 2 channels 16:06:57.687: pulse-input: Started recording from 'alsa_output.pci-_01_00.1.hdmi-stereo.monitor' (default) 16:06:57.687: [Loaded global audio device]: 'Mic/Aux' 16:06:57.687: PipeWire initialized 16:06:57.689: Switched to scene 'Scene' 16:06:57.689: 16:06:57.689: Loaded scenes: 16:06:57.689: - scene 'Scene': 16:06:57.689: - source: 'Screen Capture (PipeWire)' (pipewire-desktop-capture-source) 16:06:57.689: 16:06:57.783: [pipewire] Screencast session created 16:06:57.831: [pipewire] Asking for desktop 16:06:58.254: adding 21 milliseconds of audio buffering, total audio buffering is now 21 milliseconds (source: Desktop Audio) 16:06:58.254: 16:06:58.574: adding 64 milliseconds of audio buffering, total audio buffering is now 85 milliseconds (source: Mic/Aux) 16:06:58.574: 16:06:59.037: [pipewire] desktop selected, setting up screencast 16:06:59.041: [pipewire] Server version: 1.0.7 16:06:59.041: [pipewire] Library version: 1.0.7 16:06:59.041: [pipewire] Header version: 1.0.5 16:06:59.045: [pipewire] Created stream 0x63d00987f270 16:06:59.046: [pipewire] Stream 0x63d00987f270 state: "connecting" (error: none) 16:06:59.046: [pipewire] Playing stream 0x63d00987f270 16:06:59.047: [pipewire] Stream 0x63d00987f270 state: "paused" (error: none) 16:06:59.056: [pipewire] Negotiated format: 16:06:59.056: [pipewire] Format: 12 (Spa:Enum:VideoFormat:BGRA) 16:06:59.056: [pipewire] Modifier: 0x0 16:06:59.056: [pipewire] Size: 1920x1080 16:06:59.056: [pipewire] Framerate: 0/1 16:06:59.056: [pipewire] Negotiated format: 16:06:59.056: [pipewire] Format: 12 (Spa:Enum:VideoFormat:BGRA) 16:06:59.056: [pipewire] Modifier: 0x34fe014 16:06:59.056: [pipewire] Size: 1920x1080 16:06:59.056: [pipewire] Framerate: 0/1 16:06:59.058: [pipewire] Stream 0x63d00987f270 state: "streaming" (error: none) 16:09:02.579: - 16:09:02.580: [FFmpeg NVENC encoder: 'simple_video_recording'] settings: 16:09:02.580: encoder: NVIDIA NVENC H.264 (FFmpeg) 16:09:02.580: rate_control: CQP 16:09:02.580: bitrate: 0 16:09:02.580: cqp: 23 16:09:02.580: keyint: -1 16:09:02.580: preset: p5 16:09:02.580: tuning: hq 16:09:02.580: multipass:qres 16:09:02.580: profile: high 16:09:02.580: width:1920 16:09:02.580: height: 1080 16:09:02.580: b-frames: 2 16:09:02.580: psycho-aq:1 16:09:02.580: GPU: 0 16:09:02.580: 16:09:02.967: [NVENC encoder] nvenc_create_internal failed, trying again without Psycho Visual Tuning 16:09:02.967: - 16:09:02.968: [FFmpeg NVENC encoder: 'simple_video_recording'] settings: 16:09:02.968: encoder: NVIDIA NVENC H.264 (FFmpeg) 16:09:02.968: rate_control: CQP 16:09:02.968: bitrate: 0 16:09:02.968: cqp: 23 16:09:02.968: keyint: -1 16:09:02.968: preset: p5 16:09:02.968: tuning: hq 16:09:02.968: multipass:qres 16:09:02.968: profile: high 16:09:02.968: width:1920 16:09:02.968: height: 1080 16:09:02.968: b-frames: 2 16:09:02.968: psycho-aq:0 16:09:02.968: GPU: 0 16:09:02.968: 16:09:03.094: libfdk_aac encoder created 16:09:03.094: libfdk_aac bitrate: 192, channels: 2 16:09:03.124: Recording Start === 16:09:03.124: [ffmpeg muxer: 'simple_file_output'] Writing file '/home/juan/Videos/OBS/2024-06-14_16-09-02.mkv'... 16:09:04.842: OpenType support missing for "Open Sans", script 11 16:09:04.852: OpenType support missing for "Open Sans", script 12 16:09:04.857: OpenType support missing for "Open Sans", script 16 16:09:04.861: OpenType support missing for "Open Sans", script 20 16:09:24.975: [NVIDIA NVENC H.264 (FFmpeg) encoder: 'simple_video_recording'] Encoding queue duration surpassed 5 seconds, terminating encoder 16:09:24.975: Error encoding with encoder 'simple_video_recording' 16:09:24.979: [ffmpeg muxer: 'simple_file_output'] Output of file '/home/juan/Videos/OBS/2024-06-14_16-09-02.mkv' stopped 16:09:24.979: Output 'simple_file_output': stopping 16:09:24.979: Output 'simple_file_output': Total frames output: 529 16:09:24.979: Output 'simple_file_output': Total drawn frames: 389 (1311 attempted) 16:09:24.979: Output 'simple_file_output': Number of lagged frames due to rendering lag/stalls: 922 (70.3%) 16:09:24.979: Video stopped, number of skipped frames due to encoding lag: 12/539 (2.2%) 16:09:24.979: Recording Stop 16:09:25.084: libfdk_aac enco
[plasmashell] [Bug 487547] plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active.
https://bugs.kde.org/show_bug.cgi?id=487547 Juan changed: What|Removed |Added Alias||NVIDIA-Freezing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487547] plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active.
https://bugs.kde.org/show_bug.cgi?id=487547 --- Comment #4 from Juan --- Okay i just checked and the error is not reproducible on Intel Graphics, and it only happens on my PC (I used an HD 520 IGPU on my laptop and a GTX 1060 on my desktop), so if the devs want to reproduce the bug they will need to use NVIDIA Graphics with the Beta drivers 555 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487547] plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active.
https://bugs.kde.org/show_bug.cgi?id=487547 --- Comment #3 from Juan --- (In reply to Nate Graham from comment #2) > I can't reproduce this issue. Can you attach a screen recording that shows Unfortunately i can't use screen recorders on Wayland since there is a bug (i haven't reported it yet because i'm not sure where to report it. NVIDIA Forums might be the best bet since it's an NVIDIA specific problem, and it doesn't happen on Intel or AMD graphics, here's the picture of the error I've been getting https://imgur.com/a/VtYkgXM. > it happening? Thanks! I'll record using my phone instead if it's not an inconvenient for you... https://imgur.com/a/8FHGMsp I concluded that the bug happens when you open the "Status and notifications" tab repeatedly while a tool-tip is being shown, i'll check in a while if the same error happens on Intel Graphics, just to be 100% sure it's reproducible on anything other than just NVIDIA Graphics The bug happens randomly also, it happens each 2 minutes or 3 i reckon, so it's easily reproducible by normal use when switching between tabs or just being idle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487861] kwin crashed when opening a full-screen game unexpectedly, showing a black screen with the cursor visible
https://bugs.kde.org/show_bug.cgi?id=487861 --- Comment #2 from Juan --- (In reply to David Redondo from comment #1) > Were you recording your screen at that time? Otherwise maybe kwin did not > crash but plasmashell? According to the backtrace the crash happened in > screencasting code. Not at all, i was just opening Minecraft from the desktop in a normal Wayland session without OBS or any other program recording at the moment > Kwin logs from journalctl might also be useful Alright then, here's the output log of journalctl. I'll upload it to Google Drive. https://drive.google.com/file/d/1x5zcgqvNu2wMF-CtL24XBu4u8wO8Czuf/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)
https://bugs.kde.org/show_bug.cgi?id=488042 --- Comment #4 from Juan --- (In reply to Zamundaaa from comment #3) > (In reply to Juan from comment #2) > > Will this be fixed in the NVIDIA 560 driver > NVidia is aware of the problem, but we don't know how soon they'll have it > fixed. > > > or will this be fixed in the release of Plasma 6.1? > No, it's something that has to be fixed in the driver. Okay thanks, at least i know it's a common issue and it has been assessed. I also tried Mesa 24.1 on an Intel IGPU with Plasma 6.0.90 and it has Zero bugs, only sluggish performance but that's expected -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)
https://bugs.kde.org/show_bug.cgi?id=488042 --- Comment #2 from Juan --- (In reply to David Redondo from comment #1) > This is an issue of the nvidia driver with explicit sync. Thanks for the heads up. Will this be fixed in the NVIDIA 560 driver or will this be fixed in the release of Plasma 6.1? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)
https://bugs.kde.org/show_bug.cgi?id=488042 Juan changed: What|Removed |Added Keywords||reproducible, usability, ||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)
https://bugs.kde.org/show_bug.cgi?id=488042 Juan changed: What|Removed |Added Alias||Destkop-freezing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488042] Desktop freezes when bottom panel is hidden (Breeze theme)
https://bugs.kde.org/show_bug.cgi?id=488042 Juan changed: What|Removed |Added Summary|Desktop freezes and can't |Desktop freezes when bottom |click desktop icons or |panel is hidden (Breeze |arrange icons when panel is |theme) |not visible (dodge windows) | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488042] New: Desktop freezes and can't click desktop icons or arrange icons when panel is not visible (dodge windows)
https://bugs.kde.org/show_bug.cgi?id=488042 Bug ID: 488042 Summary: Desktop freezes and can't click desktop icons or arrange icons when panel is not visible (dodge windows) Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: juanrollgamer123456...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY Desktop freezes and can't click desktop icons or arrange icons when panel is not visible (dodge windows) STEPS TO REPRODUCE 1. Use default breeze bottom panel with "dodge windows" on 2. Go fullscreen in any app/game 3. Minimize app/game or switch to windowed mode 4: try to click in any icon on the desktop or re arrange it (for example, Firefox) while the panel is still hidden OBSERVED RESULT When the panel is hidden when coming from a fullscreen game, the desktop freezes and desktop shortcuts don't react at all at when clicking them with your mouse or even tool-tips don't work when hovering over them. All of this is fixed when the panel is shown when hovering over it with the mouse. I also noticed notifications and any panel widget don't work during this process. For example spotify doesn't play music during this freezing when it's minimized or minimized to tray. Or bluetooth doesn't connect to air buds during this freezing. Basically the desktop freezes generally, until the panel is visible again EXPECTED RESULT Desktop works even when the panel is not visible, or always show panel when there's no windows over it (That also might be a bug) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 6.9.2 KDE Plasma Version: Beta 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION If it's important at all, I'm using an NVIDIA GTX 1060 on Wayland with the beta driver 555 and explicit sync -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487861] New: kwin crashed when opening a full-screen game unexpectedly, showing a black screen with the cursor visible
https://bugs.kde.org/show_bug.cgi?id=487861 Bug ID: 487861 Summary: kwin crashed when opening a full-screen game unexpectedly, showing a black screen with the cursor visible Classification: Plasma Product: kwin Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: juanrollgamer123456...@gmail.com Target Milestone: --- SUMMARY kwin crashed when opening a full-screen game unexpectedly, showing a black screen with the cursor visible STEPS TO REPRODUCE 1. Open Minecraft (I suspect it happens with any full-screen OpenGL game but it has only happened to with Minecraft) from the desktop as a shortcut 2. Use Wayland with the 555 series NVIDIA drivers 3. Use beta version of KDE Plasma version 6.0.90 OBSERVED RESULT This error has only happened to me once but it's important that it's fixed when possible. kwin_wayland suddenly crashed when trying to open Minecraft (haven't tried with any other fullscreen game) when entering fullscreen, showing me a black screen without the possibility of doing anything besides opening the terminal with a key shortcut, only showing the cursor and the recent windows using alt-tab. After crashing, it only asked me for authentication to file the bug into a log file, here's the summary of the bug: PID: 822 (kwin_wayland) UID: 1000 (juan) GID: 1000 (juan) Signal: 11 (SEGV) Timestamp: Fri 2024-05-31 19:49:47 EDT (4min 27s ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_NKtJdv --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-kwin_wayland.service Slice: user-1000.slice Owner UID: 1000 (juan) Boot ID: 9918d87892b6498fb6f604ec782c5679 Machine ID: 5e0fa143c4a94f92ab57561fd4584ec1 Hostname: Asus Storage: /var/lib/systemd/coredump/core.kwin_wayland.1000.9918d87892b6498fb6f604ec782c5679.822.171719938700.zst (inaccessible) Message: Process 822 (kwin_wayland) of user 1000 dumped core. Stack trace of thread 822: #0 0x70351aaf63d8 n/a (libnvidia-eglcore.so.555.42.02 + 0xaf63d8) #1 0x70351aaf95fe n/a (libnvidia-eglcore.so.555.42.02 + 0xaf95fe) #2 0x70351aafad06 n/a (libnvidia-eglcore.so.555.42.02 + 0xafad06) #3 0x70351ab11fe1 n/a (libnvidia-eglcore.so.555.42.02 + 0xb11fe1) #4 0x70351a9e53a3 n/a (libnvidia-eglcore.so.555.42.02 + 0x9e53a3) #5 0x70351aadb4ee n/a (libnvidia-eglcore.so.555.42.02 + 0xadb4ee) #6 0x70351aa8e4c3 n/a (libnvidia-eglcore.so.555.42.02 + 0xa8e4c3) #7 0x70351a6c153a n/a (libnvidia-eglcore.so.555.42.02 + 0x6c153a) #8 0x70351a6c1dc2 n/a (libnvidia-eglcore.so.555.42.02 + 0x6c1dc2) #9 0x703528c6b58c n/a (screencast.so + 0xc58c) #10 0x703528c6f1ab n/a (screencast.so + 0x101ab) #11 0x703528c77244 n/a (screencast.so + 0x18244) #12 0x703528c7b649 _ZN4KWin16ScreenCastStream11recordFrameERK7QRegion6QFlagsINS0_7ContentEE (screencast.so + 0x1c649) #13 0x70352f5a17e7 n/a (libQt6Core.so.6 + 0x1a17e7) #14 0x703528c7707a n/a (screencast.so + 0x1807a) #15 0x70352f5a17e7 n/a (libQt6Core.so.6 + 0x1a17e7) #16 0x70352f5a9975 _ZN6QTimer10timerEventEP11QTimerEvent (libQt6Core.so.6 + 0x1a9975) #17 0x70352f58c0b9 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c0b9) #18 0x7035304fc55c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc55c) #19 0x70352f544e38 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x144e38) #20 0x70352f6c3c38 _ZN14QTimerInfoList14activateTimersEv (libQt6Core.so.6 + 0x2c3c38) #21 0x70352f6c6308 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2c6308) #22 0x70352fff95b3 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x5f95b3) #23 0x70352f54f10e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x14f10e) #24 0x70352f54945d _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x14945d) #25
[plasmashell] [Bug 487722] System tray settings popup showing behind panel settings dialog.
https://bugs.kde.org/show_bug.cgi?id=487722 Juan changed: What|Removed |Added Alias||widget-popup -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487722] New: System tray settings popup showing behind panel settings dialog.
https://bugs.kde.org/show_bug.cgi?id=487722 Bug ID: 487722 Summary: System tray settings popup showing behind panel settings dialog. Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: juanrollgamer123456...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY System tray settings popup showing behind panel settings dialog. STEPS TO REPRODUCE 1. Plasma beta 6.1 (6.0.90) 2. Using any hardware (tried both on my NVIDIA GPU PC and my Intel GPU Laptop as well, it still occurs) OBSERVED RESULT When glancing over the system tray with the cursor (or any widget behind the panel settings dialog) it hides behind the panel settings dialog making it impossible to manage the settings of the widget. Right clicking on the widget works as normal. EXPECTED RESULT Being able to click on the applet's popup to change it's settings on front of the panel settings dialog (if possible) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma 6.0.90 (using custom Kernel: Linux-tkg 6.9.2) (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487547] plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active.
https://bugs.kde.org/show_bug.cgi?id=487547 Juan changed: What|Removed |Added Keywords||reproducible, usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487547] plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active.
https://bugs.kde.org/show_bug.cgi?id=487547 Juan changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487547] New: plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active.
https://bugs.kde.org/show_bug.cgi?id=487547 Bug ID: 487547 Summary: plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active. Classification: Plasma Product: plasmashell Version: master Platform: Arch Linux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: juanrollgamer123456...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY plasmashell hangs/freezes when opening an app on the "icons-only task manager" or the system tray while a tool-tip or window preview is open/active. STEPS TO REPRODUCE 1. opening a tray icon while Firefox window preview is showing up 2. moving the cursor around the panel while a tool-tip is showing up and opening any other tray icon/app icon 3. glancing over app icons while a tray icon tool-tip is still showing up OBSERVED RESULT Any time a tool-tip or a window preview is active, the desktop freezes (Apps still function normally and alt-tabbing is still possible) while this happens, any time the cursor glances over the bottom panel or the desktop the cursor's icon never changes and i can't click on anything, neither desktop shortcuts, nor panel icons. Restarting the PC or killing plasmashell in the system monitor solves the problem. EXPECTED RESULT Normal functionality of the desktop without any kind of freezing. Even if the tool-tips/window previews are showing up. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, using linux-tkg custom kernel version 6.9.1-273 (available in About System) KDE Plasma Version: 6.0.90 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484204] Cierre repentino al guardar
https://bugs.kde.org/show_bug.cgi?id=484204 --- Comment #1 from Juan José --- Ya instale de nuevo la app en mi tablet y lo reinicie, pero me sigue surgiendo el fallo, llevo una semana con esto, ya he perdido algunos trabajos por esta situación y no puedo avanzar. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484204] New: Cierre repentino al guardar
https://bugs.kde.org/show_bug.cgi?id=484204 Bug ID: 484204 Summary: Cierre repentino al guardar Classification: Applications Product: krita Version: 5.1.5 Platform: Android OS: Android 13.x Status: REPORTED Severity: major Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: juanjose_16_n...@outlook.com Target Milestone: --- Created attachment 167585 --> https://bugs.kde.org/attachment.cgi?id=167585=edit Texto del registro de krita en los informes de fallo Cuando intento guardar mi trabajo, krita se cierra repentinamente y no guarda el archivo, vuelvo a entrar y me aparece que si quiero abrir el guardado automático del archivo, le doy clic y me deja entrar al proyecto, pero de nuevo al querer volver guardar se cierra de nuevo krita y no guarda mi proyecto, y así sucesivamente, al final lo intento varias veces pero es el mismo resultado. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484185] Crash when trying to Open files
https://bugs.kde.org/show_bug.cgi?id=484185 Juan changed: What|Removed |Added Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484185] Crash when trying to Open files
https://bugs.kde.org/show_bug.cgi?id=484185 --- Comment #2 from Juan --- (In reply to David REVOY from comment #1) > Hi, > Please write what Krita package you use. > If it is the community Flatpak, it is known to have issues, but it's not > maintained by the Krita team. > check: > - https://bugs.kde.org/show_bug.cgi?id=484124 > - https://bugs.kde.org/show_bug.cgi?id=484060 > > Workaround: use the appimage distributed by Krita developpers on krita.org And that worked, thank you! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 484185] New: Crash when trying to Open files
https://bugs.kde.org/show_bug.cgi?id=484185 Bug ID: 484185 Summary: Crash when trying to Open files Classification: Applications Product: krita Version: 5.2.2 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: ochoa.juancar...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Krita 2. Click on File Menu 3. Click on Open OBSERVED RESULT Krita closes without ever opening the file browser EXPECTED RESULT Window opens and I can browse for a file to open. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 Juan Méndez changed: What|Removed |Added Version|23.08.5 |24.02.0 Platform|Manjaro |unspecified --- Comment #15 from Juan Méndez --- Yeah, I can confirm this is a problem as of the latest Plasma (6.0.1). I don't think krfb was ever touched in the Qt migration, so I guess it's okay to assume krfb is still broken. On Plasma 6.x krfb even manages to crash the desktop bringing everything down (except for Qt apps) with it. --- krfb --version krfb 24.02.0 plasma-desktop 6.0.1-1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445987] Dolphin cannot create folders on an Nginx based WebDAV server.
https://bugs.kde.org/show_bug.cgi?id=445987 --- Comment #2 from juan --- Created attachment 165093 --> https://bugs.kde.org/attachment.cgi?id=165093=edit Dolphin error webdav -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445987] Dolphin cannot create folders on an Nginx based WebDAV server.
https://bugs.kde.org/show_bug.cgi?id=445987 juan changed: What|Removed |Added CC||juanrodena...@gmail.com --- Comment #1 from juan --- Over here, I also have the error that dolphin cannot create folders via webdav. STEPS TO REPRODUCE 1. Open an Nginx backed resource webdav(s)://... with Dolphin. 2. Try to create a folder there. webdav | 192.168.1.155 - juan [21/Jan/2024:09:15:06 +] "PROPFIND //Nueva%20carpeta HTTP/1.1" 404 153 "-" "Mozilla/5.0 (X11; Linux x86_64) KIO/5.113 dolphin/23.08.4" webdav | 2024/01/21 09:15:10 [error] 7#0: *4 MKCOL can create a collection only, client: ***, server: ***, request: "MKCOL /Prueba HTTP/1.1", host: "***" I check folder permissions, add 777 permissions and it still reproduces the error. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 479034] New: Online calendars appear unchecked and events don't show every now and then without any reason.
https://bugs.kde.org/show_bug.cgi?id=479034 Bug ID: 479034 Summary: Online calendars appear unchecked and events don't show every now and then without any reason. Classification: Applications Product: kontact Version: 5.240.40 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calendar Assignee: kdepim-b...@kde.org Reporter: juangg1...@gmail.com Target Milestone: --- SUMMARY *** My Google calendars are unchecked every few days. They appear checked and working properly but every now and then they are unchecked and I have to check them manually to see my events again. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Opensuse Tumbleweed (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 474304] New: Allow re-apply resolution
https://bugs.kde.org/show_bug.cgi?id=474304 Bug ID: 474304 Summary: Allow re-apply resolution Classification: Applications Product: systemsettings Version: 5.27.7 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: juancarlosp...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I am doing gamedev in Unreal Engine 5, sometimes it glitches the resolution or flicker/froze the second screen, re-applying the same resolution fixes the problems, but KDEs "Display Configuration" does not allow to change to the same resolution you are in, the "Apply" button is disabled, so I have to lower the resolution, and go back to the previous resolution. Scripts like randr allow to change to the same resolution. This sometimes happens with games and 3D software too. I think allowing to re-apply the same resolution you are using would be a nice QOL improvement. STEPS TO REPRODUCE 1. Open KDEs "Display Configuration". 2. Try to re-apply the same resolution. 3. You cant. OBSERVED RESULT You can not re-apply the same resolution. EXPECTED RESULT You can re-apply the same resolution. SOFTWARE/OS VERSIONS Windows: NO macOS: NO Linux/KDE Plasma: 5.27.7 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473515] New: Crash when activating Multibrush tool
https://bugs.kde.org/show_bug.cgi?id=473515 Bug ID: 473515 Summary: Crash when activating Multibrush tool Classification: Applications Product: krita Version: 5.2.0-beta2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: ochoa.juancar...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Select Multibrush tool 2. 3. OBSERVED RESULT Program crash without warning popups EXPECTED RESULT Proper Multibrush tool use. SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION Tried on a work in progress, on a smalller file and on a fresh file, with the same result Faulting application name: krita.exe, version: 5.2.0.51, time stamp: 0x64dca469 Faulting module name: libKF5ConfigCore.dll, version: 0.0.0.0, time stamp: 0x64da470b Exception code: 0xc005 Fault offset: 0x00011706 Faulting process id: 0xcac Faulting application start time: 0x01d9d218f83118a6 Faulting application path: C:\kritabeta\Krita (x64)\bin\krita.exe Faulting module path: C:\kritabeta\Krita (x64)\bin\libKF5ConfigCore.dll Report Id: 15881f09-b5af-4794-baf2-0afae94e4cf6 Faulting package full name: Faulting package-relative application ID: -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472764] PDF form dropdown doesn't show up
https://bugs.kde.org/show_bug.cgi?id=472764 --- Comment #3 from Juan Navarro --- (In reply to Albert Astals Cid from comment #2) > Git commit 532cb0cdcdd008fedb42f0a3ec690400b65820e1 by Albert Astals Cid. > Committed on 05/08/2023 at 20:20. > Pushed by aacid into branch 'master'. > > Initial implementation of app.popUpMenuEx > > It is defenitely not a full implementation but it's enough for the one > file we have that needs it for now > Thank you very much for your work! Okular now will be better PDF viewer than others even the pdf.js used in browsers, where the menu didn't show up either for me :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472764] New: PDF form dropdown doesn't show up
https://bugs.kde.org/show_bug.cgi?id=472764 Bug ID: 472764 Summary: PDF form dropdown doesn't show up Classification: Applications Product: okular Version: 23.04.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: oneorj...@gmail.com Target Milestone: --- Created attachment 160598 --> https://bugs.kde.org/attachment.cgi?id=160598=edit Video showing the expected behavior (using Acrobat Reader) SUMMARY A PDF form contains dropdowns with selectable choices. These don't show up in Okular. Using Okular v23.04.3, the latest version available in Flathub (https://flathub.org/apps/org.kde.okular) as of today. Underlying platform is Ubuntu 20.04. STEPS TO REPRODUCE 1. Open the PDF file that was attached to bug report #472756 (https://bugs.kde.org/show_bug.cgi?id=472756). I'm just linking to the other bug report in order to save on storage; if it's preferred that each report has its own attachments, please tell me and I will duplicate it here. 2. A header bar shows up in Okular, saying that "This document has forms. Click on the button to interact with them, or use View -> Show Forms." Click the "Show Forms" button. 3. On the left-half of the document, on the very first cell of the table (top-left) containing the text "Calle, plaza, avda., etc.", there is a dropdown. Pushing on its button does nothing. 4. On the right-half of the document, on the cell of the table containing the text "Nivel de estudios terminados", there is a dropdown. Pushing on its button does nothing. OBSERVED RESULT * Pushing on the dropdown of step 3 does nothing. The list of choices doesn't show up. * Pushing on the dropdown of step 4 does nothing. The list of choices doesn't show up. EXPECTED RESULT * Pushing on the dropdown of step 3 shows a list of strings. Selecting one, puts the text of that entry into the nearby text field. * Pushing on the dropdown of step 4 shows a list of numbered strings. Selecting one, puts the number of that entry into the nearby text field. SOFTWARE/OS VERSIONS As per Flatpak package indicated above: NameDescription Application ID Version Branch Remotes Okular Document Viewer org.kde.okular 23.04.3 stable flathub Running on an Ubuntu 20.04 system. ADDITIONAL INFORMATION The exact same issue can be seen in other programs tested: * Xreader v3.2.2 * Firefox v115 * Chromium v114 Given that it doesn't work elsewhere, I'm inclined to think that it might be a problem with the PDF file itself, and not a problem with Okular. Nevertheless, I'm reporting as maybe this opens up the chance to improve something in Okular. Attaching a screen capture video where the expected behavior is shown. This was captured using Acrobat Reader on Windows. Both dropdowns described at steps 3 and 4 show up and allow to select a single option. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472756] Infinite modal dialog in PDF form
https://bugs.kde.org/show_bug.cgi?id=472756 --- Comment #2 from Juan Navarro --- Created attachment 160597 --> https://bugs.kde.org/attachment.cgi?id=160597=edit Video showing the expected behavior (using Acrobat Reader) Attaching a screen capture video where the expected behavior is shown. This was captured using Acrobat Reader on Windows. The "DNI", "Pasaporte" and "NIE" boxes can be marked as selected right away. The "T", "P", and "C" boxes should show the modal dialog once, and afterwards they get marked as selected. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472756] Infinite modal dialog in PDF form
https://bugs.kde.org/show_bug.cgi?id=472756 --- Comment #1 from Juan Navarro --- Further info: This dialog doesn't show up at all in other PDF viewers I've tested: * Xreader v3.2.2 * Firefox v115 * Chromium v114 While these are indeed missing to show part of the PDF form to the user, the lucky consequence of that is that it becomes possible to actually fill the form successfully. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472756] New: Infinite modal dialog in PDF form
https://bugs.kde.org/show_bug.cgi?id=472756 Bug ID: 472756 Summary: Infinite modal dialog in PDF form Classification: Applications Product: okular Version: 23.04.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: oneorj...@gmail.com Target Milestone: --- Created attachment 160593 --> https://bugs.kde.org/attachment.cgi?id=160593=edit Sample PDF file SUMMARY A modal dialog is shown by the PDF form I'm trying to fill. It is just an informative dialog. The problem is that once closed, it shows up immediately again. This repeats indefinitely, which causes the form to be unfillable, and what's worse, Okular is captive in this dialog-loop, so it cannot be even closed by normal means. Using Okular v23.04.3, the latest version available in Flathub (https://flathub.org/apps/org.kde.okular) as of today. Underlying platform is Ubuntu 20.04. STEPS TO REPRODUCE 1. Open the PDF file that I'm attaching to this report. 2. A header bar shows up in Okular, saying that "This document has forms. Click on the button to interact with them, or use View -> Show Forms." Click the "Show Forms" button. 3. On the right-half of the document, on the first row that contains this text: (2) Tipo de documento de identidad DNI Pasaporte NIE T. Residencia Click on any of the checkboxes. For example, click on the checkbox under "DNI". 4. A dialog appears with this text: (1) En caso de Tarjeta de Residencia, indicar T (Temporal), P(Permanente), C(Comunitaria) And an OK button. OBSERVED RESULT Pressing the OK button closes the dialog, but it immediately appears again. The application is then permanently captured by this modal dialog, and neither of progressing with filling the form, or closing Okular, is possible. EXPECTED RESULT Pressing the OK button would close the dialog permanently. IF the reappearance of the dialog is caused by bad viewer logic of Okular: * Okular should be fixed to improve compatibility with documents like this one. IF the issue is caused by faulty logic of the document itself, and is not an issue in Okular itself, then: * Okular might try to be useful: detect the case and inform the user about it. * Okular ought to not allow a faulty document to make it into a dialog loop. For this, a reappearance limit would be a good idea, either as a fixed limit or as a UI checkbox in the dialog, giving the user the chance to silence future instances of that dialog. This is a pattern that I have seen successfully implemented in other software, such as web browsers. SOFTWARE/OS VERSIONS As per Flatpak package indicated above: NameDescription Application ID Version Branch Remotes Okular Document Viewer org.kde.okular 23.04.3 stable flathub -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 472201] New: arianna 1.1.0 does not start
https://bugs.kde.org/show_bug.cgi?id=472201 Bug ID: 472201 Summary: arianna 1.1.0 does not start Classification: Applications Product: Arianna Version: 1.0.1 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: c...@carlschwan.eu Reporter: th3pr0p...@gmail.com Target Milestone: --- SUMMARY The program does not start, when trying to run Arianna from the command line, it produces the following output: QQmlApplicationEngine failed to load component qrc:/content/ui/main.qml:272:20: Type TableOfContentDrawer unavailable qrc:/content/ui/TableOfContentDrawer.qml:9:1: module "org.kde.kirigamiaddons.treeview" is not installed STEPS TO REPRODUCE 1. Start Arianna 2. 3. OBSERVED RESULT Program does not start EXPECTED RESULT A user interface must be presented. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 --- Comment #2 from Juan Méndez --- Forgot to mention this is happening under KDE Wayland. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 470996] krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 --- Comment #1 from Juan Méndez --- gdb backtrace: kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1 [New Thread 0x7fff937fe6c0 (LWP 4568)] [New Thread 0x7fff92ffd6c0 (LWP 4569)] kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" Thread 1 "krfb-virtualmon" received signal SIGSEGV, Segmentation fault. __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:706 706 VMOVU %VMM(0), (%rdi) (gdb) backtrace #0 __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:706 #1 0x7fff7fea6255 in memcpy (__len=8294400, __src=, __dest=) at /usr/include/bits/string_fortified.h:29 #2 PWFrameBuffer::Private::handleFrame (frame=..., this=0x5583fde0) at /usr/src/debug/krfb/krfb-23.04.2/framebuffers/pipewire/pw_framebuffer.cpp:392 #3 operator() (frame=..., __closure=) at /usr/src/debug/krfb/krfb-23.04.2/framebuffers/pipewire/pw_framebuffer.cpp:156 #4 QtPrivate::FunctorCall, QtPrivate::List, void, PWFrameBuffer::Private::Private(PWFrameBuffer*):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #5 QtPrivate::Functor, 1>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #6 QtPrivate::QFunctorSlotObject, 1, QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #7 0x76be9fe7 in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #8 doActivate (sender=0x5597b4e0, signal_index=7, argv=0x7fffd760) at kernel/qobject.cpp:3923 #9 0x7fff7fa466aa in PipeWireSourceStream::frameReceived (this=this@entry=0x5597b4e0, _t1=...) at /usr/src/debug/kpipewire/build/src/KPipeWire_autogen/EWIEGA46WW/moc_pipewiresourcestream.cpp:219 #10 0x7fff7fa521fe in PipeWireSourceStream::handleFrame (this=this@entry=0x5597b4e0, buffer=buffer@entry=0x55c2f0a8) at /usr/src/debug/kpipewire/kpipewire-5.27.5/src/pipewiresourcestream.cpp:533 #11 0x7fff7fa52b4d in PipeWireSourceStream::process (this=0x5597b4e0) at /usr/src/debug/kpipewire/kpipewire-5.27.5/src/pipewiresourcestream.cpp:551 #12 0x7fff7f8a4108 in do_call_process (loop=, async=, seq=, data=, size=, user_data=0x55c2ec90) at ../pipewire/src/pipewire/stream.c:420 #13 0x7fff7f8148e1 in flush_items (impl=0x55c11138) at ../pipewire/spa/plugins/support/loop.c:171 #14 0x7fff7f813a09 in source_event_func (source=0x555b08e0) at ../pipewire/spa/plugins/support/loop.c:650 #15 0x7fff7f8155b6 in loop_iterate (object=0x55c11138, timeout=) at ../pipewire/spa/plugins/support/loop.c:483 #16 0x7fff7fa485d0 in operator() (__closure=) at /usr/src/debug/kpipewire/kpipewire-5.27.5/src/pipewirecore.cpp:78 #17 QtPrivate::FunctorCall, QtPrivate::List<>, void, PipeWireCore::init(int):: >::call (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146 #18 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256 #19 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=, ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443 #20 0x76be9fe7 in QtPrivate::QSlotObjectBase::call (a=, r=, this=, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x5558aba0, signal_index=3, argv=0x7fffde00) at kernel/qobject.cpp:3923 #22 0x76beb7e4 in QSocketNotifier::activated (this=this@entry=0x5558aba0, _t1=..., _t2=, _t3=...) at .moc/moc_qsocketnotifier.cpp:178 #23 0x76beb928 in QSocketNotifier::event (this=0x5558aba0, e=) at kernel/qsocketnotifier.cpp:302 #24 0x776ae93f in QApplicationPrivate::notify_helper (this=, receiver=0x5558aba0, e=0x7fffdf20) at kernel/qapplication.cpp:3640 #25 0x76bb4b18 in QCoreApplication::notifyInternal2
[krfb] [Bug 470996] New: krfb-virtualmonitor 23.x crashes
https://bugs.kde.org/show_bug.cgi?id=470996 Bug ID: 470996 Summary: krfb-virtualmonitor 23.x crashes Classification: Applications Product: krfb Version: 23.04.2 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: vps...@gmail.com Target Milestone: --- SUMMARY krfb-virtualmonitor simply crashes when trying to use it STEPS TO REPRODUCE 1. Try to use krfb-virtualmonitor 23.x OBSERVED RESULT krfb-virtualmonitor segfaults for no apparent reason EXPECTED RESULT - the program shouldn't segfault - downgrading to krfb-virtualmonitor 22.x solves the issue (specifically, this version works just fine: https://archive.archlinux.org/packages/k/krfb/krfb-22.12.3-1-x86_64.pkg.tar.zst) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.5-1 KDE Frameworks Version: 5.107.0-1 Qt Version: 5.15.9 (latest as of today) ADDITIONAL INFORMATION - CPU: 12th Gen Intel(R) Core(TM) i7-1280P (20) @ 4.7 GHz GPU: Intel Alder Lake-P Integrated Graphics Controller - krfb-virtualmonitor also crashes even after deleting the default config file in ~/.config - Some logs: QT_LOGGING_RULES="krfb.krfb=true" krfb-virtualmonitor --name test --resolution 2400x1080 --password test --port 5900 krfb.krfb: Loaded plugin with name "pw" krfb.krfb: Using FrameBuffer: "pw" krfb.krfb: Starting server. Listen port: 5900 Listen Address: "0.0.0.0" Password enabled: true 13/06/2023 04:55:26 PM Listening for VNC connections on TCP port 5900 13/06/2023 04:55:26 PM Listening for VNC connections on TCP6 port 5900 kpipewire_dmabuf_logging: eglChooseConfig returned this many configs: 1 kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" kpipewire_logging: invalid image "EGL_BAD_PARAMETER" kpipewire_dmabuf_logging: Failed to record frame: Error creating EGLImageKHR - "EGL_SUCCESS" Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 387366] Energy page: Energy consumption statistics not available
https://bugs.kde.org/show_bug.cgi?id=387366 Juan changed: What|Removed |Added CC||juanto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 421443] KOrganizer does not sync reliably with Zoho Calendars via CalDAV - pulls wrong remote CalDAV calendar URL
https://bugs.kde.org/show_bug.cgi?id=421443 Juan changed: What|Removed |Added Version|5.13.3 |5.22.3 CC||juan.brea...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 435232] KOrganizer automatically add slash (/) in the final of the URL and don't import correctly
https://bugs.kde.org/show_bug.cgi?id=435232 Juan changed: What|Removed |Added CC||juan.brea...@gmail.com --- Comment #12 from Juan --- Still active Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: SchenkerTechnologiesGmbH Product Name: XMG Mobile A507 VE System Version: Not Applicable -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover for disabled fwupd repo
https://bugs.kde.org/show_bug.cgi?id=462931 Juan Simón changed: What|Removed |Added Version|5.27.2 |5.27.5 Platform|Neon|Archlinux -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462931] "No metadata URIs for vendor directory" error seen in Discover for disabled fwupd repo
https://bugs.kde.org/show_bug.cgi?id=462931
Juan Simón changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED|REOPENED
CC||deced...@gmail.com
--- Comment #20 from Juan Simón ---
```
Operating System: CachyOS Linux
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.3.2-1-cachyos-lto (64-bit)
```
$ plasma-discover-update
org.kde.plasma.libdiscover: error loading "flatpak-backend" "Cannot load
library /usr/lib/qt/plugins/discover/flatpak-backend.so: (libflatpak.so.0:
cannot open shared object file: No such file or directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","archreq":2,"className":"FlatpakBackendFactory","debug":false,"version":331520})
org.kde.plasma.libdiscover: error loading "packagekit-backend" "Cannot load
library /usr/lib/qt/plugins/discover/packagekit-backend.so:
(libpackagekitqt5.so.1: cannot open shared object file: No such file or
directory)"
QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","archreq":2,"className":"PackageKitBackendFactory","debug":false,"version":331520})
QCommandLineParser: option not defined: "feedback"
Fwupd Error 10 no metadata URIs for vendor-directory
kf.newstuff.core: Could not find category "Calligra Flow Stencil"
KNS error in "Calligra_stencils" : KNSCore::ConfigFileError "All categories are
missing" QVariant(Invalid)
invalid kns backend! "/etc/xdg/calligra_stencils.knsrc" because: "Invalid
Calligra_stencils backend, contact your distributor."
org.kde.plasma.libdiscover: Discarding invalid backend
"calligra_stencils.knsrc"
kns error "/etc/xdg/calligra_stencils.knsrc" "Invalid Calligra_stencils
backend, contact your distributor."
ready 0
steady 0
No updates available, exiting
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 --- Comment #5 from juan --- Is there any progress? What can I do? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468077] It's now harder to draw an unfilled circle/ellipse/square/rectangle
https://bugs.kde.org/show_bug.cgi?id=468077 Juan Simón changed: What|Removed |Added CC||deced...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 --- Comment #4 from juan --- It should not go to the case, I don't know why it goes to the case on my mips32 OS. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 --- Comment #2 from juan --- Created attachment 158474 --> https://bugs.kde.org/attachment.cgi?id=158474=edit with the "-v -v -d -d" options to run the valgrind -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 juan changed: What|Removed |Added CC||j...@nbjetron.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (dis
https://bugs.kde.org/show_bug.cgi?id=469031 --- Comment #1 from juan --- arch: mips32 sourceCode: http://sourceware.org/pub/valgrind/ version: 3.20.0.tar.bz2 sha256sum: 8536c031dbe078d342f121fa881a9ecd205cb5a78e639005ad570011bdb9f3c6 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469031] New: run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393
https://bugs.kde.org/show_bug.cgi?id=469031 Bug ID: 469031 Summary: run command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" to check memory leak failed: vex: priv/guest_mips_toIR.c:23393 (disInstr_MIPS_WRK_10): Assertion `mode64' failed. Classification: Developer tools Product: valgrind Version: 3.20.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: j...@nbjetron.com Target Milestone: --- SUMMARY *** RUN command "valgrind --leak-check=full --show-reachable=yes --trace-children=yes /usr/bin/nr_ping_monitor&" report error: admin@OpenWrt:/# valgrind --leak-check=full --show-reachable=yes --trace-childre n=yes /usr/bin/nr_ping_monitor& admin@OpenWrt:/# ==5820== Memcheck, a memory error detector ==5820== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==5820== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info ==5820== Command: /usr/bin/nr_ping_monitor ==5820== ==5820== Conditional jump or move depends on uninitialised value(s) ==5820==at 0x4074630: ??? (in /lib/libc.so) ==5820==by 0x4085A9C: ??? (in /lib/libc.so) ==5820== ==5820== Conditional jump or move depends on uninitialised value(s) ==5820==at 0x4073ABC: ??? (in /lib/libc.so) ==5820==by 0x4074088: ??? (in /lib/libc.so) ==5820== ==5820== Conditional jump or move depends on uninitialised value(s) ==5820==at 0x4074650: ??? (in /lib/libc.so) ==5820==by 0x4085A9C: ??? (in /lib/libc.so) ==5820== vex: priv/guest_mips_toIR.c:23393 (disInstr_MIPS_WRK_10): Assertion `mode64' failed. vex storage: T total 42549728 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==5820==at 0x5803F988: ??? (in /usr/lib/valgrind/memcheck-mips32-linux) ==5820==by 0x5803F974: ??? (in /usr/lib/valgrind/memcheck-mips32-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 5820) ==5820==at 0x48E3C79: ??? (in /lib/libuci.so) ==5820==by 0x48FDF00: ??? (in /usr/lib/libjet_nvram.so) client stack range: [0x7E84 0x7E841FFF] client SP: 0x7E840C60 valgrind stack range: [0x425C5000 0x426C4FFF] top usage: 5752 of 1048576 Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. *** STEPS TO REPRODUCE 1. run valgrind to check memory leak OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: admin@OpenWrt:/# cat /proc/version Linux version 4.14.195 (jli@ubuntu) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r11208-ce6496d796)) #0 SMP Sun Sep 6 16:19:39 2020 admin@OpenWrt:/# (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466454] Vulkan and OpenGL windows not being created properly with fraction scale factors
https://bugs.kde.org/show_bug.cgi?id=466454 Juan changed: What|Removed |Added CC||mauxili...@gmail.com --- Comment #5 from Juan --- Hi, I think I'm experiencing the same error. If I run a steam game on xwayland with proton, the game window doesn't appear (but I hear the background music) The game shows the window if my monitor has scale (tested from 100% to 160%): 110%, 120%, 125%, 130%, 160% Doesn't show on scale: 105%, 115%, 135%, 140%, 145%, 150%, 155% The resolution is: 2560x1440 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 467929] New: Cannot read long logs
https://bugs.kde.org/show_bug.cgi?id=467929 Bug ID: 467929 Summary: Cannot read long logs Classification: Applications Product: kasts Version: 23.01.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: b...@mogwai.be Reporter: j...@juancanham.com Target Milestone: --- Created attachment 157693 --> https://bugs.kde.org/attachment.cgi?id=157693=edit Screenshot demonstrating the problem SUMMARY When clicking on the log viewer if the error is long, it doesn't display the whole text even if there is space to view the log on the screen. It also doesn't link to the log so I can view it in some other mechanism STEPS TO REPRODUCE 1. Cause an error that logs a long error (such as failure to poll a long url) 2. Go to settings > error viewer OBSERVED RESULT You can't see the whole error EXPECTED RESULT You can either see the whole error or select the error or open the log in some other viewer SOFTWARE/OS VERSIONS Flatpak ID: org.kde.kasts Ref: app/org.kde.kasts/x86_64/stable Arch: x86_64 Branch: stable Version: 23.01 License: GPL-2.0-or-later Origin: flathub Collection: org.flathub.Stable Installation: user Installed: 17.2 MB Runtime: org.kde.Platform/x86_64/5.15-22.08 Sdk: org.kde.Sdk/x86_64/5.15-22.08 Commit: f6580b9eaf2d617d8f80851ee159ce07c951d6bbea3c071ceb033905b5c1a7ea Parent: 7e407f28d260fba78cd879b0ef30e809adc7a0ad24b3ffdb4ea63d24b0fb0ff8 Subject: Update kirigami-addons-0.7.1.tar.xz to 0.7.2 (e19880f9) Date: 2023-03-08 13:44:26 + Operating System: Kubuntu 22.04 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-76060200-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465543] It crashes when I try to access some options.
https://bugs.kde.org/show_bug.cgi?id=465543 Juan Simón changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED --- Comment #2 from Juan Simón --- It's a Kvantum problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465543] It crashes when I try to access some options.
https://bugs.kde.org/show_bug.cgi?id=465543 --- Comment #1 from Juan Simón --- I don't know if it has to do with it but drkonqi also fails. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 465543] New: It crashes when I try to access some options.
https://bugs.kde.org/show_bug.cgi?id=465543
Bug ID: 465543
Summary: It crashes when I try to access some options.
Classification: Applications
Product: systemsettings
Version: 5.26.5
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: deced...@gmail.com
Target Milestone: ---
Created attachment 156127
--> https://bugs.kde.org/attachment.cgi?id=156127=edit
Output of gdb
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.1.11-xanmod1-1 (64-bit)
Graphics Platform: Wayland
Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series
systemsettings 5.26.5-1
systemsettings crashes when I try to access some options.
When I try to enter in "Users":
❯ systemsettings
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML
MouseArea: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML
MouseArea: Binding loop detected for property "width"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
"The name net.reactivated.Fprint was not provided by any .service files"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/share/kpackage/kcms/kcm_users/contents/ui/main.qml:50:5: QML
Connections: Implicitly defined onFoo properties in Connections are deprecated.
Use this syntax instead: function onFoo() { ... }
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:246:38:
QML FocusScope: Binding loop detected for property "contentItemMaximumWidth"
Both point size and pixel size set. Using pixel size.
file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/InlineMessage.qml:257:13:
QML SelectableLabel: Binding loop detected for property "implicitWidth"
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
file:///usr/share/kpackage/kcms/kcm_users/contents/ui/UserDetailsPage.qml:257:9:
QML SwipeView: Binding loop detected for property "implicitWidth"
file:///usr/share/kpackage/kcms/kcm_users/contents/ui/UserDetailsPage.qml:345:
ReferenceError: modelData is not defined
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML
MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML
MouseArea: Binding loop detected for property "implicitHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/OverlaySheet.qml:601:17:
QML ColumnLayout: Binding loop detected for property "width"
[kasts] [Bug 459983] No way to search inside a podcast for a specific word
https://bugs.kde.org/show_bug.cgi?id=459983 Juan Canham changed: What|Removed |Added CC||j...@juancanham.com --- Comment #1 from Juan Canham --- Ideally this could work in the episodes & queue views too. I can't be the only person who sometimes forgets what podcast I'm looking for. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 --- Comment #56 from Juan Simón --- It still fails. In my case with Telegram Desktop app. Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-native_amd-xanmod1-1 (64-bit) Graphics Platform: Wayland Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 Juan Simón changed: What|Removed |Added CC||deced...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 459446] Manual location but still "Host location.services.mozilla.com not found" error
https://bugs.kde.org/show_bug.cgi?id=459446 Juan Simón changed: What|Removed |Added Resolution|FIXED |--- CC||deced...@gmail.com Status|RESOLVED|REOPENED --- Comment #5 from Juan Simón --- Operating System: Arch Linux KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.6-zen1-2-zen (64-bit) Graphics Platform: Wayland Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor Memory: 62.6 GiB of RAM It still fails. Output of journcalctl: ene 19 08:59:38 kded5[2180]: org.kde.plasma.dataengine.geolocation: error: "Equipo location.services.mozilla.com no encontrado" -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 462565] New: fallo al iniciar el servicio de KDEconnect
https://bugs.kde.org/show_bug.cgi?id=462565 Bug ID: 462565 Summary: fallo al iniciar el servicio de KDEconnect Classification: Applications Product: kdeconnect Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: mxmo...@gmail.com Target Milestone: --- Application: kdeconnectd (21.12.3) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-56-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Este fallo se presenta cuando se inicia el sistema. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Demonio de KDE Connect (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f2ba3582d44 in QVariant::toMap() const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2b9676a7a8 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_connectivity_report.so #6 0x7f2ba4ad4101 in Device::privateReceivedPacket(NetworkPacket const&) () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.21 #7 0x7f2ba356b793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f2ba4ac4ca1 in LanDeviceLink::dataReceived() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.21 #9 0x7f2ba356b793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2ba4abd044 in SocketLineReader::dataReceived() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.21 #11 0x7f2ba356b793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2ba2cae4c5 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #13 0x7f2ba356b7c8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2ba2c5d45f in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #15 0x7f2ba2c70589 in ?? () from /lib/x86_64-linux-gnu/libQt5Network.so.5 #16 0x7f2ba40b7713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f2ba3533e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f2ba358dcc5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f2ba1a88d1b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f2ba1add6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f2ba1a863c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f2ba358d0b8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f2ba353275b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f2ba353acf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x55ab75341f9e in ?? () #26 0x7f2ba2e4fd90 in __libc_start_call_main (main=main@entry=0x55ab75341b70, argc=argc@entry=1, argv=argv@entry=0x7ffc8419e938) at ../sysdeps/nptl/libc_start_call_main.h:58 #27 0x7f2ba2e4fe40 in __libc_start_main_impl (main=0x55ab75341b70, argc=1, argv=0x7ffc8419e938, init=, fini=, rtld_fini=, stack_end=0x7ffc8419e928) at ../csu/libc-start.c:392 #28 0x55ab75342225 in _start () [Inferior 1 (process 1822) detached] The reporter indicates this bug may be a duplicate of or related to bug 451937, bug 452537, bug 459014. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 448248] Cannot change Qbittorrent Tray icon anymore
https://bugs.kde.org/show_bug.cgi?id=448248 Juan Simón changed: What|Removed |Added CC||deced...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwayland-integration] [Bug 461910] New: Implement minimize to tray
https://bugs.kde.org/show_bug.cgi?id=461910 Bug ID: 461910 Summary: Implement minimize to tray Classification: Plasma Product: kwayland-integration Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: deced...@gmail.com Target Milestone: --- ``` Operating System: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.8-native_amd-xanmod1-1 (64-bit) Graphics Platform: X11 Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: ASUS ``` I can't use Wayland because it doesn't have the option to minimize to the tray bar. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 460235] New: Crash on working
https://bugs.kde.org/show_bug.cgi?id=460235 Bug ID: 460235 Summary: Crash on working Classification: Applications Product: konsole Version: 22.08.1 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: juanfiguer...@outlook.com Target Milestone: --- Application: konsole (22.08.1) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-48-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: Crash while i was editing an script file, nothing special was happening The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Aborted [New LWP 8520] [New LWP 8522] [New LWP 108334] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f029fc5099f in __GI___poll (fds=0x7ffc0b4011b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f029a6629c0 (LWP 8518))] Thread 4 (Thread 0x7f026ac9b700 (LWP 108334)): #0 __GI___libc_read (nbytes=10, buf=0x7f026ac9aa1e, fd=87) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=87, buf=0x7f026ac9aa1e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f029ac14975 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f029b9bf416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f029b9bfeb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f029b9bff70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f029b9ce11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f029ac4372c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f029eb2c609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f029fc5d133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0291721700 (LWP 8522)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ab0a452968) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ab0a452918, cond=0x55ab0a452940) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ab0a452940, mutex=0x55ab0a452918) at pthread_cond_wait.c:647 #3 0x7f0291a285eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f0291a281eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f029eb2c609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f029fc5d133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0299875700 (LWP 8520)): #0 0x7f029fc5099f in __GI___poll (fds=0x7f02940053c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f029e16f36e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f029e16f4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f02a0223b9b in QEventDispatcherGlib::processEvents (this=0x7f0294000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f02a01c7b3b in QEventLoop::exec (this=this@entry=0x7f0299874bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f029ffe1342 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f029f018f4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f029ffe2543 in QThreadPrivate::start (arg=0x7f029f09cd80) at thread/qthread_unix.cpp:330 #8 0x7f029eb2c609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f029fc5d133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f029a6629c0 (LWP 8518)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f029fb60859 in __GI_abort () at abort.c:79 #6 0x7f029fdd0911 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f029fddc38c in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7f029fddc3f7 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f029fddc6a9 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f029fdd33ab in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f02a155a9e9 in Konsole::Screen::setSelectionEnd(int, int, bool) () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #12 0x7f02a15604b2 in ?? () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.1 #13 0x7f02a15c2117 in Konsole::TerminalDisplay::extendSelection(QPoint const&) () from
[Akonadi] [Bug 341067] Events from caldav resource do not appear in Korganizer
https://bugs.kde.org/show_bug.cgi?id=341067 Juan changed: What|Removed |Added CC||juan.brea...@gmail.com --- Comment #13 from Juan --- Same problem here, I see my Zoho Caldav calendars in the treeview but the events didn't appear. KOrganizer Versión 5.19.3 (21.12.3) Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 318819] [FeatureRequest] Panorama and spherical viewer for gwenview
https://bugs.kde.org/show_bug.cgi?id=318819 Juan J. Baca changed: What|Removed |Added Summary|Panorama and globe mode for |[FeatureRequest] Panorama |gwenview|and spherical viewer for ||gwenview -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 318819] Panorama and globe mode for gwenview
https://bugs.kde.org/show_bug.cgi?id=318819 Juan J. Baca changed: What|Removed |Added OS|Linux |All Platform|Ubuntu |unspecified Version|4.11.0 pre |unspecified CC||j...@bacamt.com --- Comment #4 from Juan J. Baca --- Panoramas (aka sphere, globe or 360 images, as you would like to call them) are getting more and more popular since 360 cameras got cheaper and smarter, among you can take it with your cellphone since years ago (since Android 4.2 camera). People are using them in sports, nature, events, etc... In the end, all of them are panoramas from a few degrees (partial panorama) to 360x180 degrees know as complete panorama. Nowadays there lot of open source implementations to take them as reference. As far as I now there are a few projection types but the more common is equirectangular. Metadata about panoramas are stored inside jpeg headers as an open standard (ISO 16684-1) aka Adobe XMP. Reference can be readed here: https://developers.google.com/streetview/spherical-metadata Some opensource projects are: - https://pchen66.github.io/Panolens/ | https://github.com/pchen66/panolens.js - https://photo-sphere-viewer.js.org/ | https://github.com/mistic100/Photo-Sphere-Viewer Hope this add some light and encourage someone to begin working to implement it in gwenview. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454931] [FeatureRequest] 360 image viewer
https://bugs.kde.org/show_bug.cgi?id=454931 Juan J. Baca changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from Juan J. Baca --- *** This bug has been marked as a duplicate of bug 318819 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 318819] Panorama and globe mode for gwenview
https://bugs.kde.org/show_bug.cgi?id=318819 Juan J. Baca changed: What|Removed |Added CC||saileshpoud...@gmail.com --- Comment #3 from Juan J. Baca --- *** Bug 454931 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 454931] [FeatureRequest] 360 image viewer
https://bugs.kde.org/show_bug.cgi?id=454931 Juan J. Baca changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||j...@bacamt.com --- Comment #1 from Juan J. Baca --- This issue duplicates Bug 318819. Currently the sphere view feature is not getting too much tracking. Therefore, merging all request in the same place may help to get developers interested on it. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Dead keys are not recognized [accute and grave accents (ú, ù), circumflex (û), diaeresis (ü)]
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added Version|22.04.1 |22.08.1 --- Comment #9 from juan --- An update on this bug. 1- I tried on both Debian Live XFCE and Debian Live KDE 11.4 in order to discard any configuration that could interfere with ktouch. The only thing I had to do after booting up is changing keyboard layout to Spanish (because standard US layout doesn't have any dead key to test). I've tried QWERTY and Dvorak layout and the bug is reproducible on the four scenarios I've described here. 2- I also tried on last flatpak version (Ktouch 22.08.1) and the bug is reproducible too. If anybody else could confirm and comment on this bug on recent versions of Ktouch, it could be useful I think. The issue turns Ktouch unusable for many languages. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458783] Negative rotation angle and wrong image
https://bugs.kde.org/show_bug.cgi?id=458783 --- Comment #2 from Juan Daniel Morcillo --- (In reply to Jasem Mutlaq from comment #1) > This should be fixed in KStars 3.6.1 Great! Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458783] New: Negative rotation angle and wrong image
https://bugs.kde.org/show_bug.cgi?id=458783 Bug ID: 458783 Summary: Negative rotation angle and wrong image Product: kstars Version: 3.5.9 Platform: unspecified OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: juandaniel.morci...@gmail.com Target Milestone: --- Created attachment 151864 --> https://bugs.kde.org/attachment.cgi?id=151864=edit Screenshot Hi, sometimes the manual rotator shows a negative angle, and the direction of the rotation that image shows is the opposite. For example, in this image I should rotate right -7º, it means rotate left 7º. I think it is a bit confusing, because another times it works fine and the number is positive with the correct image of the rotation. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 455800] Calendar Notification Sytem crashes when clicking "Dismiss"
https://bugs.kde.org/show_bug.cgi?id=455800 Juan Simón changed: What|Removed |Added Ever confirmed|0 |1 CC||deced...@gmail.com Status|RESOLVED|REOPENED Resolution|BACKTRACE |--- --- Comment #5 from Juan Simón --- Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.2-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor Memory: 62.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: ASUS Same problem. Every time I dismiss/close a reminder, it crashes. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457138] Issue with interface in Polar alignment
https://bugs.kde.org/show_bug.cgi?id=457138 --- Comment #2 from Juan Daniel Morcillo --- (In reply to Frank Stefani from comment #1) > Have you tried turning binning of for PA? Just to make sure this behavior > does not depend on binning ... Hi, I had the issue with binning 2 and binning 4. I can´t use binning 1 because I´m using a Raspberry 3 with 1GB of RAM. If I use binning 1, image is too heavy for my Raspberry and everithing crash. I want to buy a Raspberry 4, but there is not stock since a year ago... Anyway, it is strange because it doesn´t happend all the times. It looks like coordinates of image and mouse are not aligned. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 457138] New: Issue with interface in Polar alignment
https://bugs.kde.org/show_bug.cgi?id=457138 Bug ID: 457138 Summary: Issue with interface in Polar alignment Product: kstars Version: 3.5.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: juandaniel.morci...@gmail.com Target Milestone: --- Created attachment 150908 --> https://bugs.kde.org/attachment.cgi?id=150908=edit polar alignment Hi, A couple of times, when I tried to do a Polar alignment, I´m not able to position the triangle over the star that I want. When I click with the mouse in a point of the image, triangle moves to a different part of the picture. It is like coordinates of image doesn´t match with coordinates of my mouse. If I close KStars and I start the process from 0 it works fine, so it is something that doesn´t happend all the times. I´m using Ekos (version 1.9.5 of Indi) with Astroberry in a Raspberry PI 3, and I´m using VNC to handle Ekos. I don´t have any other problem with the mouse, it only happends with the alignment picture. I´m using a ASI294 MM camera, in binning 4 mode for Polar alignment. I don´t know if it could be related with binning, because it changes the size of the image and could affect to coordinates. I also tried with binning 2 and the same results. I don´t have logs, and I´m not sure this kind of issues appears in logs. I will try to collect it next time if the error appears again. For example, in the next picture I´m not able to see the entire triangle. If I click on the rigth bottom corner, triangle moves to position you see in the image. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #6 from Juan Méndez --- (In reply to Aleix Pol from comment #4) > Seems to be a bug in webrtc that recently , which is shared by both firefox > and chromium: https://webrtc-review.googlesource.com/c/src/+/265384 > > Can you test if you also have this problem with OBS? (In reply to Aleix Pol from comment #4) > Seems to be a bug in webrtc that recently , which is shared by both firefox > and chromium: https://webrtc-review.googlesource.com/c/src/+/265384 > > Can you test if you also have this problem with OBS? I just tested with OBS and everything works just fine (yay!). However, this bug is kinda weird because I was unable to replicate the same issue on GNOME (with all the latest updates as of yesterday). All these bug reports seem to indicate this issue only happens on KDE, though there's one comment about someone using NixOS + GNOME having the same issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #3 from Juan Méndez --- A couple of things worth noting: 1. None of what I mentioned above of below happens on Xorg (lol) 2. Firefox does seem to be broken as well, but not as badly as Chromium. This might deserve a bug report on its own, but here's a TL;DR of what happens when I try to test screen sharing using https://mozilla.github.io/webrtc-landing/gum_test.html : - The portal dialog shows up as usual asking me to pick a screen - I can see my screen in the miniature preview, but the preview remains frozen shortly after clicking the OK button in the portal dialog - Clicking the Pause/Play button will unfreeze the preview and things will work as expected - CPU usage goes br, with Firefox using about 60% of a CPU core and kwin_wayland using an entire CPU core. This doesn't happen with Chromium - My display's refresh rate drops to ~24 FPS with Firefox (it's a 75Hz display). I tried lowering the resolution but I still see a massive FPS drop on Wayland. This doesn't happen on Chromium, though - None of this happens on Xorg as well. CPU usage remains consistently low (no more than 20% core usage on both Chromium and FF), and no FPS drops either. 3. This also happens when using either DP or HDMI. Please let me know which logs you need, and/or the instructions to get you all the info needed to sort this out. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #2 from Juan Méndez --- Created attachment 150377 --> https://bugs.kde.org/attachment.cgi?id=150377=edit smaller resolution, everything works just fine -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 --- Comment #1 from Juan Méndez --- Created attachment 150376 --> https://bugs.kde.org/attachment.cgi?id=150376=edit native resolution, no VAAPI/hw accel hacks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456300] New: Screen sharing broken when using non-standard screen resolutions
https://bugs.kde.org/show_bug.cgi?id=456300 Bug ID: 456300 Summary: Screen sharing broken when using non-standard screen resolutions Product: kwin Version: 5.25.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: vps...@gmail.com Target Milestone: --- Created attachment 150375 --> https://bugs.kde.org/attachment.cgi?id=150375=edit native resolution SUMMARY When using a screen with an arguably _non-standard_ (or should I say _not-so-common_) resolution, screen sharing is pretty much broken on Chromium-based browsers. The "recording stream" looks glitchy and borked, for some reason. This didn't happen in Plasma 5.24.x, though. Please see pictures attached. Strangely enough, things work great on Firefox and OBS, but this wasn't broken in Plasma 5.24. Things also work if I scale back to a rather more common resolution, i.e. 2560x1080, 1920x1080, etc. In fact, I'm only able to reproduce the bug using my monitor's native resolution (3440x1440). STEPS TO REPRODUCE 1. Use any website that allows you to record your screen (zoom, jitsi, screenapp.io, etc). OBSERVED RESULT The captured stream looks glitchy, with lots of artifacts. Almost as if the computer were having GPU issues. EXPECTED RESULT No glitches or screen artifacts in the recorded stream. SOFTWARE/OS VERSIONS Linux Version: 5.15.2 Note: This doesn't seem to be a kernel issue, since I am able to reproduce the same behavior in kernel versions 5.15.x - 5.18.x. --- KDE Plasma Version: 5.25.2-1 --- KDE Frameworks Version: 5.95.0-2 --- Qt Version: 5.15.5+kde+r166-1 ADDITIONAL INFORMATION - I'm using my laptop's integrated graphics (Intel 8th gen U-series CPU). It has no issue driving the 2k screen - I'm pretty sure this is not a driver/mesa issue since I was unable to reproduce the same issue on GNOME 42 + same chromium release - I tried using older chromium releases (pre 103.x) to no avail - I did enable pipewire support in chrome://flags - I'm able to reproduce the same behavior using Flathub's Chromium, Brave, Arch's Chromium and ungoogled-chromium as well - I tried forcing Chromium's VAAPI support to see if it was a hardware-accel related issue, but that doesn't seem to be the case. - It looks like Chromium fails to call GetVSyncParametersIfAvailable() but ONLY when I use my display's native resolution. No such thing happens when I use smaller display resolutions. Maybe kwin is failing to provide some necessary info? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 456220] New: Windows doesn't unfold correctly
https://bugs.kde.org/show_bug.cgi?id=456220 Bug ID: 456220 Summary: Windows doesn't unfold correctly Product: kwin Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: juan.brea...@gmail.com Target Milestone: --- Created attachment 150329 --> https://bugs.kde.org/attachment.cgi?id=150329=edit Screen recording of the bug SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Assign double click in Title bar actions to fold and apply 2. Double click in the Title bar will fold correctly the window 3. Double click again in the Title bar. OBSERVED RESULT Double click in the Title bar will not unfold correctly the window EXPECTED RESULT Double click in the Title bar to unfold will restore the window to the previous size previous to fold, instead its needed to grab and pull down the window border to restore the size. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-40-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 455544] New: Unable to update themes. Error: "SETTINGS invalid number of concurrent streams"
https://bugs.kde.org/show_bug.cgi?id=455544 Bug ID: 455544 Summary: Unable to update themes. Error: "SETTINGS invalid number of concurrent streams" Product: Discover Version: 5.25.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Updates (interactive) Assignee: lei...@leinir.dk Reporter: deced...@gmail.com CC: aleix...@kde.org Target Milestone: --- Discover notifies me that there are several themes that can be updated but when I try it gives error. I have ran it in console and this is the output: $ plasma-discover-update adding empty sources model QStandardItemModel(0x555adbe8d4c0) Fwupd Error 10 no metadata URIs for vendor-directory no component found for "org.archlinux.arch" ready 4 steady 0 go! UpdateTransaction(0x7fb119dd6930) status! Transaction::CommittingStatus 4 qt.network.http2: connection error: SETTINGS invalid number of concurrent streams qt.network.http2: stream 7 finished with error: "SETTINGS invalid number of concurrent streams" qt.network.http2: stream 5 finished with error: "SETTINGS invalid number of concurrent streams" qt.network.http2: stream 3 finished with error: "SETTINGS invalid number of concurrent streams" qt.network.http2: stream 1 finished with error: "SETTINGS invalid number of concurrent streams" kf.newstuff.core: "SETTINGS invalid number of concurrent streams" kf.newstuff.core: "Download of \"Candy icons\" failed, error: SETTINGS invalid number of concurrent streams" KNS error in "Icons" : KNSCore::InstallationError "Download of \"Candy icons\" failed, error: SETTINGS invalid number of concurrent streams" QVariant(Invalid) kns error "/usr/share/knsrcfiles/icons.knsrc" "Download of \"Candy icons\" failed, error: SETTINGS invalid number of concurrent streams" kf.newstuff.core: "SETTINGS invalid number of concurrent streams" kf.newstuff.core: "Download of \"Nordic darker KDE\" failed, error: SETTINGS invalid number of concurrent streams" KNS error in "Global Themes" : KNSCore::InstallationError "Download of \"Nordic darker KDE\" failed, error: SETTINGS invalid number of concurrent streams" QVariant(Invalid) kns error "/usr/share/knsrcfiles/lookandfeel.knsrc" "Download of \"Nordic darker KDE\" failed, error: SETTINGS invalid number of concurrent streams" kf.newstuff.core: "SETTINGS invalid number of concurrent streams" kf.newstuff.core: "Download of \"Nordic KDE\" failed, error: SETTINGS invalid number of concurrent streams" KNS error in "Global Themes" : KNSCore::InstallationError "Download of \"Nordic KDE\" failed, error: SETTINGS invalid number of concurrent streams" QVariant(Invalid) kns error "/usr/share/knsrcfiles/lookandfeel.knsrc" "Download of \"Nordic KDE\" failed, error: SETTINGS invalid number of concurrent streams" kf.newstuff.core: "SETTINGS invalid number of concurrent streams" kf.newstuff.core: "Download of \"Nordzy-icon\" failed, error: SETTINGS invalid number of concurrent streams" KNS error in "Icons" : KNSCore::InstallationError "Download of \"Nordzy-icon\" failed, error: SETTINGS invalid number of concurrent streams" QVariant(Invalid) kns error "/usr/share/knsrcfiles/icons.knsrc" "Download of \"Nordzy-icon\" failed, error: SETTINGS invalid number of concurrent streams" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.5-arch1-1 (64-bit) Graphics Platform: X11 Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor Memory: 62.6 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 421794] dvorak-bépo dead keys (for î, û, â, ô, ï, ä, ë…) not recognised
https://bugs.kde.org/show_bug.cgi?id=421794 juan changed: What|Removed |Added CC||jumase+fo...@disroot.org --- Comment #1 from juan --- Hi, I was wondering if «It seems also that Ktouch doesn't support […] other characters such as "…" or non no-break space» may be because those characters are missing in the original text from the exercise. You can check it out by clicking on the second option in the configuration wheel/menu on the upper right corner of the screen. It says something like «Course and keyboard layout editor...» There you'll be able to find your course and exercise. Then you tan copy the text and check it in a text editor. Or you may be referring to those keys not being able to get inserted in ktouch. If that is the case, then we have another problem, possibly not completely related to dead keys. As far as I can tell (I've never written with BÉPO) you insert those characters by pressing Shift and/or AltGr + some specific key, don't you? I tested it on ktouch and I can insert these kind of characters (i.e. @, æ, Æ, «, », €, µ, etc.), I mean the issue I experience is only related to dead keys. Please check also bug https://bugs.kde.org/show_bug.cgi?id=410876 where the dead keys issue is being discussed. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Dead keys are not recognized [accute and grave accents (ú, ù), circumflex (û), diaeresis (ü)]
https://bugs.kde.org/show_bug.cgi?id=410876 --- Comment #8 from juan --- Created attachment 149088 --> https://bugs.kde.org/attachment.cgi?id=149088=edit Terminal log -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Dead keys are not recognized [accute and grave accents (ú, ù), circumflex (û), diaeresis (ü)]
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Summary|Couldn't write accent mark |Dead keys are not ||recognized [accute and ||grave accents (ú, ù), ||circumflex (û), diaeresis ||(ü)] Version|19.04.3 |22.04.1 --- Comment #7 from juan --- Hi, I've just tried version 22.04.1 from flatpak, but the issue is still there: no dead key works. I'll leave an attachment containing the terminal output as it may be useful. It's obtained from launching the software, loading an activity, trying to insert some dead key letters (á, à, ä, etc.), closing the exercise and finally exiting from the app. By the way, when failing to recognize dead keys, it won't display any particular message on terminal. I've also found another bug report that seem to be a duplicate of this one (https://bugs.kde.org/show_bug.cgi?id=423822). Let me know if I should leave "marking as duplicate" to somebody else. I do so in the hope that we could better deal with this issue. I will mark it as confirmed as well, and update version number and title to better represent the issue. Again, if that's not good practice, just let me know. Please let me know if any other information may be useful. Regards -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||bruno01da...@gmail.com --- Comment #6 from juan --- *** Bug 423822 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 423822] No support for Portuguese accents on keyboard
https://bugs.kde.org/show_bug.cgi?id=423822 juan changed: What|Removed |Added CC||jumase+fo...@disroot.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from juan --- This seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=410876 *** This bug has been marked as a duplicate of bug 410876 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453870] New: Download/Install new service menu fails
https://bugs.kde.org/show_bug.cgi?id=453870 Bug ID: 453870 Summary: Download/Install new service menu fails Product: dolphin Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: deced...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- ``` Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.6-zen1-1-zen (64-bit) Graphics Platform: X11 ``` I have tried to add several services from the Dolphin option: `Configure` > `Configure Dolphin` > `Context menu` > `Download new services` but it fails: ``` An error occurred during the installation process: Installation failed with code 1 when trying to execute the command: servicemenuinstaller install /home/juan/.local/share/servicemenu-download/comic-book-kservicemenu_1.3.3.tar.gz The returned output was: "An install script could not be found in /home/juan/.local/share/servicemenu-download/comic-book-kservicemenu_1.3.3.tar.gz-dir." ``` I have tried to install this one: https://store.kde.org/p/1235423 and this one: https://store.kde.org/p/1754455, but both fail with the same error. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||oscar.fernandez.pujol@gmail ||.com --- Comment #5 from juan --- *** Bug 436830 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 436830] In Catalan language can't insert some characters
https://bugs.kde.org/show_bug.cgi?id=436830 juan changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jumase+fo...@disroot.org Status|REPORTED|RESOLVED --- Comment #1 from juan --- This seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=410876 *** This bug has been marked as a duplicate of bug 410876 *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||fcojpe...@gmail.com --- Comment #4 from juan --- *** Bug 439933 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 439933] I cannot type words with a Spanish accent like á
https://bugs.kde.org/show_bug.cgi?id=439933 juan changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||jumase+fo...@disroot.org --- Comment #1 from juan --- This seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=410876 *** This bug has been marked as a duplicate of bug 410876 *** -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 410876] Couldn't write accent mark
https://bugs.kde.org/show_bug.cgi?id=410876 juan changed: What|Removed |Added CC||jumase+fo...@disroot.org --- Comment #3 from juan --- I confirm this behaviour on version 20.12.0 from Debian stable repositories. In the hope that this could be solved in latest version (22.04.0), I tried the flatpak one; unfortunately it still happens on that version. As mentioned on bugreport https://bugs.kde.org/show_bug.cgi?id=419137 , all dead keys don't work —accute and grave accents (ú, ù), circumflex (û), diaeresis (ü). I mean this doesn't seem to be related to a specific keyboard layout, not even to an specific language. I've tried with spanish dvorak and qwerty, but none of them worked as expected. There are also reports with Catalan (https://bugs.kde.org/show_bug.cgi?id=436830) and French (https://bugs.kde.org/show_bug.cgi?id=419137) layouts that suggest this is about dead keys in general. I've read about something related to QT libraries but I don't know how to test that, and also the reference (https://bugs.kde.org/show_bug.cgi?id=118862) is quite old. I'm usin XFCE, I don't know if that has anything to do. However, I use kmail, appimage of kdenlive, akgregator, and all of them recognize dead keys properly. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 452546] New: Plasma Settings Crash
https://bugs.kde.org/show_bug.cgi?id=452546 Bug ID: 452546 Summary: Plasma Settings Crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jpley...@gmail.com Target Milestone: --- Application: plasma-settings (22.02) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.17.1-arch1-1 x86_64 Windowing System: X11 Distribution: Linux DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I just oppened de plasma settings app after a fresh install of all Plasma environment. OS: Arcolinix WM: qtile The crash can be reproduced every time. -- Backtrace: Application: Settings (plasma-settings), signal: Segmentation fault [KCrash Handler] #4 0x7fa61ea6c520 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #5 0x7fa6040de579 in Kvantum::Animation::updateTarget() () from /usr/lib/qt/plugins/styles/libkvantum.so #6 0x7fa61e8b0923 in QAbstractAnimation::setCurrentTime(int) () from /usr/lib/libQt5Core.so.5 #7 0x7fa61e8b0a6e in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7fa61e8abd83 in QUnifiedTimer::updateAnimationTimers(long long) () from /usr/lib/libQt5Core.so.5 #9 0x7fa61e8af263 in QAnimationDriver::advanceAnimation(long long) () from /usr/lib/libQt5Core.so.5 #10 0x7fa61e068c6a in ?? () from /usr/lib/libQt5Quick.so.5 #11 0x7fa61e06d840 in ?? () from /usr/lib/libQt5Quick.so.5 #12 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #13 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #14 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7fa613fff640 (LWP 28541) "QQmlThread"): #1 0x7fa61cf186c5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #2 0x7fa61eab85f7 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #3 0x7fa61ea6488b in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7fa61e8c7a56 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #5 0x7fa61fdfed00 in ?? () from /usr/lib/libQt5Qml.so.5 #6 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #7 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #8 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7fa618923640 (LWP 28540) "QDBusConnection"): #1 0x7ffeb7de49aa in clock_gettime () #2 0x7fa61e48892d in clock_gettime@GLIBC_2.2.5 () from /usr/lib/libc.so.6 #3 0x7fa61cf1ad15 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #4 0x7fa61cf717e6 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7fa61cf186c5 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #6 0x7fa61eab85f7 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7fa61ea6488b in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #8 0x7fa61e8c7a56 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #9 0x7fa61dc123a9 in ?? () from /usr/lib/libQt5DBus.so.5 #10 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #11 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #12 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7fa619146640 (LWP 28539) "QXcbEventQueue"): #1 0x7fa61a15263b in ?? () from /usr/lib/libxcb.so.1 #2 0x7fa61a15437b in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7fa619251b12 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7fa61e8c48cc in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7fa61e43d5c2 in start_thread () from /usr/lib/libc.so.6 #6 0x7fa61e4c2584 in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7fa61964fa80 (LWP 28537) "plasma-settings"): #1 0x7fa61e43c960 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libc.so.6 #2 0x7fa61e8cbcfc in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #3 0x7fa61e072607 in ?? () from /usr/lib/libQt5Quick.so.5 #4 0x7fa61e0c4784 in QQuickWindow::event(QEvent*) () from /usr/lib/libQt5Quick.so.5 #5 0x7fa61f5881c6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #6 0x7fa61ea6c5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #7 0x7fa61ee34609 in QPlatformWindow::windowEvent(QEvent*) () from /usr/lib/libQt5Gui.so.5 #8 0x7fa61f58c4fc in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #9 0x7fa61ea6c5aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #10 0x7fa61eab7dd5 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5 #11
[kate] [Bug 445898] Terminal panel opens vi when I try to open a new file on another directory
https://bugs.kde.org/show_bug.cgi?id=445898 --- Comment #3 from juan --- Here's a video of the behaviour observed, the steps are: 1. Open a file on kate and open the Terminal Panel 2. Open another file on another directory, the Terminal Panel instead of cd on the directory will open VI on a temp file. 3. If vi is removed from the system, everything works fine. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445898] Terminal panel opens vi when I try to open a new file on another directory
https://bugs.kde.org/show_bug.cgi?id=445898 --- Comment #2 from juan --- Created attachment 145898 --> https://bugs.kde.org/attachment.cgi?id=145898=edit Video of the behaviour observed -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446908] KDEConnect sees my Ubuntu laptop, connects, then disconnects within 1 minute
https://bugs.kde.org/show_bug.cgi?id=446908 Juan E. Jot changed: What|Removed |Added CC||pbdz8...@duck.com --- Comment #1 from Juan E. Jot --- >From what I can tell under the TestFlight app, the KDE Connect developers are aware, at least as of builds 0.2.0(2) and 0.2.0(5) of the iOS app, that LTS kernels (but not non-LTS kernels such as those shipped with Ubuntu 20.10, 21.04 & 21.10) disconnect intermittently from the iOS app. I myself had been running GSConnect (a Gnome build of KDEConnect) on Pop!_OS 21.10 (based on Ubuntu 21.10), as well as KDEConnect on Manjaro XFCE 21.2.1 without issue, and then tried KDEConnect on Linux Mint 20.3 (based on Ubuntu 20.04 LTS), finding the same issue as you did (more detail below*). I set up a KDE Connect account the same as you to report the bug, then read the 0.2.0(2 and 5) release notes, only to find it known to the KDE developers. Good job being on it as to current limitations, folks! But let me add my voice to yours, michael.hubbard999, just to ask KDE developers whether there is progress being made or a timeline, for update to this behavior. I imagine that with 22.04 LTS coming up in April (for mainline Ubuntu, not for derivatives like Pop!_OS and Linux Mint right off the bat), that fixing it for the 22.04 LTS kernel is the goalpost. But I would love to hear of testing a solution for 20.04 LTS or failing that, a good backport of a solution for 22.04 LTS. That way, we'll be able to use KDEConnect on 20.04 LTS & its derivatives (such as my Linux Mint 20.3 installation) before they eventually update the kernel base. This is an individual hope partially due to other (graphical; see below) limitations^ of my aged system. === * Essentially as release notes have described, on my Linux Mint 20.3 (with kernel 5.4.x) partition, KDEConnect cannot successfully initiate connection. KDE Connect 0.2.0(5) on iOS *can* initiate it to Linux Mint, but Linux Mint announces a disconnection randomly within a few seconds, and KDE Connect on iOS never moves Linux Mint from the blue list of Discovered Devices to a green hue of connection (likewise, never having connected, it never shows up as a red Remembered Device). This is true with the firewall on or off, with ports 1714:1764 allowed or not, UDP or TCP. Neither any applets nor gnome-shell-extension-gsconnect help this behavior, as they are all about GUI rather than connection behaviors. Again, expected behavior for KDEConnect iOS 0.2.0(5) is fulfilled in connection with GSConnect on Pop!_OS 21.10 (with kernels 5.11.x, 5.13.x and 5.15.x) and with KDEConnect on Manjaro XFCE (with kernels 5.13.x and 5.15.x; *not tested* with Manjaro's latest 5.10.x LTS kernel!) on other partitions on the same machine. In a kudos to System76 &/or possibly Canonical if not Linus himself, this not only works as expected on x86_64, but also on arm64 on a Raspberry Pi 4 running Pop!_OS 21.10 (with kernel 5.13.x, so far)! Lastly, I lack any Android hardware with which to test against that mobile version of KDE Connect. ^ (Basically, I'm afraid I'll lose the full support Linux Mint offers--and uncommon present-day recommendation they make!--for the nvidia-340 driver my ancient laptop needs for any worthwhile performance at all, even in web browsers, these days. This is software completely unrelated to KDEConnect in my one-off use case, but I simply include it to show my motivation for this hope. To digress further if you're interested, I address this graphical issue on Ubuntu kernels higher than 5.4.x by using kelebek333's nvidia-legacy PPA on launchpad; hopefully support for that software extends to whatever kernel 22.04 LTS ends up using!) -- You are receiving this mail because: You are watching all bug changes.
