June 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1181449] Don´t load Gsmartcontrol
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1181449 https://bugzilla.suse.com/show_bug.cgi?id=1181449#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de Resolution|--- |WONTFIX --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- EOL distro, closing. And instead of reporting screenshots of shell output copy-paste the shell output if you want traction. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180267] Lack of an update repository for the distribution openSUSE Jump
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1180267 https://bugzilla.suse.com/show_bug.cgi?id=1180267#c4 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX CC| |Andreas.Stieger(a)gmx.de Status|NEW |RESOLVED --- Comment #4 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- not a currently maintained distro, closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180729] Repository connection error
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1180729 https://bugzilla.suse.com/show_bug.cgi?id=1180729#c9 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de Resolution|--- |WONTFIX --- Comment #9 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- EOL distro, closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208394] AUDIT-TRACKER: ruby3.2-rubygem-agama: follow-up audit of D-Bus setup (separate D-Bus design)
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1208394 https://bugzilla.suse.com/show_bug.cgi?id=1208394#c18 --- Comment #18 from Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> --- (In reply to Matthias Gerstner from comment #17) > Thanks for the additional info. You are welcome! > During testing the live ISO it happened once right after booting that the > installer couldn't come up properly, displaying "Cannot connect to D-Bus". > Pressing "Reload" fixed this though. There still seems to be some instability > there. We have improved the startup process (relying on D-Bus activation), so I expect this problem to be fixed. Anyway, we will do some further testing for the next release. > > Security wise I belive the D-bus specific parts are not that critical, since > they only run in the live environment. All processes are root there currently > anyway. I had a look at the agama D-Bus configuration and its socket > directory > in /run/amaga etc. It looks okay. OK, great. > Looking at the bigger picture of this installer the challenges lie rather in > the way people get remote access to this live environment / the installer. > Currently we have two methods: > > - root login via password on the SSH port 22 which is enabled by default. > > - root login via the web browser on SSL port 9090 which is also enabled by > default. This web server uses a self-signed SSL certificate that is not > trusted. > > An installer in this form should not be used in production since it can be > hijacked anytime once connected to a real network. We also should not rely on > a trusted network environment here. > > The root user should use a random password on SSH level. This random password > could be displayed in the graphical installer. > > For the web server, if it cannot use a properly trusted SSL certificate, the > SSL fingerprint could be displayed in the graphical installer (on the > local console) for verification. Also the login on web level needs to be made > safe some way, again the password could be displayed on the local console. It makes sense. I had though about disabling remote access by default and allowing the user to enable it through some boot argument, similar to what we do in SLES (e.g., ssh=1 sshpassword=foobar). However, displaying the password and the fingerprint looks like a better idea. > The SSH login (which probably isn't needed often, it's more kind of a > developer/expert access) could also be bootstrapped via the web server. The > web server could offer the (trusted) download of a randomly generated SSH > private key. Sure, the SSH login is an expert/developer feature. I like the idea of generating a private key and enabling the service. Thanks a lot for your feedback, Matthias. I will coordinate with the team to work on this. I will keep you informed. Regards, Imo -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211973] openSUSE-2023-116-1 (recommended update for llvm15) conflicts with qt{5,6}-creator
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211973 https://bugzilla.suse.com/show_bug.cgi?id=1211973#c5 Andrey Novikov <andrey.v.novikoff(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Andrey Novikov <andrey.v.novikoff(a)gmail.com> --- The recent update for qt-creator do fixes the requirement conflict -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211989] Snap applications stopped to work after recent apparmor update
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1211989 roke beedell <rokejulianlockhart+1674683091(a)outlook.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rokejulianlockhart+16746830 | |91(a)outlook.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212767] libdlm: fails to build with linux-glibc-devel 6.4
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212767 https://bugzilla.suse.com/show_bug.cgi?id=1212767#c2 Ana Guerrero <ana.guerrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Ana Guerrero <ana.guerrero(a)suse.com> --- https://build.opensuse.org/request/show/1095836 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212732] python-service_identity 23.1.0 breaks python-twisted:test
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1212732 https://bugzilla.suse.com/show_bug.cgi?id=1212732#c2 Ana Guerrero <ana.guerrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #2 from Ana Guerrero <ana.guerrero(a)suse.com> --- Fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210313] Conflict resolution between openssl and libressl
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1210313 https://bugzilla.suse.com/show_bug.cgi?id=1210313#c14 --- Comment #14 from Otto Hollmann <otto.hollmann(a)suse.com> --- This issue seems to be caused by added > Conflicts: openssl(cli) into openssl meta package in Tumbleweed. Then it conflicts with openssl-1_1 (from 15.4) because it has > Provides: openssl(cli) The meta package from 15.4 doesn't have any Provides/Conflicts. That's maybe another reason why conflicts should be handled by meta package but I don't know how to fix if and I don't think we will be allowed to change it in 15.4/SLE* It seems that the only is to keep devel conflicts and revert other changes. Or at least revert change that caused this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210603] all bugmail attributable to, or respecting, opensuse.org products or components should either contain opensuse.org URIs instead of suse.com, or in addition to
by bugzilla_noreply＠suse.com 28 Jun '23

28 Jun '23

https://bugzilla.suse.com/show_bug.cgi?id=1210603 https://bugzilla.suse.com/show_bug.cgi?id=1210603#c1 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tmuntaner(a)suse.com --- Comment #1 from Felix Miata <mrmazda(a)earthlink.net> --- I was hoping the bug 1210546 fix would fix this, but it's not looking good. I'm still getting only BSC links in bugmail since its reputed fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0