April 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] The screen locker is broken and unlocking is not possible anymore.
by Per Jessen 03 Apr '16

03 Apr '16

My leap421 installation just told me $SUBJ. I guess some update wasn't quite tested. I have to say, I'm glad I'm not dependent on Leap to work all the time. -- Posted with knode 4.14 from openSUSE Leap42.1 office34: Cyrix 486DX2/66MHz, 4096Mb RAM, #9 GXE -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Running a vmware VM inside virtualbox
by jdd 02 Apr '16

02 Apr '16

Le 02/04/2016 20:00, Greg Freemyer a écrit : > This is a pretty large VM so running ovftool to export it as OVF format > is going to take a couple hours (or more), but it is in progress. > the rationale is that if the image have some internal problem, the command line tool have more chance to show them let us hope the ovf will work :-( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Running a vmware VM inside virtualbox
by Greg Freemyer 02 Apr '16

02 Apr '16

All, openSUSE 13.2 VirtualBox 4.3.36 (from the official opensuse repo) I have a VM that works in VMware, but I'd rather use virtualbox. I've read half a dozen sets of instructions (all relatively simple), but none work. This is what I get if I try to create a new VM and point at the VMDK file as the drive: === Failed to open the hard disk file /media/5BE6837001885F13/VMware Machines/IAC-Athena-DEMO-Early-Sept-2015/IAC-Athena-DEMO.vmdk. Could not get the storage format of the medium '/media/5BE6837001885F13/VMware Machines/IAC-Athena-DEMO-Early-Sept-2015/IAC-Athena-DEMO.vmdk' (VERR_NOT_SUPPORTED). Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: Medium Interface: IMedium {05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} Callee: IVirtualBox {fafa4e17-1ee2-4905-a10e-fe7c18bf5554} Callee RC: VBOX_E_OBJECT_NOT_FOUND (0x80BB0001) === Any idea what I need to do? fyi: I also installed the latest virtualbox on Windows and tried. I got a similar error. Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] adding apps to the menus
by david allan finch 01 Apr '16

01 Apr '16

Is there any documentation of how to add an application to the menus as part of a package install? (I have figured this out by looking at the files themselves in the system but would like to know if I made any mistakes) Also I am interested to know how to create a sub menu group for all the apps for my package? (all the examples I have followed in the distribution tree don't seam to work so I am missing something key here) Regards D -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] DC style logos for openSuse
by Anton Aylward 01 Apr '16

01 Apr '16

At the Toronto "Suse Day" yesterday there was a flash of a screen wallpaper that had the DC Comics superman style distorted pentagon, but in green with the suse lizard head in place of the stylized "S" with a greeninsh overall tint. I suppose that a green "S" would not be clearly "Suse" enough. But it made me think. There the "batsignal", the searchlight type projection ... but make that a green instead of black background and and the lizard head instead of the batwing. I did wonder about the Green lantern logo. The thing is that the current logos we have are really like that anyway. Any other ideas of adopting well known cultural visual icons? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] gparted, btrfs, and xfs
by Tom Kacvinsky 01 Apr '16

01 Apr '16

I made the fundamental mistake of not giving enough space to the / partition, and now I find I cannot install further updates because I am out of disk space. gparted was recommended to me, and I have taken the live ISO and “burned” it onto a USB memory stick. I’m having problems booting my laptop with it (endless cycle of “rebooting in 30s”), but I think I can get around that with the latest pre-release of the ISO. In any case, what I would like to do is think /home (on an XFS partition) and use the extra space to grow the / file systems (btrfs). IS this even possible. I did not find any documentation on who to do this, but that’s probably because my search terms were not refined enough. Any help would be appreciated. Thanks, TomN��r��y隊Z)z{.�ﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǿ� ޮ�^�ˬz��

15 100

[opensuse] [opensuse-factory] Conflicts to update R-core-libs
by Edwin Aponte 01 Apr '16

01 Apr '16

Hi, When I try to update R-core-libs on openSUSE TW, zypper finds the following conflicts: Checking for file conflicts: ...............................................................................................................................................................................[error] Detected 3 file conflicts: File /usr/lib64/R/lib/libR.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) File /usr/lib64/R/lib/libRblas.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) File /usr/lib64/R/lib/libRlapack.so from install of R-core-libs-3.2.4.1-33.6.x86_64 (R core components, supplements (like rkward), and CRAN packages (openSUSE_Tumbleweed)) conflicts with file from package R-base-libs-3.2.3-1.3.x86_64 (@System) ============ So these are basically conflicts between the updated package and the installed package. I am able to continue the update but this should not be regarded as conflict. I am able to update other packages without conflict. Could this be due to some misconfiguration on my system or a packaging error? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] My huawei ascend y221 only seen as mass storage after win xp in vbox has seen it.
by Dave Plater 01 Apr '16

01 Apr '16

Hi, I'm running Leap:42.1 Kde plasma5 and the device notifier only picks up my phone as mass storage after I've enabled and disabled the phone in a vbox win xp on my computer. If I connect as an mtp(media) device or a ptp(camera) it works fine. Here's a journalctl output when I go through this process : > Connect phone and select "turn on usb storage" on the phone. > > Mar 29 15:05:20 arbuthnot kernel: usb 2-1.3: new high-speed USB device number 7 using ehci-pci > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: New USB device found, idVendor=12d1, idProduct=2350 > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=4 > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: Product: HUAWEI Y221 PHONE > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: Manufacturer: MediaTek > Mar 29 15:05:21 arbuthnot kernel: usb 2-1.3: SerialNumber: RGTKVSZST46TIVWK > Mar 29 15:05:21 arbuthnot kernel: usb-storage 2-1.3:1.0: USB Mass Storage device detected > Mar 29 15:05:21 arbuthnot kernel: scsi host13: usb-storage 2-1.3:1.0 > Mar 29 15:05:21 arbuthnot mtp-probe[5665]: checking bus 2, device 7: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3" > Mar 29 15:05:21 arbuthnot mtp-probe[5665]: bus: 2, device: 7 was not an MTP device > Mar 29 15:05:21 arbuthnot usb_modeswitch[5689]: switch device 12d1:2350 on 002/007 > > Phone doesn't show in kde device notifier > Start vbox win xp and connect then disconnect phone in vbox > > Mar 29 15:06:33 arbuthnot kernel: vboxdrv: ffffffffa08c0020 VMMR0.r0 > Mar 29 15:06:33 arbuthnot kernel: vboxdrv: ffffffffa09ba020 VBoxDDR0.r0 > Mar 29 15:06:34 arbuthnot kernel: vboxdrv: ffffffffa0015020 VBoxDD2R0.r0 > Mar 29 15:06:34 arbuthnot kernel: vboxdrv: ffffffffa0029020 VBoxEhciR0.r0 > > On disconnecting the phone in vbox xp the phone is picked up and appears in device notifier. > sdg1 is the sd card and sdh is the phone > > > Mar 29 15:07:34 arbuthnot kernel: usb 2-1.3: reset high-speed USB device number 7 using ehci-pci > Mar 29 15:07:34 arbuthnot kernel: usb-storage 2-1.3:1.0: USB Mass Storage device detected > Mar 29 15:07:34 arbuthnot kernel: scsi host14: usb-storage 2-1.3:1.0 > Mar 29 15:07:35 arbuthnot kernel: scsi 14:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: Attached scsi generic sg8 type 0 > Mar 29 15:07:35 arbuthnot kernel: scsi 14:0:0:1: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: Attached scsi generic sg9 type 0 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] 7747584 512-byte logical blocks: (3.96 GB/3.69 GiB) > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Write Protect is off > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Mode Sense: 0f 00 00 00 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] 2235904 512-byte logical blocks: (1.14 GB/1.06 GiB) > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Write Protect is off > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Mode Sense: 0f 00 00 00 > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA > Mar 29 15:07:35 arbuthnot kernel: sdg: sdg1 > Mar 29 15:07:35 arbuthnot kernel: sdh: > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:0: [sdg] Attached SCSI removable disk > Mar 29 15:07:35 arbuthnot kernel: sd 14:0:0:1: [sdh] Attached SCSI removable disk > Mar 29 15:07:48 arbuthnot kernel: FAT-fs (sdg1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. > Mar 29 15:07:48 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/index.bdmv > Mar 29 15:07:48 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/BACKUP/index.bdmv > Mar 29 15:07:48 arbuthnot udisksd[1815]: Mounted /dev/sdg1 at /run/media/davepl/2A86-17E6 on behalf of uid 1000 > Mar 29 15:07:51 arbuthnot kernel: FAT-fs (sdh): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. > Mar 29 15:07:51 arbuthnot udisksd[1815]: Mounted /dev/sdh at /run/media/davepl/B4E0-0FE0 on behalf of uid 1000 > Mar 29 15:07:51 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/index.bdmv > Mar 29 15:07:51 arbuthnot org.gtk.Private.UDisks2VolumeMonitor[1752]: disc.c:332: error opening file BDMV/BACKUP/index.bdmv Can anyone shed any light on this problem? Thanks Dave P. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 12