September 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 821629] New: no plug-ins found for cairo-dock
by bugzilla_noreply＠novell.com 07 Sep '13

07 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=821629 https://bugzilla.novell.com/show_bug.cgi?id=821629#c0 Summary: no plug-ins found for cairo-dock Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: i386 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: maxpro4u(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.20 Safari/537.36 cairo-dock installs fine but when started it reports "no plug-ins found" and then closes Reproducible: Always Steps to Reproduce: 1.install cairo-dock 2.start cairo-dock 3.cairo-dock closes Actual Results: cairo-dock plug-ins are not found in the repos cairo-dock will not run without plug-ins -- 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 839072] New: CrossToolchain:avr/avrdude: Bug
by bugzilla_noreply＠novell.com 07 Sep '13

07 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=839072 https://bugzilla.novell.com/show_bug.cgi?id=839072#c0 Summary: CrossToolchain:avr/avrdude: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: jw(a)suse.com ReportedBy: madworm_de.novell(a)spitzenpfeil.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- 5.11svn.1202-167.1: =================== The udev rules don't work on 12.2 5.11.1-2.1.1 (taken from 12.3) works just fine. -- 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 836575] New: The gnome-shell crashed once with Bus error in _st_theme_get_matched_properties() at st/st-theme.c:1000 .
by bugzilla_noreply＠novell.com 07 Sep '13

07 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=836575 https://bugzilla.novell.com/show_bug.cgi?id=836575#c0 Summary: The gnome-shell crashed once with Bus error in _st_theme_get_matched_properties() at st/st-theme.c:1000 . 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: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: bkbin005(a)rinku.zaq.ne.jp QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=554077) --> (http://bugzilla.novell.com/attachment.cgi?id=554077) a GDB backtrace file User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1610.5 Safari/537.36 I am testing openSUSE 13.1 Milestone 4 x86_64 with GNOME desktop in VirtualBox 4.2.16 r86992 on Windows 7 SP1 64 bit . Host information: https://dl.dropboxusercontent.com/u/86335040/DxDiag17.txt . When I left GNOME for about 30 minutes, the gnome-shell crashed once with Bus error in _st_theme_get_matched_properties() at st/st-theme.c:1000 . And I could not control GNOME Desktop . So I input <Ctrl>+<Alt>+F1, I logged in and sudo /sbin/shutdown -r 0 . And I found a core file . So I attatched a GDB backtrace file . And attached a screenshot . Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Login to GNOME Desktop . 2. Leave for about 30 minutes . Actual Results: The gnome-shell crashed once with Bus error in _st_theme_get_matched_properties() at st/st-theme.c:1000 . Expected Results: The gnome-shell should not crash . I also found a core file from /usr/lib/libproxy-0.4.11/pxgsettings generated after about 3 minutes . Although I do not understand in relation to this issue, I report once . -- 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 690493] New: gnome3: rebase g-s-d patches
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=690493 https://bugzilla.novell.com/show_bug.cgi?id=690493#c0 Summary: gnome3: rebase g-s-d patches Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- + We need to rebase: gnome-settings-daemon-system-proxy-configuration.diff gnome-settings-daemon-apport-monitor.patch gnome-settings-daemon-bnc462640-mute-action.patch gnome-settings-daemon-add-layout-switcher.patch gnome-packagekit-fate302445.patch gnome-packagekit-BNC383261.patch + gnome-patch-translation support was commented out until we rebased those patches. + Call to autoreconf was commented out for the same reason. Note that we can probably just drop gnome-settings-daemon-apport-monitor.patch. The two packagekit patches are covered in bug 689592. -- 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 816905] New: science/babel: undeclared conflict
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=816905 https://bugzilla.novell.com/show_bug.cgi?id=816905#c0 Summary: science/babel: undeclared conflict Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dmitry(a)roshchin.org ReportedBy: aeszter(a)gwdg.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: werner.ho(a)gmx.de Found By: --- Blocker: No The babel package includes /usr/bin/babel, as does the openbabel package from openSUSE standard repos. These packages are unrelated (openbabel is a chemistry package), and file conflicts are ignored by zypper (and yast), so an explicit conflict should be added to the .spec. If both babel and openbabel are installed, /usr/bin/babel may be from either package. If one of the packages is subsequently removed, /usr/bin/babel is missing. The 'Conflicts:' has been added in SR #149537. The SR was accepted, but the changes have subsequently been reverted for unknown reasons. -- 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 835984] New: Avahi can hang when registered with 40+ service files
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=835984 https://bugzilla.novell.com/show_bug.cgi?id=835984#c0 Summary: Avahi can hang when registered with 40+ service files Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: mgorse(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm filing this in the process of scanning for fixes that we have in SLED's GNOME stack but not in OpenSUSE: from the description in BNC#773989: Avahi daemon hangs and rises to 100% CPU utilization when tried to register with more than 40 service files(printer discovery service file). Works fine for the lower of service files. Steps to reproduce: - Create a printer discovery service file.(40 - 60 service files and more). - Try restarting the avahi-daemon using rcavahi-daemon command - Check the CPU utilization level for avahi -daemon. Also tried using the direct binary /usr/sbin/avahi-daemon which displays debug messages. It hangs after "Server startup" message and remains until it is killed forcibly. See also http://www.mail-archive.com/avahi@lists.freedesktop.org/msg01922.html (Ubuntu has also picked up the patch). -- 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 827630] New: openSUSE 12.3 will not boot with NSS-LDAP configured.
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=827630 https://bugzilla.novell.com/show_bug.cgi?id=827630#c0 Summary: openSUSE 12.3 will not boot with NSS-LDAP configured. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: david.westfall(a)red-inc.us QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux i686) Presto/2.12.388 Version/12.15 System has problems with NSS-LDAP. With nsswitch.conf is configured with hosts: files ldap dns. A getent hosts will return all hosts from the LDAP server. But will not resolve a host name. A ping and ssh HOSTNAME returns a failed hostname lookup. With nsswitch.conf configured for passwd and group to use ldap, getent passwd does not retrieve info from ldap. The major problem is the system will not boot when group and services are configured for ldap. Reproducible: Always Steps to Reproduce: 1.Configure nsswitch.conf to use ldap for user, group, and hosts. 2.Reboot 3. I did a zypper dup from 12.1 to 12.3 on two different computers. Both would not boot after update. Did a clean install of 12.3, did all updates. Both system worked until NSS-LDAP was configured. -- 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 786245] New: lxc container created with opensuse template doesn't start
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=786245 https://bugzilla.novell.com/show_bug.cgi?id=786245#c0 Summary: lxc container created with opensuse template doesn't start Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: londycircle(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 I tried creating a lxc container with the opensuse template and after it downloaded all the packages, I got these messages: initializing /var/cache/lxc/opensuse/partial-x86_64/.srcfiles.cache ... /usr/lib/build/createrpmdeps /var/cache/lxc/opensuse/partial-x86_64-packages/var/cache/zypp/packages/repo-oss/suse/x86_64 /usr/lib/build/createrpmdeps /var/cache/lxc/opensuse/partial-x86_64-packages/var/cache/zypp/packages/repo-oss/suse/noarch /usr/lib/build/createrpmdeps /var/cache/lxc/opensuse/partial-x86_64-packages/var/cache/zypp/packages/update/x86_64 /usr/lib/build/createrpmdeps /var/cache/lxc/opensuse/partial-x86_64-packages/var/cache/zypp/packages/update/noarch expanding package dependencies... Use of uninitialized value $spec in pattern match (m//) at /usr/lib/build/expanddeps line 69. /usr/lib/build/init_buildsystem: line 790: gettype: command not found binary not found: /var/cache/lxc/opensuse/partial-x86_64/.init_b_cache/rpms initializing rpm db... chroot: failed to run command ‘rpm’: No such file or directory chroot: failed to run command ‘/usr/bin/zypper’: No such file or directory chroot: failed to run command ‘/usr/bin/zypper’: No such file or directory chroot: failed to run command ‘rpm’: No such file or directory umount: /var/cache/lxc/opensuse/partial-x86_64/proc: not mounted Download complete. Copy /var/cache/lxc/opensuse/rootfs-x86_64 to /var/lib/lxc/test/rootfs ... Copying rootfs to /var/lib/lxc/test/rootfs .../usr/lib64/lxc/templates/lxc-opensuse: line 36: /var/lib/lxc/test/rootfs/etc/sysconfig/network/ifcfg-eth0: No such file or directory /usr/lib64/lxc/templates/lxc-opensuse: line 43: /var/lib/lxc/test/rootfs/etc/sysconfig/network/routes: No such file or directory /usr/lib64/lxc/templates/lxc-opensuse: line 78: /var/lib/lxc/test/rootfs/etc/sysconfig/cron: No such file or directory /usr/lib64/lxc/templates/lxc-opensuse: line 89: /var/lib/lxc/test/rootfs/etc/sysconfig/bootloader: No such file or directory /usr/lib64/lxc/templates/lxc-opensuse: line 116: /var/lib/lxc/test/rootfs/etc/sysconfig/boot: No such file or directory chroot: failed to run command ‘/sbin/insserv’: No such file or directory Please change root-password ! chroot: failed to run command ‘chpasswd’: No such file or directory 'opensuse' template installed 'test' created When I try to start it with "lxc-start -n test", I get these errors: lxc-start: No such file or directory - failed to mount 'sysfs' on '/usr/lib64/lxc/rootfs//sys' lxc-start: failed to setup the mounts for 'test' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'test' I tried using the ubuntu template and that one worked fine. 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 10

[Bug 815965] New: Can't install missing packages by YaST: Caught an unhandled exception: locale::facet::_S_create_c_locale name not valid
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=815965 https://bugzilla.novell.com/show_bug.cgi?id=815965#c0 Summary: Can't install missing packages by YaST: Caught an unhandled exception: locale::facet::_S_create_c_locale name not valid Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: lslezak(a)suse.com ReportedBy: locilka(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- Created an attachment (id=535833) --> (http://bugzilla.novell.com/attachment.cgi?id=535833) YaST Logs Run yast2-squid without having squid installed, you'll get: ┌───────────────────────────────────────────────────────┐ │ Installing required packages failed. If you continue │ │ without installing required packages, │ │ YaST may not work properly. │ │ │ │ [Continue] [Cancel] │ └───────────────────────────────────────────────────────┘ Caught an unhandled exception: locale::facet::_S_create_c_locale name not valid Package can be installed with `zypper in squid` Using yast2-pkg-bindings-2.23.1-1.1.1.x86_64 libzypp-12.9.0-1.1.1.x86_64 -- 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 803616] New: Network Interfaces Are Not Added To The Firewall External Zone By Default
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=803616 https://bugzilla.novell.com/show_bug.cgi?id=803616#c0 Summary: Network Interfaces Are Not Added To The Firewall External Zone By Default Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: PC OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: malv_star(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 Installing openSUSE 12.3 with KDE using manual configuration results in network interfaces not being added to the firewall's external, thus preventing features like remote SSH access from working by default. May be related to https://bugzilla.novell.com/show_bug.cgi?id=801374 Reproducible: Always Steps to Reproduce: 1. Install system and select "manual configuration" 2. Enable SSH during 1st phase of install (for example) 3. Attempt to access SSH server from remote machine Actual Results: External access is prevented regardless of chosen firewall policies since network interface is not assigned to external zone. Expected Results: Chosen policies are implemented and services are accessible. -- 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 22