October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 997637] LVM volume disabled after installation
by bugzilla_noreply＠novell.com 08 Oct '16

08 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=997637 http://bugzilla.suse.com/show_bug.cgi?id=997637#c31 --- Comment #31 from Liuhua Wang <lwang(a)suse.com> --- (In reply to Neil Rickert from comment #26) > I realized the mistake on that "pvscan" check. The major:minor of 8:21 > refers to the encrypted container. I should, instead, have used 254:0. > That's what gives more interesting output on my 42.1 system (which does not > use lvmetad). > > So I tried that, but still got about the same output as before. > > Hmm, shouldn't the scan be done by "lvmetad" rather than by "systemd"? > Maybe that "systemctl" command is checking something that doesn't matter. LVM needs to cooperate with other components such as iscsi, md, multipath, encrypt,etc., which depends on udev events and systemd service starting sequence. Taking LVM on top of multipath as an example: multipath set the disk READY for LVM, then LVM use lvmetad to scan on top of mutipath partitons and use multipath partitons as its physical volumes. If multipath is not READY when LVM is scanning disks then it will fail to activate them. > On the udev rules: I'm seeing what Ludwig mentioned. That is, there is no > mention of "SYSTEMD_WANTS" in that file. There is a rule: > RUN+="/sbin/lvm pvscan --background --cache --activate ay --major $major > --minor $minor", ENV{LVM_SCANNED}="1" Yes, there is where NON-ROOT partitions are activated. In case of use_lvmetad = 1 (by default), udev: 69-dm-lvm-metad.rules will scan disks and update lvmetad through "pvscan --cache $major $minor" and instantiated systemd service "lvm2-pvscan@$major:$minor.service" (which will run `pvscan --cache --ay $major:$minor` to activate LVM partitions.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 997637] LVM volume disabled after installation
by bugzilla_noreply＠novell.com 08 Oct '16

08 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=997637 http://bugzilla.suse.com/show_bug.cgi?id=997637#c30 --- Comment #30 from Liuhua Wang <lwang(a)suse.com> --- (In reply to Ludwig Nussel from comment #25) > There we go. That's the problem. lvm2 doesn't buildrequire systemd. So those > lines are completely missing in Leap. Try adding BuildRequires: > pkgconfig(systemd) like it's done in the Factory package. I am confused, why there is no problem with SLE12-sp2 but there is problem with Leap since they have the same spec(both have no BuildRequres: pkgconfig(systemd))? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 998755] New: [Leap 42.2 Beta1] Network ip addr. settings changed to static after upgrade from openSUSE 13.2
by bugzilla_noreply＠novell.com 08 Oct '16

08 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=998755 Bug ID: 998755 Summary: [Leap 42.2 Beta1] Network ip addr. settings changed to static after upgrade from openSUSE 13.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: yast2-maintainers(a)suse.de Reporter: whdu(a)suse.com QA Contact: jsrain(a)suse.com CC: bchou(a)suse.com, chcao(a)suse.com, dhkong(a)suse.com, jiawei.sun(a)suse.com, qingming.su(a)suse.com, wjiang(a)suse.com, ysun(a)suse.com Found By: --- Blocker: --- Environment Details: >From openSUSE 13.2 x86_64 (updated to the latest maintenance update), offline upgrade (with DVD image) to Leap 42.1 Beta1 (in VM). Results: After upgrading, boot to the new system, the network connection failed. Check "YaST > System > Network Settings", it was changed to "Static" rather than keep the old settings (DHCP). Maybe some scripts made the incorrect changes to the configuration when upgrading. Extra Info.: 1.y2log attached 2.updatetestcase attached -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1002699] xfs_fsr segfault
by bugzilla_noreply＠novell.com 08 Oct '16

08 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1002699 http://bugzilla.suse.com/show_bug.cgi?id=1002699#c5 --- Comment #5 from Luis Rodriguez <lurodriguez(a)suse.com> --- Also, can you try the latest kernel of the day [0] and let me know if after installing it you still see the issue? [0] https://en.opensuse.org/openSUSE:Kernel_of_the_day -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002699] xfs_fsr segfault
by bugzilla_noreply＠novell.com 08 Oct '16

08 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1002699 http://bugzilla.suse.com/show_bug.cgi?id=1002699#c4 Luis Rodriguez <lurodriguez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal(a)suse.com Flags| |needinfo?(mpluskal(a)suse.com | |) --- Comment #4 from Luis Rodriguez <lurodriguez(a)suse.com> --- (In reply to Martin Pluskal from comment #0) > Created attachment 695535 [details] > full bt > > when running xfs_fsr on xfs root, it segfaults: Thanks for the report, I can see an issue when running: xfs_fsr after a fresh install on a KVM instance with OpenSUSE 42.2 with XFS used on / but its not a segfault. Can you describe what type of work load you've put into the system prior to running xfs_fsr ? The issue I see with xfs_fsr should be addressed but is different than what you are describing. What I see is running xfs_fsr first runs in a loop and I see this in dmesg: XFS (sda2): xfs_swap_extents: inode 0x84eb1 format is incompatible for exchanging. XFS (sda2): xfs_swap_extents: inode 0x84eb1 format is incompatible for exchanging. XFS (sda2): xfs_swap_extents: inode 0x84eb1 format is incompatible for exchanging. After hitting CTRL-C, and re-running xfs_fsr, it completes but running xfs_fsr once again makes it run in an endless loop. This repeats. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1002517] New: nm-applet: wifi: wrong symbol when connected
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1002517 Bug ID: 1002517 Summary: nm-applet: wifi: wrong symbol when connected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: patrik.mueller91(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 695398 --> http://bugzilla.opensuse.org/attachment.cgi?id=695398&action=edit wrong symbol while connected to wifi The bug was came with one of the updates in the past week, I think. See attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1001314] New: Odd NetworkManager behavior after update
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=1001314 Bug ID: 1001314 Summary: Odd NetworkManager behavior after update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pilotgi(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I did an update to Tumbleweed 9-24-16 that was over 130 packages, including NetworkManager. After the update I could not connect to the internet. Ifconfig was showing I had an ip address for both wired and wireless connections but still no luck connecting outside my router. A search on openSUSE forums showed others having the same problem, and able to fix it by editing /etc/resolv.conf or deleting that file and rebooting. Eventually the latter solution worked for me. My internet is working but NetworkManager looks to be having problems. My NM icon in the panel is grayed out with a orange question mark next to it. If I click on it, it shows my wireless adapter is connected, which it is, but if I click on the software manager, it says I'm off line. I can update software via YaST or zypper with no problems, although there was a problem with YaST showing some packages were installed (mostly kernel) that weren't. I fixed that using the rpm --rebuilddb command. Conclusion: NetworkManager is having some problems after a recent update. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 990257] KDE wallpaper wrong aspect ratio
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=990257 http://bugzilla.suse.com/show_bug.cgi?id=990257#c13 --- Comment #13 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (990257) was mentioned in https://build.opensuse.org/request/show/433796 Factory / plasma5-workspace https://build.opensuse.org/request/show/433797 42.2 / plasma5-workspace -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003399] Desktop layout and wallpaper changes don't stick
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1003399 http://bugzilla.suse.com/show_bug.cgi?id=1003399#c9 --- Comment #9 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1003399) was mentioned in https://build.opensuse.org/request/show/433797 42.2 / plasma5-workspace -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1001364] New: sddm: empty avatar images
by bugzilla_noreply＠novell.com 07 Oct '16

07 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=1001364 Bug ID: 1001364 Summary: sddm: empty avatar images Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build 203 shows empty avatar images in sddm: https://openqa.opensuse.org/tests/271906#step/multi_users_dm/11 -- You are receiving this mail because: You are on the CC list for the bug.

1 3