April 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 801870] New: [vorbisgain] There is no -r or --recursive option
by bugzilla_noreply＠novell.com 11 Apr '13

11 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=801870 https://bugzilla.novell.com/show_bug.cgi?id=801870#c0 Summary: [vorbisgain] There is no -r or --recursive option Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: smyskoff(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello. I just found that vorbisgain does not support -r option. Quote from manual: -r, --recursive Enter directories (recursively) and search for files, if directories or file patterns are specified. Note: Only available if vorbisgain was configured with --enable-recursive. So, it looks like vorbisgain was configured without --enable-recursive option. But it'll be quite convenient to have such feature as recursive vorbisgain scan. If it's possible to build vorbisgain with this option it'll very helpful. Best regards, Sergey Myskov. -- 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 814648] New: Fontconfig reports error
by bugzilla_noreply＠novell.com 11 Apr '13

11 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=814648 https://bugzilla.novell.com/show_bug.cgi?id=814648#c0 Summary: Fontconfig reports error Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pgajdos(a)suse.com ReportedBy: msvec(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Eg. when running libreoffice: Fontconfig warning: "/etc/fonts/conf.d/56-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated. -- 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 738156] New: bind fails to start if switched to non chroot setup
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=738156 https://bugzilla.novell.com/show_bug.cgi?id=738156#c0 Summary: bind fails to start if switched to non chroot setup Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: ug(a)suse.com ReportedBy: lmuelle(a)suse.com QAContact: qa(a)suse.de CC: lmuelle(a)suse.com, lynn(a)steve-ss.com Found By: Community User Blocker: No If NAMED_RUN_CHROOTED is set to "no" in /etc/sysconfig/named the sym link /var/run/named points to itself. Instead we have to create a directory owned by named:named. Please test home:lmuelle:branches:server:dns/bind. -- 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 32

[Bug 716745] New: yast2 failed to get DNS server up
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=716745 https://bugzilla.novell.com/show_bug.cgi?id=716745#c0 Summary: yast2 failed to get DNS server up Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=449865) --> (http://bugzilla.novell.com/attachment.cgi?id=449865) the logs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20100101 Firefox/6.0 I´ve tried to get up a nameserver with yast2. It failed with an error message on finishing that tells that there are problems to start name. The message is a bit cryptic to me, so have a look at the screenshot I attach. The configuration was: 1.forwared settings : 157.157.120.177 2.DNS-Zones as default by yast2 (which may be the problem) -> example.com and the long lines of 0.0.0.... .ip6.arpa 3.Open Port in firewall 4.On:Start Now and when booting. Reproducible: Always Steps to Reproduce: 1.See above 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 34

[Bug 715881] New: named (BIND) does not start - openssl files missing in chroot
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=715881 https://bugzilla.novell.com/show_bug.cgi?id=715881#c0 Summary: named (BIND) does not start - openssl files missing in chroot Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: ug(a)suse.com ReportedBy: mkubecek(a)suse.com QAContact: qa(a)suse.de Found By: Community User Blocker: --- BIND nameserver named fails to start with default configuration because it cannot find OpenSSL files in chroot, namely /etc/ssl/openssl.conf /lib64/engines/* After copying these under /var/lib/named, named starts cleanly. To be precise, copying /lib64/engines/libgost.so is enough to start with default configuration. But IMHO it would be better to have all of them. If AppArmor is active, one needs to add /var/lib/named/lib64/engines/* mix, to the profile as well. -- 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 710430] New: DNS problem with LDAP server
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=710430 https://bugzilla.novell.com/show_bug.cgi?id=710430#c0 Summary: DNS problem with LDAP server Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: qwatli(a)yahoo.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 after I install named (DNS) and LDAP when I try to record the DNS server with LDAP server ,the UI (user interface ) disappear and I found the flowing auto generated error from Yast2 : YaST got signal 11 at YCP file dns-server/dialog-main.ycp:2 /sbin/yast2: line 423: 6621 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS 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 27

[Bug 813016] New: Mozc icons in Fcitx are too ugly!
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=813016 https://bugzilla.novell.com/show_bug.cgi?id=813016#c0 Summary: Mozc icons in Fcitx are too ugly! Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: i(a)marguerite.su QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 This is a bugreport for myself. I'm not Japanese, so I never use fcitx-mozc. A few days ago I saw a screenshot from a Japanese blogger, He was talking about mozc in fcitx. http://folioscope.hatenablog.jp/entry/2013/03/27/235537 And I realized that those icons from mozc upstream are not good looking under openSUSE. Because we use a black theme, and those icons have white borders. And they're even not in a same size! So I made a set of icons in fcitx upstream. and replace them here in openSUSE. Reproducible: Always -- 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 801794] New: Error: "this QEMU binary lacks hda support"
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=801794 https://bugzilla.novell.com/show_bug.cgi?id=801794#c0 Summary: Error: "this QEMU binary lacks hda support" Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KVM AssignedTo: afaerber(a)suse.com ReportedBy: jdouglas(a)suse.com QAContact: jdouglas(a)suse.com CC: brogers(a)suse.com, jfehlig(a)suse.com Found By: --- Blocker: --- Created an attachment (id=523073) --> (http://bugzilla.novell.com/attachment.cgi?id=523073) Windows 7 VM configuration I am running the latest opensuse kvm build (kvm-1.3.0-193.1) built for SLES 11 SP2 (from repo: http://download.opensuse.org/repositories/Virtualization/SLE_11_SP2/ ). When I started virt-manager and attempted to launch my Windows 7 VM (for the first time in about 3 months), the VM would not start and I received the following error message: --------------- Error starting domain: unsupported configuration: this QEMU binary lacks hda support Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1081, in startup self._backend.create() File "/usr/lib64/python2.6/site-packages/libvirt.py", line 510, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: unsupported configuration: this QEMU binary lacks hda support --------------- The VM configuration that I collected from libvirt (libvirt-0.9.6-0.23.1) 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 1

[Bug 737070] New: qemu-kvm: No sound w/ICH6 in 64-bit VM on 64-bit
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=737070 https://bugzilla.novell.com/show_bug.cgi?id=737070#c0 Summary: qemu-kvm: No sound w/ICH6 in 64-bit VM on 64-bit Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: erik(a)lotspeich.org QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=467682) --> (http://bugzilla.novell.com/attachment.cgi?id=467682) libvirt configuration User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 I have OpenSUSE 12.1 and I'm using virt-manager w/qemu-kvm with a 64-bit Windows 7 guest. The Windows 7 guest correctly sees the ICH6 sound device and it appears to work from the Windows point-of-view. I get no sound, however. At first, I thought it was a permissions issue, but I added the "qemu" user to various groups including audio, pulse, and pulse-access. I even went crazy and executed qemu-kvm with the aoss wrapper. I see that qemu-kvm is linked against libpulse, so I believe it should work just fine. I asked this question on the qemu-devel mailing list and they believe it should work and it could be a distro bug. Reproducible: Always Steps to Reproduce: libvirt configuration for my VM is attached. Actual Results: No sound Expected Results: Sound when VM emulated sound device is functioning -- 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 812189] New: Akonadi rewrite XDG_DATA_DIRS and confuse GTK applications
by bugzilla_noreply＠novell.com 10 Apr '13

10 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=812189 https://bugzilla.novell.com/show_bug.cgi?id=812189#c0 Summary: Akonadi rewrite XDG_DATA_DIRS and confuse GTK applications Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: mcaj(a)suse.com QAContact: qa-bugs(a)suse.de CC: sbrabec(a)suse.com Found By: Community of Practice Blocker: --- HI, shortly after I updated my system to 12.3 I found that icons for GTK applications disappeared. qt apps ware fine. First I thought there is something wrong with gtkutils, because I had in logs messages like this: Gtk: Useless empty GtkIconSource GLib-GObject: g_object_unref: assertion `G_IS_OBJECT (object)' failed gtkutils: gdk_pixbuf_new_from_file() returned nothing for file /usr/share/icons/hicolor/16x16/apps/pidgin.png: Couldn't recognize the image file format for file '/usr/share/icons/hicolor/16x16/apps/pidgin.png' or: glib.GError: Couldn't recognize the image file format for file '/usr/share/heartbeat-gui/ha.png' Then I spend several hours to trying found broken settings in gtk..... via gnomevfs-ls I found the system really doesn't know png file .. The reason for it is simple. I looks like akonadi rewrite XDG_DATA_DIRS ! my set looks like this: >set |grep XDG XDG_CONFIG_DIRS=/etc/xdg XDG_DATA_DIRS=/usr/share/akonadi/agents on the other machine without Akonadi it looks like this: XDG_CONFIG_DIRS=/etc/xdg XDG_DATA_DIRS=/usr/share:/etc/opt/kde3/share:/opt/kde3/share I'm not sure if/why Akonadi needs XDG_DATA_DIRS, but if so it should looks like this XDG_DATA_DIRS=/usr/share:/etc/opt/kde3/share:/opt/kde3/share:/usr/share/akonadi/agents Please can you have look into Akonadi code and fix it there ? Thanks. Martin PS Thanks to sbrabec to find 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