[kate] [Bug 458554] LSP plugin quickfix action has no effect anymore
https://bugs.kde.org/show_bug.cgi?id=458554
--- Comment #1 from Markus Pister ---
To help in identifying the issue cause in the code, I bisected kate with the
following result:
bccf9a58ab1bb6f435eb942b46a2931dd9aedd0d is the first bad commit
commit bccf9a58ab1bb6f435eb942b46a2931dd9aedd0d
Author: Mark Nauwelaerts
Date: Wed Feb 9 21:47:26 2022 +0100
lspclient: use multiple items for a diagnostic item with embedded newlines
addons/lspclient/lspclientpluginview.cpp | 30 ++
1 file changed, 26 insertions(+), 4 deletions(-)
Funnily, my proposed test code did not exhibit a quickfix action anymore, so I
worked on the following test code (put into test.cpp):
int sensor;
int main()
{
senSor = 0;
return 0;
}
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 458586] Krita with a Wacom Intuos Pro (Large) Zoom/Pan pen functionality causes Krita canvas to become unusable
https://bugs.kde.org/show_bug.cgi?id=458586 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|FIXED |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 456999] Email developer triggers unexpected close
https://bugs.kde.org/show_bug.cgi?id=456999 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.
[plasmashell] [Bug 457991] Plasma panel crashes right after login if the mouse pointer is where the panel will be created
https://bugs.kde.org/show_bug.cgi?id=457991 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457989] The system freezes when flipping through desktops using a three-finger gesture on the touch panel
https://bugs.kde.org/show_bug.cgi?id=457989 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 411211] Activity without recent documents and programs
https://bugs.kde.org/show_bug.cgi?id=411211 --- 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.
[frameworks-kglobalaccel] [Bug 393619] Pressing AltGr (configured as Compose Key) on wayland, results in opening google.com
https://bugs.kde.org/show_bug.cgi?id=393619 --- 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.
[kate] [Bug 458624] [LSP] Omnisharp-roslyn Launches Out of Scope
https://bugs.kde.org/show_bug.cgi?id=458624 nekone...@protonmail.ch changed: What|Removed |Added Alias||omnisharp -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 452813] [LSP] Add Omnisharp-roslyn C# Language Server to the Default Settings List
https://bugs.kde.org/show_bug.cgi?id=452813 nekone...@protonmail.ch changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=458624 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458624] New: [LSP] Omnisharp-roslyn Launches Out of Scope
https://bugs.kde.org/show_bug.cgi?id=458624 Bug ID: 458624 Summary: [LSP] Omnisharp-roslyn Launches Out of Scope Product: kate Version: 22.08.0 Platform: Archlinux Packages URL: https://aur.archlinux.org/packages/omnisharp-roslyn OS: Linux Status: REPORTED Keywords: needs_verification, usability Severity: normal Priority: NOR Component: scripting Assignee: kwrite-bugs-n...@kde.org Reporter: nekone...@protonmail.ch Target Milestone: --- Flags: Usability+ Created attachment 151776 --> https://bugs.kde.org/attachment.cgi?id=151776=edit LSP Output Log SUMMARY The Omnisharp language server is started by Kate in what seems to be the home directory rather than where the project folder is; this causes Omnisharp not to be able to find the desired C# solution (.sln) and not provide LSP support as it should. (Omnisharp version 1.39.1) STEPS TO REPRODUCE 1. Install Omnisharp-roslyn (There's several AUR pages for it; I provided one in the URL section of this report) 2. Clone a C# project from a source repository 3. Open the project folder with Kate (Kate will prompt the user to enable the language server) OBSERVED RESULT The language server is started but doesn't provide any of the intended functions, possibly due to being out of scope of the project location EXPECTED RESULT The language server should be directed to the C# project appropriately to provide LSP data SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458586] Krita with a Wacom Intuos Pro (Large) Zoom/Pan pen functionality causes Krita canvas to become unusable
https://bugs.kde.org/show_bug.cgi?id=458586 --- Comment #3 from Noah --- (In reply to sh_zam from comment #2) > Hello! Can you please attach Tablet Event logs both before and right after? > (https://docs.krita.org/en/contributors_manual/user_support.html#gathering- > information). The "Step 5" here (Ctrl + Shift + T). Sorry for the delay; work has been busy! The log before the bug occurs: https://pastebin.com/DStHB9nH (normal) The log after the bug occurs: https://pastebin.com/sYDW2RV7 (noticed the line "Start blocking mouse events" after I click and hold the pen button and touch the tablet) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 458623] New: Pasting multiple copies of clips doesn't work
https://bugs.kde.org/show_bug.cgi?id=458623 Bug ID: 458623 Summary: Pasting multiple copies of clips doesn't work Product: kdenlive Version: 22.08.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: findemnfi...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Add multiple copies of a video clip to a track. In my case, I'm trying to loop a 22 second clip to cover 90 minutes of video 2. Hold the shift key and select multiple (>5) copies of the video clip 3. Try to paste the copies into a later section of the track OBSERVED RESULT You get the error "Could not paste items in timeline" EXPECTED RESULT Paste the selected copies at the location specified SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 22.08.0 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 458620] Batch Queue Manager does not offer a "Color Negative Film" tool
https://bugs.kde.org/show_bug.cgi?id=458620 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|BatchQueueManager-Plugins |Plugin-Bqm-WishForNewTools -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458261] Dolphin doesn't remember size
https://bugs.kde.org/show_bug.cgi?id=458261 Oliver Beard changed: What|Removed |Added CC||olib...@outlook.com --- Comment #9 from Oliver Beard --- I can reproduce this by closing the window with ALT+F4. If the window is closed normally, by pressing the close button, the window size is saved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437521] Become opaque when screen edge with the panel is filled up with windows for reasons other than any of them being maximized
https://bugs.kde.org/show_bug.cgi?id=437521 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451906] Blackscreen with mouse pointer only on wayland when multiple displays are connected
https://bugs.kde.org/show_bug.cgi?id=451906 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442699] Laptop display remains black with only a cursor after resuming from sleep
https://bugs.kde.org/show_bug.cgi?id=442699 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391531] No containment shown on given screen in overlapping setup
https://bugs.kde.org/show_bug.cgi?id=391531 Carlo changed: What|Removed |Added CC||cirlo...@msn.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458622] New: Window order gets briefly switched when changing workspaces, when a window is set to appear on all desktops
https://bugs.kde.org/show_bug.cgi?id=458622 Bug ID: 458622 Summary: Window order gets briefly switched when changing workspaces, when a window is set to appear on all desktops Product: kwin Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- Created attachment 151775 --> https://bugs.kde.org/attachment.cgi?id=151775=edit screen recording of the problem SUMMARY When you have a window open on workspace 1, and another window open on workspace 2, a third window that is set to show up on all desktops will briefly pop up above the other windows, before (spontaneously) finding its correct order a second or so later, every time you change workspaces. This is *extremely* irritating and should be easy to reproduce. The bug is probably somehow related to https://bugs.kde.org/show_bug.cgi?id=455429 but it's not the same issue. I don't have "slide back" enabled. Note: I'm using "workspace" and "desktop" synonymously in what follows. KDE is not consistent in how it describes this concept. STEPS TO REPRODUCE 1. Open a window on workspace 1 and another window on workspace 2. 2. Open a third window and use the window actions to put the window "On All Desktops". 3. Toggle between the workspaces and raise the windows you created in step 1 so that they're above the third window in the order. 4. Toggle between the workspaces. OBSERVED RESULT The third window (created in step 2) that is set to open on all desktops will briefly "flash" above the other windows when you change workspaces, even though it should be at the bottom of the stack on both workspaces. After a brief (~1s) period, it will then drop down below the other windows to its correct order. Windows set to appear on all desktops will briefly flash above even windows that have "keep above" set. Changing the Virtual Desktop Switching Animation to "Fade Desktop" instead of "Slide" does not fix the problem. It's a little harder to detect because the animation is faster, but definitely still happening. EXPECTED RESULT Windows should stay at the correct order when switching workspaces. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.5-arch1-1 (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® HD Graphics 3000 ADDITIONAL INFORMATION I'm about 90% sure I saw someone report this issue on the KDE subreddit around the time 5.25 was released, but I can't seem to find it now. I think this is a regression in 5.25 but I'm not certain about that. At the very least it's a regression over ~6 months ago. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438883] Re-implement Desktop Cube effect with modern effects API
https://bugs.kde.org/show_bug.cgi?id=438883 JC Casiano changed: What|Removed |Added CC||j...@seanet.com --- Comment #47 from JC Casiano --- Please bring back the Cube, the Fade and Slide effects don't even compare. It was odd hearing my friend even mention it and express his disappointment the other day. I was surprised he even noticed my Linux effects, and he thought it was one of the coolest effects that he couldn't get on Windows. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458598] Kwin crashes in KWin::Workspace::clientArea() after waking from sleep with KDE Snap Assist KWin script active
https://bugs.kde.org/show_bug.cgi?id=458598 Max changed: What|Removed |Added CC||maximts...@gmail.com --- Comment #5 from Max --- (In reply to Nate Graham from comment #1) > This is an issue caused by a bug in the 3rd-party Snap Assist KWin script. > Evidently your system is missing the "pygdbmi" python modue, and this causes > it to crash But this script doesn't depend on "pygdbmi" module, or any other external libraries or modules other than the official KWin Scripting API. The fact that the crash happens only after waking from sleep also makes me suspicious. Is it possible that "clientArea()" method from the API somehow requires "pygdbmi" dependency under the hood? As it seems to be the exact place where the crash happens. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458621] New: KWrite should not have a tabbed interface
https://bugs.kde.org/show_bug.cgi?id=458621 Bug ID: 458621 Summary: KWrite should not have a tabbed interface Product: kate Version: 22.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- When I want a tabbed interface, I use Kate. But now KWrite is opening new tabs (when I click "New") instead of new windows. I do not see any way to get the old behaviour back. -- You are receiving this mail because: You are watching all bug changes.
[kmahjongg] [Bug 458566] "Restart Game" opens "Save Game" dialog
https://bugs.kde.org/show_bug.cgi?id=458566 --- Comment #2 from Stuart K. Smith --- (In reply to Albert Astals Cid from comment #1) > I think it makes sense, imagine you're almost done and Press F5 by mistake, > having a dialog that lets you save, not save, cancel, makes sense to me As someone who plays the game almost daily, I find it highly annoying and unnecessary. It's rare to solve a game on the first go so restarting is a common thing to do for 3 or 4 rounds at least. An accidental F5 only means you have to start over with the same tiles - something one does anyway. An intentional F5 now means you have to stop what you are doing and close a dialog. If it was an intentional change, it is not a benefit and has a negative impact on game play. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Pierre Choffet changed: What|Removed |Added CC||ct@peuc.net -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 454683] Holding down volume up/volume down button on a keyboard crashes KDE
https://bugs.kde.org/show_bug.cgi?id=454683 Alan Pope changed: What|Removed |Added CC||a...@popey.com --- Comment #2 from Alan Pope --- Good day! I have experienced this issue on Kubuntu (KDE 5.24.4) multiple times. I filed a bug in launchpad which collected a slew of debug information, which may or may not be helpful. https://bugs.launchpad.net/xorg-server/+bug/1988484 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Pierre Choffet changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Pierre Choffet --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #48 from pipapo --- Here on kde neon option A is working in the sense that a dialog is asking for the passphrase immediately. But the key is not used automatically with the login as before. Option B has no observable effect here. Solution C is working. But to make it work for existing configuration you have to export/import the wallet and set it as standard. Interestingly when applying changes to the wallet service the matrix-client element is complaining that it is unable to decrypt. You have to logout and login again and confirm the session via QR-code. After learning some apt I managed to go back to 5.96.0 and everything is back to normal. Going back with the package manager synaptic will remove nearly all kde stuff because of unresolved dependencies. At the moment kwallet version 5.97.0 does not work as expected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 458620] New: Batch Queue Manager does not offer a "Color Negative Film" tool
https://bugs.kde.org/show_bug.cgi?id=458620 Bug ID: 458620 Summary: Batch Queue Manager does not offer a "Color Negative Film" tool Product: digikam Version: 7.7.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: BatchQueueManager-Plugins Assignee: digikam-bugs-n...@kde.org Reporter: rjwgn...@gmail.com Target Milestone: --- I am converting color film negatives to digital using my DSLR. After copying a number of images, I wish to import them into digiKam, and convert them. After importing into an album, I would like to use BQM to perform the conversion in the album. The tool is available in the image editor, but not BQM. STEPS TO REPRODUCE 1. Photograph film negatives using DSLR 2. Import the images into digiKam 3. Open Batch Queue Manager, and look for "Color Negative Film" in base tools OBSERVED RESULT 1. There is no "Color Negative Film" tool EXPECTED RESULT 1. There should be a "Color Negative Film" tool SOFTWARE/OS VERSIONS Linux/KDE Plasma: Version 5.97.0 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 458458] Add support for thumbnails embedded in gcode files
https://bugs.kde.org/show_bug.cgi?id=458458 gudvinr+...@gmail.com changed: What|Removed |Added CC||gudvinr+...@gmail.com --- Comment #1 from gudvinr+...@gmail.com --- Thumbnails generation supported not only in PS but also in CURA and I believe in S3D too. Also PS can generate QOI thumbnails: https://github.com/prusa3d/PrusaSlicer/commit/87cff55856ae14096cd57f8e2542f1f1caef7167 There is a plugin for OctoPrint that shows thumbnails which can be helpful to see difference between implementations: https://github.com/jneilliii/OctoPrint-PrusaSlicerThumbnails -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458619] Left-side selector changed from vertical text to ugly large icons
https://bugs.kde.org/show_bug.cgi?id=458619 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED CC||waqar@gmail.com Resolution|--- |NOT A BUG --- Comment #1 from Waqar Ahmed --- Check settings-Behavior and choose the style you want. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458516] Spaces in content filenames causes a second copy of the book's content to be shown; TOC points to the second copy.
https://bugs.kde.org/show_bug.cgi?id=458516 --- Comment #2 from Duane --- Created attachment 151774 --> https://bugs.kde.org/attachment.cgi?id=151774=edit an epub file illustrating the bug This html source differs from the previous source in that it only has chapters 1-3. A necessary change so that the epub will fit wtihin the 4k file size submission restraint. It still illustrates the repeated content. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458619] New: Left-side selector changed from vertical text to ugly large icons
https://bugs.kde.org/show_bug.cgi?id=458619 Bug ID: 458619 Summary: Left-side selector changed from vertical text to ugly large icons Product: kate Version: 22.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- The left side of Kate has always had a list of open documents, which works well. At some point, a selector was added to choose between Documents, Projects, or other plugins. That was fine. But with 22.08, it's become rather large (40x40?) icons instead, which don't indicate what they are (unless you open the tooltip) and waste a lot of screen space. There appears to be no way to turn it off or make it smaller. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 458616] In report configuration, any Date range outside of "User configuration" should disable the From/To date input
https://bugs.kde.org/show_bug.cgi?id=458616 --- Comment #1 from Jack --- Not necessarily. If the user selects a preset range from the list, and then adjusts one or both dates, the selection should just automatically change to "User configuration." Sometimes that can be easier that entering both dates from scratch - such as if you only have to adjust one or two of the six date entry fields. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 458618] New: Followup reminder agent crashed
https://bugs.kde.org/show_bug.cgi?id=458618
Bug ID: 458618
Summary: Followup reminder agent crashed
Product: kmail2
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: nicolas.fe...@gmx.de
Target Milestone: ---
When trying to add a followup reminder for an email from the context menu the
agent crashed
Application: akonadi_followupreminder_agent (akonadi_followupreminder_agent),
signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#5 std::__atomic_base::load(std::memory_order) const
(__m=std::memory_order_relaxed, this=0x6c006c006f0046) at
/usr/include/c++/12/bits/atomic_base.h:486
#6 QAtomicOps::loadRelaxed(std::atomic const&) (_q_value=) at
/home/nico/kde/usr/include/QtCore/qatomic_cxx11.h:239
#7 QBasicAtomicInteger::loadRelaxed() const (this=0x6c006c006f0046) at
/home/nico/kde/usr/include/QtCore/qbasicatomic.h:107
#8 QtPrivate::RefCount::ref() (this=0x6c006c006f0046) at
/home/nico/kde/usr/include/QtCore/qrefcount.h:55
#9 QString::QString(QString const&) (other=...,
this=this@entry=0x7fff3698bf80) at
/home/nico/kde/usr/include/QtCore/qstring.h:1094
#10 FollowUpReminder::FollowUpReminderInfo::messageId() const
(this=this@entry=0xeb64e0) at
/home/nico/kde/src/kmail/agents/followupreminderagent/followupreminderinfo.cpp:130
#11 0x0040fb05 in
FollowUpReminderManager::slotCheckFollowUpFinished(QString const&, long long)
(this=0xe13ce0, messageId=..., id=107789) at
/home/nico/kde/src/kmail/agents/followupreminderagent/followupremindermanager.cpp:123
#12 0x7f807dbe1222 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff3698c0a0, r=0xe13ce0, this=0xe17a40) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate(QObject*, int, void**) (sender=0x7f802000a4b0,
signal_index=3, argv=0x7fff3698c0a0) at kernel/qobject.cpp:3886
#14 0x7f807dbdab9f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x7f802000a4b0, m=m@entry=0x426840
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff3698c0a0)
at kernel/qobject.cpp:3946
#15 0x0041b9a4 in FollowUpReminderJob::finished(QString const&, long
long) (this=this@entry=0x7f802000a4b0, _t1=..., _t2=) at
/home/nico/kde/build/kmail/agents/followupreminderagent/followupreminderagent_autogen/AJN4HOEG3V/moc_followupreminderjob.cpp:135
#16 0x0041689e in FollowUpReminderJob::slotItemFetchJobDone(KJob*)
(this=0x7f802000a4b0, job=) at
/home/nico/kde/src/kmail/agents/followupreminderagent/jobs/followupreminderjob.cpp:70
#17 0x7f807dbe1222 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff3698c210, r=0x7f802000a4b0, this=0x7f801c03b560) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#18 doActivate(QObject*, int, void**) (sender=0xf8bee0, signal_index=6,
argv=0x7fff3698c210) at kernel/qobject.cpp:3886
#19 0x7f807dbdab9f in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0xf8bee0, m=m@entry=0x7f807f23c640
, local_signal_index=local_signal_index@entry=3,
argv=argv@entry=0x7fff3698c210) at kernel/qobject.cpp:3946
#20 0x7f807f1e2cb5 in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0xf8bee0, _t1=, _t1@entry=0xf8bee0, _t2=...) at
/home/nico/kde/build/kcoreaddons/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#21 0x7f807f1e3eab in KJob::finishJob(bool) (this=0xf8bee0,
emitResult=) at
/home/nico/kde/src/kcoreaddons/src/lib/jobs/kjob.cpp:98
#22 0x7f807dbd63e0 in QObject::event(QEvent*) (this=0xf8bee0,
e=0x7f802002be90) at kernel/qobject.cpp:1314
#23 0x7f807ea5737e in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0xf8bee0, e=0x7f802002be90) at
kernel/qapplication.cpp:3637
#24 0x7f807dbac458 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0xf8bee0, event=0x7f802002be90) at kernel/qcoreapplication.cpp:1064
#25 0x7f807dbaf131 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0xc6f1f0) at
kernel/qcoreapplication.cpp:1821
#26 0x7f807dc00d83 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=0xcb9a80) at kernel/qeventdispatcher_glib.cpp:277
#27 0x7f806fd7efaf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#28 0x7f806fdd42c8 in g_main_context_iterate.constprop () at
/lib64/libglib-2.0.so.0
#29 0x7f806fd7c940 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#30 0x7f807dc004a6 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0xcbe880, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#31 0x7f807dbab03b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff3698c630, flags=..., flags@entry=...) at
[systemsettings] [Bug 458615] Window frame is shown as inactive after input of shortcut
https://bugs.kde.org/show_bug.cgi?id=458615 Nicolas Fella changed: What|Removed |Added Assignee|kdelibs-b...@kde.org|plasma-b...@kde.org Product|frameworks-kglobalaccel |systemsettings Component|general |kcm_keys CC||k...@david-redondo.de, ||nicolas.fe...@gmx.de Version|5.97.0 |5.25.4 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned
https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #24 from Maik Qualmann --- Lightroom will probably only change a metadata type e.g. Xmp.lr.HierarchicalSubject or Xmp.dc.Subject. digiKam writes its own XMP tags list in the metadata and reads them out again by default. However, since Lightroom does not change these, digiKam will not recognize anything that has changed. Go to the advanced digiKam metadata settings, here you can specify which tag metadata digiKam reads first, the list corresponds to the order from top to bottom in which digiKam queries the metadata in the file. You'll probably need to move Xmp.lr.HierarchicalSubject to the top. Maik -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458617] New: Impossible to add signing certificates on windows 11
https://bugs.kde.org/show_bug.cgi?id=458617 Bug ID: 458617 Summary: Impossible to add signing certificates on windows 11 Product: okular Version: 22.08.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: hamza.al...@gmail.com Target Milestone: --- SUMMARY Impossible to add signing certificates on Windows 11 ; Okular version 22.8.0 STEPS TO REPRODUCE 1. Open Settings / configure Backends / PDF Backend Configuration 2. Choose Custom Certificate Database 3. Input file location (ex: %AppData%/Mozilla/Firefox/Profiles/YourProfileDefault OR C:/ProgramData/Microsoft/Crypto/Keys) 4. Click Apply / OK 5. Quit and reopen Okular OBSERVED RESULT 1. No signing certificates have been found 2. Digitally Sign function still requires signing certificates to be added EXPECTED RESULT 1. Signing certificates have been found 2. Digitally Sign function may be used SOFTWARE/OS VERSIONS Windows: 11 ADDITIONAL INFORMATION Feature is expected to function based on previously merged changes (as explained here: https://tsdgeos.blogspot.com/2022/02/okular-signature-support-now-works-on.html) -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408 Darafei Praliaskouski changed: What|Removed |Added CC||m...@komzpa.net Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 458616] New: In report configuration, any Date range outside of "User configuration" should disable the From/To date input
https://bugs.kde.org/show_bug.cgi?id=458616 Bug ID: 458616 Summary: In report configuration, any Date range outside of "User configuration" should disable the From/To date input Product: kmymoney Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: m...@dawidwrobel.com Target Milestone: --- In report configuration, any Date range outside of "User configuration" should disable the From/To date input. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 448675] GTK 4 theme does not inherit color theme like gtk 3 theme
https://bugs.kde.org/show_bug.cgi?id=448675 --- Comment #5 from Trent M --- > Yes, we can do custom CSS but as far as I;m aware, it won't update at runtime > like we currently have; you'll need to restart your GTK apps to see changes. > Someone who's familiar with GTK needs to work on this to make it happen. I may be misinterpreting the intention of your reply here; the vibe I'm getting is that if we can't have hot-reloading, you don't feel that this issue is worth addressing anyways. I'm not inclined to think you actually feel this way. Lack of hot-reloading and needing to restart GTK applications so that they reload gtk.css is a small inconvenience compared to not having the theme follow your colors *at all*, unless you have one of those setups that automatically changes the colors periodically. But that type of setup is already broken by apps that can't use the colorreload module anyways. Anyways, for a fix for this issue to be submitted upstream to kde-gtk-config, what do you think would be better? Writing identical files to the gtk-4.0 directory at the same time as writing to the gtk-3.0 directory, or simply creating a symlink in the gtk-4.0 directory to the relevant files in the gtk-3.0 directory? Should this part of the discussion take place elsewhere? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365756] Cannot enable secondary output using PRIME before running "xrandr --auto"
https://bugs.kde.org/show_bug.cgi?id=365756 Faysal changed: What|Removed |Added CC||jawad.fay...@gmail.com --- Comment #13 from Faysal --- Comment on attachment 100149 --> https://bugs.kde.org/attachment.cgi?id=100149 kscreen-console bug output before xrandr --auto Hello This is my first post here and really don´t know where to write properly, newly I switched from Windows 10 to PcLinuxOs. Installed perfectly but when it comes final configuration, my laptop lenovo R500 stuck at 800x600 resolution, tried my best to find maximum solutions but failed. used cvt, xrandr commands also but it didnt work. Hope I will get some magical solution from world gems. regards Here is details of display card. Identification Vendor: Intel Corporation Description: Mobile 4 Series Chipset Integrated Graphics Controller Media class: VGA compatible controller Connection Bus: PCI PCI domain: 0 Bus PCI #: 0 PCI device #: 2 PCI function #: 0 PCI revision: 0x07 Vendor ID: 0x8086 Device ID: 0x2a42 Sub vendor ID: 0x17aa Sub device ID: 0x20e5 Misc Module: Card:Intel 810 and later -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 458486] Unneeded scrollbar space in systemsettings
https://bugs.kde.org/show_bug.cgi?id=458486 Nate Graham changed: What|Removed |Added Severity|minor |normal -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458571] Some album art is not picked up form mp3 files
https://bugs.kde.org/show_bug.cgi?id=458571 --- Comment #4 from tomash...@gmail.com --- So I guess this has been fixed then in the meantime, so marking as such. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 458615] Window frame is shown as inactive after input of shortcut
https://bugs.kde.org/show_bug.cgi?id=458615 --- Comment #1 from Frank Steinmetzger --- Created attachment 151773 --> https://bugs.kde.org/attachment.cgi?id=151773=edit Screen capture of the issue Oops, forgot to select a file to attach in the OP. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458571] Some album art is not picked up form mp3 files
https://bugs.kde.org/show_bug.cgi?id=458571 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED Version Fixed In||22.08 --- Comment #3 from Nate Graham --- The Flatpak version is 22.08, which supports my idea that that release contains the final fix (other than the .jpeg thing, which will land in 22.08.1). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 458615] New: Window frame is shown as inactive after input of shortcut
https://bugs.kde.org/show_bug.cgi?id=458615 Bug ID: 458615 Summary: Window frame is shown as inactive after input of shortcut Product: frameworks-kglobalaccel Version: 5.97.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: dev-...@felsenfleischer.de Target Milestone: --- SUMMARY Whenever I configure a custom shortcut in KDE, be it in system settings, the menu editor or an application’s own shortcuts, afterwards the window which contains the shortcut settings is drawn as if it were inactive. I need to switch focus away from it and back for the frame to be drawn as active again. It could be a kwin bug, but I suspect something in the shortcut assignment logic creates an invisible window to catch input and then does not return the original window to its original state. STEPS TO REPRODUCE 1. Open any shortcut setting dialog 2. Enter a new custom keyboard shortcut OBSERVED RESULT The window frame colour changes to inactive. EXPECTED RESULT The colour should not change. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 30.8 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: MSI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #47 from Frank Kruger --- (In reply to michaelk83 from comment #46) > (In reply to Frank Kruger from comment #45) > > Appreciated, but your solution seems to be restricted to a fix when setting > > up a GPG wallet. What about current users? > The proposed fix should work the same whether the wallet is new or existed > previously. It does not affect the wallet data in any way. > > The patch I proposed in comment 40 (once translated from pseudo- to actual > code - still TODO) would take effect when unlocking the GPG wallet, so it > should work with existing wallets as well. It's the same fix, just > automated, and only applied while unlocking the wallet (instead of a > permanent configuration change). > Thanks for the clarification. I apprecitate it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458614] New: Multiline text is displayed incorrectly in avatar chooser
https://bugs.kde.org/show_bug.cgi?id=458614 Bug ID: 458614 Summary: Multiline text is displayed incorrectly in avatar chooser Product: systemsettings Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: plasma-b...@kde.org Reporter: emtorr...@gmail.com CC: uhh...@gmail.com Target Milestone: --- Created attachment 151772 --> https://bugs.kde.org/attachment.cgi?id=151772=edit avatar_file_chooser SUMMARY In System Settings -> Users when you want to change the avatar, the text below the file browser button has 2 lines if your language is Spanish for example, and is not displayed correctly. STEPS TO REPRODUCE 1. Enter System Settings -> Users 2. Click in the avatar image OBSERVED RESULT Text below the file browser button is multiline and is not displayed correctly EXPECTED RESULT The text is displayed correctly, inside the button SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20220829 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 458560] Disable the "Subscribe" buttons when they are clicked
https://bugs.kde.org/show_bug.cgi?id=458560 b...@mogwai.be changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458571] Some album art is not picked up form mp3 files
https://bugs.kde.org/show_bug.cgi?id=458571 --- Comment #2 from tomash...@gmail.com --- The album art is embedded in all of them, no discernibale pattern. I downloaded the flatpak version of elisa and all art is displayed,including ogg - is it possible today's flatpak has the fix focer jpeg (instead of jpg)? I tried to remove cover.jpeg from my directory but the album art is still displayed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #46 from michaelk83 --- (In reply to Frank Kruger from comment #45) > Appreciated, but your solution seems to be restricted to a fix when setting > up a GPG wallet. What about current users? The proposed fix should work the same whether the wallet is new or existed previously. It does not affect the wallet data in any way. The patch I proposed in comment 40 (once translated from pseudo- to actual code - still TODO) would take effect when unlocking the GPG wallet, so it should work with existing wallets as well. It's the same fix, just automated, and only applied while unlocking the wallet (instead of a permanent configuration change). Btw, Secret Service integration did not exist at all in KWallet prior to 5.97.0. So there are three types of KWallet users: - Those using a blowfish wallet. They are not affected by this bug. - Those who were using a GPG wallet with a 3rd-party Secret Service provider. In their case, GPG was likely taking the key passphrase from the 3rd party Secret Service provider. These need the patch from Bug 458069, and to disable the new integration in KWallet, so that the 3rd party provider can function as before. - Those who were using a GPG wallet *without* a Secret Service provider (likely the majority). In their case, GPG was *not* taking the key passphrase from Secret Service, since Secret Service was not available. Adjusting `gpg-agent.conf` as suggested above (comment 36 Option A) restores the previous GPG behavior for those users. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436318] Save session doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=436318 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424485] GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
https://bugs.kde.org/show_bug.cgi?id=424485 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358277] Chrome apps assuming same icon from chrome browser, in Icon-Only Task Manager
https://bugs.kde.org/show_bug.cgi?id=358277 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458574] Denied access to save an opened file on Windows
https://bugs.kde.org/show_bug.cgi?id=458574 dasneve...@outlook.com changed: What|Removed |Added CC||dasneve...@outlook.com --- Comment #1 from dasneve...@outlook.com --- I am experiencing the same error. Reproduced it with multiple files, saved in different locations. SOFTWARE/OS VERSIONS Windows: 11 KDE Plasma Version: - KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #45 from Frank Kruger --- (In reply to michaelk83 from comment #44) > (In reply to Frank Kruger from comment #43) > > Recommendation A works fine for me - thanks for the "solution". However, I > > am really puzzled by the fact that the regression definitely introduced by > > the upgrade to KDE's KWallet 5.97.0 for those of us who are using GPG wallet > > together with Secret Service API support in KWallet is simply called > > "resolved upstream". So, who is going to inform all the users hit by this > > bug and using different distros to change their ~/.gnupg/gpg-agent.conf > > accordingly? Sorry, but the bug is not solved at all! > > Right, marking it "resolved" was my mistake. That's why I reopened it. Appreciated, but your solution seems to be restricted to a fix when setting up a GPG wallet. What about current users? -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 458243] Toolbar missing icons when using Adwaita icon theme
https://bugs.kde.org/show_bug.cgi?id=458243 --- Comment #12 from Kai Uwe Broulik --- > or embed the tools icons in the app in case your active icon theme doesn't > have them. Kolourpaint install its own custom icons into /usr/share/kolourpaint/icons. I don't know why it's not using them as a fallback. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 458613] New: CSS is displayed incorrectly
https://bugs.kde.org/show_bug.cgi?id=458613 Bug ID: 458613 Summary: CSS is displayed incorrectly Product: Falkon Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: kaesbertrich...@gmail.com Target Milestone: --- SUMMARY The CSS rules are not displayed correctly in some places. Mostly forms or upvote widgets are affected. STEPS TO REPRODUCE 1. Go to Website https://auf1.tv/nachrichten-auf1/nachrichten-auf1-vom-1-september-2022 and take a look at the upvote system below the videoplayer 2. Unfortunately, I only became aware of the problem after a while and I only have this one page as an example page but the issue appears also in many other pages. Mostly in an upvote widget or in forms I noticed the issue. OBSERVED RESULT The upvote system is displayed differently than expected or is displayed differently than in FF or Chrome. EXPECTED RESULT The upvote widget should be displayed in color and properly formatted or positioned. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Debian GNU/Linux 11 (bullseye)/Wayland/Gnome (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: QtWebEngine-Version 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 448646] Discover reports "Bad GPG signature found" where "dnf update" succeeds
https://bugs.kde.org/show_bug.cgi?id=448646 --- Comment #6 from Dennis Schridde --- Also affects the tailscale-stable repo: https://pkgs.tailscale.com/stable/#fedora ``` Bad GPG signature found: /var/cache/PackageKit/36/metadata/tailscale-stable-36-x86_64/packages/tailscale_1.30.0_x86_64.rpm could not be verified. /var/cache/PackageKit/36/metadata/tailscale-stable-36-x86_64/packages/tailscale_1.30.0_x86_64.rpm: digest: SIGNATURE: NOT OK ``` Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-11370H @ 3.30GHz Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: TUXEDO Product Name: TUXEDO InfinityBook Pro 14 Gen6 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #44 from michaelk83 --- (In reply to Frank Kruger from comment #43) > Recommendation A works fine for me - thanks for the "solution". However, I > am really puzzled by the fact that the regression definitely introduced by > the upgrade to KDE's KWallet 5.97.0 for those of us who are using GPG wallet > together with Secret Service API support in KWallet is simply called > "resolved upstream". So, who is going to inform all the users hit by this > bug and using different distros to change their ~/.gnupg/gpg-agent.conf > accordingly? Sorry, but the bug is not solved at all! Right, marking it "resolved" was my mistake. That's why I reopened it. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 458612] Subsequent right-click doesn't pull up a menu after choosing any item from the list
https://bugs.kde.org/show_bug.cgi?id=458612 Dawid Wróbel changed: What|Removed |Added OS|Other |macOS Platform|Other |macOS (DMG) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 458612] New: Subsequent right-click doesn't pull up a menu after choosing any item from the list
https://bugs.kde.org/show_bug.cgi?id=458612 Bug ID: 458612 Summary: Subsequent right-click doesn't pull up a menu after choosing any item from the list Product: kmymoney Version: git (master) Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: ux-ui Assignee: kmymoney-de...@kde.org Reporter: m...@dawidwrobel.com Target Milestone: --- SUMMARY I duplicated a transaction and subsequently it was impossible to pull up right-click menu on any transaction. Moreover, it seems that the menu is somehow shown, but not visible, based on the subsequent behavior of the ledger itself. Might be macOS-specific. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 458243] Toolbar missing icons when using Adwaita icon theme
https://bugs.kde.org/show_bug.cgi?id=458243 --- Comment #11 from gorgoglionemeis...@gmail.com --- (In reply to Nate Graham from comment #10) > If you're using GNOME, I guess using GNOME Tweaks somewhere. > > Perhaps we should hardcode the breeze icon theme in Kolourpaint to work > around this, or embed the tools icons in the app in case your active icon > theme doesn't have them. OK. Thank you very much for your support. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 445836] Falkon AdBlock doesn't work for YouTube video ads
https://bugs.kde.org/show_bug.cgi?id=445836 kaesbertrich...@gmail.com changed: What|Removed |Added CC||kaesbertrich...@gmail.com --- Comment #1 from kaesbertrich...@gmail.com --- Hm, the problem has been around for 10 months and still hasn't been solved? Why not just use uBlock Origin instead of Adblock? Or is there already a solution to the problem and I can not find it? Like an Adblock rule to add manually maybe? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447774] File system expose cannot expose certain folders on Android 11
https://bugs.kde.org/show_bug.cgi?id=447774 --- Comment #6 from Sayan Chakroborty --- Some other FOSS apps on F-Droid have the permission MANAGE_EXTERNAL_STORAGE (see https://developer.android.com/training/data-storage/manage-all-files). For example, Nextcloud [https://f-droid.org/en/packages/com.nextcloud.client/] and VLC [https://f-droid.org/en/packages/org.videolan.vlc/] ask for the permission "Allow management of all files" as it should be the case for KDE Connect as well. A major feature is broken just for one limited permission, this should be easy to fix. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #43 from Frank Kruger --- (In reply to michaelk83 from comment #36) > Reopening because the fix should ideally be automated by KWallet when > setting up a GPG wallet, or at least properly documented. > To summarize: > > This affects GPG wallets with Secret Service enabled. By default, GPG tries > to retrieve the key passphrase from Secret Service. If Secret Service is > provided by KWallet, this creates a dependency cycle, which prevents the > wallet from unlocking. There are three ways to break the cycle: > > - Option A (recommended): To prevent GPG from trying to retrieve the > passphrase from Secret Service, add the `no-allow-external-cache` option to > `~/.gnupg/gpg-agent.conf`. You can either edit the file manually, or run: > `echo no-allow-external-cache:0:1 | gpgconf --change-options gpg-agent`. GPG > will prompt the user directly when the key passphrase is needed for the > first time. > - Option B: Disable the Secret Service API support in KWallet settings. You > may use a different Secret Service provider if desired. > - Option C: Do not use a GPG wallet (downgrade to a traditional blowfish > wallet). Recommendation A works fine for me - thanks for the "solution". However, I am really puzzled by the fact that the regression definitely introduced by the upgrade to KDE's KWallet 5.97.0 for those of us who are using GPG wallet together with Secret Service API support in KWallet is simply called "resolved upstream". So, who is going to inform all the users hit by this bug and using different distros to change their ~/.gnupg/gpg-agent.conf accordingly? Sorry, but the bug is not solved at all! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458611] New: Can't interact anymore with a VLC window after dropping a video file
https://bugs.kde.org/show_bug.cgi?id=458611 Bug ID: 458611 Summary: Can't interact anymore with a VLC window after dropping a video file Product: kwin Version: 5.24.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: i6ic...@mailezee.com Target Milestone: --- SUMMARY Trying to open a video file (I tried with multiple .mkv that I know vlc can open because thy work when I open them on vlc by double click) by drag and dropping on a vlc window from dolphin results with the impossibility to interact with vlc anymore (from it's gui or trying to closing it from the title bar). Note that the dropped video doesn't get opened by vlc, but, if you already have opened a video in background, that video continues to play just fine, meaning that vlc hasn't crashed. STEPS TO REPRODUCE 1. Open vlc 2. Drag and drop a video into the vlc window OBSERVED RESULT Can't interact anymore with the vlc window EXPECTED RESULT Vlc opens the video as expected. SOFTWARE/OS VERSIONS Linux: 5.19.1-3-Manjaro KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Graphic Platform: Wayland VLC: 3.0.17.4 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447774] File system expose cannot expose certain folders on Android 11
https://bugs.kde.org/show_bug.cgi?id=447774 Sayan Chakroborty changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||sayan@e.email --- Comment #5 from Sayan Chakroborty --- (In reply to Henrique Soares from comment #3) > Also having this problem. Not my field of expertise, but it seems to be a > permission problem. I've seen some of my mobile games with the option > available to select "Allow Management of All Files", on KDE Connect there is > only "Allow Access to Media Only". -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 446358] Kasts should display chapters for podcasts with them
https://bugs.kde.org/show_bug.cgi?id=446358 --- Comment #3 from b...@mogwai.be --- (In reply to Tiago from comment #2) > The status of this ticket is RESOLVED FIXED. However, I'm using version > 22.06 on Linux and I can't find episode chapters anywhere. Re-opening. Could you please elaborate? Do you have a certain episode of a certain podcast that you know should have chapters but which don't show in Kasts? We've implemented several chapter mark standards so far, but it could be that we're missing one. But we can't add it without examples. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458610] New: Screen froze after moving mouse when the screen was locking automatically, on Wayland
https://bugs.kde.org/show_bug.cgi?id=458610 Bug ID: 458610 Summary: Screen froze after moving mouse when the screen was locking automatically, on Wayland Product: kwin Version: 5.24.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: i6ic...@mailezee.com Target Milestone: --- SUMMARY Note: it happened only once to me, I'll try to reproduce it again. While using the plasma wayland session, in the exact moment when the screen locked automatically after the timeout ended I moved the mouse to avoid that the screen actually locked. The whole screen instead actually froze, letting me only move the mouse cursor, but I couldn't interact with the open window (or the plasma panel) anymore. I ended up restarting the pc from another tty. STEPS TO REPRODUCE 1. Wait for the timeout of the automatic screen lock 2. In the moment when the screen start to lock move the mouse OBSERVED RESULT The screen, except the mouse cursor, froze. EXPECTED RESULT The locking procedure stops and it is still possible to interact with the opened windows and plasma SOFTWARE/OS VERSIONS Linux: 5.19.1-3-Manjaro KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Graphic Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 458213] Cannot launch certain applications with global shortcut
https://bugs.kde.org/show_bug.cgi?id=458213 --- Comment #8 from Nate Graham --- Only certain types triggered it, weirdly. But let's see if that's the fix. If not, we can re-open the bug. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 394945] Sometimes screen brightness gets raised at critical battery level if current brightness is lower than "low battery" profile's brightness
https://bugs.kde.org/show_bug.cgi?id=394945 Nate Graham changed: What|Removed |Added Version Fixed In|5.25|5.24.7 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 394945] Sometimes screen brightness gets raised at critical battery level if current brightness is lower than "low battery" profile's brightness
https://bugs.kde.org/show_bug.cgi?id=394945 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/powerdevil/commit/0f548c |ma/powerdevil/commit/35fb7f |53dd177235eaf5ce8452c9b4483 |501e6e0057d6fef8a0f9da425d5 |9c12e21 |8dfd27a --- Comment #12 from Nate Graham --- Git commit 35fb7f501e6e0057d6fef8a0f9da425d58dfd27a by Nate Graham, on behalf of Louis Moureaux. Committed on 01/09/2022 at 18:57. Pushed by ngraham into branch 'Plasma/5.24'. Fix profile switching in the brightness actions The current code assumes that the action is notified of every profile change, which is only the case when the action is configured to run in all profiles. The code that prevents brightness from being raised when switching to a more conservative profile gets confused if the action didn't run in the "previous" profile. Make it more robust by always querying the core for the previous profile, which it luckily hasn't updated yet when the action gets executed. FIXED-IN: 5.25 (cherry picked from commit 6220db1b8a5038ed5e1359b1afdf70c0625f0895) M +8-7daemon/actions/bundled/brightnesscontrol.cpp M +0-1daemon/actions/bundled/brightnesscontrol.h M +9-7daemon/actions/bundled/keyboardbrightnesscontrol.cpp M +0-1daemon/actions/bundled/keyboardbrightnesscontrol.h https://invent.kde.org/plasma/powerdevil/commit/35fb7f501e6e0057d6fef8a0f9da425d58dfd27a -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 394945] Sometimes screen brightness gets raised at critical battery level if current brightness is lower than "low battery" profile's brightness
https://bugs.kde.org/show_bug.cgi?id=394945 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/powerdevil/commit/6220db |ma/powerdevil/commit/0f548c |1b8a5038ed5e1359b1afdf70c06 |53dd177235eaf5ce8452c9b4483 |25f0895 |9c12e21 --- Comment #11 from Nate Graham --- Git commit 0f548c53dd177235eaf5ce8452c9b44839c12e21 by Nate Graham, on behalf of Louis Moureaux. Committed on 01/09/2022 at 18:55. Pushed by ngraham into branch 'Plasma/5.25'. Fix profile switching in the brightness actions The current code assumes that the action is notified of every profile change, which is only the case when the action is configured to run in all profiles. The code that prevents brightness from being raised when switching to a more conservative profile gets confused if the action didn't run in the "previous" profile. Make it more robust by always querying the core for the previous profile, which it luckily hasn't updated yet when the action gets executed. FIXED-IN: 5.25 (cherry picked from commit 6220db1b8a5038ed5e1359b1afdf70c0625f0895) M +8-7daemon/actions/bundled/brightnesscontrol.cpp M +0-1daemon/actions/bundled/brightnesscontrol.h M +9-7daemon/actions/bundled/keyboardbrightnesscontrol.cpp M +0-1daemon/actions/bundled/keyboardbrightnesscontrol.h https://invent.kde.org/plasma/powerdevil/commit/0f548c53dd177235eaf5ce8452c9b44839c12e21 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 458213] Cannot launch certain applications with global shortcut
https://bugs.kde.org/show_bug.cgi?id=458213 --- Comment #7 from Frank Steinmetzger --- (In reply to Nate Graham from comment #6) > Ah this is Bug 440507 which is already fixed in 5.98. I hope you’re right. I was aware of that bug, but since gwenview’s Exec line also contained arguments, I thought I was experiencing a different problem. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 394945] Sometimes screen brightness gets raised at critical battery level if current brightness is lower than "low battery" profile's brightness
https://bugs.kde.org/show_bug.cgi?id=394945 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.25 Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/commit/6220db ||1b8a5038ed5e1359b1afdf70c06 ||25f0895 --- Comment #10 from David Edmundson --- Git commit 6220db1b8a5038ed5e1359b1afdf70c0625f0895 by David Edmundson, on behalf of Louis Moureaux. Committed on 01/09/2022 at 18:52. Pushed by ngraham into branch 'master'. Fix profile switching in the brightness actions The current code assumes that the action is notified of every profile change, which is only the case when the action is configured to run in all profiles. The code that prevents brightness from being raised when switching to a more conservative profile gets confused if the action didn't run in the "previous" profile. Make it more robust by always querying the core for the previous profile, which it luckily hasn't updated yet when the action gets executed. FIXED-IN: 5.25 M +8-7daemon/actions/bundled/brightnesscontrol.cpp M +0-1daemon/actions/bundled/brightnesscontrol.h M +9-7daemon/actions/bundled/keyboardbrightnesscontrol.cpp M +0-1daemon/actions/bundled/keyboardbrightnesscontrol.h https://invent.kde.org/plasma/powerdevil/commit/6220db1b8a5038ed5e1359b1afdf70c0625f0895 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 458361] Sharpness brushes are functionally inaccurate when "Align the brush preview outline to the pixel grid" is disabled
https://bugs.kde.org/show_bug.cgi?id=458361 tomtomtomreportin...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Summary|"Align the brush preview|Sharpness brushes are |outline to the pixel grid" |functionally inaccurate |when disabled changes |when "Align the brush |functional behavior of |preview outline to the |brush |pixel grid" is disabled Status|REPORTED|CONFIRMED --- Comment #2 from tomtomtomreportin...@gmail.com --- In the wild: https://old.reddit.com/r/krita/comments/x2excx/pixel_brush_is_not_accurate_after_510_pixel_art/ https://old.reddit.com/r/krita/comments/wyobfn/just_updated_versions_and_the_brush_tip_size_2_is/ Setting to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447854] CONSISTENT RENDER CRASH - 100% of the time - right at the end of rendering
https://bugs.kde.org/show_bug.cgi?id=447854 --- Comment #38 from candideu --- (In reply to Andrey from comment #36) > (In reply to candideu from comment #35) > > Hi, I'm still having this issue. See: > > https://bugs.kde.org/show_bug.cgi?id=458252 > > Please provide more info, the output log alone is not enough. The best thing > would be a specially created small project which definitely provokes the > crash and which you can share publicly in full. Attachment has been added -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447854] CONSISTENT RENDER CRASH - 100% of the time - right at the end of rendering
https://bugs.kde.org/show_bug.cgi?id=447854 --- Comment #37 from candideu --- Created attachment 151771 --> https://bugs.kde.org/attachment.cgi?id=151771=edit example project -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 458609] New: Solid crashes (asserts) on when first connecting Apple's Magic Mouse
https://bugs.kde.org/show_bug.cgi?id=458609 Bug ID: 458609 Summary: Solid crashes (asserts) on when first connecting Apple's Magic Mouse Product: frameworks-solid Version: 5.97.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: isma...@gmail.com CC: kdelibs-b...@kde.org, lu...@kde.org Target Milestone: --- Created attachment 151770 --> https://bugs.kde.org/attachment.cgi?id=151770=edit Backtrace SUMMARY When first connecting an Apple's Magic Mouse via bluetooth, plasmashell process crashes (asserts when compiled on debug mode) Backtrace leads to Solid triggering an ASSERT on Solid::DeviceManagerPrivate::_k_deviceRemoved: (src/solid/devices/frontend/devicemanager.cpp:234) Q_ASSERT(dev->backendObject() != nullptr); Note that the magic mouse driver probably provokes some unexpected operations on UPower that triggers the assertion, where it first adds and removes a "dummy" battery device with no path, before adding the definitive one. This only happens the first time that the mouse is connected. STEPS TO REPRODUCE 1. Run a plasma session compiled on debug mode (ideally from power-on) 2. Connect a Apple's Magic Mouse OBSERVED RESULT Plasmashell process crashes SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.80 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION This is the output of: > upower --monitor-detail > /org/freedesktop/UPower/devices/mouse_hid_0coe4o41o0aobbo8b_battery upower --monitor-detail /org/freedesktop/UPower/devices/mouse_hid_0coe4o41o0aobbo8b_battery Monitoring activity from the power daemon. Press Ctrl+C to cancel. [22:47:57.526] device added: /org/freedesktop/UPower/devices/mouse_hid_0coe4o41o0aobbo8b_battery native-path: (null) power supply: no updated: jue 01 ene 1970 01:00:00 (1657831677 seconds ago) has history: no has statistics: no unknown warning-level: unknown battery-level: unknown percentage: 0% (should be ignored) icon-name: '(null)' [22:47:57.526] device removed: /org/freedesktop/UPower/devices/mouse_hid_0coe4o41o0aobbo8b_battery [22:47:57.564] device added: /org/freedesktop/UPower/devices/mouse_hid_0coe4o41o0aobbo8b_battery native-path: hid-0c:e4:41:0a:bb:8b-battery model:Magic Mouse 2 power supply: no updated: jue 14 jul 2022 22:47:57 (0 seconds ago) has history: yes has statistics: yes mouse present: yes rechargeable:yes state: discharging warning-level: none percentage: 50% icon-name: 'battery-good-symbolic' History (charge): 1657831677 50,000 discharging 1657831677 0,000 unknown 1657831677 50,000 discharging 1657831677 0,000 unknown History (rate): 1657831677 0,000 unknown 1657831677 0,000 unknown -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 380876] Tags in Digikam DB maintained after being removed from file and file re-scanned
https://bugs.kde.org/show_bug.cgi?id=380876 --- Comment #23 from RS --- Thanks a lot for your explanation, Maik – what you describe is essentially what I had expected. Unfortunately reality doesn’t exactly match my expectations: I have checked 'Clean up the metadata from the database when rescan files' in Settings > Metadata > Behaviour. My test image is a DNG that I want ot keep in sync with Adobe Lightroom (I actually plan to get rid of the latter in the near future). The original Lightroom DNG had the (hierarchic) keywords 'food', 'vergetables' and 'potatoes' saved inside the DNG (afaik as an XMP). When I scan the image in Digikam, everything is great, including the hierarchic structure. Changing and saving the keywords in Digikam and rescan the image in Lightroom is working flawless as well, but not the other way. If I’m changing the keywords in Lightroom, let’s say to 'agriculture' and nothing else, save the metadata and do the Album > Reread metadata from files command in Digikam, all metadata will be updated, except the keywords, 'food', 'vergetables' and 'potatoes' – they remain as if they’re carved in stone, obviously no chance to get rid of them. And I don’t mean the overall tag list – where they are welcome – but in the assigned file’s metadata. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #42 from michaelk83 --- (In reply to ioo+kde from comment #41) > Will this solution allow users to again use a third party secret service > agent along with kwallet again? You don't need this patch to run a 3rd-party Secret Service provider. This only applies to when Secret Service is provided by KWallet, and only if combined with a GPG wallet. To run a 3rd-party Secret Service provider, you need the patch from Bug 458069, and then disable the KWallet Secret Service integration in the KWallet settings. Alternatively, downgrade KWallet to a version earlier than 5.97.0. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 458608] New: Defaults button does not reset all settings
https://bugs.kde.org/show_bug.cgi?id=458608 Bug ID: 458608 Summary: Defaults button does not reset all settings Product: systemsettings Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_tablet Assignee: plasma-b...@kde.org Reporter: nicolas.fe...@gmx.de CC: aleix...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. Change some setting, e.g. the tablet area to a custom size 2. Click 'Defaults' OBSERVED RESULT Area setting stays the same EXPECTED RESULT Area setting is reset to 'Fit to output' SOFTWARE/OS VERSIONS KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 5.15.5-kde ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458069] Cannot disable org.freedesktop.secrets
https://bugs.kde.org/show_bug.cgi?id=458069 --- Comment #10 from michaelk83 --- (In reply to ioo+kde from comment #9) > Does this patch apply to all distributions or just archlinux? Should apply to all, but it hasn't been released yet except on Arch. It should be in the next KWallet Frameworks version, due in Sep. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452294] Option for notifications to always appear on active screen
https://bugs.kde.org/show_bug.cgi?id=452294 andresdor...@gmail.com changed: What|Removed |Added CC||andresdor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458328] when changing windows with Alt + Tab and arrows yellow square appears in right bottom corner above clock
https://bugs.kde.org/show_bug.cgi?id=458328 empyreal changed: What|Removed |Added Resolution|NOT A BUG |FIXED --- Comment #5 from empyreal --- I can't move it. I removed it in edit mode. I do not use notes, sticky notes, whatever... I didn't add any widgets. This thing appeared after upgrade. That's strange. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 --- Comment #40 from flan_suse --- Ohhh, just discovered something interesting while testing your method, @DarkVessel. What happens if you NAVIGATE to the folder *while* the copy operation is in progress? While the folder copy operation is running, and the system is fine, I can re-create the "freeze" by entering the folder before it finishes. It is not until the copy operation is finished will I regain control of the desktop. So this might have something to do with Dolphin/KDE/KIO/Plasma/whatever updating/refreshing the view of the current folder that is the destination of a large copy operation? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457633] plasma-workspace test suite resets desktop layout to default settings
https://bugs.kde.org/show_bug.cgi?id=457633 Ismael Asensio changed: What|Removed |Added CC||isma...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358231] desktop locks up when moving lots of files
https://bugs.kde.org/show_bug.cgi?id=358231 flan_suse changed: What|Removed |Added CC||windows2li...@zoho.com --- Comment #39 from flan_suse --- (In reply to DarkVessel from comment #37) > I have exactly the same problem. When copying a file, the shell freezes (but > not Dolphin), but if you copy an entire folder, plasma does not hang. LOL! Same issue here too. At first I thought it had to do with the file being *large*, yet if it involves a *FOLDER* (whether containing a single or multiple large files, doesn't matter) then it smoothly glides through the entire copy operation! I thought I was going crazy until I came across this bug report. The trick of copying a FOLDER (instead of a large FILE) magically works. Not sure why... . . . Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-3-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457633] plasma-workspace test suite resets desktop layout to default settings
https://bugs.kde.org/show_bug.cgi?id=457633 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458598] Kwin crashes in KWin::Workspace::clientArea() after waking from sleep with KDE Snap Assist KWin script active
https://bugs.kde.org/show_bug.cgi?id=458598
--- Comment #4 from aron...@gmail.com ---
(In reply to Nate Graham from comment #1)
> > Failed to do pygdbmi parsing: No module named 'pygdbmi'
> > frame={level="0",func="onWindowResize",file="/home/aronkvh/.local/share/kwin/scripts/kdesnapassist/contents/ui/code/windows.js",fullname="/home/aronkvh/.local/share/kwin/scripts/kdesnapassist/c".
>
> This is an issue caused by a bug in the 3rd-party Snap Assist KWin script.
> Evidently your system is missing the "pygdbmi" python modue, and this causes
> it to crash. You should be able to fix this by installing that module, and
> you should also report tihs to the developer because the script shouldn't
> cause KWin to crash if it's missing that module.
Thanks for the explanation, reported it.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwallet] [Bug 458069] Cannot disable org.freedesktop.secrets
https://bugs.kde.org/show_bug.cgi?id=458069 --- Comment #9 from ioo+...@posteo.net --- (In reply to Bug Janitor Service from comment #2) > A possibly relevant merge request was started @ > https://invent.kde.org/frameworks/kwallet/-/merge_requests/33 Does this patch apply to all distributions or just archlinux? I see the status was changed to resolved fixed. If it only applies to arch should I open a separate bug issue for the other distributions? I know kde neon is also affected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 458549] Random whole screen flashes/flicker on the desktop on Wayland when using AMS
https://bugs.kde.org/show_bug.cgi?id=458549 --- Comment #5 from Zamundaaa --- There's a few things you can do to narrow the source of this problem down. Unset KWIN_DRM_NO_AMS and 1. set QT_LOGGING_RULES="kwin_wayland_*.debug=true" instead, reproduce the problem and upload the output of "journalctl --user-unit=plasma-kwin_wayland" here 2. enable drm debug logging and record the output of dmesg with the problem happening at least once, and upload that here. See https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues for how to do that 3. set KWIN_DRM_USE_MODIFIERS=0 instead, check if the problem still happens 4. set KWIN_DRM_PREFER_COLOR_DEPTH=24 instead, check if the problem still happens -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458085] Wallet system takes about 1 minute to start
https://bugs.kde.org/show_bug.cgi?id=458085 --- Comment #41 from ioo+...@posteo.net --- (In reply to nic.chris...@gmail.com from comment #34) > (In reply to michaelk83 from comment #33) > > @nic.christin, one more thing to try: > > https://man.archlinux.org/man/gpg-agent.1#no-allow-external-cache > > > --no-allow-external-cache > > >Tell Pinentry not to enable features which use an external cache for > > > passphrases. > > So either start gpg-agent with `--no-allow-external-cache` flag, or add > > `no-allow-external-cache` option in `gpg-agent.conf`. > > Yes, that fixes the problem and there are no ill-effects that I can see. > pinentry-qt doesn't query dbus, the password prompt is displayed > immediately, and gpg still caches the passphrase. > > Perfect, thanks! Will this solution allow users to again use a third party secret service agent along with kwallet again? -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 452269] (SIGABRT) xdg-desktop-portal-kde crashes on logout on Wayland, resulting in a black screen
https://bugs.kde.org/show_bug.cgi?id=452269 --- Comment #6 from kinghat --- Created attachment 151769 --> https://bugs.kde.org/attachment.cgi?id=151769=edit journalctl output -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 452269] (SIGABRT) xdg-desktop-portal-kde crashes on logout on Wayland, resulting in a black screen
https://bugs.kde.org/show_bug.cgi?id=452269 kinghat changed: What|Removed |Added CC||madl...@gmail.com --- Comment #5 from kinghat --- i am on fedora as well and have tried many fresh installs and its reproducible 100% of the time. adding journalctl output. system info: Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.4-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Manufacturer: LENOVO Product Name: 20BX001FUS System Version: ThinkPad T450s -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 458607] New: Elisa crashes on launch with existing playlist and shuffle enabled
https://bugs.kde.org/show_bug.cgi?id=458607 Bug ID: 458607 Summary: Elisa crashes on launch with existing playlist and shuffle enabled Product: Elisa Version: 22.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: krazyk...@hotmail.com Target Milestone: --- Application: elisa (22.08.0) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.4-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: When Elisa is launched with an existing playlist, and shuffle is enabled it has a chance to crash. This is not 100% reproducible, but after opening and closing the application 5-10 times this can be observed. The window will open without the sidebar visible and then immediately close This happens more frequently with larger playlists (tested with 59 tracks) but has been observed with as low as 6 tracks. This does not seem related to a specific track. Hiding the sidebar does not resolve the issue. Disabling shuffle solved the issue entirely. I cannot reproduce in Wayland. The crash can be reproduced sometimes. -- Backtrace: Application: Elisa (elisa), signal: Segmentation fault [KCrash Handler] #4 0x7f528061b9d7 in KFileMetaData::ExtractorCollectionPrivate::getExtractors(QString const&) () from /lib64/libKF5FileMetaData.so.3 #5 0x7f528061be5c in KFileMetaData::ExtractorCollection::fetchExtractors(QString const&) const () from /lib64/libKF5FileMetaData.so.3 #6 0x7f52781b9caa in FileScanner::scanOneFile (this=this@entry=0x5644c54011c0, scanFile=..., scanFileInfo=...) at /usr/include/c++/12/bits/unique_ptr.h:191 #7 0x7f52781ba344 in FileScanner::scanOneFile (this=0x5644c54011c0, scanFile=...) at /usr/src/debug/elisa-player-22.08.0-2.fc36.x86_64/src/filescanner.cpp:164 #8 0x7f52781d73c2 in operator() (__closure=0x5644c7b6d2e8) at /usr/src/debug/elisa-player-22.08.0-2.fc36.x86_64/src/models/trackmetadatamodel.cpp:593 #9 QtConcurrent::StoredFunctorCall0 >::runFunctor (this=0x5644c7b6d2c0) at /usr/include/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:60 #10 QtConcurrent::RunFunctionTask::run (this=0x5644c7b6d2c0) at /usr/include/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #11 0x7f5294eba4f2 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #12 0x7f5294eb7487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #13 0x7f5294a25e2d in start_thread () from /lib64/libc.so.6 #14 0x7f5294aab1b0 in clone3 () from /lib64/libc.so.6 Thread 8 (Thread 0x7f52677fe640 (LWP 25242) "Thread (pooled)"): #1 0x7f5294eb77c5 in QBasicMutex::lockInternal() () from /lib64/libQt5Core.so.5 #2 0x7f52781d73ae in QMutexLocker::QMutexLocker (m=0x5644c54011c8, this=) at /usr/include/qt5/QtCore/qmutex.h:238 #3 operator() (__closure=0x5644c54f2e58) at /usr/src/debug/elisa-player-22.08.0-2.fc36.x86_64/src/models/trackmetadatamodel.cpp:592 #4 QtConcurrent::StoredFunctorCall0 >::runFunctor (this=0x5644c54f2e30) at /usr/include/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:60 #5 QtConcurrent::RunFunctionTask::run (this=0x5644c54f2e30) at /usr/include/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #6 0x7f5294eba4f2 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #7 0x7f5294eb7487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f5294a25e2d in start_thread () from /lib64/libc.so.6 #9 0x7f5294aab1b0 in clone3 () from /lib64/libc.so.6 Thread 7 (Thread 0x7f5267fff640 (LWP 25241) "Thread (pooled)"): #1 0x7f5294eb77c5 in QBasicMutex::lockInternal() () from /lib64/libQt5Core.so.5 #2 0x7f52781d73ae in QMutexLocker::QMutexLocker (m=0x5644c54011c8, this=) at /usr/include/qt5/QtCore/qmutex.h:238 #3 operator() (__closure=0x5644c5c9ec58) at /usr/src/debug/elisa-player-22.08.0-2.fc36.x86_64/src/models/trackmetadatamodel.cpp:592 #4 QtConcurrent::StoredFunctorCall0 >::runFunctor (this=0x5644c5c9ec30) at /usr/include/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:60 #5 QtConcurrent::RunFunctionTask::run (this=0x5644c5c9ec30) at /usr/include/qt5/QtConcurrent/qtconcurrentrunbase.h:108 #6 0x7f5294eba4f2 in QThreadPoolThread::run() () from /lib64/libQt5Core.so.5 #7 0x7f5294eb7487 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f5294a25e2d in start_thread () from /lib64/libc.so.6 #9 0x7f5294aab1b0 in clone3 () from /lib64/libc.so.6 Thread 6 (Thread 0x7f526c8e6640 (LWP 25240) "Thread (pooled)"): #1 0x7f5294eb77c5 in QBasicMutex::lockInternal() () from /lib64/libQt5Core.so.5 #2 0x7f52781d73ae in QMutexLocker::QMutexLocker (m=0x5644c54011c8, this=) at /usr/include/qt5/QtCore/qmutex.h:238 #3
