[Touch-packages] [Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
[Expired for resolvconf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: resolvconf (Ubuntu) Status: Incomplete => Expired -- 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/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration Status in resolvconf package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ...and reboot. You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/interfaces or /etc/network/interfaces.d/* will not provide DNS configuration in /etc/resolv.conf and /run/resolvconf/interfaces/. This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines "make_resolv_conf()" as a valid function for the BOUND case, but /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now, eh?) even though resolved is masked. The file existence check in the beginning of /etc/dhcp/dhclient-enter- hooks.d/resolved should be more thorough, i.e. it should ensure that resolved is enabled, rather than simply look for the existence of /lib/systemd/systemd-resolved. This works for me: -if [ -x /lib/systemd/systemd-resolved ] ; then +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled systemd-resolved ; then Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a similar check, looking for /run/resolvconf/enable-updates as a condition for meddling with DNS settings. If desired, I'll file a separate bug for that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 1776381] [NEW] lxc-test-api-reboot will hang with autopkgtest
Public bug reported: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps: - 1. Deploy Bionic on a bare-metal system. - 2. Enable deb-src, install the autopkgtest package - 3. sudo autopkgtest lxc -- null + 1. Deploy Bionic on a bare-metal system. + 2. Enable deb-src, install the autopkgtest package + 3. sudo autopkgtest lxc -- null Result: - * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: - make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' - make[1]: Nothing to be done for 'all-am'. - make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' - * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: - Connected to tty 1 - Type to exit the console, to enter Ctrl+a itself - * If you kill the job and run it again, this time the test will go on (fail with the reboot test, as the container has already been created) + * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: + make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' + make[1]: Nothing to be done for 'all-am'. + make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' + * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: + Connected to tty 1 + Type to exit the console, to enter Ctrl+a itself + * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. -- 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/1776381 Title: lxc-test-api-reboot will hang with autopkgtest Status in lxc package in Ubuntu: New Bug description: Steps: 1. Deploy Bionic on a bare-metal system. 2. Enable deb-src, install the autopkgtest package 3. sudo autopkgtest lxc -- null Result: * The test will hang, a "reboot" lxc container will be created. The last message on the screen will be: make[1]: Entering directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' make[1]: Nothing to be done for 'all-am'. make[1]: Leaving directory '/tmp/autopkgtest.JxRLRE/build.bSQ/src' * Tried to connect to the "reboot" container with "sudo lxc-console reboot", but nothing there: Connected to tty 1 Type to exit the console, to enter Ctrl+a itself * If you kill the job and run it again, this time the test will go on (fail with the lxc-test-api-reboot test, as the container has already been created) This issue can be reproduced on an amd64 box and a s390x zKVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1776381/+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 1089105] Re: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid
Precise EOL. ** Changed in: pm-utils (Ubuntu Precise) Status: New => Won't Fix ** Changed in: pm-utils (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1089105 Title: [Lenovo V480c Notebook]: Trackpad doesn't work after closing and opening the lid Status in linux package in Ubuntu: Won't Fix Status in pm-utils package in Ubuntu: Won't Fix Status in linux source package in Precise: Won't Fix Status in pm-utils source package in Precise: Won't Fix Status in linux source package in Quantal: Won't Fix Status in pm-utils source package in Quantal: Won't Fix Status in linux source package in Raring: Won't Fix Status in pm-utils source package in Raring: Won't Fix Bug description: Problem: System does not resume from suspend properly. The issue is intermitent. However most of the time the system will exhibit three problematic symptoms: 1.) System will fail to resume and start x altogether 2.) System will resume with applications in frozen state and unity unresponsive to mouse-clicks. 3.) System will resume however trackpad will be disabled. kernel tested: 3.2.0-29-generic #46-Ubuntu Release: Ubuntu 12.04.1 Can reproduce? Yes Steps: 1.) Close laptop lid 2.) wait approx 5 minutes 3.) open laptop lid for system to resume. Expected result: System is able to suspend state and applications and resume when lid is opened in a proper and timely fashion. Command to recreate: fwts_test -s s3 --s3-sleep-delay=30 --s3-device-check | tee suspend_single_times.log WORKAROUND: Log into GNOME, and manually enable the touchpad through: dconf-editor->/org/gnome/settings-daemon/peripherals/touchpad/touchpad-enabled ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-29-generic 3.2.0-29.46 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1579 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x9b61 irq 46' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa500f,00100202 HDA:80862806,80860101,0010' Controls : 26 Simple ctrls : 12 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue Dec 11 15:38:03 2012 HibernationDevice: RESUME=UUID=98d6d8c6-aa75-4069-9714-4f972d11aa61 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: LENOVO 814TF01 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb 1 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=c1701df9-c6b6-4425-b6ec-5fede7c00ad6 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic N/A linux-backports-modules-3.2.0-29-generic N/A linux-firmware1.79 SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET26WW (0.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 814TF01 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:bvrH5ET26WW(0.26):bd03/29/2012:svnLENOVO:pn814TF01:pvrLenovoV480c:rvnLENOVO:rn814TF01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814TF01 dmi.product.version: Lenovo V480c dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1089105/+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 1697535] Re: [Envy24 ICE1724] Audio doesn't work
This bug still exists in Ubuntu 18.04 $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic $ pulseaudio --version pulseaudio 11.1 -- 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/1697535 Title: [Envy24 ICE1724] Audio doesn't work Status in pulseaudio package in Ubuntu: New Bug description: Release: Ubuntu 17.04 PulseAudio Version: 1:10.0-1ubuntu2 I expected the audio on my system to work without any additional action on my part. Instead, the audio does not work despite working on Windows. A few years ago, my onboard sound broke so I bought a pci sound card (ENCORE ENM232-8VIA 7.1) which seems to have the Envy24 ICE1724 chipset. This sound card works on Windows but not Ubuntu or Debian. I've attempted to troubleshoot this myself over the past year or so and had no luck figuring out the problem (though ubuntu-bug seems to think there is a problem with pulseaudio). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Mon Jun 12 14:00:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-12-10 (184 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to zesty on 2017-04-18 (55 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.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.:bvr1104:bd09/11/2009:svnSystemmanufacturer:pnP5QL-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-E:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5QL-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1697535/+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 1720827] Re: Tab selection shouldn't have a "resize" effect
This is also applies to communitheme. -- 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/1720827 Title: Tab selection shouldn't have a "resize" effect Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: When alternating between tabs in Systems Settings -> Sound, for instance, we can notice that the tabs get resized after a tab is selected, which looks like a small visual glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1720827/+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 1776362] Re: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1776362 Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in poppler package in Ubuntu: New Bug description: did not install after clean boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpoppler73:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 11 20:06:11 2018 DuplicateSignature: package:libpoppler-glib8:amd64:0.62.0-2ubuntu2.1 Processing triggers for libc-bin (2.27-3ubuntu1) ... dpkg: error processing package libpoppler-glib8:amd64 (--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 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: poppler Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 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/poppler/+bug/1776362/+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 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop
Markus Baumann, thank you for reporting this and helping make Ubuntu better. 1) To clarify, if you don't adjust the MTU does the LAN network still connection cycle? 2) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Tags added: bios-outdated-2.72 regression-release ** No longer affects: network-manager (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1754759 Title: LAN connection keeps connecting and disconnecting in an infinite loop Status in linux package in Ubuntu: Incomplete Bug description: With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop: - Boot from live-ISO - Click on network icon in title bar and edit LAN-connection - Change MTU from Auto to 1492 - Connect LAN cable => LAN network keeps connecting and disconnecting in an infinite loop (No wireless network is configured.) The error did not occur on Xubuntu 16.04. The same situation occurs with Xubuntu installed on the SSD. I took the ISO for this bug report, in order to exclude wrong settings on the installed system. This is my first bug report - I hope I did not do too much wrong. If necessary, I can provide more information. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: XFCE Date: Fri Mar 9 20:26:21 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 802-3-ethernet 1520627169 Fr 09 Mär 2018 20:26:09 UTC yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp0s25 activated /org/freedesktop/NetworkManager/ActiveConnection/32 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 db135360-f229-3472-bd3a-eb8d6bc8b601 /org/freedesktop/NetworkManager/ActiveConnection/32 wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3822 F pulseaudio CasperVersion: 1.387 DistroRelease: Ubuntu 17.10 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.110.120.1 dev enp0s25 proto static metric 100 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 100 169.254.0.0/16 dev enp0s25 scope link metric 1000 LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: LENOVO 2333B15 Package: network-manager 1.8.4-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash
[Touch-packages] [Bug 1776362] [NEW] package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Public bug reported: did not install after clean boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpoppler73:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 11 20:06:11 2018 DuplicateSignature: package:libpoppler-glib8:amd64:0.62.0-2ubuntu2.1 Processing triggers for libc-bin (2.27-3ubuntu1) ... dpkg: error processing package libpoppler-glib8:amd64 (--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 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: poppler Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 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: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1776362 Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in poppler package in Ubuntu: New Bug description: did not install after clean boot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 wl ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libpoppler73:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 11 20:06:11 2018 DuplicateSignature: package:libpoppler-glib8:amd64:0.62.0-2ubuntu2.1 Processing triggers for libc-bin (2.27-3ubuntu1) ... dpkg: error processing package libpoppler-glib8:amd64 (--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 2018-06-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: poppler Title: package libpoppler-glib8:amd64 0.62.0-2ubuntu2.1 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/poppler/+bug/1776362/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I have got the same issue. cURL and MongoDB cannot be installed at the same time due to libcurl3 and libcurl4 conflicts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1776329] [NEW] apport-cli and cowbuilder fail with cert and keyring errors
Public bug reported: Description: Ubuntu 18.04 LTS Release: 18.04 ubuntu-keyring: Installed: 2018.02.28 apport: Installed: 2.20.9-0ubuntu7.2 cowbuilder: Installed: 0.86 On a bionic system when attempting to report what I suspect is a bug in ubuntu-keying I got the following error start capture- $ apport-cli ubuntu-keyring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (1.2 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. *** Error: Network problem Cannot connect to crash database, please check your Internet connection. Press any key to continue... end capture--- I worked around the problem by K'eeping the report and copying it to a Xenial system. From there I am submitting this bug report. The original problem that caused me to attempt to file a bug report against ubuntu-keyring was an attempt to build a bionic chroot for package building with the following command: start capture- # DIST=bionic cowbuilder --create --distribution bionic --components "main universe" --basepath /var/cache/pbuilder/base-bionic-amd64-test.cow --mirror http://us.archive.ubuntu.com:80/ubuntu --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg I: Invoking pbuilder I: forking: pbuilder create --components 'main universe' --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --buildplace /var/cache/pbuilder/base-bionic-amd64-test.cow --mirror http://us.archive.ubuntu.com:80/ubuntu --distribution bionic --no-targz --extrapackages cowdancer W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: Distribution is bionic. I: Current time: Mon Jun 11 22:44:21 UTC 2018 I: pbuilder-time-stamp: 1528757061 I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Retrieving InRelease I: Checking Release signature E: Release signed by unknown key (key id 3B4FE6ACC0B21F32) E: debootstrap failed E: Tail of debootstrap.log: gpgv: Signature made Thu Apr 26 23:38:40 2018 UTC gpgv:using RSA key 3B4FE6ACC0B21F32 gpgv: Can't check signature: No public key E: End of debootstrap.log W: Aborting with an error E: pbuilder create failed I: forking: rm -rf /var/cache/pbuilder/base-bionic-amd64-test.cow end capture--- On the same system the following command succeeds: start capture- DIST=xenial cowbuilder --create --distribution xenial \ --components "main universe" \ --basepath /var/cache/pbuilder/base-xenial-amd64.cow \ --mirror http://us.archive.ubuntu.com:80/ubuntu \ --debootstrapopts --keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg end capture--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-keyring 2018.02.28 [modified: usr/share/keyrings/ubuntu-archive-keyring.gpg] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jun 11 22:51:48 2018 Dependencies: PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 TERM=xterm SHELL=/bin/bash PATH=(custom, no user) SourcePackage: ubuntu-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1776329 Title: apport-cli and cowbuilder fail with cert and keyring errors Status in ubuntu-keyring package in Ubuntu: New Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 ubuntu-keyring: Installed: 2018.02.28 apport: Installed: 2.20.9-0ubuntu7.2 cowbuilder: Installed: 0.86 On a bionic system when attempting to report what I suspect is a bug in ubuntu-keying I got the following error start
[Touch-packages] [Bug 1757561] Re: Wifi disconnects randomly under ubuntu 17.10
Mijail Febres Soria, to see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** No longer affects: network-manager (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087454/+files/RfKill.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087453/+files/PulseList.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087451/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087450/+files/ProcEnviron.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087452/+files/ProcModules.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087448/+files/PciNetwork.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087447/+files/NetworkManager.conf.txt ** Attachment removed: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087446/+files/NetDevice.wlp3s0.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087449/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "NetDevice.lo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087445/+files/NetDevice.lo.txt ** Attachment removed: "NetDevice.enp4s0.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087444/+files/NetDevice.enp4s0.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087441/+files/JournalErrors.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087440/+files/IwConfig.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087443/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087442/+files/Lspci.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087438/+files/Dependencies.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087436/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087437/+files/CurrentDmesg.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087435/+files/AlsaInfo.txt ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087422/+files/nmcli-con.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087421/+files/WifiSyslog.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087419/+files/RfKill.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087420/+files/UdevDb.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087417/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087416/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087415/+files/ProcEnviron.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087418/+files/PulseList.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087414/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087413/+files/PciNetwork.txt ** Attachment removed: "NetworkManager.conf.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757561/+attachment/5087412/+files/NetworkManager.conf.txt ** Attachment removed: "NetDevice.wlp3s0.txt"
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Foundations team, has anyone looked at ureadahead lately to make sure that it still makes sense to include it? (a) I suspect SSDs don't benefit much from it (b) I suspect systems with spinning metal drives are also unlikely to have the memory to cache all those files, nor the free IO cycles to spend on caching. (c) If 90k files are ignored entirely because the paths are all relative, is anything being cached at all? I realize these are contradictory concerns. :) Thanks -- 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/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 1759836] Re: systemd-udevd consumes 100% of CPU
Same problem with an old Dell Inspiron 1545 recently upgraded to Ubuntu 18.04 (4.15.0-22-generic). After disabling Bluetooth in the Bios and removing package Bluez, system is usable again. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Unknown Status in linux: Unknown Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+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 1776323] [NEW] Sound cracks in video player
Public bug reported: When I play audio or video, the sound is really terrible. It goes up and down by itself ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geektutor 1525 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 11 23:17:48 2018 InstallationDate: Installed on 2018-06-08 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jun 11 23:07:52 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:07:53 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.50' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:09:02 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80' (uid=1000 pid=1525 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP ProBook 6450b, IDT 92HD75B3X5, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CDF Ver. F.03 dmi.board.name: 146E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 73.11 dmi.chassis.asset.tag: CNU0452QT8 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CDFVer.F.03:bd10/04/2010:svnHewlett-Packard:pnHPProBook6450b:pvr:rvnHewlett-Packard:rn146E:rvrKBCVersion73.11:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 6450b dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-06-11T23:17:29.683944 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1776323 Title: Sound cracks in video player Status in alsa-driver package in Ubuntu: New Bug description: When I play audio or video, the sound is really terrible. It goes up and down by itself ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: geektutor 1525 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jun 11 23:17:48 2018 InstallationDate: Installed on 2018-06-08 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jun 11 23:07:52 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:07:53 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.50' (uid=120 pid=1039 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Jun 11 23:09:02 TGM dbus-daemon[840]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.80' (uid=1000 pid=1525 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [HP ProBook 6450b, IDT 92HD75B3X5, Speaker, Internal] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2010
[Touch-packages] [Bug 1720517] Re: Software and Updates /Other Software greys out when clicking on "Canonical Partners"
Also happening on Ubuntu 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1720517 Title: Software and Updates /Other Software greys out when clicking on "Canonical Partners" Status in software-properties package in Ubuntu: Confirmed Bug description: "Other Software" only works after having clicked on "Ubuntu Software", "Updates", etc and changing some settings on those pages. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.16 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 30 10:44:47 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2017-09-29 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1720517/+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 1774739] Re: Running Qt apps inside a 18.04 container crashes
Note I have tried using the .run offline installer of Qt 5.6/5.9/5.11, what seems to happen is that they work on Ubuntu 16.04, 17.10 but fail on 18.04 - this is the stacktrace for reference https://pastebin.ubuntu.com/p/Yzj5gsmwQ3/ So it seems possible that it might be some underlying change to the platform (maybe something like dbus? or a new config/dir I need to enable). Furthermore it looks like this issue may affect Qt applications when they try to run as a snap under the core18 snap. https://github.com/snapcore/core18/issues/4 ** Bug watch added: github.com/snapcore/core18/issues #4 https://github.com/snapcore/core18/issues/4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1774739 Title: Running Qt apps inside a 18.04 container crashes Status in qtbase-opensource-src package in Ubuntu: New Bug description: What happened: 1) Install a container system (eg Docker, LXD) - I'm using Docker 2) Create a container which is Ubuntu 18.04 3) Install a Qt app, eg qtcreator, inside the container 4) Run the container so that it shows the hosts X11 socket 5) Notice that the application fails to start What I expected to happen: At step 5 for the application to start. Note that the same steps work fine for Ubuntu 16.04 and 17.10 - and if it matters my host is 17.10. Here is a stacktrace of the crash https://pastebin.ubuntu.com/p/WKKGmxqqSx/ Here is a Dockerfile that reproduces the issue https://pastebin.ubuntu.com/p/nzmJRfPYVc/ to use this make a Dockerfile in an empty folder with the pastebin contents, then simply run the following commands in that folder $ sudo apt install docker.io $ sudo docker build -t qtbug . $ sudo docker run --rm -ti -e DISPLAY --net=host --cap-add=SYS_PTRACE --security-opt seccomp=unconfined qtbug This should enter you into the gdb session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1774739/+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 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
I also ran unattended-upgrades and aptdcon --system-upgrade, both of which performed normally. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in python-apt source package in Bionic: Fix Committed Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
Fix works fine: root@bionic:~# python3 -c "import apt; c=apt.Cache(); p=c['aptitude']; c.open(); p.mark_install()" Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/apt/package.py", line 1469, in mark_install self._pcache._depcache.mark_install(self._pkg, auto_inst, from_user) ValueError: Object of different cache passed as argument to apt_pkg.DepCache method root@bionic:~# dpkg -i python3-apt_1.6.1_amd64.deb (Reading database ... 29845 files and directories currently installed.) Preparing to unpack python3-apt_1.6.1_amd64.deb ... Unpacking python3-apt (1.6.1) over (1.6.0) ... Setting up python3-apt (1.6.1) ... root@bionic:~# python3 -c "import apt; c=apt.Cache(); p=c['aptitude']; c.open(); p.mark_install()" another check: root@bionic:~# python3 -c "import apt; c=apt.Cache(); p=c['aptitude']; c.open(); p.mark_delete(); print(c.get_changes()); c.commit()" [] (Reading database ... 29852 files and directories currently installed.) Removing aptitude (0.8.10-6ubuntu1) ... ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in python-apt source package in Bionic: Fix Committed Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1776098] Re: package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/1776098 Title: package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in patch package in Ubuntu: New Bug description: no idea about this bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: patch 2.7.5-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98 Uname: Linux 4.4.0-116-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Jun 10 23:47:14 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2018-06-10 23:47:03 Commandline: apt-get install -f Requested-By: dhiliptg (1000) Upgrade: update-notifier-common:amd64 (3.168.7, 3.168.8) DpkgTerminalLog: Preparing to unpack .../update-notifier-common_3.168.8_all.deb ... Unpacking update-notifier-common (3.168.8) over (3.168.7) ... dpkg: error processing package patch (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:patch:2.7.5-1ubuntu0.16.04.1 Unpacking update-notifier-common (3.168.8) over (3.168.7) ... dpkg: error processing package patch (--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 2016-11-17 (570 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: patch Title: package patch 2.7.5-1ubuntu0.16.04.1 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/patch/+bug/1776098/+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 1776098] Re: package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to patch in Ubuntu. https://bugs.launchpad.net/bugs/1776098 Title: package patch 2.7.5-1ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in patch package in Ubuntu: New Bug description: no idea about this bug ProblemType: Package DistroRelease: Ubuntu 16.04 Package: patch 2.7.5-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-lowlatency 4.4.98 Uname: Linux 4.4.0-116-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sun Jun 10 23:47:14 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2018-06-10 23:47:03 Commandline: apt-get install -f Requested-By: dhiliptg (1000) Upgrade: update-notifier-common:amd64 (3.168.7, 3.168.8) DpkgTerminalLog: Preparing to unpack .../update-notifier-common_3.168.8_all.deb ... Unpacking update-notifier-common (3.168.8) over (3.168.7) ... dpkg: error processing package patch (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:patch:2.7.5-1ubuntu0.16.04.1 Unpacking update-notifier-common (3.168.8) over (3.168.7) ... dpkg: error processing package patch (--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 2016-11-17 (570 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: patch Title: package patch 2.7.5-1ubuntu0.16.04.1 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/patch/+bug/1776098/+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 1773316] Re: Object of different cache passed as argument to apt_pkg.DepCache method
Hello errors.ubuntu.com, or anyone else affected, Accepted python-apt into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python-apt/1.6.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python-apt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: update-manager (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1773316 Title: Object of different cache passed as argument to apt_pkg.DepCache method Status in python-apt package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Won't Fix Status in python-apt source package in Bionic: Fix Committed Status in update-manager source package in Bionic: Won't Fix Status in python-apt source package in Cosmic: Fix Released Status in update-manager source package in Cosmic: Won't Fix Bug description: [Impact] python-apt 1.6 raises an exception when objects of an old cache are passed to a apt_pkg.DepCache methods for a different cache. Prior to that, those would either segfault, succeed, or silently operate on a different object, as they use package/version ids, and e.g. two different packages in the old and new cache might have the same id. With 1.6.1, we introduce a remapping algorithm that remaps objects of apt.Cache() when calling apt.Cache.open(), allowing old objects to be used after reopening, as long as they exist in the new cache. If they don't exist in the new cache, apt_pkg.CacheMismatchError will be raised from the apt_pkg layer. [Test case] import apt c=apt.Cache() p=c["apt"] c.open() p.mark_install() [Regression potential] Could be remapping to wrong items which would cause us to install a wrong version, for example. Compared to pre-bionic, bionic is a regression already, though, and any regression caused here is less important than what we have now. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:18.04.11, the problem page at https://errors.ubuntu.com/problem/e6ff7b5c385c512b7933497ad895c8a19ed063b2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1773316/+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 1226855] Re: Cannot use open-iscsi inside LXC container
Is this still a problem on Ubuntu 18.04? -- 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/1226855 Title: Cannot use open-iscsi inside LXC container Status in linux package in Ubuntu: Confirmed Status in lxc package in Ubuntu: Confirmed Bug description: Trying to use open-iscsi from within an LXC container, but the iscsi netlink socket does not support multiple namespaces, causing: "iscsid: sendmsg: bug? ctrl_fd 6" error and failure. Command attempted: iscsiadm -m node -p $ip:$port -T $target --login Results in: Exit code: 18 Stdout: 'Logging in to [iface: default, target: $target, portal: $ip,$port] (multiple)' Stderr: 'iscsiadm: got read error (0/0), daemon died? iscsiadm: Could not login to [iface: default, target: $target, portal: $ip,$port]. iscsiadm: initiator reported error (18 - could not communicate to iscsid) iscsiadm: Could not log into all portals' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 17 14:38:08 2013 InstallationDate: Installed on 2013-01-15 (245 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-05-16 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226855/+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 1776243] Re: package linux-image-4.13.0-43-generic 4.13.0-43.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
** Tags removed: need-duplicate-check -- 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/1776243 Title: package linux-image-4.13.0-43-generic 4.13.0-43.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: Some errors while i' m updating to Ubuntu 18.04 from 16.04 using sudo apt update && sudo apt dist-upgrade sudo apt install update-manager-core sudo do-release-upgrade I' m updating because i can' t use cuda 9.2 if i use the nvidia-396 drivers which have cuda 9.2 i can' t login (i' m bounced back). ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vegito 2105 F pulseaudio /dev/snd/controlC2: vegito 2105 F pulseaudio /dev/snd/controlC0: vegito 2105 F pulseaudio Date: Mon Jun 11 17:38:12 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=8162ddfa-6b43-4039-ba85-2b4b2fbd35de InstallationDate: Installed on 2018-03-11 (92 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=b2892717-c9b9-459c-9cb1-1f5c328e4ea7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.13.0-43-generic 4.13.0-43.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to artful on 2018-06-11 (0 days ago) dmi.bios.date: 07/22/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: H81 Pro BTC R2.0 dmi.board.vendor: ASRock 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: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd07/22/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81ProBTCR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1776243/+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 1776243] [NEW] package linux-image-4.13.0-43-generic 4.13.0-43.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Public bug reported: Some errors while i' m updating to Ubuntu 18.04 from 16.04 using sudo apt update && sudo apt dist-upgrade sudo apt install update-manager-core sudo do-release-upgrade I' m updating because i can' t use cuda 9.2 if i use the nvidia-396 drivers which have cuda 9.2 i can' t login (i' m bounced back). ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vegito 2105 F pulseaudio /dev/snd/controlC2: vegito 2105 F pulseaudio /dev/snd/controlC0: vegito 2105 F pulseaudio Date: Mon Jun 11 17:38:12 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=8162ddfa-6b43-4039-ba85-2b4b2fbd35de InstallationDate: Installed on 2018-03-11 (92 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=b2892717-c9b9-459c-9cb1-1f5c328e4ea7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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: grub-pc N/A RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.13.0-43-generic 4.13.0-43.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to artful on 2018-06-11 (0 days ago) dmi.bios.date: 07/22/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: H81 Pro BTC R2.0 dmi.board.vendor: ASRock 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: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.20:bd07/22/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81ProBTCR2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful third-party-packages -- 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/1776243 Title: package linux-image-4.13.0-43-generic 4.13.0-43.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: Some errors while i' m updating to Ubuntu 18.04 from 16.04 using sudo apt update && sudo apt dist-upgrade sudo apt install update-manager-core sudo do-release-upgrade I' m updating because i can' t use cuda 9.2 if i use the nvidia-396 drivers which have cuda 9.2 i can' t login (i' m bounced back). ProblemType: Package DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vegito 2105 F pulseaudio /dev/snd/controlC2: vegito 2105 F pulseaudio /dev/snd/controlC0: vegito 2105 F pulseaudio Date: Mon Jun 11 17:38:12 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=8162ddfa-6b43-4039-ba85-2b4b2fbd35de InstallationDate: Installed on 2018-03-11 (92 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IwConfig: enp5s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed root=UUID=b2892717-c9b9-459c-9cb1-1f5c328e4ea7 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or
[Touch-packages] [Bug 1776215] Re: i lost my menu and title bar
** Package changed: xorg (Ubuntu) => unity (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/1776215 Title: i lost my menu and title bar Status in unity package in Ubuntu: New Bug description: i can't access my menu and title bar i need your help to restore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 11 13:49:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kabini [Radeon HD 8210] [103c:21f7] InstallationDate: Installed on 2014-11-04 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=661e7b31-e7f7-4fe1-b992-35c89b3ab5a7 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 21F7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd01/03/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21F7:rvr52.16:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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: Mon Jun 11 13:46:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1776215/+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 1773213] Re: U1 login dialog missing link to the privacy policy
** Description changed: The U1 login for g-o-a is missing a link to the privacy policy. + + [Impact] + + * No way to view the privacy policy for Ubuntu One + + [Test Case] + + * Open gnome-control-center + * Select "Online Accounts" on the left + * Select "Ubuntu Single Sign-On" under "Add an account" + * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. + * Verify when clicking the window a browser window opens with our data privacy page + + [Regression Potential] + + * None -- 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/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: New Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies
** Tags removed: triage-a ** Tags added: triage-g -- 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/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null) CPU min MHz: (null) L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-31 NUMA node1 CPU(s): 32-55 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 == Comment: #1 - Pridhiviraj Paidipeddi - 2017-01-11 07:06:59 == root@p8wookie:~# dmesg |grep -i powernv [0.00] Using PowerNV machine description [0.331564] EEH: PowerNV platform initialized [0.907250] powernv-rng: Registering arch random hook. [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0 [1.507167] powernv_idle_driver registered [ 34.184048] powernv_rng: Registered powernv hwrng. [ 34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree [ 34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, prod_id: 0x, dev_id: 0x00) root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ [ 42.297825315,7] OCC Common Area at 0x3b0 size 1MB [ 42.297854780,7] OCC Common Area at 0x200080 size 1MB [ 42.297884305,7] OCC Common Area at 0x200080
[Touch-packages] [Bug 1769343] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You have a broken third party init script named "noip" installed. You will have to remove it. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- 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/1769343 Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: i dont'know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.4 ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Sat May 5 15:43:53 2018 DpkgHistoryLog: Start-Date: 2018-05-05 15:43:49 Commandline: apt-get install xrdp Requested-By: sv2hrt (1000) Install: vnc4server:i386 (4.1.1+xorg4.3.0-37.3ubuntu2, automatic), xbase-clients:i386 (1:7.7+13ubuntu3, automatic), xrdp:i386 (0.6.1-2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-03 (945 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1769343/+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 1776232] Re: package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'hal
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1776232 Title: package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') Status in avahi package in Ubuntu: New Bug description: The error message popped up, it isn't anything I found through any action of my own. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 9 09:22:08 2018 DuplicateSignature: package:avahi-autoipd:0.6.32~rc+dfsg-1ubuntu2.2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package avahi-autoipd (--configure): package avahi-autoipd is not ready for configuration ErrorMessage: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-02 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1776232/+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 1768941] Re: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime
*** This bug is a duplicate of bug 1768933 *** https://bugs.launchpad.net/bugs/1768933 ** This bug has been marked a duplicate of bug 1768933 package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime -- 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/1768941 Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre- dependency problem - not installing uuid-runtime Status in util-linux package in Ubuntu: New Bug description: Encountered error message about this after upgrading from 14.04.05 to 18 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.4 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu May 3 17:57:04 2018 ErrorMessage: pre-dependency problem - not installing uuid-runtime InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768941/+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 1768943] Re: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime
*** This bug is a duplicate of bug 1768933 *** https://bugs.launchpad.net/bugs/1768933 ** This bug is no longer a duplicate of bug 1768941 package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime ** This bug has been marked a duplicate of bug 1768933 package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime -- 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/1768943 Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre- dependency problem - not installing uuid-runtime Status in util-linux package in Ubuntu: New Bug description: Encountered error message about this after upgrading from 14.04.05 to 16 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.27.1-6ubuntu3.4 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu May 3 17:57:04 2018 ErrorMessage: pre-dependency problem - not installing uuid-runtime InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: util-linux Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768943/+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 1776232] [NEW] package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'h
Public bug reported: The error message popped up, it isn't anything I found through any action of my own. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 9 09:22:08 2018 DuplicateSignature: package:avahi-autoipd:0.6.32~rc+dfsg-1ubuntu2.2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package avahi-autoipd (--configure): package avahi-autoipd is not ready for configuration ErrorMessage: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-02 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1776232 Title: package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') Status in avahi package in Ubuntu: New Bug description: The error message popped up, it isn't anything I found through any action of my own. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Jun 9 09:22:08 2018 DuplicateSignature: package:avahi-autoipd:0.6.32~rc+dfsg-1ubuntu2.2 Processing triggers for libc-bin (2.23-0ubuntu10) ... dpkg: error processing package avahi-autoipd (--configure): package avahi-autoipd is not ready for configuration ErrorMessage: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-02 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-autoipd 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: package avahi-autoipd is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1776232/+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 913323] Re: Occasional login failure and artefacts
Hello, This behavior (need to enter password 2 or 3 times) happened nearly from the beginning. It is a fresh install of a standard xubuntu 16.04 LTS with my old homedir copied from the previous 16.04 machine (that has crashed). Packages are just installed when needed, so that forgotten packages are not borrowed from the old machine. Btw lightdm: 1.18.3-0ubuntu1.1 Today I had to enter my password 3 times. here are some extracts of 3 log files where I have found 2 errors in a short time : /var/log/syslog /var/log/lightdm/lightdm.log /var/log/lightdm/seat0-greeter.log Maybe useful information: When unlocked, I select the session with 7, but once locked, I have to select Ctrl>8; Or 7 displays a black screen with something in french like this: This session is locked you will be redirected to the unlock dialog automatically in a few seconds # Syslog: A connection to the bus can't be made tail -30 /var/log/syslog Jun 11 14:07:14 dlt0001ptrstp lightdm[1248]: ** (lightdm:1248): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call Jun 11 14:07:14 dlt0001ptrstp org.gtk.vfs.Daemon[23411]: A connection to the bus can't be made Jun 11 14:07:15 dlt0001ptrstp systemd[1]: Started Session c32 of user lightdm. Jun 11 14:07:16 dlt0001ptrstp org.a11y.Bus[7986]: ** (process:7997): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Jun 11 14:07:16 dlt0001ptrstp org.a11y.Bus[7986]: Activating service name='org.a11y.atspi.Registry' Jun 11 14:07:16 dlt0001ptrstp org.a11y.Bus[7986]: Successfully activated service 'org.a11y.atspi.Registry' Jun 11 14:07:16 dlt0001ptrstp org.a11y.atspi.Registry[8002]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jun 11 14:07:20 dlt0001ptrstp lightdm[1248]: ** (lightdm:1248): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call Jun 11 14:07:20 dlt0001ptrstp org.gtk.vfs.Daemon[7986]: A connection to the bus can't be made Jun 11 14:07:21 dlt0001ptrstp systemd[1]: Started Session c33 of user lightdm. Jun 11 14:07:21 dlt0001ptrstp org.a11y.Bus[8079]: ** (process:8090): WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files Jun 11 14:07:21 dlt0001ptrstp org.a11y.Bus[8079]: Activating service name='org.a11y.atspi.Registry' Jun 11 14:07:22 dlt0001ptrstp org.a11y.Bus[8079]: Successfully activated service 'org.a11y.atspi.Registry' Jun 11 14:07:22 dlt0001ptrstp org.a11y.atspi.Registry[8095]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jun 11 14:07:27 dlt0001ptrstp org.gtk.vfs.Daemon[8079]: A connection to the bus can't be made # /var/log/lightdm/lightdm.log : Error using VT_WAITACTIVE [+1635057.87s] DEBUG: Continue authentication [+1635057.90s] DEBUG: Session pid=23480: Authentication complete with return value 0: Success [+1635057.90s] DEBUG: Authenticate result for user : Success [+1635057.90s] DEBUG: User authorized [+1635057.90s] DEBUG: Greeter sets language fr_FR [+1635057.98s] DEBUG: Greeter requests session xubuntu [+1635057.98s] DEBUG: Seat seat0: Returning to existing user session [+1635057.98s] DEBUG: Unlocking login1 session c24 [+1635057.98s] DEBUG: Activating VT 7 [+1635057.98s] WARNING: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call [+1635057.98s] DEBUG: Seat seat0: Stopping greeter [+1635057.98s] DEBUG: Session pid=23399: Sending SIGTERM [+1635057.98s] DEBUG: Activating login1 session c24 [+1635057.99s] DEBUG: Session pid=23480: Exited with return value 0 [+1635057.99s] DEBUG: Seat seat0: Session stopped [+1635058.00s] DEBUG: Greeter closed communication channel [+1635058.00s] DEBUG: Session pid=23399: Exited with return value 0 [+1635058.00s] DEBUG: Seat seat0: Session stopped [+1635058.00s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+1635058.00s] DEBUG: Sending signal 15 to process 23391 [+1635058.32s] DEBUG: Process 23391 exited with return value 0 [+1635058.32s] DEBUG: DisplayServer x-1: X server stopped [+1635058.32s] DEBUG: Releasing VT 8 [+1635058.32s] DEBUG: DisplayServer x-1: Removing X server authority /var/run/lightdm/root/:1 [+1635058.32s] DEBUG: Seat seat0: Display server stopped [+1635058.32s] DEBUG: Seat seat0: Active display server stopped, starting greeter [+1635058.32s] DEBUG: Seat seat0: Creating greeter session [+1635058.32s] DEBUG: Seat seat0: Creating display server of type x [+1635058.32s] DEBUG: Using VT 8 [+1635058.32s] DEBUG: Seat seat0: Starting local X display on VT 8 [+1635058.32s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log [+1635058.32s] DEBUG: DisplayServer x-1: Writing X server authority to /var/run/lightdm/root/:1 [+1635058.32s] DEBUG: DisplayServer x-1: Launching X Server [+1635058.32s] DEBUG: Launching process 7966:
[Touch-packages] [Bug 1768933] Re: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime
It looks like you upgraded from trusty to xenial then to bionic. Were there errors during the upgrade to xenial? It does not appear to have completed correctly since you still have the Trusty version of libuuid1 installed. ** Changed in: util-linux (Ubuntu) Status: New => Incomplete -- 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/1768933 Title: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime Status in util-linux package in Ubuntu: Incomplete Bug description: Encountered error message about this after upgrading from 14.04.05 to 18 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: uuid-runtime 2.20.1-5.1ubuntu20.9 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu May 3 17:57:04 2018 ErrorMessage: pre-dependency problem - not installing uuid-runtime InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: util-linux Title: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768933/+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 951317] Re: ufw crashed with UnicodeDecodeError in get_loglevel(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128)
*** This bug is a duplicate of bug 953372 *** https://bugs.launchpad.net/bugs/953372 @fathi733-gmail - this should've been fixed a long time ago. Anything you see now should be a new bug. Can you file one at https://bugs.launchpad.net/ufw/+filebug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/951317 Title: ufw crashed with UnicodeDecodeError in get_loglevel(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) Status in ufw package in Ubuntu: Confirmed Bug description: # ufw version ufw 0.31-0ubuntu1 Copyright 2008-2010 Canonical Ltd. # python --version Python 2.7.3rc1 # ufw status verbose Traceback (most recent call last): File "/usr/sbin/ufw", line 111, in res = ui.do_action(pr.action, "", "", pr.force) File "/usr/lib/python2.7/dist-packages/ufw/frontend.py", line 580, in do_action res = self.get_status(True) File "/usr/lib/python2.7/dist-packages/ufw/frontend.py", line 246, in get_status out = self.backend.get_status(verbose, show_count) File "/usr/lib/python2.7/dist-packages/ufw/backend_iptables.py", line 416, in get_status (level, logging_str) = self.get_loglevel() File "/usr/lib/python2.7/dist-packages/ufw/backend.py", line 542, in get_loglevel rstr += "on (%s)" % (self.defaults['loglevel']) UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: ufw 0.31-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Sat Mar 10 11:47:10 2012 ExecutablePath: /usr/sbin/ufw InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/sbin/ufw status verbose PythonArgs: ['/usr/sbin/ufw', 'status', 'verbose'] SourcePackage: ufw Title: ufw crashed with UnicodeDecodeError in get_loglevel(): 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128) UpgradeStatus: Upgraded to precise on 2012-03-03 (6 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/951317/+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 1776225] [NEW] package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: підпроцес встановлено пакунок lvm2 сценарій post-installation повернув помилковий код завершення 1
Public bug reported: error while running GNS3 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Jun 11 15:40:42 2018 ErrorMessage: підпроцес встановлено пакунок lvm2 сценарій post-installation повернув помилковий код завершення 1 InstallationDate: Installed on 2018-05-06 (35 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: підпроцес встановлено пакунок lvm2 сценарій post-installation повернув помилковий код завершення 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1776225 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: підпроцес встановлено пакунок lvm2 сценарій post-installation повернув помилковий код завершення 1 Status in lvm2 package in Ubuntu: New Bug description: error while running GNS3 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 Date: Mon Jun 11 15:40:42 2018 ErrorMessage: підпроцес встановлено пакунок lvm2 сценарій post-installation повернув помилковий код завершення 1 InstallationDate: Installed on 2018-05-06 (35 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: підпроцес встановлено пакунок lvm2 сценарій post-installation повернув помилковий код завершення 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1776225/+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 1776218] [NEW] New style hook support not robust on removal
Public bug reported:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ] ||
/usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
** 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/1776218
Title:
New style hook support not robust on removal
Status in apt package in Ubuntu:
New
Bug description:
The new style (json-rpc) hooks are great. However when using them in snapd we
noticed the following problem. When shipping a hook in
/etc/apt/apt.conf.d/20snapd.conf like:
```
AptCli::Hooks::Install { "[ ! -f /usr/bin/snap ] || /usr/bin/snap advise-snap
--from-apt || true"; };
```
this works fine.
However when the snapd package is removed apt fails with:
```
...
Purging configuration files for snapd (1337.2.32.8) ...
Final directory cleanup
Discarding preserved snap namespaces
Removing extra snap-confine apparmor rules
Removing snapd cache
Removing snapd state
E: Could not read response to hello message from hook [ ! -f /usr/bin/snap ]
|| /usr/bin/snap advise-snap --from-apt || true: Connection reset by peer
E: Could not read message separator line after handshake from [ ! -f
/usr/bin/snap ] || /usr/bin/snap advise-snap --from-apt || true: Connection
reset by peer
quiet: end of output.
```
I.e. if the hook is not there apt still expectes a handshake.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1776218/+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 1776214] [NEW] please package lxc 2.1.1 for xenial updates
Public bug reported: Please package lxc 2.1.1 for xenial updates as this will fix some bugs, i.e. fixing creation of bionic containers #1760848 ** 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/1776214 Title: please package lxc 2.1.1 for xenial updates Status in lxc package in Ubuntu: New Bug description: Please package lxc 2.1.1 for xenial updates as this will fix some bugs, i.e. fixing creation of bionic containers #1760848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1776214/+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 1776215] [NEW] i lost my menu and title bar
Public bug reported: i can't access my menu and title bar i need your help to restore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 11 13:49:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kabini [Radeon HD 8210] [103c:21f7] InstallationDate: Installed on 2014-11-04 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=661e7b31-e7f7-4fe1-b992-35c89b3ab5a7 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 21F7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd01/03/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn21F7:rvr52.16:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 097610405F1610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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: Mon Jun 11 13:46:50 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages 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/1776215 Title: i lost my menu and title bar Status in xorg package in Ubuntu: New Bug description: i can't access my menu and title bar i need your help to restore it ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 11 13:49:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Kabini [Radeon HD 8210] [103c:21f7] InstallationDate: Installed on 2014-11-04 (1314 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP 15 Notebook PC ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic root=UUID=661e7b31-e7f7-4fe1-b992-35c89b3ab5a7 ro vesafb.invalid=1 plymouth:debug nopat drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 21F7
[Touch-packages] [Bug 1760848] Re: lxc-create can't create bionic container on xenial
This is fixed in lxc 2.1.1 which is available via ppa for 14.04 but has to be pushed to xenial updates. -- 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/1760848 Title: lxc-create can't create bionic container on xenial Status in lxc package in Ubuntu: Confirmed Bug description: I did run: lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic which fails in the end: (...) Download complete Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ... Generating locales (this might take a while)... de_DE.UTF-8... done Generation complete. mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' nicht möglich: Datei oder Verzeichnis nicht gefunden lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for ubu18.04 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04 I've seen that when creating a xenial container this is the point where new sshd keys get created. dpkg -l 'lxc*' ||/ Name Version +++-==-==- ii lxc2.0.8-0ubuntu1~16.04.2 ii lxc-common 2.0.8-0ubuntu1~16.04.2 ii lxc-templates 2.0.8-0ubuntu1~16.04.2 ii lxc1 2.0.8-0ubuntu1~16.04.2 ii lxcfs 2.0.8-0ubuntu1~16.04.2 un lxcguest un lxctl lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760848/+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 1760848] Re: lxc-create can't create bionic container on xenial
Oliver, this bug is exactly about creating a bionic container on an ubuntu 16.04 host. -- 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/1760848 Title: lxc-create can't create bionic container on xenial Status in lxc package in Ubuntu: Confirmed Bug description: I did run: lxc-create -t ubuntu -n ubu18.04 -- template-options -r bionic which fails in the end: (...) Download complete Copy /var/cache/lxc/bionic/rootfs-amd64 to /var/lib/lxc/ubu18.04/rootfs ... Copying rootfs to /var/lib/lxc/ubu18.04/rootfs ... Generating locales (this might take a while)... de_DE.UTF-8... done Generation complete. mv: Aufruf von stat für '/var/lib/lxc/ubu18.04/rootfs/etc/init/ssh.conf' nicht möglich: Datei oder Verzeichnis nicht gefunden lxc-create: lxccontainer.c: create_run_template: 1295 container creation template for ubu18.04 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container ubu18.04 I've seen that when creating a xenial container this is the point where new sshd keys get created. dpkg -l 'lxc*' ||/ Name Version +++-==-==- ii lxc2.0.8-0ubuntu1~16.04.2 ii lxc-common 2.0.8-0ubuntu1~16.04.2 ii lxc-templates 2.0.8-0ubuntu1~16.04.2 ii lxc1 2.0.8-0ubuntu1~16.04.2 ii lxcfs 2.0.8-0ubuntu1~16.04.2 un lxcguest un lxctl lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1760848/+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 1776200] Re: package python3-apport 2.20.9-0ubuntu7 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1776200 Title: package python3-apport 2.20.9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: How to solve this problem? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.9-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashReports: 600:0:117:212493:2018-06-11 16:03:27.512198209 +0530:2018-06-11 16:03:28.512198209 +0530:/var/crash/python3-apport.0.crash Date: Mon Jun 11 16:03:28 2018 DuplicateSignature: package:python3-apport:2.20.9-0ubuntu7 Setting up python2.7 (2.7.15~rc1-1) ... dpkg: error processing package python3-apport (--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 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: apport Title: package python3-apport 2.20.9-0ubuntu7 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/apport/+bug/1776200/+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 1776200] [NEW] package python3-apport 2.20.9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: How to solve this problem? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.9-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashReports: 600:0:117:212493:2018-06-11 16:03:27.512198209 +0530:2018-06-11 16:03:28.512198209 +0530:/var/crash/python3-apport.0.crash Date: Mon Jun 11 16:03:28 2018 DuplicateSignature: package:python3-apport:2.20.9-0ubuntu7 Setting up python2.7 (2.7.15~rc1-1) ... dpkg: error processing package python3-apport (--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 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: apport Title: package python3-apport 2.20.9-0ubuntu7 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: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1776200 Title: package python3-apport 2.20.9-0ubuntu7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apport package in Ubuntu: New Bug description: How to solve this problem? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.9-0ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashReports: 600:0:117:212493:2018-06-11 16:03:27.512198209 +0530:2018-06-11 16:03:28.512198209 +0530:/var/crash/python3-apport.0.crash Date: Mon Jun 11 16:03:28 2018 DuplicateSignature: package:python3-apport:2.20.9-0ubuntu7 Setting up python2.7 (2.7.15~rc1-1) ... dpkg: error processing package python3-apport (--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 2018-06-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: apport Title: package python3-apport 2.20.9-0ubuntu7 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/apport/+bug/1776200/+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 1776173] [NEW] qt print dialog shipped with bionic ignores printer defaults
Public bug reported: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: New Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1769682] Re: NFS-based remote root hangs when running 'netplan apply'
This bug was fixed in the package netplan.io - 0.36.2 --- netplan.io (0.36.2) bionic; urgency=medium * doc/netplan.md: Clarify the behavior for time-based values for bonds and bridges. (LP: #1756587) * critical: provide a way to set "CriticalConnection=true" on a networkd connection, especially for remote-fs scenarios. (LP: #1769682) -- Mathieu Trudel-Lapierre Tue, 08 May 2018 15:33:48 -0400 ** Changed in: netplan.io (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1769682 Title: NFS-based remote root hangs when running 'netplan apply' Status in initramfs-tools package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Invalid Status in initramfs-tools source package in Xenial: Confirmed Status in netplan.io source package in Xenial: Invalid Status in nplan source package in Xenial: Fix Released Status in initramfs-tools source package in Artful: Confirmed Status in netplan.io source package in Artful: Invalid Status in nplan source package in Artful: Fix Released Status in initramfs-tools source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in nplan source package in Bionic: Invalid Bug description: [Impact] Netboot users with a remote filesystem over NFS (possibly over other networked filesystems). [Test cases] 1) Boot a system with its root filesystem over NFS. 2) Run 'sudo netplan apply' 3) Validate that the system remains responsive and keeps connectivity over the same IP address as it had. [Regression potential] This SRU changes network properties, and enforces that networkd does not release and re-request an IP address from DHCP when it is restarted. Environments relying on the IP release/renew behavior may find themselves staying on the previous IP address, which might negatively impact connectivity. Changes in connectivity on a system running netplan should be investigated as a potential regression from this SRU. Other regression possibilities would include failure to get a new IP address over time (usually seen as losing connectivity) or possible IP conflicts on a network. --- With a system booted on the network, with its remote root fs on NFS: Running 'netplan apply' restarts systemd-networkd, which releases the IP received from DHCP. With no IP (and and IP potentially changing), the NFS server can't be reached so the system hangs. 'netplan apply' or restarting systemd-networkd should not affect teh system, it should continue working normally despite "changing" network states, as long as the effective IP remains the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769682/+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 1708409] Re: kdump service does not start after configure/reboot
This bug was fixed in the package makedumpfile - 1:1.6.3-2~17.10.1 --- makedumpfile (1:1.6.3-2~17.10.1) artful; urgency=medium * Backport latest makedumpfile to artful. (LP: #1746299) -- Thadeu Lima de Souza Cascardo Mon, 21 May 2018 10:56:29 -0300 ** Changed in: makedumpfile (Ubuntu Artful) Status: Invalid => Fix Released -- 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/1708409 Title: kdump service does not start after configure/reboot Status in The Ubuntu-power-systems project: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in makedumpfile source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Status in makedumpfile source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - Harish Sriram - 2017-08-02 01:45:01 == kdump service does not start after configure/reboot --Problem Description--- kdump service does not start after configure/reboot. It has to be started/loaded manually, everytime after reboot. # kdump-config status current state : Not ready to kdump ---uname output--- Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type/Model = Power 8/8247-22L Additional Info- # cat /proc/cmdline root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ---Steps to Reproduce--- 1. installed linux-crashdump 2. edited the kdump-tools.cfg crashkernel cmdline to above 3. update-grub 4. reboot Expected: kdump-config to be loaded by default after reboot # kdump-config status current state : Not ready to kdump # service kdump-tools status * kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: inactive (dead) ... https://github.com/systemd/systemd/issues/6334 systemd in artful is not properly picking up the unit files in /etc/systemd/system/default.target.wants To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+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 1774740] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1774740 Title: Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Roughly every other time, hibernating (via systemctl hibernate) fails : it begins then I get back to lightdm prompt. journalctl shows the lines systemd[1]: Starting Hibernate... systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_unattended-upgrades-hibernate as 22334. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/hdparm as 22335. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_grub-common as 22336. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/wpasupplicant as 22337. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/tuxonice as 22338. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/back_to_ram as 22339. systemd-sleep[22333]: /lib/systemd/system-sleep/10_unattended-upgrades-hibernate succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/back_to_ram succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/hdparm succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/tuxonice succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/10_grub-common succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/wpasupplicant succeeded. systemd-sleep[22332]: system-sleep succeeded. systemd-sleep[22332]: Suspending system... kernel: PM: hibernation entry kernel: PM: Syncing filesystems ... kernel: PM: done. kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. kernel: OOM killer disabled. kernel: PM: Marking nosave pages: [mem 0x-0x0fff] kernel: PM: Marking nosave pages: [mem 0x00058000-0x00058fff] kernel: PM: Marking nosave pages: [mem 0x0009e000-0x000f] kernel: PM: Marking nosave pages: [mem 0xabbf4000-0xabbf5fff] kernel: PM: Marking nosave pages: [mem 0xbb835000-0xbc5fefff] kernel: PM: Marking nosave pages: [mem 0xbc60-0x] kernel: PM: Basic memory bitmaps created kernel: PM: Preallocating image memory... kernel: acpi LNXPOWER:16: Turning OFF kernel: acpi LNXPOWER:15: Turning OFF kernel: acpi LNXPOWER:14: Turning OFF kernel: acpi LNXPOWER:13: Turning OFF kernel: acpi LNXPOWER:12: Turning OFF kernel: acpi LNXPOWER:11: Turning OFF kernel: acpi LNXPOWER:10: Turning OFF kernel: acpi LNXPOWER:0f: Turning OFF kernel: acpi LNXPOWER:0e: Turning OFF kernel: acpi LNXPOWER:0d: Turning OFF kernel: acpi LNXPOWER:0c: Turning OFF kernel: acpi LNXPOWER:0b: Turning OFF kernel: acpi LNXPOWER:0a: Turning OFF kernel: acpi LNXPOWER:09: Turning OFF kernel: acpi LNXPOWER:08: Turning OFF kernel: acpi LNXPOWER:07: Turning OFF kernel: acpi LNXPOWER:06: Turning OFF kernel: acpi LNXPOWER:05: Turning OFF kernel: acpi LNXPOWER:04: Turning OFF kernel: acpi LNXPOWER:03: Turning OFF kernel: PM: Basic memory bitmaps freed kernel: OOM killer enabled. kernel: Restarting tasks ... done. kernel: video LNXVIDEO:00: Restoring backlight state kernel: PM: hibernation exit whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory acpid[1079]: client 1225[0:0] has disconnected systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE acpid[1079]: client connected from 1225[0:0] systemd[1]: Failed to start Hibernate. acpid[1079]: 1 client rule loaded systemd[1]: Dependency failed for Hibernate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 2 00:34:35 2018 InstallationDate: Installed on 2016-09-07 (632 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision Tower 3620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro nomodeset SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.1 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1774740] Re: Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory
This is more likely to be a kernel bug. ** Also affects: 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1774740 Title: Cannot hibernate : systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Roughly every other time, hibernating (via systemctl hibernate) fails : it begins then I get back to lightdm prompt. journalctl shows the lines systemd[1]: Starting Hibernate... systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_unattended-upgrades-hibernate as 22334. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/hdparm as 22335. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/10_grub-common as 22336. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/wpasupplicant as 22337. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/tuxonice as 22338. systemd-sleep[22333]: Spawned /lib/systemd/system-sleep/back_to_ram as 22339. systemd-sleep[22333]: /lib/systemd/system-sleep/10_unattended-upgrades-hibernate succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/back_to_ram succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/hdparm succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/tuxonice succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/10_grub-common succeeded. systemd-sleep[22333]: /lib/systemd/system-sleep/wpasupplicant succeeded. systemd-sleep[22332]: system-sleep succeeded. systemd-sleep[22332]: Suspending system... kernel: PM: hibernation entry kernel: PM: Syncing filesystems ... kernel: PM: done. kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. kernel: OOM killer disabled. kernel: PM: Marking nosave pages: [mem 0x-0x0fff] kernel: PM: Marking nosave pages: [mem 0x00058000-0x00058fff] kernel: PM: Marking nosave pages: [mem 0x0009e000-0x000f] kernel: PM: Marking nosave pages: [mem 0xabbf4000-0xabbf5fff] kernel: PM: Marking nosave pages: [mem 0xbb835000-0xbc5fefff] kernel: PM: Marking nosave pages: [mem 0xbc60-0x] kernel: PM: Basic memory bitmaps created kernel: PM: Preallocating image memory... kernel: acpi LNXPOWER:16: Turning OFF kernel: acpi LNXPOWER:15: Turning OFF kernel: acpi LNXPOWER:14: Turning OFF kernel: acpi LNXPOWER:13: Turning OFF kernel: acpi LNXPOWER:12: Turning OFF kernel: acpi LNXPOWER:11: Turning OFF kernel: acpi LNXPOWER:10: Turning OFF kernel: acpi LNXPOWER:0f: Turning OFF kernel: acpi LNXPOWER:0e: Turning OFF kernel: acpi LNXPOWER:0d: Turning OFF kernel: acpi LNXPOWER:0c: Turning OFF kernel: acpi LNXPOWER:0b: Turning OFF kernel: acpi LNXPOWER:0a: Turning OFF kernel: acpi LNXPOWER:09: Turning OFF kernel: acpi LNXPOWER:08: Turning OFF kernel: acpi LNXPOWER:07: Turning OFF kernel: acpi LNXPOWER:06: Turning OFF kernel: acpi LNXPOWER:05: Turning OFF kernel: acpi LNXPOWER:04: Turning OFF kernel: acpi LNXPOWER:03: Turning OFF kernel: PM: Basic memory bitmaps freed kernel: OOM killer enabled. kernel: Restarting tasks ... done. kernel: video LNXVIDEO:00: Restoring backlight state kernel: PM: hibernation exit whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com whoopsie[1377]: [00:31:31] Cannot reach: https://daisy.ubuntu.com systemd-sleep[22332]: Failed to write 'disk' to /sys/power/state: Cannot allocate memory acpid[1079]: client 1225[0:0] has disconnected systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE acpid[1079]: client connected from 1225[0:0] systemd[1]: Failed to start Hibernate. acpid[1079]: 1 client rule loaded systemd[1]: Dependency failed for Hibernate. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 2 00:34:35 2018 InstallationDate: Installed on 2016-09-07 (632 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Precision Tower 3620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=6ebb7e70-29f5-4ddf-a1a1-8cc58113961a ro nomodeset SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.8.1 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Insane amounts in /var/log/syslog Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:usb: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:devices: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3:1.0: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:..: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: message repeated 2 times: [ ureadahead:..: Ignored relative path] Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:devices: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:pci:00: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead::00:1a.0: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:usb1: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3: Ignored relative path Jun 10 19:52:56 think420 ureadahead[273]: ureadahead:1-1.3:1.0: Ignored relative path -- 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/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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
