https://bugs.kde.org/show_bug.cgi?id=497581
--- Comment #15 from LaughingMan ---
Had and uptime of over two weeks on kernel 6.12.1 and got hit by this bug twice
today. Guess it was just pure luck the bug didn't strike for that long. Either
the culprit isn't the kernel at all or th
https://bugs.kde.org/show_bug.cgi?id=497581
--- Comment #12 from LaughingMan ---
No, I didn't see anything and have no clue what exactly is happening. Reverting
the kernel was a relatively blind guess based on which packages got updated
around the time the problems started for me.
6.12.1 i
https://bugs.kde.org/show_bug.cgi?id=497581
LaughingMan changed:
What|Removed |Added
CC||lingm+kdeb...@posteo.org
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=493987
LaughingMan changed:
What|Removed |Added
CC||lingm+kdeb...@posteo.org
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=494624
LaughingMan changed:
What|Removed |Added
CC||lingm+kdeb...@posteo.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #10 from LaughingMan ---
(In reply to Andrius Štikonas from comment #8)
> I think we've gathered enough data to root cause it. So you can put your disk
> to production.
Cool. Although in case that wasn't clear: My testing
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #7 from LaughingMan ---
Ok:
- Stopped md126.
- Tried creating a partition table -> Failed
- Stopped md127
- Tried creating a partition table -> Success
Maybe Partition Manager should detect this case and run that stop command on
beh
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #5 from LaughingMan ---
So, should I run
> sudo mdadm --stop /dev/md126
or
> sudo mdadm --stop /dev/md127
?
I'm a little out of my depth here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=494548
--- Comment #3 from LaughingMan ---
/dev/md0 doesn't exist. There's md, md126 and md127.
lsblk lists the device as:
> sdf 8:80 0 14,6T 0 disk
>├─md126
https://bugs.kde.org/show_bug.cgi?id=494556
--- Comment #4 from LaughingMan ---
Tried in Firefox' settings and it has the behavior I'd expect.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=494557
--- Comment #2 from LaughingMan ---
"Unfortunately, there doesn't seem to be an easy way to change tab order of
KNewPasswordWidget."
Does that mean the tab order for the password field will still be wrong? :/
That's really the on
https://bugs.kde.org/show_bug.cgi?id=494556
--- Comment #2 from LaughingMan ---
Are you aware of an existing issue on the Qt side? Because it pretty clearly is
a bug, even if partition manager maybe isn't the right place to deploy a fix.
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=494557
Bug ID: 494557
Summary: Create a new partition: Wrong tab order if LUKS
encryption is enabled
Classification: Applications
Product: partitionmanager
Version: 24.08.2
Platform:
https://bugs.kde.org/show_bug.cgi?id=494556
Bug ID: 494556
Summary: Create a new partition: Selecting permissions radio
button with the keyboard focuses wrong option
Classification: Applications
Product: partitionmanager
Version:
https://bugs.kde.org/show_bug.cgi?id=494548
Bug ID: 494548
Summary: Partition Manager fails to create new partition table
if 'ddf_raid_member' signature is present
Classification: Applications
Product: partitionmanager
Version: 2
https://bugs.kde.org/show_bug.cgi?id=490972
LaughingMan changed:
What|Removed |Added
CC||lingm+kdeb...@posteo.org
--- Comment #14 from
https://bugs.kde.org/show_bug.cgi?id=491417
--- Comment #7 from LaughingMan ---
Alright, reading though those links you two posted there appears to be a
consensus that fiddling with fontconfig is a hack and people are working on
adding proper support to Qt. Dolphin relies on Qt, while Nemo and
https://bugs.kde.org/show_bug.cgi?id=491417
--- Comment #3 from LaughingMan ---
If it was a case of missing or misconfigured font, why do both Nemo and Konsole
manage to pick the correct one?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491417
Bug ID: 491417
Summary: Emojis in file names are displayed in black and white
or as tofu
Classification: Applications
Product: dolphin
Version: 24.05.2
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=466814
LaughingMan changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=491367
--- Comment #5 from LaughingMan ---
Created attachment 172384
--> https://bugs.kde.org/attachment.cgi?id=172384&action=edit
Screencast of the broken behaviour
Here's a short screencast.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=491367
--- Comment #3 from LaughingMan ---
Just to make sure: You tried to reproduce with the colored map emoji (🗺️),
right? Because the black and white version from my other report (🗺) does not
cause this problem.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=491367
--- Comment #2 from LaughingMan ---
You mean Konsole settings? Scrollback is set to unlimited, but other than that,
I don't think so. I can reproduce with the Built-in profile at least.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=491327
--- Comment #6 from LaughingMan ---
> UB, quite hard to reach for sure, great catch.
Thanks for the quick fix!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=491367
Bug ID: 491367
Summary: World map emoji breaks rendering
Classification: Applications
Product: konsole
Version: 24.05.2
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=491366
Bug ID: 491366
Summary: Black and white world map emoji overlaps with the
following chars
Classification: Applications
Product: konsole
Version: 24.05.2
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=426588
LaughingMan changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=491327
--- Comment #2 from LaughingMan ---
Tested a bit more. It takes a few tries but reproduction steps are:
1. Open KCalc
2. Either type "(" on the keyboard or click the "(" button.
3. Segfault
Reproduces ~50% of the time with the
https://bugs.kde.org/show_bug.cgi?id=491327
Bug ID: 491327
Summary: KCalc segfault, index out of bounds in
KCalculator::commit_Input_
Classification: Applications
Product: kcalc
Version: 24.05.2
Platform: Other
29 matches
Mail list logo
