December 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] clamav anti-virus : omni.ja
by ellanios82 24 Dec '16

24 Dec '16

Hello List , - have notified clamav that Thunderbird will not run, without omni.ja - currectly omni.ja is identified by clamav as 'infected' positive ........ greetings ellan ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] clamav anti-virus : omni.ja
by ellanios82 24 Dec '16

24 Dec '16

Hello List , - have notified clamav that Thunderbird will not run, without omni.ja - currectly omni.ja is identified by clamav as 'infected' positive ........ greetings ellan ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] New Generation HHDs in RAID arrays [Was:using "surveillance"' disks in a raid set]
by Greg Freemyer 24 Dec '16

24 Dec '16

Starting over on this topic. While I wasn't looking HDDs got a major make-over and its a drastic change. This applies only to 5TB and bigger drives from what I can see at this point. And not all of those. Anyway, I looked further into what makes a surveillance HDD different from other types. To my surprise, in the large disk (6/8/10 TB) market Seagate now offers: - Archive HDDs - Surveillance HDDs (Skyhawk) - NAS HDDs (IronWolf) - Performance HDDs (Barracuda) The reason seems to be they are incorporating SMR (shingled magnetic recording) storage tech. This youtube video does what looks like a good explanation of SMR starting 4 minutes in: https://www.youtube.com/watch?v=CR_bfbOTY1o But he doesn't explain that SMR isn't used on 100% of the platter. If it were done, half the entire drive would have to be rewritten with every write. ie. when a SMR sector is written it corrupts one of the sectors next to it. When you re-write the corrupted sector, it corrupts the next one, and before you're done fixing the corruptions you've rewritten half the drive to just write one sector in the middle of the drive. Per http://www.anandtech.com/show/10470/the-evolution-of-hdds-in-the-near-futur… the new Seagate drives are interlacing SMR sections of the platter with traditional perpendicular recording. Every time a sector in a SMR region is written, the corruption in that entire SMR has to be fixed, but the corruption process ends at the edge of the particular SMR zone. The "Archive HDDs" have highest ratio of SMR to perpendicular. In some cases a sector write can apparently take up to 20-seconds to complete because the SMR zones are so big and a write at the start of the zone would force a very large part of the SMR zone to be re-written. For some (most? all?) SMR drives, they have a portion of the platter used as a write cache. Let's say 10GB of write cache, so when you write the first 10 GB of a data writing session, it goes straight to that write cache at tradional write speeds. Then when there is idle time the disk controller moves the data out to the much slower SMR regions. So, Seagate is apparently tuning the ratio and configuration of SMR areas and perpendicular recording based on use cases. The above youtube documents someone (like me) trying to use SMR drives not designed for RAID use in a raid array. The raid array apparently started kicking the SMR drives out of the array aggressively because of the very slow i/o speeds. He got lucky and didn't have any data loss, but you clearly could if you're having too many drives kicked out of the array too quickly. Hope that's informative, Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 5

[opensuse] Hulu / hal-flash packages?
by Adam Tauno Williams 24 Dec '16

24 Dec '16

Has anyone built hal-flash [which provides the antiquated DRM calls required by Hulu's use of flash] for openSUSE? I have searched OBS and haven't found a package that looks like it matches. As mentioned in http://www.howtogeek.com/239682/how-to-watch-hulu-on-ubuntu-and-other-l inux-distributions/ - and I find the same advice other places. -- Meetings Coordinator, Michigan Association of Railroad Passengers 537 Shirley St NE Grand Rapids, MI 49503-1754 Phone: 616.581.8010 E-mail: awilliam(a)whitemice.org GPG#D95ED383 Web: http://www.marp.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Catch 22 with systemd, fstab and boot/shutdown
by Wols Lists 24 Dec '16

24 Dec '16

My setup is a laptop on a home network, accessing a server/desktop. I could well have mucked up fstab, I don't know, but ... When I originally set the laptop up, things were reasonably fine, except the CD-Rom wouldn't mount automatically, or if it did then if there wasn't a CD-Rom in the drive systemd would fall over at boot. Then I discovered that if Windows suspended, fstab couldn't mount the windows drive, and again systemd fell over at boot. Then I added my network drives, and discovered that, because it's a laptop with the wifi password stored in my user configuration, that boot hung for a couple of minutes trying to mount them until it timed out and allowed the boot to resume. Looking on the web, I discovered that apparently putting the correct options in fstab is the proper way of mounting partitions (I couldn't find any documentation specifically about creating disk service files). So I did that, and now I gather systemd creates temporary service files for me. Great, except that when I shut down the system my user is logged out, the network dies, and the unmounts seem to hang forever. I can't remember if they have ever successfully timed out and let the laptop shut down - certainly displaying the shutdown the umount command has been running for over 15 minutes. So basically, the question is "how do I make systemd do the mounts and unmounts in the right order, WHILE THE USER IS LOGGED IN, and not hang starting or stopping the system because the network is not available?" Everything I've tried so far (as you can see) has simply moved the problem somewhere else. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

Re: [opensuse] Kmail4 broken after update to 42.2 [solved?]
by stakanov＠freenet.de 24 Dec '16

24 Dec '16

> -----Ursprüngliche Nachricht----- > Von: stakanov(a)freenet.de > Gesendet: Sa. 24.12.2016 11:10 > An: opensuse , > Betreff: [opensuse] Kmail4 broken after update to 42.2 > > My local folders are all displayed as offline. The resource maildir is damaged following KDE. But it works, it > does store new local mail as expected in the respective local and previews it (see shot). It is able to > decrypt and encrypt mail via pgp and smartcardtoken. So even complicated stuff. Still it presents as follows: > >http://paste.opensuse.org/77201495 > > > As you can see the folder are shown as offline. Before I tried to akonadictl stop - akonadictl start and it > turned normal. > But with the subsequent login all is gone again. WTF? > > > It does not show previews of mails (that charge endlessly) and shows this banner that, if you click it has not > effect but to recycle to standard view of kmail, empty folder. > > >http://paste.opensuse.org/2011506 > > > btw. why is this written in English? Should be in Italian like the rest? Worth another bug report? > > > Then, any new mail is downloaded correctly and can be displayed: > > >http://paste.opensuse.org/43993833 > > > How can I recover normal operation? Happy for all help and suggestions. Seem to be akonadi related? What did > change between kmail4 in 42.2 and 42.1? > I do possess archives of these mails but this should really not happen with an update. And still, I have to > get rid of this offline problem. > provided that I do not understand what happened, I "solved" the problem. So it seems. So I had to run akonadictl stop akonadictl vacuum akonadictl fsck akonadictl start (all this with kontakt/kmail closed) During the fsck akonadi gave a few notes about "wrong command the world is going to end" After launching kmail you finish up with a new folder within your local folder called sth like akonadi resource3 or similar. Unsubscribing from it has no negative effekt. Apparently this "fix" survives also a restart. In the list this supplemental "resource was present also. Removing it had no influence neither on the mail content, nor on the availability of the local maildir folder. All this akonadi idea is somewhat weird. The old one begins to work so so while AFAIR the new is quite a desaster (see kdepim mailing list.....) I really hope that the plasma5 version will work when 42.3 will come out. For the time being it seems that the kmail4 version works (once you do not have problems as of above) Seasonal greetings. Shall you all pass a peaceful holiday, wherever you are. . --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Why are systemd's logs stored as binaries?
by Greg Freemyer 24 Dec '16

24 Dec '16

I'd like to know more about this. In particular from a authenticity and integrity perspective. Comments about those, or pointers to discussion about same would be appreciated. ==== Here is Lennart Poettering's list of problems with what journald replaces: 1) The message data is generally not authenticated, every local process can claim to be Apache under PID 4711, and syslog will believe that and store it on disk. 2) The data logged is very free-form. Automated log-analyzers need to parse human language strings to a) identify message types, and b) parse parameters from them. This results in regex horrors, and a steady need to play catch-up with upstream developers who might tweak the human language log strings in new versions of their software. Effectively, in a away, in order not to break user-applied regular expressions all log messages become ABI of the software generating them, which is usually not intended by the developer. 3) The timestamps generally do not carry timezone information, even though some newer specifications define support for it. 4) Syslog is only one of many log systems on local machines. Separate logs are kept for utmp/wtmp, lastlog, audit, kernel logs, firmware logs, and a multitude of application-specific log formats. This is not only unnecessarily complex, but also hides the relation between the log entries in the various subsystems. 5) Reading log files is simple but very inefficient. Many key log operations have a complexity of O(n). Indexing is generally not available. 6) The syslog network protocol is very simple, but also very limited. Since it generally supports only a push transfer model, and does not employ store-and-forward, problems such as Thundering Herd or packet loss severely hamper its use. 7) Log files are easily manipulable by attackers, providing easy ways to hide attack information from the administrator 8) Access control is non-existent. Unless manually scripted by the administrator a user either gets full access to the log files, or no access at all. 9) The meta data stored for log entries is limited, and lacking key bits of information, such as service name, audit session or monotonic timestamps. 10) Automatic rotation of log files is available, but less than ideal in most implementations: instead of watching disk usage continuously to enforce disk usage limits rotation is only attempted in fixed time intervals, thus leaving the door open to many DoS attacks. 11) Rate limiting is available in some implementations, however, generally does not take the disk usage or service assignment into account, which is highly advisable. 12) Compression in the log structure on disk is generally available but usually only as effect of rotation and has a negative effect on the already bad complexity behaviour of many key log operations. 13) Classic Syslog traditionally is not useful to handle early boot or late shutdown logging, even though recent improvements (for example in systemd) made this work. 14) Binary data cannot be logged, which in some cases is essential (Examples: ATA SMART blobs or SCSI sense data, firmware dumps) Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

18 192

[opensuse] Kmail4 broken after update to 42.2
by stakanov＠freenet.de 24 Dec '16

24 Dec '16

My local folders are all displayed as offline. The resource maildir is damaged following KDE. But it works, it does store new local mail as expected in the respective local and previews it (see shot). It is able to decrypt and encrypt mail via pgp and smartcardtoken. So even complicated stuff. Still it presents as follows: http://paste.opensuse.org/77201495 As you can see the folder are shown as offline. Before I tried to akonadictl stop - akonadictl start and it turned normal. But with the subsequent login all is gone again. WTF? It does not show previews of mails (that charge endlessly) and shows this banner that, if you click it has not effect but to recycle to standard view of kmail, empty folder. http://paste.opensuse.org/2011506 btw. why is this written in English? Should be in Italian like the rest? Worth another bug report? Then, any new mail is downloaded correctly and can be displayed: http://paste.opensuse.org/43993833 How can I recover normal operation? Happy for all help and suggestions. Seem to be akonadi related? What did change between kmail4 in 42.2 and 42.1? I do possess archives of these mails but this should really not happen with an update. And still, I have to get rid of this offline problem. --- Die Bundesliga hat begonnen! Alle Tore, alle Ergebnisse, alle News: Pocket Liga jetzt im https://app.adjust.com/dpynzd oder https://app.adjust.com/dpynzd herunterladen - kostenlos! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Leap 42 - what file sources ~/.xprofile?
by David C. Rankin 23 Dec '16

23 Dec '16

All, Generally ~/.xprofile is sourced through /etc/X11/xinit/xinitrc (or in xinitrc.common in openSuSE's case). Does anyone know where ~/.xprofile is (or should be) source in the Leap 42.2 X setup? Basically, I want to set the kill the bell (which can be done in ~/.inputrc on Leap) and I want to set the keyboard delay and repeat rate, e.g. xset r rate 276 50 On arch I simply put that in ~/.xprofile. Where should it go on Leap? I can't find anywhere where ~/.xprofile is sourced by the default setup. Help? -- 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

2 1

[opensuse] trying to run the auth-server yast2 module: coredump in ruby?
by L A Walsh 22 Dec '16

22 Dec '16

Trying to run the auth-server... gui was running: /usr/lib/YaST2/bin/y2base auth-server qt I also tried w/gtk, both give: YaST got signal 11 at file /usr/lib64/ruby/vendor_ruby/2.1.0/yast/i18n.rb:133 Segmentation fault (core dumped) A core dump in a script lang like ruby? Looked at line 133: (130-135): def current_language # get the current value from YaST (remove the trailing encoding # like ".UTF-8" if present) (133) lang = WFM.GetLanguage.gsub(/\..*$/, "") return DEFAULT_LOCALE if lang.empty? ---- On a lark tried to look "where on the coredump (at end). It shows ruby calling perl and who knows what modules, where? I though the idea of going to ruby was to ditch perl? But instead, its some wrapper over perl and some unspecified set of perl modules? How can I tell where the perl mods are that it is using and how to reinstall them so they recompile any modules against my system's current perl? With CPAN, I can tell it to remake my current modules so they'll work with my current perl. How do I do that with opensuse's modules? ----core backtrace... #0 Perl_leave_scope (my_perl=0x1774320, base=290) at scope.c:786 #1 0x0000003059f3f451 in S_regmatch (my_perl=my_perl@entry=0x1774320, reginfo=reginfo@entry=0x7fffd33cf9f0, prog=prog@entry=0x1c73a14) at regexec.c:5967 #2 0x0000003059f45d85 in S_regtry (my_perl=my_perl@entry=0x1774320, reginfo=reginfo@entry=0x7fffd33cf9f0, startpos=startpos@entry=0x7fffd33cf9e0) at regexec.c:2738 #3 0x0000003059f4ecfa in Perl_regexec_flags (my_perl=0x1774320, rx=0x1981ac0, stringarg=0x197fdde "/^\\Z/ { new X500::DN (reverse (@{$item[1]})); }\nDistinguishedName: name(?) { @{$item[1]} > 0 ? $item[1][0] : []; }\nname: nameComponent(s /[,;]\\s*/)\nnameComponent: attributeTypeAndValue(s /\\s*\\+\\s*/) {"..., strend=<optimized out>, strbeg=0x197fdc0 "\nstartrule: DistinguishedName /^\\Z/ { new X500::DN (reverse (@{$item[1]})); }\nDistinguishedName: name(?) { @{$item[1]} > 0 ? $item[1][0] : []; }\nname: nameComponent(s /[,;]\\s*/)\nnameComponent: attribu"..., minend=<optimized out>, sv=0x1b97f30, data=0x0, flags=10) at regexec.c:2268 #4 0x0000003059eccfb8 in Perl_pp_match (my_perl=0x1774320) at pp_hot.c:1368 #5 0x0000003059ec8a86 in Perl_runops_standard (my_perl=0x1774320) at run.c:41 #6 0x0000003059e52f50 in Perl_call_sv (my_perl=<optimized out>, sv=<optimized out>, flags=<optimized out>) at perl.c:2705 #7 0x0000003059e53581 in Perl_call_list (my_perl=<optimized out>, oldscope=<optimized out>, paramList=<optimized out>) at perl.c:4782 #8 0x0000003059e37d10 in S_process_special_blocks (my_perl=0x1774320, fullname=<optimized out>, gv=0x17b2350, cv=0x17b22a8) at op.c:6882 #9 0x0000003059e4ca71 in Perl_newATTRSUB_flags ( my_perl=my_perl@entry=0x1774320, floor=floor@entry=139, o=<optimized out>, proto=proto@entry=0x0, attrs=attrs@entry=0x0, block=<optimized out>, block@entry=0x17b6b70, flags=flags@entry=0) at op.c:6852 #10 0x0000003059e4d490 in Perl_newATTRSUB (my_perl=my_perl@entry=0x1774320, floor=floor@entry=139, o=<optimized out>, proto=proto@entry=0x0, attrs=attrs@entry=0x0, block=block@entry=0x17b6b70) at op.c:6499 #11 0x0000003059e4dc6d in Perl_utilize (my_perl=my_perl@entry=0x1774320, aver=<optimized out>, floor=139, version=<optimized out>, idop=<optimized out>, arg=<optimized out>) at op.c:4681 #12 0x0000003059e81558 in Perl_yyparse (my_perl=my_perl@entry=0x1774320, gramtype=gramtype@entry=258) at perly.y:363 #13 0x0000003059f0cc85 in S_doeval (my_perl=my_perl@entry=0x1774320, gimme=gimme@entry=2, startop=startop@entry=0x0, outside=outside@entry=0x0, seq=<optimized out>, hh=hh@entry=0x0) at pp_ctl.c:3666 #14 0x0000003059f19e69 in Perl_pp_require (my_perl=0x1774320) at pp_ctl.c:4223 #15 0x0000003059ec8a86 in Perl_runops_standard (my_perl=0x1774320) at run.c:41 #16 0x0000003059e52f50 in Perl_call_sv (my_perl=<optimized out>, sv=<optimized out>, flags=<optimized out>) at perl.c:2705 #17 0x0000003059e53581 in Perl_call_list (my_perl=<optimized out>, oldscope=<optimized out>, paramList=<optimized out>) at perl.c:4782 #18 0x0000003059e37d10 in S_process_special_blocks (my_perl=0x1774320, fullname=<optimized out>, gv=0x17a3a10, cv=0x1799498) at op.c:6882 #19 0x0000003059e4ca71 in Perl_newATTRSUB_flags ( my_perl=my_perl@entry=0x1774320, floor=floor@entry=5, o=<optimized out>, proto=proto@entry=0x0, attrs=attrs@entry=0x0, block=<optimized out>, block@entry=0x17acfa0, flags=flags@entry=0) at op.c:6852 #20 0x0000003059e4d490 in Perl_newATTRSUB (my_perl=my_perl@entry=0x1774320, floor=floor@entry=5, o=<optimized out>, proto=proto@entry=0x0, attrs=attrs@entry=0x0, block=block@entry=0x17acfa0) at op.c:6499 #21 0x0000003059e4dc6d in Perl_utilize (my_perl=my_perl@entry=0x1774320, aver=aver@entry=1, floor=5, version=version@entry=0x0, idop=idop@entry=0x17814d0, arg=<optimized out>, arg@entry=0x1781880) at op.c:4681 #22 0x0000003059e4e006 in Perl_vload_module (my_perl=0x1774320, flags=2, name=<optimized out>, ver=<optimized out>, args=0x7fffd33d0708) at op.c:4839 #23 0x0000003059e4e117 in Perl_load_module_nocontext (flags=2, name=0x17993c0, ver=0x0) at op.c:4794 #24 0x00007fe45b38fc91 in YPerl::loadModule(YCPList) () from /usr/lib64/YaST2/plugin/libpy2lang_perl.so #25 0x00007fe45b39ef25 in Y2PerlComponent::import(char const*) () from /usr/lib64/YaST2/plugin/libpy2lang_perl.so #26 0x000000310622de8c in Import::import(std::string const&, Y2Namespace*) () from /usr/lib64/libycpvalues.so.6 #27 0x000000310622e7c8 in Import::Import(std::string const&, Y2Namespace*) () from /usr/lib64/libycpvalues.so.6 #28 0x00007fe45a585e4b in ?? () from /usr/lib64/ruby/vendor_ruby/2.1.0/x86_64-linux-gnu/yastx.so #29 0x00007fe45a586504 in ?? () from /usr/lib64/ruby/vendor_ruby/2.1.0/x86_64-linux-gnu/yastx.so #30 0x000000315e775254 in ?? () from /usr/lib64/libruby2.1.so.2.1 #31 0x000000315e7794bc in ?? () from /usr/lib64/libruby2.1.so.2.1 #32 0x000000315e77cf3f in ?? () from /usr/lib64/libruby2.1.so.2.1 #33 0x000000315e77dca2 in ?? () from /usr/lib64/libruby2.1.so.2.1 #34 0x000000315e77e23f in ?? () from /usr/lib64/libruby2.1.so.2.1 #35 0x000000315e775254 in ?? () from /usr/lib64/libruby2.1.so.2.1 #36 0x000000315e781d4d in ?? () from /usr/lib64/libruby2.1.so.2.1 #37 0x000000315e7794bc in ?? () from /usr/lib64/libruby2.1.so.2.1 #38 0x000000315e77cf3f in ?? () from /usr/lib64/libruby2.1.so.2.1 #39 0x000000315e77e4ad in ?? () from /usr/lib64/libruby2.1.so.2.1 #40 0x000000315e77f78b in ?? () from /usr/lib64/libruby2.1.so.2.1 #41 0x000000315e77fe31 in rb_funcall () from /usr/lib64/libruby2.1.so.2.1 #42 0x00007fe45af4fcb7 in YRuby::callClient(std::string const&) () from /usr/lib64/YaST2/plugin/libpy2lang_ruby.so #43 0x00007fe45af4db74 in Y2RubyClientComponent::doActualWork(YCPList const&, Y2Component*) () from /usr/lib64/YaST2/plugin/libpy2lang_ruby.so #44 0x0000003105a0ee09 in main () from /usr/lib64/liby2.so.4 #45 0x0000003000c21b05 in __libc_start_main () from /lib64/libc.so.6 #46 0x00000000004006f9 in ?? () -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0