August 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] 42.3 Yast User and Group Management doesn't work.
by James Knott 07 Sep '17

07 Sep '17

I just tried to create a group in 42.3. When I start User and Group Management, the progress bar stops at 80%, step "Read users and groups" and stays there. This makes it impossible to manage groups & users. This is happening on 2 different computers. Any idea how to get past this? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 32

[opensuse] google-chrome changed gpg signing key?
by ellanios82 03 Sep '17

03 Sep '17

am seeing : File 'repomd.xml' from repository 'google-chrome' is signed with an unknown key '1397BC53640DB551' regards .... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10

[opensuse] 42.3 - Konqueror doesn't open to home directory
by James Knott 01 Sep '17

01 Sep '17

Since updating to 42.3, I find Konqueror no longer opens to my home directory. I was finally able to get it to the point where it opens to a blank screen, but I still have to click on the home button, to show my home directory? Is there any way to fix this, so that it works properly? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 34

[opensuse] root login to kde 4
by Istvan Gabor 01 Sep '17

01 Sep '17

Hello: I have openSUSE Leap 42.2 and kdm4 display manager. I would like to login to kde 4 session as root. (I have to unmount /home partition for maintaining, therefore I can't login as normal user and use su, kdesu etc, still I want to work in GUI.) If I try to login as root the login process starts but in a few moments it stops and it gives back the login window. I have set DISPLAYMANAGER_ROOT_LOGIN_LOCAL to yes in /etc/sysconfig/displaymanager file, DISPLAYMANAGER_SHUTDOWN is set to all, and PERMISSION_SECURITY is set to easy local in /etc/sysconfig/security file. I checked /usr/share/kde4/config/kdm/kdmrc file too. I did not have line AllowRootLogin, therefore I added AllowRootLogin=true line to [X-*-Core] session. This did not help, still cannot login as root. /var/log/messages shows: 2017-08-31T12:53:12.618924+02:00 linux kdm: :1[7197]: pam_unix(xdm:session): session opened for user root by (uid=0) 2017-08-31T12:53:12.626813+02:00 linux systemd[1]: Created slice User Slice of root. 2017-08-31T12:53:12.654821+02:00 linux systemd[1]: Starting User Manager for UID 0... 2017-08-31T12:53:12.667489+02:00 linux systemd-logind[1192]: New session 97 of user root. 2017-08-31T12:53:12.667732+02:00 linux systemd: pam_unix(systemd-user:session): session opened for user root by (uid=0) 2017-08-31T12:53:12.667920+02:00 linux systemd[1]: Started Session 97 of user root. 2017-08-31T12:53:12.739948+02:00 linux systemd[7220]: Reached target Sockets. 2017-08-31T12:53:12.740423+02:00 linux systemd[7220]: Reached target Paths. 2017-08-31T12:53:12.740718+02:00 linux systemd[7220]: Reached target Timers. 2017-08-31T12:53:12.741003+02:00 linux systemd[7220]: Reached target Basic System. 2017-08-31T12:53:12.741281+02:00 linux systemd[7220]: Reached target Default. 2017-08-31T12:53:12.741555+02:00 linux systemd[7220]: Startup finished in 74ms. 2017-08-31T12:53:12.741843+02:00 linux systemd[1]: Started User Manager for UID 0. 2017-08-31T12:53:12.877188+02:00 linux checkproc: checkproc: can not get session id for process 6964! 2017-08-31T12:53:12.916858+02:00 linux kdm: :1[7197]: pam_unix(xdm:session): session closed for user root 2017-08-31T12:53:15.923156+02:00 linux systemd-logind[1192]: Removed session 97. 2017-08-31T12:53:15.926077+02:00 linux systemd[1]: Stopping User Manager for UID 0... 2017-08-31T12:53:15.927075+02:00 linux systemd[7220]: Stopped target Default. 2017-08-31T12:53:15.927325+02:00 linux systemd[7220]: Stopped target Basic System. 2017-08-31T12:53:15.927524+02:00 linux systemd[7220]: Stopped target Timers. 2017-08-31T12:53:15.927674+02:00 linux systemd[7220]: Reached target Shutdown. 2017-08-31T12:53:15.927831+02:00 linux systemd[7220]: Stopped target Paths. 2017-08-31T12:53:15.928111+02:00 linux systemd[7220]: Stopped target Sockets. 2017-08-31T12:53:15.942576+02:00 linux systemd[7220]: Starting Exit the Session... 2017-08-31T12:53:15.949867+02:00 linux systemd[7220]: Received SIGRTMIN+24 from PID 7307 (kill). 2017-08-31T12:53:15.953240+02:00 linux systemd: pam_unix(systemd-user:session): session closed for user root 2017-08-31T12:53:15.956168+02:00 linux systemd[1]: Stopped User Manager for UID 0. 2017-08-31T12:53:15.961748+02:00 linux systemd[1]: Removed slice User Slice of root. How could I trace and fix this? Any help is appreciated. Thanks, Istvan ps: Please don not write that I should not log in to GUI as root, because it does not help to solve the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 15

[opensuse] Tar file Error - Urgent data recovery
by Paul Groves 01 Sep '17

01 Sep '17

I am having problems with extracting a tar file for a colleague. It was created with tar / gzip on opensuse 42.1 and a md5 checksum generated and stored on a NAS. The 42.1 box had a disk failure (which is why I keep advising everyone to use raid but they still do not listen until it goes wrong). So 42.3 has been installed on the new disk(s) which are now in raid (which would have avoided this problem had I been listened to in the first place). So first thing, I verified the md5 sum against the tar file which came back succesful. so I am using tar -xvzf /mnt/BACKUP/file.tar.gz to extract the file. But I keep getting the following error before extraction completes: gzip: stdin: Input/output error tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now The odd thing is it isn't happening on one file, it happens on a different one every time (but never gets to the end). How can I recover the data in this tar file? Is there a way to ignore this error and continue anyway? It is quite important to get this data back so I would really appreciate some help. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

13 56

[opensuse] Tape Drive Trouble
by Paul Groves 01 Sep '17

01 Sep '17

Hi, I have 4 tape drives in my server and I am lately experiencing a few problems. One night a backup failed with rmtio failed: Input output Error. I ran it again and it worked. This has happened more and more frequently and now the drive fails writing every time with this error. I put the drive (Hp storageworks Ultrium 920) in another server. It works fine. I have just received a storageworks ultrium 1760 drive today. Same problem is occuring. The easiest way to make the error come up is to try mt -f /dev/st3 erase The drive sounds like it erases the tape, then the tape is unloaded and goes back in again automatically. Then it erases it again, then does it again then again and again then eventually it gives up with the message mt: /dev/st3: rmtioctl failed: Input/output error Can anyone enlighten me, what exactly is an mt: rmtio: Input/output error and how can I diagnose where exactly this error is occuring. I have tried disconnecting all other drives on the SCSI bus and only connecting the one scsi drive. I have also tried a different scsi connector on the same cable (which is where another drive that works fine is usually connected). I thought could this be a fault with the cable or the controller? But why would the other 3 drives work fine? Then I thought but if the problem is with my two drives why do they both work in another server? I have also tried connecting one of my working drives to each SCSI connector on the cable in turn and it works fine on every one of them, so surely it is not the SCSI controller or cable? Answers to the obvious: The drive jumper pins are correct I do have a terminator on the end of the SCSI cable I have tried more than one tape I have ran several cleaning cartridges in each drive. There are no error LEDs on the drives I have already tried turning it off and on again :) Please can anyone assist with this? I am completely stumped. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 113

[opensuse] Alt-F2 man:/ broken
by James Knott 31 Aug '17

31 Aug '17

A while ago, I posted here about how pressing Alt-F2 # no longer worked properly for opening man pages. Now even using man:/ no longer works. When I try to open a man page, the Seamonkey browser opens to a blank page. In order to see a man page, I now have to open Konqueror or Dolphin and enter the command there. Why does this no longer work? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 15

[opensuse] Firefox video question
by James Knott 31 Aug '17

31 Aug '17

Is there a way to stop videos from playing automatically? I frequent a lot of news sites that include videos with the articles. For some idiotic reason someone has decided the videos should play automatically, which I find very annoying. Is there any way to turn this off? I am quite capable of clicking on the play button, should I actually wish to watch the video. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 24

[opensuse] 42.3: I had to rework openvpn@.service
by Roger Price 31 Aug '17

31 Aug '17

I installed openvpn in a fresh 42.3 and copied the configuration files from a working installation into /etc/openvpn/ . I then tried with Yast to enable and start the openvpn@.service provided by the package, This failed with message Failed to get properties: Unit name openvpn@.service is not valid. So I defined service unit /usr/lib/systemd/system/openvpn.service (no @) [Unit] Description=OpenVPN tunneling daemon instance using /etc/openvpn/server.conf After=network.target PartOf=openvpn.target [Service] Type=forking PrivateTmp=true PIDFile=/var/run/openvpn/server.pid ExecStart=/usr/sbin/openvpn --daemon --suppress-timestamps --writepid /var/run/openvpn/server.pid --cd /etc/openvpn/ --config server.conf ExecReload=/sbin/killproc -p /var/run/openvpn/server.pid -HUP /usr/sbin/openvpn [Install] WantedBy=multi-user.target openvpn.target This service unit is the same as openvpn@.service, but explicitly specifies where the configuration files are and where the pid goes. I enabled openvpn.service with Yast and successfully started it with command systemctl start openvpn.service . Why does the package provide the extra %i and %I engineering which doesn't work? Roger -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Docker update in 42.3
by Jason Evans 30 Aug '17

30 Aug '17

Hi all, Has anyone heard when Docker 17.x will be released on Leap 42.3? It's been available on SLES 12 SP 2 for a few weeks already. -- Best Regards, Jason Evans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0