November 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 665073] Zypper does not report complete package name in error message if the name includes hyphen
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.suse.com/show_bug.cgi?id=665073 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902767] YaST Proxy "test proxy settings" error when functioning normally
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902767 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Martin Vidner <mvidner(a)suse.com> --- Thanks for the report. It is already fixed for 13.2. *** This bug has been marked as a duplicate of bug 853725 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903582] net-udev rules no longer applied in 13.2
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=903582 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bos(a)je-eigen-domein.nl, | |schubi(a)suse.com Flags| |needinfo?(bos@je-eigen-dome | |in.nl) --- Comment #1 from Stefan Schubert <schubi(a)suse.com> --- Please add the logfiles and your autoinst.xml file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902086] Autoyast Stage2 segfaults when using add-on section
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902086 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #12 from Stefan Schubert <schubi(a)suse.com> --- Fixed in https://github.com/yast/yast-installation/pull/242 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 866692] New: YaST sw_single (QT) crash
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

https://bugzilla.novell.com/show_bug.cgi?id=866692 https://bugzilla.novell.com/show_bug.cgi?id=866692#c0 Summary: YaST sw_single (QT) crash Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: wbauer(a)tmo.at QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=580839) --> (http://bugzilla.novell.com/attachment.cgi?id=580839) y2log after the crash (the old one was deleted before starting YaST) User-Agent: Mozilla/5.0 (X11; Linux) KHTML/4.12.2 (like Gecko) Konqueror/4.12 SUSE This is on a fresh Factory 32bit installation (inside VMWare). When trying to install packages, YaST Software Management just crashes with: YaST got signal 11 at YCP file /usr/share/YaST2/modules/SlideShow.rb:385 /sbin/yast2: line 429: 2825 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Attached is the y2log. Reproducible: Always Steps to Reproduce: 1. Enter YaST->Software Management 2. Select a package to install 3. Click on "Accept" Actual Results: YaST crashes Expected Results: YaST should install the package(s). Please note that this was without libqdialogsolver1 installed, so it is not related to bug#866622. -- 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 48

[Bug 898395] Inserting USB2.0 device (0400:080a) triggers error
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=898395 --- Comment #35 from Takashi Iwai <tiwai(a)suse.com> --- I guess the reporter tries to compile from SUSE kernel git tree. It's different from the upstream Linux kernel git tree. SUSE kernel git contains only SUSE-specific patches, and doesn't contain the base kernel source itself. There is an expanded SUSE kernel tree that contains the whole Linus kernel tree, too. You may use this tree, or just use Linus tree instead. FYI, the Linus tree is found at git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git Also, you can create a minimal kernel config matching for the running system via "make localmodconfig". That is, 1. boot the working SUSE 3.8 kernel 2. Confirm BT is working there 3. On the Linus git tree: % git checkout v3.8 % make localmodconfig Then edit .config file, especially better to modify CONFIG_LOCALVERSION to something unique, e.g. "-test". 4. Build, install and test. After confirming this self-made 3.8 kernel works, save your .config file once. Then do "git checkout v3.9", and "make localconfig", press many RETURN keys until all satisfied, build, install and retest 3.9 kernel. Once when confirming this 3.9 kernel is really broken, you can start bisection there. Save .config file for 3.9 kernel as well. Then do "git bisect start", "git bisect good v3.8", "git bisect bad v3.9". You may need to copy the backup .config either from 3.8 or 3.9 during bisection. Have fun :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902052] Another bug for testing, please, do not close
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=902052 Neil Rickert <nrickert(a)ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert(a)ameritech.net --- Comment #2 from Neil Rickert <nrickert(a)ameritech.net> --- I'll comment on this here, because it is not obvious where to report bugzilla bugs. As I read this bug report on bugzilla, I cannot see anything except the identity of the reporter. I presume that this bug has been marked private, which is why I cannot see it. However, I was able to read the reports on the opensuse-bugs mailing list archives. It seems to me that this is a potential security problem, if bugs that are marked as private are still sent to the mailing list (with more in the mail message than just the bug title). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 898395] Inserting USB2.0 device (0400:080a) triggers error
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=898395 Bit Juggler <suse.junky(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(suse.junky@t-onli | |ne.de) | --- Comment #34 from Bit Juggler <suse.junky(a)t-online.de> --- user@MACHINE:~/kernel-source> git tag rpm-2.6.22.5-31 rpm-2.6.22.9-0.4 rpm-2.6.25.5-1.1 rpm-2.6.30-8 rpm-2.6.30.2-1 rpm-2.6.31-1 rpm-2.6.31-10 rpm-2.6.31-3 rpm-2.6.31-7 rpm-2.6.31.3-1 rpm-2.6.32-0.1 rpm-2.6.32-0.4 rpm-2.6.32-0.6 rpm-2.6.32-0.6.8 rpm-2.6.32-3 rpm-2.6.32.10-0.4 rpm-2.6.32.11-0.3 rpm-2.6.32.12-0.2 rpm-2.6.32.12-0.3 rpm-2.6.32.12-0.7 rpm-2.6.32.13-0.4 rpm-2.6.32.13-0.5 rpm-2.6.32.19-0.2 rpm-2.6.32.19-0.3 rpm-2.6.32.23-0.3 rpm-2.6.32.24-0.2 rpm-2.6.32.27-0.2 rpm-2.6.32.29-0.3 rpm-2.6.32.3-0.3 rpm-2.6.32.3-0.5 rpm-2.6.32.36-0.5 rpm-2.6.32.41-0.5 rpm-2.6.32.42-0.11 rpm-2.6.32.42-0.7 rpm-2.6.32.43-0.13 rpm-2.6.32.43-0.4 rpm-2.6.32.43-0.7 rpm-2.6.32.43-0.9 rpm-2.6.32.44-0.7 rpm-2.6.32.45-0.3 rpm-2.6.32.5-0.1 rpm-2.6.32.7-0.2 rpm-2.6.32.8-0.3 rpm-2.6.32.9-0.5 rpm-2.6.33-3 rpm-2.6.33-5 rpm-2.6.33-6 rpm-2.6.34-12 rpm-2.6.34-3 rpm-2.6.34-6 rpm-2.6.34-8 rpm-2.6.34-9 rpm-2.6.36-16 rpm-2.6.36-18 rpm-2.6.37-12 rpm-2.6.37-20 rpm-2.6.37-6 rpm-2.6.37.1-1.2 rpm-3.0.0-4 rpm-3.0.10-0.7 rpm-3.0.101-0.15 rpm-3.0.101-0.18 rpm-3.0.101-0.21 rpm-3.0.101-0.29 rpm-3.0.101-0.31 rpm-3.0.101-0.35 rpm-3.0.101-0.40 rpm-3.0.101-0.5 rpm-3.0.101-0.7.15 rpm-3.0.101-0.8 rpm-3.0.13-0.23 rpm-3.0.13-0.27 rpm-3.0.13-0.5 rpm-3.0.13-0.9 rpm-3.0.26-0.7 rpm-3.0.31-0.9 rpm-3.0.34-0.7 rpm-3.0.38-0.5 rpm-3.0.4-0.11 rpm-3.0.4-0.13 rpm-3.0.4-0.23 rpm-3.0.42-0.7 rpm-3.0.51-0.10 rpm-3.0.51-0.7.9 rpm-3.0.53-0.7 rpm-3.0.58-0.6.2 rpm-3.0.58-0.6.6 rpm-3.0.58-0.9 rpm-3.0.6-0.7 rpm-3.0.61-0.9 rpm-3.0.65-0.9 rpm-3.0.68-0.9 rpm-3.0.7-0.7 rpm-3.0.70-0.7 rpm-3.0.70-0.9 rpm-3.0.74-0.6.10 rpm-3.0.74-0.6.6 rpm-3.0.74-0.6.8 rpm-3.0.74-0.9 rpm-3.0.76-0.11 rpm-3.0.76-0.7 rpm-3.0.8-0.11 rpm-3.0.8-0.9 rpm-3.0.80-0.5 rpm-3.0.80-0.7 rpm-3.0.82-0.7 rpm-3.0.93-0.5 rpm-3.0.93-0.8 rpm-3.1.0-1.1 rpm-3.1.0-1.2 rpm-3.1.rc7-3 rpm-3.1.rc9-1 rpm-3.10.0-2.3.gc5ad3f9 rpm-3.10.1-3.5.g0cd5432 rpm-3.10.rc4-1 rpm-3.11.1-1.2.g1383321 rpm-3.11.3-1 rpm-3.11.6-3 rpm-3.11.6-4 rpm-3.12.10-2 rpm-3.12.12-3 rpm-3.12.14-1 rpm-3.12.15-3 rpm-3.12.17-2 rpm-3.12.18-3 rpm-3.12.18-4 rpm-3.12.18-5 rpm-3.12.20-1 rpm-3.12.21-2 rpm-3.12.22-2 rpm-3.12.24-7 rpm-3.12.25-2 rpm-3.12.26-3 rpm-3.12.27-2 rpm-3.12.28-2 rpm-3.12.28-4 rpm-3.12.3-2 rpm-3.12.7-1 rpm-3.12.9-1 rpm-3.16.2-1.1.gdcee397 rpm-3.16.3-1.4.gd2bbe7f rpm-3.2.0-2 rpm-3.3.0-2 rpm-3.3.rc6-1 rpm-3.4.0-2 rpm-3.4.2-1 rpm-3.4.4-1.1 rpm-3.6.3-1 rpm-3.7.1-1 rpm-3.7.10-1.1 rpm-3.7.6-1.2 rpm-3.7.9-1.1 rpm-3.9.0-1 user@MACHINE:~/kernel-source> -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902550] systemd is leaking msgs to yast2-ncursers interface
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902550 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |idonmez(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 902550] systemd is leaking msgs to yast2-ncursers interface
by bugzilla_noreply＠novell.com 03 Nov '14

03 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=902550 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #4 from Stefan Schubert <schubi(a)suse.com> --- Hm, plymouth and systemd are not working quite well here. The other point is that we do not have control about the output of your defined script: [ -f /tmp/patch_me ] && source /tmp/patch_me # for INT in $(find /sys/class/net/ -type l -not -name lo -printf '%f\n'); do dhcpcd -H $INT -t 15 & done wait if [ "$VAL" ]; then systemctl enable winbind && yast2 samba-client joindomain domain="redetresc.tre-sc.gov.br" user="join" password="$VAL" && systemctl start winbind else true fi because it will be called at once. Another place for would be the autoyast init_script which would encapsulate the calls in an own service. Or you ensure that no console output will be generated while calling the script. So I fear that we cannot do much here. I have added the plymouth maintainer. Perhaps he has another solution/opinion for. -- You are receiving this mail because: You are on the CC list for the bug.

1 0