April 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Bug fixes in opensuse are somewhat of a bad joke nowadays...
by David C. Rankin 13 Apr '18

13 Apr '18

What Removed Added ----------+----------+---------- status NEW RESOLVED ----------+----------+---------- Resolution --- WONTFIX ----------+----------+---------- Comment # 8 on bug 924818 from Tomáš Chvátal This version of openSUSE changed to end-of-life (EOL [1]) status. As such it is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of openSUSE, or consider the bug still valid, please feel free to reopen this bug against that version, or open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -------------- Thanks -- that really helped. -- 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 6

[opensuse] leap 15
by jdd＠dodin.org 12 Apr '18

12 Apr '18

hello, is this now the right place to ask about leap 15? I don't want to add factory to my already too large subscription list :-( thanks jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Late to Game, but finally moved to 42.3, clean install a bit awkward, but completes fine.
by David C. Rankin 11 Apr '18

11 Apr '18

All, I finally moved my laptop to 42.3 (even though I booted 42.2 here, because I haven't finished the hours of config still to come...), but nonetheless I have a blazing Leap_42.3 install with a fresh KDE3 desktop, all on 500G of Samsung SSD -- and yes -- the speed difference (especially compiling) is very noticeable. All in all the Leap 42.3 install was.. cumbersome, frustrating, took a bit of coaxing to install what I wanted installed and not what I didn't want, but it worked just fine. The cumbersome part was the inability to add repos prior to the install (or at any point during). This was compounded by the truly insane default partition scheme suggested using btrfs for a user-laptop?? We have dumbed-down the desktop to the point of file managers that have a shadow of the capabilities they provided a decade ago so they are "easier for the new user", but now we somehow expect the newbie to master an enterprise level filesystem notorious for snapshotting all usable space into oblivion? I guess the really smart people see the logic in that, but that logic just escapes us lesser mortals... The good parts of the install, after nuking the btrfs suggestion and the secondary non-native XFS suggestion and dropping back to the wasteful old ext4 that has never lost a file for me in a decade, the remainder went great. Both wired and wireless Intel 82579LM Gigabit Network Connection (wired) and Intel Centrino Ultimate-N 6300 (wireless) -- so kudos to that. A bit more of the cumbersome was completing the entire install in text mode with minimal yast modules present as the frustrating part of the install provided no KDE3 pattern, despite providing every other minor semi-maintained option of enlightenment, lxde, mode, cinnamon, icewm, windowmaker, etc.. You guys have a fantastic option in KDE3 that installs flawlessly, there is no reason not to have a patter for it for install. (enlightenment but KDE?) If you go this route, at least install the X-server and icewm so you will get the full yast. Even installing xterm, firefox, LibreOffice, etc.. still did not pick up the X-server dependency leading to needing to complete the install via out old buddy the yast2 interface (which is quite fine). The other slightly frustrating part (which has been there since at least 7.0) is clicking of a repo and.... waiting while the package info is loaded (and reloaded each time you move up/down the repo list) That and the 'tab-order' of all the text mode controls obviously haven't been revisited since the 10.0 days despite the letters changing. (tabbing reminds me of a pinball machine -- with no hope of shift-tab actually backing up to the previous pane) All-in-all other than the btrfs, awkward desktop pattern selection, and no X-server dependency -- there is not much to complain about. There was no fuss on the network-install connection or package retrieval, it just worked, there are some dependency issue when selecting packages without packman and/or videolan configured. The last surprise was the missing convenience directives in /etc/pam.d/su that no longer provided an easy uncomment to allow users of 'wheel' to su without a password, e.g. # Uncomment the following line to implicitly trust users in the "wheel" group. auth sufficient pam_wheel.so trust use_uid # Uncomment the following line to require a user to be in the "wheel" group. auth required pam_wheel.so use_uid ... the removal may be a security enhancement, but thankfully I have a ssh client on my phone that I could jump on an older install and get the details (heaven know I didn't recall the specifics) Maybe next time I'll take the less painful route of upgrade, but I've done a clean install of every release (other than those I skipped when we were on the 6-month rapid-fire rabbit-pellet release cycles) back in the good ole days (when that steel-trap type logic reared it head in the name of progress) So now I sit with the shiny new ssd as sda and this old platter as sdb in my laptop, just wait to finish the bulk of the install by mounting the other under /mnt and rolling all the needed files and configs back over. (and tweaking the users/groups, etc.) That will be as a time-allows project over the next few days. So good job again. Leap 42.3 installs just fine. Other than the somewhat ironic logic of making things easier for new users while feeding them btrfs there were really no hiccups in the network install. (that speaks well, I don't think I've had a serious install problem in 15 years, sure there are things that could be made better, but the installer still mows the grass) -- 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

9 43

[opensuse] Its NOT supported
by John Andersen 11 Apr '18

11 Apr '18

But it worked for me. I upgraded from 42.2 directly to Leap 15 without installing 42.3. (Took an extra backup before I started). Everything worked fine. System boots fine, and seems as responsive as ever. (Its an SSD system). There were some dependency conflicts to resolve and I carefully selected the option to switch back to Opensuse packages for almost all the multimedia things I had installed from Packman. (as I've been assured here on this list that Opensuse has ceased sending crippled packages and all those issues are handled like every other distro - it just works). This may have been an error, as I can't get any video to play. Music does play. I'll hunt down this problem later. I half expected this to be the case anyway). The upgrade loaded a boatload of texlive stuff that I did not previously have, and have no use for, but I can clean that up later. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

12 45

[opensuse] how to install viber7 on oS or TW
by Oszkó Albert 11 Apr '18

11 Apr '18

Hi all, I tried to install viber the other day on my laptops, but I met some missing dependencies - like libcrypto.so libssl.so and libpng.so named file. There are files with similar names in /usr/lib64. I tried to soft link them to the names that are expected, but without success. So how to proceed? Thanks, Albert

4 5

[opensuse] Transferring LVM
by suse＠a-domani.nl 11 Apr '18

11 Apr '18

Hi, Coming week, I'll try to transfer to a more recent virtualisation server and install it with more up-to-date platform (12.3 => 42.3) My XEN-clients (SLES) are all stored in LVM's What would be the most efficiant way to transfer them from one piece of iron to another? After I create new LVM's, can I 'dd' them over the network? from node1:/dev/data/minoss-servers ==> node2:/dev/data/minoss-servers Hans -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] Doevecot Imap Really Slow with Recent Updates
by Charles Philip Chan 10 Apr '18

10 Apr '18

Hello all: There seem to be a permission problem with Dovecot in recent updates that leads to really slow operations. This is what I see in the journal log: ,---- | Apr 10 01:19:11 karnak dovecot[2406]: master: Fatal: execv(/usr/lib/dovecot/stats) failed: Permission denied | Apr 10 01:19:11 karnak dovecot[1925]: master: Error: service(stats): command startup failed, throttling for 60 secs | Apr 10 01:19:11 karnak dovecot[2406]: stats: Fatal: master: service(stats): child 14755 returned error 84 (exec() failed) `---- The permissions for stat seems to be OK: ,---- | -rwxr-xr-x 1 root root 27240 Mar 29 07:24 /usr/lib/dovecot/stats `---- Have anyone else experienced this and is there a quick fix? Thanks. Charles

3 3

[opensuse] zypper addrepo - http:// vs. https://
by Per Jessen 10 Apr '18

10 Apr '18

I'm sure someone has a quick explanation: a) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…' This fails: Download (curl) error for 'https://download.opensuse.org/repositories/Virtualization:containers/openSU…': Error code: Bad URL Error message: Protocol http not supported or disabled in libcurl b) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:/containers/openS…' Works fine. (notice the extra slash between 'Virtualization:' and 'container'. c) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:containers/openSUS…' d) zypper addrepo 'http://download.opensuse.org/repositories/Virtualization:/containers/openSU…' Both work fine. -- Per Jessen, Zürich (9.1°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

7 13

[opensuse] File/folder permissions that does not make sense to me!
by Marc Chamberlin 09 Apr '18

09 Apr '18

I wonder if some kind guru could explain this logic to me or direct me to an appropriate users group... I have a mixed SOHO network in my home with both Linux and Windoz systems running on it. I use autofs to automount Windows folders on my Linux systems and for the most part I don't have any issues. But one thing that has been perplexing me is why I could not copy files from say my Linux laptop to my Windows system at the C:/Users/marc/Documents folder. (I automount C: using autofs under /mnt/samba/windowscomputername/C so I can have access to the entire drive from my laptop) What really perplexed me was that I could copy files to any subfolder under C:/Users/marc/Documents such as to C:/Users/marc/Documents/tmp/newfile. My instincts told me there had to be some sort of permission problem that I had to resolve on the Windows system. So I tried everything I could think of to relax the permissions so that anyone and everyone could access the Documents folder, but to no joy. It finally occurred to me to try and take a look at it from the Linux side, so using Dolphin I examined the permissions of the Documents folder and sure enough Dolphin was reporting that I only had read permissions on the Documents folder. So on a lark I decided to try and change the permissions via Dolphin (chmod also behaved the same way) to give me read/write permissions and I will be damned if that didn't work! But I will be twitched if I can understand why in the world that worked and why I have to give myself permission to write to the Documents folder on a Windows system, from/on the Linux system side also! Shouldn't file permissions and access be strictly governed by the system that owns the files and folders? Why does a Linux system user have to give himself/herself permissions in order to write to files on a different system? This is effectively saying that in order to write to a file system on another computer I have to give myself permission to do so on BOTH systems! In other words, it wasn't Windows that was blocking me from writing to the Windows file system from my Linux laptop, it apparently was Linux itself! Is there some weird magic about Documents folders on Windows systems? Doesn't make any sense to me... Just to be certain, I took a look at the folder permissions, under Windows, both before and after making the permission change on the Linux system, and I could not see any changes so this appears to be strictly a Linux side permissions issue... Marc.... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 12

[opensuse] Please show your output from "ls -l /bin/vim"
by ken 09 Apr '18

09 Apr '18

What boffoness is this!? $ whereis -b vi vim vi: /usr/bin/vi /bin/vi vim: /usr/bin/vim /bin/vim /usr/share/vim $ ll /usr/bin/vim /bin/vim /usr/bin/vi /bin/vi lrwxrwxrwx 1 root root 3 Mar 24 02:10 /bin/vi -> vim -rw-r--r-- 1 root root 2363952 Jul 2 2017 /bin/vim lrwxrwxrwx 1 root root 8 Mar 24 02:10 /usr/bin/vi -> /bin/vim lrwxrwxrwx 1 root root 8 Mar 24 02:10 /usr/bin/vim -> /bin/vim In short, everything is a symlink to /bin/vim, but /bin/vim doesn't have execute permissions. Why/How can this be? Does anyone else have this utter strangeness? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 14