[Touch-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
Using the supplied instructions I can't reproduce the bug. Any more hints? ** Package changed: wayland (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820490] Re: i find them while xdiagnose
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/1820490 Title: i find them while xdiagnose Status in Ubuntu: Incomplete Bug description: these bugs must be cleans and further bugs should be reported ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Mar 17 09:20:02 2019 DistUpgraded: 2019-03-15 15:41:59,975 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2019-02-26 (18 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=35f08810-0153-46db-9a01-b9159f8cb46e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-15 (1 days ago) dmi.bios.date: 05/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0FKWR5 dmi.board.vendor: Dell Inc. dmi.board.version: A14 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0FKWR5:rvrA14:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 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: Fri Mar 15 10:45:31 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1110 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820371] Re: PCI/internal sound card not detected
The kernel is reporting zero supported sound cards: !!Soundcards recognised by ALSA !!- --- no soundcards --- ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- 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/1820371 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Incomplete Bug description: no sound in dell inspirion soundcard unknown ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-166.216-generic 3.13.11-ckt39 Uname: Linux 3.13.0-166-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Mar 16 06:55:24 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2019-03-15 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 04XH5N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3551:pvrA00:rvnDellInc.:rn04XH5N:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3551 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820371/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820323] Re: xorg crash
Also, to help us find crashes from other people are the same as this one, please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => xorg-server (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/1820323 Title: xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: This is on Precision 3620, Precision 5820, Precision 7820 - systems with AMD bundled for OEM fail to properly boot after update/upgrade. I believe this is related to this issue: https://www.amd.com/en/support/kb/faq/amdgpupro-ubuntu-advisory Since our image contains the amdgpu-pro package we are impacted. Canonical image is not impacted. Various systems (Precision 3420, 3620, 5820, and 7820) are having login issues with AMD GPUs after running system updates on the OEM Ubuntu image. After running sudo apt-get update && apt-get upgrade, the system will exhibit one of a few different behaviors: • Boots to a black screen • Loops at login • Boots to a screen indicating the system has been forced to low graphics mode and hard locks. I have a systems in the lab that exhibits this issue and I don’t know how to get around it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 267691/28237824 files, 3796147/112924672 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Mar 15 13:22:36 2019 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 ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: Dell Device [1028:06c7] Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 2100] [1002:6995] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0b0c] InstallationDate: Installed on 2019-03-14 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision Tower 3420 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-143-generic root=UUID=ced18cfc-68aa-461d-a69d-d482f5880d16 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.2 dmi.board.name: 02K9CR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.2:bd11/07/2018:svnDellInc.:pnPrecisionTower3420:pvr:rvnDellInc.:rn02K9CR:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.name: Precision Tower 3420 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: Fri Mar 15 13:21:28 2019 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all
*** This bug is a duplicate of bug 1820314 *** https://bugs.launchpad.net/bugs/1820314 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1820314, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1820314 [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all -- 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/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 15 17:39:40 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio /dev/snd/seq:timidity 1238 F timidity Symptom_Jack: Blue Line In, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I hit this bug on Fedora 28 when using a third-party mesa build. Here's the ~/.drirc I used to fix this: This also fixed the timecode in Totem showing strange, rainbow colors, caused by the same thing. Repeat the application section as required for each program affected. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820303] Re: Ubuntu 18.04 LTS
Can you select the session you want on the login screen by clicking on the cog/gear icon? ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (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/1820303 Title: Ubuntu 18.04 LTS Status in gdm3 package in Ubuntu: Incomplete Bug description: Failure to display prior desktop login GUI (Cinnamon). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 15 11:46:27 2019 DistUpgraded: 2019-03-15 10:30:23,145 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7] InstallationDate: Installed on 2019-03-11 (4 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: ASUSTeK COMPUTER INC. X55U ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago) dmi.bios.date: 08/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55U.423 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55U 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.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X55U dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 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: Fri Mar 15 11:19:59 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
** Tags added: disco ** Package changed: xorg (Ubuntu) => xorg-server (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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg-server package in Ubuntu: Triaged Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1819943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Thanks. That reminds me, make sure you don't have 'tlp' installed. Because that would be bug 1574311 instead. ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 201391] Re: Headset volume control doesn't change headset volume
It's been over 9 years since this bug was closed. So if you'd like to discuss any problems you're still having today then it would be better to open a new bug by running: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/201391 Title: Headset volume control doesn't change headset volume Status in pulseaudio package in Ubuntu: Fix Released Bug description: I use Kubuntu Hardy and have a Plantronics USB headset that has its own volume and mute controls. When using its volume controls, they affect the master volume only and have no effect on the headset volume. I can only alter the headset volume by going into kmix and selecting the appropriate device and altering its PCM volume. The master volume setting should affect the headset volume too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/201391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820368] Re: x
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/1820368 Title: x Status in Ubuntu: Incomplete Bug description: xx ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 16 04:31:02 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2017-05-23 (661 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 4291BD2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=71ccb682-9ba5-4c82-8ab3-e914e7f1835d ro rootflags=sync drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291BD2 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: BB70354824 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET76WW(1.46):bd06/21/2018:svnLENOVO:pn4291BD2:pvrThinkPadX220:rvnLENOVO:rn4291BD2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 4291BD2 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 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 Oct 11 18:41:18 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 723 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819132] Re: DNS is broken after reboot or suspend
Marking as fix released because it looks like this was resolved by this morning's update (by a reconfiguration of systemd? dpkg.log says that it installed version 240-6ubuntu2, but it also says that this version has been installed since the 13th of March). /etc/resolv.conf now contains "nameserver 127.0.0.53". ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1819132 Title: DNS is broken after reboot or suspend Status in systemd package in Ubuntu: Fix Released Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove kernel packages that become unused in conjunction with updating by other software
rbalint, in the output there is some oddity: "Keeping auto-removable linux-image-extra-4.8.0-54-generic package(s) because it would also remove the following packages which should be kept in this step: libpam-systemd libsystemd0 libudev1 systemd systemd-sysv udev (Reading database ... 53554 files and directories currently installed.) Removing linux-image-extra-4.8.0-54-generic (4.8.0-54.57~16.04.1) ..." So it says it is keeping linux-image-extra-4.8.0-54-generic and right thereafter it is removing the same package. ** Summary changed: - By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software + By default settings unattended-upgrade does not automatically remove kernel packages that become unused in conjunction with updating by other software -- 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/1624644 Title: By default settings unattended-upgrade does not automatically remove kernel packages that become unused in conjunction with updating by other software Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-manager source package in Xenial: Fix Released Status in unattended-upgrades source package in Artful: Won't Fix Status in update-manager source package in Artful: Fix Released Bug description: [Impact] * Update-manager and unattended-upgrades install many kernel packages during the lifetime of a release but does not remove them automatically leading to those packages filling disk space potentially completely filling /boot and making the system unable to install updates or even boot. * Stable release users are impacted by this bug for years and their systems already collected many autoremovable unused kernel packages, thus they would benefit from backporting the fix greatly. * The bug is fixed by removing autoremovable (not currently booted) kernel packages when running unattended-upgrades or update-manager. Update manager offers the kernel removals when there are other updates to be installed. [Test Case] 1. Install kernel packages to be removed, mark them auto-installed and run apt's kernel hook script to make apt consider them autoremovable: sudo apt install -y linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo apt-mark auto linux-image-extra-4.4.0-92-generic linux-image-extra-4.4.0-93-generic sudo /etc/kernel/postinst.d/apt-auto-removal 2. Also downgrade a package to be upgraded: sudo apt-get install -y --allow-downgrades ca- certificates=20160104ubuntu1 3. (update-manager). Run update-manager and observe that kernel packages are offered for removal in Details of updates. sudo update-manager 4. (update-manager) Click on Install Now and observe that the kernel packages are removed. 3. (unattended-upgrades, the fix comes in an update of u-u) Run unattended-upgrades manually and observe the removal of the autoremovable kernel packages: sudo unattended-upgrade -v [Regression Potential] The change may cause update-manager or unattanded-upgrades to remove used kernel packages or fail to install other package updates. [Other Info] The unattended-upgrades fix is uploaded with many other fixes and those may cause regressions in other areas in unattended-upgrades. [Original bug text] When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days
[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks
I saw the discussion in zfs-discuss and read a bit for fun. To answer some old questions from what i understood from linked resources: This bug/deficiency seem to make it impossible to see all drives behind a port multiplier when using links in /dev/disk/by-path/ but not other links, making the drives unadressable by slot. This can be fixed by patching systemd. Why this haven't been done seems to be summarized here: https://github.com/systemd/systemd/issues/3943#issuecomment-404996399 The patch submitted here seems to be outdated, later one found here: https://github.com/sitsofe/systemd/commit/ee26c33ede684138ba9fdc7f286bfa402860aff3 IMHO, the easiest (but not easy) way to add this patch in Ubuntu on your own would be to create an PPA and rebuild systemd from ubuntu with the patch added. Note that you'll be responsible for keeping your systemd- package up to date on your own and that changes can be made upstream that breaks the patch. It could be added in the official ubuntu package of systemd, but I'm guessing they don't want to add a patch that adds a naming scheme for drives that later might change when the proper fix mentioned last in the first link is implemented. -- 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/1611945 Title: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks Status in systemd package in Ubuntu: Confirmed Bug description: We have a just-installed Ubuntu 16.04 LTS machine with a number of disks behind port-multiplier eSATA ports, all of them driven by a SiI 3124 controller (sata_sil24 kernel driver). Our machine sees all disks on all channels, however under 16.04 only one disk from each channel shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id and /dev/disk/by-uuid). For our usage this is a severe defect because we rotate disks in and out of the external enclosure and rely on mounting specific slots in the external enclosure through /dev/disk /by-path. This did not happen in Ubuntu 12.04 LTS, the release that this machine was previously running. According to 'udevadm info --export-db' and 'udevadm test-builtin path_id' and so on, systemd's udev stuff is assigning all drives behind the same port the same disk/by-path data (ID_PATH et al). In 'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show a difference in the target portion of PCI path, eg: P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH' portions do not. For both devices above, we see: S: disk/by-path/pci-:02:00.0-ata-1 E: ID_PATH=pci-:02:00.0-ata-1 Naturally only one device can have a /dev/disk/by- path/pci-:02:00.0-ata-1 symlink, so instead of four disks per channel in /dev/disk/by-path we see one. Ubuntu release: 16.04 Package versions from 'apt-cache policy udev systemd': udev: Installed: 229-4ubuntu7 systemd: Installed: 229-4ubuntu7 'journalctl -b' reports that during boot systemd does report some 'appeared twice with different sysfs paths' notes, eg: Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath- pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1 and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 However it doesn't seem to be reporting this for all port-multiplier drives and their partitions. If it would be useful I can attach full 'udevadm info --export-db' output or the like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks
I have this same problem for some time and on the latest update too. all of the discs affected are used in a zfs zpool. uname -a Linux PEI-Server 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux cat /sys/module/zfs/version 0.7.5-1ubuntu16.4 I have a total of 6 discs split equally across 2 esata port multipliers. All are part a a single raidz2 pool. Zillions of these errors: Mar 3 22:04:48 PEI-Server systemd[1]: dev-disk-by\x2dpath-pci\x2d:07:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by\x2dpath-pci\x2d:07:00.0\x2data\x2d1\x2dpart1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:1c.2/:07:00.0/ata3/host2/target2:0:0/2:0:0:0/block/sdd/sdd1 and /sys/devices/pci:00/:00:1c.2/:07:00.0/ata3/host2/target2:1:0/2:1:0:0/block/sde/sde1 I have lots of detailed data if anyone wants to see it. It would REALLY be nice if a fix trickled down soon... thanks rich -- 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/1611945 Title: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks Status in systemd package in Ubuntu: Confirmed Bug description: We have a just-installed Ubuntu 16.04 LTS machine with a number of disks behind port-multiplier eSATA ports, all of them driven by a SiI 3124 controller (sata_sil24 kernel driver). Our machine sees all disks on all channels, however under 16.04 only one disk from each channel shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id and /dev/disk/by-uuid). For our usage this is a severe defect because we rotate disks in and out of the external enclosure and rely on mounting specific slots in the external enclosure through /dev/disk /by-path. This did not happen in Ubuntu 12.04 LTS, the release that this machine was previously running. According to 'udevadm info --export-db' and 'udevadm test-builtin path_id' and so on, systemd's udev stuff is assigning all drives behind the same port the same disk/by-path data (ID_PATH et al). In 'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show a difference in the target portion of PCI path, eg: P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH' portions do not. For both devices above, we see: S: disk/by-path/pci-:02:00.0-ata-1 E: ID_PATH=pci-:02:00.0-ata-1 Naturally only one device can have a /dev/disk/by- path/pci-:02:00.0-ata-1 symlink, so instead of four disks per channel in /dev/disk/by-path we see one. Ubuntu release: 16.04 Package versions from 'apt-cache policy udev systemd': udev: Installed: 229-4ubuntu7 systemd: Installed: 229-4ubuntu7 'journalctl -b' reports that during boot systemd does report some 'appeared twice with different sysfs paths' notes, eg: Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath- pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1 and /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 However it doesn't seem to be reporting this for all port-multiplier drives and their partitions. If it would be useful I can attach full 'udevadm info --export-db' output or the like. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751657] Re: man journalctl gives info about -g option not present in command
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1751657 Title: man journalctl gives info about -g option not present in command Status in systemd package in Ubuntu: Confirmed Bug description: man journalctl documents a --grep option, however: $ journalctl -g a journalctl: invalid option -- 'g' $ journalctl --grep a Compiled without pattern matching support ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Feb 25 21:53:29 2018 InstallationDate: Installed on 2017-06-21 (248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 004: ID 10d7:1102 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash acpi_rev_override=5 pci=noaer vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago) dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)
[58.994] Require OpenGL version 2.1 or later. [58.994] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time. ok then, looks like -intel needs to be added back to xserver-xorg-video- all Recommends... sigh ** Package changed: xserver-xorg-video-intel (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Incomplete => Triaged -- 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/1819943 Title: intel video driver not installed by default in ubuntu 19.04 (Disco) Status in xorg package in Ubuntu: Triaged Bug description: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819943] [NEW] intel video driver not installed by default in ubuntu 19.04 (Disco)
You have been subscribed to a public bug: I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then updated grub. Restarted the computer and on booting the ISO no login screen appeared. However,after pressing alt + ctrl + F2, logging in at command prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and unity" I was able to get to the desktop by running the command 'sudo service lightdm start'. Command 'startx and X" gave xorg error saying server could not be connected. Command "sudo service gdm(3) start' went back to command prompt ($). This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing intel video driver and running startx command i was able to get to the desktop. Whether, "xserver-xorg-video-intel" package is not being installed by default in ubuntu or support for "intel core2duo processor" has been withdrawn. ** Affects: xorg (Ubuntu) Importance: Undecided Status: Triaged -- intel video driver not installed by default in ubuntu 19.04 (Disco) https://bugs.launchpad.net/bugs/1819943 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1820536] Re: print dialog cups "advanced tab" missing in qt5/kf5 based applications
*** This bug is a duplicate of bug 1776173 *** https://bugs.launchpad.net/bugs/1776173 The duplex settings were added in qtbase 5.9.5+dfsg-0ubuntu2, which is currently available in bionic-proposed. The whole "Advanced" tab is impossible to backport. If you look at openSUSE, they have not just patch 0010, but also a lot of patches related to printing: https://build.opensuse.org/package/show/openSUSE:Leap:15.0/libqt5-qtbase These patches change the code completely and also change (private) API/ABI, so they do not meet the Ubuntu stable release criteria. ** This bug has been marked a duplicate of bug 1776173 qt print dialog shipped with bionic ignores printer defaults -- 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/1820536 Title: print dialog cups "advanced tab" missing in qt5/kf5 based applications Status in qtbase-opensource-src package in Ubuntu: New Bug description: Qt5 (KDE) print dialogs do not show the "Advanced" for cups printers in Qt 5.9.5, making the user unable to change settings like duplex printing. The problem has been reported at https://bugreports.qt.io/browse/QTBUG-54464 It has been fixed in https://codereview.qt-project.org/#/c/213391/ Please backport this fix to 18.04 since this is an essential feature missing in a LTS release. There is a patch to Qt 5.9.4 made by the openSUSE devs: https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0/libqt5-qtbase/0010 -Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1820536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
Some more info: - The machine is a Virtualbox ubuntu bionic, and I have a snapshot before the upgrade, so I can reproduce it - I'm using ifconfig instead of netplan, because I need a ppp interface (for pppoe) - I have an /etc/network/interfaces file - it seems that the interface through which I'm using ssh loses it's IP address (defined in the interfaces file as static) - I also did these after installing bionic: "systemctl disable systemd-networkd-wait-online.service systemctl mask systemd-networkd-wait-online.service" because it was holding up the boot process for a long period -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1820542] [NEW] In a wayland session opening text file in gedit causes busy cursor
Public bug reported: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco regression reproducible single-occurrence ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in wayland package in Ubuntu: New Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version:
[Touch-packages] [Bug 1820536] [NEW] print dialog cups "advanced tab" missing in qt5/kf5 based applications
Public bug reported: Qt5 (KDE) print dialogs do not show the "Advanced" for cups printers in Qt 5.9.5, making the user unable to change settings like duplex printing. The problem has been reported at https://bugreports.qt.io/browse/QTBUG-54464 It has been fixed in https://codereview.qt-project.org/#/c/213391/ Please backport this fix to 18.04 since this is an essential feature missing in a LTS release. There is a patch to Qt 5.9.4 made by the openSUSE devs: https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0/libqt5-qtbase/0010 -Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=0 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- 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/1820536 Title: print dialog cups "advanced tab" missing in qt5/kf5 based applications Status in qtbase-opensource-src package in Ubuntu: New Bug description: Qt5 (KDE) print dialogs do not show the "Advanced" for cups printers in Qt 5.9.5, making the user unable to change settings like duplex printing. The problem has been reported at https://bugreports.qt.io/browse/QTBUG-54464 It has been fixed in https://codereview.qt-project.org/#/c/213391/ Please backport this fix to 18.04 since this is an essential feature missing in a LTS release. There is a patch to Qt 5.9.4 made by the openSUSE devs: https://build.opensuse.org/package/view_file/openSUSE:Leap:15.0/libqt5-qtbase/0010 -Reintroduce-the-Advanced-tab-in-the-QPrintProperties.patch?expand=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1820536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
Also I see this in the logs, but maybe not related (why can't I edit my comments?) Mar 17 19:31:55 localhost systemd-networkd-wait-online[14189]: Event loop failed: Connection timed out Mar 17 19:31:55 localhost apt-helper[14171]: E: Sub-process /lib/systemd/systemd-networkd-wait-online returned an error code (1) Mar 17 19:31:55 localhost systemd[1]: apt-daily.service: Control process exited, code=exited status=100 Mar 17 19:31:55 localhost systemd[1]: apt-daily.service: Failed with result 'exit-code'. Mar 17 19:31:55 localhost systemd[1]: Failed to start Daily apt download activities. -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
And logging in on the console the apt process was waiting on for some answers: ps aux | grep apt root 13335 0.1 6.6 116500 67388 pts/1S+ 19:30 0:00 apt upgrade root 15048 0.0 0.3 11856 3628 pts/3S+ 19:31 0:00 /bin/bash /usr/bin/ucf --three-way --debconf-ok /usr/share/unattended-upgrades/20auto-upgrades-disabled /etc/apt/apt.conf.d/20auto-upgrades root 15090 0.0 0.4 24460 4976 pts/3S+ 19:31 0:00 whiptail --backtitle Package configuration --title Configuring unattended-upgrades --output-fd 11 --nocancel --default-item keep the local version currently installed --menu A new version (/usr/share/unattended-upgrades/20auto-upgrades-disabled) of configuration file /etc/apt/apt.conf.d/20auto-upgrades is available, but the version installed currently has been locally modified. What do you want to do about modified configuration file 20auto-upgrades? 17 211 7 -- install the package maintainer's version keep the local version currently installed show the differences between the versions show a side-by-side difference between the versions show a 3-way difference between available versions do a 3-way merge between available versions start a new shell to examine the situation root 16771 0.0 0.1 13136 1148 tty1 S+ 19:41 0:00 grep --color=auto apt -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp.
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
Just happened to me too: root@gw:/etc# apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: eatmydata libeatmydata1 python3-blinker python3-jinja2 python3-json-pointer python3-jsonpatch python3-jsonschema python3-jwt python3-markupsafe python3-oauthlib Use 'apt autoremove' to remove them. The following packages will be upgraded: apport busybox-initramfs busybox-static docker.io initramfs-tools initramfs-tools-bin initramfs-tools-core landscape-common libidn11 libnss-systemd libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g libpci3 libseccomp2 libsystemd0 libudev1 libx11-6 libx11-data libxcb1 pciutils python3-apport python3-gi python3-problem-report systemd systemd-sysv udev unattended-upgrades 30 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 54.0 MB of archives. After this operation, 37.2 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam0g amd64 1.1.8-3.6ubuntu2.18.04.1 [55.1 kB] Get:2 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-modules-bin amd64 1.1.8-3.6ubuntu2.18.04.1 [36.7 kB] Get:3 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-modules amd64 1.1.8-3.6ubuntu2.18.04.1 [242 kB] Get:4 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libnss-systemd amd64 237-3ubuntu10.15 [105 kB] Get:5 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libsystemd0 amd64 237-3ubuntu10.15 [205 kB] Get:6 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-systemd amd64 237-3ubuntu10.15 [108 kB] Get:7 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd amd64 237-3ubuntu10.15 [2,899 kB] Get:8 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 udev amd64 237-3ubuntu10.15 [1,100 kB] Get:9 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libudev1 amd64 237-3ubuntu10.15 [54.2 kB] Get:10 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpam-runtime all 1.1.8-3.6ubuntu2.18.04.1 [37.1 kB] Get:11 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 initramfs-tools all 0.130ubuntu3.7 [9,592 B] Get:12 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 initramfs-tools-core all 0.130ubuntu3.7 [48.1 kB] Get:13 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 initramfs-tools-bin amd64 0.130ubuntu3.7 [12.8 kB] Get:14 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 busybox-initramfs amd64 1:1.27.2-2ubuntu3.1 [166 kB] Get:15 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 systemd-sysv amd64 237-3ubuntu10.15 [12.0 kB] Get:16 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libseccomp2 amd64 2.3.1-2.1ubuntu4.1 [39.1 kB] Get:17 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libidn11 amd64 1.33-2.1ubuntu1.1 [45.9 kB] Get:18 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-gi amd64 3.26.1-2ubuntu1 [153 kB] Get:19 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 busybox-static amd64 1:1.27.2-2ubuntu3.1 [918 kB] Get:20 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 pciutils amd64 1:3.5.2-1ubuntu1.1 [257 kB] Get:21 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpci3 amd64 1:3.5.2-1ubuntu1.1 [24.1 kB] Get:22 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libx11-data all 2:1.6.4-3ubuntu0.2 [113 kB] Get:23 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb1 amd64 1.13-2~ubuntu18.04 [45.5 kB] Get:24 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libx11-6 amd64 2:1.6.4-3ubuntu0.2 [569 kB] Get:25 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-problem-report all 2.20.9-0ubuntu7.6 [9,884 B] Get:26 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-apport all 2.20.9-0ubuntu7.6 [81.7 kB] Get:27 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 apport all 2.20.9-0ubuntu7.6 [124 kB] Get:28 http://hu.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 docker.io amd64 18.09.2-0ubuntu1~18.04.1 [46.4 MB] Get:29 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 landscape-common amd64 18.01-0ubuntu3.3 [85.3 kB] Get:30 http://hu.archive.ubuntu.com/ubuntu bionic-updates/main amd64 unattended-upgrades all 1.1ubuntu1.18.04.9 [40.0 kB] Fetched 54.0 MB in 5s (11.2 MB/s) Preconfiguring packages ... (Reading database ... 115046 files and directories currently installed.) Preparing to unpack .../libpam0g_1.1.8-3.6ubuntu2.18.04.1_amd64.deb ... Unpacking libpam0g:amd64 (1.1.8-3.6ubuntu2.18.04.1) over (1.1.8-3.6ubuntu2) ... Setting up libpam0g:amd64 (1.1.8-3.6ubuntu2.18.04.1) ... (Reading database ... 115046 files and
[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
I could only resolve the ssh issue with killing the apt process, and restarted networking. This is a pretty bad issue imho. Upgrading packages through ssh should not disconnect the session, but even if it is, upgrading the systemd package should not result in not being able to log back in ever again! -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820510] Re: Build errors against recent valac
The attachment "0001-Fix-build-errors-but-not-warnings-with- vala-044.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1820510 Title: Build errors against recent valac Status in libunity: New Status in libunity package in Ubuntu: New Bug description: I'd like to build Geary with support for Unity indicators in the Geary Flatpak package, but it's failing to build against recent valac: mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ vala --version Vala 0.44.0 mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ make make all-recursive make[1]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig' Making all in data make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' ITMRG com.canonical.Unity.Lenses.gschema.xml GEN com.canonical.Unity.Lenses.gschema.valid make[2]: Leaving directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' Making all in protocol make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/protocol' GEN libunity_protocol_private_la_vala.stamp Command-line option `--thread` is deprecated and will be ignored protocol-scope-discovery.vala:24.3-24.40: warning: the modifier `static' is not applicable to constants private static const string SCOPES_DIR = "unity/scopes"; ^^ protocol-scope-discovery.vala:190.5-190.43: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP = "Scope"; ^^^ protocol-scope-discovery.vala:191.5-191.45: warning: the modifier `static' is not applicable to constants private static const string DESKTOP_GROUP = "Desktop Entry"; ^ protocol-scope-discovery.vala:902.5-902.49: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP_GROUP = "Scope Group"; ^ protocol-preview-player.vala:41.3-41.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_NAME = "com.canonical.Unity.Lens.Music.PreviewPlayer"; protocol-preview-player.vala:42.3-42.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_PATH = "/com/canonical/Unity/Lens/Music/PreviewPlayer"; protocol-scope-interface.vala:117.3-117.51: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async ActivationReplyRaw activate ( ^ protocol-scope-interface.vala:124.3-124.57: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable search ( ^^^ protocol-scope-interface.vala:134.7-134.46: error: Synchronous out-parameters are not supported in async methods out HashTable out_hints, protocol-scope-interface.vala:130.3-130.43: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async string open_channel ( ^ protocol-scope-interface.vala:137.3-137.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void close_channel ( protocol-scope-interface.vala:142.3-142.63: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable push_results ( ^ protocol-scope-interface.vala:151.3-151.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void set_view_type (uint view_type) throws IOError; unity-scope-proxy-remote.vala:379.12-379.21: error: The name `channel_id' does not exist in the context of
Re: [Touch-packages] [Bug 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all
thx for reply but It was a message in the bottle because its time that I cannot resolve this prolem I cannot watch to some lessons I need Xubuntu 18.04 ALC662 ASROCK FM2A75M-DGS audio not workingAudio Problem wie folgend › Multimedia › Ubuntu verwenden › Forum › ubuntuusers.deI would appreciate any further help than ubuntu audio troubleshooting | | | | Audio Problem wie folgend › Multimedia › Ubuntu verwenden › Forum › ubun... | | | | | | | Xubuntu 18.04 ALC662 ASROCK FM2A75M-DGS audio not working I cannot hear any sound out of My mb asrock fm2a75m-dgs all sound port look unplugged even if music speaker 2 wa... | | | Il domenica 17 marzo 2019, 11:35:45 CET, Alex Murray ha scritto: Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 15 17:39:40 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio /dev/snd/seq: timidity 1238 F timidity Symptom_Jack: Blue Line In, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820319/+subscriptions -- 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/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND
[Touch-packages] [Bug 1689833] Re: OpenVPN server does not start properly on boot
Seems upstream kindly solved this bug, the solution is to: In /etc/default/openvpn AUTOSTART="none" In /etc/network/interfaces iface ethX inet static address XXX.XXX.XXX.XX netmask 255.255.255.0 openvpn my_vpn_name Where ethX is your interface (ex, eth0 for a regular interface, eth0:1 for an alias of an interface), my_vpn_name is the base filename without the .conf suffix of your /etc/openvpn/my_vpn_name.conf file. To explain, the above causes the script /etc/network/if-up.d/openvpn to get executed, this in turn executes systemctl --no-block start openvpn@my_vpn_name which starts the openvpn after the interface or alias is brought up. -- 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/1689833 Title: OpenVPN server does not start properly on boot Status in openvpn package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: OpenVPN intermittently fails to bind to local address during boot on Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does not. /var/log/openvpn.log Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:02 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address [AF_INET]192.168.4.254:1194: Cannot assign requested address Wed May 10 15:42:02 2017 Exiting due to fatal error In case it does not start, running 'sudo service openvpn start' fixes that problem. /var/log/openvpn.log Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:43 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 HWADDR=52:54:00:f0:26:0c Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100 Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500 Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 172.16.1.2 Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2 Wed May 10 15:42:43 2017 GID set to nogroup Wed May 10 15:42:43 2017 UID set to nobody Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194 Wed May 10 15:42:43 2017 UDPv4 link remote: [undef] Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256 Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0 Wed May 10 15:42:43 2017 IFCONFIG POOL LIST Wed May 10 15:42:43 2017 Initialization Sequence Completed My guess is that systemd starts OpenVPN too early before the network is brought up sufficiently. Running 'sudo systemctl edit --full openvpn' and adding 'Wants=network-online.target' does not change that behaviour. user@server:~$ sudo systemd-analyze critical-chain graphical.target @2.160s └─multi-user.target @2.159s └─ntp.service @2.054s +104ms └─remote-fs.target @2.052s └─remote-fs-pre.target @2.052s └─open-iscsi.service @1.993s +57ms └─iscsid.service @1.942s +47ms └─network-online.target @1.941s └─network.target @1.929s └─networking.service @1.793s +134ms └─apparmor.service @1.140s +395ms └─local-fs.target @1.140s └─local-fs-pre.target @1.139s └─lvm2-monitor.service @602ms +536ms └─lvm2-lvmetad.service @773ms └─systemd-journald.socket @574ms
[Touch-packages] [Bug 1689833] Re: OpenVPN server does not start properly on boot
Also affected by this bug, fresh Ubuntu Ubuntu 16.04.6 LTS minimal server install + openvpn /var/log/openvpn-.log: Sun Mar 17 14:45:59 2019 us=746742 TCP/UDP: Socket bind failed on local address [AF_INET]XXX.XXX.XXX.131:1094: Cannot assign requested address Sun Mar 17 14:45:59 2019 us=746750 Exiting due to fatal error Where XXX.XXX.XXX.131 is an IP aliased to eth0 (aliased eth0:1) in /etc/network/interfaces: auto eth0:1 allow-hotplug eth0:1 iface eth0:1 inet static address XXX.XXX.XXX.131 netmask 255.255.255.224 None of the workarounds listed in this bug or here https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ work - occurs 100% every boot. I can repeat this reliably on a fresh minimal install + openvpn + alias on primary interface -- 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/1689833 Title: OpenVPN server does not start properly on boot Status in openvpn package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: OpenVPN intermittently fails to bind to local address during boot on Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does not. /var/log/openvpn.log Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:02 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address [AF_INET]192.168.4.254:1194: Cannot assign requested address Wed May 10 15:42:02 2017 Exiting due to fatal error In case it does not start, running 'sudo service openvpn start' fixes that problem. /var/log/openvpn.log Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb 2 2016 Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key Wed May 10 15:42:43 2017 Control Channel Authentication: using './easy-rsa/keys/ta.key' as a OpenVPN static key file Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 HWADDR=52:54:00:f0:26:0c Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100 Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500 Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 172.16.1.2 Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2 Wed May 10 15:42:43 2017 GID set to nogroup Wed May 10 15:42:43 2017 UID set to nobody Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194 Wed May 10 15:42:43 2017 UDPv4 link remote: [undef] Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256 Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0 Wed May 10 15:42:43 2017 IFCONFIG POOL LIST Wed May 10 15:42:43 2017 Initialization Sequence Completed My guess is that systemd starts OpenVPN too early before the network is brought up sufficiently. Running 'sudo systemctl edit --full openvpn' and adding 'Wants=network-online.target' does not change that behaviour. user@server:~$ sudo systemd-analyze critical-chain graphical.target @2.160s └─multi-user.target @2.159s └─ntp.service @2.054s +104ms └─remote-fs.target @2.052s └─remote-fs-pre.target @2.052s └─open-iscsi.service @1.993s +57ms └─iscsid.service @1.942s +47ms └─network-online.target @1.941s └─network.target @1.929s └─networking.service @1.793s +134ms └─apparmor.service @1.140s +395ms └─local-fs.target @1.140s └─local-fs-pre.target @1.139s └─lvm2-monitor.service @602ms +536ms
[Touch-packages] [Bug 1820510] Re: Build errors against recent valac
Attached patch fixes build errors with valac 0.44 ** Patch added: "0001-Fix-build-errors-but-not-warnings-with-vala-044.patch" https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1820510/+attachment/5247025/+files/0001-Fix-build-errors-but-not-warnings-with-vala-044.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1820510 Title: Build errors against recent valac Status in libunity: New Status in libunity package in Ubuntu: New Bug description: I'd like to build Geary with support for Unity indicators in the Geary Flatpak package, but it's failing to build against recent valac: mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ vala --version Vala 0.44.0 mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ make make all-recursive make[1]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig' Making all in data make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' ITMRG com.canonical.Unity.Lenses.gschema.xml GEN com.canonical.Unity.Lenses.gschema.valid make[2]: Leaving directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' Making all in protocol make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/protocol' GEN libunity_protocol_private_la_vala.stamp Command-line option `--thread` is deprecated and will be ignored protocol-scope-discovery.vala:24.3-24.40: warning: the modifier `static' is not applicable to constants private static const string SCOPES_DIR = "unity/scopes"; ^^ protocol-scope-discovery.vala:190.5-190.43: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP = "Scope"; ^^^ protocol-scope-discovery.vala:191.5-191.45: warning: the modifier `static' is not applicable to constants private static const string DESKTOP_GROUP = "Desktop Entry"; ^ protocol-scope-discovery.vala:902.5-902.49: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP_GROUP = "Scope Group"; ^ protocol-preview-player.vala:41.3-41.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_NAME = "com.canonical.Unity.Lens.Music.PreviewPlayer"; protocol-preview-player.vala:42.3-42.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_PATH = "/com/canonical/Unity/Lens/Music/PreviewPlayer"; protocol-scope-interface.vala:117.3-117.51: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async ActivationReplyRaw activate ( ^ protocol-scope-interface.vala:124.3-124.57: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable search ( ^^^ protocol-scope-interface.vala:134.7-134.46: error: Synchronous out-parameters are not supported in async methods out HashTable out_hints, protocol-scope-interface.vala:130.3-130.43: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async string open_channel ( ^ protocol-scope-interface.vala:137.3-137.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void close_channel ( protocol-scope-interface.vala:142.3-142.63: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable push_results ( ^ protocol-scope-interface.vala:151.3-151.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void set_view_type (uint view_type) throws IOError; unity-scope-proxy-remote.vala:379.12-379.21: error: The name `channel_id' does not exist in the context of `Unity.Protocol.ScopeProxyRemote.open_channel' return channel_id; ^^ Compilation failed: 2 error(s), 12 warning(s)
[Touch-packages] [Bug 1820510] Re: Build errors against recent valac
Wrong package, apologies. ** Project changed: unity-api => libunity ** Also affects: libunity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1820510 Title: Build errors against recent valac Status in libunity: New Status in libunity package in Ubuntu: New Bug description: I'd like to build Geary with support for Unity indicators in the Geary Flatpak package, but it's failing to build against recent valac: mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ vala --version Vala 0.44.0 mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ make make all-recursive make[1]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig' Making all in data make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' ITMRG com.canonical.Unity.Lenses.gschema.xml GEN com.canonical.Unity.Lenses.gschema.valid make[2]: Leaving directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data' Making all in protocol make[2]: Entering directory '/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/protocol' GEN libunity_protocol_private_la_vala.stamp Command-line option `--thread` is deprecated and will be ignored protocol-scope-discovery.vala:24.3-24.40: warning: the modifier `static' is not applicable to constants private static const string SCOPES_DIR = "unity/scopes"; ^^ protocol-scope-discovery.vala:190.5-190.43: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP = "Scope"; ^^^ protocol-scope-discovery.vala:191.5-191.45: warning: the modifier `static' is not applicable to constants private static const string DESKTOP_GROUP = "Desktop Entry"; ^ protocol-scope-discovery.vala:902.5-902.49: warning: the modifier `static' is not applicable to constants private static const string SCOPE_GROUP_GROUP = "Scope Group"; ^ protocol-preview-player.vala:41.3-41.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_NAME = "com.canonical.Unity.Lens.Music.PreviewPlayer"; protocol-preview-player.vala:42.3-42.46: warning: the modifier `static' is not applicable to constants static const string PREVIEW_PLAYER_DBUS_PATH = "/com/canonical/Unity/Lens/Music/PreviewPlayer"; protocol-scope-interface.vala:117.3-117.51: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async ActivationReplyRaw activate ( ^ protocol-scope-interface.vala:124.3-124.57: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable search ( ^^^ protocol-scope-interface.vala:134.7-134.46: error: Synchronous out-parameters are not supported in async methods out HashTable out_hints, protocol-scope-interface.vala:130.3-130.43: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async string open_channel ( ^ protocol-scope-interface.vala:137.3-137.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void close_channel ( protocol-scope-interface.vala:142.3-142.63: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async HashTable push_results ( ^ protocol-scope-interface.vala:151.3-151.42: warning: DBus methods are recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError' public abstract async void set_view_type (uint view_type) throws IOError; unity-scope-proxy-remote.vala:379.12-379.21: error: The name `channel_id' does not exist in the context of `Unity.Protocol.ScopeProxyRemote.open_channel' return channel_id; ^^ Compilation failed: 2 error(s), 12 warning(s) make[2]: *** [Makefile:958: libunity_protocol_private_la_vala.stamp] Error 1 make[2]: Leaving directory
[Touch-packages] [Bug 1820509] [NEW] Avoid use-after-free in _XimProtoSetIMValues()
Public bug reported: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1820319 Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: even under xubuntu 16.04 my rear output did not work with headphones or Trust usb powered 2 way speaker even the front jack of my case does not work. the problem persist even if I have upgraded from 16.04 to 18.04 both lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio CurrentDesktop: XFCE Date: Fri Mar 15 17:39:40 2019 InstallationDate: Installed on 2016-09-07 (918 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: Audio interno - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hp 1709 F pulseaudio /dev/snd/controlC0: hp 1709 F pulseaudio /dev/snd/seq:timidity 1238 F timidity Symptom_Jack: Blue Line In, Rear Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.70 dmi.board.name: FM2A75M-DGS 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.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS: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. modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel model=auto mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** No longer affects: apt (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1820430] Re: failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop-amd64.iso
that's weird, the image build should've failed instead like it did for ubuntu anyway, the image should be fine now after this xorg (1:7.7+19ubuntu11) disco; urgency=medium * Drop mesa-vulkan-drivers from xserver-xorg Recommends, until vulkan- loader is in main. -- Timo Aaltonen Sat, 16 Mar 2019 00:16:43 +0200 ** Package changed: xorg (Ubuntu) => xubuntu-meta (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/1820430 Title: failed to install in latest 03-16-2019 disco-dingo xubuntu-desktop- amd64.iso Status in xubuntu-meta package in Ubuntu: New Bug description: install proceeded normally (manual partitioning) on reboot failed to start X session .. rebooted to grub selection screen chose rescue mode .. from the choices menu ran some checks then did updates install .. all of the xorg-server files were installed automaticly .. then selected the "boot resume " (not sure on wording) which then allowed normal login to proceed (lightdm) into xfce/xubuntu evironment.. seems the xorg packages were not installed initially .. this appears to be a recent "change" as earlier images did install these files normally.. early march?, but February and earlier for sure.. this is a older machine lenovo SL500 with Intel GM45 Express Chipset video .. This machine runs dicso fine normally .. has been running disco since first CD install images were available .. daily updates from proposed .. but has only run xorg-server .. not sure if chipset is wayland capable.. Description: Ubuntu Disco Dingo (development branch) Release: 19.04 march 16, 2019 daily iso tested earlier feb 8 and 15 iso's were ok ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Mar 16 17:42:14 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-16 (0 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=119a6b43-9936-4b5d-ab5b-814f531ed9b7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1820430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
