September 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 895353] New: kiwi: bug with building virtualbox/libvirt vagrant boxes from single package
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=895353 https://bugzilla.novell.com/show_bug.cgi?id=895353#c0 Summary: kiwi: bug with building virtualbox/libvirt vagrant boxes from single package Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: aspiers(a)suse.com QAContact: adrian(a)suse.com CC: tboerger(a)suse.com Found By: Development Blocker: --- [ Discovered by tboerger via https://build.suse.de/package/live_build_log/home:tboerger:vagrant:boxes/mi… ] If I set up a package in OBS with a .kiwi definition containing: <preferences> <type image="vmx" filesystem="ext3" boot="vmxboot/suse-SLES11" format="vagrant" bootloader="grub" kernelcmdline="nomodeset"> <vagrantconfig provider="virtualbox" virtualsize="50"/> <vagrantconfig provider="libvirt" virtualsize="50"/> [...] then after building the virtualbox box, it will fail with an error like this: [ 281s] Sep-05 13:08:18 <1> : EXEC [cd /usr/src/packages/KIWI-vmx/vmx && rm -f box.ovf box-disk1.vmdk sles-11sp3-minimal.x86_64-0.0.1.vmdk metadata.json Vagrantfile] [ 281s] Sep-05 13:08:18 <1> : Creating vagrant box for libvirt provider [ 281s] Sep-05 13:08:18 <1> : Creating qcow2 image...Sep-05 13:08:18 <1> : EXEC [/usr/bin/qemu-img convert -c -f raw /usr/src/packages/KIWI-vmx/vmx/sles-11sp3-minimal.x86_64-0.0.1.vmdk -O qcow2 /usr/src/packages/KIWI-vmx/vmx/sles-11sp3-minimal.x86_64-0.0.1.vmdk 2>&1] [ 281s] Sep-05 13:08:18 <3> : Couldn't create qcow2 image: qemu-img: Could not open '/usr/src/packages/KIWI-vmx/vmx/sles-11sp3-minimal.x86_64-0.0.1.vmdk': No such file or directory It seems to be attempting to create a qcow2 from a .vmdk which was already deleted?! Sounds like maybe a case of a variable being reused incorrectly in between box builds. Reversing the order of the <vagrantconfig> elements in the XML works around this issue (and then reveals other bugs, but that's another story). -- 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 895573] New: KDE:Extra/julius: Bug
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=895573 https://bugzilla.novell.com/show_bug.cgi?id=895573#c0 Summary: KDE:Extra/julius: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: kde-maintainers(a)suse.de ReportedBy: christ.juergen(a)t-online.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- mkfa not installed due to missing ${DESTDIR}. See the build log for details. Without mkfa, simon using the julius backend is unusable. -- 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 894370] VUL-0: MozillaFirefox 32/31.1 security release
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894370 https://bugzilla.novell.com/show_bug.cgi?id=894370#c12 --- Comment #12 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2014-09-08 13:01:00 CEST --- This is an autogenerated message for OBS integration: This bug (894370) was mentioned in https://build.opensuse.org/request/show/248005 Evergreen:11.4 / thunderbird24 -- 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 893650] New: [Factory 20140820] NetworkManager not working
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=893650 https://bugzilla.novell.com/show_bug.cgi?id=893650#c0 Summary: [Factory 20140820] NetworkManager not working Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: i686 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sb56637(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Hi there, on both the current 20140820 Factory snapshot and the previous one, both for Gnome and KDE, NetworkManager isn't working, at least not for WiFI and when testing the live system on a USB drive. My WiFI card is successfully detected and powered on, but I had to manually start the NetworkManager service. Even then, the Gnome and KDE interfaces to NetworkManager can't seem to communicate with NetworkManager or establish a connection. Reproducible: Always -- 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 439283] Should gcc warning "'return' with no value, in function returning non-void" result in a general build failure?
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=439283 https://bugzilla.novell.com/show_bug.cgi?id=439283#c8 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #8 from Stefan Dirsch <sndirsch(a)suse.com> 2014-09-08 09:17:23 UTC --- Meanwhile WONTFIX sounds appropriate for me here. -- 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 872758] New: help.opensuse.org links to outdated documentation
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=872758 https://bugzilla.novell.com/show_bug.cgi?id=872758#c0 Summary: help.opensuse.org links to outdated documentation Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: fs(a)suse.com ReportedBy: sknorr(a)novell.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:28.0) Gecko/20100101 Firefox/28.0 The Documentation view of help.opensuse.org is badly in need of an update: * The following sentence is completely wrong: "Novell also provides official documentation for the openSUSE distribution, previews are often published on docs.opensuse.org." + Novell is now irrelevant there + since the openSUSE documentation is now a community effort, the documentation should probably not be called official + docs.opensuse.org now links to activedoc.opensuse.org Proposal: "Find openSUSE manuals at activedoc.opensuse.org." * The page looks disorganised, the two most prominent links (SDB & HCL) are probably not the most important ones for new users. The site should give some prominence to the ActiveDoc link and the wiki link too. General criticism of the page: * The start view is not very helpful, and the menu at the side would be mostly unnecessary if the page showed all categories at once by default * The page is a bit wordy in general * Loading this small page my browser makes 57 requests, of which 18 (!) for different CSS files, 2 for JS files, and then lots for little PNGs (some of which for rounded corners etc. which now work with CSS in almost any browser) Reproducible: Always -- 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 3

[Bug 894370] VUL-0: MozillaFirefox 32/31.1 security release
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=894370 https://bugzilla.novell.com/show_bug.cgi?id=894370#c Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Alias| |CVE-2014-1562 -- 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 895342] New: creation of encrypted home directory fails in YaST
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=895342 https://bugzilla.novell.com/show_bug.cgi?id=895342#c0 Summary: creation of encrypted home directory fails in YaST Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: carlos.lange(a)ualberta.ca QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 When creating a new user immediately after installation in YaST and checking "Use Encrypted Home Directory" (any size), an error message box "stat: No such file or directory. Failed to open image" pops-up. The user is correctly created and both image and key files are created in /home, but the encrypted image is not used and the user logs into a regular unencrypted home directory. The same problem was described in the forum: https://forums.opensuse.org/showthread.php/492386-cannot-get-encrypted-home… Reproducible: Always Steps to Reproduce: 1. 2. 3. As mentioned in the forum, the problem can be worked around by loading the module loop with "modprobe loop" before creating the user. Unlike the discussion in the forum, however, there is no need to add loop.conf to /etc/modules-load.d/. Without loop.conf the creation of new encrypted homes works correctly even after reboot. -- 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 832737] New: zypper [in,dup,rm,se] segmentation fault
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=832737 https://bugzilla.novell.com/show_bug.cgi?id=832737#c0 Summary: zypper [in,dup,rm,se] segmentation fault Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: i686 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- With repos changed manually to factory-snapshot, I did zypper -v dup on a multiboot Athlon 13.1M2 system running kernel-desktop-3.10.0-rc4 but with kernel-desktop locked. The dup completed without any apparent errors. Afterward I did zypper rl kernel-desktop; zypper -v dup. That resulted in a segfault. I tried again without -v, then tried zypper -v in kernel-desktop, and repeated without -v, then zypper rm zypper-aptitude, then zypper se -s zypp. All segfaulted. I used rpm to upgrade to the Factory zypp Head packages, but it helped none for zypper se -s zypp and zypper -v dup. dmesg tail: zypper[1290]: segfault at 2 ip b75dc49a sp bff35ef0 error 4 in libzypp.so.1302.1.0[b7253000+470000] zypper[1294]: segfault at 2 ip b75ef49a sp bf81fb70 error 4 in libzypp.so.1302.1.0[b7266000+470000] zypper[1298]: segfault at 2 ip b762549a sp bfbc54b0 error 4 in libzypp.so.1302.1.0[b729c000+470000] zypper[1302]: segfault at 2 ip b76c449a sp bfac09c0 error 4 in libzypp.so.1302.1.0[b733b000+470000] zypper[1450]: segfault at 2 ip b76ae49a sp bfca9490 error 4 in libzypp.so.1302.1.0[b7325000+470000] zypper[1476]: segfault at 2 ip b760749a sp bfa036a0 error 4 in libzypp.so.1302.1.0[b727e000+470000] zypper[1503]: segfault at fff1063d ip b76788ca sp bf9f8ef0 error 5 in libzypp.so.1304.0.0[b72ee000+472000] libzypp-13.3.0-1.2.i586 rpm-4.10.3.1-8.3.i586 rpm-python-4.10.3.1-8.2.i586 zypper-1.9.0-2.3.i586 zypper-aptitude-1.9.0-2.3.noarch zypper-log-1.9.0-2.3.noarch Linux kt880 3.10.0-rc4-1-desktop #1 SMP PREEMPT Wed Jun 5 15:55:02 UTC 2013 (fc06ef7) i686 athlon i386 GNU/Linux vendor_id : AuthenticAMD cpu family : 6 model : 8 model name : AMD Athlon(tm) XP 2400+ stepping : 1 cpu MHz : 2000.098 cpuid level : 1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow clflush size : 32 cache_alignment : 32 address sizes : 34 bits physical, 32 bits virtual power management: ts -- 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 56

[Bug 890800] New: yast2-live-installer: Shouldn't probably start in stage2
by bugzilla_noreply＠novell.com 08 Sep '14

08 Sep '14

https://bugzilla.novell.com/show_bug.cgi?id=890800 https://bugzilla.novell.com/show_bug.cgi?id=890800#c0 Summary: yast2-live-installer: Shouldn't probably start in stage2 Classification: openSUSE Product: openSUSE Factory Version: 201408* Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: cyberorg(a)opensuse.org QAContact: jsrain(a)suse.com CC: mengz.you(a)gmail.com Depends on: 872903 Found By: --- Blocker: --- Created an attachment (id=601472) --> (http://bugzilla.novell.com/attachment.cgi?id=601472) stage2 error +++ This bug was initially created as a clone of Bug #872903 +++ Installing Factory live CD using yast2 live-installer starts yast again after reboot, not sure it is needed any more. It gives error as shown in attached image, selecting Quit starts the system normally. At the end of installation, the following should be run in installed system. systemctl disable YaST2-Second-Stage.service -- 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 3