September 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 837031] New: YaST got signal 11 at YCP file on installation start (Segmentation fault)
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=837031 https://bugzilla.novell.com/show_bug.cgi?id=837031#c0 Summary: YaST got signal 11 at YCP file on installation start (Segmentation fault) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rsalevsky(a)suse.com QAContact: jsrain(a)suse.com CC: trenn(a)suse.com Found By: Development Blocker: --- When I start an installation of openSuse Factory, in the first seconds the following error message during installation shows up and the process stops: *** Starting YaST2 *** Out of memory! YaST got signal 11 at YCP file /mounts/mp_0001/usr/share/YaST2/modules/Storage.rb:2343 /usr/lib/YaST2/startup/YaST2.call: line 277: 3793 Segmentation fault $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS ain:~ # Connection to ain closed by remote host. The "Out of Memory" message makes no sense for me because the Machine has 31900 MB RAM. I also realized that the build of openSUSE:Factory yast2-storage fails. I don't know if this is the reason, but it looks wrong :P https://build.opensuse.org/package/show/openSUSE:Factory/yast2-storage -- 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 834854] New: Install kernel parameters are lost in the installed system
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=834854 https://bugzilla.novell.com/show_bug.cgi?id=834854#c0 Summary: Install kernel parameters are lost in the installed system Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 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: rsalevsky(a)suse.com QAContact: jsrain(a)suse.com CC: trenn(a)suse.com Found By: --- Blocker: --- Created an attachment (id=552614) --> (http://bugzilla.novell.com/attachment.cgi?id=552614) Yast2 Logs When I start the installation with some special kernel parameters then these are lost on the installed system. pxe boot parameters: label factory-install-auto-ssh kernel dist/factory/FACTORY/inst-source/boot/x86_64/loader/linux append vga=normal console=tty0 console=ttyS0,57600 install=ftp://10.121.0.100/dist/factory/FACTORY/inst-source autoyast=ftp://10.121.0.100/autoinst/pxe/factory.xml usessh=1 sshpassword=hammer23 kexec_reboot=1 initrd=dist/factory/FACTORY/inst-source/boot/x86_64/loader/initrd sysrq_always_enabled linemode=1 panic=100 ignore_loglevel unknown_nmi_panic insecure=1 dud=ftp://10.121.0.100/dud/perl-Bootloader.dud linuxrc.debug=1 grub2 boot parameters (after installation): menuentry 'openSUSE' --class 'opensuse' --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e1ea4b21-e6af-4f75-a76d-40414b244b9a' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd0,gpt1' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 c5498087-7896-4eb7-bc08-def98aecb281 else search --no-floppy --fs-uuid --set=root c5498087-7896-4eb7-bc08-def98aecb281 fi echo 'Loading Linux 3.10.1-3.g0cd5432-default ...' linux /vmlinuz-3.10.1-3.g0cd5432-default root=UUID=e1ea4b21-e6af-4f75-a76d-40414b244b9a quiet splash=silent crashkernel=2G-:128M echo 'Loading initial ramdisk ...' initrd /initrd-3.10.1-3.g0cd5432-default } After installation boot parameters like sysrq_always_enabled or console=ttyS0,57600 are missing. -- 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 16

[Bug 837491] New: YaST appears only briefly on installation start
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=837491 https://bugzilla.novell.com/show_bug.cgi?id=837491#c0 Summary: YaST appears only briefly on installation start Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rsalevsky(a)suse.com QAContact: jsrain(a)suse.com CC: fehr(a)suse.com, trenn(a)suse.com, jreidinger(a)suse.com Found By: Development Blocker: --- Created an attachment (id=554920) --> (http://bugzilla.novell.com/attachment.cgi?id=554920) y2log When I start an installation of openSuse Factory then the YaST window shows up once briefly and then the installation stops. I found this line in the y2log: 2013-08-29 09:04:07 <3> ain.arch.suse.de(3794) [Y2Ruby] binary/YRuby.cc(loadModule):148 Module /mounts/mp_0001/usr/share/YaST2/modules/Storage load failed:cannot load such file -- storage at /usr/lib64/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require' The full log is attached. -- 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 710133] New: slow transfer between computer and USB key
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=710133 https://bugzilla.novell.com/show_bug.cgi?id=710133#c0 Summary: slow transfer between computer and USB key Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: PC OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: hayathms(a)gmail.com QAContact: qa(a)suse.de CC: danilo.gomes.freitas(a)ibest.com.br Depends on: 639427 Found By: Community User Blocker: --- +++ This bug was initially created as a clone of Bug #639427 +++ User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.53 Safari/534.3 The USB transfer is very slow it is upto 1Mb/S max, takes 3-4 hours for 6 GB transfer from My laptop to Micro-SD card, while same card with same computer in Ubuntu takes less than 30 minits. Can anyone please look into it, We have wrote several posts in forms but no one replying. please solve this, and also this is corrupting my Micro SD with corrupted mp2 files. I believe OpenSuse 11.4 has serious problem, and USB transfer is Extremely important function. My Lapi - Acer Aspire 4736ZG -- 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 13

[Bug 763399] New: excessive swap out due to compaction/LRU aging
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=763399 https://bugzilla.novell.com/show_bug.cgi?id=763399#c0 Summary: excessive swap out due to compaction/LRU aging Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mhocko(a)suse.com QAContact: qa-bugs(a)suse.de CC: ke(a)suse.com, mhocko(a)suse.com, mgorman(a)suse.com Found By: --- Blocker: --- This is a follow up for bug 719416. Karl is still seeing serious hick ups which seem to be caused by excessive swap out. From the vmstat logs (which he provided at https://bugzilla.novell.com/attachment.cgi?id=488809) we can clearly see that we really swap out a lot: $ grep pswpout bug-719416_vmstat.log | uniq -c 3 pswpout 4170 719 pswpout 5472 27 pswpout 5540 5 pswpout 5612 1 pswpout 5788 908 pswpout 5903 755 pswpout 6024 We swap out 1300 pages within a second. If we have a look at LRUs during that time period: $ grep nr_inactive_anon bug-719416_vmstat.log | head -n 6 nr_inactive_anon 55889 nr_inactive_anon 55889 nr_inactive_anon 55889 nr_inactive_anon 58193 <<< 2304 nr_inactive_anon 58193 nr_inactive_anon 58193 $ grep nr_active_anon bug-719416_vmstat.log | head -n 6 nr_active_anon 200718 nr_active_anon 200742 nr_active_anon 200742 nr_active_anon 109727 <<< -91015 nr_active_anon 109741 nr_active_anon 109763 First of all, inactive list is really low (active list is 4 times bigger!). The difference gets lower after 3rd second (when we start swapping). Inactive list gets slightly bigger while the active list get's down really considerably. $ grep nr_inactive_file bug-719416_vmstat.log | head -n 6 nr_inactive_file 219248 nr_inactive_file 219259 nr_inactive_file 219258 nr_inactive_file 266880 <<< 47622 nr_inactive_file 266880 nr_inactive_file 266883 $ grep nr_active_file bug-719416_vmstat.log | head -n 6 nr_active_file 192618 nr_active_file 192624 nr_active_file 192626 nr_active_file 218326 <<< 25700 nr_active_file 218326 nr_active_file 218326 Page cache went considerably up (by ~70k pages) which suggests that we had a hungry reader at that time. active vs. inactive lists seem to be balanced properly. $ grep nr_free_pages bug-719416_vmstat.log | head -n6 nr_free_pages 25275 nr_free_pages 25269 nr_free_pages 25267 nr_free_pages 33473 nr_free_pages 33440 nr_free_pages 33481 I guess we hit the water marks. Did we hit the direct reclaim as well? $ grep allocstall bug-719416_vmstat.log | head -n6 allocstall 45 allocstall 45 allocstall 45 allocstall 1992 <<< Yeah, we did And what about compaction? $ grep compact_pages_moved bug-719416_vmstat.log | head -n6 compact_pages_moved 131651 compact_pages_moved 131651 compact_pages_moved 131651 compact_pages_moved 186924 <<< 55273 compact_pages_moved 186924 compact_pages_moved 186924 $ grep compact_blocks_moved bug-719416_vmstat.log | head -n6 compact_blocks_moved 21117 compact_blocks_moved 21117 compact_blocks_moved 21117 compact_blocks_moved 26055 <<< 4938 compact_blocks_moved 26055 compact_blocks_moved 26055 Was the compaction successful? grep compact_fail bug-719416_vmstat.log | head -n6 compact_fail 53 compact_fail 53 compact_fail 53 compact_fail 83 <<< 30 compact_fail 83 compact_fail 83 $ grep compact_success bug-719416_vmstat.log | head -n6 compact_success 119 compact_success 119 compact_success 119 compact_success 172 <<< 53 compact_success 172 compact_success 172 Hmm, we failed only 30 times while succeeded 53. So the remaining question is who asked for the high order allocations? Check the usual suspects first: $ grep thp_fault_alloc bug-719416_vmstat.log | head -n6 thp_fault_alloc 1570 thp_fault_alloc 1570 thp_fault_alloc 1570 thp_fault_alloc 1851 <<< 281 thp_fault_alloc 1851 thp_fault_alloc 1851 Hmm, we wanted 281 huge pages, that's quite a lot. -- 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 836067] New: alias ls in zshrc causes `ls <tab>` to malfunction
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=836067 https://bugzilla.novell.com/show_bug.cgi?id=836067#c0 Summary: alias ls in zshrc causes `ls <tab>` to malfunction Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: idonmez(a)suse.com ReportedBy: tchatzimichos(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Steps to reproduce: 1) In .zshrc, add: alias ls="ls -h" (the content of the alias is not important) 2) Press ls and then <tab> 3) Observe ls to print all contents every time <tab> is pressed, instead of select them % ls bin Desktop Documents Downloads Music Pictures Public public_html Repos Templates Videos bin Desktop Documents Downloads Music Pictures Public public_html Repos Templates Videos bin Desktop Documents Downloads Music Pictures Public public_html Repos Templates Videos % cd bin/ bin/ Desktop/ Documents/ Downloads/ Music/ Pictures/ Public/ public_html/ Repos/ Templates/ Videos/ (bin/ is selected here, next <tab> press moves to Desktop/) -- 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 838000] New: Apper/PackageKit FilterNewest filter
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=838000 https://bugzilla.novell.com/show_bug.cgi?id=838000#c0 Summary: Apper/PackageKit FilterNewest filter Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: ma(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- > I found a bug in the zypp backend: > 1) It reports that it supports the FilterNewest filter, but > 2) When I call getPackages() I get all packages and not just the newest. > This can also be reproduced in apper, when just searching for packages, with > the option to use the filter enabled. -- 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 834117] New: YaST modules not working correctly with the Orca screen reader when launched from YaST control center
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=834117 https://bugzilla.novell.com/show_bug.cgi?id=834117#c0 Summary: YaST modules not working correctly with the Orca screen reader when launched from YaST control center Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: am_dxer(a)fastmail.fm QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:22.0) Gecko/20100101 Firefox/22.0 After launching modules from the YaST control center, the Orca Screen Reader does not speak the contents of the module. Reproducible: Always Steps to Reproduce: 1. Launch the YaST Control Center with the Orca screen reader enabled. 2. Select one of the modules in the control center. Actual Results: Orca reads the YaST control center, however, after a module is selected, no more speech feedback is provided. Expected Results: Orca should provide speech feedback as the user navigates the YaST module. This worked correctly in openSUSE 12.2. The problem exists in openSUSE 12.3 and also exists in the latest openSUSE factory builds. If one bypasses the control center by launching a YaST module directly from the terminal with gnomesu, orca reads its contents correctly. -- 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 836739] New: hg clone doesn't work
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=836739 https://bugzilla.novell.com/show_bug.cgi?id=836739#c0 Summary: hg clone doesn't work Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: lnussel(a)suse.com ReportedBy: tchatzimichos(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- when trying to hg clone a repo from bitbucket, I get the following: abort: could not find web.cacerts: /etc/ssl/ca-bundle.pem -- 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 837759] New: vim has wrong syntax-highlighting while editing /etc/resolv.conf - IPv6-Adresse marked red - invalid
by bugzilla_noreply＠novell.com 02 Sep '13

02 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=837759 https://bugzilla.novell.com/show_bug.cgi?id=837759#c0 Summary: vim has wrong syntax-highlighting while editing /etc/resolv.conf - IPv6-Adresse marked red - invalid 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: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tschaefer(a)t-online.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 The editor vim don't know IPv6-Adresses in /etc/resolv.conf The marked like invalid IPv4-Adresses. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: valid IPv6-adresses should marked as valid entry. -- 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