February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 770385] New: Missing documentation on O_PATH
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=770385 https://bugzilla.novell.com/show_bug.cgi?id=770385#c0 Summary: Missing documentation on O_PATH Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: pgajdos(a)suse.com ReportedBy: werner(a)suse.com QAContact: ke(a)suse.com CC: aj(a)suse.com Found By: Development Blocker: --- during a discussion on the developers mailing list of the ksh about a missing feature of the linux kernel, Linus Torvalds had explained that the kernel has the flag O_PATH which provides a similar feature than the POSIX flag O_SEARCH. I've found that the manual page open(2) does not show the flag O_PATH but includes a remark in the comments: .\" .\" FIXME . Apr 08: The next POSIX revision has O_EXEC, O_SEARCH, and .\" O_TTYINIT. Eventually these may need to be documented. --mtk .\" FIXME Linux 2.6.33 has O_DSYNC, and a hidden __O_SYNC. .\" FIXME: Linux 2.6.39 added O_PATH .\" ... IMHO there is missed an entry in the DESCRIPTION section of open(2) and/or fcntl(2) manual page(s). -- 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 860480] New: Name resolution of hostname (with .site) fails
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860480 https://bugzilla.novell.com/show_bug.cgi?id=860480#c0 Summary: Name resolution of hostname (with .site) fails Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: novell_login(a)wired-brain.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 The hostname chosen in OpenSuSE is automatically appended with .site or any other chose domain. I have a laptop installation where it is something.site. This is also reported correctly by the hostname shell command. But it cannot be resolved back to an IP address using the command host: $> host `hostname` Host something.site not found: 3(NXDOMAIN) When just resolving the part before the dot (something), the answer of the local DNS server is presented ( a fritzbox): $> host something something.fritz.box has address 192.168.178.20 I tried to fix this in /etc/hosts, but the following line had no effect: 127.0.0.1 localhost something.site something I stumbled upon this when using a corba from java which calls a method InetAddress.getLocalHost().getHostName() which fails. Reproducible: Always Steps to Reproduce: In the (bash) shell execute: host `hostname` Actual Results: Host something.site not found: 3(NXDOMAIN) Expected Results: something.site has address 127.0.0.1 -- 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 864264] New: deleting alias raises exception during write
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=864264 https://bugzilla.novell.com/show_bug.cgi?id=864264#c0 Summary: deleting alias raises exception during write Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: mfilka(a)suse.com ReportedBy: mfilka(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Reminder for me. 1) start yast2 lan 2) edit a device 3) add an alias (used prefixlen instead of netmask if it makes difference) 4) go back to overview 5) edit the device again 6) delete the alias 7) go back to overview 8) "OK" -> writing raises exception -- 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 863891] New: Crash with Segmentation fault
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=863891 https://bugzilla.novell.com/show_bug.cgi?id=863891#c0 Summary: Crash with Segmentation fault Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: iron.bone(a)wp.pl QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=578566) --> (http://bugzilla.novell.com/attachment.cgi?id=578566) The log file just after crash User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 Sometimes the X.Org crash with segmentation fault. I can see any typical situation - but often it happens when the computer is not used. I attach the log just after the crash Reproducible: Sometimes 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 4

[Bug 774126] New: login via serial console fails
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=774126 https://bugzilla.novell.com/show_bug.cgi?id=774126#c0 Summary: login via serial console fails Classification: openSUSE Product: openSUSE 12.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jeffm(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- I have a system where the primary console is via serial. It is running systemd. There are two agetty processes running, once on ttyS0 and one on tty1. I haven't tried the one on tty1. On ttyS0, I can enter the username but the login fails immediately after I type the first character of the password. The log shows: Aug 1 15:00:56 sled1 login: FAILED LOGIN 1 FROM ttyS0 FOR root, Authentication failure ... after that the results are unpredictable. It won't even accept the username. >From past experience, it seems as though there are multiple listeners on the serial port but there is only one agetty process running and lsof shows only that agetty process with that serial port open. -- 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 26

[Bug 858959] New: libhugetlbfs: mmap() with misaligned length 0x1000 got succeeded
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=858959 https://bugzilla.novell.com/show_bug.cgi?id=858959#c0 Summary: libhugetlbfs: mmap() with misaligned length 0x1000 got succeeded Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: mhocko(a)suse.cz ReportedBy: cachen(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- STEPS: 1. install libhugetlbfs package 2. echo 128 >/proc/sys/vm/nr_hugepages 3. run /usr/lib64/libhugetlbfs/tests/run_tests.py PROBLEMS: misalign (2M: 64) test failed Starting testcase "/usr/lib64/libhugetlbfs/tests/obj64/misalign", pid 7135 Mapped at 0x2aaaaac00000, length 0x200000 FAIL mmap() with misaligned length 0x1000 succeeded This testcase ensures that attempted hugepage mappings with parameters which are not correctly hugepage aligned are rejected -- 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 3

[Bug 815831] New: systemd[1]: Job sys-devices-virtual-block-dm\x2d0.device/stop timed out.
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=815831 https://bugzilla.novell.com/show_bug.cgi?id=815831#c0 Summary: systemd[1]: Job sys-devices-virtual-block-dm\x2d0.device/stop timed out. Classification: openSUSE Product: openSUSE 12.3 Version: Final 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: gp(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- There are two bugs here: #1, the fact that upon system shutdown sometimes (not always), I get the following message: systemd[1]: Job sys-devices-virtual-block-dm\x2d0.device/stop timed out. #2, and that is what I am focusing on here since #1 is not always nor easily reproducible, is that stray \x2d0 in that error message. That's strange. -- 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 623434] New: System crash during install with language=german and unchecking UTF-8
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

http://bugzilla.novell.com/show_bug.cgi?id=623434 http://bugzilla.novell.com/show_bug.cgi?id=623434#c0 Summary: System crash during install with language=german and unchecking UTF-8 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: haenig(a)cosifan.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE If one installs OpenSuSE 11.3 with german as installation language and later unchecks the UTF-8 option in locale settings, the installer crashes Reproducible: Always Steps to Reproduce: - boot from installation DVD - switch language to german (<F2>) - proceed (new install, everything else on default too, ...) - in installation settings => locale setting => language => primary language (deutsch) => details deselect "use UTF-8 Encoding" - click "O.K." - click "accept" (to return to installation settings) Actual Results: YaST's ASCII mode appears with the following error message "in der Installation trat ein Fehler auf" ("an error occured during the installation") Expected Results: Installation should simly continue -- 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 857970] New: systemd mounts nfs shares on startup, but forgets to umount them before network shutdown
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=857970 https://bugzilla.novell.com/show_bug.cgi?id=857970#c0 Summary: systemd mounts nfs shares on startup, but forgets to umount them before network shutdown Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Outsourced Testing Blocker: --- Created an attachment (id=573753) --> (http://bugzilla.novell.com/attachment.cgi?id=573753) 13.1-nfs-mount-shutdown-hang.txt 13.1 with xfce desktop. I copied the fstab from another partition, it contains also a nfs entry: IP:/share/dir /local/dir nfs soft,intr,tcp,bg,vers=3 0 0 For some reason this nfs entry gets mounted automatically, I did not do anything regarding nfs. But during 'init 6' or 'init 0' the network is stopped before that nfs share is umounted. As a result the system hangs forever at the end of the shutdown, because IP does not respond. No surprise, the network is down already! So whatevers does the automounting of such nfs share must also take care of autoumounting it before the network disappears. -- 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 864172] New: NFS mount fails after last kernel update
by bugzilla_noreply＠novell.com 17 Feb '14

17 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=864172 https://bugzilla.novell.com/show_bug.cgi?id=864172#c0 Summary: NFS mount fails after last kernel update Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pan(a)iba-group.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 Since the last kernel update, NFS is broken on 2 of my boxes. Both are OpenSUSE 12.3 64bit. Both had NFS working fine until last week or something. Current kernel is: Linux tycho.heron.net 3.7.10-1.28-desktop #1 SMP PREEMPT Mon Feb 3 14:11:15 UTC 2014 (c9a2c6c) x86_64 x86_64 x86_64 GNU/Linux. Trying to mount the NFS share manually gives this error message: tycho:~ # mount /data mount.nfs: mount system call failed And the following is logged in /var/log/messages: 2014-02-15T09:58:09.342154+01:00 tycho kernel: [ 2415.118850] NFS: nfs4_discover_server_trunking unhandled error -2. Exiting with error EIO Yes, rpcbind is running and the nfs kernel modules are loaded. I've not changed the definition of the NFS targets in fstab on either machine. Also, one of them is a laptop that I use on different networks (home and office), and the NFS mounts fail in both environments. According to user "arvidjaar": "it was reported multiple times and for different distros. [...] the simplest workaround is to force NFSv3 (option vers=3)." That workaround does indeed allow the NFS share to be mounted successfully. Reproducible: Always Steps to Reproduce: 1. Define an NFS share in your /etc/fstab without specifying the protocol version number to be used (defaults to 4) 2. Try to mount it manually (the automatic mount at boot has already failed, of course) Actual Results: tycho:~ # mount /data mount.nfs: mount system call failed tycho:~ # tail /var/log/messages [...] 2014-02-15T09:58:09.342154+01:00 tycho kernel: [ 2415.118850] NFS: nfs4_discover_server_trunking unhandled error -2. Exiting with error EIO Expected Results: NFS share mounted on local mount point. -- 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 3