[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 --- Comment #2 from aux...@gmail.com --- Created attachment 169257 --> https://bugs.kde.org/attachment.cgi?id=169257=edit PDF file with 2 acronyms demonstrating the issue. The two acronyms are REST, SOAP. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484358] Automatic adaptive sync fails to deactivate on exit
https://bugs.kde.org/show_bug.cgi?id=484358 Tom Dzmelyk changed: What|Removed |Added CC||tddzm...@mtu.edu Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Tom Dzmelyk --- Still present with kwin 6.0.4.1 Tested on Arch (fully up to date as of today). If the system is booted while the setting is set to Adaptive Sync=Never on both monitors the behavior is correct (even if it's bad). If one monitor is set to adaptive sync = automatic and the other is set to never, the flicker will manifest on both monitors I have tried minimizing every open application on every monitor, closing everything on every monitor. Only restarting the session or adjusting the refresh rate manually in "Display Properties" after changing the refresh rate will correct the undesirable behavior. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482705] Selecting MP4/H.264 for video output creates garbled video.
https://bugs.kde.org/show_bug.cgi?id=482705 illode changed: What|Removed |Added CC||ill...@illode.io --- Comment #4 from illode --- I have the same issue. Arch Linux with these versions: lib32-libva-mesa-driver 1:24.0.6-2 lib32-mesa 1:24.0.6-2 lib32-vulkan-radeon 1:24.0.6-2 libva-mesa-driver 1:24.0.6-2 mesa 1:24.0.6-2 mesa-utils 9.0.0-4 vulkan-radeon 1:24.0.6-2 CPU: Ryzen 7950X3D GPU: Radeon 6900XT Logs say it's using the GPU to record. Last I checked (>1 year), I'm able to record H.264 / H.265 without issue using either the iGPU or dGPU via OBS. I know for sure H.264 / H.265 on the iGPU work currently with OBS, since it's what I use for normal recording. Recording using vp9 also works fine. The only difference in the logs are these lines: [h264_vaapi @ 0x7dd9c80b3680] Driver does not support some wanted packed headers (wanted 0xd, found 0x1). which it says once when the recording starts, and EE ../mesa-24.0.6/src/gallium/drivers/radeonsi/radeon_vcn_enc_1_2.c:1224 radeon_enc_encode_params UVD - DCC surfaces not supported. which it spams until the recording stops. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486094] My Effects/Composition stack is unusable
https://bugs.kde.org/show_bug.cgi?id=486094 --- Comment #3 from batwalk...@gmail.com --- I just realized that the computer info is missing, I distinctly remember putting it in there, but here's the info: OS: Garuda Linux BirdOfPrey Soaring x86_64 Kdenlive: Version 24.02.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467219] Effect stack: drag and drop reordering crash
https://bugs.kde.org/show_bug.cgi?id=467219 --- Comment #8 from Jean-Baptiste Mardelle --- Git commit f5ab6310f24537ab5f9f826f7bba629e35881920 by Jean-Baptiste Mardelle. Committed on 07/05/2024 at 04:18. Pushed by mardelle into branch 'release/24.05'. FIx crash dragging from effect stack to another sequence M +15 -42 src/effects/effectstack/view/collapsibleeffectview.cpp M +6-6src/effects/effectstack/view/collapsibleeffectview.hpp M +51 -14 src/effects/effectstack/view/effectstackview.cpp M +6-1src/effects/effectstack/view/effectstackview.hpp M +0-2src/timeline2/view/qml/Clip.qml M +2-4src/timeline2/view/qml/TrackHead.qml M +1-2src/timeline2/view/qml/timeline.qml https://invent.kde.org/multimedia/kdenlive/-/commit/f5ab6310f24537ab5f9f826f7bba629e35881920 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486699] New: KDE font anti-aliasing range exclusion checkbox is fake-on when no font sizes are excluded from anti aliasing
https://bugs.kde.org/show_bug.cgi?id=486699 Bug ID: 486699 Summary: KDE font anti-aliasing range exclusion checkbox is fake-on when no font sizes are excluded from anti aliasing Classification: Applications Product: systemsettings Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_fonts Assignee: plasma-b...@kde.org Reporter: littlefroggie...@gmail.com Target Milestone: --- Created attachment 169256 --> https://bugs.kde.org/attachment.cgi?id=169256=edit Font settings panel exhibiting the bug with a red circle around the affected setting. SUMMARY Not sure if this is a duplicate, but I searched and saw no open issues about this specific UI flaw. Title is self-explanatory to an extent. When setting "Exclude range from anti-aliasing" to no in the settings and applying the setting, then quitting the settings app with the close button, and reopening it, that setting will appear on in the GUI, but not actually be on as evidenced by my text being anti-aliased. STEPS TO REPRODUCE 1. Uncheck the exclude range from anti-aliasing checkbox and apply 2. Close settings 3. Open settings OBSERVED RESULT UI is wrong about the aforementioned setting, and displays a checkmark EXPECTED RESULT There is no checkmark, as the setting is disabled. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Graphical platform: Wayland Linux Version: 6.8.7-1-default (64-bit Arm) ADDITIONAL INFORMATION Non-Wayland specific, happens in Xorg too, but was noticed first in Wayland. Issue spotted in a virtualized environment for Apple SIlicon. 200% display scaling set, and native display density set in the hypervisor. Issue also occurs at 100% scaling though. Setting applies if you disable the fake-on checkbox state, click apply, then enable, and apply, at which point the on-state for the checkbox is not a lie. Clearing the checkmark and applying disables the setting, but closing and reopening settings, or relogging the Plasma session will exhibit the UI flaw. I remember this possibly happening in some Plasma 5 version too but no guarantees. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486533] QML SoundEffect Plays choppy from plasmoid in panel when screen is in dpms off.
https://bugs.kde.org/show_bug.cgi?id=486533 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Severity|normal |minor --- Comment #5 from Nate Graham --- Thanks. Cannot reproduce on my laptop when I let the screen turn off. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 486698] New: KDEConnect displays the incorrect language pack
https://bugs.kde.org/show_bug.cgi?id=486698 Bug ID: 486698 Summary: KDEConnect displays the incorrect language pack Classification: Applications Product: kdeconnect Version: 24.02.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: windows-application Assignee: piyushaggarwal...@gmail.com Reporter: bailyka...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install another lanuage pack in windows (For my case, English was default and Korean was install) 2. take note that English should be in the top spot in the list(ie, the selected lanuage) OBSERVED RESULT KDEConnect will display in korean EXPECTED RESULT KDEConnect will display in english SOFTWARE/OS VERSIONS Windows: Windows 11 Enterprise; 22621.3447 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486697] kioworker crashes on opening Dolphin or moving items to Trash
https://bugs.kde.org/show_bug.cgi?id=486697 --- Comment #2 from main.zone4...@fastmail.com --- Also, clicking "Move to trash" on desktop items fails and also crashes kioworker. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486697] kioworker crashes on opening Dolphin or moving items to Trash
https://bugs.kde.org/show_bug.cgi?id=486697 main.zone4...@fastmail.com changed: What|Removed |Added Summary|kioworker crashes on|kioworker crashes on |opening Dolphin |opening Dolphin or moving ||items to Trash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Please provide a simple test file. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462309] Startup Crash at dl-version.c
https://bugs.kde.org/show_bug.cgi?id=462309 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485979] Expose Yolo Resizing Parameter to Improve Face Detection Accuracy
https://bugs.kde.org/show_bug.cgi?id=485979 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485966] Implement freedesktop wallpaper API
https://bugs.kde.org/show_bug.cgi?id=485966 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486697] kioworker crashes on opening Dolphin
https://bugs.kde.org/show_bug.cgi?id=486697 --- Comment #1 from main.zone4...@fastmail.com --- Created attachment 169255 --> https://bugs.kde.org/attachment.cgi?id=169255=edit Crash Handler Information -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486697] New: kioworker crashes on opening Dolphin
https://bugs.kde.org/show_bug.cgi?id=486697
Bug ID: 486697
Summary: kioworker crashes on opening Dolphin
Classification: I don't know
Product: kde
Version: unspecified
Platform: Neon
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: main.zone4...@fastmail.com
Target Milestone: ---
Created attachment 169254
--> https://bugs.kde.org/attachment.cgi?id=169254=edit
Screencast of steps to reproduce
SUMMARY
Upon opening Dolphin, a notification pops up and says "kioworker closed
unexpectly".
I feel this is associated with the Trash folder.
STEPS TO REPRODUCE
Click on the Dolphin launcher
OBSERVED RESULT
Notification shows "kioworker has crashed". Dolphin continues to work.
The notification will show again if I navigate to the trash can.
The trash folder shows "Loading cancelled".
EXPECTED RESULT
Dolphin opens.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE Neon
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
ADDITIONAL INFORMATION
```
~ ❯❯❯ dolphin
ASSERT: "info.origPath[0] == QLatin1Char('/')" in file
./src/kioworkers/trash/trashimpl.cpp, line 782
KCrash: Application 'kioworker' crashing... crashRecursionCounter = 2
KCrash: Application Name = kioworker path =
/usr/lib/x86_64-linux-gnu/libexec/kf6 pid = 929489
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kf6/kioworker trash
local:/run/user/1000/dolphinBwLHne.2.kioworker.socket
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
kf5idletime_wayland: This plugin does not support polling idle time
org.kde.drkonqi.bugzilla: RuntimeException: "Failed to resolve bugzilla
product"
org.kde.drkonqi: "Failed to resolve bugzilla product"
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: An error occurred during write. The worker terminates now.
ASSERT: "info.origPath[0] == QLatin1Char('/')" in file
./src/kioworkers/trash/trashimpl.cpp, line 782
KCrash: Application 'kioworker' crashing... crashRecursionCounter = 2
KCrash: Application Name = kioworker path =
/usr/lib/x86_64-linux-gnu/libexec/kf6 pid = 929772
KCrash: Arguments: /usr/lib/x86_64-linux-gnu/libexec/kf6/kioworker trash
local:/run/user/1000/dolphinFdhGMP.13.kioworker.socket
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
kf5idletime_wayland: This plugin does not support polling idle time
org.kde.drkonqi.bugzilla: RuntimeException: "Failed to resolve bugzilla
product"
org.kde.drkonqi: "Failed to resolve bugzilla product"
kf.kio.core: An error occurred during write. The worker terminates now.
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
QSocketNotifier: Invalid socket 11 and type 'Read', disabling...
```
--
You are receiving this mail because:
You are watching all bug changes.
[Skanlite] [Bug 486696] New: Crash on skanlite startup
https://bugs.kde.org/show_bug.cgi?id=486696 Bug ID: 486696 Summary: Crash on skanlite startup Classification: Applications Product: Skanlite Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: k...@kolivas.org Target Milestone: --- Application: skanlite (23.08.5) Qt Version: 5.15.13 Frameworks Version: 5.115.0 Operating System: Linux 6.8.7 x86_64 Windowing System: X11 Distribution: Ubuntu 24.04 LTS DrKonqi: 5.27.11 [KCrashBackend] -- Information about the crash: Crashes every time on startup. Default packages in use. Any use of scanner appears to cause the same issue (such as starting xsane). Did not crash on Kubuntu 22.04. The crash can be reproduced every time. -- Backtrace: Application: Skanlite (skanlite), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7f31aa44526e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f31aa4288ff in __GI_abort () at ./stdlib/abort.c:79 #9 0x7f31aa0b5f32 in ??? () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #10 0x7f31aa0de310 in _dbus_warn_check_failed () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #11 0x7f31aa0bec1f in dbus_connection_send () at /lib/x86_64-linux-gnu/libdbus-1.so.3 #12 0x7f318a775446 in ??? () at /usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1 #13 0x7f318a7791c3 in ??? () at /usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1 #14 0x7f318a76a7f8 in sane_hpaio_get_devices () at /usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1 #15 0x7f31a95effd2 in sane_dll_get_devices () at /lib/x86_64-linux-gnu/libsane.so.1 #16 0x7f31ab9a6578 in ??? () at /lib/x86_64-linux-gnu/libKSaneCore.so.1 #17 0x7f31aacdb674 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f31aa49ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #19 0x7f31aa529c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 5 (Thread 0x7f31922006c0 (LWP 996779) "Thread (pooled)"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x7f31921ffb00, clockid=0, expected=0, futex_word=0x562d1a210ef0) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x562d1a210ef0, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7f31921ffb00, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f31aa49bc7e in __pthread_cond_wait_common (abstime=0x7f31921ffb00, clockid=1, mutex=0x562d1a210ea0, cond=0x562d1a210ec8) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x562d1a210ec8, mutex=0x562d1a210ea0, abstime=0x7f31921ffb00) at ./nptl/pthread_cond_wait.c:652 #5 0x7f31aace1723 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f31aacdec5d in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f31aacdb674 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31aa49ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #9 0x7f31aa529c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 4 (Thread 0x7f31918006c0 (LWP 996780) "Thread (pooled)"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x7f31917ffb00, clockid=0, expected=0, futex_word=0x562d1a210d80) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x562d1a210d80, expected=expected@entry=0, clockid=clockid@entry=1, abstime=abstime@entry=0x7f31917ffb00, private=private@entry=0) at ./nptl/futex-internal.c:139 #3 0x7f31aa49bc7e in __pthread_cond_wait_common (abstime=0x7f31917ffb00, clockid=1, mutex=0x562d1a210d30, cond=0x562d1a210d58) at ./nptl/pthread_cond_wait.c:503 #4 ___pthread_cond_timedwait64 (cond=0x562d1a210d58, mutex=0x562d1a210d30, abstime=0x7f31917ffb00) at ./nptl/pthread_cond_wait.c:652 #5 0x7f31aace1723 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f31aacdec5d in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f31aacdb674 in ??? () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f31aa49ca94 in start_thread (arg=) at ./nptl/pthread_create.c:447 #9 0x7f31aa529c3c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Thread 3 (Thread 0x7f3190e006c0 (LWP 996781) "Thread (pooled)"): #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x7f3190dffb00, clockid=0, expected=0, futex_word=0x562d1a80a6f0) at ./nptl/futex-internal.c:87 #2
[plasma-pa] [Bug 485787] No output or input devices/applications found
https://bugs.kde.org/show_bug.cgi?id=485787 JohnW changed: What|Removed |Added CC||k...@woltman.com --- Comment #1 from JohnW --- I would like to add that I have experience this issue too. It happens randomly, or at least I've not been able to figure out what causes it. From a fresh boot the plasma-pa shows the same devices that the Sound Settings control panel shows. I have plasma-pa 6.0.4 installed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486695] New: Random plasmashell crashes recently
https://bugs.kde.org/show_bug.cgi?id=486695 Bug ID: 486695 Summary: Random plasmashell crashes recently Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: attila.bi...@gmail.com Target Milestone: 1.0 Application: plasmashell (6.0.4) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-28-generic x86_64 Windowing System: X11 Distribution: KDE neon 6.0 DrKonqi: 6.0.4 [CoredumpBackend] -- Information about the crash: This crash happened after (or while) the system went to sleeep after inactivity. I had open: -vscode -firefox -chrome -dolphin -spotify -konsole I had 2 external monitors attached, but i don't think it's related. The crash can be reproduced sometimes. -- Backtrace: Application: plasmashell (plasmashell), signal: Segmentation fault This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/ Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [New LWP 812128] [New LWP 812129] [New LWP 812192] [New LWP 812130] [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 --no-respawn'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=123934549491648) at ./nptl/pthread_kill.c:44 [Current thread is 1 (Thread 0x70b7c2cc3fc0 (LWP 812128))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x70b7c2cc3fc0 (LWP 812128))] Thread 4 (Thread 0x70b7c1bfe640 (LWP 812130)): #0 0x70b7c6d18bcf in __GI___poll (fds=0x70b7c1bfd928, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x70b7c9f707e2 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x70b7c9f7222c in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x70b7c2c04458 in ?? () from /lib/x86_64-linux-gnu/libQt6XcbQpa.so.6 #4 0x70b7c7783c9d in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #5 0x70b7c6c94ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #6 0x70b7c6d26850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 3 (Thread 0x70b7b91ff640 (LWP 812192)): #0 0x70b7c6d18bcf in __GI___poll (fds=0x5ca204099170, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x70b7c610b1f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x70b7c60b33e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x70b7c7676570 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #4 0x70b7c78a3e3b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #5 0x70b7c77bcf48 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #6 0x70b7c7783c9d in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #7 0x70b7c6c94ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #8 0x70b7c6d26850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 2 (Thread 0x70b7c23ff640 (LWP 812129)): #0 0x70b7c6d18bcf in __GI___poll (fds=0x5ca203f13060, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x70b7c610b1f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x70b7c60b33e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x70b7c7676570 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #4 0x70b7c78a3e3b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #5 0x70b7c77bcf48 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #6 0x70b7c847c50e in ?? () from /lib/x86_64-linux-gnu/libQt6DBus.so.6 #7 0x70b7c7783c9d in ?? () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #8 0x70b7c6c94ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x70b7c6d26850 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 1 (Thread 0x70b7c2cc3fc0 (LWP 812128)): [KCrash Handler] #6 0x70b7c91bd954 in QQuickAccessibleAttached::setRole(QAccessible::Role) () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #7 0x70b7c91b3ee4 in ?? () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #8 0x70b7c11a4496 in ?? () from /lib/x86_64-linux-gnu/libQt6QuickTemplates2.so.6 #9 0x70b7c9164b3a in QQuickTextEdit::componentComplete() () from /lib/x86_64-linux-gnu/libQt6Quick.so.6 #10 0x70b7c11a6ff6 in QQuickTextArea::componentComplete() () from
[KScreen] [Bug 485837] x conf file being changed without confirmation
https://bugs.kde.org/show_bug.cgi?id=485837 --- Comment #2 from Ada --- (In reply to Zamundaaa from comment #1) > KScreen doesn't edit any Xorg config files, it just issues xrandr commands. > The config file changes you see are done by something else It doesn't occur when I disable the kscreen daemon though... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #14 from Kalzi --- (In reply to Zamundaaa from comment #13) > hmm, those outputs looks all correct - kscreen-doctor knows it's in the > small mode, and it's sent to other wayland clients correctly as well. If you > set the correct mode with kscreen-doctor, does that work at least? If not, > can you set a different resolution first and then the correct one? I'm not sure I know how to set it with screen-doctor. Also, this issue only happens on the monitor that is connected via display port, if that helps at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486694] New: Not possible to select emojis with the Wacom Tablet
https://bugs.kde.org/show_bug.cgi?id=486694 Bug ID: 486694 Summary: Not possible to select emojis with the Wacom Tablet Classification: Plasma Product: plasmashell Version: master Platform: Ubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Emoji Selector Assignee: plasma-b...@kde.org Reporter: mika@mika.global Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Not possible to select emojis with the Wacom Tablet STEPS TO REPRODUCE 1. Bring Emoji Selector with Meta+. 2. Try to select an emoji with the Wacom Tablet OBSERVED RESULT The emoji is not being copied to the clipboard EXPECTED RESULT The emoji is copied to the clipboard, and you can see the pop-up indicating it. SOFTWARE/OS VERSIONS 4:5.24.7-0ubuntu0.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #13 from Zamundaaa --- hmm, those outputs looks all correct - kscreen-doctor knows it's in the small mode, and it's sent to other wayland clients correctly as well. If you set the correct mode with kscreen-doctor, does that work at least? If not, can you set a different resolution first and then the correct one? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486693] New: Kwin coredump using Ctrl + Alt + A on discord
https://bugs.kde.org/show_bug.cgi?id=486693 Bug ID: 486693 Summary: Kwin coredump using Ctrl + Alt + A on discord Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: mmboss...@gmail.com Target Milestone: --- SUMMARY I was playing with discord and trying to hope for global shortcuts on wayland, but ended up facing this crash STEPS TO REPRODUCE 1. Run discord in wayland mode (ozone platform + wayland) - this is my full launch for the record discord --enable-features=UseOzonePlatform,WaylandWindowDecorations,VaapiVideoDecoder --ozone-platform=wayland --ignore-gpu-blocklist --use-gl=desktop --enable-gpu-rasterization --enable-zero-copy --disable-gpu-sandbox 2. Discord opens in friends tab 3. Make sure one of the servers have unread messages 4. Open discord settings 5. Ctrl + Alt + A OBSERVED RESULT Kwin crashes EXPECTED RESULT no crashes SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-1-cachyos (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 6750 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A37 System Version: 1.0 ADDITIONAL INFORMATION Stack trace of thread 42406: #0 0x6ffd2bf442b4 _ZN4KWin6Window15cancelAutoRaiseEv (libkwin.s> #1 0x6ffd2be40cc9 _ZN4KWin9Workspace11raiseWindowEPNS_6WindowEb> #2 0x6ffd2bd5e917 _ZN4KWin9Workspace14activateWindowEPNS_6Windo> #3 0x6ffd29797549 n/a (libQt6Core.so.6 + 0x197549) #4 0x6ffd2a0f4087 _ZN7QAction8activateENS_11ActionEventE (libQt> #5 0x6ffd29797549 n/a (libQt6Core.so.6 + 0x197549) #6 0x6ffd2b3f31e0 n/a (libKF6GlobalAccel.so.6 + 0x241e0) #7 0x6ffd2b3f3cc0 n/a (libKF6GlobalAccel.so.6 + 0x24cc0) #8 0x6ffd2a4c408f n/a (libQt6DBus.so.6 + 0x3b08f) #9 0x6ffd29788324 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 +> #10 0x6ffd2a6fbfcb _ZN19QApplicationPrivate13notify_helperEP7QOb> #11 0x6ffd2973daa8 _ZN16QCoreApplication15notifyInternal2EP7QObj> #12 0x6ffd2973de34 _ZN23QCoreApplicationPrivate16sendPostedEvent> #13 0x6ffd298b1abb _ZN20QEventDispatcherUNIX13processEventsE6QFl> #14 0x6ffd2a1c14e2 _ZN23QUnixEventDispatcherQPA13processEventsE6> #15 0x6ffd29745c3e _ZN10QEventLoop4execE6QFlagsINS_17ProcessEven> #16 0x6ffd297416a8 _ZN16QCoreApplication4execEv (libQt6Core.so.6> #17 0x5a49f84a5dee n/a (kwin_wayland + 0x3adee) #18 0x6ffd29041d4a n/a (libc.so.6 + 0x25d4a) #19 0x6ffd29041e0c __libc_start_main (libc.so.6 + 0x25e0c) #20 0x5a49f84abdf5 n/a (kwin_wayland + 0x40df5) Stack trace of thread 42413: #0 0x6ffd290a68d9 n/a (libc.so.6 + 0x8a8d9) #1 0x6ffd290a9299 pthread_cond_wait (libc.so.6 + 0x8d299) #2 0x6ffd20c863fc n/a (radeonsi_dri.so + 0x863fc) #3 0x6ffd20c9ec2c n/a (radeonsi_dri.so + 0x9ec2c) #4 0x6ffd290aa1cf n/a (libc.so.6 + 0x8e1cf) #5 0x6ffd2912b6ec n/a (libc.so.6 + 0x10f6ec) Stack trace of thread 42411: #0 0x6ffd2911d9ed __poll (libc.so.6 + 0x1019ed) #1 0x6ffd2819f306 n/a (libglib-2.0.so.0 + 0xb9306) #2 0x6ffd2813f712 g_main_context_iteration
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #12 from Kalzi --- (In reply to Zamundaaa from comment #9) > (In reply to Michael Butash from comment #4) > > Is it DP output to DP input, or some mode conversion to HDMI? > > > > I have this happen almost clockwork after a suspend awaken, reboot, even > > just a glitch of the power to the dock or something, and seems to come > > largely from having to use DP on dock to HDMI on TV conversion. Often I'll > > see the display after reset come up instead of my Samsung TV's I use to > > display as generic "NVidia 640x480", and is usually all xrandr sees as well, > > indicating like the conversion chip in the cable/adapter glitches and EDID > > data doesn't resolve correctly on the host. I often have to end up > > unplugging physically and resetting the DP end of the cable/adapter to fix > > it. > That's a NVidia driver bug, the proprietary driver has some issues with > reading the EDID sometimes. You can report it at > https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 > > > (In reply to Kalzi from comment #8) > > I have attached three txt files that have the output of drm_info for before, > > during and after > > Okay, so the driver reports the correct mode list, and KWin has actually set > the 640x480 mode. Can you also attach the output of > > kscreen-doctor -o > and > > wayland-info > while the output is wrongly in that 640x480 mode? > > What I suspect is happening is that the driver temporarily reports 640x480 > as the only supported mode at some point after the display goes to standby, > and KWin doesn't automatically switch back to the correct mode (which > shouldn't be very complicated to fix). If the display settings doesn't let > you set the right mode though, there might be more going on attached both. Hope it helps. I still can't change the resolution on the blown out screen, I'd have to find a way to be able to get to the normal screen to change the correct resolution from there -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #11 from Kalzi --- Created attachment 169253 --> https://bugs.kde.org/attachment.cgi?id=169253=edit waylandinfo -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #10 from Kalzi --- Created attachment 169252 --> https://bugs.kde.org/attachment.cgi?id=169252=edit kscreen-doctor-while -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 --- Comment #9 from Natalie Clarius --- Okay, seem reasonable enough. It sounds to be like this use case would be even better addressed by adding support for activating night light based on an ambient light sensor, in addition to the ability to temporarily turn it off manually (eg for watching a video). But that would of course only work on devices that actually have an ambient light sensor. So maybe adding a "Manual mode" makes sense anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486621] Support overscan on Intel
https://bugs.kde.org/show_bug.cgi?id=486621 --- Comment #5 from Zamundaaa --- I checked which properties were supported on Intel, and it seems I misremembered. There are properties for overscan that KWin could still support, but those are for VC4, and the Intel driver doesn't support them. So it'll have to be implemented in software for Intel as well... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 Natalie Clarius changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 --- Comment #11 from Azarilh --- (In reply to Carl Schwan from comment #10) > Considering the crash was occuring with the Qt5 version deep in the QML > engine and Arianna is now ported to Qt6, I'm hoping this bug is now fixed. > > If not please open a new bug report and attach a backtrace (with symbols). Unfortunately i do not have anymore the same system where this problem occured to test it. Good news is that on my new OpenSUSE with Kde Plasma / Qt 6 works from both Flathub and the official repos. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 --- Comment #8 from Natalie Clarius --- Git commit 6ec7e919fb9f7fe80221810da4f7efe6d56ebf4a by Natalie Clarius. Committed on 06/05/2024 at 23:14. Pushed by nclarius into branch 'master'. plugins/nightlight: clarify strings for inhibition To clarify that the toggle action merely temporarily disables the blue light filter, rather than turning the schedule off permanently like the "Disbaled" setting in the KCM does, use "suspend/resume" terminology instead of "off/on" in the keyboard shortcut and OSD. Follow-up on plasma-workspace!4262 M +3-3src/plugins/nightlight/nightlightmanager.cpp https://invent.kde.org/plasma/kwin/-/commit/6ec7e919fb9f7fe80221810da4f7efe6d56ebf4a -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 486658] Spectacle not copying to clipboard
https://bugs.kde.org/show_bug.cgi?id=486658 Noah Davis changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #4 from Noah Davis --- (In reply to Nate Graham from comment #3) > > *** This bug has been marked as a duplicate of bug 485096 *** Sorry Nate, I should have marked this as NEEDSINFO. We don't know for sure if it's a duplicate yet. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 486658] Spectacle not copying to clipboard
https://bugs.kde.org/show_bug.cgi?id=486658 Noah Davis changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468507] Immediate crash
https://bugs.kde.org/show_bug.cgi?id=468507 Carl Schwan changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #10 from Carl Schwan --- Considering the crash was occuring with the Qt5 version deep in the QML engine and Arianna is now ported to Qt6, I'm hoping this bug is now fixed. If not please open a new bug report and attach a backtrace (with symbols). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 --- Comment #7 from Sin Jeong-hun --- I need NL depending on the ambient light and the content I am seeing, not on the time of the day. That is, at the same 10 PM, if the room is bright and I am watching a video, I don't need NL. But if the room is dark and I am reading text, then NL is useful because it reduces the perceived brightness lower than the lowest screen brightness (i.e., many screens lowest brightness is not low enough). In my opinion, the current NL option seems unnecessarily confusing. On Android, I could set "Schedule" to "None", and use the "Use NL" toggle or a Quick Settings toggle to turn it on/off arbitrarily, and if I turn it on/off, it stays in that state even I reboot the phone. Of course, a phone doesn't reboot often, unlike a rolling Linux like Arch. I don't remember exactly, but I think Windows 10 probably also worked like this. Simple on/off without automatic scheduling. The thing I did was setting Plasma's NL to "Always on" (because with "Always off", the shortcut did not work) and used the shortcut to turn it off/on, but the state was not remembered and when I rebooted the PC in a bright room, NL got automatically turned on at the next login. Of course, all I had to do was pressing the shortcut to turn it off, but I thought it was annoying. So, what I think is, any of the following change could be helpful to people who want only manual control, without automatic anything. (1) When NL is set to "Always off", pressing the NL shortcut change it to "Always on", and when it is set to "Always off", the shortcut changes it to "Always off". (2) NL "Switching times" can have a new entry "Manual". The shortcut turns it on/off, and it persists after reboot. (3) When NL is set to "Always on", and the user pressed the NL shortcut to turn it off, the off state persists after reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483246] Notification applet doesn't open after toggling
https://bugs.kde.org/show_bug.cgi?id=483246 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com --- Comment #7 from fanzhuyi...@gmail.com --- FWIW I can't seem to reproduce on master with Qt 6.7 (arch linux). -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468513] Arianna crash when added some books
https://bugs.kde.org/show_bug.cgi?id=468513 Carl Schwan changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #4 from Carl Schwan --- Unfortunately I can't reproduce and without a backtrace there is not much I can do :( -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 485458] Display configuration resets after waking up laptop from suspend
https://bugs.kde.org/show_bug.cgi?id=485458 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||xaver.h...@gmail.com Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 482841] After suspend, disconnect from dock, and resume, kscreenlocker_greet fails to launch with "wl_display@1: error 1: invalid arguments for wl_display@1.get_registry" Wayland
https://bugs.kde.org/show_bug.cgi?id=482841
Nate Graham changed:
What|Removed |Added
Summary|Screenlocker fails |After suspend, disconnect
|(suspend, disconnect from |from dock, and resume,
|dock, resume) |kscreenlocker_greet fails
||to launch with
||"wl_display@1: error 1:
||invalid arguments for
||wl_display@1.get_registry"
||Wayland protocol error
Severity|crash |grave
Keywords||multiscreen, wayland
CC||k...@david-redondo.de,
||k...@davidedmundson.co.uk,
||xaver.h...@gmail.com
--- Comment #5 from Nate Graham ---
Derp, you even mentioned there was no crash, sorry for bad reading
comprehension.
This stuff all looks relevant to me:
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3795669]: qt.qpa.wayland:
eglSwapBuffers failed with 0x300d, surface: 0x0
Mar 29 19:46:27 lenovo-laptop plasmashell[2700339]: kf.windowsystem.wayland:
Failed to recreate shadow for
NotificationPopup_QMLTYPE_395_QML_399(0x55700fb34c40)
Mar 29 19:46:27 lenovo-laptop plasmashell[2700339]: qt.qpa.wayland:
eglSwapBuffers failed with 0x300d, surface: 0x0
Mar 29 19:46:27 lenovo-laptop kernel: kscreenlocker_g[3795669]: segfault at 8
ip 7f552a6b6598 sp 7ffef2fc9d80 error 4 in
libPlasmaQuick.so.6.0.3[7f552a68b000+4c000] likely on CPU 4 (core 2, socket 0)
Mar 29 19:46:27 lenovo-laptop kernel: Code: cc cc 55 48 89 e5 48 8b 47 28 48 8b
40 08 48 8b 40 10 48 8b 40 38 5d c3 cc cc cc cc cc cc cc cc cc cc 55 48 89 e5
48 8b 47 28 <48> 8b 40 08 48 8b 40 10 48 8b 48 10 48 85 c9 74 20 8b 49 04 85 c9
Mar 29 19:46:27 lenovo-laptop kernel: audit: type=1701
audit(1711703787.190:807): auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined
pid=3795669 comm="kscreenlocker_g" exe="/usr/lib64/kf6/kscreenlocker_greet"
sig=11 res=1
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3615]: not a valid new
object id (2), message get_registry(n)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3615]: error in client
communication (pid 3615)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3796335]: error: received
delete_id for unknown id (84)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3796335]: error: received
delete_id for unknown id (77)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3796335]: error: received
delete_id for unknown id (74)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3796335]: error: received
delete_id for unknown id (29)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3796335]: error: received
delete_id for unknown id (28)
Mar 29 19:46:27 lenovo-laptop kwin_wayland_wrapper[3796335]: wl_display@1:
error 1: invalid arguments for wl_display@1.get_registry
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796335]: qt.qpa.wayland:
Loading shell integration failed.
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796335]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796335]: qt.qpa.plugin:
Could not load the Qt platform plugin "wayland" in "" even though it was found.
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796335]: This application
failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.
Mar 29 19:46:27 lenovo-laptop kernel: audit: type=1701
audit(1711703787.341:808): auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined
pid=3796335 comm="kscreenlocker_g" exe="/usr/lib64/kf6/kscreenlocker_greet"
sig=6 res=1
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796360]: qt.qpa.wayland:
Loading shell integration failed.
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796360]: qt.qpa.wayland:
Attempted to load the following shells QList("layer-shell")
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796360]: qt.qpa.plugin:
Could not load the Qt platform plugin "wayland" in "" even though it was found.
Mar 29 19:46:27 lenovo-laptop kscreenlocker_greet[3796360]: This application
failed to start because no Qt platform plugin could be initialized.
Reinstalling the application may fix this problem.
Mar 29 19:46:27 lenovo-laptop kernel: audit: type=1701
audit(1711703787.423:809): auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined
pid=3796360 comm="kscreenlocker_g" exe="/usr/lib64/kf6/kscreenlocker_greet"
sig=6 res=1
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 Natalie Clarius changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 Natalie Clarius changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #6 from Natalie Clarius --- See also https://invent.kde.org/plasma/plasma-workspace/-/issues/114 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/5700 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486560] OSDs display in the top left corner of the screen after Keyboard Layout switcher is used
https://bugs.kde.org/show_bug.cgi?id=486560 --- Comment #5 from Nate Graham --- Also on Fedora 40, cannot reproduce with a single screen driven by an Intel HD620 iGPU. Need to test again with a second screen attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485801] With mixed light/dark themes (e.g. Breeze Twilight) KSvg and Kirigami.Icon use app color scheme rather than Plasma color scheme when given an absolute path
https://bugs.kde.org/show_bug.cgi?id=485801 --- Comment #7 from Nate Graham --- I wonder what the reason for that is. In this use case at least, we want the SVG to be themed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] No way to turn off and on night light manually persistent across reboots
https://bugs.kde.org/show_bug.cgi?id=486647 Natalie Clarius changed: What|Removed |Added Summary|Subpar UX with night light |No way to turn off and on |manually turned on and off |night light manually ||persistent across reboots -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] Subpar UX with night light manually turned on and off
https://bugs.kde.org/show_bug.cgi?id=486647 Natalie Clarius changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Natalie Clarius --- Yes, toggling Night Light with the keyboard shortcut or the switch in applet is only meant to suspend the feature temporarily, it will not persist across boots. Can you further explain your use case for turning on night light only occasionally but persisting across reboots? The idea of the existing toggle (suspend) feature is so you have an easy way to temporarily turn the blue light filter off if you need your screen colors to be neutral for a while e.g. for editing photos when otherwise you do want it on at your preferred times. But in what kinds of situations do you feel like turning on night light on or off at arbitrary times that it would be too annoying to go into the system settings with a click on the "Configure" button in the applet, or press a shortcut to suppress it again after a reboot? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 52665] Support for application/xhtml+xml mimeType
https://bugs.kde.org/show_bug.cgi?id=52665 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443352] Plasma crashed in KIO::UndoCommand::UndoCommand()
https://bugs.kde.org/show_bug.cgi?id=443352 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 152126] konqueror drag and drop to text field
https://bugs.kde.org/show_bug.cgi?id=152126 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 11825] [PATCH] It would be very nice to be able to print selection in konqueror
https://bugs.kde.org/show_bug.cgi?id=11825 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 65602] signed secure applets konqueror
https://bugs.kde.org/show_bug.cgi?id=65602 Bug Janitor Service changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 47320] [testcase] text and background uses colors from KDE color scheme if not specified in the html style
https://bugs.kde.org/show_bug.cgi?id=47320 Bug Janitor Service changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 486494] Crash using KIO::highlightInFileManager in Flatpak app
https://bugs.kde.org/show_bug.cgi?id=486494 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #4 from Nicolas Fella --- Please add a backtrace with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] Subpar UX with night light manually turned on and off
https://bugs.kde.org/show_bug.cgi?id=486647 Nate Graham changed: What|Removed |Added Severity|wishlist|minor Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] Subpar UX with night light manually turned on and off
https://bugs.kde.org/show_bug.cgi?id=486647 Nate Graham changed: What|Removed |Added Summary|Can't turn on/off Night |Subpar UX with night light |Light with shortcut when|manually turned on and off |Night Light is "Always | |Off". | Keywords||usability Resolution|NOT A BUG |--- Status|RESOLVED|REPORTED --- Comment #3 from Nate Graham --- That makes sense; probably the current on/off status when using the shortcut is only saved in memory, not to disk. Re-opening since maybe there's more we should do to support this use case. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 486436] Saving attachment to webdavs folder crashes kontact
https://bugs.kde.org/show_bug.cgi?id=486436 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- #0 0x7f1786a949ec __pthread_kill_implementation (libc.so.6 + 0x949ec) #1 0x7f1786a41176 raise (libc.so.6 + 0x41176) #2 0x7f1788ea8be3 _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x6be3) #3 0x7f1786a41240 __restore_rt (libc.so.6 + 0x41240) #4 0x7f1765670871 _ZNK5KMime7Headers4Base2isEPKc (libKPim6Mime.so.6 + 0x35871) #5 0x7f17656708d7 _ZNK5KMime7Content12headerByTypeEPKc (libKPim6Mime.so.6 + 0x358d7) #6 0x7f176567384a _ZN5KMime7Content23contentTransferEncodingEb (libKPim6Mime.so.6 + 0x3884a) #7 0x7f17656738de _ZN5KMime7Content14decodedContentEv (libKPim6Mime.so.6 + 0x388de) #8 0x7f1747548608 n/a (libKPim6MessageViewer.so.6 + 0x135608) #9 0x7f174750d99c n/a (libKPim6MessageViewer.so.6 + 0xfa99c) #10 0x7f17873e8443 n/a (libQt6Core.so.6 + 0x1e8443) #11 0x7f1787f389a2 _ZN7QAction9triggeredEb (libQt6Gui.so.6 + 0x5389a2) #12 0x7f1787f3b594 _ZN7QAction8activateENS_11ActionEventE (libQt6Gui.so.6 + 0x53b594) #13 0x7f178876942c n/a (libQt6Widgets.so.6 + 0x36942c) #14 0x7f178876cf49 n/a (libQt6Widgets.so.6 + 0x36cf49) #15 0x7f178860e6a4 _ZN7QWidget5eventEP6QEvent (libQt6Widgets.so.6 + 0x20e6a4) #16 0x7f17885c2f1e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c2f1e) #17 0x7f17885c6b37 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c6b37) #18 0x7f178738f030 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x18f030) #19 0x7f17885c2698 _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb (libQt6Widgets.so.6 + 0x1c2698) #20 0x7f1788621541 n/a (libQt6Widgets.so.6 + 0x221541) #21 0x7f1788624245 n/a (libQt6Widgets.so.6 + 0x224245) #22 0x7f17885c2f1e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c2f1e) #23 0x7f178738f030 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x18f030) #24 0x7f1787bf034b _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE (libQt6Gui.so.6 + 0x1f034b) #25 0x7f1787c4c05c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x24c05c) #26 0x7f17700e4d5a n/a (libQt6XcbQpa.so.6 + 0x60d5a) #27 0x7f177b85b710 n/a (libglib-2.0.so.0 + 0x5d710) #28 0x7f177b85d358 n/a (libglib-2.0.so.0 + 0x5f358) #29 0x7f177b85da0c g_main_context_iteration (libglib-2.0.so.0 + 0x5fa0c) #30 0x7f17875c0a8c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3c0a8c) #31 0x7f178739979b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x19979b) #32 0x7f178876eb9f n/a (libQt6Widgets.so.6 + 0x36eb9f) #33 0x7f178876ecbf _ZN5QMenu4execERK6QPointP7QAction (libQt6Widgets.so.6 + 0x36ecbf) #34 0x7f17474fbce4 n/a (libKPim6MessageViewer.so.6 + 0xe8ce4) #35 0x7f1747513330 n/a (libKPim6MessageViewer.so.6 + 0x100330) #36 0x7f17475048fa n/a (libKPim6MessageViewer.so.6 + 0xf18fa) #37 0x7f17873e8443 n/a (libQt6Core.so.6 + 0x1e8443) #38 0x7f17474ddbd5 _ZN13MessageViewer17MailWebEngineView9popupMenuERKN15WebEngineViewer16WebHitTestResultE (libKPim6MessageViewer.so.6 + 0xcabd5) #39 0x7f17873e8443 n/a (libQt6Core.so.6 + 0x1e8443) #40 0x7f1746a7ec12 _ZN15WebEngineViewer10WebHitTest8finishedERKNS_16WebHitTestResultE (libKPim6WebEngineViewer.so.6 + 0x2cc12) #41 0x7f1746a8158c n/a (libKPim6WebEngineViewer.so.6 + 0x2f58c) #42 0x7f1780732896 _ZN21QWebEnginePagePrivate16didRunJavaScriptEyRK8QVariant (libQt6WebEngineCore.so.6 + 0x4b32896) #43 0x7f177c7e79db n/a (libQt6WebEngineCore.so.6 + 0xbe79db) #44 0x7f177c7db592 n/a (libQt6WebEngineCore.so.6 + 0xbdb592) #45 0x7f177eaadc42 n/a (libQt6WebEngineCore.so.6 + 0x2eadc42) #46 0x7f178100618b n/a (libQt6WebEngineCore.so.6 + 0x540618b) #47 0x7f1781006ade n/a (libQt6WebEngineCore.so.6 + 0x5406ade) #48 0x7f178100544e n/a (libQt6WebEngineCore.so.6 + 0x540544e) #49 0x7f178126ddf2 n/a (libQt6WebEngineCore.so.6 + 0x566ddf2) #50 0x7f178126aab9 n/a (libQt6WebEngineCore.so.6 + 0x566aab9) #51 0x7f17807c2e06 n/a (libQt6WebEngineCore.so.6 + 0x4bc2e06) #52 0x7f17807df3a3 n/a (libQt6WebEngineCore.so.6 + 0x4bdf3a3) #53 0x7f17807dfdbe n/a (libQt6WebEngineCore.so.6 + 0x4bdfdbe) #54 0x7f177c71dbdb n/a (libQt6WebEngineCore.so.6 + 0xb1dbdb) #55 0x7f17873d2246 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1d2246) #56 0x7f17885c2f1e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c2f1e) #57
[kontact] [Bug 486692] New: Two Kontact windows after quitting Kontact with a Composer window open
https://bugs.kde.org/show_bug.cgi?id=486692 Bug ID: 486692 Summary: Two Kontact windows after quitting Kontact with a Composer window open Classification: Applications Product: kontact Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: groszdaniel...@gmail.com Target Milestone: --- SUMMARY If I quit Kontact while composing an e-mail, then after starting Kontact again, two mail Kontact windows appear, and two composer windows for each one that was open before quitting Kontact. The windows mostly behave normally, but e-mails don't show up in one of the main windows. The way to exit this state is to close all the Composer windows first, then quit both main windows (at that point Kontact segfaults), then start Kontact again. After that, Kontact behaves normally. STEPS TO REPRODUCE 1. Start a new e-mail in the Mail component of Kontact, or reply to an e-mail. Optionally make some changes in the e-mail, though it doesn't seem to be needed. 2. Quit Kontact, for instance with Ctrl+Q in the main window. 3. Start Kontact again. OBSERVED RESULT Two main Kontact windows, and two Composer windows. EXPECTED RESULT One main Kontact window, and one Composer window with the e-mail I started writing. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240503 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #9 from Zamundaaa --- (In reply to Michael Butash from comment #4) > Is it DP output to DP input, or some mode conversion to HDMI? > > I have this happen almost clockwork after a suspend awaken, reboot, even > just a glitch of the power to the dock or something, and seems to come > largely from having to use DP on dock to HDMI on TV conversion. Often I'll > see the display after reset come up instead of my Samsung TV's I use to > display as generic "NVidia 640x480", and is usually all xrandr sees as well, > indicating like the conversion chip in the cable/adapter glitches and EDID > data doesn't resolve correctly on the host. I often have to end up > unplugging physically and resetting the DP end of the cable/adapter to fix > it. That's a NVidia driver bug, the proprietary driver has some issues with reading the EDID sometimes. You can report it at https://forums.developer.nvidia.com/c/gpu-graphics/linux/148 (In reply to Kalzi from comment #8) > I have attached three txt files that have the output of drm_info for before, > during and after Okay, so the driver reports the correct mode list, and KWin has actually set the 640x480 mode. Can you also attach the output of > kscreen-doctor -o and > wayland-info while the output is wrongly in that 640x480 mode? What I suspect is happening is that the driver temporarily reports 640x480 as the only supported mode at some point after the display goes to standby, and KWin doesn't automatically switch back to the correct mode (which shouldn't be very complicated to fix). If the display settings doesn't let you set the right mode though, there might be more going on -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] Can't turn on/off Night Light with shortcut when Night Light is "Always Off".
https://bugs.kde.org/show_bug.cgi?id=486647 --- Comment #2 from Sin Jeong-hun --- (In reply to Nate Graham from comment #1) > "Always Off" in fact means the feature is disabled entirely. The way to > achieve your desired usage mode is to turn it on and then you can use the > shortcuts to disable or enable it as needed. > > Did I get that right, Natalie? Actually, I had tried that but even when I "turned it off" NL with the shortcut, every time I rebooted, NL was turned on by default. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486647] Can't turn on/off Night Light with shortcut when Night Light is "Always Off".
https://bugs.kde.org/show_bug.cgi?id=486647 Nate Graham changed: What|Removed |Added CC||kwin-bugs-n...@kde.org, ||natalie_clar...@yahoo.de, ||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG Component|kcm_keys|kcm_nightcolor --- Comment #1 from Nate Graham --- "Always Off" in fact means the feature is disabled entirely. The way to achieve your desired usage mode is to turn it on and then you can use the shortcuts to disable or enable it as needed. Did I get that right, Natalie? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486646] Wrong tooltip text in kcms/desktoppaths/ui/main.qml
https://bugs.kde.org/show_bug.cgi?id=486646 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||1a8e026bb1bf303b4b46d33a8ab ||34a1ae1f64033 Version Fixed In||6.1 --- Comment #2 from Nate Graham --- Git commit 1a8e026bb1bf303b4b46d33a8ab34a1ae1f64033 by Nate Graham. Committed on 06/05/2024 at 22:10. Pushed by ngraham into branch 'master'. kcms/desktoppaths: correct wrong tooltip for Public folder Looks like a copy-paste error. FIXED-IN: 6.1 M +1-1kcms/desktoppaths/ui/main.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/1a8e026bb1bf303b4b46d33a8ab34a1ae1f64033 -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 486576] Cannot log into Google account with two factor authentication enabled
https://bugs.kde.org/show_bug.cgi?id=486576 --- Comment #3 from Edmund Laugasson --- This is possibly another issue but with that non-2FA account, where I could log in - there I could create a folder via Dolphin but could not create a file directly in Google Drive via Dolphin or upload any file form computer. Even it shows file is uploaded, the file is not visible in Dolphin (even with refresh, also with CTRL+F5) and also in web interface of Google Drive there is no file uploaded. I tried to upload *.odt file. But tried with *.txt and then succeeded to upload. If only *.txt is allowed, then this is very limited :( -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 486691] New: Content Warnings Are Not Preserved Upon Reply
https://bugs.kde.org/show_bug.cgi?id=486691 Bug ID: 486691 Summary: Content Warnings Are Not Preserved Upon Reply Classification: Applications Product: Tokodon Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: manif...@mindmesh.link CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Replying to posts does not leave the same content warning as the parent post - in fact, even if I manually turn on the CW field, it does not autofill the CW from the thread. STEPS TO REPRODUCE 1. Click reply on a post with a content warning OBSERVED RESULT Content warning is not inherited from replied-to post. EXPECTED RESULT Content warning should be inherited, at least optionally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: NixOS 23.11 (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION This one's not a bug, more an opinionated default - but it's a default that goes against the current Mastodon web UI, Tusky, Semaphore/Pinafore, and I'm sure many other clients, so at the least, an option would be good for it. It's expected behavior, and socially, many people bristle at having the warnings accidentally removed from their posts, which an unsuspecting Tokodon user might not know about, causing undue social friction. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486646] Wrong tooltip text in kcms/desktoppaths/ui/main.qml
https://bugs.kde.org/show_bug.cgi?id=486646 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Component|general |kcm_desktoppath Product|plasmashell |systemsettings Target Milestone|1.0 |--- CC||n...@kde.org Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- You're right! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 486652] ToolBarLayout shows all actions as they are loaded before collapsing them
https://bugs.kde.org/show_bug.cgi?id=486652 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486654] When restoring tabs in Microsoft Edge flatpak, the mouse leaves a trail across the screen
https://bugs.kde.org/show_bug.cgi?id=486654 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486655] Panel/dock set to fit content, align center, floating and auto-hiding will start up being too long in Wayland
https://bugs.kde.org/show_bug.cgi?id=486655 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484216] System Tray popups close immediately when opened when using a bottom or right screen edge panel and "Application" or "Window" keyboard layout switching mode
https://bugs.kde.org/show_bug.cgi?id=484216 Nate Graham changed: What|Removed |Added CC||beaux_mo...@tut.by --- Comment #18 from Nate Graham --- *** Bug 486661 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484216] System Tray popups close immediately when opened when using a bottom or right screen edge panel and "Application" or "Window" keyboard layout switching mode
https://bugs.kde.org/show_bug.cgi?id=484216 Nate Graham changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486661] Different languages selection (e.g., per application option is chosen) prevents the plasmoids to be opened
https://bugs.kde.org/show_bug.cgi?id=486661 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 484216 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486657] volume decreases when mixer popup hides
https://bugs.kde.org/show_bug.cgi?id=486657 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 485096] When default screenshot format is JPEG, screenshots copied to the clipboard cannot be pasted until Spectacle quits
https://bugs.kde.org/show_bug.cgi?id=485096 Nate Graham changed: What|Removed |Added CC||izerpi...@gmail.com --- Comment #4 from Nate Graham --- *** Bug 486658 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 486658] Spectacle not copying to clipboard
https://bugs.kde.org/show_bug.cgi?id=486658 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 485096 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486664] Some translations on the Breeze-themed SDDM theme are not used
https://bugs.kde.org/show_bug.cgi?id=486664 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||visual-des...@kde.org Product|kscreenlocker |plasmashell Version|git-master |6.0.4 Component|general |Theme - Breeze Target Milestone|--- |1.0 Summary|Some translations are not |Some translations on the |used|Breeze-themed SDDM theme ||are not used --- Comment #1 from Nate Graham --- Since this code is displayed by SDDM, the translations have to live in SDDM itself IIRC. Is that where you were checking? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486665] Plasmashell crashes randomly
https://bugs.kde.org/show_bug.cgi?id=486665 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |BACKTRACE Platform|unspecified |Arch Linux --- Comment #1 from Nate Graham --- Cannot reproduce, no KDE code is implicated in what I can see from the backtrace, and the backtrace has no debug symbols for anything that would help. :( If this crash is reproducible, could you please install debug symbols, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486337] Plasmashell crashes in MapProxySource::item
https://bugs.kde.org/show_bug.cgi?id=486337 Nicolas Fella changed: What|Removed |Added Summary|Plasmashell crash when |Plasmashell crashes in |xwayland apps are open |MapProxySource::item Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- The backtrace indicates that it's crashing in system stats code and has likely nothing to do with XWayland window. Unfortunately it's missing debug symbols, so it's not clear what exactly is happening. Can you please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports to get a backtrace with debug symbols? -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 486576] Cannot log into Google account with two factor authentication enabled
https://bugs.kde.org/show_bug.cgi?id=486576 Edmund Laugasson changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Status|NEEDSINFO |REOPENED --- Comment #2 from Edmund Laugasson --- (In reply to Justin Zobel from comment #1) > By two factor authentication do you mean a One Time Password or the > authentication that's done via a device such as a phone where it prompts you > to confirm that it is you signing in? via device > I've just been able to add my Google Account to Online Accounts using the > second method. To be honest, Online Accounts does not even reach to second factor. The error message, which screenshot I added, will appear right after email is entered and Next clicked. I do frequent, usually every day updates and tried again after fresh updates (which didn't update any KDE part) and still same issue. Although I use 24.02.2 version (https://archlinux.org/packages/extra/x86_64/kio-gdrive/), there is 24.04.80 waiting in KDE unstable (https://archlinux.org/packages/kde-unstable/x86_64/kio-gdrive/). Reason is here - https://support.google.com/accounts/answer/185833?hl=en If you’ve set up 2-Step Verification but can’t find the option to add an app password, it might be because: Your Google Account has 2-Step Verification set up only for security keys. You’re logged into a work, school, or another organization account. Your Google Account has Advanced Protection. Advanced Protection https://support.google.com/accounts/answer/7539956 With 2-Step Verification, the second step could be a: Prompt sent to your phone Verification code Security key I'm using Prompt and Verification code. Also there is written: Also, Advanced Protection limits third-party app access to your data, puts stronger checks on suspicious downloads, and tightens account recovery security to help prevent unauthorized access. This is the case. This Advanced Protection is very common - widely used and this does not allow to create app password e.g. for KDE Online Accounts. I have also another GMail account, which does not have 2FA enabled and there I could reach to password field and could log in and add account. Even it required for security reasons SMS-confirmation and sent me SMS and I could even enter confirmation code and it logged in. But no 2FA is enabled with that account. But with account, where 2FA is enabled, I cannot login. Although I have 14 third party app enabled and in that sense I'm using already that 2FA enabled Google account with 3rd party apps like KDE Online Accounts also is as I see under that non-2FA Google account, where I could log in. With that experiment I showed clearly, that 2FA is preventing to use KDE Online Accounts. Also as referred upwards, Google itself confirms, that when Advanced Protection by 2FA (Prompt sent to your phone, Verification code) is enabled, then Advanced Protection limits third-party app access to your data, puts stronger checks on suspicious downloads, and tightens account recovery security to help prevent unauthorized access. So, I experience that limitation as I don't see any way to allow KDE Online Accounts to be used while 2FA (Advanced Protection) is enabled. OAuth2 seems to be in use - https://developers.google.com/identity/account-linking/oauth-linking Why do you change importance to normal when this issue is still critical as there is not possible to log in? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486674] Links on the desktop disappear after changing their path until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=486674 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Severity|normal |major CC||n...@kde.org Summary|Links on the desktop|Links on the desktop |disappear after changing|disappear after changing |their path |their path until ||plasmashell is restarted Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Can reproduce. It's still in the ~/Desktop folder, but it does disappear from Folder View. Restarting Plasma makes it reappear -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 486690] New: Font Settings Apply To Limited Elements
https://bugs.kde.org/show_bug.cgi?id=486690 Bug ID: 486690 Summary: Font Settings Apply To Limited Elements Classification: Applications Product: Tokodon Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: manif...@mindmesh.link CC: c...@carlschwan.eu, j...@redstrate.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Content Font setting only applies to things like usernames and display names on posts, but not (ironically) any post content, let alone wider UI changes. This is a bit of an accessibility issue, and it would be incredibly nice to be able to adjust the post body text. STEPS TO REPRODUCE 1. Go to settings. 2. Change Content Font. 3. Observe. OBSERVED RESULT Content Font changes only usernames and headers and such. EXPECTED RESULT Content Font changes the font size of post text (or an additional option is provided to separately change this). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: NixOS 23.11 (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486678] some --user flatpaks have the author name as name instead
https://bugs.kde.org/show_bug.cgi?id=486678 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #2 from Nate Graham --- This is unfortunately a bug in Flatpak itself. You can see the same thing in `flatpak list` run in a terminal window. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486687] Applying autologin breaks SDDM solid color as background
https://bugs.kde.org/show_bug.cgi?id=486687 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 --- Comment #1 from Nate Graham --- Huh, I didn't know SDDM supported solid colors like that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483246] Notification applet doesn't open after toggling
https://bugs.kde.org/show_bug.cgi?id=483246 ratijas changed: What|Removed |Added CC||m...@ratijas.tk Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #6 from ratijas --- Can confirm the bug on master. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 198473] wish: add a KIO job progress for file uploads
https://bugs.kde.org/show_bug.cgi?id=198473 Christoph Cullmann changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #1 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 111344] Fixing spelling errors in KHTML forms is unfriendly
https://bugs.kde.org/show_bug.cgi?id=111344 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #10 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 108332] CSS applied to s in are not applied
https://bugs.kde.org/show_bug.cgi?id=108332 Christoph Cullmann changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #3 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486325] Crash right after unlocking
https://bugs.kde.org/show_bug.cgi?id=486325 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 443352 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443352] Plasma crashed in KIO::UndoCommand::UndoCommand()
https://bugs.kde.org/show_bug.cgi?id=443352 Nicolas Fella changed: What|Removed |Added CC||ede...@gmail.com --- Comment #8 from Nicolas Fella --- *** Bug 486325 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486341] Edit Bookmarks menu item does nothing
https://bugs.kde.org/show_bug.cgi?id=486341 --- Comment #13 from caulier.gil...@gmail.com --- Git commit 747bbe9204c0f509761e8fa35ecc142c60a9a44f by Gilles Caulier. Committed on 06/05/2024 at 21:42. Pushed by cgilles into branch 'master'. set dialog modal M +3-0core/utilities/geolocation/geoiface/bookmark/bookmarksdlg.cpp https://invent.kde.org/graphics/digikam/-/commit/747bbe9204c0f509761e8fa35ecc142c60a9a44f -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486468] Amarok 2.9.71 crashes at startup on Fedora 40
https://bugs.kde.org/show_bug.cgi?id=486468 --- Comment #6 from Tuomas Nurmi --- Ok, I installed Fedora 40 in VirtualBox. Installed Amarok 2.9.71 from default installation source. Tried starting it: No crash, I was able to play music normally. Phonon-vlc backend (Qt5) seemed to be in use. I'm not that familiar with pipewire, but I figured I could try starting wireplumber. That caused Amarok to get stuck during startup, although didn't crash (and that seemed to make everything else using sound get stuck during startup, too). Was fixed after a reboot. Tried installing Helvum. Amarok was displayed there as connected to output channels, everything looked quite normal. No success in finding the root cause of the crash yet. A useful note: To get proper debugging output from `amarok --debug` on Fedora, one should edit /usr/share/qt5/qtlogging.ini to read something like [Rules] *.debug=true qt.qpa.xcb.xcberror.warning=false qt.*=false kf.*=false -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486633] Crash on plasmashell --replace
https://bugs.kde.org/show_bug.cgi?id=486633 Nate Graham changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Nate Graham --- Ok, fair enough. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 65602] signed secure applets konqueror
https://bugs.kde.org/show_bug.cgi?id=65602 --- Comment #21 from johnelliottmar...@gmail.com --- wow, that was 21 years ago! > On May 6, 2024, at 2:05 PM, Christoph Cullmann > wrote: > > https://bugs.kde.org/show_bug.cgi?id=65602 > > Christoph Cullmann changed: > > What|Removed |Added > > Status|CONFIRMED |RESOLVED > Resolution|--- |UNMAINTAINED > > --- Comment #20 from Christoph Cullmann --- > Dear user, > > KHTML (and KJS and all related Java/plugin infrastructure) was a long time > more > or less unmaintained and got removed in KF6. > > Please migrate to use a QWebEngine based HTML component. > > We will do no further fixes or improvements to the KF5 branches of these > components beside important security fixes. > > For security issues, please see: > > https://kde.org/info/security/ > > Sorry that we did not fix this issue during the life-time of KHTML. > > Greetings > Christoph Cullmann > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 245532] [CSS] floating a element destroys the list item marker
https://bugs.kde.org/show_bug.cgi?id=245532 Christoph Cullmann changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #4 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 --- Comment #34 from Ilya Fedin --- Nate, it's in 6.7.1 (not in 6.7.0!) and it's easy to get that by copying the commit hash from gerrit and opening it on github (https://github.com/qt/qtbase/commit/). It shows the branches and tags the commit is on but only tags (starting with v) are really relevant. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486341] Edit Bookmarks menu item does nothing
https://bugs.kde.org/show_bug.cgi?id=486341 --- Comment #12 from caulier.gil...@gmail.com --- changing the edit bookmark dialog parent to active windows do not fix the problem -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 483782] Kmail Message list does not show anything in "Date" column (migration from 5.x broken
https://bugs.kde.org/show_bug.cgi?id=483782 Grósz Dániel changed: What|Removed |Added Summary|Kmail Message list does not |Kmail Message list does not |show anything in "Date" |show anything in "Date" |column |column (migration from 5.x ||broken -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 478549] Nerd fonts are not rendered on plasma 6 when using detached font
https://bugs.kde.org/show_bug.cgi?id=478549 --- Comment #33 from HE7086 --- (In reply to Nate Graham from comment #31) > If someone could figure out which exact versions of Qt it landed in, that > would be amazing. I don't know how to get that information myself. The problem was introduced in commit fc33fea999365c36ed446eee0db0d59d94be306b, and is present in: 6.6.0 ~ 6.6.3; 6.7.0 ~ 6.7.1 And the commit that revert it is 4913511d3bf8ec7838f80fbfe92c0fe900b2f003, which at the moment is only present in dev branch. P.S. you can quickly check this by `git branch --all --contains=fc33fea999365c36ed446eee0db0d59d94be306b` -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 114415] "Print this image" option is in the wrong place
https://bugs.kde.org/show_bug.cgi?id=114415 Christoph Cullmann changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UNMAINTAINED --- Comment #3 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 108197] Provide right-click context menu for form submission buttons
https://bugs.kde.org/show_bug.cgi?id=108197 Christoph Cullmann changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #5 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 170057] arrow keys at the dead ends of textual widgets causes main view to scroll (regression)
https://bugs.kde.org/show_bug.cgi?id=170057 Christoph Cullmann changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #9 from Christoph Cullmann --- Dear user, KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6. Please migrate to use a QWebEngine based HTML component. We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes. For security issues, please see: https://kde.org/info/security/ Sorry that we did not fix this issue during the life-time of KHTML. Greetings Christoph Cullmann -- You are receiving this mail because: You are watching all bug changes.
