[Touch-packages] [Bug 1855402] [NEW] [TGL] mesa support
Public bug reported: Description: this feature tracks the updates of mesa 3d for TGL support. We will update the commitid list as necessary Target Release: 20.10 Target version: TBD ** Affects: intel Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: intel-upkg-20.10 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1855402 Title: [TGL] mesa support Status in intel: New Status in mesa package in Ubuntu: New Bug description: Description: this feature tracks the updates of mesa 3d for TGL support. We will update the commitid list as necessary Target Release: 20.10 Target version: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853374] Re: pulseaudio disables GP107GL output every so often
** Tags added: eoan -- 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/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853266] Re: xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl
[775834.395] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage [775834.395] (WW) glamor: Failed to allocate 5x5 FBO due to GL_OUT_OF_MEMORY. [775834.395] (WW) glamor: Expect reduced performance. [776320.877] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage [776320.877] (EE) [776320.877] (EE) Backtrace: [776320.878] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55fb3d66d889] [776320.878] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f1c7b03ef8f] [776320.878] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so (glamor_get_pixmap_texture+0x7d) [0x7f1c7a61947d] [776320.879] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7bc8) [0x7f1c7a62bb28] [776320.879] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7fc8) [0x7f1c7a62c298] [776320.879] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x860e) [0x7f1c7a62ca6e] [776320.879] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0xa656) [0x7f1c7a630766] [776320.879] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) [0x55fb3d5efaef] [776320.879] (EE) 8: /usr/lib/xorg/Xorg (AddTraps+0x3440) [0x55fb3d5e6950] [776320.879] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) [0x55fb3d50e9fe] [776320.879] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55fb3d5129c6] [776320.880] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f1c7ae64b6b] [776320.880] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2a) [0x55fb3d4fc67a] [776320.880] (EE) [776320.880] (EE) Segmentation fault at address 0x0 [776320.880] (EE) Fatal server error: [776320.880] (EE) Caught signal 11 (Segmentation fault). Server aborting ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: disco ** Bug watch added: Red Hat Bugzilla #1648475 https://bugzilla.redhat.com/show_bug.cgi?id=1648475 ** Also affects: xorg-server (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1648475 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #647 https://gitlab.freedesktop.org/xorg/xserver/issues/647 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/647 Importance: Unknown Status: Unknown -- 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/1853266 Title: xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: New Status in xorg-server package in Fedora: Unknown Bug description: Recently, my the xserver on my system has started randomly crashing due to a segmentation fault. As far as I can tell, this segmentation fault occurs as a result of libglamoregl encountering a GL_OUT_OF_MEMORY error (see attached Xorg.log). I have had a hard time reproducing this bug reliably, but it mostly happens when I have been using Inkscape for a while. This appears to be the same bug that has been reported here https://bugs.freedesktop.org/show_bug.cgi?id=110500 https://bugs.freedesktop.org/show_bug.cgi?id=110714 In those bug reports, the usual recommendation is to switch from the -modesetting video driver to the -nouveau video driver. By default, Ubuntu is not configured in this way, so this bug probably needs to be addressed in some other way. My graphics card is listed as follows: *-display description: VGA compatible controller product: GK208B [GeForce GT 710] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:69 memory:d700-d7ff memory:c800-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 Please let me know if you need any additional information. More information: Release of Ubuntu: 19.04 Installed package versions: xserver-xorg-video-nouveau/disco,now 1:1.0.16-1 amd64 [installed] xserver-xorg-core/disco,now 2:1.20.4-1ubuntu3 amd64 [installed] xserver-xorg/disco,now 1:7.7+19ubuntu12 amd64 [installed] inkscape/disco,now 0.92.4-3 amd64 [installed] To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1853266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853221] Re: Two monitors displaying same image
Your Xorg logs are showing: [ 4864.686] (WW) modeset(0): hotplug event: connector 93's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... where connector 93 is the DisplayPort. Please try a different monitor cable, or just replugging it. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1853221 Title: Two monitors displaying same image Status in xorg-server package in Ubuntu: Invalid Bug description: I am using two monitors, they both are displaying the same image. In settings, only one monitor is recognized (technically they have the same name, though). I have tried to go into arandr to see what I could do but only one monitor is recognized there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:40:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:075b] InstallationDate: Installed on 2019-11-02 (18 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. XPS 13 9360 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-32-generic root=UUID=db637f82-b923-4a94-b32e-7c89cdc41956 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1853221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808476] Autopkgtest regression report (python2.7/2.7.17-1~18.04)
All autopkgtests for the newly accepted python2.7 (2.7.17-1~18.04) for bionic have finished running. The following regressions have been reported in tests triggered by the package: pdal/unknown (armhf) mercurial/4.5.3-1ubuntu2.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#python2.7 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1808476 Title: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Bionic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python2.7 source package in Disco: Fix Released Bug description: [Impact] $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. [Test Case] Make sure the libssl1.1 build-dependency of python2.7 is at least 1.1.1. [Regression Potential] Potentially none, besides the usual regression potential of new rebuilds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. A duplicate -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It takes few login attempts to actually login back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It takes few login attempts to actually login back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Autopkgtest regression report (python2.7/2.7.17-1~18.04)
All autopkgtests for the newly accepted python2.7 (2.7.17-1~18.04) for bionic have finished running. The following regressions have been reported in tests triggered by the package: pdal/unknown (armhf) mercurial/4.5.3-1ubuntu2.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#python2.7 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Committed Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852922] Re: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285
** Tags added: eoan -- 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/1852922 Title: Internal microphone not being detected - Ubuntu 19.10, Kernel 5.3, Laptop HP Envy 13, Realtek ALC285 Status in alsa-driver package in Ubuntu: New Bug description: I have just installed Ubuntu 19.10 with Kernel 5.3 on my HP Envy 13. Everything works just fine except the microphone which is not being detected at all. My alsa-info output: http://alsa- project.org/db/?f=1d22f0563bc25ea1ebe609a8482e5f39081abdc2 System info: Description: Ubuntu 19.10 Release: 19.10 Alsa version: alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://pl.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852922/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853120] Re: Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
** Summary changed:
- Xorg crashes with a bus error in OsLookupColor when using a second display
+ Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
** 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/1853120
Title:
Xorg crashes with SIGBUS in drmmode_load_cursor_argb_check
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/af88d9cd45acf4632e47789e4661be6a47b4dbf1
---
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
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/xorg-server/+bug/1853120/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852863] Re: Don't know
Sounds like you're not getting a login screen, is that right? It wouldn't be surprising given it's a rare and not well tested: Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz Please try editing /etc/gdm3/custom.conf and uncomment: #WaylandEnable=false then reboot. ** Package changed: xorg (Ubuntu) => mutter (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/1852863 Title: Don't know Status in mutter package in Ubuntu: Incomplete Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852752] Re: DPMS does not switch off the monitor back light
Since Xorg is using the modeset driver here I think this might be an issue with the Raspberry Pi kernel driver(s) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - DPMS does not switch off the monitor back light + DPMS does not switch off the monitor back light on Raspberry Pi 4 ** Also affects: linux (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/1852752 Title: DPMS does not switch off the monitor back light on Raspberry Pi 4 Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: 'xset dpms force off' blanks the screen but does not switch off the HDMI (LCD) monitor backlight. 'xset -q' shows DPMS is enabled. 'tvservice -o' does switch off the monitor. No warnings/errors related to dpms in /var/log/XOrg.0.log Not sure if this is a xorg, kernel, libxcb-dpms0 or other issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1012.14-raspi2 5.3.7 Uname: Linux 5.3.0-1012-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Nov 15 18:33:52 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:17:19:0B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/linux/+bug/1852752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')
Hey Guys, this bug still effects me on Ubuntu 18.04.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1383470 Title: scp does not work (fails at 'Sending command scp -v -t') Status in openssh package in Ubuntu: Expired Bug description: Following the last update of Ubuntu 14.02, scp (in the default system) has ceased working. It hangs after authentication at the point where it wold start an interactive session. I've verified that the problem is in my system: scp still works at the target machine and scp won't work on my machine to various hosts. Output below. rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org: Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), command scp -v -t . OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/rasmith/.ssh/config debug1: /home/rasmith/.ssh/config line 17: Applying options for * debug1: /home/rasmith/.ssh/config line 20: Deprecated option "rhostsauthentication" debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh" debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh" debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to apacentral.org [65.19.130.61] port 22. debug1: Connection established. debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: identity file /home/rasmith/.ssh/identity type 0 debug1: identity file /home/rasmith/.ssh/identity-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4_hpn13v11 FreeBSD-2013 debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 0x0400 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae debug1: Host 'apacentral.org' is known and matches the RSA host key. debug1: Found key in /home/rasmith/.ssh/known_hosts:26 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: rasm...@aristotle.tamu.edu debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to apacentral.org ([65.19.130.61]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t . (at this point, the command hangs more or less indefinitely until killed with Ctrl-C) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 20 15:25:14 2014 InstallationDate: Installed on 2012-10-18 (732 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2014-05-02 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1383470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1855380] Re: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK)
** Summary changed: - Touchpad not working + Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- 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/1855380 Title: Dell Inspiron 3558 touchpad stopped working in kernel 4.15.0-72 (but 4.15.0-70 is OK) Status in linux package in Ubuntu: Confirmed Bug description: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855380] [NEW] Touchpad not working
Public bug reported: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "Info about devices xinput evtest and Xorg.log" https://bugs.launchpad.net/bugs/1855380/+attachment/5310123/+files/devicesxinputEvtestXorg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1855380 Title: Touchpad not working Status in xorg package in Ubuntu: New Bug description: The touchpad is not detected by my Dell Inspiron 3000 series laptop, this happened after my kernel was updated from 4.15.0-70 to 4.15.0-72. If I enter Ubuntu Advanced Options to my previous kernel (4.15.0-70) my touchpad works correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 5 21:54:06 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:06b0] InstallationDate: Installed on 2019-07-01 (158 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ipv6.disable vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0XNXCC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0XNXCC:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1852170] Re: Severe screen corruption
*** This bug is a duplicate of bug 1848741 *** https://bugs.launchpad.net/bugs/1848741 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 1848741, 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. ** Tags added: amdgpu ** Summary changed: - Severe screen corruption + [amdgpu] Severe screen corruption ** This bug has been marked a duplicate of bug 1848741 [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) -- 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/1852170 Title: [amdgpu] Severe screen corruption Status in xorg package in Ubuntu: New Bug description: Screen occasionally shows strange distortions and corruptions during almost any activity. Static or bars of colour appear in unusual places along the screen. Corruptions are often (though not always) removed in some sections of the screen by the appearance of other display elements (windows, tooltip, mouse-over, etc.) Description: Ubuntu 19.10 Release: 19.10 xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 16:13:38 2019 DistUpgraded: 2019-11-07 18:03:17,611 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: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [17aa:506f] InstallationDate: Installed on 2018-09-07 (430 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KUCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro radeon.modeset=0 ivrs_ioapic[32]=00:14.0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-07 (4 days ago) dmi.bios.date: 07/16/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET47W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KUCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0UET47W(1.27):bd07/16/2018:svnLENOVO:pn20KUCTO1WW:pvrThinkPadE485:rvnLENOVO:rn20KUCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E485 dmi.product.name: 20KUCTO1WW dmi.product.sku: LENOVO_MT_20KU_BU_Think_FM_ThinkPad E485 dmi.product.version: ThinkPad E485 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/xorg/+bug/1852170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852194] Re: The mouse does not work smoothly (shakes when moving, works with ping)
Please run these commands on the affected machine: dmesg > dmesg.txt lspci > lspci.txt lsusb > lsusb.txt And then attach all three resulting files to this bug. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Summary changed: - The mouse does not work smoothly (shakes when moving, works with ping) + The bluetooth mouse does not work smoothly (shakes when moving and is delayed) -- 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/1852194 Title: The bluetooth mouse does not work smoothly (shakes when moving and is delayed) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After the upgrade is installed, the bluetooth does not work smoothly (shakes when moving, works with ping) 1) Ubuntu 18.04.3 LTS 2) --- 3) The bluetooth mouse should work as smoothly as before update system 4) The bluetooth mouse doesn't work smoothly (shakes when moving, works with ping) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-26 (258 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Tags: bionic dist-upgrade Uname: Linux 5.0.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom contraxsuite_docker_user dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852166] Re: Pixel pattern error in over
Sorry I can't see a problem in that screenshot. Can you provide more? ** Tags added: nouveai ** Tags removed: nouveai ** Tags added: nouveau ** Summary changed: - Pixel pattern error in over + [nouveau] Pixel pattern error in over ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - [nouveau] Pixel pattern error in over + [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works -- 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/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works Status in gnome-shell package in Ubuntu: Incomplete Bug description: The primary monitor, Microstep 24", is capable of 144 Hz refresh rate and I do use that regularly in Windows 10. When I set the rate to anything higher than 60 Hz (120 or 144) I get a wrong pixel pattern. See attached photos. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:06:45 2019 DistUpgraded: 2019-10-23 22:37:24,432 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6390] InstallationDate: Installed on 2010-10-12 (3317 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (19 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun May 13 18:05:25 2018 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::03:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852117] Re: non appare nessuna applicazione
** Package changed: xorg (Ubuntu) => 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/1852117 Title: non appare nessuna applicazione Status in Ubuntu: Incomplete Bug description: cliccando sul simbolo di ubuntu non appare nessuna applicazione neanche digitando il nome ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Nov 11 19:32:52 2019 DistUpgraded: 2019-11-11 06:32:02,732 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio «./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8)) DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:8023] InstallationDate: Installed on 2016-04-29 (1291 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Hewlett-Packard HP Stream Notebook PC 11 ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-21-generic root=UUID=e1727860-ed33-4311-9c36-c63aa9894bb6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-11-11 (0 days ago) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8023 dmi.board.vendor: Hewlett-Packard dmi.board.version: 54.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.07:bd11/28/2014:svnHewlett-Packard:pnHPStreamNotebookPC11:pvrType1-ProductConfigId:rvnHewlett-Packard:rn8023:rvr54.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Stream Notebook PC 11 dmi.product.sku: L0N58EA#ABZ dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Nov 11 19:22:49 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1852117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852158] Re: Xorg black screen on resume, and VT switch crashes with "EnterVT failed for screen 0"
*** This bug is a duplicate of bug 1421808 ***
https://bugs.launchpad.net/bugs/1421808
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 1421808 / bug 1787332 / bug 1787338, 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 1421808
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
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/1852158
Title:
Xorg black screen on resume, and VT switch crashes with "EnterVT
failed for screen 0"
Status in xorg package in Ubuntu:
New
Bug description:
Every now and then, maybe one time out of 8, resuming from suspend
gives me a black screen, no X.
If I try ctrl-alt-F7, I see a VT with a _ on it, no X or login prompt.
If I try ctrl-alt-F1, F2, F2 or F4, X crashes, every time.
I've collected X logs from the last two times this has happened; both times,
there's a message near the end:
EnterVT failed for screen 0
I found a similar but not identical upstream bug: that might be related:
https://bugs.freedesktop.org/show_bug.cgi?id=109668
There's also a Redhat bug that looks related and might have helpful info:
https://bugzilla.redhat.com/show_bug.cgi?id=1662057
Machine is a Levono Carbon X1 with Intel graphics (hopefully ubuntu-
bug attached the relevant info).
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
Date: Mon Nov 11 19:51:13 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02)
(prog-if 00 [VGA controller])
Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
InstallationDate: Installed on 2019-10-10 (32 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
MachineType: LENOVO 20QDCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET30W (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
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/xorg/+bug/1852158/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852126] Re: [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound through headphones
** Summary changed: - [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound at all + [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound through headphones -- 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/1852126 Title: [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound through headphones Status in alsa-driver package in Ubuntu: New Bug description: i can listen normally but when i try to use the headphone the sound is gone ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aoplnx 1465 F pulseaudio /dev/snd/controlC0: aoplnx 1465 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 15:04:02 2019 InstallationDate: Installed on 2019-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1012 F pulseaudio aoplnx 1465 F pulseaudio /dev/snd/controlC0: gdm1012 F pulseaudio aoplnx 1465 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Aspire A315-21, Realtek ALC255, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Squirtle_SR dmi.board.vendor: SR dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd06/19/2018:svnAcer:pnAspireA315-21:pvrV1.12:rvnSR:rnSquirtle_SR:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Aspire 3 dmi.product.name: Aspire A315-21 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
** Package changed: xorg (Ubuntu) => linux (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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: New Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852083] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement
** Package changed: xorg (Ubuntu) => linux (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/1852083 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement Status in linux package in Ubuntu: Fix Released Bug description: 1. Pair Logitech MX Master 3 bluetooth mouse with Ubuntu 18.04.3 LTS (don't use Logitech bluetooth dongle, use built in laptop bluetooth) 2. Move cursor. Cursor movement is choppy, laggy, like it's having 20 FPS refresh rate. Workaround: execute in terminal: `sudo hcitool lecup --handle 3585 --latency 0 --min 6 --max 8` This command must be used every time the mouse is connected to the laptop (after turning on the laptop, after some time of mouse inactivity etc.). When using Logitech bluetooth dongle this problem never occurs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 14:35:49 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: Cannot open /sys/bus/pci/devices/:05:02.0/resource: No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697281] Re: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all
** Tags added: eoan -- 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/1697281 Title: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 1629 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Sun Jun 11 11:37:01 2017 InstallationDate: Installed on 2015-10-24 (596 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 1629 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to xenial on 2017-05-20 (22 days ago) dmi.bios.date: 3/6/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd3/6/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: TOSHIBA NB515 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1697281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852025] Re: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem
*** This bug is a duplicate of bug 1697281 *** https://bugs.launchpad.net/bugs/1697281 ** This bug has been marked a duplicate of bug 1697281 [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] 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/1852025 Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem Status in alsa-driver package in Ubuntu: New Bug description: Everytime I boot there is no sound. With QasMixer I am able to fix it by selecting hw:0 (HDA Intel) and increasing the second slider from bottom to top, that slider says "auriculares" in spanish which is "headphones". I am not using headphones though and I didn't found any other way of increasing that slider in the standard programs that come installed by default in Ubuntu 19.10 (and many other older releases). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luigi 1637 F pulseaudio luigi 26280 F qasmixer /dev/snd/pcmC0D0p: luigi 1637 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:38:04 2019 InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio Interno - HDA Intel Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: nov 10 17:18:45 luigi-netbook dbus-daemon[887]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=122 pid=1140 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") nov 10 19:17:05 luigi-netbook pulseaudio[1140]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Symptom_Type: Volume slider, or mixer problems Title: [TOSHIBA NB515, Realtek ALC269VB, Speaker, Internal] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852025/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697281] Re: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1697281 Title: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 1629 F pulseaudio CurrentDesktop: GNOME-Flashback:Unity Date: Sun Jun 11 11:37:01 2017 InstallationDate: Installed on 2015-10-24 (596 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Audio Interno - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel 1629 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [TOSHIBA NB515, Intel CedarTrail HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: Upgraded to xenial on 2017-05-20 (22 days ago) dmi.bios.date: 3/6/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd3/6/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: TOSHIBA NB515 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1697281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852023] Re: Wayland doesn't work in GMA500
Although you are complete right about "I guess an udev rule to disable Wayland for GMA500 is all that is needed." -- 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/1852023 Title: Wayland doesn't work in GMA500 Status in mutter package in Ubuntu: Triaged Bug description: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA TOSHIBA NB515 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jul 1 17:43:10 2019 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852023] Re: Wayland doesn't work in GMA500
Although you are completely right about "I guess an udev rule to disable Wayland for GMA500 is all that is needed." ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => 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/1852023 Title: Wayland doesn't work in GMA500 Status in mutter package in Ubuntu: Triaged Bug description: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA TOSHIBA NB515 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jul 1 17:43:10 2019 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852023] Re: Wayland doesn't work in GMA500
It appears GMA500 is the infamous Poulsbo with PowerVR GPU: https://en.wikipedia.org/wiki/Intel_GMA#GMA_500 This means it is closed source and we can't support it :( -- 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/1852023 Title: Wayland doesn't work in GMA500 Status in mutter package in Ubuntu: Triaged Bug description: I had to disable Wayland in GDM3 in order to be able to login. I guess an udev rule to disable Wayland for GMA500 is all that is needed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 19:14:19 2019 DistUpgraded: 2019-11-10 16:17:45,811 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller [8086:0be1] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Atom Processor D2xxx/N2xxx Integrated Graphics Controller [1179:fc10] InstallationDate: Installed on 2012-07-29 (2660 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA TOSHIBA NB515 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=5febd6a0-8053-4b1c-92f5-df934f0ea50b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-10 (0 days ago) dmi.bios.date: 4/3/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd4/3/2012:svnTOSHIBA:pnTOSHIBANB515:pvrPLL72P-013LM1:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Dolphin10 dmi.product.name: TOSHIBA NB515 dmi.product.sku: PLL72P-013LM1 dmi.product.version: PLL72P-013LM1 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jul 1 17:43:10 2019 xserver.configfile: default xserver.errors: modeset(0): glamor initialization failed AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash
I think the more relevant thing to investigate here is the GUI used to empty the trash... Are you doing it via the desktop icon or via a Nautilus "Files" window? Probably both gnome-shell and nautilus are pulseaudio clients one way or the other. ** Tags added: eoan ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1852018 Title: Audio Stops Playing Briefly When Emptying Trash Status in pulseaudio package in Ubuntu: Incomplete Bug description: I am running Ubuntu 19.10 and encountered this issue. I had a podcast playing in the background on Firefox v. 70.0.1 and I was deleting some files. I then proceeded to empty the trash and saw that the audio stops briefly till the "Empty all items from Trash?" prompt shows up. I was able to duplicate this many times and it even occurred with audio on Chrome. The expected way for things to work would be the audio keeps on playing, if I just empty the trash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1852018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853956] Re: 34 wireguard peers result in invalid peer configuration
It turns out the fix for this issue was backported to systemd v240: https://github.com/systemd/systemd-stable/pull/37 I performed a release upgrade on one of our affected servers, bringing it up from ubuntu 18.04 to ubuntu 19.04 (which uses systemd v240), and I can confirm that the peers are being configured correctly now. So this issue affects ubuntu 18.04 LTS but not any later supported releases. 18.10 was also affected but it's EOL. -- 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/1853956 Title: 34 wireguard peers result in invalid peer configuration Status in systemd package in Ubuntu: New Bug description: ubuntu server 18.04.3 LTS systemd 237-3ubuntu10.31 wireguard 0.0.20191012-wg1~bionic from PPA. We're using systemd-networkd to configure wireguard via wireguard.netdev and wireguard.network files in /etc/systemd/network/. All endpoints have IPv4 addresses. When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev file some peers are configured incorrectly. The affected peers seem to be related to the total number of peers (counting from 0 here): 33 peers: No issue 34 peers: Peer 1 and 2 fail 35 peers: Peer 2 and 3 fail 36 peers: Peer 3 and 4 fail 37 peers: No issue In all cases peer 0 is functional. For an affected pair of peers A and B, peer A ends up with the allowed IP address range of peer B. Peer B ends up with no allowed IP addresses. This can be seen in the output of wg. The connections to both peers fail because of incorrect address range assignments. We first encountered this issue in a production environment when we moved from 33 to 34 unique peers on each server. The issue was reproduced on 3 different physical servers with similar configuration by adding and removing peer 34. The [WireGuardPeer] entries do not need to be unique to reproduce the issue. In my testing I used 6 distinct peers and then used 28 or more identical copies of a 7th peer. The results were the same. In January 2019 a bug was reported that was also related to the number of wireguard peers, but the description seems sufficiently different from our case that I felt I should file a distinct bug report. Here's a link to that report in case I'm wrong about that: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467595] Re: cursor sometimes disappears on XPS 13 9343 and external monitor
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: unity (Ubuntu) Status: Incomplete => Won't Fix -- 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/1467595 Title: cursor sometimes disappears on XPS 13 9343 and external monitor Status in Dell Sputnik: New Status in Unity: Confirmed Status in unity package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor disappears (sometimes after screen lock, other times just normal usage). I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:19:40 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1467595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
I can also confirm that on another laptop that I upgraded from Ubuntu 18.04 -> 18.10 -> 19.04 -> 19.10 with the following versions that the username was stored (at some point) successfully, and I do not need to enter it when joining the vpn. network-manager-openconnect: Installed: 1.2.4-2ubuntu network-manager-openconnect: Installed: 1.2.4-2ubuntu Note these are same versions as installed on the laptop that has the bug. That laptop was never upgraded but had Ubuntu 19.10 installed fresh prior to installing the nm packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853412] Re: Xorg freeze
Please avoid reporting multiple issues in a single bug. The tearing issue is bug 1846398 already so the remaining issues are "Ubuntu operates slow with system apps and 3rd party apps; system hangs and crashes; and more". Are you saying Ubuntu is only slow when you are using fractional scaling? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Poor performance with fractional scaling factors in Xorg ** Package changed: ubuntu => mutter (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/1853412 Title: Poor performance with fractional scaling factors in Xorg Status in mutter package in Ubuntu: Incomplete Bug description: This happens when I use fractional scaling. At 100%, my HP 840 G3 runs smooth and fast. With fractional scaling at 125%, there is the following: visual tears when moving videos while playing; Ubuntu operates slow with system apps and 3rd party apps; system hangs and crashes; and more. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 01:03:54 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079] InstallationDate: Installed on 2019-08-22 (90 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: HP HP EliteBook 840 G3 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-32-generic root=UUID=63069e05-3459-49f5-9de1-e6594c7cce44 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.13 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.74 dmi.chassis.asset.tag: 5CG7065GM1 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.74:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: V1H24UT#ABA dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/mutter/+bug/1853412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852001] Re: GUI freeze on high disk or CPU load, but disabling swap fixes it
Which GUI are you using that exhibits the problem? ** Summary changed: - Xorg freeze on high disk or cpu load or random + GUI freeze on high disk or CPU load, but disabling swap fixes it ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - GUI freeze on high disk or CPU load, but disabling swap fixes it + GUI freeze on high disk IO, but disabling swap fixes it -- 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/1852001 Title: GUI freeze on high disk IO, but disabling swap fixes it Status in linux package in Ubuntu: Incomplete Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
[Touch-packages] [Bug 1854981] Autopkgtest regression report (lvm2/2.02.176-4.1ubuntu3.18.04.2)
All autopkgtests for the newly accepted lvm2 (2.02.176-4.1ubuntu3.18.04.2) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
ganeti/2.16.0~rc2-1build1 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#lvm2
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Committed
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Committed
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE
[Touch-packages] [Bug 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only)
Thanks. I've now added this bug to the performance tracking list: https://trello.com/c/pe5mRmx7 ** Summary changed: - gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen + gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only) ** Tags added: wayland wayland-session ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen (on Wayland only) Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This started to happen with Ubuntu 19.10. When an animated gif is displayed in a browser, gnome-shell begins using 100% CPU on all cores. To reproduce: 1) open Firefox, or Chromium 2) load an URL where an animated gif is displayed - you can also use this direct link to https://i.stack.imgur.com/h6viz.gif 3) gnome-shell will start using 100% CPU on all cores (as long as Firefox/Chromium window is in the foreground) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 GsettingsChanges: InstallationDate: Installed on 2019-05-12 (172 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Autopkgtest regression report (python-stdlib-extensions/2.7.17-1~18.04)
All autopkgtests for the newly accepted python-stdlib-extensions (2.7.17-1~18.04) for bionic have finished running. The following regressions have been reported in tests triggered by the package: pyfai/0.15.0+dfsg1-1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#python-stdlib-extensions [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Committed Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Autopkgtest regression report (lvm2/2.02.176-4.1ubuntu4.2)
All autopkgtests for the newly accepted lvm2 (2.02.176-4.1ubuntu4.2) for disco
have finished running.
The following regressions have been reported in tests triggered by the package:
writeboost/unknown (armhf)
udisks2/unknown (armhf)
cinder/2:14.0.1-0ubuntu1 (i386, ppc64el, s390x, amd64, arm64, armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#lvm2
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Committed
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Committed
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS
[Touch-packages] [Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones
This bug was fixed in the package apport - 2.20.11-0ubuntu13 --- apport (2.20.11-0ubuntu13) focal; urgency=medium [ Brian Murray ] * Create additional symlinks to the source_linux.py apport package hook for many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967) [ Michael Hudson-Doyle ] * Fix autopkgtest failures since recent security update: (LP: #1854237) - Fix regression in creating report for crashing setuid process by getting kernel to tell us the executable path rather than reading /proc/[pid]/exe. - Fix deletion of partially written core files. - Fix test_get_logind_session to use new API. - Restore add_proc_info raising ValueError for a dead process. - Delete test_lock_symlink, no longer applicable now that the lock is created in a directory only root can write to. -- Michael Hudson-Doyle Fri, 06 Dec 2019 08:57:09 +1300 ** Changed in: apport (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes
This bug was fixed in the package apport - 2.20.11-0ubuntu13 --- apport (2.20.11-0ubuntu13) focal; urgency=medium [ Brian Murray ] * Create additional symlinks to the source_linux.py apport package hook for many OEM kernels. Thanks to You-Sheng Yang for the patch. (LP: #1847967) [ Michael Hudson-Doyle ] * Fix autopkgtest failures since recent security update: (LP: #1854237) - Fix regression in creating report for crashing setuid process by getting kernel to tell us the executable path rather than reading /proc/[pid]/exe. - Fix deletion of partially written core files. - Fix test_get_logind_session to use new API. - Restore add_proc_info raising ValueError for a dead process. - Delete test_lock_symlink, no longer applicable now that the lock is created in a directory only root can write to. -- Michael Hudson-Doyle Fri, 06 Dec 2019 08:57:09 +1300 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: New Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
This bug was fixed in the package base-files - 11ubuntu2 --- base-files (11ubuntu2) focal; urgency=medium * motd/50-motd-news: Don't show error when /var/cache/motd-news is missing and runnig as regular user (LP: #1855271) -- Balint Reczey Thu, 05 Dec 2019 15:39:21 +0100 ** Changed in: base-files (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a nomal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxc/issues/3198#issuecomment-562252884 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376322] Re: telepathy-mission-control is spamming dbus.log with error messages
** Changed in: mission-control-5 Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues #82 https://gitlab.freedesktop.org/telepathy/telepathy-mission-control/issues/82 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1376322 Title: telepathy-mission-control is spamming dbus.log with error messages Status in Telepathy Mission Control 5: Unknown Status in telepathy-mission-control-5 package in Ubuntu: Triaged Bug description: I was trying to figure out where excessive file system writes were coming from (to try to reduce flash writes and hence reduce power consumption) and I spotted that the dbus log on my phone is being hit by messages from process 2046: root@ubuntu-phablet:~# ps -ef | grep 2046 phablet 2046 1741 0 14:43 ?00:00:00 /usr/lib/telepathy/mission-control-5 root@ubuntu-phablet:~# tail -f /home/phablet/.cache/upstart/dbus.log (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' ..at a rate of ~15K an hour or so. This is causing unnecessary writes to the log, filling up file system space and these kind of writes to a flash file system do cost a small amount of power. Seems that there is an error somewhere, else dbus would not be logging it. To manage notifications about this bug go to: https://bugs.launchpad.net/mission-control-5/+bug/1376322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376322]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-mission- control/issues/82. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1376322 Title: telepathy-mission-control is spamming dbus.log with error messages Status in Telepathy Mission Control 5: Unknown Status in telepathy-mission-control-5 package in Ubuntu: Triaged Bug description: I was trying to figure out where excessive file system writes were coming from (to try to reduce flash writes and hence reduce power consumption) and I spotted that the dbus log on my phone is being hit by messages from process 2046: root@ubuntu-phablet:~# ps -ef | grep 2046 phablet 2046 1741 0 14:43 ?00:00:00 /usr/lib/telepathy/mission-control-5 root@ubuntu-phablet:~# tail -f /home/phablet/.cache/upstart/dbus.log (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' (process:2046): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.41.3/./gobject/gsignal.c:3101: signal id '33' is invalid for instance '0x10af8d8' ..at a rate of ~15K an hour or so. This is causing unnecessary writes to the log, filling up file system space and these kind of writes to a flash file system do cost a small amount of power. Seems that there is an error somewhere, else dbus would not be logging it. To manage notifications about this bug go to: https://bugs.launchpad.net/mission-control-5/+bug/1376322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted python-stdlib-extensions into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /python-stdlib-extensions/2.7.17-1~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Committed Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808476] Re: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants
Hello Dimitri, or anyone else affected, Accepted python2.7 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.17-1~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python2.7 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1808476 Title: Please bump libssl1.1 dependency to at least >= 1.1.1, as headers leak constants Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 source package in Bionic: Fix Committed Status in python2.7 source package in Cosmic: Fix Released Status in python2.7 source package in Disco: Fix Released Bug description: [Impact] $ python -c 'import ssl; print(ssl.OP_NO_TLSv1_3)' Prints 0, for python2.7 built against 1.1.0 headers, yet prints 536870912 when built against 1.1.1 irrespective of the runtime libssl1.1 library version. This may yield confusion, especially since ssl.OPENSSL_VERSION reports runtime libssl version, not the version of the libssl headers. Such that, e.g. it looks like ssl module is running against 1.1.1, has OP_NO_TLSv1_3 option, yet cannot actually use it to disable TLSv1.3. Also vice versa, python2.7 build against 1.1.1 can be installed with 1.1.0 runtime library, and thus OP_NO_TLSv1_3 might be set, which is not understood by the runtime library. In libpython2.7-stdlib, please bump libssl1.1 version dep to "libssl1.1 (>= 1.1.1)" when building against libssl-dev >= 1.1.1. python3.x are not affected, as they started to exploit 1.1.1-only symbols/features, and thus already have an automatic dep on >= 1.1.1. [Test Case] Make sure the libssl1.1 build-dependency of python2.7 is at least 1.1.1. [Regression Potential] Potentially none, besides the usual regression potential of new rebuilds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1808476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
Hello Matthias, or anyone else affected, Accepted python2.7 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.17-1~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python2.7 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic ** Changed in: python-stdlib-extensions (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Committed Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
I confirm the bug on 19.10 for DDS files ( from a mod for HOI4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
I confirm the bug with DDS files (for an HOI4 mod) in 19.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
Hello Matthias, or anyone else affected, Accepted python-stdlib-extensions into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /python-stdlib-extensions/2.7.17-1~19.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python-stdlib-extensions (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python-stdlib-extensions source package in Eoan: Fix Committed Status in python2.7 source package in Eoan: Fix Committed Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Description changed:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate LVM
volume will not be activate either, but since they don't need to be
mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
- One downside, user will see this fixed, will still experience the
- situation in standard ISO, since I'm afraid there is no more point
- release for Bionic and Disco.
+ One downside, for users who will see this fixed, will still experience
+ the situation in standard ISO, since I'm afraid there is no more point
+ release for Disco. (it is not recommended to do new disco installs
+ anyway since it's going EOL shortly) One would need to rely on the
+ mini.iso for fetching the latest lvm2 package in the archive.
- So one would need to rely on the mini.iso for fetching the latest lvm2
- package in the archive.
+ IIRC Bionic will have a new point release somewhere in Feb 2020 but
+ until then one would need to rely on the mini.iso for fetching the
+ latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub parameter
that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
283 log_end_msg
284
=> 285 if read_fstab_entry /usr; then
=> 286 log_begin_msg "Mounting /usr file system"
=> 287 mountfs /usr
=> 288 log_end_msg
=> 289 fi
In this case, /usr is present in
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
Hello Matthias, or anyone else affected, Accepted python2.7 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python2.7/2.7.17-1~19.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python2.7 (Ubuntu Eoan) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python-stdlib-extensions source package in Eoan: New Status in python2.7 source package in Eoan: Fix Committed Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
Hello Eric, or anyone else affected,
Accepted lvm2 into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu4.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: lvm2 (Ubuntu Disco)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-disco
** Changed in: lvm2 (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Committed
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Committed
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
[Touch-packages] [Bug 1854981] Please test proposed package
Hello Eric, or anyone else affected,
Accepted lvm2 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu3.18.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Fix Committed
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Fix Committed
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, for users who will see this fixed, will still experience
the situation in standard ISO, since I'm afraid Disco won't produces
new ISO. (it is not recommended to do new disco installs anyway since
it's going EOL shortly) One would need to rely on the mini.iso for
fetching the latest lvm2 package in the archive.
IIRC Bionic will have a new point release somewhere in Feb 2020 but
until then one would need to rely on the mini.iso for fetching the
latest lvm2 package in the archive as well.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we
[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads
same here on P52, ubuntu 19.10, all completely updated to newest versions provided on official update sites. Additional reboot needed sometimes even more reboots -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847967] Re: oem kernel packages treated differently from generic kernel ones
We have some outstanding security fixes in apport to do but we'll scheduled SRU'ing this after those are out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: Fix Committed Status in apport source package in Bionic: In Progress Status in apport source package in Disco: In Progress Status in apport source package in Eoan: In Progress Status in apport source package in Focal: Fix Committed Bug description: [SRU Justification] [Impact] When `apport-bug linux` was executed on systems with linux-oem, linux-oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. [Fix] Fix already merged in Focal: https://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/focal/apport/ubuntu/revision/2724 . SRU merge proposals in: * https://code.launchpad.net/~vicamo/ubuntu/bionic/apport/bug-1847967/+merge/376380 * https://code.launchpad.net/~vicamo/ubuntu/disco/apport/bug-1847967/+merge/376381 * https://code.launchpad.net/~vicamo/ubuntu/eoan/apport/bug-1847967/+merge/374263 [Test Case] 1. Boot with linux-oem or linux-oem-osp1 kernel and try to collect apport logs with: $ apport-cli --save saved.apport linux-oem-osp1 2. Make sure the report contains PCI/ALSA/DMI/Sysfs info. [Regression Potential] Low. original bug description When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852772] Re: test_updates_interval fails on focal
This bug was fixed in the package software-properties - 0.98.6
---
software-properties (0.98.6) focal; urgency=medium
* cloudarchive: Enable support for the Ussuri Ubuntu Cloud Archive on
18.04 (LP: #1852489).
* softwareproperties/dbus/SoftwarePropertiesDBus.py: In SetUpdateInterval,
convert days argument from dbus.Int32 to int before passing to
set_update_interval. This fixes a test failures as apt_pkg.config.set
didn't understand a dbus.Int32 type (LP: #1852772).
* debian/control: Add gpg and gpg-agent to Build-Depends to fix failing
unit tests (LP: #1852773).
-- Corey Bryant Wed, 13 Nov 2019 16:00:59
-0500
** Changed in: software-properties (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
==
FAIL: test_updates_interval (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in
test_updates_interval
self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config)
AssertionError: False is not true
Looking closer, while in the SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
dbus.Int32 type. A simple print output shows:
days=dbus.Int32(1)
D-Bus is statically typed, unlike python. More details at:
https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types
I think once we're in the dbus method (SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
dbus.Int32 to an int.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852773] Re: test failures on focal due to missing build-depends on gpg and gpg-agent
This bug was fixed in the package software-properties - 0.98.6
---
software-properties (0.98.6) focal; urgency=medium
* cloudarchive: Enable support for the Ussuri Ubuntu Cloud Archive on
18.04 (LP: #1852489).
* softwareproperties/dbus/SoftwarePropertiesDBus.py: In SetUpdateInterval,
convert days argument from dbus.Int32 to int before passing to
set_update_interval. This fixes a test failures as apt_pkg.config.set
didn't understand a dbus.Int32 type (LP: #1852772).
* debian/control: Add gpg and gpg-agent to Build-Depends to fix failing
unit tests (LP: #1852773).
-- Corey Bryant Wed, 13 Nov 2019 16:00:59
-0500
** Changed in: software-properties (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on focal due to missing build-depends on gpg and gpg-
agent
Status in software-properties package in Ubuntu:
Fix Released
Bug description:
==
ERROR: test_add_ppa_signing_key_multiple_fingerprints
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 148, in
test_add_ppa_signing_key_multiple_fingerprints
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_ok (tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 158, in
test_add_ppa_signing_key_ok
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_wrong_fingerprint
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 140, in
test_add_ppa_signing_key_wrong_fingerprint
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File
[Touch-packages] [Bug 1852489] Re: [SRU] Enable support for Ussuri Cloud Archive
This bug was fixed in the package software-properties - 0.98.6 --- software-properties (0.98.6) focal; urgency=medium * cloudarchive: Enable support for the Ussuri Ubuntu Cloud Archive on 18.04 (LP: #1852489). * softwareproperties/dbus/SoftwarePropertiesDBus.py: In SetUpdateInterval, convert days argument from dbus.Int32 to int before passing to set_update_interval. This fixes a test failures as apt_pkg.config.set didn't understand a dbus.Int32 type (LP: #1852772). * debian/control: Add gpg and gpg-agent to Build-Depends to fix failing unit tests (LP: #1852773). -- Corey Bryant Wed, 13 Nov 2019 16:00:59 -0500 ** Changed in: software-properties (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1852489 Title: [SRU] Enable support for Ussuri Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Triaged Status in software-properties source package in Focal: Fix Released Bug description: Please add support for: cloud-archive:ussuri cloud-archive:ussuri-proposed This will also need to be SRU'd back to bionic. [Impact] End users have to manually enable the ussuri cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:ussuri sudo add-apt-repository cloud-archive:ussuri-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Changed in: lvm2 (Ubuntu Xenial)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Fix Released
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
In Progress
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
In Progress
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, user will see this fixed, will still experience the
situation in standard ISO, since I'm afraid there is no more point
release for Bionic and Disco.
So one would need to rely on the mini.iso for fetching the latest lvm2
package in the archive.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if
found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes
** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1854237 Title: autopkgtests fail after security fixes Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Bionic: New Status in apport source package in Disco: New Status in apport source package in Eoan: New Bug description: The following autopkgtests fail after the recent security fixes: log:FAIL: test_get_logind_session (__main__.T) log:FAIL: test_core_dump_packaged (__main__.T) log:FAIL: test_core_dump_unpackaged (__main__.T) log:FAIL: test_crash_setuid_drop (__main__.T) log:FAIL: test_crash_setuid_keep (__main__.T) log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T) log:FAIL: test_lock_symlink (__main__.T) test_get_logind_session is a test failing to keep up with an API change. test_core_dump_* is failures to remove partly written core files. Both of these are easy fixes, I'll have a MP for them soon. test_crash_setuid_* are caused by the dropping of privileges when accessing the crashing process's /proc. They seem to be testing behaviour now explicitly forbidden by the fix to be honest! test_lock_symlink fails because the lock file is now always in /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could update the test, but is it really worth it after the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1854237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1463846] Re: if ip is specified on cmdline, networking should be brought up in initramfs
** Changed in: initramfs-tools (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1463846 Title: if ip is specified on cmdline, networking should be brought up in initramfs Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools package in Debian: New Bug description: if the initramfs has 'ip=' on the cmdline, it is arguable that we should bring the respective interface up as indicated. Currently, initramfs only does this if something thinks it should. Ie, open-iscsi might do it, or some other things might call 'configure_networking'. But it seems reasonable that if the user put 'ip=' on the cmdline then they wanted that to happen in initramfs. Additionally, one feature i'd like to have (admittedly for debug purposes) is the ability to write the /run/initramfs/open- iscsi.interface file that is used at least by open-iscsi to say "do not bring this interface down". I've done this before, the code to do it is available in intramfs-tools style module at http://bazaar.launchpad.net/~smoser/maas/maas-pkg-test/files/head:/ephemtest-vivid/initrd-updates/ generically, it seems like it'd be nice to have a way to have the same functionality that open-iscsi.interface accomplishes but not tied to open-iscsi. Ie, the user may for any reason want to keep a network from getting re-configured by normal OS bringup. I used '/run/network/initramfs-persistent-iface' file to do that. that is explicitly to patch over an existing initramfs (no 'hooks' directory). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1463846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Description changed:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate LVM
volume will not be activate either, but since they don't need to be
mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, user will see this fixed, will still experience the
situation in standard ISO, since I'm afraid there is no more point
release for Bionic and Disco.
So one would need to rely on the mini.iso for fetching the latest lvm2
package in the archive.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
+ Xenial and Eoan and late didn't exhibit the situation.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub parameter
that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
283 log_end_msg
284
=> 285 if read_fstab_entry /usr; then
=> 286 log_begin_msg "Mounting /usr file system"
=> 287 mountfs /usr
=> 288 log_end_msg
=> 289 fi
In this case, /usr is present in /etc/fstab but the logical volume is
not available, so it is mounting a filesystem without his backend
device, thus goes straight to the initramfs prompt because /usr couldn't
be mounted.
It clearly seems to be an 'auto-activation' issue at boot.
For other such as /home, /var, it's not a big deal cause they can be
activated later on in the process and they are (I haven't check but I
guess systemd or systemd unit/generator is taking care of it at some
point), but /usr is a important piece to have mounted
[Touch-packages] [Bug 1774843] Re: apport python exception handler messes up python3.7
** Also affects: python-apt (Ubuntu Focal) Importance: Undecided Status: Invalid ** Also affects: apport (Ubuntu Focal) Importance: Medium Status: Triaged ** Tags removed: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception handler messes up python3.7 Status in Apport: New Status in apport package in Ubuntu: Triaged Status in python-apt package in Ubuntu: Invalid Status in apport source package in Focal: Triaged Status in python-apt source package in Focal: Invalid Bug description: it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1774843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1855297 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
** Tags removed: ddstreet sts-sponsor-ddstreet
--
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/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
Fix Committed
Status in systemd source package in Xenial:
Fix Released
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
...
[Regression Potential]
As the patches change the communication socket between dbus and systemd,
possible regressions could cause systemd to not be notified of dbus events and
vice-versa. We could see units not getting started properly, and communication
between different services break
[Touch-packages] [Bug 1855307] [NEW] nmcli connection modify CONN vpn.secrets "password='xyz, abc'" breaks if password contains comma
Public bug reported: I have tried to set vpn.secrets password using: nmcli connection modify 'ACONNECTION' vpn.secrets 'password=abc,xyz' but it breaks because of the comma in the password. The error is: Error: failed to modify vpn.secrets: 'xyz' is not valid; use =. (my password was a different one but it had the pattern abc,xyz Note the error only contained xyz) UPDATE: also see this: https://unix.stackexchange.com/questions/554298 /nmcli-how-to-escape-comma-and-other-characters-for-shell-script ) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: I have tried to set vpn.secrets password using: nmcli connection modify 'ACONNECTION' vpn.secrets 'password=abc,xyz' but it breaks because of the comma in the password. The error is: Error: failed to modify vpn.secrets: 'xyz' is not valid; use =. + (my password was a different one but it had the pattern abc,xyz Note + the error only contained xyz) - (my password was a different one but it had the pattern abc,xyz Note the error only contained xyz) + UPDATE: also see this: https://unix.stackexchange.com/questions/554298 + /nmcli-how-to-escape-comma-and-other-characters-for-shell-script ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855307 Title: nmcli connection modify CONN vpn.secrets "password='xyz,abc'" breaks if password contains comma Status in network-manager package in Ubuntu: New Bug description: I have tried to set vpn.secrets password using: nmcli connection modify 'ACONNECTION' vpn.secrets 'password=abc,xyz' but it breaks because of the comma in the password. The error is: Error: failed to modify vpn.secrets: 'xyz' is not valid; use =. (my password was a different one but it had the pattern abc,xyz Note the error only contained xyz) UPDATE: also see this: https://unix.stackexchange.com/questions/554298/nmcli-how-to-escape- comma-and-other-characters-for-shell-script ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852772] Re: test_updates_interval fails on focal
** Changed in: software-properties (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
==
FAIL: test_updates_interval (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in
test_updates_interval
self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config)
AssertionError: False is not true
Looking closer, while in the SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
dbus.Int32 type. A simple print output shows:
days=dbus.Int32(1)
D-Bus is statically typed, unlike python. More details at:
https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types
I think once we're in the dbus method (SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
dbus.Int32 to an int.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852773] Re: test failures on focal due to missing build-depends on gpg and gpg-agent
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852773
Title:
test failures on focal due to missing build-depends on gpg and gpg-
agent
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
==
ERROR: test_add_ppa_signing_key_multiple_fingerprints
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 148, in
test_add_ppa_signing_key_multiple_fingerprints
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_ok (tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 158, in
test_add_ppa_signing_key_ok
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
ERROR: test_add_ppa_signing_key_wrong_fingerprint
(tests.test_lp.AddPPASigningKeyTestCase)
--
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
return func(*args, **keywargs)
File "/build/software-properties-0.98.6/tests/test_lp.py", line 140, in
test_add_ppa_signing_key_wrong_fingerprint
res = self.t.add_ppa_signing_key("~mvo/ubuntu/ppa")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
317, in add_ppa_signing_key
minimal_key = self._minimize_key(armored_key)
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
259, in _minimize_key
p = self.gpg_cmd("import-minimal,import-export")
File "/build/software-properties-0.98.6/softwareproperties/ppa.py", line
242, in gpg_cmd
return subprocess.Popen(cmd.split(), stdin=subprocess.PIPE,
stdout=subprocess.PIPE)
File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'gpg'
==
FAIL: test_add_gpg_key (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 372, in
test_add_gpg_key
self.assertTrue(res)
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
** No longer affects: apt (Ubuntu Cosmic) -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852772] Re: test_updates_interval fails on focal
** Tags removed: rls-ff-incoming
** Tags added: rls-ff-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
==
FAIL: test_updates_interval (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in
test_updates_interval
self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config)
AssertionError: False is not true
Looking closer, while in the SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
dbus.Int32 type. A simple print output shows:
days=dbus.Int32(1)
D-Bus is statically typed, unlike python. More details at:
https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types
I think once we're in the dbus method (SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
dbus.Int32 to an int.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
Uploaded in B/D. Waiting for SRU team verification team to approve and
allow packages to start building in -proposed.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Won't Fix
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
In Progress
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
In Progress
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, user will see this fixed, will still experience the
situation in standard ISO, since I'm afraid there is no more point
release for Bionic and Disco.
So one would need to rely on the mini.iso for fetching the latest lvm2
package in the archive.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if
found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
283
[Touch-packages] [Bug 1742912] Re: Please confine guest sessions again
I installed gnome-terminal and got 'unconfined'. So I could view the home directory of another user, but if the directories had no permissions for Other group, I could not view the contents in guest session. So I think a better solution than disabling guest sessions is to make proper default permissions for directories under /home directory. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Changed in: lvm2 (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: lvm2 (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: lvm2 (Ubuntu Disco)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: lvm2 (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Won't Fix
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
In Progress
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
In Progress
Bug description:
[Impact]
In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
Workaround:
At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
[Test Case]
- Install Bionic or Disco
- Create a VG with /usr on its on LV
- Complete the installation
- At reboot the system will be stuck at mounting /usr file system
Extra notes:
Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
LVM volume will not be activate either, but since they don't need to
be mounted in the initramfs space, it's not a problem, they can be
activated later on (after the pivot) by systemd.
So the only combination possible is when /usr is on its separate LV
only.
[Regression potential]
I don't foresee any regression, the fix will instruct udev rule to
pvscan activate volume based on their major/minor number if LVM is
scanned.
+RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
--minor $minor", ENV{LVM_SCANNED}="1"
The current situation doesn't auto-activate at all.
One downside, user will see this fixed, will still experience the
situation in standard ISO, since I'm afraid there is no more point
release for Bionic and Disco.
So one would need to rely on the mini.iso for fetching the latest lvm2
package in the archive.
or use the workaround in the [Impact] section and then apt-get dist-
upgrade in order to get the latest lvm2.
[Other information]
This problem only exhibit in Bionic and Disco.
https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
https://wiki.debian.org/UsrMerge
[Original Description]
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if
found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used
[Touch-packages] [Bug 1463846] Re: if ip is specified on cmdline, networking should be brought up in initramfs
** Also affects: initramfs-tools (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789067 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1463846 Title: if ip is specified on cmdline, networking should be brought up in initramfs Status in cloud-initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools package in Debian: Unknown Bug description: if the initramfs has 'ip=' on the cmdline, it is arguable that we should bring the respective interface up as indicated. Currently, initramfs only does this if something thinks it should. Ie, open-iscsi might do it, or some other things might call 'configure_networking'. But it seems reasonable that if the user put 'ip=' on the cmdline then they wanted that to happen in initramfs. Additionally, one feature i'd like to have (admittedly for debug purposes) is the ability to write the /run/initramfs/open- iscsi.interface file that is used at least by open-iscsi to say "do not bring this interface down". I've done this before, the code to do it is available in intramfs-tools style module at http://bazaar.launchpad.net/~smoser/maas/maas-pkg-test/files/head:/ephemtest-vivid/initrd-updates/ generically, it seems like it'd be nice to have a way to have the same functionality that open-iscsi.interface accomplishes but not tied to open-iscsi. Ie, the user may for any reason want to keep a network from getting re-configured by normal OS bringup. I used '/run/network/initramfs-persistent-iface' file to do that. that is explicitly to patch over an existing initramfs (no 'hooks' directory). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1463846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] [NEW] NetworkManager service fails to secure Ethernet connection when using kernel 5.4
Public bug reported: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
** Also affects: base-files (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Status in update-notifier package in Ubuntu: New Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a nomal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855133] Re: SRU: update python2.7 to the 2.7.17 release
** Also affects: python-stdlib-extensions (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python2.7 (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1855133 Title: SRU: update python2.7 to the 2.7.17 release Status in python-stdlib-extensions package in Ubuntu: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python-stdlib-extensions source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python-stdlib-extensions source package in Eoan: New Status in python2.7 source package in Eoan: New Bug description: This is a proposal to backport the Python 2.7.17 release to bionic. - python2.7 - python-stdlib-extensions - python-defaults is not required, but could be used to trigger autopkg tests in the -proposed pocket. The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for Python 2.7. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the Python test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, an archive rebuild for main was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, python-stdlib-extensions and python2.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. The OpenStack packaging team is checking OpenStack against the built packages in -proposed. Summary of the test rebuilds: https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191107-bionic-gcc7-bionic.html The first one is a reference build, the second one the test rebuild with the updated components. There are no additional regressions except for one Python test, which sometimes hangs on the buildds, sometimes passes (test_ttk_guionly). Will be disabled in a follow-up upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-stdlib-extensions/+bug/1855133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Description changed:
+ ## DRAFT in progress ##
+
+ [Impact]
+ In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM
activation doesn't occurs during the boot process (except for LVM root
partition) and since /usr is an important component before the 'pivot'[0], the
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume
then it will try to mount it while its backend device is not activated yet (due
to the actual auto-activation issue), thus the mounting will fails and bring
the user to the initramfs prompt for debugging.
+
+ Workaround:
+ At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the
boot process.
+
+ [Test Case]
+
+ - Install Bionic or Disco
+ - Create a VG with /usr on its on LV
+ - Complete the installation
+ - At reboot the system will be stuck at mounting /usr file system
+
+ Extra notes:
+ Since this problem is ONLY related to LVM activation. If one create a non-LVM
/usr separate partition, everything will work as expected.
+
+
+ Other separate LVM (e.g. /home, /var/, /srv) if on its own separate LVM
volume will not be activate either, but since they don't need to be mounted in
the initramfs space, it's not a problem, they can be activated later on (after
the pivot) by systemd.
+
+ So the only combination possible is when /usr is on its separate LV
+ only.
+
+ [Regression potential]
+
+ I don't foresee any regression, the fix will instruct udev rule to
+ pvscan activate volume based on their major/minor number if LVM is
+ scanned.
+
+ +RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
+ --minor $minor", ENV{LVM_SCANNED}="1"
+
+ The current situation doesn't auto-activate at all.
+
+ One downside, user will see this fixed, will still experience the
+ situation in standard ISO, since I'm afraid there is no more point
+ release for Bionic and Disco.
+
+ So one would need to rely on the mini.iso for fetching the latest lvm2
+ package in the archive.
+
+ or use the workaround in the [Impact] section and then apt-get dist-upgrade
in order to get the latest lvm2.
+
+
+ [Original Description]
+
Only the lv for root volume get activated, because of the grub parameter
that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the problem
and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
283 log_end_msg
284
=> 285 if read_fstab_entry /usr; then
=> 286 log_begin_msg "Mounting /usr file system"
=> 287 mountfs /usr
=> 288 log_end_msg
=> 289 fi
In this case, /usr is present in /etc/fstab but the logical volume is
not available, so it is mounting a filesystem without his backend
device, thus goes straight to the initramfs prompt because /usr couldn't
be mounted.
It clearly seems to be an 'auto-activation' issue at boot.
For other such as /home, /var, it's not a big deal cause they can be
activated later on in the process and they are (I haven't check but I
guess systemd or systemd unit/generator is taking care of it at some
point), but /usr is a important piece to have mounted before the pivot
since it contains most of the crucial binary, especially that nowadays
/sbin, /bin, and /lib are pointing to /usr:
lrwxrwxrwx 1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Changed in: lvm2 (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Won't Fix
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Confirmed
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Confirmed
Bug description:
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if
found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
283 log_end_msg
284
=> 285 if read_fstab_entry /usr; then
=> 286 log_begin_msg "Mounting /usr file system"
=> 287 mountfs /usr
=> 288 log_end_msg
=> 289 fi
In this case, /usr is present in /etc/fstab but the logical volume is
not available, so it is mounting a filesystem without his backend
device, thus goes straight to the initramfs prompt because /usr
couldn't be mounted.
It clearly seems to be an 'auto-activation' issue at boot.
For other such as /home, /var, it's not a big deal cause they can be
activated later on in the process and they are (I haven't check but I
guess systemd or systemd unit/generator is taking care of it at some
point), but /usr is a important piece to have mounted before the pivot
since it contains most of the crucial binary, especially that nowadays
/sbin, /bin, and /lib are pointing to /usr:
lrwxrwxrwx 1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
lrwxrwxrwx 1 root root 9 Aug 26 13:51 lib64 -> usr/lib64
lrwxrwxrwx 1 root root 9 Aug 26 13:51 lib32 -> usr/lib32
lrwxrwxrwx 1 root root 7 Aug 26 13:51 lib -> usr/lib
lrwxrwxrwx 1 root root 7 Aug 26 13:51 bin -> usr/bin
lrwxrwxrwx 1 root root 8 Aug 26 13:51 sbin -> usr/sbin
NOTE:
* That doesn't affect /usr found in /etc/fstab on its separate
partition when no LVM involve (e.g. /dev/vdb /usr ext4 ). It only
cause issue when /usr is in a LVM context.
* I was able to reproduce on Bionic and Disco so far.
Eoan doesn't seem to exhibit the situation so far in my testing.
* While certain release such as Bionic, Xenial doesn't come implicitly
with the /usr merge approach. One can install package 'usrmerge' and
convert their system /usr merged. I don't think removing the
read_fstable_entry for /usr is an option here, as some user could
potentially decide to convert their system with 'usrmerge' pkg.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1854981/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV
** Also affects: lvm2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: initramfs-tools (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu Disco)
Status: New => Won't Fix
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: initramfs-tools (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: initramfs-tools (Ubuntu)
Status: New => Won't Fix
** Changed in: lvm2 (Ubuntu)
Status: New => Fix Released
** Changed in: lvm2 (Ubuntu Disco)
Status: New => Confirmed
** Changed in: lvm2 (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: lvm2 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: lvm2 (Ubuntu Disco)
Importance: Undecided => Medium
** Changed in: lvm2 (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1854981
Title:
system doesn't properly boot as expected if /usr is on its own LV
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in lvm2 package in Ubuntu:
Fix Released
Status in initramfs-tools source package in Xenial:
Won't Fix
Status in lvm2 source package in Xenial:
Won't Fix
Status in initramfs-tools source package in Bionic:
Won't Fix
Status in lvm2 source package in Bionic:
Confirmed
Status in initramfs-tools source package in Disco:
Won't Fix
Status in lvm2 source package in Disco:
Confirmed
Bug description:
Only the lv for root volume get activated, because of the grub
parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
--lv"
http://man7.org/linux/man-pages/man7/bootparam.7.html
'root=...'
This argument tells the kernel what device is to be used as
the root filesystem while booting.
If one add a separate LV for /usr, the system will go straight to
initramfs prompt failling to mount /usr.
At initramfs prompt, we notice that 'lv-usr' status is 'NOT
available'.
Performing 'lvm vgchange -ay' at initramfs prompt workaround the
problem and allow one to successfully boot.
Adding 'debug' parameter, we clearly we see /root being detected and mounted:
initramfs.debug:
=> + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /root
=> + mountroot_status=0
+ [ ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ read_fstab_entry /usr
+ found=1
+ [ -f /root/etc/fstab ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ / = /usr ]
+ read MNT_FSNAME MNT_DIR MNT_TYPE MNT_OPTS MNT_FREQ MNT_PASS MNT_JUNK
+ [ /usr = /usr ]
+ [ -n ]
+ found=0
+ break 2
+ return 0
+ log_begin_msg Mounting /usr file system
+ _log_msg Begin: Mounting /usr file system ...
then the code read /etc/fstab and specifically search for /usr (most
likely because of the /usr binary merged) and try to mount if if
found.
initramfs-tools:init
271 maybe_break mount
272 log_begin_msg "Mounting root file system"
273 # Always load local and nfs (since these might be needed for /etc or
274 # /usr, irrespective of the boot script used to mount the rootfs).
275 . /scripts/local
276 . /scripts/nfs
277 . /scripts/${BOOT}
278 parse_numeric "${ROOT}"
279 maybe_break mountroot
280 mount_top
281 mount_premount
282 mountroot
283 log_end_msg
284
=> 285 if read_fstab_entry /usr; then
=> 286 log_begin_msg "Mounting /usr file system"
=> 287 mountfs /usr
=> 288 log_end_msg
=> 289 fi
In this case, /usr is present in /etc/fstab but the logical volume is
not available, so it is mounting a filesystem without his backend
device, thus goes straight to the initramfs prompt because /usr
couldn't be mounted.
It clearly seems to be an 'auto-activation' issue at boot.
For other such as /home, /var, it's not a big deal cause they can be
activated later on in the process and they are (I haven't check but I
guess systemd or systemd unit/generator is taking care of it at some
point), but /usr is a important piece to have mounted before the pivot
since it contains most of the crucial binary, especially that nowadays
/sbin, /bin, and /lib are pointing to /usr:
lrwxrwxrwx 1 root root 10 Aug 26 13:51 libx32 -> usr/libx32
lrwxrwxrwx 1 root root 9 Aug 26 13:51 lib64 -> usr/lib64
lrwxrwxrwx 1 root root 9 Aug 26 13:51 lib32 -> usr/lib32
lrwxrwxrwx 1 root root 7 Aug 26 13:51 lib ->
[Touch-packages] [Bug 874283]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/199. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in telepathy-gabble: Unknown Status in telepathy-gabble package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283] Re: Empathy IM Client does not connect to Zimbra via XMPP
** Changed in: telepathy-gabble Status: Incomplete => Unknown ** Bug watch added: gitlab.freedesktop.org/telepathy/telepathy-gabble/issues #199 https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/199 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in telepathy-gabble: Unknown Status in telepathy-gabble package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen
This bug only is present on Wayland. -- 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/1850874 Title: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: This started to happen with Ubuntu 19.10. When an animated gif is displayed in a browser, gnome-shell begins using 100% CPU on all cores. To reproduce: 1) open Firefox, or Chromium 2) load an URL where an animated gif is displayed - you can also use this direct link to https://i.stack.imgur.com/h6viz.gif 3) gnome-shell will start using 100% CPU on all cores (as long as Firefox/Chromium window is in the foreground) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 GsettingsChanges: InstallationDate: Installed on 2019-05-12 (172 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files
This bug was fixed in the package systemd - 229-4ubuntu21.23
---
systemd (229-4ubuntu21.23) xenial; urgency=medium
* d/p/core-use-an-AF_UNIX-SOCK_DGRAM-socket-for-cgroup-age.patch:
- prevent logind from leaking session files (LP: #1846787)
-- Heitor Alves de Siqueira Mon, 07 Oct 2019
07:44:13 -0300
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => 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/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
Fix Committed
Status in systemd source package in Xenial:
Fix Released
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
drwxr-xr-x 2 root
[Touch-packages] [Bug 1846787] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1846787
Title:
systemd-logind leaves leftover sessions and scope files
Status in dbus package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in dbus source package in Xenial:
Fix Committed
Status in systemd source package in Xenial:
Fix Released
Bug description:
[Impact]
Scope file leakage can cause SSH delays and reduce performance in systemd
[Description]
The current systemd-logind version present in Xenial can leave abandoned SSH
sessions and scope files in cases where the host sees a lot of concurrent SSH
connections. These leftover sessions can slow down systemd performance
greatly, and can have an impact on sshd handling a great number of concurrent
connections.
To fix this issue, patches are needed in both dbus and systemd. These improve
the
performance of the communication between dbus and systemd, so that they can
handle a better volume of events (e.g. SSH logins). All of those patches are
already present from Bionic onwards, so we only need those fixes for Xenial.
== Systemd ==
Upstream patches:
- core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification
(d8fdc62037b5)
$ git describe --contains d8fdc62037b5
v230~71^2~2
$ rmadison systemd
systemd | 229-4ubuntu4 | xenial | source, ...
systemd | 229-4ubuntu21.21 | xenial-security | source, ...
systemd | 229-4ubuntu21.22 | xenial-updates | source, ... <
systemd | 237-3ubuntu10| bionic | source, ...
systemd | 237-3ubuntu10.29 | bionic-security | source, ...
systemd | 237-3ubuntu10.29 | bionic-updates | source, ...
systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...
== DBus ==
Upstream patches:
- Only read one message at a time if there are fds pending (892f084eeda0)
- bus: Fix timeout restarts (529600397bca)
- DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)
$ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
dbus-1.11.10~44
dbus-1.11.10~45
dbus-1.11.16~2
$ rmadison dbus
dbus | 1.10.6-1ubuntu3| xenial | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-security | source, ...
dbus | 1.10.6-1ubuntu3.4 | xenial-updates | source, ... <
dbus | 1.12.2-1ubuntu1| bionic | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-security | source, ...
dbus | 1.12.2-1ubuntu1.1 | bionic-updates | source, ...
[Test Case]
1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost
sleep 1 & done
2) Check for leaked sessions in /run/systemd/system/:
multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
drwxr-xr-x 2 root root 160 Oct 4 15:34
[Touch-packages] [Bug 1852933] Re: Failed to read time with suspend-then-hibernate fails
> Sorry, I am new to Linux. How can I know which one it is (missing RTC or missing RTC driver)? If you have real hardware, it should have a RTC. As this isn't a bug, you probably should try asking for help at https://askubuntu.com/ > Also, is there a fix you can think of? You need a working RTC. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- 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/1852933 Title: Failed to read time with suspend-then-hibernate fails Status in systemd package in Ubuntu: Invalid Bug description: systemd version the issue has been seen with 237 Used distribution Ubuntu 18.04 Expected behaviour you didn't see Running suspend-then-hibernate service should put the machine into sleep mode and then hibernate after the delay set in the sleep.conf file. Unexpected behaviour you saw suspend-then-hibernate fails. The status shows: systemd[1]: Starting Suspend; Idle into hibernate... systemd-sleep[13130]: Failed to read time: -9 systemd[1]: systemd-suspend-then-hibernate.service: Main process exited, code systemd[1]: systemd-suspend-then-hibernate.service: Failed with result 'exit- systemd[1]: Failed to start Suspend; Idle into hibernate. Both suspend and hibernate services work fine. Steps to reproduce the problem Running sudo systemctl suspend-then-hibernate generates the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
FWIW, I've not seen this bug in over a year, I totally forgot about it. -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
I don't even know how I setup the reproducer last year. I think I mirrored main in a trusty container and put an apache in front of it, but not sure -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: Confirmed Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxc/issues/3198#issuecomment-562064091 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Bug 1851992 has been opened about the disable-lock-screen option too. But it's private for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851910] Re: Display does not show up (short flashes)
Please try editing /etc/gdm3/custom.conf and then uncomment: #WaylandEnable=false And then reboot. ** Tags added: nvidia ** Summary changed: - Display does not show up (short flashes) + [nvidia] Display does not show up (short flashes) ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-430 (Ubuntu) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** 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/1851910 Title: [nvidia] Display does not show up (short flashes) Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-430 package in Ubuntu: Incomplete Bug description: This issue started recently (I think it could be related to some package update. Steps to reproduce: - Power the PC on; - BIOS Boot screen (not visible, the display is off); - GRUB screen (not visible, the display is off); - Gnome Login screen (not visible, the display is off). Workaround: - after a reasonable time for the Gnome Login Screen to be reached, inserting my user password starts the desktop session. Screen is never shown on first try (the best I can get are short flashes of the desktop in the screen). The display keeps on trying to start. - long press the power button to force power down and immediately switch the PC back on --> after 1 or more workaround cycles the screen is shown (sometimes with wrong horizontal placement). After the display is working, it works smoothly until the next power down (i.e. if I reboot the PC everything is visible from the BIOS Boot screen onward. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompizPlugins: [core,composite,opengl,decor,regex,compiztoolbox,move,resize,imgpng,place,animation,expo,grid,vpswitch,mousepoll,workarounds,snap,gnomecompat,unitymtgrabhandles,session,ezoom,wall,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 09:20:50 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 4.15.0-39-generic, x86_64: installed nvidia, 430.50, 4.15.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8613] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic root=UUID=0c1fbe60-f395-4935-a4dc-eaea4ee92682 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4024 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4024:bd09/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
[Touch-packages] [Bug 1851789] Re: Xorg freeze
Please also tell us exactly which browsers exhibit the bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Summary changed: - Xorg freeze + GUI freeze -- 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/1851789 Title: GUI freeze Status in Ubuntu: Incomplete Bug description: While each window partly unresponsive, the system did not freeze up completely. I was still able to switch active windows or change to different desktops. But within each window, only the previously active part I was still able to interact with. For example in my browser, the active part was the address bar. I was still able to type, but any other interaction (buttons, opening new tabs etc) was not possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 09:51:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a8] InstallationDate: Installed on 2019-03-08 (244 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=6b2676ab-dd94-4534-9d03-ddde577418a3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 06K7YG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn06K7YG:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.product.sku: 07A8 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851649] Re: Package bug
** Package changed: xorg (Ubuntu) => 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/1851649 Title: Package bug Status in Ubuntu: Incomplete Bug description: I couldn't change brightness. Probably this bug is related to the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 14:54:15 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:397d] NVIDIA Corporation GF119M [GeForce 410M] [10de:1054] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF119M [GeForce 410M] [17aa:397d] InstallationDate: Installed on 2019-11-06 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO HuronRiver Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=3f6eec95-af31-4261-96ff-7e5695b716cc ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN43WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570e:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.sku: System SKUNumber dmi.product.version: Lenovo B570e dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1851649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801338] Re: apt fails to properly handle server-side connection closure
Yes, it seems to have something with pipelining, so I disabled it with
the following configuration:
Acquire {
http::Pipeline-Depth "0";
};
I have some machines updating with this setting for 2 days without errors now.
The performance impact seems insignificant (I have low RTT connections).
I also had the error occur on official mirrors, local mirrors with apache, and
local mirrors with lighty before this.
I hope this helps fixing the issue.
--
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/1801338
Title:
apt fails to properly handle server-side connection closure
Status in apt package in Ubuntu:
Triaged
Status in apt source package in Xenial:
Confirmed
Status in apt source package in Bionic:
Triaged
Status in apt source package in Cosmic:
Triaged
Bug description:
[Impact]
In some cases, apt does not correctly handle server-side connection closure
after a pipeline, and aborts the file being downloaded with an "Undetermined
Error" when the connection has been closed.
[Test case]
This could be seen by running apt build-dep evince on cosmic with a recent
apt with the pipelining fix (such as 1.6.6) against a local mirror running
apache from trusty. It remains to be seen whether this is easily reproducible
for anyone.
[Regression potential]
N/A yet.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851349] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + GUI freeze -- 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/1851349 Title: GUI freeze Status in Ubuntu: Incomplete Bug description: Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor now and then. Problem with multitasking. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 10:29:50 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2019-10-18 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/+bug/1851349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1851349] Re: Xorg freeze
Please open two Terminal windows. In one run: dmesg -w In the other run: journalctl -f Now wait and reproduce the freeze a few times. Each time look at those two Terminal windows and tell us if you see any particular messages just after each freeze. -- 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/1851349 Title: GUI freeze Status in Ubuntu: Incomplete Bug description: Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor now and then. Problem with multitasking. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 10:29:50 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2019-10-18 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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/+bug/1851349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
Still happening in Fedora 31 NetworkManager-openconnect-1.2.6-2.fc31.x86_64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
