https://bugs.kde.org/show_bug.cgi?id=488177
--- Comment #3 from Hanabishi ---
Fixed in systemd v256.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488736
--- Comment #4 from Hanabishi ---
(In reply to Nate Graham from comment #3)
> Thanks. What GPU are you using?
OpenGL core profile renderer: AMD Radeon RX 580 Series (radeonsi, polaris10,
LLVM 17.0.6, DRM 3.57, 6.10.0-rc4)
OpenGL core profile vers
https://bugs.kde.org/show_bug.cgi?id=488736
--- Comment #2 from Hanabishi ---
(In reply to Nate Graham from comment #1)
> Is the panel at the top screen edge?
>
> Does the issue reproduce in a new clean user account on the same machine?
Yes. I tested it on a fresh user account t
https://bugs.kde.org/show_bug.cgi?id=488736
Bug ID: 488736
Summary: "Adaptive" opacity mode does not work
Classification: Plasma
Product: plasmashell
Version: 6.1.0
Platform: Arch Linux
OS: Linux
Status: REPORTE
https://bugs.kde.org/show_bug.cgi?id=488700
Bug ID: 488700
Summary: No "Session > Background services" (kcm_kded) in the
System Settings
Classification: Applications
Product: systemsettings
Version: 6.1.0
Platform: Arch
https://bugs.kde.org/show_bug.cgi?id=488177
--- Comment #2 from Hanabishi ---
Made a report about it upstream.
https://github.com/systemd/systemd/issues/33361
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488177
Hanabishi changed:
What|Removed |Added
CC||i.r.e.c.c.a.k.u.n+bugs.kde
https://bugs.kde.org/show_bug.cgi?id=488455
--- Comment #2 from Hanabishi ---
(In reply to Nate Graham from comment #1)
> This already exists, it's right there on the Entries page under the
> Visibility column. :)
No, I'm talking about standalone widgets. When you use the
https://bugs.kde.org/show_bug.cgi?id=488455
--- Comment #5 from Hanabishi ---
Oh, I genuinely thought that this is a new intentional behavior, not a bug. Ok
then.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488455
--- Comment #3 from Hanabishi ---
Ok, for anyone who don't get it, a particular example:
1. RMB click on the panel => Add widgets...
2. Find "Clipboard" widget and add it to the panel.
3. Clear the clipboard contents.
Result:
Cli
https://bugs.kde.org/show_bug.cgi?id=488455
Bug ID: 488455
Summary: [Feature request] "Always show" for standalone widgets
Classification: Plasma
Product: plasmashell
Version: 6.1.0
Platform: Other
OS: All
Statu
https://bugs.kde.org/show_bug.cgi?id=479084
--- Comment #18 from Hanabishi ---
Ok, I just pointed out the pattern. But yeah, it explains simply by most early
adopters being from Arch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479084
--- Comment #15 from Hanabishi ---
I noticed that all reporters use Arch btw. So much at this point it does not
look like a coincedence.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482653
--- Comment #25 from Hanabishi ---
Created attachment 167436
--> https://bugs.kde.org/attachment.cgi?id=167436&action=edit
demo-6.0.2.mp4
Idk how it will help (is this a sanity check?), but here it is.
I even created a fresh new user to be su
https://bugs.kde.org/show_bug.cgi?id=482653
--- Comment #23 from Hanabishi ---
(In reply to Hanabishi from comment #22)
> Funny enough, no changes in behavior whatsoever.
Actually no, the behavior has changed. It only grabs the focus now, but does
not bring it back on the next layout switch.
https://bugs.kde.org/show_bug.cgi?id=482653
--- Comment #22 from Hanabishi ---
Created attachment 167425
--> https://bugs.kde.org/attachment.cgi?id=167425&action=edit
remove-onActivated.patch
It's exactly the same as on the video above.
In fact I just tried to remove that &quo
https://bugs.kde.org/show_bug.cgi?id=482653
--- Comment #20 from Hanabishi ---
100% can still reproduce it on 6.0.2. I continue to use my patch from Bug
482058 as a workaround.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482058
--- Comment #11 from Hanabishi ---
Why closed as duplicate? This report was created way earlier. Shouldn't it be
vice versa?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482058
--- Comment #7 from Hanabishi ---
I don't see any issues with the volume widget or volume OSD.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482058
--- Comment #5 from Hanabishi ---
I also suspected OSD initially, but disabling it changed nothing. And focus
visibly appears on the panel, so I narrowed it down to the applet itself.
Btw, the problem only appears on a standalone widget. It does not do
https://bugs.kde.org/show_bug.cgi?id=482058
--- Comment #2 from Hanabishi ---
(In reply to Andrey from comment #1)
> Thanks, is it regression since Plasma 5?
Yeah, it was fine in Plasma 5. So it is kind of a regression.
Although, as I see from the commit history, the function was there
https://bugs.kde.org/show_bug.cgi?id=482058
Bug ID: 482058
Summary: Keyboard Layout widget steals focus
Classification: Plasma
Product: plasmashell
Version: master
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=475629
--- Comment #19 from Hanabishi ---
Just want to say that 5.15.12 still triggers the same crash.
kwin_wayland[897]: segfault at 230 ip 7f58b774f0d6 sp 701a9f40
error 6 in libQt5Qml.so.5.15.12[7f58b76a7000+281000] likely on CPU 15 (core 7
https://bugs.kde.org/show_bug.cgi?id=475629
--- Comment #14 from Hanabishi ---
(In reply to Nate Graham from comment #12)
> Isn't Bismuth dead now? I thought Polonium was meant to be its replacement.
Yes, it is effectively abandoned. Polonium still lacks some functionality for
me, tho
https://bugs.kde.org/show_bug.cgi?id=475629
--- Comment #11 from Hanabishi ---
Well, after a day without Bismuth, I didn't faced any crashes. So yeah, that's
it.
Not sure is this report should be closed though. Because I doubt that JS code
is able to trigger segfaults by its own with
https://bugs.kde.org/show_bug.cgi?id=475629
--- Comment #9 from Hanabishi ---
Hmm, I do have Bismuth too.
Despite the crash was never due to windows manipulation, I kinda see a pattern
here.
Obviously we need to try go without it.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=475629
--- Comment #5 from Hanabishi ---
Nah, affinity does not seem to help, it still crashes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475629
--- Comment #4 from Hanabishi ---
> in QV4::Object::insertMember
Yeah, this is the same thing.
I assume there is some cross-thread syncronization issue.
Now I have an idea: restrict "kwin_wayland" process affinity to a single CPU
core.
https://bugs.kde.org/show_bug.cgi?id=476196
--- Comment #3 from Hanabishi ---
Created attachment 162616
--> https://bugs.kde.org/attachment.cgi?id=162616&action=edit
Test archive
Test archive made with '-mtr=off', just in case.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=476196
--- Comment #2 from Hanabishi ---
By the way, opening such archive in debug build causes Ark to crash with failed
assertion.
ASSERT: "isDir()" in file /ark/kerfuffle/archiveentry.cpp, line 90
[1]18771 IOT instruction (core dumped) ar
https://bugs.kde.org/show_bug.cgi?id=476196
--- Comment #1 from Hanabishi ---
The problem is, seems like there is no way to distinguish between directories
and empty files via 7z CLI, without relying on attributes.
Path = test
Size = 0
Packed Size = 0
Modified = 2023-10-28 13:10:47.8804270
CRC
https://bugs.kde.org/show_bug.cgi?id=476196
Hanabishi changed:
What|Removed |Added
Latest Commit||8c7e0a2117fc6db538b3df33b19
https://bugs.kde.org/show_bug.cgi?id=476196
Bug ID: 476196
Summary: Ark fails to parse 7z archive if it was created with
attributes omitted ('-mtr=off')
Classification: Applications
Product: ark
Version: 23.08.1
Platfor
https://bugs.kde.org/show_bug.cgi?id=475629
Bug ID: 475629
Summary: Plasma Wayland session (kwin_wayland) random crashes
(segfault)
Classification: Plasma
Product: kwin
Version: 5.27.8
Platform: Archlinux
https://bugs.kde.org/show_bug.cgi?id=456797
--- Comment #1 from Hanabishi ---
Fix: https://invent.kde.org/utilities/ark/-/merge_requests/134
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456797
Hanabishi changed:
What|Removed |Added
Latest Commit||0eea2195fc1a97778e4b970ac50
https://bugs.kde.org/show_bug.cgi?id=456797
Bug ID: 456797
Summary: Ark doesn't work with original 7-Zip
Product: ark
Version: 22.04.3
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: norm
https://bugs.kde.org/show_bug.cgi?id=444317
Hanabishi changed:
What|Removed |Added
CC||irecca@gmail.com
--- Comment #1 from Hanabishi
38 matches
Mail list logo
