November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1146018] New: Unreliable copy and cut
by bugzilla_noreply＠novell.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1146018 Bug ID: 1146018 Summary: Unreliable copy and cut Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: audi_s4(a)luukku.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After fresh installation of Tumbleweed to a new hardware (Ryzen Threadripper + AMD gfx) copy and cut with ctrl+c/x started working unreliably (never experienced this with the previous hardware setups). After KDE is started these work OK but after few hours already copy and cut start to miss these presses. 2nd press usually works but not always. After several days without restarting KDE this problem gets more severe - misses more often. Also, strange behaviour happens with Dolphin for example. When ctrl+x is pressed the file/folder icon flicks quickly to greyed out (cut selection) and back to normal. It becomes difficult to press ctrl+x so that cut selection remains. Holding ctrl+x pressed for repeat the icon start to flicker between normal and selected. Tried changing clipboard configuration options but none have made any difference to the problem. I have not seen issues with paste i.e. if there's something on a clipboard it can be pasted. This is not only ctrl+c/x button combination issue but same applied to selecting copy&cut from application menus. All applications (KDE basic apps, LibreOffice, Thunderbird, Firefox..) I use suffer from this problem thus it seems to be KDE related issue. This has been an issue for several months (since installation early 2019). In the beginning it was even worse i.e. some updates have reduced the issue a bit but not much. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1185952] New: [Build 20210510] PostgreSQL is not startable on s390x
by bugzilla_noreply＠suse.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1185952 Bug ID: 1185952 Summary: [Build 20210510] PostgreSQL is not startable on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 URL: https://openqa.opensuse.org/tests/1734657/modules/post gresql_server/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-s390x-textmode@s390x-zVM-vswitch-l2 fails in [postgresql_server](https://openqa.opensuse.org/tests/1734657/modules/postgr… All packages can be installed. The problem is that the PostgreSQL server can not be started. The journal log is saying: -- Logs begin at Mon 2021-05-10 22:41:06 EDT, end at Mon 2021-05-10 23:23:02 EDT. -- May 10 23:15:15 susetest systemd[1]: Starting PostgreSQL database server... May 10 23:15:15 susetest systemd[1]: postgresql.service: Control process exited, code=exited, status=1/FAILURE May 10 23:15:15 susetest systemd[1]: postgresql.service: Failed with result 'exit-code'. May 10 23:15:15 susetest systemd[1]: Failed to start PostgreSQL database server. May 10 23:15:15 susetest postgresql-script[12832]: Cannot find an active PostgreSQL server binary. Please install one of the PostgreSQL May 10 23:15:15 susetest postgresql-script[12832]: server packages or activate an already installed version using update-alternatives. ## Test suite description Maintainer: QE Yast Installation in textmode and selecting the textmode "desktop" during installation. ## Reproducible Fails since (at least) Build [20210510](https://openqa.opensuse.org/tests/1734657) (current job) ## Expected result Last good: [20210507](https://openqa.opensuse.org/tests/1731697) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1100677] New: trackerbug: packages do not build reproducibly from compile-time CPU-detection
by bugzilla_noreply＠novell.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1100677 Bug ID: 1100677 Summary: trackerbug: packages do not build reproducibly from compile-time CPU-detection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1100520 Blocks: 1081754 Found By: Development Blocker: --- e.g. bug 1100520 compiler options -march=native and -mtune=native make the resulting machine code depend on the build system's CPU which breaks reproducible builds. affects at least: glucat form python-annoy legion trigger-rally This is already fixed in: clpeak higan kyotocabinet one common approach seems to do sed -i "s|-march=native||g" $FILE -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1159231] New: tesseract-ocr builds with march=native
by bugzilla_noreply＠novell.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1159231 Bug ID: 1159231 Summary: tesseract-ocr builds with march=native Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: idonmez(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: hiwatari.seiji(a)gmail.com Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that the tesseract-ocr package binary varies depending on build machine CPU. This is a bug that can cause crashes on machines older that the random build machine. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1192844] New: vlc dvd:// crashes in Mesa init_source
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1192844 Bug ID: 1192844 Summary: vlc dvd:// crashes in Mesa init_source Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: ohering(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- vlc dvd:// crashes: Core was generated by `vlc dvd://'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f5b2d18b011 in init_source (buffer=0x7f5ae8842088, idct=0x7f5ae87eb4e0) at ../src/gallium/auxiliary/vl/vl_idct.c:597 597 tex = buffer->sampler_views.individual.source->texture; [Current thread is 1 (Thread 0x7f5aeed36640 (LWP 2185))] (gdb) p buffer->sampler_views $1 = {all = {0x0, 0x7f5ae8829390, 0x0, 0x7f5ae8829390}, stage = {{0x0, 0x7f5ae8829390}, {0x0, 0x7f5ae8829390}}, individual = { source = 0x0, matrix = 0x7f5ae8829390, intermediate = 0x0, transpose = 0x7f5ae8829390}} (gdb) bt #0 0x00007f5b2d18b011 in init_source (buffer=0x7f5ae8842088, idct=0x7f5ae87eb4e0) at ../src/gallium/auxiliary/vl/vl_idct.c:597 #1 vl_idct_init_buffer (intermediate=0x0, source=<optimized out>, buffer=0x7f5ae8842088, idct=0x7f5ae87eb4e0) at ../src/gallium/auxiliary/vl/vl_idct.c:806 #2 init_idct_buffer (buffer=<optimized out>, dec=0x7f5ae8841de8) at ../src/gallium/auxiliary/vl/vl_mpeg12_decoder.c:256 #3 vl_mpeg12_get_decode_buffer (dec=dec@entry=0x7f5ae87eb2e0, target=<optimized out>) at ../src/gallium/auxiliary/vl/vl_mpeg12_decoder.c:557 #4 0x00007f5b2d18ba87 in vl_mpeg12_begin_frame (decoder=0x7f5ae87eb2e0, target=<optimized out>, picture=0x7f5ae807dca8) at ../src/gallium/auxiliary/vl/vl_mpeg12_decoder.c:606 #5 0x00007f5aeddac314 in handleVASliceDataBufferType (context=context@entry=0x7f5ae807dc30, buf=<optimized out>) at ../src/gallium/frontends/va/picture.c:351 #6 0x00007f5aeddadf09 in vlVaRenderPicture (ctx=<optimized out>, context_id=<optimized out>, buffers=0x7f5ae801cb70, num_buffers=72) at ../src/gallium/frontends/va/picture.c:581 #7 0x00007f5af4bc15bf in vaRenderPicture (dpy=0x7f5ae810eb50, context=8, buffers=0x7f5ae801cb70, num_buffers=72) at /usr/src/debug/libva-2.13.0-3.1.x86_64/va/va.c:1605 #8 0x00007f5b0c92e990 in ff_vaapi_decode_issue (avctx=0x7f5ae8001580, pic=0x7f5ae807ab40) at libavcodec/vaapi_decode.c:179 #9 0x00007f5b0c93a61e in vaapi_mpeg2_end_frame (avctx=<optimized out>) at libavcodec/vaapi_mpeg2.c:121 #10 0x00007f5b0c7d3fa0 in slice_end (avctx=avctx@entry=0x7f5ae8001580, pict=pict@entry=0x7f5ae8005f80) at libavcodec/mpeg12dec.c:2042 #11 0x00007f5b0c7deb4d in decode_chunks (avctx=0x7f5ae8001580, picture=0x7f5ae8005f80, got_output=0x7f5aeed359a0, buf=0x7f5ae8045c60 "", buf_size=137080) at libavcodec/mpeg12dec.c:2495 #12 0x00007f5b0c7dfb4e in mpeg_decode_frame (avctx=0x7f5ae8001580, data=0x7f5ae8005f80, got_output=0x7f5aeed359a0, avpkt=<optimized out>) at libavcodec/mpeg12dec.c:2847 #13 0x00007f5b0c5d440a in decode_simple_internal (discarded_samples=<synthetic pointer>, frame=0x7f5ae8005f80, avctx=0x7f5ae8001580) at libavcodec/decode.c:329 #14 decode_simple_receive_frame (frame=<optimized out>, avctx=<optimized out>) at libavcodec/decode.c:530 #15 decode_receive_frame_internal (avctx=avctx@entry=0x7f5ae8001580, frame=0x7f5ae8005f80) at libavcodec/decode.c:550 #16 0x00007f5b0c5d5888 in avcodec_send_packet (avctx=avctx@entry=0x7f5ae8001580, avpkt=0x7f5ae8006d40) at libavcodec/decode.c:617 ... (gdb) info source Current source file is ../src/gallium/auxiliary/vl/vl_idct.c Compilation directory is /usr/src/debug/Mesa-drivers-21.2.5-293.2.x86_64/x86_64-suse-linux Located in /usr/src/debug/Mesa-drivers-21.2.5-293.2.x86_64/src/gallium/auxiliary/vl/vl_idct.c ... [ 26.750403][ T570] [drm] initializing kernel modesetting (RV620 0x1002:0x95C5 0x1028:0x0342 0x00). [ 26.759604][ T570] ATOM BIOS: 113 ... No idea when it started, just tried it this week on this Dell OptiPlex 980. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1205314] New: [Build 20221110] 2nd disk decrypt dialog
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205314 Bug ID: 1205314 Summary: [Build 20221110] 2nd disk decrypt dialog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2867881/modules/firs t_boot/steps/3 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation This setup configures the harddisk/partition as seen in https://openqa.opensuse.org/tests/2867881#step/select_guided_setup/1 (i.e /boot is not split out from /) After installation, we observe grub being decrypted: https://openqa.opensuse.org/tests/2867881#step/grub_test/1 but upon selecting TW to boot from, the password dialog appears again. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-crypt_no_lvm@64bit fails in [first_boot](https://openqa.opensuse.org/tests/2867881/modules/first_boot/st… ## Test suite description Maintainer: riafarov. Test installation with encrypted partitions but without lvm enabled. This is supported only by storage-ng, hence, do NOT enable test suite on distris without storage-ng. ## Reproducible Fails since (at least) Build [20221110](https://openqa.opensuse.org/tests/2867380) ## Expected result Last good: [20221109](https://openqa.opensuse.org/tests/2865109) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1199383] New: [Tumbleweed][lftp][Build_20220423] Connetion via lftp failed due with self signed certificate
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1199383 Bug ID: 1199383 Summary: [Tumbleweed][lftp][Build_20220423] Connetion via lftp failed due with self signed certificate Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: weixuan.hao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Summary This test is to test lftp with ssl enabled ## Observation After setting up vsftpd server and lftp, using lftp to login to ftp server and try to download/upload files, connection will fail with self signed certificate ## Environment # uname -m x86_64 # cat /etc/*release NAME="openSUSE Tumbleweed" # VERSION="20220423" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20220423" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20220423" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" ## Reproducible Follow steps from https://bugzilla.suse.com/tr_show_case.cgi?case_id=1769978 to set up vsftpd server and https://bugzilla.suse.com/tr_show_case.cgi?case_id=1769945 for lftp testing ## Error # lftp -d -u ftpuser -e 'set ftp:ssl-force true' localhost Password: ---- Resolving host address... ---- 2 addresses found: ::1, 127.0.0.1 lftp ftpuser@localhost:~> ls ---- Connecting to localhost (::1) port 21 **** Socket error (Connection refused) - reconnecting ---- Closing control socket ---- Connecting to localhost (127.0.0.1) port 21 <--- 220 Welcome to SUSE FTP service. ---> FEAT <--- 211-Features: <--- AUTH TLS <--- EPRT <--- EPSV <--- MDTM <--- PASV <--- PBSZ <--- PROT <--- REST STREAM <--- SIZE <--- TVFS <--- UTF8 <--- 211 End ---> AUTH TLS <--- 234 Proceed with negotiation. ---> OPTS UTF8 ON Certificate depth: 0; subject: /C=CN/ST=Beijing/L=Beijing/O=SUSE/OU=QA/CN=shawn/emailAddress=weixuan.hao(a)suse.com; issuer: /C=CN/ST=Beijing/L=Beijing/O=SUSE/OU=QA/CN=shawn/emailAddress=weixuan.hao(a)suse.com ERROR: Certificate verification: self signed certificate (31:7B:F2:C5:B6:A1:21:90:A6:61:A3:11:26:42:F7:E3:CE:0E:53:4C) **** Certificate verification: self signed certificate (31:7B:F2:C5:B6:A1:21:90:A6:61:A3:11:26:42:F7:E3:CE:0E:53:4C) ---- Closing control socket ls: Fatal error: Certificate verification: self signed certificate (31:7B:F2:C5:B6:A1:21:90:A6:61:A3:11:26:42:F7:E3:CE:0E:53:4C) lftp ftpuser@localhost:~> exit -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1184786] New: Deduplicate directory ownership with filesystem package
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1184786 Bug ID: 1184786 Summary: Deduplicate directory ownership with filesystem package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, checksec pointed out that various directories in our /usr are 0755 while they're 0555 on Fedora and Red Hat. For more hardened environments this might make a difference, as it prevents a user "root" that doesn't have DAC_OVERRIDE permission to no longer write/create files there. In order to achieve that, only one package need to own the permissions of that directory. currently we have various packages co-owning it, which means actual permission would depend on installation order, and we'd get installation conflicts. This can be prevented by de-duplicating directory ownership. this is a tracker bug that tracks the work related to it. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1198668] New: Tumbleweed: Purge old kernels service block during boot
by bugzilla_noreply＠suse.com 17 Mar '23

17 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1198668 Bug ID: 1198668 Summary: Tumbleweed: Purge old kernels service block during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Sometimes "Purge old kernels" service does not run after booting, but during boot, which slows down boot: $ LC_ALL=C journalctl -b 0 |grep -i purge Apr 20 08:16:01 dell5510 systemd[1]: Starting Purge old kernels... Apr 20 08:16:02 dell5510 zypper[1546]: Preparing to purge obsolete kernels... Apr 20 08:17:09 dell5510 systemd[1]: purge-kernels.service: Deactivated successfully. Apr 20 08:17:09 dell5510 systemd[1]: Finished Purge old kernels. Apr 20 08:17:09 dell5510 systemd[1]: purge-kernels.service: Consumed 53.594s CPU time. It started few weeks ago, it does not happen every boot, but maybe once a week. But bothered me enough to report the problem. $ LC_ALL=C rpm -qi purge-kernels-service Name : purge-kernels-service Version : 0 Release : 8.4 Architecture: noarch Install Date: Tue Feb 22 11:51:00 2022 Group : Unspecified Size : 346 License : MIT Signature : RSA/SHA256, Sat Feb 19 22:50:00 2022, Key ID b88b2fd43dbdc284 Source RPM : purge-kernels-service-0-8.4.src.rpm Build Date : Sat Feb 19 22:37:41 2022 ... $ lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220415 Codename: n/a -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1205636] New: zypper ps -s shows wrong command and no service
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1205636 Bug ID: 1205636 Summary: zypper ps -s shows wrong command and no service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After zypper dup and restarting all services reported by zypper ps -s on openSUSE Tumbleweed, USB-hotplug did not work anymore. Reason is that zypper shows wrong commands and thus not the service, which needs a restart: # zypper ps -s The following running processes use deleted files: PID | PPID | UID | User | Command | Service ------+------+------------+------------+-------------+-------- 1 | 0 | 0 | root | systemd | 2682 | 2680 | 1366800143 | kukuk | systemd | 24860 | 1 | 0 | root | udevadm | But PID 24860 is: root 24860 0.0 0.1 29840 1436 ? Ss Nov21 0:00 /usr/lib/systemd/systemd-udevd Since zypper detects the wrong command and thus does not show, that systemd-udevd.service needs to be restarted, running udevd and installed udev rules don't match and in this case e.g. USB-hotplug does not work anymore, since no more kernel modules get loaded. -- You are receiving this mail because: You are on the CC list for the bug.

1 18