January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1180543] kernel 5.10.4: Displays never wake up, though on one system it does... network is also dead
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180543 https://bugzilla.suse.com/show_bug.cgi?id=1180543#c6 Michael Hirmke <opensuse(a)mike.franken.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse(a)mike.franken.de --- Comment #6 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Jiri Slaby from comment #5) > (In reply to Bit Juggler from comment #4) > > Hope this helps. > > It would actually have helped if you had tried what is suggested in comment > #3. Had the same problem today with my DELL XPS. Using snd_hda_codec_hdmi.enable_silent_stream=0 worked around the problem, and I got back my graphics environment. Thx! Bye. Michael. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180228] New: Geeqie fails to start
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180228 Bug ID: 1180228 Summary: Geeqie fails to start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: dutchkind(a)txoriaskea.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since a few days Geeqie fails to open. I think it was after some update to the latest version. When I try to start from terminal I get the following output: Xlib: sequence lost (0x100ac > 0xae) in reply type 0x0! (geeqie:12159): Gdk-ERROR **: 17:22:56.198: The program 'geeqie' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 186 error_code 2 request_code 152 (GLX) minor_code 24) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Would be very nice to get this fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1180377] libpython3_6m1_0 undefined symbol: PyFPE_jbuf (was borgbackup)
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180377 https://bugzilla.suse.com/show_bug.cgi?id=1180377#c29 --- Comment #29 from Felix Niederwanger <felix.niederwanger(a)suse.com> --- Not sure if this is relevant, but the bug appears to be still present on Leap 15-SP3: http://duck-norris.qam.suse.de/tests/4424#step/python_scientific/10 But I guess this is already known. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180609] i915: No picture in Gnome/Wayland after booting to kernel v5.10.4
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180609 http://bugzilla.opensuse.org/show_bug.cgi?id=1180609#c2 Frank Kr�ger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org --- Comment #2 from Frank Kr�ger <fkrueger(a)mailbox.org> --- Cf. https://bugzilla.suse.com/show_bug.cgi?id=1180543#c3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180609] New: i915: No picture in Gnome/Wayland after booting to kernel v5.10.4
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180609 Bug ID: 1180609 Summary: i915: No picture in Gnome/Wayland after booting to kernel v5.10.4 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844879 --> https://bugzilla.suse.com/attachment.cgi?id=844879&action=edit Boot log from v5.10.4 (no picture) After kernel upgrade to v5.10.4 there is no picture in my graphical desktop (Gnome+Wayland). Screen backlight is lit but there is no picture on neither the laptop display nor the HDMI attached external display. Booting back to v5.10.3 fixes the issue. Hardware: Dell Inspiron 7373 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1180608] New: sort -n with fr_FR.UTF-8 does not work.
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180608 Bug ID: 1180608 Summary: sort -n with fr_FR.UTF-8 does not work. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: denebe_(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: sort with the french local LANG=fr_FR.UTF-8 doesn't work correctly in some situation. It works properly in german or in english. I create a file zz.txt: thierry@toto-PC:~> cat zz.txt 1 2 0 1 1 1 2 1 2 1 11 3 TEST 1A (in french): thierry@toto-PC:~> LANG=fr_FR.UTF-8 thierry@toto-PC:~> sort -n zz.txt 1 1 1 1 2 0 2 1 2 1 11 3 We can see, that the file zz.txt is not properly sorted, it fails. TEST 1B (in german) thierry@toto-PC:~> LANG=de_DE.UTF-8 thierry@toto-PC:~> sort -n zz.txt 1 1 1 1 11 3 1 2 0 2 1 2 it works properly. With the US langage it also works properly. TEST 2A (in french): thierry@toto-PC:~> LANG=fr_FR.UTF-8 thierry@toto-PC:~> ls -l /usr/bin/ | sort --debug -nrk 5 | head -n 30 ... --debug show that the fields, that are used to sort, are strange�� 1. if the number of the day has two numbers, then the fields, that are used to sort, are the 5 and the 6 (with blanks in the middle) 2. if the the number of the day has only one number, then there only the field 5 is used to sort (without blank after��) => the output is then falsh. We can see it without --debug and with a big value of -n (300��). TEST 2B (in german, or english): thierry@toto-PC:~> LANG=de_DE.UTF-8 # or us_US.UTF-8 thierry@toto-PC:~> ls -l /usr/bin/ | sort --debug -nrk 5 | head -n 30 ... --debug show that the fields, that are used to sort, are always the 5. => the output is then correct Reproducible: Always Steps to Reproduce: 1.LANG=fr_FR.UTF-8 2.ls -l /usr/bin/ | sort -nrk 5 | head -n 250 3. Actual Results: -rwxr-xr-x 1 root root 15182904 12. mai 2020 flashplayer -rwxr-xr-x 1 root root 9441608 25. juin 2020 gimp-2.10 -rwxr-xr-x 1 root root 6323384 16. mai 2020 librecad -rwxr-xr-x 1 root root 3625200 15. juin 2020 kleopatra -rwxr-xr-x 1 root root 3589528 25. juin 2020 gimp-console-2.10 -rwxr-xr-x 1 root root 3188584 16. mai 2020 konversation -rwxr-xr-x 1 root root 3159680 28. oct. 14:01 zypper -rwxr-xr-x 1 root root 2992656 23. nov. 23:59 vim-nox11 -rwxr-xr-x 1 root root 2496112 10. oct. 02:57 Xvnc -rwxr-xr-x 1 root root 22878400 2. d��c. 15:13 mariabackup Expected Results: -rwxr-xr-x 1 root root 22878400 2. Dez 15:13 mariabackup -rwxr-xr-x 1 root root 15182904 12. Mai 2020 flashplayer -rwxr-xr-x 1 root root 12626608 1. Jan 11:51 gdb -rwxr-xr-x 1 root root 9441608 25. Jun 2020 gimp-2.10 -rwxr-xr-x 1 root root 9112288 7. Dez 23:28 ld.bfd -rwxr-xr-x 1 root root 6323384 16. Mai 2020 librecad -rwxr-xr-x 1 root root 5123096 2. Dez 15:13 mysql_ldb -rwxr-xr-x 1 root root 5123072 2. Dez 15:13 sst_dump -rwxr-xr-x 1 root root 4508080 2. Dez 15:13 aria_chk -rwxr-xr-x 1 root root 4466416 2. Dez 15:13 aria_read_log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180059] New: unicode different with firefox and chrome ?
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180059 Bug ID: 1180059 Summary: unicode different with firefox and chrome ? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSuse 15.2 kde environment FF 83.0 Chrome 87.0.4280.88 I discover a recent problem. If I copy past from FF to chrome a password to access to the same site then I can't log in to the site with chrome. If I copy past from chrome to FF a password to access to the same site then I can't log in to the site with FF. Example of password leading to this problem : Gohc4#MectNaco Is it a kde or a FF or a chrome problem ? -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1179170] grub2 efi posttrans update-bootloader script fails
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179170 https://bugzilla.suse.com/show_bug.cgi?id=1179170#c6 --- Comment #6 from Gary Ching-Pang Lin <glin(a)suse.com> --- (In reply to Michael Chang from comment #5) > (In reply to Gary Ching-Pang Lin from comment #4) > > > It sets immutable to 0 and unlinks the path. In > > kernel/drivers/firmware/efi/vars.c, when removing a file, it uses > > uefi_set_variable() with NULL to delete the variable, and this is unlikely > > to fail. > > Yes that is where I'm looking at. There's no obvious system call made > besides ioctl to set the immutable flag would return invalid argument. > > > Maybe there are more clues in /var/log/pbl.log. > > Maybe we should enable verbose output to collect more info ? > > Index: efivar-37/src/efivar.c > =================================================================== > --- efivar-37.orig/src/efivar.c > +++ efivar-37/src/efivar.c > @@ -63,7 +63,7 @@ static const char *attribute_names[] = { > "" > }; > > -static int verbose_errors = 0; > +static int verbose_errors = 1; > > static void > show_errors(void) It'd be better to set the verbosity from efibootmgr like this: https://github.com/rhboot/efibootmgr/blob/master/src/efibootmgr.c#L1675 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179170] grub2 efi posttrans update-bootloader script fails
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179170 https://bugzilla.suse.com/show_bug.cgi?id=1179170#c5 --- Comment #5 from Michael Chang <mchang(a)suse.com> --- (In reply to Gary Ching-Pang Lin from comment #4) > It sets immutable to 0 and unlinks the path. In > kernel/drivers/firmware/efi/vars.c, when removing a file, it uses > uefi_set_variable() with NULL to delete the variable, and this is unlikely > to fail. Yes that is where I'm looking at. There's no obvious system call made besides ioctl to set the immutable flag would return invalid argument. > Maybe there are more clues in /var/log/pbl.log. Maybe we should enable verbose output to collect more info ? Index: efivar-37/src/efivar.c =================================================================== --- efivar-37.orig/src/efivar.c +++ efivar-37/src/efivar.c @@ -63,7 +63,7 @@ static const char *attribute_names[] = { "" }; -static int verbose_errors = 0; +static int verbose_errors = 1; static void show_errors(void) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179170] grub2 efi posttrans update-bootloader script fails
by bugzilla_noreply＠suse.com 06 Jan '21

06 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179170 https://bugzilla.suse.com/show_bug.cgi?id=1179170#c4 Gary Ching-Pang Lin <glin(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(glin(a)suse.com) | --- Comment #4 from Gary Ching-Pang Lin <glin(a)suse.com> --- The deletion of uefi variable in efivar is quite simple: static int efivarfs_del_variable(efi_guid_t guid, const char *name) { char *path; int rc = make_efivarfs_path(&path, guid, name); if (rc < 0) { efi_error("make_efivarfs_path failed"); return -1; } efivarfs_set_immutable(path, 0); rc = unlink(path); if (rc < 0) efi_error("unlink failed"); __typeof__(errno) errno_value = errno; free(path); errno = errno_value; return rc; } It sets immutable to 0 and unlinks the path. In kernel/drivers/firmware/efi/vars.c, when removing a file, it uses uefi_set_variable() with NULL to delete the variable, and this is unlikely to fail. Maybe there are more clues in /var/log/pbl.log. -- You are receiving this mail because: You are on the CC list for the bug.

1 0