February 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 863116] New: Missing info file in dummy gssd entry in rpc_pipefs
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=863116 https://bugzilla.novell.com/show_bug.cgi?id=863116#c0 Summary: Missing info file in dummy gssd entry in rpc_pipefs 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: manfred.h(a)gmx.net 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 After installing the latest kernel update (kernel-desktop-3.11.10-7.1.x86_64) my NFSv4 servers (no Kerberos configured, but rpc.gssd enabled to avoid long initial timeouts when accessing the NFS shares) started to generate loads of log entries when a client is attempting to mount a share: 2014-02-10T18:15:43.068324+01:00 melmac rpc.gssd[3385]: ERROR: can't open /var/lib/nfs/rpc_pipe fs/gssd/clntXX/info: No such file or directory 2014-02-10T18:15:43.068744+01:00 melmac rpc.gssd[3385]: ERROR: failed to read service info This repeats several times and generates lots of entries in the /var/log/messages file. It should be noted that the mount on the client succeeds nevertheless. Previous kernels didn't show this behaviour. This issue might be related with a similar one found in Fedora; here's the corresponding bug report: <https://bugzilla.redhat.com/show_bug.cgi?id=1037793> It looks like they've added some patches to also address the initial timeout issue I mentioned earlier. Reproducible: Always Steps to Reproduce: 1. Install kernel-desktop-3.11.10-7.1.x86_64 and nfs-kernel-server-1.2.8-4.5.1.x86_64 2. Setup an NFSv4 server 3. mount -t nfs4 server:/ /mnt # on the client Actual Results: Lots of messages are generated similar to the following ones: 2014-02-10T18:15:43.068324+01:00 melmac rpc.gssd[3385]: ERROR: can't open /var/lib/nfs/rpc_pipefs/gssd/clntXX/info: No such file or directory 2014-02-10T18:15:43.068744+01:00 melmac rpc.gssd[3385]: ERROR: failed to read service info Expected Results: While the mount succeeds, the ERROR messages should be looked at and fixed. -- 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 1

[Bug 861923] New: c99: command not found
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=861923 https://bugzilla.novell.com/show_bug.cgi?id=861923#c0 Summary: c99: command not found Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Development AssignedTo: matz(a)suse.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de CC: coolo(a)suse.com, rguenther(a)suse.com Found By: Beta-Customer Blocker: --- In openSUSE 13.1, make-3.82 did the following: $ echo .POSIX: >Makefile $ make -p 2>&1 | grep ^CC CC := cc With make-4.0 that now ships in openSUSE Factory, this has changed to CC := c99 However, our gcc package does not provide a c99 symlink yet, breaking compilation that use implicit variables/rules. -- 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 862975] New: Using "tmp" option in /etc/crypttab for /tmp creates unwritable /tmp
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862975 https://bugzilla.novell.com/show_bug.cgi?id=862975#c0 Summary: Using "tmp" option in /etc/crypttab for /tmp creates unwritable /tmp Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: arvidjaar(a)gmail.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 /etc/crypttab provides "tmp" option in which case device is setup using random key every boot and fresh filesystem is created. This means that fileystem root permissions are reset to default 755, making it non-user writable. In the past /etc/init.d/boot.crypto would explicitly set /tmp permissions to 1777 after mounting it, but it was lost after migration to systemd. This causes all sort of serious issues including KDM failing to start. See https://forums.opensuse.org/showthread.php/495266-After-update-root-works-b… 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

[Bug 859931] New: The unit files have no [Install] section. They are not meant to be enabled using systemctl.
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=859931 https://bugzilla.novell.com/show_bug.cgi?id=859931#c0 Summary: The unit files have no [Install] section. They are not meant to be enabled using systemctl. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem 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 enabled mdadm using "systemctl enable mdadmd": # systemctl enable mdadmd mdadmd.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig mdadmd on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). The LSB init files are not meant to have an [Install] section, why is systemctl complaining about it? 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 862984] New: Yast partitioner does not show up with existing bcache device
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862984 https://bugzilla.novell.com/show_bug.cgi?id=862984#c0 Summary: Yast partitioner does not show up with existing bcache device Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: rohano(a)freenet.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 After creating bcache device /dev/bcache0 with bcache tools the partitioner modul of yast dies after showing "Initializing" without further hints. /var/log/messages shows 2014-02-09T17:11:21.276567+01:00 xxxx kernel: [ 3231.626578] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found 2014-02-09T17:11:21.276600+01:00 xxxx kernel: [ 3231.626586] EDD information not available. Reproducible: Always Steps to Reproduce: 1. create /dev/bcache* 2. start Yast and select partitioner 3. /dev/bcache0 does not appear in fdisk -l Actual Results: After creating /dev/bcache0 is functional and can be used without obvious problems. Yast partitioner doesn't work at all Expected Results: Show the bcache device, (until thats realized at least the non "bcached" partitions/devices as normally) -- 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 862886] New: installation fails in grub2 installation
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=862886 https://bugzilla.novell.com/show_bug.cgi?id=862886#c0 Summary: installation fails in grub2 installation Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: suse(a)lists.killian.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Firefox/26.0 It gets to saving the bootloader configuration and hangs. I switch to the console window and see: *** Starting YaST2 *** Perl-Bootloader: 2014-02-07 13:37:16 yast-1521.1 FileIO::ReadFile.85: Error: Failed to open /etc/default/grub_installdevice: No such file or directory Perl-Bootloader: 2014-02-07 13:37:16 yast-1521.1 FileIO::ReadFile.85: Error: Failed to open /etc/default/grub: No such file or directory .. Perl-Bootloader: 2014-02-07 13:37:16 yast-1521.1 Core::GRUB2::GrubDev2UnixDevices.215: Error: did not find a match for hd0 in the device map sh: /usr/bin/grub2-editenv: No such file or directory sh: /usr/bin/grub2-editenv: No such file or directory Is there a workaround? sh: /usr/bin/grub2-editenv: No such file or directory Reproducible: Always Steps to Reproduce: 1. Boot from .iso on USB flash drive 2. Create /boot, /, swap, and data partitions on sda 3. Use default installation options -- 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 818019] New: ppc64 install initrd is too big to load over tftp
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=818019 https://bugzilla.novell.com/show_bug.cgi?id=818019#c0 Summary: ppc64 install initrd is too big to load over tftp Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: PowerPC-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dvaleev(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- There is a limit for Power machines, to have initrd is not bigger than 32MB. initrd needs to be reduced, to be able to do network installs. Current size of initrd is 37MB. -- 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 860487] New: Fail message during boot
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860487 https://bugzilla.novell.com/show_bug.cgi?id=860487#c0 Summary: Fail message during boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fdan52(a)comcast.net 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 Every boot I get the message: Failed to start LSB: Configure network interfaces and set up routing. It doesn't effect operations it would appear, at least to me. But I am a little concerned and curious as to whether this will have deeper issues. If not, what other failures during boot can be ignored. Reproducible: Always Steps to Reproduce: 1. Just boot 2. 3. Actual Results: During boot the following line appears: Failed to start LSB: Configure network interfaces and set up routing. Expected Results: LSB: Configure network interfaces and set up routing does not appear, I worked PPA, ORT and was a sysadmin at SUN Microsystems, So I got into the habit of watching the outputs during boots. Seeing failures I can't figure out always caught my attention. -- 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 1

[Bug 860093] New: kde proxy settings, confusion between global settings and app settings
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860093 https://bugzilla.novell.com/show_bug.cgi?id=860093#c0 Summary: kde proxy settings, confusion between global settings and app settings 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: epistemepromeneur(a)free.fr 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 in kde settings/network/proxy settings i expect when setting this setting is for all internet access thus all apps but in proxy settings of kmail or chokoq or else i expect when setting this setting is only for kmail or chokoq this is not the case . in proxy settings of a kde app you set proxy settings globaly for all app ! with VLC if i set vlc proxy setting i set proxy settings only for VLC it's a pb . why ? i use privoxy to delete advertisements when surfing with my browsers . privoxy is for web browsers ; it is non sense to use it for example with kmail or chokoq ; privoxy is not build for this . 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 4

[Bug 860476] New: some programs won't start at boot and unable to shutdown
by bugzilla_noreply＠novell.com 10 Feb '14

10 Feb '14

https://bugzilla.novell.com/show_bug.cgi?id=860476 https://bugzilla.novell.com/show_bug.cgi?id=860476#c0 Summary: some programs won't start at boot and unable to shutdown Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dennisgrunert(a)hotmail.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=575847) --> (http://bugzilla.novell.com/attachment.cgi?id=575847) difference between failed and successful boot User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 openSUSE 13.1 installation (not a fresh install, but upgraded several times from 11.x) In the openSUSE system settings, I have added some programs to start at boot time, like pidgin, dropbox and some scripts. Also I have selected that at each boot a new session will be started. Now at around half of all boots some of the programs (always the same), won't start. Successfully started: * network manager * kde device notifier * knotify * a windows calendar started with wine Failed to start: * kmix * klipper * pidgin * dropbox Interestingly I can start these programs manually without any problems. It seems they were just forgotten at the boot process. Also I cannot shutdown the computer with the button in kmenue, when the bug appears (when all programs start, I can shutdown like always). I first need to log-in as root and init 6. Then I have again a 50:50 chance of a successful boot. I compared ps -aux at a successful (boot_succ.txt) and a failed (boot_failed.txt) boot with diff and found that amongst others /usr/lib64/kde4/libexec/polkit-kde-authentication-agent-1 is not started. Maybe this is the root of the bug? Also this bug reminds me of Bug 812462 which I experienced before (but I followed the fix and it worked). Attached will be the ps -aux outputs (only process names) and the diff file. I can give additional information if needed. Reproducible: Sometimes -- 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