March 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 866372] New: when shutting down network is turned off before unmounting autfs nfs mounts
by bugzilla_noreply＠novell.com 03 Mar '14

03 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=866372 https://bugzilla.novell.com/show_bug.cgi?id=866372#c0 Summary: when shutting down network is turned off before unmounting autfs nfs mounts Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rob.verduijn(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Hello, I use traditional networking on my system with a static ip. I also use autofs to mount several nfs4 shares on my system. When I shutdown the system it takes very long before the system turns of. In the messages on the screen I see that the network interface is turned off and after that the autofs mounts are unmounted. This takes very long because there is no network anymore and the system waits for each unmount to timeout before finaly shutting down. Reproducible: Always Steps to Reproduce: 1. create a traditional static ip network configuration 2. define a couple nfs4 mounts via autofs 3. restart the autofs 4. access the mounts to activate them 5. shutdown the system 6. hit escape to see the shutdown messages 7. note that the network interface is turned off before the unmounting of nfs4 mounts Actual Results: network interface is switched off before unmounting off networked filesystems the shutdown takes very long to complete Expected Results: first unmount the filesystems then turn of the network interface the shutdown takes a very short time this works fine when using NetworkManager for network configuration, sadly I need a bridge so this is not an option. -- 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 795005] New: perl-Digest-Whirlpool corrupted unsorted chunks
by bugzilla_noreply＠novell.com 03 Mar '14

03 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=795005 https://bugzilla.novell.com/show_bug.cgi?id=795005#c0 Summary: perl-Digest-Whirlpool corrupted unsorted chunks Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: PowerPC-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dvaleev(a)suse.com QAContact: qa-bugs(a)suse.de CC: power-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=517489) --> (http://bugzilla.novell.com/attachment.cgi?id=517489) core file test crashes while running new.t /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(1, 'blib/lib', 'blib/arch')" t/new.t t/new.t .. 1..7 ok 1 - The object isa Digest::Whirlpool ok 2 - The object isa Digest::Whirlpool ok 3 - The object isa Digest::Whirlpool ok 4 - The object isa Digest::Whirlpool::Subclass::One ok 5 - The object isa Digest::Whirlpool::Subclass::Two ok 6 - The object isa Digest::Whirlpool ok 7 - The object isa Digest::Whirlpool::Subclass::Three *** Error in `/usr/bin/perl': free(): corrupted unsorted chunks: 0x00000100025e7100 *** ======= Backtrace: ========= /lib64/libc.so.6(+0xabb14)[0xfff7ae2bb14] /lib64/libc.so.6(+0xacc38)[0xfff7ae2cc38] /lib64/libc.so.6(+0xaf220)[0xfff7ae2f220] /lib64/libc.so.6(cfree-0x1183e0)[0xfff7ae30418] /usr/bin/perl(Perl_safesysfree-0x1272b0)[0x10094608] /usr/bin/perl(Perl_hv_undef_flags-0x1067b0)[0x100b6938] /usr/bin/perl(Perl_sv_clear-0xeee78)[0x100cef30] /usr/bin/perl(Perl_sv_free2-0xee448)[0x100cf978] /usr/bin/perl[0x100c5c90] /usr/bin/perl(Perl_sv_clean_objs-0xed9c4)[0x100d04ec] /usr/bin/perl(perl_destruct-0x1789e8)[0x100415e0] /usr/bin/perl(main-0x19943c)[0x1001f764] /lib64/libc.so.6(+0x4582c)[0xfff7adc582c] /lib64/libc.so.6(__libc_start_main-0x17db88)[0xfff7adc5a50] ======= Memory map: ======== 10000000-101b0000 r-xp 00000000 08:03 8497268 /usr/bin/perl 101b0000-101d0000 rw-p 001a0000 08:03 8497268 /usr/bin/perl 10002570000-100027b0000 rw-p 00000000 00:00 0 [heap] fff7ac60000-fff7ac70000 r-xp 00000000 08:03 8561327 /home/abuild/rpmbuild/BUILD/Digest-Whirlpool-1.09/blib/arch/auto/Digest/Whirlpool/Whirlpool.so fff7ac70000-fff7ac80000 rw-p 00000000 08:03 8561327 /home/abuild/rpmbuild/BUILD/Digest-Whirlpool-1.09/blib/arch/auto/Digest/Whirlpool/Whirlpool.so fff7ac80000-fff7ad80000 rw-p 00000000 00:00 0 fff7ad80000-fff7af30000 r-xp 00000000 08:03 8496769 /lib64/libc-2.16.90.so fff7af30000-fff7af40000 r--p 001a0000 08:03 8496769 /lib64/libc-2.16.90.so fff7af40000-fff7af60000 rw-p 001b0000 08:03 8496769 /lib64/libc-2.16.90.so fff7af60000-fff7af80000 r-xp 00000000 08:03 8496795 /lib64/libpthread-2.16.90.so fff7af80000-fff7afa0000 rw-p 00010000 08:03 8496795 /lib64/libpthread-2.16.90.so fff7afa0000-fff7afb0000 r-xp 00000000 08:03 8496773 /lib64/libcrypt-2.16.90.so fff7afb0000-fff7afc0000 rw-p 00000000 08:03 8496773 /lib64/libcrypt-2.16.90.so fff7afc0000-fff7aff0000 rw-p 00000000 00:00 0 fff7aff0000-fff7b000000 r-xp 00000000 08:03 8496775 /lib64/libdl-2.16.90.so fff7b000000-fff7b010000 rw-p 00000000 08:03 8496775 /lib64/libdl-2.16.90.so fff7b010000-fff7b0d0000 r-xp 00000000 08:03 8496777 /lib64/libm-2.16.90.so fff7b0d0000-fff7b0e0000 rw-p 000b0000 08:03 8496777 /lib64/libm-2.16.90.so fff7b0e0000-fff7b0f0000 rw-p 00000000 00:00 0 fff7b0f0000-fff7b110000 r-xp 00000000 00:00 0 [vdso] fff7b110000-fff7b140000 r-xp 00000000 08:03 8496762 /lib64/ld-2.16.90.so fff7b140000-fff7b150000 rw-p 00020000 08:03 8496762 /lib64/ld-2.16.90.so fffeef60000-fffeef90000 rw-p 00000000 00:00 0 [stack] -- 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 801775] New: liquidwar6 doesn't start (crash)
by bugzilla_noreply＠novell.com 03 Mar '14

03 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=801775 https://bugzilla.novell.com/show_bug.cgi?id=801775#c0 Summary: liquidwar6 doesn't start (crash) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ru.vinzent(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1362.0 Safari/537.22 SUSE/25.0.1362.0 I've got the following output when tried to launch the Liquid War game: ~> liquidwar6 liquidwar6: v0.0.13beta "Blackbeard" #2950 (Dec 22 2012) linux-gnu/i586 Invalid read access of chars of wide string: "\u0437\u0430\u043f\u0443\u0441\u043a \u043a\u043e\u0434\u0430 \u0441\u0445\u0435\u043c\u044b \u0441 \u043f\u043e\u043c\u043e\u0449\u044c\u044e Guile" In ice-9/boot-9.scm: 157: 9 [#<procedure 91ce000 ()>] In unknown file: ?: 8 [lazy-catch #t #<procedure 92ba540 at ice-9/eval.scm:396:13 ()> ...] In ice-9/boot-9.scm: 171: 7 [with-throw-handler #t #<catch-closure 92b65d0> #<catch-closure 92b65c0>] In unknown file: ?: 6 [catch-closure] In ice-9/eval.scm: 407: 5 [eval # #] In unknown file: ?: 4 [c-lw6sys-log 3 ...] liquidwar6: ПРЕДУПРЕЖДЕНИЕ! dump saved in file "/home/vinzent/.liquidwar6/dump.txt" Backtrace: In ice-9/boot-9.scm: 149: 3 [catch #t #<catch-closure 9296aa0> ...] 157: 2 [#<procedure 91ce8c0 ()>] In unknown file: ?: 1 [catch-closure] ?: 0 [c-lw6sys-log 3 ...] ERROR: In procedure c-lw6sys-log: ERROR: Invalid read access of chars of wide string: "\u043f\u043e\u043b\u0443\u0447\u0435\u043d\u0430 \u043e\u0448\u0438\u0431\u043a\u0430 Guile" Some deprecated features have been used. Set the environment variable GUILE_WARN_DEPRECATED to "detailed" and rerun the program to get more information. Set it to "no" to suppress this message. liquidwar6 0.0.13-8.16 guile 2.0.5-3.2.2 Reproducible: Always Steps to Reproduce: 1. Install liquidwar6 from the Games repository 2. Launch it -- 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 866279] New: pam_mount does not unmount when user logs off
by bugzilla_noreply＠novell.com 03 Mar '14

03 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=866279 https://bugzilla.novell.com/show_bug.cgi?id=866279#c0 Summary: pam_mount does not unmount when user logs off Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rob.verduijn(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Hello, When using pam_mount to mount shares in the home directory of a user, it does not unmount them when the user logs off. Reproducible: Always Steps to Reproduce: 1. create a pam_mount for a nfs share that mounts in the user homedir <volume user="*" fstype="nfs4" server="1.2.3.4" path="Music" mountpoint="~/Music"/> 2. enable pam mount in pam.d (see man pam_mount for the howto) 3.log in as a user 4. issue mount command in terminal to confirm the shares are mounted 5. logout 6 issue mount commant as root in console to see the shares are still mounted Actual Results: shares ares till mounted Expected Results: shares should be unmounted -- 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 845652] New: single line chainloader syntax fails ("GRUB _" displays on boot attempts)
by bugzilla_noreply＠novell.com 03 Mar '14

03 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=845652 https://bugzilla.novell.com/show_bug.cgi?id=845652#c0 Summary: single line chainloader syntax fails ("GRUB _" displays on boot attempts) Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=563225) --> (http://bugzilla.novell.com/attachment.cgi?id=563225) y2logs from 32 bit core2duo host hs80e Initial summary: single line chainloader syntax fails ("GRUB _" displays on boot attempts) On attempt to chainload boot: "chainloader (hd2,23)+1 GRUB _" is all that displays after Grub menu clears. That first line is the sole menu.lst stanza cmdline. This dates back at least to 11.4. I've only seen it on systems with md RAID1 partitions spread across HD0 and HD1 and the target / on HD2 (and / partitions above #15). Failure happens whether Grub Legacy setup is during installation, or using YaST-configured /etc/grub.conf and grub script, or using setup from a grub> prompt. Even after changing /boot/grub/device.map to contain only valid by-id entries boot fails, though setup command reports success on every attempt. I normally boot 13.1 (and 11.4, 12.1, 12.2 & 12.3) on the system by loading vmlinuz and initrd directly (Grub Legacy IIRC from 12.3B1 installed on a HD0 partition) instead of by chainloading. If the menu.lst stanza is instead of as above is as follows: rootnoverify (hd2,23) chainloader +1 then success, or root (hd2,23) chainloader +1 then also success. In every single HD installation I've done (hundreds), the single line syntax normally 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 9

[Bug 802977] New: It's not possible to use the computer as a bluetooth speaker
by bugzilla_noreply＠novell.com 02 Mar '14

02 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=802977 https://bugzilla.novell.com/show_bug.cgi?id=802977#c0 Summary: It's not possible to use the computer as a bluetooth speaker Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: novell(a)pontohonk.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.69 Safari/537.17 Bluez offers the feature to use the computer as an audio sink for bluetooth devices like smartphones. This is not included in the opensuse version of bluez Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Pairing to an opensuse machine does not give us a A2DP sink. Expected Results: It is possible to use opensuse as an A2DP sink. -- 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 8

[Bug 848829] New: Brightness issue in KDE on asus laptop k53sd
by bugzilla_noreply＠novell.com 01 Mar '14

01 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=848829 https://bugzilla.novell.com/show_bug.cgi?id=848829#c0 Summary: Brightness issue in KDE on asus laptop k53sd Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: fricker(a)bk.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I can set bright with my Fn keys and with mouse in kde applet but, then I set bright by button brightness indicator in kde doesn't move and popup indicator not show up(it does then I use mouse). Seems like signals from buttons have no handlers in KDE. I used last live cd KDE from the site. 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 1

[Bug 866439] New: Wallpaper - Slideshow - Custom Folders = saved settings do not reappear when reopening the window later on
by bugzilla_noreply＠novell.com 01 Mar '14

01 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=866439 https://bugzilla.novell.com/show_bug.cgi?id=866439#c0 Summary: Wallpaper - Slideshow - Custom Folders = saved settings do not reappear when reopening the window later on Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: jeanbarloy(a)free.fr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.117 Safari/537.36 Desktop Settings > Plasma Desktop Shell When choosing Slideshow as wallpaper, then checking Custom Folders, then adding folders and clicking on Apply: slideshow works as planned but the settings are not saved when you open the settings window again later on. Reproducible: Always Expected Results: Saved settings should reappear when you open the settings window after applying. -- 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 866429] New: bluedevil version 2.0~rc1 from extra-repo: binds to untrusted devices, continues search if cancelled, registers all devices found as "known"
by bugzilla_noreply＠novell.com 01 Mar '14

01 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=866429 https://bugzilla.novell.com/show_bug.cgi?id=866429#c0 Summary: bluedevil version 2.0~rc1 from extra-repo: binds to untrusted devices, continues search if cancelled, registers all devices found as "known" Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Provided that you accept after that quite long time period after the release some bug report about k-bluetooth support (see release notes) I would like to file this report about the package 2.0~rc1 of bluedevil (and libraries) offered in Extra, since this appears to be a release candidate. If you install these packages you have effectively a fix for the failing support for MS bluetooth mice (and probably for other devices) with the following drawbacks: When you do a search for add new devices and you decide to cancel, the search will go on anyway without your knowledge in background. After a 20 min (I am living in front of a bus stop) you will have about 50 devices as "known devices"). Two of these devices (a blackberry and a bt-card of a pc) I did find them in kde-settings - proxy settings - bluetooth as registered devices to my system!!! I was not asked for any password or pin when this happened. This is not the case with the regular bluetooth package. The package does further have no memory when you set: do not power on bluetooth. After a reboot it is switched on again. I tend to belief that this is also an unwanted behavior. Reproducible: Always Steps to Reproduce: 1. Install the packages 2.0~rc1 with libraries. 2. Put yourself in a crowded place and do: add new device. Interrupt the search with cancel. 3. After more or less 15 min, try to look for new devices. Enjoy 50 new "friends". 4. Do this in front of a bus station or where there is a high throughput of people with devices. You will find new "friends" registered in kde-system settings - proxy settings - bluetooth Actual Results: KDE-bt support does not honor the canceling of search for devices. It does join unknown devices to known devices. It allows registering of devices in "kde-proxy" settings dialog, without pairing. It does not remember the request for being deactivated (setting does not survive a re-log in). Expected Results: KDE does now bind to HID from MS and other mices (compliments). But it should NOT accept devices as known if no pin has been given and if the devices are not paired. It should in ANY case register these devices in proxy-settings of KDE (these ones DO survive a re-log in). It should also cancel a search for new devices when asked to do so. New and not paired devices should not be put in the same list as paired devices. Actually in KNOWN devices there should appear only PAIRED devices. By this current state it is IMO not advisable to leave this package in extra as is. Hardware setting: encountered with Lenovo X201 integrated bt card System is standard 13.1. Package from kde-extra repo. Version: 2.0~rc1 64 bit -- 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 800858] New: gpk-gstreamer-installer: fails to install if two packages found
by bugzilla_noreply＠novell.com 01 Mar '14

01 Mar '14

https://bugzilla.novell.com/show_bug.cgi?id=800858 https://bugzilla.novell.com/show_bug.cgi?id=800858#c0 Summary: gpk-gstreamer-installer: fails to install if two packages found Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: coolo(a)suse.de ReportedBy: dimstar(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=522271) --> (http://bugzilla.novell.com/attachment.cgi?id=522271) log file Using totem, and starting a video file while not having the corresponding codec installed, triggers a package kit dialog to install the missing packages (if possible.. mostly requires 3rd party repositories). In my current case, gpk/zypp suggests two versions of gstreamer-plugins-good to be installed (on top of one already insytalled) and then fails with 'can not install both') zypper se -s gstreamer-plugins-good lists those at the moment (to 'help' understanding what is available in the repos): i | gstreamer-plugins-good | package | 1.0.5-17.9 | x86_64 | (System Packages) v | gstreamer-plugins-good | package | 1.0.5-19.1 | x86_64 | GStreamer v | gstreamer-plugins-good | package | 1.0.5-17.15 | i586 | GStreamer v | gstreamer-plugins-good | package | 1.0.5-17.7 | x86_64 | GNOME:Factory v | gstreamer-plugins-good | package | 1.0.5-17.7 | i586 | GNOME:Factory Attached the pk_backend_zypp log file for further analysis. -- 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 17