[kdevelop] [Bug 401724] Crash when losing focus to another screen (likely Wayland related)
https://bugs.kde.org/show_bug.cgi?id=401724 Kevin Funk changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #3 from Kevin Funk --- I agree that this looks like an upstream bug. Though the bug Frances mentioned should be fixed in the reporter's Qt version already... We can't help here. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 401724] Crash when losing focus to another screen (likely Wayland related)
https://bugs.kde.org/show_bug.cgi?id=401724 Kevin Funk changed: What|Removed |Added Summary|Crash when losing focus to |Crash when losing focus to |another screen |another screen (likely ||Wayland related) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #7 from Anna Medonosova --- Created attachment 116665 --> https://bugs.kde.org/attachment.cgi?id=116665=edit Python script that does not trigger the issue -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #6 from Anna Medonosova --- Created attachment 116664 --> https://bugs.kde.org/attachment.cgi?id=116664=edit Python script triggering the issue -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401709] Double clicking a name in a face-frame closes image preview
https://bugs.kde.org/show_bug.cgi?id=401709 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- I agree with Maik proposal from comment #1 Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401709] Double clicking a name in a face-frame closes image preview
https://bugs.kde.org/show_bug.cgi?id=401709 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- The problem only occurs when in the system the double-click is set to open (Windows, Ubuntu...) As a KF5 Plasma users, I am used to the single click when opening the preview and feel it negative under Windows, for example, always have to double-click to open the preview or to return. In setup we have 2 options either open preview or start image editor. My proposition: the preview is always opened and closed on every system with a single click. If the image editor is set, the click behavior is used by the system. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 --- Comment #5 from Anna Medonosova --- Created attachment 116663 --> https://bugs.kde.org/attachment.cgi?id=116663=edit backtrace -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401497] document clone shuts down krita
https://bugs.kde.org/show_bug.cgi?id=401497 Anna Medonosova changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Anna Medonosova --- Thanks for supplying the whole plugin. I have run it and I can confirm the issue, it is present also on linux in git master. The python code triggers the following assert: ASSERT (krita): "!rhs.m_d->projectionUpdatesFilter" in file [..]/src/master/libs/image/kis_image.cc, line 340 How it happens: 1, the plug-in assigns the active document to self.document 2, then it runs self.document.scaleImage() and self.document.crop() 3, while operations from 2 are still running, the plug-in attempts to clone the document with self.document.clone() 4, assert is triggered I attach a simple script (401497_test.py) based on the plug-in code that reproduces the issue, to simplify testing. If I call Document::waitForDone() after scaleImage() and crop() calls, the assert is not triggered (demonstrated by 401497_test_nocrash.py). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401726] New: remote keyboard don't work since android update to 9
https://bugs.kde.org/show_bug.cgi?id=401726 Bug ID: 401726 Summary: remote keyboard don't work since android update to 9 Product: kdeconnect Version: 1.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: sylvain.bouc...@gmail.com Target Milestone: --- Created attachment 116662 --> https://bugs.kde.org/attachment.cgi?id=116662=edit screenshot of andoid screen SUMMARY On my htc u11 life all was working well, thanks, it was the good times. Then my phone updates to android 9. Since then, the virtual input keyboard doesn't work at all. Note that the virtual mouse works well. STEPS TO REPRODUCE 1. a working phone with the previous version of android 2. update the phone to android 9 3. try the virtual keyboard OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Linux Mint 18.3 KDE (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.
[kmail2] [Bug 401685] context menu option for mailing list actions confused about which list is relevant
https://bugs.kde.org/show_bug.cgi?id=401685 Laurent Montel changed: What|Removed |Added Latest Commit||https://commits.kde.org/kma ||il/e6c05ce0c7f18ab44a86124e ||4a8f1ca56750fdac Status|CONFIRMED |RESOLVED Version Fixed In||5.10.0 Resolution|--- |FIXED --- Comment #2 from Laurent Montel --- Git commit e6c05ce0c7f18ab44a86124e4a8f1ca56750fdac by Laurent Montel. Committed on 04/12/2018 at 06:42. Pushed by mlaurent into branch 'Applications/18.12'. Fix Bug 401685 - context menu option for mailing list actions confused about which list is relevant FIXED-IN: 5.10.0 M +1-3src/messageactions.cpp https://commits.kde.org/kmail/e6c05ce0c7f18ab44a86124e4a8f1ca56750fdac -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401720] Kate crash
https://bugs.kde.org/show_bug.cgi?id=401720 Kåre Särs changed: What|Removed |Added CC||kare.s...@iki.fi --- Comment #1 from Kåre Särs --- To me it looks like the problem is either wailand or radeon drivers -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 401638] Segmentation fault (version 5.9.3) when closing the full article
https://bugs.kde.org/show_bug.cgi?id=401638 --- Comment #9 from Vladimir --- Created a corresponding error message. Please correct me in the comments if something is wrong with him and/or vote if you think that the bug should be fixed as soon as possible, thanks. Link 1: https://bugreports.qt.io/browse/QTBUG-72260 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401685] context menu option for mailing list actions confused about which list is relevant
https://bugs.kde.org/show_bug.cgi?id=401685 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Laurent Montel --- I confirm it. -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 401725] Cannot display menu on certain applictaions (e.g. LyX, Kate)
https://bugs.kde.org/show_bug.cgi?id=401725 Litao Lu changed: What|Removed |Added CC||lulitao1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 401725] New: Cannot display menu on certain applictaions (e.g. LyX, Kate)
https://bugs.kde.org/show_bug.cgi?id=401725 Bug ID: 401725 Summary: Cannot display menu on certain applictaions (e.g. LyX, Kate) Product: Active Window Control Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: lulitao1...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Cannot display menu on certain applictaions (e.g. LyX, Kate) STEPS TO REPRODUCE 1. enable global menu in active-window-control. 2. open LyX. 3. click any menu item in the global menu, menu will not pop up. OBSERVED RESULT menu did not pop up. EXPECTED RESULT menu should pop up. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Kernel 4.19 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 active-window-control: latest git version. ADDITIONAL INFORMATION it also happens when clicking (Kate -> Bookmarks) menu. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401657] Falkon AdBlock Works Without Sense
https://bugs.kde.org/show_bug.cgi?id=401657 Felipe changed: What|Removed |Added CC||felipefp...@gmail.com --- Comment #2 from Felipe --- The embedded adblock must be a REALLY old version since there isnt the ability to right click on an ad or image to block it, plus it doesnt make ANY sense to load ALL the lists that were added to block when we go to the options' screen. NO Adblocker EVER does that. Also, several ads are blocked but the spaces arent removed as they should be. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399684] Desktop starts flashing when a new window opens
https://bugs.kde.org/show_bug.cgi?id=399684 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[dolphin] [Bug 400555] Dolphin crashes when trying to empty the trash using the trash-cli command
https://bugs.kde.org/show_bug.cgi?id=400555 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[ring-kde] [Bug 400605] Dial tones do not always work when dialing voicemail mailbox
https://bugs.kde.org/show_bug.cgi?id=400605 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #11 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.
[ktorrent] [Bug 366448] Crash when removing multiple torrents at a time
https://bugs.kde.org/show_bug.cgi?id=366448 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[frameworks-baloo] [Bug 399849] Baloo crashed after I delete a folder containing some files and subfolders
https://bugs.kde.org/show_bug.cgi?id=399849 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #18 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.
[Skanlite] [Bug 348911] Skanlite appears to hang yet pauses for 2 minutes after scanning->saving, and pauses for 2 minutes after returning to main interface
https://bugs.kde.org/show_bug.cgi?id=348911 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 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.
[taglib] [Bug 263136] amarok crashes adding folder to playlist [@ TagLibExtras::RealMedia::MDProperties::~MDProperties]
https://bugs.kde.org/show_bug.cgi?id=263136 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 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.
[kio-extras] [Bug 353350] usbfs: process (MtpConnection) did not claim interface before use
https://bugs.kde.org/show_bug.cgi?id=353350 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[konsole] [Bug 356385] Plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=356385 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 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.
[frameworks-baloo] [Bug 401120] Baloo ignores excluded directories
https://bugs.kde.org/show_bug.cgi?id=401120 --- 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.
[Breeze] [Bug 401101] In Firefox with CSD, the close button does not obey Fitt's Law when maximized
https://bugs.kde.org/show_bug.cgi?id=401101 --- 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.
[systemsettings] [Bug 323976] Add a more powerful tool to adjust behaviors of mice
https://bugs.kde.org/show_bug.cgi?id=323976 --- 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.
[systemsettings] [Bug 376490] KDE5 does not allow configuration of units of measure, time, or date format separate from the single value allowed by locale
https://bugs.kde.org/show_bug.cgi?id=376490 --- 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.
[KBibTeX] [Bug 398010] The source tab is no more active when creating a new element
https://bugs.kde.org/show_bug.cgi?id=398010 --- 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.
[systemsettings] [Bug 132559] FSTAB manager for KControl
https://bugs.kde.org/show_bug.cgi?id=132559 --- 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.
[i18n] [Bug 401705] Error in Translation - KMyMoney Question (Frage)
https://bugs.kde.org/show_bug.cgi?id=401705 Unknown changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Unknown --- SVN commit 1529776 by lueck: fix translation er -> erst, thx for reporting M +1 -1 branches/stable/l10n-kde4/de/messages/extragear-office/kmymoney.po M +2 -2 branches/stable/l10n-kf5/de/messages/extragear-office/kmymoney.po M +2 -2 trunk/l10n-kf5/de/messages/extragear-office/kmymoney.po WebSVN link: http://websvn.kde.org/?view=rev=1529776 -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 401705] Error in Translation - KMyMoney Question (Frage)
https://bugs.kde.org/show_bug.cgi?id=401705 Burkhard Lueck changed: What|Removed |Added Component|translation |de Product|kmymoney|i18n Version|5.0.0 |unspecified Assignee|kmymoney-de...@kde.org |kde-i18n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391613] Plasma sometimes crashes when typing in the search box of the application launcher
https://bugs.kde.org/show_bug.cgi?id=391613 --- Comment #21 from Savor d'Isavano --- So what's up with this bug report? It's been alive for 9 months and the status is not even CONFIRMED? No one replies? What are you guys busy with? If no one cares why would we bother reporting? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 --- Comment #117 from bluescreenaven...@gmail.com --- One odd thing I notice during the test, is that the kioslaves have the high CPU usage, kioclient5 has the high memory usage. I assume that means kioclient5 stores the list of files to copy, and then it must make the kioslave do the copying. My theory was maybe a process (possibly a helper is crashing on the reporters computers, such as kio_file.so) So I tried a smaller, manual test with Dolphin. Copying a smaller directory of ~24 files, Dolphin's memory usage grows a bit (not a lot). So that confirms my theory that Dolphin must stay alive to tell the kioslaves what file to copy. Killing the kioslave that the CPU usage spiked with did NOT result in a silent failure. I got a dialog warning that the file protocol died, and it gave me some options to recover which it recovered from fully. So it's not silently failing because of that. HOWEVER trying again, I went after Dolphin this time. I closed the Dolphin window. The Dolphin process smartly stayed running to continue the copy (so the issue is not the Dolphin window being clsed). As a test, to simulate a crash or abrupt exit of Dolphin, I killed the Dolphin process. Sure enough the copy stopped. ...and I got a "The copy has completed successfully" notification. I wonder if any of the reports are because of Dolphin going down? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 162211] Copying to an external causes lots of missing files
https://bugs.kde.org/show_bug.cgi?id=162211 --- Comment #116 from bluescreenaven...@gmail.com --- I made a script that makes 1,000,000 randomly placed files, with random names, with various sizes from 1kb to 1gb, into 1,000,000 randomly placed folders, with random names. It selects 3 random other directories to fill them with 100,000 additional files each as well. Then it uses kioclient5 to copy the items. https://raw.githubusercontent.com/n3rdopolis/otherstuff/master/kiocopy The names have kinds of random numbers, symbols, some are 20 chars long, some have weird symbols that try to break parsing. It then lets me diff the trees. I I tried it on my KDE frameworks 5.44 box... ...but after all that, I was NOT able to replicate it. the trees match. I have a log, and a seed file for the script, but the .tar.xz is 83MB, and it's quite worthless because it worked perfectly anyway. I am at a loss at how to replicate it. maybe I should change the outlier generated maximum file name size to 220 chars? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 games...@gmail.com changed: What|Removed |Added CC||games...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 401596] Openconnect VPN with 2-factor Authentication Shows Only 1 Password Field
https://bugs.kde.org/show_bug.cgi?id=401596 --- Comment #6 from dareh...@150mail.com --- (In reply to Jan Grulich from comment #3) > Does it work when you downgrade plasma-nm to 5.14.3? I believe this is the > same or similar problem as bug 401554. Sorry for the delay. It works when I downgrade to 5.14.3. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 401724] Crash when losing focus to another screen
https://bugs.kde.org/show_bug.cgi?id=401724 --- Comment #2 from frmdst...@protonmail.com --- Yes using a wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 401724] Crash when losing focus to another screen
https://bugs.kde.org/show_bug.cgi?id=401724 Francis Herne changed: What|Removed |Added CC||m...@flherne.uk Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Francis Herne --- Thanks for the report. I see "libQt5WaylandClient.so.5" in the backtrace - are you using a Wayland session? This looks very much like an upstream bug in Qt; there's nothing KDevelop-related in the trace at all. Maybe similar to https://bugreports.qt.io/browse/QTBUG-63411 . -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 231405] Setting terminal title - ANSI string terminator not supported
https://bugs.kde.org/show_bug.cgi?id=231405 Lucas Yamanishi changed: What|Removed |Added CC||lucas.yamani...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 214547] Kosole KPart needs an API to retrieve $PWD
https://bugs.kde.org/show_bug.cgi?id=214547 Lucas Yamanishi changed: What|Removed |Added CC||lucas.yamani...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 401724] New: Crash when losing focus to another screen
https://bugs.kde.org/show_bug.cgi?id=401724 Bug ID: 401724 Summary: Crash when losing focus to another screen Product: kdevelop Version: 5.3.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: frmdst...@protonmail.com Target Milestone: --- Application: kdevelop (5.3.0) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-39-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: Clicking to an application (firefox) in another window. The window was also on a separate screen. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcc2a489bc0 (LWP 16621))] Thread 16 (Thread 0x7fcb99ffb700 (LWP 16807)): #0 0x7fcc1f90e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640baab7d34) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fcc1f90e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640baab7ce0, cond=0x5640baab7d08) at pthread_cond_wait.c:502 #2 0x7fcc1f90e9f3 in __pthread_cond_wait (cond=0x5640baab7d08, mutex=0x5640baab7ce0) at pthread_cond_wait.c:655 #3 0x7fcc2721994b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc1d50aa65 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fcc1d50eb38 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fcc1d50eb92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fcc1d50eb92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fcc1d50c9fb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fcc27218adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fcc1f9086db in start_thread (arg=0x7fcb99ffb700) at pthread_create.c:463 #14 0x7fcc26b1088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fcb9a7fc700 (LWP 16806)): #0 0x7fcc1f90e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5640baab7d34) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fcc1f90e9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x5640baab7ce0, cond=0x5640baab7d08) at pthread_cond_wait.c:502 #2 0x7fcc1f90e9f3 in __pthread_cond_wait (cond=0x5640baab7d08, mutex=0x5640baab7ce0) at pthread_cond_wait.c:655 #3 0x7fcc2721994b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fcc1d50aa65 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #5 0x7fcc1d50eb38 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fcc1d50eb92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fcc1d50eb92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fcc1d50eb92 in () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fcc1d509c8d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7fcc1d50c9fb in ThreadWeaver::Thread::run() () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7fcc27218adb in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fcc1f9086db in start_thread (arg=0x7fcb9a7fc700) at pthread_create.c:463 #16 0x7fcc26b1088f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7fcb9affd700 (LWP 16805)): #0 0x7fcc1f90e9f3 in
[kmail2] [Bug 401723] New: KMail crashed on exit
https://bugs.kde.org/show_bug.cgi?id=401723 Bug ID: 401723 Summary: KMail crashed on exit Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dennis.schri...@uni-heidelberg.de Target Milestone: --- Application: kmail (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.2-301.fc29.x86_64 x86_64 Distribution: "Fedora release 29 (Twenty Nine)" -- Information about the crash: - What I was doing when the application crashed: I closed KMail. Immediately afterwards I received the crash notification. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff3553a7980 (LWP 9559))] Thread 26 (Thread 0x7ff310ff9700 (LWP 14363)): #0 0x7ff3619d3a68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff35c54bce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7ff35c54d9ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7ff35c54daa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7ff35c552861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7ff35c553d41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7ff35c55e171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7ff3619cd58e in start_thread () at /lib64/libpthread.so.0 #8 0x7ff362a0d593 in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7ff2a7499700 (LWP 9677)): #0 0x7ff3619d367c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff355f60f5a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7ff355f60fc5 in () at /lib64/libQt5Script.so.5 #3 0x7ff3619cd58e in start_thread () at /lib64/libpthread.so.0 #4 0x7ff362a0d593 in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7ff301ffb700 (LWP 9643)): #0 0x7ff362a02371 in poll () at /lib64/libc.so.6 #1 0x7ff3573f25a6 in () at /lib64/libglib-2.0.so.0 #2 0x7ff3573f26d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7ff3630b182b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7ff36306017b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7ff362ec8046 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7ff362ed14bb in () at /lib64/libQt5Core.so.5 #7 0x7ff3619cd58e in start_thread () at /lib64/libpthread.so.0 #8 0x7ff362a0d593 in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7ff3027fc700 (LWP 9628)): #0 0x7ff3629fdf7f in write () at /lib64/libc.so.6 #1 0x7ff36298d98d in _IO_file_write@@GLIBC_2.2.5 () at /lib64/libc.so.6 #2 0x7ff36298ccff in new_do_write () at /lib64/libc.so.6 #3 0x7ff36298e0be in __GI__IO_file_xsputn () at /lib64/libc.so.6 #4 0x7ff36296430a in buffered_vfprintf () at /lib64/libc.so.6 #5 0x7ff3629616e2 in vfprintf () at /lib64/libc.so.6 #6 0x7ff362a1cbaa in __fprintf_chk () at /lib64/libc.so.6 #7 0x7ff3567b8e7f in event_logv_ () at /lib64/libevent-2.1.so.6 #8 0x7ff3567b9048 in event_warn () at /lib64/libevent-2.1.so.6 #9 0x7ff3567baa40 in epoll_dispatch () at /lib64/libevent-2.1.so.6 #10 0x7ff3567b0598 in event_base_loop () at /lib64/libevent-2.1.so.6 #11 0x7ff35c52074d in () at /lib64/libQt5WebEngineCore.so.5 #12 0x7ff35c53f95b in () at /lib64/libQt5WebEngineCore.so.5 #13 0x7ff35c562724 in () at /lib64/libQt5WebEngineCore.so.5 #14 0x7ff35c55e171 in () at /lib64/libQt5WebEngineCore.so.5 #15 0x7ff3619cd58e in start_thread () at /lib64/libpthread.so.0 #16 0x7ff362a0d593 in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7ff302ffd700 (LWP 9627)): #0 0x7ff3619d367c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7ff35c54bc19 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7ff35c54d9c8 in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7ff35c54da5f in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7ff35c51a1df in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7ff35c53f95b in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7ff35c562724 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7ff35c55e171 in () at /lib64/libQt5WebEngineCore.so.5 #8 0x7ff3619cd58e in start_thread () at /lib64/libpthread.so.0 #9 0x7ff362a0d593 in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7ff303fff700 (LWP 9625)): #0 0x7ff355a44c24 in mainloop_defer_enable () at /lib64/libpulse.so.0 #1 0x7ff35569b0d1 in do_pstream_read_write () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7ff35569b4ad in srb_callback () at /usr/lib64/pulseaudio/libpulsecommon-12.2.so #3 0x7ff35569bd3a in
[kwin] [Bug 396585] Kwin Options dialog (Wayland) not responding
https://bugs.kde.org/show_bug.cgi?id=396585 --- Comment #6 from Panos --- Still the same under Fedora Linux 29. KDE 5.14.3 Check this video here: https://www.youtube.com/watch?v=QvoGTHktsg4 I hope this might help. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395157] Setting the realm for openconnect - Juniper makes dialog reload endlessly
https://bugs.kde.org/show_bug.cgi?id=395157 --- Comment #14 from emele...@gmail.com --- Now, this endless loop comes up when using a Juniper server. I had previously used a Cisco Openconnect server with no issues. Apparently Cisco openconnect needs redrawing the widget, while the juniper variant does not, since the dialog already contains all information needed. So I'd suggest testing for the protocol before placing the QTimer::singleShot(). Sadly, openconnect_get_protocol only comes with version 5.5, that has not yet reached my distribution. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401722] New: kamail2 crash
https://bugs.kde.org/show_bug.cgi?id=401722 Bug ID: 401722 Summary: kamail2 crash Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ro...@libero.it Target Milestone: --- Application: kmail (5.9.3) Qt Version: 5.11.1 Frameworks Version: 5.52.0 Operating System: Linux 4.19.5-300.fc29.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I was reading emails and kmail crashed more than once but in the end I can read everything. - Unusual behavior I noticed: also akregator crashes but I can read the articles more difficult because it crashes continuously. Very sorry for my bad english The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4ef867c980 (LWP 7654))] Thread 33 (Thread 0x7f4ebf0b8700 (LWP 7757)): #0 0x7f4f04caeb68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4eff826ce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f4eff8289ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f4eff828aa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f4eff82d861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f4eff82eb5f in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f4eff839171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f4f04ca858e in start_thread () at /lib64/libpthread.so.0 #8 0x7f4f05ce96a3 in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f4ea77fe700 (LWP 7754)): #0 0x7f4f04caeb68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4eff826ce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f4eff8289ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f4eff828aa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f4eff82d861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f4eff82ed41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f4eff839171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f4f04ca858e in start_thread () at /lib64/libpthread.so.0 #8 0x7f4f05ce96a3 in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f4dc33ee700 (LWP 7748)): #0 0x7f4f04caeb68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4eff826ce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f4eff8289ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f4eff828aa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f4eff82d861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f4eff82ed41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f4eff839171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f4f04ca858e in start_thread () at /lib64/libpthread.so.0 #8 0x7f4f05ce96a3 in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f4dc3bef700 (LWP 7747)): #0 0x7f4f04caeb68 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4eff826ce7 in () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f4eff8289ba in () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f4eff828aa2 in () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f4eff82d861 in () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f4eff82ed41 in () at /lib64/libQt5WebEngineCore.so.5 #6 0x7f4eff839171 in () at /lib64/libQt5WebEngineCore.so.5 #7 0x7f4f04ca858e in start_thread () at /lib64/libpthread.so.0 #8 0x7f4f05ce96a3 in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f4e64b5d700 (LWP 7746)): #0 0x7f4f04cae77c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4ef9235f5a in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7f4ef9235fc5 in () at /lib64/libQt5Script.so.5 #3 0x7f4f04ca858e in start_thread () at /lib64/libpthread.so.0 #4 0x7f4f05ce96a3 in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f4e65648700 (LWP 7733)): #0 0x7f4efa714eb4 in g_mutex_lock () at /lib64/libglib-2.0.so.0 #1 0x7f4efa6ccaf6 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f4efa6cd4db in () at /lib64/libglib-2.0.so.0 #3 0x7f4efa6cd6d0 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f4f0638d82b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f4f0633c17b in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f4f061a4046 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f4f061ad4bb in () at /lib64/libQt5Core.so.5 #8 0x7f4f04ca858e in start_thread () at /lib64/libpthread.so.0 #9 0x7f4f05ce96a3 in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f4e677fe700 (LWP
[systemsettings] [Bug 342938] Background is a mess of white and gray patterns
https://bugs.kde.org/show_bug.cgi?id=342938 --- Comment #9 from Christoph Feck --- ... and the screen shot in comment #8 still shows a vertical lines pattern because Qt doesn't use dithering in gradients. If you don't see it, you are lucky. Either bad sight, or bad display :) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401721] New: Grouping with intelligent date range is not respecting discussion start from newest message
https://bugs.kde.org/show_bug.cgi?id=401721 Bug ID: 401721 Summary: Grouping with intelligent date range is not respecting discussion start from newest message Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: stephanolbr...@gmx.de Target Milestone: --- SUMMARY When using intelligend date range for grouping, the discussion start is always first message and never newest message I only have a the german text, sorry: STEPS TO REPRODUCE 1. Goto Configure KMail --> Erscheinungsbild --> Standard-Zusammenstellung --> Einrichten 2. Create or copy a new "Zusammenstellung" 3. In the grouping settings, select intelligent date range and as discussion start, select newest message 4. activate the new Zusammenstellung OBSERVED RESULT Threads are sorted by date of the first message (not the newest) EXPECTED RESULT Threads should be sorted by date of the newest message SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Kubuntu 18.04 (available in About System) KDE Plasma Version: 5.12.7 KDE Frameworks Version: 5.47.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION When selecting "exact date" instead of "intelligent date" everything works as expected -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 401553] Can't "View Document" with question mark in filename
https://bugs.kde.org/show_bug.cgi?id=401553 --- Comment #2 from Christoph Feck --- %2522 is " percent-encoded twice. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 401720] New: Kate crash
https://bugs.kde.org/show_bug.cgi?id=401720 Bug ID: 401720 Summary: Kate crash Product: kate Version: 18.08.0 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: bilal.el...@outlook.com Target Milestone: --- Application: kate (18.08.0) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.6 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: I opened a "config file" plain text document. when I close the file it just crashed. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3af0c4e800 (LWP 8617))] Thread 21 (Thread 0x7f3aba7fc700 (LWP 8638)): #0 0x7f3af480be6c in futex_wait_cancelable (private=, expected=0, futex_word=0x560d94ad1268) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560d94ad1218, cond=0x560d94ad1240) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560d94ad1240, mutex=0x560d94ad1218) at pthread_cond_wait.c:655 #3 0x7f3ae5551d2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f3ae5551a57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f3af4805f2a in start_thread (arg=0x7f3aba7fc700) at pthread_create.c:463 #6 0x7f3af5f9bedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f3abaffd700 (LWP 8637)): #0 0x7f3af480be6c in futex_wait_cancelable (private=, expected=0, futex_word=0x560d94ad1268) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560d94ad1218, cond=0x560d94ad1240) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560d94ad1240, mutex=0x560d94ad1218) at pthread_cond_wait.c:655 #3 0x7f3ae5551d2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f3ae5551a57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f3af4805f2a in start_thread (arg=0x7f3abaffd700) at pthread_create.c:463 #6 0x7f3af5f9bedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f3abb7fe700 (LWP 8636)): #0 0x7f3af480be6c in futex_wait_cancelable (private=, expected=0, futex_word=0x560d94ad1268) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560d94ad1218, cond=0x560d94ad1240) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560d94ad1240, mutex=0x560d94ad1218) at pthread_cond_wait.c:655 #3 0x7f3ae5551d2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f3ae5551a57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f3af4805f2a in start_thread (arg=0x7f3abb7fe700) at pthread_create.c:463 #6 0x7f3af5f9bedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f3abbfff700 (LWP 8635)): #0 0x7f3af480be6c in futex_wait_cancelable (private=, expected=0, futex_word=0x560d94ad1268) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560d94ad1218, cond=0x560d94ad1240) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560d94ad1240, mutex=0x560d94ad1218) at pthread_cond_wait.c:655 #3 0x7f3ae5551d2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f3ae5551a57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f3af4805f2a in start_thread (arg=0x7f3abbfff700) at pthread_create.c:463 #6 0x7f3af5f9bedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f3ad0ff9700 (LWP 8634)): #0 0x7f3af480be6c in futex_wait_cancelable (private=, expected=0, futex_word=0x560d94ad1268) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560d94ad1218, cond=0x560d94ad1240) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x560d94ad1240, mutex=0x560d94ad1218) at pthread_cond_wait.c:655 #3 0x7f3ae5551d2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f3ae5551a57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f3af4805f2a in start_thread (arg=0x7f3ad0ff9700) at pthread_create.c:463 #6 0x7f3af5f9bedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f3ad17fa700 (LWP 8633)): #0 0x7f3af480be6c in futex_wait_cancelable (private=, expected=0, futex_word=0x560d94ad0ce8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x560d94ad0c98, cond=0x560d94ad0cc0) at pthread_cond_wait.c:502 #2
[valgrind] [Bug 401719] sterrror_r on i686 causes a GPF
https://bugs.kde.org/show_bug.cgi?id=401719 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 401719] New: sterrror_r on i686 causes a GPF
https://bugs.kde.org/show_bug.cgi?id=401719 Bug ID: 401719 Summary: sterrror_r on i686 causes a GPF Product: valgrind Version: unspecified Platform: Other URL: https://bugzilla.redhat.com/show_bug.cgi?id=1558107 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: rharw...@redhat.com Target Milestone: --- Created attachment 116661 --> https://bugs.kde.org/attachment.cgi?id=116661=edit reproducer With the attached code, we observe the following: [root@rawhide32 tmp]# gcc -O0 -ggdb -std=c99 test.c -o test [root@rawhide32 tmp]# valgrind ./test ==16919== Memcheck, a memory error detector ==16919== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==16919== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==16919== Command: ./test ==16919== ==16919== ==16919== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==16919== General Protection Fault ==16919==at 0x80485B4: main (test.c:23) ==16919== ==16919== HEAP SUMMARY: ==16919== in use at exit: 0 bytes in 0 blocks ==16919== total heap usage: 0 allocs, 0 frees, 0 bytes allocated ==16919== ==16919== All heap blocks were freed -- no leaks are possible ==16919== ==16919== For counts of detected and suppressed errors, rerun with: -v ==16919== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) Violación de segmento [root@rawhide32 tmp]# rpm -qv glibc gcc glibc-2.27.9000-10.fc29.i686 gcc-8.0.1-0.18.fc29.i686 [root@rawhide32 tmp]# This bug was initially reported downstream to Fedora at https://bugzilla.redhat.com/show_bug.cgi?id=1558107 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 208863] cannot use Super- modifier global shortcuts
https://bugs.kde.org/show_bug.cgi?id=208863 Simone Gaiarin changed: What|Removed |Added CC||simg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #19 from i.Dark_Templar --- I've posted links to patches here for a few reasons. People may try using patches and check if it fixes issue for them too and use it if it does fix the issue. Or someone may even make better fixes. I did a few improvements since originally posting the links. I might post it to the KDE phabricator later, but KDE devs still can find patches here. And posting patches doesn't mean they would be merged into upstream KDE anyway. For example of such hanging patch you may see https://bugs.kde.org/show_bug.cgi?id=383202 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 401718] New: Plasma-nm : controls to add a network are hidden when the window size is small
https://bugs.kde.org/show_bug.cgi?id=401718 Bug ID: 401718 Summary: Plasma-nm : controls to add a network are hidden when the window size is small Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: jul...@coubronne.net Target Milestone: --- On Ubuntu 18.10, the default size of the window opened by the plasma-nm is too small for the controls (the "+" and "-" signs at the bottom of the left list of networks) to show. You have to scroll down to see them. I was confused enough to have to search on google how to add a VPN connection. My suggestion would be to keep the buttons "floating" (i.e. showing without having to scroll), or to move them elsewhere (above the search bar ?). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 401717] New: Ctrl+Shift+R (which closes current tab) is too near to Ctrl+Shift+T (new tab)
https://bugs.kde.org/show_bug.cgi?id=401717 Bug ID: 401717 Summary: Ctrl+Shift+R (which closes current tab) is too near to Ctrl+Shift+T (new tab) Product: yakuake Version: 3.0.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: codestr...@posteo.org Target Milestone: --- >From time to time it happens to me that I accidentally hit Ctrl+Shift+R instead of +T. So, instead of creating a new tab, I destroy the current one which is bad for the workflow :-). Suggestion: Use another default shortcut to close the active tab. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401676] BQM resize tool : allow to resize by percentage (%)
https://bugs.kde.org/show_bug.cgi?id=401676 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/dig ||ikam/779a22e10c8435041bbd90 ||80023a778c4316f2dc Status|REPORTED|RESOLVED Version Fixed In||6.0.0 --- Comment #1 from Maik Qualmann --- Git commit 779a22e10c8435041bbd9080023a778c4316f2dc by Maik Qualmann. Committed on 03/12/2018 at 20:26. Pushed by mqualmann into branch 'master'. add percent option to the BQM resize tool FIXED-IN: 6.0.0 M +2-1NEWS M +56 -19 core/utilities/queuemanager/tools/transform/resize.cpp M +1-0core/utilities/queuemanager/tools/transform/resize.h https://commits.kde.org/digikam/779a22e10c8435041bbd9080023a778c4316f2dc -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401687] kmail doesn't send queued messages
https://bugs.kde.org/show_bug.cgi?id=401687 --- Comment #3 from Konstantin Kharlamov --- Okay, so, I configured 2-nd account, and initially it was okay. Then I started experimenting, sending from one account to another, and I think, after I changed my default identity, mails started piling up again, with error "Failed to transport message. Server error". `aconadyctl restart` doesn't help anymore. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 317666] juk startup is slow if using tree mode
https://bugs.kde.org/show_bug.cgi?id=317666 --- Comment #6 from Stephan Karacson --- Tested it now in an VM with Openuse Tumbleweed in an vm. Juk 18.08.3 Playback works but the "tree mode" is not available. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 401716] New: Volume applet not scrollable when moving stream on sink
https://bugs.kde.org/show_bug.cgi?id=401716 Bug ID: 401716 Summary: Volume applet not scrollable when moving stream on sink Product: plasma-pa Version: 5.14.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: andylem...@googlemail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 116660 --> https://bugs.kde.org/attachment.cgi?id=116660=edit Screenshot of my Plasma Volume applet opened with many sinks SUMMARY STEPS TO REPRODUCE 1. play audio with any program 2. try to move the stream to a sink where you would have to scroll down the list because you have so many sinks 3. OBSERVED RESULT unable to reach the desired sink because the list does not scroll down when moving a stream EXPECTED RESULT scroll the list also when moving a stream SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52 Qt Version: 5.11.2 PulseAudio: 11.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401687] kmail doesn't send queued messages
https://bugs.kde.org/show_bug.cgi?id=401687 --- Comment #2 from Konstantin Kharlamov --- Okay, I managed to make it work on one of PCs with a single account (didn't try setting up second yet)! Something just flashed in my mind, and I decided to try `aconadictl restart`. I got a lot of output, but now KMail works! I didn't even had to restart KMail. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 401715] Doubled network sinks in plasma volume applet
https://bugs.kde.org/show_bug.cgi?id=401715 Lemmiwinks changed: What|Removed |Added Summary|Doubled network sinks in|Doubled network sinks in |plasma volume appket|plasma volume applet -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 401715] Doubled network sinks in plasma volume appket
https://bugs.kde.org/show_bug.cgi?id=401715 Lemmiwinks changed: What|Removed |Added CC||andylem...@googlemail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 401715] New: Doubled network sinks in plasma volume appket
https://bugs.kde.org/show_bug.cgi?id=401715 Bug ID: 401715 Summary: Doubled network sinks in plasma volume appket Product: plasma-pa Version: 5.14.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: andylem...@googlemail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 116659 --> https://bugs.kde.org/attachment.cgi?id=116659=edit Screenshot of my Plasma Volume applet opened SUMMARY STEPS TO REPRODUCE 1. configure pulseaudio to be able to use the sinks of another (remote) pulseaudio server on the network (i.e. #load-module module-zeroconf-publish/discover OBSERVED RESULT All sinks of the remote server are shown doubled on the local machine, with one working and the other not. EXPECTED RESULT Show only the actually available sinks SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52 Qt Version: 5.11.2 PulseAudio: 11.1 ADDITIONAL INFORMATION Remote machine is Kubuntu 18.04, Plasma 5.12.6, KDE Frameworks 5.44, PulseAudio 11.1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401713] Discover shows update that does not exist.
https://bugs.kde.org/show_bug.cgi?id=401713 --- Comment #1 from Jadelir --- SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.4 (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401714] New: Plasma crash when connecting Bluetooth
https://bugs.kde.org/show_bug.cgi?id=401714 Bug ID: 401714 Summary: Plasma crash when connecting Bluetooth Product: plasmashell Version: 5.14.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: manfred.kitzbich...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.14.2) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.18.15-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I tried to connect to my laptop from my mobile phone through Bluetooth, using the computer as audio sink. This has worked in the past. this time, coincidence or not, it seems to have killed Plasma. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7faba079a880 (LWP 2107))] Thread 29 (Thread 0x7fab4dcc9700 (LWP 23304)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fab915f6592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fab915f4689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7faba5d449b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faba4440554 in start_thread () at /lib64/libpthread.so.0 #10 0x7faba5823ccf in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fab4e4ca700 (LWP 23303)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fab915f6592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fab915f4689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7faba5d449b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faba4440554 in start_thread () at /lib64/libpthread.so.0 #10 0x7faba5823ccf in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7fab4f4f2700 (LWP 23302)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fab915f6592 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fab915f4689 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7faba5d449b7 in () at /usr/lib64/libQt5Core.so.5 #9 0x7faba4440554 in start_thread () at /lib64/libpthread.so.0 #10 0x7faba5823ccf in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7fab4fcf3700 (LWP 23301)): #0 0x7faba44464dc in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7faba5d4516b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fab915f2800 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fab915f6538 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fab915f190d in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
[Discover] [Bug 401713] Discover shows update that does not exist.
https://bugs.kde.org/show_bug.cgi?id=401713 Jadelir changed: What|Removed |Added Platform|Other |Neon Packages Component|discover|Updater -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401713] New: Discover shows update that does not exist.
https://bugs.kde.org/show_bug.cgi?id=401713 Bug ID: 401713 Summary: Discover shows update that does not exist. Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: jaderolive...@live.com Target Milestone: --- Created attachment 116658 --> https://bugs.kde.org/attachment.cgi?id=116658=edit Screenshot shows the ishue 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 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 Kyle Tirak changed: What|Removed |Added CC||lonefen...@gmail.com --- Comment #5 from Kyle Tirak --- I filed the sddm issue. I'll look deeper into my env tomorrow. It seems to be a volatile issue for me as its gone from applications not being able to communicate with the gnome-keyring-daemon, to the daemon not starting on login, and back to the daemon starting but not communicating over the last several months. I'll note that I am also on Arch Linux, so there is some possibility of it being a packaging issue as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401711] motif/nedit: open file -> new window is not activated
https://bugs.kde.org/show_bug.cgi?id=401711 Martin Flöser changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- The application needs to set proper transient for hints. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401712] New: Blur brush mixes colour with white when near the edge of image
https://bugs.kde.org/show_bug.cgi?id=401712 Bug ID: 401712 Summary: Blur brush mixes colour with white when near the edge of image Product: krita Version: 4.1.5 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: major Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: kali...@wp.pl Target Milestone: --- SUMMARY So I'm using a predefined brush k)_Blender_Blur (though any Blender Brush causes the issue) - whenever I'm near the border of the picture, it starts mixing white into the colours I'm blending - this causes it impossible to bled colours near the picture edge. STEPS TO REPRODUCE 1. Create a file with any-but-white colour layer (so the issue is visible). 2. Use any blur brush near the picture edge. OBSERVED RESULT Krita blends white (apparently there's "infinite white space" beyond the visible canvas) into the colour when blending near the picture edge. EXPECTED RESULT Only pixels on the visible canvas are taken into account when calculating blend outcome (if needed - edge pixels are repeated to "fill" the required blur brush shape). SOFTWARE/OS VERSIONS Windows 7 x64 KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 395157] Setting the realm for openconnect - Juniper makes dialog reload endlessly
https://bugs.kde.org/show_bug.cgi?id=395157 --- Comment #13 from emele...@gmail.com --- (In reply to Jan Grulich from comment #12) > You can ignore the proposed patch, it won't work if we need to reload the > dialog in case we change the group initially. I tried this second patch and it did not work (no endless loop, but no login). However, your original patch did work for me: I was able to change the group and log in. Hope you get the issue straight. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370023] plasmashell crash when attempting to use search bar
https://bugs.kde.org/show_bug.cgi?id=370023 --- Comment #4 from Marcus Harrison --- Fine by me, tried reproducing it and can't. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401711] New: motif/nedit: open file -> new window is not activated
https://bugs.kde.org/show_bug.cgi?id=401711 Bug ID: 401711 Summary: motif/nedit: open file -> new window is not activated Product: kwin Version: 5.12.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: isj-bugzi...@i1.dk Target Milestone: --- SUMMARY When opening a file in a new window in Nedit the new window is not activated STEPS TO REPRODUCE 1. Install/build Nedit 5.7 2. Start Nedit 3. Disable tabbed editing (Preferences -> Default preferences -> Tabbed editing -> Disable "Open file in New tab") 4. Open "Open file" dialog (ctrl-O) 5. Select any file to open 6. [enter] Other Motif applications that open new windows based on a Open File dialog may exhibit the same problem. OBSERVED RESULT The Open File dialog disappears, the original nedit window is activated, and the window with the new file is not activated or brought to top. Sometimes it is even hidden behind other windows. EXPECTED RESULT The new editing window should be activated and brought to top. SOFTWARE/OS VERSIONS OpenSUSE Leap 15.0 KDE Plasma Version: 5.12.6 ? KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 ADDITIONAL INFORMATION When pressing [enter] in file dialog Nedit unmaps the file dialog and then creates a new window. I suspect that kwin tries to activate the original edit window and cannot handle that a new window (even from the same application) is created+mapped while doing that. Changing "focus stealing prevention" to "none" has no effect. This problem did not exist with kwin-4.11.2 -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 332191] Kget crash after server authenticate cancel
https://bugs.kde.org/show_bug.cgi?id=332191 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #13 from Wolfgang Bauer --- I'm not able to reproduce this crash, even though it apparently still can happen in the latest version. Can somebody affected please try to rename the file ~/.local/share/kget/transfers.kgt and report back if it helps? (in earlier versions it would be ~/.kde(4)/share/apps/kget/transfers.kgt) If yes, please attach the problematic file. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 401494] inefficient-qlist & inefficient-qlist-soft fail on 32bit Linux architectures
https://bugs.kde.org/show_bug.cgi?id=401494 Sergio Martins changed: What|Removed |Added Resolution|--- |FIXED Latest Commit|https://commits.kde.org/cla |https://commits.kde.org/cla |zy/9713a15f65424f06e45c78fc |zy/ad8e58e41537a9656b7924b5 |1bf1c2d2b27f4e36|447fdb6e7bbad43e Status|REOPENED|RESOLVED --- Comment #4 from Sergio Martins --- Git commit ad8e58e41537a9656b7924b5447fdb6e7bbad43e by Sergio Martins. Committed on 03/12/2018 at 18:59. Pushed by smartins into branch '1.4'. inefficient-qlist: Fix unit-tests on 32-bit. M +1-1tests/inefficient-qlist-soft/main.cpp M +1-1tests/inefficient-qlist/main.cpp https://commits.kde.org/clazy/ad8e58e41537a9656b7924b5447fdb6e7bbad43e -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 386945] Bogus memcheck errors on ppc64(le) when using strcmp() with gcc-7
https://bugs.kde.org/show_bug.cgi?id=386945
--- Comment #48 from Carl Love ---
Mark:
I took your patch " implement ldbrx as 64-bit load and Iop_Reverse8sIn64_x1" in
comment 44, attachment 116593 and applied it to current mainline.
commit f2387ed7bed64571197b44c1f8abae4d907bce1b
Author: Mark Wielaard
Date: Fri Nov 30 15:23:06 2018 -0500
Implement ppc64 ldbrx as 64-bit load and Iop_Reverse8sIn64_x1.
commit 206e81e8add574bbb38c11105005decedabc2f4a
Author: Mark Wielaard
Date: Sun Dec 2 12:39:27 2018 +0100
Fix tsan_unittest.cpp compile error with older compilers.
Older compilers (g++ 4.8.5) don't like '>>':
error: ‘>>’ should be ‘> >’ within a nested template argument list.
Add an extra space.
Then compiled and installed valgrind.
I then ran your string program in comment 45 on P7, P8 BE, P8 LE, P9 as
follows:
gcc -o mark_test ../mark_test.c
valgrind ./mark_test
On Power 7, Power 8 BE, Power 8 LE, Power 9 LE running the test:
valgrind ./mark_test
==18373== Memcheck, a memory error detector
==18373== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==18373== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright
info
==18373== Command: ./mark_test
==18373==
no
==18373==
==18373== HEAP SUMMARY:
==18373== in use at exit: 0 bytes in 0 blocks
==18373== total heap usage: 1 allocs, 1 frees, 5 bytes allocated
==18373==
==18373== All heap blocks were freed -- no leaks are possible
==18373==
==18373== For counts of detected and suppressed errors, rerun with: -v
==18373== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Running natively an all of these systems gives:
./mark_test
no
I read thru the patch, it looks fine. I do think there might be an
easier/faster way to implement the ldbrx instruction.
Your patch does the following:
+ assign( dw1, load(Ity_I64, mkexpr(EA)) );
+ assign( dw2, unop(Iop_Reverse8sIn64_x1, mkexpr(dw1)) );
+ putIReg( rD_addr, mkexpr(dw2) );
Note, load(Ity_I64, mkexpr(EA)) does an endian aware load:
/* This generates a normal (non load-linked) load. */
static IRExpr* load ( IRType ty, IRExpr* addr )
{
if (host_endness == VexEndnessBE)
return IRExpr_Load(Iend_BE, ty, addr);
else
return IRExpr_Load(Iend_LE, ty, addr);
}
I think if you were to call IRExpr_Load to do the load as follows:
/* Load the value with the bytes reversed by doing a BE load on an LE machine
and a LE load on a BE machine. */
if (host_endness == VexEndnessBE)
assign( dw1, IRExpr_Load(Iend_LE, Ity_I64, mkexpr(EA)));
else
assign( dw1, IRExpr_Load(Iend_BE, Ity_I64, mkexpr(EA)));
putIReg( rD_addr, mkexpr(dw1) );
You wouldn't actually need to do the byte reverse with Iop_Reverse8sIn64_x1 as
the value would be loaded with the bytes reversed already. That said, having
support for the Iop_Reverse8sIn64_x1 is nice to have around for future use.
:-)
Any way, I did work thru the logic and coding for the Iop_Reverse8sIn64x1 and
it all looks correct.
Carl Love
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 401710] New: Konsole chrash
https://bugs.kde.org/show_bug.cgi?id=401710 Bug ID: 401710 Summary: Konsole chrash Product: konsole Version: 18.04.0 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: bilal.el...@outlook.com Target Milestone: --- Application: konsole (18.04.0) Qt Version: 5.11.2 Frameworks Version: 5.51.0 Operating System: Linux 4.19.6 x86_64 Distribution: Debian GNU/Linux testing (buster) -- Information about the crash: - What I was doing when the application crashed: I run avahi-daemon.service in konsole then when I try to close konsole it crashed. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f19c606a840 (LWP 2440))] Thread 22 (Thread 0x7f19433fe700 (LWP 2494)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f19ce7702f1 in __GI_abort () at abort.c:79 #8 0x7f19cccec987 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f19cd2d80e2 in ?? () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #10 0x7f19cd391724 in QPixmap::QPixmap() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f19cd3a0a37 in QPixmapIconEngine::read(QDataStream&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #12 0x7f19cd3a279e in operator>>(QDataStream&, QIcon&) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #13 0x7f19c577921c in ?? () from /lib/x86_64-linux-gnu/libKF5WaylandClient.so.5 #14 0x7f19ccd25f81 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f19ccd2dc97 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f19cb7bef2a in start_thread (arg=0x7f19433fe700) at pthread_create.c:463 #17 0x7f19ce830edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 21 (Thread 0x7f19777fe700 (LWP 2461)): #0 0x7f19cb7c4e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55a8522258a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a852225858, cond=0x55a852225880) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a852225880, mutex=0x55a852225858) at pthread_cond_wait.c:655 #3 0x7f19c261dd2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f19c261da57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f19cb7bef2a in start_thread (arg=0x7f19777fe700) at pthread_create.c:463 #6 0x7f19ce830edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7f1977fff700 (LWP 2460)): #0 0x7f19cb7c4e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55a8522258a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a852225858, cond=0x55a852225880) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a852225880, mutex=0x55a852225858) at pthread_cond_wait.c:655 #3 0x7f19c261dd2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f19c261da57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f19cb7bef2a in start_thread (arg=0x7f1977fff700) at pthread_create.c:463 #6 0x7f19ce830edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f1988ff9700 (LWP 2459)): #0 0x7f19cb7c4e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55a8522258a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a852225858, cond=0x55a852225880) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a852225880, mutex=0x55a852225858) at pthread_cond_wait.c:655 #3 0x7f19c261dd2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f19c261da57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f19cb7bef2a in start_thread (arg=0x7f1988ff9700) at pthread_create.c:463 #6 0x7f19ce830edf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f19897fa700 (LWP 2458)): #0 0x7f19cb7c4e6c in futex_wait_cancelable (private=, expected=0, futex_word=0x55a8522258a8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55a852225858, cond=0x55a852225880) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55a852225880, mutex=0x55a852225858) at pthread_cond_wait.c:655 #3 0x7f19c261dd2b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f19c261da57 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f19cb7bef2a in start_thread (arg=0x7f19897fa700) at pthread_create.c:463 #6 0x7f19ce830edf in clone () at
[kget] [Bug 332191] Kget crash after server authenticate cancel
https://bugs.kde.org/show_bug.cgi?id=332191 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Version|2.12.2 |18.08 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401709] New: Double clicking a name in a face-frame closes image preview
https://bugs.kde.org/show_bug.cgi?id=401709 Bug ID: 401709 Summary: Double clicking a name in a face-frame closes image preview Product: digikam Version: 5.9.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: skydive...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. From thumbnail images view, double click an image to to to preview mode 2. Add a face frame or edit and existing one 3. Double click the frame's textbox Reproducible: Always OBSERVED RESULT The image preview window closes and switches back to thumbnail view. EXPECTED RESULT All the text in the textbox should become selected SOFTWARE/OS VERSIONS Linux: Ubuntu KDE Frameworks Version: 5.42.0 Qt Version: 5.9.3 -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 332191] Kget crash after server authenticate cancel
https://bugs.kde.org/show_bug.cgi?id=332191 Wolfgang Bauer changed: What|Removed |Added CC||ghzooo...@gmail.com --- Comment #12 from Wolfgang Bauer --- *** Bug 401640 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 401640] KGet crashes starting it from kickstart after fresh boot
https://bugs.kde.org/show_bug.cgi?id=401640 Wolfgang Bauer changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer --- Same backtrace as in bug 332191. Unfortunately, I'm not able to reproduce it... :-/ *** This bug has been marked as a duplicate of bug 332191 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia
https://bugs.kde.org/show_bug.cgi?id=364766 --- Comment #56 from hant0508 --- (In reply to S. Christian Collins from comment #55) > (In reply to hant0508 from comment #54) > > I've reproduced the bug using 390.x Nvidia driver and QT 5.11. Then I've > > updated Nvidia driver to 415.x version and the bug disappeared. > > Weird; I'm using NVIDIA driver 415.18 and Qt 5.11.2 and I still have the bug > on GeForce GTX 970. What OS & card are you using? I'm using Ubuntu 18.10 and Nvidia GeForce GT 730M. Btw, some little artifacts remains, e.g. white squares on Latte Dock icons (can be fixed with "latte-dock -r"), but lagging cursor, blur and most other distortions disappeared after driver upgrade. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 399267] hovering cursor over file displays file info in status bar for only 1 second
https://bugs.kde.org/show_bug.cgi?id=399267 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #2 from Nate Graham --- I'm actually not convinced that the status bar should show the file info at all when the information panel is open; it's redundant. We should definitely fix this bug, but we might want to consider not changing the status bar display at all when the information panel is open. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 401708] New: Next/Previous hotkeys cause OSD to show volume rather than song title
https://bugs.kde.org/show_bug.cgi?id=401708 Bug ID: 401708 Summary: Next/Previous hotkeys cause OSD to show volume rather than song title Product: amarok Version: 2.9.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: amarok-bugs-d...@kde.org Reporter: to.roma.from.kde...@qwertty.com Target Milestone: kf5 SUMMARY With Amarok OSD (not knotify), pressing the Next or Previous hotkeys cause the OSD to show the current volume, even though nothing changed it. This is a regression, as previous versions showed the next song’s title in this case, which is the natural thing to do. STEPS TO REPRODUCE 1. Start playing a song 2. Press your global hotkey for Next (or cause the next song to be played by any other means, it’s all the same) OBSERVED RESULT The next song starts playing as expected, but the OSD that appears is showing the current volume for some reason. EXPECTED RESULT The OSD should display the song title instead, which it correctly does when a song ends and a new one starts, but the problem occurs if the song changes due to a user action. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.13.5 KDE Frameworks Version: 5.50.0 Qt Version: 5.11.1 ALSA is being used, no PulseAudio, if this matters. Phonon backend is GStreamer. -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 401707] Touchpad off OSD message is displayed on resuming after suspending in Wayland
https://bugs.kde.org/show_bug.cgi?id=401707 --- Comment #1 from Alexander Mentyu --- Same message with disabled lock screen on resume -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401705] Error in Translation - KMyMoney Question (Frage)
https://bugs.kde.org/show_bug.cgi?id=401705 Thomas Baumgart changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||lu...@hube-lueck.de --- Comment #1 from Thomas Baumgart --- Still present in 5.0.2 -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 401707] New: Touchpad off OSD message is displayed on resuming after suspending in Wayland
https://bugs.kde.org/show_bug.cgi?id=401707 Bug ID: 401707 Summary: Touchpad off OSD message is displayed on resuming after suspending in Wayland Product: Touchpad-KCM Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: daemon Assignee: rajeeshknamb...@gmail.com Reporter: notux...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Login into Wayland. 2. Suspend system. 3. Wake up system. OBSERVED RESULT Touchpad off OSD is displayed on top of unlock screen EXPECTED RESULT Touchpad off OSD is displayed - like on resume in X session (or even no OSD message) SOFTWARE/OS VERSIONS Operating System: KDE neon Developer Edition KDE Plasma Version: 5.14.80 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-39-generic ADDITIONAL INFORMATION Lenovo Yoga 520 laptop -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 401706] New: crash repetetive lors des actions enummuré ci-dessous
https://bugs.kde.org/show_bug.cgi?id=401706 Bug ID: 401706 Summary: crash repetetive lors des actions enummuré ci-dessous Product: Falkon Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: tmack...@gmail.com Target Milestone: --- SUMMARY crash lors de la consultation des site web surtout lors de lecture video sur youtube et aussi pendant mon cours sur Udemy. STEPS TO REPRODUCE 1.crash si j active jupyter notebook 2.crash quand je travaille avec anaconda navigator 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.
[systemsettings] [Bug 342938] Background is a mess of white and gray patterns
https://bugs.kde.org/show_bug.cgi?id=342938 aus...@essex-tech.com changed: What|Removed |Added CC||aus...@essex-tech.com --- Comment #8 from aus...@essex-tech.com --- Created attachment 116657 --> https://bugs.kde.org/attachment.cgi?id=116657=edit System Settings background, non-breeze I know this bug is marked resolved / fixed, but just wanted to point out that this function *can* look nice and add a touch of class when used with different color schemes, for example the attached custom QtCurve / color combo -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 343383] After activating mouse gestures the selected button to activate a gesture does not respond
https://bugs.kde.org/show_bug.cgi?id=343383 --- Comment #36 from tuxflo --- @alekksander I found out that Easystroke was not working because I was inside a VBox VM. On bare metal it works. But I also found another little tool that just fits my mouse gesture needs and works great: https://github.com/deters/mygestures It is even possible to start this tool twice with different mouse buttons so one can define mouse gestures for the middle mouse button 2 and other ones for mouse button 3. -- You are receiving this mail because: You are watching all bug changes.
[parley] [Bug 307936] Fetching scripts throw exceptions
https://bugs.kde.org/show_bug.cgi?id=307936 --- Comment #5 from rusty.robo...@gmail.com --- I cannot re-test this due to Parley 18.8.3 not able to even activate the scripts: > Activating Script "/usr/share/parley/plugins/google_dictionary.py" > "Parley" > Kross: "Error error=Failed to determine interpreter for scriptfile > \"/usr/share/parley/plugins/google_dictionary.py\" lineno=-1 trace=\n" > Script not activated > Activating Script "/usr/share/parley/plugins/leo-dict.py" > "Parley" > Kross: "Error error=Failed to determine interpreter for scriptfile > \"/usr/share/parley/plugins/leo-dict.py\" lineno=-1 trace=\n" > Script not activated > Activating Script "/usr/share/parley/plugins/wiktionary_sound.py" > "Parley" > Kross: "Error error=Failed to determine interpreter for scriptfile > \"/usr/share/parley/plugins/wiktionary_sound.py\" lineno=-1 trace=\n" > Script not activated -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 401705] New: Error in Translation - KMyMoney Question (Frage)
https://bugs.kde.org/show_bug.cgi?id=401705 Bug ID: 401705 Summary: Error in Translation - KMyMoney Question (Frage) Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: translation Assignee: kmymoney-de...@kde.org Reporter: schoenes-...@web.de Target Milestone: --- Created attachment 116656 --> https://bugs.kde.org/attachment.cgi?id=116656=edit Screenshot SUMMARY STEPS TO REPRODUCE 1. Modify any line item in KMyMoney 2. Click "SICHERUNG" 3. "Frage" dialog is shown with text, "Die Datei muss er gespeichert werden, ..." OBSERVED RESULT Incorrect use of word, "er" EXPECTED RESULT Must be replaced by, "erst" SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- @now-im to help narrow it down, please run "env" in both the X and wayland case and look for differences there wrt gnome keyring. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401700] Cache images of apps/Plasma addons so that their previews didn't load on every scroll
https://bugs.kde.org/show_bug.cgi?id=401700 Nate Graham changed: What|Removed |Added Version Fixed In||5.15.0 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 401681] libsecrect/ gnome-keyring not working under wayland
https://bugs.kde.org/show_bug.cgi?id=401681 --- Comment #3 from Martin Flöser --- There is no indication that this is a kde problem. All we know is that using two non kde applications don't work in a plasma Wayland session. What we also know is that at least one of those applications is not intended to be used outside of gnome. The problem is certainly not in anything kde provides. If you need user support to set this up please consult the user support of the named applications. Kde's bug tracker is not a user support forum, though. If there is any evidence showing that this is truly a bug in our software, please provide it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401666] Discover window freezes after it's opening when internet connection is absent
https://bugs.kde.org/show_bug.cgi?id=401666 Alexander Mentyu changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|BACKTRACE |--- --- Comment #5 from Alexander Mentyu --- Added bt -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 401666] Discover window freezes after it's opening when internet connection is absent
https://bugs.kde.org/show_bug.cgi?id=401666 --- Comment #4 from Alexander Mentyu --- Created attachment 116655 --> https://bugs.kde.org/attachment.cgi?id=116655=edit Discover backtrace after launch when internet connection is absent -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 401704] Accepting Google Calendar invite makes me the organizer and duplicates the event
https://bugs.kde.org/show_bug.cgi?id=401704 Daniel Robbins changed: What|Removed |Added CC||k...@danieljrobbins.com -- You are receiving this mail because: You are watching all bug changes.
