November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 725062] New: zypper ignores download.max_download_speed property
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725062 https://bugzilla.novell.com/show_bug.cgi?id=725062#c0 Summary: zypper ignores download.max_download_speed property Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: pavel(a)argo-tours.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 It downloads packages on the full maximum available speed instead of limiting speed to the proper /etc/zypp/zypp.conf parameter Reproducible: Always Steps to Reproduce: 1. Add the parameter download.max_download_speed to the file /etc/zypp/zypp.conf. Set it to 100000 (assuming you have internet connection faster then 100 KBytes/s) 2. Start some update (I've used zypper -n update -l) Actual Results: I see in my KDE network monitor, that download is being processed at the full (in my case 200-300 KBytes/s) speed. Expected Results: Download should proceed with the limited (100 KBytes/s) speed -- 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 725872] New: zypper: reduce duplicated messages
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=725872 https://bugzilla.novell.com/show_bug.cgi?id=725872#c0 Summary: zypper: reduce duplicated messages Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Printing the "No package matching 'xxx*'" multiple times is redundant, it would suffice if it did this once, or completely omit it, since there is not going to be a package called "lib*". # zypper up --no-r 'lib*' 'bundle*' Loading repository data... Reading installed packages... No package matching 'bundle*' are installed. [message repeated 69 more times...] No package matching 'lib*' are installed. [message repeated 409 more times...] [...] Resolving package dependencies... [...] -- 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 668593] New: windows:mingw:win32/mingw32-pdcurses: Bug
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=668593 https://bugzilla.novell.com/show_bug.cgi?id=668593#c0 Summary: windows:mingw:win32/mingw32-pdcurses: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Windows Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: fstrba(a)novell.com ReportedBy: roger(a)opq.se QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: tlillqvist(a)novell.com, fridrich.strba(a)bluewin.ch, abharath(a)novell.com Found By: Community User Blocker: No PD Curses, like it's ncurses counterpart, supports wide characters and UTF-8. However, these versions of the library are not contained in the build. It would be really useful if they were also built. -- 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 637215] New: Yast will not start from Gnome System menu
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=637215 https://bugzilla.novell.com/show_bug.cgi?id=637215#c0 Summary: Yast will not start from Gnome System menu Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: support(a)microtechniques.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=387641) --> (http://bugzilla.novell.com/attachment.cgi?id=387641) console messages User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729) Although Yast is listed on the Gnome System menu, it will not start when selected. It will start when called as yast2 from a text-mode command line. There are several errors in the logs which are attached. Reproducible: Always Steps to Reproduce: 1.startx 2.Select Computer 3.Select YaST from System menu Actual Results: Absolutely nothing Expected Results: Yast system startup -- 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 25

[Bug 541674] New: mkinitrd: include-all-libata-drivers not always working
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=541674 Summary: mkinitrd: include-all-libata-drivers not always working Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: All 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 CC: hare(a)novell.com Found By: Beta-Customer This is about commit 87d86855cf54ff125ab6e059ddc4a66987e1b533 in mkinitrd. First of all I noticed that the commit message mentions "This default is improper as it increases the bootup time for machines that have multiple controllers". However, the code (still) causes all libata modules to be pulled in. So if I have multiple ATA controllers, it would be increasing the bootup time. Second, in recent versions of the kernel, CONFIG_ATA may have been changed from =m to =y[1], so that the test for "-L /sys/module/libata/holders/$procname" in setup-block.sh does not fire anymore, because holders will not be tracked when a piece of code is =y. [1] http://lists.opensuse.org/opensuse-kernel/2009-09/msg00001.html -- 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 4

[Bug 679092] New: kernel-desktop debuginfo missing - unable to debug kernel crash
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=679092 https://bugzilla.novell.com/show_bug.cgi?id=679092#c0 Summary: kernel-desktop debuginfo missing - unable to debug kernel crash Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b12) Gecko/20110222 Firefox/4.0b12 My openSUSE 11.4 install (kernel-desktop) oopses (almost) every time I unplug my USB audio headset. I made a kernel crash, but 'crash' claims that the debuginfo can't be found: worklaptop:/var/crash # crash 2011-03-11-19\:29/System.map-2.6.37.1-1.2-desktop 2011-03-11-19\:29/vmlinux-2.6.37.1-1.2-desktop 2011-03-11-19\:29/vmcore .. crash: 2011-03-11-19:29/vmlinux-2.6.37.1-1.2-desktop: no debugging data available worklaptop:/var/crash # rpm -qa | grep kernel-desktop kernel-desktop-2.6.37.1-1.2.2.x86_64 kernel-desktop-devel-2.6.37.1-1.2.2.x86_64 kernel-desktop-devel-debuginfo-2.6.37.1-1.2.2.x86_64 kernel-desktop-debuginfo-2.6.37.1-1.2.2.x86_64 kernel-desktop-base-2.6.37.1-1.2.2.x86_64 kernel-desktop-base-debuginfo-2.6.37.1-1.2.2.x86_64 worklaptop:/var/crash # What's more, boot.kdump is *not* in /etc/init.d/boot.d and trying to enable it results in this: worklaptop:/var/crash # chkconfig --add boot.kdump insserv: FATAL: service network is missed in the runlevels 4 to use service SuSEfirewall2_setup insserv: exiting now! /sbin/insserv failed, exit code 1 boot.kdump 0:off 1:off 2:off 3:off 4:off 5:off 6:off worklaptop:/var/crash # finally, 'openSUSE 11.4' is missing from the Operating System dropdown in bugzilla. 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 14

[Bug 732904] New: Cannot boot: "bind failed: Address already in use" and "error binding udev control socket"
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=732904 https://bugzilla.novell.com/show_bug.cgi?id=732904#c0 Summary: Cannot boot: "bind failed: Address already in use" and "error binding udev control socket" Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cymerio(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=464198) --> (http://bugzilla.novell.com/attachment.cgi?id=464198) dmesg output User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Sometimes when booting the system it stops at the recovery console prompt. When inspecting the last errors you see 4 or 5 messages like this: bind failed: Address already in use error binding udev control socket The workaround is to log in with the root password and write "exit" afterwards. The system continues booting normally. Reproducible: Sometimes Steps to Reproduce: 1. Boot the system normally (with systemd) Actual Results: The booting process is taking longer than usual. Then the nice splash logo is gone and you are in text mode and the system is asking you the root password to log in the recovery console. Expected Results: The system should boot without issues, like it normally does. Maybe related to bug #728315 ? But this one doesn't happen always, only sometimes. -- 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 19

[Bug 656536] New: booting on some sw-RAID setups does not assemble root device in initrd
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=656536 https://bugzilla.novell.com/show_bug.cgi?id=656536#c0 Summary: booting on some sw-RAID setups does not assemble root device in initrd Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: bwiedemann(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- my automated testing scripts for openSUSE can setup and boot software RAID which works for LiveCD installs such as http://www3.zq1.de/opensuse/video/openSUSE-KDE-LiveCD-x86_64-Build0681-RAID… and http://openqa.opensuse.org/opensuse/video/openSUSE-KDE-LiveCD-x86_64-Build0… but failed for 11.3-DVD and current Factory DVD/NET installs in http://openqa.opensuse.org/opensuse/video/openSUSE-DVD-x86_64-Build0909-RAI… at 01:11 you can see the intended RAID setup with / being /dev/md0 with /dev/vd[abcd]2 as underlying block-devices but at 02:14 you can see that in initrd only a /dev/md0 is assembled from /dev/vd[abcd]3 which then can not be used to boot the system, because it is the swap. -- 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 15

[Bug 702360] New: some symbols are only in kernel-*base
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=702360 https://bugzilla.novell.com/show_bug.cgi?id=702360#c0 Summary: some symbols are only in kernel-*base Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: mmarek(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- I blocked -base and -devel from LiveCDs, normally kernel-default should be enough, but some symbols are not provided by it. preload-kmp-default-1.2_k2.6.39.0_2-11.7.i586 requires ksym(default:yield) = 760a0f4f, but this requirement cannot be provided >!> uninstallable providers: kernel-default-base-2.6.39-2.3.i586[tmp] kernel-default-devel-2.6.39-2.3.i586[tmp] -- 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 732881] New: XFS module not built into initrd at install
by bugzilla_noreply＠novell.com 30 Sep '13

30 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=732881 https://bugzilla.novell.com/show_bug.cgi?id=732881#c0 Summary: XFS module not built into initrd at install Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: suse-20050616(a)bgcomp.co.uk QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; en-GB) Presto/2.9.168 Version/11.52 I upgraded from 11.4 to 12.1. All file systems are running as mirrored XFS. When initrd is recreated during upgrade, XFS is not added to the kernel module list meaning that when the system is rebooted it is unable to mount any disks including root. Provided there is an old kernel to boot from, adding xfs to INITRD_MODULES list in the file /etc/sysconfig/kernel and then rebuild the default kernel will correct the problem. Reproducible: Always Steps to Reproduce: 1. Upgrade 2. Reboot Expected Results: Boot into system -- 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