March 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Which Firefox/SeaMonkey tabs are using CPU cycles?
by Philip Amadeo Saeli 12 Mar '15

12 Mar '15

OpenSUSE-13.1 Anyone know how to determine which Firefox/SeaMonkey tabs are using up the most CPU cycles? I frequently have the case where I have many browser windows open, each with many tabs, and the browser is pegging the CPU usage to 100% on at least one CPU core and the browser becomes very sluggish. Often I am able to manually look thru the displayed pages and find the CPU hog and kill it, returning things to a more normal state. However, rather often I have not been able to do so given time and work constraints. I have found quite a bit of diagnostic info in the various Mozilla about:* pages, but nothing WRT CPU usage. Also, since it runs in a single process, ps/top/etc do not help here either? Any ideas? Thanks! --Phil -- Philip Amadeo Saeli psaeli(a)zorodyne.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 4

[opensuse] 13.2 upgrade, preserving 3rd party packages
by Michael J Dur 12 Mar '15

12 Mar '15

I have a laptop running 13.1 (fully updated). I'd like to upgrade to 13.2 by updating the repos and performing a zypper dup. When I run this the system wants to change vendor and downgrade dozens of packages installed by packman. I confirmed I have the default for change vendors, which is false, but I tried setting this explicitly with no effect. I'm concerned downgrading packman packages will break the few multimedia things I have installed. Here are the repos I'm using: # | Alias | Name | Enabled | Refresh ---+---------------------------+------------------------------------+---------+-------- 1 | erlang | erlang | Yes | Yes 2 | google-chrome | google-chrome | Yes | Yes 3 | packman-essentials | packman-essentials | Yes | Yes 4 | packman-multimedia | packman-multimedia | Yes | Yes 5 | repo-debug | openSUSE-13.2-Debug | No | Yes 6 | repo-debug-update | openSUSE-13.2-Update-Debug | No | Yes 7 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | Yes 8 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | Yes 9 | repo-oss | openSUSE-13.2-Oss | Yes | Yes 10 | repo-source | openSUSE-13.2-Source | No | Yes 11 | repo-update | openSUSE-13.2-Update | Yes | Yes 12 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | Yes The 13.2 repos were changed from 13.1 using sed. Does anyone have any suggestions? -Michael -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] 13.2/x64: xorg x11 server update, via zypper: xorg.conf exists and xorg.conf.sle11 does not
by cagsm 12 Mar '15

12 Mar '15

13.2/x64: xorg x11 server update, via zypper: xorg.conf exists and xorg.conf.sle11 does not Installing: xorg-x11-server-7.6_1.16.1-13.1 .................................................................[done] Additional rpm output: Updating /etc/sysconfig/displaymanager... xorg.conf exists and xorg.conf.sle11 does not -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: [opensuse-marketing] openSUSE on Bad Voltage
by Douglas DeMaio 12 Mar '15

12 Mar '15

> > For oSC15: it likely won't happen. Even if it made sense for the > conference (and there is space for it in the schedule) we probably won't > have the time to pull together the needed sponsors to cover the airfare (we > did it many months in advance for SCALE) and schedule it with the crew. > But doing a live show at a future oSC would be absolutely awesome. > > On the topic of the openSUSE review on the next episode: It would be > awesome to get someone on the next episode to talk about openSUSE. Maybe > Richard Brown or Doug DeMaio or... someone else? It would be a roughly 10 > to 15 minute chat about openSUSE history and, in general, talking about > what's great about it. Thoughts? Hi Bryan, I'll be snowboarding in the Alps at 2,300 meter with patchy wifi and a bunch of beer for the next week and a half. Don't hate on me too much. I recommend Andrew Wafaa do the interview on this occasion and that Richard be the secondary choice. cheers Doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: [opensuse-marketing] openSUSE on Bad Voltage
by Henne Vogelsang 12 Mar '15

12 Mar '15

Bryan, On 11.03.2015 19:16, Bryan Lunduke wrote: > we probably won't have the time to pull together the needed sponsors to > cover the airfare With openSUSEs travel support program[1] covering airfare happens faster than you can say Tomato juice! The money part of the equation shouldn't be an issue, would that make it more likely? Henne [1] https://en.opensuse.org/openSUSE:Travel_Support_Program -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] mariadb logs being written to /var/lib/mysql/hostname.err ??
by Per Jessen 12 Mar '15

12 Mar '15

See also bug#840079. I have a mysql plugin that writes debug/status messages to stderr, so I went to look for the logfile - in previous versions, this was configured as /var/log/mysql/mysqld.log. It used to be configured in my.cnf, section [mysqld_safe], but that has been removed and the logfile is now configured as a startup argument: --log-error=/var/lib/mysql/<hostname>.err This would appear to be caused by the [mysqld_safe] section having been removed from my.cnf? -- Per Jessen, Zürich (5.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] making swapfile on 3.2
by don fisher 11 Mar '15

11 Mar '15

I have tried to make a swapfile since my system currently swaps to another drive that I wish to remove. I used the commands: fallocate --length 16GiB swapfile to make a file with no holes mkswap -c -L swap0 /home/swapfile mkswap: /home/swapfile: warning: wiping old swap signature. Setting up swapspace version 1, size = 16777212 KiB LABEL=swap0, UUID=5ae6fd77-4892-4388-902b-ba81181dc255 swapon -v /home/swapfile swapon /home/swapfile swapon: /home/swapfile: found swap signature: version 1d, page-size 4, same byte order swapon: /home/swapfile: pagesize=4096, swapsize=17179869184, devsize=17179869184 swapon: /home/swapfile: swapon failed: Invalid argument Exit 255 I do not know how to translate the "Invalid argument". This used to work, but it has been awhile since I did it. Did I leave something out? The mkswap check is: mkswap -c -L swap0 /home/swapfile mkswap: /home/swapfile: warning: wiping old swap signature. Setting up swapspace version 1, size = 16777212 KiB LABEL=swap0, UUID=56ba4a10-cdcf-48d3-ba58-0a5f61807c60 Nothing appears wrong here. I used journalctl and could not find any info. But dmesg says: [ 2887.519535] swapon: swapfile has holes. I guess I need to know more journalctl. I though it was as replacement for var/log/messages, which always had the dmesg output. So how does one make a swapfile with no holes? The manpage for mkswap implies that fallocate, over cp, is a better way. Please advise. Thanks don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

18 91

[opensuse] sistemad and console messages ?
by Per Jessen 11 Mar '15

11 Mar '15

I'm pretty certain I saw someone ask this only recently - a) why do I get console messages always written to the current console? b) how do I direct to only vty10 where they used to be? Having them follow one around and continually interrupt whatever one is doing is very annoying. -- Per Jessen, Zürich (2.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 21

[opensuse] how do I override a sistemad timer ?
by Per Jessen 11 Mar '15

11 Mar '15

I want to disable/override /usr/lib/systemd/system/logrotate.timer - how is that best done? (apart from deleting the file). -- Per Jessen, Zürich (8.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

Re: [opensuse] back to the 'fix this eternally broken temp file cleanup service' debate
by Peter 11 Mar '15

11 Mar '15

On 19/02/15 16:56, Joe Zappa wrote: > Peter wrote: >> Bonjour. >> >> This is now driving me mad. Just over a year ago (I had to go hunt >> down the thread, here: >> http://lists.opensuse.org/opensuse/2014-01/msg00988.html) the issue >> was once again raised of why temp files were not being cleaned at boot >> (on openSUSE 13.1) if one tried to set the system to do so. >> >> It was established that the cron job configurable from YaST's >> sysconfig editor was no longer functional since supposedly being >> replaced by the all-round saviour and >> tuck-your-sheets-in-would-you-like-a-cup-of-hot-cocoa-with-that >> princess that is systemd. Except that the replacement doesn't work. At >> least not on any of my 13.1 installations, whereupon both /tmp and >> /var/tmp become laden with relics that outright refuse to ever part my >> system, gradually filling my root partition until there is no more >> room for maneouvre. Currently my /tmp is sitting at 5GB. Looking at >> files in there, many are up to a year old. It seems to just accumulate >> stuff like an eccentric lonely old man with an attic. This was a fresh >> 13.1 installation made about a year ago. The root partition (ext4) is >> 17GB, about half of which was filled after installation. Now there's >> little left. >> >> It was also established that SuSE likes to do its SuSEy thing and go >> its own way, against systemd defaults, in preserving temp files across >> reboots, since some SuSErs want their systems configured that way and >> consider /tmp to be a persistent directory. >> > > I've just given up > > Now, when I reboot my machines, I log into root and run a shellscript > that I call "start" > which I wrote to do any and all initializations which I USED to put in > in /etc/init.d/local.initializations and then link to from rc{2,3,5}.d > directories > as S99local.initalizations. > > But since systemd completely and utterly fucking ignores /etc/init.d/*, > that's out the window. > So is /tmp filling interminably for all users of 13.1 who haven't otherwise fiddled with something to prevent this, or who don't have /tmp stored in RAM? I don't understand if this is a universal issue/bug or it's only affecting certain users, such as those not using btrfs for example. Google searches aren't throwing up much in the way of openSUSE, only similar issues affecting various other distros. I don't know what more I can do to empty my /tmp and /var/tmp aside from simply rm -rf /tmp. I'm reluctant to do that as a last resort because I had problems long ago on this same system after emptying temp, although admittedly I stupidly did that whilst running as user with x. Doing some more plugging I found that systemctl -l status systemd-tmpfiles-clean.service was throwing up a failed message concerning gvfs. Thinking this might be preventing the service from running, I found a thread on the Arch bug tracker (https://bugs.archlinux.org/task/32715) which suggests a workaround for this being to create a file, /etc/tmpfiles.d/gvfs.conf containing, essentially: x /run/user/* to stop systemd going near /run/user at all. Well that changed nothing on my system. I've tried manually running systemd-tmpfiles --clean --remove but again, though it doesn't return an error, nothing is cleaned up or removed. I also notice when running systemctl -l status systemd-tmpfiles-clean.service the lines: Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static) Active: inactive (dead) It seems to always be inactive. Meanwhile, running systemctl -l status systemd-tmpfiles-setup.service I get this: systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since Sat 2015-02-21 20:17:27 CET; 2min 4s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 356 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --exclude-prefix=/dev (code=exited, status=0/SUCCESS) Main PID: 356 (code=exited, status=0/SUCCESS) And I've no idea how to go about setting /tmp to store files for 30 days and /var/tmp for 90 like in the good old days, because there's clearly not much point even tinkering with that idea until I can get the service to run at all. The documentation (man page) for systemd-tmpfiles is awful and tells me nothing useful. I still have 2.5GB to fill on my root partition. I'll keep waiting. Before long I'll have to do something. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 45