https://bugs.kde.org/show_bug.cgi?id=375890
Bug ID: 375890
Summary: GUI freezes when accessing GPGME
Product: kmail2
Version: Git (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #14 from Milian Wolff <m...@milianw.de> ---
this should be fixed by making sure the unknown declaration problem its check
in another thread - probably this will require some more extensive refactorings
but would certainly be
https://bugs.kde.org/show_bug.cgi?id=370515
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=375968
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Product|kdevelop|kdevpl
https://bugs.kde.org/show_bug.cgi?id=375968
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Priority|NOR |VHI
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=375968
--- Comment #4 from Milian Wolff <m...@milianw.de> ---
Yep, looking at the indices this becomes clear:
thread 11:
1474 -> 1473
thread 9:
1488 -> 1473
thread 8:
1585 -> 1473 -> 1474
thread 11 and thread 8 trigger the deadlock
--
https://bugs.kde.org/show_bug.cgi?id=375968
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
I think this only can arise when we have a cycle in the import structure, i.e.
X -> Y -> X
and probably that is only triggered by python which is why I haven't seen that
ever. The
https://bugs.kde.org/show_bug.cgi?id=375432
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=376419
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=376595
--- Comment #14 from Milian Wolff <m...@milianw.de> ---
Please also try valgrind, that is usually much more helpful in such situations:
valgrind --smc-check=all-non-file --track-origins=yes kdevelop
--
You are receiving this mail becaus
https://bugs.kde.org/show_bug.cgi?id=376713
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
can you please report a valgrind trace?
valgrind --smc-check=all-non-file --track-origins=yes kdevelop
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376432
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=376521
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=376461
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
Git commit fcba3835397bf1c830e56a0c7487c5c1ac329b40 by Milian Wolff.
Committed on 20/02/2017 at 23:01.
Pushed by mwolff into branch 'master'.
Improve code completion of paths with
https://bugs.kde.org/show_bug.cgi?id=376600
Bug ID: 376600
Summary: crash on exit when same document is opened in multiple
split views
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=376741
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=376247
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=245902
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |FIXED
Latest
https://bugs.kde.org/show_bug.cgi?id=372165
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=372842
--- Comment #2 from Milian Wolff <m...@milianw.de> ---
would indeed be nice, but I think I looked into this a couple of years ago
quickly. the problem is that everything is done async there, we load
potentially multiple projects at s
https://bugs.kde.org/show_bug.cgi?id=374992
Bug ID: 374992
Summary: provide a way to reorder the list of favorite folders
Product: kmail2
Version: Git (master)
Platform: Other
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=378196
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Version|5.1.0 |16.08
P
https://bugs.kde.org/show_bug.cgi?id=226117
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=377631
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=371474
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Component|general |part
P
https://bugs.kde.org/show_bug.cgi?id=377110
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Severity|critical|crash
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=377110
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=377672
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
there's no way we can make it right for all platforms, I'm afraid. When you
install a custom Qt into /opt and put it into your PATH, it's qmake will be the
right one. So I think keeping the or
https://bugs.kde.org/show_bug.cgi?id=377672
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
Doing what cmake does sounds fine to me.
And to your claim that "the distro Qt is always the right one" - that is
completely wrong. In my work for KDAB I see tons of Linux b
https://bugs.kde.org/show_bug.cgi?id=377742
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=378494
--- Comment #9 from Milian Wolff <m...@milianw.de> ---
heaptrack already depends on pthread (for the timer thread). I also asked a
colleague and he confirmed this is safe to do. I'll push it - thanks for the
report and helpful test case!
-
https://bugs.kde.org/show_bug.cgi?id=378494
--- Comment #7 from Milian Wolff <m...@milianw.de> ---
Reading up a bit, I think this patch should actually quite safe to do. Can you
confirm, considering you seem to have more knowledge around this idiom? If so,
then I'd push it to master in th
https://bugs.kde.org/show_bug.cgi?id=378494
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=378494
--- Comment #6 from Milian Wolff <m...@milianw.de> ---
Indeed, that work-arounds this issue:
diff --git a/src/track/libheaptrack.cpp b/src/track/libheaptrack.cpp
index b21b00b..6df2101 100644
--- a/src/track/libheaptrack.cpp
+++ b/src
https://bugs.kde.org/show_bug.cgi?id=378494
--- Comment #2 from Milian Wolff <m...@milianw.de> ---
What's odd is that it does not happen when I disable the timer thread. Stracing
the signals syscalls also doesn't reveal anything obvious. I still have no clue
what's going on here.
-
https://bugs.kde.org/show_bug.cgi?id=378494
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
ah, I can reproduce the issue with your test code even without heaptrack, when
I slightly modify it:
at the very start of main, add:
auto t = std::thread([]() { while(true)
{std::this_
https://bugs.kde.org/show_bug.cgi?id=378494
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=378428
--- Comment #7 from Milian Wolff <m...@milianw.de> ---
we also store the non-lowercased version in special PHP classes, we just need a
way to use those in place of the non-lowercased versions by introducing a new
virtual in Declaration tha
https://bugs.kde.org/show_bug.cgi?id=378419
--- Comment #8 from Milian Wolff <m...@milianw.de> ---
the lookup feature could (and should) use the indexed string of the normalized
path to find the corresponding project item, this should fix this issue then, I
guess - patches welcome!
-
https://bugs.kde.org/show_bug.cgi?id=378490
--- Comment #5 from Milian Wolff <m...@milianw.de> ---
afaik ktexteditor has an idea of virtual cursors that map to the "expected"
column. Not sure how we want to show it though, some people want to actual
cursor position, some
https://bugs.kde.org/show_bug.cgi?id=378922
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
we'd need to know whether unwinding with libunwind works at all in a wine
application (I wouldn't be surprised if it fails). if that fails, we have no
way to implement this feature.
-
https://bugs.kde.org/show_bug.cgi?id=378765
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=377143
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confi
https://bugs.kde.org/show_bug.cgi?id=377143
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=381829
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |DOWNSTREAM
https://bugs.kde.org/show_bug.cgi?id=378089
--- Comment #4 from Milian Wolff <m...@milianw.de> ---
or even "Implement Pure Virtual" and "Override Virtual"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=378089
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
Imo it should be "Override Pure Virtual" and "Override Virtual"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379220
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=379221
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Latest Commit||https://commits.kde.o
https://bugs.kde.org/show_bug.cgi?id=379220
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confi
https://bugs.kde.org/show_bug.cgi?id=379222
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=379082
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=379551
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=379219
--- Comment #7 from Milian Wolff <m...@milianw.de> ---
you could try to strace kdevelop to see the git commands it executes and files
it creates/locks, something like the following could do the trick:
strace -e open,execve,flock -f -s 1000 kdeve
https://bugs.kde.org/show_bug.cgi?id=369573
--- Comment #15 from Milian Wolff <m...@milianw.de> ---
Thanks, can you install debug information for kdevelop and rerun heaptrack
please? Many interesting locations could not be resolved in your trace. We now
only know that /something/ in kde
https://bugs.kde.org/show_bug.cgi?id=369573
--- Comment #17 from Milian Wolff <m...@milianw.de> ---
hm this didn't change anything - is there maybe a debug package for kdevqmljs?
If so, can you install that one please? Otherwise, could you give us clear
steps to reproduce the
https://bugs.kde.org/show_bug.cgi?id=379551
--- Comment #4 from Milian Wolff <m...@milianw.de> ---
The way AppImage works makes it impossible to track kdevelop with heaptrack
currently. So you'll either have to runtime attach heaptrack later on
(heaptrack --pid $(pidof kdevelop), as
https://bugs.kde.org/show_bug.cgi?id=379854
--- Comment #10 from Milian Wolff <m...@milianw.de> ---
is it thread 1 that crashed? gdb should tell you that on the segfault. I
wonder, b/c the function you point to does not contain a dynamic_cast, so i
really wonder what is going on there...
https://bugs.kde.org/show_bug.cgi?id=379219
--- Comment #18 from Milian Wolff <m...@milianw.de> ---
@mrnuke: how long does `git status --porcelain -- path/to/linux` take on your
machine? On mine it finishes within ~200ms, according to perf stat:
Performance counter stats for 'git
https://bugs.kde.org/show_bug.cgi?id=369573
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Version
https://bugs.kde.org/show_bug.cgi?id=369573
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|REOPENED|CONFIRMED
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=368555
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=380318
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |WAITINGF
https://bugs.kde.org/show_bug.cgi?id=379854
--- Comment #4 from Milian Wolff <m...@milianw.de> ---
try attaching to the kdevelop process with gdb after launching it through
appimage, does this work?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=379854
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |BACKTRACE
https://bugs.kde.org/show_bug.cgi?id=380860
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=379854
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|NEEDSINFO |UNCONFIRMED
Reso
https://bugs.kde.org/show_bug.cgi?id=379854
--- Comment #12 from Milian Wolff <m...@milianw.de> ---
Hm ok DocumentController::activeDocument actually contains a dynamic_cast, but
I wonder how that can crash here. I think we'll need to valgrind this - which
is probably not po
https://bugs.kde.org/show_bug.cgi?id=380985
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
interesting, that's pretty odd! can you share a setup with me that I can use to
reproduce this? Did your setup maybe use split debug symbols in a separate
file? I'm having a hard time figuri
https://bugs.kde.org/show_bug.cgi?id=341568
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Version Fixed In||5.0.0
https://bugs.kde.org/show_bug.cgi?id=379360
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Latest
https://bugs.kde.org/show_bug.cgi?id=379854
--- Comment #7 from Milian Wolff <m...@milianw.de> ---
try the nightly build:
http://kfunk.ddns.net:8080/job/kdevelop-appimage-centos/lastSuccessfulBuild/artifact/KDevelop-git-x86_64.AppImage
launch it normally, then attach GDB, then rep
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #5 from Milian Wolff <m...@milianw.de> ---
a) if my memory serves me right (I've written this a long time ago), I think
the WatchFiles there may have been required to get notified about file deletion
events. Anyhow, I agree that this
https://bugs.kde.org/show_bug.cgi?id=384775
--- Comment #5 from Milian Wolff <m...@milianw.de> ---
Can you try again? I think I may just have fixed this issue in the master
branch.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384775
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #1 from Milian Wolff <m...@milianw.de> ---
Thanks for creating this report so we can track this properly.
Some notes:
a)
- kdev should only watch directories, CMakeLists.txt files and open files for
changes
- the CMakeLists.tx
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #7 from Milian Wolff <m...@milianw.de> ---
I didn't mean I write KDirWatch, only the usage of that API in KDevelop is
mostly my code nowadays. Still, I think I wrote that 5-7 years ago or so, while
it was still only part of the g
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #11 from Milian Wolff <m...@milianw.de> ---
If you want to have it reviewed, put it up on phabricator - attaching it here
isn't helping anyone and just wastes our time.
Regarding QSet (without reading the code): Why no
https://bugs.kde.org/show_bug.cgi?id=385012
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=384880
--- Comment #14 from Milian Wolff <m...@milianw.de> ---
Yes.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=383889
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confi
https://bugs.kde.org/show_bug.cgi?id=387264
--- Comment #6 from Milian Wolff <m...@milianw.de> ---
Well, thanks to you to point me to the important updates in libbacktrace :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387264
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=387264
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=387259
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=387232
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=387232
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|FIXED |WAITINGFORINFO
-
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #10 from Milian Wolff <m...@milianw.de> ---
troll answer: yes, remove the project watcher as I told you to
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387232
--- Comment #8 from Milian Wolff <m...@milianw.de> ---
exactly, don't report bugs for crashes in your WIP patches
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387238
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=387264
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
oh, excellent - thanks for the pointer! I'll try to look at that soon and
update the copy of libbacktrace. Alternatively, I still contemplate porting the
code to elfutils/libdw(fl), which su
https://bugs.kde.org/show_bug.cgi?id=387264
--- Comment #4 from Milian Wolff <m...@milianw.de> ---
Can you please try
https://transfer.sh/152WHJ/heaptrack-git.3605a93-x86_64.AppImage or the
wip/debuglink branch and see if it works for you? This is a build with the
latest libbacktrace (an
https://bugs.kde.org/show_bug.cgi?id=373017
--- Comment #7 from Milian Wolff <m...@milianw.de> ---
@Sven, your idea can still fail. When we schedule, the clang parse jobs may not
yet use a lot of memory. But later when they hit $insane-template-magic-code
they suddenly sky-rocket memor
https://bugs.kde.org/show_bug.cgi?id=387994
--- Comment #5 from Milian Wolff <m...@milianw.de> ---
I mean: how did you get the correct highlighting? Do you have a patch
available?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387994
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=386421
--- Comment #10 from Milian Wolff <m...@milianw.de> ---
Uhm sorry to interrupt, but the gif shows an issue that has nothing do with
clang. It's our custom include path code completion. seems like that is not
querying for (all) the include paths an
https://bugs.kde.org/show_bug.cgi?id=387005
--- Comment #2 from Milian Wolff <m...@milianw.de> ---
Can you give more information? What compilers do you have installed? Which ones
is KDevelop using (cf. the project settings combo box that Sven references).
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=386969
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Resolution|--- |FIXED
Latest
https://bugs.kde.org/show_bug.cgi?id=387095
Milian Wolff <m...@milianw.de> changed:
What|Removed |Added
Summary|Since KDevelop 5.2.x|CMake subproject
https://bugs.kde.org/show_bug.cgi?id=387095
--- Comment #9 from Milian Wolff <m...@milianw.de> ---
Ah, now I see - thanks for the clarifications. I still find it very suspect
that CMake lists the targets multiple times. Anyhow, this can probably be
workarounded somehow in KDevelop's cmake
1 - 100 of 828 matches
Mail list logo
