[Touch-packages] [Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs

2017-04-18 Thread Rune Philosof
@dino99: I think the typical user won't realize, that the logs are being thrown away, until they need a log from the previous boot. By then it is too late to correct the configuration. Why not set `Storage=persistent` in `/etc/systemd/journald.conf` instead of creating the folder. That would ensur

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2015-11-13 Thread Rune Philosof
Might it be because it wants to ask some debconf question but the graphical ui with the question doesn't show. So it might be waiting for user input which the user has no way to give? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscri

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2015-11-13 Thread Rune Philosof
However, when I next ran apt-get install, to install something else, it completed the install of lsb* and openprinting-gutenprint without any questions: Setting up lsb-core (4.1+Debian11ubuntu8) ... Setting up lsb-graphics (4.1+Debian11ubuntu8) ... Setting up lsb-cxx (4.1+Debian11ubuntu8) ... Sett

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

2015-11-13 Thread Rune Philosof
As in #111 but on 15.10. I got this error after the "Add printer driver"-UI hanged while trying to add openprinting-gutenprint. This is the process locking the config.dat: |-aptd-+-aptd-+-dpkg | | `-sh---dpkg-preconfigu---dpkg-preconfigu I had tried to install the print

[Touch-packages] [Bug 1243932] Re: aa-logprof: Log contains unknown mode senw

2015-10-02 Thread Rune Philosof
It would be nice if patches that are backported to trusty are also backported to 15.04. I upgraded to 15.04 to enjoy newer features. I was expecting to only see new bugs related to those newer features that I chose to upgrade to, not expecting patches that made it to 14.04 didn't make it to 15.0