https://bugs.kde.org/show_bug.cgi?id=403800
Bug ID: 403800
Summary: KoPart::deleteOpenPane() should not delete
d->startupWidget(?)
Product: calligracommon
Version: unspecified
Platform: Compiled Sources
OS:
https://bugs.kde.org/show_bug.cgi?id=403644
RJVB changed:
What|Removed |Added
Assignee|kdevelop-bugs-n...@kde.org |rjvber...@gmail.com
--- Comment #1 from RJVB ---
1
https://bugs.kde.org/show_bug.cgi?id=403644
Bug ID: 403644
Summary: kdev-cmake : commit
7a16881ec33f4af2028593c2b3da7c1e20bf53c6 breaks
fallback to non-server mode
Product: kdevelop
Version: 5.3.1
https://bugs.kde.org/show_bug.cgi?id=401506
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #6 from RJVB
https://bugs.kde.org/show_bug.cgi?id=402997
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=402997
--- Comment #1 from RJVB ---
Created attachment 117342
--> https://bugs.kde.org/attachment.cgi?id=117342=edit
fatal PDF document
--
You are receiving this mail because:
You are watching all bug changes.
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed:
Opening the attached PDF document crashes Okular5 systematically.
Okular built from git/master
https://bugs.kde.org/show_bug.cgi?id=402992
Bug ID: 402992
Summary: circular symlinks can lock up kdevelop
Product: kdevelop
Version: 5.3.1
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=402760
RJVB changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC
https://bugs.kde.org/show_bug.cgi?id=402628
RJVB changed:
What|Removed |Added
URL||https://phabricator.kde.org
https://bugs.kde.org/show_bug.cgi?id=402628
--- Comment #7 from RJVB ---
I would have expected that kdev-clang depends on libclang to obtain the paths
to any headerfiles it needs at runtime. Indeed it isn't, and I can only see
that as a design flaw that more or less obliges you to build
https://bugs.kde.org/show_bug.cgi?id=402628
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #4 from RJVB ---
Time
https://bugs.kde.org/show_bug.cgi?id=402617
--- Comment #5 from RJVB ---
The simplest assumption is that `model()` returns NULL and that a check against
that is required as is done in other locations too. It's also conceivable (but
less likely) that cancelling the search invalidates
https://bugs.kde.org/show_bug.cgi?id=402617
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB ---
You
https://bugs.kde.org/show_bug.cgi?id=402497
Bug ID: 402497
Summary: server passwords are stored in cleartext in
konversationrc
Product: konversation
Version: Git
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #16 from RJVB ---
Created attachment 117049
--> https://bugs.kde.org/attachment.cgi?id=117049=edit
New crash information added by DrKonqi
kdevelop (5.3.1-4-gdc6a95e962) using Qt 5.9.7
- What I was doing when the application cras
https://bugs.kde.org/show_bug.cgi?id=339713
RJVB changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=372627
--- Comment #5 from RJVB ---
Indirectly, yes. It's that output which is compiled into a single .qch file.
In the meantime, WebKit support is still present in the Assistant (even in the
dev branch), and with talk of re-integrating the rebooted QtWebKit
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #15 from RJVB ---
Or maybe not ... I'm hardly able to work on this project at all today with
KDevelop crashing every other file:
libclang: crash detected during parsing: {
'source_filename' :
'/home/bertin/work/src/Scratch/KDE/KF5/marble
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #14 from RJVB ---
Now this is extra interesting: after sending off my previous comment and
quitting DrKonqi, the crashed KDevelop made a more or less clean exit, judging
from terminal output. It might even have able to continue to work
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #13 from RJVB ---
Created attachment 116733
--> https://bugs.kde.org/attachment.cgi?id=116733=edit
New crash information added by DrKonqi
kdevelop (5.3.0-38-g7898bb4174) using Qt 5.9.7
Here's a crash where I did manage to
https://bugs.kde.org/show_bug.cgi?id=401564
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #12 from RJVB ---
Well, I've never made such claims under the premise of spending 3 months on it
full-time (with or without the additional detail of a formal training in
computer science) O:-)
And in another there's that register: there's
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #10 from RJVB ---
Wow, is the architecture that complex or opaque (on top of the already not very
accessible libclang API itself)? If so we should hope nothing ever breaks when
the original author(s) are unavailable...
--
You
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #8 from RJVB ---
I will, though don't hold your breath I'll do better than someone who's bound
to know this part of the code a lot better than I do. The only brain fart I had
for now is how Objective C's support for sending messages
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #6 from RJVB ---
Or maybe they just designed the parser around a server architecture instead of
using lots of direct calls into libclang?
I haven't even tried to understand how the current architecture is designed.
But if the issue
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #4 from RJVB ---
Pity. Any idea how Qt Creator can pull it off then?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #2 from RJVB ---
FWIW:
Qt Creator appears to be using a server process to deploy its clang-based
parser. I don't know at what overhead cost that comes with, but I think there
are a few obvious advantages to the approach:
- crash-protection
https://bugs.kde.org/show_bug.cgi?id=401564
--- Comment #1 from RJVB ---
Another comparable crash where the process was killed before DrKonqi could get
a backtrace (= while it was trying to?). This time libclang printed a bit more:
see below.
I was in patchreview mode, and had just saved some
https://bugs.kde.org/show_bug.cgi?id=401600
--- Comment #1 from RJVB ---
Created attachment 116600
--> https://bugs.kde.org/attachment.cgi?id=116600=edit
expected UI look
This is how I expect the UI to look: matching the UI in use in KDevelop in the
other screenshot.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=401600
Bug ID: 401600
Summary: Incompatible style (colours, fonts) in git/master
(v1.1.90-182-gf338282)
Product: frameworks-purpose
Version: unspecified
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=401565
RJVB changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/pur
https://bugs.kde.org/show_bug.cgi?id=401565
RJVB changed:
What|Removed |Added
CC||mon...@kde.org
--- Comment #2 from RJVB ---
The crash
https://bugs.kde.org/show_bug.cgi?id=401565
--- Comment #1 from RJVB ---
Created attachment 116581
--> https://bugs.kde.org/attachment.cgi?id=116581=edit
New crash information added by DrKonqi
sharetool (1.0) using Qt 5.9.7
Confirmation of the crash using the `sharetool` test utility f
https://bugs.kde.org/show_bug.cgi?id=401565
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=401565
RJVB changed:
What|Removed |Added
Product|kdevelop|frameworks-purpose
Version|unspecified
Version: 5.52.0
Operating System: Linux 4.14.23-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 project for the KDevelop source tree in KDevelop
2 apply a patch and trigger the patch review plugin
https://bugs.kde.org/show_bug.cgi?id=401564
Bug ID: 401564
Summary: libclang bad filedescriptor crash (abort)?
Product: kdevelop
Version: git master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #34 from RJVB ---
Created attachment 116580
--> https://bugs.kde.org/attachment.cgi?id=116580=edit
terminal log
Here's a log showing an exceptionally large number of caught issues where a
hang would have resulted during the glo
https://bugs.kde.org/show_bug.cgi?id=401403
--- Comment #1 from RJVB ---
I've been testing a fix (workaround?) in urlForFileModel(), with some debug
output whenever a DiffModel::destinationPath() is encountered that does NOT
start with a slash. I have yet to see that warning...
Is it possible
https://bugs.kde.org/show_bug.cgi?id=401403
Bug ID: 401403
Summary: patchreview plugin causes Path::init:
invalid/unsupported Path encountered: ""
Product: kdevelop
Version: 5.3.0
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=355241
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #6 from RJVB
https://bugs.kde.org/show_bug.cgi?id=396287
RJVB changed:
What|Removed |Added
Resolution|INTENTIONAL |FIXED
Status|CLOSED
https://bugs.kde.org/show_bug.cgi?id=50
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=335584
RJVB changed:
What|Removed |Added
Resolution|--- |UNMAINTAINED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=398731
--- Comment #8 from RJVB ---
I think the queuing isn't new. Shouldn't really be a problem because how often
do you let the search wrap ("jump back and forth") under normal use?
I agree that a view flash is like the screen flickering and thu
https://bugs.kde.org/show_bug.cgi?id=398731
--- Comment #6 from RJVB ---
Created attachment 116423
--> https://bugs.kde.org/attachment.cgi?id=116423=edit
snapshot
(I also have a personal patch to make KMessage's less gaudy :) )
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=398731
--- Comment #5 from RJVB ---
Created attachment 116422
--> https://bugs.kde.org/attachment.cgi?id=116422=edit
patch to revert to simplified previous behaviour
I've patched the code for myself, back to using the Information colour (more
appropri
https://bugs.kde.org/show_bug.cgi?id=398731
RJVB changed:
What|Removed |Added
OS|Linux |All
Version|18.08.1
https://bugs.kde.org/show_bug.cgi?id=398731
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB ---
I
https://bugs.kde.org/show_bug.cgi?id=379669
--- Comment #33 from RJVB ---
FWIW, I haven't seen hangs in a while with my workaround patch applied. Debug
output showing that hang situations were handled appears quite regularly
though.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=401138
Bug ID: 401138
Summary: KDevelop showing duplicate contextmenu items
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: All
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=401069
RJVB changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=401069
RJVB changed:
What|Removed |Added
Attachment #116327|0 |1
is patch
https://bugs.kde.org/show_bug.cgi?id=401069
--- Comment #2 from RJVB ---
Created attachment 116327
--> https://bugs.kde.org/attachment.cgi?id=116327=edit
potential fix
2-hunk patch:
- Hunk 2 is a protection against emitting the signal multiple times
- Hunk 1 appears to be a fix ba
https://bugs.kde.org/show_bug.cgi?id=401069
--- Comment #1 from RJVB ---
Addendum:
Is this intended behaviour or a bug that was never detected because it never
caused visible side-effects?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401069
Bug ID: 401069
Summary: KTextEditor: aboutToShowContextMenu is emitted for all
open documents
Product: frameworks-ktexteditor
Version: unspecified
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=401018
RJVB changed:
What|Removed |Added
URL||https://phabricator.kde.org
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #8 from RJVB ---
Apologies, my initial hunch was right, this is an ECM issue.
See https://phabricator.kde.org/D16894
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401018
RJVB changed:
What|Removed |Added
Version|5.47.0 |unspecified
Product|frameworks-kconfig
https://bugs.kde.org/show_bug.cgi?id=401018
RJVB changed:
What|Removed |Added
CC||kdelibs-b...@kde.org
Component|general
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #6 from RJVB ---
Created attachment 116298
--> https://bugs.kde.org/attachment.cgi?id=116298=edit
sites.cpp preprocessed by clang 5.0.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #5 from RJVB ---
Created attachment 116297
--> https://bugs.kde.org/attachment.cgi?id=116297=edit
sites.cpp preprocessed by AppleClang
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401018
RJVB changed:
What|Removed |Added
Attachment #116295|build commands for |AppleClang build commands
description
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #4 from RJVB ---
Created attachment 116296
--> https://bugs.kde.org/attachment.cgi?id=116296=edit
clang build commands for configpage.cpp, sites.cpp and the failed link command
formatted for side-by-side comparison
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #3 from RJVB ---
Created attachment 116295
--> https://bugs.kde.org/attachment.cgi?id=116295=edit
build commands for configpage.cpp, sites.cpp and the failed link command
formatted for side-by-side comparison
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #2 from RJVB ---
Created attachment 116294
--> https://bugs.kde.org/attachment.cgi?id=116294=edit
build log with clang 5.0.2 from MacPorts
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401018
--- Comment #1 from RJVB ---
Created attachment 116293
--> https://bugs.kde.org/attachment.cgi?id=116293=edit
libkcddb 18.08.3 build log with AppleClang 602
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=401018
Bug ID: 401018
Summary: Visibility problems with Apple's Xcode/clang compilers
Product: extra-cmake-modules
Version: unspecified
Platform: Compiled Sources
OS: OS X
https://bugs.kde.org/show_bug.cgi?id=338780
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |INTENTIONAL
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=339333
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=338447
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=335881
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=337884
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UNMAINTAINED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=384710
--- Comment #6 from RJVB ---
Applies and builds in the 5.3 branch too. Can't yet say if it also has the
desired effect but why wouldn't it... So thanks, it was quite annoying for a
minor nuisance.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=377379
--- Comment #3 from RJVB ---
And I completely forgot about this issue, which I haven't seen in a long time.
If memory serves me well it was either due to something in Qt, or I found a
workaround after posting about the issue on a Qt mailing list
https://bugs.kde.org/show_bug.cgi?id=377379
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=389873
--- Comment #5 from RJVB ---
FWIW it works fine on Mac too (I'm using it to post this message ...)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=389873
--- Comment #3 from RJVB ---
Weird indeed. I presume Krypton also has the "rebooted" WebKit 5.212, not the
obsolete community release from Qt?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399985
Bug ID: 399985
Summary: konqueror mishandles website URLs given on
thecommandline
Product: konqueror
Version: Git
Platform: Compiled Sources
OS: All
https://bugs.kde.org/show_bug.cgi?id=389873
RJVB changed:
What|Removed |Added
Severity|normal |major
--- Comment #1 from RJVB ---
Still not fixed
https://bugs.kde.org/show_bug.cgi?id=370499
--- Comment #5 from RJVB ---
Indeed - didn't I imply something about my memory ;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370499
--- Comment #2 from RJVB ---
Fixed in the *current* version, over 20 releases later? Wow, that redefines
certain concepts...
And no, I didn't forget to close the ticket. I completely forgot it was there -
and since I've long stopped having the time
https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #12 from RJVB ---
Quick question: the current code puts the actual signal handler installation in
#ifdef SIGFOO blocks. I'm guessing that's for platforms like MS Windows that
don't have POSIX style signal handling?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #11 from RJVB ---
Turns out a non-blocking and clean-enough exit can be achieved simply by
calling Core::shutdown() before the actual exit so that's easy enough.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=399473
RJVB changed:
What|Removed |Added
Resolution|NOT A BUG |LATER
--- Comment #9 from RJVB ---
I guess if you
https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #7 from RJVB ---
Synthetic demonstration of unwanted behaviour:
> Xnest :1 &
> env DISPLAY=:1 kdevelop5 &
> killall -STOP %1 # suspend Xnest
> kill -HUP %2 # send SIGHUP to KDevelop
As expected this causes KDevelop
https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #6 from RJVB ---
To get this back to a hopefully more constructive state (and ignoring for the
moment whether or not calling Qt API from a signal handler is an issue or not):
what would be the best way to make the exit procedure as least
https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #5 from RJVB ---
Erm, indeed, I saw that be then remained stuck on using SIGHUP, probably
because of the added "like almost every other application on your desktop").
Not that it matters, fgrep 'signal(' shows
kdevelop-git/kd
https://bugs.kde.org/show_bug.cgi?id=399473
RJVB changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=399473
--- Comment #2 from RJVB ---
No, it doesn't, not when running remotely in any case (or when the remote
server has become unavailable). Possibly idem when a local server is going down
hard, but that's a bit of a corner case.
You're right that a normal
https://bugs.kde.org/show_bug.cgi?id=399473
Bug ID: 399473
Summary: [feature] proper exit after SIGHUP
Product: kdevelop
Version: unspecified
Platform: Compiled Sources
OS: All
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=336798
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |LATER
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=387238
RJVB changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|REMIND
https://bugs.kde.org/show_bug.cgi?id=384775
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=368905
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=345482
RJVB changed:
What|Removed |Added
Resolution|WAITINGFORINFO |UPSTREAM
--- Comment #4 from RJVB ---
I haven't used
https://bugs.kde.org/show_bug.cgi?id=399048
RJVB changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=399025
--- Comment #4 from RJVB ---
Like me.
In a way I would have preferred a different answer just to be able to exclude
the widget style as somehow responsible.
@Yichao, can you have a look and check if the issue described here and in
D15625 is indeed
https://bugs.kde.org/show_bug.cgi?id=399025
RJVB changed:
What|Removed |Added
CC||yyc1...@gmail.com
--
You are receiving this mail
301 - 400 of 1337 matches
Mail list logo
