[Touch-packages] [Bug 1765913] [NEW] Hybrid graphics don't work after resume
Public bug reported: When my laptop resumes from suspend, the secondary GPU (Radeon R7 M265) does not work. Prior to suspend I can use it. After suspend, trying DRI_PRIME=1 glxinfo | grep OpenGL simply fails (see attached file). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:14:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu wayland-session ** Attachment added: "log" https://bugs.launchpad.net/bugs/1765913/+attachment/5124784/+files/log -- 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/1765913 Title: Hybrid graphics don't work after resume Status in xorg package in Ubuntu: New Bug description: When my laptop resumes from suspend, the secondary GPU (Radeon R7 M265) does not work. Prior to suspend I can use it. After suspend, trying DRI_PRIME=1 glxinfo | grep OpenGL simply fails (see attached file). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:14:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079
[Touch-packages] [Bug 1765911] [NEW] Major performance regression from Ubuntu 17.10 with i915
Public bug reported: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.10 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.6F dmi.chassis.asset.tag: 5CG6351LQL dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 850 G3 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765911 Title: Major performance regression from Ubuntu 17.10 with i915 Status in xorg package in Ubuntu: New Bug description: Desktop performance on my laptop (Intel HD 520, driver: i915) used to be generally good on previous Ubuntu releases but on 18.04, there is a VERY noticeable regression. Moving windows around in GNOME is choppy and tearing. It gets dramatic after the laptop resumes from suspend, GNOME drops to literally ~1-2 FPS. Logging out and restarting the session usually fixes the problem in that it restores the barely acceptable performance level prior to suspend. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15 Uname: Linux 4.15.0-15-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 16:04:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:8079] Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] (rev 81) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f] InstallationDate: Installed on 2018-04-03 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402) MachineType: HP HP EliteBook 850 G3 ProcKernelCmdLine: BOOT_IMAGE=/bionic
[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04
lotuspsychje, if you don't have the hardware anymore, then this report may be closed. However, if issues exist with different hardware, it is most helpful if one files a new report about it. ** Changed in: xorg (Ubuntu) Status: Incomplete => 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/1702347 Title: Graphical glitches in screen by default on 17.10 & 18.04 Status in xorg package in Ubuntu: Invalid Bug description: Ubuntu 17.10 development branch updated and dist-upgraded on 4 july 2017 Im having weird glitches in screen when scrolling or switching windows by default Graphics: Card: NVIDIA C77 [GeForce 9100M G] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1440x900@60.00hz GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2 installing nvidia-340 resulted in a black screen after login, so i had to purge nvidia* to get back to desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Tue Jul 4 20:59:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d] InstallationDate: Installed on 2017-06-13 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) MachineType: Acer, inc. Aspire 7530 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3342 dmi.board.name: EI Capitan dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 7530 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jul 4 20:45:53 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) event6 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1742063] Re: Systemd taking long time to boot into desktop 18.04
ubuntu 18.04 desktop dev @ 21/4/2018 system still slow from gdm3 login to desktop: lotuspsychje@R00TBOOK:~$ systemd-analyze blame 32min 20.754s apt-daily-upgrade.service 5min 17.026s apt-daily.service 29.463s plymouth-quit-wait.service 9.356s dev-sda1.device 1.888s dev-loop0.device 1.880s dev-loop2.device 1.856s dev-loop1.device 1.830s dev-loop3.device 1.633s systemd-udev-trigger.service 1.341s apparmor.service 1.177s keyboard-setup.service 1.174s systemd-rfkill.service 901ms systemd-journal-flush.service 871ms upower.service 799ms systemd-journald.service 782ms NetworkManager.service 749ms plymouth-start.service 687ms preload.service 667ms grub-common.service 649ms swapfile.swap 592ms networking.service 482ms systemd-resolved.service 460ms snapd.service boot to gdm3 is fast and system halt is also fast -- 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/1742063 Title: Systemd taking long time to boot into desktop 18.04 Status in systemd package in Ubuntu: Confirmed Bug description: ubuntu desktop 18.04 development branch with gnome/xorg @ 9/1/2018 Systemd takes a long time to boot both from start to login and from login to desktop systemd-analyze blame showed apt daily services taking up to 1min and i disabled auto updates but it still takes a long time to boot to desktop, on a fast ssd here's the analyze log after apt.daily disabled: 18.598s plymouth-quit-wait.service 6.544s NetworkManager-wait-online.service 6.302s dev-sda1.device 1.126s udisks2.service 1.097s fwupd.service 1.092s systemd-udev-trigger.service 1.028s apparmor.service 786ms keyboard-setup.service 770ms systemd-journald.service 752ms swapfile.swap 750ms upower.service 743ms systemd-rfkill.service 731ms accounts-daemon.service 697ms ModemManager.service 679ms systemd-journal-flush.service 635ms grub-common.service 580ms apport.service 568ms preload.service 566ms networking.service 555ms NetworkManager.service 554ms systemd-resolved.service 503ms systemd-logind.service 412ms snapd.service ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 9 07:57:20 2018 InstallationDate: Installed on 2017-12-18 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215) Lsusb: Bus 002 Device 002: ID 0402:7675 ALi Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer AO722 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7 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: 12/06/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08: dmi.product.family: Type1Family dmi.product.name: AO722 dmi.product.version: V1.08 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742063/+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 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04
@ #5 & #7 sorry mate, dont have this machine in my posession anymore only the older amd 3200 to test on atm, ill try to find other users confirmed this does not happen on wayland, only xorg -- 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/1702347 Title: Graphical glitches in screen by default on 17.10 & 18.04 Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 development branch updated and dist-upgraded on 4 july 2017 Im having weird glitches in screen when scrolling or switching windows by default Graphics: Card: NVIDIA C77 [GeForce 9100M G] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1440x900@60.00hz GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2 installing nvidia-340 resulted in a black screen after login, so i had to purge nvidia* to get back to desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Tue Jul 4 20:59:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d] InstallationDate: Installed on 2017-06-13 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) MachineType: Acer, inc. Aspire 7530 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3342 dmi.board.name: EI Capitan dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 7530 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jul 4 20:45:53 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) event6 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04
lotuspsychje, could you please advise to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/comments/5 ? ** Changed in: xorg (Ubuntu) Status: In Progress => Incomplete -- 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/1702347 Title: Graphical glitches in screen by default on 17.10 & 18.04 Status in xorg package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 development branch updated and dist-upgraded on 4 july 2017 Im having weird glitches in screen when scrolling or switching windows by default Graphics: Card: NVIDIA C77 [GeForce 9100M G] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1440x900@60.00hz GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2 installing nvidia-340 resulted in a black screen after login, so i had to purge nvidia* to get back to desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Tue Jul 4 20:59:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d] InstallationDate: Installed on 2017-06-13 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) MachineType: Acer, inc. Aspire 7530 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3342 dmi.board.name: EI Capitan dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 7530 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jul 4 20:45:53 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) event6 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1702347] Re: Graphical glitches in screen by default on 17.10 & 18.04
** Changed in: xorg (Ubuntu) Status: Expired => In Progress -- 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/1702347 Title: Graphical glitches in screen by default on 17.10 & 18.04 Status in xorg package in Ubuntu: In Progress Bug description: Ubuntu 17.10 development branch updated and dist-upgraded on 4 july 2017 Im having weird glitches in screen when scrolling or switching windows by default Graphics: Card: NVIDIA C77 [GeForce 9100M G] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1440x900@60.00hz GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2 installing nvidia-340 resulted in a black screen after login, so i had to purge nvidia* to get back to desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Tue Jul 4 20:59:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d] InstallationDate: Installed on 2017-06-13 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) MachineType: Acer, inc. Aspire 7530 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3342 dmi.board.name: EI Capitan dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 7530 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jul 4 20:45:53 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) event6 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1748709] Re: Upgrade from xenial to bionic wants to replace moduli
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1748709 Title: Upgrade from xenial to bionic wants to replace moduli Status in openssh package in Ubuntu: Expired Bug description: I see this on upgrade on one machine, which is unexpected. If this file is generated by each machine, why would we ship a default? Configuration file '/etc/ssh/moduli' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** moduli (Y/I/N/O/D/Z) [default=N] ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1748709/+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 1765892] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765892 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 20 20:34:12 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-19 (275 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-04-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765892/+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 1765892] [NEW] package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 20 20:34:12 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-19 (275 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-04-18 (2 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765892 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 20 20:34:12 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-19 (275 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-04-18 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765892/+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 1765882] Re: Infobar has not default theming
** Branch linked: lp:~3v1n0/ubuntu-themes/infobar-default-color -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1765882 Title: Infobar has not default theming Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Nautilus->Trash: the bar where the Empty/Restore buttons are should be themed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765882/+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 1765882] [NEW] Infobar has not default theming
Public bug reported: Nautilus->Trash: the bar where the Empty/Restore buttons are should be themed ** Affects: ubuntu-themes (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1765882 Title: Infobar has not default theming Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Nautilus->Trash: the bar where the Empty/Restore buttons are should be themed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765882/+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 1707606] Re: [nautilus] no sidebar mouseover selection displayed
** Branch linked: lp:~3v1n0/ubuntu-themes/placessidebar-improvements -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1707606 Title: [nautilus] no sidebar mouseover selection displayed Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Using nautilus 3.24 in artful, if you dnd a file over one of the folders in the sidebar with Adwaita you get a green selection displayed around the target entry. When using Ambiance there is no such indication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1707606/+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 1707606] Re: [nautilus] no sidebar mouseover selection displayed
** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1707606 Title: [nautilus] no sidebar mouseover selection displayed Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Using nautilus 3.24 in artful, if you dnd a file over one of the folders in the sidebar with Adwaita you get a green selection displayed around the target entry. When using Ambiance there is no such indication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1707606/+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 1762465] Re: Nautilus sidebar theming is confusing
Not sure how this can be solved... Something like https://i.imgur.com/RA9esFK.png would be better? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+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 1762465] Re: Nautilus sidebar theming is confusing
Not sure how this can be solved... Something like https://i.imgur.com/ZVXQ1ku.png ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1762465 Title: Nautilus sidebar theming is confusing Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The new theming of the Nautilus sidebar is confusing to users. The icons and the icon labels have a different background colour, and when a specific location is selected the background colour of the selected icon changes to be the same as the background colour of the labels, while the other icons have a darker background colour. This is giving the impression that the text labels are a hierarchy of the icon, rather than simply being labels associated with each icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1762465/+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 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Triaged Bug description: This was fresh Ubuntu 16.04 instance on Windows 10, running inside a Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting to upgrade to 18.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sat Feb 10 18:59:28 2018 Dmesg: ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.2.24 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. Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+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 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default
I've given this a test in LXD on my system which triggers the RA stall; after upgrading it does not wait for an RA before marking the interface configured and also confirmed that it does not regress the case where there are existing RA's on the network; those are still received. Note that we see eth0: Configured before the Discovering IPv6 routers, and Received Router Advertisement. Apr 20 20:55:21.062761 b1 systemd[1]: Started Network Service. Apr 20 20:55:21.904103 b1 systemd-networkd[163]: eth0: Configured Apr 20 20:55:21.904190 b1 systemd-networkd[163]: eth0: Discovering IPv6 routers Apr 20 20:55:21.904252 b1 systemd-networkd[163]: NDISC: Started IPv6 Router Solicitation client Apr 20 20:55:21.904632 b1 systemd-networkd[163]: NDISC: Sent Router Solicitation, next solicitation in 3s Apr 20 20:55:21.906538 b1 systemd-networkd[163]: NDISC: Received Router Advertisement: flags none preference medium lifetime 30 sec root@b1:~# networkctl status ●State: routable Address: 10.8.107.88 on eth0 2001:db8:100:f101:216:3eff:fe5f:d776 on eth0 fe80::216:3eff:fe5f:d776 on eth0 Gateway: 10.8.107.1 on eth0 fe80::216:3eff:fe31:e211 (Xensource, Inc.) on eth0 DNS: 10.8.107.1 Search Domains: lxd -- 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/1765173 Title: networkd waits 10 seconds for ipv6 network discovery by default Status in cloud-init package in Ubuntu: Fix Released Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: [Impact] * On ipv6 less hosts, boot stalls for 10s * This is due to implicit RA being on, and wait-online awaiting for RA to timeout * Expectation is, that since explicit request for RA was not done, it should not block network-online.target, whilst all other aspects of network-online.target should be honored. [Test Case] * lxc network set lxdbr0 ipv6.address none * lxc launch ubuntu-daily:bionic lp1765173 * sleep 20 && lxc exec lp1765173 systemd-analyze blame | head Bad result is: 12.157s systemd-networkd-wait-online.service Good result is: 739ms systemd-networkd-wait-online.service [Regression Potential] * If explicit IPv6 dhcp/ra was enabled in .network file, the boot will be blocked awaiting RA response * Only kernel implicit RA configuration will now become "async" * This is inline with behaviour of xenial systems [Other Info] * Original bug report 1. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. $ apt-cache policy systemd systemd: Installed: 237-3ubuntu8 Candidate: 237-3ubuntu8 Version table: *** 237-3ubuntu8 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. systemd-networkd-wait-online doesn't block for 10 seconds waiting on an IPV6 Router Advertisement 4. systemd-networkd sends at least two RA solicitation packets waiting for a response before setting the link to configured. This blocks the boot for every Ubuntu system where it does not have a IPV6 router responding to solicitations. THis includes bionic containers, cloud instances, vms and physical machines. -- We can see that we're spending 13 seconds waiting for networkd to say the network is up. % systemd-analyze blame 13.326s systemd-networkd-wait-online.service 999ms cloud-init-local.service 954ms cloud-init.service 887ms cloud-config.service 749ms dev-vda1.device 666ms cloud-final.service 248ms keyboard-setup.service 175ms systemd-udev-trigger.service 171ms lxd-containers.service 165ms snapd.service 154ms apparmor.service 147ms ssh.service 144ms systemd-timesyncd.service 133ms grub-common.service 130ms systemd-journald.service 130ms accounts-daemon.service 99ms systemd-modules-load.service 98ms systemd-resolved.service 94ms apport.service 92ms rsyslog.service 88ms systemd-logind.service 80ms lvm2-monitor.service 75ms iscsid.service 64ms ebtables.service 62ms user@1000.service 54ms dev-mqueue.mount 53ms ufw.service 52ms systemd-remount-fs.service 52ms kmod-static-nodes.service 34ms systemd-journal-flush.service 34ms polkit.service 32ms systemd-tmpfiles-setup-dev.service 27ms systemd-udevd.service 26ms systemd-networkd.service 26ms systemd-
[Touch-packages] [Bug 1765874] Re: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1765874 Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in avahi package in Ubuntu: New Bug description: I don't know the details other than what was gathered automatically. Look at the Summary info. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: avahi-dnsconfd 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Fri Apr 20 19:32:19 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-18 (823 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-12-04 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1765874/+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 1765874] [NEW] package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I don't know the details other than what was gathered automatically. Look at the Summary info. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: avahi-dnsconfd 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Fri Apr 20 19:32:19 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-18 (823 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-12-04 (137 days ago) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1765874 Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in avahi package in Ubuntu: New Bug description: I don't know the details other than what was gathered automatically. Look at the Summary info. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: avahi-dnsconfd 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Fri Apr 20 19:32:19 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-18 (823 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32-1ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to artful on 2017-12-04 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1765874/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
** Changed in: ifupdown (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Status in ifupdown package in Debian: New Status in vlan package in Debian: Unknown Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1762159] Re: apport-gtk crashes on reports without timestamp
*** This bug is a duplicate of bug 1658188 *** https://bugs.launchpad.net/bugs/1658188 ** This bug has been marked a duplicate of bug 1658188 /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes -- 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/1762159 Title: apport-gtk crashes on reports without timestamp Status in apport package in Ubuntu: Confirmed Bug description: $ /usr/share/apport/apport-gtk Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 598, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 694, in run_argv return self.run_crashes() File "/usr/lib/python3/dist-packages/apport/ui.py", line 245, in run_crashes logind_session[1] > self.report.get_timestamp(): TypeError: '>' not supported between instances of 'float' and 'NoneType' /usr/lib/python3/dist-packages/apport/report.py: def get_timestamp(self): '''Get timestamp (seconds since epoch) from Date field Return None if it is not present. ''' so get_timestamp can return None, but run_crashes does not cover this $ dpkg -s python3-apport Package: python3-apport Status: install ok installed Priority: optional Section: python Installed-Size: 551 Maintainer: Martin Pitt Architecture: all Source: apport Version: 2.20.7-0ubuntu3.7 $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1762159/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes
** Changed in: apport (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: apport (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Description changed: + [Test Case] + Check Error Tracker bucket and make sure version from -proposed doesn't show up there. Given that this happens a whole bunch we should know pretty quick if its fixed. + The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.3-0ubuntu8.2, the problem page at https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 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 you can request it at http://forms.canonical.com/reports/. -- 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/1658188 Title: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport- gtk@597:run_argv:run_crashes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: In Progress Bug description: [Test Case] Check Error Tracker bucket and make sure version from -proposed doesn't show up there. Given that this happens a whole bunch we should know pretty quick if its fixed. The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.3-0ubuntu8.2, the problem page at https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
This could use fixing for Trusty too. https://errors.ubuntu.com/problem/385d2e8ecf335dc2cdd7216506bbf2b6e6b8751c -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Zesty: Fix Released Status in apport source package in Artful: Fix Released Status in apport source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2 --- It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes
This still needs fixing in Ubuntu 16.04. -- 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/1658188 Title: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport- gtk@597:run_argv:run_crashes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.3-0ubuntu8.2, the problem page at https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
Test pkgs for both ifupdown and vlan available in this ppa: https://launchpad.net/~ddstreet/+archive/ubuntu/lp1701023 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes
This was actually fixed in the following version of apport. apport (2.20.5-0ubuntu1) artful; urgency=medium * New upstream release: - bin/apport-retrace: Comment on bug reports when an invalid core file is encountered. (LP: #1647635) - Switch to using HxW directory names for app icons instead of just one number. Thanks to Jeremy Bicha for the patch. - apport/ui.py: Ensure the Date field exists in a report before using it in a comparison. (LP: #1658188) - bin/apport-retrace: Add in a --gdb-sandbox switch which creates or utilizes a sandbox with the report's distribution release and the host system's architecture for installing and running gdb. (LP: #1517257) - apport/hookutils.py: Don't crash if .xsession-errors is not readable by the user. (LP: #1675928) - bin/apport-retrace: Be specific about which required field is missing from a report and not retracing it. * debian/control: Adjust Vcs-Bzr: for artful branch. -- Brian Murray Fri, 12 May 2017 15:11:38 -0700 -- 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/1658188 Title: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport- gtk@597:run_argv:run_crashes Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.3-0ubuntu8.2, the problem page at https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
The function was slightly in Trusty but the attached debdiff should fix the crash seen in the Error Tracker. ** Also affects: apport (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Trusty) Status: New => In Progress ** Changed in: apport (Ubuntu Trusty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Patch added: "bug-1733366-trusty.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5124395/+files/bug-1733366-trusty.patch -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: In Progress Status in apport source package in Xenial: Fix Released Status in apport source package in Zesty: Fix Released Status in apport source package in Artful: Fix Released Status in apport source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2 --- It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+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 1765844] [NEW] openssh private key exposed due to change in permissions
Public bug reported: Following upgrading from 16.04 to 18.04 my ability to push to github stopped working. I checked the permissions on my .ssh folders files and found that the permissions had changed. $ ls -l ~/.ssh total 24 -rw-r--r-- 1 fred fred 782 Mar 29 2016 authorized_keys -rw-r--r-- 1 fred fred 1766 Mar 29 2016 id_rsa -rw-r--r-- 1 fred fred 405 Mar 29 2016 id_rsa.pub -rw-r--r-- 1 fred fred 9732 Jul 1 2016 known_hosts I do not know which package actually caused this change. Upon resetting the permissions chmod +600 ~/.ssh/* Normal ssh function was restored. $ ls -ltr ~/.ssh total 24 -rw--- 1 fred fred 405 Mar 29 2016 id_rsa.pub -rw--- 1 fred fred 1766 Mar 29 2016 id_rsa -rw--- 1 fred fred 782 Mar 29 2016 authorized_keys -rw--- 1 fred fred 9732 Jul 1 2016 known_hosts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 16:10:17 2018 InstallationDate: Installed on 2017-04-05 (380 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1765844 Title: openssh private key exposed due to change in permissions Status in openssh package in Ubuntu: New Bug description: Following upgrading from 16.04 to 18.04 my ability to push to github stopped working. I checked the permissions on my .ssh folders files and found that the permissions had changed. $ ls -l ~/.ssh total 24 -rw-r--r-- 1 fred fred 782 Mar 29 2016 authorized_keys -rw-r--r-- 1 fred fred 1766 Mar 29 2016 id_rsa -rw-r--r-- 1 fred fred 405 Mar 29 2016 id_rsa.pub -rw-r--r-- 1 fred fred 9732 Jul 1 2016 known_hosts I do not know which package actually caused this change. Upon resetting the permissions chmod +600 ~/.ssh/* Normal ssh function was restored. $ ls -ltr ~/.ssh total 24 -rw--- 1 fred fred 405 Mar 29 2016 id_rsa.pub -rw--- 1 fred fred 1766 Mar 29 2016 id_rsa -rw--- 1 fred fred 782 Mar 29 2016 authorized_keys -rw--- 1 fred fred 9732 Jul 1 2016 known_hosts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 16:10:17 2018 InstallationDate: Installed on 2017-04-05 (380 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1765844/+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 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur
Create tmpfiles for persistent journal in postinst only when running systemd - that fixes the issue and the upgrade succeeds. ** Attachment added: "systemd_237-3ubuntu8_237-3ubuntu9.diff.gz" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+attachment/5124390/+files/systemd_237-3ubuntu8_237-3ubuntu9.diff.gz ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- 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/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Triaged Bug description: This was fresh Ubuntu 16.04 instance on Windows 10, running inside a Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting to upgrade to 18.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sat Feb 10 18:59:28 2018 Dmesg: ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.2.24 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. Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
** Bug watch added: Debian Bug tracker #896433 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433 ** Also affects: ifupdown (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #896434 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896434 ** Also affects: vlan (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896434 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Status in ifupdown package in Debian: Unknown Status in vlan package in Debian: Unknown Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1755006] Re: ModemManager crashed with SIGSEGV
Just got this after rebooting. No idea what's going on here, I have no modems attached to this machine. I don't believe it is the same as the other bug, as the routine listed as crashing was neither g_closure_invoke() nor the one in the other bug. I have no idea what it actually _was_; I would have expected that to be attached with my own bug report but it wasn't. :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1755006 Title: ModemManager crashed with SIGSEGV Status in modemmanager package in Ubuntu: Confirmed Bug description: Dont know. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 11 19:02:30 2018 ExecutablePath: /usr/sbin/ModemManager ProcCmdline: /usr/sbin/ModemManager ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x55d771dd4659:repz cmpsb %es:(%rdi),%ds:(%rsi) PC (0x55d771dd4659) ok source "%es:(%rdi)" (0x55d771e68b28) ok destination "%ds:(%rsi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: modemmanager StacktraceTop: () ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ModemManager crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1755006/+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 1424768] Re: Consider switching to path based activation
** Tags added: rls-bb-notifixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1424768 Title: Consider switching to path based activation Status in whoopsie package in Ubuntu: Confirmed Status in whoopsie source package in Bionic: Confirmed Bug description: 1) Ubuntu 15.04 2) 0.2.46 3) Whoopsie to only run when it is needed. 4) Instead it runs constantly, using network activity, l See bug (there are more..): https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481 also try: sudo fnotifystat -p whoopsie Instead whoopsie should use path based activation to only run when /var/crash has changed. http://www.freedesktop.org/software/systemd/man/systemd.path.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
** Also affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Changed in: ifupdown (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Trusty) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Xenial) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Artful) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Artful) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Bionic) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1756595] Re: disk space info inadvertently provides all installed snaps
** Tags added: rls-bb-notfixing -- 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/1756595 Title: disk space info inadvertently provides all installed snaps Status in apport package in Ubuntu: Invalid Status in apt package in Ubuntu: Triaged Status in apport source package in Bionic: Invalid Status in apt source package in Bionic: Triaged Bug description: When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1756595/+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 1765646] [NEW] Ubuntu 16.04 - issue with badtar package installation
You have been subscribed to a public bug: apt install bsdtar fails with dependency issue on 16.04: root@czz17163-laptop:~/scripts# apt-get install bsdtar Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: bsdtar : Depends: libarchive13 (= 3.1.2-11build1) but 3.1.2-11ubuntu0.16.04.3 is to be installed E: Unable to correct problems, you have held broken packages. Solution: Include in repository the bsdtar package from https://packages.ubuntu.com/xenial/amd64/bsdtar/download (wget http://security.ubuntu.com/ubuntu/pool/universe/liba/libarchive/bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb ) which works with libarchive13 in version 3.1.2-11ubuntu0.16.04.3 which is included in U16.04 ** Affects: libarchive (Ubuntu) Importance: Undecided Status: Incomplete -- Ubuntu 16.04 - issue with badtar package installation https://bugs.launchpad.net/bugs/1765646 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765531] Re: python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: ordinal not in range(128)
Hello, UpgradeStatus: No upgrade log present (probably fresh install) Questions : Where could I found the upgrade log on my ubuntu installation to attach it to this bug ? Thanks by advance for your support Best regards Battant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1765531 Title: python 2.7 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: ordinal not in range(128) Status in python2.7 package in Ubuntu: New Bug description: Hello, I have eclipse 4.7 https://www.eclipse.org/downloads/ vim and openjdk-8-jre I just try to install eclim http://eclim.org/ Here us my install process log ./eclim_2.7.2.bin Welcome to the installer for eclim 2.7.2. Please specify the root directory of your eclipse install. Ex: /opt/eclipse /usr/local/eclipse Please specify the directory where you would like the eclim vimfiles installed. If you do not want to install the vimfiles (eg: emacs-eclim users), then type: skip Ex: ~/.vim ~/.vim/bundle/eclim > ../.vim Choose which eclim features you would like to install. Type the number for each feature you want to install: Ex (Java and Python): 0 5 Ex (Java and Python): 0,5 Ex (Java, Web, and C/C++): 0-2 0) Java Development 1) Web Development 2) C/C++ Development 3) Ruby Development 4) Php Development 5) Python Development 6) Scala Development 7) Groovy Development 8) Android Development > 5 Eclim plugins to install: Python Development Is this correct? (y/n): y running: ['java', '-Djava.net.useSystemProxies=true', '-jar', '/home/mparchet/Applications_d\xc3\xa9veloppement/rcp-oxygen2/eclipse/plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar', '-initialize', '-debug'] ... Traceback (most recent call last): File "/tmp/eclim-installer.6Bte/install", line 1205, in main() File "/tmp/eclim-installer.6Bte/install", line 96, in main install(options, eclim) File "/tmp/eclim-installer.6Bte/install", line 116, in install step_dependencies(options, eclipse, plugins) File "/tmp/eclim-installer.6Bte/install", line 361, in step_dependencies eclipse.gc() File "/tmp/eclim-installer.6Bte/install", line 921, in gc '-application', 'org.eclipse.equinox.p2.garbagecollector.application', File "/tmp/eclim-installer.6Bte/install", line 929, in execute self._initialize() File "/tmp/eclim-installer.6Bte/install", line 900, in _initialize info = self.execute('-initialize', '-debug') File "/tmp/eclim-installer.6Bte/install", line 936, in execute stdout, stderr = execute(cmd) File "/tmp/eclim-installer.6Bte/install", line 624, in execute stdout = stdout.decode() UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 56: ordinal not in range(128) Could you help me please to fix this bug ? Thanks by advance for your support Best regards Battant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python2.7 2.7.15~rc1-1 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 23:48:56 2018 SourcePackage: python2.7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1765531/+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 1765831] Re: systemd-logind crashed with SIGABRT in log_assert_failed_realm()
*** This bug is a duplicate of bug 1755074 *** https://bugs.launchpad.net/bugs/1755074 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1755074, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765831/+attachment/5124300/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765831/+attachment/5124303/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765831/+attachment/5124310/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765831/+attachment/5124312/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765831/+attachment/5124313/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765831/+attachment/5124314/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765831/+attachment/5124315/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755074 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1765831 Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm() Status in systemd package in Ubuntu: New Bug description: Started the system and this error occurred after around 20 seconds after login ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Sun Apr 15 10:00:27 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-03-27 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) MachineType: LENOVO 20GHS00K00 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=2e2a4599-ac88-4ca0-a25b-825c9baf38c9 ro Signal: 6 SourcePackage: systemd StacktraceTop: log_assert_failed_realm () from /lib/systemd/libsystemd-shared-237.so ?? () ?? () ?? () ?? () 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. Title: systemd-logind crashed with SIGABRT in log_assert_failed_realm() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1LET74W (1.74 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GHS00K00 dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1LET74W(1.74):bd12/26/2017:svnLENOVO:pn20GHS00K00:pvrThinkPadX1Tablet:rvnLENOVO:rn20GHS00K00:rvr0B98417WIN:cvnLENOVO:ct32:cvrNone: dmi.product.family: ThinkPad X1 Tablet dmi.product.name: 20GHS00K00 dmi.product.version: ThinkPad X1 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765831/+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 1765832] [NEW] Two finger scrolling not working after suspend
Public bug reported: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765832 Title: Two finger scrolling not working after suspend Status in xorg package in Ubuntu: New Bug description: When waking up my laptop, two finger scrolling is not working anymore. Running: $ modprobe -r psmouse $ modprobe psmouse restores the functionality. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 20 08:23:33 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2018-04-10 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) MachineType: LENOVO 20BTS09800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET26W (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS09800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS09800 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.x
[Touch-packages] [Bug 1760810] Re: Non-pinned available package in -proposed not chosen
@juliank: I tried your command (with --simulate) on my own laptop and with this option it says that gnome can't be installed, while plain apt will happily install it. For the history I'll attach my logging. ** Attachment added: "logging of installing gnome with and without aspcud solver" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1760810/+attachment/5124299/+files/apt-gnome.log -- 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/1760810 Title: Non-pinned available package in -proposed not chosen Status in Auto Package Testing: New Status in apt package in Ubuntu: Invalid Bug description: In autopkgtest we just had this situation: root@humorous-bullfrog:~# cat /etc/apt/preferences Package: * Pin: release a=bionic Pin-Priority: 990 Package: python3.6 Pin: release a=bionic-proposed Pin-Priority: 995 Package: python3.6-venv Pin: release a=bionic-proposed Pin-Priority: 995 Package: libpython3.6-stdlib Pin: release a=bionic-proposed Pin-Priority: 995 Package: python3.6-minimal Pin: release a=bionic-proposed Pin-Priority: 995 Package: libpython3.6-minimal Pin: release a=bionic-proposed Pin-Priority: 995 Package: libpython3.6 Pin: release a=bionic-proposed Pin-Priority: 995 Package: python3.6-examples Pin: release a=bionic-proposed Pin-Priority: 995 Package: python3.6-dev Pin: release a=bionic-proposed Pin-Priority: 995 Package: libpython3.6-dev Pin: release a=bionic-proposed Pin-Priority: 995 Package: libpython3.6-testsuite Pin: release a=bionic-proposed Pin-Priority: 995 Package: idle-python3.6 Pin: release a=bionic-proposed Pin-Priority: 995 Package: python3.6-doc Pin: release a=bionic-proposed Pin-Priority: 995 Package: python3.6-dbg Pin: release a=bionic-proposed Pin-Priority: 995 Package: libpython3.6-dbg Pin: release a=bionic-proposed Pin-Priority: 995 root@humorous-bullfrog:~# apt -oDebug::pkgProblemResolver=true full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib > Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mK > (< 3.6.5-2) Considering python3-distutils:amd64 7 as a solution to libpython3.6-stdlib:amd64 22 Added python3-distutils:amd64 to the remove list Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64 Investigating (0) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib > Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR > Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15 Added python3-distutils:amd64 to the remove list Fixing dh-python:amd64 via keep of python3-distutils:amd64 Investigating (1) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib > Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mK > (< 3.6.5-2) Considering python3-distutils:amd64 7 as a solution to libpython3.6-stdlib:amd64 22 Added python3-distutils:amd64 to the remove list Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64 Investigating (1) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib > Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR > Considering python3-distutils:amd64 7 as a solution to dh-python:amd64 15 Added python3-distutils:amd64 to the remove list Fixing dh-python:amd64 via keep of python3-distutils:amd64 Investigating (2) libpython3.6-stdlib:amd64 < 3.6.5~rc1-1 -> 3.6.5-3 @ii umU Ib > Broken libpython3.6-stdlib:amd64 Breaks on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mK > (< 3.6.5-2) Considering python3-distutils:amd64 7 as a solution to libpython3.6-stdlib:amd64 22 Added python3-distutils:amd64 to the remove list Fixing libpython3.6-stdlib:amd64 via remove of python3-distutils:amd64 Investigating (2) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib > Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR > Considering python3-distutils:amd64 22 as a solution to dh-python:amd64 15 Removing dh-python:amd64 rather than change python3-distutils:amd64 Investigating (3) python3:amd64 < 3.6.4-1 @ii mK Ib > Broken python3:amd64 Depends on dh-python:amd64 < 3.20180325ubuntu2 @ii mR > Considering dh-python:amd64 22 as a solution to python3:amd64 40 Added dh-python:amd64 to the remove list Fixing python3:amd64 via keep of dh-python:amd64 Investigating (3) dh-python:amd64 < 3.20180325ubuntu2 @ii mK Ib > Broken dh-python:amd64 Depends on python3-distutils:amd64 < 3.6.5~rc1-1 @ii mR > Considerin
[Touch-packages] [Bug 1765646] Re: Ubuntu 16.04 - issue with badtar package installation
Thanks for taking your time to report this issue and help making Ubuntu better. Looking at https://launchpad.net/ubuntu/+source/libarchive it seems that 3.1.2-11build1 was the original version available, but that 3.1.2-11ubuntu0.16.04.3 has been pushed as an update. It might be that the package you attempt to install is still pointing to the older version. This can occur if you have just recently installed your system or a package mirror is temporarily out of sync. Could you please try running `sudo apt update` to update the package lists and see if the issue persists? ** Package changed: vagrant (Ubuntu) => libarchive (Ubuntu) ** Changed in: libarchive (Ubuntu) Status: New => Incomplete ** Tags added: unmetdeps xenial ** Summary changed: - Ubuntu 16.04 - issue with badtar package installation + Ubuntu 16.04 - issue with bsdtar package installation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1765646 Title: Ubuntu 16.04 - issue with bsdtar package installation Status in libarchive package in Ubuntu: Incomplete Bug description: apt install bsdtar fails with dependency issue on 16.04: root@czz17163-laptop:~/scripts# apt-get install bsdtar Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: bsdtar : Depends: libarchive13 (= 3.1.2-11build1) but 3.1.2-11ubuntu0.16.04.3 is to be installed E: Unable to correct problems, you have held broken packages. Solution: Include in repository the bsdtar package from https://packages.ubuntu.com/xenial/amd64/bsdtar/download (wget http://security.ubuntu.com/ubuntu/pool/universe/liba/libarchive/bsdtar_3.1.2-11ubuntu0.16.04.3_amd64.deb ) which works with libarchive13 in version 3.1.2-11ubuntu0.16.04.3 which is included in U16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1765646/+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 1745089] Re: fsck freezing console
You asked e2fsck to run badblocks ( -c ), which takes a very, very long time. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1745089 Title: fsck freezing console Status in util-linux package in Ubuntu: Invalid Bug description: 1. After some operations, the program does not respond and does not allow you to exit back to the console. 2. Expected that the program or report the current state, or let go of it. 3. Started root@ubuntu:~# fsck.ext4 -fyc /dev/sdb1 After some time, the program froze the console. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: util-linux 2.30.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 24 05:13:39 2018 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1745089/+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 1765818] Re: systemd-journald crashed with SIGABRT in __ftruncate64()
*** This bug is a duplicate of bug 1765305 *** https://bugs.launchpad.net/bugs/1765305 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1765305, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765818/+attachment/5124216/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765818/+attachment/5124219/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765818/+attachment/5124226/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765818/+attachment/5124228/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765818/+attachment/5124229/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765818/+attachment/5124230/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765818/+attachment/5124232/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1765305 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1765818 Title: systemd-journald crashed with SIGABRT in __ftruncate64() Status in systemd package in Ubuntu: New Bug description: don't know how this happen ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 Uname: Linux 4.17.0-041700rc1-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 Date: Fri Apr 20 20:20:40 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-04 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57b3 Realtek Semiconductor Corp. Acer 640 × 480 laptop camera Bus 001 Device 002: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-533 ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc1-generic root=UUID=b694ac48-3627-4b2e-863b-049be64c80bf ro i8042.nopnp pci=nocrs vmalloc=256M i915.enable_guc=1 i915.enable_guc_submission=1 acpi_osi=! "acpi_osi=Windows 2015" pcie_ports=native quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: __ftruncate64 (fd=22, length=8388608) at ../sysdeps/unix/sysv/linux/ftruncate64.c:30 journal_file_post_change () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so 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. Title: systemd-journald crashed with SIGABRT in __ftruncate64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Stego_AP dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd10/18/2017:svnAcer:pnAspireES1-533:pvrV1.12:rvnAcer:rnStego_AP:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: APL dmi.product.name: Aspire ES1-533 dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765818/+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 1765819] [NEW] Canonical Livepatch snap cannot be installed
Public bug reported: I was trying to setup livepatch in software-properties and got the following error message: "Canonical Livepatch snap cannot be installed" How do I go about sorting that out? ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Tags added: 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/1765819 Title: Canonical Livepatch snap cannot be installed Status in software-properties package in Ubuntu: New Bug description: I was trying to setup livepatch in software-properties and got the following error message: "Canonical Livepatch snap cannot be installed" How do I go about sorting that out? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1765819/+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 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I faced issues when upgrading Ubuntu 16.04 (I don't remember exactly, maybe from 16.04.3 to 16.04.4). At end of the upgrade it showed following error: Setting up python-minimal (2.7.12-1~16.04) ... Traceback (most recent call last): File "/usr/local/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/local/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/local/lib/python2.7/compileall.py", line 16, in import struct File "/usr/local/lib/python2.7/struct.py", line 1, in from _struct import * ImportError: No module named _struct dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: python-minimal E: Sub-process /usr/bin/dpkg returned an error code (1) It started showing Broken Package error in Ubuntu so I thought re-installing python would fix this issue, but it uninstalled python with all python packages and all softwares which depends on any python library, for example gimp, kicad, kde, oxygen-icon-theme, pycharm etc (list is very long). Now when ever I try to install python: sudo apt-get install python Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpython-stdlib libpython2.7-minimal libpython2.7-stdlib python-minimal python2.7 python2.7-minimal Suggested packages: python-doc python-tk python2.7-doc The following NEW packages will be installed: libpython-stdlib libpython2.7-minimal libpython2.7-stdlib python python-minimal python2.7 python2.7-minimal 0 upgraded, 7 newly installed, 0 to remove and 21 not upgraded. Need to get 1,628 kB/3,877 kB of archives. After this operation, 16.6 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-minimal amd64 2.7.12-1ubuntu0~16.04.3 [340 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7-minimal amd64 2.7.12-1ubuntu0~16.04.3 [1,261 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 python-minimal amd64 2.7.12-1~16.04 [28.1 kB] Fetched 1,628 kB in 6s (248 kB/s) Selecting previously unselected package libpython2.7-minimal:amd64. (Reading database ... 250996 files and directories currently installed.) Preparing to unpack .../libpython2.7-minimal_2.7.12-1ubuntu0~16.04.3_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.3) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.12-1ubuntu0~16.04.3_amd64.deb ... Unpacking python2.7-minimal (2.7.12-1ubuntu0~16.04.3) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.12-1~16.04_amd64.deb ... Unpacking python-minimal (2.7.12-1~16.04) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.12-1ubuntu0~16.04.3_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.12-1ubuntu0~16.04.3) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.12-1ubuntu0~16.04.3_amd64.deb ... Unpacking python2.7 (2.7.12-1ubuntu0~16.04.3) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.12-1~16.04_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.12-1~16.04) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20180209-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ... Processing triggers for mime-support (3.59ubuntu1) ... Setting up libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.3) ... Setting up python2.7-minimal (2.7.12-1ubuntu0~16.04.3) ... Linking and byte-compiling packages for runtime python2.7... Setting up python-minimal (2.7.12-1~16.04) ... Traceback (most recent call last): File "/usr/local/lib/python2.7/runpy.py", line 174, in _run_module_as_main "__main__", fname, loader, pkg_name) File "/usr/local/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/local/lib/python2.7/compileall.py", line 16, in import struct File "/usr/local/lib/python2.7/struct.py", line 1, in from _struct import * ImportError: No module named _struct dpkg: error processing package python-minimal (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: python-minimal E: Sub-process /usr/bin/dpkg returned an error code (1) Please help m
[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found
** Also affects: ca-certificates (Ubuntu Bionic) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764848 Title: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found Status in Ubuntu Single Sign On Client: New Status in ca-certificates package in Ubuntu: Confirmed Status in ca-certificates source package in Bionic: Confirmed Status in ca-certificates package in Debian: Unknown Bug description: The certificate /usr/share/ca- certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca- certificates is conflicting with /etc/ssl/certs/UbuntuOne- Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client. This results in the postinst trigger for ca-certificates to remove the /etc/ssl/certs/ca-certificates.crt file. This happens because the postinst trigger runs update-ca-certificates --fresh. If I run update-ca-certificates without the --fresh flag, the conflict is a non-issue and the ca-certificates.crt file is restored. If I understand some of the postinst code correctly, --fresh should only be run if called directly or if upgrading from a ca-certificates version older than 2011. Running bionic with daily -updates channel and ran into this this morning due to the release of ca-certificates version 20180409. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+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 1760128] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
I tested the version of the package from -proposed (while running avahi- browse per the test case) and did not receive any errors. bdmurray@clean-xenial-amd64:~$ sudo apt-get install avahi-daemon avahi-dnsconfd avahi-utils Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: avahi-daemon avahi-dnsconfd avahi-utils 3 upgraded, 0 newly installed, 0 to remove and 576 not upgraded. 2 not fully installed or removed. Need to get 97.8 kB of archives. After this operation, 1,024 B disk space will be freed. Get:1 http://192.168.10.7/ubuntu xenial-proposed/main amd64 avahi-daemon amd64 0.6.32~rc+dfsg-1ubuntu2.2 [59.5 kB] Get:2 http://192.168.10.7/ubuntu xenial-proposed/main amd64 avahi-utils amd64 0.6.32~rc+dfsg-1ubuntu2.2 [24.3 kB] Get:3 http://192.168.10.7/ubuntu xenial-proposed/universe amd64 avahi-dnsconfd amd64 0.6.32~rc+dfsg-1ubuntu2.2 [14.0 kB] Fetched 97.8 kB in 0s (2,106 kB/s) (Reading database ... 212825 files and directories currently installed.) Preparing to unpack .../avahi-daemon_0.6.32~rc+dfsg-1ubuntu2.2_amd64.deb ... Unpacking avahi-daemon (0.6.32~rc+dfsg-1ubuntu2.2) over (0.6.32~rc+dfsg-1ubuntu2.1) ... Preparing to unpack .../avahi-utils_0.6.32~rc+dfsg-1ubuntu2.2_amd64.deb ... Unpacking avahi-utils (0.6.32~rc+dfsg-1ubuntu2.2) over (0.6.32~rc+dfsg-1ubuntu2.1) ... Preparing to unpack .../avahi-dnsconfd_0.6.32~rc+dfsg-1ubuntu2.2_amd64.deb ... Unpacking avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2.2) over (0.6.32~rc+dfsg-1ubuntu2.1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu10) ... Setting up avahi-daemon (0.6.32~rc+dfsg-1ubuntu2.2) ... Setting up avahi-utils (0.6.32~rc+dfsg-1ubuntu2.2) ... Setting up avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2.2) ... ** 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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1760128 Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in avahi package in Ubuntu: Fix Released Status in avahi source package in Xenial: Fix Committed Bug description: Ubuntu Update 30.03.18 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 30 16:32:50 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-01-31 (788 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1760128/+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 1765803] [NEW] package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127
Public bug reported: cant install upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: perl 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 20 23:21:18 2018 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6~beta1 SourcePackage: perl Title: package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1765803 Title: package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 Status in perl package in Ubuntu: New Bug description: cant install upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: perl 5.26.1-5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 Date: Fri Apr 20 23:21:18 2018 ErrorMessage: dpkg-deb --control subprocess returned error exit status 127 Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6~beta1 SourcePackage: perl Title: package perl 5.26.1-5 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1765803/+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 1765401] Re: gtk+ toolbar style setting ignored in bionic?
Thanks for your suggestions. >The list of files you have tried didn't include >$HOME/.config/gtkrc-2.0 >My own experimentation shows settings in this file take precedence over >$HOME/.gtkrc-2.0 1) Just tried it, doesn't make any difference. 2) I actually tried running GnuCash under a debugger, and I observed it in the debugger opening and parsing both ~/.gtkrc-2.0 and ~/.gtkrc-2.0.gnucash, so I don't think the issue is that my config files are in the wrong place (and that shouldn't even matter, because the setting in dconf is correct and GnuCash should be obeying that setting even if there are no config files at all). >In addition you may check for the presence of >/etc/gtk-2.0/gtkrc >Which may also set this as well as the gtkrc file for the current gtk theme >Bionic is using. Doesn't exist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765401 Title: gtk+ toolbar style setting ignored in bionic? Status in gtk+2.0 package in Ubuntu: New Bug description: I like big buttons with text labels below them in GnuCash toolbars. Fortunately, that's exactly what I had in Ubuntu 17.10. However, having upgraded to 18.04 this morning, suddenly the GnuCash toolbars are back to being small buttons with no text labels. There are SO MANY PLACES to set this preference, and yet, it's not working: $ gconftool-2 --search-key-regex toolbar /desktop/gnome/interface/toolbar_style = both /desktop/gnome/interface/toolbar_detachable = false /desktop/gnome/interface/toolbar_icons_size = large-toolbar $ gconftool --search-key-regex toolbar /desktop/gnome/interface/toolbar_style = both /desktop/gnome/interface/toolbar_detachable = false /desktop/gnome/interface/toolbar_icons_size = large-toolbar $ dconf dump /org/gnome/desktop/interface/ | grep toolbar toolbar-style='both' $ gtk-query-settings | grep toolbar ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR I have no idea why that last one says "both-horiz" rather than "both". I honestly have no idea where that setting is coming from and can't find any way to find out. (I even tried running strace on gtk-query- settings to see what it was reading, and that didn't help.) I can't find any way to change this setting in gnome-tweaks. Is the ability to have large icons with text below them simply gone in 18.04, or has the setting migrated to yet another location that I have to set it in now (it seems like Ubuntu and/or GNOME decides to move settings to a completely new backend just for the heck of it every few releases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk2.0-bin 2.24.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 08:46:15 2018 InstallationDate: Installed on 2016-01-16 (824 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+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 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying
Adding block-proposed to avoid automatic migration, without release team ack. ** Tags added: block-proposed -- 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/1761630 Title: journald takes over /dev/log in bionic, impacts usability of syslog querying Status in rsyslog package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Confirmed Status in rsyslog source package in Bionic: Fix Committed Status in systemd source package in Bionic: Confirmed Bug description: In bionic, /dev/log is now owned by systemd-journald. $ sudo fuser -v /dev/log USERPID ACCESS COMMAND /run/systemd/journal/dev-log: root 1 F systemd root628 F systemd-journal $ This is ok; there are good reasons to want to do this. (Timestamp precision that's not dependent on the syslog protocol; logging available earlier in boot and later at shutdown; unified queriability of logs around services.) The logfiles previously populated by rsyslog under /var/log are now empty (no longer being updated, and the previous files logrotated away): $ ls -l /var/log/auth.log -rw-r- 1 syslog adm 0 Mar 25 00:06 /var/log/auth.log $ This is also ok, we don't really want log data duplicated in two places on the system; so since we now have persistent journal under /var/log/journal, we don't want to also create these plaintext files by default. However, it's not clear that this is by design, rather than by accident. rsyslog is still /configured/ to log to these files; it just isn't receiving any data because it no longer controls the socket. $ sudo lsof -p 852|grep DGRAM rsyslogd 852 syslog3u unix 0x8e5680435000 0t0351 /run/systemd/journal/syslog type=DGRAM $ Dimitri and I have discussed that rsyslog should continue to function, so that users who have remote syslogging configured can still make use of this. It looks like currently this is not the case, because journald is not forwarding to rsyslog. That is not ok. What is also not ok is that, now that logs are only being written to the journal by default instead of to syslog files, querying these logs by syslog priority only works if you know the syslog facility by number (and, afaics, you can only filter by one syslog facility at a time). So whereas before, you could find mail logs by looking in /var/log/mail.log by default, you now have to know to run 'journalctl SYSLOG_FACILITY=2'; and if you want a view of what was previously in /var/log/syslog (i.e. filtering out non-syslog systemd logs, it seems the most compact way to express this is 'journalctl --system SYSLOG_FACILITY={0,1,2,3,5,6,7,8,9,11,12,13,14,15,16,17,18,19,20,21,22,23}'. This is really not good. Admins have never needed to know the mapping of symbolic names to facility numbers to work with syslog; this throws away 30 years of convention with log handling. If we are going to store the logs in the journal by default, I think there needs to be a way to query the logs using symbolic names consistent with syslog(3) and /etc/rsyslog.d/50-default.conf. I don't think we can release with things in the current state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1761630/+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 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur
** Changed in: systemd (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: This was fresh Ubuntu 16.04 instance on Windows 10, running inside a Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting to upgrade to 18.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sat Feb 10 18:59:28 2018 Dmesg: ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.2.24 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. Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+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 1765401] Re: gtk+ toolbar style setting ignored in bionic?
I don't have the solution for your issue unfortunately. But I can eliminate a few elements: Gnucash has switched to gsettings/dconf starting with 2.6.0. That means gconftool and gconftool2 changes are ignored by gnucash. As you discovered making the change in dconf is seen by gnucash 2.6.x. As I mentioned on the gnucash mailing list, gtk as of 3.10 has completely removed user control over the tool bar style. It is up to the developers to handle it (which hasn't happened for gnucash so far). That means unfortunately I don't know of any way to reliably control this setting in gnucash 3.x. >From the test result I infer gtk-query-settings only queries settings for gtk3, so any result you get from that will not help. The list of files you have tried didn't include $HOME/.config/gtkrc-2.0 My own experimentation shows settings in this file take precedence over $HOME/.gtkrc-2.0 In addition you may check for the presence of /etc/gtk-2.0/gtkrc Which may also set this as well as the gtkrc file for the current gtk theme Bionic is using. Perhaps with the switch back to gnome shell Ubuntu has chosen to make a very strict theme to enforce their style. But I have no idea about this as I'm not on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765401 Title: gtk+ toolbar style setting ignored in bionic? Status in gtk+2.0 package in Ubuntu: New Bug description: I like big buttons with text labels below them in GnuCash toolbars. Fortunately, that's exactly what I had in Ubuntu 17.10. However, having upgraded to 18.04 this morning, suddenly the GnuCash toolbars are back to being small buttons with no text labels. There are SO MANY PLACES to set this preference, and yet, it's not working: $ gconftool-2 --search-key-regex toolbar /desktop/gnome/interface/toolbar_style = both /desktop/gnome/interface/toolbar_detachable = false /desktop/gnome/interface/toolbar_icons_size = large-toolbar $ gconftool --search-key-regex toolbar /desktop/gnome/interface/toolbar_style = both /desktop/gnome/interface/toolbar_detachable = false /desktop/gnome/interface/toolbar_icons_size = large-toolbar $ dconf dump /org/gnome/desktop/interface/ | grep toolbar toolbar-style='both' $ gtk-query-settings | grep toolbar ! gtk-toolbar-style: GTK_TOOLBAR_BOTH_HORIZ ! gtk-toolbar-icon-size: GTK_ICON_SIZE_LARGE_TOOLBAR I have no idea why that last one says "both-horiz" rather than "both". I honestly have no idea where that setting is coming from and can't find any way to find out. (I even tried running strace on gtk-query- settings to see what it was reading, and that didn't help.) I can't find any way to change this setting in gnome-tweaks. Is the ability to have large icons with text below them simply gone in 18.04, or has the setting migrated to yet another location that I have to set it in now (it seems like Ubuntu and/or GNOME decides to move settings to a completely new backend just for the heck of it every few releases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgtk2.0-bin 2.24.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 08:46:15 2018 InstallationDate: Installed on 2016-01-16 (824 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+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 1765758] [NEW] Gtk.Entry is not receiving editing-done signal (at least in python3, ubuntu 16.04)
Public bug reported: Description: Ubuntu 16.04.4 LTS Release: 16.04 According to: https://developer.gnome.org/gtk3/stable/GtkCellEditable.html#GtkCellEditable-editing-done Implementations of GtkCellEditable are responsible for emitting this signal when they are done editing, e.g. GtkEntry is emitting it when the user presses Enter. What I did: On the http://python-gtk-3-tutorial.readthedocs.io/en/latest/entry.html example I added a "connect signal": self.entry.connect("editing-done", self.on_editentry_done) also added the def def on_editentry_done(self, widget, *args): print('Hi!') Running the script and pressing either the "enter" or the "return" key, inside the entry box, expected "Hi!" to be printed on the terminal. (I have not checked if this is not working in C, I checked only in python 3) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: python3 xenial -- 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/1765758 Title: Gtk.Entry is not receiving editing-done signal (at least in python3, ubuntu 16.04) Status in gtk+3.0 package in Ubuntu: New Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 According to: https://developer.gnome.org/gtk3/stable/GtkCellEditable.html#GtkCellEditable-editing-done Implementations of GtkCellEditable are responsible for emitting this signal when they are done editing, e.g. GtkEntry is emitting it when the user presses Enter. What I did: On the http://python-gtk-3-tutorial.readthedocs.io/en/latest/entry.html example I added a "connect signal": self.entry.connect("editing-done", self.on_editentry_done) also added the def def on_editentry_done(self, widget, *args): print('Hi!') Running the script and pressing either the "enter" or the "return" key, inside the entry box, expected "Hi!" to be printed on the terminal. (I have not checked if this is not working in C, I checked only in python 3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1765758/+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 1765757] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 13
Public bug reported: update-grub hangs entire system at found initrd indefinitely. If I temporarily hard-reboot and add `acpi=off` to kernel params, update-grub finishes. This is a fresh "Erase disk and Reinstall" of a Minimal from yesterdays bionic iso Description:Ubuntu Bionic Beaver (development branch) Release:18.04 initramfs-tools: Installed: 0.130ubuntu3 Candidate: 0.130ubuntu3 Version table: *** 0.130ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 18:55:21 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2018-04-19 (0 days ago) InstallationMedia: 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: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1765757 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 Status in initramfs-tools package in Ubuntu: New Bug description: update-grub hangs entire system at found initrd indefinitely. If I temporarily hard-reboot and add `acpi=off` to kernel params, update-grub finishes. This is a fresh "Erase disk and Reinstall" of a Minimal from yesterdays bionic iso Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 initramfs-tools: Installed: 0.130ubuntu3 Candidate: 0.130ubuntu3 Version table: *** 0.130ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 18:55:21 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2018-04-19 (0 days ago) InstallationMedia: 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: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1765757/+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 1762200] Re: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-graphics-drivers-340 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-390 (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1762200 Title: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: System: Ubuntu 18.04 (08.04.2018 updated) PC: Dell inspiron n5110 laptop CPU: intel i7 2630QM GPU: nvidia gt 525m *** I installed latest nvidia driver, but driver detects 2 screen. bad thing is gdm, i can't see gdm greeter only purple background. greeter in primary(unknown) screen Please check screenshot *** U1804PC:~$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 525M] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 05) 09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34) 0b:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) U1804PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1762200/+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 1765726] Re: libgoo-canvas-perl [needs-packaging]
** Package changed: ubuntu-meta (Ubuntu) => ubuntu -- 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/1765726 Title: libgoo-canvas-perl [needs-packaging] Status in Ubuntu: Confirmed Bug description: The ability to edit screenshots using shutter has been broken because Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its repository anymore: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 09:05:10 2018 InstallationDate: Installed on 2018-04-17 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1765726/+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 1765745] Re: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()
*** This bug is a duplicate of bug 1690935 *** https://bugs.launchpad.net/bugs/1690935 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1690935, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765745/+attachment/5123910/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765745/+attachment/5123913/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765745/+attachment/5123920/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765745/+attachment/5123922/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765745/+attachment/5123923/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765745/+attachment/5123924/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765745/+attachment/5123925/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1690935 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1765745 Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash() Status in systemd package in Ubuntu: New Bug description: Killed system and rebooted, because it woke up unusable from suspend. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Fri Apr 20 10:50:59 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-04-05 (14 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=/dev/mapper/ubuntu--vg-root ro Signal: 6 SourcePackage: systemd StacktraceTop: journal_file_find_data_object_with_hash () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/ureadahead.service → /etc/systemd/system/ureadahead.service.d/quiet.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: Z97 Anniversary dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd05/12/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Anniversary:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765745/+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 1765726] Re: libgoo-canvas-perl [needs-packaging]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1765726 Title: libgoo-canvas-perl [needs-packaging] Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The ability to edit screenshots using shutter has been broken because Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its repository anymore: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 09:05:10 2018 InstallationDate: Installed on 2018-04-17 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1765726/+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 1765230] Re: Immediate logout when using Chrome (and not only it)
The bug was in the Amdgpu-pro drivers. Uninstalled them, and the problem disappeared. -- 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/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 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/xorg/+bug/1765230/+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 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start
I am finding something possibly related (as are a few that have posted on Reddit). After update I can boot but I get 'welcome to ubuntu' screen and everything freezes. I can press enter to get through the welcome wizard but after that nothing works except the mouse pointer. Boring into Wayland doesn't work either. I can Alt F3 and login to a terminal. Could someone advise me what to do from here so I can provide a log. Ian -- 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/1765724 Title: Xenial -> Bionic - System fails to boot after upgrade - systemd- cryptsetup@cryptswap1.service fails to start Status in cryptsetup package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Test Case: 1. Install Xenial Desktop with encrypted home 2. Upgrade to bionic 3. Reboot Actual Result The system hangs on boot when it activates the encrypted swap. There are the following entries in the journal: $ journalctl -b-1 -o short-monotonic |grep crypt [1.535326] ubuntu kernel: Key type encrypted registered [ 125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. [ 125.637789] ubuntu systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. [ 125.638311] ubuntu systemd[1]: Dependency failed for /dev/mapper/cryptswap1. [ 125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. [ 125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. [ 125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted Volumes. [ 125.640128] ubuntu systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. [ 125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. [ 383.902153] ubuntu systemd[1]: Starting Cryptography Setup for cryptswap1... [ 383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b. [ 384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1. [ 384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes. [ 384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1. [ 384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1... [ 384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. Priority:-2 extents:1 across:2093564k FS [ 384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:2.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 15:56:52 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-18 (2 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+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 1765726] Re: libgoo-canvas-perl [needs-packaging]
sudo apt-get install shutter If you launch shutter from the command line it notifies these warnings: WARNING: Goo::Canvas/libgoo-canvas-perl is missing --> drawing tool will be disabled! WARNING: Image::ExifTool is missing --> writing Exif information will be disabled! WARNING: Gtk2::AppIndicator is missing --> there will be no icon showing up in the status bar when running Unity! -- 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/1765726 Title: libgoo-canvas-perl [needs-packaging] Status in ubuntu-meta package in Ubuntu: New Bug description: The ability to edit screenshots using shutter has been broken because Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its repository anymore: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 09:05:10 2018 InstallationDate: Installed on 2018-04-17 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1765726/+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 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start
** Changed in: cryptsetup (Ubuntu) Importance: Undecided => Critical -- 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/1765724 Title: Xenial -> Bionic - System fails to boot after upgrade - systemd- cryptsetup@cryptswap1.service fails to start Status in cryptsetup package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Test Case: 1. Install Xenial Desktop with encrypted home 2. Upgrade to bionic 3. Reboot Actual Result The system hangs on boot when it activates the encrypted swap. There are the following entries in the journal: $ journalctl -b-1 -o short-monotonic |grep crypt [1.535326] ubuntu kernel: Key type encrypted registered [ 125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. [ 125.637789] ubuntu systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. [ 125.638311] ubuntu systemd[1]: Dependency failed for /dev/mapper/cryptswap1. [ 125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. [ 125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. [ 125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted Volumes. [ 125.640128] ubuntu systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. [ 125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. [ 383.902153] ubuntu systemd[1]: Starting Cryptography Setup for cryptswap1... [ 383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b. [ 384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1. [ 384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes. [ 384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1. [ 384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1... [ 384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. Priority:-2 extents:1 across:2093564k FS [ 384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:2.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 15:56:52 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-18 (2 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+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 1765726] [NEW] libgoo-canvas-perl [needs-packaging]
Public bug reported: The ability to edit screenshots using shutter has been broken because Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its repository anymore: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 09:05:10 2018 InstallationDate: Installed on 2018-04-17 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic needs-packaging -- 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/1765726 Title: libgoo-canvas-perl [needs-packaging] Status in ubuntu-meta package in Ubuntu: New Bug description: The ability to edit screenshots using shutter has been broken because Ubuntu 18.04 does not provide the libgoo-canvas-perl package in its repository anymore: https://bugs.launchpad.net/ubuntu/+source/shutter/+bug/1760023 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 09:05:10 2018 InstallationDate: Installed on 2018-04-17 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1765726/+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 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start
Similar to bug 1736072 Note that in the fstab attached I commented out the swap entry to allow the system to boot. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1765724 Title: Xenial -> Bionic - System fails to boot after upgrade - systemd- cryptsetup@cryptswap1.service fails to start Status in cryptsetup package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Test Case: 1. Install Xenial Desktop with encrypted home 2. Upgrade to bionic 3. Reboot Actual Result The system hangs on boot when it activates the encrypted swap. There are the following entries in the journal: $ journalctl -b-1 -o short-monotonic |grep crypt [1.535326] ubuntu kernel: Key type encrypted registered [ 125.637205] ubuntu systemd[1]: Dependency failed for Cryptography Setup for cryptswap1. [ 125.637789] ubuntu systemd[1]: Dependency failed for dev-mapper-cryptswap1.device. [ 125.638311] ubuntu systemd[1]: Dependency failed for /dev/mapper/cryptswap1. [ 125.639351] ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'. [ 125.639478] ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'dependency'. [ 125.639594] ubuntu systemd[1]: Dependency failed for Local Encrypted Volumes. [ 125.640128] ubuntu systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'. [ 125.640266] ubuntu systemd[1]: systemd-cryptsetup@cryptswap1.service: Job systemd-cryptsetup@cryptswap1.service/start failed with result 'dependency'. [ 383.902153] ubuntu systemd[1]: Starting Cryptography Setup for cryptswap1... [ 383.913899] ubuntu systemd-cryptsetup[672]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-uuid/34ea85fd-854b-4892-95b9-7073dd2dbf7b. [ 384.138596] ubuntu systemd[1]: Started Cryptography Setup for cryptswap1. [ 384.143845] ubuntu systemd[1]: Reached target Local Encrypted Volumes. [ 384.167475] ubuntu systemd[1]: Found device /dev/mapper/cryptswap1. [ 384.171327] ubuntu systemd[1]: Activating swap /dev/mapper/cryptswap1... [ 384.184639] ubuntu kernel: Adding 2093564k swap on /dev/mapper/cryptswap1. Priority:-2 extents:1 across:2093564k FS [ 384.191435] ubuntu systemd[1]: Activated swap /dev/mapper/cryptswap1. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cryptsetup 2:2.0.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 15:56:52 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-04-18 (2 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: Upgraded to bionic on 2018-04-20 (0 days ago) cmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=ba774fed-a987-4070-9571-0e4790b08680 ro recovery nomodeset crypttab: cryptswap1 UUID=34ea85fd-854b-4892-95b9-7073dd2dbf7b /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+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 1765463] Re: Bionic: systemd: rename interface
the fault was somewhere else, this issue can be closed -- 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/1765463 Title: Bionic: systemd: rename interface Status in systemd package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/netword/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+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 1762200] Re: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable
** Summary changed: - [xorg.conf missing]nvidia detects 2 screen but there is no 2 screen + [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable ** Description changed: System: Ubuntu 18.04 (08.04.2018 updated) PC: Dell inspiron n5110 laptop CPU: intel i7 2630QM GPU: nvidia gt 525m + *** - i installed latest nvidia driver, but driver detects 2 screen. bad thing is gdm, i can't see gdm dialogs only purple background. dialogs in primary(unknown) screen - pls check screenshot + I installed latest nvidia driver, but driver detects 2 screen. bad thing is gdm, i can't see gdm greeter only purple background. greeter in primary(unknown) screen + Please check screenshot + *** U1804PC:~$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 525M] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF108 High Definition Audio Controller (rev a1) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 05) 09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 [Rainbow Peak] (rev 34) 0b:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) U1804PC:~$ -- 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/1762200 Title: [xorg.conf/nvidia-prime missing] Nvidia detects 2 screen, It makes ubuntu unusable Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: System: Ubuntu 18.04 (08.04.2018 updated) PC: Dell inspiron n5110 laptop CPU: intel i7 2630QM GPU: nvidia gt 525m *** I installed latest nvidia driver, but driver detects 2 screen. bad thing is gdm, i can't see gdm greeter only purple background. greeter in primary(unknown) screen Please check screenshot *** U1804PC:~$ lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Se
[Touch-packages] [Bug 1765463] Re: Bionic: systemd: rename interface
Can you please elaborate? If one puts .link files in /etc/systemd/network, they should be copied into the initramfs, and they should results in the correct interface renames in the initramfs. Once the typo was corrected (not sure if on the system, or it was in the bug description only), was everything working fine? Or is it still a bug that .link files from /etc are not getting picked up into the initramfs for you? -- 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/1765463 Title: Bionic: systemd: rename interface Status in systemd package in Ubuntu: Invalid Bug description: 1) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) apt-cache policy systemd systemd: Installed: 237-3ubuntu8 3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18 /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" /etc/systemd/netword/uplink0.link [Match] Path=pci-:02:00.0 [Link] Name=uplink0 # update-initramfs -u 4) journalctl -b | grep rename kernel: tg3 :02:00.1 eno2: renamed from eth1 kernel: tg3 :02:00.0 eno1: renamed from eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+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 1733597] Re: "gio open" handles mailto: links wrong, putting /// at the start of the email address
** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1733597 Title: "gio open" handles mailto: links wrong, putting /// at the start of the email address Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: "gio open mailto:user@host"; results in gio executing "thunderbird mailto:///user@host";, which is wrong and causes the address that shows up in the thunderbird composition window to start with three slashes when it shouldn't. Proof, from "strace gio open mailto:user@host"; output: 16976 execve("/usr/bin/gio", ["gio", "open", "mailto:user@host";], [/* 76 vars */]) = 0 16980 execve("/usr/bin/thunderbird", ["thunderbird", "mailto:///user@host";], [/* 78 vars */] ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libglib2.0-bin 2.54.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 08:39:42 2017 InstallationDate: Installed on 2017-05-19 (185 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: glib2.0 UpgradeStatus: Upgraded to artful on 2017-10-20 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1733597/+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 1765704] [NEW] bug in application menu icon in terminal
Public bug reported: /home/initu/Imagens/Captura de tela de 2018-04-19 18-23-01.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 10:06:27 2018 InstallationDate: Installed on 2018-04-06 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1765704 Title: bug in application menu icon in terminal Status in ubuntu-themes package in Ubuntu: New Bug description: /home/initu/Imagens/Captura de tela de 2018-04-19 18-23-01.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 10:06:27 2018 InstallationDate: Installed on 2018-04-06 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765704/+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 1765704] Re: bug in application menu icon in terminal
/home/initu/Imagens/Captura de tela de 2018-04-19 18-23-01.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1765704 Title: bug in application menu icon in terminal Status in ubuntu-themes package in Ubuntu: New Bug description: /home/initu/Imagens/Captura de tela de 2018-04-19 18-23-01.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 10:06:27 2018 InstallationDate: Installed on 2018-04-06 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765704/+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 1765704] Re: bug in application menu icon in terminal
** Attachment added: "Captura de tela de 2018-04-19 18-23-01.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765704/+attachment/5123758/+files/Captura%20de%20tela%20de%202018-04-19%2018-23-01.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1765704 Title: bug in application menu icon in terminal Status in ubuntu-themes package in Ubuntu: New Bug description: /home/initu/Imagens/Captura de tela de 2018-04-19 18-23-01.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 10:06:27 2018 InstallationDate: Installed on 2018-04-06 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1765704/+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 135063] Re: wget --quiet --background leaves a wget.log file
** Summary changed: - wget --quite --background leaves a wget.log file + wget --quiet --background leaves a wget.log file ** Description changed: Binary package hint: wget - wget --quite --background leaves a 0 byte wget.log file + wget --quiet --background leaves a 0 byte wget.log file it is no supposed once the quiet parameter is entered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/135063 Title: wget --quiet --background leaves a wget.log file Status in wget: Unknown Status in wget package in Ubuntu: Fix Released Bug description: Binary package hint: wget wget --quiet --background leaves a 0 byte wget.log file it is no supposed once the quiet parameter is entered. To manage notifications about this bug go to: https://bugs.launchpad.net/wget/+bug/135063/+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 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
I think that time is past, we were in beta freeze in the past week, and are in final freeze now. Unless there is a clear test case showing under which conditions this happens and how widespread it is, it's probably best to start thinking in SRU terms. It looks like a safe change, but since I don't understand the problem entirely yet (when it happens, why), I can't say. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Confirmed Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Bug description: On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+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@lists.launchpad.net
Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1484411 "Running wget with -O and -q in the background yields a file wget-log" Related but (FWICT) not precisely the same issues upstream: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888691 "wget -b produces empty wget-log file" * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874590 "wget: creates log file when run in the background", forwarded to https://savannah.gnu.org/bugs/?51181 "Unexpected "Redirecting output to 'wget-log'."" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1765690 Title: wget-log file created despite -q when run in background with & Status in wget package in Ubuntu: New Bug description: == Steps to reproduce == `wget -q https://www.google.com/ &` == What happens == wget says it's "Redirecting output to 'wget-log'" and creates an empty wget-log file in the current directory. == What I expect to happen == No wget-log file to be created. == Details == Wget has a -b (--background) option, for which the man page says: "If no output file is specified via the -o, output is redirected to wget-log." There's also the -q (--quiet) option, for which the man page says: "Turn off Wget's output." When both are given, wget goes to background, and no wget-log gets created, as expected. When only -b is given, wget goes to background, and creates wget-log, also as expected. When only -q is given, wget runs in the foreground, and no wget-log is created, still as expected. When only -q is given, but & is added to the end of the command line, wget goes to background, but also creates wget-log, which I find unexpected (and inconsistent). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: wget 1.19.4-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 14:56:17 2018 InstallationDate: Installed on 2016-10-13 (553 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1765690/+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@lists.launchpad.net
Public bug reported: == Steps to reproduce == `wget -q https://www.google.com/ &` == What happens == wget says it's "Redirecting output to 'wget-log'" and creates an empty wget-log file in the current directory. == What I expect to happen == No wget-log file to be created. == Details == Wget has a -b (--background) option, for which the man page says: "If no output file is specified via the -o, output is redirected to wget-log." There's also the -q (--quiet) option, for which the man page says: "Turn off Wget's output." When both are given, wget goes to background, and no wget-log gets created, as expected. When only -b is given, wget goes to background, and creates wget-log, also as expected. When only -q is given, wget runs in the foreground, and no wget-log is created, still as expected. When only -q is given, but & is added to the end of the command line, wget goes to background, but also creates wget-log, which I find unexpected (and inconsistent). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: wget 1.19.4-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 14:56:17 2018 InstallationDate: Installed on 2016-10-13 (553 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Red Hat Bugzilla #1484411 https://bugzilla.redhat.com/show_bug.cgi?id=1484411 ** Bug watch added: Debian Bug tracker #888691 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888691 ** Bug watch added: Debian Bug tracker #874590 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874590 ** Bug watch added: GNU Savannah Bug Tracker #51181 http://savannah.gnu.org/bugs/?51181 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1765690 Title: wget-log file created despite -q when run in background with & Status in wget package in Ubuntu: New Bug description: == Steps to reproduce == `wget -q https://www.google.com/ &` == What happens == wget says it's "Redirecting output to 'wget-log'" and creates an empty wget-log file in the current directory. == What I expect to happen == No wget-log file to be created. == Details == Wget has a -b (--background) option, for which the man page says: "If no output file is specified via the -o, output is redirected to wget-log." There's also the -q (--quiet) option, for which the man page says: "Turn off Wget's output." When both are given, wget goes to background, and no wget-log gets created, as expected. When only -b is given, wget goes to background, and creates wget-log, also as expected. When only -q is given, wget runs in the foreground, and no wget-log is created, still as expected. When only -q is given, but & is added to the end of the command line, wget goes to background, but also creates wget-log, which I find unexpected (and inconsistent). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: wget 1.19.4-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 14:56:17 2018 InstallationDate: Installed on 2016-10-13 (553 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1765690/+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 1764494] Re: X fails to start upon boot
** Package changed: xorg (Ubuntu) => sddm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1764494 Title: X fails to start upon boot Status in sddm package in Ubuntu: New Bug description: $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu6 The system is an upgrade from 17.10 to 18.04. The X-server fails to start initially, on each boot. After switching to tty2 I can start the login daemon via $ systemctl start sddm and X and sddm work as expected. (i.e. X starts, the login daemon starts, I can login to an X session) The system in question is a Lenovo X220 Thinkpad with integrated graphics. As lspci puts it: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) This behaviour started as a result of the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1764494/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
Xenial verification: ubuntu@lp1447715:/etc/network/interfaces.d$ dpkg -l | grep ifupdown ii ifupdown 0.8.10ubuntu1.2 amd64high level tools to configure network interfaces ubuntu@lp1447715:/etc/network/interfaces.d$ grep -A 2 ens7 50-cloud-init.cfg auto ens7 iface ens7 inet6 auto dhcp 1 ubuntu@lp1447715:/etc/network/interfaces.d$ sudo ip l show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:b0:86:a5 brd ff:ff:ff:ff:ff:ff ubuntu@lp1447715:/etc/network/interfaces.d$ sudo ifup -v ens7 Parsing file /etc/network/interfaces.d/50-cloud-init.cfg Configuring interface ens7=ens7 (inet6) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/ifenslave + [ inet6 = meta ] + IF_BOND_SLAVES= + [ ] + [ ] + [ -z ] + exit run-parts: executing /etc/network/if-pre-up.d/vlan /sbin/modprobe -q net-pf-10 > /dev/null 2>&1 || true # ignore failure. /sbin/sysctl -q -e -w net.ipv6.conf.ens7.accept_ra=2 /sbin/sysctl -q -e -w net.ipv6.conf.ens7.autoconf=1 /bin/ip link set dev ens7 up /lib/ifupdown/wait-for-ll6.sh /sbin/dhclient -1 -6 -S -pf /run/dhclient6.ens7.pid -lf /var/lib/dhcp/dhclient6.ens7.leases -I -df /var/lib/dhcp/dhclient.ens7.leases ens7 Failed to bring up ens7. ubuntu@lp1447715:/etc/network/interfaces.d$ dpkg -l | grep ifupdown ii ifupdown 0.8.10ubuntu1.3 amd64high level tools to configure network interfaces ubuntu@lp1447715:/etc/network/interfaces.d$ grep -A 2 ens7 50-cloud-init.cfg auto ens7 iface ens7 inet6 auto dhcp 1 ubuntu@lp1447715:/etc/network/interfaces.d$ sudo ip l show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:b0:86:a5 brd ff:ff:ff:ff:ff:ff ubuntu@lp1447715:/etc/network/interfaces.d$ sudo ifup -v ens7 Parsing file /etc/network/interfaces.d/50-cloud-init.cfg Configuring interface ens7=ens7 (inet6) /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/ethtool run-parts: executing /etc/network/if-pre-up.d/ifenslave + [ inet6 = meta ] + IF_BOND_SLAVES= + [ ] + [ ] + [ -z ] + exit run-parts: executing /etc/network/if-pre-up.d/vlan /sbin/modprobe -q net-pf-10 > /dev/null 2>&1 || true # ignore failure. /sbin/sysctl -q -e -w net.ipv6.conf.ens7.accept_ra=2 /sbin/sysctl -q -e -w net.ipv6.conf.ens7.autoconf=1 /bin/ip link set dev ens7 up /lib/ifupdown/wait-for-ll6.sh /sbin/dhclient -1 -6 -S -pf /run/dhclient6.ens7.pid -lf /var/lib/dhcp/dhclient6.ens7.leases -I -df /var/lib/dhcp/dhclient.ens7.leases ens7 /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/000resolvconf run-parts: executing /etc/network/if-up.d/ethtool run-parts: executing /etc/network/if-up.d/ifenslave + [ inet6 = meta ] + [ ] run-parts: executing /etc/network/if-up.d/ip run-parts: executing /etc/network/if-up.d/openssh-server run-parts: executing /etc/network/if-up.d/upstart verified. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial ** Tags removed: sts-sponsor ** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Fix Committed Status in ifupdown package in Debian: Fix Released Bug description: [Impact] When using dhcpv6 configured via ifupdown, the interface's dhcp client fails to start at boot with the error: Can't bind to dhcp address: Cannot assign requested address This is because ifupdown doesn't wait, after bringing the interface up, for it to complete its link-local Duplicate Address Detection (DAD), and the dhcp client can't bind to the link-local address because it's still in "tentative" state (until DAD completes). This is fixed upstream in debian ifupdown in version 0.8.11 by adding '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the script was only waiting for the link-local address to appear, now it waits until the link-local address appears and is not in 'tentative' state. [Test Case] Original test case, before dhclient was fixed: Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 dhcp) and reboot. It will fail to get a dhcp address during boot. New test case, showing failure when using dhclient in 'stateless' mode: Configure ifupdown like: auto eth0 iface eth0 inet6 auto dhcp 1 When eth0 is down, run 'sudo ifup eth0', and i
[Touch-packages] [Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
** Package changed: glib (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1707451 Title: udisksd crashed with SIGSEGV in g_mutex_lock() Status in udisks: New Status in glib2.0 package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Fix Released Bug description: Showed up after login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sun Jul 30 00:35:31 2017 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2017-06-22 (37 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170622) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f4900fb5c65 : lock xadd %eax,(%rdi) PC (0x7f4900fb5c65) ok source "%eax" ok destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: Z87 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1707451/+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 1748321] Re: Sort order is bizarre, and can not be changed
** Package changed: glib (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1748321 Title: Sort order is bizarre, and can not be changed Status in GLib: Confirmed Status in glib2.0 package in Ubuntu: Triaged Status in gnome-desktop3 package in Ubuntu: Invalid Bug description: Create some test files as follows: $ touch 0110-0.jpg 0110-A.jpg 01A00010-0.jpg 03BBF000-0.jpg 3bA1A000-0.jpg 3BD22000-0.jpg A4AC3000-0.jpg 00011 00011.jpg 00021 View them at the command line and in Nautilus: $ ls -1 0110-0.jpg 0110-A.jpg 01A00010-0.jpg 03BBF000-0.jpg 3bA1A000-0.jpg 3BD22000-0.jpg A4AC3000-0.jpg 00011 00011.jpg 00021 $ nautilus . ls sorts files as one might expect. It is not case sensitive (unless you use a case sensitive locale, e.g. LANG=C), but sorts alphabetically. Nautilus sorts the files in a bizarre order, regardless of which locale is used. Weird behaviours include: * Longer but otherwise equal filenames sort before shorter ones * Sometimes ignores runs of zeros, but not punctuation * Seems to detect runs of digits and sort them at the end The actual behaviour is very complex and difficult to predict, though it must follow some internal logic. The end result is that files don't sort in any reasonable order. This also impacts some other applications, such as Eye of Gnome. Others, like Transmission, respect locale. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-desktop3-data 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 9 10:39:25 2018 Dependencies: InstallationDate: Installed on 2016-12-02 (432 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: gnome-desktop3 UpgradeStatus: Upgraded to artful on 2017-10-12 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1748321/+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 1707451] [NEW] udisksd crashed with SIGSEGV in g_mutex_lock()
You have been subscribed to a public bug: Showed up after login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sun Jul 30 00:35:31 2017 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2017-06-22 (37 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170622) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f4900fb5c65 : lock xadd %eax,(%rdi) PC (0x7f4900fb5c65) ok source "%eax" ok destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: Z87 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: udisks Importance: Unknown Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: udisks2 (Ubuntu) Importance: High Assignee: Andrea Azzarone (azzar1) Status: Fix Released ** Tags: amd64 apport-crash artful bionic bugpattern-needed -- udisksd crashed with SIGSEGV in g_mutex_lock() https://bugs.launchpad.net/bugs/1707451 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748321] [NEW] Sort order is bizarre, and can not be changed
You have been subscribed to a public bug: Create some test files as follows: $ touch 0110-0.jpg 0110-A.jpg 01A00010-0.jpg 03BBF000-0.jpg 3bA1A000-0.jpg 3BD22000-0.jpg A4AC3000-0.jpg 00011 00011.jpg 00021 View them at the command line and in Nautilus: $ ls -1 0110-0.jpg 0110-A.jpg 01A00010-0.jpg 03BBF000-0.jpg 3bA1A000-0.jpg 3BD22000-0.jpg A4AC3000-0.jpg 00011 00011.jpg 00021 $ nautilus . ls sorts files as one might expect. It is not case sensitive (unless you use a case sensitive locale, e.g. LANG=C), but sorts alphabetically. Nautilus sorts the files in a bizarre order, regardless of which locale is used. Weird behaviours include: * Longer but otherwise equal filenames sort before shorter ones * Sometimes ignores runs of zeros, but not punctuation * Seems to detect runs of digits and sort them at the end The actual behaviour is very complex and difficult to predict, though it must follow some internal logic. The end result is that files don't sort in any reasonable order. This also impacts some other applications, such as Eye of Gnome. Others, like Transmission, respect locale. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-desktop3-data 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Feb 9 10:39:25 2018 Dependencies: InstallationDate: Installed on 2016-12-02 (432 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: gnome-desktop3 UpgradeStatus: Upgraded to artful on 2017-10-12 (119 days ago) ** Affects: glib Importance: Medium Status: Confirmed ** Affects: glib2.0 (Ubuntu) Importance: Low Status: Triaged ** Affects: gnome-desktop3 (Ubuntu) Importance: Low Status: Invalid ** Tags: amd64 apport-bug artful wayland-session -- Sort order is bizarre, and can not be changed https://bugs.launchpad.net/bugs/1748321 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
It didn't help here either, I've deleted it back when I filed this bug originally. FWIW, mine is also an upgrade, at least two releases back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+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 1756506] Re: snd_hda_intel module rejected by new kernel with retpoline
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: virtualbox (Ubuntu) Status: New => Confirmed -- 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/1756506 Title: snd_hda_intel module rejected by new kernel with retpoline Status in alsa-driver package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: After a routine software update (which updated the kernel) alsa recognises no sound card although lspci reports an audio device: Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04). $ uname -a Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ aplay -l aplay: device_list:268: no soundcards found... $ dmesg | grep snd [4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1756506/+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 1756506] Re: snd_hda_intel module rejected by new kernel with retpoline
** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1756506 Title: snd_hda_intel module rejected by new kernel with retpoline Status in alsa-driver package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: After a routine software update (which updated the kernel) alsa recognises no sound card although lspci reports an audio device: Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04). $ uname -a Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ aplay -l aplay: device_list:268: no soundcards found... $ dmesg | grep snd [4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1756506/+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 1765649] Re: package libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/li
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpng in Ubuntu. https://bugs.launchpad.net/bugs/1765649 Title: package libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/libpng12-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpng12-0/KNOWNBUG', which is different from other instances of package libpng12-0:i386 Status in libpng package in Ubuntu: New Bug description: This bug appeared when I was trying to install teamviewer which doesn't work. There are some dependencies that break the installation. Then I tried to remove teamviewer: sudo apt-get remove teamviewer Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: libpng12-0 : Breaks: libpng12-0:i386 (!= 1.2.54-1ubuntu1) but 1.2.50-2+deb8u3 is to be installed libpng12-0:i386 : Depends: libc6:i386 (>= 2.11) but it is not going to be installed Depends: zlib1g:i386 (>= 1:1.1.4) but it is not going to be installed Breaks: libpng12-0 (!= 1.2.50-2+deb8u3) but 1.2.54-1ubuntu1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). Then as suggested I tried: sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: gcc-6-base:i386 libc6:i386 libgcc1:i386 libpng12-0:i386 zlib1g:i386 Suggested packages: glibc-doc:i386 locales:i386 The following packages will be REMOVED: teamviewer The following NEW packages will be installed: gcc-6-base:i386 libc6:i386 libgcc1:i386 zlib1g:i386 The following packages will be upgraded: libpng12-0:i386 1 upgraded, 4 newly installed, 1 to remove and 210 not upgraded. 3 not fully installed or removed. Need to get 2.501 kB of archives. After this operation, 142 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 gcc-6-base i386 6.0.1-0ubuntu1 [14,3 kB] Get:2 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 libgcc1 i386 1:6.0.1-0ubuntu1 [46,8 kB] Get:3 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 libc6 i386 2.23-0ubuntu10 [2.266 kB] Get:4 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 zlib1g i386 1:1.2.8.dfsg-2ubuntu4.1 [52,1 kB] Get:5 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 libpng12-0 i386 1.2.54-1ubuntu1 [122 kB] Fetched 2.501 kB in 0s (4.625 kB/s) Preconfiguring packages ... (Reading database ... 253717 files and directories currently installed.) Removing teamviewer (12.0.93330) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.59ubuntu1) ... (Reading database ... 253416 files and directories currently installed.) Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_i386.deb ... Unpacking libpng12-0:i386 (1.2.54-1ubuntu1) over (1.2.50-2+deb8u3) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/KNOWNBUG', which is different from other instances of package libpng12-0:i386 Selecting previously unselected package gcc-6-base:i386. Preparing to unpack .../gcc-6-base_6.0.1-0ubuntu1_i386.deb ... Unpacking gcc-6-base:i386 (6.0.1-0ubuntu1) ... Selecting previously unselected package libgcc1:i386. Preparing to unpack .../libgcc1_1%3a6.0.1-0ubuntu1_i386.deb ... Unpacking libgcc1:i386 (1:6.0.1-0ubuntu1) ... Selecting previously unselected package libc6:i386. Preparing to unpack .../libc6_2.23-0ubuntu10_i386.deb ... Unpacking libc6:i386 (2.23-0ubuntu10) ... Replacing files in old package libc6-i386 (2.23-0ubuntu10) ... Selecting previously unselected package zlib1g:i386. Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_i386.deb ... Unpacking zlib1g:i386 (1:1.2.8.dfsg-2ubuntu4.1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.54-1ubuntu1 [
[Touch-packages] [Bug 1765649] [NEW] package libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/
Public bug reported: This bug appeared when I was trying to install teamviewer which doesn't work. There are some dependencies that break the installation. Then I tried to remove teamviewer: sudo apt-get remove teamviewer Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: libpng12-0 : Breaks: libpng12-0:i386 (!= 1.2.54-1ubuntu1) but 1.2.50-2+deb8u3 is to be installed libpng12-0:i386 : Depends: libc6:i386 (>= 2.11) but it is not going to be installed Depends: zlib1g:i386 (>= 1:1.1.4) but it is not going to be installed Breaks: libpng12-0 (!= 1.2.50-2+deb8u3) but 1.2.54-1ubuntu1 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). Then as suggested I tried: sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: gcc-6-base:i386 libc6:i386 libgcc1:i386 libpng12-0:i386 zlib1g:i386 Suggested packages: glibc-doc:i386 locales:i386 The following packages will be REMOVED: teamviewer The following NEW packages will be installed: gcc-6-base:i386 libc6:i386 libgcc1:i386 zlib1g:i386 The following packages will be upgraded: libpng12-0:i386 1 upgraded, 4 newly installed, 1 to remove and 210 not upgraded. 3 not fully installed or removed. Need to get 2.501 kB of archives. After this operation, 142 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 gcc-6-base i386 6.0.1-0ubuntu1 [14,3 kB] Get:2 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 libgcc1 i386 1:6.0.1-0ubuntu1 [46,8 kB] Get:3 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 libc6 i386 2.23-0ubuntu10 [2.266 kB] Get:4 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 zlib1g i386 1:1.2.8.dfsg-2ubuntu4.1 [52,1 kB] Get:5 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 libpng12-0 i386 1.2.54-1ubuntu1 [122 kB] Fetched 2.501 kB in 0s (4.625 kB/s) Preconfiguring packages ... (Reading database ... 253717 files and directories currently installed.) Removing teamviewer (12.0.93330) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ... Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ... Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.59ubuntu1) ... (Reading database ... 253416 files and directories currently installed.) Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_i386.deb ... Unpacking libpng12-0:i386 (1.2.54-1ubuntu1) over (1.2.50-2+deb8u3) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpng12-0/KNOWNBUG', which is different from other instances of package libpng12-0:i386 Selecting previously unselected package gcc-6-base:i386. Preparing to unpack .../gcc-6-base_6.0.1-0ubuntu1_i386.deb ... Unpacking gcc-6-base:i386 (6.0.1-0ubuntu1) ... Selecting previously unselected package libgcc1:i386. Preparing to unpack .../libgcc1_1%3a6.0.1-0ubuntu1_i386.deb ... Unpacking libgcc1:i386 (1:6.0.1-0ubuntu1) ... Selecting previously unselected package libc6:i386. Preparing to unpack .../libc6_2.23-0ubuntu10_i386.deb ... Unpacking libc6:i386 (2.23-0ubuntu10) ... Replacing files in old package libc6-i386 (2.23-0ubuntu10) ... Selecting previously unselected package zlib1g:i386. Preparing to unpack .../zlib1g_1%3a1.2.8.dfsg-2ubuntu4.1_i386.deb ... Unpacking zlib1g:i386 (1:1.2.8.dfsg-2ubuntu4.1) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Errors were encountered while processing: /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/libpng12-0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Apr 20 12:30:39 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DpkgTerminalLog: Preparing to unpack .../libpng12-0_1.2.54-1ubuntu1_i386.deb ... Unpacking libpng12-0:i386 (1.2.54-1ubuntu1) over (1.2.50-2+deb8u3) ... dpkg: error processing archive /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.
[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
** Changed in: clutter-gst-3.0 (Ubuntu) Status: In Progress => Incomplete ** Changed in: gstreamer-vaapi (Ubuntu) Status: In Progress => Incomplete -- 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/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GStreamer: Confirmed Status in GTK+: Fix Released Status in totem-pl-parser: Confirmed Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gst-3.0 package in Ubuntu: Incomplete Status in clutter-gtk package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Fix Released Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1698270/+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 1756506] Re: snd_hda_intel module rejected by new kernel with retpoline
Similar issue observed with the drivers supplied with virtualbox guest additions in Ubuntu 14.04 after a regular upgrade (running the same kernel as mentioned in previous post). $ gmesg | grep vbox [ 32.576197] vboxguest: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' As it turns out the virtualbox drivers are not supplied as binary .ko files in Ubuntu, their compiled during the installation using 'dkms', which uses the virtualbox driver source from the guest additions package and the kernel headers. During this step the drivers don't get the correct vermagic string. $ modinfo /lib/modules/3.13.0-143-generic/updates/dkms/vboxsf.ko filename: /lib/modules/3.13.0-143-generic/updates/dkms/vboxsf.ko version:4.3.36_Ubuntu (interface 0x00010004) license:GPL author: Oracle Corporation description:Oracle VM VirtualBox VFS Module for Host File System Access srcversion: D5BC8E0A67B7E89277BCEA9 depends:vboxguest vermagic: 3.13.0-143-generic SMP mod_unload modversions parm: follow_symlinks:Let host resolve symlinks rather than showing them (int) During compilation the /usr/src/linux- headers-3.13.0-142-generic/include/linux/vermagic.h file is used to generate the vermagic string, which includes /usr/src/linux- headers-3.13.0-143-generic/include/generated/utsrelease.h. After adding a RETPOLINE define to this header file and recompiling the drivers the problems looks solved. The steps are described below. (as root) $ echo "#define RETPOLINE 1" >> /usr/src/linux-headers-3.13.0-143-generic/include/generated/utsrelease.h $ dkms remove virtualbox-guest/4.3.36 -k 3.13.0-144-generic $ dkms install virtualbox-guest/4.3.36 -k 3.13.0-144-generic It looks like the linux-headers-3.13.0-143-generic package needs an update to fix the utsrelease.h file (which seems generated too?). This problem most likely has impact on all drivers which are created with the 'dkms' tool. -- 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/1756506 Title: snd_hda_intel module rejected by new kernel with retpoline Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a routine software update (which updated the kernel) alsa recognises no sound card although lspci reports an audio device: Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04). $ uname -a Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ aplay -l aplay: device_list:268: no soundcards found... $ dmesg | grep snd [4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1756506/+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 1764494] Re: X fails to start upon boot
It seems to be an interaction with plymouth. Setting `GRUB_CMDLINE_LINUX_DEFAULT="quiet"` i.e. removing the `splash` in /etc/default/grub and updating grub $ sudo update-grub works around the problem. -- 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/1764494 Title: X fails to start upon boot Status in xorg package in Ubuntu: New Bug description: $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu6 The system is an upgrade from 17.10 to 18.04. The X-server fails to start initially, on each boot. After switching to tty2 I can start the login daemon via $ systemctl start sddm and X and sddm work as expected. (i.e. X starts, the login daemon starts, I can login to an X session) The system in question is a Lenovo X220 Thinkpad with integrated graphics. As lspci puts it: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) This behaviour started as a result of the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764494/+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 1752417] Re: [ffe] including network-manager-openvpn-gnome and network-manager-strongswan in the default installation
** Summary changed: - [ffe] including network-manager-openvpn-gnome in the default installation + [ffe] including network-manager-openvpn-gnome and network-manager-strongswan in the default installation ** Summary changed: - [ffe] including network-manager-openvpn-gnome and network-manager-strongswan in the default installation + [ffe] including network-manager-openvpn* and network-manager-strongswan in the default installation ** Summary changed: - [ffe] including network-manager-openvpn* and network-manager-strongswan in the default installation + [ffe] including network-manager-openvpn-gnome and network-manager-strongswan in the default installation ** Summary changed: - [ffe] including network-manager-openvpn-gnome and network-manager-strongswan in the default installation + [ffe] including network-manager-openvpn-gnome, network-manager-l2tp-gnome, and network-manager-strongswan in the default installation -- 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/1752417 Title: [ffe] including network-manager-openvpn-gnome, network-manager-l2tp- gnome, and network-manager-strongswan in the default installation Status in network-manager package in Ubuntu: Triaged Status in network-manager-openvpn package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: network-manager lists only PPTP as an available VPN client connection type (and also offers to import a file). I'd expect L2TP-over-IPSec and IKEv1/IKEv2 options as well. In fact, most major desktop OSes have removed PPTP altogether because it's insecure, and Ubuntu should probably do so in 18.04 as well, at least from the GUI! $ apt list network-manager Llistant… Fet network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat] $ uname -a Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752417/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
I did, but logout/login didn't seem to fix the issue. Maybe gdm should've been restarted as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+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 1765631] Re: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1765631 Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted Status in perl package in Ubuntu: New Bug description: Giving Ubuntu Crashes ERROR. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-modules-5.22 5.22.1-9ubuntu0.3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 18 14:44:36 2018 DpkgTerminalLog: Preparing to unpack .../perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb ... Unpacking perl-modules-5.22 (5.22.1-9ubuntu0.3) over (5.22.1-9ubuntu0.2) ... dpkg: error processing archive /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted DuplicateSignature: package:perl-modules-5.22:5.22.1-9ubuntu0.3 Unpacking perl-modules-5.22 (5.22.1-9ubuntu0.3) over (5.22.1-9ubuntu0.2) ... dpkg: error processing archive /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted InstallationDate: Installed on 2017-09-14 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: perl Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1765631/+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 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
I'd still like to get the upload debdiff for 'timeout' that I prepared uploaded. Even if we manage to debug the bind9-host issue, it will still be useful to have the timeout command there as a backup. Not long before we run out of time for bionic release. I am actively looking at the bind9-host issue also, but I do not expect to get that fixed before release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Confirmed Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Bug description: On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+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 1765631] [NEW] package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted
Public bug reported: Giving Ubuntu Crashes ERROR. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-modules-5.22 5.22.1-9ubuntu0.3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 18 14:44:36 2018 DpkgTerminalLog: Preparing to unpack .../perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb ... Unpacking perl-modules-5.22 (5.22.1-9ubuntu0.3) over (5.22.1-9ubuntu0.2) ... dpkg: error processing archive /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted DuplicateSignature: package:perl-modules-5.22:5.22.1-9ubuntu0.3 Unpacking perl-modules-5.22 (5.22.1-9ubuntu0.3) over (5.22.1-9ubuntu0.2) ... dpkg: error processing archive /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted InstallationDate: Installed on 2017-09-14 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: perl Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1765631 Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted Status in perl package in Ubuntu: New Bug description: Giving Ubuntu Crashes ERROR. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: perl-modules-5.22 5.22.1-9ubuntu0.3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Wed Apr 18 14:44:36 2018 DpkgTerminalLog: Preparing to unpack .../perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb ... Unpacking perl-modules-5.22 (5.22.1-9ubuntu0.3) over (5.22.1-9ubuntu0.2) ... dpkg: error processing archive /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted DuplicateSignature: package:perl-modules-5.22:5.22.1-9ubuntu0.3 Unpacking perl-modules-5.22 (5.22.1-9ubuntu0.3) over (5.22.1-9ubuntu0.2) ... dpkg: error processing archive /var/cache/apt/archives/perl-modules-5.22_5.22.1-9ubuntu0.3_all.deb (--unpack): unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted InstallationDate: Installed on 2017-09-14 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: perl Title: package perl-modules-5.22 5.22.1-9ubuntu0.3 failed to install/upgrade: unable to open '/usr/share/perl/5.22.1/unicore/To/Uc.pl.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1765631/+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 1752053] Re: nvidia-390 fails to boot graphical display
Seems to have been fixed by a recent update; boots into SDDM now as expected, using nvidia-drivers-390. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
the issue sounds similar to bug #1620806, do you have a ~/.xinputrc? does deleting it fixes the issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+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 1765611] Re: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade when user cancels selection of switch key combination
** Tags removed: need-duplicate-check -- 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/1765611 Title: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade when user cancels selection of switch key combination Status in console-setup package in Ubuntu: New Bug description: I have layout switch combination set to both shift toggles (not via gnome configuration). During upgrade I could not find such combination. Therefore I choose cancel in combination selection window. This result in crash during upgrade. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Fri Apr 20 08:18:54 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-11 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Keyboard: XKBLAYOUT=us,lt XKBVARIANT=, BACKSPACE=guess PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6 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 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1765611/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+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 1765611] [NEW] package keyboard-configuration 1.178ubuntu2 failed to install/upgrade when user cancels selection of switch key combination
Public bug reported: I have layout switch combination set to both shift toggles (not via gnome configuration). During upgrade I could not find such combination. Therefore I choose cancel in combination selection window. This result in crash during upgrade. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Fri Apr 20 08:18:54 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-11 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Keyboard: XKBLAYOUT=us,lt XKBVARIANT=, BACKSPACE=guess PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6 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 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1765611 Title: package keyboard-configuration 1.178ubuntu2 failed to install/upgrade when user cancels selection of switch key combination Status in console-setup package in Ubuntu: New Bug description: I have layout switch combination set to both shift toggles (not via gnome configuration). During upgrade I could not find such combination. Therefore I choose cancel in combination selection window. This result in crash during upgrade. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Fri Apr 20 08:18:54 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-11 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Keyboard: XKBLAYOUT=us,lt XKBVARIANT=, BACKSPACE=guess PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6 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 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1765611/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
I can, on my old account upgraded from xenial, but not on my laptop which was installed with bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in ubuntu-themes package in Ubuntu: New Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1760818/+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