February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 861624] New: Installation gets stuck when using AutoYaST and ipv6only flag
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=861624 https://bugzilla.novell.com/show_bug.cgi?id=861624#c0 Summary: Installation gets stuck when using AutoYaST and ipv6only flag Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: fehr(a)suse.com ReportedBy: bmaloney(a)vtti.vt.edu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=576764) --> (http://bugzilla.novell.com/attachment.cgi?id=576764) y2log from attempted install User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.102 Safari/537.36 When installing with autoyast and the ipv6only=1 flag passed to linuxrc, the installation stops at "Retrieve & Read Control File". The last line in y2log is: 2014-01-31 18:06:02 <1> 2001:468:c80:a202:21c:23ff:fe82:6329(2686) [Ruby] modules/ProfileLocation.rb:281 Creating default Rules When it stop there, y2base is running at 100% CPU forever. This worked fine in OpenSUSE 12.3. Reproducible: Always Steps to Reproduce: 1. Attempt to install OpenSUSE 13.1 with AutoYaST and ipv6only=1 specified 2. 3. Actual Results: Installation gets stuck at "Retrieve & Read Control File" Expected Results: Installation completion -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 862440] New: Updates are applied automatically every day even though apper is configured to look for updates weekly
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862440 https://bugzilla.novell.com/show_bug.cgi?id=862440#c0 Summary: Updates are applied automatically every day even though apper is configured to look for updates weekly Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: junkerade(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Updates are applied automatically every day even though apper is configured to look for updates weekly. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 811452] New: Installation not finishing - Xorg does not quit
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=811452 https://bugzilla.novell.com/show_bug.cgi?id=811452#c0 Summary: Installation not finishing - Xorg does not quit Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joschibrauchle(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22 On a series of autoinstallations of openSUSE 12.3, there have been some occurrences of the installation not finishing. It looks like YaST reaches the very last step of "YaST2.call" and simply needs to kill Xorg, but Xorg does not die. Hence, the installation keeps waiting for X to die and never finishes. This is 'ps auxf' of such a machine: ---------- root 597 0.0 0.0 13396 1956 tty1 Ss+ 17:38 0:00 /bin/sh /usr/lib/YaST2/startup/YaST2.Second-Stage root 3645 0.0 0.0 13528 2004 tty1 S+ 17:39 0:00 \_ /bin/sh /usr/lib/YaST2/startup/YaST2.call installation continue root 4292 0.2 0.3 129888 14768 tty7 Ss+ 17:39 0:01 \_ Xorg -noreset -br -deferglyphs 16 vt07 root 10857 0.0 0.0 5764 568 tty1 S+ 17:52 0:00 \_ sleep 1 ---------- This is the tail of y2log: ---------- 2013-03-25 17:42:23 <1> lab05(4390) [liby2] genericfrontend.cc(main):784 Finished YaST2 component 'y2base' 2013-03-25 17:42:23 <1> lab05(4390) [liby2] genericfrontend.cc(main):789 Exiting with client return value '`next' ...stripped some lines... 2013-03-25 17:42:23 <1> lab05(4390) [Y2Perl] YPerl.cc(destroy):164 Shutting down embedded Perl interpreter. ---------- As you can see, Yast is basically done since 17:42, but is still waiting for Xorg to shut down... The relevant code for sleeping is at the very end of /usr/lib/YaST2/startup/YaST2.call ---------- ... #============================================= # 9) Clean sweep #--------------------------------------------- # 9.1) clear Qt environment... clr_inst_qt_env # 9.2) kill X-Server... if [ "$server_running" = 1 ];then sleep 1 && kill $xserver_pid while kill -0 $xserver_pid 2>/dev/null ; do sleep 1 done fi ... ---------- So I manually tried to do a "kill 4292", where 4292 is the PID of Xorg, but nothing happens... it does not die! Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Start (auto-)installation of 12.3 and wait for it to finish... Actual Results: Installation never finishes as Xorg does not react to kill -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 862583] New: No login if UID its greater than 7354396 and loginmanager is KDM.
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862583 https://bugzilla.novell.com/show_bug.cgi?id=862583#c0 Summary: No login if UID its greater than 7354396 and loginmanager is KDM. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: michael(a)geheimtinte.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.73.11 (KHTML, like Gecko) Version/7.0.1 Safari/537.73.11 If UID is greater than 7354396 no User can login if the displaymanager its set to kdm. Login via gdm, ssh or a terminal (strg-alt-f1) ist no problem. Doesn't matter if the user is a local one or comes from ldap. /var/log/messages: ---- 2014-02-05T14:47:30.041820+01:00 xyz119 kdm: :0[12579]: pam_unix(xdm:session): session opened for user tester by (uid=0) 2014-02-05T14:47:30.046893+01:00 xyz119 systemd[1]: Starting Session 46 of user tester. 2014-02-05T14:47:30.047931+01:00 xyz119 systemd-logind[672]: New session 46 of user tester. 2014-02-05T14:47:30.048942+01:00 zyx119 systemd-logind[672]: Linked /tmp/.X11-unix/X0 to /run/user/7354397/X11-display. 2014-02-05T14:47:30.049968+01:00 xyz119 systemd[1]: Started Session 46 of user tester. 2014-02-05T14:47:30.082342+01:00 xyz119 kdm: :0 '[12604]: Startup script returned non-zero exit code 2014-02-05T14:47:30.136462+01:00 xyz119 kdm: :0[12579]: pam_unix(xdm:session): session closed for user tester 2014-02-05T14:47:30.147574+01:00 xyz119 systemd-logind[672]: Removed session 46. ---- Reproducible: Always Steps to Reproduce: 1. set Displaymanager to kdm (standard if you choose KDE as default) 2. create user with uid > 7354396 3. Actual Results: after trying to login kdm appaers again. Expected Results: login user -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 862286] New: update of lvm2 create a dependency on lvmetad but this one is not present in initrd
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862286 https://bugzilla.novell.com/show_bug.cgi?id=862286#c0 Summary: update of lvm2 create a dependency on lvmetad but this one is not present in initrd Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bruno(a)ioda-net.ch QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 On system with / fully encrypted with lvm+luks lvmetad is missing in initrd. At boot the system found luks offer the password and could (or not) open the / partition. But with a second hdd encrypted, systemd fail to open the other partition. I've enough chance to get (after waiting the timeout of systemd activation) the rescue prompt at level one. forcing a vgscan -ay create the missing part after saying that lvmetad not found and reverting to default scan. Reproducible: Always Steps to Reproduce: 0. Have a full encrypted system with password on one disk, setup a second harddrive to be encrypted but use a keyfile on first harddrive, setup a number of lvm mountpoint (/ /srv /media/blah ) 1. Install last lvm2 update from oss update channel 2. Try to reboot 3. Actual Results: A mess is created due to the change of /etc/lvm.conf (which is replaced whithout checking if it has been changed by local root!!!) = missing %config_file in spec Expected Results: Able to install update without going to rescue mode. content of initrd lsinitrd initrd | grep lvm var/lock/lvm usr/lib/udev/rules.d/11-dm-lvm.rules config/lvm2.sh etc/lvm etc/lvm/lvm.conf sbin/lvm boot/61-lvm2.sh see missing lvmetad ( and certainly calls to start it ) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 860690] New: Prepare and release update for GTK 3.6.5
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860690 https://bugzilla.novell.com/show_bug.cgi?id=860690#c0 Summary: Prepare and release update for GTK 3.6.5 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: zaitor(a)opensuse.org ReportedBy: dimstar(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE 12.3 ws shipped with GTK 3.6.5 (with an addon repo allowing to update to 3.8, but that's out of scope here). GNOME Upstream released an update for the 3.6 GTK version. The Changes are: (all Bug references being bgo#) * Bug fixes: 669808 fullscreen/unscreen was broken for Quartz on OS X 672271 File chooser seems over-enthusiastic about using sub... 687066 gtk 3.6.1 fails to build for win32 688534 gdk 3.6.2 does not build with mesa 9.0.1 691426 get_current_desktop does not interpret property data... 691515 Insufficient checks for EWMH support 691572 Touch: strengthen synthesized touch crossing events... 694742 Fix possible memory leak when GlobalAlloc() fails 694755 When clicking Activities, sometimes gnome-shell cras... 695278 Avoid passing a NULL title to setTitle 695312 Initial 'text' set in the non-numeric-only GtkSpinBu... 696171 GtkAssistant highlighted font unreadable 696202 Add GtkSpinner animation back to Win32 theme win32: add more width to the slider to not cut it wh... win32: add margin to scale trough win32: set color for scale marks win32: scale slider with marks was off by 2 pixels win32: handle again gtk-font-name of which those are considered worthy for an update: 672271 File chooser seems over-enthusiastic about using sub... 691572 Touch: strengthen synthesized touch crossing events... 694742 Fix possible memory leak when GlobalAlloc() fails 694755 When clicking Activities, sometimes gnome-shell cras... 695278 Avoid passing a NULL title to setTitle The others are build related, Win32 related or rather cosmetic -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 860900] New: Maintenance updates for armadillo in openSUSE 13.1 and 12.3
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860900 https://bugzilla.novell.com/show_bug.cgi?id=860900#c0 Summary: Maintenance updates for armadillo in openSUSE 13.1 and 12.3 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: badshah400(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Upstream developers of armadillo strongly recommend updating the versions of armadillo package in 12.3 and 13.1 to the latest version in the 3.x series (3.930.4) as it involves significantly important bug fixes and is completely backward compatible with the versions presently available with 12.3 (version 3.6.1) and 13.1 (3.910.1). Please let me know if this would be acceptable, in which case I will make the necessary submissions. Thank you Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 860340] New: Reconsider Backward compatibility in openSUSE:Systemd packaging guidelines
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860340 https://bugzilla.novell.com/show_bug.cgi?id=860340#c0 Summary: Reconsider Backward compatibility in openSUSE:Systemd packaging guidelines Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other URL: http://en.opensuse.org/openSUSE:Systemd_packaging_guid elines#Backward_compatibility OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Documentation AssignedTo: fs(a)suse.com ReportedBy: mt(a)suse.com QAContact: adrian(a)suse.com CC: lnussel(a)suse.com, stefan.fent(a)suse.com, werner(a)suse.com, systemd-maintainers(a)suse.de Found By: --- Blocker: --- I've no idea if this bug is assigned correctly... PM? The systemd packaging guidelines enforce ("you have to") a rc<servicename> -> $sbin/service compatibility link causing bug reports which force packagres to create such links or implement a very specific wrapper to provide the possibility to handle a service via (IMO) the SUSE specific "rc<servicename>", On the one side there are feature requests enforcing that service have to provide native systemd support or features requiring it, on the other side "it has to work as before". Please rethink this requirement. There are many different services. Some service have switched to per instance start of services using native systemd mechanisms instead of handling all instances in one service and a target which handles all instances (e.g. bug#848070), .. or have been reworked otherwise. Please review all the /etc/rc.status, /sbin/service (can't handle targets grouping multiple instance services) and all other hooks redirecting to systemctl, decide which mechanisms are required, define and document applicable rules and cleanup all the rest. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 838185] New: MODULES_LOADED_ON_BOOT removed
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=838185 https://bugzilla.novell.com/show_bug.cgi?id=838185#c0 Summary: MODULES_LOADED_ON_BOOT removed Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ohering(a)suse.com QAContact: jsrain(a)suse.com Found By: Outsourced Testing Blocker: --- In bnc#768423 it was requested to migrate /etc/sysconfig/kernel:MODULES_LOADED_ON_BOOT to /etc/modules-load.d/ This is change is now in Factory. Today I searched for other users of MODULES_LOADED_ON_BOOT and found several in the yast sources. systemd still processes /etc/sysconfig/kernel:MODULES_LOADED_ON_BOOT, but I think thats a SuSE specific change. Please pass this bug around to update the remaining cases. linuxrc-4.1.5/net.c:2429: fprintf(fpk, "MODULES_LOADED_ON_BOOT=\"$MODULES_LOADED_ON_BOOT netiucv\"\n"); yast2-bootloader-3.0.3/src/modules/Bootloader.rb:333 yast2-installation-3.0.4/src/clients/kernel_finish.rb:156 yast2-sound-3.0.1/src/include/sound/write_routines.rb:136 yast2-storage-3.0.2/src/modules/Storage.rb:5968 yast2-3.0.5/library/system/src/modules/Kernel.rb:584 yast2-3.0.5/library/system/testsuite/tests/kernel.out:5 There are probably more, my grep through all Factory sources is not yet done. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 859342] NFS file locking issue
by bugzilla_noreply＠novell.com 06 Feb '14

06 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=859342 https://bugzilla.novell.com/show_bug.cgi?id=859342#c5 --- Comment #5 from Neil Brown <nfbrown(a)suse.com> 2014-02-06 05:41:35 UTC --- Thanks for the report. I agree with analysis and fix. Patch has been sent upstream and commited to openSUSE 13.1, SLES12, SLES11-SP3 I'll leave bug open until upstream confirms. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0