September 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] is ubuntu better than opensuse 15.1?
by Daniel Bauer 05 Sep '19

05 Sep '19

Hi, unfortunately quite working 42.3 had to be replaced with 15.1 due to end of security updates which are important to me. Now, this system seems not to be able to handle my Nvidia GeForce GTX 460. It freezes all the time. If it doesn't freeze the desktop effects get switched off due to "restart of graphics". When I log out and in, the desktop icons spread somehow over the screen and I have to reorder them - each and every time. Bug reports are not seen, obviously. Problem is, that this is my working computer and since two days I simply cannot work with it. I know that Opensuse cuts functionality in each release since 13.x, but I didn't imagine that it simply would stop being usable at all. Now I have two possibilities: - buy another graphics card that will maybe work a year or two until OpenSuse decides to stop working with it, too. - install another operating system. Both possibilities are complicated. I am with openSuse since 20 years, and it has always bettered until the regression started from 13.x. I'd have to learn a new system. Windows is excluded, as it makes me sick. So could be ubuntu? A new graphics card is expensive (I need quite a lot of power). Also I don't have any idea which one. One that fulfills my needs on one side, and that is supported by OpenSuse which I think is not really made anymore for a graphic desktop, more for a pure console computer, server or the like. What do you recommend? Give it a try with ubuntu? Buy another graphics card? Which? -- 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

16 59

[opensuse] setenv DISPLAY $HOST:0.0
by Wolfgang Mueller 05 Sep '19

05 Sep '19

Under Leap 15.1 any attempt to open the display with a $DISPLAY value different from :0.0 fails and generates the answer: <program>: can't open display <HOST>:0.0, aborting Under 13.2, an efficient work around was removing "-nolisten tcp" from the files /etc/X11/xinit/xserverrc and /etc/X11/xdm/Xservers as follows: diff /etc/X11/xinit/xserverrc /etc/X11/xinit/xserverrc.bak < args="$args" --- > args="$args -nolisten tcp" ------------------------------------------------------------- diff /etc/X11/xdm/Xservers /etc/X11/xdm/Xservers.bak < :0 local /usr/bin/X -br vt7 -keeptty --- > :0 local /usr/bin/X -nolisten tcp -br vt7 -keeptty But these modifications do not help any more, because the failure not only happens at a request from outside (TCP) but also at a local request. What can I do to provide "setenv DISPLAY $HOST:0.0" making sense under Leap 15.1? Thanks in advance, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 7

[opensuse] ssh without passwd
by Wolfgang Mueller 05 Sep '19

05 Sep '19

"ssh-keygen" generated ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub Then ~/.ssh/id_rsa.pub has been copied to the remote site and given the name ~/.ssh/authorized_keys there. Whereas ssh without password from a SuSE 13.2 site to a Leap 15.1 site works perfectly for any user, from a Leap 15.1 site to a SuSE 13.2 site it works for root only, and different users are asked for a password. How can I achieve ssh to be accepted without password for "normal" users, too? Thanks in advance for your help. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

11 18

[opensuse] Can I find the percent of cpu load for a process in a script?
by Carlos E. R. 04 Sep '19

04 Sep '19

Hi, Can I find the percent of cpu load for a process inside a script? At worst, I can find it out from "top", but I wonder if there is a more direct way. I'm looking at "/proc/21500/stat" or "/proc/21500/statm", but I have no idea what each value is, where are those virtual files documented. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

8 14

[opensuse] Flash is still used today
by Carlos E. R. 04 Sep '19

04 Sep '19

Incredible. I just hit a news site that requires flash from adobe, TODAY. :-( I'm using a new firefox instance, no plugins yet, so no flash support, I suppose. <https://cadenaser.com/emisora/2019/08/27/radio_cartagena/1566895744_214802.…> (no , I'm not asking how to add flash support... (yet)... just saying that today there are sites that still use it. I'm flabergasted) (Chrome plays it) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

8 35

[opensuse] Updating FF 60.8esr - 68.0esr - anybody notice font rendering change on Linux?
by David C. Rankin 04 Sep '19

04 Sep '19

All, I updated from FF 60.8esr to 68.0esr on one box and had font size render approximately 1-2 points smaller in the new version. Has anyone else seen this? -- 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

1 1

[opensuse] YaST language confusion
by gumb 03 Sep '19

03 Sep '19

New install, Leap 15.1. Just getting basics set up. I generally use English (GB) for all system setup and desktop interface elements, with French added as a keyboard layout and/or for secondary language support. So after looking yesterday in YaST -> Software Management and viewing the Language tab, I scrolled down to fr and ticked 4 or 5 additional French packages, including yast2-trans-fr. Today when I start YaST, all the menus are in French. Ok, I can use it, but I prefer that it stays in English, for now at least. I just like to have French as a switchable standby for providing/receiving support, and/or for possible additional system users. So thinking it must be that yast2-trans-fr package I added which is responsible, I remove it again. When I start up YaST again, the menus are still in French, whereas the configuration options shown within each YaST category are in English for some and French for others. I've looked in the root home, in /etc and cannot find where this is configured. At the bottom of the file /etc/sysconfig/language, is a setting described as 'List of installed language supports, use by YaST2'. It is set as INSTALLED_LANGUAGES="en_GB" Everything else in the system is in English GB. Why is it overriding this in YaST, and where is this set? gumb -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 26

[opensuse] Clamav process is now even more memory hungry
by Carlos E. R. 03 Sep '19

03 Sep '19

Photo using top, sort by memory, this instant: > PID USER PR NI VIRT RES SHR SWAP S %CPU %MEM TIME+ COMMAND > 21395 cer 20 0 3402620 782716 85432 166280 S 69,35 9,591 61:58.83 Web Content > 1096 cer 20 0 3688736 767644 104104 0 S 2,976 9,406 19:05.04 thunderbird-bin > 3938 vscan 20 0 999648 725460 2628 17856 S 0,000 8,889 8:09.22 clamd .................................******* 0.7 GB of RAM! I will have to uninstall it. Las time I looked, it was half a gigabyte. And it is set with swapiness of 100... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

2 29

[opensuse] why is my USB external disk disconnecting?
by Daniel Bauer 03 Sep '19

03 Sep '19

Hello, I use several encrypted USB disks for backups with rsync, some 3.5" with own power, some 2.5" only USB. Since 15.1 with /all/ of those disks I see longer "pauses" during rsync. I typed "dmesg" during the last rsync (to a 2.5") and got the following: > [442504.857344] sd 20:0:0:0: [sde] Attached SCSI disk > [442515.720544] device-mapper: table: 254:7: adding target device sde caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=33553920 > [442515.720547] device-mapper: table: 254:7: adding target device sde caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=33553920 > [442515.720594] device-mapper: table: 254:7: adding target device sde caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=33553920 > [442515.720596] device-mapper: table: 254:7: adding target device sde caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=33553920 > [442516.010328] REISERFS (device dm-7): found reiserfs format "3.6" with standard journal > [442516.010386] REISERFS (device dm-7): using ordered data mode > [442516.010386] reiserfs: using flush barriers > [442516.020114] REISERFS (device dm-7): journal params: device dm-7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 > [442516.020385] REISERFS (device dm-7): checking transaction log (dm-7) > [442516.117122] REISERFS (device dm-7): Using r5 hash to sort names > [442636.173855] sd 20:0:0:0: [sde] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT > [442636.173861] sd 20:0:0:0: [sde] tag#2 CDB: Write(10) 2a 00 4c 15 73 97 00 04 00 00 > [442636.174105] sd 20:0:0:0: [sde] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT > [442636.174109] sd 20:0:0:0: [sde] tag#1 CDB: Write(10) 2a 00 4c 15 6f 97 00 04 00 00 > [442636.175459] sd 20:0:0:0: [sde] tag#0 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD OUT > [442636.175463] sd 20:0:0:0: [sde] tag#0 CDB: Write(10) 2a 00 4c 15 6b 97 00 04 00 00 > [442636.177455] sd 20:0:0:0: [sde] tag#27 uas_eh_abort_handler 0 uas-tag 28 inflight: CMD IN > [442636.177459] sd 20:0:0:0: [sde] tag#27 CDB: Read(10) 28 00 70 c4 ff ff 00 00 08 00 > [442636.177706] sd 20:0:0:0: [sde] tag#22 uas_eh_abort_handler 0 uas-tag 23 inflight: CMD OUT > [442636.177709] sd 20:0:0:0: [sde] tag#22 CDB: Write(10) 2a 00 4c 15 67 97 00 04 00 00 > [442636.177960] sd 20:0:0:0: [sde] tag#13 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD OUT > [442636.177963] sd 20:0:0:0: [sde] tag#13 CDB: Write(10) 2a 00 4c 15 63 97 00 04 00 00 > [442636.179413] sd 20:0:0:0: [sde] tag#12 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD OUT > [442636.179417] sd 20:0:0:0: [sde] tag#12 CDB: Write(10) 2a 00 4c 15 5f 97 00 04 00 00 > [442636.181413] sd 20:0:0:0: [sde] tag#19 uas_eh_abort_handler 0 uas-tag 20 inflight: CMD OUT > [442636.181417] sd 20:0:0:0: [sde] tag#19 CDB: Write(10) 2a 00 4c 15 5b 97 00 04 00 00 > [442636.183417] sd 20:0:0:0: [sde] tag#14 uas_eh_abort_handler 0 uas-tag 15 inflight: CMD OUT > [442636.183421] sd 20:0:0:0: [sde] tag#14 CDB: Write(10) 2a 00 4c 15 57 97 00 04 00 00 > [442636.185414] sd 20:0:0:0: [sde] tag#11 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT > [442636.185417] sd 20:0:0:0: [sde] tag#11 CDB: Write(10) 2a 00 4c 15 53 ff 00 03 98 00 > [442636.187432] sd 20:0:0:0: [sde] tag#10 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT > [442636.187435] sd 20:0:0:0: [sde] tag#10 CDB: Write(10) 2a 00 4c 15 4f ff 00 04 00 00 > [442636.189431] sd 20:0:0:0: [sde] tag#25 uas_eh_abort_handler 0 uas-tag 26 inflight: CMD OUT > [442636.189435] sd 20:0:0:0: [sde] tag#25 CDB: Write(10) 2a 00 4c 15 4b ff 00 04 00 00 > [442636.191456] sd 20:0:0:0: [sde] tag#9 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT > [442636.191460] sd 20:0:0:0: [sde] tag#9 CDB: Write(10) 2a 00 4c 15 47 ff 00 04 00 00 > [442636.193425] sd 20:0:0:0: [sde] tag#23 uas_eh_abort_handler 0 uas-tag 24 inflight: CMD OUT > [442636.193429] sd 20:0:0:0: [sde] tag#23 CDB: Write(10) 2a 00 4c 15 43 ff 00 04 00 00 > [442636.195488] sd 20:0:0:0: [sde] tag#8 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT > [442636.195492] sd 20:0:0:0: [sde] tag#8 CDB: Write(10) 2a 00 4c 15 3f ff 00 04 00 00 > [442636.197426] sd 20:0:0:0: [sde] tag#7 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT > [442636.197430] sd 20:0:0:0: [sde] tag#7 CDB: Write(10) 2a 00 45 02 08 2f 00 00 b8 00 > [442636.199450] sd 20:0:0:0: [sde] tag#20 uas_eh_abort_handler 0 uas-tag 21 inflight: CMD OUT > [442636.199454] sd 20:0:0:0: [sde] tag#20 CDB: Write(10) 2a 00 45 02 04 2f 00 04 00 00 > [442636.201429] sd 20:0:0:0: [sde] tag#15 uas_eh_abort_handler 0 uas-tag 16 inflight: CMD OUT > [442636.201432] sd 20:0:0:0: [sde] tag#15 CDB: Write(10) 2a 00 45 02 00 47 00 03 e0 00 > [442636.203481] sd 20:0:0:0: [sde] tag#6 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT > [442636.203485] sd 20:0:0:0: [sde] tag#6 CDB: Write(10) 2a 00 45 01 fc 47 00 04 00 00 > [442636.237936] scsi host20: uas_eh_device_reset_handler start > [442636.403099] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd > [442636.428555] scsi host20: uas_eh_device_reset_handler success > [442677.133816] sd 20:0:0:0: [sde] tag#9 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT > [442677.133821] sd 20:0:0:0: [sde] tag#9 CDB: Write(10) 2a 00 71 cc e9 5f 00 04 00 00 > [442677.134077] sd 20:0:0:0: [sde] tag#8 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT > [442677.134082] sd 20:0:0:0: [sde] tag#8 CDB: Write(10) 2a 00 71 cc e5 5f 00 04 00 00 > [442677.135280] sd 20:0:0:0: [sde] tag#7 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD OUT > [442677.135285] sd 20:0:0:0: [sde] tag#7 CDB: Write(10) 2a 00 71 cc e1 5f 00 04 00 00 > [442677.137272] sd 20:0:0:0: [sde] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT > [442677.137276] sd 20:0:0:0: [sde] tag#6 CDB: Write(10) 2a 00 71 cc dd 5f 00 04 00 00 > [442677.139288] sd 20:0:0:0: [sde] tag#5 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT > [442677.139290] sd 20:0:0:0: [sde] tag#5 CDB: Write(10) 2a 00 71 cc d9 5f 00 04 00 00 > [442677.157853] scsi host20: uas_eh_device_reset_handler start > [442677.294928] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd > [442677.320143] scsi host20: uas_eh_device_reset_handler success > [442720.141648] sd 20:0:0:0: [sde] tag#4 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD OUT > [442720.141652] sd 20:0:0:0: [sde] tag#4 CDB: Write(10) 2a 00 77 04 d0 37 00 04 00 00 > [442720.141852] sd 20:0:0:0: [sde] tag#3 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT > [442720.141854] sd 20:0:0:0: [sde] tag#3 CDB: Write(10) 2a 00 77 04 cc 37 00 04 00 00 > [442720.157677] scsi host20: uas_eh_device_reset_handler start > [442720.286882] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd > [442720.312214] scsi host20: uas_eh_device_reset_handler success > [442752.909656] sd 20:0:0:0: [sde] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT > [442752.909661] sd 20:0:0:0: [sde] tag#2 CDB: Write(10) 2a 00 77 e0 d5 07 00 04 00 00 > [442752.909863] sd 20:0:0:0: [sde] tag#1 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT > [442752.909866] sd 20:0:0:0: [sde] tag#1 CDB: Write(10) 2a 00 77 e0 d1 07 00 04 00 00 > [442752.925674] scsi host20: uas_eh_device_reset_handler start > [442753.054945] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd > [442753.079907] scsi host20: uas_eh_device_reset_handler success > [442918.797378] sd 20:0:0:0: [sde] tag#6 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT > [442918.797384] sd 20:0:0:0: [sde] tag#6 CDB: Write(10) 2a 00 1d a8 ff ff 00 00 08 00 > [442918.813354] scsi host20: uas_eh_device_reset_handler start > [442918.942568] usb 3-2: reset SuperSpeed USB device number 2 using xhci_hcd > [442918.967540] scsi host20: uas_eh_device_reset_handler success why is this happening? All always went normal and fast with 42.3 and the same disks.... What can I do? -- 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

2 1

[opensuse] delay on boot
by jdd＠dodin.org 03 Sep '19

03 Sep '19

Hello, I'm still on research to understand why I have a 10/20s delay at the end of the kde plasma load. At some time I suspected IPV6, but finally no, it's not. then I find in the boot messages some about a large usb disk (5Tb, archives) that is connected but do not have to be mounted at boot (do not live in fstab), because it's known to be extremely so when mounting. so, why is there this dmesg entry? May be it was mounted when I switched off the computer? thanks jdd dmesg: [ 36.177914] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: (null) [ 38.276709] Bluetooth: RFCOMM ver 1.11 [ 115.782681] sd 5:0:0:0: [sdc] Synchronizing SCSI cache [ 116.021030] sd 5:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 116.106323] usb 2-2.2: USB disconnect, device number 3 journalctl -b0: sept. 01 07:54:22 linux-tivq udisksd[2328]: Unmounted /dev/sdc1 on behalf of uid 1000 sept. 01 07:54:23 linux-tivq kernel: sd 5:0:0:0: [sdc] Synchronizing SCSI cache sept. 01 07:54:24 linux-tivq udisksd[2328]: Powered off /dev/sdc - successfully wrote to sysfs path /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2.2/r> -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 11