[gentoo-user] Re: Portage detects fake "world file problems" and packages that don't exist
Did that already. No additional info is shown. On 09/01/2022 01:03, Jack wrote: If nothing else, I would start by adding a --verbose to that emerge command. It may just confuse you worse, but it might add some useful info. On 2022.01.08 15:44, Nikos Chantziaras wrote: This is weird. When doing: emerge -auDU @world Portage says: !!! Problems have been detected with your world file !!! Please run emaint --check world !!! Ebuilds for the following packages are either all !!! masked or don't exist: media-sound/pavucontrol media-sound/pulseeffects sys-block/gparted Nothing to merge; quitting. My world file is fine and "emaint --check world" doesn't find anything. Also, all these packages that portage claims are masked or don't exist are not masked and they exist. This is on ~amd64. I'm stumped :-/
Re: [gentoo-user] Portage detects fake "world file problems" and packages that don't exist
If nothing else, I would start by adding a --verbose to that emerge command. It may just confuse you worse, but it might add some useful info. On 2022.01.08 15:44, Nikos Chantziaras wrote: This is weird. When doing: emerge -auDU @world Portage says: !!! Problems have been detected with your world file !!! Please run emaint --check world !!! Ebuilds for the following packages are either all !!! masked or don't exist: media-sound/pavucontrol media-sound/pulseeffects sys-block/gparted Nothing to merge; quitting. My world file is fine and "emaint --check world" doesn't find anything. Also, all these packages that portage claims are masked or don't exist are not masked and they exist. This is on ~amd64. I'm stumped :-/
[gentoo-user] Portage detects fake "world file problems" and packages that don't exist
This is weird. When doing: emerge -auDU @world Portage says: !!! Problems have been detected with your world file !!! Please run emaint --check world !!! Ebuilds for the following packages are either all !!! masked or don't exist: media-sound/pavucontrol media-sound/pulseeffects sys-block/gparted Nothing to merge; quitting. My world file is fine and "emaint --check world" doesn't find anything. Also, all these packages that portage claims are masked or don't exist are not masked and they exist. This is on ~amd64. I'm stumped :-/
[gentoo-user] Re: yt-dlp config file different than old youtube-dl
On 08/01/2022 07:26, Dale wrote: This is the line from the old youtube-dl.conf that worked for it: --format 'bestvideo[ext=webm,ext=mp4][width<=?1280]+bestaudio/best' The "--format-sort" option is much better for this. To prefer 720p video or lower, but not higher: --format-sort=width:1280,height:720,vcodec:av1 The AV1 codec preference is nowadays default, but I like to specify it anyway. AV1 has the smallest video size but at the same time the highest video quality as well. If AV1 is not available, it will fall back to VP9 (higher quality, bigger size,) and then to H.264 (lower quality, smaller size.)
Re: [gentoo-user] yt-dlp config file different than old youtube-dl
Arve Barsnes wrote: > On Sat, 8 Jan 2022 at 06:27, Dale wrote: >> The part it really doesn't like seems to be this: >> >> SyntaxError: Invalid filter specification 'ext=webm,ext=mp4' >> >> Can someone tell me what the new and improved yt-dlp wants in its conf >> file to try for mp4 first and then webm? Nothing I tried seems to >> work. :-( > I have never used extension filtering before, but it might not be > possible to specify a list, so then you need to make one extra format > in your syntax. This worked for me: > > --format > 'bv*[ext=webm][width<=?1280]+bestaudio/bv*[ext=mp4][width<=?1280]+bestaudio/best' > > Regards, > Arve > > That doesn't spit on my keyboard so it's a good start at least. Time will tell. It's currently downloading a webm video. I'd prefer a mp4 but it may not be available for that video. Time will tell tho. Later on it might grab a mp4 and then I'll know it is getting mp4 when it can. Honestly tho, webm does work well. Thanks much. Will post updates later on how it's doing. I'm also going to study that to see if I can grasp what its doing. What's different about it. Dale :-) :-) P. S. Can't wait for fiber internet to get here. They ran the cable a while back. It's getting closer. :-D
Re: [gentoo-user] Re: X11 crashes anyone?
On Thursday, 6 January 2022 16:51:49 GMT Nikos Chantziaras wrote: > On 26/12/2021 09:34, Nikos Chantziaras wrote: > > On 21/12/2021 08:50, Ionen Wolkens wrote: > >> On Tue, Dec 21, 2021 at 08:31:55AM +0200, Nikos Chantziaras wrote: > >>> Seems to be a different issue then. I'm on an nvidia card using the > >>> binary driver, and there's no problems like the ones you're having. It's > >>> a straight disappearance of the desktop here when it happens due to the > >>> X11 process segfault. > >> > >> [...] > >> > >> With 495.44-r2 and 495.46-r10, Xorg log may have a backtrace > >> mentioning libnvidia-glcore.so, if so try 495.46-r0. > > > > Just got another one. I was smart enough this time to save > > Xorg.0.log.old before it gets overwritten. No mention of nvidia anywhere: > > > > [ 47526.314] (EE) Backtrace: > > [ 47526.321] (EE) 0: /usr/bin/X (xorg_backtrace+0x5b) [0x55c605c611cb] > > [ 47526.321] (EE) 1: /usr/bin/X (0x55c605b16000+0x14f0f5) [0x55c605c650f5] > > [ 47526.321] (EE) 2: /lib64/libpthread.so.0 (0x7fd0097df000+0x12660) > > [0x7fd0097f1660] > > [ 47526.321] (EE) 3: /lib64/libc.so.6 (0x7fd00961c000+0x15b0b3) > > [...] > > [ 47526.321] (EE) Segmentation fault at address 0x7fff46403180 > > > > [...] > > > > I guess I'll just downgrade the nvidia drivers to 470.94 anyway and see > > if it happens again. > > It just happened again with 470.94. :-/ Just an idea, have you tried rebuilding sys-libs/glibc and xorg, since this is what it barfs at as it segfaults? signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] yt-dlp config file different than old youtube-dl
On Sat, 8 Jan 2022 at 06:27, Dale wrote: > The part it really doesn't like seems to be this: > > SyntaxError: Invalid filter specification 'ext=webm,ext=mp4' > > Can someone tell me what the new and improved yt-dlp wants in its conf > file to try for mp4 first and then webm? Nothing I tried seems to > work. :-( I have never used extension filtering before, but it might not be possible to specify a list, so then you need to make one extra format in your syntax. This worked for me: --format 'bv*[ext=webm][width<=?1280]+bestaudio/bv*[ext=mp4][width<=?1280]+bestaudio/best' Regards, Arve