[dolphin] [Bug 488775] New: The last open tabs are not kept after restart
https://bugs.kde.org/show_bug.cgi?id=488775 Bug ID: 488775 Summary: The last open tabs are not kept after restart Classification: Applications Product: dolphin Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open more folders, each of them in a separate tab 2. Quit Dolphin 3. Run Dolphin OBSERVED RESULT The tabs are not kept after Dolphin restart even if this action is marked in Dolphin Settings EXPECTED RESULT Restore last open tabs SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux OS: MX23.3 XFCE. Qt Version: ADDITIONAL INFORMATION Dolphin was installed using Flathub. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 --- Comment #3 from Silviu --- The same behavior is for Kompare. Both application were installed using flatpak: sudo flatpak install -y flathub org.kde.kdiff3 sudo flatpak install -y flathub org.kde.kompare When I saw that the /home/user_name folder is seed as empty even if this is not empty and /media folder can't be seen, I tried using next commands: sudo flatpak override kde.org.kdiff3 --filesystem=host sudo flatpak override kde.org.kompare --filesystem=host but the results is the same. but -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 --- Comment #2 from Silviu --- Created attachment 168111 --> https://bugs.kde.org/attachment.cgi?id=168111=edit /media folder can't be seen -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 --- Comment #1 from Silviu --- Created attachment 168110 --> https://bugs.kde.org/attachment.cgi?id=168110=edit Home folder is empty The /home folder is seen as empty folder but isn't -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 Silviu changed: What|Removed |Added CC||laurentiusil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] New: Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 Bug ID: 484997 Summary: Kdiff3 and Kompare can't see the home folder or media folder Classification: Applications Product: kdiff3 Version: 1.10.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: laurentiusil...@gmail.com Target Milestone: --- SUMMARY I tried to open compare some files from an external drive mounted on /media// but I sow that /media directory can't be seen. I mounted the external drive to /home folder, but the /home/ is seen as empty folder. SOFTWARE/OS VERSIONS Linux/KDE Plasma: MxLinux: MX-23.2_KDE_x64 Libretto, based on Debian 12.5, KDE Plasma 5.27.5 Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480479] plasmashell spams system logs with errors ( PluginOpenAnimation: Animation is null! and OpenAnimation: Failed to open animation!)
https://bugs.kde.org/show_bug.cgi?id=480479 --- Comment #2 from Silviu C. --- Ah. It seem Doom 2016 is naughty. Linking a bug report: https://github.com/ValveSoftware/Proton/issues/6958 A partial fix may be to use this dll: https://github.com/Riesi/CChromaEditor/releases/tag/EMPTY1.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480479] New: plasmashell spams system logs with errors ( PluginOpenAnimation: Animation is null! and OpenAnimation: Failed to open animation!)
https://bugs.kde.org/show_bug.cgi?id=480479 Bug ID: 480479 Summary: plasmashell spams system logs with errors ( PluginOpenAnimation: Animation is null! and OpenAnimation: Failed to open animation!) Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: silvi...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY When I launch a game from Steam my system log gets spammed with this type of message ian 29 12:24:53 localhost.localdomain plasmashell[28916]: OpenAnimation: Failed to open animation! Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: PluginOpenAnimation: Animation is null! name=Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: PluginIsPlayingName: Animation not found! Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKillOpenAnimation: Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: OpenAnimation: Failed to open animation! Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: PluginOpenAnimation: Animation is null! name=Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: PluginIsPlayingName: Animation not found! Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKillOpenAnimation: Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: OpenAnimation: Failed to open animation! Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill ian 29 12:24:53 localhost.localdomain plasmashell[28916]: PluginOpenAnimation: Animation is null! name=Z:\home\silviu\.var\app\com.valvesoftware.Steam\.local\share\Steam\steamapps\common\DOOM\base\chroma_effect_files\ChainsawKill STEPS TO REPRODUCE 1. I open a game from Steam - in this particular example Doom 2016 OBSERVED RESULT System log gets spammed with error messages by plasmashell EXPECTED RESULT Complain once and stop SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240126 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.7.1-2-default (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz Memory: 31.1 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 GAMING X -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 Silviu C. changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #13 from Silviu C. --- Hello, This is fixed for me on Plasma 5.27.10 + Frameworks 5.114.0 - Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #18 from Silviu C. --- (In reply to Nate Graham from comment #17) > So you switched away from KDE since submitting this bug report? Yes. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #16 from Silviu C. --- (In reply to Nate Graham from comment #14) > Silviu, is that the case for you as well, that you have automatic date & > time turned off? > > If not, then Dan's issue is something else and will need a new bug report to > track it. Hello, unfortunately I'm not using the KDE version of Opensuse so I can't test it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 --- Comment #9 from Silviu C. --- Created attachment 159127 --> https://bugs.kde.org/attachment.cgi?id=159127=edit Screenshot showing the problem not manifesting on X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 --- Comment #8 from Silviu C. --- Today I was testing things with an X11 session. The bug does not happen. I switched to Wayland and there it was again. Will attach screenshot. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #4 from Silviu C. --- (In reply to Nate Graham from comment #3) > All right, thanks. Not sure how to proceed here. Just a thought... Is the code responsible for doing the colour shifting trying to do any other type of math like figuring timezones and such? When it seems to me like it's not looking at the actual system time but something else. In my case the system clock is actually set to local time. So what is shown in the time applet from the taskbar matches what the UEFI would show. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 --- Comment #2 from Silviu C. --- (In reply to Nate Graham from comment #1) > Are the latitude and longitude that it reports accurate for your real > location? > > Have you by any chance changed your timezone recently? > > If you turn off Night color in System Settings and turn it back on again, > does it work? Detected latitude and longitude are accurate. I did not change time zone. Turning it off and on again does not fix the problem. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 469732] Mouse battery percentage is not shown correctly - Logitech G603
https://bugs.kde.org/show_bug.cgi?id=469732 --- Comment #3 from Silviu C. --- (In reply to Nicolas Fella from comment #2) > Please run "upower -d" and paste the output here upower -d Device: /org/freedesktop/UPower/devices/ups_hiddev1 native-path: /sys/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/usbmisc/hiddev1 vendor: American Power Conversion model:Back-UPS XS 1400U serial: 3B1641X40632 power supply: yes updated: Du 14 mai 2023 15:17:33 +0300 (2 seconds ago) has history: yes has statistics: yes ups present: yes state: fully-charged warning-level: none time to empty: 1,9 hours percentage: 100% icon-name: 'battery-full-charged-symbolic' History (charge): 1684066653 100,000 fully-charged 1684066653 0,000 unknown 1684066623 100,000 fully-charged 1684066623 0,000 unknown 1684066593 100,000 fully-charged 1684066593 0,000 unknown 1684066562 100,000 fully-charged 1684066562 0,000 unknown History (rate): 1684066653 0,000 unknown 1684066623 0,000 unknown 1684066593 0,000 unknown 1684066562 0,000 unknown Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:G603 Wireless GaG603 Wirel serial: 406c-2a-e2-ad-22 power supply: no updated: Jo 01 ian 1970 02:00:00 +0200 (1684066655 seconds ago) has history: yes has statistics: yes mouse present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Du 14 mai 2023 15:16:33 +0300 (62 seconds ago) has history: no has statistics: no ups present: yes state: fully-charged warning-level: none time to empty: 1,9 hours percentage: 100% icon-name: 'battery-full-charged-symbolic' Daemon: daemon-version: 1.90.0 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 469732] Mouse battery percentage is not shown correctly - Logitech G603
https://bugs.kde.org/show_bug.cgi?id=469732 --- Comment #1 from Silviu C. --- Created attachment 158932 --> https://bugs.kde.org/attachment.cgi?id=158932=edit Screenshot illustrating the problem 2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 469732] New: Mouse battery percentage is not shown correctly - Logitech G603
https://bugs.kde.org/show_bug.cgi?id=469732 Bug ID: 469732 Summary: Mouse battery percentage is not shown correctly - Logitech G603 Classification: Plasma Product: Powerdevil Version: 5.27.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: silvi...@gmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 158931 --> https://bugs.kde.org/attachment.cgi?id=158931=edit Screenshot illustrating the problem 1 SUMMARY Energy -Info Centre and taskbar energy / battery power applet do not show the battery percentage correctly STEPS TO REPRODUCE 1. Click on the "battery" icon on the taskbar OBSERVED RESULT The battery percentage of the mouse is shown incorrectly as 0% EXPECTED RESULT It should show the actual reported percentage. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230512 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-2-default (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz Memory: 31,1 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 GAMING X ADDITIONAL INFORMATION In Gnome's power settings the percentage is shown correctly. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 Silviu C. changed: What|Removed |Added Platform|Other |openSUSE Version|unspecified |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] New: Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 Bug ID: 469730 Summary: Night color shifting does not start at the correct time or end at the correct time Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: silvi...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- Created attachment 158929 --> https://bugs.kde.org/attachment.cgi?id=158929=edit Screenshot illustrating the problem SUMMARY Night color shifting does not start at the correct time or end at the correct time . STEPS TO REPRODUCE 1. Go to System settings -> Display and monitor - > Night colour 2. At the option "Switching times:" select "Sunset and sunrise at current location" 3. Check that the geolocation is correct and that the proposed times for changing the colour temperature are correct (or just suited to what you'd like to happen). 4. Set the desired colour temperature. 5. Click on the "Apply button" OBSERVED RESULT The colour does not begin changing at the correct time despite what the taskbar applet shows. The next morning you may also find that despite it being way past the hour when night colour should have shifted back to daylight colour, your desktop will still have a red tint and the applet will show that night colour is still active EXPECTED RESULT Color shifting should begin and apply correctly at the advertised times SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230512 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-2-default (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz Memory: 31,1 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 GAMING X ADDITIONAL INFORMATION Attached screenshot that shows the functionality problem minus the red tint. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 --- Comment #7 from Silviu C. --- (In reply to Andrey from comment #6) > Thanks, what is the actual layout? Is it Romanian or English still? If I select the Romanian layout that is shown as "English" the actual keyboard layout changes correctly and I can use the <> key to type characters like âășțî etc. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 --- Comment #5 from Silviu C. --- Created attachment 158747 --> https://bugs.kde.org/attachment.cgi?id=158747=edit Screenshot with Romanian (Windows) layout added -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 --- Comment #4 from Silviu C. --- (In reply to Andrey from comment #3) > I mean, if you skip variant Sun Type 6/7, does it show Romanian right? I added the "Romanian (Windows)" layout and it shows fine. Adding screenshot... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 --- Comment #2 from Silviu C. --- (In reply to Andrey from comment #1) > Is "variant Sun Type 6/7" essential here? Honestly, I would be happy if it said just "Romanian". I've no clue why it thinks it's "English (US)". I tried with other languages with variants but it displayed those fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469434] New: Romanian variant Sun Type 6/7 does not show correctly
https://bugs.kde.org/show_bug.cgi?id=469434 Bug ID: 469434 Summary: Romanian variant Sun Type 6/7 does not show correctly Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Keyboard Layout Assignee: plasma-b...@kde.org Reporter: silvi...@gmail.com CC: butir...@gmail.com Target Milestone: 1.0 Created attachment 158745 --> https://bugs.kde.org/attachment.cgi?id=158745=edit Screenshot showing the issue SUMMARY STEPS TO REPRODUCE 1. Go to System Settings - > Input Devices -> Kayboard -> Layouts 2. Add Romanian variant Sun Type 6/7 - which is basically the same as what Microsoft calls Romanian Programmers 3. Click "Apply" OBSERVED RESULT The Keyboard layout switcher calls is English US (see attached screenshot) EXPECTED RESULT Show entry as "Romanian ( Sun Type 6/7)" SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230505 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.3.1-1-default (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz Memory: 31,1 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 GAMING X ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469270] Skanpage crashes when trying to do OCR if tesseract is not installed
https://bugs.kde.org/show_bug.cgi?id=469270 --- Comment #2 from Silviu C. --- (In reply to Nate Graham from comment #1) > Tesseract is required for OCR; if it's not installed, it won't work. But if > the OCR controls are appearing anyway despite Tesseract not being installed, > that sounds like a bug in the app, as it shouldn't be happening. I just > tested this by removing the `tesseract-devel package` and rebuilding the > app, and I correctly don't see the OCR controls. > > Maybe the reverse is not working, and it fails to hide them at runtime if > compiled with Tesseract support included but the package isn't actually > installed on the user's machine. Unfortunately I can't easily test this as > my distro (Fedora KDE) makes Tesseract a mandatory package and it can't be > removed at runtime. I believe this is what is happening. Skanpage is compiled with tesseract support but tesseract is not installed. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469270] New: Skanpage crashes when trying to do OCR if tesseract is not installed
https://bugs.kde.org/show_bug.cgi?id=469270 Bug ID: 469270 Summary: Skanpage crashes when trying to do OCR if tesseract is not installed Classification: Applications Product: Skanpage Version: 23.04.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: a.stipp...@gmx.net Reporter: silvi...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Skanpage crashes if OCR is selected when saving the file but tesseract-ocr is not actually installed. STEPS TO REPRODUCE 1. start Skanpage 2. scan something with text 3. when saving the PDF either leave the option to add OCR checked or check it OBSERVED RESULT Skanpage crashes. EXPECTED RESULT Skanpage test whether tesseract is actually usable. If it's not, grey out the OCR option and inform user they don't have it installed on the system SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230501 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9600K CPU @ 3.70GHz Memory: 31,1 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 GAMING X ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 456978] New: Can't send photos with certain file names
https://bugs.kde.org/show_bug.cgi?id=456978 Bug ID: 456978 Summary: Can't send photos with certain file names Product: kdeconnect Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: silvi...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. I receive images with a name like "f0a8cddd-5c22-4638-ab7f-dcbb81674604.jpeg" 2. Connect to Windows PC running KDE connect, using the iOS version of KDE connect 3. "Send photos and videos", select files and press "Add" OBSERVED RESULT If multiple files are selected transfer hangs after the first file is received on the Windows side EXPECTED RESULT All files should be transfered SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I tried to reproduce on Fedora 36 using the same iOS device. Files transferred quickly and without issues. On Windows, series of files with names like "IMG_6330.jpeg" transfer just fine. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 413942] New: ksysguard crashed after forcefully closing a frozen Viber
https://bugs.kde.org/show_bug.cgi?id=413942 Bug ID: 413942 Summary: ksysguard crashed after forcefully closing a frozen Viber Product: ksysguard Version: 5.16.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: killerm...@yahoo.com Target Milestone: --- Application: ksysguard (5.16.5) Qt Version: 5.12.4 Frameworks Version: 5.62.0 Operating System: Linux 5.3.0-19-generic x86_64 Distribution: Ubuntu 19.10 -- Information about the crash: - What I was doing when the application crashed: I sent a TERM signal to "Viber", then a KILL signal a few seconds later (Viber window was frozen). Viber windows closed on KILL. Viber processes dissapeard from the ksysguard list. Afterwards I closed the ksysguard window (everything seemed normal) and the crash handler poped up. The crash does not seem to be reproducible. -- Backtrace: Application: System Monitor (ksysguard), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb620789f00 (LWP 5004))] Thread 3 (Thread 0x7fb617fff700 (LWP 5006)): #0 0x7fb633f61c2f in __GI___poll (fds=0x7fb6100029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb62a31ea3e in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb62a31eb73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb6325bb6c3 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb63256263b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb63239ba75 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fb6328e9efa in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fb63239ccc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb62ab7a669 in start_thread (arg=) at pthread_create.c:479 #9 0x7fb633f6e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fb61f8a3700 (LWP 5005)): #0 0x7fb633f61c2f in __GI___poll (fds=0x7fb61f8a25a8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fb62abdd917 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fb62abdf53a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fb61fe01288 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fb63239ccc2 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb62ab7a669 in start_thread (arg=) at pthread_create.c:479 #6 0x7fb633f6e323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fb620789f00 (LWP 5004)): [KCrash Handler] #6 0x7fb6331f9810 in () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fb6331fa384 in QLabel::setText(QString const&) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fb6340b4223 in () at /usr/lib/x86_64-linux-gnu/libkdeinit5_ksysguard.so #9 0x7fb633cde378 in KSGRD::SensorAgent::processAnswer(char const*, int) () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #10 0x7fb633ce5802 in () at /usr/lib/x86_64-linux-gnu/libksgrd.so.7 #11 0x7fb63258f5c8 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fb6324df4ce in QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fb6324e5bd9 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fb6324e5f42 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fb63258f468 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fb63259c135 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fb63259c491 in QSocketNotifier::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fb6330bea86 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb6330c7e00 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fb632563a9a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fb6325bc305 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fb62a31e84d in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fb62a31ead0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fb62a31eb73 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7fb6325bb6a5 in QEventDispatcherGlib::processEvents(QFlags) ()
[kate] [Bug 402421] Crash with custom syntax hightligh
https://bugs.kde.org/show_bug.cgi?id=402421 --- Comment #2 from Silviu --- I can open the file specified in bug 401480 without any issue: https://raw.githubusercontent.com/letscontrolit/ESPEasy/mega/src/ESPEasy.ino -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402421] New: Crash with custom syntax hightligh
https://bugs.kde.org/show_bug.cgi?id=402421 Bug ID: 402421 Summary: Crash with custom syntax hightligh Product: kate Version: 18.04.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: killerm...@yahoo.com Target Milestone: --- Application: kate (18.04.3) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.18.0-12-generic x86_64 Distribution: Ubuntu 18.10 -- Information about the crash: - What I was doing when the application crashed: Opened a nginx config file - Custom settings of the application: Added this syntax highlight https://github.com/mtorromeo/kate-syntax-files/blob/master/nginx.xml (the xml may have a bug, can't tell) The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe035994800 (LWP 13993))] Thread 3 (Thread 0x7fe031af9700 (LWP 13995)): #0 0x7fe03b9726d9 in __GI___poll (fds=0x7fe024004db0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe038eb1e46 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe038eb1f6c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe03be9715b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe03be4416b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe03bc930b6 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe03c150545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe03bc9cc87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe03a1ea164 in start_thread (arg=) at pthread_create.c:486 #9 0x7fe03b97edef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe033c39700 (LWP 13994)): #0 0x7fe03b9726d9 in __GI___poll (fds=0x7fe033c38cb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe03a411917 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fe03a41353a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fe034ffe159 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fe03bc9cc87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe03a1ea164 in start_thread (arg=) at pthread_create.c:486 #6 0x7fe03b97edef in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe035994800 (LWP 13993)): [KCrash Handler] #6 0x7fe03d8030ca in ?? () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #7 0x7fe03b309c2d in KSyntaxHighlighting::AbstractHighlighter::highlightLine(QString const&, KSyntaxHighlighting::State const&) () from /usr/lib/x86_64-linux-gnu/libKF5SyntaxHighlighting.so.5 #8 0x7fe03d8d86cd in ?? () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #9 0x7fe03d87c5a5 in KateBuffer::doHighlight(int, int, bool) () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #10 0x7fe03d860f03 in KTextEditor::DocumentPrivate::editEnd() () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #11 0x7fe03d8664e5 in KTextEditor::DocumentPrivate::paste(KTextEditor::ViewPrivate*, QString const&) () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #12 0x7fe03d8e1d84 in KTextEditor::ViewPrivate::paste(QString const*) () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #13 0x7fe03d9db337 in ?? () from /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #14 0x7fe03be6e6db in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fe03c965ef2 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fe03c968500 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fe03c968db4 in QAction::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fe03c96c4a1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fe03c973ae0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7fe03be45499 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fe03c3dd233 in QShortcutMap::dispatchEvent(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7fe03c3dd30b in QShortcutMap::tryShortcut(QKeyEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7fe03c392866 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int,
[kdevelop] [Bug 402146] Fold all command for all nodes not only for top-level nodes. Restore the last folded nodes after Kdevelop restart
https://bugs.kde.org/show_bug.cgi?id=402146 --- Comment #2 from Silviu --- Ok! Many thanks for your time! I apologize for time lost -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402151] New: KDevelop can't be installed in Windows
https://bugs.kde.org/show_bug.cgi?id=402151 Bug ID: 402151 Summary: KDevelop can't be installed in Windows Product: kdevelop Version: 5.3.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: critical Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 116937 --> https://bugs.kde.org/attachment.cgi?id=116937=edit The installation is stopping here I tried to install KDevelop last version 5.3.0, but I got this message: -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 402146] New: Fold all command for all nodes not only for top-level nodes. Restore the last folded nodes after Kdevelop restart
https://bugs.kde.org/show_bug.cgi?id=402146 Bug ID: 402146 Summary: Fold all command for all nodes not only for top-level nodes. Restore the last folded nodes after Kdevelop restart Product: kdevelop Version: 5.3.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Please help us with the implementation of command for folding of all nodes: https://bugs.kde.org/show_bug.cgi?id=352868 This very useful when there are hundred and thousand lines of code. Another request is to restore the last folded nodes after the restart of KDevelop. There two thinks are very useful Many thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 352868] Folding for all nodes (not just top-level) and/or siblings to current
https://bugs.kde.org/show_bug.cgi?id=352868 --- Comment #9 from Silviu --- There are more than three years since the "fold all" command was requested. I'm expecting the solution on each new release, but it seems that thinks are going very hard with this. Please make a small effort and implement this in KDevelop. Otherwise KDevelop is a wonderful tool. Many thanks for your work -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 392837] Mouse Right Click menu is overlapped with Clipboard History menu
https://bugs.kde.org/show_bug.cgi?id=392837 --- Comment #8 from Silviu --- Regarding the operating system where I recorded this issue, I use Windows 7, 64 bit -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392837] New: Mouse Right Click menu is overlapped with Clipboard History menu
https://bugs.kde.org/show_bug.cgi?id=392837 Bug ID: 392837 Summary: Mouse Right Click menu is overlapped with Clipboard History menu Product: kdevelop Version: 5.2.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 111893 --> https://bugs.kde.org/attachment.cgi?id=111893=edit Issue example Please take a look on the attached print screen. I, placed the cursor over "Jump to Declaration" in order to press on it. But because before to arrive to "Jump to Declaration" line, I crossed over "Clipboard History" line, the submenu of "Clipboard History" was launched. So, I arrived with the mouse cursor over "Jump to Declaration" line in order to press on it, but even the mouse cursor was placed over the "Jump to Declaration" line, the selected menu is "Clipboard History" -> $matrix line, which is not correct, and when I pressed on the mouse button, the "Clipboard History" -> $matrix menu was launched, which is wrong. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 392833] New: Rename function doesn't work
https://bugs.kde.org/show_bug.cgi?id=392833 Bug ID: 392833 Summary: Rename function doesn't work Product: kdevelop Version: 5.2.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Let's consider that there is a function named: Function_name Press mouse right click on the name of the function and go to 'Rename "function name"...' menu. In my case, the Rename window in launched, but the function can't be found. This seems to happen because the name of the function start with upper case letter. If the function name will be changed to "function_name", then everything works, but it doesn't work if an upper case letter is in the name of the function, for example: "function_Name". This problem could be because the Rename action, when it is launched, it convert all upper case letters from function name to lower case letters, when it is launched. I saw this in the Rename window, at "New name" input field, when the name of the function is converted to lower case letters Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 388358] New: Underline (_) is not displayed if PHP static class in some conditions
https://bugs.kde.org/show_bug.cgi?id=388358
Bug ID: 388358
Summary: Underline (_) is not displayed if PHP static class in
some conditions
Product: kdevelop
Version: 5.2.1
Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: Language Support: PHP
Assignee: kdevelop-bugs-n...@kde.org
Reporter: laurentiusil...@gmail.com
Target Milestone: ---
I have below code:
else{
$error=true;
Show::_Message('The required attribute "'.$attribute.'" doesn\'t
exist!!!Please select one from the next valid attributes:
'.$this->lib_attributes_as_string);
}
The underline which is placed before Message method is not displayed if
the mouse pointer is positioned after the else{ and the zoom have some values.
This issue is related to the row length, so, in my case the Message
argument length. So, if the length of the argument is only few characters, the
issue doesn't happen.
This issue also is linked with the Appearance setting -> Highlight range
between selected brackets -> checkbox. If this is unchecked, the issue doesn't
happen.
--
You are receiving this mail because:
You are watching all bug changes.
[kdevelop] [Bug 388357] New: PHP SimpleXMLElement autocomplete don't work
https://bugs.kde.org/show_bug.cgi?id=388357 Bug ID: 388357 Summary: PHP SimpleXMLElement autocomplete don't work Product: kdevelop Version: 5.2.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Language Support: PHP Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- 1. Make a new object SimpleXMLElement which parse a XML file 2. Try to access the nodes of XML object and can be seen the autocomplete don't work. If this is not yet implemented, it will be a great future. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386915] Icons from find-replace bar aren't displayed
https://bugs.kde.org/show_bug.cgi?id=386915 --- Comment #5 from Silviu <laurentiusil...@gmail.com> --- Probably the bug was linked with another one which was solved :-) because it 5.2.1 version the icons are displayed but in 5.2.0 version it didn't. On Fri, Dec 1, 2017 at 10:59 AM, Sven Brauch <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=386915 > > --- Comment #4 from Sven Brauch <m...@svenbrauch.de> --- > Hm, we didn't change anything though. Weird. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386915] Icons from find-replace bar aren't displayed
https://bugs.kde.org/show_bug.cgi?id=386915 Silviu <laurentiusil...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Silviu <laurentiusil...@gmail.com> --- In 5.2.1 version this was solved -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] Don't complete class members if "echo" is added before
https://bugs.kde.org/show_bug.cgi?id=387044 Silviu <laurentiusil...@gmail.com> changed: What|Removed |Added Summary|Don't complete class|Don't complete class |members if "echo" is in |members if "echo" is added |added before|before -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] Don't complete class members if "echo" is in added before
https://bugs.kde.org/show_bug.cgi?id=387044 Silviu <laurentiusil...@gmail.com> changed: What|Removed |Added Summary|Don't complete class|Don't complete class |methods if "echo" is in |members if "echo" is in |added before|added before -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 387044] New: Don't complete class methods if "echo" is in added before
https://bugs.kde.org/show_bug.cgi?id=387044 Bug ID: 387044 Summary: Don't complete class methods if "echo" is in added before Product: kdevelop Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 108926 --> https://bugs.kde.org/attachment.cgi?id=108926=edit Example In a PHP project opened with KDevelop, there are two files: 1. classes.php - which contains below code: 2. test_bench.php - which contains: If in the second file, I added the next row: $test-> the autocomplete is displayed with all public methods and variable from KDevelop_Test class. But if "echo" is added before $test->, the autocomplete after $test-> is not displayed and in my opinion this is an issue. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386920] Fold all nodes
https://bugs.kde.org/show_bug.cgi?id=386920 Silviu <laurentiusil...@gmail.com> changed: What|Removed |Added OS|MS Windows |All Platform|MS Windows |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386920] New: Fold all nodes
https://bugs.kde.org/show_bug.cgi?id=386920 Bug ID: 386920 Summary: Fold all nodes Product: kdevelop Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- This is not a bug, it is a request. I think it will be very useful if there will be the possibility to fold all nodes, not only the current or the top level nodes. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386918] New: F9 shortcut is default added for two commands
https://bugs.kde.org/show_bug.cgi?id=386918 Bug ID: 386918 Summary: F9 shortcut is default added for two commands Product: kdevelop Version: 5.2.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 108865 --> https://bugs.kde.org/attachment.cgi?id=108865=edit Example If F9 key is pressed, the conflict window appears. This because F9 key was default added for two command. Please see the attachment. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386917] Shortcut Key issue
https://bugs.kde.org/show_bug.cgi?id=386917 Silviu <laurentiusil...@gmail.com> changed: What|Removed |Added OS|Linux |MS Windows Platform|Other |MS Windows -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386917] New: Shortcut Key issue
https://bugs.kde.org/show_bug.cgi?id=386917 Bug ID: 386917 Summary: Shortcut Key issue Product: kdevelop Version: 5.2.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 108864 --> https://bugs.kde.org/attachment.cgi?id=108864=edit Example Open Configure Shortcut window Filter shortcuts using "fold" word Try to add a shortcut to "Fold current node" using Ctrl+Shift+Y. But even if this shortcut is not used, the attached window conflict occurs (please see the attachment) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 386915] New: Icons from find-replace bar aren't displayed
https://bugs.kde.org/show_bug.cgi?id=386915 Bug ID: 386915 Summary: Icons from find-replace bar aren't displayed Product: kdevelop Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 108863 --> https://bugs.kde.org/attachment.cgi?id=108863=edit Example 2 KDevelop Version 5.2.0 Press Ctrl+F in order to find a string. Try to open press Switch to increment search bar button in order to find and replace the sting with another one. But the icon of Switch to increment search bar button is not present, so the button is without icon. The same situation is for: Jump to next match and Jump to preview match Please see the attachment. Platform: Windows 7, 64bits. Thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385919] New: Code folding is not kept after the restart of KDevelop
https://bugs.kde.org/show_bug.cgi?id=385919 Bug ID: 385919 Summary: Code folding is not kept after the restart of KDevelop Product: kdevelop Version: 5.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- In the last used file I fold all nodes (top level folding) I restarted KDevelop but all nodes are unfolded, so it didn't keep the last folding nodes. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385918] New: KDevelop don't keep after restart the last selected tool views
https://bugs.kde.org/show_bug.cgi?id=385918 Bug ID: 385918 Summary: KDevelop don't keep after restart the last selected tool views Product: kdevelop Version: 5.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- On the left bar with tool views, I press Project tool view and then I press Ctrl key from keyboard (in order to open two tool views) and then I press Class tool view. Everything works. After the restart of KDevelop, only one Project tool view is pressed, so it don't keep the last configuration. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385916] New: Filesystem tool view is opened after KDevelop restart
https://bugs.kde.org/show_bug.cgi?id=385916 Bug ID: 385916 Summary: Filesystem tool view is opened after KDevelop restart Product: kdevelop Version: 5.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- I opened KDevelop I pressed right click on Filesystem tool view from left bar Filesystem tool view is closed I restarted KDevelop Filesystem in opened again even it was closed before to restart KDevelop -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 385915] New: Recent project list is not cleared
https://bugs.kde.org/show_bug.cgi?id=385915 Bug ID: 385915 Summary: Recent project list is not cleared Product: kdevelop Version: 5.1.2 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- I open KDevelop No document is opened I press Recent Project button I press Clear List and the Recent Project list is cleared I close KDevelop I open again and the list is still present -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 384491] New: System Settings crash when switching the Application Color Scheme
https://bugs.kde.org/show_bug.cgi?id=384491 Bug ID: 384491 Summary: System Settings crash when switching the Application Color Scheme Product: systemsettings Version: 5.9.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: killerm...@yahoo.com Target Milestone: --- Application: systemsettings5 (5.9.5) Qt Version: 5.7.1 Frameworks Version: 5.31.0 Operating System: Linux 4.10.0-33-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: I changed the Application Color Scheme from Breeze to something else then back to Breeze. On clicking "Apply, it crashed. The crash does not seem to be reproducible. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f013aea78c0 (LWP 27607))] Thread 6 (Thread 0x7f00fab43700 (LWP 27615)): #0 0x7f0130e11ef4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0130dcc48e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0130dcc68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f01375620bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f013750bbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0137339f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0135684df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f013733ec38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0132f2f6da in start_thread (arg=0x7f00fab43700) at pthread_create.c:456 #9 0x7f0136c4bd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 5 (Thread 0x7f0107694700 (LWP 27614)): #0 0x7f0130dcba25 in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0130dcc49b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0130dcc68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f01375620bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f013750bbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0137339f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0135684df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f013733ec38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0132f2f6da in start_thread (arg=0x7f0107694700) at pthread_create.c:456 #9 0x7f0136c4bd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 4 (Thread 0x7f011157c700 (LWP 27613)): #0 0x7f0130e11ef4 in g_mutex_unlock () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0130dcc52a in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0130dcc68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f01375620bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f013750bbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0137339f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0135684df5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f013733ec38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0132f2f6da in start_thread (arg=0x7f011157c700) at pthread_create.c:456 #9 0x7f0136c4bd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 3 (Thread 0x7f011fb68700 (LWP 27610)): #0 0x7f0136c3fd8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0130dcc576 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0130dcc68c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f01375620bb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f013750bbea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0137339f83 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0137e655d5 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f013733ec38 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f0132f2f6da in start_thread (arg=0x7f011fb68700) at pthread_create.c:456 #9 0x7f0136c4bd7f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7f01287ec700 (LWP 27609)): #0 0x7f0136c3fd8d in poll () at ../sysdeps/unix/syscall-template.S:84
[kdevelop] [Bug 376790] New: Documents tool view windows is unexpected closed when Configure Ok button from KDevelop window is pressed
https://bugs.kde.org/show_bug.cgi?id=376790 Bug ID: 376790 Summary: Documents tool view windows is unexpected closed when Configure Ok button from KDevelop window is pressed Product: kdevelop Version: 5.0.3 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: laurentiusil...@gmail.com Target Milestone: --- Created attachment 104163 --> https://bugs.kde.org/attachment.cgi?id=104163=edit After Documents tool view is unexpected closed Possible bug reproduction: Press 'Documents' button (tab), from left side, in order to open the Documents tool view. Go to Settings -> Configure KDevelop... -> make any change and press Apply or OK button. When the button is pressed, Documents tool view window is closed, which I think is not a normal thing, and the Documents button (from left side, is still pressed (like when the Documents tool view window is still opened. Thanks a lot! It is a wonderful tool :) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 375779] New: kdeconnectd consuming 100% of a CPU core after user logout
https://bugs.kde.org/show_bug.cgi?id=375779 Bug ID: 375779 Summary: kdeconnectd consuming 100% of a CPU core after user logout Product: kdeconnect Version: 1.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: silvi...@fastmail.fm Target Milestone: --- I have KDE Connect 1.0.3 on openSUSE 42.2 from the KDE Extra repository. https://software.opensuse.org/download.html?project=KDE%3AExtra=kdeconnect-kde There are two users on my machine. When one of the users logs out and the other logs in, there's a kdeconnectd process still active that belongs to the first user and it consumes 100% of a CPU core. -- You are receiving this mail because: You are watching all bug changes.
