[Desktop-packages] [Bug 1401488] Re: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption
Experiencing crashes in the malloc function due to heap corruption can be challenging to resolve. Here are a few steps you can consider to address this issue: https://cryptocointricks.com/how-does-spot-trading-in-cryptocurrency-work/ Review code for memory errors: Carefully review your code for any memory-related errors, such as buffer overflows, use-after-free, or invalid pointer operations. These issues can lead to heap corruption and subsequent crashes. Use tools like memory debuggers or sanitizers to identify potential problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1401488 Title: [regression] Mir servers (since 0.9) randomly crash in malloc due to heap corruption Status in GLib: Expired Status in Mir: Fix Released Status in Mir 0.9 series: Won't Fix Status in glib2.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Bug description: This happens randomly when using the phone ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity-system-compositor 0.0.5+15.04.20141204-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf AssertionMessage: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** CrashCounter: 1 Date: Wed Dec 10 19:28:35 2014 ExecutablePath: /usr/sbin/unity-system-compositor ExecutableTimestamp: 1417733344 GraphicsCard: InstallationDate: Installed on 2014-12-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20141211-020204) ProcCmdline: unity-system-compositor --disable-overlays=false --spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket --from-dm-fd 9 --to-dm-fd 13 --vt 1 ProcCwd: / ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: __libc_message (do_abort=, fmt=0xb68e3628 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (action=1, str=0xb68e366c "corrupted double-linked list", ptr=) at malloc.c:4996 malloc_consolidate (av=av@entry=0xaa800010) at malloc.c:4165 _int_malloc (av=av@entry=0xaa800010, bytes=bytes@entry=1264) at malloc.c:3423 __GI___libc_malloc (bytes=1264) at malloc.c:2891 Title: unity-system-compositor assert failure: *** Error in `unity-system-compositor': corrupted double-linked list: 0xaa817808 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.58-2 version.lightdm: lightdm 1.13.0-0ubuntu2 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1401488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815368] Re: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side
I understand your concern about the small white border potentially creating an impression of an issue with the Ubuntu dock/panel or screen alignment. It's important to note that the issue you mentioned is specific to the wallpaper and not a system-wide problem.https://techideahub.com/what-to-consider-when-buying-scooters- online/ If the user has automatic wallpaper change enabled, it might be less apparent that the white border is solely related to the wallpaper itself. Rest assured that it doesn't indicate any underlying problem with the Ubuntu dock/panel or screen alignment. Keep enjoying your bike rides! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1815368 Title: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side Status in ubuntu-wallpapers package in Ubuntu: New Bug description: At first this may not sound like much of a issue, but this tiny white border actually makes it look like there's something wrong with the Ubuntu dock/panel or like the screen is shifted 1 pixel to the right. If the user has automatic wallpaper change enabled it may not be obvious that the issue is only the wallpaper. Either way, it makes this otherwise beautiful wallpaper that is shipped with 18.04 unpleasant. See the attached picture, the issue is even more noticeable on a highres. screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1815368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815368] Re: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side
I understand that even a small white border on the Ubuntu dock/panel can create the perception of an issue with the display or the positioning of the screen. https://thetraveltourism.com/5-common-garage-door-problems- and-how-to-fix-them/ This can be particularly misleading if the user has automatic wallpaper change enabled, as it may not be immediately apparent that the issue is solely related to the wallpaper. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1815368 Title: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side Status in ubuntu-wallpapers package in Ubuntu: New Bug description: At first this may not sound like much of a issue, but this tiny white border actually makes it look like there's something wrong with the Ubuntu dock/panel or like the screen is shifted 1 pixel to the right. If the user has automatic wallpaper change enabled it may not be obvious that the issue is only the wallpaper. Either way, it makes this otherwise beautiful wallpaper that is shipped with 18.04 unpleasant. See the attached picture, the issue is even more noticeable on a highres. screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1815368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
when using dnsmasq, you may encounter situations where it fails to resolve private names in networks with non-equivalent nameservers. This can happen when the nameservers configured for your network do not have the necessary information to resolve the private names. To troubleshoot this issue, you can try the following steps: Verify DNS configuration: Double-check your network's DNS configuration settings. Ensure that the nameservers specified in the configuration have the ability to resolve private names. If needed, update the DNS configuration to include appropriate nameservers. Check firewall settings: If you have a firewall in place, ensure that it is not blocking the necessary DNS traffic. Adjust the firewall rules to allow DNS queries and responses to flow smoothly between your network and the nameservers. https://home-decoration-ideas.com/what-forms-do-i-need-to-become-a-licensed-garage-door-repair-in-highland-springs/ Configure dnsmasq options: Review the configuration options for dnsmasq. Ensure that it is properly configured to use the correct nameservers for resolving private names. Check for any specific settings related to resolving private names and adjust them if necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Won't Fix Status in network-manager source package in Precise: Won't Fix Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1083565] Re: avahi malfunctions on a machine connected to the network via multiple interfaces
if Avahi malfunctions on a machine connected to the network via multiple interfaces, it can cause issues with service discovery and hostname resolution. Here are a few steps you can try to troubleshoot the problem: Check network connectivity: Ensure that all network interfaces are properly connected and have a valid IP configuration. Verify that you can access other devices on the network and that there are no general connectivity issues. https://homecleaningblog.com/preparing-your-home-for-garage-door-repairs/ Restart Avahi service: Restart the Avahi service on the machine. This can help refresh its configuration and resolve any temporary issues. You can do this by running the appropriate command for your operating system, such as "sudo systemctl restart avahi-daemon" on Linux. Verify Avahi configuration: Review the Avahi configuration file (/etc/avahi/avahi-daemon.conf) and check for any misconfigurations or conflicts. Pay attention to settings related to interfaces and network discovery. Make sure that all relevant interfaces are enabled for Avahi service. Check firewall settings: Ensure that the firewall on the machine is not blocking Avahi traffic. Avahi uses specific ports and protocols for service discovery. Adjust the firewall rules to allow Avahi traffic to pass through. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1083565 Title: avahi malfunctions on a machine connected to the network via multiple interfaces Status in avahi package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: I have a router making up one local NAT network connected to the internet. The router allows to connect both wired and wireless. My laptops are configured to use both wired and wireless. So I can walk around with them and also connect to the quicker wired network if they are on the desk. Problem is that when the laptops are on my desk and I plug in the network cables they stay connected on wireless and so they get connected twice, wired and wireless, with two IP addresses, appearing as two computers for the router and all other computers in the network. Most things still simply work, like accessing the internet from the laptops, SSHing to another computer, ... what causes problems is Bonjour/mDNS. Avahi broadcasts available services (I have shared CUPS printers on the laptops) into the network, using the host name of the machine assigned on installation, for example "till-lenovo". As the broadcasts go through two interfaces there is a service name conflict and it seems that Avahi tries to overcome it by using host names like "till-lenovo-1", "till-lenovo-2", ... When the laptop keeps running one sees in the "avahi-discover" output on another machine the entries from the laptop, but with host names (and so the service names) changing from time to time. This leads to a client with a print queue pointing to a printer shared by the laptop via the printer's Bonjour service name cannot print any more. I have done a short test and Avahi stops adding numbers to the original host name when turning off wireless on the laptop so that it connects only through the wired network. One way of fixing (or working around?) the problem would be a change in network-manager to automatically turn off wireless if the computer is connected to a wired network and switching wireless back on when the network cable gets disconnected. This would probably also solve problems with other server functionality. --->> http://somapills.net Another solution would be a change in Avahi, somehow recognizing that the broadcasts through the two interfaces come from the same computer and so they can (and should) have the same service names, or recognizing that the two interfaces go into the same network and therefore broadcast only through one of them, stopping the broadcasting through the weaker one (the wireless in our case). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1083565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
