July 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 412476] New: Incompatibility with KVM Switch
by bugzilla_noreply＠novell.com 15 Feb '09

15 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=412476 Summary: Incompatibility with KVM Switch Product: openSUSE 11.0 Version: Final Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Blocker Priority: P5 - None Component: Booting AssignedTo: jsrain(a)novell.com ReportedBy: andrew(a)joako.net QAContact: jsrain(a)novell.com Found By: Corporate Interoperability Test I have a "Zonet KVM3202" 2-port KVM switch. When the USB cable is connected to the openSUSE 11.0 machine the system hangs before sys v. init can run. When the USB cable is unplugged the system boots as normal. However with the KVM switch I can navigate the GRUB menu with no issues and if it is plugged in after the system has booted it works fine. -- 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 9

[Bug 381178] New: checkboxes alligned to much to the left side
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=381178 Summary: checkboxes alligned to much to the left side Product: openSUSE 11.0 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: sh(a)novell.com ReportedBy: jsuchome(a)novell.com QAContact: jsrain(a)novell.com CC: coolo(a)novell.com Found By: --- Created an attachment (id=208843) --> (https://bugzilla.novell.com/attachment.cgi?id=208843) user config in installation We already talked about this on IRC: `VBox ( `TextEntry (... `opt (`hstretch)) `Left (`CheckBox (...)) ) results in checkbox a little to the left of when TextEntry starts. -- 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 10

[Bug 305333] New: Bridge and bridge port ifup order
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=305333 Summary: Bridge and bridge port ifup order Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jfunk(a)funktronics.ca QAContact: qa(a)suse.de Found By: --- I have a rather complex network setup, so I will just list the relevant parts: eth - Physical ethernet interface, connected to a vlan trunk vlan4 - VLAN 4, on eth dot23 - A bridge containing vlan4 and my default route It appears that the network init script brings up non-physical interfaces alphabetically, so it will bring these devices in the following order: eth dot23 vlan4 Since vlan4 doesn't exist when dot23 is brought up, it is never added to the bridge, and I have to manually add it or restart the bridge. One way to solve this, of course, is to make the init script bring up any interfaces listed in BRIDGE_PORTS before bringing up the bridge. Another way is to also define port membership in the port ifcfg files. This is actually something I have been doing for a long while now with a custom {ifup,ifdown}-bridgeport script in /etc/sysconfig/network/scripts, which I will attach. Basically, I use Qemu and OpenVPN quite a bit, and I usually want them bridged to one place to another automatically. I configure them to create tap devices, with descriptive names (when you have 16 or more active interfaces at any one time, descriptive helps :-). I then create an ifcfg file like so: BOOTPROTO='none' NAME='Some Qemu Instance External Interface' STARTMODE='auto' USERCONTROL='yes' POST_UP_SCRIPT='ifup-bridgeport' PRE_DOWN_SCRIPT='ifdown-bridgeport' BRIDGENAME='dot23' If I called it ifcfg-foo and had Qemu create a tap device called foo, It would automatically be bridged to vlan4 on creation. This setup has been working quite well for me, and it would be nice if similar functionality were available in openSUSE by default. -- 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 9

[Bug 375834] New: ppp over vlan-tagged ethernet - occasional network startup order problems (rcnetwork script doesnt properly start ethernet, vlan and dsl0 in this order, but eth dsl0 (which then fails) then vlan)
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=375834 User abittner(a)stud.fh-heilbronn.de added comment https://bugzilla.novell.com/show_bug.cgi?id=375834#c7 Summary: ppp over vlan-tagged ethernet - occasional network startup order problems (rcnetwork script doesnt properly start ethernet, vlan and dsl0 in this order, but eth dsl0 (which then fails) then vlan) Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: abittner(a)stud.fh-heilbronn.de QAContact: qa(a)suse.de Found By: --- hello opensuse team, for a while now i have tried to find the reason of my networking problems on a vdsl2 line (germany, deutsche telekom vdsl2-based broadband consumer line). deutsche telekom provides a pppoe-based vdsl2 line. the only specialty and difference to other standard adsl/adsl2+ lines is the vlan-tag on the ethernet-interface of their line. the ethernet-device needs to set/use vlan-id #7 to communicate with their vdsl2 cpe (ethernet modem/bridge). everything else is standard pppoe. i used to have many older opensuse versions on normal adsl/adsl2+ lines with simple pppoe. everything worked fine. the dsl0 device was defined with yast2. fine so far. with the vdsl2 line of deutsche telekom i needed to create the textfile ifcfg-vlan7 in /etc/sysconfig/network/ eth2 is the pci ethernetcard which connects to the vdsl2 modem/bridge. # the content of ifcfg-vlan7 is: STARTMODE=hotplug ETHERDEVICE=eth2 IPADDR=10.168.2.2 NETMASK=255.255.255.0 #ifcfg-eth2 content is: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.1.1/24' MTU='1500' NAME='Realtek RTL-8169 Gigabit Ethernet' NETMASK='255.255.255.0' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' UNIQUE='JNkJ.oxSyVMMObW1' USERCONTROL='no' _nm_name='bus-pci-0000:04:09.0' PREFIXLEN='' # the content of ifcfg-dsl0 is: BOOTPROTO='none' DEVICE='vlan7' MODEM_IP='10.0.0.138' NAME='DSL Connection' PPPD_OPTIONS='' PPPMODE='pppoe' PROVIDER='tonline-dsl' STARTMODE='hotplug' UDI='' USERCONTROL='yes' VPIVCI='' the problem is that during the bootup of this system many times the dsl0 device fails to start (rcnetwork status after login displays "unused") and somehow i figured it is because the system sometimes wants to start dsl0 too quickly or virtually at the same time as the vlan7 device, and sometimes the vlan7 device coming up after the dsl0. which fails ofcourse as dsl0 devices depends/uses the vlan7 device. can this be fixed in a simple and easy way? also: yast doesnt really offer to handle vlan devices at all properly, i needed to do manual editing/configuration of the ifcfg-vlanX file, and you cant select/create/handle vlan devices inside yast. generally: vlan devices can only be ontop of eth devices, and pppoe can only be ontop of eth devices as the name already suggests. as vlan only exists on top of ethernet devices (if im not mistaken), and no vlan can be on top of ppp or such devices, the order of device starting needs to be ethernet -> vlan -> xxx-over-ethernet to make any sense, as vlan is only some bits/bytes inside a slightly enhanced/modded ethernet-frame. as pppoe can be ontop of ethernet, and ethernet can be ethernet or vlan-tagged-ethernet so ppp should only brought up after all ethernet and vlan-tagged-ethernet devices have started themselves. i have slightly taken a look into the /sbin/rcnetwork script and found: ###################################################################### # Get interfaces to handle # # Seperate this interfaces into several sets, not all mutually exclisive; # none of them may contain lo, because it will always handled separately # # AVAILABLE_IFACES are all interfaces from /sys/class/net # these have to be shut down when stopping # # PHYSICAL_IFACES are interfaces to present physical devices, they will be # derived from AVAILABLE_IFACES # # DIALUP_IFACES are modemX, dslX, etc., they are derived from ifcfg-* files # # TUNNEL_IFACES are interfaces that do not fit into PHYSICAL and DIALUP and # are as well derived from ifcfg-* files # # PHYSICAL, DIALUP and TUNNEL are mutually exclusive. Their union contains # AVAILABLE and MANDATORY and all of them have to be set up when starting # # MANDATORY_IFACES these must be up and well configured for success # At first get DIALUP and TUNNEL while IFS=- read a b; do test -z "$b" && continue b=`type_filter $b` case "`get_iface_type_from_config $b`" in lo|eth|tr|wlan|irda|ip6tnl|mip6mnha) continue ;; *ppp|dsl|modem|isdn) DIALUP_IFACES="$DIALUP_IFACES $b" ;; vlan|bond|bridge|ipip|sit|gre) TUNNEL_IFACES="$TUNNEL_IFACES $b" ............................ im not a programmer or networking expert, but to my undersanding the vlan needs to be closer to ethernet and way before a ppp devices as ppp can be over/on ethernet...... maybe other scenarios should also be taken into account, i didnt think about bonding, bridging, gre and so forth...... thanks for a quick fix or hint how to make my vdsl2 startup to work more reliable and to properly bring up the interfaces that depend on each other. best regards. -- 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 25

[Bug 212053] New: Set promote_secondaries=1 by default
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=212053 Summary: Set promote_secondaries=1 by default Product: openSUSE 10.2 Version: Alpha 5 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kernel01(a)hailfinger.org QAContact: qa(a)suse.de /proc/sys/net/ipv4/conf/*/promote_secondaries is currently set to 0 by default. Changing that to 1 would be a user-visible change for users with multiple ip addresses on one interface, but the changed behaviour is IMO less surprising than the current one. Description for promote_secondaries: Deleting the primary IP address of an interface forces deletion all secondary IP addresses unless promote_secondaries is set. This side effect of killing all secondary addresses without warning (and without documentation about this behaviour) has caused me and lots of others quite some grief. Scenario: You are logged into a remote box on one of its secondary IP addresses (to be able to change the primary IP address without disrupting your work), delete the primary IP address to later add the new primary IP address and suddenly find out that the secondary IP address you were using for administration has vanished. No way to connect to the box (it has no IP address anymore), so you have to ask someone to flip the power switch and hope it works with the old config after reboot. If promote_secondaries had been set, the disaster would not have happened. -- 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, or are watching someone who is.

1 11

[Bug 389741] New: Package selector should show the icon meaning in tooltip
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=389741 Summary: Package selector should show the icon meaning in tooltip Product: openSUSE 11.0 Version: Beta 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: visnov(a)novell.com QAContact: jsrain(a)novell.com Found By: --- IIRC on 10.3 the tooltip for the package status icon in the package selector contained description of all possible states with icons. This is gone now, so it is not completely easy to understand the symbols when seen for the first time. -- 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 399040] New: software management: keyboard shortcuts kill the focus
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=399040 Summary: software management: keyboard shortcuts kill the focus Product: openSUSE 11.0 Version: RC 1 Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)novell.com Found By: --- Search for openoffice click on the second entry in the package list press - (delete) note the focus is gone. What should happen: * focus should be still in the list pane * selection should jump to the next item in the list -- 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 407098] New: Option in software management,"yast2->filter->patterns-> All in this list is not working as expected
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=407098 Summary: Option in software management,"yast2->filter->patterns- >All in this list is not working as expected Product: openSUSE 11.0 Version: Final Platform: i386 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pg.radadia(a)gmail.com QAContact: jsrain(a)novell.com Found By: Community of Practice 1.open the software management from yast 2.select the patterns options from Filter 3.select any category in from the pattern(i have selected multimedia) 4.try to use option available in the menu available after right clicking on the pattern in "All in this list",none of them is working properly, while same option available through "main menu->package->All in this list" is working properly -"All in this list->install" hang the yast2 -"All in this list->Do not install" does nothing -"All in this list->Keep" does nothing -"All in this list->Delete" does nothing -"All in this list->Update if new version available" does nothing -"All in this list->Update unconditionally" does nothing -"All in this list->Taboo--never install" mark all the category for never install -- 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 340170] New: DefaultSize isn't nice on WideScreen-monitors
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=340170 Summary: DefaultSize isn't nice on WideScreen-monitors Product: openSUSE 11.0 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: sh(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com Found By: --- I've changed my 4:3 monitor to a WideScreen one and now it seems that Qt default-size respects the aspect ration of the monitor which is unfortunately not useful/nice on WideScreens. My monitor has 1680x1050 resulution, the default size is 1176x735 :( -- 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 9

[Bug 386391] New: Yast2 Module icons are blured on the kicker
by bugzilla_noreply＠novell.com 13 Feb '09

13 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=386391 Summary: Yast2 Module icons are blured on the kicker Product: openSUSE 11.0 Version: Factory Platform: i686 OS/Version: openSUSE 11.0 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gpant(a)htss.com.gr QAContact: jsrain(a)novell.com Found By: --- The icons for the modules are drawn blured on the kicker, this happens for the default Oxygen theme, Crystal Theme and the older Tango Theme. Possible problem is that yast provides a low resolution icon and it is rescaled dithered badly. Observed in b1 and b2. -- 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 14