November 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] root full but du not showing why - snapshots? Can't even free up
by Mikhail Ramendik 16 Nov '17

16 Nov '17

Hello, I trued to upgrade to 42.3 and the process failed because the root file system was full. df -h shows it full at 40 gigabytes. But... with du, I can only find the usage of 15 gigabytes. Moreover. I found 3 gigabytes in /root that could be deleted, and promptly deleted them. But df -h is not showing any more space! I am in the command line under root, no trash system anywhere. I suspect snapshots are the problem, because I accepted the default of btrfs for the root filesystem. So I could just delete some old snapshots. But how do I list the snapshots? And how do I remove them? Somehow when I google this I can't find anything. I mean, I did find btrfs subvolume list / and it lists quite a few lines like: ID 996 gen 288328 top level 258 path @/.snapshots/558/snapshot But I can't find a way to delete these snapshots. when I do btrfs subvolume delete @/.snapshots/558/snapshot I get "no such file or directory". So how can I delete snapshots? Even better. how do I find out which snapshots are made when and include what, so I can delete those I certainly don't need? I am tempted to reinstall with an ext4 root file system, but I do not want to spend all the time needed for a fresh install. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

15 28

Re: [opensuse] Can't scp files to Tumbleweed box anymore?
by Christopher Myers 15 Nov '17

15 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Wed, 2017-11-15 at 16:04 +0000, custom valem wrote: > > El problema puede ser por actualización o bajar de versión, pruebe > con: > > > yum downgrade openssh-server openssh-clients > yum downgrade openssh-server openssh-clients > > Cool, thank you :) It doesn't look like there are old versions of packages in the repos to try to downgrade to though: caradhras:~ # zypper search -s openssh Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository - ---+---------------------------+---------+--------------+--------+----- - ------------------- | lxqt-openssh-askpass | package | 0.12.0-1.1 | x86_64 | openSUSE-Tumbleweed-Oss | lxqt-openssh-askpass | package | 0.12.0-1.1 | i586 | openSUSE-Tumbleweed-Oss | lxqt-openssh-askpass-lang | package | 0.12.0-1.1 | noarch | openSUSE-Tumbleweed-Oss i+ | openssh | package | 7.2p2-6.1 | x86_64 | openSUSE-Tumbleweed-Oss v | openssh | package | 7.2p2-6.1 | i586 | openSUSE-Tumbleweed-Oss i | openssh-askpass | package | 1.2.4.1-10.9 | x86_64 | openSUSE-Tumbleweed-Oss v | openssh-askpass | package | 1.2.4.1-10.8 | i586 | openSUSE-Tumbleweed-Oss | openssh-askpass-gnome | package | 7.2p2-6.1 | x86_64 | openSUSE-Tumbleweed-Oss | openssh-askpass-gnome | package | 7.2p2-6.1 | i586 | openSUSE-Tumbleweed-Oss | openssh-cavs | package | 7.2p2-6.1 | x86_64 | openSUSE-Tumbleweed-Oss | openssh-cavs | package | 7.2p2-6.1 | i586 | openSUSE-Tumbleweed-Oss | openssh-fips | package | 7.2p2-6.1 | x86_64 | openSUSE-Tumbleweed-Oss | openssh-fips | package | 7.2p2-6.1 | i586 | openSUSE-Tumbleweed-Oss i | openssh-helpers | package | 7.2p2-6.1 | x86_64 | openSUSE-Tumbleweed-Oss v | openssh-helpers | package | 7.2p2-6.1 | i586 | openSUSE-Tumbleweed-Oss It looks like my SSH client was upgraded about two weeks ago: caradhras:~ # rpm -qa --last | grep ssh ksshaskpass5-lang-5.11.3-1.1.noarch Wed Nov 15 08:06:38 2017 ksshaskpass5-5.11.3-1.1.x86_64 Wed Nov 15 08:06:27 2017 openssh-helpers-7.2p2-6.1.x86_64 Wed Nov 1 14:51:43 2017 openssh-7.2p2-6.1.x86_64 Wed Nov 1 14:51:32 2017 sshfs-2.9-1.2.x86_64 Fri Oct 20 10:53:30 2017 openssh-askpass-1.2.4.1-10.9.x86_64 Fri Oct 20 10:52:22 2017 libnsssharedhelper0-1.0.10-9.10.x86_64 Fri Oct 20 10:49:51 2017 libssh2-1-1.8.0-2.2.x86_64 Fri Oct 20 10:49:24 2017 libssh4-0.7.5-3.1.x86_64 Sat Oct 14 20:48:28 2017 -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAloMcvUACgkQQ1nEo4DF CIV24QgAlqj3AaC2VKV/DOMakHdgg7cnYk07HL3RCcSpxVRcFD5CdtJ8znPhkI9E Z2MCUgayBxpn1ZjdK/57QDR3tktuOJLiqWIwhYAhv7FHC5BgkEY+lr7FIHyRZDGd BDSZKCkoRGaUFB5dsrQk+P/5r5/u8cUs5USc/juqJyB5sNh+08ahDVfrgcRYr/L4 CRSXscffkZZe+nv7sdjPip8BlDXt1/RGVs38drl82uh99RPmP19Xft6VklRXN5qv JWcHurlh+EObHIaa8qZ8oOIGmSm+dZ2OKhLTBW9FdKckZmkgUR6e1x7EvniQMeY9 qO2oUDcNfqu93GaEeuM3iDnTM6pVEA== =5yf3 -----END PGP SIGNATURE----- N��r��y隊Z)z{.�ﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǿ� ޮ�^�ˬz��

1 0

[opensuse] Boot failure after update from 42.2 to 42.3 "Grub-tpm-measure not found"
by stakanov 14 Nov '17

14 Nov '17

This is a very puzzling error as I did not install trusted grub and I do not have tpm on the system. The system is also not UEFI. The update was from 42.2 (working well) to 42.3 (screwed it up and I am now in rescue mode). Did anybody encounter this or does understand what the issue actually is? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 31

Re: [opensuse] root full but du not showing why - snapshots? Can't even free up
by nicholas cunliffe 14 Nov '17

14 Nov '17

some users DO want to be bothered by snapshots, I include myself as one of them. It also includes many TW users for obvious reasons, from observation it even includes users of other distros who go to the trouble of installing it themselves. > He does not want to be told to do complex commands most issues that arise on forums require "complex commands", the cron job links are a separate bug (just solved on TW), the balance given the situation. > The problem that started this thread would simply not have occured in case ext4 would have been the basis of all. not buying this argument. for x number of other posts and situations - 'you wouldnt be stuck with a broken system if you had snapshots' 'average users' want to interact and invest in user space (the apps that give value), they want the plumbing to be hidden. If btrfs/snapshots do not add value then they are just exposed plumbing, if they add value they are worth investing in. Snapshots add value on TW, I dont know about leap. there is no universal/best backup method. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] plasma - non-KDE windows use KDE soft-whites (fcfcfc or eff0f1) unreadable - how to fix?
by David C. Rankin 14 Nov '17

14 Nov '17

All, I'm playing with plasma: KDE Frameworks 5.39.0 Qt 5.9.2 (built against 5.9.2) The xcb windowing system I have the breeze-dark theme, which is usable, with one major exception, all non-kde windows that are supposed to be white (e.g. virtualbox/Win7, etc.) are a dim blueish white. (0xfcfcfc or 0xeff0f1 -- verified by picking colors off the scrren with kde-colorchooser, that is what is set in kcontrol->Appearance->Colors) According to https://community.kde.org/File:Breeze_Color_Palette.png These are the Breeze Colors ("Paper White" and "Cardboard Grey"). However, they are being applied to non-kde apps making things that are supposed to have a white background -- not-white, totally messing up contrast in some of the non-kde apps. How do I tell plasma to leave the colors in non-kde apps alone? Looking at windows-explorer with a 0xfcfcfc background will drive you nuts with the soft-blue contrasting highlight windows uses. (it's like staring into a 'cool-blue' florescent light-bulb). I don't understand how the colors are getting applied, it's almost like there is some filter or overlay that is trying to make all colors in all apps match the breeze "View Text" and "Window Text" color theme settings. Any help would be appreciated. (another bewildering quandary is font-size. 8-pt mono is tiny on plasma and 9-pt mono looks like 11-pt -- there is literally no in between...) -- 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

7 8

[opensuse] need file from former md RAID1 member
by Felix Miata 14 Nov '17

14 Nov '17

My Google Fu isn't working very well. I need to mount the following ro long enough to find and fetch one file from what's showing up as /dev/md127. Base on a /unix.stackexchange.com page Google found[1] I tried mdadm -A /dev/sdg12 but get message device /dev/sdb12 exists but is not an md array. Of course, because it is only one of two original parts. I tried this from a different PC and get the same message. Also from that page I tried mdadm --assemble --scan which only got a usage message on the first machine, and got No arrays found in config file or automatically. On the second Next tried on first. mount -t ext4 -o ro,noatime /dev/sdg12 /mnt but get the message /dev/sdg12 is already mounted or /mnt busy df shows no use of either /mnt or sdg12, and there is no sdg<anything> showing as in use in /proc/mdstat. What do I need to do? The machine this disk came from is the one of two I'm currently trying to use for the recovery, but isn't necessary to the recovery, simply what was handy and known to have working RAID modules available. Its own RAID1 was migrated from 320GB disks to 500GB several years ago. # blkid /dev/sdg12 /dev/sdg12: UUID="fc3787e2-bc83-c66c-8afe-62881c75f7f0" UUID_SUB="40d2e084-2321-f3f4-f6f7-c64f526127f3" LABEL="5" TYPE="linux_raid_member" # mdadm --examine /dev/sdg12 /dev/sdg12: Magic : a92b4efc Version : 1.0 Feature Map : 0x1 Array UUID : fc3787e2:bc83c66c:8afe6288:1c75f7f0 Name : 5 Creation Time : Tue Jan 6 23:55:05 2009 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 2072296 (1011.86 MiB 1061.02 MB) Array Size : 1036148 (1011.86 MiB 1061.02 MB) Super Offset : 2072304 sectors Unused Space : before=0 sectors, after=8 sectors State : clean Device UUID : 40d2e084:2321f3f4:f6f7c64f:526127f3 Internal Bitmap : 2 sectors from superblock Update Time : Sat Apr 16 21:40:43 2011 Checksum : c6042453 - correct Events : 8 Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing, 'R' == replacing) # cat /proc/mdstat Personalities : [raid1] md120 : inactive sdg13[0](S) 78140056 blocks super 1.0 md121 : inactive sdg14[0](S) 156280216 blocks super 1.0 md122 : inactive sdg8[1](S) 10650988 blocks super 1.0 md123 : inactive sdg10[0](S) 10650988 blocks super 1.0 md124 : inactive sdg9[0](S) 10650988 blocks super 1.0 md125 : inactive sdg11[0](S) 28362652 blocks super 1.0 md126 : inactive sdg7[1](S) 9422016 blocks super 1.0 md127 : inactive sdg12[0](S) 1036148 blocks super 1.0 md3 : active raid1 sdb11[3] sda11[2] 10650988 blocks super 1.0 [2/2] [UU] bitmap: 0/163 pages [0KB], 32KB chunk md0 : active raid1 sdb8[3] sda8[2] 9422016 blocks super 1.0 [2/2] [UU] bitmap: 0/144 pages [0KB], 32KB chunk md4 : active raid1 sda12[2] sdb12[3] 28362652 blocks super 1.0 [2/2] [UU] bitmap: 0/217 pages [0KB], 64KB chunk md7 : active raid1 sdb15[2] sda15[0] 156280216 blocks super 1.0 [2/2] [UU] bitmap: 0/2 pages [0KB], 65536KB chunk md6 : active raid1 sda14[2] sdb14[3] 78140056 blocks super 1.0 [2/2] [UU] bitmap: 0/150 pages [0KB], 256KB chunk md5 : active raid1 sdb13[3] sda13[2] 1036148 blocks super 1.0 [2/2] [UU] bitmap: 0/8 pages [0KB], 64KB chunk md2 : active raid1 sdb10[3] sda10[2] 10650988 blocks super 1.0 [2/2] [UU] bitmap: 0/163 pages [0KB], 32KB chunk md1 : active raid1 sdb9[3] sda9[2] 10650988 blocks super 1.0 [2/2] [UU] bitmap: 0/163 pages [0KB], 32KB chunk unused devices: <none> [1] https://unix.stackexchange.com/questions/64889/how-to-mount-recover-data-on… -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] 32-bit libidn.so.11
by Mikhail Ramendik 13 Nov '17

13 Nov '17

Hello, One particular piece of software needs a 32-bit version of libidn.so.11 . I am running OpenSuse Leap 42.3 (just upgraded from 42.2) How can I get this library version into the system? Or even just into a local directory, if "into the system" is impossible? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Evolution default browser
by Christopher Myers 13 Nov '17

13 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, I've got Evolution installed on oS Tumbleweed using KDE, and for some reason, it doesn't respect the fact that Firefox is my default browser - -- every link I try to click on opens in Chromium. Is there any way to change things around? I didn't see any option in the configuration for browser choice. I've googled around on and off for a couple of days now and haven't found anything useful. Thanks! -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEE7GM/Dul8WSWn72odQ1nEo4DFCIUFAlm6k/QACgkQQ1nEo4DF CIWfBgf+K9LYvaYDDFUMJtRTMq+58e2lEP5GkXi7dKQhxhFkeKegwqnyo+fEfpvb RI1FT2aJAqBKsIZ5oZlxsGeJYcmp/+JO7AJ6Oa8XkWz02rmhgXjKPxqQgzQX87FM rNGqxOLXfcKu+CmcMERZswTQ/B/ZtA82eUls6Y5W7lIh2tAUbt2CnFP/6q5uM4wl pO2KNbcVJTTM2uEPSzEIBCQ/7jfZ9ogF+qIClPkn1UCmu3EqkLAhS+cdKzzJs+Cx pXyosNImtxW4FMl6W+m2NS08RCc69+U3Myr9aDe8q8/2fnM/HYApeezDsIpKkdnO t2Nr2WaxarbwUyqt15vTiNs0Q229jg== =joxc -----END PGP SIGNATURE-----

4 8

[opensuse] locale handling via ssh
by Carlos E. R. 13 Nov '17

13 Nov '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I handle locale customization via editing the file ~/.i18n. For instance, on my client machine I have: cer@Telcontar:~> cat .i18n # used by /etc/profile.d/lang.sh LC_TIME=en_DK.UTF-8 LC_MONETARY=es_ES@euro LC_NUMERIC=es_ES@euro LC_PAPER=es_ES@euro LC_TELEPHONE=es_ES@euro LC_MEASUREMENT=es_ES@euro LC_NAME=es_ES@euro cer@Telcontar:~> And I get the expected result: cer@Telcontar:~> locale LANG=en_US.utf8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES@euro LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES@euro LC_MESSAGES="en_US.utf8" LC_PAPER=es_ES@euro LC_NAME=es_ES@euro LC_ADDRESS="en_US.utf8" LC_TELEPHONE=es_ES@euro LC_MEASUREMENT=es_ES@euro LC_IDENTIFICATION="en_US.utf8" LC_ALL= cer@Telcontar:~> Now, on a "remote" machine (actually a virtual vmware machine (all running 42.2)) I write: carlos-e@Eleanor-422:~> cat .i18n # # Add user specific LANG and LC_* variables here # LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES # LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT # LC_IDENTIFICATION LC_ALL # # export LANG=en_US.UTF-8 LANG=es_ES@euro # # Override system wide input method here # # export INPUT_METHOD=scim carlos-e@Eleanor-422:~> But when I login (via ssh) I don't get that locale: carlos-e@Eleanor-422:~> locale LANG=en_US.utf8 LC_CTYPE=en_US.UTF-8 LC_NUMERIC=es_ES@euro LC_TIME=en_DK.UTF-8 LC_COLLATE=POSIX LC_MONETARY=es_ES@euro LC_MESSAGES="en_US.utf8" LC_PAPER=es_ES@euro LC_NAME=es_ES@euro LC_ADDRESS="en_US.utf8" LC_TELEPHONE=es_ES@euro LC_MEASUREMENT=es_ES@euro LC_IDENTIFICATION="en_US.utf8" LC_ALL= carlos-e@Eleanor-422:~> That is the locale of the client machine! On a local text terminal I get: LANG=es_ES@euro LC_CTYPE="es_ES@euro" LC_NUMERIC="es_ES@euro" LC_TIME="es_ES@euro" LC_COLLATE="es_ES@euro" LC_MONETARY="es_ES@euro" LC_MESSAGES="es_ES@euro" LC_PAPER="es_ES@euro" LC_NAME="es_ES@euro" LC_ADDRESS="es_ES@euro" LC_TELEPHONE="es_ES@euro" LC_MEASUREMENT="es_ES@euro" LC_IDENTIFICATION="es_ES@euro" LC_ALL= which is the expected result. Why do I not get that via SSH, do I have to do something else? ("man ssh" doesn't have any hit on "locale"). - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAloG+YwACgkQtTMYHG2NR9WunQCgjI33IFBd+yRPk/LlGZRtzGhs 7n0An0ms3WhMxuGQoHRwV9yl7eGCgf20 =m93V -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 10

[opensuse] Failed to start Name Service Cache Demon
by C. Brouerius van Nidek 12 Nov '17

12 Nov '17

At booting I get the info that nscd service failed to start. What to do about it? -------------------------------- extract from journalctl: Nov 12 13:15:59 localhost systemd[1]: nscd.service: Control process exited, code=exited status=6 Nov 12 13:15:59 localhost systemd[1]: Failed to start Name Service Cache Daemon. -- Subject: Unit nscd.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nscd.service has failed. -- -- The result is failed. Nov 12 13:15:59 localhost systemd[1]: nscd.service: Unit entered failed state. Nov 12 13:15:59 localhost systemd[1]: nscd.service: Failed with result 'exit- code'. Nov 12 13:15:59 localhost systemd-logind[986]: Watching system buttons on / dev/input/event0 (AT Translated Set 2 k Nov 12 13:15:59 localhost systemd[1]: nscd.service: Service hold-off time over, scheduling restart. Nov 12 13:15:59 localhost systemd[1]: Stopped Name Service Cache Daemon. -- Subject: Unit nscd.service has finished shutting down -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nscd.service has finished shutting down. Nov 12 13:15:59 localhost systemd[1]: Starting Name Service Cache Daemon... -- Subject: Unit nscd.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nscd.service has begun starting up. Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring file `/etc/passwd` (1) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring directory `/etc` (2) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring file `/etc/group` (3) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring directory `/etc` (2) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring file `/etc/hosts` (4) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring directory `/etc` (2) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring file `/etc/resolv.conf` (5) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring directory `/etc` (2) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring file `/etc/services` (6) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring directory `/etc` (2) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring file `/etc/netgroup` (7) Nov 12 13:15:59 localhost nscd[1013]: 1013 monitoring directory `/etc` (2) Nov 12 13:15:59 localhost systemd-coredump[991]: Process 989 (nscd) of user 0 dumped core. -- Subject: Process 989 (nscd) dumped core -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: man:core(5) -- -- Process 989 (nscd) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Nov 12 13:15:59 localhost systemd[1]: Started Process Core Dump (PID 1014/UID 0). -- Subject: Unit systemd-coredump(a)2-1014-0.service has finished start-up -- Defined-By: systemd -- opensuse:tumbleweed:20171109 Qt: 5.9.2 KDE Frameworks: 5.39.0 kf5-config: 1.0 KDE Plasma: 5.11.2 plasmashell 5.11.2 Kernel: 4.13.11-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

2 1