June 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 825172] New: Booting live USB for 13.1M2 fails on a UEFI box (Copy-on-write problem?)
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825172 https://bugzilla.novell.com/show_bug.cgi?id=825172#c0 Summary: Booting live USB for 13.1M2 fails on a UEFI box (Copy-on-write problem?) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Live Medium AssignedTo: coolo(a)suse.com ReportedBy: nrickert(a)ameritech.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I prepared a USB with the live Gnome image for 13.1M2, using ImageWriter (from opensuse 12.3). I booted as a UEFI boot. The GUI never came up. On a retry, the USB was unbootable. It appears that a CoW partition was created, and creating it destroyed the boot structure on the USB. Full details are given in a forum post: https://forums.opensuse.org/english/get-technical-help-here/pre-release-bet… See comments 21 and 22. Note that "fdisk" output is given there. The CoW partition seems to have been placed where it overwrites the boot structure, instead of it being placed in the unused 2G of space at the end of the USB. I retested using the live KDE, this time written to the USB with "dd_rescue". The results were similar. It did not boot to a GUI, and the USB was unbootable afterwards. 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 5

[Bug 826157] New: osc mr diff is way too large due to linked packages
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=826157 https://bugzilla.novell.com/show_bug.cgi?id=826157#c0 Summary: osc mr diff is way too large due to linked packages Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: api AssignedTo: adrian(a)suse.com ReportedBy: meissner(a)suse.com QAContact: adrian(a)suse.com CC: abergmann(a)suse.com, bbrunner(a)suse.com Found By: --- Blocker: --- osc rq show -d 180413 shows some of the packages as "full diff". We occasionaly see that, mostly with linked packages. -- 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 776517] New: Widgets on screensaver do not allow resizing or setting of options
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=776517 https://bugzilla.novell.com/show_bug.cgi?id=776517#c0 Summary: Widgets on screensaver do not allow resizing or setting of options Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 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: suse(a)stanmiller.info QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 When you enable the option to allow widgets on the screensaver they appear as expected BUT the widgets do not have the pop-up edit sidebar that allows you to edit them or change the size of the widget. Reproducible: Always Steps to Reproduce: 1. Enable widgets on screensaver 2. Add a widget 3. Select the widget and no edit sidebar appears. Actual Results: You can get the widget menu with a right-click but you can't rezize the widget from there. Expected Results: A widget on the screensaver setup screen should have the same operation as the same widget on the 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 10

[Bug 803618] New: Remote Administration Component In Yast2 Does Not Open Firewall Ports When Selected
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=803618 https://bugzilla.novell.com/show_bug.cgi?id=803618#c0 Summary: Remote Administration Component In Yast2 Does Not Open Firewall Ports When Selected Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: PC OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 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 Using the Yast2 module "Remote Administration" allows users to permit access to the system via VNC, and also to open the relevant firewall ports. Ticking this option however, does not add the service "VNC Server" to the list of permitted services in the Yast2 module "Firewall". Instead, it must be added manually through the "Firewall" module. Reproducible: Always Steps to Reproduce: 1. Start YasT2's "Remote Administration" module. 2. Enable remote administration and tick the checkbox to open the relevant firewall ports. 3. Attempt to access machine remotely via VNC Actual Results: Connection times out as ports were never opened by firewall. Expected Results: VNC server connects and users can log in. After adding the permitted services manually, the VNC server asks the user for a password which does not appear to be the system's root password, nor the password for the current user. This appears to be new behaviour for 12.3, and it would be helpful to know if this is by design. Additionally, other bugs pertaining to network/firewall behaviour are recorded here: https://bugzilla.novell.com/show_bug.cgi?id=801374 https://bugzilla.novell.com/show_bug.cgi?id=803616 -- 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 12

[Bug 825998] New: package not found in specified repo (udev package in update repo) when zypper up
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825998 https://bugzilla.novell.com/show_bug.cgi?id=825998#c0 Summary: package not found in specified repo (udev package in update repo) when zypper up Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonysu(a)su-networking.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Not on all my machines, but one machine threw this error today, note although I'm checking "happens all the time" that's only the case with this one machine. Several other updates proceeded without the same error. zypper up File './x86_64/udev-195-13.11.1_13.25.1.x86_64.drpm' not found on medium http://download.opensuse.org/update/12.3/' Verified the file does not exist. Is referenced twice during the update(prob a dependency?), in both cases I just clicked "ignore" Hope my udev doesn't break :) This VM has not been updated for longer than the others. If it's helpful, 256 updates were downloaded while my other machines updated without error with 60 or fewer updates. Reproducible: Always Steps to Reproduce: 1. zypper up Actual Results: Error as described in "Details" Expected Results: I have clicked through (ignore the error). As I noted, for my specific situation, the VM is somewhat disposable and it remains to be seen how serious the bug is. So, for now am recommending a "Normal" severity but of course should be escalated if udev is truly broken and in a VM is exposed to relatively few "devices." -- 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 815506] New: LDAP user/group search bases not configured when using SSSD
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=815506 https://bugzilla.novell.com/show_bug.cgi?id=815506#c0 Summary: LDAP user/group search bases not configured when using SSSD Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: adaugherity(a)tamu.edu QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_3) AppleWebKit/536.28.10 (KHTML, like Gecko) Version/6.0.3 Safari/536.28.10 In previous YaST versions which supported nss_ldap (up through SLES 11 sp2 and openSUSE 12.1, apparently), it was possible for YaST to configure the user, group, and/or shadow search bases to a different value than the main LDAP search base. These options are no longer presented in YaST, despite SSSD supporting them (see ldap_user_search_base, ldap_group_search_base, etc. in sssd-ldap(5); there is no shadow search base option however). With an autoyast profile that configures these options, they *are* still applied when using nss_ldap (profile contains <sssd config:type="boolean">false</sssd>), but not when using SSSD. Because of this, it looks like this is a regression in the YaST LDAP module rather than autoyast. Reproducible: Always Steps to Reproduce: 1. Install with an autoyast profile configuring nss_base_group (etc.) under ldap. -OR- 1. Launch 'yast2 ldap'; choose "Advanced Configuration..." 2. Note the lack of "Naming Contexts" box containing User Map or Group Map. Actual Results: nss_base_group etc. settings in autoyast profile are ignored. YaST GUI for setting these is missing. Expected Results: Values should be mapped to sssd.conf settings: nss_base_passwd : ldap_user_search_base nss_base_group : ldap_group_search_base Applying the settings looks like a simple fix -- add a couple lines to WriteSSSDConfig() in modules/Ldap.ycp. Presenting the GUI may take a little more code, perhaps restoring some parts which were removed in 293b7ed. -- 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 12

[Bug 776516] New: Slideshow screensaver has very slow transitions with nouveau driver
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=776516 https://bugzilla.novell.com/show_bug.cgi?id=776516#c0 Summary: Slideshow screensaver has very slow transitions with nouveau driver Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 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: suse(a)stanmiller.info QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Compared to my 12.1 system with identical hardware several of the screen transitions run very slowly, some taking a couple minutes for the transition to complete. The worst ones are the small block replacement and the short line replacement transitions. Reproducible: Always Steps to Reproduce: 1. Enable slideshow screen saver 2. Pick a directory with a few pictures (size does not seem to matter) 3. Run in test mode or wait for the saver to kick in after your delay setting. 4. You will have to wait until the saver code picks one of the slow transitions but when it does the transition will run very slowly. Actual Results: Switching with the slow transitions takes a minute plus. Expected Results: Transition speeds similar to my 12.1 box, 2 to 5 seconds. -- 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 825956] New: Typo in default OBS appliance mysql config
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825956 https://bugzilla.novell.com/show_bug.cgi?id=825956#c0 Summary: Typo in default OBS appliance mysql config Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: BSipos(a)rkf-eng.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 In the OBS appliance version 2.4.2 disk image, there is an assumption in the init script /etc/init.d/obsapisetup that the MySQL config file /etc/my.cnf has a line matching the regexp "^datadir=.+" and this is passed to the shell "export" function to locate MySQL files. The appliance ships with a MySQL configuration with a line "datadir = /srv/obs/MySQL" which does not match the regexp and so the init script fails. This caused me a headache setting up the OBS appliance for the first time since the "out of the box" configuration was not being initialized properly. Reproducible: Always Steps to Reproduce: 1. Download and copy the OBS appliance image 2.4.2 2. Start the appliance per install instructions 3. Observe that every time the system boots it shows mysql errors and attempts to re-initialize the DB Actual Results: The appliance is never initialized properly. Expected Results: The appliance should bootstrap properly. -- 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 808144] New: systemd: disable fails to execute
by bugzilla_noreply＠novell.com 21 Jun '13

21 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=808144 https://bugzilla.novell.com/show_bug.cgi?id=808144#c0 Summary: systemd: disable fails to execute Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: fcrozat(a)suse.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- systemd-44-10.8.1.x86_64 is installed. Would be nice if it told us what file exactly it did not find. 19:10 nakamura:/etc/systemd/system # ls -l total 44 drwxr-xr-x 2 root root 4096 Jan 6 2012 basic.target.wants drwxr-xr-x 2 root root 4096 Mar 12 2011 default.target.wants drwxr-xr-x 2 root root 4096 Nov 9 08:34 getty.target.wants drwxr-xr-x 2 root root 4096 Feb 15 13:07 graphical.target.wants drwxr-xr-x 2 root root 4096 Feb 18 14:23 multi-user.target.wants drwxr-xr-x 2 root root 4096 Oct 22 2011 runlevel2.target.wants drwxr-xr-x 2 root root 4096 Sep 21 14:31 runlevel3.target.wants drwxr-xr-x 2 root root 4096 Sep 21 14:31 runlevel5.target.wants drwxr-xr-x 2 root root 4096 Mar 12 2011 sysinit.target.wants lrwxrwxrwx 1 root root 36 Mar 12 2011 default.target -> /lib/systemd/system/runlevel5.target lrwxrwxrwx 1 root root 9 Mar 6 17:25 klogd.service -> /dev/null -rw-r--r-- 1 root root 573 Mar 4 2012 systemd-random-seed-load.service lrwxrwxrwx 1 root root 50 Feb 15 13:07 teamviewerd.service -> /opt/teamviewer8/tv_bin/script/teamviewerd.service -rw-r--r-- 1 root root 163 Jul 9 2012 vpnc.service 19:10 nakamura:/etc/systemd/system # systemctl disable teamviewerd.service Failed to issue method call: No such file or directory -- 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 825815] New: home:ecsos: Bug
by bugzilla_noreply＠novell.com 20 Jun '13

20 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825815 https://bugzilla.novell.com/show_bug.cgi?id=825815#c0 Summary: home:ecsos: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Software Portal AssignedTo: ecsos(a)schirra.net ReportedBy: pat(a)indy.rr.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Other Blocker: Yes x86_64 gramps 4.0.0-28.1 openSUSE Tumbleweed fails with: 20:31 Crash: ~ > gramps ResourcePath.ERROR: Resource Path /usr/share is invalid and 4.0.0-29.1 fails with: 20:33 Crash: ~ > gramps No handlers could be found for logger "grampslocale" Traceback (most recent call last): File "/usr/bin/gramps", line 2, in <module> import gramps.grampsapp as app File "/usr/lib/python2.7/site-packages/gramps/grampsapp.py", line 54, in <module> from .gen.const import APP_GRAMPS, USER_DIRLIST, HOME_DIR File "/usr/lib/python2.7/site-packages/gramps/gen/const.py", line 197, in <module> GRAMPS_LOCALE = GrampsLocale(localedir=_resources.locale_dir) File "/usr/lib/python2.7/site-packages/gramps/gen/utils/grampslocale.py", line 541, in __init__ self.language) File "/usr/lib/python2.7/site-packages/gramps/gen/utils/grampslocale.py", line 573, in _get_translation if gettext.find(domain, localedir, [lang]): File "/usr/lib64/python2.7/gettext.py", line 426, in find if len(bundle): TypeError: object of type 'NoneType' has no len() -- 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