[kwin] [Bug 475103] Terms "Horizontal" and "vertical" are confusing in this context
https://bugs.kde.org/show_bug.cgi?id=475103 Karl Ove Hufthammer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||k...@huftis.org --- Comment #4 from Karl Ove Hufthammer --- I too find this very confusing. I would expect ‘Split Vertically’ to actually split the view vertically (into a left and a right part), just like the same option does in Kate, not horizontally (into a top and a bottom part), as in the current behaviour in the tiling manager. And ‘Split Horizontally’ to split to view horizontally, not vertically. And it looks like I’m not the only one confused by the wording: https://www.reddit.com/r/kde/comments/112gube/wow_how_did_they_miss_this_one_horizontal_runs/ I’m translating KDE, and this actually caused me to use the wrong translation. I translated ‘Split Vertically’ into something like ‘Split left/right’, as I thought this would be easier to understand, and since it was the the *correct* translation for the similarly named feature in Kate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482669] Taskbar icons are moving to the left on hover with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=482669 --- Comment #5 from Karl Ove Hufthammer --- And here’s some more system information: Operating System: openSUSE Tumbleweed 20240514 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482669] Taskbar icons are moving to the left on hover with QT_QUICK_BACKEND=software
https://bugs.kde.org/show_bug.cgi?id=482669 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #4 from Karl Ove Hufthammer --- I’m experiencing the exact same problem, and I am *not* using QT_QUICK_BACKEND=software (as far as I’m aware). Whenever I hover over a button on the panel (either a taskbar icon or a different icon), it moves to the left, overlapping the application launcher. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 480287] Browser login for openconnect has fixed size
https://bugs.kde.org/show_bug.cgi?id=480287 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 486397] New: plasmoidviewer crashes (core dump) for widgets that use QtWebEngine
https://bugs.kde.org/show_bug.cgi?id=486397 Bug ID: 486397 Summary: plasmoidviewer crashes (core dump) for widgets that use QtWebEngine Classification: Plasma Product: Plasma SDK Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: plasmoidviewer Assignee: plasma-b...@kde.org Reporter: k...@huftis.org CC: giorgos.tsiapalio...@kde.org, m...@ratijas.tk Target Milestone: --- SUMMARY When using plasmoidviewer to open a Plasma widget which uses QtWebEngine, the application immediately crashes. STEPS TO REPRODUCE 1. From the command-line, run either plasmoidviewer --applet org.kde.plasma_applet_dict or plasmoidviewer --applet org.kde.plasma.webbrowser‘ OBSERVED RESULT A window is briefly shown, but then plasmoidviewer crashes with an error message ending with: QtWebEngineQuick::initialize() must be called from the Qt gui thread. Aborted (core dumped) EXPECTED RESULT No crash and a working standalone Plasma widget shown. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240425 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION The crash also happens when using plasmawindowed: plasmawindowed org.kde.plasma_applet_dict However, it does not happen when adding the widgets to the desktop, and it does not seem to happen for widgets that don’t use QtWebEngine. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 485856] New: Duplicate dataset names in Frieze activity
https://bugs.kde.org/show_bug.cgi?id=485856 Bug ID: 485856 Summary: Duplicate dataset names in Frieze activity Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- In the Frieze activity, there are two datasets/difficulties with the exact same name: Copy and complete this frieze: any combination of shapes, colors/signs and sizes. The only thing that differs, are the icons, so I guess there must some difference in difficulty, but the names don’t give any information on this. Very confusing. STEPS TO REPRODUCE 1. Open the Frieze activity 2. Click on the purple dataset button -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 483814] New: Accent colour dropdown too narrow (doesn’t show any text)
https://bugs.kde.org/show_bug.cgi?id=483814 Bug ID: 483814 Summary: Accent colour dropdown too narrow (doesn’t show any text) Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: k...@huftis.org CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 167361 --> https://bugs.kde.org/attachment.cgi?id=167361=edit Video showing the bug SUMMARY When choosing a custom accent colour, one of the dropdown boxes is too narrow, so it can’t show any text. Only ... is displayed. See the attached video. STEPS TO REPRODUCE 1. Choose to use a custom accent colour. 2. Click the custom accent colour button OBSERVED RESULT Dropdown box only shows that first letter of the text (H on my system). When clicking on it, only ... options are shown. See the attached video. EXPECTED RESULT The text should be visible. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240314 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.9-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 483088] New: Cages in Calcudoku are difficult to notice
https://bugs.kde.org/show_bug.cgi?id=483088 Bug ID: 483088 Summary: Cages in Calcudoku are difficult to notice Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY This is based on my experience trying Calcudoku. At first, I didn’t understand the game. Only after several attempts, I finally noticed the cages. The problem is that the line width and colour is almost the same for the two types of lines. STEPS TO REPRODUCE 1. Play Calcudoku. OBSERVED RESULT Difficult to see the cages as the colours for the two types lines are very similar (dark grey vs. black) and the line widths are almost identical. EXPECTED RESULT The the black lines should be much thicker than they grey lines. And preferably, the grey lines should be somewhat lighter in colour (but still providing contrast against the background). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481940] krunner not launching due to org.kde.krunner.service file not installed.
https://bugs.kde.org/show_bug.cgi?id=481940 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473043] Embedded Konsole crash on command execution
https://bugs.kde.org/show_bug.cgi?id=473043 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 406474] Genre view grid lacks that Je-ne-sais-quoi
https://bugs.kde.org/show_bug.cgi?id=406474 --- Comment #6 from Karl Ove Hufthammer --- Here’s an example of how one can use icons to representing different musical genres: https://www.dreamstime.com/stock-illustration-musical-genre-web-icons-user-interface-design-image88220057 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 473792] New: Unnecessary warning about lack of high-accuracy timing (for alarm times far into the future)
https://bugs.kde.org/show_bug.cgi?id=473792 Bug ID: 473792 Summary: Unnecessary warning about lack of high-accuracy timing (for alarm times far into the future) Classification: Applications Product: kalarm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: k...@huftis.org Target Milestone: --- SUMMARY When adding an alarm, KAlarm shows the following warning: KAlarm does not provide high accuracy alarms. The alarm will trigger at the minute boundary before the specified time from now. According to the changelog https://github.com/KDE/kalarm/blob/master/Changelog, the intention is to only show this warning if the alarm time would be triggered very soon (in the next few minutes?). But it‘s actually shown for alarms which only would be triggered far into the future, e.g., in a year’s time, where you don’t need high-accuracy timing. STEPS TO REPRODUCE 1. Add a new alarm. 2. Set alarm time to a year into the future. 3. Click ‘OK’. OBSERVED RESULT Warning about lack of high-accuracy timing is shown. EXPECTED RESULT No warning should be shown. (It should be shown only for alarms set to be triggered in the x minutes, perhaps with x = 10.) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230822 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 473652] New: Wishlist: Different icons for different musical genres
https://bugs.kde.org/show_bug.cgi?id=473652 Bug ID: 473652 Summary: Wishlist: Different icons for different musical genres Classification: Applications Product: Elisa Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: k...@huftis.org Target Milestone: --- SUMMARY The ‘Genres’ view look very samey, with all genres having the same icon. It would be nice if different genres had different icons. It’s probably difficult to draw different and recognisable icons for *all* genres, but at least the major genres could have different icons. Here’s an example of icons representing different musical genres: https://www.dreamstime.com/stock-illustration-musical-genre-web-icons-user-interface-design-image88220057 STEPS TO REPRODUCE 1. Click the ‘Genres’ icon. OBSERVED RESULT A grid of identical icons. EXPECTED RESULT A grid of different-looking icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473035] Widget explorer categories don’t work (are almost empty) for non-English locales
https://bugs.kde.org/show_bug.cgi?id=473035 --- Comment #2 from Karl Ove Hufthammer --- (In reply to Nate Graham from comment #1) > And these strings are fully translated into Norwegian? Yes, they are: https://websvn.kde.org/branches/stable/l10n-kf5/nn/messages/plasma-workspace/plasmashellprivateplugin.po?view=markup -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472385] [Feature Request] (Widget Explorer): Better sorting and categories for widget explorer
https://bugs.kde.org/show_bug.cgi?id=472385 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #3 from Karl Ove Hufthammer --- Note that it *is* currently possible to *filter* by category (clicking ‘Alle Miniprogramme’ should show a list of a categories, though some may be missing with non-English language settings – see bug #473035). However, I agree that grouping and sorting the widgets by category, like in your macOS screenshot, would be nice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473035] Widget explorer categories don’t work (are almost empty) for non-English locales
https://bugs.kde.org/show_bug.cgi?id=473035 Karl Ove Hufthammer changed: What|Removed |Added Summary|Widgets explorer categories |Widget explorer categories |don’t work (are almost |don’t work (are almost |empty) for non-English |empty) for non-English |locales |locales -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473035] New: Widgets explorer categories don’t work (are almost empty) for non-English locales
https://bugs.kde.org/show_bug.cgi?id=473035 Bug ID: 473035 Summary: Widgets explorer categories don’t work (are almost empty) for non-English locales Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: k...@huftis.org Target Milestone: 1.0 SUMMARY The list of categories in the widget explorer is (almost) empty if the language settings are set to something different than English. For example, if you set the language to Norwegian Nynorsk, the only category visible is ‘Multimedia’ (probably because the name is the same in Norwegian and English). STEPS TO REPRODUCE 1. Go the system settings, regional settings and change the language to Norwegian Nynorsk (= norsk nynorsk). 2. Log out and in again (for the language change to fully take effect). 3. Right-click on the desktop and choose ‘Legg til element …’ (= ‘Add Widget…’). 4. In the ‘Add Widget’ thing which appear, click ‘Alle element’. OBSERVED RESULT The list of categories only include ‘Multimedia’. EXPECTED RESULT The list of categories should contain many categories, just like it does if you run Plasma with English as the language. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230804 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401342] Long plasmoid names and/or descriptions are truncated
https://bugs.kde.org/show_bug.cgi?id=401342 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #6 from Karl Ove Hufthammer --- Created attachment 160755 --> https://bugs.kde.org/attachment.cgi?id=160755=edit Screenshot showing widget explorer in Norwegian Nynorsk One *partial* solution is for the translators of the widget names/descriptions to add soft hyphen to long words. Soft hyphens are normally invisible, but if a word can’t fit on a line, it will be automatically broken at the soft hyphen(s) (which then becomes visible). We do this for the Norwegian Nynorsk translation. I’ll attach a screenshot. In it, you can see that the widget name ‘Aktivitetsbytar’ and the word ‘aktivitetshandsamaren’ in a widget description are broken over two lines. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387157] Sorting the filters of the Widgets Explorer in alphabetical order should ignore accent if Plasma language is pt-br
https://bugs.kde.org/show_bug.cgi?id=387157 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 472691] Raised buttons don't look or feel buttonlike enough
https://bugs.kde.org/show_bug.cgi?id=472691 --- Comment #9 from Karl Ove Hufthammer --- Created attachment 160713 --> https://bugs.kde.org/attachment.cgi?id=160713=edit Video showing button selection using the keyboard This bug was originally only about the very big rectangle card buttons in the welcome center not looking clickable enough, partly due to a too subtle hover effect. But I now think this applies to ordinary (small) buttons too. The effect when hovering a button or selecting it with the keyboard is just too subtle. As evidence, I’ve attached a new video. I’m using the default Breeze style, with Breeze Light as the colour palette, and one of the default 10 highlight colours (purple). So nothing very special there. In the video, you’ll see me 1) navigating through four buttons using the keyboard, 2) navigating through some checkboxes, 3) navigating back through the buttons and finally 4) navigating through some toolbar buttons. For the checkboxes and toolbar buttons, it’s very easy to see which element is currently selected. But for the four buttons, there’s only a very subtle change, namely the colour of the thin outline. I think I have pretty good eyesight, but the effect is too subtle for me. It will be much worse for people with poor eyesight, so I think this is a accessibility issue. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 472691] Welcome center buttons don’t look and feel like buttons
https://bugs.kde.org/show_bug.cgi?id=472691 --- Comment #7 from Karl Ove Hufthammer --- (In reply to Nate Graham from comment #6) > The buttons in Discover and the buttons in Welcome Center are using the same > QQC2.Button primitive with the same styling. I think you see the shadow in > Discover more easily because the button is on a white background, so the > gray shadow has better contrast there. They also have the same edge > highlight on hover. Just for the record, I was talking about the buttons on the *main* and *category* pages in Discover, the ones showing the icon, name and description of an application. They have a shadow and a nice hover effect (coloured background based on the current highlight colour). At least for me, it makes them look and feel clickable. I think you’re talking about the other, similarly shaped, buttons on the *application details* page in Discover. Yes, they look like the ones in the welcome center. And to me, they don’t look or feely especially clickable. (The button text is the only thing that really indicates they’re meant to be clicked.) Other KDE examples of ‘buttons’ with hover effect to indicate clickability: application buttons on the task bar (the background colour is changed to the highlight colour and the icons are made slightly brighter), other buttons on the task bar (the icons are made slightly brighter), and the application buttons on https://apps.kde.org/ (they rise from the page when you hover, and they also have a shadow effect to lift them from the page). -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 472691] Welcome center buttons don’t look and feel like buttons
https://bugs.kde.org/show_bug.cgi?id=472691 --- Comment #5 from Karl Ove Hufthammer --- Just noticed that the similar buttons in Discover have: – A subtle shadow effect – A ‘coloured background’ effect on hover This makes them feel much more like buttons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467325] bad french date format in tooltip.
https://bugs.kde.org/show_bug.cgi?id=467325 --- Comment #7 from Karl Ove Hufthammer --- Some additional information: If I click on the clock to open the calendar, and then click on a date, the date is displayed correctly (in the top-left corner), in long form: laurdag 29. juli 2023 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467325] bad french date format in tooltip.
https://bugs.kde.org/show_bug.cgi?id=467325 --- Comment #6 from Karl Ove Hufthammer --- Created attachment 160603 --> https://bugs.kde.org/attachment.cgi?id=160603=edit Wrong date in tooltip for Norwegian Nynorsk The red arrows shows the wrong date format. The two green arrows shows the expected date format (but the weekday need not be abbreviated). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467325] bad french date format in tooltip.
https://bugs.kde.org/show_bug.cgi?id=467325 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #5 from Karl Ove Hufthammer --- I have the same problem, but for Norwegian Nynorsk. The weekday and month names are properly localized, but the order and punctuation is wrong (it looks like it uses the US order). Also, note this happens *only* when there’s more than one timezone configured. I’ll attach a screenshot. STEPS TO REPRODUCE 1. Configure the digital clock to have at least two time zones. In my example (screenshot) I have Oslo and Aden, and I have my regional settings set to Norwegian Nynorsk. 2. Hover over the clock. OBSERVED RESULT A tooltip is shown, and the heading contains a (medium-sized) date, but the date parts are in the wrong order and have the wrong punctuation: la. juli 29 2023 «la.» is the Norwegian Nynorsk abbreviation for «laurdag» (Saturday), and «juli» is the Norwegian Nynorsk month name for July. EXPECTED RESULT For Norwegian Nynorsk, I would expect: la. 29. juli 2023 or (preferably) laurdag 29. juli 2023 (note the . after the day.) ADDITIONAL INFORMATION If I only have *one* time zone, the date is displayed correctly (but on two lines), in long form: laurdag 29. juli 2023 -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 472691] Welcome center buttons don’t look and feel like buttons
https://bugs.kde.org/show_bug.cgi?id=472691 Karl Ove Hufthammer changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #4 from Karl Ove Hufthammer --- (In reply to Nate Graham from comment #3) > If Welcome Center had looked for you like how it does in the screenshot I > attached, do you think you would have still felt like there was a problem > and submitted this bug report? > > If not, then maybe the problem is with your color scheme. Is it Breeze > Classic with a pink accent color? Yes, I use Breeze Classic. I thought that was the default theme … :/ I use a purple highlight colour (one of the default colours). So I don‘t think I use a very unusual theme / colour scheme. The ‘buttons’ do look better with the other Breeze themes. They still don’t look *very* clickable to me, though. I think the problem is that with the new, flat look of buttons, it’s mostly their size and placement that makes them look and feel like buttons. And that’s OK. But these areas have a completely different size and placement, so they don’t (to me) feel like clickable buttons. IMO, they need something more to feel clickable, at least when hovering, e.g., a subtle highlight, a shadow, expansion, a tooltip. BTW, I just *now* noticed that the small icons on the following page (Krita, Blender, VLC ) are clickable! They look even less like buttons … But they (and the big Discover icon) at least change the mouse pointer to a hand icon when hovering, and they have tooltips, so that helps. They feel very clickable once you actually hover the pointer over them. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472757] New: Tablet info text is cut off
https://bugs.kde.org/show_bug.cgi?id=472757 Bug ID: 472757 Summary: Tablet info text is cut off Classification: Applications Product: systemsettings Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: k...@huftis.org CC: aleix...@kde.org Target Milestone: --- Created attachment 160594 --> https://bugs.kde.org/attachment.cgi?id=160594=edit Screenshot showing text cut off SUMMARY When no tablet is recognized, the text on the button for manually configuring a tablet is vertically cut off. STEPS TO REPRODUCE 1. Disconnect any tablets. 2. Open system settings. 3. Go to tablet page OBSERVED RESULT The text on the second line of the button for manually configuring a tablet is cut off, i.e., both the top and the bottom of the letters are invisible. Also, the > character to the left of the button is not properly vertically aligned with the first line of text. EXPECTED RESULT The text should not be cut off. The > character should be aligned with the first line of text. And preferably, the button shouldn’t be so wide, but instead have the text wrapped over several lines, so that the window can be made smaller. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230724 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION See attached screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 472691] Welcome center buttons don’t look and feel like buttons
https://bugs.kde.org/show_bug.cgi?id=472691 --- Comment #1 from Karl Ove Hufthammer --- Created attachment 160559 --> https://bugs.kde.org/attachment.cgi?id=160559=edit Video showing how the buttons look when you hover over them -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 472691] New: Welcome center buttons don’t look and feel like buttons
https://bugs.kde.org/show_bug.cgi?id=472691 Bug ID: 472691 Summary: Welcome center buttons don’t look and feel like buttons Classification: Applications Product: Welcome Center Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@huftis.org CC: n...@kde.org Target Milestone: --- SUMMARY On page 3 (‘Powerful when needed’) of the welcome center, there are six clickable ‘buttons’. However, there’s almost no indication that they’re actually clickable. They don’t really look like buttons, and when you hover the cursor over them, there’s only a faint change in outline colour. See the attached video. STEPS TO REPRODUCE 1. Open welcome center. 2. Go to page three. 3. However over the six rectangles. OBSERVED RESULT Only the outline slightly changes colour. EXPECTED RESULT There are several ways to indicate that they‘re clickable: – They could have a different background colour (ligher or darker) – The background colour can change when you hover over them – They could have a more 3D look – They could pop up slightly when you hover them – The mouse cursor could change to a ‘hand’ cursor when you hover them (this happens when I hover a button in my browser, but not when I hover a button in the Plasma UI) – The text above the buttons can say they’re clickable (‘Click on an example below to learn more […]’) – There could be a tooltip when you hover the buttons SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230724 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.4-1-default (64-bit) Graphics Platform: offscreen ADDITIONAL INFORMATION I’m using Breeze with the default colour scheme. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 125474] MAINTENANCE : possibility to merge digiKam databases
https://bugs.kde.org/show_bug.cgi?id=125474 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 472232] Author list commit numbers are wrong (sometimes even zero)
https://bugs.kde.org/show_bug.cgi?id=472232 --- Comment #4 from Karl Ove Hufthammer --- I found one more problem with the author statistics. For the Kommit repo itself, one person is listed with no name or email address, but 1 in the Autheds column. If I compare the statistics with git log/shortlog, the person is Xin Liu . Both the name and the email address looks normal, so it’s a bit strange that they’re shown as empty strings. -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 472232] Author list commit numbers are wrong (sometimes even zero)
https://bugs.kde.org/show_bug.cgi?id=472232 --- Comment #3 from Karl Ove Hufthammer --- BTW, the tag information isn’t really reliable. It’s shown even for lightweight tags, i.e., tags that don’t have any author information stored. I guess the name is taken from the committer or author (which is typically *not* the person creating the tag)? -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 472232] Author list commit numbers are wrong (sometimes even zero)
https://bugs.kde.org/show_bug.cgi?id=472232 Karl Ove Hufthammer changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Karl Ove Hufthammer --- Thanks. I have tested the updated Git version, and there seems to be some deduplication issues. There’s an extra row for people who have added tags (i.e., their names are shown twice). The only difference is that their email addresses for the Tags row are shown with angle brackets. One example from the repository I mentioned is Nicolas Fella. He has one row (nicolas.fe...@gmx.de) with 20 commits, 22 autheds and 0 tags. And one row (, note the angle brackets) with 0 commits, 0 autheds and 1 tag. -- You are receiving this mail because: You are watching all bug changes.
[kommit] [Bug 472232] New: Author list commit numbers are wrong (sometimes even zero)
https://bugs.kde.org/show_bug.cgi?id=472232 Bug ID: 472232 Summary: Author list commit numbers are wrong (sometimes even zero) Classification: Applications Product: kommit Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: hamed.mas...@gmail.com Reporter: k...@huftis.org CC: mon...@kde.org Target Milestone: --- SUMMARY The number of of commits in the Authors panel are wrong. Some authors are even listed with zero commits, which shouldn’t be possible. STEPS TO REPRODUCE 1. Check out https://invent.kde.org/libraries/kirigami-addons.git 2. Go to the Authors panel 3. Click the Commits header 4. Scroll up/down so you see the authors with fewest commits OBSERVED RESULT Some authors are listed with 0 commits. And the number of commits in general don’t always match the output of ‘git shortlog -sne’ (even for authors with unique email addresses). Some numbers match, but some numbers are lower (e.g., 0) or higher (even if we include ‘--all’ to the git shortlog command). EXPECTED RESULT The numbers should match the git shortlog numbers. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 471868] New: NeoChat crashes when creating a new room
https://bugs.kde.org/show_bug.cgi?id=471868
Bug ID: 471868
Summary: NeoChat crashes when creating a new room
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: k...@huftis.org
CC: c...@carlschwan.eu
Target Milestone: ---
Application: neochat (23.04.3)
Qt Version: 5.15.10
Frameworks Version: 5.107.0
Operating System: Linux 6.3.9-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.27.6 [KCrashBackend]
-- Information about the crash:
NeoChat crashes when I try to create a new room.
To reproduce:
1. Click the + button.
2. Click ‘Create a Room’.
3. Choose a room name (optionally a room subject).
4. NeoChat crashes.
The crash can be reproduced every time.
-- Backtrace:
Application: NeoChat (neochat), signal: Aborted
[KCrash Handler]
#4 0x7fba43492a7c in __pthread_kill_implementation () at /lib64/libc.so.6
#5 0x7fba43441226 in raise () at /lib64/libc.so.6
#6 0x7fba43429897 in abort () at /lib64/libc.so.6
#7 0x7fba43abb4f9 in () at /lib64/libQt5Core.so.5
#8 0x7fba43aba730 in qt_assert_x(char const*, char const*, char const*,
int) () at /lib64/libQt5Core.so.5
#9 0x0045bb3b in Quotient::_impl::connectDecorated(Controller*, void
(Controller::*)(NeoChatRoom*), Controller*, std::function,
Qt::ConnectionType)::{lambda(NeoChatRoom* const&)#1}::operator()(NeoChatRoom*
const&) const (__closure=0x3f6db80, args#0=@0x3f7fce0: 0x6739820) at
/usr/include/Quotient/qt_connection_util.h:53
#10 0x0045ef93 in QtPrivate::FunctorCall,
QtPrivate::List, void,
Quotient::_impl::connectDecorated(Controller*, void
(Controller::*)(NeoChatRoom*), Controller*, std::function,
Qt::ConnectionType)::{lambda(NeoChatRoom*
const&)#1}>::call(Quotient::_impl::connectDecorated(Controller*, void
(Controller::*)(NeoChatRoom*), Controller*, std::function,
Qt::ConnectionType)::{lambda(NeoChatRoom* const&)#1}&, void**) (f=...,
arg=0x6734b68) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#11 0x0045ece8 in
QtPrivate::Functor(Controller*, void
(Controller::*)(NeoChatRoom*), Controller*, std::function,
Qt::ConnectionType)::{lambda(NeoChatRoom* const&)#1},
1>::call,
void>(Quotient::_impl::connectDecorated(Controller*, void
(Controller::*)(NeoChatRoom*), Controller*, std::function,
Qt::ConnectionType)::{lambda(NeoChatRoom* const&)#1}&, void*, void**) (f=...,
arg=0x6734b68) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#12 0x0045e90e in
QtPrivate::QFunctorSlotObject(Controller*, void
(Controller::*)(NeoChatRoom*), Controller*, std::function,
Qt::ConnectionType)::{lambda(NeoChatRoom* const&)#1}, 1,
QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase*,
QObject*, void**, bool*) (which=1, this_=0x3f6db70, r=0x6892a0
, a=0x6734b68, ret=0x0) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#13 0x7fba43d192b0 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#14 0x7fba449a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#15 0x7fba43ced4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7fba43cf0af1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#17 0x7fba43d46c83 in () at /lib64/libQt5Core.so.5
#18 0x7fba4316f8d8 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#19 0x7fba4316fce8 in () at /lib64/libglib-2.0.so.0
#20 0x7fba4316fd7c in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#21 0x7fba43d46496 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#22 0x7fba45d356c5 in
Quotient::Connection::Private::consumeRoomData(std::vector >&&, bool) () at
/lib64/libQuotient.so.0.6
#23 0x7fba45d35991 in
Quotient::Connection::onSyncSuccess(Quotient::SyncData&&, bool) () at
/lib64/libQuotient.so.0.6
#24 0x7fba45d39183 in () at /lib64/libQuotient.so.0.6
#25 0x7fba43d257a2 in () at /lib64/libQt5Core.so.5
#26 0x7fba45d176e2 in Quotient::BaseJob::success(Quotient::BaseJob*) () at
/lib64/libQuotient.so.0.6
#27 0x7fba45d803e5 in Quotient::BaseJob::finishJob() () at
/lib64/libQuotient.so.0.6
#28 0x7fba43d257a2 in () at /lib64/libQt5Core.so.5
#29 0x7fba45518958 in () at /lib64/libQt5Network.so.5
#30 0x7fba43d192b0 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#31 0x7fba449a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#32 0x7fba43ced4f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#33 0x7fba43cf0af1 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*)
[NeoChat] [Bug 462270] Neochat forgets connected accounts, starts with infinite loading screen and crashes when trying to log into an account
https://bugs.kde.org/show_bug.cgi?id=462270 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 253012] option to show translation context between original and translation edit widgets
https://bugs.kde.org/show_bug.cgi?id=253012 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423945] wish: pre-buffering of images to enable faster/smoother switching
https://bugs.kde.org/show_bug.cgi?id=423945 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 443010] Consider always using Qt::SmoothTransformation, or allow configuring it in settings
https://bugs.kde.org/show_bug.cgi?id=443010 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #11 from Karl Ove Hufthammer --- (In reply to Jens Ramke from comment #9) > (In reply to Nate Graham from comment #8) > > Are folks saying they have > > use cases where it would be useful to see the raw pixels at 101-399% zoom as > > well? > > Yes, I do use 200% zoom quite a bit and I need to see an unfiltered image. Me too. An unfiltered/non-smoothed view is very important when viewing pixel art. (It would also be nice with a shortcut to quickly switch between a smoothed and non-smoothed view.) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471194] Some images are rendered incorrectly, show weird pink doted lines
https://bugs.kde.org/show_bug.cgi?id=471194 Karl Ove Hufthammer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||k...@huftis.org --- Comment #2 from Karl Ove Hufthammer --- I have tested the example image and can confirm that this is the same problem as in bug #459627. (Resaving the image as a full-colour PNG instead of a PNG with an indexed palette is a workaround, but this might increase the file size.) *** This bug has been marked as a duplicate of bug 459627 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459627] Strange artifacting / dithering on zoom with some pngs
https://bugs.kde.org/show_bug.cgi?id=459627 Karl Ove Hufthammer changed: What|Removed |Added CC||1niko...@hotmail.gr --- Comment #14 from Karl Ove Hufthammer --- *** Bug 471194 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459627] Strange artifacting / dithering on zoom with some pngs
https://bugs.kde.org/show_bug.cgi?id=459627 --- Comment #13 from Karl Ove Hufthammer --- I did a quick Git bisect. The bug was introduced in this commit: commit 33d6203c7b4de83a8a1ea92dfc7036af87eb43f2 Author: Daniel Novomesky Date: Mon Sep 6 19:56:30 2021 +0200 Convert image to original format to enable correct color correction QImage::scaled() may unexpectedly change image’s format to Premultiplied, we need to ensure that image remains in original format supported by color correction engine. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459627] Strange artifacting / dithering on zoom with some pngs
https://bugs.kde.org/show_bug.cgi?id=459627 --- Comment #12 from Karl Ove Hufthammer --- Created attachment 159946 --> https://bugs.kde.org/attachment.cgi?id=159946=edit Indexed image (noise pattern when zooming) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459627] Strange artifacting / dithering on zoom with some pngs
https://bugs.kde.org/show_bug.cgi?id=459627 --- Comment #11 from Karl Ove Hufthammer --- Created attachment 159945 --> https://bugs.kde.org/attachment.cgi?id=159945=edit Full colour image (no problems when zooming) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459627] Strange artifacting / dithering on zoom with some pngs
https://bugs.kde.org/show_bug.cgi?id=459627 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #10 from Karl Ove Hufthammer --- It also happens with indexed PNG images *not* processed by pngquant. I’ll attach two images. The first is a full-colour PNG image (23,808 colours) image. The second is the same image, but as an indexed PNG image where the number of colours have been reduced to 120 using Gimp, but *without* any dithering applied (so it’s not a dithering problem). The first image look fine when zoomed, but the other has this strange noisy pattern on most zoom levels (not at *exactly* 100% or levels above 400%, but at all other zoom levels, AFAICS). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 469285] Can’t navigate back to filename field in open/save dialog using keyboard (Tab key)
https://bugs.kde.org/show_bug.cgi?id=469285 Karl Ove Hufthammer changed: What|Removed |Added Keywords||accessibility -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 469285] New: Can’t navigate back to filename field in open/save dialog using keyboard (Tab key)
https://bugs.kde.org/show_bug.cgi?id=469285 Bug ID: 469285 Summary: Can’t navigate back to filename field in open/save dialog using keyboard (Tab key) Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.105.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: k...@huftis.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY In an open/save dialog, when you navigate away from the filename field using the Tab key, it’s no longer possible to navigate back to it using the Tab key. You‘re stuck in a ‘Folder → File listing → Edit path button’ cycle. STEPS TO REPRODUCE 1. Start (e.g.) Kate. 2. Click the Open icon. 3. (You’re now in the Filename field.) Press the ‘Tab’ key to switch to the Filter field, then ‘Tab’ to switch to the zoom slider field, then ‘Tab’ to switch to the Places panel (it’s not possible visually to see that you’re there, but you are), and then ‘Tab’ to switch to the Folder/path field. 4. Repeatedly press the ‘Tab’ key. OBSERVED RESULT You‘re stuck in a loop, switch between ‘Folder → File listing → Edit path button → Folder → …’. You can’t navigate back to the filename field or any of the field listed in step 3 (without using the mouse pointer). EXPECTED RESULT After pressing ‘Tab’ when you’re at the ‘Edit path button’ (a checkmark), you should return to the ‘Filename’ field, so that you can cycle through *all* elements. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230428 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469110] dophin crashed during file move
https://bugs.kde.org/show_bug.cgi?id=469110 --- Comment #1 from Karl Ove Hufthammer --- Created attachment 158537 --> https://bugs.kde.org/attachment.cgi?id=158537=edit New crash information added by DrKonqi dolphin (23.04.0) using Qt 5.15.9 Dolphin crashed while moving files to an MTP / Android device. -- Backtrace (Reduced): #4 std::__atomic_base::operator-- (this=0x20) at /usr/include/c++/13/bits/atomic_base.h:410 #5 QAtomicOps::deref (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:289 [...] #7 QSharedDataPointer::~QSharedDataPointer (this=, this=) at /usr/include/qt5/QtCore/qshareddata.h:93 #8 KFileItem::~KFileItem (this=, this=) at /usr/src/debug/kio-5.105.0/src/core/kfileitem.cpp:605 #9 0x7f2925cb244d in QList::node_destruct (n=0x558c5ae89c70, this=0x558c5a951d00) at /usr/include/qt5/QtCore/qlist.h:479 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469110] dophin crashed during file move
https://bugs.kde.org/show_bug.cgi?id=469110 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 356914] Add an option to don't start playing media when call ends
https://bugs.kde.org/show_bug.cgi?id=356914 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466881] Bug reporting feature selects wrong version (leading to bug reports being automatically closed)
https://bugs.kde.org/show_bug.cgi?id=466881 --- Comment #3 from Karl Ove Hufthammer --- I had a different default version in different browsers, so I did some more digging. The default version is actually stored in a *cookie*. For example, for systemsettings bugs, it’s stored in a cookie named ‘VERSION-systemsettings’ (for me set to ‘5.27.2’). Anyway, adding the version number to the URL should override any cookie values. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466881] Bug reporting feature selects wrong version (leading to bug reports being automatically closed)
https://bugs.kde.org/show_bug.cgi?id=466881 Karl Ove Hufthammer changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Karl Ove Hufthammer --- It happens with all the pages I have tested. An example is the Bluetooth page. Reporting a bug opens a URL without any version info: https://bugs.kde.org/enter_bug.cgi?product=systemsettings=kcm_bluetooth For comparison, if I report a bug for a standalone application, e.g., Dolphin, a URL with version info is opened: https://bugs.kde.org/enter_bug.cgi?format=guided=dolphin=22.12.3 (The URL without any version info now actually defaulted to to 5.27.2 for me, so perhaps it defaults to the value used in the user’s previous/latest bug report for the given product?) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466127] Tiling configuration works erratically on cloned screens
https://bugs.kde.org/show_bug.cgi?id=466127 --- Comment #2 from Karl Ove Hufthammer --- BTW, I’m seeing this bug on Plasma 5.27.2: Operating System: openSUSE Tumbleweed 20230303 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466127] Tiling configuration works erratically on cloned screens
https://bugs.kde.org/show_bug.cgi?id=466127 Karl Ove Hufthammer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Karl Ove Hufthammer --- I think I’m having the same problem. Whenever I try to make any changes in the tiling layout editor, e.g., by dragging a split or clicking on any of the padding buttons, *nothing* seems to happen. The config dialog doesn’t update. I too have two screens, a monitor (almost always powered off) and a TV. I don’t have the screens configured as clones, but they instead positioned so that they perfectly overlap, which has the same effect. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466881] New: Bug reporting feature selects wrong version (leading to bug reports being automatically closed)
https://bugs.kde.org/show_bug.cgi?id=466881 Bug ID: 466881 Summary: Bug reporting feature selects wrong version (leading to bug reports being automatically closed) Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@huftis.org Target Milestone: --- SUMMARY If you use the bug reporting feature in systemsettings, the version field is set to an old Plasma version, and after submitting the bug report, it is automatically closed, as the version is too old. Not very user-friendly! STEPS TO REPRODUCE 1. Go to any systemsettings page. 2. Click the hamburger menu and then ‘Report a Bug in the Current Page…’ OBSERVED RESULT A bug reporting page with the ‘Version’ field set to 5.20.2 is opened. If you actually file the bug, it is automatically closed by the Bug Janitor Service, as the Plasma version is too old (‘no longer eligible for support or maintenance from KDE’). EXPECTED RESULT The bug reporting page should be opened with the ‘Version’ field set to the *correct* version. (It would also be nice if the ‘SOFTWARE/OS VERSIONS’ text in the comment box would be automatically set to the correct values.) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230303 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466877] Adding filesystem path access messes up the following checkboxes
https://bugs.kde.org/show_bug.cgi?id=466877 Karl Ove Hufthammer changed: What|Removed |Added Version|5.20.2 |5.27.2 Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|DOWNSTREAM |--- --- Comment #2 from Karl Ove Hufthammer --- Reopening. I’m actually on Plasma 5.27.2, and the bug is present in Plasma 5.27.2. (It was the automatic bug reporting feature that automatically selected the incorrect, older Plasma version.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466877] New: Adding filesystem path access messes up the following checkboxes
https://bugs.kde.org/show_bug.cgi?id=466877 Bug ID: 466877 Summary: Adding filesystem path access messes up the following checkboxes Classification: Applications Product: systemsettings Version: 5.20.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_flatpak Assignee: plasma-b...@kde.org Reporter: k...@huftis.org CC: joshiesuha...@gmail.com Target Milestone: --- Created attachment 157007 --> https://bugs.kde.org/attachment.cgi?id=157007=edit Video demonstrating checkbox bug SUMMARY If you add a new filesystem path access, the following checkboxes are messed up, e.g., one is completely missing a label, and other checkboxes change name when you click on them. See the attached video demonstrating the bug. STEPS TO REPRODUCE 1. Choose an application. 2. Click the ‘Add New’ button and add a new path. 3. Click on any of the following checkboxes. OBSERVED RESULT The checkboxes change labels when clicked on, and one has no label initially. EXPECTED RESULT Checkboxes should stay the same as before clicking adding a path. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230303 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 466257] Wrong calculation of cache size?
https://bugs.kde.org/show_bug.cgi?id=466257 --- Comment #4 from Karl Ove Hufthammer --- BTW, thanks for fixing this bug. And I’ve added a bug report (bug 466468) for general spinbox support for formatting of byte values. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 466468] Implement a spinbox for byte values respecting BinaryUnitDialect
https://bugs.kde.org/show_bug.cgi?id=466468 Karl Ove Hufthammer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=364321 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 364321] GUI to switch from JEDEC to SI units
https://bugs.kde.org/show_bug.cgi?id=364321 Karl Ove Hufthammer changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=466468 --- Comment #30 from Karl Ove Hufthammer --- FYI: I’ve added a bug report (bug 466468) for spinbox support for formatting of byte values (respecting BinaryUnitDialect). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 466468] New: Implement a spinbox for byte values respecting BinaryUnitDialect
https://bugs.kde.org/show_bug.cgi?id=466468 Bug ID: 466468 Summary: Implement a spinbox for byte values respecting BinaryUnitDialect Classification: Frameworks and Libraries Product: frameworks-kcoreaddons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: k...@huftis.org CC: kdelibs-b...@kde.org Target Milestone: --- There is a need for a QSpinBox for byte values (bytes, KiB, kB, MiB, MB etc.) that supports BinaryUnitDialect (see bug 364321) and localisation (KFormat does supoprt localisation, https://api.kde.org/frameworks/kcoreaddons/html/classKFormat.html). Suggested name: KByteSpinBox The idea is that it would hold a byte value, but it would be formatted as either bytes, KiB, kB, MiB, MB etc. depending on the user’s BinaryUnitDialect and language/locale settings. In other words, when displaying the byte value, it would be divided 1000, 1024 etc., and the suffix would be set to kB/KB/KiB. This is needed in Dolphin (bug 453853), Konqueror (bug 466257) and probably other applications too. It should be possible to specify a fixed ‘major’ unit (e.g., *always* shows the value as KiB/kB/KB, even for very large values) or have the widget (by default) automatically choose the unit based on the value (bytes for values < 1000 or 1024, kB/KiB for larger values, MB/MiB for even larger values), cf. the AutoAdjust feature in KFormat::UnitPrefix. Advantages: * BinaryUnitDialect would be respected (bug 364321) * The unit suffix would be automatically localised * The implementation of byte value widgets in applications would be simpler: * No need for manually dividing by 1000, 1024 etc. in various functions * No need for manually handling large ranges (e.g., from bytes to GiB) * No need for manually formatting the values when getting/setting byte values, adding/stripping suffixes -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 466257] Wrong calculation of cache size?
https://bugs.kde.org/show_bug.cgi?id=466257 --- Comment #3 from Karl Ove Hufthammer --- (In reply to Stefano Crocco from comment #1) > Thanks for pointing this out. The conversion factor is clearly wrong and > I'll fix it immediately. I'm not sure, instead, about using KFormat here. As > far as I can see, KFormat only returns a string representation of the number > converted to the appropriate unit, but this won't be useful here, as I need > to put the value inside a QSpinBox, which only accepts numbers. Of course I > could use KFormat to convert a dummy value, then extract the unit from the > string, but I'm not sure it's worth doing so. Could you please clarify your > suggestion? Hmm, I’m not actually sure what the best solution is. The idea was that the spinbox would support the BinaryUnitDialect setting (see bug 364321), so that spinbox should hold the number of *bytes*, but would be formatted as 'kB’, ‘KIB’ or ‘KB’ (or ‘MB’/‘MiB’) depending on the user‘s BinaryUnitDialect settings (and with the proper conversion factor, e.g. 1000 or 1024). But this is complicated to implement, and it’s not a good idea that every program with a ‘byte spinbox’ should have a complicated workaround for handling it. There really should be a general ByteSpinBox that would handle this automatically. (See also bug 453853 for a similar problem in Dolphin.) For now, I guess it’s OK to have the text hardcoded as ‘MB’. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453853] file size display: please follow BinaryUnitDialect everywhere
https://bugs.kde.org/show_bug.cgi?id=453853 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org --- Comment #2 from Karl Ove Hufthammer --- This also applies to displaying file sizes in the settings dialog, e.g., for the ‘Skip previews for local files above:’ setting (‘General’ category). Here (file settings/general/previewssettingspage.cpp) the value is hardcoded using the (translatable) string ‘MiB’. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466127] Tiling configuration works erratically on cloned screens
https://bugs.kde.org/show_bug.cgi?id=466127 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 466257] New: Wrong calculation of cache size?
https://bugs.kde.org/show_bug.cgi?id=466257
Bug ID: 466257
Summary: Wrong calculation of cache size?
Classification: Applications
Product: konqueror
Version: Git
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konq-b...@kde.org
Reporter: k...@huftis.org
Target Milestone: ---
I took a look at the source code in konqueor/settings/konqhtml/cache/cache.cpp,
and the following two lines look wrong to me:
In void Cache::load():
//Ensure that maxSizeInMB is greater than 0 if maxSizeInBytes is not 0
int maxSizeInMB = maxSizeInBytes == 0 ? 0 : std::max(1, maxSizeInBytes /
1000);
In void Cache::save():
//We store the size in bytes, not in MB
grp.writeEntry("MaximumCacheSize", m_ui->cacheSize->value()*1000);
If you divide the number of bytes by 1000, you get kB, *not* MB. Similarly, if
you multiply an MB value by 1000, you get the number of kB, not the number of
bytes.
In the UI (cache.ui), the suffix is set to ‘ MB’. So either the calculation
should be changed to divide/multiply by 1000^2, or the UI string should be
changed to ‘ kB’, or, preferably, to use the correct KFormat feature for proper
formatting (https://api.kde.org/frameworks/kcoreaddons/html/classKFormat.html).
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 465843] New: Feature request: Show indicator for new folders and files
https://bugs.kde.org/show_bug.cgi?id=465843 Bug ID: 465843 Summary: Feature request: Show indicator for new folders and files Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@huftis.org CC: kfm-de...@kde.org Target Milestone: --- This is a suggestion for a new feature: At work, I noticed that Microsoft SharePoint / OneDrive has a usability feature I actually like. *New* folders and files are marked with a special indicator (three small lines). This makes it very easy to spot them in the folder view. Here are a few screenshots (taken from the web) illustrating how it looks: * https://lh3.googleusercontent.com/Bqn_TlvCYG2dmRZpzwV9fijDRTQ7-L6Ov-OITpIfGa65WEqeVLA1AX6i1xmFdXUdvkbxkdEeQwfQux6BFftKtW0czR2TqWL_3_KXpKaf3VZzVFaN4UEgJlw2IQOGthgsAaY--Wm1 * https://filestore.community.support.microsoft.com/api/images/e87a4593-bc74-4f62-9c82-0644c9e9e201 * https://techcommunity.microsoft.com/t5/image/serverpage/image-id/23878i9608333CE926FD1B/image-size/large?v=v2=999 According to the documentation (https://support.microsoft.com/en-us/office/what-do-the-onedrive-icons-mean-11143026-8000-44f8-aaa9-67c985aa49b3#ID0EBH=Web), the three lines are called ‘glimmer marks’. I don’t have any strong preferences regarding the implemention, e.g., how the indicator should look (though I find the sparkling ‘glimmer marks’ very intuitive), or what ‘new’ should be (created in the last 24 hours, created in the current session, perhaps also including ‘recently modified’ files?). But I find the actual feature very useful, as it makes it easier and faster to find the folders/files one is *most likely* to open/edit, without having to sort by ‘last modified’. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464823] Soft hyphens are incorrectly displayed as normal spaces
https://bugs.kde.org/show_bug.cgi?id=464823 --- Comment #2 from Karl Ove Hufthammer --- (In reply to Matan Ziv-Av from comment #1) > This is an unintentional change of behaviour, but I am not sure it is a bug. The character is shown as space. The Unicode standard specifies that is should be invisible. I think that makes it a bug. Here’s the relevant section in the latest version of the Unicode standard (section 5.21) (earlier versions have similar text): https://www.unicode.org/versions/Unicode15.0.0/ch05.pdf U+00AD: soft hyphen has a null default appearance in the middle of a line: the appearance of “ther[shy]apist” is simply “therapist”—no visible glyph. In line break processing, it indicates a possible intraword break. At any intraword break that is used for a line break—whether resulting from this character or by some automatic process—a hyphen glyph (perhaps with spelling changes) or some other indication can be shown, depending on language and context. > Do you edit text with a soft hyphen in konsole, or only view files? Well, I *sometimes* edit text with soft hyphens in Konsole (or Yakuake, to be precise). But *mostly* I use Kate or other text editors (or other software) when editing text. I frequently *view* files (or application output) with soft hyphens in Konsole/Yakuake. > If you copy this text to the command line in konsole 22.08, you will see that > this > confuses bash and the cursor is displayed in the wrong place. And that should be considered a bug. To clear up, the behaviour I would *expect*, is the same behaviour as Kate (which also uses a monospace font by default, and thus should be comparable) has. That is: * The character should be invisible. * When moving the cursor using the arrow keys, the soft hyphen should function as if it were a normal (but zero-width) character. For example, if the cursor is positioned right after the ‘e’ in ther[shy]apist, you need to press the right arrow key three times (not two) to move it to right after the ‘a’. (The first moves it to the right of the r, the second to the right of the soft hyphen, and the third to the right of the a.) * Regarding the display of the cursor: In Kate when the cursor is an ‘I beam’, for the example above, the cursor moves to the right for the first key press, doesn’t move horizontally for the next key press (which really moves it from ‘to the left of the soft hyphen’ to ‘to the right of the soft hyphen’), and moves to the right for the third key press. If the cursor is a block (insert mode), the current/selected character is shown with a blinking block behind. (So if the soft hyphen is selected, the cursor is invisible. Perhaps a tiny bit confusing, but it is consistent, as we‘re ‘highlighting’ an invisible character. (BTW, I am familiar with the arguments in Jukka Korpela‘s article 1997 article on the soft hyphen, and even read it around the time it was originally written. I don’t think it’s at all relevant now that the entire world has moved to Unicode and uses Unicode semantics for all characters.) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 464823] New: Soft hyphens are incorrectly displayed as normal spaces
https://bugs.kde.org/show_bug.cgi?id=464823 Bug ID: 464823 Summary: Soft hyphens are incorrectly displayed as normal spaces Classification: Applications Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: k...@huftis.org Target Milestone: --- SUMMARY When text contains soft hyphens, the soft hyphen characters (U+00AD) are now displayed as normal spaces. They should instead be invisible, and used to be so, so this is a regression. I did a ‘git bisect’, and it looks like the bug was introduced in this commit: commit 76f879cd70fb494ab2334d2660b34679546f3d9d Author: Matan Ziv-Av Date: Sat Aug 6 19:15:42 2022 +0300 Draw characters in exact positions […] STEPS TO REPRODUCE 1. Run the following command in Konsole: echo -e 'super\u00adcali\u00adfragi\u00adlistic\u00adexpi\u00adali\u00addocious' OBSERVED RESULT The text is displayed as: super cali fragi listic expi ali docious EXPECTED RESULT The text should be displayed as: supercalifragilisticexpialidocious SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230123 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 ADDITIONAL INFORMATION If the word comes at the end of a line and causes the word to be split over two lines *at the soft hyphen*, the soft hyphen should really be displayed as a *normal* hyphen instead of being invisible. This is the way soft hyphens normally work, e.g., in Kate. But I guess this is a less important feature for a terminal application, which usually doesn’t do any real word wrapping. Just thought I would mention it. And regarding the use of soft hyphens: I’m a translator of KDE applications, and we use soft hyphens a lot in our translations, also for command-line applications. This bug causes the output (e.g., of ’--help’) to look incorrect (long words are being split). -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 464630] Multi-line strings are not extracted for translation
https://bugs.kde.org/show_bug.cgi?id=464630 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 398657] Loading games shouldn’t change the game settings
https://bugs.kde.org/show_bug.cgi?id=398657 --- Comment #3 from Karl Ove Hufthammer --- (In reply to Stephan Kulow from comment #2) > I don't disagree that it's strange behaviour - but it's not really a bug. > Because if you load a draw 1 game, you want the menu to reflect that. And if > you start a game after the save game you also expect it to continue as such. > This is not the "default" - it's the current state. > > What you're asking for implicitly is to split klondike 1 and klondike 3 into > different flavors you can switch between. Not really. I am OK with the menu reflecting the settings from the loaded game. But the settings from the game should not be saved in .config/kpatrc. So when quitting and restarting KPat, the settings should be the old/‘default’ (manually chosen) settings, not the settings from the game I loaded the previous session. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463933] Missing charts (qtcharts dependency) in fractions activity
https://bugs.kde.org/show_bug.cgi?id=463933 --- Comment #3 from Karl Ove Hufthammer --- That is, I compiled GCompris myself. I used my distro‘s package of the Qt Charts plugin (which isn’t installed by default). -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463933] Missing charts (qtcharts dependency) in fractions activity
https://bugs.kde.org/show_bug.cgi?id=463933 --- Comment #2 from Karl Ove Hufthammer --- Yes, I compiled it myself (using cmake and Ninja). -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463938] New: Autonomous communities of Spain includes entities that are not autonomous communities
https://bugs.kde.org/show_bug.cgi?id=463938 Bug ID: 463938 Summary: Autonomous communities of Spain includes entities that are not autonomous communities Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY In the geo-country activity for Spain (activities/geo-country/resource/board/board18_0.qml), the title ‘Autonomous communities of Spain’ is misleading. The level includes Ceuta and Melilla, which are *not* autonomous communities, but autonomous cities. Source and more details on the difference: https://en.wikipedia.org/wiki/Autonomous_communities_of_Spain STEPS TO REPRODUCE 1. Open the geo-country activity for Spain. OBSERVED RESULT Title: Autonomous communities of Spain EXPECTED RESULT Title: Autonomous communities or cities of Spain or Title: Autonomous communities/cities of Spain -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463937] New: The ‘Find numerator/denominator’ fractions levels are confusing numerators with denominators
https://bugs.kde.org/show_bug.cgi?id=463937 Bug ID: 463937 Summary: The ‘Find numerator/denominator’ fractions levels are confusing numerators with denominators Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY The wording is wrong in the ‘Find numerator’ and ‘Find denominator’ level names. In the ‘Find numerator’ levels, you are asked to find a denominator, and in the ‘Find denominator’ levels, you are asked to find a numerator. STEPS TO REPRODUCE 1. Open the ‘Find fractions’ activity. 2. Open the level selector. 3. Select only ‘Find numerator’ levels (or only ‘Find denominator’ levels). OBSERVED RESULT You are asked to select a denominator. (The opposite is true of you select a denominator level.) EXPECTED RESULT You should be asked to select a numerator. (Or a denominator, if you selected a denominator level.) -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463936] New: Confusing wording in fractions activity
https://bugs.kde.org/show_bug.cgi?id=463936 Bug ID: 463936 Summary: Confusing wording in fractions activity Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY In the ‘rectangle’ levels of the fractions activity, one or more squares are shown, and each square is divided into rectangles. I therefore find it a bit confusing that the instructions say, e.g., ‘Select 1.5 rectangles’. What one should actually do in this case, is select 1.5 *squares*, i.e., one square and one half square (or the number of rectangles corresponding to 1.5 squares). It’s not *technically* wrong, since a square is also a rectangle, but it would be much less confusing if the instructions used the word ‘square’ when talking about the squares. People usually don’t think about rectangles as squares. (And the charts do also contain non-square rectangles.) STEPS TO REPRODUCE 1. Launch a ‘rectangle’ fraction activity. OBSERVED RESULT The instructions talks about selecting rectangles. EXPECTED RESULT The instructions should instead talk about selecting squares. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463933] New: Missing charts (qtcharts dependency) in fractions activity
https://bugs.kde.org/show_bug.cgi?id=463933 Bug ID: 463933 Summary: Missing charts (qtcharts dependency) in fractions activity Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY When I launch the new fraction activity, no chart is displayed on the screen, only a fraction. So the activity makes no sense. (The help file says ‘A shape split in equal parts is displayed on screen.‘, but no shape is shown.) On the terminal, I found this error message: qrc:/gcompris/src/activities/fractions_create/PieChart.qml:7:1: module "QtCharts" is not installed After I installed the libqt5-qtcharts-imports package on my system (openSUSE Tumbleweed), everything works correctly (a pie chart is shown). So this bug is really about the build system. I can build GCompris without having libqt5-qtcharts-imports installed, and there are no errors or warnings indicating this, only a non-functioning activity. STEPS TO REPRODUCE 1. Build GCompris without the Qt Charts library installed (using the cmake command). 2. Start the fraction activity OBSERVED RESULT Not chart displayed. EXPECTED RESULT When running cmake, there should be an error that the Qt Charts library is missing. (Alternatively, the two fraction activities should be automatically disabled due to a missing dependency. But I prefer an error, as it is easy to overlook disabled activities.) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230102 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7673 System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 463899] New: Inconsistent max values in ‘Compare numbers’ activity
https://bugs.kde.org/show_bug.cgi?id=463899 Bug ID: 463899 Summary: Inconsistent max values in ‘Compare numbers’ activity Classification: Applications Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY Not technically a bug, but I find it very surprising that the max values are inconsistent in the four ‘Compare numbers’ that involve decimals. For two decimals, the max is 99.99, but for three decimals, it’s 99.000, not 99.999. For one decimal (two levels), it’s 9.0. So when the integer part is 0, 1, …, 8, the fractional part can be .0, .1, .2, .3, …, .9, but when it is 9, the fractional part can only be .0. STEPS TO REPRODUCE 1. Start the ‘Compare numbers’ activity 2. Look at the level selector OBSERVED RESULT For decimal levels, the max is 9.0 (two levels), 9.99, and 999.000. EXPECTED RESULT The max should be 9.9, 9.99 and 999.999 (both in the description and in the actual level files). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393956] Digital Clock widget add custom time format
https://bugs.kde.org/show_bug.cgi?id=393956 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 188476] You're returned back to the full desktop for a few seconds after confirming shutdown/logout/restart
https://bugs.kde.org/show_bug.cgi?id=188476 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455992] spice-vdagentd/spice-vdagent does not start
https://bugs.kde.org/show_bug.cgi?id=455992 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 377955] yakuake does no longer accept input
https://bugs.kde.org/show_bug.cgi?id=377955 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 458134] Suggestion for new (and more challenging) mouse practice activity
https://bugs.kde.org/show_bug.cgi?id=458134 --- Comment #3 from Karl Ove Hufthammer --- Regarding the difficulty, the (quite entertaining) review at https://www.youtube.com/watch?v=EIcImzLNMz8 makes a few good points. In the original game, you continue to lose lives at a rapid pace if your cursor doesn’t immediately move away from the enemy you touched. And it’s possible to start a level with the enemies positioned where your cursor is, so that you lose even more lives. This could be fixed by you getting invincible (e.g., indicated by a colour change for your cursor) for a short while whenever you are touched by an enemy. And by ensuring that no enemies appear at same position as the cursor at the beginning of the game, or by having a ‘safe’ zone. BTW, I found that someone created an Android clone of the original game. It actually works quite well on a touch screen: https://play.google.com/store/apps/details?id=at.therefactory.jewelthief -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 458134] New: Suggestion for new (and more challenging) mouse practice activity
https://bugs.kde.org/show_bug.cgi?id=458134 Bug ID: 458134 Summary: Suggestion for new (and more challenging) mouse practice activity Product: gcompris Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY This is just a suggestion (wishlist item). I found the game Jewel Thief on an old floppy disk and thought that the gameplay would be a nice fit for GCompris, as a new, fun and more challenging mouse practice activity. You can play it online at the Internet Archive: https://archive.org/details/JewelThief_1020 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 441001] Elisa ignores ratings for music files rated outside of Elisa
https://bugs.kde.org/show_bug.cgi?id=441001 --- Comment #4 from Karl Ove Hufthammer --- Note that different file formats (mp3, ogg, m4a, wma, …) all use different tags for storing rating information *and* different numeric rating scales (e.g., 0–100 or 0–255) *and* different number-to-stars cut-offs. To properly handle this, take a look at how it’s implemented in Kid3 (the ‘Settings → Tags → All Tags → Rating’ table and the ‘ratingstars’ pseudo tag in the development version). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435863] digikam "looses" manually tagged faces
https://bugs.kde.org/show_bug.cgi?id=435863 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 454437] Ratings written using kid3-cli are inconsistently stored
https://bugs.kde.org/show_bug.cgi?id=454437 --- Comment #7 from Karl Ove Hufthammer --- I’ve now done some testing, for various audio formats. Setting and getting a 1–5 star rating seems to work fine. Retrieving the ‘rating’ also seems to return the correct numerical rating for each format. But using the binary from https://sourceforge.net/projects/kid3/files/kid3/development/kid3-git20220528-win32-x64.zip/download, I get an error message when I try to set a rating on the .ogg file: /path/kid3-git20220528-Linux/kid3-cli: symbol lookup error: /path/kid3-git20220528-Linux/plugins/liboggflacmetadata.so: undefined symbol: __pow_finite (A similar .opus file works fine.) Also, I think trying to set an invalid star rating (e.g. ‘3.7’, ‘-1’, 6 or ‘foo’) should result in an error message (and no stored rating). Currently, it doesn’t. I’m not sure how *getting* an non-numerical rating (e.g., ‘foo’) as a ‘ratingstars’ value should be handled. Perhaps returning an empty value? Currently, the stored value (e.g., ‘foo’ for most formats, 0 for some) is returned. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 454437] Ratings written using kid3-cli are inconsistently stored
https://bugs.kde.org/show_bug.cgi?id=454437 --- Comment #5 from Karl Ove Hufthammer --- (In reply to Urs Fleisch from comment #4) > You can find a development snapshot Kid3 git20220528 in > https://sourceforge.net/projects/kid3/files/kid3/development/ where I have > implemented 'get ratingstars' and 'set ratingstars' for kid3-cli. Thanks, I’ll take a look. BTW, is there a reason this update isn’t available at https://invent.kde.org/multimedia/kid3? > - You still can only set full stars, not half stars or other fractions. That’s OK for me. :) > - If you use `kid3-cli -c "set ratingstars 2" *` this will not work > correctly when files with different tag formats are included by `*`. The > reason is by design: When a frame is added or edited on multiple files, it > is only created once and then pasted into the remaining files, so this will > only work when using ratingstars with files having the same tag format. In > other cases, you should write the tags separately, e.g. using `for i in *; > do kid3-cli -c 'set ratingstars 2' $i; done`. OK. But I think this is very surprising behaviour, so shouldn’t it be mentioned in the documentation? -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 454437] Ratings written using kid3-cli are inconsistently stored
https://bugs.kde.org/show_bug.cgi?id=454437 --- Comment #3 from Karl Ove Hufthammer --- > So I think that it would be best to support something like > > kid3-cli -c "set rating '***'" file.mp3 > > whereas using number would still provide the current low-level interface. > What do you think? Yes, I think that could work. But I think it’s a bit strange that the stars have to be quoted, so I would prefer: kid3-cli -c 'set rating ***' file.mp3 Also, this syntax can’t support half-stars (e.g., 3.5 stars), which is supported in some media players. (It is also used in the KDE rating system, e.g., shown in Dolphin, though this currently doesn’t read rating tags from audio files.) So I think a cleaner implementation would be: kid3-cli -c 'set stars 3' file.mp3 or kid3-cli -c 'set ratingstars 3' file.mp3 and where one can use half-stars: kid3-cli -c 'set ratingstars 3.5' file.mp3 (And this should give an error for invalid rating star values.) -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 454437] Ratings written using kid3-cli are inconsistently stored
https://bugs.kde.org/show_bug.cgi?id=454437 Karl Ove Hufthammer changed: What|Removed |Added Attachment #149231|0 |1 is obsolete|| --- Comment #1 from Karl Ove Hufthammer --- Created attachment 149232 --> https://bugs.kde.org/attachment.cgi?id=149232=edit Zip file containing audio files in different formats Here’s an updated attachment (the last one had some metadata stored). -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 454437] New: Ratings written using kid3-cli are inconsistently stored
https://bugs.kde.org/show_bug.cgi?id=454437 Bug ID: 454437 Summary: Ratings written using kid3-cli are inconsistently stored Product: kid3 Version: 3.9.x Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: k...@huftis.org Target Milestone: --- Created attachment 149231 --> https://bugs.kde.org/attachment.cgi?id=149231=edit Zip file containing audio files in different formats SUMMARY When I set ratings using the GUI, they are correctly stored in the files, using each file format’s rating system. For example, see the attached files (with no ratings). If I set the rating to 4/5 stars in the UI, the following information is saved in the files: m4a: 80 (Rating Percent) mp3: 196 (Popularimeter) ogg: 80 wma: 75 (Shared User Rating) If I reopen the files, they are all (correctly) shown was 4/5 stars in the UI. However, if I use the command-line to try to do the same thing, the rating mapping doesn’t work. And which ratings are saved depends on *how* I invoke kid3-cli: 1) separate command for each file, or 2) using filename wildcards. If I do: for i in *; do kid3-cli -c 'set Rating 80' $i; done I get the following in the UI: m4a: 4 stars mp3: 2 stars ogg: 4 stars wma: 80 (numeric value, no stars shown) If I instead do: kid3-cli -c 'set Rating 80' * I get the following the UI: m4a: 80 (Rating Information) mp3: 80 (Rating Information) ogg: 80 (RATING INFORMATION) wma: 80 (Rating Information) STEPS TO REPRODUCE 1. Unzip the attached file into an empty folder. 2. In this folder, type: for i in *; do kid3-cli -c 'set Rating 80' $i; done 3. Unzip the attached file into another folder. 4. In this second folder, type: kid3-cli -c 'set Rating 80' * OBSERVED RESULT See above. EXPECTED RESULT The two methods of invoking kid3-cli should result in the *same* ratings stored. And the ratings should correspond to 4/5 stars. (Though I’m not sure the ‘Rating’ field is the correct field to use, as the scale is ill-defined. Perhaps a new field called ‘Stars’ or ‘RatingStars’ could be added?) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220522 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.9-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 433509] "Play count" actually measures only skips, not full plays
https://bugs.kde.org/show_bug.cgi?id=433509 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 441001] Elisa ignores ratings for music files rated outside of Elisa
https://bugs.kde.org/show_bug.cgi?id=441001 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 444475] can't find music on Android
https://bugs.kde.org/show_bug.cgi?id=75 Karl Ove Hufthammer changed: What|Removed |Added CC||k...@huftis.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407619] Impossible to change the wallpaper immediately after changing the layout setting
https://bugs.kde.org/show_bug.cgi?id=407619 Karl Ove Hufthammer changed: What|Removed |Added Version|5.21.90 |5.24.4 Component|Desktop Containment |Image Wallpaper CC||k...@huftis.org, ||notm...@gmail.com --- Comment #3 from Karl Ove Hufthammer --- Still valid in Plasma 5.24.4. After changing to a new layout and selecting a new wallpaper, the ‘Apply’ button is greyed out and can’t be clicked, while the ‘OK’ button closes the dialogue but doesn’t change the wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452473] Krita doesn’t use color profile info in WebP files
https://bugs.kde.org/show_bug.cgi?id=452473 --- Comment #1 from Karl Ove Hufthammer --- Created attachment 148089 --> https://bugs.kde.org/attachment.cgi?id=148089=edit Corresponding JPEG version -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 452473] New: Krita doesn’t use color profile info in WebP files
https://bugs.kde.org/show_bug.cgi?id=452473 Bug ID: 452473 Summary: Krita doesn’t use color profile info in WebP files Product: krita Version: 5.0.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: k...@huftis.org Target Milestone: --- Created attachment 148088 --> https://bugs.kde.org/attachment.cgi?id=148088=edit WebP image with embedded colour profile SUMMARY Krita seems to interpret WebP files as being in the sRGB colour space even if they contain an embedded colour profile which says otherwise. STEPS TO REPRODUCE 1. Open the attached WebP image. 2. Look at the colours and in the text in the status bar. OBSERVED RESULT The colours look dull and the status bar says ‘sRGB-elle-V2-srgbrc.icc’. EXPECTED RESULT The colours should look bright and the status bar should say ‘WideRGB-elle-V2-srgbtrc.icc’. For comparison, open the attached JPEG version of the same image. Here the colours look bright and the correct colour profile is used. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220405 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.17.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-2500 CPU @ 3.30GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 ADDITIONAL INFORMATION The application Gwenview handles the WebP image properly, i.e. the colours are shown as bright, which indicates that the profile is correctly embedded. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 449522] Yakuake occasionally crashes when selecting text
https://bugs.kde.org/show_bug.cgi?id=449522 --- Comment #2 from Karl Ove Hufthammer --- Created attachment 147684 --> https://bugs.kde.org/attachment.cgi?id=147684=edit New crash information added by DrKonqi yakuake (21.12.3) using Qt 5.15.2 - What I was doing when the application crashed: Right-clicking on a link (the output of pwd). -- Backtrace (Reduced): #4 0x7f147df62ed4 in QScopedPointerDeleter::cleanup (pointer=0x559240fd91b0) at /usr/include/qt5/QtCore/qscopedpointer.h:52 #5 QScopedPointer >::~QScopedPointer (this=, __in_chrg=) at /usr/include/qt5/QtCore/qscopedpointer.h:107 #6 Konsole::SessionController::showDisplayContextMenu (this=, position=...) at /felles/kde/konsole/src/session/SessionController.cpp:1907 [...] #8 0x7f147deb8d35 in Konsole::TerminalDisplay::configureRequest (this=this@entry=0x559240e4c790, _t1=...) at /felles/kde/konsole/build/src/konsoleprivate_autogen/DRAQINE3W2/moc_TerminalDisplay.cpp:492 #9 0x7f147df2efda in Konsole::TerminalDisplay::mousePressEvent (this=0x559240e4c790, ev=0x7ffd67d7aad0) at /felles/kde/konsole/src/terminalDisplay/TerminalDisplay.cpp:1225 -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 450481] New: Bargame activites are not in the right order in menu
https://bugs.kde.org/show_bug.cgi?id=450481 Bug ID: 450481 Summary: Bargame activites are not in the right order in menu Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY In the menu, the two bargame activities are separated by the two ‘Align four‘ activities, instead of being next to each other. For all the other activity pair, the two activities are next to each other. STEPS TO REPRODUCE 1. Click the frog in the menu. OBSERVED RESULT The order of the activities are: Bargame (against Tux) Align four (with a friend) Align four (against Tux) Bargame (with a friend) Nine men’s morris (against Tux) Nine men’s morris (with a friend) Play oware against Tux Play oware with a friend Tic tac toe (against Tux) Tic tac toe (with a friend) … EXPECTED RESULT The two bargames should be next to each other, e.g.: Bargame (against Tux) Bargame (with a friend) Align four (with a friend) Align four (against Tux) Nine men’s morris (against Tux) Nine men’s morris (with a friend) Play oware against Tux Play oware with a friend Tic tac toe (against Tux) Tic tac toe (with a friend) … ADDITIONAL INFORMATION Some more consistency in the naming and order of the *other* activities would also be nice, e.g., 1) always show the ‘against Tux‘ before the corresponding ‘with a friend’ activity (it’s this way for most of them, but not for the ‘Align four’ activities), 2) be consistent with the use of parenthesis (used for most activities) or not (oware activity), 3) be consistent with ‘against Tux’ or ‘against the computer’, 4) be consistent with ‘with a friend’ or ‘with your friend’ or ‘against your friend’). -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 450480] New: Baby keyboard activity has only English letters
https://bugs.kde.org/show_bug.cgi?id=450480 Bug ID: 450480 Summary: Baby keyboard activity has only English letters Product: gcompris Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jaz...@gmail.com Reporter: k...@huftis.org Target Milestone: --- SUMMARY The baby keyboard activity has only English letters + digits. STEPS TO REPRODUCE 1. Start baby keyboard activity in a non-English locale. OBSERVED RESULT The keyboard contains the digits 0–9 and the letters a-z. EXPECTED RESULT The keyboard should (in addition) contain all letters in the alphabet for the current language. For example, for Norwegian Nynorsk (nn language / nn_NO.utf8 locale), it should also contain the letters æ, ø and å. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220215 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.8-1-default (64-bit) ADDITIONAL INFORMATION Other activities that use a virtual keyboard contain the correct letters. -- You are receiving this mail because: You are watching all bug changes.
[gcompris] [Bug 448161] Response field and buttons in decimal activities doesn’t use localised decimal mark
https://bugs.kde.org/show_bug.cgi?id=448161 --- Comment #7 from Karl Ove Hufthammer --- Also note that ‘ApplicationSettings.locale‘ is ‘system’, and if I change Qt.locale(ApplicationSettings.locale).decimalPoint to just Qt.locale().decimalPoint I get the correct decimal point (at least for my current locale). -- You are receiving this mail because: You are watching all bug changes.
