[Powerdevil] [Bug 425890] New: monitor always turns itself back on a few seconds after turning off
https://bugs.kde.org/show_bug.cgi?id=425890 Bug ID: 425890 Summary: monitor always turns itself back on a few seconds after turning off Product: Powerdevil Version: 5.19.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tg...@tutanota.com Target Milestone: --- I set my keyboard's sleep key to turn my screen off. This worked fine when I was using Nvidia drivers with my old GTX 960. At some point I replaced it with a Radeon 5600XT with Mesa drivers. Immediately after this change, pressing the sleep key shuts the screen off as usual, but it turns itself back on after 1-10 seconds. I have the same problem if I run `xset dpms force off` from a terminal, or if I wait 10 minutes for the screen to turn off automatically. I booted Kubuntu from a usb drive and the issue still occurs. I also tried Ubuntu and Xubuntu, and the problem does not occur on Gnome or XFCE. --- May be related to #423035, but that specifies using a shortcut. My issue occurs any time the screen turns off. May be related to #348082, although that is old and only mentions the lock screen. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379581] Unicode support to IPTC metadata is not consistent on the UI
https://bugs.kde.org/show_bug.cgi?id=379581 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.1.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/ad0ab9e ||feba6e2fe3bb86207a91499e4e8 ||eb170f --- Comment #2 from caulier.gil...@gmail.com --- Git commit ad0ab9efeba6e2fe3bb86207a91499e4e8eb170f by Gilles Caulier. Committed on 28/08/2020 at 05:19. Pushed by cgilles into branch 'master'. IPTC and Utf8 support: If a tag is string, check if global IPTC characterset is null to convert in latin1, else we expect to interpret the string as utf8. We use std::string accessor from Exiv2 to get an Utf8 cenversion of string. If it do not work, well this problem need to be reported as UPSTREAM to Exiv2 as pre-cenversion of string is not done in background by the library. This patch prevent to display latin1 string with a wrong Utf8 conversion which can break some characters. Related: bug 379050 FIXED-IN: 7.1.0 M +27 -3core/libs/metadataengine/engine/metaengine_iptc.cpp https://invent.kde.org/graphics/digikam/commit/ad0ab9efeba6e2fe3bb86207a91499e4e8eb170f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 379050] Umlauts and accented characters in IPTC metadata not correct
https://bugs.kde.org/show_bug.cgi?id=379050 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/ad0ab9e ||feba6e2fe3bb86207a91499e4e8 ||eb170f Version Fixed In||7.1.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from caulier.gil...@gmail.com --- Git commit ad0ab9efeba6e2fe3bb86207a91499e4e8eb170f by Gilles Caulier. Committed on 28/08/2020 at 05:19. Pushed by cgilles into branch 'master'. IPTC and Utf8 support: If a tag is string, check if global IPTC characterset is null to convert in latin1, else we expect to interpret the string as utf8. We use std::string accessor from Exiv2 to get an Utf8 cenversion of string. If it do not work, well this problem need to be reported as UPSTREAM to Exiv2 as pre-cenversion of string is not done in background by the library. This patch prevent to display latin1 string with a wrong Utf8 conversion which can break some characters. Related: bug 379581 FIXED-IN: 7.1.0 M +27 -3core/libs/metadataengine/engine/metaengine_iptc.cpp https://invent.kde.org/graphics/digikam/commit/ad0ab9efeba6e2fe3bb86207a91499e4e8eb170f -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420195] no support for UTF16 characters under Windows
https://bugs.kde.org/show_bug.cgi?id=420195 caulier.gil...@gmail.com changed: What|Removed |Added Component|Metadata-Engine |Plugin-FilesIO-HEIF --- Comment #48 from caulier.gil...@gmail.com --- Maik, I move this file in HEIF plugin as it still only libheif problem with UTF16 support under Windows to fix. Gilles -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424751] crash on panel auto-hide
https://bugs.kde.org/show_bug.cgi?id=424751 --- 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.
[krita] [Bug 425875] Crashes if selecting animated brush preset in smudge brush engine
https://bugs.kde.org/show_bug.cgi?id=425875 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425269] I can't create files
https://bugs.kde.org/show_bug.cgi?id=425269 --- Comment #2 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 418925] Audio bug
https://bugs.kde.org/show_bug.cgi?id=418925 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #14 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 424806] yakuake
https://bugs.kde.org/show_bug.cgi?id=424806 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 425889] New: Outdated GPG4Win Compendium document. Decryption doesnt work
https://bugs.kde.org/show_bug.cgi?id=425889 Bug ID: 425889 Summary: Outdated GPG4Win Compendium document. Decryption doesnt work Product: kleopatra Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: sudeeps...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Click on Help Menu 2. Select GPG4Win Compendium OBSERVED RESULT Routes to an outdated file. It doesn't have the information or screenshot that is in the latest version of Kleopatra EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #2 from caulier.gil...@gmail.com --- Please read this page for more info : https://www.digikam.org/contribute/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 --- Comment #1 from caulier.gil...@gmail.com --- The eventvwr binary file is not suitable. It highlight only a problem in Tiff loader from digiKam but no more. We need the application text trace captured with DebugView. A crash backtrace captured withe a debugger will be a plus of course, for ex to run digiKam in QtCreator. Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425848] Some notifications from PC to phone cannot be filtered
https://bugs.kde.org/show_bug.cgi?id=425848 Simon Redman changed: What|Removed |Added Component|messaging-application |common Assignee|si...@ergotech.com |albertv...@gmail.com --- Comment #1 from Simon Redman --- Sorry, that this is happening to you. This is not a part of the code I've touched before. I looked through a bit but I couldn't see how our plugin determines the list of apps which can send notifications. I am going to assign it to the proper component and hopefully someone who knows how this part work will take a look. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version|7.3.0 |7.0.0 Platform|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425884] GPS Processing Method: "charset=Ascii" to remove
https://bugs.kde.org/show_bug.cgi?id=425884 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- And ??? What did you expect from digiKam side ? you want to remove what ? The tags content ? The whole tags as well from the list ? I seen the exiv2 report : https://github.com/Exiv2/exiv2/issues/1266 It's clear that Exiv2 do not do the right job in background. Exiv2 code must be fixed in priority. I don't like to add a extra layer in client area because the low level as a problem and will not fixed quickly. We will make an hamburger. Best Glles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424050] Sometimes free space available disappears from the status bar after I mount a partition of an internal hard disk
https://bugs.kde.org/show_bug.cgi?id=424050 JanKusanagi changed: What|Removed |Added CC||jan-b...@gmx.co.uk --- Comment #1 from JanKusanagi --- This happens to me since Dolphin 20.08 without the need to mount anything. The space information bar disappears from one specific tab (and not others) when a new file is "suddenly" added to the folder being shown in that tab, by, say, being moved there by another program, a download completing, etc. When this happens, the right-click option is still checked, and the bar can be brought back just by unchecking that, and checking it again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425888] GTK3 Applications no longer automatically change their colours in Neon Focal
https://bugs.kde.org/show_bug.cgi?id=425888 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||zom...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 417070] KRunner makes excessive writes during searching.
https://bugs.kde.org/show_bug.cgi?id=417070 sgo...@gmail.com changed: What|Removed |Added CC||sgo...@gmail.com --- Comment #21 from sgo...@gmail.com --- Can anyone tell me which exact version of krunner has this bug? Thanks a lot. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425888] New: GTK3 Applications no longer automatically change their colours in Neon Focal
https://bugs.kde.org/show_bug.cgi?id=425888 Bug ID: 425888 Summary: GTK3 Applications no longer automatically change their colours in Neon Focal Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: ferenos...@outlook.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY In Neon Bionic, GTK3 applications used to automatically change their colour scheme to match the colour scheme when the colour scheme is changed, but as of Neon Focal this no longer occurs. None of the GTK3 applications, excluding the mini free space indicators in Nemo file manager's sidebar, get coloured at all by the colorreload-gtk-module when changing a colour scheme. STEPS TO REPRODUCE 1. Apply a colour scheme 2. Open a GTK3 application 3. Apply another colour scheme OBSERVED RESULT The colour scheme isn't changed in that GTK3 application, or in fact any GTK3 applications. EXPECTED RESULT The colour scheme would also change immediately in other GTK3 applications. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon User Edition 5.19.4 on Ubuntu 20.04 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION This worked just fine in Ubuntu 18.04 based Neon. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 419814] krfb does not show full screen in client if display is scaled
https://bugs.kde.org/show_bug.cgi?id=419814 Stefan Brüns changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/netw ||ork/krfb/commit/933169b4c0e ||3ea9796783f70eca2f0aae29dea ||2f Status|CONFIRMED |RESOLVED --- Comment #5 from Stefan Brüns --- Git commit 933169b4c0e3ea9796783f70eca2f0aae29dea2f by Stefan Brüns. Committed on 28/08/2020 at 02:08. Pushed by bruns into branch 'master'. Compensate for global scale factor when using xcb fb plugin The screen geometry is reported in device independent pixels, so it has to be multiplied by the devicePixelRatio to get the size of the underlying framebuffer. Otherwise, only the top left of the screen will be captured. This matches the behavior of QScreen::grabWindow(...), which also returns a QPixmap of the given size scaled by devicePixelRatio. M +5-1framebuffers/xcb/xcb_framebuffer.cpp https://invent.kde.org/network/krfb/commit/933169b4c0e3ea9796783f70eca2f0aae29dea2f -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 425803] "Send Later" sends immediately
https://bugs.kde.org/show_bug.cgi?id=425803 --- Comment #2 from Brendon Higgins --- Thanks, Laurent. Hmm, something is definitely screwey here, though. I tested on a fresh user account and it does it there, too. If I set the delay time sufficiently far into the future then it doesn't do it. So I tried a binary search, and ended up concluding that it doesn't matter what time you set: if it's for the same day, the message will get sent immediately. I'm wondering if timezones might also factor in, but no evidence as yet. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389448] Width and height of the window doesn't set correctly on HiDPI screen when using Plasma Qt scaling on X11
https://bugs.kde.org/show_bug.cgi?id=389448 Lê Hoàng Phương changed: What|Removed |Added CC||dev_rya...@zoho.com --- Comment #44 from Lê Hoàng Phương --- *** Bug 417959 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 417959] Yakuake width display not working on external 3840x2160 4k display
https://bugs.kde.org/show_bug.cgi?id=417959 Lê Hoàng Phương changed: What|Removed |Added Resolution|--- |DUPLICATE CC||lehoangphuon...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Lê Hoàng Phương --- *** This bug has been marked as a duplicate of bug 389448 *** -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 425859] Crash
https://bugs.kde.org/show_bug.cgi?id=425859 Myriam Schweingruber changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Myriam Schweingruber --- Which exact Amarok version? Yo need the kf5 build of Amarok, the Qt4 based will not work. Also: we need a backtrace, else this report is not useful. Please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425887] New: toolsQuick.xml not installed together with KDE Neon
https://bugs.kde.org/show_bug.cgi?id=425887 Bug ID: 425887 Summary: toolsQuick.xml not installed together with KDE Neon Product: okular Version: 1.11.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: david.hu...@mailbox.org Target Milestone: --- SUMMARY I was required to reinstall Neon :(, and Okular presents me > Unable to open QuickAnnotatingTools XML definition with all the consequences. It seems that /usr/share/okular/ contains all data files except toolsQuick.xml. Did we forget to add toolsQuick.xml to some cmake file, or did packagers do? STEPS TO REPRODUCE 1. Install/launch KDE Neon 2. Launch Okular from command line OBSERVED RESULT No quick annotations EXPECTED RESULT Quick annotations SOFTWARE/OS VERSIONS KDE Neon from today -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 425874] Shorter titlebar (without smaller font) option needed: less padding
https://bugs.kde.org/show_bug.cgi?id=425874 --- Comment #4 from Duncan <1i5t5.dun...@cox.net> --- Created attachment 131227 --> https://bugs.kde.org/attachment.cgi?id=131227=edit testing only tiny titlebar button option patch While this patch didn't end up giving me a vertically shorter titlebar, but it's useful for testing, with the tiny titlebar button option it offers helping to ensure it's not the button size controlling the titlebar height, just the font size. (Actually, being the first hack I tried it did give me a smaller than default titlebar, but not small enough. Clearly it was the font padding I had to attack. And after I did so I could actually choose the existing small or normal button sizes without increasing titlebar height, so this patch was no longer of much use except to ensure the buttons did not interfere with testing the padding patch.) -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 419814] krfb does not show full screen in client if display is scaled
https://bugs.kde.org/show_bug.cgi?id=419814 --- Comment #4 from Daragh --- thanks @alexey -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 425874] Shorter titlebar (without smaller font) option needed: less padding
https://bugs.kde.org/show_bug.cgi?id=425874 --- Comment #3 from Duncan <1i5t5.dun...@cox.net> --- Created attachment 131226 --> https://bugs.kde.org/attachment.cgi?id=131226=edit oxygen titlebar negative vmargins demo hack-patch Glad I took the time for a second look. A lot more made sense this time thru and I ended up dropping one patch entirely as unnecessary, and making another basically test-time only. This is the main idea here. At the given negative 2 TitleBar_TopMargin and -1 TitleBar_BottomMargin settings it squeezes things slightly on the Noto Sans Medium font, normally no exotic (aka mostly ASCII) characters common in my titlebar here. It's likely to be worse for Asian charactersets and the like, and as such it's likely to be the lower bound. Zeroing out both values (along with TitleBar_OutlineMargin, already zeroed out here) would yield a somewhat less vertically squeezed titlebar that if I'm understanding the call to qt font-functions the metrics are based on correctly, should just fit maximum font ascenders and descenders even for non-western characters. Zeroed values resulted in a 16px high titlebar at 8pt font I was working with. But the results for the negative values as posted are even better than I expected, a 10px high titlebar at the 8pt font size I was working with. That allowed me to increase the font to 10pt for 14px high. I'll have to play a bit more to see whether I prefer the extra 4px I get at 8pt font or the somewhat more comfortable to read 10pt. (9pt was the same 14px high titlebar as 10pt, while 11pt increase it to 17px. So 8pt and 10pt are the practical choices.) Would be cool if I could do the option UI too but that's beyond me ATM. Assuming it's implemented, maybe I can learn from the commit adding it... There's another minor testing-only patch coming too, adding a tiny button size, but it didn't reduce the titlebar size so I consider it only practical for testing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425886] New: DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool
https://bugs.kde.org/show_bug.cgi?id=425886 Bug ID: 425886 Summary: DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool Product: digikam Version: 7.3.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Searches-Advanced Assignee: digikam-bugs-n...@kde.org Reporter: s...@email.com Target Milestone: --- Created attachment 131225 --> https://bugs.kde.org/attachment.cgi?id=131225=edit eventvwr files of crashes SUMMARY DigiKam Crashes immediately after hitting the search button for Images, both on regular and advanced search tool STEPS TO REPRODUCE 1. open up digikam on windows 10 2. >tools/search or /advanced search type in a date range 3. hit ok or start search. OBSERVED RESULT Digicam crashes almost instantaneously with error message "digikam.exe has stopped working" A problem caused the program to stop working correctly. please close the program. EXPECTED RESULT Find the images within the date range specified SOFTWARE/OS VERSIONS Windows: 10 pro macOS: - Linux/KDE Plasma: -- (available in About System) KDE Plasma Version: (can't find this anywhere) KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 (built against 5.14.2) ADDITIONAL INFORMATION Computer info. Ryzen 3950x Radeon VII 32gb ram 1TB gen4. pcie m.2 windows eventvwr files are attached -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421186] Android and Plasma is not communicating on phone's portable WiFi HOTSPOT
https://bugs.kde.org/show_bug.cgi?id=421186 --- Comment #6 from Benedict --- I've checked the source code at https://invent.kde.org/network/kdeconnect-android Upon quick text search, I didn't found any reference to WIFI_AP_STATE string, and the manifest does not include receiver. This almost certainly tells that the android app isn't detecting status of WiFi hotspot, thus disabling the service as if the phone is not connected to wifi at all. Sorry I have no Android/Java background, I wish I can help further... (just a flutter beginner here) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421186] Android and Plasma is not communicating on phone's portable WiFi HOTSPOT
https://bugs.kde.org/show_bug.cgi?id=421186 Benedict changed: What|Removed |Added OS|Android 8.x |Android 10.x CC||yappy.bened...@gmail.com --- Comment #5 from Benedict --- "You're not connected to a WiFi network" also happens to me on the KDE Connect application. This does _not_ happen when the Android is connected using USB tethering, only on WiFi tethering. Another KDE Connect Android can connect to the desktop, but the KDE Connect on the WiFi broadcasting / hotspotting phone cannot connect, showing the aforementioned error message. Tried adding desktop IP address to the mobile app, it's on the custom device list, it still doesn't not work after refreshing (same "you're not connected to a WiFi network" message. Issue is replicated when the WiFi broadcasting phone is switched. KDE Connect version: 1.4.0 (desktop client) KDE Connect Android version: 1.14.2 (Android 9, Xiaomi Mi6 and Android 10, Samsung Note 20) -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 425885] repeatedly redrawn figure when making scatterplot with gui, leads to crash
https://bugs.kde.org/show_bug.cgi?id=425885 --- Comment #1 from Eric --- ... 9. click 'submit' so the figure is placed in the workspace. 10. Click "Run Again" ---> hard crash -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 424298] valgrind 3.16.1: RDSEED vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF8 0x89 0x4 0x24 0xF 0x82 0x63 0x1
https://bugs.kde.org/show_bug.cgi?id=424298 Mark Wielaard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from Mark Wielaard --- (In reply to Alexandra Hajkova from comment #3) > Created attachment 131196 [details] > patch > > This patch implements RDSEED support and also adds the rdseed test to the > testsuite. This looks really good, thanks. The commit message could explain the patch a bit more, which would make review a bit easier. And please add the bug number in the commit message or the URL to this bug. Also, please add a NEWS entry for the bug. It is interesting how similar rdrand and rdseed are, but they do have separate cpuid flags, and are apparently using a different way to generate the random bits. I am not sure the way a 64bit value is created from two calls to rdseed produces the correct "randomness", but it is exactly how rdrand does it. So we'll have to assume that was done correctly. Given that the rdrand and rdseed implementation are so similar I wonder if you could merge the /* 0F C7 /6 no-F2-or-F3 = RDRAND */ and /* 0F C7 /7 = RDSEED */ parts. RDSEED also has the no-F3-or-F3 part, so basically you could just check: (gregLO3ofRM(modrm) == 6 && (archinfo->hwcaps & VEX_HWCAPS_AMD64_RDRAND)) || (gregLO3ofRM(modrm) == 7 && (archinfo->hwcaps & VEX_HWCAPS_AMD64_RDSEED)) && epartIsReg(modrm) && haveNoF2noF3(pfx) && (sz == 8 || sz == 4 || sz == 2)) And then make the dLO and dHI assignments depend on gregLO3ofRM(modrm) == 6 for amd64g_dirtyhelper_RDRAND or gregLO3ofRM(modrm) == 7 for amd64g_dirtyhelper_RDSEED (and same for the DIP). That would remove some duplicate code. +/* This is wrong... assert( !(cmask != 0 && dmask != 0) ); assert( !(cmask == 0 && dmask == 0) ); +*/ It is indeed wrong. But please instead of commenting it out, either remove it or adjust the asserts to also take the new bmask into account. But all the above are really just nitpicks, nice work. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 425885] New: repeatedly redrawn figure when making scatterplot with gui, leads to crash
https://bugs.kde.org/show_bug.cgi?id=425885
Bug ID: 425885
Summary: repeatedly redrawn figure when making scatterplot with
gui, leads to crash
Product: rkward
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: User Interface
Assignee: rkward-de...@kde.org
Reporter: majzo...@umsl.edu
Target Milestone: ---
Created attachment 131224
--> https://bugs.kde.org/attachment.cgi?id=131224=edit
data file needed to observe the behavior
SUMMARY
Selecting scatterplot from the menu and doing the following below gives hard
crash.
STEPS TO REPRODUCE
1. Open R script
2. Run the script
3. Select Plots-->Scatterplot
4. scroll down to data frame ch_wide_2
5. input FISCAL_YEAR three times into "'X' variables"
6. input FS, SP, SS into the 'Y' variables
7. select the 'use wizard' button
8. keep selecting 'next' to get to the preview.
OBSERVED RESULT
The preview window repeatedly redraws the figure and it flashes, and other
things happen.
EXPECTED RESULT
It just makes the plot preview.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.18.5
kernel 5.7-17-200.fc32.x86_64
KDE Frameworks 5.70.0
Qt 5.14.2 (built against 5.14.2)
The xcb windowing system
ADDITIONAL INFORMATION
I can get it to crash doing this if I keep trying to add things to the plot
like different colors for the different Y variables, etc.
The script file is: (I have been playing with other plotting packages)
library(reshape2)
library(tidyverse)
library(skimr)
library(ggplot2)
library(ggraptR)
library(shiny)
library(ggplotgui)
library(GrapheR)
ch = read.csv("/home/me/Credit_Hour_Counts_data_fixed.csv") # read csv file
#ch[is.na(ch)] <- 0
ch_wide_1 <- dcast(ch, Term ~ FISCAL_YEAR)
ch_wide_1[is.na(ch_wide_1)] <- 0
ch_wide_2 <- dcast(ch, FISCAL_YEAR ~ Term)
ch_wide_2[is.na(ch_wide_2)] <- 0
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 424709] Plasma crashes when I try to clear the clipboard on Wayland session of neon unstable
https://bugs.kde.org/show_bug.cgi?id=424709 Tony changed: What|Removed |Added CC||jodr...@live.com --- Comment #4 from Tony --- Can aso confirm this on openSuse Tumbleweed, everytime. Also, possible duplicate : https://bugs.kde.org/show_bug.cgi?id=396308 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcuts to launch 3rd-party apps don't work
https://bugs.kde.org/show_bug.cgi?id=421329 Yoav Navott changed: What|Removed |Added CC||yoavnav...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425884] New: GPS Processing Method: "charset=Ascii" to remove
https://bugs.kde.org/show_bug.cgi?id=425884
Bug ID: 425884
Summary: GPS Processing Method: "charset=Ascii" to remove
Product: digikam
Version: 7.1.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Metadata-Exif
Assignee: digikam-bugs-n...@kde.org
Reporter: nic...@tuxfamily.org
Target Milestone: ---
Created attachment 131223
--> https://bugs.kde.org/attachment.cgi?id=131223=edit
GPS exif in digikam
SUMMARY
- GPS Processing Method in EXIF panel shows "charset=Ascii " instead of
just "" ("" = "MANUAL" for instance in the attached example).
- GPS Area Information also shows "charset=xxx" or just "binary comment"
Note: GPS Processing Method is a new decoded tag from exiv2 version 0.27.3
Note: GPSProcessingMethod and GPSAreaInformation are both encoded in the same
way as EXIF UserComment. (see details
https://github.com/Exiv2/exiv2/issues/1046#issuecomment-599540926 )
Version: digikam-7.1.0-20200826T123515-x86-64.appimage
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 425809] It is not accentuating.
https://bugs.kde.org/show_bug.cgi?id=425809 --- Comment #13 from Dmitry Kazakov --- It also works fine here on Kubuntu 18.04 with DejaVu Sans and DejaVu Serif (with Finnish keyboard layout) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425809] It is not accentuating.
https://bugs.kde.org/show_bug.cgi?id=425809 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com --- Comment #12 from Dmitry Kazakov --- Accentuation works fine on Windows on Finnish keyboard layout: https://i.imgur.com/q1POCkh.png It might actually depend on the choice of the font. Can it be that the selected font doesn't have these characters? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425830] Colorize Masks always set to visible when opening a file
https://bugs.kde.org/show_bug.cgi?id=425830 Dmitry Kazakov changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/e19f0b97c ||05a264b72f018ed527cd7999757 ||568e Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- Git commit e19f0b97c05a264b72f018ed527cd7999757568e by Dmitry Kazakov. Committed on 27/08/2020 at 21:17. Pushed by dkazakov into branch 'krita/4.3'. Fix loading visibility of colorize masks We shouldn't use KisLayerPropertiesIcons::setNodePropertyAutoUndo() unless we are ready the action to happen asynchronously in a stroke. In the loading code we should just assign the properties directly, without doing any updates or undo actions. M +1-1libs/image/commands/kis_node_property_list_command.cpp M +1-1libs/image/commands/kis_node_property_list_command.h M +2-2libs/image/kis_layer_properties_icons.cpp M +1-2libs/image/kis_layer_properties_icons.h M +1-1libs/ui/kis_node_manager.cpp M +4-2plugins/impex/libkra/kis_kra_loader.cpp M +3-2plugins/impex/libkra/tests/kis_kra_saver_test.cpp M +17 -17 plugins/tools/tool_lazybrush/kis_tool_lazy_brush.cpp M +3-3 plugins/tools/tool_lazybrush/kis_tool_lazy_brush_options_widget.cpp https://invent.kde.org/graphics/krita/commit/e19f0b97c05a264b72f018ed527cd7999757568e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425830] Colorize Masks always set to visible when opening a file
https://bugs.kde.org/show_bug.cgi?id=425830 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/e19f0b97c |hics/krita/commit/b1ff4c756 |05a264b72f018ed527cd7999757 |694add2aa4bf3815ac82621973b |568e|b105 --- Comment #2 from Dmitry Kazakov --- Git commit b1ff4c756694add2aa4bf3815ac82621973bb105 by Dmitry Kazakov. Committed on 27/08/2020 at 21:17. Pushed by dkazakov into branch 'master'. Fix loading visibility of colorize masks We shouldn't use KisLayerPropertiesIcons::setNodePropertyAutoUndo() unless we are ready the action to happen asynchronously in a stroke. In the loading code we should just assign the properties directly, without doing any updates or undo actions. M +1-1libs/image/commands/kis_node_property_list_command.cpp M +1-1libs/image/commands/kis_node_property_list_command.h M +2-2libs/image/kis_layer_properties_icons.cpp M +1-2libs/image/kis_layer_properties_icons.h M +1-1libs/ui/kis_node_manager.cpp M +4-2plugins/impex/libkra/kis_kra_loader.cpp M +3-2plugins/impex/libkra/tests/kis_kra_saver_test.cpp M +17 -17 plugins/tools/tool_lazybrush/kis_tool_lazy_brush.cpp M +3-3 plugins/tools/tool_lazybrush/kis_tool_lazy_brush_options_widget.cpp https://invent.kde.org/graphics/krita/commit/b1ff4c756694add2aa4bf3815ac82621973bb105 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425883] New: Okular crashed while scrolling page
https://bugs.kde.org/show_bug.cgi?id=425883 Bug ID: 425883 Summary: Okular crashed while scrolling page Product: okular Version: 1.9.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: germano.massu...@gmail.com Target Milestone: --- Application: okular (1.9.3) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.7.11-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I opened a PDF and during page scrolling, Okular crashed... -- Backtrace: Application: Okular (okular), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 29return SYSCALL_CANCEL (poll, fds, nfds, timeout); [Current thread is 1 (Thread 0x7f328e835900 (LWP 1131240))] Thread 21 (Thread 0x7f3223fff700 (LWP 1131261)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5650a24f5038) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5650a24f4fe8, cond=0x5650a24f5010) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5650a24f5010, mutex=0x5650a24f4fe8) at pthread_cond_wait.c:638 #3 0x7f3272e3c6db in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f3272e3c1ab in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f32918b2432 in start_thread (arg=) at pthread_create.c:477 #6 0x7f32920d6913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f3240ff9700 (LWP 1131260)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5650a24f5038) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5650a24f4fe8, cond=0x5650a24f5010) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5650a24f5010, mutex=0x5650a24f4fe8) at pthread_cond_wait.c:638 #3 0x7f3272e3c6db in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f3272e3c1ab in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f32918b2432 in start_thread (arg=) at pthread_create.c:477 #6 0x7f32920d6913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f32417fa700 (LWP 1131259)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5650a24f5038) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5650a24f4fe8, cond=0x5650a24f5010) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5650a24f5010, mutex=0x5650a24f4fe8) at pthread_cond_wait.c:638 #3 0x7f3272e3c6db in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f3272e3c1ab in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f32918b2432 in start_thread (arg=) at pthread_create.c:477 #6 0x7f32920d6913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f3241ffb700 (LWP 1131258)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5650a24f5038) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5650a24f4fe8, cond=0x5650a24f5010) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5650a24f5010, mutex=0x5650a24f4fe8) at pthread_cond_wait.c:638 #3 0x7f3272e3c6db in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f3272e3c1ab in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f32918b2432 in start_thread (arg=) at pthread_create.c:477 #6 0x7f32920d6913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f32427fc700 (LWP 1131257)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5650a24f4930) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5650a24f48e0, cond=0x5650a24f4908) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5650a24f4908, mutex=0x5650a24f48e0) at pthread_cond_wait.c:638 #3 0x7f3272e3c6db in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #4 0x7f3272e3c1ab in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #5 0x7f32918b2432 in start_thread (arg=) at pthread_create.c:477 #6 0x7f32920d6913 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f3242ffd700 (LWP 1131256)): #0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5650a24f4930) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5650a24f48e0, cond=0x5650a24f4908) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5650a24f4908, mutex=0x5650a24f48e0) at
[digikam] [Bug 425880] Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 Stephen S. changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425880] Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 --- Comment #3 from Stephen S. --- OK, everything is fine when installing from the last AppImage. I could switch to the MariaDB server which was immediately recognized then could migrate the DB from SQLite to MariaDB. Case closed. Thanks for the help! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425882] New: system settings crash when changing workspace settings
https://bugs.kde.org/show_bug.cgi?id=425882 Bug ID: 425882 Summary: system settings crash when changing workspace settings Product: systemsettings Version: 5.19.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: s.grushk...@gmail.com Target Milestone: --- Application: systemsettings5 (5.19.4) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.8.0-1-default x86_64 Windowing system: Wayland Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: i was changing the settings in workspace settings (making sure that the double click opens files in dolphin) when the app has crashed. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted [KCrash Handler] #4 0x7f1fae42c4b1 in raise () from /lib64/libc.so.6 #5 0x7f1fae415539 in abort () from /lib64/libc.so.6 #6 0x7f1fae836c27 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7f1f75735b30, msg=msg@entry=0x7f1faf31a738 "QPixmap: Must construct a QGuiApplication before a QPixmap") at global/qlogging.cpp:893 #8 0x7f1faee42eff in qt_pixmap_thread_test () at ../../include/QtCore/../../src/corelib/global/qlogging.h:90 #9 qt_pixmap_thread_test () at image/qpixmap.cpp:71 #10 0x7f1faef17ba5 in QPixmap::QPixmap (this=0x7f1f75735bb0) at image/qpixmap.cpp:109 #11 0x7f1faef2613e in QPixmapIconEngine::read (this=0x7f1f60009980, in=...) at image/qicon.cpp:483 #12 0x7f1faef29ac6 in operator>> (s=..., icon=...) at image/qicon.cpp:1450 #13 0x7f1fa985de5a in operator() (__closure=0x55a6dea72598) at /usr/src/debug/kwayland-5.73.0-1.1.x86_64/src/client/plasmawindowmanagement.cpp:646 #15 QtConcurrent::RunFunctionTask::run (this=0x55a6dea72570) at /usr/include/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #16 0x7f1fae8757c2 in QThreadPoolThread::run (this=0x55a6de84b4a0) at thread/qthreadpool.cpp:100 #17 0x7f1fae871871 in QThreadPrivate::start (arg=0x55a6de84b4a0) at thread/qthread_unix.cpp:342 #18 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #19 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in cnd_wait (mtx=0x55a6def1cc40, cond=0x55a6def1cc68) at ../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55a6de9edb00) at ../src/util/u_queue.c:275 #3 0x7f1fa2b7f8b7 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #5 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in cnd_wait (mtx=0x55a6df3c3a00, cond=0x55a6df3c3a28) at ../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55a6df36eef0) at ../src/util/u_queue.c:275 #3 0x7f1fa2b7f8b7 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #5 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in cnd_wait (mtx=0x55a6df190340, cond=0x55a6df190368) at ../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55a6ddd06a00) at ../src/util/u_queue.c:275 #3 0x7f1fa2b7f8b7 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #5 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in cnd_wait (mtx=0x55a6de5cb6c0, cond=0x55a6de5cb6e8) at ../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55a6de26d880) at ../src/util/u_queue.c:275 #3 0x7f1fa2b7f8b7 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #5 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in cnd_wait (mtx=0x55a6deb7ea80, cond=0x55a6deb7eaa8) at ../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55a6de993e60) at ../src/util/u_queue.c:275 #3 0x7f1fa2b7f8b7 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #5 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in cnd_wait (mtx=0x55a6de658300, cond=0x55a6de658328) at ../include/c11/threads_posix.h:155 #2 util_queue_thread_func (input=input@entry=0x55a6de676740) at ../src/util/u_queue.c:275 #3 0x7f1fa2b7f8b7 in impl_thrd_routine (p=) at ../include/c11/threads_posix.h:87 #4 0x7f1fad0b0eaa in start_thread () from /lib64/libpthread.so.0 #5 0x7f1fae4efaff in clone () from /lib64/libc.so.6 #1 0x7f1fa2b7f98b in
[systemsettings] [Bug 407686] sddm_kcm shows an empty error message when I cancel the password dialog to allow the installation of a theme via GHNS window
https://bugs.kde.org/show_bug.cgi?id=407686 Bug Janitor Service changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #8 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/sddm-kcm/-/merge_requests/2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 370359] Unable to use autostart in system config
https://bugs.kde.org/show_bug.cgi?id=370359 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 425469] kmix 20.08.0 crashes on exit
https://bugs.kde.org/show_bug.cgi?id=425469 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #13 from Antonio Rojas --- Any reason the fix wasn't pushed to 20.08? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425880] Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 Maik Qualmann changed: What|Removed |Added Platform|Debian stable |Flatpak -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425879] import: view -> sort order sorts only oldest day
https://bugs.kde.org/show_bug.cgi?id=425879 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/d788463 ||9cc480d28cc74fef2d9bc0c47c5 ||6c96d2 Version Fixed In||7.1.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Maik Qualmann --- Git commit d7884639cc480d28cc74fef2d9bc0c47c56c96d2 by Maik Qualmann. Committed on 27/08/2020 at 20:34. Pushed by mqualmann into branch 'master'. sync in the import view the category sorting and item sorting FIXED-IN: 7.1.0 M +2-2NEWS M +1-0core/utilities/import/models/camitemsortsettings.cpp https://invent.kde.org/graphics/digikam/commit/d7884639cc480d28cc74fef2d9bc0c47c56c96d2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425880] Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 --- Comment #2 from Stephen S. --- Thanks Maik for the prompt response. What I had not figured out is that I am using a Digikam installed from Flatpak. Will install the Debian native version whch should yield better results. Will keep you posted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415150] Save window positions
https://bugs.kde.org/show_bug.cgi?id=415150 --- Comment #28 from Piotr Mierzwinski --- (In reply to Christoph Feck from comment #22) > > developers ignore it > > Developers don't ignore tickets. Multiscreen issues are nearly impossible to > debug, because 1) you need a matching hardware configuration to be able to > reproduce, 2) several software components are involved (xrandr, kscreen, Qt, > Plasma, not to mention X11 and Wayland differences), and 3) timing issues > caused by hardware detection (on connect, disconnect, reconnect, on power > down, on power up, on suspend and sleep modes, ...). I apologize because too harsh words about developers. I face with this issue some time and didn't saw iny reply on my bug reports. Only in first (the oldest on list I put in one post) one developer suggested that my hardware is broken :(, which wasn't truth. I'm not sure where lies the problem of detecting if display is turned on/off. Maybe in possibility of communication by DDC protocol, which seems my display (NEC EA275WMi) and some other like my projector (Optoma) and another monitor produced by DELL doesn't have, or maybe xranr or different X application is not able to get this information from display. I thought that checking and detecting problems with multi monitor configuration isn't so hard if user uses graphics with open source drivers like Intel integra, where is usually uses driver i915 and second thing is just xorg for X11 session. And BTW. Is possible to provide all details about hardware users have, but I noticed nobody asks for it. Maybe some configuration might similar to this what developer has. Anyway I'm not going to push on fixing this issue if event this problem happens in the most popular in the world desktop operating system. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416255] Discover lists as installed addons already uninstalled via system settings
https://bugs.kde.org/show_bug.cgi?id=416255 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/sddm-kcm/-/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424488] Log out then login causes plasmashell to crashes
https://bugs.kde.org/show_bug.cgi?id=424488 deekshith27an...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||deekshith27an...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425746] No thumbnails when importing photos from camera
https://bugs.kde.org/show_bug.cgi?id=425746 --- Comment #20 from Sergio --- (In reply to Maik Qualmann from comment #19) > Thanks for the RAW file. When I copy the file to my memory card and connect > my camera via PTP/MTP, a thumbnail is displayed in digiKam. As the thumbnail > is created by the device with the PTP/MTP protocol, either your D300 camera > cannot do this for RAW files or GPhoto2 makes a mistake with your camera > model. Firmware updated from the camera? Maybe reset the camera to the > factory settings? As mentioned before, this was working before, it isn't something that never worked. Also, when importing with other software which is using gphoto2 as well as darktable, I can perfectly see the thumbnails. I did another test. I used the gphoto2 cli to get the thumbnails of several RAWs directly from my camera using $gphoto2 -t 330-335 I got the thumbnails from all of them with no issues, so I think we can discard that the problem is in libgphoto2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 424909] Dolphin crash *after* copying file between USB-attached Android and external HD in tabs
https://bugs.kde.org/show_bug.cgi?id=424909 --- Comment #2 from Edward --- Yes, using Tree View. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415150] Save window positions
https://bugs.kde.org/show_bug.cgi?id=415150 --- Comment #27 from Piotr Mierzwinski --- (In reply to Nate Graham from comment #24) > See https://invent.kde.org/frameworks/kxmlgui/-/merge_requests/14 Thanks a lot for adding switcher (enable/disable). Your option is very nice and I'm sure that a lot of users will be happy having it in yours KDE/Plasma. I would be very happy, and maybe others also, if option for moving window between displays would be available for taskbar icon (for running and/or minimized application). Reported last year bug: https://bugs.kde.org/show_bug.cgi?id=407647 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kxmlgui] [Bug 415150] Save window positions
https://bugs.kde.org/show_bug.cgi?id=415150 --- Comment #26 from Piotr Mierzwinski --- As I promised. I retested issue on neon-developer and met the same behavior - the newest (unstable) Plasma sees desktop coming from turned off display. Nevertheless I need to apologize what I said about multi monitor configuration in Windows. I claimed that on Windows this works well. Unfortunately doesn't. I tested multi monitor configuration with Windows 10 Professional (so not the newest build) and turned out that Windows behaves the same like Plasma, so desktop coming from turned off display is achievable. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425880] Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 Maik Qualmann changed: What|Removed |Added Severity|major |normal -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425746] No thumbnails when importing photos from camera
https://bugs.kde.org/show_bug.cgi?id=425746 --- Comment #19 from Maik Qualmann --- Thanks for the RAW file. When I copy the file to my memory card and connect my camera via PTP/MTP, a thumbnail is displayed in digiKam. As the thumbnail is created by the device with the PTP/MTP protocol, either your D300 camera cannot do this for RAW files or GPhoto2 makes a mistake with your camera model. Firmware updated from the camera? Maybe reset the camera to the factory settings? Maik -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416255] Discover lists as installed addons already uninstalled via system settings
https://bugs.kde.org/show_bug.cgi?id=416255 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de --- Comment #1 from Alexander Lohnau --- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/229 will fix the cursor theme and some others, icons has already been fixed and SDDM theme is not that trivial. And plasma styles is fixed by a related bugfix (https://invent.kde.org/frameworks/knewstuff/-/merge_requests/25). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425881] New: Do not connect
https://bugs.kde.org/show_bug.cgi?id=425881 Bug ID: 425881 Summary: Do not connect Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: liv...@penserpouragir.org Target Milestone: --- SUMMARY I often use kdeconnect, sometimes with two kdecomputers ans two smartphones. One of my (old)smartphone cannot still connect with others. Sometimes (devices must be up and kdeconnect lauched) it can connect with the other (newer) smartphone, but still not with the two computers. (at the same times the two computers can connect together and with the "newer" smartphone). I checked that I can ping on the (old) smartphone, but do not know how to check on the right port. Do not know if the is a relation, but sometimes connections between computers need association, and I do not know/remenber how I can avtivate or desactivate this security checkup... in case it would be the problem. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 4.15.0-66-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600 CPU @ 3.40GHz Memory: 11.6 Gio of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 2000 On old smartphone samsung GT-S7560M kdeconnect 1.42.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425880] Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Please activate the debug output in the terminal: export QT_LOGGING_RULES="digikam.*=true" Start digiKam in the terminal and post the output in the terminal. It should be a missing package problem. And Qt4 packages are completely out of place. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425877] FAQ hopelessly outdated
https://bugs.kde.org/show_bug.cgi?id=425877 --- Comment #3 from Maik Qualmann --- Seriously, because your question is not answered in the FAQ, should we turn off the FAQ? We have a mailing list where you can ask your questions, other digiKam users and we answer your questions. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425878] No thumbnails forthcoming
https://bugs.kde.org/show_bug.cgi?id=425878 --- Comment #3 from Maik Qualmann --- It may be that there are thumbnails on the device. But digikam requests a thumbnail via the PTP driver, if this is not provided by the device, digiKam would have to download the entire file and create a thumbnail itself, which is exactly what Gwenview does. But it is definitely a fault of the device that it does not fully support the PTP protocol. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425879] import: view -> sort order sorts only oldest day
https://bugs.kde.org/show_bug.cgi?id=425879 Maik Qualmann changed: What|Removed |Added Severity|normal |wishlist CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The sorting only affects the group. The grouping in the import view by date, just like the grouping by format, has a fixed sorting. The digiKam main view can also change the sorting for the groups. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425878] No thumbnails forthcoming
https://bugs.kde.org/show_bug.cgi?id=425878 --- Comment #2 from arne anka --- quote from original report: "thumbnails exist on phone" just opened the folder with gwenview, thumbnaisl weren't ther initially but re-created by gwenview. doesn't bother digikam, though. still no thumbnails. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425880] New: Unable to connect to a remote MariaDB server on "Driver not loaded" error
https://bugs.kde.org/show_bug.cgi?id=425880 Bug ID: 425880 Summary: Unable to connect to a remote MariaDB server on "Driver not loaded" error Product: digikam Version: 7.0.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: step...@asitemade4u.com Target Milestone: --- SUMMARY - I have a MariaDB server (latest, official image) installed on a server within a Docker container container. I know it works as I am able to connect to it through DataGrip - I have created a digikam database as per the instructions - I have installed all MySQL dependencies on the work computer: MySQL client, MySQL-QT4 library, MySQL-QT5 library - And yet, when I test the connection to the digikam database on the server from Digikam, I get a "Driver not loaded" error EXPECTED RESULT SOFTWARE/OS VERSIONS Linux: Debian 10.5, updated, Gnome Digikam: 7.00 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425877] FAQ hopelessly outdated
https://bugs.kde.org/show_bug.cgi?id=425877 --- Comment #2 from arne anka --- Well, surpise: I came to the FAQ because I had an issue I need to solve. If I could rewrite the FAQ I wouldn't need the FAQ. Give the current state it does more harm than it helps. Probably better to take it offline. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425877] FAQ hopelessly outdated
https://bugs.kde.org/show_bug.cgi?id=425877 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Make suggestions for missing FAQs or write and expand the FAQ, your help is very welcome. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425878] No thumbnails forthcoming
https://bugs.kde.org/show_bug.cgi?id=425878 Maik Qualmann changed: What|Removed |Added Component|Import-MainView |Import-IconView -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425878] No thumbnails forthcoming
https://bugs.kde.org/show_bug.cgi?id=425878 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- In PTP mode the thumbnail is sent / created by the connected device. On my Android phone, all thumbnails of image files are displayed. Which phone model do you use? Maik -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 425020] baloosearch's search support for Chinese, Japanese and Korean is very weak.
https://bugs.kde.org/show_bug.cgi?id=425020 --- Comment #22 from Weng Xuetian --- I added the fix in PR for query parser. So I think it's now ready to test: You'll need to purge the old data to trigger the new code. Right now I'm able to search Chinese content/file name quite easily. E.g. $ baloosearch 恋爱 /home/csslayer/Downloads/Telegram Desktop/恋爱循环歌词-中文+罗马音+日文.odt /home/csslayer/Downloads/Telegram Desktop/恋爱循环歌词-中文+罗马音+日文.doc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425879] New: import: view -> sort order sorts only oldest day
https://bugs.kde.org/show_bug.cgi?id=425879 Bug ID: 425879 Summary: import: view -> sort order sorts only oldest day Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-MainView Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@ginguppin.de Target Milestone: --- SUMMARY import -> view: sort items: by date group items: by date earliest images are from 2018-11-19, latest from today item sorting order: asc oldest image of 2018-11-19 is on top item sorting order: desc youngest image of 2018-11-19 is on top EXPECTED RESULT sorting sorts _all_ images, not just the oldest day SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.7.0-3-amd64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4700MQ CPU @ 2.40GHz Memory: 15,4 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 407386] Action shortcut default to "Alt+关" if not specified
https://bugs.kde.org/show_bug.cgi?id=407386 --- Comment #13 from Shinjo Park --- (In reply to Marco Martin from comment #9) > it also chooses the first available letter for those which don't have an &, > which is the same thing happening in qwidget applications when are running > under plasma This does not work at all in some languages, this is basically what the bug report is about. (In reply to Marco Martin from comment #6) > would be ok to restrict automatic shortcuts to standard latin? (then having > to explicitly set one with a non latin string which can have a shortcut) Yes please. Also when if translators need to manually set an accelerator or shortcut key, please clearly mark that cases so translators can take care of that. Currently in QWidget application, no accelerator key will be assigned if the translated string contains no latin-1 character. This is also far from ideal. I also wrote a report about that too: https://marc.info/?l=kde-frameworks-devel=158782004706664=2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425878] New: No thumbnails forthcoming
https://bugs.kde.org/show_bug.cgi?id=425878 Bug ID: 425878 Summary: No thumbnails forthcoming Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-MainView Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@ginguppin.de Target Milestone: --- SUMMARY import view does not show (all) thumbnails. the vast majority of images just show the generic icon and there's no way to force an update. thumbnails exist on phone STEPS TO REPRODUCE 1. connected my phone 2. selected PTP on phone 3. digikam -> Import -> OBSERVED RESULT import view opens with only a couple of thumbnail,s and that doesn't chnage no matter how long i wait EXPECTED RESULT thumbnails appear or an indicator is shown that something is still happening (generating thumbnails maybe?) or a useful error message tells me why there are no thumbnails or there's a button to force thumbnails regeneration/reloading SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Operating System: Debian GNU/Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.7.0-3-amd64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4700MQ CPU @ 2.40GHz Memory: 15,4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425877] New: FAQ hopelessly outdated
https://bugs.kde.org/show_bug.cgi?id=425877 Bug ID: 425877 Summary: FAQ hopelessly outdated Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Website Assignee: digikam-bugs-n...@kde.org Reporter: kde-b...@ginguppin.de Target Milestone: --- > https://www.digikam.org/documentation/faq/ is hopelessly out of date. Of course, there's no date either at the top nor the bottom, but the contents are so far from current KDE/Plasma that it obviouls ynot have been updated in a very long time. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378983] Support loading pulseaudio modules
https://bugs.kde.org/show_bug.cgi?id=378983 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- We kinda do. "Automatically switch all running streams..." setting is basically a front end to enabling the module switch-on-connect. I'm happy to expand on that; I'm not convinced generalising this is going to be a good idea. A lot of modules need extra settings, we want nice human readable names etc. Can you expand on your "for example" list. So we can deterimine what UI works best. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420641] Krita for Android: animation black canvas
https://bugs.kde.org/show_bug.cgi?id=420641 --- Comment #5 from nnn1...@nnn1590.org --- I'm sorry to reply late. The current check confirmed that the canvas did not turn black and could be played normally! Thanks! (I used a machine translation system, I hope the translation is correct.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401727] "My favourites" tag keeps doubling itself, whenever creating a new tag and adding a preset to it the first time
https://bugs.kde.org/show_bug.cgi?id=401727 voronw...@gmail.com changed: What|Removed |Added CC||voronw...@gmail.com Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #8 from voronw...@gmail.com --- Fixed in commit: 7a191ff63a022ba03c56e88e84f953853811c73f -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425655] Microphone icon role in System Tray
https://bugs.kde.org/show_bug.cgi?id=425655 --- Comment #1 from medin --- Created attachment 131222 --> https://bugs.kde.org/attachment.cgi?id=131222=edit microphone icon -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425655] Microphone icon role in System Tray
https://bugs.kde.org/show_bug.cgi?id=425655 --- Comment #2 from medin --- The best way to approach this case by putting together both speaker and microphone icons under one block like what attached image shows. In case where microphone is not used only speaker icon is shown. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419916] GUI fonts rendering in Printer Applet LIST printers is not HiDPI.
https://bugs.kde.org/show_bug.cgi?id=419916 Andrey Kozlovskiy changed: What|Removed |Added CC||andronon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 378983] Support loading pulseaudio modules
https://bugs.kde.org/show_bug.cgi?id=378983 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=425814 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 425814] Audio compressor/limiter
https://bugs.kde.org/show_bug.cgi?id=425814 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=378983 --- Comment #7 from Christoph Feck --- Maybe PulseAudio has a common way to describe plugins/modules together with their UI needs (similar to LADSPA), then this ticket would be a duplicate of bug 378983. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425858] Fonts on Windows are rough
https://bugs.kde.org/show_bug.cgi?id=425858 --- Comment #4 from nide...@gmail.com --- (In reply to David Hurka from comment #2) > Indeed, the screenshot does not look nice. But I see some other roughness in > other parts of the Okular window. E. g. the forward and back arrows look > pretty blocky. > > Does it happen with every document? Also with plaintext (.txt) documents? > > And in case you can check it: Do you have some kind of screen scaling > enabled, maybe only for specific applications? Are you maybe running Okular > in some sandbox like Flatpack, or did you install it directly? Yes, I have a scaling factor different from 100%. The screenshot is on 150% (Windows lists it as recommended), But the problem also appears on every one different from 100%. (On 100% everything is fine.) Also, this appears on every document, even txt and yes, the icons also seems to be blocky too. You can really see it on lines in the icon for Thumbnails and Marking. I have it installed from the Windows Store, and I am running it just normally. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425875] Crashes if selecting animated brush preset in smudge brush engine
https://bugs.kde.org/show_bug.cgi?id=425875 --- Comment #3 from Boudewijn Rempt --- Hm... Could you just mail the file to me, at boudewijnre...@gmail.com? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 385052] Cannot connect to the Akonadi service
https://bugs.kde.org/show_bug.cgi?id=385052 --- Comment #8 from Ahmad Samir --- Thanks for the feedback. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425875] Crashes if selecting animated brush preset in smudge brush engine
https://bugs.kde.org/show_bug.cgi?id=425875 --- Comment #2 from jane...@outlook.com --- (In reply to Boudewijn Rempt from comment #1) > I'm sorry, but I cannot reproduce this. Could you > > * attach the actual gih file, or if it's one that comes with krita, tell us > which one it is > * attach the %LOCALAPPDATA%\kritacrash.log file to this bug report? Sure, here is the log report after the crash. It won't let me attach the gih. file. SESSION: 27 Aug 2020 17:14:26 +0100. Executing E:\programs\krita\Krita (x64)\bin\krita.exe Krita Version: 4.3.0, Qt version compiled: 5.12.8, loaded: 5.12.8. Process ID: 8440 -- -- -- -- -- -- -- -- 27 Aug 2020 17:14:26 +0100: Style: fusion. Available styles: windowsvista, Windows, Fusion 27 Aug 2020 17:14:41 +0100: Created image "Unnamed", 2480 * 3508 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 1 27 Aug 2020 17:17:50 +0100: ASSERT (krita): "m_dstDabRect.size() == m_maskDab->bounds().size()" in file C:\Packaging\workspace\Krita_Release_Windows64_Build\krita\plugins\paintops\colorsmudge\kis_colorsmudgeop.cpp, line 142 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425746] No thumbnails when importing photos from camera
https://bugs.kde.org/show_bug.cgi?id=425746 --- Comment #18 from Sergio --- (In reply to Maik Qualmann from comment #17) > On my Nikon D5300, RAW files are displayed with thumbnails in PTP / MTP > mode. Can you upload a test RAW image of your D300 to a file service? > > Maik Here you are https://sendgb.com/h4gL1dsBPoW -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 385052] Cannot connect to the Akonadi service
https://bugs.kde.org/show_bug.cgi?id=385052 Achim Bohnet changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #7 from Achim Bohnet --- Ups, I think you can close it. My journal start M[130]ach@it01lt:~$ journalctl | grep org.kde.pim.akonadicontrol | grep '<[ec]>' Journal file /var/log/journal/8b6538a40de84811b63f300da18fdd0c/system@0005acc30de1b2b1-7bf0a661f843cc7a.journal~ is truncated, ignoring file. Jun 22 08:50:21 it01lt akonadi_control[8776]: ,2020-06-22T08:50:21 akonadi_control[8776]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Jun 22 08:50:22 it01lt akonadi_control[8776]: ,2020-06-22T08:50:22 akonadi_control[8776]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Jun 22 08:50:23 it01lt akonadi_control[8776]: ,2020-06-22T08:50:23 akonadi_control[8776]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Jun 22 08:50:24 it01lt akonadi_control[8776]: ,2020-06-22T08:50:24 akonadi_control[8776]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Jun 22 08:50:25 it01lt akonadi_control[8776]: ,2020-06-22T08:50:25 akonadi_control[8776]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' crashed. No restart! Jul 11 08:55:29 it01lt akonadi_control[17222]: ,2020-07-11T08:55:29 akonadi_control[17222]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_davgroupware_resource' crashed. No restart! Jul 20 10:45:36 it01lt akonadi_control[7764]: ,2020-07-20T10:45:36 akonadi_control[7764]: org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_akonotes_resource' crashed. No restart! ay, 7th and I only found: entries. Maybe due to KDE apps update of KDE neon distro. For the last weeks akonadi runs svery moothly here. Thx for your work on the great KDE pim tools! I enjoy them every day!!! Achim -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 376170] wrong dates displayed in task list/todo list
https://bugs.kde.org/show_bug.cgi?id=376170 gjditchfi...@acm.org changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #4 from gjditchfi...@acm.org --- I'm optimistic that this bug is fixed in version 5.14.3 (20.04.3); see bug 345498. I'm not a Fedora user, but if I understand https://rpms.remirepo.net/rpmphp/zoom.php?rpm=korganizer correctly, that version will be in Fedora 33. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 425874] Shorter titlebar (without smaller font) option needed: less padding
https://bugs.kde.org/show_bug.cgi?id=425874 --- Comment #2 from Duncan <1i5t5.dun...@cox.net> --- Forgot to mention, all my scaling is 1.0 (on X, obviously). I do /not/ have font-dpi forced but the xorg log says it's the standard 96x96. (Actual physical is dual 4k 75-inch TV-monitors, ~59 dpi according to the online calculator I just googled on ddg. Yes, I'm fighting for that titlebar height even with that sort of screen real estate to work with, as I typically have a video full-screen on one monitor and divide the other into a 2x2 window grid of 1730x1080 px windows with the remainder a gkrelm sysmon. RIP superkaramba. And 15 vs 30 px off the 1080 height of a single standard grid-window is still a big deal, even if that 1080 height is ~18 inches on-screen (with the 15 missing px being a measurable quarter inch!).) (In reply to Christoph Feck from comment #1) > Does it help to reduce the button size? I was using small size, the smallest possible choice, already. My first hack-patch added a tiny (*1.0) option, which did reduce size some, but not enough. So I attacked the padding, and after that I could actually set button size back to /normal/, actually /increasing/ it from small, without increasing the titlebar height. (I think it might have increased it 1 px for normal, but I was OK with that for the full-size button tradeoff, knowing I could always go back to small if I decided to. Once the padding was gone, tiny buttons aka *1.0 was /ridiculously/ tiny, /much/ tinier than either the font or the titlebar (the emblems inside were about the same size as the font was when I tried 4 pt font, unreadable), so it wasn't worth it. As I said, even normal was basically titlebar height, with the existing small below that, so tiny simply wasn't useful. But while I'm actually running normal button size ATM but with the tiny option still in the menu as I didn't actually move that patch out of my auto-patch dir, I'm still throwing in actually removing it from auto-patch as one of the pre-posting tests, just in case my tiny-button addition had some other effect and without it the small size is suddenly much bigger or something. Literally just moved it out for the test when I saw your reply popup in email, matter-of-fact. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423228] Crash in window creation after graphics context loss event
https://bugs.kde.org/show_bug.cgi?id=423228 --- Comment #8 from bertil.bo...@gmail.com --- Created attachment 131221 --> https://bugs.kde.org/attachment.cgi?id=131221=edit New crash information added by DrKonqi plasmashell (5.19.4) using Qt 5.14.2 - What I was doing when the application crashed: This bug still present in 20.04 base. Latte dock crashed and restarted. Then tooltop crash. - Unusual behavior I noticed: So far only with x-rederer. -- Backtrace (Reduced): #4 0x7fbdfb017768 in QScreen::handle (this=0x55b180e892e0) at kernel/qscreen.cpp:158 #5 0x7fbdf63e995e in QXcbIntegration::createPlatformOpenGLContext (this=, context=0x55b182106c80) at qxcbintegration.cpp:279 #6 0x7fbdfb0313a1 in QOpenGLContext::create (this=0x55b182106c80) at ../../include/QtGui/5.14.2/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:109 #7 0x7fbdfc7e8ae1 in QSGRenderThread::sync (this=this@entry=0x55b18388b810, inExpose=inExpose@entry=true, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:615 #8 0x7fbdfc7ea93b in QSGRenderThread::syncAndRender (this=0x55b18388b810, grabImage=0x0) at scenegraph/qsgthreadedrenderloop.cpp:764 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425856] Kwin FPS inconsistent after kwin is suspended
https://bugs.kde.org/show_bug.cgi?id=425856 odzi...@gmail.com changed: What|Removed |Added Component|general |compositing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 425856] Kwin FPS inconsistent after kwin is suspended
https://bugs.kde.org/show_bug.cgi?id=425856 --- Comment #1 from odzi...@gmail.com --- I think I may have found the cause of this issue. I noticed that if I had an application open but minimized, simply hovering over the task manager would not fix the issue. What would fix the issue was unminimizing the window. If all the application I had open were visible on the desktop when suspending/resuming kwin, the fps drops would not occur and my fps would stay at a constant 100. If I suspended/resumed with minimized applications, the issue would occur until all the applications were unminimized. This led me to believe that the issue must have been caused by the thumbnails being generated by the compositor. My "Keep window thumbnails" setting was originally set to "Only for shown windows" but after switching it to "Always" I was no longer experiencing this issue. I have tested it with manually suspending/resuming kwin, having an application block compositing and then closing it and suspending my pc. Issue did not occur a single time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425852] disable middle click to paste to increase usability of KDE applications and KDE desktop
https://bugs.kde.org/show_bug.cgi?id=425852 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO --- Comment #3 from David Edmundson --- Marking as needsinfo based on cfeck's question from 3 years ago. Also don't call developers lazy. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425444] Bottom panel missed every time after reboot with external monitor connected
https://bugs.kde.org/show_bug.cgi?id=425444 --- Comment #1 from zainulla.zhum...@gmail.com --- Hi, could you please respond smth? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425746] No thumbnails when importing photos from camera
https://bugs.kde.org/show_bug.cgi?id=425746 --- Comment #17 from Maik Qualmann --- On my Nikon D5300, RAW files are displayed with thumbnails in PTP / MTP mode. Can you upload a test RAW image of your D300 to a file service? Maik -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 418912] Akonadi IMAP resource in crash loop after moving and deleting folder
https://bugs.kde.org/show_bug.cgi?id=418912 Ahmad Samir changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||a.samir...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #4 from Ahmad Samir --- The backtrace isn't complete, seems to be missing debug symbols. If you can still reproduce this issue, please install the relevant -debuginfo packages and post another backtrace. -- You are receiving this mail because: You are watching all bug changes.
