February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1122727] virtualbox build fail with kernel update in Leap 15.1
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1122727 http://bugzilla.opensuse.org/show_bug.cgi?id=1122727#c13 --- Comment #13 from Ludwig Nussel <lnussel(a)suse.com> --- Larry what is the status here? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124603] Various DisplayPort multi-monitor enabling and positioning randomness
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124603 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com, | |tzimmermann(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1116625] Systemd automount units fail after suspend/resume
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1116625 http://bugzilla.suse.com/show_bug.cgi?id=1116625#c35 --- Comment #35 from Franck Bui <fbui(a)suse.com> --- (In reply to Neil Brown from comment #34) > Meanwhile. I'll submit the systemd patch (comment #14) upstream. That wasn't > the cause of this problem, but it is still a bug. Good point, please let me know the link of your submission so I can track your fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1101870] Yast Partitioner crashes: "Luks bigger than parent BlkDevice"
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.novell.com/show_bug.cgi?id=1101870 http://bugzilla.novell.com/show_bug.cgi?id=1101870#c13 --- Comment #13 from LTC BugProxy <bugproxy(a)us.ibm.com> --- ------- Comment From preeti.thakur(a)in.ibm.com 2019-02-08 01:51 EDT------- verified with SL15SP1Beta3 on same system ltczep2-lp8 and storage exception is not seen though lvm related error messages popped up for which below defect is already there https://bugzilla.linux.ibm.com/show_bug.cgi?id=175045 also while disk boot below errors are seen..pasting for reference [FAILED] Failed to start LVM2 PV scan on device 8:225. See 'systemctl status lvm2-pvscan@8:225.service' for details. [FAILED] Failed to start LVM2 PV scan on device 8:33. See 'systemctl status lvm2-pvscan@8:33.service' for details. [FAILED] Failed to start LVM2 PV scan on device 8:97. See 'systemctl status lvm2-pvscan@8:97.service' for details. [ OK ] Mounted /home. [ OK ] Reached target Local File Systems. Starting Commit a transient machine-id on disk... Starting Restore /run/initramfs on shutdown... Starting Rebuild Journal Catalog... Starting Create Volatile Files and Directories... [FAILED] Failed to start LVM2 PV scan on device 8:3. See 'systemctl status lvm2-pvscan@8:3.service' for details. [ OK ] Started Rebuild Journal Catalog. Starting Update is Completed... [FAILED] Failed to start LVM2 PV scan on device 8:161. Steps Connect to VNC> disable multipath> proceed to install Below is the output after install for reference.. This defect can be closed Welcome to SUSE Linux Enterprise Server 15 SP1 Beta3 (ppc64le) - Kernel 4.12.14-30-default (hvc0). eth0: 9.40.192.49 2002:903:15f:550:1165:9fdb:bbb2:8ee5 linux-r8u9 login: root Password: linux-r8u9:~ # uname -a Linux linux-r8u9 4.12.14-30-default #1 SMP Fri Jan 25 15:21:53 UTC 2019 (7f76697) ppc64le ppc64le ppc64le GNU/Linux linux-r8u9:~ # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 30G 0 disk ??sda1 8:1 0 7M 0 part ??sda2 8:2 0 476M 0 part ??sda3 8:3 0 25.2G 0 part ??rhel_ltczep2--lp8-swap 254:0 0 8G 0 lvm [SWAP] ??rhel_ltczep2--lp8-root 254:1 0 12.1G 0 lvm / ??rhel_ltczep2--lp8-home 254:2 0 5.1G 0 lvm /home sdb 8:16 0 30G 0 disk sdc 8:32 0 30G 0 disk ??sdc1 8:33 0 30G 0 part sdd 8:48 0 30G 0 disk sde 8:64 0 30G 0 disk sdf 8:80 0 30G 0 disk sdg 8:96 0 30G 0 disk ??sdg1 8:97 0 30G 0 part sdh 8:112 0 30G 0 disk sdi 8:128 0 30G 0 disk sdj 8:144 0 30G 0 disk sdk 8:160 0 30G 0 disk ??sdk1 8:161 0 30G 0 part sdl 8:176 0 30G 0 disk sdm 8:192 0 30G 0 disk sdn 8:208 0 30G 0 disk sdo 8:224 0 30G 0 disk ??sdo1 8:225 0 30G 0 part sdp 8:240 0 30G 0 disk sr0 11:0 1 3.2G 0 rom sr1 11:1 1 3.5G 0 rom sr2 11:2 1 3.2G 0 rom sr3 11:3 1 618.1M 0 rom sr4 11:4 1 610.4M 0 rom sdq 65:0 0 30G 0 disk linux-r8u9:~ # df -Th Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 3.9G 128K 3.9G 1% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 3.9G 23M 3.9G 1% /run tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% / /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /boot/grub2/powerpc-ieee1275 /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /srv /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /.snapshots /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /root /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /var /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /opt /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /usr/local /dev/mapper/rhel_ltczep2--lp8-root btrfs 13G 1.9G 8.3G 19% /tmp /dev/mapper/rhel_ltczep2--lp8-home xfs 5.1G 38M 5.1G 1% /home tmpfs tmpfs 792M 0 792M 0% /run/user/0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124733] New: server:monitoring/monitorix: Bug - update runtime pkg dependency to include perl-rrdtool
by bugzilla_noreply＠novell.com 08 Feb '19

08 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124733 Bug ID: 1124733 Summary: server:monitoring/monitorix: Bug - update runtime pkg dependency to include perl-rrdtool Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: nix(a)opensuse.org Reporter: bryan.gartner(a)suse.com QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- For openSUSE Tumbleweed (at least), the following runtime requirement "perl-rrdtool" should be included in the package (spec) definition. Otherwise errors like the following appear in the /var/log/monitorix logfile (and no graph output occurs): Thu Feb 7 23:27:27 2019 - WARNING: unable to load module 'system'. Can't locate RRDs.pm in @INC (you may need to install the RRDs module) (@INC contains: /usr/bin/lib /usr/lib/monitorix /usr/lib/perl5/site_perl/5.28.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.28.1 /usr/lib/perl5/vendor_perl/5.28.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.28.1 /usr/lib/perl5/5.28.1/x86_64-linux-thread-multi /usr/lib/perl5/5.28.1 /usr/lib/perl5/site_perl) at /usr/lib/monitorix/system.pm line 26. BEGIN failed--compilation aborted at /usr/lib/monitorix/system.pm line 26. Compilation failed in require at (eval 9) line 1. BEGIN failed--compilation aborted at (eval 9) line 1. ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

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

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124707 Bug ID: 1124707 Summary: chromium crashes after latest tumbleweed update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: arun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi I just updated to the latest tumbleweed (zypper dup) and now chromium crashes when called from the command line. Here is what I get: ~>[2072:2072:0207/150445.072560:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process. [2038:2038:0207/150446.384295: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 ffffc9dc77268269 #0 0x55f80c5abac1 base::debug::StackTrace::StackTrace() #1 0x55f80c5aa4e3 base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x55f80c5aba25 base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7fb790f898f0 <unknown> #4 0x7fb79031611b <unknown> #5 0x7fb790316eb1 FcFontMatch #6 0x55f80cfc9bf2 gfx::GetFontRenderParams() #7 0x55f80af65e3e font_service::FontServiceApp::FontRenderStyleForStrike() #8 0x55f809d1473b font_service::mojom::FontServiceStubDispatch::AcceptWithResponder() #9 0x55f80af64a1a font_service::mojom::FontServiceStub<>::AcceptWithResponder() #10 0x55f80c60f497 mojo::InterfaceEndpointClient::HandleValidatedMessage() #11 0x55f80c6137f0 mojo::internal::MultiplexRouter::ProcessIncomingMessage() #12 0x55f80c616f8d mojo::internal::MultiplexRouter::Accept() #13 0x55f80c60c3a3 mojo::Connector::ReadSingleMessage() #14 0x55f80c60c9cb mojo::Connector::ReadAllAvailableMessages() #15 0x55f80c629c2e mojo::SimpleWatcher::OnHandleReady() #16 0x55f80c4f61b3 base::debug::TaskAnnotator::RunTask() #17 0x55f80c574a74 base::internal::TaskTracker::RunOrSkipTask() #18 0x55f80c5bd7e1 base::internal::TaskTrackerPosix::RunOrSkipTask() #19 0x55f80c577234 base::internal::TaskTracker::RunAndPopNextTask() #20 0x55f80c57104b base::internal::SchedulerWorker::RunWorker() #21 0x55f80c5716c3 base::internal::SchedulerWorker::RunPooledWorker() #22 0x55f80c5bd001 base::(anonymous namespace)::ThreadFunc() #23 0x7fb790f7eed4 start_thread #24 0x7fb78d814cbf __GI___clone r8: 000000000000001f r9: 00007fb77f179460 r10: 000000000000002e r11: 0000000000000000 r12: 00007fb7903315b5 r13: 0000362126d30b80 r14: 00007fb77f1795f8 r15: 00007fb77f1795f8 di: 0000000000004278 si: 00007fb77f179460 bp: 00007fb77f179528 bx: 000000000000084f dx: 00007fb77f179460 ax: ffffc9dc77263ff1 cx: 00007fb77f179700 sp: 00007fb77f179410 ip: 00007fb79031611b efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000005 trp: 000000000000000e msk: 0000000000000000 cr2: ffffc9dc77268269 [end of stack trace] Calling _exit(1). Core file will not be generated. >uname -a Linux apersaud 4.20.6-1-default #1 SMP PREEMPT Thu Jan 31 07:37:50 UTC 2019 (463cfd2) x86_64 x86_64 x86_64 GNU/Linux >cat os-release NAME="openSUSE Tumbleweed" # VERSION="20190205" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20190205" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20190205" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" I haven't noticed any other issues so far. Happy to provide more details if needed or try out other suggestions. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1123245] After zypper dup from Leap:15.0 to Tumbleweed boot fails intermittently failed to find grub_efi_allocate_fixed
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1123245 http://bugzilla.opensuse.org/show_bug.cgi?id=1123245#c12 --- Comment #12 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- >That would be Boot0002* judging by the order, Boot0000* is the default boot. Those two boot entries look identical to me. However Boot0001 looks different (using a different EFI partition). Normally, an entry for secure-boot uses "shim.efi" rather than "grubx64.efi". And I do not see such an entry. Can you provide the output from: ls -l /dev/disk/by-partuuid/64f81fb7-f76b-4029-93d1-f975379ae4c7 That should identify the EFI partition used for Boot0001. And can you also provide the output for: ls -l /boot/efi/EFI/opensuse/grubx64.efi ls -l /boot/grub2/x86_64-efi/core.efi >What I still don't understand is why Leap had no problems There was no reason for it to have problems. You were using the "grubx64.efi" installed by Leap 42.3, and it was using the "/boot/grub2/x86_64-efi/" also installed by Leap. Right now it looks as if you are still using the "grubx64.efi" installed by Leap, but you are using "/boot/grub2/x86_64-efi/" installed by Tumbleweed. And there's a mismatch. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1116625] Systemd automount units fail after suspend/resume
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1116625 http://bugzilla.suse.com/show_bug.cgi?id=1116625#c34 --- Comment #34 from Neil Brown <nfbrown(a)suse.com> --- Meanwhile. I'll submit the systemd patch (comment #14) upstream. That wasn't the cause of this problem, but it is still a bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106673] LUKS keyboard layout falls back to US instead of DE since last dracut update
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1106673 http://bugzilla.suse.com/show_bug.cgi?id=1106673#c24 --- Comment #24 from Michael Hirmke <opensuse(a)mike.franken.de> --- (In reply to Aender Boy from comment #22) > (In reply to Frank Kruger from comment #21) > > Does changing "de-latin1-nodeadkeys" to "de-nodeadkeys" in > > /etc/vconsole.conf, followed by sudo mkinitrd, solve the issue? > > yes. Thank you! > > Could you make this work automatically or alternatively add this to the wiki > page as an instruction? https://en.opensuse.org/SDB:Encrypted_filesystems does not work here on Tumbleweed 8-( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124701] New: games/mouseboat: Bug no longer runs
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124701 Bug ID: 1124701 Summary: games/mouseboat: Bug no longer runs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jon(a)moozaad.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- > MouseBoat OpenGL ES 3.0 Renderer: AMD Radeon (TM) R9 Fury Series (FIJI, DRM 3.27.0, 4.20.6-7-default, LLVM 7.0.1) ERROR: _load: No loader found for resource: /usr/share/MouseBoat At: core/io/resource_loader.cpp:186. ERROR: start: Failed loading scene: /usr/share/MouseBoat At: main/main.cpp:1688. WARNING: cleanup: ObjectDB Instances still exist! At: core/object.cpp:1989. Looks like it's incompatible with the latest godot (3?). I submitted a bug upstream https://github.com/CowThing/MouseBoat/issues/3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0