[Touch-packages] [Bug 1708992] [NEW] No space left on device when trying to install a stock kernel image
Public bug reported: I have no separate boot partition. Still when trying to install a kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D I get the following error message: xitcp: cannot create regular file '/var/tmp/mkinitramfs_uNlQUF//lib/firmware/nvidia/gp100/gr/fecs_data.bin': No space left on device If the initramfs filesystem isn't growable or big enough? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu9 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Aug 7 06:37:27 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1708992 Title: No space left on device when trying to install a stock kernel image Status in initramfs-tools package in Ubuntu: New Bug description: I have no separate boot partition. Still when trying to install a kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D I get the following error message: xitcp: cannot create regular file '/var/tmp/mkinitramfs_uNlQUF//lib/firmware/nvidia/gp100/gr/fecs_data.bin': No space left on device If the initramfs filesystem isn't growable or big enough? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu9 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Aug 7 06:37:27 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1708992/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text
> GTK_THEME=Abiword solves the problem, no more flickering Does not solve for me on Artful 17.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Confirmed Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround for Ubuntu 16.04 LTS === 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+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 1695983] Re: Removing an imported openvpn connection doesn't clean up copied certificates
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1695983 Title: Removing an imported openvpn connection doesn't clean up copied certificates Status in xorg package in Ubuntu: Expired Bug description: I imported an openvpn connection with the KDE network manager, which worked fine. On import I was asked whether I want my certificates to be copied to .local/share/networkmanagement, which I confirmed. Them I removed my connection and reimported it again, this time receiving the following error message: "Error copying certificate to /home/user/.local/share/networkmanagement/certificates/myopenvpn.key: Destination file exists" Seems like copied certificates aren't cleaned up when an openvpn connection is removed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 5 21:56:31 2017 InstallationDate: Installed on 2017-06-04 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1695983/+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 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell
Is this humanity or just more missing icon symlinks (as usual) in ubuntu-themes? I thought it was the latter when I logged bug 1700736. ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-themes Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1698795 Title: Humanity should provide symbolic versions of custom icons for GNOME Shell Status in Ubuntu theme: New Status in gnome-shell package in Ubuntu: New Status in humanity-icon-theme package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: The app icon in top panel next to application menu entry is the default adwaita icons and don't match the current theming. It's either: - the fact that we don't provide the correct icon size in our themes, and so, the icons are defaulted - a bug in G-S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1698795/+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 1708137] Re: application crashes due to rival protobuffers versions
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1708137 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gstreamer-vaapi (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: mir (Ubuntu) Status: New => Incomplete -- 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/1708137 Title: application crashes due to rival protobuffers versions Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mir package in Ubuntu: Incomplete Bug description: So somewhen in last week there were made some changes in the ubuntu repository which effect libEGL. This lib newly uses libmirclient.so.9 which itself uses libprotobuf-lite.so.9. The default protobuffers version shipped with ubuntu is 2.6.1. My application uses libgstvaapi which uses libEGL. My application as well uses protobuffers but I link it statically to version 3.0.0 due to its json compatibility. So when now starting the application it crashes immediately due to rivaling protobuffers version. This problem first occured last week somewhen. This makes it impossible to use libEGL/libmir and a not-default protobuffers version in one application. Please let me how you're going to deal with that. Best, Henning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1708137/+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 1708774] Re: bluetoothd crashed with SIGSEGV
** Information type changed from Private to Public ** Summary changed: - bluetoothd crashed with SIGSEGV + bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_resolved() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1708774 Title: bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_resolved() Status in bluez package in Ubuntu: New Bug description: This is happening over and over while running behind the scenes. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: bluez 5.45-0ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Jul 31 22:44:35 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2017-07-29 (6 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: initrd=\ubuntu\initrd.img-generic root=/dev/mapper/volgrp-root rw SegvAnalysis: Segfault happened at: 0x7f2b54231cf0:mov(%rdi),%rax PC (0x7f2b54231cf0) ok source "(%rdi)" (0x3130383130303038) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: bluez StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () ?? () ?? () Title: bluetoothd crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F4:5C:89:C2:92:3C ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1054 acl:0 sco:0 events:59 errors:0 TX bytes:2965 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708774/+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 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random
** Changed in: util-linux (Ubuntu) Assignee: (unassigned) => Chris Halse Rogers (raof) -- 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/1708635 Title: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random Status in util-linux package in Ubuntu: New Bug description: This has shown up in lp:mir CI on Artful amd64 (and no other architecture or series we're using) For example: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1708635/+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 1708977] [NEW] Cannot boot after update
Public bug reported: Following minor linux update cannot boot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: /dev/sda1: clean, 223961/121970688 files, 8834593/487854592 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Aug 6 20:15:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron GK107 [GeForce GT 640 OEM] [1b0a:90c5] MachineType: Hewlett-Packard 700-230qe ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic.efi.signed root=UUID=91d8e6ac-97d6-4068-a684-bc045f783fb5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2013 dmi.bios.vendor: AMI dmi.bios.version: 80.15 dmi.board.name: 2AF3 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.0 dmi.chassis.asset.tag: 2MD3480GR8 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.15:bd09/19/2013:svnHewlett-Packard:pn700-230qe:pvr:rvnHewlett-Packard:rn2AF3:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 700-230qe dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Aug 6 19:51:39 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1708977 Title: Cannot boot after update Status in xorg package in Ubuntu: New Bug description: Following minor linux update cannot boot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: /dev/sda1: clean, 223961/121970688 files, 8834593/487854592 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Aug 6 20:15:50 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron GK107 [GeForce GT 640 OEM] [1b0a:90c5] MachineType: Hewlett-Packard 700-230qe ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic.efi.signed root=UUID=91d8e6ac-97d6-4068-a684-bc045f783fb5 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2013 dmi.bios.vendor: AMI dmi.bios.version: 80.15 dmi.board.name: 2AF3 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.0 dmi.chassis.asset.tag: 2MD3480GR8 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.15:bd09/19/2013:svnHewlett-Packard:pn700-230qe:pvr:rvnHewlett-Packard:rn2AF3:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: 700-230qe dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1593907 was recently released to fix ntp/ntpdate interactions; if they're still broken, there seems little need to justify this given that precedent. (Full disclosure: I want ntp/ntpdate interactions solid so I can use ntpdate in the ntp charm. :-) -- 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/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 Installed 17.04 using minimal server install CD, wanted to use networkmanager to manage my interfaces, encountered this pesky bug. I had removed any mention of my wired interface in /etc/network/interfaces, and still it wouldn't show up in NetworkManager. If this is supposed to be default behavior, I do not approve. It is confusing and pretty hard to fix if you don't have the slightest idea where to look. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Confirm the bug with the dafault Xubuntu theme. $ env GTK_THEME=Abiword solves the problem, no more flickering -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Confirmed Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround for Ubuntu 16.04 LTS === 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+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 1411581] Re: HP CP4525 printer confused by evince (libcairo 1.13.0~20140204-0ubuntu1) font naming mismatch
Can you please attach a PDF that we can use to reproduce this problem? ** Tags added: trusty ** Changed in: cairo (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1411581 Title: HP CP4525 printer confused by evince (libcairo 1.13.0~20140204-0ubuntu1) font naming mismatch Status in cairo package in Ubuntu: Incomplete Bug description: I have an HP Color LaserJet Enterprise CP4525 with firmware 07.164.1, which supports PDF files natively (@PJL LANGUAGE=PDF), and a print server running Debian 7 (cups-filters 1.0.18 and its pdftopdf, and a PDF-enabled PPD). I have been given a PDF file (from pdflatex) that uses four Type 1 font subsets (of four different simple fonts). This file gets printed correctly with /usr/bin/lp . Not so when using evince on Ubuntu trusty: then the printer substitutes a different font (but keeping the glyph widths from the font object in the PDF file, so the letter spacings look all wrong). I've inspected the PDF file evince sends to the printer (which is not identical to the original PDF file: evince rewrites it) and noticed that the value of /FontName in the font program object doesn't match that of /FontName in the font descriptor object; the latter does match /BaseFont in the font object and has the form prescribed in §9.6.4 of the PDF 1.7 specification for font subsets. The /FontName in the font program object, on the other hand, is of the form /CairoFont-N-M, where N and M are integers. If I hand-edit the PDF output by evince, replacing /CairoFont-N-M with the value of /FontName in the corresponding font descriptor object (and adjusting /Length and /Length1 as needed), the result gets printed with the correct fonts. §9.6.2.1 of the PDF 1.7 specification (PDF 32000-1:2008, retrieved from Adobe's web site) does say that "[f]or Type 1 fonts, [BaseFont] is always the value of the FontName entry in the font program". One wonders, then, why Cairo changes the name. I could understand it if it wanted to make the font descriptors for two different subsets of the same font share the same font program object; but it doesn't take advantage of this. The sample file I have contains ligatures and accented letters, originally represented in a single font subset by using a non-standard encoding, and evince splits these font subsets into two parts, one of which uses /WinAnsiEncoding; each of the subsets gets its own font program object (with a different value of M in /CairoFont-N-M). So this is not the explanation. I think it would be prudent, in light of HP's PDF interpreter's behaviour, for Cairo to adhere more strictly to the wording of §9.6.2.1 and use the same /FontName in the font program object as in the font descriptor object. I think I'd also like for pdftopdf to incorporate a workaround for this, simply because I have more control over the print server than over the clients. But that's for another (wishlist) bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1411581/+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 1700037] Re: terminal not opening
Switch to a virtual terminal by pressing CTRL-ALT-F1 and login. Then try: sudo apt-get --fix-broken install When finished, switch back to the desktop with CTRL-ALT-F7. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1700037 Title: terminal not opening Status in cairo package in Ubuntu: New Bug description: Terminal not opening in my Ubuntu 16.04.Before this problem occurs a update was interrupted due to system shutdown(power outage). Cant even open vim. They just show blink in taskbar n nothing happens. Calendar on the menubar also not showing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1700037/+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 675863] Re: Too large amounts of data sent when printing images
** Tags added: karmic lucid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/675863 Title: Too large amounts of data sent when printing images Status in cairo package in Ubuntu: Confirmed Status in ghostscript package in Ubuntu: Fix Released Bug description: Binary package hint: cups Hello, For printing a image of small size, say, about 150 KB, more than 50 MB data are sent to the network printer (a Cannon C2550). This blocked all the other printing tasks in the queue, and is really a big trouble for me. Now I have to ask some colleague using Windows to print Google map for me. This problem only happens for image (e.g., .jpg), and for PDF file or open office file, there is no such problem. It is Ubuntu 10.10, upgraded from 8.10 continuously. If I remember, I think I started to suffered this problem since 9.10. Hereafter is the CPUS pacakges. Please let me know if you need more information to identify the problem. Just tell me how to do it, I would be very happy to help understanding this problem. Many thanks! dpkg --list | grep cups ii bluez-cups 4.69-0ubuntu2 Bluetooth printer driver for CUPS ii cups 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - server ii cups-bsd 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - BSD commands ii cups-client1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - common files ii cups-driver-gutenprint 5.2.6-0ubuntu8 printer drivers for CUPS ii cups-ppdc 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - PPD manipulation utilities ii cupsddk1.4.4-6ubuntu2.2 Common UNIX Printing System (transitional package) ii ghostscript-cups 8.71.dfsg.2-0ubuntu7 The GPL Ghostscript PostScript/PDF interpreter - CUPS filters ii hal-cups-utils 1.2.3+20100723-0ubuntu8.1 CUPS integration with HAL ii hplip-cups 3.10.6-1ubuntu10.1 HP Linux Printing and Imaging - CUPS Raster driver (hpcups) ii libcups2 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - Core library ii libcupscgi11.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - CGI library ii libcupsdriver1 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - Driver library ii libcupsimage2 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - Raster image library ii libcupsmime1 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - MIME library ii libcupsppdc1 1.4.4-6ubuntu2.2 Common UNIX Printing System(tm) - PPD manipulation library ii libgnomecups1.0-1 0.2.3-3build2 GNOME library for CUPS interaction ii python-cups1.9.51-0ubuntu2 Python bindings for CUPS ii python-cupshelpers 1.2.3+20100723-0ubuntu8.1 Python modules for printer configuration with CUPS --- Architecture: amd64 DistroRelease: Ubuntu 10.10 Lpstat: device for 2-cor-hp: lpd://2-cor-hp.print.cern.ch/2-cor-hp device for 2-r-lhcb: lpd://2-r-lhcb.print.cern.ch/2-r-lhcb device for Generic-text-only-printer: ///dev/null device for pasteque: lpd://pasteque.lal.in2p3.fr/print device for printemps: socket://134.158.88.136:9100 MachineType: Dell Inc. Latitude E6400 Package: cups 1.4.4-6ubuntu2.2 PackageArchitecture: amd64 Papersize: letter PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: printemps: Canon imageRunner C2550 Foomatic/pxlcolor (recommended) pasteque: KONICA MINOLTA 500/420/360PS(P) 2-cor-hp: HP LaserJet p4515x, hpcups 3.10.6 2-r-lhcb: HP LaserJet P3005 Postscript (recommended) ProcCmdLine:
[Touch-packages] [Bug 1160894] Re: SVG to EPS export with transparency
** Changed in: cairo (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1160894 Title: SVG to EPS export with transparency Status in cairo package in Ubuntu: Invalid Bug description: When I try to export SVG to EPS in Inkscape, my transparent objects get rasterized. This seems to be related to bug 168610, where gradients get rasterized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1160894/+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 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power
** Also affects: libmatemixer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1580394 Title: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power Status in alsa-driver package in Ubuntu: New Status in libmatemixer package in Ubuntu: New Bug description: I have noticed that when I am on battery power on a Dell Latitude 3340 laptop with headphones plugged in , and there is no audio playing on the computer, there is a consistent static sound that comes through the headphones at a constant volume that is not affected by changing the volume level. I think it may be picking up some kind of analog loopback signal because keyboard presses and disk activity seem to influence the noise. When I plug the power cable into the laptop , the static immediately goes away. I reported this earlier to the upstream Linux Kernel bug tracker, but it seems to be fixed in any distro running a 4.4 kernel or greater that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This make me think it is not a kernel level issue and is found somewhere either in the audio settings on Ubuntu MATE or a pulseaudio bug. I cannot reproduce it on any other 16.04 distro version, but it also affects all the 14.04.4 distros as well. Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent the static. The BIOS Firmware version is up to date. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu-mate 1718 F pulseaudio /dev/snd/controlC0: ubuntu-mate 1718 F pulseaudio CasperVersion: 1.376 CurrentDesktop: MATE Date: Wed May 11 00:43:52 2016 LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+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 1707898] Re: systemd translations are not synced with upstream
** Also affects: ubuntu-translations 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/1707898 Title: systemd translations are not synced with upstream Status in Ubuntu Translations: New Status in systemd package in Ubuntu: New Bug description: Translations for systemd are outdated because they do not seem to be synced with the upstream ones. For example the Czech one: Launchpad: https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate - 0% translated Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+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 1708933] [NEW] Can't add a Microsoft account to GNOME Online Accounts
Public bug reported: In artful: 1) Open Settings->Online Accounts 2) Click on "Microsoft" under "Add an account" 3) See an authorization window pop up, enter my user/password for Microsoft Live 4) Click next, see it ask whether it's OK to give GNOME various permissions 5) Click yes, see the window disappear But at this point, no Microsoft account appears in the active-accounts section. It just seems to have closed the window and done nothing. Is there a way to get better logging for this and try again? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 6 10:03:55 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (1669 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1708933 Title: Can't add a Microsoft account to GNOME Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: In artful: 1) Open Settings->Online Accounts 2) Click on "Microsoft" under "Add an account" 3) See an authorization window pop up, enter my user/password for Microsoft Live 4) Click next, see it ask whether it's OK to give GNOME various permissions 5) Click yes, see the window disappear But at this point, no Microsoft account appears in the active-accounts section. It just seems to have closed the window and done nothing. Is there a way to get better logging for this and try again? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 6 10:03:55 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (1669 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
А есть туры в отель Odyssee 4*? Исходное сообщение От: Carl Vincent Olmo <1553...@bugs.launchpad.net> Дата: 06.08.17 4:27 (GMT+03:00) Кому: m...@ivvl.ru Тема: [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work Still not working..i hope someone can fix this problem... -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware 1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias:
[Touch-packages] [Bug 1708931] [NEW] Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04
Public bug reported: It happens at every reset, after using bluetooth mouse for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 6 16:42:56 2017 InstallationDate: Installed on 2017-08-05 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN97WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: B4:6D:83:B1:A7:87 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:301634 acl:15117 sco:0 events:1578 errors:0 TX bytes:2425 acl:31 sco:0 commands:169 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1708931 Title: Bluetooth service disconnects mouse after few minutes in Ubuntu Budgie 17.04 Status in bluez package in Ubuntu: New Bug description: It happens at every reset, after using bluetooth mouse for a few minutes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 6 16:42:56 2017 InstallationDate: Installed on 2017-08-05 (1 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic root=UUID=0585caf9-68a0-4a81-ba3d-c030affa951e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN97WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN97WW:bd01/08/2016:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: B4:6D:83:B1:A7:87 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:301634 acl:15117 sco:0 events:1578 errors:0 TX bytes:2425 acl:31 sco:0 commands:169 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708931/+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 1708930] Re: update overwrites customized apt-daily.timer
You have to use drop in units or something in /etc, files in /lib are not supposed to be modified. ** Changed in: apt (Ubuntu) Status: New => Invalid -- 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/1708930 Title: update overwrites customized apt-daily.timer Status in apt package in Ubuntu: Invalid Bug description: Ubuntu 16.04.03 LTS apt (1.2.24) I customize /lib/systemd/system/apt-daily.timer on my public facing servers so they only update and reboot once a week, at an earlier time of day, to reduce downtime during a busy part of our day. The update this week overwrote the file with no notice or prompting that it was about to overwrite a customized file. This turned out badly as we had servers rebooting a couple days later at the worst time of the day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1708930/+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 1708930] [NEW] update overwrites customized apt-daily.timer
Public bug reported: Ubuntu 16.04.03 LTS apt (1.2.24) I customize /lib/systemd/system/apt-daily.timer on my public facing servers so they only update and reboot once a week, at an earlier time of day, to reduce downtime during a busy part of our day. The update this week overwrote the file with no notice or prompting that it was about to overwrite a customized file. This turned out badly as we had servers rebooting a couple days later at the worst time of the day. ** 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/1708930 Title: update overwrites customized apt-daily.timer Status in apt package in Ubuntu: New Bug description: Ubuntu 16.04.03 LTS apt (1.2.24) I customize /lib/systemd/system/apt-daily.timer on my public facing servers so they only update and reboot once a week, at an earlier time of day, to reduce downtime during a busy part of our day. The update this week overwrote the file with no notice or prompting that it was about to overwrite a customized file. This turned out badly as we had servers rebooting a couple days later at the worst time of the day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1708930/+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 1707898] Re: systemd translations are not synced with upstream
Some languages are even unavailable via Launchpad even though they are present in upstream. -- 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/1707898 Title: systemd translations are not synced with upstream Status in systemd package in Ubuntu: New Bug description: Translations for systemd are outdated because they do not seem to be synced with the upstream ones. For example the Czech one: Launchpad: https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate - 0% translated Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707898/+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 1708924] [NEW] Monitor positions and resolution not saved
Public bug reported: Upon boot, I always have right monitor ending up on the left and vice versa. I have to move them every single time after boot and after I turn off both then turn on both. It never saves my settings. Also, 1 of the monitors is 4k and other one is 2560x1440 max, I save them both to be 2560x1440 but after boot or turn off/turn on sequence 4k goes into max resolution of 3840x2160. I tried various options with xrandr but nothing helps. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Aug 6 00:58:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Hawaii PRO [Radeon R9 290] [1043:04dd] InstallationDate: Installed on 2016-04-02 (490 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=322e367a-ab42-4f50-9ddf-fc99d43a174c ro plymouth SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Rampage III Extreme dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd05/12/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnRampageIIIExtreme:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Aug 6 00:51:37 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: amdgpu ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu xenial ** Summary changed: - Monitor positions not saved + Monitor positions and resolution not saved -- 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/1708924 Title: Monitor positions and resolution not saved Status in xorg package in Ubuntu: New Bug description: Upon boot, I always have right monitor ending up on the left and vice versa. I have to move them every single time after boot and after I turn off both then turn on both. It never saves my settings. Also, 1 of the monitors is 4k and other one is 2560x1440 max, I save them both to be 2560x1440 but after boot or turn off/turn on sequence 4k goes into max resolution of 3840x2160. I tried various options with xrandr but nothing helps. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Aug 6 00:58:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Hawaii PRO [Radeon R9 290] [1043:04dd] InstallationDate: Installed on 2016-04-02 (490 days ago) InstallationMedia: Ubuntu 14.04.4 LTS
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
Similarly, it would be great, if unattended-upgrade, apt and whatnot package tool software could predict that the requested install will not fit in system and act accordingly. Then the error in post-installation script would not happen then. The size could be hard to know in general case. If I have understood correctly, Software Updater uses information about older kernels as basis for calculating such a limit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space Status in initramfs-tools: Confirmed Status in Software Updater: Invalid Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
Marked as invalid against Software Updater (i.e. update-manager) since there is a separate report for it: Bug #1460396 ** Changed in: update-manager Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space Status in initramfs-tools: Confirmed Status in Software Updater: Invalid Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708912] Re: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1708912 Title: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gdb package in Ubuntu: New Bug description: cannot install that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gdbserver 7.11.1-0ubuntu1~16.5 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Aug 6 15:38:04 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:gdbserver:7.11.1-0ubuntu1~16.5 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package gdbserver (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-25 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gdb Title: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1708912/+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 1708912] [NEW] package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: cannot install that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gdbserver 7.11.1-0ubuntu1~16.5 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Aug 6 15:38:04 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:gdbserver:7.11.1-0ubuntu1~16.5 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package gdbserver (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-25 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gdb Title: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1708912 Title: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gdb package in Ubuntu: New Bug description: cannot install that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gdbserver 7.11.1-0ubuntu1~16.5 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Aug 6 15:38:04 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:gdbserver:7.11.1-0ubuntu1~16.5 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package gdbserver (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-25 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gdb Title: package gdbserver 7.11.1-0ubuntu1~16.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1708912/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
... and 'sudo apt-get autoremove' would work, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
I wonder why fix to Bug #1439769 has not been released as SRU for 14.04 yet. The fix would make unattended-upgrade work better in removing extra kernels in 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+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
