[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Venca B Spam changed: What|Removed |Added CC||vbs...@centrum.cz -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483349] KDE Neon User (stable) printing stopped working after update due to issues with cupsd-browsed
https://bugs.kde.org/show_bug.cgi?id=483349 Venca B Spam changed: What|Removed |Added Resolution|WORKSFORME |REMIND --- Comment #15 from Venca B Spam --- I found great workaround. If you want to use stable Plasma while keeping your laptop up-to-date, switch to Kubuntu 24.04. It has Plasma 5, same as Neon had before switched to Plasma 6, and it is significantly faster! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484018] KDE Plasma in Wayland does not support Drag and Drop operations from Dolphin to Chromium (and Firefox).
https://bugs.kde.org/show_bug.cgi?id=484018 --- Comment #6 from Venca B Spam --- I found great workaround. If you want to use stable Plasma while keeping your laptop up-to-date, switch to Kubuntu 24.04. It has Plasma 5, same as Neon had before switched to Plasma 6, and it is significantly faster! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 485122] Latte Dock stopped working after update to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485122 --- Comment #1 from Venca B Spam --- I found great workaround. If you want to use stable Plasma while keeping your laptop up-to-date, switch to Kubuntu 24.04. It has Plasma 5, same as Neon had before switched to Plasma 6, and it is significantly faster! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483349] KDE Neon User (stable) printing stopped working after update due to issues with cupsd-browsed
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #14 from Venca B Spam --- It does not work at all.V On Wed 24. 4. 2024 at 5:47, Bug Janitor Service wrote: https://bugs.kde.org/show_bug.cgi?id=483349 Bug Janitor Service changed: What |Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 485122] New: Latte Dock stopped working after update to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485122 Bug ID: 485122 Summary: Latte Dock stopped working after update to Plasma 6 Classification: Plasma Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: vbs...@centrum.cz Target Milestone: --- SUMMARY Latte Dock stopped working after update to Plasma 6 I haven found any meaningful substitution to Latte Dock in Plasma 6. Or did I miss something? STEPS TO REPRODUCE 1. pkcon update 2. reboot 3. login OBSERVED RESULT Latte Dock shall start as usually. EXPECTED RESULT Latte Dock no longer start. The system is lacking application launchers. SOFTWARE/OS VERSIONS BEFORE UPDATE Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: X11 AFTER UPDATE Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427799] Conflict between autohide panel and switch desktop on edge
https://bugs.kde.org/show_bug.cgi?id=427799 Venca B Spam changed: What|Removed |Added CC||vbs...@centrum.cz --- Comment #4 from Venca B Spam --- I have the same problem. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: X11 Processors: 20 × 12th Gen Intel® Core™ i7-12700H Memory: 31,0 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Dell Inc. Product Name: Precision 5570 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483349] KDE Neon User (stable) printing stopped working after update due to issues with cupsd-browsed
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #11 from Venca B Spam --- (In reply to Carlos De Maine from comment #10) > is this still an issue? i can print out of the box on the latest user iso. It still does not work. However good news is that I found a way how to prevent my other systems from unwanted upgrades to Plasma 6 :) I am still open to test possible fixes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484018] New: KDE Plasma in Wayland does not support Drag and Drop operations from Dolphin to Chromium (and Firefox).
https://bugs.kde.org/show_bug.cgi?id=484018 Bug ID: 484018 Summary: KDE Plasma in Wayland does not support Drag and Drop operations from Dolphin to Chromium (and Firefox). Classification: Applications Product: dolphin Version: 23.08.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: vbs...@centrum.cz CC: kfm-de...@kde.org Target Milestone: --- SUMMARY KDE Plasma in Wayland does not support Drag and Drop operations from Dolphin to Chromium (and Firefox). STEPS TO REPRODUCE 1. Login to KDE Plasma with Wayland 2. Open web page accepting upload files with Drag and Drop in Chromium (or Firefox) 3. Open Dolphin folder where there is at least one readable file 4. Drag and drop that file to the web page area which accepts uploads OBSERVED RESULT Chromium does not upload the file, instead acts like it download such file. EXPECTED RESULT Drag and Dropped file shall be accepted by the upload area in the web page SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-17-generic (64-bit) ADDITIONAL INFORMATION When tested on graphics platform X11 everything works well. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 483349] KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #8 from Venca B Spam --- (In reply to Venca B Spam from comment #7) > (In reply to Nate Graham from comment #4) > > Thanks. Do you still see your previously-configured printer in the printers > > list of the Print dialog? > > > > If so, can you make sure that printer is selected when you click "Print"? > > > > If it is, after you click print, can you click on the Printers widget in > > your System Tray and see what it says next to the icon for your printer? In > > particular, the subtitle should say something. Either "Idle" or some other > > status. > > I tried both, the default and the newly added. > > In case of the default printer: > "Paused" (it is possible to click on Resume) after clicking on it it says > "Printer disappeared or cups/browsed for printer HP > "Color_LaserJet_Pro_M478f_9f_CENSORED", is cups-browsed running?" > > In case of the newly added: > "In use" for a while and then "gziptoany ..." and then "Paused - Printer > disappeared or cups-browsed shutdown" (it is possible to click on Resume) > after click "Connecting to printer" and then "Paused" then it cycles when > clicking on Resume. When I put the printer's IP address to browser it shows normally the printer's web interface. So I assume the printer must be accessible also for cups. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 483349] KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #7 from Venca B Spam --- (In reply to Nate Graham from comment #4) > Thanks. Do you still see your previously-configured printer in the printers > list of the Print dialog? > > If so, can you make sure that printer is selected when you click "Print"? > > If it is, after you click print, can you click on the Printers widget in > your System Tray and see what it says next to the icon for your printer? In > particular, the subtitle should say something. Either "Idle" or some other > status. I tried both, the default and the newly added. In case of the default printer: "Paused" (it is possible to click on Resume) after clicking on it it says "Printer disappeared or cups/browsed for printer HP "Color_LaserJet_Pro_M478f_9f_CENSORED", is cups-browsed running?" In case of the newly added: "In use" for a while and then "gziptoany ..." and then "Paused - Printer disappeared or cups-browsed shutdown" (it is possible to click on Resume) after click "Connecting to printer" and then "Paused" then it cycles when clicking on Resume. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 483349] KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #6 from Venca B Spam --- (In reply to Nate Graham from comment #4) > If so, can you make sure that printer is selected when you click "Print"? It is automatically selected (it is default printer) -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 483349] KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #5 from Venca B Spam --- (In reply to Nate Graham from comment #4) > Thanks. Do you still see your previously-configured printer in the printers > list of the Print dialog? Yes -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 483349] KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #3 from Venca B Spam --- (In reply to Venca B Spam from comment #2) >1. Open PDF in Okular2. Ctrl+P3. Click Print >Printed documet shall appear in the printer. >Sadly, nothing happens. >On Wed 13. 3. 2024 at 23:01, Nate Graham >wrote: > > https://bugs.kde.org/show_bug.cgi?id=483349 > > Nate Graham changed: > > What |Removed |Added > > > Product|plasmashell |print-manager > CC| |n...@kde.org > Component|general |general > Version|master |unspecified > Target Milestone|1.0 |--- > Resolution|--- |WAITINGFORINFO > Assignee|plasma-b...@kde.org |dantt...@gmail.com > Status|REPORTED |NEEDSINFO > Keywords| |regression > > --- Comment #1 from Nate Graham --- > Can you please be specific about what you mean with "Printing does > not work"? > What specifically does not work, and in what app? > > -- > You are receiving this mail because: > You reported the bug. Steps to reproduce "printing does not work" 1. Open PDF in Okular 2. Ctrl+P (open print dialog, select printer or use default printer; both variants give same result) 3. Click Print Printed document shall appear in the printer. Sadly, nothing happens. On other laptop, with the same distro, same level of updates, same printer on the same network just without the recent Plasma 6x update prints like I am used to for past two years. -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 483349] KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 --- Comment #2 from Venca B Spam --- 1. Open PDF in Okular2. Ctrl+P3. Click Print Printed documet shall appear in the printer. Sadly, nothing happens. On Wed 13. 3. 2024 at 23:01, Nate Graham wrote: https://bugs.kde.org/show_bug.cgi?id=483349 Nate Graham changed: What |Removed |Added Product|plasmashell |print-manager CC| |n...@kde.org Component|general |general Version|master |unspecified Target Milestone|1.0 |--- Resolution|--- |WAITINGFORINFO Assignee|plasma-b...@kde.org |dantt...@gmail.com Status|REPORTED |NEEDSINFO Keywords| |regression --- Comment #1 from Nate Graham --- Can you please be specific about what you mean with "Printing does not work"? What specifically does not work, and in what app? -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483349] New: KDE Neon User (stable) printing stopped working after update
https://bugs.kde.org/show_bug.cgi?id=483349 Bug ID: 483349 Summary: KDE Neon User (stable) printing stopped working after update Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: vbs...@centrum.cz CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY After "apt dist-upgrade" in KDE Neon User (stable) printing stopped working. Existing printer has weird name. Adding and removing printer does not fix the printing. STEPS TO REPRODUCE 1. Install KDE Neon User stable edition (KDE neon 5.27) 2. Configure printing 3. Check if printing works (it shall/will work) 4. Do apt dist-upgrade OBSERVED RESULT Printing does not work. Existing printer has weird name. Adding and removing printer does not fix the printing. EXPECTED RESULT Printing shall work even after update. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I also noticed that the UI is a bit weird, specially font sizes are mixed (big and small texts/fonts), dialog sizes are also weird. Overall the UI looks unorganized. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 --- Comment #7 from Venca B Spam --- It hits me again! After update of my Neon I received Plasma 5.19. Same symptoms. Workarounds: 1) Use of previously backed up wallet can fix the thing. 2) Otherwise you can use the steps in my previous comment, you just need to find the system "affected" by the bug, to be able export your wallet to XML. Feedback to your teams: How hard would be to provide corrupted data migration (e.g. test the password for both variants, if it works, convert the wallet). I understand it is not possible when you do not know about the bug, however in this second case the migration should be part of the solution. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 --- Comment #2 from Venca B Spam --- This might be related to this issue https://bugs.kde.org/show_bug.cgi?id=416461 . They however also deal with problem with unlocking of the KWallet on login, which in this case works, after fixing the wallet password. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 416461] [5.18] KDE wallet not unlocked on login
https://bugs.kde.org/show_bug.cgi?id=416461 Venca B Spam changed: What|Removed |Added CC||vbs...@centrum.cz --- Comment #25 from Venca B Spam --- This issue might be related to this one #421856 https://bugs.kde.org/show_bug.cgi?id=421856 which I reported a minute ago. The referred problem is however that the KWallet does not accept the correct password at all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 --- Comment #1 from Venca B Spam --- There is workaround how to save your data. Let's have another system with Neon, just without the latest update/upgrade, call it healthy. Take the kdewallet.kwl kdewallet.salt and copy it over the healthy system files. Open KWallet manager on the healthy system and enter the correct password to open it. Export the opened wallet to XML (e.g. recovered_wallet.xml) . Go to the sick system, delete the kdewallet.kwl kdewallet.salt and restart the system. Once you login on the sick system, open the KWallet manager and import the "recovered_wallet.xml". This should fix the thing. Hope it saves other people, as this critical issue can't be prevented by any backups or archives at all. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 421856] New: KWallet does not accept correct password
https://bugs.kde.org/show_bug.cgi?id=421856 Bug ID: 421856 Summary: KWallet does not accept correct password Product: frameworks-kwallet Version: 5.18.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: va...@kde.org Reporter: vbs...@centrum.cz CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Let's have Neon testing fully working. The KWallet is used to store all your passwords. The KWallet is configured to be automatically unlocked after login. STEPS TO REPRODUCE 1. Update your system by 'apt dist-upgrade' 2. Restart the system 3. Login as usually OBSERVED RESULT The KWallet prompts you to enter password to kwallet. Even when you enter the correct password, it responds with message "Error code -9: Read error - possibly incorrect password." EXPECTED RESULT The system should not forget all my passwords after update/upgrade. SOFTWARE/OS VERSIONS Operating System: KDE neon Testing Edition KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 4.15.0-101-generic OS Type: 64-bit Wallet Manager: Version 20.04.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394790] New: Plasmashell process consumes huge amount of RAM after couple of days of running.
https://bugs.kde.org/show_bug.cgi?id=394790 Bug ID: 394790 Summary: Plasmashell process consumes huge amount of RAM after couple of days of running. Product: plasmashell Version: 5.12.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: vbs...@centrum.cz CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 112924 --> https://bugs.kde.org/attachment.cgi?id=112924&action=edit Script which kills plasmashell when system hits low memory threshold. Plasmashell process consumes huge amount of RAM after couple of days of running. I run the KDE Neon Ubuntu. When I do not reboot or re-login for day or two, the plasmashell process eats huge amount of memory. In my system with 16GB memory it is not obvious immediately, but my girlfriend has 12GB system and she suffers with this issue very frequently. It is even more annoying on systems with 4GB of RAM (e.g. my old laptop I use as home entertainment station). It is not obvious why is this happening. We almost not use GNOME apps (except some with no KDE alternatives). Basically we just use Thunderbird, Chromium browser, Inkscape, Gwenview, Gimp, Krita, VSCode and Nextcloud client. (For those who suffers this too, attached script kills plasmashell when system hits low memory threshold.Started when KDE starts does not slow the system and saves your work just before the system starts to be frozen. Can be targeted to other process, but plasmashell is in 90% the cause on my system and other processes may contain valuable data.) Unfortunately I did not find any way how to reproduce, I just install the default KDE Neon and work with the system for a day. It happens on any system I have at home. -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 393180] New: Feature request: Support webdavs:// protocol to play albums and music from Nextcloud
https://bugs.kde.org/show_bug.cgi?id=393180 Bug ID: 393180 Summary: Feature request: Support webdavs:// protocol to play albums and music from Nextcloud Product: elisa Version: 0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: vbs...@centrum.cz Target Milestone: --- Feature request: Support webdavs:// protocol to play albums and music from Nextcloud. Use case: Let's have a bookmarked place 'My Cloud Music' in Dolphin. The 'My Cloud Music' points to actual url which looks like 'webdavs://nextcloud.myserver.mydomain/nextcloud/remote.php/webdav/Media/My Albums/'. Bob wants to play Alice music: - Bob starts Elisa - Click on 'Add new path' - From the Open URL/location dialog selects the bookmarked place My Cloud Music' (optionally: inserts the url manually) (optionally advanced: or will browse for the url in special dialog) - Elisa will show to remote collection - Bob click on the album and it will start play same as local music -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389550] C/C++ language support sometimes fail to resolve included files when include file itself has never been included.
https://bugs.kde.org/show_bug.cgi?id=389550 --- Comment #3 from Venca B Spam --- The underlying cause of this issue may be related to the issue I already reported here https://bugs.kde.org/show_bug.cgi?id=387272 . -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389550] C/C++ language support sometimes fail to resolve included files when include file itself has never been included.
https://bugs.kde.org/show_bug.cgi?id=389550 --- Comment #2 from Venca B Spam --- Created attachment 110179 --> https://bugs.kde.org/attachment.cgi?id=110179&action=edit Sample project of LanguageSupportFailingScenario1 Added sample project of LanguageSupportFailingScenario1. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389550] C/C++ language support sometimes fail to resolve included files when include file itself has never been included.
https://bugs.kde.org/show_bug.cgi?id=389550 --- Comment #1 from Venca B Spam --- Created attachment 110178 --> https://bugs.kde.org/attachment.cgi?id=110178&action=edit Video of LanguageSupportFailingScenario1 Added video of LanguageSupportFailingScenario1. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 389550] New: C/C++ language support sometimes fail to resolve included files when include file itself has never been included.
https://bugs.kde.org/show_bug.cgi?id=389550 Bug ID: 389550 Summary: C/C++ language support sometimes fail to resolve included files when include file itself has never been included. Product: kdevelop Version: 5.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- C/C++ language support sometimes fail to resolve include files when include file itself has never been included. * How to reproduce? * 1. Download attached sample test case project 2. Follow steps on the video bug report attached. Shortly: - Start fresh new KDevelop session - Open the project attached and let the background parser finish its job - Open the include file "Bar/Bar.hpp" - Observe the line with "Thirdparty/Interface.hpp" inclusion * What happens? * Although the #include directive is correct in the context of the build system, KDevelop marks the line as not only problem (which is incorrect) it also do not use the "Thirdparty/Interface.hpp" for further language analyse. * What is expected? * Even if the include file is not actually never included, it should be properly parsed. KDevelop should not generate confusing false error positives. * Observation * When the include file "Bar/Bar.hpp" is included in another file (e.g. Foo.cpp), the problem disappears (demonstrated on the video attached). Also later when is such inclusion removed (from Foo.cpp) the problem does not reappear. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #25 from Venca B Spam --- Thank you for your feedback! While studying the KDevelop architecture I realized all you stated. I compared this with my user level (or call it business requirements) and I see the way how it is implemented in KDevelop as "a bit that the technical solution is exposed to the end user" - but I could be wrong and it may be an intentional effect. I compared how it is solved in QtCreator and I like it more there (they use absolute path as it is defined in the build system). However in general I still like KDevelop more - which keeps my attention to this issue :-). There are however more consequences of how the symlinks are handled in KDevelop. I reported another bug (https://bugs.kde.org/show_bug.cgi?id=387866#c5) where it is even more obvious that the canonicalized paths exposed to the end user is not perfect. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387866] KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
https://bugs.kde.org/show_bug.cgi?id=387866 --- Comment #5 from Venca B Spam --- It looks that at least the whole KTextEditor component of KF5/KDE is behaving weird - seeing from the end user perspective. Although I can see the point from the developer perspective. I looks like it always resolves symbolic links and exposes this to the user. I can understand that internally it is ok and maybe for many cases necessary. >From the user perspective it is however wrong approach. Why I thing this: Imagine my mother when I explain her,: Me: "Mom, here in your home folder e.g. /home/BestMomOnTheWorld/Documents there are all your Pie recipes." Mom: "U r great son!" ..after a while, I am at the gate leaving for holiday.. Mom is calling: "I am lost, I lost my recipes, it says something about /mnt/dataserver/mirror/raid5/diskXYZ/users/online/uuid12729837192347/Documents/best recipe on the world.txt, I believe I lost it, how can I prepare for tomorrow's party?!??" I did quick use case research and it looks that other frameworks do not propagate the resolved symlink path to the end users. Even QtCreator programmer tool properly assumes that the user wanted to not resolve the symlink in the interface. Any ideas? or am I wrong about this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 --- Comment #44 from Venca B Spam --- (In reply to Nate Graham from comment #43) > Can you reproduce the issue with an app that doesn't have spaces in the > name? If not, then the remaining issue may be > https://bugs.kde.org/show_bug.cgi?id=385942 For me this bug is already fixed. Also Libreoffice from Ubuntu 16.04 works ok. However as I am still receiving notifications, I noticed this suggestion that the libreoffice issue can be caused by space in the name. Quickly I did the test and it looks that space in the name cases this. I did test for LO and also for another app and both they suffered the behavior described here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387866] KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
https://bugs.kde.org/show_bug.cgi?id=387866 --- Comment #4 from Venca B Spam --- Created attachment 109355 --> https://bugs.kde.org/attachment.cgi?id=109355&action=edit SimpleSymlinkScenario5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387866] KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
https://bugs.kde.org/show_bug.cgi?id=387866 --- Comment #3 from Venca B Spam --- Created attachment 109354 --> https://bugs.kde.org/attachment.cgi?id=109354&action=edit How to reproduce video -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387866] KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
https://bugs.kde.org/show_bug.cgi?id=387866 --- Comment #2 from Venca B Spam --- Created attachment 109353 --> https://bugs.kde.org/attachment.cgi?id=109353&action=edit CMake server codemodel -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387866] KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
https://bugs.kde.org/show_bug.cgi?id=387866 --- Comment #1 from Venca B Spam --- Created attachment 109352 --> https://bugs.kde.org/attachment.cgi?id=109352&action=edit Video of JSON codemodel -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387866] New: KDevelop generates wrong project view tree when symbolic links are linked inside the project root.
https://bugs.kde.org/show_bug.cgi?id=387866 Bug ID: 387866 Summary: KDevelop generates wrong project view tree when symbolic links are linked inside the project root. Product: kdevelop Version: 5.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- KDevelop generates wrong project view tree when symbolic links are linked inside the project root. * How to reproduce: * 1. Open attached SampleSymlinkProject5/SampleSymlinkProject CMake project. 2. Let KDevelop parse it and then build it. 3. Browse the "project tool view" 4. Search for the location of the LibBar in the tree. Actual result: The "LibBar" is shown only as parrent of the "SomewhereInsideProjectRoot". Expected behavior: The LibBar should follow the buildsystem and should be shown as parent of the project root folder. Opinion: Also the LibBar should match the filesystem, so it should be shown twice, first as parent "SomewhereInsideProjectRoot/LibBar", second as parent of the project root folder "LibBar". Observation: As I am reporter of another symbolic links related bug https://bugs.kde.org/show_bug.cgi?id=387391 I observed that if the symbolic link is pointing to resource outside the project root, it is displayed properly as the user expects. Please see attached "How to reproduce video" for illustration. Also please see attached "CMake server codemodel" as a reference of how the project is expected to be shown from the build system perspective. I attached video of the JSON displayed in Firefox for convenience - please see "Video of JSON codemodel". -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #23 from Venca B Spam --- Created attachment 109341 --> https://bugs.kde.org/attachment.cgi?id=109341&action=edit Scenario with CMake and symbolic links INSIDE PROJECT which is BAD/FAILS. Added another test scenario covering symbolic links inside project. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #22 from Venca B Spam --- (In reply to Sven Brauch from comment #21) > Thank you very much for looking into this! Ideally, you could submit your > full patch to phabricator.kde.org, which is our usual platform for reviewing > changes. I am a bit confused by your github link, because the code you end > up with is exactly what I see in our current codebase ...? Thank you for your attention. The final change is just single line in plugins/cmake/cmakeserverimportjob.cpp which changes canonicalFilePath() call to absoluteFilePath(). (https://github.com/vbspam/kdevelop/commit/d1898acee23e8324a718414c5e4ccb0fcae0d460#diff-a96baafe1c9ef34cbcc5cbc05978cfaeR139). >From my point of view, even it pass all my test cases, it is not ready to submit due to the following reasons: a) needs some cleanup (variable names, remove comments) b) although I know why it works, I do not know why the original idea of Milian Wolff does not work with my test cases (https://github.com/vbspam/kdevelop/commit/e1500e1f) Please note, I put my changes to branch dev-387391, which I hope I properly link in this issue (at least it works on my laptop). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #20 from Venca B Spam --- Finally I found a solution to all my test cases. For anyone with better knowledge of KDevelop/KF/QT please check it here: https://github.com/vbspam/kdevelop/commit/550c6e1b6867598f372a68979c1ee7718ee2854c I put there some debugging messages to easily find out where I see the problem is. It looks that it is expected that canonicalFilePath is best to deal with symlinks. I see it as good argument, my debug messages however reveals that KDevelop uses absoluteFilePath in some cases. What is surprise to me is that my previous attempt to force use of "absoluteFilePath" (previous comment commit) sometimes caused more complex test cases did not worked. I guess it may be the IndexedString maid be malformed by my improper use of QT api. I would like to ask very politely anyone who will review it, please do not comment my use of the KF/QT API as I am absolute novice and just trying to help. The core of the issue is described in my bugreport and illustrated in the https://bugs.kde.org/attachment.cgi?id=109155. Also please note, the commit is just for discussion and tests. Should I propose merge/pull request, I will of course follow particular project rules. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 376612] There's no context-menu-driven way to unhide a hidden "Build Sequence" panel
https://bugs.kde.org/show_bug.cgi?id=376612 Venca B Spam changed: What|Removed |Added CC||vbs...@centrum.cz --- Comment #3 from Venca B Spam --- I can not find how to "hide" the "Build Sequence". How did you do it? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #19 from Venca B Spam --- As the previous post was false positive, the issue still annoys me. I did a bit investigation and it seems that changes I put here https://github.com/vbspam/kdevelop/commit/d1898acee23e8324a718414c5e4ccb0fcae0d460 solved most of my test cases (please skip my debug messages). Also please ignore changes in "plugins/custom-definesandincludes/compilerprovider/widget/compilerswidget.cpp" which are not related to this issue. Should I propose merge request, I will provide properly formed commits. I understand that the "canonicalFilePath" is probably native to KDevelop, but it does not work for symbolic links when resolving against CMake build system and also does not return properly "hasBuildSystemInfo" flag. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #18 from Venca B Spam --- The previous comment was false positive. It has still problem regardless the link is absolute or relative. (In reply to Venca B Spam from comment #17) > I have another observation :-). > > When the symbolic link is absolute, the issue does not show. > > So summary for now: > > The issue occurs *only* when relative symbolic links are employed. OK, this was false positive. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #17 from Venca B Spam --- I have another observation :-). When the symbolic link is absolute, the issue does not show. So summary for now: The issue occurs *only* when relative symbolic links are employed. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #16 from Venca B Spam --- The last sentence "This test pass ok." in comment before this one is Copy&Paste error. Of course that test case fails. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #15 from Venca B Spam --- Created attachment 109155 --> https://bugs.kde.org/attachment.cgi?id=109155&action=edit Scenario with CMake and symbolic links which is BAD/FAILS. I added another simplified scenario with CMake and symbolic links which shows the bug. This test case does use CMake project-in-project. It uses symbolic link to put external library to the 'master' project root dir which then add_subdirectory() into it. The bug shows in minimalistic case, when one browse the Bar.cpp. When one looks at Foo.cpp, it works well. It is also worth of mention, that the Bar.cpp can be temporarily 'fixed' when one execute following action: - RMB click on the project in the project tree view - from the context menu select and LMB click on 'Open Configuration' - select 'Language Support=>C/C++ Parser' - do some dummy change which will enable the 'Apply' button. (e.g. by changing and returning the 'Compiler for path' dropdown list) - press OK or Apply and then OK This will make the file Bar.cpp temporarily error free, when one insert/change any character in the editor, it will break aggain. This test pass ok. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #14 from Venca B Spam --- Created attachment 109154 --> https://bugs.kde.org/attachment.cgi?id=109154&action=edit Scenario with CMake and symbolic links which is OK I added simplified scenario with CMake and symbolic links which does not suffer with the bug. This test case does not use CMake project-in-project. It uses symbolic link just to put external library to common include directory. This test pass ok. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #13 from Venca B Spam --- Could it be caused by this? https://github.com/KDE/kdevelop/blob/master/plugins/cmake/cmakemanager.cpp#L246 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #10 from Venca B Spam --- What I can not explain is the: a) 'sometimes' it is invoked without proper -I include definitions which produces the expected issue described here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391
--- Comment #9 from Venca B Spam ---
Yes, I guess that it may be the issue. If the state machine (whatever logic)
expects the state has some meaning and it behaves a bit different it may have
unpredictable results.
In fact the symlink os API sometimes resolve symlinks sometimes do not. Symlink
itself is just inode pointing to another inode. Depends on how you watch files,
it may return results which may not be understandable for the parser.
I can imagine following:
string watch_inode_file( string file) {..}
when called:
auto result = watch_inode_file( "/path/to/project/symlinked_dir/file.cpp");
may return in result="/path/somewhere/else/symlinked_dir/file.cpp".
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #7 from Venca B Spam --- Ok, I did the test and it looks even weirdest then before. I also enabled the KDEV_CLANG_DISPLAY_ARGS=1 to see how the Clang is being invoked. Observations: a) 'sometimes' it is invoked without proper -I include definitions which produces the expected issue described here. b) 'sometimes' it is invoked WITH proper -I which gives proper output just with some linking issues (I assume it does not break the think) c) however 'sometimes' even it was initially OK (see the bullet b) above), when I press e.g. " " (space) in the editor, the editor changes the hint/parsing to error. What is really weird here is, that I do not see any Clang invocation nor even attempt to run Clang (at the moment I pressed the keyboard " " - could be any character triggering the dirty save flag) Summary: - The change to from ok to an error state changes without Clang invocation - It may start with an error state on the beginning based on Clang output which correctly generate the error as it do not get proper -I includes on argument line. Is there any debug environment variables I can use to enable logs to observe the parser loop/events? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #6 from Venca B Spam --- Thank you for your advice, I will try it. I know how to change the project to work well. It is as simple as to replace symbolic links by their targets . In other words, if the project does not contain symbolic links and all folders are 'at-the-place' everything works well. I guess it will be in some kind of evaluation of paths if they fit to some pattern. If it does not, e.g. if the include path is outside the project root, it may be excluded, even it is valid - but it is just guessing. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #4 from Venca B Spam --- I added short clip/video of how to reproduce the bug. If would be cool if anyone has an idea where to look at into the code :-). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #3 from Venca B Spam --- Created attachment 109144 --> https://bugs.kde.org/attachment.cgi?id=109144&action=edit How to reproduce bug - video illustration -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #2 from Venca B Spam --- I did not mentioned that the attached scenario assumes Linux operating system environment as it uses call to 'ln' executable (at this moment does not support Windows mklink). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 --- Comment #1 from Venca B Spam --- Created attachment 109090 --> https://bugs.kde.org/attachment.cgi?id=109090&action=edit ComplexSampleScenario -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387391] New: Random responses from the C/C++ language support when using symbolic links to CMake sub-projects.
https://bugs.kde.org/show_bug.cgi?id=387391 Bug ID: 387391 Summary: Random responses from the C/C++ language support when using symbolic links to CMake sub-projects. Product: kdevelop Version: 5.2.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- Random responses from the C/C++ language support when using symbolic links to CMake sub-projects. * How to reproduce? * 1. Open/Import attached CMake project located in ComplexSampleScenario/Projects/SampleMultiProject folder of attached archive. 2. Let KDevelop parse the project. 3. Browse the code specially files ClassA1.cpp, ClassB1.cpp, SubProjectExecutable1.cpp. * What happens? * The language support randomly shows error/warning hints in files ClassA1.cpp, ClassB1.cpp. * What is expected? * The language support should not show error/warning hints in files ClassA1.cpp, ClassB1.cpp as they are valid and the project definition provides proper include paths to build those files. * Notes/Observations* - When SubProjectLibraryA and SubProjectLibraryB is not sym-linked KDevelop language support works well (without random error/warning hints) - Sometimes files ClassA1.cpp, ClassB1.cpp does not show errors initially, later when user just press space " " keeping the file compilable, KDevelop language support changes its state and shows error/warning hints -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387272] Weird warning/error hint from the code browser - missing header guard when one present.
https://bugs.kde.org/show_bug.cgi?id=387272 --- Comment #4 from Venca B Spam --- Yes, you are right! Just tested right now. Ok, is this a bug? I still think that it is. I have more bugs like this, some more complex (e.g. After project is loaded everything is ok, when I do simple correct code change, it breaks and reports many warning/error hints). Is there any way how to get more debugging messages (e.g. how to enable extended debug messages or so)? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387272] Weird warning/error hint from the code browser - missing header guard when one present.
https://bugs.kde.org/show_bug.cgi?id=387272 --- Comment #2 from Venca B Spam --- Created attachment 109041 --> https://bugs.kde.org/attachment.cgi?id=109041&action=edit Sample project used to reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387272] Weird warning/error hint from the code browser - missing header guard when one present.
https://bugs.kde.org/show_bug.cgi?id=387272 --- Comment #1 from Venca B Spam --- Created attachment 109040 --> https://bugs.kde.org/attachment.cgi?id=109040&action=edit How to reproduce bug - video -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387272] New: Weird warning/error hint from the code browser - missing header guard when one present.
https://bugs.kde.org/show_bug.cgi?id=387272 Bug ID: 387272 Summary: Weird warning/error hint from the code browser - missing header guard when one present. Product: kdevelop Version: 5.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- Weird warning hint from the code browser - missing header guard when one present. It looks like some CMake based projects does not work well with KDevelop Clang based C/C++ language support. This is just one bug I noticed from many, which is however easy to reproduce, so I report it separately. * How to reproduce? * 1. Open attached SampleMultiProject. 2. In the project tree view click on the file ClassB.hpp (in SubProjectExecutable/include). 3. Put a mouse cursor to the first line of the file on the text "#pragma once" * What happens? * There is "warning/error" hint on the first line of the file in the editor (red underline) with following text "The given header is not guarded against multiple inclusions, either with the conventional #ifndef/#define/#endif macro guards or with #pragma once." * Expected behavior? * The correct use of language element should not be reported as warning/error. * Observations / Notes * - Please see attached video of the bug behavior. - Weird is that another file with similar contents do not show the bug - Even weirdest is that when I retype (cut&paste) the text "#pragma once" the problem disappears. - I did double check the CMake project for problems, but I did not find any which may cause this behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387249] KDevelop Language support C/C++ compilers UI crashes when clicked on manually added compiler.
https://bugs.kde.org/show_bug.cgi?id=387249 --- Comment #1 from Venca B Spam --- Created attachment 109029 --> https://bugs.kde.org/attachment.cgi?id=109029&action=edit How to reproduce bug with some debugger output. Added video showing how to reproduce the bug with some debugger output. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387249] New: KDevelop Language support C/C++ compilers UI crashes when clicked on manually added compiler.
https://bugs.kde.org/show_bug.cgi?id=387249
Bug ID: 387249
Summary: KDevelop Language support C/C++ compilers UI crashes
when clicked on manually added compiler.
Product: kdevelop
Version: 5.2.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: UI: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: vbs...@centrum.cz
Target Milestone: ---
KDevelop Language support C/C++ compilers UI crashes when clicked on manually
added compiler.
* How to reproduce? *
1. Start KDevelop, manually add Clang compiler (Settings=>Language
support=>C/C++ compilers)
2. Close KDevelop
3. Start KDevelop
4. Open "Settings=>Language support=>C/C++ compilers"
5. Click on previously added compiler.
* What happens? *
- KDevelop crashes.
* Expected behavior? *
KDevelop should allow to edit the compiler record.
* Observations / Notes*
- KDevelop crashes on the line
"kdevelop/plugins/custom-definesandincludes/compilerprovider/widget/compilerswidget.cpp:177".
It looks it crashes on calling "indexes.first()" event there is an assert two
lines above guarding the "indexes" not to be empty.
- Backtrace shows following locals:
```code
(gdb) info local
indexes = {> = {}, {p =
{static shared_null = {ref = {atomic = {_q_value = {> =
{static _S_alignment = 4, _M_i = -1}, }}}, alloc = 0, begin =
0, end = 0, array = {0x0}}, d = 0x152eb80}, d = 0x152eb80}}
compiler =
```
- It happens at least in KDevelop 5.1.x to 5.2.x including my home build made
from recent git sources.
- Also please see attached video for how to reproduce and some GDB output.
- Anyway it is not clear what is this Compilers for. ?
- Also do not understand why it always selects GCC as autodetected when my
system uses Clang as default. ?
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 387246] New: Add support for .gitignore like project treeview items exclusion.
https://bugs.kde.org/show_bug.cgi?id=387246 Bug ID: 387246 Summary: Add support for .gitignore like project treeview items exclusion. Product: kdevelop Version: 5.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- This is feature request. Add support for .gitignore like project treeview items exclusion. Although I know there is possibility to exclude items from the project tree view, I see it as a bit not practical for even a bit larger projects (I can provide examples on demand) as it require too much attention from the user. First I was thinking to ask to support .gitignore itself, but this does not have the same business requirement base. What about to have the same syntax as .gitignore (easy to parse and interpret) and just add these patterns to already existing project exclusion list of items. Minimal use case: - User will create .kdevignore and will populate it by its own patterns - User will open/import CMake project and the files will be automatically ignored. - User still can add new excluded items which will be stored the same way as today (in the project file). By the way, as I am new to KDE, is there any other more suitable place to discuss feature requests, ideas? (I did try KDE forum but it looks a bit less crowded.) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] CMake subprojects lead to duplicated targets in project model
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #11 from Venca B Spam --- I can confirm that in my own KDevelop builld (5.2.40 c2f9b5) it works well now. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #8 from Venca B Spam --- Although it looks to me now as a bit more complex design issue, the KDevelop release 5.1.x was ok, at least from the user experience perspective. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #7 from Venca B Spam --- Created attachment 108968 --> https://bugs.kde.org/attachment.cgi?id=108968&action=edit Illustration of multiproject-cmake-server-response JSON I am not sure if the CMake output is wrong. It looks they want to keep scopes. The thing is that this technique "project-in-project" is completely legal in CMake. The core issue here is that in CMake you can have multiple projects in a single build system. Looks like KDevelop idea of a "project" does not match the CMake one. In order to make the issue easier to understand please see attached screenrecording of the JSON response. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #5 from Venca B Spam --- I did some investigation and it seems that the CMake project is ok. It contains exactly what I would expect. There is however one clue which may help to find out what changed in KDevelop interpretation of the CMake output. I noticed that the "superproject" contains all targets of all "subprojects". And all "subprojects" they contain their targets as one would expect. As the superproject contains all subprojects' targets, they are in the fact in the CMake server "codemodel" reply twice. For details please see attached https://bugs.kde.org/attachment.cgi?id=108966 saved JSON response (Firefox can be used to visualize the file). I go for bisect now, however if anyone has an idea where to look to, would be nice? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #4 from Venca B Spam --- Created attachment 108966 --> https://bugs.kde.org/attachment.cgi?id=108966&action=edit Multiproject parsed by CMake server -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #3 from Venca B Spam --- Created attachment 108957 --> https://bugs.kde.org/attachment.cgi?id=108957&action=edit Bug report illustration -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #2 from Venca B Spam --- Created attachment 108956 --> https://bugs.kde.org/attachment.cgi?id=108956&action=edit SampleProject -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 --- Comment #1 from Venca B Spam --- Created attachment 108955 --> https://bugs.kde.org/attachment.cgi?id=108955&action=edit SampleMultiProject -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387095] New: Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice.
https://bugs.kde.org/show_bug.cgi?id=387095 Bug ID: 387095 Summary: Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice. Product: kdevelop Version: 5.2.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: CMake Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- Since KDevelop 5.2.x release CMake target items in the project tree view are shown twice. *How to reproduce?* 1. Open attached sample project "SampleMultiProject". 2. Build it. 3. Observe project tree view. *What happens?* There is doubled representation shown next to each other of each CMake generated target. *Expected behavior?* There should be single representation of each CMake generated target. *Notes:* - The test case applied to simple scenario does not suffer this bug. Please see attached "SampleProject". Although it may disqualify this bug report, but I do not see any CMake related issue with the multiproject case. - Also the previous 5.1.x releases did not suffered by this bug. - My system is using Clang 5.x/6.x, CMake 3.8 with server support, KDevelop 5.2.0 (also tested with recent homemade build from sources 5.2.40.) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] C++ include path completion misses system include path completion
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #15 from Venca B Spam --- I did compile the commit 015141e38b795b6c8ff9fe616e87cf0a55065406 and I can confirm that now it works. Even with the simplification described in the commit message, it works for my everyday work. In the meantime I did started learning how it works while trying to fix it. It helped me understand some part of KDevelop. Thank you all! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] IDefinesAndIncludesManager does not differentiate system and local includes (-isystem vs -I) retrieved from the build system, causing issues with C++ code completion
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #8 from Venca B Spam --- Is there a way how I can help? I cloned KDevelop just for fun and learning, trying to find out how is designed. Later after some difficulties also compiled it. Are there any design diagrams (sysml/uml/or just ideas on paper)? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #6 from Venca B Spam --- Ok, I got it. I have observation that in some cases when the include is already written e.g. ```code #include ``` The included file can be "clicked-through" (Ctrl+LMB on the included file) which will open the file. Is this evaluated by different process/principle? This observation gives me still some home.. :-) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #4 from Venca B Spam --- I did not dig into details (yet) however I was thinking that as long as KDevelop is using Clang as backend for C++ language support (code completion & friends), it does not play a role. I mean, if the Clang call for particular project/file is using proper flags/parameters, then KDevelop should receive proper expansion/evaluation of the completion query. Or am I completely wrong? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 Venca B Spam changed: What|Removed |Added Version|5.1.80 |5.2.0 --- Comment #2 from Venca B Spam --- I tested KDevelop 5.2.0 from Neon packages today and it still do not work properly. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 --- Comment #1 from Venca B Spam --- Created attachment 108662 --> https://bugs.kde.org/attachment.cgi?id=108662&action=edit Sample project required to reproduce reported behavior. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386421] New: KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects.
https://bugs.kde.org/show_bug.cgi?id=386421 Bug ID: 386421 Summary: KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects. Product: kdevelop Version: 5.1.80 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: vbs...@centrum.cz Target Milestone: --- Created attachment 108661 --> https://bugs.kde.org/attachment.cgi?id=108661&action=edit Bug report illustration KDevelop C++ code completion does not respect user defined system-wide include directories in CMake projects. Please see attached illustration video. *How to reproduce?* 1. Open attached sample project. 2. Build it. 3. Open file "SampleLibraryStuff.cpp" 4. On top of that file try to type "#include
