January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 350079] New: Networking problem with the vif-bridge layout when using NetworkManager in dom0 (Xen)
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350079 Summary: Networking problem with the vif-bridge layout when using NetworkManager in dom0 (Xen) Product: openSUSE 10.3 Version: Final Platform: i386 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: Other I use the vif-bridge layout on my laptop (never tried the other layouts). The interfaces are controlled by NetworkManager and eth0 is my primary interface to the world (although i have a wireless adapter too). eth0 is designated to be xenbr0's interface to the world. When the system is fully started up, the interface eth0 (which is a virtual interface for dom0, and the original eth0 is renamed to peth0) is in the state down, which means that NetworkManager cannot connect. Knetworkmanager showh my wired network as being disconnected. If I start a bridged VM in domU, the guest OS will be able to connect to the network, since peth0 and xenbr0 are up (BTW vif0.0 is also up, but it's not enough for dom0 since eth0 (former veth0 I believe IS DOWN)). See some commend outputs depicting the problem: milleniumfalcon:~ # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.00ffb0e33f6b no vif0.0 peth0 vif1.0 tap0 milleniumfalcon:~ # ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wmaster0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc ieee80211 qlen 1000 link/ieee802.11 00:18:de:a3:12:52 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:18:de:a3:12:52 brd ff:ff:ff:ff:ff:ff 4: peth0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 5: vif0.0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 6: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:17:08:42:e9:36 brd ff:ff:ff:ff:ff:ff 7: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 8: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 9: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 10: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 11: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 12: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 13: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:ff:b0:e3:3f:6b brd ff:ff:ff:ff:ff:ff 14: vif1.0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 32 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 15: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 500 link/ether 00:ff:b0:e3:3f:6b brd ff:ff:ff:ff:ff:ff Fortunately there is a workaround: If I do '/etc/init.d/network restart' NetworkManager will be able to connect: milleniumfalcon:~ # /etc/init.d/network restart Shutting down the NetworkManager done Shutting down the DHCP DBUS Daemon done Shutting down the NetworkManagerDispatcher done Starting the DHCP DBUS Daemon done Starting the NetworkManagerDispatcher done Starting the NetworkManager done milleniumfalcon:~ # ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: wmaster0: <BROADCAST,MULTICAST> mtu 1500 qdisc ieee80211 qlen 1000 link/ieee802.11 00:18:de:a3:12:52 brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:18:de:a3:12:52 brd ff:ff:ff:ff:ff:ff 4: peth0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 5: vif0.0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 6: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:17:08:42:e9:36 brd ff:ff:ff:ff:ff:ff inet 172.23.6.33/22 brd 172.23.7.255 scope global eth0 inet6 fe80::217:8ff:fe42:e936/64 scope link tentative valid_lft forever preferred_lft forever 7: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 8: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 9: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 10: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 11: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 12: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 13: xenbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue link/ether 00:ff:b0:e3:3f:6b brd ff:ff:ff:ff:ff:ff 14: vif1.0: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 32 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff inet6 fe80::fcff:ffff:feff:ffff/64 scope link valid_lft forever preferred_lft forever 15: tap0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 500 link/ether 00:ff:b0:e3:3f:6b brd ff:ff:ff:ff:ff:ff inet6 fe80::2ff:b0ff:fee3:3f6b/64 scope link valid_lft forever preferred_lft forever After the workaround, my computer behaves like without Xen except that eth0's link doesn't go down if I unplug the cable, which is not a wonder since it's connected to the virtual bridge and won't be disconnected by plugging out a cable from the virtual bridge's other port. -- 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 352009] New: date +%W wrong for german locale
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=352009 Summary: date +%W wrong for german locale Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- today (Jan 7) it's the 2nd calendar week in germany (KW 2), but "date +%W" outputs week number 1, even for locale de_DE. LC_ALL=POSIX date +%W 01 LC_ALL=de_DE date +%W 01 according to DIN 1355 / ISO 8601 (http://de.wikipedia.org/wiki/Woche) it should be KW 2 this week. shouldn't this be a topic for l10n ? -- 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 304611] New: DMZ cursor has a bad pixel
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=304611 Summary: DMZ cursor has a bad pixel Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: jimmac(a)novell.com ReportedBy: abockover(a)novell.com QAContact: sndirsch(a)novell.com Found By: --- I noticed my favorite new Jimmac cursors were included in Beta 2, so naturally I changed to them. There is a bad pixel that is very apparent in the default pointer on the right side. Usually it is black, located on the white border, but it changes colors sometimes, depending on where the cursor is moved to on the screen. -- 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 329271] New: GNU units database should be UTF-8
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=329271 Summary: GNU units database should be UTF-8 Product: openSUSE 10.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bj(a)sernet.de QAContact: qa(a)suse.de CC: mfabian(a)suse.de Found By: --- at the moment units database is latin1 encoded: --snip-- # units 2439 units, 71 prefixes, 33 nonlinear units You have: 1°C Unknown unit '°C' --snap-- As UTF-8 is the default please do a recode latin1..utf8 with units.dat. After doing that you might also add this line: € euro to units.dat. -- 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 346862] New: Factory: expert partitioner will only create swap partitions
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=346862 Summary: Factory: expert partitioner will only create swap partitions Product: openSUSE 11.0 Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: harbaugh(a)ncifcrf.gov QAContact: jsrain(a)novell.com Found By: Customer Created an attachment (id=186447) --> (https://bugzilla.novell.com/attachment.cgi?id=186447) jpg of expert partitioner "create a logical partition" screen when attempting to create a partition within the Expert Partitioner, the "Format" box is checked with the filesystem type "swap". Attempting to tab to the field to change the partition type skips to the next field "Start Cylinder". jpg of screen attached. -- 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 7

[Bug 93996] static route add problems
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=93996 User kmachalkova(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=93996#c7 Katarina Machalkova <kmachalkova(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #7 from Katarina Machalkova <kmachalkova(a)novell.com> 2008-01-07 08:00:12 MST --- Fixed in yast2-network 2.16.18 -- 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 0

[Bug 351197] New: several packages use wrong dir for SuSEfirewall2 services files
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351197 Summary: several packages use wrong dir for SuSEfirewall2 services files Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- On my box, the following use the WRONG directory to store their "service" file for SuSEfirewall2 - the correct dir is one of either "/etc/sysconfig/SuSEfirewall2.d/services/" or "/usr/share/SuSEfirewall2/services/". turnip:~ # rpm -qf /etc/SuSEfirewall2.d/services/* xntp-4.2.4p3-25 courier-imap-4.1.3-44 apache2-2.2.4-70.2 turnip:~ # Other packages can easily be found with (assuming /suse/opensuse10.3/ is the root for an OpenSUSE 10.3 repo, DVD image, etc...): find /suse/opensuse10.3/suse/ -type f -name '*.rpm' -exec sh -c "rpm -q --queryformat '[%{=NAME} %{FILENAMES}\n]' -p {} | grep '/etc/SuSEfire'" \; I can supply a list of everything the DVD has that is effected if necessary. -- 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 7

[Bug 350538] New: yast2 repair add fstab entries rename "Repair" and " Cancel" buttons
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350538 Summary: yast2 repair add fstab entries rename "Repair" and "Cancel" buttons Product: openSUSE 11.0 Version: unspecified Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)yahoo.com QAContact: jsrain(a)novell.com Found By: Beta-Customer In the course of the repair run a point is reached where fstab entries are checked. The actions offered are "Repair" and "Cancel", suggesting that a repair is necessary. While reading the accompanying explanatory text,it becomes clear that this may or may not be the case. As in this context "Repair" and "Cancel" are misleading, especially for the casual user, I suggest renaming the buttons to "Change" and "Skip" -- 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 350539] New: yast2 repair remove fstab entries in error
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350539 Summary: yast2 repair remove fstab entries in error Product: openSUSE 11.0 Version: unspecified Platform: x86 OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)yahoo.com QAContact: jsrain(a)novell.com Found By: Beta-Customer In the course of a yast2 repair session a point is reached where fstab entries are checked. It seems that the repair tool does not recognize the new format used recently. My disk has two Windows XP NTFS Partions, fstab entries created during installation and working perfectly well are complained about by yast2 repair. /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 /dev/disk/by-id/scsi-SATA_FUJITSU_MHV2080_NW78T662BLKF-part2 /windows/D ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0 Hardware: Notebook FSC Amilo Si1520 Graphics: Intel 945 GM, LCD 1280*800 Wireless: Intel ipw3945 Sound: Intel ICH7 Desktop: GNOME OS: openSUSE 11.0 (i586) Alpha0 VERSION = 11.0 Kernel: 2.6.24-rc5-git7-2-default rpm -qa | grep yast yast2-trans-wa-2.15.20-2 yast2-trans-cy-2.15.1-34 yast2-trans-pt-2.15.20-2 yast2-trans-zh_CN-2.15.13-2 yast2-control-center-gnome-2.13.2-127 yast2-trans-af-2.15.5-11 yast2-gtk-2.15.9-53 yast2-testsuite-2.16.0-13 yast2-ldap-2.15.1-108 yast2-autofs-2.15.2-95 yast2-control-center-qt-2.16.0-7 yast2-restore-2.16.0-15 yast2-sudo-2.15.3-118 yast2-slide-show-SuSELinux-2.15.16-2 yast2-trans-ar-2.15.4-15 yast2-trans-pot-2.15.2-25 yast2-core-2.16.16-2 yast2-ncurses-2.16.7-3 yast2-sshd-2.16.0-9 yast2-apparmor-2.1-54 yast2-samba-client-2.16.1-13 yast2-ldap-server-2.15.5-104 yast2-storage-evms-2.16.7-2 yast2-trans-bg-2.15.6-2 yast2-trans-hr-2.15.20-2 yast2-trans-vi-2.15.1-34 yast2-trans-pa-2.15.12-11 yast2-pkg-bindings-2.16.7-2 yast2-firewall-2.15.8-35 yast2-printer-2.16.6-7 yast2-kerberos-client-2.16.1-3 yast2-kerberos-server-2.16.0-11 yast2-inetd-2.15.1-72 yast2-printer-devel-doc-2.16.6-7 yast2-trans-xh-2.13.10-2 yast2-trans-zu-2.13.11-2 yast2-trans-stats-2.15.0-46 yast2-trans-ja-2.15.10-2 yast2-CASA-1.7.1461-41 yast2-iscsi-server-2.14.3-115 yast2-tv-2.16.0-27 yast2-dirinstall-2.16.0-13 yast2-installation-2.16.8-2 autoyast2-2.16.3-3 yast2-trans-en_US-2.15.5-19 yast2-trans-de-2.15.29-2 yast2-trans-it-2.15.13-2 yast2-trans-ka-2.15.1-31 yast2-transfer-2.16.0-4 yast2-x11-2.15.11-56 yast2-ldap-client-2.16.5-3 yast2-nfs-client-2.15.0-52 yast2-network-2.16.17-3 yast2-nis-server-devel-doc-2.16.0-31 yast2-casa-ats-1.7.1451-70 yast2-storage-devel-2.16.7-2 yast2-trans-tr-2.15.2-11 yast2-trans-zh_TW-2.15.13-2 yast2-trans-pl-2.15.14-2 yast2-trans-lt-2.15.12-2 yast2-trans-sr-2.15.3-2 yast2-trans-ko-2.15.5-2 yast2-trans-id-2.15.1-34 yast2-xml-2.16.0-10 yast2-add-on-creator-2.16.3-3 yast2-bluetooth-2.15.4-46 yast2-iscsi-client-2.16.2-9 yast2-repair-2.16.2-14 yast2-http-server-2.15.9-4 yast2-theme-openSUSE-2.16.2-2 yast2-trans-nb-2.15.12-2 yast2-trans-en_GB-2.15.6-2 yast2-trans-ta-2.15.5-11 yast2-country-data-2.16.4-3 yast2-trans-ro-2.15.26-2 yast2-trans-ru-2.15.26-2 yast2-trans-nl-2.15.12-2 yast2-trans-mr-2.15.5-11 yast2-trans-lo-2.15.1-31 yast2-core-devel-2.16.16-2 yast2-2.16.18-3 yast2-slp-server-2.15.0-70 yast2-runlevel-2.16.0-15 yast2-multipath-2.13.0-113 yast2-instserver-2.15.4-69 yast2-ntp-client-2.16.2-9 yast2-bootloader-2.16.3-3 yast2-tune-2.15.7-51 yast2-product-creator-2.16.6-4 yast2-samba-server-2.16.0-27 yast2-storage-2.16.7-2 yast2-metapackage-handler-0.7.3-13 yast2-trans-cs-2.15.14-2 yast2-network-devel-doc-2.16.17-3 yast2-trans-fi-2.15.22-2 yast2-trans-sk-2.15.14-2 yast2-trans-da-2.15.14-2 yast2-trans-bs-2.15.1-34 yast2-trans-et-2.15.12-2 yast2-tftp-server-2.14.0-132 yast2-security-2.15.1-52 yast2-ruby-bindings-0.2.0-29 yast2-python-bindings-2.16.2-5 yast2-drbd-2.13.1-78 yast2-scanner-2.15.5-70 yast2-control-center-2.16.0-7 yast2-mouse-2.16.0-13 yast2-update-2.16.1-15 yast2-update-FACTORY-2.16.1-15 yast2-mail-2.15.23-34 yast2-ftp-server-2.15.9-55 yast2-trans-fr-2.15.17-2 yast2-devtools-2.16.3-5 yast2-ca-management-2.16.4-3 yast2-sysconfig-2.15.3-85 yast2-fingerprint-reader-2.16.2-3 yast2-users-2.16.5-3 yast2-live-installer-2.16.1-13 yast2-storage-lib-2.16.7-2 yast2-trans-gu-2.13.6-11 yast2-trans-bn-2.15.7-11 yast2-trans-es-2.15.7-2 yast2-trans-pt_BR-2.15.15-2 yast2-trans-allpacks-2.15.0-48 yast2-country-2.16.4-3 yast2-squid-2.16.0-23 yast2-online-update-2.16.6-3 yast2-online-update-frontend-2.16.6-3 yast2-backup-2.16.1-3 yast2-firstboot-2.16.2-16 yast2-trans-km-2.15.28-2 yast2-trans-jv-2.15.1-31 yast2-trans-uk-2.15.23-2 yast2-trans-fa-2.15.1-31 yast2-irda-2.15.1-122 yast2-isns-1.0.4-34 yast2-registration-2.16.0-15 autoyast2-installation-2.16.3-3 yast2-dhcp-server-2.15.5-47 yast2-trans-sl-2.15.4-2 yast2-trans-el-2.15.14-2 yast2-trans-sv-2.15.12-2 yast2-trans-ca-2.15.4-11 yast2-slp-2.15.0-59 yast2-pkg-bindings-devel-doc-2.16.7-2 yast2-packager-2.16.12-3 yast2-support-2.15.3-42 yast2-mcs-plugin-0.1.0-64 yast2-kdump-2.16.8-3 yast2-profile-manager-2.16.0-14 yast2-qt-2.16.11-2 yast2-trans-gl-2.15.1-34 yast2-trans-si-2.15.2-34 yast2-trans-hi-2.15.6-11 yast2-trans-hu-2.15.18-2 yast2-perl-bindings-2.16.0-29 yast2-devel-doc-2.16.18-3 yast2-nfs-server-2.15.4-52 yast2-nis-server-2.16.0-31 yast2-phone-services-2.15.0-108 yast2-schema-2.15.0-156 yast2-trans-mk-2.15.2-2 yast2-mail-plugins-2.15.23-34 yast2-hardware-detection-2.16.0-7 yast2-sound-2.16.1-17 yast2-pam-2.16.0-24 yast2-nis-client-2.16.0-23 yast2-dns-server-2.16.1-3 yast2-add-on-2.16.0-22 -- 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 37

[Bug 351011] New: problem installing openSUSE 11 by NET in HP pavillion dv2000
by bugzilla_noreply＠novell.com 07 Jan '08

07 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351011 Summary: problem installing openSUSE 11 by NET in HP pavillion dv2000 Product: openSUSE 11.0 Version: unspecified Platform: HP OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jmolles(a)vodafone.es QAContact: jsrain(a)novell.com Found By: --- Hi all I try to install openSUSE from factory by NET and instalations stops because there are a software conflict and can't goes forward. Well the error is that seems openSUSE-FTP-NonOSS have conflicting with openSUSE factory and as I can`t resolve this confict because I have no options to do it, well I can't complet the instalation. Any idea? 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 2