August 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 799644] New: Warning during installation over ssh (perl-bootloader)
by bugzilla_noreply＠novell.com 28 Apr '16

28 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=799644 https://bugzilla.novell.com/show_bug.cgi?id=799644#c0 Summary: Warning during installation over ssh (perl-bootloader) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mpluskal(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- What: 1) Start installation over ssh (usessh=1) on x86_64 uefi machine 2) Log via ssh 3) Following warning appears: *** Starting YaST2 *** Use of uninitialized value $r in substitution (s///) at /usr/lib/perl5/vendor_perl/5.16.2/Bootloader/Library.pm line 136 (#1) (W uninitialized) An undefined value was used as if it were already defined. It was interpreted as a "" or a 0, but maybe it was a mistake. To suppress this warning assign a defined value to your variables. To help you figure out what was undefined, perl will try to tell you the name of the variable (if any) that was undefined. In some cases it cannot do this, so it also tells you what operation you used the undefined value in. Note, however, that perl optimizes your program anid the operation displayed in the warning may not necessarily appear literally in your program. For example, "that $foo" is usually optimized into "that " . $foo, and the warning will refer to the concatenation (.) operator, even though there is no . in your program. Perl-Bootloader: 2013-01-21 15:19:17 <3> yast-5562.1 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-efi-set-default '0' >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 32512 and output: sh: /usr/sbin/grub2-efi-set-default: No such file or directory -- 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 601779] New: 32bit 'tree' doesn't show files 2GB and larger
by bugzilla_noreply＠novell.com 28 Apr '16

28 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=601779 http://bugzilla.novell.com/show_bug.cgi?id=601779#c0 Summary: 32bit 'tree' doesn't show files 2GB and larger Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jc(a)ymmv.dk QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 Hi On 32bit systems the 'tree' command dosn't show 'large' files. I have tested on a 64bit system as well, and the problem is only present on 32bit systems. I have done a fair amount of research, comparing compile-time arguments with those of 32bit Debian packages. In the end I think it comes down to the 'spec' file: In tree.spec the 'make' command is: %build make CFLAGS="$RPM_OPT_FLAGS" -which overrides the CFLAGS set in the Makefile: CFLAGS=-O2 -Wall -fomit-frame-pointer -DLINUX -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -which results in the binary being built with these flags instead: RPM_OPT_FLAGS="-O2 -g -m32 -march=i586 -mtune=i686 -fmessage-length=0 -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables" Now; If I change the spec file so that; %build make -then the compiler gets the flags as set in the Makefile, and the resulting binary works with files larger than 2G. I'm guessing that it's desirable to get $RPM_OPT_FLAGS passed to the compiler, but I'm unsure as to how one would 'merge' this variable with $CFLAGS from the Makefile? As for the severity of the bug: It doesn't break the system, but the functionality of the command is seriously hampered by this. It seems reasonable (to me) that it's a packaging bug, and therefore it should be easily fixed. I have confirmation from the opensuse(a)opensuse.org list that the bug is present on 11.0, so it seems to be an 'old' problem... Kind Regards, Jon Clausen Reproducible: Always Steps to Reproduce: 1. get or create a file larger than 2GB I used 'dd' to create two files - one 2GB, one 1KB smaller: dd if=/dev/zero of=2G bs=1k count=2097152 dd if=/dev/zero of=2G-1k bs=1k count=2097151 2. use 'tree /path/to/large/file' 3. observe output Actual Results: output from 32bit system: jon@nx8220:~> ll tmp/largefiles/ total 4194304 -rw-r--r-- 1 jon users 2147483648 2010-04-30 12:50 2G -rw-r--r-- 1 jon users 2147482624 2010-04-30 12:52 2G-1k jon@nx8220:~> tree tmp/largefiles/ tmp/largefiles/ `-- 2G-1k 0 directories, 1 file Expected Results: output from 64bit system: jon@cnu8092slm:~> ll tmp/largefiles/ total 4194304 -rw-r--r-- 1 jon users 2147483648 2010-04-30 12:58 2G -rw-r--r-- 1 jon users 2147482624 2010-04-30 12:58 2G-1k jon@cnu8092slm:~> tree tmp/largefiles/ tmp/largefiles/ |-- 2G `-- 2G-1k 0 directories, 2 files AFAICT the flag that makes the difference is -D_FILE_OFFSET_BITS=64 - which makes the binary use *stat64() rather than *stat() when files are 'large'. On 64bit systems I suppose everything uses *stat64() anyways, which is why the problem only surfaces on 32bit systems... ? -- 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 17

[Bug 820693] New: zypper.conf: confusing description for installRecommends
by bugzilla_noreply＠novell.com 28 Apr '16

28 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=820693 https://bugzilla.novell.com/show_bug.cgi?id=820693#c0 Summary: zypper.conf: confusing description for installRecommends Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- from zypper.conf: ## Do not install soft dependencies (recommended packages) ## ## Valid values: boolean ## Default value: yes ## # installRecommends = yes The "Do not install..." is confusing (especially the "not") - can you please change it to just "Install soft dependencies"? -- 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 707860] New: Static buffers in minicom are too small
by bugzilla_noreply＠novell.com 28 Apr '16

28 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=707860 https://bugzilla.novell.com/show_bug.cgi?id=707860#c0 Summary: Static buffers in minicom are too small Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Stromeko(a)NexGo.DE QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20100101 Firefox/5.0 The terminal emulation minicom uses a static buffer for reading in config parameters. When you've got a path like: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 then it gets truncated and can't be used. Using the real device /dev/ttyUSB0 is not a good idea since udev may put this device on /dev/ttyUSB1 the next time. The buffer can be increased by setting #define PARS_VAL_LEN 196 in src/configsym.h (standard value is 64). If I build minicom with this change (and all the patches from https://build.opensuse.org/package/files?package=minicom&project=Base%3ASys…) then it will work with a configuration that references the above device. Reproducible: Always Steps to Reproduce: minicom -D /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0 Actual Results: minicom: cannot open /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Co: No such file or directory Expected Results: minicom opening the serial port it had been given -- 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 23

[Bug 578994] New: hwinfo cuts off list of cpu features
by bugzilla_noreply＠novell.com 28 Apr '16

28 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=578994 http://bugzilla.novell.com/show_bug.cgi?id=578994#c0 Summary: hwinfo cuts off list of cpu features Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: HMWiesinger(a)gmx.at QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.1 (like Gecko) The list of supported features is cut off at some point. hwinfo (16.10) shows the following list: Features: fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36, clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,ht,tm,pbe,syscall,nx,lm,constant_tsc, arch_perfmon,pebs,bts,rep_good,aperfmperf,pni,dtes64,monitor,ds_cpl,vmx, smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse whereas "cat /proc/cpuinfo" shows: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida tpr_shadow vnmi flexpriority Reproducible: Always Steps to Reproduce: 1. hwinfo --cpu 2. cat /proc/cpuinfo 3. compare output -- 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 781101] New: brp-symlink breaks build
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=781101 https://bugzilla.novell.com/show_bug.cgi?id=781101#c0 Summary: brp-symlink breaks build Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: lnussel(a)suse.com ReportedBy: bwiedemann(a)suse.com QAContact: qa-bugs(a)suse.de CC: coolo(a)suse.com Found By: Development Blocker: --- brp-symlink breaks osc build when creating a symlink to / as was needed in our qemu-accel package because cross compilers were searching files in /usr/arm-foo/ that were in / this caused $new_link_dest="" which broke in /usr/lib/rpm/brp-suse.d/brp-25-symlink:185 rm ./$link && ln -s $new_link_dest ./$link as a workaround, I symlinked "../.." which should in the end be treated equally to "/" -- 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 14

[Bug 723593] New: in.rshd: double free or corruption
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=723593 https://bugzilla.novell.com/show_bug.cgi?id=723593#c0 Summary: in.rshd: double free or corruption Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tiwai(a)suse.com QAContact: qa(a)suse.de CC: mc(a)suse.com, nadvornik(a)suse.com Found By: --- Blocker: --- After upgrading 12.1b1, rsh server crashes when invoked from xinetd, as glibc detects the double-free in libpam_misc like below: % rsh alsa2 echo foo *** glibc detected *** in.rshd: double free or corruption (out): 0x00007f2a9d6ded40 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x74bb6)[0x7f2a9cb7bbb6] /lib64/libpam_misc.so.0(pam_misc_drop_env+0x5a)[0x7f2a9ce9624a] in.rshd(+0x2ed2)[0x7f2a9d4cced2] in.rshd(+0x2037)[0x7f2a9d4cc037] /lib64/libc.so.6(__libc_start_main+0xed)[0x7f2a9cb2823d] in.rshd(+0x2061)[0x7f2a9d4cc061] ======= Memory map: ======== 7f2a9936e000-7f2a99383000 r-xp 00000000 08:11 4171234 /lib64/libgcc_s.so.1 7f2a99383000-7f2a99582000 ---p 00015000 08:11 4171234 /lib64/libgcc_s.so.1 7f2a99582000-7f2a99583000 r--p 00014000 08:11 4171234 /lib64/libgcc_s.so.1 7f2a99583000-7f2a99584000 rw-p 00015000 08:11 4171234 /lib64/libgcc_s.so.1 7f2a99584000-7f2a99585000 r-xp 00000000 08:11 4170509 /lib64/security/pam_deny.so 7f2a99585000-7f2a99784000 ---p 00001000 08:11 4170509 /lib64/security/pam_deny.so 7f2a99784000-7f2a99785000 r--p 00000000 08:11 4170509 /lib64/security/pam_deny.so 7f2a99785000-7f2a99786000 rw-p 00001000 08:11 4170509 /lib64/security/pam_deny.so 7f2a99786000-7f2a99787000 r-xp 00000000 08:11 4171037 /lib64/security/pam_warn.so 7f2a99787000-7f2a99986000 ---p 00001000 08:11 4171037 /lib64/security/pam_warn.so 7f2a99986000-7f2a99987000 r--p 00000000 08:11 4171037 /lib64/security/pam_warn.so 7f2a99987000-7f2a99988000 rw-p 00001000 08:11 4171037 /lib64/security/pam_warn.so 7f2a99988000-7f2a999a0000 r-xp 00000000 08:11 4171086 /lib64/libpthread-2.14.1.so 7f2a999a0000-7f2a99b9f000 ---p 00018000 08:11 4171086 /lib64/libpthread-2.14.1.so 7f2a99b9f000-7f2a99ba0000 r--p 00017000 08:11 4171086 /lib64/libpthread-2.14.1.so 7f2a99ba0000-7f2a99ba1000 rw-p 00018000 08:11 4171086 /lib64/libpthread-2.14.1.so 7f2a99ba1000-7f2a99ba5000 rw-p 00000000 00:00 0 7f2a99ba5000-7f2a99bac000 r-xp 00000000 08:11 4171089 /lib64/librt-2.14.1.so 7f2a99bac000-7f2a99dab000 ---p 00007000 08:11 4171089 /lib64/librt-2.14.1.so 7f2a99dab000-7f2a99dac000 r--p 00006000 08:11 4171089 /lib64/librt-2.14.1.so 7f2a99dac000-7f2a99dad000 rw-p 00007000 08:11 4171089 /lib64/librt-2.14.1.so 7f2a99dad000-7f2a99df0000 r-xp 00000000 08:11 4170683 /lib64/libdbus-1.so.3.6.3 7f2a99df0000-7f2a99fef000 ---p 00043000 08:11 4170683 /lib64/libdbus-1.so.3.6.3 7f2a99fef000-7f2a99ff0000 r--p 00042000 08:11 4170683 /lib64/libdbus-1.so.3.6.3 7f2a99ff0000-7f2a99ff1000 rw-p 00043000 08:11 4170683 /lib64/libdbus-1.so.3.6.3 7f2a99ff1000-7f2a99ff3000 r-xp 00000000 08:11 2717422 /usr/lib64/libsystemd-daemon.so.0.0.0 7f2a99ff3000-7f2a9a1f3000 ---p 00002000 08:11 2717422 /usr/lib64/libsystemd-daemon.so.0.0.0 7f2a9a1f3000-7f2a9a1f4000 r--p 00002000 08:11 2717422 /usr/lib64/libsystemd-daemon.so.0.0.0 7f2a9a1f4000-7f2a9a1f5000 rw-p 00003000 08:11 2717422 /usr/lib64/libsystemd-daemon.so.0.0.0 7f2a9a1f5000-7f2a9a1f9000 r-xp 00000000 08:11 4170829 /lib64/libcap.so.2.22 7f2a9a1f9000-7f2a9a3f8000 ---p 00004000 08:11 4170829 /lib64/libcap.so.2.22 7f2a9a3f8000-7f2a9a3f9000 r--p 00003000 08:11 4170829 /lib64/libcap.so.2.22 7f2a9a3f9000-7f2a9a3fa000 rw-p 00004000 08:11 4170829 /lib64/libcap.so.2.22 7f2a9a3fa000-7f2a9a404000 r-xp 00000000 08:11 4171252 /lib64/security/pam_systemd.so 7f2a9a404000-7f2a9a603000 ---p 0000a000 08:11 4171252 /lib64/security/pam_systemd.so 7f2a9a603000-7f2a9a604000 r--p 00009000 08:11 4171252 /lib64/security/pam_systemd.so 7f2a9a604000-7f2a9a605000 rw-p 0000a000 08:11 4171252 /lib64/security/pam_systemd.so 7f2a9a605000-7f2a9a607000 r-xp 00000000 08:11 4170032 /lib64/security/pam_umask.so 7f2a9a607000-7f2a9a806000 ---p 00002000 08:11 4170032 /lib64/security/pam_umask.so 7f2a9a806000-7f2a9a807000 r--p 00001000 08:11 4170032 /lib64/security/pam_umask.so 7f2a9a807000-7f2a9a808000 rw-p 00002000 08:11 4170032 /lib64/security/pam_umask.so 7f2a9a808000-7f2a9a80c000 r-xp 00000000 08:11 4170005 /lib64/security/pam_limits.so 7f2a9a80c000-7f2a9aa0b000 ---p 00004000 08:11 4170005 /lib64/security/pam_limits.so 7f2a9aa0b000-7f2a9aa0c000 r--p 00003000 08:11 4170005 /lib64/security/pam_limits.so 7f2a9aa0c000-7f2a9aa0d000 rw-p 00004000 08:11 4170005 /lib64/security/pam_limits.so 7f2a9aa0d000-7f2a9aa0f000 r-xp 00000000 08:11 4171025 /lib64/security/pam_loginuid.so 7f2a9aa0f000-7f2a9ac0e000 ---p 00002000 08:11 4171025 /lib64/security/pam_loginuid.so 7f2a9ac0e000-7f2a9ac0f000 r--p 00001000 08:11 4171025 /lib64/security/pam_loginuid.so 7f2a9ac0f000-7f2a9ac10000 rw-p 00002000 08:11 4171025 /lib64/security/pam_loginuid.so 7f2a9ac10000-7f2a9ac1a000 r-xp 00000000 08:11 4169863 /lib64/security/pam_gnome_keyring.so 7f2a9ac1a000-7f2a9ae19000 ---p 0000a000 08:11 4169863 /lib64/security/pam_gnome_keyring.so 7f2a9ae19000-7f2a9ae1a000 r--p 00009000 08:11 4169863 /lib64/security/pam_gnome_keyring.so 7f2a9ae1a000-7f2a9ae1b000 rw-p 0000a000 08:11 4169863 /lib64/security/pam_gnome_keyring.so 7f2a9ae1b000-7f2a9ae32000 r-xp 00000000 08:11 4170665 /lib64/libz.so.1.2.5 7f2a9ae32000-7f2a9b031000 ---p 00017000 08:11 4170665 /lib64/libz.so.1.2.5 7f2a9b031000-7f2a9b032000 r--p 00016000 08:11 4170665 /lib64/libz.so.1.2.5 7f2a9b032000-7f2a9b033000 rw-p 00017000 08:11 4170665 /lib64/libz.so.1.2.5 7f2a9b033000-7f2a9b03b000 r-xp 00000000 08:11 4438813 /usr/lib64/libcrack.so.2.8.1 7f2a9b03b000-7f2a9b23b000 ---p 00008000 08:11 4438813 /usr/lib64/libcrack.so.2.8.1 7f2a9b23b000-7f2a9b23c000 r--p 00008000 08:11 4438813 /usr/lib64/libcrack.so.2.8.1 7f2a9b23c000-7f2a9b23d000 rw-p 00009000 08:11 4438813 /usr/lib64/libcrack.so.2.8.1 7f2a9b23d000-7f2a9b240000 rw-p 00000000 00:00 0 7f2a9b240000-7f2a9b246000 r-xp 00000000 08:11 4170684 /lib64/security/pam_pwcheck.so 7f2a9b246000-7f2a9b445000 ---p 00006000 08:11 4170684 /lib64/security/pam_pwcheck.so 7f2a9b445000-7f2a9b446000 r--p 00005000 08:11 4170684 /lib64/security/pam_pwcheck.so 7f2a9b446000-7f2a9b447000 rw-p 00006000 08:11 4170684 /lib64/security/pam_pwcheck.so 7f2a9b447000-7f2a9b463000 r-xp 00000000 08:11 4170645 /lib64/libselinux.so.1 7f2a9b463000-7f2a9b662000 ---p 0001c000 08:11 4170645 /lib64/libselinux.so.1 7f2a9b662000-7f2a9b663000 r--p 0001b000 08:11 4170645 /lib64/libselinux.so.1 7f2a9b663000-7f2a9b664000 rw-p 0001c000 08:11 4170645 /lib64/libselinux.so.1 7f2a9b664000-7f2a9b665000 rw-p 00000000 00:00 0 7f2a9b665000-7f2a9b671000 r-xp 00000000 08:11 4170473 /lib64/libcrypt-2.14.1.so 7f2a9b671000-7f2a9b870000 ---p 0000c000 08:11 4170473 /lib64/libcrypt-2.14.1.so 7f2a9b870000-7f2a9b871000 r--p 0000b000 08:11 4170473 /lib64/libcrypt-2.14.1.so 7f2a9b871000-7f2a9b872000 rw-p 0000c000 08:11 4170473 /lib64/libcrypt-2.14.1.so 7f2a9b872000-7f2a9b8a0000 rw-p 00000000 00:00 0 7f2a9b8a0000-7f2a9b8ac000 r-xp 00000000 08:11 4170457 /lib64/security/pam_unix2.so 7f2a9b8ac000-7f2a9baab000 ---p 0000c000 08:11 4170457 /lib64/security/pam_unix2.so 7f2a9baab000-7f2a9baac000 r--p 0000b000 08:11 4170457 /lib64/security/pam_unix2.so 7f2a9baac000-7f2a9baad000 rw-p 0000c000 08:11 4170457 /lib64/security/pam_unix2.so 7f2a9baad000-7f2a9baae000 r-xp 00000000 08:11 4170520 /lib64/security/pam_nologin.so 7f2a9baae000-7f2a9bcae000 ---p 00001000 08:11 4170520 /lib64/security/pam_nologin.so 7f2a9bcae000-7f2a9bcaf000 r--p 00001000 08:11 4170520 /lib64/security/pam_nologin.so 7f2a9bcaf000-7f2a9bcb0000 rw-p 00002000 08:11 4170520 /lib64/security/pam_nologin.so 7f2a9bcb0000-7f2a9bcb1000 r-xp 00000000 08:11 4171033 /lib64/security/pam_rhosts.so 7f2a9bcb1000-7f2a9beb0000 ---p 00001000 08:11 4171033 /lib64/security/pam_rhosts.so 7f2a9beb0000-7f2a9beb1000 r--p 00000000 08:11 4171033 /lib64/security/pam_rhosts.so 7f2a9beb1000-7f2a9beb2000 rw-p 00001000 08:11 4171033 /lib64/security/pam_rhosts.so 7f2a9beb2000-7f2a9bebc000 r-xp 00000000 08:11 4171082 /lib64/libnss_nis-2.14.1.so 7f2a9bebc000-7f2a9c0bb000 ---p 0000a000 08:11 4171082 /lib64/libnss_nis-2.14.1.so 7f2a9c0bb000-7f2a9c0bc000 r--p 00009000 08:11 4171082 /lib64/libnss_nis-2.14.1.so 7f2a9c0bc000-7f2a9c0bd000 rw-p 0000a000 08:11 4171082 /lib64/libnss_nis-2.14.1.so 7f2a9c0bd000-7f2a9c0d2000 r-xp 00000000 08:11 4170600 /lib64/libnsl-2.14.1.so 7f2a9c0d2000-7f2a9c2d1000 ---p 00015000 08:11 4170600 /lib64/libnsl-2.14.1.so 7f2a9c2d1000-7f2a9c2d2000 r--p 00014000 08:11 4170600 /lib64/libnsl-2.14.1.so 7f2a9c2d2000-7f2a9c2d3000 rw-p 00015000 08:11 4170600 /lib64/libnsl-2.14.1.so 7f2a9c2d3000-7f2a9c2d5000 rw-p 00000000 00:00 0 7f2a9c2d5000-7f2a9c2dd000 r-xp 00000000 08:11 4170648 /lib64/libnss_compat-2.14.1.so 7f2a9c2dd000-7f2a9c4dc000 ---p 00008000 08:11 4170648 /lib64/libnss_compat-2.14.1.so 7f2a9c4dc000-7f2a9c4dd000 r--p 00007000 08:11 4170648 /lib64/libnss_compat-2.14.1.so 7f2a9c4dd000-7f2a9c4de000 rw-p 00008000 08:11 4170648 /lib64/libnss_compat-2.14.1.so 7f2a9c4de000-7f2a9c4ea000 r-xp 00000000 08:11 4170876 /lib64/libnss_files-2.14.1.so 7f2a9c4ea000-7f2a9c6e9000 ---p 0000c000 08:11 4170876 /lib64/libnss_files-2.14.1.so 7f2a9c6e9000-7f2a9c6ea000 r--p 0000b000 08:11 4170876 /lib64/libnss_files-2.14.1.so 7f2a9c6ea000-7f2a9c6eb000 rw-p 0000c000 08:11 4170876 /lib64/libnss_files-2.14.1.so 7f2a9c6eb000-7f2a9c6ed000 r-xp 00000000 08:11 4170533 /lib64/libdl-2.14.1.so 7f2a9c6ed000-7f2a9c8ed000 ---p 00002000 08:11 4170533 /lib64/libdl-2.14.1.so 7f2a9c8ed000-7f2a9c8ee000 r--p 00002000 08:11 4170533 /lib64/libdl-2.14.1.so 7f2a9c8ee000-7f2a9c8ef000 rw-p 00003000 08:11 4170533 /lib64/libdl-2.14.1.so 7f2a9c8ef000-7f2a9c906000 r-xp 00000000 08:11 4170671 /lib64/libaudit.so.1.0.0 7f2a9c906000-7f2a9cb05000 ---p 00017000 08:11 4170671 /lib64/libaudit.so.1.0.0 7f2a9cb05000-7f2a9cb06000 r--p 00016000 08:11 4170671 /lib64/libaudit.so.1.0.0 7f2a9cb06000-7f2a9cb07000 rw-p 00017000 08:11 4170671 /lib64/libaudit.so.1.0.0 7f2a9cb07000-7f2a9cc8c000 r-xp 00000000 08:11 4170453 /lib64/libc-2.14.1.so 7f2a9cc8c000-7f2a9ce8b000 ---p 00185000 08:11 4170453 /lib64/libc-2.14.1.so 7f2a9ce8b000-7f2a9ce8f000 r--p 00184000 08:11 4170453 /lib64/libc-2.14.1.so 7f2a9ce8f000-7f2a9ce90000 rw-p 00188000 08:11 4170453 /lib64/libc-2.14.1.so 7f2a9ce90000-7f2a9ce95000 rw-p 00000000 00:00 0 7f2a9ce95000-7f2a9ce97000 r-xp 00000000 08:11 4170928 /lib64/libpam_misc.so.0.82.0 7f2a9ce97000-7f2a9d097000 ---p 00002000 08:11 4170928 /lib64/libpam_misc.so.0.82.0 7f2a9d097000-7f2a9d098000 r--p 00002000 08:11 4170928 /lib64/libpam_misc.so.0.82.0 7f2a9d098000-7f2a9d099000 rw-p 00003000 08:11 4170928 /lib64/libpam_misc.so.0.82.0 7f2a9d099000-7f2a9d0a6000 r-xp 00000000 08:11 4170858 /lib64/libpam.so.0.83.1 7f2a9d0a6000-7f2a9d2a5000 ---p 0000d000 08:11 4170858 /lib64/libpam.so.0.83.1 7f2a9d2a5000-7f2a9d2a6000 r--p 0000c000 08:11 4170858 /lib64/libpam.so.0.83.1 7f2a9d2a6000-7f2a9d2a7000 rw-p 0000d000 08:11 4170858 /lib64/libpam.so.0.83.1 7f2a9d2a7000-7f2a9d2c7000 r-xp 00000000 08:11 4170411 /lib64/ld-2.14.1.so 7f2a9d494000-7f2a9d498000 rw-p 00000000 00:00 0 7f2a9d4c5000-7f2a9d4c6000 rw-p 00000000 00:00 0 7f2a9d4c6000-7f2a9d4c7000 rw-p 00000000 00:00 0 7f2a9d4c7000-7f2a9d4c8000 r--p 00020000 08:11 4170411 /lib64/ld-2.14.1.so 7f2a9d4c8000-7f2a9d4c9000 rw-p 00021000 08:11 4170411 /lib64/ld-2.14.1.so 7f2a9d4c9000-7f2a9d4ca000 rw-p 00000000 00:00 0 7f2a9d4ca000-7f2a9d4ce000 r-xp 00000000 08:11 4436083 /usr/sbin/in.rshd 7f2a9d6cd000-7f2a9d6ce000 r--p 00003000 08:11 4436083 /usr/sbin/in.rshd 7f2a9d6ce000-7f2a9d6cf000 rw-p 00004000 08:11 4436083 /usr/sbin/in.rshd 7f2a9d6cf000-7f2a9d6f0000 rw-p 00000000 00:00 0 [heap] 7fff3700c000-7fff37219000 rw-p 00000000 00:00 0 [stack] 7fff373d5000-7fff373d6000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] -- 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 16

[Bug 685093] New: Printing over Samba does not work
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=685093 https://bugzilla.novell.com/show_bug.cgi?id=685093#c0 Summary: Printing over Samba does not work Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: uli.2001(a)gmx.de QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- I am trying to print from Opensuse on a shared printer attached to a Windows machine, using Samba. This does not work. The document is not printed and shows up in the Cups webinterface with "status" begin "stopped". It has been working reliably with several Opensuse versions before 11.4. In the webinterface of Cups, I see the following: http://localhost:631/admin/log/error_log E [04/Apr/2011:21:39:20 +0200] Unable to execute /usr/lib/cups/backend/smb: insecure file permissions (0104750) E [04/Apr/2011:21:39:20 +0200] [Job 17] Stopping job because the sheduler could not execute the backend. E [04/Apr/2011:21:39:39 +0200] Unable to execute /usr/lib/cups/backend/smb: insecure file permissions (0104750) E [04/Apr/2011:21:39:39 +0200] [Job 16] Stopping job because the sheduler could not execute the backend. E [04/Apr/2011:21:40:38 +0200] Unable to execute /usr/lib/cups/backend/smb: insecure file permissions (0104750) E [04/Apr/2011:21:40:38 +0200] [Job 18] Stopping job because the sheduler could not execute the backend. E [04/Apr/2011:21:42:37 +0200] Unable to execute /usr/lib/cups/backend/smb: insecure file permissions (0104750) E [04/Apr/2011:21:42:37 +0200] [Job 18] Stopping job because the sheduler could not execute the backend. E [04/Apr/2011:21:45:39 +0200] [Job 18] Stopping unresponsive job! E [04/Apr/2011:21:50:59 +0200] Unable to execute /usr/lib/cups/backend/smb: insecure file permissions (0104750) E [04/Apr/2011:21:50:59 +0200] [Job 18] Stopping job because the sheduler could not execute the backend. This looks similar to the following, but I can't get a workaround out of that: http://forums.opensuse.org/english/get-technical-help-here/network-internet… -- 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 42

[Bug 817142] New: Fail to install on ppc64 system
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=817142 https://bugzilla.novell.com/show_bug.cgi?id=817142#c0 Summary: Fail to install on ppc64 system Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: PowerPC-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: bilias(a)edu.physics.uoc.gr QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=536849) --> (http://bugzilla.novell.com/attachment.cgi?id=536849) failed kernel dmesg User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Hi, I'm having problems with kernel 3.7.10-1.1-default on an IBM p5-520 (9131-52A) with a PCI-X Dual U320 RAID adapter (ipr driver). It cannot detect my hardware raid correctly. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 12

[Bug 702654] New: Typos in audit-laf.pot file
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=702654 https://bugzilla.novell.com/show_bug.cgi?id=702654#c0 Summary: Typos in audit-laf.pot file Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andrea.turrini(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- Created an attachment (id=437146) --> (http://bugzilla.novell.com/attachment.cgi?id=437146) useless y2logs, just to avoid "NEEDINFO" request: please attach y2logs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 The yast/audit-laf.pot file contains the following typos: logfile_settings dialog help 5/8 #: src/helps.ycp:75 msgid "" "Flush: describes how to write the data to disk. If set to INCREMANTAL the\n" "Frequency parameter tells how many records to write before issuing an explicit flush to disk.\n" "NONE means: no special effort is made to flush data, DATA: keep data portion synced,\n" "SYNC: keep data and meta-data fully synced." INCREMANTAL -> INCREMENTAL (I suppose...) #. rules dialog help 1/6 #: src/helps.ycp:145 msgid "" "<big>Rules for auditctl</big> \n" "This dialog offers the possibiltiy to enable or to disable the syscall\n" "auditing as well as to lock the audit configuration.\n" "The selected flag from Set Enabled Flag will be added to the rules." possibiltiy -> possibility #. rules dialog help 3/6 #: src/helps.ycp:152 msgid "" "Enabling auditing whithout additional rules will cause the\n" " applications which use libaudit, e.g. PAM to log to /var/log/audit/audit.log (default). " whithout -> without Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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