openSUSE Bugs September 2013

bugs@lists.opensuse.org

1 participants
4505 discussions

[Bug 510767] New: mkinitrd -b boot_dir doesn't work
by bugzilla_noreply＠novell.com 03 Sep '13

03 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=510767 Summary: mkinitrd -b boot_dir doesn't work Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: lukas(a)aiken.cz QAContact: jsrain(a)novell.com Found By: --- User-Agent: Opera/9.64 (Windows NT 6.0; U; cs) Presto/2.1.1 mkinitrd ignores the boot directory passed via -b boot_dir. It always uses /boot instead. Reproducible: Always Steps to Reproduce: 1. Create a directory (eg. /home/abcd/boot). 2. Copy the content of /boot into this directory (eg. cp -r /boot /home/abcd/boot). 3. Invoke mkinitrd with the "-b" parameter (eg. mkinitrd -b /home/abcd/boot) Actual Results: The appropriate initrd file is created inside /boot, not in the specified directory (eg. /home/abcd/boot). The same applies for the kernel image which is used from /boot. Expected Results: The image is created inside the specified directory (eg. /home/abcd/boot). -- 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 835978] New: During installation I try to disable the NTP service but it stays always enabled.
by bugzilla_noreply＠novell.com 03 Sep '13

03 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=835978 https://bugzilla.novell.com/show_bug.cgi?id=835978#c0 Summary: During installation I try to disable the NTP service but it stays always enabled. Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: comes(a)naic.edu QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 During the installation the NTP service is always enabled even if, in the Change Date and Time screen, I select Manually or deselect Run NTP as a Daemon This bug is present since 12.2 Reproducible: Always Steps to Reproduce: 1.Install and try to disable the NTP daemon 3. Actual Results: NTP service is always enabled even if told not to Expected Results: It should be possible to disable the NTP service during the installation process -- 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 712537] New: Calling mkinitrd when LVM snapshots exist gives error message about missing dm-snapshot-origin module
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=712537 https://bugzilla.novell.com/show_bug.cgi?id=712537#c0 Summary: Calling mkinitrd when LVM snapshots exist gives error message about missing dm-snapshot-origin module Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pieter(a)hollants.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=446063) --> (http://bugzilla.novell.com/attachment.cgi?id=446063) Patch to make mkinitrd not try to load dm-snapshot-origin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 If a LVM snapshot volume has been created for some LV, calling mkinitrd yields error messages that dependencies for "dm-snapshot-origin" can't be found. This stems from setup-dm.sh examining "dmsetup table" output to figure out which dm modules need to be included into the initrd. Example output: sysvg-rootlv-real: 0 4194304 linear 9:1 419430784 sysvg-rootlv_postinstall-cow: 0 2097152 linear 9:1 423625088 sysvg-rootlv_postinstall: 0 4194304 snapshot 253:5 253:7 P 8 sysvg-rootlv: 0 4194304 snapshot-origin 253:5 Here it is correct to assume "snapshot" is a dm target, however "snapshot-origin" is not (belongs to "snapshot" as well) and thus a special exception to avoid the error message. Attached trivial patch fixes this. Please apply. Reproducible: Always Steps to Reproduce: 1. Make sure /root is on LVM or otherwise make sure mkinitrd takes care of including LVM 2. lvcreate a snapshot volume of an arbitrary LV 3. Call mkinitrd Actual Results: Error messages about "dm-snapshot-origin" module that could not be found. Expected Results: No error message. -- 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 834990] New: osc's httplib module throws IncompleteRead error when doing a local build.
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=834990 https://bugzilla.novell.com/show_bug.cgi?id=834990#c0 Summary: osc's httplib module throws IncompleteRead error when doing a local build. Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.4 Platform: 64bit OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: osc AssignedTo: adrian(a)suse.com ReportedBy: musicsuse(a)gmx.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- Created an attachment (id=552739) --> (http://bugzilla.novell.com/attachment.cgi?id=552739) the output of "strace -o osc.out -f -s 300 osc build --disable-cpio-bulk-download" after "tail -1000 osc.out > osc0140-log.log" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 When starting a local build linked to an oBS instance outside build.opensuse.org, osc starts normal, however it soon dies with an error: "(openSUSE.org:openSUSE:Factory) gtk2-devel-2.24.20-1.2.x86_64.rpm 2.2 MB 00:02 IncompleteRead(0 bytes read, 4096 more expected)" Reproducible: Always Steps to Reproduce: 1. run osc co package for an account linked to an oBS instance outside build.opensuse.org (packman in my case) 2. Modify the package's spec file 3. osc build Actual Results: (openSUSE.org:openSUSE:Factory) gtk2-devel-2.24.20-1.2.x86_64.rpm 2.2 MB 00:02 IncompleteRead(0 bytes read, 4096 more expected) Expected Results: osc downloads the requirements (basic core components) and the build begins -- 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 838039] New: zypper does not present a good reason if RPM installation fails
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=838039 https://bugzilla.novell.com/show_bug.cgi?id=838039#c0 Summary: zypper does not present a good reason if RPM installation fails Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ptesarik(a)suse.com QAContact: qa-bugs(a)suse.de Found By: L3 Blocker: --- Additional output of a failed "rpm" process is not presented to the user (at least) when running "zypper in". Instead, it says: "Installation aborted by user": hananiah:~ # zypper in ImageMagick Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: ImageMagick 1 new package to install. Overall download size: 4.0 MiB. After the operation, additional 8.3 MiB will be used. Continue? [y/n/?] (y): (1/1) Installing: ImageMagick-6.8.6.7-1.3 ...........................................................................................<100%>[/] Problem occured during or after installation or removal of packages: Installation aborted by user Please see the above error message for a hint. The true reason is that "rpm -i" fails: hananiah:~ # rpm -i /var/cache/zypp/packages/repo-oss/suse/x86_64/ImageMagick-6.8.6.7-1.3.x86_64.rpm error: unpacking of archive failed on file /usr/share/doc/packages/ImageMagick/www/api/MagickCore/exception_8h.html;52247155: cpio: link error: ImageMagick-6.8.6.7-1.3.x86_64: install failed This is a regression from a previous version, which said: Installation of ImageMagick-6.8.6.7-1.2 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/share/doc/packages/ImageMagick/www/api/MagickCore/exception_8h.html;521386cc: cpio: link error: ImageMagick-6.8.6.7-1.2.x86_64: install failed Although still not ideal, the previous behaviour was much easier to debug. See bnc 835695 if you wonder why installation fails in the first place. Additional Info: hananiah:~ # rpm -q zypper libzypp zypper-1.9.1-1.1.x86_64 libzypp-13.5.0-1.1.x86_64 -- 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 836657] New: kiwi: allow custom size for recovery partition
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=836657 https://bugzilla.novell.com/show_bug.cgi?id=836657#c0 Summary: kiwi: allow custom size for recovery partition Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: ms(a)suse.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- sometimes people want to add additional information to the recovery partition thus it might make sense to allow: <oem-recovery-partition-size>...</oem-recovery-partition-size> -- 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 836569] New: CPU-related drivers stop being auto-loaded
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=836569 https://bugzilla.novell.com/show_bug.cgi?id=836569#c0 Summary: CPU-related drivers stop being auto-loaded Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: jdelvare(a)suse.com QAContact: qa-bugs(a)suse.de CC: rmilasan(a)suse.com Found By: Community User Blocker: --- A change in kernel 3.11 causes udev to no longer load CPU-related drivers such as coretemp. This has been discussed here: http://lists.lm-sensors.org/pipermail/lm-sensors/2013-August/039812.html The fix is already available upstream: http://cgit.freedesktop.org/systemd/systemd/commit?id=bf7f800f2b3e93ccd1229… As the fix is not intrusive, I would like to have it included in an upcoming maintenance update of udev on openSUSE 12.3 and possibly 12.2 as well. This will avoid regressions when users test more recent kernels. -- 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 836995] New: virtuoso package
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=836995 https://bugzilla.novell.com/show_bug.cgi?id=836995#c0 Summary: virtuoso package Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: faure(a)kde.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.97 Safari/534.34 please add --with-readline to the configure options for the virtuoso-server RPM. This makes "key up" work in the isql-vt command-line tool. Tested locally, by compiling https://github.com/openlink/virtuoso-opensource.git myself. Reproducible: Always Steps to Reproduce: 1. isql-vt 2. key up 3. Actual Results: ^[[A Expected Results: showing the last command again -- 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 818871] New: os-prober not working in a EFI System
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=818871 https://bugzilla.novell.com/show_bug.cgi?id=818871#c0 Summary: os-prober not working in a EFI System Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gjn(a)gjn.priv.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=538278) --> (http://bugzilla.novell.com/attachment.cgi?id=538278) The debug log from os-prober User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 On my Systems os-prober is not working in a efi System. os-prober don't found the installed openSUSE 12.3 and also not found the Windows system. I have installed the debug Packages and attachment the debug log 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 47

[Bug 835691] New: mkinitrd fails during installation with Perl-Bootloader error message
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=835691 https://bugzilla.novell.com/show_bug.cgi?id=835691#c0 Summary: mkinitrd fails during installation with Perl-Bootloader error message Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: snwint(a)suse.com ReportedBy: rsalevsky(a)suse.com QAContact: jsrain(a)suse.com CC: trenn(a)suse.com, mchang(a)suse.com Found By: Development Blocker: --- The mkinitrd fails during the installation with the flowing error messages (partly shortened): An error occurred during initrd creation. Kernel image: /boot/vmlinuz-3.11.0-rc5-1.gadcd98b-default Initrd image: /boot/initrd-3.11.0-rc5-1.gadcd98b-default KMS drivers: radeon Root device: /dev/disk/by-id/ata-MM0500GBKAK_9XF23BV9-part4 (/dev/sda4) (mounted on / as ext4) Kernel Modules: thermal_sys thermal processor... Firmware: ... Features: acpi kms plymouth block usb resume.userspace resume.kernel Perl-Bootloader: 2013-08-20 16:47:24 <3> pbl-7754.2 Core::GRUB2::GrubDev2UnixDev.127: Error: did not find a match for hd0 in the device map Perl-Bootloader: 2013-08-20 16:47:24 <3> pbl-7754.2 Core::GRUB2::GrubDev2UnixDev.127: Error: did not find a match for hd0 in the device map Perl-Bootloader: 2013-08-20 16:47:24 <3> pbl-7754.2 Core::GRUB2::GrubDev2UnixDev.127: Error: did not find a match for hd0 in the device map Perl-Bootloader: 2013-08-20 16:47:29 <3> pbl-7754.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "(hd0,0)" >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: error: disk `hd0,0' not found. There was an error generating the initrd (1) mchang provided me with a dud for perl-bootloader that I have testet on several machines without any problems. (by trenn): Be aware that not all, but quite some machines fail and it would be great to have a fix in factory asap, so that we can continue with factory installations. -- 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

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs September 2013