October 2015 - openSUSE Factory - openSUSE Mailing Lists

Re: [opensuse-factory] Has kernel-desktop been replaced by kernel-base?
by Dmitriy Perlow 13 Oct '15

13 Oct '15

Carlos E. R. <robin.listas(a)telefonica.net> Sun, 11 Oct 2015 20:09:27 +0300: > Anyway, I understood it is been replaced or merged with kernel-default. Both Leap 42 & Factory-Tumbleweed provide it, so it can be just forgotten not abandoned: https://build.opensuse.org/package/binaries/openSUSE:Leap:42.1/kernel-deskt… https://build.opensuse.org/package/binaries/openSUSE:Factory/kernel-desktop… -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 10

[opensuse-factory] libGraphicsMagick++-Q16-12
by Patrick Shanahan 13 Oct '15

13 Oct '15

Something amiss in Tw build: https://build.opensuse.org/package/binaries/openSUSE:Factory/GraphicsMagick… shows libGraphicsMagick++-Q16-12-1.3.22-1.1.x86_64 but http://download.opensuse.org/factory/repo/oss/suse/x86_64/ has libGraphicsMagick++-Q16-11-1.3.21-1.3.x86_64 and zypper complains: Problem: nothing provides libGraphicsMagick++-Q16.so.12 needed by photivo-1113rev66a8c1082d88-277.18.i586 Solution 1: keep obsolete photivo-1113rev66a8c1082d88-277.17.x86_64 Solution 2: break photivo-1113rev66a8c1082d88-277.18.i586 by ignoring some of its dependencies which is true as shown above. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- 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] maintainers needed for systemsmanagement:puppet
by Theo Chatzimichos 13 Oct '15

13 Oct '15

Hello, systemsmanagement:puppet needs new maintainers, as the current ones are slowly moving away from puppet. In case you are interested please contact me either by mail or in IRC (tampakrap on #opensuse-admin). If noone steps up in around a month, I plan to remove the packages from factory -- Theo Chatzimichos <tampakrap(a)opensuse.org> <tchatzimichos(a)suse.com> System Administrator SUSE Operations and Services Team

1 0

[opensuse-factory] Getting VMware Workstation to compile and run again on Tumbleweed using kernel-source-4.2.1
by James PEARSON 12 Oct '15

12 Oct '15

Hello all VMware has been working great but running "zypper dup" last night (the 5th of Oct) installed kernel 4.2.1-1. As a result I was no longer able to manually recompile the VMware Workstation "vmnet" module without errors: Ex. Error 1: No Internet connection Ex. Error 2: The status of the "Virtual ethernet" was "failed" Ex. Error 3: Virtual ethernet failed kernel-source-4.2.1 /usr/lib/vmware/modules/source/vmnet-only/bridge.o' failed For more info concerning the exact error messages when compiling, see "ORIGINAL ERROR MESSAGES" at the end of this email Note : Before the update I was on kernel 4.1.6-3.2 # my current installation of tumbleweed follows cat version Linux version 4.2.1-1-desktop (geeko@buildhost) (gcc version 5.1.1 20150713 [gcc-5-branch revision 225736] (SUSE Linux) ) #1 SMP PREEMPT Fri Sep 25 08:21:54 UTC 2015 (6996a42) # note : this was a fresh installation some 5 or 6 weeks ago # A list of the versions of installed support packages follows... kernel-source-4.2.1-1.2.noarch kernel-desktop-4.2.1-1.2.x86_64 kernel-desktop-devel-4.2.1-1.2.x86_64 gcc-5-1.24.x86_64 make-4.1-3.1.x86_64 gcc-c++-5-1.24.x86_64 # A list of the installed ***kernel*** packages... kernel-desktop-4.2.1-1.2.x86_64 kernel-desktop-devel-4.2.1-1.2.x86_64 kernel-devel-4.2.1-1.2.noarch kernel-macros-4.2.1-1.2.noarch kernel-source-4.2.1-1.2.noarch My notes on how to solve the problem and get VMware up and running again are below. The follwing works on VMware Workstatin e.x.p build-2882284 (the experential release before version 12) I believe that it will also work on version 11 # A few related sites that I found while googling today follow - https://communities.vmware.com/thread/516196 - http://rglinuxtech.com/?p=1528 # START ######################################################## # make working directory ######################################################## rm -r /tmp/vmware mkdir /tmp/vmware && cd /tmp/vmware # copy VMware source files cp -R /usr/lib/vmware/modules/source/ . cd /tmp/vmware/source for i in ./*.tar; do tar -xf $i; done for i in ./*.tar; do mv $i $i.orginal; done cd tmp/vmware/source/vmnet-only # ######################################################## # Modify vmnetInt.h ######################################################## cp ./vmnetInt.h vmnetInt.h.old vi vmnetInt.h # in vmnetInt.h, I found xtern struct proto vmnet_proto; #ifdef VMW_NETDEV_HAS_NET # define compat_sk_alloc(_bri, _pri) sk_alloc(&init_net, \ PF_NETLINK, _pri, &vmnet_proto) #else # define compat_sk_alloc(_bri, _pri) sk_alloc(PF_NETLINK, _pri, &vmnet_proto, 1) #endif # In vmnet-only/vmnetInt.h.. # Around line 79, the instructions state to change: #ifdef VMW_NETDEV_HAS_NET # define compat_sk_alloc(_bri, _pri) sk_alloc(&init_net, \ PF_NETLINK, _pri, &vmnet_proto,) #else # define compat_sk_alloc(_bri, _pri) sk_alloc(PF_NETLINK, _pri, &vmnet_proto, 1) #endif to: #ifdef VMW_NETDEV_HAS_NET #if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 2, 00) # define compat_sk_alloc(_bri, _pri) sk_alloc(&init_net, \ PF_NETLINK, _pri, &vmnet_proto, 1) #else # define compat_sk_alloc(_bri, _pri) sk_alloc(&init_net, \ PF_NETLINK, _pri, &vmnet_proto) #endif #else # define compat_sk_alloc(_bri, _pri) sk_alloc(PF_NETLINK, _pri, &vmnet_proto, 1) #endif # Now exit saving your changes and run make make cd .. ######################################################## # Results ######################################################## -rw-r--r-- 1 root root 3268 Oct 6 19:09 vmnetInt.h.old -rw-r--r-- 1 root root 3422 Oct 6 19:17 vmnetInt.h Sabertooth:/tmp/vmware/source/vmnet-only # make Using kernel build system. make -C /lib/modules/4.2.1-1-desktop/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= modules make[1]: Entering directory '/usr/src/linux-4.2.1-1-obj/x86_64/desktop' CC [M] /tmp/vmware/source/vmnet-only/driver.o CC [M] /tmp/vmware/source/vmnet-only/hub.o CC [M] /tmp/vmware/source/vmnet-only/userif.o CC [M] /tmp/vmware/source/vmnet-only/netif.o In file included from /usr/src/linux-4.2.1-1/include/linux/pci.h:35:0, from /tmp/vmware/source/vmnet-only/compat_netdevice.h:27, from /tmp/vmware/source/vmnet-only/netif.c:43: /usr/src/linux-4.2.1-1/include/linux/pci_ids.h:2253:0: warning: "PCI_VENDOR_ID_VMWARE" redefined #define PCI_VENDOR_ID_VMWARE 0x15ad ^ In file included from /tmp/vmware/source/vmnet-only/net.h:38:0, from /tmp/vmware/source/vmnet-only/vnetInt.h:26, from /tmp/vmware/source/vmnet-only/netif.c:42: /tmp/vmware/source/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition #define PCI_VENDOR_ID_VMWARE 0x15AD ^ CC [M] /tmp/vmware/source/vmnet-only/bridge.o In file included from /tmp/vmware/source/vmnet-only/net.h:38:0, from /tmp/vmware/source/vmnet-only/vnetInt.h:26, from /tmp/vmware/source/vmnet-only/bridge.c:52: /tmp/vmware/source/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined #define PCI_VENDOR_ID_VMWARE 0x15AD ^ In file included from /usr/src/linux-4.2.1-1/include/linux/pci.h:35:0, from /tmp/vmware/source/vmnet-only/compat_netdevice.h:27, from /tmp/vmware/source/vmnet-only/bridge.c:51: /usr/src/linux-4.2.1-1/include/linux/pci_ids.h:2253:0: note: this is the location of the previous definition #define PCI_VENDOR_ID_VMWARE 0x15ad ^ CC [M] /tmp/vmware/source/vmnet-only/procfs.o CC [M] /tmp/vmware/source/vmnet-only/smac_compat.o CC [M] /tmp/vmware/source/vmnet-only/smac.o CC [M] /tmp/vmware/source/vmnet-only/vnetEvent.o CC [M] /tmp/vmware/source/vmnet-only/vnetUserListener.o LD [M] /tmp/vmware/source/vmnet-only/vmnet.o Building modules, stage 2. MODPOST 1 modules CC /tmp/vmware/source/vmnet-only/vmnet.mod.o LD [M] /tmp/vmware/source/vmnet-only/vmnet.ko make[1]: Leaving directory '/usr/src/linux-4.2.1-1-obj/x86_64/desktop' make -C $PWD SRCROOT=$PWD/. \ MODULEBUILDDIR= postbuild make[1]: Entering directory '/tmp/vmware/source/vmnet-only' make[1]: 'postbuild' is up to date. make[1]: Leaving directory '/tmp/vmware/source/vmnet-only' cp -f vmnet.ko ./../vmnet.o ######################################################## # Control if the vmnet.o module was just compiled ######################################################## Sabertooth:/tmp/vmware/source # ls -trl total 9716 drwxr-xr-x 8 root root 440 Jul 9 00:47 vmmon-only drwxr-xr-x 4 root root 160 Jul 9 00:47 vsock-only drwxr-xr-x 5 root root 180 Jul 9 00:47 vmci-only -rw-r--r-- 1 root root 839680 Oct 6 18:40 vmblock.tar.orginal -rw-r--r-- 1 root root 1310720 Oct 6 18:40 vmmon.tar.orginal -rw-r--r-- 1 root root 880640 Oct 6 18:40 vmnet.tar.orginal -rw-r--r-- 1 root root 1095680 Oct 6 18:40 vsock.tar.orginal -rw-r--r-- 1 root root 1300480 Oct 6 18:40 vmci.tar.orginal -rw-r--r-- 1 root root 2026304 Oct 6 18:40 vmmon.o drwxr-xr-x 4 root root 180 Oct 6 18:48 vmblock-only drwxr-xr-x 3 root root 1720 Oct 6 19:18 vmnet-only -rw-r--r-- 1 root root 2490120 Oct 6 19:18 vmnet.o Sabertooth:/tmp/vmware/source # ######################################################## # Copy the vmnet module to proper openSUSE directory ######################################################## ls vmnet.o echo "Copying the vmnet module to /lib/modules/`uname -r`/kernel/drivers/misc/... " cp ./vmnet.o /lib/modules/`uname -r`/kernel/drivers/misc/vmnet.ko ######################################################## # Load modules and bounce VMware ######################################################## Sabertooth:/tmp/vmware/source # depmod -a Sabertooth:/tmp/vmware/source # # Sabertooth:/tmp/vmware/source # echo "Restarting vmware... " Restarting vmware... Sabertooth:/tmp/vmware/source # /etc/init.d/vmware restart Stopping VMware services: VMware Authentication Daemon done VM communication interface socket family done Virtual machine communication interface done Virtual machine monitor done Blocking file system done Starting VMware services: Virtual machine monitor done Virtual machine communication interface done VM communication interface socket family done Blocking file system done Virtual ethernet done # ********* everything is now OK VMware Authentication Daemon done Shared Memory Available done # END ######################################################## # ORIGINAL ERROR MESSAGES ######################################################## In file included from /usr/lib/vmware/modules/source/vmnet-only/bridge.c:50:0: /usr/lib/vmware/modules/source/vmnet-only/bridge.c: In function ‘VNetBridgeUp’: /usr/lib/vmware/modules/source/vmnet-only/vmnetInt.h:81:40: error: too few arguments to function ‘sk_alloc’ # define compat_sk_alloc(_bri, _pri) sk_alloc(&init_net, \ ^ /usr/lib/vmware/modules/source/vmnet-only/bridge.c:952:17: note: in expansion of macro ‘compat_sk_alloc’ bridge->sk = compat_sk_alloc(bridge, GFP_ATOMIC); ^ In file included from /usr/lib/vmware/modules/source/vmnet-only/compat_sock.h:23:0, from /usr/lib/vmware/modules/source/vmnet-only/bridge.c:35: /usr/src/linux-4.2.1-1/include/net/sock.h:1515:14: note: declared here struct sock *sk_alloc(struct net *net, int family, gfp_t priority, ^ /usr/src/linux-4.2.1-1/scripts/Makefile.build:274: recipe for target '/usr/lib/vmware/modules/source/vmnet-only/bridge.o' failed make[4]: *** [/usr/lib/vmware/modules/source/vmnet-only/bridge.o] Error 1 /usr/src/linux-4.2.1-1/Makefile:1412: recipe for target '_module_/usr/lib/vmware/modules/source/vmnet-only' failed make[3]: *** [_module_/usr/lib/vmware/modules/source/vmnet-only] Error 2 Makefile:146: recipe for target 'sub-make' failed make[2]: *** [sub-make] Error 2 Makefile:24: recipe for target '__sub-make' failed Hope this helps someone ! Regards James -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 5

[opensuse-factory] Tumbleweed: how to "enable" (run at boot) postgresql 9.4.4 service.. [GPG signed]
by André Verwijs 12 Oct '15

12 Oct '15

Tumbleweed: how to "enable" (run at boot) PostgrwSQL 9.4.4 service when i run.... OpenSUSE-TW:~ # systemctl enable postgresql.service postgresql.service is not a native service, redirecting to systemd-sysv-install Executing /usr/lib/systemd/systemd-sysv-install enable postgresql Failed to execute /usr/lib/systemd/systemd-sysv-install: No such file or directory when i start postgresql, it works great..... OpenSUSE-TW:~ # service postgresql start OpenSUSE-TW:~ # systemctl status postgresql.service postgresql.service - LSB: Start the PostgreSQL master daemon Loaded: loaded (/etc/init.d/postgresql) Active: active (exited) since Sun 2015-10-11 09:49:08 CEST; 2s ago Docs: man:systemd-sysv-generator(8) Process: 3781 ExecStart=/etc/init.d/postgresql start (code=exited, status=0/SUCCESS) Oct 11 09:49:07 OpenSUSE-TW systemd[1]: Starting LSB: Start the PostgreSQL master daemon... Oct 11 09:49:07 OpenSUSE-TW su[3793]: (to postgres) root on none Oct 11 09:49:07 OpenSUSE-TW su[3793]: pam_unix(su-l:session): session opened for user postgres by (uid=0) Oct 11 09:49:07 OpenSUSE-TW su[3831]: (to postgres) root on none Oct 11 09:49:07 OpenSUSE-TW su[3831]: pam_unix(su-l:session): sessionopened for user postgres by (uid=0) Oct 11 09:49:08 OpenSUSE-TW systemd[1]: Started LSB: Start the PostgreSQL master daemon. Oct 11 09:49:08 OpenSUSE-TW postgresql[3781]: Starting PostgreSQL 9.4.4 ..done for other services there's no problem, so why postgresql can't be added/activated, i don't know.... tips are welcome... André

2 1

[opensuse-factory] [Leap 42.1] IceWM is default login DE after install
by Uzair Shamim 12 Oct '15

12 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, I just downloaded and installed Leap Build 0222, and even though I selected KDE as my DE in the installer, I was given IceWM as my default login DE when I first boot in. For me it was obvious what the issue was but this may be confusing for some new users who are not familiar with multiple DE's on their system. Is this intentional or could it be "fixed"? - -- Regards, Uzair Shamim -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJWGUXvAAoJEKk4ocK8JbkdyRoQAJHjYj5ZS137vrK1W2CxgFAT aUjuFrG76rY/FAZSfeGlZFxFCA5VNWiQ6ihaugFinn2GKz/WnMKVM18IqldsTRsB mmA6ITSXUGncFvRxx9IkyPT5OSX9dubdCtlR8grPpZY6A9ywYuQW+Xo3YqHAEG05 0ctTa9+wJYsTVgWUv5PxnAzc41JdUmI7woAXwAXBxsV1hTV1bYwC+IQwf5sKm4Kz uxiVh10YvNZFtJfRQO8HyNd5H96xR9gcbhaon5mazH8uinSzOf3H3o7NWx43FpQr KmEGgsNwmXZivMV06z24O0HE6PHprqADvjy2MqZDBHcpYasO3o2VQSg3GL3QTVFD 2wAo/JKPs0uj9X8l6NqmenkhyM7Y+0cQCzHK5Ln4d2qFBLDXsoywBhICNmutABEG MXFvsyXDJ+tlHX3TPAZRV83R8aOVWeqlS6W4tGtDmafUIt8g26lV3OCjo+1azf0A KMyrWpkinsIMyUEg8S09wpz6P/j78TOWClbXDf0LohxVZONf2BTG93p/eVwSyKFv M3C7ABRtB+skWXkjn8WEFX0w6EZ5tLSBMO5sVOzFB0eU2Gq115Vq66qkexPW5p1d TjN9/YJMznTHMBk7JopnC1024V7TsvW8VB1+gJXulRTRZ3FPYedzfVXSrVSbsljj qXlbtSAgNueS6W79iCOo =B/Wd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 16

[opensuse-factory] Has kernel-desktop been replaced by kernel-base?
by Roman Bysh 11 Oct '15

11 Oct '15

Hi all, After perusing the kernel repositories. I've noticed that openSUSE 13.2 is the last distro using kernel-desktop. Is it being replaced with kernel-base? -- Cheers! Roman -- 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] i/o error on sdb shown in strg+alt+f10
by Thomas Langkamp 11 Oct '15

11 Oct '15

Hi, since about 2 weeks I have random crashes of different apps on one of my Tumbleweed machines. Strg+Alt+F10 shows i/o errors on /dev/sdb after such an app crash. sdb is an SSD where root and home lived happily together for the past 4 years. Could this mean that my SSD dies? And where is the output of Strg+Alt+F10 stored? I can´t find the i/o error messages in /var/log/messages, dmesg, xsession-errors or boot.log. Are there other important log-files I missed? Which diag program do you use to check your SSD with mounted root? Or is someone else seeing such errors, thus might it be a TW bug? Thank you. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 8

[opensuse-factory] Systemd error at boot.
by Steven Hess 10 Oct '15

10 Oct '15

I'm running up to date Tumbleweed in VMWare Fusion on a Mac Mini with EXT4 partitions and a Native Tumbleweed install on a HP Intel box with EXT4 partitions. When I boot I get this error: "Systemd-fstab-generator [61] Failed to create unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab? The error repeats one more time. This happens on both computers. The system boots and run normally. What is this error? How can I get rid of it? Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND openSUSE Linux 13.1 KDE, Tumbleweed KDE with Packman Known as FlameBait and The Sock Puppet of Doom. -- 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] Multiboot - shared /home w/separate Gnome version extensions possible?
by Terje J. Hanssen 10 Oct '15

10 Oct '15

Hi List, Now we have 13.2/Gome 3.14, Leap 42.1/Gnome 3.16 and soon Tumbleweed/Gnome 3.18 using Gnome DE. For ease and practical use (and disk space save) I prefere to use shared /home for multiboot installations with different roots. The only drawback I experience is that different Gnome versions has incompatible Gnome extensions. I.e to get my preferred environment setup while using Leap 42.1, I have to remove the incompatible Gnome 3.14 extensions installed and reinstall extensions for 3.16 and so on. Therefore I wonder if it would be possible to use different Gnome extensions installed 'in parallell' or separated, so that the current Gnome version in use automatical use the righ extension version? That would make testing and transitons between real installations more streamlined. Thanks, Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 3