[dolphin] [Bug 371765] Documents suddenly open as archives
https://bugs.kde.org/show_bug.cgi?id=371765 Paul changed: What|Removed |Added CC||pip@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 --- Comment #7 from Paul --- Hello... ... any progress on this yet? :) Thanks. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 347210] Usability issues with klipper menu
https://bugs.kde.org/show_bug.cgi?id=347210 --- Comment #4 from Paul --- (In reply to Ricardo J. Barberis from comment #3) > @Paul, you may want to try the kilpper application ... I have been using that for some time now, (rather than the new clipboard plasmoid). Not only due to this and https://bugs.kde.org/show_bug.cgi?id=343519 but also to the fact that "Ignore Images" is not working as intended. (https://bugs.kde.org/show_bug.cgi?id=348932 and https://bugs.kde.org/show_bug.cgi?id=349509 ) Nonetheless, thanks for the pointer. :) -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453520] Kstars aborts after first image is captured in a sequence
https://bugs.kde.org/show_bug.cgi?id=453520 --- Comment #1 from Paul --- A minor update. Retested this today, after rebuilding stellarsolver, indi, indi-3rdparty and kstars and it is still aborting, making it impossible for me to use. As previously noted this is working under Buster but not under Bullseye. Paul -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459016] New: A "Terminal" launched from Dolphin (F4) always uses konsole's "Built-in" profile, not the currently defined default.
https://bugs.kde.org/show_bug.cgi?id=459016 Bug ID: 459016 Summary: A "Terminal" launched from Dolphin (F4) always uses konsole's "Built-in" profile, not the currently defined default. Product: dolphin Version: 22.08.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: terminal Assignee: dolphin-bugs-n...@kde.org Reporter: pip@gmx.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 151998 --> https://bugs.kde.org/attachment.cgi?id=151998&action=edit Screenshot showing konsole's "Built-in" profile when launched from Dolphin. SUMMARY When launching konsole from Dolphin (F4) the konsole profile used is always "Built-in" not the currently defined "Default" STEPS TO REPRODUCE 1. Set konsole's default profile to other than "Built-in" (Apply and Exit) 2. Launch konsole from Dolphin using F4 3. OBSERVED RESULT konsole uses it's "Built-in" profile, not the one set as default EXPECTED RESULT konsole uses it's currently set default SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220907 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-1-default (64-bit) ADDITIONAL INFORMATION See attached screenshot. konsole is set to "Profile 1" as default which (amongst other changes from "Built-in) has green text on a black background. When konsole is launched from within Dolphin it uses the "Built-in" profile, not "Profile 1" it's currently set default profile. This is a regression, as previously konsole (launched from Dolphin) used it's default profile. Unfortunately I'm unsure of when the regression was introduced. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 459016] A "Terminal" launched from Dolphin (F4) always uses konsole's "Built-in" profile, not the currently defined default.
https://bugs.kde.org/show_bug.cgi?id=459016 Paul changed: What|Removed |Added Attachment #151998|0 |1 is obsolete|| --- Comment #1 from Paul --- Created attachment 152000 --> https://bugs.kde.org/attachment.cgi?id=152000&action=edit Screenshot showing konsole's "Built-in" profile when launched from Dolphin. OK - Lets attach the correct image. Could an admin please remove attachment 151998 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459018] New: Menus not rendering correctly in full screen mode.
https://bugs.kde.org/show_bug.cgi?id=459018 Bug ID: 459018 Summary: Menus not rendering correctly in full screen mode. Product: gwenview Version: 22.08.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: pip@gmx.com Target Milestone: --- Created attachment 152001 --> https://bugs.kde.org/attachment.cgi?id=152001&action=edit Screenshot showing rendering issue with menus whilat in full screen mode. SUMMARY In Full Screen Mode (CTRL-SHIFT-F1) menus are not rendering correctly - see attached screen-shot. STEPS TO REPRODUCE 1. Launch gwenview 2. Select image 3. Switch to Full Screen 4. Display menu (right click context menu for example) OBSERVED RESULT Menu unreadable EXPECTED RESULT Normal menu SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220907 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.7-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ Memory: 3.8 GiB of RAM Graphics Processor: NV84 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459018] Menus not rendering correctly in full screen mode.
https://bugs.kde.org/show_bug.cgi?id=459018 --- Comment #2 from Paul --- Created attachment 152042 --> https://bugs.kde.org/attachment.cgi?id=152042&action=edit screen-shot gwenview full screen menu - breeze classic colour scheme (In reply to Nate Graham from comment #1) > Have you done anything to suppress it or force a different color > scheme? Not that I'm aware of. Using colour scheme "Oxygen" with it's default colours. Tried with "Breeze Classic", problem still present. (Attached screen-shot) I have one machine here still running openSUSE Leap 15.3 which has: KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 Gwenview full screen menus displayed are correctly on that, using the same "Oxygen" colour scheme. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459018] Menus not rendering correctly in full screen mode.
https://bugs.kde.org/show_bug.cgi?id=459018 Paul changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 459018] Menus not rendering correctly in full screen mode.
https://bugs.kde.org/show_bug.cgi?id=459018 --- Comment #4 from Paul --- Switching to Application Style Breeze does in fact restore the correct display of menus in Gwenview's full screen mode. (It wasn't Fusion, I use QtCurve as I find it's the most compact of all the styles). The only problem there of course is I don't want to use Breeze... and, it previously worked OK Incidentally, what's the rationale for Gwenview's use of a custom colour scheme in full screen mode? A colour scheme set by the user shouldn't really be over-ridden by an application, that's rather bad form old boy; more so if the users colour scheme has been chosen to maximize readability/visibility due to a vision defect. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 402004] k3b issues System Probe warning for locale when using custom regional settings.
https://bugs.kde.org/show_bug.cgi?id=402004 Paul changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from Paul --- Closing some of my old bug reports that aren't being acted upon. (There needs to be a resolution category "Died - Old Age") To anyone on the "cc" list - please re-open if you feel the need. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 348393] Style -> Win Deco: No option to add 'Spacer' to Title Bar
https://bugs.kde.org/show_bug.cgi?id=348393 Paul changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #6 from Paul --- Closing some of my old bug reports that aren't being acted upon. (There needs to be a resolution category "Died - Old Age") To anyone on the "cc" list - please re-open if you feel the need. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389422] Feature request: Ability to restore previous Zoom state on Geolocation (Map) Views.
https://bugs.kde.org/show_bug.cgi?id=389422 Paul changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #1 from Paul --- Closing some of my old bug reports that aren't being acted upon. (There needs to be a resolution category "Died - Old Age") To anyone on the "cc" list - please re-open if you feel the need. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 402761] Occasional missing jpeg image thumbnails
https://bugs.kde.org/show_bug.cgi?id=402761 Paul changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #12 from Paul --- I've not seen this issue for a while now, I guess it was fixed at some point with one of the regular plasma updates. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 --- Comment #11 from Paul --- Any chance of movement on this? - An option to prevent image thumbnails appearing in the clipboard history. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 438507] No search results returned.
https://bugs.kde.org/show_bug.cgi?id=438507 --- Comment #3 from Paul --- (In reply to jm-ejC9o from comment #2) ... > And to fix it: > - Enable "Applications" back in KRunner's plugins > - Switch to an alternative again (doesn't matter which) > > If the relation between KRunner and the Application Menu (and its > alternative) is intended it should probably be explicit Yes, good find, (I seemed to have missed this back in June). Confirming that if "Applications" is disabled in KRunner's plugins then Search in Application Menu fails. Also found that a logout/login works as an alternative to "Switch to an alternative again (doesn't matter which)" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 Paul changed: What|Removed |Added Attachment #93093|0 |1 is obsolete|| Attachment #94614|0 |1 is obsolete|| --- Comment #13 from Paul --- Created attachment 152131 --> https://bugs.kde.org/attachment.cgi?id=152131&action=edit Screenshot showing image thumbnails in clipboard history Yes, still an issue. See attached screenshot. "Non text selection" is set to "Never save in history" I don't see an option to ignore image files Operating System: openSUSE Tumbleweed 20220914 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 Paul changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 --- Comment #15 from Paul --- Created attachment 152235 --> https://bugs.kde.org/attachment.cgi?id=152235&action=edit Clipboard settings screen-shot. paul@Orion-15:~$ cat ~/.config/klipperrc [General] IgnoreSelection=false MaxClipItems=16 paul@Orion-15:~$ Which seems mighty short, I would have expected more entries... Also attached screen-shot showing the current clipboard settings from the "General Configuration" section -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 Paul changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 --- Comment #17 from Paul --- Created attachment 152285 --> https://bugs.kde.org/attachment.cgi?id=152285&action=edit Screenshot showing jmage thumbnails in clipboard history with "IgnoreImages=true" OK, added "IgnoreImages=true" to klipperrc No difference, image thumbs still shown in Clipboard History (Screenshot attached) Logged out/in of KDE - no change in behaviour. Created a new test user, upon first login klipperrc not present. Configure Clipboard (as setup for my normal users) and the following klipperrc was created: [General] IgnoreSelection=false KeepClipboardContents=false MaxClipItems=16 SelectionTextOnly=false SyncClipboards=true Version=5.25.5 Added "IgnoreImages=true" - still no change in behaviour. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 Paul changed: What|Removed |Added CC|pip@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348932] "Ignore Images" does not...
https://bugs.kde.org/show_bug.cgi?id=348932 --- Comment #18 from Paul --- Created attachment 152309 --> https://bugs.kde.org/attachment.cgi?id=152309&action=edit Cluttered clipboard as result of file copy operations. Taking this one stage further, and I don't think it digresses to far. IMHO, it would be sensible for Clipboard to have an option such as "Allow only Text in History". At the moment all file copy operations are added to the history. I don't see any great advantage, or use, for that, it simply clutters up the history; file copy in almost all cases is a "one off" operation, one would not need to go to the clipboard history to re-select them. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 458332] Gwenview doesn't stop at last image
https://bugs.kde.org/show_bug.cgi?id=458332 Paul changed: What|Removed |Added CC||pip@gmx.com --- Comment #1 from Paul --- I'm also finding this new behaviour rather irritating. There is the option in (Gwenview's) settings for "Notify after reaching the last image" if that is enabled then the former behaviour is *almost* restored, albeit it then needs confirmation the user wishes to stay on the last image. Would it be possible to introduce another setting along the lines of "Stop at last image", which when set would stop at the last image irrespective of the setting of "Notify after reaching the last image", so one could have no notification and just stop at last image. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 465548] digiKam crashes with illegal instruction on AMD Athlon II due to SSE detection with CMake
https://bugs.kde.org/show_bug.cgi?id=465548 Paul changed: What|Removed |Added CC||pip@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] New: digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 Bug ID: 468726 Summary: digikam 8.0.0 unable to set default spell check language / kde default ignored. Classification: Applications Product: digikam Version: 8.0.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Setup-Misc Assignee: digikam-bugs-n...@kde.org Reporter: pip@gmx.com Target Milestone: --- SUMMARY The new spell checking feature of digikam 8 doesn't follow kde's spell checking settings, nor does it appear to be possible to set a default spell check language within digikam. STEPS TO REPRODUCE 1. Set KDE System Settings -> Regional Settings -> Spell Check to "Default Language - British English" and "British English" as the preferred language. (Screenshot 01) 2. Enable Spell Checking in digikam. (Screenshot 02) 3. OBSERVED RESULT digikam uses both en_US and en_GB - For example: the words "color" (US) and "colour" (GB) are both shown as correct spellings. There is no (apparent) option in digikam's Spell Checking setup to select a default or preferred language. EXPECTED RESULT To follow the KDE default setting, or the ability to define the Spell Check language, as for example "kate" does. (Screenshot 03) SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.60-default (64-bit) Graphics Platform: X11 Processors: 6 × AMD FX(tm)-6300 Six-Core Processor Memory: 7.7 GiB of RAM Graphics Processor: NV106 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #1 from Paul --- Created attachment 158239 --> https://bugs.kde.org/attachment.cgi?id=158239&action=edit Screenshot 01 - KDE System Settings - Spell Check -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #2 from Paul --- Created attachment 158240 --> https://bugs.kde.org/attachment.cgi?id=158240&action=edit Screenshot 02 - digikam Spell Check Settings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #3 from Paul --- Created attachment 158241 --> https://bugs.kde.org/attachment.cgi?id=158241&action=edit Screenshot 03 - kate Spell Check Settings (for comparison) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #6 from Paul --- (In reply to caulier.gilles from comment #4) > > ... Spellcheck is able to > auto-detect the current language used in text and will propose alternative > with miss-spelled words." > > In other word, the text is parsed and language auto-detected. If relevant > dictionary is installed, spellcheck will be processed. > So how does it differentiate between en_US and en_GB? (or for that matter any other variant of English) Unfortunately the en_US dictionary is a hard dependency "YaST2 conflicts list ... the installed hunspell-1.6.2-15.3.11.1.x86_64 requires 'myspell-en_US'..." so I can't simply remove it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #7 from Paul --- (In reply to Paul from comment #6) > > Unfortunately the en_US dictionary is a hard dependency "YaST2 conflicts > list ... the installed hunspell-1.6.2-15.3.11.1.x86_64 requires > 'myspell-en_US'..." so I can't simply remove it. Uninstalled 'myspell-en_US' (which 'breaks' hunspell) and I now have only the en_GB dictionary being used by digikam (Screenshot 04). Auto detection of language for spell checking may work well in most cases that don't involve a variant of a language, but for languages that have spelling variants, such as British English and American English, there needs to be (IMHO) an option to disable auto detection and to explicitly set the dictionary used. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #8 from Paul --- Created attachment 158265 --> https://bugs.kde.org/attachment.cgi?id=158265&action=edit Screenshot 04 - digikam Spell Check Settings with myspell-en_US removed -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #10 from Paul --- I'm sorry, I clearly don't understand this :( All of my text is in British English, I have no need for any other variant of English, or for any other language. By default hunspell installs, and has a dependency upon en_US (American English). I manually installed en_GB (British English), other applications that use hunspell enable selecting en_GB. What do I need to do, short of removing en_US as outlined in comment #7, to enable digikam to use en_GB and only en_GB for spell checking? I apologise once more, but as I said, I clearly don't understand this... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #12 from Paul --- Created attachment 158273 --> https://bugs.kde.org/attachment.cgi?id=158273&action=edit digikam-combo-list (In reply to caulier.gilles from comment #11) > Each alternative langage strings in digiKam have a property to set the > language to use for the corresponding string. set en_GB and that all the > spell-checking will parse your string with this language, if and only if the > relevant dictionary is installed. > You mean I have to select en_GB from the drop down box... ? Each and every time I make a text entry... ?? Why doesn't "x-default" default to en_GB (This machine locale settings: paul@HP255G7:~> locale LANG=en_GB.utf8 LC_CTYPE="en_GB.utf8" LC_NUMERIC="en_GB.utf8" LC_TIME="en_GB.utf8" LC_COLLATE="en_GB.utf8" LC_MONETARY="en_GB.utf8" LC_MESSAGES="en_GB.utf8" LC_PAPER="en_GB.utf8" LC_NAME="en_GB.utf8" LC_ADDRESS="en_GB.utf8" LC_TELEPHONE="en_GB.utf8" LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION="en_GB.utf8" LC_ALL= paul@HP255G7:~> ) I think I'll give up on this, sorry to have taken your time... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468726] digikam 8.0.0 unable to set default spell check language / kde default ignored.
https://bugs.kde.org/show_bug.cgi?id=468726 --- Comment #14 from Paul --- (In reply to caulier.gilles from comment #13) > > With "x-default", in all case, digiKam will auto-detect the language used > inside and process the spell checking with the right dictionary. > Yes, but here's the problem... digiKam doesn't differentiate between text written as British English (en_GB) or American English (en_US) and if both dictionaries are installed the spell checking is not always correct, as shown in my first post with the example of the words "color" (US) and "colour" (GB) which are both shown as correct spellings. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 471043] New: Dolphin (flathub install) crashes on launch due to no thumbnail directory
https://bugs.kde.org/show_bug.cgi?id=471043 Bug ID: 471043 Summary: Dolphin (flathub install) crashes on launch due to no thumbnail directory Classification: Applications Product: dolphin Version: 23.04.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: p...@roe.me CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Installed Dolphin from flathub. Tried to launch, it would appear for a few seconds then crash. Running from a terminal showed the following [user@pc ~]$ flatpak run org.kde.dolphin kf.kio.widgets: Cannot read information about filesystem under path "/home/user/.var/app/org.kde.dolphin/cache/thumbnails/" kf.solid.frontend.devicemanager: Couldn't get StorageAccess for ""/home/user/.var/app/org.kde.dolphin/cache/thumbnails/"" - File doesn't exist Manually creating the thumbnails directory solved the issue (would have thought the installation or first run would create this). Note I am running Sway window manager and have only DigiKam and Dolphin installed from KDE currently via flatpak. STEPS TO REPRODUCE 1. install Dolphin from flathub 2. launch dolphin (from rofi) 3. wait a few seconds OBSERVED RESULT Dolphin crashed EXPECTED RESULT Not crashing SOFTWARE/OS VERSIONS Fedora Sericea (up to date as of 20230614) KDE Application Platform: Branch 5.15-22.08 (updated 20230614 from flathub stable) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459670] Cursor theme changes to Adwaita when interacting with GTK applications
https://bugs.kde.org/show_bug.cgi?id=459670 Paul changed: What|Removed |Added CC||pip@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459670] Cursor theme changes to Adwaita when interacting with GTK applications
https://bugs.kde.org/show_bug.cgi?id=459670 --- Comment #1 from Paul --- (In reply to Sandro from comment #0) > ... Setting the cursor theme from the > system settings fixes the issue for the active session, but the issue > reappears when restarting. ... Unfortunately that doesn't seem to be the case here, changing the cursor theme (System Settings -> Appearance -> Cursors) from "Oxygen_White" to "Breeze" or back from "Breeze" to "Oxygen_White" doesn't result in any change to the errant behaviour of the cursor theme in GTK applications. Does anyone have a workable temporary fix for this until the issue is resolved? As Firefox and Thunderbird are both popular GTK applications this bug is rather visibly too obvious and detracts from the professional appearance of KDE. Operating System: openSUSE Tumbleweed 20221012 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 459670] Cursor theme changes to Adwaita when interacting with GTK applications
https://bugs.kde.org/show_bug.cgi?id=459670 --- Comment #3 from Paul --- (In reply to jamesxmcintosh from comment #2) > (In reply to Paul from comment #1) > > Try editing/creating: /usr/share/icons/default/index.theme > > Add this: > [Icon Theme] > Inherits=Oxygen_White There was no "default" sub-directory below "/usr/share/icons/", creating that sub-directory together with "index.theme" containing the section you indicated, does indeed "fix" the problem. I, (and my users) are most grateful to you :) Could there possibly be unintended consequences to adding that? (At the moment I don't see any). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460775] New: "TLS initialization failed" error whenever the app tries to download files.
https://bugs.kde.org/show_bug.cgi?id=460775 Bug ID: 460775 Summary: "TLS initialization failed" error whenever the app tries to download files. Classification: Applications Product: digikam Version: 7.8.0 Platform: unspecified OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: pnse...@gmail.com Target Milestone: --- Created attachment 153062 --> https://bugs.kde.org/attachment.cgi?id=153062&action=edit Screen shot SGetting "TLS initialization failed" error whenever the app tries to download files. Any operation (e.g. check for updates, download files for facial recognition) results in the above error. STEPS TO REPRODUCE 1. Start digikam.exe 2. Because it never has downloaded some accessory files, it asks to do so on startup 3. The download fails because of above error OBSERVED RESULT Internet downloads do not work EXPECTED RESULT Get the files the app needs. SOFTWARE/OS VERSIONS Windows: Windows 7 Professional, SP1, fully updated macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: ?? KDE Frameworks Version: 5.96.0 Qt Version:5.15.5 (built against 5.15.5) ADDITIONAL INFORMATION Have recently installed and un-installed a couple of other Photo Management systems, each of which might have dragged their own DLLs in to the system. I am also a developer and have have Visual Studio 2008, and a couple of other versions (2005, 2017) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460775] "TLS initialization failed" error whenever the app tries to download files.
https://bugs.kde.org/show_bug.cgi?id=460775 --- Comment #4 from Paul --- Thank you for looking into this. On my machine, Win7 SP1, I enabled TLS 1.0, 1.1, and 1.2 (also SSL 2.0 and 3.0) which were already installed and that did not change the result, FWIW. Paul -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464827] New: white/light gray screen on monitor wakeup in Wayland, all the time on X11
https://bugs.kde.org/show_bug.cgi?id=464827 Bug ID: 464827 Summary: white/light gray screen on monitor wakeup in Wayland, all the time on X11 Classification: Plasma Product: kwin Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: holle...@cs.dal.ca Target Milestone: --- Created attachment 155642 --> https://bugs.kde.org/attachment.cgi?id=155642&action=edit org.kde.KWin.supportInformation SUMMARY Under wayland, login works fine but when the monitor goes to sleep it wakes up to a blank screen. Under X11, login immediately produces the blank screen. Both kwin and plasmashell say up and running. STEPS TO REPRODUCE 1. Let system idle until monitor falls asleep 2. Move mouse 3. OBSERVED RESULT Blank white/light gray screen with cursor still responsive. As in cursor moves and changes form based on what hidden window is underneath. EXPECTED RESULT Desktop and windows visible. SOFTWARE/OS VERSIONS Linux 6.1.7 KDE Plasma 5.26.5 KDE Frameworks 5.102 Qt 5.15.8+kde+r174 mesa 22.3.3 attached output of qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation ADDITIONAL INFORMATION This is a new system using AMD integrated graphics (RDNA 2) and a single monitor plugged in with HDMI. I disabled screen locking and it still occurs. I tried creating a new user with fresh config. I can switch to another virtual console. On X11 when I switch back I briefly see the desktop. This issue was also recently reported in https://forums.gentoo.org/viewtopic-p-8768658.html?sid=6f7dccffd7790600c6e13d6afcae57d2. Unfortunately that user gave up and moved to xmonad. I now have export QT_LOGGING_RULES="kwin_*.debug=true" in .bash_profile, and have looked through the journal but not sure what to look for. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464890] New: Plasma crashed when opening the Menu (OnzeMenu 11)
https://bugs.kde.org/show_bug.cgi?id=464890 Bug ID: 464890 Summary: Plasma crashed when opening the Menu (OnzeMenu 11) Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: paul.monta...@live.co.uk CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.26.5) Qt Version: 5.15.7 Frameworks Version: 5.101.0 Operating System: Linux 6.1.3-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: Launching OnzeMenu 11 caused Plasma to crash. No unusual behaviour leading up to the crash. No newly installed app either; just seems like a random crash (from a user perspective). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7f3aa7741ff8 in QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*, QObject*) () from /lib64/libQt5Qml.so.5 #5 0x7f3aa77b83e5 in ?? () from /lib64/libQt5Qml.so.5 #6 0x7f3aa77b91a8 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib64/libQt5Qml.so.5 #7 0x7f3aa7794fac in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5 #8 0x7f3aa779591f in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () from /lib64/libQt5Qml.so.5 #9 0x7f3aa77d7de4 in ?? () from /lib64/libQt5Qml.so.5 #10 0x7f3aa77dd1af in ?? () from /lib64/libQt5Qml.so.5 #11 0x7f3aa77701de in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #12 0x7f3aa78f89fd in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #13 0x7f3aa78febb4 in QQmlBinding::evaluate(bool*) () from /lib64/libQt5Qml.so.5 #14 0x7f3aa7902dd3 in ?? () from /lib64/libQt5Qml.so.5 #15 0x7f3aa7900914 in QQmlBinding::update(QFlags) () from /lib64/libQt5Qml.so.5 #16 0x7f3aa77b87fb in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*) () from /lib64/libQt5Qml.so.5 #17 0x7f3aa77b91a8 in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib64/libQt5Qml.so.5 #18 0x7f3aa7794fac in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5 #19 0x7f3aa779591f in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () from /lib64/libQt5Qml.so.5 #20 0x7f3aa77d7de4 in ?? () from /lib64/libQt5Qml.so.5 #21 0x7f3aa77dd1af in ?? () from /lib64/libQt5Qml.so.5 #22 0x7f3aa77701de in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #23 0x7f3aa78f89fd in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #24 0x7f3aa78febb4 in QQmlBinding::evaluate(bool*) () from /lib64/libQt5Qml.so.5 #25 0x7f3aa7902dd3 in ?? () from /lib64/libQt5Qml.so.5 #26 0x7f3aa7900914 in QQmlBinding::update(QFlags) () from /lib64/libQt5Qml.so.5 #27 0x7f3aa790dc62 in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #28 0x7f3aa789e05c in QQmlComponentPrivate::complete(QQmlEnginePrivate*, QQmlComponentPrivate::ConstructionState*) () from /lib64/libQt5Qml.so.5 #29 0x7f3aa78a0011 in QQmlComponentPrivate::completeCreate() () from /lib64/libQt5Qml.so.5 #30 0x7f3aa7f41e9c in ?? () from /lib64/libQt5Quick.so.5 #31 0x7f3aa7f34c06 in ?? () from /lib64/libQt5Quick.so.5 #32 0x7f3aa7f2f748 in ?? () from /lib64/libQt5Quick.so.5 #33 0x7f3aa7f45e9c in ?? () from /lib64/libQt5Quick.so.5 #34 0x7f3aa7f4a343 in QQuickItemView::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5Quick.so.5 #35 0x7f3aa7f3c345 in ?? () from /lib64/libQt5Quick.so.5 #36 0x7f3aa77be0f0 in QV4::QObjectWrapper::setProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, QV4::Value const&) () from /lib64/libQt5Qml.so.5 #37 0x7f3aa77bec1b in QV4::QObjectWrapper::setQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, QV4::Value const&) () fr
[kwin] [Bug 464827] white/light gray screen on monitor wakeup in Wayland, all the time on X11
https://bugs.kde.org/show_bug.cgi?id=464827 Paul changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Paul --- For posterity, this is a symptom of not having installed a 2D X.org driver (xf86-video-*). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464890] Plasma crashed when opening the Menu (OnzeMenu 11)
https://bugs.kde.org/show_bug.cgi?id=464890 --- Comment #2 from Paul --- (In reply to Nate Graham from comment #1) > That's not the default menu, which means it's a bug in the code for that > menu. Can you report it to the developer? I'll report this to the developer. Thanks. Please close this bug report. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Paul changed: What|Removed |Added CC||pvt.g...@gmail.com --- Comment #39 from Paul --- For kde6 use: ``` qdbus6 org.kde.kded6 /modules/plasmavault requestImportVault ``` Worked well for me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489535] New: Turning off TV and AV Receiver connected via HDMI
https://bugs.kde.org/show_bug.cgi?id=489535 Bug ID: 489535 Summary: Turning off TV and AV Receiver connected via HDMI Classification: Plasma Product: plasmashell Version: 6.1.1 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: pwar...@pwarren.id.au Target Milestone: 1.0 Application: plasmashell (6.1.1) Qt Version: 6.7.2 Frameworks Version: 6.3.0 Operating System: Linux 6.9.6-1-default x86_64 Windowing System: Wayland Distribution: openSUSE Tumbleweed DrKonqi: 6.1.1 [CoredumpBackend] -- Information about the crash: When I turn off my AV reciever and TV, sometimes when I come back I get these plasmashell crashes. But not every time :( Intel graphics -> HDMI 2.0 -> Yamaha RX-A6A -> HDMI 2.1 -> Sony X90L Have the necessary pieces in place for enabling HDR output on the Intel Iris XE integrated graphics on an Asus NUC. OpenSuse Tumbleweed The crash can be reproduced sometimes. -- Backtrace: Application: plasmashell (plasmashell), signal: Segmentation fault Downloading separate debug info for /usr/bin/plasmashell... [New LWP 12479] [New LWP 12490] [New LWP 12480] [New LWP 12492] [New LWP 12481] [New LWP 12483] [New LWP 12489] [New LWP 12482] [New LWP 12484] [New LWP 12491] Downloading separate debug info for /lib64/libKF6DBusAddons.so.6... Downloading separate debug info for /lib64/libKF6StatusNotifierItem.so.6... Downloading separate debug info for /lib64/libKF6XmlGui.so.6... Downloading separate debug info for /lib64/libLayerShellQtInterface.so.6... Downloading separate debug info for /lib64/libKWaylandClient.so.6... Downloading separate debug info for /lib64/libPlasmaQuick.so.6... Downloading separate debug info for /lib64/libkworkspace6.so.6... Downloading separate debug info for /lib64/libKF6UserFeedbackCore.so.6... Downloading separate debug info for /lib64/libxcb.so.1... Downloading separate debug info for /lib64/libKF6Crash.so.6... Downloading separate debug info for /lib64/libKF6Solid.so.6... Downloading separate debug info for /lib64/libKF6Service.so.6... Downloading separate debug info for /lib64/libPlasma.so.6... Downloading separate debug info for /lib64/libKF6GlobalAccel.so.6... Downloading separate debug info for /lib64/libKF6Package.so.6... Downloading separate debug info for /lib64/libKF6Svg.so.6... Downloading separate debug info for /lib64/libKF6CoreAddons.so.6... Downloading separate debug info for /lib64/libKF6WindowSystem.so.6... Downloading separate debug info for /lib64/libPlasmaActivities.so.6... Downloading separate debug info for /lib64/libKF6ConfigQml.so.6... Downloading separate debug info for /lib64/libKF6ConfigGui.so.6... Downloading separate debug info for /lib64/libKF6ConfigCore.so.6... Downloading separate debug info for /lib64/libKF6I18n.so.6... Downloading separate debug info for /lib64/libQt6Quick.so.6... Downloading separate debug info for /lib64/libQt6Qml.so.6... Downloading separate debug info for /lib64/libQt6Gui.so.6... Downloading separate debug info for /lib64/libQt6DBus.so.6... Downloading separate debug info for /lib64/libstdc++.so.6... Downloading separate debug info for /lib64/libc.so.6... Downloading separate debug info for /lib64/libQt6Xml.so.6... Downloading separate debug info for /lib64/libQt6Network.so.6... Downloading separate debug info for /lib64/libQt6PrintSupport.so.6... Downloading separate debug info for /lib64/libKF6ItemViews.so.6... Downloading separate debug info for /lib64/libKF6IconWidgets.so.6... Downloading separate debug info for /lib64/libKF6ConfigWidgets.so.6... Downloading separate debug info for /lib64/libKF6WidgetsAddons.so.6... Downloading separate debug info for /lib64/libKF6IconThemes.so.6... Downloading separate debug info for /lib64/libKF6ColorScheme.so.6... Downloading separate debug info for /lib64/libKF6GuiAddons.so.6... Downloading separate debug info for /lib64/libKF6KIOWidgets.so.6... Downloading separate debug info for /lib64/libKF6KCMUtilsQuick.so.6... Downloading separate debug info for /lib64/libKF6KIOCore.so.6... Downloading separate debug info for /lib64/libKF6Notifications.so.6... Downloading separate debug info for /lib64/libm.so.6... Downloading separate debug info for /lib64/libXau.so.6... Downloading separate debug info for /lib64/libxcb-randr.so.0... Downloading separate debug info for /lib64/libX11.so.6... Downloading separate debug info for /lib64/libgcc_s.so.1... Downloading separate debug info for /lib64/libudev.so.1... Downloading separate debug info for /lib64/libmount.so.1... Downloading separate debug info for /lib64/libimobiledevice-1.0.so.6... Downloading separate debug info for /lib64/libplist-2.0.so.4... Downloading separate debug info for /lib64/libKF6Archive.so.6... Downloading separate debug info for /lib64/libQt6Svg.so.6... Downloading sepa
[plasma-nm] [Bug 477907] New: plasma-nm causing screen/panel corruption.
https://bugs.kde.org/show_bug.cgi?id=477907 Bug ID: 477907 Summary: plasma-nm causing screen/panel corruption. Classification: Plasma Product: plasma-nm Version: 5.27.9 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: pip@gmx.com Target Milestone: --- SUMMARY Attempting to use the network manager results in screen and panel corruption. This is a rather elderly openSUSE Tumblweed machine. TW is normally kept up to date although the machine is only used as a "spare", I can't be precise as to when this issue first appeared. This problem can be reproduced with a new user and the screen shots attached are those from a new, default, user. STEPS TO REPRODUCE 1. Launch Network Manager 2. Select a network connection 3. OBSERVED RESULT 1. At initial launch all is OK: Screenshot 1 2. Network Manager and the Plasma Panel now become corrupt: Screenshot 2 EXPECTED RESULT Normal operation... SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231129 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.6.2-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ Memory: 3.8 GiB of RAM Graphics Processor: NV84 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: GA-MA770-DS3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 477907] plasma-nm causing screen/panel corruption.
https://bugs.kde.org/show_bug.cgi?id=477907 --- Comment #1 from Paul --- Created attachment 163755 --> https://bugs.kde.org/attachment.cgi?id=163755&action=edit Screen Shot 1 - Initial state -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 477907] plasma-nm causing screen/panel corruption.
https://bugs.kde.org/show_bug.cgi?id=477907 --- Comment #2 from Paul --- Created attachment 163756 --> https://bugs.kde.org/attachment.cgi?id=163756&action=edit Screen Shot 2 - Corrupted state -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478708] New: Filename not displayed when sending file
https://bugs.kde.org/show_bug.cgi?id=478708 Bug ID: 478708 Summary: Filename not displayed when sending file Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Other Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: tech4...@tuta.io CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY *** When sending a file from one device with KDE Connect to another, the receiving device displays the filename, whereas the sending device doesn't, but it should. *** STEPS TO REPRODUCE 1. Send a file from one Android device running KDE connect to another 2. Pull down the notification shade on both 3. Compare the two OBSERVED RESULT Only the receiving device displays the filename EXPECTED RESULT Both should display the filename SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: N/A (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 477907] plasma-nm causing screen/panel corruption.
https://bugs.kde.org/show_bug.cgi?id=477907 --- Comment #3 from Paul --- I guess I must be the only one seeing this issue :( Network Manager is the only Plasma Applet that triggers this screen/video corruption, I don't see the issue with, for example, Digital Clock / Calendar, Disks & Devices, Printers, Notifications, etc... I appreciate I'm running Plasma on very elderly HW, but, I would like to resolve this issue if possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462154] Plasma crashed after integrating and running Appimage (Rambox v2.0.8)
https://bugs.kde.org/show_bug.cgi?id=462154 Paul changed: What|Removed |Added CC||paulmontaq...@gmail.com --- Comment #3 from Paul --- (In reply to Akseli Lahtinen from comment #2) > Has this still occured on Plasma 6? Not seen a recurrence of this in Plasma 6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488158] New: Disks & Devices (device notifier) showing non-removable devices when set to display only removable.
https://bugs.kde.org/show_bug.cgi?id=488158 Bug ID: 488158 Summary: Disks & Devices (device notifier) showing non-removable devices when set to display only removable. Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: pip@gmx.com Target Milestone: 1.0 Created attachment 170225 --> https://bugs.kde.org/attachment.cgi?id=170225&action=edit Screen-shot showing issue. SUMMARY Disks & Devices showing non-removable devices when set to display only removable. STEPS TO REPRODUCE 1. Set Disks & Devices to show removable devices only. 2. Insert removable device. 3. Open Disks & Devices OBSERVED RESULT All non-removable devices are shown as well as the inserted removable device. See attached screen-shot. EXPECTED RESULT Only the removable device is shown SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240605 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488158] Disks & Devices (device notifier) showing non-removable devices when set to display only removable.
https://bugs.kde.org/show_bug.cgi?id=488158 Paul changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Paul --- (In reply to Nate Graham from comment #1) > I can't reproduce this issue on my system. Some questions for you: > 1. How exactly are those devices physically connected? SATA > 2. Does the issue reproduce on Wayland? Unfortunately Wayland doesn't play nicely on this system - black screen + cursor > 3. Does the issue reproduce in a new clean user account? Yes > 4. Did this work in the past and break with the update to Plasma 6, or > 6.0.5, or some other specific version? Working fine prior to the Tumbleweed update 20240523 -> 20240605 (20240524 and 20240531 skipped, so unable to be exact on which update may have caused this.) Updates included that may be relevant: plasma6-* 6.0.4 -> 6.0.5 kde gear 24.04.8 -> 24.05.0 kernel 6.9.1 -> 6.9.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488158] Disks & Devices (device notifier) showing non-removable devices when set to display only removable.
https://bugs.kde.org/show_bug.cgi?id=488158 --- Comment #3 from Paul --- I think we can discount the kernel, after booting to the previous 6.9.1 version the issue still exists. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488158] Disks & Devices (device notifier) showing non-removable devices when set to display only removable.
https://bugs.kde.org/show_bug.cgi?id=488158 --- Comment #5 from Paul --- This is a dual-boot setup with the choice of boot made by bios, not grub. Physically there are 2 ssd drives: sda and sdb, and 1 hdd: sdc (all connected by SATA directly to the motherboard). paul@Orion-15:~$ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:01 55.9G 0 disk ├─sda1 8:1148G 0 part / └─sda2 8:21 4G 0 part [SWAP] sdb 8:16 1 119.2G 0 disk └─sdb1 8:17 1 112G 0 part /home sdc 8:32 1 232.9G 0 disk ├─sdc1 8:33 132G 0 part ├─sdc2 8:34 1 192G 0 part └─sdc3 8:35 1 8.9G 0 part sr0 11:01 1024M 0 rom paul@Orion-15:~$ This is fstab used when booting from the ssd drives: UUID=2511d4d8-0425-4e80-bd14-86798396bdfb /ext4 noatime,acl,user_xattr 1 1 UUID=08a4ff75-8318-40cf-b78b-b7049064dfb5 swap swap defaults 0 0 UUID=801838af-06ff-405e-a6c3-194ba5878291 /homeext4 relatime,acl,user_xattr 1 2 This is fstab used when booting from the hdd drive: UUID=ea5c2b1b-ac33-497d-b286-2c06a23623a2 /ext4 noatime,acl,user_xattr 1 1 UUID=8595c8af-adce-47f8-b9e4-9f46348154ac swap swap defaults0 0 UUID=20d5bdae-6c44-4c27-be89-9c9e91e9233f /homeext4 relatime,acl,user_xattr 1 2 The system is not new and has worked fine with this setup for several years. As I wrote in comment #2, the issue first arose following the Tumbleweed update 20240523 -> 20240605 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488158] Disks & Devices (device notifier) showing non-removable devices when set to display only removable.
https://bugs.kde.org/show_bug.cgi?id=488158 --- Comment #6 from Paul --- Follow up... I noticed on the above lsblk output the removable flag (RM) is shown as "1" and also: paul@Orion-15:~> cat /sys/class/block/sda/removable 1 paul@Orion-15:~> cat /sys/class/block/sdb/removable 1 paul@Orion-15:~> cat /sys/class/block/sdc/removable 1 paul@Orion-15:~> is showing these devices as "removable" However, there have been *no* changes made to the hardware or bios configuration of this machine. If I now boot this machine using a Leap 15.5 live USB and then issue the lsblk command the 3 non removable drives (sda, sdb, and sdc) are shown with the correct removable flag, ie "0", non-removable. linux@localhost:~> sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop07:00 814.1M 1 loop /run/overlay/squashfs_container loop17:10 4.8G 1 loop /run/overlay/rootfsbase sda 8:00 55.9G 0 disk ├─sda1 8:1048G 0 part └─sda2 8:20 4G 0 part sdb 8:16 0 119.2G 0 disk └─sdb1 8:17 0 112G 0 part sdc 8:32 0 232.9G 0 disk ├─sdc1 8:33 032G 0 part ├─sdc2 8:34 0 192G 0 part └─sdc3 8:35 0 8.9G 0 part sdd 8:48 1 57.7G 0 disk ├─sdd1 8:49 1 927.5M 0 part /run/overlay/live ├─sdd2 8:50 120M 0 part └─sdd3 8:51 1 56.8G 0 part /run/overlay/overlayfs sr0 11:01 1024M 0 rom linux@localhost:~> So it would seem the "bug" lies not with "Disks & Devices" - question now is, where or what? :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488158] Disks & Devices (device notifier) showing non-removable devices when set to display only removable.
https://bugs.kde.org/show_bug.cgi?id=488158 --- Comment #8 from Paul --- OK - Thanks. - I don't believe this to be a KDE issue. I'll raise an openSUSE bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487832] non-removable storage devices get recognized as removable media
https://bugs.kde.org/show_bug.cgi?id=487832 Paul changed: What|Removed |Added CC||pip@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487832] non-removable storage devices get recognized as removable media
https://bugs.kde.org/show_bug.cgi?id=487832 --- Comment #5 from Paul --- (In reply to g1.jasger from comment #4) > OK- thanks, I'll raise an issue on arch then. This was a regression introduced with the 6.9.* kernel. It has been fixed in 6.10-rc4 "Fix a bug where the SCSI Removable Media Bit (RMB) was incorrectly set for hot-plug capable (and eSATA) ports." https://lore.kernel.org/all/171856227442.1143.13572753599648338171.pr-tracker-...@kernel.org/T/ On openSUSE TW this fix has been backported to the 6.9 kernel and should be in 6.9.6 @g1.jasger you may want to point the arch folk to that commit. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 481860] New: Dolphin crashes and RAM usage balloons by +15-20%
https://bugs.kde.org/show_bug.cgi?id=481860 Bug ID: 481860 Summary: Dolphin crashes and RAM usage balloons by +15-20% Classification: Applications Product: dolphin Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: paul.monta...@live.co.uk CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.5-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: I launch Dolphin and navigate to the folders and locate files. Operation is fine during this launch. However, if I leave it alone for 30-60 mins I notice that the RAM usage has jumped from 26% to 40.1% (in my current example). I have mapped an NFS share so that I can access files on my separate NAS, and there appears not to be an issue navigating that share. It is only when Dolphin is left alone without any user interaction that it seems to gobble RAM, before then crashing! The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f439b388ddd in __memmove_ssse3 () from /lib64/libc.so.6 #5 0x7f43958ecc6a in memmove (__len=262112, __src=0x7f3e8d7bf810, __dest=) at /usr/include/bits/string_fortified.h:36 #6 copy_unswapped (rect=..., img=..., dstBytesPerLine=262112, dst=) at qxcbbackingstore.cpp:547 #7 native_sub_image (swap=false, rect=..., src=..., dstStride=262112, buffer=) at qxcbbackingstore.cpp:590 #8 QXcbBackingStoreImage::flushPixmap (this=0x5652ccd060e0, region=..., fullRegion=) at qxcbbackingstore.cpp:669 #9 0x7f43958ed269 in QXcbBackingStoreImage::flushPixmap (fullRegion=false, region=..., this=0x5652ccd060e0) at qxcbbackingstore.cpp:627 #10 QXcbBackingStoreImage::put (this=0x5652ccd060e0, dst=55574540, region=..., offset=...) at qxcbbackingstore.cpp:741 #11 0x7f43958edb99 in QXcbBackingStore::flush (this=0x5652cc92ad80, window=, region=..., offset=...) at qxcbbackingstore.cpp:877 #12 0x7f439c35a6a4 in QBackingStore::flush (this=this@entry=0x7f43880036f0, region=..., window=0x5652cc866ff0, offset=...) at painting/qbackingstore.cpp:263 #13 0x7f439c9b294f in QWidgetRepaintManager::flush (this=this@entry=0x5652cc928ef0, widget=0x5652cc6b67e0, region=..., widgetTextures=) at kernel/qwidgetrepaintmanager.cpp:1198 #14 0x7f439c9b44c9 in QWidgetRepaintManager::flush (this=0x5652cc928ef0) at kernel/qwidgetrepaintmanager.cpp:1096 #15 0x7f439c9b6528 in QWidgetRepaintManager::paintAndFlush (this=0x5652cc928ef0) at kernel/qwidgetrepaintmanager.cpp:1028 #16 0x7f439c9ff061 in QWidgetWindow::handleResizeEvent (this=this@entry=0x5652cc866ff0, event=event@entry=0x7fff2a27e380) at kernel/qwidgetwindow.cpp:842 #17 0x7f439ca02f12 in QWidgetWindow::event (this=0x5652cc866ff0, event=0x7fff2a27e380) at kernel/qwidgetwindow.cpp:322 #18 0x7f439c9a51ae in QApplicationPrivate::notify_helper (this=, receiver=0x5652cc866ff0, e=0x7fff2a27e380) at kernel/qapplication.cpp:3640 #19 0x7f439bced938 in QCoreApplication::notifyInternal2 (receiver=0x5652cc866ff0, event=0x7fff2a27e380) at kernel/qcoreapplication.cpp:1064 #20 0x7f439bcedb0e in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1474 #21 0x7f439c17965c in QGuiApplicationPrivate::processGeometryChangeEvent (e=) at kernel/qguiapplication.cpp:2610 #22 0x7f439c1503cc in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #23 0x7f43958f851a in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105 #24 0x7f439970ef30 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7f4399710b58 in ?? () from /lib64/libglib-2.0.so.0 #26 0x7f439971120c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7f439bd46876 in QEventDispatcherGlib::processEvents (this=0x5652cc3eb1f0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f439bcec3cb in QEventLoop::exec (this=this@entry=0x7fff2a27e600, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f439bcf4860 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x7f439c17061c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870 #31 0x7f439c9a5125 in QApplication::exec () at kernel/qapplication.cpp:2832 #32 0x5652cb7c15a7 in main (argc=, argv=) at /usr/src/debug/dolphin-23.08.4/src/main.cpp:238 [Inferior 1 (process 6503) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 458883] Copy/Paste of a rectangular selection between two different files, looses selection contents
https://bugs.kde.org/show_bug.cgi?id=458883 Paul changed: What|Removed |Added CC||paul...@protonmail.ch -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457847] kwin becomes unresponsive, need to restart session
https://bugs.kde.org/show_bug.cgi?id=457847 Paul changed: What|Removed |Added CC|paulhollen...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486390] New: Frequent crashes in plasma-discover with libglib-2.0 errors
https://bugs.kde.org/show_bug.cgi?id=486390 Bug ID: 486390 Summary: Frequent crashes in plasma-discover with libglib-2.0 errors Classification: Applications Product: Discover Version: 5.24.7 Platform: Ubuntu OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: p...@schumacher.or.at CC: aleix...@kde.org Target Milestone: --- Description: I am experiencing frequent crashes with the application plasma-discover on Ubuntu 22.04.4 LTS. These crashes occur when I attempt to access the update functions within the Discover UI. Terminal outputs and system logs indicate issues with libglib-2.0, showing repeated trap int3 errors, which are typically used for debug breakpoints in development builds. Expected Behavior: Plasma Discover should run smoothly, allowing the management of software updates and installations without crashing. Actual Behavior: Discover crashes frequently, especially when trying to access the updates section or other specific parts of the application. Steps Attempted: Resetting configuration files for Discover. Running Discover from the terminal to capture any error outputs. System update and reinstallation of plasma-discover and its dependencies. Analyzing system logs with journalctl, which showed repeated issues with libglib-2.0. System and Package Information: Ubuntu Version: 22.04.4 LTS Package Versions: libglib2.0-0: Installed: 2.72.4-0ubuntu2.2 plasma-discover: Installed: 5.24.7-0ubuntu0.1 This issue significantly impacts the functionality of the Discover application, hindering routine software management and updates. Any assistance or resolution would be greatly appreciated. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486390] Frequent crashes in plasma-discover with libglib-2.0 errors
https://bugs.kde.org/show_bug.cgi?id=486390 --- Comment #1 from p...@schumacher.or.at --- Created attachment 169071 --> https://bugs.kde.org/attachment.cgi?id=169071&action=edit Error Report -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461619] When using a chromium based application/browser typing is very laggy on Wayland.
https://bugs.kde.org/show_bug.cgi?id=461619 Paul changed: What|Removed |Added CC||m...@paul.rs -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484308] New: Removing last (1 of 1 entries) from the Clipboard results in spurious "Remove from history" overlaying the panel.
https://bugs.kde.org/show_bug.cgi?id=484308 Bug ID: 484308 Summary: Removing last (1 of 1 entries) from the Clipboard results in spurious "Remove from history" overlaying the panel. Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: pip@gmx.com Target Milestone: 1.0 SUMMARY Removing last (1 of 1 entries) from the Clipboard results in spurious "Remove from history" overlaying the panel. STEPS TO REPRODUCE 1. Ensure Clipboard only contains one entry. 2. Use "Trash Can" button to "Remove from history" (Screenshot-1) 3. OBSERVED RESULT Entry is removed, Clipboard closes, leaving a spurious "Remove from history" overlaying the panel. (Screenshot-2) EXPECTED RESULT Entry is removed, Clipboard closes. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.14.21-150500.55.52-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484308] Removing last (1 of 1 entries) from the Clipboard results in spurious "Remove from history" overlaying the panel.
https://bugs.kde.org/show_bug.cgi?id=484308 --- Comment #1 from Paul --- Created attachment 167643 --> https://bugs.kde.org/attachment.cgi?id=167643&action=edit Screenshot-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484308] Removing last (1 of 1 entries) from the Clipboard results in spurious "Remove from history" overlaying the panel.
https://bugs.kde.org/show_bug.cgi?id=484308 --- Comment #2 from Paul --- Created attachment 167644 --> https://bugs.kde.org/attachment.cgi?id=167644&action=edit Screenshot-2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484308] Removing last (1 of 1 entries) from the Clipboard results in spurious "Remove from history" overlaying the panel.
https://bugs.kde.org/show_bug.cgi?id=484308 --- Comment #3 from Paul --- I'm also seeing this on a second system (openSUSE TW + Plasma 6): Operating System: openSUSE Tumbleweed 20240320 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Graphics Processor: NV138 But *not* on a third system (also openSUSE TW + Plasma 6): Operating System: openSUSE Tumbleweed 20240320 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-1-default (64-bit) Graphics Platform: X11 Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2 The obvious difference is the first two systems that exhibit this issue both use the nouveau open source drive, the third system uses the nvidia proprietary driver (550.67). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480397] New: Issues with pop up palete
https://bugs.kde.org/show_bug.cgi?id=480397 Bug ID: 480397 Summary: Issues with pop up palete Classification: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: pslang...@gmail.com Target Milestone: --- SUMMARY *** The pop-up palette will not appear on multiple presses of the right mouse button using an XP-Pen AC19 Shortcut Remote Express Keys Keyboard for Drawing Display and Drawing Tablet and the stylus for a Huion GT-220 V2 Silver Graphics Drawing Tablet Monitor (average 1 out of 30 presses) *** STEPS TO REPRODUCE 1. In krita press the right button on the stylus to bring up the pop-up palette 2. in Krita press the shortcut key assigned to the right mouse button on the XP-PEN AC19 shortcut remote 3. OBSERVED RESULT Both steps 1 and 2 have completely erratic results, as the palette will not appear on multiple presses, then it may appear a few seconds later EXPECTED RESULT The pop-up palette appears when the right button or equivalent shortcut button is pressed SOFTWARE/OS VERSIONS Windows: Windows 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I've opened Krita on my standard monitor and both the XP-PEN shortcut remote and the Huion stylus work as expected whilst using the monitor with Krita. When I move over to the Huion tablet, both buttons are unresponsive. no other programs are running in Windows whilst this is happening. The problem has only appeared since the new 5.2.2 update as it was working with the previous version without issue. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487263] New: Cursor is hidden while hovering over maps in Kstars
https://bugs.kde.org/show_bug.cgi?id=487263 Bug ID: 487263 Summary: Cursor is hidden while hovering over maps in Kstars Classification: Applications Product: kstars Version: 3.7.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: phome...@bigpond.net.au Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY The cursor / pointer is visible while hovering over the menues but disappears when placed over the mapping area. STEPS TO REPRODUCE 1. Hover over star map in Kstars 2. 3. OBSERVED RESULT Cursor is invisible EXPECTED RESULT Cursor remains visible. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Raspberry Pi Bookworm (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is a build from today's source. Stellarsolver/INDI/Kstars and PHD2. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 446179] New: FITS viewer is not working
https://bugs.kde.org/show_bug.cgi?id=446179 Bug ID: 446179 Summary: FITS viewer is not working Product: kstars Version: 3.5.6 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: phome...@bigpond.net.au Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Select the FITS viewer icon or do a preview from camera module 2. 3. OBSERVED RESULT The viewer does not appear EXPECTED RESULT The viewer should appear and either display image or allow you to load an image for display SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Raspbian OS (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Stopped working after a new build -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 446179] FITS viewer is not working
https://bugs.kde.org/show_bug.cgi?id=446179 --- Comment #2 from Paul --- Jasem, No, but it makes no difference if I check it. I have rebooted and no difference. It was working fine until I did a git pull and make. Paul > On 28 Nov 2021, at 7:37:34 pm, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=446179 > > --- Comment #1 from Jasem Mutlaq --- > Settings --> Configure KStars --> FITS --> FITS Viewer > > is it checked? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 446179] FITS viewer is not working
https://bugs.kde.org/show_bug.cgi?id=446179 --- Comment #3 from Paul --- Jasem, I have found that I can open an image from file - Open. I have also found that checking the field you suggested will now open an image when doing preview. The view FITS icon works when the window is open and has an image but does nothing otherwise. I haven’t changed the setting, so maybe someone has “fixed” something. Paul > On 28 Nov 2021, at 7:37:34 pm, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=446179 > > --- Comment #1 from Jasem Mutlaq --- > Settings --> Configure KStars --> FITS --> FITS Viewer > > is it checked? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] New: KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 Bug ID: 453254 Summary: KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved. Product: kmymoney Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: zy.wp...@sunrise.ch Target Milestone: --- Created attachment 148487 --> https://bugs.kde.org/attachment.cgi?id=148487&action=edit active processes and remaining files SUMMARY *** KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved. *** STEPS TO REPRODUCE 1. open/mount an encrypted volume/drive with VERACRYPT 2. open a *.kmy-file stored in the encrypted volume with KMyMoney 3. do some changes in *.kmy-file 4. save *.kmy-file 5. exit KMyMoney with a click on "X" 6. wait a couple of minutes 7. dismount volume in VERACRYPT OBSERVED RESULT volume can not be dismounted "because files are in use by another program"; unless a "forced dismount" is done EXPECTED RESULT - volume should be dismounted SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Following processes of KMyMoney are still active after closing KMyMoney: -kioslave5.exe -klauncher5.exe It seems to me, that one or both of these process block the *.kmy-file and prevent dismounting of the VERACRYT-volume. After forced dismounting, a *.kmy.n~ remains in the encrypted volume (see attachment) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 Paul changed: What|Removed |Added CC||zy.wp...@sunrise.ch -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #4 from Paul --- Created attachment 148523 --> https://bugs.kde.org/attachment.cgi?id=148523&action=edit kmymoney-avast-version.JPG --- Comment #5 from Paul --- Created attachment 148524 --> https://bugs.kde.org/attachment.cgi?id=148524&action=edit kmymoney-virus-warning_1.JPG --- Comment #6 from Paul --- Created attachment 148525 --> https://bugs.kde.org/attachment.cgi?id=148525&action=edit kmymoney-virus-warning_2.JPG -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #3 from Paul --- Hi Ralf and Stephen Thanks a lot for you prompt reply. I downloaded and installed a new version from your link (see attachment). However my antivirus AVAST blocks execution of this version completely (even when adding exceptions). I had to uninstall it and reinstalled version 5.0.6. So I was unable to check if it would work with the newer version, sorry. Following the links on KMyMoney-homepage one gets the version 5.0.6 * _https://kmymoney.org/_ * _https://kmymoney.org/download.html_ * An installation package for an older stable release can be found on our _download server <https://download.kde.org/stable/kmymoney/5.0.6/>_. => _https://download.kde.org/stable/kmymoney/5.0.6/_ Thanks anyway for you help. Kind regards Paul -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #7 from Paul --- Hi again After sending the email below, I opened my *.kmy-file with the reinstalled version 5.0.6., made some changes, saved changes and closed KMyMoney. Then I waited approx. 5 seconds and dismounted the encrypted drive and astonishly I worked without any problem and did not ask me whether I want to do a "forced dismounting". No idea why! Kind regards Paul Am 03.05.2022 um 08:37 schrieb P. Furrer: > Hi Ralf and Stephen > > Thanks a lot for you prompt reply. > > I downloaded and installed a new version from your link (see attachment). > > However my antivirus AVAST blocks execution of this version completely > (even when adding exceptions). I had to uninstall it and reinstalled > version 5.0.6. > > So I was unable to check if it would work with the newer version, sorry. > > Following the links on KMyMoney-homepage one gets the version 5.0.6 > > * _https://kmymoney.org/_ > * _https://kmymoney.org/download.html_ > * An installation package for an older stable release can be found > on our _download server > <https://download.kde.org/stable/kmymoney/5.0.6/>_. => > _https://download.kde.org/stable/kmymoney/5.0.6/_ > > Thanks anyway for you help. > > Kind regards > Paul -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #10 from Paul --- Hi Ralf Thanks a lot for your help. Sorry, but I can't follow.. No idea what "variant" means. Which link should I use for downloading the version for Win 10 64-bit? Anyway, for whatever reason, it now works fine for me with version 5.0.6. Do I have to close the "bug-report" or do you do that? Have a good day and kind regards Paul Weitergeleitete Nachricht Betreff:[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved. Datum: Tue, 03 May 2022 09:37:01 + Von:Ralf Habacker Antwort an: An: zy.wp...@sunrise.ch https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #8 from Ralf Habacker --- (In reply to Paul from comment #7) > > I downloaded and installed a new version from your link (see > attachment). you are using the 64bit variant > > However my antivirus AVAST blocks execution of this version > completely > (even when adding exceptions). I had to uninstall it and > reinstalled > version 5.0.6. I checked the mentioned file dbus-daemon.exe from the 64bit installation at virustotal https://www.virustotal.com/gui/file/ce3e0f4e7b769d10740e17830b741a9afbbee0818d130e95af1af6121e372b48?nocache=1, which did not confirm that virus. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #12 from Paul --- Hi Stephen Thanks for your email. For me the case is settled. I am not sure whether there was a misunderstanding. Just to clarify (if necessary): * KMyMoney was normally installed on the computer (not on a thumb drive) * Only the *.kmy-file is stored on an encrypted VERAcrypt-volume Have a good day and take care everybody! Thanks for your efficient handling of my bug-report!! Kind regards Paul Am 02.05.2022 um 14:52 schrieb Stephen Leibowitz: > https://bugs.kde.org/show_bug.cgi?id=453254 > > Stephen Leibowitz changed: > > What|Removed |Added > > CC||librestep...@gmail.com > > --- Comment #2 from Stephen Leibowitz --- > I agree that you should try a newer version of KMyMoney. I remember using > 5.0.6 > from a thumb drive. The three processes Paul mentioned were still active after > I exited the program. The system would not say that it was safe to eject the > thumb drive with them active. I had two options. I could start Task Manager > and > manually end the processes. I could also use the Windows TaskKill command. I > gave a fuller discussion of the problem at > https://forum.kde.org/viewtopic.php?f=69&t=165131 > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #13 from Paul --- Hi Ralf Today, it does not work anymore (enclosures). I will do forced dismounting in VERAcrypt and it's OK for me. Kind regards Paul Am 03.05.2022 um 11:39 schrieb Ralf Habacker: > https://bugs.kde.org/show_bug.cgi?id=453254 > > --- Comment #9 from Ralf Habacker --- > (In reply to Paul from comment #7) >> Created attachment 148526 [details] >> attachment-13375-0.html >> >> Hi again >> >> After sending the email below, I opened my *.kmy-file with the >> reinstalled version 5.0.6., made some changes, saved changes and closed >> KMyMoney. Then I waited approx. 5 seconds and dismounted the encrypted >> drive and astonishly I worked without any problem and did not ask me >> whether I want to do a "forced dismounting". >> >> No idea why! > This should be the normal behavior as on starting kmymoney the watchdog named > kwinshutdown.exe is started and terminates any background processes 5 seconds > after kmymoney has been closed (see share/autostart/kwinshutdown.desktop). > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #18 from Paul --- Created attachment 148561 --> https://bugs.kde.org/attachment.cgi?id=148561&action=edit kmymoney-active_processes_after_closing_kmymoney.JPG -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] KMyMoney is not closed completely and blocks dismounting of an encrypted volume where the *.kmy-file was saved.
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #17 from Paul --- Hi Ralf and Stephen Thanks a again. Ralf seems to have had the right idea! Dismounting is only blocked when opening kmymoney via double click on the *.kmy-file on the encrypted file! quote Therefore, the remaining reason for the reported problem could be/*that kmymoney was started from a path inside the Veracrypt container*/ and the leftover processes are blocking unmounting. Or another program like explorer could be blocking the unmount. unquote However, there seems to be another bug in the program when opening kmymoney via start menu without having previously mounted the VERYcrypt-drive; see below SECOND and THIRD way What did I do: * downloaded 64 bit-version 5.1.2 from your snapshot-link * extracted all files and copied them to the installation directory where 5.0.6 was installed (I renamed all 5.0.6-directories first!) * AVAST did not block anything; I previously added an exception to the installation directory of 5.0.6 (now 5.1.2) in AVAST *FIRST way* * started kmymoney with your start.bat-file * my *.kmy-file on the previously mounted VERAcrypt-drive opened correctly * made some changes in the *.kmy-file and saved it * exited kmymoney * after 5-6 seconds dismounted the VERAcrypt-drive * result: it dismounts immediately as expected * shutdown the computer *SECOND way* * restarted the computer * mounted the VERAcrypt-drive * doubleclicked the *.kmy-file * made some changed in the *.kmy-file and saved it * after 3 minutes dismounted the VERYcrypt-drive * result: error message as before, i.e. only a forced dismount is possible * forced dismounting of the VERYcrypt-drive * *after 10 minutes I opened kmymoney via the start menu without previously mounting the VERYcrypt-drive* * *result: kmymoney does not open; it hangs somewere; it's freezed* * shutdown the computer *THIRD way* * restarted the computer * mounted the VERAcrypt-drive * started kmymoney via the start menu * my *.kmy-file on the previously mounted VERAcrypt-drive opened correctly * made some changes in the *.kmy-file and saved it * exited kmymoney * after 5-6 seconds dismounted the VERAcrypt-drive * result: it dismounts immediately as expected * *after a few minutes I opened kmymoney via the start menu again without previously mounting the VERYcrypt-drive* * *result: ***kmymoney *does not open; it hangs somewere; it's freezed* After closing kmymoney I checked via Task Manager what program-parts are still active. In all three ways the same parts where still active (see enclosure). So the solution for me is either way 1 or way 3 😉 Hope the above helps to find the possible bug(s). Kind regards Paul NB: I am just programming in Visual Basic 6 starting with BASICA in the year 1984😂; so my process-knowledge is not as deep as yours, sorry. Am 04.05.2022 um 14:56 schrieb Ralf Habacker: > https://bugs.kde.org/show_bug.cgi?id=453254 > > --- Comment #15 from Ralf Habacker --- > (In reply to Paul from comment #14) >> Created attachment 148557 [Details] >> kmymoney-still_active_parts.JPG > It turns out that kwinshutdown*.exe is not included in version 5.0.6, so these > processes are not killed after 5 seconds by default. Since this tool is > included in the current snapshot, you need to download a newer snapshot from > https://kmymoney.org/snapshots.php to fix this issue. > > Using kmymoney 5.0.6 and procexp > (https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer), I > verified that the running kmymoney.exe and all background processes involved > do > not have an open file handle to the kmymoney file in use, even if it is stored > in a local Veracrypt container. > > Therefore, the remaining reason for the reported problem could be that > kmymoney > was started from a path inside the Veracrypt container and the leftover > processes are blocking unmounting. Or another program like explorer could be > blocking the unmount. > > You can find this out with procexp and the menu item Find->"Find Handle or > DLL" > by entering the drive letter e.g. "a:\". > > If the problem is kmymoney or a involved background process, only a newer > snapshot will help. > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453254] explorer blocks dismounting of an encrypted volume where the *.kmy-file was saved
https://bugs.kde.org/show_bug.cgi?id=453254 --- Comment #22 from Paul --- Thanks a lot Ralf for your help, patience and feedbacks! Take care! Kind regards Paul Am 6. Mai 2022 09:01:11 MESZ schrieb Ralf Habacker : >https://bugs.kde.org/show_bug.cgi?id=453254 > >--- Comment #19 from Ralf Habacker --- >Created attachment 148601 > --> https://bugs.kde.org/attachment.cgi?id=148601&action=edit >screenshot showing explorer blocking veracrypt unmount > >(In reply to Paul from comment #17) > >> *SECOND way* >... >> * doubleclicked the *.kmy-file > >That means you entered that directory with explorer, which *BLOCKS* the >unmount, not kmymoney. > >I can reproduce this issue by > >* restarted the computer > * mount the VERAcrypt-drive > * enter veracrypt container with explorer > * dismounted the VERAcrypt-drive >* result: error message, i.e. only a forced dismount is possible > >> Hope the above helps to find the possible bug(s). > >This bug is really not kmymoney related, it is a Microsoft explorer bug > >A workaround is to not use or uninstall the kmymoney installer to avoid >associating the *.kmy file type with the kmymoney executable. > >-- >You are receiving this mail because: >You are on the CC list for the bug. >You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453520] New: Kstars aborts after first image is captured in a sequence
https://bugs.kde.org/show_bug.cgi?id=453520 Bug ID: 453520 Summary: Kstars aborts after first image is captured in a sequence Product: kstars Version: git Platform: Compiled Sources OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: phome...@bigpond.net.au Target Milestone: --- Created attachment 148651 --> https://bugs.kde.org/attachment.cgi?id=148651&action=edit log from start up to abort SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** After the first capture of a sequence and after downloading but before saving kstars aborts STEPS TO REPRODUCE 0. Installed and built kstars, ekos etc onto Raspberry Pi 4 8GB (Bullseye IMPORTANT as it works for Buster) 1. Set up a profile with QSI camera only (for darks and lights) 2. Run profile 3. On Camera page and set up a sequence (for example 5 darks of 1 second) 4. Run sequence 5. Answer YES to Pop Up dialogue box asking if the camera has a shutter (THIS IS THE FIRST PROBLEM as it should not do this) 6. Takes image and downloads OBSERVED RESULT Kstars aborts but INDI keeps going EXPECTED RESULT First image is saved and next image capture is started SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 paul changed: What|Removed |Added CC||pl.grue...@gmail.com --- Comment #6 from paul --- (In reply to kdebugzilla from comment #0) > When I scroll with the touchpad on the audio icon to adjust the volume, I > have to scroll up to lower the volume and scroll down to increase it; I > think that this doesn't make sense and these two bindings should be inverted. As a user of natural/inverted scrolling for years, I would argue that this is not actually a bug, but working as expected. "Invert scrolling" means invert it _everywhere_, including the volume applet. It also makes more sense if you picture a vertical volume slider (with 100% volume at the top) with a handle that works the same as any other scroll bar: you do scrollwheel-UP to push that handle down (i.e. lower volume) and vice versa. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456518] KDE seems to think that the desktop is a laptop
https://bugs.kde.org/show_bug.cgi?id=456518 Paul changed: What|Removed |Added CC||pip@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 453520] Kstars aborts after first image is captured in a sequence
https://bugs.kde.org/show_bug.cgi?id=453520 Paul changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Paul --- I have retested this with the latest build on Bullseye and it is working. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458087] New: System Settings - Desktop Effects missing vertical scrollbar.
https://bugs.kde.org/show_bug.cgi?id=458087 Bug ID: 458087 Summary: System Settings - Desktop Effects missing vertical scrollbar. Product: systemsettings Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_effects Assignee: kwin-bugs-n...@kde.org Reporter: pip@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 151441 --> https://bugs.kde.org/attachment.cgi?id=151441&action=edit Screen-shot of System Settings - Desktop Effects showing no vertical scrollbar. SUMMARY System Settings - Desktop Effects has no vertical scrollbar. STEPS TO REPRODUCE 1. Launch System Settings 2. Navigate to Desktop Behaviour -> System Settings 3. OBSERVED RESULT Content exceeds window height and there is no vertical scrollbar. (Screen-shot attached). EXPECTED RESULT Vertical scrollbar present... :) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220817 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-1-default (64-bit) Graphics Platform: X11 Processors: 2 × AMD Athlon(tm) 64 X2 Dual Core Processor 5600+ Memory: 3.8 GiB of RAM Graphics: Device-1: NVIDIA G84 [GeForce 8600 GTS] vendor: Micro-Star MSI driver: nouveau v: kernel arch: Tesla bus-ID: 01:00.0 Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3 driver: X: loaded: nouveau unloaded: fbdev,modesetting,nv,vesa gpu: nouveau resolution: 1280x1024~60Hz OpenGL: renderer: NV84 v: 3.3 Mesa 22.1.4 direct render: Yes ADDITIONAL INFORMATION déjà vu :) -- I had this problem back in 2019 ( bug: 406182 ) In that instance it was caused by (an openSUSE packaging error?) missing "qqc2-desktop-style". This is not the case now though, as that package is installed: paul@Orion-15:~$ zypper if qqc2-desktop-style Loading repository data... Reading installed packages... Information for package qqc2-desktop-style: --- Repository : openSUSE-Tumbleweed-Oss Name : qqc2-desktop-style Version: 5.97.0-1.1 Arch : x86_64 Vendor : openSUSE Installed Size : 417.9 KiB Installed : Yes Status : up-to-date Source package : qqc2-desktop-style-5.97.0-1.1.src Upstream URL : https://www.kde.org Summary: A Qt Quick Controls 2 Style for Desktop UIs Description: A Qt Quick Controls 2 style engine that uses the desktop style to draw controls with QStyle. paul@Orion-15:~$ Is there now a requires for a different (also missing?) package perhaps? A default new user also exhibits the same issue of the missing scrollbar. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458087] System Settings - Desktop Effects missing vertical scrollbar.
https://bugs.kde.org/show_bug.cgi?id=458087 --- Comment #1 from Paul --- Brain strain :( Step 2 of Steps to Reproduce should have read "Navigate to Workspace Behaviour -> Desktop Effects" but I guess that was obvious... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Paul changed: What|Removed |Added CC|pip@gmx.com | -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458158] New: V3.6.0 crashes immediately on launch on M1 Mini and M1 Air
https://bugs.kde.org/show_bug.cgi?id=458158 Bug ID: 458158 Summary: V3.6.0 crashes immediately on launch on M1 Mini and M1 Air Product: kstars Version: 3.6.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: paul.cala...@mysignal.ca Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Launch Kstars 2. 3. OBSERVED RESULT Starts to load, then crashes EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Maverick Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Version 3.5.9 does not crash on these same platforms -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 458158] V3.6.0 crashes immediately on launch on M1 Mini and M1 Air
https://bugs.kde.org/show_bug.cgi?id=458158 --- Comment #2 from Paul --- Hi Rob Thanks for getting back to me and for the time you spent tracking down this bug. All works as expected now. Cheers PC On Aug 27, 2022, 1:06 AM -0400, Rob , wrote: > https://bugs.kde.org/show_bug.cgi?id=458158 > > --- Comment #1 from Rob --- > It has taken me some time to work through several issues, but I think the > 3.6.0 > is now a pretty good one. Please check to see if it is improved. Based on > what you said here, I suspect you had the issue that was caused by the loading > code for the asteroids.dat file. That issue was fixed yesterday and is now in > both the current DMG on the Kstars kde website and the nightly releases. So > please check and I hope it is all better now. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 458846] New: Popup Menus in wrong position with sway
https://bugs.kde.org/show_bug.cgi?id=458846 Bug ID: 458846 Summary: Popup Menus in wrong position with sway Product: digikam Version: 8.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability-Menus Assignee: digikam-bugs-n...@kde.org Reporter: paul.wwwalker2...@gmail.com Target Milestone: --- Created attachment 151893 --> https://bugs.kde.org/attachment.cgi?id=151893&action=edit Popup at wrong position SUMMARY Using the Position and scale properties in Sway window manager causes the Popups to appear at a wrong position. Similar to whats described here: https://github.com/swaywm/sway/issues/3135 STEPS TO REPRODUCE 1. Use sway 2. `swaymsg output DP-XX position 150 360` 3. start digikam on that monitor OBSERVED RESULT the menu popups like import, export, help and many others are positioned wrong. EXPECTED RESULT they are where they are when position is set to 0 0 or like it is in the promotional material. SOFTWARE/OS VERSIONS Linux: 5.19.7-arch1-1 Sway: 1.7 Qt Version: 5.15.5 ADDITIONAL INFORMATION Possibly similar to the described issue here https://github.com/swaywm/sway/issues/3135 Possibly fixable with https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes (from the issue thread in the sway issue above). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 458846] Popup Menus in wrong position with Sway window manager.
https://bugs.kde.org/show_bug.cgi?id=458846 --- Comment #2 from paul --- Thank you for the quick answer, glad that it will be fixed soon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442850] New: Information Panel to always show "real" date for recent file timestamps, not "Just Now", "Today", etc.
https://bugs.kde.org/show_bug.cgi?id=442850 Bug ID: 442850 Summary: Information Panel to always show "real" date for recent file timestamps, not "Just Now", "Today", etc. Product: dolphin Version: 21.08.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: pip@gmx.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Currently the Information Panel shows the date (of the timestamp) for recent files in the form of: "Just now", "Today", "Yesterday", or "n Days Ago". Whilst it might look pretty, IMHO, and certainly for my own use, it would be far more useful if the actual Date was displayed. Perhaps an option to choose the display method would be a solution if it is felt that the current method of display is "best". STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442850] Option for Information Panel to always show "real" date for recent file timestamps, not "Just Now", "Today", etc.
https://bugs.kde.org/show_bug.cgi?id=442850 --- Comment #2 from Paul --- (In reply to Méven Car from comment #1) > > From your own POV you admit, this looks pretty and fits your use. > No, that was not what I wrote, read again please. I don't want to calculate what the date was n days ago, I want the date displayed. But, whatever rocks your boat I guess. > So I don't see any issue here, just an overzealous missing setting feeling > for other potential users. ??? > > In the settings it could be like (with the default I am thinking about): > > Dates display : >With hours: [ ] Display time of day with dates >relative:[x] Use "Two days ago", "Just a moment ago" >shortened: [x] Use days of the current week like "Tuesday" and skipping > years for months of this year "10th of October" > > We would have the exact date in a tooltip on hover still and ordering > wouldn't be affected. That sounds marginally better - however IMHO there is too much "dumbing down" going on here. -- You are receiving this mail because: You are watching all bug changes.
