December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 794676] New: update Apache Subversion to 1.7.8 maintenance release
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=794676 https://bugzilla.novell.com/show_bug.cgi?id=794676#c0 Summary: update Apache Subversion to 1.7.8 maintenance release Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 Maintenance release for Apache Subversion planned for 2012-12-17 See http://svn.apache.org/repos/asf/subversion/tags/1.7.8/CHANGES Maintenance requests are comming up. Reproducible: Always Steps to Reproduce: 1. svn --version Actual Results: svn, version 1.7.7 (r1393599) Expected Results: svn, version 1.7.8 (r1419691) -- 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 788015] New: update Apache Subversion to 1.7.7 maintenance release
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=788015 https://bugzilla.novell.com/show_bug.cgi?id=788015#c0 Summary: update Apache Subversion to 1.7.7 maintenance release Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 Upstream maintenance releases 1.7.6 and 1.7.7 https://svn.apache.org/repos/asf/subversion/tags/1.7.7/CHANGES Reproducible: Always Steps to Reproduce: 1. svn --version Actual Results: svn, version 1.7.5 Expected Results: svn, version 1.7.7 -- 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 713919] New: devel:tools:scm:svn/subversion: Bug
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=713919 https://bugzilla.novell.com/show_bug.cgi?id=713919#c0 Summary: devel:tools:scm:svn/subversion: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: i686 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: dmueller(a)suse.com ReportedBy: Stefan.von.Dombrowski(a)dlr.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: pascal.bleser(a)opensuse.org Found By: Customer Blocker: No Somewhere between subversion-1.6.17-32.1 and subversion-1.6.17-51.1 the source package configuration has been changed in a way that leads to SLE11 binaries being built without support for kwallet and gnome-keyring. Instead of #%define with_ruby 0%{?suse_version} > 1110 #%define with_intree_swig 0%{?suse_version} != 1110 #%if 0%{?always_use_intree_sqlite} #%define with_intree_sqlite 1 #%define with_python_ctypes 0%{?suse_version} > 1110 #%else #%define with_intree_sqlite 0%{?suse_version} < 1110 #%define with_python_ctypes 0 #%endif #%define with_kde4_kwallet 0%{?suse_version} > 1110 #%define with_gnome_keyring 0%{?suse_version} > 1110 I needed to define %define with_ruby 1 %define with_intree_swig 1 %define with_intree_sqlite 1 %define with_python_ctypes 0 %define with_kde4_kwallet 1 %define with_gnome_keyring 1 to make build for SLE11 SP1 work as before. In -32.1 the definitions were %if 0%{?sles_version} == 9 %define __python %{_usr}/bin/python2.5 %endif %if 0%{?sles_version} == 9 %define with_ruby 0 %define with_python_ctypes 0 %else %define with_ruby 1 %define with_python_ctypes 0 %endif %define with_intree_sqlite 1 %if 0%{?suse_version} > 1010 %define with_gnome_keyring 1 %else %define with_gnome_keyring 0 %endif # suse_version > 1010 %if 0%{?suse_version} > 1030 %define with_kde4_kwallet 1 %else %define with_kde4_kwallet 0 %endif # suse_version > 1030 Could the current defines please be changed so that SLE11 SP1 subversion packages are built with wallet/keyring support again? -- 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 855355] New: gnome-terminal launched by ssh -X won't open X application
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855355 https://bugzilla.novell.com/show_bug.cgi?id=855355#c0 Summary: gnome-terminal launched by ssh -X won't open X application Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: nopower(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- launching a remote gnome-terminal via ssh -X works fine, the problem is when trying to run an X application from the newly launched gnome-terminal it fails e.g. ssh -X user@remote gnome-terminal and then typing xterm (or any X app) results in xterm: Xt error: Can't open display: localhost:10.0 however ssh -X user@remote and subsequent attempts to run x applications ( xterm, gnome-terminal etc. ) all work as expected :/ problem exhibits itself on remote when remote is 13.1 ( it doesn't matter what version the client machine the ssh -X is launched from ) -- 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 855050] New: iasl option -p with path containing dot mishandled
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855050 https://bugzilla.novell.com/show_bug.cgi?id=855050#c0 Summary: iasl option -p with path containing dot mishandled Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: trenn(a)suse.com ReportedBy: brogers(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- In preparing the latest qemu package, I ran into a bug with iasl compiler (provided by acpica package), which has just been fixed upstream. We currently are having to work around this bug with a kludgey patch in qemu. Could you please consider either including the commit from the acpica git repo, commit id: 04d10e3c1f41a776cbed96dce2326ee649b9a0f0 or the December release of acpica (coming out soon), so that we don't have to work around this deficiency. Thanks!. -- 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 854522] New: Kernel trace non obvious cause
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=854522 https://bugzilla.novell.com/show_bug.cgi?id=854522#c0 Summary: Kernel trace non obvious cause Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=570898) --> (http://bugzilla.novell.com/attachment.cgi?id=570898) picture of kernel trace The attached picture shows the kernel trace. Sorry, I had to take a picture as neither the network nor US are working on the machine at the moment. This is brand new hardware; Gigabyte 990FXA-UD5 Mother board AMD FX-8350 8 Core CPU 32 GB memory -- 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 854559] New: USB connectivity is not working properly
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=854559 https://bugzilla.novell.com/show_bug.cgi?id=854559#c0 Summary: USB connectivity is not working properly Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=570923) --> (http://bugzilla.novell.com/attachment.cgi?id=570923) message on USB stick connect to a USB2 port Upon connection of a stick to a USB2 port the following is diaplayed: "usb 1-5: new highspeed USB device number 2 using ehci-pci" immediately followed by: " usb 1-5: device descriptor read/64, error -32" The error is printed twice to the log. This is followed by arn through device numbers, i.e. "usb 1-5: new highspeed USB device number 3 using ehci-pci" etc. See the attached pictures for information. Sorry about the picture, the network on this machine is not working either (filed a separate bug). The hardware is brand new: Gigabyte 990FXA-UD5 mother board AMD FX-8350 8 Core CPU When running lsusb, the operation takes much longer than expected (a few minutes) and messages as follows appear in the system log: usb 11-4: new full-speed USB device number 14 using ohci-pci usb 11-4: device descriptor read/64, error -110 Interestingly enough during installation the USB stick I used to install openSUSE 13.1 was recognized just fine. Only after the reboot does the USB stuff appear to "loose it's mind". Also the USB webcam light is on all the time. Mouse and keyboard work, these are both connected via a 2 into one ps2 to usb converter. But they only work when connected to a USB3 port. -- 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 19

[Bug 855115] New: Shutdown not effectuated with multiusersystem and secure file settings (laptop with ultrabase dockingstation)
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855115 https://bugzilla.novell.com/show_bug.cgi?id=855115#c0 Summary: Shutdown not effectuated with multiusersystem and secure file settings (laptop with ultrabase dockingstation) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: stakanov(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 I haven't tried this yet for repeatability without dockingstation but with the Lenovo X201 and ultrabase dockingstation this is repeatable and stable. Run a sistem with Lenovo X201, ultrabase and two monitors attached (hdmi and vga). Use "secure" file permissions. Open several terminal sessions for different users. Now shutdown the system from a terminal that is not the first one that you did open. The system asks for root password, you give it, it will apparently shutdown. But it isn't. The screen remains with a little dash blinking high right (like the system would have crashed. But it didn't crash). The monitor hdmi after a while will begin to "flush" in regular time frames and give a bob sound over the speakers. This stays a whole night, by this also making the material suffer. In one night the monitor will switch on and of a few hundred times. If you switch the system off with the power button (will ask correctly for root password) it will shutdown normally. If you switch to the first videoterminal you did open, (with the combination ctrl + alt + F7 which is set normally as the first terminal to open) then the system will proceed correctly to normal shutdown without further intervention. Reproducible: Always Steps to Reproduce: 1.open several video terminals of several users in a system with secure file permissions 2.close the system (shutdown) with root password from any but the original VT 3. system hangs on shutdown Actual Results: system does not shutdown, monitor switches on and off in an ultrabase Expected Results: well, it shut shutdown I guess. Bug 853116 - suse does not shutdown This could be a duplicate but as the original poster did not give any details I cannot now. I set this to normal. I will check if in such situation the encrypted LVM will stay open. In this case this would be also severe from a security point of view. But I have the hope that it isn't the case.Currently I am just afraid for the material when it happens, because you just may not notice it. Imagine you go into a weekend and the thingy is flushing on and off you monitor up to planned obsolescence. -- 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 855288] New: kiwi: fails Creating hybrid persistent partition for COW data
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855288 https://bugzilla.novell.com/show_bug.cgi?id=855288#c0 Summary: kiwi: fails Creating hybrid persistent partition for COW data Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: cyberorg(a)opensuse.org QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 Here is the relevant snippet of the log: kiwi is looking for "/dev/loo" which it of course cannot find, sed magic gone wrong. Full log is attached. ++ losetup -f --show /isofrom//openSUSE-Edu-li-f-e.i686-13.1.1.iso + biosBootDevice=/dev/loop0 + '[' '!' 0 = 0 ']' + return 0 + '[' '!' -z '' ']' + '[' '!' -z yes ']' + setupHybridPersistent + '[' '!' yes = yes ']' ++ dn /dev/loop0 +++ getDiskDevice /dev/loop0 ++++ readlink /dev/loop0 +++ local device= +++ '[' -z '' ']' +++ echo /dev/loop0 +++ return ++ local part=/dev/loop0 +++ echo /dev/loop0 +++ sed -e 's@$^.*$$p[0-9].*$$@\1@' ++ local part_new=/dev/loo ++ '[' /dev/loop0 = /dev/loo ']' ++ echo /dev/loo + local diskDevice=/dev/loo 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 2

[Bug 855221] New: libzypp or zypper should take Inhibitor Locks when installing packages
by bugzilla_noreply＠novell.com 13 Dec '13

13 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855221 https://bugzilla.novell.com/show_bug.cgi?id=855221#c0 Summary: libzypp or zypper should take Inhibitor Locks when installing packages Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: crrodriguez(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi: A while ago, I foolishly rebooted the system in the middle of a "dup" and that didn't end well, it turns out mess ups of this type can be prevented by taking an Inhibitor Lock[1] during package installation. I suggest adding an API to libzypp that can be used by zypper or YaST to take such locks at the beginning of the package *installation* sequence (not the downloading part) and released once all packages in the transaction are installed. [1]http://www.freedesktop.org/wiki/Software/systemd/inhibit/ -- 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