[Touch-packages] [Bug 1809217] Re: Image icons appear as black rectangles instead of previews
Cela pourrait être lié au démarrage de votre noyau en mode de
récupération avec "nomodeset":
[ 36.451] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=eb14491b-f949-4add-
b1ee-9395094ec859 ro recovery nomodeset
S'il vous plaît essayez de redémarrer et dès que l'écran violet
apparaît, appuyez sur Echap. Maintenant, dans les menus, sélectionnez un
noyau standard qui n'est pas en mode de récupération ("recovery").
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1809217
Title:
Image icons appear as black rectangles instead of previews
Status in gtk+3.0 package in Ubuntu:
Incomplete
Bug description:
Sorry, but I'm a french guy and my english isn't fluent enough for telling
you what is happenning to me . So I must follow in french.
Quand j'enregistre des photos ou des pages sur le net (Pinterest, FB, Tumblr,
etc...) sur mon disque dur, normalement celles-ci apparaissent telles quelles
dans le dossier que j'ai sélectionné, je n'ai pas besoin de les ouvrir avec le
visionneur d'images. Mais là, depuis environ trois semaines, quand je
télécharge un document celui-ci apparait sous la forme d'un petit rectangle
noir sur lequel est écrit JPG ou PNG. Ce petit rectangle noir que je peux
ouvrir en double-cliquant ou en me servant d'un visionneur d'image, mais qui
apparait à nouveau à la place de l'image ou du document une fois que j'ai cessé
de le visionner.
Ce malencontreux phénomène s'étend maintenant à des documents antérieurement
enregistrés, ce qui rend mes dossiers illisibles.
Si je n'excelle pas en anglais, je ne suis pas meilleur en informatique. Donc
si vous pensez pouvoir m'aider, faites le de la manière la plus claire qui
soit. Please !!!
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
.tmp.unity_support_test.1:
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Dec 20 07:33:36 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
NVIDIA Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1) (prog-if 00
[VGA controller])
Subsystem: Gigabyte Technology Co., Ltd NV44 [GeForce 6200 LE] [1458:3400]
InstallationDate: Installed on 2015-12-26 (1089 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: Dell Inc. OptiPlex 360
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
root=UUID=eb14491b-f949-4add-b1ee-9395094ec859 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0T656F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA00:bd08/12/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
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.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
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
xserver.bootTime: Thu Dec 20 08:31:42 2018
xserver.configfile: default
xserver.devices:
inputPower Button KEYBOARD, id 6
inputPower Button KEYBOARD, id 7
input USB Keyboard KEYBOARD, id 8
input USB Keyboard KEYBOARD, id 9
inputMicrosoft Microsoft Basic Optical Mouse v2.0 MOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1809217/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809217] Re: Image icons appear as black rectangles instead of previews
This might be related to your kernel starting in recovery mode with "nomodeset": [36.451] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=eb14491b-f949-4add- b1ee-9395094ec859 ro recovery nomodeset Please try rebooting and as soon as the purple screen appears, hit Esc. Now in the menus select a standard kernel that is not recovery mode. ** Summary changed: - ??? + Image icons appear as black rectangles instead of previews ** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu) ** Tags added: nouveau -- 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/1809217 Title: Image icons appear as black rectangles instead of previews Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Sorry, but I'm a french guy and my english isn't fluent enough for telling you what is happenning to me . So I must follow in french. Quand j'enregistre des photos ou des pages sur le net (Pinterest, FB, Tumblr, etc...) sur mon disque dur, normalement celles-ci apparaissent telles quelles dans le dossier que j'ai sélectionné, je n'ai pas besoin de les ouvrir avec le visionneur d'images. Mais là, depuis environ trois semaines, quand je télécharge un document celui-ci apparait sous la forme d'un petit rectangle noir sur lequel est écrit JPG ou PNG. Ce petit rectangle noir que je peux ouvrir en double-cliquant ou en me servant d'un visionneur d'image, mais qui apparait à nouveau à la place de l'image ou du document une fois que j'ai cessé de le visionner. Ce malencontreux phénomène s'étend maintenant à des documents antérieurement enregistrés, ce qui rend mes dossiers illisibles. Si je n'excelle pas en anglais, je ne suis pas meilleur en informatique. Donc si vous pensez pouvoir m'aider, faites le de la manière la plus claire qui soit. Please !!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 20 07:33:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd NV44 [GeForce 6200 LE] [1458:3400] InstallationDate: Installed on 2015-12-26 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: Dell Inc. OptiPlex 360 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=eb14491b-f949-4add-b1ee-9395094ec859 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0T656F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd08/12/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Dec 20 08:31:42 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputMicrosoft Microsoft Basic Optical Mouse v2.0 MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1809217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809217] [NEW] ???
Public bug reported: Sorry, but I'm a french guy and my english isn't fluent enough for telling you what is happenning to me . So I must follow in french. Quand j'enregistre des photos ou des pages sur le net (Pinterest, FB, Tumblr, etc...) sur mon disque dur, normalement celles-ci apparaissent telles quelles dans le dossier que j'ai sélectionné, je n'ai pas besoin de les ouvrir avec le visionneur d'images. Mais là, depuis environ trois semaines, quand je télécharge un document celui-ci apparait sous la forme d'un petit rectangle noir sur lequel est écrit JPG ou PNG. Ce petit rectangle noir que je peux ouvrir en double-cliquant ou en me servant d'un visionneur d'image, mais qui apparait à nouveau à la place de l'image ou du document une fois que j'ai cessé de le visionner. Ce malencontreux phénomène s'étend maintenant à des documents antérieurement enregistrés, ce qui rend mes dossiers illisibles. Si je n'excelle pas en anglais, je ne suis pas meilleur en informatique. Donc si vous pensez pouvoir m'aider, faites le de la manière la plus claire qui soit. Please !!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 20 07:33:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd NV44 [GeForce 6200 LE] [1458:3400] InstallationDate: Installed on 2015-12-26 (1089 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: Dell Inc. OptiPlex 360 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=eb14491b-f949-4add-b1ee-9395094ec859 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0T656F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd08/12/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Dec 20 08:31:42 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputMicrosoft Microsoft Basic Optical Mouse v2.0 MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1809217 Title: ??? Status in xorg package in Ubuntu: New Bug description: Sorry, but I'm a french guy and my english isn't fluent enough for telling you what is happenning to me . So I must follow in french. Quand j'enregistre des photos ou des pages sur le net (Pinterest, FB, Tumblr, etc...) sur mon disque dur, normalement celles-ci apparaissent telles quelles dans le dossier que j'ai sélectionné, je n'ai pas besoin de les ouvrir avec le visionneur d'images. Mais là, depuis environ trois semaines, quand je télécharge un document celui-ci apparait sous la forme d'un petit rectangle noir sur lequel est écrit JPG ou PNG. Ce petit rectangle noir que je peux ouvrir en double-cliquant ou en me servant d'un visionneur d'image, mais qui apparait à nouveau à la place de l'image ou du document une fois que j'ai cessé de le visionner. Ce malencontreux phénomène s'étend maintenant à des documents antérieurement enregistrés, ce qui rend mes dossiers illisibles. Si je n'excelle pas en anglais,
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
This is very clear now, thank you! ** Changed in: util-linux (Ubuntu) Status: Incomplete => New ** Changed in: ubuntu-power-systems Status: Incomplete => New -- 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/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: New Status in util-linux package in Ubuntu: New Bug description: ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Kernel version 4.19.10 has the fix. To install run: ukuu --install v4.19.10 And reboot. -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) 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/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR 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/1742852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I can confirm the following fixed the no-sound issue on my UX533 per buchovagabond's post above: sudo ukuu --install v4.19.10 Cheers, Craig -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. 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: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
Verified alsa-lib 1.1.6-1ubuntu1.2, it worked well. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in alsa-lib source package in Cosmic: Fix Committed Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This bug was fixed in the package linux-oem - 4.15.0-1030.35 --- linux-oem (4.15.0-1030.35) bionic; urgency=medium * linux-oem: 4.15.0-1030.35 -proposed tracker (LP: #1806663) * Add HMS CAN driver for Dell Edge Gateways (LP: #1807339) - SAUCE: (no-up) add IXXAT USB-to-CAN driver * Add support for 0cf3:535b QCA_ROME device (LP: #1807333) - Bluetooth: btusb: Add support for 0cf3:535b QCA_ROME device * Add support for Dell DW5821e WWAN/GPS module (LP: #1807342) - qmi_wwan: add support for the Dell Wireless 5821e module - qmi_wwan: fix interface number for DW5821e production firmware - USB: option: add support for DW5821e * Fix Terminus USB hub that may breaks connected USB devices after S3 (LP: #1806850) - USB: Wait for extra delay time after USB_PORT_FEAT_RESET for quirky hub * The line-out on the Dell Dock station can't work (LP: #1806532) - ALSA: usb-audio: Allow to override the longname string - ALSA: usb-audio: Give proper vendor/product name for Dell WD15 Dock - ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock * Enable new Realtek card reader (LP: #1806335) - USB: usb-storage: Add new IDs to ums-realtek - SAUCE: (noup) USB: usb-storage: Make MMC support optional on ums-realtek [ Ubuntu: 4.15.0-43.46 ] * linux: 4.15.0-43.46 -proposed tracker (LP: #1806659) * System randomly hangs during suspend when mei_wdt is loaded (LP: #1803942) - SAUCE: base/dd: limit release function changes to vfio driver only * Workaround CSS timeout on AMD SNPS 3.0 xHC (LP: #1806838) - xhci: Allow more than 32 quirks - xhci: workaround CSS timeout on AMD SNPS 3.0 xHC * linux-buildinfo: pull out ABI information into its own package (LP: #1806380) - [Packaging] limit preparation to linux-libc-dev in headers - [Packaging] commonise debhelper invocation - [Packaging] ABI -- accumulate abi information at the end of the build - [Packaging] buildinfo -- add basic build information - [Packaging] buildinfo -- add firmware information to the flavour ABI - [Packaging] buildinfo -- add compiler information to the flavour ABI - [Packaging] buildinfo -- add buildinfo support to getabis - [Config] buildinfo -- add retpoline version markers * linux packages should own /usr/lib/linux/triggers (LP: #1770256) - [Packaging] own /usr/lib/linux/triggers * CVE-2018-12896 - posix-timers: Sanitize overrun handling * CVE-2018-16276 - USB: yurex: fix out-of-bounds uaccess in read handler * CVE-2018-10902 - ALSA: rawmidi: Change resized buffers atomically * CVE-2018-18710 - cdrom: fix improper type cast, which can leat to information leak. * CVE-2018-18690 - xfs: don't fail when converting shortform attr to long form during ATTR_REPLACE * CVE-2018-14734 - infiniband: fix a possible use-after-free bug * CVE-2018-18445 - bpf: 32-bit RSH verification must truncate input before the ALU op * Packaging resync (LP: #1786013) - [Packaging] update helper scripts -- Chia-Lin Kao (AceLan) Sat, 08 Dec 2018 11:02:54 +0800 ** Changed in: linux-oem (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-10902 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12896 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-14734 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-16276 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18445 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18690 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-18710 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in alsa-lib source package in Cosmic: Fix Committed Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI,
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Install gnome-shell 3.28.3-0ubuntu0.18.04.4 from the -proposed repo fixed the problem for me! Running Ubuntu 18.04. Thanks for the fix! $ apt list gnome-shell Listing... Done gnome-shell/now 3.28.3-0ubuntu0.18.04.4 amd64 [installed,local] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764628] Comment bridged from LTC Bugzilla
--- Comment From bssrika...@in.ibm.com 2018-12-19 23:26 EDT--- Upstream testing with util-linux [@ https://github.com/karelzak/util-linux] 1. Tested version: util-linux 2.26.2 Result: root@guest:/home/srik/util-linux# ./lscpu -V lt-lscpu from util-linux 2.26.2 root@guest:/home/srik/util-linux# ./lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):64 On-line CPU(s) list: 0-63 Thread(s) per core:4 Core(s) per socket:8 Socket(s): 2 NUMA node(s): 1 Model: IBM pSeries (emulated by qemu) L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-63 2. Tested version: util-linux 2.27.1 Result: root@guest:/home/srik/util-linux# ./lscpu -V lt-lscpu from util-linux 2.27.1 root@guest:/home/srik/util-linux# ./lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):64 On-line CPU(s) list: 0-63 Thread(s) per core:4 Core(s) per socket:8 Socket(s): 2 NUMA node(s): 1 Model: IBM pSeries (emulated by qemu) > Hypervisor vendor: KVM --> correct > Virtualization type: para --> correct L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-63 On Ubuntu 16.04.5 : #lscpu -V lscpu from util-linux 2.27.1 root@guest:~# dpkg -l | grep util-linux ii util-linux2.27.1-6ubuntu3.6 ppc64el miscellaneous system utilities Result: root@guest:~# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):64 On-line CPU(s) list: 0-63 Thread(s) per core:4 Core(s) per socket:8 Socket(s): 2 NUMA node(s): 1 Model: 2.0 (pvr 004d 0200) Model name:POWER8 (architected), altivec supported > Hypervisor vendor: horizontal --> not ok > Virtualization type: full --> not ok L1d cache: 64K L1i cache: 32K NUMA node0 CPU(s): 0-63 I hope its clear now. --- Comment From bssrika...@in.ibm.com 2018-12-19 23:27 EDT--- I am on: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: 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/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: Incomplete Status in util-linux package in Ubuntu: Incomplete Bug description: ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
After installing libdvd-pkg and running: sudo dpkg-reconfigure libdvd-pkg please ensure it has also worked: $ dpkg -l | grep dvdcss which should show something like: ii libdvdcss-dev:amd641.4.2-1~local amd64library for accessing encrypted DVDs - development files ii libdvdcss2:amd64 1.4.2-1~local amd64library for accessing encrypted DVDs -- 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/1809044 Title: DVD playback error: unable to play . . . DVD source is required . . . Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards, to complete compilation. Inserted known-good DVD and clicked on "Open in Videos" which launched the Totem player. Error msg: "Unable to play the file, DVD source is required, but is not installed." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
I don't think this would be a regression. I don't think we've never been allowed to ship the required components for DVD video payback, which implies that it probably never worked out of the box in previous releases either. And it seems the instructions for how to get it working have changed over the years so I don't know what works right now... Please also try: sudo apt install ubuntu-restricted-extras sudo apt install libdvd-pkg ** Changed in: gstreamer1.0 (Ubuntu) Status: Incomplete => New ** Changed in: totem (Ubuntu) Status: Incomplete => New -- 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/1809044 Title: DVD playback error: unable to play . . . DVD source is required . . . Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards, to complete compilation. Inserted known-good DVD and clicked on "Open in Videos" which launched the Totem player. Error msg: "Unable to play the file, DVD source is required, but is not installed." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
@Daniel: sorry . . . forgot to mention that ubuntu-restricted-extras(which depends on *-addons) _is_ installed. I also ensured that all other dependencies are installed according to: https://help.ubuntu.com/stable/ubuntu-help/video-dvd-restricted.html.en This definitely feels like a regression.. On Wed, Dec 19, 2018 at 7:30 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > I wouldn't be surprised if MPEG-2 support was missing by default due to > licensing/patent restrictions. > > Please try this command: > > sudo apt install ubuntu-restricted-addons > > and tell us if it improves the situation. > > > ** Changed in: gstreamer1.0 (Ubuntu) >Status: New => Incomplete > > ** Changed in: totem (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1809044 > > Title: > DVD playback error: unable to play . . . DVD source is required . . . > > Status in gstreamer1.0 package in Ubuntu: > Incomplete > Status in totem package in Ubuntu: > Incomplete > > Bug description: > Successful installation of libdvd-pkg and dpkg-reconfigure, > afterwards, to complete compilation. > > Inserted known-good DVD and clicked on "Open in Videos" which launched > the Totem player. > > Error msg: "Unable to play the file, DVD source is required, but is > not installed." > > DVD will play normally in VLC player after installation on same > machine. > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: libgstreamer1.0-0 1.14.4-1 > ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 > Uname: Linux 4.18.0-12-generic x86_64 > ApportVersion: 2.20.10-0ubuntu13.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Dec 18 15:21:45 2018 > InstallationDate: Installed on 2018-11-13 (34 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 > (20181017.3) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gstreamer1.0 > UpgradeStatus: No upgrade log present (probably fresh install) > XorgLog: Error: [Errno 2] No such file or directory: > '/var/log/Xorg.0.log' > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions > -- 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/1809044 Title: DVD playback error: unable to play . . . DVD source is required . . . Status in gstreamer1.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards, to complete compilation. Inserted known-good DVD and clicked on "Open in Videos" which launched the Totem player. Error msg: "Unable to play the file, DVD source is required, but is not installed." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
put the bugzilla link in the email. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1200829] Re: Regression: Enabling typical bindings in "Desktop-based Viewport Switching" breaks scrollwheel scrolling in some windows with a usb mouse on a laptop
** Changed in: xorg-server Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1200829 Title: Regression: Enabling typical bindings in "Desktop-based Viewport Switching" breaks scrollwheel scrolling in some windows with a usb mouse on a laptop Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Test Case: On a laptop connect a usb mouse (using a logitech wireless "Anywhere mouse mx" here Enable theses Desktop-based Viewport Switching binding's Set prev & next to typical settings, (next = button 5, prev = button 4 Try to scroll in any of these windows using the mouse scroll-wheel - nautilus gedit synaptic dconf-editor help (Ubuntu Desktop guide Software-updater > details 'Open files' window sidebar windows in RB & totem preferences in audacious There could be a few more On the other hand many others work ok, short list - Dash Scroll on Desktop gnome-terminal libreoffice-writer ccsm all browsers preferences & playlist in vlc Note all of the no scroll apps work fine with touchpad scrolling Have tried disabling the touchpad, ect. to no avail Related to this bug, same workaround to alleviate https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1184159 Commit reverted packages for 13.10 are here https://launchpad.net/~mc3man/+archive/test-scroll ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 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: Fri Jul 12 23:46:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-06-23 (20 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=c6ab7418-5252-48e1-b7ab-cc21291285f4 ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "My Graphics" Driver "nouveau" Option "GLXVBlank" "on" EndSection dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1200829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
** Changed in: xorg-server Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1200829]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/566. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1200829 Title: Regression: Enabling typical bindings in "Desktop-based Viewport Switching" breaks scrollwheel scrolling in some windows with a usb mouse on a laptop Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Test Case: On a laptop connect a usb mouse (using a logitech wireless "Anywhere mouse mx" here Enable theses Desktop-based Viewport Switching binding's Set prev & next to typical settings, (next = button 5, prev = button 4 Try to scroll in any of these windows using the mouse scroll-wheel - nautilus gedit synaptic dconf-editor help (Ubuntu Desktop guide Software-updater > details 'Open files' window sidebar windows in RB & totem preferences in audacious There could be a few more On the other hand many others work ok, short list - Dash Scroll on Desktop gnome-terminal libreoffice-writer ccsm all browsers preferences & playlist in vlc Note all of the no scroll apps work fine with touchpad scrolling Have tried disabling the touchpad, ect. to no avail Related to this bug, same workaround to alleviate https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1184159 Commit reverted packages for 13.10 are here https://launchpad.net/~mc3man/+archive/test-scroll ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 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: Fri Jul 12 23:46:16 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-06-23 (20 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130621) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=c6ab7418-5252-48e1-b7ab-cc21291285f4 ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "My Graphics" Driver "nouveau" Option "GLXVBlank" "on" EndSection dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1200829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240957]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/566. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
Upstream for util-linux is at https://github.com/karelzak/util-linux Has this been reported as an issue there before, and now fixed? Can you find the relevant versions that fix this in that repository? -- 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/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: Incomplete Status in util-linux package in Ubuntu: Incomplete Bug description: ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
I'm confused reading this bug report. As the comments repeatedly mention identical version numbers, stating that both the issue is present and not present, requesting to pick up the version that is already in xenial, and later stating again that things are not fixed. Clearly v2.27.1-6ubuntu3.6 is still affected and is not the one that is needed. Do you have upstream git commit ids that resolve the issue for you? What does "Later we checked with upstream/util-linux_2.27.1-6ubuntu3.5 level and not able to see the issue." mean? i do not understand the meaning of this sentence. Which upstream git commit, or git tag, or released version number appear to work correctly? -- 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/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: Incomplete Status in util-linux package in Ubuntu: Incomplete Bug description: ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Done, for sending an email to them using that CC you mean without the bugzilla site? Should I just put the bugzilla link in that email? -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809110] Re: Intel drivers
Ubuntu already comes with all "Intel drivers" pre-installed. What is the problem you're trying to solve? ** 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/1809110 Title: Intel drivers Status in Ubuntu: Incomplete Bug description: i wanna see if it helps with setting up vagrant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Wed Dec 19 14:33:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2018-01-28 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. 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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804748] Re: s390x qemu vt220 terminal, tput cols and lines is wrong
Can I have like vt1-7, on per-HMC/zvm/user basis, exported and wired up via HMC/c3270/qemu-serial? =) ** No longer affects: ncurses (Ubuntu) ** No longer affects: qemu (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: ubuntu-z-systems Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1804748 Title: s390x qemu vt220 terminal, tput cols and lines is wrong Status in Ubuntu on IBM z Systems: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: s390x qemu vt220 terminal, tput cols and lines is reported as 80x24, whilst that's not true. The number of columns is semi-true, as the shell wraps them, however, one can print things beyond 80 cols. Ideally resizing qemu window, should manage to report the actual number of lines and columns to the underlying terminal. Similarly, one should be able to resize ASCII terminal window in HMC beyond 80x24. These days everyone has HD widescreen monitors, there is no reason to limit to 80x24. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1804748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808806] Re: ????
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** 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/1808806 Title: Status in Ubuntu: Incomplete Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-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: Mon Dec 17 13:48:00 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:078c] InstallationDate: Installed on 2018-11-16 (30 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_LU:fr PATH=(custom, no user) LANG=fr_LU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed root=UUID=12ce8976-9f9f-49bf-ae0c-ba49a024ad56 ro locale=fr_FR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.1 dmi.board.name: 0FGN4M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.1:bd04/20/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0FGN4M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 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.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 17 10:02:54 2018 xserver.configfile: default xserver.errors: evdev: "USB OPTICAL MOUSE ": Unable to open evdev device "/dev/input/event7". PreInit returned 2 for ""USB OPTICAL MOUSE "" SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5595 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201613 Importance: Unknown Status: Unknown -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=109102 Importance: Unknown Status: Unknown -- 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in Mesa: Unknown Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
I wouldn't be surprised if MPEG-2 support was missing by default due to licensing/patent restrictions. Please try this command: sudo apt install ubuntu-restricted-addons and tell us if it improves the situation. ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Incomplete ** Changed in: totem (Ubuntu) Status: New => Incomplete -- 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/1809044 Title: DVD playback error: unable to play . . . DVD source is required . . . Status in gstreamer1.0 package in Ubuntu: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards, to complete compilation. Inserted known-good DVD and clicked on "Open in Videos" which launched the Totem player. Error msg: "Unable to play the file, DVD source is required, but is not installed." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
you might have a try with adding ti...@suse.de and kail...@realtek.com to the CC list. And send an email to them with cc alsa-de...@alsa-project.org would be better. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807286] Re: systemd SEGV freezing on install of virtualbox
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1807286 Title: systemd SEGV freezing on install of virtualbox Status in systemd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: most of the information has been reported at VBox here: https://forums.virtualbox.org/viewtopic.php?f=7=90643 when installing VBox this happens: _ sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run [sudo] password for kinghat: Verifying archive integrity... All good. Uncompressing VirtualBox for Linux installation. VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer Installing VirtualBox to /opt/VirtualBox Python found: python, installing bindings... Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST): systemd[1]: Caught , dumped core as pid 5201. Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST): systemd[1]: Freezing execution. Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Connection timed out Failed to start vboxdrv.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) See system logs and 'systemctl status vboxdrv.service' for details. Failed to start vboxballoonctrl-service.service: Connection timed out See system logs and 'systemctl status vboxballoonctrl-service.service' for details. Failed to start vboxautostart-service.service: Connection timed out See system logs and 'systemctl status vboxautostart-service.service' for details. Failed to start vboxweb-service.service: Connection timed out See system logs and 'systemctl status vboxweb-service.service' for details. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual /opt/VirtualBox/UserManual.pdf and in the user FAQ http://www.virtualbox.org/wiki/User_FAQ We hope that you enjoy using VirtualBox. _ VB then starts fine. after reboot none of the VMs fail to launch. ive had weird install issues with VBox on 18.10 for many months. Description:Ubuntu 18.10 Release:18.10 VirtualBox-5.2.23-126798-Linux_amd64.run http://paste.debian.net/hidden/ee22b12a/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: virtualbox (not installed) ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 6 17:21:15 2018 InstallationDate: Installed on 2018-08-20 (108 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: virtualbox UpgradeStatus: Upgraded to cosmic on 2018-10-10 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807286] Re: systemd SEGV freezing on install of virtualbox
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/1807286 Title: systemd SEGV freezing on install of virtualbox Status in systemd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: most of the information has been reported at VBox here: https://forums.virtualbox.org/viewtopic.php?f=7=90643 when installing VBox this happens: _ sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run [sudo] password for kinghat: Verifying archive integrity... All good. Uncompressing VirtualBox for Linux installation. VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer Installing VirtualBox to /opt/VirtualBox Python found: python, installing bindings... Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST): systemd[1]: Caught , dumped core as pid 5201. Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST): systemd[1]: Freezing execution. Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Connection timed out Failed to start vboxdrv.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) See system logs and 'systemctl status vboxdrv.service' for details. Failed to start vboxballoonctrl-service.service: Connection timed out See system logs and 'systemctl status vboxballoonctrl-service.service' for details. Failed to start vboxautostart-service.service: Connection timed out See system logs and 'systemctl status vboxautostart-service.service' for details. Failed to start vboxweb-service.service: Connection timed out See system logs and 'systemctl status vboxweb-service.service' for details. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual /opt/VirtualBox/UserManual.pdf and in the user FAQ http://www.virtualbox.org/wiki/User_FAQ We hope that you enjoy using VirtualBox. _ VB then starts fine. after reboot none of the VMs fail to launch. ive had weird install issues with VBox on 18.10 for many months. Description:Ubuntu 18.10 Release:18.10 VirtualBox-5.2.23-126798-Linux_amd64.run http://paste.debian.net/hidden/ee22b12a/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: virtualbox (not installed) ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 6 17:21:15 2018 InstallationDate: Installed on 2018-08-20 (108 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: virtualbox UpgradeStatus: Upgraded to cosmic on 2018-10-10 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807286] Re: systemd SEGV freezing on install of virtualbox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: virtualbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1807286 Title: systemd SEGV freezing on install of virtualbox Status in systemd package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: most of the information has been reported at VBox here: https://forums.virtualbox.org/viewtopic.php?f=7=90643 when installing VBox this happens: _ sudo ./VirtualBox-5.2.23-126798-Linux_amd64.run [sudo] password for kinghat: Verifying archive integrity... All good. Uncompressing VirtualBox for Linux installation. VirtualBox Version 5.2.23 r126798 (2018-11-20T16:12:47Z) installer Installing VirtualBox to /opt/VirtualBox Python found: python, installing bindings... Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST): systemd[1]: Caught , dumped core as pid 5201. Broadcast message from systemd-journald@kinghat-kubuntu (Thu 2018-12-06 16:33:50 CST): systemd[1]: Freezing execution. Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) Failed to enable unit: Connection timed out Failed to start vboxdrv.service: Failed to activate service 'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms) See system logs and 'systemctl status vboxdrv.service' for details. Failed to start vboxballoonctrl-service.service: Connection timed out See system logs and 'systemctl status vboxballoonctrl-service.service' for details. Failed to start vboxautostart-service.service: Connection timed out See system logs and 'systemctl status vboxautostart-service.service' for details. Failed to start vboxweb-service.service: Connection timed out See system logs and 'systemctl status vboxweb-service.service' for details. VirtualBox has been installed successfully. You will find useful information about using VirtualBox in the user manual /opt/VirtualBox/UserManual.pdf and in the user FAQ http://www.virtualbox.org/wiki/User_FAQ We hope that you enjoy using VirtualBox. _ VB then starts fine. after reboot none of the VMs fail to launch. ive had weird install issues with VBox on 18.10 for many months. Description:Ubuntu 18.10 Release:18.10 VirtualBox-5.2.23-126798-Linux_amd64.run http://paste.debian.net/hidden/ee22b12a/ ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: virtualbox (not installed) ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 6 17:21:15 2018 InstallationDate: Installed on 2018-08-20 (108 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: virtualbox UpgradeStatus: Upgraded to cosmic on 2018-10-10 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1171342] Re: mouse scroll wheel not working in gedit & System Monitor
** Changed in: xorg-server Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1171342 Title: mouse scroll wheel not working in gedit & System Monitor Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Open System Monitor Using mouse wheel button - scroll up or down - list does not move. If Press the wheel button and then scroll up or down the list will move. This also occurs in Gedit. Firefox and Terminal work as expected. IE do not need to press the wheel and then scroll Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 13.04 Release: 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1171342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
** Changed in: xorg-server Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in X.Org X server: Unknown Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: In Progress Status in qtbase-opensource-src source package in Trusty: Fix Released Status in unity source package in Trusty: Invalid Status in xorg-server source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184159] Re: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching
** Changed in: xorg-server Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1184159 Title: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Hello, Scrolling with a touchpad is now a bit jerky. It's exactly the same bug than bug #1171156 introduced in Raring by an upstream's patch in order to fix bug #1046988 (which was tracked by upstream there: https://bugzilla.gnome.org/show_bug.cgi?id=690275 ) * Impact: Up & down scrolling with a touchpad is now a bit jerky, seen best with gedit in large files though also seems to affect nautilus & in general. * Testcase: Set any bindings in Viewport Switcher > Desktop-based Viewport switching try scrolling in long documents in gedit using a touchpad, is scrolling "jerky"? * Videos: Before: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650661/+files/gtk_scroll_1171156_without_patch.ogv After: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650662/+files/gtk_scroll_1171156_with_patch.ogv * Note: It seems this bug doesn't affect Gnome-Shell session: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/comments/10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 17:44:01 2013 InstallationDate: Installed on 2011-08-10 (653 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1184159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1171342]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/566. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1171342 Title: mouse scroll wheel not working in gedit & System Monitor Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Open System Monitor Using mouse wheel button - scroll up or down - list does not move. If Press the wheel button and then scroll up or down the list will move. This also occurs in Gedit. Firefox and Terminal work as expected. IE do not need to press the wheel and then scroll Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 13.04 Release: 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1171342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307701]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/569. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in X.Org X server: Unknown Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: In Progress Status in qtbase-opensource-src source package in Trusty: Fix Released Status in unity source package in Trusty: Invalid Status in xorg-server source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184159]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/566. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1184159 Title: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching Status in Compiz: Fix Released Status in GTK+: Fix Released Status in X.Org X server: Unknown Status in compiz package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Hello, Scrolling with a touchpad is now a bit jerky. It's exactly the same bug than bug #1171156 introduced in Raring by an upstream's patch in order to fix bug #1046988 (which was tracked by upstream there: https://bugzilla.gnome.org/show_bug.cgi?id=690275 ) * Impact: Up & down scrolling with a touchpad is now a bit jerky, seen best with gedit in large files though also seems to affect nautilus & in general. * Testcase: Set any bindings in Viewport Switcher > Desktop-based Viewport switching try scrolling in long documents in gedit using a touchpad, is scrolling "jerky"? * Videos: Before: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650661/+files/gtk_scroll_1171156_without_patch.ogv After: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/+attachment/3650662/+files/gtk_scroll_1171156_with_patch.ogv * Note: It seems this bug doesn't affect Gnome-Shell session: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1171156/comments/10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 17:44:01 2013 InstallationDate: Installed on 2011-08-10 (653 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1184159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
This bug was fixed in the package unattended-upgrades - 1.5ubuntu3.18.10.1 --- unattended-upgrades (1.5ubuntu3.18.10.1) cosmic; urgency=medium * Start service after systemd-logind.service to be able to take inhibition lock (LP: #1806487) * Handle gracefully when logind is down (LP: #1806487) -- Balint Reczey Thu, 13 Dec 2018 14:39:12 +0100 ** Changed in: unattended-upgrades (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken 2018-12-13 14:31:43,595 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-13 14:31:43,688 WARNING - Could not get delay inhibitor lock 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - Maybe systemd-logind service is not running. 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - To enable monitoring the PrepareForShutdown() signal instead of polling please install the python3-gi package root@bb-logind:~# systemd-analyze dot | grep unattended ...
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.8 --- unattended-upgrades (1.1ubuntu1.18.04.8) bionic; urgency=medium * Start service after systemd-logind.service to be able to take inhibition lock (LP: #1806487) * Handle gracefully when logind is down (LP: #1806487) -- Balint Reczey Thu, 13 Dec 2018 14:42:44 +0100 ** Changed in: unattended-upgrades (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken 2018-12-13 14:31:43,595 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-13 14:31:43,688 WARNING - Could not get delay inhibitor lock 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - Maybe systemd-logind service is not running. 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - To enable monitoring the PrepareForShutdown() signal instead of polling please install the python3-gi package root@bb-logind:~# systemd-analyze dot | grep unattended ...
[Touch-packages] [Bug 1806487] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago Main PID: 1938 (code=killed, signal=TERM) Status: "Processing requests..." ... * Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start: root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log ... 2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock 2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken * Restore logind's ability to start root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload * Restart unattended-upgrades.service root@bb-logind:~# service unattended-upgrades restart root@bb-logind:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-12-13 14:31:43 UTC; 3s ago Docs: man:unattended-upgrade(8) Main PID: 4129 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown. root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes 2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration 2018-12-13 14:30:17,602 DEBUG - get_lock returned 7 2018-12-13 14:30:17,602 DEBUG - lock not taken 2018-12-13 14:31:43,595 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-13 14:31:43,688 WARNING - Could not get delay inhibitor lock 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - Maybe systemd-logind service is not running. 2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead. 2018-12-13 14:31:43,691 WARNING - To enable monitoring the PrepareForShutdown() signal instead of polling please install the python3-gi package root@bb-logind:~# systemd-analyze dot | grep unattended ...
[Touch-packages] [Bug 1809174] [NEW] apt doesn't detect file corruption in /var/lib/apt/lists
Public bug reported: The Problem == /var/lib/apt/lists contains the repository index caches or similar; I'm not sure what the correct apt-terminology is. I've installed Chrome on my laptop, so I have: smacdonald@L247:/var/lib/apt/lists$ dir *goog* -rw-r--r-- 1 root root 943 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_Release -rw-r--r-- 1 root root 819 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_Release.gpg -rw-r--r-- 1 root root 4457 Dec 19 14:02 dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages for example. dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file: smacdonald@L247:/var/lib/apt/lists$ cat dl.google.com_linux_chrome_deb_dists_stable_Release Origin: Google LLC Label: Google Suite: stable Codename: stable Version: 1.0 Date: Wed, 19 Dec 2018 18:51:54 UTC Architectures: amd64 Components: main Description: Google chrome-linux software repository MD5Sum: 9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz 156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release SHA1: 4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz 0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release SHA256: fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 main/binary-amd64/Packages 2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 main/binary-amd64/Packages.gz c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 main/binary-amd64/Release If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file has become corrupt in the specific manner of being 0 bytes in length, apt does not detect this, and the repository is effectively unreachable until one of two things occurs: a) the repository has an update causing apt to re-fetch the repository information and accidentally fix-by-over-writing the corrupt 0 byte file, or, b) the user removes the corrupt 0-byte file and does an apt update to refetch the repository information. The Context == Our IoT devices run Ubuntu 16.04, and their main storage is eMMC. Sometimes there are catastrophic power cuts, and, despite other precautions, files are occasionally corrupted in the manner of becoming 0 bytes in length. We're not sure exactly why or how. Today a deployed device suffered the above scenario. We maintain a debian package repository for updating our devices in the field, and we suddenly couldn't install packages from it. A bit of investigation turned up the 0 byte *_Packages file for our repo, and we worked around the problem. Part of the situation is our debian repository doesn't have updates very often, so 'sudo apt-get update' was giving a Hit: instead of a Get: result all the time, and everything from the "normal user command line" side of things looked okay. There were no logs in /var/log/syslog either. We just could not see our packages from our repo, despite 'apt- get update' looking good. What I Expected to Happen == Given that the the *_Release file contains checksums for the *_Package file, I would expect that apt verifies the checksum, and if it fails, refetches the repository information even if there hasn't been an update, during any given 'apt update' operation. Further Information == I checked apt's project in Debian at https://bugs.debian.org/cgi- bin/pkgreport.cgi?pkg=apt and there don't appear to be any bugs about this filed already, so I'm starting by filing one here. The situation occurred on an Ubuntu 16.04 system, but is 100% reproducible with Google's chrome repository on my Ubuntu 18.04.1 laptop. I can provide a set of reproduction steps if needed, but it's fairly straight-forward. The fact that this corruption appears to be "everything working okay" to the end user, except that apt doesn't know about packages it says it knows about, and there is no error logging for any sort, is partly why I'm filing this. Note the "if one of two things happens" case a) above: if the repository has updates, apt re-fetches the repository information, and overwrites/removes the existing. This has the effect of accidentally fixing the problem without any data indicating the problem occurred in the first place. So it is probable that the problem is under-reported because it's not visible. Especially for frequently updated repositories like the core Ubuntu repos. System Details
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Thanks for testing and the feedback Daniel. You're right, cosmic is not visibly affected by the bug, nevertheless the fix was backported there too to satisfy the SRU process (see comment #45). So what should really be tested is that this doesn't introduce regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806399] Re: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127
** Changed in: python3-defaults (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: python3-defaults (Ubuntu) Status: Fix Committed => Incomplete ** Changed in: python3-defaults (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1806399 Title: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127 Status in python3-defaults package in Ubuntu: New Bug description: lkjhgfdsazASDERTYUIOP'/;.LKJHGFDSZ ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-minimal 3.6.7-1~18.04 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: python3-minimal:amd64: Configure python3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Dec 3 23:48:46 2018 DpkgTerminalLog: Setting up python3-minimal (3.6.7-1~18.04) ... /var/lib/dpkg/info/python3-minimal.postinst: 5: /var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found dpkg: error processing package python3-minimal (--configure): installed python3-minimal package post-installation script subprocess returned error exit status 127 DuplicateSignature: package:python3-minimal:3.6.7-1~18.04 Setting up python3-minimal (3.6.7-1~18.04) ... /var/lib/dpkg/info/python3-minimal.postinst: 5: /var/lib/dpkg/info/python3-minimal.postinst: py3compile: not found dpkg: error processing package python3-minimal (--configure): installed python3-minimal package post-installation script subprocess returned error exit status 127 ErrorMessage: installed python3-minimal package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-01-05 (332 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6m, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: python3-defaults Title: package python3-minimal 3.6.7-1~18.04 failed to install/upgrade: installed python3-minimal package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-09-27 (67 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1806399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
xenial: same steps as last comment. reproduction using d-i version 20101020ubuntu451.26 ~ # wget http://github.com/ --2018-12-19 20:15:36-- http://github.com/ Resolving github.com... 192.30.253.113, 192.30.253.112 Connecting to github.com|192.30.253.113|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://github.com/ [following] --2018-12-19 20:15:36-- https://github.com/ Connecting to github.com|192.30.253.113|:443... connected. ERROR: cannot verify github.com's certificate, issued by 'CN=DigiCert SHA2 Extended Validation Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US': Unable to locally verify the issuer's authority. To connect to github.com insecurely, use `--no-check-certificate'. verification of fix using d-i version 20101020ubuntu451.27 ~ # wget http://github.com/ --2018-12-19 20:18:37-- http://github.com/ Resolving github.com... 192.30.253.113, 192.30.253.112 Connecting to github.com|192.30.253.113|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://github.com/ [following] --2018-12-19 20:18:37-- https://github.com/ Connecting to github.com|192.30.253.113|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'index.html' index.html [ <=>] 78.22K --.-KB/sin 0.04s 2018-12-19 20:18:37 (1.82 MB/s) - 'index.html' saved [80096] ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done ** Tags removed: sts-sponsor sts-sponsor-ddstreet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Fix Released Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Released Status in ca-certificates source package in Trusty: Fix Committed Status in debian-installer source package in Trusty: Fix Committed Status in ca-certificates source package in Xenial: Fix Committed Status in debian-installer source package in Xenial: Fix Committed Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Released Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Released Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Released Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work out. * The ca-certificates and debian-installer builds have been done in a PPA using all architectures,
[Touch-packages] [Bug 1809162] Re: systemctl show -p doesn't show all properties
** Package changed: ubuntu => systemd (Ubuntu) -- 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/1809162 Title: systemctl show -p doesn't show all properties Status in systemd package in Ubuntu: New Bug description: In Description: Ubuntu 16.04.4 LTS Release: 16.04 using systemd package Version: 229-4ubuntu21.10 The systemctl show -p or --property= command shows some properties but not others. To reproduce create a unit some_unit.path [Unit] Description=%n [Path] PathExistsGlob=%h/foo* Unit=remove.service Using systemctl show --all some_unit.path you'll see properties PathExistsGlob and LoadState shown Now try systemctl show -p LoadState some_unit.path and you will see the property value Then try systemctl show -p PathExistsGlob some_unit.path and you will get no value back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
trusty verification: reproduce bug: 1) get the debian-installer source version 20101020ubuntu318.44 and extract 2) in the source cd build/ 3) make build_netboot 4) cd dest/netboot/ubuntu-installer/amd64 5) run steps from comment 1 6) verify wget from github.com fails due to https certificate: ~ # wget http://github.com --2018-12-19 20:04:55-- http://github.com/ Resolving github.com... 192.30.253.113, 192.30.253.112 Connecting to github.com|192.30.253.113|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://github.com/ [following] --2018-12-19 20:04:55-- https://github.com/ Connecting to github.com|192.30.253.113|:443... connected. ERROR: cannot verify github.com's certificate, issued by '/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 Extended Validation Server CA': Unable to locally verify the issuer's authority. To connect to github.com insecurely, use `--no-check-certificate'. verify fix is same steps except with debian-installer version 20101020ubuntu318.45 step #6 passes: ~ # wget github.com --2018-12-19 20:09:44-- http://github.com/ Resolving github.com... 192.30.253.112, 192.30.253.113 Connecting to github.com|192.30.253.112|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://github.com/ [following] --2018-12-19 20:09:44-- https://github.com/ Connecting to github.com|192.30.253.112|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: 'index.html' [ <=> ] 80,096 --.-K/s in 0.04s 2018-12-19 20:09:44 (1.77 MB/s) - 'index.html' saved [80096] ** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1807023 Title: installer stock images fail to validate any HTTPS certificates (ca- certificates missing) Status in debian-installer: Fix Released Status in ca-certificates package in Ubuntu: Invalid Status in debian-installer package in Ubuntu: Fix Released Status in ca-certificates source package in Trusty: Fix Committed Status in debian-installer source package in Trusty: Fix Committed Status in ca-certificates source package in Xenial: Fix Committed Status in debian-installer source package in Xenial: Fix Committed Status in ca-certificates source package in Bionic: Invalid Status in debian-installer source package in Bionic: Fix Released Status in ca-certificates source package in Cosmic: Invalid Status in debian-installer source package in Cosmic: Fix Released Status in ca-certificates source package in Disco: Invalid Status in debian-installer source package in Disco: Fix Released Status in debian-installer package in Debian: Fix Released Bug description: [Impact] * The installer stock images fail to validate any HTTPS certificates because ca-certificates is not available in the installer environment. * This causes wget/download errors for preseed files on HTTPS servers (or HTTP servers that redirect to HTTPS, which are increasingly common nowadays - e.g., GitHub) and theoretically any other files that are downloaded with d-i-utils/fetch-url/wget. * The fix is to ship ca-certificates-udeb in installer stock images. * Debian already ships ca-certificate-udeb in the stock installer images; the fix is applied since Jan 2017. (reference: Debian Bug #842040 / d-i commit 2f00c51a [1]) [Test Case] * In the installer shell: ~ # wget http://github.com # or https://github.com - FAIL if ca-certificates-udeb is missing: "ERROR: cannot verify github.com's certificate, <...>' - PASS if ca-certificates-udeb is available "Saving to: 'index.html'" * Test steps with virt-install and netboot images are provided in the comments, for each release. [Regression Potential] * Low. This just adds the ca-certificates files in /etc/ssl/certs and symlink in /usr/lib/ssl/certs, so only tools looking for that would be affected. * Apparently only wget checks for/uses those files, and the difference in behavior is download errors no longer occur. [Notes] * The ca-certificates-udeb is not currently present in the Ubuntu 'main' component, but in 'universe', despite the normal deb being in 'main'. However, when rebuilding in a PPA it goes into 'main' accordingly, and can be used by default by debian-installer (otherwise, UDEB_COMPONENTS has to be modified to include universe/d-i). * So this fix includes a no-change-rebuild for the ca-certificates package, in order to publish the udeb in the archive (at least in PPA for testing). Hopefully that can be sorted out for this fix to work
[Touch-packages] [Bug 1809162] [NEW] systemctl show -p doesn't show all properties
You have been subscribed to a public bug: In Description:Ubuntu 16.04.4 LTS Release:16.04 using systemd package Version: 229-4ubuntu21.10 The systemctl show -p or --property= command shows some properties but not others. To reproduce create a unit some_unit.path [Unit] Description=%n [Path] PathExistsGlob=%h/foo* Unit=remove.service Using systemctl show --all some_unit.path you'll see properties PathExistsGlob and LoadState shown Now try systemctl show -p LoadState some_unit.path and you will see the property value Then try systemctl show -p PathExistsGlob some_unit.path and you will get no value back. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- systemctl show -p doesn't show all properties https://bugs.launchpad.net/bugs/1809162 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Hi Brian. I have been running Cosmic (Ubuntu 18.10) as my main OS since its release, and I don't think I've ever actually hit the bug on Cosmic. (I just verified that I have the GTK_IM_MODULE=ibus variable set, too. So I think I would be hitting this bug, if Cosmic were affected.) So, my assumption has been that Cosmic has a newer snapshot of gnome- shell or ibus or some other involved package which has changed in some way to avoid the bug. All of which is to say: based on my experience at least, the update from comment #52 here isn't necessary to fix this bug in Cosmic (but perhaps it's still valuable to keep pace with upstream, or something like that). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
(My experience [of Cosmic being unaffected] seems to match what was reported in comment 44 ( https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/comments/44 ), too.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
Verifed 1.1ubuntu1.18.04.7~16.04.1 on Xenial: root@x-lp-1806487-uu:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@x-lp-1806487-uu:~# service systemd-logind stop1.1ubuntu1.18.04.7~16.04.1 root@x-lp-1806487-uu:~# vi /etc/apt/sources.list root@x-lp-1806487-uu:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@x-lp-1806487-uu:~# apt install -qq unattended-upgrades The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. Suggested packages: bsd-mailx default-mta | mail-transport-agent needrestart The following packages will be upgraded: unattended-upgrades 1 upgraded, 0 newly installed, 0 to remove and 22 not upgraded. Need to get 40.2 kB of archives. After this operation, 69.6 kB of additional disk space will be used. Preconfiguring packages ... (Reading database ... 25709 files and directories currently installed.) Preparing to unpack .../unattended-upgrades_1.1ubuntu1.18.04.7~16.04.1_all.deb ... Unpacking unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) over (0.90ubuntu0.9) ... Processing triggers for systemd (229-4ubuntu21.10) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) ... Installing new version of config file /etc/kernel/postinst.d/unattended-upgrades ... Installing new version of config file /etc/pm/sleep.d/10_unattended-upgrades-hibernate ... root@x-lp-1806487-uu:~# systemctl daemon-reload root@x-lp-1806487-uu:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Wed 2018-12-19 18:41:11 UTC; 1min 14s ago Main PID: 376 (code=killed, signal=TERM) Status: "Processing requests..." Dec 19 14:19:03 x-lp-1806487-uu systemd-logind[376]: New seat seat0. Dec 19 14:19:03 x-lp-1806487-uu systemd[1]: Started Login Service. Dec 19 18:40:20 x-lp-1806487-uu systemd-logind[376]: New session c1 of user root. Dec 19 18:41:11 x-lp-1806487-uu systemd[1]: Stopping Login Service... Dec 19 18:41:11 x-lp-1806487-uu systemd[1]: Stopped Login Service. root@x-lp-1806487-uu:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@x-lp-1806487-uu:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-19 18:42:33,848 WARNING - Could not get delay inhibitor lock 2018-12-19 18:42:33,849 DEBUG - Skip waiting for signals, starting operation now 2018-12-19 18:42:33,849 DEBUG - Starting countdown of 25.0 minutes 2018-12-19 18:42:33,850 DEBUG - Initializing apt_pkg configuration 2018-12-19 18:42:33,850 DEBUG - get_lock returned 7 2018-12-19 18:42:33,851 DEBUG - lock not taken root@x-lp-1806487-uu:~# rm /etc/systemd/system/systemd-logind.service root@x-lp-1806487-uu:~# systemctl daemon-reload root@x-lp-1806487-uu:~# service unattended-upgrades restart root@x-lp-1806487-uu:~# service unattended-upgrades restart root@x-lp-1806487-uu:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-12-19 18:43:05 UTC; 6s ago Docs: man:unattended-upgrade(8) Main PID: 1505 (unattended-upgr) Tasks: 2 Memory: 8.4M CPU: 66ms CGroup: /system.slice/unattended-upgrades.service └─1505 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 19 18:43:05 x-lp-1806487-uu systemd[1]: Started Unattended Upgrades Shutdown. root@x-lp-1806487-uu:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-19 18:42:33,848 WARNING - Could not get delay inhibitor lock 2018-12-19 18:42:33,849 DEBUG - Skip waiting for signals, starting operation now 2018-12-19 18:42:33,849 DEBUG - Starting countdown of 25.0 minutes 2018-12-19 18:42:33,850 DEBUG - Initializing apt_pkg configuration 2018-12-19 18:42:33,850 DEBUG - get_lock returned 7 2018-12-19 18:42:33,851 DEBUG - lock not taken 2018-12-19 18:43:05,014 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running root@x-lp-1806487-uu:~# ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
Verified 1.1ubuntu1.18.04.8 on Bionic: root@bb-lp-1806487-uu:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-lp-1806487-uu:~# service systemd-logind stop root@bb-lp-1806487-uu:~# root@bb-lp-1806487-uu:~# service systemd-logind status ● systemd-logind.service - Login Service Loaded: loaded (/lib/systemd/system/systemd-logind.service; masked; vendor preset: enabled) Active: inactive (dead) since Wed 2018-12-19 18:37:18 UTC; 4s ago Docs: man:systemd-logind.service(8) man:logind.conf(5) https://www.freedesktop.org/wiki/Software/systemd/logind https://www.freedesktop.org/wiki/Software/systemd/multiseat Process: 196 ExecStart=/lib/systemd/systemd-logind (code=killed, signal=TERM) Main PID: 196 (code=killed, signal=TERM) Status: "Processing requests..." Dec 19 14:08:17 bb-lp-1806487-uu systemd[1]: Starting Login Service... Dec 19 14:08:17 bb-lp-1806487-uu systemd-logind[196]: New seat seat0. Dec 19 14:08:17 bb-lp-1806487-uu systemd[1]: Started Login Service. Dec 19 18:35:38 bb-lp-1806487-uu systemd-logind[196]: New session c1 of user root. Dec 19 18:36:17 bb-lp-1806487-uu systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not per Dec 19 18:36:17 bb-lp-1806487-uu systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not per Dec 19 18:36:18 bb-lp-1806487-uu systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not per Dec 19 18:37:18 bb-lp-1806487-uu systemd[1]: Stopping Login Service... Dec 19 18:37:18 bb-lp-1806487-uu systemd[1]: Stopped Login Service. root@bb-lp-1806487-uu:~# systemctl daemon-reload root@bb-lp-1806487-uu:~# service systemd-logind stop root@bb-lp-1806487-uu:~# service systemd-logind status ● systemd-logind.service Loaded: masked (/dev/null; bad) Active: inactive (dead) since Wed 2018-12-19 18:37:18 UTC; 32s ago Main PID: 196 (code=killed, signal=TERM) Status: "Processing requests..." Dec 19 14:08:17 bb-lp-1806487-uu systemd[1]: Starting Login Service... Dec 19 14:08:17 bb-lp-1806487-uu systemd-logind[196]: New seat seat0. Dec 19 14:08:17 bb-lp-1806487-uu systemd[1]: Started Login Service. Dec 19 18:35:38 bb-lp-1806487-uu systemd-logind[196]: New session c1 of user root. Dec 19 18:36:17 bb-lp-1806487-uu systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not per Dec 19 18:36:17 bb-lp-1806487-uu systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not per Dec 19 18:36:18 bb-lp-1806487-uu systemd[1]: systemd-logind.service: Failed to reset devices.list: Operation not per Dec 19 18:37:18 bb-lp-1806487-uu systemd[1]: Stopping Login Service... Dec 19 18:37:18 bb-lp-1806487-uu systemd[1]: Stopped Login Service. root@bb-lp-1806487-uu:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@bb-lp-1806487-uu:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-19 18:37:58,922 WARNING - Could not get delay inhibitor lock 2018-12-19 18:37:58,922 DEBUG - Skip waiting for signals, starting operation now 2018-12-19 18:37:58,923 DEBUG - Starting countdown of 25.0 minutes 2018-12-19 18:37:58,923 DEBUG - Initializing apt_pkg configuration 2018-12-19 18:37:58,923 DEBUG - get_lock returned 7 2018-12-19 18:37:58,923 DEBUG - lock not taken root@bb-lp-1806487-uu:~# rm /etc/systemd/system/systemd-logind.service root@bb-lp-1806487-uu:~# systemctl daemon-reload root@bb-lp-1806487-uu:~# service unattended-upgrades restart root@bb-lp-1806487-uu:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-12-19 18:38:28 UTC; 4s ago Docs: man:unattended-upgrade(8) Main PID: 1149 (unattended-upgr) Tasks: 2 (limit: 4915) CGroup: /system.slice/unattended-upgrades.service └─1149 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 19 18:38:28 bb-lp-1806487-uu systemd[1]: Started Unattended Upgrades Shutdown. root@bb-lp-1806487-uu:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-19 18:37:58,922 WARNING - Could not get delay inhibitor lock 2018-12-19 18:37:58,922 DEBUG - Skip waiting for signals, starting operation now 2018-12-19 18:37:58,923 DEBUG - Starting countdown of 25.0 minutes 2018-12-19 18:37:58,923 DEBUG - Initializing apt_pkg configuration 2018-12-19 18:37:58,923 DEBUG - get_lock returned 7 2018-12-19 18:37:58,923 DEBUG - lock not taken 2018-12-19 18:38:28,808 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running root@bb-lp-1806487-uu:~# service unattended-upgrades restart root@bb-lp-1806487-uu:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded
[Touch-packages] [Bug 1806487] Re: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet)
Verified unattended-upgrades 1.5ubuntu3.18.10.1 on cosmic: root@cc-lp-1806487-uu:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug root@cc-lp-1806487-uu:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-19 18:29:38,461 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-19 18:32:11,165 WARNING - Could not get delay inhibitor lock 2018-12-19 18:32:11,165 DEBUG - Skip waiting for signals, starting operation now 2018-12-19 18:32:11,166 DEBUG - Starting countdown of 25.0 minutes 2018-12-19 18:32:11,166 DEBUG - Initializing apt_pkg configuration 2018-12-19 18:32:11,167 DEBUG - get_lock returned 9 2018-12-19 18:32:11,167 DEBUG - lock not taken root@cc-lp-1806487-uu:~# rm /etc/systemd/system/systemd-logind.servicerm /etc/systemd/system/systemd-logind.servicerm: cannot remove '/etc/systemd/system/systemd-logind.servicerm': No such file or directory root@cc-lp-1806487-uu:~# rm /etc/systemd/system/systemd-logind.servicerm /etc/systemd/system/systemd-logind.servicerm: cannot remove '/etc/systemd/system/systemd-logind.servicerm': No such file or directory rm: cannot remove '/etc/systemd/system/systemd-logind.service': No such file or directory root@cc-lp-1806487-uu:~# rm /etc/systemd/system/systemd-logind.service rm: cannot remove '/etc/systemd/system/systemd-logind.service': No such file or directory root@cc-lp-1806487-uu:~# systemctl daemon-reload root@cc-lp-1806487-uu:~# service unattended-upgrades restart root@cc-lp-1806487-uu:~# service unattended-upgrades status ● unattended-upgrades.service - Unattended Upgrades Shutdown Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2018-12-19 18:33:11 UTC; 7s ago Docs: man:unattended-upgrade(8) Main PID: 3164 (unattended-upgr) Tasks: 2 (limit: 4915) Memory: 8.5M CGroup: /system.slice/unattended-upgrades.service └─3164 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal Dec 19 18:33:11 cc-lp-1806487-uu systemd[1]: Started Unattended Upgrades Shutdown. root@cc-lp-1806487-uu:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2018-12-19 18:29:38,461 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2018-12-19 18:32:11,165 WARNING - Could not get delay inhibitor lock 2018-12-19 18:32:11,165 DEBUG - Skip waiting for signals, starting operation now 2018-12-19 18:32:11,166 DEBUG - Starting countdown of 25.0 minutes 2018-12-19 18:32:11,166 DEBUG - Initializing apt_pkg configuration 2018-12-19 18:32:11,167 DEBUG - get_lock returned 9 2018-12-19 18:32:11,167 DEBUG - lock not taken 2018-12-19 18:33:11,800 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running root@cc-lp-1806487-uu:~# dpkg -l unattended-upgrades | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersionArchitecture Description +++-===-==--=== ii unattended-upgrades 1.5ubuntu3.18.10.1 all automatic installation of security upgrades -- 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/1806487 Title: [regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start. * Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process. * The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence. [Test Case] * Stop systemd-logind and make it unable to start for example by masking it: root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service root@bb-logind:~# systemctl daemon-reload root@bb-logind:~# service systemd-logind stop root@bb-logind:~# service
[Touch-packages] [Bug 1807023] Re: installer stock images fail to validate any HTTPS certificates (ca-certificates missing)
autopkgtest failure notes:
glib-networking fails for trusty, but it failed exactly the same way in
the last auotpkgtest run, which was from 2017. Appears to be broken
test case and should be ignored for this sru.
snapd fails for xenial, but it's failed for the last 2+ months. The
tests for it are clearly broken and should be ignored for this sru.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1807023
Title:
installer stock images fail to validate any HTTPS certificates (ca-
certificates missing)
Status in debian-installer:
Fix Released
Status in ca-certificates package in Ubuntu:
Invalid
Status in debian-installer package in Ubuntu:
Fix Released
Status in ca-certificates source package in Trusty:
Fix Committed
Status in debian-installer source package in Trusty:
Fix Committed
Status in ca-certificates source package in Xenial:
Fix Committed
Status in debian-installer source package in Xenial:
Fix Committed
Status in ca-certificates source package in Bionic:
Invalid
Status in debian-installer source package in Bionic:
Fix Released
Status in ca-certificates source package in Cosmic:
Invalid
Status in debian-installer source package in Cosmic:
Fix Released
Status in ca-certificates source package in Disco:
Invalid
Status in debian-installer source package in Disco:
Fix Released
Status in debian-installer package in Debian:
Fix Released
Bug description:
[Impact]
* The installer stock images fail to validate any HTTPS
certificates because ca-certificates is not available
in the installer environment.
* This causes wget/download errors for preseed files on
HTTPS servers (or HTTP servers that redirect to HTTPS,
which are increasingly common nowadays - e.g., GitHub)
and theoretically any other files that are downloaded
with d-i-utils/fetch-url/wget.
* The fix is to ship ca-certificates-udeb in installer
stock images.
* Debian already ships ca-certificate-udeb in the stock
installer images; the fix is applied since Jan 2017.
(reference: Debian Bug #842040 / d-i commit 2f00c51a [1])
[Test Case]
* In the installer shell:
~ # wget http://github.com # or https://github.com
- FAIL if ca-certificates-udeb is missing:
"ERROR: cannot verify github.com's certificate, <...>'
- PASS if ca-certificates-udeb is available
"Saving to: 'index.html'"
* Test steps with virt-install and netboot images
are provided in the comments, for each release.
[Regression Potential]
* Low. This just adds the ca-certificates files in
/etc/ssl/certs and symlink in /usr/lib/ssl/certs,
so only tools looking for that would be affected.
* Apparently only wget checks for/uses those files,
and the difference in behavior is download errors
no longer occur.
[Notes]
* The ca-certificates-udeb is not currently present
in the Ubuntu 'main' component, but in 'universe',
despite the normal deb being in 'main'.
However, when rebuilding in a PPA it goes into
'main' accordingly, and can be used by default
by debian-installer (otherwise, UDEB_COMPONENTS
has to be modified to include universe/d-i).
* So this fix includes a no-change-rebuild for the
ca-certificates package, in order to publish the
udeb in the archive (at least in PPA for testing).
Hopefully that can be sorted out for this fix
to work out.
* The ca-certificates and debian-installer builds
have been done in a PPA using all architectures,
and testing has been done with the amd64 images.
* This fix is requested for Bionic, Cosmic, Disco
at least.
* The fix for Trusty and Xenial needed a little
bit more work to build/ship the (new) udeb.
(reference: Debian Bug #845456 / ca-certificates commit 3acb3a90 [2])
It would be good to have them too if at all possible.
[1]
https://salsa.debian.org/installer-team/debian-installer/commit/2f00c51a7ead982ae1cd71bee06c8416890196b6
[2]
https://salsa.debian.org/debian/ca-certificates/commit/3acb3a9042a00307ba35d10052d81cdc206c34a4
[Debugging]
For debugging purposes, one can install strace-udeb in the installer
to verify wget's stat() calls to /usr/lib/ssl/certs.
~ # anna-install strace-udeb
~ # strace -e stat wget -O- https://github.com >/dev/null
...
Resolving github.com... stat("/etc/resolv.conf", {st_mode=S_IFREG|0644,
st_size=20, ...}) = 0
140.82.118.3, 140.82.118.4
Connecting to github.com|140.82.118.3|:443... connected.
stat("/usr/lib/ssl/certs/45bfefc3.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
stat("/usr/lib/ssl/certs/244b5494.0", 0x7ffdba51b570) = -1 ENOENT (No such
file or directory)
ERROR: cannot
[Touch-packages] [Bug 1727088] Re: No indicator icons for qt apps
Reassigned to ubuntu-meta since dependency from the ubuntu-desktop package would cause sni-qt to be installed by default. ** Package changed: ubuntu => ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1727088 Title: No indicator icons for qt apps Status in ubuntu-meta package in Ubuntu: New Bug description: On a freshly installed ubuntu 17.10 the indicator/topicons will not show up for qt apps, like mumble. This is fixed by installing the sni-qt package. Since it's not common knowledge to install that package manually, maybe it should be installed by default on the 18.04 release to have more applications working out of the box with the indicators/topicons? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1727088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
** Merge proposal unlinked: https://code.launchpad.net/~osomon/network-manager/+git/network-manager/+merge/361051 -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: * Impact When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not * Test case Configure the system to send all the traffic to a VPN, do a name resolution, the request should not go to the public DNS server (to be checked by capturing the traffic by example with wireshark) * Regression potential The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727933] Re: as
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (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/1727933 Title: as Status in xorg package in Ubuntu: Incomplete Bug description: asas ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-97.120~14.04.1-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: symap_custom_4_4_0_97_generic_x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.25 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: Fri Oct 27 11:16:58 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04f5] InstallationDate: Installed on 2017-10-13 (14 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. OptiPlex 390 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic root=UUID=c958b84c-581e-4d67-bbba-80b143853c6f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0M5DCD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnOptiPlex390:pvr01:rvnDellInc.:rn0M5DCD:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 390 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Oct 27 09:39:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
Please see also: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1803689 -- 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/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809135] Re: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** 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/1809135 Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: Invalid Bug description: Failed when system update was running ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupsimage2 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Dec 19 16:29:02 2018 DuplicateSignature: package:libcupsimage2:2.2.7-1ubuntu2.1 Unpacking cups-server-common (2.2.7-1ubuntu2.2) over (2.2.7-1ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-wbU1UN/23-cups-server-common_2.2.7-1ubuntu2.2_all.deb (--unpack): unable to sync file '/usr/share/cups/doc-root/apple-touch-icon.png.dpkg-new': Input/output error ErrorMessage: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-19 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: System manufacturer System Product Name Papersize: a4 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: cups Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1504:bd12/14/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1809135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version
** Merge proposal linked: https://code.launchpad.net/~osomon/network-manager/+git/network-manager/+merge/361051 -- 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/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: New Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727088] [NEW] No indicator icons for qt apps
You have been subscribed to a public bug: On a freshly installed ubuntu 17.10 the indicator/topicons will not show up for qt apps, like mumble. This is fixed by installing the sni-qt package. Since it's not common knowledge to install that package manually, maybe it should be installed by default on the 18.04 release to have more applications working out of the box with the indicators/topicons? ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- No indicator icons for qt apps https://bugs.launchpad.net/bugs/1727088 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta 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 1784499] Re: AppArmor treats regular NFS file access as network op
** Also affects: apparmor Importance: Undecided Status: 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/1784499 Title: AppArmor treats regular NFS file access as network op Status in AppArmor: New Status in snapd: New Status in apparmor package in Ubuntu: Confirmed Bug description: I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic. I have the usr.bin.man profile enforced, and home directories in NFS. The log excerpt copied below is the result of a single invocation of "man ls" by an unprivileged user. (The program did display the man page correctly to the user.) It does not seem appropriate for AppArmor to report the man(1) program as having attempted to contact the NFS server directly, when it only tried to access an NFS-served file in the normal way. "man" is not a network-aware program and the log below misleadingly implies otherwise. Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 callbacks suppressed Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2788 comm="man" laddr=X.X.X.X
[Touch-packages] [Bug 1806532] Please test proposed package
Hello Hui, or anyone else affected, Accepted alsa-lib into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.6-1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in alsa-lib source package in Cosmic: Fix Committed Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340076] Re: HDMI audio is severely distorted.
Thanks, fixed my Cosmic, too :) -- 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/1340076 Title: HDMI audio is severely distorted. Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have recently installed Ubuntu onto a newly built computer with an ASRock H87 Performance Motherboard. I am using a TV monitor for a screen, connected with HDMI. The visuals work fine but the audio is severely distorted and echoes. When testing the sound in the hardware settings, it sounds like "FRONTFRONTFRONTFRONT" with static or overdrive getting more and more prominent as the sound goes on. I have changed the Alsamixer levels but found no change. The built-in sound card also shows up when i look for it as per the Sound Troubleshooting page. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: snd_hda_codec_generic snd_hda_controller fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luke 2371 F pulseaudio /dev/snd/controlC1: luke 2371 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 10 17:52:52 2014 InstallationDate: Installed on 2014-07-09 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Digital Out, HDMI Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [To Be Filled By O.E.M., ATI R6xx HDMI, Digital Out, HDMI] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H87 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd05/06/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1340076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721693] Re: Settings list separators conflict visually with list item backgrounds
That's more a theme issue than a settings one right? Also with the new theme in 18.10 the rows don't alternate colors, does that resolve the issue for you? ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/1721693 Title: Settings list separators conflict visually with list item backgrounds Status in Ubuntu theme: New Status in gnome-control-center package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: New Bug description: Settings list separators conflict visually with list item backgrounds. The separators should be more visually significant than the things they are separating, however the Ubuntu theme is using alternating light/dark backgrounds which drown out the separators. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 Date: Fri Oct 6 13:38:00 2017 InstallationDate: Installed on 2017-05-03 (156 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1721693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809135] Re: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1809135 Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: New Bug description: Failed when system update was running ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupsimage2 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Dec 19 16:29:02 2018 DuplicateSignature: package:libcupsimage2:2.2.7-1ubuntu2.1 Unpacking cups-server-common (2.2.7-1ubuntu2.2) over (2.2.7-1ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-wbU1UN/23-cups-server-common_2.2.7-1ubuntu2.2_all.deb (--unpack): unable to sync file '/usr/share/cups/doc-root/apple-touch-icon.png.dpkg-new': Input/output error ErrorMessage: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-19 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: System manufacturer System Product Name Papersize: a4 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: cups Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1504:bd12/14/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1809135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809135] [NEW] package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1
Public bug reported: Failed when system update was running ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupsimage2 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Dec 19 16:29:02 2018 DuplicateSignature: package:libcupsimage2:2.2.7-1ubuntu2.1 Unpacking cups-server-common (2.2.7-1ubuntu2.2) over (2.2.7-1ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-wbU1UN/23-cups-server-common_2.2.7-1ubuntu2.2_all.deb (--unpack): unable to sync file '/usr/share/cups/doc-root/apple-touch-icon.png.dpkg-new': Input/output error ErrorMessage: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-19 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: System manufacturer System Product Name Papersize: a4 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: cups Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1504 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1504:bd12/14/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** 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/1809135 Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: New Bug description: Failed when system update was running ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupsimage2 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Dec 19 16:29:02 2018 DuplicateSignature: package:libcupsimage2:2.2.7-1ubuntu2.1 Unpacking cups-server-common (2.2.7-1ubuntu2.2) over (2.2.7-1ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-wbU1UN/23-cups-server-common_2.2.7-1ubuntu2.2_all.deb (--unpack): unable to sync file '/usr/share/cups/doc-root/apple-touch-icon.png.dpkg-new': Input/output error ErrorMessage: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-19 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: System manufacturer System Product Name Papersize: a4 ProcCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=cf83b71b-137b-4615-863c-06d99447fbf8 ro acpi=off quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: cups Title: package libcupsimage2 2.2.7-1ubuntu2.1 failed to install/upgrade: new libcupsimage2:amd64 package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 942856] Re: NetworkManager does not support AES-encrypted private keys for WPA 802.1x authentication
** Description changed:
+ * Impact
+
+ Selecting AES-{192,256}-CBC keys to connect isn't working
+
+ * Test case
+
+ 1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
+ 2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
+ 3. Delete the settings for the test network and attempt to reconnect using
the new key.
+
+ That should work
+
+ * Regression potential
+
+ That's new code for an extra type of keys, it shouldn't impact existing
+ options
+
+ --
+
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util when
setting up a WPA 802.1x TLS wifi connection.
-
- To test:
-
- 1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
- 2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
- 3. Delete the settings for the test network and attempt to reconnect using
the new key. Even with the correct passphrase, the "Connect" button will
remain disabled; debugging will determine that nm-util is failing to validate
the private key.
--
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/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
I've updated the description for the SRU but if someone had a better description of a testcase that would be welcome ** Description changed: + * Impact + + When using a VPN the DNS requests might still be sent to a DNS server + outside the VPN when they should not + + * Test case + + Configure the system to send all the traffic to a VPN, do a name + resolution, the request should not go to the public DNS server (to be + checked by capturing the traffic by example with wireshark) + + + * Regression potential + + The code change the handling of DNS servers when using a VPN, we should + check that name resolution still work whne using a VPN in different + configurations + + - + + In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: * Impact When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not * Test case Configure the system to send all the traffic to a VPN, do a name resolution, the request should not go to the public DNS server (to be checked by capturing the traffic by example with wireshark) * Regression potential The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809132] [NEW] Updated bionic to the current 1.10 stable version
Public bug reported: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing ** 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/1809132 Title: Updated bionic to the current 1.10 stable version Status in network-manager package in Ubuntu: New Bug description: * Impact The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS The detail of the changes can be seen in the NEWS entry https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS * Test case There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc. * Regression potential The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- 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/1809044 Title: DVD playback error: unable to play . . . DVD source is required . . . Status in gstreamer1.0 package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards, to complete compilation. Inserted known-good DVD and clicked on "Open in Videos" which launched the Totem player. Error msg: "Unable to play the file, DVD source is required, but is not installed." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided
Mesa-bug: https://bugs.freedesktop.org/show_bug.cgi?id=109102 ** Bug watch added: freedesktop.org Bugzilla #109102 https://bugs.freedesktop.org/show_bug.cgi?id=109102 -- 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/1797882 Title: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Using ubuntu wayland with dual monitors, configured above each other. Dock is configured at both displays, not hiding. Icons for "terminal" and "libreofffice Writer" are present at the dock. Start terminal on primary screen by mouseclick on dock. Start libreoffice Writer on primary screen by mouseclick on dock. Terminate libreoffice Witer by mouseclick on X. Repeat the starting and stopping of Writer. Login-screen will appear. Syslog shows: Oct 15 00:09:51 Gert2 org.gnome.Shell.desktop[5892]: intel_do_flush_locked failed: Resource deadlock avoided Oct 15 00:09:51 Gert2 gnome-terminal-[6439]: Error reading events from display: Connection reset by peer Oct 15 00:09:51 Gert2 systemd[5755]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE This problem doesnot occur in a dual monitor-session without wayland. It also doesnot occur, if only one monitor used with wayland It also doesnot occur, if the dock is only present at the primary screen. It also doesnot occur if second started application is present at the dock and doesnot add an icon to the dock (as libreoffice does). All other dual monitor/dock configurations seem to have this problem. No idea if this is helpful info, but the used graphics card does not support OpenGL version 2.1: Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Require OpenGL version 2.1 or later. Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor Oct 15 00:02:32 Gert2 org.gnome.Shell.desktop[4426]: Failed to initialize glamor, falling back to sw glxinfo: OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 7.0, 128 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 18.2.2 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic i686 ApportVersion: 2.20.10-0ubuntu13 Architecture: i386 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 13:25:10 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809108] Re: package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout
The failure is not related to unattended-upgrades, but happened when upgrading packages using synaptic and synaptic lost debconf frontend connection when debconf tried to ask a question about the changed conffile: DpkgHistoryLog.txt: ... Start-Date: 2018-12-19 10:37:30 Commandline: /usr/sbin/synaptic Requested-By: wim (1000) Upgrade: gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.1, 3.28.1-0ubuntu4.18.04.8), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.1, 3.28.1-0ubuntu4.18.04.8), unattended-upgrades:amd64 (1.1ubuntu1.18.04.5, 1.1ubuntu1.18.04.7), gnome-software-common:amd64 (3.28.1-0ubuntu4.18.04.1, 3.28.1-0ubuntu4.18.04.8) ... DpkgTerminalLog.txt: ... Configuratiebestand '/etc/xdg/autostart/gnome-software-service.desktop' ==> Gewijzigd (door u of door een script) sinds de installatie. ==> Pakketdistributeur heeft een bijgewerkte versie gemaakt. Wat wilt u er aan doen ? De volgende keuzes zijn mogelijk: Y of I : installeer de versie van de pakketbeheerder N of O : behoud de huidige geïnstalleerde versie D : toon de verschillen tussen de versies Z : start een shell om de situatie te onderzoeken De standaardactie is om uw huidige versie te behouden. *** gnome-software-service.desktop (Y/I/N/O/D/Z) [standaard=N] ? y Nieuwe versie van configuratiebestand /etc/xdg/autostart/gnome-software-service.desktop wordt geïnstalleerd ... Bezig met afhandelen van triggers voor systemd (237-3ubuntu10.9) ... Instellen van unattended-upgrades (1.1ubuntu1.18.04.7) ... root@wim-bigdell:/# y y: opdracht niet gevonden root@wim-bigdell:/# exit exit Gdk-[1;32mMessage[0m: [34m10:46:32.095[0m: frontend: Fatal IO error 0 (Gelukt) on X server :0.0. dpkg: fout bij verwerken van pakket unattended-upgrades (--configure): geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 ... The frontend works properly when it is used from apt CLI, and the question can also be avoided by placing a different configuration file snippet in /etc/apt/apt.conf.d/ sorting higher than the ones to be overridden. ** Also affects: synaptic (Ubuntu) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1809108 Title: package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post- installation script subproces meldde een fout afsluitstatus 1 Status in synaptic package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Bug description: i dont know what went wrong ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 19 10:46:32 2018 ErrorMessage: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 InstallationDate: Installed on 2018-12-18 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 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 "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-12-18T22:41:06.854870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1809108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795764] Re: systemd: core: Fix edge case when processing /proc/self/mountinfo
** Description changed: [Impact] kubernetes loaded inactive dead transient mount points grows https://github.com/kubernetes/kubernetes/issues/57345 [Test Case] # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest-abc.mount loaded inactive dead /tmp/bind-test/abc tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test Expected outcome (w/ the fix) : # cd /tmp # mkdir -p bind-test/abc # mount --bind bind-test bind-test # mount -t tmpfs tmpfs bind-test/abc # umount bind-test/abc # systemctl list-units --all | grep bind-test tmp-bind\x2dtest.mount loaded active mounted /tmp/bind-test [Regression Potential] This is a adapted version of 2 upstream fixes as the original upstream commit has been made on top on 2 functions mount_setup_new_unit() & mount_setup_existing_unit() that not yet exist systemd 229. It is easily adaptable because the current function mount_setup_unit() is dealing with both of at the moment instead of being individually separate in two distinct function. It is an adaptation of commits : [65d36b495] core: Fix edge case when processing /proc/self/mountinfo [03b8cfede] core: make sure to init mount params before calling mount_is_extrinsic() This patch changes mount_setup_unit() to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialised properly. Additionally, the patch got the blessing of 'xnox' who looked at it and mention it looks fine to him. [Pending SRU] Note: No autopkgtests has been reported since systemd (21.5) ... between 21.5 and now (21.11) everything released has been about security fixes : systemd (229-4ubuntu21.11) xenial; urgency=medium ==> Current SRU systemd (229-4ubuntu21.10) xenial-security; urgency=medium systemd (229-4ubuntu21.9) xenial-security; urgency=medium systemd (229-4ubuntu21.8) xenial-security; urgency=medium systemd (229-4ubuntu21.6) xenial-security; urgency=medium systemd (229-4ubuntu21.5) xenial; urgency=medium ==> Previous SRU + + + Note: I don't know the level of adoption of Netplan in Xenial, but I suspect it is low as Netplan replaced ifupdown as the default configuration utility starting with Ubuntu 17.10 Artful only AFAIK. * Regression in autopkgtest for nplan (s390x): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/n/nplan/20181023_132448_031b9@/log.gz Error: modprobe: FATAL: Module cfg80211 not found in directory /lib/modules/4.4.0-138-generic Justification: This above seems to be a recurrent failure since a couple of release already. This wasn't introduce by this particular SRU. I don't think having wifi module is relevant in s390x anyway, so most likely the module is not there on purpose for kernel w/ s390x architecture. * Regression in autopkgtest for nplan (amd64): test log https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nplan/20181217_010129_e07e2@/log.gz Error: (Ran on autopkgtest Ubuntu infra) test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL test_bridge_priority (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL test_dhcp6 (__main__.TestNetworkManager) ... Error: Could not create NMClient object: Cannot invoke method; proxy is for a well-known name without an owner and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag.FAIL Justification: The test are "passing" if ran manually in my own HW : autopkgtest [15:29:15]: host ; command line: /usr/bin/autopkgtest nplan -U --apt-pocket=proposed --log-file /tmp/adt-proposed.out --- qemu /var/lib/libvirt/images/autopkgtest-xenial-amd64.img . Setting up systemd (229-4ubuntu21.11) ... Setting up nplan (0.32~16.04.6) ... Setting up network-manager (1.2.6-0ubuntu0.16.04.3) ... test_dhcp6 (__main__.TestNetworkManager) ... ok test_bridge_priority (__main__.TestNetworkManager) ... ok test_bond_mode_balance_rr_pps (__main__.TestNetworkManager) ... ok I *think* that these test may eventually works, but is it really worth it to retry them until success if it works fine outside the Ubuntu infra w/ the same proposed packages ? (See attachment:
[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
This definitely occurs in both 18.04 & 19.04 but only in a ubuntu (gnome) session Is not an issue in wayland or unity(7) sessions ** Tags added: disco gnome-session -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Yes I already did that but I may not understand how to add the required maintainers into the mailing list Here is it https://bugzilla.kernel.org/show_bug.cgi?id=201613 ** Bug watch added: Linux Kernel Bug Tracker #201613 https://bugzilla.kernel.org/show_bug.cgi?id=201613 -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809110] [NEW] Intel drivers
Public bug reported: i wanna see if it helps with setting up vagrant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Wed Dec 19 14:33:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2018-01-28 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. 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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1809110 Title: Intel drivers Status in xorg package in Ubuntu: New Bug description: i wanna see if it helps with setting up vagrant ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Wed Dec 19 14:33:31 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f] InstallationDate: Installed on 2018-01-28 (324 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. OptiPlex 760 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0M858N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 760 dmi.sys.vendor: Dell Inc. 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.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go
[Touch-packages] [Bug 1809108] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fo
Public bug reported: i dont know what went wrong ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 19 10:46:32 2018 ErrorMessage: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 InstallationDate: Installed on 2018-12-18 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 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 "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-12-18T22:41:06.854870 ** Affects: unattended-upgrades (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1809108 Title: package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post- installation script subproces meldde een fout afsluitstatus 1 Status in unattended-upgrades package in Ubuntu: New Bug description: i dont know what went wrong ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 19 10:46:32 2018 ErrorMessage: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 InstallationDate: Installed on 2018-12-18 (0 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7 failed to install/upgrade: geïnstalleerd unattended-upgrades pakket post-installation script subproces meldde een fout afsluitstatus 1 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 "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-12-18T22:41:06.854870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1809108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
@Luca, I have no idea what is the root cause of this problem and how to fix it. Please file a bugzilla bug against the mainline linux kernel, let us ask for help from mainline kernel community where realtek engineer probably will be involved. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Any updates on this? -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809103] [NEW] Memory leak in evolution
Public bug reported: I have been experiencing huge memory leaks in evolution data server in the last days and I came to this bug report https://gitlab.gnome.org/GNOME/evolution-data-server/issues/46 which apparently has been fixed in 3.30.2. Ubuntu is currently using 3.30.1 so an upgrade seems encouraged ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1809103 Title: Memory leak in evolution Status in evolution-data-server package in Ubuntu: New Bug description: I have been experiencing huge memory leaks in evolution data server in the last days and I came to this bug report https://gitlab.gnome.org/GNOME/evolution-data-server/issues/46 which apparently has been fixed in 3.30.2. Ubuntu is currently using 3.30.1 so an upgrade seems encouraged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1809103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Mime is M585 and seems like it works with Bluez 5.50. There are lots of fixes in Bluez master, maybe some commits fix the issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Ah indeed... $ LANG=C apt policy bluez bluez: Installed: 5.50-0ubuntu1 Candidate: 5.50-0ubuntu1 Version table: *** 5.50-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status In that case I don't think I can confirm this fixes it, or maybe mine is a different issue (M535 mouse here). I've certainly had trouble pairing since I've upgraded to cosmic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Cosmic already has BlueZ 5.50 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
@Feng could you please rebuild for cosmic, too? I'll try it out then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 608150] Re: [Realtek ALC268] internal mic does not work
Aaahh, OK, sorry. Launchpad proposed me to choose this report. I will
make a new report.
--
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/608150
Title:
[Realtek ALC268] internal mic does not work
Status in pulseaudio package in Ubuntu:
Invalid
Bug description:
Binary package hint: pulseaudio
The microphone on this Acer aspire 7720 with the above audio chipset
does not produce any signal.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard3834 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x9b30 irq 17'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1025011e,0013
HDA:14f12c06,1025011e,0010'
Controls : 11
Simple ctrls : 8
Date: Wed Jul 21 15:14:59 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: pulseaudio
Symptom: audio
Title: [Realtek ALC268] PA test tone failed (alsa tone succeeded)
dmi.bios.date: 01/05/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.27
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Poyang
dmi.board.vendor: Acer
dmi.board.version: V1.27
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.27
dmi.modalias:
dmi:bvnAcer:bvrV1.27:bd01/05/2008:svnAcer:pnAspire7720:pvrV1.27:rvnAcer:rnPoyang:rvrV1.27:cvnAcer:ct1:cvrV1.27:
dmi.product.name: Aspire 7720
dmi.product.version: V1.27
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/608150/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809093] [NEW] Internal microphone doesn't work with Realtek ALC268 chipset
Public bug reported: I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers : HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset. Audio is working but not internal microphone (and on HP Pavilion, external microphone doesn't work too). As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I tried to add linux-backports-modules-*** but this package isn't anymore in Ubuntu and Mint repositories. I tried all options as explained in https://doc.ubuntu- fr.org/audio_intel_hda , no result. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6306 F pulseaudio CasperVersion: 1.399 Date: Wed Dec 19 09:35:53 2018 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.58 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6700 Notebook PC dmi.product.sku: KS356EA#ABF dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1809093 Title: Internal microphone doesn't work with Realtek ALC268 chipset Status in pulseaudio package in Ubuntu: New Bug description: I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers : HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset. Audio is working but not internal microphone (and on HP Pavilion, external microphone doesn't work too). As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I tried to add linux-backports-modules-*** but this package isn't anymore in Ubuntu and Mint repositories. I tried all options as explained in https://doc.ubuntu- fr.org/audio_intel_hda , no result. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6306 F pulseaudio CasperVersion: 1.399 Date: Wed Dec 19 09:35:53 2018 LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.58 dmi.board.name: 30D2 dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.58:bd06/16/2008:svnHewlett-Packard:pnHPPaviliondv6700NotebookPC:pvrRev1:rvnQuanta:rn30D2:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6700 Notebook PC dmi.product.sku: KS356EA#ABF dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1809093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 608150] Re: [Realtek ALC268] internal mic does not work
David, this bug has expired and is closed.
Please open your own new bugs.
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed => Invalid
--
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/608150
Title:
[Realtek ALC268] internal mic does not work
Status in pulseaudio package in Ubuntu:
Invalid
Bug description:
Binary package hint: pulseaudio
The microphone on this Acer aspire 7720 with the above audio chipset
does not produce any signal.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard3834 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x9b30 irq 17'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1025011e,0013
HDA:14f12c06,1025011e,0010'
Controls : 11
Simple ctrls : 8
Date: Wed Jul 21 15:14:59 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: pulseaudio
Symptom: audio
Title: [Realtek ALC268] PA test tone failed (alsa tone succeeded)
dmi.bios.date: 01/05/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.27
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Poyang
dmi.board.vendor: Acer
dmi.board.version: V1.27
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.27
dmi.modalias:
dmi:bvnAcer:bvrV1.27:bd01/05/2008:svnAcer:pnAspire7720:pvrV1.27:rvnAcer:rnPoyang:rvrV1.27:cvnAcer:ct1:cvrV1.27:
dmi.product.name: Aspire 7720
dmi.product.version: V1.27
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/608150/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805857] Re: network-manager dep8 failure blocks dnsmasq proposed migration
IRC comment from upstream on #nm in case it's useful 'not that `nmcli device disconnect $DEV` and `nmcli connection down $PROFILE` do not set the interface down (like `ip link set $IF down`). Instead, the ~logically~ disconnect the interface, which essentially means that `nmcli device` reports that the device is disconnected and that there is no IP configuration on the device. asserting that the interface is down, may just check the wrong thing.' -- 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/1805857 Title: network-manager dep8 failure blocks dnsmasq proposed migration Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Disco: Triaged Bug description: dnsmasq 2.80-1 is blocked from migrating to the release pocket because of, amongst other things, a network-manager dep8 regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1805857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 608150] Re: [Realtek ALC268] internal mic does not work
Files
--
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/608150
Title:
[Realtek ALC268] internal mic does not work
Status in pulseaudio package in Ubuntu:
Invalid
Bug description:
Binary package hint: pulseaudio
The microphone on this Acer aspire 7720 with the above audio chipset
does not produce any signal.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard3834 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x9b30 irq 17'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1025011e,0013
HDA:14f12c06,1025011e,0010'
Controls : 11
Simple ctrls : 8
Date: Wed Jul 21 15:14:59 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: pulseaudio
Symptom: audio
Title: [Realtek ALC268] PA test tone failed (alsa tone succeeded)
dmi.bios.date: 01/05/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.27
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Poyang
dmi.board.vendor: Acer
dmi.board.version: V1.27
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.27
dmi.modalias:
dmi:bvnAcer:bvrV1.27:bd01/05/2008:svnAcer:pnAspire7720:pvrV1.27:rvnAcer:rnPoyang:rvrV1.27:cvnAcer:ct1:cvrV1.27:
dmi.product.name: Aspire 7720
dmi.product.version: V1.27
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/608150/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 608150] Re: [Realtek ALC268] internal mic does not work
I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers :
HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset.
Audio is working but not internal microphone (and on HP Pavilion, external
microphone doesn't work too).
As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I tried
to add linux-backports-modules-*** but this package isn't anymore in Ubuntu and
Mint repositories.
I tried all options as explained in https://doc.ubuntu-
fr.org/audio_intel_hda , no result. Please heelp.
** Changed in: pulseaudio (Ubuntu)
Status: Expired => Confirmed
--
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/608150
Title:
[Realtek ALC268] internal mic does not work
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Binary package hint: pulseaudio
The microphone on this Acer aspire 7720 with the above audio chipset
does not produce any signal.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: richard3834 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x9b30 irq 17'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,1025011e,0013
HDA:14f12c06,1025011e,0010'
Controls : 11
Simple ctrls : 8
Date: Wed Jul 21 15:14:59 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: pulseaudio
Symptom: audio
Title: [Realtek ALC268] PA test tone failed (alsa tone succeeded)
dmi.bios.date: 01/05/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.27
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Poyang
dmi.board.vendor: Acer
dmi.board.version: V1.27
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.27
dmi.modalias:
dmi:bvnAcer:bvrV1.27:bd01/05/2008:svnAcer:pnAspire7720:pvrV1.27:rvnAcer:rnPoyang:rvrV1.27:cvnAcer:ct1:cvrV1.27:
dmi.product.name: Aspire 7720
dmi.product.version: V1.27
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/608150/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
It should be fairly safe. -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To
[Touch-packages] [Bug 1809088] [NEW] Application startup fail, the whole GUI is freezing during startup
Public bug reported: DESCRIPTION: When I trying to start this application, the whole GUI is just freezing for minutes. After that application just stops with an error message or application started up, but the window could not loaded correctly, the window just full with squares. Environment details:__ Ubuntu version: Ubuntu 16.04 LTS (4.15.0-42-generic #45~16.04.1-Ubuntu) CPU Architecture: 64bit CPU: Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 Graphic card: Intel® HD Graphics 620 (Kaby Lake GT2) CLI Output:__ (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information unity::action::ActionManager::ActionManager(QObject*): Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable. UCUriHandler: Empty "APP_ID" environment variable, ignoring. file:///usr/share/webbrowser-app/webbrowser/ContentPickerDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webbrowser/ContentDownloadDialog.qml:22:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/ContentHandler.qml:20:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/webbrowser/DownloadHandler.qml:20:1: module "Ubuntu.DownloadManager" is not installed (webbrowser-app:11283): IBUS-WARNING **: Unable to connect to ibus: Nem sikerült kapcsolódni: Engedély megtagadva libGL error: MESA-LOADER: failed to retrieve device information libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915 libGL error: MESA-LOADER: failed to retrieve device information shm_open() failed: Engedély megtagadva (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. (webbrowser-app:11283): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Engedély megtagadva. dconf will not work properly. [1219/100111.415397:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain TouchSelectionController::active is deprecated, use TouchSelectionController::status instead qml: Loaded 8 UA override(s) from file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-mobile.js OxideQQuickWebView: canGoForward is deprecated. Please use the API provided by OxideQQuickNavigationHistory instead OxideQQuickWebView: canGoBack is deprecated. Please use the API provided by OxideQQuickNavigationHistory instead file:///usr/share/webbrowser-app/Downloader.qml:23:1: module "Ubuntu.Content" is not installed file:///usr/share/webbrowser-app/Downloader.qml:22:1: module "Ubuntu.DownloadManager" is
[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Seems like Bluez 5.50 fixes the issue, tried re-repairing BT mouse 5 times and it seems to work so far. I guess this commit fixes the issue: commit a07eb3a5e96d7f23a2aa554088d3cc3a9e57744f Author: Andrzej Kaczmarek Date: Thu Mar 22 16:21:00 2018 +0100 shared/gatt-client: Fix discovery of discontinuous database A simple Disco rebuild for Bionic PPA for testing: https://launchpad.net/~kaihengfeng/+archive/ubuntu/lp1773897 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected Status in Bluez Utilities: Confirmed Status in OEM Priority Project: New Status in bluez package in Ubuntu: Confirmed Bug description: The BT 3.0 mouse is disconnected automatically after connected with the notebook. The fail rate is around 9/10. 1. The bug only occurs on the machine with intel 8265 module. I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265). This bug can not be reproduced on the machine with Killer 1435. 2. This bug can be reproduced since bluez 5.46. Using bluez 5.45, this bug can not be reproduced. Notebook: Dell XPS 13 Wi-Fi/BT module: intel 8265, 8087:0a2b bluez: 5.48 BT mouse: logitech M337 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 27c6:5385 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: third-party-packages bionic Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.3.13 dmi.board.name: 0173S1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: D4:25:8B:4F:7E:D6 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:61781 acl:382 sco:0 events:536 errors:0 TX bytes:7985 acl:69 sco:0 commands:168 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806458] Re: Intel I219-V ethernet connection lost
A stupid question: I'm using mainly Ubuntu Disco; can I install an old kernel like v4.4.X without problems? -- 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/1806458 Title: Intel I219-V ethernet connection lost Status in systemd package in Ubuntu: New Bug description: Ethernet connection id dropped randomly, sometimes works fine for the whole day, sometimes the connection falls 2 or 3 times i a hour. I'm reporting this bug being unable to add usable info to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171 that seems similar. I have the problem with Ubuntu 18.10 with standard kernel and with 19.04 with standard (4.18.0-11) and with 4.20.0-042000rc4 mainline kernel. When the connection drops i can restart it just closing and restarting the net. Problem: when the connection is dropped and i run 'ubuntu-bug systemd' i'm forced to do reconnect to send the doc. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: systemd 239-7ubuntu14 Uname: Linux 4.20.0-042000rc4-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 18:33:12 2018 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.20.0-042000rc4-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-07 (26 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181107) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: systemd 239-7ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=841241bf-e35d-4dee-a750-dac4a9bda901 ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Tags: wayland-session disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be
[Touch-packages] [Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Was your /tmp filesystem full at the time of the problem maybe? Marking invalid for chromium-browser, as it's unlikely it's a problem in chromium itself (besides the actual crash that you were trying to report, but without an actual core dump we can't do anything about that one, unfortunately). ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated Status in apport package in Ubuntu: Incomplete Status in chromium-browser package in Ubuntu: Invalid Bug description: Trying to report a crash in chromium-browser, get Unreportable reason Invalid core dump: BFD: warning apport_core is truncated (see screenshot, can't copy message from apport dialog - bug # 1273752). UnreportableReason: Invalid core dump: BFD: warning: /tmp/apport_core_6yb3cl_7 is truncated: expected core file size >= 1245646848, found: 760283136 warning: core file may not match specified executable file. Expected: able to report ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportLog: ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: called for pid 15848, signal 5, core limit 0, dump mode 1 ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser\ --enable-pinch") ERROR: apport (pid 31805) Mon Dec 17 15:14:09 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 31805) Mon Dec 17 15:15:23 2018: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 17 15:30:28 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-12 (96 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-09-28 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809084] [NEW] Confirm prompt for systemctl --full edit is redundant and interferes with scripting
Public bug reported: On Ubuntu version Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 and systemd package Version: 229-4ubuntu21.10 When the --full argument is used with systemctl edit a confirm prompt of ...some.service" already exists. Overwrite with "..."? [(y)es, (n)o] is issued. Since the systemctl edit command won't function w/o a unit file in place the message tells the user something they already know. There appears to be no way to bypass this message, so it makes running systemctl edit from a script more difficult. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1809084 Title: Confirm prompt for systemctl --full edit is redundant and interferes with scripting Status in systemd package in Ubuntu: New Bug description: On Ubuntu version Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 and systemd package Version: 229-4ubuntu21.10 When the --full argument is used with systemctl edit a confirm prompt of ...some.service" already exists. Overwrite with "..."? [(y)es, (n)o] is issued. Since the systemctl edit command won't function w/o a unit file in place the message tells the user something they already know. There appears to be no way to bypass this message, so it makes running systemctl edit from a script more difficult. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1809084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
