February 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] old packages
by George from the tribe 19 Feb '18

19 Feb '18

12 46

[opensuse] KMail problem: Decrypting emails does not work as intended
by Kaigue7 19 Feb '18

19 Feb '18

Hi, I'm have an issue with Kmail. Every gnuPGP encrypted email I get won't open corretly. It only shows as two attachments, one PGP/MIME version idenfication and one OpenPGP encrypted message.asc. It works fine in Thunderbird, even though I get a message, that the email "needs to be repaired". Could it be related to incorrect formatting? Like HTML on the sender's side? The sender is using Thunderbird with Enigmail plugin via outlook.com IMAP. Thanks. David -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] X + keyboard freeze, sysrq fun
by Michael Fischer 18 Feb '18

18 Feb '18

Been a while, but I just got hit with the "X, keyboard and mouse all freeze at once" - no getting to another VT. But I could ssh in from another machine. As always when this happens, nothing useable in any logs. Trying to `sudo kill -9 pidof X`, etc.. did absolutely nothing. After a reboot, I went googl'ing for sysrq, which led me to discover that (a) my keyboard is not mapped for it (fixable), (b) /proc/sysrq-trigger would be just fine over ssh and (c) I can't figure out where output of sysrq's like 'l' (backtrace for all CPUS) goes - if only so that I can tell I've got things set up properly. The web says "goes to console", but on Leap, where the heck is that? If it is hidden by X on 1, is there a way to get it into the journal (journalctl)? So, I hereby solicit advice on: 1) clever ways to kill things that are locking up my system from an ssh session 2) clever ways to use /proc/sysrq-trigger, esp. if I can figure out if it is even working... 3) Debugging any of the above. After a dozen of these over the past 5 years or so, with no trace left in logs, I've kind of given up, but hey. TIA Michael -- Michael Fischer michael(a)visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 17

[opensuse] wrong kbd/vtty using mc
by Felix Miata 18 Feb '18

18 Feb '18

OK in 42.3: ● systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled) Active: active (exited) since Tue 2018-01-30 23:03:26 EST; 2 weeks 4 days ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Main PID: 610 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512) CGroup: /system.slice/systemd-vconsole-setup.service Jan 30 23:03:26 00srv systemd[1]: Started Setup Virtual Console. Wrong function key assignments in 15.0: ● systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) vconsole.conf is identical in both. How do I get the same behavior in 15.0 as in 42.3? I see nothing helpful in man page for either vconsole.conf or systemd-vconsole-setup.service. /usr/lib/systemd/systemd-vconsole-setup.service is a fraction of the size of 42.3 in 15.0, 18488 vs 59744. -- "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

1 0

[opensuse] Re: TW partitioner
by Chuck Davis 18 Feb '18

18 Feb '18

I was going to do an install today but when I tried to import mount points from the old install the feature apparently is no longer in the partitioner. I certainly hope that feature is coming back soon....?? Anybody know? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 63

[opensuse] Re: update
by Chuck Davis 18 Feb '18

18 Feb '18

I never was able to get my first machine to update from 20171228 to 201802xx (tried a few versions). So I reinstalled using 20180214 and it's back on track. Fearfully, I updated my development machine today from 20180205 to 20180215 and it went quite smoothly while I held my breath! I even still have a functional desktop after the update. So at least I'm current. Next is my laptop though it is using the Nvidia driver so should go smoothly. This just to confirm that it is apparently "safe" once again to do updates if you're lurking -- at least if you're not still at the end of December like my first machine. Regards. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Ancient History
by Richard Brown 18 Feb '18

18 Feb '18

> On 10 February 2018 at 19:59, Carlos E. R. <robin.listas(a)telefonica.net> wrote: >> Ok, but my system has been upgraded from SuSE 6.2 upwards (ie, it is >> much older than 13.x), so it will not work. And I do not use btrfs, either. SuSE 6.2 was released in 1999 and support ceased for it in 2001 That is 18 and 16 years ago respectively 18 years before SuSE 6.2 was released, IBM PC 5150 was launched (August 1981). This technology was no longer supported by 1999, and was not supported by SuSE 6.2 in any way, manner, or form. 16 years ago, IBM PC XT was launched. This technology was also not supported by 1999 and was also not supported by SuSE 6.2 in any way, manner, or form. I'm legitimately curious how 16-18 years after the release of SuSE 6.2 you can make the quoted statement like it's a 'good thing' you've been able to do that. The best case implies you have an likely endless collection of hacks and workarounds to handle the winds of time that have no doubt ravaged that system over those years. Your system heralds from an era of the Melissa and ILOVEYOU viruses, of a time before the HTTP/1.1 standard was written, of Windows XP and KDE 1.1.1. When ext3 was the new filesystem on the horizon scaring the shit out of people. I can only imagine the collection of digital crud that are cluttering up forgotten parts of the filesystem on a system that old. I think it might be valuable to a museum, but I honestly cannot understand how anyone could possibly want to run a system that is so encumbered with ancient history. What benefit do you think you get from such an approach to computing? How do you think someone running an IBM PC 5150 in 1999 would have been seen by the people developing Linux 2.2 and SUSE 6.2? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 30

[opensuse] Leap 42.3 and Coffe Lake?
by Peter Suetterlin 16 Feb '18

16 Feb '18

Hi list, I wonder if someone here has experience with running 42.3 on Coffee Lake hardware. The MB of our server is having issues, and a (possible) replacement is an ASRock Fatality Z370 with an i7-8700. Are there known issues with the 4.4 kernel and Coffe Lake CPUs? I know the onboard graphics isn't working with Mesa 17, but I don't really care, its a server and runs text mode anyhow. The board also has a 10G card using the 'atlantic' kernel module that is not (yet) there in the 42.3 kernel. I can also live without that (for now). I'm running the board with TW at the moment, and that seems to work nicely (including graphics and 10G), but I'm not going to run TW on a server. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] /var/log and btrfs on Leap 42.3
by Roger Oberholtzer 16 Feb '18

16 Feb '18

I have a Leap 42.3 system that was working fine. I started a zypper dup, and part way through, it started complaining that there was no space on /var/log. This is not true. There are a couple of GB free on the /var file system. Still, I deleted a couple of log files to see what happened. The files deleted fine, and the free space as reported by df increased ad expected. However, I cannot write anything to /var/log. If I just try to touch a new file it complains that there is no free space on the device. I have rebooted, but the problem persists. The setup is btrfs as Leap 42.3 set up. Until this, all has been working great. When you cannot write to /var/log or such places, lots of system stuff no longer starts. So even though I can log in, all is rather basic. If this was the old ext4, I would run fsck. I have to admit that the options with btrfs are less clear to me. I have tried the suggestions here: https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_get_.22No_space_left_… When I run "btrfs fi balance start -dusage=5 /mount/point", no chunks are relocated. So I tried increasing the usage= value. When I hit 70, it complains that there is no space left on the device. So this seems not to be able to solve the problem. I cannot get it re reallocate a chunk. I have also checked here: https://www.suse.com/documentation/sles11/stor_admin/data/trbl_btrfs_volful… It suggests pretty much the same thing. I have not tried removing a snapshot. I would only expect that to help when there is actually no free space. But that is not the case. I do not want to destroy this system It is my work system. I'm open to suggestions. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 9

[opensuse] Display managers...
by Roger Oberholtzer 16 Feb '18

16 Feb '18

Recent versions of openSUSE have been using the sddm display manager as the default one. I think it looks and acts okay. Unfortunately, it does not work with XDMCP. So running rdesktop against such a system is not possible. I need to access the systems via something like rdestop. We have enabled kdm instead. It does work. But I think it is butt ugly. Is it really the case that it should be a gray screen with a gray Gecko? And a field in which you enter the name, and after pressing enter get a new field for the password? And that has a useless (IMHO) console window both during the login and after KDE starts? Not looking very impressive. Perhaps I have missed something that looks better? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5