[kdenlive] [Bug 454420] New: Crashes When Trying to play video project on Fedora 36
https://bugs.kde.org/show_bug.cgi?id=454420
Bug ID: 454420
Summary: Crashes When Trying to play video project on Fedora 36
Product: kdenlive
Version: 22.04.1
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: Video Display & Export
Assignee: j...@kdenlive.org
Reporter: aaron.lf...@gmail.com
Target Milestone: ---
SUMMARY
I can upload a video clip, and cut the video. However, once I try to play the
any video clip I've edited the application crashes. I can render a video clip
without playing it, but it is moot as I cannot play my video to ensure edits
were done correctly.
Playing any video in Kdenlive would cause it to crash.
***
Backtrace is not working and keeps crashing and unable to compile report.
***
STEPS TO REPRODUCE
1. Open application
2. Once selecting video you want to edit and dragging into the master section,
press play.
3. The video will play for a second or two and then crash
4. Receive error noting: "Oops, it seems kdelinve unexpectedly crashed. Please
contact the developers."
5. Problem reporting reports the following: kdenlive quit unexpectedly
OBSERVED RESULT
Application crashes and closes
EXPECTED RESULT
Application crashes and closes
SOFTWARE/OS VERSIONS
Linux: Fedora 36
OS: Fedora Linux 36 (workstation edition)
Macbook 7.1 1.0
Kernel 5.17.5--300.fc36 x86_64
Gnome 42
Intel Core 2 duo P8600 @ 2.39
NVIDIA GeForce 320 M
Current GPU Drivers: NVAF
ADDITIONAL INFORMATION
Recently upgraded from Fedora 35 to (now currently on) Fedora 36.
I'm using the stable flatpack (and always have)
I was having this issued on Fedora 35: I couldn't do anything in the
application; it would just crash on start.
When upgrading to Fedora 36, I was actually able to get somewhere; I could
upload a video clip and actually cut some of it and render the clip. The
problem of crashing ensued when I would play the clip.
Just playing any video in Kdenlive would cause it to crash.
Back to the issue with Kdenlive:
I cannot "Report a Problem" when Kdenlive crashes, as I keep getting
"Processing failed" on Fedora
the log shows the following:
--- Running report uReport ---
Error: No segments dound in coredump './coredump'
('report_ureport' exitd with 1)
--
You are receiving this mail because:
You are watching all bug changes.
[kid3] [Bug 451787] Edit chapters in MP4/AAC files
https://bugs.kde.org/show_bug.cgi?id=451787 --- Comment #14 from Lee --- (In reply to Urs Fleisch from comment #13) > You can find kid3-git20220523 in > https://sourceforge.net/projects/kid3/files/kid3/development/, where I have > implemented support for chapters in MP4 files. First make sure that you have > activated the Mp4v2Metadata plugin and that it is above the TaglibMetadata > plugin. Restart Kid3 if a plugin change was needed. > > You can then find the chapters of MP4 files in a "Chapters" frame. I have > reused the same dialog as for the synchronized lyrics in MP3 files, so you > can play the file and have the chapters displayed in a (slow) Karaoke-like > fashion. With the context menu, you can directly seek to the position of a > chapter and you can add chapter timestamps while the file is playing or add > them manually and enter the time with the keyboard. I installed the version from git, I checked the plugin is enabled correctly, and am not seeing the chapters frame, the m4b file has 20 chapters in itcreated with OpenAudible -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454416] The "Empty Grouping Plasmoid" and "Empty System Tray" options on the desktop "Add Panel" submenu do nothing
https://bugs.kde.org/show_bug.cgi?id=454416 Bacteria changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||dev.bacterios...@aleeas.com Version|5.24.4 |5.24.90 Ever confirmed|0 |1 --- Comment #1 from Bacteria --- Can reproduce Operating System: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454419] New: Desktop crashes to a Black screen in Wayland, with only the bug reporting tool showing crash info.
https://bugs.kde.org/show_bug.cgi?id=454419 Bug ID: 454419 Summary: Desktop crashes to a Black screen in Wayland, with only the bug reporting tool showing crash info. Product: plasmashell Version: 5.24.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: profhfar...@outlook.com Target Milestone: 1.0 Created attachment 149224 --> https://bugs.kde.org/attachment.cgi?id=149224=edit Screenshot 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. Upgraded to Kubuntu 22.04 from Kubuntu 21.10 with Plasma Wayland Working 2. Try to log into Plasma Wayland. OBSERVED RESULT : instant crash to black screen. In fact loging in by wayland only worked once, and without sound, never again. EXPECTED RESULT: Getting a beautiful KDE Plasma workspace to use. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: PlasmaShell 5.24.4, Kubuntu 22.04 QT 5.15.3, Frameworks 5.920, Linux 5.15.0-33 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Application: plasmashell (5.24.4) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-33-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 22.04 LTS DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140556172900800) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140556172900800) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140556172900800, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fd5ccf91476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fd5ccf777f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fd5cd433ba3 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fd5cb6103e4 in QtWaylandClient::QWaylandDisplay::checkError() const () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7fd5cb6a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7fd5cd6947b8 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fd5cd6b6082 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fd5cd65b74b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fd5cd663ce4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x55bc82bcedce in ?? () #17 0x7fd5ccf78d90 in __libc_start_call_main (main=main@entry=0x55bc82bcdf70, argc=argc@entry=1, argv=argv@entry=0x7fff1164e3a8) at ../sysdeps/nptl/libc_start_call_main.h:58 #18 0x7fd5ccf78e40 in __libc_start_main_impl (main=0x55bc82bcdf70, argc=1, argv=0x7fff1164e3a8, init=, fini=, rtld_fini=, stack_end=0x7fff1164e398) at ../csu/libc-start.c:392 #19 0x55bc82bceef5 in ?? () [Inferior 1 (process 73930) detached] Report to https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 454330] kmymoney crashes when importing a csv file
https://bugs.kde.org/show_bug.cgi?id=454330 Thomas Baumgart changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Thomas Baumgart --- This sounds like it is related to a (malloc/free) problem introduced by an external library. Can you check if this is the case? See https://bugs.kde.org/show_bug.cgi?id=453857#c9 through comments 9-11 how to possibly solve it and report back here. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 454418] Davinci resolve no menu bar or global menu
https://bugs.kde.org/show_bug.cgi?id=454418 --- Comment #1 from Otis Root --- Created attachment 149223 --> https://bugs.kde.org/attachment.cgi?id=149223=edit Example of when applications menu daemon is not running To clarify - this is a solution to the issue but not the ideal solution as it breaks menu bars in all other apps -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 454418] New: Davinci resolve no menu bar or global menu
https://bugs.kde.org/show_bug.cgi?id=454418 Bug ID: 454418 Summary: Davinci resolve no menu bar or global menu Product: kded-appmenu Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: export Assignee: plasma-b...@kde.org Reporter: o...@otisroot.com Target Milestone: --- Created attachment 149222 --> https://bugs.kde.org/attachment.cgi?id=149222=edit Example of observed result when application menus daemon is enabled SUMMARY When opening davinci resolve, there is no menu bar (file, edit, etc) and it does not show up on the KDE global menu widget either. Disabling "Application menus daemon" in Background Services makes a menu bar show up in the davinci resolve menu, but then breaks menu bars for other apps. STEPS TO REPRODUCE 1. Configure global menus+enable the application menus daemon and start it 2. Install and run davinci resolve for linux (I use version 17 from the AUR - davinci-resolve) 3. Open a sample project OBSERVED RESULT There is no menu bar for davinci resolve EXPECTED RESULT There is a menu bar for davinci resolve (either in the global menu or in the app menu) SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION Note that in the attachments, the black space at the very top of the screenshot represents where there should be a global menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450750] Plasma Wayland Crashes when Login
https://bugs.kde.org/show_bug.cgi?id=450750 --- Comment #14 from HFarmer --- I'd like to point out that exactly once I was able to login to plasma wayland BUT for some reason my sound didn't work. Like devices were not detected. No idea if this was a coincidence. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 453007] Editing Latte Dock crashes the whole dock
https://bugs.kde.org/show_bug.cgi?id=453007 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.
[korganizer] [Bug 453062] No method to add attendee/contacts
https://bugs.kde.org/show_bug.cgi?id=453062 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |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.
[kwin] [Bug 452065] Wallpaper background is appearing as white
https://bugs.kde.org/show_bug.cgi?id=452065 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #15 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.
[kwin] [Bug 452522] Display changes to low resolution when HDMI was disconnected
https://bugs.kde.org/show_bug.cgi?id=452522 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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 452251] Incorrectly handling default panels in multi-monitor setups with PRIME
https://bugs.kde.org/show_bug.cgi?id=452251 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[krita] [Bug 445579] Move tool feels really laggy compared to before
https://bugs.kde.org/show_bug.cgi?id=445579 --- 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.
[kdenlive] [Bug 453644] Can't add or remove effects from favorites
https://bugs.kde.org/show_bug.cgi?id=453644 --- 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.
[kwin] [Bug 452941] Crashes when wide window opened
https://bugs.kde.org/show_bug.cgi?id=452941 --- Comment #8 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 453506] Need to kick hotkeys on release, not press
https://bugs.kde.org/show_bug.cgi?id=453506 --- 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.
[frameworks-kglobalaccel] [Bug 426821] Global Shortcut conflicts with another user's conf
https://bugs.kde.org/show_bug.cgi?id=426821 --- 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 453964] Can't prevent system clipboard from being written, even if using blackhole register, when deleting text in Kate Vi mode
https://bugs.kde.org/show_bug.cgi?id=453964 red_Arti changed: What|Removed |Added Version|20.04.2 |22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454248] Kate Vi Mode can't set kaymapping
https://bugs.kde.org/show_bug.cgi?id=454248 red_Arti changed: What|Removed |Added Version|20.04.2 |22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454248] Kate Vi Mode can't set kaymapping
https://bugs.kde.org/show_bug.cgi?id=454248 red_Arti changed: What|Removed |Added Component|part|Vi Input Mode -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415720] switches to pan tool randomly and gets constantly stuck holding the canvas, the only way to exit it is to click another tool.
https://bugs.kde.org/show_bug.cgi?id=415720 2vampirelov...@gmail.com changed: What|Removed |Added CC||2vampirelov...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454417] New: 'gv' can't select last selection sometimes in Kate Vi input mode
https://bugs.kde.org/show_bug.cgi?id=454417 Bug ID: 454417 Summary: 'gv' can't select last selection sometimes in Kate Vi input mode Product: kate Version: 22.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Vi Input Mode Assignee: kwrite-bugs-n...@kde.org Reporter: jijili...@yandex.com Target Milestone: --- STEPS TO REPRODUCE 1. Open Kate and set into Vi input mode 2. Make a selection (visual mode) from right to left, or from down to up. (Use 'v', 'V', or mouse) 3. Press ESC to cancel the selection 4. Press 'gv' to reuse last selection OBSERVED RESULT Can't correctly select last selection EXPECTED RESULT 'gv' restores last selection SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Graphics Platform: X11 ADDITIONAL INFORMATION This bug won't occur if the first selection is from left to right , or from up to down -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454415] System Settings Icon View appears to not honour single- vs double-click setting
https://bugs.kde.org/show_bug.cgi?id=454415 --- Comment #1 from Wedge009 --- I don't know if something has changed in recent Plasma versions but I notice the same has happened with adding widgets to the Panel - used to require a double-click, now it happens with a single-click (double-click adds the selected widget twice). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454416] New: The "Empty Grouping Plasmoid" and "Empty System Tray" options on the desktop "Add Panel" submenu do nothing
https://bugs.kde.org/show_bug.cgi?id=454416 Bug ID: 454416 Summary: The "Empty Grouping Plasmoid" and "Empty System Tray" options on the desktop "Add Panel" submenu do nothing Product: plasmashell Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: zocsfxljsgpmiua...@protonmail.com CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY Title. I'm not sure when those options were added but they do nothing when clicked. STEPS TO REPRODUCE 1. Open the right-click menu on the desktop 2. Click on "Empty Grouping Plasmoid" or "Empty System Tray" on the "Add Panel" submenu OBSERVED RESULT Nothing happens. EXPECTED RESULT Something happens. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.3 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454415] New: System Settings Icon View appears to not honour single- vs double-click setting
https://bugs.kde.org/show_bug.cgi?id=454415 Bug ID: 454415 Summary: System Settings Icon View appears to not honour single- vs double-click setting Product: systemsettings Version: 5.24.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: iconview Assignee: plasma-b...@kde.org Reporter: wedge...@wedge009.net Target Milestone: --- I apologise if this has already been reported - I've searched the reports and couldn't find anything matching what I've been experiencing. I also don't know if the issue lies with KDE specifically or with Kubuntu's packages. SUMMARY I use System Settings in the 'classic' icon view. Single-click vs double-click to open files and folders appears to be set via Workspace Behaviour -> General Behaviour -> Click Behaviour. (The text is different depending on Plasma version but the functionality appears to be the same.) I can also confirm that the 'SingleClick=false' configuration is added to the [KDE] section under ~/.config/kdeglobals. Under Kubuntu 20.04, which uses Plasma 5.18, the System Settings icons behave as I expect with respect to click behaviour. However, with a fresh installation of Kubuntu 22.04, which uses Plasma 5.24, icons are always opened with a single-click regardless if I have specified single-click or double-click to open files/folders. STEPS TO REPRODUCE 1. Install Kubuntu 22.04 (default click behaviour seems to be 'double-click to open') 2. Open KDE System Settings 3. Switch to icon view 4. Click once on any icon OBSERVED RESULT The System Settings icon opens its function with a single-click EXPECTED RESULT The System Settings icon should be selected with a single-click and only open with a double-click, consistent with file/folder behaviour elsewhere. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I grant this isn't a blocker of a bug, but the inconsistency is rather confusing to someone accustomed to double-click to open behaviour, as I am. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454379] plasmashell starts lagging after any file is copied from dolphin and dolphin is closed
https://bugs.kde.org/show_bug.cgi?id=454379 Bacteria changed: What|Removed |Added Summary|When large files are|plasmashell starts lagging |copied, plasmashell slows |after any file is copied |down|from dolphin and dolphin is ||closed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454379] When large files are copied, plasmashell slows down
https://bugs.kde.org/show_bug.cgi?id=454379 --- Comment #1 from Bacteria --- Using the above method, i am able to reproduce with file of any size. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 453716] Kate sometimes crashes when closing a tab in a split view
https://bugs.kde.org/show_bug.cgi?id=453716 --- Comment #3 from Matthew Trescott --- That was quick! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454414] New: Dolphin crashes when inactive and not really doing anything
https://bugs.kde.org/show_bug.cgi?id=454414 Bug ID: 454414 Summary: Dolphin crashes when inactive and not really doing anything Product: dolphin Version: 21.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devyn.ma...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (21.12.2) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.17.9-300.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Dolphin was unfocused for a period of time with two tabs open. I switched from another application to Dolphin and it crashed. Dolphin crashes in similar situations like this for me fairly regularly though I have yet to find some specific cause. The crash can be reproduced sometimes. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::operator-- (this=, this=) at /usr/include/c++/12/bits/atomic_base.h:393 #5 QAtomicOps::deref (_q_value=..., _q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:289 #6 QBasicAtomicInteger::deref (this=, this=) at /usr/include/qt5/QtCore/qbasicatomic.h:119 #7 QSharedDataPointer::~QSharedDataPointer (this=, this=) at /usr/include/qt5/QtCore/qshareddata.h:93 #8 KFileItem::~KFileItem (this=, this=) at /usr/src/debug/kf5-kio-5.93.0-1.fc36.x86_64/src/core/kfileitem.cpp:604 #9 0x7fd07635c601 in QList::node_destruct (n=0x56025c048d40, this=0x56025c13c670) at /usr/include/qt5/QtCore/qlist.h:479 #10 QList::erase (it=..., this=0x56025c13c670) at /usr/include/qt5/QtCore/qlist.h:566 #11 KCoreDirListerCache::reinsert (this=, item=..., oldUrl=...) at /usr/src/debug/kf5-kio-5.93.0-1.fc36.x86_64/src/core/kcoredirlister_p.h:287 #12 0x7fd07636fbe6 in KCoreDirListerCache::processPendingUpdates (this=0x7fd0763e3460 <_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0>) at /usr/src/debug/kf5-kio-5.93.0-1.fc36.x86_64/src/core/kcoredirlister.cpp:2023 #13 0x7fd0749c3726 in QtPrivate::QSlotObjectBase::call (a=0x7ffc6e1490d0, r=, this=0x56025b2b5350) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x7fd0763e3530 <_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0+208>, signal_index=3, argv=0x7ffc6e1490d0) at kernel/qobject.cpp:3886 #15 0x7fd0749be747 in QMetaObject::activate (sender=, m=m@entry=0x7fd074c685a0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc6e1490d0) at kernel/qobject.cpp:3946 #16 0x7fd0749c6abe in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #17 0x7fd0749ba015 in QObject::event (this=0x7fd0763e3530 <_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0+208>, e=0x7ffc6e149230) at kernel/qobject.cpp:1336 #18 0x7fd075525c22 in QApplicationPrivate::notify_helper (this=, receiver=0x7fd0763e3530 <_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0+208>, e=0x7ffc6e149230) at kernel/qapplication.cpp:3637 #19 0x7fd074990118 in QCoreApplication::notifyInternal2 (receiver=0x7fd0763e3530 <_ZZN12_GLOBAL__N_121Q_QGS_kDirListerCache13innerFunctionEvE6holder.lto_priv.0+208>, event=0x7ffc6e149230) at kernel/qcoreapplication.cpp:1064 #20 0x7fd0749e0011 in QTimerInfoList::activateTimers (this=0x56025b24c4a0) at kernel/qtimerinfo_unix.cpp:643 #21 0x7fd0749e08ec in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #22 0x7fd0725f6f4f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7fd07264c168 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #24 0x7fd0725f48e0 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #25 0x7fd0749e0c8a in QEventDispatcherGlib::processEvents (this=0x56025b249e20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x7fd07498eb7a in QEventLoop::exec (this=this@entry=0x7ffc6e1494d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #27 0x7fd074996c22 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #28 0x560259f7771d in main () [Inferior 1 (process 25254) detached] The reporter indicates this bug may be a duplicate of or related to bug 426962. Possible duplicates by query: bug 452658, bug 436680, bug 435346, bug 432268, bug 431071. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379289] Reminders for complete calendar history issued after new install and addition of Google Calendar
https://bugs.kde.org/show_bug.cgi?id=379289 gjditchfi...@acm.org changed: What|Removed |Added Assignee|kdepim-b...@kde.org |dvra...@kde.org Component|reminder daemon (korgac)|Google Resource Product|korganizer |Akonadi CC||gjditchfi...@acm.org, ||kdepim-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 297483] Task reminder doesn't work as expected when "remind my x days before" is used
https://bugs.kde.org/show_bug.cgi?id=297483 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #15 from gjditchfi...@acm.org --- As of version 22.04.0 (5.20.0), korgac has been replaced by a new reminder daemon, kalendarac. If you have upgraded to that version, please watch for unreliable reminders and report them as bugs for product "Reminder Daemon". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 416193] Expose update check interval as a configurable setting
https://bugs.kde.org/show_bug.cgi?id=416193 --- Comment #15 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/310 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454413] Transition from Alt+Tab to Alt+Grave without releasing Alt unexpectedly switches windows
https://bugs.kde.org/show_bug.cgi?id=454413 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 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #13 from RedBearAK --- (In reply to Natalie Clarius from comment #12) > Re. §2: I was not talking about activation and the tab-grave transition > issue, but raising and the singling out a window issue. If I understood you > correctly, you want to be able break the pattern of raising all windows of > an application together by activating a single window of an application with > Alt+Grave. That's the inconsistency I'm questioning. Ah. But I don't see it as inconsistent. If you don't bother to switch to Alt+Graving, all windows are always kept together in GNOME. But if you do take the extra step of moving to Alt+Grave in the middle of Alt+Tabbing then the GNOME devs decided, "Oh, I guess the user just wants a single window this time." It's a hybrid mode that takes the best of both macOS app switching and Linux/Windows window switching. Even in macOS, you can do the right-click context menu or direct click method. But that means you have to take an extra, unusual step to make it happen. If you stick to Cmd+Tab or clicking on the whole Dock icon in macOS, and macOS sticks to keeping all the app windows together. No problem in either case. But there is the flexibility to just grab a single window if/when you really need to. Think of a situation where you might want to just see a single Dolphin window to be able to drag a file onto a Firefox window. If you have several Dolphin windows open and spread all over the screen, they may obscure the browser window and make the drag-and-drop action difficult if you bring the whole group forward in front of the browser window. This is one of the drawbacks of grouping application windows. On rare occasions you simple _don't_ want them all together. I escape the grouped-windows model using one of these methods probably much less than 5% of the time, maybe as little as 1%, but when I do I appreciate that it exists as an option. It's just not something I've ever thought of as being difficult or confusing to the overall issue of keeping app windows together 99% of the time. Simpler task switching, until I need to do something very specific, then I have to make slightly more effort. I see it all as very logical and consistent. Although, macOS is the only environment that has the consistency to keep you "inside" that same application if you happen to close the "isolated" window. In that limited sense, GNOME can produce a bit of inconsistency as it dumps you into a different app. But when you isolated a window and then wanted to close it, quite often that meant you wanted to switch back to a different app anyway, so this hasn't caused me too much of a problem when moving between macOS and GNOME. A little, but not too much. Nothing like the complete lack of app-based switching. I submitted a new bug about the unexpected window activation when transitioning to Alt+Grave. Tried to be as clear as possible with the instructions, so hopefully others can see it the way I see it. But I'm expecting to see a lot of confusion and "Meh?" responses. It's not exactly a showstopper bug. https://bugs.kde.org/show_bug.cgi?id=454413 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454105] plasma panel widgets disappear/get misplaced after plasmashell restart if application icons are present in panel
https://bugs.kde.org/show_bug.cgi?id=454105 Fushan Wen changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453878] Allow configuring the applet to use more than one dictionary, but not all of them
https://bugs.kde.org/show_bug.cgi?id=453878 --- Comment #7 from Fushan Wen --- Git commit 988bcc37b008a8cb4cecbdb18fa985417f1a7aec by Fushan Wen. Committed on 25/05/2022 at 15:56. Pushed by fusionfuture into branch 'master'. applets/dict: add EnabledDictModel to show enabled dictionaries The model will be initialized after the dict list is fetched. M +2-0applets/dict/plugin/dict_plugin.cpp M +230 -1applets/dict/plugin/dictionariesmodel.cpp M +51 -4applets/dict/plugin/dictionariesmodel.h https://invent.kde.org/plasma/kdeplasma-addons/commit/988bcc37b008a8cb4cecbdb18fa985417f1a7aec -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453878] Allow configuring the applet to use more than one dictionary, but not all of them
https://bugs.kde.org/show_bug.cgi?id=453878 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kdeplasma-addons/commit/ ||be5f636c0baa63de4981b89b697 ||0ba02fe2abb87 Resolution|--- |FIXED Version Fixed In||5.26 --- Comment #6 from Fushan Wen --- Git commit be5f636c0baa63de4981b89b6970ba02fe2abb87 by Fushan Wen. Committed on 26/05/2022 at 01:06. Pushed by fusionfuture into branch 'master'. applets/dict: support multiple dictionaries in the config dialog Multiple dictionaries are saved in a string, split with comma ",". FIXED-IN: 5.26 A +77 -0applets/dict/package/contents/ui/AvailableDictSheet.qml [License: GPL(v2.0+)] M +76 -42 applets/dict/package/contents/ui/ConfigDictionaries.qml A +59 -0applets/dict/package/contents/ui/DictItemDelegate.qml [License: GPL(v2.0+)] https://invent.kde.org/plasma/kdeplasma-addons/commit/be5f636c0baa63de4981b89b6970ba02fe2abb87 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453878] Allow configuring the applet to use more than one dictionary, but not all of them
https://bugs.kde.org/show_bug.cgi?id=453878 --- Comment #5 from Fushan Wen --- Git commit 04773128a2d268a79ca9274cb2bd3d56afc03591 by Fushan Wen. Committed on 25/05/2022 at 15:29. Pushed by fusionfuture into branch 'master'. dict: support multiple dicts in the engine The dict protocol supports "Command Pipelining", so the engine can concatenate multiple DEFINE commands into one command. See also: https://datatracker.ietf.org/doc/html/rfc2229#section-4 M +11 -7dict/dictengine.cpp M +2-2dict/dictengine.h https://invent.kde.org/plasma/kdeplasma-addons/commit/04773128a2d268a79ca9274cb2bd3d56afc03591 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 453878] Allow configuring the applet to use more than one dictionary, but not all of them
https://bugs.kde.org/show_bug.cgi?id=453878 --- Comment #4 from Fushan Wen --- Git commit bc8d35bae6d8f67bda734261a84ef4488b2738a7 by Fushan Wen. Committed on 25/05/2022 at 15:29. Pushed by fusionfuture into branch 'master'. dict: don't early return when no definition is found We don't want to abort loading when one dict returns no definition. M +3-2dict/dictengine.cpp M +1-1dict/dictengine.h https://invent.kde.org/plasma/kdeplasma-addons/commit/bc8d35bae6d8f67bda734261a84ef4488b2738a7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454413] New: Transition from Alt+Tab to Alt+Grave without releasing Alt unexpectedly switches windows
https://bugs.kde.org/show_bug.cgi?id=454413 Bug ID: 454413 Summary: Transition from Alt+Tab to Alt+Grave without releasing Alt unexpectedly switches windows Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: redb...@redbearnet.com Target Milestone: --- Alt+Tab and Alt+Grave shortcuts, when used separately by themselves, perform no action until the Alt key is released. User can "cycle" through any number of windows before releasing the Alt key with either shortcut. The chosen window is finally raised only when the user releases the Alt key. Escape will cancel out of the task switcher/action. Transitioning from Alt+Tab to Alt+Grave without releasing Alt currently produces an immediate window raise/activation event, before Alt is released. This is undesirable and contrary to the behavior of these shortcuts when used separately. STEPS TO REPRODUCE 1. Open up at least two different applications, with at least two windows of each app open. 2. Change task switcher settings to clarify what is happening: - Disable "Show selected window" - Visualization: "Large Icons" - Enable "Only one window per application" 3. Press Alt+Tab and release Tab, but keep Alt held down. Result: - The selected icon in the task switcher dialog is the "other" app that doesn't have focus. - No window of the other app has actually been activated/raised. - As long as Alt is held down, the task switcher dialog remains visible. - User can hit Tab any number of times, no window will be raised until Alt is released. 4. Still holding down the Alt key from previous step, now tap the Grave key above Tab. Keep Alt held down. Result: - One window of the "other" app is immediately raised, even though Alt is still held down. (Not normal or expected!) - Subsequent presses of Grave while holding Alt produce no action until Alt is released. (Normal.) 5. Release Alt, then press Alt+Grave and hold Alt again. Result: - Task switcher dialog shows only the windows of the current "app". - No window is raised/activated until the user releases Alt. - Grave can be pressed many times prior to releasing Alt, without performing an action. - Window action results ONLY from releasing the Alt key. EXPECTED RESULT When transitioning (without releasing Alt) between Alt+Tab (Tab pressed any number of times), which produces no action until Alt is released, to Alt+Grave, which also normally produces no final action until Alt is released, the expected behavior is: - No window is immediately raised until Alt is released. - Task switcher dialog changes, as it normally does, from showing all windows (or a single large icon for each "application" with "Large Icons" visualizer and "Only one window per application" enabled) to showing just the windows/thumbnails/icons of the application that was highlighted in the task switcher after pressing Alt+Tab. Repeat: Alt+Tab to Alt+Grave without releasing Alt should result in the user moving through representations in the task switcher of the application that had an icon HIGHLIGHTED in the task switcher after the last Alt+Tab. User should be able to transition back and forth between Alt+Tab and Alt+Grave as many times as they like, without any window raise/activation action ever occurring until Alt is finally released. Or until they hit Escape to cancel the task switcher dialog/action entirely. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon and Fedora 36 KDE spin (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425715] Rectangular Region: Spectacle sometimes hides window, but i can't select a region, when Compositor is suspended.
https://bugs.kde.org/show_bug.cgi?id=425715 --- Comment #5 from CnZhx --- It is my first experience on this issue after doing a system update (upgrade for Tumbleweed). And this issue disappears after toggling on and off the compositor. My system: openSUSE Tumbleweed: 20220523 KDE Plasma: 5.24.5 Qt: 5.15.2 KDE Frameworks: 5.94.0 KDE Applications: 22.04.1 Kernel: 5.17.9-1-default -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454286] Allow using WIP translations
https://bugs.kde.org/show_bug.cgi?id=454286 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1459 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454100] G'MIC-Qt window minimizes itself when not in focus
https://bugs.kde.org/show_bug.cgi?id=454100 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1459 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453949] GMIC:The result of the "boost fade" filter is incorrect
https://bugs.kde.org/show_bug.cgi?id=453949 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1459 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453945] GMIC:the selection area causes the picture position to shift
https://bugs.kde.org/show_bug.cgi?id=453945 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1459 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453947] GMIC:Preview window exception
https://bugs.kde.org/show_bug.cgi?id=453947 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1459 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453190] Copy then paste in reference image tool with nothing selected will crash
https://bugs.kde.org/show_bug.cgi?id=453190 --- Comment #16 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1459 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #12 from Natalie Clarius --- Re. §2: I was not talking about activation and the tab-grave transition issue, but raising and the singling out a window issue. If I understood you correctly, you want to be able break the pattern of raising all windows of an application together by activating a single window of an application with Alt+Grave. That's the inconsistency I'm questioning. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 431610] Suspended reminders gone after restart
https://bugs.kde.org/show_bug.cgi?id=431610 gjditchfi...@acm.org changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #5 from gjditchfi...@acm.org --- As of version 22.04.0 (5.20.0), korgac has been replaced by a new reminder daemon, kalendarac. If you have upgraded to that version, please watch for unreliable reminders and report them as bugs for product "Reminder Daemon". I couldn't reproduce this bug with kalendarac. When I pressed its "Remind in 5 mins" button and shut down until well after the 5 minutes had elapsed, the reminder popped up as soon as I logged in. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #11 from RedBearAK --- (In reply to Natalie Clarius from comment #10) > The transition from Tab to Grave already activating the window before > releasing Alt is an issue on its own though, so I suggest you file a > separate bug report about it. > Yes, I think I should probably do that. I do consider it a bug. > Re. §3: What I meant by "broken" was that you're asking to not have the > auto-raising in the scenario of switching from Tab to Grave, when you > otherwise do want to have it as part of the tab switcher. This sounds > unpredictable to me; but I wouldn't know, I wouldn't use the application > group feature myself at all, so I'm asking what others (besides you) think. > I think we're still not quite on the same page with this part. The tab switcher doesn't act until Alt is released. You can even hit Escape to make it go away without performing any action. Isn't that how Alt+Tab works for you, if you don't release the Alt key? I guess having "Show selected window" active, which it is by default, may make this lack of instant action far less obvious, and vice versa if you disable it the lack of action should be far more obvious. There is definitely no true, final "action" by Alt+Tab until Alt is released. I just want Grave to work the same way. And it does, normally, if used by itself. It's just this transition between Alt+Tab and Alt+Grave which results in an immediate action. To my mind that unexpected immediate action (while Alt is still held down) is what is unpredictable based on the general behavior of either shortcut separately, while Alt is held down. > Re. §4: Okay, this no longer being weird with the script resolves my > confusion. *thumbs up emoji* -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426644] Screens go black / unresponsive after sleep or lock
https://bugs.kde.org/show_bug.cgi?id=426644 --- Comment #17 from Bob English --- Well, for me the problem subsided a while ago after a few updates, but I still have some minor issues with apps all ending up on one screen after sleep, and even some completely off screen with no way to grab them and bring into focus., with a reboot doing the trick for most, accept for a popup from Gnome Evolution that I got lucky and found an edge showing on another desktop! These and other multi-monitor problems have been annoying me for years, and I am about to reinstall my OS to make some changes and in doing so, will try Wayland. I sure hope it doesn't turn out to be a disaster! I will still stick to KDE Plasma though, as Gnome has become cumbersome in getting rid of standard menus (A standard since the first ever GUI) with the hamburger menu just adding clicks and making navigation all messed up, lack of app functionality... and other DE's and bundled apps just not being up to my power user standards. I built a new box, same OS...: Operating System: EndeavourOS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 62.8 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #10 from Natalie Clarius --- Re. §1: Okay, I hadn't thought about disabling the preview. The transition from Tab to Grave already activating the window before releasing Alt is an issue on its own though, so I suggest you file a separate bug report about it. Re. §3: What I meant by "broken" was that you're asking to not have the auto-raising in the scenario of switching from Tab to Grave, when you otherwise do want to have it as part of the tab switcher. This sounds unpredictable to me; but I wouldn't know, I wouldn't use the application group feature myself at all, so I'm asking what others (besides you) think. Re. §4: Okay, this no longer being weird with the script resolves my confusion. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429453] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=429453 --- Comment #9 from Luke-Jr --- https://bugs.kde.org/show_bug.cgi?id=454412 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] New: Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412 Bug ID: 454412 Summary: Bookmarks should have a top-level menu item rather than being hidden in the Go menu Product: kate Version: 22.04.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- Prior to 22.04, Kate had a very usable top-level Bookmarks menu, accessible quickly with Alt-B. After upgrading, it's hidden under a "Go" menu, which has terrible usability. Related (Dolphin has the same complaint): https://bugs.kde.org/show_bug.cgi?id=429453 (In the meantime, what do I need to downgrade to get this back?) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419622] Allow closing the Discover window during install and showing a progress notification instead
https://bugs.kde.org/show_bug.cgi?id=419622 Nate Graham changed: What|Removed |Added Version Fixed In||5.25 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429453] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=429453 --- Comment #8 from Nate Graham --- Yes please. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 454128] Pipewire screen share restore does not restore after the next session
https://bugs.kde.org/show_bug.cgi?id=454128 Nate Graham changed: What|Removed |Added Version|5.23.90 |5.24.90 Version Fixed In||5.25 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #9 from RedBearAK --- (In reply to Natalie Clarius from comment #8) > > But as soon as you press Grave while still holding Alt after doing Alt+Tab, > > the Grave key press triggers the app switch event > > What's the problem with that exactly? You can still switch back to a > different application with Alt+Tab, and you can switch to a different window > being pulled to the front with Alt+Grave. > Main way I can respond to that is by mentioning how I have "Show selected window" disabled. I don't like the way the screen keeps changing when that is enabled. And most desktop environments in Linux or otherwise don't switch to a window when you are Alt+Tabbing until you release Alt. So it's just odd that Alt+Grave would instantly bring that app's windows forward as if you had pressed Alt+Tab and released Alt already. Alt+Grave doesn't pull each individual window forward as you cycle through with additional Grave presses. In other words, it acts like Alt+Tab, waiting for you to decide which window you want before performing an action, except for the very first time you press Grave after Alt+Tab, when it instantly performs an action. The behavior just doesn't feel consistent and predictable. There is no opportunity to Escape without performing any action at all. > The idea is that the implementation would be moved from a KWin script, which > just picks up a signal that a window was activated and catches up on the > other ones, to the task switcher itself, which knows what keys are being > pressed and could decide whether or not to also bring other windows forward > on its own accord. > Yes, that sounds like a solution. > But what you're saying is that the functionality should be ported to core > KWin for the task switcher component but deliberately be broken in the case > of using Alt+Grave in conjunction with Alt+Tab, and I'm not sure that's what > most users who would like to use this option would expect and want. > I'm not aware of asking for anything to be broken. I probably just worded something wrong. > (Also from the GitHub thread) > > > Of course the user can choose to use a thumbnail switcher at all times, but > > "app switching" only really makes sense with the somewhat strange "Only one > > window per application" KDE task switcher option enabled, which makes > > everything weird. > > Why? What is weird about this option? How to explain? It's weird because when you enable that option the task switcher will only show a single icon/preview for each "application", no matter how many windows that app has open. It may or may not be a window preview that does a good job representing the whole application. Application-centric task switching like macOS really treats each application as a monolithic entity, and so such paradigms usually choose to simply show a large application icon for each application, instead of a thumbnail preview of any particular window. Thumbnail sized window previews often look substantially similar, even for completely different applications. Application icons, on the other hand, often look very different from one another. So split-second "app switching" decisions become much easier on the brain, requiring less visual analysis. When you have the "Only one window" option disabled while also trying to use "app switching" as the main task switching paradigm, you give up the simplicity of seeing just a single easily distinguished icon in the task switcher. Which, to me, is one of the primary benefits. If you have six "applications" running and each has 10 windows open, that's 60 icons (or tiny thumbnails) in the task switcher dialog with a window-centric task switcher. But only six icons in an application-centric task switcher dialog. It completely changes the act of task switching, and the mental model of task switching. This was a completely alien way of thinking when I first transitioned from Windows/Linux and started spending most of my time in macOS. It took me a long time to let go of the idea that I was being "limited" by not being able to see all of the open windows on the whole system in the task switcher dialog. But as you can see, I changed my mental model eventually, and learned to work with it. Now I really dislike task switchers that try to show me dozens of almost useless window thumbnails, or even take over the whole screen trying to make the thumbnails big enough to be usable. Pop_OS! does a similar bad thing where it forces the use of the one-icon-per-app task switcher, but completely breaks the ability to actually switch to that "application" as a window group. They apparently did not like the visual complexity of the GNOME "Switch windows" task switcher mode that shows all open windows as thumbnails, but they rejected the logic of treating the windows as a group the way that "Switch applications" normally does. Bug reports were rejected without fixing the issue. In the same way,
[xdg-desktop-portal-kde] [Bug 454128] Pipewire screen share restore does not restore after the next session
https://bugs.kde.org/show_bug.cgi?id=454128 Aleix Pol changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/xdg-desktop-portal-kde/c |ma/xdg-desktop-portal-kde/c |ommit/d782e10c63a7ac9e93951 |ommit/fce184a2fb3ee626e7e23 |2fa9e2352aa3343d143 |28248580ce7382b6125 --- Comment #3 from Aleix Pol --- Git commit fce184a2fb3ee626e7e2328248580ce7382b6125 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 25/05/2022 at 23:30. Pushed by apol into branch 'Plasma/5.25'. screencast: Keep persisting if the user chose to persist (cherry picked from commit d782e10c63a7ac9e939512fa9e2352aa3343d143) M +1-1src/screencast.cpp https://invent.kde.org/plasma/xdg-desktop-portal-kde/commit/fce184a2fb3ee626e7e2328248580ce7382b6125 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 454128] Pipewire screen share restore does not restore after the next session
https://bugs.kde.org/show_bug.cgi?id=454128 Aleix Pol changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/xdg-desktop-portal-kde/c ||ommit/d782e10c63a7ac9e93951 ||2fa9e2352aa3343d143 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Aleix Pol --- Git commit d782e10c63a7ac9e939512fa9e2352aa3343d143 by Aleix Pol. Committed on 25/05/2022 at 14:39. Pushed by apol into branch 'master'. screencast: Keep persisting if the user chose to persist M +1-1src/screencast.cpp https://invent.kde.org/plasma/xdg-desktop-portal-kde/commit/d782e10c63a7ac9e939512fa9e2352aa3343d143 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 419622] Allow closing the Discover window during install and showing a progress notification instead
https://bugs.kde.org/show_bug.cgi?id=419622 Aleix Pol changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/discover/commit/5751e862 ||556f8ee17ea0af60b8e0959559b ||90b6d Resolution|--- |FIXED --- Comment #17 from Aleix Pol --- Git commit 5751e862556f8ee17ea0af60b8e0959559b90b6d by Aleix Pol. Committed on 24/05/2022 at 16:12. Pushed by apol into branch 'master'. Do not prevent closing the main window while busy Instead now we will hide the main window and let discover finish performing the remaining transactions in the background. Thus, now when we close we will: - Hide the main window - Show a SNI to restore the window - Expose the transaction state in KUiServerJobTracker M +1-2CMakeLists.txt M +2-0discover/CMakeLists.txt M +83 -5discover/DiscoverObject.cpp M +5-1discover/DiscoverObject.h M +3-3discover/qml/DiscoverWindow.qml M +4-3libdiscover/backends/DummyBackend/DummyTransaction.cpp https://invent.kde.org/plasma/discover/commit/5751e862556f8ee17ea0af60b8e0959559b90b6d -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429453] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=429453 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #7 from Luke-Jr --- Ugh, now Kate has copied this regression too. Should I open a separate bug? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 438728] after login reminders are shown for dates long passed
https://bugs.kde.org/show_bug.cgi?id=438728 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED --- Comment #3 from gjditchfi...@acm.org --- As of version 22.04.0 (5.20.0), korgac has been replaced by a new reminder daemon, kalendarac. If you have upgraded to that version, please watch for unreliable reminders and report them as bugs for product "Reminder Daemon". Perhaps the system upgrade damaged the files where korgac stored its records of dismissed reminders. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452243] Programs running on Xwayland randomly crash and Xwayland stops working
https://bugs.kde.org/show_bug.cgi?id=452243 winbloc...@gmx.de changed: What|Removed |Added Resolution|UPSTREAM|--- Status|RESOLVED|REOPENED --- Comment #14 from winbloc...@gmx.de --- Sadly i have to report that i encountered the bug again despite xorg-xwayland-git. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 245992] drkonqi should display the gdb output when gdb crashes
https://bugs.kde.org/show_bug.cgi?id=245992 --- Comment #8 from BEEDELL ROKE JULIAN LOCKHART --- As "http://bugs.kde.org/show_bug.cgi?id=454411; demonstrates, for me, DrKonqi reproducibly crashes when I install gdb whilst DrKonqi is operative. Diagnosis would be significantly less difficult if DrKonqi had provided the information that it would have if this proposition had been implemented. Consequently, please reconsider this. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 454411] New: When gdb is installed whilst DrKonqi is operative, DrKonqi is unable to generate traces. Reinitialisation of DrKonqi is necessary to generate traces.
https://bugs.kde.org/show_bug.cgi?id=454411 Bug ID: 454411 Summary: When gdb is installed whilst DrKonqi is operative, DrKonqi is unable to generate traces. Reinitialisation of DrKonqi is necessary to generate traces. Product: drkonqi Version: 5.24.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: backtraceparsing Assignee: plasma-b...@kde.org Reporter: beedellrokejulianlockh...@gmail.com Target Milestone: --- SUMMARY: More specifically, I mean that installation of the GNU Debugger (rather than mere presence, which is what installation is able to mean) does not allow DrKonqi to generate traces, despite the sole instruction that DrKonqi provides if the GNU Debugger is not present being to merely "install gdb", and no way for DrKonqi to be reinitalised without subsequent occurrence of the error that caused initial initialisation of DrKonqi. STEPS TO REPRODUCE: 1. Experience crash. 2. Click the button whose label is “Report Bug” that DrKonqi provides. 3. Observe that DrKonqi is unable to generate traces because the GNU Debugger is not present. 4. Install the GNU Debugger. 5. Observe that DrKonqi is unable to generate traces despite the presence of the GNU Debugger. 6. Experience the crash again if the crash is luckily possible to consistently reproduce. 7. Click the button whose label is “Report Bug” that DrKonqi provides. OBSERVED RESULT: 8. DrKonqi is able to generate traces. EXPECTED RESULT: 3. Generation of the trace by DrKonqi. SOFTWARE/OS VERSIONS: Windows: Unknown. macOS: Unknown. Linux/KDE Plasma: Positive. KDE Plasma Version: “5.24.5”. KDE Frameworks Version: “5.94.0”. Qt Version: “5.15.4”. ADDITIONAL INFORMATION: Addition of "http://bugs.kde.org/show_bug.cgi?id=245992; would have assisted remediation of this problem, so I suggest that it be implemented to assist subsequent diagnosis. I have labelled this problem as "crash" because I recall that DrKonqi stated paraphrasally that the GNU Debugger has crashed. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453700] dolphin in detailed view open files and folders also if I click elsewhere on the line not only on the filename
https://bugs.kde.org/show_bug.cgi?id=453700 thwr...@gmail.com changed: What|Removed |Added CC||thwr...@gmail.com --- Comment #13 from thwr...@gmail.com --- *** Bug 453198 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453198] Switching to a pane in Details view mode results in a file opening
https://bugs.kde.org/show_bug.cgi?id=453198 thwr...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from thwr...@gmail.com --- *** This bug has been marked as a duplicate of bug 453700 *** -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 432301] Korganizer reminders not working
https://bugs.kde.org/show_bug.cgi?id=432301 gjditchfi...@acm.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from gjditchfi...@acm.org --- As of version 22.04.0 (5.20.0), korgac has been replaced by a new reminder daemon, kalendarac. If you have upgraded to that version, please watch for unreliable reminders and report them as bugs for product "Reminder Daemon". If you haven't upgraded that far, can you still reproduce this bug? If so, is the to-do an all-day to-do? Is the reminder set to occur before its start, or before it is due? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 311764] Drkonqi should disable the "Report Bug" button when no debugger is installed and thus no backtrace can be obtained.
https://bugs.kde.org/show_bug.cgi?id=311764 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added CC||beedellrokejulianlockhart@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #8 from Natalie Clarius --- > But as soon as you press Grave while still holding Alt after doing Alt+Tab, > the Grave key press triggers the app switch event What's the problem with that exactly? You can still switch back to a different application with Alt+Tab, and you can switch to a different window being pulled to the front with Alt+Grave. (From the thread on GitHub https://github.com/nclarius/kwin-application-switcher/issues/2) > I don't know how even a modified task switcher could bring back the ability > to optionally choose a single window to isolate and bring forward. The idea is that the implementation would be moved from a KWin script, which just picks up a signal that a window was activated and catches up on the other ones, to the task switcher itself, which knows what keys are being pressed and could decide whether or not to also bring other windows forward on its own accord. But what you're saying is that the functionality should be ported to core KWin for the task switcher component but deliberately be broken in the case of using Alt+Grave in conjunction with Alt+Tab, and I'm not sure that's what most users who would like to use this option would expect and want. (Also from the GitHub thread) > Of course the user can choose to use a thumbnail switcher at all times, but > "app switching" only really makes sense with the somewhat strange "Only one > window per application" KDE task switcher option enabled, which makes > everything weird. Why? What is weird about this option? -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 245992] drkonqi should display the gdb output when gdb crashes
https://bugs.kde.org/show_bug.cgi?id=245992 BEEDELL ROKE JULIAN LOCKHART changed: What|Removed |Added CC||beedellrokejulianlockhart@g ||mail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454166] Cannot change user avatar through System Settings
https://bugs.kde.org/show_bug.cgi?id=454166 --- Comment #3 from 2637827...@qq.com --- Just a banner showing Error saving changes. Reproducible? I'm afraid it is. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 431000] Android 10 permission denied when receiving file
https://bugs.kde.org/show_bug.cgi?id=431000 Tomas Dolezal changed: What|Removed |Added CC||todol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 451437] For Android 10 and 11, KDEConnect cannot send files from phone/tablet (needs upgraded file permissions)
https://bugs.kde.org/show_bug.cgi?id=451437 Tomas Dolezal changed: What|Removed |Added CC||todol...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412655] Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt
https://bugs.kde.org/show_bug.cgi?id=412655 RedBearAK changed: What|Removed |Added CC||redb...@redbearnet.com --- Comment #4 from RedBearAK --- Yep, this bug makes it impossible to transition between the main and alternate task switchers without releasing the Alt key between using Alt+Tab and Alt+Grave. I can finally do grouped-window "app switching" in Plasma with this Kwin script created by Natalie Clarius: https://github.com/nclarius/kwin-application-switcher But I can't have a "Large Icons" task switcher for switching apps, and an alternate "Thumbnails" task switcher unless I release the Alt key after Alt+Tabbing to the desired "application". Without releasing Alt the Alt+Grave shortcut assigned to the alternate task switcher will instead just continue to present the "Large Icons" task switcher from the main task switcher settings. Fully reproducible. This really limits the power of having an alternate task switcher. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454129] [Wayland] Pixelated artifacts when resuming from suspend, which partially reveals content
https://bugs.kde.org/show_bug.cgi?id=454129 --- Comment #4 from Samuel Reddy --- Created attachment 149221 --> https://bugs.kde.org/attachment.cgi?id=149221=edit bad photo of issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454410] New: No subwoofer sound and side channels are playing on the rear channels
https://bugs.kde.org/show_bug.cgi?id=454410 Bug ID: 454410 Summary: No subwoofer sound and side channels are playing on the rear channels Product: systemsettings Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jonas.ja...@gmail.com Target Milestone: --- SUMMARY *** No subwoofer sound and side channels are playing on the rear channels *** STEPS TO REPRODUCE 1. Use Sony STRDH790.CEK 7.2 Channel Dolby Atmos/DTS: X 4K HDR AV Receiver (or probably any 7.1 receiver) 2. In Kubuntu audio settings select "Digital Surround 7.1 (HDMI) Output" 3. Test audio channels OBSERVED RESULT No subwoofer sound Side channels are playing on rear channels EXPECTED RESULT Subwoofer sound Side channels play on side speakers SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454370] Cannot drag and drop in some scenarios Using Wayland (Wine windows apps & Unreal engine)
https://bugs.kde.org/show_bug.cgi?id=454370 Nate Graham changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |kwin-bugs-n...@kde.org Status|NEEDSINFO |REPORTED Product|dolphin |kwin Resolution|WAITINGFORINFO |--- Version|22.04.1 |5.24.5 Component|general |wayland-generic --- Comment #3 from Nate Graham --- Thanks, moving to KWin. Though this may be a WINE issue. Hopefully the KWin developers can tell us or help track it down. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #16 from Benjamin --- regarding your question: no the port should not be a problem...port forwarding and stuff is handled by apache serverside so that is almost surely not a problem -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 448681] digikam uses abandoned library incompatible with ffmpeg 5.0
https://bugs.kde.org/show_bug.cgi?id=448681
--- Comment #28 from caulier.gil...@gmail.com ---
Hi Bernhard and Maik,
I tried to play MP4 video file with FFMPEG5 (current git/master code), without
success. 2 frames are decoded and after, all is stopped:
digikam.metaengine: -- FFMpeg video stream metadata entries :
digikam.metaengine: QMap(("creation_time",
"2016-07-25T16:06:42.00Z")("encoder", "AVC Coding")("handler_name", "Video
Media Handler")("language", "und")("vendor_id", "[0][0][0][0]"))
digikam.metaengine: -
digikam.metaengine: -- FFMpeg audio stream metadata entries :
digikam.metaengine: QMap(("creation_time",
"2016-07-25T16:06:42.00Z")("handler_name", "Sound Media
Handler")("language", "und")("vendor_id", "[0][0][0][0]"))
digikam.metaengine: -
digikam.metaengine: -- FFMpeg root container metadata entries :
digikam.metaengine: QMap(("compatible_brands", "MSNVmp42isom")("creation_time",
"2016-07-25T16:06:42.00Z")("major_brand", "MSNV")("minor_version",
"19595376"))
digikam.metaengine: --
digikam.metaengine: Loading metadata with "FFMpeg" backend from
"/home/gilles/Images/MAH09461.MP4"
digikam.general: Metadata loading with Exiv2 took 171 ms ( true )
digikam.general: "Standard Exif Tags" decoding took 0 ms ( false )
digikam.qtav.warn: no frame could be decompressed: Success 81586/81586
digikam.qtav.warn: invalid video frame from decoder. undecoded data size: 81586
digikam.general: "MakerNote Exif Tags" decoding took 0 ms ( false )
digikam.general: "IPTC Records" decoding took 0 ms ( false )
digikam.general: "XMP Schema" decoding took 0 ms ( false )
digikam.general: Stacked View Mode : 6
digikam.metaengine: ExifTool complete command for action "Load Metadata" with
elasped time (ms): 117
digikam.metaengine: Json Array size: 1
digikam.metaengine: ExifTool Json map size: 134
digikam.metaengine: ExifTool parsed command for action "Load Metadata"
digikam.metaengine: 133 properties decoded
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav.warn: no frame could be decompressed: Success 81586/81586
digikam.qtav.warn: invalid video frame from decoder. undecoded data size: 81586
digikam.qtav.warn: [FFmpeg:h264] illegal short term buffer state detected
digikam.qtav: setInSize => calculating aspect ratio from converted input
data(1.78)
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav.warn: Decode audio failed. undecoded: 0
...
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav: End of file. erreof=1 feof=0
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav: audio thread gets an eof packet. pkt.pts: -1.000,
d.render_pts0:-1.000
digikam.qtav.warn: Decode audio failed. undecoded: 0
digikam.qtav: audio decode eof done
digikam.qtav: delay 0.50s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.15 s, nb fast: 30, v_a: 0.4200
digikam.qtav: delay 0.51s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.15 s, nb fast: 31, v_a: 0.4300
digikam.qtav: delay 0.52s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.16 s, nb fast: 32, v_a: 0.4400
digikam.qtav: delay 0.53s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.16 s, nb fast: 33, v_a: 0.4500
digikam.qtav: delay 0.54s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.17 s, nb fast: 34, v_a: 0.4600
digikam.qtav: delay 0.55s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.17 s, nb fast: 35, v_a: 0.4700
digikam.qtav: delay 0.56s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.18 s, nb fast: 36, v_a: 0.4800
digikam.qtav: delay 0.57s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.18 s, nb fast: 37, v_a: 0.4900
digikam.qtav: delay 0.58s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.19 s, nb fast: 38, v_a: 0.5000
digikam.qtav: delay 0.59s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.19 s, nb fast: 39, v_a: 0.5100
digikam.qtav: delay 0.60s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.20 s, nb fast: 40, v_a: 0.5200
digikam.qtav: delay 0.61s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.20 s, nb fast: 41, v_a: 0.5300
digikam.qtav: delay 0.62s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.21 s, nb fast: 42, v_a: 0.5400
digikam.qtav: delay 0.63s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.21 s, nb fast: 43, v_a: 0.5500
digikam.qtav: delay 0.64s @0.000s pts:0.120
digikam.qtav.warn: video too fast!!! sleep 0.22 s, nb fast: 44, v_a: 0.5600
digikam.qtav: delay 0.65s @0.000s pts:0.120
digikam.qtav.warn:
[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #15 from Benjamin --- Not easy to say, but I would check the follwowing: - Update nextcloud to the newest release - Install openssl 3 on the server where the nc instance is running on your desktop: check out the issue i have posted above maybe there is a different solution to your problem. ...besides: I use backports ppa on my kubuntu to ensure that the newest packages are installed and updated... This is all I can say sofar. But to be honest: I don't think that the problem is within nextcloud or serverside. It seems more a problem with akonadi/openssl/kontact (as this work together)... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 nk0...@yahoo.fr changed: What|Removed |Added CC||nk0...@yahoo.fr --- Comment #7 from nk0...@yahoo.fr --- I have strictly always the the same scrambled position as that described by William 2022-05-25 16:07:54 utc. My initial bug was 452506 with the changes in the file plasma-org.kde.plasma.desktop-appletsrc (see 452506 But my two machines with the problem have each an additional screen An additional observation : Sometimes after boot, when the start screen closes and the desktop opens we can see in reality two desktop screen : -the first one during half a second with the icons scrambled -the second one with the icons at the right place I wanted to go further and find why the system displays two screens but sorrily I did find anything in journalctl. But this is for me the way. And for time to time sometimes the second screen display does not come and the icons remain scrambled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435170] Option to bring all of an app's windows to the front when one window is switched to
https://bugs.kde.org/show_bug.cgi?id=435170 --- Comment #7 from RedBearAK --- (In reply to Natalie Clarius from comment #6) > It should be noted that the KWin script acts on any window activation event, > i.e. not only when task switching with Alt+Tab, but also with the task > manager in the panel, clicking on a window directly, or when activation was > requested from another process. Distinguishing how a window was activated is > not possible with the KWin scripting API. > > So if it is desired to have application grouping behavior only selectively, > e.g. only in the Alt+Tab task switcher, and maybe only when the window was > not selected by going from Tab to Grave while holding Alt as described in > the previous comment, that would actually require reimplementing the feature > in the core tabbox code (and wherever else one would want to have this). > > Would this still be desirable? The thing with the Alt+Grave issue is that Alt+Tabbing as many times as you want doesn't trigger a window activation as long as you keep holding the Alt key. But as soon as you press Grave while still holding Alt after doing Alt+Tab, the Grave key press triggers the app switch event, and brings all of the app's windows forward. You can then continue to hold Alt and press Grave as many times as you want, but no other window will be brought forward within the app's stack until you release the Alt key. I would have expected the initial press of the Grave key after Alt+Tab to _not_ produce a window activation, the same way that pressing Alt+Tab doesn't immediately trigger a window switch. And I would want Alt+Grave after Alt+Tab (while holding Alt) to mimic the method in GNOME that allows a single window to be brought forward. If the icon was selected via Alt+Grave rather than Alt+Tab, only that individual window should be brought forward. (The thing that apparently can't be done with just a Kwin script.) GNOME's implementation of this is actually superior to macOS. In macOS the only ways to bring a single window forward are A) right-clicking on the app's Dock icon and selecting from the window list in the context menu, or B) finding a way to make a piece of the desired background window visible behind the current window so that you can click on it with the mouse cursor. You can of course also use these methods in GNOME, but I prefer the predictability and speed of hitting Alt+Tab, Grave, Grave, to zero in on a specific window on those rare occasions that I don't want to bring the whole "application" forward as a group. You could describe this as application-centric task switching with the option to enact a single instance of window-centric task switching if the situation calls for it. The application-centric main task switcher still allows the choice of the specific window to be found more rapidly than typical "show me all open windows" task switching, which can be quite overwhelming with many open windows. (Thus the reason to invent workspaces.) But most of the time the most important thing is to keep app windows together. When I'm working with files I typically want to see multiple locations in different windows and be able to drag/move/copy between them easily without tracking down the sibling windows. Same goes for apps like terminals. What I have going in one terminal is often directly related to what I have in another terminal, so I normally want them to just hang out together. So the way the Kwin script is already working is a _BIG_ piece of the puzzle. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 412655] Tabbox uses wrong visualization when switching between Main and Alternative while holding a common Alt
https://bugs.kde.org/show_bug.cgi?id=412655 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 453857] malloc() aborts during save
https://bugs.kde.org/show_bug.cgi?id=453857 Isaac Wismer changed: What|Removed |Added CC||kdeb...@iwismer.ca --- Comment #11 from Isaac Wismer --- I'm no longer seeing the crash after updating gnutls 3.7.5-1 to 3.7.5-2 on Arch. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 453121] calender can't connect to nextcloud
https://bugs.kde.org/show_bug.cgi?id=453121 --- Comment #14 from m.eik michalke --- i checked with "akonadictl --verbose start" and don't see any errors regarding "qt.network.ssl", it just shows the HTTP error (0) without any further warnings or errors. i also configured nextcloud to use log level 0 (debug, most verbose) and checked the logs: i don't even see a communication attempt, let alone any errors. there's also nothing logged by apache2. after that, i installed vdirsyncer in my kubuntu 22.04 client and configured it to use the same auth data i was trying to use with kontact. it took quite a while, but i was able to discover and sync both calendars and contacts with vdirsyncer. also, i can see that in the nextcloud logs as expected. any theories why kontact might noch even try to reach the nextcloud server? i am using a custom port (not 443) for HTTPS, is it possible that kontact/akonadi are ignoring it allthough it's given in the URL? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454370] Cannot drag and drop in some scenarios Using Wayland (Wine windows apps & Unreal engine)
https://bugs.kde.org/show_bug.cgi?id=454370 --- Comment #2 from xdm.corporat...@gmail.com --- (In reply to Nate Graham from comment #1) > Are you using Wayland or X11? Wayland. When I tested in x11 the issue was not happening -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 454409] New: Skanlite crashes when it attempts to access my scanner.
https://bugs.kde.org/show_bug.cgi?id=454409 Bug ID: 454409 Summary: Skanlite crashes when it attempts to access my scanner. Product: Skanlite Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: beedellrokejulianlockh...@gmail.com Target Milestone: --- Application: skanlite (22.04.1) Qt Version: 5.15.4 Frameworks Version: 5.94.0 Operating System: Linux 5.18.0-60.fc37.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 37 (Rawhide Prerelease) DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I have been able to scan 2 times, but currently Skanlite is unable to preview and reselect the device. I have not interacted with my printer since my 2nd initialisation of Skanlite. This error occured during my 3rd and subsequent initialisations. - Custom settings of the application: This occurred during my 3rd initialisation of Skanlite. The previous initialisation did not retain what I configured during my 1st initialisation. The 3rd initialisation retained the configuration of the 2nd initialisation. Closure of Skanlite and subsequent disablement and enablement of my scanner has remediated this problem: I was instructed to choose the device to utilise, I am able to preview and scan, and Skanlite did not retain my previous configuration. The crash can be reproduced every time. -- Backtrace: Application: Skanlite (skanlite), signal: Segmentation fault [KCrash Handler] #4 0x7f3e4b203ee5 in esci_request_status () from /usr/lib64/sane/libsane-epson2.so.1 #5 0x7f3e4b204c5a in close_scanner () from /usr/lib64/sane/libsane-epson2.so.1 #6 0x7f3e568114c8 in sane_dll_close () from /lib64/libsane.so.1 #7 0x7f3e586b3a12 in KSaneIface::KSaneCore::closeDevice() () from /lib64/libKF5Sane.so.5 #8 0x7f3e586a9aca in KSaneIface::KSaneWidget::closeDevice() () from /lib64/libKF5Sane.so.5 #9 0x5653f0dc5d4a in Skanlite::reselectScannerDevice() () #10 0x7f3e56f28216 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #11 0x7f3e57aa3ca6 in QAbstractButton::clicked(bool) () from /lib64/libQt5Widgets.so.5 #12 0x7f3e57aa3f1e in QAbstractButtonPrivate::emitClicked() () from /lib64/libQt5Widgets.so.5 #13 0x7f3e57aa5b5c in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 #14 0x7f3e57aa5d7b in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f3e579f2768 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f3e579afc42 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f3e579b82c2 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f3e56ef4c38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f3e579b63c2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib64/libQt5Widgets.so.5 #20 0x7f3e57a0babc in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f3e57a0ee80 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f3e579afc42 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #23 0x7f3e56ef4c38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #24 0x7f3e57330d95 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib64/libQt5Gui.so.5 #25 0x7f3e5730ff7c in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #26 0x7f3e526a7b7e in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #27 0x7f3e55640f9f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #28 0x7f3e556962a8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #29 0x7f3e5563e930 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #30 0x7f3e56f458da in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #31 0x7f3e56ef369a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #32 0x7f3e56efb742 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #33 0x5653f0dc04be in main () [Inferior 1 (process 32668) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454026] can't turn off application menu translucency
https://bugs.kde.org/show_bug.cgi?id=454026 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #13 from Nate Graham --- > Of course breeze has opaque option but I don't plan to use breeze. Thanks, that's what I thought. Transparency is a theme-specific thing, as is the ability to configure it. If you want the ability to configure the opacity level of non-Breeze Plasma themes as well, you'll have to contact their creators and ask them to opt into it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 --- Comment #18 from ice@spoko.pl --- Created attachment 149220 --> https://bugs.kde.org/attachment.cgi?id=149220=edit New crash information added by DrKonqi krita (5.0.5) using Qt 5.15.4 - What I was doing when the application crashed: I was exporting a saved image. Krita crashed every time upon confirming the export. -- Backtrace (Reduced): #4 0x7f6af7f69c47 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x2) at /usr/include/c++/9/bits/atomic_base.h:413 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x2) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 [...] #8 QList::~QList (this=0x55ed5114ca70, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:873 #9 0x7f6af7ff378c in KToolBar::Private::~Private (this=0x55ed5114c9c0, __in_chrg=) at ./libs/widgetutils/xmlgui/ktoolbar.cpp:83 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 453884] Krita 5.0.6 crashes during saving
https://bugs.kde.org/show_bug.cgi?id=453884 ice@spoko.pl changed: What|Removed |Added CC||ice@spoko.pl -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 454026] can't turn off application menu translucency
https://bugs.kde.org/show_bug.cgi?id=454026 --- Comment #12 from David Chmelik --- Turning them on makes readable but shouldn't have to enable some effects to stop others rather than turn all off (as was possible) to be normal/plain... disabling translucency/transparency effect should be for all cases. Of course breeze has opaque option but I don't plan to use breeze. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 --- Comment #10 from Nate Graham --- If that environment variable does something different for GTK4 apps compared to GTK3 apps, that's pretty unfortunate. I don't know if it's possible for us to conditionalize it in Plasma code based on the GTK toolkit version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454408] New: Zoom effect isn't smoothed anymore
https://bugs.kde.org/show_bug.cgi?id=454408 Bug ID: 454408 Summary: Zoom effect isn't smoothed anymore Product: kwin Version: 5.24.90 Platform: Other OS: Linux Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- Until https://invent.kde.org/plasma/kwin/-/merge_requests/2451, the image displayed by the Zoom effect was smoothed. Not it isn't anymore, and it's pixelated instead. I suspect because of using nearest neighbor scaling: data->texture->setFilter(GL_NEAREST); -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452707] [Wayland] Moving files from one partition to another with Dolphin results in a Plasma memory leak that can potentially make the whole computer unusable
https://bugs.kde.org/show_bug.cgi?id=452707 guimarcalsi...@gmail.com changed: What|Removed |Added CC||guimarcalsi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442901] GTK4 apps have double scaling on hidpi
https://bugs.kde.org/show_bug.cgi?id=442901 Dennis Aldea changed: What|Removed |Added CC||dennis.al...@gmail.com --- Comment #9 from Dennis Aldea --- (In reply to Felis from comment #7) > It looks like the GDK_DPI_SCALE variable used to offset the font size isn't > being used anymore by GTK4 > https://github.com/GNOME/gtk/blob/0579220546f7daff16a907f4c3256098c344e40c/ > NEWS.pre-4.0#L1308. My workaround is to halve the font size in the > settings.ini. Changes made to `~/.config/gtk-4.0/settings.ini` do not take effect; the file is rewritten at startup. I have been explictly setting `GDK_SCALE=1` whenever I run a GTK4 application. Is there any way to persistently change this setting for GTK4 apps only? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 452707] [Wayland] Moving files from one partition to another with Dolphin results in a Plasma memory leak that can potentially make the whole computer unusable
https://bugs.kde.org/show_bug.cgi?id=452707 guimarcalsi...@gmail.com changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from guimarcalsi...@gmail.com --- I can confirm this happens. There are a few interesting things: 1. The memory on plasmashell only starts increasing after the moving operation is complete. 2. If you close Dolphin while it's increasing, it stops increasing, but it doesn't free up the memory it used either. 3. As reported in the original message, it only happens when Cutting and pasting files, not copying. 4. When I clicked on the panel after closing Dolphin, the shell crashed with the following output: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 39581] [New LWP 39495] [New LWP 39457] [New LWP 39436] [New LWP 39437] [New LWP 39607] [New LWP 39580] [New LWP 39603] [New LWP 39435] [New LWP 39439] [New LWP 39604] [New LWP 39441] [New LWP 39442] [New LWP 39644] [New LWP 39443] [New LWP 39444] [New LWP 39445] [New LWP 39446] [New LWP 39447] [New LWP 39448] [New LWP 39456] [New LWP 39458] [New LWP 39497] [New LWP 39579] [New LWP 39602] [New LWP 39605] [New LWP 39606] [New LWP 39438] [New LWP 39494] [New LWP 39440] [New LWP 39496] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f473b7fe700 (LWP 39581))] __preamble__ [Current thread is 1 (Thread 0x7f473b7fe700 (LWP 39581))] Thread 31 (Thread 0x7f474b42d700 (LWP 39496)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e42ba26700) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e42ba266b0, cond=0x55e42ba266d8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e42ba266d8, mutex=0x55e42ba266b0) at pthread_cond_wait.c:647 #3 0x7f47b92ff6db in QWaitConditionPrivate::wait(QDeadlineTimer) (deadline=..., this=0x55e42ba266b0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait(QMutex*, QDeadlineTimer) (this=this@entry=0x55e42bb2c258, mutex=mutex@entry=0x55e42bb2c250, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f47baf88214 in QSGRenderThreadEventQueue::takeEvent(bool) (wait=true, this=0x55e42bb2c248) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qdeadlinetimer.h:68 #6 QSGRenderThread::processEventsAndWaitForMore() (this=this@entry=0x55e42bb2c1b0) at scenegraph/qsgthreadedrenderloop.cpp:936 #7 0x7f47baf88689 in QSGRenderThread::run() (this=0x55e42bb2c1b0) at scenegraph/qsgthreadedrenderloop.cpp:1053 #8 0x7f47b92f9643 in QThreadPrivate::start(void*) (arg=0x55e42bb2c1b0) at thread/qthread_unix.cpp:331 #9 0x7f47b8c8d609 in start_thread (arg=) at pthread_create.c:477 #10 0x7f47b8f76133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 30 (Thread 0x7f47b0947700 (LWP 39440)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e4298ff850) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e4298ff800, cond=0x55e4298ff828) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e4298ff828, mutex=0x55e4298ff800) at pthread_cond_wait.c:647 #3 0x7f47a263a5eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47a263a1eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f47b8c8d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f47b8f76133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 29 (Thread 0x7f4765c13700 (LWP 39494)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55e42bba3dc4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55e42bba3d70, cond=0x55e42bba3d98) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55e42bba3d98, mutex=0x55e42bba3d70) at pthread_cond_wait.c:647 #3 0x7f47a263a5eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47a263a1eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f47b8c8d609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f47b8f76133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 28 (Thread 0x7f47b3448700 (LWP 39438)): #0 0x7f47b8f6999f in __GI___poll (fds=0x7f47a8004a60, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f47b77f636e in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f47b77f64a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f47b953ac72 in QEventDispatcherGlib::processEvents(QFlags)
[dolphin] [Bug 452289] service-menu-installer ignores symlinks on uninstall
https://bugs.kde.org/show_bug.cgi?id=452289 Nate Graham changed: What|Removed |Added Version Fixed In||22.08 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
