May 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] The Live CD iso report
by Larry Finger 29 May '12

29 May '12

Coolo, I can now report that the Gnome Live CD also builds and boots. Both KDE and Gnome both will boot from a USB stick written with imagewriter; however, both fail when booted using the iso with qemu-kvm. At the point of failure, /var/lob/kiwi.boot shows the following: =========================================================================== + echo /dev/ram1 + return + ramOnly=1 + '[' 1 = 1 ']' ++ cat /proc/meminfo ++ cut -f1 -dk ++ grep MemFree ++ cut -f2 -d: + haveKByte=' 405108 ' ++ expr 405108 / 1024 + haveMByte= ++ expr '*' 7 / 10 expr: syntax error + haveMByte= + clic_cmd='clicfs -m ' + '[' '!' -z '' ']' + '[' -z /livecd/openSUSE-12.1-livecd-gnome-read-only.x86_64-2.8.0 ']' + clicfs -m /livecd/openSUSE-12.1-livecd-gnome-read-only.x86_64-2.8.0 /read-only can't read from packfile : Is a directory read_pack: Invalid argument + Echo 'Failed to mount clic filesystem' + '[' 0 = 0 ']' + set +x + echo '[ 9.208387] Failed to mount clic filesystem' + '[' 0 = 0 ']' + set +x + return 1 + retval=1 + '[' no = no ']' + '[' '!' clean = fine ']' + '[' 1 = 0 ']' + resetMountCounter + local curtype=auto + local command + FSTYPE=auto + IFS=' ' + return 1 + systemException 'Failed to mount root filesystem' reboot + set +x + echo '[ 9.270200] Failed to mount root filesystem' =========================================================================== At first, I thought the differences might be that the USB boot had used the swap partition on the real disk; however, when I boot using a VirtualBox VM and the iso file, it works whether the attached vdi has a swap partition or not. The problem is not due to too little memory in the qemu-kvm VM. It fails with the "-m 512" option. I think that should be enough. The failure seems to start with a blank value for haveMByte. I have noticed a couple of small bugs with the KDE image. (1) When one does the media check, it asks for "any key" to continue. In fact, the key must be "Enter". (2) If one selects the "Boot from hard disk" option when using the USB stick, the system reboots from the stick. This situation may arise because the USB disk is first in the boot selection. It works correctly when running from the VB VM. In any case, the Live CDs are a lot closer to release than they have been for a while. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 8

[opensuse-factory] Speeding up SRs process to devel projects
by Togan Muftuoglu 29 May '12

29 May '12

Hi, I have made SR# 115787 to Publishing for dblatex which is a version update. However after almost a month it is still waiting for decision. As the beta is coming in soon I am not sure if this package if approved by the devel project will go to factory in a timely manner, but the real problem is I do not thing I am the only one in this situation, so the question what can be done in situations where the upstream ( in this case the devel project or the package maintainer) is lagging in the process of SR's Togan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 22

[opensuse-factory] Build disabled for devel packages [Publishing]?
by Kyrill Detinov 29 May '12

29 May '12

Hello. I found that some my devel packages are disabled for Factory in Publishing project. Who and why… ? And I see more disabled in Publishing: https://build.opensuse.org/project/monitor?arch_i586=1&defaults=0&disabled=… -- WBR Kyrill -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] build 383 use wrong branding
by Bruno Friedmann 29 May '12

29 May '12

The new 383 doesn't contain the new branding like previous build 381,382 Why ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] RPM 4.10 release
by Ilya Chernykh 29 May '12

29 May '12

RPM 4.10 release: will it get to 12.2? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 8

[opensuse-factory] More about the KDE Live CD
by Larry Finger 29 May '12

29 May '12

I rebuilt the KDE Live CD again today as a lot of packages were changed. It seems that the OBS is working better; however, the latest Live CD in Factory is still from May 20. The new CD boots up as openSUSE 12.2 Milestone 4. I have noticed a couple of other things. The initial boot screen no longer has an entry for direct installation. Is this intentional? The initial boot screen also lists 12.1, not 12.2. I still do not know my way around the build materials, or I would submit a patch. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] Boot failure with latest Live CD iso
by Larry Finger 28 May '12

28 May '12

Coolo, Good news. After 'osc update' this morning, the KDE Live CD builds once again, *and* it boots. Thus far, I have run only limited tests, but they include connecting to a WPA2-TKIP(AES)-encrypted AP. Networking appears to be fine. Are there any specific tests you would like me to run? Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Failure of Gnome Live CD Build on 5/27
by Larry Finger 28 May '12

28 May '12

The Gnome Live CD build fails today with the following: Reading installed packages... /usr/src/packages/BUILD/kiwi-image-livecd-gnome-12.1/tmp/screenrc.smart: line 12: 14028 Segmentation fault chroot "/usr/src/packages/BUILD/kiwi-image-livecd-gnome-12.1/tmp" zypper --non-interactive --no-gpg-checks --reposd-dir /var/cache/kiwi/zypper/repos --cache-dir /var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.12832 install --auto-agree-with-licenses --no-recommends aaa_base bootsplash-branding-openSUSE gfxboot-branding-openSUSE package-lists-openSUSE-GNOME-cd pam pam-config pam-modules patch tar udev yast2-live-installer zypper + ECODE=139 + echo 139 + exit 139 May-27 16:00:58 <1> : EXEC [rm -f /usr/src/packages/BUILD/kiwi-image-livecd-gnome-12.1/tmp/screenrc.smart*] May-27 16:00:59 <1> : EXEC [rm -f /usr/src/packages/BUILD/kiwi-image-livecd-gnome-12.1/tmp/screenrc.ctrls] failed May-27 16:00:59 <1> : Removing zypper service(s): home_rpmdir_rpms May-27 16:00:59 <1> : EXEC [chroot "/usr/src/packages/BUILD/kiwi-image-livecd-gnome-12.1/tmp" bash -c "zypper --non-interactive --no-gpg-checks --reposd-dir /var/cache/kiwi/zypper/repos --cache-dir /var/cache/kiwi/zypper --config /var/cache/kiwi/zypper/zypper.conf.12832 removerepo home_rpmdir_rpms 2>&1"] done May-27 16:00:59 <1> : Release package manager lock May-27 16:00:59 <1> : EXEC [rm -f /var/lock/kiwi-init.lock] May-27 16:00:59 <3> : Image installation failed failed May-27 16:00:59 <3> : KIWI exited with error(s) done May-27 16:00:59 <1> : Release package manager lock May-27 16:00:59 <1> : EXEC [rm -f /var/lock/kiwi-init.lock] Am I correct that "rm -f /usr/src/packages/BUILD/kiwi-image-livecd-gnome-12.1/tmp/screenrc.ctrls" failed? That command worked in a separate terminal. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 8

[opensuse-factory] Latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my NAS
by Daniel Bischof 28 May '12

28 May '12

Hi, the latest Tumbleweed kernel update 3.3.6 to 3.4.0 breaks cifs-mounting my NAS (used to work flawlessly with 3.3.6 and before). Accessing the NAS with smbclient still works. Bug? /etc/fstab excerpt --- //garcon/media /home/mediarw cifs nodfs,user,noauto,user=daniel,uid=daniel,gid=users,credentials=/home/daniel/.smbcredentials,iocharset=utf8,file_mode=0755,dir_mode=0755 0 0 --- verbose error messages in /var/log/messages --- May 24 18:36:39 kernel: [ 5128.053888] /[...]/linux-3.4/fs/cifs/cifsfs.c: Devname: //garcon/Volume_1/ flags: 0 May 24 18:36:39 kernel: [ 5128.053921] /[...]/linux-3.4/fs/cifs/connect.c: iocharset set to utf8 May 24 18:36:39 kernel: [ 5128.053940] /[...]/linux-3.4/fs/cifs/connect.c: Username: daniel May 24 18:36:39 kernel: [ 5128.053944] /[...]/linux-3.4/fs/cifs/connect.c: file mode: 0x1ed dir mode: 0x1ed May 24 18:36:39 kernel: [ 5128.054003] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 12 with uid: 0 May 24 18:36:39 kernel: [ 5128.054006] /[...]/linux-3.4/fs/cifs/connect.c: UNC: \\garcon\Volume_1 ip: 192.168.42.13 May 24 18:36:39 kernel: [ 5128.054020] /[...]/linux-3.4/fs/cifs/connect.c: Socket created May 24 18:36:39 kernel: [ 5128.054022] /[...]/linux-3.4/fs/cifs/connect.c: sndbuf 16384 rcvbuf 87380 rcvtimeo 0x1b58 May 24 18:36:39 kernel: [ 5128.054335] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_get_smb_ses as Xid: 13 with uid: 0 May 24 18:36:39 kernel: [ 5128.054347] /[...]/linux-3.4/fs/cifs/connect.c: Existing smb sess not found May 24 18:36:39 kernel: [ 5128.054367] /[...]/linux-3.4/fs/cifs/cifssmb.c: secFlags 0x7 May 24 18:36:39 kernel: [ 5128.054381] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 114 May 24 18:36:39 kernel: [ 5128.054389] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 82 May 24 18:36:39 kernel: [ 5128.054428] /[...]/linux-3.4/fs/cifs/connect.c: Demultiplex PID: 3264 May 24 18:36:39 kernel: [ 5128.067828] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x67 May 24 18:36:39 kernel: [ 5128.067854] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=114 mid=1 state=4 May 24 18:36:39 kernel: [ 5128.067861] /[...]/linux-3.4/fs/cifs/cifssmb.c: Dialect: 2 May 24 18:36:39 kernel: [ 5128.067864] /[...]/linux-3.4/fs/cifs/cifssmb.c: negprot rc 0 May 24 18:36:39 kernel: [ 5128.067867] /[...]/linux-3.4/fs/cifs/connect.c: Security Mode: 0x3 Capabilities: 0x80f3fd TimeAdjust: -3600 May 24 18:36:39 kernel: [ 5128.067870] /[...]/linux-3.4/fs/cifs/sess.c: sess setup type 1 May 24 18:36:39 kernel: [ 5128.067893] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 115 May 24 18:36:39 kernel: [ 5128.067895] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 244 May 24 18:36:39 kernel: [ 5128.081018] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x68 May 24 18:36:39 kernel: [ 5128.081081] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=115 mid=2 state=4 May 24 18:36:39 kernel: [ 5128.081093] /[...]/linux-3.4/fs/cifs/misc.c: Null buffer passed to cifs_small_buf_release May 24 18:36:39 kernel: [ 5128.081103] /[...]/linux-3.4/fs/cifs/sess.c: UID = 100 May 24 18:36:39 kernel: [ 5128.081110] /[...]/linux-3.4/fs/cifs/sess.c: bleft 62 May 24 18:36:39 kernel: [ 5128.081120] /[...]/linux-3.4/fs/cifs/sess.c: serverOS=Unix May 24 18:36:39 kernel: [ 5128.081128] /[...]/linux-3.4/fs/cifs/sess.c: serverNOS=Samba 3.0.24 May 24 18:36:39 kernel: [ 5128.081136] /[...]/linux-3.4/fs/cifs/sess.c: serverDomain=MYWORKGROUP May 24 18:36:39 kernel: [ 5128.081145] /[...]/linux-3.4/fs/cifs/sess.c: ssetup freeing small buf f2205e40 May 24 18:36:39 kernel: [ 5128.081153] /[...]/linux-3.4/fs/cifs/connect.c: CIFS Session Established successfully May 24 18:36:39 kernel: [ 5128.081162] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_smb_ses (xid = 13) rc = 0 May 24 18:36:39 kernel: [ 5128.081174] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_get_tcon as Xid: 14 with uid: 0 May 24 18:36:39 kernel: [ 5128.081186] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 117 May 24 18:36:39 kernel: [ 5128.081193] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 90 May 24 18:36:39 kernel: [ 5128.091411] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x36 May 24 18:36:39 kernel: [ 5128.091483] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=3 state=4 May 24 18:36:39 kernel: [ 5128.091498] /[...]/linux-3.4/fs/cifs/connect.c: disk share connection May 24 18:36:39 kernel: [ 5128.091509] /[...]/linux-3.4/fs/cifs/connect.c: nativeFileSystem=NTFS May 24 18:36:39 kernel: [ 5128.091516] /[...]/linux-3.4/fs/cifs/connect.c: Tcon flags: 0x3 May 24 18:36:39 kernel: [ 5128.091525] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_get_tcon (xid = 14) rc = 0 May 24 18:36:39 kernel: [ 5128.091532] /[...]/linux-3.4/fs/cifs/connect.c: CIFS Tcon rc = 0 May 24 18:36:39 kernel: [ 5128.091538] /[...]/linux-3.4/fs/cifs/connect.c: DFS disabled (1) May 24 18:36:39 kernel: [ 5128.091545] /[...]/linux-3.4/fs/cifs/cifssmb.c: In QFSDeviceInfo May 24 18:36:39 kernel: [ 5128.091555] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 50 May 24 18:36:39 kernel: [ 5128.091563] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 72 May 24 18:36:39 kernel: [ 5128.092535] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x40 May 24 18:36:39 kernel: [ 5128.092580] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=4 state=4 May 24 18:36:39 kernel: [ 5128.092596] /[...]/linux-3.4/fs/cifs/cifssmb.c: In QFSAttributeInfo May 24 18:36:39 kernel: [ 5128.092607] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 50 May 24 18:36:39 kernel: [ 5128.092614] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 72 May 24 18:36:39 kernel: [ 5128.093353] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x4c May 24 18:36:39 kernel: [ 5128.093389] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=5 state=4 May 24 18:36:39 kernel: [ 5128.093403] /[...]/linux-3.4/fs/cifs/connect.c: build_unc_path_to_root: full_path=\\garcon\Volume_1 May 24 18:36:39 kernel: [ 5128.093416] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 117 May 24 18:36:39 kernel: [ 5128.093423] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 96 May 24 18:36:39 kernel: [ 5128.094927] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x30 May 24 18:36:39 kernel: [ 5128.094998] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=117 mid=6 state=4 May 24 18:36:39 kernel: [ 5128.095015] /[...]/linux-3.4/fs/cifs/connect.c: CIFS Tcon rc = 0 ipc_tid = 2 May 24 18:36:39 kernel: [ 5128.095024] /[...]/linux-3.4/fs/cifs/cifssmb.c: In GetDFSRefer the path \garcon\Volume_1 May 24 18:36:39 kernel: [ 5128.095038] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 50 May 24 18:36:39 kernel: [ 5128.095046] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 108 May 24 18:36:39 kernel: [ 5128.096086] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0xc8 May 24 18:36:39 kernel: [ 5128.096132] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=50 mid=7 state=4 May 24 18:36:39 kernel: [ 5128.096149] /[...]/linux-3.4/fs/cifs/cifssmb.c: Decoding GetDFSRefer response BCC: 145 Offset 56 May 24 18:36:39 kernel: [ 5128.096166] /[...]/linux-3.4/fs/cifs/cifssmb.c: num_referrals: 1 dfs flags: 0x3 ... May 24 18:36:39 kernel: [ 5128.096205] /[...]/linux-3.4/fs/cifs/dns_resolve.c: dns_resolve_server_name_to_ip: resolved: garcon to 192.168.42.13 May 24 18:36:39 kernel: [ 5128.096319] /[...]/linux-3.4/fs/cifs/connect.c: iocharset set to utf8 May 24 18:36:39 kernel: [ 5128.096384] /[...]/linux-3.4/fs/cifs/connect.c: Username: daniel May 24 18:36:39 kernel: [ 5128.096393] /[...]/linux-3.4/fs/cifs/connect.c: cifs_put_tcon: tc_count=1 May 24 18:36:39 kernel: [ 5128.096403] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_put_tcon as Xid: 15 with uid: 0 May 24 18:36:39 kernel: [ 5128.096410] /[...]/linux-3.4/fs/cifs/cifssmb.c: In tree disconnect May 24 18:36:39 kernel: [ 5128.096421] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 113 May 24 18:36:39 kernel: [ 5128.096429] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 39 May 24 18:36:39 kernel: [ 5128.097409] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x23 May 24 18:36:39 kernel: [ 5128.097447] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=113 mid=8 state=4 May 24 18:36:39 kernel: [ 5128.097459] /[...]/linux-3.4/fs/cifs/connect.c: cifs_put_smb_ses: ses_count=1 May 24 18:36:39 kernel: [ 5128.097470] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_put_smb_ses as Xid: 16 with uid: 0 May 24 18:36:39 kernel: [ 5128.097478] /[...]/linux-3.4/fs/cifs/cifssmb.c: In SMBLogoff for session disconnect May 24 18:36:39 kernel: [ 5128.097486] /[...]/linux-3.4/fs/cifs/transport.c: For smb_command 116 May 24 18:36:39 kernel: [ 5128.097493] /[...]/linux-3.4/fs/cifs/transport.c: Sending smb: total_len 43 May 24 18:36:39 kernel: [ 5128.098346] /[...]/linux-3.4/fs/cifs/connect.c: RFC1002 header 0x27 May 24 18:36:39 kernel: [ 5128.098381] /[...]/linux-3.4/fs/cifs/transport.c: cifs_sync_mid_result: cmd=116 mid=9 state=4 May 24 18:36:39 kernel: [ 5128.098408] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 12) rc = 0 May 24 18:36:39 kernel: [ 5128.098418] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: in cifs_mount as Xid: 17 with uid: 0 May 24 18:36:39 kernel: [ 5128.098426] /[...]/linux-3.4/fs/cifs/connect.c: UNC: (null) ip: (null) May 24 18:36:39 kernel: [ 5128.098432] CIFS VFS: Connecting to DFS root not implemented yet May 24 18:36:39 kernel: [ 5128.098550] /[...]/linux-3.4/fs/cifs/connect.c: CIFS VFS: leaving cifs_mount (xid = 17) rc = -22 May 24 18:36:39 kernel: [ 5128.098559] CIFS VFS: cifs_mount failed w/return code = -22 --- Thanks, --D. -- Daniel Bischof <suse-bugz(a)bischof.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 11

[opensuse-factory] Kernel 3.4
by Moby 28 May '12

28 May '12

I had posted this on the regular oss discussions list but was told this might be a better forum. Just a word of caution in case anyone else is boldly tumbling through tumbleweed. I updated to kernel-default-3.4.0-x from the tumbleweed repository yesterday. The machines are primarily used as "nfs servers" and the nfs exports are mounted for use by vmware vSphere hosts. Today, there was massive disk corruption on all files being written to the nfs shares. Not sure if anyone else is seeing this but just something to keep in mind before using the Tumbleweed repo. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1