July 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 709103] New: let libxslt provide xsltproc
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=709103 https://bugzilla.novell.com/show_bug.cgi?id=709103#c0 Summary: let libxslt provide xsltproc Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 The binary package libxslt provides an executable xsltproc that is extensively used by documentation tools that do not link against the library itself. Accordingly, libxslt should provide xsltproc so that to build packages that request it. Reproducible: Always Steps to Reproduce: 1. Build package xmlto. Actual Results: 1. W: explicit-lib-dependency libxslt Expected Results: 1. xmlto should require xsltproc because this is what it uses. The update is ready in project devel:libraries:c_c++; I filed this bug report so as to get a notification when it is 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 5

[Bug 708326] New: /bin/on_ac_power does not exist anymore
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=708326 https://bugzilla.novell.com/show_bug.cgi?id=708326#c0 Summary: /bin/on_ac_power does not exist anymore Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: dmueller(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Kernel image: /boot/vmlinuz-3.0.0-2-desktop Initrd image: /boot/initrd-3.0.0-2-desktop do_ypcall: clnt_call: RPC: Timed out KMS drivers: nouveau Root device: /dev/disk/by-id/scsi-SATA_ST3750330AS_9QK00WQA-part1 (/dev/sda1) (mounted on / as ext4) Kernel Modules: thermal_sys processor thermal pata_marvell fan edd button video wmi mxm-wmi i2c-algo-bit drm drm_kms_helper ttm nouveau cp: cannot stat `/bin/on_ac_power': No such file or directory Features: kms block usb Bootsplash: openSUSE (1680x1050) ldd: /bin/on_ac_power: No such file or directory 44429 blocks Kernel image: /boot/vmlinuz-3.0.0-rc7-2-default Initrd image: /boot/initrd-3.0.0-rc7-2-default KMS drivers: nouveau Root device: /dev/disk/by-id/scsi-SATA_ST3750330AS_9QK00WQA-part1 (/dev/sda1) (mounted on / as ext4) Kernel Modules: thermal_sys processor thermal pata_marvell fan edd button video wmi mxm-wmi i2c-algo-bit drm drm_kms_helper ttm nouveau usbcore pcmcia_core pcmcia mmc_core ssb ohci-hcd ehci-hcd uhci-hcd usbhid cp: cannot stat `/bin/on_ac_power': No such file or directory Features: kms block usb -- 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 640352] New: virtualbox-ose-guest-kmp-default-3.2.8_k2.6.34.7_0.2-105.2 fail to load
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=640352 https://bugzilla.novell.com/show_bug.cgi?id=640352#c0 Summary: virtualbox-ose-guest-kmp-default-3.2.8_k2.6.34.7_0.2-1 05.2 fail to load Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: saubert(a)majesty.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 After yesterday's kernel and virtualbox extensions update, I realize that all my virtual machines fail to load the virtualbox extensions on boot (Virtualbox 3.2.8). Reproducible: Always Steps to Reproduce: 1. Install Virtualbox 3.2.8 on a Windows host operating system. 2. Install OpenSUSE 11.3 as a guest. 3. install kernel-default-2.6.34.7-0.2.2.i586 update 4. reboot 5. install virtualbox-ose-guest-kmp-default-3.2.8_k2.6.34.7_0.2-105.2.i586 update from Virtualization repository. 6. reboot 7. check boot screen and /var/log/boot.msg Actual Results: virtualbox extensions fail to load with the following message in boot.msg: Failed services in runlevel 3: vboxadd Expected Results: load virtualbox extensions, just as done always before this update. -- 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 533800] New: mkinitrd: fails to understand fstab's LABEL= names
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

http://bugzilla.novell.com/show_bug.cgi?id=533800 Summary: mkinitrd: fails to understand fstab's LABEL= names Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 When /etc/fstab contains a LABEL= specification for the root filesystem, mkinitrd fails. Reproducible: Always Steps to Reproduce: 1. Start 11.1 installer 2. Choose "mount by filesystem label" (and give the filesystems some label) 3. When initial installation is done and the new system itself runs, run mkinitrd. Actual Results: # mkinitrd -k vmlinuz -i itest Kernel image: /boot/vmlinuz Initrd image: /boot/itest Root device: /dev/root (mounted on / as xfs) Device root not found in sysfs Script /lib/mkinitrd/setup/72-block.sh failed! Expected Results: Cope with the situation, or never use LABEL= in the first place (but instead: /dev/disk/by-label/ when the installer creates the fstab entries) Oddly enough, the initial system is installed fine, despite the use of LABEL=. It is only in the final system. Also, there is a workaround possible: using "/dev/disk/by-label/root" instead of "LABEL=root" in fstab, after which things work: # mkinitrd -k vmlinuz -i itest Kernel image: /boot/vmlinuz Initrd image: /boot/itest Root device: /dev/disk/by-label/root (/dev/md1) (mounted on / as xfs) Kernel Modules: scsi_mod libata ahci exportfs xfs md-mod raid1 crc-t10dif sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd hid usbhid raid0 xor async_tx async_memcpy async_xor raid456 Features: block usb md 16091 blocks -- Configure bugmail: http://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 708095] New: apache does not start - unspecified error
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=708095 https://bugzilla.novell.com/show_bug.cgi?id=708095#c0 Summary: apache does not start - unspecified error Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 I´ve tried to start apache2 with yast2->runlevel and get an error message: "unspecified error". It is with /etc/init.d/apache2 I will attach the init.d, the package list and the logs. When you are missing something, please contact me. 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 11

[Bug 681065] New: KMail/message forwarding: Headers of forwarded message are not correct in Finnish translation
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=681065 https://bugzilla.novell.com/show_bug.cgi?id=681065#c0 Summary: KMail/message forwarding: Headers of forwarded message are not correct in Finnish translation Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: matti.kettunen(a)gmail.com QAContact: ke(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; fi-FI; rv:1.9.2.15) Gecko/20110303 SUSE/3.6.15-1.1 Firefox/3.6.15 In the file: /usr/share/locale/fi/LC_MESSAGES/kmail.mo (after converting it to po) Original in English: \n ---------- Forwarded Message ----------\n \n Subject: %1\n Date: %2, %3\n From: %4\n %OADDRESSEESADDR\n \n %5\n ----------------------------------------- Finnish translation: \n ---------- Välitetty viesti ----------\n \n Aihe: %1\n Päiväys: %2\n Lähettäjä: %3\n Vastaanottaja: %4\n \n %5\n ------------------------------------------------------- ************ Finnish translation should be: \n ---------- Välitetty viesti ----------\n \n Aihe: %1\n Päiväys: %2, %3\n Lähettäjä: %4\n %OADDRESSEESADDR\n \n %5\n ------------------------------------------------------- Reproducible: Always Steps to Reproduce: 1. 2. 3. I have OpenSUSE 11.3 with KDE 4.6.1 installed from http://download.opensuse.org/repositories/KDE%3a/Release%3a/46/openSUSE_11.… kde4-l10n-fi package version 4.6.1-157.5 -- 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 2

[Bug 709380] New: libffi's pkg-config file (installed from package libffi45-devel) is missing "description:" field
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=709380 https://bugzilla.novell.com/show_bug.cgi?id=709380#c0 Summary: libffi's pkg-config file (installed from package libffi45-devel) is missing "description:" field Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)damienradtke.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.122 Safari/534.30 After installing the package libffi45-devel from openSUSE:11.4/standard, running "pkg-config --list-all" ends with the error "Package 'libffi' has no Description: field". This causes the action to be terminated prematurely, which means that not all available packages are listed. The fix would be to add a line in /usr/lib/pkgconfig/libffi.pc like the following: Description: Foreign Function Interface library After adding this line, "pkg-config --list-all" successfully lists all available packages. 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 2

[Bug 708680] New: encrypted volume failed with error -4000
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=708680 https://bugzilla.novell.com/show_bug.cgi?id=708680#c0 Summary: encrypted volume failed with error -4000 Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=442682) --> (http://bugzilla.novell.com/attachment.cgi?id=442682) the error popup User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 On openSUSE12.1 build171 64bit, I´ve tried a new installation of a LVM based full encrypted system(default partitioning). The installation fails with error code -4000. I attach a screenshot for the error popup. It was a new installation in KVM, but on a virtual disk where I tried to install a btrfs before, which may be caused this. 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 707692] New: 12.1 MS3 - Selecting separate user and root causes user account not to be created
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=707692 https://bugzilla.novell.com/show_bug.cgi?id=707692#c0 Summary: 12.1 MS3 - Selecting separate user and root causes user account not to be created Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: osl2008(a)googlemail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 Net install from loop-mounted DVD image on second machine via local network. Target hardware is a Pentium-II machine with 512M & NVidia graphics, 80G HD. Apart from selected btrfs in teh partitioner, the only other non-default choice in the installation was the selection of separate user and root accounts. Boot with System-V causes a lock-up, but thanks to bug #707418 selecting systemd gives a run-level 3 prompt. Here only root log-in is accepted, then it is clear that the user account was not created. Also installation phase 2 has not been run. Created user account with YaST, but now booting (either with System-V or systemd) I get bug #707110 (nomodeset required) before I finally complete teh installation. Reproducible: Always Steps to Reproduce: 1. Install with separate user and root accounts 2. 3. Actual Results: Boot fails in at second stage of installation Expected Results: second stage runs as it should what logs are useful here? Machine is finally up so I can retrieve them via network. -- 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 669453] New: osc dies with error regularly
by bugzilla_noreply＠novell.com 01 Aug '11

01 Aug '11

https://bugzilla.novell.com/show_bug.cgi?id=669453 https://bugzilla.novell.com/show_bug.cgi?id=669453#c0 Summary: osc dies with error regularly Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: SLES 11 Status: NEW Severity: Major Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: choeger(a)open-xchange.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 Ubuntu/10.10 (maverick) Firefox/3.6.13 This is on our internal buildservice, versions: obs-api-2.1.2-4.4 obs-common-2.1.0-1.1 obs-service-verify_file-0.1-3.1 obs-service-tar_scm-0.2-6.1 obs-worker-2.1.2-4.4 obs-utils-2.1.2-4.4 obs-server-2.1.2-4.4 obs-signd-2.1.2-1.1 obs-service-set_version-0.1-4.1 We're doing continuous builds and nightly builds and thus, osc permanently dying is a very awkward issue. What's strange is, that his error happened never with obs <2.x, sometimes in the beginning of obs 2.x and now it happens permanently. This is a checkin stacktrace: Traceback (most recent call last): File "/usr/bin/osc", line 21, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.6/site-packages/osc/babysitter.py", line 50, in run return prg.main() File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 309, in main return self.cmd(args) File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 332, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 448, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.6/site-packages/osc/cmdln.py", line 1178, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.6/site-packages/osc/commandline.py", line 2782, in do_checkout prj_dir=project_dir, service_files = opts.source_service_files, server_service_files=opts.server_side_source_service_files, progress_obj=self.download_progress, size_limit=opts.limit_size, meta=opts.meta) File "/usr/lib/python2.6/site-packages/osc/core.py", line 3793, in checkout_package p.update(revision, server_service_files, size_limit) File "/usr/lib/python2.6/site-packages/osc/core.py", line 1873, in update fm = self.get_files_meta(revision=rev) File "/usr/lib/python2.6/site-packages/osc/core.py", line 1358, in get_files_meta root = ET.fromstring(fm) File "<string>", line 86, in XML SyntaxError: no element found: line 1, column 0 This is a rresults stacktrace: Traceback (most recent call last): File "/usr/bin/osc", line 12, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.5/site-packages/osc/babysitter.py", line 40, in run return prg.main() File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 256, in main return self.cmd(args) File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 279, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 395, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.5/site-packages/osc/cmdln.py", line 1070, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.5/site-packages/osc/commandline.py", line 1593, in do_rresults print '\n'.join(get_results(apiurl, prj, pkg)) File "/usr/lib/python2.5/site-packages/osc/core.py", line 2606, in get_results tree = ET.parse(StringIO(''.join(f))) File "<string>", line 45, in parse File "<string>", line 32, in parse SyntaxError: no element found: line 1, column 0 I could add debugging to log the time where this is happening, but a look at some of the logs in /srv/www/obs/api/log shows, that not all of them contain time and date. Also I don't know, where to look. Reproducible: Sometimes 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