November 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1192067] Rust1.55 miscompiles Firefox on Tumbleweed
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192067 https://bugzilla.suse.com/show_bug.cgi?id=1192067#c15 --- Comment #15 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Manfred Hollstein from comment #0) > <https://build.opensuse.org/project/show/home:manfred-h:mozilla> ... seems to work for me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1105229] GnomeShell/Plasmashell doesn't work with wayland-egl1 from wayland (still worked with wayland-egl1 from Mesa)
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1105229 https://bugzilla.suse.com/show_bug.cgi?id=1105229#c22 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |alynx.zhou(a)suse.com Resolution|--- |FIXED --- Comment #22 from Alynx Zhou <alynx.zhou(a)suse.com> --- Close as fixed and no new comment. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c47 --- Comment #47 from guek wu neo <guek.neo(a)toshibagcs.com> --- (In reply to Thomas Zimmermann from comment #45) > (In reply to guek wu neo from comment #40) > > (In reply to guek wu neo from comment #38) > > > (In reply to Takashi Iwai from comment #37) > > > > Then please try the quarterly update release of SLE15-SP3. It contains the > > > > recent upstream kernel in the installer, and this might have been already > > > > fixed. > > > > > I tried 'SLE-15-SP3-Full-x86_64-QU1-Media1.iso' that is with kernel > > 5.3.18=59.24-default.. but still run into the same red error prompt > > 'An error occured during the installation' > > Can you please confirm that the kernel bug is present even with the latest > installer? > > According to our internal logs, the kernel fix was added on Jan 12. It > should have been in the installer since forever. If it still shows up, > there's maybe another issue here. :/ Yes, see comment 46 :attachment 853485 for the Zip of /var/log of the affected system of TigerLake. Xorg.0.log: "..[ 86.031] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f982ae3234d] [ 86.031] (EE) 10: Xorg (_start+0x2a) [0x562700cc9cba] [ 86.031] (EE) [ 86.031] (EE) Segmentation fault at address 0x0 [ 86.031] (EE) Fatal server error: [ 86.031] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 86.031] (EE) [ 86.031] (EE) ...? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192279] New: re-engineer reporting of locked packages during up and dup operations
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192279 Bug ID: 1192279 Summary: re-engineer reporting of locked packages during up and dup operations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Original summary: re-engineer reporting of locked packages during up and dup operations Mailing list thread starter (7 participants total): Summary: unnecessarily noisy zypper -v <https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…> There seemed to be a consensus that some improvement would be desirable, instead of such locks as *-lang or texlive* generating a list of thousands of locked packages, of which only the first hundred or so litter the screen before being ellipses'd and a 4 digit total presented: [quote]# zypper -n dup -l Retrieving repository�� The following 8109 items are locked and will not be changed by any action: Available:�� brltty brltty-debuginfo brltty-debugsource brltty-driver-at-spi2 �� texlive-addfont-doc ... and 8006 more items. Installed: cherrytree cherrytree-lang iwscanner Run 'zypper locks -s' to see the complete list of locked items. �� [/quote] IMO, detailed reporting of locked packages that are not installed do not need mentioning, unless possibly as a summary total, whether with or without zypper's -v option. Leave detailed locks reporting of uninstalled packages to the ll -s options. It's entirely silly to show a list subset that concludes with ellipsis. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c3 --- Comment #3 from Jason Straight <jason-opensuse(a)straights.net> --- (In reply to Takashi Iwai from comment #2) > Hrm, it's very hard to judge only from the description... Does the problem > appear without graphics? > > Basically the best option for hunting the culprit would be the git > bisection. If you don't mind to compile the kernel by yourself, it'd be > appreciated to perform git bisection. > > The kernel build itself won't be too difficult in this case. It'll need the > significant disk space and certain compile time, though. Booted with latest nvidia drivers that updated today and the problem appears to be gone, so it was likely just the last nvidia driver with that kernel version. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188922] AUDIT-TRACKER: barrier: security report for Barrier networking logic
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188922 https://bugzilla.suse.com/show_bug.cgi?id=1188922#c15 --- Comment #15 from Simon Lees <simonf.lees(a)suse.com> --- Unfortunately the 2.4.0 tarball is missing some files we need so we are now blocked on https://github.com/debauchee/barrier/issues/1373 if I don't see any progress there in the next day or so then i'll take the 2.3.4 release until its resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c46 --- Comment #46 from guek wu neo <guek.neo(a)toshibagcs.com> --- Created attachment 853485 --> https://bugzilla.suse.com/attachment.cgi?id=853485&action=edit zip of /var/log of the affected system -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192248] $HOME/.local/bin not part of PATH
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192248 http://bugzilla.opensuse.org/show_bug.cgi?id=1192248#c5 Neil Rickert <nwr10cst-oslnx(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx(a)yahoo.com --- Comment #5 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- I am not persuaded that this makes any sense. Traditionally, such user executables have been in "$HOME/bin", and that is on the default path. That tradition existed before "freedesktop.org", and even before linux existed. I occasionally find it useful to: rm -rf .local .config .cache so that the next login will reset my desktop back to default settings. I do not want to delete user executables when I do that. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041112] KDE packagekit update dialog shows still updates available for a short time after applying updates
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1041112 https://bugzilla.suse.com/show_bug.cgi?id=1041112#c90 --- Comment #90 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: kde https://openqa.opensuse.org/tests/2009712 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192178] New: AutoYaST <authorized_key> not working on openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192178 Bug ID: 1192178 Summary: AutoYaST <authorized_key> not working on openSUSE Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST Assignee: yast2-maintainers(a)suse.de Reporter: opensuse(a)wolke7.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853443 --> http://bugzilla.opensuse.org/attachment.cgi?id=853443&action=edit /var/log/YaST2/*; /var/log/zypp/*; /var/log/zypper.log; etc. Hello, I'm making my own autoinst.xml files. Everything works fine but I cannot give a user authorized_keys file. After installing, I login and find there is no $HOME/.ssh/authorized_keys files, even no $HOME/.ssh folder. Below is part of autoinst.xml: <user t="map"> <username>user_name</username> <encrypted t="boolean">true</encrypted> <user_password>xxxxxxxxxxxx</user_password> <authorized_keys t="list"> <authorized_key>ssh-rsa xxxxxxxxxx</authorized_key> </authorized_keys> </user> Is there a bug that authorized_keys cannot be assigned in AutoYast? I search online finding someone else uses <chroot-scripts> to add authorized_key. eg:https://gist.github.com/ofrzeta/60d895d8ddbd581ac9f08b16c36ba6a9 which may confirm that <authorized_keys> in AutoYast doesn't work. Below I attach the log files: /etc/os-release /var/log/zypper.log /var/log/YaST2/* /var/log/zypp/* autoinst.xml Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 3