April 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Trying and failing to save a video with avidemux - leap 15.1 Beta
by Carlos E. R. 21 Apr '19

21 Apr '19

I load a video, select codecs, and when I click on "save video" it saves a photo instead, as large as the original video. What? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Where can I find my stored Wifi-Passwords?
by Daniel Bauer 20 Apr '19

20 Apr '19

Hi everybody I use Opensuse 42.3, KDE 5.8.7 and connect to WiFis with Network-Manager. I want to connect to a WiFi from my mobile phone, but can't find the password. In network-Manager the password field has no "show password" checkbox. In KDE-Wallet I don't find any WiFi-entries. In the files in /etc/NetworkManager/system-connections/ there are no passwords... Where do they hide? Thanks! Daniel -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 26

[opensuse] How do I interpret this router advert?
by Carlos E. R. 17 Apr '19

17 Apr '19

Hi, I see entries like this in "iptraf": │ ICMPv6 router adv (72 bytes) from fe80::fa8e:85ff:fe64:78f2 to ff02::1 on eth0 │ Who is "ff02::1"? This machine or the router? linux-0o2k:~ # ping6 ff02::1 connect: Invalid argument linux-0o2k:~ # ping6 "ff02::1" connect: Invalid argument linux-0o2k:~ # linux-0o2k:~ # ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.134 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::221:85ff:fe16:2d0b prefixlen 64 scopeid 0x20<link> ether 00:21:85:16:2d:0b txqueuelen 1000 (Ethernet) RX packets 41190 bytes 39147997 (37.3 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 19592 bytes 1793875 (1.7 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 31

[opensuse] x11vnc service suddenly died on me :-(
by Marc Chamberlin 17 Apr '19

17 Apr '19

Hello - I am running OpenSuSE Leap 15.0, with the KDE desktop using sddm as the display manager, on a number of systems to which I need VNC access to the real display :0 at all times. (I cannot use VNC in a mode where it brings up a log in prompt, I need access to the running display. I leave these systems running 24/7 under my log in account. Most of these run in remote places, running unattended, so it is not easily possible for me to interact with them directly. ) Nor is it an option to change the KDE desktop since I am not the only person accessing these remote systems via VNC and interacting with them, and the other users are NOT sophisticated Linux users and need the GUI support provided by KDE. Up until what appears to have been a recent update, I have had this working by running x11vnc as a service, on the remote systems, with the following setup - > # cat /etc/systemd/system/x11vnc.service > [Unit] > Description=X11VNC Service > > [Service] > Type=simple > ExecStart=/usr/bin/x11vnc -auth /home/marc/.Xauthority -display :0 > -forever -loop -noxdamage -repeat -rfbauth /etc/vncpasswd -o > /var/log/x11vnc.log -rfbport 5900 -noipv6 -shared > ExecStop=/usr/bin/x11vnc -R stop > Restart=on-failure > RestartSec=2 > User=root > Group=root > > [Install] > WantedBy=multi-user.target I am not sure how to display the contents of the .Xauthority file here as it appears to contain binary data but this cut/paste shows a little bit - > bigbang:/home/marc # cat .Xauthority > > linux-0per0MIT-MAGIC-COOKIE-1��4#��T�o~�;��6 > linux-1een0MIT-MAGIC-COOKIE-1��lQ��!�� > linux-8kpg0MIT-MAGIC-COOKIE-1bv"��d\�̙��bigbang1MIT-MAGIC-COOKIE-1�à��RŘ��R� > linux-13qd0MIT-MAGIC-COOKIE-12�^��l��׋��'bigbang0MIT-MAGIC-COOKIE-1ǂ__z�e��!,�m� When I start the x11vnc service and then look at the x11vnc log file, I see something has gotten sick with connecting to DISPLAY :0 and the magic cookie stored in the .Xauthority file- > cat /var/log/x11vnc.log > 14/04/2019 07:34:23 passing arg to libvncserver: -rfbauth > 14/04/2019 07:34:23 passing arg to libvncserver: /etc/vncpasswd > 14/04/2019 07:34:23 passing arg to libvncserver: -rfbport > 14/04/2019 07:34:23 passing arg to libvncserver: 5900 > 14/04/2019 07:34:23 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 3672 > Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified > 14/04/2019 07:34:23 XOpenDisplay(":0") failed. > 14/04/2019 07:34:23 Trying again with XAUTHLOCALHOSTNAME=localhost ... > Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified > > 14/04/2019 07:34:23 *************************************** > 14/04/2019 07:34:23 *** XOpenDisplay failed (:0) > > *** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue. > *** There may be "Xlib:" error messages above with details about the > failure. > > Some tips and guidelines: I won't show all the tips and guidelines, but I think I am doing everything suggested... Any ideas why x11vnc suddenly broke? Thanks in advance... Marc... -- Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Boot after fresh install fails with "no such device //efi/boot/fallback.efi"
by Andrei Verovski 17 Apr '19

17 Apr '19

Hi ! Its seems there is a strange installer bug in both Leap 15.0 and latest Tumblweed snapshot. Installation pattern: Launch installer from DVD, go with default options Expert partitioner -> Start with current proposal (SuSE installer suggests its own partitioning scheme and GPT partition map) Delete all partitions except EFI boot and bios_boot (EFI boot and bios_boot added automatically by installer) Create /swap 8GB, / ext4 80GB and the rest /home ext4 Install First boot fails with "no such device //efi/boot/fallback.efi" PC is HP Intel i5 with EFI boot. I have another HD with Linux which boots just fine on same PC (with EFI boot). Legacy boot is disabled in BIOS. Secure boot is disabled in BIOS. SSD with fresh SuSE install is being left as single disk, no dual boot, only DVD-RW attached to another SATA port. Thanks in advance. Andrei -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] tumbleweed update from 20190403 to 20190409 qemu-kvm windows-xp guest did not start
by Simon Becherer 16 Apr '19

16 Apr '19

Hi, update tumbleweed from 20190403 to 20190409 try to start with virt-manager qemu-kvm windows xp professionel guest. was running without problems before, now windows did not boot, not in save mode. always falling back to the windows screen where i could choose save mode or start normal. what must i change that it will start again? thanks, simooN -- www.becherer.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 3

RE: [opensuse] zypper up: access denied error
by Hermann-Josef Beckers 16 Apr '19

16 Apr '19

-----Original Message----- From: Hermann-Josef Beckers Sent: Thursday, April 11, 2019 3:43 PM To: 'Per Jessen' <per(a)computer.org> Subject: RE: [opensuse] zypper up: access denied error > I went back to the "download.opensuse.org" repo entries and it works again. > Thanks for all replies. Wrote to early. Since switching to download.opensuse.org I get no updates. My actual "zypper lr --details" output pasted as: http://susepaste.org/12434989 http://paste.opensuse.org/12434989 A "zypper -v up" run is pasted as: http://susepaste.org/41262599 http://paste.opensuse.org/41262599 A lot (117) of packages wont be installed? Yours Hermann-Josef Beckers

3 9

[opensuse] Enter password to unlock your keyring?
by Istvan Gabor 15 Apr '19

15 Apr '19

Hello: I tried to set up VPN in networkmanager. When I tried to save the configuration a window titled "Unlock login keyring" appeared saying: "Enter password to unlock your login keyring. The login keyring did not get unlocked when you logged into your computer." I uploaded a screenshot of that widow here: http://i64.tinypic.com/der886.jpg (susepaste.org did not load) This window completely disabled writing text in any other window (terminal, document editor). I have no idea what login keyring is and what password the window expects. I worked with vpn clients (cisco vpnclient and shrew ike) previously but they run their system service daemons and I did not have to enter any extra passwords to make them work (only my vpn password). Can someone please enlighten my what this is all about, what login keyring is, what password that window asks for and how to avoid constant requests for extra passwords? A link to some good manual or documentation would be also helpful. Thank you in advance, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Flightgear causes removal of Nvidia driver.
by Carlos E. R. 15 Apr '19

15 Apr '19

#### YaST2 conflicts list - generated 2019-04-15 15:02:52 #### FlightGear-2017.3.1-lp150.1.8.x86_64 requires FlightGear-data = 2017.3.1, but this requirement cannot be provided not installable providers: FlightGear-data-2017.3.1-lp150.1.3.noarch[download.opensuse.org-oss] [ ] break FlightGear-2017.3.1-lp150.1.8.x86_64 by ignoring some of its dependencies [ ] do not install FlightGear-2017.3.1-lp150.1.8.x86_64 [ ] Following actions will be done: downgrade of FlightGear-data-2018.3.2-lp150.24.2.noarch to FlightGear-data-2017.3.1-lp150.1.3.noarch install FlightGear-data-2017.3.1-lp150.1.3.noarch (with vendor change) obs://build.opensuse.org/games --> openSUSE downgrade of FlightGear-docs-2018.3.2-lp150.24.2.noarch to FlightGear-docs-2017.3.1-lp150.1.3.noarch install FlightGear-docs-2017.3.1-lp150.1.3.noarch (with vendor change) obs://build.opensuse.org/games --> openSUSE deinstallation of nvidia-computeG03-340.107-lp151.12.2.x86_64 deinstallation of x11-video-nvidiaG03-340.107-lp151.12.2.x86_64 or: #### YaST2 conflicts list - generated 2019-04-15 15:06:16 #### FlightGear-2017.3.1-lp150.1.8.x86_64 requires libSimGearCore.so.2017.3.1()(64bit), but this requirement cannot be provided not installable providers: libSimGearCore-2017_3_1-2017.3.1-lp150.1.3.x86_64[download.opensuse.org-oss] [ ] Following actions will be done: deinstallation of nvidia-computeG03-340.107-lp151.12.2.x86_64 deinstallation of x11-video-nvidiaG03-340.107-lp151.12.2.x86_64 [ ] break FlightGear-2017.3.1-lp150.1.8.x86_64 by ignoring some of its dependencies [ ] do not install FlightGear-2017.3.1-lp150.1.8.x86_64 -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

1 0

[opensuse] Getting apcupsd to work
by James Knott 14 Apr '19

14 Apr '19

I just installed apcupsd and have connected an APC BE600M1 600VA UPS. I installed the apcupsd package, along with apcupsd cgi & gui. According to Yast Services Manager, apcupsd has failed. What am I missing to get this to work? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6