February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1124885] GRUB2 doesn't display UFT-8 characters for KIWI-ng generated LiveCD ISO images
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124885 http://bugzilla.opensuse.org/show_bug.cgi?id=1124885#c2 --- Comment #2 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- (In reply to Mindaugas Baranauskas from comment #1) > > In other image, generated locally by kiwi-ng, I see: > set font=($root)/boot/x86_64/loader/unicode.pf2 > Similarly, unicode.pf2 exist in other place as > /boot/grub2/unicode.pf2 Please ignore cited part of text. Correct text should be: In other image, generated locally by kiwi-ng, I see: set font=($root)/boot/x86_64/loader/unicode.pf2 Similarly, unicode.pf2 exist in other place as /boot/unicode.pf2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124886] Can not change name or URL of repository via YaST
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124886 http://bugzilla.suse.com/show_bug.cgi?id=1124886#c3 Frank Kruger <fkrueger(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fkrueger(a)mailbox.org --- Comment #3 from Frank Kruger <fkrueger(a)mailbox.org> --- (In reply to Mindaugas Baranauskas from comment #0) > Created attachment 796446 [details] > y2logs > > YaST repository module can not change repo name or repo URL. > You can press Edit button, write different name or URL, but this editing has > no effect. It is a known issue (cf. https://bugzilla.suse.com/show_bug.cgi?id=1117079) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124863] VUL-0: CVE-2019-7443: kauth: Insecure handling of arguments in helpers
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124863 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |security-team(a)suse.de Summary|kauth: Insecure handling of |VUL-0: CVE-2019-7443: |arguments in helpers |kauth: Insecure handling of |(CVE-2019-7443) |arguments in helpers Alias| |CVE-2019-7443 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124886] Can not change name or URL of repository via YaST
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124886 http://bugzilla.suse.com/show_bug.cgi?id=1124886#c2 --- Comment #2 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- The same problem in installed system (not Live system) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124886] Can not change name or URL of repository via YaST
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124886 http://bugzilla.suse.com/show_bug.cgi?id=1124886#c1 --- Comment #1 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- i.e. with openSUSE-Leap-15.0-KDE-Live-x86_64-Snapshot20.130-Media.iso -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124886] New: Can not change name or URL of repository via YaST
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124886 Bug ID: 1124886 Summary: Can not change name or URL of repository via YaST Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 796446 --> http://bugzilla.opensuse.org/attachment.cgi?id=796446&action=edit y2logs YaST repository module can not change repo name or repo URL. You can press Edit button, write different name or URL, but this editing has no effect. This is regression compared to openSUSE Leap 42.3 Tested with openSUSE KDE LiveCD -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124881] New: Chromium crashes on startup
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=1124881 Bug ID: 1124881 Summary: Chromium crashes on startup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bart.vanassche+novell(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running the following command: chromium --user-data-dir=$HOME/.config/chromium/Gmail https://mail.google.com https://calendar.google.com https://drive.google.com https://photos.google.com https://hangouts.google.com https://www.google.com/alerts results in the following crash: [9621:9621:0209/192429.355737:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process. [9589:9611:0209/192429.802274:ERROR:nss_util.cc(748)] After loading Root Certs, loaded==false: NSS error code: -8018 [9589:9589:0209/192429.836372:ERROR:x11_input_method_context_impl_gtk.cc(144)] Not implemented reached in virtual void libgtkui::X11InputMethodContextImplGtk::SetSurroundingText(const string16&, const gfx::Range&) Received signal 11 SEGV_MAPERR 0863604ff0d5 #0 0x55951d7e6ac1 base::debug::StackTrace::StackTrace() #1 0x55951d7e54e3 base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x55951d7e6a25 base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7f549436a8f0 <unknown> #4 0x7f54936f6f51 <unknown> #5 0x7f54936f8115 FcFontSetSort #6 0x7f54936f877c FcFontSort #7 0x55951e18a585 SkFontConfigInterfaceDirect::matchFamilyName() #8 0x55951c1a084c font_service::FontServiceApp::MatchFamilyName() #9 0x55951af4fc71 font_service::mojom::FontServiceStubDispatch::AcceptWithResponder() #10 0x55951c19fa1a font_service::mojom::FontServiceStub<>::AcceptWithResponder() #11 0x55951d84a497 mojo::InterfaceEndpointClient::HandleValidatedMessage() #12 0x55951d84e7f0 mojo::internal::MultiplexRouter::ProcessIncomingMessage() #13 0x55951d851f8d mojo::internal::MultiplexRouter::Accept() #14 0x55951d8473a3 mojo::Connector::ReadSingleMessage() #15 0x55951d8479cb mojo::Connector::ReadAllAvailableMessages() #16 0x55951d864c2e mojo::SimpleWatcher::OnHandleReady() #17 0x55951d7311b3 base::debug::TaskAnnotator::RunTask() #18 0x55951d7afa74 base::internal::TaskTracker::RunOrSkipTask() #19 0x55951d7f87e1 base::internal::TaskTrackerPosix::RunOrSkipTask() #20 0x55951d7b2234 base::internal::TaskTracker::RunAndPopNextTask() #21 0x55951d7ac04b base::internal::SchedulerWorker::RunWorker() #22 0x55951d7ac6c3 base::internal::SchedulerWorker::RunPooledWorker() #23 0x55951d7f8001 base::(anonymous namespace)::ThreadFunc() #24 0x7f549435fed4 start_thread #25 0x7f5490bf5cbf __GI___clone r8: 0000000000000021 r9: 000008666160af78 r10: 000000000000002e r11: 0000000000000000 r12: 000008666071d820 r13: 0000000000000000 r14: 00007f549371e040 r15: 000008666160b048 di: 0000000000000001 si: 00000866604ff0d0 bp: 00000866604ff0d0 bx: 0000000000000000 dx: 00000863604ff0d5 ax: 0000086660d2c600 cx: 0000000000000001 sp: 00007f5484107640 ip: 00007f54936f6f51 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 00000863604ff0d5 [end of stack trace] Calling _exit(1). Core file will not be generated. Version information: $ cat /etc/issue.net Welcome to openSUSE Tumbleweed 20190205 - Kernel %r (%t). $ rpm -qf /usr/bin/chromium chromium-71.0.3578.98-3.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124707] chromium crashes after latest tumbleweed update
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=1124707 Bart Van Assche <bart.vanassche+novell(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bart.vanassche+novell@gmail | |.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124878] New: M17N build status still shows 'not found' SLE_12_SP1 repository
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124878 Bug ID: 1124878 Summary: M17N build status still shows 'not found' SLE_12_SP1 repository Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: qantas94heavy(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- It appears that SLE_12_SP1 is still shown in build status for M17N, but when you click on it, the following error appears: "Couldn't find repository 'SLE_12_SP1'. Are you sure it still exists?" The repository page does not show SLE_12_SP1 as present: https://build.opensuse.org/repositories/M17N -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1122174] [Build 142.1] multiple missing icons
by bugzilla_noreply＠novell.com 10 Feb '19

10 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1122174 http://bugzilla.opensuse.org/show_bug.cgi?id=1122174#c10 Christian Boltz <suse-beta(a)cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta(a)cboltz.de --- Comment #10 from Christian Boltz <suse-beta(a)cboltz.de> --- (In reply to Marco Calistri from comment #9) > if I click on Yast configuration_management I get the following error: > > "There are no formulas available. Please check the log files.There are no > formulas available. Please check the log files." That sounds like a completely different bug - please open a separate bugreport for it. > But I don't know where is the log for this error. Run save_y2logs to collect the logs, for details see https://en.opensuse.org/openSUSE:Report_a_YaST_bug -- You are receiving this mail because: You are on the CC list for the bug.

1 0