https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #11 from RJVB ---
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/devel/clazy
The "Por
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #60 from RJVB ---
Created attachment 101792
--> https://bugs.kde.org/attachment.cgi?id=101792&action=edit
latest backtrace from KDevelop5
I'm still getting this crash with frameworks 5.27.0 and KDevelop5, but very
sporadica
https://bugs.kde.org/show_bug.cgi?id=348414
RJVB changed:
What|Removed |Added
Status|REOPENED|NEEDSINFO
Resolution
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #64 from RJVB ---
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=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 ---
Created attachment 101835
--> https://bugs.kde.org/attachment.cgi?id=101835&action=edit
the "offending" ticket content
Crossing fingers, toes and eyes in hope the spam filter doesn't attack
at
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 ---
Created attachment 101836
--> https://bugs.kde.org/attachment.cgi?id=101836&action=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=370227
--- Comment #4 from RJVB ---
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 abort much earlier in that
https://bugs.kde.org/show_bug.cgi?id=370227
--- Comment #8 from RJVB ---
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 events pending, which can
cktrace
Application: 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
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: gr
https://bugs.kde.org/show_bug.cgi?id=371934
--- Comment #2 from RJVB ---
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 submitted manually as
https://bu
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #3 from RJVB ---
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 the BKO up
https://bugs.kde.org/show_bug.cgi?id=366577
--- Comment #3 from RJVB ---
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). IOW, I think the crash ha
https://bugs.kde.org/show_bug.cgi?id=366577
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=366577
RJVB changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #5 from RJVB ---
*** 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=371933
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=371934
--- Comment #4 from RJVB ---
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 write their own b
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #16 from RJVB ---
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 everything builds correc
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #18 from RJVB ---
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 different on Ma
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #24 from RJVB ---
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 MacPorts thing or not.
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #26 from RJVB ---
Created attachment 102004
--> https://bugs.kde.org/attachment.cgi?id=102004&action=edit
patch to allow building against llvm 3.7 on Mac
As said, I have no idea if the versions libLLVM name is an LLVM thing or a
M
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #27 from RJVB ---
(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, I'm getting d
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #30 from RJVB ---
(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 this mail because:
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #31 from RJVB ---
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
where that library doesn&#x
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #33 from RJVB ---
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 don't really s
https://bugs.kde.org/show_bug.cgi?id=352896
--- Comment #29 from RJVB ---
This is what I have in the llvm lib dir:
> lc /opt/local/libexec/llvm-3.9/lib/libLLVM*
> libLLVM.dylib*
> libLLVM
https://bugs.kde.org/show_bug.cgi?id=366104
--- Comment #6 from RJVB ---
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 import from an iPhone?
--
Yo
https://bugs.kde.org/show_bug.cgi?id=366104
--- Comment #7 from RJVB ---
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 watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=369276
RJVB changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #2 from RJVB ---
The thing is that
https://bugs.kde.org/show_bug.cgi?id=369276
--- Comment #4 from RJVB ---
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've seen a rea
https://bugs.kde.org/show_bug.cgi?id=369276
RJVB changed:
What|Removed |Added
CC||cullm...@kde.org
--- Comment #5 from RJVB ---
So, I
https://bugs.kde.org/show_bug.cgi?id=371933
--- Comment #6 from RJVB ---
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=362037
--- Comment #3 from RJVB ---
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 correct, as in when you change a
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #4 from RJVB ---
> 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 input or focus movement that ch
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #5 from RJVB ---
Created attachment 102145
--> https://bugs.kde.org/attachment.cgi?id=102145&action=edit
simple patch to prevent beachballing
It may be useful to add a processEvents() call in this function's fore
https://bugs.kde.org/show_bug.cgi?id=362037
--- Comment #7 from RJVB ---
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 processing the
events if
https://bugs.kde.org/show_bug.cgi?id=370227
--- Comment #13 from RJVB ---
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 could be a prime can
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 ---
Created attachment 102304
--> https://bugs.kde.org/attachment.cgi?id=102304&action=edit
glyph clipping in v5.2.7; Macintosh native style
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #2 from RJVB ---
Created attachment 102305
--> https://bugs.kde.org/attachment.cgi?id=102305&action=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=372629
--- Comment #4 from RJVB ---
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 receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #5 from RJVB ---
Created attachment 102307
--> https://bugs.kde.org/attachment.cgi?id=102307&action=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 #6 from RJVB ---
Created attachment 102308
--> https://bugs.kde.org/attachment.cgi?id=102308&action=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
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=335079
RJVB changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
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 #7 from RJVB ---
(In reply to RJVB from comment #4)
> This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3
Clearly not only that commit. Reverting just that makes line spacing too
generous (total text height increases by approx.
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #8 from RJVB ---
(In reply to RJVB from comment #4)
> This commit? 4c83bac52716a08a549dca50a76be8aa47c11ca3
Clearly not only that commit. Reverting just that makes line spacing too
generous (total text height increases by approx.
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #9 from RJVB ---
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 avoid artifacts: line height too
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #11 from RJVB ---
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 I use
the Freetype font engine
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #13 from RJVB ---
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).
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #15 from RJVB ---
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 be tied to the hidpi setting
https://bugs.kde.org/show_bug.cgi?id=372629
--- Comment #17 from RJVB ---
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 spacing, and that a same font size will
https://bugs.kde.org/show_bug.cgi?id=365331
--- Comment #5 from RJVB ---
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, and only for a few Qt librari
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #68 from RJVB ---
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 difficult it is to reproduc
https://bugs.kde.org/show_bug.cgi?id=348414
--- Comment #69 from RJVB ---
As if it's contagious: I had another one of these crashes in KDevelop, with
5.27.0 installed.
And then just now dolphin5 crashed on me when I tried to suppress a file (with
Shift-Del to delete it without going throug
https://bugs.kde.org/show_bug.cgi?id=340982
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #117 from RJVB ---
(In reply to Don Curtis from comment #112)
> (In reply to phma from comment #102)
> > I'd like to see KLocale reinstated, at least until QLocale is as flexible
> > as KLocale.
>
> My vote is
https://bugs.kde.org/show_bug.cgi?id=450529
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB ---
(In
https://bugs.kde.org/show_bug.cgi?id=450529
--- Comment #5 from RJVB ---
Erm, if the digiKam version is too old to run on 12.x it probably shouldn't run
at all, not simply lose all settings and then work again after resetting them.
And if an update of digiKam itself causes this kind of fa
https://bugs.kde.org/show_bug.cgi?id=439639
--- Comment #7 from RJVB ---
Not broken, just not updated. At least, that was the case in July 2021. I've
had it working for some time since but it seems something may have changed yet
again.
--
You are receiving this mail because:
You are wat
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #219 from RJVB ---
And what happened to the "there are no [more] KDE apps" (certainly not as
opposed to "mere" Qt apps) I got whacked with only a few years back, when the
KF5 frameworks were nothing more and nothin
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #222 from RJVB ---
Doesn't Qt have to be configured to use ICU, or is that only on non-linux/unix
platforms (Mac included)?
ICU uses hardcoded locale definitions?
FWIW, the specialty library approach I mentioned could of course pr
https://bugs.kde.org/show_bug.cgi?id=405227
--- Comment #3 from RJVB ---
That's going to be tricky because KInit is a tier-3 fw and I am still blocked
on 5.60.0 on my Mac. I'll see if any relevant changes have been made to the
code paths involved here, to what extent I can backport the
https://bugs.kde.org/show_bug.cgi?id=405227
--- Comment #5 from RJVB ---
Besides being in the MacPorts camp HB still wouldn't allow me to run Qt 5.15 .
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405227
--- Comment #7 from RJVB ---
Because my system doesn't run anything newer than Qt 5.9
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412469
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=419831
RJVB changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=408725
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=413876
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=337356
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #271 from RJVB ---
(In reply to Erec from comment #270)
> Either roll a klocale or something that allows a user to select
> their own date time settings or honor a custom locale.
I think it must be clear to everyone by now that t
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #258 from RJVB ---
(In reply to brenbarn from comment #257)
> (In reply to Nate Graham from comment #253)
> > "ALERT! Changing this only affects KDE apps! It will not affect the way
> > dates are expressed in any
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #260 from RJVB ---
(In reply to Nate Graham from comment #259)
> Is there such an option for GTK and/or other toolkits?
How is that relevant if KDE already has a sync service that apparently does
what I'm suggesting? I have no i
https://bugs.kde.org/show_bug.cgi?id=274170
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #21 from RJVB ---
(In
https://bugs.kde.org/show_bug.cgi?id=486210
Bug ID: 486210
Summary: Missing future-proofing "fix" for clang >= 16
Classification: Frameworks and Libraries
Product: Phonon
Version: unspecified
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #51 from RJVB ---
I too only seem to be getting this crash only sporadically nowadays, and AFAICT
there's (almost) always a prematurely unloaded language plugin involved. But
I'm pretty certain it does not only occur after work
https://bugs.kde.org/show_bug.cgi?id=446319
Bug ID: 446319
Summary: [Proposal] legacy Qt5 branch
Product: qca
Version: Git
Platform: Other
OS: All
Status: REPORTED
Severity: wishlist
Priority: NO
https://bugs.kde.org/show_bug.cgi?id=446319
--- Comment #2 from RJVB ---
This doesn't just apply to "super old Qt" of course,but whatever :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361958
--- Comment #9 from RJVB ---
Sure, and if you run it on different machines you remove a few other potential
possibilities for unexpected or at least unwanted interaction.
IOW, it (partly) defeats the purpose of being able to open several projects in
a
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #47 from RJVB ---
> The problem is that currentIndex is 0 and it never bails out. This is with
> the very latest release.
IIRC this is one of the things my patch addresses.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=442674
Bug ID: 442674
Summary: Extension side-effects on unsupported platforms
Product: plasma-browser-integration
Version: unspecified
Platform: Other
OS: macOS
Status: REPORTED
)
Qt Version: 5.9.8
Frameworks Version: 5.60.0
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Windowing system: X11
Distribution: Ubuntu 14.04.6 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I quit KDevelop. I have my personal patch that helps
https://bugs.kde.org/show_bug.cgi?id=387061
--- Comment #43 from RJVB ---
(In reply to Wolfgang Bauer from comment #42)
> Have you tried in Chromium though? (which is what QtWebEngine is based upon)
Current versions of Firefox tend to consume more memory than Chromium - in
fact,I underst
https://bugs.kde.org/show_bug.cgi?id=387061
--- Comment #45 from RJVB ---
(In reply to Wolfgang Bauer from comment #44)
> I do use QtWebKit with konqueror, and opening large OBS logs (which are just
> text files) do take a while.
TBH, Konqueror is such a multipurpose tool that I have n
https://bugs.kde.org/show_bug.cgi?id=371489
--- Comment #14 from RJVB ---
(In reply to Nate Graham from comment #12)
> I don't think this is an actionable issue, sorry. :( There is a vocal
> contingent of users on both sides of this issue: right now, we get bug
> reports and c
https://bugs.kde.org/show_bug.cgi?id=371489
--- Comment #16 from RJVB ---
And I said create two ADDITIONAL styles, one smaller, one larger, so that all 3
camps (assuming there are indeed 3) have a choice.
But it should be possible to make the padding (as well as the size of elements)
scalable
https://bugs.kde.org/show_bug.cgi?id=438201
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #11 from RJVB
https://bugs.kde.org/show_bug.cgi?id=439091
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=405556
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB ---
This
https://bugs.kde.org/show_bug.cgi?id=440466
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #2 from RJVB ---
The
https://bugs.kde.org/show_bug.cgi?id=440580
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #2 from RJVB
https://bugs.kde.org/show_bug.cgi?id=403913
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #8 from RJVB ---
Isn&#
Version: 5.9.8
Frameworks Version: 5.60.0
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Windowing system: X11
Distribution: Ubuntu 14.04.6 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I had checked the Print Preview and closed it by hitting
https://bugs.kde.org/show_bug.cgi?id=439216
--- Comment #1 from RJVB ---
And FWIW, PageView::capability() needs to check every one of the QActions in
the d-ptr before accessing them, because aViewContinuous, aViewMode and
aTrimMargins can all turn out to be a nullptr.
Add a qDebug if you want
https://bugs.kde.org/show_bug.cgi?id=439216
--- Comment #4 from RJVB ---
Well, this is strange, I'm convinced that DrKonqi showed me a backtrace of the
same bug, but I must have gotten confused.
I am positive though that it didn't suggest bug 415340 - evidently I would not
have fil
1 - 100 of 1357 matches
Mail list logo
