January 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 218177] New: "/etc/cron.d/suse.de-clean-core" from findutils-locate-4.2.28-16 doesn't identify core dumps reliably
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=218177 Summary: "/etc/cron.d/suse.de-clean-core" from findutils-locate- 4.2.28-16 doesn't identify core dumps reliably Product: openSUSE 10.2 Version: Beta 1 plus Platform: i586 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreas.bolsch(a)alumni.tu-berlin.de QAContact: qa(a)suse.de The script may easily identify non-core files as core dumps. "locate '*/core' '*/core.[0-9]*'" and "find "$COREFILE" $ -name core -o -regex ".*/core\\.[0-9]+" $ -type f" hits arbitrary files named "core". Although there is an improvement over SuSE 10.1 (where /usr/share/man/man5/core.5.gz got found and *deleted*), it's still not quite safe. Furthermore, using "safe-rm" instead of the plain "rm" might be a good idea. Suggested fix: --- suse.de-clean-core 2006-10-31 01:23:04.000000000 +0100 +++ suse.de-clean-core.new 2006-11-04 17:21:37.000000000 +0100 @@ -49,18 +49,15 @@ for i in $(find "$COREFILE" ! $ -fstype nfs -o -fstype NFS $ \ $ -name core -o -regex ".*/core\\.[0-9]+" $ -type f \ -mtime +"$MAX_DAYS_FOR_CORE" 2> /dev/null); do - if [ "$DELETE_OLD_CORE" = yes ]; then - echo "Deleting core file older than $MAX_DAYS_FOR_CORE days: $i" if [ -x /usr/bin/file ]; then - echo file "$i" - /usr/bin/file "$i" - fi - rm -f "$i" + FILE=`/usr/bin/file $i` + if `echo $FILE | egrep -i -q 'core (file|dump)'`; then + if [ "$DELETE_OLD_CORE" = yes ] && [ -x /usr/bin/safe-rm ]; then + echo "Deleting core file older than $MAX_DAYS_FOR_CORE days: $FILE" + /usr/bin/safe-rm "$i" else - echo "Found core file older than $MAX_DAYS_FOR_CORE days: $i" - if [ -x /usr/bin/file ]; then - echo file "$i" - /usr/bin/file "$i" + echo "Found core file older than $MAX_DAYS_FOR_CORE days: $FILE" + fi fi fi done -- 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 2

[Bug 173361] kpowersave: CPU frequency missing
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=173361 ------- Comment #8 from seife(a)novell.com 2007-01-09 04:58 MST ------- ACK. Just left-click the kpowersave icon to get a continously updated, up-to-date view of the system state. Click again and it is gone. Even faster than waiting for the tooltip to appear :-)) -- 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 173361] kpowersave: CPU frequency missing
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=173361 dkukawka(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife(a)novell.com Status|ASSIGNED |RESOLVED Resolution| |WONTFIX ------- Comment #7 from dkukawka(a)novell.com 2007-01-09 04:50 MST ------- Sorry, but this is a WONTFIX. We decided to remove this information and add the new information dialog, which is more reliable since the Tooltip get not updated while you are over the tooltip. With dynamic CPU Freq Policy the information in the tooltip can be outdated in the moment you display the tooltip. Please remember: there are machines with more than only 2 possible frequencies and at least with more than one CPU/Core. Btw. You should normaly always use the dynamic CPU Freq Policy which should work for all cases and adjust the CPU Freq automtically to the needed frequency. -- 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 173361] kpowersave: CPU frequency missing
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=173361 dkukawka(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dkukawka(a)suse.de |dkukawka(a)novell.com Status|REOPENED |ASSIGNED -- 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 231072] New: no /dev/shm in fstab, no /dev/shm in jack-0.102.20-16
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=231072 Summary: no /dev/shm in fstab, no /dev/shm in jack-0.102.20-16 Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: edogawa(a)aon.at QAContact: qa(a)suse.de CC: appleonkel(a)flashgrafik.de when trying to setup a rt system for audio, based on kernel-rt-2.6.19-4 from jacklab project i continuously get jackd xruns. after investigating i set up a fstab entry manually like this: none /dev/shm tmpfs defaults 0 0 which should do the job as /dev/shm where jackd writes its tempfiles. this still didn`t help; just by accident i found out that the xruns disappear when i start jack-rack, but not with other jack clients. it seems that the package jack-0.102.20-16 doesn`t setup tmpfs properly either, jackd --version shows: jackd version 0.102.20 tmpdir /tmp protocol 16 although writing to /dev/shm/jack* instead of /tmp. thx edogawa -- 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 2

[Bug 185042] YAST System Backup Tool To Tape Device
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=185042 harbrink(a)bluewin.ch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harbrink(a)bluewin.ch Status|RESOLVED |REOPENED Priority|P5 - None |P4 - Low Resolution|FIXED | Version|unspecified |Final ------- Comment #4 from harbrink(a)bluewin.ch 2007-01-09 04:45 MST ------- Unfortunately this doesn't work. Now the backup stops with the message: directoy /dev full. Probably when saving the xml-file. Instead of trying to save the xml-file into filesystem, the backup should tar it out to the same device-file. -- 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 168602] Can not administer CUPSD via http://localhost:631 because root password is rejected
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=168602 kssingvo(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kssingvo(a)novell.com |mzugec(a)novell.com ------- Comment #4 from kssingvo(a)novell.com 2007-01-09 04:27 MST ------- Package "cups-libs" and "filesystem" contain correct ownership. IIRC yast is doing a "chown" on "/etc/passwd" sometimes. --> reassign. -- 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 232111] New: ladspa-1.12.code10-49: array subscript out of range
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=232111 Summary: ladspa-1.12.code10-49: array subscript out of range 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 ladspa-1.12.code10-49 with the Intel C compiler. The compiler said Amp.cc(371): warning #175: subscript out of range The source code is *ports[7] = OVERSAMPLE; but d_sample * ports [7]; I agree with the compiler. Suggest code rework. -- 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 2

[Bug 228194] New: No mail for root - expecting to see output from crontab jobs output but none shows.
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=228194 Summary: No mail for root - expecting to see output from crontab jobs output but none shows. Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gdoig(a)pcug.org.au QAContact: qa(a)suse.de After setting up a number of crontab jobs in 10.2, I expected to get output at the mail prompt, after the crontab job finished, but this is not happening it just shows 'No mail for root'. How do I configure things so I see the results the job at the local mail prompt ? The installation is KDE based of 10.2 (64bit) and includes all patterns/products on the installation dvd . In previous installations, (10.1,10.0 and 9.x) I used to see the output. -- 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 203482] [Fix_is_Ready:10.0/10.1] Wrong handling of hardlinks in tar archives in ktar
by bugzilla_noreply＠novell.com 09 Jan '07

09 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=203482 dmueller(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Wrong handling of hardlinks |[Fix_is_Ready:10.0/10.1] Wrong handling of |in tar archives in ktar |hardlinks in tar archives in ktar -- 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