[kde3][15.5] kdeutils3-extra requires libpython2_7 not in STD or KDE3 repos
<https://lists.opensuse.org/archives/list/kde3@lists.opensuse.org/thread/GCZIVX6WR3BP7PELCZUQBJW55PUO5DPC/> has last month's thread about this that seems to have gone dead without resolution. # zypper -v in -d kdeutils3-extra ... Selecting 'kdeutils3-extra-3.5.10-lp155.122.1.x86_64' from repository 'KDE3' for installation. ... Problem: nothing provides 'libpython2.7.so.1.0()(64bit)' needed by the to be installed kdeutils3-extra-3.5.10-lp155.122.1.x86_64 Solution 1: do not install kdeutils3-extra-3.5.10-lp155.122.1.x86_64 Solution 2: break kdeutils3-extra-3.5.10-lp155.122.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c # opi libpython2_7 1. libpython2_7-1_0 2. libpython2_7-1_0-32bit Pick a number (0 to quit): 1 You have selected package name: libpython2_7-1_0 1. Packman Extra ? | 2.7.18 | x86_64 2. home:deltafox ! | 2.7.18 | x86_64 3. home:deltafox ! | 2.7.18 | x86_64 4. home:deltafox ! | 2.7.18 | x86_64 5. home:goupilmtos ! | 2.7.18 | x86_64 Pick a number (0 to quit): 0 # I looked for an open bug about this and found no open KDE3 bugs at all. Is anything in the works to get this dependence filled from KDE3 or standard repos? Is a bug report needed? My workaround so far is installing libpython2_7-1_0-2.7.18-lp155.293.1.x86_64.rpm from deltafox. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 7/24/23 18:09, Felix Miata wrote:
<https://lists.opensuse.org/archives/list/kde3@lists.opensuse.org/thread/GCZIVX6WR3BP7PELCZUQBJW55PUO5DPC/> has last month's thread about this that seems to have gone dead without resolution.
# zypper -v in -d kdeutils3-extra ... Selecting 'kdeutils3-extra-3.5.10-lp155.122.1.x86_64' from repository 'KDE3' for installation. ... Problem: nothing provides 'libpython2.7.so.1.0()(64bit)' needed by the to be installed kdeutils3-extra-3.5.10-lp155.122.1.x86_64 Solution 1: do not install kdeutils3-extra-3.5.10-lp155.122.1.x86_64 Solution 2: break kdeutils3-extra-3.5.10-lp155.122.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c/d/?] (c): c # opi libpython2_7 1. libpython2_7-1_0 2. libpython2_7-1_0-32bit Pick a number (0 to quit): 1 You have selected package name: libpython2_7-1_0 1. Packman Extra ? | 2.7.18 | x86_64 2. home:deltafox ! | 2.7.18 | x86_64 3. home:deltafox ! | 2.7.18 | x86_64 4. home:deltafox ! | 2.7.18 | x86_64 5. home:goupilmtos ! | 2.7.18 | x86_64 Pick a number (0 to quit): 0 #
I looked for an open bug about this and found no open KDE3 bugs at all. Is anything in the works to get this dependence filled from KDE3 or standard repos? Is a bug report needed?
My workaround so far is installing libpython2_7-1_0-2.7.18-lp155.293.1.x86_64.rpm from deltafox.
This is bad... The ultimate fix is to patch kdeutils3-extra for python3 since all distros are racing to drop python 2.7. This will likely need a bug report. I hate python and python dependencies - it just ties your desktop to yet another package. Felix, are you going to open one? I'm probably still a couple of weeks away from a 15.5 install -- which I suspect is where I'll hit this issue. But this issue isn't going away and we can't have KDE3 depending on a buildservice build from a home:/ repo. -- David C. Rankin, J.D.,P.E.
On 7/24/23 20:19, David C. Rankin wrote:
This is bad...
The ultimate fix is to patch kdeutils3-extra for python3 since all distros are racing to drop python 2.7. This will likely need a bug report. I hate python and python dependencies - it just ties your desktop to yet another package.
Felix, are you going to open one? I'm probably still a couple of weeks away from a 15.5 install -- which I suspect is where I'll hit this issue. But this issue isn't going away and we can't have KDE3 depending on a buildservice build from a home:/ repo.
The only direct dependency I find in the kdeutils3.spec is: BuildRequires: python-devel So it looks like the 2.7 dep is pulled in by another dependency relied on by kdeutils3 -- which make it a bit more of an issue. Yasuhiko, have you tried a build against python3 yet? (to see how bad this is?) Anybody know what TDE did, or is Debian still shipping a python 2.7 package? -- David C. Rankin, J.D.,P.E.
On 7/24/23 20:35, David C. Rankin wrote:
On 7/24/23 20:19, David C. Rankin wrote:
This is bad...
The ultimate fix is to patch kdeutils3-extra for python3 since all distros are racing to drop python 2.7. This will likely need a bug report. I hate python and python dependencies - it just ties your desktop to yet another package.
Felix, are you going to open one? I'm probably still a couple of weeks away from a 15.5 install -- which I suspect is where I'll hit this issue. But this issue isn't going away and we can't have KDE3 depending on a buildservice build from a home:/ repo.
The only direct dependency I find in the kdeutils3.spec is:
BuildRequires: python-devel
So it looks like the 2.7 dep is pulled in by another dependency relied on by kdeutils3 -- which make it a bit more of an issue.
Yasuhiko, have you tried a build against python3 yet? (to see how bad this is?) Anybody know what TDE did, or is Debian still shipping a python 2.7 package?
Okay, damn, The kdeutils-3.5.10.tar.bz2 source is littered with python dependencies. A majority for superkaramba. The autotools acinclude.m4 and acinclude.m4.in is where the version is set, e.g.: acinclude.m4:4650:AC_DEFUN([KDE_CHECK_PYTHON], acinclude.m4:4652: KDE_CHECK_PYTHON_INTERN("2.5", acinclude.m4:4653: [KDE_CHECK_PYTHON_INTERN("2.4", acinclude.m4:4654: [KDE_CHECK_PYTHON_INTERN("2.3", acinclude.m4:4655: [KDE_CHECK_PYTHON_INTERN("2.2", acinclude.m4:4656: [KDE_CHECK_PYTHON_INTERN("2.1", acinclude.m4:4657: [KDE_CHECK_PYTHON_INTERN("2.0", acinclude.m4:4658: [KDE_CHECK_PYTHON_INTERN($1, $2) ]) admin/acinclude.m4.in:4486:AC_DEFUN([KDE_TRY_LINK_PYTHON], The ./configure script picks it up from there. Hopefully, the changes are not that exhaustive to have python3 provide the same services that 2.7 currently provides. It looks like the main mess starts here: superkaramba/README:1:This is SuperKaramba, a version of Karamba with python scripting! superkaramba/src/config_python.h:2:* config_python.h - Functions for config python api superkaramba/src/config_python.h:25:#ifndef CONFIG_PYTHON_H superkaramba/src/config_python.h:26:#define CONFIG_PYTHON_H superkaramba/src/config_python.h:138:#endif // CONFIG_PYTHON_H superkaramba/src/widget_python.cpp:2:* widget_python.h - Functions for widget python api superkaramba/src/widget_python.cpp:29:#include <Python.h> superkaramba/src/widget_python.cpp:33:#include "meter_python.h" superkaramba/src/widget_python.cpp:34:#include "widget_python.h" superkaramba/src/widget_python.cpp:36:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:43:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:61:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:100:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:118:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:136:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:156:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:174:/* now a method we need to expose to Python */ superkaramba/src/widget_python.cpp:194:/* now a method we need to expose to Python */ superkaramba/src/meter_python.cpp:15:#include <Python.h> superkaramba/src/meter_python.cpp:20:#include "meter_python.h" superkaramba/src/meter_python.cpp:92:// Converts a Python String to a QString with Unicode support superkaramba/src/meter_python.cpp:116:// Converts a QString to a Python String with Unicode support superkaramba/src/textlabel_python.h:2:* textlabel_python.h - Functions for textlabel python api superkaramba/src/textlabel_python.h:25:#ifndef TEXTLABEL_PYTHON_H superkaramba/src/textlabel_python.h:26:#define TEXTLABEL_PYTHON_H superkaramba/src/textlabel_python.h:69:* You can reference text in your python code that was created in the superkaramba/src/textlabel_python.h:240:* created through python currently). textToChange is the reference to the superkaramba/src/textlabel_python.h:273:* through python currently). textToChange is the reference to the text superkaramba/src/textlabel_python.h:305:* through python currently). textToChange is the reference to the text superkaramba/src/textlabel_python.h:339:* through python currently). Text is the reference to the text superkaramba/src/textlabel_python.h:397:#endif // TEXTLABEL_PYTHON_H There are other sources as well, but this is where the majority of it is. -- David C. Rankin, J.D.,P.E.
After a clean install of Trinity the default fonts are microscopic. Not ever 7+ readers can see them. Which configuration file contains the setting for the fonts? CWSIV
Carl Spitzer {L Juno} composed on 2023-08-15 07:35 (UTC-0700):
After a clean install of Trinity the default fonts are microscopic. Not ever 7+ readers can see them.
Which configuration file contains the setting for the fonts?
TDE-specific files are: ~/.tderc ~/.trinity/share/config/kcmfonts What you may have is a DPI issue. What does inxi -GSaz report? Do you have Gnome, Cinnamon, Mate or other GTK-based/dominant environment? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On Tue, 2023-08-15 at 11:31 -0400, Felix Miata wrote:
Carl Spitzer {L Juno} composed on 2023-08-15 07:35 (UTC-0700):
After a clean install of Trinity the default fonts are microscopic. Not ever 7+ readers can see them.
Which configuration file contains the setting for the fonts?
TDE-specific files are:
~/.tderc ~/.trinity/share/config/kcmfonts
No such file. Perhaps If I saw yours I could make it up from there.
What you may have is a DPI issue. What does inxi -GSaz report? Do you have Gnome, Cinnamon, Mate or other GTK-based/dominant environment?
no Gnome3 as I have no 3d. Mate yes . inxi -GSaz System: Kernel: 5.14.21-150500.55.7-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=UUID=0154825c-3aa7-4e5d-9283-56f5014b7300 splash=silent preempt=full mitigations=auto quiet security=apparmor Desktop: MATE v: 1.26.0 info: mate-panel wm: marco v: 1.26.0 vt: 7 dm: 1: SDDM note: stopped 2: TDM 3: XDM Distro: openSUSE Leap 15.5 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-6 process: Intel 32nm built: 2011 ports: active: LVDS-1 empty: VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300 Device-2: NVIDIA GF108M [GeForce GT 525M] vendor: Dell driver: nouveau v: kernel non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: VGA-2 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:0df5 class-ID: 0300 temp: 61.0 C Device-3: Microdia Laptop_Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.5:5 chip-ID: 0c45:6483 class-ID: 0e02 Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: marco v: 1.26.0 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel,nouveau,nv,nvidia dri: crocus,zink gpu: i915,nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 55 s-size: 631x406mm (24.84x15.98") s-diag: 750mm (29.54") Monitor-1: LVDS-1 pos: primary,left model: AU Optronics 0x22ec built: 2009 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768 Monitor-2: VGA-2 mapped: VGA-1-2 pos: right res: 1024x768 hz: 60 size: N/A modes: max: 1024x768 min: 640x480 API: OpenGL v: 3.3 Mesa 22.3.5 renderer: Mesa Intel HD Graphics 3000 (SNB GT2) direct render: Yes CWSIV
Have you tried creating a new user login to use with TDE without ever having logged into Mate? If this produces fonts more like expected, it means a personal setting is involved rather than a global problem needs to be isolated. The only other DEs I've ever had installed alongside TDE are Plasma and IceWM, and no trouble anything like you have. Carl Spitzer {L Juno} composed on 2023-08-21 18:02 (UTC-0700):
On Tue, 2023-08-15 at 11:31 -0400, Felix Miata wrote:
Carl Spitzer {L Juno} composed on 2023-08-15 07:35 (UTC-0700):
After a clean install of Trinity the default fonts are microscopic. Not ever 7+ readers can see them.
Which configuration file contains the setting for the fonts?
TDE-specific files are:
~/.tderc ~/.trinity/share/config/kcmfonts
No such file. Perhaps If I saw yours I could make it up from there.
~/.tderc is a corollary to ~/.kderc with a few more lines in it. NAICT, it doesn't exist until you use TDE Control Center to make a change that deviates any font or color from the default. ~/.trinity/share/config/kcmfonts also correlates to KDE3. This file here contains only three lines: [General] dontChangeAASettings=false forceFontDPI=0 The KControl UI for handling this file offers a limited selection of choices, but managing the file with a text editor, any number within reason can be used. Going below 96 can make things ugly. Going too far past 96, can cause things to misfit or not fit where they belong. I've tested with up to about 240 or so. This is actually one place it might pay to experiment with, instead of 0, try a DPI value that corresponds to your display's actual density, or simply use one bigger than 96 as a knob to increase the sizes of most things, including fonts. I don't normally use it myself directly, as I make that very change at a global level, applicable to all GUI logins, using xrandr in /etc/X11/xinit/xinitrd.d/. On this my main box it's set to 120 in a script there. Try 120. See what happens. 'xrdb -query | grep dpi' will report the current value in your ENV. Try the command first, to see if something else has already set it. You may find 55, as explained below. 96 is the default. If it reports differently, something has changed a default somewhere. The change only affects subsequent starts, so you need to logout and back in for full effect.
What you may have is a DPI issue. What does inxi -GSaz report? Do you have Gnome, Cinnamon, Mate or other GTK-based/dominant environment?
no Gnome3 as I have no 3d. Mate yes .
inxi -GSaz System: Kernel: 5.14.21-150500.55.7-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=UUID=0154825c-3aa7-4e5d-9283-56f5014b7300 splash=silent preempt=full mitigations=auto quiet security=apparmor Desktop: MATE v: 1.26.0 info: mate-panel wm: marco v: 1.26.0 vt: 7 dm: 1: SDDM note: stopped 2: TDM 3: XDM Distro: openSUSE Leap 15.5 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-6 process: Intel 32nm built: 2011 ports: active: LVDS-1 empty: VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0116 class-ID: 0300 Device-2: NVIDIA GF108M [GeForce GT 525M] vendor: Dell driver: nouveau v: kernel non-free: series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm built: 2010-16 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports: active: VGA-2 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:0df5 class-ID: 0300 temp: 61.0 C
Laptop with two, Intel + NVidia, GPUs spells "Optimus". This normally entails special extra effort in getting good X configuration, typically utilizing suse-prime software. There are opensuse.org SDB pages covering the issues. I have never had Optimus, so never any hands on experience with it.
Device-3: Microdia Laptop_Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-1.5:5 chip-ID: 0c45:6483 class-ID: 0e02 Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: marco v: 1.26.0 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel,nouveau,nv,nvidia dri: crocus,zink gpu: i915,nouveau display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 55 s-size: 631x406mm (24.84x15.98") s-diag: 750mm (29.54")
"s-dpi: 55" spells tiny fonts. It may be technically correct for the 631x406 (30" diagonal) screen, but the software and fonts systems aren't capable of being competent when that number is much below 96. Something somewhere seems to be wanting to force a technically accurate match between physical display density and logical (software) screen density. I can only guess something your Mate configuration did in some personal setting got badly inherited by TDE. When you have two displays of disparate sizes with right size fonts, the DPI numbers should be closer to this bunch: Screen-1: 0 s-res: 4240x1440 s-dpi: 120 s-size: 897x304mm (35.31x11.97") s-diag: 947mm (37.29") Monitor-1: DP-1 pos: primary,left model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-2: DP-2 pos: right model: Dell P2213 serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
Monitor-1: LVDS-1 pos: primary,left model: AU Optronics 0x22ec built: 2009 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768 Monitor-2: VGA-2 mapped: VGA-1-2 pos: right res: 1024x768 hz: 60 size: N/A modes: max: 1024x768 min: 640x480 API: OpenGL v: 3.3 Mesa 22.3.5 renderer: Mesa Intel HD Graphics 3000 (SNB GT2) direct render: Yes
cat ~/.tderc [General] StandardFont=Sans Serif,10,-1,5,50,0,0,0,0,0 activeFont=Sans Serif,10,-1,5,75,0,0,0,0,0 background=239,239,239 fixed=Monospace,10,-1,5,50,0,0,0,0,0 font=Sans Serif,10,-1,5,50,0,0,0,0,0 foreground=0,0,0 menuFont=Sans Serif,10,-1,5,50,0,0,0,0,0 selectBackground=103,141,178 selectForeground=255,255,255 taskbarFont=Sans Serif,9,-1,5,50,0,0,0,0,0 toolBarFont=Sans Serif,10,-1,5,50,0,0,0,0,0 windowBackground=255,255,255 windowForeground=0,0,0 -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
participants (3)
-
Carl Spitzer {L Juno}
-
David C. Rankin
-
Felix Miata