[Touch-packages] [Bug 1779720] Re: Thinkpad Extra Buttons - two keys not recognized
Does kernel report correct key events? -- 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/1779720 Title: Thinkpad Extra Buttons - two keys not recognized Status in systemd package in Ubuntu: New Bug description: These two keys out of Thinkpad Extra Buttons are not recognized when trying to setup keyboard shortcuts in settings: "Keyboard Icon" Button: MSC_SCAN 49 "Star Icon" Button: MSC_SCAN 45 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules 70-snap.gimp.rules 70-snap.canonical-livepatch.rules 70-snap.keepassxc.rules Date: Mon Jul 2 18:28:58 2018 InstallationDate: Installed on 2018-07-01 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20KHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=40e13b59-4cfd-42bb-a056-6e9b72aa999c ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET40W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET40W(1.15):bd04/13/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779720/+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 1783693] Re: failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado d
i have installed lubuntu minimal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1783693 Title: failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 Status in sudo package in Ubuntu: New Bug description: no direct access after installing wine ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:28:22 2018 ErrorMessage: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-07-21 (4 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: sudo Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers análisis OK /etc/sudoers.d/README análisis OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1783693/+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 1783571] Re: Set Yaru as default
As a reminder, ubuntu-settings is failing due to a meson issue: https://github.com/mesonbuild/meson/issues/3914. The stack has been tested locally and everything works well, including transition with removal of older alternatives and fallback to plan Shell for GDM without the theme installed. ** Bug watch added: github.com/mesonbuild/meson/issues #3914 https://github.com/mesonbuild/meson/issues/3914 -- 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/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+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 1783693] [NEW] failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado
Public bug reported: no direct access after installing wine ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:28:22 2018 ErrorMessage: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-07-21 (4 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: sudo Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers análisis OK /etc/sudoers.d/README análisis OK ** Affects: sudo (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 sudo in Ubuntu. https://bugs.launchpad.net/bugs/1783693 Title: failed to install winepackage sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 Status in sudo package in Ubuntu: New Bug description: no direct access after installing wine ProblemType: Package DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:28:22 2018 ErrorMessage: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 InstallationDate: Installed on 2018-07-21 (4 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: sudo Title: package sudo 1.8.21p2-3ubuntu1 failed to install/upgrade: instalado sudo paquete pre-removal guión el subproceso devolvió un error con estado de salida 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers análisis OK /etc/sudoers.d/README análisis OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1783693/+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 1780440] Re: [i915] [regression] Tray icons are displayed incorrectly with MESA 18.0.5
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1780440 Title: [i915] [regression] Tray icons are displayed incorrectly with MESA 18.0.5 Status in mesa package in Ubuntu: Confirmed Bug description: The recent upgrade from MESA 17.2.8 to 18.0.5 is causing the icons of some applications bundled with Ubuntu 16.04 to be displayed incorrectly in the status bar. The icons are surrounded by a shadow and some colorization is missing. The problem can be seen on the attached picture - VLC and Electrum icons are affected by the problem (VLC's icon is surrounded by an extra shadow and Electrum icon is supposed to be blue but is all black), and HexChat's icon is displayed correctly next to them. I'm using Linux Mint MATE 18.3 (based on Ubuntu 16.04's package base), but the problem is present on Ubuntu MATE 16.04, too. The hardware i'm using is ThinkPad T400 with an integrated Intel graphic accelerator, using the default intel Xorg driver. $ lspci -k | grep -EA3 'VGA|3D|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07) Subsystem: Lenovo Mobile 4 Series Chipset MEI Controller $ glxinfo | grep -i vendor server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Vendor: Intel Open Source Technology Center (0x8086) OpenGL vendor string: Intel Open Source Technology Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780440/+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 1783689] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: Speakers work from windows partition. Hear sounds when ubuntu log in page comes up. Once logged in cannot hear sound using alsa or pulseaudio. No reports of speaker problems or app complaints ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1974 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 25 22:26:23 2018 InstallationDate: Installed on 2018-01-05 (201 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1974 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1783689 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Speakers work from windows partition. Hear sounds when ubuntu log in page comes up. Once logged in cannot hear sound using alsa or pulseaudio. No reports of speaker problems or app complaints ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1974 F pulseaudio CurrentDesktop: Unity Date: Wed Jul 25 22:26:23 2018 InstallationDate: Installed on 2018-01-05 (201 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jon1974 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783689/+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 1596248] Re: [Dell XPS 13 9343] Touchpad stops working occasionally
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1596248 Title: [Dell XPS 13 9343] Touchpad stops working occasionally Status in xorg package in Ubuntu: Expired Bug description: Occasionally, my cursor stops following my mouse movements. I followed instructions described here: https://wiki.ubuntu.com/DebuggingTouchpadDetection If you do not find a Touchpad in you /proc/bus/input/devices, the bug is in the kernel itself and you should follow these steps: Provide the general information. Directly after logging in to GNOME, KDE, or Xfce open a terminal and enter the following commands: cat /proc/bus/input/devices > ~/devices dmesg > ~/dmesg_boot cp /var/log/Xorg.0.log ~/Xorg.0.log Wait until your touchpad stops working. Open a Virtual Terminal by pressing Ctrl-Alt-F1. Enter the following commands: LANG=C dmesg > ~/dmesg diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff Attach as separate attachments to your bug report ~/devices, ~/dmesg_boot, ~/dmesg_diff, ~/Xorg.0.log and ~/Xorg.0.log_diff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jun 25 17:57:40 2016 DistUpgraded: 2016-05-30 11:23:22,422 ERROR failed to import apport python module, can't generate crash: No module named 'xml.dom' DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665] InstallationDate: Installed on 2015-05-18 (404 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) LightdmLog: [+7057.65s] DEBUG: Seat seat0 changes active session to [+7063.85s] DEBUG: Seat seat0 changes active session to 40 [+7145.78s] DEBUG: Seat seat0 changes active session to c7 [+7145.78s] DEBUG: Session c7 is already active MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7 init=/sbin/upstart SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-05-30 (26 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1596248/+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 1771111] Re: Freezes on Thinkpad R500
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/177 Title: Freezes on Thinkpad R500 Status in xorg package in Ubuntu: Expired Bug description: Problem with black boxes on screen, freezing mouse, random freezes (1-2s). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 BootLog: /dev/sda1: clean, 586416/5447680 files, 15738435/21777920 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 14 14:36:13 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e5] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e5] InstallationDate: Installed on 2017-11-12 (182 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 271434G PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=0b74ca14-9767-4eca-95ac-fcbedc338d77 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7YET50WW (1.20 ) dmi.board.name: 271434G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7YET50WW(1.20):bd10/30/2008:svnLENOVO:pn271434G:pvrThinkPadR500:rvnLENOVO:rn271434G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad R500 dmi.product.name: 271434G dmi.product.version: ThinkPad R500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/177/+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 1783684] Re: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: corrupted-package ** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783684 Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive Status in cups package in Ubuntu: Invalid Bug description: please help me to solve this problem ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-server-common 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:18:44 2018 Dependencies: ErrorMessage: corrupted filesystem tarfile - corrupted package archive InstallationDate: Installed on 2018-07-25 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20236 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: cups Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN24WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500 dmi.modalias: dmi:bvnLENOVO:bvr78CN24WW(V2.02):bd09/23/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500: dmi.product.family: IDEAPAD dmi.product.name: 20236 dmi.product.version: Lenovo G500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783684/+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 1783684] [NEW] package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Public bug reported: please help me to solve this problem ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-server-common 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:18:44 2018 Dependencies: ErrorMessage: corrupted filesystem tarfile - corrupted package archive InstallationDate: Installed on 2018-07-25 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20236 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: cups Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN24WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500 dmi.modalias: dmi:bvnLENOVO:bvr78CN24WW(V2.02):bd09/23/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500: dmi.product.family: IDEAPAD dmi.product.name: 20236 dmi.product.version: Lenovo G500 dmi.sys.vendor: LENOVO ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1783684 Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive Status in cups package in Ubuntu: New Bug description: please help me to solve this problem ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-server-common 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:18:44 2018 Dependencies: ErrorMessage: corrupted filesystem tarfile - corrupted package archive InstallationDate: Installed on 2018-07-25 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20236 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: cups Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN24WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500 dmi.modalias: dmi:bvnLENOVO:bvr78CN24WW(V2.02):bd09/23/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500: dmi.product.family: IDEAPAD dmi.product.name: 20236 dmi.product.version: Lenovo G500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783684/+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 1783684] Re: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783684 Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive Status in cups package in Ubuntu: New Bug description: please help me to solve this problem ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-server-common 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jul 26 00:18:44 2018 Dependencies: ErrorMessage: corrupted filesystem tarfile - corrupted package archive InstallationDate: Installed on 2018-07-25 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 20236 PackageArchitecture: all Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=44e1ab89-4cab-48c5-8b06-7c9b87d701fd ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: cups Title: package cups-server-common 2.2.7-1ubuntu2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 78CN24WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500 dmi.modalias: dmi:bvnLENOVO:bvr78CN24WW(V2.02):bd09/23/2013:svnLENOVO:pn20236:pvrLenovoG500:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500: dmi.product.family: IDEAPAD dmi.product.name: 20236 dmi.product.version: Lenovo G500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783684/+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 1781739] Re: 18.04 Leaking wireless connection to other users
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781739 Title: 18.04 Leaking wireless connection to other users Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: In ubuntu 18.04, when setting up a new wireless connection: Select "Connect automatically" Untick "Make this connection available to other users" Select "Store the password only for this user" Once you are connected to the network, switch user once or twice. Eventually the other user will be connected to the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
I'll add my name to the list of people saying this is a blocker. I am currently working on a massive upgrade of 1000+ systems to Ubuntu 18.04 planned for early next year. Local dns resolution is an absolute must, and it must work out of the box. I can't update /etc/resolv.conf symlinks on thousands of systems manually. Even in an automated way, this is cumbersome and prone to break unexpectedly when updates get applied and revert the manual change. My DHCP server hands out a DNS server, and I expect my clients to ask that DNS server for all name resolution. How this long held tenant of network operation is being so horribly violated by systemd-resolved I don't understand. Did no one test this once? This is "Insanely broken and wrong". Please fix this bug ASAP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783624] Re: Some programs do not work
It sounds like you might be reporting two issues: * Cannot access software through Ubuntu Software * VLC does not play DVD movies So I'm going to make this bug about the more definite second issue. Reassigning to VLC. ** Package changed: xorg (Ubuntu) => vlc (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/1783624 Title: Some programs do not work Status in vlc package in Ubuntu: New Bug description: Cannot access software through Ubuntu Software VLC does not play DVD movies ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 26 04:07:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] [1462:1910] InstallationDate: Installed on 2018-07-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP-Pavilion VT563AA-ABG HPE-170a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.07 dmi.board.name: IONA dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: VT563AA-ABG HPE-170a dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jul 26 04:05:37 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 0b38:0010KEYBOARD, id 8 inputHID 0b38:0010KEYBOARD, id 9 inputHID 413c:3010MOUSE, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1783624/+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 1783650] Re: freezed
It sounds like some part of the system has crashed. Please: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => 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/1783650 Title: freezed Status in Ubuntu: Incomplete Bug description: I m new here and a have no plan about all this stoff i little bit to old for all this, only i can talk that i have ubuntu 18.04.1 LTS Aspire-ES 1-711 Speicher 3.7 GB Intel Pentium CPU 3540@21 GHz+4 Intel Bay Trail Gnome 3.28.2 64 Bit 491.2Gb Machine Acer mybig prtoblem is all like 20 minuts my laptop is complet freezed sorry a have no idee about computers bud i need help and my inglish is well not verry good ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 25 18:16:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0939] InstallationDate: Installed on 2018-06-14 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Acer Aspire ES1-711 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=aff7ad2c-74bc-4b1e-aee1-32dba4908d09 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire ES1-711 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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/+bug/1783650/+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 1778960] Re: SRU: Update python 2.7 to the final 2.7.15 release
no, none is wrong with these breaks. These were for Debian unstable, not for any Ubuntu release. Dropping those doesn't do anything, as Ubuntu doesn't allow any partial upgrades. -- 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/1778960 Title: SRU: Update python 2.7 to the final 2.7.15 release Status in python2.7 package in Ubuntu: New Bug description: Ubuntu 18.04 LTS shipped with the python 2.7.15 release candidate. Please let's update to the final release. Upstream changes are: - bpo-33374: Tweak the definition of PyGC_Head, so compilers do not believe it is always 16-byte aligned on x86. This prevents crashes with more aggressive optimizations present in GCC 8. - Identify as 2.7.15 instead of 2.7.15rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1778960/+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 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working
Please also verify that you see no devices, or just the dummy device in: Settings > Sound If pulseaudio is indeed crashing for you then that's what we need to debug. Please: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1783200 Title: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working Status in pulseaudio package in Ubuntu: Incomplete Bug description: I believe this is a pulseaudio regression, as the output of alsa-info (http://www.alsa- project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine as far as I can see. I'm currently running Ubuntu 18.04, and I believe this is a regression as audio used to work under 17.10. Since upgrading (which fixed a good number of other incompatibilities with the machine), I've had no luck getting audio to work at all. I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and 'pulseaudio -vv'. If I can provide any other information, or if there's anything you'd like me to try, I'd be happy to help in any way possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+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 1783663] Re: Erroe at bootup
*** This bug is a duplicate of bug 1727356 *** https://bugs.launchpad.net/bugs/1727356 I would ask for more information usually but from your CPU model I can tell you will be experiencing bug 1727356. ** Package changed: xorg (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1727356 Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) -- 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/1783663 Title: Erroe at bootup Status in Ubuntu: New Bug description: Cancel request. Error on both desktop 16.04LTS install and same on a laptop at bootup, intermitantly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jul 25 21:24:23 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-131-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0263] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0263] InstallationDate: Installed on 2018-07-13 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E5500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=7ed22adf-d5c3-4e3e-811b-4d7bc238c150 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0DW635 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd08/11/2009:svnDellInc.:pnLatitudeE5500:pvr:rvnDellInc.:rn0DW635:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E5500 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 25 20:06:52 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 32884 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1783663/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
This bug is closed. Please log a new bug by running: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1783663] [NEW] Erroe at bootup
Public bug reported: Cancel request. Error on both desktop 16.04LTS install and same on a laptop at bootup, intermitantly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jul 25 21:24:23 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-131-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0263] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0263] InstallationDate: Installed on 2018-07-13 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E5500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=7ed22adf-d5c3-4e3e-811b-4d7bc238c150 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0DW635 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd08/11/2009:svnDellInc.:pnLatitudeE5500:pvr:rvnDellInc.:rn0DW635:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude E5500 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 25 20:06:52 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 32884 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1783663 Title: Erroe at bootup Status in xorg package in Ubuntu: New Bug description: Cancel request. Error on both desktop 16.04LTS install and same on a laptop at bootup, intermitantly. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jul 25 21:24:23 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-131-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0263] Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller [1028:0263] InstallationDate: Installed on 2018-07-13 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E5500 PccardctlIdent: Socket 0: no product info
[Touch-packages] [Bug 1783662] [NEW] Xorg server crashing on boot "Failing initialization of X screen 0"
Public bug reported: Ubuntu version: Ubuntu 18.04 LTS I have recently been having a problem with my desktop completely locking up (no input is accepted) after a few minutes of usage. Every time I restarted my PC, the time it took to freeze got shorter and shorter until GDM just refused to load on startup (I couldn't even login). I Eventually got stuck on the screen where it shows services starting with their status with the last item being "[ OK ] Started GNOME Display Manager". I started having this problem just a few days ago. Prior to these freezing issues my installation was working perfectly, buttery smooth. The only major thing that I did that may be causing this issue is my Oculus Rift that I left plugged into my PC. After leaving my PC on the services screen all night, it actually unfroze and displayed a stack trace. Unfortunately, I don't have that stack trace. However, I have posted the Xorg.0.log below which may be relevant. Since, I have been able to recover my PC from the freezing issues. After the services screen disappeared and a stack trace displayed, I was able to access a terminal session with Ctrl+Alt+F2 and run the command "sudo apt purge nvidia*". * /var/log/Xorg.0.log * [ 1165.010] (--) Log file renamed from "/var/log/Xorg.pid-19451.log" to "/var/log/Xorg.0.log" [ 1165.011] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 1165.011] X Protocol Version 11, Revision 0 [ 1165.011] Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu [ 1165.011] Current Operating System: Linux austin-Z87-DS3H 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 [ 1165.011] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=c512947f-950a-4c87-99a0-9b7b6c9d6e68 ro quiet splash vt.handoff=1 [ 1165.011] Build Date: 13 April 2018 08:07:36PM [ 1165.011] xorg-server 2:1.19.6-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) [ 1165.011] Current version of pixman: 0.34.0 [ 1165.011]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1165.011] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1165.011] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 24 23:24:11 2018 [ 1165.011] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1165.011] (==) No Layout section. Using the first Screen section. [ 1165.011] (==) No screen section available. Using defaults. [ 1165.011] (**) |-->Screen "Default Screen Section" (0) [ 1165.011] (**) | |-->Monitor "" [ 1165.011] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1165.011] (==) Automatically adding devices [ 1165.011] (==) Automatically enabling devices [ 1165.011] (==) Automatically adding GPU devices [ 1165.011] (==) Automatically binding GPU devices [ 1165.011] (==) Max clients allowed: 256, resource mask: 0x1f [ 1165.011] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1165.011]Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [ 1165.011]Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [ 1165.011]Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [ 1165.011]Entry deleted from font path. [ 1165.011] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [ 1165.011]Entry deleted from font path. [ 1165.011] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1, built-ins [ 1165.011] (==) ModulePath set to "/usr/lib/xorg/modules" [ 1165.011] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1165.011] (II) Loader magic: 0x5632520ad020 [ 1165.011] (II) Module ABI versions: [ 1165.011]X.Org ANSI C Emulation: 0.4 [ 1165.011]X.Org Video Driver: 23.0 [ 1165.011]X.Org XInput driver : 24.1 [ 1165.011]X.Org Server Extension : 10.0 [ 1165.012] (++) using VT number 1 [ 1165.013] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c504 [ 1165.014] (II) xfree86: Adding drm device (/dev/dri/card1) [ 1165.014] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 12 paused 0 [ 1165.014] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1165.014] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0 [ 1165.015] (**) OutputClass "nvidia" ModulePath extended to
[Touch-packages] [Bug 1782038] Re: [Patch included] Window buttons are small in a maximized Chromium window
The attachment "patch.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- 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/1782038 Title: [Patch included] Window buttons are small in a maximized Chromium window Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1782038/+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 1783650] [NEW] freezed
Public bug reported: I m new here and a have no plan about all this stoff i little bit to old for all this, only i can talk that i have ubuntu 18.04.1 LTS Aspire-ES 1-711 Speicher 3.7 GB Intel Pentium CPU 3540@21 GHz+4 Intel Bay Trail Gnome 3.28.2 64 Bit 491.2Gb Machine Acer mybig prtoblem is all like 20 minuts my laptop is complet freezed sorry a have no idee about computers bud i need help and my inglish is well not verry good ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 25 18:16:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0939] InstallationDate: Installed on 2018-06-14 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Acer Aspire ES1-711 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=aff7ad2c-74bc-4b1e-aee1-32dba4908d09 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire ES1-711 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 package-from-proposed 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/1783650 Title: freezed Status in xorg package in Ubuntu: New Bug description: I m new here and a have no plan about all this stoff i little bit to old for all this, only i can talk that i have ubuntu 18.04.1 LTS Aspire-ES 1-711 Speicher 3.7 GB Intel Pentium CPU 3540@21 GHz+4 Intel Bay Trail Gnome 3.28.2 64 Bit 491.2Gb Machine Acer mybig prtoblem is all like 20 minuts my laptop is complet freezed sorry a have no idee about computers bud i need help and my inglish is well not verry good ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 25 18:16:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0939] InstallationDate: Installed on 2018-06-14 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Acer Aspire ES1-711 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=aff7ad2c-74bc-4b1e-aee1-32dba4908d09 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
I still have this problem, Anybody running the latest pulseaudio on Raspberry Pi or CM3? I'm using pulseaudio 12.2 with bluez 5.50. After I connected to a Bluetooth speaker. When play something, it's really choppy and skipping a lot. The debug message shows: D: [bluetooth] module-bluez5-device.c: Skipping 43083 us (= 7600 bytes) in audio stream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: SRU Request: [Impact] When the connection drops temporarily, using A2DP, a noticeable latency is introduced, and the audio goes out of sync. [Test Case] 1) Enable the -proposed repository, and install the new pulseaudio 2) Restart your computer, connect it to a bluetooth device (e.g. a headset or a speaker), play one or more videos either locally or online, and see if you can still reproduce the problem. [Regression Potential] Low, as the changes are upstream, and, if anything, it should also fix a memory leak. Furthermore, the changes only affect the bluez5-device module, in pulseaudio, and they make the buffer updating logic more conscious of how things can change when the connection drops. This is unlikely to affect anything else in pulseaudio. As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1783643] [NEW] System was stuttering during intensive IO on SD card
Public bug reported: dmesg output follows: [476712.748600] mmc0: new ultra high speed SDR104 SDXC card at address [476712.750392] mmcblk0: mmc0: SP64G 59.5 GiB [476712.761168] mmcblk0: p1 [477821.312742] BUG: unable to handle kernel paging request at 3858 [477821.312771] IP: page_vma_mapped_walk+0x1e7/0x5a0 [477821.312782] PGD 0 [477821.312783] P4D 0 [477821.312800] Oops: [#1] SMP NOPTI [477821.312810] Modules linked in: cdc_acm unix_diag af_packet_diag netlink_diag uas usb_storage mmc_block xfrm_user xfrm_algo xt_addrtype br_netfilter aufs sctp_diag sctp dccp_diag dccp tcp_diag udp_diag inet_diag ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp joydev bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter rtsx_pci_ms snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc memstick rtsx_pci_sdmmc snd_hda_codec_conexant snd_hda_codec_generic snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi [477821.312971] snd_seq_midi_event arc4 snd_rawmidi intel_rapl x86_pkg_temp_thermal intel_powerclamp snd_seq kvm_intel binfmt_misc uvcvideo kvm videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 irqbypass nls_iso8859_1 videobuf2_core crct10dif_pclmul videodev crc32_pclmul media ghash_clmulni_intel intel_cstate intel_rapl_perf snd_seq_device snd_timer iwlmvm mac80211 snd psmouse hp_wmi sparse_keymap e1000e ptp pps_core wmi_bmof iwlwifi soundcore cfg80211 idma64 virt_dma ahci mei_me rtsx_pci mei libahci intel_lpss_pci intel_pch_thermal i2c_hid hid intel_lpss_acpi intel_lpss hp_accel lis3lv02d input_polldev hp_wireless acpi_pad coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio af_alg dm_crypt raid10 raid456 libcrc32c async_raid6_recov [477821.313150] async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 raid0 multipath linear amdgpu amdkfd i915 amd_iommu_v2 radeon aesni_intel aes_x86_64 crypto_simd cryptd glue_helper ttm i2c_algo_bit drm_kms_helper input_leds nvme serio_raw syscopyarea sysfillrect sysimgblt nvme_core fb_sys_fops drm shpchp wmi pinctrl_sunrisepoint video pinctrl_intel mac_hid [477821.313225] CPU: 1 PID: 54 Comm: kswapd0 Not tainted 4.13.0-46-generic #51-Ubuntu [477821.313241] Hardware name: HP HP ZBook 14u G4/828C, BIOS P78 Ver. 01.18 05/16/2018 [477821.313258] task: 977d1ba65f00 task.stack: b97b01a9c000 [477821.313274] RIP: 0010:page_vma_mapped_walk+0x1e7/0x5a0 [477821.313287] RSP: 0018:b97b01a9fa70 EFLAGS: 00010246 [477821.313300] RAX: RBX: b97b01a9fab8 RCX: b97b01a9fb98 [477821.313315] RDX: 00013808 RSI: 3808 RDI: ebab8ff50980 [477821.313331] RBP: b97b01a9faa0 R08: 000a R09: 8ac4 [477821.313356] R10: R11: 0010 R12: ebab8ff50980 [477821.313384] R13: R14: 00013808 R15: 977d01cfcec0 [477821.313402] FS: () GS:977d2f48() knlGS: [477821.313419] CS: 0010 DS: ES: CR0: 80050033 [477821.313434] CR2: 3858 CR3: 00010340a002 CR4: 003606e0 [477821.313450] Call Trace: [477821.313460] page_referenced_one+0xa1/0x1a0 [477821.313471] rmap_walk_anon+0xfa/0x270 [477821.313482] rmap_walk+0x48/0x60 [477821.313491] page_referenced+0xdc/0x170 [477821.313501] ? rmap_walk_anon+0x270/0x270 [477821.313512] ? page_get_anon_vma+0x90/0x90 [477821.313527] shrink_active_list+0x1d4/0x410 [477821.313539] shrink_node_memcg+0x225/0x770 [477821.313550] shrink_node+0xf7/0x300 [477821.313559] ? shrink_node+0xf7/0x300 [477821.313569] kswapd+0x2b4/0x730 [477821.313578] kthread+0x128/0x140 [477821.313587] ? mem_cgroup_shrink_node+0x190/0x190 [477821.313599] ? kthread_create_on_node+0x70/0x70 [477821.313611] ret_from_fork+0x1f/0x40 [477821.313620] Code: c3 48 85 c0 0f 85 7d fe ff ff e8 15 1f 01 00 85 c0 0f 85 4c ff ff ff 4c 8b 73 10 48 8b 75 d0 4c 89 f0 48 c1 e8 27 25 ff 01 00 00 <48> 8b 56 50 48 8b 3c c2 48 ba ff 0f 00 00 00 c0 ff ff 40 f6 c7 [477821.313677] RIP: page_vma_mapped_walk+0x1e7/0x5a0 RSP: b97b01a9fa70 [477821.313692] CR2: 3858 [477821.319563] ---[ end trace 5fdf55adc9c23577 ]--- Attempt to umount sdcard said: umount: /media/user/sdcard: target is busy. Attempt to use sudo fuser -k -m /media/user/sdcard gave a reply: Killed New lines appeared in dmesg: [478635.472515] BUG: unable to handle kernel paging request at 822a [478635.475689] IP: show_map_vma.isra.18+0x4f/0x200 [478635.478576] PGD 0 [478635.478576] P4D 0 [478635.485284] Oops: [#5] SMP NOPTI [478635.487162] Modules linked in: cdc_acm unix_diag
[Touch-packages] [Bug 1528139] Re: serialize_profile_from_old_profile() crash if file contains multiple profiles
Done - https://gitlab.com/apparmor/apparmor/merge_requests/131 will be
part of AppArmor 3.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1528139
Title:
serialize_profile_from_old_profile() crash if file contains multiple
profiles
Status in AppArmor:
Fix Released
Status in AppArmor 2.10 series:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
= Changed Local Profiles =
The following local profiles were changed. Would you like to save
them?
[1 - /sbin/dhclient]
2 - /usr/sbin/nmbd
3 - /usr/bin/snx
4 - /usr/sbin/dnsmasq
5 - /{usr/,}bin/ping
6 - /usr/sbin/smbd
7 - /usr/lib/telepathy/mission-control-5
(S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes
b/w (C)lean profiles / Abo(r)t
Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in
apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2197, in
do_logprof_pass
save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2277, in
save_profiles
newprofile = serialize_profile_from_old_profile(aa[which], which, '')
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3961, in
serialize_profile_from_old_profile
if write_prof_data[hat]['network'].is_covered(network_obj, True, True):
AttributeError: 'collections.defaultdict' object has no attribute 'is_covered'
An unexpected error occoured!
For details, see /tmp/apparmor-bugreport-v7wx9fu9.txt
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
When I pressed V button aa-logprof exits with error.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: apparmor 2.10-0ubuntu6
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Mon Dec 21 09:54:51 2015
InstallationDate: Installed on 2014-04-19 (611 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.2.0-21-generic
root=/dev/mapper/ubuntu-root ro splash elevator=cfq nomdmonddf nomdmonisw
crashkernel=384M-:128M
SourcePackage: apparmor
Syslog:
UpgradeStatus: Upgraded to wily on 2015-11-14 (36 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1528139/+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 1782038] Re: [Patch included] Window buttons are small in a maximized Chromium window
** Attachment added: "Screenshot_2018-07-25-17-21-09.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+attachment/5167792/+files/Screenshot_2018-07-25-17-21-09.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/1782038 Title: [Patch included] Window buttons are small in a maximized Chromium window Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1782038/+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 1782038] Re: [Patch included] Window buttons are small in a maximized Chromium window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (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/1782038 Title: [Patch included] Window buttons are small in a maximized Chromium window Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1782038/+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 997899] Re: Ubuntu accessibility packages such as at-spi2 and gnome-orca should have touch screen support
** Description changed: With Ubuntu making a move tward phones and tablets, accessibility needs to be taken into account. The accessibility stack should allow a totally blind person to access and explore the contents on screen without needing a physical keyboard. Accessibility related commands will need to be mapped to touch gestures. For example, opening the Orca preferences - dialog. I thing a package such as Easystroke can help with this project. + dialog. I think a package such as Easystroke can help with this project. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: at-spi2-core 2.4.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Thu May 10 21:39:14 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/997899 Title: Ubuntu accessibility packages such as at-spi2 and gnome-orca should have touch screen support Status in at-spi2-core package in Ubuntu: New Status in gnome-orca package in Ubuntu: New Bug description: With Ubuntu making a move tward phones and tablets, accessibility needs to be taken into account. The accessibility stack should allow a totally blind person to access and explore the contents on screen without needing a physical keyboard. Accessibility related commands will need to be mapped to touch gestures. For example, opening the Orca preferences dialog. I think a package such as Easystroke can help with this project. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: at-spi2-core 2.4.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Thu May 10 21:39:14 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/997899/+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 969750] Re: K53E volume hardware shortcuts not working
** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released -- 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/969750 Title: K53E volume hardware shortcuts not working Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: When I try to use function+f11 and function+f12 to raise and lower the volume of my system, nothing happends. These key strokes worked as expected in beta 1. I have an Asus K53E. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-desktop 1.265 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 20:15:23 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120321) ProcEnviron: TERM=xterm 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/969750/+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 1503762] Re: Provide systemd service
** Changed in: apparmor (Debian) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1503762 Title: Provide systemd service Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor package in Debian: New Status in apparmor package in Gentoo Linux: Fix Released Bug description: AppArmor is in the critical path for bootup for any systems that use it. Let's specify a systemd service file instead of having systemd use sysv compatibility mode. There seems to be a few bugs tracking the precursor this work, like https://bugs.launchpad.net/apparmor/+bug/1488179, but no actual bug for the systemd service itself. AUR has a simple service file, not sure if that would be useful - https://aur.archlinux.org/packages/apparmor/ To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1503762/+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 1783200] Re: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working
Yup, pulseaudio doesn't start at all. When I run it with 'pulseaudio -vv' to get the debug output, it ends with a SIGKILL. There's no daemon running. Here's a bug that I believe might be connected, and I commented on it before: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1759942 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1783200 Title: [Lenovo Miix 310, Ubuntu 18.04] Audio no longer working Status in pulseaudio package in Ubuntu: Incomplete Bug description: I believe this is a pulseaudio regression, as the output of alsa-info (http://www.alsa- project.org/db/?f=730ab5b8f0499ef58c0e17f67f8f911ba53a011c) looks fine as far as I can see. I'm currently running Ubuntu 18.04, and I believe this is a regression as audio used to work under 17.10. Since upgrading (which fixed a good number of other incompatibilities with the machine), I've had no luck getting audio to work at all. I'm attaching the output of dmesg, 'aplay -l', 'aplay -L' and 'pulseaudio -vv'. If I can provide any other information, or if there's anything you'd like me to try, I'd be happy to help in any way possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1783200/+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 1638492] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1638492 Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: In Progress Bug description: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 2 09:21:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-07-29 (95 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-09-14T10:24:20.453516 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1638492/+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 1782190] Re: Set default interface font size to 11 for communitheme sessions
The fix was uploaded to cosmic (failing to build on a meson issue) and bionic (waiting for review) ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: ubuntu-settings (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1782190 Title: Set default interface font size to 11 for communitheme sessions Status in ubuntu-settings package in Ubuntu: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Committed Bug description: [Impact] * communitheme snap users see the gnome shell overview window thumbnail labels cutted off * 18.04 users can install the communitheme snap from within gnome- software * To fix this the default font size of the interface needs to be switched to 11 (again) [Test Case] * Install ubuntu * install the communitheme snap * reboot * select the communitheme snap session and login * Open "activities" by clicking "activities" in the GNOME shell's upper left corner or by pressing the super/ubuntu/windows key * Each window thumbnail is labeled with a text which is now cut * This is caused by a bug in gnome-shell which can't handle any other font size than 11 for any other font beside cantarell * install the new ubuntu-settings version * open again activities * check that window thumbnails aren't cut anymore [Regression Potential] * It's affecting only the communitheme session, not available by default and reverting to the same default than ubuntu main session [Other Info] * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome- shell/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1782190/+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 1783626] [NEW] systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed
Public bug reported: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed See https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed -- 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/1783626 Title: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed Status in systemd package in Ubuntu: New Bug description: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed See https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783626/+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 1670959] Re: systemd-resolved using 100% CPU
I just started noticing this issue on my machine today. Ubuntu 18.04. I
also had nameserver 127.0.0.1 in /etc/resolv.conf. Changed to
127.0.0.53, per diepes' comment and CPU calmed down for me as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Status in dnsmasq package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
dmi.bios.date: 03/09/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M77 Ver. 01.05
dmi.board.name: 2271
dmi.board.vendor: Hewlett-Packard
[Touch-packages] [Bug 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center
This bug was fixed in the package software-properties - 0.96.24.36 --- software-properties (0.96.24.36) cosmic; urgency=medium * SoftwarePropertiesGtk.py: Hide livepatch widgets in flavors without an online account panel in gnome-control-center (LP: #1770686). -- Andrea Azzarone Wed, 25 Jul 2018 17:42:31 +0200 ** Changed in: software-properties (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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: New Bug description: Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+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 1783624] [NEW] Some programs do not work
Public bug reported: Cannot access software through Ubuntu Software VLC does not play DVD movies ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 26 04:07:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] [1462:1910] InstallationDate: Installed on 2018-07-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP-Pavilion VT563AA-ABG HPE-170a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.07 dmi.board.name: IONA dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnVT563AA-ABGHPE-170a:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr: dmi.product.name: VT563AA-ABG HPE-170a dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jul 26 04:05:37 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 0b38:0010KEYBOARD, id 8 inputHID 0b38:0010KEYBOARD, id 9 inputHID 413c:3010MOUSE, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1783624 Title: Some programs do not work Status in xorg package in Ubuntu: New Bug description: Cannot access software through Ubuntu Software VLC does not play DVD movies ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 26 04:07:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] [1462:1910] InstallationDate: Installed on 2018-07-13 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP-Pavilion VT563AA-ABG HPE-170a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic root=UUID=177d2679-ed89-447c-874b-cdd3cf3d72b6 ro splash quiet plymouth:debug=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1783618] [NEW] package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
Public bug reported: I tried everything from askubuntu but the system doesn't give in. Each time I do "sudo apt-get upgrade" I get the message Errors were encountered while processing: gstreamer1.0-tools gstreamer1.0-plugins-base-apps E: Sub-process /usr/bin/dpkg returned an error code (1) I belive its a Bug. Please verify it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 25 22:54:34 2018 DuplicateSignature: package:gstreamer1.0-tools:1.14.1-1~ubuntu18.04.1 Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot dpkg: error processing package gstreamer1.0-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (74 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gstreamer1.0 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (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 gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1783618 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gstreamer1.0 package in Ubuntu: New Bug description: I tried everything from askubuntu but the system doesn't give in. Each time I do "sudo apt-get upgrade" I get the message Errors were encountered while processing: gstreamer1.0-tools gstreamer1.0-plugins-base-apps E: Sub-process /usr/bin/dpkg returned an error code (1) I belive its a Bug. Please verify it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 25 22:54:34 2018 DuplicateSignature: package:gstreamer1.0-tools:1.14.1-1~ubuntu18.04.1 Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot dpkg: error processing package gstreamer1.0-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (74 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gstreamer1.0 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1783618/+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 1783618] Re: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1783618 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gstreamer1.0 package in Ubuntu: New Bug description: I tried everything from askubuntu but the system doesn't give in. Each time I do "sudo apt-get upgrade" I get the message Errors were encountered while processing: gstreamer1.0-tools gstreamer1.0-plugins-base-apps E: Sub-process /usr/bin/dpkg returned an error code (1) I belive its a Bug. Please verify it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 25 22:54:34 2018 DuplicateSignature: package:gstreamer1.0-tools:1.14.1-1~ubuntu18.04.1 Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot dpkg: error processing package gstreamer1.0-tools (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (74 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gstreamer1.0 Title: package gstreamer1.0-tools 1.14.1-1~ubuntu18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1783618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies
Could someone please also check that lscpu still works without error on amd64? Seems to me that we're fixing an edge case, which is fine, but we should also verify the common case functionality. I'd hate to release something that breaks the world on amd64 just because nobody checked it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null) CPU min MHz: (null) L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-31 NUMA node1 CPU(s): 32-55 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 == Comment: #1 - Pridhiviraj Paidipeddi - 2017-01-11 07:06:59 == root@p8wookie:~# dmesg |grep -i powernv [0.00] Using PowerNV machine description [0.331564] EEH: PowerNV platform initialized [0.907250] powernv-rng: Registering arch random hook. [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0 [1.507167] powernv_idle_driver registered [ 34.184048] powernv_rng: Registered powernv hwrng. [ 34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree [ 34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, prod_id: 0x, dev_id: 0x00)
[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies
(please also state the package version strings tested) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: (null) CPU min MHz: (null) L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-31 NUMA node1 CPU(s): 32-55 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 == Comment: #1 - Pridhiviraj Paidipeddi - 2017-01-11 07:06:59 == root@p8wookie:~# dmesg |grep -i powernv [0.00] Using PowerNV machine description [0.331564] EEH: PowerNV platform initialized [0.907250] powernv-rng: Registering arch random hook. [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0 [1.507167] powernv_idle_driver registered [ 34.184048] powernv_rng: Registered powernv hwrng. [ 34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree [ 34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, prod_id: 0x, dev_id: 0x00) root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ [ 42.297825315,7] OCC Common Area at 0x3b0 size 1MB [ 42.297854780,7] OCC Common Area at 0x200080 size 1MB [ 42.297884305,7] OCC Common Area at
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
Hi, for me it seems to work with latest bionic as well. -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1770686] Re: Hide livepatch widgets in flavors without an online account panel in gnome-control-center
** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Committed -- 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/1770686 Title: Hide livepatch widgets in flavors without an online account panel in gnome-control-center Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Bionic: New Bug description: Unfortunately Livepatch strictly depends on the online account panel in gnome-control-center. We should hide the checkbutton in flavors (e.g. Xubuntu) that do not ship gnome-control-center and/or the online account panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1770686/+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 1783571] Re: Set Yaru as default
yaru MIR is https://bugs.launchpad.net/ubuntu/+source/yaru- theme/+bug/1783600 ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- 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/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in yaru-theme package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+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 1591833] Re: [Featue] Upgrade Openssl for Intel QAT (quickassist-technology)
** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1591833 Title: [Featue] Upgrade Openssl for Intel QAT (quickassist-technology) Status in intel: Fix Released Status in openssl package in Ubuntu: In Progress Status in openssl package in Debian: Fix Released Bug description: In order to support Intel QAT, please upgrade Openssl package from 1.0.2 to 1.1.0 HW: Purley-4s Upstream schedule: Openssl: 1.1.0 Target release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591833/+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 1783571] Re: Set Yaru as default
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+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 1783571] Re: Set Yaru as default
** Merge proposal linked: https://code.launchpad.net/~didrocks/ubuntu-seeds/+git/ubuntu/+merge/350929 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+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 1783571] Re: Set Yaru as default
** Merge proposal linked: https://code.launchpad.net/~didrocks/ubuntu/+source/gnome-session/+git/gnome-session/+merge/350928 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in ubuntu-settings package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1783571/+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 1783571] Re: Set Yaru as default
Note: Need as well Yaru 18.10.1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in ubuntu-settings package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1783571/+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 1783571] Re: Set Yaru as default
** Merge proposal linked: https://code.launchpad.net/~didrocks/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/350925 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in ubuntu-settings package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1783571/+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 1205263] Re: pm-utils AC/Battery policy requirement for Audio
Thanks for filing this bug. This project is being shut down as it’s not actively monitored by any team or individual. This bug will not be deleted but will be closed as <>. If this bug is something that is still affecting a product in Ubuntu, you can take one of the following steps to report this bug correctly: File a new bug on the right distribution/package (‘ubuntu/linux’ for example). Or Set the visibility on this bug as public, and then affect the right distribution/package. Keep in mind at that point all information would become public on this particular bug report. ** Changed in: intel Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1205263 Title: pm-utils AC/Battery policy requirement for Audio Status in intel: Won't Fix Status in pm-utils package in Ubuntu: New Bug description: On boards with charger connected, pm-utils disable *all* power-saving feture for PCI devices(include audio pci devices), the hooks is pci- devices under power.d. This policy maybe too regressive. Here's our case: On Intel's Harris beach baord, there're two HDA controller, one HDA in GPU side ,which powered by a area "power-well". Harris Beach has only one eDP panel, if there's no HDMI/DP monitor connected, the audio function is not needed, and power-well should be shutdown. Otherwise some eDP feature will not be enabled. When charger connected, the pm-utils policy let audio subsystem always active, which power-well always on and block eDP features. So should we do some changing on the policy? To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1205263/+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 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Description changed:
+ [Impact]
+
+ * Unattended-upgrades hangs and gets killed when installing upgrades
+ that stat/stop services on shutdown, leaving the system in a broken
+ state
+
+ [Test Case]
+
+ * Install an updated bionic system:
+$ lxc launch ubuntu:18.04 uu-shutdown-test
+# apt update
+...
+
+ * When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
+ # systemd-analyze dot | grep unatt
+ "unattended-upgrades.service"->"-.mount" [color="green"];
+ "unattended-upgrades.service"->"system.slice" [color="green"];
+ "unattended-upgrades.service"->"network.target" [color="green"];
+ "unattended-upgrades.service"->"systemd-journald.socket"
[color="green"];
+ "unattended-upgrades.service"->"local-fs.target" [color="green"];
+ "unattended-upgrades.service"->"-.mount" [color="black"];
+ "unattended-upgrades.service"->"system.slice" [color="black"];
+ "shutdown.target"->"unattended-upgrades.service" [color="green"];
+ "shutdown.target"->"unattended-upgrades.service" [color="grey66"];
+Color legend: black = Requires
+ dark blue = Requisite
+ dark grey = Wants
+ red = Conflicts
+ green = After
+
+ * Configure u-u to run on shutdown and install -updates:
+# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
+# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
+
+ * Downgrade snapd:
+# apt install snapd=2.32.5+18.04
+
+ * # reboot
+
+ * With not fixed u-u observe the upgrade process being stuck:
+ # pstree| grep unatt
+
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
+ `-{unattended-upgr}
+
+ * With fixed u-u observe snapd update taking place and system rebooting
+ after a few seconds with all updates installed
+
+ * Since this fix is partially reverting the fix for LP: #1654600 please
+ test LP: #1654600 as well to avoid regressions.
+
+ [Regression Potential]
+
+ * As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during normal boot when there
is a bug in the implementation.
+ on-testing the SRU.
+ * Due to relationship changes between u-u.service, other services and
targets u-u may fail to run on shutdown in case of an unexpected regression.
+
+ [Original Bug Text]
+
When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
package installation on various packages hangs until the systemd
ShutdownTimeout (30min) is expired and systemd kills all processes and
powers off/reboots the system.
This leaves packages in an unconfigured, broken state. At least
sometimes this cannot be fixed with a "dpkg --configure -a", but instead
requires the user to manually reinstall the package that caused the
hang.
This appears to be a deadlock, because the hanging commands are always
"systemctl stop ..." or "systemctl restart ...", etc.. If I understand
this correctly, those systemctl commands block because systemd tries to
shutdown the system and tries to satisfy all dependencies for the
shutdown targets before those systemctl commands could get executed,
which creates a deadlock.
Steps to reproduce:
- Install 18.04
- activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
- disable bionic-updates in /etc/apt/sources.list (more on that later)
- execute "unattended-upgrade --download-only"
- reboot the system
-> The upgrade on shutdown hangs when configuring the apport package.
The hanging command is "systemctl stop apport-forward.socket". The
system hangs until the systemd ShutdownTimeout expires and systemd
forcefully reboots the system.
After the system is rebooted the apport package is in "iUR" state, and
needs to be reinstalled to fix this.
I disabled the bionic-updates pocket in sources.list, because in the
default configuration unattended-updates does not use bionic-updates,
and seems to have skipped installation of apport from bionic-security
(supposedly because an already newer version of apport was in bionic-
updates). If my understanding of why apport initially did not get
installed is correct, then this would be another problem, because it
would mean that unattended-upgrades potentially does not install all
available security updates when bionic-updates is enabled in
sources.list (which is the default).
The problem can also be reproduced without disabling bionic-updates in
sources.list, but instead enabling
[Touch-packages] [Bug 1783452] Re: Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications
** Package changed: ubuntu => gtk+2.0 (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/1783452 Title: Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications Status in gtk+2.0 package in Ubuntu: New Bug description: After switching from 16.04 to 18.04 I noticed that fonts are now (in 18.04) rendered differently in GTK+ apps. For example, there is a vertical bar charcter `│` [U+2502](https://unicode-table.com/en/2502), that is used extensively to create solid vertical lines using just text characters. You can see it in console apps such as `mc` or `pstree`. While it is rendered correctly in Terminal in both 16.04 and 18.04, when rendered inside GTK apps it has unexpected vertical gap in-between characters on 18.04 (16.04 renders it correctly). The issue can be seen in GTK apps such as gVIM, Geany, GEdit, but Qt apps seem to render it properly. I have attached a screenshot that clearly demonstrates the difference. It shows brand new Ubuntu 16.04 on a left side where you can see vertical line in GEdit is completely solid, as it should be. On a right side it shows Ubuntu 18.04 where you can see line now has gaps that should not be there. I built a small GTK2 test app that reproduces the problem (sources at https://pastebin.com/WCH1ds4P), and using it I found that the problem occurs when libfreetype 2.8+ is used. I tested FreeType 2.6, 2.7, 2.7.1 and all of them work fine. While 2.8 and above has this gap. I am not 100% sure if this is an Ubuntu font configuration issue, or bug in FreeType, or GTK or some other Ubuntu components, but I hope someone at least can point me at the right direction. Please also check my post on AskUbuntu which has additional detail and screenshots: https://askubuntu.com/questions/1054779/incorrect-font- glyphs-rendering-in-gtk-applications-in-ubuntu-18-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1783452/+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 1783452] [NEW] Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications
You have been subscribed to a public bug: After switching from 16.04 to 18.04 I noticed that fonts are now (in 18.04) rendered differently in GTK+ apps. For example, there is a vertical bar charcter `│` [U+2502](https://unicode-table.com/en/2502), that is used extensively to create solid vertical lines using just text characters. You can see it in console apps such as `mc` or `pstree`. While it is rendered correctly in Terminal in both 16.04 and 18.04, when rendered inside GTK apps it has unexpected vertical gap in-between characters on 18.04 (16.04 renders it correctly). The issue can be seen in GTK apps such as gVIM, Geany, GEdit, but Qt apps seem to render it properly. I have attached a screenshot that clearly demonstrates the difference. It shows brand new Ubuntu 16.04 on a left side where you can see vertical line in GEdit is completely solid, as it should be. On a right side it shows Ubuntu 18.04 where you can see line now has gaps that should not be there. I built a small GTK2 test app that reproduces the problem (sources at https://pastebin.com/WCH1ds4P), and using it I found that the problem occurs when libfreetype 2.8+ is used. I tested FreeType 2.6, 2.7, 2.7.1 and all of them work fine. While 2.8 and above has this gap. I am not 100% sure if this is an Ubuntu font configuration issue, or bug in FreeType, or GTK or some other Ubuntu components, but I hope someone at least can point me at the right direction. Please also check my post on AskUbuntu which has additional detail and screenshots: https://askubuntu.com/questions/1054779/incorrect-font- glyphs-rendering-in-gtk-applications-in-ubuntu-18-04 ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications https://bugs.launchpad.net/bugs/1783452 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.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 1783571] [NEW] Set Yaru as default
Public bug reported: Set Yaru as default ubuntu 18.10 theme. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~didrocks/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/350879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in ubuntu-settings package in Ubuntu: New Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1783571/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
This bug was fixed in the package console-setup - 1.178ubuntu6
---
console-setup (1.178ubuntu6) cosmic; urgency=medium
* keyboard-configuration.{config,templates}: There is no good default for
layout toggling, stop pretending there is. Console users can set one
with dpkg-reconfigure or editing /etc/defaults/keyboard (LP: #1762952)
-- Adam Conrad Wed, 25 Jul 2018 05:50:59 -0600
** Changed in: console-setup (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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative shortcut for layout switching Alt+Shift unexpectedly set
by default
Status in console-setup package in Ubuntu:
Fix Released
Status in gnome-control-center package in Ubuntu:
Invalid
Status in console-setup source package in Bionic:
Confirmed
Status in gnome-control-center source package in Bionic:
Invalid
Bug description:
[Impact]
The keyboard-configuration package provides a tool for configuring the
keyboard via /etc/default/keyboard. However, there are desktop GUIs
which provide such tools as well, and in the case of gnome-control-
center it has another idea of what /etc/default/keyboard should
contain. In short: The different tools don't play well together.
The proposed upload does not claim to fix all issues with this
incompatibility. But one of the annoyances is that a pure upgrade of
the keyboard-configuration package may result in a changed keyboard
configuration without the user asking for it. The proposed upload does
address that particular issue on desktop systems.
[Test Case]
1. On an Ubuntu 18.04 system, make sure that the contents of
/etc/default/keyboard is 'the g-c-c style', for instance:
XKBLAYOUT=se,us
BACKSPACE=guess
XKBVARIANT=,
2. Reboot.
3. Upgrade to the version of the keyboard-configuration package in
bionic-proposed.
=> Find that /etc/default/keyboard was not changed through the
upgrade.
4. Run the command
sudo dpkg-reconfigure keyboard-configuration
=> Find that you are now offered to change your keyboard
configuration.
[Regression Potential]
As a result of this upload, and unlike before, no keyboard
configuration will happen behind the scenes on a desktop system due to
an upgrade of the keyboard-configuration package. This is the desired
change, and I can't think of a case when a user would want the
configuration to be changed without having asked for it.
[Original description]
Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
18.04
Steps to reproduce:
1. Define two keyboard input methods in Settings -> Region & Language ->
Input Sources
2. Open several applications
3. Observe that application windows can be iterated with Alt + Tab
4. Once application window iteration was begun with Alt + Tab, try to iterate
backwards with Alt + Shift + Tab.
5. Try to change keyboard input method switching hotkeys in Settings ->
Region & Language -> Input Sources -> Options.
6. Observe that Keyboard shortcut for "Alternative switch to next source" is
set to "Alt + Shift" and that keyboard shortcuts can only be changed in
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
7. Observe that the shortcut for "Alternative switch to next source" is not
available for configuration in Settings -> Devices -> Keyboard -> Keyboard
Shortcuts.
Actual state:
* Performing step 4 does not select the previous app in application switcher
but instead changes keyboard input method.
Expected state:
* The shortcut for "Alternative switch to next source" can be changed and /
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
Notes:
* The above was working fine in Ubuntu 17.10. I assume "Alternative switch to
next source" did not exist in that version of Gnome Shell.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1776475] Re: Unlocking existing session often requires several attempts.
Sometimes a variant of the bug happens: after typing password, the expected session does not happen. Instead, a black screen with a white message on center, saying that session is locked and I have to wait for a moment. About 20 seconds later, a lightdm login greeter appears and only after typing the correct password *again*, I can access my session. I just experienced that variant and captured logs (journalctl) of it. I compared with journalctl logs when unlocking. Again, I don't see anything really salient in logs. I can post them here if useful. Any hint appreciated. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: New Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
** Changed in: console-setup (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: console-setup (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => Adam Conrad (adconrad) -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Committed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1690933] Re: isc-dhcp-server/dhcpd listens on 0.0.0.0:67/UDP no matter which interfaces is specified
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1690933 Title: isc-dhcp-server/dhcpd listens on 0.0.0.0:67/UDP no matter which interfaces is specified Status in isc-dhcp package in Ubuntu: Confirmed Bug description: The behaviour of the `systemd` unit `isc-dhcp-server.service` is the same as on the command line: both `sudo dhcpd` and `sudo dhcpd p18p1` (where `p18p1` is the name of a network interfaces) cause the daemon to listen on all interfaces according to `sudo netstat -tupln | grep :67`: udp0 0 0.0.0.0:67 0.0.0.0:* 5382/dnsmasq The `isc-dhcp-server6.service` unit is deactivated. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: isc-dhcp-server 4.3.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 15 23:41:54 2017 DhServerLeases: InstallationDate: Installed on 2015-04-20 (756 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: Upgraded to zesty on 2017-05-05 (9 days ago) mtime.conffile..etc.dhcp.dhcpd.conf: 2017-05-15T23:37:21.502892 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1690933/+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 1780842] Re: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nv
Solution in bug 1753796 seems to solve the issue. -- 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/1780842 Title: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nvidia-396 396.26-0ubuntu1 Status in mesa package in Ubuntu: Confirmed Bug description: The major system change occurred when I upgraded the nvidia driver. At that point I have a system dependency issue with lib-mesa0 trying to overwrite a file that the nvidia driver created. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglx-mesa0 18.0.0~rc5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.26 Mon Apr 30 18:01:39 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libglx-mesa0:amd64: Install libglx-mesa0:i386: Install libglapi-mesa:i386: Install libglapi-mesa:amd64: Install NULL: ConfigurePending Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jul 9 14:07:16 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-24-generic, x86_64: installed nvidia-396, 396.26, 4.15.0-24-generic, x86_64: installed DpkgTerminalLog: Preparing to unpack .../libglx-mesa0_18.0.5-0ubuntu0~18.04.1_amd64.deb ... De-configuring libglx-mesa0:i386 (18.0.0~rc5-1ubuntu1) ... Unpacking libglx-mesa0:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc5-1ubuntu1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libglx-mesa0_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nvidia-396 396.26-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nvidia-396 396.26-0ubuntu1 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11ad] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 1060 Mobile] [1462:11ad] InstallationDate: Installed on 2018-05-30 (40 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GS63VR 7RF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=e77cd1c5-8736-401d-bd7f-0f4ecc27bfcb ro quiet splash intel_iommu=on vt.handoff=1 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.2 Renderer: Software SourcePackage: mesa Title: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nvidia-396 396.26-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16K2IMS.314 dmi.board.asset.tag: Default string dmi.board.name: MS-16K2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16K2IMS.314:bd10/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnGS63VR7RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16K2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS63VR 7RF dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1783549] [NEW] package keyboard-configuration 1.178ubuntu2.3 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro
Public bug reported: Error when i logged in ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 23:17:19 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-20 (65 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Keyboard: XKBLAYOUT="us,gr" XKBVARIANT="," BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.3 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/1783549 Title: package keyboard-configuration 1.178ubuntu2.3 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 10 Status in console-setup package in Ubuntu: New Bug description: Error when i logged in ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 24 23:17:19 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-05-20 (65 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Keyboard: XKBLAYOUT="us,gr" XKBVARIANT="," BACKSPACE="guess" XKBMODEL="pc105" XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.3 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/1783549/+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 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783377 Title: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 / bionic systemd: Installé : 237-3ubuntu10.3 Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required packages for the VPN that has the bug fixed (5.6.2-2): network-manager-strongswan: Installé : 1.4.4-1 Candidat : 1.4.4-1 Table de version : *** 1.4.4-1 300 300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 100 /var/lib/dpkg/status 1.4.2-2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages libcharon-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libcharon-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-extra-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-standard-plugins: Installé : 5.6.2-2ubuntu1 Candidat : 5.6.2-2ubuntu1 Table de version : *** 5.6.2-2ubuntu1 300 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 5.6.2-1ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Before connecting the VPN, `systemd-resolve --status` shows : DNS Servers: 192.168.1.254 # my home box resolver After connecting : DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server 192.168.1.254 # my home box resolver This seems OK, but the resolution fails as it is still using the local DNS : systemd-resolved[270]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. After issuing `systemctl reload-or-restart systemd-resolved.service`, everything seems fine. systemd-resolved[5651]: Got DNS stub UDP query packet for id 24298 systemd-resolved[5651]: Looking up RR for my.host.inside.vpn IN A. systemd-resolved[5651]: Switching to DNS server 10.0.0.254 for interface enp0s3. systemd-resolved[5651]: Cache miss for my.host.inside.vpn IN A systemd-resolved[5651]: Transaction 9273 for scope dns on enp0s3/*. systemd-resolved[5651]: Using feature level UDP+EDNS0 for transaction 9273. systemd-resolved[5651]: Using DNS server 10.0.0.254 for transaction 9273. I was hoping that `systemd-resolved` could find the new DNS without restarting its service after connecting to the VPN. Thanks for reading Best Regards, Vincent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783377/+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 1778960] Re: SRU: Update python 2.7 to the final 2.7.15 release
It sounds strange having rc1 in the LTS release of Ubuntu. I hoped that would be fixed before 18.04.1 but it seems like does not ((( -- 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/1778960 Title: SRU: Update python 2.7 to the final 2.7.15 release Status in python2.7 package in Ubuntu: New Bug description: Ubuntu 18.04 LTS shipped with the python 2.7.15 release candidate. Please let's update to the final release. Upstream changes are: - bpo-33374: Tweak the definition of PyGC_Head, so compilers do not believe it is always 16-byte aligned on x86. This prevents crashes with more aggressive optimizations present in GCC 8. - Identify as 2.7.15 instead of 2.7.15rc1 Acceptance criteria: The package builds, and the testsuite doesn't show regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1778960/+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 822041] Re: software-properties-kde Other Software list jumps on de-selection
It still happens on Lubuntu 18.04. It jumps after ticking or unticking a checkbox. -- 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/822041 Title: software-properties-kde Other Software list jumps on de-selection Status in software-properties package in Ubuntu: Confirmed Bug description: unticking a box in Other Software causes the scrollbar to jump up to the top of the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/822041/+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 520546] Re: Alt-f2 switches to virtual terminal 2
I see this also in Kubuntu 18.04 (all updates installed) Also Alt+F4 etc is doing the same (except for Alt+F1 which). -- 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/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
@Adam: Sad to hear that the proposed fix caused yet another regression, and sorry for the inconvenience it caused. On 2018-07-25 03:31, Adam Conrad wrote: > That said, I think the "run it sometimes, but not always" fix was > probably naive at best. The only two options that seem to make > sense for fixing this properly are: > > 1) Make GNOME stop writing things to that file that console-setup > doesn't understand, or > 2) Make console-setup understand the things GNOME writes to that > file. Basically it's the other way around; console-setup adds XKBOPTIONS to /etc/default/keyboard, sometimes behind the scenes, but GNOME does not include GUIs for controlling XKBOPTIONS system wide (only per user). At the same time, when you use the GNOME GUI to change the keyboard configuration system wide, it brutally drops any XKBOPTIONS in /etc/default/keyboard. I'm going to bring it up with the desktop team, and try to figure out a better approach to handle this dissonance. Then let's make sure in advance that whatever we comes up with does not interfere with the installer. -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1783527] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] Playback problem
Public bug reported: Hello, i can't hear any sound neither from the test. the audio isn't working, and, i tried to configure the speakers but linux doesn't recognize the speakers of the laptop, infect, checking the settings,i can see only headphones listed and not speakers or any other option. ]what can i do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vecio 1250 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 25 09:50:13 2018 InstallationDate: Installed on 2018-07-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1783527 Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Hello, i can't hear any sound neither from the test. the audio isn't working, and, i tried to configure the speakers but linux doesn't recognize the speakers of the laptop, infect, checking the settings,i can see only headphones listed and not speakers or any other option. ]what can i do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vecio 1250 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 25 09:50:13 2018 InstallationDate: Installed on 2018-07-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783527/+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 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
The fix for LP: #1654600 in addition to making u-u keep /var mounted also made u-u perform the upgrades in ExecStop that causes hanging when an upgrade would start/stop services. ** Changed in: unattended-upgrades (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state Status in init-system-helpers package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: In Progress Bug description: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The system hangs until the systemd ShutdownTimeout expires and systemd forcefully reboots the system. After the system is rebooted the apport package is in "iUR" state, and needs to be reinstalled to fix this. I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: unattended-upgrades 1.1ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1778219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
gaetan-quentin's workaround helped me for now: systemctl stop systemd-udevd sudo apt remove *nvidia-compute-utils* systemctl start systemd-udevd (Lenovo P51) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU Status in Bluez Utilities: Confirmed Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Changed in: init-system-helpers (Ubuntu) Status: In Progress => Invalid ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1778219 Title: unattended-upgrades hangs on shutdown, leaves system in a broken state Status in init-system-helpers package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: In Progress Bug description: When using unattended-upgrades with "InstallOnShutdown" on Bionic, the package installation on various packages hangs until the systemd ShutdownTimeout (30min) is expired and systemd kills all processes and powers off/reboots the system. This leaves packages in an unconfigured, broken state. At least sometimes this cannot be fixed with a "dpkg --configure -a", but instead requires the user to manually reinstall the package that caused the hang. This appears to be a deadlock, because the hanging commands are always "systemctl stop ..." or "systemctl restart ...", etc.. If I understand this correctly, those systemctl commands block because systemd tries to shutdown the system and tries to satisfy all dependencies for the shutdown targets before those systemctl commands could get executed, which creates a deadlock. Steps to reproduce: - Install 18.04 - activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades - disable bionic-updates in /etc/apt/sources.list (more on that later) - execute "unattended-upgrade --download-only" - reboot the system -> The upgrade on shutdown hangs when configuring the apport package. The hanging command is "systemctl stop apport-forward.socket". The system hangs until the systemd ShutdownTimeout expires and systemd forcefully reboots the system. After the system is rebooted the apport package is in "iUR" state, and needs to be reinstalled to fix this. I disabled the bionic-updates pocket in sources.list, because in the default configuration unattended-updates does not use bionic-updates, and seems to have skipped installation of apport from bionic-security (supposedly because an already newer version of apport was in bionic- updates). If my understanding of why apport initially did not get installed is correct, then this would be another problem, because it would mean that unattended-upgrades potentially does not install all available security updates when bionic-updates is enabled in sources.list (which is the default). The problem can also be reproduced without disabling bionic-updates in sources.list, but instead enabling bionic-updates in /etc/apt/apt.conf.d/50unattended-upgrades. Then, in my case, the upgrade did hang when installing the package snapd (the hanging command was "systemctl stop snapd.autoimport.service snapd.core-fixup.service snapd.service snapd.snap-repair.service snapd.snap-repair.service snapd.socket snapd.system-shutdown.service"). This leads to the same problems as described above. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: unattended-upgrades 1.1ubuntu1 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1778219/+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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
Kubuntu 18.04 on Zenbook Pro UX550VE. Also doesn't work. Tried all the suggestions like installing pm-utils and modifying logind.conf. Nothing has helped. -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+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 1783499] [NEW] systemd: Failed to send signal
Public bug reported: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: dbus systemd ** Also affects: dbus (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/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send
[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies
--- Comment From ppaid...@in.ibm.com 2018-07-25 02:53 EDT--- (In reply to comment #38) > > Could we get a verification of this package? Sorry for the delay in response, machine was not available. Now i got P8 machine where i tested the above proposed package. lscpu works fine even after guarding multiple CPU's from multiple chips. No segfault/crashes. root@powerkvm2-lp1:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):144 On-line CPU(s) list: 8-15,24-47,56-79,88-95,104-143,152-191 Thread(s) per core:8 Core(s) per socket:4 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 3325. CPU min MHz: 2061. Hypervisor vendor: horizontal Virtualization type: full L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 8-15,24-47 NUMA node1 CPU(s): 56-79,88-95 NUMA node16 CPU(s):104-143 NUMA node17 CPU(s):152-191 root@powerkvm2-lp1:~# root@powerkvm2-lp1:~# dpkg -l | grep -i util-linux ii util-linux 2.27.1-6ubuntu3.6 ppc64el miscellaneous system utilities root@powerkvm2-lp1:~# ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1732865 Title: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Status in util-linux source package in Artful: Fix Released Bug description: [Impact] lscpu fails to list CPU max and min frequencies if some CPUs are guarded. [Regression potential] Isolated change to lscpu min/max CPU frequency output, so the worst that could happen is that it fails to work elsewhere. [Test case] 1. Clone https://github.com/open-power/op-test-framework 2. Run this command to GUARD the cpu. ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert 3. Repeat again, so that multiple CPUs are guarded. 4. Run lscpu 5. Observe that no CPU frequencies are displayed: CPU max MHz: (null) CPU min MHz: (null) 6. Install util-linux from -proposed. 7. Run lscpu again 8. Observe that max and min CPU frequencies are correctly displayed. == Comment: #0 - Pridhiviraj Paidipeddi - 2017-01-03 05:34:32 == ---Problem Description--- After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies Contact Information = ppaid...@in.ibm.com ---uname output--- Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = PowerNV 8284-22A ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Read lscpu output 2. Inject HMI Non recoverable error three times 3. Read lscpu output again compare the output cpu frequencies will list as NULL Stack trace output: no Oops output: no Userspace tool common name: lscpu Userspace rpm: util-linux The userspace tool has the following bit modes: 64-bit System Dump Info: The system is not configured to capture a system dump. Userspace tool obtained from project website: na *Additional Instructions for ppaid...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach sysctl -a output output to the bug. -Attach ltrace and strace of userspace application. Before CPU's are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):112 On-line CPU(s) list: 0-71,80-103,112-127 Thread(s) per core:8 Core(s) per socket:3 Socket(s): 4 NUMA node(s): 4 Model: 2.1 (pvr 004b 0201) Model name:POWER8E (raw), altivec supported CPU max MHz: 4322. CPU min MHz: 2061. L1d cache: 64K L1i cache: 32K L2 cache: 512K L3 cache: 8192K NUMA node0 CPU(s): 0-31 NUMA node1 CPU(s): 32-63 NUMA node16 CPU(s):64-71,80-95 NUMA node17 CPU(s):96-103,112-127 After 4 cores are garded: root@p8wookie:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):96 On-line CPU(s) list: 8-55,64-71,80-103,112-127 Thread(s) per core:8 Core(s) per
[Touch-packages] [Bug 1783377] Re: systemd-resolved updated by network-manager-strongswan needed to restart to use the new dns servers
** Description changed: Ubuntu 18.04.1 / bionic + + systemd: + Installé : 237-3ubuntu10.3 Fresh install on a VM, was facing a bug when connecting to strongswan ikev2 vpn (https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705) -> Updated from cosmic the required packages for the VPN that has the bug fixed (5.6.2-2): network-manager-strongswan: - Installé : 1.4.4-1 - Candidat : 1.4.4-1 - Table de version : - *** 1.4.4-1 300 - 300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages - 100 /var/lib/dpkg/status - 1.4.2-2 500 - 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages + Installé : 1.4.4-1 + Candidat : 1.4.4-1 + Table de version : + *** 1.4.4-1 300 + 300 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages + 100 /var/lib/dpkg/status + 1.4.2-2 500 + 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages libcharon-extra-plugins: - Installé : 5.6.2-2ubuntu1 - Candidat : 5.6.2-2ubuntu1 - Table de version : - *** 5.6.2-2ubuntu1 300 - 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 100 /var/lib/dpkg/status - 5.6.2-1ubuntu2 500 - 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installé : 5.6.2-2ubuntu1 + Candidat : 5.6.2-2ubuntu1 + Table de version : + *** 5.6.2-2ubuntu1 300 + 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 100 /var/lib/dpkg/status + 5.6.2-1ubuntu2 500 + 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libcharon-standard-plugins: - Installé : 5.6.2-2ubuntu1 - Candidat : 5.6.2-2ubuntu1 - Table de version : - *** 5.6.2-2ubuntu1 300 - 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 100 /var/lib/dpkg/status - 5.6.2-1ubuntu2 500 - 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installé : 5.6.2-2ubuntu1 + Candidat : 5.6.2-2ubuntu1 + Table de version : + *** 5.6.2-2ubuntu1 300 + 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 100 /var/lib/dpkg/status + 5.6.2-1ubuntu2 500 + 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-extra-plugins: - Installé : 5.6.2-2ubuntu1 - Candidat : 5.6.2-2ubuntu1 - Table de version : - *** 5.6.2-2ubuntu1 300 - 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 100 /var/lib/dpkg/status - 5.6.2-1ubuntu2 500 - 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installé : 5.6.2-2ubuntu1 + Candidat : 5.6.2-2ubuntu1 + Table de version : + *** 5.6.2-2ubuntu1 300 + 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 100 /var/lib/dpkg/status + 5.6.2-1ubuntu2 500 + 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libstrongswan-standard-plugins: - Installé : 5.6.2-2ubuntu1 - Candidat : 5.6.2-2ubuntu1 - Table de version : - *** 5.6.2-2ubuntu1 300 - 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 100 /var/lib/dpkg/status - 5.6.2-1ubuntu2 500 - 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installé : 5.6.2-2ubuntu1 + Candidat : 5.6.2-2ubuntu1 + Table de version : + *** 5.6.2-2ubuntu1 300 + 300 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 100 /var/lib/dpkg/status + 5.6.2-1ubuntu2 500 + 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Before connecting the VPN, `systemd-resolve --status` shows : - DNS Servers: 192.168.1.254 # my home box resolver + DNS Servers: 192.168.1.254 # my home box resolver After connecting : - DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server - 192.168.1.254 # my home box resolver + DNS Servers: 10.0.0.254# DNS resolver provided by the VPN server + 192.168.1.254 # my home box resolver This seems OK, but the resolution fails as it is still using the local DNS : systemd-resolved[270]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. After issuing `systemctl reload-or-restart systemd-resolved.service`, everything seems fine. systemd-resolved[5651]: Got DNS stub UDP query packet for id 24298 systemd-resolved[5651]: Looking up RR for my.host.inside.vpn IN A. systemd-resolved[5651]: Switching to DNS server 10.0.0.254 for interface enp0s3. systemd-resolved[5651]: Cache miss for my.host.inside.vpn IN A systemd-resolved[5651]: Transaction 9273 for scope dns on enp0s3/*. systemd-resolved[5651]: Using feature level UDP+EDNS0 for transaction 9273. systemd-resolved[5651]: Using DNS server 10.0.0.254
[Touch-packages] [Bug 1778497] Re: Add a remember option to whoopsie so that users can diminish crash interactions
Are you sure that your configuration was still set to manual and not "never"? (there is a timeout bug in whoopsie-preferences which reset the condition to "never" if g-c-c is kept opened). I just tried with the -proposed version, generated a crash which can be reported (note as well that some crashes can't be reported under some condition, hence the "Continue"), and got Don't Send/Send. Marking as verified as I guess your issue is due to the above issue in -preferences (and I tested a lot of combinations) ^ ** Tags removed: verification-failed verification-failed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1778497 Title: Add a remember option to whoopsie so that users can diminish crash interactions Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Fix Committed Bug description: [ Impact ] A lot of users are bother by the number of whoopsie dialog. We introduced on "G-C-C privacy option don't allow sending manual report" bug (https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774597) a way for users to change from always reporting manually (prompting an UI) to auto reporting or never reporting, via a "Remember this in future". This only impacts the apport gtk UI, still offering the underlying capability to other UIs type without changing them. This was a goal for 18.04, but due to a lack of time, we want to introduce this in 18.04.1 [ Test Case ] * There are multiples dialog forms (a good 20 of them), but they are all covered by unit tests which have been updates. One use case would be: * Install the new version and trigger a crash * Check that the dialog has a "Remember this in future" option, check it, and click send. * Check in g-c-c UI, privacy option, that the crash reporting is now in auto mode, always send. * Revert in g-c-c to manual * Create another crash, check "Remember this…" and click don't send * Check in g-c-c UI that crash reporting is now disabled. [ Regression potential ] * The impacted code is both UI and fileutils. It's covered by an extensive testsuite, and checking under KDE has also been done to not trigger a crash. We introduce 5 new strings to translate: "Can't remember send report status settings" "Saving crash reporting state failed. Can't set auto or never reporting mode." "Remember this in future" "Relaunch this application" "Don't send" We are reusing an existing transalted string "Send problem report to the developers?" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1778497/+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 1692353] Re: systemd-fsckd : useless CR displayed on console
Interesting, I was sure we upstreamed completely systemd-fsckd. Anyway,
+1 for me, let me assign to xnox who is doing most of systemd uploads
nowdays so that he attaches it to next upload.
Many thanks!
** Changed in: systemd (Ubuntu)
Assignee: Didier Roche (didrocks) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Status: Incomplete => 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/1692353
Title:
systemd-fsckd : useless CR displayed on console
Status in systemd package in Ubuntu:
Triaged
Bug description:
Hello,
My system is "Ubuntu 16.04.2 LTS" (grep DISTRIB_DESCRIPTION /etc/lsb-
release).
The systemd package is installed:
$ dpkg -l | grep systemd
> systemd 229-4ubuntu17
I noticed that approximately 15 seconds after the boot, a useless
Carriage Return ('\r') is displayed on the console (/dev/console).
This character interacts with the display of the user currently logued in
on the console. This screws the current line, when users is pressing keys.
After monitoring system activity, I found the culprit:
/lib/systemd/system/systemd-fsckd.service
To test, run:
service systemd-fsckd stop# In case, it is still running.
service systemd-fsckd start
Go to the console, wait for approximately 15 seconds, and you see the cursor
jumping from its current position to the beginning of the line. This is the
BUG.
Note: the console is not the X11 terminal (xterm, lxterminal, etc.) ; the
console is the text tty reached with Control-Alt-F1.
The systemd-fsckd.service starts the following daemon:
/lib/systemd/systemd-fsckd
This is the daemon which displays two useless '\r' characters.
I went to:
http://packages.ubuntu.com/xenial/systemd
I downloaded:
http://archive.ubuntu.com/ubuntu/pool/main/s/systemd/systemd_229-4ubuntu10.debian.tar.xz
The file debian/patches/fsckd-daemon-for-inter-fsckd-communication.patch
contains:
+static int manager_write_console(Manager *m, const char *message) {
[...]
+if (message) {
+fprintf(console, "\r%s\r%n", message, );
+if (m->clear < (size_t)l)
+m->clear = (size_t)l;
+} else {
+fputc('\r', console);
+for (j = 0; j < m->clear; j++)
+fputc(' ', console);
+fputc('\r', console);
+}
So, when no message was previously displayed, "m->clear" is still set
to 0.
Then, when the program ends it calls:
+/* clear last line */
+manager_write_console(m, NULL);
However, in the "else" above, two '\r' characters are displayed, surrounding
no space characters.
So, when no message was previously displayed, there is nothing to clear, so
no '\r' character to display.
A trivial patch is attached. It is untested.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1692353/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Update: We have made sofar couple of discoveries, thanks to Petr Jediny. We suspected OpenSSL incompatibility in the OS, so as the PEAP is creating underlying TLS tunnel for auth and we see an error in wpa_supplicant regarding TLS negotiation (hello). tl;dr - Cypher set of Ubuntu bionic do not match (pass/negotiate) ciphers on our appliance/radius (We uses Aruba appliances, the firmware is not up to date with latest security standards; Aruba is working last three months on an update (obviously without pressure)). --- The radius/server or Aruba is accepting TLS_RSA_WITH_3DES_EDE_CBC_SHA The mentioned cipher suite is mandated by https://tools.ietf.org/html/rfc5216#section-2.4, but the TLS_RSA_WITH_AES_128_CBC_SHA should be supported too It looks like the radius server is not accepting any of these suggested by ubuntu bionic wpa_supplicant: Cipher Suites (28 suites) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x009f) Cipher Suite: TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca9) Cipher Suite: TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8) Cipher Suite: TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xccaa) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x009e) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 (0xc024) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x006b) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 (0xc023) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (0x0067) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (0xc00a) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (0xc009) Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_RSA_WITH_AES_256_GCM_SHA384 (0x009d) Cipher Suite: TLS_RSA_WITH_AES_128_GCM_SHA256 (0x009c) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA256 (0x003d) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA256 (0x003c) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_EMPTY_RENEGOTIATION_INFO_SCSV (0x00ff) TLS_RSA_WITH_AES_128_CBC_SHA is mentioned. We think the issue directly relates to remove 3DES from Bionic: openssl ciphers -V '3DES' Error in cipher list 13040823744:error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match:../ssl/ssl_lib.c:2129: --- Note similar issue was discovered on Fedora as well and has this workaround: https://www.systutorials.com/docs/linux/man/8-update-crypto-policies/ and set "LEGACY" crypto policy $ update-crypto-policies --set LEGACY --- I suggest keeping the bug open for a while, just for case somebody will come with a workaround. In a long-term this is not the problem of the Ubuntu or gnome, but the list of supported ciphers Ubuntu Bionic vs. HW appliances you connect to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: Connection to open or WPA secured wifi works without any issues. Connection to WPA2/PEAP fails. Repeatedly asks for username/password. Possible gnome-shell integration issue. The system was updated from Xenial to Bionic in mid-January. At that time this WPA2/PEAP setup worked without any issues. With the updates coming in the last week of January / First February week - the bug was experienced. 1) ➜ syncthing git:(master) lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2) - up to date packages [code] ➜ cat /etc/apt/sources.list |egrep -v '^#' deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted [/code] Note: # some pkg version related to problem might be from proposed-updates repo 2b) [code] dpkg -l |egrep -i 'network manager|networkm|libnm' ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4
[Touch-packages] [Bug 1783479] Re: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error),
** 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/1783479 Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped Status in console-setup package in Ubuntu: New Bug description: I fixed my many random crashes by adding this to the grub menu: intel_idle.max_cstate=1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 24 18:35:35 2018 DuplicateSignature: package:console-setup:1.178ubuntu2.3 Setting up console-setup (1.178ubuntu2.3) ... update-initramfs: deferring update (trigger activated) dpkg: error processing package console-setup (--configure): installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped ErrorMessage: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-07-20 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped 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/1783479/+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 1783479] [NEW] package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error
Public bug reported: I fixed my many random crashes by adding this to the grub menu: intel_idle.max_cstate=1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 24 18:35:35 2018 DuplicateSignature: package:console-setup:1.178ubuntu2.3 Setting up console-setup (1.178ubuntu2.3) ... update-initramfs: deferring update (trigger activated) dpkg: error processing package console-setup (--configure): installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped ErrorMessage: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-07-20 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped 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/1783479 Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped Status in console-setup package in Ubuntu: New Bug description: I fixed my many random crashes by adding this to the grub menu: intel_idle.max_cstate=1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: console-setup-linux:amd64: Install console-setup:amd64: Install keyboard-configuration:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue Jul 24 18:35:35 2018 DuplicateSignature: package:console-setup:1.178ubuntu2.3 Setting up console-setup (1.178ubuntu2.3) ... update-initramfs: deferring update (trigger activated) dpkg: error processing package console-setup (--configure): installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped ErrorMessage: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2018-07-20 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.3 failed to install/upgrade: installed console-setup package post-installation script subprocess was killed by signal (Bus error), core dumped 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/1783479/+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
