[ark] [Bug 474593] Previewing a file in Ark always tries to open with KDE Connect
https://bugs.kde.org/show_bug.cgi?id=474593 --- Comment #1 from omano --- This should be fixed, it is a general issue from KDE Connect I have the issue in Dolphin, and other applications. https://bugs.kde.org/show_bug.cgi?id=472697 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 474593] New: Previewing a file in Ark always tries to open with KDE Connect
https://bugs.kde.org/show_bug.cgi?id=474593 Bug ID: 474593 Summary: Previewing a file in Ark always tries to open with KDE Connect Classification: Applications Product: ark Version: 23.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: om...@redorchestra2.fr CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- Created attachment 161658 --> https://bugs.kde.org/attachment.cgi?id=161658=edit KDE Connect opening when previewing a file SUMMARY *** Every time I try to preview a file in Ark, it tries to open it with KDE Connect on connected device, even if no device connected, even when the file type is known and already associated with another program (plain text files, shell script, whatever the file type is, or if I manually force again the file association) *** STEPS TO REPRODUCE 1. Open an archive 2. Try to preview a file in Ark 3. See the KDE Connect URL handler opening asking you to open the file on associated device. OBSERVED RESULT Ark doesn't preview the file with the associated program, like Kate for a plain text file for example, it opens KDE Connect EXPECTED RESULT It previews the file either with a default proper preview program, most likely a text editor (as we generally don't try to preview a compiled binary) or with the associated program for that file type. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This behavior was not always like that. when I was previewing text file, PKGBUILD, shell script, it was opening in Kate, or some internal preview tool looking like Kate/Kwrite -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469103] Plasmashell leak memory after disabling second monitor from Nvidia Settings
https://bugs.kde.org/show_bug.cgi?id=469103 --- Comment #1 from omano --- Additional info (inxi -Fazy): ``` System: Kernel: 6.1.25-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64 root=UUID=6a81f472-9ea9-40f8-85f6-7925c4bbe742 ro quiet splash udev.log_priority=3 sysrq_always_enabled=1 amd_pstate=passive amd_pstate.shared_mem=1 mitigations=off nowatchdog delayacct Desktop: KDE Plasma v: 5.27.4 tk: Qt v: 5.15.9 wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux Machine: Type: Desktop System: Gigabyte product: B450M DS3H v: N/A serial: Mobo: Gigabyte model: B450M DS3H-CF serial: UEFI: American Megatrends LLC. v: F64a date: 02/09/2023 CPU: Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701030 Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 32 MiB desc: 2x16 MiB Speed (MHz): avg: 588 high: 909 min/max: 550/4426 boost: enabled scaling: driver: amd-pstate governor: schedutil cores: 1: 550 2: 550 3: 627 4: 550 5: 550 6: 550 7: 551 8: 550 9: 550 10: 909 11: 579 12: 550 bogomips: 86279 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Vulnerabilities: Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: retbleed status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 status: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers Type: spectre_v2 status: Vulnerable, IBPB: disabled, STIBP: disabled, PBRSB-eIBRS: Not affected Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: eVga.com. driver: nvidia v: 530.41.03 alternate: nouveau,nvidia_drm non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 07:00.0 chip-ID: 10de:1c03 class-ID: 0300 Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.1 compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1200 s-dpi: 93 s-size: 524x320mm (20.63x12.60") s-diag: 614mm (24.17") Monitor-1: DP-0 pos: primary res: 1920x1200 dpi: 94 size: 518x324mm (20.39x12.76") diag: 611mm (24.05") modes: N/A Monitor-2: HDMI-0 size-res: N/A modes: N/A API: OpenGL v: 4.6.0 NVIDIA 530.41.03 renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 direct-render: Yes Audio: Device-1: NVIDIA GP106 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 10de:10f1 class-ID: 0403 Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403 API: ALSA v: k6.1.25-1-MANJARO status: kernel-api with: aoss type: oss-emulator tools: alsamixer,amixer Server-1: JACK v: 1.9.22 status: off tools: N/A Server-2: PipeWire v: 0.3.70 status: off with: pipewire-media-session status: off tools: pw-cat,pw-cli Server-3: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: Drives: Local Storage: total: 2.03 TiB used: 1.05 TiB (51.6%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Crucial model: CT1000P1SSD8 size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: rev: P3CR020 temp: 46.9 C scheme: GPT ID-2: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD PLUS 480GB size: 447.14 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: rev: 00RL scheme: GPT ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD5001AALS-00E3A0 size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: N/A serial: rev: 1D05 scheme: MBR ID-4: /dev/sdc maj-min: 8:32 vendor: SanDisk model: SDSSDHP256G size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: rev: 6RL scheme: GPT Partition: ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%) used: 801.42 GiB (87.5%
[plasmashell] [Bug 469103] New: Plasmashell leak memory after disabling second monitor from Nvidia Settings
https://bugs.kde.org/show_bug.cgi?id=469103 Bug ID: 469103 Summary: Plasmashell leak memory after disabling second monitor from Nvidia Settings Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-performance Assignee: plasma-b...@kde.org Reporter: om...@redorchestra2.fr Target Milestone: 1.0 Created attachment 158516 --> https://bugs.kde.org/attachment.cgi?id=158516=edit Logging of Plasmashell monitoring SUMMARY *** After I enable, and then disable my second monitor with the Nvidia driver, Plasmashell leaks memory rapidly untill the point the system runs out of memory. The issue is ongoing since multiple months/updates. *** STEPS TO REPRODUCE 1. Enable the second monitor in Nvidia Panel 2. Disable the second monitor in Nvidia Panel after a while 3. See Plasmashell increasing its memory usage by a lot constantly OBSERVED RESULT Plasmashell has memory leak EXPECTED RESULT Plasmashell doesn't leak memory SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.25 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION I made a script that I run every minutes with CRON to monitor Plasmashell PID, memory usage, cpu usage, and the second monitor, you can see as soon as I disable my second monitor, memory usage is increasing by a lot and it never stops. I attached the log it produces for you to have a look. You can also see that the CPU usage by Plasmashell is to the roof too at this point (I only added that to the end when I was writing this issue so it appears only at the end). Plasmashell PID also changes after I disable the second monitor. It seems trying to reproduce it quickly from cold boot and enabling/disabling the second monitor after a couple minutes doesn't make the memory leak as quick as it is in the attached log. In the attached log, the second monitor is enabled at "ven. 28 avril 2023 06:20:01 CEST" and is disabled at "ven. 28 avril 2023 14:40:01 CEST" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 omano changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 --- Comment #10 from omano --- I can confirm that on Wayland with the focus stealing prevention set to LOW, the taskbar stays on top too when the game starts. But there is a difference, clicking inside the game makes the taskbar go in the background. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 --- Comment #8 from omano --- Thanks for testing, I will try to setup Wayland later to confirm the behavior, however I just wanted to interject to make sure there is no confusion. I'm talking about Unreal Engine 3 games, Killing Floor 2 is one of them. It is not a Unity game. Far Cry also is a Cry Engine game, so again not the same game engine, which would explain the different behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 --- Comment #3 from omano --- I'm using X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 --- Comment #1 from omano --- I don't know what happened but there is no summary :\ Basically, every single Unreal Engine 3 game I start as a Steam/Proton game, starts fullscreen but with the taskbar visible over the game, BUT the game still has focus and you can interact with it. Setting Focus Stealing Prevention to NONE seems to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466160] New: Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games
https://bugs.kde.org/show_bug.cgi?id=466160 Bug ID: 466160 Summary: Taskbar visible in Steam Proton fullscreen games in Unreal Engine 3 games Classification: Plasma Product: kwin Version: 5.26.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: om...@redorchestra2.fr 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. Set Focus Stealing Prevention settings to something other than NONE 2. Start an Unreal Engine 3 game from Steam (Windows/Proton game) OBSERVED RESULT The taskbar is visible in the fullscreen game (you can play the game normally, interact with the game with no issue) EXPECTED RESULT The taskbar disappears when the fullscreen game is started SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 6.1.12 / KDE 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Here is the old Proton issue about it, where there is a link to the commit that supposedly fix this reoccurring issue (this was already fixed couple years ago) https://github.com/ValveSoftware/Proton/issues/3945 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 458390] New: Text file preview in internal text editor produces error in system journal
https://bugs.kde.org/show_bug.cgi?id=458390 Bug ID: 458390 Summary: Text file preview in internal text editor produces error in system journal Product: ark Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: om...@redorchestra2.fr CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY Every time you preview a text file from withing the archive, it produces error in system journal STEPS TO REPRODUCE 1. open an archive 2. preview a text file within archive, it opens in the internal text editor window 3. journal has error logged : ark[85751]: kf.xmlgui: Shortcut for action "close" "" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. OBSERVED RESULT nothing seems broken visually EXPECTED RESULT no error produced in journal SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436300] More disk usage reported in Plasma System Monitor then what other tools report
https://bugs.kde.org/show_bug.cgi?id=436300 omano changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #9 from omano --- How is the disk usage supposed to be counted, please answer so I can verify it works, because currently it seems it doesn't. If I unmount all drives but one, and restart System Monitor, then it keeps the previous disk usage (which is not correct anyway). If I mount all my drives, still kinda the same but different, it adds a wrong ammount to used/total, and when I unmount all these freshly mounted drives, then it stick with the new wrong value... SOFTWARE/OS VERSIONS Linux: 5.12.15-1 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 436473] Cursor is stuck to resize icon when hovering into panels across the movable dividers
https://bugs.kde.org/show_bug.cgi?id=436473 omano changed: What|Removed |Added CC||om...@redorchestra2.fr --- Comment #51 from omano --- I can confirm the workaround works! This was annoying as hell. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436300] More disk usage reported in Plasma System Monitor then what other tools report
https://bugs.kde.org/show_bug.cgi?id=436300 omano changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436300] More disk usage reported in Plasma System Monitor then what other tools report
https://bugs.kde.org/show_bug.cgi?id=436300 --- Comment #4 from omano --- Can you tell me how it calculates Disks in Overview page? I have multiple disks, half of them being mounted. What should I expect from Disks in Overview page? What does it calculate? Here are some more info, I actually found more issues: Initial state two disks mounted: https://i.imgur.com/7vplv8d.png Second disk unmounted: https://i.imgur.com/yR2uTm6.png Then I mount back the second disk: https://i.imgur.com/mTn3GDK.png It doesn't make sense. I tried to restart System Monitor but result is the same. Can you maybe try on your side to reproduce the issues? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436300] More disk usage reported in Plasma System Monitor then what other tools report
https://bugs.kde.org/show_bug.cgi?id=436300 --- Comment #3 from omano --- I could but Disks in Overview is a percentage it doesn't list any value. Hence the part where I explain the calculation of "df -H" output. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 436300] New: More disk usage reported in Plasma System Monitor then what other tools report
https://bugs.kde.org/show_bug.cgi?id=436300 Bug ID: 436300 Summary: More disk usage reported in Plasma System Monitor then what other tools report Product: plasma-systemmonitor Version: 5.21.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: om...@redorchestra2.fr CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Seems like there is a slight difference in the free space reported in Disks in Overview page, compared to manually calculating from the output of tools like "df -H". Seems like Plasma System Monitor reports more disk usage than what is manually calculated. STEPS TO REPRODUCE 1. Open the Overview page of Plasma System Monitor and check Disk usage 2. Calculate manually your disk usage from output of "df- H" command 3. Note the difference of around 4% OBSERVED RESULT Monitor reports more disk usage EXPECTED RESULT Monitor reports accurate disk usage SOFTWARE/OS VERSIONS Linux: 5.10.32 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION There may be an explanation but so far I didn't find exactly how Plasma System Monitor calculates the disk usage. If someone can share the details about that it could help find the culprit, if this is not intended. -- You are receiving this mail because: You are watching all bug changes.
