- openSUSE Bugs

[Bug 197190] IA64: Xserver shutdown freezes machine w/ R420 + flat panels
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=197190 ------- Comment #69 from mhopf(a)novell.com 2006-12-19 06:50 MST ------- See Bug #197572, patch p_pci-domain.diff, compare comments 22 + 27. I'm sorry, I don't remember the exact circumstances. -- 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 0

[Bug 211867] New: SuSE Linux IP stack sets Don't Fragment flag on UDP datagrams.
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=211867 Summary: SuSE Linux IP stack sets Don't Fragment flag on UDP datagrams. Product: SUSE Linux 10.1 Version: Final Platform: x86 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fdjongh(a)novell.com QAContact: qa(a)suse.de The Don't Fragment flag is meant for Path MTU discovery. Unlike TCP, UDP does not support Path MTU Discovery, since UDP does not packetize data into segments. Section 6.1 on page 9 of RFC 1191 reads the following about this topic: "We do not want the IP layer to simply set the DF bit in every packet, since it is possible that a packetization layer, perhaps a UDP application outside the kernel, is unable to change its datagram size." However, the SuSE Linux TCP/IP stack sets the DF bit in every datagram, unless Path MTU discovery is disabled by the sysctl parameter 'ip_no_pmtu_disc'. Of course, disabling Path MTU Discovery is not a solution, because Path MTU Discovery is very useful for performance of TCP connections, since it avoids fragmentation and reassembly. Especially fragmentation can put a heavy load on routers. The IP stack should only set the DF bit on datagrams that carry TCP segments, unless a UDP application specifically requests to set it with socket initialization. From the ip manual page in section 7 I understand that the IP stack allows applications to choose whether they want Path MTU Discovery per IP_MTU_DISCOVER socket option. As this manual page also reads that, in case 'ip_no_pmtu_disc' is false, the IP stack is supposed to only enable Path MTU Discovery with SOCK_STREAM (TCP) sockets, and to disable it on all others, I have no doubt that the actual behaviour of the IP stack is not in conformance with the intended, documented behaviour and RFC 1191. Please note that setting the DF flag with UDP datagrams will cause connectivity problems on UDP connections that cross a network path with links that support a smaller MTU than the local segment of the SuSE Linux host, if the concerning UDP application does not support Path MTU Discovery. Most UDP applications do not support Path MTU Discovery. Although I report this bug for SuSE Linux 10.1, the same defect is in every SuSE Linux distribution. -- 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 6

[Bug 197190] IA64: Xserver shutdown freezes machine w/ R420 + flat panels
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=197190 ------- Comment #68 from sndirsch(a)novell.com 2006-12-19 06:44 MST ------- Ok. I've reverted this change. -- 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 0

[Bug 229284] New: yast2 software installation source information unusable
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=229284 Summary: yast2 software installation source information unusable Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: misc(a)dstoecker.de QAContact: jsrain(a)novell.com When I click on the versions (Versionen) tab of a RPM package in software installation the installation sources (Installationsquelle) are shown. Anyway a information like 20061213-165326 or 20061213-165408 is not really helpful. Here the URL of the source should be displayed (inaccuracies in naming are due to backtranslating from German). At the moment it is not possible to find out, where a RPM package will be or was installed from. -- 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 3

[Bug 197190] IA64: Xserver shutdown freezes machine w/ R420 + flat panels
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=197190 ------- Comment #67 from mhopf(a)novell.com 2006-12-19 05:30 MST ------- Do not apply; Domain 0 is really considered special, not only in this piece of sh^H^Hcode but also in other parts of the Xserver. I've already tested exactly this approach, it failed. -- 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 0

[Bug 229586] New: g77 fails when buildin executable
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=229586 Summary: g77 fails when buildin executable Product: openSUSE 10.2 Version: Final Platform: i386 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: francesco.teodori(a)gmail.com QAContact: qa(a)suse.de The compiler cannot find the library libgcc_s.so.1. I had to create a symbolic link ln -s libgcc_s.so.1 libgcc_s.so After that the compiler works appropriately -- 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 1

[Bug 227385] New: fc-cache always fails with error "(dir): failed to write cache"
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=227385 Summary: fc-cache always fails with error "(dir): failed to write cache" Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: sndirsch(a)novell.com ReportedBy: belphegor(a)belbel.or.jp QAContact: sndirsch(a)novell.com This is an system which upgraded from 10.1 (final release with many patches) to 10.2 (final release). When I started the application "fc-cache", many errors occured as follows. --- /usr/share/fonts: failed to write cache /usr/share/fonts/100dpi: failed to write cache /usr/share/fonts/75dpi: failed to write cache /usr/share/fonts/CID: failed to write cache /usr/share/fonts/CID/Adobe-CNS1: failed to write cache /usr/share/fonts/CID/Adobe-CNS1/AFM: failed to write cache /usr/share/fonts/CID/Adobe-CNS1/CFM: failed to write cache (...) /usr/share/fonts/Speedo: failed to write cache /usr/share/fonts/Type1: failed to write cache /usr/share/fonts/URW: failed to write cache /usr/share/fonts/cyrillic: failed to write cache /usr/share/fonts/encodings: failed to write cache --- And this may be an additional information, "fc-list" takes too long time. On openSUSE 10.1 system, "fc-list" takes about <1 sec, But on openSUSE 10.2 system, "fc-list" takes about 30 sec. I think that this problem was caused by this (fc-cache) failure. -- 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 12

[Bug 217425] New: Installation stops with one package
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=217425 Summary: Installation stops with one package Product: openSUSE 10.2 Version: Beta 1 Platform: 32bit OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: timmi(a)gmx-topmail.de QAContact: jsrain(a)novell.com CC: timmi(a)gmx-topmail.de I'm installing 32 bit version of beta1 (CD-check during installation okay). For a while, the installation works, but then appears a message that a certain package can't be installed (see attached screenshot.png). "Retry" doesn't change nothing: the same message is displayed another time. "Abort" and "Ignore" do both the same thing: yast is closed and I see linuxrc, displaying a message that an error during the installation occurred. The problem does occur each time with another package, but until now I never got installed the beta completely. -- 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 30

[Bug 229385] New: Synaptics Touchpad does not work properly on Pavilion dv5000z --loses bytes
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=229385 Summary: Synaptics Touchpad does not work properly on Pavilion dv5000z --loses bytes Product: openSUSE 10.2 Version: Final Platform: All OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: starfrost(a)gmail.com QAContact: qa(a)suse.de Upon a fresh install of openSuse 10.2, I found that the touchpad often would randomly "stick" or freeze. Dmesg output: psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: issuing reconnect request psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched. psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: issuing reconnect request psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 - driver resynched. psmouse.c: Failed to reset mouse on isa0060/serio1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 4 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: issuing reconnect request input: PS/2 Generic Mouse as /class/input/input6 psmouse.c: Failed to enable mouse on isa0060/serio1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at byte 1 (etc.) output of cat /proc/bus/input/devices I: Bus=0010 Vendor=001f Product=0001 Version=0100 N: Name="PC Speaker" P: Phys=isa0061/input0 S: Sysfs=/class/input/input0 H: Handlers=kbd event0 B: EV=40001 B: SND=6 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/class/input/input1 H: Handlers=kbd event1 B: EV=120013 B: KEY=1004 2200002 3802078 f950d401 feffffdf ffefffff ffffffff ffffffff B: MSC=10 B: LED=7 I: Bus=0011 Vendor=0002 Product=0007 Version=0000 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio4/input0 S: Sysfs=/class/input/input2 H: Handlers=mouse0 event2 B: EV=b B: KEY=6420 0 70000 0 0 0 0 0 0 0 0 B: ABS=11000003 I: Bus=0011 Vendor=0002 Product=0001 Version=0000 N: Name="PS/2 Generic Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/class/input/input6 H: Handlers=mouse1 event3 B: EV=7 B: KEY=70000 0 0 0 0 0 0 0 0 B: REL=3 I am using an HP Pavilion dv5000z, AMD Sempron 3300+. -- 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 1

[Bug 228709] New: rdesktop-1.5.0-20: comparison with string literal
by bugzilla_noreply＠novell.com 19 Dec '06

19 Dec '06

https://bugzilla.novell.com/show_bug.cgi?id=228709 Summary: rdesktop-1.5.0-20: comparison with string literal Product: openSUSE 10.3 Version: unspecified Platform: All OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dcb314(a)hotmail.com QAContact: qa(a)suse.de I just tried to compile package rdesktop-1.5.0-20 The compiler said printer.c:113: warning: comparison with string literal The source code is if (pprinter_data->printer == "mydeskjet") Suggest new code if (strcmp( pprinter_data->printer, "mydeskjet") == 0) -- 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 4