July 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 374370] New: KIWI: Confusing root options
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=374370 Summary: KIWI: Confusing root options Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: ms(a)novell.com ReportedBy: psladek(a)novell.com QAContact: qa(a)suse.de Found By: --- I tried preparing an image using the information from 'man kiwi' (or kiwi --help) as: kiwi -p /usr/share/kiwi/image/netboot/suse-SLES10-SP1 --base-root /root/images/myNetboot but it failed, returning: " Mar-27 13:16:12 <2> : Can't open log port: 9000Mar-27 13:16:12 <1> : Reading image description... skipped done Mar-27 13:16:12 <2> : Description provides no MD5 hash, check skipped Mar-27 13:16:12 <1> : Using profile(s): default done Mar-27 13:16:12 <1> : Checking for default root in XML data... notset Mar-27 13:16:13 <1> : Importing overlay path /root/images/myNetboot -> /tmp/kiwi.k23581 done Mar-27 13:16:21 <1> : Set root log: /tmp/kiwi.k23581.23536.screenrc.log... done Mar-27 13:16:21 <1> : Setting up package manager: smart done Mar-27 13:16:22 <1> : Mounting required file systems done Mar-27 13:16:22 <1> : Mounting local channel: kiwi1-23536 skipped Mar-27 13:16:22 <2> : Path /usr/share/kiwi/image/netboot/suse-repo/suse-sles-repo is writable, trying read-only mount skipped Mar-27 13:16:22 <2> : Couldn't mount read-only, using bind mount done Mar-27 13:16:23 <1> : Setting RPM signature check to: False failed Mar-27 13:16:23 <3> : chroot: cannot run command `smart': No such file or directory Mar-27 13:16:23 <3> : Image installation failed failed Mar-27 13:16:23 <1> : Umounting path: /tmp/kiwi.k23581//base-system/usr/share/kiwi/image/netboot/suse-repo/suse-sles-repo Mar-27 13:16:23 <1> : Umounting path: /tmp/kiwi.k23581/dev/pts Mar-27 13:16:23 <1> : Umounting path: /tmp/kiwi.k23581/sys Mar-27 13:16:23 <1> : Umounting path: /tmp/kiwi.k23581/dev Mar-27 13:16:23 <1> : Umounting path: /tmp/kiwi.k23581/proc Mar-27 13:16:23 <1> : Logfile available at: /tmp/kiwi.k23581.log done Mar-27 13:16:23 <3> : KIWI exited with error(s) " on the other hand, the same procedure described in kiwi.pdf implies using --root instead of --base-root (ch 1.6, p 21) and the command kiwi -p /usr/share/kiwi/image/netboot/suse-SLES10-SP1 --root /root/images/myNetboot finally succeeded. What is the purpose of the '--base-root ' parameter? (manual is not clear on this, found only an indirect reference on p.9 of kiwi.pdf) Am I doing something wrong or is there an error in man kiwi and kiwi --help? In all cases, there certainly seems to be an inconsistency. -- 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 336619] New: logprof fails with german locale in certain cases
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=336619 Summary: logprof fails with german locale in certain cases Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: msvec(a)novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: msvec(a)novell.com Found By: --- I had logprof failing with error: PromptUser: CMD_DENY: (V)erweigern when my root user has german locale set (what is the default on 10.3 for german installations). I guess that only happens when there are events in the log which occur when a confined application execs another binary because I don't get it everytime. -- 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 4

[Bug 334557] New: syslog-ng cannot open /etc/hosts.allow and /etc/hosts. deny
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=334557 Summary: syslog-ng cannot open /etc/hosts.allow and /etc/hosts.deny Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: truckk(a)inbox.lv QAContact: qa(a)suse.de Found By: --- I have regulary such: Oct 17 13:02:39 zorro syslog-ng: warning: cannot open /etc/hosts.allow: Permission denied Oct 17 13:02:39 zorro syslog-ng: warning: cannot open /etc/hosts.deny: Permission denied entries in /var/log/messages Host zorro is syslog collector. -- 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 389139] New: 100% CPU in apparmour while connecting to repository
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=389139 Summary: 100% CPU in apparmour while connecting to repository Product: openSUSE 11.0 Version: Beta 2 Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: agruen(a)novell.com ReportedBy: quentin.jackson(a)exclamation.co.nz QAContact: qa(a)suse.de Found By: Customer Just decided to make an apparmor profile, it asked if I wanted to connect to a profile repository, it errored out and now it's locked on connecting to repository and has cpu at between 96-100%. Presumably this will be replcicatable, not sure what logs to attach. -- 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 216530] New: When Atheros card detected, give a hint about binary drivers
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=216530 Summary: When Atheros card detected, give a hint about binary drivers Product: openSUSE 10.2 Version: Beta 1 plus Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dominique.leuenberger(a)tmf-group.com QAContact: jsrain(a)novell.com When an Atheros card is detected in a notebook, the user needs to install the madwifi package, which for known reasons are not distributed with openSUSE. It would be a very nice hint for the user if he could get a small information about the website http://en.opensuse.org/Atheros_madwifi in this case. The solution would be somehow similiar to the one used in xine, about video playing. If it can not be included in YAST in that short time, at least a comment in the release notes should make it. -- 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 396361] New: Boot loader ignores other bootable systems on HD
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=396361 User osl2008(a)googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=396361#c374693 Summary: Boot loader ignores other bootable systems on HD Product: openSUSE 11.0 Version: RC 1 Platform: Macintosh OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: osl2008(a)googlemail.com QAContact: jsrain(a)novell.com Found By: --- Other bootable systems (e.g. OS-X, other Linux) on the HD are ignored by the installer when setting up the boot loader. They can be added manually, either during installation or afterwards, but this requires more knowledge than we should assume users have. This was touched on in bug #374693 but was not the subject of that bug, neither was it fixed... -- 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 13

[Bug 310483] New: Ext3 partitions should have no forced fsck
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=310483 Summary: Ext3 partitions should have no forced fsck Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ma2412ma(a)hotmail.com QAContact: qa(a)suse.de Found By: --- I've noticed that every 30th boot takes a very long time. The reason for this is that all ext3 partitions are checked automatically every 30th mount. This is very annoying and unnecessary. Ubuntu has also a bug report on this (https://bugs.launchpad.net/ubuntu/+source/partman-ext3/+bug/3581) -- 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 302004] New: merge existing GRUB menu.lst for parallel installation
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=302004 Summary: merge existing GRUB menu.lst for parallel installation Product: openSUSE 10.3 Version: Beta 1 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tilman(a)imap.cc QAContact: jsrain(a)novell.com Found By: Beta-Customer For my first test, I installed 10.3 Beta1 on a working openSUSE 10.2 system which has everything except /boot in LVM, by creating a new LVM logical volume for the 10.3 root partition and mounting the existing /boot partition without formatting. Despite the warning from YaST this works perfectly fine, but I had to merge the GRUB menu items for 10.2 from /boot/grub/menu.lst.old into /boot/grub/menu.lst manually, whereafter the 10.2 installation also boots fine again. As this is rather convenient for testing, I'd like to suggest that this be done automatically, ie. if the installation procedure finds an existing menu.lst it should preserve its entries and just add a new one in front of them. Also, the strong warning against mounting existing partitions without reformatting them could, at least in the case of /boot, be toned down a bit. -- 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 349942] New: Apparmour Update Profile Wizzard crashes: unknown mode mrwiuplk
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=349942 Summary: Apparmour Update Profile Wizzard crashes: unknown mode mrwiuplk Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: AppArmor AssignedTo: msvec(a)novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- Created an attachment (id=188337) --> (https://bugzilla.novell.com/attachment.cgi?id=188337) screenshot showing the bug First time I use the wizard in 10.3 It asked something about a repository, and I said Ok. Then it crashed (see screenshot). I can not start it again, it crashes every time. -- 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 395760] New: cups-autoconfig: wrong default papersize
by bugzilla_noreply＠novell.com 11 Feb '09

11 Feb '09

https://bugzilla.novell.com/show_bug.cgi?id=395760 Summary: cups-autoconfig: wrong default papersize Product: openSUSE 11.0 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: crivera(a)novell.com ReportedBy: lnussel(a)novell.com QAContact: jsmeix(a)novell.com Found By: --- When plugging in a usb printer cups-autoconfig correctly configures a new print queue. It however chooses a wrong paper size. It enters "*DefaultPageSize: Letter" in the ppd file. I have an installation with German locale so A4 should be the default. YaST correctly suggests A4 if I try to manually configure the printer so that kind of information must be available somewhere. -- 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 11