January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1169874] [Build 20200417] Failure to boot due to resume=/dev/disk/by-path
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c23 --- Comment #23 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Fabian Vogt from comment #22) > (In reply to Josef Reidinger from comment #21) > > (In reply to Fabian Vogt from comment #20) > > > (In reply to Ancor Gonzalez Sosa from comment #18) > > > > We have still not unified the YaST Bootloader and YaST Storage code, as we > > > > stated we should do in several comments. But we have implemented something > > > > that should fix the main problem described in this bug report. > > > > > > > > Starting with yast2-storage-ng 4.3.34, new swap devices will have a > > > > pre-generated UUID, which means that UUID will be used by the YaST > > > > Bootloader proposal if that's the default method. See more details at > > > > https://github.com/yast/yast-storage-ng/pull/1192 > > > > > > > > Submitted to TW as https://build.opensuse.org/request/show/858102 > > > > > > I'm trying to verify that this is fixed, but apparently none of the openQA > > > tests has "resume=" as part of the kernel cmdline or embedded in the initrd > > > at all anymore. I verified that with a local install. > > > > > > Is that intentional? > > > > Well, we have now flag that decide if we propose resume or not. But for > > opensuse it should propose it for x86_64 for non server roles if I remember > > correctly. > > It is part of feature to not propose hibernation on servers. > > I tried the "generic desktop" role and even checked the "expand swap to ram" > box, > but didn't get "resume=". In openQA, it doesn't seem to be in any test, so > also GNOME, > KDE and so on, with several file systems. I found "# Do not propose resume on virtuals (jsc#SLE-12280)", so it's probably expected that it doesn't work in VMs. I'll try to fake real HW. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1169874] [Build 20200417] Failure to boot due to resume=/dev/disk/by-path
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c22 --- Comment #22 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Josef Reidinger from comment #21) > (In reply to Fabian Vogt from comment #20) > > (In reply to Ancor Gonzalez Sosa from comment #18) > > > We have still not unified the YaST Bootloader and YaST Storage code, as we > > > stated we should do in several comments. But we have implemented something > > > that should fix the main problem described in this bug report. > > > > > > Starting with yast2-storage-ng 4.3.34, new swap devices will have a > > > pre-generated UUID, which means that UUID will be used by the YaST > > > Bootloader proposal if that's the default method. See more details at > > > https://github.com/yast/yast-storage-ng/pull/1192 > > > > > > Submitted to TW as https://build.opensuse.org/request/show/858102 > > > > I'm trying to verify that this is fixed, but apparently none of the openQA > > tests has "resume=" as part of the kernel cmdline or embedded in the initrd > > at all anymore. I verified that with a local install. > > > > Is that intentional? > > Well, we have now flag that decide if we propose resume or not. But for > opensuse it should propose it for x86_64 for non server roles if I remember > correctly. > It is part of feature to not propose hibernation on servers. I tried the "generic desktop" role and even checked the "expand swap to ram" box, but didn't get "resume=". In openQA, it doesn't seem to be in any test, so also GNOME, KDE and so on, with several file systems. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1169874] [Build 20200417] Failure to boot due to resume=/dev/disk/by-path
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c21 --- Comment #21 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Fabian Vogt from comment #20) > (In reply to Ancor Gonzalez Sosa from comment #18) > > We have still not unified the YaST Bootloader and YaST Storage code, as we > > stated we should do in several comments. But we have implemented something > > that should fix the main problem described in this bug report. > > > > Starting with yast2-storage-ng 4.3.34, new swap devices will have a > > pre-generated UUID, which means that UUID will be used by the YaST > > Bootloader proposal if that's the default method. See more details at > > https://github.com/yast/yast-storage-ng/pull/1192 > > > > Submitted to TW as https://build.opensuse.org/request/show/858102 > > I'm trying to verify that this is fixed, but apparently none of the openQA > tests has "resume=" as part of the kernel cmdline or embedded in the initrd > at all anymore. I verified that with a local install. > > Is that intentional? Well, we have now flag that decide if we propose resume or not. But for opensuse it should propose it for x86_64 for non server roles if I remember correctly. It is part of feature to not propose hibernation on servers. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180487] chromium crash: FATAL:string_piece.h(328)] Check failed: pos <= size() (18446744073709551615 vs. 36)
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180487 https://bugzilla.suse.com/show_bug.cgi?id=1180487#c6 --- Comment #6 from Rolf Eike Beer <eike(a)sf-mail.de> --- Correct me if I'm wrong, but crash reports are disabled in the Chromium build? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1169874] [Build 20200417] Failure to boot due to resume=/dev/disk/by-path
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1169874 https://bugzilla.suse.com/show_bug.cgi?id=1169874#c20 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- Flags| |needinfo?(ancor(a)suse.com) --- Comment #20 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Ancor Gonzalez Sosa from comment #18) > We have still not unified the YaST Bootloader and YaST Storage code, as we > stated we should do in several comments. But we have implemented something > that should fix the main problem described in this bug report. > > Starting with yast2-storage-ng 4.3.34, new swap devices will have a > pre-generated UUID, which means that UUID will be used by the YaST > Bootloader proposal if that's the default method. See more details at > https://github.com/yast/yast-storage-ng/pull/1192 > > Submitted to TW as https://build.opensuse.org/request/show/858102 I'm trying to verify that this is fixed, but apparently none of the openQA tests has "resume=" as part of the kernel cmdline or embedded in the initrd at all anymore. I verified that with a local install. Is that intentional? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180297] New: enhance lvm2 device-mapper package, add dmfilemapd command
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180297 Bug ID: 1180297 Summary: enhance lvm2 device-mapper package, add dmfilemapd command 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: heming.zhao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- as subject saying, I filed this bug for adding new binary dmfilemapd in to device-mapper package. it will enhance device-mapper package function, give customer more flexibility to manage their system. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1179739] New: update lvm.conf, make it closely to upstream's setting
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179739 Bug ID: 1179739 Summary: update lvm.conf, make it closely to upstream's setting Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: heming.zhao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently opensuse lvm.conf setting herit from sle15sp2. It's time to do the updating job to following upstream's setting. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1180508] jeos image does not boot on nanopi neo air
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180508 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |afaerber(a)suse.com, | |dmueller(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180508] jeos image does not boot on nanopi neo air
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180508 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume.gardet(a)arm.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180306] Tumbleweed 20201221 breaks "csh"
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180306 https://bugzilla.suse.com/show_bug.cgi?id=1180306#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1180306) was mentioned in https://build.opensuse.org/request/show/860398 Factory / elfutils -- You are receiving this mail because: You are on the CC list for the bug.

1 0