[Touch-packages] [Bug 1691996] Re: DNS and search domain is not pushed to systemd-resolved sometimes
The DNS for the tun0 of my OpenVPN connection completely fails. There's nothing in systemd-resolve --status or /var/run/resolv.conf or /etc or any of the other usual places; I don't have time to go digging so I shove stuff in /etc/hosts for now. Pretty useless state of affairs, all told... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1691996 Title: DNS and search domain is not pushed to systemd-resolved sometimes Status in network-manager package in Ubuntu: Confirmed Bug description: I have an OpenVPN connection with statically configured DNS server address and the search domain. When this connection is established, there is a high chance that the DNS address and the search domain are not pushed to systemd-resolved for this connection. The problem does not reproduce reliably, sometimes the parameters are pushed. When the parameters are not pushed, 'systemd-resolve --status' reports no DNS servers or DNS domain for the VPN connection, and name resolution does not work. This bug has been reportedly fixed upstream in NetworkManager 1.8. The upstream bug reports are: https://bugzilla.gnome.org/show_bug.cgi?id=782597 https://bugzilla.gnome.org/show_bug.cgi?id=779087 Please, update NetworkManager shipped with Ubuntu or backport the fix. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 Uname: Linux 4.10.0-16.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 19 13:35:42 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-01 (748 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 100 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-05-11T15:26:12.449289 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH virbr0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 virbr0 a80bff56-e5d6-4fa4-b544-89cb3c389e3b /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 44a70bab-e44e-3942-8259-e96eb6f3fe5b /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tun unmanaged /org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1691996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243642] Re: .Xmodmap not automatically loaded on start
I'm seeing the same behaviour after an upgrade from Precise to Trusty, and it is disheartening to see that the bug was reported during an upgrade between intermediate versions with very little traction. I've added logic to my shell rc script to run xmodmap when I log in, but this does not address the case where I resume, so I still need to manually run xmodmap somewhat regularly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1243642 Title: .Xmodmap not automatically loaded on start Status in xorg package in Ubuntu: Confirmed Bug description: I'm using a ~/.Xmodmap file to define two keycode mappings. 13.10 doesn't seem to automatically load this file any more. 13.04 did. (same file, same laptop) manual execution of xmodmap ~/.Xmodmap works on 13.10! That means I'm e.g. able to use this key in a terminal or in geany. I discovered, that by switching the keyboard layouts using gnome- control-center region layouts the mappings of the xmodmap ~/.Xmodmap will be lost again. Then another manual execution of xmodmap ~/.Xmodmap has to be executed and it works again. Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control- center () later. Sorry, I can't figure out which packet this bug has to be asigned to. By using apport-bug xorg was choosen, but it could be xorg-server or gnome-control-center, also. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 23 12:05:11 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:013c] Subsystem: Acer Incorporated [ALI] Device [1025:013c] InstallationDate: Installed on 2013-10-18 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Acer Extensa 5630 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.34 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 23 11:15:16 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5459 vendor CMO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
Is there a reason update-initramfs can't calculate it's needed space and compare with available space before trying to make an initrd image? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in tools for generating an initramfs: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
