February 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] vnc server on Tumbleweed
by Roger Oberholtzer 02 Feb '17

02 Feb '17

I am trying to connect to a vnc server on a Tumbleweed system. I have done this for many openSUSE releases on many systems, so I think I know the required steps. On the client, I run: vncviewer -passwd /home/roger/.vncpasswd 10.2.10.40:0 And I get this error: Connected to RFB server, using protocol version 3.8 Performing standard VNC authentication vncviewer: read: Connection reset by peer On the Tumbleweed server, I see this in /var/log/x11vnc.log: 02/02/2017 08:01:49 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 22296 02/02/2017 08:01:49 02/02/2017 08:01:49 wait_for_client: WAIT:cmd=FINDDISPLAY 02/02/2017 08:01:49 02/02/2017 08:01:49 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560 02/02/2017 08:01:49 02/02/2017 08:01:49 initialize_screen: -inetd mode: F_GETFL(stdin): 0x2 02/02/2017 08:01:49 initialize_screen: -inetd mode: F_GETFL(stdout): 0x2 02/02/2017 08:01:49 initialize_screen: -inetd mode and stdio is O_RDWR 02/02/2017 08:01:50 other clients: 02/02/2017 08:01:50 incr accepted_client=1 for 10.2.10.41:35914 sock=3 02/02/2017 08:01:50 Client Protocol Version 3.8 02/02/2017 08:01:50 Protocol version sent 3.8, using 3.8 02/02/2017 08:01:50 wait_for_client: got client 02/02/2017 08:01:50 client progressed=1 in 0/0 0.000000 s 02/02/2017 08:01:50 client useCopyRect: 10.2.10.41 0 02/02/2017 08:01:50 client_set_net: 10.2.10.41 0.0002 02/02/2017 08:01:50 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.yAvInj 02/02/2017 08:01:50 wait_for_client: find display cmd failed. 02/02/2017 08:01:50 wait_for_client: bad reply ' When I checked the error message, there were thoughts that I needed Xvfb installed. X is running on the remote. Anyway, I do not see Xvfb for Tumbleweed. And I'm not certain it is needed. I am starting vnc with xinetd, as I have always done. The xinitd description is the one I have always used: service x11vncservice { socket_type = stream protocol = tcp wait = no user = root server = /usr/bin/x11vnc server_args = -inetd -rfbauth /etc/vncpasswd -o /var/log/x11vnc.log -find -env FD_XDM=1 -shared -forever port = 5900 type = UNLISTED } /etc/vncpasswd was created with: x11vnc -storepasswd secret /etc/vncpasswd Should this work as it always has in the past? Or is something now different? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] rpm conflict, missing packages, on game repo: libSimGearCore.so.2016.2.1 & libgif.so.7
by Carlos E. R. 02 Feb '17

02 Feb '17

I get this conflict list: #### YaST2 conflicts list - generated 2017-02-02 01:30:54 #### nothing provides libSimGearCore.so.2016.2.1()(64bit) needed by fgrun-2016.1.1-1.4.x86_64 [ ] deinstallation of fgrun-2016.1.1-1.4.x86_64 [ ] break fgrun-2016.1.1-1.4.x86_64 by ignoring some of its dependencies nothing provides libgif.so.7()(64bit) needed by OpenSceneGraph-plugins-3.4.0-9.1.x86_64 [ ] deinstallation of OpenSceneGraph-plugins-3.4.0-9.1.x86_64 [ ] break OpenSceneGraph-plugins-3.4.0-9.1.x86_64 by ignoring some of its dependencies nothing provides libgif.so.7()(64bit) needed by OpenSceneGraph-plugins-3.4.0-9.1.x86_64 [ ] break OpenSceneGraph-plugins-3.4.0-9.1.x86_64 by ignoring some of its dependencies [ ] deinstallation of libSimGearCore-2016_2-2016.4.4-2.1.x86_64 nothing provides libgif.so.7()(64bit) needed by OpenSceneGraph-plugins-3.4.0-9.1.x86_64 [ ] break OpenSceneGraph-plugins-3.4.0-9.1.x86_64 by ignoring some of its dependencies [ ] deinstallation of FlightGear-2016.4.4-1.1.x86_64 nothing provides libgif.so.7()(64bit) needed by OpenSceneGraph-plugins-3.4.0-9.1.x86_64 [ ] break OpenSceneGraph-plugins-3.4.0-9.1.x86_64 by ignoring some of its dependencies [ ] deinstallation of FGx-2.10.0-2.4.x86_64 #### YaST2 conflicts list END ### Repo list: Telcontar:~ # zypper lr --details Repository priorities in effect: (See 'zypper lr -P' for details) 95 (raised priority) : 1 repository 99 (default priority) : 7 repositories 100 (lowered priority) : 2 repositories 105 (lowered priority) : 3 repositories 107 (lowered priority) : 2 repositories 109 (lowered priority) : 1 repository 111 (lowered priority) : 1 repository # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service ---+---------------------------------+-----------------------------------------+---------+-----------+---------+----------+----------+----------------------------------------------------------------------------------------+-------- 1 | EXT_Packman | EXT: Packman Repository | Yes | (r ) Yes | Yes | 95 | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_42.2/ | 2 | Local_RPMs | Local RPMs | Yes | ( p) Yes | Yes | 100 | plaindir | dir:///data/storage_c/repositorios_zypp/LocalRPMs | 3 | Local_RPMs_42.2 | Local RPMs 42.2 | Yes | ( p) Yes | Yes | 100 | plaindir | dir:///data/storage_c/repositorios_zypp/LocalRPMs_42.2 | 4 | OBSH_plater | OBSH plater | No | ---- | ---- | 115 | rpm-md | http://download.opensuse.org/repositories/home:/plater/Leap_42.2 | 5 | OBS_Emulators_Wine | OBS: Emulators: Wine | Yes | (r ) Yes | Yes | 109 | rpm-md | http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.… | 6 | OBS_Games | OBS: Games | Yes | (r ) Yes | Yes | 111 | rpm-md | http://download.opensuse.org/repositories/games/openSUSE_Leap_42.2/ | 7 | OBS_KDE3 | OBS: KDE:KDE3 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_42.2/ | 8 | OBS_devel_languages_pascal | OBS: devel: languages: pascal | No | ---- | ---- | 105 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/pascal/openSUSE… | 9 | OBS_devel_languages_perl | OBS: devel: languages: perl | Yes | (r ) Yes | Yes | 107 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_L… | 10 | OBS_graphics | OBS graphics | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/graphics/openSUSE_Leap_42.2/ | 11 | OBS_opensuse_Tools | OBS: opensuse: Tools | Yes | (r ) Yes | Yes | 105 | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tools/openSUSE_42.2/ | 12 | OBS_server_mail | OBS: server: mail | Yes | (r ) Yes | Yes | 107 | rpm-md | http://download.opensuse.org/repositories/server:/mail/openSUSE_Leap_42.2/ | 13 | OBS_utilities | OBS: Utilities | Yes | (r ) Yes | Yes | 105 | rpm-md | http://download.opensuse.org/repositories/utilities/openSUSE_Leap_42.2/ | 14 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.2 | 15 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ | 16 | download.opensuse.org-non-oss_1 | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/ | 17 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/oss/ | 18 | download.opensuse.org-oss_1 | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/oss | 19 | google-chrome | EXT: google-chrome | Yes | (r ) Yes | Yes | 105 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 | 20 | openSUSE-42.2-0 | openSUSE-42.2-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/usb-Verbatim_STORE_N_GO_1203001215022E28-0:0-part2 | 21 | repo-debug | openSUSE-Leap-42.2-Debug | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/debug/distribution/leap/42.2/repo/oss/ | 22 | repo-debug-non-oss | openSUSE-Leap-42.2-Debug-Non-Oss | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/debug/distribution/leap/42.2/repo/non-oss/ | 23 | repo-debug-update | openSUSE-Leap-42.2-Update-Debug | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/42.2/oss/ | 24 | repo-debug-update-non-oss | openSUSE-Leap-42.2-Update-Debug-Non-Oss | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/42.2/non-oss/ | 25 | repo-source | openSUSE-Leap-42.2-Source | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/ | 26 | repo-source-non-oss | openSUSE-Leap-42.2-Source-Non-Oss | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/source/distribution/leap/42.2/repo/non-oss/ | Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

1 0

[opensuse] Settings to have wifi up and running after boot
by Albert, Oszkó 01 Feb '17

01 Feb '17

Hi all, This is a long standing problem for me. Now I have an ASUS K501 UX laptop with Leap 42.2 and KDE. Tha laptop possibly does not matter, since this was the situation with 42.1 on this laptop and 42.1 on a Lenovo and on another kind of ASUS with 42.2. The symptoms: When I boot, wired connection gets initialized, and usable when I plug in the cord. I would expect that if and when the network cable is not plugged, the wifi starts working automatically. This is not the case and rfkill says wireless is hard blocked. I can only get wifi running if I put the system to sleep (with fn+Zz or mains switch), and then wake it up (with Esc or mains switch). Sometimes this should be done twice. There is another twist: boot+put to sleep + waking always works on one condition: the mains (or battery charger) is plugged. In this case closing the lid suspends the system and opening the lid wakes it up. When the charger is not plugged the above sequence sometimes works and sometimes (mostly) not. Closing the lid suspends the laptop, opening the lid either wakes it up or causes reboot. I do not know and understand how and why these phenomena are connected. What the charger plugged in state has to do with wifi start or reboot. It is mysterious why the things sometimes at least partly work and sometimes why not. And the basic question is: why the configured wifi does not start after or during bootup. Any kind of hints or tips are welcome. Regards, Albert

6 21

[opensuse] Leap 42.2 overwrote Archlinux mbr on /dev/sda on grub update for SuSE install on /dev/sdb
by David C. Rankin 01 Feb '17

01 Feb '17

SuSE Devs, I am Real Unhappy with fact that a 2nd update of grub2 on my laptop has overwritten the master boot record for the Archlinux install I had on /dev/sda when Leap is installed and boots from a completely separate drive (/dev/sdb). This is a follow-on post to a similar "Leap 42.2 overwrote Win10 mbr on /dev/sda on grub update for SuSE on /dev/sdb" Why can't grub keep its damn hands off disks that do NOT belong to it by default? Instead, it broke booting Arch by setting the incorrect initrd. The opensuse grub update set: initrd /intel-ucode.img causing a KERNEL PANIC on the next boot of Arch -- WTF? Well no wonder, the initrd for arch is: initrd /intel-ucode.img /initramfs-linux.img Why the hell are you touching the mbr on /dev/sda when the opensuse install is on /dev/sdb and boots EXCLUSIVELY from /dev/sdb without any chainload or syslinux call (my bios tells it to boot from the 2nd drive). What do we find in the new grub2 update? os-prober is run without any notice to the user on grub update (which is something that should ONLY RUN on distro INSTALL, not thereafter, and certainly NOT without express configuration *by the user* to initiate the chaos it is likely to cause depending on whether a USB device is also plugged in at the time of update. Now some misguided (but presumably well meaning) soul has included: GRUB_DISABLE_OS_PROBER="false" in /etc/default/grub guaranteeing that the havoc causing os-prober will run wild on each grub patch, update, or randomly triggered recompile by build service and start writing unwanted entries into grub.cfg and then for some bewildering reason writes the mbr to the wrong disk. (the GRUB_DISABLE_OS_PROBER entry was not present in /etc/default/grub before the update -- I have since changed it to "true") C'mon... You guys usually do such a good job, but this "Russian Roulette" grub update business has got to stop. An UPDATE of grub should NEVER write a bootloader to a device where one does not already exist. That is NOT an UPDATE of a bootloader -- that is a complete NEW INSTALL that should not be triggered on 'update'. Further, after the last update that thrashed the Win10 mbr, I expressly set grub_installdevice so that /dev/sda is NOT the grub_installdevice: # cat /etc/default/grub_installdevice /dev/sdb1 /dev/sdb activate generic_mbr However Leap still overwrote the mbr on /dev/sda ?? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] alternative to veromix plasmoid
by eddie 01 Feb '17

01 Feb '17

I am running Leap 42.2 but there are certain things that are not available so with great pain I have managed to get kde4 going. One of the main reasons for this is the veromix plasmoid which for those who don't know allows you to manage sound independently on different apps. For example, I can easily adjust the hdmi sound output to my TV while at the same time use a different setting for my media player on my pc. I can easily swap the output of my video player to the hdmi or pc depending on what device I feel in the mood to use to watch a video. Question. Is there an easy way (app. or plasmoid) that can do this type of thing on Leap42.2? In addition to this issue, the days of the week settings are "naff". In order to achieve my desired settings, I have to mix and match from various countries. I don't think that the person who thought that up was fully awake at the time. When I do this certain apps (or at least one app that I use fairly regularly) doesn't work. I think this has been an issue for others (possibly for other reasons) but is anyone giving any thought to this, to bring back some of the flexibility that existed in KDE4. It would be nice. Thanks Eddie -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] cannot delete a RAID drive
by george from the tribe 01 Feb '17

01 Feb '17

I am trying to free up a partition on my work desktop. One of the partitions on the extra disk is part of an old RAID-1 configuration, and I am trying to delete the raid drive from the system and re-format that partition. However, whenever I try to use fdisk, it re-activates the RAID even though I have already removed it. Here is my partition table: # fdisk -l /dev/sdb Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x12c2c333 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sdb2 206848 324458495 324251648 154.6G 7 HPFS/NTFS/exFAT /dev/sdb3 324458496 358275071 33816576 16.1G 82 Linux swap / Solaris /dev/sdb4 * 358275072 1953523711 1595248640 760.7G 5 Extended /dev/sdb5 358277120 419717119 61440000 29.3G 83 Linux /dev/sdb6 419719168 481159167 61440000 29.3G 83 Linux /dev/sdb7 481161216 1953523711 1472362496 702.1G 83 Linux The device in question is /dev/sdb5. Note how if I look at the mdstat file, it shows it is active. So I try to fail the drive, but it won't let me. Then I stop the raid drive and remove it, and it shows it is no longer there. Seems like it should work. facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb5[0] 30703616 blocks super 1.2 [2/1] [U_] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> facofficeeng02:/home/george # cat /etc/mdadm.conf ARRAY /dev/md/facofficeeng02:1 UUID=a8872a97:eecd6828:f759773c:cb18678e facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb5[0] 30703616 blocks super 1.2 [2/1] [U_] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> facofficeeng02:/home/george # mdadm --fail /dev/md0 /dev/sdb5 mdadm: set device faulty failed for /dev/sdb5: Device or resource busy facofficeeng02:/home/george # mdadm --stop /dev/md0 mdadm: stopped /dev/md0 facofficeeng02:/home/george # mdadm --remove /dev/md0 facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> However, then when I run fdisk again, just to try and mess with it, the array re-activates itself: acofficeeng02:/home/george # fdisk /dev/sdb Welcome to fdisk (util-linux 2.28). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): q facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb5[0] 30703616 blocks super 1.2 [2/1] [U_] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> I wanted to use fdisk to try and do something to that partition, but the array is reactivated as soon as I run fdisk. I tried gdisk for experiment (I can't use gdisk because the drive is mbr, not gpt), and it does the same thing. The drive re-activates itself. How do I completely get rid of my system seeing the raid in this partition and reactivating itself? I removed all the information from the /etc/mdadm.conf file for that drive, so it is not getting information from there. I am on a 42.2 system. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] TW: Plymouth boot-up screen blank-black
by ellanios82 01 Feb '17

01 Feb '17

TW: Plymouth boot-up screen blank-black - my preference is Text & NO Plymouth regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Leap 42.2 - why does wicked take 39 seconds to get a dhcp address?
by David C. Rankin 01 Feb '17

01 Feb '17

All, I use this same laptop with both Leap and Arch, wpa/wireless. With Arch/netctl the IP is established in 13 seconds. With Leap/wicked it consistently takes 39 seconds. Is there some way to speed up the network connection? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 24