July 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 626629] New: /usr/sbin/Check -- wrong shebang line
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626629 http://bugzilla.novell.com/show_bug.cgi?id=626629#c0 Summary: /usr/sbin/Check -- wrong shebang line Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: torsten.foertsch(a)gmx.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.1 SUSE/6.0.443.0 (KHTML, like Gecko) Chrome/6.0.443.0 Safari/534.1 /usr/sbin/Check reads: #!/bin/sh ... . /etc/profile "$0" will be "/usr/bin/Check" in this case even while /etc/profile is executed. Now /etc/profile reads: ... is=$(readlink /proc/$$/exe) ... because /bin/sh is a symlink to /bin/bash that yields "/bin/bash". Then "$is" is matched against "*/bash" and if so "$0" is consulted to distiguish between "sh" and "bash". This check reads: case "$0" in sh|-sh|*/sh) is=sh ;; esac ;; Now, because "$0" is "/usr/sbin/Check" "$is" still holds "bash" after the check. Later on /etc/profile reads "$HOME/.bashrc". Unfortunately, if called as "sh" instead of "bash" its syntax slightly changes. For example a-b () { :; } is a valid function definition in bash but fails in sh. So, if the user calling /usr/sbin/Check while rebuilding for example an opensuse source rpm his .bashrc is consulted but the bash runs in sh-mode. Hence "rpmbuild --rebuild" may fail due to the $HOME/.bashrc of an arbitrary user. One possible solution is to change the shebang line in /usr/sbin/Check to #!/bin/bash Another solution is to put more intelligence into the code to tell apart bash and sh in /etc/profile. Reproducible: Always Steps to Reproduce: 1. create a .bashrc for a normal user (not root!) containing "a-b () { :; }" 2. call as this user /usr/sbin/check 3. Actual Results: backup@opi:~> /usr/sbin/Check /home/backup/.bashrc: line 1: `a-b': not a valid identifier Expected Results: backup@opi:~> /usr/sbin/Check Check does not work for normal users. -- 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 8

[Bug 626582] New: tunctl has not manual page, changelog and so ..
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626582 http://bugzilla.novell.com/show_bug.cgi?id=626582#c0 Summary: tunctl has not manual page, changelog and so .. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nettezzaumanaa(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.10) Gecko/20100506 SUSE/3.5.10-0.1 Firefox/3.5.10 hi there, in suse: # rpm -ql tunctl /bin/tunctl in fedora: # rpm -ql tunctl /usr/sbin/tunctl /usr/share/doc/tunctl-1.5/ /usr/share/doc/tunctl-1.5/ChangeLog /usr/share/man/man8/tunctl.8.gz in debian: # dpkg --listfiles $(dpkg -S `which tunctl` | sed 's/:.*//') | grep tunc /usr/share/man/man8/tunctl.8.gz /usr/sbin/tunctl in bubuntu: $ dpkg --listfiles $(dpkg -S `which tunctl` | sed 's/:.*//') | grep tunc /usr/sbin/tunctl /usr/share/man/man8/tunctl.8.gz . please put there at least missing manpage, regards, daniel Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 3

[Bug 626515] New: NFS4 Domain is localdomain in idmapd.conf for NIS clients with automounter
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626515 http://bugzilla.novell.com/show_bug.cgi?id=626515#c0 Summary: NFS4 Domain is localdomain in idmapd.conf for NIS clients with automounter Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lnxgnome(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 openSUSE 11.3 (i586) VERSION = 11.3 Scenario: Workstation is configured as NIS Client + Automounter. There are not any nfs entries in /etc/fstab Problem: idmapd Domain is "localdomain", which is incorrect and results in owner UID/GID of all automounted files to be 'nobody'. /etc/idmapd.conf [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs Domain = localdomain The NIS domain name is provided during NIS Client configuration in YaST, but this might be different from the NFS4 Domain parameter for idmapd. Workaround: Manually update /etc/idmapd.conf with the correct NFS4 Domain name. Reproducible: Didn't try Steps to Reproduce: 1. Inital Install of openSuSE 11.3 Final 2. Configure NIS+Automounter in YaST Actual Results: Domain = localdomain Owner UID/GID of all automounted files to be 'nobody'. Expected Results: Expected result: YaST prompts and configures NFS4 Domain in /etc/imapd.conf to appropriate value. The normal environment will contain additional servers, which include a working NIS Server with maps for automounter (auto.home), and a NFS server to serve the /home mount points specified in the NIS maps. -- 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 24

[Bug 626368] New: openSUSE Documentation badly labeled in KDE Help Center
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626368 http://bugzilla.novell.com/show_bug.cgi?id=626368#c0 Summary: openSUSE Documentation badly labeled in KDE Help Center Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: carlos.lange(a)ualberta.ca QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=378939) --> (http://bugzilla.novell.com/attachment.cgi?id=378939) first KDE HElp Center window User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 Looking for the set of Manuals for openSUSE in the KDE Help Center required scrolling down through all Control Center Modules, KInfo Center Modules and KIOSlaves. If the user has not given up by then, he/she will have to deduce that the suite of manuals is hidden behind the deceptive label "openSUSE manual: Security Guide Documentation (en)", which gives the impression there is only one manual about security underneath. Reproducible: Always Expected Results: One well labeled entry "openSUSE Documentation" prominently shown, i.e. among the top 4 or 5 items, in the KDE Help Center. -- 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 9

[Bug 626280] New: yast2: typo in network config
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626280 http://bugzilla.novell.com/show_bug.cgi?id=626280#c0 Summary: yast2: typo in network config Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ke(a)novell.com QAContact: jsrain(a)novell.com Found By: Documentation Blocker: --- There is a tiny typo in an error pop-up: No valid netmask or prefix s/lenght/length/ -- 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 4

[Bug 626132] New: grub/perl-Bootloader: device hd(0,975) does not exist
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626132 http://bugzilla.novell.com/show_bug.cgi?id=626132#c0 Summary: grub/perl-Bootloader: device hd(0,975) does not exist Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- There seems to be an ugly enumeration bug in 11.3's perl-Bootloader, leading to values like (hd0,975) and (hd0,976) to be used in menu.lst and elsewhere and leads to a failure to automatically boot. The initial installer already did this odd thing, and I had to fix it up manually with the rescue system. Installing a new kernel image in the now-running lvie system also appends such bogus entry to menu.lst. Please advise how to debug this. /boot on /dev/md0 level1 consisting of /dev/sda1, /dev/sdb1 / on /dev/md1 level1 consisting of /dev/sda3, /dev/sdb3 Kernel image: /boot/vmlinuz-2.6.34-12-xen Initrd image: /boot/initrd-2.6.34-12-xen Root device: /dev/disk/by-id/md-uuid-1ea4d76b:07e349d8:0a1d3ae2:4eb0c6cc (/dev/md1) (mounted on / as ext4) Resume device: /dev/disk/by-id/ata-WDC_WD5002ABYS-02B1B0_WD-WCASY7452556-part2 (/dev/sda2) Kernel Modules: scsi_mod libata ata_piix xennet cdrom xenblk crc16 jbd2 ext4 pata_mpiix sata_uli sata_promise ahci pata_hpt37x pata_opti pata_cmd64x pata_ali pata_ninja32 sata_mv pata_marvell pata_it821x sata_sil pata_atp867x pata_amd pata_ns87415 pata_optidma pata_via sata_qstor sata_sx4 pata_radisys pata_cmd640 pata_sc1200 sata_nv pata_sis ata_generic pata_triflex pata_netcell pata_efar sata_sis pdc_adma pata_rz1000 pata_cs5520 pata_cypress pata_hpt366 pata_sch pata_serverworks pata_pdc2027x pata_it8213 pata_rdc sata_inic162x pata_sl82c105 pcmcia_core pcmcia pata_pcmcia pata_piccolo pata_cs5530 sata_sil24 pata_hpt3x2n pata_sil680 sata_vsc pata_atiixp sata_via pata_acpi pata_jmicron pata_hpt3x3 pata_artop pata_pdc202xx_old pata_ns87410 sata_svw pata_oldpiix sd_mod usbcore ohci-hcd ehci-hcd uhci-hcd hid usbhid raid0 raid1 raid10 async_tx async_memcpy xor async_xor raid6_pq async_pq async_raid6_recov raid456 Features: block usb md 27930 blocks Perl-Bootloader: 2010-07-27 17:50:57 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 976. Perl-Bootloader: 2010-07-27 17:50:57 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 976. Perl-Bootloader: 2010-07-27 17:50:57 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 976. Perl-Bootloader: 2010-07-27 17:50:57 WARNING: GRUB::GrubDev2UnixDev: No partition found for /dev/sda with 976. -- 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 26

[Bug 626127] New: pam_mount suggests to specify "fskeyhash" when mounting a LUKS partition
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=626127 http://bugzilla.novell.com/show_bug.cgi?id=626127#c0 Summary: pam_mount suggests to specify "fskeyhash" when mounting a LUKS partition Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bugreports(a)tittel.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 When mounting a LUKS-encrypted partition with pam_mount on login, pam_mount gives the following warning: pam_mount(rdconf1.c:1325): Volume /dev/sda8: consider specifying the fskeyhash pam_mount(rdconf1.c:1325): Volume /dev/sda8: consider specifying the fskeyhash (yes, the warning appears twice) Specifiying an fskeyhash for a LUKS-partition doesn't make sense (it's all in the LUKS header) and if I set an fskeyhash for a LUKS partition in /etc/security/pam_mount.conf.xml it is actually ignored. In short: This warning shouldn't be there. If I look at bugs like http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580430 in den Debian bugtracker, it seems like pam_mount is probably warning about the missing fskeyhash in other situations (like mounting tmpfs) in which it doesn't make sense. I talked to the pam_mount upstream author (Jan Engelhardt) and this problem seems to be fixed in more current versions of pam_mount. Thanks in advance! 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 20

[Bug 625987] New: Can't add 11.3 Sources repository
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=625987 http://bugzilla.novell.com/show_bug.cgi?id=625987#c0 Summary: Can't add 11.3 Sources repository Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: yuvalery(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.1 Firefox/3.6.8 Sources repository does not work due to missing content.key Reproducible: Always Steps to Reproduce: 1. open yast repositories tool 2. choose community repos -> Sources 3. yast gives error about content.key while adding 4. the repo is empty Actual Results: No packages in Sources repo Expected Results: See packages in Sources repo -- 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 19

[Bug 625883] New: Missing libpng-devel-32bit
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=625883 http://bugzilla.novell.com/show_bug.cgi?id=625883#c0 Summary: Missing libpng-devel-32bit Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: bon(a)elektron.ikp.physik.tu-darmstadt.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 with 11.3, libpng-devel-32bit is removed. Libpng is needed for compiling wine from source (on a 64-bit machine). Could anybody trigger the building of libpng-devel-32bit? Or is there a way to build libpng-devel-32bit from the source package? I short search didn't turn up soemthing usefull. Reproducible: Always Steps to Reproduce: 1.Search for libpng-devel-32bit for 11.3 2.No result found 3. Actual Results: Doesn't apply. Expected Results: Doesn't apply -- 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 5

[Bug 625763] New: Missing '/' in rpm output when updating branding pkgs
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=625763 http://bugzilla.novell.com/show_bug.cgi?id=625763#c0 Summary: Missing '/' in rpm output when updating branding pkgs Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: sven.zallmann(a)rwth-aachen.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100714 SUSE/2.0.6-2.2 SeaMonkey/2.0.6 Dear all, When I updated my system Sunday night I noticed the following "Additional rpm output" for two packages: - for kdm-branding-openSUSE: "Updating etc/sysconfig/displaymanager" - for kdebase4-workspace-branding-openSUSE: "Updating etc/sysconfig/windowmanager" Both statements are missing the leading slash ('/') in front of the file path. My question now is: Is this just a typo in the rpm output, or does rpm try to update the wrong, normally non-existing files relative to the directory from which 'zypper up' was started? I was requested to file this as a bug so that it doesn't get overlooked. The repository in question is KDE:Distro:Factory where KDE 4.4.93 (4.5-rc2) got updated to 4.4.95 (4.5-rc3). Reproducible: Didn't try Steps to Reproduce: 1. Have any KDE4 version previous to 4.4.95 installed. 2. Run 'zypper up' (verbosity at your choice), or 'zypper dup' if updating to 4.4.95 requires vendor change. 3. Watch the "Additional rpm output" when packages 'kdm-branding-openSUSE' and 'kdebase4-workspace-branding-openSUSE' are installed. Actual Results: see above Expected Results: Output should have read 'Updating /etc/sysconfig/displaymanager' and 'Updating /etc/sysconfig/windowmanager' respectively. -- 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 7