June 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 724713] New: Installation of openSUSE 12.1b1 as VirtualBox guest fails after graphical installer when running installed system with kexec
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=724713 https://bugzilla.novell.com/show_bug.cgi?id=724713#c0 Summary: Installation of openSUSE 12.1b1 as VirtualBox guest fails after graphical installer when running installed system with kexec Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Bernd.Strieder(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 Have seen it happen every time I tried. Installing a 12.1b1 guest after installing packages, doing some configuration, during kexec, or shortly before the screen gets garbeled, possibly leftovers from the splash screen from booting mixed with console messages contorted by a mode switch. The it hangs, console switching is no more possible, only resetting helps. The installed system cannot be booted after resetting the VM, which I would not expect. At this point grub should be installed. After installation in text mode, everything went through pretty fine, X11 comes up in the 12.1b1 after booting the first time, then it works. VirtualBox earlier had issues with kexec, so it might still have issues. Or linux has issues after changes affecting virtualbox. Don't know who might have to fix anything. So, there is a problem, there is a workaround, to use text mode installation, and it is unclear who is responsible. If anybody knows a place to forward this bug to, feel free. If there is any further information I could provide, please ask. Reproducible: Always Steps to Reproduce: 1. Use VirtualBox under 11.4 2. Create guest with 12.1b1 DVD x86_64 3. Use graphical installer, e.g. minimal installation Actual Results: When booting into new system vm hangs, only reset helps. Grub is missing in the freshly installed guest, and installation has to be done from the beginning. Expected Results: Running the freshly installed system works. -- 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 26

[Bug 721676] New: openSUSE-12.1 beta1 installation fails with transition lock on /var/lib/rpm/ error
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=721676 https://bugzilla.novell.com/show_bug.cgi?id=721676#c0 Summary: openSUSE-12.1 beta1 installation fails with transition lock on /var/lib/rpm/ error Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lee_matheson(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110920 SUSE/3.6.23-0.2.1 Firefox/3.6.23 32-bit openSUSE-12.1 beta1 (build 0315) DVD fails installation immediately after software installation complete, but before 1st reboot with error: *** Starting YaST *** error: can't create a transition lock on /var/lib/rpm/ .rpm lock (no such file or directory) I obtained the same error on these 4 cases: 1. chose LXDE desktop with no special boot codes 2. chose LXDE desktop with nomodeset boot code 3. chose LXDE desktop with safe settings 4. chose KDE desktop with nomodeset boot code I note I had selected to install / on sdb1 and /home on /sdb5. This partition combination worked on openSUSE-12.1 milestone5. PC is an athlon-1100 w/2GB RAM and a nVidia FX5200 graphic card Reproducible: Always Steps to Reproduce: 1. Attempt to install and problem occurs everytime 2. 3. Actual Results: Above noted failure occurs every time, with PC install halting at "error: can't create a transition lock on /var/lib/rpm/ .rpm lock (no such file or directory)" error. Pressing <enter> does not help. Pressing <ctrl><c> aborts the install, giving ansi menu's to install or reboot. GRUB is already setup, but rebooting results in a hang at the log in menu with no users recognized. Expected Results: Install should complete nominally. I kept failed install on PC. I can likely boot to a liveCD and access the installation logs. Is there any log file that I can provide to help in the debugging ? Note my 'paid' daytime work (which is not related to GNU/Linux) is very busy currently, so my reply's to this bug report may be slow. -- 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 42

[Bug 723777] New: yast/X11 crashes shortly before end of installation
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=723777 https://bugzilla.novell.com/show_bug.cgi?id=723777#c0 Summary: yast/X11 crashes shortly before end of installation Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=456144) --> (http://bugzilla.novell.com/attachment.cgi?id=456144) yast logs after crash this happend twice now (for 2 tries), so it's not just a spurious problem: I'm booting from Beta1 via usb stick and start network installation directly from factory. I've selected XFCE desktop which installs ~2500+ packages. this takes >2h for my slow DSL line. more or less at the end of installation (shortly after I've seen ~2 min left) the Xserver crashes (see Xorg.0.log) and the installation stuck in text mode... this is the end of y2log -- full log attached... 2011-10-13 05:35:28 <1> noname(3444) [zypp:fetcher] Fetcher.cc(provideFromCache):350 start fetcher with 1 cache directories. 2011-10-13 05:35:28 <1> noname(3444) [zypp:fetcher] Fetcher.cc(provideToDest):548 Not found in cache, downloading 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaSetAccess.cc(provide):203 Going to try to provide file /suse/x86_64/xorg-x11-Xvnc-7.6_1.10.4-34.2.x86_64.rpm from media number 1 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaManager.cc(checkDesired):112 checkDesired(5): desired (cached) 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaManager.cc(checkDesired):112 checkDesired(5): desired (cached) 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaMultiCurl.cc(doGetFileCopy):1266 dest: /mnt/var/tmp/AP_0x00000001/suse/x86_64/xorg-x11-Xvnc-7.6_1.10.4-34.2.x86_64.rpm 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaMultiCurl.cc(doGetFileCopy):1267 temp: /mnt/var/tmp/AP_0x00000001/suse/x86_64/xorg-x11-Xvnc-7.6_1.10.4-34.2.x86_64.rpm.new.zypp.gSJUGZ 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaCurl.cc(doGetFileCopyFile):1320 /suse/x86_64/xorg-x11-Xvnc-7.6_1.10.4-34.2.x86_64.rpm 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaCurl.cc(doGetFileCopyFile):1330 URL: http://download.opensuse.org/factory/repo/oss/suse/x86_64/xorg-x11-Xvnc-7.6… 2011-10-13 05:35:28 <2> noname(3444) [qt-ui] YQUI.cc(qMessageHandler):729 <libqt-warning> YaST2: Fatal IO error: client killed 2011-10-13 05:35:28 <3> noname(3444) [qt-ui] YQUI.cc(qMessageHandler):744 Client killed. Possibly caused by X server shutdown or crash. 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/zypp.RJkCec 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.RJkCec{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.xGar88 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.xGar88{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [Pkg] PkgFunctions.cc(~PkgFunctions):147 Releasing the zypp pointer... 2011-10-13 05:35:28 <1> noname(3444) [Pkg] PkgFunctions.cc(~PkgFunctions):149 Zypp pointer released 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.6ulJhL 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.6ulJhL{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.m76rxn 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.m76rxn{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.OQfDVv 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.OQfDVv{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.Cf5P4o 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.Cf5P4o{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.ysL27y 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.ysL27y{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.QZ0Yqc 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.QZ0Yqc{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp] PathInfo.cc(recursive_rmdir):429 recursive_rmdir /var/tmp/TmpDir.oX0l2P 2011-10-13 05:35:28 <1> noname(3444) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/TmpDir.oX0l2P{d 0700 0/0} 2011-10-13 05:35:28 <1> noname(3444) [zypp++] MediaSetAccess.cc(release):431 Releasing all media IDs held by this MediaSetAccess -- 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 44

[Bug 815222] New: LDAP users not shown in "lastlog" command or at KDM login prompt
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=815222 https://bugzilla.novell.com/show_bug.cgi?id=815222#c0 Summary: LDAP users not shown in "lastlog" command or at KDM login prompt Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lnt-sysadmin(a)lists.lrz.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31 In openSUSE12.3, 1) "lastlog" does not show information about LDAP (or non-local) users. The information about these users is available in "/var/log/lastlog" but is not shown (see bnc https://bugzilla.novell.com/show_bug.cgi?id=780764#c7) In openSUSE 11.4, LDAP users used to be shown here. 2) same situation for the KDM login prompt. There is a **empty** gray box when using LDAP users, see screenshot attached. In openSUSE 11.4, LDAP users used to be listed in this box. Reproducible: Always Steps to Reproduce: 1. Login with an LDAP user account (at KDM) Actual Results: User login information not shown by "lastlog" or at KDM login prompt Expected Results: User login information should be shown by "lastlog" and at KDM login prompt, which was the case for openSUSE 11.4 (and possibly later). -- 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 826861] New: [openSUSE goes SLE12]: xfig: Change and/or patches may have been lost
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=826861 https://bugzilla.novell.com/show_bug.cgi?id=826861#c0 Summary: [openSUSE goes SLE12]: xfig: Change and/or patches may have been lost Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All URL: http://w3.suse.de/~max/openSUSE-Hardening/xfig.html OS/Version: SLES 11 Status: NEW Keywords: automation, regression_test_needed Severity: Normal Priority: P5 - None Component: Other AssignedTo: werner(a)suse.com ReportedBy: patch-lost-in-sle(a)suse.de QAContact: qa-bugs(a)suse.de CC: patch-lost-in-sle(a)suse.de Found By: --- Blocker: --- These are the findings of the openSUSE-Hardening Team. We tried to help avoiding regressions when going from SLE 11 code base to SLE 12 based on current openSUSE code base. The scripts only can find a guidance for your work on detecting these regressions, we tried to write these reports to be as helpful as possible, but please consider it's purely automatic. So if we made a mistake (and you know your package better than we do), just set this bug to INVALID - it's part of the process we came up with. The assignee is taken from the maintainer data of https://build.suse.de/search/owner, if these are wrong now is a good time to fix them. But please note that external maintainers do not have access to the SLE 11 patches, so the current openSUSE maintainer can't help. An HTML version of this report can be found at http://w3.suse.de/~max/openSUSE-Hardening/xfig.html When looking at the sources, we found references in SLE 11 that did not appear in openSUSE's sources. It's worth double checking that ignoring them for openSUSE is not causing regressions later: xfig.3.2.5b-libpng14.dif To retrieve SLE code: osc -A https://api.suse.de co SUSE:SLE-11-SP3:GA xfig also it is worth to check the projects SUSE:SLE-11-SP3:Update and SUSE:SLE-11-SP3:Update:Test for available updates of xfig which may or had been happen after this report. To retrieve openSUSE code: DP=$(osc -A https://api.opensuse.org develproject openSUSE:Factory xfig) osc -A https://api.opensuse.org co $DP xfig -- 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 819142] tiff2pdf renders pdf with severely degredaded images
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=819142 https://bugzilla.novell.com/show_bug.cgi?id=819142#c17 --- Comment #17 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2013-06-26 08:00:11 CEST --- This is an autogenerated message for OBS integration: This bug (819142) was mentioned in https://build.opensuse.org/request/show/181002 Factory / tiff -- 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 819142] tiff2pdf renders pdf with severely degredaded images
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=819142 https://bugzilla.novell.com/show_bug.cgi?id=819142#c16 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P4 - Low --- Comment #16 from Petr Gajdos <pgajdos(a)suse.com> 2013-06-26 05:29:30 UTC --- Fixed for factory. We can eventually add this to some upcoming maintenance update -- leaving opened but with P4. -- 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 825503] New: libstorage doesn't handle /dev/loop* absence properly
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825503 https://bugzilla.novell.com/show_bug.cgi?id=825503#c0 Summary: libstorage doesn't handle /dev/loop* absence properly Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: fehr(a)suse.com ReportedBy: fcrozat(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- when creating a loopback based crypted storage point using yast partitionner, creation fails because there is no /dev/loop0 created by default. This is because /dev/loop[0-4] aren't created anymore by default, until "loop" module is loaded (which is not the case by default). /dev/loop-control is always created and will handle "loop" module autoload and /dev/loop? creation (see https://lkml.org/lkml/2011/7/26/148 ). To work "nicely", losetup should be called as : "losetup -f <loopback_file>" instead of "losetup /dev/loop0 <loopback_file>" This issue is present in both 12.3 and Factory -- 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 10

[Bug 823576] New: liferea updated to 1.8.14 fixing many tt-rss issues
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=823576 https://bugzilla.novell.com/show_bug.cgi?id=823576#c0 Summary: liferea updated to 1.8.14 fixing many tt-rss issues Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lijewski.stefan(a)zabka.pl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Liferea was updated to 1.8.14 fixing two tiny tiny rss related issues: -broken rendering in tt-rss feeds (sf#1069) -Updates ttrss feeds over and over (sf#1038,sf#1074) and several others. Those two makes liferea almost unusable with tt-rss. 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 7

[Bug 799660] New: yast2 ldap-server - uninitialized value $initial_skip ... /usr/lib/perl5/vendor_perl/5.16.2/Parse/RecDescent.pm line 3054
by bugzilla_noreply＠novell.com 26 Jun '13

26 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=799660 https://bugzilla.novell.com/show_bug.cgi?id=799660#c0 Summary: yast2 ldap-server - uninitialized value $initial_skip ... /usr/lib/perl5/vendor_perl/5.16.2/Parse/RecDescent.pm line 3054 Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: david.bahi(a)emc.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.9) Gecko/20100101 Firefox/10.0.9 bang:~ # yast2 ldap-server Use of uninitialized value $initial_skip in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.16.2/Parse/RecDescent.pm line 3054 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl will try to tell you the name of the variable (if any) that was undefined. In some cases it cannot do this, so it also tells you what operation you used the undefined value in. Note, however, that perl optimizes your program anid the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. Reproducible: Always Steps to Reproduce: 1. install opensuse 12.3 beta1 2. run 'yast2 ldap-server' 3. see exception in Parse/RecDescent.pm cannot use yast to configure LDAP server without this fixed. -- 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 18