October 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 878503] New: xlock: Error in `/usr/lib/xlock/xlock': free(): invalid pointer: 0x0000000002252630
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=878503 https://bugzilla.novell.com/show_bug.cgi?id=878503#c0 Summary: xlock: Error in `/usr/lib/xlock/xlock': free(): invalid pointer: 0x0000000002252630 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)ifyouwantblood.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 SUSE/34.0.1847.116 xlock crashed while running a screensaver. no user input, i came back to my pc and xlock was gone. the memory map doesn't look complete, but there is nothing more. Reproducible: Sometimes Steps to Reproduce: 1. xlock 2. 3. Actual Results: ==== Backtrace: ========= /lib64/libc.so.6(+0x7410f)[0x7f71dd82c10f] /lib64/libc.so.6(+0x7996e)[0x7f71dd83196e] /usr/lib/xlock/xlock[0x423191] /usr/lib/xlock/xlock[0x427e55] /usr/lib/xlock/xlock[0x41133f] /usr/lib/xlock/xlock[0x50ff4d] /usr/lib/xlock/xlock[0x411466] /usr/lib/xlock/xlock[0x40b9b7] /usr/lib/xlock/xlock[0x40bcdc] /usr/lib/xlock/xlock[0x40d6cb] /usr/lib/xlock/xlock[0x40a697] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f71dd7d9be5] /usr/lib/xlock/xlock[0x40af01] ======= Memory map: ======== 00400000-005ac000 r-xp 00000000 00:14 1309675 /usr/lib/xlock/xlock 007ab000-007ac000 r--p 001ab000 00:14 1309675 /usr/lib/xlock/xlock 007ac000-00878000 rw-p 001ac000 00:14 1309675 /usr/lib/xlock/xlock 00878000-008dc000 rw-p 00000000 00:00 0 01e0e000-0235a000 rw-p 00000000 00:00 0 [heap] 7f71d3edb000-7f71d3efb000 rw-s 1d9ddf000 00:04 1290 /dev/dri/card0 7f71d3efb000-7f71d3f1b000 rw-s 1d9dbf000 00:04 1290 /dev/dri/card0 7f71d3f1b000-7f71d3f3b000 rw-s 1d9d9f000 00:04 1290 /dev/dri/card0 7f71d3f3b000-7f71d3f5b000 rw-s 1d9d7f000 00:04 1290 /dev/dri/card0 7f71d3f5b000-7f71d3f7b000 rw-s 1d9d5f000 00:04 1290 /dev/dri/card0 7f71d3f7b000-7f71d3f9b000 rw-s 1d9d3f000 00:04 1290 /dev/dri/card0 7f71d3f9b000-7f71d3fbb000 rw-s 1d9d1f000 00:04 1290 /dev/dri/card0 7f71d3fbb000-7f71d3fdb000 rw-s 1d9cff000 00:04 1290 /dev/dri/card0 7f71d3fdb000-7f71d3ffb000 rw-s 1d9cdf000 00:04 1290 /dev/dri/card0 7f71d3ffb000-7f71d401b000 rw-s 1d9cbf000 00:04 1290 /dev/dri/card0 7f71d401b000-7f71d403b000 rw-s 1d9c9f000 00:04 1290 /dev/dri/card0 7f71d403b000-7f71d405b000 rw-s 1d9c7f000 00:04 1290 /dev/dri/card0 7f71d405b000-7f71d407b000 rw-s 1d9c5f000 00:04 1290 /dev/dri/card0 7f71d407b000-7f71d409b000 rw-s 1d9c3f000 00:04 1290 /dev/dri/card0 7f71d409b000-7f71d40bb000 rw-s 1d9c1f000 00:04 1290 /dev/dri/card0 7f71d40bb000-7f71d40db000 rw-s 1d9bff000 00:04 1290 /dev/dri/card0 7f71d40db000-7f71d40fb000 rw-s 1d9bdf000 00:04 1290 /dev/dri/card0 7f71d40fb000-7f71d411b000 rw-s 1d9bbf000 00:04 1290 /dev/dri/card0 7f71d411b000-7f71d413b000 rw-s 1d9b9f000 00:04 1290 /dev/dri/card0 7f71d439b000-7f71d43bb000 rw-s 1d991f000 00:04 1290 /dev/dri/card0 7f71d43bb000-7f71d43db000 rw-s 1d98ff000 00:04 1290 /dev/dri/card0 7f71d43db000-7f71d43fb000 rw-s 1d98df000 00:04 1290 /dev/dri/card0 7f71d43fb000-7f71d441b000 rw-s 1d98bf000 00:04 1290 /dev/dri/card0 7f71d441b000-7f71d443b000 rw-s 1d989f000 00:04 1290 /dev/dri/card0 7f71d443b000-7f71d445b000 rw-s 1d987f000 00:04 1290 /dev/dri/card0 7f71d445b000-7f71d447b000 rw-s 1d985f000 00:04 1290 /dev/dri/card0 7f71d447b000-7f71d449b000 rw-s 1d983f000 00:04 1290 /dev/dri/card0 7f71d449b000-7f71d44bb000 rw-s 1d981f000 00:04 1290 /dev/dri/card0 7f71d44bb000-7f71d44db000 rw-s 1d97ff000 00:04 1290 /dev/dri/card0 7f71d44db000-7f71d44fb000 rw-s 1d97df000 00:04 1290 /dev/dri/card0 7f71d44fb000-7f71d451b000 rw-s 1d97bf000 00:04 1290 /dev/dri/card0 7f71d451b000-7f71d453b000 rw-s 1d979f000 00:04 1290 /dev/dri/card0 7f71d453b000-7f71d455b000 rw-s 1d977f000 00:04 1290 /dev/dri/card0 7f71d455b000-7f71d457b000 rw-s 1d975f000 00:04 1290 /dev/dri/card0 7f71d457b000-7f71d459b000 rw-s 1d973f000 00:04 1290 /dev/dri/card0 7f71d459b000-7f71d45bb000 rw-s 1d971f000 00:04 1290 /dev/dri/card0 7f71d45bb000-7f71d45db000 rw-s 1d96ff000 00:04 1290 /dev/dri/card0 7f71d45db000-7f71d45fb000 rw-s 1d96df000 00:04 1290 /dev/dri/card0 7f71d45fb000-7f71d467b000 rw-s 1d783d000 00:04 1290 /dev/dri/card0 7f71d467b000-7f71d46fb000 rw-s 1d87ef000 00:04 1290 /dev/dri/card0 7f71d46fb000-7f71d471b000 rw-s 1ccf1a000 00:04 1290 /dev/dri/card0 7f71d471b000-7f71d473b000 rw-s 1ccefa000 00:04 1290 /dev/dri/card0 7f71d473b000-7f71d47bb000 rw-s 1748b7000 00:04 1290 /dev/dri/card0 7f71d47bb000-7f71d483b000 rw-s 174837000 00:04 1290 /dev/dri/card0 7f71d483b000-7f71d48bb000 rw-s 1747b7000 00:04 1290 /dev/dri/card0 7f71d48bb000-7f71d52bb000 rwxp 00000000 00:00 0 7f71d52bb000-7f71d533b000 rw-s 172276000 00:04 1290 /dev/dri/card0 7f71d5343000-7f71d5363000 rw-s 1d96bf000 00:04 1290 /dev/dri/card0 7f71d5363000-7f71d5383000 rw-s 1d969f000 00:04 1290 /dev/dri/card0 7f71d5383000-7f71d53a3000 rw-s 1d967f000 00:04 1290 /dev/dri/card0 7f71d53a3000-7f71d53c3000 rw-s 1cdec3000 00:04 1290 /dev/dri/card0 7f71d53c3000-7f71d53cc000 r-xp 00000000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d53cc000-7f71d55cb000 ---p 00009000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d55cb000-7f71d55cc000 r--p 00008000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d55cc000-7f71d55cd000 rw-p 00009000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d55cd000-7f71d55d7000 r-xp 00000000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d55d7000-7f71d57d6000 ---p 0000a000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d57d6000-7f71d57d7000 r--p 00009000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d57d7000-7f71d57d8000 rw-p 0000a000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d57d8000-7f71d5858000 rw-s 174737000 00:04 1290 /dev/dri/card0 7f71d5858000-7f71d585c000 r-xp 00000000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d585c000-7f71d5a5b000 ---p 00004000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d5a5b000-7f71d5a5c000 r--p 00003000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d5a5c000-7f71d5a5d000 rw-p 00004000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d5a5d000-7f71d5a97000 r-xp 00000000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5a97000-7f71d5c97000 ---p 0003a000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5c97000-7f71d5c99000 r--p 0003a000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5c99000-7f71d5c9a000 rw-p 0003c000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5c9a000-7f71d5cbe000 r-xp 00000000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5cbe000-7f71d5ebe000 ---p 00024000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5ebe000-7f71d5ebf000 r--p 00024000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5ebf000-7f71d5ec0000 rw-p 00025000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5ec0000-7f71d5edf000 r-xp 00000000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d5edf000-7f71d60df000 ---p 0001f000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d60df000-7f71d60e0000 r--p 0001f000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d60e0000-7f71d60e1000 rw-p 00020000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d60e1000-7f71d615c000 r-xp 00000000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d615c000-7f71d635c000 ---p 0007b000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d635c000-7f71d635e000 r--p 0007b000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d635e000-7f71d6360000 rw-p 0007d000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d6360000-7f71d63ce000 r-xp 00000000 00:14 555596 /usr/lib64/ this is a Tumbleweed install. -- 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 815161] New: mount --no-canonical no longer works for output from 'mount"; (but does for df)
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=815161 https://bugzilla.novell.com/show_bug.cgi?id=815161#c0 Summary: mount --no-canonical no longer works for output from 'mount"; (but does for df) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 When I use the no-canonical option in mount, it should take a dev-mapper file like this: /dev/mapper/HnS-Media_Back and change the display device name to /dev/HnS/Media_Back (which is what is listed in /etc/fstab). When I display this with mount, this no longer works. Maybe Mount no longer dispays values from /etc/mtab as it should: The programs mount and umount maintain a list of currently mounted filesystems in the file /etc/mtab. If no arguments are given to mount, this list is printed. Reproducible: Always Steps to Reproduce: 1. put a lvh volume in fstab by it's given name /dev/VolGroup/LogVolName in fstab. 2. Mount it with and without the --no-canonical 3. Try remounting it with "-f" as described in the man page: --no-canonicalize Don't canonicalize paths. The mount command canonicalizes all paths (from command line or fstab) and stores canonicalized paths to the /etc/mtab file. This option can be used together with the -f flag for already canonicalized absolut paths. Actual Results: the canonical name with "mapper" and dashes instead of slashes and double slashes instead of slashes, is shown in the mount command. Note: the "df" command shows the canonical name!! Expected Results: mount should display values from /etc/mtab not /proc/mounts. -- 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 815322] New: device of "$PWD" not in output of mount if on 'root' (/dev/rootfs not in mount output)
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=815322 https://bugzilla.novell.com/show_bug.cgi?id=815322#c0 Summary: device of "$PWD" not in output of mount if on 'root' (/dev/rootfs not in mount output) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 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: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 I have a simple util program that has worked until recently -- I'm not sure if it went into 12.3 (I think so), or if it is in factory. These 3 lines demonstrate the problem: dev=$(df /bin |tail -1|cut -d\ -f1) mountline=$(mount|grep "$dev"); [[ -z ${mountline:-} ]] && mountline=ERROR echo "mounted with /etc/fstab line: '$mountline'" For some reason, the devices shown by 'mount' don't seem to be the devices shown in 'df' nor in /etc/fstab, yet both are documented to use /etc/mtab. Reproducible: Always Steps to Reproduce: 1. Try above script lines -- note that dev for root = /dev/root 2. But note that output of mount doesn't show /dev/root -- (only rootfs). 3. mount doesn't recognize 'rootfs' as a block device or special type: # mount rootfs /mnt mount: special device rootfs does not exist Ishtar:/bin# mount rootfs /mnt -t rootfs mount: wrong fs type, bad option, bad superblock on rootfs, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Actual Results: mount claims root is on a non-existent device. Expected Results: mount should list values in mtab that show existing devices, not non-existent device aliases. -- 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 15

[Bug 852036] New: incorrect work of command _login_
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=852036 https://bugzilla.novell.com/show_bug.cgi?id=852036#c0 Summary: incorrect work of command _login_ Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Microsoft-SUXX(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 login by standart way in system type in console $login "username" 1) result in X - nothing 2) in console Alt-[F1-F6] result of this comman is LOGOUT but if username already loggeid in one of the other console - then rasult is also nothing Reproducible: Always Steps to Reproduce: 1. Add 2 or more user account in system 2. Get in X (graphic mode) console (terminal window) or 2A. Go to clear terminal in Alt-F1...Alt-F6 3. Type: login username Actual Results: In case 2. Nothing In case 2A. result of this command is LOGOUT. but if username already loggeid in one of the other console - then result is nothing Expected Results: Login with username account. -- 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

[Bug 856765] New: glmatrix process does not exit when xdcreensaver stops.
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=856765 https://bugzilla.novell.com/show_bug.cgi?id=856765#c0 Summary: glmatrix process does not exit when xdcreensaver stops. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Situation: 13.1 system with XFCE desktop, freshly installed with all mandatory updates, nvidia proprietary driver (obviously, because it needs 3D to run this app) installed via rpm. Xscreensaver is configured to run GLmatrix screensaver. When the screensaver triggers, and I use the machine again, I see this in top: top - 11:40:06 up 2 days, 12:52, 10 users, load average: 0.10, 0.13, 0.14 Tasks: 249 total, 2 running, 247 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.5 us, 0.9 sy, 0.6 ni, 97.0 id, 1.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 8193444 total, 3444632 used, 4748812 free, 474056 buffers KiB Swap: 22017008 total, 334780 used, 21682228 free, 1524108 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7613 cer 39 19 128488 37036 22104 S 4.318 0.452 0:32.43 glmatrix 31774 root 20 0 344936 216676 35976 S 1.661 2.645 39:55.93 X 5105 cer 20 0 1598580 249768 42852 S 0.332 3.048 8:29.26 thunderbird-bin A process named 'glmatrix' is still running, using more CPU than any - which is why I noticed. It can not be killed normally, it has to be killed 9. See: cer@Elessar:~> killall glmatrix cer@Elessar:~> killall -9 glmatrix cer@Elessar:~> killall glmatrix cer@Elessar:~> killall glmatrix cer@Elessar:~> killall -9 glmatrix cer@Elessar:~> killall -9 glmatrix glmatrix: no process found cer@Elessar:~> -- 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 858493] New: mount-by-device ceased to work properly in 13.1
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=858493 https://bugzilla.novell.com/show_bug.cgi?id=858493#c0 Summary: mount-by-device ceased to work properly in 13.1 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mario.natiello(a)math.lth.se QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 The following fstab entries [CODE] /dev/sdb1 /mount/usbdisk vfat user,rw,noauto 0 0 remuser@IP:. /localuser/target fuse.sshfs users,allow_other,reconnect, follow_symlinks,rw, noauto,_netdev,idmap=user,uid=1000,gid=100, IdentityFile=/localuser/.ssh/id_rsa,ServerAliveInterval=60 0 0 [/CODE] should allow to mount the filesystems just by stating EITHER the device OR the mountpoint as in, e.g., [CODE] > mount /dev/sdb1 > mount /mount/usbdisk > mount /localuser/target [/CODE] All these work ok. However the following one does not work: [CODE] > mount remuser@IP:. mount: remuser@IP:.: No such file or directory > mount --source remuser@IP:. mount: remuser@IP:.: No such file or directory[/CODE] [/CODE] despite the fact that the syntax is supported by the man pages of fstab, mount and sshfs, and despite the fact that it did work in 12.2 and it currently works in other distros (I tried in ubuntu 13.04). Reproducible: Always Steps to Reproduce: 1. Put in fstab a remote device that is mounted by sshfs 2. mount the device by stating "mount device" or "mount --source device" 3. mount fails while "mount mountpoint" does not fail. Actual Results: [/CODE] > mount remuser@IP:. mount: remuser@IP:.: No such file or directory > mount --source remuser@IP:. mount: remuser@IP:.: No such file or directory [/CODE] [/CODE] Expected Results: Remote file system properly mounted -- 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 877685] New: smartmontools can not read information from MegaRaid controller
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=877685 https://bugzilla.novell.com/show_bug.cgi?id=877685#c0 Summary: smartmontools can not read information from MegaRaid controller Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: svalx(a)svalx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 smartmontools-6.2-2.1.2.x86_64 I have a single MegaRaid 9240-8i controller with 8 disks on 2 RAID's. and want to get info about this disks. Reproducible: Always Steps to Reproduce: ---------- # smartctl -i /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd failed: DELL or MegaRaid controller, please try adding '-d megaraid,N' --------- # smartctl -i -d megaraid,0 /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd [megaraid_disk_00] failed: INQUIRY failed --------- $ man smartctl ... megaraid,N - [Linux only] the device consists of one or more SCSI/SAS disks connected to a MegaRAID controller. The non-negative integer N (in the range of 0 to 127 inclusive) denotes which disk on the controller is monitored. Use syntax such as: smartctl -a -d megaraid,2 /dev/sda smartctl -a -d megaraid,0 /dev/sdb smartctl -a -d megaraid,0 /dev/bus/0 The following entry in /proc/devices must exist: For PERC2/3/4 controllers: megadevN For PERC5/6 controllers: megaraid_sas_ioctlN ... --------- $ grep mega /proc/devices 250 megaraid_sas_ioctl --------- So I have megaraid_sas_ioctl instead megaraid_sas_ioctl0 and probably it case of failed inquiry. -- 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

[Bug 862739] New: openvpn creates non-functional client config
by bugzilla_noreply＠novell.com 26 Feb '18

26 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=862739 https://bugzilla.novell.com/show_bug.cgi?id=862739#c0 Summary: openvpn creates non-functional client config Classification: openSUSE Product: openSUSE 13.1 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: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I have recently upgraded our local openvpn endpoint to 13.1, which also meant upgrading openvpn to 2.3.2 . I copied over our existing configuration and added "topology subnet". The new configuration no longer works, it seems to be handing out an invalid client config. Previous config that worked: 2013-07-30T17:02:44.084956+02:00 toshi1 openvpn[5616]: PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.0.0,route 192.168.13.1,ping 10,ping-restart 120,ifconfig 192.168.13.9 192.168.13.10' Current config which doesn't work: 2014-02-07T09:56:14.797888+01:00 toshi1 openvpn[8133]: PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.240.0,topology p2p,ping 10,ping-restart 120,ifconfig 255.255.255.0 192.168.13.10' The "ifconfig 255.255.255.0 192.168.13.10" part looks particularly dodgy and presumably leads to this faulty network config: 4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100 link/none inet 255.255.255.0 peer 192.168.13.10/32 scope global tun0 valid_lft forever preferred_lft forever It is correctable by amending the addresses: ip addr add 192.168.13.9 peer 192.168.13.10 dev tun0 ip addr del 255.255.255.0/32 dev tun0 Reproducible: Always -- 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 901949] New: Valgrind does not support recent Intel instructions
by bugzilla_noreply＠novell.com 22 Feb '18

22 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=901949 Bug ID: 901949 Summary: Valgrind does not support recent Intel instructions Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mjr19(a)cam.ac.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Valgrind does not support the new Haswell instructions. Valgrind is 3.8.1, and 3.9.0 (October 2013) added support for the AVX2 instruction set, as found in Intel's Haswell (released June 2013). OpenSuSE 13.1 (released November 2013) might be expected to support this. pc71:/tmp> cat test.c #include "immintrin.h" #include <stdio.h> int main(){ unsigned int value=1234; unsigned char c; c=_pext_u32(value, 0x11111111); printf("%d\n",(int)c); } pc71:/tmp> g++ -mbmi2 test.c pc71:/tmp> ./a.out 2 pc71:/tmp> valgrind ./a.out [...] vex amd64->IR: unhandled instruction bytes: 0xC4 0xE2 0x7A 0xF5 0xC2 0x88 0x45 0xFB vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=1 VEX.L=0 VEX.nVVVV=0x0 ESC=0F38 vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=1 [...] ==23452== valgrind: Unrecognised instruction at address 0x400642. ==23452== at 0x400642: main (in /tmp/a.out) ==23452== Your program just tried to execute an instruction that Valgrind ==23452== did not recognise. Of course, the above test make sense only when run on a Haswell. Given that 13.1 is an evergreen release, Valgrind probably ought to support fully Intel CPUs released in 2013. Intel's MKL uses some AVX2 instructions unrecognised by the shipped version of Valgrind. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 819514] New: After update pushed 5/10/2013, network unavailable after resuming from sleep
by bugzilla_noreply＠novell.com 20 Feb '18

20 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=819514 https://bugzilla.novell.com/show_bug.cgi?id=819514#c0 Summary: After update pushed 5/10/2013, network unavailable after resuming from sleep Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonysu(a)su-networking.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 First reported in this Forum thread http://forums.opensuse.org/english/get-technical-help-here/network-internet… For others in the thread, unknown whether recommendations were helpful. Note that others in the thread were not using Network Manager, whereas I am. For myself, my wireless networking was not functional (for that matter any networking) was functional resuming from sleep. Attempted to systemctl stop|start|restart network.service systemctl status network service returned Active with no errors after each above attempt. Service was verified stopped and restarted without errors. After rebooting, my network was still unavailable. Attampted again to stop|start|restart services. Then, I did a hardware NIC disable/re-enable which resulted in NM reporting networking enabled, but wireless "undetermined" (no check or unchecked box, a weird white box). Using NM, unchecked, re-checked "networking" and the wireless box was "normal, unchecked" Checked the box an wireless is working. After the wireless working was working again, I re-ran "systemctl status network.service" with the following results NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat 2013-05-11 14:35:15 PDT; 56s ago Main PID: 26829 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └─26829 /usr/sbin/NetworkManager --no-daemon May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr0): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> ModemManager available in the bus The above may not be helpful, I suspect that the errors only refer to a number of virtual device bridges I have configured on this machine, but of course NM does not support managing those. Reproducible: Always Steps to Reproduce: 1. zypper up 5/10/2013 2. Put machine to sleep 3. resume machine Actual Results: Networking unavailable. Expected Results: Network should re-connect to available networks automatically Assigning Major, but impact likely depends on whether the User is able to regain networking either by restarting the network service or re-booting. If there are critical programs which would be adversely affected by a re-boot, then the problem is very serious, maybe even critical. -- 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