[Bug 1906918] Re: Rsyslog can't write to sympa.conf log file because of missing permissions
As it turned out after further investigation, changing the log file's group from sympa to adm, plus changing the mode to 640, seems to be sufficient to give rsyslog access. As the config fragment for logrotate uses the same attributes to create new logfiles, I'd say this is the best solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906918 Title: Rsyslog can't write to sympa.conf log file because of missing permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sympa/+bug/1906918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906918] [NEW] Rsyslog can't write to sympa.conf log file because of missing permissions
Public bug reported: Sympa is sending its log messages to rsyslogd, which is supposed to write them to /var/log/sympa.log. But this file is owned by sympa:sympa, so rsyslogd can't write to it. If it tries, you get errors like - Dec 4 23:55:51 sympa-test rsyslogd: file '/var/log/sympa.log': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ] Dec 4 23:55:51 sympa-test rsyslogd: action 'action-8-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2001.0 try https://www.rsyslog.com/e/2007 ] Dec 4 23:55:51 sympa-test rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') [v8.2001.0 try https://www.rsyslog.com/e/2359 ] Dec 4 23:55:51 sympa-test rsyslogd: action 'action-8-builtin:omfile' suspended (module 'builtin:omfile'), retry 0. There should be messages before this one giving the reason for suspension. [v8.2001.0 try https://www.rsyslog.com/e/2007 ] Dec 4 23:55:51 sympa-test rsyslogd: action 'action-8-builtin:omfile' resumed (module 'builtin:omfile') [v8.2001.0 try https://www.rsyslog.com/e/2359 ] (suspend-resumed repeated multiple times) - in /var/log/syslog. Sympa's log messages go to syslog, too. This could possibly solved in two ways. One is to hand sympa.log over to a fitting owner and group like syslog:adm. But I don't know whether or in what way Sympa itself needs access to sympa.log, so this might not be the best solution. The second way is to extend the rsyslogd conf for Sympa in /etc/rsyslog.d/sympa.conf. You can set the file owner before the config and reset it after. This would look similar to - $fileOwner sympa :programname, contains, "sympa" /var/log/sympa.log :programname, contains, "wwsympa" /var/log/sympa.log :programname, contains, "archived" /var/log/sympa.log :programname, contains, "bounced" /var/log/sympa.log :programname, contains, "bulk" /var/log/sympa.log :programname, contains, "task_manager" /var/log/sympa.log $fileOwner root - This problem appears in Ubuntu 20.04.1 with the package version sympa_6.2.40~dfsg-4. ** Affects: sympa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906918 Title: Rsyslog can't write to sympa.conf log file because of missing permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sympa/+bug/1906918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605117] Re: Unity greeter indicators don't show on second launch
Mostly for the records, I've had a very similar, but more severe problem. Since upgrading from 14.04 to 16.04, not only were the indicators (other than a11y) missing, but I couldn't log in anymore. The correct password was reproducibly rejected as incorrect. After the next restart of lightdm, things worked smoothly, until the next logout. I'd reckon that the same cause that kept the indicators from loading kept lightdm from connecting to its source of authentication (PAM?), but that's highly guesswork. The new 1.18.2-0ubuntu2 so far seems to have fixed that variant of the problem, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605117 Title: Unity greeter indicators don't show on second launch To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1605117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315966] Re: banshee crashes on startup
I'm affected by this as well. When I add specific podcasts and close the application, Banshee crashes at the next start. It doesn't happen with every podcast, but with those that do invoke the crashes the problem is reproducible. Some (arbitrarily chosen) examples: WDR 2 Kabarett (http://www1.wdr.de/radio/podcasts/wdr2/kabarett132.podcast) - breaks Banshee WDR Quarks Co (http://podcast.wdr.de/quarks.xml) - breaks Banshee Pentacast (http://www.c3d2.de/pentacast.xml) - does not break Banshee IT-Cast (http://www.it-cast.de/?feed=podcast) - does not break Banshee In my opinion this looks like a problem with special characters, string encodings or something in that venue. Maybe the crash casts have some kind of problematic character in the podcast name, an episode name, an episode description etc. When the podcast is added, this gets stored in Banshees database, and at following restarts the application trips over it badly. There's another observation that may help you to find the cause of the problem: I've been listening to the first podcast from the above list for several years with Banshee, and it never gave me problems. This was on an Ubuntu machine that was upgraded with every release from 2010 or 2011 to 14.04 LTS. Recently, I got a new machine that I installed 14.04 LTS on, and the WDR 2 Kabarett podcast makes Banshee crash every time I tried to add the podcast. In my opinion this indicates that it's rather a problem of getting the data into the database when adding the podcast in contrast to loading data that previous versions (of Banshee? of Mono? of SQLite?) wrote to the db. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315966 Title: banshee crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1315966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
