https://bugs.kde.org/show_bug.cgi?id=436654
wokim changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #24 from wokim ---
(In reply to Nate Graham from comment #23)
> > However, there's a new bug. The task bar freezes randomly
> That was Bug 449163, which is fixed now.
>
> Let's keep this bug for the excessive
https://bugs.kde.org/show_bug.cgi?id=414834
wokim changed:
What|Removed |Added
CC|mequer...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=476018
wokim changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=477016
--- Comment #4 from wokim ---
I did a system upgrade, including some KDE packages (to v6.0.4) , and now the
brightness flickering even happens when watching a video in fullscreen. Before
the update, watching a fullscreen video would set the refreshrate
https://bugs.kde.org/show_bug.cgi?id=477016
--- Comment #7 from wokim ---
(In reply to Ataberk Özen from comment #5)
> There's a regression in 6.0.4 release of kwin. I've downgraded it back to
> 6.0.3 and everything is fine here.
I just tried playing a game and it stutters like
https://bugs.kde.org/show_bug.cgi?id=485730
Bug ID: 485730
Summary: Severe stuttering with Plasma 6.0.4
Classification: Plasma
Product: kwin
Version: 6.0.4
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=485730
--- Comment #3 from wokim ---
Reverting this commit and rebuilding kwin fixes the stuttering for me, both
with VRR disabled or enabled:
https://invent.kde.org/plasma/kwin/-/commit/19ffe2ac411b866cd646942d4e3cfb41d8ca89a1
I tried reverting that commit
https://bugs.kde.org/show_bug.cgi?id=485639
wokim changed:
What|Removed |Added
CC||t...@nijstekje.nl
--- Comment #4 from wokim ---
(In
https://bugs.kde.org/show_bug.cgi?id=485730
--- Comment #5 from wokim ---
(In reply to Bug Janitor Service from comment #4)
> A possibly relevant merge request was started @
> https://invent.kde.org/plasma/kwin/-/merge_requests/5626
Just tested it and I can confirm that only applyi
https://bugs.kde.org/show_bug.cgi?id=453356
Bug ID: 453356
Summary: Unable to click/activate notification from history
Product: plasmashell
Version: 5.24.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=451301
--- Comment #9 from wokim ---
(In reply to Christoph Cullmann from comment #8)
> There is no sane way to avoid this crash in KTextEditor or Kate/KWrite.
Like I said earlier, KWrite does not crash when doing the same.
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=451301
Bug ID: 451301
Summary: Kate crashes when opening a file while save file
dialog is open
Product: kate
Version: 21.12.3
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=451301
--- Comment #2 from wokim ---
(In reply to Christoph Cullmann from comment #1)
> Hmm, the Save As... dialog should be modal, I am not able to click File ->
> Open... at all.
Oh, yeah, I used the Application menu in the Titlebar (customi
https://bugs.kde.org/show_bug.cgi?id=451301
--- Comment #4 from wokim ---
(In reply to Christoph Cullmann from comment #3)
> Have you some backtrace for the crash?
No, but if you put the Application menu in the Titlebar through System
Settings, you'll probably get the same behavior.
https://bugs.kde.org/show_bug.cgi?id=434584
wokim changed:
What|Removed |Added
CC||mequer...@gmail.com
--- Comment #3 from wokim
https://bugs.kde.org/show_bug.cgi?id=441707
Bug ID: 441707
Summary: Consistent crash when hitting "Apply" in Window Rules
Product: systemsettings
Version: 5.22.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=414834
wokim changed:
What|Removed |Added
CC|mequer...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=436654
wokim changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=439353
Bug ID: 439353
Summary: ramdom kwin-wayland crash
Product: kwin
Version: 5.22.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priori
https://bugs.kde.org/show_bug.cgi?id=439353
--- Comment #1 from wokim ---
Created attachment 139771
--> https://bugs.kde.org/attachment.cgi?id=139771&action=edit
backtrace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=439353
--- Comment #2 from wokim ---
Created attachment 139772
--> https://bugs.kde.org/attachment.cgi?id=139772&action=edit
core backtrace
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #2 from wokim ---
(In reply to Bharadwaj Raju from comment #1)
> Can you reproduce the issue on X11?
On X11, the task manager still lags and plasmashell also fully loads one
thread, but there are no hangs or crashes.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #4 from wokim ---
(In reply to Nate Graham from comment #3)
> Can you please attach a backtrace of the crash? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports
I tried attaching
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #6 from wokim ---
(In reply to Nate Graham from comment #5)
> Just load plasmashell into gdb before it crashes:
>
>
> ```
> killall plasmashell
> gdb /usr/bin/plasmashell
> run
> [make it crash]
> bt
>
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #9 from wokim ---
(In reply to Nate Graham from comment #5)
> Just load plasmashell into gdb before it crashes:
>
>
> ```
> killall plasmashell
> gdb /usr/bin/plasmashell
> run
> [make it crash]
> bt
> ```
https://bugs.kde.org/show_bug.cgi?id=463067
wokim changed:
What|Removed |Added
CC||mequer...@gmail.com
--- Comment #7 from wokim ---
I&#
https://bugs.kde.org/show_bug.cgi?id=477016
Bug ID: 477016
Summary: VRR always enabled in full-screen, ignores/overrides
drirc.d config
Classification: Plasma
Product: kwin
Version: 5.27.9
Platform: Archlinux
https://bugs.kde.org/show_bug.cgi?id=460329
--- Comment #12 from wokim ---
(In reply to dfodre from comment #10)
> I seem to have found a better solution, using `radeon-profile` and disabling
> the lowest available Core clock in the overclock section (in my case that
> would be 500MHz,
https://bugs.kde.org/show_bug.cgi?id=456697
wokim changed:
What|Removed |Added
CC||mequer...@gmail.com
--- Comment #5 from wokim ---
(In
https://bugs.kde.org/show_bug.cgi?id=476018
--- Comment #9 from wokim ---
(In reply to Zamundaaa from comment #3)
> There's no flag that says they're generated, they're all "driver". So I'm
> afraid we can't even mark them as generated in kscreen-docto
https://bugs.kde.org/show_bug.cgi?id=477016
--- Comment #2 from wokim ---
(In reply to Zamundaaa from comment #1)
> It's not a bug, Mesa enabling or disabling vrr for specific fullscreen
> programs is an X11 thing and has no relevance on Wayland.
> The brightness flicker is so
https://bugs.kde.org/show_bug.cgi?id=476018
--- Comment #10 from wokim ---
(In reply to wokim from comment #8)
> Another problem is that even if I select the real 120 Hz through
> kscreen-doctor, it'll default/revert back to the fake 120 Hz after a reboot
> or after restarting KDE.
https://bugs.kde.org/show_bug.cgi?id=460329
wokim changed:
What|Removed |Added
CC||mequer...@gmail.com
--- Comment #6 from wokim ---
(In
https://bugs.kde.org/show_bug.cgi?id=476018
Bug ID: 476018
Summary: Fake refresh rates when using adaptive sync (VRR)
Classification: Plasma
Product: KScreen
Version: 5.27.8
Platform: Archlinux
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=460329
--- Comment #9 from wokim ---
(In reply to dfodre from comment #7)
> Both profile_standard and profile_peak fix the issue for me. I have a
> 6950XT, so that means idle power consumption of 90W and 220W respectively,
> according to `sensors` an
https://bugs.kde.org/show_bug.cgi?id=476018
--- Comment #2 from wokim ---
(In reply to Zamundaaa from comment #1)
> You can check the modes the kernel advertises with drm_info, but I'm 100%
> sure that KWin doesn't generate any such modes. There's probably a bug in
>
https://bugs.kde.org/show_bug.cgi?id=476018
wokim changed:
What|Removed |Added
Resolution|UPSTREAM|WAITINGFORINFO
--- Comment #4 from wokim ---
(In
https://bugs.kde.org/show_bug.cgi?id=476018
wokim changed:
What|Removed |Added
Resolution|UPSTREAM|WAITINGFORINFO
--- Comment #6 from wokim ---
(In
https://bugs.kde.org/show_bug.cgi?id=476018
--- Comment #7 from wokim ---
(In reply to wokim from comment #6)
> (In reply to Zamundaaa from comment #5)
> > Yes. You can report the modes being generated despite the option being off,
> > and the image being distorted with some o
https://bugs.kde.org/show_bug.cgi?id=476018
--- Comment #8 from wokim ---
(In reply to wokim from comment #7)
> I also tried Gnome, and they list every refresh rate (all real and all fake
> refresh rates). And because they use decimals (e.g. 120.00 Hz and 119.94 Hz)
> I can distinguis
https://bugs.kde.org/show_bug.cgi?id=439353
wokim changed:
What|Removed |Added
Summary|ramdom kwin-wayland crash |random kwin-wayland crash
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #19 from wokim ---
(In reply to Vlad Zahorodnii from comment #18)
> Can you run plasmashell with WAYLAND_DEBUG=1 environment variable and post
> the output here? It might be a duplicate of bug 447717
I'm on plasma 5.23.5 now,
https://bugs.kde.org/show_bug.cgi?id=449431
Bug ID: 449431
Summary: PlasmaUserFeedback crashes/freezes whole desktop
Product: plasmashell
Version: 5.23.5
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #21 from wokim ---
(In reply to Vlad Zahorodnii from comment #18)
> Can you run plasmashell with WAYLAND_DEBUG=1 environment variable and post
> the output here? It might be a duplicate of bug 447717
Here is an archive of the logs:
https://bugs.kde.org/show_bug.cgi?id=436654
--- Comment #13 from wokim ---
(In reply to Bug Janitor Service from comment #12)
> This bug has been in NEEDSINFO status with no change for at least
> 30 days. The bug is now closed as RESOLVED > WORKSFORME
> due to lack of needed infor
46 matches
Mail list logo
