https://bugs.kde.org/show_bug.cgi?id=465977
Bug ID: 465977
Summary: ASSERT failure in Uils::exec: "Query failed:UNIQUE
constraint failed: ResourceInfo.targettedResource
Classification: Plasma
Product: kactivitymanagerd
Version: m
https://bugs.kde.org/show_bug.cgi?id=465357
--- Comment #6 from Dāvis ---
By the way it's not even that unusual use case. I have both NFS and Samba
mounts in `/etc/fstab` aswell. Several reasons :P And I have been doing this
for like 10 years or so :D
And KDE/Dolphin issue is not really
https://bugs.kde.org/show_bug.cgi?id=465357
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #7 from Dāvis ---
(In
https://bugs.kde.org/show_bug.cgi?id=482077
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #18 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=479721
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #3 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=482746
Bug ID: 482746
Summary: Ugly text/font
Classification: Applications
Product: NeoChat
Version: 24.02.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severit
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #21 from Dāvis ---
Created attachment 166630
--> https://bugs.kde.org/attachment.cgi?id=166630&action=edit
kwin_wayland
(In reply to Jonathan Lopes from comment #16)
> [...]
> If I had enough time, I could try to plug
https://bugs.kde.org/show_bug.cgi?id=482774
Bug ID: 482774
Summary: Still tiny border shown even when set as "No Window
Borders"
Classification: Plasma
Product: kwin
Version: 6.0.1
Platform: Arch Linux
O
https://bugs.kde.org/show_bug.cgi?id=482774
--- Comment #1 from Dāvis ---
Created attachment 166632
--> https://bugs.kde.org/attachment.cgi?id=166632&action=edit
Discord border
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482774
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=482774
Dāvis changed:
What|Removed |Added
Attachment #166632|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=482774
--- Comment #4 from Dāvis ---
(In reply to Nate Graham from comment #3)
> This isn't a border, it's an outline. You can turn it off in the Breeze
> decoration config dialog.
Awesome, thanks, that worked! It's in System Settin
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #44 from Dāvis ---
Hmm my backtrace is different than Jonathan's.
#0 KWin::IdleDetector::IdleDetector (this=0x55b8773c4220,
timeout=std::chrono::duration = { 4294967295ms }, parent=0x55b877124e50,
this=, timeout=std::chrono::dur
https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #55 from Dāvis ---
(In reply to Vlad Zahorodnii from comment #46)
> > It looks like some application is using
> > ext_idle_notifier_v1::get_idle_notification() with 4294967295ms as timeout
> > value, it's uint
https://bugs.kde.org/show_bug.cgi?id=482780
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #1 from Dāvis
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #2 from Dāvis ---
Created attachment 166728
--> https://bugs.kde.org/attachment.cgi?id=166728&action=edit
Photo example with HDR disabled
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #3 from Dāvis ---
Ohh it looks like SDR Brightness calculation is wrong. Atleast for me if I set
it to max 542 nits then I get correct saturation but screen is WAY too bright
(it daylight can be fine but at night I don't want to be bl
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #4 from Dāvis ---
No, it's not related to brightness, colors are just wrong, it's very noticeable
when opening `htop` in Konsole and switching between HDR on and HDR off. The
difference is so insane that HDR off looks WAY bette
https://bugs.kde.org/show_bug.cgi?id=482774
--- Comment #6 from Dāvis ---
(In reply to Nate Graham from comment #5)
> The outline is only shown by the Breeze decoration.
That's not true, see my previously attached screenshot "System settings
border", that black outline comes
https://bugs.kde.org/show_bug.cgi?id=483107
Bug ID: 483107
Summary: Plasma doesn't provide any feedback about progress of
Suspend/Sleep
Classification: Plasma
Product: Powerdevil
Version: 6.0.1
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=483107
Dāvis changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=454363
Dāvis changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=454363
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=483141
Bug ID: 483141
Summary: KMail doesn't exit/froze/hung
Classification: Applications
Product: kmail2
Version: 6.0.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=483149
Bug ID: 483149
Summary: Konsole's content doesn't update/is stuck/frozen
Classification: Applications
Product: konsole
Version: 24.02.0
Platform: Arch Linux
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=483149
--- Comment #1 from Dāvis ---
By the way I figured out how to get it unstuck, if I resize Konsole's window
with mouse then it gets unstuck and content renders/works again :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482768
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #2 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=482768
Dāvis changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=464258
Dāvis changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=482768
Dāvis changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=480835
Dāvis changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #9 from Dāvis ---
Created attachment 166908
--> https://bugs.kde.org/attachment.cgi?id=166908&action=edit
Android (MIUI) HDR/Color settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #10 from Dāvis ---
Created attachment 166909
--> https://bugs.kde.org/attachment.cgi?id=166909&action=edit
Android (MIUI) HDR/Color settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #11 from Dāvis ---
Created attachment 166910
--> https://bugs.kde.org/attachment.cgi?id=166910&action=edit
Android (MIUI) HDR/Color settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #12 from Dāvis ---
Created attachment 166911
--> https://bugs.kde.org/attachment.cgi?id=166911&action=edit
Android (MIUI) HDR/Color settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #13 from Dāvis ---
Created attachment 166912
--> https://bugs.kde.org/attachment.cgi?id=166912&action=edit
Android (MIUI) HDR/Color settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #14 from Dāvis ---
> (In reply to Dāvis from comment #1)
> > Also for me that SDR Color Intensity slider doesn't work at all, it does
> > nothing - no visual change between 0% and 100%.
> That's bug 482809
&
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #15 from Dāvis ---
By the way another interesting thing regarding =>
https://webkit.org/blog-files/color-gamut/Webkit-logo-P3.png
My phone's photo viewer does show logo in these modes:
* Standard color mode is enabled (Contrast wil
https://bugs.kde.org/show_bug.cgi?id=483038
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #1 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=482780
--- Comment #16 from Dāvis ---
I just tested Colorblindness Correction (in Window Management => Desktop
Effects) and it doesn't work at all in HDR mode, I basically get nearly black
screen (it's incredibly dim) so there definitivel
https://bugs.kde.org/show_bug.cgi?id=473808
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=479891
--- Comment #24 from Dāvis ---
(In reply to Nate Graham from comment #23)
> Apparently setting QT_SCALE_FACTOR_ROUNDING_POLICY=RoundPreferFloor in the
> environment works around this.
Indeed, that makes it look WAY better.
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=389191
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
Version|5.11.95
https://bugs.kde.org/show_bug.cgi?id=389191
--- Comment #37 from Dāvis ---
(In reply to Nate Graham from comment #36)
> (In reply to Dāvis from comment #35)
> > Why this bug report is closed? It's still broken...
> Please see
> https://community.kde.org/Get_Involve
https://bugs.kde.org/show_bug.cgi?id=452011
Bug ID: 452011
Summary: krunner blocks UI
Product: frameworks-krunner
Version: 5.92.0
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=452011
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=452011
--- Comment #2 from Dāvis ---
(In reply to Nate Graham from comment #1)
> This seems to be the culprit:
>
> #5 0x7fd4714fd9ac in QDBusInterface::QDBusInterface(QString const&,
> QString const&, QString const&, QDBusCo
https://bugs.kde.org/show_bug.cgi?id=452011
--- Comment #6 from Dāvis ---
Okay, for now I just uninstalled telepathy runner. But it's very unfortunate
issue because it might not be obvious at all why krunner freezes things and
there could be other slow runners aswell. Many people can have
https://bugs.kde.org/show_bug.cgi?id=454122
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #13 from Dāvis
https://bugs.kde.org/show_bug.cgi?id=460594
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #36 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=461574
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #1 from Dāvis
https://bugs.kde.org/show_bug.cgi?id=464023
Bug ID: 464023
Summary: Deadlock in KToolBarPrivate::init
Classification: Frameworks and Libraries
Product: frameworks-kxmlgui
Version: 5.101.0
Platform: Archlinux
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=464023
Dāvis changed:
What|Removed |Added
Summary|Deadlock in |Stuck in
|KToolBarPrivate::init
https://bugs.kde.org/show_bug.cgi?id=386379
--- Comment #52 from Dāvis ---
(In reply to Nate Graham from comment #51)
> We just implemented the standard line-of-text-based scroll behavior for
> Dolphin, making it consistent with everything else. The fact that scrolling
> long distanc
https://bugs.kde.org/show_bug.cgi?id=414404
Bug ID: 414404
Summary: Sometimes akonadi_pop3_resource and
akonadi_imap_resource crashes on exit
Product: Akonadi
Version: 5.12.3
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=414404
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
Platform|Other
https://bugs.kde.org/show_bug.cgi?id=402882
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #6 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=386379
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #32 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=386379
--- Comment #33 from Dāvis ---
Forgot to mention, using Dolphin 18.12.1 on ArchLinux with libinput
KDE Frameworks 5.54.0
Qt 5.12.0 (built against 5.12.0)
The xcb windowing system
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=402882
--- Comment #8 from Dāvis ---
(In reply to Nate Graham from comment #7)
> (In reply to Dāvis from comment #6)
> > But even that while looks nicer does provide a lot less configuration
> > options than was possible with evdev. For
https://bugs.kde.org/show_bug.cgi?id=386379
--- Comment #41 from Dāvis ---
(In reply to Cqoicebordel from comment #39)
> I understood that.
>
> I was just referencing the comment of Nate Graham
> > I think the height of a single line of text might make sense. If that's not
https://bugs.kde.org/show_bug.cgi?id=386379
--- Comment #43 from Dāvis ---
(In reply to Cqoicebordel from comment #42)
> (In reply to Dāvis from comment #41)
> > That's not possible if you use libinput, see bug #403842
>
> Indeed, but is the bug present when using libinput
https://bugs.kde.org/show_bug.cgi?id=348812
--- Comment #31 from Dāvis ---
I submit a patch to Qt https://codereview.qt-project.org/144745 and with this
patch it now crashes inside NVIDIA library so it seems to be GPU driver bug but
not sure exactly how it's caused.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=357329
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #2 from Dāvis ---
I
https://bugs.kde.org/show_bug.cgi?id=355463
Dāvis changed:
What|Removed |Added
CC||davis...@gmail.com
--- Comment #13 from Dāvis ---
I
65 matches
Mail list logo