January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 286591] New: headphone jack mode, mic/ line jack mode are not preserved over suspend/resume cycles
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=286591 Summary: headphone jack mode, mic/line jack mode are not preserved over suspend/resume cycles Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: teheo(a)novell.com QAContact: qa(a)suse.de Found By: --- After suspend/resume cycle, headphone jack mode and mic/jack mode are reset to line in/line out regardless of the setting prior to suspend. If mixer software is open over suspend/resume, the changed status is not updated in the mixer making things more confusing. Will attach 'hwinfo --all'. -- 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 345459] New: Stacking of Khmer letters broken in qt 3.3.8
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=345459 Summary: Stacking of Khmer letters broken in qt 3.3.8 Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: bart(a)geesink.org QAContact: qa(a)suse.de Found By: --- In Khmer, letters can be stacked. Up to three letters can be stacked. So if you type a consonant, followed by a consonant, this second consonant changes to a subscript and is placed below the first consonant. If this is followed by a vowel, the vowel will be placed under the two already stacked letters. This is broken in QT 3.3.8. The third letter (the consonant) does not show at all. I have looked in the QT 3.3.8 changelog, which says this: - Fixed rendering of text with stacking diacritics. Sounds to me this is the source of the problem. We tried to address this issue with the guys at Trolltech, but they stated that QT3 is not supported anymore, and they cannot fix it. So we decided to find the source of the problem. I took the QT 3.3.8 source RPM and I replaced the relevant file which does the fontrendering (qt-x11-free-3.3.8/src/kernel/qfontengine_x11.cpp) with the file from QT 3.3.7. After recompiling and installing the problem was fixed. A diff between qfontengine_x11.cpp from qt 3.3.7 and qt 3.3.8 only shows a couple of lines difference. As qt3 will be in openSUSE 11.0, this is quite an important problem for us, since 10.3 has been unusable with Khmer because of this problem. Is this fixable? -- 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 351900] New: GTK version YaST2 - statusbars always take fokus
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351900 Summary: GTK version YaST2 - statusbars always take fokus Product: openSUSE 10.3 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: de(a)lincomp.eu QAContact: jsrain(a)novell.com Found By: --- Within the GTK version of YaST2 subprocess like process bars (during updating repository cache, e.g.) always take focus. This is very disturbing if you e.g. try to work with OOo during an online update. The process bars should respect the focus of their parents. Best Regards Marcus -- 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

[Bug 352873] New: No flash with konqueror
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=352873 Summary: No flash with konqueror Product: openSUSE 10.2 Version: Final Platform: 32bit OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lars.behrens(a)pi.uka.de QAContact: qa(a)suse.de Found By: Customer Flash on websites doesn't work in konqueror 3.5.5 (KDE 3.5.5 "release 45.6 openSUSE 10.2). Independent of website. In Firefox all woks well. Lars Behrens -- 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

[Bug 352300] New: jpackage-utils install failed
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=352300 Summary: jpackage-utils install failed Product: openSUSE 11.0 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: aj(a)novell.com QAContact: qa(a)suse.de Found By: --- with current factory and a fresh install, I get a failure installing jpackage-utils: rpm output: error: %post(jpackage-utils-1.7.3-3.i586) scriptlet failed, exit status 127 -- 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 344356] New: using ntpd, some times the clock starts to go slow.
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=344356#c2 Summary: using ntpd, some times the clock starts to go slow. Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- Sometimes, I see messages like this in the kernel log: Nov 27 15:27:32 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB] Nov 27 15:57:46 nimrodel kernel: set_rtc_mmss: can't update from 1 to 57 Nov 27 15:58:00 nimrodel syslog-ng[10590]: last message repeated 13 times Nov 27 15:58:00 nimrodel kernel: set_rtc_mmss: can't update from 1 to 58 Nov 27 15:58:03 nimrodel syslog-ng[10590]: last message repeated 3 times Nov 27 15:58:04 nimrodel kernel: set_rtc_mmss: can't update from 1 to 58 Nov 27 15:58:04 nimrodel kernel: set_rtc_mmss: can't update from 1 to 58 Nov 27 15:58:06 nimrodel kernel: set_rtc_mmss: can't update from 2 to 58 Nov 27 15:59:00 nimrodel syslog-ng[10590]: last message repeated 53 times Nov 27 15:59:00 nimrodel kernel: set_rtc_mmss: can't update from 2 to 59 Nov 27 15:59:03 nimrodel syslog-ng[10590]: last message repeated 3 times Nov 27 15:59:04 nimrodel kernel: set_rtc_mmss: can't update from 2 to 59 Nov 27 15:59:04 nimrodel kernel: set_rtc_mmss: can't update from 2 to 59 Nov 27 15:59:06 nimrodel kernel: set_rtc_mmss: can't update from 3 to 59 Nov 27 16:00:03 nimrodel syslog-ng[10590]: last message repeated 15 times (no more entries in 90 minutes) About the same period, ntp stops being able to maintain sync, and aborts: 27 Nov 15:27:38 ntpd[12905]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) 27 Nov 15:27:38 ntpd[12905]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:38 ntpd[12905]: Deleting interface #2 lo, ::1#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs 27 Nov 15:27:38 ntpd[12905]: Deleting interface #3 eth0, fe80::240:f4ff:fe2e:b121#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs 27 Nov 15:27:42 ntpd[12905]: peer 91.121.2.175 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:44 ntpd[12905]: peer 195.55.174.243 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:45 ntpd[12905]: peer 80.33.107.110 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:45 ntpd[12905]: peer 217.155.68.49 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:45 ntpd[12905]: peer 84.88.69.10 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:46 ntpd[12905]: peer 88.191.19.23 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:27:46 ntpd[12905]: peer 192.33.214.57 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 15:30:51 ntpd[12905]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_local_proto, 2 events, event_restart' (0xc521) 27 Nov 15:30:51 ntpd[12905]: synchronized to LOCAL(0), stratum 10 27 Nov 15:30:51 ntpd[12905]: kernel time sync status change 0001 27 Nov 15:30:51 ntpd[12905]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_local_proto, 3 events, event_peer/strat_chg' (0x534) 27 Nov 15:30:51 ntpd[12905]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_local_proto, 4 events, event_sync_chg' (0x543) 27 Nov 15:31:56 ntpd[12905]: synchronized to 91.121.2.175, stratum 2 27 Nov 15:38:31 ntpd[12905]: synchronized to 192.33.214.57, stratum 2 27 Nov 15:39:25 ntpd[12905]: synchronized to 195.55.174.243, stratum 2 27 Nov 15:39:40 ntpd[12905]: synchronized to LOCAL(0), stratum 10 27 Nov 16:22:22 ntpd[12905]: synchronized to 84.88.69.10, stratum 2 27 Nov 16:22:22 ntpd[12905]: time correction of 1678 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. 27 Nov 16:22:22 ntpd[12905]: system event 'event_fault' (0x02) status 'leap_none, sync_ntp, 12 events, event_peer/strat_chg' (0x6c4) Then I have to restart it to force a time set: 27 Nov 17:13:54 ntpd[18877]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) 27 Nov 17:13:55 ntpd[18877]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 27 Nov 17:13:55 ntpd[18877]: Deleting interface #2 lo, ::1#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs The clock was going about half an hour slow - during my lunch hour! This thing started happening with 10.3, and is random. Normally, I'm not present or watching when it happens. Once I was scanning a page via a usb scanner, and the desktop froze. Sometimes the desktop freezes (the cpu applet and other things stop) till I press any key or move the mouse. Once the keyboard froze for 5 minutes (gkrelmn showed activity), and suddenly started working again, after 5 minutes, just as I had booted up a second computer and I was ready to try sshing (didn't have to). I tell all these things, but I don't know if they are related. I have also tried recompiling the kernel. One possibility is that all the time servers I use go bad and miss-set my clock (ntp goes to LOCAL(0)). Another is that the kernel clock doesn't respond well. I already have "logconfig =all" in "/etc/ntp.conf" and: KERNEL_LOGLEVEL=7 so I don't know what to activate to get more info about the problem. -- 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 21

[Bug 271198] New: /etc/init.d/java.binfmt_misc too chatty
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=271198 Summary: /etc/init.d/java.binfmt_misc too chatty Product: openSUSE 10.3 Version: Alpha 3plus Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de Just seen when updating factory rpms: 34:jpackage-utils ########################################### [ 44%] Starting java.binfmt_misc none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) done /etc/init.d/java.binfmt_misc should use 'grep -q' or just retest the presence of /proc/sys/fs/binfmt_misc/register. -- 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 13

[Bug 349896] New: YaST2' s partition manager creates every raid5 array with left-symmetric layout
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=349896 Summary: YaST2's partition manager creates every raid5 array with left-symmetric layout Product: openSUSE 10.3 Version: Final Platform: PC OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: jsrain(a)novell.com Found By: Other It show the other possible layouts too, but choosing another one seems to have no effect for me. The array created will be left symmetric. -- 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 329655] New: Cannot boot if SUSE has / on an USB external hard drive
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=329655 Summary: Cannot boot if SUSE has / on an USB external hard drive Product: openSUSE 10.3 Version: RC 1 Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giosif(a)ase.ro QAContact: jsrain(a)novell.com Found By: --- Hello, While installing OpenSUSE 10.3 RC1, I used an LVM group on an USB external hard drive for creating the root partition. The first part of the setup (until the first reboot) went without problems, but, after rebooting, the root partition would not be detected any more. After some troubleshooting, I found out that the script that activates the LVM group (/boot/62-lvm2.sh) is run BEFORE the USB subsystem had time to finish detecting all attached devices (especially, but not limited to, when using external USB hubs). The way I solved the problem was by inserting a /bin/sleep 10 line in the /boot/62-lvm2.sh file from the initrd, right before the following statement: for vgr in $lvm $vg_root $vg_roots; do vgchange -a y $vgr done Now, although this solved my particular problem, I think you should consider the delay (that the USB subsystem introduces while scanning and detecting devices) in a more general manner (I haven't figured it out when exactly does the boot process activate the USB subsystem - 04-udev.sh maybe ?) because it may affect other installation scenarios as well (external USB drive with no LVM, or with software RAID). The problem was also present in Beta 3 but I didn't have the time to troubleshoot. Cheers, George Iosif -- 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 350300] New: SuSE Linux 10.1 mirrors are not up to date.
by bugzilla_noreply＠novell.com 10 Jan '08

10 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=350300 Summary: SuSE Linux 10.1 mirrors are not up to date. Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: SuSE-User02(a)TheMoreIKnow.info QAContact: jsrain(a)novell.com Found By: Customer A number of SuSE Linux 10.1 mirrors are over a month old. Since this is a problem affecting multiple mirrors, there must be some problem on the master server. http://ftp.suse.com/pub/suse/update/10.1/repodata/ shows files as current as 21-Dec-2007. These mirrors show files as current as 19-Nov-2007 (or older): http://spout.ussg.indiana.edu/linux/suse/suse/update/10.1/repodata/ http://mirror.anl.gov/pub/suse/update/10.1/repodata/ ftp://suse.mirrors.tds.net/pub/suse/update/10.1/repodata ftp://mirrors.kernel.org/suse/update/10.1/repodata -- 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