[Touch-packages] [Bug 1216399] Re: [llvmpipe] compiz crashed with SIGSEGV in _mm_set_epi32()
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/1216399 Title: [llvmpipe] compiz crashed with SIGSEGV in _mm_set_epi32() Status in mesa package in Ubuntu: Expired Bug description: this just appeared when I first logged in - there was a freeze of 30 seconds, screen when blank and then reappeared with this error. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130822-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Sat Aug 24 20:28:52 2013 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-15 (70 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130615) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () lp_rast_shade_quads_mask () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so lp_rast_triangle_2 () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so lp_rast_queue_scene () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: compiz crashed with SIGSEGV in lp_rast_shade_quads_mask() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1216399/+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 1813097] Re: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package li
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/1813097 Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: Expired Bug description: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:36ec] InstallationDate: Installed on 2014-12-08 (1507 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Supermicro X10SRA-F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=7439bd5c-2c10-4e9d-8ccc-144a158d3318 ro radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 audio=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: X10SRA-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd01/28/2016:svnSupermicro:pnX10SRA-F:pvr0123456789:rvnSupermicro:rnX10SRA-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1813097/+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 1818456] Re: gedit text area is not showed in a white background but "cloning" everything that were in that screen position
[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1818456 Title: gedit text area is not showed in a white background but "cloning" everything that were in that screen position Status in gedit package in Ubuntu: Expired Status in gtk+3.0 package in Ubuntu: Expired Bug description: Since my new fresh install of Ubuntu 18.04 I can't have a good experience. Use a simple gEdit is impossible because the text area is not showed in a white background but "cloning" everything that were in that screen position curiously it not happen with Leafpad editor. But occur with Gnome-claculator. My LibreOffice can't show their buttons in any toolbar. I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf /graphics-drivers) expcting some improve but nothing change. Unhappily. Some years ago I have this same experience in Ubuntu 16.04 but it was over (I don't know how) and even after a dist-upgrade to 18.04 it is OK, but now I had to to new install and the bug is here. Unhappily. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 22:17:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-01 (183 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H87M-HD3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-45-generic root=UUID=3c502856-3b66-4815-8747-59e0fce0d335 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1902261830.d54e54~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1903030730.cb4e3e~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1903030730.cb4e3e~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1902111932.15697e~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1903011933.6afed3~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1901290732.ec2b45~oibaf~b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818456/+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 1818456] Re: gedit text area is not showed in a white background but "cloning" everything that were in that screen position
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1818456 Title: gedit text area is not showed in a white background but "cloning" everything that were in that screen position Status in gedit package in Ubuntu: Expired Status in gtk+3.0 package in Ubuntu: Expired Bug description: Since my new fresh install of Ubuntu 18.04 I can't have a good experience. Use a simple gEdit is impossible because the text area is not showed in a white background but "cloning" everything that were in that screen position curiously it not happen with Leafpad editor. But occur with Gnome-claculator. My LibreOffice can't show their buttons in any toolbar. I've tried to install the oibaf PPA (sudo add-apt-repository ppa:oibaf /graphics-drivers) expcting some improve but nothing change. Unhappily. Some years ago I have this same experience in Ubuntu 16.04 but it was over (I don't know how) and even after a dist-upgrade to 18.04 it is OK, but now I had to to new install and the bug is here. Unhappily. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 3 22:17:53 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,bailer,detection,composite,opengl,compiztoolb ox,decor,grid,move,resize,mousepoll,regex,snap,gno mecompat,place,imgpng,vpswitch,animation,wall,work arounds,fade,session,expo,ezoom,unityshell] GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-09-01 (183 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. H87M-HD3 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-45-generic root=UUID=3c502856-3b66-4815-8747-59e0fce0d335 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/16/2014:svnGigabyteTechnologyCo.,Ltd.:pnH87M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H87M-HD3 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1902261830.d54e54~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1903030730.cb4e3e~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1903030730.cb4e3e~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1902111932.15697e~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1903011933.6afed3~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1901290732.ec2b45~oibaf~b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1818456/+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 1816780] Re: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/1816780 Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mesa package in Ubuntu: Expired Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Feb 20 22:03:16 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:162b] InstallationDate: Installed on 2019-02-14 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP EliteBook 2560p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=b4f30c78-5458-4470-9efe-b17753fcc893 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: mesa Title: package libglx-mesa0:amd64 18.2.2-0ubuntu1~18.04.2 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) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SSU Ver. F.22 dmi.board.name: 162B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 04.21 dmi.chassis.asset.tag: CNU2101KVC dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SSUVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook2560p:pvrA0001C02:rvnHewlett-Packard:rn162B:rvrKBCVersion04.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 2560p dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1816780/+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 1818517] Re: "Network Login" browser does not remember cookies
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1818517 Title: "Network Login" browser does not remember cookies Status in network-manager package in Ubuntu: Expired Bug description: This is with respect to the gnome-shell-portal-helper, part of the gnome-shell package, which opens its own browser window to prompt for a wifi hotspot login. It all works fine except one little papercut: Could it remember cookies? So when I go back to the same hotspot most days I don't have to click OK to accept cookies every time before I can actually click to go online. It's possible I suppose they don't all use cookies. The hotspot in question is a BT wifi hotspot, so probably quite common in GB anyway. Desired behaviour, hate to say, is like Windows: It actually remembered my choice from before and just logged me in right away. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 4 14:05:46 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (173 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-01-13 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1818517/+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 1827691] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827691/+attachment/5261389/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 7881 F pulseaudio /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio /dev/snd/controlC0: widon 7881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU 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/pulseaudio/+bug/1827691/+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 1827691] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1827691/+attachment/5261387/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 7881 F pulseaudio /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio /dev/snd/controlC0: widon 7881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU 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/pulseaudio/+bug/1827691/+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 1827691] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827691/+attachment/5261388/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 7881 F pulseaudio /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio /dev/snd/controlC0: widon 7881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU 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/pulseaudio/+bug/1827691/+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 1823761] Re: [SRU] Move Livepatch in a different tab as in Disco
Hello Andrea, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /software-properties/0.96.24.32.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1823761 Title: [SRU] Move Livepatch in a different tab as in Disco Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact The livepatch graphical interfaces are currently limited in bionic, there is no easy way to know the current status and the details of the changes applied. The new design improves the user experience and we want that to benefit the LTS users * Test case Open software-properties-gtk, you should see a livepatch new tab which has the detail of the status (including the CVEs fixes with the applied livepatch where there is one) * Regression potential The changes are mostly new code so check that the livepatch tab works correctly. There is some UI refactoring so it's best to check that the other tabs still look the same. Note that the changes include some new strings. Those are translated in disco and have been announced to the translators in march as coming to bionic for a SRU (https://lists.ubuntu.com/archives/ubuntu-translators/2019-March/007530.html). Launchpad shares translations between series so we should get those translations included in the next bionic langpacks export. --- Backport the new Livepatch tab from Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823761/+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 1827691] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1827691/+attachment/5261390/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 7881 F pulseaudio /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio /dev/snd/controlC0: widon 7881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU 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/pulseaudio/+bug/1827691/+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 1827691] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1827691/+attachment/5261386/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 7881 F pulseaudio /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio /dev/snd/controlC0: widon 7881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU 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/pulseaudio/+bug/1827691/+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 1827691] Re: Speaker "Front right" do not have sound
apport information ** Tags added: apport-collected disco ** Description changed: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: widon 7881 F pulseaudio + /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio + /dev/snd/controlC0: widon 7881 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-05-01 (2 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + Package: pulseaudio 1:12.2-2ubuntu3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 11/13/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X555YI.510 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X555YI + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: X + dmi.product.name: X555YI + dmi.product.sku: ASUS-NotebookSKU + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1827691/+attachment/5261385/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: widon 7881 F pulseaudio /dev/snd/pcmC1D0p: widon 7881 F...m pulseaudio /dev/snd/controlC0: widon 7881 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/13/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555YI.510 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555YI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555YI.510:bd11/13/2015:svnASUSTeKCOMPUTERINC.:pnX555YI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555YI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555YI dmi.product.sku: ASUS-NotebookSKU 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/pulseaudio/+bug/1827691/+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 1827691] [NEW] Speaker "Front right" do not have sound
Public bug reported: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827691 Title: Speaker "Front right" do not have sound Status in pulseaudio package in Ubuntu: New Bug description: My system is Ubuntu19.04 I use gnome-control-center Sound->Output: Output device(Choose speaker)-> Test Front left have sound but front right have not sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827691/+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 1164016] Re: restore type-ahead find
** Bug watch removed: gitlab.gnome.org/GNOME/nautilus/issues #244 https://gitlab.gnome.org/GNOME/nautilus/issues/244 ** Bug watch removed: GNOME Bug Tracker #679900 https://gitlab.gnome.org/679900 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1164016] Re: restore type-ahead find
** Bug watch removed: GNOME Bug Tracker #680118 https://gitlab.gnome.org/680118 ** Bug watch removed: GNOME Bug Tracker #699087 https://gitlab.gnome.org/699087 ** Bug watch removed: GNOME Bug Tracker #699455 https://gitlab.gnome.org/699455 ** Bug watch removed: GNOME Bug Tracker #721968 https://gitlab.gnome.org/721968 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1666676] Re: Install tracker by default
This is fixed with nautilus 1:3.30.4-1ubuntu1 and later in Disco --- nautilus (1:3.30.4-1ubuntu1) disco; urgency=medium [...] * Depend on tracker instead of Suggests. It is no longer optional. (Closes: #908800) ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released ** No longer affects: ubuntu-meta (Ubuntu) ** Bug watch added: Debian Bug tracker #908800 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800 ** Also affects: nautilus (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908800 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/176 Title: Install tracker by default Status in nautilus package in Ubuntu: Fix Released Status in nautilus package in Debian: Unknown Bug description: Benefits 1. It speeds up searching for files in the Files app. 2. It enables full-text search in the Files app. In other words, you can look for files that contain specific words, instead of searching just by filename. 3. It allows the Batch Rename feature in the Files app able to rename based on file metadata. For instance, you can use the Artist name for properly tagged music files as part of the new file name. 4. It enables file and folder search in the Activities Overview on GNOME. Without tracker, this is a functional regression from Unity and is noticed by a lot of people. Other Info -- You can customize the folders it indexes from Settings > Search > gear button. (LP: #1702878) How to Install == Until this is installed by default, you can install it yourself. Run this command in a terminal then log out and log back in (LP: #1697769): sudo apt install tracker Original Bug Report === For Nautilus' built-in search to not be very slow, Nautilus needs to use tracker for search. This is especially important since it's being seriously proposed for Ubuntu 17.10 that we drop the "type-ahead search" patch that reverted the removal of that feature by Nautilus years ago. (LP: #181) To not cripple Ubuntu GNOME, it was previously decided to let Nautilus build against tracker but not use that functionality on Unity. See this patch: https://bazaar.launchpad.net/~ubuntu- desktop/nautilus/ubuntu/view/head:/debian/patches/ubuntu_tracker_only_on_GNOME.patch This bug is requesting that patch be dropped and the extra tracker components be allowed into main and installed by default in Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/176/+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 1793550] Re: tracker 2.1.4+ library needs ontology files from tracker binary package
** No longer affects: nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1793550 Title: tracker 2.1.4+ library needs ontology files from tracker binary package Status in tracker package in Ubuntu: Fix Released Status in tracker package in Debian: Fix Released Bug description: See the Debian bug for more details. The tracker 2.1.4 libraries will exit with an error, basically crashing the app if they can't find /usr/share/tracker/domain- ontologies/default.rule which is currently provided by the tracker binary package. The most obvious consequence is this means that nautilus won't run if tracker is not installed. But the tracker binary package isn't yet in main. The MIR is LP: #1770877 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1793550/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
FWIW, https://blog.kafaiworks.com/posts/arch-linux-audio-setup-on-msi- gp63/ fixed it for me. Might give the package maintainers a hint what's wrong. (GL63 8RE) -- 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/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
FWIW, https://blog.kafaiworks.com/posts/arch-linux-audio-setup-on-msi- gp63/ fixed it for me. Might give the package maintainers a hint what's wrong. -- 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/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1827685] [NEW] Corrupted background after automatic power suspend
Public bug reported: Another one graphical bug in a new Ubuntu 19.04, GNOME. Corrupted background appears every time after automatic power suspend. The background may show some buggy pictures, but usually shows a white screen. See attached images in .zip archive. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Fri May 3 16:31:10 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption disco ubuntu ** Attachment added: "Screenshots.zip" https://bugs.launchpad.net/bugs/1827685/+attachment/5261360/+files/Screenshots.zip -- 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/1827685 Title: Corrupted background after automatic power suspend Status in xorg package in Ubuntu: New Bug description: Another one graphical bug in a new Ubuntu 19.04, GNOME. Corrupted background appears every time after automatic power suspend. The background may show some buggy pictures, but usually shows a white screen. See attached images in .zip archive. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Fri May 3 16:31:10 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56,
[Touch-packages] [Bug 1793763] Re: NetworkManager interaction with dhclient triggers IP conflict detection at dhcp server, causes ip address changing every day
Probably bug 1826403 is related. It got reported upstream as https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166 Please check whether your bug is perhaps the same and comment on/follow the upstream bug. ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #166 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1793763 Title: NetworkManager interaction with dhclient triggers IP conflict detection at dhcp server, causes ip address changing every day Status in network-manager package in Ubuntu: New Bug description: After installing my laptop with Ubuntu and using the wired network cable with default NetworkManager service to handle the connection, I ran into the issue that my local ipv4 address changes every day, while this never happens for other devices in the network. This is undesirable to me, because it exhausts the local networks IP address pool and the change of IP is inconvenient when working with services like SSH, samba, etc. Added to this, I sometimes experience random network outages especially when waking up from suspend. After some investigation, I found the following to happen: - The exact time the DHCP server provides with a new IP address that different from previous one, is when I wake up my laptop after about 12 hours of being suspended, typicaly at the start of the new working day. - When I lookup the logs of the DHCP server at the time of the laptop getting its new IP address, I find the following: Sep 21 14:36 router dhcpd: DHCPDISCOVER from 68:f7:28:3f:a0:11 via eth2 Sep 21 14:36 router dhcpd: Abandoning IP address 192.168.1.137: pinged before offer Sep 21 14:36 router dhcpd: DHCPDISCOVER from 68:f7:28:3f:a0:11 via eth2 Sep 21 14:36 router dhcpd: DHCPOFFER on 192.168.1.139 to 68:f7:28:3f:a0:11 (kubuntu1804) via eth2 It looks like the DHCP server is detecting a possible IP conflict because it can ping .137 while a DHCPDISCOVER for the hardware address matches the lease with the same IP address it is about to offer. To prevent problems, the DHCP server finds a new free IP address .139 and offers this one instead. Why is this triggered by the ubuntu client? When I look at the client logs at the same time, I see following to happen: Sep 21 00:27 kubuntu1804 systemd-sleep[21703]: Suspending system... Sep 21 14:36 kubuntu1804 kernel: [14934.160293] Restarting tasks ... done. Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.1923] device (enp0s25): carrier: link connected Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.1925] device (enp0s25): DHCPv4 lease renewal requested Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2246] dhcp4 (enp0s25): canceled DHCP transaction, DHCP client pid 18900 Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2247] dhcp4 (enp0s25): state changed bound -> done Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2257] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds) Sep 21 14:36 kubuntu1804 NetworkManager[1027]: [1537533403.2292] dhcp4 (enp0s25): dhclient started with pid 21860 Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3 (xid=0x71ed8c51) Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5 (xid=0x71ed8c51) Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPREQUEST of 192.168.1.139 on enp0s25 to 255.255.255.255 port 67 (xid=0x518ced71) Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPOFFER of 192.168.1.139 from 192.168.1.1 Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPACK of 192.168.1.139 from 192.168.1.1 So if I understand it well, the summary of what happens here is: 1) Client wakes up after being suspended for about 14h 2) Existing running dhclient fired from NetworkManager discovers the lease has expired and requesting a renewal 3) Shortly after that this dhclient is killed by NetworkManager, probably because NetworkManager has detected a "link connected" event, caused by the suspend (the cable has not been removed physicaly). The old dhclient is killed during the lease renewal and probably long before the renewal procedure could be proparly handled 4) A new dhclient is fired by NetworkManager, performing a whole new DHCP request, getting a new IP address from the server I expect the events 2 and 3 happening simultaneously are causing trouble. Probably the old IP .137 is already set to the interface while handling the lease renewal and then a new dhclient is started performing again a new DHCPREQUEST, confusing the dhcp server. When I look at the ISC dhclient, it is running the hook script "/sbin
[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
Xenial was not affected by this bug due to the fix of LP: #1821101 was not released to Xenial. The fix for LP: #1821101 however will be released including the fix for the regression for this bug thus the verification of this regression fix is needed. Verified 1.1ubuntu1.18.04.7~16.04.3 on Xenial: Original version: root@x-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic installation of security upgrades root@x-lp-1824804:~# unattended-upgrade --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial ... Checking: libpam-systemd ([, ]) package libpam-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) Checking: libsystemd0 ([, ]) package libsystemd0 upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) Checking: systemd ([, ]) pkg systemd is on hold sanity check failed pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] Fixed version: root@x-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.3 all automatic installation of security upgrades root@x-lp-1824804:~# unattended-upgrade --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial ... Checking: libpam-systemd ([, ]) package libpam-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting libpam-systemd's dependencies recursively adjusting candidate version: libaudit1=1:2.4.5-1ubuntu2 adjusting candidate version: init-system-helpers=1.29ubuntu1 adjusting candidate version: libpam-modules=1.1.8-3.2ubuntu2 ... ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-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/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt-mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version:
[Touch-packages] [Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
@rbalint I've included the logs but I don't see any Traces as mentioned in LP: #1824341 -- 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/1826916 Title: MAAS uninstalls itself on unattended upgrade Status in maas package in Ubuntu: Incomplete Status in unattended-upgrades package in Ubuntu: New Bug description: Having recently found my MAAS unresponsive I was surprised to find out it's because it uninstalled itself. First, how on earth does this happen, and second how do I go about recovering this I have several critical juju services deployed on a nodes that this MAAS runs and juju is unusable with MAAS down. I've just done the backup as per https://docs.maas.io/2.5/en/manage- backup do I just do a fresh install now and do the restore steps? Will this simply get removed on the next upgrade? Start-Date: 2019-04-24 06:02:09 Commandline: /usr/bin/unattended-upgrade Remove: libjs-yui3-full:amd64 (3.5.1-1ubuntu3), python3-pexpect:amd64 (4.0.1-1), python3-distro-info:amd64 (0.14build1), libwebp5:amd64 (0.4.4-1), python3-roman:amd64 (2.0.0-2), python3-html5lib:amd64 (0.999-4), squid-langpack:amd64 (20150704-1), python3-ecdsa:amd64 (0.13-2), python3-dnspython:amd64 (1.12.0-0ubuntu3), python3-mimeparse:amd64 (0.1.4-1build1), libirs-export141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), fonts-font-awesome:amd64 (4.5.0~dfsg-1), python3-zope.interface:amd64 (4.1.3-1build1), python3-djorm-ext-pgarray:amd64 (1.2-0ubuntu2), javascript-common:amd64 (11), python3-formencode:amd64 (1.3.0-0ubuntu5), dbconfig-pgsql:amd64 (2.0.4ubuntu1), os-prober:amd64 (1.70ubuntu3.3), python3-seamicroclient:amd64 (0.4.0-1ubuntu1), python3-babel:amd64 (1.3+dfsg.1-6), docutils-common:amd64 (0.12+dfsg-1), python3-maas-provisioningserver:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libibverbs1:amd64 (1.1.8-1.1ubuntu2), python3-sphinx:amd64 (1.3.6-2ubuntu1.1), libfreeipmi16:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1:amd64 (1.5.4-1build1), libipmidetect0:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-netaddr:amd64 (0.7.18-1), grub-common:amd64 (2.02~beta2-36ubuntu3.17), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), squid-common:amd64 (3.5.12-1ubuntu7.5), authbind:amd64 (2.1.1+nmu1), freeipmi-common:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-pam:amd64 (0.4.2-13.2ubuntu2), python3-pbr:amd64 (1.8.0-4ubuntu1), python3-pil:amd64 (3.1.2-0ubuntu1.1), python3-simplestreams:amd64 (0.1.0~bzr426-0ubuntu1.2), libaprutil1-dbd-sqlite3:amd64 (1.5.4-1build1), python3-netifaces:amd64 (0.10.4-0.1build2), python3-django-maas:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libjs-jquery:amd64 (1.11.3+dfsg-4), libjs-underscore:amd64 (1.7.0~dfsg-1ubuntu1), libjs-yui3-min:amd64 (3.5.1-1ubuntu3), python3-curtin:amd64 (17.1-11-ga4c9636b-0ubuntu1~16.04.1), python-django-common:amd64 (1.8.7-1ubuntu5.8), python3-service-identity:amd64 (16.0.0-2), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), librdmacm1:amd64 (1.0.21-1), libconfig-general-perl:amd64 (2.60-1), python3-jsonschema:amd64 (2.5.1-4), maas-common:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-txtftp:amd64 (0.1~bzr42-0ubuntu2), apache2-data:amd64 (2.4.18-2ubuntu3.10), python3-crochet:amd64 (1.4.0-0ubuntu2), python3-httplib2:amd64 (0.9.1+dfsg-1), python3-iso8601:amd64 (0.1.11-1), pxelinux:amd64 (3:6.03+dfsg-11ubuntu1), python3-sphinx-rtd-theme:amd64 (0.1.9-1), python3-pyparsing:amd64 (2.0.3+dfsg1-1ubuntu0.1), libpaper1:amd64 (1.1.24+nmu4ubuntu1), libjs-yui3-common:amd64 (3.5.1-1ubuntu3), python3-twisted:amd64 (16.0.0-1ubuntu0.2), python3-simplejson:amd64 (3.8.1-1ubuntu2), ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5.9), libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.2), libapr1:amd64 (1.5.2-3), maas-rack-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libipmiconsole2:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1-ldap:amd64 (1.5.4-1build1), maas-cli:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), distro-info:amd64 (0.14build1), maas-dns:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libisccfg-export140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), python3-pyvmomi:amd64 (5.5.0-2014.1.1-3), sphinx-rtd-theme-common:amd64 (0.1.9-1), python3-petname:amd64 (2.0-0ubuntu1~16.04), python3-alabaster:amd64 (0.7.7-1), python3-maas-client:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), tgt:amd64 (1:1.0.63-1ubuntu1.1), python3-docutils:amd64 (0.12+dfsg-1), postgresql:amd64 (9.5+173ubuntu0.1), python3-tempita:amd64 (0.5.2-1build1), python3-bson-ext:amd64 (3.2-1build1), python3-convoy:amd64 (0.2.1+bzr39-1), maas-region-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libpaper-utils:amd64 (1.1.24+nmu4ubuntu1), ieee-data:amd64 (20150531.1), maas-dhcp:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-django-piston3:amd64 (0.3~rc2-3ubuntu1), liblua5.1-0:amd64 (5.1.5-8ubuntu1), python-babel-localedata:amd64
[Touch-packages] [Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
dpk logging from the same time period ** Attachment added: "unattended-upgrades-dpkg.log.1" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261356/+files/unattended-upgrades-dpkg.log.1 -- 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/1826916 Title: MAAS uninstalls itself on unattended upgrade Status in maas package in Ubuntu: Incomplete Status in unattended-upgrades package in Ubuntu: New Bug description: Having recently found my MAAS unresponsive I was surprised to find out it's because it uninstalled itself. First, how on earth does this happen, and second how do I go about recovering this I have several critical juju services deployed on a nodes that this MAAS runs and juju is unusable with MAAS down. I've just done the backup as per https://docs.maas.io/2.5/en/manage- backup do I just do a fresh install now and do the restore steps? Will this simply get removed on the next upgrade? Start-Date: 2019-04-24 06:02:09 Commandline: /usr/bin/unattended-upgrade Remove: libjs-yui3-full:amd64 (3.5.1-1ubuntu3), python3-pexpect:amd64 (4.0.1-1), python3-distro-info:amd64 (0.14build1), libwebp5:amd64 (0.4.4-1), python3-roman:amd64 (2.0.0-2), python3-html5lib:amd64 (0.999-4), squid-langpack:amd64 (20150704-1), python3-ecdsa:amd64 (0.13-2), python3-dnspython:amd64 (1.12.0-0ubuntu3), python3-mimeparse:amd64 (0.1.4-1build1), libirs-export141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), fonts-font-awesome:amd64 (4.5.0~dfsg-1), python3-zope.interface:amd64 (4.1.3-1build1), python3-djorm-ext-pgarray:amd64 (1.2-0ubuntu2), javascript-common:amd64 (11), python3-formencode:amd64 (1.3.0-0ubuntu5), dbconfig-pgsql:amd64 (2.0.4ubuntu1), os-prober:amd64 (1.70ubuntu3.3), python3-seamicroclient:amd64 (0.4.0-1ubuntu1), python3-babel:amd64 (1.3+dfsg.1-6), docutils-common:amd64 (0.12+dfsg-1), python3-maas-provisioningserver:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libibverbs1:amd64 (1.1.8-1.1ubuntu2), python3-sphinx:amd64 (1.3.6-2ubuntu1.1), libfreeipmi16:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1:amd64 (1.5.4-1build1), libipmidetect0:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-netaddr:amd64 (0.7.18-1), grub-common:amd64 (2.02~beta2-36ubuntu3.17), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), squid-common:amd64 (3.5.12-1ubuntu7.5), authbind:amd64 (2.1.1+nmu1), freeipmi-common:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-pam:amd64 (0.4.2-13.2ubuntu2), python3-pbr:amd64 (1.8.0-4ubuntu1), python3-pil:amd64 (3.1.2-0ubuntu1.1), python3-simplestreams:amd64 (0.1.0~bzr426-0ubuntu1.2), libaprutil1-dbd-sqlite3:amd64 (1.5.4-1build1), python3-netifaces:amd64 (0.10.4-0.1build2), python3-django-maas:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libjs-jquery:amd64 (1.11.3+dfsg-4), libjs-underscore:amd64 (1.7.0~dfsg-1ubuntu1), libjs-yui3-min:amd64 (3.5.1-1ubuntu3), python3-curtin:amd64 (17.1-11-ga4c9636b-0ubuntu1~16.04.1), python-django-common:amd64 (1.8.7-1ubuntu5.8), python3-service-identity:amd64 (16.0.0-2), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), librdmacm1:amd64 (1.0.21-1), libconfig-general-perl:amd64 (2.60-1), python3-jsonschema:amd64 (2.5.1-4), maas-common:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-txtftp:amd64 (0.1~bzr42-0ubuntu2), apache2-data:amd64 (2.4.18-2ubuntu3.10), python3-crochet:amd64 (1.4.0-0ubuntu2), python3-httplib2:amd64 (0.9.1+dfsg-1), python3-iso8601:amd64 (0.1.11-1), pxelinux:amd64 (3:6.03+dfsg-11ubuntu1), python3-sphinx-rtd-theme:amd64 (0.1.9-1), python3-pyparsing:amd64 (2.0.3+dfsg1-1ubuntu0.1), libpaper1:amd64 (1.1.24+nmu4ubuntu1), libjs-yui3-common:amd64 (3.5.1-1ubuntu3), python3-twisted:amd64 (16.0.0-1ubuntu0.2), python3-simplejson:amd64 (3.8.1-1ubuntu2), ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5.9), libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.2), libapr1:amd64 (1.5.2-3), maas-rack-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libipmiconsole2:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1-ldap:amd64 (1.5.4-1build1), maas-cli:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), distro-info:amd64 (0.14build1), maas-dns:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libisccfg-export140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), python3-pyvmomi:amd64 (5.5.0-2014.1.1-3), sphinx-rtd-theme-common:amd64 (0.1.9-1), python3-petname:amd64 (2.0-0ubuntu1~16.04), python3-alabaster:amd64 (0.7.7-1), python3-maas-client:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), tgt:amd64 (1:1.0.63-1ubuntu1.1), python3-docutils:amd64 (0.12+dfsg-1), postgresql:amd64 (9.5+173ubuntu0.1), python3-tempita:amd64 (0.5.2-1build1), python3-bson-ext:amd64 (3.2-1build1), python3-convoy:amd64 (0.2.1+bzr39-1), maas-region-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libpaper-utils:amd64 (1.1.24+nmu4ubuntu1), ieee-data:amd64 (20150531.1), maas-dhcp:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1),
[Touch-packages] [Bug 1826916] Re: MAAS uninstalls itself on unattended upgrade
requested logging during the month of the error ** Attachment added: "unattended-upgrades.log.1" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1826916/+attachment/5261355/+files/unattended-upgrades.log.1 -- 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/1826916 Title: MAAS uninstalls itself on unattended upgrade Status in maas package in Ubuntu: Incomplete Status in unattended-upgrades package in Ubuntu: New Bug description: Having recently found my MAAS unresponsive I was surprised to find out it's because it uninstalled itself. First, how on earth does this happen, and second how do I go about recovering this I have several critical juju services deployed on a nodes that this MAAS runs and juju is unusable with MAAS down. I've just done the backup as per https://docs.maas.io/2.5/en/manage- backup do I just do a fresh install now and do the restore steps? Will this simply get removed on the next upgrade? Start-Date: 2019-04-24 06:02:09 Commandline: /usr/bin/unattended-upgrade Remove: libjs-yui3-full:amd64 (3.5.1-1ubuntu3), python3-pexpect:amd64 (4.0.1-1), python3-distro-info:amd64 (0.14build1), libwebp5:amd64 (0.4.4-1), python3-roman:amd64 (2.0.0-2), python3-html5lib:amd64 (0.999-4), squid-langpack:amd64 (20150704-1), python3-ecdsa:amd64 (0.13-2), python3-dnspython:amd64 (1.12.0-0ubuntu3), python3-mimeparse:amd64 (0.1.4-1build1), libirs-export141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), fonts-font-awesome:amd64 (4.5.0~dfsg-1), python3-zope.interface:amd64 (4.1.3-1build1), python3-djorm-ext-pgarray:amd64 (1.2-0ubuntu2), javascript-common:amd64 (11), python3-formencode:amd64 (1.3.0-0ubuntu5), dbconfig-pgsql:amd64 (2.0.4ubuntu1), os-prober:amd64 (1.70ubuntu3.3), python3-seamicroclient:amd64 (0.4.0-1ubuntu1), python3-babel:amd64 (1.3+dfsg.1-6), docutils-common:amd64 (0.12+dfsg-1), python3-maas-provisioningserver:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libibverbs1:amd64 (1.1.8-1.1ubuntu2), python3-sphinx:amd64 (1.3.6-2ubuntu1.1), libfreeipmi16:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1:amd64 (1.5.4-1build1), libipmidetect0:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-netaddr:amd64 (0.7.18-1), grub-common:amd64 (2.02~beta2-36ubuntu3.17), libirs141:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), squid-common:amd64 (3.5.12-1ubuntu7.5), authbind:amd64 (2.1.1+nmu1), freeipmi-common:amd64 (1.4.11-1.1ubuntu4~0.16.04), python3-pam:amd64 (0.4.2-13.2ubuntu2), python3-pbr:amd64 (1.8.0-4ubuntu1), python3-pil:amd64 (3.1.2-0ubuntu1.1), python3-simplestreams:amd64 (0.1.0~bzr426-0ubuntu1.2), libaprutil1-dbd-sqlite3:amd64 (1.5.4-1build1), python3-netifaces:amd64 (0.10.4-0.1build2), python3-django-maas:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libjs-jquery:amd64 (1.11.3+dfsg-4), libjs-underscore:amd64 (1.7.0~dfsg-1ubuntu1), libjs-yui3-min:amd64 (3.5.1-1ubuntu3), python3-curtin:amd64 (17.1-11-ga4c9636b-0ubuntu1~16.04.1), python-django-common:amd64 (1.8.7-1ubuntu5.8), python3-service-identity:amd64 (16.0.0-2), bind9utils:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), librdmacm1:amd64 (1.0.21-1), libconfig-general-perl:amd64 (2.60-1), python3-jsonschema:amd64 (2.5.1-4), maas-common:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), python3-txtftp:amd64 (0.1~bzr42-0ubuntu2), apache2-data:amd64 (2.4.18-2ubuntu3.10), python3-crochet:amd64 (1.4.0-0ubuntu2), python3-httplib2:amd64 (0.9.1+dfsg-1), python3-iso8601:amd64 (0.1.11-1), pxelinux:amd64 (3:6.03+dfsg-11ubuntu1), python3-sphinx-rtd-theme:amd64 (0.1.9-1), python3-pyparsing:amd64 (2.0.3+dfsg1-1ubuntu0.1), libpaper1:amd64 (1.1.24+nmu4ubuntu1), libjs-yui3-common:amd64 (3.5.1-1ubuntu3), python3-twisted:amd64 (16.0.0-1ubuntu0.2), python3-simplejson:amd64 (3.8.1-1ubuntu2), ntp:amd64 (1:4.2.8p4+dfsg-3ubuntu5.9), libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.2), libapr1:amd64 (1.5.2-3), maas-rack-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libipmiconsole2:amd64 (1.4.11-1.1ubuntu4~0.16.04), libaprutil1-ldap:amd64 (1.5.4-1build1), maas-cli:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), distro-info:amd64 (0.14build1), maas-dns:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libisccfg-export140:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.12), python3-pyvmomi:amd64 (5.5.0-2014.1.1-3), sphinx-rtd-theme-common:amd64 (0.1.9-1), python3-petname:amd64 (2.0-0ubuntu1~16.04), python3-alabaster:amd64 (0.7.7-1), python3-maas-client:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), tgt:amd64 (1:1.0.63-1ubuntu1.1), python3-docutils:amd64 (0.12+dfsg-1), postgresql:amd64 (9.5+173ubuntu0.1), python3-tempita:amd64 (0.5.2-1build1), python3-bson-ext:amd64 (3.2-1build1), python3-convoy:amd64 (0.2.1+bzr39-1), maas-region-controller:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1), libpaper-utils:amd64 (1.1.24+nmu4ubuntu1), ieee-data:amd64 (20150531.1), maas-dhcp:amd64 (2.3.0-6434-gd354690-0ubuntu1~16.04.1),
[Touch-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
This could well be related to this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1793763 I experience the same problem, not only during boot but also when waking up from sleep. All ethernet connectivity is dead for 30 minutes because the switch in my network seems to have detected an IP conflict. This does not occur if I put the plug in after boot. Very annoying, my work arround is to use ifplugd for eth0 instead of NetworkManager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: Confirmed Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+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 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
BTLE persition mouse. There were problems with pair and repeated connection.( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779413 ) All decided this way: https://gist.github.com/Mygod/f390aabf53cf1406fc71166a47236ebf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Invalid Status in gnome-bluetooth package in Ubuntu: Fix Released Bug description: * Impact Bluetooth pointer devices are not always correctly paired, which leads to have them failing to connect or not auto-reconnecting * Test case Pair a bluetooth mouse, it should re-connect automatically after suspend/resume or reboot cycles * Regression potential The change makes all devices go through pairing with the standard code that should work fine but we should keep an eye if it confuses some devices and lead to prompt for a PIN when that shouldn't be needd -- This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+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 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04
Hello Peret - To test the kernel that I built, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages and then reboot. After rebooting, run 'cat /proc/version_signature' and ensure that "lp1827040.1" is included in the output. Then try your iptables timestart rules to see if they work as expected. Additionally, could you include an example timestart rule that you have? I could also test it locally. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1827040 Title: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04 Status in iptables package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I have detected that iptables does not behave in the same way as with previous kernel. Old behaviour: 'timestart' referred to the absolute time (UTC or whatever) to start applying the rul New behaviour: 'timestart' refers to the offset since boot start It implies a migration of the old rules, and it is difficult to keep compatibility, as the offset is complex to behave as an absolute time. Is that expected? Man page suggests that the correct behaviour is the old one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1827040/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Changed in: unattended-upgrades (Ubuntu Disco) Importance: Undecided => High ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** No longer affects: qemu (Ubuntu) -- 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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security
[Touch-packages] [Bug 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
The system is up to date, so I think I have the updates installed. The content of /sys/class/power_supply/BAT0/status is "Not charging". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: Incomplete Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+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 1827644] Re: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
Thank you for your bug report, what's the content of /sys/class/power_supply/BAT0/status? Also do you have the updates from bug #1745032 installed? ** Changed in: upower (Ubuntu) Importance: Undecided => Low ** Changed in: upower (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: Incomplete Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+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 1826870] Re: cache.commit() doesn't release the archives lock
** Changed in: python-apt (Ubuntu) Importance: Undecided => High ** Changed in: python-apt (Ubuntu Xenial) Importance: Undecided => High ** Changed in: python-apt (Ubuntu Bionic) Importance: Undecided => High ** Changed in: python-apt (Ubuntu Cosmic) Importance: Undecided => High ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1826870 Title: cache.commit() doesn't release the archives lock Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Triaged Status in python-apt source package in Bionic: Triaged Status in python-apt source package in Cosmic: Triaged Status in python-apt package in Debian: Fix Released Bug description: [Impact] cache.commit() does not release all the locks it acquires as part of committing. This is a regression of locking fixes in bug 1795407. [Test case] This script should work: #!/usr/bin/env python import apt import subprocess cache = apt.Cache() pkg = cache["hello"] pkg.mark_install() cache.commit() subprocess.check_call(["apt", "remove", "--yes", "hello"]) [Regression potential] Other new locking bugs could pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826870/+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 1795407] Re: python-apt frontend locking
** Bug watch removed: Debian Bug tracker #922416 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922416 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1795407 Title: python-apt frontend locking Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Released Bug description: [Impact] Add support to python-apt for frontend locking. This is a bit more complicated, and also requires some other restructuring: (1) The archives lock was only taken for a short time, when it should have been kept for the duration of an installation, as otherwise debs could disappear from archives/ while the install is running. (2) There was no lock handling at all. Tools essentially acquire the lock, and then release it before commit(). The fix is based on the apt fix, which makes apt_pkg.SystemLock() manage both the frontend and the normal lock, and allows code to call apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner() around dpkg invocations to release the inner lock. Cache.commit() takes care of locking itself now. It releases the inner lock as needed for dpkg invocations. It also now requires apt_pkg.SystemLock to be hold - if it is not, it will acquire it itself. [Test case] 1. Mark a package in the cache for install/removal and commit() - FE lock should be taken while dpkg is running. 2. Mark a package in the cache for install/removal and commit() while holding the lock. Releasing the lock afterwards should still work correctly, and the FE lock should never be released 3. Observe that the archive lock is not released until the last dpkg run The locking behavior can be observed via strace. [Regression potential] The dpkg lock changed the most: Some lock counting might go wrong and programs might fail as a result. Any problems will be isolated, though - dpkg still acquires its locks, and if a lock miscount happens, apt would not tell dpkg to skip acquiring the frontend lock, so even if we were losing the lock anywhere, dpkg would still try to acquire it and not run unlocked. The archive lock done by commit()/fetch_archives() in apt.Cache() is now hold as long as the fetcher object exists though (as it uses the fetcher's get_lock method), which might cause unexpected behavior in apps not expecting that. The lists/ lock is unaffected by the changes, so there should not be any regressions when it comes to updating index files. [Other info (1)] CI changes: There were some improvements to type hints for mypy needed to make type checks pass, and changes to the CI's Dockerfile to pull a new apt from the apt stable PPA (as a new enough apt is only in unapproved atm). Neither of those files are used anywhere outside of the package, so they should not cause any problems. [Other info (2)] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html - This SRU depends on the apt SRU above, and breaks unattended- upgrades in bionic without its SRU due to a bug in the u-u code in handling the new API. - xenial depends on unattended-upgrades SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
Verified 1.1ubuntu1.18.04.11 on Bionic: Old version: root@bb-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===--=== ii unattended-upgrades 1.1ubuntu1.18.04.10 all automatic installation of security upgrades root@bb-lp-1824804:~# unattended-upgrade --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Using (^linux-image-[0-9]+\.[0-9\.]+-.*|^linux-headers-[0-9]+\.[0-9\.]+-.*|^linux-image-extra-[0-9]+\.[0-9\.]+-.*|^linux-modules-[0-9]+\.[0-9\.]+-.*|^linux-modules-extra-[0-9]+\.[0-9\.]+-.*|^linux-signed-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-image-[0-9]+\.[0-9\.]+-.*|^kfreebsd-headers-[0-9]+\.[0-9\.]+-.*|^gnumach-image-[0-9]+\.[0-9\.]+-.*|^.*-modules-[0-9]+\.[0-9\.]+-.*|^.*-kernel-[0-9]+\.[0-9\.]+-.*|^linux-backports-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-modules-.*-[0-9]+\.[0-9\.]+-.*|^linux-tools-[0-9]+\.[0-9\.]+-.*|^linux-cloud-tools-[0-9]+\.[0-9\.]+-.*) regexp to find kernel packages Using (^linux-image-4\.18\.0\-18\-generic$|^linux-headers-4\.18\.0\-18\-generic$|^linux-image-extra-4\.18\.0\-18\-generic$|^linux-modules-4\.18\.0\-18\-generic$|^linux-modules-extra-4\.18\.0\-18\-generic$|^linux-signed-image-4\.18\.0\-18\-generic$|^kfreebsd-image-4\.18\.0\-18\-generic$|^kfreebsd-headers-4\.18\.0\-18\-generic$|^gnumach-image-4\.18\.0\-18\-generic$|^.*-modules-4\.18\.0\-18\-generic$|^.*-kernel-4\.18\.0\-18\-generic$|^linux-backports-modules-.*-4\.18\.0\-18\-generic$|^linux-modules-.*-4\.18\.0\-18\-generic$|^linux-tools-4\.18\.0\-18\-generic$|^linux-cloud-tools-4\.18\.0\-18\-generic$) regexp to find running kernel packages Checking: libpam-systemd ([]) adjusting candidate version: libpam-systemd=237-3ubuntu10.19 falling back to marking libpam-systemd, then adjusting changes package libpam-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 adjusting candidate version: 2to3=3.6.5-3 adjusting candidate version: amavisd-new=1:2.11.0-1ubuntu1 adjusting candidate version: amavisd-new-postfix=1:2.11.0-1ubuntu1 adjusting candidate version: amd64-microcode=3.20180524.1~ubuntu0.18.04.1 adjusting candidate version: aodh-api=6.0.0-0ubuntu1 adjusting candidate version: aodh-common=6.0.0-0ubuntu1 adjusting candidate version: aodh-doc=6.0.0-0ubuntu1 adjusting candidate version: aodh-evaluator=6.0.0-0ubuntu1 adjusting candidate version: aodh-expirer=6.0.0-0ubuntu1 adjusting candidate version: aodh-listener=6.0.0-0ubuntu1 adjusting candidate version: aodh-notifier=6.0.0-0ubuntu1 adjusting candidate version: apport-gtk=2.20.9-0ubuntu7.1 adjusting candidate version: apport-kde=2.20.9-0ubuntu7.1 adjusting candidate version: apport-noui=2.20.9-0ubuntu7.1 adjusting candidate version: apport-retrace=2.20.9-0ubuntu7.1 adjusting candidate version: apport-valgrind=2.20.9-0ubuntu7.1 adjusting candidate version: appstream=0.12.0-3 adjusting candidate version: appstream-doc=0.12.0-3 adjusting candidate version: apt-config-icons=0.12.0-3 adjusting candidate version: apt-config-icons-hidpi=0.12.0-3 ... Fixed version: root@bb-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===--=== ii unattended-upgrades 1.1ubuntu1.18.04.11 all automatic installation of security upgrades root@bb-lp-1824804:~# unattended-upgrade --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic ... Checking: libpam-systemd ([]) adjusting candidate version: libpam-systemd=237-3ubuntu10.19 falling back to adjusting libpam-systemd's dependencies recursively adjusting candidate version: libpam-systemd=237-3ubuntu10.19 adjusting candidate version: libpam-modules=1.1.8-3.6ubuntu2 adjusting candidate version: fdisk=2.31.1-0.4ubuntu3 adjusting candidate version: libidn11=1.33-2.1ubuntu1 adjusting candidate version: libncursesw5=6.1-1ubuntu1 ... ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed
[Touch-packages] [Bug 1827644] [NEW] UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop
Public bug reported: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821 100,000 discharging History (rate): 1556904821 12,453 discharging 1556904818 3,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1827644 Title: UPower and battery indicator show wrong information on fully charged ASUS Vivobook X510UR laptop Status in upower package in Ubuntu: New Bug description: When the ASUS Vivobook X510UR laptop is completely charged, the correct information is displayed on Windows. However, Ubuntu 18.04.2 LTS is unable to detect the true battery state. The GNOME battery indicator usually shows "Estimating..." or "Not charging", when the battery is at 100%. If you use the upower version 0.99.7-2ubuntu0.18.04.1 command "upower -i /org/freedesktop/UPower/devices/battery_BAT0", this is what you get: native-path: BAT0 vendor: ASUSTeK model:ASUS Battery power supply: yes updated: sex 03 mai 2019 14:33:43 -03 (4 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: pending-charge warning-level: none energy: 39,191 Wh energy-empty:0 Wh energy-full: 39,26 Wh energy-full-design: 42,082 Wh energy-rate: 12,453 W voltage: 11,52 V percentage: 100% capacity:93,294% technology: lithium-ion icon-name: 'battery-full-charging-symbolic' History (charge): 1556904821100,000 discharging History (rate): 155690482112,453 discharging 15569048183,744 discharging The "state" should be "fully-charged", but instead it is "pending- charge". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri May 3 14:34:14 2019 InstallationDate: Installed on 2018-12-11 (142 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1827644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
Verified 1.10ubuntu5.1 on Disco. Discos' 1.10ubuntu5 already had the fix to not fall back to mark all upgradable packages, it just received follow-up commits to all kinds of dependencies and skip held packages earlier. root@dd-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-=--=== ii unattended-upgrades 1.10ubuntu5.1 all automatic installation of security upgrades root@dd-lp-1824804:~# apt-mark showhold systemd root@dd-lp-1824804:~# unattended-upgrade --verbose --debug Running on the development release Initial blacklist : Initial whitelist: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=disco, o=Ubuntu,a=disco-security, o=UbuntuESM,a=disco ... Checking: console-setup ([]) adjusting candidate version: console-setup=1.178ubuntu12 Checking: console-setup-linux ([]) adjusting candidate version: console-setup-linux=1.178ubuntu12 Checking: keyboard-configuration ([]) adjusting candidate version: keyboard-configuration=1.178ubuntu12 Checking: libnss-systemd ([]) package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting libnss-systemd's dependencies recursively package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) sanity check failed for: set() Checking: libpam-systemd ([]) package libpam-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting libpam-systemd's dependencies recursively package libpam-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) sanity check failed for: set() Checking: libsystemd0 ([]) package libsystemd0 upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) falling back to adjusting libsystemd0's dependencies recursively package libsystemd0 upgradable but fails to be marked for upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.) sanity check failed for: set() Checking: python3-distupgrade ([]) adjusting candidate version: python3-distupgrade=1:19.04.16 Checking: systemd ([]) pkg systemd is on hold sanity check failed for: set() Checking: systemd-sysv ([]) package systemd-sysv upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting systemd-sysv's dependencies recursively package systemd-sysv upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) sanity check failed for: set() Checking: ubuntu-release-upgrader-core ([]) adjusting candidate version: ubuntu-release-upgrader-core=1:19.04.16 pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Packages that will be upgraded: InstCount=0 DelCount=0 BrokenCount=0 Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2019-05-03 17:28:55 root@dd-lp-1824804:~# ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt-mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed
[Touch-packages] [Bug 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
Verified 1.5ubuntu3.18.10.4 on Cosmic: Buggy version: root@cc-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.5ubuntu3.18.10.3 all automatic installation of security upgrades root@cc-lp-1824804:~# unattended-upgrade --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=cosmic, o=Ubuntu,a=cosmic-security, o=UbuntuESM,a=cosmic ... Checking: libnss-systemd ([]) adjusting candidate version: libnss-systemd=239-7ubuntu10.12 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2to3=3.6.6-1 adjusting candidate version: amphora-agent=3.0.0-0ubuntu2 adjusting candidate version: aodh-api=7.0.0-0ubuntu3 ... Fixed version: root@cc-lp-1824804:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.5ubuntu3.18.10.4 all automatic installation of security upgrades root@cc-lp-1824804:~# unattended-upgrade --verbose --debug Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=cosmic, o=Ubuntu,a=cosmic-security, o=UbuntuESM,a=cosmic ... Checking: libnss-systemd ([]) adjusting candidate version: libnss-systemd=239-7ubuntu10.12 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=239-7ubuntu10.12 adjusting candidate version: libidn11=1.33-2.2ubuntu1 adjusting candidate version: libsystemd0=239-7ubuntu10.12 adjusting candidate version: libpam0g=1.1.8-3.6ubuntu2 ... ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt-mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on
[Touch-packages] [Bug 1770482] Re: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error ex
Work around: Deprecate Ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1770482 Title: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 1 Status in console-setup package in Ubuntu: Confirmed Bug description: This was caused during an upgrade to ubuntu 18.04 from 17.10. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 10 21:00:12 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-12-13 (513 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Keyboard: XKBLAYOUT="querty" BACKSPACE="guess" XKBMODEL="pc105" XKBVARIANT="" XKBOPTIONS="" PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1770482/+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 1827391] Re: Japanese era Reiwa SRU
** Changed in: icu (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1827391 Title: Japanese era Reiwa SRU Status in icu package in Ubuntu: New Status in icu source package in Precise: New Status in icu source package in Trusty: New Status in icu source package in Xenial: New Status in icu source package in Bionic: New Status in icu source package in Cosmic: New Status in icu source package in Disco: New Status in icu source package in Eoan: New Status in icu package in Debian: Confirmed Bug description: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan Note reported abi break / crash of chromium at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
** Description changed: [Impact] - * The fix for LP: #1821101 allowed installing packages for which APT's + * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] - * Set up a system where systemd (or a package that can't be upgraded + * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. - * Mark systemd on hold -apt mark hold systemd + * Mark systemd on hold + apt-mark hold systemd - * Observe u-u falling back to adjusting all upgradable packages in + * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... - Fixed: + Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] - * The less extensive fallback may not find solutions for installing + * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. - [Other Info] Originally reported at: https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1396787/comments/21 -- 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/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt-mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. [Other Info] Originally reported at:
[Touch-packages] [Bug 1824526] Re: It does not send .crash reports manually
Sending of crash reports to Launchpad, but not the Error Tracker, is disabled when a release of Ubuntu approaches the final version. apport (2.20.10-0ubuntu26) disco; urgency=medium * etc/apport/crashdb.conf: Disable Launchpad crash reports for 19.04 release. -- Brian Murray Mon, 08 Apr 2019 14:59:46 -0700 ** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1824526 Title: It does not send .crash reports manually Status in apport package in Ubuntu: Invalid Bug description: When executing: /var/crash$ ubuntu-bug _usr_bin_nautilus.1000.crash It does not send a report. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apport 2.20.10-0ubuntu27 Uname: Linux 5.0.7-050007-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 08:33:57 2019 InstallationDate: Installed on 2018-12-02 (130 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to disco on 2018-12-02 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824526/+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 1821415] Re: pkexec fails in a non-graphical environment
** Changed in: policykit-1 (Ubuntu) Importance: Undecided => Low ** Changed in: policykit-1 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in policykit-1 package in Ubuntu: Triaged Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1614080] Re: PATH contains dot when PATH is unset before running bash
This bug was fixed in the package bash - 5.0-3ubuntu2 --- bash (5.0-3ubuntu2) eoan; urgency=medium * Resurrect "Set the default path to comply with Debian policy" in deb-bash-config.diff which went missing since 4.2+dfsg-1 or so. LP: #1792004 LP: #1614080 Closes: #781367 * Add autopkgtest for the built-in path. -- Dimitri John Ledkov Fri, 03 May 2019 14:31:24 +0100 ** Changed in: bash (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Released Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: In Progress Status in bash source package in Xenial: In Progress Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: In Progress Status in bash source package in Eoan: Fix Released Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+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 1821415] Re: pkexec fails in a non-graphical environment
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in policykit-1 package in Ubuntu: New Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
Reported upstream on https://gitlab.gnome.org/GNOME/totem/issues/323 ** Changed in: totem (Ubuntu) Status: New => Triaged ** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #323 https://gitlab.gnome.org/GNOME/totem/issues/323 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in gst-plugins-good1.0 package in Ubuntu: New Status in totem package in Ubuntu: Triaged Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1827194/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
Verified 1.1ubuntu1.18.04.7~16.04.3 on Xenial: root@x-lp-1823872:~# cat acpid.equivs Source: acpid Section: misc Priority: optional Standards-Version: 3.9.2 Package: acpid File: /etc/acpi/events/powerbtn/powerbtn # /etc/acpi/events/powerbtn # This is called when the user presses the power button and calls # /etc/acpi/powerbtn.sh for further processing. . # Optionally you can specify the placeholder %e. It will pass # through the whole kernel event message to the program you've # specified. . # We need to react on "button power.*" and "button/power.*" because # of kernel changes. . event=button[ /]power action=/etc/acpi/powerbtn.sh root@x-lp-1823872:~# equivs-build acpid.equivs ... root@x-lp-1823872:~# dpkg -i acpid_1.0_all.deb dpkg: warning: downgrading acpid from 1:2.0.26-1ubuntu2 to 1.0 (Reading database ... 32148 files and directories currently installed.) Preparing to unpack acpid_1.0_all.deb ... Unpacking acpid (1.0) over (1:2.0.26-1ubuntu2) ... Setting up acpid (1.0) ... Processing triggers for man-db (2.7.5-1) ... root@x-lp-1823872:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all automatic installation of security upgrades root@x-lp-1823872:~# unattended-upgrade --dry-run Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/acpi/events/powerbtn' root@x-lp-1823872:~# apt install -y -qq unattended-upgrades The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. Suggested packages: bsd-mailx default-mta | mail-transport-agent needrestart The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 9 not upgraded. Need to get 41.4 kB of archives. After this operation, 8,192 B of additional disk space will be used. Preconfiguring packages ... (Reading database ... 32136 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_1.1ubuntu1.18.04.7~16.04.3_all.deb ... Unpacking unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) over (1.1ubuntu1.18.04.7~16.04.2) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up unattended-upgrades (1.1ubuntu1.18.04.7~16.04.3) ... root@x-lp-1823872:~# unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial Option --dry-run given, *not* performing real actions Packages that will be upgraded: acpid Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log /usr/bin/dpkg --status-fd 9 --unpack --auto-deconfigure /var/cache/apt/archives/acpid_1%3a2.0.26-1ubuntu2_amd64.deb /usr/bin/dpkg --status-fd 11 --configure acpid:amd64 /usr/bin/dpkg --status-fd 13 --configure --pending All upgrades installed # ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to
[Touch-packages] [Bug 1827391] Re: Japanese era Reiwa SRU
** Description changed: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan + + Note reported abi break / crash of chromium at https://bugs.debian.org + /cgi-bin/bugreport.cgi?bug=927933 ** Description changed: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan - Note reported abi break / crash of chromium at https://bugs.debian.org - /cgi-bin/bugreport.cgi?bug=927933 + Note reported abi break / crash of chromium at + + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 ** Bug watch added: Debian Bug tracker #927933 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 ** Also affects: icu (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1827391 Title: Japanese era Reiwa SRU Status in icu package in Ubuntu: New Status in icu source package in Precise: New Status in icu source package in Trusty: New Status in icu source package in Xenial: New Status in icu source package in Bionic: New Status in icu source package in Cosmic: New Status in icu source package in Disco: New Status in icu source package in Eoan: New Status in icu package in Debian: Unknown Bug description: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan Note reported abi break / crash of chromium at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1577575] Re: NFS share does not mount on boot using fstab
Sorry - those last two comments were meant for bug #1827286. -- 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/1577575 Title: NFS share does not mount on boot using fstab Status in nfs-utils package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+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 1577575] Re: NFS share does not mount on boot using fstab
I did a little more testing and this looks to be specific to /home. Even mounting over /home (no linking) with autofs results in the same issue. All autofs files as well as the list of packages installed have been attached. As a side note, having /home as a link is an artifact of some very old build scripts and worked fine with an /etc/fstab NFS mount. autofs was deployed as a workaround for bug #1577575. The new workaround for both these bugs is to update all /etc/passwd entries to /vol/home/. -- 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/1577575 Title: NFS share does not mount on boot using fstab Status in nfs-utils package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+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 1820886] Re: Potential inconsistency due to system halt/reboot being allowed when package installation in progress
OK so where we are right now: - Needs coordination with unattended-upgrades to avoid breaking its features - Inhibitors are ignored for root: https://github.com/systemd/systemd/pull/9356 -- 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/1820886 Title: Potential inconsistency due to system halt/reboot being allowed when package installation in progress Status in apt package in Ubuntu: In Progress Bug description: [System] Any current Ubuntu Desktop/Server supported release (Trusty, Xenial, Bionic, Cosmic). [Impact] Package installation turns into an inconsistent state if system is rebooted in the middle of an apt install/upgrade. [Test Case] 1. User1 at Ubuntu box issues "sudo apt-get upgrade"; 2. User2 at Ubuntu box issues "shutdown -r" or reboots it using the GUI; 3. System reboots and potentially turns into an inconsistent state. [Remarks] APT should automatically inhibit system halts/reboots while packages being installed/removed. A similar behavior to what is shown by unattended-upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1820886/+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 1577575] Re: NFS share does not mount on boot using fstab
** Attachment added: "chi.packages" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+attachment/5261278/+files/chi.packages -- 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/1577575 Title: NFS share does not mount on boot using fstab Status in nfs-utils package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: What I expected to happen? I want an NFS share to be mounted on startup using 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ /media/captainplanet/banane/ nfs rw 0 0 What happened instead? It does not mount on startup. Systemd waits 91sec instead and finally starts after failing. I can successfully mount the NFS share with sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575 /media/captainplanet/banane/ When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS share manually before shutdown fixes the second problem. Do you need more information? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon May 2 23:10:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (10 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20DM003XUK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JFET44WW(1.21) dmi.board.asset.tag: Not Available dmi.board.name: 20DM003XUK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DM003XUK dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+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 1827391] Re: Japanese era Reiwa SRU
** Description changed: Japanese era Reiwa SRU + + $ rmadison icu + 4.8.1.1-3ubuntu0.7 | precise-updates + 52.1-3ubuntu0.8| trusty-updates + 55.1-7ubuntu0.4| xenial-updates + 60.2-3ubuntu3 | bionic + 60.2-6ubuntu1 | cosmic + 63.1-6 | disco + 63.1-6 | eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1827391 Title: Japanese era Reiwa SRU Status in icu package in Ubuntu: New Status in icu source package in Precise: New Status in icu source package in Trusty: New Status in icu source package in Xenial: New Status in icu source package in Bionic: New Status in icu source package in Cosmic: New Status in icu source package in Disco: New Status in icu source package in Eoan: New Bug description: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1614080] Re: PATH contains dot when PATH is unset before running bash
** Also affects: bash (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Eoan) Importance: Medium Status: Fix Released ** Also affects: bash (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: bash (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: bash (Ubuntu Eoan) Status: Fix Released => In Progress ** Changed in: bash (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: bash (Ubuntu Disco) Status: New => In Progress ** Changed in: bash (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: bash (Ubuntu Bionic) Status: New => In Progress ** Changed in: bash (Ubuntu Xenial) Status: New => In Progress ** Changed in: bash (Ubuntu Trusty) Status: New => In Progress ** Also affects: bash (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: bash (Ubuntu Precise) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1614080 Title: PATH contains dot when PATH is unset before running bash Status in bash package in Ubuntu: Fix Committed Status in bash source package in Precise: Fix Released Status in bash source package in Trusty: In Progress Status in bash source package in Xenial: In Progress Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: Fix Released Status in bash source package in Disco: In Progress Status in bash source package in Eoan: Fix Committed Bug description: [Impact] * The fallback path built into bash contains '.' which leads to unexpected addition of the current working directory. It should not be there, just like it isnt' in pre-precise and cosmic+. [Test Case] * $ env -u PATH /bin/bash -c 'echo $PATH' Should not have '.' as any component. Nor should there be any empty components, i.e. '::'. [Regression Potential] * Normally PATH is always set by either init, systemd, or any other hypervisor. Thus this only affects executions under bash, when it was started without any environment - e.g. booting with 'init=/bin/bash'. [Other Info] * Original bug report. On ubuntu 16.04 (but also 14.04), running bash with PATH unset always adds '.' to PATH: philippe@pv-desktop:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games philippe@pv-desktop:~$ unset PATH philippe@pv-desktop:~$ /bin/bash philippe@pv-desktop:~$ echo $PATH /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. Even when testing in a virtual machine / docker, and erasing /root/.profile /root/.bashrc /etc/profile /etc/bash.bashrc the problem still happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1614080/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
Verified 1.10ubuntu5.1 on Disco. The crash was already fixed, but u-u did not recognize the moved conffile as the same: root@dd-lp-1823872:~# dpkg -l qemu-guest-agent unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===--=== ii qemu-guest-agent1:3.1+dfsg-2ubuntu2 amd64Guest-side qemu-system agent ii unattended-upgrades 1.10ubuntu5 all automatic installation of security upgrades root@dd-lp-1823872:~# unattended-upgrade --dry-run --verbose --debug ... fetch.run() result: 0 http://archive.ubuntu.com/ubuntu/pool/universe/q/qemu/qemu-guest-agent_3.1+dfsg-2ubuntu3_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/qemu-guest-agent_1%3a3.1+dfsg-2ubuntu3_amd64.deb) found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status blacklist: [] ... Fixed u-u recognize them being the same: root@dd-lp-1823872:~# dpkg -l qemu-guest-agent unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===--=== ii qemu-guest-agent1:3.1+dfsg-2ubuntu2 amd64Guest-side qemu-system agent ii unattended-upgrades 1.10ubuntu5.1 all automatic installation of security upgrades root@dd-lp-1823872:~# unattended-upgrade --dry-run --verbose --debug ... fetch.run() result: 0 http://archive.ubuntu.com/ubuntu/pool/universe/q/qemu/qemu-guest-agent_3.1+dfsg-2ubuntu3_amd64.deb' ID:0 ErrorText: ''> check_conffile_prompt(/var/cache/apt/archives/qemu-guest-agent_1%3a3.1+dfsg-2ubuntu3_amd64.deb) found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 current md5: 15f6ff42cbc5550a07ee21c2a471d905 blacklist: [] ... ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like:
[Touch-packages] [Bug 1827516] Re: unattended-upgrade-shutdown: ModuleNotFoundError: No module named '_dbus_bindings
It seems to be common in the error reports that the Python 3 version running unattended-upgrades is not compatible with the python3-dbus package. Either because the system is running Python 3.6 on Xenial with python3-dbus compiled to support only 3.5 or because the system is upgraded to Bionic and python3-dbus is not upgraded to the version compiled with 3.6. ** Summary changed: - /usr/share/unattended-upgrades/unattended-upgrade-shutdown:ModuleNotFoundError:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@28:/usr/lib/python3/dist-packages/dbus/__init__.py@82:/usr/lib/python3/dist-packages/dbus/types.py@6 + unattended-upgrade-shutdown: ModuleNotFoundError: No module named '_dbus_bindings ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.9, the problem page at https://errors.ubuntu.com/problem/aed6c392ed81ed052ff251ef1c387f22b0ad1884 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. + + Traceback (most recent call last): + File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 28, in + import dbus + File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in + import dbus.types as types + File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in + from _dbus_bindings import ( + ModuleNotFoundError: No module named '_dbus_bindings' ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- 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/1827516 Title: unattended-upgrade-shutdown: ModuleNotFoundError: No module named '_dbus_bindings Status in unattended-upgrades package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.9, the problem page at https://errors.ubuntu.com/problem/aed6c392ed81ed052ff251ef1c387f22b0ad1884 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 28, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827516/+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 1827515] Re: Doom 2016 Would not PLay
** Description changed: I tried running Doom 2016 through play on linux & wine and I keep getting the error message (VK_ERROR_EXTENSION_NOT_PRESENT). I looked through some forums regarding this and I was led to believe that the error was related to a driver issue for my Lenovo T460s laptop. I am not sure if this is the main issue nor know how to install the driver. I - would appreciate any help regarding this matter + would appreciate any help regarding this matter. At the very bottom of + this will be the error log from play on linux that I mentioning about. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 3 09:13:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233] InstallationDate: Installed on 2019-05-02 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:0706 Acer, Inc Bus 001 Device 006: ID 258a:1007 Bus 001 Device 010: ID 1fd2:5003 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FAS1MF00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET73W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS1MF00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: PC0D42G820FAS1MF00 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET73W(1.41):bd12/07/2018:svnLENOVO:pn20FAS1MF00:pvrThinkPadT460s:rvnLENOVO:rn20FAS1MF00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS1MF00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.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 + + Run on Linux Error Log + Unhandled exception: page fault on read access to 0x0038 in 64-bit code (0x000140dd8f0e). + Register dump: + rip:000140dd8f0e rsp:046ddd90 rbp:00014569b088 eflags:00010202 ( R- -- I - - - ) + rax: rbx:046df190 rcx:000145845a20 rdx:046ddd64 + rsi: rdi:000145845a20 r8:1999 r9:0008 r10:00014116d388 + r11:046d9bb0 r12:046de530 r13:046de3e0 r14:7fea4000 r15:046de360 + Stack dump: + 0x046ddd90: 046df190 046df190 + 0x046ddda0: 000145845a20 046de360 + 0x046dddb0: 05c312f0 0001402bf495 + 0x046dddc0: 046df190 + 0x0460: 7bcdf860 046d9680 + 0x046ddde0: + 0x046dddf0: fffe 00014569b088 + 0x046dde00: 0001 00014278b270 + 0x046dde10: 046dde24 + 0x046dde20: 8014 + 0x046dde30: 2f0c60ac38c7 + 0x046dde40: 046df190 7b455a0c + Backtrace: + =>0 0x000140dd8f0e EntryPoint+0xece1bbfe() in doomx64vk (0x00014569b088) + 1 0x0001402bf495 EntryPoint+0xec302184() in doomx64vk (0x00014569b088) + 2 0x7b455a0c UnhandledExceptionFilter+0xbb() in kernel32 (0x046de2f0) + 3 0x7bc5627a RtlSetUnhandledExceptionFilter+0x29() in ntdll (0x046de320)
[Touch-packages] [Bug 1827516] [NEW] unattended-upgrade-shutdown: ModuleNotFoundError: No module named '_dbus_bindings
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.9, the problem page at https://errors.ubuntu.com/problem/aed6c392ed81ed052ff251ef1c387f22b0ad1884 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 28, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic 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/1827516 Title: unattended-upgrade-shutdown: ModuleNotFoundError: No module named '_dbus_bindings Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.9, the problem page at https://errors.ubuntu.com/problem/aed6c392ed81ed052ff251ef1c387f22b0ad1884 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback (most recent call last): File "/usr/share/unattended-upgrades/unattended-upgrade-shutdown", line 28, in import dbus File "/usr/lib/python3/dist-packages/dbus/__init__.py", line 82, in import dbus.types as types File "/usr/lib/python3/dist-packages/dbus/types.py", line 6, in from _dbus_bindings import ( ModuleNotFoundError: No module named '_dbus_bindings' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1827516/+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 1827515] [NEW] Doom 2016 Would not PLay
Public bug reported: I tried running Doom 2016 through play on linux & wine and I keep getting the error message (VK_ERROR_EXTENSION_NOT_PRESENT). I looked through some forums regarding this and I was led to believe that the error was related to a driver issue for my Lenovo T460s laptop. I am not sure if this is the main issue nor know how to install the driver. I would appreciate any help regarding this matter ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 3 09:13:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233] InstallationDate: Installed on 2019-05-02 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:0706 Acer, Inc Bus 001 Device 006: ID 258a:1007 Bus 001 Device 010: ID 1fd2:5003 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FAS1MF00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET73W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS1MF00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: PC0D42G820FAS1MF00 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET73W(1.41):bd12/07/2018:svnLENOVO:pn20FAS1MF00:pvrThinkPadT460s:rvnLENOVO:rn20FAS1MF00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS1MF00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Description changed: - I tried running Doom 2016 through wine and I keep getting the error - message (VK_ERROR_EXTENSION_NOT_PRESENT). I looked through some forums - regarding this and I was led to believe that the error was related to a - driver issue for my Lenovo T460s laptop. I am not sure if this is the - main issue nor know how to install the driver. I would appreciate any - help regarding this matter + I tried running Doom 2016 through play on linux & wine and I keep + getting the error message (VK_ERROR_EXTENSION_NOT_PRESENT). I looked + through some forums regarding this and I was led to believe that the + error was related to a driver issue for my Lenovo T460s laptop. I am not + sure if this is the main issue nor know how to install the driver. I + would appreciate any help regarding this matter ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 3 09:13:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233] + Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Skylake GT2 [HD Graphics
[Touch-packages] [Bug 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
Here's a sample video I found that I assume is OK to share a link to. Just open it, turn subtitles off, and finally open the same file in the same Totem window. https://github.com/Matroska-Org/matroska-test- files/blob/master/test_files/test5.mkv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in gst-plugins-good1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1827194/+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 1826394] Re: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW
More additional: To emphasise that this isn't a wifi-related issue, I have also attached an ethernet adaptor and the same outcome is present on this interface as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1826394 Title: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW Status in network-manager package in Ubuntu: New Bug description: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826394/+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 1827506] [NEW] temporary black screen before login approx 2s
Public bug reported: Did not notice this on live session run from usb, but happens consistently after full install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 3 21:34:07 2019 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP EliteBook 745 G3 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=fb6e31db-1d96-44cb-8452-43deb2fca3a0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2016 dmi.bios.vendor: HP dmi.bios.version: N73 Ver. 01.16 dmi.board.name: 807E dmi.board.vendor: HP dmi.board.version: KBC Version 75.64 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN73Ver.01.16:bd08/17/2016:svnHP:pnHPEliteBook745G3:pvr:rvnHP:rn807E:rvrKBCVersion75.64:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 745 G3 dmi.product.sku: 1234567#ABC dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1827506 Title: temporary black screen before login approx 2s Status in systemd package in Ubuntu: New Bug description: Did not notice this on live session run from usb, but happens consistently after full install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri May 3 21:34:07 2019 InstallationDate: Installed on 2019-05-01 (2 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: HP HP EliteBook 745 G3 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=fb6e31db-1d96-44cb-8452-43deb2fca3a0 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2016 dmi.bios.vendor: HP dmi.bios.version: N73 Ver. 01.16 dmi.board.name: 807E dmi.board.vendor: HP dmi.board.version: KBC Version 75.64 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN73Ver.01.16:bd08/17/2016:svnHP:pnHPEliteBook745G3:pvr:rvnHP:rn807E:rvrKBCVersion75.64:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 745 G3 dmi.product.sku: 1234567#ABC dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1827506/+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 1781699] Re: DHCPv6 server crashes regularly (bionic)
This has been assigned CVE-2019-6470 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6470 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1781699 Title: DHCPv6 server crashes regularly (bionic) Status in DHCP: Unknown Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp package in Debian: New Status in isc-dhcp package in Fedora: Unknown Bug description: The isc-dhcp-server crashes regularly on bionic, sometimes directly after boot, sometimes later. The version installed is 4.3.5-3ubuntu7. journalctl shows: Jul 14 09:35:11 dhcpd[1543]: Solicit message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x7E8EC00 Jul 14 09:35:11 dhcpd[1543]: Advertise NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 8 Jul 14 09:35:11 dhcpd[1543]: Sending Advertise to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:12 dhcpd[1543]: Request message from fe80::18eb:dfc7:17e5:c8d7 port 546, transaction ID 0x65FADB00 Jul 14 09:35:12 dhcpd[1543]: Reply NA: address ::1998 to client with duid 00:01:00:01:21:9f:3a:02:d4:a3:3d:bf:17:e9 iaid = 0 valid for 86400 Jul 14 09:35:12 dhcpd[1543]: Sending Reply to fe80::18eb:dfc7:17e5:c8d7 port 546 Jul 14 09:35:53 dhcpd[1543]: Confirm message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x5105F400 Jul 14 09:35:53 dhcpd[1543]: Sending Reply to fe80::725a:b6ff:fea2:6120 port 546 Jul 14 09:35:53 dhcpd[1543]: Rebind message from fe80::725a:b6ff:fea2:6120 port 546, transaction ID 0x1FEA7E00 Jul 14 09:35:53 dhcpd[1543]: Reply NA: address ::1992 to client with duid 00:04:c2:47:10:e8:8b:dc:d4:a1:0a:1d:21:f2:be:20:e8:a0 iaid = -1230 Jul 14 09:35:53 sh[1543]: ../../../lib/isc/heap.c:251: REQUIRE(idx >= 1 && idx <= heap->last) failed, back trace Jul 14 09:35:53 sh[1543]: #0 0x7efc458a6417 in ?? Jul 14 09:35:53 sh[1543]: #1 0x7efc458a636a in ?? Jul 14 09:35:53 sh[1543]: #2 0x7efc458ad4ea in ?? Jul 14 09:35:53 sh[1543]: #3 0x55d9ee65d571 in ?? Jul 14 09:35:53 sh[1543]: #4 0x55d9ee658701 in ?? Jul 14 09:35:53 sh[1543]: #5 0x55d9ee65ab05 in ?? Jul 14 09:35:53 sh[1543]: #6 0x55d9ee65bff3 in ?? Jul 14 09:35:53 sh[1543]: #7 0x55d9ee65cafc in ?? Jul 14 09:35:53 sh[1543]: #8 0x55d9ee678402 in ?? Jul 14 09:35:53 sh[1543]: #9 0x55d9ee667463 in ?? Jul 14 09:35:53 sh[1543]: #10 0x55d9ee696476 in ?? Jul 14 09:35:53 sh[1543]: #11 0x7efc458dd73b in ?? Jul 14 09:35:53 sh[1543]: #12 0x7efc458ccf9e in ?? Jul 14 09:35:53 sh[1543]: #13 0x7efc458d1e60 in ?? Jul 14 09:35:53 sh[1543]: #14 0x7efc458d2325 in ?? Jul 14 09:35:53 sh[1543]: #15 0x55d9ee6696b0 in ?? Jul 14 09:35:53 sh[1543]: #16 0x55d9ee61d519 in ?? Jul 14 09:35:53 sh[1543]: #17 0x7efc454c6b97 in ?? Jul 14 09:35:53 sh[1543]: #18 0x55d9ee61de0a in ?? Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Main process exited, code=dumped, status=6/ABRT Jul 14 09:35:54 systemd[1]: isc-dhcp-server6.service: Failed with result 'core-dump'. The bug was reported to Debian independently, https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=896122. To manage notifications about this bug go to: https://bugs.launchpad.net/dhcp/+bug/1781699/+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 1827499] Re: bash uninitialized memory access
Confirmed in bionic and it's fixed in 5.0/disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1827499
Title:
bash uninitialized memory access
Status in bash package in Ubuntu:
New
Bug description:
The following gives an error message that suggests that bash is
reading from uninitialized memory:
bash -c 'foo() { declare -n bar=baz; declare -A bar; bar[x]=y; }; foo'
environment: line 0: `�d�K�U': not a valid identifier
The short string of garbled characters is different on each run.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bash 4.4.18-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 3 11:07:11 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: bash
UpgradeStatus: Upgraded to bionic on 2019-04-02 (30 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1827499/+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 1827500] [NEW] 57Y6kpFYMVG4JPr
Public bug reported: 57Y6kpFYMVG4JPr ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 3 03:14:19 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Wrestler [Radeon HD 6310] [1179:fde8] InstallationDate: Installed on 2019-04-16 (16 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: TOSHIBA Satellite C655D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=92c2b91a-d79e-4179-ae8f-406984690f92 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.50:bd04/07/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-007008:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-007008 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 3 02:48:52 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug compiz-0.9 i386 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/1827500 Title: 57Y6kpFYMVG4JPr Status in xorg package in Ubuntu: Invalid Bug description: 57Y6kpFYMVG4JPr ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 3 03:14:19 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Wrestler [Radeon HD 6310] [1179:fde8] InstallationDate: Installed on 2019-04-16 (16 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: TOSHIBA Satellite C655D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=92c2b91a-d79e-4179-ae8f-406984690f92 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.50:bd04/07/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-007008:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D
[Touch-packages] [Bug 1827500] Re: 57Y6kpFYMVG4JPr
** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1827500 Title: 57Y6kpFYMVG4JPr Status in xorg package in Ubuntu: Invalid Bug description: 57Y6kpFYMVG4JPr ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 3 03:14:19 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Wrestler [Radeon HD 6310] [1179:fde8] InstallationDate: Installed on 2019-04-16 (16 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: TOSHIBA Satellite C655D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=92c2b91a-d79e-4179-ae8f-406984690f92 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.50:bd04/07/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-007008:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-007008 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 3 02:48:52 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827500/+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 1827417] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261190/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64 UpgradeStatus:
[Touch-packages] [Bug 1827417] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261193/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic
[Touch-packages] [Bug 1827417] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261195/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827417] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261189/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64 UpgradeStatus:
[Touch-packages] [Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.
apport information ** Tags added: apport-collected third-party-packages ** Description changed: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e + InstallationDate: Installed on 2011-10-07 (2765 days ago) + InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) + IwConfig: + lono wireless extensions. + + lxcbr0no wireless extensions. + + eth0 no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 + Package: pulseaudio 1:8.0-0ubuntu3.10 + PackageArchitecture: amd64 + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 + ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-146-generic N/A + linux-backports-modules-4.4.0-146-generic N/A + linux-firmware 1.157.21 + RfKill: + + Tags: xenial third-party-packages xenial + Uname: Linux 4.4.0-146-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2018-05-23 (344 days ago) + UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev pulse sambashare video + _MarkForUpload: True + dmi.bios.date: 11/15/2010 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F1 + dmi.board.name: M68MT-S2 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. +
[Touch-packages] [Bug 1197569] Re: Move from zeitgeist-1.0 to zeitgeist-2.0
Updating totem task as implemented since version 3.10 (Ubuntu 14.04). ** Changed in: totem (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart-app-launch in Ubuntu. https://bugs.launchpad.net/bugs/1197569 Title: Move from zeitgeist-1.0 to zeitgeist-2.0 Status in Bijiben: Fix Released Status in Cairo-Dock Plug-ins: Fix Released Status in Diodon: Fix Released Status in Scratch: Fix Released Status in Totem: Fix Released Status in Ubuntu Application Launcher: Fix Released Status in Unity: Fix Released Status in unity-lens-applications: In Progress Status in unity-lens-files: Fix Committed Status in Unity Videos Lens: In Progress Status in activity-log-manager package in Ubuntu: Fix Released Status in bijiben package in Ubuntu: Fix Released Status in cairo-dock-plug-ins package in Ubuntu: Fix Released Status in diodon package in Ubuntu: Fix Released Status in folks package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in synapse package in Ubuntu: Fix Released Status in totem package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: In Progress Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: In Progress Status in upstart-app-launch package in Ubuntu: Fix Released Bug description: The older libzeitgeist (http://launchpad.net/libzeitgeist) served its days and will be deprecated soon. All the apps should slowly move to libzeitgeist 2 (zeitgeist-2.0) To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1197569/+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 1827417] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261186/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64 UpgradeStatus:
[Touch-packages] [Bug 1827417] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261197/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827417] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261196/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827417] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261188/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827417] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261194/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827417] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261192/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827417] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261185/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux
[Touch-packages] [Bug 1827417] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1827417/+attachment/5261187/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827417 Title: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only. Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a problem - after one of the updates (sorry for being not precise - I can only track it back to the time I have been surely listening something on headphones - it has to be beginning of this year because last time I have been listening more on my SB Live for sure was in last one-two weeks of February 2019 - I have suddenly lost "stereo" on my headphones. I have speakers connected to on-board sound card and headphones connected to SB Live Value for few years, so I did not mess with outputs or something - one day I changed Audacious output to SbLive in pavucontrol (as usually) and that time the sound was weirdly filtered. I have found that this must be "surround upmix" which I do not need and tried to disable it, enable-remixing = no and the same for "LFE remixing" in /etc/pulse/daemon.conf did not work. It does not matter what configuration I choose in pavucontrol- analog stereo duplex, "analog stereo output", "Analog surround 5.1" or 4.1 - for all "Analog output" scenarios the output is the same except for "mono" (no sound at all). I have tried do "skip" pulseaudio choosing "ALSA" output in Audacious + the alsa configuration for stereo but the upmix is still present. I have followed the old thread in Launchpad Answers: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/169428 = Hello, i'm on ubuntu 16.04LTS (AMD64, with emu10k1 based soundcard) and since the last update I have similar problem - I have lost ability to listen stereo music on my Soundblaster Live Value (i use earphones). Even system sounds , web browser content and mp3 files are up-mixed. Few days ago it was no problem to choose "analag stereo output" in pavucontrol, now it seems that at this output have rear surround channel only (as I suppose, there is "stereo" but vocals are like heard from the other room and there is sometimes reverb as in the bathroom) :/. I had tried adding "set enable-remixing=no" in both /etc/pulse/daemon.conf and in the home directory configuration file without success. I have purged pulseaudio but with the ALSA there is the same problem, I have tried purging alsa and reinstalling without effect. So i thought that it can be emu10k1 driver specific, after digging in the network for solutions I have had tried adding "hint.emu10kx.0.multichannel_disabled " to the module configuration file without visible (or rather soundible ;) effect. I have tried to check EMU10K1 configuration with aweset, but it gives error message, so maybe the bad magic sits somewhere around? aweset /dev/sequencer: No such file or directory Once again - everything worked fine until the last update. I use xubuntu desktop as my machine is quite old, in despair I have installed unity to find the sound settings / speaker configuration etc and button to "disable all effects" as I have seen somewhere, but there were no such options. Help me Obi Wan Kenobi, you're my only hope... = I have next tried to follow the path from ubuntu sound troubleshooting guide, I have purged everything, installed back and now I'm here again with this "upmix" on SBLive! Value. Thanks in advance for help :) Tom --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=654027ee-6ab0-41ba-8537-452da07cda0e InstallationDate: Installed on 2011-10-07 (2765 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. M68MT-S2 Package: pulseaudio 1:8.0-0ubuntu3.10 PackageArchitecture: amd64 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=4559c496-f083-41a2-ad7c-1e03334389fd ro plymouth usbcore.autosuspend=-1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 RfKill: Tags: xenial third-party-packages xenial Uname: Linux 4.4.0-146-generic x86_64
[Touch-packages] [Bug 1827499] [NEW] bash uninitialized memory access
Public bug reported:
The following gives an error message that suggests that bash is reading
from uninitialized memory:
bash -c 'foo() { declare -n bar=baz; declare -A bar; bar[x]=y; }; foo'
environment: line 0: `�d�K�U': not a valid identifier
The short string of garbled characters is different on each run.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bash 4.4.18-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 3 11:07:11 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: bash
UpgradeStatus: Upgraded to bionic on 2019-04-02 (30 days ago)
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1827499
Title:
bash uninitialized memory access
Status in bash package in Ubuntu:
New
Bug description:
The following gives an error message that suggests that bash is
reading from uninitialized memory:
bash -c 'foo() { declare -n bar=baz; declare -A bar; bar[x]=y; }; foo'
environment: line 0: `�d�K�U': not a valid identifier
The short string of garbled characters is different on each run.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bash 4.4.18-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 3 11:07:11 2019
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: bash
UpgradeStatus: Upgraded to bionic on 2019-04-02 (30 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1827499/+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 1827498] [NEW] Geoclue 2 very high memory usage
Public bug reported: After geoclue 2 running at high CPU for some minutes I found CPU usage had dropped to zero but geoclue was still hogging a whopping 11GB of memory (the PC has 16GB). I stopped the geoclue service to recover the memory. Kubuntu 18.04 $ apt-cache policy geoclue-2.0 geoclue-2.0: Installed: 2.4.7-1ubuntu1 Candidate: 2.4.7-1ubuntu1 Version table: *** 2.4.7-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Happy to provide other info on request. ** Affects: geoclue (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to geoclue in Ubuntu. https://bugs.launchpad.net/bugs/1827498 Title: Geoclue 2 very high memory usage Status in geoclue package in Ubuntu: New Bug description: After geoclue 2 running at high CPU for some minutes I found CPU usage had dropped to zero but geoclue was still hogging a whopping 11GB of memory (the PC has 16GB). I stopped the geoclue service to recover the memory. Kubuntu 18.04 $ apt-cache policy geoclue-2.0 geoclue-2.0: Installed: 2.4.7-1ubuntu1 Candidate: 2.4.7-1ubuntu1 Version table: *** 2.4.7-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Happy to provide other info on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/1827498/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
** Changed in: oem-priority Importance: Critical => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: Incomplete Status in bluez package in Ubuntu: Invalid Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+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 1657646] Re: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1657646 Title: Missing thin-provisioning-tools prevents VG with thin pool LV from being (de)activated, but not its creation Status in The Ubuntu-power-systems project: Triaged Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 package in Debian: New Bug description: Creating a thin pool LV is allowed even when thin-provisioning-tools is not installed. But deactivating or activating that VG fails. Since deactivating the VG usually only happens at reboot, the user might fail to notice this big problem until then. I think the lvconvert tool, used to combine the two "thin LVs" into a thin pool LV, should refuse to run if thin-provisioning-tools, or the needed scripts, aren't installed. Steps to reproduce: root@15-89:~# vgcreate vg /dev/vdb1 Volume group "vg" successfully created root@15-89:~# vgs VG #PV #LV #SN Attr VSize VFree vg 1 0 0 wz--n- 40.00g 40.00g root@15-89:~# lvcreate -n pool0 -l 90%VG vg Logical volume "pool0" created. root@15-89:~# lvcreate -n pool0meta -l 5%VG vg Logical volume "pool0meta" created. root@15-89:~# lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert pool0 vg -wi-a- 36.00g pool0meta vg -wi-a- 2.00g root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 100 Jun 21 14:15 ./ drwxr-xr-x 20 root root3820 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:14 vg-pool0 -> ../dm-0 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0meta -> ../dm-1 root@15-89:~# lvconvert --type thin-pool --poolmetadata vg/pool0meta vg/pool0 WARNING: Converting logical volume vg/pool0 and vg/pool0meta to pool's data and metadata volumes. THIS WILL DESTROY CONTENT OF LOGICAL VOLUME (filesystem etc.) Do you really want to convert vg/pool0 and vg/pool0meta? [y/n]: y Converted vg/pool0 to thin pool. root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 120 Jun 21 14:15 ./ drwxr-xr-x 20 root root3840 Jun 21 14:15 ../ crw--- 1 root root 10, 236 Jun 21 13:15 control lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tdata -> ../dm-1 lrwxrwxrwx 1 root root 7 Jun 21 14:15 vg-pool0_tmeta -> ../dm-0 root@15-89:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%S ync Convert [lvol0_pmspare] vg ewi--- 2.00g pool0 vg twi-a-tz-- 36.00g 0.00 0.01 [pool0_tdata] vg Twi-ao 36.00g [pool0_tmeta] vg ewi-ao 2.00g If you now reboot the system, all that is gone: root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:28 ./ drwxr-xr-x 19 root root3760 Jun 21 14:28 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control The same happens if you deactivate the VG (which the reboot undoubtedly triggers). It fails because of a missing /usr/sbin/thin_check which is provided by the thin-provisioning-tools package: root@15-89:~# vgchange -a n /usr/sbin/thin_check: execvp failed: No such file or directory WARNING: Integrity check of metadata for pool vg/pool0 failed. 0 logical volume(s) in volume group "vg" now active root@15-89:~# ll /dev/mapper/ total 0 drwxr-xr-x 2 root root 60 Jun 21 14:29 ./ drwxr-xr-x 19 root root3760 Jun 21 14:29 ../ crw--- 1 root root 10, 236 Jun 21 14:28 control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1657646/+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 1827194] Re: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze
Thanks, it looks like it's neither new nor a regression then (in the sense of something that used to work and stopped). Ideally having an example would make easier to test/work on the issue but I guess most of subtitled videos are non free content and can't be easily shared here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1827194 Title: Loading a subtitled mkv file while already playing a subtitled mkv file makes the UI freeze Status in gst-plugins-good1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: When you have been playing a subtitled mkv file for a while and try to load a new subtitled mkv file in the same instance of Totem, the UI freezes. You must let the video play for a while for the problem to manifest. I don't know how long exactly, but ten minutes should do it. Loading file after file in quick succession works fine, and it doesn't happen if you seek forward in the file to go to a later time in the video. You have to actually watch the video for a while for it to happen. This problem has been in Totem for the past several versions of Ubuntu, but in 19.04 the problem has slightly changed: Totem used to become completely unresponsive and you had to force quit it, but in 19.04 you can click the close button and it closes immediately. Other than that, the problem is the same: all you get is a frozen black screen. This problem could affect other file formats as well, but subtitled Matroska files is what I've personally been affected by. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 1 11:52:22 2019 InstallationDate: Installed on 2019-04-26 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1827194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1827040] Re: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04
Hello, Tyler,I am happy to know you have probably found the issue. And I am happy to test it. The problem is that I am not experienced in testing kernels at all.I am an advanced users, but not a programmer.I do not know how to switch (with no high risk) the kernel, test, and switch it back.If you can give me some indications, just to have an idea of the process, I think I will manage; maybe it is as simple as copying it to the place where kernels are copied, and changing the 'pointer' to the active kernel somewhere.Thanks! En jueves, 2 de mayo de 2019 16:15:31 CEST, Tyler Hicks escribió: Hi Peret - Thanks for the bug report. I was browsing through the kernel commit log and I think this bug may already be fixed by the following commit: commit 916f6efae62305796e012e7c3a7884a267cbacbf Author: Florian Westphal Date: Wed Apr 17 02:17:23 2019 +0200 netfilter: never get/set skb->tstamp https://git.kernel.org/linus/916f6efae62305796e012e7c3a7884a267cbacbf I've built a test kernel that is 5.0.0-13.14 plus that patch. Would you be able to test it? You can find it here: https://people.canonical.com/~tyhicks/lp1827040/ Thanks again! -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1827040 Title: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04 Status in iptables package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I have detected that iptables does not behave in the same way as with previous kernel. Old behaviour: 'timestart' referred to the absolute time (UTC or whatever) to start applying the rul New behaviour: 'timestart' refers to the offset since boot start It implies a migration of the old rules, and it is difficult to keep compatibility, as the offset is complex to behave as an absolute time. Is that expected? Man page suggests that the correct behaviour is the old one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1827040/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1827040 Title: Misbehaviour of iptables 'timestart' parameter in Ubuntu 19.04 Status in iptables package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: I have detected that iptables does not behave in the same way as with previous kernel. Old behaviour: 'timestart' referred to the absolute time (UTC or whatever) to start applying the rul New behaviour: 'timestart' refers to the offset since boot start It implies a migration of the old rules, and it is difficult to keep compatibility, as the offset is complex to behave as an absolute time. Is that expected? Man page suggests that the correct behaviour is the old one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1827040/+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 1827460] Re: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep
** No longer affects: alsa-driver (Ubuntu) ** No longer affects: pulseaudio (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep + [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep in kernel 4.15.0-48.51-generic (but v4.15.0-47.50 works). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1827460 Title: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep in kernel 4.15.0-48.51-generic (but v4.15.0-47.50 works). Status in linux package in Ubuntu: Incomplete Bug description: My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine initially. However, when I close it down (to sleep) and then return, all the sound disappears. The only way to get back the sound is to restart the laptop. The issue seem to start after a recent automatic update. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rickodesea 1545 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 22:49:12 2019 InstallationDate: Installed on 2019-03-28 (36 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1139 F pulseaudio rickodesea 1545 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7XCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IGM dmi.modalias: dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM: dmi.product.family: ideapad 330-15IGM dmi.product.name: 81D1 dmi.product.version: Lenovo ideapad 330-15IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827460/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: New Bug description: Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
With some more trickery I created this situation in Disco: root@d:~# apt-cache policy qemu-guest-agent unattended-upgrades qemu-guest-agent: Installed: 1:2.12+dfsg-3ubuntu8 Candidate: 1:2.12+dfsg-3ubuntu8.6 unattended-upgrades: Installed: 1.10ubuntu5 Candidate: 1.10ubuntu5 But in that case despite root@d:~# apt list --upgradable Listing... Done qemu-guest-agent/disco 1:3.1+dfsg-2ubuntu3 amd64 [upgradable from: 1:2.12+dfsg-3ubuntu8] But unattended upgrades does not like to upgrade it: root@d:~# sudo unattended-upgrade -d Running on the development release Initial blacklist : Initial whitelist: Starting unattended upgrades script [...] No packages found that can be upgraded unattended and no pending auto-removals Not sure what exactly you had in mind to test in Disco, but this seems not to be the path. Can you set up your equivs setup there? -- 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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add:
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
I can indeed trigger it in cosmic with an upgrade from 1:2.12+dfsg- 3ubuntu8 -> 1:2.12+dfsg-3ubuntu8.6 But forcing the same (by enabling cosmics sources) in Disco does not trigger the bug (1.10ubuntu5). You will need an equiv trick to verify Disco as well I think. Here he logs of the cosmic verify: # trigger bug before upgrade /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status An error occurred: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1669, in main install_start_time) File "/usr/bin/unattended-upgrade", line 1875, in run if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 1015, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2019-05-03 05:45:41 Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2138, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1669, in main install_start_time) File "/usr/bin/unattended-upgrade", line 1875, in run if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 1015, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' # upgrade to proposed apt install unattended-upgrades Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: bsd-mailx default-mta | mail-transport-agent needrestart The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. Need to get 41.8 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 unattended-upgrades all 1.5ubuntu3.18.10.4 [41.8 kB] Fetched 41.8 kB in 0s (535 kB/s) Preconfiguring packages ... (Reading database ... 46512 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_1.5ubuntu3.18.10.4_all.deb ... Unpacking unattended-upgrades (1.5ubuntu3.18.10.4) over (1.5ubuntu3.18.10.3) ... Processing triggers for systemd (239-7ubuntu10.13) ... Setting up unattended-upgrades (1.5ubuntu3.18.10.4) ... Processing triggers for man-db (2.8.4-2) ... # retry with fix root@c:~# sudo unattended-upgrade -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script [...] check_conffile_prompt(/var/cache/apt/archives/qemu-guest-agent_1%3a2.12+dfsg-3ubuntu8.6_amd64.deb) found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 current md5: 15f6ff42cbc5550a07ee21c2a471d905 blacklist: [] whitelist: [] Packages that will be upgraded: qemu-guest-agent Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log applying set ['qemu-guest-agent'] (Reading database ... 46512 files and directories currently installed.) Preparing to unpack .../qemu-guest-agent_1%3a2.12+dfsg-3ubuntu8.6_amd64.deb ... Unpacking qemu-guest-agent (1:2.12+dfsg-3ubuntu8.6) over (1:2.12+dfsg-3ubuntu8) ... Setting up qemu-guest-agent (1:2.12+dfsg-3ubuntu8.6) ... Processing triggers for systemd (239-7ubuntu10.13) ... Processing triggers for man-db (2.8.4-2) ... left to upgrade set() All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from /var/log/unattended-upgrades/unattended-upgrades-dpkg.log since 2019-05-03 05:49:31 Mark cosmic as verified ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: Invalid Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such
