September 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1149070] New: Make use of plymouth features while loading the installation images
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1149070 Bug ID: 1149070 Summary: Make use of plymouth features while loading the installation images Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: hellcp(a)mailbox.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- To better justify the waiting time while loading the installation system, we could use plymouth to display a progress bar accurately representing the progress, which is displayed in the log when the installer sets itself up. plymouth --help command reveals what commands should be run to show a progressbar: # To change the display to "updates mode" plymouth change-mode --updates # To display a custom message plymouth display-message --text="[TEXT]" # To change the progress status plymouth system-update --progress=[0-100] # etc. The order should most likely be to first display the basic messages (Loading the basic drivers, Starting hardware detection etc.) and then showing the progress for the Loading Installation System steps. Keep in mind, this will work with the splash used as the default in Tumbleweed (bgrt theme), not with the theme currently used in the installation scenario (tribar theme). The themes would need to be swapped, either for the TW default or the spinner theme (this will require further investigation into space constrains). An implementation of this already exists in multiple programs, like: PackageKit https://github.com/hughsie/PackageKit/blob/master/client/pk-offline-update.c fwupd https://github.com/fwupd/fwupd/blob/master/src/fu-offline.c This would increase user's understanding of the boot process, and let them know that the installation will load up soon, without entering a less friendly looking console. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1143125] systemd-vconsole-setup.service succeeds and fails several times on each boot
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1143125 http://bugzilla.suse.com/show_bug.cgi?id=1143125#c22 --- Comment #22 from Andreas Schwab <schwab(a)suse.com> --- Probably missing GNU_STACK header. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144244] New: Drop jasper dependency from gstreamer-plugins-bad
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1144244 Bug ID: 1144244 Summary: Drop jasper dependency from gstreamer-plugins-bad Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mvetter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Regarding bsc#1130404. We plan to drop libjasper from the repos. Let's remove the build dependcy on libjasper from gstreamer-plugins-bad and thus disable JPEG2000 support. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1124823] btrfsmaintenance service enabled, although no BTRFS used
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1124823 http://bugzilla.suse.com/show_bug.cgi?id=1124823#c18 --- Comment #18 from Lukas Ocilka <locilka(a)suse.com> --- (In reply to ravas mi from comment #13) > Then I guess I would setup a popup to activate an hour after boot, and ask > if it's a convenient time to perform disk maintenance. "It has been <X > amount of time> since the disk maintenance script ran: Would you like to run > it now?" With options to remind me in 1 hour, day, or week. There's no good place/time/way to display such a pop-up. Remember: Systems are to serve, not to bother. For that reason, systems can run without any user interaction (headless) or with several different display managers or even without GUI, just with text-mode. FS maintenance (if really needed) should be called when the system is actually idle. If it's idle, it often means there's nobody reading any pop-ups and nobody can answer such question. And BTW cron is ideally replaced with systemd-timer(s) https://www.freedesktop.org/software/systemd/man/systemd.timer.html -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1110542] Zypper resolution prompt appears twice
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1110542 http://bugzilla.suse.com/show_bug.cgi?id=1110542#c14 --- Comment #14 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2019:2265-1: An update that solves three vulnerabilities and has 13 fixes is now available. Category: security (moderate) Bug References: 1049825,1109893,1110542,1111319,1112911,1113296,1116995,1120629,1120630,1120631,1127155,1131823,1134226,1137977,1140039,1145521 CVE References: CVE-2018-20532,CVE-2018-20533,CVE-2018-20534 Sources used: SUSE OpenStack Cloud Crowbar 8 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE OpenStack Cloud 8 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE OpenStack Cloud 7 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server for SAP 12-SP3 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server for SAP 12-SP2 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server 12-SP4 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server 12-SP3-LTSS (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server 12-SP3-BCL (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server 12-SP2-LTSS (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Server 12-SP2-BCL (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Linux Enterprise Desktop 12-SP4 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Enterprise Storage 5 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE Enterprise Storage 4 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 SUSE CaaS Platform 3.0 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 HPE Helion Openstack 8 (src): libsolv-0.6.36-2.27.19.8, libzypp-16.20.2-27.60.4, zypper-1.13.54-18.40.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144919] devel:languages:nodejs/nodejs8: Inconsistent npmrc location vs. nodejs10
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1144919 http://bugzilla.suse.com/show_bug.cgi?id=1144919#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2019:2260-1: An update that solves 8 vulnerabilities and has one errata is now available. Category: security (important) Bug References: 1144919,1146090,1146091,1146093,1146094,1146095,1146097,1146099,1146100 CVE References: CVE-2019-9511,CVE-2019-9512,CVE-2019-9513,CVE-2019-9514,CVE-2019-9515,CVE-2019-9516,CVE-2019-9517,CVE-2019-9518 Sources used: SUSE Linux Enterprise Module for Web Scripting 15-SP1 (src): nodejs8-8.16.1-3.20.1 SUSE Linux Enterprise Module for Web Scripting 15 (src): nodejs8-8.16.1-3.20.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149070] Make use of plymouth features while loading the installation images
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149070 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149070] Make use of plymouth features while loading the installation images
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149070 http://bugzilla.suse.com/show_bug.cgi?id=1149070#c2 --- Comment #2 from Steffen Winterfeldt <snwint(a)suse.com> --- Well, we've *had* something like this in pre-plymouth times (with kernel splash). Then we switched to plymouth, had to cut down on features, and since then nobody really cared. FWIW, the old progress update function even still exists (and is called in the code at intervalls): https://github.com/openSUSE/linuxrc/blob/master/util.c#L1669 Also, note that the last step(s) (should) happen not in linuxrc but in the yast startup scripts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124823] btrfsmaintenance service enabled, although no BTRFS used
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1124823 http://bugzilla.suse.com/show_bug.cgi?id=1124823#c17 --- Comment #17 from Jean Delvare <jdelvare(a)suse.com> --- (In reply to ravas mi from comment #15) > It's a different question, and it's implied that it needs to happen -- just > like a system update, or when my phone tells me it's been 7 days and it > would be beneficial to reboot. There's nothing implied. The examples you give are nice illustrations of failed technology which takes user time instead of saving it. If your phone needs to be rebooted every 7 days to keep working properly, it's a bad phone. System updates should ideally be transparent to the user as well, the only case where users must be bothered is when a system update requires a reboot, but that's hopefully rare. I wish all other system updates would restart dependent applications automatically to switch to the new code ASAP without user interaction, but we are not there yet. Anyway, filesystem maintenance should definitely be transparent to the user by default. Filesystems are here to serve the users, not to educate them. I'm with Stefan all the way here, no pop-up, no question asked, it must just do the right thing by default. If btrfs is so complex that there is no reasonable default then that means btrfs should not be the default filesystem to start with. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1141433] Get no hint that network connection is made by NetworkManager when start YaST Networkmanagement
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1141433 David Diaz <dgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgonzalez(a)suse.com, | |locilka(a)suse.com Flags| |needinfo?(locilka(a)suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0