December 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 792330] New: nvidia ion HDMI out wrong default device
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=792330 https://bugzilla.novell.com/show_bug.cgi?id=792330#c0 Summary: nvidia ion HDMI out wrong default device Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de Found By: Third Party Developer/Partner Blocker: --- This is on a Lenovo IdeaCentre Q150, Intel Atom / NVidia ION nettop box. Trying to get sound over HDMI is not easy, as the default device is wrong: linux-pwuk:~ # aplay -L [...] hdmi:CARD=NVidia,DEV=0 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=1 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=2 HDA NVidia, HDMI 0 HDMI Audio Output hdmi:CARD=NVidia,DEV=3 HDA NVidia, HDMI 0 HDMI Audio Output This works: # aplay -D hdmi:CARD=NVidia,DEV=3 /usr/share/sounds/alsa/test.wav however, the default for pulseaudio etc. seems to be to use hdmi:CARD=NVidia,DEV=0 which produces no output. A different default would be useful, or an option to set the default device (I have not found one) Sorry, no easy way to test this with Factory :-( -- 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 729169] New: Double entry for feed reader
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=729169 https://bugzilla.novell.com/show_bug.cgi?id=729169#c0 Summary: Double entry for feed reader Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: m4ng4n(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 In K-Menu -> Applications -> Internet is a double entry for Feed Reader 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 3

[Bug 789182] New: libopensync-plugin-evolution2 has been failing to build in Factory for a long time
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=789182 https://bugzilla.novell.com/show_bug.cgi?id=789182#c0 Summary: libopensync-plugin-evolution2 has been failing to build in Factory for a long time Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: cstender(a)opensuse.org ReportedBy: christian.morales.vega(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- libopensync-plugin-evolution2 has been failing to build in Factory for a long time --- Comment #1 from Christopher Stender <cstender(a)opensuse.org> 2012-11-12 10:17:53 UTC --- *** Bug 789184 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=789184 -- 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 792335] New: tmpfs allocates excessive amount of memeory
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=792335 https://bugzilla.novell.com/show_bug.cgi?id=792335#c0 Summary: tmpfs allocates excessive amount of memeory Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Curt.Blank(a)curtronics.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 tmpfs filsystems allocate excessive memory. i.e. devtmpfs 16G 84K 16G 1% /dev tmpfs 16G 68K 16G 1% /dev/shm tmpfs 16G 1.2M 16G 1% /run tmpfs 16G 1.2M 16G 1% /var/lock tmpfs 16G 1.2M 16G 1% /var/run tmpfs 16G 0 16G 0% /media Provide a configuration variable whereby the user can specify the memory amount to be used such as size=12%. Yes 16G of memory is not really used but if some process goes amuck and starts writing to one of those mount points it could be used possibly degrading system performance. There is no need to set the maximum that high and should be considered best practice not to. Reproducible: Always Steps to Reproduce: 1. boot 2. 3. Actual Results: Excessive amount of memory allocated to tmpfs file systems. Expected Results: Excessive amount of memory allocated to tmpfs file systems. -- 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 10

[Bug 732976] New: Headphones and microphone in front jacks not working
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=732976 https://bugzilla.novell.com/show_bug.cgi?id=732976#c0 Summary: Headphones and microphone in front jacks not working Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: hrach2(a)post.sk QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=464243) --> (http://bugzilla.novell.com/attachment.cgi?id=464243) alsa-info.txt, All unplugged, internal speakers and internal microphone working User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 Using opensuse 12.1 on Fujitsu Siemens Celsius H270. I have two possibilities, how to connect headphones and microphone A. Connectors directly on notebook (in front part) B. Connectors on port replicator With default model option (empty string): When connecting headphones to A, speakers are muted, but no sound in headphones When connecting microphone to A, nothing is recorded My codec is Realtek ALC262. Headphones and microphone in connection B are working correctly. For kernel 2.6 problems for this hardware were successfully solved (see https://bugzilla.novell.com/show_bug.cgi?id=637263) Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: Headhphones and microphones in connection A (front jacks) are not working Expected Results: Headhphones and microphones in connection A (front jacks) working correctly Actual SW configuration: # rpm -qa '*alsa*' alsa-oss-1.0.17-37.1.2.x86_64 alsa-plugins-pulse-1.0.24-18.1.2.x86_64 alsa-plugins-1.0.24-18.1.2.x86_64 alsa-1.0.24.1-23.1.2.x86_64 alsa-plugins-32bit-1.0.24-18.1.2.x86_64 alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64 alsa-oss-32bit-1.0.17-37.1.2.x86_64 alsa-utils-1.0.24.2-12.8.1.x86_64 # rpm -qa '*pulse*' pulseaudio-module-lirc-1.1-1.2.x86_64 alsa-plugins-pulse-1.0.24-18.1.2.x86_64 vlc-aout-pulse-1.1.12-11.4.x86_64 libpulse0-1.1-1.2.x86_64 pulseaudio-module-jack-1.1-1.2.x86_64 libpulse0-32bit-1.1-1.2.x86_64 pulseaudio-module-x11-1.1-1.2.x86_64 pulseaudio-lang-1.1-1.2.noarch pulseaudio-module-zeroconf-1.1-1.2.x86_64 alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64 pulseaudio-module-bluetooth-1.1-1.2.x86_64 pulseaudio-utils-1.1-1.2.x86_64 libxine1-pulse-1.1.20-59.3.x86_64 libpulse-mainloop-glib0-1.1-1.2.x86_64 pulseaudio-1.1-1.2.x86_64 # rpm -q libasound2 libasound2-1.0.24.1-23.1.2.x86_64 # uname -a Linux x.y.z 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux # cat /etc/modprobe.d/50-sound.conf options snd slots=snd-hda-intel # u1Nb.6gHZkwoFfB3:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel -- 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 791855] New: bash drops errexit option in sourced file
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=791855 https://bugzilla.novell.com/show_bug.cgi?id=791855#c0 Summary: bash drops errexit option in sourced file Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rschiele(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11 While normally sourced files have identical options set like the invoking environment this is not true if the sourcing is done from within a function foo that was called with something like: foo && true The following example demonstrates this: $ cat bug #!/bin/bash set -e int() { echo A: $- . source echo D: $- } echo Broken: int && true echo OK: int $ cat source echo B: $- false echo C: $- $ bash bug Broken: A: ehB B: hB C: hB D: ehB OK: A: ehB B: ehB $ This error showed up in bash 4.0 first and was not present in 3.2 or older. As you can see in the invocation "int && true" the flag is still set inside the function but magically disappears once the file is sourced, while in the second incocation "int" everything behaves as expected. Apparently something gets broken when the exit on error is temporarily disabled for the chained command "int && true" because while it gets properly restored within the function itself it disappears again when sourcing the other file. This problem was also reported upstream as https://savannah.gnu.org/support/index.php?108191 Reproducible: Always Steps to Reproduce: Invoke the scripts as described in the details section. Actual Results: errexit option gets dropped in sourced file. Expected Results: errexit option should not get dropped in sourced file. -- 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 781046] New: libtag1 does not read MP4 tags
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=781046 https://bugzilla.novell.com/show_bug.cgi?id=781046#c0 Summary: libtag1 does not read MP4 tags Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: imre_herceg(a)freemail.hu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0 Kid3 using libtag1 does not read properly the tags of files in the MP4 container format (aac). Nor do Clementine, soundKonverter which also use libtag1 for reading the tags. They only show the title, track number and album artist tag, but when I try to update any of the tags, all the tags get deleted. MPlayer shows the tags (it apparently does not use libtag.so.1). When I replaced libtag.so.1 and libtag.so.1.7.2 in the /usr/lib directory with the version from openSUSE 12.1 (libtag.so.1 and libtag.so.1.7.0), Kid3 showed all the tags present in the music files. Reproducible: Always Steps to Reproduce: 1. Launch kid3 (if you do not have it, install it first). 2. Open an m4a (aac) file within Kid3, which has artist, title, album, comment tags. 3. Actual Results: The Artist, Title, Album, Comment fields seem to be empty. Expected Results: The Artist, Title, Album, Comment fields should not be empty, they should be isplay. -- 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 613873] New: Bootloader is always installed incorrectly on certain system
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

http://bugzilla.novell.com/show_bug.cgi?id=613873 http://bugzilla.novell.com/show_bug.cgi?id=613873#c0 Summary: Bootloader is always installed incorrectly on certain system Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)novell.com ReportedBy: bugzilla(a)go4more.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux; de-DE) AppleWebKit/532.4 (KHTML, like Gecko) rekonq Safari/532.4 I report this bug against 11.3, however, openSUSE has for several versions never ever been able to consistently put the bootloader grub to the correct location as long as I've been using this hardware (several years). On a system with seperate Windows- and Linux-harddisks, grub is very often written to the wrong harddisk, making the system unbootable and sometimes partially damaging the Windows installation (Windows XP repair console necessary - FIXMBR, FIXBOOT). This happens reproducably during new installations: Then grub always complains "/boot/message not found" during the first boot. Using the grub-console, however, "kernel=/boot/vmlinux" and "initrd=/boot/initrd" will find the correct files nevertheless and boot the Linux installation. However, this also happens sometimes during system updates requiring bootloader re-setups. Here I have, with no apparent logic, different results, from no problem to messing up the Windows boot sector. The system consists of two harddisks: 40 GB Harddisk, Windows XP (further referred to as W) 160 GB Harddisk, Linux (L) BIOS order (as reported during BIOS start up): W: Channel 0 (first IDE/PATA-drive) L: Channel 3, (first SATA-drive) Harddisk boot priority (as set up with BIOS settings) First W, then L (i.e. reverse order) The running Linux installation at least recognizes W as /dev/sdb1, L as /dev/sda1, i.e. according to the BIOS priority settings. Expected bootloader installation: MBR is on drive L. Bootloader should be installed here and leave completely W untouched. When booting Windows, only W and L have to be logically swapped with the corresponding grub command in order to make Windows believe to be on the first drive in the system. The openSUSE bootloader installation, however, does seemingly not always recognize the harddisks in the same order: There seem to be situations in which the harddisks are mixed up. Moreover, grub seems to be reluctant to put the bootloader on the 160 GB-drive, complaining about an "128 GB" problem making the system potentially unbootable during new installations. As a user, I have no chance to find out whether the system messes up the bootloader installation or not, as there are no or not enough informations how the system assumes to set up the bootloader. And, even more annoying, there seem to be situations in which a grub installation, manually adapted to be correct, can be changed without warning to be defunct. Any process requiring a bootloader reinstall is a game of chance for mr :( : I don't know which actual drive will be written to if YaST talks about "MBR". I can't tell the bootloader "whatever you think is necessary, simply don't ever touch partition W" During updates which require bootloader reinstalls, this process is completely automatic and gives me no further control. As the problem is probably hard to pinpoint and fix, it would be simply great to have more control over bootloader installation, and the necessary informations (which drive are we talking about now?) to make educated decisions. Reproducible: Always -- 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 16

[Bug 788443] New: 12.2 installation: choosing NetworkManager causes unresolved dependency on libsoup
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=788443 https://bugzilla.novell.com/show_bug.cgi?id=788443#c0 Summary: 12.2 installation: choosing NetworkManager causes unresolved dependency on libsoup Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: locilka(a)suse.com ReportedBy: rneuhauser(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- 12.2 DVD, New Installation, no desktop (other / text mode) * uncheck "Use Automatic Configuration" * Installation Settings / Software - Product: openSUSE - System Type: Minimal Server Selection (Text Mode) - Patterns: + Base System + Laptop + YaST Installation Packages + Software Management * confirm, it will reboot into curses YaST2 after a while * Network Configuration - enable NetworkManager - disable firewall * a popup says "These packages need to be installed: NetworkManager" - choose [Install] * a popup says: Error There are unresolved dependencies which need to be solved manually in the software manager. i'll attach y2 logs in a 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 8

[Bug 743717] New: fsck.*: Invalid argument while trying to open /dev/md/*
by bugzilla_noreply＠novell.com 03 Dec '12

03 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=743717 https://bugzilla.novell.com/show_bug.cgi?id=743717#c0 Summary: fsck.*: Invalid argument while trying to open /dev/md/* Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ray(a)openland.cz QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.77 Safari/535.7 I recently installed openSUSE 12.1 and found that fsck.* is unable to open an md device(s) during the boot. It did not happen every time, it was about 1/4 of all boots but it did happen (and stop the system start). I start digging into the detail what is going wrong there and I found hat udev has some scripts for creating /dev/md/* devices (symlinks). I also found that openSUSE 12.1 installer created following /etc/mdadm.conf file: DEVICE containers partitions ARRAY /dev/md/1 UUID=7d6b05f2:c4ca4c78:aac6bf1b:9da6b8ef ARRAY /dev/md/2 UUID=003589a4:9aa5e883:41cb207e:8a8c8541 ARRAY /dev/md/3 UUID=b9a9b25d:215c7531:0916e080:b9e2b338 My previous setup was using openSUSE 11.3 (btw worked great) and /etc/mdadm.conf has been using /dev/md* devices (not devices created by udev) so I changed the setup to: ARRAY /dev/md1 UUID=7d6b05f2:c4ca4c78:aac6bf1b:9da6b8ef ARRAY /dev/md2 UUID=003589a4:9aa5e883:41cb207e:8a8c8541 ARRAY /dev/md3 UUID=b9a9b25d:215c7531:0916e080:b9e2b338 And problem is finally gone! I guess it was failing in cases when udev created /dev/md/* devices (symlinks) too late and then fsck failed of course. This is critical problem I think and should be corrected (in installer and maybe in Yast?) in next release. Reproducible: 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 24