https://bugs.kde.org/show_bug.cgi?id=495546
--- Comment #1 from Matthew Woehlke ---
Created attachment 175342
--> https://bugs.kde.org/attachment.cgi?id=175342&action=edit
New crash information added by DrKonqi
DrKonqi auto-attaching complete backtrace.
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=495546
--- Comment #2 from Matthew Woehlke ---
On a different occasion, I got this trace (doing the exact same thing):
#0 0x7fff6e497c4d in
clang::ASTReader::ReadStmtFromStream(clang::serialization::ModuleFile&) ()
at /lib64/libclang.so.18.
https://bugs.kde.org/show_bug.cgi?id=495546
Bug ID: 495546
Summary: KDevelop crashed while editing code
Classification: Applications
Product: kdevelop
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #11 from Matthew Woehlke ---
Thread 732 (Thread 0x7fff33e006c0 (LWP 3923482) "Queue(0x576"):
#0 0x7fff6e54c420 in
L__N_119LValueExprEvaluatorEbJEE15VisitMemberExprEPKNS_10MemberExprE
(or_rangeIT_EE=0x7f
https://bugs.kde.org/show_bug.cgi?id=495259
--- Comment #5 from Matthew Woehlke ---
Created attachment 175316
--> https://bugs.kde.org/attachment.cgi?id=175316&action=edit
example of correct coloring
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495259
--- Comment #4 from Matthew Woehlke ---
Created attachment 175315
--> https://bugs.kde.org/attachment.cgi?id=175315&action=edit
example of incorrect coloring
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #10 from Matthew Woehlke ---
Thread 717 (Thread 0x7fff3cc006c0 (LWP 3923457) "Queue(0x576"):
#0 0x7fff6de9a8d2 in tuple_element<0UL, std::tuple > (InfoEv=0, *,
clang::IdentifierInfo *, clang::IdentifierInfo *, clang
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #9 from Matthew Woehlke ---
Thread 715 (Thread 0x7fff4be006c0 (LWP 3923454) "Queue(0x576"):
#0 anonymous namespace)::ParameterStatus *, const (anonymous
namespace)::ParameterStatus *> (
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #8 from Matthew Woehlke ---
> Maybe a small program ...
Alas, I don't think it's going to be that simple. I tried this:
```
#include
#include
#include
QDateTime getMTime(QString const& path)
{
auto const fi
https://bugs.kde.org/show_bug.cgi?id=495259
--- Comment #3 from Matthew Woehlke ---
Another update... the problem isn't that the intensity is initially being
treated as 100%. The colors are just *wrong*. I now suspect they're being
computed (perhaps with the correct intensity) as if
https://bugs.kde.org/show_bug.cgi?id=495259
--- Comment #2 from Matthew Woehlke ---
It looks like this may only happen with "follow system color scheme". I suspect
(but haven't checked because changing the system color scheme is very
disruptive for me) Breeze Dark would have prob
https://bugs.kde.org/show_bug.cgi?id=495261
--- Comment #6 from Matthew Woehlke ---
> can you get us a `thread apply all bt`
Um... attempts to do so are causing gdb to go out to lunch for extended
periods...
That said, after a few runs I ran into a different failure mode, albeit one
that st
https://bugs.kde.org/show_bug.cgi?id=495261
Matthew Woehlke changed:
What|Removed |Added
Resolution|BACKTRACE |FIXED
--- Comment #2 from Matthew Woehlke
https://bugs.kde.org/show_bug.cgi?id=495261
Bug ID: 495261
Summary: Parsing CMake crashes KDevelop
Classification: Applications
Product: kdevelop
Version: 6.0.240802
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=495259
Bug ID: 495259
Summary: Code colorization intensity is wonky at startup
Classification: Applications
Product: kdevelop
Version: 6.0.240802
Platform: Other
OS: Linux
St
https://bugs.kde.org/show_bug.cgi?id=488378
Bug ID: 488378
Summary: CMake crashes kdevelop
Classification: Applications
Product: kdevelop
Version: 5.14.240500
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=439683
Bug ID: 439683
Summary: Enter/return key in address bar does not work
Product: konqueror
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=430433
Bug ID: 430433
Summary: Unable to launch debugger
Product: kdevelop
Version: 5.6.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Pr
https://bugs.kde.org/show_bug.cgi?id=429859
--- Comment #2 from Matthew Woehlke ---
Yeah... consistently reproducible when saving a .qrc.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429859
--- Comment #1 from Matthew Woehlke ---
Just happened again. *Might* be related to automatic CMake re-run when editing
a .qrc?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429859
Bug ID: 429859
Summary: KDevelop keeps changing active launch
Product: kdevelop
Version: 5.6.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=429065
Bug ID: 429065
Summary: Katepart does not migrate user's .kateschema
Product: kate
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity
https://bugs.kde.org/show_bug.cgi?id=425413
--- Comment #2 from Matthew Woehlke ---
Do you notice any other problems with your system? Is your previously selected
color scheme applied, or are you getting the default scheme?
I've had problems with one machine recently (fortunately, one one
https://bugs.kde.org/show_bug.cgi?id=416776
Matthew Woehlke changed:
What|Removed |Added
Component|kcm_colors |general
Assignee|plasma-b
https://bugs.kde.org/show_bug.cgi?id=396530
--- Comment #4 from Matthew Woehlke ---
Is anyone working on this? Right now the UX is that plasma+nm+openvpn is broken
due to this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399225
--- Comment #2 from Matthew Woehlke ---
Does it work if you import the connection using some other means? See also bug
#396530.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396530
Matthew Woehlke changed:
What|Removed |Added
CC||mwoehlke.fl...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=402713
--- Comment #4 from Matthew Woehlke ---
Does it work if you import the connection using some other means? See also bug
#396530.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=395596
--- Comment #10 from Matthew Woehlke ---
Martin, does it work if you import the connection using some other means? See
also bug #396530.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414996
Bug ID: 414996
Summary: Python HL does not highlight octal numbers
Product: kate
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=408619
Matthew Woehlke changed:
What|Removed |Added
Resolution|DUPLICATE |FIXED
--- Comment #2 from Matthew Woehlke
https://bugs.kde.org/show_bug.cgi?id=408619
Bug ID: 408619
Summary: Typing close parenthesis has no effect
Product: kate
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=403563
Matthew Woehlke changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=403563
--- Comment #9 from Matthew Woehlke ---
Created attachment 118229
--> https://bugs.kde.org/attachment.cgi?id=118229&action=edit
plasma-org.kde.plasma.desktop-appletsrc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403563
--- Comment #7 from Matthew Woehlke ---
Created attachment 118227
--> https://bugs.kde.org/attachment.cgi?id=118227&action=edit
plasmarc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403563
--- Comment #8 from Matthew Woehlke ---
Created attachment 118228
--> https://bugs.kde.org/attachment.cgi?id=118228&action=edit
plasmashellrc
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403563
--- Comment #4 from Matthew Woehlke ---
...and again:
v: 14.9G
r: 13.0G
m: 41%
This was with basic/software.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387272
Matthew Woehlke changed:
What|Removed |Added
CC||mwoehlke.fl...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=404053
--- Comment #5 from Matthew Woehlke ---
> The option is about "inactive windows" not "inactive parts of windows".
Actually, widgets that show persistent selections (usually QAbstractItemView
and derived) *do* use inactive colo
https://bugs.kde.org/show_bug.cgi?id=403563
--- Comment #3 from Matthew Woehlke ---
Okay... after initially making the first change (render loop = basic), it ran
fine for a while, then X crashed. This morning, however:
virt: 15.2G
res: 11.8G
shr: 3.8M
mem: 37.6%
time: 1h23m
Is it
https://bugs.kde.org/show_bug.cgi?id=403061
Matthew Woehlke changed:
What|Removed |Added
CC||mwoehlke.fl...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=403563
--- Comment #2 from Matthew Woehlke ---
Created attachment 117657
--> https://bugs.kde.org/attachment.cgi?id=117657&action=edit
kwin info
Unfortunately, it's going to be hard to answer "does it go away" questions,
since it us
https://bugs.kde.org/show_bug.cgi?id=403563
Bug ID: 403563
Summary: Memory leak in plasma desktop (plasmashell)
Product: plasmashell
Version: 5.14.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=403088
--- Comment #2 from Matthew Woehlke ---
Oh, wow... I hadn't even thought about std::atomic being non-copyable. Checking
for that (since following clazy's advice in such cases will break your code) is
indeed a much better fix; thanks!
-
https://bugs.kde.org/show_bug.cgi?id=403088
Bug ID: 403088
Summary: function-args-by-value should ignore std::atomic
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #131 from Matthew Woehlke ---
> Virtual memory is not a relevant measure of anything useful.
That is neither necessarily true, nor necessarily untrue. While I have seen
instances of processes having huge VIRT that didn't correspond
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #129 from Matthew Woehlke ---
What's the story with this? Because it is apparently still happening with
qt5-5.11.1-9.fc29.x86_64... (I just killed a plasma that had ballooned to
almost 27G VIRT.)
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=335758
--- Comment #2 from Matthew Woehlke ---
It seems to be "working" now by virtue of middle click *never* navigating to
the URL in the middle-click buffer any more...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400452
--- Comment #2 from Matthew Woehlke ---
FYI: possible fix at https://phabricator.kde.org/D16517.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400452
--- Comment #1 from Matthew Woehlke ---
Wow... fiddling with this some more (and also looking at the clazy sources), it
seems that clazy is doing the right thing *if* run on a single source file.
Actually, what may be happening is that the list of
https://bugs.kde.org/show_bug.cgi?id=400452
Bug ID: 400452
Summary: disabling checks doesn't work
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
P
https://bugs.kde.org/show_bug.cgi?id=397062
--- Comment #7 from Matthew Woehlke ---
> Presumably, if you run your app like `theapp >&- 2>&-` it will write to
> journald
Well, I thought that would work, but apparently not. I did confirm, however,
that a simple app for m
https://bugs.kde.org/show_bug.cgi?id=397062
--- Comment #6 from Matthew Woehlke ---
Presumably, if you run your app like `theapp >&- 2>&-` it will write to
journald, and thus you could do so and expect that you can see your message in
`journalctl`. (For that matter, there should be
https://bugs.kde.org/show_bug.cgi?id=397062
--- Comment #4 from Matthew Woehlke ---
Omar, is your test app Qt4 or Qt5? If Qt5, was Qt built with journald support?
Qt4 works, Qt5 depends on if it was built with journald support (as e.g.
Fedora's package is).
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=397062
Bug ID: 397062
Summary: missing Qt5 QDebug output
Product: kdevelop
Version: 5.2.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Prior
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #46 from Matthew Woehlke ---
I am also still seeing the issue with Qt 5.9.4, plasma 5.11.5 (full list of my
current packages posted to Bug 388580 so as not to clutter this report).
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=388580
--- Comment #3 from Matthew Woehlke ---
Still occurs with:
bash-4.4.19-1.fc27.x86_64
coreutils-8.27-20.fc27.x86_64
dbus-x11-1.12.0-1.fc27.x86_64
glibc-2.26-24.fc27.x86_64
iso-codes-3.75-2.fc27.noarch
kactivitymanagerd-5.11.5-1.fc27.x86_64
kde-settings
https://bugs.kde.org/show_bug.cgi?id=368838
--- Comment #26 from Matthew Woehlke ---
I'm not sure if Bug 388580 is a duplicate or not; I have only started noticing
problems recently, and I'm using the radeon driver.
(Random data point: immediately after start-up, plasmashell was 4G/
https://bugs.kde.org/show_bug.cgi?id=388580
--- Comment #1 from Matthew Woehlke ---
I am using:
bash-4.4.12-12.fc27.x86_64
coreutils-8.27-17.fc27.x86_64
dbus-x11-1.12.0-1.fc27.x86_64
glibc-2.26-21.fc27.x86_64
iso-codes-3.75-2.fc27.noarch
kactivitymanagerd-5.11.4-1.fc27.x86_64
kde-settings-plasma
https://bugs.kde.org/show_bug.cgi?id=388580
Bug ID: 388580
Summary: Memory leak in plasmashell
Product: plasmashell
Version: master
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=387534
--- Comment #1 from Matthew Woehlke ---
I'm not sure that's even possible. At best, you might want to turn off 'apply
colors to non-Qt applications'.
At any rate, you should definitely (also) file bugs against applications that
d
https://bugs.kde.org/show_bug.cgi?id=386394
Bug ID: 386394
Summary: Crash in auto-indenter
Product: frameworks-ktexteditor
Version: 5.38.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: cras
https://bugs.kde.org/show_bug.cgi?id=384933
Matthew Woehlke changed:
What|Removed |Added
Ever confirmed|0 |1
Component|kcm_colors
https://bugs.kde.org/show_bug.cgi?id=195046
--- Comment #7 from Matthew Woehlke ---
Thanks. Addendum: I think I've seen the second behavior with krdc also, which
would tend to implicate kwin...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=195046
--- Comment #5 from Matthew Woehlke ---
Just checked with 16.12.3; still present.
Also, switching to fullscreen changes which screen gwenview is on... (gwenview
bug? or kwin bug?)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=382107
--- Comment #2 from Matthew Woehlke ---
Cool; thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=382074
--- Comment #3 from Matthew Woehlke ---
(Ugh, use a build tool that mucks with my FS in unknown ways? I'll stick to
'git clone', thanks!)
Wow, that was a quick fix! And a much better fix than my (being unfamiliar with
the code in
https://bugs.kde.org/show_bug.cgi?id=382107
Bug ID: 382107
Summary: kdevplatform FTBFS due to missing __cpu_model
Product: kdevplatform
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=382074
Bug ID: 382074
Summary: Infinite symlink loop -> infinite parsing loop
Product: kdevelop
Version: 5.1.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Sever
https://bugs.kde.org/show_bug.cgi?id=380366
Bug ID: 380366
Summary: Can't change password of Google account
Product: KAccounts
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Sever
https://bugs.kde.org/show_bug.cgi?id=366796
--- Comment #3 from Matthew Woehlke ---
(In reply to Ian Wadham from comment #1)
> (In reply to Matthew Woehlke from comment #0)
> > Multi-select behavior should work like it does in every other application.
>
> Is there a standard
https://bugs.kde.org/show_bug.cgi?id=366796
Bug ID: 366796
Summary: Ctrl-click should never, ever deselect all pieces
Product: palapeli
Version: 2.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Seve
72 matches
Mail list logo
