[gentoo-user] Plasma6 audio volume keys no longer working
Hi there, After recent update world, my laptop upgraded from kde5/plasma5/x11 to kde6/ plasma6/wayland. Now I have a very strange behavior of the volume+/- and mute button. When being logged in, those keys have no effect (ignored), but mic-mute button works as it should. The behavior gets more weird, because all of the keys work perfectly when the session is locked (e.g. after wakeup from suspend, when I have to enter the password go unlock). This means, that the keys themselves, and the proper handling in drivers and evdev and forwarding to some application works, but something in plasma6 goes wrong. I checked bindings of the keys, when trying to rebind Volume+ or Volume- to their respective keys, it says that that they are already bound to that key. Any ideas? --- Relevant software information --- Kde-plasma/plasma-meta-6.1.5 Kde-frameworks 6.6.0 + 5.116.0 (Both slots installed) Qt 6.7.2 + 6.15.14 (Both slots installed) dev-libs/wayland-1.23.1
Re: [gentoo-user] NFS mounting
On Tuesday 22 October 2024 22:07:06 BST I wrote: > Also while bug-hunting, I found an extra-long Ethernet cable and strung the > i5 into the LAN that way. The M9 only ever sees the LAN, whereas I can now > start and stop the LAN and WLAN at will on the i5. The Fritz!Box router > sits at the junction. Eventually, of course, once I get this setup working, > the cable will go back in the cupboard. I should have added that the remote compilation works well with the cable. I have found though that the linux-firmware ebuild requires the /boot partition to be mounted, which it shouldn't be on a foreign machine, so I say emerge -uaDvN --exclude="linux-firmware-20241017-*", only to find that it's emerged anyway. Dropping that last hyphen gives the required result. Is this a portage bug? -- Regards, Peter.
Re: [gentoo-user] NFS mounting
On Wed, 23 Oct 2024 at 12:56, Peter Humphrey wrote: > I should have added that the remote compilation works well with the cable. I > have found though that the linux-firmware ebuild requires the /boot partition > to be mounted, which it shouldn't be on a foreign machine, so I say > emerge -uaDvN --exclude="linux-firmware-20241017-*", only to find that it's > emerged anyway. Dropping that last hyphen gives the required result. > > Is this a portage bug? It is definitely weird, but it is documented to be that way. From the manual ebuild(5): The version part that comes before the ’*’ must be a valid version in the absence of the ’*’. For example, ’2’ is a valid version and ’2.’ is not. Therefore, ’2*’ is allowed and ’2.*’ is not. Regards, Arve
Re: [gentoo-user] NFS mounting
On Wednesday 23 October 2024 12:36:23 BST Arve Barsnes wrote: > On Wed, 23 Oct 2024 at 12:56, Peter Humphrey wrote: > > I should have added that the remote compilation works well with the cable. > > I have found though that the linux-firmware ebuild requires the /boot > > partition to be mounted, which it shouldn't be on a foreign machine, so I > > say emerge -uaDvN --exclude="linux-firmware-20241017-*", only to find > > that it's emerged anyway. Dropping that last hyphen gives the required > > result. > > > > Is this a portage bug? > > It is definitely weird, but it is documented to be that way. From the > manual ebuild(5): > > The version part that comes before the ’*’ must be a valid version in > the absence of the ’*’. For example, ’2’ is a valid version and ’2.’ > is not. Therefore, ’2*’ is allowed and ’2.*’ is not. Ah! Thank you Arve. The subtleties of a complex system seem endless at times... :) -- Regards, Peter.
[gentoo-user] Re: Suppressing some "emerge" output
On Wed, 09 Oct 2024 17:25:13 +0200 I myself wrote: > ... > after a recent KDE upgrade among other new packages "emerge" also in- > stalled "dev-qt/qtwebengine" as a new dependency. Since on my five year > old laptop this package requires about 6 hours 20 minutes to build, I > decided to slightly redesign my package managing script and to use bina- > ry packages for long bilding dependencies I build with default USE flags > anyway. > > It works, but is there a way (short of using "|grep -v ...") to prevent > "emerge" from spitting plenty of noisy but rather irrelevant progress > messages to standard output (which it also logs to "/var/log/emerge- > fetch.log")? I meanwhile learned two things: 1. Running "emerge --ask ... | grep -v ..." does't work nicely, because after "emerge" has produced its output it doesn't immediately close its output stream, while "grep" waits for more input to fill its in- ternal buffer. So the pipe stalls without asking whether or not to continue and one has to blindly type "y" or "n". 2. By accidentally running an unrelated "wget" command without option "--quiet" I realized that these noisy progress messages most probably originate from a call to "wget" issued by "emerge" directly. So I appended the line "quiet = on" to file "/etc/wgetrc" and that real- ly suppressed all these progress messages. The only question remaining now is whether "emerge" calling "wget" without "--quiet" option is a bug or a feature. Opinions? Sincerely, Rainer
Re: [gentoo-user] Re: Suppressing some "emerge" output
On 10/23/24 12:35 PM, Dr Rainer Woitok wrote: > So I appended the line "quiet = on" to file "/etc/wgetrc" and that real- > ly suppressed all these progress messages. The only question remaining > now is whether "emerge" calling "wget" without "--quiet" option is a bug > or a feature. Opinions? An interactive user should be able to see how long they are going to wait for a download to complete. That's why wget defaults to this. If users wish to not have that feedback, they can define FETCHCOMMAND in make.conf to contain the --quiet flag. -- Eli Schwartz OpenPGP_signature.asc Description: OpenPGP digital signature
[gentoo-user] format usb as ext4
I format usb as ext4 mkfs.ext4 /dev/sda1 but XFCE does not automount the partition my other usb (ext4 as well) shows up automatically under /run/media/joseph/disk_name
Re: [gentoo-user] format usb as ext4
On Wed, Oct 23, 2024 at 10:35 PM syscon edm wrote: > It was my error, the command should be: > mkfs.ext4 /dev/sda > The usb was auto-mounted as soon as the command finished. > You can format the whole thing (/dev/sda) as one big ext4 volume, yes, but unless I'm very mistaken, that's not standard practice. USB storage devices usually have a partition table with one or more partitions defined. The first partition would be /dev/sda1, so the usual commands to format such a partition would use /dev/sda1, not /dev/sda. Since you're formatting it as ext4, I suppose you only intend to use this on Linux machines. I guess it's probably OK to format the whole device as ext4, without any partition table. However, I would definitely advise against it for any USB device you might use in a cross-platform environment. I have no idea whether you can skip the partition table and still be usable with computers running Windows or Mac OS or with embedded systems like home printers or commercial photo kiosks. -MD
Re: [gentoo-user] format usb as ext4
It was my error, the command should be: mkfs.ext4 /dev/sda The usb was auto-mounted as soon as the command finished. It has been some time since I run it, but looking at some documentation on-line a lot of instructions show to run: sudo mkfs.ext4 /dev/sdX1 eg: https://unix.stackexchange.com/questions/422656/how-to-make-an-ext4-formatted-usb-drive-with-full-rw-permissions-for-any-linux-m Even Google AI if one search: "gentoo format usb as ext4" it shows to run: sudo mkfs -t ext4 /dev/sdb1 this will work but the disk will not automount in XFCE, it should be: sudo mkfs.ext4 /dev/sdX On Wed, Oct 23, 2024 at 8:20 PM Mitchell Dorrell wrote: > On Wed, Oct 23, 2024, 20:35 syscon edm wrote: > >> I format usb as ext4 >> mkfs.ext4 /dev/sda1 >> >> but XFCE does not automount the partition >> my other usb (ext4 as well) shows up automatically under >> /run/media/joseph/disk_name >> > > I think you're correct that if something is automounting your USB storage > device, it's probably XFCE (or some part of it). > > I don't personally use XFCE, but I'm sure others here probably do. If you > don't get any responses on this mailing list, then perhaps try the > #gentoo-xfce IRC channel. If that's also quiet, you might try another venue > that focuses specifically on XFCE, such as the official XFCE links at > https://www.xfce.org/community . > > -Mitchell Dorrell > >>
