September 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 612859] New: Incoming 802.1q tagged packets can't be seen by tcpdump or wireshark
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=612859 http://bugzilla.novell.com/show_bug.cgi?id=612859#c0 Summary: Incoming 802.1q tagged packets can't be seen by tcpdump or wireshark Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.2 Firefox/3.6.3 Please note that this report is for SLES 11 SP1 I'm using the x86_64 version of SLES 11 SP1 on a HP ProLiant DL180 G6 server. Ethernet interface type of the server NC362i (made by Intel, I assume), and its driver is the 'igb' kernel module. The NIC has two gigabit interfaces, eth0 and eth1 which are actually enclosed in a bonding driver which, in turn has a 802.1q tagged subinterface, which is connected to a virtual bridge, which is the default ethernet interface of the system. Before upgrading from plain SLES11 (with the exact same configuration) I was able to monitor all the network traffic on the phyisical interfaces, but now incoming 802.1q tagged packets are invisible to tcpdump and wireshark, however, they can be observed on all the virtual interfaces (bonding, 802.1q and bridge), and thay arrive to the applications too. Outgoing and untagged packets can be observed correctly. 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 612065] New: NFS hang
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=612065 http://bugzilla.novell.com/show_bug.cgi?id=612065#c0 Summary: NFS hang Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: SLED 11 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: R.Eggermont(a)TUDelft.nl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.2 Firefox/3.6.3 We are experiencing (endless) hangs of NFS (v4) tcp connections in the FIN_WAIT2 state on multiple clients in out network. These connections don't time out, and neither do programs that have files open on the NFS mount. The hangs coincide with "nfs: server <x> not responding, still trying" and "nfs: server <x> not responding, timed out" entries in the log. In network traces on the client, we see the client ending the connection (seemingly in the middle of a conversation). The client receives an ACK from the server, but not a FIN. The clients are not sending out any retries for this connection (as expected). It is possible to terminate the connections by spoofing a FIN packet from the server. After that, new connections are working fine. The hang in the FIN_WAIT2 state seems correct, but counter-productive for a connection that is being terminated, as there is no way for the connection to get out of this state. I feel the user would be better served with a time-out on the FIN_WAIT2 state. Reproducible: Always Steps to Reproduce: Ideally (haven't tried): 1. Make an NFS (v4, sec=krb5) tcp connection to a server. 2. Make the NFS client terminate the connection. 3. Block the FIN packet from the server. Real-life (with hangs on ~50 out of ~300 clients): 1. Make an NFS (v4, sec=krb5) tcp connection to a server. 2. Overload the network(firewall?), causing the client to terminate the connection. 3. Let the network(firewall?) drop or block the FIN packet from the server. Actual Results: The connection hangs forever in the FIN_WAIT2 state. Expected Results: The connection is terminated after a time out in the FIN_WAIT2 state. This happened on 64-bit openSUSE 10.3 and SLED 11 clients (including SLED 11 kernel 2.6.27.45-0.1-default). -- 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 581526] New: X not starting on my laptop with intel gma hd graphics
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=581526 http://bugzilla.novell.com/show_bug.cgi?id=581526#c0 Summary: X not starting on my laptop with intel gma hd graphics Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ruchir.brahmbhatt(a)ecosmob.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9 (KHTML, like Gecko) Chrome/5.0.307.9 Safari/532.9 I was trying to boot kde4 X86_64 live cd on my dell inspiron 1464 laptop. I started in live cd mode. After startup when it tries to start kdm, it shows blank screen which looks like X not starting properly. Reproducible: Always Steps to Reproduce: 1. Boot kde4 live cd on system having intel gma hd graphics Actual Results: X not starting Expected Results: KDM should show up. -- 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 568114] New: Installer does not recognize MD raid volumes properly
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=568114 http://bugzilla.novell.com/show_bug.cgi?id=568114#c0 Summary: Installer does not recognize MD raid volumes properly Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: erik.kjellson(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=334863) --> (http://bugzilla.novell.com/attachment.cgi?id=334863) y2 logs and screenshots from the installer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.16) Gecko/2009120200 SUSE/3.0.16-0.1 Firefox/3.0.16 In the partitioning phase of the installer: A. The "RAID Type" of the volume /dev/mdX is "RAID_UNKNOWN" for the MD raid5 volumes. For the MD raid1 volume /dev/md0 it is "RAID1" though. B. The individual partitions are only shown for one of my four HDDs (i.e. /dev/sdd), even though all four disks are partitioned in the same way. C. The raid volumes are shown as both /dev/mdX and /dev/mapper/isw_XXX... I guess that the raid volumes are assumed to be both MD and DM raid at the same time. Reproducible: Always Steps to Reproduce: 1. Choose new installation 2. Choose either to edit the proposed partition setup or creating a new one, it doesn't seem to matter. I currently have openSuse 11.0 installed, but the raid volumes were created in an earlier version of openSuse, probably 10.2. -- 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 293977] kernel-debug fails in early boot
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=293977 https://bugzilla.novell.com/show_bug.cgi?id=293977#c8 Jeff Mahoney <jeffm(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #8 from Jeff Mahoney <jeffm(a)novell.com> 2010-09-20 18:03:18 UTC --- Apologies, this report was assigned but work didn't progress on it. Now that openSUSE 10.2 is out of maintenance, we'll have to close it as WONTFIX. If you are able to reproduce with openSUSE 11.3 or openSUSE Factory, please re-open. -- 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 640399] New: "zypper in -t patch timezone-2010l" doesn't find patch
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=640399 https://bugzilla.novell.com/show_bug.cgi?id=640399#c0 Summary: "zypper in -t patch timezone-2010l" doesn't find patch Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- Created an attachment (id=390387) --> (http://bugzilla.novell.com/attachment.cgi?id=390387) zypper.log.bz2 > zypper lp Loading repository data... Reading installed packages... Repository | Name | Version | Category | Status --------------+----------------+---------+-------------+------- Updates [...] | kernel | 3105 | security | needed Updates [...] | timezone-2010l | 3011 | recommended | needed > zypper in -t patch timezone-2010l Loading repository data... Reading installed packages... Patch 'timezone' not found. <------------ Resolving package dependencies... Nothing to do. The reason for this bug is quite obvious when looking at the output above and also in zypper.log (full log attached): [zypper] PackageArgs.cc(argsToCaps):239 got wanted 'patch:timezone == 2010l'; Obviously zypper splits the patch name at the "-" and things everything on the right side is a version number. There are two options how this bug can be solved: a) let zypper search for the full name (as given on the commandline) first, before splitting it into name and version b) forbid usage of "-" in patch names BTW: zypper in -t patch timezone-2010l-3011 fails with the same error message. -- 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 551746] New: Booting hangs setting RTC. Last message rtc0 alarms up to one month
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=551746 Summary: Booting hangs setting RTC. Last message rtc0 alarms up to one month Classification: openSUSE Product: openSUSE 11.2 Version: RC 2 Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: support(a)microtechniques.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) On several HP systems the boot process would freeze setting the RTC. The last message on the screen was- rtc0 alarms up to one month. If I waited long enough - say 10 minutes - the process would eventually continue. It happened about 80% of the time. I disabled the boot.clock startup process, and the machines booted normally. I just retested with latest build, and the problem did not seem to reoccur. Reproducible: Sometimes 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 9

[Bug 503446] New: No acpi event received when pressing power button on T60p
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

http://bugzilla.novell.com/show_bug.cgi?id=503446 Summary: No acpi event received when pressing power button on T60p Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- On my thinkpad T60p, when I press the button, I can't get gnome-power-manager to do any action. Thanks to Timo, I saw that I actually don't see any event in "lshal -m" or "acpi_listen" for this -- I saw events when pressing volume down, though. So it appears that this would be a ACPI 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 3

[Bug 484346] acpi information about battery and ac_adapter gets lost after some time
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=484346 https://bugzilla.novell.com/show_bug.cgi?id=484346#c39 Jeff Mahoney <jeffm(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #39 from Jeff Mahoney <jeffm(a)novell.com> 2010-09-20 17:39:37 UTC --- Apologies, this report was assigned but work didn't progress on it. Now that openSUSE 11.2 is in security/data corruption maintenance-only mode, we'll have to close it as WONTFIX. If you are able to reproduce with openSUSE 11.3 or openSUSE Factory, please re-open. -- 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 640587] New: empathy: Fails to connect to im.novell.com:443
by bugzilla_noreply＠novell.com 20 Sep '10

20 Sep '10

https://bugzilla.novell.com/show_bug.cgi?id=640587 https://bugzilla.novell.com/show_bug.cgi?id=640587#c0 Summary: empathy: Fails to connect to im.novell.com:443 Classification: openSUSE Product: openSUSE 11.4 Version: Milestone 1 of 6 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: bphilips(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- Identical to this issue: https://bugs.launchpad.net/empathy/+bug/417432 0) Launch empathy 1) Add Groupwise account 2) Configure im.novell.com and 443 3) Fails to connect 4) cp .purple/certificates/x509/tls_peers/im.novell.com /tmp/haze-UzIht7/certificates/x509/tls_peers/ 5) Reconnect and SUCCESS -- 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