- openSUSE Bugs

[Bug 1227259] New: Upgrade of mariadb creates new system table files as owner "root" when it needs to be "mysql"
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227259 Bug ID: 1227259 Summary: Upgrade of mariadb creates new system table files as owner "root" when it needs to be "mysql" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: grant.eureka(a)xtra.co.nz QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- The upgrade of MariaDB to version 11.4.2-lp156.2.1 completes a post-install procedure to upgrade the MariaDB internal system table files to version 11.4.2 The post-install creates these files as owner "root" instead of "mysql". To fix this, I had to chown mysql for all the files in the mariadb/mysql mariadb/performance_schema and mariadb/sys directories. The upgrade path followed was mysql 5.7.44 to MariaDB 11.2.3 while using Leap 15.6 (beta). Finally upgrade to MariaDB 11.4.2 using Leap 15.6 (RC). Without changing the owner, MariaDB fails to start. The username for the mariadb service is mysql. Following is the error log: 2024-06-10 8:43:55 0 [Note] Starting MariaDB 11.2.3-MariaDB-log source revision 79580f4f96fc2547711f674eb8dd514abd312b4a as process 1471 2024-06-10 8:43:55 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 2024-06-10 8:43:55 0 [Note] InnoDB: Number of transaction pools: 1 2024-06-10 8:43:55 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-06-10 8:43:55 0 [Note] InnoDB: Using Linux native AIO 2024-06-10 8:43:55 0 [Note] InnoDB: Initializing buffer pool, total size = 10.000MiB, chunk size = 1.000MiB 2024-06-10 8:43:55 0 [Note] InnoDB: Completed initialization of buffer pool 2024-06-10 8:43:55 0 [Note] InnoDB: File system buffers for log disabled (block size=4096 bytes) 2024-06-10 8:43:55 0 [Note] InnoDB: Resetting space id's in the doublewrite buffer 2024-06-10 8:43:55 0 [Note] InnoDB: End of log at LSN=779791006 2024-06-10 8:43:56 0 [Note] InnoDB: Opened 3 undo tablespaces 2024-06-10 8:43:56 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active. 2024-06-10 8:43:56 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-06-10 8:43:56 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-06-10 8:43:56 0 [Note] InnoDB: log sequence number 779791006; transaction id 5516328 2024-06-10 8:43:56 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-10 8:43:56 0 [Note] Plugin 'wsrep-provider' is disabled. 2024-06-10 8:43:56 0 [Note] InnoDB: Loading buffer pool(s) from /db/mariadb/ib_buffer_pool 2024-06-10 8:43:57 0 [Note] InnoDB: Buffer pool(s) load completed at 240610 8:43:57 2024-06-10 8:43:57 0 [Note] Server socket created on IP: '192.168.43.40'. 2024-06-10 8:43:57 0 [Note] mysqld: Event Scheduler: Loaded 0 events 2024-06-10 8:43:57 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '11.2.3-MariaDB-log' socket: '/var/run/mysql/mysql.sock' port: 3306 MariaDB package 2024-06-10 10:06:16 4 [Warning] Aborted connection 4 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 10:06:29 6 [Warning] Access denied for user 'root'@'socrates.local' (using password: NO) 2024-06-10 10:14:49 8 [Warning] Aborted connection 8 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 12:40:45 13 [Warning] Access denied for user 'root'@'socrates.local' (using password: NO) 2024-06-10 12:59:48 17 [Warning] Aborted connection 17 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 18:32:29 34 [Warning] Aborted connection 34 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 22:47:18 45 [Warning] Aborted connection 45 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 22:51:57 47 [Warning] Aborted connection 47 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 22:57:40 49 [Warning] Aborted connection 49 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 23:09:09 51 [Warning] Aborted connection 51 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 23:16:53 54 [Warning] Aborted connection 54 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 23:26:25 56 [Warning] Aborted connection 56 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 23:46:09 60 [Warning] Aborted connection 60 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-10 23:55:48 63 [Warning] Aborted connection 63 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-11 0:37:54 66 [Warning] Aborted connection 66 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-11 0:49:14 69 [Warning] Aborted connection 69 to db: 'unconnected' user: 'root' host: 'socrates.local' (Got an error reading communication packets) 2024-06-11 1:00:26 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown 2024-06-11 1:00:26 0 [Note] InnoDB: FTS optimize thread exiting. 2024-06-11 1:00:26 0 [Note] InnoDB: Starting shutdown... 2024-06-11 1:00:26 0 [Note] InnoDB: Dumping buffer pool(s) to /db/mariadb/ib_buffer_pool 2024-06-11 1:00:26 0 [Note] InnoDB: Restricted to 157 pages due to innodb_buf_pool_dump_pct=25 2024-06-11 1:00:26 0 [Note] InnoDB: Buffer pool(s) dump completed at 240611 1:00:26 2024-06-11 1:00:26 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-06-11 1:00:26 0 [Note] InnoDB: Shutdown completed; log sequence number 780656937; transaction id 5516899 2024-06-11 1:00:26 0 [Note] /usr/sbin/mysqld: Shutdown complete The automatic post-install process needs to create new files with the ownership the same as the user for the MariaDB service (or owner of the parent database directory), not root. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228366] New: Missing package for Application:Geo/qgis: causes fatal error std::bad_alloc on loading plugin
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228366 Bug ID: 1228366 Summary: Missing package for Application:Geo/qgis: causes fatal error std::bad_alloc on loading plugin Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: grant.eureka(a)xtra.co.nz QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- qgis 3.34.1 crashes when loading the Plugin "LINZ Data Importer" with fatal error std::bad_alloc I have traced the error to the package python311-OWSLib which attempts to load the Python package pyproj which needs to be installed correctly from python311-pyproj. The package python311-pyproj is missing from Leap 15.6 repos. I have successfully installed python311-pyproj 3.6.1 from a Tumbleweed community project. This has corrected the bad_alloc fatal error. Package python311-pyproj is needed in Leap 15.6 for qgis and should be listed as a "required by" in package python311-OWSLib. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227167] New: VUL-0: CVE-2024-24792: keybase-client: golang.org/x/image/tiff: parsing of a corrupt or malicious image with invalid color indices can cause a panic
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227167 Bug ID: 1227167 Summary: VUL-0: CVE-2024-24792: keybase-client: golang.org/x/image/tiff: parsing of a corrupt or malicious image with invalid color indices can cause a panic Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/412299/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: marix(a)marix.org Reporter: camila.matos(a)suse.com QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1227158 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1227158 +++ Parsing a corrupt or malicious image with invalid color indices can cause a panic. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-24792 https://www.cve.org/CVERecord?id=CVE-2024-24792 https://go.dev/cl/588115 https://go.dev/issue/67624 https://pkg.go.dev/vuln/GO-2024-2937 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226517] New: After snapper rollback/restore marks packages as explicitly installed which were autoinstalled previously
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226517 Bug ID: 1226517 Summary: After snapper rollback/restore marks packages as explicitly installed which were autoinstalled previously Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ors0092(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday, I filed a bug report directly on Snapper's upstream GitHub, as I was advised to do so on the Matrix support chat (https://github.com/openSUSE/snapper/issues/916). However, the issue was closed and I was redirected here. Two days ago, I accidentally noticed something strange. I don't know if this is how Snapper is supposed to work, but here are my observations and steps to reproduce: 1. I installed `firewall-applet` manually, and zypper marked it with `i+` as explicitly installed. It also pulled `firewall-config` automatically as a dependency (marking it with `i` as auto-installed status) - so far, so good. 2. Then, I did a `sudo zypper rm --clean-deps firewall-applet`, and it perfectly caught `firewall-config` too, as it was installed automatically as a dependency. 3. Next, I did a reboot and told Snapper to use the `post` snapshot from the time when `firewall-applet` was installed. This reverted the removal process to the point where `firewall-applet` was installed instead, so chronologically we are at step 1. 4. In the read-only mode, I did a `zypper se -i firewall-`, and to my surprise, `firewall-config` was also marked with `i+`. 5. I made the `sudo snapper rollback` to see the changes live, and yes, `firewall-config` was still marked with `i+`. 6. When I did `sudo zypper rm --clean-deps firewall-applet`, it no longer recognized `firewall-config` to be auto-removed since it was marked as explicitly installed. 7. This can be also reproduced without rebooting when steps are done from the GUI YaST2 snapshot tool. 8. Since it was late yesterday, I thought I was too tired and maybe misunderstood something. So, I double-checked myself and simulated the steps I made yesterday, just to confirm my theory, and yepp - same results. No idea why, but snapper removes any affected packages during a snapper procedure within `/var/lib/zypp/AutoInstalled` but this step is nowhere logged. Also an additional question for us affected users: how do we trace back which packages were marked by these rollbacks? As you might guess, there could be plenty of unnecessary packages using extra drive space, now that are explicitly marked and thus never get removed via `sudo zypper dup --remove-orphaned` nor gets listed by `zypper pa --orphaned` or `zypper pa --unneeded` sadly. 4years ago it seems it got already uncovered under boo 1175304, but is also reported under Leap, this ticket is all about Tumbleweed experiences. Operating System: openSUSE Tumbleweed 20240617 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7972 System Version: 2.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228365] No Snapper root config and mount created, installer 20240722
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228365 Arvin Schnell <aschnell(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228364] New: VUL-0: CVE-2023-50700: deepin-file-manager: privileged operations can be called by unprivileged users via the D-Bus method
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228364 Bug ID: 1228364 Summary: VUL-0: CVE-2023-50700: deepin-file-manager: privileged operations can be called by unprivileged users via the D-Bus method Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/415238/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: hillwoodroc(a)gmail.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Insecure Permissions vulnerability in Deepin dde-file-manager 6.0.54 and earlier allows privileged operations to be called by unprivileged users via the D-Bus method. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-50700 https://www.cve.org/CVERecord?id=CVE-2023-50700 https://bugzilla.opensuse.org/show_bug.cgi?id=1134131 https://bugzilla.opensuse.org/show_bug.cgi?id=1134132 https://github.com/linuxdeepin/developer-center/issues/10007 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226656] New: rsync --chown sets permissions to root:root after upgrade to Leap 15.6
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226656 Bug ID: 1226656 Summary: rsync --chown sets permissions to root:root after upgrade to Leap 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, On the client: ``` rsync -a --delete --super --owner --group --chown=477:479 --chmod='u=rwX,g=rX,o=' $PWD/ rsync://saltpush@witch1.infra.opensuse.org:873/salt-push/ ``` On the server, rsyncd.socket is listening with the following /etc/rsyncd.conf: ``` # Salt managed defaults address = :: gid = users log format = %h %o %f %l %b secrets file = /etc/rsyncd.secrets transfer logging = True use chroot = True # Salt managed modules [salt-push] path = /srv/salt-git/ comment = /srv/salt-git/ list = false uid = root gid = salt auth users = saltpush read only = False hosts allow = 2a07:de40:b27e:1203::126, 2a07:de40:b27e:1203::127 ``` With Leap 15.5, sync operations would keep the expected permissions and ownership on the directory /srv/salt-git and its contents. After the upgrade to Leap 15.6, which installed `rsync-3.2.7-150600.1.5.x86_64` on both the client and server side, the following happens: ``` root@witch1 ~# chown -R 477:479 /srv/salt-git root@witch1 ~# ls -dn /srv/salt-git drwxr-x--- 1 477 479 426 Jun 20 16:35 /srv/salt-git/ 8ec7287bf746:/srv/salt-git # rsync -a --delete --owner --group --chown=477:479 --chmod='u=rwX,g=rX,o=' $PWD/ rsync://saltpush@witch1.infra.opensuse.org:873/salt-push/ root@witch1 ~# ls -dn /srv/salt-git drwxr-x--- 1 0 0 426 Jun 20 16:35 /srv/salt-git/ ``` The directory gets recursively owned as root:root instead of keeping 477:479. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1228365] New: No Snapper root config and mount created, installer 20240722
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228365 Bug ID: 1228365 Summary: No Snapper root config and mount created, installer 20240722 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: lassi.vaatamoinen(a)gmail.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- DESCRIPTION: There seems to be an grave issue with Snapper snapshot subvolume cretaion in 20240722 installer. 1. After installation, there is no /.snapshots BTRFS subvolume created 2. /etc/fstab: no mount point for /.snapshots defined Accordint to the tutorial disk size > 16GB should have automatic snapshot feature available: https://en.opensuse.org/openSUSE:Snapper_Tutorial My disk size was 96GB, and there was no mount point. ACTIONS NEEDED: 1. Add the missing line to /etc/fstab: UUID=0aafc776-2ae2-45f6-8ce5-b84725de8c8a /.snapshots btrfs subvol=/(a)/.snapshots 0 0 2. Rn snapper config and mount: # snapper --config root create-config / # mount /.snapshots If I did not do the above, with the exception of '0' snapshot, there was nothing listed by 'snapper ls' when I booted to a read-only snapshot. ADDITIONAL INFORMATION Also perhaps the snapshot rollbacking failed due to this earlier, when booting to read-only snapshot. There only was the '0' snapshot listed and Snapper complained about "unknown subvolume" and proposed using "--ambit classic". But that did not work either then. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228269] Internal microphone not working on Lenovo Thinkpad E16 Gen 2 (Model 21M5)
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228269 https://bugzilla.suse.com/show_bug.cgi?id=1228269#c27 --- Comment #27 from tigerlily <helen(a)coldboot.plus.com> --- (In reply to Takashi Iwai from comment #26) > Thanks for confirmation. So it indicates that the remaining click noise bug > is specific to ASoC AMD driver. > > I submitted the fix patches for the shutdown noise to the upstream, and > backported to SLE15-SP6 git branch now. Many thanks for your help -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228269] Internal microphone not working on Lenovo Thinkpad E16 Gen 2 (Model 21M5)
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228269 https://bugzilla.suse.com/show_bug.cgi?id=1228269#c26 --- Comment #26 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for confirmation. So it indicates that the remaining click noise bug is specific to ASoC AMD driver. I submitted the fix patches for the shutdown noise to the upstream, and backported to SLE15-SP6 git branch now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0