September 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1176207] Chromium: no hardware acceleration after updating to 85.0.4183.69
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176207 https://bugzilla.suse.com/show_bug.cgi?id=1176207#c16 John Paul Adrian Glaubitz <adrian.glaubitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.glaubitz(a)suse.com --- Comment #16 from John Paul Adrian Glaubitz <adrian.glaubitz(a)suse.com> --- (In reply to Dan Rask from comment #13) > (In reply to Tomáš Chvátal from comment #12) > > You can try on commandline to force the engine: > > > > chromium --use-gl=egl > > > > to get the acceleration on Wayland, another option is 'desktop' to get it on > > Xorg afaik. > > Adding --use-gl=desktop to /etc/default/chromium helped and > chromium-85.0.4183.83-lp152.2.25.1.x86_64 started using Mesa again instead > of SwiftShader, giving me the proper hardware acceleration. Seems weird, > that the previous version works with Mesa without this flag though. These additional flags added make those GL error messages go away, but Chromium still crashes for me: [10530:10530:0911/115249.446601:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [10498:10513:0911/115252.555730:FATAL:memory_linux.cc(37)] Out of memory. #0 0x5622d8455112 (/usr/lib64/chromium/chromium+0x3be6111) #1 0x5622dd267a02 (/usr/lib64/chromium/chromium+0x89f8a01) #2 0x5622d8386c6d (/usr/lib64/chromium/chromium+0x3b17c6c) #3 0x5622d847335d (/usr/lib64/chromium/chromium+0x3c0435c) #4 0x5622d839fc9e operator new() #5 0x5622dd5c2a1f (/usr/lib64/chromium/chromium+0x8d53a1e) #6 0x5622d83cbd37 (/usr/lib64/chromium/chromium+0x3b5cd36) #7 0x5622d9d40e9d (/usr/lib64/chromium/chromium+0x54d1e9c) #8 0x5622d9d413a8 (/usr/lib64/chromium/chromium+0x54d23a7) #9 0x5622d9d417c9 (/usr/lib64/chromium/chromium+0x54d27c8) #10 0x5622d9c701b6 (/usr/lib64/chromium/chromium+0x54011b5) #11 0x5622d62a80b1 (/usr/lib64/chromium/chromium+0x1a390b0) #12 0x5622d62b285f (/usr/lib64/chromium/chromium+0x1a4385e) #13 0x5622d5fe8566 (/usr/lib64/chromium/chromium+0x1779565) #14 0x5622d84764bc (/usr/lib64/chromium/chromium+0x3c074bb) #15 0x5622d84b754f (/usr/lib64/chromium/chromium+0x3c4854e) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175341] Could not configure "print over network" with yast2 printer
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175341 https://bugzilla.suse.com/show_bug.cgi?id=1175341#c1 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED URL| |https://lists.opensuse.org/ | |yast-devel/2015-03/msg00044 | |.html Found By|--- |Community User Resolution|--- |WONTFIX --- Comment #1 from Johannes Meixner <jsmeix(a)suse.com> --- Regarding the YaST printer module: In practice the YaST printer module is no longer acually further developed since it was "converted from YCP to Ruby by YCP Killer" that happened in July 2013, see the yast2-printer.changes entry ---------------------------------------------------------- Wed Jul 31 08:37:43 UTC 2013 - yast-devel(a)opensuse.org - converted from YCP to Ruby by YCP Killer (https://github.com/yast/ycp-killer) - version 3.0.0 ---------------------------------------------------------- at https://build.opensuse.org/package/view_file/YaST:Head/yast2-printer/yast2-… My last change is dated Mon Jan 19 14:51:39 UTC 2015 and my last actual further development enhancement are dated before it was "converted from YCP to Ruby by YCP Killer". Since that time the YaST printer module is kept working as is as far as possible with reasonable effort by YaST team members who know about how to deal with their generated Ruby code. Since my YCP code was converted into generated Ruby code it is no longer my code and it is no longer code that I could further develop with reasonable effort. Because the YaST printer module is based on the traditional way how printing works with CUPS <= 1.5.4 in particular for printing in the network, the YaST printer module intentionally fails with error messages when things won't work with nowadays way how printing in the network works with CUPS >= 1.6 cf. "CUPS >= 1.6 has major incompatible changes" in https://en.opensuse.org/SDB:CUPS_in_a_Nutshell According to htps://bugzilla.suse.com/page.cgi?id=status_resolution_matrix.html I can only close it as "wontfix" because this issue is a bug but it cannot be fixed in practice in foreseeable future. See also https://lists.opensuse.org/yast-devel/2015-03/msg00044.html https://features.opensuse.org/308045 https://features.opensuse.org/316789 At least currently links to features.opensuse.org fail with "the service you want to access is not supported any longer" so it seems those feature requests are no longer accessible. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159963] post-build-checks breaks permissions
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159963 http://bugzilla.opensuse.org/show_bug.cgi?id=1159963#c17 Fabian Vogt <fabian(a)ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fabian@ritter-vog | |t.de) | --- Comment #17 from Fabian Vogt <fabian(a)ritter-vogt.de> --- (In reply to Ruediger Oertel from comment #16) > well, build-compare hides the change in this case. No, that's why I asked for a wipebinaries a few days ago. The build log shows that the used post-build-checks version includes the fix. > if you manually branch that and force a real rebuild (or watch the buildlog > during a rebuild in the project above) you will see: It works in branches, but not in openSUSE:Factory(:Rebuild), probably because post-build-checks is installed after fuse3 (see the initial bug description). > [ 55s] fusermount3: missing mountpoint argument > [ 55s] + ret=1 > [ 55s] + '[' 1 -eq 126 ']' > > so the call to fusermount3 does not fail because of permissions IMHO That means it works. It checks for the exit code of 126 explicitly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174709] cups-browsed restart fails with "status=1/FAILURE" when there is an invalid leftover queue from a previous run
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

1 0

[Bug 1175597] cups-browsed fails with "status=1/FAILURE"
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

1 0

[Bug 1175597] can not print on remote printers
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1175597 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174709] cups-browsed crashes when detected printers become unavailable
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1174709 https://bugzilla.suse.com/show_bug.cgi?id=1174709#c4 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner(a)suse.com --- Comment #4 from Johannes Meixner <jsmeix(a)suse.com> --- *** Bug 1175597 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1159963] post-build-checks breaks permissions
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1159963 http://bugzilla.opensuse.org/show_bug.cgi?id=1159963#c15 Fabian Vogt <fabian(a)ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fabian@ritter-vog | |t.de) | --- Comment #15 from Fabian Vogt <fabian(a)ritter-vogt.de> --- (In reply to Ruediger Oertel from comment #14) > can I get project and package of that build please ? Sure: https://build.opensuse.org/package/show/openSUSE:Factory:Rebuild/kio-fuse -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176246] aarch64 Leap 15.2 container image fails to build
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

https://bugzilla.suse.com/show_bug.cgi?id=1176246 https://bugzilla.suse.com/show_bug.cgi?id=1176246#c6 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #6 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Adrian Schröter from comment #3) > Kernel modules where missing due to a missing path in template project. > > Fabian, I have added the :Images project repo in > openSUSE:Containers:Leap:15.2 for containers_ports as well. openSUSE:Leap:15.2 is missing the "system-packages:docker" substitute, which 15.2:Images has. I changed openSUSE:Containers:Leap:15.2/containers_ports to build against openSUSE:Leap:15.2:Images/ports now, like 15.1. (In reply to Duncan Mac-Vicar from comment #5) > I can't find it in registry.opensuse.org? Do I need to do something special > to have it pushed there? No, but you need to enable publishing. Currently you have it disabled at the project level. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176304] GDM showing openSUSE / SUSE logo
by bugzilla_noreply＠suse.com 11 Sep '20

11 Sep '20

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

1 0