[yakuake] [Bug 488467] Yakuake does not retain screen setting choice after screen power save event. Always reverts to Screen 2
https://bugs.kde.org/show_bug.cgi?id=488467 b2cc changed: What|Removed |Added CC||b...@dest-unreachable.net --- Comment #3 from b2cc --- I have the same issue since upgrading to Plasma 6.2. I have a triple display setup, with yakuake configured to use the right-most screen. After every restart it seems yakuake just chooses a random screen, and the ID of the right-most screen is also varying (e.g. I can't tell if the right-most screen will be on ID 1, 2 or 3, it's just trial and error). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489959] New: Plasma 6.1 wayland - screen sharing in Chrome and apps (e.g. Slack) is flickering
https://bugs.kde.org/show_bug.cgi?id=489959 Bug ID: 489959 Summary: Plasma 6.1 wayland - screen sharing in Chrome and apps (e.g. Slack) is flickering Classification: Plasma Product: kwin Version: 6.1.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: b...@dest-unreachable.net Target Milestone: --- SUMMARY Since Plasma 6.1 (Nvidia/Wayland), whenever I share my screen with a Chrome/Electron based app (e.g. Slack), the screen sharing is flickering wildly for the viewers whenever the cursor is moved, making screen sharing very difficult. This was working correctly in Plasma 6.0, and only started to show in Plasma 6.1 A similar bug was reported here: * https://forum.manjaro.org/t/kde-wayland-6-1-broke-chromium-screen-sharing-lag/164552 STEPS TO REPRODUCE 1. Open Chrome or Slack 2. Share screen 3. Observe flickering EXPECTED RESULT 1. Screen sharing doesn't flicker for viewers SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3 Qt Version: 6.7.2 NVIDIA drivers: 555.58.02 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")
https://bugs.kde.org/show_bug.cgi?id=440397 --- Comment #14 from b2cc --- Ok, since yesterday, after some package+kernel updates, I don't have this specific behavior anymore. But now I have a different issue where KDE kind-of starts, but then shows a black screen with a mouse cursor. If I move the mouse the whole screen flickers and looks like as if mouse-trail was active. wayland-session.log gets spammed with a never ending stream of EDID messages (~200MB after a minute or so) until I kill the session. Is this a known issue in multi-display (I have three displays) setups with Nvidia? Or should I open a new bug for this? I tried to search through the wayland bugs, but there are so many that I couldn't find one that resembles this error. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")
https://bugs.kde.org/show_bug.cgi?id=440397 --- Comment #13 from b2cc --- (In reply to b2cc from comment #12) This happens with an empty/fresh user directory, completely unconfigured KDE. I'm on Gentoo and the install is from the ebuilds from the KDE overlay: https://anongit.gentoo.org/git/proj/kde.git -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440397] Plasma fails to launch with Wayland and NVidia (kwin_scene_opengl: Creating the OpenGL rendering failed: "query surface failed")
https://bugs.kde.org/show_bug.cgi?id=440397
b2cc changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO |---
CC||b...@dest-unreachable.net
Status|RESOLVED|REOPENED
--- Comment #12 from b2cc ---
I have the same issue on KDE 5.27.5.
I can't start a plasma-wayland session, it crashes immediately and then I'm
back on the login screen.
wayland-session.log:
--
org.kde.startup: not a reply org.freedesktop.locale1 QDBusMessage(type=Error,
service="org.freedesktop.DBus", error
name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name
org.freedesktop.locale1 was not provided by any .service files", signature="s",
contents=("The name org.freedesktop.locale1 was not provided by any .service
files") )
QIODevice::read (QFile, "/home/david/.config/kdedefaults/package"): device not
open
kf.service.services: The desktop entry file
"/usr/share/applications/qemu.desktop" has Type= "Application" but no Exec line
kf.service.sycoca: Invalid Service : "/usr/share/applications/qemu.desktop"
kf.service.services: The desktop entry file
"/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type=
"Application" but no Exec line
kf.service.sycoca: Invalid Service :
"/usr/share/applications/org.freedesktop.Xwayland.desktop"
QDBusConnection: error: could not send signal to service "" path
"//home/david/.config/kdedefaults/kdeglobals" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//home/david/.config/kdedefaults/kdeglobals
QDBusConnection: error: could not send signal to service "" path
"//home/david/.config/kdedefaults/kdeglobals" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//home/david/.config/kdedefaults/kdeglobals
QDBusConnection: error: could not send signal to service "" path
"//home/david/.config/kdedefaults/kdeglobals" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//home/david/.config/kdedefaults/kdeglobals
QDBusConnection: error: could not send signal to service "" path
"//home/david/.config/kdedefaults/kcminputrc" interface
"org.kde.kconfig.notify" member "ConfigChanged": Invalid object path:
//home/david/.config/kdedefaults/kcminputrc
QDBusConnection: error: could not send signal to service "" path
"//home/david/.config/kdedefaults/kwinrc" interface "org.kde.kconfig.notify"
member "ConfigChanged": Invalid object path:
//home/david/.config/kdedefaults/kwinrc
QDBusConnection: error: could not send signal to service "" path
"//home/david/.config/kdedefaults/kwinrc" interface "org.kde.kconfig.notify"
member "ConfigChanged": Invalid object path:
//home/david/.config/kdedefaults/kwinrc
No protocol specified
/usr/bin/xrdb: Resource temporarily unavailable
/usr/bin/xrdb: Can't open display ':0'
QPixmap: QGuiApplication must be created before calling defaultDepth().
QPixmap: QGuiApplication must be created before calling defaultDepth().
dbus-daemon[6557]: [session uid=1001 pid=6557] Activating service
name='org.kde.KSplash' requested by ':1.0' (uid=1001 pid=6558
comm="/usr/bin/startplasma-wayland")
dbus-daemon[6557]: [session uid=1001 pid=6557] Activating service
name='org.freedesktop.portal.Desktop' requested by ':1.4' (uid=1001 pid=10021
comm="/usr/bin/ksplashqml")
dbus-daemon[6557]: [session uid=1001 pid=6557] Activating service
name='org.freedesktop.portal.Documents' requested by ':1.5' (uid=1001 pid=10028
comm="/usr/libexec/xdg-desktop-portal")
kdeinit5: preparing to launch '/usr/lib64/libexec/kf5/klauncher'
kdeinit5: Launched KLauncher, pid = 10037, result = 0
dbus-daemon[6557]: [session uid=1001 pid=6557] Activating service
name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.6'
(uid=1001 pid=10034 comm="/usr/libexec/xdg-document-portal")
dbus-daemon[6557]: [session uid=1001 pid=6557] Successfully activated service
'org.freedesktop.impl.portal.PermissionStore'
dbus-daemon[6557]: [session uid=1001 pid=6557] Successfully activated service
'org.freedesktop.portal.Documents'
** (/usr/libexec/xdg-desktop-portal:10028): WARNING **: 19:30:15.975: Failed to
load RealtimeKit property:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.freedesktop.Realtime
[KScreen] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 --- Comment #11 from b2cc --- Also I just noticed that other crashdumps have been generated too - if you need a backtrace from any of them please let me know: Crashdumps: --- core-gmenudbusmenupr.7591.1668952110 core-kaccess.6867.1668952110 core-kactivitymanage.8020.1668952110 core-kded5.16071.1668952111 core-kded5.5994.1668952111 core-kglobalaccel5.16068.1668952111 core-kglobalaccel5.6028.1668952111 core-klauncher.5449.1668952110 core-kscreen_osd_ser.15892.1668952110 core-ksmserver.6056.1668952110 core-kwalletd5.5008.1668952110 core-org_kde_powerde.16069.1668952111 core-org_kde_powerde.6870.1668952111 core-plasmashell.6869.1668952111 core-xembedsniproxy.6871.1668952110 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 --- Comment #10 from b2cc --- Additionally I see this in dmesg: Nov 20 14:48:30 born2chill kernel: [ 26.072392][T13609] kscreen_backend[13609]: segfault at 8 ip 7f984582141d sp 7ffe7adeb450 error 4 in KSC_XRandR.so[7f984581e000+19000] Nov 20 14:48:30 born2chill kernel: [ 26.072407][T13609] Code: 00 00 00 4c 8b 60 10 8b 58 04 49 01 c4 e8 3b 28 01 00 0f b7 d3 31 f6 48 89 c7 4c 89 e1 e8 9b d4 ff ff 89 44 24 1c 85 c0 75 13 <8b> 04 25 08 00 00 00 0f 0b 66 2e 0f 1f 84 00 00 00 00 00 e8 0b 28 Nov 20 14:48:30 born2chill kernel: [ 26.072434][ T8020] kactivitymanage[8020]: segfault at c ip 7f39bf941101 sp 7ffca9ee8690 error 4 in libQt5XcbQpa.so.5.15.5[7f39bf909000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072443][ T6867] kaccess[6867]: segfault at c ip 7f4f42f6b101 sp 7ffc265fed00 error 4 Nov 20 14:48:30 born2chill kernel: [ 26.072447][ T8020] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072460][ T6867] in libQt5XcbQpa.so.5.15.5[7f4f42f33000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072465][ T6867] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072494][ T5008] kwalletd5[5008]: segfault at c ip 7fb59b18e101 sp 7ffc86070890 error 4 in libQt5XcbQpa.so.5.15.5[7fb59b156000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072508][ T5008] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072521][ T6056] ksmserver[6056]: segfault at c ip 7fc78ea43101 sp 7ffdd8774380 error 4 Nov 20 14:48:30 born2chill kernel: [ 26.072526][ T7591] gmenudbusmenupr[7591]: segfault at c ip 7fa916742101 sp 7ffdf7b531f0 error 4 in libQt5XcbQpa.so.5.15.5[7fa91670a000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072541][ T6056] in libQt5XcbQpa.so.5.15.5[7fc78ea0b000+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072545][ T7591] Nov 20 14:48:30 born2chill kernel: [ 26.072545][ T6056] Nov 20 14:48:30 born2chill kernel: [ 26.072548][ T6056] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072548][ T7591] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 Nov 20 14:48:30 born2chill kernel: [ 26.072751][ T6871] xembedsniproxy[6871]: segfault at c ip 7f3e07f48101 sp 7ffefe0983c0 error 4 in libQt5XcbQpa.so.5.15.5[7f3e07f1+a9000] Nov 20 14:48:30 born2chill kernel: [ 26.072763][ T6871] Code: ff ff 0f 1f 80 00 00 00 00 48 8b 7d 20 8b 54 24 44 8b 74 24 4c e8 8f 84 fc ff 48 8b 7d 20 31 d2 89 c6 e8 62 8a fc ff 49 89 c7 <8b> 40 0c 85 c0 0f 85 ca 04 00 00 e8 7f 1c fd ff 0f b6 40 10 84 c0 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added Product|kwin|KScreen Component|general |common -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added Version|5.24.4 |5.26.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #9 from b2cc --- Hi Nate, thanks for checking in, and again apologies for the late reply. So I just got back to testing this on the latest KDE 5.26.3 and the crash still happens for me. I uploaded a new backtrace, and also a screenshot with my display configuration, since I run 3x 27" displays in a non-standard layout - maybe this contributes to the problem I'm experiencing? Anyways here are my package configurations and versions: x11-base/xorg-drivers-21.1-r1::gentoo INPUT_DEVICES="evdev libinput -elographics -joystick -synaptics -vmmouse -void -wacom" VIDEO_CARDS="nvidia vesa -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -i915 -intel -mga -nouveau (-nv) (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -via -virtualbox -vmware (-glint%) (-i965%)" x11-base/xorg-server-21.1.4:0/21.1.4::gentoo USE="elogind udev unwind xcsecurity xorg -debug -minimal (-selinux) -suid -systemd -test -xephyr -xnest -xvfb (-dmx%) (-kdrive%)" x11-drivers/xf86-input-evdev-2.10.6::gentoo x11-drivers/xf86-input-libinput-1.2.1::gentoo x11-drivers/xf86-video-vesa-2.5.0::gentoo kde-plasma/libkscreen-5.26.3:5/7::gentoo USE="-debug -doc -test" kde-plasma/kwin-5.26.3:5::gentoo USE="lock plasma -accessibility -caps -debug -gles2-only -handbook -multimedia -screencast -test" kde-plasma/kscreen-5.26.3:5::gentoo USE="-debug -test" x11-libs/libXrandr-1.5.2::gentoo USE="-doc" ABI_X86="32 (64) (-x32)" dev-qt/qtcore-5.15.5-r3:5/5.15.5::gentoo USE="icu -debug -old-kernel -systemd -test" dev-qt/qtdbus-5.15.5-r1:5/5.15::gentoo USE="-debug -test" Thanks and all the best! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 --- Comment #8 from b2cc --- Created attachment 153905 --> https://bugs.kde.org/attachment.cgi?id=153905&action=edit 3 display screen layout and configuration -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 --- Comment #7 from b2cc --- Created attachment 153904 --> https://bugs.kde.org/attachment.cgi?id=153904&action=edit kscreen_backend backtrace from KDE 5.26 / 2022-11-20 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added Product|kwin|KScreen Component|general |libkscreen -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added Version|5.23.5 |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- Assignee|kwin-bugs-n...@kde.org |b...@dest-unreachable.net --- Comment #5 from b2cc --- Created attachment 147868 --> https://bugs.kde.org/attachment.cgi?id=147868&action=edit backtrace frombacktrace-kscreen_backend.txt Sorry for the late follow up, real life happened and I just now finally set up my system for debugging. I managed to get a crashdump from /usr/lib64/libexec/kf5/kscreen_backend_launcher which seems to be the binary causing the crash in the first place. Took me a while to figure that out, not used to stuff like this. I attached the full backtrace as text to the issue now, maybe you guys can take another look and make something of it? PS: I updated the gentoo bug at https://bugs.gentoo.org/832047 as well, not sure where the root cause is to be found. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 448968] kwin 5.23.5 crashes with nvidia-drivers 495.46
https://bugs.kde.org/show_bug.cgi?id=448968 b2cc changed: What|Removed |Added CC||b...@dest-unreachable.net --- Comment #1 from b2cc --- I have the same issue with linux 5.15.16 and nvidia-drivers 5.10.93. when I try to log in with SDDM, kwin segfaults: [Tue Jan 25 15:20:04 2022] kscreen_backend[6550]: segfault at 8 ip 7f06e0e583cd sp 7ffd4535baf0 error 4 in KSC_XRandR.so[7f06e0e55000+19000] I opened a similar bug report (and some more logs) here: https://bugs.gentoo.org/831846 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417895] Pull current track/artist name from radio stream
https://bugs.kde.org/show_bug.cgi?id=417895 --- Comment #6 from b2cc --- I second this request - it seems like a minor thing but would bre really nice to have. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 417895] Pull current track/artist name from radio stream
https://bugs.kde.org/show_bug.cgi?id=417895 b2cc changed: What|Removed |Added CC||b...@dest-unreachable.net --- Comment #5 from b2cc --- *** Bug 442444 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442444] Display stream metadata (Artist/Title/etc.) when playing Radios
https://bugs.kde.org/show_bug.cgi?id=442444 b2cc changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from b2cc --- Sorry just noticed this was already reported in 417895. My bad, closing this ticket. *** This bug has been marked as a duplicate of bug 417895 *** -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442444] New: Display stream metadata (Artist/Title/etc.) when playing Radios
https://bugs.kde.org/show_bug.cgi?id=442444 Bug ID: 442444 Summary: Display stream metadata (Artist/Title/etc.) when playing Radios Product: Elisa Version: 21.04.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: b...@dest-unreachable.net Target Milestone: --- SUMMARY Display stream metadata (Artist/Title/etc.) when playing Radios STEPS TO REPRODUCE 1. Add stream from to "Radios" in Elisa:, e.g. https://orf-live.ors-shoutcast.at/fm4-q2a 2. Start replay 3. No Artist/Title or other information from the stream metadata is shown in the replay window OBSERVED RESULT No Artist/Title or other information from the stream metadata is shown in the replay window EXPECTED RESULT Show stream metadata information alongside the name of the radio SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Elisa: 21.04.3 Linux/KDE Plasma: Gentoo x86_64 KDE Plasma Version: 5.22 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 ADDITIONAL INFORMATION I tested that the stream sends metadata with a little python script I grabbed from SO: * https://stackoverflow.com/a/44391393 When testing with the stream it regularly outputs the stream metadata and one can observe the metadata updates. The stream itself is provided by an Icecast streaming server and in mpeg audio format. Sample output I gathered: --- ~# python3 script.py https://orf-live.ors-shoutcast.at/fm4-q2a New title: Cypress Hill - Dr. Greenthumb | FM4 Homebase Title: Cypress Hill - Dr. Greenthumb | FM4 Homebase New title: James Hersey - Souvenir | FM4 Homebase Title: James Hersey - Souvenir | FM4 Homebase --- It would be nice if this information was displayed somewhere in Elisa while playing streams. Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
