June 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Amarok locks up frequently
by James Knott 08 Jun '19

08 Jun '19

Since updating to openSUSE 15.1, I've noticed Amarok locks up frequently. Some times it runs for hours, other times it stops after a few songs. While I can usually close it with Quit, sometimes I have to kill the app from the command line. In 15.0 it locked up occasionally, nowhere near as it does in 15.1. Has anyone else experienced this? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Problem booting 15.1
by Frans de Boer 08 Jun '19

08 Jun '19

LS, Ever since I updated my 15.0 to 15.1, including updates, the system will not boot correctly with the supplied kernel. Any other (own compiled or directly copied from TW) does boot correctly. My system is an old but still going strong enough Phenom II 965. Observation: the kernel does boot, it displays messages about an attached USB mass storage device, I see a lot of disk activity but never ends at a prompt or other display. Interrupts are still going on, but no display. Anybody a suggestion? Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] 15.1 .Xresources not honored - Where to set xterm*termName: xterm-256color
by David C. Rankin 08 Jun '19

08 Jun '19

All, Using zsh on 15.1 my prompt was set without color. The problem is the xterm TERM variable (resource xterm.termName: xterm-256color) is not set as specified in my ~/.Xresources file. Where to set xterm-256color in 15.1? -- 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

2 4

[opensuse] certbot error
by Dave Howorth 08 Jun '19

08 Jun '19

I just decided to see if I could set up HTTPS on the Apache server(s) on my private LAN. I installed certbot (Leap 15.0) but I got an error when I ran it: # certbot --apache Saving debug log to /var/log/certbot/letsencrypt.log Plugins selected: Authenticator apache, Installer apache Enter email address (used for urgent renewal and security notices) (Enter 'c' to cancel): certbot(a)howorth.org.uk ------------------------------------------------------------------------------- Please read the Terms of Service at https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must agree in order to register with the ACME server at https://acme-v01.api.letsencrypt.org/directory ------------------------------------------------------------------------------- (A)gree/(C)ancel: A An unexpected error occurred: The server experienced an internal error :: Unable to update registration Please see the logfiles in /var/log/certbot for more details. The contents of the log are just under 15000 bytes from that session! The error seems to start at: 2019-06-07 21:57:08,381:DEBUG:urllib3.connectionpool:https://acme-v01.api.letsencrypt.org:443 "POST /acme/reg/58775261 HTTP/1.1" 500 107 2019-06-07 21:57:08,382:DEBUG:acme.client:Received response: HTTP 500 Server: nginx Content-Type: application/problem+json Content-Length: 107 Boulder-Requester: 58775261 Replay-Nonce: mEggCvGs9jNQkdzADeFIjybA87yrXSm3jK2rYlucpdM Expires: Fri, 07 Jun 2019 20:57:08 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 07 Jun 2019 20:57:08 GMT Connection: close { "type": "urn:acme:error:serverInternal", "detail": "Unable to update registration", "status": 500 } 2019-06-07 21:57:08,382:DEBUG:certbot.log:Exiting abnormally: Traceback (most recent call last): File "/usr/bin/certbot", line 11, in <module> load_entry_point('certbot==0.24.0', 'console_scripts', 'certbot')() File "/usr/lib/python2.7/site-packages/certbot/main.py", line 1315, in main return config.func(config, plugins) File "/usr/lib/python2.7/site-packages/certbot/main.py", line 1072, in run le_client = _init_le_client(config, authenticator, installer) File "/usr/lib/python2.7/site-packages/certbot/main.py", line 637, in _init_le_client acc, acme = _determine_account(config) File "/usr/lib/python2.7/site-packages/certbot/main.py", line 516, in _determine_account config, account_storage, tos_cb=_tos_cb) File "/usr/lib/python2.7/site-packages/certbot/client.py", line 166, in register regr = perform_registration(acme, config, tos_cb) File "/usr/lib/python2.7/site-packages/certbot/client.py", line 190, in perform_registration tos_cb) File "/usr/lib/python2.7/site-packages/acme/client.py", line 838, in new_account_and_tos return self.client.agree_to_tos(regr) File "/usr/lib/python2.7/site-packages/acme/client.py", line 292, in agree_to_tos regr.update(body=regr.body.update(agreement=regr.terms_of_service))) File "/usr/lib/python2.7/site-packages/acme/client.py", line 110, in update_registration updated_regr = self._send_recv_regr(regr, body=body) File "/usr/lib/python2.7/site-packages/acme/client.py", line 76, in _send_recv_regr response = self._post(regr.uri, body) File "/usr/lib/python2.7/site-packages/acme/client.py", line 95, in _post return self.net.post(*args, **kwargs) File "/usr/lib/python2.7/site-packages/acme/client.py", line 1185, in post return self._post_once(*args, **kwargs) File "/usr/lib/python2.7/site-packages/acme/client.py", line 1202, in _post_once response = self._check_response(response, content_type=content_type) File "/usr/lib/python2.7/site-packages/acme/client.py", line 1054, in _check_response raise messages.Error.from_json(jobj) Error: urn:acme:error:serverInternal :: The server experienced an internal error :: Unable to update registration 2019-06-07 21:57:08,404:ERROR:certbot.log:An unexpected error occurred: 2019-06-07 21:57:08,405:ERROR:certbot.log:The server experienced an internal error :: Unable to update registration /var/log/certbot/letsencrypt.log lines 130-185/185 (END) Does anybody have any idea what it all means? Yours, Puzzled -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] Dead disk
by Carlos E. R. 08 Jun '19

08 Jun '19

Hi, My only 3 TB Seagate disk died suddenly, at 19447 hours of use. Smartctl was perfect one day, thousand of bad sectors the next day. Report attached. I bought a new disk and tried dd_rhelp to try recover some. It coredumped after a while. So I switched to ddrescue instead, which did finished - but it recovered less than 1%. Telcontar:~/Rescate_sde # time ddrescue --force /dev/sdf /dev/sde mapfile GNU ddrescue 1.23 Press Ctrl-C to interrupt ipos: 3000 GB, non-trimmed: 0 B, current rate: 0 B/s opos: 3000 GB, non-scraped: 0 B, average rate: 270 kB/s non-tried: 0 B, bad-sector: 2975 GB, error rate: 15374 kB/s rescued: 24785 MB, bad areas: 6, run time: 1d 1h 29m pct rescued: 0.82%, read errors:5857531191, remaining time: n/a time since last successful read: 1d 53m 36s Finished real 1529m30.632s user 135m6.844s sys 750m55.166s Telcontar:~/Rescate_sde # On syslog, tons of errors - I copy the end of it: <1.4> 2019-06-06 17:47:33 Telcontar udisksd 4343 - - Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_Z1F42M6N: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) <1.4> 2019-06-06 17:57:33 Telcontar udisksd 4343 - - Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_Z1F42M6N: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) <0.6> 2019-06-06 17:57:33 Telcontar kernel - - - [156725.304768] sd 7:0:0:0: [sdf] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-06-06 17:57:33 Telcontar kernel - - - [156725.304772] sd 7:0:0:0: [sdf] tag#17 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00 <1.4> 2019-06-06 18:07:33 Telcontar udisksd 4343 - - Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_Z1F42M6N: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) <0.6> 2019-06-06 18:07:33 Telcontar kernel - - - [157325.363715] sd 7:0:0:0: [sdf] tag#19 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-06-06 18:07:33 Telcontar kernel - - - [157325.363719] sd 7:0:0:0: [sdf] tag#19 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00 <1.4> 2019-06-06 18:17:34 Telcontar udisksd 4343 - - Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_Z1F42M6N: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) <0.6> 2019-06-06 18:17:34 Telcontar kernel - - - [157925.740068] sd 7:0:0:0: [sdf] tag#21 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-06-06 18:17:34 Telcontar kernel - - - [157925.740072] sd 7:0:0:0: [sdf] tag#21 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00 <1.4> 2019-06-06 18:27:34 Telcontar udisksd 4343 - - Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_Z1F42M6N: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) <0.6> 2019-06-06 18:27:34 Telcontar kernel - - - [158526.004939] sd 7:0:0:0: [sdf] tag#23 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-06-06 18:27:34 Telcontar kernel - - - [158526.004944] sd 7:0:0:0: [sdf] tag#23 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00 <1.4> 2019-06-06 18:37:33 Telcontar udisksd 4343 - - Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/ST3000DM001_1CH166_Z1F42M6N: Error updating SMART data: Error sending ATA command CHECK POWER MODE: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0) <0.6> 2019-06-06 18:37:33 Telcontar kernel - - - [159125.573187] sd 7:0:0:0: [sdf] tag#25 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK <0.6> 2019-06-06 18:37:33 Telcontar kernel - - - [159125.573191] sd 7:0:0:0: [sdf] tag#25 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00 I attach what I think is the start section of the log when I connected the disk. How can a disk get that amount of bad data? The surface can not go bad entirely except for a few megabytes at the start of the disk, it has to be the electronics. Any ideas? I want to know if it is possible to power cycle the disk, then use ddrescue again in some form so that it ignores previously read sectors and goes for the bad areas directly. The data is just multimedia, no big deal - I hope - so I'm mostly playing with the disk. Apparently I don't have any other 3TB unit (I know they were bad, but hey, this unit is years old) to switch the board. I do have a 2TB unit with true surface defects. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

4 3

[opensuse] install-new-recommends auto-agree-with-licenses
by christian schmitt 08 Jun '19

08 Jun '19

Hello, after adding the Nvidie repositories I'm trying to install-new-recommends with the following command: zypper --non-interactive install-new-recommends Then I get the following Warning: 92 new packages to install. Overall download size: 108.9 MiB. Already cached: 0 B. After the operation, additional 431.9 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Do you agree with the terms of the license? [yes/no] (no): no Aborting installation due to the need for license confirmation. Please restart the operation in interactive mode and confirm your agreement with required licenses, or use the --auto-agree-with-licenses option. In this case the problem is the Nvidia license. But there is no way to combine install-new-recommends with --auto-agree-with-licenses I tried different orders like zypper install-new-recommends --auto-agree-with-licenses The flag --auto-agree-with-licenses is not known zypper --auto-agree-with-licenses install-new-recommends The flag --auto-agree-with-licenses is not known. Is there any other way to install new recommends with auto accept licenses? Best regards Chris -- Christian Schmitt Network and Systemadministrator Technische Universität Darmstadt Graduate School of Computational Engineering Dolivostraße 15, S4 10/326 64293 Darmstadt Office: +49 (0)6151 / 16-24403 Fax: +49 (0)6151 / 16-24404 schmitt(a)gsc.tu-darmstadt.de http://www.graduate-school-ce.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 9

[opensuse] Install openSUSE 15.1 on ThinkPad
by James Knott 06 Jun '19

06 Jun '19

My next victim for installing 15.1 is my Lenovo ThinkPad E520. On the disk, there's a primary partition /dev/sda4, which is Lenovo recovery. Part of my plan is to convert the disk from MBR to UEFI. Will this partion cause any problems? Is it just a matter of backing up and restoring that partition? Does it have to be in the same place? This computer is currently running 15.0. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] NFS: nfs4_reclaim_open_state: Lock reclaim failed! / nfs root on ipv6 with leap 15.0 ?
by Per Jessen 05 Jun '19

05 Jun '19

I seem to be hitting $SUBJ more and more often, with Leap 15.0 systems/clients. Sofar the easy way out has been to force a connection over ipv4 only. Before I go delve into this, does $subj ring a bell with anyone? -- Per Jessen, Zürich (27.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] susepaste image is broken -- again..
by David C. Rankin 05 Jun '19

05 Jun '19

Please route this to the susepaste maintainer (I can't find one on the page, "powered by..." doesn't count) Attempting to paste an image results in: 404 Page Not Found Two attempts were made an hour apart, same result. -- 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

6 10

[opensuse] How to exclude sites from Zypper?
by Anton Aylward 04 Jun '19

04 Jun '19

I mean site not repository. I know, because in the past, I can download at speed in excess of 6megabytes/sec from some sites 9and, lets face it, from YouTube and other streaming sites), and still can if I sftp/wget/cURL from specific ones, but the supposed smarts or mirrorbrain are selecting sites that, while they may be electrically closer, are delivering less than 1% of that, often even less, sometimes single digit byes/sec. Other than firewalling out specific sites, and somehow getting zypper to deal with that error (but I'm not sure how), how can I tell the mirrorbrain selection that I don't want "the closest and mostest"? Who knows, perhaps Estonia is faster than Waterloo? Currently downloading a new kernel at between 88 and 32 kiloBITS/sec -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 20