[Touch-packages] [Bug 1589289] [NEW] fstrim: cannot open /dev/.lxd-mounts: Permission denied

2016-06-05 Thread Tamas Papp
Public bug reported: fstrun daily cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue:

[Touch-packages] [Bug 1589005] Re: After update DNS work unstable

2016-10-21 Thread Tamas Papp
I still have this problem with network-manager 1.2.4-0ubuntu1. sudo service network-manager restart provides a temporary workaround. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu.

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-17 Thread Tamas Papp
I cannot reproduce the issue very recently, for about ~1 week. Let me check it in another location tomorrow. ii dnsmasq 2.76-5all Small caching DNS proxy

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-19 Thread Tamas Papp
Weird, I can reproduce the issue again after about 1-2 weeks of silence... I can test the DNSSEC=off setting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title:

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-19 Thread Tamas Papp
> This is a good workaround, but perhaps the actual fix should be to remove the package on upgrade to 17.04? What do you mean by this? The fix should not ever something like this. There is reason why dnsmasq is installed on these machines. This is a workaround by not good. -- You received this

[Touch-packages] [Bug 1670959] [NEW] systemd-resolved using 100% CPU

2017-03-07 Thread Tamas Papp
Public bug reported: Sometimes systemd-resolved process is using 100% CPU. After a while it changes back to normal. It happens usually after connecting to the (wifi) network, like starting the OS. strace output: sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-25 Thread Tamas Papp
Actually it's happening continuously, it does not even require a wakup, of wifi reconnection or anything... It's a complete useless peace of crap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-25 Thread Tamas Papp
Recently I can definitely reproduce the issue anytime. It's extremely annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100%

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-10-15 Thread Tamas Papp
hi All, Is it possible to eliminate systemd-resolved from the system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU

[Touch-packages] [Bug 1732030] [NEW] 'apt update' dies with seccomp error

2017-11-13 Thread Tamas Papp
Public bug reported: $ apt-get update 0% [Working] Seccomp prevented execution of syscall 78 on architecture amd64 Reading package lists... Done E: Method mirror has died unexpectedly! E: Sub-process mirror returned an error code (31) ProblemType: Bug DistroRelease: Ubuntu

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2017-11-13 Thread Tamas Papp
Workaround: echo 'apt::sandbox::seccomp "false";' > /etc/apt/apt.conf.d/999seccomp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1732030 Title: 'apt update' dies with

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2018-02-01 Thread Tamas Papp
I've just tried it and I does not face the error anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1732030 Title: 'apt update' dies with seccomp error Status in apt

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

2018-02-01 Thread Tamas Papp
I've just tried it and I do not face the error anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1732030 Title: 'apt update' dies with seccomp error Status in apt

[Touch-packages] [Bug 1933589] [NEW] lightdm login window cannot come up

2021-06-24 Thread Tamas Papp
Public bug reported: After upgrading the package to the latest, lightdm login windows does not appear. I can see just a blank black display with a mouse cursor, nothing else. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gsettings-desktop-schemas 40.0-1ubuntu1 ProcVersionSignature: