October 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 843304] New: wireshark build fails with compiler error
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=843304 https://bugzilla.novell.com/show_bug.cgi?id=843304#c0 Summary: wireshark build fails with compiler error Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network 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:24.0) Gecko/20100101 Firefox/24.0 Wireshark fails to build in 13.1 and Factory: [ 257s] In file included from /usr/include/glib-2.0/glib/gdir.h:34:0, [ 257s] from /usr/include/glib-2.0/glib.h:47, [ 257s] from packet-gluster_cli.c:38: [ 257s] packet-gluster.h:359:2: error: redeclaration of enumerator 'DT_UNKNOWN' [ 257s] DT_UNKNOWN = 0, [ 257s] ^ [ 257s] /usr/include/dirent.h:99:5: note: previous definition of 'DT_UNKNOWN' was here [ 257s] DT_UNKNOWN = 0, [ 257s] ^ Upstream commits: http://anonsvn.wireshark.org/viewvc?view=revision&revision=52142 http://anonsvn.wireshark.org/viewvc?view=revision&revision=52144 ------------------------------------------------------------------------ r52142 | eapache | 2013-09-19 13:50:25 +0100 (Thu, 19 Sep 2013) | 3 lines Changed paths: M /trunk/epan/dissectors/packet-gluster.h Remove unused enum that started conflicting with /usr/include/dirent.h on my system. ------------------------------------------------------------------------ ------------------------------------------------------------------------ r52144 | eapache | 2013-09-19 14:04:37 +0100 (Thu, 19 Sep 2013) | 3 lines Changed paths: M /trunk/epan/dissectors/packet-gluster.h M /trunk/epan/dissectors/packet-glusterfs.c Enum was used after all. Restore it and namespace it with GLUSTER_ to avoid the collision. ------------------------------------------------------------------------ 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 3

[Bug 841678] New: Installation GUI does not start/work, text install cannot change packages
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=841678 https://bugzilla.novell.com/show_bug.cgi?id=841678#c0 Summary: Installation GUI does not start/work, text install cannot change packages Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Macintosh OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mario_bz(a)mgtech.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 I am reporting this as an installation problem since it is occurring right at the start of the install. I have already reported this as an xorg problem but do not think it is related to xorg and there is no more activity on that problem (bug 835975) where logs, etc. can be found. i apologize if this should not be reported again. I do not know if the installation problem and xorg problem should be reported separately since different people may work on them. I do think this is not an xorg issue but an issue with the hardware not being detected correctly.See the above bug for info and let me know if more is needed, although I have no idea how to get the log of the system at such an early stage of installation. BTW, the GUI is required since I find customizing packages in text mode does not work (at least what I wanted to do). I thought this is important since it prevents installation and may affect others when GA is released. I would like to convert to 13.1 but this is a show stopper. Reproducible: Always Steps to Reproduce: 1.Installation - no GUI 2. 3. Actual Results: No install GUI Expected Results: Install GUI can be used. -- 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 842992] New: GNOME Music does not display the Album Cover art in the notifications
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=842992 https://bugzilla.novell.com/show_bug.cgi?id=842992#c0 Summary: GNOME Music does not display the Album Cover art in the notifications Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML, like Gecko) Chromium/25.0.1349.2 Chrome/25.0.1349.2 Safari/538.1 SUSE/13.1 (3.10.0) Epiphany/3.10.0 When displaying notifications, GNOME Music fails to display the album cover art. The place where the cover should be is blank. Rhythmbox on the other hand does display the cover art in the notifications. Reproducible: Always Steps to Reproduce: 1.launch gnome-music 2.wait for notifications or click on the gnome-music icon in the system tray 3. notice missing cover art on the left Actual Results: the area where the cover art should be is blank Expected Results: cover art to be displayed GNOME 3.10 from GNOME Factory repo -- 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 843451] New: Unused network interface still being configured??
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=843451 https://bugzilla.novell.com/show_bug.cgi?id=843451#c0 Summary: Unused network interface still being configured?? Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 During installation phase 2, I called /usr/lib/yast/startup/yast2.ssh, but didn't change anything. I left both network interfaces untouched, one with dhcp4, the other unconfigured. I was surprised to see a config file for the _unconfigured_ interface: # cat /etc/sysconfig/network/ifcfg-enp13s0 BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='82573E Gigabit Ethernet Controller (Copper)' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='nfsroot' USERCONTROL='no' 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 822888] New: IPv4-mapped IPv6 addresses do not work
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=822888 https://bugzilla.novell.com/show_bug.cgi?id=822888#c0 Summary: IPv4-mapped IPv6 addresses do not work Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: james.knott(a)rogers.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17 Lightning/2.2b1 IPv4-mapped IPv6 addresses is a method of expressing an IPv4 address as an IPv6 address. For example, 172.16.1.10 would become ::ffff:172.16.1.10. As I recall, this worked in openSUSE when I tried it about 3 years ago, but it does not now. As an experiment, I also tried it in Window 7, where it does work. When I try it in openSUSE, Wireshark shows the computer sending the packet to the router, which returns an unreachable error. With Windows, the address is converted to IPv4 as expected. Here is the Wikipedia link on this: https://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses And the RFC: https://tools.ietf.org/html/rfc4291 2.5.5.2. IPv4-Mapped IPv6 Address Reproducible: Always Steps to Reproduce: 1.ping6 an address such as ::ffff:172.16.1.10 2.That address should be converted to 172.16.1.10 3.ping6 gets an echo Actual Results: Instead of converting to an IPv4 address, the IPv4 mapped IPv6 address is sent to the router, which returns an unreachable error. Expected Results: Mapped address should have been converted to IPv4 and pinged the destination. See also IPv6 Essentials 2nd edition by Silvia Hagen (O'Reilly), page 45. -- 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 804202] New: Import Fedora updates repository also
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=804202 https://bugzilla.novell.com/show_bug.cgi?id=804202#c0 Summary: Import Fedora updates repository also Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.3 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: General AssignedTo: adrian(a)suse.com ReportedBy: baurthefirst(a)gmail.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0) Gecko/20100101 Firefox/18.0 Dear developers, Fedora 18 was imported into OBS as it Fedora 18 was released. Now, couple of month later, some important libraries were updated in Fedora, and I wonder, whether it's possible to build actual packages for Fedora via OBS? Currently those packages are still being built against older libraries. Fox example, gnuradio was updated from 3.6.2 to 3.6.3 in Fedora, and in OBS its still 3.6.2. Gnuradio offers only libgnuradio.3.6.3 so file. Sometimes in Fedora re-builds of packages against new libraries happen, for example when new boost was imported. Thank you Reproducible: Always Steps to Reproduce: 1. Build a package against Fedora 18 repo in OBS 2. Try to install in Fedora 18. 3. Library Actual Results: Packages in OBS built for Fedora 18 are being linked against older libraries. Expected Results: Make packages build on OBS for Fedora fully functional. E.g. build packages against latest updated libraries from Fedora. -- 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 842450] New: inconsistent network naming - enp13s0 and eth1 ?
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=842450 https://bugzilla.novell.com/show_bug.cgi?id=842450#c0 Summary: inconsistent network naming - enp13s0 and eth1 ? Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Hardware: taggart24, 1u zattoo box, dual-core, 1Gb memory, dual GiGE. Software: opensuse 13.1 beta1, 64bit Process: installation+boot over pxe+iscsi On the first boot-up, I see the following network config: # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:30:48:92:f3:1c brd ff:ff:ff:ff:ff:ff inet6 fe80::230:48ff:fe92:f31c/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:30:48:92:f3:1d brd ff:ff:ff:ff:ff:ff inet 10.42.8.110/21 brd 10.42.15.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fe80::230:48ff:fe92:f31d/64 scope link valid_lft forever preferred_lft forever According to dmesg, the system initially had eth0 and eth1, and eth0 was then later renamed to enp13s0. Why wasn't eth1 renamed too? Remarkably, the network config is called "ifcfg-enp14s0". 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 8

[Bug 840445] New: yast does not recognize HP 2200 scanner, problem with sane-find-scanner on 64 bit systems
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=840445 https://bugzilla.novell.com/show_bug.cgi?id=840445#c0 Summary: yast does not recognize HP 2200 scanner, problem with sane-find-scanner on 64 bit systems Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: peter.krummrich(a)gmx.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 I have installed openSUSE 12.3 on two systems - 32 bit on a laptop and 64 bit on a tower PC. The 32 bit system on the laptop recognizes the HP 2200 C scanner attached to the USB port, installation with yast works fine and I can use the scanner with xsane. On the 64 bit system, the same scanner is found when I start yast rigth after booting the system, but it does not work. Xsane takes more than 5 minutes to start and scanning is not possible. If I start yast again, the scanner is not found any more. This seems to be the existing problem with sane-find-scanner on 64 bit systems, which I reported on the sane developer bug tracker: https://alioth.debian.org/tracker/?func=detail&atid=410366&aid=314021&group… Please try to motivate the team to continue working on the bug. I hoped that the issue might be solved with openSUSE 12.3, but it is not. The problem will most likely not only exist with the HP 2200 scanner on 64 bit systems, but most likely with several scanners using the plustek backend.There seems to be an issue with the way sane-find-scanner uses the usblib. Reproducible: Always Steps to Reproduce: 1. boot 64 bit system, start yast, install scanner, scanner is found but does not work 2. start yast again, install scanner, no scanner is found Actual Results: scanner is not installed properly on 64 bit system, cannot be used Expected Results: successful scanner installation on 64 bit system as on 32 bit system -- 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 801944] New: yast errs while starting apache2
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=801944 https://bugzilla.novell.com/show_bug.cgi?id=801944#c0 Summary: yast errs while starting apache2 Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: jw(a)suse.com QAContact: qa-bugs(a)suse.de CC: draht(a)suse.com Found By: --- Blocker: --- yast -> system -> system services (Runlevel) apache2 -> Enable -> /bin/systemctl start apache2.service returned 0 (success): [OK] Now the changes to runlevels will be saved. -> [YES] -> Error Failed services: apache2 -> [OK] Next time yast shows apache2 as disabled, although it is up and running. -- 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 810387] New: /usr/bin/acroread: line 32: xdpyinfo: command not found
by bugzilla_noreply＠novell.com 01 Oct '13

01 Oct '13

https://bugzilla.novell.com/show_bug.cgi?id=810387 https://bugzilla.novell.com/show_bug.cgi?id=810387#c0 Summary: /usr/bin/acroread: line 32: xdpyinfo: command not found Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Commercial AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gp(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- Starting acroread, I get the following warning/error: /usr/bin/acroread: line 32: xdpyinfo: command not found The code in questions reads if [ "$(xdpyinfo | grep XInputExtension)" == "" ] ; then # there is no XInputExtension in the VNC X-servers unset GTK2_RC_FILES fi That is, it blindly assumes xdpyinfo is available? This is a system upgraded from 12.1. -- 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