January 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1130404] Considering removal of libjasper in openSUSE
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1130404 Bug 1130404 depends on bug 1158897, which changed state. Bug 1158897 Summary: Remove jasper dependency from gtk2 http://bugzilla.opensuse.org/show_bug.cgi?id=1158897 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158897] Remove jasper dependency from gtk2
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1158897 http://bugzilla.opensuse.org/show_bug.cgi?id=1158897#c4 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #4 from Michael Vetter <mvetter(a)suse.com> --- SR#757536 got accepted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159704] ACPI errors on the OpenSUSE Tumbleweed Live CD
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1159704 http://bugzilla.suse.com/show_bug.cgi?id=1159704#c4 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #4 from Borislav Petkov <bpetkov(a)suse.com> --- Ok, lemme explain more: the BIOS issue is unlikely to cause the live CD boot failure. So, has *any* live cd booted on that machine successfully in the past? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144249] Drop jasper dependency from libqt5-qtimageformats
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1144249 http://bugzilla.opensuse.org/show_bug.cgi?id=1144249#c6 --- Comment #6 from Michael Vetter <mvetter(a)suse.com> --- Not sure what kind of detailed explanation you are looking for. I think it's all clearly documented here on bugzilla. Comment 1 mentions that this regards https://bugzilla.suse.com/show_bug.cgi?id=1130404 which has all the details and links for further reading. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159704] ACPI errors on the OpenSUSE Tumbleweed Live CD
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1159704 http://bugzilla.suse.com/show_bug.cgi?id=1159704#c3 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |bpetkov(a)suse.com Resolution|--- |INVALID --- Comment #3 from Borislav Petkov <bpetkov(a)suse.com> --- This is most likely a BIOS issue, like all the gazillion other ones we see. And I'm pretty sure you'll see it with the upstream kernel too. If the machine works despite the issue, I'd ignore it. So lemme close, if you feel there's anything else we can do, feel free to reopen. Thx. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1132308] LVM lvcreate fails with "Failed to lock logical volume"
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1132308 http://bugzilla.suse.com/show_bug.cgi?id=1132308#c3 heming zhao <heming.zhao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #3 from heming zhao <heming.zhao(a)suse.com> --- from comment #0 info: ``` device-mapper: reload ioctl on (254:4) failed: Input/output error Failed to lock logical volume some_data/some_data_lv. Aborting. Manual intervention required. ``` _lv_create_an_lv +-> lv_update_and_reload | +-> _lv_update_and_reload | +-> suspend_lv => _do_dm_ioctl() => log: | | device-mapper: reload ioctl on (254:4) failed: Input/output error | +-> log: Failed to lock logical volume some_data/some_data_lv. +-> log: "Aborting. Manual intervention required." This is very common error, the lvm log "reload ioctl on ..." responses kernel dm layer: table_load() For the too little info, I closed this bug for noresponse. If the bug reporter still interesting the fix, please provide info which I said in comment #2. and please also provide below commands output: dmsetup ls --tree dmsetup table dmsetup status lsof /dev/some_data/some_data_lv Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157670] YaST bootloader module doesn't start: Invalid UTF-8 sequence in es_ES
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1157670 http://bugzilla.suse.com/show_bug.cgi?id=1157670#c28 Rafael linux <rafael.linux.user(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Found By|--- |Community User Resolution|--- |FIXED --- Comment #28 from Rafael linux <rafael.linux.user(a)gmail.com> --- Comment #15 fixed the issue https://bugzilla.suse.com/show_bug.cgi?id=1157670#c15 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157670] YaST bootloader module doesn't start: Invalid UTF-8 sequence in es_ES
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1157670 http://bugzilla.suse.com/show_bug.cgi?id=1157670#c27 --- Comment #27 from Rafael linux <rafael.linux.user(a)gmail.com> --- (In reply to Ancor Gonzalez Sosa from comment #25) > (In reply to Rafael linux from comment #15) > > I think I should create a new bug for that, but let me know what do you > > think about: I discovered that "F2 - Language" option in main boot menu only > > appears WHEN BOOTING IN BIOS MODE (MBR or Legacy or CSM) mode, not in UEFI > > mode. Is this normal???? > > Yes, it is. In UEFI mode we use standard grub2 to boot the DVD/USB instead > of gfxboot. Thanks Ancor. But I understand that's a choice of OpenSUSE, cause I remember to see other distros to always show the language option in BIOS and UEFI mode. Could OpenSUSE next releases do it same way? Thank you -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159674] Java:packages/hibiscus: Update to 2.8.22
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1159674 http://bugzilla.suse.com/show_bug.cgi?id=1159674#c1 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pmonrealgonzalez(a)suse.com --- Comment #1 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- Update to 2.8.22 submitted: https://build.opensuse.org/request/show/760588 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157670] YaST bootloader module doesn't start: Invalid UTF-8 sequence in es_ES
by bugzilla_noreply＠novell.com 03 Jan '20

03 Jan '20

http://bugzilla.suse.com/show_bug.cgi?id=1157670 http://bugzilla.suse.com/show_bug.cgi?id=1157670#c26 --- Comment #26 from Rafael linux <rafael.linux.user(a)gmail.com> --- (In reply to Josef Reidinger from comment #24) > OK, so let me comment this a bit. Usual reason why bootloader failed in this > is because grub.cfg is localized. So it means, that title are translated. > When YaST2 reads that file it assumes that UTF-8 encoding is used ( there is > not reliable way to get encoding from file ). So what probably caused it is > that file is generated when locale was non-UTF8 variant. > Way to fix it is ensure you have UTF-8 variant of locale and regenerate file. > So something like: > ``` > LANG=es_ES.utf8 LC_ALL=es_ES.utf8 grub2-mkconfig --output > /boot/grub2/grub.cfg > ``` > and after this yast2 bootloader should work. Happy new year!! I'm sorry but too much work from coming of holidays, but I just tried what you suggested. First, I checked my "locale" output (to try to understand why you forced it in command line): LANG=es_ES.UTF-8 LC_CTYPE="es_ES.UTF-8" LC_NUMERIC="es_ES.UTF-8" LC_TIME="es_ES.UTF-8" LC_COLLATE="es_ES.UTF-8" LC_MONETARY="es_ES.UTF-8" LC_MESSAGES="es_ES.UTF-8" LC_PAPER="es_ES.UTF-8" LC_NAME="es_ES.UTF-8" LC_ADDRESS="es_ES.UTF-8" LC_TELEPHONE="es_ES.UTF-8" LC_MEASUREMENT="es_ES.UTF-8" LC_IDENTIFICATION="es_ES.UTF-8" LC_ALL= Then I did what you suggested: `LANG=es_ES.utf8 LC_ALL=es_ES.utf8 grub2-mkconfig --output /boot/grub2/grub.cfg` And ... I worked like a charm!!!!!! You make it work again!!! I really don't know why this happen, but really I happy to be able to change parameters finally!! Thank you Josef -- You are receiving this mail because: You are on the CC list for the bug.

1 0