August 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] sustemd-journald: Failed to set file attributes: Inappropriate ioctl for device
by Per Jessen 06 Aug '16

06 Aug '16

Whilst investigating another issue, I saw a few of these in the dmesg output: [10110426.160993] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10225680.239405] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10340035.362265] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10455291.134708] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10570546.617025] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10685802.019186] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10801057.829769] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10916312.965022] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [10943324.505592] Clock: inserting leap second 23:59:60 UTC [11031567.937132] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [11145923.325636] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [11261178.194167] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device [11385867.249075] systemd-journald[288]: Failed to set file attributes: Inappropriate ioctl for device This is on openSUSE 13.2, systemd-210-25.16.1.i586. -- Per Jessen, Zürich (17.4°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 2

Re: [opensuse] Leap, FF48 since the updates no RSS feeds loaded anymore [SOLVED]
by stakanov＠freenet.de 05 Aug '16

05 Aug '16

> -----Ursprüngliche Nachricht----- > Von: Dave Howorth > Gesendet: Fr. 05.08.2016 12:37 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Leap, FF48 since the updates no RSS feeds loaded anymore > > On 2016-08-05 10:25, stakanov(a)freenet.de wrote: >> Does anyone else experience this? >> Since the update to FF 48 I cannot load any rss feeds any more. >> The pages load from the sites but not the rss feeds. Astonishingly one provider (heise.de) does load the > rss feeds. All other feeds (nearly 40 or more in my case) do not load in any way. When choosing the associated > main page that one does instead open. >> I tried also to delete and join a rss feed. No difference. >> What could be the reason? Is there any "cache" or other folder that I have to erase? >> I do have the setting to empty all cache and history when I shutdown the browser. >> Anybody else faces the problem? >> Feed technology is "atom" (I think it is called like that, it is the orange icon with white > lines when you join it). > > Do you use NoScript? I noticed there was an update to fix a problem with > RSS caused by the FF48 release. > > Cheers, Dave > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- In deed it is noscript. The latest version is installed and the about:feed and about:feeds workaround is there too. But it does not work. Deactivating noscript does restore rss. I will wait a while if a bugfix comes up, if not, I will have to register to their forum or bugzilla to post a bug. Thank you very much for pointing me at it. Have a good day! --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Leap, FF48 since the updates no RSS feeds loaded anymore
by stakanov＠freenet.de 05 Aug '16

05 Aug '16

Does anyone else experience this? Since the update to FF 48 I cannot load any rss feeds any more. The pages load from the sites but not the rss feeds. Astonishingly one provider (heise.de) does load the rss feeds. All other feeds (nearly 40 or more in my case) do not load in any way. When choosing the associated main page that one does instead open. I tried also to delete and join a rss feed. No difference. What could be the reason? Is there any "cache" or other folder that I have to erase? I do have the setting to empty all cache and history when I shutdown the browser. Anybody else faces the problem? Feed technology is "atom" (I think it is called like that, it is the orange icon with white lines when you join it). --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] Shutdown not powering off machine
by stakanov＠freenet.de 05 Aug '16

05 Aug '16

> -----Ursprüngliche Nachricht----- > Von: ianseeks > Gesendet: Do. 04.08.2016 17:15 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Shutdown not powering off machine > > On Thursday, 4 August 2016 11:06:36 BST Anton Aylward wrote: >> On 08/04/2016 10:25 AM, ianseeks wrote: >> > Yes, its been working fine for a long time, its just these past 3 days-- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Fwd: [#ULZ-505-90625]: [opensuse] Kactivitymanage + systemd-coredump
by ianseeks 05 Aug '16

05 Aug '16

Hi Anyone know about the email below I received after emailing this list about "Kactivitymanage + systemd-coredump"? I've not opened a ticket. Regards Ian ---------- Forwarded Message ---------- Subject: [#ULZ-505-90625]: [opensuse] Kactivitymanage + systemd-coredump Date: Thursday, 4 August 2016, 20:40:04 BST From: Mega Support <support(a)mega.co.nz> To: ianseeks(a)btinternet.com CC: opensuse(a)opensuse.org ianseeks, Thank you for contacting us. This is an automated response confirming the receipt of your ticket. *** One of our consultants will answer your query as soon as possible. Thank you for your patience. *** Ticket ID: ULZ-505-90625 Subject: [opensuse] Kactivitymanage + systemd-coredump Department: Support Type: Issue Status: Open Priority: Normal Kind regards, Mega Limited Kind Regards, Mega Support Follow us on https://www.facebook.com/MEGAprivacy https://twitter.com/ MEGAprivacy & https://mega.nz/#blog -- ----------------------------------------- -- Qt: 5.6.1 KDE Frameworks: 5.24.0 kf5-config: 1.0 KDE Plasma: 5.7.3 Kernel: 4.6.4-2-default "openSUSE Tumbleweed (20160730) (x86_64)" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

Re: [opensuse] Shutdown not powering off machine
by stakanov＠freenet.de 04 Aug '16

04 Aug '16

> -----Ursprüngliche Nachricht----- > Von: ianseeks > Gesendet: Do. 04.08.2016 17:15 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Shutdown not powering off machine > > On Thursday, 4 August 2016 11:06:36 BST Anton Aylward wrote: >> On 08/04/2016 10:25 AM, ianseeks wrote: >> > Yes, its been working fine for a long time, its just these past 3 days-- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

re: [opensuse] What are the recommended reporitories for KDE/Leap 42.1?
by stakanov＠freenet.de 04 Aug '16

04 Aug '16

> -----Ursprüngliche Nachricht----- > Von: Rodney Baker > Gesendet: So. 31.07.2016 05:51 > An: opensuse(a)opensuse.org > Betreff: [opensuse] What are the recommended reporitories for KDE/Leap 421? > > Hi all. What repositories should I have selected to have a properly working KDE desktop > in Leap 42.1? Or do I need to go back to 13.2 and start afresh with a clean install? > > What I'm currently seeing: > > On first login after boot, often plasma widgets (e.g. the Start menu search field) and > dialog boxes (e.g. the KDE Wallet password dialog) won't accept any keyboard input, > despite apparently having the focus. This requires logging out and back in again to get > things working. > > Kmail5 never starts first time - it hangs indefinitely, requiring a "pkill kmail" followed by > another attempt, which usually then works. Using QT5.7 as a repo is not a good choice. Leap is a mix of kde4 and kde5, only 42.2 (when stable) will be more on the plasma5 side. This is not because of a lack of support from Leap but because of the fact that Plasma 5 was at that state when Leap came out. > > Konsole windows eventually stop responding to keyboard input after having been open > for a while, necessitating a logout/login to restore keyboard input. I think this is because you are experiencing crashes due to the mixed repo setup you did choose. Stick to Leap 42.1 main, update. Deactivate the rest of repos. Do a zypper ref, then a zypper dup. You will be asked to drop back to kmail4 and kontact4. This is a good choice. I tried the newer versions but in Leap they did not work, at least not reliably enough to do the job. > > No DTV in Kaffeine (or any other DTV app) - black screen only, despite the DTV tuner > card apparently correctly tuning and the correct program details being displayed on the > OSD. Again, try the above. Kaffeine and DTV needs the packman repo (do this at last). You will also need libdvdcss if it is possible and legal in you country (in Europe AFAIK it is). > > A space bar that can't keep up with my typing speed, resulting in > wordsthatfrequentlyrunon (requiring frequent back-spaces to correct - at this rate I'll > wear out my backspace key). These are plasma crashes due to the repos I think. > > Updates that frequently result in unsolvable dependency conflicts. > > KDE-related repositories that I currently have selected: > Again: just select > OpenSuSE-Leap-42.1-Update Leap 42.1 main repo. Standard packages. > > When I first upgraded to 42.1, the only DE could get (sort of) working was Gnome. Given the repos, this is normal. > Without the above repositories, I could not even get close to a working KDE desktop > after upgrading from 13.2 Because you used additional repos and shifted to plasma 5 in 13.2. If you want this, do not use Leap. Upgrade to TW. With you settings you are not going to get a stable system anyway and you went for the latest and greatest already in 13.2. So there is no reason to go for Leap. > Oh - I also lost all of my desktop customisations and many plasma widgets that I had > come to rely on that obviously haven't been ported to KF5/Plasma 5. That makes it even > more tempting to revert. This is expected behaviour. Plasma 5 is not ready yet, only partially ported applications and plasmoids. If you want to the the "state of the moment" go TW not Leap. This is my opinion YMMV. Leap has been build to be extremely conservative for minimizing risks, have little updates, so it is in parts even "older" then 13.2. This is wanted. If you want to try and risk the current status of a working KDE Plasma 5 desktop go for tumbleweed. I do not see any sense in what you are trying to achieve, if I am honest. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] What are the recommended reporitories for KDE/Leap 42.1?
by Rodney Baker 04 Aug '16

04 Aug '16

Hi all. What repositories should I have selected to have a properly working KDE desktop in Leap 42.1? Or do I need to go back to 13.2 and start afresh with a clean install? What I'm currently seeing: On first login after boot, often plasma widgets (e.g. the Start menu search field) and dialog boxes (e.g. the KDE Wallet password dialog) won't accept any keyboard input, despite apparently having the focus. This requires logging out and back in again to get things working. Kmail5 never starts first time - it hangs indefinitely, requiring a "pkill kmail" followed by another attempt, which usually then works. Konsole windows eventually stop responding to keyboard input after having been open for a while, necessitating a logout/login to restore keyboard input. No DTV in Kaffeine (or any other DTV app) - black screen only, despite the DTV tuner card apparently correctly tuning and the correct program details being displayed on the OSD. A space bar that can't keep up with my typing speed, resulting in wordsthatfrequentlyrunon (requiring frequent back-spaces to correct - at this rate I'll wear out my backspace key). Updates that frequently result in unsolvable dependency conflicts. KDE-related repositories that I currently have selected: KDE Framework 5 OpenSuSE-Leap-42.1-Update KDE:Extra KDE Applications KDE Unstable Extra (mainly for kaffeine5, which isn't working properly either) Qt 5.7 When I first upgraded to 42.1, the only DE could get (sort of) working was Gnome. Without the above repositories, I could not even get close to a working KDE desktop after upgrading from 13.2. Oh - I also lost all of my desktop customisations and many plasma widgets that I had come to rely on that obviously haven't been ported to KF5/Plasma 5. That makes it even more tempting to revert. Nevertheless, it feels like I'm almost there with KF5/Plasma5, as long as I can figure out how to get everything that does work, working properly. Or do I just blow the whole lot away and go to 42.2 as a fresh install? Thanks in advance, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] Kactivitymanage + systemd-coredump
by ianseeks 04 Aug '16

04 Aug '16

Hi This message about a systemd coredump appears everyday in the journal log - Any ideas and should i bug report it ? Journalctl -S "2016-08-02 20:00:00" | grep coredump Aug 03 08:40:30 LianLi systemd-coredump[3398]: Process 1382 (kactivitymanage) of user 1004 dumped core. Aug 03 08:49:39 LianLi systemd-coredump[4758]: Process 3636 (kactivitymanage) of user 1001 dumped core. Aug 03 09:03:56 LianLi systemd-coredump[6368]: Process 4975 (kactivitymanage) of user 1000 dumped core. Aug 03 11:04:50 LianLi systemd-coredump[8035]: Process 6728 (kactivitymanage) of user 1000 dumped core. Aug 03 12:11:06 LianLi systemd-coredump[9813]: Process 8810 (kactivitymanage) of user 1001 dumped core. Aug 03 12:20:22 LianLi systemd-coredump[11272]: Process 10028 (kactivitymanage) of user 1004 dumped core. Aug 03 12:21:49 LianLi systemd-coredump[11963]: Process 11484 (kactivitymanage) of user 1004 dumped core. Aug 03 12:47:04 LianLi systemd-coredump[13080]: Process 12165 (kactivitymanage) of user 1005 dumped core. Aug 03 15:25:21 LianLi systemd-coredump[16102]: Process 15970 (http.so) of user 1001 dumped core. Aug 03 17:06:00 LianLi systemd-coredump[22674]: Process 13303 (kactivitymanage) of user 1001 dumped core. Aug 03 17:13:19 LianLi systemd-coredump[24331]: Process 22889 (kactivitymanage) of user 1004 dumped core. Aug 03 18:05:22 LianLi systemd-coredump[27138]: Process 24555 (kactivitymanage) of user 1000 dumped core. Aug 03 21:01:47 LianLi systemd-coredump[28329]: Process 27979 (kactivitymanage) of user 1000 dumped core. Aug 04 09:18:55 LianLi systemd-coredump[3878]: Process 1388 (kactivitymanage) of user 1000 dumped core. -- Qt: 5.6.1 KDE Frameworks: 5.24.0 kf5-config: 1.0 KDE Plasma: 5.7.3 Kernel: 4.6.4-2-default "openSUSE Tumbleweed (20160728) (x86_64)" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Spamassassin blacklist_from not working ??
by Anton Aylward 04 Aug '16

04 Aug '16

I have some "blacklist_from" entries in my .spamassassin/user_prefs blacklist_from *(a)sendio.pl blacklist_from *(a)supermailito.pl They don't seem to be working; mail from those sites is getting though unaltered. I'm using 'spamd', started by systemd. I've just restarted that to make sure: # ps -ef | grep spam root 6017 1 0 08:08 ? 00:00:01 /usr/sbin/spamd -d -c -L -r /var/run/spamd.pid root 6018 6017 0 08:08 ? 00:00:00 spamd child root 6019 6017 0 08:08 ? 00:00:00 spamd child My .fetchmailrc piped to procmail: mda "/usr/bin/procmail -f %F -d %T"; and procmail pipes to spamassassin :0 fw: /tmp/spamassassin.lock * < 256000 | /usr/bin/spamc I realise there are other ways of doing this involving .forward and Postfix with a modified mail.cf but this way I'm doing strikes me as minimalist and least dependencies. I can't see why it shouldn't work. However those addresses are getting though! I can't see why. I can add debug to my .procmail but that doesn't let me see the working *within* spamassassin. All I can see it how it rates SPAM, not what it does with blacklist items. Any idea how I can drill down with the debug? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 19