[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #28 from Niels Ole Salscheider --- > * EffectWatcher constructor for "_KDE_NET_WM_BACKGROUND_CONTRAST_REGION" > atom is often !isNull() Does "often" mean that you observed it to be Null sometimes? Because often is not always... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 366032] plasma-pa should allow to select the sink for volume control
https://bugs.kde.org/show_bug.cgi?id=366032 --- Comment #1 from Niels Ole Salscheider --- Or maybe it would be enough to recursively query the master sink starting from the default sink and then adjust the volume of the sink you end up with eventually. That would fix my use-case at least but I do not know about others... -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 366032] New: plasma-pa should allow to select the sink for volume control
https://bugs.kde.org/show_bug.cgi?id=366032 Bug ID: 366032 Summary: plasma-pa should allow to select the sink for volume control Product: plasma-pa Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: niels_...@salscheider-online.de CC: plasma-b...@kde.org Currently, plasma-pa just sets the volume of the default sink when the volume keys on the keyboard are pressed. This is not necessarily what the user wants if he has a bit more complex setup. It would therefore be good if the sink for the volume control could be configured in plasma-pa's KCM. For example, I have this in my default.pa: load-module module-remap-sink sink_name=headphones channels=2 master_channel_map=front-left,front-right channel_map=front-left,front-right remix=0 sink_properties=device.description=Headphones load-module module-virtual-surround-sink sink_name=vsurround master=headphones hrir=/home/olesalscheider/.ir.wav sink_properties=device.description=VirtualSurround set-default-sink vsurround This splits two channels of the sound card and creates a "headphone" sink from them. The other channels could for example be connected to a surround sound system but I do not use them currently. Then it creates another sink (vsurround) with the "headphone" sink as master. This sink computes virtual surround sound from its input signals and passes the generated signal to the master. I have set "vsurround" as my default sink because I want all new streams to go there by default. But I have moved some manually to "headphones" where I do not want the virtual surround effect (e. g. for music). When I now press the volume keys I want them not to change the volume of the "vsurround" sink but the volume of the master sink. Because otherwise the volume of the streams that I moved to "headphones" is not changed. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362257] spectacle.khotkeys: The specified file is empty or not a configuration file
https://bugs.kde.org/show_bug.cgi?id=362257 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de --- Comment #11 from Niels Ole Salscheider --- I can confirm that this is in fact a bug! The source code of libkhotkeysprivate (Settings::isConfigFileValid to be precisely) clearly states that only version 2 is supported. Therefore, spectacle.khotkeys should be adjusted accordingly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #3 from Niels Ole Salscheider --- Created attachment 98784 --> https://bugs.kde.org/attachment.cgi?id=98784&action=edit Plasma after being restarted (with transparency) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 --- Comment #2 from Niels Ole Salscheider --- Created attachment 98783 --> https://bugs.kde.org/attachment.cgi?id=98783&action=edit Plasma right after login (no transparency) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362531] New: Plasma panels are not transparent after login
https://bugs.kde.org/show_bug.cgi?id=362531 Bug ID: 362531 Summary: Plasma panels are not transparent after login Product: plasmashell Version: 5.6.3 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: niels_...@salscheider-online.de When plasmashell starts after logging in, the panels are not transparent. Restarting plasmashell fixes this. I think this might be because of a race condition with kwin: plasmashell will only enable the background contrast if the _KDE_NET_WM_BACKGROUND_CONTRAST_REGION atom is registered. But this only happens when kwin loads the backgroundcontrast plugin which seems to happen too late for me. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 362142] New: The session does not finish cleanly / startkde exits too early?
https://bugs.kde.org/show_bug.cgi?id=362142 Bug ID: 362142 Summary: The session does not finish cleanly / startkde exits too early? Product: frameworks-kinit Version: 5.20.0 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: niels_...@salscheider-online.de CC: kdelibs-b...@kde.org When I try to log out or power down my computer, the current kde session stays in the closing state. In this case, loginctl session-status prints something similar to this: - olesalscheider (1000) Since: Sat 2016-04-23 15:56:16 CEST; 8min ago Leader: 1121 Seat: seat0; vc1 Display: :0 Service: sddm; type x11; class user Desktop: KDE State: closing Unit: session-1.scope �~T~\�~T~@1292 /usr/x86_64-pc-linux-gnu/bin/pulseaudio --start --log-target=syslog �~T~\�~T~@1494 gpg-agent --homedir /home/olesalscheider/.gnupg --use-standard-socket --daemon �~T~\�~T~@1616 kdeinit4: kio_http_cache_cleaner [kdeinit] �~T~T�~T~@1827 /usr/x86_64-pc-linux-gnu/libexec/kf5/kio_http_cache_cleaner Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kdeinit5[1191]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* Apr 23 16:02:51 OleDesktop kactivitymanagerd[1231]: The X11 connection broke (error 1). Did the X11 server die? Apr 23 16:02:51 OleDesktop kdeinit5[1191]: The X11 connection broke: I/O error (code 1) Apr 23 16:02:52 OleDesktop drkonqi[2550]: QXcbConnection: Could not connect to display :0 Apr 23 16:02:52 OleDesktop kdeinit5[2555]: QXcbConnection: Could not connect to display :0 It seems that the problem is that the X server is terminated before kdeinit5 finishes and before it can terminate all children. But AFAIK the X server should only be terminated once startkde finishes and that can only happen when the kdeinit5_shutdown wrapper for kdeinit returns. Therefore it seems likely that the bug is either in kdeinit or the wrapper. The session can be cleanly terminated by running "loginctl terminate-session". Reproducible: Always Steps to Reproduce: 1. Log out 2. Run loginctl list-sessions / loginctl session-status Actual Results: Session stays in closing state Expected Results: Session finishes cleanly -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360967] The breeze-plymouth theme contains subdirectories
https://bugs.kde.org/show_bug.cgi?id=360967 --- Comment #2 from Niels Ole Salscheider --- plymouth-populate-initrd is part of plymouth, though, and is only used by dracut. This means it is either a plymouth bug or that it was an intentional decision by the plymouth developers... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 360967] New: The breeze-plymouth theme contains subdirectories
https://bugs.kde.org/show_bug.cgi?id=360967 Bug ID: 360967 Summary: The breeze-plymouth theme contains subdirectories Product: Breeze Version: 5.6.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-de...@kde.org Reporter: niels_...@salscheider-online.de The breeze-plymouth theme does not have a flat structure but contains sub-directories for the images. The plymouth-populate-initrd does not support this so that the images do not end up in the initramfs when using dracut. This obviously breaks the theme. However, I'm not sure if plymouth themes must not contain sub-directories or it this is a bug in plymouth. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105 --- Comment #7 from Niels Ole Salscheider --- Please ignore what I said. The real problem is that the window is not visible because of setFixedSize(minimumSize()); where minimumSize() returns (0, 0). -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 360105] Doesn't start with Qt 5.6
https://bugs.kde.org/show_bug.cgi?id=360105
Niels Ole Salscheider changed:
What|Removed |Added
CC||niels_ole@salscheider-onlin
||e.de
--- Comment #6 from Niels Ole Salscheider ---
It seems that kcalc polls on a socket in "/tmp/.ICE-unix/". The relevant output
from strace is:
[...]
socket(PF_LOCAL, SOCK_STREAM, 0)= 6
getsockopt(6, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
uname({sysname="Linux", nodename="OleDesktop", ...}) = 0
connect(6, {sa_family=AF_LOCAL, sun_path=@"/tmp/.ICE-unix/1317"}, 22) = 0
fcntl(6, F_SETFD, FD_CLOEXEC) = 0
[...]
poll([{fd=5, events=POLLIN}, {fd=6, events=POLLIN}], 2, -1) = 1 ([{fd=5,
revents=POLLIN}])
read(5, "\1\0\0\0\0\0\0\0", 16) = 8
And then the last two lines are repeated.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #27 from Niels Ole Salscheider --- Yes, this would be sufficient. For mesa at least, since it queries the environment variable in eglGetDisplay. We already use EGL_PLATFORM for the hwcomposer backend and the wayland QPA, so it should be fine to also use it here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #24 from Niels Ole Salscheider --- (In reply to Thomas Lübking from comment #23) > The relevant code (initEGL()) is in platform agnostic in libkwineffects - > we'd either have to transfer it into the platform implementations to make us > of eglGetPlatformDisplayEXT (or pass it down alongside the EGL_EXT_platform* > tests incl. an explicit query for client extensions on EGL_NO_DISPLAY) Yes, that's why I haven't proposed a patch yet... > => Simply setting EGL_PLATFORM avoids the crash? The crash is already avoided by the patch I sent to mesa-dev. But simply setting EGL_PLATFORM makes mesa choose another platform that uses render nodes instead of /dev/dri/card0 so that I do not see "radeon: Failed to get PCI ID, error number -13" anymore. Also, it would avoid the crash even when my patch was not applied to mesa. EGL_PLATFORM was a workaround by mesa for this problem when eglGetPlatformDisplayEXT was not yet around. It still works but I think that the latter is the cleaner solution. > I'm however not sure whether that's a general solution to the problem (see > eglinfo situation) I'm afraid that there is not really a general solution, because unfortunately eglGetDisplay made it into the standard in its current form without considering that there might be drivers with multiple platforms. Applications should probably use glGetPlatformDisplayEXT when possible. And for all that don't, distributions should set a sane default backend that will hopefully not fail (surfaceless?). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #22 from Niels Ole Salscheider --- Or even better, use eglGetPlatformDisplayEXT to get a display for the right platform (if available). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #21 from Niels Ole Salscheider --- Maybe KWin should set EGL_PLATFORM to x11 or wayland, depending on where it runs. This is at least what other compositors do. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #20 from Niels Ole Salscheider --- No, the current code tries all EGL drivers (which is only drm), but it only tries one platform for each driver. This platform is either what is set by the EGL_PLATFORM env var or if that is empty what was the first passed to the configure script in --with-egl-platforms. In my case this was drm and I was not aware that the order matters. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #18 from Niels Ole Salscheider --- > The code in question looks like it unconditionally tries /dev/dri/renderD0, > that one's likely occupied and in return it resorts to card0 > > What *should* (probably, I'm no expert) happen is to try all available > render nodes (ie. loop from 0-128?) until one available is found?! The current code just tries to open /dev/dri/card0 twice (on Linux), because "int n = snprintf(buf, sizeof(buf), DRM_DEV_NAME, DRM_DIR_NAME, 0);" just copies that string into buf. So it does not use render nodes at all. Of course, the path of the render node could be calculated in a similar way - the hardcoded path was mostly just to see if it works. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #16 from Niels Ole Salscheider --- Created attachment 96909 --> https://bugs.kde.org/attachment.cgi?id=96909&action=edit Mesa patch to prefer rendernodes Ok, I get significantly more output and no error with the attached patch. But I am not sure if this is the right thing to do or if it is supposed to work with /dev/dri/card0... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #15 from Niels Ole Salscheider --- The output seems to be missing? I wonder if the problem has something to do with rendernodes. The platform code opens /dev/dri/card0 when no display is supplied but the pipe-loader code seems to open a render node (/dev/dri/renderD*). The RADEON_INFO ioctl that fails has DRM_AUTH|DRM_RENDER_ALLOW as access restrictions. This means that the ioctl can be called from render nodes, but I am not completely sure what DRM_AUTH implies and if that can cause it to fail when using /dev/dri/card0. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #13 from Niels Ole Salscheider --- It seems so, this is the output I get: radeon: Failed to get PCI ID, error number -13 EGL API version: 1.4 EGL vendor string: Mesa Project EGL version string: 1.4 (DRI2) EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 EGL extensions string: EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_create_context EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context EGL_MESA_configless_context EGL_MESA_image_dma_buf_export EGL client extensions string: EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_wayland EGL_EXT_platform_x11 EGL_KHR_client_get_all_proc_addresses EGL_MESA_platform_gbm Configurations: bf lv colorbuffer dp st msvis cav bi renderable supported id sz l r g b a th cl ns bid eat nd gl es es2 vg surfaces - 0x01 32 0 8 8 8 8 0 0 0 0 0x34325241-- y y y win 0x07 32 0 8 8 8 8 16 0 0 0 0x34325241-- y y y win 0x0d 32 0 8 8 8 8 24 0 0 0 0x34325241-- y y y win 0x13 32 0 8 8 8 8 24 8 0 0 0x34325241-- y y y win 0x19 32 0 8 8 8 8 32 0 0 0 0x34325241-- y y y win 0x1f 24 0 8 8 8 0 0 0 0 0 0x34325258-- y y y win 0x25 24 0 8 8 8 0 16 0 0 0 0x34325258-- y y y win 0x2b 24 0 8 8 8 0 24 0 0 0 0x34325258-- y y y win 0x31 24 0 8 8 8 0 24 8 0 0 0x34325258-- y y y win 0x37 24 0 8 8 8 0 32 0 0 0 0x34325258-- y y y win 0x79 16 0 5 6 5 0 0 0 0 0 0x36314752-- y y y win 0x7f 16 0 5 6 5 0 16 0 0 0 0x36314752-- y y y win 0x85 16 0 5 6 5 0 24 0 0 0 0x36314752-- y y y win 0x8b 16 0 5 6 5 0 24 8 0 0 0x36314752-- y y y win 0x91 16 0 5 6 5 0 32 0 0 0 0x36314752-- y y y win I'm not sure if it is ok to fail or not. I will have to look into it a bit more... Just for reference, a link to the patch: http://lists.freedesktop.org/archives/mesa-dev/2016-January/106102.html -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #11 from Niels Ole Salscheider --- Thank you for your patience. I have sent a patch to mesa-dev that fixes the crash. I still see "radeon: Failed to get PCI ID, error number -13" (both with KWin and eglinfo) but apart from that, both seem to work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #10 from Niels Ole Salscheider --- It segfaults in the same function. So it really seems to be a driver issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #8 from Niels Ole Salscheider --- I have only tried with mesa master. I can also compile the latest stable version but this will take a bit since I will have to downgrade llvm, clang and maybe some other first. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 Niels Ole Salscheider changed: What|Removed |Added Attachment #96907|0 |1 is obsolete|| --- Comment #6 from Niels Ole Salscheider --- Created attachment 96908 --> https://bugs.kde.org/attachment.cgi?id=96908&action=edit Backtrace with debug symbols -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #4 from Niels Ole Salscheider --- Created attachment 96907 --> https://bugs.kde.org/attachment.cgi?id=96907&action=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 --- Comment #5 from Niels Ole Salscheider --- (In reply to Thomas Lübking from comment #3) > From the mesa troubleshooting guide: > > If see this error message: radeon: Failed to get PCI ID, error number -13, > make sure you have permissions to access the device (usually > /dev/dri/card0), and get the latest version of mesa from git. Prior to this > commit: 044de40cb0c6af54d99252f55145972780362afa, you would have seen this > error message when running compute programs and X at the same time. Yes, I know. It's not a permission problem though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 Niels Ole Salscheider changed: What|Removed |Added CC||niels_ole@salscheider-onlin ||e.de --- Comment #1 from Niels Ole Salscheider --- Created attachment 96906 --> https://bugs.kde.org/attachment.cgi?id=96906&action=edit Output of "qdbus org.kde.KWin /KWin supportInformation" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358750] New: KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755
https://bugs.kde.org/show_bug.cgi?id=358750 Bug ID: 358750 Summary: KWin crashes with compositing enabled since e641022bf9482a11209577b5654cd43231be0755 Product: kwin Version: 5.5.4 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: niels_...@salscheider-online.de Since commit e641022bf9482a11209577b5654cd43231be0755, KWin crashes during startup when compositing is enabled. The crash is caused by the addition of if (dpy == EGL_NO_DISPLAY) dpy = eglGetDisplay(EGL_DEFAULT_DISPLAY); in libkwineffects/kwinglutils.cpp. When reverting the commit or removing these two lines, everything works fine again. Right before the crash, I see "radeon: Failed to get PCI ID, error number -13" which comes from mesa (more precisely from do_winsys_init in src/gallium/winsys/radeon/drm/radeon_drm_winsys.c when RADEON_INFO_DEVICE_ID is queried). Reproducible: Always Steps to Reproduce: 1. Start KWin with compositing enabled -- You are receiving this mail because: You are watching all bug changes.
