[kdevplatform] [Bug 371210] patch review shouldn't add files it opens to the recent files menu

https://bugs.kde.org/show_bug.cgi?id=371210 RJVB changed: What|Removed |Added Resolution|--- |FIXED

[kdevplatform] [Bug 371210] patch review shouldn't add files it opens to the recent files menu

https://bugs.kde.org/show_bug.cgi?id=371210 RJVB changed: What|Removed |Added URL||https://git.reviewboard.kde

[kdevplatform] [Bug 371210] patch review shouldn't add files it opens to the recent files menu

https://bugs.kde.org/show_bug.cgi?id=371210 RJVB changed: What|Removed |Added Severity|wishlist|normal -- You are receiving this

[kdevplatform] [Bug 371210] patch review shouldn't add files it opens to the recent files menu

https://bugs.kde.org/show_bug.cgi?id=371210 --- Comment #1 from RJVB --- Created attachment 101650 --> https://bugs.kde.org/attachment.cgi?id=101650=edit patch review temporary patchfiles in the recent files menu The large number of changed files that overwrote my recent

[kmail2] [Bug 371228] enable remote search on IMAP servers

https://bugs.kde.org/show_bug.cgi?id=371228 --- Comment #1 from RJVB --- Created attachment 101647 --> https://bugs.kde.org/attachment.cgi?id=101647=edit a first draft for enabling remote search in the QuickSearch toolbar. WIP! -- You are receiving this mail because: You

[kmail2] [Bug 371228] enable remote search on IMAP servers

https://bugs.kde.org/show_bug.cgi?id=371228 RJVB changed: What|Removed |Added CC||d...@newtech.fi -- You are

[kmail2] [Bug 371228] New: enable remote search on IMAP servers

https://bugs.kde.org/show_bug.cgi?id=371228 Bug ID: 371228 Summary: enable remote search on IMAP servers Product: kmail2 Version: unspecified Platform: Other OS: other Status: UNCONFIRMED Severity:

[kdevplatform] [Bug 371210] New: patch review shouldn't add files it opens to the recent files menu

https://bugs.kde.org/show_bug.cgi?id=371210 Bug ID: 371210 Summary: patch review shouldn't add files it opens to the recent files menu Product: kdevplatform Version: unspecified Platform: Compiled Sources

[Akonadi] [Bug 340813] sometimes two copies of mysqld are running with Akonadi

https://bugs.kde.org/show_bug.cgi?id=340813 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment

[Akonadi] [Bug 367638] DATABASE ERROR: 1452

https://bugs.kde.org/show_bug.cgi?id=367638 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #2

[kontact] [Bug 370646] Crash because of stale (dangling) pointers in the attribute registry

https://bugs.kde.org/show_bug.cgi?id=370646 RJVB changed: What|Removed |Added URL||http://arstechnica.com/civi

[kontact] [Bug 370646] Crash because of stale (dangling) pointers in the attribute registry

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #8 from RJVB --- This bug has gotten under my skin. Having looked at this a bit more and asking around a bit, the most likely explanation for the crash is this: - KCModuleLoader::loadModule() loads the library to get a

[kontact] [Bug 370646] Crash because of stale (dangling) pointers in the attribute registry

https://bugs.kde.org/show_bug.cgi?id=370646 RJVB changed: What|Removed |Added Summary|Crash when opening Kontact |Crash because of stale

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #15 from RJVB --- Let's just hope that it's the only fix required. As I said, it's not like I had systematic error messages about the dynamic_cast or even systematic failures, making this somewhat of a Heisenbug. I'll

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #11 from RJVB --- Created attachment 101587 --> https://bugs.kde.org/attachment.cgi?id=101587=edit Give IProblem public visibility. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #10 from RJVB --- For now the patch below seems to be a proper fix but I cannot vouch if it's a definite fix too. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #9 from RJVB --- So, changing the "assert's" else clause to const auto ptr = diagnostic.data(); qWarning() << Q_FUNC_INFO << "dynamic cast to ClangProblem failed of" << ptr <<

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #8 from RJVB --- BTW, I see that ClangProblem already has a KDEVCLANGPRIVATE_EXPORT macro in its definition; its parents have KDEVPLATFORMLANGUAGE_EXPORT except for IProblem. Am I correct that this changes your

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #7 from RJVB --- Ok, let's not call it a fix then, but a sensible protection. It's still wrong to just let code fail somewhere down the line by allowing it to dereference a null pointer. And if the dynamic_cast isn't

[kontact] [Bug 370646] Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #7 from RJVB --- I see there's been a chronological glitch in my comments :-/ I wonder: shouldn't it be more elegant to do the actual unregistering (attributes.erase(x)) in the Attribute dtor? I'll need to check if the

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #5 from RJVB --- What can possibly wrong about the fix? If a variable shouldn't be NULL and there are apparently reasons why it can happen outside of reasonable precautions, NOT checking is wrong. And clearly this is

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #3 from RJVB --- scrap that about not seeing the warning: ClangFixits ClangProblem::allFixits() const dynamic cast to ClangProblem failed of 0x7fa2e1f475a8 ClangFixits ClangProblem::allFixits() const dynamic cast to

[kdevelop] [Bug 363893] dynamic_cast error, type_info's (sic) should have public visibility

https://bugs.kde.org/show_bug.cgi?id=363893 RJVB changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 RJVB changed: What|Removed |Added CC||kf...@kde.org See Also|

[kontact] [Bug 370646] Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #6 from RJVB --- #1 (anonymous namespace)::NoteSharedRegistrar::~NoteSharedRegistrar()() at .../kdepim-4.14.git/noteshared/attributes/attributeregistrar.cpp:44 #2 (anonymous

[kontact] [Bug 370646] Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #5 from RJVB --- I don't understand how or why dynamically allocated memory can go stale when the shared library which allocated it is unloaded, but apparently something like that happens. When I replace

[kdevelop] [Bug 370641] kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 --- Comment #1 from RJVB --- Another one: Is this output from KDevelop too? "error: abstractnavigationwidget.cpp.o DWARF DIE at 0x16b4 for class 'QWidget' has a base class 'QObject' that is a forward declaration, not a

[kontact] [Bug 370646] Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #4 from RJVB --- Why this happens is unclear to me, but the line const bool registered = dummy(); in libnoteshared's attributeregistrar.cpp is executed twice. I think that can only happen when the library is loaded

[kontact] [Bug 370646] Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #3 from RJVB --- I ran kontact through valgrind to get another angle. I think in the end it just confirms what I already thought: ``` --72548-- run: /usr/bin/dsymutil "/opt/local/lib/kde4/kcm_knote.so" --72548-- run:

[kontact] [Bug 370646] Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 --- Comment #2 from RJVB --- Backtrace below. Among the things I tried was not deleting only attributes of type NoteDisplayAttribute. That actually made things worse, somehow, causing crashes even when the application was starting

[kontact] [Bug 370646] New: Crash when opening Kontact preferences

https://bugs.kde.org/show_bug.cgi?id=370646 Bug ID: 370646 Summary: Crash when opening Kontact preferences Product: kontact Version: GIT (master) Platform: Compiled Sources OS: OS X Status: UNCONFIRMED

[kdevelop] [Bug 370641] New: kdevelop (clang parser) crash when selecting a specific line

https://bugs.kde.org/show_bug.cgi?id=370641 Bug ID: 370641 Summary: kdevelop (clang parser) crash when selecting a specific line Product: kdevelop Version: 5.0.1 Platform: Compiled Sources OS: OS X

[frameworks-kfilemetadata] [Bug 370499] New: bug in FindFFmpeg.cmake

https://bugs.kde.org/show_bug.cgi?id=370499 Bug ID: 370499 Summary: bug in FindFFmpeg.cmake Product: frameworks-kfilemetadata Version: 5.27.0 Platform: Compiled Sources OS: All Status: UNCONFIRMED

[kate] [Bug 370257] [OS X] weird window "dissociation" glitch

https://bugs.kde.org/show_bug.cgi?id=370257 --- Comment #2 from RJVB --- I cannot reproduce this when starting Kate through the Finder; in that case its window also opens with the document already open. It is thus faster to start, but also faster to quit. And finally, when I

[kate] [Bug 370257] [OS X] weird window "dissociation" glitch

https://bugs.kde.org/show_bug.cgi?id=370257 --- Comment #1 from RJVB --- Created attachment 101475 --> https://bugs.kde.org/attachment.cgi?id=101475=edit screenshot showing the glitch -- You are receiving this mail because: You are watching all bug changes.

[kate] [Bug 370257] New: [OS X] weird window "dissociation" glitch

https://bugs.kde.org/show_bug.cgi?id=370257 Bug ID: 370257 Summary: [OS X] weird window "dissociation" glitch Product: kate Version: 16.04.1 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED

[kdevelop] [Bug 361805] cmake project manager should call cmake without any arguments on imported pre-existing build directories (and maybe not auto-call at all)

https://bugs.kde.org/show_bug.cgi?id=361805 --- Comment #2 from RJVB --- Will do, but probably not before next week. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

https://bugs.kde.org/show_bug.cgi?id=348414 --- Comment #52 from RJVB --- Sadly, no. I cannot recall having seen this crash, but I also do not normally get an audio notification when I do a git commit through KDevelop. If ever it becomes a habit I can try to provoke this

[kdevplatform] [Bug 369278] debugger toolbar (and toolbar items in general) should remain put where user left it (and maintain its visibility across restarts)

https://bugs.kde.org/show_bug.cgi?id=369278 RJVB changed: What|Removed |Added Flags||Usability+ --- Comment #2 from

[kdevplatform] [Bug 369278] debugger toolbar (and toolbar items in general) should remain put where user left it (and maintain its visibility across restarts)

https://bugs.kde.org/show_bug.cgi?id=369278 RJVB changed: What|Removed |Added Summary|debugger toolbar should |debugger toolbar (and

[frameworks-knotifications] [Bug 348414] Crash in KNotification::flags() (NotifyByAudio::onAudioFinished)

https://bugs.kde.org/show_bug.cgi?id=348414 RJVB changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #9 from RJVB --- I think that what happens is that the review and debug areas have its own setting for the documentation visibility, and that somehow the visibility isn't restored properly when going back to the code

[kdevplatform] [Bug 369278] debugger toolbar should remain put where user left it (and maintain its visibility)

https://bugs.kde.org/show_bug.cgi?id=369278 --- Comment #1 from RJVB --- A bit more info on this one: apparently the debugger toolbar state is saved in more than 1 location. If it reappears against my instructions, I quit KDevelop and turn the debugger toolbar off in

[buildsystem] [Bug 369554] sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity

https://bugs.kde.org/show_bug.cgi?id=369554 RJVB changed: What|Removed |Added URL||https://git.reviewboard.kde

[buildsystem] [Bug 369554] sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity

https://bugs.kde.org/show_bug.cgi?id=369554 --- Comment #1 from RJVB --- I don't really know how invasive it would be to address this issue properly, or rather, how to fix this without being overly invasive. Looking at KPeople I see

[buildsystem] [Bug 369554] New: sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity

https://bugs.kde.org/show_bug.cgi?id=369554 Bug ID: 369554 Summary: sleeper design bug in the installation layout due to assumptions about filesystem case sensitivity Product: buildsystem Version: unspecified Platform:

[kdevplatform] [Bug 369546] code browser popup shows wrong function declaration

https://bugs.kde.org/show_bug.cgi?id=369546 --- Comment #1 from RJVB --- Created attachment 101352 --> https://bugs.kde.org/attachment.cgi?id=101352=edit screenshot showing the code browser glitch. NB: INFINITE is defined to be -1 -- You are receiving this mail because:

[kdevplatform] [Bug 369546] New: code browser popup shows wrong function declaration

https://bugs.kde.org/show_bug.cgi?id=369546 Bug ID: 369546 Summary: code browser popup shows wrong function declaration Product: kdevplatform Version: git master Platform: Compiled Sources OS: All Status:

[kdevelop] [Bug 369525] Rewrite the command echo in the Build toolview

https://bugs.kde.org/show_bug.cgi?id=369525 --- Comment #2 from RJVB --- "Copy to clipboard" doesn't give a lot of leeway to address the issue; the only intervention I can see that can be applied without too much 2nd-guessing is to strip the final newline from the selection.

[kdevelop] [Bug 369525] New: Rewrite the command echo in the Build toolview

https://bugs.kde.org/show_bug.cgi?id=369525 Bug ID: 369525 Summary: Rewrite the command echo in the Build toolview Product: kdevelop Version: git master Platform: Other OS: All Status: UNCONFIRMED

[kdevelop] [Bug 369483] New: KDevelop crash after cancelling a CMake project import

https://bugs.kde.org/show_bug.cgi?id=369483 Bug ID: 369483 Summary: KDevelop crash after cancelling a CMake project import Product: kdevelop Version: 5.0.1 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED

[kdevplatform] [Bug 369278] debugger toolbar should remain put where user left it (and maintain its visibility)

https://bugs.kde.org/show_bug.cgi?id=369278 RJVB changed: What|Removed |Added CC||7437...@gmail.com -- You are

[kde] [Bug 369238] KDevelop5 hang on exit in itemrepository.h (deleteItem())

https://bugs.kde.org/show_bug.cgi?id=369238 RJVB changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this

[kdevplatform] [Bug 369278] New: debugger toolbar should remain put where user left it (and maintain its visibility)

https://bugs.kde.org/show_bug.cgi?id=369278 Bug ID: 369278 Summary: debugger toolbar should remain put where user left it (and maintain its visibility) Product: kdevplatform Version: git master Platform: Compiled Sources

[frameworks-kxmlgui] [Bug 369276] New: KActionCollection, menu/action reuse and the native Mac menubar

https://bugs.kde.org/show_bug.cgi?id=369276 Bug ID: 369276 Summary: KActionCollection, menu/action reuse and the native Mac menubar Product: frameworks-kxmlgui Version: unspecified Platform: Other OS: OS X

[kdevplatform] [Bug 306128] kdevelop crashs on launch after crash on remove project [ItemRepository::followerIndex assertion]

https://bugs.kde.org/show_bug.cgi?id=306128 --- Comment #5 from RJVB --- Let me copy part of the duplicate I just filed (through DrKonqi which didn't find this report): In a debug build the ASSERTS will provoke an abort in the situation that caused my latest hang, but now

[kde] [Bug 369238] KDevelop5 hang on exit in itemrepository.h (deleteItem())

https://bugs.kde.org/show_bug.cgi?id=369238 --- Comment #2 from RJVB --- DrKonqi c/should have picked up that report... -- You are receiving this mail because: You are watching all bug changes.

[kde] [Bug 369238] KDevelop5 hang on exit in itemrepository.h (deleteItem())

https://bugs.kde.org/show_bug.cgi?id=369238 RJVB changed: What|Removed |Added CC||kf...@kde.org -- You are

[kde] [Bug 369238] New: KDevelop5 hang on exit in itemrepository.h (deleteItem())

https://bugs.kde.org/show_bug.cgi?id=369238 Bug ID: 369238 Summary: KDevelop5 hang on exit in itemrepository.h (deleteItem()) Product: kde Version: unspecified Platform: unspecified OS: Linux

[kde] [Bug 369237] New: KDevelop5 hang on exit in itemrepository.h (deleteItem())

https://bugs.kde.org/show_bug.cgi?id=369237 Bug ID: 369237 Summary: KDevelop5 hang on exit in itemrepository.h (deleteItem()) Product: kde Version: unspecified Platform: unspecified OS: Linux

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=369207 --- Comment #5 from RJVB --- Created attachment 101240 --> https://bugs.kde.org/attachment.cgi?id=101240=edit Patch to work around the issue on OS X Moving the Mode and Highlighting menus into the popup/context menu makes them

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=369207 --- Comment #4 from RJVB --- According to QMenu::isEnabled() and QAction::isEnabled(), the submenus and their actions are all enabled. However, according to the QMenu documentation: QMenu on OS X with Qt Build Against Cocoa

[kdevelop] [Bug 369227] New: relative build directories

https://bugs.kde.org/show_bug.cgi?id=369227 Bug ID: 369227 Summary: relative build directories Product: kdevelop Version: unspecified Platform: Other OS: All Status: UNCONFIRMED Severity: wishlist

[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than what is set globally (e.g. 3 lines)

https://bugs.kde.org/show_bug.cgi?id=256561 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=369207 --- Comment #3 from RJVB --- So this appears to be related to using the Mac toplevel menubar: adding QCoreApplication::setAttribute(Qt::AA_DontUseNativeMenuBar); to main() gives functional and populated Mode an Highlighting

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=369207 --- Comment #2 from RJVB --- Created attachment 101236 --> https://bugs.kde.org/attachment.cgi?id=101236=edit screenshot of KDevelop running in X11 mode on OS X, showing a normal Tools/Mode menu (with an additional item) -- You

[kate] [Bug 369207] Mode & Highlighting menus remain empty on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=369207 --- Comment #1 from RJVB --- Created attachment 101235 --> https://bugs.kde.org/attachment.cgi?id=101235=edit screenshot of KDevelop running in native mode on OS X, showing the crippled Tools/Mode menu -- You are receiving this

[kate] [Bug 369207] New: Mode & Highlighting menus remain empty on Mac OS X

https://bugs.kde.org/show_bug.cgi?id=369207 Bug ID: 369207 Summary: Mode & Highlighting menus remain empty on Mac OS X Product: kate Version: 16.08 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED

[digikam] [Bug 368965] Crash when clicking on Table button in top menu bar [patch]

https://bugs.kde.org/show_bug.cgi?id=368965 --- Comment #5 from RJVB --- I haven't been able to reproduce this crash, but I'll incorporate it in my port. Thanks. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #21 from RJVB --- I'd have to figure out how to start a debugging session in lldb-mi manually, in order to check this correctly :) But: did you ever notice how starting the debugger on a C++ app using KDE or Qt takes so

[kdevelop] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #19 from RJVB --- Yes, at least as far as starting with a break in main goes. I didn't go much beyond testing that; lldb-mi-3.9 took so much memory when I tried with a simple Qt5 app that my whole plasma4 environment

[kde] [Bug 368928] New: crash while quitting KDevelop with a debug session still open

https://bugs.kde.org/show_bug.cgi?id=368928 Bug ID: 368928 Summary: crash while quitting KDevelop with a debug session still open Product: kde Version: unspecified Platform: unspecified OS: Linux

[kdevelop] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #17 from RJVB --- Thanks, but I just found the reason when I tried a manual debugging session. Turns out it's more a bug in the lldb-3.9 package: it doesn't install non-versioned binaries, but it wants an lldb-server

[kate] [Bug 368905] New: a shell is started even when the konsole plugin isn't loaded

https://bugs.kde.org/show_bug.cgi?id=368905 Bug ID: 368905 Summary: a shell is started even when the konsole plugin isn't loaded Product: kate Version: 16.08 Platform: Compiled Sources OS: All

[kate] [Bug 364807] KWrite does not sport its icon.

https://bugs.kde.org/show_bug.cgi?id=364807 RJVB changed: What|Removed |Added CC||rjvber...@gmail.com --- Comment #2

[kdevelop] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #15 from RJVB --- No, I didn't tick the "don't ask again option". I checked with an unpatched lldb 3.8.1 on OS X and I indeed got the warning in the debugger console, but IIRC everything else was functional. No, on

[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open

https://bugs.kde.org/show_bug.cgi?id=368568 RJVB changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #3 from RJVB

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #12 from RJVB --- (In reply to Aetf from comment #8) > Could you try if this works for you? It works in the sense that it rejects Apple-style version reporting ... With these hunks I get a functional LLDB plugin

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #11 from RJVB --- I'll try tomorrow, but how do you handle the case where you cannot determine the version of a perfectly acceptable lldb-mi? Again, the user may not have much choice to install a patched lldb-mi (think

[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open

https://bugs.kde.org/show_bug.cgi?id=368568 --- Comment #1 from RJVB --- Application: kdevelop5 (5.0.0) git v5.0.0-257-gff07af4 / v4.90.91-551-g4a90319 (Compiled from sources) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux

[kdevelop] [Bug 368568] Crash when quitting KDevelop with a patch review open

https://bugs.kde.org/show_bug.cgi?id=368568 RJVB changed: What|Removed |Added OS|OS X|All Version|5.0.0

[konversation] [Bug 364899] konversation5 crashes on exit

https://bugs.kde.org/show_bug.cgi?id=364899 RJVB changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[konversation] [Bug 368682] another konversation5 crash at exit

https://bugs.kde.org/show_bug.cgi?id=368682 --- Comment #1 from RJVB --- Happens on Linux too. In addition, DrKonqi insists that this is the same crash as the closed bug 364988, so that one wasn't fixed at all apparently. -- You are receiving this mail because: You are

[konversation] [Bug 368682] New: another konversation5 crash at exit

https://bugs.kde.org/show_bug.cgi?id=368682 Bug ID: 368682 Summary: another konversation5 crash at exit Product: konversation Version: unspecified Platform: Compiled Sources OS: OS X Status: UNCONFIRMED

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #7 from RJVB --- One more thought: I don't think you can expect that every user will have a patched lldb-mi anytime soon, so I'd advise to add a workaround like the one I posted. I don't really see any other way how you

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #6 from RJVB --- With the patch I get > lldb-mi-mp-3.9 (gdb) version ~"lldb-360.99.0\n" ^done (gdb) A year or two ago I asked about using the lldb-mi driver, on the lldb mailing list. I was told that the really

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #4 from RJVB --- No, I didn't apply that patch, I'm just running 3.9.0 (release). > lldb-mi-mp-3.9 --versionLong LLDB Machine Interface Driver (MI) All rights reserved Version: 1.0.0.9 Version: GNU gdb (GDB) 7.4 (This

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 RJVB changed: What|Removed |Added CC||7437...@gmail.com -- You are

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #2 from RJVB --- I think this happens because/when DebugSession::handleVersion() is called with an empty QStringList argument. Why that would happen I have no idea, possible it's related to commit

[kde] [Bug 368603] crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 --- Comment #1 from RJVB --- Backtrace on OS X : Backtrace of the crash I experienced: Application: KDevelop (kdevelop), signal: Segmentation fault: 11 (lldb) process attach --pid 32720 Process 32720 stopped Executable module set

[kde] [Bug 368603] New: crash when starting an lldb debug session

https://bugs.kde.org/show_bug.cgi?id=368603 Bug ID: 368603 Summary: crash when starting an lldb debug session Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #8 from RJVB --- (posted too fast) Wouldn't that give a hint at what's going here, i.e. "simply" a lack of persistence of the documentation view's settings? -- You are receiving this mail because: You are watching

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #7 from RJVB --- Well, I thought I could simply work around this issue by removing the Documentation button from my toolbars. While that's true I have to repeat the action each time I restart KDevelop because that damn.

[frameworks-kio] [Bug 360488] dolphin with >=kde-frameworks-5.20 crashes when copy+paste file in same directory

https://bugs.kde.org/show_bug.cgi?id=360488 --- Comment #15 from RJVB --- That's an old KDE4 version! I can confirm that Dolphin 16.08.0 (with FWs 5.24.0) doesn't crash when doing a copy/paste of a file without changing directories. It pops up a warning that offers to give

[kdevelop] [Bug 368568] New: Crash when quitting KDevelop with a patch review open

https://bugs.kde.org/show_bug.cgi?id=368568 Bug ID: 368568 Summary: Crash when quitting KDevelop with a patch review open Product: kdevelop Version: 5.0.0 Platform: Compiled Sources OS: OS X Status: UNCONFIRMED

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

https://bugs.kde.org/show_bug.cgi?id=363473 --- Comment #20 from RJVB --- I've elaborated the patch a bit and submitted it for review: https://git.reviewboard.kde.org/r/128880/ -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

https://bugs.kde.org/show_bug.cgi?id=363473 --- Comment #19 from RJVB --- Created attachment 101017 --> https://bugs.kde.org/attachment.cgi?id=101017=edit many tabs, QtCurve with a Fusion QTabBar -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

https://bugs.kde.org/show_bug.cgi?id=363473 --- Comment #18 from RJVB --- Created attachment 101016 --> https://bugs.kde.org/attachment.cgi?id=101016=edit Many tabs, Breeze with a Fusion QTabBar -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

https://bugs.kde.org/show_bug.cgi?id=363473 --- Comment #17 from RJVB --- Created attachment 101015 --> https://bugs.kde.org/attachment.cgi?id=101015=edit Many tabs with the native Macintosh theme but the Fusion style for the QTabBar widget I think this may yet be the

[kdevelop] [Bug 363473] KDevelop should use a different tab bar widget for tabbed documents

https://bugs.kde.org/show_bug.cgi?id=363473 --- Comment #16 from RJVB --- (In reply to RJVB from comment #12) > It wouldn't be possible to force a specific widget style on one particular > widget class, perchance? Something like "QTabBar { style : Fusion }" ? In fact it is:

  1   2   3   >