[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 --- Comment #8 from M-Rick --- I made some tricking and I found the reason. It's a bug in the initialization process. It's specific to Ventura and above. In the settings, I reverted language to English and relaunched Digikam. Then I changed the language again to French and it worked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 --- Comment #7 from M-Rick --- Created attachment 164069 --> https://bugs.kde.org/attachment.cgi?id=164069=edit Brand new install on a new macOS fresh install on an intel Mac -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 --- Comment #6 from M-Rick --- I just installed it on a completely fresh brand new install on an Intel macOS Ventura. I just installed macOS now, it doesn't even have other softwares than the macOS default ones. Digikam has been the first software to be installed after the initial system set up. I got exactly the same result with everything in English, unlocalized as it should be. In the localisation settings, French has been selected by default, but everything is displayed in English! Since you are the developer, how did you install it? Your installation can include libraries available on your computer, that haven't been well packaged in the regular package installer. I tried several packages available in the download section on the website. And whatever the package I downloaded, I got the same result. You should try on another session or into a VM to isolate everything from your development environment. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 --- Comment #4 from M-Rick --- OK, I am running it on an M2 MacBook Pro. It was a fresh install. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 --- Comment #2 from M-Rick --- (In reply to caulier.gilles from comment #1) > With the 8.2.0 just released and current pre-release version, the problem is > not reproducible on my macbook pro: > > https://imgur.com/F3b4pO9 > > Best regards > > Gilles Caulier Do you run it on an ARM Mac as well? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478084] New: Digikam 8.x language issue on macOS
https://bugs.kde.org/show_bug.cgi?id=478084 Bug ID: 478084 Summary: Digikam 8.x language issue on macOS Classification: Applications Product: digikam Version: 8.1.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Bundle-MacOS Assignee: digikam-bugs-n...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- Created attachment 163875 --> https://bugs.kde.org/attachment.cgi?id=163875=edit Digikam remains unlocalized after a fresh installation SUMMARY *** In Digikam 8.1 / 8.2 the language settings are unworking on macOS. The interface remains in English by default despite the settings. *** STEPS TO REPRODUCE 1. Download Digikam 8.1 or 8.2 and install 2. Launch Digikam in a non English language. OBSERVED RESULT Digikam sets up automatically everything, even select the default OS localisation, but remains in English even after restart. EXPECTED RESULT Digikam should launch with the system default localisation SOFTWARE/OS VERSIONS macOS: macOS Ventura 13.6.1 Apple Silicon (Rosetta 2) Digikam: 8.2.0 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 cocoa windowing system ADDITIONAL INFORMATION Default pkg from Digikam website. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469758] New: Won't use global menus in Flatpak
https://bugs.kde.org/show_bug.cgi?id=469758 Bug ID: 469758 Summary: Won't use global menus in Flatpak Classification: Applications Product: digikam Version: 8.0.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Bundle-FlatPak Assignee: digikam-bugs-n...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- When using the Flatpak version of Digikam, the global menus aren't enabled and not exported to the top panel. No problem if using the Debian package or the AppImage version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465622] regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 Rick Scholten changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465622] regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 --- Comment #6 from Rick Scholten --- Did a clean Fedora 38 Kinoite install and now 8000hz works fine. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 --- Comment #6 from Rick Smegal --- Here is some final clarification detail. When I originally installed marble with opensuse YaST, the marble version was used, NOT the marble-qt front end; this is the situation with crashes. Later, I noticed that there was a marble-qt version which I then installed with YaST; this fixed the crash upon exit. In case you don't have the information, I am using KDE plasma Version 5.24.4 and KDE Frameworks Version 5.90.0. On 2023-04-07 23:08, Torsten Rahn wrote: > https://bugs.kde.org/show_bug.cgi?id=466853 > > --- Comment #5 from Torsten Rahn --- >> How does one execute marble with the marble-qt front end installed? >> The only executable I see is: /usr/bin/marble-qt > Yes, marble-qt is the executable that is the version which has technically no > KDE dependency. > If there was a version /usr/bin/marble as well then this would be the KDE > version. > > Both should work equally well without crashing. Personally I don't see any > crashes when working with marble-qt. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 --- Comment #3 from Rick Smegal --- How does one execute marble with the marble-qt front end installed? The only executable I see is: /usr/bin/marble-qt On 2023-04-07 12:56, Torsten Rahn wrote: > https://bugs.kde.org/show_bug.cgi?id=466853 > > Torsten Rahn changed: > > What|Removed |Added > > CC||r...@kde.org > > --- Comment #2 from Torsten Rahn --- > So does the issue still occur with "marble" but not with "marble-qt" ? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 --- Comment #1 from Rick Smegal --- The above error no longer occurred following installation of the package marble-qt. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] New: Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 Bug ID: 466853 Summary: Marble crashes on exit. Classification: Applications Product: marble Version: unspecified Platform: openSUSE OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: rsme...@aardvarr.ca Target Milestone: --- Created attachment 157001 --> https://bugs.kde.org/attachment.cgi?id=157001=edit Saved report. SUMMARY A saved bug report is attached. 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.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Rick Scholten changed: What|Removed |Added CC|khr...@proton.me| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465622] regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 --- Comment #5 from Rick Scholten --- (In reply to Vlad Zahorodnii from comment #4) > (In reply to Rick Scholten from comment #3) > > (In reply to Vlad Zahorodnii from comment #2) > > > Does KWIN_DRM_NO_AMS=1 envvar make any different? > > > > I looked up setting variables and came across > > https://userbase.kde.org/Session_Environment_Variables > > > > I've made $HOME/.config/plasma-workspace/env/mouse.sh containing > > #!/bin/bash > > KWIN_DRM_NO_AMS=1 > > > > Rebooted and set mouse firmware to 8000hz. No change in erratic mouse > > behaviour. > > > > I can't stop thinking there's a flaw in my process and I wonder how I can > > test if that variable has been set. Could you point me in the right > > direction? > > Run "qdbus org.kde.KWin /KWin supportInformation | grep Atomic" > > if the envvar is properly set, you should see > > Atomic Mode Setting on GPU 0: false Ty! "Atomic Mode Setting on GPU 0: false" appears both with and without manually setting KWIN_DRM_NO_AMS=1, and in both cases 8000hz does not work properly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465622] regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 --- Comment #3 from Rick Scholten --- (In reply to Vlad Zahorodnii from comment #2) > Does KWIN_DRM_NO_AMS=1 envvar make any different? I looked up setting variables and came across https://userbase.kde.org/Session_Environment_Variables I've made $HOME/.config/plasma-workspace/env/mouse.sh containing #!/bin/bash KWIN_DRM_NO_AMS=1 Rebooted and set mouse firmware to 8000hz. No change in erratic mouse behaviour. I can't stop thinking there's a flaw in my process and I wonder how I can test if that variable has been set. Could you point me in the right direction? -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 466036] New: kded5 crash after resume from blank
https://bugs.kde.org/show_bug.cgi?id=466036 Bug ID: 466036 Summary: kded5 crash after resume from blank Classification: Plasma Product: kded-appmenu Version: 5.27.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Titlebar menu button/popup Assignee: plasma-b...@kde.org Reporter: dxq7...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** kded5 crash after resume from blank ``` Application: kded5 (kded5), signal: Segmentation fault [KCrash Handler] #4 0x7f49d62ad270 in KScreen::Output::id() const () from /lib64/libKF5Screen.so.8 #5 0x7f49d62a01f8 in KScreen::Config::setOutputPriority(QSharedPointer const&, unsigned int) () from /lib64/libKF5Screen.so.8 #6 0x7f49d62a9ca2 in KScreen::SetConfigOperation::start() () from /lib64/libKF5Screen.so.8 #7 0x7f4a11907d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7f4a127a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #9 0x7f4a118dc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f4a118df181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #11 0x7f4a11934413 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f4a1051ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #13 0x7f4a1051be48 in ?? () from /lib64/libglib-2.0.so.0 #14 0x7f4a1051bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #15 0x7f4a11933c16 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f4a118dac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f4a118e2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55f59658b976 in ?? () #19 0x7f4a1102caf0 in __libc_start_call_main () from /lib64/libc.so.6 #20 0x7f4a1102cbb9 in __libc_start_main_impl () from /lib64/libc.so.6 #21 0x55f59658bb75 in ?? () [Inferior 1 (process 2368) detached] ``` STEPS TO REPRODUCE 1. settings -> power management -> display off after 1 minute 2. resume display after the screen black 3. get kded5 crash error, tray icon not working and maybe others OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux/opensuse tumbleweed (available in About System) KDE Plasma Version:plasma 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465622] regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 Rick Scholten changed: What|Removed |Added Version|5.26.90 |5.27.0 --- Comment #1 from Rick Scholten --- Issue on Fedora 37 Kinoite with Plasma 5.27.0 too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 Rick Scholten changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #10 from Rick Scholten --- After Fedora 37 Kinoite update from plasma 5.26.5 to 5.27.0 the was resolved. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #9 from Rick Scholten --- Looks like KDE Frameworks 5.103.0 introduced the problem, not Plasma 5.26.90. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #8 from Rick Scholten --- After updating Fedora 37 Kinoite with plasma 5.26.5 to KDE Frameworks 5.103.0 the problems has appeared there too. I've also tested it on my iGPU Intel laptop with F37K 5.26.5 and 5.103.0 and it has the problem too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #7 from Rick Scholten --- In X11 I experience the same behaviour as in Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #6 from Rick Scholten --- Ty for the information. 1. It's Fedora Kinoite 38: image based distro. No installation on my part. 2. Wayland 3. Nvidia GTX 1060. I don't have proprietary Nvidia drivers installed. The launchers are the default launchers shipped in Plasma, both 5.26.5 and 5.26.90. It happens with all Chromium based flatpak browsers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #5 from Rick Scholten --- Created attachment 156227 --> https://bugs.kde.org/attachment.cgi?id=156227=edit Log - resulting in plasma/kwin crash Opening Incognito window by right-click Google Chrome from Application Menu/Internet. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #4 from Rick Scholten --- Created attachment 156226 --> https://bugs.kde.org/attachment.cgi?id=156226=edit Log - resulting in unresponsive behaviour Opening Chrome Incognito by right-click favourite in Application Menu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu/Launcher/Dashboard and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 Rick Scholten changed: What|Removed |Added Summary|regression: unresponsive|regression: unresponsive |Application Menu and Task |Application |Manager |Menu/Launcher/Dashboard and ||Task Manager -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #2 from Rick Scholten --- I encounter the same unresponsiveness when opening Google Chrome Incognito window from either Application Dashboard or Application Launcher. Here there is no Plasma/KWin crash when not opening the Incognito window from favourites. There is only unresponsive Application Dashboard/Launcher and Task Manager. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 374890] kscreenlocker_greet freezes with multiscreen setup and blocks unlocking
https://bugs.kde.org/show_bug.cgi?id=374890 Rick Scholten changed: What|Removed |Added CC||khr...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 --- Comment #1 from Rick Scholten --- STEPS TO REPRODUCE 1. Install Google Chrome from Flathub. 2. In Application Menu go to Internet, Right-click Google Chrome, Add to Favourites 3. From Favourites in Application Menu, Right-click Google Chrome, New Incognito window. OBSERVED RESULT: unresponsive Application Menu and Task Manager Seems to be related to Plasma?/KWin? crashing and restarting: 1. Install Google Chrome from Flathub. 2. In Application Menu go to Internet, Right-click Google Chrome, New Incognito window. OBSERVED RESULT: Plasma?/KWin? crashing and restarting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] regression: unresponsive Application Menu and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 Rick Scholten changed: What|Removed |Added Summary|Plasma 5.26.90 causes |regression: unresponsive |unresponsive Application|Application Menu and Task |Menu and Task Manager |Manager Keywords||regression Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465685] New: Plasma 5.26.90 causes unresponsive Application Menu and Task Manager
https://bugs.kde.org/show_bug.cgi?id=465685 Bug ID: 465685 Summary: Plasma 5.26.90 causes unresponsive Application Menu and Task Manager Classification: Plasma Product: kwin Version: 5.26.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: khr...@proton.me Target Milestone: --- SUMMARY *** Flatpak Google Chrome Incognito window causes unresponsive Application Menu and Task Manager in Plasma 5.26.90. No problems in normal Chrome window. No problems in Plasma 5.26.5 with Incognito. *** STEPS TO REPRODUCE 1. Install Google Chrome from Flathub. 2. Open Google Chrome Incognito with right click from Application Menu. OBSERVED RESULT Application Menu and Task Manager are unresponsive. EXPECTED RESULT Application Menu and Task Manager are responsive. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kinoite 38 KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Screen recording: https://ufile.io/g3jwvtlx -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465622] New: regression: 8000hz mouse polling does not work properly
https://bugs.kde.org/show_bug.cgi?id=465622 Bug ID: 465622 Summary: regression: 8000hz mouse polling does not work properly Classification: Plasma Product: kwin Version: 5.26.90 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: khr...@proton.me Target Milestone: --- SUMMARY *** Since upgrading to Plasma 5.26.90 I can't use 8000hz mouse polling. In 5.26.5 it worked fine. *** STEPS TO REPRODUCE Boot into Fedora Kinoite 38 on Plasma 5.26.90. Does not happen when I boot back into FK37 with Plasma 5.26.5. OBSERVED RESULT Sluggish and erratic mouse behaviour. EXPECTED RESULT Precise mouse control. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kinoite KDE Plasma Version: 5.26.90 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428511] KMyMoney for MacOS is not localised
https://bugs.kde.org/show_bug.cgi?id=428511 --- Comment #4 from M-Rick --- Created attachment 154546 --> https://bugs.kde.org/attachment.cgi?id=154546=edit Language settings Language settings, only English is available -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428511] KMyMoney for MacOS is not localised
https://bugs.kde.org/show_bug.cgi?id=428511 M-Rick changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #3 from M-Rick --- I reopen this bug because it's back in the latest releases. kmymoney-5.1-1597-macos-clang-x86_64. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 389127] message and folder selection unresponsive
https://bugs.kde.org/show_bug.cgi?id=389127 Rick Smegal changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Rick Smegal --- This problem has not manifested itself following upgrades to version 5.5.2. However, I cannot add much in regard to recent versions since kmail2 was dropped as my mail client at the start of year 2019. This ticket can be closed. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461734] macOS GUI improvements
https://bugs.kde.org/show_bug.cgi?id=461734 --- Comment #1 from M-Rick --- Created attachment 153691 --> https://bugs.kde.org/attachment.cgi?id=153691=edit Underscores in menu an on buttons -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461734] New: macOS GUI improvements
https://bugs.kde.org/show_bug.cgi?id=461734 Bug ID: 461734 Summary: macOS GUI improvements Classification: Applications Product: digikam Version: 7.8.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Bundle-MacOS Assignee: digikam-bugs-n...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- Created attachment 153690 --> https://bugs.kde.org/attachment.cgi?id=153690=edit Icons in macOS menus On macOS, the GUI guideline do not recommend the use of icons in menus. Plus, when using a dark them, the white icons aren't visible on a light theme. And, is there a way to remove all the underscores appearing everywhere over the buttons or windows? They are completely useless because macOS behaviour is different. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460161] Unable to run commands from Power menu
https://bugs.kde.org/show_bug.cgi?id=460161 --- Comment #1 from Rick --- Created attachment 152663 --> https://bugs.kde.org/attachment.cgi?id=152663=edit unable to run command popup error -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 460161] New: Unable to run commands from Power menu
https://bugs.kde.org/show_bug.cgi?id=460161 Bug ID: 460161 Summary: Unable to run commands from Power menu Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: meeseekslifeish...@tutanota.com Target Milestone: --- SUMMARY When I try to run commands like Unlock, Suspend I am able to run those from KDE Connect application but when I try to run the same through power menu device control it says not found. Control is unavilable STEPS TO REPRODUCE 1. Add commands to execute in kde Connect app 2. Now enable device control in android 3. add the commands to device control 4. Press power button and try to launch the commands from the power menu OBSERVED RESULT It says not found, Control is unavailable. EXPECTED RESULT Ability to run commands from power menu SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 36 (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.
[systemsettings] [Bug 458971] Add a section in system settings "About This System" page to change device\host name of the computer
https://bugs.kde.org/show_bug.cgi?id=458971 --- Comment #1 from Rick --- Created attachment 151968 --> https://bugs.kde.org/attachment.cgi?id=151968=edit Example form Ubuntu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458971] Add a section in system settings "About This System" page to change device\host name of the computer
https://bugs.kde.org/show_bug.cgi?id=458971 Rick changed: What|Removed |Added Attachment #151967|Example of the device name |tool tip example description|from Ubuntu and tool tip| |example | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458971] New: Add a section in system settings "About This System" page to change device\host name of the computer
https://bugs.kde.org/show_bug.cgi?id=458971 Bug ID: 458971 Summary: Add a section in system settings "About This System" page to change device\host name of the computer Product: systemsettings Version: 5.24.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s.snide...@gmail.com Target Milestone: --- Created attachment 151967 --> https://bugs.kde.org/attachment.cgi?id=151967=edit Example of the device name from Ubuntu and tool tip example SUMMARY I have noticed that there is no GUI way to change the computer\machine\Host name or even view the name in KDE Plasma. This is a basic function that is even implemented in Gnome settings. This would be a great addition for user friendliness and an UI improvement. STEPS TO REPRODUCE 1. There are no steps to reproduce as this is a feature request. EXPECTED RESULT I think this computer name change feature could be simply added to the "About This System" page. It can be setup exactly like the Hardware and Software sections are setup. The header would be called "Device Name" and under it an editable box with the current device name. One name is inputted prompt for reboot if required. Additional as a tool tip, when you hoover over the editable box a tool tip should appear explaining that this sections changes the name of the device and the new name will be how it appears throughout your network and a reboot may be required. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04.1 (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.95 Qt Version: 5.15.3 ADDITIONAL INFORMATION None -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457693] digikam crashes if trying to delete selection of multiple files
https://bugs.kde.org/show_bug.cgi?id=457693 Rick Wagner changed: What|Removed |Added CC||rjwgn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 457693] digikam crashes if trying to delete selection of multiple files
https://bugs.kde.org/show_bug.cgi?id=457693 --- Comment #11 from Rick Wagner --- Created attachment 151934 --> https://bugs.kde.org/attachment.cgi?id=151934=edit New crash information added by DrKonqi digikam (7.7.0) using Qt 5.15.5 Marked two items in the thumbnail view, then pressed the "Delete Key", resulting in this crash. Happens frequently, but not always. -- Backtrace (Reduced): #4 0x7efd7369966f in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () at /lib64/libQt5Widgets.so.5 #5 0x7efd7369da49 in QTreeView::drawTree(QPainter*, QRegion const&) const () at /lib64/libQt5Widgets.so.5 #6 0x7efd736a4168 in QTreeView::paintEvent(QPaintEvent*) () at /lib64/libQt5Widgets.so.5 #7 0x7efd733f1828 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #8 0x7efd7349e512 in QFrame::event(QEvent*) () at /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 458620] New: Batch Queue Manager does not offer a "Color Negative Film" tool
https://bugs.kde.org/show_bug.cgi?id=458620 Bug ID: 458620 Summary: Batch Queue Manager does not offer a "Color Negative Film" tool Product: digikam Version: 7.7.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: BatchQueueManager-Plugins Assignee: digikam-bugs-n...@kde.org Reporter: rjwgn...@gmail.com Target Milestone: --- I am converting color film negatives to digital using my DSLR. After copying a number of images, I wish to import them into digiKam, and convert them. After importing into an album, I would like to use BQM to perform the conversion in the album. The tool is available in the image editor, but not BQM. STEPS TO REPRODUCE 1. Photograph film negatives using DSLR 2. Import the images into digiKam 3. Open Batch Queue Manager, and look for "Color Negative Film" in base tools OBSERVED RESULT 1. There is no "Color Negative Film" tool EXPECTED RESULT 1. There should be a "Color Negative Film" tool SOFTWARE/OS VERSIONS Linux/KDE Plasma: Version 5.97.0 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458303] Elisa cannot play a physical CD, unless carefully found by opening Files -> Dev -> FD.
https://bugs.kde.org/show_bug.cgi?id=458303 Rick Stockton changed: What|Removed |Added CC||rickstockton@reno-computerh ||elp.com -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458303] New: Elisa cannot play a physical CD, unless carefully found by opening Files -> Dev -> FD.
https://bugs.kde.org/show_bug.cgi?id=458303 Bug ID: 458303 Summary: Elisa cannot play a physical CD, unless carefully found by opening Files -> Dev -> FD. Product: Elisa Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: rickstock...@reno-computerhelp.com Target Milestone: --- Attempting to use Elisa as an alternative to VLC media player. Loaded a physical CD (a commercial, not a home-made burn) my KDE desktop offers 4 alternative actions for the properly recognized device. "Open with Elisa Music Player" is not among them. (I am offered 'Copy with K3b', Open with File Manager', 'Open with VLC media player', and 'Extract Digital Audio with K3b'). When an audio CD has been loaded (and recognized as such by solid), the left menu should offer to play it without digging into 'files'. Also, when the removable device has been loaded as a 'removable device', the menu item (within the pop-up Disks and Devices Applet) should have "Open with Elisa music player" as an alternative - possibly even offered as a default 'Action'. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 458047] New: black screen
https://bugs.kde.org/show_bug.cgi?id=458047 Bug ID: 458047 Summary: black screen Product: skrooge Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: anrimer...@yahoo.com CC: steph...@mankowski.fr Target Milestone: --- SUMMARY *** used sudo command to install Skrooge, rebooted on completed install, clicked icon and received a black screen 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. 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.
[digikam] [Bug 456365] Importing filetype QOI
https://bugs.kde.org/show_bug.cgi?id=456365 --- Comment #4 from Rick Wortelboer --- Gratis. Thank! Rick Op di 5 jul. 2022 22:19 schreef Maik Qualmann : > https://bugs.kde.org/show_bug.cgi?id=456365 > > Maik Qualmann changed: > >What|Removed |Added > > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > Go to digiKam Setup under View-> Mime Types and add "qoi" as Image Mime > Type. > digiKam will rescan the collection and will display the files. Since the > Image > Magick Loader lists the file type, a thumbnail and display of such images > should work. > > Maik > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456365] Importing filetype QOI
https://bugs.kde.org/show_bug.cgi?id=456365 Rick Wortelboer changed: What|Removed |Added CC||rickwortelb...@gmail.com Alias||QOI, import, and, export -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 456365] New: Importing filetype QOI
https://bugs.kde.org/show_bug.cgi?id=456365 Bug ID: 456365 Summary: Importing filetype QOI Product: digikam Version: 7.7.0 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Database-Files Assignee: digikam-bugs-n...@kde.org Reporter: rickwortelb...@gmail.com Target Milestone: --- SUMMARY *** I would like to use QOI type files with DigiKam. *** STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Can not import QOI File Type EXPECTED RESULT Importing and exporting QOI Files 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.
[kdenlive] [Bug 455508] unable to import MKV or MP4 clips containing x.264 video with single stereo audio track. Files downgraded to 'TS' using ffmpeg import OK.
https://bugs.kde.org/show_bug.cgi?id=455508 Rick Stockton changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #2 from Rick Stockton --- following an upgrade to today's released tumbleweed version, the MP4 file imports OK. A new and upgraded version of Melt was included, replacing Melt 7.6 (which had the problem). Kdelinve "Version 22.04.2". Melt Version "7.8.0", Tumbleweed RPM version "7.8.0-1.1" Marking RESOLVED - UPSTREAM by changes in MELT 7.8.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455508] unable to import MKV or MP4 clips containing x.264 video with single stereo audio track. Files downgraded to 'TS' using ffmpeg import OK.
https://bugs.kde.org/show_bug.cgi?id=455508 --- Comment #1 from Rick Stockton --- With this comment, I reference a 'failing' MP4 clip (kdenlive crash upon import), along with a 'working bypass' MTS file. Both play within VLC, and import to other manipulation apps (handbrake, avidimux, etc). Although these files contain an irrelevant audio recode to OPUS, the import problem is related to the video, not the audio. When the MTS is imported to this project, KDE correctly offers to modify the FPS of the project to match the clip, and when I choose not to do that, the clip is adapted to the project's specified profile. Either choice is successful. But, when the MP4 is imported, kdenlive crashes. (Sometimes with a Dr Konqi popup, sometimes without.) The MTS was created from the MP4 using this simple ffmpeg command: ffmpeg -i out2.mp4 -c:v copy -c:a copy out2.mts - - - This may be a critical hint: For the failing MP4 file input file, ffmpeg shows "59.94 fps, 59.94 tbr, 30k tbn, 119.88 tbc (default)" For the 'succeeding' MTS output file from ffmpeg, ffmpeg shows specification changes to tbn and tbc: "59.94 fps, 59.94 tbr, 90k tbn, 30k tbc (default)" - - - MP4 file download: https://drive.google.com/file/d/17JMkKClcMJZJbnfY5428nf3lS24h8ffL/view?usp=sharing MTS file download: https://drive.google.com/file/d/1-W0uBkgvN3Od8YzGCA49E_JKvyswHqWN/view?usp=sharing Empty Project Download: https://drive.google.com/file/d/1_LHyzty2F0sciM520r_ao5SAUSkb6Jes/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455508] unable to import MKV or MP4 clips containing x.264 video with single stereo audio track. Files downgraded to 'TS' using ffmpeg import OK.
https://bugs.kde.org/show_bug.cgi?id=455508 Rick Stockton changed: What|Removed |Added CC||rickstockton@reno-computerh ||elp.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 455508] New: unable to import MKV or MP4 clips containing x.264 video with single stereo audio track. Files downgraded to 'TS' using ffmpeg import OK.
https://bugs.kde.org/show_bug.cgi?id=455508 Bug ID: 455508 Summary: unable to import MKV or MP4 clips containing x.264 video with single stereo audio track. Files downgraded to 'TS' using ffmpeg import OK. Product: kdenlive Version: 22.04.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: rickstock...@reno-computerhelp.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Unable to attach a report via the KDE crash handler, it hangs on current OpenSuse Tumbleweed updated today (with Kernel 5.18.2-1-default, melt and most of KDE were updated among 5000+ other packages). New with this version and its co-requisite MELT-7 and FFMPEG4, did not happen yesterday. KDE Apps are version 5.25.0, Frameworks is Tumblweed 5.94.0. STEPS TO REPRODUCE 1. Create a project. 2. Add a valid and playable MP4 or MKV clip, containing one track of Stereo audio using codec AAC (LAV), OPUS, or AC3. OBSERVED RESULT Instant crash results, with failing KDE crash handler. EXPECTED RESULT Successful Import to the Project. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse Tumbleweed, rev 06/06/14/2022 mlweed (available in About System) KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.90.4 Qt Version: 5.15.2+kde294-5.4 ADDITIONAL INFORMATION Converted the Camera's "native" AC3 audio to Opus. AAC. and a re-encoded AC3 within both an MKV and MP4 container (with -moveflags present in the MP4 container conversion). No alternative audio version was succesfully imported. I did not (yet) try importing the video track alone. Failing file size was about 20GB. BYPASS: A failing large file can be exported to a single long "ts" output file using an external tool such as avidemux; the 'ts' version can then be imported to kdenlive without issues. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 454986] New: Crash when manipulating profiles in a specific way.
https://bugs.kde.org/show_bug.cgi?id=454986 Bug ID: 454986 Summary: Crash when manipulating profiles in a specific way. Product: konsole Version: 21.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: rickeyachamb...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Settings -> Manage Profiles 2. Add a new profile with the default settings, and press Okay. 3. Make this new profile the default profile 4. Now make the original profile the default profile 5. Then click on the new profile you created. 6. Click remove, and then without clicking anything else click set as default again on the right hand side OBSERVED RESULT Konsole then crashes EXPECTED RESULT Konsole should instead select another profile from the list when you delete a profile if possible, so this can't happen, or it should disable the buttons on the right hand side if no profile is selected. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453666] Pen is acting super funny
https://bugs.kde.org/show_bug.cgi?id=453666 Rick changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453666] New: Pen is acting super funny
https://bugs.kde.org/show_bug.cgi?id=453666 Bug ID: 453666 Summary: Pen is acting super funny Product: krita Version: 5.0.6 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tablets (tablet issues are only very rarely bugs in Krita!) Assignee: krita-bugs-n...@kde.org Reporter: rick.g.phi...@gmail.com Target Milestone: --- SUMMARY *** Just today, when I try to use my pen on my Huion GT-190 tablet screen, it senses the pen from too far away and won't let go of it. Even after i pull my pen and arm away from the tablet, the program is still trying to sense the pen and will continue to draw as if I was putting pressure on the pen, even if I move the mouse around. *** STEPS TO REPRODUCE 1. Close program 2. Open Program 3. Draw OBSERVED RESULT Program acts as if the pen is pressing against the screen when it actually is away from screen. EXPECTED RESULT To draw normally SOFTWARE/OS VERSIONS Windows: 10 (86_64) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.12 ADDITIONAL INFORMATION I have tried to recalibrate my pen and drawing tablet, but it hasn't worked. I have also restarted my computer and programs and it hasn't worked. I have tested this out on other programs, like Paint.net and photoshop, and I don't have a problem with them. I had this problem on a previous version, (It was 4.4 something) and I thought updating it would fix it. It hasn't. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 446580] Contact synchronization with google doesn't work.
https://bugs.kde.org/show_bug.cgi?id=446580 Rick changed: What|Removed |Added CC||rhs.mess...@gmail.com --- Comment #2 from Rick --- Operating System: FreeBSD 13.0 KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 13.0-RELEASE-p7 (64-bit) Graphics Platform: X11 Memory: 15.9 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 3000 Not only is the Gcontact import stub not working, but, manually trying to add a Vcard file will not work either. You now have to request your data be sent to you by google if you want a vcard formated list of your contacts. This should at the minimum work locally. What a disappointment after successfully setting up what seems to be a very good imap server with Kmail. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 449506] New: The program can't start because api-ms-win=downlevel-kernel32-12-1-0.dll is missing from your computer.
https://bugs.kde.org/show_bug.cgi?id=449506 Bug ID: 449506 Summary: The program can't start because api-ms-win=downlevel-kernel32-12-1-0.dll is missing from your computer. Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: richardneif...@gmail.com Target Milestone: --- Created attachment 146178 --> https://bugs.kde.org/attachment.cgi?id=146178=edit Information from "Please paste the following information into the bug report!" Upon install, and again upon reinstall, at startup, Krita 5.0.2 displays the message "The program can't start because api-ms-win=downlevel-kernel32-12-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem." Prior installed version of Krita did not display this message. Krita, nevertheless, does start, despite this message, and works as intended. STEPS TO REPRODUCE 1. Download "krita-x64-5.0.2-setup.exe" 2. Install Krita 5.0.2 in Windows 7 Ultimate, service pack 1. 3. Run krita.ex at location "C:\Program Files\Krita (x64)\bin\krita.exe" OBSERVED RESULT Dialog box opens, title bar "krita.exe - System error" and text "The program can't start because api-ms-win=downlevel-kernel32-12-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem." Click "OK" on the box, wait 10 seconds, and the Krita interface appears (and Krita runs without problems.) EXPECTED RESULT No dialog box should open. SOFTWARE/OS VERSIONS Windows: Windows 7 Ultimate, SP 1 Krita 5.0.2 ADDITIONAL INFORMATION - See attachment containing information from "Please paste the following information into the bug report!" -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 445976] Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 --- Comment #5 from Rick --- I've changed my distro from KDE Neon to MX Linux KDE version. This distro uses Dolphin 20.12.2 and everything is running fine. The only change in my setup is the distro; hardware, network and server are all the same. I'll keep a version of KDE Neon around to help you with troubleshooting but it is not my daily use distro anymore. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445976] Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 --- Comment #3 from Rick --- just checked and yes it is installed. Krusader works in place of Dolphin but I hate that app. On Tue, Nov 23, 2021 at 12:14 PM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=445976 > > Nate Graham changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > CC||n...@kde.org > Status|REPORTED|NEEDSINFO > > --- Comment #2 from Nate Graham --- > Do you have kio-fuse installed? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445976] Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 --- Comment #1 from Rick --- Libreoffice exits without saving file or leaving partial file on server. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445976] New: Cannot write to samba share
https://bugs.kde.org/show_bug.cgi?id=445976 Bug ID: 445976 Summary: Cannot write to samba share Product: dolphin Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: rick0...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Client can read and create files and folders but cannot overwrite existing files on samba share. STEPS TO REPRODUCE 1. Open shared file on samba server through Dolphin 2. Edit file in kwrite, kate, libreoffice 3. Save file OBSERVED RESULT The following error appears: Could not rename partial file smb://raspberrypi.local/pi/shared/filename.part. Please check permissions. A partial file is left on server. EXPECTED RESULT Save file without issues SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: 5.11.0.40-generic(64-bit) (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Windows 11 Notepad works perfectly through Windows file explorer Dolphin version 20.12.2 works perfectly Linux kernel: 5.10.0-9-amd64 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445497] New: All Konsole windows crashed when a session which had launched a background application was closed
https://bugs.kde.org/show_bug.cgi?id=445497 Bug ID: 445497 Summary: All Konsole windows crashed when a session which had launched a background application was closed Product: konsole Version: 21.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: karl.solomo...@gmail.com Target Milestone: --- Application: konsole (21.08.3) Qt Version: 5.15.2 Frameworks Version: 5.87.0 Operating System: Linux 5.14.16-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.23.2 [KCrashBackend] -- Information about the crash: - Multiple Konsole sessions opened, some in split view, some SSH'd into VPN - I had opened a text editor (Sublime) with 'nohup subl &' - When I closed the session which had spawned sublime all konsole windows crashed Sublime Text Build 4121 OpenConnect version v8.10 (for VPN) The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [KCrash Handler] #4 0x7f15f159bb24 in QProcess::processId() const () at /usr/lib/libQt5Core.so.5 #5 0x7f15f296c82e in Konsole::Session::processId() const () at /usr/lib/libkonsoleprivate.so.21 #6 0x7f15f296dbef in Konsole::Session::isForegroundProcessActive() () at /usr/lib/libkonsoleprivate.so.21 #7 0x7f15f2a3aa87 in Konsole::MainWindow::queryClose() () at /usr/lib/libkonsoleapp.so.21 #8 0x7f15f27fdc55 in KMainWindow::closeEvent(QCloseEvent*) () at /usr/lib/libKF5XmlGui.so.5 #9 0x7f15f21fc0be in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7f15f283f668 in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #11 0x7f15f21b8d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7f15f16313fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x7f15f21f6f7e in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f15f16687ab in () at /usr/lib/libQt5Core.so.5 #15 0x7f15f16687ab in () at /usr/lib/libQt5Core.so.5 #16 0x7f15f29729bc in Konsole::Session::done(int, QProcess::ExitStatus) () at /usr/lib/libkonsoleprivate.so.21 #17 0x7f15f16687ab in () at /usr/lib/libQt5Core.so.5 #18 0x7f15f159a6f9 in QProcess::finished(int, QProcess::ExitStatus) () at /usr/lib/libQt5Core.so.5 #19 0x7f15f15a0206 in () at /usr/lib/libQt5Core.so.5 #20 0x7f15f15a033e in () at /usr/lib/libQt5Core.so.5 #21 0x7f15f16687e0 in () at /usr/lib/libQt5Core.so.5 #22 0x7f15f166bc70 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #23 0x7f15f166c47d in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7f15f21b8d62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f15f16313fa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f15f168ac3e in () at /usr/lib/libQt5Core.so.5 #27 0x7f15ef6bb4dc in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #28 0x7f15ef70f799 in () at /usr/lib/libglib-2.0.so.0 #29 0x7f15ef6b8bc1 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #30 0x7f15f168a09f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #31 0x7f15f162fd6c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #32 0x7f15f16382d4 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #33 0x5565c24cd63f in () #34 0x7f15f0fbdb25 in __libc_start_main () at /usr/lib/libc.so.6 #35 0x5565c24cd9de in () [Inferior 1 (process 166224) detached] Possible duplicates by query: bug 374174, bug 342216, bug 306503, bug 298337, bug 236867. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 442751] New: Crash when closing KDevelop session
https://bugs.kde.org/show_bug.cgi?id=442751 Bug ID: 442751 Summary: Crash when closing KDevelop session Product: kdevelop Version: 5.6.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: rjwgn...@gmail.com Target Milestone: --- Application: kdevelop (5.6.2) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.16-200.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.4 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: I had a development session open. I was only reviewing code, not modifying any code, so had not made any changes. I closed the session by clicking the close button on the application title bar, and go the pop-up saying "KDevelop has crashed". The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f81debf0d13 in QStackedLayout::widget(int) const () at /lib64/libQt5Widgets.so.5 #5 0x7f814e323a1d in Konsole::TabbedViewContainer::viewSplitterAt(int) () at /lib64/libkonsoleprivate.so.21 #6 0x7f814e3268a6 in Konsole::TabbedViewContainer::currentTabViewCount() () at /lib64/libkonsoleprivate.so.21 #7 0x7f814e2ce849 in Konsole::ViewManager::sessionFinished() () at /lib64/libkonsoleprivate.so.21 #8 0x7f81ddf453a9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #9 0x7f81ddf453a9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #10 0x7f81dde98e73 in QProcess::finished(int, QProcess::ExitStatus) () at /lib64/libQt5Core.so.5 #11 0x7f81dde9d433 in QProcessPrivate::_q_processDied() () at /lib64/libQt5Core.so.5 #12 0x7f81ddea1102 in QProcessPrivate::waitForFinished(int) () at /lib64/libQt5Core.so.5 #13 0x7f814e3389e0 in Konsole::Session::closeInNormalWay() () at /lib64/libkonsoleprivate.so.21 #14 0x7f814e32f13a in Konsole::Session::close() () at /lib64/libkonsoleprivate.so.21 #15 0x7f81ddf453a9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #16 0x7f81ddf403e3 in QObject::destroyed(QObject*) () at /lib64/libQt5Core.so.5 #17 0x7f81dec08813 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #18 0x7f814e3091dd in Konsole::TerminalDisplay::~TerminalDisplay() () at /lib64/libkonsoleprivate.so.21 #19 0x7f81ddf3a78a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #20 0x7f81dec08556 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #21 0x7f814e2ad6f5 in Konsole::ViewSplitter::~ViewSplitter() () at /lib64/libkonsoleprivate.so.21 #22 0x7f81ddf3a78a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #23 0x7f81dec08556 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #24 0x7f81ded8588d in QStackedWidget::~QStackedWidget() () at /lib64/libQt5Widgets.so.5 #25 0x7f81ddf3a78a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #26 0x7f81dec08556 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #27 0x7f814e3239dd in Konsole::TabbedViewContainer::~TabbedViewContainer() () at /lib64/libkonsoleprivate.so.21 #28 0x7f81dc1420b7 in KParts::Part::~Part() () at /lib64/libKF5Parts.so.5 #29 0x7f817802f11c in Konsole::Part::~Part() () at /usr/lib64/qt5/plugins/konsolepart.so #30 0x7f81ddf3a78a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #31 0x7f81dec08556 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #32 0x7f8178044ee0 in KDevKonsoleView::~KDevKonsoleView() () at /usr/lib64/qt5/plugins/kdevplatform/34/kdevkonsoleview.so #33 0x7f81ddf3a78a in QObjectPrivate::deleteChildren() () at /lib64/libQt5Core.so.5 #34 0x7f81dec08556 in QWidget::~QWidget() () at /lib64/libQt5Widgets.so.5 #35 0x7f81dc534900 in Sublime::IdealController::removeView(Sublime::View*, bool) () at /lib64/libKDevPlatformSublime.so.56 #36 0x7f81dc534a2c in Sublime::MainWindowPrivate::aboutToRemoveToolView(Sublime::View*, Sublime::Position) () at /lib64/libKDevPlatformSublime.so.56 #37 0x7f81ddf453a9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #38 0x7f81dc515aa4 in Sublime::Area::aboutToRemoveToolView(Sublime::View*, Sublime::Position) () at /lib64/libKDevPlatformSublime.so.56 #39 0x7f81dc51cbfc in Sublime::Area::removeToolView(Sublime::View*) () at /lib64/libKDevPlatformSublime.so.56 #40 0x7f81df7cf13b in KDevelop::UiController::removeToolView(KDevelop::IToolViewFactory*) () at /lib64/libKDevPlatformShell.so.56 #41 0x7f81df7c4fff in KDevelop::PluginController::unloadPlugin(KDevelop::IPlugin*, KDevelop::PluginController::PluginDeletion) () at /lib64/libKDevPlatformShell.so.56 #42 0x7f81df7c5412 in
[frameworks-kio] [Bug 430894] Confirmation prompt displayed every time a file is opened on a NextCloud webdav share
https://bugs.kde.org/show_bug.cgi?id=430894 --- Comment #6 from Rick Kerkhof --- This also happens on my system, with the addition that every time I open the account in Dolphin I am greeted with the same warning (I do not have to open a file). Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.12-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 430894] Confirmation prompt displayed every time a file is opened on a NextCloud webdav share
https://bugs.kde.org/show_bug.cgi?id=430894 Rick Kerkhof changed: What|Removed |Added CC||r...@nanosector.nl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 272539] WISH: Instant preview like OSX Snow Leopard
https://bugs.kde.org/show_bug.cgi?id=272539 Rick Kerkhof changed: What|Removed |Added CC||r...@nanosector.nl -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 330472] ownCloud News App support
https://bugs.kde.org/show_bug.cgi?id=330472 Rick Kerkhof changed: What|Removed |Added CC||r...@nanosector.nl -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 441011] New: Strange wording on the bluetooth file sharing dialog; "Back" instead of Cancel et al
https://bugs.kde.org/show_bug.cgi?id=441011 Bug ID: 441011 Summary: Strange wording on the bluetooth file sharing dialog; "Back" instead of Cancel et al Product: dolphin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: r...@nanosector.nl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140753 --> https://bugs.kde.org/attachment.cgi?id=140753=edit The dialog in question SUMMARY The bluetooth file sharing dialog (right-click a file, Share -> Share via Bluetooth) has strange wording on the dialog's actions. The bottom two options are Run and Back, neither of which makes sense in this context. Run does not make sense because what are you supposed to "run"? An action like "Share with device" would make more sense here, as you are supposed to select a device to share with in the context of this window. Back does not make sense because the window is separate from the main Dolphin context. I have assumed this is named the way it is because of mobile file sharing being more common, but "Cancel" seems more appropriate in either scenario. STEPS TO REPRODUCE 1. Right-click a file 2. From the Share menu, select Share via Bluetooth 3. Observe the dialog wording OBSERVED RESULT The wording on the action buttons does not make sense in the context. EXPECTED RESULT The wording on the action buttons should make sense in the context. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.9-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441010] New: Plasma breaks system locale when a locale which is not supported by the system is selected
https://bugs.kde.org/show_bug.cgi?id=441010 Bug ID: 441010 Summary: Plasma breaks system locale when a locale which is not supported by the system is selected Product: plasmashell Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: r...@nanosector.nl CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 140752 --> https://bugs.kde.org/attachment.cgi?id=140752=edit An example of a locale configured while the system does not support it SUMMARY I could not find a dedicated Bugzilla project for plasma-workspace, so I filed it here; I'm sorry if this is incorrect. Plasma lists *all* locales in its Formats KCM (System Settings -> Regional Settings -> Formats), even ones which are not supported by the underlying system, unlike the Language KCM. Setting one of these unsupported locales breaks some software which relies on proper locale configuration and causes warnings in others. For example, Minecraft's launcher no longer launches and crashes, and DNF throws warnings. STEPS TO REPRODUCE 1. Open the Formats KCM; 2. Set an unsupported locale by your system, for example nl_EN; 3. Restart your session and observe application behaviour. OBSERVED RESULT The Minecraft launcher breaks and DNF and other programs throw locale errors. > Failed to set locale, defaulting to C.UTF-8 EXPECTED RESULT Plasma should not break the locale settings the way it currently does and all programs should continue working. SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.13.9-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz Memory: 15,4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 ADDITIONAL INFORMATION >From what I could find in the repos, the Formats KCM relies on the output of QLocale::matchingLocales: https://invent.kde.org/plasma/plasma-workspace/-/blob/master/kcms/formats/kcmformats.cpp#L72 This method, https://doc.qt.io/qt-5/qlocale.html#matchingLocales , in turn relies on a list of locale data built in to Qt: https://github.com/qt/qtbase/blob/dev/src/corelib/text/qlocale_data_p.h#L79-L88 A possible solution therefore would be to filter the list given by Qt on locales known by the system. On top of this, Plasma itself seems to not have any issues with the locale and seems to honour it quite well. So another thought would be to set the system locale to C.UTF-8 or something similar if the selected locale is not supported, and maybe show a warning to the user? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439294] Kdenlive will crash at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=439294 --- Comment #6 from M-Rick --- If you can get it building, I can write the daemon file if you need it to. I don't know yet this MacPackager python script. I'll give it a look. I used to build Gnumeric under MacOS previously. I did it with Glom as well. http://macbidouille.com/news/2016/08/18/gnumeric-sous-os-x http://gnome-apps.13852.n7.nabble.com/Gnumeric-on-Mac-OS-X-td68552.html And I created the very first MacOS version of Inkscape years ago. https://forum.macbidouille.com/index.php?showtopic=68=Inkscape -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439294] Kdenlive will crash at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=439294 --- Comment #4 from M-Rick --- Created attachment 139742 --> https://bugs.kde.org/attachment.cgi?id=139742=edit Example of startup deamon file -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439294] Kdenlive will crash at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=439294 --- Comment #3 from M-Rick --- It's because the DMG is a disk image such as an ISO. But in order to launch a deamon like D-Bus, you cannot launch it directly from a single drag-and-drop install. Mac applications are packages like Appimages in Linux. So to launch a deamon it's better to create a pkg that can embed shell scripts. https://en.wikipedia.org/wiki/Package_(macOS) https://en.wikipedia.org/wiki/Installer_(macOS) But KDE apps really integrate well in the MacOS environment. The Damon must be launch by an XML startup file that'll be place in ~/Libray/LaunchAgents An example in attachement with Multipass. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439294] Kdenlive will crash at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=439294 --- Comment #1 from M-Rick --- Created attachment 139736 --> https://bugs.kde.org/attachment.cgi?id=139736=edit Crash log -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439294] New: Kdenlive will crash at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=439294 Bug ID: 439294 Summary: Kdenlive will crash at startup on MacOS Product: kdenlive Version: git-master Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- Created attachment 139735 --> https://bugs.kde.org/attachment.cgi?id=139735=edit Frameworks directory without any of the necessary Qt libraries Kdenlive will crash at startup on MacOS. All the necessary Qt libraries are missing in the packaged application. https://binary-factory.kde.org/view/MacOS/job/Kdenlive_Nightly_macos/lastSuccessfulBuild/ You should give a look at QGIS Mac that embed most of the necessary Qt libraries. https://github.com/qgis/QGIS-Mac-Packager SOFTWARE/OS VERSIONS macOS: 10.14.6 Qt Version: 5.x -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 428942] KDevelop crashes at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=428942 --- Comment #1 from M-Rick --- It's missing some Qt libraries. That's why it will crash at startup. You should give a look at QGIS Mac that embed most of the Qt libraries necessary. https://github.com/qgis/QGIS-Mac-Packager -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 428512] Kate for MacOS is not localised
https://bugs.kde.org/show_bug.cgi?id=428512 M-Rick changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from M-Rick --- It has been fixed in last versions. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 --- Comment #7 from Rick Wagner --- Yes, I use network manager. This is on Fedora 33, Plasma 5.20.5. nmcli shows one physical (wired) connection: $ nmcli device DEVICE TYPE STATE CONNECTION enp5s0 ethernet connected Wired connection 1 docker0 bridgeconnected (externally) docker0 br-88e9fca1b449 bridgeconnected (externally) br-88e9fca1b449 virbr0 bridgeconnected (externally) virbr0 knemo is able to show statistics for the enp5s0 device, but Network System Monitor shows no devices. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 433258] Network system monitor doesn't work for network bridges
https://bugs.kde.org/show_bug.cgi?id=433258 Rick Wagner changed: What|Removed |Added CC||rjwgn...@gmail.com --- Comment #4 from Rick Wagner --- I see this also for non-bridge devices on Plasma 5.20.5 (Fedora 33). Network monitor shows no textual or graphic transfer rates. $ ifconfig enp5s0: flags=4163 mtu 1500 inet 192.168.1.30 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::af0c::: prefixlen 64 scopeid 0x20 ether xx txqueuelen 1000 (Ethernet) $ solid-hardware5 nonportableinfo '/org/kde/solid/udev/.../net/enp5s0' udi = '/org/kde/solid/udev/sys/devices/pci:00/:00:01.3/:02:00.2/:03:01.0/:05:00.0/net/enp5s0' DEVPATH = '/devices/pci:00/:00:01.3/:02:00.2/:03:01.0/:05:00.0/net/enp5s0' (string) ID_BUS = 'pci' (string) ID_MM_CANDIDATE = '1' (string) ID_MODEL_FROM_DATABASE = 'I211 Gigabit Network Connection' (string) ID_MODEL_ID = '0x1539' (string) ID_NET_DRIVER = 'igb' (string) ID_NET_LINK_FILE = '/usr/lib/systemd/network/99-default.link' (string) ID_NET_NAME_MAC = 'enx7085cxx' (string) ID_NET_NAME_PATH = 'enp5s0' (string) ID_NET_NAMING_SCHEME = 'v245' (string) ID_OUI_FROM_DATABASE = 'ASRock Incorporation' (string) ID_PATH = 'pci-:05:00.0' (string) ID_PATH_TAG = 'pci-_05_00_0' (string) ID_PCI_CLASS_FROM_DATABASE = 'Network controller' (string) ID_PCI_SUBCLASS_FROM_DATABASE = 'Ethernet controller' (string) ID_VENDOR_FROM_DATABASE = 'Intel Corporation' (string) ID_VENDOR_ID = '0x8086' (string) IFINDEX = '2' (string) INTERFACE = 'enp5s0' (string) SUBSYSTEM = 'net' (string) SYSTEMD_ALIAS = '/sys/subsystem/net/devices/enp5s0' (string) TAGS = ':systemd:' (string) USEC_INITIALIZED = '7198612' (string) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #40 from Rick --- (In reply to David Edmundson from comment #38) > hypothetically are you able to build your own kwin if I provided some > patches? Yes I could. I'd like to help solve this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #39 from Rick --- (In reply to David Edmundson from comment #37) > That attached file doesn't look like the output of "xkbcli interactive-x11" > it looks like a stack trace. Is it the right file? Apologies. Here is the output: keysyms [ Super_L ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layout [ English (US) (0) ] level [ 0 ] mods [ ] leds [ ] keysyms [ XF86WakeUp ] unicode [ ] layo
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #36 from Rick --- All that typing gone when I attached that file! On a fresh restart, I ran 'dbus-monitor' from the terminal and streamed the output to kate. I grepped for 'member=activateLauncherMenu'. There were no hits. I launched kicker successfully and there was 1 hit. I closed the lid and activated the bug. I grepped again but got no new hits. The hit total stands at 1. I restarted my machine because I can 100% reproduce the bug on the first time. I setup my gdb and then ran 'xkbcli interactive-x11'. I pressed meta and then clicked on the desktop to close the menu. Then I launched kicker again, and with the menu open, I closed the lid. The bug activated. I restarted my pc to post the results and the log file (kwin.dbg). I'm happy to assist further. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #35 from Rick --- Created attachment 133912 --> https://bugs.kde.org/attachment.cgi?id=133912=edit logs for xkbcli interactive-x11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #32 from Rick --- The binding always breaks after first suspend. I pressed *alt+shift+f12* and the screen blinked. I then closed the lid and the binding broke. I restored with *kwin_x11 --replace & disown*. I restarted my machine for the next test because after I restore, I can't reliably reproduce the problem by closing the lid - it becomes random. But when I freshly login and close the lid I can break it 100% of the time. When I logged in after the restart, I entered *sudo udevadm trigger -s input* into the console It didn't trigger the meta key binding breakage. I then closed my laptop lid and I triggered the meta key binding breakage. On Wed, Nov 25, 2020 at 11:14 PM David Edmundson wrote: > https://bugs.kde.org/show_bug.cgi?id=391322 > > --- Comment #31 from David Edmundson --- > Could you also see if: > > sudo udevadm trigger -s input > > reliably triggers it? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You voted for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391322] Meta key randomly stops opening Plasma launcher menu
https://bugs.kde.org/show_bug.cgi?id=391322 --- Comment #29 from Rick --- KWin stops working when I close my laptop lid. My power options are set to "do nothing". When I open the lid, the meta key has lost its binding. I started my pc and opened a terninal. I entered echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope gdb -pid $(pidof kwin_x11) -batch -ex "set logging file kwin.gdb" -ex "set logging on" -ex "continue" -ex "thread apply all backtrace" -ex "quit" and closed the lid. The meta key lost its binding. Then I opened another terminal and entered win_x11 --replace & disown to restore functionality. Below is the stacktrace from kwin.gdb. I hope it helps. Thread 1 "kwin_x11" received signal SIGINT, Interrupt. 0x7fe0da57156e in ppoll () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7fe0ce58e640 (LWP 51981) "QSGRenderThread"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0da9220d4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5 #2 0x7fe0d96d52fb in () at /usr/lib/libQt5Quick.so.5 #3 0x7fe0d96d789b in () at /usr/lib/libQt5Quick.so.5 #4 0x7fe0da91be8f in () at /usr/lib/libQt5Core.so.5 #5 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 9 (Thread 0x7fe0cc850640 (LWP 34522) "kwin_x11"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0da26afee in () at /usr/lib/libQt5Script.so.5 #2 0x7fe0da26b019 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 8 (Thread 0x7fe0bcbf8640 (LWP 34477) "kwin_x1:disk$3"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fe0bd3f9640 (LWP 34476) "kwin_x1:disk$2"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fe0bdbfa640 (LWP 34475) "kwin_x1:disk$1"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fe0be3fb640 (LWP 34474) "kwin_x1:disk$0"): #0 0x7fe0d9ddc6a2 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe0beced8dc in () at /usr/lib/dri/iris_dri.so #2 0x7fe0beced7d8 in () at /usr/lib/dri/iris_dri.so #3 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe0cdabc640 (LWP 34410) "QQmlThread"): #0 0x7fe0da57156e in ppoll () at /usr/lib/libc.so.6 #1 0x7fe0dab568ab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe0dab57fed in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe0dab0065c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe0da91aca2 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe0d938c4b9 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe0da91be8f in () at /usr/lib/libQt5Core.so.5 #7 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe0cf79f640 (LWP 34353) "QDBusConnection"): #0 0x7fe0da57156e in ppoll () at /usr/lib/libc.so.6 #1 0x7fe0dab568ab in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe0dab57fed in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe0dab0065c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe0da91aca2 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe0dbc05098 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fe0da91be8f in () at /usr/lib/libQt5Core.so.5 #7 0x7fe0d9dd63e9 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe0da57c293 in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe0d4a99640 (LWP 3433
[konversation] [Bug 429378] New: sysinfo
https://bugs.kde.org/show_bug.cgi?id=429378 Bug ID: 429378 Summary: sysinfo Product: konversation Version: 1.7.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: sambora1...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. sysinfo does not work if using linux 19 or 20.04 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.
[kdevelop] [Bug 428942] New: KDevelop crashes at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=428942 Bug ID: 428942 Summary: KDevelop crashes at startup on MacOS Product: kdevelop Version: 5.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: All build tools Assignee: kdevelop-bugs-n...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- Created attachment 133209 --> https://bugs.kde.org/attachment.cgi?id=133209=edit Crash log KDevelop crashes at startup on MacOS. I tried on both BigSur and Mojave. KDevelop won't work on none of them. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 428512] New: Kate for MacOS is not localised
https://bugs.kde.org/show_bug.cgi?id=428512 Bug ID: 428512 Summary: Kate for MacOS is not localised Product: kate Version: 20.08.1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- Created attachment 132916 --> https://bugs.kde.org/attachment.cgi?id=132916=edit Language settings window SUMMARY Kate for MacOS it not localised. STEPS TO REPRODUCE Install and launch Kate on MacOS. Open Settings > Configure Language In the menu, only American English is available in the list. SOFTWARE/OS VERSIONS macOS: macOS 10.14.6 (18G4032) aka Mojave Kate: Version 20.08.1 KDE Frameworks: 5.74.0 Qt: 5.15.1 (built against 5.15.1) The cocoa windowing system -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 428511] New: KMyMoney for MacOS is not localised
https://bugs.kde.org/show_bug.cgi?id=428511 Bug ID: 428511 Summary: KMyMoney for MacOS is not localised Product: kmymoney Version: 5.1.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: translation Assignee: kmymoney-de...@kde.org Reporter: m.rick@gmail.com Target Milestone: --- Created attachment 132915 --> https://bugs.kde.org/attachment.cgi?id=132915=edit Language settings window SUMMARY KMyMoney for MacOS it not localised. STEPS TO REPRODUCE Install and launch KMyMoney on MacOS. Open Help > Switch Application Language In the menu, only American English is available in the list. SOFTWARE/OS VERSIONS macOS: macOS 10.14.6 (18G4032) aka Mojave KMyMoney: Version 5.1.0-df4451f17 KDE Frameworks: 5.71.0 Qt: 5.15.0 (built against 5.15.0) The cocoa windowing system -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 Rick Stockton changed: What|Removed |Added Assignee|rickstockton@reno-computerh |plasma-b...@kde.org |elp.com | --- Comment #47 from Rick Stockton --- (removed myself as assignee) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #46 from Rick Stockton --- (In reply to Nate Graham from comment #41) > > Even if there's no explicit Qt support (is this still true?) we could still > implement it ourselves on the KDE side. I should note that Qt support is explicitly "good" for X11, and Wayland seems ready for up to 16 buttons. The reasons why I should no longer be the assignee are (1) the fact that I am unqualified to make the 'visionary' choices: which buttons should default to which actions; and (2) the glue which must hold it together (clicks -> signals and slots for "actions") and (3) making coherent updates for all of the programs which should perhaps make use of higher-numbered buttons. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 34362] Support for configuring additional mouse buttons
https://bugs.kde.org/show_bug.cgi?id=34362 --- Comment #45 from Rick Stockton --- (In reply to Nate Graham from comment #41) > Re-opening since this is a reasonable request. Binding shortcuts/actions to > additional mouse buttons seems reasonable. > > Even if there's no explicit Qt support (is this still true?) we could still > implement it ourselves on the KDE side. I'm not much of a programmer. It seems that KGlobalAccel would need some new member function signatures, creating a bit of a mess for backward compatibility. Or, would it be better to create an entire new class for "KGlobalMouseAccel" ? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 424656] Uninitialised value was created by a heap allocation
https://bugs.kde.org/show_bug.cgi?id=424656 --- Comment #2 from Rick Stanley --- Is there a way to suppress a valgrind warning in the code for specific lines and/or functions by setting/un-setting a variable or using comment lines? If not then there should be. In the real code I am writing, I want to simply display in hex the values of each byte of an allocation irregardless of all the bytes being initialized or not. Thank you! On Sat, 2020-07-25 at 15:11 +, Philippe Waroquiers wrote: > https://bugs.kde.org/show_bug.cgi?id=424656 > > Philippe Waroquiers changed: > >What|Removed |Added > --- > - > CC| > |philippe.waroquiers@skynet. >||be > > --- Comment #1 from Philippe Waroquiers < > philippe.waroqui...@skynet.be> --- > That looks like a real bug that valgrind detects. > > The malloc allocates 32 bytes, the strcpy initialises 16 bytes > but the printf loop prints the 32 bytes, so effectively prints data > nopt > initialised. > -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 424656] New: Uninitialised value was created by a heap allocation
https://bugs.kde.org/show_bug.cgi?id=424656
Bug ID: 424656
Summary: Uninitialised value was created by a heap allocation
Product: valgrind
Version: unspecified
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: rstan...@rsiny.com
Target Milestone: ---
SUMMARY
Possible incorrect errors using the source below. Occurs with gcc-8, gcc-9,
gcc-10 on Debian Testing, "valgrind-3.16.1"
STEPS TO REPRODUCE
1. Source:
#include
#include
#include
#define DIM 32
int main(void)
{
char *p = NULL;
p = malloc(DIM);
if(p == NULL)
{
printf("Allocation error.\n");
exit(1);
}
strcpy(p, "This is a test.");
for(int x = 0 ; x < DIM; ++x)
{
printf("%02x ", p[x]);
}
putchar('\n');
free(p);
return 0;
}
2. "gcc -std=c18 -Wall -Wextra -Wpedantic -g -I . -o ptest ptest.c"
3. "valgrind -s --track-origins=yes ./ptest"
OBSERVED RESULT
==11539== Use of uninitialised value of size 8
==11539==at 0x48B4E5A: _itoa_word (_itoa.c:180)
==11539==by 0x48CE753: __vfprintf_internal (vfprintf-internal.c:1687)
==11539==by 0x48BAD6A: printf (printf.c:33)
==11539==by 0x10920D: main (ptest.c:33)
==11539== Uninitialised value was created by a heap allocation
==11539==at 0x483877F: malloc (vg_replace_malloc.c:307)
==11539==by 0x10919E: main (ptest.c:21)
==11539==
...
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.
[frameworks-kconfigwidgets] [Bug 423302] New: Document in API for KRecentFilesAction::addAction that temp files are ignored
https://bugs.kde.org/show_bug.cgi?id=423302
Bug ID: 423302
Summary: Document in API for KRecentFilesAction::addAction that
temp files are ignored
Product: frameworks-kconfigwidgets
Version: 5.70.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: rjwgn...@gmail.com
Target Milestone: ---
SUMMARY
Developing an app which uses KRecentFilesAction, I did my debug testing storing
a file in /tmp/xxx.json, where added it to a KRecentFilesAction, using
addUrl(). When I went to the associated "Open Recent..." menu entry, and found
it greyed out. Spent hours looking at the creation of the action (through
KXmlGuiClien::actionCollection()->addAction() and other permutations). Finally
looked at the source for KRecentFilesAction::addAction() and found where the
code quietly discards files in the temp directory:
if (url.isLocalFile() && url.toLocalFile().startsWith(QDir::tempPath())) {
return;
}
While this makes some sense, "favors" done by the code should be documented.
Some note to this effect should be in the API for the widget.
STEPS TO REPRODUCE
1. create an app using a KRecentFilesAction action
2. add a QUrl to a local file stored in the temp path
3. wonder why it does not show up in the recent files list
OBSERVED RESULT
1. File mysteriously does not show up in the recents list
EXPECTED RESULT
1. It should not be a mystery, as behavior should be documented.
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.
[elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830 Rick changed: What|Removed |Added CC|rickjcar...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 416830] Elisa crashes on start Kubuntu 20.04
https://bugs.kde.org/show_bug.cgi?id=416830 Rick changed: What|Removed |Added CC||rickjcar...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 419951] dh_view.html missing
https://bugs.kde.org/show_bug.cgi?id=419951 Rick Stanley changed: What|Removed |Added CC||rstan...@rsiny.com -- You are receiving this mail because: You are watching all bug changes.
