July 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1095096] Leap 42.3: update broke boot with encrypted partitions on NVMe
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1095096 http://bugzilla.suse.com/show_bug.cgi?id=1095096#c49 --- Comment #49 from Franck Bui <fbui(a)suse.com> --- (In reply to Dariusz Ostolski from comment #48) > Hi, > > I used mockup algo #3 and here are results: Thanks Dariusz. > > ls -alh /dev/disk/by-id > total 0 [...] > lrwxrwxrwx 1 root root 13 Jul 3 17:04 nvme-200080d03000c85f8 -> > ../../nvme0n1 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part1 -> > ../../nvme0n1p1 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part2 -> > ../../nvme0n1p2 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part3 -> > ../../nvme0n1p3 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part4 -> > ../../nvme0n1p4 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part5 -> > ../../nvme0n1p5 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part6 -> > ../../nvme0n1p6 > lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part7 -> > ../../nvme0n1p7 So it looks like the old symlinks are back. However I would recommend to use the ones shipped by upstream at that point. For example, you can choose "nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU" and use it in /etc/crypttab. Thank you a lot for helping us debug this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1058509] grub segfault in ncurses
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1058509 http://bugzilla.opensuse.org/show_bug.cgi?id=1058509#c37 Felix Miata <mrmazda(a)earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mrmazda@earthlink | |.net) | --- Comment #37 from Felix Miata <mrmazda(a)earthlink.net> --- On host hpg33, lp150.2.2 from 2018-04 on 15.0 OSS doesn't segfault, but it lacks command history. Thus 0.97-210.3 from 42.3 2017-06 with working command history is preferable. In TW I still have all installations locked on 0.97.203.7 from 2016-10. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1093378] conflicting udev rules completely break USB Serial bridges
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1093378 http://bugzilla.suse.com/show_bug.cgi?id=1093378#c25 --- Comment #25 from Stanislav Brabec <sbrabec(a)suse.com> --- I created a project https://hackweek.suse.com/17/projects/user-assisted-udev-rules -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1096401] New: snapper: segfault found in openQA tests
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1096401 Bug ID: 1096401 Summary: snapper: segfault found in openQA tests Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While checking some logs on openQA, trying to find why so many tests are failing, I stumbled over a segfault of snapper: Jun 07 02:18:14 susetest org.opensuse.Snapper[719]: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >' Jun 07 02:18:14 susetest org.opensuse.Snapper[719]: what(): boost: mutex lock failed in pthread_mutex_lock: Invalid argument Jun 07 02:18:14 susetest systemd[1]: Started Process Core Dump (PID 20684/UID 0). Jun 07 02:18:15 susetest systemd-coredump[20685]: Process 18707 (snapperd) of user 0 dumped core. TIME PID UID GID SIG COREFILE EXE Thu 2018-06-07 02:09:35 EDT 2722 0 0 6 present /bin/login Thu 2018-06-07 02:14:34 EDT 14648 0 0 6 present /usr/sbin/snapperd Thu 2018-06-07 02:15:58 EDT 16462 0 0 6 present /usr/sbin/snapperd Thu 2018-06-07 02:18:15 EDT 18707 0 0 6 present /usr/sbin/snapperd This can explain why openQA has a hard time passing the tests, as the system is pre-occupied writing coredumps The three snaperd coredumps are available in the openQA provided tarball https://openqa.opensuse.org/tests/688332/file/gimp-problem_detection_logs.t… (directory coredumps) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1099987] Update prosody to 0.10.2 and 0.9.14
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.novell.com/show_bug.cgi?id=1099987 Tomáš Chvátal <tchvatal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |mvetter(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1100004] dmenu 4.5 missing dmenu_path
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.novell.com/show_bug.cgi?id=1100004 Tomáš Chvátal <tchvatal(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |sleep_walker(a)opensuse.org |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099755] netcfg: /etc/hosts.allow and /etc/hosts.deny deprecated?
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1099755 http://bugzilla.suse.com/show_bug.cgi?id=1099755#c7 --- Comment #7 from Tomáš Chvátal <tchvatal(a)suse.com> --- (In reply to Matthias Gerstner from comment #6) > (In reply to tchvatal(a)suse.com from comment #5) > > Hmm, overall maybe we could just give up on hosts.* as this should be > > handled by firewall anyway? > > One could argue this way. However, I fear there are still a number of users > (customers) around that use this and will complain. Also I think it would > require a FATE to get completely rid of it? Well yes and no, opensuse has no fate system anymore, if we here agree to drop it and cc relevant parties thats it. For older releases of course fate/eco is needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1100004] dmenu 4.5 missing dmenu_path
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1100004 http://bugzilla.suse.com/show_bug.cgi?id=1100004#c1 --- Comment #1 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1100004) was mentioned in https://build.opensuse.org/request/show/620487 42.3 / dmenu.Leap -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099755] netcfg: /etc/hosts.allow and /etc/hosts.deny deprecated?
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1099755 http://bugzilla.suse.com/show_bug.cgi?id=1099755#c6 --- Comment #6 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- (In reply to tchvatal(a)suse.com from comment #5) > Hmm, overall maybe we could just give up on hosts.* as this should be > handled by firewall anyway? One could argue this way. However, I fear there are still a number of users (customers) around that use this and will complain. Also I think it would require a FATE to get completely rid of it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095096] Leap 42.3: update broke boot with encrypted partitions on NVMe
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=1095096 http://bugzilla.suse.com/show_bug.cgi?id=1095096#c48 Dariusz Ostolski <dariusz.ostolski(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dariusz.ostolski@ | |gmail.com) | --- Comment #48 from Dariusz Ostolski <dariusz.ostolski(a)gmail.com> --- Hi, I used mockup algo #3 and here are results: ls -alh /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 13 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part5 -> ../../nvme0n1p5 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 15 Jul 3 17:04 -THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part7 -> ../../nvme0n1p7 drwxr-xr-x 2 root root 1020 Jul 3 17:04 . drwxr-xr-x 8 root root 160 Jul 3 17:03 .. lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-name-cr_nvme-200080d03000c85f8-part7 -> ../../dm-0 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-name-system-home -> ../../dm-3 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-name-system-root -> ../../dm-1 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-name-system-swap -> ../../dm-2 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-uuid-CRYPT-LUKS1-45c782c30f044c10855a09f94cc81d42-cr_nvme-200080d03000c85f8-part7 -> ../../dm-0 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-uuid-LVM-xK1naeJ70xbO0e0X3BaC8y7R2yi1oxV73Ofb6d5K9VtdGOh2k4q9fVodhFndSNVp -> ../../dm-1 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-uuid-LVM-xK1naeJ70xbO0e0X3BaC8y7R2yi1oxV73Wh8EQVdds22xrOiGqGpEvj2P0cEyO9x -> ../../dm-2 lrwxrwxrwx 1 root root 10 Jul 3 17:04 dm-uuid-LVM-xK1naeJ70xbO0e0X3BaC8y7R2yi1oxV7LBg2KaKmC8RtCFFKBm1KilFcpxL3lv3D -> ../../dm-3 lrwxrwxrwx 1 root root 10 Jul 3 17:04 lvm-pv-uuid-tS06RV-2T2C-rJhc-aXCP-F1RW-vZC3-o7Pcp0 -> ../../dm-0 lrwxrwxrwx 1 root root 13 Jul 3 17:04 nvme-200080d03000c85f8 -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part5 -> ../../nvme0n1p5 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-200080d03000c85f8-part7 -> ../../nvme0n1p7 lrwxrwxrwx 1 root root 13 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part5 -> ../../nvme0n1p5 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-SNVMe_THNSN5512GPUK_NV17BB502BKSHU-part7 -> ../../nvme0n1p7 lrwxrwxrwx 1 root root 13 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part5 -> ../../nvme0n1p5 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_17BB502BKSHU-part7 -> ../../nvme0n1p7 lrwxrwxrwx 1 root root 13 Jul 3 17:04 nvme-eui.00080d03000c85f8 -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part5 -> ../../nvme0n1p5 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 15 Jul 3 17:04 nvme-eui.00080d03000c85f8-part7 -> ../../nvme0n1p7 md5sum /etc/udev/rules.d/61-persistent-storage-compat.rules 6d0aa38d985da6d64b6f5622183d34e3 /etc/udev/rules.d/61-persistent-storage-compat.rules BR, Dariusz -- You are receiving this mail because: You are on the CC list for the bug.

1 0