[Bug 2073797] Re: man-db trigger for apt is excessively slow
I've made an interesting discovery with respect to this. If I remove the `percona-toolkit` package, then mandb runs much faster (2 seconds instead of 2 minutes). I think there is something wrong with the man pages in that package (although I am using the download from https://www.percona.com/percona- toolkit to get a newer version of it, not sure if that would make a difference). However, ideally, mandb would be able to handle this more gracefully. And in 20.04 this wasn't a problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073797 Title: man-db trigger for apt is excessively slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/2073797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053156] Re: update-resolv-conf uses invalid device name
Sorry I respond sooner. I've been very busy. Some basic steps to reproduce: Create an openvpn configuration that includes the following configuration: ``` client dev tun script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf ``` along with any other necessary configuration for your vpn. Then start the vpn. and the update-resolv-conf fails to run. However, it looks like this is no longer a problem as of the time of writing, and instead of the above error I now just get the following warning: ``` Dropped protocol specifier '.openvpn' from 'tun0.openvpn'. Using 'tun0' (ifindex=15). ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053156 Title: update-resolv-conf uses invalid device name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/2053156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073799] Re: Flickering on sway with nvidia on multiple monitors
FWIW, I don't get flickering if I use the nouveau drivers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073799 Title: Flickering on sway with nvidia on multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sway/+bug/2073799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073799] [NEW] Flickering on sway with nvidia on multiple monitors
Public bug reported: When using sway on a setup with an Nvidia graphics card using the proprietary drivers, and multiple monitors. I get constant flickering on the external monitor (this is a laptop). It looks like there are flashes where long narrow triangles of the screen become transparent, showing the background instead of the content of the window. https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/3671 may be a possible fix for this, I haven't had a chance to compile with the patch to see if it actually fixes it for me yet. I do not have this problem if I use gnome with wayland. I have tried several attempts to work around this to no avail: - I tried both enabling and disabling hybrid graphics in my bios. It is much worse with hybrid graphics enabled - I have tried setting WLR_RENDERER=vulkan. This seems to have no effect - I have tried configuring WLR_DRM_DEVICES to prefer the intel graphics card in hybrid mode ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: sway 1.9-1build2 [modified: usr/share/wayland-sessions/sway.desktop] ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 22 12:38:32 2024 InstallationDate: Installed on 2024-07-19 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: sway UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sway (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073799 Title: Flickering on sway with nvidia on multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sway/+bug/2073799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2073797] [NEW] man-db trigger for apt is excessively slow
Public bug reported: Whenever I install a package that includes a man page, apt-install gets stuck for multiple minutes on the step "Processing triggers for man-db". In many cases, this means that the "man-db" trigger takes significantly longer the rest of the installation combined. This slowness is enough of a nuisance that I eventually disabled the man-db update by running ``` echo "set man-db/auto-update false" | sudo debconf-communicate 0 value set ``` However, many users probably won't go to the effort of figuring out how to do this, and will just be frustrated by installations taking a long time. According to some of my co-workers this started happening a few weeks ago (on 24.04). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: man-db 2.12.0-4build2 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 22 12:20:30 2024 InstallationDate: Installed on 2024-07-19 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) SourcePackage: man-db UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: man-db (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073797 Title: man-db trigger for apt is excessively slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/2073797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698090] Re: Segmentation fault
@Bostjan I'm really sorry it took so long to get back to you. I just kept putting it off because I was busy, and never got around to testing it. But we recently ran into this issue again, and tested with building with the --enable-thread-safety configure flag, and that did in fact fix the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698090 Title: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snoopy/+bug/1698090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
> If you know of specific problems with it, we can best help you (and all other Ubuntu users) if you give us bug reports for those problems. There's this: https://github.com/systemd/systemd/issues/5755 Also, systemd-resolved does not have an equivalent of dnsmasq's "all- servers" option, which I need. And because of this bug, I can't run dnsmasq instead of systemd-resolved. I have been able to get something working with both systemd-resolved and dnsmasq running, but having two local dns resolvers is unnecessarily redundant, and more complicated than if I could just run dnsmasq. See my comments on https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745463 ** Bug watch added: github.com/systemd/systemd/issues #5755 https://github.com/systemd/systemd/issues/5755 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928367] Re: openvpn postinst script restarts with init.d, resulting in duplicate openvpn processes
** Tags added: systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928367 Title: openvpn postinst script restarts with init.d, resulting in duplicate openvpn processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1928367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928367] [NEW] openvpn postinst script restarts with init.d, resulting in duplicate openvpn processes
Public bug reported: On Ubuntu 20.04.2 with openvpn 2.4.7-1ubuntu2.20.04.2: The postinst script for openvpn has the following: if [ -x "/etc/init.d/openvpn" ]; then pathfind invoke-rc.d if [ $? = 0 ]; then invoke-rc.d openvpn cond-restart || invoke-rc.d openvpn restart else /etc/init.d/openvpn cond-restart || /etc/init.d/openvpn restart fi fi and since cond-restart isn't one of start,stop,restart, or try-restart, invoke-rc.d will kill the openvpn processes managed by systemd and start a new process using the init.d script. If the systemd service is later restarted, this results in two processes for the same openvpn configuration that conflict with each other. Some ways this could be fixed: 1. Don't run the cond-restart in the postinst script 2. Change inti.d to defer to systemd to start the daemon, at least for cond-restart 3. Stop using the init.d script altogether. 3. Change the systemd service to make sure to kill conflicting processes as part of a restart. ** Affects: openvpn (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/1928367 Title: openvpn postinst script restarts with init.d, resulting in duplicate openvpn processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1928367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907128] Re: Subiquity only provisions half of available space for root logical volume
> There's not much point in using LVM if you then completely fill up the volume group with a single logical volume That's not true. LVM is necessary for LUKS encryption, which is why I am using it. I want a single encrypted volume which uses the entire space. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907128 Title: Subiquity only provisions half of available space for root logical volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1907128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907128] [NEW] Subiquity only provisions half of available space for root logical volume
Public bug reported: When using the ubuntu server installation media, using a full-disk setup with LVM and encryption enabled, the default configuration only uses half of the available space for the root logical group instead of all available space. See attached screenshot. ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Tags: lvm ** Attachment added: "Screenshot of misconfigured LVM setup" https://bugs.launchpad.net/bugs/1907128/+attachment/5441728/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907128 Title: Subiquity only provisions half of available space for root logical volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1907128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698090] Re: Segmentation fault
I can look at seeing if it can be reproduced with a newer version. 2.4.6 would be easier to test than 2.4.9, since it is in the apt repos for 18.04 and 20.04, but I might be able to compile 2.4.9 as well. As far as reproducing it, I don't have great reproduction steps. I've only seen this happen with bitbucket server (which is proprietary), and even then it was happening somewhat randomly, but about once a day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698090 Title: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snoopy/+bug/1698090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
In this systemd github issue https://github.com/systemd/systemd/issues/5755 in particular is problematic darkstar states "the DNS servers are supposed to be exactly equivalent". But as far as I can tell systemd doesn't have any provision for temporarily falling back to a different nameserver if the main one is unavailable and reverting back when it becomes available again. Besides the scenario I listed in my previous comments, this also prevents using a local nameserver as the main nameserver but falling back to an external nameserver if the local one becomes unavailable, with recovery. In that case the two nameservers may not even return the same responses, but having a working nameserver that returns public records is better than no nameserver at all. Again, if there is a way to accomplish failovers with recovery with resolved, I'd love to know how to do it. Maybe systemd-resolved will get functionality that supports these use cases, but right now ifaict it doesn't. And even when it does, will it get backported to LTS versions of ubuntu such as 18.04? ** Bug watch added: github.com/systemd/systemd/issues #5755 https://github.com/systemd/systemd/issues/5755 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
> Can you help me understand the motivation underlying the requirement? The motivation is that if the current dns server goes down, we don't have to wait for the request to timeout and make another request to the next server. Before resolved this was more of a problem since libc would always try to use the first server if it was down and didn't have any memory, so we would add the timeout for the dns lookup to each dns query. But I understand that resolved does remember if a server is down and continues to use that one, but afaict it never switches back, and that is a problem, as I'll explain below. > Do you have DNS servers in your configuration which are always farther / slower? If so, why do you have them in your configuration at all? Yes. We have one DNS server in each availability zone (AWS). We would prefer to use the DNS server in the same availability zone as the host, but want to fall back to one of the others if that one becomes unavailable. > Do you have a particular application requirement for low-latency DNS resolution - and if so, wouldn't the use of a caching local resolver (a configuration which resolved supports, and which we enable by default) have more of an impact on satisfying that requirement? The less time it takes for our application servers to receive an answer the better. Bandwidth for DNS traffic is very cheap and the overhead for DNS CPU is also very inexpensive. We want to have the ability to use the fastest answer from an upstream DNS server as possible. We are also want redundancy so that we can remain unimpacted by planned and unplanned maintenance / issues. A local DNS cache helps with the fast response, but it does not help with an upstream servers availability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
> If there are scenarios where it is not appropriate to run resolved, then we should absolutely evaluate those and determine how they should be supported in Ubuntu. Maybe there is a better way to do this, but here is my situation. I need to be able to send DNS queries to multiple dns servers in parallel and use the first response I get back (so that I use the fastest/closest dns server). On 16.04 I did this by running dnsmasq with the "all-servers" option enabled. afaict, resolved doesn't have an equivalent option. The nameservers come from a supersede rule in the dhclient configuration. But on 18.04 if resolved is running, then dnsmasq uses resolved as the nameserver, which isn't what I want, but if resolved isn't running then I run into this bug and dnsmasq doesn't get any nameservers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698090] Re: Segmentation fault
I'm not sure if this is the same issue. But while running BitBucket we got a segfault about once a day (and had to restart bitbucket), until we figured out it was coming from snoopy code and disabled snoopy on the host. The relevant part of the backtrace: #1236 0x7fa0e54ac746 in strlen () at ../sysdeps/x86_64/strlen.S:106 #1237 0x7fa0e59fd0fd in snoopy_datasource_cmdline () at /lib/snoopy.so #1238 0x7fa0e59fcdc4 in snoopy_message_generateFromFormat () at /lib/snoopy.so #1239 0x7fa0e59fcc6b in snoopy_log_syscall () at /lib/snoopy.so #1240 0x7fa0e59fca45 in execve () at /lib/snoopy.so #1241 0x7fa0e2fd8284 in execve_with_shell_fallback (mode=, file=0x7fa081e75d60 "/usr/bin/git", argv=0x7fa080bfd5e0, envp=0x7fa081316ad0) at /build/openjdk-8-W2Qe27/openjdk-8-8u151-b12/src/jdk/src/solaris/native/java/lang/childproc.c:213 #1242 0x7fa0e2fd86a9 in childProcess (arg=arg@entry=0x7fa0808e4ee0) at /build/openjdk-8-W2Qe27/openjdk-8-8u151-b12/src/jdk/src/solaris/native/java/lang/childproc.c:365 #1243 0x7fa0e2fd5114 in vforkChild (c=c@entry=0x7fa0808e4ee0) at /build/openjdk-8-W2Qe27/openjdk-8-8u151-b12/src/jdk/src/solaris/native/java/lang/UNIXProcess_md.c:434 #1244 0x7fa0e2fd580d in Java_java_lang_UNIXProcess_forkAndExec (env=0x7fa09c73f9e0, process=, helperpath=, c=0x7fa0808e4ee0) at /build/openjdk-8-W2Qe27/openjdk-8-8u151-b12/src/jdk/src/solaris/native/java/lang/UNIXProcess_md.c:552 #1245 0x7fa0e2fd580d in Java_java_lang_UNIXProcess_forkAndExec (env=0x7fa09c73f9e0, process=, mode=3, helperpath=0x7fa03276cef0, prog=0x7fa03276cef8, argBlock=0x7fa03276cf00, argc=2, envBlock=0x7fa03276cf30, envc=21, dir=0x7fa03276cf40, std_fds=0x7fa03276cf48, redirectErrorStream=0 '\000') at /build/openjdk-8-W2Qe27/openjdk-8-8u151-b12/src/jdk/src/solaris/native/java/lang/UNIXProcess_md.c:645 #1246 0x7fa0cf948ac9 in [native offset=0x149] java.lang.UNIXProcess.forkAndExec(int,byte,byte,byte,int,byte,int,byte,int,boolean) () at java/lang/UNIXProcess.java #1247 0x7fa0d43e3394 in [inlined] java.lang.StringCoding.encode(char,int,int) () at java/lang/StringCoding.java:388 0x7fa0d43e3394 in [inlined] java.lang.String.getBytes() () at java/lang/String.java:958 0x7fa0d43e3394 in [inlined] java.lang.ProcessImpl.toCString(java.lang.String) () at java/lang/ProcessImpl.java:51 0x7fa0d43e3394 in [compiled offset=0x834] java.lang.ProcessImpl.start(java.lang.String,java.util.Map,java.lang.String,java.lang.ProcessBuilder$Redirect,boolean) () at java/lang/ProcessImpl.java:134 #1248 0x7fa0d3745548 in [inlined] com.atlassian.utils.process.ExternalProcessImpl.createDefaultProcess(java.util.List,java.util.Map,java.io.File) () at com/atlassian/utils/process/ExternalProcessImpl.java:376 0x7fa0d3745548 in [compiled offset=0x7c8] com.atlassian.utils.process.ExternalProcessImpl.createProcess(java.util.List,java.util.Map,java.io.File) () at com/atlassian/utils/process/ExternalProcessImpl.java:387 #1249 0x7fa0d52478cc in [inlined] com.atlassian.utils.process.ExternalProcessBuilder.build() () at com/atlassian/utils/process/ExternalProcessBuilder.java:55 May be related to https://github.com/a2o/snoopy/issues/46, but I think that the commit that supposedly fixed that is on version 2.3.1. ** Bug watch added: github.com/a2o/snoopy/issues #46 https://github.com/a2o/snoopy/issues/46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698090 Title: Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snoopy/+bug/1698090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899878] Re: Software center have hardcoded colors and shows white font on white bg
Why is this still not fixed? it seems like it wouldn't be that hard, and it has been years since it was first reported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899878 Title: Software center have hardcoded colors and shows white font on white bg To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/899878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
