https://bugs.kde.org/show_bug.cgi?id=482481
--- Comment #7 from Matt Whitlock ---
Created attachment 171664
--> https://bugs.kde.org/attachment.cgi?id=171664&action=edit
an alternative fix that doesn't override fontconfig
To fix the original issue without overriding the
https://bugs.kde.org/show_bug.cgi?id=482481
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=479891
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=484639
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=464868
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=379294
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=383379
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=350688
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=384695
--- Comment #9 from Matt Whitlock ---
(In reply to sevens from comment #7)
> Current behavior of `Shift+Wheel` (scroll an entire screen's worth of
> content[…]) is also useful IMO but could maybe use a different shortcut?
Personally, I wo
https://bugs.kde.org/show_bug.cgi?id=384695
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=380454
--- Comment #2 from Matt Whitlock ---
I don't use Akonadi anymore. I switched to a mail client designed for IMAP
(Trojitá).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459366
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=423920
Matt Whitlock changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=362089
Matt Whitlock changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #33 from Matt Whitlock ---
I'm the original reporter on this bug. This is no longer affecting me. I
haven't had to manually open/start KDE Connect on my phone within my
recollection. It Just Works™. And I'm no longer using th
https://bugs.kde.org/show_bug.cgi?id=109374
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=446531
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=450118
Matt Whitlock changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=450118
--- Comment #2 from Matt Whitlock ---
Git bisection reveals 3b4d5583713e4dbba046cc79f02c6c8c356ed43b as the culprit.
https://invent.kde.org/plasma/kwin/-/commit/3b4d5583713e4dbba046cc79f02c6c8c356ed43b
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=450118
--- Comment #1 from Matt Whitlock ---
Created attachment 146653
--> https://bugs.kde.org/attachment.cgi?id=146653&action=edit
KCalc on KWin 5.24.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450118
Bug ID: 450118
Summary: Regression: KWin 5.24.0 renders window borders with
gradient in wrong direction
Product: kwin
Version: 5.24.0
Platform: Gentoo Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=441551
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=365299
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #6 from Matt Whitlock ---
(In reply to Milian Wolff from comment #5)
> can you please try the latest master and see if you are still seeing this
> breakage?
Yes, that fixed it. I no longer get nonsense traces in Heaptrack, and I
ac
https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #2 from Matt Whitlock ---
(In reply to Milian Wolff from comment #1)
> Since you are using gentoo: Are the debug symbols you are using for
> plasmashell and qt and so forth matching the build that you profiled?
Yes. The debug symbo
https://bugs.kde.org/show_bug.cgi?id=439897
Bug ID: 439897
Summary: Heaptrack produces impossible/incorrect stack traces
Product: Heaptrack
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=439307
Bug ID: 439307
Summary: heaptrack launch script help text shows wrong option
name for --output-file
Product: Heaptrack
Version: unspecified
Platform: Gentoo Packages
https://bugs.kde.org/show_bug.cgi?id=423920
Bug ID: 423920
Summary: Erroneous lambda expression crashes KDevelop in C++17
mode with clang 10.0.1
Product: kdevelop
Version: 5.5.2
Platform: Gentoo Packages
OS:
https://bugs.kde.org/show_bug.cgi?id=421704
--- Comment #6 from Matt Whitlock ---
(In reply to Aaron Puchert from comment #5)
> I hope you don't mind.
Not at all! I'm glad you were able to come up with an incantation that makes
Clang crash when run from the command line. Thanks fo
https://bugs.kde.org/show_bug.cgi?id=421704
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=422716
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=171295
--- Comment #26 from Matt Whitlock ---
(In reply to Nate Graham from comment #25)
> I'd really like this particularly for the case of many-button mice. I'd like
> to be able to assign the side keys to "next/previous" tab.
I
https://bugs.kde.org/show_bug.cgi?id=363932
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=416001
--- Comment #9 from Matt Whitlock ---
I haven't upgraded Qt yet, but my expectation is that this bug is no more.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416001
--- Comment #7 from Matt Whitlock ---
Adding the following to a script in ~/.config/plasma-workspace/env/ and
restarting my KDE session makes my Konsole behave correctly again:
# work around https://bugreports.qt.io/browse/QTBUG-80967
export
https://bugs.kde.org/show_bug.cgi?id=416001
--- Comment #6 from Matt Whitlock ---
These reports appear to regard the exact same issue:
https://phabricator.kde.org/D26185
https://bugreports.qt.io/browse/QTBUG-80967
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416001
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=415537
--- Comment #2 from Matt Whitlock ---
Analogous concerns apply for switch-statement with initializer.
/* BEGIN example2.cpp */
#include
#include
#include
unsigned parse_uint_clamp(const char *begin, const char *end) {
unsigned v;
switch
https://bugs.kde.org/show_bug.cgi?id=415537
Bug ID: 415537
Summary: Syntax highlighter fails on C++17 if-statement with
initializer
Product: kdevelop
Version: 5.4.5
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=255070
--- Comment #8 from Matt Whitlock ---
I stopped using Konqueror a long time ago because it wasn't keeping up with
Chromium. I no longer keep it installed, so I have no stake in this bug report
anymore. Feel free to close, as there are no
https://bugs.kde.org/show_bug.cgi?id=304148
--- Comment #7 from Matt Whitlock ---
(In reply to Andrew Crouthamel from comment #6)
> re-test if the bug is valid
I have no means of reproducing this crash on demand, and I have not experienced
it again.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=205854
--- Comment #5 from Matt Whitlock ---
Another data point. I had 3 files in my Trash with ctimes older than 90 days
ago. Immediately after I checked this, I moved one file to the Trash (via the
context menu in a File Open dialog in a KDE application
https://bugs.kde.org/show_bug.cgi?id=205854
Matt Whitlock changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=372552
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #8 from
https://bugs.kde.org/show_bug.cgi?id=394436
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #120 from Matt Whitlock ---
(In reply to Ovidiu Chi from comment #117)
> > I am running a slideshow of 2560x1600 images every 2 seconds with
> > QSG_RENDER_LOOP=basic
>
> @Matt, You'd have to start the slideshow the
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #116 from Matt Whitlock ---
(In reply to Ovidiu Chi from comment #114)
> Matt, I'm not knowledgeable enough to say which memory leak this is, or the
> precise nature of it, but scrolling the list of widgets doesn't do much
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #113 from Matt Whitlock ---
(In reply to David Edmundson from comment #112)
> @Matt
> How can you tell what is leaking from looking at comment #0?
There have been at least two distinct memory leaks discussed in this thread.
The or
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #111 from Matt Whitlock ---
(In reply to Ovidiu Chi from comment #110)
Plasmashell *does* still have a memory leak, but it's not the one from this
bug. Actually, it *is* the one from the original report in Comment #0, but this
t
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #76 from Matt Whitlock ---
(In reply to Nate Graham from comment #74)
> So should Qt use the threaded render loop by default, then? Or
> should we? Or something else?
Presumably the VRAM memory leak in the basic render loop should be
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #73 from Matt Whitlock ---
(In reply to Nate Graham from comment #72)
> So the consensus is that QSG_RENDER_LOOP=threaded doesn't fix the issue?
There are two issues. QSG_RENDER_LOOP=threaded *does* avoid the VRAM memory
leak but *
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #63 from Matt Whitlock ---
(In reply to Alexander Schlarb from comment #62)
> the RSS memory leak with the nVidia binary
> drivers.
Um, I'm using the open-source AMDGPU driver, and I can easily drive up
plasmashell's VmR
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #60 from Matt Whitlock ---
(In reply to Antonio Orefice from comment #59)
> I just made a video showing how plasma can reach about 1GB of ram usage from
> 300MB in a bunch of seconds.
I too can reproduce a rather serious memory lea
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #57 from Matt Whitlock ---
(In reply to Marco Martin from comment #50)
> can this be tried again with a more recent Qt? either the latest 5.9 or 5.10
> making sure both of these patches are in:
>
> https://codereview.qt-pro
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #55 from Matt Whitlock ---
(In reply to Alexander Schlarb from comment #54)
> `QCG_RENDER_LOOP=basic`.
It's supposed to be QSG_RENDER_LOOP. ("SG" for "scene graph.")
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=387341
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #16 from
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #43 from Matt Whitlock ---
(In reply to Nate Graham from comment #42)
> Is there anyone using Qt 5.9.2 or beyond who can reproduce this issue?
As I mentioned in comment #36 and comment #38, I am running Qt 5.9.4, and I can
still eas
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #40 from Matt Whitlock ---
Sorry your bug report has been "derailed," Antonio, though it's very possible
that the symptoms we're each observing may have the same root cause.
I just installed radeontop and watched my car
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #38 from Matt Whitlock ---
(In reply to David Edmundson from comment #37)
> Please see my requests on #34
(In reply to David Edmundson from comment #34)
> If you're running < Qt5.10 or < 5.9.3 upgrade now so you ha
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #36 from Matt Whitlock ---
Created attachment 110735
--> https://bugs.kde.org/attachment.cgi?id=110735&action=edit
time-series chart demonstrating plasmashell memory leak
Do we need to open a new bug report for the slideshow wa
https://bugs.kde.org/show_bug.cgi?id=368838
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #31 from
https://bugs.kde.org/show_bug.cgi?id=370716
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=384404
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=384476
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=384476
--- Comment #1 from Matt Whitlock ---
Created attachment 107805
--> https://bugs.kde.org/attachment.cgi?id=107805&action=edit
New crash information added by DrKonqi
ktorrent (5.1.0) using Qt 5.7.1
- What I was doing when the application cras
https://bugs.kde.org/show_bug.cgi?id=380454
Bug ID: 380454
Summary: Akonadi IMAP resource neglects to reconnect failed
control socket while IDLE connection remains live
Product: Akonadi
Version: 5.5.1
Platform: Gentoo Packa
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #19 from Matt Whitlock ---
(In reply to Theresa from comment #18)
> Alas my phone (Oneplus One) only has Android 6.
FYI, LineageOS 14.1 (Android 7.1) is available for the OnePlus One. LineageOS
is the successor to CyanogenOS (which, if
https://bugs.kde.org/show_bug.cgi?id=378189
--- Comment #14 from Matt Whitlock ---
(In reply to Matt Whitlock from comment #13)
> I have the Akonadi Console open with the Job Tracker enabled now, to try to
> see if any jobs hang in Akonadi.
Nope. KMail has gone out to lunch again, but A
https://bugs.kde.org/show_bug.cgi?id=378189
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #17 from Matt Whitlock ---
(In reply to Theresa from comment #16)
> @Albert/Matt: any idea what's causing my connection drops?!
I never did figure it out. Upgrading to Android 7.1 made the problem disappear
for me.
--
You are r
https://bugs.kde.org/show_bug.cgi?id=338012
--- Comment #9 from Matt Whitlock ---
(In reply to David Rosenstrauch from comment #8)
> IIRC, oxygen-gtk is no longer being supported. (Since the upgrade to gtk3.)
GTK3 support in SWT (the GUI toolkit that Eclipse uses) is half-baked (lots
https://bugs.kde.org/show_bug.cgi?id=338012
--- Comment #7 from Matt Whitlock ---
Created attachment 104832
--> https://bugs.kde.org/attachment.cgi?id=104832&action=edit
patch that fixes the bug
I couldn't find a way to reference count the GtkTreeViewColumn without causing
crashes
https://bugs.kde.org/show_bug.cgi?id=338012
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #10 from Matt Whitlock ---
KDE Connect has been working flawlessly for me for a while now. I am not sure
whether something changed in KDE Connect or if it's due to my upgrading to
LineageOS 14.1 (Android 7.1.1).
My current versions:
https://bugs.kde.org/show_bug.cgi?id=208625
--- Comment #38 from Matt Whitlock ---
(In reply to David Faure from comment #34)
> The only course of action I can suggest is that someone who can reproduce
> the bug applies the patch below to their kio build and reports the results.
>
https://bugs.kde.org/show_bug.cgi?id=366768
--- Comment #3 from Matt Whitlock ---
I have produced a patch, attached to Bug 308444, that fixes the problem of time
zone information being discarded when processing these template variables.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=341909
--- Comment #14 from Matt Whitlock ---
I have produced a patch, attached to Bug 308444, that fixes the problem of time
zone information being discarded when processing these template variables in a
reply.
Note: I did not attempt to address the problem
https://bugs.kde.org/show_bug.cgi?id=355195
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=308444
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=341909
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=366768
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=372712
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=331891
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #8 from Matt Whitlock ---
(In reply to Albert Vaca from comment #7)
> Is there a way I can reproduce it?
I'm not sure. KDE Connect is broken for me more often than it works, and I
still don't know the exact conditions tha
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #6 from Matt Whitlock ---
There is a data-race bug in LanLink.java:
https://github.com/albertvaka/kdeconnect-android/blob/master/src/org/kde/kdeconnect/Backends/LanBackend/LanLink.java#L116
Because LanLink.socket is not declared volatile
https://bugs.kde.org/show_bug.cgi?id=368438
Matt Whitlock changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=368580
Bug ID: 368580
Summary: Auto Brackets forgets about multiple levels of
brackets when overtyping closing bracket
Product: frameworks-ktexteditor
Version: unspecified
Platform: Gent
https://bugs.kde.org/show_bug.cgi?id=368438
Matt Whitlock changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #3 from Matt Whitlock ---
Created attachment 101004
--> https://bugs.kde.org/attachment.cgi?id=101004&action=edit
KDE Connect memory usage statistics
Here's another screen shot. Android reports that the KDE Connect app is &qu
https://bugs.kde.org/show_bug.cgi?id=368438
Matt Whitlock changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=368438
--- Comment #2 from Matt Whitlock ---
Created attachment 101003
--> https://bugs.kde.org/attachment.cgi?id=101003&action=edit
Running app details
Thanks for the reply. You've been too quick to dismiss this, though.
In fact, the KDE Co
https://bugs.kde.org/show_bug.cgi?id=368438
Bug ID: 368438
Summary: KDE Connect does not communicate while running in
background on phone
Product: kdeconnect
Version: 1.0
Platform: Gentoo Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=96431
--- Comment #52 from Matt Whitlock ---
(In reply to Aloysius from comment #51)
> I'm afraid the only way is to use xbindkeys or switch to wayland.
Preposterous. If xbindkeys can do it, then KDE's global hotkeys daemon can do
the same t
https://bugs.kde.org/show_bug.cgi?id=360567
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--- Comment #2 from
https://bugs.kde.org/show_bug.cgi?id=348194
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=348123
Matt Whitlock changed:
What|Removed |Added
CC||k...@mattwhitlock.name
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=362089
--- Comment #5 from Matt Whitlock ---
(In reply to Matt Whitlock from comment #4)
> (In reply to Hugo Pereira Da Costa from comment #3)
> > - and what is the Qt5 version you are using ?
>
> 5.5.1
Same problem exists when running on Qt
https://bugs.kde.org/show_bug.cgi?id=362089
--- Comment #4 from Matt Whitlock ---
Created attachment 98534
--> https://bugs.kde.org/attachment.cgi?id=98534&action=edit
KCalc (Qt5) running with "-style breeze"
(In reply to Hugo Pereira Da Costa from comment #3)
> You are r
https://bugs.kde.org/show_bug.cgi?id=362089
--- Comment #2 from Matt Whitlock ---
Created attachment 98516
--> https://bugs.kde.org/attachment.cgi?id=98516&action=edit
Ugly hard black border around menu in Kate (Qt5)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=362089
--- Comment #1 from Matt Whitlock ---
Created attachment 98515
--> https://bugs.kde.org/attachment.cgi?id=98515&action=edit
Comparison of menus in KMail (Qt4) and KCalc (Qt5)
--
You are receiving this mail because:
You are watching all bug changes.
1 - 100 of 102 matches
Mail list logo
