[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-12-19 Thread Marc Kolly
This problem has been around since 2012 when they enabled IPv6 for their "core services". This: #241305 shows the development of the problem we face now. I'm not using HE. I tested it using Telekom + M-Net (Germany) and O2 + UPC (Czech Republic), so we can basically say that it's not reachable in

[Bug 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

2016-07-03 Thread Marc Kolly
@pitti: your fix still doesn't work all the time. It still happens once in ~10 times. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due

[Bug 1568339] Re: Libreoffice does not update printer list

2016-08-19 Thread Marc Kolly
Were you able to find out the root cause of this? I am also seeing this on a 16.04 machine. I've several other 14.04 machines in the same network, that don't have this issue. I have a central cups:amd64/stable 1.7.5-11+deb8u1 server, that broadcasts the list of printers to all of our

[Bug 1020048] Re: after certain time printing to cups stops working

2016-08-18 Thread Marc Kolly
How is it possible I see the exact same issue with LO (1:5.1.4-0ubuntu1) and cups (2.1.3-4) on Ubuntu 16.04 with a central Debian cups server (1.7.5-11+deb8u1)? I'm not using the /etc/cups/client.conf, but instead a normal full Ubuntu 16.04 installation + all released updates. -- You received

[Bug 1636142] Re: toolbox.py assert failure: *** buffer overflow detected ***: /usr/bin/python3 terminated

2017-09-18 Thread Marc Kolly
Did you ever manage to install the HP Designjet T520 on Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636142 Title: toolbox.py assert failure: *** buffer overflow detected ***:

[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir

2019-12-20 Thread Marc Kolly
@zyga any update on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to:

[Bug 1662552] Re: snaps don't work with NFS home

2019-12-20 Thread Marc Kolly
I recently reinstalled around 20 fat-clients to Ubuntu 18.04, which were previously running 14.04 and I am running into the same problem. Just like michalmaria, our configuration is: 1. Debian 10, provides home folders via NFS and runs Kerberos, OpenLDAP is off-site. 2. Ubuntu 18.04 clients.

[Bug 1662552] Re: snaps don't work with NFS home

2020-10-06 Thread Marc Kolly
Yes, I also removed snapd on all machines in the office, because it was a total unstable mess in 18.04 and reinstalled the Gnome calculator and some other apps that had been switched to snaps by default via a method that actually works everywhere. Unfortunately the chromium package from the

[Bug 1662552] Re: snaps don't work with NFS home

2020-10-05 Thread Marc Kolly
Hello all, we have since then upgraded all our machines to Ubuntu 20.04 and are facing the same issues here with our NFS4 homes. I moved the mountpoint from /user to /home as @zyga suggested, but had no success actually running snaps. Oct 05 15:55:20 pc-021 systemd[1583]: Started Application

[Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab

2020-08-23 Thread Marc Kolly
That is great to hear @marianrh! I switched the entire workforce to the 5.8 kernel after the bug was introduced on those machines that are still on 18.04 and have HWE installed. Now I installed two machines for testing purposes with Ubuntu 20.04 and the problem reappeared quite quickly, so I put

[Bug 1886277] Re: Regression on NFS: unable to handle page fault in mempool_alloc_slab

2020-09-28 Thread Marc Kolly
mainline 5.4.60-050460-generic #202008210836 did indeed fix the setup for me, I just forget to get back to you guys here. Hello Martin, It looks like the fix had not been included in the 5.4.0-47 release, but only in the following 5.4.0-48 release. Have you had the time to update to the updated