[kate] [Bug 486623] New: Opening this 909kb file in Kate causes it to leak memory and potentially crash the entire system

2024-05-05 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=486623

Bug ID: 486623
   Summary: Opening this 909kb file in Kate causes it to leak
memory and potentially crash the entire system
Classification: Applications
   Product: kate
   Version: 24.02.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: kwrite
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: i...@fdossena.com
  Target Milestone: ---

Created attachment 169211
  --> https://bugs.kde.org/attachment.cgi?id=169211=edit
File that causes the leak

SUMMARY
The attached file is a config file from the game Colin McRae Rally 2005. I
thought it would just be a text file so I tried opening it in Kate, it turned
out to be a binary file, but instead of simply showing garbled text, Kate locks
up, starts leaking memory and eventually gets killed by OOM (or crashes the
whole system if you don't have OOM).

STEPS TO REPRODUCE
1. Open Kate (or KWrite or any application like Ark that previews unknown files
as text)
2. Drag the attached file into it
3. Watch RAM usage

OBSERVED RESULT
Kate freezes and fills up the entire memory

EXPECTED RESULT
Garbled text

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (Kernel 6.8.9-arch1-1)
(available in About System)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 484334] New: Context menus, drop-down menus and tooltips sometimes open as separate windows in Wayland

2024-03-23 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=484334

Bug ID: 484334
   Summary: Context menus, drop-down menus and tooltips sometimes
open as separate windows in Wayland
Classification: Plasma
   Product: kwin
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: decorations
  Assignee: kwin-bugs-n...@kde.org
  Reporter: i...@fdossena.com
  Target Milestone: ---

Created attachment 167658
  --> https://bugs.kde.org/attachment.cgi?id=167658=edit
Screenshot of the issue

SUMMARY
Somtimes when a context menu, a drop-down menu or a tooltip is created, it
opens in the middle of the screen as a fully decorated window that can be
moved, maximised, etc.

This only seems to happen under Wayland.

STEPS TO REPRODUCE
The problem can be easily triggered following these steps:
1. Open dolphin and right click on a file
2. Without closing the context menu, right click an empty area of the desktop
3. The plasmashell context menu opens as a separate window

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux amd64, Linux 6.8.1
(available in About System)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
It's unlikely to be related, but I had to set
QT_SCALE_FACTOR_ROUNDING_POLICY=round because plasmashell was all blurry on my
PC after the upgrade to 6.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 469445] ScreenMapping entry in config file can grow infinitely due to lack of auto-removal of stale entries, which makes plasmashell slow down and eventually crash

2024-01-27 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=469445

--- Comment #47 from Federico Dossena  ---
No, this was fixed a while ago as far as I can tell.

On 1/27/24 08:36, bugzilla_nore...@kde.org wrote:
> https://bugs.kde.org/show_bug.cgi?id=469445
>
> fanzhuyi...@gmail.com changed:
>
> What|Removed |Added
> 
>   CC||fanzhuyi...@gmail.com
>
> --- Comment #46 from fanzhuyi...@gmail.com ---
> I can't seem to reproduce on plasma 6 RC1. Is this still a problem?
>

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 473031] Thunderbird UI invisible/glitching after exiting a fullscreen application

2023-08-07 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=473031

Federico Dossena  changed:

   What|Removed |Added

 Status|RESOLVED|REPORTED
 Resolution|DOWNSTREAM  |---

--- Comment #3 from Federico Dossena  ---
I reported it here because it looks like a compositing issue that seems to be
specific to KDE, version 115 introduced client side decorations so I thought it
could be related. It's not something specific about my system either, I did a
clean install of the OS and as soon as I added my accounts it started doing it
again.

I don't see reports of this issue on their side so I should probably report it
there too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 473031] Thunderbird UI invisible/glitching after exiting a fullscreen application

2023-08-05 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=473031

--- Comment #1 from Federico Dossena  ---
Created attachment 160754
  --> https://bugs.kde.org/attachment.cgi?id=160754=edit
Another example

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 473031] New: Thunderbird UI invisible/glitching after exiting a fullscreen application

2023-08-05 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=473031

Bug ID: 473031
   Summary: Thunderbird UI invisible/glitching after exiting a
fullscreen application
Classification: Plasma
   Product: kwin
   Version: 5.27.7
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: i...@fdossena.com
  Target Milestone: ---

Created attachment 160753
  --> https://bugs.kde.org/attachment.cgi?id=160753=edit
Screenshot of the invisible UI

Since Thunderbird 115 came out if I leave it minimized then play a game or run
any fullscreen application for a while, the UI becomes invisible or a glitchy
mess.

See attached screenshot.

STEPS TO REPRODUCE
1. Launch Thunderbird
2. Minimize it
3. Launch a game, close it
4. Restore Thunderbird



SOFTWARE/OS VERSIONS
Linux: Kernel 6.4.8, Arch Linux, X11
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
The GPU is an AMD 6900xt and I'm running Mesa 23.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash

2023-07-05 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=469445

--- Comment #17 from Federico Dossena  ---
As a temporary workaround for people who are affected by this bug, I just run
this script at login and at logout:

#!/bin/bash
cd ~
sed -i /screenMapping=/d .config/plasma-org.kde.plasma.desktop-appletsrc

It simply removes all the lines that contain "screenMapping=" from that file,
it's a crappy workaround but it's better than having to reset my config every
time it breaks, and it hasn't broken anything in the last couple of months that
I've been using it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash

2023-05-31 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=469445

--- Comment #9 from Federico Dossena  ---
Why did you mark this as fixed? That's a workaround, not a solution.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash

2023-05-22 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=469445

--- Comment #3 from Federico Dossena  ---
That's exactly what I was doing, I work on wine, dxvk and vkd3d and have
several folders where I build them regularly on my desktop.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 470081] New: Desktop not loading after reboot, apps not starting, dmesg full of "comm: plasmashell, not enough memory for the allocation"

2023-05-21 Thread Federico Dossena
https://bugs.kde.org/show_bug.cgi?id=470081

Bug ID: 470081
   Summary: Desktop not loading after reboot, apps not starting,
dmesg full of "comm: plasmashell, not enough memory
for the allocation"
Classification: Plasma
   Product: plasmashell
   Version: 5.27.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Startup process
  Assignee: plasma-b...@kde.org
  Reporter: i...@fdossena.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
This issue has been happening to me every few months for almost 2 years now and
now it finally annoyed me enough to report it.

Every now and then, after a reboot, all my desktop icons are gone, I can't
launch any application from plasmashell, and dozens of GB of RAM are being used
by it.

When it happens, dmesg shows a lot of out of memory errors and restaring
plasmashell has no effect:
```
comm: plasmashell, not enough memory for the allocation
```

To fix this I have no choice but to delete
`~/.config/plasma-org.kde.plasma.desktop-appletsrc` and restart plasmashell,
which resets all my desktop icons, the widgets, and the taskbar to their
defaults, then the issue happens again after a few weeks, sometimes a few
months.

I took a look at my  `~/.config/plasma-org.kde.plasma.desktop-appletsrc` file
before deleting it and it had a line with almost 2 MILLION characters in the
ScreenMapping section, with a really long list of files that have been on my
desktop at some point (either directly or in a subdirectory) and aren't there
anymore. I can't upload this file for privacy reasons unfortunately.

This issue has happened to me on different distros and KDE versions over the
years, not just arch, so it's either me doing something wrong or a plasmashell
bug.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux amd64, Kernel 6.3.2
KDE Plasma Version: 5.27.5 from official repos
KDE Frameworks Version: 5.106.0 from official repos
Qt Version: 5.15.9 from official repos
Graphics Platform: X11

-- 
You are receiving this mail because:
You are watching all bug changes.