[kdevelop] [Bug 369025] Relative paths in error output not recognized correctly when building in subdirectories
https://bugs.kde.org/show_bug.cgi?id=369025 --- Comment #4 from Frank Fischer --- Created attachment 153161 --> https://bugs.kde.org/attachment.cgi?id=153161&action=edit version 2 of example project -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 369025] Relative paths in error output not recognized correctly when building in subdirectories
https://bugs.kde.org/show_bug.cgi?id=369025 Frank Fischer changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Platform|Archlinux |Debian stable Version|5.0.0 |5.8.220403 Status|NEEDSINFO |REPORTED --- Comment #3 from Frank Fischer --- I've just tested the issue again, and I can still reproduce it. Note that you have to create the build-directory first (in my case /home/fifr/test/test_project_build) as Kdevelop does not create it for you if it does not exist. I've attached an archive of the example project I used. Note that it may contain some absolute path in the kdev4 project files, maybe they should be adapted to your local machine in order to reproduce the problem. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 345960] Forward sync in live preview points to wrong position if "Trim Margins" is set
https://bugs.kde.org/show_bug.cgi?id=345960 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e --- Comment #4 from Frank Fischer --- At least in version 2.99.2 (on my system) the bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 424663] Could not find a package configuration file provided by "Qt5X11Extras"
https://bugs.kde.org/show_bug.cgi?id=424663 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e --- Comment #1 from Frank Fischer --- I have the same problem on Debian Buster. It comes with Qt 5.11 so I need to compile Qt along kdesrc-build, but I get exactly the same error message. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416895] kdeinit5 crashes in KIO::SlaveBase::waitForAnswer() after return from suspend
https://bugs.kde.org/show_bug.cgi?id=416895 --- Comment #2 from Frank Fischer --- (In reply to Nate Graham from comment #1) > Would you be interested in submitting a patch to fix the issue, or at least > downgrade it to a warning? Sure, I could do this. However, I'm totally unfamiliar with the kio code and do not know whether just returning an error code is ok with the rest of the code. In particular, I do not know whether this would result in some kind of inconsistent or invalid internal state of the slave (are there some assumptions about the internal state? Is all code expected to reset internal date to some valid state in case of an error, e.g. by cancelling the active connection?). So, in any case I would need some assistance to verify whether my changes make sense. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416895] kdeinit5 crashes after return from suspend
https://bugs.kde.org/show_bug.cgi?id=416895 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 416895] New: kdeinit5 crashes after return from suspend
https://bugs.kde.org/show_bug.cgi?id=416895 Bug ID: 416895 Summary: kdeinit5 crashes after return from suspend Product: frameworks-kio Version: 5.66.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: HTTP Assignee: kdelibs-b...@kde.org Reporter: frank-fisc...@shadow-soft.de Target Milestone: --- Created attachment 125511 --> https://bugs.kde.org/attachment.cgi?id=125511&action=edit backtrace of crash Whenever I return my laptop from suspension (after a few minutes), kdeinit5 crashes with the attached backtrace. I think this is related to Bug 402646, but in my case the culprit seems to be from a http/dav connection (it could be a synchronization connection in the background for a calendar). I've tried to track down the bug a little. It seems that the function KIO::SlaveBase::waitForAnswer hits a qFatal if the received response type (or "command") is not the expected one. In particular, the syslog says kdeinit5[9992]: Fatal Error: Got cmd 77, while waiting for an answer! If I understand the code correctly, 77 means CMD_SPECIAL, which is not one of the expected commands checked by the call to "isSubcommand", hence the qFatal is hit. I can only speculate what the reason is, but I would suspect some kind of race condition (caused by the suspend), the received message belongs to some other request or so. Anyway, the main question to me is in this case ... why is there this qFatal? If the received message originates from a (potentially) external source (please forgive me if this assumption is wrong, I am not really familiar with the kio code), then any received message could contain garbage for whatever reason. So wouldn't it more sensible to return with an error instead of crashing the program? (i.e. replace the call to qFatal by "return -1" or so, so that it is the task of the caller to handle the error correctly) Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66 Qt Version: 5.14.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 390798] Akonadi EWS failed to authenticate with Exchange Server
https://bugs.kde.org/show_bug.cgi?id=390798 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404234] plasmoid previews not working
https://bugs.kde.org/show_bug.cgi?id=404234 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369141] svn commands fail in path containing spaces
https://bugs.kde.org/show_bug.cgi?id=369141 Frank Fischer changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Frank Fischer --- No, it seems to work now. Thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388036] Include support for autocrypt
https://bugs.kde.org/show_bug.cgi?id=388036 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 386507] Caldav and Carddav sync does not work
https://bugs.kde.org/show_bug.cgi?id=386507 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 380058] Option to hide command messages (like topic and mode messages) from channel buffers
https://bugs.kde.org/show_bug.cgi?id=380058 --- Comment #2 from Frank Fischer --- I can do this. But this was not meant to be a patch, just an illustration what I did as a quick hack. I rather thought to start a discussion whether my requested feature should be implemented and how, and then I could try to craft a proper patch. But maybe phabricator is the right place to do this? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 380058] Option to hide command messages (like topic and mode messages) from channel buffers
https://bugs.kde.org/show_bug.cgi?id=380058 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 380058] New: Option to hide command messages (like topic and mode messages) from channel buffers
https://bugs.kde.org/show_bug.cgi?id=380058 Bug ID: 380058 Summary: Option to hide command messages (like topic and mode messages) from channel buffers Product: konversation Version: 1.7.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: ignore Assignee: konversation-de...@kde.org Reporter: frank-fisc...@shadow-soft.de Target Milestone: --- Created attachment 105662 --> https://bugs.kde.org/attachment.cgi?id=105662&action=edit Patch to hide command messages from channel buffers. When entering a channel konversation shows several command messages like the topic, who set the topic, channel modes. These messages are also shown if the server connection is lost (e.g. due to suspend of the machine) and reestablished. As the channel modes and topics seldom change, the buffers (especially if they have low traffic) are just flooded with completely equal messages (if you use a laptop you might reconnect several times a day). AFAICT it is sufficient to modify `appendCommandMessageToChannel` and `appendCommandMessage` methods to get the desired behaviour. I have append a patch that hides these messages if the hide join/part option is set. Probably this is not the best option and one should add another configuration option to do the same. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e --- Comment #69 from Frank Fischer --- I agree, this should be fixed. I remember I had the same problem one or two years ago but both, calendar and contacts, used to work for me in the last months. However, both stopped to work approximately one month ago. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374898] Missing command line flag "-u" for the pull command.
https://bugs.kde.org/show_bug.cgi?id=374898 --- Comment #1 from Frank Fischer --- I'm not sure about this anymore. Apparently, git updates only files on pull that do not have any conflicts. Mercurial's pull -u, however, would force a merge (possibly leaving conflict markers in the file). According to the documentation of IDistributedVersionControl::pull, it should only get changes but do not merge them into the working tree. This is what mercurial's pull without -u would do. The difference to git is: - if there are no conflicts, "git pull" will move HEAD to the newly pulled change, "hg pull" will just get the changes but does not update working tree - if there are conflicts, "git pull" will just fail, leaving HEAD at its old position In my opinion (and according to the documentation of IDistributedVersionControl::pull), the plain "hg pull" (without -u) is the correct thing to do, and the implementation for "git pull" should rather be "git fetch" (but does this make sense because one would have to use FETCH_HEAD to refer to the newly pulled changes?). I'm not sure here, maybe the difference is just fine and necessary because of the differences between git and hg. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374904] Error cases of sub-jobs in MercurialPushJob and MercurialAnnotateJob not handled properly
https://bugs.kde.org/show_bug.cgi?id=374904 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374904] New: Error cases of sub-jobs in MercurialPushJob and MercurialAnnotateJob not handled properly
https://bugs.kde.org/show_bug.cgi?id=374904 Bug ID: 374904 Summary: Error cases of sub-jobs in MercurialPushJob and MercurialAnnotateJob not handled properly Product: kdevplatform Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: mercurial Assignee: kdevelop-bugs-n...@kde.org Reporter: frank-fisc...@shadow-soft.de Target Milestone: --- The signals `readyForParsing` as well as `resultsReady` of a DVcsJob might only be emitted if the process exits normally, i.e. if the process does not crash, if it exits with code 0 or if it exits with some code != 0 and DVcsJob::setIgnoreError(false) had been called (because of the implementation of DVcsJob::slotProcessExited). However, the class MercurialPushJob only connects to the signal `readyForParsing`, thus it may not recognize if one of the sub-jobs crashed/fails. I suggest to connect to the signal `KJob::finished` in all cases to catch errors properly (and call MercurialPushJob::setFail() then). I think the same problem exists in MercurialAnnotateJob. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374898] Missing command line flag "-u" for the pull command.
https://bugs.kde.org/show_bug.cgi?id=374898 Frank Fischer changed: What|Removed |Added Version|unspecified |git master -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374898] Missing command line flag "-u" for the pull command.
https://bugs.kde.org/show_bug.cgi?id=374898 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374897] Wrong test for empty locations after directory filtering in MercurialPlugin::add
https://bugs.kde.org/show_bug.cgi?id=374897 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374898] New: Missing command line flag "-u" for the pull command.
https://bugs.kde.org/show_bug.cgi?id=374898 Bug ID: 374898 Summary: Missing command line flag "-u" for the pull command. Product: kdevplatform Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mercurial Assignee: kdevelop-bugs-n...@kde.org Reporter: frank-fisc...@shadow-soft.de Target Milestone: --- The git plugin uses the command "git pull" for implementing the pull method. This command gets new revisions from remote and updates the working tree accordingly. In contrast, mercurial's "hg pull" merely fetches remote changes without updating the working tree. Updating the working tree can be done by adding the "-u" flag to the pull command. (However, I'm not sure whether the ::pull method is supposed to update the working tree, but I think so). Actually, "git pull" means "git fetch" plus "git merge FETCH_HEAD", so maybe it's even better to use "hg fetch", but this is marked as deprecated. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 374897] New: Wrong test for empty locations after directory filtering in MercurialPlugin::add
https://bugs.kde.org/show_bug.cgi?id=374897 Bug ID: 374897 Summary: Wrong test for empty locations after directory filtering in MercurialPlugin::add Product: kdevplatform Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: mercurial Assignee: kdevelop-bugs-n...@kde.org Reporter: frank-fisc...@shadow-soft.de Target Milestone: --- The condition `if (localLocations.empty())` in method MercurialPlugin::add (line 201 in the current master) should probably be `if (locations.empty())` (as it is in many other methods). -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 308613] kile removes trailing space when it saves automatically for live preview
https://bugs.kde.org/show_bug.cgi?id=308613 Frank Fischer changed: What|Removed |Added CC||frank-fischer@shadow-soft.d ||e --- Comment #2 from Frank Fischer --- Today I realized that this problem reappeared: Kile consistently removes the space I've just (half a second ago) typed left to the cursor when saving the document due to live-previews. This is really annoying (for me) and I had to disable the removal of trailing whitespaces. I'm not sure if this is the right place for the bug-report, though. Certainly it's part of the behaviour of katepart, but it is also an unfortunate interaction of kate's whitespace-removal-feature and the automatic saving of kile due to live-preview. The comments in the bug report of katepart do not seem to discuss the case of automatic saving (only frequent pressing of Ctrl-S). -- You are receiving this mail because: You are watching all bug changes.
