April 2012 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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

[Bug 559704] New: gnome-web-photo doesn't work because it can't find libxul.so
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=559704 http://bugzilla.novell.com/show_bug.cgi?id=559704#c0 Summary: gnome-web-photo doesn't work because it can't find libxul.so 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: arizonagroovejet(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-1.1.2 Firefox/3.5.5 mike@continuity:/tmp$ gnome-web-photo http://news.bbc.co.uk foo.png gnome-web-photo: error while loading shared libraries: libxul.so: cannot open shared object file: No such file or directory Reproducible: Always Steps to Reproduce: 1. Try and use gnome-web-photo Actual Results: Error message as shown above. Expected Results: That it works. It can be made to work like this: mike@continuity:/tmp$ LD_LIBRARY_PATH="/usr/lib/xulrunner-1.9.1.5/" gnome-web-photo http://news.bbc.co.uk foo.png *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable). mike@continuity:/tmp$ identify foo.png foo.png PNG 1024x1710 1024x1710+0+0 8-bit DirectClass 530kb -- 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 16

[Bug 578053] New: postgresql-plperl looks for libperl.so in the wrong place
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=578053 http://bugzilla.novell.com/show_bug.cgi?id=578053#c0 Summary: postgresql-plperl looks for libperl.so in the wrong place Classification: openSUSE Product: openSUSE 11.3 Version: Factory 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: eggyknap(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/532.8 (KHTML, like Gecko) Chrome/4.0.299.0 Safari/532.8 On a completely new openSUSE 11.3 machine, I installed the postgresql-server, postgresql, and postgresql-plperl packages. After starting PostgreSQL and letting it initialize a new database, I sudo-d to the postgres user, and tried to add the PL/Perl language, as follows, with the error below: postgres@linux-e16r:~> createlang plperl createlang: language installation failed: ERROR: could not load library "/usr/lib/postgresql/plperl.so": libperl.so: cannot open shared object file: No such file or directory libperl.so lives in /usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE/libperl.so. Creating a symlink at /usr/lib/libperl.so to the installed libperl.so binary works around the problem. This also exists in at least one of the 10.x versions, though I don't have access to the servers to know the precise version(s) As a secondary note, the description of the postgresql-plperl package, at least as it appears in YaST2, says the package also includes PL/Tcl and PL/Python. This is incorrect. Thirdly, the documentation also claims "PostgreSQL also offers the builtin procedural language PL/SQL". This is also incorrect -- PL/SQL is an Oracle-specific language. PostgreSQL offers PL/pgSQL, which fact might be worth noting in the PL/Perl documentation, or it might not. Reproducible: Always Steps to Reproduce: 1.install postgresql, postgresql-server, and postgresql-plperl 2.start postgresql (/etc/init.d/postgresql start) 3.become the postgres user (sudo su - postgres) 4.create the plperl language in the default database: createlang plperl Actual Results: # createlang plperl createlang: language installation failed: ERROR: could not load library "/usr/lib/postgresql/plperl.so": libperl.so: cannot open shared object file: No such file or directory Expected Results: createlang should have no output, and a 0 exit status I realize this is a packaging bug, and likely not something distributed by Novell directly. I saw nowhere else to file the bug. -- 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 551014] New: one click install: error ccoured while initializing the software repository
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=551014 Summary: one click install: error ccoured while initializing the software repository Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: jsrain(a)novell.com Found By: Beta-Customer Created an attachment (id=324701) --> (http://bugzilla.novell.com/attachment.cgi?id=324701) y2logs (11.2 repo from today, probably near RC2) I tried to install YaBSC from the openSUSE:Tools repo using one click install. After entering the root password, YaST showed an error dialog: An error ccoured while initializing the software repository. Details: Try again? [Ja] [Nein] (= Yes / No) Yes, the line after "Details:" was really empty. Therefore this bug has two parts: - the missing information about details in the error dialog - maybe the failure itsself is also a bug The last lines from y2log when the error dialog was open: 2009-10-29 15:48:16 <1> geeko(26435) [zypp] RepoManager.cc(init_knownRepositories):557 end construct known repos 2009-10-29 15:48:16 <3> geeko(26435) [Pkg] Source_Create.cc(RepositoryAdd):449 alias openSUSE:Tools already exists [That's probably the disabled 11.1 version of the openSUSE:tools repo] 2009-10-29 15:48:16 <1> geeko(26435) [Pkg] OneClickInstallWorkerFunctions.ycp:113 Pkg Builtin called: SourceRefreshNow 2009-10-29 15:48:16 <3> geeko(26435) [Interpreter] OneClickInstallWorkerFunctions.ycp:113 Parameter 1 is nil, Integer is required 2009-10-29 15:48:16 <1> geeko(26435) [Pkg] OneClickInstallWorkerFunctions.ycp:116 Pkg Builtin called: LastError 2009-10-29 15:48:16 <1> geeko(26435) [ui] YPushButton.cc(setFunctionKey):183 Guessing button role YOKButton for YPushButton "Ja" at 0x18fb1b8 from function key F10 2009-10-29 15:48:16 <1> geeko(26435) [ui] YPushButton.cc(setFunctionKey):183 Guessing button role YCancelButton for YPushButton "Nein" at 0x198aac 8 from function key F9 The full y2logs are attached. Search for [cb] in y2log - I have marked when the error dialog popped up. BTW: After answering the dialog with yes (= try again) and confirming the repo details, the installation worked. -- 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 630434] New: Server refuses to boot, while used iSCSI based non "/" file system is not available.
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c0 Summary: Server refuses to boot, while used iSCSI based non "/" file system is not available. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: DOlsson(a)WEB.de 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.1 Firefox/3.6.6 On our SLES 11 GM based "mirror" server (running as a virtual XEN guest), we are using iSCSI to attach to our NAS holding the "/data" file system, whereas all other file systems (/, /boot, /var, /home) are placed on local disk. When rebooting the server, it refuses to boot correctly, while it is not able to "fsck" the "/data" file system -- The system stops in "(repair filesystem) #" mode (after having entered the "root" password). Using the "nofail" option for the "/data" file system helps to get the system to reboot correctly, but in this case the "/data" file system is neither being checked nor mounted during the system startup, which therefore -- once again -- makes the system unusable! Using the "nofail" option is part of the "solution" listed in the SLES 11 SP1 documentation, but since the system is unusable, this is *not* the solution to the problem. The problem is that the "mkinitrd" is and the boot scripts are not capable of handling iSCSI attached file systems correctly. The correct way of handling iSCSI attached devices are: - All iSCSI devices having the "onboot" set as node startup setting must be attached during the "initrd" boot sequence (i.e. by "boot.open-iscsi") -- and this *independent* of whether the "/" (root) file system is attached via iSCSI or not, - All iSCSI devices having the "automatic" set as node startup setting need to be attached during the normal booting sequence (i.e. by "open-iscsi"), - All iSCSI devices having the "manual" set as node startup setting should be left alone. Using such a attaching schema will ensure that a server is capable of being booted with all its iSCSI file systems being attached, checked and mounted. Reproducible: Always Steps to Reproduce: 1a. Setup an iSCSI device and mount it e.g. as "/home" (no changes to "/etc/fstab"). 2a. Reboot the system 3a. System fails to boot, while "/home" is not available. 1b. Setup an iSCSI device and mount it e.g. as "/home", and add the "nofail" option in "/etc/fstab" to the "/home" mount point. 2b. Reboot system. 3b. System boots, but "/home" is neither checked nor mounted! Actual Results: When using iSCSI devices for non root file systems - the system is not able to boot, when the file system on the iSCSI device is listed in "/etc/fstab" as a file system that should be mounted or - the system boots boots, when the file system on the iSCSI device has been marked with "nofail" in "/etc/fstab", but the file is neither being checked nor it is being mounted. Expected Results: System boots with all file systems listed in "/etc/fstab" being checked and mounted independently of whether they are on local or iSCSI attached disks. -- 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 91

[Bug 710541] New: Zypper gives no information about where source-install downloads files
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=710541 https://bugzilla.novell.com/show_bug.cgi?id=710541#c0 Summary: Zypper gives no information about where source-install downloads files Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)damienradtke.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1 When installing a package's source using "zypper source-install", no information can be found about where the source is actually downloaded to. "zypper help source-install" doesn't help, nor does "man zypper". The target location is /usr/src/packages/SOURCES, but those unfamiliar with RPM practices won't know that. Please provide a message, such as in the help text for source-install, that points the user to the directory the source was downloaded to. 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 10