[kate] [Bug 370243] New: Font is rendered differently in kwrite and konsole
https://bugs.kde.org/show_bug.cgi?id=370243 Bug ID: 370243 Summary: Font is rendered differently in kwrite and konsole Product: kate Version: 16.08 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: kokok...@gmail.com Liberation Mono 10,2 points is rendered way wider in kate/kwrite Reproducible: Always Steps to Reproduce: 1. Set xft dpi to 96 2. Select Liberation Mono 10,2 in kwrite and konsole (for kwrite you have to edit the value manually as seen in the attached screenshot,. (probably a different bug) Actual Results: See that the text in kwrite is wider. Expected Results: To have the font rendered in the very same way. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370243] Font is rendered differently in kwrite and konsole
https://bugs.kde.org/show_bug.cgi?id=370243 Antonio Orefice changed: What|Removed |Added CC||kokok...@gmail.com --- Comment #1 from Antonio Orefice --- Created attachment 101468 --> https://bugs.kde.org/attachment.cgi?id=101468&action=edit screenshot Kwrite on top, konsole on bottom, very same font and size, rendered differently. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370243] Font is rendered differently in kwrite and konsole
https://bugs.kde.org/show_bug.cgi?id=370243 --- Comment #3 from Antonio Orefice --- Thanks for the explaination, but wouldn't be more uniform/consistent to use the same setting (QFont::ForceIntegerMetrics) when kwrite is using monospaced fonts? As a side note, the same happens on the fonts kcm module when selecting the fixed width font (here, there is way to select a proportional font) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370243] Font is rendered differently in kwrite and konsole
https://bugs.kde.org/show_bug.cgi?id=370243 --- Comment #4 from Antonio Orefice --- Sorry, typo: As a side note, the same happens on the fonts kcm module when selecting the fixed width font (here, there is *NO* way to select a proportional font) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 370243] Font is rendered differently in kwrite and konsole
https://bugs.kde.org/show_bug.cgi?id=370243 --- Comment #6 from Antonio Orefice --- Ok, thanks for the detailed explaination (again!) -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 343061] Yakuake creates task list entry when being opened
https://bugs.kde.org/show_bug.cgi?id=343061 Antonio Orefice changed: What|Removed |Added CC||kokok...@gmail.com --- Comment #4 from Antonio Orefice --- Taskbar entry may or may not appear, it seems to be completely random. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 343061] Yakuake creates task list entry when being opened
https://bugs.kde.org/show_bug.cgi?id=343061 --- Comment #5 from Antonio Orefice --- Oh, and when it appears, it stays there till i hide yakuake. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370628] New: Allow to chose fractional font sizes
https://bugs.kde.org/show_bug.cgi?id=370628 Bug ID: 370628 Summary: Allow to chose fractional font sizes Product: systemsettings Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: kokok...@gmail.com CC: unassigned-b...@kde.org When the font dialog appears, it is not possible to use a decimal value for the font size. Reproducible: Always Steps to Reproduce: 1. open system settings 2. select a font 3. select size 10 4. edit the size field and write 10.2 Actual Results: Font is rendered at 102 points Expected Results: Font is rendered at 10.2 points manually editing kdeglobals, from: fixed=Liberation Mono,102,-1,5,50,0,0,0,0,0 to: fixed=Liberation Mono,10.2,-1,5,50,0,0,0,0,0 ..does indeed works As a side note, the same applies to other components too, like konsole, while kwrite/kate seems fine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370628] Allow to chose fractional font sizes
https://bugs.kde.org/show_bug.cgi?id=370628 --- Comment #2 from Antonio Orefice --- Thanks, done: https://bugreports.qt.io/browse/QTBUG-56547 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 371077] New: Unable to get the original text size after enlarging/shrinking it
https://bugs.kde.org/show_bug.cgi?id=371077 Bug ID: 371077 Summary: Unable to get the original text size after enlarging/shrinking it Product: kate Version: 16.08 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: kokok...@gmail.com When using a fractional point size as default value, enlarging it and shrinking it (ctrl++, ctrl+-) will not return to the original value. Reproducible: Always Steps to Reproduce: 1. Select a font (eg: 10) 2. Set a fractional point size that visually differs from the lower and upper integers (eg: 10,5) 3. return to the editor and write something 4. enlarge the font (ctrl++) 5. shrink the font (ctrl+-) Actual Results: Notice that the font is not rendered in the original size (eg 10,5) Expected Results: The font to be rendered in the original size (eg 10,5) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365102] New: Can't change "Desktop" font
https://bugs.kde.org/show_bug.cgi?id=365102 Bug ID: 365102 Summary: Can't change "Desktop" font Product: systemsettings Version: 5.6.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: kokok...@gmail.com CC: unassigned-b...@kde.org In Kde4, systemsettings font module provided a way to change the font used by the Desktop elements like the taskbar or the folderview widget. In Plasmashell this option is not implemented (yet?) I whish it will be added ina Desktop-wide manner, or at least a way to customize the fonts used by single desktop elemens. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #5 from Antonio Orefice --- First time i tried was with framework 5.25. It persists with 5.26 qt5 is 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365240] kde.systemtray floods .xsession-errors with messages if Thunderbird is running
https://bugs.kde.org/show_bug.cgi?id=365240 Antonio Orefice changed: What|Removed |Added CC|kokok...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365240] kde.systemtray floods .xsession-errors with messages if Thunderbird is running
https://bugs.kde.org/show_bug.cgi?id=365240 Antonio Orefice changed: What|Removed |Added CC||kokok...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 Antonio Orefice changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #6 from Antonio Orefice --- @David Edmundson : Are you able to reproduce with Nvidia proprietary drivers? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #7 from Antonio Orefice --- New info: with raster backend, apart from having a broken desktop, it seems plasma still allows me to interact with panels, so i interacted with them by using the menu, popup some tooltips, showed the calendar and so on. Well, with export QMLSCENE_DEVICE=softwarecontext i've a ram usage that starts with 228MB and ends to 276MB Using classic opengl, doing the exact same things, it starts at 228MB and reaches 420MB. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #8 from Antonio Orefice --- Since it seems nouveau is not affected, I reported the very same to nvidia https://devtalk.nvidia.com/default/topic/966824/linux/huge-memory-allocation-on-plasmashell-with-proprietary-driver-nouveau-is-fine/post/4981667/?offset=5#4981701 In there, at posted a script using xdotool that did nothing else that showing the plasma configuration window; then the get wallpapers window, close both and reiterate. After 20 minutes of that, my system started swapping badly and plasma was eating almost 6GB of ram. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #11 from Antonio Orefice --- I made a 3 minute run of that xdotool script (open and close wallpaper settings multiple times). Nvidia proprietary driver + QSG_RENDER_LOOP=basic Start: 286MB End: 486MB Nvidia proprietary driver + unset QSG_RENDER_LOOP Start: 281MB End: 533MB Nouveau + unset QSG_RENDER_LOOP Start 289MB End 436MB So, in the end it seems that NVIDIA blob is using more ram, but not that much, and plasma/qt are leaking more memory just because qt uses threads with nvidia proprietary driver, right? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] New: plasmashell keeps eating ram, but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 Bug ID: 368838 Summary: plasmashell keeps eating ram, but never release it. Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kokok...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org On an always on system, my plasmashell memory usage grows and grows. Last time i checked before restarting it, it was eating almost 900MB of ram. Reproducible: Always Steps to Reproduce: 1. measure the memory usage of plasmashell just after startup 2. use it (open apps, display notifications, move widgets, show menu, clock, calendar) 3. leave it as it was in the fresh state (close apps, close notifications restore panel position etc) 3. measure the memory usage again 4. leave it alone for some time (30 minutes?) 5. check the ram usage again Actual Results: The ram usage increased a lot. Expected Results: The ram usage to be almost back to the startup state. I attached pmap,ksysguard and /proc/$(pidof plasmashell)/status before and after usage. Where usage has been: Show the 'kickoff menu' and walk through applications send notifications show notifications show calendar hover the mouse on the taskbar items right click on the desktop to show his configuration window right click on the desktop to show the activities window move a desktop widget resize a desktop widget to the entire screen size click on the panel configuration icon show the available widgets -- Revert all of the changes so that apparently it is a newly started session Before all the described operations, Resident+shared mem was little less than 300MB After, it reached more than 630MB (!) ...and it stays that way (or still grows) till a restart. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram, but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #1 from Antonio Orefice --- Created attachment 101094 --> https://bugs.kde.org/attachment.cgi?id=101094&action=edit Memory informations -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 Antonio Orefice changed: What|Removed |Added Summary|plasmashell keeps eating|plasmashell keeps eating |ram, but never release it. |ram (NVIDIA BLOB), but ||never release it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #2 from Antonio Orefice --- I just played with nuoveau, and found that it consumes so much less memory. With a quick test (show kickoff menu, clock, panel configuration window, moving a plasmoid): nvidia blob reached 400MB nuoveau stayed at about 250MB tried nvidia 367.35 and 370.28 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell keeps eating ram (NVIDIA BLOB), but never release it.
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #3 from Antonio Orefice --- I forgot to add that running a compositor or not running a compositor makes 0 difference -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365240] kde.systemtray floods .xsession-errors with messages if Thunderbird is running
https://bugs.kde.org/show_bug.cgi?id=365240 Antonio Orefice changed: What|Removed |Added CC||kokok...@gmail.com --- Comment #7 from Antonio Orefice --- Same with steam. I manually restart plasmashell in a terminal that way: kquitapp plasmashell ; sleep 1 ; plasmashell &>/dev/null & -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363794] New: Ddolphin ignores Maxsize in breeze index.theme icon file.
https://bugs.kde.org/show_bug.cgi?id=363794 Bug ID: 363794 Summary: Ddolphin ignores Maxsize in breeze index.theme icon file. Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: kokok...@gmail.com Dolphin scales 22x22 sized icon file file to bigger sizes even if bigger sized icon files are specified in the theme file, (ex: breeze) Reproducible: Always Steps to Reproduce: 1. open dolphin and display some icons in the lowest possible size 2. scale them up using the dolphin silder to the max Actual Results: The same 22x22 svg icon size is shown even for the bigger sizes. Expected Results: Dolphin to pick a bigger sized file, as described in the .index theme file. Maybe a video is clearer then my words: dolphin q4 scaling icons, notice that the displayed image changes. This means the picked icon image changes according to the icon size requested, which imho, is the right thing to do: http://wpage.unina.it/aorefice/sharevar … in-qt4.ogv dolphin qt5 scaling icons, notice that it always pick up the same file and scales it: http://wpage.unina.it/aorefice/sharevar … in-qt5.ogv According to https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html --- When type is "Scalable": MinSize:Specifies the minimum size that the icons in this directory can be scaled to. Defaults to the value of Size if not present. MaxSize:Specifies the maximum size that the icons in this directory can be scaled to. Defaults to the value of Size if not present. --- and from breeze index.theme: --- [mimetypes/16] Size=16 Context=MimeTypes Type=Fixed MinSize=16 #22x22 - Fixed size - For small file type icons >!!!ONLY!!!< - DO_NOT_USE_ANYWHERE_ELSE - Monochrome [mimetypes/22] Size=22 Context=MimeTypes Type=Scalable MinSize=22 MaxSize=24 #32x32 - Scalable - For file type icons >!!!ONLY!!!< - Scalable to the following sizes: 64x64 (default), 32x32, 128x128, 256x256 - DO_NOT_USE_ANYWHERE_ELSE - Color [mimetypes/32] Size=32 Context=MimeTypes Type=Scalable MinSize=32 MaxSize=48 #64x64 - Scalable - For file type icons >!!!ONLY!!!< - Scalable to the following sizes: 64x64 (default), 32x32, 128x128, 256x256 - DO_NOT_USE_ANYWHERE_ELSE - Color [mimetypes/64] Size=64 Context=MimeTypes Type=Scalable MinSize=64 MaxSize=256 --- ...but MaxSize=24 is ignored by dolphin qt5, it uses the first Scalable type icons for all of the bigger sizes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363794] Ddolphin ignores Maxsize in breeze index.theme icon file.
https://bugs.kde.org/show_bug.cgi?id=363794 Antonio Orefice changed: What|Removed |Added URL||http://wpage.unina.it/aoref ||ice/sharevari/dolphin/ --- Comment #1 from Antonio Orefice --- Here are some media files that show the issue, and even compare the behaviour of dolphin in qt4 and dolphin qt5 http://wpage.unina.it/aorefice/sharevari/dolphin -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363794] Ddolphin ignores Maxsize in breeze index.theme icon file.
https://bugs.kde.org/show_bug.cgi?id=363794 --- Comment #2 from Antonio Orefice --- I'm using the qt5ct plugin; somehow it works good in a full kde desktop; can't say why. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359987] New: Cannot place widgets "near" a vertical panel
https://bugs.kde.org/show_bug.cgi?id=359987 Bug ID: 359987 Summary: Cannot place widgets "near" a vertical panel Product: plasmashell Version: 5.5.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: kokok...@gmail.com i've two screens, the right one has an orizontal panel; while the left one has a vertical panel. It seems that the left vertical panel is surrounded by a margin that makes impossivle to place widgets near the panel. The "bug" is that that margin is too wide; more precisely it is wide exactly as the panel; this means that the bigger the panel; the bigger will be the margin. See screenshot attached for details; you can see i'm trying to move the folderview widgets but plasmashell highlights what will be the folderview position at the end of the drag operation; and clearly it wants to place it very far from the vertical panel. Reproducible: Always Steps to Reproduce: 1.have a multihead configuration with two screens and an entire desktop spawned on horizontal. 2. make the right screen the primary one 3. place panels on the screen as seen in the attached screenshot. 4. try to place a widget near the rightmost, vertical, panel Actual Results: see that there is a huge margin around the rightmost, vertical panel. Notice also that if you enlarge the vertical panel, the margin will be even bigger. Expected Results: The margins have to be smaller, and should not be big as the panel width. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359987] Cannot place widgets "near" a vertical panel
https://bugs.kde.org/show_bug.cgi?id=359987 --- Comment #1 from Antonio Orefice --- Created attachment 97637 --> https://bugs.kde.org/attachment.cgi?id=97637&action=edit screenshot showing me trying to put a widget near the panel -- You are receiving this mail because: You are watching all bug changes.
