Description of problem: Version-Release number of selected component (if applicable): gimp 2.10.36-1.mga9 x86_64 How reproducible:when you load gimp you can read anything at each time i use Kernel 6.6.14-desktop-2.mga9 Steps to Reproduce: 1.Load gimp 2. 3.
Summary: its impossible to read the items of the drop down menu of gimp the letters are too too small (minuscule in french) => its impossible to read the items of the drop down menu of gimp the letters are too too small (minuscules in french)
Sorry to have left you. A few basic questions: What Desktop are you using? Does its own settings have anything relevant? (Plasma at least does: System Setting-Appearance-Fonts). I have just been quickly through Gimp's 'parameters', but cannot see anything there; but do have a look there if you can. (Gimp menus fine here). If you can find out, say what Theme you are using. Is only Gimp affected? Please post the output of (terminal): $ inxi -Gxx
CC: (none) => lewyssmith
Can anyone with a French language system confirm this?
Hi, I have already told that i use Kernel 6.6.14-desktop-2.mga9 I use my computer in double boot (mageia 9/ win 7) and the same version of Gimp work perfectly with win 7 With The Mageia9 gimp 2.10.36-1.mga9 x86_64 I can't reach the Gimp' parameters because i can't read any word of the drops menus . No problem with the settings of plasma Gimp is the only program affected $ inxi -Gxx Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750] vendor: ASUSTeK driver: nvidia v: 535.154.05 arch: Maxwell pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1381 Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X: loaded: nvidia,v4l gpu: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 1360x768 s-dpi: 30 Monitor-1: HDMI-0 res: 1360x768 dpi: 22 diag: 1836mm (72.27") API: OpenGL v: 4.6.0 NVIDIA 535.154.05 renderer: NVIDIA GeForce GTX 750/PCIe/SSE2 direct-render: Yes i have no connection with other French users(In reply to Lewis Smith from comment #2) (In reply to Lewis Smith from comment #1) > Sorry to have left you. > > A few basic questions: > What Desktop are you using? > Does its own settings have anything relevant? (Plasma at least does: System > Setting-Appearance-Fonts). > I have just been quickly through Gimp's 'parameters', but cannot see > anything there; but do have a look there if you can. (Gimp menus fine here). > If you can find out, say what Theme you are using. > Is only Gimp affected? > > Please post the output of (terminal): > $ inxi -Gxx (In reply to Lewis Smith from comment #2) > Can anyone with a French language system confirm this? (In reply to Lewis Smith from comment #1) > Sorry to have left you. > > A few basic questions: > What Desktop are you using? > Does its own settings have anything relevant? (Plasma at least does: System > Setting-Appearance-Fonts). > I have just been quickly through Gimp's 'parameters', but cannot see > anything there; but do have a look there if you can. (Gimp menus fine here). > If you can find out, say what Theme you are using. > Is only Gimp affected? > > Please post the output of (terminal): > $ inxi -Gxx (In reply to Lewis Smith from comment #1) > Sorry to have left you. > > A few basic questions: > What Desktop are you using? > Does its own settings have anything relevant? (Plasma at least does: System > Setting-Appearance-Fonts). > I have just been quickly through Gimp's 'parameters', but cannot see > anything there; but do have a look there if you can. (Gimp menus fine here). > If you can find out, say what Theme you are using. > Is only Gimp affected? > > Please post the output of (terminal): > $ inxi -Gxx
If you create a new user and log in as that, do the problem appear there too?
CC: (none) => fri
Not sure if I understand the bug I force the installation for French language for gimp Force start gimp in French LANGUAGE=fr gimp and take this screenshot https://www.imagebam.com/view/MESB1EO , looks well for me
When i force start gimp in French with $ LANGUAGE=fr gimp This is what i see when gimp start https://www.imagebam.com/view/MESB39U The menu is not readable in the terminal there's a message : Warning: Unknown input_id: -1 for input: surfacemap_x
(In reply to katnatek from comment #5) > and take this screenshot https://www.imagebam.com/view/MESB1EO , looks well > for me Same here. I never had any problem with the font size in Gimp.
(In reply to Gilbert BONNET from comment #6) > When i force start gimp in French with $ LANGUAGE=fr gimp > > This is what i see when gimp start > > https://www.imagebam.com/view/MESB39U > > The menu is not readable > > in the terminal there's a message : > > Warning: Unknown input_id: -1 for input: surfacemap_x I get that warning too so is not related with bug Is a clean installation or an upgrade from mageia 8?
(In reply to katnatek from comment #8) > (In reply to Gilbert BONNET from comment #6) > > When i force start gimp in French with $ LANGUAGE=fr gimp > > > > This is what i see when gimp start > > > > https://www.imagebam.com/view/MESB39U > > > > The menu is not readable > > > > in the terminal there's a message : > > > > Warning: Unknown input_id: -1 for input: surfacemap_x > > I get that warning too so is not related with bug > > > Is a clean installation or an upgrade from mageia 8? It's an upgrade from Mageia 8.
See if you have mga8 packages that could make some noise What is the output of rpm -qa|grep mga8
(In reply to katnatek from comment #10) > See if you have mga8 packages that could make some noise > > What is the output of > > rpm -qa|grep mga8 A lot of package Mageia8 appears !! What can i do ?
Try update from console urpmi --auto-update --auto --force See if the # of mga8 package is less than before (and if you still have the issue), dump the list to a file rpm -qa|grep mga8 > mg8list.txt Attach the list in this bug
lib64boost_iostreams1.75.0-1.75.0-1.mga8 lib64plasmacomicprovidercore1-5.20.4-1.mga8 ndiswrapper-1.63-2.mga8 lib64boost_locale1.75.0-1.75.0-1.mga8 lib64yui12-mga-ncurses-1.1.0-4.mga8 lib64kpimimportwizard5-20.12.0-1.mga8 lib64opencv_highgui4.5-4.5.1-1.3.mga8https://www.imagebam.com lib64kf5akonadisearchpim5-20.12.0-1.mga8 lib64kdeconnectcore20-20.12.0-1.mga8 lib64hd21-21.71-1.mga8 lib64kwaylandserver5-5.20.4-1.mga8 lib64gupnp-igd1.0_4-1.2.0-1.mga8 lib64poppler105-20.12.1-1.4.mga8 lib64qalculate21-3.15.0-2.mga8 lib64irs161-9.11.37-1.1.mga8 lib64ilmimf2_5_25-2.5.7-1.3.mga8 lib64kf5identitymanagement5-20.12.0-1.mga8 lib64kf5pulseaudioqt_2-1.2-3.mga8 lib64cfitsio9-3.490-1.mga8 lib64kpimaddressbookimportexport5-20.12.0-1.mga8 lib64boost_filesystem1.75.0-1.75.0-1.mga8 lib64k3blib7-20.12.0-1.mga8 lib64pulsecore14.2-14.2-2.1.mga8 lib64kf5tnef5-20.12.0-1.mga8 lib64kwin4_effect_builtins1-5.20.4-3.mga8 lib64kf5messagelist5-20.12.0-1.1.mga8 lib64kmailgrammalecte5-20.12.0-2.mga8 lib64akonadiprivate5-20.12.0-1.mga8 lib64opencv_video4.5-4.5.1-1.3.mga8 lib64kpimsmtp5-20.12.0-1.mga8 lib64vpx6-1.9.0-1.mga8 lib64git2_1.1-1.1.0-1.mga8 lib64kf5mime5-20.12.0-1.mga8 lib64kpimgapicalendar5-20.12.0-1.mga8 lib64ccolamd2-4.4.6-4.mga8 lib64avcodec58-4.3.6-1.mga8.tainted lib64kwinxrenderutils12-5.20.4-3.mga8 lib64unistring2-0.9.10-4.mga8 lib64kf5messagecore5-20.12.0-1.1.mga8 lib64boost_date_time1.75.0-1.75.0-1.mga8 lib64boost_thread1.75.0-1.75.0-1.mga8 lib64mjpegtools2.1_0-2.1.0-6.mga8 lib64k3bdevice7-20.12.0-1.mga8 lib64avresample4-4.3.6-1.mga8.tainted lib64kf5mailimporter5-20.12.0-1.mga8 lib64qt5webkitwidgets5-5.212.0-1.alpha4.6.mga8 lib64grammarcommon5-20.12.0-2.mga8 lib64kf5akonadicore5-20.12.0-1.mga8 lib64kf5pimtextedit5-20.12.0-1.mga8 lib64boost_system1.75.0-1.75.0-1.mga8 lib64kf5mailtransport5-20.12.0-1.mga8 lib64kf5calendarutils5-20.12.0-1.mga8 lib64avutil56-4.3.6-1.mga8.tainted lib64kmaillanguagetool5-20.12.0-2.mga8 lib64kf5akonadisearchxapian5-20.12.0-1.mga8 lib64opencv_core4.5-4.5.1-1.3.mga8 lib64gupnp1.2_0-1.2.4-1.1.mga8 lib64protobuf-lite25-3.14.0-1.2.mga8 lib64tiff5-4.2.0-1.15.mga8 lib64pulsecommon14.2-14.2-2.1.mga8 lib64kdsoap1-1.10.0-1.mga8 lib64dav1d5-0.8.0-1.mga8 lib64kf5kscreen7-5.20.4-1.mga8 lib64yui12-mga-qt-1.1.0-4.mga8 lib64qgpgme7-1.15.0-2.mga8 lib64microdns0-0.1.2-1.mga8 lib64kf5akonadimime5-20.12.0-1.mga8 lib64kpimgapicontacts5-20.12.0-1.mga8 lib64colamd2-4.4.6-4.mga8 lib64kf5kontactinterface5-20.12.0-1.mga8 lib64kf5mbox5-20.12.0-1.mga8 lib64postproc55-4.3.6-1.mga8.tainted lib64cholmod3-4.4.6-4.mga8 lib64aom2-2.0.1-3.5.mga8 lib64isl15-0.18-2.mga8 lib64kf5mimetreeparser5-20.12.0-1.1.mga8 lib64magick-7Q16HDRI_9-7.0.10.62-1.mga8.tainted lib64opencv_flann4.5-4.5.1-1.3.mga8 lib64opencv_calib3d4.5-4.5.1-1.3.mga8 lib64dns1115-9.11.37-1.1.mga8 lib64lwres161-9.11.37-1.1.mga8 lib64kcolorpicker0.1.4-0.1.4-2.mga8 lib64flac8-1.3.3-3.1.mga8 lib64kpmcore10-20.12.0-1.mga8 lib64kdeconnectpluginkcm20-20.12.0-1.mga8 lib64kwineffects12-5.20.4-3.mga8 kwayland-server-5.20.4-1.mga8 lib64wacom2-1.7-2.mga8 lib64kf5webengineviewer5-20.12.0-1.1.mga8 lib64yui12-3.10.0-3.mga8 lib64ruby2.7-2.7.7-33.6.mga8 lib64kf5akonadiwidgets5-20.12.0-1.mga8 lib64molletnetwork5_20-20.12.0-2.mga8 lib64kf5grantleetheme5-20.12.0-1.mga8 lib64suitesparseconfig4-4.4.6-4.mga8 lib64icu68-68.2-1.1.mga8 lib64kf5mailtransportakonadi5-20.12.0-1.mga8 lib64gpsd29-3.23-1.mga8 lib64kf5mailimporterakonadi5-20.12.0-1.mga8 lib64opencv_features2d4.5-4.5.1-1.3.mga8 lib64protobuf25-3.14.0-1.2.mga8 smtube-20.6.0-2.mga8 lib64qt5webkit5-5.212.0-1.alpha4.6.mga8 lib64pcre2posix2-10.36-1.1.mga8 lib64kf5akonadinotes5-20.12.0-1.mga8 lib64ffi7-3.3-2.mga8 apache-commons-daemon-jsvc-1.2.2-3.mga8 lib64lua5.3-5.3.5-5.mga8 lib64openssl1.1-1.1.1v-1.mga8 lib64kf5messageviewer5-20.12.0-1.1.mga8 lib64kf5messagecomposer5-20.12.0-1.1.mga8 lib64yui12-ncurses-2.55.0-2.mga8 lib64okular5core9-20.12.0-1.mga8 lib64kf5akonadicontact5-20.12.0-1.mga8 gstreamer1.0-ofa-1.18.5-1.mga8.tainted lib64kpimgapitasks5-20.12.0-1.mga8 lib64camd2-4.4.6-4.mga8 lib64kf5akonadicalendar5-20.12.0-1.mga8 lib64swresample3-4.3.6-1.mga8.tainted lib64opencv_imgcodecs4.5-4.5.1-1.3.mga8 lib64dns1114-9.11.31-1.1.mga8 lib64bind9_161-9.11.37-1.1.mga8 lib64torrent-rasterbar10-1.2.13-1.mga8 lib64kdeconnectinterfaces20-20.12.0-1.mga8 lib64kf5akonadisearchcore5-20.12.0-1.mga8 lib64kwinglutils12-5.20.4-3.mga8 lib64gs9-9.53.3-2.6.mga8 lib64boost_regex1.75.0-1.75.0-1.mga8 lib64isccfg163-9.11.37-1.1.mga8 lib64kpimpkpass5-20.12.0-1.mga8 lib64kf5ldap5-20.12.0-1.mga8 lib64nfs13-4.0.0-3.mga8 lib64kf5libkleo5-20.12.0-1.mga8 lib64kpimitinerary5-20.12.0-1.mga8 lib64amd2-4.4.6-4.mga8 lib64x264_157-0.157-0.20191217.stable.2.mga8.tainted lib64kf5gravatar5-20.12.0-1.mga8 lib64filezilla15-0.30.0-1.mga8 lib64gssdp1.2_0-1.2.3-1.mga8 lib64swscaler5-4.3.6-1.mga8.tainted lib64konsoleprivate20-20.12.0-1.mga8 lib64zxing1-1.1.1-2.1.mga8 lib64yui12-mga-1.1.0-3.mga8 lib64opencv_imgproc4.5-4.5.1-1.3.mga8 lib64mlt++3-6.24.0-2.mga8 lib64opencv_objdetect4.5-4.5.1-1.3.mga8 lib64kf5imap5-20.12.0-1.mga8 lib64jasper4-2.0.27-1.1.mga8 lib64kpimgapicore5-20.12.0-1.mga8 lib64kf5akonadisearchdebug5-20.12.0-1.mga8 lib64kf5mailcommon5-20.12.0-1.mga8 lib64kdecorations2private7-5.20.4-1.mga8 lib64botan2_17-2.17.3-2.2.mga8 lib64kf5templateparser5-20.12.0-1.1.mga8 lib64kf5akonadixml5-20.12.0-1.mga8 lib64yui12-qt-2.53.0-6.mga8 lib64opencv_dnn4.5-4.5.1-1.3.mga8 lib64qpdf28-10.1.0-1.mga8 lib64flac++6-1.3.3-3.1.mga8 lib64kimageannotator0.4.0-0.4.0-2.mga8 lib64kf5contacteditor5-20.12.0-1.mga8 lib64ilmbase2_5_25-2.5.7-1.3.mga8 lib64kf5libkdepim5-20.12.0-1.mga8 lib64lua5.2-5.2.4-7.mga8 lib64bpf0-5.15.126-1.mga8 lib64kerfuffle20-20.12.0-1.mga8 lib64mlt6-6.24.0-2.mga8 lib64isc1107-9.11.37-1.1.mga8 lib64kf5akonadiagentbase5-20.12.0-1.mga8 icu68-data-68.2-1.1.mga8 (In reply to katnatek from comment #12) > Try update from console > > urpmi --auto-update --auto --force > > > See if the # of mga8 package is less than before (and if you still have the > issue), dump the list to a file > > rpm -qa|grep mga8 > mg8list.txt > > Attach the list in this bug
I have to go see you tomorrow Thanks a lot
Morgan you report also you have a lot of mga8 packages after the upgrade, some advice you can provide ?
These packages (.mg8) are not visible via the CCM. Are they useful and required for Mageia 9 If not, where are they hidden to try to erase them ?
(In reply to katnatek from comment #15) > Morgan you report also you have a lot of mga8 packages after the upgrade, > some advice you can provide ? To make sure all packages are updated to correct version, try https://wiki.mageia.org/en/Mageia_9_Errata#Synchronizing_from_development_to_release https://wiki.mageia.org/en/Using_DNF#Synchronize_with_repos However this will still leave extra mga8 packages installed. For a nice list: $ urpmq --not-available | grep .mga8 | sort One of my laptops have 171 .mga8 packages. I have not detected they cause any problems. More info see https://wiki.mageia.org/en/Mageia_9_Errata#Unused_packages I guess there exist a smart way to remove all by a smart command but that is above my knowledge. I asked about it but got no answer: in [qa-discuss] list 17 Feb 2024 "Synchronising with repos"
(In reply to Morgan Leijström from comment #17) > I guess there exist a smart way to remove all by a smart command but that is > above my knowledge. in a terminal one can do: rpms_tbe=$(rpm -qa --last | grep .mga8. | cut -d' ' -f1 | xargs printf '%s ' ) printf '%s\n' $rpms_tbe urpme --test $rpms_tbe Explanation: 1. generate the list of packages: "rpm" lists all packages by full name, arch included, "grep"/"cut" identifies and generates the list of packages while "printf" formats the list. 2. print the list of packages for review 3. test the removal, remove "--test" when you are sure the list is fine.
CC: (none) => arusanu
Thank you Aurelian, I will test it and add to https://wiki.mageia.org/en/Using_DNF#Synchronize_with_repos As the procedure at that URL use DNF, is there a smart switch to use to extend the commands already used there, or should we just provide a DNF alternative version of your point 3 (for users perferring DNF)
I'm not that familiar with dnf. Although, removal with dnf should work similarly by executing "dnf remove" instead of "urpme". I'm not aware of a "dnf" option for testing only as urpme has.
(In reply to Aurelian R from comment #18) > (In reply to Morgan Leijström from comment #17) > > I guess there exist a smart way to remove all by a smart command but that is > > above my knowledge. > > in a terminal one can do: > > rpms_tbe=$(rpm -qa --last | grep .mga8. | cut -d' ' -f1 | xargs printf '%s ' > ) > printf '%s\n' $rpms_tbe > urpme --test $rpms_tbe > I think is more direct urpme --test $(rpm -qa|grep mga8)
I have just had a look at my M9 system upgraded from M8, and find loads of .mga8 pkgs. I tested a few of these, and they were all cases of pkgs whose *names incorporate a version* which became superseded. Examples (shorter names are MGA9): lib64protobuf-lite25-3.14.0-1.mga8 lib64protobuf-lite32 lib64gepub0.6_0-0.6.0-5.mga8 lib64gepub0.7_0 lib64opencv_flann4.5-4.5.1-1.3.mga8 lib64opencv_flann406 lib64dmapsharing3.0_2-2.9.41-2.mga8 lib64dmapsharing4.0_3 This is a perennial problem... My guess is that these replaced pkgs are not used by the M9 system, and can be removed. Aurelian's comment 18 is neat, calling urpme just once with the entire list of M8 pkgs. Re stage 3 "urpme --test $rpms_tbe ... test the removal, remove "--test" when you are sure the list is fine", look for any threat to remove a dependant 'mga9' pkg. You can use --auto with urpme to avoid prompts. I tried a loop which called urpme repeatedly for each mga8 pkg, and it took ages. I checked that for each M8 pkg wanting to remove others, that those were all M8. And did a cross-check that 'mga9' got no mention among them. When I took the plunge and deleted the whole lot, the process was peppered with mention of a redundant mga9 kernel! But all this is academic. I doubt that residual M8 pkgs are the problem if non are required by any M9 package. Have we yet suggested removing Gimp, and deleting ~/.cache/gimp and ~/.config/GIMP ; then re-installing Gimp?
(In reply to Lewis Smith from comment #22) > I have just had a look at my M9 system upgraded from M8, and find loads of > .mga8 pkgs. I tested a few of these, and they were all cases of pkgs whose > *names incorporate a version* which became superseded. Examples (shorter > names are MGA9): > lib64protobuf-lite25-3.14.0-1.mga8 > lib64protobuf-lite32 > lib64gepub0.6_0-0.6.0-5.mga8 > lib64gepub0.7_0 > lib64opencv_flann4.5-4.5.1-1.3.mga8 > lib64opencv_flann406 > lib64dmapsharing3.0_2-2.9.41-2.mga8 > lib64dmapsharing4.0_3 > > This is a perennial problem... My guess is that these replaced pkgs are not > used by the M9 system, and can be removed. > Aurelian's comment 18 is neat, calling urpme just once with the entire list > of M8 pkgs. > Re stage 3 "urpme --test $rpms_tbe ... test the removal, remove "--test" > when you are sure the list is fine", look for any threat to remove a > dependant 'mga9' pkg. You can use --auto with urpme to avoid prompts. > > I tried a loop which called urpme repeatedly for each mga8 pkg, and it took > ages. I checked that for each M8 pkg wanting to remove others, that those > were all M8. And did a cross-check that 'mga9' got no mention among them. > When I took the plunge and deleted the whole lot, the process was peppered > with mention of a redundant mga9 kernel! > > But all this is academic. I doubt that residual M8 pkgs are the problem if > non are required by any M9 package. > > Have we yet suggested removing Gimp, and deleting > ~/.cache/gimp and > ~/.config/GIMP > ; then re-installing Gimp? Morgan did ask to try with new user BTW are reported conflict with some of the packages bug#31586,this sound to me like the clamav report bug#32908 new packages that not remove the old ones
(In reply to Lewis Smith from comment #22) > I have just had a look at my M9 system upgraded from M8, and find loads of > .mga8 pkgs. I tested a few of these, and they were all cases of pkgs whose > *names incorporate a version* which became superseded. Examples (shorter > names are MGA9): > lib64protobuf-lite25-3.14.0-1.mga8 > lib64protobuf-lite32 > lib64gepub0.6_0-0.6.0-5.mga8 > lib64gepub0.7_0 > lib64opencv_flann4.5-4.5.1-1.3.mga8 > lib64opencv_flann406 > lib64dmapsharing3.0_2-2.9.41-2.mga8 > lib64dmapsharing4.0_3 > > This is a perennial problem... My guess is that these replaced pkgs are not > used by the M9 system, and can be removed. > Aurelian's comment 18 is neat, calling urpme just once with the entire list > of M8 pkgs. > Re stage 3 "urpme --test $rpms_tbe ... test the removal, remove "--test" > when you are sure the list is fine", look for any threat to remove a > dependant 'mga9' pkg. You can use --auto with urpme to avoid prompts. > > I tried a loop which called urpme repeatedly for each mga8 pkg, and it took > ages. I checked that for each M8 pkg wanting to remove others, that those > were all M8. And did a cross-check that 'mga9' got no mention among them. > When I took the plunge and deleted the whole lot, the process was peppered > with mention of a redundant mga9 kernel! > > But all this is academic. I doubt that residual M8 pkgs are the problem if > non are required by any M9 package. > > Have we yet suggested removing Gimp, and deleting > ~/.cache/gimp and > ~/.config/GIMP > ; then re-installing Gimp? I have removed Gimp and deleteted ~/.cache/gimp and ~/.config/GIMP No change after the re-installation :(
(In reply to Gilbert BONNET from comment #24) > I have removed Gimp and deleteted ~/.cache/gimp and ~/.config/GIMP > No change after the re-installation :( So maybe inflicted by the desktop system, maybe a setting for the whole desktop, or the user. So you could try as another user, if that do not help install another desktop - maybe Gnome. And yes could try removing the mga8 packages. Have you searched internet for other users seeing the problem, maybe search or ask on a Gimp forum?
Another test is to boot your system with a Mageia 9 Live USB stick and launch Gimp. IIRC Gimp is included in all, even in Xfce, so that is a way to try fresh user and different desktops without messing with your system. If you want to try with updates, see https://wiki.mageia.org/en/Persistent_live_systems
Reporter has a pretty large screen(72") with low resolution so one test will be to connect a smaller size monitor/tv 20"-32" and see if the issue persists.
Between the output of urpmq --requires-recursive gimp lib64poppler-glib8 lib64poppler126 So the presence of lib64poppler105-20.12.1-1.4.mga8 could be the issue As long as you have packages not present in mageia 9: smtube and ndiswrapper. try just urpme lib64poppler105-20.12.1-1.4.mga8 Does gimp works well now?
urpmq --requires-recursive Gimp | grep mga8 $ urpmq --requires-recursive gimp | grep mga8 $ on my system shows nothing - fortunately. $ urpmq --requires-recursive gimp | grep lib64poppler lib64poppler-glib8 lib64poppler126 Interesting suggestion above. Can be tested with $ rpm -qa | grep lib64poppler which will show whether one or both library version are present; although what they might have to do with the problem is very questionable. (In reply to Aurelian R from comment #27) > Reporter has a pretty large screen(72") with low resolution so one test will > be to connect a smaller size monitor/tv 20"-32" and see if the issue > persists. This looks nearer the nub of the matter. Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750] vendor: ASUSTeK driver: nvidia v: 535.154.05 arch: Maxwell pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1381 Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X: loaded: nvidia,v4l gpu: nvidia display-ID: :0 screens: 1 Screen-1: 0 s-res: 1360x768 s-dpi: 30 Monitor-1: HDMI-0 res: 1360x768 dpi: 22 diag: 1836mm (72.27") API: OpenGL v: 4.6.0 NVIDIA 535.154.05 renderer: NVIDIA GeForce GTX 750/PCIe/SSE2 direct-render: Yes Yes, Gilbert, if you can try a different screen, that is certainly worth trying.
(In reply to Lewis Smith from comment #29) > urpmq --requires-recursive Gimp | grep mga8 > $ urpmq --requires-recursive gimp | grep mga8 > $ > on my system shows nothing - fortunately. > > $ urpmq --requires-recursive gimp | grep lib64poppler > lib64poppler-glib8 > lib64poppler126 > Interesting suggestion above. Can be tested with > $ rpm -qa | grep lib64poppler > which will show whether one or both library version are present; although > what they might have to do with the problem is very questionable. Perhaps you are right and is not the cause Name : lib64poppler126 Version : 23.02.0 Release : 1.1.mga9 Group : System/Libraries Size : 3781912 Architecture: x86_64 Source RPM : poppler-23.02.0-1.1.mga9.src.rpm URL : https://poppler.freedesktop.org Summary : PDF rendering library Description : Poppler is a PDF rendering library based on the xpdf-3.0 code base.
FWIW Gimp menus etc displays OK here, same GPU, rather big screen, Plasma X11 Upgraded from mga8, but well synced, mga8 packages removed, and some from updates testing, as well as having tainted repos. [morgan@svarten ~]$ inxi --edid Graphics: Device-1: NVIDIA GM107 [GeForce GTX 750] vendor: eVga.com. driver: nvidia v: 550.54.14 alternate: nvidiafb, nouveau, nvidia_drm, nvidia_current non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-19 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: none off: DP-1 empty: DVI-I-1,HDMI-A-1 bus-ID: 07:00.0 chip-ID: 10de:1381 class-ID: 0300 Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X: loaded: nvidia,v4l gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 103 s-size: 947x533mm (37.28x20.98") s-diag: 1087mm (42.78") Monitor-1: DP-1 note: disabled model: Philips PHL 436M6VBP serial: 7968 built: 2018 res: 3840x2160 hz: 60 dpi: 104 gamma: 1.2 chroma: red: x: 0.690 y: 0.302 green: x: 0.243 y: 0.710 blue: x: 0.153 y: 0.059 white: x: 0.314 y: 0.329 size: 941x529mm (37.05x20.83") diag: 1080mm (42.5") ratio: 16:9 modes: 3840x2160, 1920x2160, 2560x1440, 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x960, 1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480 EDID-Warnings: 1: parse_edid: unhandled CEA mode 96 2: parse_edid: unhandled CEA mode 97 API: OpenGL v: 4.6.0 NVIDIA 550.54.14 renderer: NVIDIA GeForce GTX 750/PCIe/SSE2 direct-render: Yes
(In reply to Lewis Smith from comment #1) > Sorry to have left you. > > A few basic questions: > What Desktop are you using? > Does its own settings have anything relevant? (Plasma at least does: System > Setting-Appearance-Fonts). > I have just been quickly through Gimp's 'parameters', but cannot see > anything there; but do have a look there if you can. (Gimp menus fine here). > If you can find out, say what Theme you are using. > Is only Gimp affected? > > Please post the output of (terminal): > $ inxi -Gxx Gimp is not guilty, Freetux have also the same problem. I should have checked that straight away I am really sorry
Freetux and GIMP are using gtk+2.0. Maybe some other gtk+2 programs present similar symptoms. Something like "viewnior" or "lshw-gui".
(In reply to Gilbert BONNET from comment #16) > These packages (.mg8) are not visible via the CCM. > > Are they useful and required for Mageia 9 > > If not, where are they hidden to try to erase them ? I find a way to make more easy to make it visible In MCC -> Install % Remove Software, in the Options menu check Search in full packages names , also make sure both Drop down filters select All, then in the search box type mga8 and run the search
GTK+2: another good idea. Just to poke it: $ urpmq --whatrequires gtk+2.0 gracket lib64gtk+-x11-2.0_0 lib64gtk2-theme-engines perl-Gimp perl-Gtk2 perl-Gtk2-TrayIcon uim-gtk $ urpmq --whatrequires lib64gtk+2.0_0 gtk+2.0 lib64gtk+-x11-2.0_0 lib64gtk+2.0-devel lib64gtk+2.0_0 lib64gtk-gir2.0 lsb-lib64 lshw-gui perl-Gimp perl-Gtk2 $ urpmq --whatrequires-recursive lib64gtk+2.0_0 | uniq | wc -l 859
(In reply to Aurelian R from comment #33) > Freetux and GIMP are using gtk+2.0. Maybe some other gtk+2 programs present > similar symptoms. Something like "viewnior" or "lshw-gui". Same problem with viewnior and lshw-gui
(In reply to Lewis Smith from comment #35) > GTK+2: another good idea. Just to poke it: > > $ urpmq --whatrequires gtk+2.0 > gracket > lib64gtk+-x11-2.0_0 > lib64gtk2-theme-engines > perl-Gimp > perl-Gtk2 > perl-Gtk2-TrayIcon > uim-gtk > > $ urpmq --whatrequires lib64gtk+2.0_0 > gtk+2.0 > lib64gtk+-x11-2.0_0 > lib64gtk+2.0-devel > lib64gtk+2.0_0 > lib64gtk-gir2.0 > lsb-lib64 > lshw-gui > perl-Gimp > perl-Gtk2 > > $ urpmq --whatrequires-recursive lib64gtk+2.0_0 | uniq | wc -l > 859 $ urpmq --whatrequires gtk+2.0 gracket # not installed gtk+2.0 # installed lib64gtk+-x11-2.0_0 # installed lib64gtk2-theme-engines # not installed perl-Gimp # not installed perl-Gtk2 # not installed perl-Gtk2-TrayIcon # not installed uim-gtk # not installed urpmq --whatrequires lib64gtk+2.0_0 gtk+2.0 # installed lib64gtk+-x11-2.0_0 # installed lib64gtk+2.0-devel # not installed lib64gtk+2.0_0 # installed lib64gtk-gir2.0 # not installed lsb-lib64 # not installed lshw-gui # installed perl-Gimp # not installed perl-Gtk2 # not installed $ urpmq --whatrequires-recursive lib64gtk+2.0_0 | uniq | wc -l 861
(In reply to Gilbert BONNET from comment #36) > Same problem with viewnior and lshw-gui I still believe your issue is related to the screen size and the low DPI value, 22-30, reported for your screen. You seem to be using Plasma KDE, so try to force a higher DPI, open System Settings and under Appearance->Fonts at the bottom of the "Fonts" window check/select "Force font DPI" and manually play with that value, normally around 100.
I have to use the resolution 1360x768 (85:48) with my LG screen because if I choose 1920x1080 (16:9) I no longer see (or barely) the lower menu bar of the KDE Plasma desktop which is practically out of frame of the TV screen, this by having reduced the height width diagonal parameters of the TV with the remote control to a minimum. Which makes it difficult, for example, to turn off the computer. Now, I have tried your last manip And Miracle, it's the SOLUTION !!! So I thank you very, very much :))) (In reply to Aurelian R from comment #38) > (In reply to Gilbert BONNET from comment #36) > > Same problem with viewnior and lshw-gui > > I still believe your issue is related to the screen size and the low DPI > value, 22-30, reported for your screen. You seem to be using Plasma KDE, so > try to force a higher DPI, open System Settings and under Appearance->Fonts > at the bottom of the "Fonts" window check/select "Force font DPI" and > manually play with that value, normally around 100.
Status comment: (none) => Résolu / resolved
Thank's everybody !!!
Applause for Aurelian! This was not an invalid complaint, but our usual rule says if no modification of Mageia was needed it should be closed thus. I would like to close it resolved/fixed as Gilbert himself says, but will heed other Bugsquad views.
Great the cause could be found :) Cause: Obscure setting Nothing bad in Mageia that got fixed. For resolution status i would suggest WORKSFORME
Glad it worked out, His low resolution settings seems to be quite an annoyance. Gilbert may either figure out if his screen settings allow to shrink/move/adjust vertically the actual image or he can figure out how to set a custom resolution for the graphical server(1920x1084(5)?).
(In reply to Morgan Leijström from comment #42) > Nothing bad in Mageia that got fixed. > For resolution status i would suggest WORKSFORME Good advice, doing. I had not thought of that.
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED