February 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 571953] New: YaST2 Network Devices/Network Settings uses Gnome button order in KDE
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=571953 http://bugzilla.novell.com/show_bug.cgi?id=571953#c0 Summary: YaST2 Network Devices/Network Settings uses Gnome button order in KDE Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bbregister(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2) Specifically, this applet uses Cancel/OK, and therefore looks out of place on a KDE desktop. There may also be other places where this applet uses the wrong button order, and it may be worth reviewing every dialog for both button order and placement. Please refer to the wiki about how to handle Gnome/KDE button order differences using the ButtonBox widget: http://en.opensuse.org/YaST/Development/Misc/Button_Order 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 2

[Bug 571966] New: YaST2 Network Services/Remote Administration (VNC) uses Gnome button order in KDE
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=571966 http://bugzilla.novell.com/show_bug.cgi?id=571966#c0 Summary: YaST2 Network Services/Remote Administration (VNC) uses Gnome button order in KDE Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bbregister(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2) Specifically, this applet uses Cancel/OK, and therefore looks out of place on a KDE desktop. There may also be other places where this applet uses the wrong button order, and it may be worth reviewing every dialog for both button order and placement. Please refer to the wiki about how to handle Gnome/KDE button order differences using the ButtonBox widget: http://en.opensuse.org/YaST/Development/Misc/Button_Order 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 2

[Bug 571951] New: YaST2 Network Devices/ISDN uses Gnome button order in KDE
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=571951 http://bugzilla.novell.com/show_bug.cgi?id=571951#c0 Summary: YaST2 Network Devices/ISDN uses Gnome button order in KDE Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bbregister(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2) Specifically, this applet uses Cancel/OK, and therefore looks out of place on a KDE desktop. There may also be other places where this applet uses the wrong button order, and it may be worth reviewing every dialog for both button order and placement. Please refer to the wiki about how to handle Gnome/KDE button order differences using the ButtonBox widget: http://en.opensuse.org/YaST/Development/Misc/Button_Order 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 2

[Bug 571954] New: YaST2 Network Services/Hostnames uses Gnome button order in KDE
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=571954 http://bugzilla.novell.com/show_bug.cgi?id=571954#c0 Summary: YaST2 Network Services/Hostnames uses Gnome button order in KDE Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bbregister(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2) Specifically, this applet uses Cancel/OK, and therefore looks out of place on a KDE desktop. There may also be other places where this applet uses the wrong button order, and it may be worth reviewing every dialog for both button order and placement. Please refer to the wiki about how to handle Gnome/KDE button order differences using the ButtonBox widget: http://en.opensuse.org/YaST/Development/Misc/Button_Order 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 2

[Bug 571968] New: YaST2 Network Services/iSCSI Initiator uses Gnome button order in KDE
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=571968 http://bugzilla.novell.com/show_bug.cgi?id=571968#c0 Summary: YaST2 Network Services/iSCSI Initiator uses Gnome button order in KDE Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bbregister(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; NET CLR 1.1.4322; MS-RTC LM 8; MS-RTC EA 2) Specifically, this applet uses Cancel/OK, and therefore looks out of place on a KDE desktop. There may also be other places where this applet uses the wrong button order, and it may be worth reviewing every dialog for both button order and placement. Please refer to the wiki about how to handle Gnome/KDE button order differences using the ButtonBox widget: http://en.opensuse.org/YaST/Development/Misc/Button_Order 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 2

[Bug 504769] New: nondevel packages contain devel libraries
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=504769 User behlert(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=504769#c450061 Summary: nondevel packages contain devel libraries Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: puzel(a)novell.com ReportedBy: behlert(a)novell.com QAContact: qa(a)suse.de CC: hare(a)novell.com, behlert(a)novell.com, coolo(a)novell.com, meissner(a)novell.com, nadvornik(a)novell.com, postadal(a)novell.com, ro(a)novell.com, seife(a)novell.com, kde-maintainers(a)suse.de, jmatejek(a)novell.com, dmueller(a)novell.com, hschaa(a)novell.com, jkupec(a)novell.com, prusnak(a)novell.com, nangelov(a)novell.com, crrodriguez(a)novell.com, puzel(a)novell.com Depends on: 450061 Found By: --- +++ This bug was initially created as a clone of Bug #450061 +++ The following package contains files that may be better put into a -devel package. Please evaluate: pth-2.0.7-102.22 -- 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 12

[Bug 540966] New: unscd still runs as user nobody
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=540966 Summary: unscd still runs as user nobody Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 7 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: pbaudis(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de CC: security-team(a)suse.de Found By: --- unscd still runs as user nobody, please use a dedicated user for that task. -- 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 11

[Bug 446098] perl warning: Constant subroutine main::SEEK_SET redefined
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=446098 http://bugzilla.novell.com/show_bug.cgi?id=446098#c6 --- Comment #6 from Jean Delvare <jdelvare(a)novell.com> 2010-02-01 11:50:04 UTC --- Apparently this is fixed in SLE11 SP1, so we should be able to close this bug? -- 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 0

[Bug 552916] New: dhcp client swamps networ with dhcp requests although ip already obtained
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=552916 Summary: dhcp client swamps networ with dhcp requests although ip already obtained Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 the wireless NIC (orionoco_cs Lucent WaveLAN) on a notebook issues DHCP requests in short repetitions, although IP and route already obtained. # ifstatus eth1 cat: /sys/class/net/eth1/device/prod_id4: No such device eth1 device: Lucent Technologies WaveLAN/IEEE Version 01.01 DHCP4 client (dhcpcd) is running . . but is still waiting for data eth1 is up 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:02:2d:5a:95:9f brd ff:ff:ff:ff:ff:ff inet 192.168.178.23/24 brd 192.168.178.255 scope global eth1 inet6 fe80::202:2dff:fe5a:959f/64 scope link valid_lft forever preferred_lft forever eth1 IP address: 192.168.178.23/24 Configured IPv4 routes for interface eth1: default 192.168.178.1 - eth1 169.254.0.0/16 - - eth1 Active IPv4 routes for interface eth1: 192.168.178.0/24 proto kernel scope link src 192.168.178.23 169.254.0.0/16 scope link default via 192.168.178.1 2 of 2 configured IPv4 routes for interface eth1 up Active IPv6 routes for interface eth1: fe80::/64 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0 bssid=00:1f:3f:d1:6d:6c ssid=>noli me tangere< id=0 pairwise_cipher=TKIP group_cipher=TKIP key_mgmt=WPA-PSK wpa_state=COMPLETED ip_address=192.168.178.23 # tcpdump -envfi eth1 tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes 17:49:05.859515 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 123, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:08.863156 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 126, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:09.053464 00:02:2d:5a:95:9f > 00:1f:3f:de:fe:46, ethertype IPv4 (0x0800), length 90: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 76) 192.168.178.23.123 > 192.53.103.104.123: NTPv4, length 48 Client, Leap indicator: (0), Stratum 2, poll 6s, precision -20 Root Delay: 0.056991, Root dispersion: 0.031463, Reference-ID: 192.53.103.104 Reference Timestamp: 3466428436.113001680 (2009/11/05 17:47:16) Originator Timestamp: 3466428484.063633550 (2009/11/05 17:48:04) Receive Timestamp: 3466428484.112597805 (2009/11/05 17:48:04) Transmit Timestamp: 3466428549.053322950 (2009/11/05 17:49:09) Originator - Receive Timestamp: +0.048964255 Originator - Transmit Timestamp: +64.989689400 17:49:09.111920 00:1f:3f:de:fe:46 > 00:02:2d:5a:95:9f, ethertype IPv4 (0x0800), length 90: (tos 0x0, ttl 55, id 4485, offset 0, flags [DF], proto UDP (17), length 76) 192.53.103.104.123 > 192.168.178.23.123: NTPv4, length 48 Server, Leap indicator: (0), Stratum 1, poll 6s, precision -20 Root Delay: 0.000000, Root dispersion: 0.001083, Reference-ID: PTB^@ Reference Timestamp: 3466428537.932398660 (2009/11/05 17:48:57) Originator Timestamp: 3466428549.053322950 (2009/11/05 17:49:09) Receive Timestamp: 3466428549.071317518 (2009/11/05 17:49:09) Transmit Timestamp: 3466428549.071349705 (2009/11/05 17:49:09) Originator - Receive Timestamp: +0.017994567 Originator - Transmit Timestamp: +0.018026754 17:49:10.180795 00:1f:3f:de:fe:46 > 00:02:2d:5a:95:9f, ethertype IPv4 (0x0800), length 74: (tos 0x0, ttl 64, id 30889, offset 0, flags [DF], proto TCP (6), length 60) 192.168.178.1.2870 > 192.168.178.23.14013: Flags [S], cksum 0x1e7b (correct), seq 1891213494, win 5840, options [mss 1460,sackOK,TS val 30201887 ecr 0,nop,wscale 3], length 0 17:49:10.180997 00:02:2d:5a:95:9f > 00:1f:3f:de:fe:46, ethertype IPv4 (0x0800), length 54: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 40) 192.168.178.23.14013 > 192.168.178.1.2870: Flags [R.], cksum 0x7702 (correct), seq 0, ack 1891213495, win 0, length 0 17:49:11.866842 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 129, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:14.870474 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 132, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:17.874302 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 135, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:20.878011 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 138, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:23.881678 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 141, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:26.885325 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 144, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] 17:49:29.888967 00:02:2d:5a:95:9f > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 351: (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 337) 192.168.178.23.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:02:2d:5a:95:9f, length 309, xid 0xa462b013, secs 147, Flags [none] Client-IP 192.168.178.23 Client-Ethernet-Address 00:02:2d:5a:95:9f [|bootp] ^C 13 packets captured 13 packets received by filter 0 packets dropped by kernel dhcpcd-3.2.3-47.2.i586 dhcp-3.1.2p1-4.5.i586 dhcp-client-3.1.2p1-4.5.i586 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 12

[Bug 572186] New: VLAN - multiple configuration of the same vlan ethX.Y
by bugzilla_noreply＠novell.com 01 Feb '10

01 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=572186 http://bugzilla.novell.com/show_bug.cgi?id=572186#c0 Summary: VLAN - multiple configuration of the same vlan ethX.Y Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: adrian.ban(a)mantech.ro QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) I found a strange bug in network configuration if i got two vlans with same ID, let's say VID 17, and two interfaces, let's say eth0 and bond0 (bond0 using eth1,eth2,eth3 and eth4) Starting the configuration eth0.17 from ifcfg-eth0.11 works fine ifcfg-eth0.11: BOOTPROTO='static' ETHERDEVICE='eth0' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='A.B.C.D/28' MTU='' NAME='VLAN 11 - Servers Interconnect' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' But if i add a new vlan 11 on bond0 with ifcfg-bond0.11: BOOTPROTO='static' ETHERDEVICE='bond0' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='A.B.C.E/28' MTU='' NAME='VLAN 11 - Servers Interconnect' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' The /etc/init.d/network start bond0.11 returns me: PPPoE1:/etc/sysconfig/network/scripts # /etc/init.d/network start bond0.11 Hint: you may set mandatory devices in /etc/sysconfig/network/config Setting up network interfaces: bond0.11 name: VLAN 11 - Servers Interconnect ERROR: unable to rename vlan interface 'eth0.11 bond0.11' to 'bond0.11': Cannot find device "eth0.11 bond0.11" ERROR: if_name must be 15 characters or less. bond0.11 Trying some echo for debug in ifup-802.1q at line 195: # Don't hurry too much udevadm settle viface=`get_vlan_iface_name "$nr"` echo $INTERFACE $viface if test "x$viface" = x ; then bond0.11 name: VLAN 11 - Servers Interconnect bond0.11 eth0.11 bond0.11 ERROR: unable to rename vlan interface 'eth0.11 It seems that get_vlan_iface_name "$nr" returns both of interfaces: eth0.11 bond0.11 Reproducible: Always Steps to Reproduce: 1. create ifcfg-eth0.11 and ifcfg-bond0.11 2. fireup the eth0.11 and after that bond0.11 Actual Results: Script failed to fireup complety the second vlan with same VID but different interface. Expected Results: I should start up both interfaces with no problems -- 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