Re: [gentoo-user] Your opinion on jpeg encoders, please
On Mon, Jan 04, 2021 at 10:37:34PM +0100, Frank Steinmetzger wrote > > When I edit photos, I like to shrink and recompress them to save on > space, but not mangle them too much in the process to lose quality. Actually, shrinking *BY AN INTEGER NUMBER SHOULD IMPROVE QUALITY* as well as saving space. In Google look up the phrase... photography binning adjacent pixel If you bin a 3840x2160 image by 2, you'll get a 1920x1080 result. If you bin it by 3, you'll get 1280x720 image. The math is a bit convoluted, but when you bin by a value of "n"... * the information per combined pixel increases by a factor of "n" * the noise per combined pixel increases by a factor of square root of "n" So the "signal-to-noise-ratio" increases. The resulting image is less noisey. The tradeoff is that the new image is smaller than the original. I use the imagemagick "convert" utility from the commandline, but any capable image software should work. -- Walter Dnes I don't run "desktop environments"; I run useful applications
Re: [gentoo-user] Yet another USE flag problem
On 1/4/21 7:32 AM, Bertram Scharpf wrote: These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds built with USE flags to satisfy "dev-lua/luv[lua_single_target_luajit(-)?,lua_single_target_lua5-1(-)?,lua_single_target_lua5-2(-)?]". !!! One of the following packages is required to complete your request: - app-editors/neovim-0.4.4-r100::gentoo (Change USE: -lua_single_target_lua5-1, this change violates use flag constraints defined by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( lua_single_target_luajit lua_single_target_lua5-1 lua_single_target_lua5-2 )') (dependency required by "app-editors/neovim-0.4.4-r100::gentoo" [ebuild]) (dependency required by "neovim" [argument]) # emerge --info | grep -i lua 1 LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" USE="..." ... LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" ... USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." As far as I can see, only one is selected. Bertram Well, that's annoying, it doesn't show the package. How about `equery uses app-editors/neovim-0.4.4-r100` ? Note: You need app-portage/gentoolkit for equery. That should give you output like this: final flag setting for installation] [: I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-editors/neovim-0.4.4-r100: U I + - lto : Build with Link Time Optimization (LTO) + + lua_single_target_lua5-1 : Build for Lua 5.1 only - - lua_single_target_lua5-2 : Build for Lua 5.2 only - - lua_single_target_luajit : Build for LuaJIT only + - nvimpager: Install nvimpager symlink to less.sh macro + - tui : Build the neovim unix tui The "U" column indicates what USE flags are selected, and if it's already installed, the "I" column indicates what the installed package USE flags are. Dan
[gentoo-user] Your opinion on jpeg encoders, please
Hi all, this is not really a Gentoo-specific question, but some of you know your way around stuff, so here goes. When I edit photos, I like to shrink and recompress them to save on space, but not mangle them too much in the process to lose quality. So for average images I tend to use a quality setting between 80 and 86, very bad shots such as defocussed or blurred ones just 70. And for the really good ones (crystal sharp, portraits, extraordinary motives etc) 90 and more. In the far past I’ve been using Gimp, but for some years now mostly Showfoto (the editor from Digikam) due to its more useful photo enhancement features. However I noticed that the latter procuces larger files for the same quality setting. So currently, I first save with a very high setting from Showfoto and then recompress the whole directory in a one-line-loop using imagemagick’s convert. I have the impression that it produces far smaller files at the same visual quality. Now I know that one can’t fully compare quality settings of different encoders, but it started me wondering: which is really “better”? Or maybe just a little more enhanced, or up-to-date from an algorithmic standpoint? Just because many distros and tools use libjpeg, that doesn’t mean it’s the best one out there. Gimp, showfoto and convert use different encoders, because compressing the same PNG with the same JPEG setting does not result in three identical files. Does any of you have an opinion on that matter? Cheers. -- Gruß | Greetings | Qapla’ Please do not share anything from, with or about me on any social network. What do you call a man with a seagull on his head? – Cliff. signature.asc Description: PGP signature
[gentoo-user] Thunderbird - Unable to save your message as a draft.
With Thunderbird-78.6.0 I'm getting an error message when composing messages: Unable to save your message as a draft. Sending of the message failed. What is the solution? I've run onto few of them but they are mostly for Windows users not really applicable to Linux.
Re: [gentoo-user] Yet another USE flag problem
On Monday, 04. Jan 2021, 07:12:18 -0800, Daniel Frey wrote: > On 1/4/21 4:15 AM, Bertram Scharpf wrote: > > On Monday, 04. Jan 2021, 07:09:06 +0100, Arve Barsnes wrote: > > > On Mon, 4 Jan 2021 at 06:05, Bertram Scharpf > > > wrote: > > > > As far as I see, I defined _exactly_ _one_ _of_ them: > > > > > > Please show what USE flags you've defined for either this package or > > > LUA. Hard to give advice without knowing your config. > > > ># emerge --info | grep -i lua > >LUA_SINGLE_TARGET="lua5-1" > >LUA_TARGETS="lua5-1" > >USE="..." ... LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" ... > >USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." > > > ># grep -rnHi lua /etc/portage > >/etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit > >/etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit > >/etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit > >/etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit > >/etc/portage/package.accept_keywords/local:26: > ~amd64 > > > > Here's another time how emerge complains: > > > >- app-editors/neovim-0.4.4-r100::gentoo (Change USE: > > -lua_single_target_lua5-1, this change violates use flag constraints > > defined by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( > > lua_single_target_luajit lua_single_target_lua5-1 lua_single_target_lua5-2 > > )') > > > > As far as I understand this, emerge tells me to remove the > > use flag "lua_single_target_lua5-1" because the use flag > > "lua_single_target_lua5-1" is required. > > > > What could I try next? > > > > > > Bertram > > > > > > It looks like you have multiple lua USE-flags selected, and the package > requires only one to be selected. > > Whats the output of `emerge -pv neovim`? # emerge -pv neovim 1 These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds built with USE flags to satisfy "dev-lua/luv[lua_single_target_luajit(-)?,lua_single_target_lua5-1(-)?,lua_single_target_lua5-2(-)?]". !!! One of the following packages is required to complete your request: - app-editors/neovim-0.4.4-r100::gentoo (Change USE: -lua_single_target_lua5-1, this change violates use flag constraints defined by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( lua_single_target_luajit lua_single_target_lua5-1 lua_single_target_lua5-2 )') (dependency required by "app-editors/neovim-0.4.4-r100::gentoo" [ebuild]) (dependency required by "neovim" [argument]) # emerge --info | grep -i lua 1 LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" USE="..." ... LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" ... USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." As far as I can see, only one is selected. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: [gentoo-user] Yet another USE flag problem
Hi, On Monday, 04. Jan 2021, 15:12:24 +0100, Arve Barsnes wrote: > On Mon, 4 Jan 2021 at 14:46, Bertram Scharpf wrote: > > # grep -rnHi '^[^#]*lua' /etc/portage > > /etc/portage/make.conf:40:LUA_SINGLE_TARGET="luajit" # lua5-1 > > /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit > > /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit > > /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit > > /etc/portage/package.accept_keywords/local:26: >~amd64 > > # emerge --info | grep -i lua > > LUA_SINGLE_TARGET="luajit" > > LUA_TARGETS="lua5-1" > > USE="..." ... LUA_SINGLE_TARGET="luajit" LUA_TARGETS="lua5-1" ... > > USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." > > > > What else could I try? > > I would try removing both the make.conf entry and the dev-lua/luv USE entry. > > Maybe either of the other two packages with luajit are also involved, > but give the emerge command you're trying to run and any error > messages after doing that. This is the point where the whole problem arose from. I unmasked the newest NeoVim "app-editors/neovim-0.4.4-r100". Then: !!! The following update has been skipped due to unsatisfied dependencies: app-editors/neovim:0 selected: (app-editors/neovim-0.4.4:0/0::gentoo, installed) skipped: (app-editors/neovim-0.4.4-r100:0/0::gentoo, ebuild scheduled for merge) (see unsatisfied dependency below) !!! All ebuilds that could satisfy "dev-lang/lua:5.1" have been masked. !!! One of the following masked packages is required to complete your request: - dev-lang/lua-5.1.5-r106::gentoo (masked by: ~amd64 keyword) (dependency required by "app-editors/neovim-0.4.4-r100::gentoo[lua_single_target_lua5-1]" [ebuild]) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Unmasking the mentioned Lua version generates the error messages I posted above. Sorry that I cannot post the whole output of my command "emerge -avuND @world". In the meantime yet the next adversity shows up and I don't want to mix these two problems into one thread. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de
Re: [gentoo-user] Yet another USE flag problem
On 1/4/21 4:15 AM, Bertram Scharpf wrote: On Monday, 04. Jan 2021, 07:09:06 +0100, Arve Barsnes wrote: On Mon, 4 Jan 2021 at 06:05, Bertram Scharpf wrote: As far as I see, I defined _exactly_ _one_ _of_ them: Please show what USE flags you've defined for either this package or LUA. Hard to give advice without knowing your config. # emerge --info | grep -i lua LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" USE="..." ... LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" ... USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." # grep -rnHi lua /etc/portage /etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit /etc/portage/package.accept_keywords/local:26: It looks like you have multiple lua USE-flags selected, and the package requires only one to be selected. Whats the output of `emerge -pv neovim`? Dan
Re: [gentoo-user] Yet another USE flag problem
On Mon, 4 Jan 2021 at 14:46, Bertram Scharpf wrote: > # grep -rnHi '^[^#]*lua' /etc/portage > /etc/portage/make.conf:40:LUA_SINGLE_TARGET="luajit" # lua5-1 > /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit > /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit > /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit > /etc/portage/package.accept_keywords/local:26: ~amd64 > # emerge --info | grep -i lua > LUA_SINGLE_TARGET="luajit" > LUA_TARGETS="lua5-1" > USE="..." ... LUA_SINGLE_TARGET="luajit" LUA_TARGETS="lua5-1" ... > USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." > > What else could I try? I would try removing both the make.conf entry and the dev-lua/luv USE entry. Maybe either of the other two packages with luajit are also involved, but give the emerge command you're trying to run and any error messages after doing that. Regards, Arve
Re: [gentoo-user] Yet another USE flag problem
On Monday, 04. Jan 2021, 13:39:47 +0100, Arve Barsnes wrote: > On Mon, 4 Jan 2021 at 13:15, Bertram Scharpf wrote: > > # grep -rnHi lua /etc/portage > > /etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit > > /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit > > /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit > > /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit > > /etc/portage/package.accept_keywords/local:26: >~amd64 > > > > Here's another time how emerge complains: > > > > - app-editors/neovim-0.4.4-r100::gentoo (Change USE: > > -lua_single_target_lua5-1, this change violates use flag constraints > > defined by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( > > lua_single_target_luajit lua_single_target_lua5-1 lua_single_target_lua5-2 > > )') > > > > As far as I understand this, emerge tells me to remove the > > use flag "lua_single_target_lua5-1" because the use flag > > "lua_single_target_lua5-1" is required. > > As far as I understand it, this is saying that your emerge command is > about to remove that USE flag from neovim, which breaks the > constraint. So basically some other package is stopping your update. If this is what happens, then I miss that emerge tells me the reason why it tries to remove the use flag. > Your original mail mentioned that this was because of dev-lua/luv. You > have in your /etc/portage/package.use/zz-autouse set the luajit flag > on this package. Might this be the problem? > I'm not that familiar with lua, but as far as I understand the output, > app-editors/neovim and dev-lua/luv needs the same LUA_SINGLE_TARGET, > and setting that USE flag on dev-lua/luv might trip up this. Reading > the latest ebuild, this flag has been removed in the ~amd64 package, > so might as well remove it now and see if that fixes your problem. As the name of the file tells, the "zz-autouse" use flags were set a long time ago by - of course - emerge. I tried to remove them, but that didn't change anything. emerge: there are no ebuilds built with USE flags to satisfy "dev-lua/luv[lua_single_target_luajit(-)?,lua_single_target_lua5-1(-)?,lua_single_target_lua5-2(-)?]". !!! One of the following packages is required to complete your request: - app-editors/neovim-0.4.4-r100::gentoo (Change USE: -lua_single_target_lua5-1, this change violates use flag constraints defined by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( lua_single_target_luajit lua_single_target_lua5-1 lua_single_target_lua5-2 )') (dependency required by "app-editors/neovim-0.4.4-r100::gentoo" [ebuild]) (dependency required by "@selected" [set]) (dependency required by "@world" [argument]) # grep -rnHi '^[^#]*lua' /etc/portage /etc/portage/package.accept_keywords/local:26:=dev-lua/lpeg-1.0.1 luajit /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit /etc/portage/package.accept_keywords/local:26:http://www.bertram-scharpf.de
Re: [gentoo-user] Yet another USE flag problem
On Mon, 4 Jan 2021 at 13:15, Bertram Scharpf wrote: > # grep -rnHi lua /etc/portage > /etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit > /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit > /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit > /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit > /etc/portage/package.accept_keywords/local:26: ~amd64 > > Here's another time how emerge complains: > > - app-editors/neovim-0.4.4-r100::gentoo (Change USE: > -lua_single_target_lua5-1, this change violates use flag constraints defined > by app-editors/neovim-0.4.4-r100: 'exactly-one-of ( lua_single_target_luajit > lua_single_target_lua5-1 lua_single_target_lua5-2 )') > > As far as I understand this, emerge tells me to remove the > use flag "lua_single_target_lua5-1" because the use flag > "lua_single_target_lua5-1" is required. As far as I understand it, this is saying that your emerge command is about to remove that USE flag from neovim, which breaks the constraint. So basically some other package is stopping your update. Your original mail mentioned that this was because of dev-lua/luv. You have in your /etc/portage/package.use/zz-autouse set the luajit flag on this package. Might this be the problem? I'm not that familiar with lua, but as far as I understand the output, app-editors/neovim and dev-lua/luv needs the same LUA_SINGLE_TARGET, and setting that USE flag on dev-lua/luv might trip up this. Reading the latest ebuild, this flag has been removed in the ~amd64 package, so might as well remove it now and see if that fixes your problem. Regards, Arve
Re: [gentoo-user] Yet another USE flag problem
On Monday, 04. Jan 2021, 07:09:06 +0100, Arve Barsnes wrote: > On Mon, 4 Jan 2021 at 06:05, Bertram Scharpf wrote: > > As far as I see, I defined _exactly_ _one_ _of_ them: > > Please show what USE flags you've defined for either this package or > LUA. Hard to give advice without knowing your config. # emerge --info | grep -i lua LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" USE="..." ... LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" ... USE_EXPAND="... LUA_SINGLE_TARGET LUA_TARGETS ..." # grep -rnHi lua /etc/portage /etc/portage/make.conf:40:LUA_SINGLE_TARGET="lua5-1" # luajit /etc/portage/package.use/zz-autouse:3:>=dev-lua/lpeg-1.0.1 luajit /etc/portage/package.use/zz-autouse:6:>=dev-lua/mpack-1.0.4 luajit /etc/portage/package.use/zz-autouse:10:>=dev-lua/luv-1.30.1.1 luajit /etc/portage/package.accept_keywords/local:26:http://www.bertram-scharpf.de
Re: [gentoo-user] Gentoo chroot with old glibc
> > That's what I did: I found a 2017 stage3 with a still older glibc and > > managed to upgrade to a 2020 gentoo while masking the last glibc > > versions. That was tricky because I had to git-checkout intermediate > > versions of the portage tree in order to deal with the EAPI changes but > > I have a working chroot now. Thanks. > That's the easy way to do it, yes. > The hard way is to treat this as a cross-compilation problem and bootstrap > your own stages from scratch. Instructions would be a bit longer... > Andreas K. Hüttel I have looked through crossdev. Is that what it would take to cross-compile and bootstrap stages from scratch? Could that be done from (instead of an old glibc) musl, uClibc, or FreeBSD or NetBSD? Tom
Re: [gentoo-user] No sound after resuming from hibernation
On Monday, 4 January 2021 10:33:47 GMT Dr Rainer Woitok wrote: > Oh well, is there a replacement for ALSA? Can I use "pulseaudio" with- > out ALSA? > > Sincerely, > Rainer Without the alsa kernel driver available, the pulseaudio mixing controls won't be able to talk to the hardware. Does 'alsactl init' report something different after a cold reboot when sound works as expected, as opposed to after hibernation? Does your audio driver have a power saving function? modinfo will show this and you can enable/disable it, via /etc/modprobe.d/ - see here for more info: https://wiki.gentoo.org/wiki/Power_management/Soundcard Do you have alsasound service configured to run at boot? If so, does sound return if you restart the service after hibernation? Another thought: could it be the default audio device changes after restoring from hibernation? What I mean is, if your audio device has PCM and HDMI outputs, it may be the order is reversed for some unknown reason. If so, you should still have sound on one of the outputs. In this case, you could hardcode the order of the audio devices in /etc/asound.conf so the desired audio card output is always the default. If none of the above provide a solution, then it must be some MoBo/driver bug, which will need more involved debugging with the latest testing kernel version. signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] No sound after resuming from hibernation
Michael,
On Sunday, 2021-01-03 18:43:34 +, you wrote:
> ...
> > /usr/share/alsa/init/default:102: value write error: Input/output error
>
> The above on my system refers to headphone control:
>
> CTL{name}="Headphone Playback Switch",CTL{do_search}=="1", \
> CTL{values}="on"
>
> > /usr/share/alsa/init/default:263: value write error: Input/output error
> > /usr/share/alsa/init/default:263: value write error: Input/output error
>
> This refers to recording volume:
>
> CTL{name}="Capture Volume",CTL{do_search}=="1", \
> CTL{write}!="$env{cvolume}",CTL{values}="$env{cpercent}"
Same here.
> is your user a member of the audio group?
$ id
uid=1000(rainer) gid=1000(rainer)
groups=1000(rainer),7(lp),10(wheel),18(audio),19(cdrom),27(video),80(cdrw),85(usb),100(users),106(lpadmin),250(portage),272(plugdev),997(scanner)
$
> Are you able to unmute your settings, if muted, with alsamixer?
After running "alsactl init" the only settings muted in "alsamixer" are
"Master" and "Headphone", and yes, I can unmute both by pressing the "m"
key. But this does neither bring back sound nor does it change the out-
put from another "alsactl init".
> I recall an older alsa bug with some realtek driver, whereby to get their
> audio back some users had to suspend to RAM first. :-/ Yes, I know, it
> sounds like cargo-culting, but apparently it worked for them.
Oh well, is there a replacement for ALSA? Can I use "pulseaudio" with-
out ALSA?
Sincerely,
Rainer
