[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
I'm getting this error on Ubuntu 17.10: W: Download is performed unsandboxed as root as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) I have a user _apt, and it owns /var/lib/update-notifier/package-data- downloads/partial/ It looks like the problems are 2-fold: 1. The double-slash in '/root/.synaptic/tmp//tmp_cl' is equivalent to /tmp_cl, isn't it? That doesn't exist, and probably shouldn't. The double-slash should probably be a single slash. 2. Why is _apt supposed to be able to access anything in /root? If /root/.synaptic/tmp is a special case, then somebody or some program needs to change its ownership. Right now it's: drwx-- 2 root root /root/.synaptic/tmp -- 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/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1735594] Re: ubuntu automatically logs out when hovering sidebar
and could you run 'lspci -vnn | grep VGA' and tell what it says -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: ubuntu automatically logs out when hovering sidebar Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: ubuntu automatically logs out when hovering sidebar
Bug misfiled, would've been useful to know about it a month ago :/ If you are able to build the package from ppa:ubuntu-x-swat/updates then that would be great. PPA builders are offline for days now because of SPECTRE. ** Package changed: compiz (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Also affects: mesa (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: ubuntu automatically logs out when hovering sidebar Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: New Status in mesa source package in Artful: New Bug description: When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Could you test 17.10 live image? It comes with 17.2.2 and should work, then upgrading to artful-proposed should break it again since it has 17.2.4. Looks like Intel gen4 & 5 regressed, everything newer seems to work fine which is why testing didn't catch this. There is a newer upstream version available (17.2.8) but PPA builders are down so I don't have that available for testing. ** Package changed: unity (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go
[Touch-packages] [Bug 1735594] [NEW] ubuntu automatically logs out when hovering sidebar
You have been subscribed to a public bug: When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status ** Affects: mesa (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Confirmed ** Tags: crash logout -- ubuntu automatically logs out when hovering sidebar https://bugs.launchpad.net/bugs/1735594 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1741447] [NEW] Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
You have been subscribed to a public bug: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Jan 5 11:14:24 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: mesa (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Confirmed ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 https://bugs.launchpad.net/bugs/1741447 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 937951] Re: Dir::Cache::archives="" places archives in / instead of turning off caches. See apt.conf(5).
** Summary changed: - An empty Dir::Cache::archives is treated incorrectly and even removes all files in the root folder + Dir::Cache::archives="" places archives in / instead of turning off caches. See apt.conf(5). ** Changed in: apt (Ubuntu) Status: Invalid => Confirmed -- 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/937951 Title: Dir::Cache::archives="" places archives in / instead of turning off caches. See apt.conf(5). Status in APT: Invalid Status in apt package in Ubuntu: Confirmed Bug description: From apt.conf(5): Dir::Cache contains locations pertaining to local cache information, such as the two package caches srcpkgcache and pkgcache as well as the location to place downloaded archives, Dir::Cache::archives. Generation of caches can be turned off by setting their names to be blank Following this documentation, I created /etc/apt/apt.conf.d/30nocache containing the below line to disable the cache: Dir::Cache::archives ""; To my surprise, the directory /partial is created and downloaded .deb files get into / as well as the lock file. Even worse, when apt-get clean is executed, all files under / get removed! # apt-get -s clean Del /* /partial/* Please fix the documentation and/ or prevent /* from being removed. Affected versions: - 0.8.16~exp5ubuntu13 (Ubuntu Oneiric) - 0.8.10.3+squeeze1 (Debian Squeeze) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/937951/+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 1741675] Re: desktop screen
It seems to be the same bug reported here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1741502 -- 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/1741675 Title: desktop screen Status in xorg package in Ubuntu: New Bug description: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741675/+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 1741629] Re: OEM install test case fails at user login
Same problem using 32-bit iso. -- 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/1741629 Title: OEM install test case fails at user login Status in apport package in Ubuntu: New Bug description: Testing Kubuntu 17.10.1 with test cases on http://iso.qa.ubuntu.com/qatracker/milestones/385/builds/164205/testcases/1305/results At step 33 the user login screen didn't show. It just stuck there without any reaction. I tested it on Virtual Box 5.1.30 r118389 (Qt5.6.1), the virtual machine contains 2 CPUs and 2GB ram, 40GB HDD, 16MB display ram. No 2D & 3D acceleration. UEFI turned on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741629/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate
journalctl output after resume: https://paste.ubuntu.com/26337345/ -- 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/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1737264] Re: ALSA output is silent but SDL works fine
This seems to be triggered by connecting an external monitor over DisplayPort, then disconnecting. And rebooting does indeed clear the problem. -- 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/1737264 Title: ALSA output is silent but SDL works fine Status in alsa-driver package in Ubuntu: New Bug description: Gnome error sounds do play, but sound output from Firefox and other applications doesn't work unless they can support a non-ALSA sound driver. E.g. mplayer makes no sound unless the "-ao sdl" or "-ao openal" parameter is added. ALSA and PulseAudio don't work. Reloading the ALSA kernel modules doesn't fix the problem. # alsa force-reload /sbin/alsa: Warning: Processes using sound devices: 1808(pulseaudio). Unloading ALSA sound driver modules: snd-hda-codec-hdmi snd-soc-rt5640 snd-soc-rl6231 snd-soc-core snd-hda-codec-conexant snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-compress snd-pcm-dmaengine snd-hda-core snd-hwdep snd-seq-midi snd-seq-midi-event snd-pcm snd-rawmidi snd-seq snd-seq-device snd-timer snd-soc-sst-acpi snd-soc-sst-match (failed: modules still loaded: snd-hda-codec-hdmi snd-hda-codec-conexant snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer). Loading ALSA sound driver modules: snd-hda-codec-hdmi snd-soc-rt5640 snd-soc-rl6231 snd-soc-core snd-hda-codec-conexant snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-compress snd-pcm-dmaengine snd-hda-core snd-hwdep snd-seq-midi snd-seq-midi-event snd-pcm snd-rawmidi snd-seq snd-seq-device snd-timer snd-soc-sst-acpi snd-soc-sst-match. Unloading the kernel modules manually also fails. # rmmod snd-hda-codec-hdmi snd-hda-codec-conexant snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep snd-pcm snd-timer rmmod: ERROR: Module snd_hda_codec_hdmi is in use rmmod: ERROR: Module snd_hda_codec_conexant is in use rmmod: ERROR: Module snd_hda_codec_generic is in use by: snd_hda_codec_conexant rmmod: ERROR: Module snd_hda_intel is in use rmmod: ERROR: Module snd_hda_codec is in use by: snd_hda_intel snd_hda_codec_conexant snd_hda_codec_hdmi snd_hda_codec_generic rmmod: ERROR: Module snd_hda_core is in use by: snd_hda_intel snd_hda_codec_conexant snd_hda_codec snd_hda_codec_hdmi snd_hda_codec_generic rmmod: ERROR: Module snd_hwdep is in use by: snd_hda_codec rmmod: ERROR: Module snd_pcm is in use by: snd_hda_intel snd_hda_codec snd_pcm_dmaengine snd_hda_core snd_soc_rt5640 snd_hda_codec_hdmi snd_soc_core rmmod: ERROR: Module snd_timer is in use by: snd_seq snd_pcm No HDMI device is currently connected, but one was a few days ago. There have been several suspend-resume cycles since then. I expect that rebooting will clear this issue, however obviously that shouldn't be needed with Linux. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmj1808 F pulseaudio /dev/snd/pcmC1D0c: pmj1808 F...m pulseaudio /dev/snd/controlC1: pmj1808 F pulseaudio CurrentDesktop: GNOME Date: Sat Dec 9 10:03:15 2017 InstallationDate: Installed on 2016-12-02 (370 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [UX303LAB, Conexant CX20751/2, Black Headphone Out, Right] Playback problem UpgradeStatus: Upgraded to artful on 2017-10-12 (57 days ago) dmi.bios.date: 08/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LAB.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LAB.210:bd08/25/2015:svnASUSTeKCOMPUTERINC.:pnUX303LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX303LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737264/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1741698] Re: DNS break after Artful/17.10 upgrade
The following does not help per https://askubuntu.com/questions/966870 /dns-not-working-after-upgrade-17-04-to-17-10 $ sudo rm /etc/resolv.conf $ sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf $ sudo systemctl restart resolvconf -- 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/1741698 Title: DNS break after Artful/17.10 upgrade Status in systemd package in Ubuntu: New Bug description: I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using upgrade-manager. Priot to upgrade everything worked fine using DHCP. After reboot name resolution broke. I understand Systemd is now the resolver. A lot of people are suffering https://askubuntu.com/questions/966870 /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of Network Manager problems and Systemd problems. This looks like a similar report, but comment 20 says to file a new bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 . Something is missing in the upgrade scripts. I don't know what, but it would be nice if it was fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741698/+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 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
Ping... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in resolvconf package in Ubuntu: Confirmed Bug description: After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS lookup on my wireless network connection did not work any more. As it seems, the file /etc/resolv.conf was static and contained wrong data assigned by the NetworkManager. When I changed the file content manually to nameserver 127.0.0.53 DNS lookup worked fine. After reboot, however, I had to repeat this operation since NetworkManager seems to have replaced the file content. Finally, I found a solution. Running sudo dpkg-reconfigure resolvconf the file /etc/resolv.conf was replaced by the link /etc/resolv.conf -> ../run/resolvconf/resolv.conf Now, the wireless network seems to work properly. Hence, there must be some kind of bug during the update process from Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly. Best regards, Artur ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 23:17:38 2017 InstallationDate: Installed on 2013-10-18 (1463 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+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 1741416] Re: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1741416 Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: Confirmed Bug description: I noticed after a reboot that this was an issue for some reason after the system tried to upgrade apport: Start-Date: 2018-01-05 07:44:52 Commandline: /usr/bin/unattended-upgrade Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2018-01-05 07:45:10 I fixed it with: apt-get dist-upgrade -f ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 Uname: Linux 4.14.8-041408-generic x86_64 ApportLog: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashReports: 600:0:116:145106:2018-01-05 07:45:09.131217479 +:2018-01-05 07:45:10.131217479 +:/var/crash/apport.0.crash Date: Fri Jan 5 07:45:10 2018 DuplicateSignature: package:apport:2.20.1-0ubuntu2.15 Setting up apport (2.20.1-0ubuntu2.15) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-05-29 (220 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741416/+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 1741698] Re: DNS break after Artful/17.10 upgrade
Running 'dpkg-reconfigure resolvconf' per comment 9 at https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 did not help. -- 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/1741698 Title: DNS break after Artful/17.10 upgrade Status in systemd package in Ubuntu: New Bug description: I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using upgrade-manager. Priot to upgrade everything worked fine using DHCP. After reboot name resolution broke. I understand Systemd is now the resolver. A lot of people are suffering https://askubuntu.com/questions/966870 /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of Network Manager problems and Systemd problems. This looks like a similar report, but comment 20 says to file a new bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 . Something is missing in the upgrade scripts. I don't know what, but it would be nice if it was fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741698/+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 1741697] Re: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
*** This bug is a duplicate of bug 1741416 *** https://bugs.launchpad.net/bugs/1741416 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1741416, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1741416 package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 -- 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/1741697 Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: There was this issue when upgrading or installing package ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jan 5 08:26:11 2018 DpkgHistoryLog: Start-Date: 2018-01-05 08:25:48 Commandline: /usr/bin/unattended-upgrade Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), gir1.2-webkit2-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1) DuplicateSignature: package:apport:2.20.1-0ubuntu2.15 Setting up apport (2.20.1-0ubuntu2.15) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-05-04 (247 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741697/+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 1741698] [NEW] DNS break after Artful/17.10 upgrade
Public bug reported: I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using upgrade-manager. Priot to upgrade everything worked fine using DHCP. After reboot name resolution broke. I understand Systemd is now the resolver. A lot of people are suffering https://askubuntu.com/questions/966870 /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of Network Manager problems and Systemd problems. This looks like a similar report, but comment 20 says to file a new bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 . Something is missing in the upgrade scripts. I don't know what, but it would be nice if it was fixed. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1741698 Title: DNS break after Artful/17.10 upgrade Status in systemd package in Ubuntu: New Bug description: I was running Zesty/17.04. I upgraded to Artful/17.10 over SSH using upgrade-manager. Priot to upgrade everything worked fine using DHCP. After reboot name resolution broke. I understand Systemd is now the resolver. A lot of people are suffering https://askubuntu.com/questions/966870 /dns-not-working-after-upgrade-17-04-to-17-10 . It looks like a mix of Network Manager problems and Systemd problems. This looks like a similar report, but comment 20 says to file a new bug. https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840 . Something is missing in the upgrade scripts. I don't know what, but it would be nice if it was fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741698/+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 1741697] [NEW] package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
*** This bug is a duplicate of bug 1741416 *** https://bugs.launchpad.net/bugs/1741416 Public bug reported: There was this issue when upgrading or installing package ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jan 5 08:26:11 2018 DpkgHistoryLog: Start-Date: 2018-01-05 08:25:48 Commandline: /usr/bin/unattended-upgrade Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), gir1.2-webkit2-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1) DuplicateSignature: package:apport:2.20.1-0ubuntu2.15 Setting up apport (2.20.1-0ubuntu2.15) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-05-04 (247 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1741697 Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: There was this issue when upgrading or installing package ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Jan 5 08:26:11 2018 DpkgHistoryLog: Start-Date: 2018-01-05 08:25:48 Commandline: /usr/bin/unattended-upgrade Upgrade: apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), python3-apport:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), apport-gtk:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), gir1.2-webkit2-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), python3-problem-report:amd64 (2.20.1-0ubuntu2.14, 2.20.1-0ubuntu2.15), libwebkit2gtk-4.0-37-gtk2:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.18.3-0ubuntu0.16.04.1, 2.18.4-0ubuntu0.16.04.1) DuplicateSignature: package:apport:2.20.1-0ubuntu2.15 Setting up apport (2.20.1-0ubuntu2.15) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-05-04 (247 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741697/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
I set up an Ubuntu 18.04 test server today as an LXD host machine and ran into this issue. network: version: 2 renderer: networkd ethernets: ens33: dhcp4: no dhcp6: no bridges: br0: interfaces: [ens33] dhcp4: no dhcp6: no addresses: [192.168.1.101/24] gateway4: 192.168.1.1 nameservers: addresses: [192.168.1.1, 8.8.8.8, 8.8.4.4] root@bionic:/home/bionic# systemd-resolve --status Global DNS Servers: 192.168.1.1 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 6 (tun0) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 5 (veth0OI7SQ) Current Scopes: LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (br0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.1.1 8.8.8.8 8.8.4.4 Link 2 (ens33) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no root@bionic:/home/bionic# ping google.com ping: google.com: Temporary failure in name resolution Also the error message is misleading, there's nothing "temporary" about this failure. It's permanent. I can reach IP addresses directly but all DNS lookups are failing, preventing me from doing upgrades and normal operations. -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1741694] [NEW] package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir b
Public bug reported: Im just trying to install 0 AD game. :( ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Jan 6 21:42:52 2018 DpkgTerminalLog: dpkg: erro ao processar o pacote coreutils (--configure): o pacote coreutils não está pronto para configuração não pode configurar (status actual `half-installed') ErrorMessage: o pacote coreutils não está pronto para configuração não pode configurar (status actual `half-installed') InstallationDate: Installed on 2017-01-20 (351 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (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 coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1741694 Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/bin/basename usr/bin/dircolors usr/bin/hostid usr/bin/md5sum usr/bin/shuf usr/bin/stat usr/bin/stdbuf usr/bin/unlink usr/lib/x86_64-linux-gnu/coreutils/libstdbuf.so usr/sbin/chroot usr/share/doc/coreutils/changelog.Debian.gz usr/share/man/man1/arch.1.gz usr/share/man/man1/base32.1.gz usr/share/man/man1/base64.1.gz usr/share/man/man1/basename.1.gz usr/share/man/man1/cat.1.gz usr/share/man/man1/chcon.1.gz usr/share/man/man1/chgrp.1.gz usr/share/man/man1/chmod.1.gz usr/share/man/man1/chown.1.gz usr/share/man/man1/cksum.1.gz usr/share/man/man1/comm.1.gz usr/share/man/man1/cp.1.gz usr/share/man/man1/csplit.1.gz usr/share/man/man1/cut.1.gz usr/share/man/man1/date.1.gz usr/share/man/man1/dd.1.gz usr/share/man/man1/df.1.gz usr/share/man/man1/dir.1.gz usr/share/man/man1/dircolors.1.gz usr/share/man/man1/dirname.1.gz usr/share/man/man1/du.1.gz usr/share/man/man1/echo.1.gz usr/share/man/man1/env.1.gz usr/share/man/man1/expand.1.gz usr/share/man/man1/expr.1.gz usr/share/man/man1/factor.1.gz usr/share/man/man1/false.1.gz usr/share/man/man1/fmt.1.gz usr/share/man/man1/fold.1.gz usr/share/man/man1/groups.1.gz usr/share/man/man1/head.1.gz usr/share/man/man1/hostid.1.gz usr/share/man/man1/id.1.gz usr/share/man/man1/install.1.gz usr/share/man/man1/join.1.gz usr/share/man/man1/link.1.gz usr/share/man/man1/ln.1.gz usr/share/man/man1/logname.1.gz usr/share/man/man1/ls.1.gz usr/share/man/man1/md5sum.1.gz usr/share/man/man1/mkdir.1.gz usr/share/man/man1/mkfifo.1.gz usr/share/man/man1/mknod.1.gz usr/share/man/man1/mktemp.1.gz usr/share/man/man1/mv.1.gz usr/share/man/man1/nice.1.gz usr/share/man/man1/nl.1.gz usr/share/man/man1/nohup.1.gz usr/share/man/man1/nproc.1.gz usr/share/man/man1/numfmt.1.gz usr/share/man/man1/od.1.gz usr/share/man/man1/paste.1.gz usr/share/man/man1/pathchk.1.gz usr/share/man/man1/pinky.1.gz usr/share/man/man1/pr.1.gz usr/share/man/man1/printenv.1.gz usr/share/man/man1/printf.1.gz usr/share/man/man1/ptx.1.gz usr/share/man/man1/pwd.1.gz usr/share/man/man1/readlink.1.gz usr/share/man/man1/realpath.1.gz usr/share/man/man1/rm.1.gz usr/share/man/man1/rmdir.1.gz usr/share/man/man1/runcon.1.gz usr/share/man/man1/seq.1.gz usr/share/man/man1/sha1sum.1.gz usr/share/man/man1/sha224sum.1.gz usr/share/man/man1/sha256sum.1.gz usr/share/man/man1/sha384sum.1.gz usr/share/man/man1/sha512sum.1.gz usr/share/man/man1/shred.1.gz usr/share/man/man1/shuf.1.gz usr/share/man/man1/sleep.1.gz usr/share/man/man1/sort.1.gz usr/share/man/man1/split.1.gz usr/share/man/man1/stat.1.gz usr/share/man/man1/stdbuf.1.gz usr/share/man/man1/stty.1.gz usr/share/man/man1/sum.1.gz usr/share/man/man1/sync.1.gz usr/share/man/man1/tac.1.gz usr/share/man/man1/tail.1.gz usr/share/man/man1/tee.1.gz usr/share/man/man1/test.1.gz usr/share/man/man1/timeout.1.gz usr/share/man/man1/touch.1.gz usr/share/man/man1/tr.1.gz usr/share/man/man1/true.1.gz usr/share/man/man1/truncate.1.gz usr/share/man/man1/tsort.1.gz usr/share/man/man1/tty.1.gz usr/share/man/man1/uname.1.gz usr/share/man/man1/unexpand.1.gz usr/share/man/man1/uniq.1.gz usr/share/man/man1/unlink.1.gz usr/share/man/man1/users.1.gz usr/share/man/man1/vdir.1.gz usr/share/man/man1/wc.1.gz usr/share/man/man1/who.1.gz usr/share/man/man1/whoami.1.gz usr/share/man/man1/yes.1.gz usr/share/man/man8/chroot.8.gz] failed to install/upgrade: o pacote coreutils não está
[Touch-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices
Is there a chance that we will see this backported to xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1718554 Title: Need updated libimobiledevice to mount IOS 11 devices Status in libimobiledevice package in Ubuntu: Fix Released Bug description: After upgrading to IOS 11, I stopped being able to mount my ipad in ubuntu. The relevant log lines from gvfs-afc are: gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc) gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount) gvfsd[1855]: afc: Lockdown client try #0 gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client' gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown error (-3)) The fix is here in the upstream github: https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1718554/+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 1737835] Re: libunity fails to build, test failure
Mh, this builds pretty fine here... Might be due to not-properly initialized session bus in headless mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1737835 Title: libunity fails to build, test failure Status in libunity package in Ubuntu: New Bug description: libunity fails to build from source in current bionic. Full build log at https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861 Build log excerpt = TEST: test-vala... (pid=18081) /Unit/ResultsSynchronizer: OK /Unit/IO/AsyncDesktopFile: OK /Unit/IO/AsyncOpenFromDataDirs: OK /Unit/Utils/AsyncOnce: OK /Unit/Utils/AsyncMutex: OK /Unit/AppInfoManager/Allocation: OK /Unit/AppInfoManager/ClearEmpty: OK /Unit/AppInfoManager/SyncLookupMissing: OK /Unit/AppInfoManager/AsyncLookupMissing: OK /Unit/AppInfoManager/SyncLookupOk: OK /Unit/AppInfoManager/AsyncLookupOk: OK /Unit/Launcher/EmptyEntry: (test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1737835/+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 1741675] [NEW] desktop screen
Public bug reported: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1741675 Title: desktop screen Status in xorg package in Ubuntu: New Bug description: when i go to launcher the screen keeps resetting ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 6 18:33:24 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:022f] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:022f] LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Inspiron 1525 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0CP549 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0CP549:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2
[Touch-packages] [Bug 1644541] Re: Update stuck at “configuring unattended-upgrades”
I was trying to fix the files/nautilus NOT working then went down a rabbit hole until I came here. Files/nautilus is still not working and I'm having same problem of unattended upgrades. I've attached the term.log as well. here's the error from terminal @dgd-System-Product-Name:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 36.1 MB/36.1 MB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-image-extra-4.4.0-101-generic amd64 4.4.0-101.124 [36.1 MB] Fetched 36.1 MB in 5s (6,138 kB/s) Preconfiguring packages ... (Reading database ... 412842 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_0.90ubuntu0.9_all.deb ... Unpacking unattended-upgrades (0.90ubuntu0.9) over (0.90ubuntu0.8) ... Processing triggers for systemd (229-4ubuntu21) ... Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package linux-image-extra-4.4.0-101-generic (--configure): package linux-image-extra-4.4.0-101-generic is not ready for configuration cannot configure (current status 'half-installed') Setting up unattended-upgrades (0.90ubuntu0.9) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ** Attachment added: "term log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1644541/+attachment/5032014/+files/term.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1644541 Title: Update stuck at “configuring unattended-upgrades” Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: On basically fresh install from ubuntu-16.04.1-desktop-amd64.iso; no updates or installs had been applied since installing the OS from the media. During execution of "Software Updater", it freezes indefinitely while "Installing updates..." at the step marked "Configuring unattended- upgrades." It appears that this happens if System Settings->Software & Updates->Updates, "Automatically check for updates" has been set to "Never." If that is instead set to "Daily" and the following are then set in /etc/apt/apt.conf.d/10periodic then the update succeeds: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "7"; APT::Periodic::Unattended-Upgrade "1"; Someone else had asked about this issue at AskUbuntu. Their question along with my answer (from Kevin) provide some further details: http://askubuntu.com/questions/851371/update-stuck-at-configuring- unattended-upgrades-software-updater-turned-black/852110#852110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1644541/+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 1741672] [NEW] Cannot build 235-3ubuntu3 due to missing ... libsystemd-shared-235.so
Public bug reported: Ubuntu 17.10 systemd 234-2ubuntu12.1 Building 235-3ubuntu3 from sources with: dpkg-buildpackage --no-sign --build=binary leads to: ... dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-remote (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-upload (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-gatewayd (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') ... dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-machined (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/bin/machinectl (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-export (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/usr/bin/systemd-nspawn (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-importd (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-import (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-pull (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') It's the first time I meet such a catch 22 issue when building a package. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1741672 Title: Cannot build 235-3ubuntu3 due to missing ... libsystemd-shared-235.so Status in systemd package in Ubuntu: New Bug description: Ubuntu 17.10 systemd 234-2ubuntu12.1 Building 235-3ubuntu3 from sources with: dpkg-buildpackage --no-sign --build=binary leads to: ... dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-remote (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-upload (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-journal-remote/lib/systemd/systemd-journal-gatewayd (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') ... dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-machined (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/bin/machinectl (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-export (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/usr/bin/systemd-nspawn (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-importd (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-import (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/lib/systemd') dpkg-shlibdeps: error: cannot find library libsystemd-shared-235.so needed by debian/systemd-container/lib/systemd/systemd-pull (ELF format: 'elf64-x86-64' abi:
[Touch-packages] [Bug 1741673] [NEW] package apparmor 2.10.95-0ubuntu2.7 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren al
Public bug reported: this just appears after boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Jan 6 19:09:45 2018 ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. InstallationDate: Installed on 2018-01-06 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=078c3b1f-8051-46e0-b2bd-28f8338f4dcf ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apparmor Syslog: Jan 6 18:38:06 wendie-X705UAR dbus[790]: [system] AppArmor D-Bus mediation is enabled Jan 6 18:56:11 wendie-X705UAR dbus[777]: [system] AppArmor D-Bus mediation is enabled Jan 6 19:17:47 wendie-X705UAR dbus[771]: [system] AppArmor D-Bus mediation is enabled Title: package apparmor 2.10.95-0ubuntu2.7 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1741673 Title: package apparmor 2.10.95-0ubuntu2.7 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. Status in apparmor package in Ubuntu: New Bug description: this just appears after boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2.7 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Sat Jan 6 19:09:45 2018 ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. InstallationDate: Installed on 2018-01-06 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=078c3b1f-8051-46e0-b2bd-28f8338f4dcf ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apparmor Syslog: Jan 6 18:38:06 wendie-X705UAR dbus[790]: [system] AppArmor D-Bus mediation is enabled Jan 6 18:56:11 wendie-X705UAR dbus[777]: [system] AppArmor D-Bus mediation is enabled Jan 6 19:17:47 wendie-X705UAR dbus[771]: [system] AppArmor D-Bus mediation is enabled Title: package apparmor 2.10.95-0ubuntu2.7 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1741673/+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 1704681] Re: package python3-apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1704681 Title: package python3-apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade Status in apparmor package in Ubuntu: Confirmed Bug description: An error message occurs when trying to update package via command line : `sudo apt-get update && sudo apt-get upgrade`. I've got below error message : "" package python3-apparmor 2.10.95-0ubuntu2.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration. "" ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apparmor 2.10.95-0ubuntu2.6 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 Date: Wed Jul 12 22:33:38 2017 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-10 (798 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) KernLog: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic.efi.signed root=UUID=ba670a30-9821-4238-9e27-25887fc23447 ro usbhid.quirks=0x1B1C:0x1B19:0x2000 quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: apparmor Syslog: Title: package python3-apparmor 2.10.95-0ubuntu2.6 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/apparmor/+bug/1704681/+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 1733557] Re: Login screen showing Authentication Failed Switch to greeter...
Same on 16.04.3 after updating Unity to latest proposed packages. Also on 17.10 with installed unity-session. For me, this issue appears after switching to another user. Steps to reproduce (must be more than one local users on system, eg. "bob", "alice"): 1. Login under bob. 2. Via upper-right menu switch to "alice". 3. On greeter screen setect "alice", login under alice. 4. Logout, return to greeter screen. 5. Select bob (already logged in). Enter password. 6. Lock screen. Issue appeared. Issue appeared on every screen lock. Messages in syslog: Jan 6 17:15:33 eugene-Lenovo-Flex-2-14 systemd[1411]: Stopped Backing Service for the Unity Panel in Lockscreen mode. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 1 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 2 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Starting Backing Service for the Unity Panel in Lockscreen mode... Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on object path: "/com/ubuntu/Upstart" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Test.Upstart was not provided by any .service files Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd-prestart-check[3804]: grep: /usr/share/gnome-session/sessions/ubuntu.session: Нет такого файла или каталога Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Started Backing Service for the Unity Panel in Lockscreen mode. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Reached target A target that, when running, represents the screen being locked. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 3 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 4 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 5 time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failed Switch to greeter... Status in lightdm package in Ubuntu: Confirmed Bug description: When I lock my machine, the login screen shows my current user with the message: "Authentication Failed" ..and in the position when the password normally exists, the option "Switch to greeter..." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 21 10:28:47 2017 InstallationDate: Installed on 2017-04-17 (217 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/+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 1741658] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1741658
Title:
package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
Status in gconf package in Ubuntu:
New
Bug description:
System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not
installed:
I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others.
Translated:
Failed to install during the systemupgrade:
==
gconf2 (+ "gconf2 will possibly not work")
gnupg-agent
gnupg2
libgdata22
gvfs-backends
adwaita-icon-theme-full
libgail-3-0
gstreamer1.0-plugins-bad
gstreamer0.10-plugins-good
gstreamer1.10-plugins-good
libgssdp-1.0-3
libupnp-1.0-4
libupnp-igd-1.0-4
libnice10
gstreamer1.0-nice
libfarstream-0.2-5
libpurple0
gnome-keyring
libgpgme11
libgmime-2.6-0
libwebkitgtk-3.0-0
geary
gnome-icon-theme
===
Hope the list is complete :-))
Since then only logging-out is possible, but the menu items: "Close the
system" ("Afsluiten" in Dutch) nor "Restart" gave any effect. Caption of this
menu is:
Lubuntu
Session Zorin-OS-lite 16.04
Best regards!
Dirk De Backer
mailto:debacker.d...@worldonline.be
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Jan 6 15:32:06 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-12-19 (748 days ago)
InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.3
apt 1.2.24
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1741658/+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 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
i suppose that such comment could be silenced instead of confusing users
(via lintian ?)
--
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/1658273
Title:
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-
dc.service is masked.
Status in samba package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
On a standalone desktop running zesty with a gnome-shell session, when
upgrading the samba packages, i get:
Setting up samba (2:4.4.5+dfsg-2ubuntu7) ...
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is
masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on
samba-ad-dc.service: No such file or directory
note: ubuntu-bug ask questions about a possible windows relationship,
but there is no option for a standalone system like that one; so as
samba is installed to satisfy qemu, these questions completly ignore
such case and send inappropriate report.
and smbd still crashing on cold boot ( lp:1658293 ) (standalone
desktop)
note2: a more recent Debian version seems workaround that output:
samba (2:4.4.5+dfsg-3)
[ Mathieu Parent ]
* Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge.
Closes: #832352
and samba (2:4.4.6+dfsg-1)
Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not
ctdb.service) Closes: #838000.
and samba (2:4.4.6+dfsg-2)
* Remove uses of tevent internals. This fixes segfault.
Closes: #840382, #840298.
http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog
... time to get package synced
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+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 1741658] [NEW] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported:
System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not
installed:
I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others.
Translated:
Failed to install during the systemupgrade:
==
gconf2 (+ "gconf2 will possibly not work")
gnupg-agent
gnupg2
libgdata22
gvfs-backends
adwaita-icon-theme-full
libgail-3-0
gstreamer1.0-plugins-bad
gstreamer0.10-plugins-good
gstreamer1.10-plugins-good
libgssdp-1.0-3
libupnp-1.0-4
libupnp-igd-1.0-4
libnice10
gstreamer1.0-nice
libfarstream-0.2-5
libpurple0
gnome-keyring
libgpgme11
libgmime-2.6-0
libwebkitgtk-3.0-0
geary
gnome-icon-theme
===
Hope the list is complete :-))
Since then only logging-out is possible, but the menu items: "Close the system"
("Afsluiten" in Dutch) nor "Restart" gave any effect. Caption of this menu is:
Lubuntu
Session Zorin-OS-lite 16.04
Best regards!
Dirk De Backer
mailto:debacker.d...@worldonline.be
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Jan 6 15:32:06 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-12-19 (748 days ago)
InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.3
apt 1.2.24
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)
** Affects: gconf (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-package i386 xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1741658
Title:
package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
Status in gconf package in Ubuntu:
New
Bug description:
System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not
installed:
I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others.
Translated:
Failed to install during the systemupgrade:
==
gconf2 (+ "gconf2 will possibly not work")
gnupg-agent
gnupg2
libgdata22
gvfs-backends
adwaita-icon-theme-full
libgail-3-0
gstreamer1.0-plugins-bad
gstreamer0.10-plugins-good
gstreamer1.10-plugins-good
libgssdp-1.0-3
libupnp-1.0-4
libupnp-igd-1.0-4
libnice10
gstreamer1.0-nice
libfarstream-0.2-5
libpurple0
gnome-keyring
libgpgme11
libgmime-2.6-0
libwebkitgtk-3.0-0
geary
gnome-icon-theme
===
Hope the list is complete :-))
Since then only logging-out is possible, but the menu items: "Close the
system" ("Afsluiten" in Dutch) nor "Restart" gave any effect. Caption of this
menu is:
Lubuntu
Session Zorin-OS-lite 16.04
Best regards!
Dirk De Backer
mailto:debacker.d...@worldonline.be
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Jan 6 15:32:06 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-12-19 (748 days ago)
InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.3
apt 1.2.24
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1741658/+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 1741656] [NEW] occured when i wanted to install the updates
Public bug reported: occured when i wanted to install the updates. i can't upgrade ubuntu from 17.04 to 17.10 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1741656 Title: occured when i wanted to install the updates Status in initramfs-tools package in Ubuntu: New Bug description: occured when i wanted to install the updates. i can't upgrade ubuntu from 17.04 to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1741656/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
@gunnarhj Ok, thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: In Progress Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
On 2018-01-06 15:54, ITEAS wrote: > Ok... so what is to do now that this text will be changed in german > versions ubuntu 16.04 and up comming versions? The change will affect 18.04 primarily. If another translation update of 16.04 is accomplished, the change will be seen there as well. 17.04 and 17.10 will probably not be changed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: In Progress Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
@gunnarhj: Thanks for correcting, I just hit the wrong row with not being a programmer. Ooops. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: In Progress Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
Ok... so what is to do now that this text will be changed in german versions ubuntu 16.04 and up comming versions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: In Progress Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
@schuko24: Please note that you didn't change the unattended-upgrades package; you changed the Launchpad translation for the package. ** Changed in: ubuntu-translations Status: New => In Progress ** Changed in: ubuntu-translations Assignee: Ubuntu German Translators (ubuntu-l10n-de) => schuko24 (gerd-saenger) ** Changed in: unattended-upgrades (Ubuntu) Status: Fix Committed => New ** Changed in: unattended-upgrades (Ubuntu) Assignee: schuko24 (gerd-saenger) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: In Progress Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
@schuko24 (gerd-saenger) i think more better to understand: »Automatische Systemupdates werden während des Herunterfahrens installiert. Der Vorgang kann einige Zeit dauern. Gerät bitte nicht ausschalten.« Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: New Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
Hello, and thanks for the fast reply :) @Hans Joachim Desserud (hjd) Thanks for the information. Never used Apport before. But looks likes easy too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: New Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
Translation changed to: »Unattended-Upgrade läuft während des Herunterfahrens weiter, es beginnt in fünf Sekunden, Gerät bitte nicht ausschalten.« ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: New Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => schuko24 (gerd-saenger) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: New Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741629] Re: OEM install test case fails at user login
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1741629 ** Tags added: iso-testing -- 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/1741629 Title: OEM install test case fails at user login Status in apport package in Ubuntu: New Bug description: Testing Kubuntu 17.10.1 with test cases on http://iso.qa.ubuntu.com/qatracker/milestones/385/builds/164205/testcases/1305/results At step 33 the user login screen didn't show. It just stuck there without any reaction. I tested it on Virtual Box 5.1.30 r118389 (Qt5.6.1), the virtual machine contains 2 CPUs and 2GB ram, 40GB HDD, 16MB display ram. No 2D & 3D acceleration. UEFI turned on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741629/+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 1712039] Re: AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1712039 Title: AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache Status in apparmor package in Ubuntu: Confirmed Bug description: The evince AppArmor profile seems to miss an entry for /var/lib/snapd/desktop/applications/mimeinfo.cache. If evince is launched, the following gets logged to syslog: kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268 comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 I don't know if this should be allowed or denied. If you could add the correct behaviour to the profile, that would be nice; otherwise, every time evince is launched, a notification pops up (apparmor-notify installed). (Workaround: Add to original profile (/etc/apparmor.d/usr.bin.evince): #include Insert into local profile (/etc/apparmor.d/local/usr.bin.evince): /var/lib/snapd/desktop/applications/mimeinfo.cache r, ) Release: Ubuntu 16.04.3 LTS Package Version: evince-common 3.18.2-1ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1712039/+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 1727390] Re: New bugfix release 17.2.4
mesa 17.2.4-0ubuntu1~16.04.1 in xenial lots of issues with unity and compiz. See this bugs: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1741447 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1735594 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1741629] [NEW] OEM install test case fails at user login
Public bug reported: Testing Kubuntu 17.10.1 with test cases on http://iso.qa.ubuntu.com/qatracker/milestones/385/builds/164205/testcases/1305/results At step 33 the user login screen didn't show. It just stuck there without any reaction. I tested it on Virtual Box 5.1.30 r118389 (Qt5.6.1), the virtual machine contains 2 CPUs and 2GB ram, 40GB HDD, 16MB display ram. No 2D & 3D acceleration. UEFI turned on. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1741629 Title: OEM install test case fails at user login Status in apport package in Ubuntu: New Bug description: Testing Kubuntu 17.10.1 with test cases on http://iso.qa.ubuntu.com/qatracker/milestones/385/builds/164205/testcases/1305/results At step 33 the user login screen didn't show. It just stuck there without any reaction. I tested it on Virtual Box 5.1.30 r118389 (Qt5.6.1), the virtual machine contains 2 CPUs and 2GB ram, 40GB HDD, 16MB display ram. No 2D & 3D acceleration. UEFI turned on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1741629/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
** Changed in: ubuntu-translations Assignee: (unassigned) => Ubuntu German Translators (ubuntu-l10n-de) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: New Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741579] Re: Wrong/confuse text on shutdown at unattended-upgrades
Thanks for taking your time to report this issue and help making Ubuntu better. I found the original message, "Unattended-upgrade in progress during shutdown, sleeping for 5s" (https://translations.launchpad.net/ubuntu/artful/+source/unattended- upgrades/+pots/unattended-upgrades/de/52/+translate). Though I am not sure if the issue is with the translation or the original text. When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Also affects: ubuntu-translations Importance: Undecided Status: New ** Tags removed: update upgrade ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1741579 Title: Wrong/confuse text on shutdown at unattended-upgrades Status in Ubuntu Translations: New Status in unattended-upgrades package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades-0.90ubuntu0.9 Uname: 4.4.0-104-generic #127-Ubuntu SMP Architecture: amd64 I've german systems, so when updates will be installed at shutdown this text will be displayed at the screen. German: "unattended upgrade läuft während des herunterfahrens weiter, es wird fünf Sekunden lange gewartet" English: "unattended upgrade runs during the shutdown, it waits for five seconds" This sentence make absolutly no sence for me. Maybe it is an translationproblem? Don't know text on the english ubuntuversion. The problem is that some customer turned of some computers, because the updates need more time then 5 seconds ;) A better message will that was Windows10 displays at shutdown ...don't turn off the computer, updates will be installed... Thanks and best Reagards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1741579/+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 1741468] Re: Broken GUI in Ubuntu MATE Live Session
18.04, bionic beaver testing live session. -- 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/1741468 Title: Broken GUI in Ubuntu MATE Live Session Status in xorg package in Ubuntu: New Bug description: Device: MacBook Air, late 2013 -The toolbar on the top and the bottom loads, but they seem to be images only. -I cannot click on the Applications, Places, System, Firefox, or MATE Welcome, nor the power button on the top bar. -The Bottom bar's show desktop and switch desktop does not click either. -My cursor shows and tracks, but it does not seem to register clicks. This is both with a mouse and a trackpad. -Background image is black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741468/+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 1741468] Re: Broken GUI in Ubuntu MATE Live Session
What version of Ubuntu MATE? -- 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/1741468 Title: Broken GUI in Ubuntu MATE Live Session Status in xorg package in Ubuntu: New Bug description: Device: MacBook Air, late 2013 -The toolbar on the top and the bottom loads, but they seem to be images only. -I cannot click on the Applications, Places, System, Firefox, or MATE Welcome, nor the power button on the top bar. -The Bottom bar's show desktop and switch desktop does not click either. -My cursor shows and tracks, but it does not seem to register clicks. This is both with a mouse and a trackpad. -Background image is black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1741468/+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 310262] Re: APT::Acquire::Retries only applies to archives and source files
** Changed in: apt (Ubuntu) Status: Confirmed => Fix Committed -- 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/310262 Title: APT::Acquire::Retries only applies to archives and source files Status in apt package in Ubuntu: Fix Committed Status in apt package in Debian: Fix Released Bug description: Binary package hint: apt The APT::Acquire::Retries configuration directive for apt only applies to source and archive, not the various index files (Packages, Release and friends). Intuitively, you would think that it should, but it does not. As far as I can tell, there is no other equivalent directive that would restrict the number of time apt should try to fetch an index case before it give up. This can trigger a relatively rare problem where apt would try to download the same index file again and again, forever until stopped, if the download systematically fail abruptly midway. See LP #291748 for such an example. If apt is being run automatically in the background, this could end consuming a lot of bandwidth and hammer the archive pretty badly before someone notice. According to long-standing upstream Debian bug #119544, fixing this bug would be a relatively trivial code change, but would break the ABI. As such, I would be curious to know if there is an ABI bump on apt roadmap; if yes, would it be possible to nominate this bug for the next major release of apt? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/310262/+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 310262] Re: APT::Acquire::Retries only applies to archives and source files
** Changed in: apt (Debian) Status: New => Fix Released -- 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/310262 Title: APT::Acquire::Retries only applies to archives and source files Status in apt package in Ubuntu: Confirmed Status in apt package in Debian: Fix Released Bug description: Binary package hint: apt The APT::Acquire::Retries configuration directive for apt only applies to source and archive, not the various index files (Packages, Release and friends). Intuitively, you would think that it should, but it does not. As far as I can tell, there is no other equivalent directive that would restrict the number of time apt should try to fetch an index case before it give up. This can trigger a relatively rare problem where apt would try to download the same index file again and again, forever until stopped, if the download systematically fail abruptly midway. See LP #291748 for such an example. If apt is being run automatically in the background, this could end consuming a lot of bandwidth and hammer the archive pretty badly before someone notice. According to long-standing upstream Debian bug #119544, fixing this bug would be a relatively trivial code change, but would break the ABI. As such, I would be curious to know if there is an ABI bump on apt roadmap; if yes, would it be possible to nominate this bug for the next major release of apt? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/310262/+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 1741603] Re: package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemp
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1741603 Title: package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gcc-4.8 package in Ubuntu: New Bug description: unbekannt ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Sat Jan 6 08:49:09 2018 DpkgHistoryLog: Start-Date: 2018-01-06 08:48:14 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Upgrade: initramfs-tools-bin:amd64 (0.103ubuntu4.9, 0.103ubuntu4.10), libruby1.9.1:amd64 (1.9.3.484-2ubuntu1.5, 1.9.3.484-2ubuntu1.6), firefox-locale-de:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), firefox-locale-en:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), google-chrome-stable:amd64 (63.0.3239.108-1, 63.0.3239.132-1), firefox:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), initramfs-tools:amd64 (0.103ubuntu4.9, 0.103ubuntu4.10), ruby1.9.1:amd64 (1.9.3.484-2ubuntu1.5, 1.9.3.484-2ubuntu1.6), firefox-globalmenu:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1) DuplicateSignature: package:libstdc++-4.8-dev:amd64:4.8.4-2ubuntu1~14.04.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (50 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: gcc-4.8 Title: package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1741603/+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 1741603] [NEW] package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte
Public bug reported: unbekannt ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Sat Jan 6 08:49:09 2018 DpkgHistoryLog: Start-Date: 2018-01-06 08:48:14 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Upgrade: initramfs-tools-bin:amd64 (0.103ubuntu4.9, 0.103ubuntu4.10), libruby1.9.1:amd64 (1.9.3.484-2ubuntu1.5, 1.9.3.484-2ubuntu1.6), firefox-locale-de:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), firefox-locale-en:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), google-chrome-stable:amd64 (63.0.3239.108-1, 63.0.3239.132-1), firefox:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), initramfs-tools:amd64 (0.103ubuntu4.9, 0.103ubuntu4.10), ruby1.9.1:amd64 (1.9.3.484-2ubuntu1.5, 1.9.3.484-2ubuntu1.6), firefox-globalmenu:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1) DuplicateSignature: package:libstdc++-4.8-dev:amd64:4.8.4-2ubuntu1~14.04.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (50 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: gcc-4.8 Title: package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-16 (50 days ago) ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1741603 Title: package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gcc-4.8 package in Ubuntu: New Bug description: unbekannt ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Sat Jan 6 08:49:09 2018 DpkgHistoryLog: Start-Date: 2018-01-06 08:48:14 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Upgrade: initramfs-tools-bin:amd64 (0.103ubuntu4.9, 0.103ubuntu4.10), libruby1.9.1:amd64 (1.9.3.484-2ubuntu1.5, 1.9.3.484-2ubuntu1.6), firefox-locale-de:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), firefox-locale-en:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), google-chrome-stable:amd64 (63.0.3239.108-1, 63.0.3239.132-1), firefox:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1), initramfs-tools:amd64 (0.103ubuntu4.9, 0.103ubuntu4.10), ruby1.9.1:amd64 (1.9.3.484-2ubuntu1.5, 1.9.3.484-2ubuntu1.6), firefox-globalmenu:amd64 (57.0.3+build1-0ubuntu0.14.04.1, 57.0.4+build1-0ubuntu0.14.04.1) DuplicateSignature: package:libstdc++-4.8-dev:amd64:4.8.4-2ubuntu1~14.04.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-16 (50 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: gcc-4.8 Title: package libstdc++-4.8-dev:amd64 4.8.4-2ubuntu1~14.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2017-11-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1741603/+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
