December 2021 - openSUSE Support - openSUSE Mailing Lists

Re: gs unable to open shared library on TW
by Adam Mizerski 11 Dec '21

11 Dec '21

W dniu 10.12.2021 o 13:07, Jogchum Reitsma pisze: > Op 09-12-2021 om 12:31 schreef Adam Mizerski: >> W dniu 09.12.2021 o 12:20, Jogchum Reitsma pisze: >>> Hi, >>> >>> When I try to run gs, it says >>> >>> gs: error while loading shared libraries: libpcre2-8.so.0: failed to >>> map segment from shared object >>> >>> libpcre2-8.so.0 is present on the system, as a link to >>> libpcre2-8.so.0.10.4 >>> in both /usr/lib and /usr/lib64 >>> >>> There is also a variant in /usr/local/lib64, this time linking to >>> libpcre2-8.so.0.8.0 >>> >>> Any idea how I can get gs to life back again? >>> >>> regards, Jogchum >>> >> >> Anything in /usr/local is something you had to install manually. > > If by "install manually" you mean installed outside yast2, that is not > entirely true: cuda, for example, is installed by yast in /usr/local. > But maybe I misunderstand what you mean. Well, you're right, that cuda from official nvidia rpm repository installs files into /usr/local. But it should not. According to "Filesystem Hierarchy Standard" chapter "4.9. /usr/local : Local hierarchy" (https://refspecs.linuxbase.org/FHS_3.0/fhs/ch04s09.html) "The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated." So you understood correctly, but cuda breaks the rule. > >> There is a conflict between libpcre in /usr/local/lib64 and >> /usr/lib64. You should: >> 1) investigate how did you get those libraries in /usr/local > It is from a pcre2 installation,NOT installed through yast or zypper. No > idea why, it's from October 2019. >> 2) remove the conflicting libraries from /usr/local > > I'll remove the who pcre2 thing, I suppose. > > Thanks! > I'm glad I could help. Please reply to the mailing list.

1 0

susepaste-screenshot
by Marco Calistri 11 Dec '21

11 Dec '21

Hello, Today I noticed that zypper wish to install susepaste and susepaste-screenshot. The first is working ok but whenever I try to upload a picture by using susepaste-screenshot I get back the error: "Paste failed :-(" Here a syntax example I used: susepaste-screenshot --all -t "Test" Would like to know if are there any particular/additional settings to add in order to be able to use this script. Many Thanks. -- Marco Calistri Build: openSUSE Tumbleweed 20211208 Kernel:5.15.6-1-default Desktop: XFCE (4.16.0)

2 2

AutoMySQLBackup alternatives?
by Vojtěch Zeisek 11 Dec '21

11 Dec '21

Hi, I'm used to use https://sourceforge.net/projects/automysqlbackup/ for rotating MySQL/MariaDB backups. Although it hasn't changes for ages, it's simple, it works perfectly, so seemingly no need to change. It's packaged in two home projects in OBS, so fine. But I just wonder what others use to get rotating MySQL/MariaDB backups? Requirements are just simple thing doing the backups in dedicated directory, so no need for any advanced functions. -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/

2 2

unbound and Tumbleweed. Unbound service fails to start, complaining about a permission problem
by Stakanov 11 Dec '21

11 Dec '21

Unbound cannot start because of an apparent permission issue. Output is: × unbound.service - Unbound recursive Domain Name Server Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2021-12-07 08:14:54 CET; 1h 25min ago Process: 1937 ExecStartPre=/usr/bin/sudo -u unbound /usr/sbin/unbound- anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem (code=exited, status=0/SUCCESS) Process: 1993 ExecStartPre=/usr/sbin/unbound-checkconf (code=exited, status=0/SUCCESS) Process: 1994 ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS (code=exited, status=1/FAILURE) Main PID: 1994 (code=exited, status=1/FAILURE) CPU: 25ms Dec 07 08:14:54 silversurfer sudo[1937]: pam_kwallet5(sudo:session): pam_kwallet5: pam_sm_close_session Dec 07 08:14:54 silversurfer sudo[1937]: pam_kwallet5(sudo:setcred): pam_kwallet5: pam_sm_setcred Dec 07 08:14:54 silversurfer unbound-checkconf[1993]: [1638861294] unbound- checkconf[1993:0] warning: Explicit port randomisation disabled, ignoring outgoing-port-permit and outgoing-port-avoid configuration options Dec 07 08:14:54 silversurfer unbound-checkconf[1993]: [1638861294] unbound- checkconf[1993:0] warning: Explicit port randomisation disabled, ignoring outgoing-port-permit and outgoing-port-avoid configuration options Dec 07 08:14:54 silversurfer unbound-checkconf[1993]: unbound-checkconf: no errors in /etc/unbound/unbound.conf Dec 07 08:14:54 silversurfer systemd[1]: Started Unbound recursive Domain Name Server. Dec 07 08:14:54 silversurfer unbound[1994]: [1638861294] unbound[1994:0] error: Could not open /etc/unbound/unbound.conf: Permission denied Dec 07 08:14:54 silversurfer unbound[1994]: [1638861294] unbound[1994:0] fatal error: Could not read config file: /etc/unbound/unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound- checkconf Dec 07 08:14:54 silversurfer systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE Dec 07 08:14:54 silversurfer systemd[1]: unbound.service: Failed with result 'exit-code'. So the event is here: > Process: 1994 ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS (code=exited, > status=1/FAILURE) And it seems to be a permission issue: > Dec 07 08:14:54 silversurfer unbound[1994]: [1638861294] unbound[1994:0] > error: Could not open /etc/unbound/unbound.conf: Permission denied Dec 07 > 08:14:54 silversurfer unbound[1994]: [1638861294] unbound[1994:0] fatal > error: Could not read config file: /etc/unbound/unbound.conf. Maybe try > unbound -dd, it stays on the commandline to see more errors, or > unbound-checkconf running unbound with -dd as sudo on CLI gives no further hints, same output. So, is this a packaging issue / pam issue that should be reported? Do the users have all to be part of the unbound group? (Would make any sense to me). Or do I have to put explicitly root to user of the unbound group? Permission of /etc/unbound/unbound.conf are (default, I erased my own setup and de and then reinstalled the package) as follows: entropy@silversurfer:~> ls -l /etc/unbound/ totale 24 drwxr-xr-x 1 root unbound 32 7 dic 09.53 conf.d drwxr-xr-x 1 root unbound 30 7 dic 09.53 keys.d drwxr-xr-x 1 root unbound 44 7 dic 09.53 local.d -rw-r----- 1 root unbound 21947 22 apr 2018 unbound.conf should unbound.conf be readable to unbound user? What is wrong here. Any help appreciated.

4 15

gs unable to open shared library on TW
by Jogchum Reitsma 09 Dec '21

09 Dec '21

Hi, When I try to run gs, it says gs: error while loading shared libraries: libpcre2-8.so.0: failed to map segment from shared object libpcre2-8.so.0 is present on the system, as a link to libpcre2-8.so.0.10.4 in both /usr/lib and /usr/lib64 There is also a variant in /usr/local/lib64, this time linking to libpcre2-8.so.0.8.0 Any idea how I can get gs to life back again? regards, Jogchum

2 1

Dual Monitor on tumbleweed
by Christian Schmitz 09 Dec '21

09 Dec '21

Hi everyone: I am trying to setup 2 monitors. The hardware is: AMD chipset, ATI video card screen 3 Vga monitor 20" ( 1600x900 ) screen 2 DVI-I to adapter to Vga monitor 14" ( 1024x768) I can use "display and rotation" program under TDE to get following setup: screen3 main monitor screen2 extended desktop But i have 2 problems and question 1) every boot the screen are cloned and not extended. How i can do to store permanently the extended configuration? 2) when the screen are cloned i see well into screen 2, but when i switch to extended the screen 2 the color are degraded like old 16 ega. How fix it? Other thing is that i perform this on TDE desktop, marking "override system setting" option. So the 3rd question is: 3) How i set on the system the dual monitor setup? Best Regards Christian -- Be Free, Be Linux

5 6

Re: Dual Monitor on tumbleweed
by TomasK 09 Dec '21

09 Dec '21

On Wed, 2021-12-08 at 18:52 -0300, Christian Schmitz wrote: > > On Wednesday 08 December 2021 15:31:58 you wrote: > > On Wed, Dec 8, 2021, 13:03 Christian Schmitz <list(a)schweb.com.ar> > wrote: > > > Helo everyone: > > > Thanks for all. The working option was: > > > > > > xrandr --output VGA-0 --auto --primary --output DVI-0 --mode > > > 1024x768 --right-of VGA-0 > > > > > > I add --mode because i dont know why the system try to use a out > of > > > specifications resolution on small ( and secondary monitor) > > > > > > Also --primary because the TDE use the small monitor as primary > > > > > > The result is that the system start mirrored on boot, when X > start for 0 > > > seconds still mirrored and after that switch to the alright > screen > > > > > > . > > > > These days the screen resolution info comes from edit monitor data, > as > > supposed to more/less elaborate guess in the past. > > > > Your vga screen has no way of communicating that data over vga, > even if it > > would support it over hdmi/DP. The same is most likely true for > your DVI > > connected screen. > VGA still have DDC detection of monitor model, resolution and H/V > data. > > > > That is why X picks some sort of safe options. > I think in same way > > > > You probably would have correct resolution, refresh rates, etc. set > > correctly with modern monitors connected over DP/USB-C/hdmi > > > > -T > Thanks you for your answer. I am on Argentine, so the hardware is > some old, > but working hehehe. > > -- By no means I wanted to suggest that people should use the latest and greatest - just wanted to reason about the possibility that the screen maybe unable to share its info. If you install read-edid and then run: sudo get-edid to find if you get any screen info on any I2C buses. If you do see info - decode it and see what the monitors are reporting. It works like this: > sudo get-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 4 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 2 potential busses found: 8 10 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. 128-byte EDID successfully retrieved from i2c bus 8 ??????????????-Z??x??TL??&PT??7????p8>@:*5%?? ??AUO ??B133HAN05.A Looks like i2c was successful. Have a good day. > sudo get-edid -b 8 | parse-edid 8 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 8 as per your request. 128-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "AUO" # Monitor Manufactured week 0 of 2018 # EDID version 1.4 # Digital Display DisplaySize 290 170 Gamma 2.20 Option "DPMS" "false" Modeline "Mode 0" 142.60 1920 1978 2020 2080 1080 1083 1088 1142 -hsync -vsync EndSection > sudo get-edid -b 10 | parse-edid 1 0 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 10 as per your request. 256-byte EDID successfully retrieved from i2c bus 10 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "DELL U3011" ModelName "DELL U3011" VendorName "DEL" # Monitor Manufactured week 41 of 2012 # EDID version 1.3 # Digital Display DisplaySize 640 400 Gamma 2.20 Option "DPMS" "true" Horizsync 29-94 VertRefresh 49-86 # Maximum pixel clock is 180MHz #Not giving standard mode: 1152x864, 75Hz #Not giving standard mode: 1280x800, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1920x1200, 60Hz #Not giving standard mode: 1600x1200, 60Hz #Extension block found. Parsing... Modeline "Mode 17" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 0" 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync Modeline "Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 2" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline "Mode 4" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 6" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace Modeline "Mode 7" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace Modeline "Mode 8" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync Modeline "Mode 9" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline "Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline "Mode 12" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace Modeline "Mode 13" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline "Mode 14" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline "Mode 15" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 16" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 18" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace Modeline "Mode 19" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Modeline "Mode 20" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync Option "PreferredMode" "Mode 17" EndSection

2 2

Wicked unexpected interface flags
by Togan Muftuoglu 08 Dec '21

08 Dec '21

Hi, While trying to solve another problem I found the following in the wicked logs. What does is it mean and a direction to fix it is very much appreciated unexpected combination of interface flags 0x11003 Thanks

1 0

Old Telegram in Leap 15.3
by Mykola Krachkovsky 07 Dec '21

07 Dec '21

Hi, telegram-desktop in Leap 15.3 has version 2.5.8 and it says it will stop working soon. As I understand, next versions need Qt 5.15 to compile. Is there any workaround for Leap 15.3? Installing from site (with bundled Qt) isn't very nice solution, IMHO. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський

2 2

Re: unbound and Tumbleweed. Unbound service fails to start, complaining about a permission problem
by Georg Pfuetzenreuter 07 Dec '21

07 Dec '21

Sorry, accidentally did not reply-all: On 12/7/21 19:16, Georg Pfuetzenreuter wrote: > Hi, > > This seems to be a flaw in the package. > > the package shipping with a sudo statement in the service file is indeed > unusual, but understandable from the packagers perspective, as the > ExecStartPre statement performs not only a validation of the > configuration syntax, but also a validation of the configuration > permissions this way. > > However! The packaged configuration file ships with a "username: > unbound" line, which performs setuid to the unbound user upon starting > the program as root (which is what systemd does if no user= statement is > set): > https://build.opensuse.org/package/view_file/openSUSE:Factory/unbound/unbou… > (line 218). > > Whilst generally configuration files owned by root should not pose an > issue with applications performing setuid/setgid, I *assume* the > configuration file needs to be readable by the "unbound" user, as > otherwise the program could not read it on the fly after startup (i.e. > for configuration reloads using unbound-control). > > Please attempt to `chown unbound /etc/unbound/unbound.conf`. If this > resolves the issue, open a bug in order for the package maintainer to be > informed of the issue. They can then adjust > > https://build.opensuse.org/package/view_file/openSUSE:Factory/unbound/unbou… > (line 388) > > respectively. > > If this does not resolve the issue, I suggest to still open a bug, > stating the program does not work out of the box, informing them about > the attempts you performed. > > Best, > Georg > > On 12/7/21 11:24, Stakanov wrote: >> In data martedì 7 dicembre 2021 11:23:07 CET, Stakanov ha scritto: >>> In data martedì 7 dicembre 2021 10:44:28 CET, Carlos E. R. ha scritto: >>>> On Tuesday, 2021-12-07 at 09:57 +0100, Stakanov wrote: >>>>> Unbound cannot start because of an apparent permission issue. >>>>> >>>>> >>>>> >>>>> Output is: >>>>> × unbound.service - Unbound recursive Domain Name Server >>>>> >>>>> Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; >>>>> vendor preset: disabled) >>> >>> Active: failed (Result: exit-code) since >>> >>>>> Tue 2021-12-07 08:14:54 CET; 1h 25min ago> >>>>> Process: 1937 ExecStartPre=/usr/bin/sudo -u unbound >>>>> /usr/sbin/unbound- >>>> >>>> Now this is peculiar. A service using sudo to start? Perhaps the >>>> service >>>> is not running as root. >>>> >>>>> Process: 1994 ExecStart=/usr/sbin/unbound -d $UNBOUND_OPTIONS >>>>> (code=exited, status=1/FAILURE) >>>>> Main PID: 1994 (code=exited, status=1/FAILURE) >>>> >>>> Then this process (1994) would not be running as root. And it fails: >>>>> Dec 07 08:14:54 silversurfer unbound[1994]: [1638861294] >>>>> unbound[1994:0] >>>>> error: Could not open /etc/unbound/unbound.conf: Permission denied >>>> >>>> ... >>>> >>>>> entropy@silversurfer:~> ls -l /etc/unbound/ >>>>> totale 24 >>>>> drwxr-xr-x 1 root unbound 32 7 dic 09.53 conf.d >>>>> drwxr-xr-x 1 root unbound 30 7 dic 09.53 keys.d >>>>> drwxr-xr-x 1 root unbound 44 7 dic 09.53 local.d >>>>> -rw-r----- 1 root unbound 21947 22 apr 2018 unbound.conf >>>> >>>> If the process is not running as root, it can not read unbound.conf. >>>> >>>> -- >>>> Cheers, >>>> >>>> Carlos E. R. >>>> (from openSUSE 15.2 x86_64 at Telcontar) >>> >>> but for what I understood the service is intentional not running as >>> root. >>> And this for what I understand for security reasons? >>> The thing about the permission is haunting me since quite a while. >>> You can >>> of course relax the permissions for unbound conf but I do not know if >>> this >>> is a bug or if this is a setup error that I am making. >> and forget about sudo, I did run it from CLI as root but it fails >> either way >> >> silversurfer:~ # unbound -d >> [1638872635] unbound[22176:0] error: Could not open >> /etc/unbound/unbound.conf: >> Permission denied >> [1638872635] unbound[22176:0] fatal error: Could not read config file: >> /etc/ >> unbound/unbound.conf. Maybe try unbound -dd, it stays on the >> commandline to >> see more errors, or unbound-checkconf >>

1 0