[systemsettings] [Bug 347070] Moving the 'Drag me' icon provokes a crash
https://bugs.kde.org/show_bug.cgi?id=347070 gary changed: What|Removed |Added CC||garybambro...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 444097] New: Custom "Create Folder" shortcut doesn't work within application file dialogs
https://bugs.kde.org/show_bug.cgi?id=444097 Bug ID: 444097 Summary: Custom "Create Folder" shortcut doesn't work within application file dialogs Product: dolphin Version: 21.08.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: gvcal...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I have assigned a custom assigned keyboard shortcut to create a new folder (Ctrl + Shift + N in my case). It works perfectly if I open a standalone Dolphin window. However, when another application (such as Google Chrome) opens up Dolphin itself (e.g. in order to choose where to save a file) then my custom shortcut does not work, but the default "F10" does work. STEPS TO REPRODUCE 1. Assign a custom keyboard shortcut to the "Create Folder" command from within Dolphin 2. Open an external application which provides some interface to save a file (in this example, Google Chrome) 3. Opt to save a file to a specific location (in Chrome, right click on web page > Save As...) 4. Test custom shortcut OBSERVED RESULT The command to create a new folder is not fired EXPECTED RESULT The command should fire as expected SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It should be noted that in some older applications, an older file dialog appears. This is the case for me and Firefox. With these older dialogs, neither F10 nor the custom shortcut work. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 424826] New: Krusader Mint 19.3 root mode login fails
https://bugs.kde.org/show_bug.cgi?id=424826 Bug ID: 424826 Summary: Krusader Mint 19.3 root mode login fails Product: krusader Version: 2.6.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: gh...@mail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY Krusader Mint 19.3 root mode login fails to login with correct password. 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.
[krusader] [Bug 424826] Krusader Mint 19.3 root mode login fails
https://bugs.kde.org/show_bug.cgi?id=424826 --- Comment #1 from Gary --- OS = Linux Mint 19.3 Cinnamon x64 bit. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474600] New: Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=474600 Bug ID: 474600 Summary: Dolphin crashed Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: garyt...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.4.0-4-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: I had 2 instances of Dolphin open with 2 or 3 tabs in each one. The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #7 0x7f97ec1d7611 in KCoreConfigSkeleton::load() () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 [...] #9 0x7f97ec1af8f7 in KConfigWatcher::configChanged(KConfigGroup const&, QList const&) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 [...] #11 0x7f97ec1afc62 in KConfigWatcher::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libKF5ConfigCore.so.5 [...] #13 0x7f97eaeef400 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f97ebb62d2e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474600] Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=474600 --- Comment #1 from Gary --- Created attachment 161661 --> https://bugs.kde.org/attachment.cgi?id=161661&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463940] Unable to launch digikam 7.9.0 on macOS 10.14.6 (Mojave)
https://bugs.kde.org/show_bug.cgi?id=463940 Gary changed: What|Removed |Added CC||gazol...@iinet.net.au --- Comment #3 from Gary --- Created attachment 155274 --> https://bugs.kde.org/attachment.cgi?id=155274&action=edit Header of crash report at digikam 7.9.0 launch (repeatable) I had the same issue as Tim - Unable to launch digikam 7.9.0 on macOS 10.14.6 (Mojave). My setup: iMac 5K 2017 (18,3) 3.4GHz i5, MacOS 10.14.6, 16GB RAM, Radeon Pro 570 4GB. Images are stored on my local network. The problem persisted despite adding access rights in the macOS Security and Privacy Panel Ref. https://docs.digikam.org/en/getting_started/installation.html#application-rights My workaround was uninstalling 7.9.0 (using AppCleaner 3.6.7 app), rebooting and re-installing digikam 7.8.0. It appears that Files and Folders Access Rights don't exist in the macOS Security and Privacy Panel before 10.15 (Catalina). Ref. https://support.apple.com/en-au/guide/mac-help/mchld5a35146/mac Tim & Gilles, hope this helps (this is my first bug report here). There might be some other issue that I'm missing. Regards, Gary -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 249759] data cd copy fails
https://bugs.kde.org/show_bug.cgi?id=249759 Gary changed: What|Removed |Added CC||leti2...@ckt.net --- Comment #4 from Gary --- When trying to copy a CD with maybe 100 mb info, it copies and then when it writes it gets only part way through and stops dead. What am I doing wrong?? The CD has family pixs on it---have tried numerous times. Can burn pixs OK onto a CD but the "Copy" function has quit in the last month---maybe from an update?? Am using Ubuntu 20.4.3lts for OS. Have tried the copy function on a Microsoft Windows machine and that works. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 424826] Krusader Mint 19.3 root mode login fails
https://bugs.kde.org/show_bug.cgi?id=424826 --- Comment #3 from Gary --- Install of kdesu packages did NOT add a link in /usr/bin pointing to kdesu. Added symbolic link to /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu in /usr/bin "start root mode" in krusader now works ok. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 426296] New: Astropy Install Failure
https://bugs.kde.org/show_bug.cgi?id=426296 Bug ID: 426296 Summary: Astropy Install Failure Product: kstars Version: 3.4.3 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: gary.jo...@bigpond.com Target Milestone: --- SUMMARY Polar Alignment and Plate Solving Work Initially, then fail STEPS TO REPRODUCE 1. Run in Simulator mode 2. Try to run Polar Alignment or Plate-Solving 3. Tested using Online & Offline Solver OBSERVED RESULT Error message : Python 3 and Astropy not installed. EXPECTED RESULT PA and Plate solving work as expected - no error message SOFTWARE/OS VERSIONS macOS: 10.14.6 ADDITIONAL INFORMATION When running'Options .../Astronomy.net/Setup':- - Homebrew installed - Python3 installed - Astropy will install when you click Ok But when I press OK I get the message 'Astropy install failure'. I have run the manual installer using Terminal : pip3 install astropy That seemed to work. PA seemed to work OK (on the simulator) the first time. Subsequent attempts did not work. I reinstalled OSX (for other reasons) and tried again. PA and plate solving worked OK - but only the FIRST TIE. Subsequent attempts failed. Attempting to re-install Astropy using 'pip3 install astropy' gives this message :- Requirement already satisfied: astropy in /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages (4.0.1.post1) Requirement already satisfied: numpy>=1.16 in /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages (from astropy) (1.19.1) Restarting KStars then trying to do a PA online, KStars seems to TRY to connect to astronomy.net to solve the first image :- "Upload complete. Waiting for astrometry.net solver to complete..." But it never completes - spinning wheel adjacent to "Stop" button just keeps spinning. After several minutes, the responder says 'Solver timed out', but the icon next to the 'Stop' button keeps spinning and KStars appears to keep waiting. If I stop the process and try again offline, I get this message :- "Astrometry.net uses python3 and the astropy package for plate solving images offline. These were not detected on your system." Same if I try again using Online. So there appears to be an issue with the way KStars accesses the resources needed to run Solver. Gary -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 426296] Astropy Install Failure
https://bugs.kde.org/show_bug.cgi?id=426296 --- Comment #2 from Gary --- Hi Jasem Many thanks for your speedy reply. OK - I tried Sextractor - it worked ... 1. OFFline 2. ONline Interestingly … Python worked the first time I attempted a plate-solve after booting up, but failed on the second attempt. So - a couple of questions :- 1. Why does Python work sometimes, but not others - do I have issues with my installation ? 2. What is the difference between using Python vs Sextractor ? Ive spent a lot of time researching but cant find anything that explains this. They each seem to interface to Astro.net <http://astro.net/> / ASTAP, or use offline data ? Ekos does a nice job of image capture … Do you have plans for Ekos to do image stacking as well ? Best regards, Gary = > On 08 Sep 2020, at 21:37, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=426296 > > --- Comment #1 from Jasem Mutlaq --- > No need to use Python in the latest KStars release, you can configure Align > settings to use sextractor instead. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 424826] Krusader Mint 19.3 root mode login fails
https://bugs.kde.org/show_bug.cgi?id=424826 --- Comment #8 from Gary --- When I try either command I get an error. $ kdesu -c KDE_FULL_SESSION=true krusader qt5ct: using qt5ct plugin org.kde.kdesu: Daemon not safe (not sgid), not using it. When I try to click on the "start root mode" in the Krusader/Tool menu, it fails to accept the password. If I execute "sudo kdesu krusader" then it starts root mode krusdaer. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 426296] Astropy Install Failure
https://bugs.kde.org/show_bug.cgi?id=426296 --- Comment #4 from Gary --- Thanks Jasem, Ok - so 3 questions for you :- 1. When do you expect the next release of Ekos ? 2. Is there a way to run Ekos without using KStars ? I use a different planetarium pp - but prefer Ekos for scope control and image capture 3. Do you have plans for Ekos to do image stacking as well ? Gary = > On 10 Sep 2020, at 07:37, Jasem Mutlaq wrote: > > https://bugs.kde.org/show_bug.cgi?id=426296 > > --- Comment #3 from Jasem Mutlaq --- > We are in the process of removing them actually. There would be no python in > the next KStars release hopefully if all goes well. So you don't have to worry > about sextractor/python again. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 430785] New: The legend shows symbols, but no labels
https://bugs.kde.org/show_bug.cgi?id=430785 Bug ID: 430785 Summary: The legend shows symbols, but no labels Product: LabPlot2 Version: 2.8.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: frontend Assignee: alexander.se...@web.de Reporter: gzai...@gmail.com Target Milestone: --- Created attachment 134308 --> https://bugs.kde.org/attachment.cgi?id=134308&action=edit No legend text SUMMARY Adding legend shows rectangle with the symbols. But, no text is visible 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.
[LabPlot2] [Bug 430785] The legend shows symbols, but no labels
https://bugs.kde.org/show_bug.cgi?id=430785 --- Comment #2 from Gary --- Created attachment 134309 --> https://bugs.kde.org/attachment.cgi?id=134309&action=edit Labplot legend bug- The project file -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 430785] The legend shows symbols, but no labels
https://bugs.kde.org/show_bug.cgi?id=430785 --- Comment #4 from Gary --- oops... Thanks! On Thu, 24 Dec 2020 at 15:41, Alexander Semke wrote: > https://bugs.kde.org/show_bug.cgi?id=430785 > > --- Comment #3 from Alexander Semke --- > (In reply to Gary from comment #2) > > Created attachment 134309 [details] > > Labplot legend bug- The project file > > the font color is set to white in the legend with a white background color. > This is the reason for why you don't see anything. Just set the font color > to > another color and you'll see the names of your curves. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 413753] New: Firewalld will not start.
https://bugs.kde.org/show_bug.cgi?id=413753 Bug ID: 413753 Summary: Firewalld will not start. Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gh...@mail.com Target Milestone: --- SUMMARY Upgrade Kubuntu 18.10 to 19.04 and Firewalld will not start. If you do a new install of Kubuntu 19.04, then it works ok. STEPS TO REPRODUCE 1. Upgrade Kubuntu 18.10 to 19.04 2. systemctl status firewalld will display WARNING: iptables-restore and iptables are missing, disabling IPv4 firewall. FATAL ERROR no IPv4 or IPv6 firewall. 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.
[Discover] [Bug 406632] New: Feature request for Discover
https://bugs.kde.org/show_bug.cgi?id=406632 Bug ID: 406632 Summary: Feature request for Discover Product: Discover Version: 5.13.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: gh...@mail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Please add a Feature that allows the user to specify when the Discover tool should run. 1) During PC Boot, my VPN is trying to establish a connection, but the Discover tool interferes as it is trying to find updates. 2) Sometimes while I am trying to login to a web site, the Discover tool interferes as it is trying to find updates. Please allow the user to establish a time for the Discover tool to run, instead of the current forced interference. Thanks, looking forward to a fix. Kubuntu 18.10 Discover 5.13.5 X64 bit OS -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406632] Feature request for Discover
https://bugs.kde.org/show_bug.cgi?id=406632 --- Comment #2 from Gary --- 1) Discover prevents VPN from making initial connection. 2) Discover prevents login from working. User should be able to control when Discover runs. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406632] Feature request for Discover
https://bugs.kde.org/show_bug.cgi?id=406632 --- Comment #4 from Gary --- The Discover Icon is on the task bar, usually blinking, when the conflict happens. When Discover is not active, there is no conflict and everything works ok. Please add a feature that allows the user to define when Discover should run. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 406632] Feature request for Discover
https://bugs.kde.org/show_bug.cgi?id=406632 --- Comment #6 from Gary --- FYI --- I have several PC's, with different CPU & Mobo, which are booted daily and I see the same conflict with Discover & other network usage. Please allow the user to establish when Discover runs. Personally, I would prefer to run it via a cron job prior to shutdown (at Logout). But others may prefer to run it at a set time, say at lunch time. In any case, please end the forced interference which prevents users from working, because they must yield their PC to forced updates. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 410587] New: Falcon Crashes when attempting to play HTML5 web video content
https://bugs.kde.org/show_bug.cgi?id=410587 Bug ID: 410587 Summary: Falcon Crashes when attempting to play HTML5 web video content Product: Falkon Version: 3.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: now...@gmail.com Reporter: gree...@kde.org Target Milestone: --- Application: falkon (3.1.0) Qt Version: 5.13.0 Frameworks Version: 5.60.0 Operating System: Linux 5.2.3-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I was starting to watch an episode of an anime on www.crunchyroll.com. App crashed when playback began. -- Backtrace: Application: Falkon (falkon), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc935456f40 (LWP 31216))] Thread 34 (Thread 0x7fc8eca90700 (LWP 31308)): #0 0x7fc93949b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc93ce1f6a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc93ce20073 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc93ce201f1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc93cdd84b1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc93cddb34d in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc93cddba44 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc93ce224e5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc939494faa in start_thread () at /lib64/libpthread.so.0 #9 0x7fc9432b273f in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fc8e5e24700 (LWP 31291)): #0 0x7fc93949ae05 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc93ce1f5ac in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc93ce20080 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc93ce201af in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc93cdd8486 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc93cddb34d in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc93cddba84 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc93ce224e5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc939494faa in start_thread () at /lib64/libpthread.so.0 #9 0x7fc9432b273f in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fc8e4ca3700 (LWP 31286)): #0 0x7fc93949b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc93ce1f6a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc93ce20073 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc93ce201f1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc93cdd84b1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc93cddb34d in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc93cddba44 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc93ce224e5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc939494faa in start_thread () at /lib64/libpthread.so.0 #9 0x7fc9432b273f in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fc8e54a4700 (LWP 31285)): #0 0x7fc93949b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc93ce1f6a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc93ce20073 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc93ce201f1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc93cdd84b1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc93cddb69b in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc93cddba44 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc93ce224e5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc939494faa in start_thread () at /lib64/libpthread.so.0 #9 0x7fc9432b273f in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7fc8e7b70700 (LWP 31283)): #0 0x7fc93949b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc93ce1f6a6 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fc93ce20073 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fc93ce201f1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fc93cdd84b1 in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fc93cddb69b in () at /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fc93cddba44 in () at /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fc93ce224e5 in () at /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7fc939494faa in start_thread () at /lib64/libpthread.so.0 #9 0x7fc9432b273f in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fc8e8371700 (LWP 31269)): #0 0x7fc93949b16c in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc9422e5f38 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/l
[Discover] [Bug 420901] New: Discover Startup
https://bugs.kde.org/show_bug.cgi?id=420901 Bug ID: 420901 Summary: Discover Startup Product: Discover Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: gh...@mail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Discover starts during PC startup and may crash if the network isn't ready. The user has no control of when Discover runs. Please add a menu item to Discover that allows the user to specify when Discover will run. I suggest a time of day choice, that way the user can start a VPN and run checks before Discover attempts access to the network. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415258] New: Kontact crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=415258 Bug ID: 415258 Summary: Kontact crashes shortly after startup Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gree...@kde.org Target Milestone: --- Application: kontact (5.13.0 (19.12.0)) Qt Version: 5.13.1 Frameworks Version: 5.64.0 Operating System: Linux 5.3.12-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: While reading/navigating through emails, kontact crashes within 20 to 30 seconds after launch of the application Currently running: kontact-19.12.0-110.1.x86_64 kontact-debugsource-19.12.0-110.1.x86_64 kontactinterface-lang-19.12.0-144.1.noarch kontact-debuginfo-19.12.0-110.1.x86_64 kontact-lang-19.12.0-110.1.noarch This is on openSUSE Tumbleweed with the KDE:Applications and KDE:Extra repos enabled The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5129db4a40 (LWP 7740))] Thread 42 (Thread 0x7f4fbadb3700 (LWP 7879)): #0 0x7f513b51fbdf in poll () from /lib64/libc.so.6 #1 0x7f513840a27e in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f513840a39f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f513a18e98b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f513a1370cb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f5139f6f021 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f5139f701a2 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #8 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 41 (Thread 0x7f4fd617c700 (LWP 7856)): #0 0x7f5138e6b9ca in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5132d9d516 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5132d9dee3 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5132d9e061 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5132d56191 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5132d5937b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5132d59724 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5132da0355 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 40 (Thread 0x7f4fd6c7d700 (LWP 7855)): #0 0x7f5138e6b6a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5125f28b8b in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f5125f28a37 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #4 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 39 (Thread 0x7f4fd77fe700 (LWP 7854)): #0 0x7f5138e6b6a5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f5132d9d41c in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f5132d9def0 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f5132d9e01f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f5132d56166 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f5132d5937b in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f5132d59764 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f5132da0355 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #8 0x7f5138e64f2a in start_thread () from /lib64/libpthread.so.0 #9 0x7f513b52a4af in clone () from /lib64/libc.so.6 Thread 38 (Thread 0x7f4fd7fff700 (LWP 7851)): #0 0x7f513b4b0ca7 in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7f513b498b0e in buffered_vfprintf () from /lib64/libc.so.6 #2 0x7f513b495a24 in __vfprintf_internal () from /lib64/libc.so.6 #3 0x7f513b53889f in __fprintf_chk () from /lib64/libc.so.6 #4 0x7f512e749f2e in event_logv_ () from /usr/lib64/libevent-2.1.so.7 #5 0x7f512e74cb15 in event_warn () from /usr/lib64/libevent-2.1.so.7 #6 0x7f512e74e678 in ?? () from /usr/lib64/libevent-2.1.so.7 #7 0x7f512e75f086 in event_base_loop () from /usr/lib64/libevent-2.1.so.7 #8 0x7f5132da41b8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #9 0x7f5132d302d7 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #10 0x7f5132d6749f in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #11 0x7f5132da0355 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5 #12 0x7f5138e64f2a in start_thread () from
[kontact] [Bug 415258] Kontact crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=415258 Gary L. Greene, Jr. changed: What|Removed |Added Version|unspecified |5.13.0 --- Comment #1 from Gary L. Greene, Jr. --- This crash is occuring every time kontact is started. I've had to resort to using the GMail webmail interface for now with reduced functionality I depend on from the PIM suite. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 415380] New: KMahjongg score sheet problem
https://bugs.kde.org/show_bug.cgi?id=415380 Bug ID: 415380 Summary: KMahjongg score sheet problem Product: kpat Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: co...@kde.org Reporter: la.bu...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 124608 --> https://bugs.kde.org/attachment.cgi?id=124608&action=edit kmahjong score sheet SUMMARY In the kMahjong game. Poor scoring, shown in attached screen capture. [7th] position score, by time is out, if scored by points it is out. Also it does not follow a mathematical sequence if time, it is 8th position not [7] if scored by points, it is 10th position not [7] STEPS TO REPRODUCE -nothing to reproduce, it is ongoing. 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux openSuse 15.1 /KDE Plasma: 5.12.8 (available in About System) KDE Plasma Version:5.12.8 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION KMahjongg version 18.12.3-lp151.1.2-x86_64 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415258] Kontact crashes shortly after startup
https://bugs.kde.org/show_bug.cgi?id=415258 Gary L. Greene, Jr. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #2 from Gary L. Greene, Jr. --- Disregard. This appears to be resolved with recent updates from Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420901] Discover Startup
https://bugs.kde.org/show_bug.cgi?id=420901 --- Comment #2 from Gary --- kdelibs5-dbg & discover-dbg not available in Kubuntu 20.04 Muon Package Manager. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420901] Discover Startup
https://bugs.kde.org/show_bug.cgi?id=420901 --- Comment #3 from Gary --- Created attachment 128283 --> https://bugs.kde.org/attachment.cgi?id=128283&action=edit Discover crash Screen shot of error message seen during PC startup. Please stop running Discover before the network is ready. User should be able to select a time for Discover to run !!! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421282] New: Discover Error Messges
https://bugs.kde.org/show_bug.cgi?id=421282 Bug ID: 421282 Summary: Discover Error Messges Product: Discover Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: fwupd Backend Assignee: sharma.abhijeet2...@gmail.com Reporter: gh...@mail.com CC: lei...@leinir.dk Target Milestone: --- SUMMARY When running Discover from command line, the following error messages are displayed: qrc:/qml/Feedback.qml:2:1: module "org.kde.userfeedback" is not installed invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation". adding empty sources model QStandardItemModel(0x560a43807900) org.kde.plasma.libdiscover: Couldn't find a catagory for "fwupd-backend" PackageKit stopped running! STEPS TO REPRODUCE 1. Packages mentioned do not appear in Muon Package Manager. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION xterm -132 -fn 10x20 -e /usr/bin/plasma-discover -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 397034] New: completed piles fail to fall and left a space between completed piles
https://bugs.kde.org/show_bug.cgi?id=397034 Bug ID: 397034 Summary: completed piles fail to fall and left a space between completed piles Product: kpat Version: 3.6 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: la.bu...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (3.6) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.138-59-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: after 4th completed pile fell i still had a space between 2nd and 3rd pile when i moved cursor spider crashed -- Backtrace: Application: KPatience (kpat), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3217779780 (LWP 26121))] Thread 3 (Thread 0x7f31fb1ef700 (LWP 26124)): #0 0x7f321313630d in poll () from /lib64/libc.so.6 #1 0x7f320e912314 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f320e91242c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f3213d3f1ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f3213cecbfb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f3213b27f5a in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f320fb61295 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f3213b2ca29 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f320f046724 in start_thread () from /lib64/libpthread.so.0 #9 0x7f321313ee8d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f32035d1700 (LWP 26123)): #0 0x7f321313630d in poll () from /lib64/libc.so.6 #1 0x7f320cf613c2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f320cf62faf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f3205b2c0d9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f3213b2ca29 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f320f046724 in start_thread () from /lib64/libpthread.so.0 #6 0x7f321313ee8d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f3217779780 (LWP 26121)): [KCrash Handler] #6 0x0045ac49 in ?? () #7 0x7f3213d18de3 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #8 0x7f3213d18de3 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #9 0x7f3213d18de3 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5 #10 0x7f3213d25dd2 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib64/libQt5Core.so.5 #11 0x7f3213d19bf4 in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #12 0x7f32150a828c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x7f32150ac8ea in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #14 0x7f3213ceebe5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #15 0x7f3213d3eafe in QTimerInfoList::activateTimers() () from /usr/lib64/libQt5Core.so.5 #16 0x7f3213d3eec1 in ?? () from /usr/lib64/libQt5Core.so.5 #17 0x7f320e912134 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #18 0x7f320e912388 in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x7f320e91242c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #20 0x7f3213d3f18c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #21 0x7f3213cecbfb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #22 0x7f3213cf4ae6 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5 #23 0x0041efaf in ?? () #24 0x7f3213072725 in __libc_start_main () from /lib64/libc.so.6 #25 0x0041f849 in _start () Possible duplicates by query: bug 395984, bug 395983, bug 395982, bug 395624, bug 389064. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376958] New: Tax form fill in doesn't work
https://bugs.kde.org/show_bug.cgi?id=376958 Bug ID: 376958 Summary: Tax form fill in doesn't work Product: okular Version: 0.24.0 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: gh...@mail.com Target Milestone: --- Created attachment 104235 --> https://bugs.kde.org/attachment.cgi?id=104235&action=edit WI 2016 Tax Form Wisconsin 2016 tax form (fill in) won't fill in lines 14 & 39. Works on Windows 7 Adobe Reader, but fails on all Linux PDF Viewers. Form is attached. Please advise gh...@mail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 376958] Tax form fill in doesn't work
https://bugs.kde.org/show_bug.cgi?id=376958 --- Comment #3 from Gary --- Thanks for the testing info & the GitHub Link. Will this be fixed ? regards, Gary H. On 02/28/2017 07:06 PM, Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=376958 > > Albert Astals Cid changed: > > What|Removed |Added > > CC||aa...@kde.org > > --- Comment #2 from Albert Astals Cid --- > Those fields are auto updating, i did some coding and it's "kind of working" > but still needs work https://www.youtube.com/watch?v=fCLFkpaW3Ug > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 378676] New: 4.8.0 multiple installation problems on windows
https://bugs.kde.org/show_bug.cgi?id=378676 Bug ID: 378676 Summary: 4.8.0 multiple installation problems on windows Product: kmymoney4 Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: gf...@twoshoelaces.com Target Milestone: --- Been using 4.7.2 on Windows, trying to install 4.8.0 on Windows (via http://sourceforge.net/projects/kmymoney2/files/KMyMoney-Windows/4.8.0/kmymoney-x86-setup-4.8.0.exe/download) using MySQL. After program is installed, File -> Save as Database results in multiple errors: 1) CREATE TABLE kmmAccountsPayeeIdentifier (accountId varchar(32) NOT NULL, "order" smallint unsigned NOT NULL, identifierId varchar(32) NOT NULL, PRIMARY KEY (accountId, "order")) ENGINE = InnoDB; dies due to using "order", per bug #365615. I changed 4 instances in the SQL calls (2 each in creating tables kmmAccountsPayeeIdentifier and kmmPayeesPayeeIdentifier ) from order to userOrder 2) What appears to be a typo in INSERT INTO kmmFileInfo row, hiPayeeIdentifierId data is NULLentifierId when I'm guessing it should be NULL? After making the above changes, the SQL tables create successfully, but the program dies when using File -> Open database. Another instance of Bug 365615, hardcoded "order" instead of userOrder in the query ORDER BY, here is error text: Cannot open file as requested. Error was: Error in function const class QMap __thiscall MyMoneyStorageSql::fetchPayees(const class QStringList &,bool) const : reading Payee Driver = QMYSQL, Host = localhost, User = root, Database = kmymoney2 Driver Error: Database Error No -1: Text: Error type 0 Executed: SELECT kmmPayees.id AS id, kmmPayees.name AS name, kmmPayees.reference AS reference, kmmPayees.email AS email, kmmPayees.addressStreet AS addressStreet, kmmPayees.addressCity AS addressCity, kmmPayees.addressZipcode AS addressZipcode, kmmPayees.addressState AS addressState, kmmPayees.telephone AS telephone, kmmPayees.notes AS notes, kmmPayees.defaultAccountId AS defaultAccountId, kmmPayees.matchData AS matchData, kmmPayees.matchIgnoreCase AS matchIgnoreCase, kmmPayees.matchKeys AS matchKeys, kmmPayeesPayeeIdentifier.identifierId AS identId FROM ( SELECT * FROM kmmPayees ) kmmPayees LEFT OUTER JOIN kmmPayeesPayeeIdentifier ON kmmPayees.Id = kmmPayeesPayeeIdentifier.payeeId ORDER BY kmmPayees.id, kmmPayeesPayeeIdentifier."order"; Query error No 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '"order"' at line 1 QMYSQL: Unable to execute query Error type 2 Is there a way to modify the SQL code given that I'm running it using the Windows .exe installer? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney4] [Bug 378676] 4.8.0 multiple installation problems on windows
https://bugs.kde.org/show_bug.cgi?id=378676 --- Comment #1 from Gary --- Here is the exact SQL in my 2), error is in 4th from last field: INSERT INTO kmmFileInfo (version, created, lastModified, baseCurrency, institutions, accounts, payees, tags, transactions, splits, securities, prices, currencies, schedules, reports, kvps, dateRangeStart, dateRangeEnd, hiInstitutionId, hiPayeeId, hiTagId, hiAccountId, hiTransactionId, hiScheduleId, hiSecurityId, hiReportId, encryptData, updateInProgress, budgets, hiBudgetId, hiOnlineJobId, hiPayeeIdentifierId, logonUser, logonAt, fixLevel) VALUES (8, '2017-04-11', '2017-04-11', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 'N', NULL, NULL, NULL, NULLentifierId, NULL, NULL, 4); -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 359295] New: Kontact crashes when installing third-party header theme Material through GHNS
https://bugs.kde.org/show_bug.cgi?id=359295 Bug ID: 359295 Summary: Kontact crashes when installing third-party header theme Material through GHNS Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: gree...@kde.org Application: kontact (5.1.48 pre) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Installing a new header theme through the GHNS wizard. Unsure if this is related to the specific theme or not. The theme I was attempting to install is called Material. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f091c4aa7c0 (LWP 32343))] Thread 61 (Thread 0x7f090074b700 (LWP 32344)): #0 0x7f09190eec1d in poll () at /lib64/libc.so.6 #1 0x7f0912872422 in _xcb_conn_wait () at /usr/lib64/libxcb.so.1 #2 0x7f091287400f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f090289b3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f09199fd44f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 60 (Thread 0x7f08f3215700 (LWP 32345)): #0 0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f09169ec733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f09169ec759 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 59 (Thread 0x7f08b2252700 (LWP 32346)): #0 0x7f09199f5cda in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f0919c30ba5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f0911c314ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0911c31d80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f0911c31f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f0919c30c7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f0919bd7c73 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f09199f872a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f09199fd44f in () at /usr/lib64/libQt5Core.so.5 #9 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 58 (Thread 0x7f08a61cd700 (LWP 32347)): #0 0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f08b0d91ae3 in radeon_drm_cs_emit_ioctl () at /usr/lib64/dri/r600_dri.so #2 0x7f08b0d91337 in impl_thrd_routine () at /usr/lib64/dri/r600_dri.so #3 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 57 (Thread 0x7f08a4d09700 (LWP 32348)): #0 0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f09166f875d in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f0916a1b031 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 56 (Thread 0x7f08a4508700 (LWP 32349)): #0 0x7f091245305f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f09166f9733 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f0916a1b031 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 55 (Thread 0x7f0892ca7700 (LWP 32350)): #0 0x7f0919c3175b in () at /usr/lib64/libQt5Core.so.5 #1 0x7f0911c318f1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7f0911c31df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f0911c31f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f0919c30c7b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f0919bd7c73 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f09199f872a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f09199fd44f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f091244f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f09190f704d in clone () at /lib64/libc.so.6 Thread 54 (Thread 0x7f08924a6700 (LWP 32351)): #0 0x7ffe27159b26 in clock_gettime () #1 0x7f0919103c9d in clock_gettime () at /lib64/libc.so.6 #2 0x7f0919aae906 in () at /usr/lib6
[plasmashell] [Bug 359783] New: Folder view icons aligned left, but configured to be on the right
https://bugs.kde.org/show_bug.cgi?id=359783 Bug ID: 359783 Summary: Folder view icons aligned left, but configured to be on the right Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: gree...@kde.org CC: plasma-b...@kde.org After configuring my icons to be on the right, on login, they show on the left. Once I click on the desktop, the icons properly reposition themselves on the right side of the screen. Reproducible: Always Steps to Reproduce: 1. Configure folder view for the desktop containment and then set the icons to align top to bottom on the right hand side of the screen. 2. Log out. 3. Log back in. Actual Results: On login, you'll see the icons aligned to the LEFT. Clicking on the desktop will cause them to reposition to the right, as they are configured to be. Expected Results: On login, they should be aligned top-to-bottom, on the RIGHT of the screen. I'm using OpenSuSE's Git built RPMs from their OBS, but I'm pretty sure this isn't caused by a distribution patch, but rather is a legitimate bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 474723] Group items into "user-installed" and "system-installed" sections
https://bugs.kde.org/show_bug.cgi?id=474723 Gary changed: What|Removed |Added CC||jan.selc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 423344] Group items on "Installed" page by high-level categories
https://bugs.kde.org/show_bug.cgi?id=423344 Gary changed: What|Removed |Added CC||jan.selc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 397486] Add sort by date installed, for the Installed software view
https://bugs.kde.org/show_bug.cgi?id=397486 Gary changed: What|Removed |Added CC||jan.selc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426326] Ability to reverse sort order of installed applications
https://bugs.kde.org/show_bug.cgi?id=426326 Gary changed: What|Removed |Added CC||jan.selc...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447532] Kate 21.12.0 on Windows doesn't save user color scheme
https://bugs.kde.org/show_bug.cgi?id=447532 --- Comment #7 from Gary Wang --- This issue still exist in kate-21.12.2-1567-windows-msvc2019_64-cl.exe Since kate-21.12.0-1500-windows-msvc2019_64-cl.exe works fine and after kate-21.12.0-1515-windows-msvc2019_64-cl.exe it got this issue, does anyone know what's changed between #1500 and #1515 these two builds? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469174] New: Ledger Lens doesn't turn off.
https://bugs.kde.org/show_bug.cgi?id=469174 Bug ID: 469174 Summary: Ledger Lens doesn't turn off. Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: gary.mo...@canonsfield.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 *** Ledger Lens doesn't turn off. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT Ledger Lens doesn't turn off. EXPECTED RESULT Ledger Lens should turn off. SOFTWARE/OS VERSIONS Windows: 11 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.
[kmymoney] [Bug 469174] Ledger Lens doesn't turn off.
https://bugs.kde.org/show_bug.cgi?id=469174 --- Comment #2 from Gary Moore --- No Gary Moore MCIWM CRWM MInstLM P: 07712 735474 E: gary.mo...@canonsfield.com A: 62 Canonsfield, Werrington, Peterborough, PE4 5AQ -Original Message- From: Jack Sent: Sunday, May 7, 2023 11:10 PM To: gary.mo...@canonsfield.com Subject: [kmymoney] [Bug 469174] Ledger Lens doesn't turn off. <https://bugs.kde.org/show_bug.cgi?id=469174> https://bugs.kde.org/show_bug.cgi?id=469174 Jack < <mailto:ostrof...@users.sourceforge.net> ostrof...@users.sourceforge.net> changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Jack < <mailto:ostrof...@users.sourceforge.net> ostrof...@users.sourceforge.net> --- In the KMyMoney settings dialog, Ledger section. Display tab, is "Show all ledger entries in full detail" checked? If so, the ledger lens doesn't show any additional detail, so it looks like it's always on. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 --- Comment #15 from Gary Carter --- Created attachment 152526 --> https://bugs.kde.org/attachment.cgi?id=152526&action=edit Sample script for detecting if the external GPU is plugged in on an AMD multi-GPU laptop Hi all, While we wait to see if Mesa will acknowledge + potentially resolve this upstream, I'm attaching a little script I have in /etc/profile.d that checks to see if a monitor is plugged into the dGPU's DisplayPort (USB-C), and if so, puts the cards in the 'right' order in KWIN_DRM_DEVICES (and similarly, forces the opposite order if the port is disconnected). This way at least, it's just a log out and back in as opposed to having to manually edit that variable in your profile. The usual caveats apply here in that this could mess with power consumption + thermals by potentially unnecessarily keeping the dGPU powered up. -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 460158] New: Incorrect input method (IME) position
https://bugs.kde.org/show_bug.cgi?id=460158 Bug ID: 460158 Summary: Incorrect input method (IME) position Classification: Applications Product: ghostwriter Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: wzc782970...@gmail.com Target Milestone: --- SUMMARY Ghostwritter seems doesn't have proper input method (IME) support, IME position will always be at the top-left corner of the window. Tested both under Arch Linux with fcitx5-rime and Windows 11 with it's default Microsoft Chs-IME when Windows system language was set to Chinese. STEPS TO REPRODUCE 1. Install an IME (Chinese/Japanese/etc.) on your system 2. Open Ghostwriter 3. Type anything with IME enabled OBSERVED RESULT IME popped at the top-left side of the window. EXPECTED RESULT IME popped at the correct position (normally below the input cursor) SOFTWARE/OS VERSIONS Windows: Windows 11 21H2 Linux/KDE Plasma: Arch Linux (rolling) KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Linux version get from Arch Linux's official package repo, with ghostwriter 2.1.4-1 Windows version get from GitHub, release 2.1.6 I did a quick glance at the related source code and it seems the MarkdownEditor widget/class didn't handle the QWidget::inputMethodQuery(Qt::InputMethodQuery) query so that's probably the reason... Feel free to let me know if you need any extra information. -- You are receiving this mail because: You are watching all bug changes.
[ghostwriter] [Bug 460158] Incorrect input method (IME) position
https://bugs.kde.org/show_bug.cgi?id=460158 --- Comment #2 from Gary Wang --- Hi again, > Which IME application are you using so I can try to replicate this? As already provided in the original report: When tested under Arch Linux: fcitx5-rime [1] When tested under Windows 11: default Microsoft Chs-IME when Windows system language was set to Chinese. [1]: https://archlinux.org/packages/community/x86_64/fcitx5-rime/ in case you need a link. > A followup question would be: Is this application for GTK or Qt apps? It would be generic enough to support both GTK and Qt apps. I did set up some environment variable to make fcitx work under my Arch Linux installation tho. here is the related content in my `/etc/environment` file: GTK_IM_MODULE=fcitx QT_IM_MODULE=fcitx XMODIFIERS=@im=fcitx -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 117648] Add a "show whitespaces" option in the "View" menu
https://bugs.kde.org/show_bug.cgi?id=117648 Gary Wang changed: What|Removed |Added CC||wzc782970...@gmail.com --- Comment #8 from Gary Wang --- Just would like to leave a comment here, I'm a user of Notepad++-style editor and also use a similar feature a lot, so I proposed a MR to allow user to add such entry to the toolbar if they preferred. See https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/698 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488784] New: icon request: show whitespaces / show all characters
https://bugs.kde.org/show_bug.cgi?id=488784 Bug ID: 488784 Summary: icon request: show whitespaces / show all characters Classification: Plasma Product: Breeze Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: wzc782970...@gmail.com CC: kain...@gmail.com, m...@nueljl.in Target Milestone: --- I'm a user of Notepad++-style editor, which provides a lot of common-used features in their toolbar and makes the toolbar icon-only. One of the features is "Show all characters" which allows user see all characters which are usually hard to distinguish or invisible, like Tab and Space, CR LF and LF. I'd like to contribute such a feature to Kate so I can use it the same way, so icons for such action are needed. The icons I think we might need are: 1. Show whitespaces 2. Show non-printable spaces 3. Show all characters ADDITIONAL INFORMATION If you would like to try out the "Show all characters" feature but don't want to install Windows or use Wine, you can try other Notepad++-clones like the following ones, which I confirmed have such feature: - Notepadqq: https://archlinux.org/packages/extra/x86_64/notepadqq/ - NotepadNext: https://flathub.org/apps/details/com.github.dail8859.NotepadNext - Notepad--: https://aur.archlinux.org/packages/notepad---git - Textosaurus: https://flathub.org/apps/io.github.martinrotter.textosaurus About the feature itself, I currently have a MR to add the "Show whitespaces" action to KTextEditor, see: - https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/698 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 488784] icon request: show whitespaces / show all characters
https://bugs.kde.org/show_bug.cgi?id=488784 --- Comment #1 from Gary Wang --- Some info might be helpful for creating related icons: For the "Show whitespaces" action, the glyph of the ␣ (U+2423 OPEN BOX) character can be used as reference, which itself is the graphic for space. For the "Show non-printable spaces" action, I actually don't have any good idea but the glyph of the ␢ (U+2422 BLANK SYMBOL) character might be good to be used as reference, which itself is the graphic for (blank) space. Actually U+2400-2421 is for these non-printable control characters, like U+240A is LF and so on, KCharSelect can be used to check those characters. Alternatively, ☒ (U+2612 BALLOT BOX WITH X) can be used as reference, which more likely a tofu character. For the "Show all characters" action, the glyph of the ¶ (U+00B6 PILCROW SIGN) character can be used as reference. This is the icon that most Notepad++-clones (include Notepad++ itself) use for such action. Whatever acceptable or not I'm both fine with VDG's decision, hope that helps :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] New: local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 Bug ID: 488232 Summary: local x-window app that still works from command line no longer launches Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: ga...@teledyn.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY This is very new behaviour as of within the past few days. Clicking a launcher for a local app will animate on click, but the app does not launch and no error is reported. STEPS TO REPRODUCE 1. create a launcher with ~/.local/bin/xwin-prog given environment XPROG=~/.xprog and parameters "--this='that'" 2. drag and drop the launcher on to the Panel 3. click the panel icon or the launcher icon to launch OBSERVED RESULT the icon on hover identifies the program, blue dots spin around it when it is clicked, but the program no longer appears. EXPECTED RESULT this particular application opens a shell window and another graphic chart display; interacting with the chart displays data in the shell. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu Studio 24.04 X11 (not Wayland) (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: ADDITIONAL INFORMATION when bash is given the command line > XPROG=~/.xprog ~/.local/bin/xwin-prog --this='that' the program displays as expected. to be fair, I haven't yet tested using a different xwindows program, but this particular application is one I would query frequently from the panel. Editing the launcher, I noticed the environment variable assignment had been quoted; I removed these, saved, but re-editing shows they were put back in. The program parameters however are not shown as quoted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 --- Comment #1 from Gary Murphy --- I can confirm this did not affect loading the Qt application qutebrowser, or the KDE Snapshot app. This only seems to affect the xwindow app. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 --- Comment #2 from Gary Murphy --- Have confirmed recompiling the xwindows application after an apt upgrade and reboot to ensure libraries match; that wouldn't explain why Konsole can launch the same command line in bash, but I wanted to make sure. There is a slightly different behaviour in a Konsole window now appears briefly and then vanishes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 --- Comment #3 from Gary Murphy --- Also confirm that, after reboot, clicking the launcher from the Application Launcher works, but clicking the icon on the panel does not. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488286] New: Dolphin Windows do not properly restore after a Launcher reboot
https://bugs.kde.org/show_bug.cgi?id=488286 Bug ID: 488286 Summary: Dolphin Windows do not properly restore after a Launcher reboot Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ga...@teledyn.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When the desktop is rebooted with multiple Dolphin Windows open (each with several tabs), when the desktop returns, the dolphin windows are all same size, same position, with default zoom and not the size that was closed. STEPS TO REPRODUCE 1. open several Dolphin windows with multiple tabs, position, resize and zoom as desired 2. Open KDE Launcher and select reboot OBSERVED RESULT EXPECTED RESULT All other applications return to their last position, window dimensions and zoom. I expect Dolphin, as an official KDE app, to do the same SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.8.0-35-lowlatency (64-bit) X11 Ubuntustudio 24.04 (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 ADDITIONAL INFORMATION All packages current and rebooted as of June 8, 2024 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 Gary Murphy changed: What|Removed |Added Component|general |Application Launcher ||(Kickoff) Status|NEEDSINFO |REPORTED Summary|local x-window app that |local x-window app that |still works from command|still works from command |line no longer launches |line no longer launches |from Kickoff or Panel | Resolution|WAITINGFORINFO |--- --- Comment #5 from Gary Murphy --- I should have done this before and apologize for not thinking of it, but I set the terminal to not close after execution and the problem appears to be those inserted quote marks around the environment variable assignment, the variable is ignored and so the program is exiting because it cannot find its data files. While this is a good theory, it doesn't explain why the same quoted 'XPROG=~/.xprog' in the Environment form does work when launched from the KDE Launcher, but not when put into the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 --- Comment #6 from Gary Murphy --- The work-around is to explicitly add the working directory so all its files are local. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 488320] New: Feature request: hot-keys for sorting
https://bugs.kde.org/show_bug.cgi?id=488320 Bug ID: 488320 Summary: Feature request: hot-keys for sorting Classification: Applications Product: dolphin Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ga...@teledyn.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I find in practice that most folders need to be either sorted by modification time, newest first, or sorted by name a-z. Unfortunately to switch between these modes requires a lot of mouse-clicks and menu nav. Would it be possible to map these two sort options to hot-keys? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488232] local x-window app that still works from command line no longer launches
https://bugs.kde.org/show_bug.cgi?id=488232 --- Comment #7 from Gary Murphy --- I think we can actually close this ticket: I just noticed the Launcher version of the app had already defined a working directory whereas the Panel icon launcher did not; I was not aware that these where independent launchers! It is not unlikely that this particular app, which is not mine, may intend to use XPROG as a working directory, but it maybe does not, or the ~ is not expanded, it could be anything but it does not appear to be specific to the Panel or the Launcher. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 486617] New: Folder phone/Android/data/ appears empty when browsing from Dolphin
https://bugs.kde.org/show_bug.cgi?id=486617 Bug ID: 486617 Summary: Folder phone/Android/data/ appears empty when browsing from Dolphin Classification: Applications Product: kdeconnect Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: g...@caaos.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Log into phone 2. Open Dolphin and browse to Phone/Android/data 3. OBSERVED RESULT folder is empty EXPECTED RESULT Contains data for installed apps on phone SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.6.26-1-MANJARO(64bit) (available in About System) KDE Plasma Version: KDE 5.27.11 KDE Frameworks Version: 5.115 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484295] New: Dolphin ignores setting the search options in settings
https://bugs.kde.org/show_bug.cgi?id=484295 Bug ID: 484295 Summary: Dolphin ignores setting the search options in settings Classification: Applications Product: dolphin Version: 23.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: ga...@teledyn.com CC: kfm-de...@kde.org 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 *** Every new tab uses 'natural' sort order and resets settings put in the Settings dialog. STEPS TO REPRODUCE 1. Ctrl+Shift , and set sort order to Alphabetic 2. Double Click on any folder OBSERVED RESULT Opened folder is now in 'natural' order, and in the Settings sort order is also set back to natural order EXPECTED RESULT I really just want to open most folders in Filename A-Z order or sometimes in last-modified; I almost never want to open folders in time-created sort order. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: latest updates to 23.10 (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.
[kwin] [Bug 471893] Resizing tiled windows (using Super+Arrow) on one virtual desktops affects all other tiled windows across all virtual desktops
https://bugs.kde.org/show_bug.cgi?id=471893 Gary Taylor changed: What|Removed |Added CC||gary.tay...@hismessages.com -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 486958] New: Resizing of windows in a grid layout affects other activities
https://bugs.kde.org/show_bug.cgi?id=486958 Bug ID: 486958 Summary: Resizing of windows in a grid layout affects other activities Classification: Plasma Product: kactivitymanagerd Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: gary.tay...@hismessages.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Resizing of windows in a grid layout affects other activities STEPS TO REPRODUCE 1. Setup 2 activities 2. In each activity, open 4 windows of any application and drag into each corner of the screen 3. In the first activity, drag any horizontal or vertical divider between the windows 4. The change is made in both the first and second activity 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.
[frameworks-syntax-highlighting] [Bug 445649] New: OrgMode syntax highlighting support
https://bugs.kde.org/show_bug.cgi?id=445649 Bug ID: 445649 Summary: OrgMode syntax highlighting support Product: frameworks-syntax-highlighting Version: 5.88.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: syntax Assignee: kwrite-bugs-n...@kde.org Reporter: wzc782970...@gmail.com CC: walter.von.entfer...@posteo.net Target Milestone: --- SUMMARY Feature request for OrgMode (https://orgmode.org/) file syntax highlighting support. STEPS TO REPRODUCE 1. Prepare a valid OrgMode file 2. Open it with Kate for example 3. See the result OBSERVED RESULT No syntax highlighting, the selectable language list also doesn't have Org Mode to select. EXPECTED RESULT Able to do syntax highlight for OrgMode files. SOFTWARE/OS VERSIONS syntax-highlighting tag 5.88.0 and also master branch ADDITIONAL INFORMATION I try to follow the manual to create a custom syntax highlighting XML file for OrgMode mode to fit my need, but I still have trouble understanding the manual, and the XML I created only covers the very basic usage of OrgMode. Hope we can get official OrgMode syntax highlighting from KDE. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 445649] OrgMode syntax highlighting support
https://bugs.kde.org/show_bug.cgi?id=445649 --- Comment #2 from Gary Wang --- (In reply to Waqar Ahmed from comment #1) > If you have created a syntax file for org mode, feel free to make a merge > request with it. It doesn't have to be perfect, you can improve it with time. Thanks! My current syntax file is here. It still lacks some functionality, I still cannot figure out how to make it foldable by heading level but anyway it's here. Any help is appreciated. https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/272 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446633] New: Can't Zoom without Rotation
https://bugs.kde.org/show_bug.cgi?id=446633 Bug ID: 446633 Summary: Can't Zoom without Rotation Product: krita Version: 5.0.0-beta5 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: garyda...@hotmail.com Target Milestone: --- I'm running the 5.0 Beta, and I think this is an issue that I didn't have with 4.0. I'm using a two-finger gesture to zoom, as I've always done, but I can't seem to zoom without rotation, which I don't want. I can use the various zoom tools to zoom without rotation, but is there a way I can continue to use touch without having the canvas spin every which way? No matter how I touch the screen, the canvas rotates when I change the zoom. Thanks! Gary -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 446633] Can't Zoom without Rotation
https://bugs.kde.org/show_bug.cgi?id=446633 --- Comment #2 from Gary Dave --- Great, thanks - will do! This is not an issue in the older version I just reverted to, so perhaps the default setting is different in 5.0, since I didn't address it before. If so, the default setting should be touch rotation disabled. Gary Sent from Mailspring (https://getmailspring.com/), the best free email app for work On Dec 7 2021, at 10:35 am, Halla Rempt wrote: > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.kde.org%2Fshow_bug.cgi%3Fid%3D446633&data=04%7C01%7C%7Ca8bf7f91d1794910cd4c08d9b9b048eb%7C84df9e7fe9f640afb435%7C1%7C0%7C637744989058814284%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=PutfODQcTePeTSl04AoTQlRuriZX7IJ48UIiaCY17co%3D&reserved=0 > > Halla Rempt changed: > What |Removed |Added > > CC| |ha...@valdyas.org > Resolution|--- |NOT A BUG > Status|REPORTED |RESOLVED > > --- Comment #1 from Halla Rempt --- > Disable Touch Rotation in settings->configure krita->general->Tools. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453312] New: Not able to launch after upgrading from 21.12.3 to 22.04.0-1 under Windows
https://bugs.kde.org/show_bug.cgi?id=453312 Bug ID: 453312 Summary: Not able to launch after upgrading from 21.12.3 to 22.04.0-1 under Windows Product: kdenlive Version: 22.04.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: wzc782970...@gmail.com Target Milestone: --- SUMMARY Not able to launch after upgrading from 21.12.3 to 22.04.0-1 under Windows, using the installer. Uninstalling and re-installing also won't fix this issue. STEPS TO REPRODUCE 1. Get the 21.12.3 version installed using the 21.12.3 version installer 2. Install the 22.04.0-1 version using the installer 3. Try launching kdenlive.exe OBSERVED RESULT After the splash screen, there is a dialog that says it crashed last time and asks if I need to reset the config file. Whichever option is chosen, the dialog disappeared and the kdenlive.exe process also disappeared (seems exited or crashed). EXPECTED RESULT The program can launch. SOFTWARE/OS VERSIONS Windows: 11 Home, 21H2, 22000.613 ADDITIONAL INFORMATION System language: Simplified Chinese Installer Hash: 0b534ca34feef79422b84bf140809cf8c68dc00911cf4eb9d100cdffb69561e8 *kdenlive-22.04.0-1.exe Graphics Card: Intel(R) UHD Graphics 630 (It's a dual graphics card laptop, but it will use Integrated graphics by default, which is the Intel one) Since this bug looks very similar to https://bugs.kde.org/show_bug.cgi?id=436269 so I tried to uninstall Kdenlive and reinstall it to see if that can fix, but sadly the issue still occur. So, I have to downgrade to 21.12.3 for now. I'm not sure what other information needs to be provided so let me know if you need any additional information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453312] Not able to launch after upgrading from 21.12.3 to 22.04.0-1 under Windows
https://bugs.kde.org/show_bug.cgi?id=453312 Gary Wang changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |BACKTRACE --- Comment #1 from Gary Wang --- I got another PC and did a clean installation of 22.04.0-1 using the same installer mentioned in the description, and it can be launched and works fine. So, I checked again and found out the 21.12.3 uninstaller won't delete all the Kdenlive files from my PC. After uninstall 21.12.3 with the uninstaller, also manually delete the kdenlive installation location folder, and then install 22.04.0-1, Kdenlive can now works fine again! I'll mark this bug report as resolved then... -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453536] New: Mix clip for audio track is reversed in 2nd and 4th time
https://bugs.kde.org/show_bug.cgi?id=453536 Bug ID: 453536 Summary: Mix clip for audio track is reversed in 2nd and 4th time Product: kdenlive Version: 22.04.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: wzc782970...@gmail.com Target Milestone: --- SUMMARY Mix clip (Select both audio clip and press U key) for audio track is reversed in 2nd and 4th time. STEPS TO REPRODUCE 1. 2. 3. It's hard for me to describe in text so I also recorded a video to reproduce this issue. 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.
[kdenlive] [Bug 453537] New: Mix clip for audio track is reversed in 2nd and 4th time and so on
https://bugs.kde.org/show_bug.cgi?id=453537 Bug ID: 453537 Summary: Mix clip for audio track is reversed in 2nd and 4th time and so on Product: kdenlive Version: 22.04.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: wzc782970...@gmail.com Target Milestone: --- SUMMARY Mix clip (Select both audio clip and press U key) for audio track is reversed in 2nd and 4th time. STEPS TO REPRODUCE 1. Import testkdenlive.mp4 and drag it to the timeline 2. Use Shift+R to split it twice, delete the clip in the middle and remove the blank space 3. Select the remaining two clip and use shortcut U to create a mix clip 4. Try playback, in this time it behave normally 5. Repeat step 2 and 3 to create another clip mix next to the previous mix clip 6. Try playback / see the result. It's hard for me to describe in text so I also recorded a video to reproduce this issue. OBSERVED RESULT At step 6, you will hear reversed clip mix instead of the same result as you can get in step 3. EXPECTED RESULT At step 6, you will hear the same result as you can get in step 3. SOFTWARE/OS VERSIONS Tested both on Windows with 22.04.0 and Arch Linux with 22.04.0 and git-master. ADDITIONAL INFORMATION After step 6, if you repeat step 2 and 3, you will get the same wrong mix clip at 2nd, 4th, 6th time you repeat the steps. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453536] Mix clip for audio track is reversed in 2nd and 4th time
https://bugs.kde.org/show_bug.cgi?id=453536 Gary Wang changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Gary Wang --- Seems I wrongly pressed the Enter key while selecting attachment. The description is not completed. See https://bugs.kde.org/show_bug.cgi?id=453537 for the full report. Sorry for created an incomplete bug report. *** This bug has been marked as a duplicate of bug 453537 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453537] Mix clip for audio track is reversed in 2nd and 4th time and so on
https://bugs.kde.org/show_bug.cgi?id=453537 --- Comment #1 from Gary Wang --- *** Bug 453536 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453537] Mix clip for audio track is reversed in 2nd and 4th time and so on
https://bugs.kde.org/show_bug.cgi?id=453537 --- Comment #2 from Gary Wang --- Created attachment 148657 --> https://bugs.kde.org/attachment.cgi?id=148657&action=edit video that recorded the steps to reproduce this issue -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453537] Mix clip for audio track is reversed in 2nd and 4th time and so on
https://bugs.kde.org/show_bug.cgi?id=453537 --- Comment #3 from Gary Wang --- Created attachment 148658 --> https://bugs.kde.org/attachment.cgi?id=148658&action=edit testkdenlive.mp4: The original video clip used in the recording that reproduced this bug -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453537] Mix clip for audio track is reversed in 2nd and 4th time and so on
https://bugs.kde.org/show_bug.cgi?id=453537 Gary Wang changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Gary Wang --- It should be fixed on 22.04.1. Related fix: https://invent.kde.org/multimedia/kdenlive/-/merge_requests/299 The official website still offers 22.04.0 currently but Arch Linux and KDE Binary Factory already contain 22.04.1 package/binary, so I guess I should close this bug now :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 453537] Mix clip for audio track is reversed in 2nd and 4th time and so on
https://bugs.kde.org/show_bug.cgi?id=453537 Gary Wang changed: What|Removed |Added Version Fixed In||22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware/romanized alphabetic categories for when using a language with a non-Latin alphabet
https://bugs.kde.org/show_bug.cgi?id=433297 --- Comment #10 from Gary Wang --- > Improve kickoff's group for non-latin language. Thanks for the fix! Does the fix also apply to the Application Dashboard applet since it also behaviors the same way as Kicker and Kickoff? If not, do I need to open a separated bug report for the Application Dashboard behavior? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware/romanized alphabetic categories for when using a language with a non-Latin alphabet
https://bugs.kde.org/show_bug.cgi?id=433297 --- Comment #13 from Gary Wang --- (In reply to Fushan Wen from comment #11) > (In reply to Gary Wang from comment #10) > > Thanks for the fix! Does the fix also apply to the Application Dashboard > > applet since it also behaviors the same way as Kicker and Kickoff? If not, > > do I need to open a separated bug report for the Application Dashboard > > behavior? > > Yes > > The group in Dashboard was also fixed. Thanks for clarifying! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 447532] Kate 21.12.0 on Windows doesn't save user color scheme
https://bugs.kde.org/show_bug.cgi?id=447532 --- Comment #14 from Gary Wang --- Tested and it's fixed on kate-21.12.3-1-1612-windows-msvc2019_64-cl.exe from the binary factory. Thanks for the fix! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kimageformats] [Bug 428238] Not able to render PSD file with depth other than 8 and 16
https://bugs.kde.org/show_bug.cgi?id=428238 Gary Wang changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Gary Wang --- Yeah, you're right, sorry I forgot to mark it as fixed when I noticed it's fixed. Thanks for the patch and release! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 Gary Carter changed: What|Removed |Added CC||kit...@gmail.com --- Comment #4 from Gary Carter --- Hi - for what it's worth, I've been experiencing the same issue on my all-AMD gaming laptop (ASUS ROG Strix G513QY 'AMD Advantage Edition') with an external USB-C -> DisplayPort monitor with VRR under Artix Linux, and have been deliberately holding back actually on the last versions of: kscreen (5.24.5-1) kwin (5.24.5-2) kwayland-server (5.24.5-1.1) kwayland-integration (5.24.5-1) While letting everything else stay up-to-date as normal with so far no ill repercussions. There's definitely some kind of regression with this particular combination of Wayland + Plasma 5.25 + an external monitor on a dGPU (though 5.24 itself fixed a lot of issues on this front for me, especially around either it being DisplayPort or because the DP connection is connected to the dGPU while HDMI is on the iGPU, and there's no MUX here, so PRIME and Reverse PRIME are involved, I think.) A quick search of pkgs.org shows me that for Fedora 36, it's the 'Fedora Updates' channel that's pulling in Plasma 5.25.4-1, while the base 'Fedora' one still is on 5.24.3-4. It looks like kwayland-server was rolled into kwin itself at some point, so if you want to try rolling back here to see if this works around the issue, you may want to manually install kwayland-server 5.24.3 as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 --- Comment #6 from Gary Carter --- Huh, wow! I can confirm this does indeed also resolve the issue for me, though for whatever reason my particular setup has the cards reversed (checked with lspci and what /dev/dri/by-path was linking to), so I had to flip the card order in that profile script, but after upgrading to 5.25.4 and relogging, I do see the change in the About panel to the 6800M from RENOIR, and my initial testing so far here lets me launch things like games from Steam (Timberborn via GE-Proton-7.29, for reference), get to the main menu, and Alt-Tab out and back in without everything freezing (MangoHud's frame time graph is a good indicator as that freezes up, too). I wonder if this bug & relevant commit is related? https://bugs.kde.org/show_bug.cgi?id=453386 Or whatever this is doing about 'multi-GPU' setups: https://invent.kde.org/plasma/kwin/-/commit/6012e409a61cf4100455c2db664fe6e058a57165 (I'm just looking at the changelog at https://kde.org/announcements/changelogs/plasma/5/5.24.5-5.25.0/) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 --- Comment #8 from Gary Carter --- Created attachment 151419 --> https://bugs.kde.org/attachment.cgi?id=151419&action=edit Wayland Session log with KWin Debugging Bug triggered with QT_LOGGING_RULES="kwin_*.debug=true" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 --- Comment #9 from Gary Carter --- (In reply to Zamundaaa from comment #7) > So there's a few things you can test to narrow this down: > 1. with the dedicated GPU set as primary, do games freeze if they're on the > laptop screen? No, everything (mostly) works fine regardless of screen with the first workaround, though I don't get a mouse cursor while over on the laptop panel in multi-monitor mode for some reason... > 2. with the integrated GPU set as primary and KWIN_DRM_NO_DIRECT_SCANOUT=1 > set, do games still freeze when they're on the external screen? This also fixes the issue! I tried swapping the card order and then not exporting KWIN_DRM_DEVICES at all, and confirmed the System Settings -> About panel went back to showing RENOIR, and I can still Alt-Tab just fine. (I did also try KWIN_DRM_DEVICES once more and re-confirmed that the bug *does* come up in that case) > 3. set QT_LOGGING_RULES="kwin_*.debug=true", trigger the bug and upload the > output of "journalctl --boot 0 --user-unit plasma-kwin_wayland" here > afterwards I'm on Artix, which uses OpenRC (so no journalctl), *but*, I believe I figured out where that logging went (~/.local/share/sddm/wayland-session.log) and attached. I can already see something that looks suspicious, though - a whole lot of this around when I triggered the bug: kwin_wayland_drm: Presentation failed! Invalid argument kwin_wayland_drm: Atomic commit failed! This should never happen! Invalid argument kwin_wayland_drm: Flags: kwin_wayland_drm:DRM_MODE_PAGE_FLIP_EVENT Let me know if there's anything else you'd like me to test; I'm more than happy to help. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 --- Comment #10 from Gary Carter --- (also, while looking for what, exactly, 'KWIN_DRM_NO_DIRECT_SCANOUT' does, I stumbled on this bug filed against the AMD drivers: https://gitlab.freedesktop.org/drm/amd/-/issues/2075 ) So not sure then if this sounds like a Mesa or AMDGPU bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457096] Screen hangs when losing focus and refocusing fullscreen app/game while USB-C external monitor is set as primary monitor on laptop
https://bugs.kde.org/show_bug.cgi?id=457096 Gary Carter changed: What|Removed |Added Resolution|UPSTREAM|FIXED --- Comment #12 from Gary Carter --- Will do once my account registration there is approved - in the meantime, I'm assuming that the 'right' workaround is still switching the card order in KWIN_DRM_DEVICES, as it sounds like KWIN_DRM_NO_DIRECT_SCANOUT implies there could be other knock-on effects? (e.g. https://pointieststick.com/2021/02/05/this-week-in-kde-kwin-gains-direct-scan-out-and-gwenview-gets-a-lot-of-love/ mentions specifically that direct scan-out helps with latency & performance in games.. but that's assuming it works with the swapped cards here anyhow) Thanks again either way! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 429382] black icon with dark theme for Windows build.
https://bugs.kde.org/show_bug.cgi?id=429382 --- Comment #3 from Gary Wang --- Oh, by reading the comments in the newer bug report seems the fix you're working on is so much better approach than what I tried to do! Kdenlive could also get benefit from that patch :) About Craft build, I guess the gibberish output is just because it's printing Chinese in gb2312 encoding instead of UTF-8. I guess set language to English by using `[Threading.Thread]::CurrentThread.CurrentUICulture = 'en-US'` could be a solution but I haven't tried it out. I'll try to open bug report to Craft project once I got time to work on that. Thanks for the fix/update <3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433249] New: KDE System Settings crashed on startup - every time
https://bugs.kde.org/show_bug.cgi?id=433249 Bug ID: 433249 Summary: KDE System Settings crashed on startup - every time Product: systemsettings Version: 5.18.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: gary.d...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.4) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-65-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.2 LTS -- Information about the crash: On the indicated system, launching from the (Main -> Applications -> Preferences -> KDE System Settings) menu. Crashes every time with the same backtrace. I got as many dbgsym packages loaded for the backtrace as I could find. Let me know if there are other symbol table packages that would improve the trace. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fada241f080 (LWP 2249945))] Thread 5 (Thread 0x7fad99338700 (LWP 2249949)): #0 0x7fada9338aff in __GI___poll (fds=0x7fad880029e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fada734a18e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fada734a2c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fada98d4583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fada987b4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fada96b3785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fada89661a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fada96b49d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fada7ef2609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fada9345293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fad9ab05700 (LWP 2249948)): #0 __GI___libc_read (nbytes=16, buf=0x7fad9ab04b30, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=19, buf=0x7fad9ab04b30, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fada739289f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fada7349cde in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fada734a132 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fada734a2c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fada98d4583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fada987b4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fada96b3785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fada89661a9 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fada96b49d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fada7ef2609 in start_thread (arg=) at pthread_create.c:477 #12 0x7fada9345293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fada0feb700 (LWP 2249947)): #0 0x7fada739724d in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fada734a174 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fada734a2c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fada98d4583 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fada987b4db in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fada96b3785 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fada9b56efa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fada96b49d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fada7ef2609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fada9345293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fada1ad7700 (LWP 2249946)): #0 0x7fada9338aff in __GI___poll (fds=0x7fada1ad6c68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fada7eafc1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fada7eb190a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fada22d6298 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fada96b49d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fada7ef2609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fada9345293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread
[systemsettings] [Bug 433249] KDE System Settings crashed on startup - every time
https://bugs.kde.org/show_bug.cgi?id=433249 Gary Delp changed: What|Removed |Added Platform|Ubuntu Packages |Kubuntu Packages CC||gary.d...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433249] KDE System Settings crashed on startup - every time
https://bugs.kde.org/show_bug.cgi?id=433249 --- Comment #1 from Gary Delp --- Better Backtrace (more symbols loaded) Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a272f0080 (LWP 2319286))] Thread 5 (Thread 0x7f6a13fff700 (LWP 2319290)): #0 __GI___libc_read (nbytes=16, buf=0x7f6a13ffeb30, fd=21) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=21, buf=0x7f6a13ffeb30, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6a2c26389f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a2c21acde in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a2c21b132 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a2c21b2c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6a2e7a5583 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6a0c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7f6a2e74c4db in QEventLoop::exec(QFlags) (this=this@entry=0x7f6a13ffed40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7f6a2e584785 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7f6a2d8371a9 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7f6a2e5859d2 in QThreadPrivate::start(void*) (arg=0x55f55d971290) at thread/qthread_unix.cpp:361 #11 0x7f6a2cdc3609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f6a2e216293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6a1dc4f700 (LWP 2319289)): #0 0x7f6a2c21770d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6a2c219165 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a2c21a64b in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a2c21b0bb in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a2c21b2c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a2e7a5583 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6a14000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f6a2e74c4db in QEventLoop::exec(QFlags) (this=this@entry=0x7f6a1dc4ed40, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f6a2e584785 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f6a2d8371a9 in () at /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f6a2e5859d2 in QThreadPrivate::start(void*) (arg=0x55f55ceeb020) at thread/qthread_unix.cpp:361 #10 0x7f6a2cdc3609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f6a2e216293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f6a25ebe700 (LWP 2319288)): #0 __GI___libc_read (nbytes=16, buf=0x7f6a25ebdb20, fd=6) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=6, buf=0x7f6a25ebdb20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6a2c26389f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a2c21acde in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a2c21b132 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a2c21b2c3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f6a2e7a5583 in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f6a18000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #7 0x7f6a2e74c4db in QEventLoop::exec(QFlags) (this=this@entry=0x7f6a25ebdd30, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #8 0x7f6a2e584785 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #9 0x7f6a2ea27efa in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f6a2e5859d2 in QThreadPrivate::start(void*) (arg=0x7f6a2eaaad80) at thread/qthread_unix.cpp:361 #11 0x7f6a2cdc3609 in start_thread (arg=) at pthread_create.c:477 #12 0x7f6a2e216293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f6a269ab700 (LWP 2319287)): #0 0x7f6a2e209aff in __GI___poll (fds=0x7f6a269aac68, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a2cd80c1a in () at /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f6a2cd8290a in xcb_wait_for_event () at /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f6a271a5298 in () at /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f6a2e5859d2 in QThreadPrivate::start(void*) (arg=0x55f55cc59390) at thread/qthread_unix.cpp:361 #5 0x7f6a2cdc3609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6a2e216293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f6a272f0080 (LWP 2319286)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/
[plasmashell] [Bug 433297] New: Locale-aware alphabetic index/category in kickoff for non-English applications
https://bugs.kde.org/show_bug.cgi?id=433297 Bug ID: 433297 Summary: Locale-aware alphabetic index/category in kickoff for non-English applications Product: plasmashell Version: master Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: wzc782970...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Currently, the kickoff uses the first character in the application entry name to do the alphabetic indexing [1], makes non-English application also use its first character as an index/category. For CJK or other non-English users that have a lot of applications with non-English names, it'll be less useful and confused. [1] https://github.com/KDE/plasma-workspace/blob/a5c7df39460eff7454f992a2307753bfb1eb095f/applets/kicker/plugin/rootmodel.cpp#L374-L390 For example, in a Chinese locale environment, there are some applications names: * System Settings // just showcase what will happen if there are also English application * 音乐播放器 // Audio player in English, Yinyue bofangqi in pinyin. * 视频播放器 // Video player in English, Shipin bofangqi in pinyin * 游戏中心 // Game center in English, Youxi zhongxin in pinyin * 手机助手 // Phone manager in English, Shouji zhushou in pinyin There will be five indexes/categories in the current implementation, each index contains only one entry, like: S * System Settings 视 * 视频播放器 手 * 手机助手 音 * 音乐播放器 游 * 游戏中心 If we could do locale-aware alphabetic indexing, it could look like this, with two indexes/categories: S * System Settings * 视频播放器 * 手机助手 Y * 音乐播放器 * 游戏中心 ADDITIONAL INFORMATION In ICU, there is an AlphabeticIndex API [2] that can be used to create locale-aware alphabetic indexes. I didn't find the exact same alternative in Qt, not sure if there is in KDE. [2]: http://site.icu-project.org/design/alphabetic-index -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware alphabetic index/category in kickoff for non-English applications
https://bugs.kde.org/show_bug.cgi?id=433297 --- Comment #2 from Gary Wang --- (In reply to Mikel Johnson from comment #1) > Actually kickoff uses ListView's section group > (https://doc.qt.io/qt-5/qml-qtquick-listview.html#section.criteria-prop) Oh, seems I found the wrong one, but it seems both Kickoff, Kicker, and Application Dashboard are behave the same, is Application Dashboard also use the ListView's section group? And do I need to open two other bugs to report the Kicker and Application Dashboard behavior? By the way, where can I found the source code of the Application Dashboard applet? And is there a place to look up which applets are in which source repo? Thanks a lot! > Would be nice to get that fixed upstream, so everyone could enjoy the > benefits > > section.criteria: ViewSection.FirstCharacterRomanized or something like that Agree. I'll try to report a bug to upstream later if no one already reported it :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware alphabetic index/category in kickoff for non-English applications
https://bugs.kde.org/show_bug.cgi?id=433297 --- Comment #4 from Gary Wang --- > be sure to post the link here once you do Here you go https://bugreports.qt.io/browse/QTBUG-91258 :) btw since I don't know much about QML, so if you found anything that needs to be added to that bug report, please consider comment there :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433297] Locale-aware alphabetic index/category in kickoff for non-English applications
https://bugs.kde.org/show_bug.cgi?id=433297 --- Comment #6 from Gary Wang --- (In reply to Shawn Rutledge from comment #5) > I'm a bit surprised that Chinese people consider the first character of > modern pinyin a better index character than the ancient symbols that are > actually seen on the screen. Since there are a lot of Chinese characters than just 26 characters in English, if you have a bunch of Chinese apps on the screen with a different name, they could be very little chance to have a common first character, as the demo case mentioned in SUMMARY. > If a file clerk is organizing folders in a > paper file cabinet, is there an implicit order that they always use? Why > should digital apps be different? What's the convention in non-Qt contexts, > e.g. in native contacts apps on phones? No different, in Microsoft Windows start menu, Microsoft Launcher Android app, and LineageOS default contact app, they both sort and category in the first symbol in pinyin. And also, Chinese dictionaries also use the same way to sort and category characters. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439913] New: iNaturalist Export "Unknown Error" when click in Identification field
https://bugs.kde.org/show_bug.cgi?id=439913 Bug ID: 439913 Summary: iNaturalist Export "Unknown Error" when click in Identification field Product: digikam Version: 7.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-iNaturalist Assignee: digikam-bugs-n...@kde.org Reporter: ghu...@gmail.com Target Milestone: --- SUMMARY iNaturalist Export "Unknown Error" when click in Identification field STEPS TO REPRODUCE 1. ensure you've registered your iNaturalist account info into digiKam first 2. select one or a few jpg files (with valid date and GPS info and under 2000px per side dimension) 3. open "Export to iNaturalist" dialog 4. click in "Enter Identification" field 5. click "OK" to the "Unknown Error" message 6. at the cursor in the "enter ID" field, type in a taxon and select one of the iNat suggestions returned 7. click the "start uploading" button, wait 8. click "OK" to the (2nd) "Unknown Error" message OBSERVED RESULT at 4. an "Error - digiKam" pops up with "Unknown Error" message. at 7. another "Error - digiKam" pops up with "Unknown Error" message. (If the "resize image" check box is checked, there is a short delay before the error pops up.) The green progress bar shows 50% (if selected one photo, or 25% if selected 3 photos) but that progress never changes. If you now go to your iNat account directly, a new observation has been created but no image attached. Each time you repeat these steps, a new observation record created with the chosen taxa ID shown but without image(s). Also, whether or not the "write Photo-ID" to Source Image" is checked, I see no added ID info in the source image metadata. EXPECTED RESULT no error msgs, create iNat Observation record with attached image(s), see chosen taxa ID added to caption or description or keyword fields in source jpg file. SOFTWARE/OS VERSIONS Windows: 10 Pro 21H1 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 439913] iNaturalist Export "Unknown Error" when click in Identification field
https://bugs.kde.org/show_bug.cgi?id=439913 Gary Hundt changed: What|Removed |Added CC||ghu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436269] New: Not able to launch after upgrading from 20.12.3 to 21.04.0 under Windows
https://bugs.kde.org/show_bug.cgi?id=436269 Bug ID: 436269 Summary: Not able to launch after upgrading from 20.12.3 to 21.04.0 under Windows Product: kdenlive Version: 21.04.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: wzc782970...@gmail.com Target Milestone: --- SUMMARY Not able to launch after upgrading from 20.12.3 to 21.04.0 under Windows, using the installer. STEPS TO REPRODUCE 1. Get the 20.12.3 version installed using the 20.12.3 version installer 2. Install the 21.04.0 version using the installer 3. Try launch kdenlive.exe OBSERVED RESULT After the splash screen, there is a dialog that says it's crashed last time and asks if I need to reset the config file. If choose Yes, the dialog will be shown again and again, if choose No, the dialog disappeared and the kdenlive.exe process also disappeared (seems exited or crashed). EXPECTED RESULT The program can launch. SOFTWARE/OS VERSIONS Windows: 10 Home, 2H12, 19042.928 ADDITIONAL INFORMATION System language: Simplified Chinese Installer Hash: 7c397da79f3006eef17a6c4dc0511fc1e6752f4d19f1007859ead2c3f8eea0ad *kdenlive-21.04.0.exe Graphics Card: Intel(R) UHD Graphics 630 (It's a dual graphics card laptop, but it will use Integrated graphics by default, which is the Intel one) I also use Arch with KDE and already upgraded to kdenlive 21.04.0. It works fine. Not sure if this information could help. I'm not sure what other information needs to be provided so let me know if you need any additional information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 436269] Not able to launch after upgrading from 20.12.3 to 21.04.0 under Windows
https://bugs.kde.org/show_bug.cgi?id=436269 Gary Wang changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INTENTIONAL --- Comment #3 from Gary Wang --- Thanks! After uninstalling 20.12.3 and then install 21.04.0 instead of use the 21.04.0 installer to upgrade, it's able to launch now. It still shows the reset configuration dialog but after that, the program can run! I just notice on the download page from kdenlive.org it says "Windows: Uninstall old version. Then install version 21.04.0.", I probably missed this notice while I download at the first time. Sorry about that. I'll change the status to resolve then. Thanks again for the help! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436331] New: Kate 21.04 from Binary Factory stable build crash at launch
https://bugs.kde.org/show_bug.cgi?id=436331 Bug ID: 436331 Summary: Kate 21.04 from Binary Factory stable build crash at launch Product: kate Version: 21.04.0 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: wzc782970...@gmail.com Target Milestone: --- SUMMARY Kate 21.04 downloaded from Binary Factory stable build crash at launch. STEPS TO REPRODUCE 1. Download Kate from binary factory (kate-21.04.0-1259-windows-msvc2019_64-cl.exe) 2. Install it 3. Try launch kate.exe OBSERVED RESULT kate.exe crashed at launch EXPECTED RESULT It can launch normally SOFTWARE/OS VERSIONS Windows: 10 Home, 20H2 19042.928 ADDITIONAL INFORMATION System Language: Simplified Chinese Crash log generated by drmingw: kate.exe caused an Unknown [0xC374] Exception at location 7FFEF654F0B9 in module ntdll.dll. AddrPC Params 7FFEF654F0B9 7FF62637BE10 000D1BEFEBE0 014184F9 ntdll.dll!RtlIsZeroMemory 7FFEF654F083 0080 7FFEF65B77F0 000F ntdll.dll!RtlIsZeroMemory 7FFEF6557E02 000F 0030 01418508 ntdll.dll!RtlpNtSetValueKey 7FFEF65580EA 01418CB95400 001B 01418CB9F030 ntdll.dll!RtlpNtSetValueKey 7FFEF655DD71 02820360 001B 01418CB9F030 ntdll.dll!RtlpNtSetValueKey 7FFEF650284F 014184F9 0020 ntdll.dll!memset 7FFEF647B3C7 0020 000D1BEFCFA8 ntdll.dll!RtlAllocateHeap 7FFEF41AFDE6 0008 0008 ucrtbase.dll!_malloc_base 7FFE77000DE1 000D1BEFD218 0004 Qt5Core.dll!QArrayData::allocate 7FFE770899CF 0044 000D1BEFD278 Qt5Core.dll!QString::reallocData 7FFE76FD24FF 01418CB56800 0001 Qt5Core.dll!QString::operator+= 7FFE8DCCE38D 01418CB568C0 000D1BEFD218 000D1BEFD280 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DCB4466 01418CB951A0 7FFE772724E0 0080 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DC97AE8 01418CB568C0 01418CB951A0 01410080 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DC8FCB9 01418CB568C0 01418A5EA6C0 01418CB329A0 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DCB0DE1 01418CB329A0 01418CB568C0 01418A4448F0 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DC58D59 01418CA47DD0 01418A5EA6C0 01418CB329A0 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DC5A243 01418CAC2508 01418CAC2520 01418CA47DD0 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DB8B2ED 01418A5EA6C0 01418A5EA950 0141 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DB5BE81 01418A5E9DF0 01418517BEE0 01418517BEE0 KF5TextEditor.dll!Kate::TextLineData::firstChar 7FFE8DA6C25C 01418A5E9DF0 7FFE8DDBE808 001B002E KF5TextEditor.dll!Kate::TextLineData::firstChar 7FF6263122F0 01418CAD1A10 01418C4BCB70 01418517BEE0 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262A035B 01418517BEE0 01418517BEE0 01418C4BCB70 kate.exe!cleanupRunningKateAppInstanceMap 7FF6263159AC 01418CAD1A10 01418A4FBCF0 01418CAD1A10 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262A4FFA 000D1BEFE468 01418A5D8AD8 01418A4FBCF0 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262A55D9 000D1BEFE600 000D1BEFE620 01410001 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262AE1A8 01418A3C76D0 01418A50A500 000D1BEFE6B0 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262803CB 000D1BEFE760 01418A3C76D0 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262D203D 000D1BEFE940 000D1BEFE900 000D1BEFF701 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262CF0A3 000D1BEFF750 000D1BEFE940 01418A43B100 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262CEBAA 000D1BEFF750 000D0002 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262CEB46 7FFE772724E0 kate.exe!cleanupRunningKateAppInstanceMap 7FF6262CFF08 0003 kate.exe!cleanupRunningKateAppInstanceMap 7FF626282352 000D1BEFEC00 000D 7FF626398C20 kate.exe!cleanupRunningKateAppInstanceMap 7FF62627FE32 000D1BEFF6A0 01418A4FB500 0141850B0020 kate.exe!cleanupRunningKateAppInstanceMap 7FF626279DE4 0001 0141850F5A00 kate.exe!cleanupRunningKateAppInstanceMap 7FF62
