April 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1084640] GCC 8: open-iscsi build fails
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084640 http://bugzilla.suse.com/show_bug.cgi?id=1084640#c11 --- Comment #11 from Martin Liška <martin.liska(a)suse.com> --- I can confirm that Factory version is fine. There must be some broken link in OBS. Thanks for the fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084812] [aarch64] IPv4 DNS leading to segfaults
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084812 http://bugzilla.suse.com/show_bug.cgi?id=1084812#c28 --- Comment #28 from Richard Biener <rguenther(a)suse.com> --- There is the --fix-cortex-a53-843419 linker option (-Wl,--fix-cortex-a53-843419 if you use the GCC driver), also enabled via -mfix-cortex-a53-843419 (at link time). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087713] New: firefox about dialog on Leap 15 says Tumbleweed
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1087713 Bug ID: 1087713 Summary: firefox about dialog on Leap 15 says Tumbleweed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://openqa.opensuse.org/tests/647395/modules/firef ox/steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The Firefox about dialog in Leap 15 says that Firefox is from Tumbleweed. I guess the branding package needs to be adjusted to check for %sle_version -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 834155] GCC runs out of memory trying to allocate 3 GB during a compilation
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=834155 http://bugzilla.suse.com/show_bug.cgi?id=834155#c6 Richard Biener <rguenther(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX Flags|needinfo?(matz(a)suse.com) | --- Comment #6 from Richard Biener <rguenther(a)suse.com> --- It's not fixed on the GCC side in Leap/SLE but there's no plan to do so given the input to GCC is invalid. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078708] yast broken bootloader
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1078708 http://bugzilla.suse.com/show_bug.cgi?id=1078708#c3 --- Comment #3 from Josef Reidinger <jreidinger(a)suse.com> --- It should be only temporary glitch of inconsistent repo. Can you please retry it with the latest TW DVD now? Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084630] GCC 8: libstoragemgmt build fails
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084630 http://bugzilla.suse.com/show_bug.cgi?id=1084630#c4 --- Comment #4 from nick wang <nwang(a)suse.com> --- The pr mentioned in Comment#3 is still open. The patch passed the test on obs, will submit as long as the pr is merged. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087749] New: pam_mount with LUKS encrypted /home partition unwarily umounts /home at logout
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1087749 Bug ID: 1087749 Summary: pam_mount with LUKS encrypted /home partition unwarily umounts /home at logout Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: i686 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ChG(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- LUKS-encrypted /home partition gets un-mounted at logout of any user, even when there are still other users logged in, effectively kicking them out. The /home partition (common to all users) as a whole is encrypted - for collaboration reasons, we don't use individual /home/<user> containers separately encrypted. Details: The /home partition is a LUKS device on /dev/sda4, with passwords of several users in the LUKS device's key slots. Concurrent login of several users works, but logging out any one of them kicks all others out, due to /home being forcibly umount'ed. This is unacceptable for a workstation used by several users - even root is affected when its login shell happens to have 'cd'ed into any of the /home subbdirectories. Furthermore, it renders the "Switch User" function of the (KDE) login screen useless: user A logs in, leaves the desktop and his screen locks up, user B "switches user" to himself, does its work and logs out again - user A is kicked off the system, loosing all unsaved work. How the volume was created and users were added: # cryptsetup --verify-passphrase --use-random --header-backup-file=/root/home.LUKS luksFormat /dev/sda4 # cryptsetup --verify-password luksAddKey /dev/sda4 In /etc/security/pam_mount.conf.xml, the following options are set: <logout wait="2000" hup="no" term="yes" kill="yes" /> Changing this does not help, as pam_mount uses the "ofl" tool from the "hxtools" package to TERMinate or KILL processes still using /home/user. According to "man ofl", it can NOT differentiate between processes of different users, effectively killing ALL processes still having anything open in /home. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1084640] GCC 8: open-iscsi build fails
by bugzilla_noreply＠novell.com 02 Apr '18

02 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084640 http://bugzilla.suse.com/show_bug.cgi?id=1084640#c9 Lee Duncan <lduncan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #9 from Lee Duncan <lduncan(a)suse.com> --- Factory open-iscsi submitted to SLE-15, but probably won't make GA? Note that open-iscsi sources are the same for SLE-15:GA and for Factory at this time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084640] GCC 8: open-iscsi build fails
by bugzilla_noreply＠novell.com 02 Apr '18

02 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084640 http://bugzilla.suse.com/show_bug.cgi?id=1084640#c8 --- Comment #8 from Lee Duncan <lduncan(a)suse.com> --- (In reply to Martin Liška from comment #7) > The package update landed to Factory, but I still can see the failure: > https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging: > Gcc7/open-iscsi/standard/x86_64 > > I double checked that by building the package locally. That is still the old code. The error message is complaining about this line in libopeniscsiusr/sysfs.c: > [ 44s] sysfs.c: In function '_iscsi_host_id_of_session': > [ 44s] sysfs.c:326:48: error: '/iscsi_host/' directive output may be truncated writing 12 bytes into a region of size between 1 and 4096 [-Werror=format-truncation=] > [ 44s] snprintf(sys_scsi_host_dir_path, PATH_MAX, "%s/iscsi_host/", > [ 44s] ^~~~~~~~~~~~ > [ 44s] In file included from /usr/include/stdio.h:862, > [ 44s] from sysfs.c:22: > [ 44s] /usr/include/bits/stdio2.h:64:10: note: '__builtin___snprintf_chk' output between 13 and 4108 bytes into a destination of size 4096 > [ 44s] return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, > [ 44s] ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > [ 44s] __bos (__s), __fmt, __va_arg_pack ()); > [ 44s] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ But that code has been changed is now looks like: > strncpy(sys_scsi_host_dir_path, sys_dev_path, PATH_MAX); > strncat(sys_scsi_host_dir_path, iscsi_host_dir_str, > PATH_MAX - iscsi_host_dir_strlen); So you need to trigger a rebuild? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087796] New: Fully updated Tumbleweed image on Raspberry Pi2 halts regularly
by bugzilla_noreply＠novell.com 02 Apr '18

02 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1087796 Bug ID: 1087796 Summary: Fully updated Tumbleweed image on Raspberry Pi2 halts regularly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I started a Tumbleweed image from ARM-JeOS-raspberrypi2.armv7l-2018.01.20-Build1.1 and regularly updated it using "zypper dup --no-recommnds" to the latest version. A bluetooth dongle is present in the system. During its lifetime it halts regularly, after days without a problem. Power off and on again restores a working system for a few days. Most of the time there is nothing in the journal to indicate the cause of halting the system. Messages do not appear anymore in the journal. A few days back I found the following: mrt 30 17:12:44 smahp kernel: Unable to handle kernel paging request at virtual address 00cfad70 mrt 30 17:12:44 smahp kernel: pgd = c2082d00 mrt 30 17:12:44 smahp kernel: [00cfad70] *pgd=2e689003, *pmd=00000000 mrt 30 17:12:44 smahp kernel: Internal error: Oops: a06 [#1] PREEMPT SMP ARM mrt 30 17:12:44 smahp kernel: Modules linked in: rfcomm cmac nf_log_ipv6 xt_comment nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_rec mrt 30 17:12:44 smahp kernel: CPU: 0 PID: 1481 Comm: SBFspotUploadDa Not tainted 4.14.14-1-lpae #1 mrt 30 17:12:44 smahp kernel: Hardware name: BCM2835 mrt 30 17:12:44 smahp kernel: task: c2b2f7c0 task.stack: c2be8000 mrt 30 17:12:44 smahp kernel: PC is at memcpy+0x50/0x330 mrt 30 17:12:44 smahp kernel: LR is at 0x0 mrt 30 17:12:44 smahp kernel: pc : [<c0ceb750>] lr : [<00000000>] psr: 200f0013 mrt 30 17:12:44 smahp kernel: sp : c2be9d74 ip : 00000000 fp : c2be9dbc mrt 30 17:12:44 smahp kernel: r10: dac0a000 r9 : dac0a000 r8 : 00000052 mrt 30 17:12:44 smahp kernel: r7 : 40a9e95f r6 : 7e30303a r5 : 35333a38 r4 : 30203332 mrt 30 17:12:44 smahp kernel: r3 : 2d35302d r2 : 000001f0 r1 : dac0ad80 r0 : 00cfad70 mrt 30 17:12:44 smahp kernel: Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user mrt 30 17:12:44 smahp kernel: Control: 30c5387d Table: 02082d00 DAC: fffffffd mrt 30 17:12:44 smahp kernel: Process SBFspotUploadDa (pid: 1481, stack limit = 0xc2be8210) mrt 30 17:12:44 smahp kernel: Stack: (0xc2be9d74 to 0xc2bea000) mrt 30 17:12:44 smahp kernel: 9d60: 00000001 00000ff0 00000010 mrt 30 17:12:44 smahp kernel: 9d80: ffffe000 00cfa010 00cfa010 c083a254 c22317d0 ef865f00 00001000 00001000 mrt 30 17:12:44 smahp kernel: 9da0: c2be9ef0 efbdc168 c2be9ee8 00000000 c2be9dcc c2be9dc0 c083a44c c083a17c mrt 30 17:12:44 smahp kernel: 9dc0: c2be9ddc c2be9dd0 c083fa90 c083a438 c2be9e1c c2be9de0 c0842f7c c083fa64 mrt 30 17:12:44 smahp kernel: 9de0: ef0de900 c109d43c dac0a000 00cfa010 c04eca08 dcd08d44 c23099c0 efbdc168 mrt 30 17:12:44 smahp kernel: 9e00: 00000e06 c2be9f08 00001000 dcd08c50 c2be9e8c c2be9e20 c05c57d0 c0842d6c mrt 30 17:12:45 smahp kernel: 9e20: c15158c8 00000000 c2be9e44 014000c0 00080001 00000000 00000e05 00000000 mrt 30 17:12:45 smahp kernel: 9e40: 00000e07 c2309a28 c2be9ef0 00000000 ffffe000 00000000 01bf3fff 00000000 mrt 30 17:12:45 smahp kernel: 9e60: c2be9e8c c2be9f08 00001000 c2be9f78 00cfa010 c2be9f78 00000000 c2be9ef0 mrt 30 17:12:45 smahp kernel: 9e80: c2be9ecc c2be9e90 c05c6c08 c05c55d4 c23099c0 00000000 00001000 00028002 mrt 30 17:12:45 smahp kernel: 9ea0: 00000000 00000000 c23099c0 c2be9f78 00cfa010 c2be9f78 00000000 00000000 mrt 30 17:12:45 smahp kernel: 9ec0: c2be9edc c2be9ed0 c06f352c c05c6ae8 c2be9f44 c2be9ee0 c0652a6c c06f34f4 mrt 30 17:12:45 smahp kernel: 9ee0: 00001000 c069bbf4 00cfa010 00001000 00000000 00000000 00001000 c2be9ee8 mrt 30 17:12:45 smahp kernel: 9f00: 00000001 c2be9f10 c23099c0 00000000 00e06000 00000000 00000000 00000000 mrt 30 17:12:45 smahp kernel: 9f20: 00000000 00000000 ffffe000 00001000 c23099c0 00cfa010 c2be9f74 c2be9f48 mrt 30 17:12:45 smahp kernel: 9f40: c0652b54 c0652994 00000008 c06741d8 c23099c0 c23099c0 00e06000 00000000 mrt 30 17:12:45 smahp kernel: 9f60: 00cfa010 00001000 c2be9fa4 c2be9f78 c06530fc c0652ac4 00e06000 00000000 mrt 30 17:12:45 smahp kernel: 9f80: 00001000 00cfa010 00000007 00000003 c0436ac8 c2be8000 00000000 c2be9fa8 mrt 30 17:12:45 smahp kernel: 9fa0: c04368c0 c06530bc 00001000 00cfa010 00000007 00cfa010 00001000 00000000 mrt 30 17:12:46 smahp kernel: 9fc0: 00001000 00cfa010 00000007 00000003 00000000 00cfa010 00000000 b6edf6f0 mrt 30 17:12:46 smahp kernel: 9fe0: 00000000 bed6edb8 00000000 b6b3b9f0 800f0010 00000007 00000000 00000000 mrt 30 17:12:46 smahp kernel: [<c0ceb750>] (memcpy) from [<c083a254>] (__copy_to_user_memcpy+0xe4/0x18c) mrt 30 17:12:46 smahp kernel: [<c083a254>] (__copy_to_user_memcpy) from [<c083a44c>] (arm_copy_to_user+0x20/0x34) mrt 30 17:12:46 smahp kernel: [<c083a44c>] (arm_copy_to_user) from [<c083fa90>] (copyout+0x38/0x48) mrt 30 17:12:46 smahp kernel: [<c083fa90>] (copyout) from [<c0842f7c>] (copy_page_to_iter+0x21c/0x498) mrt 30 17:12:46 smahp kernel: [<c0842f7c>] (copy_page_to_iter) from [<c05c57d0>] (generic_file_buffered_read+0x208/0x8b0) mrt 30 17:12:46 smahp kernel: [<c05c57d0>] (generic_file_buffered_read) from [<c05c6c08>] (generic_file_read_iter+0x12c/0x180) mrt 30 17:12:46 smahp kernel: [<c05c6c08>] (generic_file_read_iter) from [<c06f352c>] (ext4_file_read_iter+0x44/0x58) mrt 30 17:12:46 smahp kernel: [<c06f352c>] (ext4_file_read_iter) from [<c0652a6c>] (__vfs_read+0xe4/0x130) mrt 30 17:12:46 smahp kernel: [<c0652a6c>] (__vfs_read) from [<c0652b54>] (vfs_read+0x9c/0x164) mrt 30 17:12:46 smahp kernel: [<c0652b54>] (vfs_read) from [<c06530fc>] (SyS_read+0x4c/0xa4) mrt 30 17:12:46 smahp kernel: [<c06530fc>] (SyS_read) from [<c04368c0>] (ret_fast_syscall+0x0/0x4c) mrt 30 17:12:46 smahp kernel: Code: f5d1f05c f5d1f07c e8b151f8 e2522020 (e8a051f8) I have another Raspberry Pi2 system starting with the same image and also regularly updated with "zypper dup --no-recommends", which never did halt. Only this one does not have a bluetooth dongle. -- You are receiving this mail because: You are on the CC list for the bug.

1 0