https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #15 from RJVB <rjvber...@gmail.com> ---
I agree that a fix would involve moving this algorithm to its own thread though
if that's all that is done we will probably see the same kind of behaviour I
had in an early version of my work
https://bugs.kde.org/show_bug.cgi?id=335111
--- Comment #95 from RJVB <rjvber...@gmail.com> ---
I haven't been seeing this problem for a long time, I though it was solved?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #136 from RJVB <rjvber...@gmail.com> ---
(In reply to Sebastian Kügler from comment #135)
> Quite simply, we're not looking for a solution, the right solution has been
> proposed already. Someone needs to sit down and do th
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #16 from RJVB <rjvber...@gmail.com> ---
(In reply to Milian Wolff from comment #14)
> this should be fixed by making sure the unknown declaration problem its
> check in another thread
How about using handling the he
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #17 from RJVB <rjvber...@gmail.com> ---
(Doh, I meant QThread of course, not QProcess)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #122 from RJVB <rjvber...@gmail.com> ---
Better get a grip on actual statistics before you make statements like that
(and even then re-read it twice before posting).
The only critique one can emit towards the "KDE folks&
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #126 from RJVB <rjvber...@gmail.com> ---
Well, there *is* a reason why I'm still using Kubuntu 14.04 with its "Plasma 4"
desktop and run what's basically a home-brewn Neon5 parallel KF5 install.
No "official" rea
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #129 from RJVB <rjvber...@gmail.com> ---
PS: probably not made any easier given that (as far as I can tell) QLocale
works as one would expect on Mac (i.e. respecting system settings giving me my
desired MMDD dates etc.) and pres
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #128 from RJVB <rjvber...@gmail.com> ---
I was't sure if you were following this issue.
How feasible would it be to derive QLocale to something like a KLocale class
that provides the functionality missing from QLocale?
-
https://bugs.kde.org/show_bug.cgi?id=373950
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
URL||https://phabricator.k
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #132 from RJVB <rjvber...@gmail.com> ---
(In reply to Sebastian Kügler from comment #130)
> I've explained that in comment#9 already.
That comment explains that *using* KLocale would not be an option. I can
understand that, to t
https://bugs.kde.org/show_bug.cgi?id=373950
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comm
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #18 from RJVB <rjvber...@gmail.com> ---
https://phabricator.kde.org/D4411
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #12 from RJVB <rjvber...@gmail.com> ---
I've been looking for a somewhat less brute work-around, because I have had a
bit too many cases where I couldn't even select a variable or function by
double clicking without being taken
https://bugs.kde.org/show_bug.cgi?id=375745
Bug ID: 375745
Summary: cmake subprojects in a single session
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=372040
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Attachment #103447|0 |1
is ob
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #13 from RJVB <rjvber...@gmail.com> ---
Created attachment 103723
--> https://bugs.kde.org/attachment.cgi?id=103723=edit
improved workaround
This is a workaround patch implementing some of the ideas outlined in my
previou
https://bugs.kde.org/show_bug.cgi?id=375548
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 103634
--> https://bugs.kde.org/attachment.cgi?id=103634=edit
side-ways related: possible optimisation for
KTextEditor::ViewPrivate::contextMenu()
This is a change I test
https://bugs.kde.org/show_bug.cgi?id=375548
Bug ID: 375548
Summary: context menu not opened every other click (Mac)
Product: frameworks-ktexteditor
Version: 5.29.0
Platform: Compiled Sources
OS: OS X
Status:
https://bugs.kde.org/show_bug.cgi?id=339006
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
FWIW, the possibly-related problem with SemiBold is due to a font weight
handling issue in Qt5 itself.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #20 from RJVB <rjvber...@gmail.com> ---
What kind of news are you hoping for?
I'm currently using the patch below with 5.29.0 on Mac and that works well
enough. I should maybe try the patch on Linux too (not sure why I never did)
bec
https://bugs.kde.org/show_bug.cgi?id=376835
--- Comment #6 from RJVB <rjvber...@gmail.com> ---
That would be a good way to initialise the combobox I suggested ;)
Seriously, isn't that something you could re-utilise from KCrash?
In the meantime I'll try to remember patching that mapping mec
https://bugs.kde.org/show_bug.cgi?id=376835
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
That's interesting, I didn't notice that DrKonqi failed to assign this report
to the proper project?!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=376835
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 104181
--> https://bugs.kde.org/attachment.cgi?id=104181=edit
New crash information added by DrKonqi
kdevelop5 (5.1.40) using Qt 5.8.0
- What I was doing when the ap
https://bugs.kde.org/show_bug.cgi?id=376835
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
CC||rjvber...@gmail.com
-
: 5.8.0
Frameworks Version: 5.29.0
Operating System: Linux 4.9.8-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed:
1 Open a KDevelop session
2 Open a patch review
3 "Export Diff" / "Revie
https://bugs.kde.org/show_bug.cgi?id=376849
Bug ID: 376849
Summary: clipped error text in toolviews
Product: kdevplatform
Version: git master
Platform: Compiled Sources
OS: other
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=376835
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
Doesn't KCrash provide bug reporting info that should protect against this
probably quite common kind of situation?
FWIW it might be quite useful anyway to extend DrKonqi with the same project
co
https://bugs.kde.org/show_bug.cgi?id=376854
Bug ID: 376854
Summary: patchreview/purpose integration: result dialog doesn't
provide review URL
Product: kdevplatform
Version: git master
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=376854
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
The signal in question is Purpose::Menu::finished
where is that one emitted? I suppose that should be done by `Purpose::Menu`,
but I cannot find where in the Purpose code...
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #73 from RJVB <rjvber...@gmail.com> ---
This is probably not related but then again maybe it is:
smb4k (git/head) has been crashing on me when quitting, with the backtrace
below. In this case it looks like there is a bug in VLC 2.2.4
https://bugs.kde.org/show_bug.cgi?id=348784
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Hah, I knew the crash rang a bell, interesting how the bug survived for such a
long time (without biting even me at least once a week)!
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=372040
--- Comment #11 from RJVB <rjvber...@gmail.com> ---
Created attachment 103447
--> https://bugs.kde.org/attachment.cgi?id=103447=edit
workaround patch
(In reply to Kevin Funk from comment #10)
> *** Bug 362037 has been marked as
https://bugs.kde.org/show_bug.cgi?id=365331
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
See my edit: the issue apparently resolved itself before the 5.3.0 release.
I haven't had time to follow digiKam development lately but I've made a mental
note to schedule an upgrade to git/
https://bugs.kde.org/show_bug.cgi?id=365331
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Reso
https://bugs.kde.org/show_bug.cgi?id=377107
Bug ID: 377107
Summary: key translation issue connecting to Linux from Mac
Product: krdc
Version: unspecified
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=369276
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #2 fro
https://bugs.kde.org/show_bug.cgi?id=369276
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
I guess this depends on exactly what you use it for in the toolbar, but yes,
it's possible.
The problem is a bit that I'm not perfectly sure exactly which classes are
concerned. The last time I'v
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
This is still a frequent obstacle that really degrades the user experience.
Having to wait up to several seconds every time your (mouse) cursor enters code
that is not correct (or no longer c
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Created attachment 102145
--> https://bugs.kde.org/attachment.cgi?id=102145=edit
simple patch to prevent beachballing
It may be useful to add a processEvents() call in this function's for
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
> Ideally this operation would be performed on a thread of its own, while the
> main thread continues to process events and aborts the operation in reaction
> to certain events (text
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
Yes, that's exactly what it is - but you can also provoke a nice fireworks
display of context browser tooltips with it ;)
It might resemble more of a fix if it's possible to check after proc
https://bugs.kde.org/show_bug.cgi?id=370227
--- Comment #13 from RJVB <rjvber...@gmail.com> ---
Looking at the backtrace again I'm not sure that this is a likely result of
using delete instead of deleteLater, but you could begin by checking that
AqBanking dialog. If it's a KDE dialog it
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #6 from RJVB <rjvber...@gmail.com> ---
Just had another one, I seem to be getting this crash more often these days.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366104
--- Comment #6 from RJVB <rjvber...@gmail.com> ---
Can't check anymore because I no longer manage to get my iPhone recognised
under Linux.
Off-topic here (maybe), but what exactly are the libraries, services etc.
required to be able to impor
https://bugs.kde.org/show_bug.cgi?id=366104
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
FWIW, someone should write a tiny iOS that allows to download photos off an
iDevice over TCP/IP, much like the G+/PicasaWeb plugin does!
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=369276
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comm
https://bugs.kde.org/show_bug.cgi?id=365331
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Edit: it would *seem* that the issue has resolved itself in 5.3.0 .
I agree something was wrong, but digiKam is the only application where I've
seen this happen with my build settings, an
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #68 from RJVB <rjvber...@gmail.com> ---
The KNotification file(s) in the backtrace may not even have evolved since 5.26
but indeed it's highly likely that the cause is elsewhere (= not in the
functions on the trace) given how dif
https://bugs.kde.org/show_bug.cgi?id=372627
Bug ID: 372627
Summary: Qt Assistant rendering glitch
Product: docs
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=372629
Bug ID: 372629
Summary: [OS X] line height too low issue(s)
Product: frameworks-ktexteditor
Version: 5.27.0
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 102304
--> https://bugs.kde.org/attachment.cgi?id=102304=edit
glyph clipping in v5.2.7; Macintosh native style
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
Hah, well, that misfired then, at least on OS X. I didn't check if 5.24.0 does
worse with the FreeType font engine.
This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
Created attachment 102305
--> https://bugs.kde.org/attachment.cgi?id=102305=edit
no clipping with v5.24.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372638
Bug ID: 372638
Summary: "the file was created by another program"
Product: frameworks-ktexteditor
Version: 5.27.0
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #8 from RJVB <rjvber...@gmail.com> ---
(In reply to RJVB from comment #4)
> This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3
Clearly not only that commit. Reverting just that makes line spacing too
generous (total te
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #9 from RJVB <rjvber...@gmail.com> ---
FWIW, this seems to work acceptably for me:
```C++
void KateRenderer::updateFontHeight()
{
// use height of font + round down, ensure we have at least one pixel
// we round down to
https://bugs.kde.org/show_bug.cgi?id=372629
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=335079
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #7 from RJVB <rjvber...@gmail.com> ---
(In reply to RJVB from comment #4)
> This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3
Clearly not only that commit. Reverting just that makes line spacing too
generous (total te
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #6 from RJVB <rjvber...@gmail.com> ---
Created attachment 102308
--> https://bugs.kde.org/attachment.cgi?id=102308=edit
better line spacing with 5.24.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
Created attachment 102307
--> https://bugs.kde.org/attachment.cgi?id=102307=edit
touching lines with 5.27.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #11 from RJVB <rjvber...@gmail.com> ---
What other OSes have you tried?
I guess it must have something to do with the font engine, an observation that
I think is supported by the fact that the adjustment isn't required when
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #17 from RJVB <rjvber...@gmail.com> ---
I'd say that the most important aspect here is that behaviour is as much the
same as possible across platforms. In this case that would mean that they all
have a sufficient line s
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #15 from RJVB <rjvber...@gmail.com> ---
Did you compare the spacing with qCeil and qFloor on Linux and/or MS Windows? I
find the line spacing just fine on Linux, and would regret it getting
significantly more ample *). Maybe it can b
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #13 from RJVB <rjvber...@gmail.com> ---
Yes, that seems to have about the same effect as my tweak. `qCeil(1.005f *
height)` is too much though (I tried that too, tuning down the extra space that
was obtained in the original code).
-
ion: kdevelop5 (5.0.2)
(Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.27.0
Operating System: Linux 4.5.7-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I hit the "Show differences
https://bugs.kde.org/show_bug.cgi?id=371934
--- Comment #2 from RJVB <rjvber...@gmail.com> ---
I no longer have the exact error message, but the code (114) should be all you
need. It was explained as "comment exceeds limit (65535 bytes)".
The report compiled in DrKonqi was su
https://bugs.kde.org/show_bug.cgi?id=366577
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=366577
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
FWIW, I now think the Q_QASSERT wasn't even reached; often the line number in a
backtrace like this is 1 higher than the location where the crash really
occurred (when code has been inlined).
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Kevin: judging from the report title they certainly appear to be related.
DrKonqi didn't serve up any candidate related tickets though, but that's maybe
just another feature that didn't survive t
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #5 from RJVB <rjvber...@gmail.com> ---
*** Bug 366577 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366577
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=371933
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
See Also||https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=371934
Bug ID: 371934
Summary: compatibility with DrKonqi
Product: bugs.kde.org
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
Severity:
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #16 from RJVB <rjvber...@gmail.com> ---
Have you tested building against LLVM versions < 3.7.9 on OS X? According to my
local patches those had a versioned libLLVM name (libLLVM-${LLVM_VERSION}), at
least in MacPorts.
Also, while e
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #18 from RJVB <rjvber...@gmail.com> ---
Is there anything Mac specific in support for different clang versions? I
didn't mention it but the exact same "build recipe" works fine on Linux with
clang 3.9 . Why would that be any
https://bugs.kde.org/show_bug.cgi?id=371934
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
Who remembers the days where 640Kb seemed a reasonable limit? ;)
I'm a bit surprised the database would (still) use a hard length limit, but
then I'm not a DB engineer and I guess KDE didn't
https://bugs.kde.org/show_bug.cgi?id=371752
Bug ID: 371752
Summary: Crash on exit because of Sublime::Document::view()
called through stale instance (this==NULL)
Product: kdevplatform
Version: git master
Platform: Compiled
https://bugs.kde.org/show_bug.cgi?id=371752
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 101836
--> https://bugs.kde.org/attachment.cgi?id=101836=edit
the complete bug report + backtrace.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371751
Bug ID: 371751
Summary: overzealous spam filter
Product: bugs.kde.org
Version: unspecified
Platform: Other
OS: All
Status: UNCONFIRMED
Severity: critical
https://bugs.kde.org/show_bug.cgi?id=371751
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 101835
--> https://bugs.kde.org/attachment.cgi?id=101835=edit
the "offending" ticket content
Crossing fingers, toes and eyes in hope the spam filter doesn't
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #60 from RJVB <rjvber...@gmail.com> ---
Created attachment 101792
--> https://bugs.kde.org/attachment.cgi?id=101792=edit
latest backtrace from KDevelop5
I'm still getting this crash with frameworks 5.27.0 and KDevelop5,
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #11 from RJVB <rjvber...@gmail.com> ---
Antonio: apologies for the delay. I never got (saw) a notification for your
question.
In practice I used a personal MacPorts port to build clazy:
https://github.com/RJVB/macstrop/tree/master
https://bugs.kde.org/show_bug.cgi?id=370227
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
The kdelibs libraries have always had a 5 version, confusingly.
If that gaelicish library is built against Qt5 then I'd indeed expect crashes,
but not just on exit. There should be an abor
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #24 from RJVB <rjvber...@gmail.com> ---
This works with 3.7, 3.8 and 3.9 from MacPorts. However, for 3.7 I had to
compensate for the fact that libLLVM is called libLLVM-3.7.dylib in that
version. I have no idea whether that's a Ma
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #26 from RJVB <rjvber...@gmail.com> ---
Created attachment 102004
--> https://bugs.kde.org/attachment.cgi?id=102004=edit
patch to allow building against llvm 3.7 on Mac
As said, I have no idea if the versions libLLVM name is an L
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #27 from RJVB <rjvber...@gmail.com> ---
(In reply to Sergio Martins from comment #25)
> but we're not linking to libLLVM.dylib, it's all static libs.. so why is
> that needed ? Or the static libs are also versioned ?
Well, no,
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #30 from RJVB <rjvber...@gmail.com> ---
(In reply to Sergio Martins from comment #28)
> the clazy branch fixing_mac doesn't even link to libLLVM
Oops, cross-over. Indeed, that corresponds to my observation!
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #31 from RJVB <rjvber...@gmail.com> ---
Except that then you need to get rid of this:
-if(APPLE)
- target_link_libraries(clazylib LLVM)
-endif()
because that adds -lLLVM to the link command. That'll succeed except with 3.7
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #33 from RJVB <rjvber...@gmail.com> ---
Yep, after removing that everything builds and runs against 3.7, 3.8 and 3.9 .
Note I've only tested it against a simple file that contains nothing clazy
complains about even at level3 but I
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #29 from RJVB <rjvber...@gmail.com> ---
This is what I have in the llvm lib dir:
> lc /opt/local/libexec/llvm-3.9/lib/libLLVM*
> l
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #64 from RJVB <rjvber...@gmail.com> ---
We'll see. I've applied the patch to my 5.27.0 systems and will update this
ticket when I get another crash.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=348414
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Reso
https://bugs.kde.org/show_bug.cgi?id=370227
--- Comment #8 from RJVB <rjvber...@gmail.com> ---
Do those supposed still-open dialogs have a QObject-based proxy/wrapper class?
One source of UI-related crashes on OS X is deleting object instances
representing UI elements that still have
https://bugs.kde.org/show_bug.cgi?id=373380
--- Comment #4 from RJVB <rjvber...@gmail.com> ---
Annoyingly I haven't yet been able to reproduce the crash. I'll update this
ticket if/when I can, but it certainly seems likely that the crash had
something to do with compositing. In fact I'm sur
https://bugs.kde.org/show_bug.cgi?id=373380
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
You're right, damn. DrKonqi gave 3 starts to the backtrace so I didn't look any
further.
I'll have to figure out if KaOS has something equivalent to Debuntu's dbg
packages. Not for everything, it
https://bugs.kde.org/show_bug.cgi?id=373475
--- Comment #3 from RJVB <rjvber...@gmail.com> ---
Apologies, the crash seemed familiar indeed but I couldn't find any previous
reports, nor could DrKonqi.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #9 from RJVB <rjvber...@gmail.com> ---
I'm now running a local patch that adds `m_view_to_action.contains()` checks
before all uses of `m_view_to_action.value()`, and which replaces Q_ASSERT with
a qCritical() message. No more crash
Target Milestone: ---
Application: kdevelop5 (5.0.3)
(Compiled from sources)
Qt Version: 5.6.2
Frameworks Version: 5.27.0
Operating System: Linux 4.5.7-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed
1 - 100 of 1337 matches
Mail list logo
