December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 852992] New: eclipse crash due to bug in webkit
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=852992 https://bugzilla.novell.com/show_bug.cgi?id=852992#c0 Summary: eclipse crash due to bug in webkit 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: nico.kruber(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Eclipse 4.3 seems to crash because of a bug in webkit as soon as you hover over a function with documentation (rendered with webkit). see https://bugs.webkit.org/show_bug.cgi?id=118396 (includes a fix) https://bugs.eclipse.org/bugs/show_bug.cgi?id=400626 Reproducible: Always Steps to Reproduce: 1. open eclipse 4.3 (supposedly also happens with 4.4) 2. open a java file 3. mouse-hover over a function that has documentation attached to it Actual Results: eclipse crashes Expected Results: no crash -- 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 838226] New: YaST2: ext3 formating error during installation
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=838226 https://bugzilla.novell.com/show_bug.cgi?id=838226#c0 Summary: YaST2: ext3 formating error during installation Classification: openSUSE Product: openSUSE 12.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: abergmann(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- The system was supposed to be installed on a single root partition. The partition table was looking like this: # type size mount point 1 SWAP 750MB - 2 EXT3 25GB / During ext3 formatting an error message is displayed and the setup is aborted. ------------------------------- System error code was: -3008 /sbin/mke2fs -O dir_index -m4.1 -t ext3 -v '/dev/sda2': mke2fs 1.42.6 (21-Sep-2012) Continue despite the error? ------------------------------- See y2log output for (maybe) more details. -- 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 19

[Bug 844336] New: wrmsr in msr-tools fails to write whole 64 bits value
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=844336 https://bugzilla.novell.com/show_bug.cgi?id=844336#c0 Summary: wrmsr in msr-tools fails to write whole 64 bits value Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jin.kyu.song(a)intel.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 wrmsr executable included in msr-tools-1.2-43.4.x86_64.rpm cannot write 64bit value to MSR. Only low 32bits are written. Disassembled code for wrmsr : 400aca: e8 41 fe ff ff call 400910 <strtoull@plt> 400acf: 41 83 fc ff cmp r12d,0xffffffff 400ad3: 4c 63 e8 movsxd r13,eax -> return value from strtoull() is treated as 32bits (eax instead of rax). This is where truncation occurs. 400ad6: 74 10 je 400ae8 <__sprintf_chk@plt+0x148> 400ad8: 44 89 e2 mov edx,r12d 400adb: 4c 89 ee mov rsi,r13 -> truncated value is passed to wrmsr_on_cpu() 400ade: 44 89 ff mov edi,r15d 400ae1: e8 9a 01 00 00 call 400c80 <__sprintf_chk@plt+0x2e0> It seems like OpenSuse packager of msr-tools has a wrong prototype of strtoull() or they do not even have a prototype declared. Reproducible: Always Steps to Reproduce: Example : Try setting CQoS per core// Successful # wrmsr –p 1 0xc8f 1 # rdmsr –p 1 0xc8f 1 Try setting CQoS, second attempt //Unsuccessful # wrmsr –p 0 0xc8f 0x10000000 # rdmsr –p 0 0xc8f 0 Expected Results: 0x10000000 msr-tools are moved to 01.org/msr-tools, which directs to the latest (version 1.3) source code repository at github.com/01org/msr-tools . Version 1.3 added cpuid utility. Please update with the latest code. -- 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 777394] New: grub2: does not know how to resolve MD
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=777394 https://bugzilla.novell.com/show_bug.cgi?id=777394#c0 Summary: grub2: does not know how to resolve MD Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: PowerPC OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- grub2 is not smart enough to understand really simple RAID1s. Rescue:/ # grub2-install Couldn't find IEEE1275 device tree path for md. You will have to set `boot-device' variable manually. /boot is on /dev/md0, which is a md0 : active raid1 sda3[0] sdc3[2] sdb3[1] 204788 blocks super 1.0 [3/3] [UUU] The version is grub2-2.00-4.1.ppc. -- 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 855948] New: zypper: problem comparing version numbers
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855948 https://bugzilla.novell.com/show_bug.cgi?id=855948#c0 Summary: zypper: problem comparing version numbers Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: koenig(a)linux.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- trying to update MPlayer I noticed this problem: 1.1.1 should be newer as 1.1 ?! but I understand that it's difficult to handle all those separator characters between digits in a universal and perfect way:-( # rpm -q MPlayer MPlayer-1.1+35127-4.1.x86_64 # zypper in MPlayer-1.1.1+r36500-6.4 Loading repository data... Reading installed packages... The selected package 'MPlayer-1.1.1+r36500-6.4.x86_64' from repository 'Packman Repository' has lower version than the installed one. Use 'zypper install --oldpackage MPlayer-1.1.1+r36500-6.4.x86_64' to force installation of the package. Resolving package dependencies... # zypper install --oldpackage MPlayer-1.1.1+r36500-6.4.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: gmplayer-1.1+35127-4.1.x86_64 requires MPlayer = 1.1+35127, but this requirement cannot be provided deleted providers: MPlayer-1.1+35127-4.1.x86_64 Solution 1: downgrade of gmplayer-1.1+35127-4.1.x86_64 to gmplayer-1.1.1+r36500-6.4.x86_64 Solution 2: do not install MPlayer-1.1.1+r36500-6.4.x86_64 Solution 3: break gmplayer-1.1+35127-4.1.x86_64 by ignoring some of its dependencies so I "downgraded" to the "older" 1.1.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 2

[Bug 809242] New: Squashfs 4.2-1.2 is compiled without lzma support
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=809242 https://bugzilla.novell.com/show_bug.cgi?id=809242#c0 Summary: Squashfs 4.2-1.2 is compiled without lzma support Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: openSUSE 12.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: steve-holvoet(a)edpnet.be QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 squashfs 4.2-1.2 is compiled without lzma support so it does not support mounting/extracting lzma compressed squashed filesystems. Tried extracting a lzma compressed squashed filesystem from an embedded system and was unable to do so with the unsquashfs 4.2 tool provided by the OpenSUSE 12.1 repo. Reproducible: Always Steps to Reproduce: 1.unsquashfs Actual Results: SYNTAX: unsquashfs [options] filesystem [directories or files to extract] -v[ersion] print version, licence and copyright information -d[est] <pathname> unsquash to <pathname>, default "squashfs-root" -n[o-progress] don't display the progress bar -no[-xattrs] don't extract xattrs in file system -x[attrs] extract xattrs in file system (default) -p[rocessors] <number> use <number> processors. By default will use number of processors available -i[nfo] print files as they are unsquashed -li[nfo] print files as they are unsquashed with file attributes (like ls -l output) -l[s] list filesystem, but don't unsquash -ll[s] list filesystem with file attributes (like ls -l output), but don't unsquash -f[orce] if file already exists then overwrite -s[tat] display filesystem superblock information -e[f] <extract file> list of directories or files to extract. One per line -da[ta-queue] <size> Set data queue to <size> Mbytes. Default 256 Mbytes -fr[ag-queue] <size> Set fragment queue to <size> Mbytes. Default 256 Mbytes -r[egex] treat extract names as POSIX regular expressions rather than use the default shell wildcard expansion (globbing) Decompressors available: gzip Expected Results: SYNTAX: unsquashfs [options] filesystem [directories or files to extract] -v[ersion] print version, licence and copyright information -d[est] <pathname> unsquash to <pathname>, default "squashfs-root" -n[o-progress] don't display the progress bar -no[-xattrs] don't extract xattrs in file system -x[attrs] extract xattrs in file system (default) -p[rocessors] <number> use <number> processors. By default will use number of processors available -i[nfo] print files as they are unsquashed -li[nfo] print files as they are unsquashed with file attributes (like ls -l output) -l[s] list filesystem, but don't unsquash -ll[s] list filesystem with file attributes (like ls -l output), but don't unsquash -f[orce] if file already exists then overwrite -s[tat] display filesystem superblock information -e[f] <extract file> list of directories or files to extract. One per line -da[ta-queue] <size> Set data queue to <size> Mbytes. Default 256 Mbytes -fr[ag-queue] <size> Set fragment queue to <size> Mbytes. Default 256 Mbytes -r[egex] treat extract names as POSIX regular expressions rather than use the default shell wildcard expansion (globbing) Decompressors available: gzip lzma lzo xz Please rebuild with XZ_SUPPORT = 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 622241] New: grub failure on disk larger 2TiB
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

http://bugzilla.novell.com/show_bug.cgi?id=622241 http://bugzilla.novell.com/show_bug.cgi?id=622241#c0 Summary: grub failure on disk larger 2TiB Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: duwe(a)novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Blocker: --- Grub still fails on disk larger than 2 TiB even if the root partition is located well below 2TiB. The problem seems to be that grub still used GETSIZE instead of GETSIZE64 as already observed in bug #591566. -- 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 3

[Bug 685674] New: The "-I" flag of traceroute is blocked by apparmor
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=685674 https://bugzilla.novell.com/show_bug.cgi?id=685674#c0 Summary: The "-I" flag of traceroute is blocked by apparmor Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: 64bit OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: jeffm(a)novell.com ReportedBy: nrickert(a)ameritech.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 Attempts to use: traceroute -I destination fail with "permission denied", even when the user is root. This turns out to be an apparmor problem. Reproducible: Always Steps to Reproduce: 1.# traceroute -I yahoo.com 2.(assumes that apparmor is being used) 3. Actual Results: Note: the -i and -I options were exchangedfor compability with LBL traceroute Use -I for ICMP, and -i <ifname> to specify the interface name unable to create ICMP send socket: Permission denied Expected Results: There should be a route trace using ICMP echo requests. /var/log/audit/audit.log showed the line: type=AVC msg=audit(1302098571.660:201): apparmor="DENIED" operation="create" par ent=446 profile="/usr/sbin/traceroute" pid=5840 comm="traceroute" family="inet" sock_type="raw" protocol=255 I was able to work around the problem by editing the apparmor profiles in Yast, adding a line to allow "network inet raw" for traceroute, which apparently allows the use of raw sockets. This seems to be an oversight in preparing the default rules for apparmor -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 851835] New: Kerberos authentication not working after opensuse upgrade 12.3 to 13.1
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=851835 https://bugzilla.novell.com/show_bug.cgi?id=851835#c0 Summary: Kerberos authentication not working after opensuse upgrade 12.3 to 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: Upgrade Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: omusson(a)epo.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 Before upgrade I could logon (kdm/xdm), ftp, telnet, ssh using Kerberos authentication. Now only the SSH authentication is working for all the others connection is refused. Turning debug on in kerberos client I get this error : pam_setcred(PAM_ESTABLISH_CRED) returning 14 (Cannot make/remove an entry for the specified session) Funny thing is I enter with local authentication and when I lock my screen I can use password from Kerberos to unlock it. So it looks like a session opening problem. Reproducible: Always Steps to Reproduce: 1.ftp connect from Windows XP machine to remote server (Opensuse 13.1) 2.enter user 3.enter password 4. 530 login incorrect. Actual Results: Connection refused Expected Results: Access granted 2013-11-22T13:24:07.936003+01:00 om03830s vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=om03830 rhost=10.3.203.140 user=om03830 2013-11-22T13:24:07.936360+01:00 om03830s vsftpd: pam_krb5[12362]: flag: debug 2013-11-22T13:24:07.936606+01:00 om03830s vsftpd: pam_krb5[12362]: flag: don't always_allow_localname 2013-11-22T13:24:07.936890+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_afs 2013-11-22T13:24:07.937146+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no null_afs 2013-11-22T13:24:07.937417+01:00 om03830s vsftpd: pam_krb5[12362]: flag: cred_session 2013-11-22T13:24:07.937737+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_k5login 2013-11-22T13:24:07.938013+01:00 om03830s vsftpd: pam_krb5[12362]: flag: user_check 2013-11-22T13:24:07.938366+01:00 om03830s vsftpd: pam_krb5[12362]: will try previously set password first 2013-11-22T13:24:07.938693+01:00 om03830s vsftpd: pam_krb5[12362]: will let libkrb5 ask questions 2013-11-22T13:24:07.938925+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no use_shmem 2013-11-22T13:24:07.939150+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no external 2013-11-22T13:24:07.939377+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no multiple_ccaches 2013-11-22T13:24:07.939602+01:00 om03830s vsftpd: pam_krb5[12362]: flag: validate 2013-11-22T13:24:07.939796+01:00 om03830s vsftpd: pam_krb5[12362]: flag: warn 2013-11-22T13:24:07.940070+01:00 om03830s vsftpd: pam_krb5[12362]: minimum uid: 1 2013-11-22T13:24:07.940285+01:00 om03830s vsftpd: pam_krb5[12362]: banner: Kerberos 5 2013-11-22T13:24:07.940573+01:00 om03830s vsftpd: pam_krb5[12362]: ccache dir: /tmp 2013-11-22T13:24:07.940789+01:00 om03830s vsftpd: pam_krb5[12362]: ccname template: DIR:/run/user/%U/krb5cc_XXXXXX 2013-11-22T13:24:07.940996+01:00 om03830s vsftpd: pam_krb5[12362]: keytab: FILE:/etc/krb5.keytab 2013-11-22T13:24:07.941203+01:00 om03830s vsftpd: pam_krb5[12362]: token strategy: 2b,rxk5 2013-11-22T13:24:07.941412+01:00 om03830s vsftpd: pam_krb5[12362]: pam_authenticate called for 'om03830', realm 'INTERNAL.EPO.ORG' 2013-11-22T13:24:07.941630+01:00 om03830s vsftpd: pam_krb5[12362]: authenticating 'om03830(a)INTERNAL.EPO.ORG' 2013-11-22T13:24:07.941859+01:00 om03830s vsftpd: pam_krb5[12362]: trying previously-entered password for 'om03830', allowing libkrb5 to prompt for more 2013-11-22T13:24:07.942079+01:00 om03830s vsftpd: pam_krb5[12362]: authenticating 'om03830(a)INTERNAL.EPO.ORG' to 'krbtgt/INTERNAL.EPO.ORG(a)INTERNAL.EPO.ORG' 2013-11-22T13:24:07.949122+01:00 om03830s vsftpd: pam_krb5[12362]: krb5_get_init_creds_password(krbtgt/INTERNAL.EPO.ORG(a)INTERNAL.EPO.ORG) returned 0 (Success) 2013-11-22T13:24:07.949562+01:00 om03830s vsftpd: pam_krb5[12362]: validating credentials 2013-11-22T13:24:07.949758+01:00 om03830s vsftpd: pam_krb5[12362]: error reading keytab 'FILE:/etc/krb5.keytab' 2013-11-22T13:24:07.949992+01:00 om03830s vsftpd: pam_krb5[12362]: TGT verified 2013-11-22T13:24:07.950203+01:00 om03830s vsftpd: pam_krb5[12362]: got result 0 (Success) 2013-11-22T13:24:07.950382+01:00 om03830s vsftpd: pam_krb5[12370]: no need to create "/tmp" 2013-11-22T13:24:07.951620+01:00 om03830s vsftpd: pam_krb5[12370]: error creating ccache using pattern "FILE:/tmp/krb5cc_1000_XXXXXX" 2013-11-22T13:24:07.951838+01:00 om03830s vsftpd: pam_krb5[12370]: error creating ccache for user "om03830" 2013-11-22T13:24:07.951990+01:00 om03830s vsftpd: pam_krb5[12370]: krb5_kuserok() says "true" for ("om03830(a)INTERNAL.EPO.ORG","om03830") 2013-11-22T13:24:07.952119+01:00 om03830s vsftpd: pam_krb5[12362]: 'om03830(a)INTERNAL.EPO.ORG' passes .k5login check for 'om03830' 2013-11-22T13:24:07.952336+01:00 om03830s vsftpd: pam_krb5[12362]: authentication succeeds for 'om03830' (om03830(a)INTERNAL.EPO.ORG) 2013-11-22T13:24:07.952544+01:00 om03830s vsftpd: pam_krb5[12362]: pam_authenticate returning 0 (Success) 2013-11-22T13:24:07.952757+01:00 om03830s vsftpd: pam_krb5[12362]: flag: debug 2013-11-22T13:24:07.952957+01:00 om03830s vsftpd: pam_krb5[12362]: flag: don't always_allow_localname 2013-11-22T13:24:07.953215+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_afs 2013-11-22T13:24:07.953445+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no null_afs 2013-11-22T13:24:07.953724+01:00 om03830s vsftpd: pam_krb5[12362]: flag: cred_session 2013-11-22T13:24:07.953944+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_k5login 2013-11-22T13:24:07.954142+01:00 om03830s vsftpd: pam_krb5[12362]: flag: user_check 2013-11-22T13:24:07.954339+01:00 om03830s vsftpd: pam_krb5[12362]: will try previously set password first 2013-11-22T13:24:07.954539+01:00 om03830s vsftpd: pam_krb5[12362]: will let libkrb5 ask questions 2013-11-22T13:24:07.954744+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no use_shmem 2013-11-22T13:24:07.954978+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no external 2013-11-22T13:24:07.955394+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no multiple_ccaches 2013-11-22T13:24:07.955583+01:00 om03830s vsftpd: pam_krb5[12362]: flag: validate 2013-11-22T13:24:07.955759+01:00 om03830s vsftpd: pam_krb5[12362]: flag: warn 2013-11-22T13:24:07.955932+01:00 om03830s vsftpd: pam_krb5[12362]: minimum uid: 1 2013-11-22T13:24:07.956104+01:00 om03830s vsftpd: pam_krb5[12362]: banner: Kerberos 5 2013-11-22T13:24:07.956274+01:00 om03830s vsftpd: pam_krb5[12362]: ccache dir: /tmp 2013-11-22T13:24:07.956475+01:00 om03830s vsftpd: pam_krb5[12362]: ccname template: DIR:/run/user/%U/krb5cc_XXXXXX 2013-11-22T13:24:07.956720+01:00 om03830s vsftpd: pam_krb5[12362]: keytab: FILE:/etc/krb5.keytab 2013-11-22T13:24:07.956894+01:00 om03830s vsftpd: pam_krb5[12362]: token strategy: 2b,rxk5 2013-11-22T13:24:07.957064+01:00 om03830s vsftpd: pam_krb5[12362]: pam_acct_mgmt called for 'om03830', realm 'INTERNAL.EPO.ORG' 2013-11-22T13:24:07.957234+01:00 om03830s vsftpd: pam_krb5[12362]: account management succeeds for 'om03830' 2013-11-22T13:24:07.957408+01:00 om03830s vsftpd: pam_krb5[12372]: no need to create "/tmp" 2013-11-22T13:24:07.957520+01:00 om03830s vsftpd: pam_krb5[12372]: error creating ccache using pattern "FILE:/tmp/krb5cc_1000_XXXXXX" 2013-11-22T13:24:07.957653+01:00 om03830s vsftpd: pam_krb5[12372]: error creating ccache for user "om03830" 2013-11-22T13:24:07.957801+01:00 om03830s vsftpd: pam_krb5[12372]: krb5_kuserok() says "true" for ("om03830(a)INTERNAL.EPO.ORG","om03830") 2013-11-22T13:24:07.957905+01:00 om03830s vsftpd: pam_krb5[12362]: 'om03830(a)INTERNAL.EPO.ORG' passes .k5login check for 'om03830' 2013-11-22T13:24:07.958106+01:00 om03830s vsftpd: pam_krb5[12362]: pam_acct_mgmt returning 0 (Success) 2013-11-22T13:24:07.958279+01:00 om03830s vsftpd: pam_krb5[12362]: flag: debug 2013-11-22T13:24:07.958453+01:00 om03830s vsftpd: pam_krb5[12362]: flag: don't always_allow_localname 2013-11-22T13:24:07.958631+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_afs 2013-11-22T13:24:07.958804+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no null_afs 2013-11-22T13:24:07.959012+01:00 om03830s vsftpd: pam_krb5[12362]: flag: cred_session 2013-11-22T13:24:07.959190+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_k5login 2013-11-22T13:24:07.959363+01:00 om03830s vsftpd: pam_krb5[12362]: flag: user_check 2013-11-22T13:24:07.959539+01:00 om03830s vsftpd: pam_krb5[12362]: will try previously set password first 2013-11-22T13:24:07.959722+01:00 om03830s vsftpd: pam_krb5[12362]: will let libkrb5 ask questions 2013-11-22T13:24:07.959894+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no use_shmem 2013-11-22T13:24:07.960068+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no external 2013-11-22T13:24:07.960241+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no multiple_ccaches 2013-11-22T13:24:07.960437+01:00 om03830s vsftpd: pam_krb5[12362]: flag: validate 2013-11-22T13:24:07.960629+01:00 om03830s vsftpd: pam_krb5[12362]: flag: warn 2013-11-22T13:24:07.960802+01:00 om03830s vsftpd: pam_krb5[12362]: minimum uid: 1 2013-11-22T13:24:07.960973+01:00 om03830s vsftpd: pam_krb5[12362]: banner: Kerberos 5 2013-11-22T13:24:07.961148+01:00 om03830s vsftpd: pam_krb5[12362]: ccache dir: /tmp 2013-11-22T13:24:07.961320+01:00 om03830s vsftpd: pam_krb5[12362]: ccname template: DIR:/run/user/%U/krb5cc_XXXXXX 2013-11-22T13:24:07.961491+01:00 om03830s vsftpd: pam_krb5[12362]: keytab: FILE:/etc/krb5.keytab 2013-11-22T13:24:07.961668+01:00 om03830s vsftpd: pam_krb5[12362]: token strategy: 2b,rxk5 2013-11-22T13:24:07.961857+01:00 om03830s vsftpd: pam_krb5[12362]: pam_setcred (establish credential) called 2013-11-22T13:24:07.962042+01:00 om03830s vsftpd: pam_krb5[12362]: flag: debug 2013-11-22T13:24:07.962214+01:00 om03830s vsftpd: pam_krb5[12362]: flag: don't always_allow_localname 2013-11-22T13:24:07.962385+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_afs 2013-11-22T13:24:07.962561+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no null_afs 2013-11-22T13:24:07.962733+01:00 om03830s vsftpd: pam_krb5[12362]: flag: cred_session 2013-11-22T13:24:07.962905+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no ignore_k5login 2013-11-22T13:24:07.963075+01:00 om03830s vsftpd: pam_krb5[12362]: flag: user_check 2013-11-22T13:24:07.963271+01:00 om03830s vsftpd: pam_krb5[12362]: will try previously set password first 2013-11-22T13:24:07.963457+01:00 om03830s vsftpd: pam_krb5[12362]: will let libkrb5 ask questions 2013-11-22T13:24:07.963634+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no use_shmem 2013-11-22T13:24:07.963807+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no external 2013-11-22T13:24:07.963990+01:00 om03830s vsftpd: pam_krb5[12362]: flag: no multiple_ccaches 2013-11-22T13:24:07.964161+01:00 om03830s vsftpd: pam_krb5[12362]: flag: validate 2013-11-22T13:24:07.964346+01:00 om03830s vsftpd: pam_krb5[12362]: flag: warn 2013-11-22T13:24:07.964518+01:00 om03830s vsftpd: pam_krb5[12362]: minimum uid: 1 2013-11-22T13:24:07.964715+01:00 om03830s vsftpd: pam_krb5[12362]: banner: Kerberos 5 2013-11-22T13:24:07.964901+01:00 om03830s vsftpd: pam_krb5[12362]: ccache dir: /tmp 2013-11-22T13:24:07.965074+01:00 om03830s vsftpd: pam_krb5[12362]: ccname template: DIR:/run/user/%U/krb5cc_XXXXXX 2013-11-22T13:24:07.965245+01:00 om03830s vsftpd: pam_krb5[12362]: keytab: FILE:/etc/krb5.keytab 2013-11-22T13:24:07.965415+01:00 om03830s vsftpd: pam_krb5[12362]: token strategy: 2b,rxk5 2013-11-22T13:24:07.965594+01:00 om03830s vsftpd: pam_krb5[12362]: pam_open_session called for 'om03830', realm 'INTERNAL.EPO.ORG' 2013-11-22T13:24:07.965795+01:00 om03830s vsftpd: pam_krb5[12362]: creating ccache for 'om03830', uid=1000, gid=100 2013-11-22T13:24:07.965969+01:00 om03830s vsftpd: pam_krb5[12362]: no need to create "/run/user/1000" 2013-11-22T13:24:07.966163+01:00 om03830s vsftpd: pam_krb5[12362]: error creating ccache using pattern "DIR:/run/user/1000/krb5cc_XXXXXX" 2013-11-22T13:24:07.966348+01:00 om03830s vsftpd: pam_krb5[12362]: error creating ccache for user "om03830" 2013-11-22T13:24:07.966519+01:00 om03830s vsftpd: pam_krb5[12362]: pam_setcred(PAM_ESTABLISH_CRED) returning 14 (Cannot make/remove an entry for the specified session) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 854365] New: 13.1 systemd hangs in loop when trying to mount ntfs if Win8 is Hibernating
by bugzilla_noreply＠novell.com 18 Dec '13

18 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=854365 https://bugzilla.novell.com/show_bug.cgi?id=854365#c0 Summary: 13.1 systemd hangs in loop when trying to mount ntfs if Win8 is Hibernating 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: graymark(a)ptd.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 The Win8 on one of my laptops sometimes leaves its C: drive in a "hibernating state" (according to ntfs-ng). If sytemd tries to mount it during boot-up it will loop apparently trying to enter "emergency mode". The blankety-blank thing about the Win8 on this laptop is that it often leaves its C: drive in this state whether you reboot, or halt it (I've tried both ways this morning (several times) and it makes no difference to ntfs-ng or systemd -- it will loop without ever finishing the boot, or entering emergency mode. The only way out was to hold down the power-off button, boot a rescue disk, and remove the C: drive from /etc/fstab. Trying to mount the Win8 C: drive from a running 13.1 gives: Windows is hibernated, refused to mount. Failed to mount '/dev/sda4': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Reproducible: Always Steps to Reproduce: 1. Boot-up (my) Win8 to check for updates. 2. Tell Win8 to Restart or Halt 3. Boot up 13.1 Actual Results: systemd prints an error about failing to mount Win8's C: drive, then proceeds to loop trying to enter emergency mode but failing again, and again, and again .. Expected Results: openSUSE should have booted up, either ignoring the lack of a mounted Win8 C: drive or successfully entering emergency mode. HP and M$ have gotten really in your face obnoxious about not upgrading to 8.1 on the two Win8 laptops I own, and even prevented me from booting Win8 without doing so for awhile. (8.1 requires "joining" M$ store and then downloading 4GB worth of totally unnecessary software (I only use M$ Win8 to update my bios, and have absolutely no other use for it.) -- 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