[Touch-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
That kernel option was not easy to find, but it's working now. FW_LOADER_COMPRESS=y FW_LOADER_COMPRESS_ZSTD=y -- 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/1942260 Title: compress firmware in /lib/firmware Status in firmware-sof package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in firmware-sof source package in Mantic: Fix Released Status in initramfs-tools source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware-raspi source package in Mantic: Confirmed Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+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 1917187] Re: lxc cgroup2: containers unbootable
Hmmm, that's an old one. IIRC the real root cause was, that some files possibly included via /usr/share/lxc/config/ubuntu.common.conf still used lxc.cgroup.devices.* instead of lxc.cgroup2.devices.* (the machine was upgraded from bionic to focal). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1917187 Title: lxc cgroup2: containers unbootable Status in lxc package in Ubuntu: Invalid Bug description: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal If one sets in /etc/default/grub (as e.g. desired by facebook oomd): GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1 swapaccount=1 ..." lxc is not able to start any containers anymore. # lxc-start -F n04-01 lxc-start: n04-01: conf.c: lxc_setup_boot_id: 3249 Permission denied - Failed to mount /dev/.lxc-boot-id to /proc/sys/kernel/random/boot_id Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems. Exiting PID 1... config: --- # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf # Container specific configuration lxc.apparmor.profile = lxc-default-cgns-with-mounting lxc.start.auto = 1 lxc.rootfs.path = dir:/zones/n04-01/rootfs lxc.rootfs.options = noatime lxc.mount.fstab = /zones/n04-01/fstab lxc.uts.name = n04-01 lxc.arch = amd64 # Network configuration lxc.net.0.type = macvlan lxc.net.0.macvlan.mode = bridge lxc.net.0.flags = up lxc.net.0.link = vlan2 lxc.net.0.hwaddr = 00:80:41:22:0d:10 lxc.net.0.name = n04-01_0 #lxc.include = /zones/n04-01/nvconfig lxc.start.order = 16 #lxc.net.0.ipv4 = 10.2.1.65/16 #lxc.net.0.ipv4.gateway = 10.2.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917187/+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 1959646] [NEW] dhcrelay does not obey -i interface option
Public bug reported: If one starts dhcrelay with explicitly specifying the interfaces to listen,it silently ignores these options and still listens on all interfaces. This is neither what the man page says (it says, only if no interface is given, it listen on all interfaces), nor what is needed. It might be even considered being a security bug because dhcrelay listens on interfaces it shouldn't. Needless filter work causes unwanted overhead as well. Wrt. the source package the patches/dhcrelay-listen.patch seems to be the root cause. It makes no sense at all to me ... Please explain or remove. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1959646 Title: dhcrelay does not obey -i interface option Status in isc-dhcp package in Ubuntu: New Bug description: If one starts dhcrelay with explicitly specifying the interfaces to listen,it silently ignores these options and still listens on all interfaces. This is neither what the man page says (it says, only if no interface is given, it listen on all interfaces), nor what is needed. It might be even considered being a security bug because dhcrelay listens on interfaces it shouldn't. Needless filter work causes unwanted overhead as well. Wrt. the source package the patches/dhcrelay-listen.patch seems to be the root cause. It makes no sense at all to me ... Please explain or remove. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1959646/+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 1917192] [NEW] lxc-stop -r does not work
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal lxc-stop -r -n $zone Stops the container, but does not reboot it anymore, as in bionic. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1917192 Title: lxc-stop -r does not work Status in lxc package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal lxc-stop -r -n $zone Stops the container, but does not reboot it anymore, as in bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917192/+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 1917187] [NEW] lxc cgroup2: containers unbootable
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal If one sets in /etc/default/grub (as e.g. desired by facebook oomd): GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1 swapaccount=1 ..." lxc is not able to start any containers anymore. # lxc-start -F n04-01 lxc-start: n04-01: conf.c: lxc_setup_boot_id: 3249 Permission denied - Failed to mount /dev/.lxc-boot-id to /proc/sys/kernel/random/boot_id Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems. Exiting PID 1... config: --- # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf # Container specific configuration lxc.apparmor.profile = lxc-default-cgns-with-mounting lxc.start.auto = 1 lxc.rootfs.path = dir:/zones/n04-01/rootfs lxc.rootfs.options = noatime lxc.mount.fstab = /zones/n04-01/fstab lxc.uts.name = n04-01 lxc.arch = amd64 # Network configuration lxc.net.0.type = macvlan lxc.net.0.macvlan.mode = bridge lxc.net.0.flags = up lxc.net.0.link = vlan2 lxc.net.0.hwaddr = 00:80:41:22:0d:10 lxc.net.0.name = n04-01_0 #lxc.include = /zones/n04-01/nvconfig lxc.start.order = 16 #lxc.net.0.ipv4 = 10.2.1.65/16 #lxc.net.0.ipv4.gateway = 10.2.0.1 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1917187 Title: lxc cgroup2: containers unbootable Status in lxc package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal If one sets in /etc/default/grub (as e.g. desired by facebook oomd): GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1 swapaccount=1 ..." lxc is not able to start any containers anymore. # lxc-start -F n04-01 lxc-start: n04-01: conf.c: lxc_setup_boot_id: 3249 Permission denied - Failed to mount /dev/.lxc-boot-id to /proc/sys/kernel/random/boot_id Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted [!!] Failed to mount API filesystems. Exiting PID 1... config: --- # Common configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf # Container specific configuration lxc.apparmor.profile = lxc-default-cgns-with-mounting lxc.start.auto = 1 lxc.rootfs.path = dir:/zones/n04-01/rootfs lxc.rootfs.options = noatime lxc.mount.fstab = /zones/n04-01/fstab lxc.uts.name = n04-01 lxc.arch = amd64 # Network configuration lxc.net.0.type = macvlan lxc.net.0.macvlan.mode = bridge lxc.net.0.flags = up lxc.net.0.link = vlan2 lxc.net.0.hwaddr = 00:80:41:22:0d:10 lxc.net.0.name = n04-01_0 #lxc.include = /zones/n04-01/nvconfig lxc.start.order = 16 #lxc.net.0.ipv4 = 10.2.1.65/16 #lxc.net.0.ipv4.gateway = 10.2.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1917187/+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 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks
Łukasz Zemczak, yes, upgraded a machine from bionic to focal - same
problem. However, the patch looks not optimal but sufficient.
--
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/1868892
Title:
initramfs-tools/hooks/udev for network *.link really sucks
Status in systemd package in Ubuntu:
In Progress
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Eoan:
Fix Committed
Status in systemd source package in Focal:
In Progress
Bug description:
[impact]
If the /{etc,lib}/systemd/network directory itself is a symlink, the find
command will not actually find any of the files in the dir it links to.
[test case]
$ sudo touch /etc/systemd/network/lp1868892.link
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
...
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
usr/lib/systemd/network/lp1868892.link
$ sudo mv /etc/systemd/network /etc/systemd/network.abc
$ sudo ln -s network.abc /etc/systemd/network
$ sudo update-initramfs -u
$ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
$
[regression potential]
this adjusts how link files are included in the initramfs, so
regressions would likely occur when creating new initramfs, such as
failure to create initramfs at all, or failure to properly copy link
files into the initramfs, causing network setup failure.
[scope]
this is a Debian/Ubuntu specific file, and the Debian MR was just
opened, so this is needed for Debian and all releases of Ubuntu.
[other info]
This bug likely has a very limited impact, as it is uncommon to
symlink either the /lib/systemd/network or /etc/systemd/network dirs.
[original description]
If one creates e.g. /etc/systemd/network.cu and
/etc/systemd/network.fc and symlinks /etc/systemd/network to one of
them, network setup will fail on reboot, because /usr/share/initramfs-
tools/hooks/udev does a very poor job: it simply checks for a
directory instead of the link files and therefore skips copying
required files to the ram image. Another poor job is done when copying
the files to the ram image: instead of following symlinks it copies
them as which in turn makes them useless, because it does not copy the
related dirs and thus the symlinks point to nothing. So keeping the
system in an consistent state which such poor scripts is very hard,
asking for trouble.
Suggested fix is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1868892] [NEW] initramfs-tools/hooks/udev for network *.link really sucks
Public bug reported: If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc and symlinks /etc/systemd/network to one of them, network setup will fail on reboot, because /usr/share/initramfs-tools/hooks/udev does a very poor job: it simply checks for a directory instead of the link files and therefore skips copying required files to the ram image. Another poor job is done when copying the files to the ram image: instead of following symlinks it copies them as which in turn makes them useless, because it does not copy the related dirs and thus the symlinks point to nothing. So keeping the system in an consistent state which such poor scripts is very hard, asking for trouble. Suggested fix is attached. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Patch added: "/usr/share/initramfs-tools/hooks/udev patch" https://bugs.launchpad.net/bugs/1868892/+attachment/5341158/+files/networkd-ramfs.patch -- 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/1868892 Title: initramfs-tools/hooks/udev for network *.link really sucks Status in systemd package in Ubuntu: New Bug description: If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc and symlinks /etc/systemd/network to one of them, network setup will fail on reboot, because /usr/share/initramfs- tools/hooks/udev does a very poor job: it simply checks for a directory instead of the link files and therefore skips copying required files to the ram image. Another poor job is done when copying the files to the ram image: instead of following symlinks it copies them as which in turn makes them useless, because it does not copy the related dirs and thus the symlinks point to nothing. So keeping the system in an consistent state which such poor scripts is very hard, asking for trouble. Suggested fix is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1868892/+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 1799977] Re: [MIR] gssdp
It has to answer unicast M-SEARCH. That's in the UPnP spec and validation test suite. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp Status in gssdp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+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 1080591] Re: shotwell fails to authenticate with non-primary address
I think the original report was against the UOA implementation which does no longer exist anyway -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1080591 Title: shotwell fails to authenticate with non-primary address Status in One Hundred Papercuts: Invalid Status in Shotwell: Invalid Status in gnome-control-center-signon package in Ubuntu: Invalid Status in shotwell package in Ubuntu: Invalid Bug description: I am trying to export some pictures from Shotwell to my Picasa account. I select Picasa from the "publish" list, and push the button to authenticate. I am asked for password, which I enter. I am then told that "Authentication failed". Subsequent attempts go directly to "Authentication failed", and there is no apparent way to enter the password again. (I thought this was due to me logging in with a non-gmail address, and it seemed to work when I changed to the gmail one, but now it fails again) Further suggestions: 1) Shotwell should be more informative about the Authentication Failure, and report what exactly is wrong. I thought I had mistyped the password, and then it's frustrating not to be offered the opportunity to retype it. 2) The login dialog should offer a direct link or pointer to the accounts settings, now I need to select "Add an account" from the drop down. 3) Incidentally, removing accounts doesn't work, in the end I had to disable two (non-working) instances of Google account configurations. Shotwell version 0.13.0-0ubuntu3, on Ubuntu 12.10, 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1080591/+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 1811051] [NEW] lxc-templates: too many senseless dependencies
Public bug reported: # apt install lxc-templates Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv ibverbs-providers libaio1 libassuan0 libcurl3-gnutls libibverbs1 libiscsi7 libksba8 libnghttp2-14 libnl-3-200 libnl-route-3-200 libnpth0 libnspr4 libnss3 libpsl5 librados2 librbd1 librtmp1 pinentry-curses publicsuffix qemu-block-extra qemu-utils sharutils uuid-runtime wget Suggested packages: cloud-utils-euca mtools ubuntu-archive-keyring dbus-user-session pinentry-gnome3 tor shunit2 wodim cdrkit-doc parcimonie xloadimage scdaemon qemu-user-static pinentry-doc sharutils-doc The following NEW packages will be installed: busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm ibverbs-providers libaio1 libassuan0 libcurl3-gnutls libibverbs1 libiscsi7 libksba8 libnghttp2-14 libnl-3-200 libnl-route-3-200 libnpth0 libnspr4 libnss3 libpsl5 librados2 librbd1 librtmp1 lxc-templates pinentry-curses publicsuffix qemu-block-extra qemu-utils sharutils uuid-runtime wget The following packages will be upgraded: gpgv 1 upgraded, 40 newly installed, 0 to remove and 76 not upgraded. 3 not fully installed or removed. Need to get 10.9 MB of archives. After this operation, 40.8 MB of additional disk space will be used. ... 41 MB of totally useless bloat just to get some config alias text files is far too much! Actually this package should not have any dependencies at all! > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1811051 Title: lxc-templates: too many senseless dependencies Status in apparmor package in Ubuntu: New Bug description: # apt install lxc-templates Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv ibverbs-providers libaio1 libassuan0 libcurl3-gnutls libibverbs1 libiscsi7 libksba8 libnghttp2-14 libnl-3-200 libnl-route-3-200 libnpth0 libnspr4 libnss3 libpsl5 librados2 librbd1 librtmp1 pinentry-curses publicsuffix qemu-block-extra qemu-utils sharutils uuid-runtime wget Suggested packages: cloud-utils-euca mtools ubuntu-archive-keyring dbus-user-session pinentry-gnome3 tor shunit2 wodim cdrkit-doc parcimonie xloadimage scdaemon qemu-user-static pinentry-doc sharutils-doc The following NEW packages will be installed: busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm ibverbs-providers libaio1 libassuan0 libcurl3-gnutls libibverbs1 libiscsi7 libksba8 libnghttp2-14 libnl-3-200 libnl-route-3-200 libnpth0 libnspr4 libnss3 libpsl5 librados2 librbd1 librtmp1 lxc-templates pinentry-curses publicsuffix qemu-block-extra qemu-utils sharutils uuid-runtime wget The following packages will be upgraded: gpgv 1 upgraded, 40 newly installed, 0 to remove and 76 not upgraded. 3 not fully installed or removed. Need to get 10.9 MB of archives. After this operation, 40.8 MB of additional disk space will be used. ... 41 MB of totally useless bloat just to get some config alias text files is far too much! Actually this package should not have any dependencies at all! > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1811051/+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 1810458] [NEW] do-release-upgrade fails with "No such file or directory: 'gpg'"
Public bug reported: > + do-release-upgrade Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,263 kB] Fetched 1,264 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' Traceback (most recent call last): File "/usr/bin/do-release-upgrade", line 200, in fetcher.run() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 282, in run if not self.authenticate(): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 76, in authenticate if self.gpgauthenticate(f, sig): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 108, in gpgauthenticate close_fds=False, universal_newlines=True) File "/usr/lib/python3.5/subprocess.py", line 947, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'gpg' > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial > + apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > which gpg gpg: Command not found. > which gpg2 /usr/bin/gpg2 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1810458 Title: do-release-upgrade fails with "No such file or directory: 'gpg'" Status in apparmor package in Ubuntu: New Bug description: > + do-release-upgrade Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,263 kB] Fetched 1,264 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' Traceback (most recent call last): File "/usr/bin/do-release-upgrade", line 200, in fetcher.run() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 282, in run if not self.authenticate(): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 76, in authenticate if self.gpgauthenticate(f, sig): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 108, in gpgauthenticate close_fds=False, universal_newlines=True) File "/usr/lib/python3.5/subprocess.py", line 947, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'gpg' > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial > + apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > which gpg gpg: Command not found. > which gpg2 /usr/bin/gpg2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1810458/+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 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)
I also ran into the problem but solved it by downgrading systemd: > apt install systemd=229-4ubuntu4 libsystemd0=229-4ubuntu4 > apt-mark hold systemd -- 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/1804847 Title: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz) Status in systemd package in Ubuntu: Confirmed Bug description: The following description is taken from: https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237 Hello everyone, I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After a recent reboot I found most of my services to be in a failed state. The reason for that, I guess, are these log entries: Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/elasticsearch failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/systemd/netif failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/systemd/netif/links failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/systemd/netif/leases failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: Invalid argument To verify I tried this: /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create elasticsearch.conf Reading config file "elasticsearch.conf". Running create action for entry d /var/run/elasticsearch Found existing directory "/var/run/elasticsearch". "/run/elasticsearch" has right mode 40755 chown "/run/elasticsearch" to 120.128 fchownat() of /run/elasticsearch failed: Invalid argument I can manually chown the directories, e.g. "chown elasticsearch:elasticsearch /var/run/elasticsearch" and restart the service successfully. My suspicion is, this is related to an upgrade of systemd to 229-4ubuntu21.8. At this point I don't know what to do. I'm also confused about the version I have installed, which I thought is systemd-229. Howver, I looked at https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found that fchownat() is only used from version 238+: Tag v237 (and earlier, including 229): /.../ if (chown(fn, i->uid_set ? i->uid : UID_INVALID, i->gid_set ? i->gid : GID_INVALID) < 0) return log_error_errno(errno, "chown(%s) failed: %m", path); } /.../ Tag v238 /.../ if (fchownat(fd, "", i->uid_set ? i->uid : UID_INVALID, i->gid_set ? i->gid : GID_INVALID, AT_EMPTY_PATH) < 0) return log_error_errno(errno, "fchownat() of %s failed: %m", path); /.../ Any help fixing this problem would be highly appreciated. Many thanks, Rafael === Notes === fchownat() was added to Linux in kernel 2.6.16; library support was added to glibc in version 2.4. checkinf if it is blocked/filtered/sandboxed, rarther than unavailable. glibc in bionic requires minimum linux 3.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+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 1799442] [NEW] Missing xcb_dri3_get_supported_modifiers
Public bug reported: After upgrading to Ubuntu 18.10 I can't run eagle: ./eagle: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0: undefined symbol: xcb_dri3_get_supported_modifiers https://www.autodesk.com/products/eagle/free-download libglx-mesa0: Installed: 18.2.2-0ubuntu1 Candidate: 18.2.2-0ubuntu1 Version table: *** 18.2.2-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglx-mesa0 18.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 13:57:08 2018 DistUpgraded: 2018-10-19 12:58:32,323 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Misslyckades med att köra barnprocessen ”./xorg_fix_proprietary.py” (Filen eller katalogen finns inte) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:075b] InstallationDate: Installed on 2018-01-05 (290 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (4 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.9.0 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.9.0:bd07/09/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1799442 Title: Missing xcb_dri3_get_supported_modifiers Status in mesa package in Ubuntu: New Bug description: After upgrading to Ubuntu 18.10 I can't run eagle: ./eagle: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0: undefined symbol: xcb_dri3_get_supported_modifiers https://www.autodesk.com/products/eagle/free-download libglx-mesa0: Installed: 18.2.2-0ubuntu1 Candidate: 18.2.2-0ubuntu1 Version table: *** 18.2.2-0ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglx-mesa0 18.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 13:57:08 2018 DistUpgraded: 2018-10-19 12:58:32,323 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Misslyckades med att köra barnprocessen ”./xorg_fix_proprietary.py” (Filen eller katalogen finns inte) (8)) DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:075b] InstallationDate: Installed on 2018-01-05 (290 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (4 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 879838] Re: Keyboard Layout "Germany Neo 2": Mod4 does not work if used as secondary keyboard layout
Working output with xkbcomp $DISPLAY
** Attachment added: "output-neo2-working.xkb"
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+attachment/5149978/+files/output-neo2-working.xkb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/879838
Title:
Keyboard Layout "Germany Neo 2": Mod4 does not work if used as
secondary keyboard layout
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
Mod4) don't work. To reproduce this bug, do the following:
1: Neo 2 as primary keyboard layout
- start gnome-keyboard-properties
- Click "Add..."
- Select Country: "Germany" and Variants: "Germany Neo 2"
- Select "Germany Neo 2" and move it to the top of the list.
Try to use Neo Layer 4 or 6. E.g. type the number "4" which is "Mod4" and "n"
in Neo ("<" and "j" in standard German QWERTZ layout) or move the cursor left
using "Mod4" and "i" ("AltGr" and "s" in QWERTZ layot). Works as expected.
2: Neo as secondary layout
- Now add "Germany Eliminate dead keys" to the list and move it to the top
- Use "Neo 2" as secondary layout
- Click "Options" and select "Scroll lock" (or any other) as "Key(s) to
change layout"
Now switch to Neo using the selected key and try to type "4" or move the
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is,
you will be typing an "n" instead of a "4" and an "i" instead of moving the
cursor left).
Choosing other keys for layout change or turning the compose key
on/off does not change anything. Neither does applying "Neo 2" as
primary layout system wide and using "Germany Eliminate dead keys"
with "Neo 2" as a secondary keyboard layout as local user.
Applying the patch suggested on neo-layout.org for a similar problem
(http://wiki.neo-layout.org/ticket/174) does not have any effect.
Description: Ubuntu 11.04
Release: 11.04
xkb-data: 2.1-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+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 879838] Re: Keyboard Layout "Germany Neo 2": Mod4 does not work if used as secondary keyboard layout
Not working export with xkbcomp $DISPLAY
** Attachment added: "output-neo2-not-working.xkb"
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+attachment/5149977/+files/output-neo2-not-working.xkb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/879838
Title:
Keyboard Layout "Germany Neo 2": Mod4 does not work if used as
secondary keyboard layout
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
Mod4) don't work. To reproduce this bug, do the following:
1: Neo 2 as primary keyboard layout
- start gnome-keyboard-properties
- Click "Add..."
- Select Country: "Germany" and Variants: "Germany Neo 2"
- Select "Germany Neo 2" and move it to the top of the list.
Try to use Neo Layer 4 or 6. E.g. type the number "4" which is "Mod4" and "n"
in Neo ("<" and "j" in standard German QWERTZ layout) or move the cursor left
using "Mod4" and "i" ("AltGr" and "s" in QWERTZ layot). Works as expected.
2: Neo as secondary layout
- Now add "Germany Eliminate dead keys" to the list and move it to the top
- Use "Neo 2" as secondary layout
- Click "Options" and select "Scroll lock" (or any other) as "Key(s) to
change layout"
Now switch to Neo using the selected key and try to type "4" or move the
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is,
you will be typing an "n" instead of a "4" and an "i" instead of moving the
cursor left).
Choosing other keys for layout change or turning the compose key
on/off does not change anything. Neither does applying "Neo 2" as
primary layout system wide and using "Germany Eliminate dead keys"
with "Neo 2" as a secondary keyboard layout as local user.
Applying the patch suggested on neo-layout.org for a similar problem
(http://wiki.neo-layout.org/ticket/174) does not have any effect.
Description: Ubuntu 11.04
Release: 11.04
xkb-data: 2.1-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+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 879838] Re: Keyboard Layout "Germany Neo 2": Mod4 does not work if used as secondary keyboard layout
I just hit this bug too and can confirm it for 17.10 and 18.04.
However, there is an easy workaround: Make sure Neo2 is the only layout
in your XKB keymap. The easiest way would be to have just one layout.
Another solution for me is to have exactly 4 layouts and Neo2 is the
4th. Checking with "xkbcomp $DISPLAY output.xkb" both ways lead to the
same keymap.
I will attach a working and non working xkbcomp output. Maybe someone
with more experience can diff these and find the root cause.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/879838
Title:
Keyboard Layout "Germany Neo 2": Mod4 does not work if used as
secondary keyboard layout
Status in xkeyboard-config package in Ubuntu:
Confirmed
Bug description:
If Neo 2 is used as secondary keyboard layout, Layer 4 and 6 (that is,
Mod4) don't work. To reproduce this bug, do the following:
1: Neo 2 as primary keyboard layout
- start gnome-keyboard-properties
- Click "Add..."
- Select Country: "Germany" and Variants: "Germany Neo 2"
- Select "Germany Neo 2" and move it to the top of the list.
Try to use Neo Layer 4 or 6. E.g. type the number "4" which is "Mod4" and "n"
in Neo ("<" and "j" in standard German QWERTZ layout) or move the cursor left
using "Mod4" and "i" ("AltGr" and "s" in QWERTZ layot). Works as expected.
2: Neo as secondary layout
- Now add "Germany Eliminate dead keys" to the list and move it to the top
- Use "Neo 2" as secondary layout
- Click "Options" and select "Scroll lock" (or any other) as "Key(s) to
change layout"
Now switch to Neo using the selected key and try to type "4" or move the
curser as above. Instead of Neo Layer 4 or 6 you will have Layer 1/3 (that is,
you will be typing an "n" instead of a "4" and an "i" instead of moving the
cursor left).
Choosing other keys for layout change or turning the compose key
on/off does not change anything. Neither does applying "Neo 2" as
primary layout system wide and using "Germany Eliminate dead keys"
with "Neo 2" as a secondary keyboard layout as local user.
Applying the patch suggested on neo-layout.org for a similar problem
(http://wiki.neo-layout.org/ticket/174) does not have any effect.
Description: Ubuntu 11.04
Release: 11.04
xkb-data: 2.1-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+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 1769284] Re: ssh client: blowfish-cbc required - missing in bionic
No, this is not an option. Also note, that this breaks a lot of workflows without reason, because Ubuntu ssh client simply stops working with a message like "~/.ssh/config line 3: Bad SSH2 cipher spec '...'": it simply does not know such ciphers (does not ignore them). So especially in environments with shared homes bionic (the usual case in enterprises?) cannot be deployed (and telling people, that they need to use different options when the are on bionic, is simply is useless pain for the users as well as company hotlines). Ubuntu should do, what all major enterprise ready distributions/unices do, i.e. bundle support for those ciphers for backward compatibility, but disable them per default). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1769284 Title: ssh client: blowfish-cbc required - missing in bionic Status in openssh package in Ubuntu: Won't Fix Status in openssh-ssh1 package in Ubuntu: Fix Released Bug description: In bionic openssh client/server ships without blowfish-cbc, arcfour, arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required for backward compatibility, especially for embedded devices, which do not support other ciphers (e.g. Rittal Liquid Cooling Package for racks). So disable them per default is ok, but one should still be able to use them on demand for older, non-upgradable HW/SW envs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1769284/+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 1769284] [NEW] ssh client: blowfish-cbc required - missing in bionic
Public bug reported: In bionic openssh client/server ships without blowfish-cbc, arcfour, arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required for backward compatibility, especially for embedded devices, which do not support other ciphers (e.g. Rittal Liquid Cooling Package for racks). So disable them per default is ok, but one should still be able to use them on demand for older, non-upgradable HW/SW envs. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1769284 Title: ssh client: blowfish-cbc required - missing in bionic Status in openssh package in Ubuntu: New Bug description: In bionic openssh client/server ships without blowfish-cbc, arcfour, arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required for backward compatibility, especially for embedded devices, which do not support other ciphers (e.g. Rittal Liquid Cooling Package for racks). So disable them per default is ok, but one should still be able to use them on demand for older, non-upgradable HW/SW envs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1769284/+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 1753216] [NEW] dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor
Public bug reported: Fehlermeldung: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor beim Installieren eines deb-Paketes mit Paket-Instalaationsprogramm Description:Ubuntu Bionic Beaver (development branch) Release:18.04 gdebi: Installiert: 0.9.5.7+nmu2 Installationskandidat: 0.9.5.7+nmu2 Versionstabelle: *** 0.9.5.7+nmu2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Package changed: deja-dup (Ubuntu) => gdebi (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1753216 Title: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor Status in gdebi package in Ubuntu: New Bug description: Fehlermeldung: dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor beim Installieren eines deb-Paketes mit Paket-Instalaationsprogramm Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 gdebi: Installiert: 0.9.5.7+nmu2 Installationskandidat: 0.9.5.7+nmu2 Versionstabelle: *** 0.9.5.7+nmu2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1753216/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
I followed the steps from #27 and everything works fine now on 16.04.3 with a SuperMicro Board X11SSH-F with Intel C236 Chipsets RST and two sata disks as Raid 1. I can also confirm #28, the first reboot still needed a hard reset and a rebuild of the Raid 1, but after this, every (>10) shutdown and reboot was OK. And the solution still is alive after an update on the newest 4.4.0-116 kernel today. Sorry for testing delay, but after missing a solution for too long time, we installed our servers different way, only this week I got a new testing machine until 18.04 is out. -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
I found another workaround, that works fine without changing package versions or DNS servers. It is tested with the issues I had with openconnect for NM. it is "just" killing the dnsmasq instance and it gets restarted automatically which then results in a working system again. It easy and not pretty, but works. Then only (perhaps) noticeable interruption is a few seconds where DNS is not working 15 seconds after the connection has been established: $ cat /etc/NetworkManager/dispatcher.d/99-openconnect-dnsmasq-bug #!/bin/bash set -e # force restart of dnsmasq on vpn connect if [[ "$1" =~ "vpn" ]] && [ $2 = "up" ] then if [ -e /var/run/NetworkManager/dnsmasq.pid ] then $( sleep 15 && /bin/kill -15 $(cat /var/run/NetworkManager/dnsmasq.pid) ) fi fi -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
I can confirm the workaround in #92 for my 16.04.3 LTS installation. -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions. Please see wall of text on comment 50 for a long excuse. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1745475] Re: Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3
** Summary changed: - Broken eventless 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3 + Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1745475 Title: Broken eventlet 0.20.0 with python2.7 2.7.12-1ubuntu0~16.04.3 Status in python2.7 package in Ubuntu: Confirmed Bug description: Recently we found in Neutron bug described in https://bugs.launchpad.net/neutron/+bug/1745013 It looks that there is problem with eventlet.monkey_patch() when using eventlet < 0.22.0 and python2.7 2.7.12-1ubuntu0~16.04.3 Details of issue can be found in Neutron's bug report. It looks that breaking change can be related to fix for https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1512068 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1745475/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner
Lenovo Ideapad 2 13 (2 in 1 convertible, touchscreen) Ubuntu 18.04 (+ 17.10, + 16.04) even after installing 18.04 and the latest updates on Jan 2nd 2018 the following feature persists: a few times a week the cursor goes nuts - it looks like it's jumping to the lower left corner (gnome desktop), clicking, and thereby calling the program tiles onto the screen. Then clicking again making the tiles disappear, clicking again calling the tiles,. sometimes with quite a high frequency. This turns the laptop pretty much useless because it's "trapped" in this state. Whatever you try it's always calling the tiles :-( This happens even if I'm not touching the notebook at all!! I couldn't find anything to influence this behavior. Even after rebooting it continues! But at some random point in time the jumping stops and the notebook can be used as before and works like a charm - until the jumping starts again. Because I used the fix from https://askubuntu.com/users/750621/keringar (Thank you!!) the on screen keyboard is not coming any more. But for me it looks that the root cause of the osk popping up is the cursor jump/click. As I have tried very many of the suggestions above and in other forums I tend to believe that it's really a bug somewhere deep inside (graphic driver?) as this bug appeared with Gnome and also Unity desktop. Solving this for good would REALLY promote the use of Ubuntu :-) -- 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/1574667 Title: Mouse pointer occasionally jumps to the bottom-left corner Status in xorg package in Ubuntu: Confirmed Bug description: Sometimes the mouse pointer jumps directly to the bottom-left corner of the screen, which results in opening the trash window when clicking. This seems to be related: https://ubuntu-mate.community/t/mouse- pointer-jumps-on-clicking-touchpad/2932. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 25 15:55:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06b2] InstallationDate: Installed on 2016-04-23 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 064e:920b Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 06CMH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 13:43:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log
[Touch-packages] [Bug 1739862] [NEW] package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welc
Public bug reported: 6.0-8ubuntu1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 AptOrdering: libperl5.26:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Dec 23 08:49:56 2017 DpkgTerminalLog: Vorbereitung zum Entpacken von .../libperl5.26_5.26.0-8ubuntu1_i386.deb ... Entpacken von libperl5.26:i386 (5.26.0-8ubuntu1) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist InstallationDate: Installed on 2017-09-03 (110 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist UpgradeStatus: Upgraded to artful on 2017-10-30 (53 days ago) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1739862 Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist Status in perl package in Ubuntu: New Bug description: 6.0-8ubuntu1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libperl5.26 5.26.0-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 AptOrdering: libperl5.26:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Dec 23 08:49:56 2017 DpkgTerminalLog: Vorbereitung zum Entpacken von .../libperl5.26_5.26.0-8ubuntu1_i386.deb ... Entpacken von libperl5.26:i386 (5.26.0-8ubuntu1) ... dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/libperl5.26_5.26.0-8ubuntu1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist InstallationDate: Installed on 2017-09-03 (110 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: perl Title: package libperl5.26 5.26.0-8ubuntu1 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.26:i386 ist UpgradeStatus: Upgraded to artful on 2017-10-30 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1739862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 @rouniy @m-witte-d Hi, locking down the packages resulted in breaking gdm3 in my installation of ubuntu-gnome 16.04.4. That's because gdm3 has a inherited dependency on libnm0 (>= 1.2.6-0ubuntu0.16.04.2) from gir1.2-networkmanager-1.0. It might work going down the dependencies and lock down even more packages, but I don't have a good feeling when locking down more and more packages. BTW: I am using network-manager-openconnect and network-manager- openconnect-gnome both in version 1.2.0-0ubuntu0.16.04.1. And the "killall dnsmasq" gets the system back into working order, but e.g. KVM NAT network connections are having issues as dnsmasq is used for that setup. -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
Same here, sample ps auxf output: http://paste.ubuntu.com/26112646/ In the upgrade there was a systemd update at the same time as the other package update, which seems to be the trigger according to the debian bug. ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent Status in systemd package in Ubuntu: Confirmed Status in systemd package in Debian: Fix Released Bug description: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+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 1676829] Re: Mic input volume always resets (to middle/low value) on resume or restart
properties: alsa.card = "0" alsa.card_name = "HDA Intel PCH" alsa.long_card_name = "HDA Intel PCH at 0xf434 irq 142" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:00:1f.3" sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "a171" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" In my case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1676829 Title: Mic input volume always resets (to middle/low value) on resume or restart Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sound card: CA0106/CA0111 Each time I start PC - mic input volume resets to some "default" value. This happens from 16.04 (maybe earlier). Now I have 17.04, still have it. Each time I run: 1) alsamixer 2) select input device, "Line In" 3) set it to max. (Or same actions in Ubuntu GUI) Then (after restart or suspend) the volume goes back to some middle value (low for me). I'm pissed off setting it back again and again. Does someone else have this problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1676829/+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 1676829] Re: Mic input volume always resets (to middle/low value) on resume or restart
Confirmed, except for me it always resets to 100%. That's far too high, I need it to be around 50% or so. Either way, the resetting is very annoying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1676829 Title: Mic input volume always resets (to middle/low value) on resume or restart Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sound card: CA0106/CA0111 Each time I start PC - mic input volume resets to some "default" value. This happens from 16.04 (maybe earlier). Now I have 17.04, still have it. Each time I run: 1) alsamixer 2) select input device, "Line In" 3) set it to max. (Or same actions in Ubuntu GUI) Then (after restart or suspend) the volume goes back to some middle value (low for me). I'm pissed off setting it back again and again. Does someone else have this problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1676829/+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 991666] Re: VPN Connects Successfully & Then Shortly Thereafter Fails
Hi, had the same problem with a pptp vpn (don't ask why we use pptp). As described i had to set the MTU of the physical network adapter (e.g. eth0) to 1000 to get the VPN working without disconnectes all the time. You can set the MTU easily via the network manager on the "ethernet" tab, but you have to restart the network stack before it gets activated (just diconnect and reconnect you normal network connection via network manager). You can find the current value of the MTU with ifconfig ... -- 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/991666 Title: VPN Connects Successfully & Then Shortly Thereafter Fails Status in network-manager-pptp: New Status in network-manager package in Ubuntu: Confirmed Bug description: I am able to successfully establish a PPTP VPN connection in Ubuntu 12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to 1.5 minutes it will fail. During the connection time I am only able to load about 1-2 webpages and then they freeze and I cannot access resources on the VPN network. I do not believe this is related to my VPN server as I am able to establish VPN connections with my Windows machines and Smartphones all day long with no problems. Is there a solution to this problem? Description: Ubuntu 12.04 LTS Release: 12.04 network-manager: 0.9.4.0-0ubuntu3 Here is the syslog: Apr 30 00:17:50 satellite-p755 NetworkManager[994]: Starting VPN service 'pptp'... Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 15069 Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' appeared; activating connections Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN plugin state changed: starting (3) Apr 30 00:17:51 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (Connect) reply received. Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 <--> /dev/pts/2 Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 0). Apr 30 00:17:55 satellite-p755 pppd[15073]: CHAP authentication succeeded Apr 30 00:17:55 satellite-p755 pppd[15073]: MPPE 128-bit stateless compression enabled Apr 30 00:17:55 satellite-p755 pppd[15073]: local IP address 192.168.1.20 Apr 30 00:17:55 satellite-p755 pppd[15073]: remote IP address 192.168.1.1 Apr 30 00:17:55 satellite-p755 pppd[15073]: primary DNS address 8.8.8.8 Apr 30 00:17:55 satellite-p755 pppd[15073]: secondary DNS address 8.8.4.4 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (IP Config Get) reply received. Apr 30 00:17:55 satellite-p755 NetworkManager[994]: VPN Gateway: 75.75.79.330 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Tunnel Device: ppp0 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Address: 192.168.1.20 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Prefix: 32 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Point-to-Point Address: 192.168.1.1 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Maximum Segment Size (MSS): 0 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Forbid Default Route: no Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 DNS: 8.8.8.8
[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error
Actually this is the problem: Users think, their system is up-to-date, but it is not for sure because a site failed to respond. Therefore only if _all_ sites answered the request properly, apt-get should return 0. If not, it should return a specified return code, which lets the callee know, that there was a problem [and imply, that a subsequent apt-get upgrade might bring the system to the latest supported state, or not]. If the exit code for such situations is documented properly, the tool can still decide, whether to run the upgrade or would be bredless art. BTW: It doesn't really matter, what error (whether temp. DNS, LDAP lookup, network, etc.) prevented a successful update. Fact is, that there was an error and this needs to be communicated. CLI tools do that via exit code. -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Triaged Bug description: When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1693900] Re: apt-get update should return exit code != 0 on error
The bug/subject here is, that apt-get doesn't return a proper exit code, not, what else one could use to workaround the bug. Saying, that update from one of all (i.e. 1+) sites is sufficient is like going to fly with a jet, where one of two engines is already broken before it starts. Making this decision for yourself is ok, but making it for all other passengers is IMHO irresponsible. -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Triaged Bug description: When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1564451] Re: User processes are counted towards systemd limit for sshd processes (add libpam-systemd to openssh-server)
This seems to have been solved by https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1561658, which could be considered a duplicate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1564451 Title: User processes are counted towards systemd limit for sshd processes (add libpam-systemd to openssh-server) Status in systemd: New Status in openssh package in Ubuntu: Incomplete Bug description: When running Xenial, user processes are counted towards the limit for the ssh.service, with a limit of 512. So if I login as a normal user via ssh and start 512 processes, nobody will be able to login any more and even all other users currently logged in will not be able to start any new tasks. I'm not certain whether this behaviour is by design, but to me it looks like a critical DOS possibility, so tagging as security bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1564451/+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 1693900] Re: apt-get update should return exit code != 0 on error
Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not able to update properly and thus the result of the operation is unreliable. So its like "your connection is secured, but may be not". I guess most people wouldn't do any financial transaction when reading this ... ;-) -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: Triaged Bug description: When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1693900] [NEW] apt-get update should return exit code != 0 on error
Public bug reported: When running 'apt-get update' (e.g. on a container install post-install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1693900 Title: apt-get update should return exit code != 0 on error Status in apt package in Ubuntu: New Bug description: When running 'apt-get update' (e.g. on a container install post- install script), apt-get return with exit code 0, even so it wasn't able to "update" properly. E.g.: + apt-get update Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease Temporary failure resolving 'de.archive.ubuntu.com' Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease Temporary failure resolving 'security.ubuntu.com' Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease Temporary failure resolving 'de.archive.ubuntu.com' Reading package lists... Done W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease Temporary failure resolving 'de.archive.ubuntu.com' W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease Temporary failure resolving 'security.ubuntu.com' W: Some index files failed to download. They have been ignored, or old ones used instead. It should be corrected to return useful exit code, so that scripts can take the appropriate actions ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900/+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 1692109] Re: mount is broken/misbehaving
AFAICS the problem is libmount/src/context_mount.c:exec_helper() which is uses operands in a wrong/not posixly incorrect way. See also http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1692109 Title: mount is broken/misbehaving Status in util-linux package in Ubuntu: New Bug description: "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil rpool/zones/bla /zones/bla" fails, if env var POSIXLY_CORRECT is set, because it calls "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously a bug. Options should always come first and operands last ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1692109/+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 1692109] Re: mount is broken/misbehaving
mount from util-linux 2.27.1 (libmount 2.27.0: selinux, assert, debug) Description:Ubuntu 16.04.2 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1692109 Title: mount is broken/misbehaving Status in util-linux package in Ubuntu: New Bug description: "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil rpool/zones/bla /zones/bla" fails, if env var POSIXLY_CORRECT is set, because it calls "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously a bug. Options should always come first and operands last ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1692109/+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 1692109] [NEW] mount is broken/misbehaving
Public bug reported: "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil rpool/zones/bla /zones/bla" fails, if env var POSIXLY_CORRECT is set, because it calls "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously a bug. Options should always come first and operands last ... ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1692109 Title: mount is broken/misbehaving Status in util-linux package in Ubuntu: New Bug description: "/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil rpool/zones/bla /zones/bla" fails, if env var POSIXLY_CORRECT is set, because it calls "/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously a bug. Options should always come first and operands last ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1692109/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Same problem with a SuperMicro Board X11SSH-F with Intel C236 Chipset and two sata disks. Installing the server with bios sata mode "RAID" and a RAID1 configured in the Intel Raid bios (Ctrl+I), on a fresh Ubuntu install and also on updated Ubuntu 16.04.2 the server doesn't restart or shutdown, it hangs at "Reached target shutdown". Installing the server with bios sata mode "AHCI", so without configuring something in the Intel Raid bios, but configuring a RAID1 only direct at Ubuntu as mdraid, restart and shutdown work fine with fresh install and also with all updates to 16.04.2 as expected. May I ask, if this bug will be solved in the future, and if there is a timeline? We planned to buy a lot of this servers, install Ubuntu and put them in a data centre miley away, but we can't wait another year. It someone in Germany really is able and willing to solve this bug, I would be willing to lend our server for some weeks. Regards, Jens -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759
[Touch-packages] [Bug 1690891] [NEW] RFE: remove ureadahead from package minimal
Public bug reported: Since on common platforms ureadahead solves nothing but causes a huge amount of garbage/totally useless error messages, which makes it really hard to extract the important messages from e.g. journalctl output, it should be removed from ubuntu-minimal. If there are people, who need it, can still explicitly install it. ** Affects: ureadahead (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1690891 Title: RFE: remove ureadahead from package minimal Status in ureadahead package in Ubuntu: New Bug description: Since on common platforms ureadahead solves nothing but causes a huge amount of garbage/totally useless error messages, which makes it really hard to extract the important messages from e.g. journalctl output, it should be removed from ubuntu-minimal. If there are people, who need it, can still explicitly install it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1690891/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
I am another Dell XPS 15 owner who is affected by this bug using 16.10.
Please incorporate the fix as soon as possible, as the normal end user
(e.g. my wife) is not willing to kill dnsmasq each time the notebook
wakes up from suspend.
--
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/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
Fix Released
Status in dnsmasq source package in Xenial:
In Progress
Status in dnsmasq source package in Yakkety:
In Progress
Status in dnsmasq package in Debian:
Fix Released
Bug description:
[Impact]
* suspend/resume (which involves disconnection of network devices)
leads to dnsmasq failures.
[Test Case]
* suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
failures upon resume.
[Regression Potential]
* The fix was NMU'd in Debian in the version immediately after
16.10's. I believe the regression potential is very low as this is a
clear bug-fix from upstream.
---
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
I've tried to reproduce this on a yakkety cloud instance as well as with lxc for some time, but sadly with no success. So I'm not sure whether this is still present in yakkety at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Unknown Status in systemd: Unknown Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Fix Committed Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original Description] I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to:
[Touch-packages] [Bug 1637123] [NEW] mythtv-frontend: missing dependencies
Public bug reported: After a clean install of Ubuntu 16.10 it is not possible to install the package "mythtv-frontend" because it depends on the package "transcode". The package "transcode" is not available anymore. It seems that in 16.10 a special package for transcoding purposes in mythtv was created. But the package dependencies were not adjusted. BTW: I cannot install Cinnamon due to unresolved dependecies too. Are there more "dead dependencies" in 16.10? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: packaging -- 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/1637123 Title: mythtv-frontend: missing dependencies Status in network-manager package in Ubuntu: New Bug description: After a clean install of Ubuntu 16.10 it is not possible to install the package "mythtv-frontend" because it depends on the package "transcode". The package "transcode" is not available anymore. It seems that in 16.10 a special package for transcoding purposes in mythtv was created. But the package dependencies were not adjusted. BTW: I cannot install Cinnamon due to unresolved dependecies too. Are there more "dead dependencies" in 16.10? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1637123/+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 1565804] Re: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists
*** This bug is a duplicate of bug 1224007 *** https://bugs.launchpad.net/bugs/1224007 ** This bug has been marked a duplicate of bug 1224007 mtu not always set properly on bond/vlan interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1565804 Title: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists Status in ifupdown package in Ubuntu: Confirmed Bug description: /e/n/i: auto lo iface lo inet loopback dns-nameservers 10.245.168.2 dns-search dellstack auto eth0 iface eth0 inet static gateway 10.245.168.1 address 10.245.168.17/21 dns-nameservers 10.245.168.2 mtu 1500 auto eth1 iface eth1 inet manual mtu 1500 auto eth1.2667 iface eth1.2667 inet static address 10.245.184.20/24 vlan-raw-device eth1 mtu 9000 vlan_id 2667 output from networking startup: ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf Active: failed (Result: exit-code) since Mon 2016-04-04 12:14:26 UTC; 1h 33min ago Docs: man:interfaces(5) Process: 1255 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 868 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, Main PID: 1255 (code=exited, status=1/FAILURE) Apr 04 12:14:25 reflecting-attraction systemd[1]: Starting Raise network interfaces... Apr 04 12:14:26 reflecting-attraction ifup[1255]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Apr 04 12:14:26 reflecting-attraction ifup[1255]: RTNETLINK answers: File exists Apr 04 12:14:26 reflecting-attraction ifup[1255]: Failed to bring up eth1.2667. Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Apr 04 12:14:26 reflecting-attraction systemd[1]: Failed to start Raise network interfaces. Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Unit entered failed state. Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: User Name 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 4 13:42:48 2016 SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1565804/+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 1630191] Re: MTU settings not always applied after reboot
*** This bug is a duplicate of bug 1224007 *** https://bugs.launchpad.net/bugs/1224007 ** This bug has been marked a duplicate of bug 1224007 mtu not always set properly on bond/vlan interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1630191 Title: MTU settings not always applied after reboot Status in ifupdown package in Ubuntu: New Bug description: On a node with two 10G interfaces, we configure a bond interface from these two interfaces and then a vlan interface on top of it. The MTU of these interfaces shall be set to be 1550 instead of the default 1500, so we have these settings in /etc/network/interfaces.d: root@controller-node13:~# cat /etc/network/interfaces.d/xge0 auto xge0 iface xge0 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xge1 auto xge1 iface xge1 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xiondata auto xiondata iface xiondata inet manual bond-slaves xge0 xge1 bond-miimon 100 bond-lacp-rate 1 bond-mode 4 mtu 1550 root@controller-node13:~# cat /etc/network/interfaces.d/xiondata.200 auto xiondata.200 iface xiondata.200 inet static address 10.80.1.13/24 vlan_raw_device xiondata mtu 1550 After a reboot, the correct MTU is applied to the vlan interface only 50% of the time, on the other attempts, it stays at 1500, leading to broken connectivity. If I restart the interfaces manually, by doing "ifdown xiondata; ifup -a" the MTU settings seem to be applied correctly every time. root@controller-node13:~# apt policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 500 500 http://eu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 09:44:40 2016 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1630191/+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 1630191] [NEW] MTU settings not always applied after reboot
Public bug reported: On a node with two 10G interfaces, we configure a bond interface from these two interfaces and then a vlan interface on top of it. The MTU of these interfaces shall be set to be 1550 instead of the default 1500, so we have these settings in /etc/network/interfaces.d: root@controller-node13:~# cat /etc/network/interfaces.d/xge0 auto xge0 iface xge0 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xge1 auto xge1 iface xge1 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xiondata auto xiondata iface xiondata inet manual bond-slaves xge0 xge1 bond-miimon 100 bond-lacp-rate 1 bond-mode 4 mtu 1550 root@controller-node13:~# cat /etc/network/interfaces.d/xiondata.200 auto xiondata.200 iface xiondata.200 inet static address 10.80.1.13/24 vlan_raw_device xiondata mtu 1550 After a reboot, the correct MTU is applied to the vlan interface only 50% of the time, on the other attempts, it stays at 1500, leading to broken connectivity. If I restart the interfaces manually, by doing "ifdown xiondata; ifup -a" the MTU settings seem to be applied correctly every time. root@controller-node13:~# apt policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 500 500 http://eu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 09:44:40 2016 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1630191 Title: MTU settings not always applied after reboot Status in ifupdown package in Ubuntu: New Bug description: On a node with two 10G interfaces, we configure a bond interface from these two interfaces and then a vlan interface on top of it. The MTU of these interfaces shall be set to be 1550 instead of the default 1500, so we have these settings in /etc/network/interfaces.d: root@controller-node13:~# cat /etc/network/interfaces.d/xge0 auto xge0 iface xge0 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xge1 auto xge1 iface xge1 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xiondata auto xiondata iface xiondata inet manual bond-slaves xge0 xge1 bond-miimon 100 bond-lacp-rate 1 bond-mode 4 mtu 1550 root@controller-node13:~# cat /etc/network/interfaces.d/xiondata.200 auto xiondata.200 iface xiondata.200 inet static address 10.80.1.13/24 vlan_raw_device xiondata mtu 1550 After a reboot, the correct MTU is applied to the vlan interface only 50% of the time, on the other attempts, it stays at 1500, leading to broken connectivity. If I restart the interfaces manually, by doing "ifdown xiondata; ifup -a" the MTU settings seem to be applied correctly every time. root@controller-node13:~# apt policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 500 500 http://eu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 09:44:40 2016 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1630191/+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 1624415] [NEW] tcsh coredumps all the time on tab
Public bug reported: When a users having tcsh as its [login] shell presses tab key (autocompletion), tcsh coredumps immediately, always: admin.python ~ > gdb tcsh GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git ... (gdb) run Starting program: /local/home/admin/tcsh admin.python ~ > ls . Suspended (tty output) admin.python ~ > fg gdb tcsh Program received signal SIGSEGV, Segmentation fault. __GI___rewinddir (dirp=0x771808) at ../sysdeps/posix/rewinddir.c:34 34 ../sysdeps/posix/rewinddir.c: No such file or directory. (gdb) quit A debugging session is active. Inferior 1 [process 25990] will be killed. Quit anyway? (y or n) y admin.python ~ > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Codename: yakkety ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1624415 Title: tcsh coredumps all the time on tab Status in apport package in Ubuntu: New Bug description: When a users having tcsh as its [login] shell presses tab key (autocompletion), tcsh coredumps immediately, always: admin.python ~ > gdb tcsh GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git ... (gdb) run Starting program: /local/home/admin/tcsh admin.python ~ > ls . Suspended (tty output) admin.python ~ > fg gdb tcsh Program received signal SIGSEGV, Segmentation fault. __GI___rewinddir (dirp=0x771808) at ../sysdeps/posix/rewinddir.c:34 34../sysdeps/posix/rewinddir.c: No such file or directory. (gdb) quit A debugging session is active. Inferior 1 [process 25990] will be killed. Quit anyway? (y or n) y admin.python ~ > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1624415/+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 1580577] Re: python2.7 crashes with SegFault when running Zope
Sorry for impatience. I just found it is already in proposed updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1580577
Title:
python2.7 crashes with SegFault when running Zope
Status in python2.7 package in Ubuntu:
Confirmed
Bug description:
Source package / Package:
python2.7_2.7.11-7ubuntu1
System:
Description: Ubuntu 16.04 LTS
Release: 16.04
This is a bug report originating from the findings documented in
https://github.com/zopefoundation/Zope/issues/56
The expected behaviour is this:
- Upon installing Zope2 in a virtualenv a default instance should work with
no issues.
What happens instead:
- The freshly installed Zope instance causes Python to SegFault after only a
few requests.
But Python should never SegFault.
The following program produces the error:
#!/bin/bash
set -e
# Call this testing script with an argument "setup" for the first time
# to build the testing case
#
# After that, the script only performs the test as described below.
#
# Requirements: apt-get install virtualenv python2.7-dbg
#
# This script needs internet access when running.
# The python version to test:
python=/usr/bin/python2.7-dbg
# This part builds the testing environment
if [ "$1" == "setup" ] ; then
# Virtual environment with the chosen python
virtualenv --python ${python} --no-site-packages zope-virtualenv
cd zope-virtualenv
# Basic Zope installation
./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
# Simplest possible Zope instance
./bin/mkzopeinstance --dir instance --user admin:admin
cd ..
fi
# THE TEST
# Run Zope instance in the background
zope-virtualenv/instance/bin/runzope &
# Give Zope some time to start up
sleep 3
# Call a few management URLs, nothing too fancy...
urls="
http://admin:admin@localhost:8080/Control_Panel/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
http://admin:admin@localhost:8080/manage
http://admin:admin@localhost:8080/acl_users/manage_main
http://admin:admin@localhost:8080/acl_users/manage_access
"
while true ; do
for url in ${urls} ; do
echo ${url}
curl -s $url -o /dev/null
done
done
# This test fails after about 10 requests with
# Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has
negative ref count -1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+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 1580577] Re: python2.7 crashes with SegFault when running Zope
Any update if this fix will go into 16.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1580577
Title:
python2.7 crashes with SegFault when running Zope
Status in python2.7 package in Ubuntu:
Confirmed
Bug description:
Source package / Package:
python2.7_2.7.11-7ubuntu1
System:
Description: Ubuntu 16.04 LTS
Release: 16.04
This is a bug report originating from the findings documented in
https://github.com/zopefoundation/Zope/issues/56
The expected behaviour is this:
- Upon installing Zope2 in a virtualenv a default instance should work with
no issues.
What happens instead:
- The freshly installed Zope instance causes Python to SegFault after only a
few requests.
But Python should never SegFault.
The following program produces the error:
#!/bin/bash
set -e
# Call this testing script with an argument "setup" for the first time
# to build the testing case
#
# After that, the script only performs the test as described below.
#
# Requirements: apt-get install virtualenv python2.7-dbg
#
# This script needs internet access when running.
# The python version to test:
python=/usr/bin/python2.7-dbg
# This part builds the testing environment
if [ "$1" == "setup" ] ; then
# Virtual environment with the chosen python
virtualenv --python ${python} --no-site-packages zope-virtualenv
cd zope-virtualenv
# Basic Zope installation
./bin/easy_install -i http://download.zope.org/Zope2/index/2.13.24 Zope2
# Simplest possible Zope instance
./bin/mkzopeinstance --dir instance --user admin:admin
cd ..
fi
# THE TEST
# Run Zope instance in the background
zope-virtualenv/instance/bin/runzope &
# Give Zope some time to start up
sleep 3
# Call a few management URLs, nothing too fancy...
urls="
http://admin:admin@localhost:8080/Control_Panel/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/manage_main
http://admin:admin@localhost:8080/Control_Panel/Database/main/manage_activity
http://admin:admin@localhost:8080/manage
http://admin:admin@localhost:8080/acl_users/manage_main
http://admin:admin@localhost:8080/acl_users/manage_access
"
while true ; do
for url in ${urls} ; do
echo ${url}
curl -s $url -o /dev/null
done
done
# This test fails after about 10 requests with
# Fatal Python error: ../Objects/descrobject.c:10 object at 0x??? has
negative ref count -1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1580577/+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 1578141] Re: Predictable interface names partially broken with igb driver
@Martin: Fixing the installed system is easy, the bad case happens when the installer sets up the system with "rename2" as the first interface, making access via console necessary in order to recover. root@compute-node37:~# SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id /sys/class/net/eno1 calling: test-builtin === trie on-disk === tool version: 229 file size: 6841778 bytes header size 80 bytes strings1755242 bytes nodes 5086456 bytes Load module index timestamp of '/etc/systemd/network' changed timestamp of '/lib/systemd/network' changed Parsed configuration file /lib/systemd/network/99-default.link Parsed configuration file /lib/systemd/network/90-mac-for-usb.link Created link configuration context. ID_NET_NAME_MAC=enx002590d8975a ID_OUI_FROM_DATABASE=Super Micro Computer, Inc. ID_NET_NAME_ONBOARD=eno1 ID_NET_NAME_PATH=enp7s0f0 Unload module index Unloaded link configuration context. root@compute-node37:~# SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id /sys/class/net/rename3 calling: test-builtin === trie on-disk === tool version: 229 file size: 6841778 bytes header size 80 bytes strings1755242 bytes nodes 5086456 bytes Load module index timestamp of '/etc/systemd/network' changed timestamp of '/lib/systemd/network' changed Parsed configuration file /lib/systemd/network/99-default.link Parsed configuration file /lib/systemd/network/90-mac-for-usb.link Created link configuration context. ID_NET_NAME_MAC=enx002590d8975b ID_OUI_FROM_DATABASE=Super Micro Computer, Inc. ID_NET_NAME_ONBOARD=eno1 ID_NET_NAME_PATH=enp7s0f1 Unload module index Unloaded link configuration context. Also note that the whole renaming process seems to come from an Ubuntu specific patch in Revert-udev-network-device-renaming-immediately- give.patch, IIUC plain systemd would fail the renaming process and end up with either (eno1, eth1) or (eth0, eno1) as interface tuples. If there was a way to get rid of the race condition and make sure that the system always ends up with the same tuple, that would already be a large step forward. -- 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/1578141 Title: Predictable interface names partially broken with igb driver Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Note: I'm not sure whether this is really a kernel bug or something within systemd/udev, please advise how to further debug. On a system with two GE ports, instead of getting named eno1 and eno2, I am getting eno1 and renameN. Where N starts at 3 and increases by 2 on every iteration of doing "rmmod igb;modprobe igb". The corresponding lines in dmesg look like this: [2.748429] igb :07:00.0: added PHC on eth0 [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e [2.748505] igb :07:00.0: eth0: PBA No: 106100-000 [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.802555] igb :07:00.1: added PHC on eth1 [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f [2.802631] igb :07:00.1: eth1: PBA No: 106100-000 [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.803618] igb :07:00.0 eno1: renamed from eth0 [2.833208] igb :07:00.1 rename3: renamed from eth1 What is even worse: Sometimes the naming changes and the second interface ends up as eno1 while the first interface is named renameN with an even N. The bad thing about this version is that when it happens while the installer is running, the installer will setup "rename2" as the primary network interface, which works fine for the installation itself, but after installation is finished and the first boot of the installed system happens, that interface will be gone, leaving the system without network connectivity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 4 09:48 seq crw-rw 1 root audio 116, 33 May 4 09:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
[Touch-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver
Looking further, it seems that the BIOS is providing broken information, see this snippet from dmidecode output: Handle 0x007E, DMI type 41, 11 bytes Onboard Device Reference Designation: Onboard Intel Ethernet 1 Type: Ethernet Status: Enabled Type Instance: 1 Bus Address: :07:00.0 Handle 0x007F, DMI type 41, 11 bytes Onboard Device Reference Designation: Onboard Intel Ethernet 2 Type: Ethernet Status: Enabled Type Instance: 1 Bus Address: :07:00.1 and as a result we get ID_NET_NAME_ONBOARD=eno1 for both devices. So udev tries to rename both interfaces to eno1, only one succeeds, the other one fails due to a name collision. Would be nice to implement a workaround for these broken BIOS data. -- 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/1578141 Title: Predictable interface names partially broken with igb driver Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Note: I'm not sure whether this is really a kernel bug or something within systemd/udev, please advise how to further debug. On a system with two GE ports, instead of getting named eno1 and eno2, I am getting eno1 and renameN. Where N starts at 3 and increases by 2 on every iteration of doing "rmmod igb;modprobe igb". The corresponding lines in dmesg look like this: [2.748429] igb :07:00.0: added PHC on eth0 [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e [2.748505] igb :07:00.0: eth0: PBA No: 106100-000 [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.802555] igb :07:00.1: added PHC on eth1 [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f [2.802631] igb :07:00.1: eth1: PBA No: 106100-000 [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.803618] igb :07:00.0 eno1: renamed from eth0 [2.833208] igb :07:00.1 rename3: renamed from eth1 What is even worse: Sometimes the naming changes and the second interface ends up as eno1 while the first interface is named renameN with an even N. The bad thing about this version is that when it happens while the installer is running, the installer will setup "rename2" as the primary network interface, which works fine for the installation itself, but after installation is finished and the first boot of the installed system happens, that interface will be gone, leaving the system without network connectivity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 4 09:48 seq crw-rw 1 root audio 116, 33 May 4 09:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed May 4 10:00:39 2016 HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT-HF+ PciMultimedia: ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT-HF+ dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag:
[Touch-packages] [Bug 1578141] Re: Predictable interface names partially broken with igb driver
We have seen the issue only when deploying Xenial, installations running Precise or Trusty do not seem to be affected. Running with 4.6.0-040600rc6-generic has shown the same behaviour. After doing the rmmod/modprobe cycle, I have now found the attached set of messages in the output of "journalctl -x", so this seems to confirm my suspicion of some bad interaction between kernel and systemd going on. ** Attachment added: "Output of "journalctl -x" when doing "rmmod igb;sleep 3;modprobe igb"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141/+attachment/4657073/+files/journal.txt ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1578141 Title: Predictable interface names partially broken with igb driver Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Note: I'm not sure whether this is really a kernel bug or something within systemd/udev, please advise how to further debug. On a system with two GE ports, instead of getting named eno1 and eno2, I am getting eno1 and renameN. Where N starts at 3 and increases by 2 on every iteration of doing "rmmod igb;modprobe igb". The corresponding lines in dmesg look like this: [2.748429] igb :07:00.0: added PHC on eth0 [2.748431] igb :07:00.0: Intel(R) Gigabit Ethernet Network Connection [2.748433] igb :07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e [2.748505] igb :07:00.0: eth0: PBA No: 106100-000 [2.748506] igb :07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.802555] igb :07:00.1: added PHC on eth1 [2.802557] igb :07:00.1: Intel(R) Gigabit Ethernet Network Connection [2.802559] igb :07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f [2.802631] igb :07:00.1: eth1: PBA No: 106100-000 [2.802632] igb :07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s) [2.803618] igb :07:00.0 eno1: renamed from eth0 [2.833208] igb :07:00.1 rename3: renamed from eth1 What is even worse: Sometimes the naming changes and the second interface ends up as eno1 while the first interface is named renameN with an even N. The bad thing about this version is that when it happens while the installer is running, the installer will setup "rename2" as the primary network interface, which works fine for the installation itself, but after installation is finished and the first boot of the installed system happens, that interface will be gone, leaving the system without network connectivity. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 4 09:48 seq crw-rw 1 root audio 116, 33 May 4 09:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed May 4 10:00:39 2016 HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT-HF+ PciMultimedia: ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT-HF+ dmi.board.vendor: Supermicro dmi.board.version: 0123456789
[Touch-packages] [Bug 1564922] Re: Warning messages during package installation
** Description changed: - This log is from installing the pre-release packages, but I got the same - warnings when installing 10.0.5 earlier: + When having a custom /usr/sbin/policy-rc.d, there are various warnings + during installation, like: Preparing to unpack .../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. Unpacking ceph (10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201) over (10.0.5-0ubuntu1) ... Preparing to unpack .../ceph-common_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. - Not sure whether this is a bug in deb-systemd-invoke really. + The issue seems to be that deb-systemd-invoke is called with the + systemd-type service name, while /usr/sbin/policy-rc.d expects the "old" + service name as parameter, e.g. "ceph-mon.service" vs "ceph-mon". ** Description changed: When having a custom /usr/sbin/policy-rc.d, there are various warnings during installation, like: Preparing to unpack .../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. Unpacking ceph (10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201) over (10.0.5-0ubuntu1) ... Preparing to unpack .../ceph-common_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. The issue seems to be that deb-systemd-invoke is called with the systemd-type service name, while /usr/sbin/policy-rc.d expects the "old" - service name as parameter, e.g. "ceph-mon.service" vs "ceph-mon". + service name as parameter, e.g. "ceph-mon.service" vs "ceph-mon": + + root@controller-node11:~# /usr/sbin/policy-rc.d ceph-mon start + root@controller-node11:~# echo $? + 104 + root@controller-node11:~# /usr/sbin/policy-rc.d ceph-mon.service start + root@controller-node11:~# echo $? + 100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1564922 Title: Warning messages during package installation Status in ceph package in Ubuntu: Invalid Status in init-system-helpers package in Ubuntu: New Bug description: When having a custom /usr/sbin/policy-rc.d, there are various warnings during installation, like: Preparing to unpack .../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. Unpacking ceph (10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201) over (10.0.5-0ubuntu1) ... Preparing to unpack .../ceph-common_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. The issue seems to be that deb-systemd-invoke is called with the systemd-type service name, while /usr/sbin/policy-rc.d expects the "old" service name as parameter, e.g. "ceph-mon.service" vs "ceph- mon": root@controller-node11:~# /usr/sbin/policy-rc.d ceph-mon start root@controller-node11:~# echo $? 104 root@controller-node11:~# /usr/sbin/policy-rc.d ceph-mon.service start root@controller-node11:~# echo $? 100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1564922/+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 1564922] Re: Warning messages during package installation
I'm now seeing the warnings also in the postinst for dmeventd, so probably deb-systemd-invoke should be fixed as being the common denominator. ** Also affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1564922 Title: Warning messages during package installation Status in ceph package in Ubuntu: Invalid Status in init-system-helpers package in Ubuntu: New Bug description: This log is from installing the pre-release packages, but I got the same warnings when installing 10.0.5 earlier: Preparing to unpack .../ceph_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. Unpacking ceph (10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201) over (10.0.5-0ubuntu1) ... Preparing to unpack .../ceph-common_10.1.0.dfsg-0ubuntu1~ubuntu16.04.1~ppa201603311201_amd64.deb ... deb-systemd-invoke only supports /usr/sbin/policy-rc.d return code 101 and 104! Got return code 100, ignoring. Not sure whether this is a bug in deb-systemd-invoke really. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1564922/+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 1564451] Re: User processes are counted towards systemd limit for sshd processes
Thanks to some help in #systemd I could find the cause: On the affected systems libpam-systemd was not installed. So maybe it would make sensu to turn this into a stronger dependency than "recommended", at least in combination with openssh-server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1564451 Title: User processes are counted towards systemd limit for sshd processes Status in systemd: New Status in openssh package in Ubuntu: New Bug description: When running Xenial, user processes are counted towards the limit for the ssh.service, with a limit of 512. So if I login as a normal user via ssh and start 512 processes, nobody will be able to login any more and even all other users currently logged in will not be able to start any new tasks. I'm not certain whether this behaviour is by design, but to me it looks like a critical DOS possibility, so tagging as security bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1564451/+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 1564451] Re: User processes are counted towards systemd limit for sshd processes
Hmm, on a cloud instance this looks different, even when logged in multiple time, the output only shows the master process: # systemctl status ssh ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-04-01 06:00:11 UTC; 1h 44min ago Main PID: 971 (sshd) Tasks: 1 (limit: 512) Memory: 5.3M CPU: 169ms CGroup: /system.slice/ssh.service └─971 /usr/sbin/sshd -D Package versions are identical in both systems: root@jr-xeni1:~# apt-cache policy systemd systemd: Installed: 229-3ubuntu1 Candidate: 229-3ubuntu1 Version table: *** 229-3ubuntu1 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status root@jr-xeni1:~# apt-cache policy openssh-server openssh-server: Installed: 1:7.2p2-2 Candidate: 1:7.2p2-2 Version table: *** 1:7.2p2-2 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status So I'm wondering what else could be causing the different behaviour here. ** Also affects: systemd Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1564451 Title: User processes are counted towards systemd limit for sshd processes Status in systemd: New Status in openssh package in Ubuntu: New Bug description: When running Xenial, user processes are counted towards the limit for the ssh.service, with a limit of 512. So if I login as a normal user via ssh and start 512 processes, nobody will be able to login any more and even all other users currently logged in will not be able to start any new tasks. I'm not certain whether this behaviour is by design, but to me it looks like a critical DOS possibility, so tagging as security bug. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1564451/+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 1564451] Re: User processes are counted towards systemd limit for sshd processes
Do your sleep processes show up in the output of "systemctl status ssh.service" in the CGroup section? For me they do (sample with just one process backgrounded): # systemctl status ssh.service ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2016-04-01 05:53:59 UTC; 1min 1s ago Main PID: 2928 (sshd) Tasks: 10 (limit: 512) CGroup: /system.slice/ssh.service ├─2928 /usr/sbin/sshd -D ├─4966 sshd: jrosenboom [priv ├─5087 sshd: jrosenboom@pts/ ├─5127 -bash ├─5208 sudo -i ├─5213 sudo -i ├─5214 -bash ├─6386 sleep 100 ├─6403 systemctl status ssh.service └─6404 pager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1564451 Title: User processes are counted towards systemd limit for sshd processes Status in openssh package in Ubuntu: New Bug description: When running Xenial, user processes are counted towards the limit for the ssh.service, with a limit of 512. So if I login as a normal user via ssh and start 512 processes, nobody will be able to login any more and even all other users currently logged in will not be able to start any new tasks. I'm not certain whether this behaviour is by design, but to me it looks like a critical DOS possibility, so tagging as security bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1564451/+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 1521613] Re: Default route not installed but received in dhcp offer
This is the expected behaviour if your DHCP server also specifies a classless static route, see RFC 3442: If the DHCP server returns both a Classless Static Routes option and a Router option, the DHCP client MUST ignore the Router option. ** Changed in: isc-dhcp (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1521613 Title: Default route not installed but received in dhcp offer Status in isc-dhcp package in Ubuntu: Invalid Bug description: Hi, I am booting the ubuntu cloud image for wily (from 27-Nov-2015 22:04) in an openstack enviroment. The system comes up, gets an IP via DHCP, but no default route is being installed. A verification with dhcpdump shows that open 3, routers contains 1 entry. Attached are screenshots from an ifup and from the dhcpdump, if any further input is required please let me know. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: isc-dhcp-client 4.3.1-5ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Tue Dec 1 12:44:14 2015 DhclientLeases: Ec2AMI: ami-0009 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: None Ec2Ramdisk: None ExecutablePath: /sbin/dhclient ProcAttrCurrent: /sbin/dhclient (enforce) ProcEnviron: PATH=(custom, no user) SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1521613/+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 139097] Re: dash variable expansion error using local, readonly, and export
As dash is used to replace bash for non-interactive shells, dash should
reproduce the bash syntax of the `local` keyword as best as it can.
I agree with Dan's comment #7 "the above DASH behaviour is broken, for
all three uses "local", "export", and "readonly". BASH is correct, and
DASH should be fixed."
The "local" keyword should not change anything to the required syntax of the
assignment, e.g.
if `y=$x` works, `local y=$x` must work also!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/139097
Title:
dash variable expansion error using local, readonly, and export
Status in dash package in Ubuntu:
Confirmed
Bug description:
Binary package hint: dash
[Edited May 2010]
True for all dash up to at least May 2010.
Bug in variable expansion (incorrect word-splitting) using an assignment
with "local", "readonly", or "export in dash:
$ x='1 2 3'
$ y=$x# this works fine
$ echo "$y"
1 2 3
$ local y=$x # this fails due to dash bug
local: 2: bad variable name
$ echo "$y"
1
$ readonly y=$x# this fails due to dash bug
readonly: 2: bad variable name
$ export y=$x # this fails due to dash bug
export: 2: bad variable name
The same use of assignment using "local", "readonly" and "export" all work
fine in bash:
bash-3.2$ x='1 2 3'
bash-3.2$ y=$x
bash-3.2$ echo "$y"
1 2 3
bash-3.2$ local y=$x
bash: local: can only be used in a function
bash-3.2$ foo () {
> local y=$x
> echo "$y"
> }
bash-3.2$ foo
1 2 3
bash-3.2$ readonly y=$x # works fine
bash-3.2$ export y=$x # works fine
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/139097/+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 1347020] Re: systemd does not boot in a container
Today I upgraded our last utopic containers (~10) to vivid using do- release-upgrade: Everywhere the same: after reboot systemd is the only thing which is running in the container, but nothing else happens. It doesn't start anything! So the only way to get the stuff fixed is to manually attach to the container, do a ' ln -sf upstart /sbin/init', logout and force a lxc-stop/start of the container and do the remaining things ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Fix Released Bug description: Opening against cloud-init for now, but ultimately might end up as bug-fixes / srus against some other packages in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+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 1310104] Re: No way to trigger fingerprint authentication on lock screen
I have the same issue. Not a solution, but a good work around for me was to turn on the onscreen keyboard in the universal access settings. This leads to a (fallback?) old school login screen which has no problem with the finger print reader. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1310104 Title: No way to trigger fingerprint authentication on lock screen Status in lightdm package in Ubuntu: Confirmed Bug description: With fprintd/libpam_fprintd installed, the user can in all places authenticate via the fingerprint reader. (Command line, login screen, light locker screen). However, light locker does not interact well with fingerprint authentication: Immediately after locking the session, the user can unlock via fingerprint. But once the fingerprint authentication times out, light locker waits for a password to be typed, and the user cannot re-initiate fingerprint authentication. The usual way of pressing ESC does not have effect. There even is a state, where light locker does not accept fingerprint nor password authentication -- the user is left without any possibility to unlock the screen. This is not acceptable. Please correct light locker's behavior with respect to libpam-fprintd authentication. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 23:21:11 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-12-20 (484 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: light-locker UpgradeStatus: Upgraded to trusty on 2014-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1310104/+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 1319535] Re: Desktop animations jitter / stutter under load
This seems to have been solved after updating kernel and graphics drivers to the current LTS version backports. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1319535 Title: Desktop animations jitter / stutter under load Status in Unity: New Status in unity package in Ubuntu: New Bug description: The new desktop animations, fading etc. of windows is great. However, unlike with 12.04, all these animations - and in fact every action on the desktop that involves moving windows around - becomes noticeably slower and "stutters", when the system is under high load. (Example: MP4 encoding with Handbrake.) The system should reserve sufficient resources not to noticeably disrupt the user experience. IMHO, this is a regression since it worked under 12.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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 CurrentDesktop: Unity Date: Wed May 14 20:57:00 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7817] InstallationDate: Installed on 2014-05-12 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: MSI MS-7817 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.2:bd09/25/2013:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnToBeFilledByO.E.M.:ct3:cvr2.0: dmi.product.name: MS-7817 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed May 14 18:40:00 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputMicrosoft Microsoft Basic Optical Mouse v2.0 MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2589 vendor SAM xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1319535/+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
Re: [Touch-packages] [Bug 1476781] Re: [mako] voicecalls and sms are broken unless a network connection is active
Thank you, now I also get an update! Greetings from Germany Am 28.07.2015 um 14:52 schrieb Camilo Ernesto Blanco Peña: Hi: I installed via Sytem Config/Updates (running on Nexus 4 in version 21). The version 22 is available for to install (it is a fix). Regards... El 28/07/15 a las 07:56, Jens Becker escibió: Silly question: How do I install the fix? Settings says there are no updates available!? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1476781 Title: [mako] voicecalls and sms are broken unless a network connection is active Status in Canonical System Image: Fix Committed Status in telepathy-mission-control-5 package in Ubuntu: Fix Released Status in telepathy-ofono package in Ubuntu: Invalid Status in telepathy-mission-control-5 package in Ubuntu RTM: Fix Released Status in telepathy-ofono package in Ubuntu RTM: Invalid Bug description: Mako only Latest ota5 update or rc-proposed Turn off wifi and cell data try to send an sms, it will fail to send try to make a phone call, it will fail enable either data connection, it will succeed syslog contains Jul 21 10:27:46 ubuntu-phablet kernel: [ 16.082435] type=1400 audit(1437488866.193:170): apparmor=DENIED operation=connect info=Failed name lookup - disconnected path error=-13 profile=/usr/lib/telepathy/mission-control-5 name=dev/socket/property_service pid=1592 comm=getprop requested_mask=wr denied_mask=wr fsuid=32011 ouid=0 Jul 21 10:27:46 ubuntu-phablet kernel: [ 16.083137] type=1400 audit(1437488866.193:171): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/proc/cmdline pid=1592 comm=getprop requested_mask=r denied_mask=r fsuid=32011 ouid=0 version is 1:5.16.3-1ubuntu1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476781/+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 1476781] Re: [mako] voicecalls and sms are broken unless a network connection is active
Silly question: How do I install the fix? Settings says there are no updates available!? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1476781 Title: [mako] voicecalls and sms are broken unless a network connection is active Status in Canonical System Image: Fix Committed Status in telepathy-mission-control-5 package in Ubuntu: Fix Released Status in telepathy-ofono package in Ubuntu: Invalid Status in telepathy-mission-control-5 package in Ubuntu RTM: Fix Released Status in telepathy-ofono package in Ubuntu RTM: Invalid Bug description: Mako only Latest ota5 update or rc-proposed Turn off wifi and cell data try to send an sms, it will fail to send try to make a phone call, it will fail enable either data connection, it will succeed syslog contains Jul 21 10:27:46 ubuntu-phablet kernel: [ 16.082435] type=1400 audit(1437488866.193:170): apparmor=DENIED operation=connect info=Failed name lookup - disconnected path error=-13 profile=/usr/lib/telepathy/mission-control-5 name=dev/socket/property_service pid=1592 comm=getprop requested_mask=wr denied_mask=wr fsuid=32011 ouid=0 Jul 21 10:27:46 ubuntu-phablet kernel: [ 16.083137] type=1400 audit(1437488866.193:171): apparmor=DENIED operation=open profile=/usr/lib/telepathy/mission-control-5 name=/proc/cmdline pid=1592 comm=getprop requested_mask=r denied_mask=r fsuid=32011 ouid=0 version is 1:5.16.3-1ubuntu1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1476781/+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 1347020] Re: systemd does not boot in a container
I'm running utopic with latest updates. Any container, which has systemd running simply hangs, when /sbin/init gets started (no matter, whether config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and today with a vivid container. So wondering, whether there is a bugfix available at all? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1347020 Title: systemd does not boot in a container Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Bug description: Opening against cloud-init for now, but ultimately might end up as bug-fixes / srus against some other packages in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+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 1432683] Re: apt-get install lxc doesn't load required apparmor profiles
It appears, that something is still broken. Because systemd doesn't
work, I installed upstart + upstart-sysv (and uninstalled systemd-
sysv), but unfortunately sssd doesn't come up (has exactly the same
config, as in other 14.10 zones, where it works as expected). And
because sssd doesn't come up, other depending services like autofs
doesn't come up either.
The problem seems to be /lib/init/apparmor-profile-load as well, which returns
with 1 and thus probably causes start always fail.
As a workaround I modified /etc/init/sssd.conf:
...
pre-start script
test -f /etc/sssd/sssd.conf || { stop; exit 0; }
/lib/init/apparmor-profile-load usr.sbin.sssd || true
end script
...
which makes it work, however, I still wonder, what apparmor-profile-load
causes to return != 0 ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1432683
Title:
apt-get install lxc doesn't load required apparmor profiles
Status in apparmor package in Ubuntu:
Fix Released
Status in init-system-helpers package in Ubuntu:
Triaged
Status in lxc package in Ubuntu:
Fix Committed
Status in squid3 package in Ubuntu:
Fix Released
Status in upstart package in Ubuntu:
Triaged
Bug description:
I'm trying to use LXC on my openstack instance which runs vivid daily:
$ sudo apt-get install lxc -y
$ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache
--stream=daily --release=vivid
$ sudo lxc-start --name vivid --logfile=lxc.log
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 346 To get more details, run the container in
foreground mode.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by
setting the --logfile and --logpriority options.
In the log file (lxc.log) I observe the following error:
lxc-start 1426516387.814 ERRORlxc_apparmor -
lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory -
failed to change apparmor profile to lxc-container-default
This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was
not loaded appropriately.
This issue disappears if I:
(a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload
or
(b) reboot the instance
I'd expect that 'apt-get install lxc' has to load all appropriate
apparmor profiles to allow starting containers w/o profile reloading /
rebooting.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1432683/+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 1460163] [NEW] Still No data sources availableon Nexus 4
Public bug reported: On my Nexus 4 running Ubuntu Touch from channel Stable (presently Ubuntu 14.10 r19) the welcome screen always shows No data sources available, no matter if the option is selected or not in the settings. Is the problem known and will it be solved soon? ** Affects: libusermetrics (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1460163 Title: Still No data sources availableon Nexus 4 Status in libusermetrics package in Ubuntu: New Bug description: On my Nexus 4 running Ubuntu Touch from channel Stable (presently Ubuntu 14.10 r19) the welcome screen always shows No data sources available, no matter if the option is selected or not in the settings. Is the problem known and will it be solved soon? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1460163/+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 1447807] Re: systemctl enable fails to enable a SysV service
Thanks for the fast fix, is there already a package built from the patch somewhere that I could test? Also you might want to amend the title of the bug, as enabling the service is in fact performed properly, systemctl just throws an error in the end when it should simply terminate successfully instead. -- 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/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1447807] Re: systemctl enable shows error on enabling a SysV service
Tested and confirmed working, thanks again. -- 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/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1451797] Re: rc.local should require network-online.target
While I agree that this may never have been guaranteed, it has been working with all previous init systems. For me, the implied policy of using rc.local is: Run after all other init stuff has finished. For example, https://github.com/puppetlabs/razor-server uses modifying rc.local in order to trigger some post installation actions to happen once the node has rebooted after being installed. This works pretty well with Precise and Trusty and also seems to be fine with most other distros. Also, having a server with no network connectivity ever will also not be very useful. This is certainly different for desktop systems, but then, why would you have the After=network.target at all? ** Changed in: systemd (Ubuntu) Status: Incomplete = New -- 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/1451797 Title: rc.local should require network-online.target Status in systemd package in Ubuntu: New Bug description: The current definition in `/lib/systemd/system/rc-local.service` uses `After=network.target`, which is pretty useless, as `network.target` according to http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ only has relevance during shutdown, which never happens for rc.local. The result is that tasks in rc.local may get started before the network is properly setup, which may cause them to fail, as this is a significant change from the old SysV init behaviour. The solution would be to change the dependency to Wants=network-online.target After=network-online.target see also the notes in http://www.freedesktop.org/software/systemd/man/systemd.special.html for that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 [modified: lib/systemd/system/rc-local.service] ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 11:40:42 2015 Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT dmi.board.vendor: Supermicro dmi.board.version: 1.21 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd05/04/2012:svnSupermicro:pnX9DRT:pvr0123456789:rvnSupermicro:rnX9DRT:rvr1.21:cvnSupermicro:ct3:cvr0123456789: dmi.product.name: X9DRT dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1451797/+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 1451797] [NEW] rc.local should require network-online.target
Public bug reported: The current definition in `/lib/systemd/system/rc-local.service` uses `After=network.target`, which is pretty useless, as `network.target` according to http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ only has relevance during shutdown, which never happens for rc.local. The result is that tasks in rc.local may get started before the network is properly setup, which may cause them to fail, as this is a significant change from the old SysV init behaviour. The solution would be to change the dependency to Wants=network-online.target After=network-online.target see also the notes in http://www.freedesktop.org/software/systemd/man/systemd.special.html for that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 [modified: lib/systemd/system/rc-local.service] ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 11:40:42 2015 Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT dmi.board.vendor: Supermicro dmi.board.version: 1.21 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd05/04/2012:svnSupermicro:pnX9DRT:pvr0123456789:rvnSupermicro:rnX9DRT:rvr1.21:cvnSupermicro:ct3:cvr0123456789: dmi.product.name: X9DRT dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug systemd-boot vivid -- 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/1451797 Title: rc.local should require network-online.target Status in systemd package in Ubuntu: New Bug description: The current definition in `/lib/systemd/system/rc-local.service` uses `After=network.target`, which is pretty useless, as `network.target` according to http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ only has relevance during shutdown, which never happens for rc.local. The result is that tasks in rc.local may get started before the network is properly setup, which may cause them to fail, as this is a significant change from the old SysV init behaviour. The solution would be to change the dependency to Wants=network-online.target After=network-online.target see also the notes in http://www.freedesktop.org/software/systemd/man/systemd.special.html for that. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 [modified: lib/systemd/system/rc-local.service] ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 11:40:42 2015 Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9DRT ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/hostname--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DRT dmi.board.vendor: Supermicro dmi.board.version: 1.21 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias:
[Touch-packages] [Bug 1447807] Re: systemctl enable fails to enable a SysV service
I wouldn't agree that this is purely cosmetical, as it breaks things like Chef automation: https://github.com/gmiranda23/ntp/issues/105 -- 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/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: Triaged Bug description: Trying to enable a SysV init service results in an error: # systemctl enable sysstat Synchronizing state for sysstat.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d sysstat defaults Executing /usr/sbin/update-rc.d sysstat enable Failed to execute operation: No such file or directory I expected the service to be enabled. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1451743] Re: systemctl enable ntp fails with an error
*** This bug is a duplicate of bug 1447807 *** https://bugs.launchpad.net/bugs/1447807 ** This bug has been marked a duplicate of bug 1447807 systemctl enable fails to enable a SysV service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1451743 Title: systemctl enable ntp fails with an error Status in ntp package in Ubuntu: New Bug description: root@node10:~# systemctl enable ntp Synchronizing state for ntp.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ntp defaults Executing /usr/sbin/update-rc.d ntp enable Failed to execute operation: No such file or directory root@node10:~# ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 09:24:06 2015 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.ntpd: [modified] modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.ntpd: 2015-05-05T08:45:35.134023 mtime.conffile..etc.ntp.conf: 2015-05-05T08:45:35.170023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1451743/+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 1447807] Re: systemctl enable fails to enable a SysV service
Looking at the source code a bit, I see that in systemctl.c:enable_sysv_units there is a comment that it should reshuffle the args array, but it seems it never does that? So strv_isempty(names) in enable_unit never matches, causing the call to systemd which is failing, because there is no unit file. -- 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/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: Triaged Bug description: Trying to enable a SysV init service results in an error: # systemctl enable sysstat Synchronizing state for sysstat.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d sysstat defaults Executing /usr/sbin/update-rc.d sysstat enable Failed to execute operation: No such file or directory I expected the service to be enabled. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1451743] [NEW] systemctl enable ntp fails with an error
Public bug reported: root@node10:~# systemctl enable ntp Synchronizing state for ntp.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ntp defaults Executing /usr/sbin/update-rc.d ntp enable Failed to execute operation: No such file or directory root@node10:~# ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 09:24:06 2015 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.ntpd: [modified] modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.ntpd: 2015-05-05T08:45:35.134023 mtime.conffile..etc.ntp.conf: 2015-05-05T08:45:35.170023 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug systemd-boot vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1451743 Title: systemctl enable ntp fails with an error Status in ntp package in Ubuntu: New Bug description: root@node10:~# systemctl enable ntp Synchronizing state for ntp.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ntp defaults Executing /usr/sbin/update-rc.d ntp enable Failed to execute operation: No such file or directory root@node10:~# ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue May 5 09:24:06 2015 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apparmor.d.usr.sbin.ntpd: [modified] modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.apparmor.d.usr.sbin.ntpd: 2015-05-05T08:45:35.134023 mtime.conffile..etc.ntp.conf: 2015-05-05T08:45:35.170023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1451743/+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 1414778] Re: Click and draw of certain links results in double mouse pointer
I am still not able to reproduce this. As far as I am concerned this bug
can be closed.
--
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/1414778
Title:
Click and draw of certain links results in double mouse pointer
Status in xorg package in Ubuntu:
Expired
Bug description:
1. Open www.efneo.com/en/hub/ with Firefox (35.0)
2. At the bottom there is a circle with a mouse pictogram and an animated
arrow. Click on it with your left mouse button, draw it a couple of cm and
release the button. Now you should have a double mouse pointer with parts of
the circle and mouse pictogram. Here it looks like this:
http://img3.fotos-hochladen.net/uploads/doublemousepohna02kloqg.jpg
3. While both of the visible mouse pointers are somewhat distorted the left
one is fully functional, also in other applications. (except on one of the
systems I tested, where the mouse pointer went back no normal when closing
Firefox)
I tried to reproduce this on 3 notebooks with Xubuntu and succeded on
all of them. I also noticed that while I can see the strange mouse
pointer on the screen I was not able to capture it with
xfce4-screenshooter. In the captured picture the mouse pointer always
looks normal.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 35.0+build3-0ubuntu0.14.10.2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jens 2464 F pulseaudio
/dev/snd/controlC0: jens 2464 F pulseaudio
BuildID: 20150112203438
Channel: Unavailable
Date: Mon Jan 26 21:05:56 2015
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2014-12-29 (28 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
IpRoute:
default via 192.168.2.1 dev wlan0 proto static
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.108
metric 9
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-35f0f403-581d-46ab-a144-c6a462150117
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{a7c6cf7f-112c-4500-a7ea-39801a327e5f}/defaults/preferences/fireftp.js
[Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js
Profiles: Profile0 (Default) - LastVersion=35.0/20150112203438 (In use)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs: bp-35f0f403-581d-46ab-a144-c6a462150117
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET93WW (3.23 )
dmi.board.name: 2089A22
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2089A22:pvrThinkPadT500:rvnLENOVO:rn2089A22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2089A22
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1414778/+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 1449567] [NEW] Cannot see login box on a locked screen
Public bug reported: 1. Lock the screen 2. Try to log in and find the entire screen is white, except for the mouse cursor 3. Pressing any keys on the keyboard does not change anything 4. Pressing any mouse button makes the login screen visible the way expected. This happens since the upgrade to 15.04. Its reproduceable always on my main notebook but not on a 2nd. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue Apr 28 15:15:20 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-29 (119 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-24 (4 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449567 Title: Cannot see login box on a locked screen Status in lightdm package in Ubuntu: New Bug description: 1. Lock the screen 2. Try to log in and find the entire screen is white, except for the mouse cursor 3. Pressing any keys on the keyboard does not change anything 4. Pressing any mouse button makes the login screen visible the way expected. This happens since the upgrade to 15.04. Its reproduceable always on my main notebook but not on a 2nd. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Tue Apr 28 15:15:20 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-12-29 (119 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: lightdm UpgradeStatus: Upgraded to vivid on 2015-04-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1449567/+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 1424253] Re: RFE: procps tools should support lxc
Actually that's not the same at all, because $cgroup != $lxc_name . Your
workaround is absolutely user UNfriendly, i.e. still hard to read and
for casual users inconvinient, because one needs supply all that many
format options ...
Anyway, I agree, that these utils should support such things out of the
box, but 'til than, it remains a distribution thing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1424253
Title:
RFE: procps tools should support lxc
Status in lxc package in Ubuntu:
Invalid
Status in procps package in Ubuntu:
New
Bug description:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
filter the output wrt. a certain zone or to add a column, which
shows the zone name a process belongs to.
E.g. for what is needed:
{ps|pgrep|pkill|top} ... -z $myzone
# show zone name as well
{ps|top} -Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424253/+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 1424233] Re: RFE lxc: lxc should do a better jon of housekeeping containers
Yepp, and that's IMHO a design flaw. E.g. if one wants to distribute the load on iots storage, it might make sense, to distribute the zones of several storage devices, e.g. zone1 on JBOD1, zone2 on JBOD2, etc As said, the only thing, which lxc nees to track is a single config directory which either contains the symlinks to the real zone configs OR the real config fails itself - since they usually contain lxc.rootfs = ..., there is not really a need, to keep it in its original place. And last but not least, IMHO LXC should have an interest to make things easy to manage for the users, otherwise there is no wonder, why everyone is talking about docker but not about lxc ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1424233 Title: RFE lxc: lxc should do a better jon of housekeeping containers Status in lxc package in Ubuntu: Won't Fix Bug description: Right now lxc does a pretty poor job wrt. managing containers, i.e. one needs to know, where containers have been installed to be able to access/use/manage them (option -P dir) unless they've been installed in the default location. Even if one knows the install path, it is still a pain to work with corresponding lxc commands, because one always needs to specify -P ... This really sucks (especially if one needs to service foreign machines). So the proposal is, that if a zone gets created, lxc puts a symlink to the related config under /etc/lxc/cfg/ or something like that and all lxc tools like lxc-ls first check this directory, and if the link destination exists, it has all information it needs to know., i.e. all -P idontknow madness is not required anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+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 1414778] Re: Click and draw of certain links results in double mouse pointer
This is strange, I remember having answered this weeks ago and had also
received a reply of yours. I was not able to reproduce the bug in 15.04.
and you wrote this would likely not be fixed in 14.10. except I manage
to convince the developers of its importance.
--
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/1414778
Title:
Click and draw of certain links results in double mouse pointer
Status in xorg package in Ubuntu:
Incomplete
Bug description:
1. Open www.efneo.com/en/hub/ with Firefox (35.0)
2. At the bottom there is a circle with a mouse pictogram and an animated
arrow. Click on it with your left mouse button, draw it a couple of cm and
release the button. Now you should have a double mouse pointer with parts of
the circle and mouse pictogram. Here it looks like this:
http://img3.fotos-hochladen.net/uploads/doublemousepohna02kloqg.jpg
3. While both of the visible mouse pointers are somewhat distorted the left
one is fully functional, also in other applications. (except on one of the
systems I tested, where the mouse pointer went back no normal when closing
Firefox)
I tried to reproduce this on 3 notebooks with Xubuntu and succeded on
all of them. I also noticed that while I can see the strange mouse
pointer on the screen I was not able to capture it with
xfce4-screenshooter. In the captured picture the mouse pointer always
looks normal.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 35.0+build3-0ubuntu0.14.10.2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jens 2464 F pulseaudio
/dev/snd/controlC0: jens 2464 F pulseaudio
BuildID: 20150112203438
Channel: Unavailable
Date: Mon Jan 26 21:05:56 2015
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2014-12-29 (28 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
IpRoute:
default via 192.168.2.1 dev wlan0 proto static
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.108
metric 9
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-35f0f403-581d-46ab-a144-c6a462150117
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
Shockwave Flash - [HomeDir]/.mozilla/plugins/libflashplayer.so
PrefSources:
prefs.js
[Profile]/extensions/{a7c6cf7f-112c-4500-a7ea-39801a327e5f}/defaults/preferences/fireftp.js
[Profile]/extensions/https-everywh...@eff.org/defaults/preferences/preferences.js
Profiles: Profile0 (Default) - LastVersion=35.0/20150112203438 (In use)
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not
accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs: bp-35f0f403-581d-46ab-a144-c6a462150117
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET93WW (3.23 )
dmi.board.name: 2089A22
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2089A22:pvrThinkPadT500:rvnLENOVO:rn2089A22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2089A22
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1414778/+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 1424233] [NEW] RFE lxc: lxc should do a better jon of housekeeping containers
Public bug reported: Right now lxc does a pretty poor job wrt. managing containers, i.e. one needs to know, where containers have been installed to be able to access/use/manage them (option -P dir) unless they've been installed in the default location. Even if one knows the install path, it is still a pain to work with corresponding lxc commands, because one always needs to specify -P ... This really sucks (especially if one needs to service foreign machines). So the proposal is, that if a zone gets created, lxc puts a symlink to the related config under /etc/lxc/cfg/ or something like that and all lxc tools like lxc-ls first check this directory, and if the link destination exists, it has all information it needs to know., i.e. all -P idontknow madness is not required anymore. ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1424233 Title: RFE lxc: lxc should do a better jon of housekeeping containers Status in upstart package in Ubuntu: New Bug description: Right now lxc does a pretty poor job wrt. managing containers, i.e. one needs to know, where containers have been installed to be able to access/use/manage them (option -P dir) unless they've been installed in the default location. Even if one knows the install path, it is still a pain to work with corresponding lxc commands, because one always needs to specify -P ... This really sucks (especially if one needs to service foreign machines). So the proposal is, that if a zone gets created, lxc puts a symlink to the related config under /etc/lxc/cfg/ or something like that and all lxc tools like lxc-ls first check this directory, and if the link destination exists, it has all information it needs to know., i.e. all -P idontknow madness is not required anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1424233/+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 1424233] Re: RFE lxc: lxc should do a better jon of housekeeping containers
** Package changed: upstart (Ubuntu) = lxc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1424233 Title: RFE lxc: lxc should do a better jon of housekeeping containers Status in lxc package in Ubuntu: New Bug description: Right now lxc does a pretty poor job wrt. managing containers, i.e. one needs to know, where containers have been installed to be able to access/use/manage them (option -P dir) unless they've been installed in the default location. Even if one knows the install path, it is still a pain to work with corresponding lxc commands, because one always needs to specify -P ... This really sucks (especially if one needs to service foreign machines). So the proposal is, that if a zone gets created, lxc puts a symlink to the related config under /etc/lxc/cfg/ or something like that and all lxc tools like lxc-ls first check this directory, and if the link destination exists, it has all information it needs to know., i.e. all -P idontknow madness is not required anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424233/+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 1424253] [NEW] RFE: procps tools should support lxc
Public bug reported:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
filter the output wrt. a certain zone or to add a column, which shows
the zone name a process belongs to.
E.g. for what is needed:
{ps|pgrep|pkill|top} ... -z $myzone
# show zone name as well
{ps|top} -Z
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1424253
Title:
RFE: procps tools should support lxc
Status in lxc package in Ubuntu:
New
Bug description:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
filter the output wrt. a certain zone or to add a column, which
shows the zone name a process belongs to.
E.g. for what is needed:
{ps|pgrep|pkill|top} ... -z $myzone
# show zone name as well
{ps|top} -Z
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424253/+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 1418870] Re: Double mouse cursor
The bug does not show up on 2 laptops I tested with Ubuntu 15.04. -- 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/1418870 Title: Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: 1. Open www.efneo.com/en/hub/ with Firefox (35.0) 2. At the bottom there is a circle with a mouse pictogram and an animated arrow. Click on it with your left mouse button, draw it a couple of cm and release the button. Now you should have a double mouse pointer with parts of the circle and mouse pictogram. Here it looks like this: http://img3.fotos-hochladen.net/uploads/doublemousepohna02kloqg.jpg 3. While both of the visible mouse pointers are somewhat distorted the left one is fully functional, also in other applications. (except on one of the systems I tested, where the mouse pointer went back no normal when closing Firefox) I tried to reproduce this on 3 notebooks with Xubuntu and succeded on all of them. I also noticed that while I can see the strange mouse pointer on the screen I was not able to capture it with xfce4-screenshooter. In the captured picture the mouse pointer always looks normal. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 6 09:57:15 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2014-12-29 (38 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1768): WARNING **: Failed to load user image: Failed to open file '/home/jens/.face': Permission denied g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1729): WARNING **: Failed to load user image: Failed to open file '/home/jens/.face': Permission denied MachineType: LENOVO 2089A22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=30df4b9e-1568-4f78-8c2d-ef2403a6f3f2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2089A22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2089A22:pvrThinkPadT500:rvnLENOVO:rn2089A22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2089A22 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Feb 6 09:56:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2106 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1418870/+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 1418870] Re: Double mouse cursor
Both of the laptops I tested are Thinkpad T500. I can do tests on other machines if needed. -- 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/1418870 Title: Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: 1. Open www.efneo.com/en/hub/ with Firefox (35.0) 2. At the bottom there is a circle with a mouse pictogram and an animated arrow. Click on it with your left mouse button, draw it a couple of cm and release the button. Now you should have a double mouse pointer with parts of the circle and mouse pictogram. Here it looks like this: http://img3.fotos-hochladen.net/uploads/doublemousepohna02kloqg.jpg 3. While both of the visible mouse pointers are somewhat distorted the left one is fully functional, also in other applications. (except on one of the systems I tested, where the mouse pointer went back no normal when closing Firefox) I tried to reproduce this on 3 notebooks with Xubuntu and succeded on all of them. I also noticed that while I can see the strange mouse pointer on the screen I was not able to capture it with xfce4-screenshooter. In the captured picture the mouse pointer always looks normal. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 6 09:57:15 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2014-12-29 (38 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1768): WARNING **: Failed to load user image: Failed to open file '/home/jens/.face': Permission denied g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1729): WARNING **: Failed to load user image: Failed to open file '/home/jens/.face': Permission denied MachineType: LENOVO 2089A22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=30df4b9e-1568-4f78-8c2d-ef2403a6f3f2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2089A22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2089A22:pvrThinkPadT500:rvnLENOVO:rn2089A22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2089A22 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Feb 6 09:56:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2106 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1418870/+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 1418870] [NEW] Double mouse cursor
Public bug reported: 1. Open www.efneo.com/en/hub/ with Firefox (35.0) 2. At the bottom there is a circle with a mouse pictogram and an animated arrow. Click on it with your left mouse button, draw it a couple of cm and release the button. Now you should have a double mouse pointer with parts of the circle and mouse pictogram. Here it looks like this: http://img3.fotos-hochladen.net/uploads/doublemousepohna02kloqg.jpg 3. While both of the visible mouse pointers are somewhat distorted the left one is fully functional, also in other applications. (except on one of the systems I tested, where the mouse pointer went back no normal when closing Firefox) I tried to reproduce this on 3 notebooks with Xubuntu and succeded on all of them. I also noticed that while I can see the strange mouse pointer on the screen I was not able to capture it with xfce4-screenshooter. In the captured picture the mouse pointer always looks normal. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 6 09:57:15 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2014-12-29 (38 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1768): WARNING **: Failed to load user image: Failed to open file '/home/jens/.face': Permission denied g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1729): WARNING **: Failed to load user image: Failed to open file '/home/jens/.face': Permission denied MachineType: LENOVO 2089A22 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=30df4b9e-1568-4f78-8c2d-ef2403a6f3f2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2089A22 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2089A22:pvrThinkPadT500:rvnLENOVO:rn2089A22:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2089A22 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Feb 6 09:56:26 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2106 vendor SAM xserver.version: 2:1.16.0-1ubuntu1.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu utopic -- 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/1418870 Title: Double mouse cursor Status in xorg package in Ubuntu: New Bug description: 1. Open www.efneo.com/en/hub/ with Firefox (35.0) 2. At the bottom there is a circle with a mouse pictogram and an animated arrow. Click on it with your left mouse button, draw it a couple of cm and release the button. Now you should have a double mouse pointer with parts of the circle and mouse pictogram. Here it looks like this: http://img3.fotos-hochladen.net/uploads/doublemousepohna02kloqg.jpg 3. While both of the visible mouse pointers are somewhat distorted the left one is fully functional, also in other applications
[Touch-packages] [Bug 1393169] Re: Double mouse cursor
@Christopher M. Penalver: This bug is still incomplete as the TO did not respond for more that 2 months now. I can reproduce it reliably on a Thinkpad T500 Bios 6FET93WW (3.23 ) (duplicate 1414778). What information do you need? -- 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/1393169 Title: Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: Last up to date Xubuntu 64 bits installed on a laptop Since 2 days, the mouse cursor is double with only the left part as active and a bar just behing of both arrow (see picture joined). I tried to change the theme but no way to go back to a normal mouse cursor Regards ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Nov 16 11:12:21 2014 InstallationDate: Installed on 2013-01-03 (681 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fde0] Subsystem: Toshiba America Info Systems Device [1179:fde0] InstallationDate: Installed on 2013-01-03 (695 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: Impossible d'ouvrir le fichier « /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission non accordée ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: /home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: TOSHIBA Satellite Pro C650 Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Tags: utopic ubuntu Uname: Linux 3.16.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite Pro C650 dmi.product.version: PSC09E-00R01YMV dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
[Touch-packages] [Bug 1413699] Re: pkill|pgrep are buggy
Please read carefully! This bug is not about upstart-udev-bridge or any
other service but about PGREP . 'pgrep upstart-udev-bridge' is just an
example, which should work on any Ubuntu, i.e. to reproduce the problem!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1413699
Title:
pkill|pgrep are buggy
Status in procps package in Ubuntu:
New
Bug description:
'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
doesn't. When one uses the option -f than it actually prints the PID
of the upstart-udev-bridge process. However using -f is a bad
workaround, because than (at least wrt. the man page) the arguments
and operands get included into the match, which may break scripts or
even lead to security issues.
I guess, the bug is, that p{grep|kill} strips off everything after the
first '-' of the command before it actually tries to compare with the
given operand (or something like that).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1413699/+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 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration
I can confirm this bug using Thinkpad T420 with nvidia optimus enabled and proprietary driver. Is there any update on this or any workaround? Thanks -- 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/1382462 Title: Desktop/windows painted incorrectly in dual monitor configuration Status in xorg package in Ubuntu: Confirmed Bug description: My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached to DisplayPort. I was using Nvidia 331.38 prioprietary driver for quite a long time with Ubuntu 14.04 LTS and everything worked perfectly. Today I upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed the following problem: 1. When I boot up the computer with the monitor connected, the login screen looks fine. Both displays get detected properly and resolutions are ok (1920x1080 on the builtin laptop display and 2560x1600 on U3011) and screen contents scaled properly. 2. Then I log into my account, for 3 seconds U3011 displays some rubbish (but it was always like that) and when it finally logs in, it displays everything stretched horizontally through both my screens. It looks as if it tried to paint the contents of a single display on two of them, by stretching the content horizontally, so everything (icons, windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar seem to render correctly and the resolution/size of the top menu is correct. Physical resolution of both screens is ok. I'll attach a photo, because it is hard to describe how it looks. 3. I cannot use system in this state - mouse click position seems to not be synchronized with what's on the display - e.g. I can start applications, but then they don't react to mouseclicks. However: booting up without the second display connected, logging in and *then* connecting the second display works fine. If I boot up with connected monitor and log in (desktop distorted), disconnecting and connecting monitor does *not* help. After disconnecting the U3011, the builtin display is painted ok, but after connecting, it returns back to the incorrect state and both are rendered incorrectly. The only thing that helps recovering from this state seems to be disconnecting the second monitor, reboot, logging in and then connecting. Suspending to memory and waking up does not change the layout of the screen (neither fixes the broken one nor destroys the good one). Using a Guest session instead of my account does not fix my problem (I was hoping this was something screwed up in my .config). Switching to a Guest user account while I'm using both monitors in the good layout creates a session with a broken layout. Then logging out from Guest and switching back to my original session restores the good layout. The good layout seems to not be forgotten until I finish the session and logout. The bad layout is created whenever I start a new session with both monitors plugged in. BTW: I'm using a docking station - not sure if it is related - if you think it might be, I can try with connecting the monitor directly. I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem remains. I also tried to go into the Displays configuration when everything is ok, apply the settings there (without any changes) in hope it will persist them somehow, but after restart it is broken again. I also tried reinstalling nvidia 331.89 drivers, because it complained about not being able to install nvidia-uvm during the upgrade process (reported separately), and now all nvidia packages installed cleanly. Before that I also got rid of all the ppa mainline kernels I had, just in case they mess something up. I remember the same problem happened on Ubuntu 14.04 when I tried to upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy workaround was to downgrade back to official 331.38. Now I have no choice :( Some other observations that may or may not be related to the problem, but I disclose them anyway, maybe they are helpful: * Notifications (e.g. network connection) displayed on the login screen in dual screen mode seem to be misplaced and instead of being painted in the upper right corner of one of the displays they get painted in some hard to logically explain position - neither at the center, nor in any corner. * The splash screen of IntelliJ IDEA (this is using Java / AWT probably) is also rendered in a strange position - below the center of the laptop screen, moved to the right (but not touching the edge), instead of exact center as it should be. * GMail notification just displayed at the moment when I'm writing it exactly at the left-lower corner of the bigger screen (U3011). * Nvidia settings lists only U3011 in the list of the devices (attached screenshot).
[Touch-packages] [Bug 1413699] [NEW] pkill|pgrep are buggy
Public bug reported:
'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
doesn't. When one uses the option -f than it actually prints the PID of
the upstart-udev-bridge process. However using -f is a bad workaround,
because than (at least wrt. the man page) the arguments and operands get
included into the match, which may break scripts or even lead to
security issues.
I guess, the bug is, that p{grep|kill} strips off everything after the
first '-' of the command before it actually tries to compare with the
given operand (or something like that).
** Affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Package changed: system-config-kickstart (Ubuntu) = procps (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1413699
Title:
pkill|pgrep are buggy
Status in procps package in Ubuntu:
New
Bug description:
'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
doesn't. When one uses the option -f than it actually prints the PID
of the upstart-udev-bridge process. However using -f is a bad
workaround, because than (at least wrt. the man page) the arguments
and operands get included into the match, which may break scripts or
even lead to security issues.
I guess, the bug is, that p{grep|kill} strips off everything after the
first '-' of the command before it actually tries to compare with the
given operand (or something like that).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1413699/+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 1410637] [NEW] gai.conf changes seem to have no effect
Public bug reported: Ubuntu documentation states, that changing /etc/gai.conf is the way to be able to prefer IPv4 over IPv6. So from the original gai.conf we removed the comment in front of the precedence statements AND set the value for :::0:0/96 to 60. Unfortunately this does not seem to have an effect. E.g.: 'getent hosts heise.de' still returns '2a02:2e0:3fe:1001:302:: heise.de' instead of '193.99.144.80heise.de', even if no interface has an IPv6 addr configured, all /proc/sys/net/ipv6/conf/*/disable_ipv6 have the value 1 and no ipv6 specific iptables/rules are in use. This is extremly odd and needs to be fixed. /etc/nsswitch.conf uses 'hosts: files dns'. Linux tb 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /etc/os-release NAME=Ubuntu VERSION=14.10 (Utopic Unicorn) ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 14.10 VERSION_ID=14.10 HOME_URL=http://www.ubuntu.com/; SUPPORT_URL=http://help.ubuntu.com/; BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/; ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1410637 Title: gai.conf changes seem to have no effect Status in eglibc package in Ubuntu: New Bug description: Ubuntu documentation states, that changing /etc/gai.conf is the way to be able to prefer IPv4 over IPv6. So from the original gai.conf we removed the comment in front of the precedence statements AND set the value for :::0:0/96 to 60. Unfortunately this does not seem to have an effect. E.g.: 'getent hosts heise.de' still returns '2a02:2e0:3fe:1001:302:: heise.de' instead of '193.99.144.80 heise.de', even if no interface has an IPv6 addr configured, all /proc/sys/net/ipv6/conf/*/disable_ipv6 have the value 1 and no ipv6 specific iptables/rules are in use. This is extremly odd and needs to be fixed. /etc/nsswitch.conf uses 'hosts: files dns'. Linux tb 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /etc/os-release NAME=Ubuntu VERSION=14.10 (Utopic Unicorn) ID=ubuntu ID_LIKE=debian PRETTY_NAME=Ubuntu 14.10 VERSION_ID=14.10 HOME_URL=http://www.ubuntu.com/; SUPPORT_URL=http://help.ubuntu.com/; BUG_REPORT_URL=http://bugs.launchpad.net/ubuntu/; To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1410637/+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 1391652] Re: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
I've updated the BIOS. xorg (or is it gnome-shell?) still hangs, but without any ACPI-warnings this time. The bios version as requested is: A19 09/07/2012 There are still some warnings during startup: Jan 10 22:01:33 jens-XPS-L702X kernel: [3.753967] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [...] Jan 10 22:01:33 jens-XPS-L702X kernel: [9.081351] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Jan 10 22:01:33 jens-XPS-L702X kernel: [9.081561] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) I also have these warnings. I have no idea what driver they refer to: Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.264661] lp: driver loaded but no devices found Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.276445] ppdev: user-space parallel port driver Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719545] ACPI Warning: 0x0428-0x042f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719554] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719737] ACPI Warning: 0x0540-0x054f SystemIO conflicts with Region \GPIN 1 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719741] ACPI Warning: 0x0540-0x054f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719745] ACPI Warning: 0x0540-0x054f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 3 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719749] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719751] ACPI Warning: 0x0530-0x053f SystemIO conflicts with Region \GPIN 1 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719754] ACPI Warning: 0x0530-0x053f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719757] ACPI Warning: 0x0530-0x053f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 3 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719761] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719762] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \GPIN 1 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719765] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719769] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 3 (20131115/utaddress-251) Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719772] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Jan 10 22:01:33 jens-XPS-L702X kernel: [ 11.719774] lpc_ich: Resource conflict(s) found affecting gpio_ich -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell
[Touch-packages] [Bug 1351351] Re: Printer does print only after reconnect
First I want to point out that I had to reinstall my system a week ago. While I still have trouble to print its not the same syptom it was before. Now I am not able to print anything anymore, independent from when I connect the printer to the computer. However, I have tried all the modifications you mentioned and did not have success with any of them. Would you suggest to open a new bug with current log files or should I attach them here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1351351 Title: Printer does print only after reconnect Status in cups package in Ubuntu: Incomplete Bug description: I use a USB printer Samsung ML-1640. Since the latest ubuntu upgrade the printer does not start to print anymore when I send a print job via libreoffice or evince. The printer queue says its processing the print job but nothing happens. By trial and error I found that it is possible to print when I follow a certain sequence: 1. The printer is switched on but not connected to the PC 2. I open the document and send a print job 3. About 4s later I connect the printer to the PC 4. The printer prints To print another document I have to repeat steps 1 to 4 again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.15.6-031506-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: Date: Fri Aug 1 16:56:48 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-26 (248 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) Lpstat: device for Samsung-ML-1640-Series: usb://Samsung/ML-1640%20Series?serial=144QBAIS500148D. MachineType: LENOVO 2731A11 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: Samsung-ML-1640-Series: Samsung ML-1640, 2.0.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.6-031506-generic root=UUID=ec5b1571-ab35-4cc5-bce8-3b36ea5596c3 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to trusty on 2014-04-22 (101 days ago) dmi.bios.date: 02/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET85WW (3.15 ) dmi.board.name: 2731A11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7YET85WW(3.15):bd02/13/2012:svnLENOVO:pn2731A11:pvrThinkPadR500:rvnLENOVO:rn2731A11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2731A11 dmi.product.version: ThinkPad R500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1351351/+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 1367214] Re: Newly installed openssh-server and upstart: status: Unknown job: ssh
Probably because this piece of junk (upstart) just silently discards any *.conf file with errors/unknown directives in it instead of reporting/logging the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1367214 Title: Newly installed openssh-server and upstart: status: Unknown job: ssh Status in upstart package in Ubuntu: Confirmed Bug description: Just after installing openssh-server, there is no ssh service in the initctl's list. Consequently, the SSH server cannot be started: # initctl start ssh initctl: Unknown job: ssh # dpkg -l | grep ssh ii openssh-client 1:6.6p1-2ubuntu2 i386 secure shell (SSH) client, for secure access to remote machines ii openssh-server 1:6.6p1-2ubuntu2 i386 secure shell (SSH) server, for secure access from remote machines # cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04.1 LTS # initctl reload-configuration # initctl list | grep ssh ssh-agent start/running # ps axuw | grep ssh ivoras1578 0.0 0.0 4216 200 ?Ss Sep08 0:00 ssh-agent -s root 11810 0.0 0.0 6168 852 pts/2S+ 11:26 0:00 grep ssh # initctl start ssh initctl: Unknown job: ssh Running /etc/init.d/ssh does not do anything since the script exits, AFAIK in the upstart check. Running service ssh restart results in: # service ssh restart stop: Unknown job: ssh start: Unknown job: ssh After rebooting the machine, sshd is started (!), but still not visible in initctl list (!!) and running /etc/init.d/ssh still doesn't do anything (!!!), as well as the service command returning the same Unknown job: ssh error. Exactly the same problem happens with the php5-fpm service. I've also installed nginx and while it can be controlled by using /etc/init.d/nginx , it is not visible in initctl list. The question is - how do I control the services in Ubuntu 14.04? This is a fresh install, the ssh service was the first service installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1367214/+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 1391652] BootLog.txt
apport information ** Attachment added: BootLog.txt https://bugs.launchpad.net/bugs/1391652/+attachment/4271452/+files/BootLog.txt -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f240 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f000 (32-bit, non-prefetchable) [size=32M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=64M] I/O ports at 4000 [size=128] Expansion ROM at f200 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] NVIDIA Corporation GF106M [GeForce GT 550M] [10de:0dd6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] InstallationDate: Installed on 2014-03-06 (268 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: Dell Inc. Dell System XPS L702X Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1391652] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1391652/+attachment/4271455/+files/DpkgLog.txt -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f240 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f000 (32-bit, non-prefetchable) [size=32M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=64M] I/O ports at 4000 [size=128] Expansion ROM at f200 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] NVIDIA Corporation GF106M [GeForce GT 550M] [10de:0dd6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] InstallationDate: Installed on 2014-03-06 (268 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: Dell Inc. Dell System XPS L702X Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2011 dmi.bios.vendor: Dell Inc.
[Touch-packages] [Bug 1391652] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1391652/+attachment/4271454/+files/Dependencies.txt -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f240 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f000 (32-bit, non-prefetchable) [size=32M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=64M] I/O ports at 4000 [size=128] Expansion ROM at f200 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] NVIDIA Corporation GF106M [GeForce GT 550M] [10de:0dd6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] InstallationDate: Installed on 2014-03-06 (268 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: Dell Inc. Dell System XPS L702X Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2011 dmi.bios.vendor:
[Touch-packages] [Bug 1391652] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1391652/+attachment/4271456/+files/GconfCompiz.txt -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f240 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f000 (32-bit, non-prefetchable) [size=32M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=64M] I/O ports at 4000 [size=128] Expansion ROM at f200 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] NVIDIA Corporation GF106M [GeForce GT 550M] [10de:0dd6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] InstallationDate: Installed on 2014-03-06 (268 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: Dell Inc. Dell System XPS L702X Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2011 dmi.bios.vendor:
[Touch-packages] [Bug 1391652] LightdmGreeterLogOld.txt
apport information ** Attachment added: LightdmGreeterLogOld.txt https://bugs.launchpad.net/bugs/1391652/+attachment/4271459/+files/LightdmGreeterLogOld.txt -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f240 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f000 (32-bit, non-prefetchable) [size=32M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=64M] I/O ports at 4000 [size=128] Expansion ROM at f200 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] NVIDIA Corporation GF106M [GeForce GT 550M] [10de:0dd6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] InstallationDate: Installed on 2014-03-06 (268 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: Dell Inc. Dell System XPS L702X Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2011
[Touch-packages] [Bug 1391652] LightdmGreeterLog.txt
apport information ** Attachment added: LightdmGreeterLog.txt https://bugs.launchpad.net/bugs/1391652/+attachment/4271458/+files/LightdmGreeterLog.txt -- 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/1391652 Title: 30 sec Xorg freeze - ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) Status in xorg package in Ubuntu: Incomplete Bug description: XOrg freezes for about 30 seconds and this warning is printed in the syslog: kernel: [ 752.250482] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) kernel: [ 752.250740] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95) However, the console still works while X is frozen. This is a Dell XPS L702X with optimus graphics. The freeze appears to occur randomly. Using nautilus, gedit or other gtk3-programs seems to cause it happen more frequently. Eclipse and Chromium that uses gtk2 does not seem to trigger the bug. There are two similar bugs: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1362532 https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1281966 3.13.0-39-generic x86_64 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 52 Memory at f240 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 01:00.0 VGA compatible controller: NVIDIA Corporation GF106M [GeForce GT 550M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device 04b8 Flags: bus master, fast devsel, latency 0, IRQ 51 Memory at f000 (32-bit, non-prefetchable) [size=32M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=64M] I/O ports at 4000 [size=128] Expansion ROM at f200 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel driver in use: nouveau LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] NVIDIA Corporation GF106M [GeForce GT 550M] [10de:0dd6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b8] InstallationDate: Installed on 2014-03-06 (268 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140226) MachineType: Dell Inc. Dell System XPS L702X Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash intel_pstate=enable vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/22/2011
