January 2015 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42
by grantksupport＠operamail.com 22 Jan '15

22 Jan '15

On Wed, Jan 21, 2015, at 05:47 PM, Patrick Shanahan wrote: > * grantksupport(a)operamail.com <grantksupport(a)operamail.com> [01-21-15 20:24]: > > On Wed, Jan 21, 2015, at 05:10 PM, Patrick Shanahan wrote: > > > an answer to this question/demand was posted to list in the last several > > > hours. The zypper package was "broken" and slipped bye. > > > > Thanks. > > > > For anyone interested, found it here: http://lists.opensuse.org/opensuse/2015-01/msg00612.html > > > > Imo, we have too many lists, &/or no clear guidance/policy where breakage like this is announced; you'd think that if a patch/update is announced on opensuse-updates, then any change/breakage/rollback to it should also be posted there. > > > > Also re-raises old questions of why/how it's allowed to push & publish updates before a stable, non-broken state is verified, AND that once done, there's no "current-1" snapshot, or other backup, to rollback to. Other topics ... > > You do realize that your post is private, not to the list, or both lists > against list netiquette. > > You do realize that your post is private, not to the list, or both lists > against list netiquette. Seriously? Well, gee-willikers -- my bad for just clicking "Reply to all ..." oh wait. Then again -- maybe you shouldn't have first responded to ME only "against list nettiquette": ------ Return-Path: <ptilopteri(a)gmail.com> ... Date: Wed, 21 Jan 2015 20:10:53 -0500 From: Patrick Shanahan <ptilopteri(a)gmail.com> To: grantksupport(a)operamail.com Subject: Re: [opensuse] please replace/repair the packages made previously availble in patch openSUSE-2015-42 Message-ID: <20150122011053.GC3960(a)wahoo.no-ip.org> Mail-Followup-To: grantksupport(a)operamail.com References: <1421886690.4030279.217141201.0F8A1C99(a)webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1421886690.4030279.217141201.0F8A1C99(a)webmail.messagingengine.com> X-Operating-System: Linux 3.11.10-25-desktop x86_64 openSUSE 13.1 Organization: Ptilopteri in Pandemonium User-Agent: Mutt/1.5.21 (2010-09-15) X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 ------ How's that? better ON the list? Wow ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] zypper went backwards?
by John Andersen 21 Jan '15

21 Jan '15

In Yast today, I noticed that Zypper (and friends) is in red (newer than what is available) Alternate Version Installed Version 1.11.14-2.1 1.11.17-5.1 I haven't changed repositories since many months. Why is this going backwards in version numbers? -- 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

2 3

[opensuse] Accessing a USB-disk as normal user
by Koenraad Lelong 21 Jan '15

21 Jan '15

Hi, This is not the first time I experience this, but now I wanted to ask. I formatted (EXT4) a new disk in a USB-to-SATA enclosure. All is fine. But when it is mounted via the "tray", I can't access it, I don't have rights to write on the disk. What I'm doing now is adding a directory as root and chowning that directory to my user. Then I can use that directory as storage. Is this the way to go or am I missing something ? On OS13.1. Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 15

[opensuse] Cursor disappears, inactive on new windows or edit boxes
by vincent＠webfresco 21 Jan '15

21 Jan '15

Cursor disappears and seems not to know where it is supposed to be -- or which window or position or input boxis supposed to be active. I just installed 13.2, KDE. Example: I opt to open a shell window. Formerly, it opened with the cursor active. Now it opens with the cursor blank (in outline form) and I have to click my mouse to activate the cursor and window. As I am typing along, the cursor will frequently go blank, and I have to click my mouse to reactivate it. This wreaketh havoc with my attempts at speed typing ... Often, but not always, a little search box widget pops up at the top of the window. I'm using KDE, but with some gnome programs like evolution. That little popup search widget looks like something associated with gnome. But again, that does not happen every time. My most frustrating experience was trying to type in a password ... Progress/typing/etc. stopped multiple times. I tried reinstalling 13.2 after that. Didn't help. I can't figure anything in particular that triggers the disappearance. Sometimes it just disappears while I'm not doing anything. I have watch that vi cursor just go blank while I'm thinking what to type next. >From what looking around I've done, I get the impression mine may be a driver conflict, but I don't know how to resolve that. Thanks for any help. Kathy -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] 13.1 pam obstacle (was: missing services)
by Felix Miata 20 Jan '15

20 Jan '15

Samba (nmb and smb) I got working following reinstallation of samba and systemd, then enabling with systemctl. Joe Zappa composed on 2015-01-19 10:38 (UTC-0500): > Don't run telnet server on any host that can be accessed by telnet connection > initiated from any host outside of your control. We've been through security preaching ad nauseum before, something like 30-40 posts in just one thread: http://lists.opensuse.org/opensuse-factory/2014-06/msg00234.html Admonitions are precisely why this has been taking me so long, as searches produce preaching abundantly supplied by Google, instead of answers to questions asked. IIRC that thread includes somewhere the why of my wish to use telnet rather than sshd, and a consequent response stream that sshd supposedly isn't that "hard" even when dealing with 12+ installations per HD. On my LAN, all installations are under my control. Windows is rarely used. This is on a test box. It gets little use. I want telnet server to work on it. Telnet server is installed, but my attempts to get it enabled, via xinetd as that's apparently how it's supposed to work on systemd systems, were producing no fruit, unlike on Fedora on the same box. It was so late and I was so tired last night when I gave up I can't remember how I finally enabled xinetd and got past connection refused starting a telnet client. Looking at bash history it may have been systemctl enable telnetd.socket and/or systemctl enable xinetd.socket, after reinstalling telnet-server. At this point I can bring up a session prompt with telnet client, but pam has apparently become the obstacle I'm not getting figured out. It accepts non-root login, but not root. As on most of my test installations I don't even create non-root users, and sometimes need some things to work without /home mounted, I want to know how to enable root to login. Until https://bugzilla.opensuse.org/show_bug.cgi?id=833253 I never even knew pam existed, much less how to customize it, while pam's man page isn't even 2 screens long. The man page refers to /etc/pam.conf, but this file does not exist. /etc/pam.d/ exists, but has over 50 files in it that the man page says nothing about. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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

4 7

[opensuse] Need help investigating KDE lags after boot
by Stanislav Baiduzhyi 20 Jan '15

20 Jan '15

Thinkpad T540p, openSUSE 13.2, KDE4, wicked, only couple of additional repositories, like KDE:Qt5, KDE:Extra. Autologin option selected during installation. Last week KDE started behaving strangely. I thought that was the result of some service changes (nm was starting slowly, so I moved nm and wpa_supplicant to forking), made full reinstall yesterday (no nm this time, wicked only), but still seeing the same behaviour. Cannot see anything interesting in logs. Symptoms: * after the boot, for two-three minutes KDE is absolutely unresponsive. * in two-three minutes, notifier that USB mouse is detected so touch pad can be disabled appear. * after that notifier, kwin shortcuts to move between virtual desktops are up. * takes another minute before application launching shortcuts starting to work. * when apps are launched before that time, they are mostly hanging in there, actually starting only when system becomes responsive again. Before the reinstall, I was almost sure that it is caused by dbus. Attempt to change shortcut to launch konsole actually crashed systemsettings, printing some dbus-related timeout messages before that. Now I cannot reproduce it because I cannot start anything before lags are finished. As I cannot find any indication in logs on what is happening, I will greatly appreciate any suggestions how to increase logging levels or do some concrete queries from text console, or anything else that will help to find a cause of those lags, as it is extremely annoying. -- Regards, Stas -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Re: [security-announce] Upcoming update for shim requires confirmation on reboot
by jdd 19 Jan '15

19 Jan '15

Le 19/01/2015 09:21, jsegitz(a)suse.de a écrit : > On Fri, Jan 16, 2015 at 05:18:27PM +0100, jdd wrote: >> just for the record, is it possible to have secure boot in a VM? > > It is, but it is very unlikely that you will encounter that. > http://blog.hansenpartnership.com/uefi-secure-boot/ that's good, thanks. In fact there is no use right now, apart experimentation, but in a very near future, when uefi will be standard, legacy boot may be deprecated thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Limiting memory usage via cgroups
by Carlos E. R. 19 Jan '15

19 Jan '15

You forgot to email to the list. On 2015-01-19 11:59, Andrea Turrini wrote: > 2015-01-18 21:35 GMT+08:00 Carlos E. R. <>: >> On 2015-01-16 09:11, Andrea Turrini wrote: >> >>> The problem of ulimit is that it limits the virtual memory, not the >>> resident one, >> >> Not true. ulimit is a bash internal command, so man ulimit explains it: >> >> -m The maximum resident set size (many systems do not honor this >> limit) > > The practical result is that it has no effect on the resident memory. > And anyway I don't think that ulimit permits to limit the actual used > memory. I don't know (or remember) if "-m" works or not, but the option exists. I use "-v" to catch some applications prone to runaway (kbabel). -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

1 0

[opensuse] 13.1 missing services
by Felix Miata 19 Jan '15

19 Jan '15

Grepping for smb, nmb and telnet through systemctl list-unit-files and systemctl list-units produce nada, even though packages providing them are installed. All are missing from chkconfig -l output too. Smb & nmb produce inactive (dead), telnet not-found. What have I forgotten or missed for finding or changing services from cmdline? Is systemctl broken in 13.1? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (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

5 8

[opensuse] Limiting memory usage via cgroups
by Andrea Turrini 19 Jan '15

19 Jan '15

Hi all, I'm facing a strange problem with cgroups in my openSUSE 13.2 fully updated with kernel 3.16.7-7-desktop. I run some experiment with a tool that sometimes takes a lot of memory; for my purposes, I consider the experiment failed if it takes too much memory or too much time. To limit its memory consumption, on oS 13.1 I used to create a cgroup via the commands: mkdir /tmp/experiment mount -t cgroup -o memory memory /tmp/experiment mkdir /tmp/experiment/test echo 8G > /tmp/experiment/test/memory.limit_in_bytes echo 8G > /tmp/experiment/test/memory.memsw.limit_in_bytes echo experiment_shell_PID > /tmp/experiment/test/tasks and then from the shell with PID experiment_shell_PID I can run my experiments on several files without problems. Now, with oS 13.2, the memory.memsw.* part is missing, so when the tool requires more than 8Gb of memory, instead of being killed as in oS 13.1, it starts to swap until it takes the whole swap (20Gb) or it is killed by timeout. As a workaround, I tried to disable the swap via "swapoff -a" but it works only for at most 15 minutes since then swap is re-enabled automatically. How can I get the oS 13.1 behavior back in oS 13.2? Best, Andrea -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 18