[lokalize] [Bug 412837] New: Make translation units searchable by metadata/file reference
https://bugs.kde.org/show_bug.cgi?id=412837 Bug ID: 412837 Summary: Make translation units searchable by metadata/file reference Product: lokalize Version: 19.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: editor Assignee: sdepi...@gmail.com Reporter: aspotas...@gmail.com CC: sha...@ukr.net Target Milestone: --- SUMMARY Make translation units searchable by metadata/file reference. Use case: Filter all messages in www_www.po that come from file plasma-5.17.0.php. For now these can be found with Pology, but not using just Lokalize tools: posieve find-messages -sntransl -scomment:'plasma-5.17.0.php' www_www.po I see two approaches to fulfill the use case: 1. Add column "unit metadata" in the Translation Units panel and make it searchable. 2. Organize messages in the Translation Units panel in a tree view where top-level nodes represent source file references. Would be similar to how Qt Linguist works. I know there will be duplicate messages across different files, we can just display them multiple times in the tree view. Example: + dolphincontextmenu.cpp . "Empty Trash" . "Restore" . "Create New" + panels/places/placespanel.cpp . "Empty Trash" . "Show Hidden Places" 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.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 --- Comment #11 from Rober --- (In reply to Lê Hoàng Phương from comment #10) > This bug doesn't happen to me on X11 but on Wayland only. I use X11 and I have this bug -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412429] No display of transactions in the tags view when tags are specified in a split
https://bugs.kde.org/show_bug.cgi?id=412429 Ralf Habacker changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kmy ||money/65461d923923c4f0b163b ||c790a63463dbcc8b5b7 Version Fixed In||5.0.8 --- Comment #13 from Ralf Habacker --- Git commit 65461d923923c4f0b163bc790a63463dbcc8b5b7 by Ralf Habacker. Committed on 11/10/2019 at 05:21. Pushed by habacker into branch '5.0'. Fix 'No display of transactions in the tags view when tags are specified in a split' Since it is currently not clear whether this change will lead to unwanted side effects at other code locations, the new method setConsiderCategorySplits() has been added to enable this functionality. FIXED-IN:5.0.8 Test Plan: tested on linux with mymoneytransactionsfiltertest Reviewed By: tbaumgart, #kmymoney Differential Revision: https://phabricator.kde.org/D24426 M +10 -1kmymoney/mymoney/mymoneytransactionfilter.cpp M +10 -0kmymoney/mymoney/mymoneytransactionfilter.h M +5-2kmymoney/mymoney/tests/mymoneytransactionfilter-test.cpp M +1-0kmymoney/views/ktagsview.cpp https://commits.kde.org/kmymoney/65461d923923c4f0b163bc790a63463dbcc8b5b7 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406403] Tags within Split transaction not reporting correctly
https://bugs.kde.org/show_bug.cgi?id=406403 Bug 406403 depends on bug 412429, which changed state. Bug 412429 Summary: No display of transactions in the tags view when tags are specified in a split https://bugs.kde.org/show_bug.cgi?id=412429 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404527] When excluding a tag from a report the information reported is incorrect
https://bugs.kde.org/show_bug.cgi?id=404527 Bug 404527 depends on bug 412429, which changed state. Bug 412429 Summary: No display of transactions in the tags view when tags are specified in a split https://bugs.kde.org/show_bug.cgi?id=412429 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 412836] Checkboxes under "Searchable column" act like radiobuttons
https://bugs.kde.org/show_bug.cgi?id=412836 Alexander Potashev changed: What|Removed |Added Version|19.07.80|19.08.1 -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 412836] New: Checkboxes under "Searchable column" act like radiobuttons
https://bugs.kde.org/show_bug.cgi?id=412836 Bug ID: 412836 Summary: Checkboxes under "Searchable column" act like radiobuttons Product: lokalize Version: 19.07.80 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: sdepi...@gmail.com Reporter: aspotas...@gmail.com CC: sha...@ukr.net Target Milestone: --- SUMMARY Checkboxes under "Searchable column" act like radiobuttons. Only one option can be selected in the Translation Units' "options" menu under "Searchable column", thus the menu items should look like radiobuttons. However at the moment they look like checkboxes. 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: 5.62.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION lokalize 19.08.1 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 406466] When adding more than one album at a time to the playlist, songs are added in mixed-up order
https://bugs.kde.org/show_bug.cgi?id=406466 Matthieu Gallien changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||elisa/commit/cccafdff17a3b7 ||dfcca97d49f8598757abb3dbda --- Comment #4 from Matthieu Gallien --- Git commit cccafdff17a3b7dfcca97d49f8598757abb3dbda by Matthieu Gallien. Committed on 09/10/2019 at 05:02. Pushed by mgallien into branch 'master'. insert album tracks at the correct place instead of at the end Summary: inserting the tracks not at the end fix the bug detected by QAbstractItemModelTester which is really a nice tool Test Plan: new test is OK, no regressions Reviewers: #elisa, ngraham, astippich, jguidon Differential Revision: https://phabricator.kde.org/D24271 M +143 -0autotests/mediaplaylisttest.cpp M +2-0autotests/mediaplaylisttest.h M +2-2src/mediaplaylist.cpp https://invent.kde.org/kde/elisa/commit/cccafdff17a3b7dfcca97d49f8598757abb3dbda -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 412346] Personal settings not being saved
https://bugs.kde.org/show_bug.cgi?id=412346 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411664] clicking on a certain brush preset crashes software
https://bugs.kde.org/show_bug.cgi?id=411664 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412160] Kwin (Kwin_x11) segmentation fault causes by libthread_db.
https://bugs.kde.org/show_bug.cgi?id=412160 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412781] Various graphical glitches since Qt5.14
https://bugs.kde.org/show_bug.cgi?id=412781 Pawel changed: What|Removed |Added CC||pavbara...@gmail.com --- Comment #8 from Pawel --- (In reply to mthw0 from comment #0) Try to upgrade your system to current version of package in kde-unstable (there is qt5-svg with fix patch). Those changes resolved this problem in my system. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412835] Random assert message
https://bugs.kde.org/show_bug.cgi?id=412835 --- Comment #1 from acc4commissi...@gmail.com --- I was just drawing and nothing alse was going on in the canvas. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412835] New: Random assert message
https://bugs.kde.org/show_bug.cgi?id=412835 Bug ID: 412835 Summary: Random assert message Product: krita Version: nightly build (please specify the git hash!) Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- Created attachment 123141 --> https://bugs.kde.org/attachment.cgi?id=123141=edit capture SUMMARY git 56ee905 Krita was autosaving when this poped up, but I'm not sure those are related. SOFTWARE/OS VERSIONS Windows: Win7 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.
[konsole] [Bug 412705] Konsole leaves hundreds of megabytes in thousands of temp history files
https://bugs.kde.org/show_bug.cgi?id=412705 --- Comment #9 from Kurt Hindenburg --- We could revert https://invent.kde.org/kde/konsole/commit/660559600f1663e4538611870d1fcde418e55704 - and perhaps just leave a note when debugging history files to re-add it. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412705] Konsole leaves hundreds of megabytes in thousands of temp history files
https://bugs.kde.org/show_bug.cgi?id=412705 --- Comment #8 from Mariusz Glebocki --- Fix: https://invent.kde.org/kde/konsole/merge_requests/39 Should also work on systems where QTemporaryFile does not create unnamed files. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412621] Creating a folder in desktop which starts with ":" will create it in home instead of desktop
https://bugs.kde.org/show_bug.cgi?id=412621
--- Comment #3 from David Edmundson ---
It goes in this path
if (QDir::isAbsolutePath(name)) {
url = QUrl::fromLocalFile(name);
which exists if you click mkdir and then type (for some reason)
"/home/david/fullpath/fullpath'
input ":foo" ends up with the final url ends up being "file::foo"
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 412621] Creating a folder in desktop which starts with ":" will create it in home instead of desktop
https://bugs.kde.org/show_bug.cgi?id=412621 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #2 from David Edmundson --- Some finds: It doesn't created it in your home folder, it gets created in the CWD. It's not unique to desktop:// if you make a folder in file:///home/david/foo called :something it still goes into another folder -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385359] Plasmashell crashes repeatedly
https://bugs.kde.org/show_bug.cgi?id=385359 David Edmundson changed: What|Removed |Added Component|general |generic-crash Assignee|k...@davidedmundson.co.uk|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 411256] Track ordering does not work as expected
https://bugs.kde.org/show_bug.cgi?id=411256 --- Comment #5 from rita...@fastmail.com --- 19.08.2 definitely improved it but "split audio tracks" still does not order properly for me after adding a new av track. A1 and V1 are not in the correct position. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412834] New: "Cannot refresh cache whilst offline" -- except I'm online.
https://bugs.kde.org/show_bug.cgi?id=412834 Bug ID: 412834 Summary: "Cannot refresh cache whilst offline" -- except I'm online. Product: Discover Version: 5.16.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: hgc...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY "Cannot refresh cache whilst offline" -- except I'm not offline, obviously since I'm filing this report. STEPS TO REPRODUCE 1. Click the icon indicating updates are available in the task bar 2. Click 'check for updates'. 3. Notice it gives an error message and does nothing of any use. System is the latest Ubuntu 'eoan', though this bug has been around for a long time. My system's network is configured via systemd/networkd as is indicated in /etc/netplan. I don't use the network manager for anything. This bug appears whether the disused network-manager is enabled or disabled in systemd, or is running or not running. 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.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 Lê Hoàng Phương changed: What|Removed |Added CC||herophuon...@gmail.com --- Comment #10 from Lê Hoàng Phương --- This bug doesn't happen to me on X11 but on Wayland only. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412833] New: Monthview shows comma in year
https://bugs.kde.org/show_bug.cgi?id=412833 Bug ID: 412833 Summary: Monthview shows comma in year Product: korganizer Version: 5.12.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: kdeb...@trevorparsons.com Target Milestone: --- Created attachment 123140 --> https://bugs.kde.org/attachment.cgi?id=123140=edit Screenshot of part of korganizer window showing comma in year in monthview SUMMARY In the month view of Korganizer, the year contains a comma, as if it were a normal numeral. STEPS TO REPRODUCE 1. Start Korganizer 2. Switch to month view OBSERVED RESULT The year contains a comma. For example, at the time of reporting the month and year are shown as "October 2,019". EXPECTED RESULT The year should not contain a comma. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.3.5-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.16.90 KDE Frameworks Version: 5.62.0 Qt Version: 5.14.0 (built against 5.13.1) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 412677] Runtime error - file was compiled ahead of time
https://bugs.kde.org/show_bug.cgi?id=412677 --- Comment #2 from Sebastian Gottfried --- Git commit cb5792c6e9c72d9cc02e93223c86c793c0157b79 by Sebastian Gottfried. Committed on 10/10/2019 at 23:22. Pushed by gottfried into branch 'Applications/19.08'. Disable QML Precompilation by Default The reduction of the time the app needs to launch because the precompiled QML files is neglible, but we still get bug reports because people try to run KTouch builds against newer Qt releases which doesn't work. So from now on, this feauture must be turned on explicitely to reduce further fallout. M +1-1CMakeLists.txt https://commits.kde.org/ktouch/cb5792c6e9c72d9cc02e93223c86c793c0157b79 -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 412832] New: Cannot create vaults
https://bugs.kde.org/show_bug.cgi?id=412832 Bug ID: 412832 Summary: Cannot create vaults Product: Plasma Vault Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: prmsr...@gmail.com Target Milestone: --- SUMMARY Vault creation fails on Arch Linux with message "Unable to perform the operation (error code 9).". I cannot find anywhere what error code 9 means. STEPS TO REPRODUCE 1. Create new vault using CryFS as backend OBSERVED RESULT Vault creation failed with error code 9 EXPECTED RESULT Vault should be created successfully SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 CryFS Version: 0.10.2 ADDITIONAL INFORMATION respecitve folders in ~/Vaults and ~/.local/share/plasma-vault/ are created but are empty -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #39 from Mau --- Let's vote this bug in order to rise severity. I'm not updating since v1.10.1. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412831] New: Filter for custom properties have to be prefixed with v_operation_display_all
https://bugs.kde.org/show_bug.cgi?id=412831 Bug ID: 412831 Summary: Filter for custom properties have to be prefixed with v_operation_display_all Product: skrooge Version: Trunk from git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: bernhard+...@scheirle.de CC: steph...@mankowski.fr Target Milestone: --- Hi, previously in 2.20 you could filter the operations list for custom properties. For example the search string: "-myproperty.:myvar" would remove all operations having a custom property "myproperty" set to the value "myvar". In the current trunk custom properties have to be prefixed with "v_operation_display_all". E.g. "-v_operation_display_all.myproperty.:myvar" to achieve the same filter as above. That seems strange. Regards Bernhard -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #2 from philip mirabelli --- Hi, just tried editing an .rtf file and it does the same thing - bug report attached. I also tried with a .doc file and it seems to be ok with those, regards On Thu, 2019-10-10 at 19:41 +, Elvis Angelaccio wrote: > https://bugs.kde.org/show_bug.cgi?id=412791 > > --- Comment #1 from Elvis Angelaccio --- > Version of kio-gdrive and libkgapi? Does it crash with every word > file? > -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 412360] All items entered are gone
https://bugs.kde.org/show_bug.cgi?id=412360 --- Comment #22 from Dave --- Since my last email and having removed (I believe) every file associated with the previous version 2.15.0 l had gone to my Package Manager as you had previously mentioned and selected the installation of the program using the Flathub.org installation.All looked promising until the end of the install as you can see in the attached copy of my terminal.I was left with the Skrooge icon in my "Office" file and when i selected it there was an image of the new Skrooge label that read it was the 2.20.0 version which looked good..but it would not load the program.This is the last attempt l have made as evidenced by the screenshot of the terminal and l am again hoping you may offer a solution.RegardsDave On Wednesday, October 9, 2019, 01:44:56 p.m. EDT, Stephane MANKOWSKI wrote: https://bugs.kde.org/show_bug.cgi?id=412360 --- Comment #20 from Stephane MANKOWSKI --- Yes in settings -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356006] Breeze GTK does not respect the color scheme
https://bugs.kde.org/show_bug.cgi?id=356006 --- Comment #9 from Guo Yunhe --- Good job! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 412830] New: The key sequence 'U' is ambiguous
https://bugs.kde.org/show_bug.cgi?id=412830 Bug ID: 412830 Summary: The key sequence 'U' is ambiguous Product: kmail2 Version: 5.9.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: luca-...@llucax.com Target Milestone: --- SUMMARY Out of the blue, without touching anyting (although it might have been after some upgrade of some KDE component, not KMail), I started to get this message when trying to use the 'U' shortcut to mark messages as unread: The key sequence 'U' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered. I looked in the shortcuts configuration and there is nothing else bound to `U`, not even in the global KDE shortcuts defined in the KDE Settings. STEPS TO REPRODUCE 1. Open KMail 2. Select an e-mail 3. Press the "U" letter in the keyboard OBSERVED RESULT A dialog with this message is shown: The key sequence 'U' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered. EXPECTED RESULT The message is marked as unread. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable, kde version 5:104 (from the debian package) KDE Plasma Version: 5.14.5.1 (?). Is the version of the plasma-desktop package KDE Frameworks Version: ? Qt Version: ? ADDITIONAL INFORMATION If I remove the binding for 'U' from the shortcuts config and then press 'U', there is no visible effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411637] plasmashell leaks shared memory segments. Eventually apps needing these (oracle) fail
https://bugs.kde.org/show_bug.cgi?id=411637 --- Comment #6 from Jeremy Harding --- hmm, I tried all the activity switchers that I could find, and they all exhibit a similar problem. Which activity switching mechanism did you use which didn't please? One of them seemed to waste less memory, which is good, and has a smaller panel footprint which is very good. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 412778] digikam 6.3.0 appimage fails to run on centos 7.6
https://bugs.kde.org/show_bug.cgi?id=412778 --- Comment #5 from Simon J Mudd --- ok, so I searched around and found this: $ sudo yum install jack-audio-connection-kit That seems to fix the libjack.so issue. So I try again: $ ./digikam-6.4.0-git-20191005T120037-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Note: to integrate this bundle to your desktop, use AppImageLauncher. libudev.so.0 -- Preloading shared libs: digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamcore.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamcore.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamcore.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamdatabase.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamdatabase.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamgui.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamgui.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libdigikamgui.so.6.4.0) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Sql.so.5) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libMagick++-7.Q16.so.4) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libMagick++-7.Q16.so.4) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Network.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5DBus.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Xml.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Widgets.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Gui.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Concurrent.so.5) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Core.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Core.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5Core.so.5) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5XmlPatterns.so.5) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libexiv2.so.27) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libexiv2.so.27) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libmarblewidget-qt5.so.28) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/liblensfun.so.2) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libopencv_objdetect.so.3.4) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libopencv_objdetect.so.3.4) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libopencv_imgcodecs.so.3.4) digikam: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5PrintSupport.so.5) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5WebKit.so.5) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libQt5WebKit.so.5) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libopencv_calib3d.so.3.4) digikam: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/.mount_digikaidWKaV/usr/lib/libopencv_features2d.so.3.4) digikam: /lib64/libstdc++.so.6: version
[zanshin] [Bug 411339] zanshin fails to run on neon
https://bugs.kde.org/show_bug.cgi?id=411339 kde-b...@cerritus.eu changed: What|Removed |Added CC||kde-b...@cerritus.eu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 412829] New: KMessageWidget: Wrong vertical size after show animation with word-wrap enabled
https://bugs.kde.org/show_bug.cgi?id=412829 Bug ID: 412829 Summary: KMessageWidget: Wrong vertical size after show animation with word-wrap enabled Product: frameworks-kwidgetsaddons Version: 5.62.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: sgd.or...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 123137 --> https://bugs.kde.org/attachment.cgi?id=123137=edit Video recording of the mentioned behaviour. SUMMARY The message widget resizes wrongly after animation with word-wrap enabled. STEPS TO REPRODUCE 1. Enable word-wrap 2. set text to something which will be wrapped with default size, let it resize (or qt resize ?) 3. observe OBSERVED RESULT - The widget picked the initial size (width and height) while the toolview size was not determined and started animation with these values. Small width and big height in this case. - After animation finished the coloured message box was resized to match the size of the toolview. It matched the width and adjusted its height as needed. - After it finished it left the black vertical space between its own coloured message box and other elements in layout. - When the massage box is closed by clicking on the big X, the message box is gone and the excess space is also removed, when the message box shows next it picks the current size of the toolview. EXPECTED RESULT The widget properly takes care of the required space and adjust accordingly without leaving blank space. SOFTWARE/OS VERSIONS Operating System: Artix Linux KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 Kernel Version: 4.19.74-1-lts OS Type: 64-bit ADDITIONAL INFORMATION I found this during tweaking KDevelop`s plugin fileteplates and its TemplatePreviewToolview. The bug appears when the toolview "Template Preview" is added to some dock, if word-wrap is enabled. The required changes to KDevelop to reproduce the bug can be found in KDE GitLab. https://invent.kde.org/kde/kdevelop/merge_requests/68 -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 412827] default logging location not useful
https://bugs.kde.org/show_bug.cgi?id=412827 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 412826] Server Authenticity check dialog pops up on startup and on wake from sleep, even though the certificate is saved forever.
https://bugs.kde.org/show_bug.cgi?id=412826 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412828] New: Color selector crashed the program
https://bugs.kde.org/show_bug.cgi?id=412828 Bug ID: 412828 Summary: Color selector crashed the program Product: krita Version: 4.2.6 Platform: Other OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Tools/Colorize Assignee: krita-bugs-n...@kde.org Reporter: nya.thecuteness.na...@gmail.com Target Milestone: --- Idk how or why the program simply stopped responding after it decided i clicked to select a color rather than reseting them to black and white and crashed the entire program, im assuming somehow the system overwhelmed itself with the most simple of functions. while im here the setup for the solor selector is disgustingly cluttered i liked it to be significantly more simplified like it used to be -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 412791] Uploading a docx file causes a crash
https://bugs.kde.org/show_bug.cgi?id=412791 --- Comment #1 from Elvis Angelaccio --- Version of kio-gdrive and libkgapi? Does it crash with every word file? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 356006] Breeze GTK does not respect the color scheme
https://bugs.kde.org/show_bug.cgi?id=356006 Nate Graham changed: What|Removed |Added CC||i...@guoyunhe.me --- Comment #8 from Nate Graham --- *** Bug 400101 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 400101] Look & feel change doesn't affect GTK application settings
https://bugs.kde.org/show_bug.cgi?id=400101 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nate Graham --- This was fixed by Bug 356006! *** This bug has been marked as a duplicate of bug 356006 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412813] Changes in report not taken into account
https://bugs.kde.org/show_bug.cgi?id=412813 --- Comment #4 from Thomas Baumgart --- That is more of a question for kubuntu. The KMyMoney project provides the source tarballs for them and they need to pick it up. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 --- Comment #3 from stuart --- Ok, I didn't suspect that since it is communicating with the database. Just that the query fails and Akonadi shuts down. On Thu, Oct 10, 2019 at 9:20 PM Sandro Knauß wrote: > https://bugs.kde.org/show_bug.cgi?id=412629 > > Sandro Knauß changed: > >What|Removed |Added > > > CC||skna...@kde.org > Status|REPORTED|CONFIRMED > Ever confirmed|0 |1 > > --- Comment #2 from Sandro Knauß --- > Keep in mind, that even Qt does not support Postgres 12 atm, so in first > glance > there needs to be a bug filed against Qt: > > > https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp#n1080 > > also in Debian this bug is reported: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941763 > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412813] Changes in report not taken into account
https://bugs.kde.org/show_bug.cgi?id=412813 --- Comment #2 from Patrick --- Thanks Thomas, but how to upgrade. It comes from kubuntu package which proposes only 5.0.1-2 Le 10/10/2019 à 19:40, Thomas Baumgart a écrit : > https://bugs.kde.org/show_bug.cgi?id=412813 > > Thomas Baumgart changed: > > What|Removed |Added > > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > > --- Comment #1 from Thomas Baumgart --- > This was fixed in the meantime. Please update to current 5.0.7 > -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 412827] New: default logging location not useful
https://bugs.kde.org/show_bug.cgi?id=412827 Bug ID: 412827 Summary: default logging location not useful Product: konversation Version: 1.7.5 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: logging Assignee: konversation-de...@kde.org Reporter: lang...@fedoraproject.org Target Milestone: --- If you enable logging in konversation in a flatpak, the default location for those logs is not persistent across runs of the software. Obviously, this kind of defeats the purpose of enabling logging. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 412826] New: Server Authenticity check dialog pops up on startup and on wake from sleep, even though the certificate is saved forever.
https://bugs.kde.org/show_bug.cgi?id=412826 Bug ID: 412826 Summary: Server Authenticity check dialog pops up on startup and on wake from sleep, even though the certificate is saved forever. Product: konversation Version: 1.7.5 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: lang...@fedoraproject.org Target Milestone: --- I use konversation in a flatpak on Fedora Silverblue (f31 beta atm) against a znc server with a self-signed cert and the "accept cert forever" function seems to not be working. I get the prompt every time I start konversation and every time my computer wakes from sleep (or any network disconnect). I thought at first this might be not having persistence where this was flag was stored might be the problem however, the wake from sleep scenario makes me think this is not it. I can confirm, on f30 (and maybe f31) with a native install this was working with my setup. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 Sandro Knauß changed: What|Removed |Added CC||skna...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Sandro Knauß --- Keep in mind, that even Qt does not support Postgres 12 atm, so in first glance there needs to be a bug filed against Qt: https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers/psql/qsql_psql.cpp#n1080 also in Debian this bug is reported: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941763 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 412825] New: With automatic login enabled, kwallet doesn't ask for password fast enough for enabling network
https://bugs.kde.org/show_bug.cgi?id=412825 Bug ID: 412825 Summary: With automatic login enabled, kwallet doesn't ask for password fast enough for enabling network Product: kwalletmanager Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: va...@kde.org Reporter: adam.golan...@gmail.com Target Milestone: --- SUMMARY On the systems with Auto Login enabled (Startup and Shutdown > Login Screen > Advanced), soon after launch Network Manager tries to initialize the Wi-Fi network for about 10 seconds – and fails miserably, as it doesn't have access to the Wi-Fi password Only then Wallet asks for user password, provides it to Network Manager, so the user can start Wi-Fi connection manually. While it is probably not a bug per se, its bad UX. It would be nice if: 1. Wi-Fi passwords on systems with automatic login enabled would be accessible for network manager without providing user password. If it is not possible due to security reasons, then at least: 2. Turning auto login ON would switch automatic wifi connection OFF, or 3. Kwallet asks for user password to unlock access to Wi-Fi password quickly enough for Network Manager to connect to Wi-Fi at first attempt. STEPS TO REPRODUCE 1. Switch the login style to Auto Login 2. Have a set up automatic wi-fi connection with password (like WPA2) OBSERVED RESULT Wi-Fi connection fails after autologin and only then wallet system asks for user password EXPECTED RESULT Seamless wifi connection on autologin systems Linux/KDE Plasma: Neon 5.16 (available in About System) KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.3 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 408830] skanlite.snap not recognize scan wireless
https://bugs.kde.org/show_bug.cgi?id=408830 --- Comment #4 from Lvaskz --- any progress? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412684] [Wayland] kwin_wayland[3904]: segfault at 10 ip 00007f35691b6c30 sp 00007ffcf514ce98 error 4 in libKF5WaylandServer.so.5.63.0[7f3569191000+60000]
https://bugs.kde.org/show_bug.cgi?id=412684 --- Comment #4 from Tony --- I've tried with 2 more recent video cards, HD 7700 and R9 280 both using amdgpu driver instead of radeon. Same result in both cases. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412693] Show zoom level with named zoom levels
https://bugs.kde.org/show_bug.cgi?id=412693 Nate Graham changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- Thanks for understanding! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412824] "Warning: QT_AUTO_SCREEN_SCALE_FACTOR is deprecated."
https://bugs.kde.org/show_bug.cgi?id=412824 Antonio Rojas changed: What|Removed |Added Latest Commit||a0a80c67f91cd52baf8f349b71f ||587c09820054e Version Fixed In||5.17.0 Resolution|--- |FIXED CC||aro...@archlinux.org Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- Already fixed in 5.17 final -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412822] idk
https://bugs.kde.org/show_bug.cgi?id=412822 --- Comment #2 from Michail Vourlakos --- how to you reproduce this? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407000] "Defaults" button in "Global shortcuts" kcm sets all shortcuts of the task switcher to "None"
https://bugs.kde.org/show_bug.cgi?id=407000 Luca Weiss changed: What|Removed |Added CC||l...@z3ntu.xyz -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 412813] Changes in report not taken into account
https://bugs.kde.org/show_bug.cgi?id=412813 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Thomas Baumgart --- This was fixed in the meantime. Please update to current 5.0.7 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 412693] Show zoom level with named zoom levels
https://bugs.kde.org/show_bug.cgi?id=412693 --- Comment #4 from mthw0 --- I don't have arguments to support this idea. If you feel like it doesn't belong here, please close this issue, I won't mind. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412824] New: "Warning: QT_AUTO_SCREEN_SCALE_FACTOR is deprecated."
https://bugs.kde.org/show_bug.cgi?id=412824 Bug ID: 412824 Summary: "Warning: QT_AUTO_SCREEN_SCALE_FACTOR is deprecated." Product: plasmashell Version: 5.16.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: matejm98m...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY "...Instead use: QT_ENABLE_HIGHDPI_SCALING to enable platform plugin controlled per-screen factors." Every time I start any app from terminal, I get this message. I guess it's meant for devs rather than users, right? Since Qt5.14 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412823] New: Please add a refresh function.
https://bugs.kde.org/show_bug.cgi?id=412823 Bug ID: 412823 Summary: Please add a refresh function. Product: kdeconnect Version: unspecified Platform: Other OS: Android 9.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: g...@g4b.org Target Milestone: --- SUMMARY If your device is not found, closing and reopening the app, lately even force stop does not work. I have to use another phone to connect. Or restart my phone. Would be awesome if there was a refresh button which manually starts to search for the currently opened device E.g. if I open KDE connect from another room and walk into the area I could connect -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 364149] I was working on an art piece and I saved it as a new krita file. I try and open the file the next day and it comes up with a message that says that the file cannot be opened beca
https://bugs.kde.org/show_bug.cgi?id=364149 Mary changed: What|Removed |Added CC||marywchaf...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412822] idk
https://bugs.kde.org/show_bug.cgi?id=412822 --- Comment #1 from zuri --- Comment on attachment 123133 --> https://bugs.kde.org/attachment.cgi?id=123133 description bug >Application: latte-dock (0.9.3) > >Qt Version: 5.13.1 >Frameworks Version: 5.62.0 >Operating System: Linux 5.3.5-zen1-1-zen x86_64 >Distribution: "Arch Linux" > >-- Information about the crash: >- What I was doing when the application crashed: >idk >no lo se, escribo esto en español, espero y puedan traducirlo jejeje... >de un pronto a otro el latte dock empezo a parpadear mucho sin caso alguno, vi >que cambiaba el icono de una aplicacion y lo volvia a restablecer, lo que hice >fue quitarla de el dock esa aplicacion y ahi se soluciono, luego la volvi a >añadir y el dock parece que se reinicio, no entiendo muy bien lo que sucedio >la verdad, estaba abierto el chrome y el wps writter... nada mas, les >agradezco. espero no sea de molestia que esto lo este haciendo en español, >puesto que es mi idioma nativo y el ingles se me complica un poco.. gracias > >The crash can be reproduced sometimes. > >-- Backtrace: >Application: Latte Dock (latte-dock), signal: Segmentation fault >Using host libthread_db library "/usr/lib/libthread_db.so.1". >[Current thread is 1 (Thread 0x7f9e20447e40 (LWP 887))] > >Thread 9 (Thread 0x7f9e01577700 (LWP 1106)): >#0 0x7f9e23eeec45 in pthread_cond_wait@@GLIBC_2.3.2 () at >/usr/lib/libpthread.so.0 >#1 0x7f9e2508f660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at >/usr/lib/libQt5Core.so.5 >#2 0x7f9e2508f752 in QWaitCondition::wait(QMutex*, unsigned long) () at >/usr/lib/libQt5Core.so.5 >#3 0x7f9e26d63dad in () at /usr/lib/libQt5Quick.so.5 >#4 0x7f9e26d6405e in () at /usr/lib/libQt5Quick.so.5 >#5 0x7f9e250895b0 in () at /usr/lib/libQt5Core.so.5 >#6 0x7f9e23ee84cf in start_thread () at /usr/lib/libpthread.so.0 >#7 0x7f9e24bb52d3 in clone () at /usr/lib/libc.so.6 > >Thread 8 (Thread 0x7f9e021bd700 (LWP 1068)): >#0 0x7f9e23eeec45 in pthread_cond_wait@@GLIBC_2.3.2 () at >/usr/lib/libpthread.so.0 >#1 0x7f9e2508f660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at >/usr/lib/libQt5Core.so.5 >#2 0x7f9e2508f752 in QWaitCondition::wait(QMutex*, unsigned long) () at >/usr/lib/libQt5Core.so.5 >#3 0x7f9e26d63dad in () at /usr/lib/libQt5Quick.so.5 >#4 0x7f9e26d6405e in () at /usr/lib/libQt5Quick.so.5 >#5 0x7f9e250895b0 in () at /usr/lib/libQt5Core.so.5 >#6 0x7f9e23ee84cf in start_thread () at /usr/lib/libpthread.so.0 >#7 0x7f9e24bb52d3 in clone () at /usr/lib/libc.so.6 > >Thread 7 (Thread 0x7f9e02dbe700 (LWP 1061)): >#0 0x7f9e23eeec45 in pthread_cond_wait@@GLIBC_2.3.2 () at >/usr/lib/libpthread.so.0 >#1 0x7f9e2508f660 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at >/usr/lib/libQt5Core.so.5 >#2 0x7f9e2508f752 in QWaitCondition::wait(QMutex*, unsigned long) () at >/usr/lib/libQt5Core.so.5 >#3 0x7f9e26d63dad in () at /usr/lib/libQt5Quick.so.5 >#4 0x7f9e26d6405e in () at /usr/lib/libQt5Quick.so.5 >#5 0x7f9e250895b0 in () at /usr/lib/libQt5Core.so.5 >#6 0x7f9e23ee84cf in start_thread () at /usr/lib/libpthread.so.0 >#7 0x7f9e24bb52d3 in clone () at /usr/lib/libc.so.6 > >Thread 6 (Thread 0x7f9e03fff700 (LWP 1060)): >#0 0x7ffd129ad923 in clock_gettime () >#1 0x7f9e24bc256b in clock_gettime () at /usr/lib/libc.so.6 >#2 0x7f9e252af302 in () at /usr/lib/libQt5Core.so.5 >#3 0x7f9e252adbea in QTimerInfoList::updateCurrentTime() () at >/usr/lib/libQt5Core.so.5 >#4 0x7f9e252ae1b6 in QTimerInfoList::timerWait(timespec&) () at >/usr/lib/libQt5Core.so.5 >#5 0x7f9e252af75f in () at /usr/lib/libQt5Core.so.5 >#6 0x7f9e22fbba60 in g_main_context_prepare () at >/usr/lib/libglib-2.0.so.0 >#7 0x7f9e22fbc0a6 in () at /usr/lib/libglib-2.0.so.0 >#8 0x7f9e22fbc251 in g_main_context_iteration () at >/usr/lib/libglib-2.0.so.0 >#9 0x7f9e252afa1c in >QEventDispatcherGlib::processEvents(QFlags) () >at /usr/lib/libQt5Core.so.5 >#10 0x7f9e252564ec in >QEventLoop::exec(QFlags) () at >/usr/lib/libQt5Core.so.5 >#11 0x7f9e25088385 in QThread::exec() () at /usr/lib/libQt5Core.so.5 >#12 0x7f9e269fa849 in () at /usr/lib/libQt5Qml.so.5 >#13 0x7f9e250895b0 in () at /usr/lib/libQt5Core.so.5 >#14 0x7f9e23ee84cf in start_thread () at /usr/lib/libpthread.so.0 >#15 0x7f9e24bb52d3 in clone () at /usr/lib/libc.so.6 > >Thread 5 (Thread 0x7f9e15c12700 (LWP 1053)): >#0 0x7f9e23eeec45 in pthread_cond_wait@@GLIBC_2.3.2 () at >/usr/lib/libpthread.so.0 >#1 0x7f9e1627d66c in () at /usr/lib/dri/i965_dri.so >#2 0x7f9e1627d268 in () at /usr/lib/dri/i965_dri.so >#3 0x7f9e23ee84cf in start_thread () at /usr/lib/libpthread.so.0 >#4 0x7f9e24bb52d3 in clone () at /usr/lib/libc.so.6 > >Thread 4 (Thread 0x7f9e17fff700 (LWP 955)): >#0 0x7f9e24baa9ef in poll () at /usr/lib/libc.so.6 >#1 0x7f9e22fbc180 in () at
[lattedock] [Bug 412822] New: idk
https://bugs.kde.org/show_bug.cgi?id=412822 Bug ID: 412822 Summary: idk Product: lattedock Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: zurielsot...@gmail.com Target Milestone: --- Created attachment 123133 --> https://bugs.kde.org/attachment.cgi?id=123133=edit description bug SUMMARY 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 latte crash -- You are receiving this mail because: You are watching all bug changes.
[Phonon] [Bug 412708] no more playback after several updates e.g. of phonon4qt5 4.10 on 25th Sept. 2019
https://bugs.kde.org/show_bug.cgi?id=412708 --- Comment #2 from Sönke Jensen --- Dear Myriam, does a realistic expected time scale exist for the portation of amarok to QT5? Kindly and warm regards, Sönke Am 09.10.19 um 21:26 schrieb Myriam Schweingruber: > https://bugs.kde.org/show_bug.cgi?id=412708 > > Myriam Schweingruber changed: > > What|Removed |Added > > Product|amarok |Phonon > CC||myr...@kde.org, > ||romain.per...@gmail.com > Target Milestone|kf5 |--- > Assignee|amarok-bugs-d...@kde.org|sit...@kde.org >Component|Playback|general > Version|2.9.0 |4.10.0 > > --- Comment #1 from Myriam Schweingruber --- > This is distribution related, as the Neon devs have probably removed Qt4. > Redirecting to Phonon. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412804] Crash when using the Magnetic Selection Tool
https://bugs.kde.org/show_bug.cgi?id=412804 --- Comment #5 from Kuntal Majumder --- Git commit 6310d2d7ad293f20a758ac80b84d95a90fa6c06b by Kuntal Majumder. Committed on 10/10/2019 at 16:37. Pushed by kuntalmajumder into branch 'master'. Switched exactBounds with defaultBounds for calculating the right number of tiles M +4-12 plugins/tools/selectiontools/KisMagneticWorker.cc https://invent.kde.org/kde/krita/commit/6310d2d7ad293f20a758ac80b84d95a90fa6c06b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411870] Plasma desktop crashes right after start
https://bugs.kde.org/show_bug.cgi?id=411870 --- Comment #1 from Mayeul Cantan --- Created attachment 123132 --> https://bugs.kde.org/attachment.cgi?id=123132=edit New crash information added by DrKonqi plasmashell (5.16.5) using Qt 5.13.1 - What I was doing when the application crashed: Starting a wayland session from sddm. Crash is reproductible everytime if starting plasmashell again from the command line. - Custom settings of the application: Sway Wayland session (with xwayland) open on other tty under the same user. -- Backtrace (Reduced): #6 0x7fa95d4a4e78 in JobModel::updateJob(int, KCupsJob const&) () at /usr/lib/libkcupslib.so #7 0x7fa95d4a6fec in JobModel::insertJob(int, KCupsJob const&) () at /usr/lib/libkcupslib.so #8 0x7fa95d4a74c0 in JobModel::getJobFinished(KCupsRequest*) () at /usr/lib/libkcupslib.so #9 0x7fa98cb9544a in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #10 0x7fa98d6a94f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 411870] Plasma desktop crashes right after start
https://bugs.kde.org/show_bug.cgi?id=411870 Mayeul Cantan changed: What|Removed |Added CC||mayeul.can...@live.fr -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 412821] New: KIO crashed kdeinit5 in FileProtocol::put (SYSCALL_CANCEL)
https://bugs.kde.org/show_bug.cgi?id=412821 Bug ID: 412821 Summary: KIO crashed kdeinit5 in FileProtocol::put (SYSCALL_CANCEL) Product: frameworks-kio Version: 5.62.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: szots...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY After let my PC idling for some minutes I got a report that kdeinit5 crashed. Unfortunately, I don't know what caused that. Crash dump: Application: kdeinit5 (kdeinit5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7efbff508549 in __GI_abort () at abort.c:79 #8 0x7efbfe815a97 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1907 #9 QMessageLogger::fatal (this=this@entry=0x7ffba3e0, msg=msg@entry=0x7efbfb236700 "Fatal Error: Got cmd %d, while waiting for an answer!") at global/qlogging.cpp:888 #10 0x7efbfb165e5c in KIO::SlaveBase::waitForAnswer (this=0x7ffba8d0, expected1=84, expected2=65, data=..., pCmd=0x7ffba454) at /usr/include/qt5/QtCore/qlogging.h:91 #11 0x7efbfb1e653d in KIO::SlaveBase::canResume (this=this@entry=0x7ffba8d0, offset=12289) at /usr/src/debug/kio-5.62.1-1.1.x86_64/src/core/slavebase.cpp:1043 #12 0x7efbfb115725 in FileProtocol::put (this=0x7ffba8c0, url=..., _mode=-1, _flags=...) at /usr/src/debug/kio-5.62.1-1.1.x86_64/src/ioslaves/file/file.cpp:609 #13 0x7efbfb1e7f92 in KIO::SlaveBase::dispatch (this=0x7ffba8d0, command=68, data=...) at /usr/src/debug/kio-5.62.1-1.1.x86_64/src/core/slavebase.cpp:1202 #14 0x7efbfb1f1ea6 in KIO::SlaveBase::dispatchLoop (this=this@entry=0x7ffba8d0) at /usr/src/debug/kio-5.62.1-1.1.x86_64/src/core/slavebase.cpp:348 #15 0x7efbfb114adf in kdemain (argc=, argv=) at /usr/src/debug/kio-5.62.1-1.1.x86_64/src/ioslaves/file/file.cpp:122 #16 0x5655c40c in launch (argc=4, _name=0x5655575bf6a8 "/usr/lib64/qt5/plugins/kf5/kio/file.so", args=, cwd=, envc=0, envs=, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x5655e175 "0") at /usr/src/debug/kinit-5.62.0-1.1.x86_64/src/kdeinit/kinit.cpp:704 #17 0x5655d218 in handle_launcher_request (sock=, who=) at /usr/src/debug/kinit-5.62.0-1.1.x86_64/src/kdeinit/kinit.cpp:1142 #18 0x5655dbf4 in handle_requests (waitForPid=0) at /usr/src/debug/kinit-5.62.0-1.1.x86_64/src/kdeinit/kinit.cpp:1335 #19 0x5655866b in main (argc=5, argv=) at /usr/src/debug/kinit-5.62.0-1.1.x86_64/src/kdeinit/kinit.cpp:1774 [Inferior 1 (process 23058) detached] SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382307] Panels and desktop freezes
https://bugs.kde.org/show_bug.cgi?id=382307 --- Comment #2 from David Edmundson --- >#7 0x7f2e58e6393d in QDBusAbstractInterface::call(QString const&, >QVariant const&, QVariant const&, QVariant const&, QVariant const&, QVariant >const&, QVariant const&, QVariant const&, QVariant const&) () at >/usr/lib64/libQt5DBus.so.5 Means your kactivitesmanagerstats is frozen. A backtrace and a bug report there would be useful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session
https://bugs.kde.org/show_bug.cgi?id=412152
--- Comment #7 from Seqularise ---
with export `dbus-launch`
dbus-update-activation-environment: warning: error sending to systemd:
org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.systemd1
was not provided by any .service files
Warning: QT_AUTO_SCREEN_SCALE_FACTOR is deprecated. Instead use:
QT_ENABLE_HIGHDPI_SCALING to enable platform plugin controlled per-screen
factors.
QCommandLineParser: already having an option named "h"
QCommandLineParser: already having an option named "help-all"
QCommandLineParser: already having an option named "v"
No backend specified through command line argument, trying auto resolution
Icon theme "gnome" not found.
"/usr/bin/kwin_wayland" ("--xwayland", "--libinput",
"--exit-with-session=/usr/lib/startplasma-waylandsession") exited with code 11
startplasmacompositor: Shutting down...
startplasmacompositor: Done.
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 412810] Input is not shown when typing FDE password
https://bugs.kde.org/show_bug.cgi?id=412810 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- Yeah sounds like a broken fontconfig to me. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 405847] SFTP transfer corrupts all files
https://bugs.kde.org/show_bug.cgi?id=405847 --- Comment #38 from Mark Fraser --- (In reply to Yuriy Vidineev from comment #37) > I still have issue with corrupted JPEG on kdeconnect android 1.13.2 and > 1.3.5-0xneon+18.04+bionic+build21 desktop app Same here 1.3.5-0ubuntu1~ubuntu19.04~ppa1 and 1.13.2, tried to copy a 2.9MB JPEG from phone to computer and it is corrupted. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371875] Plasma 5 Desktop shows Black bar on Second screen in ultra-wide UW-UXGA (2560x1080) resolution
https://bugs.kde.org/show_bug.cgi?id=371875 --- Comment #14 from GHPS --- > Is this bug still happening on newer Plasma versions? All versions of Plasma I tested were affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 412820] New: recent files list not working
https://bugs.kde.org/show_bug.cgi?id=412820 Bug ID: 412820 Summary: recent files list not working Product: lokalize Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: kepl...@cmc.pl CC: sha...@ukr.net Target Milestone: --- SUMMARY "Recent files" list doesn't work in Lokalize. STEPS TO REPRODUCE 1. Open Lokalize, open a file to translate. 2. Close it. OBSERVED RESULT An bogus entry of "[]" appears in the "Recent files" list. Clicking it launches "Open file" dialog. After restart the list is empty. EXPECTED RESULT "Recent files" lists, well, recent files. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412796] Can we get an icon for Gravit designer ???
https://bugs.kde.org/show_bug.cgi?id=412796 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- This isn't a Breeze icon problem; it's more likely a bug in the app itself or in the Qt SVG renderer. Can you attach gravit's .desktop file? You should be able to find it in /usr/share/applications/. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 412819] main window layout not saved/restored
https://bugs.kde.org/show_bug.cgi?id=412819 --- Comment #1 from Piotr Keplicz --- Created attachment 123131 --> https://bugs.kde.org/attachment.cgi?id=123131=edit lokalize window maximized -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 412819] New: main window layout not saved/restored
https://bugs.kde.org/show_bug.cgi?id=412819 Bug ID: 412819 Summary: main window layout not saved/restored Product: lokalize Version: 19.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: sdepi...@gmail.com Reporter: kepl...@cmc.pl CC: sha...@ukr.net Target Milestone: --- Created attachment 123130 --> https://bugs.kde.org/attachment.cgi?id=123130=edit default window size SUMMARY Lokalize doesn't seem to remeber the window/toolbar layout. It always starts with the list of translatable strings (left pane) very narrow, while the edit fields are enormously big. STEPS TO REPRODUCE 1. Start lokalize OBSERVED RESULT Main window layout should be restored to match previous setup. At least the left and right panes should be of equal width. EXPECTED RESULT Main window layout defaults to narrow string list on the left side and big edit fields on the right side. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412818] Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12
https://bugs.kde.org/show_bug.cgi?id=412818 Christophe Giboudeaux changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christophe Giboudeaux --- *** This bug has been marked as a duplicate of bug 412629 *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 Christophe Giboudeaux changed: What|Removed |Added CC||sfbar...@gmail.com --- Comment #1 from Christophe Giboudeaux --- *** Bug 412818 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 403791] Replace all passivenotification messages with InlineMessages
https://bugs.kde.org/show_bug.cgi?id=403791 --- Comment #3 from Nate Graham --- Created attachment 123129 --> https://bugs.kde.org/attachment.cgi?id=123129=edit "Aborted due to failure" I'm not sure that worked. See this attachment. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412818] Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12
https://bugs.kde.org/show_bug.cgi?id=412818 stuart changed: What|Removed |Added CC||sfbar...@gmail.com Keywords||reproducible URL||https://www.postgresql.org/ ||docs/12/release-12.html#id- ||1.11.6.5.5 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 411866] kdevelop crashed
https://bugs.kde.org/show_bug.cgi?id=411866 Piotr Keplicz changed: What|Removed |Added CC||kepl...@cmc.pl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412152] [Wayland] cannot start session
https://bugs.kde.org/show_bug.cgi?id=412152 --- Comment #6 from Pawel --- (In reply to David Edmundson from comment #5) > try with > > > export `dbus-launch` > > before starting kwin If I should change line Exec= in /usr/share/wayland-sessions/plasmawayland.desktop to Exec=dbus-launch /usr/bin/startplasma-wayland then it doesn't works. The main difference is that after I choose plasma-wayland in SDDM it starts and return to login screen. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 412818] New: Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12
https://bugs.kde.org/show_bug.cgi?id=412818 Bug ID: 412818 Summary: Akonadi query on SchemaVersionTable is broken in PostgreSQL Version 12 Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: sfbar...@gmail.com Target Milestone: --- SUMMARY When backed by the postgres db, Akonadi executes the query; "SELECT pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_attrdef.adsrc FROM pg_class, pg_attribute LEFT JOIN pg_attrdef ON (pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum = pg_attribute.attnum) WHERE pg_table_is_visible(pg_class.oid) AND pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND pg_attribute.attrelid = pg_class.oid AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum ;" In versions of PostGreSQL before 12, this query succeeds. Due to the changes to the informationschema, as identified in PostGreSQL PostgreSQL release notes: E.1. Release 12 https://www.postgresql.org/docs/12/release-12.html#id-1.11.6.5.5 PostgreSQL Version 12 removes: obsolete pg_constraint.consrc column obsolete pg_attrdef.adsrc column STEPS TO REPRODUCE 1. Upgrade PostGreSQL backend database to 12.x 2. Restart with Akonadictl start 3. OBSERVED RESULT This causes the query to fail and Akonadi quits with the error. org.kde.pim.akonadiserver: Starting up the Akonadi Server... org.kde.pim.akonadiserver: Running DB initializer org.kde.pim.akonadiserver: "\nSql error: ERROR: column \"version\" of relation \"schemaversiontable\" already exists\n(42701) QPSQL: Unable to create query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0" org.kde.pim.akonadiserver: Unable to initialize database. org.kde.pim.akonadiserver: Shutting down AkonadiServer... EXPECTED RESULT When the query succeeds, Akonadi continues to process emails. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ANY (available in About System) KDE Plasma Version: ANY KDE Frameworks Version: ANY Qt Version: ANY ADDITIONAL INFORMATION The schema information for these dropped columns can be obtained using the functions, pg_constraint.consrc pg_get_constraintdef(pg_constraint.oid) pg_attrdef.adsrc pg_get_expr(pg_attrdef.adbin, pg_class.oid) So the Akonadi query: SELECT pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_attrdef.adsrc FROM pg_class, pg_attribute LEFT JOIN pg_attrdef ON (pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum = pg_attribute.attnum) WHERE pg_table_is_visible(pg_class.oid) AND pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND pg_attribute.attrelid = pg_class.oid AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum ; should probably be changed to something like: SELECT pg_attribute.attname, pg_attribute.atttypid::int, pg_attribute.attnotnull, pg_attribute.attlen, pg_attribute.atttypmod, pg_get_expr(pg_attrdef.adbin, pg_class.oid) AS adsrc FROM pg_class LEFT JOIN pg_attribute ON ( pg_attribute.attrelid = pg_class.oid ) LEFT JOIN pg_attrdef ON ( pg_attrdef.adrelid = pg_attribute.attrelid AND pg_attrdef.adnum = pg_attribute.attnum ) WHERE pg_table_is_visible(pg_class.oid) AND pg_class.relname = 'schemaversiontable' AND pg_attribute.attnum > 0 AND pg_attribute.attisdropped = false ORDER BY pg_attribute.attnum; This will produce something like the following table: attname | atttypid | attnotnull | attlen | atttypmod | adsrc +--+++---+--- version| 23 | t | 4 |-1 | 0 generation | 23 | t | 4 |-1 | 0 (2 rows) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 412817] New: Selected area (rectangle) app crash
https://bugs.kde.org/show_bug.cgi?id=412817 Bug ID: 412817 Summary: Selected area (rectangle) app crash Product: Spectacle Version: 19.08.1 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: d...@northshoresunset.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (19.08.1) Qt Version: 5.11.3 Frameworks Version: 5.62.0 Operating System: Linux 5.2.0-3-amd64 x86_64 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: App works fine except when I try to select a rectangle (partial screen area), then it crashes everytime. The crash can be reproduced sometimes. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbdc306c800 (LWP 3008))] Thread 4 (Thread 0x7fbdba1e4700 (LWP 3011)): #0 0x7fbdc632ddb5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fbdbaa0b30b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #2 0x7fbdbaa0af27 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #3 0x7fbdc6327fb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fbdc753f2ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fbdc0ddf700 (LWP 3010)): #0 0x7fbdc75308bc in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbdc578ccef in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbdc5745bee in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbdc5746042 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbdc57461bf in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbdc7a9b3e3 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbdc7a48cfb in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbdc7898d8e in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbdc827b545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fbdc78a2a07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fbdc6327fb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7fbdc753f2ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fbdc24a0700 (LWP 3009)): #0 0x7fbdc754061d in recvmsg () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7fbdc8f99e58 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fbdc8f97fb5 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fbdc8f9991a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #4 0x7fbdc2c2cd79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #5 0x7fbdc78a2a07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbdc6327fb7 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #7 0x7fbdc753f2ef in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7fbdc306c800 (LWP 3008)): [KCrash Handler] #6 0x7fbdc85b3743 in QWidget::window() const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7fbdc8594557 in QApplicationPrivate::sendSyntheticEnterLeave(QWidget*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7fbdc85c63cf in QWidgetPrivate::hideChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7fbdc85c63a1 in QWidgetPrivate::hideChildren(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7fbdc85cc2b2 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fbdc858d501 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fbdc85949b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fbdc7a4a029 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fbdc85e8344 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fbdc85e8a52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7fbdc858d501 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7fbdc85949b0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7fbdc7a4a029 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fbdc7df1701 in
[krita] [Bug 412816] New: GDquest tag multiplication
https://bugs.kde.org/show_bug.cgi?id=412816 Bug ID: 412816 Summary: GDquest tag multiplication Product: krita Version: 4.2.6 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: simon.mannerha...@gmail.com Target Milestone: --- SUMMARY When I add new GDquest brushes to a tag it multiplies my 'Favourites' and other tags STEPS TO REPRODUCE 1. download cdquest free bundle 2. add cdquest brushes to tag 3. OBSERVED RESULT it multiplies tags EXPECTED RESULT it doesn't multiply tags SOFTWARE/OS VERSIONS Windows: yes 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-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Tomasz C. changed: What|Removed |Added CC||tli...@cebula.eu.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412781] Various graphical glitches since Qt5.14
https://bugs.kde.org/show_bug.cgi?id=412781 --- Comment #7 from Nate Graham --- Will fixing that Qt bug fix all of these issues, or only some of them? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 409652] xembedsniproxy segmentation faults in FdoSelectionManager::init when logging into Plasma on X after running scap-workbench remediation script
https://bugs.kde.org/show_bug.cgi?id=409652 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-workspace/741441765601c ||00cb84ecb7fa7b38e69d185f51a Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||5.17.1 --- Comment #3 from Nate Graham --- Git commit 741441765601c00cb84ecb7fa7b38e69d185f51a by Nate Graham, on behalf of Konrad Materka. Committed on 10/10/2019 at 14:42. Pushed by ngraham into branch 'Plasma/5.17'. [XembedSNIProxy] Do not crash on null pointer Summary: XCB may return null pointer as a response. Add a check to prevent segmentation fault. FIXED-IN: 5.17.1 Test Plan: It is hard to reproduce, but the reason of the segmentation fault is pretty obvious, thanks to the debug dump from bug 409652 Reviewers: #plasma_workspaces, #plasma, davidedmundson Reviewed By: #plasma_workspaces, #plasma, davidedmundson Subscribers: ngraham, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D24514 M +11 -11 xembed-sni-proxy/fdoselectionmanager.cpp M +2-3xembed-sni-proxy/fdoselectionmanager.h https://commits.kde.org/plasma-workspace/741441765601c00cb84ecb7fa7b38e69d185f51a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412781] Various graphical glitches since Qt5.14
https://bugs.kde.org/show_bug.cgi?id=412781 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366047] sni proxy scaling not always appropriate
https://bugs.kde.org/show_bug.cgi?id=366047 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-workspace/13efbfca67f82 ||70458d103e128ba76525f663329 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Version Fixed In||5.17.1 --- Comment #7 from Nate Graham --- Git commit 13efbfca67f8270458d103e128ba76525f663329 by Nate Graham, on behalf of Konrad Materka. Committed on 10/10/2019 at 14:39. Pushed by ngraham into branch 'Plasma/5.17'. [XembedSNIProxy] Scale only big icons Summary: Do not scale up small icons to avoid quality detoriation. For small icons scaling should be done in SystemTray only. Currently XembedSNIProxy scales to 32x32, then SystemTray (usually) scales it down to 24x24. FIXED-IN: 5.17.1 Test Plan: I've run few applications with small icons: - keepassx (22x22) - liferea (16x16) - tuxguitar (16x16) It looks much better without scaling in xemebdsniproxy. Reviewers: davidedmundson, #plasma, #plasma_workspaces Reviewed By: davidedmundson, #plasma, #plasma_workspaces Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D24531 M +1-1xembed-sni-proxy/sniproxy.cpp https://commits.kde.org/plasma-workspace/13efbfca67f8270458d103e128ba76525f663329 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366047] sni proxy scaling not always appropriate
https://bugs.kde.org/show_bug.cgi?id=366047 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358240] KeePass2 system tray icon is shown as white square
https://bugs.kde.org/show_bug.cgi?id=358240 Nate Graham changed: What|Removed |Added Version Fixed In||5.17.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358240] KeePass2 system tray icon is shown as white square
https://bugs.kde.org/show_bug.cgi?id=358240 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-workspace/acf91005b60c8 ||2f8381fb119f327f4d443c5b98d --- Comment #5 from Nate Graham --- Git commit acf91005b60c82f8381fb119f327f4d443c5b98d by Nate Graham, on behalf of Konrad Materka. Committed on 10/10/2019 at 14:31. Pushed by ngraham into branch 'Plasma/5.17'. [XembedSNIProxy] Check size in each update() Summary: If needed, perform resize in each update(). Client window may be too big, it must be resized to a certain reasonable size. Sometimes resizing in the constructor is not enough because it is too early and the client window is not fully initialized. Even if client window is resized, on first update it reverts back to original size (or just ignores the first request - some kind of a race condition). In addition, I applied some rules from: https://community.kde.org/Policies/Kdelibs_Coding_Style Test Plan: I tested it using keepass2, now it shows better results (still not perfect). Window is resized to 32x32, but icon is only 24x24 it top-left. Better than 273x273 with tiny dot in the corner. This is a workaround for unsolvable bug in Mono - AFAIK Windows Forms are not longer maintained so it won't be fixed. I tested this change with several other apps for regressions, no issues: pidgin liferea hexchat tuxguitar xchat keepassx stardict and other I don't remember now. No regressions. Reviewers: davidedmundson, #plasma, #plasma_workspaces, broulik Reviewed By: davidedmundson, #plasma, #plasma_workspaces Subscribers: broulik, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D24529 M +42 -41 xembed-sni-proxy/sniproxy.cpp M +1-0xembed-sni-proxy/sniproxy.h https://commits.kde.org/plasma-workspace/acf91005b60c82f8381fb119f327f4d443c5b98d -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412815] Keyboard Input is different than physical keyboard input
https://bugs.kde.org/show_bug.cgi?id=412815 Christoph Feck changed: What|Removed |Added CC||bhus...@gmail.com Product|kvkbd |kscreenlocker Component|general |general Assignee|smar...@ubuntu.com |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412814] Keyboard size is too large on desktop mode
https://bugs.kde.org/show_bug.cgi?id=412814 Christoph Feck changed: What|Removed |Added Component|general |general Assignee|smar...@ubuntu.com |plasma-b...@kde.org Product|kvkbd |kscreenlocker CC||bhus...@gmail.com --- Comment #4 from Christoph Feck --- That's not kvkbd, but the QtVirtualKeyboard. I am not sure if its API allows configuring the "window" size, if not I would suggest reporting it Qt developers. Reassigning to Plasma developers for inspection. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 412783] Screen configuration should have "orientation: Auto" as an option
https://bugs.kde.org/show_bug.cgi?id=412783 Aleix Pol changed: What|Removed |Added CC||aleix...@kde.org --- Comment #2 from Aleix Pol --- Are you on Wayland or X11? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412637] Panel resets upon restarting Plasma
https://bugs.kde.org/show_bug.cgi?id=412637 --- Comment #4 from Christoph Feck --- You need to insert a spacer, because widgets are layouted from left to right. The taskmanager on the bottom panel takes all remaining width, so there is no need to insert a spacer there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358240] KeePass2 system tray icon is shown as white square
https://bugs.kde.org/show_bug.cgi?id=358240 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 404622] Discover crashed when closed immediately after opening
https://bugs.kde.org/show_bug.cgi?id=404622 --- Comment #3 from Aleix Pol --- :( drat, I guess I'll have to try harder. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 412807] Discover crashes -- segmentation fault
https://bugs.kde.org/show_bug.cgi?id=412807 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Aleix Pol --- This issue was fixed recently, it was a packaging issue in Qt. You will have to use the terminal to update. You can do so by calling "pkcon update". Sorry for the inconvenience. :/ -- You are receiving this mail because: You are watching all bug changes.
[kvkbd] [Bug 412815] New: Keyboard Input is different than physical keyboard input
https://bugs.kde.org/show_bug.cgi?id=412815 Bug ID: 412815 Summary: Keyboard Input is different than physical keyboard input Product: kvkbd Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: smar...@ubuntu.com Reporter: alexis.diava...@gmail.com Target Milestone: --- Created attachment 123127 --> https://bugs.kde.org/attachment.cgi?id=123127=edit vKeyboard different input than physical keyboard STEPS TO REPRODUCE 1. Open vKeyboard 2. Change the input to another language from the indicator OBSERVED RESULT The vKeyboard doesn't change input, so the physical keyboard types on a different input than the vKeyboard EXPECTED RESULT When we change input from the indicator, vKeyboard should change input too, and vice versa; When we change input from the vKeyboard, the input should change for the physical keyboard too -- You are receiving this mail because: You are watching all bug changes.
