June 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Cutting video files in half
by Constant Brouerius van Nidek 07 Jul '17

07 Jul '17

First of all, I am not trying to find a video editor. I just want to cut video files in half in order to send them to a family member oversees. Thanks to the help of list members and ongoing discussions about video editors I have read multiple man pages etc. googled around and have seen to it that i have multiple editors installed. I have chosen WeTransfer for the transport which only allows a maximum of 2 gigabyte per session. The video files are all approximately 4 gigabyte and I need a simple method to cut these MOV files in half. Looking at video editors in alphabetical order Avidemux, ffmpeg, kdenlive and Openshot I am just looking for a program that just cuts the 4Gb videos in half. ffmpeg seems the most logical candidate but finding the right command line sequence is problematic. Could somebody give me just the lines that work? -- opensuse:tumbleweed:20170613 Qt: 5.9.0 KDE Frameworks: 5.34.0 kf5-config: 1.0 KDE Plasma: 5.10.1 plasmashell 5.10.1 Kernel: 4.11.4-1-default Linux User 183145 working on a Pentium IV . -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 7

[opensuse] How to enable raid 1 in LEap 42.2?
by Istvan Gabor 04 Jul '17

04 Jul '17

Hello: I have installed openSUSE Leap 42.2 on a standalone hard disk. Then I connected to the system 2 other hard disks which have several raid 1 (mirror) arrays. When I boot Leap 42.2 it doesn't activate the raid arrays. How can I enable raid (mdraid) in Leap 42.2? In yast services manager I see mdadm-grow-continue@, mdadm-last-resort@, mdmon@, mdmonitor services, all of which are in disabled/inactive state. I don't know what they are for and which one I should enable (if any of them at all). Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 25

[opensuse] Scroll Lock LED not mapped
by Paul Groves 04 Jul '17

04 Jul '17

Hi Similar to my keys not being mapped (but oh so different). (The LED isn't broken because it works in Windows) so I assume that LED is using a different scancode to the standard one? Any one know how to re-map the LED? Num Lock and Caps Lock LEDs work fine. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 22

[opensuse] network manager system default setup
by Istvan Gabor 02 Jul '17

02 Jul '17

Hello: I noticed that network-manager configured networks are different for different users. I would like to make a default system setup and I want that network-manager offers every user the same choices. I would like to setup some default connections as admin. All users should see the same default connections, able to start and stop those connections but not able to modify the connections (add new connection or remove connection). (That is, I would like to imitate the previous smpppd/kinternet/ifup combo behavior with nm.) How to do this in Leap 42.2? Does it matter which nm-applet is run (kde or gtk)? Links to good network manager manuals or howtos are also welcomed. Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] Are many 42.2 related (not 'official') repositories often out of sync with each other?
by Carl Hartung 30 Jun '17

30 Jun '17

Hi All, I'm prepping a fallback Leap 42.2 system to substitute for my daily workhorse during it's 'vacation' in the shop for a warranty repair. I thought this process was going to be relatively straightforward, but I keep running into an astonishing number of inconsistencies like the examples excerpted below. (I have triple checked and both systems are definitely configured to use the same repositories): < abiword-3.0.1-1.14.x86_64 < abiword-docs-3.0.1-1.1.noarch --- > abiword-3.0.1-54.3.x86_64 > abiword-docs-3.0.1-31.2.noarch < dia-0.97.3-65.2.x86_64 < dia-lang-0.97.3-65.2.noarch --- > dia-0.97.3-3.35.x86_64 > dia-lang-0.97.3-3.35.noarch 'zypper if epson-inkjet-printer-escpr' yields the following on one machine: Repository : @System Name : epson-inkjet-printer-escpr Version : 1.6.13-1lsb3.2 Arch : x86_64 Vendor : Seiko Epson Corporation ... and this on the other: Repository : @System Name : epson-inkjet-printer-escpr Version : 1.6.4-1lsb3.2 Arch : x86_64 Vendor : Seiko Epson Corporation ... Also, these inconsistencies aside (presuming this issue is going to be solved,) does anyone have a proven fast and reliable way to replicate an installed system on a parallel box without transplanting or imaging drives or attempting something like rsync? These systems are not much like each other from a hardware perspective, but I need the software that's installed on them to be the same. All constructive comments and ideas will be appreciated and are welcome! Thx! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 18

[opensuse] Epson Scanner V500 Isn't Detected
by Mark Misulich 29 Jun '17

29 Jun '17

Hi, I installed Opensuse 42.2 on a computer that I finished building the other day. I am using KDE 5.8.6-7.1 as the desktop environment. I am trying to install an Epson Perfection V500 Photo Scanner that I have used for maybe 7 years on my previous desktop computer using various Opensuse versions starting with 12.something up to 42.2, with the Epson iscan installation software for this scanner. The version of this software is iscan-bundle-1.0.4.x64.rpm But the scanner won't install on this computer using yast; here's the details. In yast in the Scanner Configuration window, it shows the following: Driver Scanner epkowa No scanner recognized by this driver Not Configured Epson Scanner USB scanner (vendor=0x04b8 [EPSON Scanner] at libusb:001:015 epkowa is the driver I use for this scanner, and is supplied by the iscan driver bundle. It has always recognized the scanner in the past. I downloaded the latest version of the iscan driver bundle from Epson and it installs all the required software to run the scanner using a shell script. If I try to configure the scanner using Yast2, it autoselects Epson Perfection V500 Photo in the Scanner Models dialog box. I then click "Next," and a dialog box informs me "Possibly Problematic Driver The epkowa driver may cause problems on 64-bit x86_64 architecture. Selecting "Continue," Yast does it's thing, and promptly brings me back to the Scanner Configuration window with the same results as I have shown above. What I've tried: 1. Multiple tries of reinstalling the driver software via the shell script. 2. Regressing to earlier versions of the driver software. 3. Trying the 32-bit architecture driver software . 4. Moving the USB cable on the computer from USB3 to USB2 ports 5. Disconnecting the Scanner USB cable from the USB Hub and connecting it directly to the back of the computer, using both the USB3 and USB2 ports. In all cases, the scanner is not recognized. As a final note, yes, the scanner power is on. I would appreciate some help to get the scanner working. Thanks, Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 22

[opensuse] ubuntu reports probs w/new sysd DNS service...is this going to hit openSUSE?
by L A Walsh 29 Jun '17

29 Jun '17

Warning! This could be alot of "nonsense" and be a potentially reactive topic. Please don't escalate things emotionally or no one will ever understand what the facts are. That said, I see some trends/repeated behavior+history consistent with sysd's expansion into other OS functions, so I see no reason to completely disbelieve some of the statements I've read or try to summarize below. Does anyone know what's happening in OpenSUSE related to this? Will it be generating the same types of instability and problems? Will opensuse still support other DNS resolvers (bind/named, dnsmasq, etc) even if they are incompatible with new sysd operation? /There is a sysxxxd vulnerability <https://www.ubuntu.com/usn/usn-3341-1/> in the latest ubuntu distributions due to sysxxxd's new DNS resolver. The inclusion of the dns resolver was lamented by many on the mailing list <https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html>, not without cause. All are advised to update their distribution./ New features include(**) -taking over glibc library functions gethostbyname & getaddrinfo in nsswitch to redirect dns calls into sysd's version -changes /etc/resolv.conf creating race conditions with various SW packages. leading to inconsistent address resolution - turns DNS requests into XML requests fed over the sysdbus for requests and answers, duplicating DNS protocol handling code requiring sysd to keep up with DNS changes. - does forwarding-only & relies on DHCP for a full DNS server stripping off DNS security records in the process so sysd-local changes can't be detected by local applications. - scans for its own group of DNS servers on all interfaces and sends out DNS queries on all ports using "first-received" answers vs. authoritative answers (including ones w/NXDOMAIN), allowing easy propagation of poisoned DNS info. - believed not to handle split DNS schemes needed for VPN setups to work correctly. (**- https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html) Apparently sysd's DNS changes haven't gone over well in terms of interoperability w/existing DNS -- a persistent theme as sysd takes on a new system function/area. _I_ have more than a little anxiety over the idea that all alternate DNS solutions will be thrown out.. comments? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] Services not started after update/reboot
by Peter Suetterlin 29 Jun '17

29 Jun '17

Hi List, Last night I updated our server (Mail, Homedirs etc.). It is running Leap 42.2. The ones I did so far went smooth: Zypper up, then reboot. Not this time: The system rebooted fine, but all client machines were dead because they didn't get the NFS directories: systemd had decided to not start nfs-server, although it is enabled :o So it's not that it tried to start and failed with an error. The first mention of it in the logs was when I manually started it. This morning I found out that the same had happened to postfix: enabled, but not started during reboot. Has anyone seen a similar issue lately, or has some suggestions how to find out why that happened? Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin(a)royac.iac.es +46 8 5537 8559 (Sweden) Peter.Suetterlin(a)astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] test
by André Verwijs 29 Jun '17

29 Jun '17

test -- ______________________________________________________________________________________ JAV-logo-met-naam <http://www.facebook.com/andre.verwijs> La Ventura (heavy metal band) Tumblr page: http://laventurafan.tumblr.com My Twitter Page: http://twitter.com/OpenSimFan My Facebook page (Be my friend please :) ) http://www.facebook.com/andre.verwijs My Google+ page (follow me please ) André Verwijs - Google+ https://plus.google.com/111310545842863442992 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] test
by André Verwijs 29 Jun '17

29 Jun '17

test.. -- ______________________________________________________________________________________ JAV-logo-met-naam <http://www.facebook.com/andre.verwijs> La Ventura (heavy metal band) Tumblr page: http://laventurafan.tumblr.com My Twitter Page: http://twitter.com/OpenSimFan My Facebook page (Be my friend please :) ) http://www.facebook.com/andre.verwijs My Google+ page (follow me please ) André Verwijs - Google+ https://plus.google.com/111310545842863442992 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0