November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 729348] New: Confusing output when upgrading nscd: Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended.
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=729348 https://bugzilla.novell.com/show_bug.cgi?id=729348#c0 Summary: Confusing output when upgrading nscd: Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended. Classification: openSUSE Product: openSUSE 12.1 Version: Factory 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: gp(a)suse.com QAContact: qa(a)suse.de Found By: Product Management Blocker: --- Just upgrading Factory, I got: Installing: nscd-2.14.1-17.1 [done] Additional rpm output: redirecting to systemctl Warning: Unit file of created job changed on disk, 'systemctl --system daemon-reload' recommended. Not sure what "redirecting to systemctl" tries to tell me in the first place, but then the warning is really confusing: if this is recommended, why not just do it as part of the upgrade? -- 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 726939] New: bash completion for systemctl breaks completion for stdout redirection
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=726939 https://bugzilla.novell.com/show_bug.cgi?id=726939#c0 Summary: bash completion for systemctl breaks completion for stdout redirection Classification: openSUSE Product: openSUSE 12.1 Version: Factory 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: koenig(a)linux.de QAContact: qa(a)suse.de Found By: --- Blocker: --- due to some bug reports around systemd I noticed the following (as root): # ls -l sys* -rw-r--r-- 1 root root 1058 Oct 27 09:34 systemctl-failed-1 -rw-r--r-- 1 root root 1058 Oct 27 09:35 systemctl-failed-2 -rw-r--r-- 1 root root 2115 Oct 27 21:40 systemctl_show_home.mount-0 -rw-r--r-- 1 root root 2058 Oct 27 21:46 systemctl_show_home.mount-after-mount -rw-r--r-- 1 root root 1903 Oct 27 21:46 systemctl_show_home.mount-before-mount -rw-r--r-- 1 root root 215408 Oct 26 15:04 systemd-dmesg-1 -rw-r--r-- 1 root root 216315 Oct 26 15:41 systemd-dmesg-2 -rw-r--r-- 1 root root 216061 Oct 27 09:21 systemd-dmesg-3 -rw-r--r-- 1 root root 250241 Oct 27 10:59 systemd-dmesg-4 -rw-r--r-- 1 root root 213067 Oct 27 17:38 systemd-dmesg-5 # systemctl > sys<TAB><TAB> # systemctl > ./s<TAB><TAB> do not show *any* output/completion :-( # systemctl > s<TAB><TAB> shows: set-environment show show-environment snapshot start status stop # complete | grep system complete -F _systemctl systemctl why is that completion relevant for output redirection ? I hate bash completions :-((( -- 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 555222] New: zypper dup should check if mkinitrd succeeds
by bugzilla_noreply＠novell.com 13 Jan '14

13 Jan '14

http://bugzilla.novell.com/show_bug.cgi?id=555222 Summary: zypper dup should check if mkinitrd succeeds Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mail(a)philipp-wagner.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-7.1 Firefox/3.5 I updated from 11.1 to 11.2 using zypper dup. My /boot partition was full and mkinitd during the installation of the kernel image probably failed. I didn't see the message as I let the update run unattended and only saw the last lines of output from zypper dup, which seemed to suggest that everything went ok. When rebooting I got a "kernel panic: attempted to kill init". Fortunately I had another kernel installed and were able to boot, remove some old files from /boot and call mkinitrd again. Now the system boots fine. A full /boot partition is not that unlikely (the default partition layout suggests a rather small /boot and installing two testkernels is enough to fill it so that mkinitrd fails. Could zypper dup give a summary of errors that happened while installing all packages in the end of the upgrade process so that the user sees this error before rebooting? 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 6

[Bug 713331] New: kbd: "Loading keymap unknown keysym 'cyrillic_small_letter_short_i"
by bugzilla_noreply＠novell.com 11 Jan '14

11 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=713331 https://bugzilla.novell.com/show_bug.cgi?id=713331#c0 Summary: kbd: "Loading keymap unknown keysym 'cyrillic_small_letter_short_i" Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 3 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lazy.kent(a)opensuse.org QAContact: qa(a)suse.de CC: highwaystar.ru(a)gmail.com, lazy.kent(a)opensuse.org, av.linux.dev(a)gmail.com Depends on: 643538 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #643538 +++ User-Agent: Mozilla/5.0 (X11; U; Linux i686; ru; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-3.4 Firefox/3.6.10 kbd failed to start on KDE LiveCD boot with message Loading keymap unknown keysym 'cyrillic_small_letter_short_i' Reproducible: Always Steps to Reproduce: 1. Booot KDE LiveCD 11.4 M2 with Russian language selected in booloader 2. When it boots see boot messages in text terminal (Ctrl+Alt+F1) 3. Try to restart kbd. Actual Results: kbd failed to start on boot, so there is no cyrillic fonts loaded in text terminal -> ureadable messages. When kbd restarted from text terminal fonts are loaded fine and all works ok. Expected Results: kbd should starts fine on boot -- 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 26

[Bug 702276] New: Fix XSLT Stylesheet Issues in susedoc
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=702276 https://bugzilla.novell.com/show_bug.cgi?id=702276#c0 Summary: Fix XSLT Stylesheet Issues in susedoc Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: thomas.schraitle(a)novell.com QAContact: ke(a)novell.com Found By: Documentation Blocker: --- There are several issues in our susedoc package in regard of XSLT. This bug collects all issues for easier accessibility. -- 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 40

[Bug 712599] New: Stylesheets: <command> in titles handled differently
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=712599 https://bugzilla.novell.com/show_bug.cgi?id=712599#c0 Summary: Stylesheets: <command> in titles handled differently Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: taroth(a)novell.com QAContact: ke(a)novell.com CC: fs(a)novell.com Found By: Documentation Blocker: --- If a <command> element is used in a title, it is handled differently depending on the section to which the title belongs (and depending on the output - PDF or HTML): PDF: - sect2 title: <command> appears in different font than the rest - sect3 title: <command> appears in the same font like the rest HTML: - <command> appears in different font in both sect2 + sect3 titles I personally prefer to have a markup for a command name even in a title, but I know there are different opinions on that. I would be fine with either solution as long as we make it consistent for all titles and outputs. (I stumbled across that in the current daps version, daps-0.9beta4-16.1.noarch) -- 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 703213] New: FOP: Font Size for Product Name on Titlepage
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=703213 https://bugzilla.novell.com/show_bug.cgi?id=703213#c0 Summary: FOP: Font Size for Product Name on Titlepage Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: taroth(a)novell.com QAContact: ke(a)novell.com Found By: Documentation Blocker: --- Created an attachment (id=437718) --> (http://bugzilla.novell.com/attachment.cgi?id=437718) HA Guide, built with FOP The font size for the product name on the title page is so large that it turns a product name like "SUSE Linux Enterprise High Availability Extension" into a 4-liner (with XEP, it takes 3 lines). -- 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 684418] New: Use serif fonts for b/w (aka printed) PDFs
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=684418 https://bugzilla.novell.com/show_bug.cgi?id=684418#c0 Summary: Use serif fonts for b/w (aka printed) PDFs Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: fs(a)novell.com QAContact: ke(a)novell.com CC: canadapatriot(a)yahoo.com Found By: --- Blocker: --- >From a cutomer mail (see Cc): Concerning the pdf documents, I notice that the last few versions of the manuals are all in sans-serif font. I urge you to consider getting the text body in a serif font (see 11.1 manuals). Sans-serif font is inappropriate for the body text, for it is less comfortable on the eye. On the other hand, serif font is appropriate for titles. The vast majority of print documents are in a serif font, and the pdf document should fit the purpose of printing, unlike the html version. -- 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 8

[Bug 705502] New: suse-ami-tools initscripts shoudn't use $ALL target
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=705502 https://bugzilla.novell.com/show_bug.cgi?id=705502#c0 Summary: suse-ami-tools initscripts shoudn't use $ALL target Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fcrozat(a)novell.com QAContact: qa(a)suse.de Blocks: 696902 Found By: --- Blocker: --- there is no plan in systemd to support SUSE non official $ALL LSB target in initscripts. It should be removed from /etc/init.d/amazon-late initscript in suse-ami-tools package. -- 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 9

[Bug 730959] New: zypper up is ignoring interactive option
by bugzilla_noreply＠novell.com 07 Jan '14

07 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=730959 https://bugzilla.novell.com/show_bug.cgi?id=730959#c0 Summary: zypper up is ignoring interactive option Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: schoenberg(a)fv-berlin.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 While installing security updates using zypper up -y --skip-interactive the latest kernel 2.6.37.6-0.9-default was installed, not skipped Reproducible: Didn't try Steps to Reproduce: 1. zypper up -y --skip-interactive 2. uname -a 3. rpm -qa |grep kernel Actual Results: uname -a # uname -a Linux 2.6.37.1-1.2-default #1 SMP 2011-02-21 10:34:10 +0100 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa |grep kernel kernel-default-2.6.37.6-0.9.1.x86_64 Expected Results: Kernel is interactive, should be skipped -- 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