[plasmashell] [Bug 442425] New: After invoke Application Launcher, typing does nothing
https://bugs.kde.org/show_bug.cgi?id=442425 Bug ID: 442425 Summary: After invoke Application Launcher, typing does nothing Product: plasmashell Version: git-master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I click into Application Launcher and start typing. In result happens nothing, only highlights first icon in "Favorites" not related with typed letter. STEPS TO REPRODUCE 1. Invoke Application Launcher 2. Start typing 3. OBSERVED RESULT Highlight first icon (Firefox) in "Favorite", even I enter not "f" EXPECTED RESULT start searching/matching results for entered string and showing results SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Neon Unstable. System up-to-date on day 2021/09/14 (morning) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442285] Moving Digital Clock widget in direction of Task Manager causes that Digital Clock disappars
https://bugs.kde.org/show_bug.cgi?id=442285 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Neon Packages CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442285] New: Moving Digital Clock widget in direction of Task Manager causes that Digital Clock disappars
https://bugs.kde.org/show_bug.cgi?id=442285 Bug ID: 442285 Summary: Moving Digital Clock widget in direction of Task Manager causes that Digital Clock disappars Product: plasmashell Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: 1.0 SUMMARY I have vertical panel. Digital Clock is placed on very bottom. I wanted to rearrange a bit the widgets on my Panel, so tried to move Digital Clock on top of the panel. In result I was very surprised because Digital Clock just disappeared when mouse cursor was over Task Manager. The same happened when I moved System Tray widget, which was placed also on bottom. Notice that underneath the Panel was nothing, I moved it from left to right edge of screen. This disappearing was very confused. I noticed, that when I want to rearrange widgets on Panel I need to just move Task Manager widget. Only in this case other widgets just jumps on Task Manager. To back to the previous situation I needed to drag and drop lost widgets taking them from Widgets side bar. STEPS TO REPRODUCE 1. Set panel as right side 2. Add to the panel (counting from bottom) Digital Clock, System Tray, Task Manager, Application launcher 3. Turn on "Edit Panel" 4. Try to move Digital Clock on top OBSERVED RESULT Digital Clock disappears EXPECTED RESULT Digital Clock should try to jump on Task Manger and don't lost SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Up-to-date Neon/Linux on day 2021/09/10, time 23:32 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442284] New: konsole is very small after very first start
https://bugs.kde.org/show_bug.cgi?id=442284 Bug ID: 442284 Summary: konsole is very small after very first start Product: konsole Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- Created attachment 141461 --> https://bugs.kde.org/attachment.cgi?id=141461=edit konsole - 3 rows, very first start SUMMARY I logged in on new user, and started konsole. In result I got window with 3 rows. STEPS TO REPRODUCE 1. Create new user 2. Log in on new ueser 3. Start konsole OBSERVED RESULT konsole window has 3 row EXPECTED RESULT In my opinion konsole window shold have more than 3 row, maybe 30 SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Up-to-date Neon/Linux on day 2021/09/10, time 23:32 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442283] Restore session in Wayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=442283 --- Comment #2 from Piotr Mierzwinski --- After I back to x11 I got broken desktop, I mean I lost the panel. Only Firefox was restored. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442283] Restore session in Wayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=442283 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- I started again my all applications. Logged out and logged in. In result again nothing was restored. I back to x11 windowing system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442283] New: Restore session in Wayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=442283 Bug ID: 442283 Summary: Restore session in Wayland doesn't work Product: plasmashell Version: git-master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 141460 --> https://bugs.kde.org/attachment.cgi?id=141460=edit Configuratio-Destkop_Session SUMMARY I switched for tests to Wayland session. I have opened couple applications like Firefox, Dolphin, Konsole, Kate and Clementine (on one from 3 activities). After first login ot Wayland session was correctly restored. So I started Dolphin application in my second activity, back to my default activity and signed out. I signed it and turned out that only Firefox was restored. STEPS TO REPRODUCE 1. Create couple activities 2. Start couple applications on 'default' activity 3. Sign off 4. Select Wayland session and sign in 5. On second activity start Dolphin 6. Sign out and Sign in OBSERVED RESULT Only Firefox is restored EXPECTED RESULT Should be restore all running applications in moment of signing out SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Up-to-date Neon/Linux on day 2021/09/10, 23:32 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 --- Comment #3 from Piotr Mierzwinski --- Sign out -> Sign in, just helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 --- Comment #2 from Piotr Mierzwinski --- Notice that changing "Font style" in Digital Clock settings helps nothing. Still we can see visually broken digital clock. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 141459 --> https://bugs.kde.org/attachment.cgi?id=141459=edit lasma-broken-Digital_Clock -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] New: Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 Bug ID: 442282 Summary: Adding Digital Clock from desktop onto Panel makes that widget is visually broken Product: plasmashell Version: git-master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: 1.0 SUMMARY When you move Digital Clock onto desktop and want you put it back to Panel then turns out that on Panel we get trashes (check screen shot). To get visually correct Digital Clock need to drag and drop it directly from Widgets side bar. I use vertical panel and didn't test it on horizontal one. STEPS TO REPRODUCE 1. Turn on "Edit Panel" 2. Move Digital Clock onto desktop (isn't possible to put is anywhere, because it will stuck very close to the panel) 3. Move back (Drag and Drop) Digital Clock from Desktop onto Panel OBSERVED RESULT we get visually broken Digital Clock, seems like could chosen some strange font. Clock is not readable EXPECTED RESULT Digital Clock when backs onto the panel should look like before we moved it onto desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION In test I used up-do-date Neon on day: 2021/09/10, 23:02 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442193] Cancel sending files doesn't stop kio_file proces
https://bugs.kde.org/show_bug.cgi?id=442193 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- After all processes (daamon, tags, and kio_file) have been killed by signal 9, socket file isn't removed /run/user/1000/kdeconnect.daemonWKCwsb.2.slave-socket After I remove this file and run again daemon then I can send files otherwise I can see only bouncing process and on my phone message that sending failed. BTW. I'm able to send (from phone to PC ) only couple filesfrom all I try to send, because after 2 or 3 sending stops, hung. I mean progress shows for example 2 of 10 and on Android I can see "sent 10 files". In "Download" there is only 2. Nothing happens with sending, because stuck. I will report another bug for this issue. on my phone I have Android 8.0, sorry for mistake. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442193] New: Cancel sending files doesn't stop kio_file proces
https://bugs.kde.org/show_bug.cgi?id=442193 Bug ID: 442193 Summary: Cancel sending files doesn't stop kio_file proces Product: kdeconnect Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY I send several files from Android to my PC and in the middle click "Cancel" button on progress dialog. Progress window disappear, so we think that sending process stopped, but it didn't I run in terminal command: ps -ef | grep kdeco and found still working process kio_file 0:00:00 kio_file.so [kdeinit5] file local:/run/user/1000/klauncherFsicHy.1.slave-socket local:/run/user/1000/kdeconnect.daemonQdIljE.2.slave-socket STEPS TO REPRODUCE 1. in kdeconnect pair your Android smartfon with your PC 2. send several files from Android to your PC 3. click "Cancel" on progress dialog OBSERVED RESULT progress dialog disappears, but kio_file process still working EXPECTED RESULT progress dialog disappears, and kio_file process should be also stopped, because sending has been interrupted, so stopped SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 with kde patch collection ADDITIONAL INFORMATION system on my phone: Android 7 kdeconnect on Android: 1.17 (debug version, because in this version works SMS sending) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 442190] New: "Download" link in progress window moves to Dolphin in another activity
https://bugs.kde.org/show_bug.cgi?id=442190 Bug ID: 442190 Summary: "Download" link in progress window moves to Dolphin in another activity Product: kdeconnect Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY During sending files from Android to PC is showing progress windows where is present link "Download". Clicking into this link opens directory in Dolphin. The problem is that it opens directory in Dolphin present in different activity than current one. STEPS TO REPRODUCE 1. Create couple activities (I have 3: A, B) 2. Open Dolphin on activity A and activity B 3. Back to activity A and minimize Dolphin 4. pair kdeconnect with your Android phone 5. in Android try so send couple files to your PC 6. in progress window click into "Download" OBSERVED RESULT plasma switches to activity B and opens directory in Dolphin EXPECTED RESULT plasma should not switch to different activity looking for Dolphin instance whereas Dolphin is working in current one and here should open directory for example in another card SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 ADDITIONAL INFORMATION my phone system: Android 8.0 kdeconnect 21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441779] New: OSD is showing in the middle of the both screens in case two displays connected
https://bugs.kde.org/show_bug.cgi?id=441779 Bug ID: 441779 Summary: OSD is showing in the middle of the both screens in case two displays connected Product: plasmashell Version: 5.22.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY My second display is always connected to PC, only usually disabled in Display Settings. When I want to use it just enable it in Display Settings and turn device. on All is fine. I get second display working properly. Only the issue is that OSD menu starting to show in the middle of these two screens. I mean half on one and second half on second - in the middle concatenated screens, or in other words - centrally like both would be one big screen. Please look at the below ascii picture. I expected that OSM will be show only on current one. +-- ---+---+ |1st scr. |2nd scr. | | OSD | |1st scr. |2nd scr. | +- ++ STEPS TO REPRODUCE 1. Connect second display to your PC 2. In configuration arrange them like one next to second 3. Apply settings 4. Disable second display in configuration and turn device off 5. Relogin or restart your PC 6. In Display Setting enable second display 7. Turn on device 8. Try to volume up or down by special keys OBSERVED RESULT OSD menu is showing half on one screen and half on the second - centred like both would be one big screen. EXPECTED RESULT OSD menu should be shown only on current screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents/changes on quit
https://bugs.kde.org/show_bug.cgi?id=353654 --- Comment #13 from Piotr Mierzwinski --- As I promised, I retested kate in today's Neon. Unfortunately in restored kate changes, which should be stashed wasn't restored. I got original file without any changes made before log out. And kwrite blocks log out, asking for unsaved file. Kate 21.11.70 Plasma 5.22.80 Framework 5.86 Qt-5.15.3 Graphics X11 Kernel 5.11.0-27-generic -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents/changes on quit
https://bugs.kde.org/show_bug.cgi?id=353654 Piotr Mierzwinski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Piotr Mierzwinski --- I tested this in Neon updated at Jul, 24th 2021 (details below) and noticed that when I close kate with not saved file then it doesn't ask me for saving this file. So this is what we expected. The same happens when I have in kate not saved file and try to logoff or shutdown the system. Nice. Only the problem is that after kate starts with new session of Plasma, the changes made before closing it are not restored, so nothing was swapped in moment on kate was closed. Second thing is that this (not asking for save not saved file) works only in Kate. When I tried to do the same with kwrite, it asked me for saving file. Please notice that I had the same setting in both. BTW. I have 3 activities, but kate and krwite were tested only on one. Kate 21.11.70 Plasma 5.22.80 Framework 5.85 Qt-5.15.3 Graphics X11 Kernel 5.8.0 I will retest this also with today;s Neon. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441496] New: "Open in containing folder" switches to Dolphin in different Activity
https://bugs.kde.org/show_bug.cgi?id=441496 Bug ID: 441496 Summary: "Open in containing folder" switches to Dolphin in different Activity Product: gwenview Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY In Gwenview there is option 'Open in containing folder'. Nice, only the problem is that this option works well only when we don't have any additional Activities with opened Dolphin. In my case after I used option 'Open in containing folder' then was opened folder in Dolphn which was placed (Dolphin) on different activity than Gwenview (used to viewing pictures), despite on the same activity I had working Dolphin. From some unknown reason has been chosen different instance of dolphin than placed in different activity. STEPS TO REPRODUCE 1. Add one or two additional activitites (I have 3 : A, B, C) 2. Open Dolphin on both (A and B) 3. Open Gwenview on folder with pctires on A 4. Choose option: 'Open in containing folder' for opened picture OBSERVED RESULT Plasma switches to activity B and here opens folder in Dolphin EXPECTED RESULT Plasma should not switch current activity, only open folder in Dolphin working on current activity SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 with kde patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 441493] New: Missing option 'Share' in context menu
https://bugs.kde.org/show_bug.cgi?id=441493 Bug ID: 441493 Summary: Missing option 'Share' in context menu Product: gwenview Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY In my opinion in context menu after RMB click on showed picture is missing option 'Share' . I mean showing the same group of options like we have in Dolphin. I found only option with 'Export', but here cannot send anything via bluetooth or using KDE Connect. Use case. Viewing pictures in Gwenview I would like to send a one or more to my phone via KDE Connect. Unfortunately in Gwenview this is not possible. To do this I need to open Dolphin and here looking at small side view, choose picture to send. RMB click on file and 'Share -> Send to Device'. Plenty of clicking. I know that in Gwenview there is option 'Open in containing folder', but it doesn't work well if we have couple activities and Dolphin working on each of them. I will raise bug report about this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 441264] Save As dialog doesn't remember recently used file type
https://bugs.kde.org/show_bug.cgi?id=441264 Piotr Mierzwinski changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 441264] Save As dialog doesn't remember recently used file type
https://bugs.kde.org/show_bug.cgi?id=441264
Piotr Mierzwinski changed:
What|Removed |Added
CC||piotr.mierzwin...@gmail.com
Resolution|WAITINGFORINFO |FIXED
--- Comment #2 from Piotr Mierzwinski ---
(In reply to Nate Graham from comment #1)
> It's because there is already an option to choose the default file type in
> the settings window.
I reported this because wasn't able to find this option, but now I found
(here:: Configure -> Save -> Filename:").
> If the save dialog remembered the last-used choice,
> then these would conflict ("two sources of truth" problem) and we would need
> to remove the option in the settings window for which file type to use by
> default. Why can't you just change the value in the settings window to the
> file type you want to use more often?
Yes,.You are right would be conflict unless would be added new option to
combobox (in configuration window) calling for example 'last used;. At the
very first use of "Save As" would be selected for example "PNG". And now if
the user would changed it then new one would be suggested in "Save As" dialog.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 441262] In Configure Digital Clock, Font Style is displayed incorrectly - always "Default"
https://bugs.kde.org/show_bug.cgi?id=441262 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Archlinux Packages CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 441264] New: Save As dialog doesn't remember recently used file type
https://bugs.kde.org/show_bug.cgi?id=441264 Bug ID: 441264 Summary: Save As dialog doesn't remember recently used file type Product: Spectacle Version: 21.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: piotr.mierzwin...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY I observed that whenever I open "Save As" dialog I have always the same, default value of file type, which is saved in configuration file (~/.config/spectaclerc) in field: "defaultSaveImageFormat". In configuration there is no any option which forcing this, so why Spectacle doesn't remember recently used file type to save? This really annoying for me. I prefer one type and Spectacle forces different and every time I need to change it. STEPS TO REPRODUCE 1. make any screen shot 2. invoke "Save as" and select different file type 3. click "Save" 4. make another screen shot 5. invoke "Save as" and look at "File type" OBSERVED RESULT always the same default file type, set in configuration file EXPECTED RESULT recently used file type, alternatively switched by option in configuration and by default set as "recently used file type". SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85 Qt Version: 5.15.2 with kde patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441262] New: In Configure Digital Clock, Font Style is displayed incorrectly - always "Default"
https://bugs.kde.org/show_bug.cgi?id=441262 Bug ID: 441262 Summary: In Configure Digital Clock, Font Style is displayed incorrectly - always "Default" Product: plasmashell Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: 1.0 SUMMARY I opened Configure Digital Clock, and in Font Style field I found value calling "Default", so I assumed that this is font which is set in System Settings -> Font. I changed "Font Style" in "Configure Digital Clock" to different one, applied changes and was happy to have new font. Next day I turned one my PC, and font style in "Digital Clock" was the same, so great. Nevertheless I opened configuration, so "Configure Digital Clock" and noticed there there is again value "Default", no my previously set font. STEPS TO REPRODUCE 1. by RMB on Digital Clock open "Configure Digital Clock" 2. change value in field "Font Style" 3. apply changes, OK 4. restart your PC or relogin OBSERVED RESULT value "Default" in field "Font Style" EXPECTED RESULT recently set font name in field "Font Style" SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85 Qt Version: 5.12.2 with kde patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429249] Sending SMS doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=429249 --- Comment #14 from Piotr Mierzwinski --- (In reply to Simon Redman from comment #13) ... > > Attempt to read from field 'java.lang.String > > org.kde.kdeconnect.Helpers.TelephonyHelper$LocalPhoneNumber.number' on a > > null object reference > > Has already been fixed but is not yet in the release version: > https://invent.kde.org/network/kdeconnect-android/-/merge_requests/258 > > I'd be very happy for you both (and anybody else silently reading this) to > run the new version and get the logcat records and report whether or not it > works! Today I installed debug version which you suggested, retested and seems sending SMS works. Thanks a lot for fixing. I hope merge request will be soon accepted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #58 from Piotr Mierzwinski --- Created attachment 140783 --> https://bugs.kde.org/attachment.cgi?id=140783=edit ertical_Panel-Date.-2_68pix -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #57 from Piotr Mierzwinski --- Created attachment 140782 --> https://bugs.kde.org/attachment.cgi?id=140782=edit Vertical_Panel-Date.-1_70px -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #56 from Piotr Mierzwinski --- Created attachment 140780 --> https://bugs.kde.org/attachment.cgi?id=140780=edit System fonts settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #55 from Piotr Mierzwinski --- Issue still persists (for custom date: "ddd d"). When I increase panel to 70 pixels then (today date) "pon.16" fits to panel width, if it has 68 pixels width I get wrapped date, so "pon." in one line, and "16" in second (check attached screen shot). Size of date font seems to be the same like time. I think that date and time should be scaled when I increase and decrease panel width, just to fit panel width. It doesn't happen. I checked this also in up-to-dated KDE Neon. and behavior is the same. My system font is "Noto" (for more details please check screenshot) Plasma 5.22.4 KFrameworks 5.85 Qt 5.15.2 (with kde patches) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429249] Sending SMS doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=429249 --- Comment #12 from Piotr Mierzwinski --- (In reply to Ori B from comment #10) > (In reply to Piotr Mierzwinski from comment #9) > > > For those with this problem, are you trying to send a message to your own > > > number? > > Sorry? I don't get you. How can I send any message to my own number if my > > number is assigned to device what actual sends message? > > In my phone I can send an SMS to myself, it shows up as a received message a > moment later and it's a good way to test. That's what I was trying to do but > from kdeconnect. What's happening for me now, with the latest kdeconnect, is > that an SMS to myself fails silently. I'm not sure how you did it, so I tried to do it like below: 1st way: I entered my phone number (9 digits) in field 'Filter' and clicked 'New'. In result number appeared in list below. I clicked into it and entered messaged and pressed Enter. In result happened nothing. 2st way: I entered my phone number (+country_prefix concatenated with 9 digits) in field 'Filter' and clicked 'New'. One was added number without "+"... After pressing Enter in message field happened nothing. Notice please. This is not so much important because I can send any test message to my friend. > > Let me know please what should I do to provide some logs from phone, > > assuming that an issue happens in Android application. > > Sure thing. You can set up adb (Android debugging), instructions for that > are online and the simplest method involves plugging the phone to your > computer with a USB cable. Then run the command "adb logcat" from a terminal > window and you'll have a stream of all log messages coming from your phone. > Ctrl+C in that terminal to stop that process soon after you've tried sending > a message. OK. Thanks for helpful info. I did what you described and in result got info about crashed application - very similar to one provided by Charis Mitsakis. 08-16 19:57:33.953 3851 13715 W Sending message: Unable to get outgoing address for sub ID 1 using null 08-16 19:57:33.959 3016 12719 D TelephonyProvider: subIdString = 1 subId = 1 08-16 19:57:33.977 3851 13715 E Sending message: Exception 08-16 19:57:33.977 3851 13715 E Sending message: java.lang.NullPointerException: Attempt to read from field 'java.lang.String org.kde.kdeconnect.Helpers.TelephonyHelper$LocalPhoneNumber.number' on a null object reference 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Plugins.SMSPlugin.SmsMmsUtils.sendMessage(SmsMmsUtils.java:158) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Plugins.SMSPlugin.SMSPlugin.onPacketReceived(SMSPlugin.java:413) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Device.onPacketReceived(Device.java:570) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Backends.BaseLink.packageReceived(BaseLink.java:70) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.receivedNetworkPacket(LanLink.java:249) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0(LanLink.java:97) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.LanLink.lambda$reset$0$LanLink(Unknown Source:0) 08-16 19:57:33.977 3851 13715 E Sending message: at org.kde.kdeconnect.Backends.LanBackend.-$$Lambda$LanLink$u8LWlVA_uGoxlkxdXMbWulE13kY.run(Unknown Source:4) 08-16 19:57:33.977 3851 13715 E Sending message: at java.lang.Thread.run(Thread.java:764) KDE Connect (Android) 1.17.0 KDE Connect (Plasma) 21.08.0 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 429249] Sending SMS doesn't work at all
https://bugs.kde.org/show_bug.cgi?id=429249 --- Comment #9 from Piotr Mierzwinski --- (In reply to Ori B from comment #8) > I was having the same problem with the CLI and the widget for sending SMS > messages. I've installed the latest version and at first thought the issue > remains, but then realized it's silently /not/ sending messages to the > device's own phone number. It did work for sending messages other contacts. > For those with this problem, are you trying to send a message to your own > number? Sorry? I don't get you. How can I send any message to my own number if my number is assigned to device what actual sends message? Therefore no, I didn't try to send any message to my own number! or I didn't understand you As I said I tried to send SMS to any person from my contacts list what KDE Connect SMS loads from my phone, so I do following things: 1. I select one contact (history of conversation is loading in KDE Connect SMS) 2. Click into "Compose messages" 3, Enter any message and press Enter or click "Send" In result happens nothing, or actually field where I put message freezes. Clicking in other contact unfreezes it. Notice that when I try to send SMS my phone is unlocked. Let me know please what should I do to provide some logs from phone, assuming that an issue happens in Android application. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 --- Comment #8 from Piotr Mierzwinski --- I tested this also in Neon updated at Jul, 24th 2021 (details belwow) and noticed that when I close kate with not saved file then it doesn't ask me for saveing this file. The same is happen when I have in kate not saved file and try to logoff or shutdown the system. Nice. Only the problem is that after kate starts with new session of Plasma then changes made before closing are not restored, so nothing was swapped in moment on kate was closed. Second thing is that this (not asking for file save not saved file) works only in Kate. When I tried to do the same with kwrite, it asked me for saveing file. Please notice that I had the same setting in both. Kate 21.11.70 Plasma 5.22.80 Framework 5.85 Qt-5.15.3 Graphics X11 Kernel 5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 --- Comment #7 from Piotr Mierzwinski --- kio 5.84 kio-fuse 5.0.1 kdesdk-kioslaves 21.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 Piotr Mierzwinski changed: What|Removed |Added Version|unspecified |21.04.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 --- Comment #6 from Piotr Mierzwinski --- Created attachment 140202 --> https://bugs.kde.org/attachment.cgi?id=140202=edit kwrite - File Opening & Saving-2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 Piotr Mierzwinski changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #5 from Piotr Mierzwinski --- I'm not sure if bug which was linked with this one and fixed (at March), so Bug 353654 is actually related with this issue. Anyway still I experience behaviour described below . I mean every time kwrite asks me for saving, not saved document, when I close application or when try to log off or turn off my PC. Of course swap file option is turned on (check attached screen shot). I tested with default location and selected one. I tested this on newly created user. KWrite 21.04.3 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 (with KDE patches) Kernel Version: 5.12.15-arch1-1 (64-bit) Graphics Platform: X11 Operating System: Antergos Linux -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 385275] When exiting the application don't force user to save, unsaved document only save it as temporary
https://bugs.kde.org/show_bug.cgi?id=385275 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #4 from Piotr Mierzwinski --- Created attachment 140201 --> https://bugs.kde.org/attachment.cgi?id=140201=edit kwrite - File Opening & Saving -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #8 from Piotr Mierzwinski --- (In reply to tagwerk19 from comment #7) > (In reply to Piotr Mierzwinski from comment #5) > > Anyway I went to command line and called following commands: > > $ balooctl enable > > Enabling and starting the File Indexer > > > > .. and after couple seconds this one: > > $ balooctl status > > Baloo File Indexer is not running > > ... > It's possible you need to enable twice... There are times (Bug 435315) that > saying it once is not enough. Yes I did it couple time, but without effect. > > ... Seems baloo failed (maybe because of broken links what I > > have in home directory), and stopped indexing before has found my newly > > created file ... > Broken links? as in symbolic links pointing nowhere? I think baloo makes a > deliberate choice not to follow links. It relies on a one-to-one mapping > between the full filename and an internal ID (which is built from the device > number of the disc/partition and the inode). A symbolic link could make that > a many-to-one mapping. OK. So maybe files without permission to read? If not then I don't know what is the reason this failed. > I'd suggest as a next step, open a couple of windows and run > balooctl monitor > in one. That should show you what "baloo is doing" in terms of files > indexed. In the second try first the > balooctl enable > and then a > balooctl check > The latter prompts baloo to scan through the filesystem looking to see if > there are any files it has missed. OK. I started all commands you suggested. Below please find result: $ balooctl monitor Waiting for file indexer to start Press Ctrl+C to stop monitoring File indexer is running Starting Checking for stale index entries Waiting for file indexer to start Press Ctrl+C to stop monitoring > > $ balooctl failed > > The following files could not be indexed: > > > > > > > > > > > > > > > > > > > > $ balooctl status > Ooo... Just to make sure I've not missed anything. You've not been running > (and updating) this system for a long time? Sorry? What do you mean? I update my system every day, and even couple times. I have Linux Arch based distribution (Antergos, migrated to Arch repositories). $ pacman -Q baloo baloo 5.84.0-1 > There is a bug about a fix to the database sometime back and the need to > reindex now it's fixed > (Bug 431664). In this case you'd need to do a > balooctl purge OK. I did it and another to start indexing, so: $ balooctl enable > and have a cup of coffee... (you will be able to see the files listed as > they are indexed listed in the monitor) After some time it was finished and in GUI I found: "Status Idle, 100% complete [Pause Indexer]" BTW. Is this button saying "pause" is a bug? Because indexing finished. And of course this time I was able to find my file in Dolphin :). > Did I cover everything? Yes. I think you did. Big thanks for help. Seems purge was the solution for this issue. But still don't know why indexing stuck and what files cased this. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 --- Comment #6 from Piotr Mierzwinski --- Created attachment 140104 --> https://bugs.kde.org/attachment.cgi?id=140104=edit file-search_settings-2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|NOT A BUG |--- --- Comment #5 from Piotr Mierzwinski --- (In reply to tagwerk19 from comment #4) > (In reply to Piotr Mierzwinski from comment #0) > > Created attachment 140099 [details] > This says > Status: Not Running, 0% complete > > If baloo was stopped it would not notice and index files you've just added. > It could be you are seeing Bug 436352, where the indexer is paused but the > button still says "Pause Indexer". > > You can try a "balooctl status" from the command line to see what it thinks > the state of the indexer is or press the "Pause Indexer" button. Ups. I didn't notice that status was "Not running, 0% complete" Maybe I met Bug 436352, but in File Search I clicked nothing. I met status like on first screen shot just after I wanted to check file search status. Notice that when I click into button "Pause Indexer" then happens nothing - no any message changes in "File Search" window. It looks like on screen shot: "file-search_settings-2.png". Anyway I went to command line and called following commands: $ balooctl enable Enabling and starting the File Indexer .. and after couple seconds this one: $ balooctl status Baloo File Indexer is not running Total files indexed: 50,045 Files waiting for content indexing: 1 Files failed to index: 10 Current size of index is 345.79 MiB In attachment please find screenshot of search setting with strange message looking like a bug. Seems baloo failed (maybe because of broken links what I have in home directory), and stopped indexing before has found my newly created file. And info in GUI was: Status: Not running, 99% complete Currently indexing !% (I18N_ARGUMENT_MISSING) After restart of System Settings window, and checking "File Search" I found the same like on first screen shot. I wanted to know which files failed (cannot be indexed:), so I called: $ balooctl failed The following files could not be indexed: $ balooctl status [the same like above] Hmm. As you can see, is missing information I requested by command. Of course still I cannot find my file. Notice that ~/Documents is not symlink only regular folder. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #3 from Piotr Mierzwinski --- Ok. I retested it on different account and turned out that searching works. Only from some unknown reason it doesn't work on my regular account. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 --- Comment #2 from Piotr Mierzwinski --- Created attachment 140101 --> https://bugs.kde.org/attachment.cgi?id=140101=edit dolphin - search 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 140100 --> https://bugs.kde.org/attachment.cgi?id=140100=edit dolphin - search 1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] New: Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Bug ID: 439909 Summary: Searching in current directory doesn't work alt all Product: dolphin Version: 21.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140099 --> https://bugs.kde.org/attachment.cgi?id=140099=edit file search - options SUMMARY I opened directory "~/Documents" to find file which I recently saved here. I was very surprise when after using Ctrl+F and putting name of this file I saw blank view. I closed it and started search manually, just typing first letters. I found my file in this way. I wonder why I wasn't to do it by "Search" option. I thought that maybe baloo didn't update its index yet for this directory, so I also tried to do it next day. Unfortunately with the same result. Notice that "File Search" is turned on (details on the screen shot). Some time ago I added my home directory, and found it there with status "indexed". I also added several other directories, which are "Not indexed", because they are mounted by nfs. In this list there is no "~/Documents" Additionally I tried to find file which is present in my home directory (which has status "Indexed"). Result the same as previously - blank view. Because of this my conclusion is: searching in dolphin doesn't work. STEPS TO REPRODUCE 1. Add your home directory to be indexed to "Search settings" 2. Save any file in ~/Documents, for example "my_document.pdf" 3. open dolphin, and go to "~/Documents" directory 4. press "Ctrl+F" and paste name of your file OBSERVED RESULT blank view EXPECTED RESULT file which was searched SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84 Qt Version: 5.15.2 with latest kde patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] When a device connects, it is positioned too far down for a moment, causing it to overlap the separator line
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #14 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #13) > Yeah it's that line, but without it, the loader for the section delegate > that we're trying to hide is invisibly there with too much height. > > Can't figure it out right now, giving up. Hopefully someone smarter than me > can figure it out. Thank you for your effort. I think this was redesigned comparing to 5.21, so maybe author this change will be know something more. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #10 from Piotr Mierzwinski --- Created attachment 139396 --> https://bugs.kde.org/attachment.cgi?id=139396=edit how-to-achieve-incorrect-separator-in_blutooth -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #9 from Piotr Mierzwinski --- Created attachment 139394 --> https://bugs.kde.org/attachment.cgi?id=139394=edit plasma-bluetooth-separating_line (incorrect)-Neon -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #7 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #6) I'm not sure, but I think you are doing something wrong and that's why you cannot replicate it. I just did it on KDE Neon (Unstable edition) using newly created user account. So having couple BT devices please click "Connect" on first and immediately click into desktop. After connection will be established please open Bluetooth panel. I will attach another screen shot coming from Neon. Plasma 5.22.80; Style: ROUNDED COLOR; Color: Dark Breeze; Font: Noto Sans 10pt with forced DPI (120) KF 5.83 Qt 5.15.3 X11 Let me know if you need more details. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438627] tabs in dark mode have barely visible contrast
https://bugs.kde.org/show_bug.cgi?id=438627 --- Comment #4 from Piotr Mierzwinski --- Created attachment 139350 --> https://bugs.kde.org/attachment.cgi?id=139350=edit tabs, kvantum dark (konsole) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438627] tabs in dark mode have barely visible contrast
https://bugs.kde.org/show_bug.cgi?id=438627 Piotr Mierzwinski changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #2) > The blue line is intended to be a contrast enhancer. I gather that's not > good enough for you? Yes. I think is not enough. In my opinion comparing to bright mode this is very poor contrast. And blue line barely marks the contrast in tabs. I think bright mode seems to be more polished in this case. When I run my eyes over the cards is easier for me to find active card when it contrasts enough, even if font in title contrasts then is easier to find such tab. In dark mode in Breeze this doesn't happen. We have only workaround like mentioned line. And because of this sometime ago I started to use dark kvantum style, where I have brigher font for active tab and darker for not active tab. Please check attached screenshot. I think this makes better contrast than line drowing on top or bottom of tab. Notice please that line might be unnoticed under certain circumstances, for example when something in similar color will be placed in very close this line. In my humble opinion this doens't happen if we have better contrast of background like in bright mode or if title is drawn brighter for active or darker for not active tab, if contrast of background for both types of them is worse, like current situation. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 Piotr Mierzwinski changed: What|Removed |Added Resolution|FIXED |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #5 from Piotr Mierzwinski --- Created attachment 139346 --> https://bugs.kde.org/attachment.cgi?id=139346=edit Plasma-font -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 Piotr Mierzwinski changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #3) > Works for me. What font and font size are you using? Are you overriding the > font DPI in any way? Fixed width: Hack 10pt All other: Noto Sans 10pt DPI is not overridden. Other details in attached screen. As I mentioned for me also works, but only when I wait till connection will be established, otherwise always this line is drawn in incorrect place (as in attachment). -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438614] Not disappearing popup menu after choosing option
https://bugs.kde.org/show_bug.cgi?id=438614 --- Comment #4 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #1) > This is a behavior provided by the upstream QMenu component and it's not > something we can override in any KDE code. You would need to report it to > the Qt people. I thought that KDE just implemented own extended popup menu, which just inherit from QMenu. But from what you are saying, didn't. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438614] Not disappearing popup menu after choosing option
https://bugs.kde.org/show_bug.cgi?id=438614 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Resolution|UPSTREAM|FIXED --- Comment #3 from Piotr Mierzwinski --- (In reply to Kai Uwe Broulik from comment #2) > I thought you could hold shift while clicking so the menu doesn't close but > maybe that was a Windows thing I tested this and doesn't work. Holding Shift key doesn't help at all - menu just disappear. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438627] tabs in dark mode have barely visible contrast
https://bugs.kde.org/show_bug.cgi?id=438627 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 139314 --> https://bugs.kde.org/attachment.cgi?id=139314=edit tabs, breeze high contrast -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438627] New: tabs in dark mode have barely visible contrast
https://bugs.kde.org/show_bug.cgi?id=438627 Bug ID: 438627 Summary: tabs in dark mode have barely visible contrast Product: Breeze Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- Created attachment 139313 --> https://bugs.kde.org/attachment.cgi?id=139313=edit tabs, dark color SUMMARY As in subject. For details please look at attached screen shots. Using Application style Breeze and color "Dark Breeze" I observe barely visible contrast between active and not active tabs. Notice please that using color: "Breeze High Contrast" doesn't help. Actually this nothing changes. BTW. Checking views in System Settings (i.e. for Plasma Styles) with this color as current we experience even less contrast for highlight. STEPS TO REPRODUCE 1. start konsole or dolphin and open couple tabs 2. look at the contrast between active and not active tab 3. OBSERVED RESULT contrast between active and not active tab is barely visible EXPECTED RESULT contrast between active and not active tab should be more visible, at least like it happens in bright style SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 (+kde patches) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 438614] New: Not disappearing popup menu after choosing option
https://bugs.kde.org/show_bug.cgi?id=438614 Bug ID: 438614 Summary: Not disappearing popup menu after choosing option Product: Breeze Version: 5.22.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY As in subject. I mean situation when in popup menu are placed options type 'check box'. In this case I need to click several time to set all needed options. I mean I need every time open popup menu and click into proper option (check box) to have checked all options, because after first click popup menu disappears. Notice please that there is no issue if popup menu disappears in case we have 'radio button', but not useful if we need to check radio button + check box or couple check boxes. This action needs a lot of clicking. STEPS TO REPRODUCE 1. open any popup menu with check boxes 2. click into first option type 'check box' 3. OBSERVED RESULT popup menu disappears EXPECTED RESULT popup could not disappears to give user possibility to check another option SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22 KDE Frameworks Version: 5.83 Qt Version: 5.15.2 (+kde patches) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 --- Comment #2 from Piotr Mierzwinski --- In case of bright plasma I used Plasma Style calling: Breeze In case of dark plasma I used Plasma Style calling: ROUNDED COLOR -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438610] Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 139307 --> https://bugs.kde.org/attachment.cgi?id=139307=edit plasma-bluetooth-separating_line (incorrect,dark) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438610] New: Line which separates devices in Bluetooth panel crosses out connected device
https://bugs.kde.org/show_bug.cgi?id=438610 Bug ID: 438610 Summary: Line which separates devices in Bluetooth panel crosses out connected device Product: plasmashell Version: 5.22.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 139306 --> https://bugs.kde.org/attachment.cgi?id=139306=edit plasma-bluetooth-separating_line (incorrect) SUMMARY I have paired couple BT devices. After connecting device to bluetooth, line which separates them in Bluetooth panel partially crosses out connected device when I close it (panel) before connection has been established. If I will wait till connection will be established this line is correctly displayed. Details please find in attached screenshot. STEPS TO REPRODUCE 1. Click connect in Bluetooth panel/applet 2. Don't wait till connection will be established only click into desktop, closing Bluetooth panel 3. If connection becomes established open Bluetooth panel 4. Look at separating line OBSERVED RESULT line partially crosses out connected device EXPECTED RESULT line should not cross out connected device SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22 KDE Frameworks Version: 5.82 Qt Version: 5.15.2 (+kde patches) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438433] New: KDevelop crashed after applied settings in Plugins configuration
https://bugs.kde.org/show_bug.cgi?id=438433 Bug ID: 438433 Summary: KDevelop crashed after applied settings in Plugins configuration Product: kdevelop Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- Application: kdevelop (5.6.40) Qt Version: 5.15.3 Frameworks Version: 5.83.0 Operating System: Linux 5.4.0-74-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.80 Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: Turned off couple plugins, like file manager, Subversion and couple more. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [New LWP 1464] [New LWP 1841] [New LWP 1481] [New LWP 6654] [New LWP 1843] [New LWP 1840] [New LWP 1842] [New LWP 1838] [New LWP 1837] [New LWP 6658] [New LWP 6656] [New LWP 6657] [New LWP 1495] [New LWP 6640] [New LWP 1556] [New LWP 1494] [New LWP 1578] [New LWP 1492] [New LWP 1844] [New LWP 6655] [New LWP 1613] [New LWP 6659] [New LWP 1839] [New LWP 1836] [New LWP 1647] [New LWP 1493] [New LWP 1501] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/kdevelop -session 10bfb8cad200016233506730011750017_1623352347_401'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f6ace5ea240 (LWP 1464))] [Current thread is 1 (Thread 0x7f6ace5ea240 (LWP 1464))] Thread 27 (Thread 0x7f6abb7fe700 (LWP 1501)): #0 0x7f6ae4964aff in __GI___poll (fds=0x7f6aac014450, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6ae127336e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ae12734a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ae4f32b22 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6ae4ed6dcb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6ae4cf0bb2 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6ae5969f4b in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f6ae4cf1d4c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6ae1c85609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f6ae4971293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7f6ac10fe700 (LWP 1493)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5598204ed358) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5598204ed308, cond=0x5598204ed330) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5598204ed330, mutex=0x5598204ed308) at pthread_cond_wait.c:638 #3 0x7f6ac6d5eb5b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f6ac6d5e75b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f6ae1c85609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6ae4971293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7f6a85333700 (LWP 1647)): #0 0x7f6ae4964aff in __GI___poll (fds=0x7f6a6c0044d0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6ae127336e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6ae12734a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6ae4f32b22 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6ae4ed6dcb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6ae4cf0bb2 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6ae398e0c0 in () at /lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.57 #7 0x7f6ae4cf1d4c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6ae1c85609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f6ae4971293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f6a72255700 (LWP 1836)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x559820c616b4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x559820c61660, cond=0x559820c61688) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x559820c61688, mutex=0x559820c61660) at pthread_cond_wait.c:638 #3 0x7f6ae4cf7ebb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6ae1208f40 in
[kate] [Bug 436636] New: Swap file doesn't work after restoring Plasma session
https://bugs.kde.org/show_bug.cgi?id=436636 Bug ID: 436636 Summary: Swap file doesn't work after restoring Plasma session Product: kate Version: Git Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY I set option "Swap file" as "Enabled" in second case as "Alternative Directory". In both cases after I restored Plasma session, where kate was restored with its last session, I got not swapped file. Both options were worked if I closed kate manully and started it again. STEPS TO REPRODUCE 1. open any file 2. set option: Configuration -> Open/Save -> Advanced -> Swap file: "Enable" or "Alternative Directory" (with proper path) 2. modify opened file 3. Log out from Plasma or restart system OBSERVED RESULT kate loads original, not mofied file EXPECTED RESULT kate should load swapped file, like it happens in case if user close application manually and run it again SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 kate: 21.07.70 ADDITIONAL INFORMATION Neon updated today (2021/04/05) afternoon. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 --- Comment #12 from Piotr Mierzwinski --- (In reply to Waqar Ahmed from comment #10) > Another reason and I think this is the main reason for not doing more > coloring is because we don't have that big of a color palette. A usual color > scheme has about 5 - 7 colors, of which one is normal text. We simply can't > change this because it's not in our hands, so we have to work with this. Sorry? You don't have such bgi of color palette? So how semantic highlighting implemented in KDevelop manges color palette? I think it uses shades of colors to increase palette. Isn't possible to do it in Kate? You have 5-7 colors, but I think is possible use shades of color for each of them. I don't understand what is not in your hands? That there is available only 5-7 colors. Not all need to be in completely different color. > Introducing hard Coded colors like kdevelop is not an option. And is is solution also. We do not have to be condemned to 7 colors. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 --- Comment #11 from Piotr Mierzwinski --- > 1. We don't color all the information provided by clangd at the moment, some > is ignored. > This was intentionally done by me to not color everything there is in the > source file. What gets > In my opinion semantic highlighting in KDevelop significantly increase readability of code. I consider this is the pattern of how it should work. Readability of code, thanks to usage of semantic highlighting is very important, at least for me. Why you don't color all the information provided by clangd ? Is this technical reason or any different? Why this cannot be configurable like in KDevelop where we can increase/decrease its intensity? And I don't understand if you don't want to achieve or even pursue level of semantic highlighting provided by KDevelop or this is impossible because of some technical reasons. > 2. Even with semantic token API things will likely not change. So seems I misunderstood what Christoph said about this API. Notice please, he considered this solution like temporary. And to be honest, after usage mentioned API and semantic tokens, I expected better highlighting in Kate, which will be comparable to one is present in KDevelop . I know it uses different way do it. Anyway tell me please what will bring new API and support for semantic tokens? And last thing, which was reported here as a bug. Should I understand that local variables will be not colored in future version of Kate, I mean in such way that each of them has different color, like in KDevelop? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 --- Comment #8 from Piotr Mierzwinski --- Created attachment 138017 --> https://bugs.kde.org/attachment.cgi?id=138017=edit kdevelop-semantic highlighting -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 --- Comment #7 from Piotr Mierzwinski --- Created attachment 138016 --> https://bugs.kde.org/attachment.cgi?id=138016=edit kate-21.04 semantic highlighting -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 Piotr Mierzwinski changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #6 from Piotr Mierzwinski --- Since some time I have Kate 21.04, so I decided to test this fix. In my humble opinion this fix (considered as temporary) doesn't work at all. Local variables still have the same colour! Only one change I noticed is that types changed colour to much brightest (for dark theme ), so they are more readable. Only this wasn't reported here as issue. Please check attached screenshot and compare to one took from KDevelop. I assume that we need to wait "we are able to support for new API and till LSPs themselves add proper support for offical semantic tokens." SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 (with KDE patches) KApplications 21.04 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 398035] Crash in Overview mode after invoking "Find/Replace in Files" option
https://bugs.kde.org/show_bug.cgi?id=398035 Piotr Mierzwinski changed: What|Removed |Added Version|5.6.1 |5.6.2 --- Comment #6 from Piotr Mierzwinski --- Issue still persists in the newest stable version. Today I met this again. Usage "Find in file" being in mode "Show Differences" made crash. Operating System: Antergos Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.11-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f39148a8c5e in () at /usr/lib/libQt5Core.so.5 #5 0x7f39148aa28d in QRegExp::operator=(QRegExp const&) () at /usr/lib/libQt5Core.so.5 #6 0x7f38e25c593e in () at /usr/lib/qt/plugins/kdevplatform/34/kdevgrepview.so #7 0x7f38e25c95e0 in () at /usr/lib/qt/plugins/kdevplatform/34/kdevgrepview.so #8 0x7f3914a44532 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f39156af752 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f3914a17a2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #11 0x7f3914a1a523 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #12 0x7f3914a71054 in () at /usr/lib/libQt5Core.so.5 #13 0x7f39110edf9c in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #14 0x7f3911141a49 in () at /usr/lib/libglib-2.0.so.0 #15 0x7f39110eb6f1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #16 0x7f3914a70691 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7f3914a163ac in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #18 0x7f3914a1e844 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #19 0x5569a9e2f3b1 in () #20 0x7f39143ddb25 in __libc_start_main () at /usr/lib/libc.so.6 #21 0x5569a9e300de in _start () [Inferior 1 (process 1375) detached] -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 434797] New: Dolphin blocks 'Safety remove' of external storage
https://bugs.kde.org/show_bug.cgi?id=434797 Bug ID: 434797 Summary: Dolphin blocks 'Safety remove' of external storage Product: dolphin Version: 21.03.80 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I connect external hard drive to my laptop with Neon distribution. In Dolphin appears proper entry I click into it and in /media/neon get mounted resource calling (in my case) "My Passport". I open couple media files and close it after some time. Sometime I open in also in Midnight Commander. After I finish I got out from mounted media directory and in Dolphin I change director, or even close it. Now when I try to "Safety remove" my external storage in Dolphin I get error message saying that "One or more files on this device are open within an application.". Trying to rid off this message I close all my applications and run Dolphin again with Home directory. Now again try to "Safety remove", but it doesn't help. Error still persists Please notice that error message is not so clear, because says about some files. User don't know which file or directory is opened. The worse is I cannot unmount resource. Quick investigation brings me the answer that resource is blocked by library calling "file.so". I suppose Dolphin use it and it is not unload from some unknown reason. Just after I kill the process, I'm able to "Safety remove" (unmount) resource. Investigation relies on calling command lsof, what in my case looks like this: $ lsof | grep media file.so2193 neon5r REG 8,49 328056931 130881 /media/neon/My Passport/Piotrek/video/my_movie.mp4 STEPS TO REPRODUCE 1. Via USB connect external storage 2. Open it in Dolphin clicking into entry showed in left panel "Places" 3. Open couple media files, for example movies, and close them 4. Change directory in Dolphin and restart it 5. Try to "Safety remove" connected storage in Dolphin OBSERVED RESULT Error message saying that "One or more files on this device are open within an application." caused by library: "file.so". EXPECTED RESULT User should be able to "Safety remove" (unmount) connected storage when any file or directory in opened in any application he used. Here Dolphin or mc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.80 KDE Frameworks Version: 5.80.0 (or current in Neon) Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #52 from Piotr Mierzwinski --- Created attachment 136954 --> https://bugs.kde.org/attachment.cgi?id=136954=edit Date-scalled corectly -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #51 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #50) > I'm not suggesting that you increase the width as a fix; I'm trying to > understand whether that workaround still works. If it does, then this bug is > not fully fixed and we can re-open it. If it does not, then the issue you're > seeing is in fact a slightly different bug, and we should leave this one > closed and file a new one to track the fix for that. > > Does that make sense to you? Sorry for misunderstanding, now I found you asked for resize panel to check if problem still persists. I increased width and got date in one line. For example today the day is displayed correctly (with original width of panel) - check attached screenshot. The issue happens only when Sunday happen and day has number contains 2 digits for other is fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 Piotr Mierzwinski changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #49 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #48) > It is working fine for me. Does the problem go away if you manually resize > the panel, as I asked before? Can you please attach a screen recording that > shows this? For me also works, but only at days different than Sunday and with 1 digit in day number. I suppose you have locale "US", so your names of day are shorter and thanks that always names fit originaly set panel width. Please use PL, and check date at Sunday, then you will see date in two lines instead of one. Suggesting increase width in my opinion is not solution only workaround. To be honest I expected decrease size of font, which still cannot be be decreased/increased in configuration. Please notice that polish translators cannot change this name of day to be shorter, like for example with "Nie", just because this word has own meaning in our language and means "No". I'm not 100% sure, but I think that in calendars in an English-speaking country the short for November isn't "No", only "Nov", to avoid misleading. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 Piotr Mierzwinski changed: What|Removed |Added Status|NEEDSINFO |REOPENED Resolution|WAITINGFORINFO |--- --- Comment #47 from Piotr Mierzwinski --- Reopened due to fix doesn't work in the newest stable version. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #46 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #45) > What version of Plasma are you using? This looks like it might be a separate > issue. Does manually resizing the panel fix it? Operating System: Antergos Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.7-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 --- Comment #44 from Piotr Mierzwinski --- Created attachment 136932 --> https://bugs.kde.org/attachment.cgi?id=136932=edit Dante incorrectly scaled -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417852] Date in vertical panels is too big until panel is manually resized
https://bugs.kde.org/show_bug.cgi?id=417852 Piotr Mierzwinski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #43 from Piotr Mierzwinski --- Seems scaling of date still doesn't work correctly. Please look at attached screenshot. Please notice that others day are correctly displayed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 434622] Error messages disappear very quickly when update of addons
https://bugs.kde.org/show_bug.cgi?id=434622 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 136845 --> https://bugs.kde.org/attachment.cgi?id=136845=edit addons to update - errors -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 434622] New: Error messages disappear very quickly when update of addons
https://bugs.kde.org/show_bug.cgi?id=434622 Bug ID: 434622 Summary: Error messages disappear very quickly when update of addons Product: Discover Version: 5.21.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: piotr.mierzwin...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 136844 --> https://bugs.kde.org/attachment.cgi?id=136844=edit addons to update SUMMARY When I update addons by Discover the errors happen from time to time, due to many reasons. Discover reports them in details, only the issue is that them disappear very quickly and I'm not able to get full message. STEPS TO REPRODUCE 1. Turn on "Application Addons" view 2. Try to update addons which cases errors during update, for example "Classic Color Icons" (provided via deb, and I use Arch distio). 3. OBSERVED RESULT Error messages cover part bottom part of application (details in attached screenshot) and disappear quickly - One by one, not giving user any chance to copy error message, or read it fully. EXPECTED RESULT Errors messages should be show in way as in other KDE application, where user can close appeared on bottom of window any error message. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Discover version: 20:12.3 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431014] LSP Client. In dark mode some types has very low contrast (are too dark)
https://bugs.kde.org/show_bug.cgi?id=431014 --- Comment #7 from Piotr Mierzwinski --- (In reply to Waqar Ahmed from comment #6) > Please wait for "Kate 21.04" release to come out or build from source. Sorry, for reopening. Message from Christoph was a bit misleading. He said: "..., this change will only work for KF > 5.79.", so I tested after got KF-5.80 Thanks for info. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 Piotr Mierzwinski changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Piotr Mierzwinski --- Seems this fix doesn't work. Yesterday I got update with KF-5.80. Today tested Kate. Result please find in attache screenshot. Local variables still are not coloured differently - all are white. Color Scheme is "Breeze-Dark" Color Theme is "Breeze-Dark" -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431011] LSP Client.Local variables/members are not highlighted (all in one color)
https://bugs.kde.org/show_bug.cgi?id=431011 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #3 from Piotr Mierzwinski --- Created attachment 136715 --> https://bugs.kde.org/attachment.cgi?id=136715=edit kate-dark-mode-with-LSP -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431014] LSP Client. In dark mode some types has very low contrast (are too dark)
https://bugs.kde.org/show_bug.cgi?id=431014 Piotr Mierzwinski changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #5 from Piotr Mierzwinski --- Seems this fix doesn't work. Yesterday I got update with KF-5.80. Today tested Kate. Result please find in attache screenshot. Types have still the same colour. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431014] LSP Client. In dark mode some types has very low contrast (are too dark)
https://bugs.kde.org/show_bug.cgi?id=431014 --- Comment #4 from Piotr Mierzwinski --- Created attachment 136714 --> https://bugs.kde.org/attachment.cgi?id=136714=edit kate-dark-mode-with-LSP -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 358801] Formatter removes all white characters placed between type of function and its name
https://bugs.kde.org/show_bug.cgi?id=358801 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Piotr Mierzwinski --- In the newest KDevelop (5.6.2) mentioned function is still missing. Nevertheless I consider this as very minor issue and just close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 294583] Incorrect cpp signature update when I add const to method
https://bugs.kde.org/show_bug.cgi?id=294583 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #6 from Piotr Mierzwinski --- In the newest stable version of KDevelop (5.6.2) this seems works. The issue is that this partially work and quickly stops work (in the same class/file). Partially because, when we remove (newly added and adapted in definition) 'const' then happens nothing. And the worst is that since now feature adapting 'const' in definition stops work. Therefore if we will add const at end of declaration of method then happens nothing. Unless we switch to another file and here it will work, but only till we remove 'const'. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 255706] KDevelop does not rename a variable in method declaration, definition, and function body
https://bugs.kde.org/show_bug.cgi?id=255706 --- Comment #13 from Piotr Mierzwinski --- In the newest stable version of KDevelop (5.6.2) this seems to be broken. What happens in current version when we rename argument in the prototype from baz to baz1? 1. problem - is adding prefix of class name to the method, so here it would be: 'Foo::' and method would looks like: Foo::Bar(int baz1) ; all of this in prototype (header) file. 2. problem usage of argument is renamed in definition of method, so fine, but unfortunately doesn't in its declaration in method definition (header of definition). 3. problem. when we over renamed argument by mouse cursor in definition of method then all occurrences are highlighted, even this not renamed in header of definition. Fortunately to restore old names we can use Ctrl+Z. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 295683] 'Add private/public member' functionality made adding function to private/public slots except to private/public
https://bugs.kde.org/show_bug.cgi?id=295683 Piotr Mierzwinski changed: What|Removed |Added Resolution|FIXED |UNMAINTAINED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 295683] 'Add private/public member' functionality made adding function to private/public slots except to private/public
https://bugs.kde.org/show_bug.cgi?id=295683 Piotr Mierzwinski changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Piotr Mierzwinski --- Feature where I found this bug just disappeared. There is no proper status for this so I need to select 'RESOLVED'. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433974] Sematic highlighting stops work after insert one or more lines in the middle of code
https://bugs.kde.org/show_bug.cgi?id=433974 --- Comment #2 from Piotr Mierzwinski --- Thanks for very quick answer. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433974] Sematic highlighting stops work after insert one or more lines in the middle of code
https://bugs.kde.org/show_bug.cgi?id=433974 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Archlinux Packages CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433974] New: Sematic highlighting stops work after insert one or more lines in the middle of code
https://bugs.kde.org/show_bug.cgi?id=433974 Bug ID: 433974 Summary: Sematic highlighting stops work after insert one or more lines in the middle of code Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY Sematic highlighting stops work after insert one or more lines, but only in code present below inserted lines. Needs to refresh file to get proper sematic highlighting in opened file. I think this didn't happen in previous version, so seems to be regression. STEPS TO REPRODUCE 1. Open project with several files 2. Open couple files 3. After indexing finished try to modify one of them 4. In the middle of code insert one or more lines (with correct syntax) OBSERVED RESULT Sematic highlighting stops work in code below inserted lines and needs to refresh whole file EXPECTED RESULT Sematic highlighting should not stops work after inserting any lines SOFTWARE/OS VERSIONS Linux/KDE Plasma: Antergos/KDE (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I observed also this issue in today's version of KDevelop built from code coming from master branch: kdevelop-git-5.6.2.r288.g0ac533db1e KDE Application part in version 20.12.3 (among other: Kate, KWrite) -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 433973] New: After switching tab Scratchpad appears in the middle of screen as single window
https://bugs.kde.org/show_bug.cgi?id=433973 Bug ID: 433973 Summary: After switching tab Scratchpad appears in the middle of screen as single window Product: kdevelop Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY As in subject. Working of Scratchpad makes that KDevelop became almost unusable. Usually I work with KDevelop on full screen. Every time I switch tab with editor then in the middle of the screen appears single window of Scratchpad, or rather its ghost, because shows something like screen buffer under this window. I know this is Scratchpad, because when I click on toolbar with label Scratchpad then it disappears, only I switch to another editor then this ghost window appears covering 1/3 of screen. I turned off plugin in settings, but this didn't help. Scratchpad still appears. I uncheck Scratchpad in toolbar, but this also didn't help. Finally helped restart of KDevelop. STEPS TO REPRODUCE 1. Open several files or project with opened several files 2. Turn on plugin Scratchpad 3. Try to switch from one to another tab editor 4. Move mouse cursor OBSERVED RESULT In the middle of screen appears either normal Scratchpad window or its ghost (window buffer under window) EXPECTED RESULT Should not appear any window related with plugin when tads with editor are switched. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Antergos/KDE (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Issue also happens in today's version of KDevelopw coming from master branch: kdevelop-git-5.6.2.r288.g0ac533db1e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 432665] Cannot update all updateable stuff by one click only need to do it one by one
https://bugs.kde.org/show_bug.cgi?id=432665 --- Comment #2 from Piotr Mierzwinski --- (In reply to Dan Leinir Turthra Jensen from comment #1) > This is basically what Discover is for - updating your entire system to the > freshest bits everywhere :) I think you have too optimistic approach. It would be good a solution if Discover would be mature software, but isn't and because of this doesn't work well enough, yet. Why I think like that? Recently I discovered bug which was related with updating "stuff" (Bug 428423 and Bug 430812 ). Second one has been raised by developers and probably fixed. I cannot confirm. I didn't test this yet, because didn't happen my issued "stuff" (checked today). I'm not sure if you aware of this, so shortly - there was a problem if any package had couple sub-packages (often package of icons has sub-package with icons in different colour), and then Discover frozen progress. I looked like nothing wasn't updated, but in background was doing its job. Of course affected stuff didn't update. In Arch distribution I prefer different application - pamac, which is real package manager and here of course I can update my system. I don't want to install another application to be able to update my "stuff". IMO such option should be available in KNewStuff. Here I would like fully manage my "stuff" and not in different application. > That said, having the ability to update all the updateable things for a > specific knsrc file would probably be nice to have. It's not going to be a > very high priority, i'm afraid, but certainly it'd be useful functionality. > Resetting priorities and whatnot, and marking as confirmed :) Thank you for changing status this report. I wonder why if Discover is able to do it (update all) and KNewStuff doesn't. Anyway would be nice to have such possibility in place and not only in another application. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 432665] Cannot update all updateable stuff by one click only need to do it one by one
https://bugs.kde.org/show_bug.cgi?id=432665 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com Summary|Cannot update all |Cannot update all |updateable stuff only need |updateable stuff by one |to click one by one |click only need to do it ||one by one -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 432665] New: Cannot update all updateable stuff only need to click one by one
https://bugs.kde.org/show_bug.cgi?id=432665 Bug ID: 432665 Summary: Cannot update all updateable stuff only need to click one by one Product: frameworks-knewstuff Version: 5.78.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: piotr.mierzwin...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When I have several stuff to update I have to click one by one to update them and cannot just update all by one click. Please notice this is a bit annoying when we have a lot of stuff to update. STEPS TO REPRODUCE 1. Open Settings for any NewStuff, for example icons, themes or colors 2. Click Gen New 3. Click "Show Updateable only" 4. OBSERVED RESULT Missing button "Update All" EXPECTED RESULT Should be present button allowing of update all (updateable) stuff in given category SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.,15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 400293] REGRESSION: NFS root folder not writable with 18.08.2 because NFS ioslave claims root item isn't writable
https://bugs.kde.org/show_bug.cgi?id=400293 Piotr Mierzwinski changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #9 from Piotr Mierzwinski --- (In reply to Jonathan Marten from comment #8) > Is this actually using the NFS ioslave (via a URL starting > "nfs://serverhost/"), or a locally mounted NFS filesystem? If it is the > latter then it is handled via the file ioslave in the same way as any other > local file, and the appropriate component is either frameworks-kio or > dolphin. In my case, so Bug 429835 this was locally mounted NFS filesystem (by "mount -t nfs" command). I open such mounted directory in Dolphin. The issue was that in Dolphin I could not rename file whilst I was able to do it in mc, just because Dolphin says 'no write permission'. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 428423] Discover stuck with installation of Addons
https://bugs.kde.org/show_bug.cgi?id=428423 Piotr Mierzwinski changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Piotr Mierzwinski --- (In reply to utomas from comment #2) > I can reproduce same behaviour and I think I realise what might be happening. > > When you install an icon theme, for instance, it can have different versions > of it, a dark and a light version, or maybe different release version, so a > menu asking to choose a version appears. I think discover expects the same > and so it get stucks because is waiting for your choose which is not showing > on screen BTW. > > Sorry for my english :) This is original report, but I created also duplicated one (I forgot about this one) which has been took into account by developers and I thins issue has been fixed. I didn't test it yet, because no happened update for stuff which cased the issue for me. Please check Bug 430812 for details. And back to this report. You are right. Sometimes happens that exists two or more versions of the same package (dark and light or more colours), and Discover is not (or, considering Bug 430812, wasn't) able to match proper one, so didn't update an interface, but the update was still in progress, only we didn't see it. I was wrong saying that update stuck. After enough of time when we wait, update might pass with success. After we close Discover and open again turns out that system is up to date. I discovered that to unblock such stuck progress (in the middle of update), needs to open "System Settings" go to proper configuration, check update and in"New Stuff" tool and click update there. And then after back to Discover turns out that progress is showing correctly. Shortly. The issue was that Discover wasn't able to interpret correctly the answer from external system, and just not updated progress bar, but he skipped this package and was going further. I think this was fixed already. Check my another bug report. https://bugs.kde.org/show_bug.cgi?id=430812 I change status of this one as resolved, because this report is a duplication. *** This bug has been marked as a duplicate of bug 430812 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 430812] Installation of "stuff" which has sub-packages, where one need to be select, made that update of system is stopped
https://bugs.kde.org/show_bug.cgi?id=430812 --- Comment #10 from Piotr Mierzwinski --- *** Bug 428423 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
