October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1230891] Difficult to update mesa with Packman repo installed on Slowroll
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230891 https://bugzilla.suse.com/show_bug.cgi?id=1230891#c12 --- Comment #12 from Stefan Dirsch <sndirsch(a)suse.com> --- I digged deeper into the packages packman provides and obviously the -32bit packages for the -drivers flavor of Mesa is only available in 24.1.3 whereas any other Mesa packages, i.e. the main flavor of Mesa (64 and 32bit packages) and the -driver flavor 64bit packages are available in 24.1.7. So I believe this is a packman issue here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230673] perl: y2038: 32-bit builds use 4-byte time_t
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230673 https://bugzilla.suse.com/show_bug.cgi?id=1230673#c15 --- Comment #15 from Michael Schröder <mls(a)suse.com> --- Yes, that's also my suggestion. Drop them until the complete 32bit distro uses 64bit time_t (if that happens at all). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c81 --- Comment #81 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Dirk Weber from comment #80) > > Why are you patching /etc/bash.bashrc instead of /etc/bash.profile ... does > > /etc/profile.d/mc.sh and/or /usr/share/mc/mc.sh include shell functions > > or only environment variables? > > I do not have a /etc/bash.profile (now on Leap 15.6, and don't remember it > existed in prior Leap versions; also not in Tumbleweed). I meant /etc/profile :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c80 --- Comment #80 from Dirk Weber <d_werner(a)gmx.net> --- (In reply to Dr. Werner Fink from comment #79) > (In reply to Dirk Weber from comment #78) > > The issue in current Tunbleweed (e.g. 20241006) with mc-4.8.32 is completely > > different from this bug. > > > > The issue in Tumbleweed is related to upstream > > https://midnight-commander.org/ticket/4575 > > > > The wrapper script calls mc with a nonexistent directory, therefore mc can > > not write the information of the current directory to the file and the > > function can not get that information to cd to this directory. As a > > workaround the directory can be created in order to restore the > > functionality. > > > > $ pidof mc > > 6253 > > > > $ ps -Fp 6253 > > UID PID PPID C SZ RSS PSR STIME TTY TIME CMD > > user 6253 6049 0 5135 13680 0 08:58 pts/2 00:00:00 > > /usr/bin/mc -P /tmp/mc-user/mc.pwd.6049 > > > > > > $ ll /tmp/mc-user > > ls: cannot access '/tmp/mc-user': No such file or directory > > > > > > Workaround: > > $ mkdir "/tmp/mc-$(whoami)" && chmod 0700 "/tmp/mc-$(whoami)" > > > I really wonder why a file is used at all ... this is a typical usecase for > an environment variable as a process can not only set a variable (e.g. here > at start) but also read this variable at any time (e.g. here at exit). I am not the developer of mc, but the goal is: mc is started from a shell and runs as a child process. It is desired that after quitting mc the cwd of this shell - parent process of mc - should be the last directory of the active mc panel. So the wrapper function generates a temporary file name and at exit mc writes into this file the last directory. The wrapper function in the parent shell can then cd to the directory it finds in the temporary file. The mc binary in the child process can not modify the environment of its parent process, therefore it can not transfer the last directory in an environment variable. BTW: I realized I missed your question in comment 71: > Why are you patching /etc/bash.bashrc instead of /etc/bash.profile ... does > /etc/profile.d/mc.sh and/or /usr/share/mc/mc.sh include shell functions > or only environment variables? I do not have a /etc/bash.profile (now on Leap 15.6, and don't remember it existed in prior Leap versions; also not in Tumbleweed). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217747] New: colord: reproducible builds: icc varies from CPU
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1217747 Bug ID: 1217747 Summary: colord: reproducible builds: icc varies from CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://github.com/omgovich/colord/issues/122 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: gnome-bugs(a)suse.de Blocks: 1100677 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for ALP+openSUSE, I found that our colord package varied from differences in .icc files caused by differences in build machine CPU capabilities (probably AVX) Also filed upstream at https://github.com/omgovich/colord/issues/122 but they seem inactive. You find a reproducer and more details there. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1231354] [SELinux] bootctl denied { getattr ioctl open read } on removable device if system was installed on eMMC drive
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231354 Cathy Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |cathy.hu(a)suse.com CC| |cathy.hu(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c79 --- Comment #79 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Dirk Weber from comment #78) > (In reply to David Rankin from comment #76) > > I can confirm on TW, that mc does not exit to the current directory any > > longer when sourcing mc-wrapper.sh as the mc startup. Instead, mc reverts > > back to exiting to the start directory regardless of the current directory. > > The mc-wrapper.sh script has worked for -- ever. So something broke that > > setup. > > The issue in current Tunbleweed (e.g. 20241006) with mc-4.8.32 is completely > different from this bug. > > The issue in Tumbleweed is related to upstream > https://midnight-commander.org/ticket/4575 > > The wrapper script calls mc with a nonexistent directory, therefore mc can > not write the information of the current directory to the file and the > function can not get that information to cd to this directory. As a > workaround the directory can be created in order to restore the > functionality. > > $ pidof mc > 6253 > > $ ps -Fp 6253 > UID PID PPID C SZ RSS PSR STIME TTY TIME CMD > user 6253 6049 0 5135 13680 0 08:58 pts/2 00:00:00 > /usr/bin/mc -P /tmp/mc-user/mc.pwd.6049 > > > $ ll /tmp/mc-user > ls: cannot access '/tmp/mc-user': No such file or directory > > > Workaround: > $ mkdir "/tmp/mc-$(whoami)" && chmod 0700 "/tmp/mc-$(whoami)" I really wonder why a file is used at all ... this is a typical usecase for an environment variable as a process can not only set a variable (e.g. here at start) but also read this variable at any time (e.g. here at exit). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231336] New: default-system-colors do not work in gnome-terminal
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231336 Bug ID: 1231336 Summary: default-system-colors do not work in gnome-terminal Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello by default gnome-terminal uses system colors, which seem to be undefined as terminal seems to display missing background and ends up with weird graphical artifacts. Other themse gnome-dark etc work fine. Workaround: Unselect use system colors in gnome-terminal preferences and choose any other color profile (e.g. tango-dark). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c78 --- Comment #78 from Dirk Weber <d_werner(a)gmx.net> --- (In reply to David Rankin from comment #76) > I can confirm on TW, that mc does not exit to the current directory any > longer when sourcing mc-wrapper.sh as the mc startup. Instead, mc reverts > back to exiting to the start directory regardless of the current directory. > The mc-wrapper.sh script has worked for -- ever. So something broke that > setup. The issue in current Tunbleweed (e.g. 20241006) with mc-4.8.32 is completely different from this bug. The issue in Tumbleweed is related to upstream https://midnight-commander.org/ticket/4575 The wrapper script calls mc with a nonexistent directory, therefore mc can not write the information of the current directory to the file and the function can not get that information to cd to this directory. As a workaround the directory can be created in order to restore the functionality. $ pidof mc 6253 $ ps -Fp 6253 UID PID PPID C SZ RSS PSR STIME TTY TIME CMD user 6253 6049 0 5135 13680 0 08:58 pts/2 00:00:00 /usr/bin/mc -P /tmp/mc-user/mc.pwd.6049 $ ll /tmp/mc-user ls: cannot access '/tmp/mc-user': No such file or directory Workaround: $ mkdir "/tmp/mc-$(whoami)" && chmod 0700 "/tmp/mc-$(whoami)" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222752] ugrep: build results depend on CPU
by bugzilla_noreply＠suse.com 08 Oct '24

08 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1222752 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|Andreas.Stieger(a)gmx.de |junguo.wang(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0