https://bugs.kde.org/show_bug.cgi?id=465522
Naxdy changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=465522
--- Comment #5 from Naxdy ---
(In reply to Vlad Zahorodnii from comment #4)
> Do you use libstdc++ or libc++?
libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6
(0x7fba6780)
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=465558
Bug ID: 465558
Summary: 5.27: [wayland only] tooltips from desktop plasmoids
can show up even when behind applications
Classification: Plasma
Product: plasmashell
Version: 5.26.90
https://bugs.kde.org/show_bug.cgi?id=465522
Naxdy changed:
What|Removed |Added
Summary|(wayland) seemingly random |(wayland) possible crash in
|crash
https://bugs.kde.org/show_bug.cgi?id=465522
--- Comment #6 from Naxdy ---
Some more info: Just now as I tried reproducing this crash again (lock screen
-> wait for display to sleep -> wake display -> unlock screen), although kwin
didn't crash, I found that the padding of the cus
https://bugs.kde.org/show_bug.cgi?id=465595
Bug ID: 465595
Summary: 5.27: task manager hover is sluggish
Classification: Plasma
Product: plasmashell
Version: 5.26.90
Platform: Gentoo Packages
OS: Linux
Status: R
https://bugs.kde.org/show_bug.cgi?id=465595
Naxdy changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=465595
--- Comment #3 from Naxdy ---
Is it possible to implement the delay only if a tooltip / window list is
present, or is that nontrivial?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465323
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=465595
--- Comment #5 from Naxdy ---
I have tooltips and window lists disabled personally, so I don't think I'm
entirely qualified to comment, but instinctively I'd say yes, a delay there
seems reasonable, so you don't accidentally &q
https://bugs.kde.org/show_bug.cgi?id=454616
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=465323
--- Comment #8 from Naxdy ---
Created attachment 156186
--> https://bugs.kde.org/attachment.cgi?id=156186&action=edit
Comparison of Xwayland window with Breeze (dark pixel) and native Wayland
window with Breeze
No, it isn't. In the vi
https://bugs.kde.org/show_bug.cgi?id=465323
Naxdy changed:
What|Removed |Added
Component|aurorae |decorations
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=465323
--- Comment #9 from Naxdy ---
Also, not sure how relevant this is, but if using the third-party KWin effect
LightlyShaders ( https://github.com/a-parhom/LightlyShaders ), which rounds all
corners of a window, this problem disappears entirely
https://bugs.kde.org/show_bug.cgi?id=465662
Bug ID: 465662
Summary: [22.11] Wayland: Background animation only plays while
mouse is being moved in window.
Classification: Applications
Product: kweather
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=454616
--- Comment #6 from Naxdy ---
That's true, however that's also true on X11. Maybe not for plasmashell (don't
remember right now), but for various other applications.
I find that under X11, if I change the cursor theme, it tends to be
https://bugs.kde.org/show_bug.cgi?id=465662
--- Comment #1 from Naxdy ---
Could be upstream, as Linphone is also affected by this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465662
--- Comment #3 from Naxdy ---
Yep, flatpak version exhibits the exact same behavior.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465662
Naxdy changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=465252
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=464417
--- Comment #5 from Naxdy ---
Something else I've just noticed: This bug disappears when the window in
question is constantly rendering something.
To confirm this, you can follow these steps:
1. Open Firefox
2. Enable the server-side titlebar
3.
https://bugs.kde.org/show_bug.cgi?id=455526
--- Comment #24 from Naxdy ---
(In reply to Andrej Halveland from comment #18)
> After many hours of bisecting (and wasting my time on bisecting whatever was
> already bisected, and fixed... sigh), I have come to this
> (https://invent.kde.o
https://bugs.kde.org/show_bug.cgi?id=454349
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=466655
Bug ID: 466655
Summary: Wayland: Red and blue channels are swapped when
screencasting in certain applications
Classification: Plasma
Product: kwin
Version: 5.27.2
Platform: Ot
https://bugs.kde.org/show_bug.cgi?id=466655
Naxdy changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=466674
Bug ID: 466674
Summary: Wayland: kscreenlocker crashes on when display enters
sleep
Classification: Plasma
Product: kscreenlocker
Version: 5.27.2
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=466674
Naxdy changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=466674
--- Comment #1 from Naxdy ---
Backtrace:
Thread 1 "kscreenlocker_g" received signal SIGSEGV, Segmentation fault.
0x7fecd208d3db in serialize_closure () from
/usr/lib64/libwayland-client.so.0
#0 0x7fecd208d3db in serialize_closure ()
https://bugs.kde.org/show_bug.cgi?id=466674
--- Comment #3 from Naxdy ---
Letting the display turn off naturally doesn't seem to produce this bug. Locked
the screen, waited 10+ mins, woke up the display, and it was fine.
Manually turning it off using ESC always produces this problem t
https://bugs.kde.org/show_bug.cgi?id=466747
Bug ID: 466747
Summary: Wayland: Invert effect causes certain UI elements to
stutter
Classification: Plasma
Product: kwin
Version: 5.27.2
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=466747
Naxdy changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=466785
Bug ID: 466785
Summary: Wayland: Red and blue channels are swapped for cursor
when screencasting in certain applications
Classification: Plasma
Product: kwin
Version: 5.27.2
P
https://bugs.kde.org/show_bug.cgi?id=466844
Bug ID: 466844
Summary: Wayland: Clipboard history is not always on top
Classification: Plasma
Product: plasmashell
Version: 5.27.2
Platform: Other
OS: Linux
Status: R
https://bugs.kde.org/show_bug.cgi?id=466674
Naxdy changed:
What|Removed |Added
Keywords||regression
Component|general
https://bugs.kde.org/show_bug.cgi?id=466674
Naxdy changed:
What|Removed |Added
Summary|Wayland: kscreenlocker |Wayland: various apps crash
|crashes
https://bugs.kde.org/show_bug.cgi?id=466674
--- Comment #6 from Naxdy ---
Here you go, these are the full logs from start to crash when the display
turned off:
kf.kirigami: Failed to find a Kirigami platform plugin
Locked at 1678032889
qt.qpa.wayland: Wayland does not support QWindow
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #4 from Naxdy ---
Interestingly, this issue is not present on my Fedora laptop (Intel integrated
graphics).
Perhaps Fedora is applying some patch that inadvertently fixes this issue? Or
it could be GPU related?
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #6 from Naxdy ---
@Prajna can you confirm which combination of pulseaudio / pipewire your Arch
Linux install is using?
Particularly, I'm interested in which alsa plugin you have installed. On my
Gentoo install I have the pulseaudio
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #8 from Naxdy ---
Just swapped my pulseaudio plugin for the pipewire one and also don't see any
improvement. I'm definitely leaning towards Fedora doing something now. Would
be great if we could get reports from people using oth
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #11 from Naxdy ---
Interesting. I didn't have KMix installed, and installing / enabling it, having
it running (or not) didn't change anything for me - indicator still had its
incorrect behavior.
I will test booting from a Fedor
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #13 from Naxdy ---
I don't have EasyEffects installed either. Based on the fact that it works for
you using a clean user, I think the problem might be config related. Did you
customize your plasma panel in any way? E.g. mine is on th
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #15 from Naxdy ---
Hey look at that, you're right! If I disconnect / disable all input devices
except one, the indicator works as expected!
Likewise, if I do have multiple input devices connected, but I select the first
one in the
https://bugs.kde.org/show_bug.cgi?id=465301
Naxdy changed:
What|Removed |Added
Summary|5.27: Microphone indicator |5.27: Microphone indicator
|and
https://bugs.kde.org/show_bug.cgi?id=465301
--- Comment #16 from Naxdy ---
On a side note, this could also explain why sometimes it worked fine for you
after rebooting, since perhaps the order of devices got mixed up, and whenever
your active input device was at the top of the list, the
https://bugs.kde.org/show_bug.cgi?id=467516
Bug ID: 467516
Summary: Collision between Mouse Mark and Custom Tiling
keyboard shortcuts
Classification: Plasma
Product: kwin
Version: 5.27.2
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=457729
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=457727
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=446924
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=455526
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=424485
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=448839
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=458655
Naxdy changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=459774
Bug ID: 459774
Summary: Make "resident" notifications the default.
Classification: Plasma
Product: plasmashell
Version: master
Platform: unspecified
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #1 from Naxdy ---
Created attachment 152492
--> https://bugs.kde.org/attachment.cgi?id=152492&action=edit
Example of how notifications look with "resident" forced to "true"
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #7 from Naxdy ---
Created attachment 152494
--> https://bugs.kde.org/attachment.cgi?id=152494&action=edit
A Discord notification with the "resident = true" hack applied
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #8 from Naxdy ---
(In reply to David Edmundson from comment #4)
> There's a massive difference between what your saying happens and the spec.
>
> " When set the server will not automatically remove the notification w
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #12 from Naxdy ---
(In reply to Nate Graham from comment #9)
> It sounds like you're using this hack as a workaround for the lack of Bug
> 407667? Can we fix that without doing this?
I'm using it as a workaround for http
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #14 from Naxdy ---
(In reply to Nate Graham from comment #13)
> Why can't we just make expired non-resident notifications clickable in the
> history view, such that clicking on them launches or activates the app that
> sent th
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #15 from Naxdy ---
I've submitted a much-less-hacky implementation here:
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2178
This does not touch resident functionality at all and should therefore mitigate
any pote
https://bugs.kde.org/show_bug.cgi?id=467516
--- Comment #2 from Naxdy ---
Then I see solution 1 as the only viable option.
Though I'm not sure if Meta+Control would incur any other collisions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449709
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=468456
Bug ID: 468456
Summary: "Exception" type events are seen as their own
standalone events
Classification: Plasma
Product: plasmashell
Version: 5.27.4
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=468458
Bug ID: 468458
Summary: Events are capped at 5 per day
Classification: Plasma
Product: plasmashell
Version: 5.27.4
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=468538
Bug ID: 468538
Summary: Wayland: Upon display entering sleep and being woken,
certain windows are placed out of bounds
Classification: Plasma
Product: kwin
Version: 5.27.4
Pla
https://bugs.kde.org/show_bug.cgi?id=468538
--- Comment #2 from Naxdy ---
This was tested on Wayland. Not sure if it also happens on X11.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=470288
Bug ID: 470288
Summary: Cannot pick any reminder time other than "on event
start"
Classification: Applications
Product: kalendar
Version: 23.04.1
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=470288
Naxdy changed:
What|Removed |Added
Keywords||regression
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=425315
Naxdy changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=468538
--- Comment #6 from Naxdy ---
Shouldn't it be the other way around, given that this bug was reported first?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469034
Naxdy changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=469034
--- Comment #5 from Naxdy ---
Just quick drop by to report that Dolphin has disappeared to 6513, 4727 (this
is well out of bounds considering my monitor is 5120x1440). Its previous
position was 4070, 831.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=462399
Naxdy changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=458279
--- Comment #3 from Naxdy ---
Created attachment 152719
--> https://bugs.kde.org/attachment.cgi?id=152719&action=edit
New crash information added by DrKonqi
latte-dock (0.10.77) using Qt 5.15.5
In my instance, I clicked on an already open
https://bugs.kde.org/show_bug.cgi?id=458279
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=460265
Bug ID: 460265
Summary: [WAYLAND] 1 pixel high gap between application content
and window decoration
Classification: Plasma
Product: kwin
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=460265
--- Comment #2 from Naxdy ---
(In reply to Nate Graham from comment #1)
> Cannot reproduce at 200% scale. But it seems plausible given the floating
> point positioning work we did for Plasma 5.26.
Sorry forgot to mention, this is at 100% scal
https://bugs.kde.org/show_bug.cgi?id=459774
--- Comment #18 from Naxdy ---
(In reply to Carlos Solís from comment #17)
> Regarding the implementation, I was under the impression that the hints
> boolean values, which include the "resident" and "transient"
https://bugs.kde.org/show_bug.cgi?id=464417
Naxdy changed:
What|Removed |Added
CC||xna...@hydra-development.ne
https://bugs.kde.org/show_bug.cgi?id=460265
--- Comment #4 from Naxdy ---
Seems to have disappeared somewhere in the 5.26 cycle, I'll keep an eye on it
over the lifespan of 5.27
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465227
Bug ID: 465227
Summary: Wine system tray entries are not interactable under
Wayland
Classification: Plasma
Product: plasmashell
Version: master
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #2 from Naxdy ---
- Display -
Global Scale: 100%
Refresh Rate: 120Hz
Resolution: 5120x1440
- Font -
Anti-Aliasing: ENABLED
Exclude range from anti-aliasing: DISABLED
Sub-pixel rendering: None
Hinting: Slight
Force Font DPI: DISABLED
https://bugs.kde.org/show_bug.cgi?id=465227
Naxdy changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #4 from Naxdy ---
It hasn't worked in 5.26, not sure about prior versions since I didn't really
try out Wayland before that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #6 from Naxdy ---
Rockstar Games Launcher, Ubisoft Connect, and IINACT all exhibit this problem
for me.
IINACT should be the easiest to test since it's just a portable application
that sits in the tray: https://github.com/marzent/I
https://bugs.kde.org/show_bug.cgi?id=465301
Bug ID: 465301
Summary: 5.27: Microphone indicator and popup display
conflicting information upon toggle
Classification: Plasma
Product: plasmashell
Version: master
Platform:
https://bugs.kde.org/show_bug.cgi?id=465302
Bug ID: 465302
Summary: 5.27: Ending a Pipewire recording / screen sharing
does not actually end it
Classification: Plasma
Product: plasmashell
Version: 5.26.90
Platform: Gent
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #8 from Naxdy ---
Upon further testing, I've discovered that this bug only occurs when the panel
is placed at the top of the screen.
If I move my panel to the bottom, then the context menu appears no problem, but
if I move it to th
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #11 from Naxdy ---
Applied your patch locally, but still doesn't work for me (context menu doesn't
show on right click)
My systray is in the top right, screen resolution is 5120x1440, panel height is
32px
If I move the panel to
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #14 from Naxdy ---
> Did you also apply
> https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2503 ?
Not explicitly, but I'm building the latest 5.27 branch and also checked my
local copy and that MR is already in.
https://bugs.kde.org/show_bug.cgi?id=465367
Bug ID: 465367
Summary: 5.27: Blur effect stops working / produces artifacts
after a while (wayland)
Classification: Plasma
Product: kwin
Version: 5.26.90
Platform: Gentoo Pac
https://bugs.kde.org/show_bug.cgi?id=465227
--- Comment #15 from Naxdy ---
Correction: The MR does indeed fix the issue for me. My problem was that Gentoo
isolates xembed-sni-proxy into its own package, which I did not apply the patch
to.
All good from my end!
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=465397
Bug ID: 465397
Summary: Pretty big memory leak in X11 only
Classification: Plasma
Product: plasmashell
Version: 5.26.90
Platform: Gentoo Packages
OS: Linux
Status: REP
https://bugs.kde.org/show_bug.cgi?id=465397
Naxdy changed:
What|Removed |Added
Summary|Pretty big memory leak in |5.27: Pretty big memory
|X11 only
https://bugs.kde.org/show_bug.cgi?id=465302
--- Comment #2 from Naxdy ---
Additional Info: This seems to only affect apps running outside flatpak. Those
running under flatpak (tested with Slack & Google Chrome) have their recording
/ streaming freeze when the "end" button is cli
https://bugs.kde.org/show_bug.cgi?id=465367
--- Comment #1 from Naxdy ---
Further testing indicates this is probably related to the display turning on /
off.
As the glitch happened again (with dolphin), I manually turned the display off
and then on again, after which Dolphin's window was o
https://bugs.kde.org/show_bug.cgi?id=465397
Naxdy changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=465302
--- Comment #3 from Naxdy ---
Think I've found the issue, MR is up:
https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/159
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465522
Bug ID: 465522
Summary: (wayland) seemingly random crash in
KWin::Tile::descendants()
Classification: Plasma
Product: kwin
Version: 5.26.90
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=465522
--- Comment #1 from Naxdy ---
After more investigation, it appears that the crash has a chance to occur every
time the display is woken from sleep. For me, this is usually in the morning,
since I leave the display off overnight with the screen locked
https://bugs.kde.org/show_bug.cgi?id=488816
Bug ID: 488816
Summary: When using a top panel "Text Only" system monitor
sensor widgets have dramatically reduced size compared
to 6.0, and are offset to the top
Classification: Plasma
1 - 100 of 276 matches
Mail list logo
