[gentoo-user] Smplayer adjusting PCM level in Kmix.
Howdy, I've had this problem for a really long time. I've tried adjusting settings in Smplayer to stop it but so far, I have not found the magic combination or option to change. I don't have pulseaudio here. Just Alsa and friends. As some know, I use Smplayer to watch TV with. I use the old dying Gnome-player to watch other videos on my computer screen and sound through computer speakers. I tend to watch fix it videos etc with Gnome-player. Anyway, one thing that Smplayer does that annoys me is each time it starts a new video, from either a fresh start or next video in the playlist, it adjusts the PCM sound level in Kmix. Usually it adjusts it down to almost mute. I've seen it adjust down to 6 and even 2. Either way, no sound. I've tried every setting in Smplayer and the audio section I can find and no matter what, it adjusts the PCM sound level in Kmix every single time. It's annoying as heck. I think I've looked in every config file that deals with sound. I've removed or commented out a lot of volume settings with no change. Does anyone know if there is a way to tell it to knock it off? It's getting so annoying, I'm thinking about abandoning Smplayer. So far, I haven't seen any other player do this. That's why I think it is a Smplayer setting somewhere. By the way, Smplayer is set to not change volume with Kmix or anything else. I adjust the volume on the TV itself, with a remote. One woould think that it bypassing sound control devices that it would also leave Kmix alone, since it shouldn't even be going through it anyway. Ideas? Dale :-) :-)
Re: [gentoo-user] New install - Wayland and graphical login
On Saturday, 26 June 2021 11:50:01 BST antlists wrote: > I just want a working systemd/wayland desktop system. So basically, a > full-weight normal desktop. [snip ...] > I've got this one selected, /desktop/plasma/systemd Select default/linux/amd64/17.1/desktop/plasma/systemd (stable). Then update @world. You should be good to go as long as video drivers and firmware are in place, but if X11 is not working this could be an area meriting further investigation. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] New install - Wayland and graphical login
On 26/06/2021 10:28, Michael wrote: On Saturday, 26 June 2021 08:19:24 BST Wols Lists wrote: On 26/06/21 00:51, Michael wrote: Given your error, you appear to not have installed the requisite packages for the Plasma/KDE. It should have been installed as a dependency of plasma-workspace: Ah. Another piece of missing information ... I'll try that. I would have thought that would have been pulled in seeing as I've got wayland and qt use flags etc $ qfile startplasma-wayland kde-plasma/plasma-workspace: /usr/bin/startplasma-wayland I am not clear on your particular use case(s). Plasma desktop is usually installed by setting the appropriate make.profile: I just want a working systemd/wayland desktop system. So basically, a full-weight normal desktop. $ eselect profile list Available profile symlink targets: [1] default/linux/amd64/17.1 (stable) [2] default/linux/amd64/17.1/selinux (stable) [3] default/linux/amd64/17.1/hardened (stable) [4] default/linux/amd64/17.1/hardened/selinux (stable) [5] default/linux/amd64/17.1/desktop (stable) [6] default/linux/amd64/17.1/desktop/gnome (stable) [7] default/linux/amd64/17.1/desktop/gnome/systemd (stable) [8] default/linux/amd64/17.1/desktop/plasma (stable) * [9] default/linux/amd64/17.1/desktop/plasma/systemd (stable) I've got this one selected, /desktop/plasma/systemd [10] default/linux/amd64/17.1/desktop/systemd (stable) [11] default/linux/amd64/17.1/developer (stable) [12] default/linux/amd64/17.1/no-multilib (stable) [13] default/linux/amd64/17.1/no-multilib/hardened (stable) [14] default/linux/amd64/17.1/no-multilib/hardened/selinux (stable) [15] default/linux/amd64/17.1/systemd (stable) [16] default/linux/amd64/17.0 (dev) [17] default/linux/amd64/17.0/selinux (dev) [18] default/linux/amd64/17.0/hardened (dev) [19] default/linux/amd64/17.0/hardened/selinux (dev) [20] default/linux/amd64/17.0/desktop (dev) [21] default/linux/amd64/17.0/desktop/gnome (dev) [22] default/linux/amd64/17.0/desktop/gnome/systemd (dev) [23] default/linux/amd64/17.0/desktop/plasma (dev) [24] default/linux/amd64/17.0/desktop/plasma/systemd (dev) [25] default/linux/amd64/17.0/developer (dev) [26] default/linux/amd64/17.0/no-multilib (dev) [27] default/linux/amd64/17.0/no-multilib/hardened (dev) [28] default/linux/amd64/17.0/no-multilib/hardened/selinux (dev) [29] default/linux/amd64/17.0/systemd (dev) [30] default/linux/amd64/17.0/x32 (dev) [31] default/linux/amd64/17.0/musl (exp) [32] default/linux/amd64/17.0/musl/hardened (exp) [33] default/linux/amd64/17.0/musl/hardened/selinux (exp) [34] default/linux/amd64/17.0/uclibc (exp) [35] default/linux/amd64/17.0/uclibc/hardened (exp) If you are looking for some minimalist desktop, a Plasma DE plus KDE applications with hundred of dependencies is probably not what you want. Also, I think Plasma DE and most DMs will pull in X11, because: a) they work both with X11 and wayland; b) many X11 applications can only run in X using XWayland. XWayland is an X Server running as a Wayland client to enable displaying native X11 client applications within a Wayland compositor environment. I haven't looked into it at any depth to see if you can strip a heavy DE like Plasma from all xserver dependencies - I'd guess you can't. Not after a minimalist system, and if it pulls in X that's fine. (Actually, I've installed X, and at the moment it blows up on me, but if I can get Wayland working, I don't see the point in debugging it until I need to ...) If you have Gnome already installed then you can use the stanza for gnome- session instead. My use flags also contain -gtk -gnome ... gnome at least is on my list of pet hates ... Cheers, Wol OK, select the Plasma profile, then have a quick look at: https://wiki.gentoo.org/wiki/KDE You'll need to disable some USE flags of plasma-meta to avoid dragging in things you may not need/require, like 'display-manager', 'sddm', 'accessibility', etc. Eventually, after you update @world, add any kde-apps *-meta packages you need. However, if you intend to use wayland for the most minimalist of purposes, then you may want to consider something like Wayfire, instead of Plasma. I'll need something like sddm, because I'll have multiple users logged in simultaneously. I was trying to use qtgreet as per the "Wayland Landscape" page, but the package doesn't seem to exist ... I'd rather avoid gnome/gdm and gtkgreet, lightdm and sddm look like X11 (and I said I didn't want to debug it :-), and tuigreet looks like it might not support multi-user/multi-head. Still, if I can get plasma running, I can work from there ... Cheers, Wol
Re: [gentoo-user] New install - Wayland and graphical login
On Saturday, 26 June 2021 08:19:24 BST Wols Lists wrote: > On 26/06/21 00:51, Michael wrote: > > Given your error, you appear to not have installed the requisite packages > > for the Plasma/KDE. It should have been installed as a dependency of > > plasma-workspace: > > Ah. Another piece of missing information ... I'll try that. I would have > thought that would have been pulled in seeing as I've got wayland and qt > use flags etc > > > $ qfile startplasma-wayland > > kde-plasma/plasma-workspace: /usr/bin/startplasma-wayland I am not clear on your particular use case(s). Plasma desktop is usually installed by setting the appropriate make.profile: $ eselect profile list Available profile symlink targets: [1] default/linux/amd64/17.1 (stable) [2] default/linux/amd64/17.1/selinux (stable) [3] default/linux/amd64/17.1/hardened (stable) [4] default/linux/amd64/17.1/hardened/selinux (stable) [5] default/linux/amd64/17.1/desktop (stable) [6] default/linux/amd64/17.1/desktop/gnome (stable) [7] default/linux/amd64/17.1/desktop/gnome/systemd (stable) [8] default/linux/amd64/17.1/desktop/plasma (stable) * [9] default/linux/amd64/17.1/desktop/plasma/systemd (stable) [10] default/linux/amd64/17.1/desktop/systemd (stable) [11] default/linux/amd64/17.1/developer (stable) [12] default/linux/amd64/17.1/no-multilib (stable) [13] default/linux/amd64/17.1/no-multilib/hardened (stable) [14] default/linux/amd64/17.1/no-multilib/hardened/selinux (stable) [15] default/linux/amd64/17.1/systemd (stable) [16] default/linux/amd64/17.0 (dev) [17] default/linux/amd64/17.0/selinux (dev) [18] default/linux/amd64/17.0/hardened (dev) [19] default/linux/amd64/17.0/hardened/selinux (dev) [20] default/linux/amd64/17.0/desktop (dev) [21] default/linux/amd64/17.0/desktop/gnome (dev) [22] default/linux/amd64/17.0/desktop/gnome/systemd (dev) [23] default/linux/amd64/17.0/desktop/plasma (dev) [24] default/linux/amd64/17.0/desktop/plasma/systemd (dev) [25] default/linux/amd64/17.0/developer (dev) [26] default/linux/amd64/17.0/no-multilib (dev) [27] default/linux/amd64/17.0/no-multilib/hardened (dev) [28] default/linux/amd64/17.0/no-multilib/hardened/selinux (dev) [29] default/linux/amd64/17.0/systemd (dev) [30] default/linux/amd64/17.0/x32 (dev) [31] default/linux/amd64/17.0/musl (exp) [32] default/linux/amd64/17.0/musl/hardened (exp) [33] default/linux/amd64/17.0/musl/hardened/selinux (exp) [34] default/linux/amd64/17.0/uclibc (exp) [35] default/linux/amd64/17.0/uclibc/hardened (exp) If you are looking for some minimalist desktop, a Plasma DE plus KDE applications with hundred of dependencies is probably not what you want. Also, I think Plasma DE and most DMs will pull in X11, because: a) they work both with X11 and wayland; b) many X11 applications can only run in X using XWayland. XWayland is an X Server running as a Wayland client to enable displaying native X11 client applications within a Wayland compositor environment. I haven't looked into it at any depth to see if you can strip a heavy DE like Plasma from all xserver dependencies - I'd guess you can't. > > If you have Gnome already installed then you can use the stanza for gnome- > > session instead. > > My use flags also contain -gtk -gnome ... gnome at least is on my list > of pet hates ... > > Cheers, > Wol OK, select the Plasma profile, then have a quick look at: https://wiki.gentoo.org/wiki/KDE You'll need to disable some USE flags of plasma-meta to avoid dragging in things you may not need/require, like 'display-manager', 'sddm', 'accessibility', etc. Eventually, after you update @world, add any kde-apps *-meta packages you need. However, if you intend to use wayland for the most minimalist of purposes, then you may want to consider something like Wayfire, instead of Plasma. signature.asc Description: This is a digitally signed message part.
[gentoo-user] Interesting portage upgrade
Hello list, This is just an observation. I update the rescue system on this box weekly. Today, portage version 3.0.18 wanted to upgrade itself to 3.0.20-r6, plus 31 other packages, and remerge 16 others. After saying No and emerging portage, those 16 remerges were not included: just the 31 upgrades. This is the first time I've witnessed a real difference in portage's behaviour between versions, as far as I can remember. As I said, just an observation. -- Regards, Peter.
