March 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 586072] New: Identical sentences.
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=586072 http://bugzilla.novell.com/show_bug.cgi?id=586072#c0 Summary: Identical sentences. Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: isis.binder(a)gmail.com QAContact: ke(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pt-BR; rv:1.9.2) Gecko/20100115 Firefox/3.6 File: apparmor-utils.po line 30: #: ../genprof:55 msgid "AppArmor does not appear to be started. Please enable AppArmor and try again." line 160: #: ../unconfined:57 msgid "AppArmor does not appear to be started. Please enable AppArmor and try again." line 744: #: ../Reports.pm:443 ../Reports.pm:532 ../Reports.pm:1480 #, perl-format msgid "DBI Execution failed: %s." line 806: #: ../Reports.pm:970 ../Reports.pm:983 ../Reports.pm:991 #, perl-format msgid "DBI Execution failed: %s" Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 4

[Bug 588231] New: Want to create a project for NAnt
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=588231 http://bugzilla.novell.com/show_bug.cgi?id=588231#c0 Summary: Want to create a project for NAnt Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: mrueckert(a)novell.com ReportedBy: rmboggs(a)gmail.com QAContact: adrian(a)novell.com Found By: --- Blocker: --- We are trying to revive the NAnt project (http://nant.sourceforge.net/) and was hoping that we could use this service to help us with scheduled builds with Mono. It would be nice to setup some space outside the normal userhome namespace relm since there will be multiple people involved with this project. If there are any questions, please let me know and, if possible, CC: cchan_qa _AT_ users.sourceforge.net as well. -- 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 3

[Bug 578608] New: Require Devel:HP-CNB and SUSE:SLE-11:HP-ZIP
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=578608 http://bugzilla.novell.com/show_bug.cgi?id=578608#c0 Summary: Require Devel:HP-CNB and SUSE:SLE-11:HP-ZIP Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: mrueckert(a)novell.com ReportedBy: jzheng(a)novell.com QAContact: adrian(a)novell.com CC: gekker(a)novell.com, uwedr(a)novell.com, mchang(a)novell.com, jzheng(a)novell.com, machen(a)novell.com, jcheung(a)novell.com, jlee(a)novell.com Found By: --- Blocker: --- Devel:HP-CNB and SUSE:SLE-11:HP-ZIP are required for preload for hp-cnb-nadal. -- 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 9

[Bug 586066] New: Speed up start-up time of OpenOffice.org by tinkering with the memory settings
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=586066 http://bugzilla.novell.com/show_bug.cgi?id=586066#c0 Summary: Speed up start-up time of OpenOffice.org by tinkering with the memory settings Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: pBakhuis(a)Gmail.com QAContact: cwei(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 The memory settings described on: http://www.ghacks.net/2007/08/18/speed-up-open-office/ * Number of Steps: 30 * Use for Open Office: 128 * Memory per Object: 20 * Number of Objects: 20 Greatly speed up the startup time of openoffice compared to the default settings, I think these should be used by default if the system has at least a certain amount of memory. (768MB?) Reduced the startup time for me personally from 6 seconds or so to about 2. On a side note, Preventing it from using the JRE makes the startup time comparable to that of MS Office, but at the cost of functionality... so that's probably not something that should be done by default. Reproducible: Always -- 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 5

[Bug 588156] New: Linux Libertine font is not available for xelatex
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=588156 http://bugzilla.novell.com/show_bug.cgi?id=588156#c0 Summary: Linux Libertine font is not available for xelatex Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ctrippe(a)gmx.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.4; Linux) KHTML/4.4.1 (like Gecko) SUSE I am using the texlive packages from the publishing repo. I tried to use the Linux Libertine font with xelatex which always produced an error that \setmainfont{Linux Libertine O} is an unknown command. According to http://wiki.archlinux.org/index.php/TeXLive#Fonts the reason seems to be that the otf fonts of the texlive package are not available to fontconfig. A workaround is also described on that page. I attach an example document to reproduce the error. Reproducible: Always -- 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 2

[Bug 580361] New: netconfig(8) manpage misses crucial dnsmasq setup information
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=580361 http://bugzilla.novell.com/show_bug.cgi?id=580361#c0 Summary: netconfig(8) manpage misses crucial dnsmasq setup information Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pieter(a)hollants.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) I was trying to find out how to setup the network configuration so that I could run my own local nameserver (dnsmasq) and have dynamic nameservers stored not in resolv.conf but an appropriate seperate file. So I was looking into the netconfig(8) manpage at first. It mentioned the NETCONFIG_DNS_FORWARDER variable with a possible setting of "dnsmasq", but no further info on what would actually change then. I found this information in /usr/share/doc/packages/sysconfig/README.netconfig, but seeing it is crucial it should be in the manpage: --> Pls add to the appropriate paragraph a notice for dnsmasq that /var/run/dnsmasq-forwarders.conf will be modified instead of /etc/resolv.conf, which should be referenced in dnsmasq with the "resolv-file" option. The same for bind (/etc/name.d/forwarders.conf and whatever option necessary to include that file). I was then still having a NETCONFIG_DNS_STATIC_SERVERS entry 127.0.0.1, which, I thought, would be written to /etc/resolv.conf, but the dynamic data would go into /var/run/dnsmasq-forwarders.conf. Instead static and dynamic data go in the latter, which is, no doubt, correct, but confused me, and I wondered whether I had to modify /etc/resolv.conf manually. It wasn't until I read through /etc/netconfig.d/dns-resolver that I learned that no "nameserver 127.0.0.1" entry is required at all since glib defaults to localhost if no "nameserver" entries are given. --> Pls add to the appropriate paragraph also a note that 127.0.0.1 should not be declared in NETCONFIG_DNS_STATIC_SERVERS since glibc will automatically use the local nameserver. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 8

[Bug 572327] New: dhcpcd and dhclient do not accept offered IP address
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=572327 http://bugzilla.novell.com/show_bug.cgi?id=572327#c0 Summary: dhcpcd and dhclient do not accept offered IP address Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i386 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: angie(a)nameless-host.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 Shortly after the installation the machine will have an IP address. If the machine is turned off for a while it seems to be ignoring all addresses offered by the dhcp server. dhclient: does not use any old lease - nevertheless a leas file is created. dhcpcd: accepts the IP address, but ignores it since the lease time for this IP is over - the created lease file is not cleaned up at all although I configured DHCLIENT_RELEASE_BEFORE_QUIT="yes". As a result the lease is not accepted by dhcpcd, and dhclient ignores the offered IP from the dhcp host when activated via rcnetwork restart. The following will work nevertheless: rcnetwork restart && dhclient eth0 -> eth0 will gain an address (but not write it to the official lease file) Reproducible: Always Steps to Reproduce: 1. Configure eth0 to use dynamic address 2. Edit /etc/sysconfig/network/dhcp and set dhclient for DHCLIENT_BIN 3. Shutdown the machine for at least 4 hours (until the lease has expired) 4. Boot the machine Actual Results: /etc/sysconfig/network/dhcp: DHCLIENT_BIN="dhclient" Jan 19 08:34:42 client ifup: lo Jan 19 08:34:42 client ifup: lo Jan 19 08:34:42 client ifup: IP address: 127.0.0.1/8 Jan 19 08:34:42 client ifup: Jan 19 08:34:42 client ifup: Jan 19 08:34:42 client ifup: IP address: 127.0.0.2/8 Jan 19 08:34:42 client ifup: Jan 19 08:34:43 client ifup: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Jan 19 08:34:43 client kernel: [ 13.844606] r8169: eth0: link up Jan 19 08:34:43 client ifup-dhcp: eth0 Starting DHCP4 client Jan 19 08:34:43 client dhclient: nss_ldap: could not search LDAP server - Server is unavailable Jan 19 08:34:44 client ifup-dhcp: . Jan 19 08:34:45 client kernel: [ 15.312648] NET: Registered protocol family 17 Jan 19 08:34:46 client dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Jan 19 08:34:46 client dhclient: DHCPOFFER from 192.168.20.1 Jan 19 08:34:47 client ifup-dhcp: . Jan 19 08:34:50 client ifup-dhcp: . Jan 19 08:34:51 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:34:53 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:34:53 client ifup-dhcp: . Jan 19 08:34:53 client kernel: [ 24.103025] eth0: no IPv6 routers present Jan 19 08:34:56 client ifup-dhcp: . Jan 19 08:34:57 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:34:59 client ifup-dhcp: . Jan 19 08:35:02 client ifup-dhcp: . Jan 19 08:35:06 client ifup-dhcp: . Jan 19 08:35:07 client ifup-dhcp: Jan 19 08:35:07 client ifup-dhcp: eth0 DHCP4 continues in background Jan 19 08:35:08 client dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Jan 19 08:35:08 client dhclient: DHCPOFFER from 192.168.20.1 Jan 19 08:35:18 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:35:24 client dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 Jan 19 08:35:24 client dhclient: DHCPOFFER from 192.168.20.1 Jan 19 08:35:29 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:35:31 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:35:36 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:35:41 client dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 Jan 19 08:35:41 client dhclient: DHCPOFFER from 192.168.20.1 Jan 19 08:35:46 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:35:49 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Jan 19 08:35:53 client dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 rcnetwork output: Shutting down network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) eth0 .doneShutting down service network . . . . . . . . ...done Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) eth0 Starting DHCP4 client. . . . . . . . eth0 DHCP4 continues in background eth0 Setting up service network . . . . . . . . . ...done /etc/sysconfig/network/dhcp: DHCLIENT_BIN="" Jan 19 08:36:44 client ifdown: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Jan 19 08:36:45 client avahi-daemon[2740]: Withdrawing address record for fe80::230:5ff:febc:4558 on eth0. Jan 19 08:37:32 client ifdown: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Jan 19 08:37:36 client ifup: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) Jan 19 08:37:37 client kernel: [ 187.460813] r8169: eth0: link up Jan 19 08:37:37 client ifup-dhcp: eth0 Starting DHCP4 client Jan 19 08:37:37 client dhcpcd[6622]: eth0: dhcpcd 3.2.3 starting Jan 19 08:37:37 client dhcpcd[6622]: eth0: hardware address = 00:30:05:bc:45:58 Jan 19 08:37:37 client dhcpcd[6622]: eth0: broadcasting for a lease Jan 19 08:37:37 client dhcpcd[6622]: eth0: offered 192.168.20.38 from 192.168.8.198 Jan 19 08:37:37 client ifup-dhcp: . Jan 19 08:37:39 client avahi-daemon[2740]: Registering new address record for fe80::230:5ff:febc:4558 on eth0.*. Jan 19 08:37:40 client ifup-dhcp: . Jan 19 08:37:43 client ifup-dhcp: . Jan 19 08:37:46 client ifup-dhcp: . Jan 19 08:37:48 client kernel: [ 198.385049] eth0: no IPv6 routers present Jan 19 08:37:50 client ifup-dhcp: . Jan 19 08:37:53 client ifup-dhcp: . Jan 19 08:37:56 client ifup-dhcp: . Jan 19 08:37:57 client dhcpcd[6622]: eth0: timed out Jan 19 08:37:57 client dhcpcd[6622]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info' Jan 19 08:37:57 client dhcpcd[6622]: eth0: lease information file `/var/lib/dhcpcd/dhcpcd-eth0.info' does not exist Jan 19 08:37:57 client dhcpcd[6622]: eth0: broadcasting for a lease Jan 19 08:37:57 client dhcpcd[6622]: eth0: offered 192.168.20.38 from 192.168.8.198 Jan 19 08:37:59 client ifup-dhcp: . Jan 19 08:38:01 client ifup-dhcp: Jan 19 08:38:01 client ifup-dhcp: eth0 DHCP4 continues in background Jan 19 08:38:17 client dhcpcd[6622]: eth0: timed out Jan 19 08:38:17 client dhcpcd[6622]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info' Jan 19 08:38:17 client dhcpcd[6622]: eth0: lease information file `/var/lib/dhcpcd/dhcpcd-eth0.info' does not exist Jan 19 08:38:17 client dhcpcd[6622]: eth0: broadcasting for a lease Jan 19 08:38:17 client dhcpcd[6622]: eth0: offered 192.168.20.38 from 192.168.8.198 Jan 19 08:38:37 client dhcpcd[6622]: eth0: timed out Jan 19 08:38:37 client dhcpcd[6622]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info' Jan 19 08:38:37 client dhcpcd[6622]: eth0: lease information file `/var/lib/dhcpcd/dhcpcd-eth0.info' does not exist Jan 19 08:38:37 client dhcpcd[6622]: eth0: broadcasting for a lease Jan 19 08:38:37 client dhcpcd[6622]: eth0: offered 192.168.20.38 from 192.168.8.198 Jan 19 08:38:57 client dhcpcd[6622]: eth0: timed out Jan 19 08:38:57 client dhcpcd[6622]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info' Jan 19 08:38:57 client dhcpcd[6622]: eth0: lease information file `/var/lib/dhcpcd/dhcpcd-eth0.info' does not exist Jan 19 08:38:57 client dhcpcd[6622]: eth0: broadcasting for a lease Jan 19 08:38:57 client dhcpcd[6622]: eth0: offered 192.168.20.38 from 192.168.8.198 Jan 19 08:39:17 client dhcpcd[6622]: eth0: timed out Jan 19 08:39:17 client dhcpcd[6622]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info' Jan 19 08:39:17 client dhcpcd[6622]: eth0: lease information file `/var/lib/dhcpcd/dhcpcd-eth0.info' does not exist Jan 19 08:39:17 client dhcpcd[6622]: eth0: broadcasting for a lease Jan 19 08:39:17 client dhcpcd[6622]: eth0: offered 192.168.20.38 from 192.168.8.198 rcnetwork output: Shutting down network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) eth0 .doneShutting down service network . . . . . . . . ...done Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) eth0 Starting DHCP4 client. . . . . . . . eth0 DHCP4 continues in background eth0 Setting up service network . . . . . . . . . ...done client:~ # dhclient eth0 Internet Systems Consortium DHCP Client V3.1.2p1 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:30:05:bc:45:58 Sending on LPF/eth0/00:30:05:bc:45:58 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 192.168.20.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.20.1 bound to 192.168.20.38 -- renewal in 1658 seconds. Expected Results: Internet Systems Consortium DHCP Client V3.1.2p1 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/00:30:05:bc:45:58 Sending on LPF/eth0/00:30:05:bc:45:58 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPOFFER from 192.168.20.1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 192.168.20.1 bound to 192.168.20.38 -- renewal in 1658 seconds. A very interesting behavior I had with a host using the e1000 driver before the automatic installation started: "Address 0.0.0.0 already in use" -> I had to configure the network manually, so I cannot use a fully automatized installation here. At least I found a tiny hint for the automatic installation: since you might obtain a dynamic address during the installation gain all necessary information while still installing and configure static IP addresses - which would mean that the dhcp server is useless after the installation has finished. Please give me a hint on which configuration files I need to check to verify that it is _not_ caused by misconfiguration. The whole machine setup and use depends highly on a working network configuration: LDAP authentication, home directory mounted via nfs, ntp usage ... every day users. Thanks, Angie. -- 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 8

[Bug 578451] New: Very bad (no) connection to Internet, so can't use Yast
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=578451 http://bugzilla.novell.com/show_bug.cgi?id=578451#c0 Summary: Very bad (no) connection to Internet, so can't use Yast Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.thiessen(a)gmx.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.7) Gecko/20091222 SUSE/3.5.7-1.1.1 Firefox/3.5.7 After openSUSE installation, the network card worked out of the box (?), I can't connect to the Internet, or rather I could connect but firefox must start connecting for three times. And no chance to loading the online repositorys. Reproducible: Always Steps to Reproduce: 1.Go to Yast network options 2.change all network-cards (ports?) to activate at system start 3.save -- 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 7

[Bug 535750] New: Wireless NIC with Atheros chipset can't connect with any websites despite having ip address
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=535750 Summary: Wireless NIC with Atheros chipset can't connect with any websites despite having ip address Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pilotgi(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-3.1 Firefox/3.5.2 I have a D-Link wireless pci NIC that uses the Atheros ar2413 chipset. It's recognized and configured with YaST2 using the ath5k module. Everything I look at shows that wlan0 is up and running except for an error that 'dhcp4 client is not running'. ifconfig looks like this: eth0 Link encap:Ethernet HWaddr 00:17:31:6F:3C:02 inet addr:192.168.1.69 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::217:31ff:fe6f:3c02/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:14843 errors:0 dropped:0 overruns:0 frame:0 TX packets:11946 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12916277 (12.3 Mb) TX bytes:2106314 (2.0 Mb) Interrupt:23 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:141 errors:0 dropped:0 overruns:0 frame:0 TX packets:141 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10780 (10.5 Kb) TX bytes:10780 (10.5 Kb) wlan0 Link encap:Ethernet HWaddr 00:24:01:12:A5:27 inet addr:192.168.1.68 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::224:1ff:fe12:a527/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1706 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:76506 (74.7 Kb) TX bytes:7878 (7.6 Kb) wmaster0 Link encap:UNSPEC HWaddr 00-24-01-12-A5-27-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) And this is what I get when I do rcnetwork restart (eth0 disconnected): rcnetwork restart Shutting down network interfaces: eth0 device: nVidia Corporation MCP51 Ethernet Controller (rev a3) eth0 done wlan0 device: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) wlan0 done Shutting down service network . . . . . . . . . done Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: eth0 device: nVidia Corporation MCP51 Ethernet Controller (rev a3) eth0 Starting DHCP4 client. . . . . . . . eth0 DHCP4 continues in background eth0 waiting wlan0 device: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) wlan0 starting wpa_supplicant wlan0 Starting DHCP4 client. . wlan0 DHCP4 client NOT running wlan0 failed Setting up service network . . . . . . . . . . done SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... SuSEfirewall2: using default zone 'ext' for interface wmaster0 SuSEfirewall2: batch committing... SuSEfirewall2: Firewall rules successfully set I can ping 192.168.1.68 with no errors but I can't ping any other web addresses. This is the results of dhcpcd-test: info, wlan0: hardware address = 00:24:01:12:a5:27 info, wlan0: broadcasting for a lease debug, wlan0: sending DHCP_DISCOVER with xid 0x5224f7fc debug, wlan0: waiting for 10 seconds debug, wlan0: got a packet with xid 0x5224f7fc info, wlan0: offered 192.168.1.68 from 192.168.1.254 IPADDR='192.168.1.68' NETMASK='255.255.255.0' NETWORK='192.168.1.0' BROADCAST='192.168.1.255' ROUTES='' GATEWAYS='192.168.1.254' DNSSERVERS='192.168.1.254' DHCPSID='192.168.1.254' LEASETIME='86400' RENEWALTIME='43200' REBINDTIME='75600' INTERFACE='wlan0' CLASSID='dhcpcd 3.2.3' CLIENTID='01:00:24:01:12:a5:27' DHCPCHADDR='00:24:01:12:a5:27' info, wlan0: exiting This NIC is working with 11.1. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 42

[Bug 586338] New: openSUSE if{up,down} scripts are bloated and they work fathomless
by bugzilla_noreply＠novell.com 15 Mar '10

15 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=586338 http://bugzilla.novell.com/show_bug.cgi?id=586338#c0 Summary: openSUSE if{up,down} scripts are bloated and they work fathomless Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nettezzaumanaa(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 hi suse developers .. sorry for bothering you again with network scripts but .. eh. suse network scripts are unclear, complicated and works badly in 11.2 .. there are many issues like bad invoking dhcpcd via /sbin/ifup-dhcp which leads to preserving dhcpcds' own resolv.conf and so .. issues are for example: 1) dhcp client survives after carrier removal, iface has address as is up 2) etc/resolv.conf is preserverd using strange way, so you need to manually kill dhcpcd (dhcpcd -x $iface) and run it again after carrier removal a plug in again 3) dhcp client is invoked for all iface at startup even if there is no link 4) rc scripts produces errors while waiting for *mandatory devices 5) at least ipv6 on/off switch in yast doesn't work .. i think that these scripts need a general maintenance and refresh .. Reproducible: Always Steps to Reproduce: 1. don't use NM 2. take a closer look at how traditional network stack in suse works 3. simply put a "set -x; exec 2>/tmp/dhcp-$$.log" at beginning of /sbin/ifup-dhcp and take a look which all nonsenses and fathomless things script does and probes Actual Results: i please a network maintainers in openSUSE to don't scratch this BUG with poor putoff that we have to use a NM if we want our netstack working reasonable way . have a nice day and regards .. ave, daniel -- 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 3