December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 700416] New: click in scroll area causes more than one page advance or retard
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=700416 https://bugzilla.novell.com/show_bug.cgi?id=700416#c0 Summary: click in scroll area causes more than one page advance or retard Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86 OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: jsrain(a)novell.com Found By: --- Blocker: --- To reproduce: 1-Select package details 2-select e.g. summary or search that produces a lot of pages of right pane output 3-click space above or below scroll grabber/button Actual results: 1-usually, a single pgdn or pgup is painted, then another (sometimes not, assuming more than one is possible) Expected results: 1-only one page up or down occurs (always, if more than one is even possible) This has actually been going on for quite some weeks, maybe months dating back to pre-11.4GM, and occurs AFAIR on every mouse/trackball/computer I try with, though mostly I use PS/2 devices rather than USB, and all my systems are pre-multicore. My most used pointing device is a Trackman Marble. -- 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 35

[Bug 618068] New: ssh DISPLAY not set unless /etc/sshd/sshd_config `X11UseLocalhost no' set
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

http://bugzilla.novell.com/show_bug.cgi?id=618068 http://bugzilla.novell.com/show_bug.cgi?id=618068#c0 Summary: ssh DISPLAY not set unless /etc/sshd/sshd_config `X11UseLocalhost no' set Classification: openSUSE Product: openSUSE 11.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pablo(a)blueoakdb.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.4) Gecko/20100611 SUSE/3.6.4-6.1 Firefox/3.6.4 Howdy, ssh'ing from `openSUSE 11.1' to `openSUSE 11.3 RC1' results in the DISPLAY shell variable not being set with a stock `/etc/sshd/sshd_config' file. The work-around is to set in `/etc/sshd/sshd_config', `X11UseLocalhost no' The solution was found by googling around. Note: I'm not sure whether I should set the severity to `Normal' or `Major' As I mentioned above, I was able to come up with a work-around but I'm not sure whether enough people will google for a solution. You'd think a savvy enough SysAdmin would ... In order to help others in searching for this bug, I'll also include `/var/log/messages' entries found during `ssh'ing without the above setting: sshd[5538]: error: Failed to allocate internet-domain X11 display socket. Below are the `sshd' configuration values for the two machines: `openSUSE 11.3 RC1' =================== ROOT-root@zoom-37-[/root]: grep -v '^#' /etc/ssh/sshd_config | grep -v '^[ ]*$' PasswordAuthentication no UsePAM yes X11Forwarding yes X11UseLocalhost no Subsystem sftp /usr/lib/ssh/sftp-server AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT AcceptEnv LC_IDENTIFICATION LC_ALL `openSUSE 11.1' =============== ROOT-root@oreo-1011-[/root]: grep -v '^#' /etc/ssh/sshd_config | grep -v '^[ ]*$' Protocol 2 PasswordAuthentication no UsePAM yes X11Forwarding yes Subsystem sftp /usr/lib/ssh/sftp-server AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT AcceptEnv LC_IDENTIFICATION LC_ALL Reproducible: Always Steps to Reproduce: 1. Using stock '/etc/ssh/sshd_config', `ssh -Y' from `openSUSE 11.1' to `openSUSE 11.3 RC1' Note, it's possible to use `ssh -X' with the same result. 2. Type `xclock' to test whether DISPLAY is set correctly. Actual Results: As DISPLAY is not set in the shell, you cannot remotely view the X application. Expected Results: The X application should display correctly on the remote node. -- 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 30

[Bug 855164] New: VNSTATD does not start - INIT-Script Error
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855164 https://bugzilla.novell.com/show_bug.cgi?id=855164#c0 Summary: VNSTATD does not start - INIT-Script Error Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: linreg(a)gmx.net 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/31.0.1650.63 Safari/537.36 vnstatd oes not start. After the Version 1.11 the parameter -u for a User-account will not be supported. The INIT-Script must be changed. Reproducible: Always Steps to Reproduce: 1. Install vnstat 2. start vnstat with systemctl or rcvnstatd 3. See the daemon status. It will be not started Actual Results: vnstatd does not run/start Expected Results: vnstatd should be start Solution for this: # Create a PID File touch /var/run/vnstatd.pid chown vnstat:vnstat /var/run/vnstatd.pid # Chnage INIT-Script /etc/init.d/vnstatd: Replace line 49: "$VNSTATD_BIN" -d -p "$VNSTATD_PIDFILE" -u "$VNSTATD_USER" With: /sbin/startproc -u "$VNSTATD_USER" "$VNSTATD_BIN" -d -p "$VNSTATD_PIDFILE" AND rm /etc/cron.d/vnstat (Please) -- 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 846945] New: open-iscsi should be updated to start when needed using systemd
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=846945 https://bugzilla.novell.com/show_bug.cgi?id=846945#c0 Summary: open-iscsi should be updated to start when needed using systemd Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: lduncan(a)suse.com ReportedBy: lduncan(a)suse.com QAContact: qa-bugs(a)suse.de CC: hare(a)suse.com, meissner(a)suse.com, werner(a)suse.com, michaelc(a)cs.wisc.edu, fcrozat(a)suse.com, fxzhang(a)suse.com Depends on: 821695,827654 Found By: Development Blocker: --- +++ This bug was initially created as a clone of Bug #827654 +++ +++ This bug was initially created as a clone of Bug #821695 +++ Now that open-iscsi has been integrated with systemd in openSUSE, it now has reduced functionality compared with earlier versions, a clear regression. The open-iscsi service used to be installed, when based on system V init, as enabled. As part of the integration process with systemd, open-iscsi has been modified so that it is now socket activated. This means that, in conjunction with systemd, the iscsi service need not be enabled as long as the iscsid.socket *is* enabled. If this base-level socket is enabled then systemd takes care of starting the iscsid service (and accompanying daemon) when needed. This means that if no iscsid service is being used that the iscsid daemon is never started. This is why the iscsid.socket service should be enabled by default. In addition, the new open-iscsi/systemd integration means that higher-level iscsi services, such as logging into (or out of) targets, thus establishing sessions, is now layered as an additional service on top of the iscsid.service. This new top-level service is called iscsi.service, and only worries about logging into targets if (and only if) the user has those targets in their iSCSI database as needing to be connect at boot time. This new iscsi.service service has no associated daemon, and will only activate the iscsi.service iscsid daemon if needed. Again, no load on the end-user's system. And I would argue that if the user has iscsi nodes in their database that are listed as needing to be connect "onboot", that we had better have that service enabled, or the user is not going to have a good boot experience. Again, the systemd units iscsid.socket and iscsi.service need to be enabled by default. -- 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 11

[Bug 762098] New: mpt-firmware has broken udvev rule
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=762098 https://bugzilla.novell.com/show_bug.cgi?id=762098#c0 Summary: mpt-firmware has broken udvev rule Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: hare(a)suse.com ReportedBy: aj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- >From /var/log/messages: May 14 14:38:19 hp-Mini udevd[234]: unknown key 'RUN{ignore_error}' in /etc/udev/rules.d/81-mptctl.rules:4 May 14 14:38:19 hp-Mini udevd[234]: invalid rule '/etc/udev/rules.d/81-mptctl.rules:4' -- 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 11

[Bug 133718] memory allocation hangs during DVD-RAM writing
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=133718 https://bugzilla.novell.com/show_bug.cgi?id=133718#c37 --- Comment #37 from Stanislav Brabec <sbrabec(a)suse.com> 2013-12-12 19:52:25 CET --- I will test it. My current settings (openSUSE 13.1): # cat /proc/sys/vm/dirty_ratio 20 # cat /proc/sys/vm/dirty_bytes 0 # cat /proc/sys/vm/dirty_background_bytes 0 My work-around preventing hangs was: while : ; do echo 3 >/proc/sys/vm/drop_caches ; sleep 30 ; done -- 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 801862] New: synaptics touchpad "disable touchpad while typing" option does not work
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=801862 https://bugzilla.novell.com/show_bug.cgi?id=801862#c0 Summary: synaptics touchpad "disable touchpad while typing" option does not work Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: hendersj(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is similar to bug 748332, but for GNOME3 (and the suggested fix does not apply in GNOME). I have a Dell R17 N7110 laptop, and the touchpad is detected (two-finger scrolling works, as does edge scrolling if that is enabled). The option to disable the touchpad while typing, however, does not. Let me know what info is needed to further diagnose this issue, and I'll be happy to provide 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 5

[Bug 830465] New: KDE Dolphin fish protocol does not work
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=830465 https://bugzilla.novell.com/show_bug.cgi?id=830465#c0 Summary: KDE Dolphin fish protocol does not work Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: i686 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: hendrikw(a)arcor.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=548755) --> (http://bugzilla.novell.com/attachment.cgi?id=548755) sshd logfile in DEBUG3 mode of an unsuccessful fish-login attempt User-Agent: Mozilla/5.0 (X11; Linux i686; rv:22.0) Gecko/20100101 Firefox/22.0 Connecting to a ssh-server with Dolphin using the fish protocol does not work. Dolphin asks for username and password and tries to connect, but with no success. Reproducible: Always Steps to Reproduce: 1. enter a fish-address in the Dolphin-address-line 2. enter username and password 3. Actual Results: the connection does not get established Expected Results: the connection should succeed Using the fish protocol works at the same hardware in openSUSE 12.3 + Tumbleweed. -- 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 854916] New: openSUSE:12.3/libapr1: Bug
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=854916 https://bugzilla.novell.com/show_bug.cgi?id=854916#c0 Summary: openSUSE:12.3/libapr1: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: draht(a)suse.com ReportedBy: urs.beyerle(a)env.ethz.ch QAContact: adrian(a)suse.com Found By: --- Blocker: --- libarp1 is compiled with -fvisibility=hidden. As a result some symbols are not included in libapr-1.so.0.4.8. For example ganglia needs libganglia.so: undefined reference to `apr_sockaddr_vars_set' libganglia.so: undefined reference to `apr_inet_ntop' compiling without -fvisibility=hidden solves the problem. # nm -D /usr/lib64/libapr-1.so.0.4.8 | grep apr_inet_ntop 000000000001c900 T apr_inet_ntop nm -D /usr/lib64/libapr-1.so.0.4.8 | grep apr_sockaddr_vars_set 000000000001ddc0 T apr_sockaddr_vars_set Please see https://build.opensuse.org/project/show/home:beyerle:Ganglia Why was -fvisibility=hidden introduced in openSUSE 13.1? It's not there in openSUSE 12.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 12

[Bug 854940] New: Some GTK applications miss icons when using Oxygen icon theme under KDE
by bugzilla_noreply＠novell.com 12 Dec '13

12 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=854940 https://bugzilla.novell.com/show_bug.cgi?id=854940#c0 Summary: Some GTK applications miss icons when using Oxygen icon theme under KDE Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: robert.munteanu(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=571325) --> (http://bugzilla.novell.com/attachment.cgi?id=571325) Screenshot of kde gtk styles User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 When starting GTK apps under KDE, like gedit or evolution, some icons are painted as a red 'forbidden' icon. KDE is configured to use the Oxygen icon theme and fallback to gnome. There seem to be two problems here: 1. The Oxygen icon theme is incomplete 2. There is no fallback to the Gnome icon theme When I set Gnome as the icon theme and Oxygen as the fallback, there are no missing icons. The terminal output when starting gedit is ** (gedit:25221): WARNING **: Could not load theme icon user-bookmarks-symbolic: Icon 'user-bookmarks-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon user-home-symbolic: Icon 'user-home-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon drive-harddisk-symbolic: Icon 'drive-harddisk-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon folder-symbolic: Icon 'folder-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon folder-symbolic: Icon 'folder-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon folder-symbolic: Icon 'folder-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon folder-symbolic: Icon 'folder-symbolic' not present in theme ** (gedit:25221): WARNING **: Could not load theme icon folder-symbolic: Icon 'folder-symbolic' not present in theme This looks related to bug #851523, but I'm not sure it's a dupe. 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 3