[frameworks-kio] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 Nate Graham changed: What|Removed |Added Version Fixed In|5.108 |5.109 --- Comment #15 from Nate Graham --- My mistake sorry, it's fixed in 1.09, not 1.08. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 471079] okteta show empty HEX-dump area
https://bugs.kde.org/show_bug.cgi?id=471079 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Kalk] [Bug 471790] Incorrect calculations, possibly because of formatting
https://bugs.kde.org/show_bug.cgi?id=471790 --- Comment #7 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.
[okular] [Bug 471198] Ocular crashes when unplugging UCB-C multi-monitor docking station.
https://bugs.kde.org/show_bug.cgi?id=471198 --- Comment #7 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 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 --- 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.
[frameworks-kconfigwidgets] [Bug 466743] Crash when using KCommandBar
https://bugs.kde.org/show_bug.cgi?id=466743 --- 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.
[Discover] [Bug 472296] Crashed when opening an item in discover
https://bugs.kde.org/show_bug.cgi?id=472296 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472296] New: Crashed when opening an item in discover
https://bugs.kde.org/show_bug.cgi?id=472296 Bug ID: 472296 Summary: Crashed when opening an item in discover Classification: Applications Product: Discover Version: 5.24.7 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: ian.sch...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.15.0-76-generic x86_64 Windowing System: Wayland Distribution: Linux Mint 21.1 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Double-clicked on tuxracer to get more information about the program. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=139670658741824) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=139670658741824) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=139670658741824, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f07f63ea476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f07f63d07f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f07f688aba3 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f07f2246e45 in () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #11 0x7f07f22565dd in QtWaylandClient::QWaylandDisplay::dispatchQueueWhile(wl_event_queue*, std::function, int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #12 0x7f07f225c63b in QtWaylandClient::QWaylandWindow::waitForFrameSync(int) () at /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #13 0x7f07eb463bf2 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so #14 0x7f07f85f761c in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7f07f85f7e07 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x7f07f68c6ca1 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f07f643cb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #18 0x7f07f64cea00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 15 (Thread 0x7f07c8c6d640 (LWP 38281) "plasma-d:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55dfcd02d8e0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55dfcd02d8e0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f07f643bac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dfcd02d890, cond=0x55dfcd02d8b8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55dfcd02d8b8, mutex=0x55dfcd02d890) at ./nptl/pthread_cond_wait.c:627 #5 0x7f07e9a9fced in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f07e9a5335b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f07e9a9fc1b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f07f643cb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f07f64cea00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 14 (Thread 0x7f07c946e640 (LWP 38280) "plasma-d:gdrv0"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x0, clockid=0, expected=0, futex_word=0x55dfccf899f4) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55dfccf899f4, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f07f643bac1 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55dfccf899a0, cond=0x55dfccf899c8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0x55dfccf899c8, mutex=0x55dfccf899a0) at ./nptl/pthread_cond_wait.c:627 #5 0x7f07e9a9fced in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #6 0x7f07e9a5335b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #7 0x7f07e9a9fc1b in () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #8 0x7f07f643cb43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f07f64cea00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 13 (Thread 0x7f07ca66d640 (LWP 38273) "dconf worker"): #1 0x7f07f54011f6 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f07f53a93e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f07d011d33d in () at /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so #4
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 --- Comment #14 from S. Christian Collins --- This bug is marked as "fixed in 5.108", but I have KDE Frameworks 5.108.0 and I can still repro the bug exactly as in my original instructions. Unless the "5.108" version is incomplete or pertaining to something other than frameworks? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472295] New: Crash upon first invocation of Discover
https://bugs.kde.org/show_bug.cgi?id=472295 Bug ID: 472295 Summary: Crash upon first invocation of Discover Classification: Applications Product: Discover Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: rvdois+rvu...@rokejulianlockhart.anonaddy.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.6) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.2-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.6 [CoredumpBackend] -- Information about the crash: I installed this system 5 minutes ago. When I first opened Discover, it crashed. I opened the Konqi notification. After that, I authenticated with Wi-Fi and opened Discover again, and it worked without crashing. Upon submitting the report via Konqi, Konqi told me it couldn't report the issue, citing https://bugs.kde.org/rest/bug?token=236970-SLGSrc4Kg8. When I closed Konqi, a crash report appeared again, which was this one. The crash does not seem to be reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault PID: 2329 (plasma-discover) UID: 1000 (rokejulianlockhart) GID: 1000 (rokejulianlockhart) Signal: 11 (SEGV) Timestamp: Sun 2023-07-16 03:14:15 BST (23s ago) Command Line: /usr/bin/plasma-discover Executable: /usr/bin/plasma-discover Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.discover-787fe276487641799129be7f3ccd29c1.scope Unit: user@1000.service User Unit: app-org.kde.discover-787fe276487641799129be7f3ccd29c1.scope Slice: user-1000.slice Owner UID: 1000 (rokejulianlockhart) Boot ID: e316e2e767bb4e098fa0d1ced4d47fa2 Machine ID: 908d4262dade41a1915eaf926da23809 Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.plasma-discover.1000.e316e2e767bb4e098fa0d1ced4d47fa2.2329.168947365500.zst (present) Size on Disk: 49.2M Message: Process 2329 (plasma-discover) of user 1000 dumped core. Stack trace of thread 2329: #0 0x7f0e51292abc __pthread_kill_implementation (libc.so.6 + 0x8fabc) #1 0x7f0e51241266 raise (libc.so.6 + 0x3e266) #2 0x7f0e53b98d3a _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d3a) #3 0x7f0e51241330 __restore_rt (libc.so.6 + 0x3e330) #4 0x7f0e51904497 _ZNSt13__atomic_baseIP10QMutexDataE23compare_exchange_strongERS1_S1_St12memory_orderS4_ (libQt5Core.so.5 + 0x104497) #5 0x7f0e51aef374 _ZNSt11unique_lockI6QMutexE4lockEv (libQt5Core.so.5 + 0x2ef374) #6 0x7f0e51af050d _ZN16QCoreApplication9postEventEP7QObjectP6QEventi (libQt5Core.so.5 + 0x2f050d) #7 0x7f0e00379b69 _ZNSt17_Function_handlerIFvvEZN17PackageKitBackend6searchERKN24AbstractResourcesBackend7FiltersEEUlvE7_E9_M_invokeERKSt9_Any_data (packagekit-backend.so + 0x2bb69) #8 0x7f0e51b192b0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x3192b0) #9 0x7f0e535a519e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1a519e) #10 0x7f0e51aed4f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2ed4f8) #11 0x7f0e51af0af1 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2f0af1) #12 0x7f0e51b46c83 postEventSourceDispatch (libQt5Core.so.5 + 0x346c83) #13 0x7f0e50116988 g_main_context_dispatch (libglib-2.0.so.0 + 0x5d988) #14 0x7f0e50116d98 n/a (libglib-2.0.so.0 + 0x5dd98) #15 0x7f0e50116e2c g_main_context_iteration (libglib-2.0.so.0 + 0x5de2c) #16 0x7f0e51b46496 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x346496) #17 0x7f0e51aebf8b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebf8b) #18 0x7f0e51af4420 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2f4420) #19 0x5615e12462a0 main (plasma-discover + 0x192a0) #20 0x7f0e5122abf0 __libc_start_call_main (libc.so.6 + 0x27bf0) #21 0x7f0e5122acb9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27cb9) #22 0x5615e1246c95 _start (plasma-discover + 0x19c95) Stack trace of thread 2343: #0 0x7f0e50112f6a n/a (libglib-2.0.so.0 + 0x59f6a) #1
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 jade changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=468295 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 jade changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=461657 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 jade changed: What|Removed |Added CC||k...@lfcode.ca --- Comment #7 from jade --- See also (possible duplicate): https://bugs.kde.org/show_bug.cgi?id=461657 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 --- Comment #8 from jade --- Another thought I have is there's another bug that I sometimes experience in which the monitor brightness gets desynchronized after monitors dim for sleep warning: is this a general DDC/DPMS handling bug where the monitor's state gets out of sync? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 --- Comment #7 from maelstrom256+bugs.kde@gmail.com --- (In reply to Ilya Bizyaev from comment #6) > Looks like this might be the same problem as described in > https://bugs.kde.org/show_bug.cgi?id=468295. WDYT? It sounds reasonable for me. I think main reasons are: * night-to-day transition doesn't occurs for some reason * day-to-night transition doesn't calculate real transition, but forces start point at instant -- You are receiving this mail because: You are watching all bug changes.
[www.kde.org] [Bug 472294] New: Add a "Help" link to the header
https://bugs.kde.org/show_bug.cgi?id=472294 Bug ID: 472294 Summary: Add a "Help" link to the header Classification: Websites Product: www.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: n...@kde.org Target Milestone: --- We have https://kde.org/support/, but the link to it is buried at the bottom of the page where someone looking for help will never get to before they quit. I'd recommend moving the link to this page up to the header, and rename it "Help" rather than "Support". -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 472293] New: Won't open/display VCard created by Thunderbird
https://bugs.kde.org/show_bug.cgi?id=472293 Bug ID: 472293 Summary: Won't open/display VCard created by Thunderbird Classification: Applications Product: kaddressbook Version: 5.19.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@marcchamberlin.com CC: to...@kde.org Target Milestone: --- SUMMARY Can't import/display VCard from Thunderbird client email application. *** 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. Create a VCard in Thunderbird and select to attach it to emails. 2. Send a test email to yourself. 3. Click on the attached VCard to open it. 4. KAddressBook is selected, by default, for opening VCards. Click on it to open the VCard. OBSERVED RESULT The KaddressBook app is started and opens of it's main dialog. Nothing is shown about the information stored in the VCard. I did try it with Emacs to make sure there is content in the VCard. There is, and it appears to be OK. EXPECTED RESULT The VCard content should be shown and automatically added to the Address Books. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSuSE 15.4 with KDE (available in About System) AND WHERE IS "ABOUT SYSTEM" LOCATED IN OPENSUSE? Please pay attention to details! KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 462672] Night Color Custom Time "Begin day color at:" fails to activate (at least when screen locked).
https://bugs.kde.org/show_bug.cgi?id=462672 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com Version|5.26.4 |5.27.6 --- Comment #1 from Ilya Bizyaev --- Could this be a duplicate of https://bugs.kde.org/show_bug.cgi?id=468295? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469730] Night color shifting does not start at the correct time or end at the correct time
https://bugs.kde.org/show_bug.cgi?id=469730 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com --- Comment #5 from Ilya Bizyaev --- Could this be a duplicate of https://bugs.kde.org/show_bug.cgi?id=468295? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461657] Night color does not deactivate when waking the computer up from sleep
https://bugs.kde.org/show_bug.cgi?id=461657 Ilya Bizyaev changed: What|Removed |Added CC||bizy...@zoho.com --- Comment #6 from Ilya Bizyaev --- Wow, I have an almost identical script! $ cat ~/bin/fix-kwin-color.sh #!/usr/bin/env bash qdbus-qt5 org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect.preview 4000 sleep 5s qdbus-qt5 org.kde.KWin /ColorCorrect org.kde.kwin.ColorCorrect.stopPreview Looks like this might be the same problem as described in https://bugs.kde.org/show_bug.cgi?id=468295. WDYT? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable
https://bugs.kde.org/show_bug.cgi?id=468295 Ilya Bizyaev changed: What|Removed |Added Version|5.27.4 |5.27.6 CC||bizy...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 472085] NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 Ben Cooksley changed: What|Removed |Added CC||bcooks...@kde.org Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Ben Cooksley --- This was due to a faulty mirror that was no longer active and has been removed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472292] New: discover reports unexpected stop when I close the app after updating.
https://bugs.kde.org/show_bug.cgi?id=472292 Bug ID: 472292 Summary: discover reports unexpected stop when I close the app after updating. Classification: Applications Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: texag...@hotmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. run update 2. close program 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472291] Media player doesn't show up in notification tray
https://bugs.kde.org/show_bug.cgi?id=472291 geoangerc...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from geoangerc...@gmail.com --- seems to be fixed with 1.26.4 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472291] New: Media player doesn't show up in notification tray
https://bugs.kde.org/show_bug.cgi?id=472291 Bug ID: 472291 Summary: Media player doesn't show up in notification tray Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: geoangerc...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY When I connect KDE Connect to my PC, I cannot see the media playing from my PC in my Android's notification tray. It was previously possible, but now it seems to be broken. STEPS TO REPRODUCE 1. Connect android and PC 2. Play some music on PC 3. Look at android's media players OBSERVED RESULT The media player from the PC doesn't show up on android. even though they correctly show up when you open the app then go to "Multimedia controls" EXPECTED RESULT I would expect the app to show media controls in android's notification tray SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: GNOME 44 ADDITIONAL INFORMATION I'm using GSConnect on PC. I've reset & reinstalled both KDE on my android and GSConnect on my PC. The media players show correctly when I open the "KDE Connect" app on phone and click on "Multimedia controls". -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 471514] Need a plasma widget to display progress of data transfer between devices, i.e., usb to/from hdd, etc
https://bugs.kde.org/show_bug.cgi?id=471514 --- Comment #1 from Steven --- I would like to see widgets that display a graph of transfer speed, like Winblows. The y-axis should be the transfer speed of the channel, i.e., SATA-1 is 150 MB/s, SATA-2 is 300 MB/s, and SATA-3 is 600 MB/s. USB 1.0 low speed is 192 kB/s, USB 1.0 full speed is 1.5 MB/s, USB 2.0 high speed is 60 MB/s, USB 3.0 SuperSpeed (aka USB 3.1 Gen 1) is 500 MB/s, USB 3.1 SuperSpeed+ (aka USB 3.1 Gen 2) is 1.212 GB/s, USB 3.2 SuperSpeed+[66] (aka USB 3.2 Gen 2×2) is 2.424 GB/s, USB4 Gen 3×2 is 4.8 GB/s, USB4 Gen 4×2 is 9.6 GB/s. These values taken from: https://en.wikipedia.org/wiki/List_of_interface_bit_rates#Peripheral I would hope the device driver can detect the max capability of a channel, i.e., most usb-a to usb-c cables are only wired for usb 2.0 speeds. Can the driver detect usb 3.0 speed cables? usb 3.1 cables?, etc. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453853] file size display: please follow BinaryUnitDialect everywhere
https://bugs.kde.org/show_bug.cgi?id=453853 Jack Hill changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kcoreaddons/-/commit ||/58cb8fcc5f8290cf2ecac5c3f5 ||ebd9ac69aa8f10 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Jack Hill --- Git commit 58cb8fcc5f8290cf2ecac5c3f5ebd9ac69aa8f10 by Jack Hill. Committed on 12/07/2023 at 17:01. Pushed by cullmann into branch 'master'. Use BinaryUnitDialect from config when using DefaultBinaryDialect in formatByteSize Still fall back to IECBinaryDialect if the value isn't set, or isn't set properly. Related: bug 472111 M +8-2src/lib/util/kformatprivate.cpp https://invent.kde.org/frameworks/kcoreaddons/-/commit/58cb8fcc5f8290cf2ecac5c3f5ebd9ac69aa8f10 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 472111] Respect the users' choice of BinaryUnitDialect
https://bugs.kde.org/show_bug.cgi?id=472111 Jack Hill changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kcoreaddons/-/commit ||/58cb8fcc5f8290cf2ecac5c3f5 ||ebd9ac69aa8f10 --- Comment #3 from Jack Hill --- Git commit 58cb8fcc5f8290cf2ecac5c3f5ebd9ac69aa8f10 by Jack Hill. Committed on 12/07/2023 at 17:01. Pushed by cullmann into branch 'master'. Use BinaryUnitDialect from config when using DefaultBinaryDialect in formatByteSize Still fall back to IECBinaryDialect if the value isn't set, or isn't set properly. Related: bug 453853 M +8-2src/lib/util/kformatprivate.cpp https://invent.kde.org/frameworks/kcoreaddons/-/commit/58cb8fcc5f8290cf2ecac5c3f5ebd9ac69aa8f10 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472290] systemsettings5 crash after changing theme (and after debian upgrade 10 to 11)
https://bugs.kde.org/show_bug.cgi?id=472290 --- Comment #2 from ulysse.schwa...@gmail.com --- Hello, OK thank you, I will upgrade plasma. Best regards Le sam. 15 juil. 2023 à 21:33, Bug Janitor Service a écrit : > https://bugs.kde.org/show_bug.cgi?id=472290 > > Bug Janitor Service changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |DOWNSTREAM > > --- Comment #1 from Bug Janitor Service --- > > Thank you for the bug report! > > However Plasma 5.20.5 is no longer eligible for support or maintenance from > KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a > supported version as soon as your distribution makes it available to you. > Plasma is a fast-moving project, and bugs in one version are often fixed > in the > next one. > > If you need support for Plasma 5.20.5, please contact your distribution, > who > bears the responsibility of providing support for older releases that are > no > longer supported by KDE. > > If you can reproduce the issue after upgrading to a supported version, feel > free to re-open this bug report. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472290] systemsettings5 crash after changing theme (and after debian upgrade 10 to 11)
https://bugs.kde.org/show_bug.cgi?id=472290 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.20.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.20.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 472085] NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 --- Comment #4 from Zhenbo Li --- (In reply to Ben Cooksley from comment #3) > If you'd prefer not to make that information public please email it to me > direct. Thank you. I've sent these info to your email. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 469377] Elisa's latest (23.7.70) f-droid build can't find any music on the device.
https://bugs.kde.org/show_bug.cgi?id=469377 Stefan Brüns changed: What|Removed |Added Component|Baloo File Daemon |general Assignee|baloo-bugs-n...@kde.org |matthieu_gall...@yahoo.fr Product|frameworks-baloo|Elisa CC||stefan.bruens@rwth-aachen.d ||e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 468394] r.xml syntax highlighting definitions miss specified integers (e.g., 3L)
https://bugs.kde.org/show_bug.cgi?id=468394 Christoph Cullmann changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/syntax-highlighting/ ||-/commit/ef856a14e35194f0ee ||532326dfa5042adbeea251 Status|ASSIGNED|RESOLVED --- Comment #4 from Christoph Cullmann --- Git commit ef856a14e35194f0ee532326dfa5042adbeea251 by Christoph Cullmann, on behalf of Jonathan Poelen. Committed on 15/07/2023 at 19:26. Pushed by cullmann into branch 'master'. R: add numeric suffix (i and L) It doesn't seem to be a bug on our side, but I did make one change: highlighting suffixes. I wonder if we shouldn't generalize and standardize this? There are several behaviors depending on the syntax: There are several behaviors depending on the syntax: - no treatment for suffixes, they often (always?) have the Normal color - number and suffix have the same color, but the color of the same suffix can vary between Float, Int, Hex, etc. - suffixes have a dedicated color As shown in this commit, I'm in favor of the dedicated color and propose to generalize it to all syntaxes, what do you think? M +3-0autotests/folding/highlight.R.fold M +3-0autotests/html/highlight.R.dark.html M +3-0autotests/html/highlight.R.html M +3-0autotests/input/highlight.R M +3-0autotests/reference/highlight.R.ref M +7-2data/syntax/r.xml https://invent.kde.org/frameworks/syntax-highlighting/-/commit/ef856a14e35194f0ee532326dfa5042adbeea251 -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 472085] NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 --- Comment #3 from Ben Cooksley --- Can you please provide the contents (as an attachment) of the detailed Craft logs? It looks like the mirror you are being sent to for those files is refusing to provide service to you however i'll need those logs to confirm. If you could also confirm your ISP/Country that would be helpful as well. If you'd prefer not to make that information public please email it to me direct. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472275] kphotoalbum hangs on new image detection.
https://bugs.kde.org/show_bug.cgi?id=472275 --- Comment #7 from Tobias Leupold --- Displaying which file is currently processed is for sure no bad idea. It's only that we never ran into such a problem during the last two decades, so nobody came up with this idea yet ;-) So, v...@phux.dev, it would be very kind if you would spare some time to track this down. If we can identify some image/file which causes this, which we can use to reproduce the problem, we will of course try to fix this. In spite of that, it's a good idea to be more verbose about what's going on when scanning for new files. We will take that into account. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472002] Some KCMs take a few seconds to load completely
https://bugs.kde.org/show_bug.cgi?id=472002 --- Comment #3 from Alexander Lohnau --- Same if you scroll in the plasmasearch KCM. Some actions are only rendered when scrolling to them, but when scrolling to the top, the ones previously shown take time to render again. I asked Marco about this a few days ago, maybe we can investigate it the next days. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472290] New: systemsettings5 crash after changing theme (and after debian upgrade 10 to 11)
https://bugs.kde.org/show_bug.cgi?id=472290 Bug ID: 472290 Summary: systemsettings5 crash after changing theme (and after debian upgrade 10 to 11) Classification: Applications Product: systemsettings Version: 5.20.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ulysse.schwa...@gmail.com Target Milestone: --- Application: systemsettings5 (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-23-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: - What I was doing when the application crashed: i upraded from debian10 to debian11, then lauchned systemsettings5 it worked, i changed a them, close systemsettings5, and since then systemsettings5 keep crashing if i try to reopen it. discover also crash. i have not tried all kde applications, ktorrent works for example... - Unusual behavior I noticed: - Custom settings of the application: The crash can be reproduced every time. -- Backtrace: Application: Configuration du système (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f24e08c4610 in QObject::objectName() const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f24d97234d6 in chameleon::ChameleonStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/libchameleon.so #6 0x7f24d971d9e0 in chameleon::ChameleonStyle::drawComplexControl(QStyle::ComplexControl, QStyleOptionComplex const*, QPainter*, QWidget const*) const () from /usr/lib/x86_64-linux-gnu/qt5/plugins/styles/libchameleon.so #7 0x7f244b86b89f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #8 0x7f244b86c87f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so #9 0x7f24dfd25d95 in QQuickWindowPrivate::polishItems() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f24dfdab18e in QQuickRenderControl::polishItems() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7f24e0048be5 in ?? () from /lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5 #12 0x7f24e149aa04 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f24e145a15f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f24e089afca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f24e1492046 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f24e1496963 in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f24e1499af3 in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f24e14968e9 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f24e149697f in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f24e1496909 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f24e149697f in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f24e1499af3 in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f24e14968e9 in QWidgetPrivate::showChildren(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f24e149697f in QWidgetPrivate::show_helper() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f24e1499af3 in QWidgetPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x55e1efd4a82f in ?? () #27 0x55e1efd4c1d9 in ?? () #28 0x7f24e08c6ff1 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f24e1e01659 in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #30 0x7f24e145a15f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f24e089afca in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f24e089da01 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f24e08f2e93 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f24de3bce6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f24de3bd118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f24de3bd1cf in
[systemsettings] [Bug 461439] Application Appearance - KDE apps - systemsettings5 crash
https://bugs.kde.org/show_bug.cgi?id=461439 ulysse.schwa...@gmail.com changed: What|Removed |Added CC||ulysse.schwa...@gmail.com Component|general |generic-crash Version|5.18.7 |5.20.5 Platform|unspecified |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472289] Render - Queue hangs (project must be reopened)
https://bugs.kde.org/show_bug.cgi?id=472289 fehler-im-progr...@posteo.de changed: What|Removed |Added Summary|Render - queue hangs|Render - Queue hangs |(project must be reopened) |(project must be reopened) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472289] New: Render - queue hangs (project must be reopened)
https://bugs.kde.org/show_bug.cgi?id=472289
Bug ID: 472289
Summary: Render - queue hangs (project must be reopened)
Classification: Applications
Product: kdenlive
Version: 23.04.3
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Effects & Transitions
Assignee: j...@kdenlive.org
Reporter: fehler-im-progr...@posteo.de
Target Milestone: ---
Created attachment 160309
--> https://bugs.kde.org/attachment.cgi?id=160309=edit
Screenshot "Render-Warten ..."
STEPS TO REPRODUCE
1. Render many small videos or video sequences (1 second is enough).
2. At some point the project has to be restarted, even though the last video
was rendered successfully.
OBSERVED RESULT
Video successfully rendered, but re-rendering doesn't work because queue
freezes ("Wait ...")
EXPECTED RESULT
Rendering again works, queue processed
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[Craft] [Bug 472085] NeoChat failed to install on Windows 10 via craft, may due to libs/mingw-crt4msvc
https://bugs.kde.org/show_bug.cgi?id=472085 --- Comment #2 from Zhenbo Li --- Thanks Tobias I've tried various times, and I found wget failed very frequently. Is this caused by my internet condition (I assume it's good enough) or something at the server? ===full log=== PS C:\CraftRoot> craft libs/mingw-crt4msvc Craft : C:\CraftRoot Version : master ABI : windows-cl-msvc2019-x86_64 Download directory : C:\CraftRoot\download *** Handling package: dev-utils/7zip-base, action: all *** *** Action: fetch-binary for dev-utils/7zip-base *** *** dev-utils/7zip-base not found in cache *** *** Action: fetch for dev-utils/7zip-base *** wget https://files.kde.org/craft/3rdparty/7zip/2301/7z2301-extra.zip Action: fetch for dev-utils/7zip-base:23.01 FAILED *** Craft all failed: dev-utils/7zip-base after 0 seconds *** fatal error: package dev-utils/7zip-base all failed Craft stopped with out completing ['dev-utils/7zip-base', 'dev-utils/cmake-base', 'dev-utils/kshimgen', 'dev-utils/7zip', 'dev-utils/cmake', 'dev-utils/wget', 'dev-utils/git', 'python-modules/pip-system', 'python-modules/virtualenv', 'dev-utils/python3', 'python-modules/pip', 'virtual/bin-base', 'dev-utils/patch', 'dev-utils/sed', 'dev-utils/jom', 'dev-utils/ninja', 'virtual/craft-blueprints-kde-base', 'craft/craft-core', 'craft/craft-blueprints-kde', 'virtual/base', 'libs/mingw-crt4msvc'] -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 472288] Updated language file for Hungarian language
https://bugs.kde.org/show_bug.cgi?id=472288 --- Comment #4 from Maik Qualmann --- You don't need to do anything else, the translators will read along with you. I changed the product from digiKam to i18n and set the components to "hu" so that the translators would be made aware of this bug report via email. Maik -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 472288] Updated language file for Hungarian language
https://bugs.kde.org/show_bug.cgi?id=472288 --- Comment #3 from Peter --- Thank You Maik. "I redirected it to the Hungarian translators. " Who should I send the translations to? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 472288] Updated language file for Hungarian language
https://bugs.kde.org/show_bug.cgi?id=472288 --- Comment #2 from Maik Qualmann --- Hi Peter, I redirected it to the Hungarian translators. We as the digiKam team are only responsible for the original English text. Maik -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 472288] Updated language file for Hungarian language
https://bugs.kde.org/show_bug.cgi?id=472288 Maik Qualmann changed: What|Removed |Added Assignee|digikam-bugs-n...@kde.org |ulys...@kubuntu.org Product|digikam |i18n CC||metzping...@gmail.com Version|8.2.0 |unspecified Component|Usability-i18n |hu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472288] Updated language file for Hungarian language
https://bugs.kde.org/show_bug.cgi?id=472288 --- Comment #1 from Peter --- Sorry, I made a mistake... Correct po file sources: https://l10n.kde.org/stats/gui/trunk-kf5/po/digikam.po/ -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470128] Saving document with resized text creates huge memory footprint
https://bugs.kde.org/show_bug.cgi?id=470128 --- Comment #7 from dorla.hu...@gmail.com --- Update: this time, the problem popped up again but it seems to be random. Going from 2MiB to 102MiB. I have manually redownloaded the PDF and transfered all anotations manually to the new PDF, which is 100MiB smaller now. Unfortunately, this is stressful, when I try to learn for an oral exam in two days and have only finished half of the materials. I did not resize anything this time. I probably pressed accidentally an unknown key combination. The `pdffonts` tools does not show any suspicious fonts and is the same for the 102MiB and the 2MiB version of the same document: ``` name type encoding emb sub uni object ID - --- --- --- - AC+ArialMT TrueType WinAnsi yes yes yes 9 0 AE+Calibri TrueType WinAnsi yes yes yes 17 0 AG+ArialMT TrueType WinAnsi yes yes yes 24 0 AI+ArialMT TrueType WinAnsi yes yes yes 41 0 AK+Wingdings-Regular TrueType WinAnsi yes yes yes 64 0 AM+Calibri-ItalicTrueType WinAnsi yes yes yes 91 0 AO+Calibri TrueType WinAnsi yes yes yes109 0 ``` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471835] "Apply Plasma settings" popup is bigger than normal and its buttons are missing
https://bugs.kde.org/show_bug.cgi?id=471835 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472288] New: Updated language file for Hungarian language
https://bugs.kde.org/show_bug.cgi?id=472288 Bug ID: 472288 Summary: Updated language file for Hungarian language Classification: Applications Product: digikam Version: 8.2.0 Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Usability-i18n Assignee: digikam-bugs-n...@kde.org Reporter: benedekppe...@gmail.com Target Milestone: --- Hi I don't know where to upload it, so I'm posting it here... The Hungarian language translation of digiKam is very neglected. I decided to review, improve and expand the translation. po file source: https://l10n.kde.org/stats/gui/trunk-kf5/po/digikam._desktop_.po/ Updated language file: https://mega.nz/folder/1VICTQTa#HQYqUgt5os9NWjkqushTNw Regards Peter -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 471941] KJob dtor force-quits applications
https://bugs.kde.org/show_bug.cgi?id=471941 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- So Nicolas, is this expected and we need to mention it in the KF5->KF6 porting notes? Or is something we should fix? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471935] Cannot interact with tabbox using pointer when modifier key used to trigger the tabbox is shared with the window move feature
https://bugs.kde.org/show_bug.cgi?id=471935 Nate Graham changed: What|Removed |Added Flags|Wayland+|Wayland- Severity|normal |minor Keywords||wayland CC||n...@kde.org Summary|Cannot interact with tabbox |Cannot interact with tabbox |window due to Alt window|using pointer when modifier |move|key used to trigger the ||tabbox is shared with the ||window move feature -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472003] Clicks on systray icons have no effect
https://bugs.kde.org/show_bug.cgi?id=472003 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Cannot reproduce. Can you reproduce it with today's git master, Patrick? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471874] In Plasma 6 Wayland, Spectacle via Shift-PrtScr yields garbage image, (GTK/Gnome app issue?)
https://bugs.kde.org/show_bug.cgi?id=471874 Nate Graham changed: What|Removed |Added Version|unspecified |master Product|kde |kwin Status|CONFIRMED |NEEDSINFO CC||n...@kde.org Summary|Plasma 6 Screenshotting,|In Plasma 6 Wayland, |(Shift-PrtScr) in Wayland |Spectacle via Shift-PrtScr |yields garbage image, |yields garbage image, |(GTK/Gnome app issue?) |(GTK/Gnome app issue?) Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org Resolution|--- |WAITINGFORINFO Component|general |wayland-generic --- Comment #3 from Nate Graham --- Cannot reproduce. Some questions for both of you who can reproduce the issue: Does it only happen while Flatseal is open, or does it always happen when you take a screenshot using Shift+PrintScreen? Does it happen if you use the GUI to take a full screen screenshot, instead of a shortcut? Does it happen if you take a Rectangular Region screenshot, instead of a fulls screen screenshot? What kind of GPU are you using? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472287] Media control notification missing
https://bugs.kde.org/show_bug.cgi?id=472287 --- Comment #1 from Fabian --- Ironically, I usually control my laptop's media with the physical buttons of my phone via a macro, but that macro checks if a media control notification exists, so it also got broken. I guess I'll switch it to detecting the persistent notification instead and leave that on for now, then this bug barely affects me anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472287] Media control notification missing
https://bugs.kde.org/show_bug.cgi?id=472287 Fabian changed: What|Removed |Added CC||fabianroel...@googlemail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472287] New: Media control notification missing
https://bugs.kde.org/show_bug.cgi?id=472287 Bug ID: 472287 Summary: Media control notification missing Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 10.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: fabianroel...@googlemail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY There is no media control notification anymore. A while ago it worked. Media control in the app works and other notifications are shown. Toggling the setting off and on again does not help. SOFTWARE/OS VERSIONS Linux: Manjaro 23.0 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.5.10 App version: 1.26.3 (can't select that in the version field) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472002] Some KCMs take a few seconds to load completely
https://bugs.kde.org/show_bug.cgi?id=472002 Nate Graham changed: What|Removed |Added CC||alexander.loh...@gmx.de, ||n...@kde.org --- Comment #2 from Nate Graham --- I notice that both KCMs are using the PluginSelector component. Does the same issue happen in any other KCMs? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 76380] Trashing files on other partitions and disks that are mounted without UID=USERID, GID=USERGROUPID, FMASK=177, DMASK=077 copies them to the Trash directory on /
https://bugs.kde.org/show_bug.cgi?id=76380 calvinatorzcr...@gmail.com changed: What|Removed |Added CC||calvinatorzcr...@gmail.com --- Comment #85 from calvinatorzcr...@gmail.com --- (In reply to Oleg Grigorev from comment #82) > The problem is reproducible on Arch Linux for a drive with BTRFS inside LUKS > mounted at /mnt/hdd > Dolphin moves files from another drive to ~/.local/Trash > Everything works correctly when using trash-cli, files are moved to > /mnt/hdd/.Trash-1000 > I can't say at what point it broke, but as far as I remember, on a previous > laptop with a similar drives configuration, but without LUKS on the > additional disk, everything worked. Perhaps the problem is with LUKS, but > there could be something else. > > Software versions: > Plasma v5.23.1 > KDE Framework v5.87.0 have pretty much the exact same problem with an arch btrfs system on latest everything -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472190] Deleting messages causes folder contents to disappear
https://bugs.kde.org/show_bug.cgi?id=472190 --- Comment #2 from Tweak --- (In reply to Colin J Thomson from comment #1) > I have seen this over many releases/years. > I think it is something to do with the threading. FWIW I have the Mailing > List option set. > > I just ran a quick test and it does not seem happen with the "flat" view > options. > > View > Message List > Aggregation > > > kmail-23.04.3 Thank you for this, I will give it a try. Hopefully this gets repaired at some point. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472275] kphotoalbum hangs on new image detection.
https://bugs.kde.org/show_bug.cgi?id=472275 --- Comment #6 from Andreas Schleth --- Yes, it does not solve the problem immediately, but it would open up the path to fixing the issue. The guys programming KPA put in a lot of effort and are quite good at fixing problems they can reproduce. We have a twofold problem here: a) the program hangs (should be fixed) b) you suggest a program improvement (somehow show the current filename) To my understanding, it would help a lot if we know about a) (why does it hang? can we reproduce it?). The hang might not even be due to a corrupt file or so but due to some other filesystem problems (permissions, strange filename or whatever). I often encounter problems with non-ASCII letters in filenames. One program interprets them as ISO8859 the other as UTF-8, ... So the hang might even occur before the program has any chance to write out the filename. So my first idea would be to have a critical look at the folder names. Image files usually have standardized names from the camera or phone that are pure ASCII. "... so the program just stopped working the day I added some random file it did not like. ..." If you have an idea about the date, you only need to look at the files (and folders!) from around that date and not the whole database. Anyway, binary search is very nice to you, even with a large number of files. 1 instead of 1000 images would only take 3-4 more loops. Just imagine how much more (unpaid!) effort goes into improving and fixing the program :-) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472275] kphotoalbum hangs on new image detection.
https://bugs.kde.org/show_bug.cgi?id=472275 Tobias Leupold changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||t...@stonemx.de --- Comment #5 from Tobias Leupold --- Hey, thanks for your bug report. But we can't fix a "It no work on me system", if we can't reproduce the problem. It would be for sure no problem to add a debugging output showing which exact file is currently processed. But you would have to compile this code to get the output. We can't add some code as a random shot, so that you can wait until our next release to get it. So either, you do what Andreas suggested (that's the way I would search for the problem, too), or you learn how to manually compile KPA. It's quite easy, you can read this here: https://community.kde.org/KPhotoAlbum/build_instructions – in this case I can send a patch containing the code that will output the currently scanned image. I don't see another way to fix this if we can't see the problem … -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472286] New: Add a default virtual keyboard for plasma
https://bugs.kde.org/show_bug.cgi?id=472286 Bug ID: 472286 Summary: Add a default virtual keyboard for plasma Classification: Plasma Product: plasmashell Version: master Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Input Method Assignee: plasma-b...@kde.org Reporter: greenismypep...@protonmail.com CC: aleix...@kde.org Target Milestone: 1.0 SUMMARY *** I noticed that KDE plasma includes it's own qt based virtual keyboard however it only works on SDDM. Is there anyway to make this keyboard accessible on the desktop like any other virtual keyboard and make it the default option? Currently if you install a KDE plasma distro you either have to hope your distro maintainers included a virtual keyboard package or you have to manually find and download one yourself. This is inconvenient for tablet PC users who want their system to work out of the box. *** STEPS TO REPRODUCE 1. Go to 'System Settings' 2. Go to 'Input Devices' 3. Go to 'Virtual Keyboard' OBSERVED RESULT There is no default virtual keyboard unless your distro maintainers preinstalled a package. EXPECTED RESULT There should be a default virtual keyboard option for users who do not wish/don't know how to install third party virtual keyboard packages. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 472285] New: HTML-Mail - Picture is rotated 90°
https://bugs.kde.org/show_bug.cgi?id=472285 Bug ID: 472285 Summary: HTML-Mail - Picture is rotated 90° Classification: Applications Product: kontact Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: axel.br...@gmx.de Target Milestone: --- When taking pictures with a camera, this is usually done in landscape or in portrait mode. When inserting a picture in a HTML-mail in landscape mode, everything is fine. When inserting a portrait picture, it is rotated 90° - although dolphin display it correctly! Reproducible - always An option to rotate picture in the mail would solve the issue - respecting EXIF settings probably as well. Thank you -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472275] kphotoalbum hangs on new image detection.
https://bugs.kde.org/show_bug.cgi?id=472275 --- Comment #4 from v...@phux.dev --- that is a lot of work for a big library like mine and totally unnecessary one if the program would simply offer proper transparency about what it is doing and where it is running into issues. Thank you for the fast response but your suggestion is not a solution to my problem, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 472275] kphotoalbum hangs on new image detection.
https://bugs.kde.org/show_bug.cgi?id=472275 --- Comment #3 from Andreas Schleth --- There is quite a good way to find the right file. It will take some patience but not too much: 1. create a new folder somewhere outside your current image folder 2. copy a few (maybe 10-100) of your latest images there 3. create a new KPA database in the new folder and see if it hangs a) it hangs: one of the images is the culprit goto 4. b) it does not hang: add a few more images - repeat until you hit a hang (goto 2.) 4. The culprit is one of the last batch. Let's call it the "suspects". Copy the suspects somewhere you find them. 5. Start again with 1. (an empty folder) and put just half of the suspects there. Repeat the process until you are down to one image that makes KPA hang. Have a look at that image with another tool - does it look normal or strange? This sounds quite tedious but it converges quite fast: for ~1000 images, you would only need 10 passes to find the culprit. Welcome to binary search! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470743] Next and Previous buttons of the Media Player applet don't work
https://bugs.kde.org/show_bug.cgi?id=470743 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/d75188e860a6abd215550a7be ||43486175f2e645b Status|ASSIGNED|RESOLVED --- Comment #10 from Nate Graham --- Git commit d75188e860a6abd215550a7be43486175f2e645b by Nate Graham. Committed on 15/07/2023 at 15:32. Pushed by ngraham into branch 'master'. applets/mediacontroller: fix broken actions Broken in the Actions refactor when these invocations of the old API weren't ported. A simple fix would be to port these old invocations of the removed action_thing() function calls to use root.serviceOp() instead, but that would lead to some code duplication, so instead let's add new top-level public functions for these things and reference those functions consistently in all places, which fixes the bug automatically. M +5-5 applets/mediacontroller/package/contents/ui/ExpandedRepresentation.qml M +31 -11 applets/mediacontroller/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/d75188e860a6abd215550a7be43486175f2e645b -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472283] plasmashell crashes when attempting to configure unknown applet
https://bugs.kde.org/show_bug.cgi?id=472283 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472283] plasmashell crashes when attempting to configure unknown applet
https://bugs.kde.org/show_bug.cgi?id=472283 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 472284] New: Modifying the playlist while Elisa is playing results in a wrong playing order
https://bugs.kde.org/show_bug.cgi?id=472284 Bug ID: 472284 Summary: Modifying the playlist while Elisa is playing results in a wrong playing order Classification: Applications Product: Elisa Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: mosa...@posteo.de Target Milestone: --- SUMMARY When a song from above the currently playing position is moved to the position after the currently playing, Elisa does not play this song next. Instead the next song playing is one from above the current position or the current position again. STEPS TO REPRODUCE 1. Create a playlist with three songs. 2. Play the last (third) song by double clicking it. 3. Drag the first song to the last position. 4. The next song that will be played is not the expected (just dragged) one. OBSERVED RESULT The next song playing will be song two of the playlist (the one, you just listened to). In longer playlists it could be another one from above the current position, but it will never be the recently dragged song. EXPECTED RESULT The now third (former fist) song should be played. After the dragging the song this is the next song in the list, thus it should be played next. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 6.3.12-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 472078] xdg-desktop-portal-kde crashes on Plasma 6 startup
https://bugs.kde.org/show_bug.cgi?id=472078 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Nate Graham --- Awesome, thanks for following up! -- You are receiving this mail because: You are watching all bug changes.
